Documenting processes without dying trying: the one-page SOP.

“Documenting the processes” sounds like an endless project, which is why it never starts. But the problem isn't documenting: it's over-documenting. A long manual ages the day it's finished and nobody consults it when it matters.

What does work in service companies is the one-page SOP: a short document per process, with the minimum for someone to do it well without asking.

What the page includes

• Why the process exists. One sentence. If it doesn't fit in one sentence, it's two processes.
• When it starts and when it ends. The trigger (an inquiry arrives, a contract is signed) and the result (quote sent, client registered).
• The steps, in order. Between five and ten. Each with who does it and which tool they use.
• The minimum information. Which data or documents are needed so the process doesn't get stuck.
• The decision criteria. What gets approved, what gets escalated, what is never promised. This is the most valuable part.
• Known exceptions. Two or three rare cases and what was done. They get added over time.

What gets left out

Screenshots of every click, the history of the process, long justifications, anything that changes every month. If something needs a long explanation, it goes in a separate linked document; the page stays clean.

How to write it in an hour

The owner doesn't write it alone. It's done in a process interview: the person who executes it best tells it out loud with a real case, someone takes notes (or it's recorded and AI transcribes), and the draft comes from that. It's reviewed once with another team member and published. Not perfect; usable.

How to keep it alive

• One owner per document. A person responsible for updating it when the process changes.
• Every new exception gets noted. That's where the value grows: in the rules for the rare cases.
• Visible last-review date. If it's older than six months, someone looks at it.

A process documented on one page isn't bureaucracy. It's the difference between depending on a person and being able to train, delegate or automate.

The natural next step

Once you have three or four processes like this, the automation candidates appear on their own: the repeated steps with clear rules and low risk. And when an internal AI assistant needs to “know” how your company works, these pages are exactly what it will read.