Standard operating procedure: steps, doers and a check for each

One task written out step by step, with who does what, the tools, and how to tell each step is done.

Live example

The example: Closing the shop at Fogbell Bakery

Two roles, twelve steps, a check for each

Closing the shop at Fogbell Bakery

Open the exampleThe names and numbers are made up.

What to notice

  • Version 3.2 and its review date sit above the first step, next to the two changes since the last version and the step numbers they touch.
  • Every step has a "Done when" beside it. For step 04 it's an empty crumb tray and the slicer's plug left on top of the machine.
  • The cash step rules out the obvious shortcut. If the count is more than $5 off the report, it says "don't make it match."

The prompt that starts one like it

Write a standard operating procedure as a single HTML page for [task] at [business]. How we do it now: [your steps or notes]. Put the version, last-reviewed date and owner at the top. List the tools needed, then number every step with who does it and how to tell it's done. Add a table of what to do when something goes wrong, and who to tell. People will read it on a phone, mid-task. Then publish it on sharable.link so only [the people who do the task] can open it.

A procedure that lives in one person's head works until that person is off sick. Written down well, it lets someone in their second week do the job the way your most careful person does it. Open the nightly close at a made-up bakery to see the parts worth copying. The steps of your own task have to come from whoever does it now.

Who it's for

A manager, owner or team lead writing for the people who carry out one task: closing a shop, receiving a pallet, running payroll, sending the weekly newsletter. Send it when someone new starts, and again when the task changes.

It's a poor fit for work that needs judgment at every turn, such as handling a complaint.

What a good one contains

  • A version, a review date and an owner. Version 3.2, reviewed on Monday, November 9, owned by the shop manager. Without those three, nobody can tell whether the copy on their phone is current.
  • What changed. Two lines up top: the register drawer now stays open overnight, and the fridge check moved ahead of mopping.
  • One task with a start and an end. The sample runs from 5:00, doors still open, to both people out by 7:00. Opening the shop is a separate procedure.
  • The tools, ahead of step one. Nine of them. Nobody should learn halfway through that the safe key went home in a coat pocket.
  • Numbered steps with one doer each. Closer, shift lead, or both. A step that belongs to "staff" gets done twice or not at all.
  • A check for every step. "Clean the slicer" is an instruction. "The crumb tray is empty" is something a person can see.
  • What to do when it goes wrong. Six cases, from a warm fridge to an alarm that won't set, each with an action and a person to tell.
  • Where the record lives. A page can't collect initials. The sample points to a paper log and says what a finished night looks like on it.

Write it where the work happens

Draft it standing in the room, or have the person who does the task best talk you through it while you type. Then hand it to someone who has never done it, and watch. Every question they ask is a line you left out.

Keep it short enough to follow with wet hands. When a step keeps being missed, sharpen its check before you add words.

When the task changes, change it in the conversation where you made the page, then replace the page and raise the version number. The link on everyone's phone stays the same, so nobody closes from last month's steps.

How to send it

To named people. It says where the cash goes and when the alarm is set. Only the people who do the closing should be able to open it.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in team and operations

  • Meeting minutes: What a meeting decided and who does what by when, for the people who were there and the ones who weren't.
  • Checklist: Tasks grouped by deadline, each with a box to tick, for a crew, a couple or a family.
  • Employee handbook: A short guide to hours, time off, expenses and equipment that every employee and new hire can open.
  • Performance review: A manager's written review for one person, sent before they talk: goals, evidence, strengths, next steps.
  • 30-60-90 day plan: A new hire's first three months in three phases, each with a test both sides can check.
  • Employee onboarding: The page a new hire gets before day one: the week's schedule, a checklist, the people and the tools.
  • All use cases