From a source record to a next decision

Starting question. A hypothetical H125 support supplier asks: “Does this documented acquisition justify further account research, and which requirements may already be covered?”

1. Select the evidence. Florida Intel's public aircraft excerpt, AC-MD-H125-FLEET, records four H125 / AS350B3 aircraft contracted in 2024 and FAA-registered by December 2025; current mission use is unverified. The Florida edition's base cutoff is September 20, 2026, with September 23 source updates. Read the saved record.
2. Read the transaction, not just the quantity. The county's May 21, 2024 legislative record for RFP-01647 describes the four-aircraft purchase, warranty, training, spares and airframe support. It records approval as amended. These are documented contract components, not proof of a new unfilled requirement. Read the county record ↗.
3. Make a bounded qualification decision. Keep this as an account to research, with “existing acquisition and support coverage; present operational status unverified” attached. Do not turn the four-aircraft quantity or maximum contract value into an available sales pipeline.
4. Set the next checks. Look for newer official delivery and acceptance evidence, current support scope and contract amendments, the responsible purchasing office and any separate current solicitation. Record each unresolved item before deciding whether outreach is warranted.

Illustrative output. One research-qualified account; known acquisition and support context; a short verification list. No current procurement lead or customer outcome is claimed.

Starting question. A hypothetical agency planning a UAS program asks: “Which public examples can help us frame demand and reporting questions for a peer discussion?”

1. Select two dated examples. Wyoming Complete Intel, October 8, 2026, page 17, record WY-ACT-016, reports 55 calls to Cheyenne police's sUAS team during 2025. North Carolina Intel, October 5, 2026, Programs row 10, NC-NTB-POL-UAS-001, points to a February 1, 2026 town update documenting a North Topsail Beach police drone flight. Read the Cheyenne excerpt · Read the North Topsail Beach excerpt.
2. Keep the measures separate. Cheyenne's annual call total suggests a demand-reporting question; a call is not a flight or aircraft. North Topsail Beach's single event shows a dated use, not an annual activity rate. Neither establishes current staffing, fleet size or readiness.
3. Assign a purpose to each peer inquiry. For Cheyenne, ask how deployment calls are defined and converted into launches, mission hours and staffing records. For North Topsail Beach, ask how the weather-response mission was approved, staffed and documented. The sources support these questions, not the answers.
4. Set a comparison rule before planning capacity. Request the same reporting period, mission categories and units from any selected peers, then compare them with your own jurisdiction and service model. Leave staffing and equipment recommendations unresolved until comparable evidence is available.

Illustrative output. A two-program inquiry shortlist and a common set of data questions. This is a research starting point, not a finding that the agencies are operationally equivalent.

Primary evidence: Cheyenne's March 18, 2026 annual-report release ↗ · North Topsail Beach's February 1, 2026 update ↗. These public examples come from separate state editions; purchasing one state does not include another.