Writing an SOP a remote hire can follow from day one
The single biggest predictor of a successful remote seat is a written procedure. Here is how to write one in an afternoon.
Why SOPs matter more remotely
In an office, missing instructions are filled by overheard conversations. Remotely, they are filled by guesses. A standard operating procedure replaces the guesses and makes the seat transferable if the person changes.
A structure that works
Every SOP we write with clients follows the same outline:
- Purpose — one sentence on why the task exists.
- Trigger — what starts the task (a call, a form, a time of day).
- Steps — numbered, one action each, with screenshots for software.
- Decision rules — what to do when the normal path does not apply.
- Escalation — who to contact, how and by when.
- Definition of done — how the person knows the task is complete.
Record, then write
The fastest method is to record yourself doing the task once while narrating, then turn the recording into steps. A first draft is good enough; the new hire will improve it in the first two weeks by noting where they got stuck.
