Fleet Driver Safety Checklist
Driver safety is not a poster. It is a sequence of controls that either exist or do not: who is allowed to drive what, what condition the vehicle left in, how long the shift really was, and what happens after a near miss. This checklist covers the controls.
Ask any fleet why its last serious incident happened and the answer is rarely mysterious. The driver had been on since four. The reversing camera had been on the defect list for a fortnight. The route had a manoeuvre in it that nobody had ever driven in daylight. The agency driver had never operated that tail lift and said so to somebody who was busy.
Every one of those is a control that was supposed to exist. Safety work is mostly the unglamorous business of checking that controls are real rather than documented: that the licence check actually happened, that the defect actually got fixed, that the schedule the planner built could actually be driven inside the hours.
This list is written for the person who has to make that true on a Tuesday. It is not a legal compliance framework, and it does not replace the duty rules that apply where you operate. It covers the operational checks that sit between a policy document and a driver pulling out of the gate.
40 checks across 6 sections
Before anyone is allowed to drive
- Verify the licence with the issuing authority rather than accepting a photograph of a card, and record the date you checked.
- Confirm the categories and entitlements match every vehicle the driver could be assigned, including the ones they will only drive at Christmas.
- Check for endorsements, restrictions and any medical requirement attached to the licence, and diarise the next check date rather than trusting an annual sweep.
- Complete an assessment drive on a representative route with a representative vehicle before the first solo shift, not a lap of the industrial estate.
- Record familiarisation on the specific equipment the driver will use: tail lift, crane, reversing aids, retarder, load restraint system.
- Confirm the driver has read and signed the driving-for-work policy, including the mobile phone rule and the reporting duty after any contact.
- Check that the driver knows what to do when the vehicle is unroadworthy, and that they believe you will support them if they refuse to take it.
Vehicle handover, every shift
- Complete the walkaround with the vehicle keys in your hand and the vehicle in front of you, not from the cab and not from memory.
- Check tyre tread across the full width of the tread, not just the centre rib, and check the inner tyre on twin-wheel axles.
- Check tyre pressures rather than kicking the tyre. A visibly flat truck tyre is already a long way past the point at which it started costing you.
- Confirm every exterior light works, including the ones you cannot see from the driving seat: marker lights, number plate lamp, high-level brake light.
- Test the reversing camera and any proximity sensors while stationary, and report a failed camera as a defect rather than driving on mirrors for a fortnight.
- Check mirrors are set for this driver rather than inherited from whoever had the vehicle yesterday.
- Look under the vehicle for fresh fluid on the ground before it is moved, since the puddle will be gone once you drive off.
- Report every defect found, including the ones you can live with. The deferred defect list is only useful if it is complete.
Fatigue and hours, before the schedule is issued
- Check that the route can be driven legally inside the hours available, including loading, waiting and the run back to the depot.
- Count the driver's real day from report time to release, not the driving hours alone. A shift with six hours of waiting in it is still a long shift.
- Check the rest period the driver actually had rather than the one the rota shows, particularly after a night out or a late finish.
- Look at whether the driver has been asked to start earlier than usual after a normal finish, which is where sleep gets taken from.
- Review incident timing against shift hour across the fleet. Clusters late in long shifts are the fleet telling you something about the roster.
- Give drivers a way to say they are too tired that does not require an argument, and check whether anyone has ever used it. If nobody has, it does not exist.
In the cab, on the road
- Set the phone rule to no handheld use at all and enforce it on managers first. A driver who has taken a call from dispatch while moving will not believe the policy.
- Review harsh braking, harsh cornering and over-speeding by segment rather than as a driver total, so a badly designed junction stops being blamed on a person.
- Check seatbelt use rather than assuming it, particularly on short multi-drop work where drivers get out constantly.
- Look at speeding against the actual limit for that road and that vehicle class, not against a single fleet-wide threshold that ignores where the vehicle was.
- Check for tailgating and following-distance events on trunk routes, which is the one behaviour that turns a small mistake into a serious one.
- Watch reversing manoeuvres at customer sites. Most damage happens below walking pace, and almost all of it happens going backwards.
- Confirm that in-vehicle alerts are calibrated to fire rarely enough to be believed. A cab that beeps constantly is a cab where nobody hears anything.
When something happens
- Make sure every driver knows the first three actions after a collision, in order, without looking anything up: make safe, check for injury, report.
- Confirm the reporting number works and is answered outside office hours, and test it yourself rather than assuming.
- Capture the scene before the vehicles are moved where it is safe to do so: position, damage, road conditions, other party details.
- Require near misses to be reported and make it obviously safe to do so. A fleet with no near-miss reports does not have no near misses.
- Check the vehicle's data record after any incident — speed, braking, position — before memories harden into a story that the data will contradict.
- Get the driver a conversation with a human being on the same day, particularly after anything involving injury. A driver who is quietly shaken is a driver going back out tomorrow.
The loop that actually changes behaviour
- Coach within days of the event, while the driver can still remember the junction. A monthly report of last month's mistakes changes nothing.
- Show the driver the actual trip, not a score. A score is an opinion; a replay of the segment is a conversation about a specific piece of road.
- Compare a driver only against others who ran the same lane at similar weight, and show them the comparison group so they can check it is fair.
- Separate the events the driver caused from the events the schedule caused, and fix the schedule ones yourself rather than coaching a driver about your own planning.
- Follow up on whether the coached behaviour changed, and if it did not, ask whether the driver disagreed, did not understand, or could not comply given the route.
- Recognise the drivers with no events as deliberately as you address the ones with many. A safety programme that only ever appears as criticism is a discipline programme.
How to use this checklist
- Split it by owner. Licensing and induction belong to whoever hires. Handover belongs to the driver and the supervisor. Hours and scheduling belong to the planner. Coaching belongs to a named person with time in their week. An unowned safety list is a document.
- Audit rather than collect. A pile of completed inspection forms proves paperwork, not condition. Pick five vehicles a month at random and check them yourself against what was submitted this morning.
- Fix the system items before the person items. If the same manoeuvre at the same site keeps producing damage, coaching eleven drivers individually is the expensive way to avoid moving a barrier.
- Keep the fatigue section honest. It is the one people quietly skip, because acting on it means arguing with the schedule, and the schedule usually has a customer behind it.
Frequently asked questions
They improve it when they start a conversation and damage it when they replace one. A score computed across mixed routes tells a driver that the system does not understand their job, and once that belief exists nothing you build on top of it works. What changes behaviour is a specific event, on a specific piece of road, discussed within days, with the driver allowed to explain. The score is at best a way of deciding whose trip to look at first.
With the same controls and more friction, because the assumptions do not carry. The agency's licence check is not your licence check, and a driver who has driven forty vehicles this year has not driven yours. Verify the licence yourself, do the familiarisation on the specific equipment, and be explicit about the reporting duty. The temptation is to skip all of it because the driver is only here for a day, which is exactly the day it goes wrong.
Tell them the truth, which is that it is both and that the balance depends entirely on how you use it. Be specific about what is recorded, who sees it, how long it is kept, and what it will never be used for. Then honour that. The fastest way to lose the argument is to promise the data is only for coaching and then produce it in a disciplinary. The fastest way to win it is the first time the data clears a driver who was blamed for something they did not do, which happens more often than most fleets expect.
Context, and it cuts both ways. Telematics can tell you a vehicle braked hard; it cannot tell you a car cut in. That distinction decides whether you coach a driver or defend one, and getting it wrong in either direction is costly. What a camera does not add is prevention on its own — footage of an incident is evidence, not a control. It earns its cost when someone reviews it and changes something, and it is dead weight when it is only opened after a claim.
Licensing and vehicle condition, in that order, because those are the two failures that are indefensible afterwards. A driver without the right entitlement or a vehicle with a known unrepaired defect turns an accident into a liability with your name on it. They are also the cheapest controls to establish: both are administrative, neither needs hardware, and both can be running properly inside a month. Behaviour monitoring is worth doing and it is worth doing second.
Run this checklist automatically
Driver Management Software turns these checks into scheduled, assignable work with a full audit trail.