How to Write SOPs and Checklists People Actually Follow

Disclosure: this post was written with AI assistance and reviewed before publishing.

Most standard operating procedures die the same way: someone writes a long document, saves it in a shared drive, and nobody opens it again. The problem is rarely the idea of documenting a process. It's that the document is built for the writer, not for the person doing the task at 4 pm on a Friday. Here's a practical way to write SOPs and checklists that get used.

Decide what deserves an SOP

Not everything does. Good candidates share at least one of these traits:

• Repeated at least monthly
• Costly when wrong (payroll, client deliverables, publishing, backups)
• Done by more than one person, or likely to be handed over
• Easy to forget a step because it's done rarely (year-end tasks, onboarding)

Make a quick list of your recurring tasks and score each from 1–3 on frequency and risk. Document the highest scores first.

Checklist or SOP?

These are different tools:

• A checklist is a short list of steps for someone who already knows how to do the task. It prevents skipped steps. Think pilot pre-flight lists.
• An SOP explains how and why for someone learning the task. It includes context, screenshots and decisions.

Often you need both: an SOP for training, and a one-screen checklist extracted from it for daily use.

A structure that works

Keep every SOP in the same format so people know where to look:

1. Title and purpose — one sentence: what this achieves.
2. Owner and last reviewed date — so people know if it's current.
3. When to use it — the trigger ("When a new client signs").
4. What you need — tools, access, files.
5. Steps — numbered, one action per step, starting with a verb.
6. Definition of done — how you know it's finished correctly.
7. Common problems — the two or three things that usually go wrong.

Writing the steps

The steps are where most SOPs fail. A few rules:

• One action per step. "Export the report and send it to finance" is two steps.
• Start with a verb. "Open", "Copy", "Check", "Send".
• Be specific about where. "In Settings → Billing, click Export" beats "export the billing data".
• Mark decision points clearly. "If the invoice is over €1,000, go to step 9; otherwise continue."
• Add a screenshot only where the interface is confusing. Screenshots go out of date fast.

Test it on someone else

The best quality check is to hand the SOP to someone who has never done the task and watch, without helping. Every time they hesitate or ask a question, the document has a gap. Fix it, then repeat with another person if you can. Two rounds usually catch the major problems.

Example: a short publishing checklist

Before publishing a blog post
[ ] Title under 60 characters
[ ] One clear primary keyword in title and first paragraph
[ ] All links tested
[ ] Images have alt text and are compressed
[ ] Meta description written
[ ] Spelling check run
[ ] Author and category set
[ ] Preview checked on mobile

Eight items, one screen, no explanation needed — because the explanation lives in the full SOP.

Keeping SOPs alive

Documentation decays. Build in maintenance:

• Review date on every document; review high-risk ones quarterly.
• Change on contact. Whoever notices a step is wrong updates it immediately (or flags it).
• Single source of truth. Link to the SOP rather than pasting copies into chats.
• Put it where the work happens. Link the checklist from the project template, ticket type or calendar event that triggers the task.

Common mistakes

• Writing an SOP for a process that hasn't stabilised yet. Run it a few times first.
• Documenting the ideal process instead of the real one.
• Burying critical warnings in paragraphs. Put them right before the step they apply to.
• Making it too long. If an SOP passes two pages, split it.

Summary

Pick the processes that are frequent or risky, separate checklists from SOPs, use a consistent seven-part structure, write one verb-led action per step, test with a newcomer and schedule reviews. Short, current and easy to find beats complete and forgotten.

---

If you'd rather start from a ready-made structure, I put together a small, inexpensive, AI-assisted kit on this topic: Checklist and SOP packs. There's a *free sample** (the intro plus one complete template), so you can check whether it's useful before paying anything. Everything above works without it. Other kits: all products.*