How to Build a Government Drone Program (Policy 101)

Drones have quietly become an everyday tool for public agencies. Not just police and fire, but county road departments, utilities, transit authorities, environmental and emergency-management teams. They're using drones for mapping, inspection, disaster assessment, and infrastructure work.

But here's the catch most small agencies hit: before you can fly, you usually need the paperwork. Who authorizes a flight? Who can cancel one? How long is footage kept? What happens when something goes wrong? Most agencies are small. A pilot or two, and not much administrative capacity. So they either spend serious staff time and legal fees reinventing the wheel, or they fly in a compliance gray zone with no written policy at all.

There's a better way. Here's the plain-English roadmap. (General information, not legal advice. Adopt any policy only with your agency's legal counsel.)

Step 1: Choose your legal framework

A public agency can operate under Part 107 (like any commercial operator) or as a public aircraft operation under a COA (Certificate of Waiver or Authorization). Part 107 is simple to start. A COA can grant broader authority, but it adds responsibility. Pick the path that fits your missions, and pick it with counsel.

Step 2: Write the policy before you buy more drones

The single biggest mistake is buying aircraft before writing the policy. A solid UAS policy manual covers:

• Governance & roles: who runs the program, who's the remote PIC, who approves flights.
• Authorized and prohibited missions: spelled out, so use never drifts.
• Operational control: critical when more than one agency is involved (more below).
• Airspace, risk assessment, and emergency procedures.
• Records, privacy, and data management: retention periods, access logs, public-records handling.
• Contractor oversight: the rules for any vendor flying on your behalf.
• Public communication: transparency that keeps community trust.

Step 3: Solve "who's in charge of this flight?"

When a county asks a city fire department to fly during a disaster, or an agency hires a contractor, or two agencies share aircraft in a mutual-aid response, who actually has operational control? A clean way to decide it before takeoff is four questions:

1. Who requested the aircraft?
2. Who is paying for it?
3. Who is directing it?
4. Who benefits from it?

If the answers point to more than one entity, designate a lead agency in writing, including who holds final cancel authority, before you fly. That prevents dangerous confusion in exactly the high-stakes moments where drones are most valuable.

Step 4: Cover BOTH legal layers

Federal Part 107 is only half the picture. A growing number of states have their own UAS laws: data-handling rules, annual reporting, law-enforcement use restrictions. An agency can be fully Part 107-compliant and still violate state law. Your policy has to bring both layers into one document. (See our post on state drone laws vs. Part 107.)

Step 5: Keep the law-enforcement stuff modular

A public-works department shouldn't have to wade through surveillance and warrant procedures that don't apply to it. Smart programs keep public-safety / law-enforcement provisions in an optional annex. Attach it only if you need it.

Step 6: Adopt, publish, train, review

Route the policy through leadership and legal counsel, adopt and date it, publish it (plus an annual usage report to sustain trust), train every pilot to it, and review it annually and after any incident.

Don't start from scratch

You don't have to build all of this from a blank page. Our Government UAS Policy Toolkit is a customizable, multi-state policy manual. It carries the operational-control framework, contractor oversight, a modular public-safety annex, and a step-by-step customization checklist, all built to be adapted with your counsel. And our Public Safety UAS course covers the operations and legal foundations for agencies flying life-safety missions.

Building a program? Get the Government UAS Policy Toolkit → and skip the blank page.

General information only. Not legal advice. Adopt any policy with your agency's legal counsel; verify federal rules at faa.gov and your state/local requirements with the appropriate authority.