Roadside breakdowns without compliance gaps

A roadside breakdown becomes a compliance issue the moment the driver stops. The commercial pressure is always to get the vehicle moving, protect the load, reassure the customer and recover the route. That is all real, but for an operator licence holder the paper trail matters just as much. If the records are weak, a simple mechanical failure can turn into questions about maintenance control, driver reporting, tachograph accuracy and whether the vehicle was put back into service without proper evidence.

The safest approach is to treat every breakdown as an incident that needs one complete file. That file should show what the driver found, who was told, what repair was carried out, what checks were made before the vehicle moved again, how the driver recorded time, and what happened if DVSA became involved. That is the practical standard for compliance after an HGV roadside breakdown, and the same discipline helps van fleets, buses and coaches as well.

What must be recorded as soon as the breakdown happens

The first record is the driver’s defect report. If the fault appears during the shift, the driver should report it as soon as it is safe to do so, not just at the end of the day. In UK operator licensing terms, that report is part of the evidence that the driver identified a defect and the operator took action.

At minimum, we want the driver to record:

• date and time of breakdown
• exact location, or the nearest safe and identifiable location
• registration number, trailer number if relevant, and fleet number
• driver name
• a clear description of the symptoms, not just “broken down”
• whether any warning lights appeared
• whether the vehicle was immobilised, limped to a safe place, or recovered
• whether the load, passengers or temperature-controlled goods were affected
• whether police, National Highways, recovery or DVSA attended
• whether the vehicle was declared VOR

That report should be separate from any casual phone call or messaging thread. A transport manager needs a formal defect entry that can be filed against the vehicle and, where relevant, the trailer. If the driver has already completed a daily walk-round check, the new defect should still be entered as an in-service defect. It is not enough to rely on the fact that the defect was not present earlier in the day.

Who needs to be told depends on the operation, but the minimum internal chain is usually the transport office or duty manager, the person controlling maintenance, and the customer-facing team if the route, load or service is affected. If the vehicle is hired, leased or under an external maintenance contract, the relevant provider should also be notified without delay. If the breakdown affects insurance, roadside assistance entitlement or vehicle identity checks, operators may also need access to policy and vehicle data, and some fleets cross-check records through askMID with the Motor Insurers' Bureau, or MIB, when dealing with incidents and third-party attendance.

If the defect has obvious road safety implications, the instruction to the driver should be clear. Do not continue unless the vehicle can lawfully and safely move. That sounds obvious, but many compliance problems begin with an informal judgement that the vehicle is “probably alright for a few miles”.

How to document roadside repairs by a third party

A roadside repair done by a third party is only compliant if the operator can show what was found, what was done, and why the vehicle was considered fit to move afterwards. A verbal assurance from the mechanic is not enough on its own.

We expect the roadside repairer to provide evidence that includes:

• the repairer’s business name
• date, time and location of attendance
• vehicle and trailer identification
• reported defect
• diagnosis
• work carried out
• parts fitted, if any
• any limitation on use, such as “return to depot only” or “temporary repair”
• the name or signature of the person who carried out the repair

If the repair was temporary, the paperwork should say so. Temporary repairs are one of the main areas where compliance gaps appear. A hose clipped, wiring insulated, an airline patched, or a wheel-end issue made mobile enough for recovery may be enough to reach base, but not enough to return the vehicle to normal service. The maintenance file needs to show that the temporary roadside action was followed by proper workshop rectification.

Rectification should then be signed off by the operator’s authorised person. In practice that may be the fitter, workshop controller, maintenance provider or transport manager, depending on how the maintenance system is structured. The key point is that the operator accepts responsibility for recording that the defect was rectified, not merely that somebody attended.

That paperwork should be added to the vehicle’s maintenance history with the same discipline as a safety inspection record. It should sit with the defect report, repair invoice or worksheet, any recovery note, and any follow-up workshop inspection. If a trailer was involved, the trailer file should also contain the documents. If the defect affected a safety inspection schedule, note whether the planned inspection interval was preserved or whether an additional inspection was carried out.

