How to Read a Tachograph Printout the Right Way

You've got the printout in front of you, the driver's already said “it should be fine”, and the clock is ticking before a DVSA visit. That's usually the moment a new compliance officer realises a tachograph sheet isn't just a strip of paper, it's an evidential record that can either support the day's work or expose the gaps.

A proper tachograph printout gives you the story of the shift in a form you can check quickly, but only if you read it in the right order. The symbols matter, yet the bigger risk is missing the identity fields, the date roll-over, the handwritten annotations, or the numbered data blocks that matter when calibration, faults, and annual test evidence come under scrutiny.

Table of Contents

• Sitting Down With a Printout for the First Time
• The Fixed Reading Order Every Operator Should Follow
• Decoding Activity Symbols on the Daily Graph
• Reading Speed Bands, Distance Totals and Odometer Reconciliation
• Reading the Numbered Data Blocks on a Vehicle-Unit Print
  • What each block is doing
• Common Reading Mistakes That Trigger Findings and Prohibitions
  • The mistakes that really matter
• Retention, Download Deadlines and Evidence Handling

Sitting Down With a Printout for the First Time

A curled strip of thermal paper never looks important until someone asks you to explain it. On the desk, it's usually beside a driver card, a binder of download reports, and a manager who wants a quick answer before the vehicle leaves the yard. That's when the unfamiliar layout starts to matter, because the sheet isn't a narrative, it's a sequence of machine-printed fields, activity bars, and checks that only make sense when you know what kind of printout you're holding.

A digital tachograph printout is usually narrow, with a header at the top, a timeline through the middle, and totals or event details lower down. The dot-matrix print can be faint, especially on older thermal paper, so a clean copy matters when the record is going to be reviewed later as evidence. GOV.UK explains that tachographs record driving time, speed, and distance, and that printout paper is the quickest compliant way to record periods in blocks when manual recording is needed. See the practical guidance on tacho rules and printout use.

Three artefacts get confused all the time. A daily driver card print shows what's on the card for a given day, a vehicle unit 24-hour print shows what the unit recorded for that vehicle, and an events and faults print is what you pull when you need the unit's error history. They're related, but they're not interchangeable, and inspectors do cross-reference them against downloaded data files rather than treating the paper alone as the full record.

Practical rule: if the paper, the card, and the download don't tell the same story, assume the discrepancy will be the first thing an examiner notices.

That's why how to read a tachograph printout starts with recognising the artefact before you even look at the symbols. For a new compliance officer, the job is to ask, “What is this sheet proving?” not “What does this icon mean?” Once that's clear, the reading order becomes much less intimidating.

The Fixed Reading Order Every Operator Should Follow

Start at the top and work down. That sounds obvious, but bottom-up reading is one of the easiest ways to miss the problem, especially when you're under pressure and the activity graph looks clean at a glance. The header fields tell you whether you're looking at the right driver, the right vehicle, and the right day, and that's the part too many people skip when they jump straight to the symbols.

The first check is identity. Confirm the date, time, driver surname or card number, vehicle registration, and vehicle unit details before you touch the timeline. GOV.UK says the driver's name, driver card number, or driving licence number must identify the person on digital printout paper, which is why the header isn't a formality, it's the link between the paper and the legal person behind it. The roadside logic is simple. If the header is wrong, everything below it becomes harder to rely on.

Next, read the activity timeline against the 24-hour clock. That's where driving, other work, availability, and rest are laid out in sequence, and where a card-swap or a missing insertion shows up as a gap or a mismatch. If you start in the middle, you can convince yourself a shift began later than it did, or that a break belongs to the wrong driver.

The last pass is the totals and fault area. Look at distance, odometer values, and any printed events or faults at the foot of the sheet. That is where the inspector checks whether the record is coherent, not just readable.

Read the header first, always. A clean graph with the wrong registration is still a bad record.

A useful habit is to annotate your own review in the same order every time. That keeps the office check aligned with the roadside check, and it stops you chasing the most visually obvious part of the sheet while missing the field that proves compliance.

Decoding Activity Symbols on the Daily Graph

