Reference
ALPR questions a city council will ask
Written for the chief who has to answer and the manager who has to sit next to him. Every question below is one that has actually been asked in a public meeting somewhere in the last two years.
Reviewed 26 July 2026
What determines the outcome
Watch enough of these meetings and a pattern shows up. The departments that keep their programs are not the ones with the best crime statistics or the smoothest presentation. They are the ones who walked in able to answer specific questions with specific documents.
The departments that lose are the ones who answered with assurances. We do not do that. Nobody else has access. It has never been misused. Those answers sound fine in the room and they age badly, because six weeks later somebody runs an audit.
The single best preparation is to find your own problems first. A council will forgive a department that says here is what we found and here is what we fixed. It will not forgive one that is informed of a problem by a resident.
The questions
Are you tracking everyone who drives through town?
The honest answer is that the system reads every plate that passes a camera, and most of those reads belong to people who have done nothing. Do not soften that. What follows it is the part that matters: how long you keep a read that never matched anything, who can search the stored data, and what record exists of each search. If your answers to those three are weak, this is the question that ends your program.
Who else can see our data?
Answer with a list, not a principle. Name the agencies, say what authority each one has, and say whether any of it was on by default. If you have not pulled that list recently, say that you are pulling it and will report back, and then actually do it. Guessing here has gone badly for other departments, because the audit eventually happens and the transcript does not go away.
Can federal agencies query our system?
Know the answer before you walk in. This has become the single most contentious question in the country, and in several cities the department believed the answer was no and the audit said otherwise. If you can switch federal access off yourself, say so and say whether it is on.
How many crimes has this actually solved?
Resist the temptation to reach for a vendor statistic. Bring your own numbers: alerts received, stops made, cases where the reader contributed to a clearance. If you cannot produce those, that is worth saying plainly, along with what you are doing to start measuring. A department that admits it does not measure and commits to measuring is in better shape than one caught quoting a number it cannot source.
What happens when it gets the plate wrong?
They will have read about a case. Do not minimize it. Explain your verification requirement, explain what an officer is required to check before acting, and explain how you would find out if it happened here. If you do not have a written verification requirement, that is the gap to close before this meeting, not after it.
How do we know officers are not misusing it?
Point to the access record. Who can search, whether the system requires a stated purpose or a case number, who reviews the log, and how often. If nobody reviews the log, say so and propose a schedule. An unreviewed audit log is a liability rather than a control, and councils understand that instantly.
Why should we renew this contract?
Because of what it does for your caseload, in your numbers, with the governance to back it up. Not because the vendor's material says it solves ten percent of crime. The renewal conversations that go well are the ones where the department shows up having already found and fixed its own problems.
Three things not to say
- The data is completely secure. You cannot promise this and nobody believes it. Describe your controls instead.
- Only authorized personnel have access. True by definition and therefore meaningless. Say who, how many, and who reviews the log.
- That happened somewhere else. The question underneath is whether it could happen here. Answer that one.
If you are in Texas
Expect a version of the sharing question, and know that the honest answer is uncomfortable. Under the DPS License Plate Reader User Agreement, sharing your contributed reads with other authorized criminal justice agencies is not a setting you control. It is a condition of access. Saying we decide who sees our data is not accurate, and a resident who has read the agreement will know that.
The better answer describes the framework. Who the data goes to, on what authority, what record exists, and what your agency does control, which is what you contribute and whether you remove it.
What to bring
- 1
The access list
Every agency that can see your data, current as of that week, with the authority for each.
- 2
The query log summary
How many searches, by whom, over the last twelve months, and how many carried a case reference.
- 3
Your own outcome numbers
Alerts, stops, clearances, and errors. Including the errors is what makes the rest credible.
- 4
The written policy
Current, dated, and matching whatever actually governs you.
- 5
Training records
What officers were taught about verification, and when they last had it.
If you cannot assemble those five in a week, that is worth knowing now rather than the night before. A program audit produces all five.