What this is
What is a roadside breakdown record?
What is a roadside breakdown record?
It is the record of a vehicle becoming immobile or unsafe to continue while away from base, and of what was done about it. It covers the location and the fault, the driver's own protection at the roadside, the response and recovery times, the effect on the load and on the driver's hours, and the judgement on whether maintenance or the pre-trip check should have caught it.
How does a breakdown differ from a defect?
A defect is a condition found while the vehicle is under your control; a breakdown is a defect that announced itself in traffic. Every breakdown therefore generates a defect that must be reported, repaired and certified, and this record is the wrapper proving the roadside event was handled and the underlying fault passed on. One that closes without a defect record has documented an inconvenience, not a failure.
Who completes it, and who reviews it?
The driver completes the header, the roadside safety block and the response, because those facts are only knowable from the verge and decay within hours. Maintenance and the fleet manager complete the prevention judgements: preventable by maintenance, should have been caught at pre-trip, recurring on this vehicle. Asking the driver those three turns the record into a self-assessment nobody trusts.
Scope
When is a roadside breakdown record required?
This record covers a vehicle failing away from base. Its neighbours in the fleet programme cover collisions, enforcement stops, defects found under your own control and load damage, and a breakdown record used in their place produces an event that cannot be counted later.
Use this template when
- A vehicle has become immobile, or unsafe to continue, at any point away from base
- A fault forced an unplanned stop even if the driver was able to continue afterwards
- A refrigeration unit failed in transit and the load was at risk while the vehicle was stopped
- Recovery or third-party assistance was called out to a vehicle on the road
- The driver ran out of fuel, misfuelled or otherwise caused the stop, which the fault category records as driver error rather than hiding
Do not use it for
- A collision, however minor, which needs the Road Collision Report because the evidence set, the notification duties and the insurer's timescales are all different
- A roadside enforcement stop, which belongs in the Roadside Inspection Record along with any out-of-service order and its clearance
- A defect found at pre-trip, walkaround or in the yard, which is a Vehicle Defect Report and should never be dressed as a breakdown to explain a late departure
- Damage to the goods discovered on delivery, which is a Cargo Damage Report even where the delay caused it
- A near miss where nothing failed and nothing stopped, which is a Near Miss Road Report and is diluted if logged here
Compliance mapping
Which FMCSA 396 requirements does this satisfy?
There is no regulation called breakdown reporting. The duties assemble from three directions: how a stopped vehicle must be made visible, what must happen to the defect that stopped it, and what the maintenance programme must have done beforehand. A defensible record satisfies all three, not the delay accounting.
| Clause | Requirement | Where it lands |
|---|---|---|
| 49 CFR 392.22(a) | Hazard warning signal flashers activated immediately on stopping on the travelled portion or shoulder, and kept on until warning devices are placed | Safety at the roadside |
| 49 CFR 392.22(b) | Warning devices placed within ten minutes of stopping, in the pattern required for the road type and visibility | Safety at the roadside |
| 49 CFR 393.95 | Emergency equipment, including warning devices and fire extinguisher, carried and in working order | Safety at the roadside |
| 49 CFR 396.7 | Vehicle not to be operated in a condition likely to cause an accident or breakdown; movement permitted only to the nearest place of safe repair | Response |
| 49 CFR 395.1(b) | Adverse driving conditions relief is limited to weather and unforeseen road or traffic conditions, and does not extend to vehicle failure | Response |
| 21 CFR 1.908(e) | Carrier duty to maintain agreed temperature conditions and to determine, after any indication of material failure, whether the food remains safe | Load impact |
| 49 CFR 396.11 | Any defect or deficiency discovered by the driver during operation reported, repaired and the repair certified before the vehicle is dispatched again | Prevention |
| 49 CFR 396.3(a)(1) | Systematic inspection, repair and maintenance of all vehicles under the carrier's control, with records evidencing it | Prevention |
What it does not cover
- The driver vehicle inspection report, which is the daily instrument under 49 CFR 396.11 and 396.13; the breakdown record feeds it but cannot replace the day's report or the review of the previous one.
- Repair certification, which belongs on the work order and must name what was done and who certifies the vehicle safe, including where the work happened at the roadside.
- The out-of-service clearance, which lives with the roadside inspection record and requires the specific defect to be repaired and the certification returned to the enforcement authority.
- The temperature excursion assessment, which is a food safety disposition against the product specification, not a driver's judgement that the temperature held.
- Hours of service correction, which needs its own violation record and log annotation; noting that hours were affected does not discharge the duty to fix the log.
Global
Roadside Breakdown Record requirements by country
Every regime treats the stopped vehicle and the underlying defect as separate duties. What varies is how prescriptive the roadside protection rules are, and whether the maintenance system behind the breakdown is licensable.
49 CFR 392.22, 393.95, 396.3, 396.7 and 396.11
Prescriptive on warning devices and timing, and on the route a discovered defect must take through report, repair and certification.
A breakdown creates a documentary trail an investigator can walk end to end, and the missing certification is the finding that recurs most often.
Road Traffic Act 1988 s.40A; Goods Vehicles (Licensing of Operators) Act 1995 undertakings
Using a vehicle in a dangerous condition is an offence, and the operator licence carries an undertaking that vehicles are kept fit and serviceable.
Repeat roadside failures are evidence against the licence itself at a public inquiry, which makes the recurring-fault answer a regulatory statement rather than a fleet metric.
Regulation (EC) 561/2006 art.12; Directive 2014/47/EU
A driver may depart from the driving and rest limits only to reach a suitable stopping place, recording the reason manually, and technical roadside inspection targets poorly maintained fleets.
The departure must be written on the record sheet or printout at the time; claiming it retrospectively after a breakdown is not accepted.
National Safety Code Standard 11 and Standard 13
Trip inspection and defect reporting under Standard 11, hours of service under Standard 13, both administered provincially.
Major defects listed in the Standard 11 schedules prohibit further operation outright, so the record must distinguish major from minor before anyone decides to limp home.
Heavy Vehicle National Law, primary duty and chain of responsibility
Every party in the chain must ensure safety so far as reasonably practicable, including maintenance and scheduling.
A breakdown caused by a deferred repair or a schedule that left no time for the walkaround reaches the scheduler and the consignor, not just the driver.
ISO 39001; ADR 8.1.5 for dangerous goods
Road traffic safety management system requirements, with ADR prescribing the safety equipment carried on dangerous goods vehicles.
For a dangerous goods breakdown the equipment schedule and the emergency instructions in writing govern the roadside response, and the generic warning device answer is not enough.
How to complete it
How to complete a roadside breakdown record, step by step
The template will produce a complete record from a driver standing on a verge in the rain. What decides whether it is worth anything is who answers which questions, and when.
The fault will still be there in ten minutes; the driver's exposure will not. Answering the six roadside questions first, from behind the barrier, is both the correct sequence and the reason those fields sit ahead of the diagnosis in the form. Record the position honestly even where it convicts the driver of leaving on the traffic side, because that answer is the only one that ever changes anything about how the fleet briefs breakdowns.
The fault category is a routing label: engine, brakes, electrical, reefer, driver error. It is not a cause. Electrical covers a corroded earth, a flat battery and an alternator that has now failed three times, and the description field is where the difference lives. Write what the driver observed, what the technician found and what was replaced as three distinct statements.
Preventable by maintenance, should have been caught at pre-trip, and recurring on this vehicle are technical findings needing the asset history and the workshop view. Drivers answering their own pre-trip question will say no, which is human rather than dishonest. Route those three to maintenance once the vehicle returns, and require the previous record IDs before recurring can be marked yes.
A roadside wait consumes hours the driver will need to finish the run, and the decision to send relief is only cheap while it is early. Take the delay estimate at the point assistance is booked, compare it with the remaining driving time, and make the call then. Recording hours affected as managed after the driver has run over describes a violation rather than managing one.
What auditors find
Most common roadside breakdown record findings
Breakdown records almost always exist, because somebody has to explain a late delivery. The findings concern what they leave out: the defect that never became a defect, and the safety answers nobody checked.
| Finding | Clause | What fixes it |
|---|---|---|
| Record raised days later from recollection, with location given as a road number and direction. | 49 CFR 396.11 | Raise it at the roadside and drop the pin; a reconstructed location cannot be matched to a recovery invoice or a camera clip. |
| Fault repaired at the roadside; no defect report, work order or repair certification created. | 49 CFR 396.11 | Make the repaired-roadside answer raise a defect record and a work order naming the part and the certifying signature. |
| Every roadside safety answer on file is maximum score, including on records where recovery reported the driver beside the vehicle. | 49 CFR 392.22 | Sample the block against telematics and recovery notes each month, and brief the mismatches rather than the scores. |
| Warning devices recorded as used, with no time of placement and no check that they were carried. | 49 CFR 393.95 | Record the placement time against the stop time, and verify the emergency equipment at pre-trip rather than after the event. |
| Vehicle driven on after a brake, tyre or coupling failure because the load was due. | 49 CFR 396.7 | Treat those categories as no-go; 396.7(b) permits movement only to the nearest place of safe repair, and nowhere else. |
| Recurring fault marked yes with nothing linked, or marked no where three earlier records exist on the same asset. | 49 CFR 396.3(a)(1) | Search the asset history before answering, and attach the previous record IDs so the review sees the pattern rather than a checkbox. |
| Driver hours exceeded during the wait, recorded as managed, with no relief record and no log annotation. | 49 CFR 395.1(b) | Raise the hours of service record and annotate the log; breakdown is not an adverse driving condition. |
| Temperature recorded as maintained on a five-hour reefer failure, on the driver's judgement alone. | 21 CFR 1.908(e) | Attach the unit's temperature download and let quality make the disposition; a driver's opinion is not a temperature record. |
| Secondary near miss recorded and never investigated, because the record closed as a maintenance item. | 49 CFR 392.22 | Route any secondary incident answer other than no to the near miss process on submission, independently of the defect. |
| PM plan review answered no on a preventable failure, and the maintenance interval left unchanged. | 49 CFR 396.3(a)(1) | Require a stated reason where a preventable breakdown does not trigger a review of the interval or the inspection content. |
Case in point
Case in point: the alternator that failed three times and was recorded once
A chilled distribution fleet ran a tractor unit on a nightly trunk between two depots. In February it lost electrical power on a dual carriageway slip road. The driver moved onto the verge, put the hazard lights on, and waited in the cab. A mobile technician arrived in ninety minutes, fitted an alternator from his van, and the unit completed the run. The record was raised next morning by the transport office: electrical, delay two hours, repaired roadside, preventable by maintenance no.
In April the same unit lost power on a motorway at night. The trailer refrigeration ran off its own engine and the load survived, but the driver stood on the verge for two hours and a passing vehicle clipped the cone the recovery operator had placed. In June it failed a third time, was recovered, and quality rejected part of the load. Only then did anyone open the asset history, and it showed one electrical record, not three. February had been invoiced through the roadside assistance contract; April was van stock with no work order.
The failing component was never the story. A charging circuit fault that eats alternators shows itself as a pattern, and the pattern was invisible because two of the three repairs had been treated as expenses rather than maintenance events. The corrective action was not a better breakdown form; it was making repaired-roadside raise a work order automatically, and requiring the asset history before the recurring-fault question could be answered.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- FLT-015
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Downtime hours
- Direction
- High is bad
- Singleton
- No
- Basis
- FMCSA 396
- Links
- Links Asset; feeds work order
- Tags
- Fleet, Reliability
- Sections
- 5
- Fields
- 55
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 6
Header
22 fieldsRecord ID*
Auto sequence. Format RBD-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Exact Location
Drop a pin. Roadside events rarely have a useful address.
Vehicle*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Unit Number
The number painted on the door, which is what drivers actually use.
Driver*
Person ID*
Links to FDN-003 Person ID
Licence Class
Trip Or Route Reference
Origin
Destination
Odometer Reading
Load Carried
Chilled, frozen, ambient, mixed temperature, dangerous goods or empty.
Customer Or Site
Time Of Breakdown*
Fault Category*
Engine, transmission, brakes, tyres, electrical, reefer unit, fuel, or driver error such as running out of fuel.
Description*
Safety at the roadside
7 fieldsThe Hard Shoulder Is The Most Dangerous Place
More drivers are killed standing beside a broken down vehicle than in the breakdown itself. Get out on the safe side, get behind a barrier, and stay there.
Vehicle Moved To Safe Location*
- Yes3 pts
- Not possible1 pt
- No0 pts
Hazard Lights And Triangle Used*
- Both3 pts
- One only1 pt
- Neither0 pts
High Visibility Clothing Worn*
- Yes3 pts
- No0 pts
Driver Left The Vehicle Safely*
- Yes, safe side3 pts
- Traffic side0 pts
- Stayed in cab1 pt
Waited Away From Carriageway*
- Yes, behind barrier3 pts
- On verge1 pt
- Beside vehicle0 pts
Any Secondary Incident*
- No3 pts
- Near miss1 pt
- Yes0 pts
Response
6 fieldsAssistance Called*
- Yes3 pts
- Self recovered2 pts
- No0 pts
Time To Assistance Arriving*
Repaired Roadside Or Recovered*
- Repaired roadside3 pts
- Recovered1 pt
Total Delay Hours*
Driver Hours Affected*
A long roadside wait can push the driver over their hours. Plan the relief rather than the push home.
- No3 pts
- Yes, managed1 pt
- Yes, exceeded0 pts
Relief Driver Arranged
- Yes3 pts
- Not needed3 pts
- No0 pts
Load impact
6 fieldsReefer Continued Running
- Yes3 pts
- Intermittent1 pt
- No0 pts
Temperature Maintained*
- Yes3 pts
- Marginal1 pt
- No0 pts
Excursion Record ID
Links to FLT-027 Record ID
Load Transferred
Product Rejected On Arrival
- No3 pts
- Partly1 pt
- Yes0 pts
Customer Notified*
- Yes3 pts
- Not required3 pts
- No0 pts
Prevention
14 fieldsPreventable By Maintenance*
- No3 pts
- Yes0 pts
Should Have Been Caught At Pre-Trip*
- No3 pts
- Yes0 pts
Recurring Fault On This Vehicle*
- No3 pts
- Yes0 pts
Work Order ID
Links to MNT-002 Work Order ID
PM Plan Review Triggered*
- Yes3 pts
- Not needed3 pts
- No0 pts
Cost Of Breakdown
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Fleet Manager*
Signature*
Transport Supervisor*
Second Signature*
FLT-015 · record IDs look like CASE-2026-000 · Links Asset; feeds work order
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the straightforward part. What breaks is the handover: the defect that never became a work order, the recurring fault nobody counted, and the roadside decision made by a driver with nobody on the other end of the phone.
Holds breakdown records against the asset register, counts failures by unit and category, and surfaces the vehicles whose reliability is a maintenance question rather than bad luck.
Turns every roadside repair and recovery into a work order with a part, an owner and a certification, and raises the PM interval review when a preventable failure recurs.

