Digital HGV walkaround check records: what DVSA wants to see

This post in 30 seconds.

• The rule: a defect report is part of the vehicle's maintenance record and has to be kept for at least 15 months, with the assessment, the rectification work and the repairer. Electronic records are explicitly acceptable.
• The gap: a tick in a box proves a sheet was filled in. It does not tell the workshop what the crack looks like, how big it is, or where on the trailer it sits.
• The loop that gets audited: DVSA's earned recognition scheme measures whether reported road safety defects were actioned, not whether checks were logged.
• Who this is for: transport managers, compliance managers and fleet engineers running an O-licence operation in the UK and Ireland. Not for anyone looking for a free check sheet to print.

The defect book lives in the cab. It gets rained on, sat on, and filled in at 04:50 by a driver who wants to be on the A1 by five.

Three weeks later a DVSA examiner asks to see the walkaround records for one tractor unit and its trailer. Somebody starts going through a crate in the transport office.

Nothing in that story is unusual and nothing in it is illegal. The check may well have been done properly every single morning. The problem is that the operator cannot prove it quickly, and cannot show what happened next.

This post is about the record, not the app market. What the driver actually has to do before the vehicle moves, what the report has to contain, how long you keep it, what a photograph adds that a tick cannot, how the defect reaches the fitter, and what somebody looks for when they audit you.

Transport managers carry the undertakings personally, which is why "the check was done, I'm sure of it" is such an uncomfortable sentence at a public inquiry. We build Venta Capture, VentaVid's guided capture product, so the person standing at the vehicle can record what they found properly, first time. See how a guided defect report works, then judge it against your own check regime.

In this post:

• What the driver has to do before the vehicle moves
• What the record has to contain, field by field
• Nil defect reporting, and why a clean year is a problem
• What a photo adds that a tick box cannot
• How the defect gets from the gate to the workshop
• What an audit or a public inquiry looks for
• Moving off the paper pad without breaking the check

What the driver has to do before the vehicle moves

The duty sits before first use, not at the end of the shift, and it sits on a named person who has to be competent to do it. DVSA's Guide to Maintaining Roadworthiness, updated in April 2025, puts it plainly: "A driver or responsible person must conduct a walkaround check of a vehicle prior to using the equipment on the public highway."

Two more lines from the same guide matter operationally:

• Frequency. "At least one walkaround check should be carried out in every 24-hour period that the vehicle is in service."
• Scope. The check "should cover the whole vehicle or combination and include all interior and exterior items that can be safely assessed without the use of a workshop." Combination means the trailer too, every time it is coupled.

The HGV daily walkaround check itself is well documented. DVSA's guidance on carrying out daily HGV walkaround checks runs from inside the cab (front view, wipers and washers, dashboard warning lights, steering, horn, brakes and air build-up, height marker, seatbelts) to the outside items every transport manager can recite: lights and indicators, leaks, security of body and wings, tyres and wheel fixing, brake lines and the trailer parking brake, electrical connections, coupling security, security of load, number plate, reflectors, markings and warning plates.

What drivers have to report is broader than most defect books suggest. The guide says "any defects, or symptoms of defects, that could prevent the safe operation of the vehicles." Symptoms. A noise, a pull to one side, a warning lamp that came on yesterday and went off again.

And one line is worth reading aloud at a toolbox talk, because it is the one operators lose on: "It is important that enough time is allowed for the completion of walkaround checks." A fifteen-minute pre-start window that everybody knows takes twenty-five minutes is not a records problem. It is a rota problem that shows up in your records.

What the record has to contain, field by field

Most digital check tools stop at the tick. The guide does not: it is specific about what a defect report has to record, and it lists eight things.

Reading that section of the guide again for this piece, the thing that stands out is how much of the record gets written after the driver has gone. Four of the eight fields are filled in by somebody else, after the check is over. A walkaround record is not a snapshot of a morning, it is a small case file that stays open until the work is signed off. That is the single biggest reason paper struggles: the sheet that records the defect and the job card that records the fix live in different places, and only one of them is easy to find.

On how long you keep it, the guide splits the two cases and the split is worth getting right:

• A report listing defects "is part of the vehicle's maintenance record and must be kept for at least 15 months, together with details of any assessment, the rectification work and repairer."
• Nil defect reports are treated as good practice rather than a 15 month obligation, which is why most operators settle on a shorter retention for them and keep the defect reports for the full period.
• Electronic records are dealt with in one sentence that removes the usual objection: "Electronic records of reported defects are acceptable and must be available for 15 months."

Available is the load-bearing word. Not stored somewhere. Available, to somebody who asks, for the whole period. If your retention policy purges media at 12 months, a digital system will fail this quietly and you will not find out until an examiner asks. Set data retention deliberately, per record type, and write down why.

