Capture what works.
An SOP toolkit for the work you already know how to do. Write a process down once, while you are doing it, check the work before it goes out, see whether the process is holding, and decide which steps a tool can take over.
Make the process outlive the person who knows it.
Writing a process down can feel like paperwork for its own sake. The toolkit works from the other end: you write the process while you are doing it, keep only what someone else needs to run it, and stop there.
The toolkit turns the unwritten parts of how you already work into a process someone else can follow: the least you need to write down for the work to stop drifting, enough structure around it that the record stays current, and a clear line between what a tool can run and what stays a human call.
When a process only lives in the head of the person who runs it, it leaves with them. With the process written down, you hand a task to someone new with the steps, the checks and the standard already on the page, and you can take a week off while the work runs from it.
Document it, guard it, measure it, automate it.
The guide teaches the thinking, and the four worksheets are where you put it to work, one for each stage of turning a process you repeat into one that runs without you.
How do you get something you could do in your sleep onto paper, so it survives you being off that day?
You fill it in while you work, and come out with a written process someone else could pick up and run.
How do you catch work that is about to go out wrong, before the client is the one who finds it?
A checkpoint you set once. Each check stays highlighted until it is met, so you can see exactly what still has to pass before the work goes out.
Is the process really holding, or does it just feel like it? A few honest numbers settle it.
You enter the raw counts each period. It works out the on-time rate and highlights any period that falls below the target you set.
Which parts of this could run without you, and which must never? The line between them is the whole game.
You sort the steps, name the tool and the trigger, and mark the first one worth building.
The same ideas, tested in other fields for decades.
This method came out of doing the work, and was put through research of its own. The same ideas are established elsewhere. Each is named where the guide meets it, then turned into a worksheet you fill in on your own work.
Taiichi Ohno and the Toyota Production System
Standardised work: a written standard is what every later improvement is built on.
Atul Gawande, The Checklist Manifesto (2009)
Why a short checklist catches what even experts skip under pressure, the idea behind the Quality Gate Checklist.
W. Edwards Deming and the Plan-Do-Check-Act cycle
Set it, run it, measure it and change one thing, the loop behind the Metrics Tracking Sheet.
Start with this one, or take all four.
Includes an SOP Structure, a Quality Gate Checklist, a Metrics Tracking Sheet and an Automation Planner, plus a guide, so the process that only lives in one person's head gets written down once and reused, instead of rebuilt from scratch every time someone is off.
- Repeatable Operations Guide
When to capture, when to leave alone and how to keep documentation useful rather than performative.PDF - SOP StructureDOCX
- Quality Gate ChecklistXLSX
- Metrics Tracking SheetXLSX
- Automation PlannerXLSX
Buying for a team? Access for each person, a private session, or both →
When a process is never written down, it gets rebuilt every time.
This one comes from the operator's side of the same problem. You do good work, the same kinds of tasks come round on every project, and each time you rebuild them from memory, a little differently. The know-how stays with you, so the quality rides on what you remember on the day, and nobody else can pick it up. Work that should get lighter with repetition stays as heavy as it was the first time.
Repeatable Operations is about writing that down once, so it can be repeated instead of reinvented. It is just the least you need for the work to stop drifting: a clear way to document a process, a checklist that holds the quality, a simple way to see whether it is working, and a plan for handing the mechanical parts to a tool. The point is not more admin; it is that the thing only you know how to do stops depending on you being in the room.
If your growth keeps meeting the ceiling of what one person can hold, this is built for that.
The diagnostic points to where to begin.
The Operator Clarity Diagnostic is a short set of questions that reads how your work is carried across decisions, demand, process and value, then names the toolkit most likely to help first.
Answers before you decide.
What exactly do I receive?
The Repeatable Operations Guide (PDF) plus its four worksheets: the SOP Structure, Quality Gate Checklist, Metrics Tracking Sheet and Automation Planner. Ready-to-use files, delivered the moment you buy.
How is it delivered?
The moment your payment clears, an email arrives with a link to open your account, and every file is there, ready to download. Access is permanent.
What if something isn't right?
You get complete, immediate access to the unlocked files, so all sales are final once you have them. If anything is faulty or not as described, your rights under the Consumer Rights Act 2015 still apply: we fix or replace it, or refund you where we can't. Beyond that, any genuine request is considered in good faith, as the Refund Policy sets out.
Is this a subscription?
No. It is a one-time purchase, and what you buy is yours to keep and use.
Can I buy this for my team?
Yes. A team can buy access for each person, book a private session that works through the toolkit on the team's own work, or both, each priced on its own. The For Teams page sets out the options.
Should I buy this toolkit or the Operator Bundle?
Each toolkit stands on its own and covers one area end to end. The Bundle is all four at the same price as buying them separately, with a roadmap for working through them in order, and any toolkit you already own comes off it, so starting with one never costs you more.