Skip to main content
Chief Energy Officer Josephus M. Allmond

Virginia Data Center Planning and Community Engagement Toolkit

Building the Virginia Data Center Planning and Community Engagement Toolkit

The Office of the Chief Energy Officer is seeking input to help shape Virginia’s Data Center Planning and Community Engagement Toolkit, being developed pursuant to Executive Order 22 and informed by the Governor’s Data Center Accountability Framework. 

The Toolkit is intended to help local governments, communities, and other stakeholders navigate data center development decisions in an informed, transparent, and structured manner. 

Share your perspective 

We welcome input on practical recommendations, examples, tools and resources, and lessons learned on topics including: 

  • Considerations for minimizing impacts, including siting, design, infrastructure planning, and practices to address environmental and community concerns.
  • Approaches to community benefits, including community benefit agreements, workforce opportunities, local procurement, and accountability for commitments.
  • Best practices for early, accessible, and ongoing community engagement, including useful templates, case studies, and lessons from experience. 

Input is welcome from local governments, residents, community and environmental organizations, data center developers and operators, utilities, workforce organizations, researchers, and other interested stakeholders. Respondents may address any subset of the questions. Focused or partial responses are welcome. 

How to Submit: 

Deadline: Monday, November 16, at 5:00 p.m. ET

Please see the full Virginia Data Center Community Toolkit Request for Input for the complete set of questions, submission instructions, and important notices. 

Use this form to submit your response.

  • Submit a single PDF or Word attachment, no more than 10 pages, excluding appendices.
  • Include your name, email, organization, respondent type, and the question numbers you are addressing.
  • Place all substantive input in the attachment; information included only in the email body may not be reviewed.