What Clients Actually Receive After a Commercial Drone Mission

The flight is the part people see. The drone goes up, the cameras roll, the operator brings it back down. What happens in the 24 to 72 hours after that — the processing, the packaging, the actual hand-off — is where a professional drone operation separates from someone who owns a nice aircraft.

This post is about exactly that: what leaves my hands and lands in yours after a commercial mission. Not a sales pitch. A real accounting of the deliverable chain, from raw capture through final delivery, with specific file types, processing workflows, and the reasoning behind how I structure what I hand over.

---

The Raw Capture Is Not the Deliverable

The first thing to understand is that what the drone captures and what you receive are two different things. The DJI Matrice 30T, which is the primary platform for most of my commercial work, captures multiple data streams simultaneously: 48MP still frames from the zoom camera, 12MP wide-angle frames, 640x512 radiometric thermal data, and laser rangefinder coordinates. The DJI Matrice 4TD adds additional sensor capability. The Mavic 3 Pro brings Hasselblad-calibrated color to lower-altitude creative and inspection work.

Raw capture from a single 41-minute battery cycle on the M30T can run 8 to 12 GB of mixed media. A full survey mission with multiple batteries produces data volumes that are meaningless to a client in their raw state. Nobody needs a folder of 1,200 unprocessed DNG files with no structure, no georeferencing confirmed, and no context.

What clients actually need is processed, organized, labeled, and explained output. Here is what that looks like broken down by mission type.

---

Deliverable Breakdown by Mission Type

Aerial Photography and Video

For standard commercial photography — real estate, architecture, event documentation, marketing assets — the deliverable package contains:

• **Edited stills:** JPEG exports at full resolution, color-corrected and exposure-balanced, typically 20 to 50 selects depending on scope. File naming convention includes date, location, and sequential numbering so the client's asset management system can absorb them without manual renaming.
• **RAW files on request:** If the client has an in-house photo editor or a brand standard that requires RAW originals, I include the DNG source files for the selects. This is not the default — most clients don't need them, and 50 DNG files at 48MP each is not a lightweight download.
• **Video deliverables:** H.264 or H.265 MP4 exports at the agreed resolution and frame rate. I shoot LOG or D-Log M depending on platform, grade in post, and deliver a color-corrected master. If the client wants a flat LOG file for their own color pipeline, that's a separate deliverable discussed at the scope stage.
• **Flight summary:** One-page document with flight date, location, weather conditions at time of flight (wind speed, cloud cover, temperature), aircraft used, and total images captured. This matters for legal and insurance contexts more than clients initially expect.

Mapping and Photogrammetry

This is the most technically dense deliverable category. A mapping mission produces processed outputs from photogrammetric reconstruction — a process where hundreds of overlapping still frames are aligned by GPS coordinates and feature-matching algorithms to produce spatial data products.

The specific outputs depend on what the client needs:

• **Orthomosaic:** A georeferenced, top-down composite image of the entire survey area, stitched and corrected for camera distortion and terrain variation. Delivered as a GeoTIFF with embedded coordinate reference system, typically in WGS84 or a local UTM zone. File sizes range from 200MB to several GB depending on acreage and resolution. A 40-acre site flown at 1.5 cm/pixel ground sampling distance produces a substantial file — clients need to know this before delivery so their GIS environment can receive it.
• **3D point cloud:** LAS or LAZ format, georeferenced. Used for volumetric calculations, surface modeling, and BIM integration. This is what a quarry manager in Junction City uses to calculate stockpile volumes without walking the pile with a tape measure.
• **Digital Surface Model / Digital Terrain Model:** GeoTIFF elevation rasters representing surface elevation with and without vegetation filtering. Useful for drainage analysis, grading verification, and earthwork quantity estimates.
• **Contour lines:** Exported as shapefile or DXF for clients whose engineering workflow requires CAD-compatible formats.
• **Inspection report:** For infrastructure or facility inspection missions, a PDF report with annotated screenshots, GPS coordinates of flagged features, and a plain-language description of observed conditions. If I'm inspecting a roof and find anomalies on the northeast quadrant near the ridge, the report shows the thermal and optical images of that area, the GPS coordinates, and a description. No guessing which corner I'm talking about.

