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.
bait-and-switch · BW 100.02← Hive library (every repo)
BAIT AND SWITCH · CASE 2026-BSW-01

Bills That Did the Opposite

Part 2 of 4: Four more bills, and the pattern

CASE 2026-BSW-01 · Posted Sept. 8, 2026 · Updated Oct. 18, 2026 · Page look updated Nov. 2, 2026

New to this? Read it in plain words About 900 words for all four parts, with simple charts.
Short version
  • Case 5: H.B. 236 (2026), "Truth in Taxation Amendments," required a no-increase budget first in its introduced and S01 versions. That test was removed at S02, and the summary wording stayed the same.
  • Case 6: H.B. 125 and H.B. 157 (2026), with the same House sponsor, carried the same DNR water-litigation statute. H.B. 125 passed without the $5 million; H.B. 157 died with it, 17 minutes later.
  • Case 7: In H.B. 273 (2026), "designed specifically for instructional use" became "demonstrated to have significant educational value."
  • Case 8: H.B. 17 (2026) removed a narrow PID board "retreat" exception and allowed meetings within the boundaries of the entity that created the PID.
  • The pattern section notes that most changes came at a substitute or amendment stage, and that the one case graded good for the public is the one where 152,000 signatures changed the outcome.
  • Updated Oct. 18, 2026: This series now has four parts and 19 cases. Part 3 adds nine more bills from 2025 and 2026. Part 4 explains the 471 bills closed out at 11:59 p.m. on March 6, 2026, and adds two cases from Congress.
Bait-and-switch pages (6) · tap to open
  1. Bait-and-switch docketEvery case, searchable
  2. In plain wordsThe short, simple version of all four parts
  3. Part 1: The rubric and the first four billsCases 1 to 4
  4. Part 2: Four more bills, and the patternCases 5 to 8
  5. Part 3: Nine more bills, 2025 and 2026Cases 9 to 17
  6. Part 4: 11:59 p.m., and Congress tooCases 18 and 19, and the bills that never got a final vote
  7. Transparency docketWhere this series first ran

The grades below use the rubric in Part 1: Power and Transparency, with design and outcome graded separately.

CASE 5 OF 8

The Necessity Test That Went Missing

H.B. 236 (2026)

Added Oct. 17, 2026 (record check): LegiScan lists 29 sponsors, with Rep. Karen Peterson first and Sen. Daniel McCay as the Senate sponsor, and text versions Introduced, S01, S02, S03 and Enrolled. The governor signed it March 23, 2026 (le.utah.gov).

WHAT IT LOOKED LIKE, AS INTRODUCED AND IN S01 "Truth in Taxation Amendments" — and, for its first two versions, a genuine one: a taxing entity that wanted to exceed the certified tax rate first had to adopt a tentative budget built entirely on its existing revenue — explicitly excluding the proposed increase — proving the entity could function without the extra money. Only after that, and only after public notice and a hearing, could it adopt a second, separate "alternative" budget built around the increase.
WHAT'S ACTUALLY IN THE LAW Between the S01 and S02 substitutes, that entire two-budget test was removed. What replaced it, and what remains in the enrolled law today, is a taxing entity simply adopting an interim budget already built around its proposed increase from the start — backed only by a one-way "property tax impact schedule" disclosure, never a forced side-by-side comparison of what the entity could do without the increase.

The introduced bill and S01 required what amounts to a necessity test: show the public, in a checkable budget document, that the entity can operate on existing revenue before asking to take more. That test is gone from the version Utah taxing entities actually operate under. S02 and the enrolled S03 are essentially identical to each other on this point — the substantive change happened once, at S02, and never moved again.

What makes this a bait-and-switch rather than a simple weakening is that the bill's own "Highlighted Provisions" summary reads almost identically across all four versions — it still says "interim budget," it still says "property tax impact schedule," in the introduced bill, S01, S02, and the enrolled text alike. The same two phrases describe two different mechanisms depending on which version you're reading, and nothing in the summary language itself flags that the underlying requirement changed.

The one-year enforcement grace period documented in earlier drafts of this piece is real and still worth noting: for the law's first year, the State Tax Commission cannot deny a taxing entity's rate increase even if the entity skips the impact-schedule disclosure entirely. But it's a secondary finding next to the removed necessity test — a temporary gap in enforcing a disclosure requirement is a smaller thing than removing the underlying requirement to prove the increase is needed at all.

In fairness, one piece of the bill cuts the other way: a genuine accessibility accommodation lets small towns without a public website post the required notice physically at town hall instead. That provision isn't part of the bait-and-switch — it's a real fix for towns the disclosure requirement would otherwise be hardest to meet.

C−
Design (introduced / S01): Good for the public — a genuine necessity test forcing a public, checkable without-the-increase comparison before any tax hike could proceed.
Design (S02 onward, the version that passed): Bad for the public — the necessity test is gone, replaced by one-way disclosure with no forced comparison, plus a one-year window where even that disclosure isn't enforced.
Outcome: Matches the weaker S02/S03 design — that's the version signed into law.
Same words, different bill — what changed between S01 and S02

