top of page

Our Comments to Virginia Data Center Planning and Community Engagement Toolkit RFI

Writer: paulBVL
paulBVL
5 days ago
4 min read

Block Valley Link

30281 Springfield Farm Ln

Locust Grove, Va 22508

November 16, 2026


Response to Virginia Data Center Planning and Community Engagement Toolkit RFI 

Question 7: Community Engagement


Respondent Information

Name: Paul McDonald 

Organization: Block Valley Link / Concerned Orange County Citizen 

Type: Resident / Community Advocate

 

Introduction

The Toolkit’s emphasis on early, accessible, transparent, and good-faith community engagement is welcome. In Orange County, Virginia, citizens have experienced the opposite over multiple years of data-center recruitment and related infrastructure planning. The following uses that experience not as a model of success, but as a case study in what the Toolkit should explicitly warn against and design safeguards to prevent. Disclosure in Orange County has repeatedly arrived only after FOIA requests, litigation, or citizen intervention rather than through proactive local process.


7a. Practices that failed to foster early, accessible, transparent, and good-faith engagement (timing, frequency, stakeholder identification, information sharing, feedback, and locality-developer coordination)

Orange County’s approach demonstrates the costs of delayed or absent engagement:

  • Timing and secrecy: For nearly three years, county staff and Board members conducted a recruitment campaign involving confidential conversations, site marketing of private parcels (reportedly nearly 9,000 acres concentrated in eastern District 4, east of Route 522 and north of Route 20), and guided site tours, largely under non-disclosure agreements. Citizens learned of the scale and specific parcels primarily through FOIA rather than early public briefings. Official statements that “there are no applications” and “nothing has really happened yet” persisted while marketing, ordinance work, and infrastructure alignment advanced.

  • Information sharing and feedback: Details about project codenames (e.g., Project White, Project Ascent, and others revealed via FOIA), public-resource expenditures on recruitment, and knowledge timelines for projects such as Valley Link (the proposed 765 kV line) were not proactively shared. A March 24, 2026, Dominion presentation noted route selection looking for “co-location opportunities” with industrial areas or tech overlay districts, the same districts the county was advancing. Citizens discovered apparent alignment between marketed parcels and proposed transmission routes only after independent mapping and records requests. Feedback opportunities were effectively postponed until after key directional decisions.

  • Coordination between locality and developers: Industry input occurred early and extensively (including, per citizen accounts and records, attorneys for Amazon and others shaping ordinance language). Protective provisions such as a 1,000-foot residential setback reportedly disappeared after industry feedback. Public stakeholders were identified late or not at all for the recruitment phase. Coordination with developers happened under confidentiality; coordination with residents happened reactively.


These practices produced the opposite of early, accessible engagement: citizens in the affected eastern area discovered that transformers, substations, ordinance language, and transmission routing considerations had converged on the same geography while official communications continued to emphasize the absence of formal applications.


7b. Problematic roles of local representatives, industry, and other stakeholders

In Orange County the roles inverted the sequence the Toolkit appears to seek:

  • Local representatives and staff led or facilitated confidential recruitment, site selection/marketing, and ordinance drafting with industry, while treating public engagement as a later, separate step. Board members signed NDAs in the earlier Wilderness Crossing matter (ultimately obtained only after a Piedmont Environmental Council FOIA lawsuit that also confirmed Amazon involvement and VEDP’s brokering role). More recent NDAs with potential data-center developers were initially withheld under the economic-development exemption before ordered released.

  • Industry stakeholders exercised outsized influence on the drafting of the Technology District / overlay rules. Citizen Sarah Regan documented at a Board meeting that outside counsel for developers effectively determined which protective provisions were “acceptable,” with language changing overnight. This is the reverse of communities leading negotiations or setting non-negotiable local standards first.

  • Other stakeholders (residents, civic groups, environmental organizations) were largely excluded from the formative stages. Their role was reduced to filing FOIA requests, speaking during limited public comment, or litigating after the fact. The Economic Development Authority’s involvement has also been questioned by residents seeking accounting of public funds and staff time spent advancing private parcels.


The Toolkit should caution against local representatives acting as confidential gatekeepers or industry partners before public stakeholders are identified and engaged, and against industry counsel driving the substance of local ordinances before community input.


7c. Lessons the Toolkit should incorporate to support meaningful and ongoing engagement throughout the project lifecycle

Orange County supplies clear negative lessons:

  • Do not treat “no application yet” as a reason to withhold information about active recruitment, site marketing, or infrastructure coordination. The absence of a formal application is not equivalent to the absence of consequential local action. Require early public disclosure of recruitment efforts, expenditures of public resources, and any NDA-governed discussions that affect land-use or infrastructure planning.

  • Do not allow industry drafting influence to precede or substitute for public process. Protective standards (setbacks, water use, noise, decommissioning, etc.) should be established through open local process before or concurrent with developer input, not revised behind closed doors and presented as finished.

  • Do not align major infrastructure (transmission, substations) with privately marketed parcels without contemporaneous public explanation and opportunity for comment. When Dominion or others cite “co-location opportunities” with districts the locality is simultaneously promoting, residents are entitled to know the timeline of local knowledge and any coordination.

  • Do not rely on FOIA, lawsuits, or individual citizen persistence as the primary disclosure mechanism. Proactive, scheduled public briefings, publication of relevant non-proprietary materials, and standing community working groups should be the default throughout site selection, ordinance development, application review, construction, and operations. Ongoing engagement must include monitoring of commitments, not merely pre-approval hearings.

  • Identify affected stakeholders early by geography and impact, not only by formal applicant status.  Eastern Orange residents whose communities sit in the path of both marketed parcels and Valley Link routes were stakeholders long before any application existed.


The Toolkit can usefully codify that meaningful engagement begins at the recruitment and site-identification stage, requires contemporaneous public information rather than post-hoc document releases, limits confidential industry influence over local rules, and treats infrastructure decisions that enable data-center loads as part of the same public process. Orange County’s multi-year experience shows what happens when those elements are missing: eroded trust, reactive disclosure, and communities learning about major land-use and infrastructure shifts only after the directional choices have already been made.


These observations are offered so the Toolkit can strengthen safeguards that make the Orange County pattern the exception rather than a recurring risk for other Virginia localities.

 

Sincerely,

 

Paul McDonald

Block Valley Link

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page