Where the time goes before a review
The evidence for a monthly review is spread across inboxes, folders, portals and systems, so a Transport Manager spends time putting the case together before the review itself can begin. Records that are missing, stale or in conflict often come to light only when a deadline or a decision is close.
For a consultancy that reviews several operator licences, that assembling comes round for each licence every month. It is the part we prepare.
What we prepare before the review
We agree one case with you: one operator licence, one review period, the sources that count as authoritative and a named reviewer. Records come from the exports, folders, mailboxes or APIs you approve, and each keeps its document reference. Names, dates and expected evidence are matched up, and we tell a problem in the source apart from a problem in reading it. What comes out is a draft review pack that waits for the named professional’s decision.
One monthly review pack, worked through
Take one operator licence, one monthly period and one named Transport Manager. The tachograph, driver infringement, maintenance or PMI, brake, MOT and insurance records are linked to their source and status, and each record is matched to its source and to the review period before it enters the pack.
The working part of the pack is an evidence index. Each record has a source, a capture date, a status (present, missing, conflicting, stale or low-confidence) and a reviewer field, so the named qualified reviewer sees what to chase. The index is a working document for the review. It is not a statutory monthly checklist.
Where a driver or vehicle record is missing, mismatched, overdue or low-confidence, it appears in the pack with an owner and a link to the source. Nothing is quietly resolved. A specific evidence request is prepared for a named role and an agreed date, and it remains a draft until approved. The Transport Manager records the decision, the corrective action, the owner, the due date and the sign-off. That space is reserved for the qualified person.
Why the pack is built this way
The Traffic Commissioners’ framework for operator compliance audits in Great Britain says the auditor must have access to the compliance evidence and that unavailable evidence should be stated. It says maintenance records should cover at least four scheduled PMIs and driver records at least the previous three months. That describes a job that draws evidence from several sources and has to say plainly what is absent, which is the job the pack prepares.
The framework does not let us judge compliance, accept evidence, conduct the audit or make the professional declaration, and we do none of those.
What stays with the Transport Manager
The Transport Manager retains compliance judgement, investigation and sign-off. The workflow does not make roadworthiness, safety, disciplinary or regulatory decisions. The professional also approves every request, correction, write-back to a system or outside submission. Disputed, safety-critical, sensitive and low-confidence cases stop with a named reviewer.
How we start
We map one real monthly cycle. You authorise the licence, fleet, driver, tachograph, maintenance, PMI, brake, MOT, insurance and client-task records for that cycle, and we look at what your current systems already do before proposing anything on top of them.
You then receive a recommendation on the flow of evidence, and it will be one of three: run a draft-only pilot, configure the platform you already have, or stop because there is no useful gap left to fill. If your compliance systems already produce the complete case and trail of exceptions, we do not sell you another layer.
A pilot is draft-only. A small set of cases is prepared alongside your current process and every correction is classified, with no outside submission and nothing committed in a system. Task creation, approved requests or write-back are added only after accuracy, ownership and a way to roll back have been demonstrated.