Virginia permit readiness review

Get a clean first read on a Virginia data-center project.

For an early-stage Virginia data-center or gen-set project, we organize the known facts, compare them with the available The Permit Signal 2024–2026 issued-permit precedent set, and show what needs specialist follow-up.

Evidence boundary

Available Virginia DEQ precedent

The review uses the issued permits and source notes in the Virginia data-center gen-set pack. Those records provide context for questions; they do not determine a new project’s outcome.
  • 01Issued-permit records from 2024–2026
  • 02Run-hour, Tier, BACT, and annual-netting fields
  • 03Source-linked agency documents for review
01 / What the review covers

Four lenses for a Virginia readiness review.

The review organizes the facts already known about the site, generation equipment, phasing, operating assumptions, and schedule. Each lens stays bounded by the available Virginia issued-permit record and flags what needs specialist follow-up.

Review lens

Project facts and applicability framing

A structured first read of the supplied site, equipment, phasing, and schedule facts against the available Virginia precedent, with confirmed inputs, assumptions, and unresolved applicability questions separated.

Review lens

Run-hour and threshold context

The source summary’s 350–750 synthetic-minor run-hour-cap range per unit per year and annual major-source threshold tracking are comparison context, not a prediction for a new project; both are drawn from issued permits.

Review lens

Tier and control context

A review lens for Tier 4 Final and Tier 4i citations, the July 1, 2026 APG-576 revision, and SCR-based control context, including whether a written rebuttal is part of the project record.

Review lens

Operating records and assumptions

A source and record checklist for testing assumptions about duty cycle, load-following, engine start frequency, phasing, and annual netting before a specialist relies on them.

02 / What you receive

Four deliverables for the next handoff.

The output is designed to hand cleanly from development, EPC, and permitting leads to the legal, engineering, or agency-facing specialists who take the next step. It records what the supplied facts support and what still needs confirmation.

Client output
01

Project-fact and applicability read

A plain-language comparison of the supplied project facts with the available Virginia issued-permit context, with assumptions marked and no claim that precedent determines the project.

Client output
02

Prioritized issue/gap register

An ordered list of missing facts, assumptions, and questions that could change the next specialist workstream or the records that workstream needs.

Client output
03

Source/document checklist

A collection list for equipment details, site context, operating scenarios, existing permits, source records, and operating records needed for follow-up.

Client output
04

Next-step briefing

A concise handoff that turns the first read into ordered conversations, confirmations, and specialist workstreams; it is not a filing, sign-off, or agency representation.

03 / How the review works

The review process: four steps from facts to specialist handoff.

  1. 01

    Collect the project facts

    Share the site, equipment, operating, phasing, and schedule context currently available.

  2. 02

    Compare with Virginia precedent

    Use the available 2024–2026 issued-permit set as a source-bounded comparison frame.

  3. 03

    Surface assumptions and gaps

    Separate known inputs from unresolved questions, including source-context questions about controls, netting, and run hours.

  4. 04

    Hand off a scoped briefing

    Leave the team with an ordered next-step brief for the appropriate specialist follow-up.

04 / Scope, plainly stated

Scope boundaries before professional sign-off.

This is an advisory readiness review built around supplied facts and source-backed context. It does not replace the legal, engineering, filing, or agency-facing work that follows.

  • No legal advice

    The review is not a legal opinion or attorney-client representation.

  • No stamped engineering or emissions calculations

    We do not provide stamped design, engineering sign-off, dispersion modeling, or emissions calculations.

  • No permit drafting or filing

    The service does not draft, file, or submit a permit application.

  • No agency representation

    We do not represent the project before an agency or conduct agency negotiations.

  • No guaranteed approval or timing

    A precedent comparison cannot guarantee approval, a project outcome, or an agency timeline.

05 / Questions before intake

A clear boundary around the first read.

A concise guide to the review scope, intended handoff, and boundaries for early-stage Virginia project teams.

Request a Virginia review

Bring the project facts

Request the Virginia permit-readiness review.

Tell us what is known, what is still moving, and which questions the permitting team needs to frame before specialist work begins.