File 00 — Orientation
SOP, checklist, or playbook: which document does the job need?
Owners use the three words as if they were one document. They are not — and the confusion is expensive. A crew handed a 40-step procedure for a five-minute task stops reading procedures altogether. A crew handed a bare checklist for a judgement call improvises. This file settles which document a job needs, using the three forms exactly as they appear inside a Your Deputy pack.
Definitions that hold up on a job site
The three documents, side by side.
| Aspect | SOP / project template | Checklist | Playbook |
|---|---|---|---|
| Answers the question | “What are the phases of this kind of job, in order?” | “Did the required things actually happen?” | “How do we handle this situation when it shows up?” |
| Shape | Phases, each with tasks, in sequence | Short pass/fail items with evidence attached | A trigger, a sequence of moves, and the wording to use |
| Used when | A job opens | A phase is about to close | A repeatable situation occurs |
| In the pack | File 01 — the project template | File 05 — the QA checklists | Files 02, 04, 06 — per-service-line and sequence playbooks |
| Failure mode | Phases close out of order; work gets skipped silently | Boxes get ticked from memory in the truck | Every reminder and request sounds different, or never goes out |
The checklist rule
A checklist beats a procedure when the steps are known and the risk is skipping one.
Nobody needs a paragraph explaining how to photograph a repaired pipe. They need a gate that will not let the job close until the photo exists. That is the whole design of the pack's QA file: five evidence artifacts, pass or fail, filed on the work order. If a task needs teaching, it does not belong on a checklist — it belongs in a playbook or a training note. If a task needs proving, it does not belong in a paragraph — it belongs on a checklist with the evidence attached.
The playbook rule
A playbook beats both when the situation repeats but the details change.
A drain call is never the same drain call — but the sequence is: identify the affected fixtures, run the machine through the cleanout, flush, camera-inspect the main line, photograph the findings, present options before proceeding. A playbook holds that sequence plus the judgement points (when to stop and present options, what never gets promised). The payment-reminder ladder and the review-request sequence are playbooks for the same reason: the timing and wording are fixed, the job inside them is not.
How they nest
One job, three documents, no overlap.
In a running pack the three forms nest without competing. The project template opens the job and walks it through its phases. Inside each phase, a playbook tells the tech how that kind of work is handled. At the end of the phase, a checklist decides whether the phase may close — and it closes only when its evidence is filed. Template for structure, playbook for judgement, checklist for proof. When a document tries to do two of those jobs, it does neither: that is the document your crew has stopped reading.
The field test
Hand it to your newest hire.
The test for any of the three is the same: give the document to the newest person on the crew, with no commentary. If they can run the phase, handle the situation, or prove the work — the document is finished. If they come back with questions, the questions tell you which form you actually needed. A question about order means the template is missing a phase. A question about a situation means a playbook is missing. A question about whether something counts as done means the checklist is missing its evidence line.
From the pack
A Your Deputy trade pack ships all three forms pre-built for your trade — the project template, the per-service-line playbooks, and the QA checklists — so the nesting above is installed, not theorised. See what's included, file by file, or read the next file: File 03 — the pipeline is a promise.
Straight answers
Asked about the three documents.
What is the difference between an SOP and a checklist?
An SOP (here, the project template) defines the phases of a job and the tasks inside each phase, in order. A checklist is the short pass/fail gate at the end of a phase: it proves the required steps and evidence actually happened before the phase may close.
What is a playbook in a service business?
A playbook is the fixed sequence for a situation that repeats with different details — a drain call, a quote follow-up, a late-payment reminder. It holds the order of moves, the judgement points, and the wording, so the situation is handled the same way whoever picks it up.
Which document should a small shop write first?
The checklist for the job that costs you most when a step is skipped — usually closeout evidence. It is the shortest document, it pays back on the first job, and it shows you exactly which phases and playbooks are worth writing next.
End of shift
Your competitors are one missed call away from your customer.
Stop renting a back office. Tour your trade's template pack — the whole system, bought once and delivered as files you keep.
Illustrative sample report — what your end-of-day looks like with your trade pack on the job.