Jefferson County committee hears Altoonas lessons from Meta data center, eyes binding community-benefit rules

Jefferson County's Economic Development Objectives Committee spent its meeting hearing advice from Altoona, Iowa, officials and a county consultant about how to write enforceable community benefit and development agreements for large data centers.

Mayor Mary O'Connor of Altoona and Chad Quick, Altoona's economic development director, told the committee that Meta's campus in Altoona has expanded over more than a decade and that the company has repeatedly upgraded servers and buildings as technology advanced. "They update it and keep it the highest level as they can," O'Connor said, describing continuous replacement of computing equipment and the construction of new halls.

The Altoona officials sought to balance concerns about utilities and land use with economic gains. Quick estimated the complex is currently assessed at about $1.3 billion; O'Connor said when pilot tax agreements expire the property could be taxed at full value, which she estimated could translate into roughly $43.5 million a year across taxing entities (figure cited by Altoona as an estimate). O'Connor also said Meta funded major local infrastructure, including a water tower and sewer mains, and that the company has provided annual grants to schools and libraries. "They've changed kind of the thinking of your community," she said.

Committee members pressed for technical detail. On water and cooling, Altoona officials said the entire Meta facility uses "I think it's under 400,000 gallons a day," with peak evaporative cooling demand in hot months, and that water rates had not increased in Altaona due to the facility. On power, officials said Meta invested in in-state wind and works with the local regulated utility; Altoona representatives stressed that the city itself does not generate electricity and that utility-rate impacts are governed by the state-regulated provider.

Mitch Baer, the county's consultant on community benefit frameworks, presented a hybrid approach that ties any community-benefit agreement to land-use approvals. Baer recommended requiring development agreements or CBAs as a condition of zoning, then building in enforcement tools: annual public reporting on energy and water use and community payments; cure periods and financial penalties for noncompliance; third-party audits; and clawbacks or exit penalties tied to ownership changes or early closure. "Failure to comply with the material terms of the agreement will constitute a violation of applicable zoning approval and may result in enforcement action," Baer said, describing standard enforcement language the county could use.

Baer outlined specific components he recommends: infrastructure-cost recovery (road and utility upgrades tied to the development), energy and environmental commitments (renewable procurement and demand-response participation), workforce and economic inclusion (construction-phase local-hire goals and apprenticeship targets, and operational internships/training partnerships), and limits on water use or use of nonpotable/reclaimed water where local scarcity exists. For construction-phase hiring, he suggested a midrange local-hiring goal and apprenticeship requirements (30—50% local hiring range and apprenticeship utilization), and recommended that apprenticeship ratios not exceed 1-to-1 of apprentice-to-journeyman, a point later echoed by a committee member.

On closure and decommissioning, Baer recommended requiring a decommissioning plan before occupancy, updated every five years, with a timeline to begin remediation within 90 days of permanent cessation and to complete work within 12 months unless the county grants an extension. He also proposed financial assurance equal to 100—125% of the county-approved estimated cost of decommissioning and remediation, posted before a certificate of occupancy is issued, so the county could draw on those funds if an owner failed to remediate the site.

Committee members discussed procedural and political issues as well. County Executive Gannon and others cautioned that organized opposition is likely when a proposal reaches public hearings, based on the St. Charles example; one committee speaker warned that outside groups often mobilize and may be paid to oppose projects. The committee discussed whether agreements should survive annexation and asked staff to seek legal opinions on survivability.

No formal decision was made on incentives or an individual project at the meeting; members asked staff to draft a regulatory template and an agreement outline. The committee set a Planning & Zoning public hearing timeline (Baer requested draft regulations ahead of a March 12 public hearing) and approved a meeting date by motion for February 4, 2026, before adjourning.

What happens next: staff will work with legal counsel and the county consultant to produce draft regulations and a template CBA/development-agreement for committee review and public notice ahead of the planning commission's public hearing. The committee emphasized it wants clear, enforceable standards in place so any future application that "checks the boxes" can be judged consistently, even amid public controversy.