The guide also says where the report has to go: "All drivers' defect reports must be given to a responsible person with sufficient authority to ensure that any appropriate action is taken." A shared mailbox is not a person with authority. Neither is a folder.

Nil defect reporting, and why a clean year is a problem

Nil reporting is the part of the driver daily defect report that people either skip or over-engineer. DVSA's position is that it is useful precisely because it proves the check happened: "It is good practice to complete and retain 'nil' defect reports as they are a useful means of checking that drivers are carrying out their duties and these forms can be used for audit purposes." The driver-facing guidance is blunter still. "Record 'nil' defects if you do not find any."

So a nil report is a positive statement, not an absence of one. It says a named person looked at this vehicle on this date and found nothing.

Which leads to the pattern every auditor knows. A fleet whose walkaround records are one hundred percent nil, month after month, has not found a way to run perfect vehicles. It has found a way to stop reporting. Compare your own nil rate against two other numbers you already have: defects found at safety inspection, and prohibitions or advisories picked up at the roadside. If the vehicles are generating findings at PMI that the drivers never raised, the check is being signed rather than done.

For a sense of how often something is genuinely there to find, DVSA's own vehicle enforcement data for Great Britain records 3,213 HGV mechanical checks in Great Britain in the April to June 2025 quarter, resulting in 899 mechanical prohibitions. That is a 27.98% prohibition rate.

Be honest about what that number is and isn't. DVSA targets its stops using intelligence and risk scoring, so this is not a random sample of the national parc and it does not mean a quarter of British lorries are unroadworthy. It does mean that when an examiner has reason to look, there is something to find more often than not, and most of what they find is on the walkaround list: tyres, lights, brakes, body security.

If your drivers are returning nil every day on vehicles in that population, the question is not whether you have a paperwork problem.

Getting a driver to raise something small takes about four seconds of friction removed. Have a look at Venta Capture if the reporting step is where your check regime keeps failing.

What a photo adds that a tick box cannot

A tick box answers one question: was this item acceptable, yes or no. Useful. It just is not enough for anything downstream.

Think about what happens after a driver writes "damage to nearside curtain" in a book. The fitter learns that something is wrong with a curtain. They do not learn:

• How bad. A scuff, a tear you could put an arm through, or a rail pulled out of the top.
• Where exactly. Third pillar back, low, near the load bar, or right across the buckle line.
• How big. A phone next to the tear, or a hand, settles it. A description never does.
• What is around it. The strap that caused it, the corner of the pallet that moved, the kerb mark on the trailer skirt.
• Whether it moved. A defect noted yesterday and a defect that is worse today are different jobs.
• Whether it is safe to run. A defect classification call is far easier to make from a picture than a phrase.

That last one is where the money and the risk both sit. The driver is "always legally responsible for the condition of the vehicle while in use", in the guide's words, but the driver is not the person deciding whether the unit runs. A transport manager making that call from a text message is guessing. Making it from three photographs and twenty seconds of the driver talking over the damage is a judgement.

There is a second thing a picture does, quietly, and it matters at audit. It is evidence that somebody was physically at the vehicle. A timestamped photo recorded in the session, rather than picked out of a gallery, is a far better answer to "how do you know the check was done" than a signature that could have been written anywhere.

One caution, because this gets oversold in this market. A server-verified receipt time proves when the record arrived with you. It does not prove when the damage happened. Say that out loud in your own documentation and you will never be caught overclaiming it in front of an examiner.

How the defect gets from the gate to the workshop

This is the bit that decides whether digitising the check was worth anything. Recording the defect faster is pleasant. Closing it faster is the thing you get audited on.

DVSA's earned recognition scheme is the clearest published statement of what "good" means here, and it is worth reading even if you never intend to join. Four maintenance KPIs are monitored across 4-week reporting periods, and the fourth one is the whole argument of this post:

M4: driver defect reports where road safety related items have been reported are appropriately actioned.

Key performance indicator: 100%. The scheme's own explanation adds that "it is up to the operator to decide what is safety related and what is the most appropriate action, this will be checked during the periodic audit."

Note what is being measured. It is not how many checks were completed, or how quick the app is. It is whether the reported safety defects were actioned, provably, every time. For fleets of 20 vehicles or fewer including trailers, the scheme sets the bar at no more than one breach in a reporting period.

So design the chain backwards from that. A defect report should carry:

• An owner, not an inbox. Assign it to the named responsible person the guide requires, with escalation to a manager when nobody picks it up.
• A status that means something. Reported, assessed, VOR, awaiting parts, rectified, signed off. Define them once, for the whole fleet.
• A clock. A response time on the route, so an overnight report on a safety-critical item is visibly late rather than invisibly late.
• A way for the fitter to see it without a login. Subcontract fitters and mobile techs will not create accounts. A view link on a phone puts the photos and the driver's words in front of them.
• The rectification written back onto the same record. Otherwise you have two files and the eight fields never sit together.
• An audit trail nobody has to assemble. Who opened it, who assessed it, who signed it off, and when.

