Drone Client Approval Checklist
What project owners, marketing teams and engineering reviewers should check before accepting drone deliverables.
By SkyViews Aerial Drone Studio
A drone project is complete only when the client can use the files for the agreed purpose. A beautiful video may contain a wrong location label. A sharp roof image may miss the area the facilities team needed to see. A survey file may open correctly but use the wrong coordinate system. Approval therefore needs more than a quick look at a thumbnail.
This guide gives project owners a clear order for reviewing drone photos, films, inspection records and mapping files. Choose the parts that fit your project. The person who approves a social video may be different from the person who accepts a technical map. Name both people before delivery, and give each one the brief, file list and review deadline.
Scope Verification & Technical File Inspection
Start with the written scope
Open the final quote or approved brief beside the delivery folder. Check the site name, capture date, work areas, intended use and promised file types. A reviewer cannot judge whether something is missing without that list. If the scope calls for ten edited photos, two vertical clips and source footage, make three separate checks. Do not accept a folder simply because it contains many files.
Make a short acceptance table with four columns: promised item, delivered filename, reviewer and decision. Mark an item as accepted, correction needed or awaiting information. This avoids vague feedback such as “the drone work looks fine” when one essential view is absent. If the project changed during capture, attach the written change approval and check the new scope rather than relying on memory.
Also check what the project did not promise. A marketing shoot does not automatically include a measured site map. A visual inspection does not by itself provide a signed engineering opinion. A source-video handover may not include edited social clips. Keeping the purpose clear protects both the client and the crew from misunderstanding.
Check the files before judging the pictures
Download or open a sample of every file type on the device or software your team will use. Check that the folder is complete, filenames are readable and no files are corrupt. A preview in a cloud drive is not proof that a full-resolution file can be downloaded. If delivery includes a large master film, play the downloaded master from beginning to end. For maps or models, open the actual working file rather than judging a PDF screenshot.
Confirm dimensions, file format and orientation against the brief. A 16:9 landscape film and a 9:16 vertical film serve different screens; a simple crop can cut off a building, person or label. Photo files intended for print may need more detail than small web images. A GIS team may need a GeoTIFF with usable location data instead of a flattened JPEG. Ask for the format your team can open, not the format with the most impressive name.
Keep an untouched copy of the original delivery. Put review notes in a separate document rather than renaming or editing the only supplied files. This makes it possible to tell whether a problem came from capture, export, upload or a later client edit.
Media Asset & Technical Map Review Procedures
Review video in a useful sequence
First watch the film once without pausing. Does it make sense to someone who does not know the site? Does the opening establish where the viewer is, does the middle show the promised subjects, and does the ending give the intended conclusion or call to action? Then watch a second time and pause at specific problems. Note the filename and timecode for each comment.
Check focus, exposure, level horizon, stable movement and natural colour. Look for a jump in colour between shots, a clipped skyline, fast movement that hides the subject or a transition that suggests two places are connected when they are not. If the film uses ground footage as well as aerial footage, check that the sequence accurately shows the real route through the property or site.
Listen with sound on and with headphones if sound matters. Check voice clarity, music level, abrupt cuts and any location sound that should have been removed. Read every caption and screen label. Verify the property name, address, distances, dates and project stage with the owner. An attractive edit should not imply that a planned amenity is already built or that an old view shows the current condition.
Finally, view each export where it will appear. A website banner, presentation screen and phone feed crop the frame in different ways. Check the first frame, cover image, safe space for platform controls, logo placement and final contact details. Marketing should approve these points before any public upload.
Review still photos one by one
Match each selected photo to a purpose in the shot list: entrance, roof, full plot, road approach, amenity, elevation or context. A group of similar wide views is not a substitute for a missing detail view. Zoom in at full size to check focus, motion blur, stitch errors and unwanted objects. Panoramas deserve special attention at join lines and around moving vehicles or people.
Compare the image with the actual site. Colour correction can help a photo look natural, but it must not change a safety or property fact. Do not remove a neighbouring building, unfinished work, a boundary marker or a visible defect to make a factual record look cleaner. If the photo is for advertising, the owner should still confirm that labels, visible facilities and capture date are fair to a buyer or visitor.
Decide whether the delivered set is ready for web, print or internal reporting. A high-resolution original, a smaller website version and a captioned report image can all come from one capture, but each has a different use. Record which version is approved for each channel so the wrong file does not circulate later.
Give technical maps a technical reviewer
A survey or mapping handover needs review by someone who understands the intended measurement or design decision. Start with the site extent and capture date. Check for gaps, blurred areas, heavy shadows, moving objects and features hidden by roofs or trees. Ask whether excluded areas are marked on the map and described in the report. A seamless-looking image can still have missing or weak data.
Confirm the coordinate reference system, units, ground control or check-point method, stated accuracy and known limits. Check that sample coordinates and distances appear where the project team expects them. If the output is an orthomosaic, inspect edges, joins and important features at full resolution. If it is a surface model or point cloud, check classification, holes and whether a ground surface was actually produced. Do not infer terrain beneath a roof or dense trees from a surface model.
Ask the survey lead to explain how quality was checked and what the file may be used for. A drone map for visual planning may be very useful without being suitable for a legal boundary, construction setting-out or a certified quantity. If those decisions matter, the acceptance note should identify the separate survey control, validation and professional sign-off required by the project. A client should never assume that a colourful map proves a measurement claim by itself.
For inspection work, match each image to an asset ID, location and observation in the report. Can a maintenance person find the same roof panel, wall crack or solar row later? Are uncertain findings marked as uncertain? Separate what the image shows from what an engineer must diagnose with a closer test. Request a missing view or a clearer label while the capture team still knows the site.
Rights Verification & Final Version Sign-Off
Check privacy, rights and release permission
Before publication, look for faces, vehicle plates, private windows, neighbouring homes, security layouts, screens, confidential stock or restricted work areas. Some details can be cropped or blurred; other frames may need to stay internal. Review the full-resolution files, not just small previews, because sensitive details may appear only when zoomed in.
Confirm who owns the right to use the music, voice, logo, map layer, ground photograph and any other asset in the finished work. Ask whether people shown in a campaign have the permissions needed for that use. The site owner should approve publication where property access or confidentiality terms require it. A team may be allowed to capture an area for internal records but not to place the same view in an advertisement.
Check metadata too. Photo and mapping files may contain coordinates, capture times or equipment details. Decide whether public copies need that information. Keep the original technical files for authorised users, and create separate publication exports when needed. Send sensitive files only through the agreed channel and confirm who may download them.
Resolve comments and sign off a version
Write corrections as numbered items tied to a filename, timecode, image number, map layer or report page. Say what is wrong and what the approved result should be. “Fix the map” gives a production team little to act on; “the north roof is missing from mosaic version 1, sheet 2” is useful. Group comments from marketing, operations and technical staff before sending one consolidated list.
When a revised delivery arrives, check the corrections and any nearby parts they may have affected. Keep the first delivery and each revision in separate folders. Name the accepted version, acceptance date and person who approved it. Record any open limit, such as a shadowed area that could not be captured safely or a measurement that remains unverified. Approval can be conditional if everyone knows exactly what is still pending.
Archive the brief, permissions, delivery manifest, final files, correction list and sign-off together. A later campaign, inspection or dispute may require someone to trace which image was used and when it was captured. Good records make that answer simple. For more on file choices, read the video deliverables guide. For access and storage decisions, use the data-security guide.
Plan your project
Share your site, dates and intended output so we can confirm a suitable scope.
Drone Survey & Mapping · Compare project scope · Get in touch
Related reading
- Drone Mapping QA Checklist: Before You Accept an Orthomosaic or 3D Model
- Agriculture Drone Mapping for Farms and Estates in Karnataka: Practical Guide
- Archaeological Excavation Drone Mapping in India: Documentation Guide
- Drone Inspection for Sewer and Utility Corridors in India: Planning Guide
- Drone Inspection for Substations and Electrical Assets in India
- Using Drone Data for BIM Coordination and Construction Progress in India
Contact SkyViews Aerial Drone Studio at +91 90190 56479 or skyviewsdronestudio@gmail.com. Service area: Bangalore, Karnataka and India and wider Bangalore, Karnataka and India.