Frederick’s Data-Center Debate Needs Comparable Numbers, Not Just Big Ones
Frederick County’s data-center debate is full of impressive numbers. A useful public comparison must separate temporary jobs, recurring revenue, one-time payments, infrastructure costs, and neighborhood-level impacts.
Frederick County’s data-center debate is full of impressive numbers.
Residents have heard about the hundreds of construction jobs, approximately 200 permanent positions associated with one Amazon facility, more than $50 million in real-estate taxes, and a proposed $110 million community-benefits agreement.
Each number may describe a real benefit. Taken together, however, they do not yet amount to a complete economic case. The figures measure different things, cover different periods, and answer different questions.
Hundreds of construction jobs can produce meaningful wages and economic activity, but they are temporary. Permanent operating jobs are more useful when evaluating the long-term employment value of a project.
More than $50 million in real-estate taxes sounds substantial, but the public needs to know what period that figure covers, how much represents recurring revenue, and what public costs accompany the development.
The proposed $110 million community-benefits agreement was not ordinary annual tax revenue. It was a negotiated package associated with an agreement that would have restricted the county’s ability to change certain development rules affecting the company’s property. County Executive Jessica Fitzwater ultimately rejected that proposal after public opposition.
Those distinctions matter.
What Should Frederick Measure?
A credible economic analysis should allow residents and policymakers to compare data centers with other realistic uses for the same land and infrastructure.
At minimum, the county should report the following.
Revenue per Acre
Frederick County’s Critical Digital Infrastructure overlay covers approximately 2,600 acres north of Adamstown. Fitzwater has said she would support reducing it to properties with existing development approvals, reported as roughly 1,376 acres.
Total revenue alone does not show whether those acres are being used efficiently. Revenue per acre would provide a better comparison with warehouses, advanced manufacturing, life-sciences facilities, housing, agriculture, or land preservation.
Revenue per Megawatt
Data centers are unusually dependent on electrical capacity. Their economic value should therefore be evaluated not only by acreage, but also by the amount of power they require.
Revenue per megawatt would help answer a basic public-policy question: How much local economic benefit is Frederick receiving for the electrical capacity committed to these facilities?
That comparison is increasingly important when large electrical loads may require transmission upgrades, generation capacity, substations, or other investments whose costs can extend beyond the project site.
Temporary and Permanent Employment
Construction employment and permanent employment should always be reported separately.
Both matter, but they represent different forms of economic value. A multiyear construction project may employ hundreds of people while producing a much smaller number of permanent operating positions.
Reports should also distinguish among:
- Workers employed directly by the facility
- Contractors and subcontractors
- Temporary construction employment
- Permanent operations and maintenance jobs
- Indirect jobs attributed to broader economic modeling
Without those distinctions, employment estimates can sound more durable than they are.
Net Public Revenue
Gross tax collections are only one side of the ledger.
A meaningful analysis should identify public expenses associated with road improvements, emergency-response capacity, planning and permitting, environmental monitoring, utility infrastructure, and any other government obligations created by the development.
The relevant figure is not simply how much revenue a project generates. It is how much remains after the public costs attributable to that project are considered.
The Timing and Reliability of Payments
Not every dollar has the same long-term value.
Recurring property taxes are different from one-time payments. Negotiated community benefits are different from legally required taxes. Projected revenue is different from revenue already collected.
Public presentations should clearly separate:
- Taxes already paid
- Forecast annual revenue
- One-time payments
- Voluntary community benefits
- Infrastructure provided by the developer
- Tax incentives, abatements, or other public concessions
This would help residents determine which benefits are dependable and which depend on future construction, contractual terms, or changing market conditions.
Geographic Concentration of Costs
Countywide averages can conceal neighborhood-level effects.
Even if a project produces a positive fiscal result for Frederick County as a whole, nearby residents may experience most of its construction traffic, noise, visual impact, land-use change, or property-market uncertainty.
An honest economic analysis should identify where benefits are received and where costs are concentrated. A countywide net benefit does not automatically mean that every affected community is treated fairly.
The Standard Should Be Comparison, Not Promotion
The question is not whether data centers create economic benefits. They can produce tax revenue, construction activity, permanent employment, and investment in previously industrial land.
The harder question is whether those benefits justify the land, electrical capacity, infrastructure, and regulatory commitments required—and whether they compare favorably with the alternatives.
That question cannot be answered by placing several large but fundamentally different numbers next to one another.
Before Frederick makes additional commitments that may be difficult to reverse, officials should publish a transparent, standardized ledger covering the full expected life of each project.
Big numbers are persuasive.
Comparable numbers are useful.
Frederick needs the latter.
Sources and Further Reading
- Frederick County data-center overview
- Frederick County Critical Digital Infrastructure overlay record
- Maryland Data Center Impact Analysis and Report legislation
- Frederick News-Post reporting supplied by Katie for editorial analysis