BAMML Executive Insights
Compliance in Transport Fails at the Depot, Not the Head Office
Transport compliance is designed at head office and decided at a depot gate.
Head office writes the policy, maintains the register, reports the assurance and answers to the board. All of that is real work and it is necessary.
But the moment that determines whether the organisation is actually compliant happens somewhere else — at four in the morning, at a depot, when a vehicle is due out, a document is missing or a driver is not quite right, and somebody has to decide whether the load goes.
That person is usually junior, under time pressure, and aware that a delayed load has immediate, visible, personal consequences.
What is actually happening
The compliance system is built to produce assurance upwards. Policies exist. Registers are maintained. Reports are compiled and presented, and they generally show compliance, because they are drawn from the system that records what should have happened.
The exception — the load that went out when it should not have — frequently does not enter that system at all. Not because anyone is concealing it, but because there is no comfortable route for recording it. The person who let the load go has no incentive to log a decision that looks like a breach. The supervisor who was called has no incentive either.
So the organisation's compliance reporting is, in a quite specific way, a report on its policies rather than a report on its behaviour.
Then an incident happens, and the gap becomes visible all at once — because the enquiry does not ask what the policy said. It asks what was done, and what can be evidenced about the state of the vehicle and the driver at the moment of dispatch.
Why it matters
Three features make this exposure worse than it first appears.
The decision sits at the wrong level. The person with the authority to stop a load usually has the least organisational protection for doing so. Stopping a load is visible, costly and attributable. Letting it go is invisible unless something happens. The incentives point the wrong way, and no amount of policy corrects an incentive.
The pressure is predictable. Breaches do not occur randomly. They cluster — at particular times, particular depots, under particular customer deadlines, when a particular supervisor is on duty. That predictability is useful, but only if exceptions are recorded, which is exactly what does not happen.
Assurance is confused with evidence. A signed policy, an annual declaration and a training register demonstrate that a system exists. They do not demonstrate that a particular vehicle was fit and a particular driver was compliant on a particular morning. When it matters, only the second kind of record helps.
The Integrated View
| Discipline | The depot-level question | The usual head-office answer |
|---|---|---|
| Risk & Compliance | Can we evidence fitness and compliance at the moment of dispatch? | We have a policy and a register |
| Operational Performance | What happens to the load when the answer is no? | Not defined — it is handled |
| Workforce Governance | Who may stop a vehicle, and what happens to them when they do? | Anyone may raise a concern |
| Financial Governance | What does a stopped load cost, versus an incident? | The first is measured; the second is insured |
| Executive Decision Intelligence | How many loads were dispatched outside standard last month? | That figure does not exist |
The final row is the diagnostic. If your organisation cannot say how many exceptions occurred last month, it is not because there were none.
What good looks like
Name, in writing, who has authority to stop a vehicle — and make it explicit that exercising that authority correctly is never held against the person, even when the customer complains. Then make that real the first time it happens, because everyone will be watching how that first case is handled.
Create a route for recording an exception that does not function as a confession. An exception log that is reviewed for pattern rather than for blame will receive entries. One that triggers disciplinary attention will receive none, and the absence of entries will be misread as compliance.
Report exceptions upward as a standing figure. Not to punish depots, but because a depot with zero exceptions and high volume is either exceptional or not recording, and the executive needs to know which.
And check evidence at the point of dispatch rather than the existence of policy at head office. Those are different audits, and only one of them helps afterwards.
What to do on Monday
- Ask how many loads were dispatched outside standard last month. If the number is zero, ask how it would have been recorded if it were not.
- Ask who may stop a vehicle, by name and by role. Then ask them whether they believe they can.
- Find the last time a load was stopped on compliance grounds. What happened to the person who stopped it?
- Check whether exceptions cluster by depot, time, supervisor or customer deadline.
- Pull five recent dispatches at random and ask for the evidence that vehicle and driver were compliant that morning.
That last test is the one that tells you where you actually stand, and it takes an hour.
