What callbacks are really costing you

The job is closed. The invoice is paid. The customer rings because something is not right, and you send somebody back.

That visit costs you a tech's day, fuel, a part, and a slot another customer would have paid for. In almost every set of contractor books we open, it costs exactly nothing — because it was never recorded against anything.

Why callbacks are invisible

The original job is already closed and invoiced. There is no open job to charge the time to.

So the hours go into general payroll, the part goes into materials, the fuel goes into vehicle costs, and all of it lands in overhead. The job that caused it still shows the margin it showed on the day it closed.

Which means two things are quietly true:

Every job looks better than it was. Your job costing is systematically optimistic by however much rework you do.

You cannot see the pattern. Callbacks are not evenly distributed. They cluster around particular crews, particular job types, particular products or particular customers. None of that is visible if the cost has been smeared across overhead.

What a callback actually costs

More than the visit. Worth counting properly:

The tech's loaded hours, including drive time. Not the base wage — the loaded cost, as with any job costing.

Parts and material, at cost.

Vehicle cost for the trip.

The opportunity cost. This is the big one and it is usually left out. That slot could have carried a billable call. On a busy day, the callback does not just cost what it consumes — it displaces revenue.

Administrative time. Someone took the call, rescheduled, and dealt with an unhappy customer.

How to track it without new software

You do not need a system. You need somewhere for the cost to land.

Open a warranty or callback job, linked to the original. The hours and parts go there, and it rolls up to the original job's true margin.

Record a reason code. Even four options is enough: our workmanship, a material or equipment failure, something the customer did, or something outside anybody's control. The point is not precision — it is being able to sort by it later.

Report it monthly. Callback hours as a share of total field hours, and callback cost by reason. Two numbers.

What the numbers tell you

Once you can see it, the picture is usually specific rather than general.

A crew or a tech. Not necessarily a competence problem — often a training gap, or someone consistently given work slightly beyond their experience.

A job type. One kind of install generating disproportionate return visits usually points at a process or a scoping problem rather than the people.

A product or supplier. If failures cluster around one manufacturer, that is a purchasing decision, and it may also be a warranty claim you are not making.

A customer. Occasionally the calls are not defects at all. That is a conversation about scope, and it is much easier to have with a list of dates in front of you.

What good looks like

A callback rate that is measured, watched, and trending down. Not zero — zero would mean you were refusing to stand behind your work.

The contractors who get this under control are rarely the ones who tried hardest to reduce it. They are the ones who could see where it was coming from, because somebody was recording it.

Related

• Job costing for contractors
• Why jobs that look profitable still lose you money
• The eight numbers a contractor should look at every month