Technician On-Site Property Damage Report Form

Use it as soon as accidental damage is discovered during or immediately after the visit, while the details are still fresh. It is meant for one incident at one customer site, not for general service notes. If the issue involves injury, unsafe conditions, or a broader safety event, the form should still capture the basics and route the case to the right internal process.

The technician who observed the incident should usually complete it, with a supervisor reviewing it if needed. If the technician cannot finish it on-site, a dispatcher, field manager, or claims coordinator can complete the record from the technician’s notes and photos. The key is to preserve the original facts and avoid rewriting the incident after the fact.

It covers accidental damage to customer property during a visit, such as broken fixtures, scratched surfaces, damaged equipment, or accidental impact during work. It also captures the work activity in progress, the location, witnesses, and immediate actions taken. It is not a replacement for a legal claim form, insurance packet, or incident report for employee injuries.

Use it every time a technician causes or may have caused customer property damage, even if the damage seems minor. Consistent use creates a reliable audit trail and reduces gaps when a claim is reviewed later. Skipping small incidents is a common reason records become incomplete and harder to defend.

Include clear photos of the damaged item, the surrounding area, and any relevant context such as the equipment position or work area. Add notes that explain what each photo shows and whether any additional evidence exists, such as job tickets or witness statements. Avoid uploading unrelated images or excessive personal data that is not needed to document the incident.

It supports data minimization by collecting only the details needed to document the incident and begin follow-up. If you collect names, contact details, signatures, or photos that may include PII, the form should include a clear notice about what happens after submission and who can access the record. Keep fields required only where necessary and use conditional logic so users do not see extra questions unless they apply.

Yes. You can adjust the damage types, add service-specific work activities, or change the follow-up routing based on your operations. For example, appliance, HVAC, telecom, and facilities teams may need different incident categories or different supervisor notification paths. The structure should stay focused on the incident, evidence, and next steps.

Common integrations include ticketing systems, field service platforms, document storage, and claims workflows. A submission can create a case, notify a supervisor, attach photos to the job record, and preserve an audit trail. If your process uses e-signature or approval steps, keep the acknowledgment and signature fields tied to the same incident record.

A structured form captures the same facts every time, which makes incidents easier to review, compare, and route. Ad-hoc messages often miss the date, time, location, witness names, or photo context, and they are harder to search later. This template turns a messy incident into a consistent record that can support follow-up without back-and-forth.