How to Write an SOP Your Assistant Will Actually Follow
An SOP your assistant will actually follow is short, specific, and lives where the work happens. State the outcome, list numbered steps in plain language, show what done looks like, and assign an owner who keeps it current. The best way to create one is to record yourself doing the task, then turn that recording into steps.
What is an SOP?
An SOP, or standard operating procedure, is a written set of steps for completing a recurring task the same way every time. It turns a process that lives in your head into one anyone on your team can run without asking you.
Good SOPs are the difference between a business that depends on you and one that runs without you. They also protect knowledge: when an assistant follows a documented process, that process stays with the company even if the person moves on.
What is the anatomy of a good SOP?
A good SOP has a predictable structure so anyone can scan it and act. Every SOP should include these parts.
| Component | What it does |
|---|---|
| Title | Names the task clearly so it is easy to find |
| Purpose | One line on why the task matters and the outcome it produces |
| Trigger | When to run this SOP, the event or schedule that starts it |
| Steps | Numbered, plain-language actions in the exact order to do them |
| Definition of done | What a finished, correct result looks like |
| Owner and date | Who maintains it and when it was last updated |
Why should you record, not write?
Recording beats writing because it captures the details you forget to mention. When you write from memory, you skip the small clicks, the exceptions, and the context that make a process actually work.
Do this instead: record your screen while you narrate the task in real time. Then have an assistant, or an AI tool, turn the recording into numbered steps. The video becomes the deep reference and the written steps become the quick scan. AI-trained operators do this fast, which is why KeyPlayers assistants can turn a single recording into a clean, usable SOP without you writing a word.
The reason most SOPs fail is that they are written from memory, so they miss the exact details that trip people up. Record the task once, and the SOP writes itself from what you actually did, not what you think you do.
What does a simple SOP template look like?
Keep the template short enough that filling it out is not a project of its own. Use this structure for any recurring task.
- 1Title: name the task, for example Weekly Pipeline Report.
- 2Purpose: one sentence on the outcome, for example a clean weekly view of deal stages for the Monday review.
- 3Trigger: when it runs, for example every Friday by end of day.
- 4Steps: numbered actions, one action per line, in exact order, with links to the tools or files used.
- 5Definition of done: the finished state, for example report shared in the team channel with all stages updated.
- 6Owner and last updated: the person responsible and the date of the last change.
Write the steps for the person doing the task, not for a compliance binder. Short sentences. One action per step. Link to the exact place the work happens. If a step needs judgment, say what good judgment looks like with a quick example.
How do you keep an SOP alive?
An SOP is a living document, and a stale one is worse than none, because people stop trusting it. Keep it current with three habits.
- Assign an owner: one person is responsible for keeping it accurate.
- Review on a cadence: revisit key SOPs on a set schedule, not only when something breaks.
- Make updates easy: let whoever runs the task flag drift the moment reality no longer matches the doc.
Store SOPs where the work happens, not in a forgotten folder. When your processes live in a shared system your assistant uses daily, the knowledge compounds and stays with the business. That continuity is the real payoff: an SOP is not paperwork, it is the asset that lets the company run without you touching every task.
Frequently asked questions
What makes an SOP actually get followed?
Clarity and simplicity. An SOP gets followed when it states the outcome, lists numbered steps in plain language, shows what done looks like, and lives where the work happens. If it is long, vague, or buried in a folder no one opens, it gets ignored. Write for the person doing the task, not for a manual.
Should I write SOPs or record them?
Record first, then write. The fastest way to capture a process is to record yourself doing it while narrating, then turn that into numbered steps. Recording captures the small details you forget to write down. Use the video as the source and the written steps as the quick reference your assistant scans later.
How do I keep SOPs from going stale?
Assign an owner, add a last-updated date, and review on a set cadence. Make it normal for whoever runs the task to flag when reality no longer matches the doc. An SOP is a living document, not a one-time write-up. The moment it drifts from how the work is actually done, people stop trusting it.