The recheck is the most procedurally fussy moment in WOF work: a vehicle comes back days after failing, possibly to a different inspector, and the paperwork has to tie the visit back to a previous inspection precisely. It's exactly the kind of process that runs fine on a quiet Tuesday and falls apart in a busy week — which is why it features so regularly in review findings. (For where rechecks sit among the other usual suspects, see the pillar guide: Common audit misses and how to avoid them.)
What the rule actually says
Under the VIRM (In-service certification, section 3-11, with the fee side set by the Land Transport (Certification and Other Fees) Regulations 2014):
- If a vehicle fails a WOF inspection, no fee is payable for a subsequent inspection done within 28 days of the failed inspection, at the same inspecting organisation — any site of that organisation, not necessarily the same one.
- After 28 days, a fee is payable and a new WOF inspection is required. There is no such thing as a day-30 recheck; there is only a fresh inspection.
- If the vehicle passed a performance test but failed on condition, and the repair could affect performance, the performance should be re-tested at the recheck — replaced brake pads put the vehicle back on the brake tester, not just up on the hoist for a visual.
One caution worth repeating to every counter person: the 28 days govern fees and inspection requirements, not the legal operation of the vehicle. A car that failed its WOF doesn't gain 28 days of lawful road use; without a current WOF it may generally only be driven for purposes like repair or obtaining a new WOF.
The four recheck failure modes
The calendar slip. Day 29 treated as day 28. Without a system counting the window per-vehicle, "about four weeks" does the counting — and the dates on the documents contradict the site's story, in a way a reviewer can spot from across the room.
The orphan recheck. A recheck recorded on a fresh sheet with no reference to the original failed inspection. Now nothing proves what was originally failed, what was repaired, or that only eligible items were rechecked. The chain of evidence has a missing link, and the record can't answer the only question it exists for.
The skipped re-test. Condition fail, performance-relevant repair, no re-test recorded. The classic is brake pads: the original sheet shows a brake condition failure, the recheck sheet shows a pass, and no brake test result appears anywhere. The recheck looks like a wave-through even when it wasn't.
The generous recheck. Items inspected and passed at recheck that were never part of the original fail — or worse, a recheck that quietly became a full re-inspection without being recorded (or charged) as one. Scope discipline cuts both ways.
Make the recheck inherit its history
Every one of those failures has the same root: the recheck lived as a separate document, and a human was asked to reconnect it to the original by memory. The fix is to never let the connection be optional. When a recheck record is created from the original failed inspection — as it is with WoFMate's digital checksheets — it arrives knowing its parent: the failed items are pre-loaded, the 28-day window is computed from the original date rather than guessed, performance re-tests are prompted where the failed items call for them, and the completed recheck files alongside the original as one continuous story.
A reviewer reading that record gets every answer without asking. That's the standard: rechecks that carry their own history, so the compliance question answers itself.