When a Data Center Comes to Town: Nine Questions Every Local Government Should Be Ready to Answer
National · Data Centers & Development Review · Regulatory Guide
Originally published August 21, 2026 · Updated November 2026
Local officials do not need to decide whether data centers are good or bad before they build the capacity to review one. That was the premise of this guide when we published it in August, and the November 3, 2026 elections did not change it. What the elections changed is who is asking the questions, how much time they have, and what they inherit when they take office.
Voters in at least ten states decided roughly 40 local ballot measures on data centers, and in nearly every contest the restrictive position won, often by three to one. Several mayors and council members who supported specific projects were recalled or defeated. Candidates for governor and the U.S. Senate in Ohio, Texas, Kansas, Wisconsin, and Florida campaigned on data center positions. The counts and margins below come from reporting published November 4 and 5 and remain unofficial until certified.
This edition keeps the nine questions and adds what the results mean for the officials who now have to answer them: newly elected or re-elected governing bodies, the staff who serve them, and the applicants whose projects were pending when the votes were counted.
The point in one sentence
A community cannot make a deliberate, lawful choice about a data center until its code interpretation, technical studies, fiscal analysis, and public record all describe the same project; the 2026 elections changed who is asking the nine questions and how quickly they need answers, not the questions themselves.
At a glance
- Define the project. Distinguish accessory computing equipment from a principal data center use, and document the full campus and its proposed phases.
- Test the assumptions. Ask for project-specific evidence on infrastructure, water, sound, fiscal effects, and emergency response.
- Choose the review path deliberately. Evaluate the standards and authority available under the current code before recommending a conditional use process, a code amendment, or a temporary pause.
- Make participation useful. Publish nonexempt information early enough for questions to be considered within the applicable review schedule.
- Write obligations that staff can administer. Each material condition should identify a measurable requirement, a verification method, and a responsible party.
- Keep lawful outcomes available. Approval, conditional approval, a temporary pause, prohibition, or denial may be available in different circumstances. Counsel should identify which options the jurisdiction can lawfully use.
- New this edition. Inventory what the governing body inherited on election night: pending applications, vested rights, moratoria with expiration dates, and campaign commitments that have not yet been converted into lawful instruments.
What the November 2026 elections changed
What voters decided
Three independent trackers counted the local measures and reached slightly different totals, which is itself a lesson for staff reports: cite the tracker and the date.
- Ballotpedia counted 41 data center measures in 10 states on November 3, 2026. Twenty-eight would limit development and 13 would facilitate it or express support. (Reported by The Policy Circle, November 4, 2026.)
- Data Centers on the Ballot, a tracker operated by Redbud Consulting, counted at least 40 measures in 13 states, with the restrictive position winning or leading in 39 and averaging about 75 percent of the vote. The only "allow" outcome it recorded was Harwood, North Dakota, where voters declined to add a review and hearing requirement for industrial development. (Reported by ALEC and RTO Insider, November 4, 2026.)
- Forbes, drawing on Ballotpedia and U.S. Data Center Map, listed 41 measures across 38 jurisdictions and reported 36 restrictive measures passing or on track to pass, with the balance pending or unclear. (November 4, 2026.)
Ohio accounted for 21 measures in 18 municipalities, more than half the national total. The Christian Science Monitor's tally, based on the same sources, put at least 18 measures as outright or size-based bans, four as moratoriums, and ten as new zoning or other restrictions, with the rest advisory.
What kinds of measures passed
The form of the measure matters more than the headline, because each form lands on a different question in this guide.
| Form of measure | Examples (as reported Nov. 4 and 5, 2026) | Where it lands in this guide |
|---|---|---|
| Charter prohibition on new data centers | Edgewater, Florida (Amendment 4, about 77 percent in favor); Pataskala, Ohio | Question 01 (definition), Question 03 (a prohibition is not a pause) |
| Ban above a stated electric threshold | Sunbury, Ohio (25 MW, about 79 percent); Trenton, Ohio (about 80 percent); El Dorado and Emporia, Kansas ("high impact" facilities); Ottawa, Kansas (25 MW, pending) | Question 01 (intensity thresholds) |
| Ban above a stated floor area | North Berwick, Maine (25,000 square feet) | Question 01 |
| Zoning referendum on a specific rezoning | Wilmington, Ohio (four rezonings of rural residential sites to light industrial; about 80 percent voted to reject) | Question 02 (siting) and Question 06 (the record) |
| Temporary moratorium by vote | Peru, Wells, and Wiscasset, Maine (180 days or six months); Bloomington, Illinois (advisory, about 78 percent) | Question 03 |
| Vote to block a project under construction | Ashville, Ohio (over 80 percent) | Question 09 (vested rights and transition) |
| Voter-approval requirement for large projects | Janesville, Wisconsin (projects over $450 million at a former GM site) | Question 06 (who decides) |
| Conditions on tax abatements | Perry, Ohio (financial guarantees and noise limits as a condition of tax breaks, over 87 percent) | Questions 07 and 08 |
| Advisory votes | Joliet, Granite City, and four other Madison County, Illinois communities (opposition by wide margins); Downe Township, New Jersey | Question 04 (public participation) |
Two cautions. First, an advisory vote binds no one; a charter amendment binds the council until voters change it; a moratorium expires. Staff reports should name the instrument. Second, the Ohio measures turned in part on that state's referendum procedures for municipal zoning and township zoning actions, which do not exist in the same form everywhere. Counsel should confirm what a petition can and cannot reach in the jurisdiction's own state before anyone assumes a ballot route is available.
Recalls and candidate races
Data centers also moved from the measure column to the candidate column.
- In Minnesota, challengers who opposed proposed Google data centers won the mayor's race in Pine Island and council seats in Hermantown and Monticello; in Hermantown, both newcomers outpolled an incumbent who had voted to approve the project the previous week. (MPR News, November 4, 2026.)
- Piqua and Urbana, Ohio, both adopted bans and recalled officials who had supported projects, three city commissioners in Piqua and the mayor in Urbana. The mayor of Yukon, Oklahoma, and a council member in Mason, Michigan, also lost recall elections tied to data center positions. The Christian Science Monitor counted up to 30 data-center-related recall attempts in 2026.
- Data centers were a stated issue in statewide races in Ohio, Texas, Kansas, Wisconsin, and Florida, with candidates across parties taking positions on moratoria, ratepayer protection, siting, and tax incentives. In Florida, Governor-elect Byron Donalds campaigned on keeping the siting decision with cities and counties, on the principle that residential utility rates should not rise because of a hyperscale facility, and on state standards for how close facilities may be built to homes. Those positions track the structure the Legislature adopted in Chapter 2026-65, which left land use authority local and routed rate protection through the Public Service Commission. (Orlando Sentinel via GovTech, October 19, 2026; results reporting November 4 and 5.)
An NBC exit poll reported that 56 percent of voters called AI and data centers a "crucial" or "major" factor in their congressional vote. Polling before the election pointed the same direction: a May Gallup poll found about 70 percent of Americans opposed a data center in their area, and a July University of North Florida poll found 68 percent of Florida voters opposed one in theirs. For local officials the figures are a reason to expect attendance and questions at every hearing, not a finding about any project.
Florida since August
- Edgewater (Volusia County). The City Council adopted an ordinance prohibiting AI data centers in late October, effective immediately, as a bridge to Charter Amendment 4, which voters approved November 3 with about 77 percent in favor according to preliminary results. A charter prohibition cannot be repealed by a future council alone.
- Orange County. On September 15, commissioners signaled support for a temporary moratorium on large data centers and directed staff to study zoning districts, electric load, water, and noise. No ordinance had been adopted as of this edition; the item was expected to return in early December. Both candidates in the November mayoral runoff supported a moratorium.
- Lake County. The Board of County Commissioners enacted a 90-day pause on new data centers in September and in October directed staff to draft an ordinance requiring a conditional use permit, and therefore a commission vote, for any proposed facility.
- Osceola County. The County has not adopted a moratorium. It has indicated that it will time any policy work on large-scale data centers to the state data center study due in July 2027, so that local standards can reflect the state's findings. The existing code governs any application in the interim.
Florida local governments start from a clearer position than most. The Legislature addressed the large-load question in statute before the election. Chapter 2026-65 preserved local planning and land development authority, assigned ratepayer protection to the Public Service Commission through large-load tariffs, and added water-use review through the consumptive-use permit process. That is the separation of forums this guide recommends in Questions 05 and 08, and it means a Florida city or county answering the nine questions is working inside a framework the state has already drawn. The jurisdictions above reached different postures under the same statute, which is the point: the law leaves the decision local. The statutory framework did not change on November 3.
What a new governing body inherits
The order of operations changed. An official who campaigned on a pause, a ban, or a set of conditions takes office with existing rules, pending applications, prior approvals, and in some cases a moratorium already running. Converting a commitment into a lawful instrument requires knowing what is already there.
We recommend five steps in the first 30 days, before any new policy direction is proposed.
- Inventory pending and approved applications. For each: the applicable code at the time of filing, the stage reached, any vested rights or transition provisions, and the next decision deadline. A campaign promise does not change the law that applies to an application already in review.
- Read the existing moratorium, if there is one. Confirm its expiration date, its stated purpose and deliverables, the budget behind it, and what happens to covered applications when it ends. A pause adopted before the election with no funded work plan is the new body's problem now.
- Identify the instrument that matches the commitment. A moratorium, a code amendment, a conditional use requirement, a charter amendment, a utility tariff proceeding, and a tax-abatement policy are different tools with different authority, timelines, and reach. Several of the November measures combined them.
- Separate the local decision from the utility decision. Ratepayer protection was the dominant campaign theme. In most states the allocation of interconnection costs and the terms of large-load tariffs are decided by the utility and its regulator, not the land use body. The local record should say which findings belong to which forum.
- Publish what is nonexempt now. Transparency was the second theme. Several of the recall and challenger campaigns ran on undisclosed negotiations and development NDAs. The cure is a written records policy and an early project summary, which Question 04 describes.
A new governing body that completes those five steps will understand what it has before deciding what it wants. That is the neutral position this guide has recommended since August, and it is the position that lets a council explain its decision whichever way the decision goes.
Where should I start?
| Your situation | Start with | Then use |
|---|---|---|
| The code places data centers in a broad office, warehouse, or utility category | Questions 01 and 02 | A written classification and an assessment of whether existing definitions, intensity measures, and review criteria fit the proposed use |
| Residents raise concerns about utility costs, water, or sound | Questions 05 and 07 | Project-specific studies, the responsible agencies' findings, and locally justified performance standards |
| Residents cannot find or understand project information | Questions 04 and 06 | A nonexempt project summary, a records-law review, and a publication schedule coordinated with required deadlines |
| Officials are considering a temporary pause | Question 03 | An authority review and, if justified, a defined moratorium with a funded work plan and an adoption calendar |
| A newly elected body inherited a running moratorium or pending applications | "What a new governing body inherits," then Questions 03 and 09 | An inventory of applications, applicable law, expiration dates, and transition provisions |
| An application is imminent or already under review | Questions 04 and 06 | The rules applicable to that application, a coordinated completeness review, a master schedule, and an evidence index |
| An incentive or infrastructure agreement is being negotiated | Questions 07 and 08 | Separate local-budget and ratepayer analyses, documented assumptions, and enforceable commitments |
| An approved facility proposes equipment, load, or ownership changes | Question 09 | A review of the existing approval, applicable transition rules, and the authorized procedure for the particular change |
Review capacity is the neutral position
The August edition argued that review capacity enables a jurisdiction to make a deliberate, lawful choice. That still requires the code interpretation, technical studies, fiscal analysis, and public record to describe the same project. If those documents assume different buildout levels or operating conditions, decision makers are being asked to evaluate different projects at once.
We recommend a review system that gives applicants understandable requirements, gives residents access to nonexempt evidence, and gives staff a clear basis for findings. Public participation can reveal questions that deserve investigation. The final decision must still follow the governing approval criteria and applicable procedures.
Four tasks organize that work. A temporary pause is an option to evaluate within the first task, not a required starting point.
| Step | What it means | What capacity it requires |
|---|---|---|
| 1. Assess the rules | Review definitions, allowed locations, existing approvals, infrastructure information, and gaps in adopted criteria | Planning and legal review; an application inventory; a defined study plan if a lawful pause is justified |
| 2. Set measurable standards | Draft requirements tied to documented local effects and the jurisdiction's authority | Technical studies; stated measurement methods; feasible inspection and enforcement procedures |
| 3. Explain the process | Publish nonexempt project information and identify when and how the public can participate | A records-law procedure; coordinated notice and review calendars; a log of questions and responses |
| 4. Coordinate review | Assign responsibilities, reconcile inconsistent submissions, and maintain one decision record | A project manager; a shared issue log; qualified reviewers; tools appropriate to the actual review tasks |
A by-right process can provide strong protection when its standards address the use. A discretionary process needs clear criteria to support consistent decisions. A moratorium needs a defined purpose and work plan. The choice among these approaches should follow the identified regulatory gap and the authority available to address it. Process quality and policy outcome are separate things, and this guide evaluates only the first.
Policy snapshot at publication
November 2026
This dated snapshot provides context at publication; it is not a live tracker. The guide's substantive framework does not depend on these matters remaining in the same posture. Readers should consult current official materials before acting.
Local ballots. See "What voters decided" above. All results are preliminary until certified. Counts differ by tracker; cite the tracker and date.
Florida statute. Florida enacted Chapter 2026-65 in May 2026, with most provisions effective July 1. The law preserves local planning and land development powers granted by law for large-load customers. Its utility provisions use anticipated monthly peak demand of at least 50 MW at one location, measured over a 15-minute interval, with specific colocation and load-splitting rules. Covered public electric utilities were required to file tariffs for Public Service Commission approval by October 1 to address full service costs and protect other ratepayers from cost shifting and nonpayment risk. The filing requirement does not establish that every tariff has been approved.
Separate provisions govern consumptive water-use permits. A large-scale data center seeking an average allocation of at least 100,000 gallons per day must provide additional water-use information and a conservation plan. A hearing is required before approval of a large-scale data center's consumptive-use permit application; that hearing rule is not limited to the 100,000-gallon threshold. Water-permit modifications proposed by such a facility follow initial-application procedures. These provisions do not create a general local zoning hearing or reapplication requirement.
Florida local actions. See "Florida since August" above for Edgewater, Orange, Lake, and Osceola Counties.
Larimer County, Colorado. The County began a temporary moratorium on new data center land-use applications in unincorporated areas in January 2026 and extended it through February 2027. On October 27, 2026, it released draft regulations for public comment that would cap facilities at 30 MW (which the County describes as effectively excluding hyperscale facilities), require at least 80 percent renewable power, prohibit evaporative cooling, limit the use to its Industrial Heavy and Industrial Light zones, and require an air quality mitigation plan and pre- and post-construction noise studies. The drafts remained proposals when checked for this edition; work sessions and hearings had not been scheduled.
Moratorium activity. Moratorium activity deserves careful interpretation. In a fixed panel of 285 jurisdictions, Shovels reported that 98 of 349 data-center-related decisions during January through July 2026 involved moratorium activity, or 28.1 percent. The company's classification uses titles and descriptions of local actions. Its sample is not a national census, and moratorium-related activity can include consideration of a proposal that is later rejected. The figure should not be read as the share of U.S. projects halted. Separately, Fortune reported more than 125 active local moratoria in Ohio alone as of November 2026.
The national range. Within the nine-question framework, the examples that follow illustrate different policy choices and administrative practices. Their dates and legal status matter. An adopted ordinance, a proposed amendment, an applicant projection, and an election return should be identified separately when they appear in a staff report.
01 What exactly is the proposed use?
Start with the use classification. A code may place a proposal within office, warehouse, utility, or information-processing language that does not expressly address its equipment or intensity. Staff should explain the applicable classification and identify which project effects the existing standards actually cover.
A useful structure to evaluate is three levels: computing equipment accessory to another principal use; a data center as a principal use; and a larger or more intensive facility subject to additional requirements when a stated threshold is met. Anticipated peak electric demand in megawatts is one possible intensity measure. It measures power. Power density expresses that power relative to a defined basis, such as watts per square foot or kilowatts per rack. Other relevant measures may include generation capacity, floor area, cooling-water demand, and battery storage. Select thresholds for their relationship to the effects the jurisdiction is authorized to regulate. Explain how phases, co-located users, connected buildings, and conversions are counted so that equivalent proposals receive equivalent treatment.
Pair each category with a stated review path. A conditional use or special-exception process may be appropriate where authorized criteria call for site-specific findings. A by-right path may be appropriate where adopted standards adequately address the use. Neither label establishes the quality of the review by itself. The ordinance should identify the deciding authority, required findings, available conditions, and appeal route.
If an application arrives before a dedicated definition is adopted, the authorized official should classify it under the law applicable to that application. Put the interpretation in writing and obtain counsel's review where the classification or effect on existing rights is uncertain. A proposed code amendment should not be treated as though it were already in force.
Policy snapshot cross-reference. Florida's utility definition illustrates why statutory thresholds need to be read carefully. It aggregates qualifying co-located users at one location and prohibits dividing that location's load to avoid classification. It does not aggregate every location owned by the same customer. A local zoning definition needs its own authority and rationale.
What survives challenge. The classification record should identify the observable facts, the applicable definition, the treatment of phases, and the reason for the selected review path.
In practice. Before adopting a definition, test it against an in-house server room, a converted warehouse, a small colocation facility, a phased campus, and a mixed campus with on-site generation. Record where the draft produces uncertainty and revise those provisions before using them in an application review.
02 Where can the use fit, and under what review path?
Siting combines land use compatibility with the location and capacity of electric, water, wastewater, road, fiber, and emergency-response systems. A parcel near transmission may reduce the need for new lines while remaining unsuitable for other reasons. Staff should evaluate infrastructure and surrounding uses together.
Assemble four sets of information: the plan designation, zoning district, and review path; nearby uses and sensitive receptors, environmental constraints, and cumulative development; infrastructure capacity and the authority responsible for each system; and the site's role in the jurisdiction's industrial, housing, agricultural, or conservation plans. Distinguish mapped infrastructure from confirmed service capacity.
Setbacks should have a documented purpose and a defined measurement method. A jurisdiction may evaluate separation distances alongside equipment enclosure, building orientation, sound limits, and site design. The appropriate distance depends on the regulated effect and local evidence. This guide does not prescribe a universal 1,000-foot buffer or assume that a cooling-system label establishes acceptable performance.
Counterweights. Two Virginia examples show different approaches. Loudoun County's March 2025 amendments require special-exception review for data centers in three named industrial districts, with transition provisions for certain earlier applications. Fairfax County's September 2024 amendment retains different review paths by district and project characteristics while adding equipment, sound-study, and separation requirements. Fairfax generally requires 200 feet between a data center building and residential property or districts; its ground-level equipment rule generally uses 300 feet or separation by the principal building, with lesser distances available through special-exception approval. Those are local standards, not national defaults.
What survives challenge. Explain how the selected districts, distances, and procedures address locally regulated effects. Counsel should review the relationship to state utility and environmental authority, as well as any transition provisions for pending or existing approvals.
In practice. Prepare a constraints and capacity map for intake and review, and publish the nonexempt planning information. Identify data dates and limitations. The map should help reviewers ask better questions; utility proximity alone does not demonstrate service availability or land use compatibility.
03 Does the jurisdiction need a temporary pause?
A moratorium is an interim tool that may give a jurisdiction time to address a defined regulatory gap. We recommend considering it only after identifying the legal authority, the work that cannot reasonably be completed under the existing process, and the effect on pending applications. A pause without a funded work plan leaves the same questions unresolved at its expiration.
Before recommending a moratorium, document its purpose, coverage, duration, and proposed treatment of pending or vested applications. Identify the specific study products: for example, a land inventory, a utility-capacity assessment, revised use definitions, or enforceable performance standards. Assign staff and outside expertise, estimate the budget, and schedule drafting, public participation, required notices, and adoption. Counsel should confirm the authority and procedures for the particular jurisdiction.
Work backward from the expiration date. Leave enough time for the legally required notice and hearing process, revisions after public review, and staff training. Report progress at scheduled public meetings. Any proposed extension needs its own legal review and justification.
Counterweights. Larimer County, Colorado, illustrates a documented study process. It began a temporary moratorium on new data center land-use applications in unincorporated areas in January 2026 and extended it through February 2027. The County identified definitions, infrastructure, resource demands, and compatibility as subjects for its work, and its October 2026 draft regulations (described in the policy snapshot) are the deliverable. The drafts remained proposals when checked for this edition.
What survives challenge. The record should connect the pause to a specific planning purpose and show progress toward the stated deliverables. It should also explain which applications are covered, what exceptions apply, and how staff will proceed when the pause ends.
In practice. Adopt the work plan with the moratorium, if one is used. Name the person responsible for each deliverable and identify the meeting at which the governing body will review progress.
04 What must the applicant disclose before review begins?
A completeness checklist should identify the information required by the applicable review criteria. For a substantial campus, relevant submissions may include ownership and responsibility for conditions; buildings, phases, parcels, and maximum buildout; electric demand and interconnection status; cooling design and water sources; generators, batteries, fuel, and air-permit status; sound modeling; emergency response and traffic; fiscal assumptions; and operations or closure information. Distinguish required application materials from optional information and later technical-review questions.
Label each utility statement by its actual stage. An interconnection request establishes that a request was made; it does not establish that a study is complete, capacity is available, upgrades are scheduled, or costs are allocated. The project record should identify the completed stage, the outstanding work, and the party responsible for confirming each item.
Public records and confidentiality. We recommend a written policy requiring counsel to review proposed confidentiality terms before staff accept them. Identify the legal basis for withholding particular records, the custodian, and the release trigger. A jurisdiction may consider a policy declining development NDAs where consistent with its authority and obligations. Such a policy does not override statutory confidentiality. Publish nonexempt material and evaluate whether a redacted document or public summary can convey the relevant information.
Time for public review. Establish a publication schedule that gives residents a useful opportunity to examine nonexempt materials and raise questions. Coordinate it with statutory deadlines and adopted procedures. The project summary should identify the applicant, property, requested approval, proposed buildout, review criteria, responsible agencies, and participation opportunities. Label unresolved information clearly and update the summary as the record develops.
Policy snapshot cross-reference. Florida's 2026 amendment to section 288.075 removes the optional additional 12-month extension for qualifying data-center economic-development confidentiality. The initial statutory protection, earlier release triggers, and other applicable exemptions remain. It does not make every project document public or create a blanket prohibition on NDAs.
Keep completeness and merits review distinct. Missing required information may affect completeness under the governing procedure; disagreement about an assumption or the adequacy of mitigation may instead require technical review. Staff should identify the applicable requirement and the action needed to resolve the issue.
What survives challenge. A useful intake record consists of a dated completeness determination, an inventory of submissions, and a separate issue log, with each required item mapped to an adopted review criterion and applied consistently.
In practice. An optional workshop or internal review step should not be assumed to suspend a statutory clock or create an additional completeness requirement. Where mandatory review clocks apply, make the completeness determination the earliest milestone the clock allows.
05 What are this project's effects and benefits?
Generic industry averages provide context. A project finding needs evidence about the proposed facility, its location, and its operating assumptions. Separate construction from operations, initial development from full buildout, and proposed mitigation from a binding obligation. Ask how each material benefit or impact will be checked.
Organize the analysis around the questions that can affect the decision. For many proposals, staff will need to examine electric demand and cost allocation, water supply and cooling, sound, emergency equipment, employment, and local fiscal effects. Explain which agency controls each issue and which findings belong to the local land use decision.
Electric service and ratepayers. Request documentation of demand by phase, interconnection status, planned upgrades, applicable tariffs, and the allocation of costs and nonpayment risk. Identify who is responsible for each conclusion. Where residential-rate effects are material, seek the utility's or regulator's supported analysis and disclose its assumptions. Staff should not convert a developer's projection into a utility finding or assume that a service commitment resolves every land use issue. Ratepayer cost was the most repeated theme in the November campaigns; it is also the issue the land use body usually has the least authority over. The record should say so.
Water. Berkeley Lab's national energy-use report distinguishes water used directly by data centers from water associated with electricity generation. Local review should identify which measure is being discussed. Request average and peak demand, withdrawal and consumption, water source, cooling configuration, seasonal operating assumptions, and drought response. Evaluate any claimed savings against a stated baseline. A closed-loop system or a non-potable supply label alone does not quantify the project's total water demand.
Sound and air. Sound analysis should identify equipment, operating combinations, measurement locations, and relevant day and night conditions. Federal air requirements may apply to stationary engines and other generating equipment, alongside applicable state or local requirements. Identify the equipment and permitting agency, and distinguish air compliance from the separate land use questions under review.
Benefits. Benefits should receive the same scrutiny. Separate construction jobs from permanent positions and identify the expected duration of each category. Reconcile tax claims with exemptions, assessment practices, depreciation, revenue recipients, and public costs. An applicant projection should remain labeled as such until the responsible reviewer has evaluated it.
What survives challenge. For each disputed issue, record the submitted evidence, the reviewing agency's conclusion, the applicable criterion, and the basis for the recommended finding. Explain how material conflicting evidence was addressed.
In practice. When a modeled assumption supports an approval, decide whether it should become a lawful condition, a monitoring requirement, or a disclosed uncertainty. State who will verify it and what happens if the operating facility differs materially from the reviewed case.
06 Who reviews the application, in what sequence, and what is the record?
The review file should let another reader trace the decision: what was requested, what evidence was submitted, which agency had authority, how conflicting information was addressed, what findings were adopted, and how continuing obligations will be verified. Build that file throughout review and publish the nonexempt portions at useful milestones.
Assign one project manager to coordinate planning, legal, utilities, engineering, fire, environmental review, finance, assessment, economic development, and records staff as needed. Identify the actual decision authority for each issue. Retain independent technical expertise when existing staff cannot evaluate a material study, using the applicable procurement and cost-recovery procedures.
We recommend the following sequence, adapted to the jurisdiction's mandatory steps and deadlines:
- Legal and procedural intake: identify applicable rules, pending rights, records-law issues, conflicts, and decision deadlines.
- Publish a nonexempt project summary when sufficient information is available, identifying what is known and what remains unresolved.
- Complete the required completeness review within the governing timeframe. Record missing required submissions separately from disputed technical conclusions.
- Provide public participation through the required process and any authorized additional opportunities. An optional early workshop may be useful; its timing should not be assumed to extend a review clock.
- Conduct coordinated technical review and any necessary peer review, using one issue log and consistent project assumptions.
- Publish the nonexempt staff report and evidence index in accordance with required notice and hearing procedures.
- Hold the required hearing or take the authorized administrative action, and document findings under the applicable criteria.
- Transfer conditions and reporting obligations to the departments responsible for inspection, monitoring, finance, and enforcement.
If a workshop is used, explain its purpose and how comments will enter the review record. Counsel should identify any meeting, notice, recordkeeping, or quasi-judicial restrictions that apply. A workshop should not become an undocumented negotiation or substitute for the required hearing.
Two disciplines protect the record. Maintain an evidence index linking each criterion to the relevant submission, agency review, public information, staff analysis, finding, and condition. Use status labels consistently: adopted requirement, proposed change, applicant projection, verified fact, or unresolved issue. Update the index when plans or assumptions change.
Decision makers should obtain counsel's guidance on conflicts, prior public statements, ex parte communications, disclosure, and recusal where relevant. The evidentiary standard depends on the jurisdiction and type of decision. Public support or opposition should not be described as satisfying a technical criterion without the evidence that criterion requires.
Counterweights. A hypothetical coordination problem illustrates the need for a shared record. Suppose an applicant proposes a first phase using 40 MW and a full campus using 120 MW. The sound study addresses the first phase, while the fiscal estimate assumes full buildout. Before staff compare benefits and impacts, they should reconcile the reviewed development scope or explain which later approvals and studies will address the remaining phases. This example describes no actual project.
What survives challenge. Use the jurisdiction's actual evidentiary standard and hearing rules, resolve material contrary evidence on the record, and make sure the findings can be located in the file rather than reconstructed from memory.
In practice. The staff report should state exactly what the proposed decision would authorize, deny, or leave for later review. It should also identify unresolved material questions and explain how public submissions affected the analysis.
07 Which conditions or agreements make the decision operational?
A workable condition identifies the regulated activity, the measurable requirement, the method and timing of verification, the reporting recipient, the response to noncompliance, and the responsible party. Counsel and technical reviewers should confirm that each element is authorized and practical to administer.
We recommend placing recurring requirements in the code when the jurisdiction has the authority and evidence to do so. Reserve site-specific conditions for circumstances the adopted standards leave to individual review. Explain the reason for each condition and avoid repeating an existing rule without clarifying responsibility or enforcement.
The following table identifies matters to evaluate when drafting standards. Numeric limits and design requirements must come from the applicable code or a locally supported adoption process.
| Subject | Requirement to define | Evidence and verification |
|---|---|---|
| Sound | Applicable sound limits, measurement locations, operating conditions, and day or night distinctions | Baseline study; modeled full operating case; commissioning tests; a defined retesting and complaint procedure |
| Equipment | Equipment enclosure, screening, layout, and any authorized generator-testing restrictions | Approved design and as-built verification; operating records; coordination with air-permit requirements |
| Water | Authorized water-use limits, source requirements, conservation measures, and drought triggers | Documented average and peak demand; metering where required; reporting and comparison with permit conditions |
| Setbacks | Locally justified separation distances and a clear method for measuring them | Approved site plan; documented treatment of equipment, sensitive receptors, and proposed expansions |
| Power | The demand and infrastructure assumptions that support the approval, and any authorized phase conditions | Written confirmation from the responsible utility or agency at the specified project milestones |
| Phasing | Infrastructure or mitigation that must be completed before an authorized development or occupancy milestone | A named approving department and documentary evidence for each required milestone |
| Closure | Any authorized decommissioning duties, cost-estimate updates, and financial assurance | A responsible owner; an accepted estimate and security instrument; review triggers and release criteria |
Keep existing conditions, applicant projections, external benchmarks, and binding limits separate in the approval. If a number supports a finding, say whether it is an enforceable ceiling, a monitoring benchmark, or explanatory context.
Counterweights. Chandler, Arizona, provides a concrete example of continuing verification. Its ordinance requires an initial sound study when the certificate of occupancy or completion is issued, whichever comes first, followed by annual studies during peak equipment operation for five years after the initial study. Fairfax also requires sound studies before site-plan approval and before the nonresidential use permit. Larimer County's October 2026 draft would require pre- and post-construction studies by a professional sound engineer. These are examples of verification schedules, not a substitute for selecting locally appropriate limits.
Name the instrument. Identify the legal instrument for each commitment. A zoning condition, development agreement, utility agreement, incentive agreement, infrastructure reimbursement agreement, and private community agreement can have different parties, authority, enforcement rights, and obligations after transfer. The nonexempt public record should identify the approving authority, trigger, responsible party, financial terms where disclosable, and enforcement mechanism. A promised benefit does not resolve an unmet approval criterion by itself.
Requirements should rest on statutory and code authority and address identified project effects. When a demand for property, money, or improvements constitutes an exaction, counsel should evaluate the governing nexus and proportionality requirements. In Sheetz v. County of El Dorado (2024), the Supreme Court rejected a categorical exemption for legislatively imposed permit conditions. The decision does not establish that every zoning or operating standard is an exaction.
What survives challenge. Before adoption, connect each proposed condition to the criterion and finding it implements. Specify how the jurisdiction will document compliance, respond to a violation, and handle a change in the responsible owner.
In practice. Ask the inspector and enforcement attorney to walk through a compliance failure, a proposed equipment change, and an ownership transfer using the draft approval. Revise any obligation whose responsible party, evidence, or enforcement path remains unclear.
08 What is the likely local fiscal result?
A fiscal finding should distinguish announced investment, investment located in the jurisdiction, taxable value after applicable exclusions and incentives, revenue received by the deciding jurisdiction, and the net effect after public costs. Keep three analyses separate: the jurisdiction's budget, utility and ratepayer effects, and broader regional economic activity. A favorable result in one does not establish a favorable result in another.
The ratepayer analysis should identify the applicable tariff or agreement, the infrastructure costs assigned to the customer, any remaining exposure, and the authority that determines the allocation. Reconcile it with the local fiscal model without treating utility costs as though they were county or municipal tax revenues.
The illustrative arithmetic. The following hypothetical shows why the investment announcement is an insufficient basis for a revenue estimate. Assume $5 billion in investment, a 1 percent local property-tax rate, and the simplified tax treatments shown below. These assumptions describe no real project, tax system, or jurisdiction.
| Line | Headline calculation | Illustrative mechanics |
|---|---|---|
| Announced investment | $5 billion | $5 billion |
| Land and buildings | Included in total | $1.0 billion × 70% taxable = $700 million |
| Equipment | Included in total | $4.0 billion × 20% taxable × 50% assessment factor = $400 million |
| Gross property tax at 1% | $50 million a year | ($700 million + $400 million) × 1% = $11 million a year |
| Project-linked public costs | Not included | $3 million a year |
| Net local fiscal effect | Not established | $11 million − $3 million = $8 million a year |
The $8 million result is the hypothetical year's net effect before indirect effects and further risk adjustment. A real analysis should model asset cohorts, assessment dates, exemptions, recipients, phasing, recurring service costs, and annualized capital costs.
Counterweights. Local rules change the result: Loudoun County publishes a specific assessment schedule for data center equipment, while Indiana's incentive program can affect sales and use taxes and may involve a separate local personal-property exemption. These taxes and exemptions must be modeled separately.
What survives challenge. Show the assumptions and source dates, then test delay, reduced buildout, faster equipment depreciation, larger exemptions, and early closure. Identify who reviewed the model and which assumptions remain applicant estimates.
In practice. Have finance staff prepare a concise public assumptions summary, subject to applicable disclosure rules, and retain the supporting model. The summary should explain the revenue recipients, relevant years, principal exemptions, public costs, and downside cases so readers can understand what the estimate does and does not represent.
09 What happens after approval, expansion, transfer, or closure?
The operating facility may change as equipment, tenants, ownership, cooling systems, and load change. The original approval should identify continuing obligations and the procedures applicable to later proposals. Establish the compliance file before construction so that the monitoring program can be carried out by the staff who inherit it.
Depending on the applicable approval, the program may include a preconstruction meeting, final condition matrix, as-built certification, commissioning tests, periodic reports, a complaint channel, inspections, ownership notifications, and closure requirements. Publish nonexempt results and explain who is responsible for investigating a reported problem. Each obligation needs authority, staffing, and a practical verification method.
The material-change screen. Define material-change review in the applicable code or approval. Relevant changes may involve electric demand, campus area, cooling, water use, generation, storage, sound sources, emergency assumptions, infrastructure responsibilities, or closure security. The authorized response may differ by type and scale of change. New equipment, an ownership transfer, or a revised plan does not by itself establish that a wholly new local application is required. Florida's initial-application procedure for certain data center modifications concerns consumptive water-use permits; it is not a general zoning rule.
Existing approvals. Existing approvals require an explicit transition analysis. Review the governing law, the original approval, vested or nonconforming rights where applicable, and the proposed change before determining whether new standards apply. Do not assume that an expansion or transfer automatically subjects the entire facility, or even the changed portion, to every subsequently adopted requirement.
Counterweights. Loudoun's 2025 amendments illustrate the importance of transition provisions: certain earlier applications may continue without the new special-exception requirement under the County's adopted resolution. Chandler illustrates a separate issue, ongoing verification after construction. A transition rule and a compliance program solve different administrative problems.
What survives challenge. Assign continuing obligations to a responsible department, specify funding and access where authorized, and identify how successor responsibilities will be documented. Closure security, if required, should have a defined calculation, update process, acceptable instrument, and release procedure.
In practice. For each continuing obligation, identify the responsible party, the reporting deadline, and the action staff should take if the operator fails to comply. Keep those assignments with the approval and the inspection record.
A readiness sequence
The first 72 hours after a serious inquiry. These are suggested internal coordination targets, not legal review deadlines. Adjust them to staffing, the actual request, and any applicable statutory clock.
- Within 24 hours, assign a project manager and counsel contact, open a project file, record the request and any confidentiality claim, and identify the rules potentially applicable. Avoid assurances about approval, utility capacity, revenue, or vested rights before the responsible review. An inquiry alone should not be assumed to establish entitlement.
- Within 48 hours, convene the necessary reviewers, identify who has authority over each issue, list the information already available, and prepare a coordinated response or request for required information.
- Within 72 hours, provide the known review path and next steps, identify unresolved procedural questions, and establish the master schedule and issue log. Set publication and participation milestones that fit applicable requirements. Keep the jurisdiction's formal completeness and decision deadlines visible.
The first 30 days after an election. See "What a new governing body inherits" above. The inventory of pending applications, the reading of any running moratorium, and the matching of commitments to instruments should be complete before the new body's first policy discussion on the subject.
A 90-day planning sequence. For jurisdictions preparing standards without an active application, the following is a suggested work program. It does not require a moratorium or promise ordinance adoption within 90 days. If a pause is adopted, its legal duration and required procedures govern.
| Days | Work |
|---|---|
| 1 to 15 | Review authority, current definitions, pending and existing approvals, confidentiality rules, and procedural deadlines. Identify the specific gaps to address. |
| 16 to 30 | Inventory relevant land and infrastructure information; identify data limitations; assign reviewers; arrange any necessary outside technical support. |
| 31 to 50 | Draft use definitions and proposed review paths. Develop locally supported performance standards, application requirements, and fiscal and utility-analysis templates. |
| 51 to 70 | Review siting criteria, transition provisions, and implementation responsibilities. Invite public input on the proposed standards using the required process. |
| 71 to 90 | Test the draft against hypothetical facilities; revise unclear provisions; prepare staff training and an adoption schedule that satisfies notice and hearing requirements. |
Peer exchange. A conversation with counterpart staff can help identify practical issues in utility coordination, public participation, staffing, and post-approval monitoring. Use peer experience to develop questions for the local review. Verify any suggested ordinance or procedure against the jurisdiction's own authority and circumstances.
Where AI-assisted systems fit
Our position from August stands after the election: defined support tasks under professional supervision. Those tasks include checking submissions against a published checklist, locating relevant code provisions, comparing numbers across revisions, organizing evidence, tracking assignments, and drafting summaries from approved source material. These tasks should be defined and tested before deployment. A system that extracts a stated sound level or water-demand figure has not independently validated the engineering analysis behind it.
One task has become more urgent. A new governing body that needs an inventory of pending applications, applicable code at filing, and expiration dates across dozens of files is doing document review at scale. That is a defined support task. The findings drawn from the inventory remain the staff's and counsel's.
Professional reviewers remain responsible for source verification, legal interpretation, engineering conclusions, findings, and the decision. Require traceable citations, human validation, version control, and approved handling of confidential material.
The larger lesson
Data centers are the immediate subject, but the administrative lesson is broader. New infrastructure-heavy uses arrive before codes, staffing, and interagency procedures are ready, and the next one, whether battery storage, hydrogen, or something not yet named, will not announce itself either. Officials who take office after an election inherit existing rules, pending applications, and commitments made under them. A review system that separates the stable questions from the volatile project, policy, and election facts lets a new governing body understand what it has inherited before proposing a new direction, and produces decisions that can be explained whatever that direction turns out to be.
Conclusion
A useful data center review gives decision makers a consistent description of the project, evidence tied to the applicable criteria, a clear account of public questions, and obligations that staff can administer after approval. Build that capacity before committing to an outcome, so the decision follows the applicable rules and evidence. Public participation improves the opportunity to identify and address concerns; it does not guarantee agreement. The November results show communities using every lawful outcome this guide describes, from charter prohibitions to conditioned approvals. The final record should explain the lawful decision and identify who is responsible for carrying it out.
Frequently asked questions
Did voters ban data centers in the 2026 midterms? In most of the roughly 40 local measures decided November 3, 2026, voters approved some restriction: outright or size-based bans, temporary moratoria, zoning reversals, or advisory opposition. The measures bind differently. A charter prohibition stands until voters change it; a moratorium expires; an advisory vote binds no one. Results were unofficial as of this edition.
What is a "25 megawatt" data center ban? Several measures and ordinances use anticipated electric demand as the trigger for a ban or heightened review, with 25 MW the most common figure in November 2026. The number has to be paired with a measurement method, a point in time, and a footprint rule (building, parcel, campus, co-located tenants) to be administrable.
Can a city or county stop a data center that already has permits? That depends on state vesting law and the text of the new rule. A ban or moratorium adopted after permits issue may not reach the permitted project. Counsel should answer the question for the specific project in writing.
Does a moratorium require a work plan? Not always by law, but in practice a pause without funded deliverables and an adoption calendar leaves the same gap at expiration. Larimer County, Colorado's January 2026 moratorium and October 2026 draft regulations illustrate a documented process.
Who decides whether a data center raises electricity rates? In most states, the utility and its regulator decide the terms of large-load service and the allocation of interconnection costs, not the local land use body. Florida's Chapter 2026-65 required covered public utilities to file large-load tariffs for Public Service Commission approval by October 1, 2026. The local record should identify which findings belong to which forum.
What should newly elected officials do first? Inventory pending and approved applications and the law that applied when they were filed, read any running moratorium, match each campaign commitment to a lawful instrument, separate the local decision from the utility decision, and publish what is nonexempt.
About SwiftGov
SwiftGov develops software to support local government permit review, including identifying applicable requirements and organizing review work. This guide offers a framework for evaluating complex proposals while retaining professional responsibility for findings and decisions. Product capabilities and suitability should be assessed against the jurisdiction's actual workflow. Learn more about SwiftGov
A note on dates. Laws, local examples, and source status were reviewed for the August 21, 2026 edition and re-reviewed for this November 2026 update. Election results are unofficial until certified. Confirm current requirements before applying an example to a particular project. Recommendations in this guide are the authors' proposed practices unless an identified source establishes a legal requirement.
Related
- The 21st Century ROAD to Housing Act: What Public Law 119-101 Actually Requires of Local Government
- Florida's Permitting Reset: HB 803, HB 927, and the New Operating Discipline for Local Government
- SwiftGov product overview
- Hernando County case study
Selected sources
November 2026 election results (all preliminary; added this edition)
- Volusia County Supervisor of Elections, November 3, 2026 General Election. City of Edgewater Municipal Referenda, Amendment 4, Prohibition on New Data Centers. Official results
- Forbes, "Here's Where Voters Are Rejecting Data Centers On Midterm Ballots (Full List)." Zachary Folk, November 4, 2026. State-by-state list drawn from Ballotpedia and U.S. Data Center Map. Article
- Fortune, "Ohioans overwhelmingly oppose data centers. 21 ballot measures just put their ire to the test." November 4, 2026. Ohio measures, ICAPP/SurveyUSA poll, and active-moratorium count. Article
- The Christian Science Monitor, "Voters sent a resounding message against data centers." November 5, 2026. Classification of measures by type; recall elections; state races. Article
- The Policy Circle, "2026 Data Center Ballot Results: What Comes Next?" November 4, 2026. Ballotpedia count of 41 measures in 10 states; Edgewater, Sunbury, Bloomington, and Joliet margins. Article
- RTO Insider, "2026 Midterms: Data Centers Lose Big in Local Referenda." Vincent Gabrielle, November 4, 2026. Article
- MPR News, "Data center backlash ousts incumbents in some Minnesota towns." November 4, 2026. Pine Island, Hermantown, and Monticello results. Article
- TIME, "How AI Backlash Shaped the 2026 Midterms." November 4, 2026. NBC exit poll figure; state races; industry spending. Article
- Data Centers on the Ballot (Redbud Consulting). Live tracker; methodology notes on "restrict/allow" coding and count completion. Tracker
- American Legislative Exchange Council, "After a Rebuke at the Ballot Box, What's Next for State Data Center Policy?" November 2026. Industry-aligned analysis citing the Data Centers on the Ballot count. Article
- Orlando Sentinel via GovTech, "How Data Centers Are Impacting Florida's Political Campaigns." October 19, 2026. Lake, Orange, and Osceola County actions; gubernatorial candidate positions; UNF poll. Article
- Central Florida Public Media, "Orange County plans a moratorium on AI data centers." September 15, 2026. Article
- FOX 35 Orlando, "Edgewater approves ban on AI data centers as Orange County weighs moratorium." Late October 2026. Edgewater council ordinance as bridge to Charter Amendment 4. Article
- Larimer County, "Feedback needed for draft Larimer County data center regulations." October 27, 2026. Draft 30 MW cap, renewable power, cooling, zoning, air, and noise provisions. Notice; Draft regulations
Carried forward from the August 2026 edition
- Shovels, "Data Center Moratoriums Went From Rare to Routine in a Year." September 22, 2026. Methodology and January to July comparison for a fixed panel of 285 jurisdictions; 98 of 349 data-center-related decisions involved moratorium activity in 2026. Analysis and methodology
- Florida, Chapter 2026-65, Laws of Florida, CS/CS/SB 484. Sections 1 and 3; sections 163.326 and 366.043, Florida Statutes. Local planning authority, the single-location peak-load definition, colocation, load splitting, and covered public-utility tariff requirements. Most provisions effective July 1, 2026. Enacted law; Official legislative history
- Florida Statutes, sections 373.262 and 373.239. 2026 edition. Section 373.262(4) addresses additional information and hearings for consumptive-use permits; section 373.239(2) addresses modifications. Section 373.262; Section 373.239
- Florida Statutes, section 288.075. 2026 edition, subsection (2)(a). Qualifying economic-development confidentiality and the exclusion of data-center information from the optional additional 12-month extension. Section 288.075
- Loudoun County, Data Center Standards and Locations Phase 1. CPAM-2024-0001 and ZOAM-2024-0001, adopted March 18, 2025, with the accompanying grandfathering resolution. Adopted amendments and transition provisions
- Fairfax County, adopted Data Centers Zoning Ordinance Amendment. Ordinances ZO 112.1-2024-9 and ZO 112.2-2024-8, adopted September 10, 2024, effective September 11. Section 4102.6.A(1), (4), and (6). Adoption record; Adopted ordinance
- Larimer County, Temporary Moratorium on Data Center Facilities. Official record of the January 27, 2026 pause and July extension through February 2027. Moratorium project record
- Shehabi and colleagues, 2024 United States Data Center Energy Usage Report. Lawrence Berkeley National Laboratory, December 2024, LBNL-2001637. Full report
- U.S. Environmental Protection Agency, Clean Air Act Resources for Data Centers. EPA regulatory resources
- City of Chandler, Ordinance No. 5033. Section 35-2214(4) to (7). Effective January 5, 2023. Ordinance text; City explanation
- Sheetz v. County of El Dorado, 601 U.S. 267. U.S. Supreme Court, April 12, 2024. Supreme Court opinion
- Loudoun County, Business Personal Property Tax Assessment Schedules. Schedule effective January 1, 2026. Official assessment schedules
- Indiana Economic Development Corporation, Data Center Sales Tax Exemption. Program overview
- SwiftGov product overview. Published capabilities are not independent verification of performance for a particular application type. SwiftGov official product information
- Swiftbuild, Hernando County case study. Vendor-published case study reporting residential zoning-review results. The guide does not transfer those results to data center applications. Hernando County case study
Disclaimer
This guide is an educational resource for local government readers. It does not provide legal advice or recommend an outcome for a particular project. Consult the jurisdiction's counsel and qualified technical reviewers on applicable authority, procedures, rights, studies, conditions, and enforcement.