A data center agreement is tested when something departs from the plan: a neighbor reports a failing well, equipment produces an unexpected nighttime hum, construction stops between phases or an operator decides to leave.
For Hermantown, the experience of other communities points toward a practical question beyond the size of Google’s investment: How quickly can the city require a problem to be corrected, and who pays while responsibility is being determined?
There is an important distinction between identifying questions and establishing omissions. Hermantown has publicly described substantial protections, including neighboring-well provisions and a reuse and decommissioning agreement. This column examines those published summaries alongside other communities’ experiences and agreements. It is not a finding that the provisions discussed here are absent from Hermantown’s complete contract package; the latest council packet could not be retrieved for a clause-by-clause review.
Noise provides one documented example of a protection communities have strengthened after gaining operating experience. Chandler, Arizona, adopted requirements for baseline sound studies, mitigation and annual testing during peak operations for five years after construction. Its rules also address generator testing, neighborhood notification and an on-site liaison. The city explained that changes in data center design had increased potential neighborhood noise impacts and prompted stronger requirements.
Virginia’s legislative auditors identified the underlying difficulty: Continuous low-frequency sound from some facilities troubled nearby residents even when it rarely violated existing noise ordinances. Most facilities did not generate complaints, which researchers attributed to location or design. That finding directs attention to the measurement standard itself, rather than an assumption that every facility will be disruptive or that compliance with a general ordinance resolves every complaint.
For Hermantown, the contractual questions follow from that experience. Where will sound be measured, under which operating conditions and by whom? Will testing address tonal and low-frequency sound as well as overall volume? What happens when additional cooling equipment begins operating? A useful protection would connect a defined standard to independent verification, a correction deadline and an enforceable remedy. A telephone number for complaints serves a different purpose from a binding obligation to resolve a verified violation.
Water protections require comparable precision. Hermantown’s Oct. 19 presentation describes a voluntary well-assessment program for properties within one-half mile of the project boundary, with a specified enrollment period. It also describes baseline groundwater testing before the first building permit and continuous monitoring during construction. Those are identifiable commitments. The follow-up questions concern households outside the boundary, owners who miss enrollment and problems that become apparent after construction ends.
The distinction is whether eligibility for a testing program also determines eligibility for assistance. The public should be able to establish whether an affected household can obtain temporary water promptly, who selects the expert investigating causation and who pays for that investigation. A separate question is whether interim assistance can begin without requiring either side to concede liability. These are proposed points for contract review, not findings that Google has refused such protections.
Residents of The Dalles, Oregon, raised similar concerns during negotiations over Google’s expansion. At a 2021 council meeting, well owners asked what would happen if groundwater declined and whether they would have to contest responsibility against a company with far greater financial resources. The reporting documents those questions; it does not establish that Google subsequently caused their wells to fail. It does show that access to a workable remedy can matter as much to residents as the promise of protection.
Hermantown also has site-specific advice from Minnesota’s Department of Natural Resources. In its Sept. 10 letter, the agency emphasized collecting baseline information before construction, identifying the observations that would trigger intervention and establishing corrective measures that could be implemented promptly. The DNR acknowledged progress and did not object to the environmental review. Its recommendations nevertheless distinguish collecting measurements from deciding in advance what those measurements will require someone to do.
Closure planning is another area where Hermantown has already negotiated a significant commitment. The city’s presentation identifies Google as a signatory to a decommissioning agreement carrying a $210 million obligation, adjusted annually for inflation, with a 50-year term following final project completion. It describes that arrangement as effectively a parent-company guarantee. Any assessment of the city’s negotiations should acknowledge that protection rather than suggest officials have ignored the possibility of closure.
The next inquiry concerns how that obligation would be funded and enforced. A corporate promise, an escrow account and a bank letter of credit provide different routes to payment. Reviewers should establish whether money is available before the city incurs cleanup expenses, whether the amount is periodically checked against an independent cost estimate and what happens if demolition costs rise faster than general inflation. Partial closure also deserves examination: One operating building could coexist with other buildings that have been unused for years.
Lancaster, Pennsylvania, offers an example of provisions another city has negotiated, although its agreement should not be presented as a proven long-term operating success. Lancaster’s published summary says missed payments can be collected through financial security, including a letter of credit. It requires new owners to assume obligations when property is sold and describes remedies for nonfinancial violations after notice and an opportunity to correct them, including seeking court orders requiring compliance or discontinuance of operations.
That example raises two separate issues for Hermantown: whether obligations survive a sale or change of operator, and whether financial backing survives with them. Naming a new owner as responsible does not by itself establish that the owner has adequate resources. The World Resources Institute, in its guidance on data center agreements, recommends parent-company backing, independent monitoring and explicit provisions governing transfers. Those are recommendations for managing contractual risk, not evidence that a particular Google subsidiary is financially unsound.
Public disclosure is another operational protection. In The Dalles, Google’s water-use information became the subject of a legal dispute before records were released. A contract-review question for Hermantown is whether routine reports on resource use, monitoring results, violations and corrective work will be published on a schedule, subject to applicable public-records law. Security-sensitive facility information can be distinguished from the measurements residents need to evaluate compliance.
The city also needs the capacity to interpret those reports. Independent testing has limited practical value if no one has funding to review results or pursue a violation. WRI recommends developer-funded technical and legal resources alongside independent oversight. For Hermantown, one option to examine is a replenishing fund controlled by the city for qualified outside review, with clear limits on eligible expenses and procedures for resolving disputed charges. That would make oversight an operating responsibility with a budget.
Emergency response costs can be specified, too. Lancaster’s agreement summary requires emergency planning, ongoing training for first responders at no cost and reimbursement of city response costs above $25,000 per incident. Hermantown’s appropriate terms would depend on its own fire department, mutual-aid arrangements and equipment needs. The useful comparison is the specificity: Which training, equipment and extraordinary response expenses are the operator’s responsibility, and when must payment occur?
Electricity obligations belong partly in a different proceeding. Minnesota’s Public Utilities Commission reviews the service agreement and protections against shifting data center costs to other customers. Hermantown cannot resolve that entire issue through a municipal development contract. Its review can, however, distinguish responsibilities assigned to the city from those assigned to the utility and state regulators, so that a general assurance does not obscure which institution must act.
The possible weakness, then, is not necessarily an overlooked subject. Noise, wells, infrastructure and closure already appear in Hermantown’s public discussion. The closer examination concerns the steps between a reported problem and a completed remedy: the evidence required, the responsible decision-maker, the deadline, the available money and the consequences of noncompliance.
Other communities’ experience gives Hermantown a basis for asking those questions before residents, city staff or a future operator must answer them under pressure.
