From the Emergency Services edition of November 6, 2026
RapidSOS×APCO survey: 42% of ECCs deploy or pilot AI, but only ~8% completed any AI risk assessment and high-stakes trust stays low
RapidSOS / APCO International · 911 / Emergency Communications Centers · United States (740 respondents; 53 states/regions represented)
- Publisher
- RapidSOS × APCO International State of AI in Public Safety Survey 2026
- Original publication
- October 2026
- Source retrieved
- 2026-11-07
What happened
October 2026 RapidSOS×APCO report (fielded July 31–Sept 17, 2026; n=740) finds 27.0% of ECCs actively deploy AI and 14.5% are piloting (42% combined), with real-time transcription the top capability (~38.9%). Only 3.2% report an established formal AI risk-assessment framework and 4.9% an informal one (~8% any assessment); 49.7% say no. Mean trust that AI can reliably support (not replace) human judgment in high-stakes decisions is 2.5/5; only 18% rate trust at 4–5. Accuracy/reliability is the top adoption barrier (75.3% top-3). Liability for AI-assisted decisions is the top legal concern (75.4%). 40.1% have no AI policy and no plans. Why now: pairs today's vendor EOC routing metrics with national ECC self-report that governance and trust lag adoption.
Why it matters
Core U.S. 911/fire-EMS dispatch governance signal: adoption is spreading while documented risk assessment, policy, and high-stakes trust remain scarce—directly frames sales and delivery of emergency-services AI.
Evidence and measured results
Opened PDF report; methodology states 740 respondents, no incentives; figures cited from Q4, Q16, Q29, Q9, Q34 as printed.
Limitations and uncertainty
Vendor-co-branded survey (RapidSOS) with APCO; self-selected respondents; not a controlled performance study of any product; some policing-capable ECCs included though questions are ECC/911 focused; October publication is slightly before the Nov. 5 last run but newly paired here with fresh ops claims and was not in the emergency-services archive.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- ECC leaders face pressure to adopt AI amid staffing strain but lack trust, risk assessments, and clarity on liability.
- Stakeholders
- 911/ECC director
- Fire/EMS chiefs sharing the center
- County counsel
- Telecommunicator workforce/union
- Elected officials
- APCO/NENA peers
- Discovery questions
- Has a documented AI risk assessment been done?
- Who owns legal oversight if AI contributes to a bad outcome?
- What accuracy evidence exists on local call audio?
- Is there a public notice plan for AI use?
- Value hypothesis
- A governance-first engagement that closes the survey's risk-assessment and policy gaps can unlock safer pilots where agencies already want transcription/non-emergency automation.
- Potential engagement
- ECC AI readiness assessment mapped to the survey's risk, policy, and trust items, producing a board-ready gap report.
- Unsupported claims
- That 42% adoption proves any product is safe
- Guaranteed accuracy improvements
- That RapidSOS sponsorship implies product neutrality on all findings
Pre-sales engineering
Role takeaway
- Fit
- Fits assistive ECC AI (transcription, translation, QA, non-emergency automation) with human judgment retained on high-stakes decisions.
- Architecture and integration
- AI services alongside CAD/call-handling with override, logging, and no silent automation of dispatch recommendations until accuracy gates pass.
- Prerequisites
- Documented risk assessment
- CAD integration plan
- CJIS/privacy review
- Accuracy evaluation dataset
- Constraints
- Survey is perception/self-report not bench accuracy
- Mixed agency types in sample
- Vendor co-brand
- Security
- Address cyber, data security, and privacy risks respondents ranked highly; clarify vendor vs agency data ownership.
- Proof of value
- Pre/post trust score on Q29-like scale
- Accuracy audit on held-out calls
- Completion of formal risk assessment artifact
Delivery
Role takeaway
- Work
- Stand up risk assessment, policy, oversight assignment, and accuracy pilot before scaling AI in the ECC.
- Dependencies
- Legal counsel
- CAD vendor
- QA/training unit
- Labor engagement
- Ownership
- ECC director owns AI use policy; counsel owns liability posture; operations owns day-to-day overrides.
- Skills and adoption
- Train PSTs on when to distrust AI outputs; supervisors audit AI-influenced calls.
- Governance checkpoints
- Risk assessment complete
- Policy adopted or timed plan
- Public communication decision
- Accuracy gate before expanding use cases
- Acceptance criteria
- Written risk assessment on file
- Named legal oversight role
- Measured accuracy/override metrics meeting local bar
- Risks
- Deploying without assessment (majority posture in survey)
- Liability ambiguity after an AI-touched incident
- Staff distrust blocking adoption
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Prioritize human-in-the-loop assistive uses (transcription, translation, QA) with explicit non-automation of high-stakes judgment until risk assessments and accuracy evaluations exist.
Governance
Who approves, reviews and stays accountable for outcomes?
Agencies adopting AI should complete documented risk assessments, assign legal oversight, and publish community notices—areas where the survey shows large gaps.
Security and privacy
What data, permissions and controls need testing?
Respondents rate cyber/data security and privacy among material risks; liability and CJIS/privacy evaluation difficulty are highlighted as barriers.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Translation and transcription top desired capabilities, suggesting accessibility gains for non-English callers, while over-reliance eroding skill is a top-rated risk—training and staffing models must preserve PST judgment.
Procurement
What should contracts, pricing and exit terms secure?
RFPs should demand accuracy evidence, CAD integration, CJIS/privacy detail, and risk-assessment support—the items ECCs say are hardest to evaluate and most needed.
Operating model
Which teams own the service once it runs?
Operate AI as assistive under explicit human authority until trust and formal risk processes mature; publish community notices as centers move beyond pilots.
Publication history
- 2026-11-06Emergency Services · Issue 614 resources
Stable resource ID: rapidsos-apco-state-of-ai-public-safety-survey-202610