If you are responsible for an O-licence, the best way to record HGV repairs is the method that lets you prove, quickly and clearly, what was reported, what was inspected, what decision was made, what work was done, who signed it off, and why the vehicle was considered fit to return to service. That matters more than whether the record started on paper, in Excel, or in software.
For a small fleet, paper can still work if the discipline is excellent. For a growing fleet, it usually breaks at the same points. Defect reports go missing. Job cards do not match the original defect. A PMI finds something that was “done last time”, but nobody can show when, by whom, or with what parts. That is where operators get into trouble. Not because they repaired the vehicle, but because they cannot evidence the repair properly when DVSA asks.
What DVSA needs your repair records to prove
When DVSA looks at maintenance records, it is not admiring your filing system. It is testing whether your vehicles are being kept in a fit and serviceable condition, and whether your systems actually control roadworthiness.
Your repair records need to show a chain of decisions. In practice, that means being able to produce:
- the reported defect, whether from a driver walkaround check, workshop inspection, PMI, MOT preparation, roadside issue, or breakdown
- the date and time it was identified
- the vehicle and trailer registration or fleet number
- what assessment was made
- whether the defect made the vehicle unroadworthy, or whether it was safe to move under control to a workshop
- what repair was authorised and carried out
- who carried out the work
- what date the work was completed
- who checked or signed off the repair
- when the vehicle returned to service
That is the level that stands up when records are examined after a prohibition, a follow-up investigation, or a visit linked to OCRS concerns.
It also needs to be consistent with the rest of your maintenance file. If a driver defect report says “NSF brake binding”, and the job card says “adjusted brakes”, but the next PMI still records uneven braking, you have a story to explain. If a vehicle fails MOT on a component that your records show was repaired and checked days earlier, DVSA will want to know whether the repair was ineffective, whether the check was poor, or whether the record was not true.
For UK operators, this is tied directly to the undertakings on the O-licence. You must have an effective system for reporting and recording defects, and for keeping vehicles and trailers fit and serviceable. In an EU context the broad maintenance duty is familiar, but the operator licensing structure, and the way the Traffic Commissioner can examine maintenance systems, is specific to Great Britain. That is why record quality matters so much here.
A good repair record also shows judgement, not just activity. If a defect was deferred, there should be a reason. If a vehicle was taken off the road, that should be clear. If a repair was temporary pending parts, there must be control around that decision. “Will monitor” is not a maintenance system.
If you want a wider list of what should be ready when records are called for, our guide to records to have ready for a DVSA O-licence audit sets that out in more detail.
Paper defect books and job cards
Paper still has one advantage. It is easy to start. A driver can fill in a defect book in the cab. A fitter can write up a job card at the bench. A workshop controller can put both in a tray and feel that the vehicle has a history.
For a very small operation, with one site, a handful of vehicles, and the same people handling defects every day, paper can still do the job. If every defect report is dated, legible, signed, matched to a repair document, and filed against the vehicle, you can maintain a usable trail.
The problem is not that paper is invalid. The problem is that paper depends on habits that usually weaken as the fleet grows.
What tends to go missing when a vehicle history is checked?
- the original driver defect sheet
- the note showing who decided the vehicle could keep running
- the job card for the actual repair
- the parts detail
- the sign-off after the repair
- the link between a PMI finding and the later rectification
- the evidence that a nil defect report was reviewed, not just collected
Paper also fails quietly. A page tears out. A fitter writes “done” with no detail. A defect is copied from one sheet to another and the dates stop making sense. A trailer swaps depots and the folder stays behind. Nobody notices until there is a DVSA encounter, an MOT failure, or a public inquiry letter.
We see another common problem in mixed workshop setups. The transport office keeps defect books. The workshop keeps job cards. The invoice system holds parts. If the vehicle is maintained externally, the dealer has some records too. On the day someone needs the full story, there are four partial stories instead.
Paper can still be useful at the point of work. Plenty of workshops like a printed sheet in the cab or on the dash while a vehicle is being inspected. But if paper is your master record, you need a very disciplined filing process and someone responsible for checking that every defect has an outcome. Most operators underestimate how much admin that takes.
Spreadsheets shared across the office and workshop
Spreadsheets are usually the next step after paper starts to hurt. They give more visibility. You can sort by registration, date, defect type, workshop status, or outstanding work. You can share them across the office and workshop. For a while, they feel like control.
Compared with paper, spreadsheets are better at:
- seeing open defects in one place
- checking whether repairs are overdue
- spotting repeat issues on the same vehicle
- giving the transport manager a quick view without opening files
- tracking PMI outcomes and bookings
That is why many fleets between five and twenty vehicles end up there.
But spreadsheets have hard limits, and those limits matter for O-licence risk.
First, consistency. One person writes “OSR lamp inop”. Another writes “rear marker light out”. A third writes “lighting”. You cannot search or report properly because the data is not standardised.
Second, audit trail. A spreadsheet rarely tells you enough about who changed what, when, and why. If a status moves from “VOR” to “complete”, can you show who made that decision? Can you show whether the repair was actually signed off, or whether someone just updated a cell to clear the list?
Third, attachments. A repair record without the actual documents behind it is thin. You need the defect sheet, the inspection sheet, photos where relevant, outside repair invoices, and sometimes supporting documents such as tachograph calibration records if related work was done. Spreadsheets can point to files, but they are poor at holding a complete vehicle history together.
Fourth, version control. Shared spreadsheets are notorious for duplicate copies, broken formulas, overwritten rows, and separate depot versions. One office copy says the repair is done. The workshop copy says waiting for parts. Neither one is a reliable legal record.
Fifth, scale. Once you have enough vehicles, enough trailers, enough PMIs, and enough defects moving at once, a spreadsheet becomes a list manager, not a repair record system. It tells you that something happened, but not the full maintenance story behind it.
That is usually the point where operators start looking for the best way to record HGV repairs for operator licence purposes, not because they want software for its own sake, but because they need records that hold up under scrutiny. We covered that crossover point in our piece on small-fleet maintenance records without spreadsheet risk.
Workshop software built around repair records
Proper maintenance software does something paper and spreadsheets struggle to do. It links the whole chain together in one place.
That means a defect can start as a driver report, become a workshop job, pull through parts and labour, carry notes from the fitter, and end with a sign-off that shows who returned the vehicle to service. If the defect came from a PMI, the rectification sits against that inspection. If it was a repeat issue, the history is visible.
That sounds simple. In practice, it is the difference between “we repaired it” and “here is the exact record”.
A workshop-led system should let you:
- create a repair record against the exact vehicle or trailer
- categorise the source, driver defect, PMI, preventative maintenance inspection, MOT prep, roadside issue, breakdown, warranty, recall
- record defect severity and operating decision
- assign work to a fitter or contractor
- record parts used and labour time
- attach photos, documents, invoices and inspection sheets
- hold the repair open while waiting for parts, without losing visibility
- require sign-off before the vehicle is shown as back in service
- keep a full history by vehicle and by defect type
That matters on the workshop floor as much as it does in an investigation. Fitters need to know whether they are dealing with a one-off lamp failure or the third repeat wiring issue in six weeks. The transport office needs to know whether a vehicle is genuinely available or still awaiting a safety-critical part. The person named on the O-licence needs to know whether nil defects, PMI outcomes, and repairs are actually being closed properly.
Good software also helps with the awkward areas that brochures tend to skate over. Subcontracted repairs, for example. If an outside workshop does the work, you still need your own record to show what was reported, what was authorised, what evidence came back, and who accepted the vehicle back into service. Uploading an invoice alone is not enough.
The same applies where a repair decision overlaps with compliance records. A wheel-end issue may connect to a roadside prohibition. A dashboard warning may lead to a tachograph fault investigation. A PMI advisory may become a monitored item at the next inspection. If your records live in separate places with no link, the real picture gets lost.
This is exactly why we built Operator Compliance Software from a working HGV workshop. We needed records that made sense to fitters and transport managers, not software that looked neat in a demo but fell apart when a vehicle came in with three defects, two parts on back order, and a PMI due on Friday.
Which method is best for a five to 100 vehicle fleet?
For five vehicles, paper can still be enough, if your workshop is simple, your filing is disciplined, and one person checks every defect through to completion. That is a big if, but it can work.
From around that point upward, spreadsheets often become the bridge method. They are cheap, familiar, and better than disconnected paper. If your fleet is stable, your workshop is in-house, and your defect volume is modest, a spreadsheet may hold for a while.
The problem is not fleet size on its own. It is complexity.
A ten-vehicle fleet can outgrow spreadsheets quickly if:
- vehicles work long hours and defects come in daily
- trailers are added to the mix
- more than one depot is involved
- outside workshops do some of the maintenance
- different people report, approve and repair defects
- the same person is carrying transport compliance and workshop admin
- OCRS pressure means records need to be produced fast and cleanly
A thirty-vehicle fleet with one workshop controller and two fitters usually needs something stronger than Excel, even if nobody has admitted it yet. A hundred-vehicle fleet definitely does, unless it wants a full-time exercise in chasing paperwork.
So which method is best?
Paper is best only where the operation is genuinely small, local, and controlled.
Spreadsheets are best as a short-term step up from paper, not as the end state for a growing fleet.
Software is best where the repair record needs to be complete, searchable, and auditable without relying on one person’s memory.
That is the practical answer for most operators between five and 100 vehicles. Not because software is fashionable, but because the admin load and the risk of missing links become too high otherwise. If you are weighing up options, our guide to choosing maintenance records software for your O-licence goes into the trade-offs in plain terms.
What a good repair record looks like in practice
A good repair record is not a vague note saying “fixed in workshop”. It is specific enough that someone who was not there can understand what happened and why the vehicle was considered safe afterward.
At minimum, each repair record should include:
- vehicle registration, trailer number, fleet number, and odometer reading if relevant
- date and time defect was reported
- source of defect, driver report, PMI, preventative maintenance inspection, MOT prep, roadside stop, breakdown, workshop finding
- defect description in plain language
- defect category or system, brakes, steering, tyres, lights, suspension, body, emissions, tachograph, coupling, etc
- severity or operating status, safe to use, restricted use, VOR
- person reporting the defect
- person assessing it
- decision made, including any temporary control
- work carried out
- parts fitted
- labour recorded
- date and time repair completed
- fitter or contractor who completed the work
- sign-off by a competent person
- date and time returned to service
The attachments matter too. A solid record will often include:
- scanned or digital driver defect report
- job card
- PMI sheet where the defect arose from inspection
- photos, especially for tyre, body, load security, lighting, or accident damage issues
- outside workshop invoice or worksheet
- supplier paperwork for key replaced components where relevant
- any follow-up note if the issue is to be rechecked at a later date
Status control is where many systems fail. A record should not move to “complete” just because work has started. It should move through clear stages, such as reported, assessed, in repair, waiting parts, ready for check, signed off, returned to service. That way, nobody mistakes workshop activity for a finished safety repair.
You also need enough detail to deal with repeat faults. “Nearside front ABS issue repaired” tells you very little. “NSF ABS sensor wiring chafed on bracket, loom repaired and secured, fault codes cleared, road test completed” is useful. If the same issue returns, you have something to compare.
Another point often missed is linking the repair back to the original trigger. If a PMI notes brake imbalance, the rectification should sit against that PMI outcome. If a roadside check raises a tyre issue, the repair should link to that event. If a driver reports a steering pull and the workshop finds a suspension bush failure, both the report and the finding should remain visible. That is what makes the record credible.
Finally, a good repair record supports a simple question. If DVSA, the Traffic Commissioner, or your own maintenance provider asked tomorrow, “Why did you let this vehicle back on the road?”, could you answer from the record alone?
If the answer is yes, your system is doing its job.
If the answer depends on who happens to remember it, it is not.
For most fleets, the best way to record HGV repairs for operator licence purposes is the method that keeps that full chain intact every time, not just when everybody is on site and the week has gone well. That is why workshop-led records beat improvised admin systems in the long run. They are better for roadworthiness, better for control, and much safer for your O-licence.
Do I have to keep HGV repair records for my O-licence?
You need maintenance records that show how defects were identified, assessed and dealt with. Repair records are part of that picture and help demonstrate roadworthiness if DVSA asks to see evidence.
Are paper records acceptable to DVSA?
Yes, paper records can be acceptable if they are complete, legible and easy to retrieve. The problem is usually not legality. It is missing pages, weak follow-up and poor visibility across the fleet.
Is a spreadsheet enough for defect and repair tracking?
It can be for a smaller operation with disciplined staff. But spreadsheets are weak at attachments, timestamps, version control and linking one defect to inspection findings, parts used and final sign-off.
What should a repair record include?
At minimum, record the vehicle, date, reported defect, who found it, assessment, work done, parts fitted, who completed the repair, and whether the vehicle was safe to return to service.
Should repair records link to PMI records?
Yes. If a defect is found during a preventative maintenance inspection, the repair record should connect back to that PMI so you can show what was found, what was done and when it was cleared.
