New Kent data centers: where things stand after the moratorium vote

A vote against a pause can sound awfully like a vote to press ahead. If you’re trying to work out whether a data center could be built near your home, that is a consequential difference to leave buried in meeting paperwork.

New Kent’s September 29 vote concerned a proposed moratorium: a temporary prohibition on data centers. The motion would have started the process of creating a two-year moratorium through a zoning amendment. It failed. That decision did not approve a particular development, and it did not adopt the separate rules the county is drafting.

Those are different decisions, but they belong to the same story. The county has changed its approach to regulating data centers, considered a temporary pause, and begun working through a new set of proposed standards. Following all three threads takes some patience. You shouldn’t have to arrive at this discussion already fluent in zoning.

District 3 Supervisor Amy M. Pearson has offered an explanation of her vote in a Facebook statement. It is worth hearing her reasoning fairly—and then looking at what the county’s records tell residents about the protections and decisions still ahead.

What Pearson is saying about her vote

The official September 29 action agenda records two votes in favor of initiating the moratorium amendment and three against. Pearson was among those voting against it.

Her broader argument concerns the kind of protection the county should build. She favors durable, legally defensible standards that would be ready if a developer submits a proposal. In her statement, she questions the legal footing of a temporary moratorium and argues that enforceable requirements would give the county grounds to impose conditions, require changes or reject an unacceptable proposal.

That is her policy and legal argument. The action agenda verifies what the Board voted on; it does not settle whether her assessment of a moratorium’s legal strength is correct.

I can see the appeal of rules designed to keep working after the immediate controversy has passed. I can also see why a resident might value a pause while those rules are developed. If the concern is a well, a property boundary or the possibility of persistent noise, time to examine the details can itself feel like protection.

Understanding Pearson’s position therefore doesn’t require a resident to stop asking what happens in the meantime. That question belongs in the conversation alongside her explanation.

Why the old overlay proposal keeps coming up

To understand the current draft, it helps to go back to the county’s earlier proposal, the Technology Overlay District. The name describes a way of adding rules to land within a designated area. The underlying zoning would remain, with an additional layer governing data-center development.

Think of the overlay as a second layer on a zoning map. Under the county’s February proposal, data centers within its boundaries would have followed its special standards and process. Other uses already allowed by the underlying zoning would not have followed that data-center process.

The proposed approval process is the important part. Adopting the overlay itself would have required public hearings. After that, a data-center proposal inside its boundaries that met its standards and other applicable requirements could have followed an administrative permit and site-plan process, without project-specific public hearings. That would have put an opportunity for public input at the stage of setting the district’s rules, rather than requiring a new hearing for each qualifying project.

On July 13, the Board stopped development of that overlay approach and directed staff to prepare data-center performance standards instead. The February presentation therefore explains an abandoned proposal. It does not describe an approval route that the county adopted.

The September draft proposes individual conditional-use permits for data centers on industrially zoned land. That route would bring a particular project before the Planning Commission and Board of Supervisors for consideration. The draft also requires a community meeting before the Planning Commission hearing, giving residents an opportunity to ask the applicant about that project.

The proposals differ in how an individual development would be reviewed and when residents would have an opportunity to participate. That is the practical change to keep in view as the county develops the new rules.

For someone trying to follow the debate, the practical consequence is simple. Use the old overlay presentation to understand the history, and the September draft to examine the process and protections the county is considering now.

Where that leaves things today

The county’s Planning page reports no pending data-center applications as of September 29. Keep the date attached: it tells us the formal application status at that checkpoint. It does not establish that no developer is interested or that no preliminary planning has occurred.

The Board also expressed a strong policy preference in July that applications not be filed or advanced while regulations are being developed. The current Planning page says that preference remains in effect.

I would use the county’s wording carefully here. A policy preference expresses the Board’s position. It should not be relabeled as an adopted zoning moratorium. Nor does an unfinished draft mean that no existing laws apply. The practical question is which existing provisions would govern an application arriving before the new ordinance is adopted, and how the county would handle it. The records reviewed for this article do not provide a complete answer to that question.

What the draft gives residents to examine

