The card download lands on a Tuesday. By Wednesday morning it's spat out an amber flag — driver ran 9 minutes over the 4.5-hour driving limit before the break. Small. Not the end of the world. But it is, in a way. Because if you let that flag sit there, the Traffic Commissioner is going to call it a pattern, and patterns are what get transport managers hauled into a Public Inquiry.
I've held a Transport Manager CPC for eleven years. I've run compliance for a 12-vehicle fleet in Coventry, done external work for a 3-vehicle skip operator in Birmingham, and sat in the back of a PI listening to an old boss lose his repute. Here's what the workflow looks like when a driver's card flags an infringement, written for the person whose name is on the O-licence.
The "continuous and effective" standard
Your CPC says you are responsible for the continuous and effective management of the transport activities of the operator. Those two words — continuous and effective — are the test. The Traffic Commissioner doesn't care whether you were on holiday that week. They care whether the system that catches infringements was running.
Continuous means the downloads happen on schedule. Driver cards every 28 days, vehicle units every 90. If you go 40 days between downloads because the yard was short on bodies in March, you've failed the continuous test.
Effective means the flags get reviewed, discussed with the driver, rectified, and logged. If the downloads happen but the flags sit in the analyser for three months because nobody's checking the dashboard, you've failed the effective test.
You can have one. You can have both. You cannot claim you have a compliance system if you only have the first half.
What lands on your desk when the card flags
Your analyser — Tachomaster, TruTac, FleetCheck, OPTAC3, whichever your operator uses — categorises infringements by severity. The DVSA severity categories apply: most serious (MSI), very serious (VSI), serious (SI), and minor. A 9-minute break overrun is usually minor. A 2-hour daily rest shortfall is most serious. The analyser colour-codes them and produces a report.
The flag gives you:
- Driver name and card number
- Vehicle registration
- Date, time, duration of the infringement
- The specific rule breached (561/2006 article or WTD regulation)
- Severity category
That's the raw material. Your job is to turn it into a resolved case within days, not weeks.
The 48-hour workflow
Here's what I do. Every fleet runs it slightly differently, but the bones are the same.
Day 1 — triage. Pull the analyser report. Flag anything MSI or VSI for same-day action. Everything else goes into the weekly review queue. A most serious infringement — daily rest under 7 hours, weekly rest under 20 hours, driving over 11 hours in a day — is not a tomorrow problem. Call the driver. Today.
Day 1–2 — driver conversation. Talk to the driver. Not an email. A phone call or a face-to-face. Two reasons: first, you need the context — was the card missing, did the traffic on the M6 make them blow the 4.5-hour break, did the planner send them an impossible load? Second, the driver needs to feel that you've noticed. A silent infringement becomes a habitual infringement.
Day 2–3 — written warning or note. Log it. The analyser has a notes field. Write up what happened, what the driver said, what action you took. Sign it with your name and date. This is the document DVSA will ask for if they come calling. "Conversation held with driver Thompson 24 April 2026 regarding MSI daily rest infringement of 52 minutes on 22 April. Driver cited delayed unload at Felixstowe; planner has been instructed to build 30 min buffer for Felixstowe runs. Driver signed confirmation of understanding."
Day 3–5 — systemic fix. If the same infringement keeps coming up from different drivers, the driver isn't the problem. The system is. Common ones: a planner sending tight-turn loads, a depot that regularly holds drivers past their break, a yard that doesn't have a proper parking bay so drivers park on the card to load.
Weekly — pattern review. Every week I pull a fleet-level summary. Count infringements by driver, by route, by day of week. Most serious at the top. If one driver's card has 8 flags in 4 weeks, that driver needs a formal development plan. If one route has flags across 5 drivers, that route needs rebuilding.
The bit that bites — reduced weekly rest debts
Infringements aren't the only thing your analyser tracks. It also tracks open compensation debts. If a driver took a 24-hour reduced weekly rest in Week 10 and hasn't booked the 21-hour compensation by end of Week 13, that becomes a fresh infringement on Week 14's download. The compensation must be en bloc, attached to another rest of at least 9 hours.
I covered the mechanics in the weekly rest post. From the TM's side, the key is the analyser flags the debt the moment the reduced rest is taken — so you have three weeks to schedule the payback before it goes red. Don't wait until the deadline hits.
What the Traffic Commissioner expects
I've sat through a Public Inquiry where the TC spent 40 minutes on the infringement handling process before they looked at a single piece of paperwork. Their questions, in roughly this order:
- How often are driver cards downloaded?
- Who downloads them?
- How are infringements reviewed?
- How is the driver informed?
- What training follows an infringement?
- Show me the notes from the last six most serious infringements.
- Show me the training records for the drivers involved.
If any of those answers is "I'm not sure" or "we don't have a written process", you've already lost. The TC needs to see a system that is continuous and effective — their words, not mine.
They also care, a lot, about the relationship between workload and infringements. If a driver's been booked 13-hour shifts five days a week and then flagged for WTD breaches, the TC will ask who planned the rota and why they thought it could be done legally. That question's for the TM, not the planner.
Repute — yours, not the operator's
Here's the bit that gets forgotten. Your Transport Manager CPC is held in your name. The O-licence belongs to the operator. If the operator's licence is revoked at a PI, the business loses the right to run vehicles. If your repute is lost, you personally lose the right to be a named TM on any O-licence in the UK.
That's the career consequence. An external TM can be named on up to 4 operators with a combined total of no more than 50 vehicles. Lose repute and all four operators need a new TM inside the grace period the TC grants — usually 3 to 6 months. Your name stops appearing on licence applications.
The fastest way to lose repute isn't one big failure. It's a pattern of inattention. A failed download schedule. Infringements stacking up without resolution notes. Drivers saying they've never heard from you. Planners running rotas that make the rules mathematically impossible. The TC sees the pattern across the O-licence data and the OCRS score before you ever sit down in front of them.
The three-row spreadsheet that saved my repute
I run a spreadsheet. Three columns: Date, Infringement, Action Taken.
Every flag goes in. Every conversation goes in. Every training session, every warning letter, every route rebuild. If the TC asks me tomorrow what happened between February and April, I open the spreadsheet and the story is there. Dates. Names. Outcomes.
My analyser has a notes feature. I still keep the spreadsheet. Belt and braces. The analyser data can be exported if the subscription lapses, but I've watched a TM lose access to their old operator's analyser the day they left, and the records they thought they had went with it. Keep your own copy. It's your CPC.
The 12-month rule
Operators must produce records to enforcement officers for 12 months. That's the minimum retention window. Any download, any infringement log, any training record has to be retrievable for 12 months minimum.
I retain everything for 24 months, and I archive to the cloud monthly. An OCRS encounter that happens today will look at data from today. An encounter next month might look at data from 11 months ago. A PI looks at the whole year. If you can't produce a record, the TC assumes the record doesn't exist, and absence of record is taken as failure of the "effective" half of continuous and effective.
Short version for the folder in your desk drawer
- Driver card downloads every 28 days max
- Vehicle unit downloads every 90 days max
- MSI and VSI infringements — same-day action, phone the driver
- All infringements — written note on the analyser plus a copy of your own
- Weekly pattern review — count flags by driver and route
- Monthly fleet summary to the operator
- 12 months minimum retention
- If you're named on more than one O-licence, run the process identically across all of them
Transport manager is not a job where you can be 80% compliant. Your repute is binary — you have it or you don't. The workflow above is boring. It's meant to be. Boring workflows are what the Traffic Commissioner wants to see.
If you're tired of writing tacho infringements into a notebook and hunting for training records at the bottom of an email thread, ShiftOwt tracks 561/WTD compliance automatically — £5.99/mo for drivers, agency pricing on request.