Coverage Download Guides Toolkit Open the map
Home › Toolkit › Examples › Storm Damage Drone Inspection Report Example

Storm Damage Drone Inspection Report Example

Opening sections, freeWritten from 05 Insurance and storm damage

This is a worked example, not a real survey. Every name, address and finding is invented. It shows how the template reads once the placeholders are filled in and the guidance notes are deleted.

Storm Damage Assessment

14 Lindenweg - claim MK-2026-88213

Report referenceAER-2026-233
Claim referenceMK-2026-88213
Insurer / instructing partyMeridian Kasko Versicherung
PolicyholderHerr T. Bauer
Risk address14 Lindenweg, 4020 Linz
Reported perilStorm, wind gusts to 118 km/h
Date of loss3 July 2026
Date of inspection9 July 2026
Inspected byA. Petrov, operator BGR-OP-4471

1. Executive summary

The property was inspected by unmanned aircraft on 9 July 2026, six days after the reported date of loss.

11 items of damage were recorded. Of these, 7 are consistent with the reported storm, 3 appear pre-existing or attributable to wear, and 1 could not be attributed from aerial imagery.

Requiring immediate attention
  • D-01 - Missing tiles, north slope, underlay exposed and torn. Water ingress is likely at the next rainfall. Temporary covering recommended. The policyholder was advised on site and the insurer notified the same day.

Areas not assessed. The valley gutter between the main roof and the rear extension could not be seen from any safe flight position. Graded NA.

2. Scope

Visual inspection by unmanned aircraft of the roof, elevations and curtilage to record the extent and nature of damage reported under claim MK-2026-88213.

This report records observations. It does not determine liability, causation or quantum. Attribution grades in section 5 state what the evidence is consistent with. The decision on cover rests with the insurer and its adjuster.

Not within scope: internal inspection, moisture testing, structural assessment, cost of reinstatement, policy interpretation, cause of any pre-existing defect.

A worked finding, from later in the report

D-01 - Missing tilesS2
LocationNorth slope, approx. 2 m below the ridge, bays 4-6
ObservationNine tiles missing over approx. 1.8 m2. Underlay exposed and torn at two points. Displaced tiles found in the garden to the south-east.
AttributionA - consistent with the reported event. Damage is confined to the windward slope. Break edges are clean and unweathered, and the displaced tiles lie downwind of the gap.
If untreatedWater ingress at the next rainfall.
RecommendationTemporary covering now; re-tile the affected bays.
EvidenceIMG_0512, IMG_0513

The rest of this report

The sections below are in the full document, which ships as an editable .docx and a finished PDF inside the pack.

  • 3. Limitations
  • 4. Method and evidence
  • 5. How findings are graded
  • 6. Damage recorded
  • 7. Damage schedule
  • 8. Recommended next steps
  • Appendix A - Evidence register
  • Appendix B - Operator details
When would I send this?

As soon after the event as the weather allows, to the loss adjuster or the broker handling the claim - and separately from any repair quote, which would compromise its independence. The adjuster is not asking what is wrong with the roof; they are asking whether this specific storm caused it, so anything that reads as a general condition survey weakens the claim. A late report invites the argument that the damage predates the event.