Every Australian fleet operator has the same workflow on paper: driver reports a defect, the office triages, the mechanic or workshop repairs, the vehicle goes back out. Where the workflow fails is in the gaps between these steps — the moments when a defect is "raised", "noted", "passed on", "looked at", "sorted", and the operator cannot prove what actually happened in what order.

This article is for SMB fleet operators where the workflow is informal. It is not for enterprise operators with dedicated transport managers and CMMS systems. It is for the 10-50 vehicle operator who runs the office out of a converted shed next to the depot, where the manager is also the dispatcher and the bookkeeper, where defects are sometimes raised verbally at handover, where the workshop is a one-person business that comes by twice a week, and where the records are a mixture of paper, WhatsApp, voice notes and a spreadsheet.

If that is your operation, this article is the one that matters most for you in 2026.

The five-step workflow that survives

The NHVR Master Code for heavy vehicles and the equivalent state guidance for light vehicles set out the expected workflow in formal language. Translated into operational terms, it has five steps. Every step has to leave a contemporaneous, identifiable, unalterable artefact behind.

Step 1: Driver report

The driver raises a defect. The artefact is the report itself, with:

  • Date and time of report — generated by the system, not typed by the driver.
  • Driver identity — verified, not just typed.
  • Vehicle identity — registration plate, fleet number, odometer reading at report.
  • The defect description — the driver's own words, not pre-filled tick-boxes alone.
  • Photos where possible — with EXIF carrying GPS, capture timestamp and device fingerprint.
  • A submission acknowledgement — the driver sees confirmation the report was received.

The failure mode at this step is the verbal report. "I told the boss on the way out" leaves no artefact. The boss does not remember exactly when. The driver does not remember exactly which boss. The report exists in human memory, which Australian courts treat as one of the least reliable forms of evidence.

Step 2: Operator acknowledgement

Someone at the operator level acknowledges receipt. The artefact is:

  • Date and time of acknowledgement.
  • Acknowledger identity — by name, not just "the office".
  • The decision taken — quarantine the vehicle, schedule a fix, or no further action with reasons.
  • Linkage to the original report.

The failure mode at this step is the silent triage. The defect is read, considered "minor", and dismissed without any record of who decided what. When the same defect contributes to a loss two weeks later, there is nothing to show whether it was dismissed by the senior manager (who has the authority) or the apprentice (who does not).

Step 3: Vehicle quarantine

Where the defect is safety-critical, the vehicle must be removed from service until the fix is verified. The artefact is:

  • A status flag on the vehicle — visible in the dispatch system.
  • Physical control — keys removed, vehicle parked separately, signage on dashboard.
  • A record of the quarantine decision and timing.

The failure mode at this step is the unallocated-vehicle problem. Where vans are not allocated to specific drivers — common in last-mile, courier and same-day operations across Australian capital cities — a quarantined van can be re-issued by the next dispatcher who does not see the flag. The Wednesday note in the office tray fails this step.

Step 4: Repair and parts

The fix is carried out. The artefact is:

  • Date and time of repair.
  • Identity of the person who carried out the repair, with their licence or qualification.
  • Description of the fix.
  • Parts used, with reference numbers and supplier where appropriate.
  • Photos of the fix — the new component installed, with EXIF.
  • An invoice or job sheet from the workshop where the work was contracted out.

The failure mode at this step is the verbal fix. "The mechanic took it on Thursday" with no job sheet, no parts record and no photo of the new component leaves the operator unable to show whether the fix was effective, whether it addressed the actual defect, or whether the repair was carried out by a competent person.

Step 5: Verification before re-issue

The vehicle is returned to service only after a competent person verifies the fix. The artefact is:

  • Identity of the verifier — separate from the person who carried out the repair where possible.
  • Date and time of verification.
  • Description of the verification — visual, road test, mechanical test as appropriate.
  • The decision to release the vehicle.
  • A linked thread back to the original defect report.

The failure mode at this step is the missing verification. The mechanic declares the fix done; the dispatcher takes the keys back; the van goes out the next morning with no formal sign-off. If the fix was inadequate, no second pair of eyes saw it, and there is no record that anyone at the operator level took responsibility for releasing the vehicle.

Why courts care about each step separately

A WorkSafe inspector, a Coroner, a loss adjuster acting for an insurer, a state DPP prosecutor — all of them assemble the same picture from the same artefacts. They draw a timeline of the defect: reported on day N, acknowledged on day N+0, quarantined on day N+0, fixed on day N+5, verified on day N+5, returned to service on day N+5.

If any of those points is missing, they substitute the absence into a finding. "There is no record of when the report was acknowledged, and we cannot determine whether the decision-maker was authorised to dismiss the defect" is a finding. "There is no record of the vehicle being quarantined, and the same vehicle was issued to a different driver the next morning" is a finding. "The fix was carried out without parts records and without verification by a second competent person" is a finding.

The sum of three or four findings, in a fatal incident, becomes a "gross breach" or "reckless conduct" under the relevant state industrial manslaughter law. In Queensland, section 34A of the Work Health and Safety Act 2011 (Qld) carries a 20-year individual maximum and corporate fines up to 100,000 penalty units. The Office of Industrial Relations and WorkSafe Queensland investigates these matters in conjunction with the Director of Public Prosecutions.

The unallocated-fleet variant

Same-day couriers, last-mile delivery operators, parcel networks and food-delivery fleets across Australian cities frequently run unallocated fleets — drivers are issued whatever van is available that morning. The workflow is harder to enforce here because no driver has continuous accountability for any vehicle.

