QUALITY REVIEW · 5 MIN READ
Drone property-media QC checklist before delivery
Aerial files can look polished while still showing the wrong property context, missing an ordered view or carrying the wrong delivery variant.
QUICK ANSWER
Review drone media against the exact property job and ordered output: verify the property identity, expected stills or clips, requested context, visible file quality, current version, branding and delivery format. A qualified operator’s capture decision and legal compliance process remain separate responsibilities; QC should approve only the client-facing media your team actually reviewed.
Match every file to the property order
Verify the property address or job identifier, source set, current submission and ordered aerial service. Use the approved capture brief to confirm expected stills, clips or context without adding unagreed requirements during QC.
Do not treat flight planning or operator compliance as a checkbox performed by the media reviewer; those belong to the responsible operator and the business’s current process.
- Correct property and job.
- Expected still, clip or variant list.
- Current submitted version.
- Property-specific request and approved output format.
Review content and output systematically
Check that the intended property is identifiable, requested context is represented, frames or clips are usable under your studio standard, and exports do not contain obvious corruption or unintended elements from the editing process. Confirm orientation, resolution and file type against the ordered output.
| Checkpoint | Evidence | If it fails |
|---|---|---|
| Identity | Job and property match | Hold the entire submission |
| Completeness | Ordered asset list | Request the named missing item |
| Visual review | Current studio and job brief | Cite the exact file or timecode |
| Packaging | Approved format and variant | Replace before client access |
Illustrative aerial-package review
A fictional order requires six aerial stills and one short exterior clip. QC receives all seven files but discovers that one still shows an older property boundary annotation not requested for this version. The reviewer rejects the submitted package, names the affected file and approves the corrected version only after reopening the client-facing folder.
This example concerns workflow accuracy, not flight or property-boundary advice.
Record approval and delivery scope
Name the reviewer, approved version and client package. If weather, access or another capture decision changed the agreed scope, ensure the coordinator has documented the client communication before delivery. Keep later change requests attached to the same job history.