Peak Docs · Use case · SOPs & playbooks
Processes that
everyone understands.
SOPs and playbooks people actually use: a process as a document with steps that become tasks. Shown with a made-up sample team.
Which change do you want to check?
The “Set up a new client” process lives in one colleague's head and in old emails. First write down only the steps, in the order they happen today.
Write it down once,
do it well every time.
- 01In someone's head
- 02Document
- 03In use
A real story starts with its release.
A process only one person knows is a risk.
When they're away, the work stops. An SOP in Peak Docs records the process as a document with numbered steps. Each step can have a checklist, and every checklist item can become a task when the process actually runs.
This pattern shows the structure. It doesn't tell a real customer case yet.
The path to change
A process in three stages.
Knowledge in someone's head
The “Set up a new client” process lives in one colleague's head and in old emails. First write down only the steps, in the order they happen today.
A raw list of stepsEvidence 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 · first notes The document
Create a document of the SOP type. Each step gets a heading, a short explanation and a checklist. Related processes hang below it as subpages.
An SOP with steps and checklistsEvidence format · not filled in yetOne step.
Traceable.BeforeOriginal processSource evidence requiredChangeConcrete interventionProduct view and date requiredExample · SOP with outline The process in use
With the next new client the team walks through the steps and turns open checklist items into tasks. Questions land as comments on the step, improvements as a new version.
The process runs without questionsEvidence 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 · steps as tasks
What can be evidenced
How you notice it holds.
The evidence is still pending
No customer results. You can tell an SOP holds when someone new can run the process without asking.
The sculpture does not depict a customer.
One perspective.
With name and release.
Beyond the single case
What makes any SOP easier.
Describe first, then improve
Write the process down as it is today. Improvements come as a new version; the version comparison shows what changed.
Key ideaStart honestly
One valid version
Flag the SOP as the authoritative version. Peak Docs points out duplicates and shows when a process hasn't been looked after for a long time.
Key ideaOne source instead of many copies
What this article is based on.
Editorial use case with a made-up sample team, not a customer story and no measured values. Document types, wiki subpages, checklist → task, comments, versions, the canonical flag and freshness signals exist in Peak Docs today.
- 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 first process fits on one page.
Create an SOP in Peak Docs and write the steps down as they run today.
Frequently asked questions
Can a checklist step become a task?
Yes. A checklist item can be turned into a task that stays linked to the document.
How do I see that an SOP is outdated?
Peak Docs shows health and freshness signals. Versions with a diff show what changed last.
Are there read confirmations?
No, read confirmations and analytics are planned and not available today.