SOP upkeep
Stop depending on one person's memory. How your business does things gets written down, and stays true as the work changes.
Hours back
2
hours a week back, typically
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
Processes caught as they're explained
When someone walks a colleague through a process in a meeting, a voice note or a long message, it's noticed and set aside.
- 02
Checked against what you already have
If there's an existing SOP for it, the two are compared. If not, it's marked as new.
- 03
A draft SOP written
Numbered steps in plain language, with who does each step and which tool it happens in. Only processes with at least three steps that will happen again get a draft.
- 04
Drift flagged on existing documents
When someone describes a process differently from the written version, the difference is flagged for the owner to decide which one is right.
- 05
Approved before it's filed
Each draft or change goes to the process owner. Nothing becomes the official version until they approve it.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
Every new SOP and every change to an existing one is approved by the person who owns that process. The system drafts and flags. It never decides how the work should be done.
What it's worth
What those hours add up to.
2 hours a week, over 46 working weeks, is 92 hours a year. At $50 an hour, that’s
$4,600
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
Most procedures live in one or two people's heads. The few that were written down are three years old and nobody trusts them. New starters learn by shadowing, and they pick up whatever shortcuts the person they shadow has picked up.
What we build
- Processes caught as they're explained
- Checked against what you already have
- A draft SOP written
- Drift flagged on existing documents
- Approved before it's filed
A month in
New starters have something accurate to read on day one, and a key person going on holiday stops being a risk. Procedures don't go quietly out of date.
FAQ
Won't it write an SOP for every little thing?
No. SOP upkeep only drafts a procedure when a process has several steps and is likely to happen again. One-off explanations are ignored.
We have nothing written down. Where do we start?
Start with the three or four processes that cause the most mistakes or calls to the office. Those get written down during the build, and from then on they're kept current for you.
More for operations
See them all →Next step
Bring this one to a free live build.
Thirty minutes on sop upkeep. We build its elf with you, live, and you keep it.