TEMPLATE · Operations
Vehicle inspection checklist
A pre- or post-use check of a vehicle: mileage, fuel, lights, tires, fluids, damage, with photos and a supervisor's sign-off.
Complete this check before (or after) using the vehicle. Report anything that is not right; do not drive a vehicle that is unsafe.
The vehicle and driver
- Driver's nametext
- Emailemail
- Vehicletext
- Check typechoiceBefore use · After use · Weekly check
- Odometer readingtext
- Fuel or chargechoiceFull · Three quarters · Half · Quarter · Low
The check
- LightschoiceOK · Needs attention
- TireschoiceOK · Needs attention
- BrakeschoiceOK · Needs attention
- Mirrors and windowschoiceOK · Needs attention
- Fluids and warning lightschoiceOK · Needs attention
- Seat beltschoiceOK · Needs attention
- Safety kitchoiceYes · Something missing
- Damage or problemstext, optionalWhere and what. Leave empty if there is none.
- Photosfile (PDF or picture), optionalA PDF or a picture (PNG or JPEG). It is kept exactly as you upload it.
- To the best of my knowledge the answers above are correct, and I have reported every problem I found.tick box
Signature
- Driver signaturesignature
- Driver date signeddate signed
For supervisor use
- Decisionchoice · SupervisorFit to drive · Fit to drive after repair · Not fit to drive
- Notetext, optional · SupervisorOptional. Shown on the signed copy.
- Supervisor signaturesignature · Supervisor
- Supervisor date signeddate signed · Supervisor
What people see
The template, the way the person you send it to fills it in.
In this template
What is on the page.
- The vehicle and driver: 6 fields
- The check: 10 fields
- Signature: 2 fields
- For supervisor use: 4 fields
It is your own copy in your workspace. Change any of it before you send.
Send it from code
Send the vehicle inspection checklist template from your own code.
Make your own copy once, then send it to the person you name. A test key sends only to you.
npx docustay templates customize vehicle-inspection-checklist --name "Vehicle inspection checklist"
# prints the new template's id; then send it as a test:
npx docustay send --test $DOCUSTAY_TEMPLATE_ID --party 'signer=Name <email>'curl -X POST "$DOCUSTAY_URL/api/v1/documents/send" \
-H "Authorization: Bearer $DOCUSTAY_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"templateId":"$DOCUSTAY_TEMPLATE_ID","parties":[{"seat":"signer","name":"Name","email":"name@example.com"}]}'What you keep
A sealed copy and its record.
Each person who signs gets the sealed PDF with a certificate of completion, and so do you. Search them in your workspace and read each one by its own record.
Questions
Quick answers.
Who fills it in?
The person you send it to. They are the driver in this template: they type their own name and email, fill in each box and sign. Then the supervisor you choose on your team adds a decision and counter-signs.
Can I send it to many people at once?
Yes. Send to a list sends your own copy to each person on it, and each person signs their own copy.
Can I change the questions?
Yes. In your workspace it is your own copy: add, remove or reword any field, then send it. The original is never changed.
Can people attach files?
18 fields make up the vehicle inspection checklist template. Where it has a file box, people may attach a PDF or a picture, and it is stored exactly as they upload it and never converted.
Is this legal advice?
No. The vehicle inspection checklist template is a starting point in plain words. Change what does not fit before you send it.
More like this
More operations templates.
Incident report
What happened, when and where, who was involved, any injury or damage, what was done straight away, with witnesses and photos, reviewed by a supervisor.
See every field →OperationsService request or work order
Request work: what needs doing, where, how urgent, access arrangements, photos, and the technician's sign-off on completion.
See every field →OperationsVisitor sign-in
A visitor's name, organization, who they are seeing, arrival time, vehicle and agreement to the site rules.
See every field →