What to put in a drone inspection report

RotorRun team · October 2026

Clients rarely want every photo you took. They want to know what you found, where it is, and what to do next. A report that answers those three questions quickly gets read and gets you rehired.

1. Job details

Client, address, date, pilot, aircraft and weather. It takes a minute to record and answers the first questions anyone asks later.

2. Findings first

Put a short summary at the top: what you inspected and the main issues, in plain language. Someone who reads only that paragraph should still understand the result.

3. Photos with context

A photo of a damaged shingle means little without its location. For each key image, say where on the structure it was taken, which direction the camera faced and when. Keep wide shots next to close-ups so the reader can place the problem.

4. Conditions and limits

Note anything that limited the inspection, such as areas you could not reach or poor light. It protects you and sets honest expectations.

5. Clear delivery

Send one organised package instead of a folder of files and a separate email. A PDF suits clients who file reports; a web page suits those who want to click through the photos.

Where the time goes

Most of the effort is assembling: sorting photos, matching them to notes and formatting. If your photos and notes already live with the job, the report is mostly arranging what you have. RotorRun builds a delivery packet from the job's own photos, notes and checklist, and exports it as a PDF or a client web page.