In Venta Capture the submission arrives as a case rather than a folder of photos: your own reference format, plus a separate field for the job number your fleet system already issued, every answer stored as a structured field, and the driver's spoken explanation transcribed into searchable text. Statuses, assignment, escalation with a reason and routing with a response time in hours are configured per operation, and workflow automation forwards cases onward by status. Webhooks and the API push the record into your fleet maintenance or planning system so the job card and the evidence travel together.

Where a report is incomplete, a retake request names the missing step and goes back to the driver in one click, and the new material links to the original case rather than starting a fresh one. The review and retake loop is what stops a half-finished report becoming a hole in the record 14 months later.

Say the honest thing here, because your auditor will. None of this makes an operation compliant. It produces the record that lets you show what you did. The undertaking on the licence is yours, the assessment of the defect is a competent person's, and the decision to run or not run a vehicle stays with people.

What an audit or a public inquiry looks for

The obligation traces back to a single sentence of statute. Section 13C(4) of the Goods Vehicles (Licensing of Operators) Act 1995 requires "satisfactory facilities and arrangements for maintaining the vehicles used under the licence in a fit and serviceable condition", quoted in the DVSA guide. Everything else is evidence about whether that sentence is true of your operation.

When somebody tests it, whether that is a DVSA maintenance investigation or a traffic commissioner calling an operator and a transport manager to public inquiry, the questions are consistent:

1. Can you produce the records at all, for the period asked for? Fifteen months of defect reports, for the vehicles named, without a crate.
2. Do the walkaround records reconcile with the vehicle's life? Against safety inspection sheets, brake test results, annual test history, VOR and any roadside encounters.
3. Were reported defects actioned, and how fast? Report to assessment to rectification to sign-off, with dates.
4. Is anything suspiciously tidy? Identical times, identical handwriting across drivers, a nil rate no fleet achieves, sheets completed in advance.
5. Who is the responsible person, and did the reports reach them? Names, not roles.
6. What changed after the last finding? A transport manager who can show the dated change they made after the previous audit is in a different conversation from one who cannot.

Traffic commissioners have real powers here, including curtailing, suspending or revoking a licence and taking action against a transport manager's repute. It is not the place for a sentence beginning "we've always done it, we just don't write it down."

There is a quieter benefit to a dated, structured record that nobody puts in the brochure. It protects the driver. When a prohibition is issued for something that genuinely appeared mid-journey, a report filed at 05:12 that morning showing the item clear, with a photograph, is the difference between a defensible position and an argument.

Ireland: the same check, a longer retention

If you run under an Irish licence, the shape is the same and two numbers are different. The RSA's guidance on daily walkaround checks says the check may be carried out by "any person trained to conduct such checks (including: drivers or mechanics)" and that it happens "before the vehicle is used on a public road."

For each defect, the record must carry the description of the defect, the time and date it was discovered, and any temporary measure taken to mitigate it. That third field is one GB operators often do not capture at all.

On retention, the CVRT record keeping requirements are longer than the GB rule: records covering defects reported or discovered and when they were rectified, including by whom, "must be retained for at least two (2) years after their creation." Electronic is explicitly fine there too: "The recording system can be paper based or an electronic one."

If you run vehicles on both sides of the Irish Sea, set your retention to the longer of the two and stop thinking about it.

Moving off the paper pad without breaking the check

The failure mode when operators digitise a walkaround is not technical. It is that the new flow takes longer than the pad, so drivers start completing it in the cab at the end of the shift, and you have swapped a scruffy true record for a tidy false one.

Design for the four minutes the driver actually has. Here is a flow that works as a first standard build, in the order a driver walks the vehicle.

1. Identify the vehicle by scanning, not typing. A QR code in the cab or on the trailer headboard, on a sticker or on a screen, opens the flow already tied to that unit. A scan step with a torch and a manual-entry fallback covers a dark yard at five in the morning.
2. Confirm the driver. Name and driver number. The report has to be attributable to a person.
3. Confirm the combination. Trailer number, and whether it was coupled this morning. This one field stops the most common records gap of all.
4. Run the interior items as a short checklist. Warning lights, steering, horn, brakes and air build-up, wipers and washers, mirrors and glass, height marker, seatbelts. Yes or no, with an optional note.
5. Run the exterior items in walking order. Nearside, rear, offside, front, so the sequence matches the walk rather than a form designer's list.
6. Branch on any "no". A failed item opens a photo slot with an example photo and a one-line instruction, and a free-text box, rather than making every driver photograph everything.
7. Ask for scale on damage. A hand, a tape, a phone next to the tear. Trivial to ask for, impossible to add later.
8. Offer twenty seconds of video with the driver talking. "Point at it and tell us what you can see and hear." Spoken explanations get transcribed and become searchable text on the case, which is worth more at audit than most people expect.
9. Ask the two questions that drive routing. Is the vehicle safe to move, and has the vehicle been immobilised. A "no" on the first should route straight to the duty manager, not into a queue.
10. Nil declaration if nothing was found. An explicit "I carried out the check and found no defects", with the driver's name and the time, not an empty form.
11. Submit, with a reference number the driver can quote. The thank-you page shows it and the driver can screenshot it on the way to the cab.

