An SOP format is the fixed layout you reuse every time you document a process — which sections appear, in what order, and what a reader can count on finding in each one. Most formats give you steps and nothing else, which is exactly why a task done by different people on different days keeps drifting. The format below adds the part that stops the drift: a short table of decisions, with who is allowed to make each one.
Key takeaways
- Inconsistency between shifts is usually an unwritten decision-rights problem, not a training problem.
- A working SOP format has two halves: a decision table written as decision | who may decide | limit | escalate when, and a plain checklist of steps.
- Fill in the decisions first; the steps are fast once nobody has to guess who is allowed to act.
- You can build one for a routine shift process — opening, closing, handover — in about fifteen minutes.
Why the same process gives different results
Two people run the same opening routine and the morning looks different. One opener sees a light fixture flickering, messages you, and waits for a reply before unlocking the front. Another opener sees the same fixture, notes it, and gets on with the morning. Same instructions, same building, two very different openings.
The difference isn't skill or care. Neither opener knew what they were allowed to decide, so one guessed and one waited. Until you write those permissions down, the process is really being run by whoever happens to be on shift and how confident they feel that day.
An SOP format built for work that changes hands
For a process that hands off between people, the format has two sections in this order:
- The decision table — every judgement call the process requires, with who may make it, the limit they can act within, and the trigger that sends it upward.
- The steps — a short checklist of what gets done, in order, pointing back at the table wherever a decision comes up.
That order matters. If you write the steps first, you end up encoding one person's instincts and calling it a process. If you settle the decisions first, the steps almost write themselves. The free SOP template at https://tools.exiuss.com/sop-template lays out both sections already, and its "Fill with an example" button shows the decision table filled in so you can see the shape before you commit your own.
Step one: list every decision that varies by person
Don't start from the process. Start from your messages. Every time someone messaged you mid-shift to ask whether they could do something, that was a decision with no owner — a missing row. Scroll back through a couple of weeks and collect them.
Then walk the process in your head and stop at every "well, it depends." For an opening routine, the list usually includes things like: approving an early opening when a delivery arrives before hours, handling a cash drawer that comes up short, calling a contractor for a broken fixture, sending someone home when the shift is overstaffed, and deciding whether a no-show counts as a call-out.
Step two: fill four fields for every decision
The table is the whole point of this format. Four columns, one row per decision.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Open early for a delivery | Any opener on shift | Only with a scheduled delivery and a second person present | No second person, or the delivery isn't on the schedule |
| Cash drawer comes up short | Any opener on shift | Within the small-shortage limit you set — note it and carry on | Above that limit, or a second shortage within the same week |
| Broken fixture or equipment | Any opener on shift | Can log it and place a service call during business hours | It affects safety, security, or the ability to open |
| Send someone home early | Shift lead | Only when the floor is covered for the rest of the shift | Someone would be left alone on the floor |
| Suspected no-show | Shift lead | Text the person, note the time, start the shift short-handed | No reply after the point you've decided is too late, or it's the second time that month |
Four things to get right:
- Who may decide is a role, not a name. Names change and leave; roles stay. "Any opener on shift" survives turnover in a way that "Sam" does not.
- The limit is a number you choose deliberately. Pick a shortage figure small enough that a phone call would be silly and large enough that you'd want to know about it.
- Escalate when is a trigger, not a mood. Write the actual condition — above the limit, not covered by any row, safety affected.
- "Ask me" is not a decision right. If every row ends in a phone call to you, you've documented the bottleneck instead of removing it.
Step three: write the steps as a checklist
Now the steps, and keep them plain. Short imperative lines in the order they happen: unlock and disarm, walk the floor, check the drawer against the count sheet, power up the equipment, check the schedule against who's arrived. Wherever a decision point lands, point at the table by name — "if the drawer is short, follow the cash row" — instead of restating the rule twice and letting the two versions drift apart.
A checklist someone can actually run at the start of a shift beats a two-page narrative nobody opens.
The mistake that undoes all of it
The common failure isn't a missing step. It's writing "ask the manager" as the answer for every decision, which just moves the queue from the floor to your phone. The second most common is writing the steps perfectly and leaving the decisions in your head — the document looks complete, and the same questions keep arriving.
The advanced move: treat the table as a delegation ladder
Once the table exists, it becomes a tool rather than a document. Any time you get asked the same question twice, that's a signal to move a row one level down and give it a limit. Over a few months, decisions migrate from you to the shift lead to any opener on shift, each with a boundary attached. That's how a process stops depending on who's working without you having to re-explain it every time.
Quick checklist
- List the last ten questions your team asked you mid-shift; each one is a missing decision row.
- Write each decision as decision | who may decide | limit | escalate when.
- Replace every name in the "who may decide" column with a role.
- Set a real limit for each row so the boundary is obvious without a phone call.
- Convert the steps into short checklist lines that point back at the table by name.
- Run one shift with it, then fix the rows that still produced a message to you.
The full layout, with the decision table and the checklist already in place, is at https://tools.exiuss.com/sop-template. It's free, it drafts from what you type in, and fifteen minutes is genuinely enough to get your first shift SOP out of your head and into a document your team can run without you.
