Peak Docs · Guide · AI documents
Better documents
through good instructions.
A guide to AI documents: a clear instruction, a targeted change, and you review every difference before it is accepted. Three stages with a made-up example.
Which change do you want to check?
Say what the document is for, who reads it and what should happen afterwards. Example: “Project briefing for a new team member, one page, ending with their first three tasks.”
Think first,
then let it write.
- 01Instruction
- 02Draft
- 03Review
A real story starts with its release.
The AI writes as well as you ask.
In Peak Docs the AI proposes changes as a diff you accept or reject. Nothing is applied without you. Your workspace needs AI access for this. This guide shows how an instruction becomes a document you trust.
This pattern shows the structure. It doesn't tell a real customer case yet.
The path to change
An AI document in three stages.
The instruction
Say what the document is for, who reads it and what should happen afterwards. Example: “Project briefing for a new team member, one page, ending with their first three tasks.”
Purpose, reader and outcome are clearEvidence format · not filled in yetThe starting point.
In the original.Original excerptInsert the released passage here.
A / ObservationWhich concrete friction is visible in this source?Example · instruction in three sentences The draft
Let the AI write or rephrase a section. Peak Docs shows the suggestion as a diff against the current text. You accept what fits and reject the rest.
A draft you know sentence by sentenceEvidence format · not filled in yetOne step.
Traceable.BeforeOriginal processSource evidence requiredChangeConcrete interventionProduct view and date requiredExample · suggestion as a diff The review
Check numbers, names and commitments yourself. “Ask this document” helps you find contradictions in your own text, and versions record what the AI changed.
A reviewed documentEvidence format · not filled in yetThe result.
With a yardstick.- Observation
- Not evidenced yet
- Period
- Open
- Source & release
- Pending
Without released data this statement stays open.
Example · checklist before sharing
What can be evidenced
How you recognise a good result.
The evidence is still pending
No customer results and no time-saving promises. You recognise a good result when you can stand behind every sentence.
The sculpture does not depict a customer.
One perspective.
With name and release.
Beyond the single case
What makes every instruction better.
Ask small, change precisely
Ask for one section rather than the whole document. Small suggestions are easier to review and to improve precisely.
Key ideaStay in control
The AI only knows what you give it
It answers from the document and your instruction. Search across all your documents is planned and not available today.
Key ideaProvide the context yourself
What this article is based on.
Editorial guide with a made-up example, not a customer story and no measured values. AI writing with a diff you accept (with AI access in the workspace), “Ask this document”, Document Memory and versions exist in Peak Docs today. AI answers across several documents are planned.
- Editorial demo
Editorial example with made-up sample data. It describes features Peak Docs has today; everything else is marked as example, concept or planned.
- Evidence pending
No released Peak Docs customer story. No customers, quotes or results are shown.
Your next document starts with three sentences.
Open Peak Docs, write down purpose, reader and outcome, and let the AI propose the first section.
Frequently asked questions
Does the AI write straight into my document?
No. Suggestions appear as a diff that you accept or discard.
What do I need for it?
An AI key in the workspace. Without it the AI features stay off.
Does the AI know my other documents?
Not across documents. Retrieval across documents is planned.