The mechanics behind steps 1, 6 and 8 are covered on the guided video capture and request video by link pages, and the general idea behind step 6 is what we mean by guided capture: the organisation decides what gets recorded and in what order, so the right evidence comes back the first time.

Four things not to do

• Don't make every driver photograph all 27 items. You will get 27 useless pictures and a check that takes twenty minutes. Photographs belong on the exceptions.
• Don't let the app become the assessment. Software can classify nothing. A competent person assesses the defect, and the record should show who that was.
• Don't run paper and digital side by side for six months. Two systems means the defect that matters lands in whichever one nobody is watching. Pick a depot, switch it fully, then move on.
• Don't build the branching and the routing yourself on day one. A standard flow comes ready-made and your own team adjusts steps, slots and wording. Conditional routing, escalation rules and the link into your fleet system are set up around your process by VentaVid, scoped on a call.

One practical note on the phone in the driver's hand. The flow runs in the mobile browser with no app to install and no account to create, in the driver's own language, which is most of the reason agency and subcontract drivers actually complete it. Check it in your worst yard for signal before you roll it out across the fleet, because a submission still has to leave the phone.

Want to run one depot through this before committing the fleet? Take a look at Venta Capture and build the defect branch first.

Yard plant has its own version of the pre-use check, set out in forklift daily check records, and the rules for making a defect photo count are in photo evidence for inspections.

Frequently asked questions

Are digital HGV walkaround check records legally acceptable?

Yes. The DVSA Guide to Maintaining Roadworthiness says directly that "electronic records of reported defects are acceptable and must be available for 15 months." The format is not the test. Whether the record contains the required fields, is attributable to a person, and can be produced when asked, is the test.

How long do I have to keep walkaround check records?

In Great Britain, any report listing defects must be kept for at least 15 months, together with the assessment, the rectification work and the repairer. Nil defect reports are treated as good practice rather than a 15 month obligation, so most operators keep them for a shorter period. In Ireland the equivalent maintenance records must be kept for at least two years.

Do drivers have to record nil defects?

DVSA's driver guidance says to record nil defects if you do not find any, and the Guide to Maintaining Roadworthiness describes nil reports as a useful way of checking that drivers are carrying out their duties. Treat a nil report as a positive statement that a named person checked the vehicle and found nothing, not as an empty form.

Does a photo timestamp prove when the damage happened?

No. A server-verified receipt time proves when the record reached you, which is a useful and defensible fact in its own right. What caused the damage and when it occurred is established by the photos, the driver's account and whatever investigation follows.

Does software make our O-licence compliant?

No, and be careful with anyone who implies otherwise. The undertakings sit with the operator and the transport manager, the assessment of a defect sits with a competent person, and the decision to run or stop a vehicle sits with people. Software produces the record and moves it to the right person quickly.

What does DVSA earned recognition actually measure on defects?

KPI M4 measures whether driver defect reports involving road safety related items were appropriately actioned, against a key performance indicator of 100% across 4-week reporting periods. The scheme leaves it to the operator to decide what counts as safety related and what the appropriate action is, and checks that judgement at the periodic audit.

How does a digital defect report reach our fleet maintenance system?

Each case carries your own reference format plus a separate field for the job or works order number your system already issued, and the answers arrive as structured fields rather than a block of text. From there you can share a view link with a fitter who has no login, copy the case into your CRM, or use webhooks and the API to push it into your maintenance or planning system. Conditional routing and system integrations are set up around your process on a scoping call.

Start with one depot, one vehicle type

If your walkaround records live in a crate and your defect close-outs live somewhere else, the fix is not a bigger crate. Pick one depot and one vehicle type, write down the eight fields the guide requires, and build the flow that collects them in the order a driver walks the vehicle.

What it takes to start.

• Free plan, no credit card. Build the flow, run it on your own yard, then put it in front of a driver.
• Live in 10 minutes for a first standard flow. Stuck? Book a free setup call and we build it with you.
• Everything goes out in your own branding, in the driver's own language, with no app to install.

The VentaVid team builds Venta Capture and runs the free setup call on your own check regime.

See Venta Capture on your walkaround check

Or start for free and build the defect branch this afternoon. If you would rather see it against your own O-licence records first, book a demo and bring last month's defect reports.