Fleet Manager Daily Checklist
A fleet manager's day is decided in the first thirty minutes and lost in the last thirty. This checklist covers what to look at before the keys go out, what deserves an interruption during the shift, and what has to be closed before you go home.
The daily job is not a job description. It is a sequence of small decisions made under time pressure, most of them about information that arrived while you were asleep. The overnight alert nobody read. The vehicle that came back on a recovery truck at eleven. The driver whose licence check was due last Thursday.
What makes the day go wrong is almost never a dramatic failure. It is a vehicle dispatched with an expired test certificate because the reminder went to somebody's old mailbox, or a route assigned to a driver with two hours of driving time left on the card. Both are catchable in the first half hour by someone who knows where to look.
This list assumes a depot supervisor or fleet manager with vehicles going out in the morning and coming back at night. Adapt the timings to your shift pattern, but keep the order: what changed overnight, what is about to leave, what is happening now, what must be closed. Reversing that order is how the end of the day becomes tomorrow's problem.
34 checks across 5 sections
First thirty minutes: what changed overnight
- Read the overnight alert queue oldest first. The event from 02:00 is the one nobody has looked at, and reading newest first means you never reach it.
- List every vehicle that has not reported a position since the previous shift ended, and separate a flat battery from an unplugged device before you call anyone.
- Confirm each vehicle booked out for today is physically in the yard, not still sitting at a roadside or on the back of a recovery truck.
- Work the vehicle-off-road list one line at a time and ask two questions of each: what exactly is it waiting for, and whose name is against getting it.
- Check for any document expiring inside the next seven days — test certificate, insurance, tachograph calibration, operator disc — before that vehicle is dispatched.
- Review fuel level changes at overnight parking locations, and look specifically at drops recorded somewhere that is neither a depot nor a fuel station.
- Scan any incident, damage or third-party contact reported after you left yesterday, and confirm somebody has already started the claim clock.
Before the keys go out
- Confirm every route has a named driver and that the driver actually holds the licence category and any specific entitlement the vehicle needs.
- Check remaining driving time for each driver against the route they have been given, not against a nominal shift length that assumes no traffic.
- Verify that agency and temporary drivers have had familiarisation on this specific vehicle, particularly the tail lift, the reversing aids and the handbrake interlock.
- Read the walkaround inspection submissions. Read the defects raised, not the count of vehicles that passed.
- Query any inspection completed in an implausibly short time. A ninety-second walkaround on an articulated vehicle did not happen.
- Compare today's tyre defects against yesterday's. A repeat pressure complaint on the same axle is a slow puncture, not a driver being difficult.
- Confirm any vehicle carrying a deferred defect is still legal to run with it, and that the deferral has a date on it rather than an intention.
- Check that keys, fuel cards and access fobs went to the driver named on the route, and not to whoever arrived first.
During the shift: what earns an interruption
- Respond to panic and duress alerts inside the window your own policy promises, and record the time you responded rather than the time you noticed.
- Act on a vehicle leaving a customer site while its load still shows as undelivered — that is a two-minute phone call now or a claim next week.
- Watch for any vehicle stationary on a live route beyond its planned dwell time, and call the driver before the customer calls you.
- Group harsh braking and acceleration events by location before you group them by driver. Three drivers braking hard at the same roundabout is a route defect.
- Check that every breakdown has two plans running in parallel: one for recovering the vehicle and one for moving the load that is sitting inside it.
- Confirm temperature-controlled units are holding setpoint on the road, not just that the unit is switched on.
- Reroute around a known closure once, at the depot, rather than letting eleven drivers each discover it individually.
Cost and fuel, while the day is still recoverable
- Reconcile yesterday's fuel card transactions against the tank rises they should have produced, and leave anything unmatched open rather than tidying it away.
- Check idle time by location. Ninety minutes of engine-on time at one loading bay is a scheduling problem you can fix this week.
- Look at any vehicle whose consumption sits well outside the group of vehicles running the same lane at the same weight today.
- Confirm depot bowser issues have been recorded against a registration number and not just a shift total in a logbook.
- Check tolls, penalty notices and congestion charges received today and match each to the trip and driver that incurred it while the day is still identifiable.
Before you leave: close the day
- Confirm every trip opened today is closed. Chase the open ones before the driver goes home, because tomorrow he will not remember.
- Post today's defects into the workshop queue with a priority and an owner attached, rather than into a shared inbox.
- Check tomorrow's service bookings against tomorrow's route plan so no vehicle has been promised to both the workshop and a customer.
- Note which vehicles are staying out overnight, where they are parked, and whether that was planned or has quietly become normal.
- Confirm proof of delivery has been captured for every completed drop, and chase the missing ones today while the driver still has the paperwork.
- Check that any vehicle returning damaged has been photographed before it is washed, moved or parked behind three other trucks.
- Write down the one thing that went wrong today and why. The monthly review needs a diary, and nobody can reconstruct four weeks of small failures from memory.
How to use this checklist
- Run the first section before you open your email. Email is a queue of other people's priorities; the alert list is a queue of yours.
- Time-box it. This is a twenty to thirty minute routine, not a morning. If a section regularly overruns, that section is describing a systemic problem rather than a daily task, and it belongs in the monthly review instead.
- Delegate by section, not by item. A depot with a transport clerk can hand over the dispatch readiness block cleanly. Splitting individual lines between two people means both assume the other did it.
- Keep the items you skip. If you skip the same line for three weeks and nothing bad happens, delete it deliberately. A checklist nobody trusts gets ticked without being read, which is worse than having no checklist.
Frequently asked questions
Alerts tell you that something happened. They do not tell you that something failed to happen, and most of the expensive items on this list are absences: the inspection that was not submitted, the trip that was never closed, the vehicle that stopped reporting. A system can only alert on the absence it has been configured to notice. The checklist is the sweep for everything else.
Twenty to thirty minutes for the morning blocks, and ten at the end of the day, on a depot of a few dozen vehicles. If it takes two hours, the problem is not the checklist. It usually means exceptions are not being filtered, so you are reading every event instead of the ones that broke a rule, and the fix is in alert configuration rather than in your calendar.
At your handover, not at midnight. Run the overnight block at the start of whichever shift you supervise, treating the previous shift as the overnight. The important property is that every alert gets read by exactly one person who owns it, and that nothing falls in the gap between two supervisors both assuming the other saw it.
The date-driven ones. Document expiry, service due, licence recheck and calibration dates are pure calendar arithmetic and a person should not be doing them. Automate those and keep the judgement items on the list: reading defects, deciding whether an idle pattern is a bay problem, deciding whether a breakdown needs the load moving. Those do not automate, and pretending otherwise is how fleets end up with dashboards nobody acts on.
It shortens the first block and it makes the last one enforceable. Overnight events arrive as a filtered exception list rather than a raw feed, document expiries surface before they bite, and open trips, missing inspections and unmatched fuel transactions stay visible as open items instead of quietly disappearing. The judgement calls are still yours. The searching is not.
Run this checklist automatically
Fleet Management Software turns these checks into scheduled, assignable work with a full audit trail.