New Kent’s two-year data-center moratorium proposal failed. What happens next?

If you were hoping New Kent would put data centers on hold for two years, Tuesday’s vote was a disappointment. If you’re now wondering whether that means a developer just got permission to build one, take a breath. That is not what the Board voted on.

The distinction matters, particularly when you’re trying to understand what could change near your home or business without taking up municipal procedure as a second occupation. The moratorium proposal failed. The proposed development rules are still being worked on. Those two facts leave a much more useful question than who won the morning: what happens in the meantime?

At the September 29 work session, the motion to start a two-year moratorium amendment failed with two votes for and three against. Thomas Evelyn, John Moyer and Amy Pearson voted no; Ron Stiers and Jordan Stewart voted yes. The roll call is in the county’s recording [38:38]. The New Kent–Charles City Chronicle also reported the result.

I worked through the revised packet, the recording’s timestamped transcript and the governor’s written order for this follow-up. The picture is more complicated than a red NO or a green YES. It is also more useful. Here is what changed, what did not, and where I would keep my attention next.

The Board declined to start a moratorium amendment

Resolution R-41-26 would have initiated a zoning-ordinance amendment and sent the proposed moratorium to the Planning Commission for review and a public hearing. A later adoption decision would still have been needed. Tuesday was a vote on starting that process, not the final switch that would have turned a two-year prohibition on.

That makes the defeat consequential without making it a construction permit. The Board declined this route toward a formal pause. It did not use this motion to approve a particular campus, building or developer.

There was another important update: planning staff said [40:37] there were no pending data-center applications as of September 29. That gives residents a newer checkpoint than the July notice still displayed on the county’s Planning and Zoning page. It does not tell us that nobody is talking privately about land or preparing a proposal. It tells us what staff reported about the application queue that day.

The county’s July policy preference remains an important part of the background: the Board had asked that applications not be filed or advanced while standards were developed. In Tuesday’s discussion, an exchange about an existing moratorium was clarified as the Board’s stated policy. I would keep those descriptions separate. An expressed preference and an adopted ordinance are different things, and residents should not have to guess which protection someone means.

Both sides talked about time and public participation

Pearson’s explanation [33:25] emphasized considering proposals individually, hearing constituents with different views, the possibility of a broader tax base and waiting for the state’s framework. She also objected to making a decision extending beyond this Board’s term. Stewart argued that two years was a reasonable period for government to work through the issues and that a moratorium would not remove the public from the process.

Those arguments deserve to be understood on their own terms. Someone worried about irreversible development may see time as a protection. Someone who wants to evaluate future proposals may see a blanket pause as closing off choices before their details are known. That is a real policy disagreement. A vote tally cannot settle it for us.

I would also be careful about turning one supervisor’s explanation into three supervisors’ motives. The recording establishes who voted which way. It does not give us permission to fill in every reason behind every vote.

The fiscal question deserves the same discipline. A larger tax base is a reason to examine a proposal carefully; it is not a project-specific savings estimate. For a business owner paying local taxes, the useful comparison would be expected revenue against infrastructure, service and oversight costs, including a slower buildout than the developer hopes for. A spreadsheet can accommodate that possibility. A campaign slogan generally struggles.

Waiting for Richmond does not finish New Kent’s rules

The next stretch of the calendar matters. Staff recommended [1:07:50] allowing time to consider the state’s work and suggested public hearings no earlier than February. That was a tentative timetable, not an advertised hearing date. The Board also deleted the agenda item that would have authorized a 30-day citizen-review period. Residents should not be told that particular formal window opened on Tuesday.

Governor Abigail Spanberger’s Executive Order 22, signed September 18, directs an initial planning and community-engagement toolkit within 120 days. That points to mid-January. The meeting discussion also mentioned mid-November before returning to January and roughly four months. I’m using the written order for the deadline rather than turning the earlier estimate into a promise.

The toolkit is supposed to help communities evaluate proposed projects and their impacts. The order also directs work on noise and backup generation. Separately, the governor’s announcement includes measures proposed for the 2027 legislative session. An executive directive, a future toolkit and a proposal that needs legislation are not all the same stage of completion.

There is a sensible reason to compare local drafting with new state guidance. It could prevent conflicting requirements or identify protections the county has missed. But waiting productively takes more than putting a month on a slide. I would want the county to explain what staff will keep developing, what specifically depends on the state and how residents will see the next version.

Most of all, I would want a plain-English answer to this: if an application arrives before the new ordinance is adopted, what happens to it? Which existing provisions apply, what can staff accept or process, and when does the public hear about it? That is a question for the county’s planning and legal staff to answer in the public record. A failed moratorium motion, by itself, does not supply the answer.

For anyone trying to plan around this debate, that explanation would be more reassuring than another broad assurance that the matter is under review. It would describe the actual procedure during the interval, including its limits.

The question I would keep: what happens after the letter?

Near the end of the presentation, Stewart asked about enforcement [1:12:57] when a facility fails to comply, using generator noise as an example. Staff discussed an initial opportunity to correct a violation, work on civil penalties and a process for conditional-use-permit revocation. Those explanations describe possible enforcement steps, not a guarantee that a noisy facility would immediately shut down.

This is where the discussion becomes tangible. Imagine a future facility has been operating for six months and nearby residents begin reporting a persistent nighttime sound. That is a hypothetical, not a claim about an existing New Kent data center. The test is whether the eventual rules make it clear who investigates, how the sound is measured, when a result is published and what happens if the problem continues.

The draft contains follow-up sound studies, including a study following a zoning-administrator request, and calls for corrective measures when standards are exceeded. That is worth having. I would still want the next version to make the route from complaint to correction easy to follow. A resident should not need to become an acoustics specialist to find out whether the county has acted.

There is also a detail worth reading carefully: the proposed sound limits use the existing ambient level or 55 dBA and 65 dBC, whichever is greater. Those numbers are not unconditional ceilings. The baseline study therefore matters. Before treating a limit as reassuring, ask where and when the baseline would be measured and how the public could inspect it.

I like protections that continue doing their job after everyone leaves the hearing. That requires staff capacity, usable records and a clear response when something goes wrong. Otherwise, the burden of making the system work quietly migrates to the person trying to sleep next door.

What is worth watching now

The most useful next document is the county’s written action record. The Board’s information page says action agendas are generally posted within two days, while minutes follow approval. At this research cutoff, I had located the recording but not the September 29 action record in the meeting portal. A next-morning gap should not be mistaken for a missing public process.

After that, watch for a revised draft and an actual notice of public hearings. A meeting on the general calendar is not automatically your opportunity to speak at a data-center hearing. The county’s Planning and Zoning page is also a route for questions while the formal timetable is being developed; it lists planning@newkent-va.us.

If you want to send a useful question now, make it specific enough to receive a checkable answer. Ask which rules would govern an application received before adoption. Ask how a noise complaint would lead to a measurement and corrective action. Ask which parts of the draft depend on the state toolkit and which can be improved now. Those questions work whether you supported the proposed pause or opposed it.

I’m enthusiastic about what AI can do for a local business. That does not oblige me to treat every infrastructure proposal as good news. The value of a technology and the merits of a particular development still have to be examined honestly.

Tuesday settled this motion. It left the harder work in front of the county: explaining the interim process, finishing standards people can understand and showing how those standards would be enforced. That is where I would look for reassurance now. Preferably in a document with a date on it.

Research cutoff: September 30, 2026. This follow-up uses the county’s published packet and autogenerated meeting transcript, corroborating local reporting, and the written executive order. Statements about pending applications are dated to the September 29 staff report; future hearing dates remain unconfirmed.