Introduced / S01: Adopt a tentative budget based solely on existing revenue (increase excluded). Hold public notice and a hearing. Only then adopt a second, alternative budget reflecting the proposed increase.

S02 / enrolled (S03): Adopt an interim budget based on the proposed tax rate increase from the outset. Disclose a property tax impact schedule. No without-the-increase budget is ever required.

Both versions use the phrases "interim budget" and "property tax impact schedule" in their own Highlighted Provisions summaries — the language describing the bill didn't change even though the mechanism it describes did.

How they voted — H.B. 236

Full floor roll call not yet pulled for this bill. Flagged for the next research pass.

Added Oct. 17, 2026 (record check): LegiScan now shows the tallies: House committee 10–0–1 (Jan. 29, 2026); House 3rd reading 72–0–3 (Feb. 10); Senate committee 5–0–2 (Feb. 17); Senate 2nd and 3rd readings 28–0–1 (March 6); House concurrence 67–0–8 (March 6). By-name lists were not pulled.

At a glance: our Sept. 17, 2026 summary of Case 5

Why this is here: This short version first ran on the bait-and-switch page on Sept. 17, 2026. It is kept so nothing is lost, and it adds vote tallies and links to each Bill-Tracker case file.

CASE 5 GRADE D

H.B. 236 (2026) — "Truth in Taxation Amendments"

The introduced bill and its first substitute required a genuine "necessity test": a taxing entity proposing to exceed the certified tax rate first had to adopt a tentative budget based solely on existing revenue — proving it could function without the increase — before presenting a second budget showing what the increase would fund. That two-budget, without/with comparison was a real, checkable constraint. Between the first and second substitutes, the entire mechanism was removed and replaced with a one-way disclosure: the entity simply adopts a budget based on the proposed increase from the start, with only a "property tax impact schedule" attached — no forced without-the-increase comparison is ever produced.

Verdict

✓The bill's own "Highlighted Provisions" summary reads almost identically across all four versions — still referencing "interim budget" and "property tax impact schedule" — while the actual constraining mechanism was substituted out between S1 and S2.
?HD50's small-town website disclosure carve-out, added elsewhere in the same bill, is a genuine accommodation rather than a loophole — noted for fairness, not counted against the bill's grade.
CASE 6 OF 8

Same Sponsor, Two Bills, One Survived Midnight

H.B. 125 (2026)H.B. 157 (2026)

Added Oct. 17, 2026 (record check): le.utah.gov lists H.B. 125's title as "Department of Natural Resources Related Modifications Amendments." The introduced text was titled "Aquatic Invasive Species Amendments," with Rex P. Shipp as sponsor. LegiScan shows the governor signed H.B. 125 March 25, 2026. LegiScan lists H.B. 157 ("Department of Natural Resources Amendments," Rep. Rex Shipp and Sen. Keven Stratton) as failed March 6, 2026, with its enacting clause struck that day; LegiScan's action list does not show times. The tallies below match LegiScan.

WHAT IT LOOKED LIKE Two separate, unrelated-looking bills: H.B. 125, introduced as "Aquatic Invasive Species Amendments" (boating and invasive-mussel rules), and H.B. 157, "Department of Natural Resources Amendments" (general DNR housekeeping).
WHAT IT ACTUALLY DID Both bills, independently, came to carry an identical new statute (§ 73-1-22) authorizing DNR to fund water litigation, and at different points each carried an identical $5 million General Fund appropriation to pay for it. On the last night of the session, their fates split within the same hour — one survived without the money, the other died still holding it.

H.B. 157 carried the litigation statute and the $5 million appropriation from its House substitute filed February 11, 2026, unchanged through every version on record. It passed the House 57–1–17 on February 19 and the Senate's 2nd reading 22–0–7 on March 2 — but never received a final Senate vote. It sat in Senate Rules from March 4 onward. A fourth substitute removing the litigation statute entirely was drafted by Sen. Stratton — H.B. 157's own floor sponsor — but the bill's own status log shows no vote ever adopting it; it appears to have been prepared and never brought to a vote before the bill died.

Meanwhile, H.B. 125 — introduced as an unrelated boating-and-invasive-species bill — picked up the identical litigation statute in a Senate committee substitute on March 3, with no money attached. On the night of March 6, the two bills' final hours ran in parallel:

The same night, minute by minute

9:04 PM — The Senate substitutes H.B. 125 from #1 to #2, adding the identical $5 million appropriation for DNR water litigation.

9:41 PM — The House refuses to concur with the Senate's amendments.

10:25–10:34 PM — A conference committee is appointed and produces H.B. 125's third substitute, removing the $5 million again.

11:32–11:42 PM — Both chambers adopt the conference report and pass H.B. 125's final version — the litigation statute enacted, no money attached.

11:59 PM — Seventeen minutes after H.B. 125 finished passing, the Senate strikes H.B. 157's enacting clause, killing it outright. Its own $5 million and litigation statute — never touched by anyone that night — die with it.

March 6, 2026: two bills, one night

Times from this case.

