Ask the owner of a plumbing company where the procedures live and you usually get one of three answers: "in my head," "in a doc somewhere," or "we tried that once." All three mean the same thing — the owner is the system. Every dispatch decision, every callback argument, every "how do we handle a flooded basement call at 6 p.m. on a Friday" routes through one person's memory, and that person is also on a ladder somewhere with a wrench in their hand.
That is not a discipline problem. It is what happens when a business grows faster than its wiring. The fix is not a 200-page operations manual nobody opens. It is a short stack of standard operating procedures — SOPs — for the handful of jobs that run every week, written the way the work actually happens, and stored where the work starts.
This article gives you the template, the priority list, and the order to write them in.
Why plumbing shops feel this first
Nationwide reports that 71% of small businesses depend on one or two people for their organizational success. Plumbing is that statistic with a phone number: if the owner is the only person who knows how estimates get approved, which supplier gets the after-hours call, and what the callback policy actually is, then the business has a single point of failure wearing a tool belt.
There is a second cost, and it is measured in hours. Intuit QuickBooks' 2024 Business Solutions Survey (630 U.S. owners and executives) found that businesses with 10 to 99 employees reported spending an average of 25 hours a week on manual data entry and reconciling information across applications, and 54% named excessive manual and repetitive tasks as a top challenge. A plumbing shop feels that as re-typed work orders, invoices rebuilt from memory, and the same customer information asked for three times.
The quotable version: 71% of small businesses depend on one or two people — in a plumbing shop, that usually means the business stops when the owner is under a house. An SOP is how the shop keeps running on the owner's worst day, not just their best one.
You do not need to document everything. You need the ten procedures below, in this order, starting with the two that touch money and trust.
The template (copy this structure for every SOP)
Every SOP in your shop should fit the same skeleton, so any tech can open any procedure and find what they need in the same place:
- Title and number — e.g., "SOP 04 — Emergency Call Intake and Dispatch"
- Purpose — one sentence: what this procedure protects (money, safety, the customer relationship)
- Owner — the named person who keeps this SOP true, plus a review date
- When it applies — the trigger: "every call flagged emergency," not "sometimes"
- What you need first — tools, access, information, approvals — before step 1
- Steps — numbered, in order, written as actions a competent tech can follow without the owner
- Definition of done — what "finished" looks like, in writing, so two people are not holding two different pictures of done
- Escalation — the exact situations where the tech stops and calls the owner, with the phone number right there
- The one number — the single metric this SOP is supposed to move (callback rate, days-to-invoice, first-visit fix rate)
Here is that skeleton filled in for the most valuable SOP most shops never write:
SOP 01 — The Callback / Warranty Return Visit. Purpose: a callback is handled the same way every time, so a fixable problem never becomes a reputation problem. Trigger: any customer reporting a failure of work we performed inside the warranty window. Steps: (1) Log the callback against the original job before dispatching anyone. (2) The original tech gets first right to the return visit; if they are unavailable within the promised window, the owner assigns the backup and tells the customer who is coming. (3) Diagnose before replacing parts; photograph the failure and the fix. (4) No charge discussion happens at the door — warranty questions go to the owner the same day. (5) Close the job with the cause written in one plain sentence. Definition of done: customer has a working system, the cause is logged, and the office knows whether it was parts, installation, or diagnosis. Escalation: any callback on a gas line, any sign of water damage beyond the immediate area, any customer asking for a refund. The one number: callbacks per 100 completed jobs.
That is the whole format. One to two pages per SOP, written in the language your crew actually uses.
The 10 SOPs a plumbing business should write first
- Emergency call intake and dispatch — what counts as an emergency, the questions asked every time (shutoff location, water still running, occupants at risk), and who gets woken up in what order.
- Estimate approval and scope sign-off — what a tech can quote on the spot, what needs the owner's approval and above what dollar amount, and what a signed scope must contain before work starts. This is the SOP that kills "but the other guy said it would include…" arguments.
- The standard service call — arrival, walkthrough, diagnosis, options presented, authorization, work, test, cleanup, review request. Same shape every time is what customers are actually buying when they call a "professional" shop.
- Callback and warranty handling — the template above. Callbacks are where reputations are quietly won or lost.
- Water heater replacement — your highest-frequency big-ticket job: sizing questions, permit steps, haul-away, startup checks, and the photo set that proves the install.
- Invoicing and payment collection — what triggers the invoice (job marked complete, not "Friday"), where the numbers come from, card-on-file rules, and the day-by-day overdue cadence. Finished work is not revenue; collected work is revenue.
- Parts, truck stock, and the supplier run — what each truck carries, who restocks, the after-hours supplier protocol, and how a special-order part gets tracked so a job never stalls waiting on a fitting nobody ordered.
- New-hire first two weeks — ride-along order, which SOPs they read on which days, what they may do supervised versus solo, and who signs off. Documented onboarding is what turns a good hire into a productive tech instead of a month of shadowing chaos.
- Safety non-negotiables — gas, confined spaces, lockout, trench and ladder rules, and the stop-work authority: any tech can halt a job on a safety concern without asking permission first. Write this one like lives depend on it, because they do.
- The owner-is-unreachable file — where credentials, banking, supplier accounts, and key customer information live, who can reach them, and the minimum checklist that keeps the shop running for two weeks without the owner. Low frequency, highest consequence — the exact profile humans are worst at planning for.
How to write them without losing a week
Do not sit down and "write the manual." Capture the work instead. For one SOP at a time: have the tech who does the job best talk through it while someone records, or record yourself doing it once, start to finish. Turn that recording into the numbered steps, cut anything that is habit rather than requirement, then have a second tech run the draft cold on a real job and mark every place they had to guess. Those guesses are your edits. Two or three SOPs a month, written this way, gets you the full ten inside a quarter — in the hours you were already spending answering the same questions.
Score before you write: if a process fails, how much money or trust walks out? How often does it run? How much rework does it cause today? Would it stall if one person vanished for two weeks? The highest scores get written first. That filter — not ease of writing — is the priority list.
One illustrative example of the payoff (illustrative math — plug in your real figures): if unclear callback and dispatch handling costs a three-truck shop just two owner phone calls a day at ten minutes each, that is roughly 120 hours a year of the most expensive person in the business doing a job a one-page SOP could route. The SOP does not remove the calls that truly need the owner. It removes the other kind.
What AI can — and can't — do here
AI is genuinely useful for the drafting layer: it can turn a transcript of you talking through a job into a clean numbered first draft, reformat a ten-page ramble into the one-page skeleton above, and keep every SOP in your shop in the same structure so they are easy to scan. Use it for that.
What AI can't do is decide your process. It does not know your approval limits, which supplier actually answers at 9 p.m., which customer gets the owner personally, or where your real practice differs from the textbook version — and a few of those differences exist in every shop. It will also happily write a fluent, confident procedure for a job it has never seen, including steps that are wrong for your code jurisdiction or your equipment. Draft with AI, decide yourself, and have a licensed tech verify anything safety- or code-adjacent before it becomes the shop standard. An SOP that is wrong in writing is worse than no SOP, because now the mistake is official.
The bottom line
A plumbing business does not need more documentation. It needs the ten procedures above, each one page or two, each with an owner, a definition of done, and an escalation line — stored where the work starts, not in a folder nobody opens. Start with emergency intake and estimate approval this month. When the shop runs the same on your day off as on your best day, you will know the SOPs are real.
Build the system around your SOPs: JOJO WORLD's AI Business Tools collection gathers the practical, human-reviewed systems we build for service businesses — lead response, follow-up, intake, and the everyday workflows where AI drafts and you stay in charge. Browse AI Business Tools →