How to get HVAC jobs install-ready without chasing
Once a job is sold, six things have to land before the crew shows up. Deposit, permit, equipment, PO, financing, an open slot. We connect the systems that already track each one so they move together instead of you calling around.
Answered in short
4 things that decide this
- 01An HVAC job is install-ready when six things clear: the deposit is collected, the permit is pulled, the equipment is ordered and confirmed, the purchase order matches what was sold, financing is approved, and a crew slot exists for the promised date.
- 02Today those six live in different places: the FSM, a supplier portal, the permitting office's site, a financing partner's dashboard and someone's inbox. A coordinator or the comfort advisor chases most of them by phone and email.
- 03We connect the systems already involved so a watched checklist tracks all six against the sold job, instead of a person re-checking each one on a schedule.
- 04The mechanism writes status changes back into ServiceTitan, Housecall Pro, Jobber or whatever you run, so install-ready is a status you can see on the job, not a guess a coordinator makes on a Friday.
Sold isn't install-ready. Here's the gap between them
Your comfort advisor closes the sale and marks the job sold in ServiceTitan or Housecall Pro. Then they move to the next estimate. What happens next, before the crew's van reaches the driveway, is where an install coordinator's week actually goes. It rarely shows up on a dashboard until a date slips.
Your office collects the deposit, sometimes same day, sometimes after two follow-up calls. Someone who knows the local jurisdiction's portal pulls the permit. That can take a same-day online submission or a multi-week paper process, depending on the county. Equipment gets ordered against the distributor's stock, and someone has to catch it if the model gets substituted or the ship date moves. The purchase order has to match what your customer actually bought, including the accessory a tech quietly added on the walkthrough. If they financed the job, you need a funding confirmation before you can schedule with any confidence. And a crew slot has to exist for a technician certified on that equipment. That's a scheduling constraint, not an open calendar square.
Right now, you probably have one person holding all six of those threads in their head, or in a spreadsheet next to the FSM. That's the chasing, and it won't scale past a handful of jobs a week before something slips.
- 01Deposit and financing status: usually the office, checking the FSM and the financing partner's portal separately.
- 02Permit status: whoever knows the jurisdiction, checking a government portal that has no API most of the time.
- 03Equipment and PO accuracy: the install coordinator, cross-checking the distributor portal against what was actually sold.
- 04Crew slot with the right certification: the dispatcher or scheduler, working from the same board as every other job type.
One watched checklist instead of six separate follow-ups
You don't need a new system for your team to log into. What you need is a checklist attached to the sold job, watching what you already run. That means your FSM for deposit and job status, plus the distributor portal for order and shipping status. It also means the financing partner's API or portal for funding confirmation, and the permitting site for approval status wherever the jurisdiction supports it.
When a status changes anywhere on that list, the checklist updates and the job's install-ready flag moves with it. Clear all six items, and the job becomes eligible for scheduling on its own. Your dispatcher can then offer a real slot instead of a tentative one. Say the equipment ships with the wrong accessory kit. You get a flag against that job specifically, not a discovery three days before the install.
Not every jurisdiction or distributor exposes a clean feed. Where a portal has no API, that step becomes a tracked manual task with a due date and a reminder. Even that beats a step nobody is tracking at all.
- Deposit confirmedWritten back automatically from the FSM's own payment record
- PO matches the saleCross-checked against the distributor order; mismatches flagged, not silently accepted
- Permit and financing statusPulled where the portal allows it; tracked as a manual step where it doesn't
- A back-ordered unit or a slipped dateA person calls the supplier and decides whether to substitute or wait
- Moving the install date with the customerThat conversation stays with your team, every time
The checklist tracks status and flags exceptions. It doesn't call a distributor or negotiate a new date with a homeowner, and it's not supposed to.
Some of the systems we have shipped
Related questions
01Does this replace ServiceTitan, Housecall Pro, Jobber or whatever we run?+
No. Whatever FSM you run stays the system of record for the job. The checklist reads from it and writes status updates back into it, so your team keeps working from the board they already know.
02What if the permitting office has no online portal?+
Plenty don't. Where there's nothing to connect to, that step becomes a tracked manual task with a due date and a reminder, so it's still visible on the checklist instead of living only in someone's memory.
03Who decides when a job is actually install-ready?+
The checklist reports status; your coordinator still confirms it. The value is that they're confirming against a live list of six checked items instead of reconstructing the status from six separate logins.
04Does this work if we use a custom-built system instead of a named FSM?+
Yes, as long as it exposes a way to read and write job status, whether that's an API, a database connection or a scheduled export. We confirm the specifics during the audit rather than assuming a standard integration path.
05How long does it take to see the checklist working on real jobs?+
Timing hinges on how many of your systems expose a clean feed versus a manual step. An audit of your current stack answers that question before any build starts.
