The install went clean. New rooftop unit set, the old one craned off, the system charged and running, and the customer signed the ticket before your crew pulled out of the lot. You sent the invoice that afternoon and moved on to the next call.
Three weeks later the payment still hasn't landed. You call the property manager, and they tell you accounting won't release the final check until the city has signed off on the work. Then comes the part that stings: nobody pulled a permit, so there's no inspection to sign off on.
Now you're back on a job you thought was done. Someone has to apply for the permit after the fact, line up an inspector, and hope the install passes a review it was never staged for. Your last invoice sits in limbo the whole time, and the customer starts wondering why a finished job still isn't finished.
Why the permit is the thing nobody tracks
On a straight repair, you rarely need one. On a replacement, a new system, or a tenant build-out, you usually do, and that's exactly where it gets forgotten. The permit and the final inspection live at the two far ends of the job, nowhere near the actual wrench work your crew remembers.
Quote time feels too early to worry about paperwork. The inspection comes after the truck's gone and everyone's mentally closed the ticket. So the one step that unlocks your money is the one step with no natural reminder attached to it.
There's a Houston wrinkle on top of that. Your service area probably crosses a half dozen permitting authorities, and they don't all play by the same rules. The City of Houston, unincorporated Harris County, Pasadena, Sugar Land, each has its own line on what needs a permit and who's allowed to pull it. A job off the Loop and a job out past the county line can need completely different paperwork for the same box on the same kind of roof.
Decide at quote time, not on the roof
The best moment to flag a permit is while you're still writing the quote, when you have the scope in front of you and nobody's standing on a ladder waiting. Add one question to your quote process and answer it every time.
- Is this a replacement or new equipment, or just a repair?
- Which jurisdiction is the address in?
- Does the scope cross a threshold that triggers a permit (tonnage, a gas line, new electrical)?
- Is it a tenant space where the landlord requires sign-off before they'll pay?
Put a plain permit: yes / no flag on every quote that goes out. If it's a yes, the job doesn't get scheduled until someone owns pulling it. That one habit catches the problem a month before it would've cost you anything.
The tracker that closes the job
You don't need software for this. A shared spreadsheet or a few fields in your field app will do, as long as every permit job lands in one place where you can see it at a glance.
Track these columns, and nothing you don't need:
- Job, address, jurisdiction
- Permit required? yes or no, decided at quote
- Permit number, who pulled it, date
- Inspection booked for what date
- Result: passed, failed, or correction needed
- Customer notified? and when
This is where a little automation earns its keep. You can set up a simple tool that reads new quotes or work orders, spots the ones that look like replacements or tenant jobs from the scope wording, and nudges whoever owns the permit column so nothing sits unflagged. It can also watch the inspection date and remind you the morning it's due.
Be honest about what that tool can and can't do, though. It can flag, remind, and draft, and it's good at not letting a job fall off the board. It can't pull the permit, read an inspector's correction notes, or know every local rule for you. A person still files the application and handles the back-and-forth with the city, and you never want the software quietly deciding a job doesn't need a permit. Treat it as the thing that remembers, not the thing that judges.
Text the customer the minute it passes
Here's the step that actually frees your money. The moment the inspection passes, the final invoice should go out that same day, with proof the city signed off.
Set up two short texts and let them fire automatically. One when the inspection's booked, so the customer knows it's handled and expects the inspector. One the instant it passes, with the final invoice right behind it.
Something as plain as this does the job: "Good news, the city signed off on your install at 400 Commerce today. Final invoice is on its way, and we've attached the inspection record for your file." That record is often the exact document AP was waiting on. When you hand it to them before they ask, the last check stops being a chase and starts being a formality.
Worth doing this week
You can stand this up in an afternoon and feel it on the next replacement that goes out.
- List every jurisdiction you work in, and jot down what triggers a permit in each. Keep it where the person writing quotes can see it.
- Add a permit: yes / no field to your quote template so the call gets made up front.
- Start the tracker with your open installs, the ones already in the ground waiting on sign-off.
- Write the two customer texts once, the "inspection booked" and the "inspection passed," so they're ready to fire.
- Name one person who owns the permit column. A tracker with no owner is just a list nobody reads.
If you'd rather not build the flags and reminders yourself, that's the kind of small, boring automation we set up for Houston shops at AI Agency Houston, the stuff that quietly keeps a finished job from turning back into an open one.