Disclose Easement and Right-of-Way Constraints for GPU Offtake Pads

Consider an illustrative site review: an owner outlines a GPU pad beside an existing substation and marks the adjacent road as construction access. Then the survey shows a utility easement crossing the proposed equipment area, and the road agreement excludes the adjoining parcel. The site may still work, but the original layout and delivery assumptions do not.

That is the disclosure job. Before a buyer evaluates a GPU offtake opportunity, separate what the site controls from what another party can restrict. Show where each constraint lands, which activity it affects, and what remains unresolved.

1. Start with a rights register, not a clean aerial

An aerial can show open ground. It cannot establish the right to occupy that ground, trench through it, or cross a neighbor's property. Assemble a rights register before presenting a pad boundary as available for procurement.

• Identify the parcels: legal descriptions, parcel identifiers, ownership or lease boundaries, and the proposed GPU pad footprint.
• Collect the source records: available title materials, recorded easements, plats, surveys, amendments, releases, and relevant unrecorded agreements known to the owner.
• Log each restriction: instrument identifier, parties, affected land, stated purpose, term, and any consent, relocation, or termination provisions.
• Record evidence quality: source date, reviewer, missing exhibits, uncertain boundaries, and documents still requested.

Do not label an empty register 'no easements' merely because no documents were supplied. Use 'not yet verified' and name the next verification step. Recorded instruments and known contractual restrictions both belong in the review.

Keep this packet aligned with the separate land-control, lease, and ownership disclosure checklist. Owning a parcel and controlling every proposed use of it are different questions.

2. Put every spatial constraint on the same drawing

Give reviewers one dated overlay showing the proposed pad and the rights that intersect it. Distinguish surveyed boundaries from approximate locations. If an instrument describes broad rights without a fixed corridor, flag that uncertainty rather than drawing an invented narrow strip.

• Show recorded easement areas, utility rights-of-way, shared access routes, drainage corridors, and other identified restricted areas.
• Overlay containers or buildings, transformers, cooling equipment, fencing, gates, laydown areas, and proposed trench routes.
• Include temporary works: crane setup, excavation, material storage, construction parking, and heavy-haul turning areas.
• Tag conflicts by document reference and activity affected: permanent placement, temporary occupation, crossing, maintenance, or emergency access.

Do not treat an easement as an automatic no-build zone or assume it permits construction. The instrument, applicable requirements, and rights-holder review determine the restrictions. Make the conflict visible; leave the legal and technical conclusion to the appropriate reviewers.

3. Separate utility presence from corridor rights

A nearby power line or fiber route is a location fact, not evidence of service entitlement. Disclose who controls the proposed route and whether the rights support the specific connection, equipment, and ongoing operating use under evaluation.

• Power: identify the proposed route to the pad, crossings, off-parcel segments, equipment locations, and any rights still needed for installation or maintenance.
• Fiber: identify building-entry and trench routes, carrier-controlled segments, shared ducts, and any permissions needed to reach the proposed demarcation point.
• Utility ROW: flag restrictions on structures, grading, excavation, fencing, vegetation, and storage wherever the governing documents address them.
• Consent status: distinguish a discussion with a utility representative from an executed crossing, encroachment, or corridor agreement.

Keep corridor permission separate from utility capacity, interconnection, energization, and carrier service commitments. A secured route does not establish available megawatts or a service date. An indicative service discussion does not secure the route.

If relocation is proposed, disclose whose approval is required and whether design, cost responsibility, and schedule have been agreed. 'We can move it' is not a resolved constraint.

4. Prove the access chain from road to pad

Walk the complete route from the public road to the equipment location. A driveway visible on a map may cross multiple parcels or serve only a limited use. Legal access and physical suitability need separate evidence.

• Legal access: identify each private segment, the controlling agreement, permitted users, permitted activities, and any time-of-day limitations.
• Construction access: evaluate delivery dimensions, axle loads, bridge limits, turning movements, staging, and permissions for temporary widening.
• Operating access: check whether the rights cover operators, contractors, utility crews, equipment replacements, and emergency responders.
• Shared-road obligations: disclose maintenance allocations, repair duties, gate control, notice requirements, and applicable insurance or indemnity provisions.