flowchart TD A["9:04 PM
Senate adds $5 million
to H.B. 125"] --> B["9:41 PM
House refuses
to concur"] B --> C["10:25 to 10:34 PM
Conference committee
removes the $5 million"] C --> D["11:32 to 11:42 PM
H.B. 125 passes
statute, no money"] D --> E["11:59 PM
Senate strikes H.B. 157
enacting clause"]

The statute itself — DNR's authority to fund water litigation — became law through H.B. 125. Where the money to use that authority might come from is not specified anywhere in the version that passed; the only appropriation for it died in a different bill, by the same sponsor, seventeen minutes later.

Added Oct. 17, 2026 (record check): The Salt Lake Tribune reported Feb. 19, 2026 that H.B. 157 would give DNR $5 million for water legal fights and quoted Rep. Shipp: "This is mainly to litigate our Colorado River issues." Source: The Salt Lake Tribune, Feb. 19, 2026.

D
Design: Bad for the public — the same substantive change moved through two parallel bills from the same sponsor, with the public left to track which vehicle actually mattered; the one that passed enacted new spending authority with no funding source, title, or public explanation for why the money disappeared in the final hour of session.
Outcome: Same as design.
How they voted — H.B. 157 (killed) and H.B. 125 (passed)
H.B. 157 House 3rd reading: 57–1–17H.B. 157 Senate 2nd reading: 22–0–7

H.B. 157 never received a final Senate 3rd-reading vote — its enacting clause was struck at 11:59 PM on March 6, the same procedural mechanism (a same-night enacting-clause strike) used against several other 2026 bills tracked separately in this project.

Added Oct. 18, 2026 (record check): Striking the enacting clause at 11:59 p.m. on the last night is how the Legislature closes out every bill that has not passed. On March 6, 2026, it was done to 471 bills, including 158 that had passed one chamber. What stands out about H.B. 157 is how far it got, not how it ended. Part 4 explains this.

H.B. 157 HOUSE 3RD READING, LONE NO

Rep. Lee Hansen — the same legislator who cast the only No vote on H.B. 125's final passage below. Hansen is the sole member of either chamber to vote against either bill carrying this litigation-funding language.

H.B. 157 SENATE 2ND READING YES (22)

J. Stuart Adams, Balderree, Blouin, Brammer, Escamilla, Fillmore, Grover, Harper, Hinkins, Ipson, Johnson, Kwan, McKell, Musselman, D.R. Owens, Pitcher, Plumb, Stratton, Vickers, Weiler, C. Wilson, Winterton

H.B. 157 House 3rd reading absent/not voting: Auxier, Brooks, Chevrier, Cutler, Fiefia, Hawkins, MacPherson, Peck, T. Peterson, V. Peterson, Roberts, Schultz, Shallenberger, Snider, Thompson, Watkins, Welton. Senate 2nd reading absent/not voting: Buss, Cullimore, McCay, Millner, Riebe, Sandall, Stevenson. This 2nd-reading vote is the furthest H.B. 157 ever got — a near-unanimous passage with the $5 million litigation appropriation still fully intact, four days before the bill died without ever reaching a Senate 3rd reading.

H.B. 125 Senate Conference Committee final passage: 29–0–0H.B. 125 House Conference Committee final passage: 66–1–8

Rep. Lee Hansen cast the only No vote in either chamber's final passage of H.B. 125. Every Senator present voted yes.

At a glance: our Sept. 17, 2026 summary of Case 6

Why this is here: This short version first ran on the bait-and-switch page on Sept. 17, 2026. It is kept so nothing is lost, and it adds vote tallies and links to each Bill-Tracker case file.

Corrected Oct. 18, 2026: This short summary said the litigation language moved from H.B. 157 to H.B. 125 after the Senate stripped it from H.B. 157. The bills' own status records on le.utah.gov show something different, and the full case above follows them. H.B. 125 picked up the same statute in a March 3 Senate committee substitute. On March 6, a Senate substitute added $5 million at 9:04 p.m., and a conference committee substitute removed it at 10:34 p.m. H.B. 157 kept its own $5 million and died at 11:59 p.m. The summary below is kept as first published.

CASE 6 GRADE C

H.B. 157 → H.B. 125 (2026) — Six Hours, Two Bills, $5 Million

A new DNR water-litigation-funding authority (§73-1-22) and a $5,000,000 appropriation to fund it first appeared together in H.B. 157's third substitute. The Senate then removed both from H.B. 157 in its final substitute — and the Senate struck H.B. 157's enacting clause outright that same day, March 6, killing the bill. Hours later that same day, H.B. 125 — until then a bill about aquatic invasive species with no water-rights content at all — was substituted to reinsert the identical litigation-authority language word-for-word. Six hours after that, a third H.B. 125 substitute kept the litigation authority but dropped the $5 million appropriation again.

H.B. 157 (S03): House 57-1-17, Senate 2nd reading 22-0-7, before being killed the same day it was due for further action

Verdict

✓The litigation-authority language is now law (§73-1-22); no funding source for it is specified anywhere in the enacted text, and the public record does not show who requested the funding's removal from either bill.
?Whether DNR has used this authority since its effective date, and from what account, is unconfirmed.
CASE 7 OF 8

"Designed For" Becomes "Demonstrated To Have Value"

H.B. 273 (2026)

Added Oct. 17, 2026 (record check): LegiScan lists 30 sponsors, with Rep. Ariel Defay first and Sen. Chris Wilson as the only senator, and shows the governor signed it March 18, 2026 (le.utah.gov).

WHAT IT LOOKED LIKE A classroom-technology bill requiring instructional tools used in Utah schools to be "designed specifically for instructional use."
WHAT IT ACTUALLY DID Weakened that standard, via a floor amendment from the bill's own Senate sponsor, to "demonstrated to have significant educational value" — a standard broad enough for general-purpose consumer tools, including Google's Gemini for Education, to qualify.

The original standard would have excluded a tool built for the general public and merely adapted for schools. The revised standard doesn't. The change was proposed by Sen. Chris H. Wilson — the bill's own floor sponsor — the night before the Senate's final vote. The connection to Google specifically isn't speculation: the Utah Association of Public Charter Schools raised the exact concern in its own legislative update, warning that requiring software be "specifically designed for education" would be a problem, "noting that popular tools like Google and Microsoft" wouldn't qualify under the stricter language. Weeks later, Utah's Board of Education rolled out Google Gemini for Education statewide, starting the 2026–2027 school year. News reports describe it as an optional state contract and do not tie it to this bill.

Added Oct. 17, 2026 (record check): Google announced the partnership with the Utah State Board of Education on June 4, 2026, starting in the 2026–2027 school year (Google, June 4, 2026). KSL reported Oct. 7, 2026 that the state left it to districts to decide how to use Gemini, so access varies: Canyons School District turned it on for teachers, staff and high school students, while Provo City School District told parents it is not available on student Chromebooks while it writes an AI policy (KSL, Oct. 7, 2026).

Why this standard matters in practice — a separate study, same underlying problem

A joint BYU/Internet Safety Labs investigation of 100 Utah EdTech apps (the study behind a related bill, H.B. 55) found that 52% of apps with a signed state privacy agreement collected at least one data element they weren't contractually permitted to collect, and 61% shared data with third parties, 36% specifically with advertisers. Three apps shared data with 32, 33, and 54 advertisers respectively. The study predates Gemini's 2026 rollout in Utah schools and doesn't cover Gemini itself — it's cited here because it's the most direct evidence available of what "demonstrated to have significant educational value" doesn't guarantee: a tool can clear that bar and still handle student data in ways a parent wouldn't expect.

Added Oct. 17, 2026 (record check): H.B. 55 (2026), "Privacy Compliance for Education Technology Vendors," lists Rep. Tiara Auxier and Sen. John Johnson; the governor signed it Feb. 27, 2026 (LegiScan). GovTech reported Sept. 4, 2026 that 44 of the 85 tested apps with standard data privacy agreements (52%) collected at least one data type their agreement did not permit (GovTech).

Worth stating plainly: H.B. 273 is otherwise a genuine guardrails bill — it sets new AI-use standards, restricts screen time in early grades, and requires parental notification for classroom AI tools. This case is about one narrowed standard inside it, not a claim that the bill as a whole favors industry.

C
Design: Neutral leaning bad — the standard's purpose (limiting classroom tools to education-built products) was measurably loosened by its own sponsor, without a public explanation on the floor of why.
Outcome: Same as design.
How they voted — H.B. 273
House 3rd reading: 68–1–6Senate: 17–9–3House concurrence: 62–6–7

Aggregate only, by-name not yet pulled. Worth noting the Senate margin (17–9) is far closer than either House vote — the floor amendment that weakened the tech standard passed the night before that closer Senate vote.

Added Oct. 17, 2026 (record check): LegiScan lists a Senate committee vote of 3–2–2 on Feb. 27, 2026. Its action list shows the Senate floor amendment and the 17–9–3 Senate vote both on March 4, 2026; the list does not show times. The House tallies above match LegiScan.

At a glance: our Sept. 17, 2026 summary of Case 7

Why this is here: This short version first ran on the bait-and-switch page on Sept. 17, 2026. It is kept so nothing is lost, and it adds vote tallies and links to each Bill-Tracker case file.

CASE 7 GRADE D

H.B. 273 (2026), "Classroom Technology Amendments" — Instructional Technology Standard

Amended the standard for classroom instructional technology via Senate Floor Amendment 5 — proposed by the bill's own Senate sponsor, Sen. Wilson, the night before final Senate passage — from software "designed specifically for instructional use" to software merely "demonstrated to have significant educational value." The change broadens the standard to let general-purpose tools qualify, the opposite of the bill's stated aim of setting a higher bar for what schools can deploy. Google is named directly in legislative testimony (UAPCS) alongside the confirmed statewide rollout of Gemini for Education the following school year.

House Education Cmte 10-0-5 · House 3rd reading 68-1-6 · Senate Education Cmte 3-2-2 · Senate 2nd/3rd reading 17-9-3 · House concurred 62-6-7 · Signed Mar 18, 2026

Verdict

✓The floor amendment came from the bill's own sponsor, not an opposing member — the loosening was not contested on the record. The vote also got noticeably more contested at each later stage (68-1-6 in the House, then 17-9-3 in the Senate, then 62-6-7 on concurrence) as the substitute language moved through.
?The same Senate amendment also struck the bill's parent-transparency provisions (a digital-tools list, on-request device/browsing-history access, a sensitive-material opt-in alert) — but the final enrolled text still contains all three, intact. Whether they were restored by a later, unlogged floor action isn't resolved.
?The bill otherwise contains genuine guardrails (AI standards, screen-time limits, parental notification) — this case is about one narrowed standard inside it, not a claim that the whole bill favors industry.
CASE 8 OF 8

A Narrow Exception, Swapped for a Wider One

H.B. 17 (2026)

Added Oct. 17, 2026 (record check): The enrolled H.B. 17 lists Doug Welton (House) and Brady Brammer (Senate) and says "This bill takes effect on May 6, 2026." LegiScan and le.utah.gov list the governor's signature on March 13, 2026. The enrolled text keeps the main rule that "a board shall hold regular and special meetings at a location within the boundaries of the public infrastructure district," then lists three exceptions: no location in the district can fit the board and the public (and the chosen spot is near the district); emergency circumstances; or "the location the board selects is within the boundaries of the creating entity."

WHAT IT LOOKED LIKE, IN COMMITTEE A bill closing a specific loophole that let Public Infrastructure District boards meet away from the public: a "retreat" exception allowing PID boards to gather once a year, for planning and education only, with no votes or final action taken. House committee voted to strike that exception outright.
WHAT'S ACTUALLY IN THE LAW The narrow retreat exception is genuinely gone — but it wasn't simply removed. In its place, the version Gov. Cox signed into law on March 13, 2026 (it took effect May 6, 2026) lets a PID board hold meetings anywhere "within the boundaries of the entity that created the PID" — with no limit on how often, no restriction to planning or education, and no ban on taking final action or votes at those meetings.

The swap matters because of scale. A PID's own boundaries are typically small — the development it was created to finance. The boundaries of the city or county that created the PID are usually far larger. For any PID whose creating entity is an entire county, the new language effectively removes the core idea that PID board meetings have to happen somewhere near the district itself: the board can now meet, and take binding votes, anywhere within a jurisdiction that may bear no resemblance to the PID's own footprint.

This isn't a case of language quietly reinstated after committee struck it — the committee's specific fix stayed struck. It's a case where removing a narrow, well-bounded exception created room for a broader, functionally looser one to take its place, and neither chamber's floor vote shows anyone flagging the trade.

D
Design: Bad for the public — a specific, narrow committee fix was replaced by a broader standing allowance with no frequency limit, no purpose restriction, and no bar on final votes, passed with no recorded floor debate.
Outcome: Same as design.
How they voted — H.B. 17
Senate: 26–0–3

Senate final vote only — aggregate, by-name not yet pulled. House committee vote (the one that struck the narrow retreat exception) not yet located as a numbered tally. Passed unanimously at every recorded stage — no member's floor remarks flagged the boundary-scope trade documented above.

Added Oct. 17, 2026 (record check): LegiScan shows the tallies not listed above: House committee 11–0–1 (Jan. 21, 2026, including two amendment votes); House 3rd reading 70–0–5 (Jan. 23); Senate committee 5–0–3 (Jan. 30); Senate 2nd reading 24–0–5 (Feb. 5); Senate 3rd reading 26–0–3 (Feb. 6).

At a glance: our Sept. 17, 2026 summary of Case 8

Why this is here: This short version first ran on the bait-and-switch page on Sept. 17, 2026. It is kept so nothing is lost, and it adds vote tallies and links to each Bill-Tracker case file.

CASE 8 GRADE F Reframed 9/11/26

H.B. 17 (2026) — "Public Infrastructure District Meeting Amendments"

A narrow exception letting a PID board hold an annual retreat outside its own boundaries — limited to once a year, planning and education only, no votes or final action — was removed. What replaced it is not a fix; it's a broader loophole in better packaging: PID meetings may now be held anywhere "within the boundaries of the entity that created the PID," with no frequency limit, no purpose restriction, and no ban on votes or final action. Because a PID's creating entity (a city or county) is typically far larger than the PID itself, this functionally hollows out the core requirement that PID meetings happen within the PID's own boundaries — for any PID created by a whole county, in particular.

Passed unanimously at every recorded stage — no member flagged this substitution on the record.

Verdict

✓Confirmed directly against enrolled text: the narrow retreat exception is genuinely gone, not merely relabeled — but its replacement is broader, not narrower, than what it replaced.

The pattern

Read one at a time, these are eight unrelated stories about eight unrelated topics — taxes, water, lakes, air, schools, meeting rooms. Read together, a shape repeats:

The bill's title describes the beginning, not the end. "Water Rights Amendments" doesn't say it narrows who can object to a water application. "Truth in Taxation Amendments" doesn't say its own necessity test would be removed between the first and second substitute, or that the disclosure requirement left in its place would go unenforced for a year. Nothing in "Aquatic Invasive Species Amendments" suggests it would carry a DNR litigation-funding statute by the time it passed.

The reversal usually happens at a substitute stage, not the introduced bill. H.B. 236's necessity test, H.B. 273's weakened tech standard, H.B. 125's added-then-removed funding, H.B. 17's swapped meeting exception — none of these were in the bill as first written. They arrived, or vanished, in a substitute, an amendment, or a same-day swap between two different bill numbers, at points in the process that usually draw less public attention. H.B. 236 is the starkest version of this: the bill's own summary language never changed at all — "interim budget" and "property tax impact schedule" describe two different mechanisms in two different versions, word for word.

The same names recur inside this list alone. Sen. Scott Sandall moved the substitute on H.B. 491 (Case 2) and separately sponsored the repeal in H.B. 373 (Case 4) — two different reversals, three years apart, same senator. Sen. Keven Stratton is the Senate sponsor on both H.B. 60 (Case 3) and H.B. 157 (Case 6) — two different water-authority bills in the same 2026 session. Rep. Rex Shipp was the primary sponsor of both H.B. 125 and H.B. 157 (Case 6) himself — two parallel vehicles for the identical new authority, one of which happened to survive. None of these overlaps required outside research to find; every name is already on the bills covered here.

Almost none of it required a majority to reverse course. H.B. 491 passed 73–0 and 26–0. H.B. 17 passed with no recorded opposition at its floor votes. H.B. 60 drew 17 no votes in the House and 7 in the Senate, and H.B. 273 passed the Senate 17–9. The one case where a real fight happened in public — S.B. 2001's food tax — is also the one case where the public won.

From our Sept. 17, 2026 summary: the pattern and the system-level grade

Why this is here: The Sept. 17 version of this page covered ten cases (Cases 9 and 10 are now in Part 3). Its pattern notes and D+ system grade are kept here as first published.

Read individually, each of these looks like an isolated committee-substitute decision — the ordinary mechanics of a bill moving through 45 days. Read together, a shape emerges: the bill's "Highlighted Provisions" summary and public framing barely change from introduction to passage, while the actual operative language — the part that would have created a real check, cost, or disclosure requirement — gets substituted out, usually with no debate on the record at the moment it happens.

Corrected Oct. 18, 2026: In the note below, Sen. Keven Stratton was the Senate sponsor of H.B. 157. H.B. 125's Senate sponsor was Sen. David Hinkins. The phrase "vanished and reappeared twice in six hours" describes the earlier version of Case 6; see the correction in Case 6. Kept as first published.

Two sponsors appear on opposite sides of this pattern in the same 2026 session. Sen. Keven Stratton was Senate sponsor on both H.B. 60 (Case 3, narrowing who can protest a water application) and H.B. 157/H.B. 125 (Case 6, the water-litigation-funding language that vanished and reappeared twice in six hours) — two separate water-authority bills, not previously connected as a pair. Separately, Sen. Scott Sandall shows the identical House-to-Senate role on both H.B. 491 (2023) and H.B. 373 (2024): a co-sponsor on the bill that created a body, then the sponsor who personally carried the bill that repealed it.

System-Level Grade — Power / Transparency / Financial Accountability

D+

Graded against the Hive's standing five-criteria rubric (Power, Transparency, Financial Accountability, Environmental Impact, Community Impact). None of the ten cases below score well on Power or Transparency — in every one, a real constraint on discretion, spending, or standing was removed with no on-the-record explanation of why. The one partial exception is Case 8 (H.B. 17), where the replacement language is broader than what it replaced but isn't a total removal — hence a "+" rather than a flat D.

CriterionWhat the pattern shows
PowerIn 9 of 10 cases, a constraint the public would otherwise rely on (a hearing requirement, a spending cap, a disclosure mandate, standing to protest, an oversight seat) was removed between substitutes.
TransparencyThe removal itself is rarely explained on the record. Committee minutes typically show only the motion and the vote, not the reasoning — in several cases the change happens by voice vote on the floor, minutes before final passage.
Financial accountabilityTwo cases (H.B. 236, H.B. 125/157) directly concern how spending is disclosed or funded; both had the stronger version of that disclosure or funding mechanism removed.
Environmental impactThree cases (H.B. 491, H.B. 60, H.B. 392/373) directly touch water rights or air-quality oversight; each narrowed public or independent standing over an environmental decision.
Community impactNot separately graded case-by-case here; several cases (H.B. 491, H.B. 60) connect to the Great Salt Lake water-rights thread where community standing to protest is the resource being narrowed.

What this means for the public

Graded across all eight cases together, using the same two questions applied to each one individually.

Four of these eight cases involve taxpayer money directly, not just process or procedure. S.B. 2001 raised the state sales tax on every grocery and gas purchase in Utah — ongoing revenue collected from taxpayers statewide, not a one-time fee. H.B. 491 appropriated $12.5 million in General Fund taxpayer money to the Great Salt Lake Account. H.B. 125 created a new DNR litigation-spending authority the same day its $5 million funding source disappeared — leaving the public record showing an authority to spend without a disclosed source of what it spends. And H.B. 236 governs how much added property tax revenue every city and county in Utah can collect from residents without the checkable, without-the-increase budget comparison its own earlier drafts required.
D+
Power: Bad for the public in seven of eight cases — a check the public would otherwise have (a protest ground, an air-quality board seat, a necessity test before a tax hike, a boundary-bound meeting requirement) was removed, not added. Good in exactly one (S.B. 2001/H.B. 185, where the public's own referendum power is what forced the reversal).
Transparency: Bad for the public in six of eight cases — new records exemptions, a swapped meeting-location exception, a disclosure requirement's own one-year enforcement gap, and — in H.B. 125's case specifically — a taxpayer-funded spending authority with no disclosed funding source at all.

The one bright spot in this set is instructive rather than comforting: the only case that ends well for the public is the one where the public itself — 152,000 signatures — is what changed the outcome, not any legislative or procedural safeguard built into the process.

What would have earned a passing grade

As with every case in this project, none of these fixes require undoing the underlying bill's stated purpose — a commissioner for the lake, a modernized signature process, a classroom-technology standard, a faster path to a special session. Each is a narrow, identifiable design choice at the exact point already documented in each case above.

What actually happenedWhat would have kept the same goal, without the opacity
S.B. 2001 raised the grocery tax without the two-thirds majority that would have made it referendum-proof Pass major tax-structure changes with enough margin to survive a public vote, or hold the food-tax change as its own separate bill the public can weigh in on directly
H.B. 491 walled off water rights from its own new Commissioner and cut $40M to $10M with no explanation recorded State the reason for the funding change in the record; if water rights are meant to stay with the state engineer, say so in the bill's own title rather than leaving it to be found in the text
H.B. 60 narrowed water-application protest grounds down to only quantity/quality/availability Keep the broader public-welfare standard, or add a sunset/review clause so the narrower standard has to be re-justified rather than becoming permanent by default
H.B. 373 replaced a board with reserved academic/NGO seats with an all-industry-appointed working group Keep at least one seat reserved for someone with no financial stake in the outcome, alongside the industry expertise
H.B. 236 removed the necessity test requiring a without-the-increase budget between its S01 and S02 substitutes, replacing it with one-way disclosure and a year-long enforcement gap Keep the two-budget comparison, or if it's dropped, say so plainly in the bill's own summary rather than leaving "interim budget" to describe two different requirements across versions
H.B. 125 gained a new DNR litigation-funding statute the same day its $5M funding source disappeared Don't create spending authority and remove its funding source in the same substitute — if the money isn't there yet, say that in the bill rather than leaving the gap unaddressed
H.B. 273's classroom-tech standard was weakened by its own sponsor the night before final passage, with no floor explanation Route standard-weakening amendments back through committee for a public hearing, rather than a same-week floor amendment with no debate on the record
H.B. 17 traded a narrow, well-bounded meeting exception for a broader one tied to a PID's much-larger creating entity, with no floor discussion of the trade If a narrow exception is being removed, replace it with something equally narrow — not a standing allowance with no frequency, purpose, or final-action limits

Who benefits

Same three-tier standard used across this project: named means a specific company or person with a documented, dated gain; industry means a sector benefits generally with no single named winner; diffuse means the cost or benefit is spread too broadly for a concentrated winner to be shown by the record.

In plain terms: "diffuse" means the taxpayers of Utah. When a cost or benefit is spread out across every taxpayer instead of landing on one traceable company or person, that's diffuse. Nobody in particular gained or paid — everybody did, a little bit each.

Where a case involves direct taxpayer money — tax revenue, an appropriation, a spending authority — that's noted specifically below, since "who benefits" from public money is a sharper question than "who benefits" from a procedural change.

CaseTierBasis
S.B. 2001 / H.B. 185 (food tax)DIFFUSEDirect taxpayer impact: raised ongoing state sales tax revenue on every grocery and gas purchase in Utah. Cost fell on consumers broadly; no single named corporate winner documented.
H.B. 491 (GSL Commissioner)NAMEDDirect taxpayer impact: $12.5 million in General Fund taxpayer money appropriated to the account. Keller Cattle Corp filed two applications 55 days after the bill's effective date, 556.7 acre-feet combined, approved together July 18, 2024.
H.B. 60 (water rights)NAMEDBar H Ranch's own application is the direct, dated example of the narrower standard in use.
H.B. 392 / H.B. 373 (air quality board)INDUSTRYPollution-control rulemaking moved to the Oil, Gas and Mining Board; no single named company documented.
H.B. 236 (Truth in Taxation)DIFFUSEDirect taxpayer impact: under the introduced/S01 design, the necessity test constrained every taxing entity equally — no beneficiary. Under the enacted S02/S03 design, taxing entities generally benefit from the weaker, disclosure-only requirement; the cost falls on residents and businesses paying the resulting tax increases broadly, not a single named party.
H.B. 125 / H.B. 157 (water litigation)DIFFUSEDirect taxpayer impact: DNR gains a new taxpayer-funded litigation-spending authority through H.B. 125, with no funding source left in the version that passed. The identical statute and its $5 million appropriation survived, untouched, in a duplicate bill (H.B. 157) that died the same night; that bill's own floor sponsor drafted a fourth substitute removing the authority entirely, but it was never brought to a vote. No specific pending litigation or named private beneficiary has been documented for either bill; the cost of any future litigation this authority funds would fall on general taxpayers, not a named party.
H.B. 273 (classroom tech)NAMED / INDUSTRYGoogle specifically identified by the Utah Association of Public Charter Schools in its own legislative testimony as a tool the original standard would have excluded; Google Gemini for Education launched statewide in Utah schools the following school year under the weakened standard.
H.B. 17 (PID meetings)INDUSTRYPID boards generally — and, by extension, the developers whose districts they govern — benefit from a meeting-location rule tied to a much larger creating entity's boundaries rather than the PID's own; no single named PID or developer documented as the direct beneficiary yet.

All eight cases now have a tier assigned. Five are named or industry beneficiaries and three are diffuse. Four of the eight cases involve taxpayer money directly — and in all four, the taxpayers footing the bill are in the "diffuse" tier, not the concentrated winner. The named and industry cases are also, without exception, the cases graded worst on the Power question above — the pattern of who loses a check on power and who gains a concentrated benefit is the same pattern, not two separate ones.

From our Sept. 17, 2026 summary: who benefits, all ten cases

Corrected Oct. 18, 2026: The H.B. 491 row says 56 days; the applications were filed 55 days after the bill took effect (see Case 2). Kept as first published.

CaseTier
H.B. 491 / water application approvalsNamed — the bill's own sponsor's company, Keller Cattle Corp, 56 days after effective date
H.B. 60 / narrowed protest standingNamed-adjacent — agricultural water users; opposed by Utah Rivers Council and four physicians on public-health grounds
H.B. 392 repeal (H.B. 373)Industry — shifts pollution rulemaking to the industry-aligned Board of Oil, Gas and Mining
H.B. 236 / Truth in TaxationTaxing entities generally — removes the forced without-the-increase budget comparison that gave the public a checkable baseline
H.B. 125 / H.B. 157Unclear — the record doesn't show who requested the funding removal either time
H.B. 273 / instructional technologyNamed — general-purpose AI vendors, Google specifically identified in legislative testimony
H.B. 17 / PID meeting locationPID boards whose creating entity is a large county — meeting-location requirement effectively hollowed out
S.B. 2001 repeal (H.B. 185)The legislature itself — mooted a qualified voter referendum before signature verification finished
H.B. 492 / prison loan & board mergerPoint of the Mountain State Land Authority (the relabeled loan); unclear who benefits from the second board — record doesn't say
QUESTIONS WORTH ASKING
  1. Why did the Legislature repeal its own 2019 tax law rather than let the referendum it had already qualified for reach the ballot?
  2. Who requested the water-rights carve-out and the new records exemption in H.B. 491, and why in the same bill that created the Lake Commissioner?
  3. Why leave the state's core environmental statutes on a path to automatic expiration in 2029, in a bill that extended thirty other program deadlines?
  4. Who proposed removing H.B. 236's necessity test between the first and second substitute, and why does the bill's own summary language never change to reflect it?
  5. Why did the same representative run two separate bills carrying identical new DNR spending authority in the same session — and why was the funding source added to one of them, then removed again, in the space of two and a half hours on the last night of the session?
  6. If H.B. 157's own floor sponsor drafted a substitute removing the litigation authority entirely, why was it never brought to a vote before the bill died by other means?

Updates since this was posted

Updates for the cases in this part. The full list is in Part 1.

Words to know

Tap a card to see what it means.

Connected Hive work

Behind this piece

8
Cases documented
13
Bills named, each now linked
13
le.utah.gov bill pages checked Oct. 17
13
LegiScan records checked Oct. 17
3
Bill texts opened (introduced or enrolled)
13
News articles opened for the update
18
Searches run for the Oct. 17 update (estimate)

Posted Sept. 8, 2026 (the docket also lists an update on Sept. 13, 2026). Updated Oct. 17, 2026: split into two linked parts; new colors and large print; short versions, diagrams, words to know, questions to ask, links to related Hive pages, a plain-words page, links for every bill named, and dated record-check notes in each case. Wording fix: "chief-sponsored" changed to "was the primary sponsor of" in two places (Case 6 and The pattern). No earlier facts changed. Updated Oct. 18, 2026: moved to the bait-and-switch repo and linked to new Parts 3 and 4; our Sept. 17, 2026 short summary of each case added inside the case, with two dated corrections; a records check of all 2026 bill status pages added to the updates. No earlier text removed.

Sources (tap to open)
  • Bill text, substitute comparisons, and status/vote histories: le.utah.gov (S.B. 2001, H.B. 185, H.B. 491, H.B. 60, H.B. 392, H.B. 373, S.B. 12, H.B. 236 [introduced, S01, S02, S03/enrolled], H.B. 125, H.B. 157, H.B. 273, H.B. 17)
  • Referendum signature totals and timeline: KSL.com, Ballotpedia, Deseret News, The Salt Lake Tribune (Dec. 2019 – Jan. 2020)
  • Sen. Sandall's floor remarks on H.B. 373: The Salt Lake Tribune, Feb. 29, 2024
  • Bar H Ranch withdrawal and H.B. 60 timing: public water-right filing records

Bill pages (links added Oct. 17, 2026)

le.utah.gov bill pages load sponsor and status details with JavaScript, so each bill's sponsor, status and votes were also checked on LegiScan on Oct. 17, 2026.

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

Bait and Switch: independent accountability reporting on Weber County and Utah government.

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

Bait-and-switch docket · Master Index (Hive library) · Read on Substack