Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Most plumbers don't think of permits and inspections as a moneymaker or a money-loser. They think of them as paperwork — a box to check, a thing the office handles, a nuisance the jurisdiction imposes. But watch where jobs actually get stuck, and the pattern is hard to miss: the pipe was set days ago, the crew has moved on, and the job is sitting open because a permit wasn't pulled early enough or an inspection wasn't scheduled in time. Permitting and inspection aren't compliance paperwork bolted onto the job — they're a scheduling workflow that either carries a job to completion or strands it half-finished.
Framed that way, the fix changes. A stranded job doesn't just cost the day you wait on an inspector. It holds your final payment, blocks you from closing the wall, keeps a crew from returning cleanly, and quietly stretches your cash cycle. This is an operations problem, not a legal one — and operations problems have operational answers.
PERMIT / INSPECTION AS A WORKFLOW
job sold
│
├─ permit pulled EARLY ──► rough-in ──► inspection booked ahead ──► pass ──► close + bill
│
└─ permit as afterthought ─► rough-in done ─► "now schedule it" ─► wait ─► job STRANDEDOwner symptoms
Finished-looking jobs sit open for days waiting on a permit or an inspector's visit.
Crews return to a site a second or third time just to catch an inspection window.
Final payments lag because the job can't be formally closed until it's signed off.
Why this happens
Permitting and inspection get treated as events instead of a sequence. The permit is pulled when someone remembers, not when the job is sold. The inspection is scheduled after the rough-in is done, not before — so the crew finishes, then waits. Because no one owns the timeline end to end, each step starts only after the previous one visibly stalls. Add a jurisdiction with a two- or three-day inspection lead time, and a job that was mechanically finished on Tuesday isn't closable until the following week. The delay isn't the inspector's fault; it's the absence of a workflow that stages each step ahead of when it's needed.
Common mistakes
Pulling permits reactively — starting the application when the crew is already scheduled, so the job waits on the paperwork instead of the reverse.
Scheduling inspections after the work, not before — booking the window only once the rough-in is visibly done, forfeiting the jurisdiction's lead time.
No single owner of the timeline — the tech assumes the office has it, the office assumes the tech will call, and nothing gets staged.
Failing an inspection on avoidable details — leaving something inaccessible or unlabeled that a five-minute pre-check would have caught, then eating a full re-inspection cycle.
Not confirming requirements per jurisdiction — treating every city and county as identical when lead times, forms, and inspection rules differ.
Business consequences
A stranded job is expensive in ways that don't show up on any one invoice. The crew's time gets fragmented across return trips. The wall stays open, so the job can't be closed and the final draw can't be billed — which stretches the gap between doing the work and getting paid. On larger jobs, a failed inspection can cascade: the general contractor's schedule slips, and your name is on the slip. The owner who runs permitting and inspection as a staged workflow finishes jobs on the day the pipe is set, bills sooner, and keeps crews moving forward instead of doubling back. Over a year, that's the difference between a smooth cash cycle and one that's always a week behind.
How experienced operators think about it
They treat the permit and the inspection as scheduled milestones on the job timeline, planned backward from completion — not as tasks that begin when the work is done. The mental shift is simple: the inspection lead time is a known input, so it gets booked into the schedule the same way material lead time does. If a jurisdiction needs three days' notice, the inspection is requested when the rough-in is planned, not when it's finished. They also build a short pre-inspection check into the crew's routine, because a job that passes clean the first time is dramatically cheaper than one that cycles. The goal isn't to satisfy the inspector — it's to keep the job moving to close and to bill.
Practical actions
Pull the permit when the job is sold, not when the crew is dispatched. Make it a step in job setup so it never trails the schedule.
Book the inspection ahead of the work. Treat the jurisdiction's lead time as a scheduling input and request the window when you plan the rough-in.
Assign one owner of the permit-to-signoff timeline per job, so no step waits on someone assuming someone else has it.
Run a pre-inspection check before the inspector arrives — access, labeling, test pressure, anything a first-timer commonly flags — to avoid re-inspection cycles.
Keep a per-jurisdiction reference of forms, lead times, and common failure points, so the workflow adapts to where the job is instead of guessing.
Tie closing and billing to signoff. The moment an inspection passes, the job closes and the final draw goes out — no lag.
Questions every owner should ask
On our last stranded job, was it the inspector's schedule — or ours — that actually caused the delay?
Who owns the permit-to-signoff timeline on a given job, and could they name where each step stands right now?
How often do we eat a re-inspection for something a two-minute pre-check would have caught?
Frequently asked questions
Isn't permitting really the jurisdiction's timeline, not something I control?
You don't control how fast an inspector arrives, but you control when you ask. Most delays owners blame on the jurisdiction actually trace to when the permit was pulled or the inspection was requested — both of which are yours to stage. Treat the jurisdiction's lead time as a fixed input you plan around, the way you'd plan around a special-order part, and the "their timeline" problem shrinks to a scheduling problem you can manage. This is general business information, not legal advice. Consult a qualified professional for permitting requirements in your jurisdiction.
We're a small shop — do we really need a formal workflow for this?
The smaller the shop, the more a stranded job hurts, because you have fewer crews to absorb the return trips and a tighter cash position. The workflow doesn't have to be software; it can be two steps on a checklist: pull the permit at job setup, book the inspection when you schedule the rough-in. What matters is that the steps happen ahead of the work by default, instead of after it by memory.
Related articles
Running a Profitable Plumbing Company — the pillar.
Getting More From Your Supply House: Plumbing Vendor Relationships — another lead-time you plan around.
Why Jobs Take Longer Than You Quoted — the general time-overrun problem.
Where Time Leaks on a Typical Job — where the hours actually go.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.