Thermal Missions

Radiometric thermal data requires its own treatment. The M30T's 640x512 thermal sensor captures actual temperature values per pixel, not just a color-mapped image. That distinction matters because the deliverable for a thermal inspection is fundamentally different from a visual photograph.

• **Radiometric TIFF:** Raw thermal data with embedded temperature values, processable in FLIR Tools, DJI Thermal Analysis Tool, or equivalent. Clients who need to run their own thermal analysis get this.
• **Annotated thermal report:** For most clients — solar farms, building envelope assessments, agricultural moisture surveys — the deliverable is a PDF with thermal images calibrated to their emissivity and reflected temperature parameters, color-palette-normalized for the application, and annotated with temperature readings at points of interest. A solar panel showing a cell-level hotspot at 71°C while the surrounding array runs at 38°C is a defect. The report names it, locates it, and documents it with GPS coordinates and the panel's position in the array layout.
• **Comparison sets:** Where relevant, I include side-by-side thermal and optical images of the same feature so the client can see both what the thermal found and what the area looks like visually. This is especially useful for building envelope work where you want to cross-reference a thermal anomaly with the physical construction detail.

---

The Delivery Method and Timeline

Every deliverable package is transferred via a shared folder link — no email attachments, no cloud platforms requiring account creation from the client. The link is live for 30 days. If the client needs it re-sent after that, I re-send it. There is no fee for that.

Timeline varies by mission type:

• **Photography and video:** Selects and edited video within 48 hours of flight, in most cases faster for straightforward deliverables.
• **Mapping and photogrammetry:** 3 to 5 business days depending on dataset size and processing queue. Photogrammetric reconstruction for a 200-acre site is computationally intensive — I run it locally on dedicated hardware, not on metered cloud processing. That keeps cost controlled and keeps the data in-house.
• **Thermal inspection reports:** 24 to 48 hours post-flight. The annotation and report writing is the time-consuming part, not the processing.

Rush delivery is possible depending on schedule. I have operated at 1:00 AM in Springfield, Oregon, running emergency thermal search patterns on behalf of a family in crisis. Turnaround speed scales to the urgency of what is actually needed.

---

What the Flight Summary Document Does for You

I want to give specific attention to the flight summary because it is the deliverable clients ask about least and use most unexpectedly.

The flight summary includes: date and time of flight, GPS coordinates of the operational area, aircraft used (specific model and serial if required), pilot certificate number, weather data logged at time of operations, battery cycles flown, and total flight time. It is a one-page document that takes me ten minutes to produce.

Here is when it becomes important: an insurance claim, a legal dispute over site conditions, a regulatory question about operations near controlled airspace. The flight summary is contemporaneous documentation that you can hand to an attorney, an adjuster, or a regulator. It establishes what was done, by whom, under what conditions, and when. The aerial data proves conditions at a specific moment in time only if you can prove when that moment was.

For construction clients documenting site conditions before a subcontractor begins work, or property owners documenting pre-loss conditions for an insurance carrier, that document has real dollar value attached to it.

---

The Conversation That Should Happen Before the Flight

Every deliverable problem I have seen — and I have seen them — originates in scope conversations that did not happen before the flight, not after.

The client who receives a GeoTIFF and does not have GIS software to open it. The client who wanted video but did not specify delivery format and cannot play ProRes on their Windows machine. The thermal client who needed emissivity set for painted metal but did not flag that until after the mission.

The intake conversation is not bureaucratic overhead. It is where I confirm: what software will you use to open the data, what coordinate reference system does your GIS team prefer, do you need LOG video or a finished grade, do you have a specific PDF format for inspection reports that needs to match your internal template. Fifteen minutes of specifics before the flight saves two rounds of re-delivery after.

---

The Standard You Should Expect

If a drone service provider cannot give you a clear description of your deliverables before the flight — specific file types, coordinate systems, report format, delivery timeline — that is diagnostic information. It tells you the operation is built around the flight, not around what you actually need.

The flight is not the product. The data is the product. And data is only valuable when it arrives in a form you can open, verify, use, and retain.

Before your next mission, ask for the deliverable specification in writing. What files. What formats. What timeline. What the flight summary contains. If those answers are immediate and specific, you have the right operator.