Mark any off-site work needed to make the route usable. A road upgrade requiring a neighbor's consent is an unresolved dependency, even if the owner is willing to fund it.

5. Surface third-party controls before fixing the layout

Restrictions can sit outside the easement schedule. Review leases, shared-facility agreements, recorded covenants, and other relevant documents for rights that could affect construction or operations. Identify the actual provision rather than summarizing everything as 'standard restrictions.'

• Approval rights: disclose required landlord, association, neighboring-owner, lender, or other third-party consents where applicable.
• Use restrictions: flag provisions affecting equipment type, industrial activity, noise, lighting, operating hours, or exterior installations.
• Control continuity: identify term limits, renewal conditions, assignment restrictions, and provisions relevant to a change of operator or project structure.
• Interference rights: disclose utility or other rights-holder access, maintenance, excavation, or removal rights that could affect equipment placement or uptime planning.

Private permissions do not replace public approvals, and public approvals do not necessarily override private restrictions. Track those workstreams separately using the GPU offtake permitting and zoning disclosure checklist.

6. Turn each unresolved item into a procurement gate

A useful disclosure does more than name risks. It tells the buyer which decisions can proceed and which assumptions remain conditional. Use a short issue log linked to the drawing and supporting documents.

• State the issue: for example, a proposed transformer overlaps an easement whose placement restrictions remain under review.
• Name the dependency: document retrieval, survey clarification, revised layout, counsel review, or written rights-holder consent.
• Assign accountability: list the party responsible for progressing the item and the external party whose action is needed.
• Define closure evidence: specify the document or technical confirmation required; do not close an item on a verbal assurance.
• Set the decision gate: identify which layout, construction, delivery, or operating commitment should remain conditional pending resolution.

Use plain statuses such as 'documented,' 'under review,' 'consent requested,' and 'unresolved.' Date every status. A target response date is not an approval date, and an executed agreement still needs review against the intended use.

7. Submit a reviewable packet, then evaluate fit

Package the rights register, dated constraint overlay, access summary, source documents, and open-issue log together. Give the reviewer enough context to reconstruct the proposed route and pad layout without relying on a sales call.

• Lead with material constraints: put possible layout blockers and missing corridor rights in the summary, not only in attachments.
• Control versions: identify the drawing and document revisions supporting each conclusion, and circulate changes when assumptions shift.
• Protect sensitive materials: use an agreed diligence channel for restricted agreements while clearly disclosing that a relevant restriction exists.
• Keep claims bounded: say what is documented, what is proposed, and what still requires independent confirmation.

Use Pacific's bridge-capacity evaluation pathway to frame the commercial review. The disclosure packet helps separate a potentially workable site from assumptions that should not yet support an offtake commitment.

Ready to review the site? Schedule a 30-minute GPU site disclosure discussion with Pacific Intelligent Technologies, Inc.. Bring the current pad sketch and the unresolved rights list; flag missing records rather than waiting to make the packet look complete.

FAQ

Does a recorded easement automatically disqualify a GPU pad?

No. Its effect depends on the governing instrument, location, intended use, and applicable requirements. A revised layout or documented consent may address a conflict, but neither should be assumed. Disclose the easement and have the appropriate reviewers determine the available options.

What if the owner does not have a current survey or complete records?

Submit the available materials with explicit gaps. Label approximate locations and avoid an unqualified buildability statement. Assign document retrieval and survey review as open diligence tasks, and identify the procurement decisions that depend on their completion.

Is a neighbor's verbal permission enough for access or trenching?

Do not present verbal permission as durable, verified corridor control. Disclose the conversation as preliminary and ask counsel what written rights are needed for construction, operation, maintenance, and the relevant parties. Keep dependent commitments conditional until the required evidence has been reviewed.