Data Center Construction Permit Tracking: A Status and Dependency Register

Start with the exact mobilization question

The useful question is not “Is the project permitted?” It is “May this named party start this defined work package, in this location, during this time window, under these plans and conditions, based on which current records and whose authorization?” That narrower question prevents one valid approval from becoming a project-wide green light.

Build the register from the governing jurisdiction, contract, permit documents, approved plans, authority instructions, environmental requirements, inspection plan, schedule, and legal or professional advice applicable to the project. A generic checklist can organize evidence, but it cannot determine which approvals are legally required or interpret them for a particular site.

• Give every site, phase, area, work package, authority, permit, submission, condition, inspection, and decision a stable identifier.
• Name the Owner, controlling contractor, responsible discipline, permit holder, submitting party, authority contact, qualified reviewer, and person authorized to release the work.
• Record the jurisdiction, location, project phase, governing document, revision, effective date, and source link instead of relying on a copied status label.
• Route unclear scope, conflicting requirements, missing authority, or uncertain applicability to the appropriate authority or professional before mobilization.

Build the seven-stage permit dependency register

The following checklist is an editorial evidence model for organizing a representative package. It is not a universal legal, environmental, engineering, safety, or code checklist. Local requirements and authorized interpretations control.

• 1. Jurisdiction and authority matrix: identify the site and legal jurisdiction, each authority having jurisdiction, review or permit category, authority contact, scope boundary, governing source, responsible project role, and unresolved applicability questions.
• 2. Exact work package versus exact permit: link one defined activity, location, limits, contractor, schedule window, drawing or specification revision, and means-and-methods boundary to the specific permit or approval said to cover it.
• 3. Prerequisite, submission, and revision evidence: preserve required inputs, submitted forms and plans, calculations or studies where applicable, receipt, completeness notice, comments, responses, resubmissions, fees or bonds when relevant, and the exact current revision.
• 4. Status, conditions, expiry, and review state: record the authority-issued status in its own words, effective and expiration dates, conditions, limitations, appeal or additional-review state, responsible owner, next action, due date, and source document.
• 5. Dependencies and mobilization boundary: map predecessor permits, utility or access dependencies, environmental or other reviews, approved-plan availability, notices, meetings, inspections, hold points, and the separate authorized release decision for the exact package.
• 6. Inspection, closeout, and handoff evidence: connect required inspections, requests, results, deficiencies, corrections, reinspections, completion records, as-built or turnover evidence, outstanding conditions, and the receiving role without treating a field observation as formal acceptance.
• 7. Append-only change and correction register: retain every permit revision, condition change, authority communication, schedule or scope effect, superseded value, correction reason, actor, timestamp, source, review, and downstream notification.

Separate work packages from permit documents

A permit title and a schedule activity rarely describe scope at the same level. Create an explicit many-to-many map: one permit may cover only part of a package, one package may depend on several permits or reviews, and a later phase may require evidence that was irrelevant to early work.

Use package examples such as site access, erosion controls, mass grading, underground utilities, foundations, structural work, building systems, energization, commissioning, or occupancy only as organizing labels. Do not assume those labels correspond to the same permits, sequence, or authority in every jurisdiction.

• Package record: precise activity, physical limits, responsible contractor, planned dates, controlling drawings and specifications, exclusions, interfaces, and downstream handoff.
• Permit record: authority, official identifier and title, holder, exact covered scope, plans incorporated by reference, conditions, dates, status source, and retained document.
• Coverage link: the cited clause, plan sheet, boundary, phase, or authority response that supports the asserted relationship between the package and permit.
• Gap record: uncovered activity, ambiguous boundary, missing prerequisite, conflicting revision, owner, due date, escalation route, and mobilization effect.

Use states that cannot turn false green

Status should describe what the source proves, not what the team hopes it means. Keep authority review, document issuance, condition completion, inspection outcome, and project authorization in separate fields so a dashboard cannot collapse them into one misleading color.

