How to Justify a UAV Programme to Your Procurement Committee
You have identified the operational need. You have evaluated the platforms. You know what you want to procure. The hardest part of a government UAV programme is not the technology - it is the internal approval process.
This guide covers how to build the business case, answer the five questions your committee will ask, and structure a recommendation that survives the procurement review.
Where UAV Programmes Actually Stall
Most UAV procurement cycles in government and defence do not fail because of technology. They stall because the internal business case is not structured to answer the specific objections that procurement committees, finance departments, and legal teams raise.
The security manager or operational lead who initiates the procurement knows why UAVs are needed. The procurement committee does not start from that knowledge - they start from budget scrutiny, vendor risk assessment, compliance questions, and comparisons with existing capability. If your submission does not proactively address those angles, it will be returned for more information. Multiple times.
Understanding the procurement committee's actual concerns - not just the operational case - is what separates submissions that get approved quickly from those that spend 18 months in review.
The Five Questions Your Committee Will Ask
Based on the procurement discussions we have had with government and defence organisations across the EU and internationally, the same five objections appear in almost every case. Address them in your submission before they are raised.
What is the total cost of ownership over five years?
Unit price is the wrong metric for a UAV programme evaluation. Committees that approve capital spend need to see TCO - platform cost, operator training, maintenance, spare parts, insurance, and EASA certification costs combined. More importantly, they need this compared against the cost of the capability they are replacing: helicopter hours, ground team days, or contracted surveillance services. The comparison almost always favours the UAV programme when stated correctly.
Who owns the data?
This is the most frequently raised objection in EU government procurement since 2023. The committee needs a clear, written answer: where is operational data stored, who can access it, and under what legal jurisdiction does it sit. For platforms with cloud-connected telemetry, this question cannot be answered satisfactorily. A platform with self-hosted data architecture answers it in one sentence: all data remains on infrastructure under your direct control.
Are we compliant with NIS2 / GDPR / EASA requirements?
Compliance questions are often raised by legal or IT security teams who have been copied on the procurement request. Your submission should include a one-page compliance summary covering: EASA airspace category (Specific or Open, and why), GDPR data processing basis for any footage of persons, and NIS2 supply chain security obligations if your organisation is classified as essential infrastructure. Each of these has a documented answer - have them prepared.
What happens if the vendor fails or withdraws from the market?
This is a vendor lock-in question, and it is legitimate. A procurement committee approving a multi-year operational dependency on a single vendor needs to understand exit options. Your answer should cover: platform documentation ownership, whether spare parts are standardised or proprietary, and what contractual protections exist if the vendor is acquired, sanctioned, or otherwise becomes unavailable. Platforms with open documentation and standard components are substantially easier to answer for than closed-ecosystem hardware.
What is the risk if this does not work?
Committees approve spend; they also approve risk. The de-risk mechanism for a UAV procurement is a structured assessment phase before hardware commitment. Framing your procurement as a phased process - operational assessment first, hardware specification second - significantly reduces the perceived risk of the decision. The committee is no longer approving a multi-year hardware contract; they are approving a four-week assessment with a written outcome. That is an easier decision to make.
Building the TCO Comparison
Total cost of ownership comparisons are the most persuasive element of a UAV procurement business case when done correctly. The mistake most operational leads make is comparing the UAV unit price against other UAV unit prices. The right comparison is against the current cost of delivering the same operational outcome.
Structure the TCO comparison in three columns:
- Current method: Total annual cost of helicopter hours, ground teams, contracted surveillance, or other means currently used to achieve the same surveillance or inspection output.
- UAV programme (Year 1): Platform cost plus operator training plus EASA authorisation plus integration setup. This will be higher than current method in Year 1.
- UAV programme (Years 2–5): Operational cost only - maintenance, parts, crew time.
The break-even point is usually 18–24 months for surveillance applications and 12–18 months for inspection applications where helicopter costs are the alternative. Present this as a graph, not a table - the visual form of a break-even curve is significantly more persuasive in committee than rows of numbers.
Answering the Data Sovereignty Question
Data sovereignty has moved from a preference to a hard requirement in EU government procurement in the last two years. The NIS2 Directive, the EU AI Act, and a series of documented security incidents have changed the baseline expectation in procurement reviews.
Your submission should include a data flow diagram - even a simple one - showing what data the UAV generates, where it is stored, who can access it, and under what legal framework. For many closed-ecosystem platforms, this diagram cannot be completed accurately because the data routing architecture is not publicly documented and does not permit third-party audit.
For a sovereign UAV platform with self-hosted architecture, the diagram is simple and auditable. That simplicity is itself persuasive - it demonstrates that the vendor has nothing to hide and that operational data is genuinely under the operator's control.
How to Structure the Hardware Recommendation
A procurement submission that specifies a single platform is vulnerable to the objection that alternatives were not properly evaluated. The recommended structure is:
- Define the operational requirement first. Payload capacity, range, endurance, environmental conditions, data sovereignty requirements. This section should be written by the operational lead, not the procurement team.
- Evaluate platforms against the requirement. A structured comparison of three to four platforms against your defined criteria. Include lower-cost alternatives in the comparison - and document how they score on the data sovereignty criterion. This pre-empts the objection that you did not consider cheaper options.
- Recommend the Phase 1 Assessment, not the hardware. Frame your procurement recommendation as approval for an operational assessment phase, not a hardware purchase. The assessment ends with a written specification - that specification then becomes the basis for the hardware procurement in Phase 2. This reduces the perceived risk of the initial decision dramatically.
The Phase 1 Assessment as a Procurement De-Risk Tool
The most effective mechanism for getting UAV procurement approved through a conservative committee is to separate the capability decision from the hardware decision.
A Phase 1 operational assessment - four weeks, on-site - answers the questions that committees cannot answer from a brochure: What exactly does your operation need? Which payload configuration delivers it? What EASA authorisation path is required? What does operator training look like for your team?
The output is a written specification document, not a sales proposal. It documents your operational requirement, the recommended hardware configuration, and the total cost of the full deployment. That document then becomes the basis for the Phase 2 hardware procurement submission - which is far easier to approve because the uncertainty has been eliminated.
From a committee perspective, you are asking them to approve a bounded, defined-cost assessment that generates a specification. That is a straightforward decision. The hardware purchase that follows is supported by evidence, not speculation.
Request a Phase 1 Assessment
If you are in the business case phase and need a vendor who can support the procurement process - not just supply hardware - contact us. We work directly with operational leads preparing committee submissions, and we can provide the operational data, compliance documentation, and TCO frameworks that procurement teams require.
