The half of the job that isn't the work
For a lot of electrical, plumbing, HVAC, and gas work, the actual repair or install is only part of what you're on the hook for. The other part is regulatory: a permit pulled from the local authority before the work begins, and an inspection passed after it's done, before the job can legally be called complete. A panel upgrade, a service change, a water-heater replacement, a new gas line, a rooftop unit swap — these are permit-required jobs in most jurisdictions, and the permit-and-inspection layer is not optional paperwork you can quietly skip when you're busy. Skip the permit and the work is illegal, uninsurable if something goes wrong, and a landmine at the next sale of the property. Skip the inspection and the job technically never closed, no matter how good the work looks.
What makes this genuinely hard to manage isn't the forms — it's that a permit-required job depends on a third party who runs on their own calendar. You pull the permit when the building department is open, you do the work, and then you wait for an inspector whose next available slot might be three days out and whose arrival window is "sometime Thursday." Your job's completion date is no longer something you control; it's gated by a government office. Manage that badly and permitted jobs become the ones that silently sit open for weeks, the ones where the invoice gets disputed because the customer's own final sign-off never happened, and the ones that generate the angriest callbacks when an inspector fails something you thought was done. Manage it well and it's just another kind of multi-visit job with a scheduled dependency baked in.
Fold the permit into the estimate, not the surprise
The first place permits go wrong is the quote. A customer who gets a clean estimate for the work and then a separate, unexplained "permit fee" line weeks later feels nickel-and-dimed, even when the fee is a real municipal cost you're just passing through. And a tech who quotes a job without checking whether it needs a permit can commit you to a price that doesn't cover the permit cost, the pull-time, and the extra inspection trip.
So make the permit part of how the job is scoped from the start:
- Flag permit-required work at estimate time. When you're building the quote, decide then whether this scope trips a permit — most shops know their local rules well enough that the trade and the scope tell you. Put the permit cost and the fact that an inspection is involved on the estimate as a visible line, so the customer approves the whole reality, not just the fun part.
- Price the trips, not just the fee. The permit fee itself is often the small part. The real cost is the time to pull it and the extra visit to meet the inspector — that's a second or third trip to the site that your price book should already account for on permitted job types, so the tech isn't quoting it from scratch each time.
- Set the expectation that completion depends on the inspector. The estimate is also where you first tell the customer that "done" means "passed inspection," which happens on the municipality's timeline. Saying it up front turns a frustrating three-day wait into an expected step instead of a broken promise.
Track permit and inspection status as job states, not sticky notes
The operational heart of managing permits is refusing to let their status live in someone's head. A permit-required job moves through a sequence — permit needed, permit applied for, permit issued, work done, inspection scheduled, inspection passed (or failed and needing a re-inspection) — and every one of those is a state the office needs to be able to see at a glance. When that status lives on a sticky note or in one dispatcher's memory, jobs stall in the gaps: the permit nobody remembered to pull, the finished work waiting on an inspection nobody scheduled, the failed inspection nobody followed up on.
Hosting Field's job state machine already treats a job as something that moves through defined stages rather than a binary open/closed, and permitted work rides on exactly that discipline. The permit and inspection milestones become visible checkpoints on the job — captured with a reusable checklist for that job type so no tech has to remember the sequence — and a job waiting on an inspection is a job the office can see is waiting, not one that has silently gone quiet. That visibility is the whole game: it's the same reason you hunt down jobs stuck in progress, because a permitted job stalled at "waiting on inspection" for two weeks is unbilled revenue and a nervous customer, and you can only chase it if the board shows it.
Schedule around the inspection window like the constraint it is
The inspection is a scheduling dependency, and the shops that handle permitted work smoothly treat it as seriously as they treat their own arrival windows. The inspector's availability determines when the job can close, so the moment the work passes the point where an inspection can be called, someone schedules it — and the job's timeline reflects that the next milestone is out of your hands.
A few practices keep this from wrecking the calendar:
- Book the inspection the moment the work is inspectable. Don't let a completed rough-in sit while everyone assumes someone else called it in. The tech finishing the work should trigger the inspection request the same day, before the site is closed up.
- Plan the re-visit into the day. Many inspections need someone from your crew on site to open things up or answer questions, and that's a trip you have to fit into a route — treat it like the schedule constraint it is so you're not pretending a day is full when an inspection visit was never accounted for.
- Keep the customer informed while you wait. The gap between "work done" and "inspection passed" is exactly when a customer starts wondering if you disappeared. A short note that the work is complete and you're waiting on the municipal inspection — the same proactive communication you'd give on any visit — turns dead air into a status update.
Document the work so it passes the first time
A failed inspection is one of the most expensive events in permitted work: it's a re-visit, a re-inspection wait, sometimes a difficult conversation about who pays for the rework, and always a delay in getting the job to invoice. The cheapest failed inspection is the one that never happens because the work was done and documented to code the first time.
This is where photo evidence earns its keep beyond customer trust. Photos of the rough-in before it's closed up, of the labeled panel, of the fittings and connections that a finished job hides — these are both your proof to the inspector and your defense if a question comes up later. When the inspection is documented as part of the job record, a pass is captured cleanly as the milestone that lets you close and bill, and a fail is captured with exactly what was flagged, so the correction is precise instead of a guessing game. And because it all lives on the job, the permit number, the inspection result, and the photos are retrievable years later — when a customer sells the property, or an insurer asks, or the same equipment needs service and the service history matters.
Be honest about the boundary
Software tracks the permit and inspection status; it does not pull the permit, know your local code, or pass the inspection for you. Hosting Field gives you the place to flag which jobs need a permit, hold the permit and inspection milestones as visible job states, schedule around the inspector's window, and keep the documentation that helps the work pass and proves it later. The actual regulatory obligations — which jobs require permits in your jurisdiction, what your local code demands, which licensed person is allowed to pull and sign for the permit — are real professional responsibilities you carry with your licensing authority and your local building department, not something a job board decides.
What the system does is make sure the paperwork half of the job never silently derails the work half: no permitted job starts un-permitted because someone forgot, no finished job sits unbilled because nobody scheduled the inspection, and no inspection gets failed for something a photo would have caught. Handle permits and inspections as first-class parts of the job — scoped in the estimate, tracked as states, scheduled as constraints, documented as proof — and the regulatory layer stops being the thing that makes trade jobs drag and becomes just another step you run cleanly, start to signed-off finish.