Defect reporting: from driver to workshop and back

A defect reporting system has three parts: finding the fault, recording it, and closing it. Operators generally do the first two adequately. The third is where records go thin, and it is the one a maintenance investigation examines most closely.

A reported defect with no closure is worse than an unreported one

An unreported defect is a gap in the check regime. A reported defect with no recorded rectification is documentary evidence that the operator knew and cannot show it acted — which is a materially worse position to be in, and it is created by the system rather than by any individual.

Which is why the closure record matters as much as the report: what was done, by whom, when, and who confirmed the vehicle was fit to return to service.

Nil defect reporting is the part that decays

Where drivers record that they checked and found nothing, that record proves the check happened. Where nil returns stop being submitted, nobody notices — an absence is invisible in a way a report is not, and the regime can quietly stop functioning for a subset of drivers or a depot without any alarm.

Monitoring for missing returns, rather than only reading the ones that arrive, is what catches that.

In practice: the defect that was fixed twice

A driver reports a brake performance concern. It is looked at, nothing found, vehicle returned to service. Three weeks later a different driver reports the same thing on the same vehicle. Two separate records, two separate closures, no link between them.

Recording defects against the vehicle rather than against the shift is what makes the second report read as a pattern rather than as a new event — and in this case the pattern was the finding.

Common mistakes

• –Reports recorded without a matching rectification record
• –Vehicles returned to service with no named person confirming fitness
• –Nil defect returns quietly stopping, which is invisible without monitoring
• –Defects recorded against a shift rather than against the vehicle
• –No link between repeat reports of the same fault
• –Drivers reporting into a book nobody reads the same day

Make reporting easier than not reporting

Where a driver has to find a book in an office, fill in a duplicate pad and hand it to someone who may not be there, the friction does the deciding — and borderline items go unreported. Where reporting takes seconds from the cab, more gets reported, which looks worse on paper and is a far healthier operation.

A rising defect report count after a system change is usually good news being misread. The figure to watch is not how many are reported but how long they take to close and how many recur.

Getting this right

The closure record is what a maintenance investigation examines most closely, and the same data drives off-road tracking and annual test preparation. One record, three uses.

• –Make reporting possible from the cab, in seconds
• –Record who confirmed the vehicle fit to return to service
• –Monitor for missing nil returns as well as reading the reports that arrive
• –Hold defects against the vehicle so repeats are visible as patterns
• –Treat a rise in reports after a change as a sign the system is working

One practical test: count reports before and after

If you change how defects are reported — a phone instead of a book, a form instead of a conversation — count reports for the month before and the month after.

A rise is usually read as a problem and is almost always the opposite: the same defects were occurring and were not being reported because the friction did the deciding. The figures worth watching are not how many are reported but how long they take to close and how many recur on the same vehicle.

• –Make reporting possible from the cab, in seconds
• –Record who confirmed the vehicle fit to return to service
• –Monitor for missing nil returns as well as reading the reports that arrive
• –Hold defects against the vehicle so repeats are visible as patterns
• –Treat a rise in reports after a change as the system working