C-DRONE GUIDE · 13 AUGUST 2026
Annual multi-site drone contract: pooling missions instead of one quote per site
A retail chain with a network of branches, a multi-plant industrial group, a property company or a social landlord with a building portfolio: as soon as a company manages several sites, drone mission needs repeat from one building to the next — annual regulatory thermography, roof inspection, solar panel monitoring, facade surveys — and each site defaults to triggering its own quote request with a different local provider. An annual framework contract changes that logic: a single point of contact, a price fixed in advance per mission type, an identical report format from one site to the next. Here is when this setup makes sense, how it is structured, and what to define before signing.
Published on 13 August 2026, reviewed on 13 August 2026 — regulations in force as of August 2026.
One quote per site: a drag on a building portfolio
For a portfolio manager or a multi-site health-and-safety officer, scattered quotes cost more than the price shown on each one: time spent re-explaining the need at every site, no continuity in the data from one year to the next — a thermographic report only has comparative value if it is produced under comparable conditions and in a comparable format —, and the risk of missing a regulatory deadline on an isolated site for lack of centralised tracking. Our guide on the tertiary decree and drone thermography covers that obligation building by building; the subject here is different: how to organise it across an entire portfolio rather than site by site.
The problem is especially acute for a geographically spread-out estate: no single provider necessarily covers every region involved, and changing point of contact at every site rules out any reliable comparison between two buildings. Our guide on choosing a drone pilot by geographic coverage covers that criterion for a one-off mission; across a multi-site portfolio, it becomes the very condition for coherent tracking.
What an annual framework contract changes
An annual drone framework contract formalises, for a fixed term — usually one year, renewable —, a common structure for every mission across the portfolio: a single point of contact who already knows the sites and their history, a price per mission type fixed in advance rather than renegotiated at every building, and a guaranteed response time for emergencies — a roof leak spotted after a storm cannot wait for the same procedure as a planned thermography survey. The contract also fixes the frequency of recurring missions (often annual for regulatory thermography, six-monthly for roof checks in a higher-risk area) and requires deliverables in an identical format from one site to the next — the condition for tracking degradation over time rather than stacking up disparate reports.
It is not the only option: a company whose mission volume justifies buying a drone and training an in-house pilot may consider bringing all or part of the need in-house, an option covered in our guide on bringing drones in-house versus outsourcing. The framework contract remains the fastest option to set up and the best fit for a mission volume that does not yet justify an in-house investment.
Missions suited to pooling
Not every mission is equally suited to pooling. The best candidates are those that recur on a predictable cycle, across enough sites to justify setting up a common framework: the annual regulatory thermography survey required by the tertiary decree across a portfolio of offices or retail units, roof-terrace inspection before and after the rainy season across a network of logistics warehouses, checking the yield of solar panels on the roofs of an industrial group running several self-consumption arrays, or auditing the roofs and facades of a social housing portfolio spread across several municipalities.
Conversely, a single one-off mission — a corporate film, event coverage, a topographic survey for an extension project — stays simpler, and often cheaper, as a standalone quote: pooling only makes sense for a need that recurs, across a volume of sites large enough to justify a common framework rather than a string of separate quotes.
What research shows about periodic monitoring
The value of periodic monitoring over isolated checks is not specific to drones. A review by Bagavathiappan, Lahiri, Saravanan, Philip and Jayakumar, published in 2013 in Infrared Physics & Technology, notes that the value of infrared thermography for condition-based maintenance comes largely from repeating it at regular intervals — it catches a drift before it becomes a failure — rather than from an isolated check, which only captures a state at a single point in time (see the study on Google Scholar).
On the specific ground of aerial inspection, a review by Dorafshan and Maguire, published in 2018 in the Journal of Civil Structural Health Monitoring and comparing drone inspection with traditional human bridge inspection, notes that one of the barriers to adoption is less the technical reliability of detection than the asset owner's lack of an organised way to make use of repeated surveys over time rather than isolated inspections (see the study on Google Scholar). A framework contract answers exactly that gap: it turns a series of isolated checks into a comparable history, usable to steer a maintenance budget rather than to react after the fact.
Budget: how an annual contract is priced
As with any drone service, there is no single price for a framework contract: it depends on the number of sites, the type and frequency of missions, and how spread out they are geographically. Two structures come up most often on the French market: a flat rate per site and mission type, discounted beyond a certain number of sites committed for the year; or a total budget excl. VAT committed over twelve months, drawn down mission by mission as work happens. Either way, the gain over the sum of equivalent one-off quotes comes less from a headline discount than from removing hidden costs: no new tender at every site, no re-briefing for a provider discovering the building for the first time, a standard report format already set from the first mission.
Request a quote describing your portfolio of sites, the recurring missions already identified and their frequency: we will put together a framework contract proposal matched to your real volume, without locking you into a commitment disproportionate to your needs.
What to define before signing
A private framework contract does not carry the formal procedure of a public-procurement framework agreement — that process, reserved for local authorities and covered in our guide on buying drone services through public procurement, does not apply to a private company, which remains free to contract directly with a provider. Five points are still worth setting out in writing before signing: the term and the conditions for termination or non-renewal; the deliverable format, identical from one site to the next so degradation can be tracked over time; the handling of data collected at each site — who hosts it, who can access it, how any people caught on camera are anonymised, a point covered in our guide on GDPR applied to professional drones; the provider's professional liability insurance, to check site by site if the areas flown over carry different risks — see our guide on professional drone liability insurance; and the guaranteed response time for unplanned missions, distinct from the timing of the recurring missions already on the calendar.
A well-defined framework contract does not freeze the relationship: it should stay adjustable as the portfolio changes — a site sold off, a new building acquired, a change in regulatory frequency — without needing a full renegotiation for every adjustment.
Frequently asked questions
From how many sites does a drone framework contract become worthwhile?
There is no fixed threshold: what matters is the number of recurring missions rather than the number of sites. A handful of buildings sharing the same annual obligation (thermography, roof checks) is already enough to justify setting up a common framework.
Does a framework contract commit to a fixed number of missions?
It depends on the structure chosen. A total budget drawn down mission by mission leaves room to adjust the volume during the year; a flat rate per site committed in advance gives a more predictable price but less flexibility if the portfolio changes.
Does this type of contract apply to local authorities?
A local authority falls under public procurement rules: it uses a public-procurement framework agreement rather than a direct contract, with a tendering process specific to that framework. The principle of pooling recurring missions stays the same.