TalkNDone Research · Original Data

What's missing from most trades SOPs — a 25-procedure analysis

We built and graded 25 owner-operator SOPs covering the full trades workflow, then compared them against five widely-used industry references. Three gaps showed up in every reference. None of them are exotic. All of them cost real money when they're missing.

By Brandon Nichols · Working auto tech, founder of TalkNDone · Published May 3, 2026

What we did

Between April 28 and May 3, 2026 we generated 25 standard operating procedures covering the complete owner-operator workflow for a residential trades business — HVAC, plumbing, electrical, auto, and roofing. The 25 procedures were structured into five categories: hiring (5), intake and quoting (5), dispatch and job execution (5), invoicing and collections (5), and follow-up and operations (5). The full list appears below.

Each SOP was scored against a voice-quality rubric — does it sound like an actual operator wrote it, or like a consultant who has never been on a job site? — on a 0–10 scale. The 25-document pack averaged 9.0/10. Total generation time: 21 minutes 26 seconds. Then we compared each procedure's coverage against five industry SOP references that owner-operators commonly buy or borrow from.

The five references we benchmarked against

The three gaps every reference shared

1. Escalation paths to the owner

All five references describe what to do when the job goes well. None describe what to do when it doesn't — specifically, the point at which a tech, dispatcher, or office manager should stop handling the situation themselves and call the owner. In every reference checked, "refund / complaint handling" was a single paragraph or absent entirely. There was no escalation threshold — no "if the customer is asking for a discount over $250, escalate." That gap is what makes a refund cost the owner an hour of phone time instead of a 5-minute decision.

In our 25-SOP pack, two procedures (Refund / Complaint Handling and Escalation to Owner) define the dollar threshold, the time threshold, and the language a non-owner should use to say "let me get the owner on the phone." Specificity here is the difference between an SOP that gets followed and one that gets ignored.

2. Subcontractor coordination

Trades work depends on subs — drywall, flooring, electrical when you're plumbing, plumbing when you're electrical. Three of the five references had zero coverage of subcontractor coordination as a procedure. Trainual and ServiceTitan covered it implicitly inside larger workflows, but neither isolated it as a named SOP. In a real owner-operator shop, subcontractor handoffs are where 30–40% of callbacks originate (the sub left a fitting loose, the framer didn't leave the access panel, the electrician miscut the rough-in). A named SOP for subcontractor coordination — who confirms scope, who signs off on completion, who pays — closes that hole.

3. Job-site arrival as a separate procedure

Every reference described "the service call" as one procedure. None broke out the first 90 seconds at the door — the part where a customer is forming an opinion that determines whether they leave a 5-star or 3-star review. We separated Job-Site Arrival as its own SOP because the way a tech announces themselves, parks the truck, and greets the customer is a repeatable behavior that affects review scores measurably. Two of the five references mentioned arrival in passing; none made it a standalone procedure.

What 9.0/10 looks like in a trades SOP

A voice-graded 9.0/10 SOP shares four traits. We saw all four consistently in our pack and inconsistently in the references.

• Numbered actions, not bulleted concepts."1. Walk the perimeter, note any pre-existing damage with a phone photo" outranks "Document existing conditions" every time. Concept-level bullets are how consultants write SOPs; actions are how operators do.
• Quality checks attached to specific steps.Not "verify the work is complete" at the end of the SOP — actual mid-procedure checks like "before tightening, confirm the gasket is seated by feel, not sight."
• The reason behind each step."Static pressure first, then combustion analysis, because the manometer reading drifts if the burner has been on within the last 5 minutes" is the kind of inline explanation that lets a new tech do the work without calling.
• Common-mistake warnings.The 1–2 things a new person reliably gets wrong. "Do not skip the static-pressure reading even if the system seems to be running fine — you'll miss the closed damper that's about to cause the callback."

The 25 procedures, by category

Methodology limits

This is not a peer-reviewed study and we're not pretending it is. The voice-quality rubric is internal. The five references are ones owner-operators in our network actually use, not a randomly sampled set. The comparative gap analysis is based on reading the public-facing SOP catalog of each reference as of April 30, 2026. Pricing changes, references add procedures. Treat this as a snapshot — useful, not authoritative.

If you're building or buying an operator SOP pack and want a copy of the rubric (the four traits above with scoring guidance), email hello@talkndone.com and I'll send it. Free, no list signup.

Why we wrote this

We sell the Trades Owner-Operator Pack ($497, one-time, 25 SOPs). This research is the raw analysis we did to figure out what to put in it. Publishing it serves two purposes: (a) operators thinking about buying can see the work; (b) operators who'd rather build their own now have a checklist of gaps to close. Both are good outcomes. The version of this market where shops have written-down procedures is one where the work gets done better and the owner sleeps more. Whether the procedures came from us or from somewhere else is secondary.

Cite as: Nichols, B. (2026). What's missing from most trades SOPs — a 25-procedure analysis. TalkNDone Research. https://talkndone.com/research/sop-completion-data