A plumbing job that requires a permit and doesn't have one is a liability. A job that stalls waiting for an inspection because no one tracked the inspection request is lost revenue. Permit management is not glamorous, but it's one of the highest-risk administrative gaps in a growing plumbing company — and software handles it better than any manual system.
TL;DR
- An estimated 25–35% of plumbing companies performing permitted work have experienced at least one project delay due to missed permit milestones or inspection scheduling failures (industry survey data)
- Permit-related delays average 3–7 business days per occurrence — directly delaying job completion and invoicing
- Jobs completed without required permits expose plumbing contractors to license suspension, customer liability, and mandatory re-work costs that can exceed the original job value
- Software-based permit tracking reduces permit-related delays by 70–85% through automated milestone reminders and inspection scheduling prompts
- Project close-out time (final documentation and customer sign-off) drops by 40–60% when permit documentation is maintained in the job record throughout the project
The Real Risk of Manual Permit Management
Permit requirements for plumbing work vary by jurisdiction, job type, and scope. Water heater replacements require permits in most U.S. municipalities. Drain line replacements, water service replacements, gas piping work — all typically require permits, inspections, and final sign-off before the job is considered complete.
Most plumbing companies have a general awareness of which job types require permits. The failure happens in the execution:
Permit pulled but not tracked. The permit is obtained, the work is completed, and no one tracks whether the inspection was called for. The permit expires (most have 180-day validity), the job is technically incomplete from a compliance standpoint, and the homeowner discovers this when they try to sell the house.
Inspection not called when ready. Work is complete, the technician moves to the next job, and the inspection scheduling task disappears in the operational chaos. Days pass. The GC is waiting on the plumbing final. The delay shows up as a professional failure.
Multiple jurisdiction rules. A plumbing company working across multiple municipalities deals with different permit requirements, fee structures, and inspection procedures per jurisdiction. Managing this manually — remembering which jobs in which cities require what permits — is error-prone at scale.
Documentation not filed. Final permit certificates, inspection reports, and code compliance records need to be retained and associated with the specific property. Without a system, this documentation lives in a file folder that may or may not be findable when needed.
What Permit Tracking Software Does
Permit tracking integrated into job management software handles the permit lifecycle as a defined workflow:
Permit requirement identification When a job is created, the system identifies whether a permit is required based on job type and jurisdiction. The dispatcher or project manager sees a "permit required" flag before scheduling. The permit application process starts at job creation, not as an afterthought after the work is already scheduled.
Permit application tracking The permit application is recorded in the job record: application date, permit number, jurisdiction, fees paid, and expected issuance date. Status is tracked through application submitted → permit issued → work authorized.
Inspection milestone scheduling For jobs with multiple required inspections (rough-in, pressure test, final), the system maintains an inspection checklist. When work reaches an inspection-ready milestone, the system prompts the appropriate person to schedule the inspection. The inspection date is added to the project timeline, and a reminder triggers the day before.
Inspection results logging Each inspection result — pass, fail, conditional pass — is recorded with any corrective action requirements. Failed inspections trigger task creation for corrective work. Re-inspection scheduling happens from the same record.
Document storage Permit certificates, inspection reports, and code correction notices are stored in the job record and attached to the property record in the CRM. When a homeowner calls two years later asking for their water heater permit documentation, it's in the system.
Expiration tracking Permits with time limits generate automatic alerts as expiration approaches. A permit pulled in January that hasn't been finaled by November triggers an escalating warning sequence rather than quietly expiring.
Permit Management for Multi-Jurisdiction Operations
Plumbing companies working across multiple municipalities — common for suburban and regional operations — face the additional complexity of jurisdiction-specific requirements. The inspection procedure for a water heater replacement in one city may differ from the procedure in the adjacent city. Fee structures differ. Some jurisdictions accept applications online; others require in-person filing.
Software that maps job addresses to their relevant building department handles this automatically. The permit workflow for a job in jurisdiction A uses A's rules; jurisdiction B jobs use B's rules. Technicians and project managers don't need to know each jurisdiction's requirements — the system guides them through the correct process.
This is particularly valuable for companies expanding their service area. Adding a new jurisdiction should require updating the system configuration, not retraining every employee on new rules.
Code Compliance Documentation
Beyond the permit itself, plumbing work subject to code inspection generates compliance documentation that needs to be maintained:
- Approved permit documents: The stamped permit that authorizes the work
- Inspection sign-off records: The inspector's signature or digital confirmation that work passed
- Code correction notices: Any identified violations and their resolution
- As-built drawings (for commercial and significant residential work)
- Equipment documentation: Model numbers, serial numbers, and installation specs for installed equipment
This documentation serves three purposes: immediate compliance (the job is legally complete), future reference (warranty claims, property disclosure), and liability protection (if a problem arises years later, you have records showing the work was done correctly and inspected).
Maintaining this documentation in a job record that's linked to the property record in the CRM creates a permanent, searchable archive. When a building inspector or insurance company requests permit records for a 3-year-old water heater installation, the answer is retrievable in seconds.
Integrating Permit Tracking with Project Billing
For commercial work, permit milestones are often contractually linked to billing milestones. A contract that requires plumbing rough-in sign-off before the second payment draw means the permit inspection triggers the billing action.
Software that connects permit status to billing workflows automates this connection: when the rough-in inspection passes, the system flags the billing milestone as available and generates the progress billing document. Without this integration, billing milestones are tracked separately from permit milestones, and the two get out of sync in ways that delay payment.
For residential work, the same logic applies more informally: a job that can't be invoiced as complete until the final permit is filed should not be invoiced until the permit is filed. Job status tracking that includes permit completion as a required step for "job complete" status prevents premature billing and the customer disputes that follow.
For the broader software context including how permit tracking fits within a full plumbing management platform, see the plumbing software guide. If you're managing commercial projects with multiple permit phases, the commercial plumbing software guide covers that level of complexity.
FAQ
Do software tools file permits directly with building departments, or just track them? Most plumbing field service software tracks permit status and documentation rather than filing directly with building departments. Some markets have digital permit portals that allow electronic application and status tracking, and better software integrates with these systems where available. For most jurisdictions, permit filing is still a manual step that the software tracks and prompts but doesn't execute.
What happens to permit records when we switch software systems? Permit records should be exportable as part of your job and property records in standard formats (CSV, PDF). Before switching software, confirm that permit history is included in data export. Historical permit documentation is worth retaining permanently — it has liability protection value long after the job is complete.
How do we handle jobs in states where permit requirements recently changed? Jurisdiction-specific permit rules in software need to be updated when requirements change. Most software vendors provide regular updates to built-in permit requirement databases. For locally specific changes, you can typically configure custom permit rules within the system. Assign one person to monitor local code changes and update the system accordingly.
Eliminate Permit Chaos Before It Creates Liability
A missed permit or failed inspection doesn't just delay a job — it creates real liability exposure. See how Exoserva handles permit tracking for plumbing companies or view pricing options.