ZeroDelay Academy · Follow-up and handoff worksheet
HVAC callback review: reasons and incremental revisit cost
A callback uses technician time, parts and a truck roll that the original job did not plan for. Before deciding whether callbacks are a training, parts, scheduling or communication problem, record why each return visit happened and what it added in cost beyond the original job.
By ZeroDelay.ai · An educational framework, not a customer case study
A question to start with
Why are customers needing a second visit, and what does each revisit add in cost that was not already counted on the original job?
Step 1
Define what counts as a callback
Write one rule and apply it to every job: for example, a return visit to the same equipment within a fixed number of days for the same complaint. Keep planned follow-up visits, new unrelated problems and maintenance agreement visits outside the callback count so the review is not inflated.
Step 2
Record one reason per revisit
Use a short, fixed reason list such as incomplete diagnosis, part failure, part not on truck, installation or adjustment issue, customer usage question, or unclear. Pick the reason from the technician notes and customer description; if the notes do not support a reason, mark it unclear rather than guessing.
Step 3
Cost only the incremental revisit
Add the loaded labor hours of the revisit, parts used on the revisit and any travel cost that would not have happened without it. Do not add the original visit labor again, and do not count revenue you imagine was lost; that is not a cost the business actually incurred.
Records to gather first
- Completed work orders for the review period, including the original visit and any revisit on the same equipment.
- Technician time stamps for the revisit (arrival, departure and travel if paid).
- Parts issued on the revisit, at your actual cost.
- Your loaded hourly labor cost, defined the same way you use it elsewhere.
- Technician and dispatcher notes describing the customer complaint on the return visit.
Copy or print this blank worksheet
Copy the table into your own document or use your browser's Print command, then fill it in there or on paper. There are no entry fields here, nothing is saved, and numbers you write do not transfer into the diagnostic.
| Job / reference | Original visit date | Revisit date | Callback reason | Revisit hours | Revisit parts $ | Extra travel $ | Incremental cost $ |
|---|---|---|---|---|---|---|---|
| Revisit 1 | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| Revisit 2 | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| Revisit 3 | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| Revisit 4 | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| Revisit 5 | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
| Total | ______ | ______ | ______ | ______ | ______ | ______ | ______ |
Fictional worked example
All figures are made-up assumptions to show the arithmetic. They are not industry benchmarks, customer data, achieved outcomes or a forecast for your business.
Assumptions
- Fictional single revisit to adjust a system after an installation. The original job is already invoiced and its labor is already recorded on that job.
- The revisit took 3 technician hours at an assumed loaded labor cost of $42 per hour.
- A replacement part on the revisit cost $26. The extra truck roll added an estimated $18 of incremental travel cost.
- The reason recorded from the notes is an installation adjustment issue.
Simple math
- Revisit labor: 3 hours × $42 = $126.
- Incremental revisit cost: $126 labor + $26 parts + $18 travel = $170.
- Not included: the original visit labor (already counted on the original job) and any revenue you think the technician might have earned elsewhere in those 3 hours. Neither is an incurred cost of this revisit.
What this suggests checking: One $170 revisit says little on its own. Group several weeks of revisits by reason: if most share one reason, that reason is the place to look first, whether it points to checklists, parts stocking or customer instructions.
Review the filled worksheet: affected jobs versus revisit count
Once revisits are logged, report two different numbers. In this fictional review, follow each of the 60 completed original jobs for the same defined follow-up window before counting its callbacks. Do not mix original jobs from one cohort with unrelated returns from another. One job can need more than one return visit, so affected jobs and revisit counts answer different questions.
Separate fictional scenario for teaching only. It does not change the worked example above and is not a benchmark, customer result or forecast.
| Measure | Fictional count | How it is counted | Rate |
|---|---|---|---|
| Completed original jobs | 60 | Each original job once, inside the review period | Base |
| Original jobs with at least one callback | 4 | Unique job references, not visits | 4 ÷ 60 = 6.7% of jobs affected |
| Callback revisits | 6 | Every return visit under your callback rule | 6 ÷ 60 × 100 = 10 revisits per 100 original jobs |
| Jobs with repeat revisits | 2 | Two of the four affected jobs needed a second return | Not a rate; check these first |
Check the arithmetic
- Affected share: 4 ÷ 60 = 0.0667, shown as 6.7%. Revisit rate: 6 ÷ 60 × 100 = 10 per 100 original jobs.
- Cost only the 6 revisits with the incremental method above. Original labor on all 60 jobs stays on those jobs and is never added a second time.
- Neither 6.7% nor 10 per 100 is a benchmark; they only describe this fictional period.
Investigate when
- Jobs with repeated returns: inspect the notes for an unresolved issue, missing information or a different problem rather than assuming a cause.
- Recurring recorded reasons across jobs; there is no universal percentage that proves a training, parts or pricing problem.
- Revisits marked unclear, since the notes do not yet support a reason.
Next actions
- Name one owner per leading reason and a dated check, such as reviewing the install checklist or truck stock list.
- Re-run the same counts next period with the same callback rule before judging whether anything changed.
If revisits are consuming technician hours, compare booked and completed HVAC work.
What this cannot tell you
- A reason code reflects what the notes say, not a confirmed root cause.
- Incremental cost is not the same as lost profit, and this review does not estimate customer satisfaction or future sales.
- These fictional figures are not HVAC benchmarks or a typical callback cost.
- For capacity questions about booked versus completed work, use the separate HVAC capacity guide rather than this review.
Choose a next step from your worksheet
After recording callback time and incremental costs, check how many usable technician hours remain for completed work before seeking more bookings. Compare HVAC bookings with completed work.
For a separate, no-signup calculation, open the free Profit Leak Check. Choose HVAC to compare bookings, completions and workable hours; it does not identify callback causes or calculate this worksheet's incremental revisit cost. Calculations stay in your browser.
If this worksheet raises a wider business question, the diagnostic below uses the answers you provide about your business; it does not import this worksheet or calculate its results. View the fictional sample 90-Day Plan to see an illustrative complete paid report, not your free results or a promised outcome. Available market research varies.