The activity graph is where the process often begins, because it looks like the business end of the printout. It's also where people make their first mistake, which is to read the symbols like they're fixed to the wall clock instead of the driver's continuous in-car clock. The printout follows the tachograph's time line, not the driver's memory of when lunch happened.

Symbol	Meaning	Legal Category	Typical Scenario
Steering wheel	Driving	Driving time	Vehicle in motion on the road
Crossed spanner	Other work	Working time	Loading, paperwork, walkaround checks
Cot	Rest	Daily or weekly rest	Genuine off-duty rest period
Armchair	Availability / POA	Availability	Waiting when the delay is known
Hashed break	Break	Break time	Statutory break within driving limits

The key is to read the bars as a sequence, not isolated icons. A 30-minute break appears as a single hashed block within the driving limit window, and that matters because the break has to sit in the right place against the cumulative driving time. A later 45-minute break can be reflected as a full rest block, or split in a way that's still legible to the analyst, but only if the recording matches what happened.

A cross-day shift is where new readers get caught out. The date stamp changes at 00:00, so a single duty can run over midnight and still be one continuous shift, just split across two calendar days. If you're only looking for a neat day-by-day pattern, you can misread a lawful overnight run as two separate blocks or, worse, assume a rest happened when it didn't.

Manual entries need special care. When a driver adds a period by hand, the printout usually shows a thinner annotation line and the back of the printout should support it with the driver's own note. That's where the paper stops being a passive record and becomes a contemporaneous explanation.

For a practical refresher on symbol categories, the UK explanation at drivers' hours rules and activity modes is a useful companion when you're matching the legend to real shifts.

Reading Speed Bands, Distance Totals and Odometer Reconciliation

Once the timeline makes sense, the next question is whether the numbers hang together. The speed band underneath the activity graph is the simplest way to see whether the unit's movement record matches the day's driving pattern, but it's not a mirror of GPS. A tachograph records what the vehicle unit measured, so slight differences between the printout and other tracking systems don't automatically mean something is wrong.

The better check is reconciliation. Compare the distance total on the printout with the odometer reading recorded on the vehicle. When the two are close but not identical, the analyst looks for context rather than panic. A small discrepancy can come from calibration drift, tyre-size variation, or a driver-card issue that interrupted the continuity of the record.

Parameter	Recorded Value	Expected Range	Analyst Note
Shift distance	287 km	Close to odometer movement for the duty	Check against departure and arrival odometer readings
Odometer mismatch	1 km difference	Small variation may be explainable	Review calibration history and card continuity
Speed record	Activity-linked speed bands	Must fit the driving pattern	Look for suspicious gaps or impossible jumps
Pulse count context	K-factor data in the unit	The unit must stay within its programmed calibration data	If the pulse record and movement don't line up, treat it as a technical issue

That last point matters because the tachograph unit relies on K-factor calibration data, and the accepted range is 500 to 24,000 pulses per km. If the figures don't sit comfortably inside the unit's expected calibration profile, the question becomes technical very quickly. The printout is then less about what the driver did and more about whether the unit itself can be trusted.

In practice, a 1 km discrepancy by itself won't prove tampering. What it does is force you to ask whether the unit was calibrated properly, whether the tyres changed the effective rolling circumference, or whether a card swap broke the chain of attribution. That's the analyst's job, not the driver's excuse.

For depot systems that pull the underlying files rather than waiting for a paper copy, remote download handling is useful background because it shows how the printout fits into the wider digital record.

Reading the Numbered Data Blocks on a Vehicle-Unit Print

Most driver-facing guides stop at the symbols. That's where they miss the part that matters at annual test and during evidence review, the numbered data blocks buried in a vehicle-unit print. DVSA's memo on K-factor matching makes the point clearly, the important information sits inside blocks such as 01, 02, 03, and 04, and the recent 04 block should normally be the first one you check. The document is tucked away in a technical note, but it's exactly the kind of thing that saves time when the unit's calibration history is being challenged. See the DVSA memo on K-factor matching and data blocks.

What each block is doing

