How to write SOP is four moves, and the first is not writing. Walk the task with the person who does it best and note every step, decision and record. Draft the numbered steps with the role first inside the seven sections. Test the page by handing it to someone who has never done the task and watching where they stop. Approve the corrected version, record who approved it, and retire whatever it replaces. The standard operating procedure template on this site sizes the document before the first move.
Walk it
Watch the task done by the person who does it best, and write down what they actually do rather than what the process is supposed to be: the step the system does for them, the decision where they call the manager, the form they keep for a reason nobody remembers. The walkthrough is where the procedure is; the meeting room is where the guess is.
Draft it
Purpose and scope in a sentence each; the roles; the systems and forms by name; then the steps, one action each, numbered, the role first, decision points as their own steps that say where to go next; then the records and the version block. The template adds a section per decision point and prints the reading time, so the draft is checked against the task before it is tested.
Test it
Give the page to someone who has never done the task and watch them do it from it. Every place they stop, ask or guess is a rewrite. A procedure that survives that test is one that will survive the day its author is away.
Approve and version it
The person accountable for the outcome signs the corrected version; the sign-off is recorded with the date; the previous version is retired; everyone who follows it reads it and signs. RunbookDesk Pro keeps that record; without it the procedure is a draft with authority nobody can point to.
Questions people ask about how to write sop
How long does it take to write an SOP?
The worked example on the SOP development cost calculator uses four drafting hours, an hour and a half of review and two short approvals; put in your own figures.
What is the most common mistake?
Writing from memory instead of a walkthrough, and skipping the test. Both produce a document that describes the process as it should be rather than as it is.
Who should approve it?
The person accountable for the outcome, who is often not the person who wrote it.