New Here? Start Simple
Utah's Truth in Taxation law requires a public hearing before a local government can raise property taxes above the certified rate. H.B. 236 changed what that entity has to show the public before that hearing.
The introduced bill and its first substitute required a genuine "necessity test": the entity had to adopt a tentative budget based solely on existing revenue — explicitly excluding the proposed increase — before presenting a second budget showing what the increase would fund. That two-budget comparison was a real, checkable way for the public to see whether the entity could function without the increase.
Between the first and second substitutes, that entire mechanism was removed. What replaced it: the entity simply adopts one budget based on the proposed increase from the start, with only a "property tax impact schedule" attached. The without-the-increase comparison is never produced.
27 cosponsors are listed on the enacted version, including Rep. Katy Hall and Rep. Jake Sawyer (neither is chief sponsor).
What Changed, Section by Section
| Introduced & 1st Substitute | |
|---|---|
| Required | A tentative budget based solely on existing revenue (no increase), then a second "alternative" budget showing what the increase would fund |
| What it proved | Whether the entity could function without the increase, before asking for it |
| 2nd Substitute (Enacted) | |
| Now required | One interim budget, based on the proposed increase from the outset, plus a one-way "property tax impact schedule" |
| What's missing | No without-the-increase budget is ever produced or compared |
The Timeline
- IntroducedBill requires the two-budget necessity test.
- 1st SubstituteTwo-budget test is retained.
- 2nd SubstituteThe two-budget mechanism is removed entirely, replaced with a single interim budget plus a property tax impact schedule.
- 3rd Substitute / EnrolledEssentially identical to S2 on this point — the substantive change was locked in at S2.
Graded against the standing rubric
This isn't a personal opinion of the bill. The grade below asks two questions, applied the same way to every bill in this series — not whether any one person likes the outcome: 1. Power — does it add or remove a check on power that the public, collectively, would otherwise have no say over? 2. Transparency — does it add or remove what the public can actually see about the process, regardless of who ends up holding the final decision? Design and outcome are graded separately because a bill can be structurally sound and still fail to become law, or pass in a form very different from how it started — collapsing the two into one score would hide which one actually happened.
The Bill's Public Summary
A reader relying only on the bill's own summary would not see the mechanism change.
What Actually Changed
A real, checkable constraint was quietly substituted out.
Graded by the Collective Rubric
This is The Weber County Hive's standing five-part rubric, applied the same way across every piece: Power — does it add or remove a check on power the public would otherwise have no say over? Transparency — can the public actually see the process? Financial Accountability — who actually pays, and is that disclosed plainly? Environmental Impact — is the effect on water, wetlands, and wildlife treated as a real constraint or a box to check? Community Impact — who bears the cost or holds a stake in this decision, and did they get real standing to be heard?
| Criterion | Grade | Assessment |
|---|---|---|
| Power | D | Removed the only mechanism that forced a taxing entity to show it could function without the proposed increase. |
| Transparency | D | The bill's own summary language didn't change even as the substantive mechanism did. |
| Financial Accountability | D | A one-way disclosure schedule replaced a genuine two-budget comparison. |
| Environmental Impact | N/A | Not applicable to a property-tax procedure bill. |
| Community Impact | C | A genuine small-town website disclosure carve-out elsewhere in the bill is a real accommodation, not a loophole. |
A real budget-comparison requirement was replaced with a one-way disclosure, while the bill's own summary language stayed the same.
How This Could Have Actually Protected the Public
- Restore the two-budget, without/with comparison as a required disclosure before a Truth in Taxation hearing
- Require a bill's "Highlighted Provisions" summary to be updated whenever a substantive mechanism like this changes between substitutes, not just when a section is added or removed
- Publish, for every entity that raises rates under this law, both what it said it needed and what it could have done without the increase
Part of a Larger Pattern
This case is one of eight in "Bills That Did the Opposite," a cross-bill tracker documenting Utah legislation where the public description stayed the same while the substance was quietly swapped out mid-process.
Sources
Show sources ▸Hide sources ▾
Sources
Show sources ▸Hide sources ▾- H.B. 236, official bill text (introduced, S1, S2, S3/enrolled) — le.utah.gov
- Direct comparison of all four bill versions
- Enacted cosponsor list, le.utah.gov Bill Status page