• Applicability unresolved: the team has not confirmed whether a review or permit is required for the stated package and jurisdiction.
• Preparing or submitted: project records are being assembled or have been delivered; neither state proves completeness, review, or approval.
• Incomplete, comments issued, or revision required: the authority or reviewer requested additional information or change; record each open item and response revision.
• Under review: the named authority is reviewing the stated submission revision; elapsed time is not evidence of approval.
• Issued with conditions: preserve the actual issued document and every condition, limitation, effective date, expiry, and prerequisite. “Issued” alone is not a mobilization decision.
• Suspended, expired, appealed, withdrawn, superseded, or revoked: retain the source, effective time, affected packages, containment action, notification, and authorized disposition.
• Inspection or closeout recorded: cite the exact inspected scope and result. A passed inspection for one stage does not prove project-wide completion or permission to operate.

Add a dated policy-to-project status register

Permits sit inside a wider chain of statutes, executive actions, agency work, rulemaking, local land-use decisions, utility proceedings, authority-issued records, and project evidence. A useful register keeps those layers separate because each has a different decision maker, effective date, scope, and consequence.

For every row, preserve the source title and URL, issuing body, jurisdiction, legal or procedural status, publication and effective dates, affected threshold or scope, required follow-up, project applicability, responsible owner, expiry or review date, and the event that forces revalidation. A summary should never outrank the controlling source.

• Effective authority: identify an enacted statute, effective regulation, operative order, final tariff, issued permit, or other current instrument and state exactly whom and what it governs. An executive order applies only within its lawful and stated scope; it is not automatically a project permit condition.
• Directed future work: record an agency assignment, study, toolkit, draft standard, or rulemaking deadline as work to be completed. The direction is real, but the future deliverable is not yet a final requirement or satisfied project condition.
• Proposed or pending action: label a framework proposal, introduced bill, one-chamber-passed bill, draft rule, pending tariff, or requested approval with its current stage and next authority. Do not relabel it as enacted, effective, final, or approved.
• Local, utility, or authority decision: preserve the exact board, commission, utility, permitting authority, decision date, docket or identifier, covered site or package, conditions, appeal or review state, and source record.
• Project condition satisfied: cite the exact evidence, requirement, responsible reviewer, verification date, limitations, affected package, and authorized disposition. A project assertion or uploaded file is not satisfaction by itself.
• Superseded, expired, stayed, challenged, withdrawn, or rejected: retain the prior state and source, effective time, affected dependencies, containment action, notification, and next review instead of deleting the history.

Make dependencies and mobilization separate decisions

A dependency graph explains why work is waiting; it does not itself authorize work. Connect each package to predecessor evidence, then require an authorized person to review the current sources and record the bounded mobilization decision.

When permit timing affects access, sequence, procurement, staffing, temporary works, or downstream milestones, link that effect to the schedule and the governing change process. Do not silently rewrite the permit record, schedule baseline, contract entitlement, or cost status.

• Hard dependency: the project cannot release the stated package until the cited requirement is satisfied under the governing source.
• Conditional dependency: work may proceed only within recorded limits, controls, notifications, inspections, or time windows.
• Coordination dependency: a utility, adjacent package, site-access plan, owner decision, or third-party interface must be ready even if it is not itself a permit.
• Evidence dependency: the decision maker needs the issued record, incorporated plans, completed condition, inspection result, or professional review before acting.
• Mobilization decision: the authorized person records proceed, proceed with conditions, hold, or stop for the exact package, with time, evidence, limitations, and next review.

Carry inspection and closeout evidence through handoff

The register should continue after issuance. For each required inspection or closeout step, retain the request, scheduled and actual times, inspected scope, governing revision, inspector or authority, result in the source record, deficiency, correction, reinspection, and outstanding condition.

Handoff should tell the next responsible role exactly what was inspected or closed, what was excluded, which conditions remain open, which records are authoritative, and what future review is required. A photograph, daily-log note, or contractor completion statement may be useful evidence but is not automatically an authority inspection or acceptance.

