Peak Docs / Scope of work
“Website relaunch” is in the proposal.Everyone reads something different.
Vague scope descriptions lead to arguments later. In Peak Docs you describe the scope, collect questions as comments on the text and see in the versions what changed.
One answer changes the follow-up
Pick a sample rating.
Local draft · no product activationTest the sample rule — nothing is saved.
02 / The boundary
What is explicitly not included?
A deliverable with scope, boundary and a feedback round.
Example · no real documents · not the product interface
Check the rule yourself
Change the rating. See the difference.
Pick a rating. At 0 to 6 the boundary question appears, at 7 to 10 it doesn't. Nothing is saved or sent.
Local rule demo · Please use neutral sample details only.
Pick a rating to see the next step.
The answer sets the direction.
- Rating
- —
- Follow-up
- Waiting for a rating
No example picked yet.
The rule behind the example
Draw the line first, then record it.
In the example a rating of 0 to 6 triggers the question about the boundary. From 7 the deliverable is described clearly enough.
- 01Describe
One deliverable per section.
Starting point“New homepage including copy.”
You write each deliverable in its own section. The outline shows the scope at a glance.
Section → rating from 0 to 10 - 02Bound
At 0 to 6, ask.
0–6Follow-up7–10FinishThe sample rule asks what is not included. In Peak Docs such questions go as a comment on the passage.
Condition → 0–6: boundary - 03Record
The settled version stays traceable.
ResultA deliverable with scope, boundary and a feedback round.
Versions with a comparison show what changed since the last round. Approval workflows and e-signature are planned.
Sample artifact → scope note
From the rule to a real scope
Write your next scope in Peak Docs.
In Peak Docs you describe the scope together, settle questions as comments, restore earlier versions and export the document as PDF.
Start Peak Docs for freePeak Docs / Your next step
What isn't written isn't agreed.
Test both paths in the example and write the boundary into your next scope.
Check a deliverable in the example
Clear scope, less renegotiation.
A deliverable with scope, boundary and a feedback round.
Frequently asked questions
Can the client approve the scope in Peak Docs?
Not yet. Approval workflows with sequence and roles as well as e-signature are planned.
Can I see what changed between two rounds?
Yes. Versions show changes in a comparison and can be restored.
Which export formats are there?
PDF, Markdown and HTML. There is no DOCX export.