POLISCOPE
Back to bills

The civic record

Read. Follow. Verify.
Enacted

Utah requires large new data centers to report water use and communicate with local water providers

Original title: Data Center Water Transparency Amendments

Last action · March 23, 2026: Governor SignedSponsors: Jill Koford and 13 others

Introduced
Committee
Floor Vote
Passed
Law

Track this bill to get notified when it advances a stage. One tap to stop, anytime.

Public stanceCommunity reactions are separate from the official record and reporting.

What This Bill Does

This law requires operators of new large data centers withdrawing 75 or more of water annually to notify water providers and report water consumption, discharge, and conservation plans to the Division of Water Rights before construction and annually thereafter starting July 1, 2026. Land use authorities must notify water and environmental agencies when reviewing new data center applications, and the state engineer may penalize operators up to $100 per day for failing to submit required reports.

Why it matters

Operators of large data facilities face mandatory pre-construction disclosures, annual water-use reporting requirements, and daily fines of up to $100 for non-compliance, while the state publicly discloses water withdrawal data for individual facilities.

Background
  • Large data centers require significant amounts of water for cooling server hardware, drawing increased scrutiny from state lawmakers regarding local water supplies. context
  • The Utah Legislature considers bills addressing water conservation and reporting standards during its annual general sessions. context

Who It Affects

Groups the bill's text affects, as described in the record. Being affected is not a position for or against it.

Directly affected

Operators of large data centers

Operators must submit pre-construction notices and annual water withdrawal reports, communicate with water providers, and face daily fines of up to $100 for incomplete reporting.

Directly affected

Land use authorities

Municipal and county land use authorities are required to notify state water agencies and relevant water providers before approving land use applications for new large data centers.

Directly affected

Water providers

Retail water suppliers and water conservancy districts receive pre-construction notifications and details regarding anticipated water consumption to determine location compatibility.

Directly affected

Division of Water Rights

The division must receive operator reports, enforce reporting rules, impose fines for non-compliance, and publish non-aggregated water withdrawal data on its website.

Key Facts

You don't have to trust us. Each fact below is taken straight from the official document - click any one to see the exact passage, highlighted in the original.

Frequently Asked Questions

What qualifies as a large data center under this law?
A large data center is a facility with an annual water withdrawal of 75 or more that houses networked server computers, spans at least 10,000 square feet, includes cooling or power generation infrastructure, and is owned or leased by the operator or a commonly owned entity.
What information must data center operators report to the state?
Operators must report their location, estimated annual water withdrawal, discharge treatment plans, discharge temperature adjustments, water reuse or replacement activities, and annual efforts made to reduce water consumption.
Will individual data center water use data be made public?
Yes, the Division of Water Rights must publish water withdrawal data for each individual new large data center on its public website by September 1 for the previous calendar year, rather than publishing it only in the aggregate.
What are the penalties for failing to submit water use reports?
If an operator fails to submit a complete report after receiving notice, the Division of Water Rights will impose a fine of up to $100 for each day the operator fails to comply.

What else do you want to know?

News Coverage

No news coverage found yet. Articles are indexed twice daily.

Where This Stands

Current status: Signed into law.

Procedural history

63 actions
  1. Mar 23, 2026Lieutenant Governor's office for filingEnrolled
    Governor Signed
  2. Mar 12, 2026House
    House/ to Governor
  3. Mar 12, 2026House
    House/ received enrolled bill from Printing
  4. Mar 11, 2026House
    House/ enrolled bill to Printing
  5. Mar 11, 2026Clerk of the House
    Enrolled Bill Returned to House or Senate
  6. Mar 6, 2026Legislative Research and General Counsel / Enrolling
    Draft of Enrolled Bill Prepared
