Inspection scope and handoff
What should a drone inspection deliver?
Choose the structure and assignment. Build the views, records, field controls, QA checks, and professional handoff before you quote or fly.
CAPTURE · INDEX · REVIEWThe short answer
Deliver evidence another professional can verify.
A drone inspection is useful when every image answers three questions: what asset is this, where is the component, and what should the reviewer examine? The package needs complete coverage, a traceable index, retained originals, stated conditions, and a clear record of anything the aircraft could not see.
The same aircraft can collect roof, solar, bridge, tower, and facade imagery. The assignment is not the same. Each asset has its own component names, access hazards, review authority, supporting methods, and definition of complete evidence.
Get the owner's method and reviewer before choosing the flight pattern, sensor, report, or price.
Build the assignment
Start with the asset and reviewer.
The aircraft comes later. Choose the structure, the reason for the visit, and any specialist data the client expects.
Example file name
SITE-BLDG01-FACET-N-PENETRATION03-DETAIL-20260827.jpgReplace the fields with the client's asset hierarchy. Do not force your own names into a system the reviewer already uses.
Reviewer-ready capture scope
Roof / property
Baseline record
Baseline record for roof / property: build a component-indexed evidence set that the named reviewer can locate, verify, and compare without relying on the pilot's memory.
- Capture views
- 9
- Record fields
- 7
- Package items
- 7
Capture sequence
- 01Property orientation view showing the building, access, and surrounding hazards
- 02Full-roof nadir overview with every facet visible or logged as an exception
- 03Oblique overview of each roof facet with its ridge, eave, rake, hip, and valley context
- 04All penetrations, flashing, drains, scuppers, gutters, skylights, and rooftop equipment
- 05Context and detail pair for every visible condition selected for review
- 06All building elevations where roof edge, drainage, flashing, or impact context matters
- 07Obscured, inaccessible, reflective, or unsafe areas recorded as coverage exceptions
- 08One orientation key that connects the site, asset hierarchy, and capture direction
- 09Representative normal-condition context, not only candidate problem areas
Review boundary
The roofer or building professional owns condition and repair conclusions. The adjuster or insurer owns claim decisions. A qualified thermographer owns thermal interpretation.
- Visible imagery does not establish cause, code compliance, repair scope, material quantity, coverage, or settlement value.
- A model or measurement report needs independent validation and does not become a legal survey or engineering conclusion.
This builder is a scoping aid, not a flight authorization, engineering procedure, claims opinion, code inspection, or defect diagnosis. The asset owner's written method and the qualified reviewer control the assignment.
Scope before equipment
Four decisions make the assignment usable
A larger sensor does not repair an undefined brief. Set ownership, identity, acceptance, and exceptions first.
- 01
- Name the review owner
- Identify the roofer, adjuster, thermographer, PV specialist, bridge team leader, tower owner, architect, engineer, or envelope consultant who will interpret and accept the evidence.
- 02
- Use the owner's asset hierarchy
- Building, facet, block, row, module, bridge, span, member, tower, sector, elevation, floor, and bay IDs must match the receiving system.
- 03
- Define complete coverage
- List every required overview, context, detail, paired image, condition record, and supporting method. Put inaccessible areas in the package instead of hiding them.
- 04
- Separate observation from conclusion
- The pilot records what is visible and where. The qualified reviewer determines defect type, cause, severity, code status, repair, coverage, or follow-up.
Roof
Complete every facet, edge, penetration, drainage path, rooftop item, and coverage exception.
Solar
Tie each file to the owner's block, row, module, or equipment IDs and retain thermal conditions.
Bridge
Follow the bridge-specific written procedure and show what still requires hands-on or other access.
Tower
Use face, sector, elevation, mount, cable, work-order, RF-control, and closeout identifiers.
Facade
Map each elevation by floor and bay, then pair every detail with enough context to locate it.
Primary source desk
Rules and methods behind the builder
The builder combines current federal flight rules with public agency guidance for bridge, solar, tower, pilot-proficiency, and documentation workflows. The asset owner's current procedure remains controlling.
Reviewed 2026-08-27 · Educational, not legal, engineering, claims, code, or inspection advice.
- 14 CFR 107.49 preflight actions
Requires the remote pilot to assess weather, airspace, people, property, and other ground hazards and brief participants before flight.
- 14 CFR 107.31 visual line of sight
The current VLOS requirement still applies when an asset extends beyond a convenient single viewpoint.
- FHWA National Bridge Inspection Standards Q&A
Explains that UAS may supplement but not supplant bridge personnel and physical inspection methods, and identifies bridge-specific procedure and documentation needs.
- FHWA UAS data collection for bridge inspection
Research on UAS platforms, sensors, inspection data needs, data management, and real bridge-inspection use cases.
- DOE photovoltaic system owner's guide
States that aerial and handheld IR can support PV inspection, while trained imaging professionals are required to perform and interpret the work properly.
- NREL PV operations and maintenance best practices
Covers aerial thermal imaging, commissioning and maintenance uses, image quality, processing, and system-level PV O&M context.
- OSHA and FCC communication tower best practices
Addresses owner, carrier, contractor, RF, structural, safety, information-sharing, photo closeout, and drone-inspection practices.
- NIST aerial drone proficiency test methods
Provides repeatable test methods for remote-pilot positioning, visual acuity, and structure-inspection tasks near objects.
- NPS standards for architectural documentation
A strong documentation model: select coverage for the intended use, make it independently verifiable, state limitations, and retain primary field records.
- DroneDeploy Roof Report documentation
Official platform documentation for roof capture and report outputs. A client platform specification does not become a universal inspection standard.
Common questions
Drone inspection deliverables, plainly answered
What should a drone inspection deliver?
A useful drone inspection delivers traceable evidence, not a folder of attractive images. The package should include original files, a component and image manifest, complete overview-to-detail coverage, capture conditions, exceptions, a neutral observation log, quality checks, and the name of the qualified person who will interpret the evidence.
Can a drone perform a complete bridge inspection?
Not by itself. FHWA states that UAS may supplement portions of a bridge inspection but cannot replace all visual and physical methods, including tactile examination, sounding, auditory cues, and live-load response. The bridge owner and qualified inspection team define the procedure and own the findings.
What belongs in a drone roof inspection package?
A visual roof package normally needs property orientation, full-roof coverage, every facet, edge, penetration, flashing, drain, gutter, skylight, and rooftop equipment item in scope, plus paired context and detail images. Originals, metadata, an image index, coverage exceptions, neutral observations, and the qualified review owner should travel with the imagery.
Does a thermal drone image prove a defect?
No. Thermal patterns depend on the surface, operating load, solar loading, wind, clouds, angle, emissivity, reflections, focus, range, equipment, and method. Preserve the radiometric original, pair it with RGB, record conditions and settings, and send the candidate pattern to a qualified thermographer or domain reviewer.
Is a drone model or measurement automatically survey-grade?
No. A mesh, point cloud, orthomosaic, roof measurement, or dimension set is only as defensible as its capture geometry, coordinate reference, control, checkpoints, processing, validation, and intended use. It does not automatically become a legal survey, as-built record, engineering model, or authoritative measurement.
Who decides whether an observed condition is a defect?
The responsible qualified reviewer does. Depending on the asset, that may be a roofer, adjuster, thermographer, PV specialist, bridge inspection team leader, tower owner, architect, engineer, envelope consultant, or authority having jurisdiction. The pilot can record a visible condition and its location without assigning cause, severity, coverage, code status, or repair action.
Continue the workflow