Data Center Pre-Lease Agreements: What They Really Prove

Data Center Pre-Lease Agreements: What They Really Prove

*By Matthieu Gallego*

A data center pre-lease agreement can unlock a project—or create a misleading sense of certainty. The document may sit at the centre of a financing case, a land acquisition, a modular-equipment order or a grid-capacity decision. Yet the commercial meaning changes completely depending on whether the agreement is binding, conditional, cancellable, phased or dependent on a separate lease that has not yet been signed.

That distinction matters because the market increasingly compresses several different milestones into one headline: “tenant secured.” In practice, a memorandum of understanding, a capacity reservation, a framework agreement and a long-form take-or-pay lease do not carry the same risk. Investors and developers need to examine the chain of obligations, not just the announcement.

A useful current example came on 25 September 2026. Brightray Science announced a modular sales framework for a planned 40 MW IT campus in Macao. The public release is unusually helpful because it states that the agreement is non-binding and that a definitive transaction depends on Brightray securing a tenant and the developer entering into a binding lease by 30 September 2027. The project may be serious, but the framework is evidence of a pathway—not proof that the capacity is contracted.

What a data center pre-lease agreement must establish

The first question is not whether a document exists. It is what each party is actually required to do.

A robust review starts with five points: the identity and credit quality of the tenant; the amount and definition of capacity; the conditions precedent; the delivery and acceptance regime; and the consequences if either party fails. These points should be read alongside the project evidence available through PowerlandMap’s market-intelligence workflow, rather than in isolation.

Capacity language deserves particular care. “40 MW” can refer to IT load, utility supply, a future campus design, a reservable block or an initial phase. A lease should identify the delivered product precisely: critical IT load, resilient electrical topology, density assumptions, cooling duty, availability standard and the point at which capacity is deemed ready. If those definitions remain in schedules to be agreed later, the headline volume is less firm than it appears.

The same applies to time. A target ready-for-service date is not necessarily a hard delivery obligation. The agreement may permit extensions for grid delays, permits, long-lead equipment or tenant design changes. Those exceptions can be reasonable, but they must be reconciled with the project’s actual development-readiness milestones.

Conditions precedent are the real risk map

In my experience, the conditions precedent often reveal more than the term sheet’s headline economics. They show which risks the parties have not yet solved.

Typical conditions include land control, planning approval, a binding grid connection, financing, satisfactory technical due diligence, customer credit approval and execution of ancillary agreements. A condition may be objective, such as receipt of a permit, or discretionary, such as approval “in the tenant’s sole satisfaction.” The second category gives one party far more optionality.

The reviewer should build a conditions matrix with an owner, evidence requirement, deadline and failure consequence for every item. A condition with no accountable owner or no long-stop date is not a milestone; it is an open risk.

This is where the public record becomes valuable. A claimed power position should be tested against utility documents and the site evidence described in our powered-land due-diligence guide. Planning status, grid capacity, delivery dates and campus phasing should agree across the lease, technical schedules and external sources.

From commercial signal to bankable contract

A bankable data center pre-lease normally creates durable cash-flow visibility. That does not mean every project needs the same contract, but lenders and investment committees will look for recurring features: a clearly identified tenant entity, enforceable payment obligations, limited termination rights, meaningful security, defined acceptance tests and a rent commencement mechanism that is not endlessly deferrable.

The contrast with a framework agreement is important. A framework can validate vendor selection or commercial intent. It may preserve pricing, reserve manufacturing capacity or set a route to a definitive contract. It can also expire without a project proceeding.

A long-term lease may provide materially stronger evidence. In June 2026, Applied Digital announced a 15-year, 210 MW take-or-pay lease at its Delta Forge 2 campus. The public announcement still does not replace a review of the underlying agreement, but it communicates a different level of commitment from a non-binding framework conditional on a future tenant.

The financing context must also be separated from the lease itself. Nscale’s 25 September 2026 announcement of $3.36 billion in convertible financing demonstrates access to corporate capital, but it does not disclose allocation to individual sites. Corporate funding, project debt, tenant prepayments and landlord equity each support a project differently. Our analysis of AI data center financing structures explains why a large headline amount should not be treated as site-level funding without tracing the obligor, security package and use of proceeds.

Test the delivery chain, not only the lease

A pre-lease can be strong while the delivery chain remains weak. The building may lack a final connection date. Transformers may not be ordered. The cooling design may not match the tenant’s density. The commissioning plan may be incomplete.

The construction evidence needs the same discipline as the commercial evidence. On 22 September 2026, BDx announced the groundbreaking of its CGK4 campus in West Java, reporting a 640 MW campus plan, 845 MVA of secured grid power and phased commissioning over approximately three years. Those figures describe different things: planned campus capacity, utility supply and delivery sequence. They should not be collapsed into one “available MW” number.

For a leased phase, the due-diligence team should connect the commercial schedule to a critical path covering grid works, permits, design freeze, equipment manufacture, installation, energisation and commissioning readiness. Acceptance tests must be achievable and aligned with the systems actually being delivered. Otherwise, the tenant may be contracted but rent commencement remains uncertain.

A practical evidence hierarchy

I use a simple hierarchy when assessing a pre-lease.

First, confirm the parties and the legal instrument. Second, identify exactly what capacity is committed and on what date. Third, map every condition precedent and termination right. Fourth, verify that land, power, permits, design and procurement support the contracted delivery. Fifth, test whether financing is committed at the correct project level. Finally, reconcile public announcements with the source documents and site milestones.

This approach avoids two common errors. The first is treating every tenant-related announcement as contracted demand. The second is dismissing a conditional agreement as meaningless. A well-structured framework can be an important precursor to a lease, especially when it fixes the technical product and creates a credible timetable. It simply belongs in a different evidence category.

PowerlandMap’s role is to connect those categories across markets, sites, grid evidence, supply, delivery milestones and public commercial signals. The product overview shows how that evidence can support a shortlist or investment review without converting estimates into facts.

Conclusion: underwrite the obligation, not the headline

A data center pre-lease agreement is valuable when it converts commercial intent into enforceable obligations that match the physical project. The strongest evidence is not a large MW figure. It is a coherent chain from tenant credit and contract terms to land, power, permits, equipment, commissioning and rent commencement.

My view is straightforward: classify the agreement before valuing it. A conditional framework, a capacity reservation and a take-or-pay lease can all be useful, but they should never occupy the same line in an underwriting model. If the evidence chain is incomplete, keep the opportunity visible while preserving the uncertainty.

For teams comparing projects or validating a live transaction, request access to PowerlandMap to review the market, site, capacity and power evidence in one place.