Retention is the compliance question with the clearest answer and the messiest practice. The rule is short; the failures come from storage that can't honour it — records that technically exist but can't be found, proven unaltered, or distinguished from the ones it was safe to discard. This article sits alongside the QMS audit pillar guide and the document-control article; here we focus purely on how long and in what state.
What the rule says
Retention sits in the conditions of appointment (VIRM In-service certification, section 3-1, under the Vehicle Standards Compliance Rule 2002):
- Minimum 12 months for all records and associated documents relating to vehicle inspections and certifications — including failed inspections.
- Indefinitely for LT400s and other heavy vehicle specialist or engineer certificates. These don't age out; they stay.
That's the whole rule. The wrinkles are all in how you hold the records.
Electronic storage is allowed — on two conditions
You don't have to keep paper. The manual permits electronic storage provided:
- The electronic copy is not changed and is stored in a way that protects it from being changed — the manual's own example is saving as a read-only file.
- The information is readily searchable and accessible if you or NZTA need it.
Those two conditions are doing a lot of work, and they're where ad-hoc digital storage fails. A folder of PDFs anyone can open and overwrite fails condition one — not because anyone did alter a record, but because the storage can't prove nobody could. A shared drive with no naming discipline fails condition two — the record exists but isn't readily accessible, and "give us until tomorrow" is itself a finding.
Why "we still have it somewhere" isn't retention
Retention isn't a measure of whether a record physically survives. It's a measure of whether you can produce it, intact, on request. Three common gaps:
- The unfindable record. It's in a box, in a drive, in an inbox — somewhere. If it can't be retrieved quickly when named, the ready-accessibility condition isn't met.
- The alterable archive. Records kept where they could be edited after the fact lose their evidential value, because the record can no longer vouch for itself.
- The premature purge. Failed inspections binned as worthless; records cleared at twelve months that should have been held (or, for HVS certificates, kept forever). Retention cuts both ways — keeping too little and discarding the wrong things.
Make retention a property of the system, not a chore
The reliable way to honour a retention rule is to stop relying on anyone to honour it. Records that, on completion, are stored write-once, indexed for instant retrieval, and aged according to policy satisfy all three demands — minimum periods, indefinite exceptions, and tamper-resistance — without a human deciding anything case by case.
That's how WoFMate's digital checksheets and the QMS Compliance Centre treat records: locked on completion, searchable in seconds, retained on policy — with auditor access so a reviewer gets exactly the record they name, immediately. Retention stops being something you do and becomes something the system simply is.
The rule is twelve months, some things forever, never altered, always findable. Build storage that makes all four automatic and retention stops being a question you can get wrong.