How to write a SOP is mostly four decisions, and the typing that follows takes a fraction of the time the decisions save. Decide the boundary, what triggers the task and what state finishes it. Decide the roles. Decide where the task branches. Decide which steps leave a record. Then type the numbered steps, one action each, role first, and sign the version. The standard operating procedure example builder on this site prints a worked document from those four decisions so the typing starts from the right shape.
Decision one: the boundary
One task, one trigger, one finished state, written as a sentence at the top. A procedure with two triggers is two procedures; one with no finished state is never complete. This is the cheapest decision in the process and the one most often skipped, which is why so many procedures sprawl.
Decisions two and three: roles and branches
Roles are positions, named so the document survives staff changes, and the hand-offs between them are where a task stalls. Branches are the points where the next step depends on what was found; each becomes its own numbered step that says where to go. Counting both before writing is what the builder uses to size the document.
Decision four: the records
Which steps produce evidence: the dispatch note, the reconciliation, the sign-off. Those steps say so in the procedure, become the lines of the checklist, and the completed checklist is the record an auditor reads. A procedure that never says what it produces cannot be evidenced as followed.
Then the typing, and the signature
One action per numbered step, role first, system and form named exactly, sub-steps lettered under their step. Then the approver signs the version, the doers sign that they read it, and the review date goes on the cover. RunbookDesk Pro keeps those three records and reminds the owner when the review is due.
Questions people ask about how to write a sop
How long does it take?
The walkthrough that produces the four decisions is most of it; the typing is an hour for a typical procedure once the shape is right.
What if the task is different every time?
Then the branches are the procedure. Write each decision point as a step with its outcomes; if there are more decisions than actions, it may be a guideline rather than a procedure.
Is the example builder free?
Yes, without an account. Keeping the signed procedure and its versions is the paid product.