The draft presented September 29 contains concrete proposals. Consider the proposed 500-foot setback for data-center buildings and supporting equipment from exterior property lines. The required buffer is included within that distance. A resident looking at a future site plan would have a measurement to examine, rather than having to decide how much comfort to take from a phrase such as “well screened.”

The water provisions address a different concern. Cooling would have to use closed-loop systems, which recirculate cooling fluid. Groundwater could not supply cooling or process water, while potable-system water would be limited to domestic use and fire flow. These are proposed restrictions on how a facility would use water. They are not a claim that it would use none.

I would give those provisions a serious look. Specific requirements make it possible to ask specific questions about whether a proposal would comply. That is useful progress in drafting, even while the requirements remain proposed rather than adopted.

Noise deserves a little more time because the numbers can look simpler than the rule actually is. The draft uses existing ambient sound levels or 55 dBA and 65 dBC, whichever is greater. In other words, the recorded background sound can affect the applicable limit. Those numerical figures are not unconditional ceilings.

That makes the baseline study consequential. Before deciding whether the proposed limit is reassuring, I would want to understand the measurements on which it depends and how residents could inspect them. A number printed in an ordinance is easier to discuss when people can see how it would apply to the place they live.

A rule also needs a route to a remedy

The next question is what happens after a facility opens. Imagine a future neighbor reporting a persistent nighttime sound. This is a hypothetical, not a report about an existing New Kent facility. For that neighbor, the useful information would be whom to contact, how the complaint would be investigated, and what happens if the facility is exceeding its limits.

The proposed noise provisions require sound studies within 90 days of each phase becoming operational and within 90 days of full operation. Additional studies must be conducted within 90 days of a request from the zoning administrator. If a post-construction study establishes noncompliance, sound-reduction measures must be designed and implemented, with the implementation time dependent on an approved mitigation plan.

That distinction is worth slowing down for. The study has a deadline. Correcting the problem follows a timetable approved for the mitigation plan. Saying “90 days” without explaining which step it applies to could leave someone expecting a remedy the wording does not promise within that period.

I welcome those proposed study requirements and the duty to correct violations established by a study. What this part of the draft does not explain is how a resident’s complaint would lead to an administrator’s request. I would want the county to make that route clear, along with where findings become available, how residents track corrective work, and what enforcement follows if an operator fails to comply.

Someone trying to sleep should be able to find the next step without acquiring a second career in zoning. That is a reasonable test of how usable the eventual rules will be.

How residents can take part now

Pearson describes approximately 120 days for residents to review the proposed ordinance. The county’s current Planning page does not give hearing dates or a formal start and end to that period. Her statement offers an expectation, but it is not enough to put a confirmed deadline on the calendar.

A separate proposed 30-day review authorization was pulled from the September 29 agenda. That particular formal window should not be described as having opened. The county does say that advertised public hearings must precede adoption and will be scheduled as the ordinance develops.

The county Planning page invites questions and feedback at planning@newkent-va.us. Residents can use that address to comment on the rules while they are being developed, before a hearing date has been announced.

There is a second, later kind of participation described in the draft. For future project applications, it would require a community meeting before the Planning Commission hearing, with written notice to adjacent owners and owners within one mile. That is about examining an individual proposal. It does not set the schedule for adopting the countywide ordinance.

If you want to write now, I would start with the question the county’s current position leaves open: Which existing rules and procedures would apply if an application arrived before the new ordinance was adopted? A second useful request is for a clear place to find each revised draft, an explanation of its changes and the eventual hearing notices.

For feedback on a specific rule, connect the wording to the problem you want it to solve. A comment on noise enforcement, for example, could ask where a resident would find the investigation results and the deadline for corrective work. That gives staff something concrete to address in the next draft or in an explanation of how existing procedures apply.

Pearson’s explanation helps us examine the reasoning behind her vote. The next reassurance I would look for is a process people can follow all the way through: from the current drafting work, through a future application, to help when a protection is needed. Residents can give her explanation a fair hearing and keep asking for those details. There is plenty of room for both.

Records checked October 4, 2026. Application status is dated September 29; future hearing dates remain unconfirmed.