SOP Writing Template 1
SOP skeleton: Purpose → Scope → Owner → Preconditions → Inputs/tools → Numbered procedure → Expected results → Exceptions → Escalation → Records → Version/review date.
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong SOP is executable by its intended user, uses observable actions in the correct order, distinguishes requirements from explanation, names ownership and exceptions, and includes enough verification that readers can tell whether the procedure was completed correctly.
SOP skeleton: Purpose → Scope → Owner → Preconditions → Inputs/tools → Numbered procedure → Expected results → Exceptions → Escalation → Records → Version/review date.
Step format: [#] [Action verb] [object]. If [condition], [branch]. Expected result: [observable state].
Exception block: If [exception], do not [unsafe/default action]. Instead [alternative]. Escalate to [role] when [threshold].
SOP test sheet: New user → completion time → unclear step → missing prerequisite → failed branch → verification result → revision needed.
Scenario transfer worksheet for SOP Writing: current task → [ ]; reader/genre → [ ]; constraint → [ ]; tempting default → [ ]; better decision → [ ]; why it fits → [ ]; next related guide → [ ].
Skill progression worksheet for SOP Writing: beginner version → [ ]; intermediate constraint → [ ]; advanced constraint → [ ]; what changed in the writing decision → [ ]; next skill to study → [ ].
Constraint decision sheet for SOP Writing: normal case → [ ]; harder constraint → [ ]; what must stay true → [ ]; what can change → [ ]; evidence/reader/genre check → [ ]; specialist skill to study next → [ ].
Misconception correction audit for SOP Writing: shortcut or assumption → [ ]; why it fails here → [ ]; corrective move → [ ]; principle that must remain true → [ ]; goal-based next skill → [ ].
Failure-mode and reader-intent audit for SOP Writing: visible symptom → [ ]; likely underlying problem → [ ]; reader need → [ ]; competing technique considered → [ ]; correction → [ ]; evidence/genre/format constraint → [ ]; final verification → [ ].
Boundary-and-tool-choice audit for SOP Writing: reader objection → [ ]; actual writing job → [ ]; evidence/genre/format boundary → [ ]; tempting alternative → [ ]; why it is the wrong tool here → [ ]; correct adjustment → [ ]; final verification → [ ].
Evidence/support and mastery ladder for SOP Writing: minimum acceptable → [ ]; strong → [ ]; expert → [ ]; audience/genre constraint → [ ]; evidence or story support → [ ]; boundary that would require a different technique → [ ].
Certainty and expert-exception audit for SOP Writing: statement or choice → [ ]; evidence/canon/authority supporting it → [ ]; confidence level → [ ]; uncertainty that must be named → [ ]; expert exception → [ ]; nearest alternative technique → [ ]; why the final choice fits better → [ ].
Purpose-and-verification decision audit for SOP Writing: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].
Publication-readiness audit for SOP Writing: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].
Provenance and classification audit for SOP Writing: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Source-record and update audit for SOP Writing: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Source-ledger and revision-history audit for SOP Writing: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].