DomainValidatedUpdated 2026-08-10

Source: Waka Kotahi NZ Transport Agency — “Model Quality Management System” (Feb 2025, current/authoritative) and “Quality Management System Requirements” (30 May 2014, superseded, kept here for historical comparison). This is regulator source material — treat it as ground truth for scope, not a Benchmarq design decision. Product opinions derived from it belong in product/, not here.

Why this document matters

This is the actual regulatory specification Benchmarq’s automotive beachhead customers are required to comply with: the six categories, the review process, and the exact record set required are published and fixed by Waka Kotahi — this isn’t something Benchmarq needs to infer from customer interviews, only validate against real operator pain.

Correction, 2026-08-10: this document originally stated there was no dedicated software solution for these requirements in the NZ market. Desk research found that’s not accurate — two live, NZ-specific, NZTA-approved products exist today, WoFMate and itsallauto.com’s eWOF™, and one of them (WoFMate) already ships a “QMS Compliance Centre” covering most of the master records list below. See research/nz-specific-trade-compliance-check.md for the full findings. Neither product shows evidence of having saturated the market — most of NZ’s 4,000–5,000 vehicle repair businesses still appear to be on paper/spreadsheets or a self-built solution (as with the Totara-based prototype) — so this isn’t a “someone already solved it” situation, but “no dedicated software exists” is not a true starting premise. This document still serves as the base regulatory spec for what Benchmarq’s QMS product needs to do; the competitive picture belongs in opportunity/market-analysis.md and research/, not here.

Stability of the requirement set

Comparing the 2014 and 2025 versions: the six categories and their intent have not changed in over a decade. Amendments since 2014 have been narrow, additive administrative changes:

Date Change
Feb 2021 Vehicle inspector certificates no longer need physical display if held electronically
Oct 2023 Review timeframe changed from 5 years to 3 years; process update for non-compliance handling; added public liability/professional indemnity insurance requirement; added specific technical information management requirements; added performance assessment checksheet links; clarified assessment scope (IO + any VI employed)
Oct 2024 “Vehicle Inspection and Certification (VIC)” system named
Feb 2025 Added Duplicate Labels Register requirement

Product implication: this is a low-churn regulatory spec. A system built against the current six-category structure is unlikely to need structural rework — amendments have been incremental record/field additions, not framework changes. That reduces roadmap risk for a compliance-first product considerably.

The six requirement categories

1. Organisational ownership and accountability

2. Technical performance

3. Administrative performance

4. Resources

5. Management

Eight sub-areas, each requiring a “coordinated approach” and (mostly) a dedicated record:

6. Performance improvement

Master records list (the full record set an IO must maintain)

This is effectively the object model for a Benchmarq MVP:

  1. Complaints record
  2. Controlled document record
  3. Delegation record
  4. Equipment record
  5. Improvement record
  6. Induction record
  7. Internal performance assessment checksheet — Inspecting Organisation (general + technical parts)
  8. Internal performance assessment checksheet — Vehicle Inspector
  9. Notification of lost or stolen controlled documents
  10. Notification of vehicle inspector transfer
  11. Staff record
  12. Technical information record
  13. Training record
  14. Duplicate labels register (added Feb 2025)

Waka Kotahi currently distributes these as downloadable templates (Excel/manual checksheets) from https://vehicleinspection.nzta.govt.nz/prs-qms/qms — i.e. the status quo is a pile of disconnected spreadsheets and forms, which is exactly the gap thesis Benchmarq is built on.

The review & enforcement process (relevant to product value prop)

Product implication: there’s a concrete, quantifiable value story here — a system that keeps records audit-ready in real time plausibly reduces an operator’s chance of tipping into non-routine (paid) review territory. This is a stronger ROI pitch than generic “save time on admin.”

Terminology to reuse verbatim in product/docs

Using the regulator’s own terms (rather than inventing new ones) will matter for credibility with MTA and NZTA-adjacent audiences: IO (Inspecting Organisation), VI (Vehicle Inspector), VIRM, controlled / uncontrolled / external document, Notice of Appointment (NoA), routine / non-routine performance review, Internal Performance Assessment.