The first-fix rate is a training number

Callbacks tell you more about learning than any course does

By The Human Union team · 24 Oct 2026 · 4 min read

Most firms treat the first-fix rate as an operations figure. It goes on the dashboard next to jobs per day, and when it dips someone talks about scheduling. It is a training figure. It is the clearest signal you have of what your people know and what they were never taught.

Read the callbacks, not the rate

A rate of eighty-one percent tells you nothing on its own. The nineteen percent that came back tells you everything, if you look at why.

Sort a month of callbacks and the same handful of causes appear. A fault reset rather than found. A part swapped on a hunch. A check skipped because it takes twenty minutes and the slot had ten left. A note that said "no heating" and nothing else, so the next visit started blind. Each of those is a thing someone did not know, did not have time to do, or did not know mattered.

The first is a training gap. The second is a diagnostic habit nobody corrected. The third is a scheduling decision that is quietly teaching people to skip the check. The fourth is a writing-up habit that costs the next person an hour.

Why courses do not move it

Send the team on a manufacturer's course and the rate barely changes, because the course teaches the product and the callbacks are about the job. Nobody comes back from a course knowing to run the system under load for twenty minutes before leaving, or to photograph the data plate so the office orders the right part. Those come from the person next to you, or they do not come at all.

What does move it

Three things, none of them expensive.

  1. Tell people when their job came back. In most firms the first engineer never hears. They cannot learn from a callback they do not know about.
  2. Make the reasoning visible. Pair the newer engineer with the one whose fixes hold, and have the experienced one say what they are checking and why. The skill is in the why.
  3. Write the fix down where the next person will see it. Not the official procedure: the specific thing that fixed this model with this fault, in the words of the person who found it.

Do those for a quarter and watch the rate. It is the cheapest training programme you will run.


If this is on your mind, we would like to hear how your team learns. Thirty minutes with our team, no slides.

See it with your own example

Thirty minutes with our team, using a question from your own work.

Book a demo