• Link field observations and photos to the exact location, package, date, author, source file, and related inspection or condition without relabeling them as approval.
• Keep failed, partial, cancelled, deferred, or inaccessible inspections visible with accountable follow-up and the resulting work boundary.
• Preserve final records, incorporated revisions, open conditions, warranties or maintenance handoffs when applicable, retention location, and authorized recipient.
• Do not infer occupancy, operation, acceptance, code compliance, environmental compliance, or project completion from a generic closed status.

Preserve changes and corrections as append-only evidence

Permit and package records change as authorities comment, plans are revised, conditions are clarified, schedules move, and field facts emerge. Preserve the event history so a reviewer can reconstruct what the team knew and which source controlled each decision at that time.

A correction should point to the superseded value instead of silently overwriting it. If a status, date, package boundary, permit identifier, condition, or dependency was entered incorrectly, record the original, corrected value, reason, author, time, evidence, reviewer, and affected downstream records.

• Use durable event IDs, source-document versions, timestamps with time zones, responsible organizations and roles, and links to the exact affected package and permit.
• Separate authority-issued changes from project interpretation, internal planning assumptions, schedule forecasts, and editorial summaries.
• Notify the named downstream owners when a change affects mobilization, sequencing, inspections, procurement, safety controls, or a submitted revision.
• Retain withdrawn, rejected, superseded, or expired records so current status can be traced without allowing obsolete files to appear active.

Avoid false-green permitting failure modes

False green occurs when a real but bounded event is presented as broader permission. The register should surface these failures before a schedule status or executive summary strips away the limiting context.

• Treating an application receipt, fee payment, meeting note, verbal update, submitted drawing, or absence of comments as an issued permit.
• Using “approved” without the authority, permit identifier, covered package, incorporated revision, conditions, effective date, expiry, and source document.
• Applying a site, grading, environmental, utility, building, inspection, or occupancy record to work outside its stated scope.
• Showing the newest uploaded file as current without confirming whether the authority accepted, incorporated, superseded, or rejected that revision.
• Hiding conditions, unresolved comments, dependencies, inspection failures, appeal or review state, expiry, suspension, or package exclusions behind a green icon.
• Letting a schedule activity, daily log, photo, AI summary, internal checklist, or contractor assertion replace the authority record or authorized decision.
• Assuming a requirement or sequence from another state, county, city, project type, or authority without verifying local applicability.

Virginia’s September 18 framework: separate action from proposal

On September 18, 2026, the Virginia Governor’s Office released a Data Center Accountability Framework and signed Executive Order 22. The official release expressly separates actions placed into effect through the order, immediate directions to executive-branch agencies, and proposals intended for the 2027 General Assembly session. GovTech independently reported that framework items not covered by the order or agency directives still require General Assembly approval.

The release says Executive Order 22 bars executive-branch bodies under the Governor’s supervision from entering into or requiring non-disclosure agreements for data center projects, directs an initial planning and community-engagement toolkit, expedites development of data center noise regulations, and directs review of backup-generation operations, among other work. Those are bounded actions and assignments. They do not make every broader framework proposal current Virginia law, determine how a provision applies to a particular project, or prove any permit, utility, environmental, construction, or operating condition is satisfied.

• Register the signed order and each operative instruction as an effective source with the exact responsible body and scope.
• Register a directed toolkit, regulation, review, or best-practice deliverable as pending agency work until the responsible body publishes the actual output and its status is verified.
• Register items identified for the 2027 legislative session as proposals unless and until the General Assembly and other required authorities complete the applicable process.
• Recheck the current law, agency materials, local approvals, utility decisions, and project records before applying any statewide summary to a site or work package.

H.R. 9340 is House-passed, not enacted law

GovInfo’s official bill-status record, updated September 18, shows that H.R. 9340 passed the House 417–3 on September 16, 2026 and was received in the Senate on September 17. As of this guide’s September 21 review, that record does not show enactment. The House-engrossed text calls the proposal the Ratepayer Protection Act and would add a federal standard under the Public Utility Regulatory Policies Act for certain large-load customers if the legislative process is completed.

