Property Damage Incident Report Form
A Property Damage Incident Report Form for documenting what was damaged, where it happened, who was involved, and what follow-up is needed. Use it to create a clear record for facilities, insurance, and safety review.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Facilities Management · Retail · Manufacturing · Logistics And Warehousing · Property Management
Overview
This Property Damage Incident Report Form captures the facts needed to document a damage event in one place: when it happened, where it happened, what was damaged, who saw it, what evidence exists, and what immediate actions were taken.
Use it when an incident could lead to repair work, an insurance claim, a police report, or an internal safety review. The template is especially useful when multiple people may later describe the event differently, because it creates a consistent record with date/time fields, location fields, witness fields, photo uploads, and follow-up notes. The submission notice also helps set expectations about what happens after the report is sent.
Do not use this form as a catch-all for every workplace issue. If there was no property damage, a different incident or near-miss form is a better fit. If the event involves sensitive personal data, collect only what you need and keep the wording narrow. For injury-heavy events, use a separate injury or medical intake process and keep this form focused on the property damage itself.
The template works best when the organization wants a simple, auditable record that can move from discovery to review without relying on scattered emails or chat messages.
Standards & compliance context
- Keep the form aligned with GDPR data minimization by collecting only the PII needed to document and investigate the damage.
- If witness or involved-person details are collected, include a clear disclosure about how the information will be used and who can access it.
- Use accessible labels, validation messages, and upload controls that meet WCAG 2.1 AA expectations for public-facing or employee-facing forms.
- If the form is used in a workplace safety process, preserve an audit trail of submission time, reviewer actions, and follow-up status.
- If injury details are included, keep the scope limited to what is necessary and route medical information through the appropriate separate process.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section tells the reporter exactly what happens after submission so they know who receives the report and what next step to expect.
-
What happens after I submit?
Your report will be logged for review, and any required follow-up actions may be assigned to the appropriate team. If you include contact details, they may be used only for incident follow-up.
Incident Details
This section captures the core facts of the event, which are the foundation for repair decisions, claims, and later review.
- Date of Incident
- Time of Incident
- Location of Damage
- Whose property was damaged?
- Type of Damage
- Describe the Damage
People Involved and Witnesses
This section records whether anyone was injured or observed the incident, which helps verify the timeline and scope without over-collecting information.
- Did anyone get injured?
- Injury Details
- Were there witnesses?
- Witness Names
Photos and Evidence
This section preserves visual proof and supporting materials before the scene changes, which is critical for accurate review.
-
Upload Photos
Attach clear photos of the damage, surrounding area, or any relevant evidence.
-
Additional Evidence
Optional supporting documents such as repair estimates, police report, or incident notes.
Immediate Actions and Follow-Up
This section documents what was done right away and what still needs attention so the report turns into action instead of just a record.
- Immediate Actions Taken
- Was a police report filed?
- Police Report Number
- Follow-up Needed
- Follow-up Notes
How to use this template
- 1. Set the submission notice to explain where the report goes, who reviews it, and whether the reporter should take any immediate safety or preservation steps after submitting.
- 2. Configure the incident details section with date picker, time field, location field, property owner field, damage type multi-select, and a short description field for the facts of the event.
- 3. Add conditional logic so injury fields appear only when injury_occurred is marked yes, and keep witness fields optional unless witnesses were actually present.
- 4. Require photo uploads or additional evidence only when available, and prompt the reporter to attach images taken at the time of discovery rather than after cleanup.
- 5. Route the completed report to the right manager, facilities lead, security contact, or claims owner, then review follow-up_needed and follow_up_notes before closing the incident.
- 6. Use the report as the starting point for repairs, police reporting, insurance documentation, and any corrective action tracking that follows.
Best practices
- Use a date picker for incident_date and a time field for incident_time so reporters do not enter vague free text.
- Mark only the truly necessary fields as required and keep optional fields available for details that may not apply to every incident.
- Use conditional logic to hide injury fields unless an injury actually occurred, which keeps the form shorter and reduces bad data.
- Ask for the exact incident location, not just a building name, so facilities or security can find the site without follow-up.
- Capture witness names only when witnesses_present is yes, and add a note that anonymous reporting may be allowed if your process supports it.
- Request photos before cleanup or repair begins, because later images often miss the original condition of the damage.
- Keep damage_description factual and specific, and avoid blame language or assumptions about fault.
- Include a clear what happens after I submit line so the reporter knows whether the form triggers review, repair, insurance, or police follow-up.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kinds of incidents should this form be used for?
Use it for any event where company, tenant, customer, or third-party property is damaged and you need a written record. That includes broken fixtures, vehicle damage, equipment damage, water leaks, vandalism, and accidental damage during work activities. It is not the right form for injury-only events unless property damage also occurred.
Who should complete the report?
The person who discovered the damage, the employee involved, or the supervisor on site can complete it, as long as they can enter accurate facts. If the incident is serious, have a manager or safety lead review the report before it is closed. The key is to capture the details while they are still fresh.
How often should this form be used?
Use it every time a reportable damage event occurs, even if the damage seems minor at first. Small incidents often become important later when repair costs, insurance claims, or liability questions come up. A consistent process also helps spot repeat issues in the same location or equipment.
Does this form support insurance or police follow-up?
Yes. The template includes fields for police report status, report number, photos, and additional evidence so the record can support internal review or an external claim. If police were not contacted, the form still captures the reason through the follow-up notes. Keep the facts objective and avoid guessing at fault.
What should we avoid collecting in this form?
Only collect the information needed to document the incident and support follow-up. Avoid unnecessary PII, such as full personal identifiers, and do not add unrelated medical details if no injury occurred. If witnesses or involved people are named, make sure the form includes a clear notice about how the information will be used.
Can this form be customized for different sites or departments?
Yes. You can add conditional logic for site-specific fields, such as vehicle number, asset tag, room number, or contractor name, without showing every field to every user. That keeps the form shorter and improves completion quality. It also helps you align the template with facilities, operations, or security workflows.
How does this compare with handling damage reports by email or chat?
Email and chat are easy to start but hard to search, standardize, and audit later. This template gives you consistent fields for date, location, witnesses, evidence, and follow-up so each report is easier to review and compare. It also reduces missing information that usually causes delays in repair or claim handling.
What happens after someone submits the form?
The submission notice should tell the user whether the report goes to facilities, safety, security, or a manager, and whether they should expect a confirmation. That matters because people often need to know if they should also call emergency services, file a separate claim, or preserve the scene. A clear handoff line prevents duplicate or missed reporting.
Related templates
Ready to use this template?
Get started with MangoApps and use Property Damage Incident Report Form with your team — pricing built for small business.
