Module 1
Identity and site-control evidence
Locks the site, parcels, project entities, load scenario, utility path, milestone and client-provided site-control evidence used throughout the package.
Founding Baseline · R1 contracting-client use
The Site Evidence Record establishes the versioned factual baseline. Its companion 90-Day Gate Closure Plan converts every material open gate into one managed item with a closure condition, owner, dependency sequence and date. They are delivered together.
Page one · Advancement Snapshot
The first rendered page is a traceable projection of the underlying evidence, discrepancy, cross-gate and gate registers. It is not the 90-Day Plan itself.
The six evidence modules
Module 1
Locks the site, parcels, project entities, load scenario, utility path, milestone and client-provided site-control evidence used throughout the package.
Module 2
Records what eligible utility and process artifacts state, their dates, identifiers, conditions and limits without turning them into a capacity or timing conclusion.
Module 3
Separates ordinance text, application status, formal actions, factual inquiries and parcel-specific professional or Authority determinations.
Module 4
Tracks the plans, civil work and cross-workstream interfaces that affect the named milestone and identifies the responsible professional or team.
Module 5
Records relevant prior actions with stated comparison dimensions, source pinpoints and limits; it does not convert precedent into a forecast.
Module 6
Connects discrepancies, gaps, dependencies and closure evidence across workstreams while preserving each source and status separately.
Separate operating structures
The companion artifact
Each item states why the gate affects the milestone, current evidence and applicability, the exact closure condition, accountable owner, dependencies, due and escalation dates, professional-review requirement and revision trigger. Ninety days is the planning horizon, not a promise that every gate will close in that period.
0–30
Immediate dependencies and first closure evidence
31–60
Sequenced work unlocked by the first set of actions
61–90
Remaining milestone conditions, escalations and external waits
Fixed scope
Eight included deliverables
Release control
By the end of Business Day 10 after written Day 0 confirmation.
Written Day 0 requires the contracted scope, Identity Lock, required inputs, authorized users, secure workspace and release controls to be complete. Third-party nonresponse remains visible as an open dependency and does not automatically stop the clock.
The included 45-calendar-day response-eligibility window applies only to qualifying material responses to enumerated requests sent before release. It is not continuing service or a third-party response deadline.
Use boundary
R1 — Contracting Client Use Only. Authorized Viewers may inspect the Record but may not rely on it. Forwarding, quoting, adviser participation or professional module review does not create third-party reliance.
Signature boundary
A GridVision signature identifies the signer, scope, date, material source traceability and execution of the stated Protocol, subject to disclosed limitations, exceptions and protocol deviations. It does not convert the Record into a legal or engineering opinion and does not prove readiness, capacity, legal compliance, approval or energization.
GridVision organizes source-linked facts and coordinates defined work. It does not provide legal advice, engineering conclusions, utility commitments, permit decisions, title work, environmental assessment, brokerage, lobbying or investment advice. The client’s utility, public authorities and retained professionals remain responsible for their own decisions and work.
Common questions
Qualification first
We will first determine whether the site, milestone and cross-workstream dependency fit the current Northern Virginia scope.
Submitting a request is not an engagement or site analysis. A bounded qualification conversation is scheduled only after the limited entity, E&O, counsel-notice, conflict and secure-workspace controls pass. No proposal, signature or payment is accepted until the full commercial gate passes. Controlled production intake and Identity Lock additionally require a signed SOW and settled payment. SER/Plan evidence assembly and Baseline production, Authority outreach, and R1 artifact work begin only after Day 0 is confirmed in writing.