How to Write an SOP Your Team Will Actually Follow (Free Template)
If a process lives only in your head, nobody else can do it, and every handoff turns into a string of questions. A standard operating procedure (SOP) turns that process into clear, repeatable steps, so a new hire or virtual assistant can get it right the first time.
How to Write an SOP in 7 Steps
- 1Choose one task. Start with something repeatable that eats your time.
- 2Record yourself doing it. A screen recording with narration captures details you’d forget to write.
- 3Write the steps in order. One action per step, starting with a verb.
- 4Add context: the purpose, when it happens, and the tools needed.
- 5Cover what goes wrong, including common problems and when to escalate.
- 6Test it by having someone else follow it while you watch.
- 7Review it regularly, and update it whenever the process changes.
Copy-and-Paste SOP Template
Copy this template and replace everything in brackets.
SOP Title: [Task name, e.g., Confirming Next-Day Appointments] Owner: [Role responsible] Last updated: [Date] Purpose [One sentence: why this task matters and what "done" looks like] When to do it [Trigger or schedule, e.g., every weekday at 2 p.m.] Tools needed - [Software or system 1] - [Software or system 2] Steps 1. [First action, starting with a verb] 2. [Second action] 3. [Third action] 4. [Continue until the task is complete] If something goes wrong - [Common problem] β [What to do] - [When to escalate, and to whom] Quality check [How to confirm the task was done correctly] Reference [Link to screen recording or example]
If you can’t hand it off, you haven’t written it down yet.
Tips for SOPs That Get Used
- βKeep steps short. One action per line.
- βUse screenshots or video for anything visual.
- βName the exact tool and button, not just “update the system.”
- βDefine “done” so quality is easy to check.
- βStore SOPs in one place your whole team can find.
- βWriting from memory instead of watching the task done.
- βSkipping exceptions, so the first unusual case stalls the work.
- βNever updating it after the process changes.

Using SOPs to Onboard a Virtual Assistant
SOPs are the fastest way to get a new VA productive. Start with three to five core tasks, review work daily at first, and ask your VA to suggest improvements once they own the process.
See the full plan in our 30-60-90 day virtual assistant onboarding guide, and pick which work to document first with 25 tasks to delegate.
Frequently Asked Questions
What is an SOP?
A standard operating procedure (SOP) is a written, step-by-step guide to completing a recurring task the same way every time.
How do you write an SOP?
Choose one task, record yourself doing it, write the steps in order, add context and exceptions, test it with someone else, and review it regularly.
What should an SOP include?
A title, owner, purpose, trigger or schedule, tools, numbered steps, what to do when something goes wrong, a quality check, and a reference recording.
How long should an SOP be?
As short as possible while still complete. Most task-level SOPs fit on one page, with a video for visual steps.
Do I need SOPs to hire a virtual assistant?
They make onboarding much faster. Start with SOPs for three to five core tasks before day one.