Turn a Rough Process Into a Numbered SOP
The process that lives in one person's head is a risk, not a system. This takes the rough steps you can already describe, numbers them, attaches an owner and a checkpoint to each, and formats the whole thing into an SOP page someone else could follow. Local only; nothing leaves the tab.
- Formatting
- Rough steps numbered, owned, and checkpointed
- local
- What it replaces
- The empty SOP template
- $0.00
- Input
- The process, in rough steps
- no card
- Output
- A numbered SOP page with owners
- recomputed
What you pay otherwise
| Route | What you get | Cost |
|---|---|---|
| Process consultant | Maps your process into a manual | $1k+ |
| SOP software | Templates and approvals, plus a subscription | $10+/mo |
| It stays in one head | The bus-factor risk, undocumented | fragile |
| This page | Your steps, formatted into an SOP | $0 |
The workflow
Describe the steps in the order they happen
One step per line, as rough as you like — 'then email the client the draft'. The builder keeps your order and only adds structure, so the sequence is yours.
Mark owners and checkpoints where you know them
Append '— owner: Sam' or '— check' to a line and the builder formats it. Where you don't know the owner, the page leaves a blank to fill — which is itself a finding.
Read the page as a stranger would
Someone who's never done the job should be able to follow the steps and know where to stop and check. If a step reads 'do the usual thing', that's the step to expand next.
Put the page where the team actually looks
An SOP in a drawer is still one person's head, with extra steps. The page only counts when it's linked in the place work actually happens.
Worked example
Sample: a 6-step client onboarding process Steps 6, numbered in order Owners 3 assigned, 3 left blank to fill Checkpoints 2 (after draft, before send) Uploaded nothing — formatted in the tab
Numbers above are sample data produced by the tool's own pre-loaded example, run in the browser — not averages or measured benchmarks.
What breaks this
Steps written as 'handle onboarding' format into one vague line — break it down to the actions. Leaving every owner blank is the finding you're ignoring: an unowned step is a step that will be skipped. Writing the SOP and never linking it is the quiet failure — the page lives where the work happens, or it doesn't live at all.
Try it now
A six-step onboarding process is loaded and formatted. Paste your own process and watch the SOP page rebuild.
Open the SOP builder →Go deeper: the PDF-ready export
The SOP page is free forever. The $4 one-time tier adds:
- PDF-ready export — the page as a clean, printable document — estimate: ~20 min saved versus reformatting.
- Saved SOP shelf — keep every process in one place — estimate: ~15 min saved per onboarding.
- Version log — track what changed and when — estimate: ~10 min saved.