Missing Driver Checks: A Morning Reconciliation Routine

A dashboard showing ten checks does not tell you whether ten departures were covered. One driver may have submitted twice, a spare lorry may not have moved and a trailer collected later may not appear in the morning total. To find missing driver checks, start with actual use rather than form counts.

A short reconciliation can give a small transport office a clearer answer: which working assets have evidence, which need investigation and who will resolve each exception?

Build the expected-use list

Take the departures and handovers for the period under review. Include actual driver, vehicle, trailer, start time and any later equipment change. Remove a cancelled movement only after confirming it did not happen.

Do not start with the whole fleet register and call every parked vehicle a failure. Equally, do not assume the original planning board still reflects a last-minute substitution.

Match records by identity and timing

Compare expected use with the submitted evidence. Match asset identity, driver context and the recorded time. Investigate reports attached to another vehicle, duplicate submissions and records that arrive after departure.

DVSA's roadworthiness guidance supports a monitored checking and defect-reporting system. This reconciliation is an office control to support that system, not a substitute for checking the vehicle.

Use a short set of outcomes:

• Evidence found and relevant to the actual equipment.
• Equipment not used, with that fact confirmed.
• Record present but identity or timing needs review.
• Upload outstanding and driver contacted safely.
• Check not completed or unable to establish what happened.

Give every exception an owner

A list of unresolved names becomes background noise unless someone is responsible for the next action. Record the question, owner and review time. Escalate safety concerns to the person authorised to make an operational decision.

Do not contact a driver in a way that requires them to interact with their phone while driving. Use your safe communications procedure and agree how an urgent issue is handled.

Keep the explanation truthful

If a record was captured but not uploaded, retain the distinction between inspection time and receipt time where evidence allows. If the driver cannot establish that a check occurred, do not resolve the exception by asking for a backdated nil report.

A fictional twelve-departure review might find ten relevant records, one cancelled departure and one wrong-trailer entry. The open issue is one record mismatch, not automatically two missing checks. That distinction makes follow-up proportionate.

Measure what keeps going wrong

Review exception reasons weekly. Are drivers selecting a default trailer that changes at the yard? Is a checking area unavailable? Does the office allocate a different vehicle after the driver opens the job?

Count unresolved expected-use events, then show the denominator. “Two unresolved out of twelve departures” is more useful than “ten checks submitted”. Keep separate figures for late receipt and confirmed omission so improvement is visible.

Make the software demonstration answer this question

Ask the supplier to show a departure with the wrong asset, a trailer swap and a late upload. Then ask the office user to locate the outstanding evidence. This tests the link between assignment and records rather than the appearance of the checklist screen.

HauliK's walkaround check software provides asset-linked history and a demonstrated driver workflow. Use those records alongside your expected-use list. If a check reveals a fault, follow it into the defect reporting workflow instead of marking the morning review complete simply because a form exists.