A license plate reader hotlist is a list of plates of interest, such as stolen vehicles, wanted persons and missing persons, that the system checks every read against. A match triggers an alert. Hotlists must be kept current, with an owner, a reason for each entry and an expiry date, and an officer must verify every hit before acting.
What a license plate reader hotlist is
A license plate reader hotlist is a list of plates the system checks every read against. When a passing vehicle’s plate matches an entry, the system raises a hit, also called an alert, and notifies the people who should see it. The hotlist is what turns a camera that only records plates into one that helps find stolen vehicles, wanted persons and missing people. For the vocabulary, see the ALPR, LPR and ANPR glossary.
Where hotlists come from
Hotlists are built from several kinds of records. Which ones an agency uses depends on its policy and its access to state and national systems.
Stolen vehicles
Reports of stolen vehicles and plates from the agency’s own records, and from state and national records such as NCIC. See stolen vehicle alerts.
Wanted and protective-order subjects
Plates linked to a wanted person or an active order, entered under the agency’s authority and policy.
Missing and endangered persons
AMBER, Silver and similar alerts, so a plate becomes searchable the moment it is known.
Local lookouts
Agency “be on the lookout” entries for a specific case. These should carry a reason, an owner and an expiry date.
Keeping hotlists clean
A hotlist is only as good as its upkeep. Stale or wrong entries cause bad stops and missed recoveries. Good practice, drawn from the Bureau of Justice Assistance’s policy template and agency policies, looks like this:
- An owner. A named person or unit is responsible for each list and its refresh schedule.
- A reason for every entry. Manual additions record who added them, why and under what authority.
- Expiry and removal. Entries expire or are removed when a vehicle is recovered or a case closes.
- A refresh schedule that matches how fast the source records change. Ask your vendor exactly how and how often imported lists update.
- Audit. Every list change and every hit is logged and reviewed on a schedule.
Verify every hit
A hit is a lead, not a reason to stop or arrest. Agency policies across the country say so directly. Reviewing public policies, we found a consistent pattern: the officer compares the plate image with the hotlist entry to confirm they match, then confirms the record is still active through dispatch or a live NCIC or state-system check before making contact. One city’s policy, for example, requires confirmation with the National and state Crime Information Centers and a second officer’s verification absent exigent circumstances. Another states that a hit is not sufficient probable cause for an arrest without additional verification.
For the rules behind those checks, see NCIC and license plate readers.
Frequently asked questions
What is a license plate reader hotlist?
A list of plates of interest that the system checks every read against. A match creates an alert for officers or dispatchers.
What goes on a hotlist?
Commonly stolen vehicles, wanted persons, missing or endangered persons and local lookouts. The exact sources depend on the agency’s policy and access to state and national records.
How often are hotlists updated?
It varies by source and by vendor. Ask exactly how and how often each list refreshes, and who is responsible when a record changes.
Can officers add plates to a hotlist by hand?
Many systems allow manual entries. Good policy requires a reason, an owner and an expiry date for each, and logs them for audit.
Does a hotlist hit justify a stop?
Agency policies generally say no: a hit must be verified visually and through a live record check before contact. A hit alone is not probable cause.