This is exactly where one system helps. If the defect report, roadside worksheet, sign-off and VOR dates are split across email, WhatsApp, a paper diary and a maintenance spreadsheet, the Traffic Commissioner file becomes harder to defend. We built Operator Compliance around keeping that evidence together, in line with the DVSA Guide to Maintaining Roadworthiness and the practical record-keeping expected by transport managers. Our guidance on roadside prohibitions and PG9 stops sits alongside the same principle.

Checks before the vehicle is accepted back as roadworthy

A roadside repair may get the vehicle moving, but an operator still needs to decide whether that is enough to return the vehicle to service. The decision should be based on evidence, not convenience.

Before accepting the vehicle back as roadworthy, we would expect practical checks such as:

• confirmation of the original defect and exactly how it was rectified
• a driver re-check, where safe and relevant, to confirm the defect symptoms have gone
• confirmation that no other safety-critical systems were affected
• if warning lights or fault codes were involved, confirmation of their status
• where relevant, brake performance, steering feel, air build-up, lighting, tyre condition, wheel security and coupling security
• confirmation that any load restraint issue has been addressed
• if a trailer defect caused the stop, confirmation that both tractor and trailer were checked for resulting damage or associated faults

The level of checking depends on the defect. A simple bulb replacement is not the same as a brake, steering, suspension or wheel-end issue. A conservative operator will escalate safety-critical roadside repairs to a workshop inspection before the vehicle resumes normal work, even if it can legally move from the roadside.

For that reason, many operators use three statuses rather than a simple yes or no:

• repaired and fit to continue service
• repaired for controlled movement only, such as return to depot or workshop
• not repaired, recover only

That internal discipline matters. If the roadside job was only enough to get the vehicle off the carriageway, the records should say so clearly. It should not later appear that the operator treated a temporary roadside fix as full rectification.

Where defects are serious or repeated, the transport manager should also look wider. Was this an isolated failure, poor daily defect reporting, missed preventive maintenance, or a recurring issue with a particular unit or trailer type? A single breakdown can expose a maintenance trend.

Tachograph records while the driver waits, assists or is recovered

Tachograph records during a breakdown are often untidy because the driver’s day stops following the plan. The safest approach is to keep the record accurate to what the driver is actually doing at each stage.

If the driver is simply waiting and is free to dispose of their time, break or rest may be appropriate depending on the circumstances. If the driver is required to remain with the vehicle, liaise with recovery, protect the scene, supervise the load, assist with access, or otherwise remain responsible for work, that is more likely to be other work or, in some cases, availability rather than break. The exact mode depends on the facts, so we advise drivers and managers to be conservative and avoid claiming break unless the legal conditions for break are genuinely met.

As a practical rule:

• active fault reporting, dealing with authorities, arranging recovery, assisting repair or load transfer, and vehicle checks should be recorded as other work
• waiting where the duration is known in advance and the driver is not required to work may fall under availability
• break should only be used if the driver is genuinely on a qualifying break and free from work duties
• if the driver is recovered as a passenger, record the period according to what the driver is actually doing and keep notes if the situation is unusual

If a record cannot be captured properly on the unit, manual records may be needed. Drivers should make a printout or manual entry where required and note the reason, such as breakdown, roadside repair or recovery. The note should include date, time and place, and the driver should sign it if that is how the record is being completed. The aim is not to create extra paperwork for its own sake. It is to make sure anyone reviewing the day later can understand why the trace looks irregular.

For mixed fleets, remember that the UK rules on drivers’ hours and tachographs can differ in detail from EU generally, particularly depending on vehicle type, route and legal regime. Where EU rules apply, they should be followed as such. Where domestic rules apply, record-keeping still needs to be clear enough to explain the driver’s time. If a breakdown causes an unavoidable extension or exceptional situation, the driver should make the required written note on the record and the operator should retain it.

This is one of the reasons operators want tachograph evidence and incident notes in the same place. We often see the maintenance side kept in one system and the driver explanation somewhere else. That is harder to defend than one joined-up record.

What to do if DVSA issues a prohibition at the roadside

