On 16 April 2026 NZTA confirmed a set of light vehicle inspection changes that begin on 1 November 2026. They follow the public consultation that ran from 29 October to 17 December 2025, which drew more than 5,000 submissions with overall support for the proposals. For inspecting organisations this is the most significant change to the in-service regime in years, and the work to be ready for it starts well before the date.
This article is an operational summary for IOs. It is based on NZTA's published overview; the detailed VIRM updates, further ADAS guidance and system changes are still to come, so treat the specifics below as the announced position rather than the final manual text.
What's changing, in three parts
The announcement covers inspection frequency, inspection scope, and enforcement. The first two are what change your day-to-day work.
1. Inspection frequency
The headline is fewer inspections for lower-risk light vehicles. The six-month cycle disappears for the affected classes, and several groups move to longer intervals:
| Vehicle type and age | Current frequency | New frequency | Takes effect |
|---|---|---|---|
| New light vehicles | Second WoF at 3 years | Second WoF at 4 years | 1 November 2026 |
| Light vehicles 4 to 14 years old | Annual | Every 2 years | Registered on/after 1 Nov 2019: 1 Nov 2026. Registered 1 Nov 2013–31 Oct 2019: 1 Nov 2027 |
| Light vehicles 14 to 26 years old | Annual | Annual | No change |
| Light vehicles over 26 years old (registered before 1 Jan 2000) | Every 6 months | Annual | 1 November 2026 |
| Light rental vehicles | CoF every 6 months | Annual CoF | 1 November 2026 |
| Motorcycles registered before 1 Jan 2000 | Every 6 months | Annual | 1 November 2026 |
| Motorcycles registered on/after 1 Jan 2000 | Annual | Annual | No change |
In short: from 1 November 2026 the six-month WoF is removed for light vehicles, new vehicles get their second WoF at four years instead of three, and many vehicles aged 4 to 14 move to a two-yearly cycle — though that group is phased by registration date through to 1 November 2027.
The phasing on the 4-to-14-year group is the detail most likely to trip a front counter. For roughly a year, two vehicles of the same age can be on different cycles purely on their registration date — your system and your team both need to get that right.
2. Inspection scope: ADAS enters the WoF
WoF and CoF A inspections will check that no warning or malfunction indicators are showing for Automatic Emergency Braking (AEB) and Lane Keep Assist systems, where fitted. This is a malfunction-indicator check in the same family as the existing airbag and ABS checks — not a functional test of the system. NZTA has said more ADAS information is coming, and that's the guidance to brief your inspectors against once it lands.
3. Enforcement
Not inspection work, but worth knowing because customers will ask:
- The infringement fee for operating a vehicle with a WoF expired by more than two months rises from $200 to $350.
- Penalties for non-compliant wheels and tyres rise to $350 (infringement) and up to $1,000 (maximum court-ordered fine).
What an IO should action before 1 November
Nothing here requires a scramble if you start now:
- Brief the team on the new frequency rules — especially the phased 4-to-14-year group, and log that briefing in your training record.
- Plan for the ADAS guidance — watch for NZTA's ADAS material and the VIRM update, then run a second briefing when the detail is published.
- Confirm your checksheet and systems will reflect the change — the approved checksheet and any inspection software you use will need the new scope items and frequency logic. NZTA has flagged system updates of its own.
- Prepare a customer-facing line — front-of-house will field "why is my warrant different now?" from day one.
The changes are being implemented through amendments to the Land Transport Rule: Vehicle Standards Compliance 2002 and associated regulations, as part of the Government's Land Transport Rules Reform Programme. As with any amendment, the discipline that protects you is the same: read the VIRM update when it publishes, brief your inspectors, and log that you did both. That's the subject of turning a VIRM amendment into site practice, and it's exactly the workflow the VIRM alerts module is built to hold. For the wider picture of how amendments reach you and how to keep up, see understanding VIRM amendments.