Legislative tracking software

What legislative tracking software is for

A state legislature files on the order of a thousand bills in a session and passes several hundred of them in a few weeks. Some of those bills change what a city may charge, how a county runs an election, what a special district must report, or what a department has to do by a date. Legislative tracking software exists to answer three questions before the vote rather than after it: what was filed, which of it reaches us, and what are we going to do about it.

The first question is a data problem and is largely solved — most tools can list bills. The second and third are where organizations actually struggle, and where tools differ most.

What the work really involves

Ask anyone who has done a session by hand and the bottleneck is never the list. It is everything after it:

• Reading enough of each bill to know whether it matters — the part that does not scale with staff.
• Getting it in front of the right department, in a form they will actually read, while there is still time to respond.
• Collecting those responses into a position the organization can state publicly with one voice.
• Noticing when a bill you already cleared is amended into something different.
• Turning the ones that pass into work someone owns.

A tool that only does the first of these hands you a spreadsheet with more rows.

How to judge one tool against another

• Does it explain a bill, or only list it? A title and a status is not analysis.
• Can you check what it tells you? AI summaries without a citation back to the provision are unverifiable, which in a council packet means unusable.
• Does it route? Getting the right bill to the right department is the step that decides whether anything happens.
• Does it catch amendments? A bill rewritten in committee is a new bill wearing the old number.
• Does it record the decision? Tracking without a position is a reading exercise.
• What happens after it passes? Enacted bills become deadlines someone has to own.

How CivicRelay approaches it

CivicRelay reads every bill in the session rather than a filtered subset, because the filtering is the part you cannot check afterwards. Each bill gets a plain-English summary of what it does, who it affects and why it matters — with a verbatim citation to the provision behind every claim, and claims that cannot be matched to the bill text dropped rather than displayed.

From there it routes to departments, collects reviewer responses into unit and organization positions, diffs each new version of a bill and rates how significant the change is, and turns enacted bills into implementation items. The path from "a bill was filed" to "we did something about it" is one system rather than five.

The detail on grounding and limits is on how it works, and the security posture is on the security page.

Who it is built for

Cities and towns, counties, associations, special districts and state agencies. Coverage is Utah today, built one legislature at a time.