What does a callback actually cost us if we never invoice it?
The visible cost is nothing and the real cost is capacity. Every callback consumes a slot that could have held revenue work, plus the drive time to get there, plus dispatcher time to squeeze it in. Track callbacks two ways: as a share of completed jobs, and as a share of total board hours. The second number is what explains why the schedule feels tight in a slow month.
Counting callbacks by job count understates them
Callback rate is almost always reported as callbacks divided by completed jobs. That framing makes them look small, because callbacks are usually a modest share of visits.
Measured in hours they are much larger, for two reasons. Callbacks skew toward the harder jobs, which take longer. And they arrive as unplanned inserts, which means they displace routed work and add drive legs that would not otherwise exist. A callback rarely costs one slot; it costs a slot plus the damage done to the rest of that truck's day.
The three buckets to add up
Add these and express the result as a percentage of total available board hours for the period. That is the number to put in front of an owner who is deciding whether to add a truck.
- On-site hours. Straightforward: sum the arrived-to-completed time on jobs classified as callbacks.
- Displacement drive time. Compare the day's actual driving with a re-sequenced version excluding the insert. The difference is real capacity consumed and never appears in any standard report.
- Office handling. The inbound call, the apology, the rescheduling of whatever got bumped, and the follow-up. Small per event, not small in aggregate during a bad month.
The second-order cost nobody tracks
A bumped customer is a customer who now has a worse experience than the one who caused the callback. Track how many appointments were moved to accommodate inserts, and whether those customers later canceled or left reviews. In many shops this chain — callback creates insert, insert bumps a paying job, bumped job cancels — is the real revenue effect, and none of its links are recorded together.
Joining job records to customer outcomes is what makes that chain visible. That is the kind of question customer intelligence is built to answer, because it requires records from several systems in one place.
Use it as a leading indicator, carefully
Callback hours per hundred board hours is a useful trend line. Rising with unchanged job mix suggests a training or parts issue. Rising alongside a hiring wave is usually a ramp effect and should recede. Rising in a specific job type points at a process, not at people.
Set the interpretation rules before you look at the chart, and route the findings into human coaching rather than automatic conclusions. The metric is an input to a conversation, and a weekly operations brief is a reasonable place for it to live.
Topics: callbacks · capacity · utilization · metrics
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.