Drone client footage lost on a commercial job starts two clocks at once, at different speeds. The technical clock is how long the media stays recoverable; the commercial clock is the client’s launch, broadcast slot, or inspection deadline. Handling the loss well means running both in parallel.
The first decision matters most: notify the client that a delivery risk exists within hours, using language that neither promises recovery nor announces failure. Most relationships are damaged not by the loss itself but by a late, vague notice followed by a definitive no. What follows is the triage, the wording, and how to keep the schedule alive while recovery runs.
The First Hour: Triage Before You Call Anybody
You need four facts before the first client conversation, because without them any update you give will be wrong within a day.
- Which media actually holds the footage. Onboard aircraft storage, a microSD card, an external SSD in the editing pipeline, or a client’s own drive. Each has a different recovery outlook, and the differences between drone storage media decide which route applies.
- Which leg of the pipeline broke. In-flight recording, offload from the aircraft, transfer to the edit system, or post-production storage. A file that vanished during an offload is frequently still intact at the source, which changes the message completely.
- Whether the loss is local or global. One missing clip from a completed flight is a scheduling problem. An entire flight or an entire day is a re-shoot decision. Confirm by listing what you do have, not just what you are missing.
- What duplicates exist. Any second copy — a card still in the bag, a backup drive, an upload that partially completed — can end the entire incident. Check before you alarm anyone. If duplicates were never part of the workflow, the drone footage backup workflow is the fix to adopt afterward.
Freeze the media while you gather those facts. Power down the aircraft, remove the card, do not format anything, do not let the app sync or auto-upload, and do not mount the suspect drive on a desktop more than necessary. Every diagnostic step that writes reduces what remains.
What to Say Now, and What to Hold Back
The table below maps the situation to the message. The general rule: state what is confirmed, state what is being checked, and give a time for the next update. Do not volunteer a re-shoot before you have tried recovery, and do not imply the footage is safe when you do not know.
| Situation | Tell the client now | Hold back | Delivery action |
|---|---|---|---|
| One clip missing, the rest of the flight intact | A specific clip is under recovery; delivery remains on schedule if it succeeds | Which technical mode failed and why | Deliver everything else on time |
| An entire flight or day missing | Immediate notice that delivery is at risk, with a next-update time | Root cause until it is confirmed | Offer a partial cut using available material |
| Loss found during offload, source card intact | Almost nothing — verify the source first | Any mention of the recovery process | Re-run the copy and confirm file counts |
| Client will discover it at review if unaddressed | Notice before they ask | Internal debate about blame | Deliver with a written scope note |
| Confirmed overwrite or destroyed media | State plainly that the material is not recoverable and present options | Detailed technical explanation | Re-shoot quote and revised schedule |
| Could not yet be determined | That a loss is possible and you are checking | Any assessment of whether it is recoverable | Keep the current delivery date in place |
Two phrases do real work. “We are assessing whether this is recoverable and will give you a firm answer by Thursday” is honest and actionable. “We think we can get it back” is a promise you may have to break, and it is the sentence clients remember.
A Notice and Recovery Message You Can Adapt
Copy the block below, fill the brackets, and send it by email so the client can forward it internally without paraphrasing. In a commercial relationship, a written record also protects you if the schedule is later disputed.
Subject: [Project name] — update on [deliverable], delivery risk identified
>
[Client name],
>
A short update before you see the next [cut / batch / dataset].
>
During [offload / review] on [date] we identified that [one clip / a portion of the footage / the flight recorded on [date]] from [site name] is not currently accessible. Everything else from the shoot is accounted for and is unaffected.
>
Here is what we know and what we are doing:
– Confirmed: [state exactly what is missing and what is intact].
– In progress: we are working on the media with the aim of recovering the files. Recovery on this type of media typically takes [timeframe].
– Next update: [day and time], whether or not there is a result by then.
>
To protect your [launch date / submission deadline], we propose:
1. Delivering the [number] completed [clips / images / datasets] on [date] as planned, so your review can start on schedule.
2. Adding the [missing element] as soon as it is recovered, or, if it cannot be recovered, covering the same [shot / area / sequence] in a re-flight on [proposed window], weather permitting.
>
If a re-flight becomes necessary, it will be included at no additional cost, and we will confirm that decision by [date] so your timeline is not affected.
>
I will call you at [time] today to agree on the approach.
>
[Your name]
Three elements make this message work: it separates confirmed facts from work in progress, it commits to a next-update time it can be met even with no news, and it proposes a delivery structure that keeps part of the schedule intact. Adjust the re-flight commitment to match your contract — the value of offering it proactively is that it moves the conversation from blame to a plan.
Protecting the Delivery Timeline While Recovery Runs
Recovery and production do not have to compete for the same hours. Several moves keep the schedule moving in parallel.
Ship the partial delivery. A cut containing everything except the missing element is still progress, and it lets the client’s internal review proceed. If the missing piece is one sequence, cut around it with a temporary placeholder and label it clearly rather than leaving a silent gap.
Analyze the re-shoot as a real option now, not as a fallback. Check airspace authorization, weather window, site access, the sun angle at the required time of day, and whether the subject has changed since the original flight. A re-shoot that is possible in three days changes the entire negotiation; a re-shoot that is impossible for a month changes it in the other direction. Cost that analysis in the first hour, not the third day.
Tell your own post-production chain to stop waiting. Editors holding a slot for footage that may never arrive cost you the ability to deliver anything else. Reassign that capacity to the work that can be finished.
Protect the redundant copy on the next sortie. If a re-flight does happen, record to two storage destinations and offload before leaving the site. The dual-destination storage approach for drones is the cheapest insurance available on an aerial job.
Recovery, Re-Shoot, or Renegotiation
Once the media has been assessed, three options exist and they cost very different amounts.
| Option | When it applies | Typical cost | What the client sees |
|---|---|---|---|
| Software recovery from intact media | Card or drive enumerates; files deleted or unplayable | Low, hours of work | A professional process that worked |
| Laboratory recovery | Controller failure, physical damage, media not enumerating | High, days to weeks | A professional process invoked correctly |
| Partial or full re-shoot | Media overwritten or destroyed; subject still available | Flight cost, crew time, weather risk | Whether you protected their deadline |
| Scope renegotiation | Re-shoot impossible; alternative content exists | Reduced fee or substituted deliverable | Honesty, with the strongest possible alternative |
The decision between a paid lab attempt and a re-shoot is a genuinely close call when the subject is expensive to re-create. Circuit-board-level recovery has real failure rates and real turnaround times; the comparison of software recovery and laboratory services lays out the cost structure, and the honest limits page on unrecoverable data describes the signals that mean a lab attempt would be wasted money. If the media is a card that a computer still recognizes, the outcome depends only on whether the original data has been overwritten: if it has not, it comes back in full, and if a recovered file will not play, the recovered portion can be re-encoded into a playable file. If the aircraft was destroyed or the media was submerged, start with the handling procedure for a drone that crashed or went into water, because the order of operations in the first hours decides whether anything survives.
For card-based cases, recovery should start in parallel with the client conversation rather than after it. If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive.
Frequently Asked Questions
Should I tell the client immediately or wait until I know the outcome?
Tell them as soon as you have confirmed that a delivery element is at risk, with a specific next-update time. Waiting for certainty means the client learns about the problem late, which is the part they actually resent. An early, factual notice with a plan preserves the relationship even when the answer ends up being no.
Is a re-shoot or a lab attempt the better use of money?
It depends on whether the subject still exists. If the location, subject, and conditions can be re-created, a re-shoot gives a better outcome with a predictable cost. If the moment cannot be repeated — aerial survey coverage of a site that has changed, a one-off event — a laboratory attempt is worth its price because it is the only route left.
What should be in the contract to cover this?
At minimum: an agreed definition of delivery failure, a notification window, a cap on re-shoot liability, and a clause covering acts of weather and airspace restriction. Many aerial contracts are written to assume success; adding two sentences about recovery and re-flight protects both parties.
How do I prevent this on the next commercial job?
Record to two destinations when the aircraft supports it, offload at every site visit rather than at the end of the project, verify file counts before formatting anything, and never hand over or delete the original media until a checked copy exists in two places.