SOP structure is the list of sections a procedure has and the order they come in, and the order exists because a procedure has three readers who want different parts. The doer wants the steps. The auditor wants the control block and the records. The owner wants the version history. A structure that puts each where its reader looks is the one that gets used. The standard operating procedure template on this site prints the sections in that order from your task's counts, with the reading time and the training load, free and without an account.
The front: control block, purpose, scope
The control block, with owner, approver, version, approval date and review date, is on page one because it is what an auditor reads first and what says whether the procedure is current. Purpose is one sentence on what the procedure achieves; scope is one sentence on where it applies and stops. Together they take a third of a page.
The body: roles, materials, steps
Roles by position; materials and systems named exactly; then the numbered steps, one action each, the role first, in the order the work happens, with decision points as steps and sub-steps lettered. This is the section the doer reads with a finger on the page, and its length is what the template's reading-time figure measures against the run time.
The back: records and history
Records say what the procedure produces and where it goes; they are what the checklist is cut from and what an auditor checks the steps against. Version history lists every version, what changed, who approved it and when. Both are read after the fact, which is why they close the document. RunbookDesk Pro fills the history as versions are signed.
Why the structure is fixed
The same sections in the same order in every procedure means a reader who knows one knows all of them. A procedure that reorders its sections to suit its writer costs every reader the time to find the steps again. A section the task does not need, materials for a desk task, is removed rather than left as a heading.
Questions people ask about sop structure
Does every SOP need every section?
The control block, steps and records always; materials and decision points when the task has them. Empty headings are removed.
Where does a flowchart fit in the structure?
After the steps, as a view of them carrying the same numbers, when there are enough decision points to justify it.
Can I see the structure filled?
The standard operating procedure example builder prints a worked procedure in this structure from your task's figures, without an account.