The engrossed text uses a 100-megawatt single-site or campus threshold and addresses consideration of full incremental upgrade-cost recovery and financial assurances. Utility Dive provides independent context on the House action and uncertain Senate path. None of those records proves the proposal is current law, a final utility tariff, an interconnection decision, a permit condition, available service, or approval for a data center project. Keep the bill stage and exact as-of date visible, then follow the responsible federal, state, utility, local, and project sources separately.

A current Botetourt County example, with a bounded conclusion

Botetourt County posted an official update on August 26 and updated it on August 28, 2026. The County said Google satisfied County requirements and received a Land Disturbance Permit after County review of Mass Grading Package No. 1. The permit allows phased grading on the 312-acre site. The same update says work requiring additional state or federal environmental permits remains subject to review and that the Virginia Department of Environmental Quality oversees several environmental permits.

WSLS independently reported the land-disturbance permit, phased grading, 312-acre site, remaining state and federal environmental review, and Virginia DEQ oversight on August 28 at 3:25 p.m. The durable lesson is the boundary: evidence for one land-disturbance permit and a defined initial grading package does not prove approval for building construction, every environmental approval, operation, inspection acceptance, or project-wide permission. The reports do not establish any relationship with NEXUS.

Use planning toolkits within their stated jurisdiction

The Pennsylvania Department of Community and Economic Development says its Data Center Planning Toolkit helps local governments evaluate proposals against local authority, infrastructure realities, and community goals, and supports the process from initial inquiry through zoning, permitting, and long-term planning. It identifies considerations that include power, water, broadband, land use, fiscal, economic and service impacts, and zoning, planning, and legal issues.

That toolkit is useful background for organizing questions and evidence. It is Pennsylvania guidance for local officials and municipal decision-makers, not a statement of law or a complete permit list for projects outside Pennsylvania. Each team still needs to verify the authorities, requirements, terminology, sequence, and professional advice applicable to its own site.

Pilot one representative permit-to-work package

Choose one bounded package with a real jurisdiction, responsible contractor, current source records, and an authorized decision maker. Run it through all seven stages, then compare the register with the actual authority file, contract, approved plans, schedule, field evidence, inspection records, and handoff requirements.

• Authority coverage: every asserted requirement or non-requirement names the jurisdiction, authority, governing source, reviewer, date, and unresolved uncertainty.
• Scope traceability: the work location, limits, contractor, schedule window, and controlling revisions map to the exact permit scope and exclusions.
• Revision integrity: the register distinguishes submitted, commented, resubmitted, issued, incorporated, superseded, and current documents without losing history.
• Condition closure: every permit condition and prerequisite has a responsible owner, evidence, status, due date, effect on mobilization, and authorized disposition.
• Inspection traceability: requests, results, deficiencies, corrections, reinspections, exclusions, and open items point to the authoritative record.
• Decision integrity: each proceed, conditional proceed, hold, or stop decision identifies the authorized person, exact package, source evidence, limitations, time, and next review.
• Exception and correction quality: sampled gaps and changes preserve the prior value, reason, actor, evidence, downstream notification, and human review.

Where AI and NEXUS fit

AI may draft proposed register fields from authorized documents, compare revisions, group related evidence, summarize authority comments, and flag missing conditions or dependencies. Every output remains a draft or advisory signal. A responsible person should open the source, correct the draft, preserve uncertainty, and record the disposition before the information affects mobilization or another consequential action.

NEXUS is currently a BETA, AI-assisted construction-operations platform. Its public product facts support a restrained connection among source documents, field evidence, shared review, project records, and human-authorized decisions. The seven-stage register in this guide is an editorial framework, not a claim that NEXUS issues permits, determines legal, environmental, engineering, safety, or code compliance, approves work, or replaces authorities and qualified professionals.

Authorized people remain responsible for permit interpretation, compliance, professional review, inspections, mobilization, approvals, contractual and legal decisions, payment status, and fund release. NEXUS is not a bank, custodian, money transmitter, or milestone payments holder.