Key takeaways
- Flying is the short part. Most of the calendar between a request and a deliverable is spent before the flight and after it, not during it.
- The delays clients complain about most are usually ones they can remove: site access and escorts, a coordinate system decided late, and a scope that changes after the data is captured.
- Ask for turnaround as a commitment in the scope, measured from a named trigger — data capture, not the day you first called — with a stated exception for weather and airspace.
- A rush is a real option, but it buys queue priority and overtime, not a shorter list of steps. What it cannot compress is the quality assurance that makes the number defensible.
Almost every drone survey request arrives with the same unspoken question attached: when do I get it? And almost every disappointing answer traces back to the same misunderstanding — that the flight is the job.
The flight is generally the shortest and most predictable part of a drone survey. The calendar sits on either side of it. This is what those stages actually are, which ones can move, and which delays are yours to remove.
The stages between your call and your deliverable
Every job runs through roughly the same sequence, whether it is one stockpile or a whole facility:
- Scope. Deciding what is being measured or inspected, to what accuracy, in what coordinate system, delivered in what format and to whom.
- Pre-flight checks. Airspace, aviation activity, site hazards, access, prequalification and any authorisation the flight needs.
- Mobilisation. Getting a crew, aircraft and ground control to the site inside a workable weather and operations window.
- Capture. The flight itself, plus ground control survey and the on-site check that the data set is complete before the crew leaves.
- Processing. Photogrammetric reconstruction or point-cloud processing — largely machine time, and the one stage where the size of your site translates almost directly into hours.
- Analysis. Turning a surface or a point cloud into the thing you asked for: volumes, contours, an anomaly list, a set of callouts.
- Quality assurance. Checking the result against independent check points or against the previous survey, and confirming it is defensible before it is sent.
- Delivery. Packaging, transfer and the walk-through where anybody who has to act on the number understands it.
Only stage four involves a drone in the air. Stages one to three are where most surprises live, and stages five to seven are where the actual production time sits.
Delays that belong to the operator
Some of the calendar is genuinely the contractor's, and you should expect a straight answer about each of them.
- Queue. Field seasons in Alberta are compressed. A capable operator has a backlog in the busy months, and honest scheduling means telling you where you sit in it rather than promising a date they intend to renegotiate later.
- Processing capacity. Large sites and high-resolution capture take real compute time, and several jobs compete for it.
- Analysis effort. Volumes against a defined base surface are quick. Interpreting a thermal survey, or writing an inspection report with severity-ranked callouts, is skilled work that does not compress well.
- Quality assurance. The step most often quietly skipped when someone has promised a date they cannot hit. If a number is going into a financial or engineering decision, this is the step you least want compressed.
Delays that belong to the client — and are the easiest to remove
These are the ones worth reading twice, because they are usually free to fix.
Site access and escorts
Orientation, gate procedures, escort availability and prestart requirements are all reasonable and all consume calendar. A crew that cannot get to the work face on the planned morning has burned a mobilisation. Name the access requirements at quoting and book the escort with the flight.
The coordinate system decided at the end
The single most common avoidable rework on a survey. If the coordinate system, datum and vertical reference are decided after processing, the survey may have to be re-processed and, in the worst case, re-flown with different ground control. Decide it in the scope, in writing, before the flight.
Scope that changes after capture
"While you are at it, can you also do the north yard" is fine before the flight and expensive after it, because the data for the north yard does not exist. Additions found after capture usually mean another mobilisation.
Approvals and recipients
A deliverable that sits in one person's inbox waiting for a sign-off is not delivered. Name the people who need it and who signs off on it before the job starts.
Reference data supplied late
Previous surveys, design surfaces, base surfaces, site control, asset registers — anything the result has to be compared against or tied into. If it arrives after processing, the analysis restarts.
Weather and airspace: real, but manageable
Weather is the honest exception in any turnaround commitment, and it is not only about rain. Wind, cloud and light all affect whether captured data is usable, and thermal work has its own condition requirements — the reason our thermal inspection conditions post exists is that a survey flown in the wrong conditions is not interpretable at any turnaround.
Snow cover, low sun angles and short daylight change what is achievable in an Alberta winter, which our winter operations post covers in detail.
Airspace is the other one. If your site needs a flight authorisation, that review time is part of the schedule — which is why the airspace check belongs at quoting, not on mobilisation day.
Neither should ever be a surprise. Both should appear in the scope as named exceptions with a re-attempt commitment attached, so a weather stand-down is a known process rather than an argument.
What a rush actually buys
Rush turnaround is a legitimate thing to ask for and a legitimate thing to charge for. It is worth understanding what it does and does not do.
It buys priority — your job jumps the processing queue and the analyst works on it first, possibly outside normal hours. On a genuinely urgent job, that is often most of the gap.
It does not buy fewer steps. The processing still has to run, the analysis still has to be done, and the quality check still has to happen. An operator who promises a same-day turnaround on a survey that normally takes days is usually promising to skip the last one.
A more useful ask, when only part of the result is urgent: phase the delivery. A quick-look orthomosaic or a preliminary volume the day after the flight, with the full checked package to follow, gives the person who needs to make a decision something to act on without anybody pretending the quality assurance happened faster than it did.
Write turnaround into the scope
Four lines are enough to prevent almost every turnaround dispute:
- A number, and what it is measured from. Business days from completion of data capture — not from the day you first enquired, and not from an unstated milestone.
- What is included at that point. Which deliverables land on the committed date and which follow. A phased delivery is fine as long as it is written down.
- The exceptions. Weather, airspace authorisation and site access, each with a stated re-attempt commitment rather than an open-ended "subject to conditions".
- What the client owes, and by when. Coordinate system, reference data, escort, sign-off names. A commitment that depends on your inputs should say so.
Any operator who is comfortable with their own process will put those four lines in writing. Reluctance to commit to a turnaround measured from a named trigger tells you something worth knowing before the job starts.