Logistics & Transport /Document processing live field guide · 9 min

CoR-Evidence Monitor

Watches the driver logs, telematics, and maintenance records where Chain of Responsibility evidence lands, flags a fatigue, mass, or work-hour breach before an inspection finds it, and assembles an audit-ready evidence pack against the Heavy Vehicle National Law — surfacing exceptions for the compliance manager, never signing off on its own.

Open the live demo

theater/demos/logistics_cor-evidence-monitor.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads each evidence document as it lands — work diary, mass declaration, pre-start check — extracts the figures, checks them against the HVNL work, rest and mass limits, and surfaces every breach and near-miss for the compliance manager to approve before anything is filed.

Input 01

The evidence as it lands

The records Chain of Responsibility runs on: National Driver Work Diaries, fatigue records, mass and dimension declarations, pre-start vehicle checks and load-restraint certificates — handwritten dockets, scans and exports.

Agent 02

Extracts, then checks against the limit

Pulls the operator, date, vehicle and the regulated figure off each document, then checks it against the HVNL threshold that applies — work and rest hours, the General Mass Limit for the axle group, the load requirements — and names the breach where one is found.

Output 03

An exception list, with its working shown

A continuously current evidence pack plus an exception list — each breach or near-miss with the figure, the limit and the document it came from — for the compliance manager to review and approve before it is filed to the CoR register or escalated.

Where it works well

It checks every document against its limit, the same way, every time — before an inspection does.

Best where a fleet runs steady volume of fatigue-regulated trips — the breach you catch the day the diary lands is one you can still act on.
The overmass declaration or the short rest break gets read on arrival, not at audit, so the exception reaches the compliance manager while it is still fixable.
At a fleet's daily evidence volume, the recaptured hours go back into closing the breach and managing the CoR parties, not collating paper.

The slow, invisible work in Chain of Responsibility is the cross-checking: tracing each figure on a work diary or mass declaration to the HVNL threshold that governs it, across records that arrive scattered across drivers, telematics and email. Done by hand, it happens after the fact — when an inspection forces it.

Where it works badly

It is confidently wrong when the evidence is stale or incomplete — and the pack looks audit-ready when the underlying record is not.

Weak on the figure it can't read — a faded handwritten docket, a sideways scan, a number it has to guess. It should flag low confidence, not assume.
It checks the figure on the page; it can't tell you the page is the wrong version, or that a permit exists that would make an overmass load legal.
It does not know what never arrived — a driver who didn't lodge a diary is silence, and silence is not compliance.

The honest test

If you cannot say, right now, that every fatigue-regulated trip has a record in front of this tool — then a clean evidence pack is telling you about the paper you have, not the breaches you don't.

Point it at a work diary that was never filled in, or a mass declaration for a permit the system doesn't hold, and it produces a clean, organised evidence pack around a gap. A missing record reads as "nothing to flag", not as a hole. That is the trap.

What it doesn't do — and shouldn't

It surfaces and assembles. A person approves and signs off. That boundary is deliberate.

WHAT IT DOES

Surfaces the figure it read and the HVNL limit it checked against

Flags the breach or near-miss with the document it came from

Assembles the evidence pack and routes exceptions to the compliance manager

WHAT IT WON’T

Sign off the evidence pack as compliant

Decide which CoR parties carry a breach, or report it to the NHVR

Treat a missing record as a passed check

Under the Heavy Vehicle National Law, every party in the chain — operator, scheduler, loader, consignor — carries a primary duty to ensure safety so far as is reasonably practicable, and a breach can expose a business and its directors to substantial penalties enforced by the NHVR. A wrong call on a fatigue or mass breach lands on a named person, so the accountable person stays on the decision — the tool does not.

What your data has to look like

The regulated figures as readable fields, the limits in force, and every fatigue-regulated trip actually lodging a record.

Typical readiness

across orgs we see, before the first job

Work, rest and mass figures as readable fields

Needs shaping

A record lodged for every fatigue-regulated trip

Needs shaping

The current HVNL limits and any permits on file

Usual weak point

Vehicle and operator identity tied to each record

Usual weak point

A single place the evidence lands

Needs shaping

The real first job

The weak point is almost never the checking — it is the capture. Records arrive late, scattered, or not at all, and the limits and permits live in someone's head or last year's spreadsheet. Fixing how CoR evidence is captured, made readable and kept current is usually the real first job — larger and more valuable than the checking layer on top. Once the evidence flows in clean and complete, every check after that is faster and right by default.

Right fit if…

You run steady volume of fatigue-regulated trips and want breaches caught the day the evidence lands

Your work diaries, mass declarations and checks already arrive in one place, readable

You can point to the current HVNL limits and your permits on file today

A named compliance manager owns the sign-off and the CoR register

Walk away if…

Most of your trips are local-area work that never generates a lodged record

Records arrive as photographed dockets nobody retypes consistently

Your fleet's compliance is occasional and ad hoc, not a daily flow of evidence

You want a tool that certifies CoR compliance, or reports breaches to the NHVR, on its own

Open questions

The worried-buyer questions, answered straight

It can read a figure wrong, which is exactly why nothing is filed or cleared on its say-so. It extracts the work, rest or mass figure, checks it against the Heavy Vehicle National Law limit that applies, and shows its working — the figure it read, the limit it checked, and a flag where its confidence is low or a record is missing. The compliance manager reviews those before approving. The tool surfaces the breach; the person stands behind the call.

It works from readable figures — work hours, continuous rest, gross mass, axle group. A faded handwritten National Driver Work Diary or a sideways photo is exactly where it should flag low confidence rather than guess, and a person reads the original. Getting those records captured as clean, readable fields is usually the first piece of work — and the piece that pays off across every check after.

No. It removes the collation and the line-by-line cross-checking against the HVNL limits — the clerical hours — so the compliance manager spends their time on the judgement: whether a flagged breach is real, which Chain of Responsibility parties it attaches to, and what to do about it. The sign-off and the CoR register stay theirs. The capacity it frees goes back into managing the breaches, not assembling the paper.

Current to the trip and to the law in force. The Heavy Vehicle National Law’s mass and dimension limits are under active review, and a mass or access permit can change what’s legal for a given load — so a check against a stale limit, or a record that arrives days after the trip, drafts a confident wrong answer. The honest test: do you know, today, that the limits it’s checking against are current and that every regulated trip has lodged its record?

Driver work and rest records, operator details and vehicle data are sensitive and carry obligations under the HVNL and the Privacy Act. Any deployment runs against your own systems and data handling, not a shared pool — we scope where the data sits and who can see it as part of the build. The demo here runs entirely on fabricated data; Hume Freight Lines and the drivers shown are not real.

No — it makes breaches visible, it does not certify compliance or discharge your primary duty. Under the HVNL each party in the chain must ensure safety so far as is reasonably practicable, and that is a duty a business and its named officers carry, not a box a tool ticks. It gets the evidence pack and the exception list most of the way; the accountable person confirms the call and owns the sign-off.

What it takes to build

3–5 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · document extraction · rules engine · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One evidence type, one check

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your fleet?

The honest place to start is a bite-sized first piece — one evidence type, one HVNL check, low risk. Tell us where the compliance paperwork hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work