The countermeasure is a vehicle-side quarantine state that travels with the vehicle, not with the driver. A quarantined van cannot be issued from the gate. The keys are physically separated. The dispatcher's screen shows the vehicle in red. The defect history is attached to the vehicle, not to whichever driver last reported something.

This is the single most important workflow change unallocated-fleet operators can make. The operator who continues to track defects through driver-side channels (whoever was driving when it happened tells whoever is dispatching today) loses cases. The operator who tracks them through vehicle-side channels (the vehicle is quarantined, full stop, until fix verified) wins them.

The contractor driver question

Where drivers are independent contractors paid per drop — the dominant model in Australian same-day and parcel delivery — the operator's duty of care still applies. Under Safe Work Australia guidance, the PCBU duty under WHS Act section 19 extends to "workers" in the broadest sense: employees, contractors, sub-contractors, employees of contractors, labour hire workers, outworkers, apprentices, trainees, work experience students, and volunteers.

The Fair Work Ombudsman's view of contractor classification (the sham contracting question) is a separate issue but feeds into the same evidential problem. The investigator looking at a fatal collision will not be persuaded that the contractor "was responsible for their own pre-trip" if the operator paid them per drop, set their route, set their vehicle assignment and never received the check. The investigator will treat the operator as having retained the duty of care, and will look for the operator's record of how that duty was discharged.

The defensible operator runs the same defect workflow regardless of employment status. Every driver — own or contracted — submits the walk-round and any defect report through the same system. The system records who submitted what. The record is identical in evidential weight whether the driver was on PAYG or paid through ABN.

Notifiable incidents — the regulator finds out automatically

Section 38 of each state's WHS Act requires the PCBU to notify the regulator immediately of a "notifiable incident" — including the death of a person, a serious injury or illness, and a "dangerous incident" (including the failure of a load-bearing part of a vehicle). Notification is by phone in the first instance, followed by written notification within 48 hours.

The investigator arrives — sometimes the same day, sometimes within days — and asks for the workflow record. If your defect-report-to-fix-verified workflow is intact, the investigator usually concludes the operator discharged the duty of care and closes the file with an improvement notice or no further action. If the workflow has gaps, the investigation widens, the inspector talks to drivers, and the case starts moving toward enforcement.

For heavy vehicles, the NHVR Chain of Responsibility investigation runs in parallel with the WHS investigation. The same records satisfy both.

The Officer due-diligence duty under WHS s27

Section 27 of each state's WHS Act imposes a personal duty on each "officer" of a PCBU — directors, trustees, senior managers — to exercise due diligence to ensure the PCBU complies with its duties. The due-diligence elements are codified: acquire and keep up-to-date knowledge of WHS matters, gain an understanding of the operations and the hazards, ensure appropriate resources and processes are available, ensure information about incidents and hazards is received and responded to, ensure compliance with notification obligations, and verify the provision and use of the resources and processes.

An officer who cannot demonstrate compliance with the s27 duty faces personal liability — fines, in some jurisdictions, in the hundreds of thousands of dollars, and in industrial manslaughter cases, imprisonment. The records that demonstrate compliance are the same records the WHS regulator and the Coroner will examine.

What "tamper-evident" means in this context

The principle is simple: each artefact in the five-step workflow is sealed at the moment it is created. Each entry includes the cryptographic hash of the previous entry for that vehicle, forming a chain. Any retroactive change to an old entry breaks every entry that came after it.

What this gives the operator: the ability to show, at any point, that the entries are in their original state. What it gives the investigator: the ability to verify the chain themselves, without trusting the operator's word. What it gives the court: a record that has the same evidential weight as a contemporaneous bank statement or a court-stamped legal document.

The cost of running such a system in 2026 is small. The cost of running a paper-and-spreadsheet system in 2026 is the inability to defend a case that the chain-of-custody system would have defended.

The checklist for Australian SMB fleet operators today

  1. Map your current defect workflow. From "driver notices something" to "vehicle returns to service", who owns each step?
  2. For each step, identify the artefact. If the artefact is a verbal handover, a WhatsApp message or a tear-off pad, mark it as a workflow gap.
  3. For each gap, design the artefact that should exist there — driver report, acknowledgement, quarantine decision, repair and parts, verification.
  4. For unallocated fleets, build a vehicle-side quarantine state that the dispatcher cannot override.
  5. Apply the same workflow to contractor drivers as to own drivers. There is no second class of evidence.
  6. Brief the team on notifiable-incident timelines under WHS section 38. The regulator finds out about serious incidents one way or another.
  7. Migrate to a tamper-evident system within 90 days. The cost is small. The protection is large.

Sources & further reading

Related Mekavo articles: Coronial inquest — what your fleet maintenance record must prove, NHVR roadside intercept — the 12-minute window, Four phrases Australian insurers use to refuse a fleet claim, Adapted vehicles, the DDA and industrial manslaughter exposure.

Why we care

Mekavo Fleet was built around the five-step defect workflow. Every report is sealed at submission, hash-chained, EXIF-bound. Every acknowledgement carries the operator's identity. Every quarantine state lives on the vehicle and cannot be overridden by a dispatcher who did not see the flag. Every repair carries parts, photos and a competent-person signature. Every verification is a separate sealed entry. When the WorkSafe inspector arrives, you do not assemble a defence — you produce the record. We do not give you software. We give you a chain of custody.