An amendment lands. Someone at the site reads it. The work changes at the bench. And then — at most sites — nothing is written down. That last gap is where an otherwise diligent IO turns a strength into an audit finding.
This article is about the step after you've found an amendment: turning it into practice that holds up under review. (For how amendments reach you in the first place, see how to keep up with VIRM amendments.)
The obligation behind it
The VIRM is explicit that vehicle inspectors and inspecting organisations must know their responsibilities, and must read and understand them. NZTA can monitor and review how an IO and its inspectors comply. So "we keep up with amendments" isn't a nice-to-have — it's part of what your authority to inspect rests on. The question an auditor asks is simply: show me that you do. (For how amendments work and why they slip through, see understanding VIRM amendments.)
From amendment to practice, in four steps
A repeatable routine turns a published change into evidenced practice:
- See it. The amendment reaches a named person responsible for reviewing it — not "whoever happens to notice."
- Understand it. Work out what actually changes at the bench: a new check, a changed limit, a different pass/fail call. ADAS guidance ahead of November 2026 is a live example.
- Brief it. Make sure every affected inspector knows before they next apply it. A short, dated team briefing is enough.
- Log it. Record that the review and briefing happened — who, what, and when — in your training record.
Steps one to three happen at most sites already. Step four is the one that routinely doesn't.
The unlogged read: a near-universal miss
Here's the pattern I see again and again. Inspectors do read amendments. They do discuss VIRM changes over a coffee. They genuinely keep current. But none of it is recorded as training — so when an auditor asks for evidence of continuing competence, there's a real activity and no record of it.
This is one of the most common and most avoidable findings, because the work is already being done. The fix isn't more effort; it's capturing the effort that's already happening. And the net is wider than people assume: reading and discussing an amendment counts, working through new technical guidance counts, and even relevant industry video content can count as loggable training — provided it's recorded.
Make the logging automatic, not a chore
The reason the log doesn't get kept is friction: it's a separate step, usually a paper register, done after the fact if at all. Remove the friction and the record keeps itself. The most reliable pattern is to capture the training at the moment the amendment is read — an attestation, or a short read-and-confirm, that writes the date, the person and the amendment straight into the record. That's precisely the model the VIRM alerts module is built around, and it feeds the broader register discipline described in the QMS registers every IO must keep and held together in the QMS Compliance Centre.
The principle is the same one that runs through every well-run site: the work and the evidence of the work should be the same action, not two.