Block 01 identifies the vehicle. It carries the registration, approval mark, and vehicle identity data, so it ties the printout to the actual unit in the cab.

Block 02 identifies the card holders. That includes driver and co-driver details, and the issuing Member State where relevant.

Block 03 gives you calibration history. The last calibration date, odometer reading at calibration, and tyre-size parameters appear here.

Block 04 is the one that catches people out. It records the most recent events and faults stored in the unit, which is exactly why it matters during annual test and evidential review.

These blocks don't always appear in the same way on every print. A daily print might show one set of details, while an events or faults print brings out the block data more clearly. A technical data print can be the cleanest way to pull the calibration trail when you need to file it against a public inquiry bundle.

The filing habit matters as much as the read. Keep the printout with the download record, the workshop note, and any analyst comments, then cross-reference the date and unit serial number. If you only store the digital file, you can lose the manual note that explains why the print was taken in the first place.

Practical rule: block 04 tells you what the unit remembered, block 03 tells you when it was last set, and block 01 tells you which vehicle you're actually dealing with.

Common Reading Mistakes That Trigger Findings and Prohibitions

A printout usually goes wrong in the same places. The symbols are not the hard part, the reading discipline is. The first trap is midnight. A shift that crosses 00:00 can look like two separate days if you scan it too quickly, and that can create a rest period on paper that never existed in practice.

The second trap is the handwritten layer. If a driver has added a note on the back of the printout and that note does not line up with the vehicle unit record, the sheet stops supporting the story you want to tell. An inspector will not treat a contradiction as a helpful clarification. It becomes a credibility problem, especially if the note is meant to explain missing card use, a transfer, or a fault.

The mistakes that really matter

• Midnight roll-over misread: One continuous duty period is read as two separate records.
• Ignored manual note: A handwritten explanation is filed without checking it against the printout.
• Fault code left uninvestigated: The unit printed an event or fault, but nobody checked the cause.
• Card absence not questioned: Movement without a card is missed because the reader only watched the activity bar.
• Symbol anomaly dismissed: An odd symbol or gap is treated as harmless without review.

Those errors matter because they change what enforcement sees. A roadside examiner may treat an unexplained card issue as an hours problem, and an unresolved equipment fault can lead to an immediate prohibition. After the stop, a Driver and Vehicle Standards Officer can still raise the issue in writing if the file shows a pattern of poor review.

A good compliance file treats the printout as evidence, not a summary sheet. Analyst-reviewed handling matters here. Keep the sheet with the download record, the workshop note, and any review comments, then cross-reference the date and unit serial number so the record stays defensible when someone asks which vehicle you're dealing with.

That is why how to read a tachograph printout has to cover the ugly bits as well as the legend. A tidy sheet can still be weak evidence if nobody checked the fault line, the date stamp, or the annotation trail.

Retention, Download Deadlines and Evidence Handling

A printout only becomes defensible evidence when the rest of the handling chain is disciplined. The operational rhythm is straightforward, even if fleets don't always follow it well. Driver card data should be downloaded every 28 days, vehicle unit data every 90 days, and both should be retained for at least 12 months. For roadside production, drivers need the current day's record plus the previous 28 days in scope, and the newer UK production wording refers to 56 days where that wider period applies. Those numbers belong together because they control both what the driver can produce at the kerbside and what the office must store for later review.

The cleanest systems treat the paper as part of a wider evidence pack. A scanned printout bundle with hash verification, a dated sign-off log, and analyst review notes all help turn thermal paper into something a DVSA examiner can follow without guesswork. That matters most where the paper carries a manual note, because the note is often the only explanation for a missing card, a brief fault, or a transfer from one vehicle to another.

The gap I see most often is simple. Operators keep the downloaded file and bin the paper. That saves space, but it destroys the annotation history that explains why the sheet was printed in the first place. If a driver adds a reason on the back, that note needs to stay attached to the record.

A practical chain of custody should include who printed the sheet, who checked it, who signed it off, and where the copy was stored. If a roadside printout is challenged, keep the depot copy, keep the witness details, and escalate the issue through the transport manager rather than letting the sheet drift into an unlabeled file. For a fuller view of the