How to Write an Agency Drone RFP: 2026 Procurement Checklist

Most agency drone purchases don't fail because someone picked the wrong aircraft. They fail because the solicitation never said what the aircraft had to do, who would fly it, where the data would live, or which funding rules applied. The result is a protest, a re-bid, or a fleet that sits in a closet because nobody budgeted for batteries and training.

This guide walks public safety, public works, and other government buyers through writing a drone RFP (or RFQ, or ITB) in 2026. It's a practical checklist, not a legal template. Your purchasing office, counsel, and grant administrator have the final word on format and terms.

Step 1: Decide which solicitation you actually need

Before you write a single requirement, confirm the procurement path with your purchasing office. The right document depends on the size of the buy, your local thresholds, and whether federal money is involved.

• Request for Quote (RFQ): best when you already know the exact configuration and you're mostly comparing price, availability, and delivery.
• Invitation to Bid (ITB): a sealed, lowest-responsive-bid process. Works for well-defined commodity buys, but it punishes vague specs.
• Request for Proposal (RFP): best when you want vendors to propose a solution (aircraft, payloads, software, training, support) and you'll score on more than price.
• Cooperative contracts: many agencies buy through existing state or cooperative purchasing contracts. If you go this route, still use the checklist below to write your internal requirements and quote request.

If any portion is grant-funded, read the grant's terms before you choose. Federal awards carry their own procurement standards (see 2 CFR 200 for most federal grants), and many now carry drone sourcing restrictions.

Step 2: Write mission requirements, not brand requirements

The strongest RFPs describe outcomes. "Locate a person-sized heat signature at night from a standoff distance" is a requirement vendors can answer. "Must be Brand X Model Y" invites a protest unless you've documented a sole-source justification.

Start by listing the missions the program will fly in its first two years, then translate each one into measurable capabilities:

For thermal missions, decide early whether you need temperature measurement. Our guide on choosing field vs docked public safety aircraft shows how mission type drives the platform choice.

Step 3: Get the sourcing and compliance language right

This is the section that causes the most rework in 2026. Write it with your grant administrator and counsel, then copy it word for word into the solicitation.

• Funding source: state plainly whether federal grant, cooperative agreement, or other federal award funds will pay for any part of the purchase or its operation. Since December 22, 2025, the American Security Drone Act restricts using federal award funds to procure or operate drones from covered foreign entities. See OMB memo M-26-02 and your grantor's guidance for specifics.
• NDAA / Blue UAS language: if you require it, say exactly what you require: "NDAA-compliant components," "listed on the DCMA Blue UAS Cleared List," or both. These aren't the same thing. Ask bidders to cite the exact listed configuration and point to it on bluelist.dcma.mil.
• FCC Covered List: ask bidders to confirm that the equipment and its radios are authorized for sale and use, and check the FCC Covered List yourself before award.
• State and local rules: several states restrict which drones agencies may buy or fly. Cite your state's rule if one applies.
• Remote ID: require FAA Remote ID compliance for every aircraft. Our Remote ID explainer covers the basics.

A common mistake is to describe Blue UAS as a certification. It isn't one; it's a cleared list of specific configurations. Require listing on the Blue UAS Cleared List for the specific configuration, and have the bidder provide documentation. Our NDAA and Blue UAS buying guide explains the differences in plain language.

Step 4: Specify data security and records handling

Drones create evidence, public records, and sometimes sensitive infrastructure data. The RFP should require bidders to answer, in writing:

• Where flight logs, photos, and video are stored by default (on the aircraft, controller, local server, or cloud), and in which country any cloud service is hosted.
• Whether the system can operate fully offline or in a local data mode, and how that mode is enforced.
• How firmware updates are delivered and whether your IT team can control their timing.
• Encryption for the video link, stored media, and any fleet management platform.
• Export formats for evidence and records retention, and whether metadata (time, GPS, altitude) is preserved.
• Whether the vendor has third-party security assessments to share.

Bring your IT security lead into the scoring. If your agency follows CJIS or similar policies, say so in the solicitation so bidders can answer specifically.

Step 5: Don't forget the "day one" items

Aircraft-only bids look attractive on a tab sheet and then stall the program. Require a complete, ready-to-fly configuration. At a minimum, ask bidders to itemize:

• Aircraft, controller, and any required ground station or relay.
• Payloads by mission (thermal, zoom, mapping camera, spotlight, speaker).
• Batteries sized for a full operational period, plus chargers and a field charging plan.
• Hard cases, spare propellers, and a spare-parts kit.
• Software licenses (flight, fleet management, mapping or processing) with term lengths.
• Training for pilots and visual observers, plus any manufacturer certification.
• Warranty and repair coverage, including loaner or advance-replacement options.

Our guide to budgeting a full kit vs aircraft-only lists what usually gets missed.

Step 6: Build a scoring rubric before you release the RFP

Publish the evaluation criteria and weights in the solicitation. A balanced rubric for a public safety drone RFP often looks like this (adjust to your policy):

• Technical fit to missions, scored against your capability table.
• Compliance, often pass/fail: sourcing, Remote ID, FCC authorization, data handling.
• Total cost of ownership over the expected service life: batteries, software renewals, repairs, and training, not just the aircraft.
• Support and lead time: delivery date, repair turnaround, US-based support, and spare parts availability.
• Demonstration results, if you hold a fly-off.
• References from comparable agencies.

If you plan a demo or fly-off, describe the scenarios in advance and score every bidder the same way. Record the demo flights for your file.

Step 7: Plan the program, not just the purchase

Evaluators and councils increasingly ask "what happens after delivery?" Include, or ask bidders to support:

• Operating framework: will you fly under Part 107, as a public aircraft under an FAA certificate of waiver or authorization, or both? Decide before you write training requirements.
• Policy and community transparency: many agencies publish a drone use policy and flight log summary. Grant programs may require privacy and civil liberties policies.
• Maintenance and battery lifecycle: who tracks cycles, firmware, and inspections.
• Growth path: whether the platform supports added payloads, docks, or a second aircraft class later.

Agency drone RFP checklist (copy and paste)

• ☐ Procurement method confirmed with purchasing (RFQ, ITB, RFP, cooperative)
• ☐ Funding sources identified, with grant terms and drone clauses attached
• ☐ Mission list translated into measurable capability requirements
• ☐ Sourcing language reviewed by counsel (NDAA, Blue UAS listing, ASDA, state rules)
• ☐ Bidders required to cite exact Blue UAS listed configuration, if required
• ☐ FCC Covered List and Remote ID requirements stated
• ☐ Data storage, encryption, offline mode, and firmware questions included
• ☐ Complete kit itemized: batteries, chargers, cases, spares, software, training
• ☐ Warranty, repair turnaround, and loaner terms requested
• ☐ Scoring rubric and weights published
• ☐ Demo or fly-off scenarios defined in advance
• ☐ Delivery date and lead-time commitments requested in writing

Get help building a quote package

We're an enterprise drone retailer in Irvine, California, and we help agencies turn mission lists into complete, itemized quotes for DJI Matrice and NDAA / Blue-candidate platforms. If you're drafting a solicitation or need a budgetary quote to size a grant application, send us your missions, timeline, and funding source.

Request an agency quote →

This article is general information, not legal or procurement advice. Follow your agency's purchasing rules and your grant's terms. Regulatory references reflect public guidance as of October 2026. Always confirm listings on bluelist.dcma.mil and fcc.gov/supplychain/coveredlist.