Disclose Permitting and Zoning Status for GPU Offtake Buyers

A site owner recently described an industrial parcel as “ready for data center development.” The property had suitable utility service and industrial zoning—but the local code did not list data centers as an allowed use. Planning staff expected a conditional use permit, public notice, a traffic study, and a hearing. “Ready” actually meant an approval process with an uncertain calendar.

That distinction matters to GPU offtake buyers. An unused interconnect position may create a compelling power opportunity, but it does not automatically establish the right to construct or operate a GPU facility. Buyers need to know what is allowed today, which approvals remain, who controls the process, and what could delay commercial operation.

Separate current rights from future approvals

Start with what the site can legally support now. Avoid broad labels such as “industrial,” “entitled,” or “shovel-ready” unless the underlying documents support them.

A useful disclosure identifies:

• The jurisdiction and current zoning designation
• Whether a data center, computing facility, or comparable use is permitted by right
• Whether the proposed use requires administrative approval, a conditional use permit, a special exception, or rezoning
• Existing entitlements and their expiration dates
• Conditions attached to prior approvals
• Development agreements, overlays, covenants, or deed restrictions
• Whether approvals transfer to a buyer, tenant, or project entity
• Any limits on operating hours, building height, floor area, noise, lighting, or exterior equipment

Quote the applicable code section or provide a written zoning determination when possible. If local rules do not expressly define a data center, disclose that ambiguity rather than assuming the project falls within another technology or industrial category.

The goal is not to deliver a legal opinion. It is to give the buyer and its counsel a traceable starting point.

Build a permit matrix around the proposed facility

Zoning approval is only one line in the development schedule. Package the remaining approvals in a permit matrix that names the authority, status, dependency, and expected decision path for each item.

Depending on the project and jurisdiction, that matrix may include:

• Site-plan or development-plan approval
• Conditional use or special-use approval
• Building permits
• Electrical and mechanical permits
• Grading, erosion-control, and stormwater permits
• Fire-code and life-safety review
• Air permits or registrations for regulated equipment
• Environmental review under applicable state, local, or federal processes
• Wetlands, floodplain, cultural-resource, or endangered-species review
• Road-access, traffic, or right-of-way approvals
• Certificate of occupancy or equivalent operational authorization

Label every item precisely: not started, pre-application complete, application submitted, completeness confirmed, under review, approved with conditions, appealed, or closed.

“Discussed with the county” is not the same as an application. “Approved” is not the same as final and non-appealable. Include dates and copies of available correspondence so buyers can distinguish an informal planning conversation from an enforceable approval.

Disclose the timeline risks buyers cannot see

GPU buyers typically work backward from a target energization or service date. A permit that takes six months under an ideal sequence can become a twelve-month constraint if hearings occur quarterly, studies must span a season, or an appeal stays construction.

Call out schedule factors such as:

• Mandatory pre-application meetings
• Application windows and hearing calendars
• Public-notice or neighborhood-meeting requirements
• Agency staffing or review backlogs
• Required third-party studies
• Sequential versus parallel reviews
• Appeal and judicial-review periods
• Approval expiration or vesting deadlines
• Conditions that must be satisfied before permit issuance
• Construction inspections required before occupancy

Use ranges rather than unsupported certainty. State who supplied each estimate and when it was last confirmed. A planning consultant's schedule, a jurisdiction's published service target, and an owner's internal assumption should not appear as if they carry equal weight.

Buyers comparing the site with other available infrastructure capacity opportunities need enough detail to place entitlement risk beside power availability, capital requirements, and deployment timing.

Give buyers a clean diligence package

Create one indexed folder rather than forwarding scattered emails. Include the zoning map, parcel list, code excerpts, land-use opinions, approved plans, permit matrix, agency correspondence, studies, hearing records, recorded conditions, and a log of open questions.

Add a one-page entitlement summary with four clear sections:

• Allowed today: rights already established and still valid.
• Pending: applications filed but not finally approved.
• Required next: approvals needed for the proposed GPU use and buildout.
• Unresolved: interpretations, studies, appeals, or agency decisions that could change scope or timing.

Also identify the applicant of record, land-control entity, consultants, and primary agency contacts. If the site will be leased or transferred, explain which permits can be assigned and which must be reissued.

Pacific Intelligent Technologies, Inc. helps site owners frame unused grid positions for credible counterparties. Review the broader Pacific infrastructure platform and its approach to bridge capacity for near-term deployment constraints.

Make the entitlement gap actionable

A strong disclosure does not pretend every approval is complete. It shows that the owner understands the gap between current site status and an operable GPU facility.

End the package with a responsibility table. Assign each open task to the owner, buyer, landlord, developer, or project company. Note required inputs, decision deadlines, and whether completion is a condition to lease execution, notice to proceed, or commercial operation.

If you control a site with unused interconnect and want to package its permitting position for GPU offtake discussions, schedule a 30-minute site review.

FAQ

What do GPU offtake buyers ask for first?

Most ask for the zoning designation, confirmation that the intended use is permitted, copies of existing entitlements, a permit matrix, agency correspondence, and a realistic critical-path schedule. They may also request evidence that approvals survive a lease, sale, or change in project entity.

Should a site owner wait until every permit is approved?

Not necessarily. Early-stage sites can still be marketable when the remaining path is explicit and supported by documents. The key is to separate completed approvals from assumptions and assign the unresolved timeline risk.

Is industrial zoning enough for a GPU facility?

Not always. Local codes may treat data centers as a distinct use or require discretionary approval because of building systems, exterior equipment, noise, traffic, or operating characteristics. Obtain jurisdiction-specific confirmation.

How does entitlement status affect the offtake conversation?

It influences the credible start date, conditions precedent, development responsibilities, and risk allocation. Buyers assessing capacity opportunities across Pacific Intelligent Technologies, Inc. need to understand whether a site offers an executable path—not merely a favorable zoning label. For a working packet, book 30 minutes with Harper.

A credible GPU offtake pitch therefore connects four things: current legal rights, a permit matrix with statuses, timeline risks a buyer cannot see from a zoning label, and a diligence package that assigns the remaining gap. That is what turns “the site should be permitted” into an entitlement path a counterparty can underwrite.