This website is designed as a complete educational module a city can drop into a city. It explains the opportunity, surfaces the risks, organizes a KPI scorecard, and gives leaders the 10 questions they should ask before approving a data center deal.
A city should approve a deal only when measurable public value is larger than measurable public burden, and when that value is contractually enforceable.
The best city argument for a data center is not “jobs.” It is a stronger mix of long-term tax base, upgraded power and fiber infrastructure, future AI and digital ecosystem positioning, and structured community benefits. These pages should help city leaders separate real upside from sales language.
That framework should define zoning, utility cost allocation, disclosure requirements, water guardrails, noise standards, community benefits, and an annual public dashboard.
Most failed or controversial projects break down in one of four places: power, water, community impact, or governance. The education pages should explain each risk in plain language and show how it translates into measurable city exposure.
Can the local grid absorb the load without shifting upgrade costs to households? Can water systems supply peak use through drought conditions? Are backup systems and transmission interconnects understood early?
Noise, diesel testing, visual scale, traffic during construction, and land-use conflict can quickly create backlash. If nearby residents feel they are absorbing the burden while others capture the value, the deal becomes politically fragile.
Poorly structured abatements, weak PILOTs, and open-ended subsidies can erase the public upside. Cities need to compare revenue per acre and per MW against alternative land uses.
Opaque negotiations, NDAs, weak reporting, and no clawbacks create the biggest long-term problem: the city cannot prove whether the deal worked.
Use four KPI pillars. Every major project should be scored before approval and then monitored annually after commissioning. This page can become the core scorecard page inside the app.
| Pillar | What to measure | Why it matters | Suggested threshold |
|---|---|---|---|
| Fiscal value | Net annual public value, PILOT/tax revenue, revenue per acre, revenue per MW, incentive payback period | Shows whether the city is actually winning financially | Positive within 3–5 years |
| Infrastructure burden | Peak MW demand, who funds grid upgrades, daily/annual water draw, reclaimed water share, cooling approach | Tests whether the project creates hidden utility and resilience costs | No residential cost shift |
| Community outcome | Noise at property line, diesel runtime, local hiring, training seats, community fund contribution, complaint count | Measures whether nearby residents experience the project as fair | Binding CBA/PBA |
| Governance quality | Disclosure completeness, independent review, audit rights, clawbacks, annual reporting cadence | Prevents the city from approving a deal it cannot later evaluate | Full public dashboard |
These questions should become an intake form, policy checklist, and stakeholder interview guide. Each answer should map directly to one or more KPIs in the scorecard.
Is the goal tax base, strategic infrastructure, AI ecosystem positioning, redevelopment, or workforce development? If the objective is vague, the KPI will be vague too.
How much annual tax, PILOT, and fee revenue remains after abatements, public incentives, utility upgrades, road work, and staff overhead?
Does the operator fund substations, interconnection, transmission, and resilience upgrades, or do those costs flow to ratepayers?
Measure daily draw, annual draw, drought sensitivity, source reliability, and the percentage served by reclaimed or non-potable systems.
Quantify noise, visual scale, diesel testing, truck traffic, construction duration, and buffer distances from homes, schools, and sensitive uses.
Ask for local hiring targets, apprenticeship seats, community college programs, supplier diversity, and public-benefit funding with enforcement.
Compare the project against alternative uses for the same acreage, tax base, employment profile, and long-term planning goals.
Will the city disclose the operator, end user, key utility assumptions, incentive schedule, and annual reporting obligations before approval?
Define reporting cadence, independent verification, complaint tracking, water and energy reporting, and the exact triggers for clawbacks.
Set red-line thresholds before negotiation: water risk too high, grid costs socialized, weak PILOT, poor transparency, or community harm too great.
If this is being added to a city, these sections can become standalone pages or nested routes. Together they form a complete reading and research experience for city leaders, staff, residents, and investors.
Explains the market context, why data centers are growing, and what municipalities hope to gain.
Separates durable public value from common overclaims around jobs and growth.
Shows how electricity demand, substation upgrades, and ratepayer exposure should be evaluated.
Explains consumption, drought stress, reclaimed water options, and cooling design tradeoffs.
Compares deal structures, payback logic, and the difference between strong and weak agreements.
Defines what should be mandatory in a CBA or public-benefit agreement.
The city’s core dashboard page, with pillar scores, thresholds, and annual reporting.
A policy intake page that staff can use before moving a proposal to council or planning commission.
A final recommendation page: approve, approve with conditions, redesign, or reject.
At the end of the workflow, the app should produce a simple answer supported by evidence. The city should not approve a project because it is fashionable or because the capital spend looks large.
Use when fiscal value is strong, grid and water burden are controlled, community benefits are binding, and reporting is transparent.
Use when the project is strategically attractive but still needs stronger PILOT terms, utility cost allocation, or neighborhood protections.
Use when the site or deal structure is wrong, but a different layout, cooling design, or incentive package could make the project viable.
Use when the project fails red-line criteria: socialized grid costs, excessive water stress, weak fiscal return, or weak transparency.
Use this to turn the website into app pages and internal working modules.
Suggested slugs: /overview, /opportunity, /risk, /kpi, /questions, /decision.
Each answer should populate a KPI record or weighted decision score.
After approval, the same KPI structure can support annual reporting and compliance monitoring.
The site is intentionally editorial and low-friction so it can sit cleanly inside the product.