The vehicle is back in the yard, the driver has handed over the keys and the next booking is already waiting. It looks as though the journey is complete.
But the final mileage has not been recorded. Nobody has confirmed the fuel level. A new scrape on the rear panel has been mentioned in passing, and a warning light seen during the trip sits in a private message on a supervisor’s phone.
The vehicle has returned, but the job is still open.
A disciplined return handover closes that gap. It gives the next driver, the fleet coordinator and the business a dependable record of the vehicle’s condition and the work that must happen next.
Treat the return as a separate workflow
Dispatch and return are two different operational moments. At dispatch, the team confirms that a vehicle, driver and job are ready to leave. At return, the team must reconcile what actually happened.
Create a clear return status rather than moving straight from “on the road” to “available”. Useful stages might include returned, awaiting inspection, action required and ready for allocation. The exact labels matter less than their meaning: everyone should know whether the vehicle is physically present, safe to allocate and fully closed out.
Give one person responsibility for completing the handover. A shared responsibility often becomes nobody’s responsibility when the depot is busy.
Capture the final mileage first
Mileage is a simple number with several operational consequences. It helps the team understand vehicle use, reconcile the journey and keep future servicing decisions grounded in current information.
Record the odometer reading while the vehicle is present, not from memory at the end of the week. If the reading differs significantly from the expected route, do not silently change it to match the plan. Confirm whether there was a diversion, an additional stop, an incorrect starting figure or a recording mistake.
The aim is not to investigate every small variation. It is to keep an accurate record and make unusual differences visible while the driver can still explain them.
Check fuel, keys and required items
A returned vehicle can still be unready for its next job. Confirm the fuel level or charging position according to your fleet policy, then record whether refuelling or charging is required.
Check that the expected keys, fuel cards, access devices, permits and other issued items have returned. If something is missing, name the item and assign the follow-up immediately. “Driver to bring it tomorrow” is not a closed action unless somebody owns that contact and the next team can see the dependency.
Where proof of delivery, collection notes or journey paperwork is required by your process, confirm that it has been submitted to the correct owner. The fleet return should connect the physical vehicle with the administrative close-out.
Record condition without blame
A short, consistent condition check is more useful than a rushed conversation about whether the vehicle “looks fine”. Walk around the vehicle and note visible changes, tyre concerns, damaged lights, windscreen marks, interior issues and anything the driver experienced during the journey.
Describe what was observed, where it appears and when it was reported. Avoid turning the handover into an argument about responsibility. The immediate purpose is to capture accurate information and decide the next action. Any investigation can follow the organisation’s normal process.
Photographs can support the record where your policy allows them, but a photograph should not replace a clear written note. A future reader needs to understand why the image matters.
Separate a defect from a maintenance action
Drivers often notice early signs of a problem before a breakdown occurs: a warning light, unusual vibration, slow tyre-pressure loss or a door that no longer closes properly.
Record each concern separately. Decide whether it prevents further use, requires inspection before the next allocation or can be scheduled under the normal maintenance process. Then assign an owner and due point.
Do not leave an important defect inside a general return note. A visible action should show what needs attention, who is responsible and when the vehicle can be reconsidered for service.
Use a practical example
Consider a van returning from a two-day delivery route. The driver reports a dashboard warning that appeared intermittently and hands over one of two issued access tags. The vehicle is due to leave again early the next morning.
Without a return workflow, the keys may be placed on the hook and the van marked available. The next driver discovers the missing tag at the gate and the warning returns on the road.
With a structured handover, the coordinator records the final mileage and fuel level, marks the access tag as outstanding and places the vehicle in “action required”. The warning is assigned for inspection, while a colleague contacts the driver about the tag. Only after the relevant checks are completed does the status change to ready for allocation.
The process takes a few minutes and protects the next job from inheriting unresolved work.
Close every return with a next state
A return is complete only when the record shows what happened and what happens next. Before closing it, confirm:
- the final mileage and fuel or charge position;
- the return of keys, cards and required items;
- the vehicle’s reported and observed condition;
- any documents still outstanding;
- each defect or maintenance action and its owner; and
- whether the vehicle is ready, restricted or unavailable.
This makes the next allocation a deliberate decision, not an assumption based on where the vehicle is parked.
MT Fleet is MyTalent’s offering for the vehicles, people and day-to-day needs of a fleet operation. Explore MT Fleet or talk to our team to discuss the capabilities available for your organisation.
A journey does not end when the engine stops. It ends when the mileage, condition, equipment and next action are clear.