Ask a workshop manager whether his inspectors have conflicts of interest and the answer is usually a confident no. Ask whether any of them has ever inspected a mate's ute, a brother-in-law's van, or a vehicle that came out of the owner's own yard, and the answer changes.
That gap is the whole subject. The difficulty with conflicts is not that they happen. In a trade where everyone knows everyone, they will. The difficulty is that the usual way of dealing with them — a quiet word and getting on with the job — leaves no evidence at all.
What the system actually asks for
The NZTA Model QMS includes a conflict of interest record among its master records, and the wording is deliberate: actual, potential and perceived conflicts, managed and documented. Three words, and the last two do most of the work. A potential conflict has not hurt anyone yet. A perceived one may not be a conflict at all. Both are in scope, because the point of the record is not to catch wrongdoing; it is to show that the site notices situations where independence could be questioned and decides what to do before the vehicle is on the bench.
The NZTA Vehicle Inspector Code of Conduct says the same thing from the inspector's side. Inspectors commit to avoiding conflicts of interest and to not behaving in ways that create an actual one, and the Code recognises that a conflict can arise whenever an organisation or inspector has relationships or interests that make it hard to perform their duties objectively. That is a personal commitment, not something a policy in a folder satisfies.
At the other end, conflicts of interest are one of the topics a certification officer may cover if a site assessment is carried out at reappointment.
Where conflicts actually turn up
They are rarely dramatic. The ones that turn up at WOF sites are mundane:
- The inspector's own vehicle, or one owned by their household.
- The employer's vehicle — a courtesy car, a company ute, a vehicle from the owner's other business that comes through for its WOF.
- A family member's vehicle, brought in because "it's easier to do it here".
- A colleague's vehicle, where the inspector and the owner work side by side every day.
- A friend's vehicle, which is the hardest to spot because nothing on the paperwork shows the relationship.
None of these says the inspection was done badly. The problem is that nobody outside the workshop can tell, and the record is what lets them.
The three ways the record fails
The register that does not exist. The policy is somewhere, the Code of Conduct was signed at induction, and there is nothing in between. A reviewer asking for the conflict of interest record is handed a blank page, and "we've never had one" is a claim the site cannot support.
The declaration made after the fact. Someone remembers during the review week, writes it up, and dates it correctly — which is honest, but shows that the control did not operate when it was needed. A conflict record is only worth much if the entry came before the result.
The record that says nothing. "Conflict – friend's car" with no detail is better than silence, but not by much. What was decided? Did another inspector do the work, or did someone check it? Without the outcome the entry records that a conflict existed and is silent on whether it was managed, which is the half a reviewer cares about.
What a useful entry looks like
It does not need to be long. Who was involved, which vehicle, the nature of the relationship, the date, and what was done about it. The relationship is best captured against a small, fixed list — own vehicle, employer's vehicle, family member, colleague, friend, other — so entries are consistent and can be counted. "Other" needs a sentence of explanation, because it is exactly the case a reviewer will ask about.
If your policy requires a signed declaration, keep the signed form with the entry. And keep the policy itself where the rest of your controlled documents are, so the version staff signed against is the version on file.
One decision the record cannot make for you: what your policy actually allows. Some sites bar anyone from inspecting a vehicle they have an interest in. Others permit it with a declaration and a second inspector's check. Either can be defended. A policy that is silent, or one that says one thing and a site that does another, cannot.
Where WoFMate sits
The QMS Compliance Centre carries a conflict of interest register on Professional and above. Entries are made as incidents rather than as an annual form: the staff member is picked from your own staff list, the vehicle registration is recorded, and the reason is chosen from the same fixed list above, with a details field that is required when the reason is "other". Signed declaration forms can be attached to the entry, entries can be archived rather than deleted, and the conflict of interest policy can be uploaded as a controlled document so it sits alongside the rest of your library. A recurring conflict of interest review can also be set up as a QMS task with its own due dates.
What it does not do is judge whether a relationship is a conflict, or decide who should do the inspection instead. Those calls remain with the site, and the register's job is to show that the call was made.
Three things worth doing this month
- Ask the question out loud. At the next team meeting, ask whether anyone has inspected a vehicle belonging to family, a friend, a colleague or the employer. Five minutes will tell you more than the register has.
- Write down what your policy permits. Barred, or permitted with a declaration and a second check — pick one, in plain words, and make sure staff have actually read it.
- Make the entry before the inspection, not after. Whoever books the vehicle in is usually the first to know. Agree who records it, and put the job on someone's name, because a task that everyone assumes is covered is one nobody does.
The conflict record is one of the quieter items in the registers an IO has to keep, and it is also one of the cheapest to get right. A few honest lines made at the time show a reviewer how the site actually behaves, which is worth more than a polished register built for the visit — and it will be tested as part of the annual self-assessment long before anyone from outside looks at it. If it turns out the practice has been drifting, the answer is a corrective action that closes, not a reminder email.