For about two years I used a spreadsheet. Nothing fancy — dates in column A, driving hours in column B, rest start/end times in column C. My TM had one too, different format, different colour coding, completely different numbers sometimes. We'd compare them every fortnight and argue about who'd made the error. Turns out we were both just bad at maths under time pressure.
The problem with a spreadsheet isn't that it's inaccurate. It's that it's passive. It tells you where you've been. It doesn't warn you where you're heading.
The three things a spreadsheet can't see
EU 561/2006 runs on three clocks simultaneously. Your daily driving limit — the 9-hour cap, extended to 10 hours twice a week. Your weekly driving limit — 56 hours. And the fortnightly cap — 90 hours across any rolling two calendar weeks.
A spreadsheet can track all three if you set it up properly. The issue is that the fortnightly clock doesn't follow a Monday-to-Sunday boundary like most people assume. It's a rolling 14-day window. Start a fortnight on a Wednesday and you've immediately got a maths problem that no column of dates handles cleanly.
Missed that fortnightly calculation once. Thought I had 8 hours left. Had 3. Ended up parked on the A5 near Towcester at 22:30, calling my TM, both of us baffled about where the hours had gone. Cost me a delivery, cost the depot relationship, and cost me a £200 graduated fixed penalty at the next roadside check when DVSA pulled three weeks of data.
Second problem: the Working Time Directive runs on a completely separate 17-week reference period. You can't hit a 561 cap without hitting a WTD cap at the same time — but you absolutely can hit a WTD breach without hitting 561. Plenty of agency drivers run light on driving but heavy on POA and other work, especially multi-drop retail. A spreadsheet that tracks driving time will miss this entirely if you're not manually adding every waiting-at-bay minute as working time.
Third: tachograph download compliance. The card needs downloading every 28 days, the vehicle unit every 90 days. That's straightforward to track in a spreadsheet — until you've got three drivers, two vehicles, agency cards showing up on Monday, and someone's card reader at the depot that's been glitchy since October. Then you're guessing, and you're one DVSA visit away from a finding that your records have gaps.
What a live tracking app actually does differently
The fundamental difference isn't features. It's that the tool knows where you are right now in all three windows, not just where you were yesterday.
ShiftOwt pulls tachograph data and updates your remaining hours in real time. It tracks the 9/10-hour daily limit, the 56-hour weekly cap, and the 90-hour fortnight — all three simultaneously, all rolling correctly regardless of what day of the week you started work. The app flags when you're approaching a threshold, not after you've blown through it.
For the WTD side, it tracks your availability periods separately from driving. That matters for multi-drop work especially. Waiting in a bay counts as availability or other work depending on whether you've been told roughly when you'll be loaded and whether you need to stay in the vehicle. A spreadsheet treats it as whatever you type. The app treats it as whatever the tachograph recorded.
It also tracks download windows. You get a flag before the 28-day card download deadline, not after. Small thing, but it's the sort of thing that slips when you're running hard.
Where spreadsheets still work
Look, I'm not saying every driver needs a compliance app. If you're a single-vehicle owner-driver, you work regular Monday-to-Friday hours for one client, and you sit down every Sunday to update your records — a spreadsheet is probably fine. You've got low complexity and the discipline to maintain it.
Same goes for small fleets where the TM is in the office every morning pulling downloads. That's a manual process that works if it's actually happening.
Where spreadsheets fall apart is anywhere there's variability. Agency work with different start days. Tramping across calendar weeks. Multiple vehicles, multiple drivers, anybody sharing a card reader. The moment you're tracking more than two drivers or your week doesn't start on Monday, spreadsheet errors compound fast.
The OCRS problem
Here's the thing that most drivers don't connect until it's too late: it's not just the fixed penalty you're looking at when infringements stack up. It's the OCRS hit. Operator Compliance Risk Score goes red when DVSA pulls enough data to show a pattern. One driver, three infringements in six months — that's not an anomaly. That's a compliance failure, and the Traffic Commissioner treats it as one.
A mate of mine runs a 12-vehicle fleet out of Coventry. Two drivers hit the fortnightly cap within the same month. He was tracking on a spreadsheet, neither infringement showed up until the DVSA check. By the time he knew about it, the OCRS had shifted to amber. He spent six months in earned-recognition territory trying to get it back down, and that was before the undertakings meeting with the TC.
The cost of a tool that prevents that outcome is trivial compared to the cost of a TC public inquiry. Even if you're a single driver. Especially if you're a single driver, because you're the operator as well.
What about the cost
ShiftOwt is £5.99 a month for drivers. That's less than the cheapest truck stop meal at Stafford Services northbound. Agency pricing is on request for fleet use.
I know that sounds like an advert. It's not — I just can't think of a sensible argument for spending more time and stress on a spreadsheet that still gets it wrong. Took me three infringements to figure that out. Hopefully it takes you fewer.
Making the switch
You don't need to throw away your records. The historical spreadsheet data stays useful — it's your evidence base if DVSA requests records going back more than what the card holds. Keep it. Just stop using it as your primary compliance tool going forward.
The setup takes about 20 minutes. You connect your tachograph data source, set your usual work pattern, and the app starts tracking from there. Transport managers get a separate view — they can see remaining hours per driver, download compliance, and approaching limits. No more arguing over who entered what in which column.
One thing worth knowing: the app doesn't replace your manual records obligation. If DVSA requests records, you still need to be able to produce them. What it does is make sure those records are accurate, current, and flagging issues before they become infringements rather than after.
That's the actual difference. Not features. Not interface. Just the difference between finding out you've run over your fortnightly limit before you move the truck, versus finding out at a roadside check three weeks later when the officer is already writing up the fixed penalty.
I know which version I prefer.
If you're tired of writing infringements into a notebook and arguing with your TM about where the hours went, ShiftOwt tracks EU 561 and WTD compliance automatically — £5.99/mo for drivers, agency pricing on request.
