WoFMate

eWOF explained: what an electronic WOF checksheet actually is

What an electronic WOF checksheet (eWOF) actually is, why NZTA has to approve one before a site can use it, what changes at the bench — and the questions to ask a provider before you adopt one.

By Mike Reece · Published 2026-07-26 · Updated 2026-07-27

Ask five people in the trade what an "eWOF" is and you will get five slightly different answers. Some mean the software their site uses. Some mean a checksheet that gets emailed instead of handed over. A few motorists think it is a new type of warrant with different rules.

The confusion matters, because sites are now making a real decision about whether to move off the paper pad, and it is hard to evaluate something the whole industry names three different ways.

So, plainly: an eWOF is an electronic WoF check sheet. It is the record of a WOF inspection, captured on a device instead of a carbon pad, producing the same check sheet in the NZTA-specified format. Nothing about the inspection itself changes.

Three names, one thing

The vocabulary sorts out like this:

  • Digital checksheet — NZTA's own term, used throughout its framework and provider documentation.
  • e-checksheet — trade shorthand, common among suppliers.
  • eWOF — what people in the workshop actually say.

They all describe the same object. If a supplier's brochure says one and an NZTA document says another, they are not describing different products.

What an eWOF is not

It is worth being blunt about this, because the misconception costs sites real confidence:

  • It is not a different inspection standard. The VIRM applies exactly as before. Same inspection items, same pass and fail criteria, same reasons for rejection.
  • It is not a relaxation of anything. If anything, an electronic record is harder to fudge than a paper one — which is rather the point.
  • It is not a windscreen label change. The label regime is separate from how the check sheet is recorded.
  • It is not a vendor taking over your compliance. Your inspecting organisation obligations remain yours. Software can make them easier to meet; it cannot assume them.

The only real change is the medium of the record, and everything that follows from that — legibility, retrieval, integrity, and how fast you can put a record in front of a reviewer.

Why NZTA has to approve it

You cannot simply build a form that looks like the check sheet and start using it. Digital check sheets sit inside a framework NZTA administers, and there are two distinct layers to it:

  1. The provider. The organisation supplying the software is assessed — fit-and-proper checks on the people behind it, security controls, record availability, breach notification, disaster recovery. This is the Digital Checksheet Provider layer.
  2. The product. Each check sheet — WoF, CoF-A, CoF-B and so on — is separately built and tested against NZTA's published check sheet specifications, demonstrated to NZTA, and approved by version.

That second point is the one sites most often miss. Approval is version-specific. A product is approved against a particular specification baseline, and substantive changes to the check sheet have to go back through NZTA rather than simply being shipped. When you ask a supplier "are you approved?", the useful follow-up is "approved to which version, and what happens when the specification changes?"

Both layers are about to matter a good deal more. NZTA has now confirmed publicly that check sheets will connect directly to its systems through approved providers, and that it will publish a list of those providers — see NZTA approved digital check sheet providers for what the transition means for a site choosing a product today.

What actually changes at the bench

Less than people fear, and more than they expect.

The inspector still inspects. What changes is that the record completes itself properly, or it does not complete at all. The failure modes that generate the most audit findings — blank fields, vague rejection reasons, missing signatures — are the ones a well-built electronic check sheet simply will not let you leave behind. A field that must be filled is filled. A rejection reason that must be specific is prompted for.

The same applies to the 28-day recheck: on paper, the link between a recheck and its original inspection is a filing convention, and filing conventions fail. Electronically, the recheck carries its own lineage because it cannot exist without it.

And document control — superseded forms in circulation, records that cannot be located on request, storage that allows quiet tidying-up after the fact — largely stops being a category of risk. There is one current version. Records are retrievable in seconds. Nothing can be altered after locking.

What does not change

Your obligations. All of them.

Record retention still applies with the same periods and the same indefinite-retention exceptions. Your QMS still has to be maintained. Your inspectors still have to be current and working within their appointments. A reviewer arriving on site will test the same things — they will just be reading a screen instead of a lever-arch file.

This is the point at which some sites relax too early. Adopting an electronic check sheet closes the record-keeping category of findings almost entirely. It does nothing at all for the training register, the calibration schedule, or the complaints record. Those remain a QMS problem, and they are where the other common findings live — which is a separate decision about whether to take your QMS online, and one with no approval regime attached to it.

Questions worth asking before you adopt one

A short list that separates serious products from hopeful ones:

  1. Is the check sheet approved by NZTA, and to which version? Ask to see it in writing.
  2. What happens when the specification changes? There should be a defined path, not a shrug.
  3. Can you get your records out? Export in a usable format, on demand, without a support ticket.
  4. Can a reviewer be given access? Read-only access to your records for an NZTA review saves an entire afternoon.
  5. Are records locked once complete? If a finished check sheet can be quietly edited, its evidentiary value drops sharply.
  6. What happens when the internet drops? Every site should know its fallback before it needs one.
  7. Who holds the compliance obligation? The honest answer is always you do — be wary of anyone who implies otherwise.

Where WoFMate sits

WoFMate's electronic WoF check sheet is approved by NZTA (Version 1.13/2026) for Warrant of Fitness inspections on light vehicles — cars, motorcycles and trailers — and is live in production. That approval is a temporary one, valid to 31 December 2027, while NZTA moves digital check sheet providers onto direct integration with its new Vehicle Inspection and Certification system, and we are continuing toward contracted Digital Checksheet Provider approval. The detail, including NZTA's approval letter, is on our compliance page, and the product itself is described on digital WOF checksheets.

Whatever you end up using: the terminology is not the hard part. The hard part is that a paper record is an act of discipline performed under time pressure, dozens of times a day — and an electronic one is not.

Frequently asked questions

Is an eWOF a different kind of Warrant of Fitness?

No. An eWOF is the same Warrant of Fitness, inspected to the same VIRM standard, with the same pass or fail outcome. The only thing that changes is the medium of the check sheet record — electronic instead of a paper pad. A vehicle inspected on an electronic check sheet is not held to a different standard, and the motorist's obligations are unchanged.

What's the difference between 'eWOF', 'e-checksheet' and 'digital checksheet'?

In practice, nothing — they are three names for the same thing. 'Digital checksheet' is the term NZTA uses in its own framework and provider documents. 'e-checksheet' is the common trade shorthand, and 'eWOF' is what most workshops and motorists actually say. If a supplier uses one term and NZTA another, they are still talking about an electronic WoF check sheet.

Can any inspecting organisation just build or use its own digital checksheet?

No. A digital check sheet has to be approved by NZTA before it can be used for live inspections, and the software behind it has to be built to NZTA's published check sheet specifications. An inspecting organisation adopting one should confirm the product is approved and which version of the specification it was approved against.

Does going electronic change my record-retention obligations?

Not the obligation — only the mechanics. The retention periods, the indefinite-retention exceptions and the requirement to produce a record on request all still apply, and they remain the inspecting organisation's responsibility, not the software vendor's. What changes is that electronic records are easier to store intact, retrieve quickly, and prove were never altered after the fact.

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.