New Here? Start Simple
A Public Infrastructure District (PID) is a small government created to pay for things like roads and sewer lines in a new development — with the power to issue its own debt and set its own budget.
This bill said a PID's board has to hold its meetings inside its own district. That's a real rule for public access.
But the bill also lists exceptions. As introduced, one exception let a board meet outside the district once a year, for planning only, with no votes allowed. A House floor amendment removed that exception — but replaced it with one that lets a board meet anywhere inside the much bigger city or county that created it, any time, taking real votes. And nothing in the law requires the board to explain when it's used that exception, or checks how often it does.
What Changed, Section by Section
| As Introduced | |
|---|---|
| Exception for meeting outside the district | Once a year, for planning/education only, no final action or votes, public notice required |
| Replaced By a House Floor Amendment | |
| New exception | Any meeting may be held within the boundaries of the entity that created the PID — no frequency limit, no purpose restriction, votes allowed |
| What's Actually Enforced | |
| Reporting requirement | None specific to meeting location. Only the district's pre-existing general annual report to its creating entity — which would not surface a violation. |
A Quiet, Unanimous Path to a Real Loophole
- Jan 21, 2026House committee adopts amendments — including the retreat-exception swap described above — and gives the bill a favorable recommendation, 11-0-1.
- Jan 23, 2026Passes the House floor 70-0-5.
- Jan 30 – Feb 6, 2026Passes Senate committee and both floor readings, 5-0-3, 24-0-5, and 26-0-3 — zero recorded opposition at any stage in either chamber.
- May 6, 2026Signed into law.
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 Rule As It Reads
On its face, a real requirement with a clear boundary.
What The Exception Actually Allows
The requirement survives in name only. A narrow exception was traded for a broader one, and neither version of the law has any way to check compliance.
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 | F | A geographic boundary requirement was replaced with an exception broad enough to cover an entire county — the check on where a board can meet is functionally gone. |
| Transparency | F | No requirement to disclose when the exception is used, and no audit or penalty tied to meeting location. |
| Financial Accountability | N/A | This bill doesn't touch how a PID raises or spends money. |
| Environmental Impact | N/A | Not applicable to a meeting-location rule. |
| Community Impact | D | Residents near a PID lose the practical ability to observe board meetings if the board chooses to meet elsewhere in a large creating county. |
A transparency requirement that reads well and enforces nothing.
How This Could Have Actually Protected the Public
The bill didn't need to choose between the old retreat exception and the new creating-entity exception. A version that actually protected the public could have:
- Kept the exception narrow and specific — limited to a defined radius around the district, not the entire boundary of whatever city or county happens to have created it
- Required a board to publicly state, in its own meeting notice, which exception it's relying on and why, every time it meets outside the district
- Required an annual public report specifically listing every out-of-district meeting held that year — not buried inside a general annual report that doesn't mention location at all
- Made a decision reached at an out-of-district meeting void if the board can't show one of the stated exceptions actually applied
Sources
Show sources ▸Hide sources ▾
Sources
Show sources ▸Hide sources ▾- H.B. 17, official bill text (introduced, amended, and enrolled versions) — le.utah.gov
- H.B. 17 voting record — le.utah.gov Bill Status/Votes page