WoFMate

Checksheet record-keeping failures: the most common audit finding at WOF sites

Why checksheet records are the first thing an NZTA reviewer tests, the specific ways they fail — blanks, vague rejection reasons, missing signatures — and how to make them fail-proof.

By Mike Reece · Published 2026-06-13 · Updated 2026-06-13

If an NZTA reviewer only had time to look at one thing on a site visit, they'd look at your completed checksheets — because the checksheet is where every other compliance question leaves its evidence. It's also, year after year, where the most findings come from.

This article digs into the specific failure modes. For the full landscape of what reviews find, start with the pillar guide: Common audit misses and how to avoid them.

What the rules actually ask for

The requirements (VIRM In-service certification, section 3-6, under the Vehicle Standards Compliance Rule 2002) are short enough to summarise:

  • An NZTA-approved checksheet must be used — approved format, current version.
  • It must accurately record all applicable requirements for the vehicle class being inspected.
  • Writing must be legible on all copies, and the sheet must be signed by the vehicle inspector — in writing or electronically — once the pass/fail determination is made.
  • On a fail, the reasons for rejection must be clearly stated.
  • Where several people inspect parts of one vehicle, all must be vehicle inspectors, the sheet must record who inspected each part, and one inspector signs with overall responsibility.
  • The agent copy stays with the inspecting organisation; the customer copy goes to the owner on a fail or on request.

None of this is onerous on any single inspection. The trouble is that a busy site does it forty times a day, and paper makes every one of those forty an act of individual discipline.

How checksheets actually fail

The eloquent blank. A section left empty says one of two things to a reviewer: the item wasn't checked, or it was checked and not recorded. Both are findings. "We always check that" is not evidence; the record is.

Rejection reasons that can't be reconstructed. "Brakes" scrawled in the fail box tells nobody — not the customer, not the recheck inspector, not the reviewer — what was wrong, against which requirement, on which axle. Clearly stated reasons for rejection are an explicit VIRM requirement, and vague ones are among the easiest findings a reviewer can write up.

The missing or premature signature. The signature certifies the determination. Sheets that were signed before the road test, signed by someone other than the inspector who did the work, or never signed at all each undermine the one thing the document exists to prove.

The phantom second inspector. Hoist-side help is normal. A second pair of hands whose work isn't attributed on the sheet is not — if two people inspected, the record has to show who did what.

The illegible copy. Legibility is required on all copies. A duplicate that can't be read is, for evidential purposes, a blank.

Why good inspectors keep bad records

It's never laziness. It's that handwriting a complete, legible, attributed, well-reasoned record is a small tax paid forty times a day under time pressure, and paper collects whatever the worst five minutes of the day produces. The record quality of a paper site is set by its busiest hour, not its best intentions.

That's the argument for making the record structural. A digital checksheet that walks the inspector through every applicable section, won't complete with required fields empty, demands a specific rejection reason against the requirement, attributes each section to the inspector who did it, and applies the electronic signature as part of the determination step — that system produces a compliant record as a side effect of doing the inspection. The discipline moves out of the inspector's head and into the tool.

A quick self-test

Pull ten random agent copies from last month and ask: could a stranger reconstruct each inspection — what was checked, by whom, what failed and why — from the sheet alone? If the answer is "mostly", you've found your next internal corrective action before a reviewer finds it for you.

Frequently asked questions

What does the VIRM actually require of a WOF checksheet?

An NZTA-approved checksheet must be used, it must accurately record all applicable requirements for the vehicle class, the writing must be legible on all copies, and it must be signed by the vehicle inspector once they've determined the outcome. On a fail, the reasons for rejection must be clearly stated. The agent copy is retained by the inspecting organisation.

Can a checksheet be signed electronically?

Yes. The VIRM accepts a digital signature, the inspector's VI authority number, or a PDF e-signature on electronic checksheets. The signature must be applied once the inspector has completed the inspection and determined the pass or fail outcome.

What if more than one person inspects the vehicle?

Everyone inspecting the vehicle must be a vehicle inspector, the checksheet must record who inspected each part, and one inspector must take overall responsibility and sign the sheet. A record that doesn't show who did what is a finding waiting to happen.

Keep reading

See WoFMate on your own vehicles

Book a walkthrough with the founder, or start a 30-day free trial and run your next inspection digitally.