A standard operating procedure (SOP) is only useful if someone can follow it without calling you. Most SOPs fail because they are written by the person who already knows the job, so the small steps and the exceptions are missing. This guide shows a simple way to write SOPs a remote team can actually use.
Start with the task, not the document
Do not try to document the whole business at once. Start with the three tasks your team does most often. One good SOP that gets used is worth more than a binder nobody opens.
Record first, write second
- Record the task once with a screen recording, talking through each step and why you do it.
- Have your team member write the SOP from the recording, in their own words.
- Review it together and fill the gaps. The questions they ask are the steps you left out.
Writing it this way also tests whether the person understood the task.
A simple template
Every SOP needs the same six parts:
- Purpose: one line on what the task is for and why it matters.
- When: how often it runs, and what triggers it.
- Tools and access: which systems are used, and where to find them.
- Steps: numbered, one action per step, with a screenshot where a screen is confusing.
- Exceptions: what to do when something does not match, and who to ask.
- Done means: how to check the work is finished and correct.
Write for someone new
- Use plain words and short sentences. Many offshore professionals work in their second language, and clear writing helps everyone.
- Name the exact button, field or folder, not "the usual place".
- Spell out the rules for when to ask. "Use your judgment" is not a step.
- Keep each SOP to one task. If it runs past two pages, split it.
Keep them current
SOPs go stale when tools or rules change. Make updating them part of the job:
- Whoever does the task owns its SOP and updates it when something changes.
- Review each SOP every quarter, or after any mistake it should have prevented.
- Keep all SOPs in one shared folder, with the date they were last checked at the top.
How employmagic helps
From 10 seats, employmagic includes monthly process advisory: 10 hours a month with our operations team. That covers SOPs surfaced and written with your team, team leads chosen and trained in process engineering, team level reporting and a review of which processes AI could improve.