Most of what has been written about the 1 November 2026 changes is about inspection frequency. The change that lands on the inspector's own bench is smaller on paper and more demanding in practice: a new item on the check sheet, and a requirement to say what kind of system has failed.
This article covers what NZTA has actually published, what it leaves open, and what a site should have in place before the date. For the full November package, see the November 2026 WOF inspection changes.
What the rule says
From 1 November 2026, WoF and CoF A inspections check that no warning or malfunction indicators are showing for any advanced driver assistance system (ADAS) that fully or partially assists with the steering or movement of the vehicle. NZTA's July 2026 check sheet specifications list it as an "ADAS warning light" item in the vehicle interior group, from that date. It is not required for trailers, and on the CoF side it applies to CoF A only.
It is an indicator check, in the same family as the existing airbag and ABS lamps. Nobody is being asked to verify that a system works — only to see whether the vehicle is telling its driver that it does not.
The new part: record the category
NZTA's notice to check sheet owners of 15 September 2026, Changes to check sheets – WoF and CoF A, adds a new fault code under Internal Inspection. When an ADAS warning or malfunction indicator is showing, the inspector must record the category of ADAS the vehicle has failed in the notes section of the check sheet.
There are four categories:
| Code | Category | NZTA's examples |
|---|---|---|
| ADAF | Acceleration functions | Adaptive cruise control, intelligent speed assist, predictive cruise control |
| ADS | Steering | Lane keep assist, emergency lane keeping, lane centering assist |
| ADB | Braking | Automatic emergency braking, rear AEB, brake assist |
| ADCF | Autonomous control functions | Self-parking, autonomous driving functions |
NZTA is explicit that the examples are not a complete list. That matters, because the earlier public shorthand — "AEB and lane keep assist" — covers two of the four categories and none of the other two. Brief the categories and the question behind them: what is this system doing to the vehicle's steering, braking, acceleration or control?
Why this is harder than it looks
An airbag lamp is an airbag lamp. ADAS indicators are not so tidy, and a few problems are predictable.
Lamps don't say which category they mean. A generic "driver assist fault" message or a camera-sensor warning may cover several functions at once. The inspector has to work out what the system controls — which means knowing the systems, not just the lamps.
The fleet is mixed. A decade-old import, a current hybrid and a five-year-old SUV can each present ADAS differently, and a lot of inspector knowledge predates these systems entirely. This is a competence question, not only a paperwork one.
Overlap is real. One forward camera can feed lane keeping and emergency braking. NZTA's wording does not address this. Record every category that applies and write down what you saw.
One question the published text leaves open. NZTA's wording concerns indicators that are showing. It does not say how to treat a vehicle where the driver has switched a system off, or where an indicator is displayed intentionally. Until the VIRM says otherwise, treat that as a judgement call — make it deliberately, note the reasoning, and raise it with NZTA if a real case lands on your bench.
Where the text lives, and where it doesn't
The ADAS text is not in the 14 October 2026 amendment — that is covered in the 14 October VIRM amendment. The requirement currently reaches inspectors through NZTA's inspection news, the July 2026 specifications and the 15 September check sheet notice. That is a thin, scattered paper trail for something an inspector will be expected to apply from day one, and it is exactly the kind of change that never arrives as a tidy amendment. Diary a check of the VIRM and NZTA's communications for further ADAS detail before 1 November, and give it an owner.
Three jobs before 1 November
1. Update the check sheet you actually use. NZTA's notice says check sheet owners must update their sheets before 1 November, and send a copy or screenshot of the change to NZTA's technical team. If you run your own paper or in-house sheet, that is your job. If you use a digital check sheet from a provider, ask them directly whether and when it will carry the new fault code and a place for the category. An inspector cannot record what the form gives them nowhere to write.
2. Brief every inspector, by category. A single read-this email will not do. Walk the team through the four categories using vehicles they will actually see, including the awkward overlap cases above. Treat it as a VIRM change turned into site practice, with a second session once any further NZTA guidance lands.
3. Log the briefing as training. This is the part that gets skipped. Reading, discussing and working through new technical material is loggable training, provided the record says who, what and when — and the audit finding that follows an unrecorded briefing is the one covered in unlogged training. Where you want evidence that inspectors took it in, rather than merely received it, that is the distinction in read and understood: evidencing inspector comprehension. WoFMate's VIRM alerts and inspector quizzing exist for precisely that gap between circulating a change and proving it landed.
The reviewer's question
If a reviewer asks in November how your site prepared for the ADAS item, a good answer has three parts: this is the form we changed, this is when every inspector was briefed and by whom, and this is the record showing it. A vague answer — "the team knows" — is the one that turns a sound workshop into a finding.
For where this sits among the wider rule changes, see the pillar guide, understanding VIRM amendments.