Writing an SOP goes wrong in the same place every time: the writer opens a blank document and starts at the purpose statement. The order that works starts before the document. Pick the task boundary; walk the task with the person who does it best; put the steps, roles, decision points and systems into the sizing tool; then write the steps, one action each; name the records; get the version signed; and set the review date. The standard operating procedure template on this site is the sizing step, free and without an account.
Pick the boundary first
An SOP covers one task from a trigger to a finished state: from the order arriving to the parcel leaving, from the invoice landing to the payment posting. A procedure that covers two triggers is two procedures, and a procedure whose finished state is unclear never ends. Writing the boundary as a sentence before anything else is the cheapest decision in the whole exercise.
Walk it, then size it
The step list comes from watching the task done, not from remembering it. The walkthrough yields the steps, the systems and forms actually used, and the points where the doer stops to decide. Those figures go into the template, which prints the sections, the reading time and the training minutes across the team, so the length is known before the writing.
Write the steps, name the records
One action per numbered step, the role first, the system and form named exactly, decision points as their own steps saying where to go next. The steps that produce a record say so. The example builder on this site turns the step list into the worked example that the procedure's own steps are checked against.
Sign it, train it, date it
The version is signed by the approver; the people who do the task sign that they read it; the review date goes on the cover. Those three records are what an auditor or customer asks for, and they are what RunbookDesk Pro keeps, with a reminder to the owner when the review is due.
Questions people ask about writing an sop
What is the most common mistake when writing an SOP?
Starting to type before the walkthrough. The second is a step that contains two actions, which is the line two people read two ways.
How detailed should the steps be?
Detailed enough that a competent new hire can follow them with a finger on the page. The reading time the tool prints is the check that detail has not become length.
Do I need software to write an SOP?
No. The free tools on this site size and exemplify the procedure; the paid product is for keeping the versions, sign-offs and review dates once it exists.