If DVSA issues a prohibition, the vehicle, trailer or both have been found with a defect serious enough to restrict use. In practice, that means the unit cannot simply go back into service because the operator believes the issue has been dealt with. The terms of the prohibition control what happens next.

A prohibition may be immediate or delayed. An immediate prohibition means use is stopped at once, subject to any specific movement allowed. A delayed prohibition allows limited continued use until the stated time, but operators should still treat it seriously and rectify the defect promptly.

The first step is to retain the prohibition notice and record:

• what defect was stated
• whether it applied to the vehicle, trailer or both
• whether it was immediate or delayed
• any conditions on movement
• the name of the examiner if shown
• the date, time and place of issue

Clearing the defect means more than fixing the fault. The operator needs evidence that the prohibition has been satisfied before the vehicle is used again. Depending on the defect and the terms of the notice, that may involve repair evidence, inspection evidence and, where required, formal clearance by an authorised examiner or a test station process. Operators should follow the instructions on the notice itself and any accompanying DVSA guidance. Do not assume that a workshop invoice alone is always enough.

The records to retain should include the prohibition, repair worksheet, any parts record, any fitter sign-off, any subsequent inspection or test result, and the operator’s own decision record returning the vehicle from VOR status. If the prohibition led to a missed inspection, route cancellation, driver hours issue or customer claim, keep those linked records as well.

Where a prohibition is issued, the transport manager should review whether it triggers wider action. That may mean checking similar vehicles, reviewing maintenance provider performance, or assessing whether the defect should be reported internally as a maintenance control issue. Our practical notes on prohibitions and PG9 roadside stops cover the operational side in more detail.

The file a Traffic Commissioner would expect afterwards

After a roadside breakdown, especially one involving a serious defect or prohibition, the Traffic Commissioner would expect a clear audit trail. Not a pile of disconnected documents, but one coherent file showing control.

A good post-incident file will usually contain:

• the driver’s defect report
• the time and method of internal notification
• VOR start and finish times
• roadside assistance or recovery attendance details
• third-party repair worksheet and invoice
• any photographs
• any tachograph printouts or manual records explaining the day
• any DVSA prohibition or roadside check documents
• workshop follow-up inspection and rectification sign-off
• the decision authorising return to service
• any review note from the transport manager
• evidence of any preventive action taken afterwards

That last point matters. If the incident exposed a weak process, the file should show what changed. That might be a revised driver instruction, a new escalation rule for temporary repairs, or a decision that certain roadside defects must always be seen in the workshop before normal use resumes.

Preparation beforehand is simple, but it needs to exist before the phone rings. We recommend three things.

First, one agreed process. Drivers, traffic office staff, workshop staff and out-of-hours managers should all know the same steps. Who takes the first call, who declares VOR, who approves roadside repair, who checks tachograph notes, and who signs the vehicle back into service should not be improvised.

Second, provider contacts that match the areas the fleet actually runs. Keep current details for recovery, tyre support, mobile technicians, trailer specialists and workshop cover in the regions your vehicles use, and keep a plain reference such as PG9 and S-marked prohibitions explained where the office can find it. If you run nationally, a local garage number in one depot drawer is not enough.

Third, one place to capture incident details. Not five places. One record should hold the defect, contacts, documents, sign-off and follow-up. That is the difference between a manageable compliance file and a scramble before a public inquiry. In Operator Compliance, that is the standard we work to because Fleeta Limited runs under an operator licence itself and built the system around the record set operators are actually asked to produce.

For operators that want to tighten the process before the next incident, our operator licence compliance software for one joined-up record is designed to hold vehicle, trailer and driver evidence together, and our team can talk through the workflow you want in place. If your wider stack needs data moving between systems, we also support integration work through REST API and webhooks, with Fleetalyse and Logivo.AI often part of the wider compliance conversation.

When a vehicle breaks down, speed matters. But the operator that comes out of it cleanly is the one that can show, in order, what happened, what was fixed, why the vehicle was considered roadworthy, how the driver’s time was recorded, and what was done afterwards to prevent a repeat. That is what sound compliance after an HGV roadside breakdown looks like in practice.