In this post
# HVAC Technician Scheduling Checklist
Schedules do not usually fail on the big decisions. They fail because nobody checked whether the technician holding Tuesday at ten can actually commission a heat pump, or because four jobs went into a day with no travel allowance, or because a cancellation left a hole nobody filled.
This is the checklist that catches those. Work it in order: taking the call → booking → building the day → dispatching → during the day → closing out → weekly review.
1 · Taking the call
- Customer name, phone and service address confirmed — including whether billing differs
- Problem recorded in the customer's own words, not paraphrased into a job type
- Is there any heat or cooling at all?
- Anyone elderly, very young or unwell in the property?
- Anything being damaged right now — water, gas smell?
- Priority assigned: emergency, high, normal or low
- Equipment identified if known — make, model, age
- Existing customer checked for service history at that address
- Access constraints captured: gate codes, dogs, parking, who must be home
- Commercial sites: site contact, access hours, roof or plant-room key
- Customer's own timing constraints recorded
- Whether they are a maintenance-plan customer
2 · Booking the appointment
- Job type selected, with a realistic duration for that type — not a default two hours
- Appointment window agreed and stated plainly to the customer
- Window is one you can actually hold, not one that sounded good on the phone
- Required skill identified from the job type
- At least one technician on that day holds the skill
- Travel allowance included, not assumed away
- Job placed geographically with the rest of that technician's day
- Capacity checked before committing, not after
- Confirmation sent — date, window, and what happens on arrival
- Deposit or payment terms stated if the job type needs them
3 · Building the day
- Fixed commitments placed first — installs, commercial access windows
- Recurring maintenance placed next, clustered by area
- Repair and diagnostic work fitted around those, by area
- Deliberate slack left in — not filled because it looked empty
- Each technician's day sits in one part of the map where possible
- Stop order sequenced by proximity, not by booking order
- Drive time between consecutive stops sanity-checked
- Skill coverage confirmed across the whole day, not just per job
- Apprentices paired rather than sent solo
- Install crews kept whole
- Parts availability confirmed for anything known in advance
- First appointment of the day is not the furthest one
4 · Dispatching
- Technician assigned by skill first, then availability, distance and workload
- Assignment recorded — who decided, and when
- Conflict check run: does this overlap something they already hold?
- Technician has the address, access notes and problem description before setting off
- Equipment and service history available to them on site
- Customer notified that a technician is assigned
- En-route notification sent when they actually set off
- Emergency jobs: cost of pulling the technician considered, not just distance
- Displaced customers called — by voice — and offered a specific alternative
5 · During the day
- Every job has a current status, not "scheduled" all day
- Arrival recorded
- Running late identified before the customer notices
- Customer told about a delay proactively
- Any customer reply to an automated message reaches a person immediately
- Overruns reflected in the rest of that technician's day
- Cancellations backfilled from a standby list, or the gap deliberately accepted
- New emergencies triaged against the same framework, not by who shouts loudest
- Parts runs logged rather than absorbed invisibly
6 · Closing each job
- Arrival and completion times recorded
- Diagnosis written as a separate field from work performed
- Work performed described in terms a customer can follow
- Parts listed with quantity and price
- Labour hours and rate recorded
- Recommended work that was declined written down, with the date
- Photos taken where they will matter later — nameplate, before, after
- Customer approval captured in a retrievable form
- Work order closed, not left open overnight
- Completion notification sent
- Invoice raised or queued
- Follow-up scheduled if work was recommended
7 · Weekly review
- Estimated against actual duration, by job type — are the defaults honest?
- Technicians consistently running over: is that them, or the estimate?
- Average trips and minutes between jobs
- Cancellation rate, with reasons recorded
- Jobs that needed a second visit, and why
- Emergencies: how many, and what each one displaced
- Skills held by exactly one person — a single point of failure
- Next week built before Friday ends
The eight that cost the most when missed
| # | Missed check | What it costs |
|---|---|---|
| 1 | Skill not verified at booking | A wasted visit and a second truck roll |
| 2 | No travel allowance in the schedule | Every job after the second runs late |
| 3 | Day booked to capacity | The next emergency displaces a paying customer |
| 4 | Stops in booking order, not proximity order | Miles and hours, every day, on every route |
| 5 | Access notes not captured | A technician at a locked gate |
| 6 | Diagnosis and work performed collapsed into one line | Disputes, and no history for the next visit |
| 7 | Declined recommendations not recorded | Lost follow-up revenue, and exposure if it fails |
| 8 | Cancellation reasons not recorded | You cannot tell a scheduling problem from a sales problem |
From checklist to system
A printed checklist works, and if you take one thing from this page, print it.
But it still depends on someone working it at half past five after a full day. The version that does not depend on discipline is the same list built into the software: durations that default by job type, skill checks that run at booking, travel allowance built into the blocks, assignment that shows its reasoning, statuses that cannot sit at "scheduled" all day, and work orders that will not close without a diagnosis and a signature.
That is the difference between a dispatcher who is good at this and a company that is.
See it working → A full day for a fictional contractor — dispatch board, calendar, assignment recommendations, work orders and customer notifications. No signup.
Size the problem on your own numbers first:
Related
- HVAC Dispatch Software →
- HVAC Scheduling Software →
- How to Schedule HVAC Technicians Efficiently →
- HVAC Work Order →
Want these checks built into the way your office actually books and dispatches? Talk to BDEVY →
hvac scheduling checklist hvac dispatch checklist hvac job management software