A good SOP example does two things at once: it lists the steps, and it tells the person running those steps what they are allowed to decide. Most SOP examples you will find online only do the first job. They read cleanly, then stall the moment reality shows up — a start date shifts, a laptop is out of stock, a new hire needs a tool that is not on the list — and the person holding the document stops and asks you.
This article puts two versions of the same SOP side by side: a bare-bones, steps-only version, and the same document with a decision-rights block added. Same scenario, same team, same week. The only difference is where the pauses land.
Key takeaways
- A steps-only SOP example documents the happy path and quietly routes every real decision back to the founder.
- The pause is not a training problem. It is a missing section, and adding that section removes the pause.
- The decision block uses four fields: decision | who may decide | limit | escalate when.
- You can build the second version of an SOP in about 15 minutes using the free template at https://tools.exiuss.com/sop-template.
The scenario: onboarding a new hire
Someone starts on Monday. You have a coordinator who handles onboarding, a hiring manager, and you. The coordinator is capable and conscientious. They are also brand new to the limits of their own authority, which nobody has written down.
Version one is the document most small teams actually have. Version two is what it looks like after fifteen minutes of work.
Version one: the bare-bones SOP example (steps only)
- Send the offer letter and welcome email.
- Create the accounts: email, shared drive, project tool.
- Order the standard laptop and set up the desk.
- Schedule the first-week meetings with the team.
- Assign an onboarding buddy.
- Book the 30-day check-in.
Clean, correct, and complete as a description of the happy path. If nothing deviates, the coordinator sails through it.
The exact moment version one stops
Wednesday. The new hire asks whether they can start a week later than the date on the offer so they can finish something at their current job. The coordinator opens the SOP. There is no line for this. The steps say send the offer letter, not what to do when the offer letter needs to change.
So the coordinator does the only sensible thing: they message you. You are in meetings. The new hire waits most of a day for an answer to a question that has two obvious outcomes. Multiply that pause across equipment substitutions, tool access requests, and a manager who wants to shift the 30-day check-in, and the document that was supposed to create independence is mostly generating interruptions.
That is the whole failure. Nothing in version one is wrong. It is just incomplete at the point where a person has to choose.
Version two: the same SOP with a decision-rights block
The six steps stay exactly as they are. Underneath them, one more section goes in — the section most SOP templates leave out:
Decisions this SOP covers
- Start date moves by up to two weeks | hiring manager may decide | limit: no change to offer terms or compensation | escalate to founder if beyond two weeks or if pay changes
- Substitute laptop when the standard spec is unavailable | coordinator may decide | limit: within the approved equipment budget, comparable spec | escalate if the cost goes above the approved amount
- Extra tool access requested in week one | team lead may decide | limit: tools the team already pays for | escalate to founder for any new vendor or contract
- 30-day check-in moved | hiring manager may decide | limit: within the first 60 days | escalate if the move is driven by a performance concern
Same document. Slightly longer. The coordinator now answers the start-date question in the time it takes to read one line, and you hear about it later — or not at all, which is the point.
Side by side
| Situation | Version one (steps only) | Version two (with decision rights) | What it saves |
|---|---|---|---|
| Start date shifts a week | Coordinator stops and asks you | Hiring manager decides within the stated limit | A day of waiting |
| Standard laptop unavailable | Coordinator stops and asks you | Coordinator substitutes inside the budget | A stalled first day |
| New hire wants an extra tool | Coordinator stops and asks you | Team lead approves existing tools, escalates new vendors | A round of messages |
| Check-in needs to move | Coordinator stops and asks you | Hiring manager moves it inside the window | A calendar negotiation |
Read the middle column and notice that every row is the same sentence wearing different clothes: somebody has to ask you. That is the pattern a decision block interrupts.
Why the four fields matter
The format is not decoration. Each field closes a specific gap.
- Decision names the fork in the road, so nobody has to guess whether their situation is covered.
- Who may decide puts a name and a role on the authority instead of leaving it floating.
- Limit draws the boundary in the same breath as the permission, which is what makes delegation safe rather than reckless.
- Escalate when gives the person a clean, non-embarrassing path back to you for the cases that genuinely need you.
Skip the limit and you have not delegated, you have abdicated. Skip the escalation line and people guess, and guessing is how small problems become expensive ones.
How to build version two in about 15 minutes
Open the free SOP template at https://tools.exiuss.com/sop-template. Write your steps the way you already do — plain sentences, no ceremony. When you reach the decision section, hit Fill with an example to see how decisions are written as decision | who may decide | limit | escalate when, then replace the example lines with the ones your team actually hits.
The test for whether you got it right is simple: take the last three things someone interrupted you to ask about. If each one now has a line in the decision block, the SOP is doing its job. If a question has no line, that is your next line to write.
This is the quiet shift from being the person who answers everything to being the person who designed the answering. The document stops describing work and starts holding authority. Your team acts without asking, and the decisions that used to queue outside your calendar get made where the work is.
Quick checklist
- Write the six steps of your process in plain sentences.
- List the last five questions your team brought to you about this process.
- Turn each question into a decision line with all four fields filled in.
- Set a limit on every permission so nobody has to interpret it.
- Write the escalate-when condition for each line, plainly.
- Hand the document to the person who runs it and ask what is still unclear.
When you are ready to build it, the free template is at https://tools.exiuss.com/sop-template — fill in the form, get a clear SOP you can use, and stop being the bottleneck in your own onboarding.