A sop example is most useful when the same task gets done by different people on different days, because that is where a process quietly stops being a process. Opening the office, closing the store, running the morning handover — the steps are easy to list. The decisions inside those steps are what change depending on who is working. This article works through one example end to end so you can copy the shape of it, and you can fill in your own version in the free SOP template as you read.
Key takeaways
- The inconsistency in a shift process comes from undocumented decisions, not from missing steps.
- List every judgment call that shifts depending on who is working before you write a single step.
- Capture each decision as a row: decision | who may decide | limit | escalate when.
- Write the steps as a short checklist that points back to the decision table.
Why the process changes depending on who's working
Watch two people open the same office and you'll see it. One arrives, checks the door, turns on the lights, and gets going. The other hesitates at the till, texts the manager about a shortfall, waits for an answer about the broken fixture, and the first hour goes sideways. Nothing in the checklist was wrong. What went wrong is that both people hit a decision the checklist never mentioned, and each handled it differently — or stopped and asked.
The SOP example: opening the office
The example below is deliberately small. One shift, one location, a handful of decisions. The pattern scales to any process where the person changes but the outcome shouldn't.
Step 1: List the decisions that vary by person
Before you write a single step, walk the shift in your head and note every point where the answer depends on who is standing there. Write them as questions, not tasks:
- Can I open early if the delivery arrives before our posted hours?
- The till is short — how short is short enough to just note and move on?
- A fixture is broken. Who calls maintenance, and does it wait until the morning rush ends?
- The alarm code didn't take. Do I try again or call someone?
- A customer wants a refund with no receipt. What can I approve on the spot?
Keep going until you run out. The list will be longer than you expect, and that length is the actual problem you are solving.
Step 2: Fill one row per decision
Turn each question into a row with four fields: the decision, who may decide, the limit, and when to escalate. The limit is what keeps delegation safe — it is the line past which someone else gets involved. The escalate field is what the person reads when they hit that line, so they don't freeze.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Open the doors early | Any opener | Staff are on site and signage is up | Posted hours can't be met at all |
| Cash shortage at open | Any opener | Under $20 — note it and proceed | $20 or more, or the drawer won't balance |
| Broken fixture | Any opener | Move customers clear and mark the area | A trade call is needed or the area must close |
| No-receipt refund | Shift lead | Item is in sellable condition | Customer disputes the outcome or the value is large |
| Alarm code rejected | Any opener | Try once more, then stop | Second attempt fails — call the manager |
That table is the real content of the shift SOP. Everything else is logistics.
Step 3: Write the steps as a plain checklist
With the decisions captured, the steps get short. Each one is an action, and where a step touches a decision, it points at the table.
- Unlock the door and disarm the alarm. If the code is rejected twice, call the manager.
- Turn on lights, and check that the entrance and fire exit are clear.
- Count the till float and record it. If it's short, see the cash row.
- Walk the floor and note anything broken. Move customers clear, then check the fixture row.
- Set up the front, put out the open signage, and log the open time.
- Hand over anything you escalated to the next shift lead.
Six lines. Someone new can run it on their first morning and land in the same place as someone who has done it for a year.
The mistake that keeps the process person-dependent
Most people write the steps first, feel productive, and stop. Then the SOP goes in a folder and the questions keep arriving, because the checklist told people what to do but not what they are allowed to decide. The steps were never the hard part. The judgment calls were.
What changes once the decision table exists
Two things. The first is speed: someone hits a small call, reads the row, acts, and moves on. The second is what stops landing on your desk. Every row you fill in is a question that won't be waiting for you tomorrow morning. Writing the decision down is not about control — it's about release.
Keep the table alive. When a new question arrives, add a row instead of answering it in a message. That way each answer lasts longer than the chat it came from, and the process gets a little more independent every week.
Quick checklist
- Walk the shift and list every decision that varies by person.
- Turn each one into a row: decision | who may decide | limit | escalate when.
- Set a limit that lets someone act without asking.
- Write the escalate line so nobody freezes at the limit.
- Rewrite the steps as a short checklist that points to the table.
- Add a new row every time a question lands on you.
Build your own shift SOP
You don't have to start from a blank page. The free SOP template walks you through the same three steps — decisions, limits, checklist — and you can have your first shift SOP written in about 15 minutes. Hit 'Fill with an example' if you want to see how the decision rows look before you write your own, and if you want to know where the waiting is actually costing you time, the free five-minute diagnostic shows you.
