The DFR policy and SOP checklist: everything your drone program should have in writing
A complete DFR policy package covers six areas: operating authority (Part 107 with waivers, or public aircraft operations under a COA), operational SOPs including launch criteria and lost-link procedures, video and data handling, training and currency, community-facing transparency, and a scheduled review cadence.
A Drone as First Responder program runs on paper as much as it runs on aircraft. When something goes wrong (a lost link over a school, a records request, an FAA question, a council challenge), the first thing anyone asks for is the policy and the SOPs. This is a practical checklist of what should exist in writing before your program flies, organized the way most agencies actually build it: authority first, operations second, data third, people fourth, public last, and then a schedule for revisiting all of it.
1. Operating authority: Part 107 or a public-aircraft COA?
Everything downstream depends on which legal pathway you fly under, so settle this first. Public safety agencies have two options, and the FAA's Public Safety Toolkit walks through both:
| Part 107 (with waivers) | Public aircraft operations (COA) | |
|---|---|---|
| Pilot credential | FAA Remote Pilot Certificate required | Agency self-certifies pilots, with a documented training program |
| Operating limits | Standard Part 107 rules; waivers for night, over people, BVLOS | Defined by the COA: areas, altitudes, ATC coordination |
| Best fit | Fastest way to start; well-understood framework | Recurring governmental operations under an approved concept of operations |
Many programs run both: Part 107 as the foundation, a COA for the recurring DFR mission. Whichever you choose, the SOPs below must match the authority you actually hold. An SOP that assumes a waiver you never obtained is a finding waiting to happen.
2. Policy foundations
- Purpose statement and authorized uses. What the program is for, stated as a positive list. Anything not listed is out.
- Prohibited uses. Written explicitly, not implied. Typical entries: routine neighborhood patrol, monitoring lawful assemblies, harassment, and any use outside the purpose statement.
- Roles and accountability. Program manager, chief pilot, remote pilots, visual observers: who owns compliance, and who can ground the program.
- Legal review. Counsel sign-off on the policy against state law, local ordinance, and your operating authority.
- Insurance and mutual aid. Coverage for the aircraft and operations, and written terms for any flying done on behalf of neighboring agencies. Borrowed missions still run under your policy.
3. Operational SOPs
This is the working core of the program. At minimum:
- Mission planning. Airspace check, weather minimums, crew assignments, notification requirements, and risk assessment before launch.
- Launch criteria. The specific call types and conditions that justify a DFR launch, and who has authority to order or deny one. Vague launch criteria are how mission creep starts.
- Standardized pre-flight and post-flight checklists. Written, versioned, and actually used. The FAA toolkit includes checklist templates; adapt them rather than inventing from scratch.
- Emergency procedures. Flyaway, battery failure, injury on the ground, manned-aircraft conflict, each with a named action sequence.
- Lost-link procedures. What the aircraft is programmed to do, where it goes, and who gets notified. This must match the aircraft's actual configuration, not the manual's defaults.
- Flight debriefs. A short, structured debrief after missions, feeding a log of issues that the program review (section 6) actually reads.
4. Video and data handling
This section of the SOP gets the most outside scrutiny, from councils, records requesters, and courts, so write it tightly:
- Who sees the live feed. Decide deliberately which roles can view live video and how it reaches command, dispatch, or a teleoperator. Ad-hoc screen-sharing is not a policy.
- Whether video is retained at all. This is a real architectural choice, not a default. If you retain, specify what, where, the retention schedule, access controls, and how footage enters evidence. If you stream live-only, say so. A live-only layer such as BabbarOps, where video is watched in real time and never stored, keeps this entire section short: no archive accrues, and your evidence system remains the only system of record.
- Records and disclosure. How flight logs, telemetry, and any retained video are handled under your state's public-records law.
5. Training and currency
- Initial qualification. Part 107 certificate, or the agency's documented self-certification curriculum under a COA. The FAA expects the training program itself to be documented either way.
- Currency requirements. Minimum flight hours or sorties per quarter, recurrent training, and night or BVLOS currency where waivers apply.
- Scenario training. Emergency and lost-link procedures practiced, not just read. A lost-link SOP nobody has rehearsed is a paragraph, not a capability.
- Records. Per-pilot training files: certificates, currency, evaluations, and remedial actions.
6. Community transparency and review cadence
The community-facing layer is policy, not public relations: publish the purpose limits and prohibited uses, report flight activity (a public dashboard with flight logs is becoming the norm among leading programs), and name a contact for questions and complaints.
Then put review on the calendar. A practical cadence: SOPs reviewed annually or after any incident, waiver or COA terms checked against current operations quarterly, the public policy revisited with the governing body at renewal, and the whole package re-read whenever the FAA changes the rules, which, with BVLOS rulemaking moving, it will. A DFR program is never finished being written; the checklist above is the version you keep current, not the one you frame.
The test for the whole package is simple. If you can hand a single binder (operating authority, policy, SOPs, checklists, training records, data-handling rules, and transparency commitments) to an FAA inspector, a city council, or a records requester without flinching, your program is in good shape. Build the binder before the program needs it.
At minimum: mission planning, specific launch criteria and launch authority, standardized pre-flight and post-flight checklists, emergency procedures, lost-link procedures that match the aircraft's actual configuration, and structured flight debriefs. It should also be paired with policy-level documents covering purpose limits, prohibited uses, video and data handling, and training requirements.
Part 107 (with waivers for night, over-people, or BVLOS operations) is the fastest, best-understood way to start and requires pilots to hold an FAA Remote Pilot Certificate. Public aircraft operations under a COA suit recurring governmental missions and let the agency self-certify pilots, but require a documented training program and operate within the COA's defined areas and conditions. Many agencies run both, and the FAA Public Safety Toolkit covers each pathway.
A free FAA resource collection for public safety agencies starting or running drone programs. It explains the two operating pathways, Part 107 and public aircraft operations under a COA, and includes practical materials such as a Part 107 waivered-operations checklist and program guidance that agencies can adapt into their own SOPs.
Decide deliberately who can view the live feed, how it reaches command, and whether video is retained at all. If video is retained, the SOP must specify storage, retention schedules, access controls, and public-records handling. A live-only streaming layer, where video is watched in real time and never stored, keeps the data-handling section short because no archive accumulates and the agency's evidence system stays the only system of record.
See how a live-only video layer simplifies the data-handling section of your DFR SOP.
This article is general information, not legal or regulatory advice. FAA requirements change and differ by operation type, aircraft, and authority. Confirm current requirements with the FAA, your COA or waiver terms, and your agency's legal authority before operating. BabbarOps is an independent commercial product and is not affiliated with or endorsed by the FAA or any law enforcement agency.