Rental vehicle damage record template: what to include
Use a rental vehicle damage record template for identity, photos and observations. Keep reported accounts and later decisions separate, with an example to copy.
By AuditIt Editorial Team · Fact checked
What to know
- Record one vehicle at one visit, with a clear observation time and location.
- Connect context and detail photographs to the named panel or part.
- Keep observed condition, reported accounts, suspected causes and later decisions separate.
- AuditIt's current incident starter requires 3–12 damage photos; the copyable table suggests additional fields.
A rental vehicle damage record should identify the vehicle, say where and when the condition was observed, show the affected area in context and detail photographs, and separate first-hand observations from reported accounts. Use the template below for one vehicle at one visit, with unknowns left visible rather than filled with guesses.
This is a recordkeeping guide for rental teams documenting visible damage. It is not a vehicle inspection procedure, repair diagnosis, insurance guide or decision about responsibility.
How to make a useful one-visit damage record
- Identify the vehicle and the visit. Record the registration number and any internal vehicle reference, then the recorder, observation location, date, time and time zone. Do not substitute the time of the record for an unknown incident time.
- Make the damage findable. Include a context view and detail views that connect the visible mark to a particular panel or part. Name the side and position consistently in the text and photo references.
- Separate what you saw from what you were told. Describe the visible condition first. Put another person's account under a reported-account heading; label a possible cause as a suspicion, not a finding.
- Link the next review without changing the first account. Include related hire-out, return or earlier damage-record references when available. Keep any later decision identifiable by its decision-maker, date and supporting record.
A copyable rental vehicle damage record template
These are suggested editorial fields, not a claim that every field below is built into AuditIt's starter. Adapt them to your operation and collect only information relevant to the record.
| Field | What to record | Keep clear |
|---|---|---|
| Record details | Record ID, recorder, observation date, time and time zone. | When it was noticed is not necessarily when it happened. |
| Vehicle identity | Registration number and an internal vehicle reference, if used. | Use the same identifier in related records; do not rely on colour alone. |
| Location | Where the vehicle was observed; where the incident happened, if known. | Keep the observation location separate from an unconfirmed incident location. |
| Context photograph | A wider view showing which vehicle area contains the mark. | A close-up alone may not show where the mark sits. |
| Detail photographs | Views that show the visible mark and its surrounding panel. | Describe what the images show, not a cause they cannot establish. |
| Observed condition | Panel or part, side, position, visible mark and photo reference. | State the area observed; do not turn a local observation into a whole-vehicle verdict. |
| Reported account | Who supplied the account, what they said and when. | Label it as reported rather than presenting it as your own observation. |
| Suspected cause | A clearly labelled hypothesis and the reason for considering it, if relevant. | Unknown is an acceptable entry; do not convert a guess into a finding. |
| Related information | Relevant record references; third-party details or a police reference only when needed. | Avoid collecting unrelated personal information. |
| Follow-up decision | Decision, decision-maker, date and supporting record, when a later review is complete. | Keep later decisions identifiable instead of rewriting the original account. |
Swipe horizontally to view every column.
If a location or time is uncertain, say which part is unknown. For example, “Observed in the return bay at 16:40; incident location and time not known” is clearer than presenting the return bay as the place where the damage happened.
Example: a mark noticed at return
The following example is fictional. It demonstrates record language, not a finding about an actual vehicle or customer.
Record details: DEMO-VEHICLE-01, observed in the return bay on 6 September 2026 at 16:40 IST. This is the observation time; the incident time is unknown.
Observed condition: A light-coloured scuff is visible on the lower half of the left rear door. Photo 1 shows the left side and identifies the door; photos 2 and 3 show the scuff and the surrounding panel. The observation covers that area only.
Reported account: The renter said they noticed the mark after a supermarket stop. Record that attribution rather than changing it to “The damage happened at the supermarket.”
Suspected cause: Unknown. A shopping trolley is one possible explanation suggested by the renter; it has not been established.
Related record and follow-up: Refer to DEMO-HIREOUT-01 if a hire-out record exists. Leave the review decision pending until the responsible person records it separately.
Keep observations, accounts and decisions distinct
Four headings can help a reviewer understand the status of each statement. They are a suggested way to organise your notes or customise a form, not four default fields supplied by the starter.
- Observed: What the recorder directly saw in the stated area, with a photo reference where useful.
- Reported: What another person said, clearly attributed to them.
- Suspected: A possible explanation, explicitly unconfirmed.
- Decided: A later review outcome, with the decision-maker, date and basis.
A text field labelled “What happened” does not verify the account entered into it. If all you know is that damage was noticed, say that. Do not let the label push you into inventing an event, time or cause.
When to use a hire-out and return record instead
A one-visit incident record answers “What was recorded at this visit?” A paired hire-out and return record supports comparison between two checkpoints. Use the latter when the task is to record both sides of a rental, and link a separate damage record when additional detail is needed.
For matching views and checkpoint fields, see Vehicle hire-out and return: a comparable condition record.
Two sets of photographs do not by themselves establish why a change occurred or who is responsible. Keep the comparison and any later decision separate.
What AuditIt's vehicle incident starter includes
AuditIt's vehicle rental catalog includes a Vehicle incident record starter using a one-visit, record-only workflow. Its current defaults are:
- Required text: Registration number, Where it happened and What happened.
- Required damage photographs: at least 3 and at most 12.
- Optional wider-scene photographs: 1–4 images if the field is used.
- Optional walk-round video: up to 1 video, with a 90-second limit.
- Optional text: Third party details and Police reference.
The photo count is a starter setting, not a universal standard for damage documentation. Likewise, the video field's name is not a claim that a video replaces an inspection.
The starter's location label is “Where it happened”. If the incident location is unknown, make that clear; keep the place where the condition was observed distinct in the description or in a customised field. Do not fill in a guessed incident location just to complete a form.
Adopting a starter creates an organisation-owned copy that can be customised. If you want the separate headings in the copyable table, add or adapt fields in your copy. Check its current requirements before use, because an adopted template may differ from the starter defaults described here.
What this record cannot decide
Related templates and next steps
For equipment beyond vehicles, use the equipment damage report template as a starting point for record structure.
For help adapting your own fields, read How to build an audit workflow template.
Ready to set up a one-visit record? Create an AuditIt workspace and adapt the Vehicle incident record starter to the fields your team needs.
Direct answers
Frequently asked questions
What should a rental vehicle damage record include?
Include vehicle identity, the recorder, observation location and time, context and detail photographs, and a description of the visible condition. Keep reported accounts, suspected causes, related records and later decisions clearly labelled. The table in this guide is an adaptable recordkeeping template, not a universal required form.
How should I describe vehicle damage without guessing the cause?
Name the panel or part, side, position and visible mark, then refer to the relevant photographs. Attribute anything another person told you. If the cause or incident time is unknown, say so; record a possible explanation as a suspicion rather than a finding.
Is a damage record the same as a hire-out and return record?
No. A one-visit damage record captures the condition and account recorded at one visit. A hire-out and return workflow records two checkpoints for comparison. Link the records when useful, without treating a visible difference as an automatic decision about responsibility.
How many damage photos does AuditIt's vehicle incident starter require?
The current starter requires at least 3 and allows up to 12 damage photographs. Its wider-scene photo field is optional and allows 1–4 images when used. These are starter defaults, not a universal documentation standard; an organisation's adopted template may have different settings.
Does the vehicle incident starter include separate observed, reported and suspected fields?
Not by default. The current starter includes a required What happened long-text field. You can label those categories within the account or customise your organisation-owned copy with separate fields. The headings in this guide are editorial suggestions, not a description of extra default fields.
Can a damage record determine fault or insurance coverage?
No. AuditIt does not determine liability, and this guide does not assess insurance coverage. The record organises observations and submitted accounts for review; it should not present a suspected cause or a later decision as something the original photographs proved.
- vehicle rental
- damage record
- incident record
- condition records
- record only
