Of all the moments in a data center’s path from concept to operation, the tax abatement hearing is often the one where residents have the most practical power. It is a specific, publicly noticed, time-limited event. A governing body — a city council, county board, or industrial development authority — is required to take a vote, and before that vote, there is usually an opportunity for public comment. The decision has not yet been made. The leverage is real.
This window closes fast, and most communities miss it entirely. By the time residents notice a data center being built, the subsidy has already been approved, the deal has been signed, and the leverage that existed six months earlier is gone. Understanding how abatement proceedings work — how to find them, what to say at them, and what to ask for — is the most practical knowledge a community can have at the beginning of a data center siting fight.
The Scale of What Is Being Given Away
The subsidy at stake is not marginal. According to Good Jobs First, at least ten states already lose more than $100 million per year in tax revenue to data centers. Virginia, Texas, and Georgia each report losses exceeding $1 billion annually. In the space of twenty-three months, Texas revised its fiscal year 2025 cost projection for data center tax exemptions from $130 million to $1 billion. Twelve states do not disclose how much revenue they are forgoing at all.
State sales and use tax exemptions are the largest category of subsidy, but they are typically automatic — enacted by the legislature and applied to any qualifying project without further public action. Property tax abatements are different. A property tax abatement — an agreement to reduce or eliminate property taxes on a new facility for a specified number of years — usually requires approval by a local governing body. That approval vote is the hearing.
The abatements themselves can be enormous relative to local government budgets. A thirty-five-year property tax abatement of 80 percent, like the one negotiated in El Paso with Meta for a $1.5 billion data center, represents a commitment that outlasts most political careers and extends well beyond any reasonable projection of the industry’s current form. What is agreed to at a single public hearing can bind a community for decades.
How to Find Out About Upcoming Hearings
Local government meeting agendas are the primary tool. Most counties, cities, and industrial development authorities are required to post agendas for public meetings in advance — commonly forty-eight to seventy-two hours before the meeting, though some jurisdictions post further in advance. Many local governments now post agendas on their websites. Economic development authority meetings, industrial development authority meetings, and city council or county board of supervisors meetings are all relevant venues.
The challenge is that data center abatement requests are not always labeled clearly on agendas. They may appear as a specific company name — which may be a project-specific LLC with no obvious connection to a hyperscaler — or as a line item under economic development consent agenda items. Signing up for agenda notifications from your local government is the baseline step.
State economic development disclosure requirements vary significantly. Some states require that proposed economic development incentive packages be made public before a vote; others do not. Good Jobs First’s Subsidy Tracker aggregates subsidy data from multiple states and can help identify patterns of deal-making in a given region, though it is necessarily retrospective.
Local investigative journalism is often the earliest warning system. Reporters covering economic development beats in high-density data center markets — Northern Virginia, Phoenix, Dallas, Atlanta — have developed sources that alert them when deals are in negotiation. Following local business journals and regional newspapers that cover economic development is practical. In Michigan, an overflow crowd showed up to testify before state lawmakers in April 2026{target=”_blank”} about data center secrecy after communities learned that developers had secured tax exemptions in deals negotiated behind NDAs. The anger there was partly a function of having missed the earlier opportunity: residents found out after decisions were made.
Local real estate records and zoning notices are another early indicator. Data center developers frequently acquire land and file initial permit applications well before any subsidy request is made public. Monitoring building permit applications in commercially zoned areas near existing data center corridors, or tracking large land transfers in county property records, can provide advance notice of projects that will eventually come before a governing body for subsidy approval.
What Effective Participation at Abatement Hearings Looks Like
A public comment period at an abatement hearing is not a debate. It is an opportunity to create a record — a set of documented concerns that governing body members must be seen to address, or that can later be cited if the community seeks accountability. Effective participation is organized, specific, and documented.
Organized presence matters in ways that are hard to overstate. A governing body deciding whether to approve a thirty-year tax abatement is more likely to attach conditions to that approval, or to delay for further study, when fifty residents show up than when five do. The residents who attend do not all need to testify. Their presence is itself testimony about the political stakes of the decision.
Testimony that is effective in these settings is specific rather than general. Opposition to data centers in the abstract is less useful than testimony documenting a specific concern — noise impacts on a named residential street, water demand in a named watershed, grid cost implications for residential ratepayers in the county — supported by evidence. Governing body members making a decision about a tax abatement for a specific project are more likely to respond to specific factual arguments than to general opposition.
The most durable form of participation at an abatement hearing is a written comment submitted for the public record. Verbal testimony is often summarized or paraphrased in meeting minutes; written submissions become part of the record as filed. Documenting community concerns in writing creates a basis for later accountability: if the governing body approved the abatement despite documented warnings about noise or water use, that record can inform future organizing.
Community Benefit Agreements: Conditions in Exchange for Subsidy
A community benefit agreement (CBA) is a formal contract between a developer and a community, typically negotiated as a condition of receiving a public subsidy or development approval. A well-crafted CBA converts a governing body’s leverage — the power to approve or withhold subsidy — into legally enforceable commitments by the developer.
The Brookings Institution has identified key components that effective data center CBAs should include: quantifiable job commitments tied to wage standards, water use limits, noise level caps, local hiring requirements, renewable energy commitments, public reporting obligations, and clawback provisions if commitments are not met. These are not aspirational statements — they are enforceable contractual terms.
Documented cases illustrate what is achievable. In Lancaster, Pennsylvania, local officials working with Chirisa Technology Parks and CoreWeave negotiated an agreement that restricted water usage to 20,000 gallons per day, required reliance on clean energy, and set strict noise levels as contractual conditions. In Cedar Rapids, Iowa, a “community betterment” agreement with Google and QTS tied a twenty-year, 70 percent tax exemption to a minimum of thirty-one full-time positions at wages of at least $26.20 per hour after construction. In West Des Moines, Iowa, Microsoft’s agreement committed to 100 percent renewable energy and over $2 billion in projected tax revenue.
El Paso’s agreement with Meta required the company to start at 750,000 gallons of water per day with a closed-loop cooling system, publish annual sustainability reports detailing water and electricity usage, and commit to specific construction and operations employment levels — all as conditions of the 80 percent property tax abatement. These terms are contractually enforceable and represent the governing body using its leverage before the vote, not after.
Clawback provisions are among the most important elements of any CBA and among the most frequently omitted. A clawback provision specifies what happens if the developer fails to meet commitments: a return of abated taxes, financial penalties, or termination of the agreement. Without clawbacks, commitments made at a public hearing become aspirational. With them, commitments become obligations with consequences.
Job quality standards matter alongside job quantity claims. Data centers employ relatively few permanent operations workers — Meta’s $1 billion data center in Kansas City, for example, generated approximately 1,500 construction jobs and about 100 operations jobs once fully operational. Governing bodies that approve decades-long abatements based on employment projections should require wage floors, benefits standards, and local hiring preferences as conditions, not as developer talking points.
Conditions That Can Be Attached to Abatement Approval
The range of conditions that governing bodies have attached to data center abatements — or that community advocates have successfully argued for — includes:
Noise standards, typically specified as maximum decibel levels measured at the property line or at the nearest residential structure. Some agreements specify both daytime and nighttime limits and include low-frequency noise requirements, since data center cooling equipment produces low-frequency hum that can penetrate residential structures even at moderate measured decibel levels.
Water use limits, either as absolute caps or as conditions requiring the use of specified cooling technologies. The Lancaster, Pennsylvania agreement’s 20,000-gallon-per-day limit is an example; the El Paso agreement’s requirement for a closed-loop cooling system is another approach.
Local hiring requirements and prevailing wage standards for construction workers. Data centers are capital-intensive facilities with large construction phases, and construction employment is often the most significant local employment benefit. Prevailing wage requirements ensure that those jobs pay community-sustaining wages.
Renewable energy commitments, specifying what percentage of the facility’s energy must come from renewable sources or requiring the developer to execute power purchase agreements for new renewable generation.
Public reporting requirements, obligating the developer to submit annual reports on water use, energy use, employment levels, and compliance with other conditions. Some agreements require these reports to be publicly posted; the Brookings report recommends requiring public dashboards with key metrics.
Clawback provisions tied to specific triggers: failure to reach specified employment levels, failure to meet water or energy commitments, or early closure of the facility.
After the Hearing: Monitoring and Enforcement
Governing body approval of an abatement with conditions does not end the community’s role. The conditions must be monitored, and violations must be reported and pursued.
Most local governments do not have dedicated staff for monitoring compliance with economic development agreements. The practical work of checking whether a company is meeting its commitments often falls to residents and community organizations who track the relevant metrics — employment levels, noise complaints, water utility records — and bring discrepancies to the attention of local officials.
When a developer fails to meet employment commitments, the question of whether clawback provisions are enforced often depends on whether anyone is paying attention and pressing local officials to act. Good Jobs First has documented numerous cases nationally where companies received subsidies based on employment projections they did not meet, and where clawback provisions were not enforced because no one tracked compliance systematically.
The accountability structures that make CBAs meaningful over time are community organizations with sustained interest in monitoring outcomes, local journalism that covers economic development accountability, and local officials who understand that the political consequences of allowing commitments to lapse without enforcement are real. Building those accountability structures is work that begins at the abatement hearing, when the conditions are set, and continues for as long as the agreement is in effect.
For residents who miss the abatement hearing and want to understand what was agreed to, local government records — meeting minutes, adopted resolutions, executed agreements — are public documents. Requesting a copy of the abatement agreement from the local economic development authority or governing body is the starting point for any post-approval accountability effort.
The abatement hearing is the most accessible leverage point. It exists at a defined time, it is legally required to be noticed in advance, and the decision-makers present are accountable to voters in ways that utility commissioners and planning staff are not. Communities that show up organized, with specific asks and documented concerns, have changed outcomes. Communities that discover the deal after it is done have far fewer options.
This article was researched and drafted with AI assistance under human review. See our full AI and editorial practices.