Most WOF sites don't fail audits because their inspectors can't inspect. They pick up findings because the paperwork doesn't prove what the inspectors actually did — and in a regulated system, what you can't evidence didn't happen.
Having sat on the receiving end of NZTA reviews, the pattern is remarkably consistent. The same handful of misses come up again and again, and almost all of them are system problems wearing the costume of people problems.
1. Incomplete or vague checksheet records
The classic. The inspection was done; the record doesn't show it was done properly. Reasons for rejection noted so briefly they can't be reconstructed later, sections left blank because "everyone knows" they were checked, results that don't match the story the rest of the record tells.
The fix is structural, not motivational. A checksheet format that guides the inspector through every section — and won't let a record complete with the required detail missing — removes the failure mode entirely. Handwriting and memory are where this miss breeds. The record-keeping failures that come up most often are catalogued in checksheet record-keeping failures.
2. Recheck process slips
Failed items come back for recheck, and the recheck is where process discipline gets tested: was it within the allowed window, was it limited to what may be rechecked, is the recheck record connected to the original inspection so the chain of evidence is complete?
A loose recheck — a new sheet with no link to the original, or an out-of-window recheck treated as if it were in-window — is one of the easiest findings for a reviewer to spot, because the dates and documents speak for themselves.
Avoid it by never letting rechecks live as orphan documents. If your recheck record is created from the original inspection and carries its history with it, the compliance question answers itself. The recheck-window rules and where sites slip are covered in the 28-day recheck guide.
3. Equipment and calibration lapses
Brake testing equipment and other measuring devices carry calibration requirements, and the register that proves it is exactly the kind of document that quietly goes stale. The equipment works fine — but the record says the calibration expired weeks ago, and now an entirely avoidable finding is on the report.
Calibration is a dates problem, and dates problems are what systems are for: a register with the renewal dates visible, owned by someone, reviewed on a schedule — not a folder checked the week before a review. See equipment and calibration lapses for the register detail.
4. Training that happened — but was never logged
This one deserves special attention because it's so nearly universal. The team does read the VIRM updates. They do discuss them at the toolbox meeting. The technical knowledge is genuinely current. And almost none of it makes it into the training register.
Come review time, the site's true position is "our inspectors are across every change" — but the register says training stopped months ago. The reviewer can only assess what's evidenced, so real diligence scores as a finding anyway. It's the most frustrating non-compliance there is, because the work was done; only the logging wasn't.
Two things make this miss cheaper to fix than most sites realise:
- The bar for what counts is wider than people think. Industry-relevant content — including video content — can be logged in the training record. If an inspector watched a manufacturer's walkthrough of a new ADAS system or a technical briefing on a rule change, that's training; log it.
- The logging itself can be automatic. A system where a VIRM update is pinged to each inspector and logged in the training record the moment they confirm they've read it — or better, a short quiz that proves they understood it — closes the gap between "we read it" and "we can prove we read it" without anyone remembering to fill in a register. (More on logging amendment reads as training in turning a VIRM amendment into site practice.)
5. Operating outside authority or scope
Inspections done by someone whose appointment doesn't cover that vehicle class, or while an authority had lapsed. Nobody intends this — it happens when the site's view of "who can inspect what, right now" lives in someone's head instead of a current register that's checked as part of the job allocation. The detail is in operating outside authority or scope.
6. Document control and the vehicle file
The miscellaneous category that catches everyone: superseded forms still in use, checksheets that can't be located on request, records stored in ways that allow alteration after the fact. Reviewers care about this because record integrity is the foundation the whole system rests on — a record that could have been tidied up after the fact is worth very little as evidence. The usual offenders are listed in document-control slips at WOF sites.
The pattern behind the misses
Read back through the list and one thing stands out: none of these are about inspection skill. They're about whether the site runs on systems or on memory. Paper-and-memory operations generate findings at a steady rate no matter how good the people are, because every record is an act of discipline performed under time pressure, dozens of times a day.
The sites that consistently review well have made the compliant path the easy path: records that complete themselves properly or not at all, rechecks that carry their own history, registers that surface their own expiry dates. That's the design philosophy behind WoFMate's digital checksheets and the QMS Compliance Centre — but whether you use software or a very disciplined whiteboard, the principle is the same: stop asking people to remember, and start making the system do the remembering.