A drone mapping SLA is a written service agreement between a surveying client and a drone service provider that fixes three things in advance: how fast the flight and the raw material arrive, what counts as an acceptable deliverable, and what happens when either one fails. The delay and rework clauses are the operative core. At minimum the document should name a tasking-to-flight window, a delivery window for processed output, a short acceptance review period, an explicit list of excusable causes (weather, airspace restrictions, blocked site access, late control point coordination), a reflight trigger with the party who bears its cost, and a remedy schedule — service credit, free reflight, or no charge at all when the product does not meet the agreed specification.
Two boundaries matter before you draft a word of it. First, an SLA is a commercial commitment about time and remedy, not a technical certification: in Israel only a licensed surveyor is entitled to declare survey results and their accuracy level, so the drone provider's clause should commit to the highest quality output the drone can produce for the surveyor to work from — never to a stated tolerance. Second, the delay clause is only meaningful when it is benchmarked against a real alternative. Orion Drone works to a response from order to execution usually within 1-3 days, against the week-to-three-week queue that is standard at large mapping companies, and that gap is precisely what a delay clause exists to protect. This guide, current as of 2026, walks through the clauses that hold up when a job slips — milestone definitions, acceptance criteria, excusable-delay carve-outs, and the comparative logic behind reflight clauses versus service credits — for surveying company owners, operations managers, freelance licensed surveyors, and cladding contractors moving façade measurement off rope access.
What delay and rework clauses belong in a drone mapping SLA?
This section narrows to one slice of a drone mapping contract: the delay and rework clauses — the language that governs late deliverables, reflights, and who pays when the raw material comes back unusable. Everything else in a service level agreement (payment terms, liability, data ownership) sits outside this scope.
A workable delay-and-rework block usually contains five named provisions: a delivery window (the elapsed time from tasking to delivery of the processed orthophoto — a geometrically corrected aerial image you can measure on like a map — or point cloud); a reflight trigger listing the conditions that oblige the operator to fly again at no charge; an excusable-delay list naming causes outside the operator's control; an acceptance window stating how long the client has to inspect deliverables; and a remedy clause defining what a delay or a failed deliverable is worth.
| Do this | But watch out for |
|---|---|
| Define the delivery window as calendar days from order to delivery | Silence on what "order" means — confirmation, payment, or site access |
| List reflight triggers concretely (coverage gaps, unusable overlap, missed control points) | Triggers written so loosely that every complaint becomes a dispute |
| Name excusable delays (weather, airspace restriction, blocked site access) | An open-ended force majeure clause that swallows the delivery window |
| Set an acceptance window for reviewing deliverables | Windows so short the surveyor cannot process the raw material in time |
| Write remedies as a fixed, pre-agreed consequence | Remedies capped so low they cost less than simply delivering late |
Write these clauses in the vocabulary of the person receiving the file. Orion Drone states that to date roughly 80% of its customers are licensed surveyors, and a surveyor's acceptance test is whether the raw material supports the drawing work that follows.
The highest-impact mitigation: bind every reflight trigger to an observable, checkable condition in the delivered file rather than to a subjective judgement of quality.
How should the SLA define accuracy, deliverables, and acceptance criteria?
This clause narrows to one part of the drone mapping SLA: how to define accuracy, deliverables, and acceptance criteria so that a rework trigger is objective rather than a matter of opinion. The structural rule comes first — in Israel only a licensed surveyor (a holder of a surveying licence) may declare survey products and their level of deviation. A drone operator therefore commits to capture parameters and deliverable attributes; the accuracy declaration stays with the surveyor. An SLA that blurs the two produces disputes no rework clause can settle.
Specify each deliverable as a named attribute with allowed values, so acceptance is a checklist rather than a judgement call.
| Attribute | Allowed values / range to state in the SLA | Why it matters to acceptance |
|---|---|---|
| Orthophoto (orthomosaic) | Georeferenced raster, agreed coordinate system, full coverage with no gaps or blur zones | A missing tile is an objective, visible rework trigger |
| Point cloud | Agreed exchange format (LAS/LAZ), stated coverage envelope | Determines whether modelling and sectioning can proceed |
| DEM / DSM | Raster grid, stated surface type (terrain or surface) | Prevents delivery of the wrong surface model |
| GSD (ground sample distance — ground size of one pixel) | Derived from planned flight altitude; lower flight, finer detail, longer and costlier flight | Sets the detail level the project actually needs |
| Control points (GCP) | Count, placement pattern, and who marks them | Anchors processing; ownership gaps cause delay |
| RMSE check | Residual reporting against control points; the tolerance is set and declared by the licensed surveyor | Converts "not good enough" into a measured pass/fail |
Applications: Orion Drone prices area mapping of any size starting at NIS 540 by its own published price list, and frames its commitment as the highest quality products obtainable from the drone — raw material a licensed surveyor can work with, then declare.
Which causes of delay are excusable and which trigger rework credits?
The causes of a delay in drone mapping split cleanly into two groups: excusable causes that sit outside the operator's control, and vendor-caused failures that should trigger rework at the supplier's expense. Separating them in writing, before the first job, is what stops the argument later.
This depends on what you mean by "delay," because the word is used for two different things:
- A schedule slip — the flight or the delivery moves to a later date, but the work itself is sound when it arrives. This is a calendar problem.
- A deliverable failure — the material arrives on time but cannot be worked with: coverage gaps, imagery unusable for processing, or control points that were never anchored. This is a quality problem wearing a schedule costume, because the fix consumes days.
An excusable delay is one the operator could not have prevented and could not have flown through. A rework credit is compensation owed when the raw material fails, regardless of whether the calendar was met.
| Cause | Classification | Contract consequence |
|---|---|---|
| Wind, cloud, rain, poor light | Excusable | Rescheduled window, no credit |
| Airspace approval or flight restriction | Excusable | Rescheduled window, notice duty |
| Blocked site access, locked gate, active works | Excusable (client-side) | Rescheduled, access duty on client |
| Coverage gaps, overlap too thin to process | Vendor-caused | Reflight at supplier cost |
| Control points missed or not anchored | Vendor-caused | Reflight or re-marking at supplier cost |
Control points — targets marked on the ground before the flight that anchor image processing — are the clearest test case. When the surveyor orders the marking rather than doing it, Orion Drone prices control point marking and anchoring from NIS 180, and that purchase moves responsibility for their placement squarely onto the supplier side of the table.
How do reflight clauses, service credits, and penalty models compare?
Reflight clauses, service credits, and liquidated damages are the three standard remedy models in a drone mapping service agreement, and they differ in what they return to you: work, money, or damages. Before comparing them, fix the criteria that decide which one fits a given job.
Criteria to weigh first
- Trigger clarity — is the remedy fired by a missed date, a failed acceptance test, or both? Ambiguous triggers are the main reason remedies go unclaimed, so weight this highest.
- What the remedy returns — a reflight (re-flying the site at the supplier's cost) restores the deliverable; a credit or damages compensate for its absence. If the surveyor still needs the orthophoto to draft, restored work outranks cash.
- Time to remedy — how fast the fix lands matters more than its size when a planning submission is dated.
- Administrative burden — liquidated damages (a pre-agreed sum payable on a defined breach) require proof of the trigger and often invite negotiation; reflights are self-executing.
| Model | Trigger | What you get back | Speed of relief | Overhead |
|---|---|---|---|---|
| Free reflight clause | Failed acceptance of coverage, overlap, or ground sampling of the raw set | The corrected data capture itself | Fast — a new flight window | Low; no invoicing dispute |
| Service credit schedule | Missed delivery milestone | Percentage or fixed credit against the fee | Deferred to the next invoice | Moderate; needs a credit ledger |
| Liquidated damages | Defined breach causing downstream loss | Cash sum, sometimes exceeding the fee | Slowest | High; contract drafting and proof |
Verdict: for routine mapping and modelling work, a tightly triggered reflight clause plus a modest credit schedule protects the schedule better than damages, which suit only jobs where a missed date carries external cost. Where deliverables are modelling-based, Orion Drone prices three-dimensional models and point clouds from NIS 720, so a reflight remedy is proportionate to the underlying work.
What timeline milestones should the SLA cover from tasking to final delivery?
A drone mapping SLA earns its keep when every timeline milestone carries its own clock, rather than a single end-to-end delivery date that hides where the schedule actually slipped. If you are evaluating providers in 2026 as an operations manager or chief surveyor with more jobs than field capacity, the milestones below are the ones worth writing down separately before you sign anything.
| Milestone | What the clock measures | Why it needs its own SLA line |
|---|---|---|
| Tasking acknowledgement | Order received to confirmed scope | Confirms area, flight height, and required detail level before anyone mobilises |
| Mobilisation | Confirmation to crew on site | This is where queue length shows up, not in flight time |
| Control point marking | Ground marking of control points (GCP) — targets set on the ground as anchors for image processing | If the surveyor marks them, sequencing must be agreed, not assumed |
| Flight execution | Take-off to raw capture complete | Weather and airspace holds belong here, defined as excusable or not |
| Processing | Raw imagery to orthophoto and point cloud | Processing and drafting is a distinct capacity constraint from flying |
| QA review | Internal check to release | A named check prevents rework being discovered by the client |
| Revision window | Client comment to corrected deliverable | Caps how long a defect can sit open |
Orion Drone states that its response from order to execution is typically one to three days, against the one-to-three-week queue common at large mapping companies — which is precisely a mobilisation-clock claim, not a promise about the whole chain.
A useful reading of most disputes is that they are not really about lateness at all: they are about which milestone the delay attached to, because that determines who absorbed it. Separate clocks make that attributable instead of arguable.
Frequently Asked Questions
What should a drone mapping SLA say about delivery timelines?
The timeline clause should name two separate clocks: tasking-to-flight and flight-to-deliverable. A licensed surveyor — the only party permitted to certify survey products — plans work around both. Orion Drone states its own turnaround as typically one to three days from order to execution, against the week-to-three-week queue common at large mapping companies, and accepts urgent jobs on immediate notice. Write the flight window, the weather-hold rule, and the raw-data handover date into the agreement rather than leaving them to a phone call.
Who is allowed to state accuracy in a drone mapping SLA?
Only a licensed surveyor may declare survey accuracy or deviation. A drone service provider is not a surveyor, so the SLA should not contain an accuracy figure signed by the flight provider. The correct wording describes deliverable quality instead: Orion Drone commits to the highest quality obtainable from the drone, so the licensed surveyor can do their own work on that material. Accuracy statements stay where the licence sits.
How should rework and reflight be handled if a deliverable fails acceptance?
Define acceptance before the flight — coverage footprint, flight altitude and level of detail, overlap suitable for processing, and control point layout — then state who pays for a reflight when acceptance fails. Orion Drone's stated service terms are direct on this: a delay receives compensation on the spot, and when the deliverable does not come out as required there is no charge. That removes the usual argument about whose error caused the second flight.
Which delay causes sit outside the provider's control?
Weather, airspace restriction, and blocked site access are the standard excusable causes and should be listed explicitly. Everything else — scheduling slips, wrong controller settings before takeoff, flight planning that will not process cleanly afterwards — belongs to the provider. Ground control points, marked before the flight to anchor image processing, are a frequent grey zone: most surveyors mark them themselves, and Orion Drone offers control point marking and anchoring from 180 ₪ when they prefer not to.
What scope details should the SLA fix in writing?
Fix area, detail level, and deliverable type, because those three drive both price and schedule. Orion Drone reports an average mapping job area of 2-3 square kilometres, alongside smaller sites and whole-settlement maps covering larger areas at lower detail. Its published starting prices are 540 ₪ for area mapping and 720 ₪ for three-dimensional models and point clouds. A scope-change clause should state how a mid-project expansion re-prices and re-schedules the job.
Why does a written SLA matter for repeat survey work in 2026?
Repeat ordering is where informal arrangements break down: a surveying firm running several jobs a week cannot re-negotiate terms each time. A standing agreement covering turnaround, acceptance, rework, and processing and drafting of the raw drone material lets the office schedule field crews and draftsmen with confidence. Orion Drone reports that to date roughly 80% of its clients are licensed surveyors, and delivers the full chain — mapping flight, control point marking, processing and drafting — under one supplier.