Utah Hive Politics logoUtah Hive Politicsfrom the publisher of The Weber County HiveThe people's publication. We investigate what's best for the public as a whole, not any party or special interest.
Surveillance · SV 100.04← All Surveillance articles · ← Hive library (every repo)
The Weber County Hive · Surveillance Investigation · Data Sheet

Utah's Required Records
and the GRAMA Gap

Utah law names exactly what an agency has to keep on file for every ALPR search. What Weber County actually released doesn't line up cell for cell with that list — and two of the biggest gaps can't be resolved from a summary. They require reading the production itself.

Posted Aug. 18, 2026 · Page look updated Nov. 2, 2026

What does Utah law require agencies to preserve, and what can the public actually inspect?

Three sources, one comparison
S.B. 250 (2023)
What Utah Code § 41-6a-2005 says a law enforcement agency must preserve about every search — the legal floor.
Weber County's GRAMA production
The 5,171,087-row dataset and companion documents the county actually released — what exists on paper today.
Flock's exported fields
What the vendor's own platform captures and exposes to the agency in the first place — the technical ceiling on what any record could ever show.
Interactive · Statute-to-Record Crosswalk

Where the requirement meets the record

Tap any row for the sourcing behind it. Crime type and incident number are now resolved — not by opening Weber County's raw production file directly, but through Flock's own documented platform export schema, which sets a hard ceiling on what any agency's production could contain regardless of how the GRAMA request was worded.

Yes / Documented Partial No / Not shown
Who Oversees This

The committees that could have closed this gap

Every audit-findings row above reads "not established" or "no historical forms produced" for a reason: a bill that would have fixed exactly that gap already passed both committees with jurisdiction over it — and still died.

House Transportation Committee
Approved HB 468 (Automatic License Plate Reader Amendments) 10–0–2 on Feb. 18, 2025. Unanimous.
House Floor
Passed HB 468 64–2 on Feb. 27, 2025. Overwhelming, bipartisan.
Senate Transportation Committee
Approved HB 468 6–0–2 on Mar. 4, 2025. Also unanimous.

HB 468 would have required every agency running these systems to submit standardized annual audit reports to the State Commission on Criminal and Juvenile Justice — a central, external body actually reading the audits, instead of an agency's own unlogged internal review. It would have set a hard 150-day statewide purge cap, in place of the patchwork retention rules currently in force. Both committees with substantive jurisdiction over ALPR legislation reviewed it and let it through without a single "no" vote.

The bill never got a final recorded floor vote in the Senate. At 11:59 p.m. on March 7, 2025 — one minute before the constitutional session deadline — the Senate struck the bill's enacting clause, killing it procedurally. No open debate, no recorded up-or-down vote on the substance. Who specifically moved that strike is not yet established in the record reviewed for this piece; that remains an open question worth a formal records request to the Senate Secretary's office.

This is not a one-off. A data-center transparency bill (S.B. 318, 2026) and an AI transparency bill (H.B. 286, 2026) were killed the same way, in the same window — sent to Senate Rules with days left in session, then struck at 11:59 p.m. on the final night, after committee approval. The lever that stops these bills isn't the committee that hears them on the merits. It's whatever happens after a bill leaves committee with support and reaches Senate Rules in the session's final days.

Primary Takeaway

Utah requires records connecting searches to crimes and incidents. The public production may not contain enough information to validate that those connections were ever made.

Crime type has no field to occupy in Flock's own platform, and incident number exists only as an unvalidated free-text field — both confirmed against Flock's documented export schema, not assumed from a summary.
Sources & methodology

This sheet does not conclude that Weber County or any agency failed to comply with state law. It documents what the statute requires, what Flock's own platform is technically capable of capturing, and what's been confirmed in Weber County's released records so far.

Part of a nine-part series on ALPR and privacy oversight in Weber County. ← Article 3: The Camera Said “Match.”  |  All articles  |  Article 5: The Privacy Report You Cannot Read →

Utah Hive Politicsfrom the publisher of The Weber County HiveIndependent · Accountability · Journalism

The Weber County Hive and Utah Hive Politics: the people's publication. We investigate what's best for the public as a whole, not for any party or special interest group. We report public records. You decide.

Send a tipTips we checkedSee a mistake? Tell us

We never name tipsters. When we correct a page, the fix and its date are shown on the page.

All Surveillance articles · Master Index (Hive library) · Read on Substack