New Jersey Mandates Biannual Energy and Water Disclosures for Data Centers

New Jersey Governor Mikie Sherrill signed legislation requiring data center operators within the state to submit detailed biannual reports on their energy and water usage to the New Jersey Board of Public Utilities. Under the new mandate, facilities must break down their power consumption between IT hardware and mechanical cooling systems, disclose peak daily water draws and sourcing, and detail backup power configurations. Concurrently, the state terminated a legacy $500 million tax incentive program previously aimed at attracting compute facilities without resource guardrails. This development marks a decisive shift in how regional authorities manage the explosive infrastructure growth driven by cloud computing and generative AI. Historically, hyperscalers and colocation providers treated localized power draw and water utilization figures as closely guarded proprietary data. By establishing mandatory regulatory reporting, the law ensures that public utility commissions can accurately audit localized grid strain and verify efficiency claims. Infrastructure planners and enterprise engineering leaders deploying workloads in Mid-Atlantic zones now face direct accountability for their physical footprint, as state regulators move to prevent commercial data centers from transferring upgrade costs to public utility ratepayers. Contextually, this legislation mirrors a wider policy shift across major cloud corridors. Similar measures—ranging from grid-connection clean energy mandates in Delaware to proposed reliability backstop fees in Pennsylvania—reflect growing systemic friction between accelerated AI deployments and regional utility capacities. With hyperscalers expanding data center capacity at unprecedented rates to accommodate compute-dense GPU clusters, state governments are transitioning from economic subsidies to strict operational guardrails and resource accounting. In practice, this regulatory trend requires cloud architects and DevOps teams to institutionalize GreenOps across their deployment pipelines. Teams must integrate telemetry for fine-grained carbon intensity, Power Usage Effectiveness (PUE), and Water Usage Effectiveness (WUE) directly into infrastructure-as-code and scheduling workflows. Workload scheduling strategies will need to incorporate dynamic regional carbon and grid-stress signals, shifting non-urgent batch processing and model training away from constrained availability zones. In the long term, engineering organizations that lack deep visibility into their per-workload resource overhead will face increasing operational friction, higher regional utility tariffs, and localized deployment throttles.