Every WOF inspection is conducted against a moving target: the Vehicle Inspection Requirements Manual is amended as vehicle technology and safety requirements evolve, and an inspector's job is to inspect to the manual as it stands today — not as it stood when they qualified.
That gap between "the manual changed" and "every inspector on the floor knows it changed" is where a quiet but serious compliance risk lives.
How amendments actually fail to land
No site ignores VIRM amendments on purpose. The failure mode is mundane:
- The amendment lands centrally — someone in the office knows.
- It gets mentioned at a toolbox meeting that two inspectors missed.
- A printout goes on the noticeboard, where it ages into wallpaper.
- Six months later, an inspector makes a call based on the superseded requirement — genuinely believing they're right.
The site didn't lack diligence; it lacked a mechanism. Knowledge transfer by proximity works in a three-person workshop and fails everywhere else. The fix is a deliberate monitoring routine — how to keep up with VIRM amendments lays one out.
The standard worth holding yourself to
For each amendment that affects your site's inspections, you want to be able to show four things:
- Detection — the amendment was identified when it was published.
- Distribution — it reached every affected inspector, individually.
- Acknowledgement — each inspector confirmed they read it, with a record of when.
- Understanding — for material changes, something that tests comprehension rather than just receipt, feeding the inspector's training record.
That last step is what separates "we told them" from "they know" — and it's the difference between asserting inspector currency at a review and demonstrating it. Turning a VIRM amendment into site practice walks through that four-step routine.
November 2026: ADAS warning-lamp checks
The next significant change on the horizon is the introduction of checks relating to advanced driver assistance system warning lamps, entering WOF and CoF A requirements from 1 November 2026. NZTA's scope is defined by function rather than by product name: any ADAS that fully or partially assists with the steering or movement of the vehicle. It is an indicator check, not a functional test of the system.
It's a meaningful change for inspection practice: ADAS-equipped vehicles are now a substantial share of the in-service fleet, and inspectors who qualified before these systems existed will be making calls on them. Sites that treat this as a briefing-and-evidence exercise — not just an email — will walk into their next review in a much stronger position. Plan three things now: who is affected, how they'll be briefed, and what record will prove it. The full amendment — including the new inspection-frequency table — is covered in the November 2026 WOF inspection changes, and the frequency rules themselves in how WOF inspection frequency works.
Not every change arrives as an amendment
The VIRM is the main channel, but it isn't the only one. NZTA also changes the framework around inspections — most recently by confirming that digital check sheets will connect directly to its systems through approved digital check sheet providers, with a published list of who those providers are. That announcement arrived in an industry newsletter rather than an amendment page, which is exactly why a monitoring routine has to cover NZTA's communications and not just the manual.
Making currency continuous
Inspector currency of technical knowledge isn't a one-off qualification — it's a maintained state, and like every maintained state in a QMS, it needs a system rather than good intentions. That's the thinking behind WoFMate's VIRM alerts and inspector quizzing module: amendments flagged to every affected inspector, read attestation recorded, comprehension quizzed on the Complete tier, results feeding the training record automatically.
The distinction that does the work there is between circulating an amendment and evidencing that someone took it in — which is a different record, kept in a different place, and the one a reviewer asks for. That's covered in read and understood: evidencing inspector comprehension of a VIRM amendment.
Until your site has a mechanism — software or otherwise — the noticeboard is carrying a compliance load it was never designed for.