Watches breakdown duration against remaining driving time and prompts the relief decision while it is still early, then routes the load and defect consequences to their owners.
Takes any secondary incident or near miss out of the maintenance queue and into investigation, and reports the roadside safety answers as exposure rather than as compliance.
This template lives in KnowFleet — fleet and transport. Drivers, vehicles, hours, cargo securement and operator licence compliance.
Meet KnowFleet→Glossary
Roadside Breakdown Record definitions and key terms
- Driver vehicle inspection report
- The daily record under 49 CFR 396.11 of any defect or deficiency discovered by or reported to the driver, and of the repair and certification that follows.
- Warning device
- The reflective triangles, flares or fusees required by 49 CFR 393.95 and placed under 392.22(b) to make a stopped vehicle visible on approach.
- Out-of-service order
- An enforcement prohibition on further operation until a specified defect is repaired and certified, issued at a roadside inspection rather than at a breakdown.
- Major defect
- A defect that prohibits further operation outright, as scheduled in trip inspection standards, distinguished from a minor defect that may be recorded and driven on.
- Secondary incident
- A collision or near miss involving the stopped vehicle, its driver or the responders, occurring after and because of the original failure.
- Adverse driving conditions
- Weather or unforeseen road and traffic conditions that permit limited extra driving time under 49 CFR 395.1(b); vehicle failure is expressly not one of them.
- Preventable breakdown
- A failure that a scheduled inspection, service interval or pre-trip check would have caught, judged after the fact by maintenance rather than by the driver.
- Temperature excursion
- A departure from the agreed temperature range for a load, which requires a documented disposition of the product rather than a note that the unit was restarted.
FAQ
Frequently asked questions about roadside breakdown record
Is a breakdown a reportable defect even if the driver fixed it?+
Yes. 49 CFR 396.11 turns on the defect being discovered during operation, not on who repaired it or how long it took. A tyre changed on the verge, a fuse replaced, a coupling reseated: each is a defect discovered in operation, each needs to reach the report, and each needs a repair certification before the vehicle goes out again.
Should the driver leave the vehicle or stay in the cab?+
Get out on the nearside and get behind a barrier where one exists. Staying in the cab is the safer choice only where there is no safe exit or no refuge to reach, and it should be recorded as the deliberate decision it was rather than as the default. Standing beside the vehicle on the traffic side is the worst of the three, and it is what the form's answer options exist to surface.
Does a breakdown excuse an hours of service overrun?+
No. The adverse driving conditions relief in 49 CFR 395.1(b) is defined by weather and unforeseen road or traffic conditions, and the equivalent European provision in article 12 of Regulation 561/2006 permits departure only to reach a suitable stopping place, recorded manually at the time. Your own vehicle failing is neither. Plan relief, or record the violation and manage it.
Who should answer whether the pre-trip should have caught it?+
Maintenance, after the vehicle is back and the failed part has been seen. A worn brake lining, a chafed hose or a tyre already below limit are visible at walkaround; a sheared injector or a failed control module is not. Leaving the question with the driver produces a uniform no, and leaving it with a manager who has not seen the part produces a uniform yes.
How many breakdowns on one vehicle is too many?+
Two unrelated failures inside a quarter is worth a maintenance review; two of the same category is a diagnosis that was missed the first time. Absolute thresholds matter less than comparison against the rest of the fleet on similar duty, because a double-shifted urban multidrop unit will legitimately break down more than a trunker.
Should the driver take photographs at the roadside?+
Only from a position of safety, and never on the traffic side. A picture of the failed component, the position of the vehicle and the warning devices in place is useful evidence for both the maintenance review and any later claim. It is not worth a step into a live lane, and any instruction to capture evidence should say so.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Fleet and Driver Compliance
Transport Provider Assessment
Assesses a haulier for licensing, driver management, vehicle standards, temperature capability and load security
Driver Vehicle Inspection Report
The pre-trip and post-trip inspection a driver completes on a commercial vehicle
Annual Vehicle Inspection
The yearly statutory inspection of a commercial vehicle
Trailer Inspection
Checks trailer coupling, brakes, lights, tyres, doors and structure
Reefer Unit Check
Checks refrigeration unit operation, fuel, temperature setpoint and alarm history
Vehicle Defect Report
Reports a defect found on a vehicle at any time, not just during a scheduled inspection
More in Road Incidents
Road Collision Report
Records a collision involving a company vehicle on public roads
Cargo Damage Report
Records damage to cargo discovered in transit or at delivery
Near Miss Road Report
Records a close call on the road that did not result in a collision
Post Incident Driver Assessment
Assesses a driver's fitness and competency following a serious incident

Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- 49 CFR 392.22 — Emergency signals; stopped commercial motor vehicles
- 49 CFR 393.95 — Emergency equipment on all power units
- 49 CFR 396.3, 396.7, 396.11 and 396.13 — inspection, repair, maintenance and driver vehicle inspection reports
- 49 CFR 395.1(b) and 395.3 — adverse driving conditions and driving limits
- Regulation (EC) 561/2006, article 12 — departure from the driving and rest rules
- 21 CFR 1.908(e) — FSMA sanitary transportation, carrier requirements
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.