Ask a WOF site for its complaints record and you will usually get one of two answers. Either a folder comes out with two entries in it going back three years, or — more often — someone says, quite genuinely, "we haven't really had any."
Both answers are a problem, and for the same reason. Neither one is a process.
The VIRM does not ask an inspecting organisation to keep a list of complaints. It asks for a complaint management process, and the register is only the last of the seven things that process has to do. Most sites have built the register and skipped the other six.
What the VIRM actually requires
The In-service WOF and CoF introduction sets out a process that has to cover all of the following:
- A clear statement recognising the positive value of complaints.
- Clear instructions to customers on how to register one — a conspicuous notice on the workplace wall, a statement on any receipt or invoice, or a statement on the check sheet.
- A plain explanation of the expected standards for resolution and the customer's right to appeal to NZTA if they are dissatisfied with what you propose.
- Documented investigation, prepared to your QMS requirements, so the detail can be readily checked.
- Written acknowledgement of every written complaint within three working days, with the investigation completed and a resolution proposed within twenty working days of the complaint being made.
- A record of all complaints, verbal as well as written.
- Directions for any customer wanting to complain or appeal a decision to contact the NZTA Helpdesk on 0800 699 000.
Read that list against your own site. Most sites find the same three gaps.
Gap one: the nil return
"We haven't had any complaints" is the most common thing a WOF site says about this register, and it is almost never true. It is true of written complaints. It is not true of the customer at the counter who thinks the tyre call was harsh, or the fleet operator who rings about a fail he does not accept.
The requirement is explicit: verbal complaints go in the record too. An empty register does not read to a reviewer as a site with no complaints. It reads as a site not capturing them — the same shape as training that happened but was never logged, where the work occurred and the record went nowhere.
If your register is empty, decide what counts as a complaint, tell whoever is on the front counter, and start writing them down — including the ones resolved on the spot in four minutes. "Resolved at counter" is a perfectly good entry. An unrecorded one is not.
Gap two: the customer is never told how to complain — or that they can appeal
Two of the seven requirements put an obligation on you to publish the route, and a third says that route includes NZTA.
This is the one sites resist, because it feels like inviting trouble. It does the opposite. A customer who knows there is a process at your site tends to use it; one who does not goes straight past you — to NZTA, to a review site, or to the workshop down the road with the story.
It is also the cheapest requirement in the manual to satisfy: a notice on the wall behind the counter and a line on the invoice, with the check sheet expressly listed as another acceptable place to carry it.
Gap three: nobody is watching the clock
Three working days to acknowledge. Twenty working days to investigate and propose a resolution. Both start when the complaint is made, not when someone gets to it.
Twenty working days sounds generous until you notice it is a month of calendar time. The failure mode is not refusal — it is drift. The complaint lands in an email folder, the person who owns it is on the tools, and it resurfaces when the customer chases.
A complaint with a received date, a named owner and a status is a managed complaint. A complaint in somebody's inbox is a liability with a deadline already running.
The complaint you cannot answer without the check sheet
Nearly every disputed inspection decision comes down to one question: what did the inspector actually record, and when?
Produce the check sheet for that vehicle in under a minute — fail items, inspector, date, odometer — and the complaint is usually over in one phone call. Go to a box in the back and hope it was filed in the right month, and you have lost the argument before the paperwork arrives. That is the practical case for electronic check sheets that has nothing to do with tidiness: retrieval under pressure — which is also why record-keeping failures and complaints turn up together at a review.
Where a complaint reveals something real, it should not stop at the complaints register. It becomes a corrective action with an owner and a close-out test — a complaint the site agreed with and then did nothing about is a worse finding than the complaint itself.
Where WoFMate sits
To be precise about what the platform does: the QMS Compliance Centre carries a complaints register on Professional and above, recording the date received, the channel the complaint arrived through, the complainant, the nature of it and its status. The channel field is deliberate — it makes the counter conversation recordable alongside the emailed letter, which is the requirement most sites miss. Where a complaint needs fixing, it carries into the improvement register as a corrective action with an origin, an owner and a target date.
What no platform does — this one included — is meet the requirement for you. The notice on the wall, the decision about what counts as a complaint and the call to the customer are all yours. NZTA approves digital check sheets; there is no approval regime for QMS software, whatever a supplier implies. Software can hold the record and surface what is still open. It cannot have the conversation.
Three things worth doing this month
- Write the notice. One paragraph on the wall and one line on the invoice, both naming NZTA and 0800 699 000.
- Start logging verbal complaints. Backdate nothing; just start. In six months the register will look like a working site instead of an empty one.
- Put a date and an owner on every open complaint. Three and twenty working days are not aspirations; they are the standard you will be measured against.
A complaints record with a dozen resolved entries is not evidence that your site has a problem. It is evidence that it has a process — and alongside the other registers an IO has to keep, it is one of the easiest things to have straight before a reviewer arrives. A reviewer can tell the difference at a glance.