'Fully insured' is the phrase that appears in every drone LiDAR quote and means three different things depending on which policy is being referenced. Public liability covers third-party physical damage; professional indemnity covers errors in the deliverable; equipment cover protects the operator's own kit. Each has limits, exclusions and project-specific applicability — and the gap between 'we have insurance' and 'our insurance protects your project' is wider than most buyers realise. This article is the reading-the-certificate field guide.
If you've ever asked a drone LiDAR operator for proof of insurance, received a certificate of currency that looked official, and filed it without really reading it, you've participated in the most common insurance-due-diligence pattern in the industry. The certificate exists; the quote line says "fully insured"; the procurement checkbox gets ticked.
What the certificate often doesn't tell you: whether the cover applies to your specific project, what the relevant exclusions look like, whether the limits are appropriate for the project value, and whether the operator's deliverable errors are actually covered or only covered if catastrophic. Working out the answers takes a careful read of three documents and a few specific questions to the operator — most of which buyers don't ask.
This article is the working pattern: the three insurance types that "fully insured" actually means, the limits appropriate for different project values, the exclusions that routinely bite, the certificate-reading checklist, and the additional-insured nomination that turns operator cover into protection that actually includes your project.
What it covers. Damage to third parties or third- party property caused by the operator's drone operations. Drone hits a parked car: PL responds. Drone falls and injures a pedestrian: PL responds. Drone strikes a powerline and causes outage: PL responds (subject to exclusions).
Typical limits. Australian survey-grade drone operators carry $10-50 million PL cover. The figure appears in the quote and on the certificate.
What "fully insured" usually means. If only one policy type is being referenced, PL is the most common. Worth confirming.
What to watch for. Sub-limits on specific categories (e.g., $5M cap on damage to powerlines even within a $20M overall limit); exclusions for specific operations (BVLOS, populous areas without permit, controlled airspace); territorial restrictions (some policies exclude operations outside Australia).
What it covers. Financial loss to the client arising from professional errors in the deliverable — wrong accuracy, wrong datum, processing errors, missed deliverables. Project owner relies on a DTM, design is wrong because the DTM was wrong, the operator's PI responds to the project owner's direct financial loss.
Typical limits. $1-10 million PI cover is the typical Australian survey range. Smaller operators may have lower limits ($1M); larger operators or those targeting government work carry $5-10M.
What "fully insured" usually doesn't mean. Many operators carry PL but skip PI, or carry token PI ($500k). For projects where deliverable accuracy genuinely matters financially, PI cover is the relevant policy — but it's often the missing one.
What to watch for. Sub-limits for design-and- construction errors vs pure data errors; exclusions for project-specific work types; aggregate vs per- occurrence limits (aggregate means the limit is shared across all claims in the policy year, not per-project).
What it covers. The operator's own kit if it's damaged, lost or stolen. Drone crashes into a tree: equipment cover responds (or doesn't, depending on exclusions for operator error).
Typical limits. Usually equivalent to the replacement cost of the operator's fleet — $200,000-1,000,000 for a survey-grade operator with modern hardware.
Relevance to buyers. Indirect. Equipment cover doesn't protect the project; it protects the operator's ability to continue trading after a kit loss. The connection is that an operator without equipment cover who loses a sensor mid-project may struggle to deliver. Worth knowing the operator carries it; not the primary thing to check.
A useful framework: the PL limit should be proportional to the worst-case damage the drone could cause on your specific site. The PI limit should be proportional to your worst-case downstream loss from a defective deliverable.
Small project, low-risk site (open paddock, planning- grade deliverable, no nearby infrastructure).
Mid-size project, moderate-risk site (mixed land use, some infrastructure within or near AOI, engineering-grade deliverable).
Large project, high-risk site (active infrastructure, populated areas, complex airspace, critical infrastructure exposure).
Programme work (multi-cycle, multi-million-dollar combined contract value).
The operator quotes a single set of limits across all their work; the question for the buyer is whether those limits match your project's risk profile.
Specific exclusion clauses worth checking on the certificate or policy:
BVLOS operations. Many PL policies exclude or restrict cover for Beyond Visual Line of Sight operations. If the project requires BVLOS, the operator needs specific endorsement covering it. (See BVLOS article for the operational context.)
Populous areas. Operations over public areas with no permit can void cover. Even with a permit, the limit may be sub-limited or the cover may have specific conditions. Confirm the policy aligns with the operator's CASA approvals.
Controlled airspace. Operations within controlled airspace (typically near aerodromes) without appropriate clearance can void cover. Confirm the operator's PL covers the specific airspace classes of your project.
Contractual liability. Some PL policies exclude liability assumed under contract beyond what would exist at common law. If your contract has indemnity clauses, the operator's PL may not respond to a claim arising from those clauses. Worth a specific question.
Indirect or consequential loss. PI policies typically exclude indirect or consequential loss (loss of revenue, project delay damages). The direct loss from a deliverable error is covered; the downstream business consequences may not be.
Pollution. Drone batteries can cause fire and spillage; some PL policies exclude pollution events. Worth checking for fire-prone or environmentally sensitive sites.
Operator under-25 / unqualified pilot. Some policies have age or qualification minimums for named operators. If the operator's certificate of currency lists qualified pilots and the field crew on the day doesn't match, cover may not apply.
Pre-existing damage / wear and tear. Equipment cover typically excludes pre-existing damage or normal wear; relevant if equipment cover is being relied on for a specific kit-loss scenario.
A certificate of currency (COC) is the standard insurance proof document. It's not a copy of the policy; it's a summary. Specific items to read:
Insured party. Should match the operator's legal trading name. A certificate naming "ABC Drones Pty Ltd" for an operator trading as "ABC Survey" may indicate a related but different entity. Worth clarifying.
Policy number. Should be a real policy number referenceable with the insurer. If you have concerns, you can call the insurer to verify the policy is current (most insurers will confirm existence and limits, though not specific terms).
Limits. Specifically stated. "Up to $20M public liability" with no sub-limit caveats is cleaner than "$20M aggregate with $5M sub-limits for X, Y, Z".
Excess / deductible. The amount the operator pays before the policy responds. A $50k excess means small claims aren't covered — relevant for PL claims under that threshold.
Policy period. Should cover the entire duration of your project. A COC valid until 30 June for a project running into August is a problem unless renewal is confirmed.
Insurer name. Should be a recognised Australian insurer or Lloyd's syndicate. Less recognised insurers may have limited capacity in a large claim scenario.
Endorsements / additional insured. If the certificate lists your organisation as an additional insured, that's a substantive protection (see next section). If it doesn't, the cover is the operator's protection, not yours.
The single most useful insurance arrangement for project buyers, and one that's commonly missed.
What it is. A specific endorsement to the operator's PL policy that names your organisation as a co-insured party for the duration of the project. If a third party sues both the operator and your organisation over an incident, both parties are defended by the operator's insurer up to the policy limit.
Why it matters. Without the nomination, you are protected only by your own insurance and any indemnity clause you've negotiated against the operator. With the nomination, the operator's insurer is on the hook for your defence as well.
Cost. Operators can typically add an additional-insured endorsement for $100-500 per project, or sometimes at no charge as a relationship gesture. Cheap relative to the protection it provides.
When to request it. Any project where:
The additional-insured nomination is the gold standard for buyer-side insurance protection. Most buyers don't ask; most operators don't proactively offer.
Six questions that surface the insurance picture:
1. "Can you provide certificates of currency for public liability AND professional indemnity?" Both documents, not just one.
2. "What are the specific limits and any sub- limits on each policy?" Forces specific numbers rather than "fully insured".
3. "Are there exclusions relevant to my project type?" BVLOS, populous areas, controlled airspace — ask explicitly if any apply.
4. "Can I be named as an additional insured for this project?" Tests both willingness and policy flexibility.
5. "Are your aggregate or per-occurrence limits adequate for our combined contract value?" Relevant for programme work where multiple claims could occur in one policy year.
6. "What's your claims history in the last 3 years?" Optional but useful — operators with a clean record will say so; operators with a history will either disclose or deflect.
Three patterns we see:
Treating "fully insured" as a verified fact. The phrase appears on the quote; the certificate isn't requested. Most operators do have appropriate insurance, but the few who don't are exactly the ones whose claims you'd most need to call on.
Requesting the certificate without reading it. The document arrives; goes into procurement file; never examined. The reading takes 15 minutes; catches the exclusions that bite.
Not requesting additional-insured nomination on high-value projects. The single most protective arrangement, missed because buyers don't know to ask.
For some projects, the operator's standard insurance is structurally insufficient regardless of how it's read. Three scenarios:
Critical infrastructure work. Power, water, telecoms, rail — the third-party exposure can exceed standard PL limits. Either require specific project-level insurance or accept that operator cover is partial.
Operations adjacent to high-value assets. Mining operations, hazardous facilities, expensive machinery. PL cover may be inadequate; equipment- specific cover may be needed.
Multi-year programme work. Aggregate limits become an issue. May warrant operator obtaining project-specific policies rather than relying on their annual cover.
For these cases, the right answer is sometimes buyer-procured insurance covering the project, sometimes a higher-limit operator policy obtained for the specific project, sometimes an additional- insured arrangement with higher limits negotiated specifically. None are typical defaults; all are arrangements that can be put in place when the project warrants it.
"Fully insured" on a quote means three different policies: public liability (third-party damage, $10-50M typical), professional indemnity (deliverable errors, $1-10M typical), equipment cover (operator's own kit, indirect relevance).
Appropriate limits scale with project risk: $10M PL / $1-2M PI for low-risk planning work, $20M PL / $5M PI for mid-size engineering, $50M+ PL / $10M+ PI for high-risk infrastructure.
Exclusions that routinely bite: BVLOS, populous areas, controlled airspace, contractual liability, indirect/consequential loss, pollution, operator qualifications, pre-existing damage.
Certificate-reading checklist: insured party matches, policy number real, limits explicit, excess understood, period covers the project, insurer recognised, endorsements noted.
The additional-insured nomination is the gold standard for buyer-side insurance protection — operator's PL extends to defend the buyer in a third-party claim. Cheap to obtain ($100-500), rarely requested, materially more protective than just the indemnity clause.
Six questions surface the insurance picture without ambiguity. For critical-infrastructure or high-value projects, operator standard insurance may be structurally inadequate and project- specific arrangements are warranted.
If you're scoping a project and want a sample certificate-of-currency review against your specific project shape, send through the project parameters and we'll walk through what limits and endorsements would be appropriate — including the additional-insured arrangement if it's warranted. Insurance is the part of procurement most buyers skip; it's also where the catastrophic-event protection actually lives.
The regulatory document set that sits alongside insurance — both are administrative due-diligence items that distinguish reputable operators from improvised ones.
Insurance verification is one of the procurement-checklist items most commonly skipped — the broader checklist of buyer-side due diligence.