Vehicle return form: what it should actually contain
A return form that's too long ends up half-filled-in; one that's too vague is useless exactly when you need it (a dispute, a breakdown, an audit). Here's the information that actually makes a difference.
Starting and ending mileage, never a single number
Asking only for the final mileage doesn't let you check the trip's consistency or calculate the distance covered on that specific occasion. Both values (start and end) allow a cross-check with the next trip.
Fuel status, not just "full or not"
Specifying whether the tank was refilled, wasn't, or the vehicle is electric and was plugged back in, avoids unpleasant surprises for the next person and disagreements over who was supposed to refuel.
An incident report that doesn't get lost in a separate email
An incident reported by text or informal email to one person is easily lost. Attached directly to the return form for the relevant trip, it stays traceable and dated, and can trigger an automatic alert to the manager.
Frequently asked questions
Should every field be required?
Starting and ending mileage should be required (it's the most useful data). The incident report, on the other hand, should only need detail if an incident is actually flagged — no required field for a case that doesn't apply.
Who should have access to completed return forms?
At minimum the fleet manager; some tools, like Flotalyo, also block the person concerned from making a new booking until their own return form for the previous trip is submitted, which keeps completion rates close to 100%.
A return form that actually gets filled in
Set up your first fleet in just a few minutes.