•
Nerissa Goedhart
Building the business case for a Drone as First Responder programme
Most public safety organisations looking at Drone as First Responder have stopped asking whether it works. Enough forces are flying to settle that. The question that decides whether a programme happens is narrower and less exciting: can you get it funded, and can you get it funded before the budget year closes.
This is a guide to building that case. It covers what you are actually buying, which costs get missed, what to measure when cost per flight tells you nothing useful, and how the authorisation timeline shapes the calendar you are working to.
What you are actually buying
A DFR programme has three cost blocks, and organisations tend to budget the first one well and the other two badly.
Aircraft and docks. The visible part. Docks are the item that turns a drone team into a DFR programme, because they remove the drive to the scene. The number you need follows from your coverage target rather than from your fleet size, which is a point most business cases get the wrong way round.
Software, integration and connectivity. The layer that turns a dock and a drone into a response capability: the launch decision, the route, the live picture in the control room, the link into computer-aided dispatch (CAD) and into your video management system (VMS), and the record afterwards. This is also where the recurring cost sits, so it belongs in the operating budget rather than the capital one.
People and authorisation. Remote pilots, their training and currency, the person in the control room, and the work of getting an operational authorisation. The last of these is consistently underestimated and it is often the item that sets your start date.
The costs that get missed
Five things turn up late in almost every DFR business case.
The authorisation work itself. Flights to an incident go beyond the pilot's visual line of sight, which puts them in the specific category and means a risk assessment and an operational authorisation from your national aviation authority. That is preparation time, sometimes external support, and a queue at the authority.
Currency and training. Pilots need recurrent training, and a control room operator running several aircraft is a distinct role from a field pilot. Budget the hours.
Connectivity at the dock. A dock on a rooftop needs power and a reliable connection. Site surveys and civil works have a habit of appearing after the drone quote is signed.
Depreciation and replacement. An aircraft launching several times a day reaches its service life faster than a standard write-off schedule assumes, so set the depreciation period on expected flight hours. Batteries are rated in charge cycles, which makes them a consumable in the operating budget rather than part of the capital purchase.
Insurance and legal review. Both are straightforward and both take longer than expected when it is the first time.
What to measure
Cost per flight is the wrong metric and it will sink your case, because a DFR flight is cheap and the number says nothing about value. Four measures tend to hold up better with a finance committee.
Time to first visual. The interval between a call coming in and someone seeing the scene. This is the number a DFR programme moves, and it is measurable from day one.
Calls resolved without a unit. Where the drone arrives first, some incidents need no ground response at all. US forces report this as a share of the calls their drone attended, and Police Chief Magazine puts it at around a quarter across established programmes, with individual forces reporting both less and considerably more. Measure your own once you are running, and check first whether your dispatch policy allows a call to be closed on a drone observation.
Better-informed arrival. Harder to quantify and often the strongest argument in the room. Officers who know what they are walking into make different decisions, and so do commanders deciding what to send.
Evidence and accountability. Automated flights produce a complete record: who authorised, who was in command, what was seen. That has value in court and in oversight, and it is worth naming in the case because it offsets a risk that your legal colleagues will otherwise raise as an objection.
What this looks like in a European force
Belgian Police zones use drones for real-time situational awareness during live incidents, and their experience is a useful reference for anyone building a case, because it speaks to outcomes rather than to technology.
Chief Inspector Bram Schoors puts the outcome plainly: “We have already been able to find two missing persons alive and well thanks to the deployment of the drone via the platform”
First inspector Kristof van den Broeck describes why running more than one aircraft changes the picture available to commanders: “The deployment of multiple drones is a major advantage. It allows us to use one drone to zoom in on the situation and relay coordinates, while the other provides a broad overview of the scene”
There is more in their case study, which is worth attaching to a business case as an annex.
Procurement criteria worth writing in early
Two things belong in your requirements rather than in a later discussion.
Where the data lives. For a police force, the location of video and mission data and the question of who can reach it is rarely a technical footnote. AirHub is a European company, is ISO 27001 and ISO 9001 certified, operates in line with GDPR and European data protection requirements, and can be deployed on-premise or in a private cloud where an organisation needs full control over sensitive operational data. Writing that into the requirement early saves a procurement round later.
Hardware independence. A platform tied to one manufacturer ties your fleet decisions to that manufacturer for the life of the programme. Specifying hardware agnosticism keeps the choice yours.
The calendar problem
Here is the practical constraint on a year-end business case. Your national authority sets your start date, and processing times in several member states are long. An organisation that secures budget in December and opens the authorisation conversation in January is not flying in the first quarter.
So the sequence that works is to start the authority conversation while the budget case is still being written. It costs nothing, it produces a realistic timeline to put in the case, and it turns an optimistic slide into a defensible one.
Our public safety page sets out how the platform supports each stage, and our regulatory consultancy team works with operators on the authorisation route itself.
