An SOP format is the fixed order in which a standard operating procedure is written: purpose, scope, steps, decision rights, and revision log. That order matters more than the wording inside it, because it decides whether a reader can act on the document or has to come back and ask you a question. Get the order right and a procedure takes fifteen minutes to write and months to outlive. Get it wrong and you have a document that looks professional and answers nothing.
Key takeaways
- An SOP format is a section order, not a writing style: purpose, scope, steps, decision rights, revision log.
- Decision rights sit directly after the steps because that is where the reader is standing when a judgment call shows up.
- Every decision gets four fields — decision, who may decide, limit, escalate when — so nobody has to guess or wait.
- The free SOP template at https://tools.exiuss.com/sop-template already has these five sections in this order, so you fill in the blanks instead of designing the page.
The SOP format, section by section
Five sections, in this order. Skip one and the document turns into a reference nobody opens twice.
1. Purpose — why this exists
One or two sentences, starting with "so that." So that a customer with a wrong or broken order gets a refund without waiting for the founder. The purpose is not a summary of the steps. It is the argument for following them, and it is what a reader checks when they are deciding whether this document is worth their attention.
2. Scope — where it starts and stops
Who it applies to, what it covers, and — the line most people skip — what it explicitly does not cover. The out-of-scope line does most of the work. It stops someone applying the procedure to a case it was never designed for, and it stops the procedure growing a new branch every time an edge case appears.
3. Steps — the sequence as it actually happens
Numbered, one action per line, verb first. Name the role doing each step when more than one person touches the process. Write the sequence as it happens on a normal week, not the ideal version you would present in a meeting. A step nobody follows is worse than no step at all, because it teaches the reader that the document is decorative.
4. Decision rights — who decides when the steps run out
This is the block most templates leave out. Steps describe the path; decision rights describe what to do when the path ends. Four fields per row: decision | who may decide | limit | escalate when. Name one decision per line. Give it to a role, not a person. State the boundary the role can act within, and the condition that sends it upward.
5. Revision log — who changed what, and when
Date, change, owner. One line per edit. It takes ten seconds to add and it is the difference between a living document and a document everyone quietly distrusts.
| Section | What goes in it | The question it answers |
|---|---|---|
| Purpose | One or two sentences on why the procedure exists | Why does this exist? |
| Scope | Who and what it covers, plus what it excludes | Does this apply here? |
| Steps | Numbered actions, one per line, verb first | What do I do next? |
| Decision rights | Decision, who may decide, limit, escalate when | Can I decide this myself? |
| Revision log | Date, change, owner | Is this current, and who owns it? |
Why decision rights belong after the steps, not in an appendix
A reader moves through an SOP in order. They read the purpose, check that the scope applies to them, then walk the steps. Somewhere around step three or four they hit a case the steps do not cover — a customer asking for something slightly different, an order that does not fit the pattern. That is the exact moment they need to know whether they are allowed to decide it themselves.
If decision rights live in an appendix, the reader has to leave the flow of the document, find the appendix, and map the decision back to the step they were on. Most people do not bother. They close the document and ask you, because asking is faster than hunting. That is a chaos tax paid in interruptions, collected from people who would happily have decided it themselves with one line of permission.
Putting the block straight after the steps fixes the reading order. The reader finishes the steps, hits the judgment calls, and the answers are the next thing on the page. No hunt, no message to you, no waiting.
There is a second reason the placement matters. Writing decision rights immediately after the steps forces you to name the decisions you have been absorbing yourself. You cannot write "who may decide" for a call you have never handed over. The section order makes the delegation visible, and visibility is what makes it happen.
The worked example: a refund SOP in this order
Here is the same format filled in for a refund process, section by section.
Purpose. So that a customer with a wrong, damaged, or missing order gets a refund without waiting for the founder.
Scope. Covers orders placed through our own store. Does not cover chargebacks, wholesale contracts, or marketplace orders.
Steps.
- Find the order in the store dashboard and confirm the customer's email matches.
- Check the delivery status and any photos the customer sent.
- Decide the refund and note the reason on the order timeline.
- Issue the refund to the original payment method.
- Send the customer a short note confirming what happens next.
Decision rights.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Refund a damaged or incorrect item | Support lead | Orders inside the standard return window | The customer wants a replacement instead of money |
| Refund without requiring a return | Support lead | Items where return shipping would cost more than the item | The item is custom or made to order |
| Refund outside the return window | Operations manager | Goodwill refunds only | The request falls outside the manager's approval ceiling |
Revision log. Version 1 — first draft built from the current refund process — owner: support lead.
That is the whole document. Two sentences of purpose, two of scope, five steps, three decisions, one log line.
Quick checklist
- Write the purpose in one or two sentences, starting with "so that"
- List what the SOP covers and what it explicitly does not
- Number the steps, one action per line, verb first
- Add a decision-rights row for every judgment call the steps run into
- Fill all four fields: decision, who may decide, limit, escalate when
- Add a revision log line with date, change, and owner
If you would rather not build the structure from a blank page, the free SOP template at https://tools.exiuss.com/sop-template has all five sections in this order, plus the decision-rights block most templates leave out. Click "Fill with an example" and you can see how a decision is written as decision | who may decide | limit | escalate when before you write your own. The template drafts from your own inputs, so what comes out is your process, not a generic sample. There is also a free five-minute diagnostic if you want to see how much time leaks out of your week before you start. Fill in the form, and you walk away with a procedure your team can follow and a set of decisions you no longer have to make.