IACP 2026 Annual Conference: What Policing-Technology Buyers Should Watch For in Orlando
600-plus vendors, 16,000 attendees, and a regulatory year that changed which questions matter. A procurement-side guide to the IACP 2026 exposition floor.
By IPA-IAC · 6 min · 6 August 2026
The IACP Annual Conference and Exposition returns to the Orange County Convention Center in Orlando, October 24–27, 2026, with more than 16,000 public safety professionals and over 600 vendors in an exposition hall open Sunday through Tuesday.
For agencies attending with budget authority, 2026 is a different buying year than 2025 was. Not because the products changed dramatically, but because the year produced a series of enforcement actions, audits, and statutory sunsets that moved several questions from “nice to have in the contract” to “the thing that determines whether you can operate the system at all.” The demo will not surface them. You have to ask.
The Question That Now Precedes All Others
For any system that stores or shares operational data, ask this before features: can you export a complete, per-query audit trail, including queries run by outside agencies against our data, with requesting user, agency, timestamp, and stated purpose — as a file we control?
The reason is the 2026 record. Dayton discovered through audit that its ALPR data had been searched more than 7,100 times for immigration enforcement — a use its own policy prohibited — by outside agencies on a shared network. Illinois’s Secretary of State found a vendor had facilitated federal access contrary to state law and ordered it shut off. In neither case did the operating agency authorize the conduct; in both cases it lacked the visibility to notice.
A vendor dashboard summary is not an audit trail. If the answer involves opening a support ticket, or if the export omits external queries, that is a finding at the booth rather than eighteen months later. This applies to ALPR platforms most acutely, but equally to any regional information-sharing system.
Category-Specific Questions
ALPR and shared-network camera systems. Beyond the audit export: what is the default sharing scope for a new deployment, and who can change it? Several 2026 incidents traced to national or regional lookup defaults that were broader than the purchasing agency believed. Ask whether retention can be configured by purpose rather than as a single global value — Washington’s SB 6002 requires tiered retention, from 12 hours for parking enforcement to 21 days as a default, and a platform that supports only one number cannot comply. Ask how the system handles a warrant requirement for data held by private entities, which Washington now imposes.
Facial recognition. The threshold question is legal, not technical: do you have express statutory authorization? Virginia’s authorizing statute sunset on July 1, 2026, and the replacement provisions specify that statutes not explicitly referencing facial recognition cannot be read as authorization. Several states require a warrant, probable cause, or a court order, and the standards differ materially between them.
Where you can procure, Virginia’s expired framework left behind the most concrete standard any state adopted: NIST-evaluated systems demonstrating at least 98 percent true positives with minimal performance variation across demographics. Use it as a floor even where it is not law — and press on the gap it leaves. NIST test conditions do not resemble a low-quality probe image from an overhead camera, and field performance on poor probes is where documented misidentifications originate. Ask for accuracy data on degraded imagery specifically. Most vendors will not have it, which is itself informative.
AI-assisted report writing. This is the fastest-moving category on the floor and the one with the newest compliance surface. Ask what artifact the system retains to establish which portions of a report were machine-generated, because disclosure requirements now vary by state and a system that produces no provenance record cannot satisfy one. Ask whether draft text and the underlying audio or notes persist, where, and for how long — that material is discoverable.
Analytics and alerting. For any system that generates suspicion rather than answering a query, ask what the false-positive rate is under the customer’s own conditions and how it is measured. LAPD discontinued an ALPR deployment in 2026 after an audit reportedly found roughly one in three hot-list alerts were false. An unmeasured error rate is not a low one. Proactive alerting also produces records that are harder to reconstruct after the fact than query logs, which raises the governance stakes for real-time crime center deployments and for pattern-alerting ALPR products.
Dispatch and NG911. Carriers and PSAP vendors are working through new federal location and interconnection obligations, and the FCC’s 2026 NG911 order sets deadlines that depend on originating service providers as much as on the PSAP. Ask vendors to state which obligations fall on them versus on your carrier, in writing. Interoperability claims deserve the same scrutiny they always have in CAD/RMS procurement — ask for a reference customer running the same integration you are buying, not a capability statement.
Contract Terms Worth More Than Features
Four provisions determine what happens after the honeymoon, and none of them appear in a demo.
Data ownership and portability. Who owns the records, and what does exit look like? Ask for the export format and whether historical data comes with you. Agencies that cancelled contracts in 2026 — the EFF has documented at least 53 cities across 20 states terminating or declining ALPR contracts — discovered exit terms mattered.
Public records exposure. A Washington court held that data captured by these camera systems are subject to public disclosure. That changes both your retention calculus and your redaction workload. Ask whether the platform has any tooling for responding to a records request at volume, because if it does not, that labor is yours.
Subprocessors and downstream access. Who else touches the data — cloud hosts, analytics partners, the vendor’s own staff — and under what terms? Several 2026 findings involved access paths the purchasing agency had not mapped.
Price escalation and the renewal cliff. Multi-year camera and cloud subscriptions with escalators in later years are common. Model the year-three and year-five cost before signing, not the year-one promotional figure.
How to Use the Floor
The exposition is worth attending precisely because it compresses 600 vendors into three days, but it rewards preparation over browsing. Arrive with a written list of the questions above, ask them at every relevant booth, and record who could answer and who deferred. The pattern in the answers is more useful than any single response.
Then confirm the important ones in writing before procurement. A capable salesperson can answer an audit-trail question affirmatively in good faith and still be describing a roadmap item. The agencies that spent 2026 explaining audit findings to their councils generally had the vendor’s verbal assurance and not much else.