Every repairs report has a first-time-fix percentage on it. It is a useful number and a poor explanation. It tells you that something went well or badly; it never tells you why. The why is in the appointment data underneath, the bookings, reschedules and no-access events that the headline figure flattens into one number.
The KPI is a lagging summary
A first-time-fix rate is computed after the fact, across a period, for a whole service. By the time it moves, the cause is weeks old. Worse, two services with the same rate can be operating completely differently: one books well and occasionally fails on parts, the other reschedules constantly and happens to net out to the same figure.
Read the appointment trail
NEC’s dynamic scheduling records the journey, not just the outcome. The engine calculates travel and expected job time and updates appointments through the day as operatives record travel and work. That trail, if you keep it, shows where time and certainty leak.
- Reschedules by reason, the difference between a parts problem and an access problem.
- No-access by time slot, whether your morning appointments are quietly failing.
- Offered versus accepted, how much real choice residents actually get.
- Travel versus on-site time, whether the round is geography or workload.
Join it back to the cause
Appointment data on its own is operations trivia. Joined back to the works order that triggered it, and the property it happened at, it becomes diagnosis. A no-access cluster on one patch at one time of day is a scheduling decision you can change, not a number to apologise for at the next performance meeting.
First-time-fix tells you how the month went. The appointment trail tells you what to do on Monday.