# Hot List A **list of license plates of interest** against which ALPR reads are compared in real time. When a camera reads a plate matching a hot list, the system produces a **hit** that triggers an officer alert. Hot lists can be authoritative-database feeds (NCIC, ACIC), agency-internal officer-curated lists, or custom lists shared between agencies. ## Definition (per CPD Policy 800-32) > "Any database that contains lists of license plate numbers that are of interest to police personnel, such as those associated with vehicles and/or license plates that have been stolen, wanted for specific crimes, or those that are associated with, or may assist with the identification of, suspects involved in criminal activity. This will also include data held by the Office of Motor Vehicles, the Arkansas Crime Information Center including without limitation the Arkansas Crime Information Center's Missing Persons database, the National Crime Information Center, and the Federal Bureau of Investigation Kidnapping and Missing Persons database." ## How it appears in the corpus The Conway production surfaces three classes of hot list: 1. **System-feed hot lists** — Per [[LPR Report First Half 2025]]: "The hotlist provided daily by ACIC includes all stolen vehicles, and license plates in the United States, as tracked by NCIC." This is the daily authoritative feed (NCIC routed through Arkansas Crime Information Center). 2. **Agency-internal hot lists** — Per the same report: "CPD hotlist. Officers can manually enter license plates into the system, relevant to investigations." Plates added by Conway officers via the platform admin UI. 3. **Custom shared hot lists** — Per [[Escambia County FL SO Hot List Share]]: a Florida sheriff's office can share its own custom hot list directly into another agency's Flock-platform alert feed. The receiving agency need only configure the "audience" toggle to begin receiving alerts on the foreign list. The H1 2025 reporting data: **6,316,810 reads → 2,007 hits → 3 logged successful outcomes** on the six pre-Flock Genetec cameras. Per CPD Policy 800-32 Section D, the breakdown of hits per hot-list source (which list each hit matched against) is a required public-report field but is not enumerated in the surfaced H1 2025 report. ## Stakeholders - **System operators** (NCIC, ACIC) — provide authoritative-database feeds. - **Agency administrators** (Conway PD's [[Lt. Andrew Burningham]]) — curate the agency-internal hot list and toggle the audience on shared custom hot lists. - **Officers** — receive alerts when a hit is generated. - **Auditing bodies** (LPR supervisor, public via FOIA) — receive the semi-annual statistical accounting. ## Notes - The **CPD Policy 800-32 enumeration** of in-scope hot-list databases is **narrower** than the Flock platform's actual capability. The policy names ACIC, NCIC, OMV, FBI Kidnapping/Missing Persons. The platform supports arbitrary custom hot lists shared from arbitrary jurisdictions. A custom hot list authored by a Florida sheriff is technically a "hot list" under the broader Flock product taxonomy and operationally similar (it produces hits and alerts), but it is not in the CPD-policy enumeration — a policy-vs-practice gap to flag in synthesis. - The Escambia County share is one documented instance. The total count of custom hot lists Conway PD's Flock instance is configured to receive alerts from is not visible in the corpus. A follow-up FOIA item: request a snapshot of all enabled custom hot lists on the Conway Flock instance.