01 · The idea
Specifically wrong, so you correct it
An empty vault asks “what do you know?” and gets silence. Not because the operator knows nothing, but because nobody can enumerate their own procedure on demand.
A prepopulated runbook asks “is this how you do it?” and gets twenty minutes of an operator saying “no, we do it this way, and here's why.” That is capture, and it is the fastest capture mechanism we have found. The runbook is not the deliverable. It is the instrument that gets your actual procedures out of your head and into a system that keeps them true.
So every procedure ships marked verified: no, and every one ends with a block of real questions (where this differs at your shop), each with a named owner. A note that reads as finished does not get corrected.
02 · Three layers
Whose knowledge is it?
They have different authors, different value and different liability, and the pack tells the truth about its own provenance from the first minute.
Canon: the industry's
How a shop in your trade makes money, the vocabulary, how your field-service software models a job, the seasonal curve. Fixed text, safe to give away, and filed in the vault's reference folder, the one whose whole meaning is third-party material, not ours.
Procedures: ours, until they're yours
The inbound call flow, the estimate follow-up cadence, the weekly ops pack. Written from outside, to be corrected. This is what a Runbook actually is.
Your specifics: only yours
Your fee script, your pricebook rules, who gets escalated to. Not shipped, because nobody can write them in advance. Produced in a working session at the desk the procedure belongs to, and recorded by flipping the procedure to verified: yes with a date and a name.
Progress is a number you can read. The fraction of procedures at verified: yes is the honest measure of how much of your operation is written down. It goes up over an engagement, and it can be put in front of an owner every month.
03 · The first pack
Trades · Plumbing & HVAC
An operating manual for the office of a plumbing, heating and air-conditioning company.
Seventeen procedures
- Front desk: the inbound call flow, web-form and after-hours intake, the missed-call and callback SLA, price and fee questions at the desk, the late-or-reschedule call
- Dispatch: daily dispatch triage and the escalation ladder
- Estimates: the follow-up cadence and the aging-estimates review
- Reputation and membership: the post-job pulse check, responding to a negative review, the membership pitch and lifecycle
- Management: the numbers that matter, the weekly ops pack, the monthly trend review
- People: a new CSR's first week
Day one, three questions
Ask the vault these, in order. Each produces something you can look at and immediately judge as right or wrong.
- “Using the Weekly Ops Pack runbook, build the agenda and the number sheet for Monday's staff meeting.”
- “A customer is disputing the dispatch fee. What do we say?”
- “A new CSR starts Monday. What do they need to know in week one?”
The answers will be close and they will not be yours. Fixing the three things that are wrong is the point. Your front desk then has a script that did not exist that morning.
04 · Scope
The office, never the truck
A Runbook covers nothing a technician does in a customer's home. No diagnostic procedure, no code, no permits, no gas or refrigerant handling, no equipment sizing, no jobsite safety.
Why the line is here
Field work in the trades is licensed and regulated, and the rules change by state and by town. We are not licensed in your trade and we have not read your jurisdiction's code. A document that is wrong about a desk costs a phone call. A document that is wrong about a gas appliance costs something else.
The second reason is less serious and just as real: the office is where the money leaks. Unanswered calls and unchased estimates are the first place we look, and they are a desk problem, not a truck problem.
Not a substitute for
- Legal, employment or tax advice. The scripts are operational, not legal
- Your software vendor's documentation. Where a procedure describes what your system does, the vendor's docs win
- Your own judgment about a customer. Every script is a default for the ordinary case; the exceptions are the job
05 · How you get one
With an engagement, not a download
Runbooks are not sold on their own. A pack comes with a consulting engagement, and the engagement is where it gets localized: read aloud to the person who does the job, corrected in their words, verified with a date and a name.
One pack exists today, for the trades. If your industry is a field-service business with a dispatch board (electrical, pest, landscaping, mobile repair), the shape carries and the vocabulary is the week of work. Ask.
The thinking behind this. A Runbook is the same discipline applied to procedure instead of judgment: written down, attributed, dated, and corrected by the person who does the job. The whole argument is published: Your Archive Is Not a Memory.