SOP format
There is no official SOP format, but there is a functional one: a reader has to know when the procedure applies, who does what, in what order, and what to do at each point where the path forks. Here are the seven parts that produce that, and a builder that gives you one as a Word document.
The specific event that starts this, and who notices it. Not a topic.
Comma separated. Job functions, not people's names.
Steps
- 1
- 2
Leave the step number blank if that answer ends the procedure.
- 3
The seven parts, and what each is for
Title
What the procedure is, specific enough to distinguish it from adjacent ones.
People find procedures by scanning titles. A vague title means the document is not found, or the wrong one is opened.
ExampleSupplier invoice approval and payment
Common mistakeNaming a department instead of a process. "Finance procedures" is not a title, it is a folder.
Trigger
The specific event that starts the procedure, and who notices it.
A reader needs to know whether this document applies to the situation in front of them right now. A title alone rarely tells them.
ExampleWhen a supplier invoice arrives in the accounts payable inbox.
Common mistakeStating a topic rather than an event. "Invoice processing" does not tell anyone when to start.
Roles
The job functions involved, named as functions rather than as people.
Names go stale the moment someone changes team. Functions survive reorganisations.
ExampleAccounts Payable, Budget Owner, Finance Director
Common mistakeUsing individuals' names, or omitting roles entirely so every step is addressed to an implied "you".
Numbered steps
One action per step, in order, each starting with the role that performs it.
Numbering lets someone say "I am stuck on step 4", which is far more useful than "somewhere in the middle". Subject-first removes the ambiguity about whose job it is.
Example4. Accounts Payable checks the invoice against the purchase order and the goods receipt.
Common mistakeCompound steps. "Create the folder and share it with the team" is two steps, and it will get half done.
Step detail
Exceptions, thresholds, and known failure modes, attached to the step they affect.
Nobody reads a general notes section at the bottom while executing step 3.
ExampleNever pay from bank details supplied in an email. Verify any change by phoning a number you already hold.
Common mistakeCollecting every caveat in a notes block at the end, where it is invisible at the moment it matters.
Decision branches
At each point where the answer changes the path, the question and where each answer goes.
This is the part almost every template omits, and the part that decides whether the document survives real use. A linear list that assumes the happy path stops being followable exactly where the reader needed help.
ExampleIs the invoice over 10,000? If yes, go to step 7. If no, go to step 9.
Common mistakeDescribing the check but not the consequence, so the reader knows to look but not what to do with either answer.
Review date and owner
When this gets re-checked, and who is accountable for it.
Every procedure has a shelf life. An SOP that is quietly wrong is worse than none, because people follow it.
ExampleReviewed quarterly by the Financial Controller. Last reviewed 7 August 2026.
Common mistakeLeaving it blank, which turns going stale from a visible event into a discovery made by someone doing the wrong thing confidently.
Questions about SOP format
Is there an official SOP format?
No. There is no single standard that dictates SOP layout, and anyone claiming an official format is describing a convention. What is genuinely required is functional: a reader has to know when the procedure applies, who does what, in what order, and what to do at each point where the path forks. ISO 9001 requires documented information to be controlled, identifiable, and approved, but it does not prescribe a layout.
What format should an SOP be written in, Word or Excel?
Word or an equivalent document format suits procedures, because steps have detail and branches that a spreadsheet cell handles badly. Excel suits checklists where the point is ticking off repeated instances. If you find yourself needing merged cells to fit the text, you wanted a document.
How long should an SOP be?
As long as the process, and no longer. If it runs past roughly 15 steps, check whether it is actually two procedures joined at a handoff, which is usually the case. Splitting them and linking is better than one document nobody finishes.
Do I need all seven sections?
The trigger, roles, and numbered steps are not optional; without any one of them the document is not followable. Step detail and decision branches apply where the process has exceptions or forks, and most real processes have both. The review date is what stops it silently going stale.
Should an SOP include screenshots?
For anything performed on a screen, yes, and they are the difference between a procedure people follow and one they skim. The cost is maintenance: screenshots go stale when interfaces change, so they are worth it for stable tools and a liability for ones that change monthly.
Faster than filling in a form
This builder is manual entry, which is the right tool when you already know what the procedure says. If you do not, it is quicker to click through the process once in your browser, or describe it out loud for two minutes, and have the steps written for you. That works with no account either.