Permit Management Integrations for HVAC Teams

If you run an HVAC company and you’re asking which permit management integration is right for your team, the answer starts with a simpler question: does it live inside the software your office already opens every morning, or does it make someone open a second tool?

For HVAC and plumbing contractors running ServiceTitan, iPermit Pro is built natively on that platform. Your dispatcher books the job in ServiceTitan. The permit request fires from the same record. The permit number writes back to the same job without anyone re-keying anything. That’s what native means — and it’s the single biggest operational difference between a permit integration that actually saves time and one that just moves the paperwork somewhere else.

This guide covers how permit integrations work, where they move the needle for HVAC teams, and what to verify before you commit to a vendor.

Why the integration matters more than the permit service

An HVAC operation moves fast. Dispatchers book jobs, technicians move between calls, and the office manager is fielding calls, scheduling inspections, and trying to keep the job board clean. Permits are not the hard part of that job — they’re the friction that slows down everything else.

That friction compounds when the permit workflow lives outside your FSM. Every permit that needs to be submitted requires someone to leave ServiceTitan, open a portal, retype the address, license number, and scope of work that ServiceTitan already has, then check back later to see if it’s been submitted. That double entry is where delays accumulate — not at the building department, inside your own office.

The integration fixes the internal delay. The rest of the turnaround depends on the building department, which no vendor controls.

ServiceTitan-native: what it actually does

“Native integration” gets used loosely. Here’s what it means with iPermit Pro specifically:

1. You stay on your dispatch board. The permit request is initiated from inside the ServiceTitan job record — no separate login, no tab-switching.
2. The job data pre-populates. Customer name, address, scope of work, license information — whatever ServiceTitan already knows, the permit request already knows. Nothing gets retyped.
3. Status writes back to the job. Submitted, issued, in review, ready for inspection — your dispatchers see where the permit stands without leaving ServiceTitan.
4. The office manager’s job shrinks. Their workflow goes from “did I submit the permit?” to “did the permit issue?” That’s a smaller question, and it’s one they can answer from the same screen they were already on.

Bolt-on tools that describe themselves as working “with” ServiceTitan are usually something else: a CSV importer, a Zapier-style connector, or a separate portal with a button that links back. All of them reintroduce double entry. None of them eliminate the tab-switching problem.

Three delays — and which ones you can actually fix

HVAC operators usually frame permit timing as one problem. It’s three:

Submission lag — the gap between a job being booked and the permit application landing at the AHJ. This is internal. It’s yours to fix. It’s where most of the avoidable delay lives.

AHJ review lag — the city’s clock. From the moment the application is in, to the moment they issue. No vendor controls this. Some jurisdictions issue same-day; some sit on a stack for ten business days. Anyone who guarantees approval speed across jurisdictions doesn’t understand how AHJs work.

Inspection-close lag — the gap between work completion and the permit closing. Permits left open can come back to haunt you. They surface during home sales, refinances, and CSLB audits years after the job closed. An open permit on a closed job is a slow-burning liability.

A permit integration moves the needle on the first delay and the third. It can’t touch the second. The question to ask any vendor is how they handle #1 and #3 specifically.

The 24-hour submission commitment

iPermit publishes this number because we measure it: 100% of our permits submitted within 24 hours.

That’s not a figure for issued permits — that’s when the application hits the AHJ. From the moment a job is in our queue, the application is at the building department before the next business day rolls over.

It holds because three things are true operationally:

• The job triggers the work immediately. There’s no batch processing, no end-of-day sweep.
• Every AHJ has a known local procedure on file. We’re not learning how a jurisdiction formats its cover sheet on a Tuesday afternoon — we already know.
• Staffing is built for the SLA, not for an average.

For an HVAC company running a high volume of change-outs, the difference between submitted same-day and submitted when someone gets to it is measured in days of unbillable truck time per job.

Over 50 years and more than 1,000,000 permits, that’s not a promise we made recently.

Closing the back end — final inspections

The second place a permit integration earns its keep is the close-out.

Final inspection scheduling is available as a paid add-on: the job comes in, the permit pulls, the install happens, the inspection gets scheduled, and the permit closes. Start to finish — no dangling files, no open permits sitting in a spreadsheet with a “we’ll get to it” note.

If you’re in California, HERS testing (Title 24 / CF-3R compliance) is part of the same picture. We’ve completed more than 250,000 HERS tests. For California HVAC contractors, the ability to pull the permit, run the HERS test, and close the inspection through one vendor is the reason permit management stops being a coordination problem. For contractors outside California, the relevant close-out piece is the final inspection — same principle, different form.

The liability case here is direct. Permits left open are a future-you problem. They surface at exactly the wrong times — when a homeowner is selling, when an auditor is looking, when you’re pulling a permit at the same address and the city flags an unresolved one. The integration that handles close-out is not a premium add-on; it’s the part that determines whether the job actually closes.

Multi-state coverage

If your operation is California-only, a permit clerk with strong local AHJ relationships can cover you. Two or three counties of muscle memory is manageable.

Once you cross a state line — or even cross from one county to an adjacent one — that muscle memory expires. Every AHJ has its own portal, its own required forms, its own quirks about license number formatting.

For HVAC companies scaling past a single market, the choice is between a patchwork (one clerk per market, each learning the AHJ from scratch) and a national vendor (one workflow, one SLA, every AHJ already on file).

We’re nationwide. Fifty years of pulling permits across jurisdictions means the legwork is done. You don’t pay for a vendor to figure out a new AHJ on your first job there.

Five questions to ask before you sign with a permit vendor

Whether you’re talking to iPermit or evaluating anyone else, these are the questions that determine whether the integration delivers:

1. Is it native or is it middleware? Does the permit get requested from inside the FSM job record, or do I open a second tool? If the demo involves a Zapier walkthrough, it’s middleware.

2. What’s the submission SLA, and how is it measured? “Fast” isn’t a number. “100% within 24 hours” is a number. Ask what they measure and how they track it.

3. Does the status write back to the job automatically? Or does someone retype the permit number into the FSM? Bidirectional data flow is the whole point of native integration.

4. Does the service include final inspection scheduling, and at what price? If the answer is no, you’ve solved half the problem. Open permits are the liability, not pulled permits.

5. Who handles the back-and-forth with the building department when something gets kicked back? If the answer is “you do,” that’s a software subscription, not a permit service. The honest answer should be a named point of contact on the vendor’s staff.

If a vendor can’t answer all five clearly, the integration probably isn’t what they’re marketing. They’re selling software that lives next to your FSM, not inside it.

Where iPermit fits

We’ve pulled more than 1,000,000 permits over 50 years in this work. The HVAC and plumbing contractors we work with run anywhere from 10 to 100+ technicians. The shops where the ServiceTitan integration moves the needle fastest are the ones where the office manager is handling permit submissions on top of everything else and the first permit that slips past deadline costs more than a month of the service.

If that sounds like your operation, the question isn’t which permit service to pick. It’s when you want to stop running permits as a side job.

Next step

If you want to see how the ServiceTitan integration works inside a live job, book a 20-minute walk-through with our team. We’ll open a real job, fire a real permit request, and show you exactly what your office manager would see on day one. Reach us at 855-737-6484 or ipermitusa.com.