MASTERPAGE / GUIDES
Recording vehicle handovers and customer changes
A handover record connects a vehicle to a particular usage period. Clear history helps review charges that arrive later without automatically assigning them to the customer currently displayed in the vehicle file.
Record an event instead of replacing a name
Simply changing the customer name hides the previous relationship. Record handover as an event with date, time, vehicle, agreement, document reference and approval details. A return or new agreement should create another event preserving the previous period. The project should define how open or overlapping periods are identified and corrected.
Capture what operational review needs
Fields may include mileage, condition, notes and supporting image or document references if agreed. Retain necessary information and define who may see attachments. An operational record does not replace a handover contract or official evidence requirements. Recording a note does not automatically establish a customer’s responsibility.
Review charges by incident time
A toll or fine may arrive after the customer’s association has ended. Compare the incident date and time with the source, handover history and agreement. If dates conflict, keep the item under review and assign someone to obtain evidence. Statement arrival date alone should not determine the usage period.
A practical checklist
- Vehicle, agreement and customer linked by clear identifiers.
- Handover and return times with an explicit timezone.
- Supporting references, approval and only necessary notes.
- Review of overlapping periods before charge allocation.
Common questions
Is a date without time sufficient?
It may be sufficient for some operations, but time matters when multiple handovers occur on the same day or charges need time-based matching.
Does a handover entry establish legal responsibility?
It provides information for review but does not decide responsibility alone. Supporting documents, the agreement and applicable procedures matter.