Shared vehicles have a way of coming back with less fuel, a new scratch and no note. I want one record at the start of every trip: who has it, where it goes, what state it was in. Then a scratch has a date next to it.
The trip
Purpose, destination, dates, passengers and distance. They show whether the trip fits the vehicle, and who else may want it that day.
The driver
Name, phone and a licence confirmation. The tick box is the driver's own statement. The form does not ask for a licence number, and checking licences stays with you.
The vehicle
Fuel, odometer and damage seen before leaving. This is the baseline that makes a later question simple to answer.
Who fills it and who reads it
Drivers fill it in. A fleet or office manager reads the CSV, checks the diary and replies. A driver's AI might ask: "Where are you going?" Then "When do you pick it up?" Then "Is there damage on the vehicle?" It shows the answers and sends them only after a yes. See agent-fillable forms.
A tip
Keep your own diary as the source of truth, because this fleet form shows no availability. Gear that travels with the vehicle can go through an equipment checkout form. Damage and repairs belong in a work order request. More tools are in IT and operations forms.
Questions
Does the form check that the vehicle is free?
No. It collects a request. You check your diary against the pickup and return dates, then reply with a yes or a no.
Why does it not ask for a licence number?
Government ID numbers are left out on purpose. The tick box records the driver's statement, and you check licences through your own process.
How do I log damage found on return?
Ask the driver to send a second entry on return and describe the new damage in the last box. Sort the CSV by `driver_name` to see both entries together.