Peak Docs / Personalised documents
The client reads team internals.The team hunts for the essentials.
Often everyone gets the same document although they need different things. Personalised perspectives per role are planned in Peak Docs and not yet available. This page shows the idea as a local concept demo.
One answer changes the follow-up
Pick a sample rating.
Local draft · no product activationConcept demo · feature planned, not yet available.
02 / The missing perspective
Which information does the client side need that the team doesn't?
What stays internal, and what must the team see first?
Concept demo with fictional data · feature planned, not yet available · not the product interface
Check the rule yourself
Change the rating. See the difference.
Pick a rating. At 0 to 6 the perspective question appears, at 7 to 10 it doesn't. Nothing is saved.
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 concept
Perspective first, then the text.
In the example a rating of 0 to 6 triggers the question about the missing perspective. From 7 the section fits.
- 01Rate
Does the section fit this reader?
Base documentOne state with all information.
You rate how well a section fits the client side.
Input → rating from 0 to 10 - 02Separate
At 0 to 6, name the gap.
0–6Follow-up7–10FinishThe sample rule asks what the client side is missing. Today you share a separate released state as a reading page instead.
Condition → 0–6: perspective question - 03Show
Everyone sees their version.
Team sideWhat stays internal, and what must the team see first?
Automatically adapted versions per role are planned. In the trial run only a local note is created.
Concept → local perspective note
What works today
Share exactly the state the client should see.
In Peak Docs you release a specific state as a read-only link as the owner. Internal alignment stays in comments in the document, visible only to your team.
Start Peak Docs for freePeak Docs / Your next step
A document that takes every reader seriously.
Test both paths in the concept and already share a separate state for the client side today.
Check a perspective in the example
For every reader, what matters.
What stays internal, and what must the team see first?
Frequently asked questions
Are there personalised documents per role?
No, this is planned. The page shows the idea as a concept demo with fictitious data.
What can I use instead today?
Templates from your own documents and variables that stay live or are frozen.
When will the feature arrive?
We do not give a date. What is built is listed on the feature pages.