City of Lehi
From around 50 bills tracked in a session to more than 300 reviewed — in their words.
What changed
“Last year we tracked maybe 50 bills total. This year we reviewed and tracked over 300 bills for the city.”
That ratio is the whole problem in one sentence. A Utah general session runs well over a thousand bills — 1,016 in 2026, all of them tracked in CivicRelay. The bills that actually reach a city are a small fraction of that, but finding which fraction, by hand, costs more staff time than a city has. So in practice the search stops early, and the bills that matter are found late.
What the staff noticed
“The AI has been their favorite part, how easy CivicRelay makes it to understand the major impacts of each bill. The one comment I get every single week: this is so helpful.”
Worth noting what this says and does not say. The value reported here is not that the software found more bills — it is that more people inside the organization could understand the ones it found. A bill summary that a department head can read in a minute is what makes it reasonable to ask them for a position at all, and that is the step where legislative review usually stalls.
How it works in practice
CivicRelay reads every bill in the session, writes a plain-English summary with a verbatim citation back to the provision it came from, and routes the ones that matter to the right people. Reviewer responses roll up into a department position, department positions into an official city position, and bills that pass become implementation action items. When a bill is amended, the change is diffed against the previous version and rated for significance, so a rewrite doesn't slip past on a bill already cleared.
You can read more about how the analysis is grounded in the bill text — including what happens to claims the system cannot verify.
See it with your own legislature
The fastest way to judge whether this works for your organization is to look at your own session rather than a demo dataset. You can book a demo.