Writing SOPs people actually use

Most SOPs are written once, filed, and never opened again. The failure is almost always in the writing, not the discipline of the team.

Why they get ignored

They're too long. Five pages of prose for a fifteen-minute task. Nobody reads five pages while working.

They describe the ideal, not the real. Written by someone who no longer does the job, they omit the exceptions that make up half of actual practice.

They can't be found in the moment. If it takes ninety seconds to locate, people ask a colleague instead.

They're out of date. Once a team encounters two wrong instructions, they stop trusting all of them.

The format that works

Keep it to one page where possible:

• Purpose: what this achieves, in one line
• Trigger: what starts it
• Owner: the role accountable
• Steps: numbered, each beginning with a verb
• Exceptions: the three or four situations that actually recur, and what to do
• Done means: how you know it's complete and correct

The exceptions section is what separates a real SOP from a wishlist. Ask the person who does the job: "what goes wrong most often?" Their answer belongs in the document.

Write in the imperative

"Open the client folder. Copy the template. Rename it using the client code." Not "the template should then be copied".

Short lines. One action per step. Screenshots only where words would be ambiguous — screenshots age badly and create maintenance work.

Include decision rules

The most valuable content in an SOP isn't the clicking. It's the judgment being encoded:

• Approve under this threshold; escalate above it
• Use option A when the client is new, option B when renewing
• If it's after 4pm on Friday, schedule for Monday

Every rule you write down is a question that stops reaching a manager.

Test before publishing

Have someone who doesn't do the task follow the document exactly. Watch without helping. Every pause, every question, every assumption they get wrong is a fix. This step takes twenty minutes and roughly doubles the quality.

Make them findable

One home, consistent naming, and search that works. Name by question — "How do I onboard a new client?" — not by internal jargon.

If your team uses chat all day, the link should be pasted in chat constantly. Findability is a habit as much as a feature.

Keep them true

Every SOP carries a last-reviewed date and an owner. Quarterly, each owner re-reads theirs and updates the date. Anything older than six months is treated as unverified.

When a process changes, the document changes in the same week, by the person who changed it. This is the single rule that determines whether your documentation is an asset or a liability in a year.

The measure of success

You'll know they're working when new hires stop asking questions that have answers, when the same task produces the same quality regardless of who does it, and when the founder stops being interrupted by decisions someone else could have made from a page.