What this is
What is a driver performance review?
What is a driver performance review?
A driver performance review is a periodic assessment of one driver's safety, compliance, delivery and behavioural record over a defined period, held with the driver rather than about them. It draws together collision and near miss history, roadside and hours of service violations, telematics events, delivery and cold chain outcomes and workload, and closes with a rating, a development plan and any change to authorisation. It is a management instrument, not a qualification record.
How is a driver performance review different from a qualification file?
The qualification file proves entitlement and must exist and be current for every driver at all times; it answers whether the person may lawfully drive. The performance review answers how well they do it, over a period, and has no bearing on entitlement unless the review itself restricts or withdraws authorisation. One is a statutory dossier that decays; the other is a conversation that either happens or does not.
What is a preventable collision?
One the driver could reasonably have avoided, irrespective of who was legally at fault. The distinction matters because fault is a liability question decided elsewhere and often much later, while preventability is the only version of the question that supports coaching. A driver struck while stationary at a light has been in a collision and has nothing to learn; a driver who was legally in the right but drove into a foreseeable conflict does.
Scope
When is a driver performance review required?
This review is a synthesis. Every input it summarises is created somewhere else, and it works only when those records already exist, which is why the most common misuse is running the review as the place where a collision or a violation gets investigated for the first time.
Use this template when
- The stated review interval has come round for a driver, whether annual, six monthly or probationary
- An incident, roadside prohibition or hours of service violation has triggered a review outside the cycle
- The trend across telematics and violation data has worsened and needs a conversation rather than an alert
- A driver is coming off probation and a decision is needed on unrestricted authorisation
- Recognition is due: a sustained record worth recording where the only records are otherwise negative
Do not use it for
- Investigating a collision, which is the Road Collision Report and needs causation and evidence, not a preventability tick in a quarterly summary
- Auditing hours of service records, which is the Hours of Service Log Review and examines the logs themselves rather than a count of violations
- Analysing the telematics population, which is the Telematics Performance Review and works at fleet and route level rather than per driver
- Assessing a driver immediately after an incident, which is the Post Incident Driver Assessment and answers a fitness question, not a performance one
- Evaluating whether the schedule itself is safe, which is the Fatigue Risk Assessment and looks at the roster rather than the driver's answer about tiredness
Compliance mapping
Which FMCSA CSA requirements does this satisfy?
There is no regulation that requires a driver performance review by name. What regulation does is make the operator answerable for the conduct it tolerated, which is why the review earns its place: it is the record showing that the pattern was seen, discussed and acted on before the collision that made it a legal question.
| Clause | Requirement | Where it lands |
|---|---|---|
| FMCSA CSA Crash Indicator BASIC | Crash involvement weighted by severity and recency, with preventability determination available for review | Safety record |
| FMCSA CSA Unsafe Driving BASIC | Speeding, reckless driving, improper lane change, inattention and seat belt violations measured against exposure | Telematics and behaviour |
| FMCSA CSA Hours of Service Compliance BASIC | Driving beyond permitted hours and false or incomplete records of duty status, weighted by severity | Safety record |
| FMCSA 392.82 | Prohibition on hand-held mobile telephone use while driving a commercial motor vehicle | Telematics and behaviour |
| FMCSA 396.13 | Driver must be satisfied the vehicle is in safe operating condition and review the last inspection report before driving | Safety record |
| FMCSA 392.3 | Prohibition on operating while ability or alertness is impaired through fatigue, illness or any other cause | Wellbeing and workload |
| 21 CFR 1.908(e) | Carrier duties for sanitary transportation of food, including temperature control and demonstrable personnel training | Delivery and cold chain |
| ISO 39001 cl.6 | Road traffic safety performance factors identified, objectives set and driver-level results planned and reviewed | Outcome |
What it does not cover
- The qualification dossier, which is the driver qualification file under FMCSA 391.51 and has to exist and stay current no matter how well the driver performs.
- Hours of service compliance, which is established by auditing the logs under 49 CFR Part 395 or Regulation (EC) 561/2006, not by counting violations once a period.
- Collision investigation, which needs sequence, evidence and causation, and produces the preventability determination this review can only carry forward.
- A disciplinary process, which has its own evidential and procedural rules; conducting one inside a coaching record contaminates both.
- Fatigue risk management, which assesses the roster, the schedule and the network rather than asking a driver whether they have felt tired.
Global
Driver Performance Review requirements by country
Nobody mandates the review. Several regimes mandate the consequence of not having done one, either by scoring the operator on the same events or by asking, after a fatality, what the organisation knew about the driver and when.
FMCSA Compliance, Safety, Accountability and the Safety Measurement System; 49 CFR Part 385
Roadside violations and crashes are weighted by severity and recency into BASIC percentiles at carrier level.
One driver's roadside record moves the operator's percentile and its intervention exposure, so the review is a commercial control as well as a safety one.
Goods Vehicles (Licensing of Operators) Act 1995 undertakings; DVSA Operator Compliance Risk Score
Operator licence undertakings require effective arrangements for driver conduct, with roadside outcomes feeding a risk score that drives targeting.
At public inquiry a Traffic Commissioner asks what was done about a driver whose record was already visible, and coaching records are the answer or the absence of one.
Regulation (EC) 1071/2009 good repute; Directive 2006/22/EC risk rating system; GDPR for telematics data
Operator good repute can be lost through serious infringements, while worker monitoring needs a lawful basis and proportionality.
Telematics can be used for coaching, but drivers must be told what is collected and why, and covert or open-ended monitoring is not defensible.
National Safety Code Standard 7 carrier and driver profiles; Standard 14 safety rating
Provincial profiles accumulate driver convictions, inspections and collisions, and roll up into a carrier safety rating.
The driver profile is a public-facing consequence, so a driver whose record is deteriorating is degrading the operating authority as they go.
Heavy Vehicle National Law, primary duty at s26C and executive due diligence at s26D
Chain of responsibility duties extend to everyone influencing transport activity, with executives personally accountable for assurance.
Due diligence is evidenced by what the organisation monitored and acted on, which makes a documented driver review a direct defence.
ISO 39001 road traffic safety management systems
Requires performance factors, objectives and driver-level monitoring to be defined and reviewed within the management system.
Auditors look for the loop from telematics to coaching to a changed result, not for the existence of a dashboard.
How to complete it
How to complete a driver performance review, step by step
Filling in the counts takes ten minutes and produces nothing. The review is made or wasted by four judgements: what the numbers are divided by, what preventable means here, what would change authorisation, and whether the driver spoke.
The Safety record and Telematics and behaviour sections are almost entirely raw counts, and the template has no field for distance, driving hours or drops. Add one and populate it, then rate events per unit of exposure and compare within a peer group doing comparable work. Without that, Ranking In Fleet and the weighted score describe route allocation, and every driver who has looked at their own data knows it.
Collisions and Preventable Collisions are separate fields for a reason, and the second is the one that carries meaning. Preventability should come from the collision report, determined against a consistent standard, and be agreed before the review opens. Arguing about it across the table converts a coaching conversation into a dispute about blame, and the driver stops offering anything useful for the rest of the hour.
Authorisation Affected offers Restricted and Withdrawn, which are qualification decisions taken in a performance record. Define in advance what triggers them, a preventable collision with injury, a pattern of hours of service violations, a phone use event, so the decision is a rule rather than a mood. Then push the change into the qualification file and the rota, because a restriction recorded only here will not stop anyone from being dispatched.
The driver signs, and the Any Concerns Raised By Driver field is where the review earns its keep: drivers see the yards, the customers, the traffic patterns and the schedules that produce the events being counted. Record what they said even when it is inconvenient, particularly on rest facilities and weekly hours, and route it to whoever owns the schedule. A run of reviews where that field is empty means nobody is being asked.
What auditors find
Most common driver performance review findings
Findings here are rarely about the form. They are about whether the review changed anything, whether the numbers meant what the rating claimed, and whether the pattern that was obvious in hindsight was visible in the record beforehand.
| Finding | Clause | What fixes it |
|---|---|---|
| Event counts rated without any exposure measure; highest-mileage drivers consistently ranked worst. | ISO 39001 cl.6 | Record distance or driving hours for the period and rate events per unit of exposure within a peer group. |
| Collision involvement scored without a preventability determination. | FMCSA CSA Crash Indicator BASIC | Take preventability from the collision report against a consistent standard, and rate only preventable events. |
| Near miss reports treated as a negative, or drivers who report ranked below those who do not. | ISO 39001 cl.6 | Score reporting positively and say so to the fleet; a fall in reports is a warning, not an improvement. |
| Telematics data used to issue warnings without ever being discussed with the driver. | FMCSA CSA Unsafe Driving BASIC | Show the data, ask what happened at each flagged event, and record the discussion before any rating. |
| Needs improvement rating recorded with Development Plan Agreed set to No and no action raised. | ISO 39001 cl.6 | Make a poor rating raise a plan with an owner and a date, or explain in the record why none was needed. |
| Hours of service violations counted in the review but never audited against the logs. | FMCSA CSA Hours of Service Compliance BASIC | Route the count to a log review; a tally without the underlying records cannot distinguish driver from dispatcher. |
| Fatigue reported as Frequently with no change to the roster and no fatigue assessment raised. | FMCSA 392.3 | Escalate reported fatigue to the schedule owner and raise a fatigue risk assessment on the route, not on the driver. |
| Phone use or distraction events recorded and closed with a verbal reminder. | FMCSA 392.82 | Treat hand-held use as a prohibited act with a defined consequence, recorded consistently across all drivers. |
| Authorisation recorded as Restricted with no matching entry in the qualification file or the rota. | FMCSA 391.51 | Push every authorisation change into the qualification record and the dispatch system on the same day. |
| Defects missed at pre-trip counted against the driver with no check on inspection time allowed. | FMCSA 396.13 | Verify that the schedule allows a real inspection before attributing missed defects to the driver. |
Case in point
Case in point: the bottom-quartile driver who was the safest one there
A chilled multi-temperature operator introduced telematics scoring and began quarterly reviews built on it. The dashboard ranked drivers on harsh braking, harsh acceleration and speeding events per period. The bottom quartile was stable across three quarters and consisted almost entirely of the urban multi-drop drivers working inside the M25, one of whom was in the bottom five every time. He was put on a development plan, then a second one, and told his ranking was a concern.
In the fourth quarter a top quartile driver on nightly trunk work ran into the back of a motorway queue at speed. The collision was preventable, he was on his eleventh consecutive night shift, and his telematics record was clean because two hundred miles of empty motorway generates almost no events. The review that had rated him Excellent twice had never asked about hours; Average Weekly Hours was blank because it was not required.
When events were recalculated per hundred thousand kilometres and split by route type, the bottom-quartile urban driver moved into the top decile of his peer group and the trunk drivers occupied the bottom. The rankings had been measuring drop density for a year. The corrective action was an exposure field, peer grouping by work type, and making weekly hours a required entry, and the operator wrote off the two development plans it had issued.
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.
6 sections
- Reference
- FLT-013
- Archetype
- Review
- Record ID
- DPR-2026-000
- Scoring
- Weighted percent
- Direction
- High is good
- Singleton
- No
- Basis
- FMCSA CSA
- Links
- Links Worker, Asset
- Tags
- Fleet, Performance
- Sections
- 6
- Fields
- 56
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
12 fieldsReview ID*
Auto sequence. Format DPR-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
Driver*
Person ID*
Links to FDN-003 Person ID
Licence Class
Period Reviewed*
Reviewed By*
Review Type*
Safety record
6 fieldsCollisions*
Preventable Collisions*
Preventability is the fair measure. Being hit while stationary is not a performance issue.
Near Miss Reports Submitted*
Roadside Violations*
Hours Of Service Violations*
Defects Missed At Pre-Trip*
Telematics and behaviour
9 fieldsHarsh Braking Events
Harsh Acceleration Events
Speeding Events
Distraction Or Phone Use Events
Seat Belt Compliance*
- Always3 pts
- Occasional lapse1 pt
- Poor0 pts
Idling Percent
Ranking In Fleet
- Top quartile4 pts
- Second quartile3 pts
- Third quartile1 pt
- Bottom quartile0 pts
Trend Versus Last Period*
- Improving3 pts
- Stable2 pts
- Worsening0 pts
Telematics Data Discussed With Driver*
Telematics used only to discipline breeds resentment. Used to coach, it works.
- Yes3 pts
- No0 pts
Delivery and cold chain
6 fieldsOn Time Delivery Percent
Cold Chain Excursions Caused*
Cargo Damage Incidents*
Temperature Logs Completed*
- Always3 pts
- Mostly1 pt
- Poor0 pts
Paperwork Accuracy*
- Excellent3 pts
- Adequate2 pts
- Poor0 pts
Customer Feedback
- Positive3 pts
- Neutral2 pts
- Negative0 pts
Wellbeing and workload
4 fieldsFatigue Reported*
- No3 pts
- Occasionally1 pt
- Frequently0 pts
Average Weekly Hours
Rest Facilities Adequate*
- Yes3 pts
- Marginal1 pt
- No0 pts
Any Concerns Raised By Driver
Drivers see the network, the customers and the yards. They are worth asking.
Outcome
19 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Overall Rating*
- Excellent4 pts
- Good3 pts
- Acceptable2 pts
- Needs improvement0 pts
Recognition Given
- Yes3 pts
- No1 pt
Development Plan Agreed*
- Yes3 pts
- Not needed3 pts
- No0 pts
Additional Training Required*
- No3 pts
- Yes1 pt
Authorisation Affected*
- No3 pts
- Restricted1 pt
- Withdrawn0 pts
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
Next Due*
Fleet Manager*
Signature*
Driver*
Second Signature*
FLT-013 · record IDs look like DPR-2026-000 · Links Worker, Asset
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The review itself is an hour in a room. What fails around it is the input that was never collected, the coaching plan that closed without a change, and the restriction that never reached dispatch.
Assembles the period record from collision, roadside, hours of service and telematics sources, and pushes any authorisation change into the qualification file and the rota.
Supplies the delivery and cold chain picture, on-time performance, temperature excursions and cargo damage, attributed to the trip rather than to the driver by default.
Carries reported fatigue, weekly hours and rest facility concerns into occupational health and the roster, so wellbeing answers reach whoever owns the schedule.
Normalises event counts against distance and hours, flags worsening trends between reviews, and raises an out-of-cycle review when a trigger fires.
This template lives in KnowFleet — fleet and transport. Drivers, vehicles, hours, cargo securement and operator licence compliance.
Meet KnowFleet→Glossary
Driver Performance Review definitions and key terms
- Preventable collision
- A collision the driver could reasonably have avoided regardless of legal fault, which is the only version of the measure that supports coaching.
- BASIC
- One of the behaviour analysis and safety improvement categories in the FMCSA CSA programme, each aggregating violations of a particular type at carrier level.
- Safety Measurement System
- The FMCSA system that weights roadside violations and crashes by severity and recency and expresses the result as a percentile against peer carriers.
- Exposure denominator
- The distance, driving hours or delivery count that event totals are divided by, without which counts measure workload rather than behaviour.
- Harsh event
- A telematics-detected deceleration, acceleration or cornering force exceeding a configured threshold, which is a proxy for driving style and heavily route dependent.
- Idling percent
- The share of engine-on time spent stationary, a fuel and emissions measure that is often driven by yard waiting and reefer duty rather than driver habit.
- Coaching
- A discussion of specific evidenced events aimed at changing a method, distinct from discipline in its purpose, its record and its procedural protections.
- Chain of responsibility
- The principle in Australian heavy vehicle law that everyone influencing a transport activity, including schedulers and consignors, holds a duty for its safety.
FAQ
Frequently asked questions about driver performance review
Should telematics data be used in a performance review?+
Yes, with a denominator and with the driver present. Telematics is the only source that observes every trip rather than the ones that produced an incident, and refusing to use it wastes the safest available evidence. What fails is using it raw: unnormalised counts, no peer grouping, and a rating issued before anybody asked the driver what happened at the flagged events.
How often should the review run?+
The template offers annual, six monthly, after an incident and probation, and the interval matters far less than the triggers. An annual cycle with incident and trend triggers catches more than a quarterly cycle without them. What a short interval buys is early detection on new drivers, which is why probation reviews are worth running at a few weeks rather than a few months.
Is a performance review a disciplinary record?+
It should not be, and blurring the two destroys the data. Once drivers understand that what they say in a review can be used against them, near miss reports fall, telematics events are gamed, and the fatigue question is answered No by everybody. Keep the coaching record separate from any disciplinary process, and if an event warrants discipline, run that process on its own evidence.
Does the driver have to agree with the rating?+
No, but their view has to be recorded. The second signature is acknowledgement that the review happened and the driver saw the data, not agreement with the conclusion. Where a driver disputes a rating, the useful record is the specific disagreement in the concerns field, because the disputes are frequently right and they are frequently about the schedule.
What should trigger a change to authorisation?+
A rule written before the case appears. A preventable collision causing injury, a hand-held phone use event, a pattern of hours of service violations, or a defect deliberately concealed are all defensible triggers. What is not defensible is restricting one driver for a third-quartile ranking while another with a preventable collision keeps full authorisation, and inconsistency here is what makes a restriction hard to sustain.
Do drivers need a review if the numbers are good?+
Yes, and the Recognition Given field is the reason. In most fleets the only records attached to a driver's name are negative ones, so a sustained clean record produces no evidence of anything. It also matters that the wellbeing questions get asked of the drivers nobody is worried about, since a clean event record can mean low exposure to the conditions that generate events rather than skill.
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 Driver Records
Driver Qualification File
Holds everything required to prove a driver is qualified, including licence, medical, record of violations and employment history
Driver Licence Verification
Verifies a driver's licence class, endorsements and status with the issuing authority
Medical Certificate Record
Holds the driver's medical examiner certificate and its expiry date
Motor Vehicle Record Review
Reviews a driver's traffic violation history
Road Test Record
Records a practical driving assessment covering vehicle handling, coupling, backing and defensive driving
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:
- FMCSA Compliance, Safety, Accountability Safety Measurement System methodology and BASIC definitions (US)
- 49 CFR 392.3, 392.82 and 396.13 — impaired operation, mobile telephone use, driver inspection duty
- 49 CFR Part 395 — hours of service of drivers
- 21 CFR Part 1 Subpart O, section 1.908 — sanitary transportation of human and animal food
- ISO 39001:2012 road traffic safety management systems, clauses 6 and 9
- Heavy Vehicle National Law, sections 26C and 26D, primary duty and executive due diligence (Australia)
- Directive 2006/22/EC on enforcement of social legislation in road transport and the risk rating system (EU)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.