Show 57 earlier actions
  1. Mar 6, 2026Legislative Research and General Counsel / Enrolling
    Bill Received from House for Enrolling
  2. Mar 5, 2026House
    House/ signed by Speaker/ sent for enrolling
  3. Mar 5, 2026House
    House/ received from Senate
  4. Mar 5, 2026Senate
    Senate/ to House
  5. Mar 5, 2026Senate
    Senate/ signed by President/ returned to House
  6. Mar 5, 2026Senate
    Senate/ received from House
  7. Mar 5, 2026House
    House/ to Senate
  8. Mar 5, 2026House
    House/ concurs with Senate amendment
  9. Mar 5, 2026House
    House/ placed on Concurrence Calendar
  10. Mar 5, 2026House
    House/ received from Senate
  11. Mar 5, 2026Senate
    Senate/ to House with amendments
  12. Mar 5, 2026SenateFloor
    Senate/ passed 2nd & 3rd readings/ suspension
  13. Mar 5, 2026Senate
    Senate/ placed on 2nd Reading Calendar
  14. Mar 5, 2026Senate
    Senate/ motion to reconsider
  15. Mar 5, 2026Senate
    Senate/ to House
  16. Mar 5, 2026Senate
    Senate/ failed
  17. Mar 5, 2026Senate
    Senate/ uncircled
  18. Mar 4, 2026Senate
    Senate/ circled
  19. Mar 4, 2026Senate
    Senate/ 2nd & 3rd readings/ suspension
  20. Mar 3, 2026Released
    LFA/ fiscal note publicly available for HB0076S03
  21. Mar 3, 2026Senate
    Senate/ placed on 2nd Reading Calendar
  22. Mar 3, 2026Senate
    Senate/ comm rpt/ substituted
  23. Mar 3, 2026Senate
    Senate Comm - Favorable Recommendation
  24. Mar 3, 2026Senate
    Senate Comm - Substitute Recommendation
  25. Mar 3, 2026Version Sponsor
    LFA/ fiscal note sent to sponsor for HB0076S03
  26. Mar 2, 2026Legislative Fiscal Agency
    LFA/ bill sent to agencies for fiscal input for HB0076S03
  27. Mar 2, 2026Legislative Fiscal Analyst
    LFA/ bill assigned to staff for fiscal analysis for HB0076S03
  28. Feb 26, 2026Senate
    Senate Comm - Not Considered
  29. Feb 24, 2026Released
    LFA/ fiscal note publicly available for HB0076S02
  30. Feb 24, 2026SenateCommittee
    Senate/ to standing committee
  31. Feb 13, 2026Version Sponsor
    LFA/ fiscal note sent to sponsor for HB0076S02
  32. Feb 11, 2026Legislative Fiscal Agency
    LFA/ bill sent to agencies for fiscal input for HB0076S02
  33. Feb 11, 2026Legislative Fiscal Analyst
    LFA/ bill assigned to staff for fiscal analysis for HB0076S02
  34. Jan 30, 2026SenateIntroduced
    Senate/ 1st reading (Introduced)
  35. Jan 29, 2026Senate
    Senate/ received from House
  36. Jan 29, 2026House
    House/ to Senate
  37. Jan 29, 2026HouseFloor
    House/ passed 3rd reading
  38. Jan 29, 2026House
    House/ 3rd reading
  39. Jan 26, 2026Released
    LFA/ fiscal note publicly available for HB0076S01
  40. Jan 23, 2026House
    House/ 2nd reading
  41. Jan 23, 2026House
    House/ comm rpt/ substituted/ amended
  42. Jan 23, 2026Version Sponsor
    LFA/ fiscal note sent to sponsor for HB0076S01
  43. Jan 22, 2026House
    House Comm - Favorable Recommendation
  44. Jan 22, 2026House
    House Comm - Amendment Recommendation
  45. Jan 22, 2026House
    House Comm - Substitute Recommendation
  46. Jan 22, 2026Legislative Fiscal Agency
    LFA/ bill sent to agencies for fiscal input for HB0076S01
  47. Jan 22, 2026Legislative Fiscal Analyst
    LFA/ bill assigned to staff for fiscal analysis for HB0076S01
  48. Jan 21, 2026HouseCommittee
    House/ to standing committee
  49. Jan 20, 2026HouseIntroduced
    House/ 1st reading (Introduced)
  50. Jan 14, 2026House
    House/ received fiscal note from Fiscal Analyst
  51. Jan 14, 2026House
    House/ received bill from Legislative Research
  52. Jan 8, 2026Released
    LFA/ fiscal note publicly available for HB0076
  53. Jan 5, 2026Version Sponsor
    LFA/ fiscal note sent to sponsor for HB0076
  54. Dec 23, 2025Legislative Fiscal Agency
    LFA/ bill sent to agencies for fiscal input for HB0076
  55. Dec 23, 2025Legislative Fiscal Analyst
    LFA/ bill assigned to staff for fiscal analysis for HB0076
  56. Dec 23, 2025Legislative Research and General Counsel
    Numbered Bill Publicly Distributed
  57. Dec 23, 2025Legislative Research and General Counsel
    Bill Numbered but not Distributed

Version history

Only one version on file - nothing to compare yet. As later stages (committee substitute, engrossed, enrolled) are captured, the redline appears here.

View official text →

Voting Record

Motion succeededHouse1/29/2026Utah LegislatureOfficial roll call ↗

House/ passed 3rd reading

Total

75

Yes
72
No
0
Present
0
Not voting
3
Abstain
0

Lobbying Activity

No state lobbying filings in our records match this bill. Federal lobbying reports (LDA) cover Congress, so they are not listed on state bills.

Full breakdown

Who this bill affects and the strongest case for and against it, written only from the bill’s own text.

Sponsors

Discoveries

1 pattern noticed across the record

Patterns POLISCOPE noticed across the record. These are observations to investigate, not conclusions.

policy shift98% confidence

Mandatory Data Center Water Transparency

The state shifts from general water monitoring to specific facility-level reporting and public disclosure for large data centers withdrawing over 75 acre-feet annually.

Connected Entities

Salt Lake County, Scott D. Sandall, Division of Water Rights and 2 more
locationSalt Lake County“Jurisdiction for district court review of state engineer orders”Map →
PersonScott D. Sandall“Senate Sponsor of HB 76”Map →
OrganizationDivision of Water Rights“Division responsible for receiving reports and publishing data”Map →
OrganizationDivision of Water Quality“State division receiving notices and non-proprietary report information”Map →
PersonJill Koford“Chief Sponsor of HB 76”Map →

Sources

Analysis Score

0–100
  • Significance65
    How much this matters to a regular citizen
  • Controversy35
    Intensity of disagreement among stakeholders
  • Entertainment5
    Compellingness for a non-policy-wonk reader
  • Buzz40
    Current news / social attention level

Publisher tools

Share or embed this record

POLISCOPE publisher tools

Share or embed this record