Build a Power Proof File Before You Sell

A power proof file is the evidence your sales team needs to show exactly what is available, what is contracted, and what is still conditional. Build it before campaigns launch or a broker asks for a tour. It keeps promising opportunities moving and stops your team from creating a credibility problem in the first discovery call.

Why can’t sales just say the site has power?

Because buyers no longer hear “we have power” as a useful answer. They hear a claim that needs to survive diligence.

A tenant with a near-term deployment has to know whether the stated capacity is utility-delivered, backed by an executed supply agreement, dependent on a substation upgrade, or merely part of a development plan. Their infrastructure lead will ask. Their finance team will ask a different version of it. If they are using a broker or site-selection adviser, expect the question to arrive in a spreadsheet with a deadline.

The distinction matters more as power costs become a commercial issue, not just an engineering one. The U.S. House recently passed a measure directing state utility regulators to consider charging data centers the full cost of generation, transmission, and distribution upgrades needed to serve them. It passed 417–3, though it is a recommendation rather than an imposed federal rate design (Associated Press). For operators, that is a reminder that a capacity claim without an explanation of cost responsibility can fall apart late in the deal.

Honestly, vague language may get you a first meeting. It rarely gets you through technical validation.

What belongs in a useful power proof file?

Start with the smallest set of documents and facts that a commercial person can explain accurately. This is not a dump of engineering drawings into a shared folder. It is a controlled deal-enablement package with source material behind every material claim.

For each facility or development phase, include:

• The capacity available now, including the actual service state and any limits on deployment timing.
• Capacity under executed contract, with the agreement type, counterparty category, term, conditions precedent, and planned service date stated plainly.
• Capacity that is planned or under evaluation, clearly labeled as such. Do not place it in the same column as contracted supply.
• The delivery path: utility service, dedicated generation, energy-services agreement, behind-the-meter arrangement, or another structure.
• Known dependency dates, such as interconnection work, substation completion, equipment delivery, permitting, or customer-funded upgrades.
• Who pays for what: recurring energy charges, demand charges where relevant, extension work, deposits, make-ready costs, and upgrade exposure.
• The primary commercial and technical contacts who can answer follow-up questions without forcing the prospect through three internal handoffs.

That last item is easy to overlook. A buyer does not care that your teams have an internal process. They care whether an answer comes back while they are building a shortlist.

AIB Data Centers offers a useful public example of the language discipline operators need. Its September presentation distinguishes a 15-year energy-services agreement for 65 MW, scheduled to begin October 1, from other capacity figures that remain evaluation-stage or non-binding (SEC filing). You do not need to copy anyone’s commercial structure. You should copy the habit of separating secured supply from prospective supply.

How should you label power without killing momentum?

Use labels that a non-engineer can understand and that your legal, operations, and utility teams can defend. We have seen teams improve quickly by replacing one broad “power available” label with a simple status framework.

Operational means the site can support the stated load under current service arrangements, subject to the normal details you disclose around configuration and deployment.

Contracted means an executed agreement supports the stated capacity, but the file should identify conditions and the scheduled service date. Contracted does not automatically mean ready this quarter.

In delivery means the path is committed but still dependent on specific construction, equipment, or utility milestones. This can be a strong story when the milestones are real and documented. It is not the same as operational capacity.

Planned means the capacity is part of a development case, application, study, or negotiation. It may be commercially relevant, especially for a buyer with a long runway, but it should never be presented as firm availability.

The point is not to make marketing sound cautious for its own sake. The point is to match the claim to the buyer’s decision stage. A prospect seeking a fast deployment needs operational capacity and a credible installation sequence. A prospect reserving future expansion may care more about a contracted path and the operator’s ability to carry milestones to completion.

Digital Realty’s planned Ankara campus illustrates why proof should be layered rather than reduced to a single megawatt headline. The company says land, power, and permits are secured, early construction is underway, and completion is targeted for 2028 (Digital Realty). Those are distinct pieces of evidence. For a buyer, each one reduces a different risk.

Who should own the file?

Commercial operations should own the process. Engineering, legal, development, finance, and utility relations must validate their parts, but none of them should be expected to translate every technical update into sales-ready language.

Set one owner responsible for four things: version control, approval status, seller access, and update triggers. If a utility study changes, a permit is issued, a transformer delivery date moves, or a customer takes down capacity, the file needs a defined review. Otherwise, your best pitch deck becomes stale while still looking authoritative.

A practical workflow is simple:

1. Development or operations submits a change with supporting documentation.
2. The subject-matter owner confirms what changed and what did not.
3. Commercial operations updates the buyer-facing summary and flags deals that may be affected.
4. Legal or executive review is required only for claims that alter a public statement, contractual position, or material commercial representation.

Do not force every routine update through a committee. That is how sales falls back to old slides and verbal assurances. Reserve escalation for the claims that truly need it.

How does this change outreach and deal qualification?

It gives marketing something far better than generic “power-ready” copy. You can build campaigns around a specific, supportable buyer fit: a near-term deployment profile, a phased expansion path, a location with a defined energy structure, or a facility that has completed particular development milestones.

Then make the proof file part of qualification, not a document that appears after an NDA. In an early call, ask the buyer:

• What load is needed at initial deployment, and what is the expansion schedule?
• Is the target date tied to a signed customer commitment, hardware delivery, or a planning assumption?
• Does the buyer need a fixed commercial structure, or can it absorb utility and upgrade variability?
• Who must validate power claims before a letter of intent can move forward?

Those answers tell you which evidence to provide first. A buyer with a firm deployment date needs dates, dependencies, and ownership of risks. A buyer exploring a future region may first need confidence that your capacity path is more than a market rumor.

The same logic applies to financing claims. CleanSpark’s proposed senior-secured-notes offering identifies remaining build-out funding, reimbursement of prior equity, debt-service reserves, and a completion guarantee if proceeds are insufficient (CleanSpark). The broader lesson is that buyers look beyond announced intent. They want to understand whether the project has a path through completion.

Common questions

Should we share power documents before an NDA?

Share a concise, approved summary early. Hold back agreements, sensitive drawings, and counterparties where appropriate, but do not make a serious prospect wait for basic status, delivery logic, and known dependencies.

What if our power status changes frequently?

That is exactly why you need a controlled file and a named owner. Use an “as of” date on every buyer-facing summary, and train sellers to state when an answer requires confirmation rather than guessing.

Will more disclosure scare buyers away?

Unsupported certainty is more damaging than qualified clarity. Most sophisticated buyers can work with dependencies if they understand the owner, timeline, and commercial consequence of each one.

Is this only for large wholesale deals?

No. Smaller colocation deals may involve less capacity, but buyers still need to know what they can install, when they can install it, and whether their growth plan has a credible home. A right-sized proof file helps account executives answer those questions consistently.

What to do with this

Audit every current power claim in your website, pitch deck, broker materials, and active opportunity notes. If a seller cannot point to the underlying evidence and explain the status in plain English, rewrite the claim or fix the file. GridReach helps data center and energy companies turn expertise like this into qualified pipeline.