Think a designation is wrong or outdated?

What we are asking for

A challenge is strongest when it points at a document. The most useful submissions are:

• a contract, purchase order, or procurement record
• a policy, general order, or municipal code section
• a council agenda item, minutes entry, or staff report
• a public-records response — including a denial
• a data-sharing agreement or mutual-aid arrangement
• an annual surveillance or audit report
• a dated photograph of installed equipment, with a location

Reporting is useful too. A link to a named outlet is a perfectly good starting point, and we will trace it toward the underlying record the same way we do everything else.

Evidence that a community does not qualify is equally welcome

This is not a formality. A designation that survives only because nobody looked is worthless, and the failure mode we most want to avoid is a badge on a city that quietly kept a regional database login.

The question that most often decides a case is the least intuitive one: can this department query somebody else’s ALPR network? A city can prohibit itself from operating cameras and still search a county or vendor system covering the same roads. If you have evidence of that, it matters more than almost anything else you could send us.

What happens to a challenge

1. The submission creates a private review record.
2. We attempt to obtain the underlying document if we do not already hold it.
3. The affected criterion is re-assessed. If a designation is in doubt, status moves to suspended during review rather than silently persisting.
4. The municipality is given a factual summary and an opportunity to respond with evidence.
5. The outcome is published in the record’s change log — including when a challenge does not succeed.

Challenges are not posted publicly on submission. Evaluating evidence before publishing an accusation is the difference between a correction mechanism and a pile-on.