The worst way to learn about a VIRM change is from a customer, or from an auditor. Both happen, and both come down to the same root cause: no one at the site owns the job of watching for amendments. Keeping up isn't hard, but it does need to be deliberate. (Understanding VIRM amendments explains why the stakes are higher than they look.)
This article is about the input side — how changes reach you and how to make sure they always do. What you do once an amendment lands is covered in turning a VIRM amendment into site practice.
Where amendments actually live
NZTA publishes VIRM amendments on the Vehicle Inspection Portal, and there's more than one place a change can appear:
- The Amendments tab, with a dedicated page per manual — the one most WoF sites care about is VIRM: In-service certification.
- Amended-page stamps. Individual manual pages carry a note such as "Page amended [date] (see amendment details)", so you can see what changed and when.
- The minor changes and improvements register, for smaller corrections and clarifications.
- The interim amendments page, for changes published between the regular updates.
- The News and Inspection news pages, where larger changes — like the November 2026 inspection changes — are announced ahead of time.
The portal also has a "Sign up for news and updates" subscription. That single step pushes announcements to you instead of relying on you to go looking, and it's the cheapest piece of insurance available.
Scheduled vs interim: why periodic checking isn't enough
A monthly "check the Amendments tab" habit is good, but it has a blind spot: interim amendments. Because NZTA can publish these between scheduled updates to act quickly, a change can take effect inside your checking gap. The fix is layered: subscribe for push notifications and keep a periodic manual sweep, so nothing falls between the two.
Build a routine that survives busy weeks
A monitoring process that depends on goodwill fails the first hectic week. Make it robust:
- Name an owner. One person is responsible for reviewing amendments — with a named backup for leave.
- Use both channels. Subscribe to updates, and diarise a regular sweep of the Amendments tab and interim amendments page.
- Record what you receive. Log technical information and amendments in your QMS technical information record — that's both your working list and your evidence that the process runs.
- Hand off to the practice step. Once an amendment is logged, it moves into the brief-and-record routine so it reaches every affected inspector.
Steps three and four are where monitoring connects to compliance: the technical information record proves you received the change, and the training record proves you acted on it. Together they answer the auditor's question before it's asked.
Turn watching into a system
Manual monitoring works, but it leans on one person remembering. The more durable approach is to have the watching done for you and the receipt logged automatically — which is what the VIRM alerts module is built to do, feeding the register discipline described in the QMS registers every IO must keep. However you do it, the test is simple: could a change reach your bench before it reached your inspectors? If the honest answer is "possibly," the routine isn't finished yet.