LDDR Deep Dive — Critical Bankability Issues

This is the single most consequential structural shift between the two concession agreements and fundamentally alters the credit architecture of the entire project. In the Precedent CA, the Client is DGCL — a direct subsidiary of the Public Investment Fund of Saudi Arabia, which is a sovereign wealth fund with assets exceeding USD 930 billion. While PIF does not provide an explicit guarantee, the institutional heft and sovereign adjacency of PIF as the ultimate parent provides implicit credit comfort that permeates every commercial arrangement under the concession. SBDC, by contrast, is a subsidiary of Sports Boulevard Foundation — itself a giga-project vehicle established by Royal Order but without the balance sheet depth, track record, or institutional permanence of PIF. SBF is a development-phase entity whose financial capacity is entirely dependent on government funding allocations, which are not contractually committed beyond project-specific approvals. The chain of consequences is severe. First, the Client's ability to meet its payment obligations under the CA — particularly Termination Prices under Schedule 6, Compensation Event payments under Clause 37, and Change in Law compensation under Clause 36 — is only as strong as SBF's willingness and ability to fund SBDC. There is no parent company guarantee, no letter of comfort, and no commitment from the Saudi government to backstop SBF's obligations. Second, the Payment Security carve-out at Clause 45 means that where Building Owners are SBF affiliates (which, given the nature of the Sports Boulevard masterplan, is likely to include the majority of initial buildings), there is zero credit enhancement for the revenue stream. The Provider is exposed to affiliate counterparty risk with no security. Third, the absence of any financial capacity representation means that even at the date of signing, there is no contractual baseline against which to measure the Client's solvency. Lenders cannot point to a breached representation if SBDC becomes underfunded — they simply have an unsecured claim against an SPV. Fourth, unlike PIF-backed entities which benefit from a well-understood implicit sovereign support framework, SBF's funding depends on continued government prioritization of the Sports Boulevard giga-project. Saudi Vision 2030 reprioritizations — which have already affected NEOM and other giga-projects — could reduce SBF's funding envelope without triggering any contractual protection for the Provider or its lenders. The financial quantum is material: Termination Price A alone could exceed SAR 500 million in early operational years, and there is no assurance SBDC can fund this absent SBF support. For lenders, this means the termination compensation regime — the ultimate credit backstop in any BOOT concession — rests on an untested, undercapitalized counterparty.

In Saudi PPP/BOOT concessions, the gold standard is a PIF-backed or Ministry-backed client entity with either an explicit government guarantee or a government support agreement. The DGCL/PIF structure in the Precedent CA represents the upper end of creditworthiness in the Saudi market. The ISTP (Integrated Smart Transport Project) and KAFD district cooling concessions both featured government-adjacent counterparties with explicit support mechanisms. The SBF structure is more akin to entertainment or tourism giga-project SPVs (e.g., Seven or RCU subsidiaries) where government support is implicit but not contractually committed. For a project finance transaction requiring 15-25 year debt tenors, this level of counterparty uncertainty is below market standard. International comparators — UAE district cooling concessions (Empower, Tabreed) — typically feature either investment-grade rated off-takers or government-guaranteed minimum revenue commitments.

The demand risk profile has materially deteriorated compared to the Precedent in three compounding ways. First, the absolute capacity reduction from 26,254 RT to 23,499 RT represents a 10.5% decrease in the maximum addressable revenue base at the Initial Stage. This directly reduces the revenue ceiling against which debt service coverage ratios are modeled. For a capital-intensive BOOT concession where the Provider must fund the full district cooling network infrastructure regardless of connected load, a smaller revenue base increases the breakeven utilization rate and extends the payback period. Second, the 20,000 RT minimum CP threshold for Commercial Operation means that the Client need only deliver buildings representing 85.1% of the planned Initial Stage capacity before the Provider must accept Commercial Operation and begin the concession term countdown. In the Precedent, the equivalent threshold was proportionally higher relative to total capacity. The gap between the CP minimum (20,000 RT) and the planned capacity (23,499 RT) is 3,499 RT — representing approximately SAR 15-25 million per annum in potential stranded capacity costs if those buildings are delayed or never connected. The Provider bears the capital cost of oversizing the network for 23,499 RT but may only receive revenue from 20,000 RT. Third, and most critically, the 4,000 RT BAC cap for the first two Contract Years is a severe revenue suppression mechanism with no equivalent in the Precedent. The Building Allocated Capacity determines the billing base — the Provider can only charge for capacity up to the BAC, regardless of actual connected capacity or consumption. At 4,000 RT per building across 19 buildings, the maximum billable capacity in years 1-2 is 76,000 RT — but this is misleading because actual connected loads in early years will be far below BAC for most buildings. The real concern is for anchor buildings that may have actual demand exceeding 4,000 RT in early years. For these buildings, the Provider delivers cooling capacity above 4,000 RT but cannot bill for it. This creates an unfunded service obligation. The interaction between the 4,000 RT BAC cap and the Diversity Factor (Issue #4) further compounds the revenue suppression: the billable amount is BAC multiplied by Diversity Factor, meaning actual billable capacity per building in years 1-2 could be as low as 4,000 × 0.65 = 2,600 RT. Across the Initial Stage, this implies a worst-case billable base of approximately 49,400 RT before Diversity Factor, reducing to approximately 33,600 RT after Diversity Factor — against infrastructure sized for 23,499 RT of actual cooling delivery capacity. The lender's base case financial model must stress-test a scenario where (a) only 20,000 RT of buildings achieve COD, (b) BAC is capped at 4,000 RT for those that do, and (c) Diversity Factor reduces billing to 65% of BAC. In this downside case, year 1-2 revenue could be 40-50% below the level required for 1.20x DSCR.

In comparable Saudi district cooling BOOTs (KAFD, KAIA, Diriyah Gate), the initial capacity commitment is typically set at a level that supports base case debt service from COD, with capacity ramp-up provisions designed to protect (not penalize) the Provider. The 4,000 RT BAC cap in years 1-2 is unprecedented in Saudi district cooling concessions and appears to have been introduced to protect the Client/Building Owners from paying for capacity they have not yet fully occupied. This is a demand-side protection that has been inserted into a supply-side concession — a fundamental misallocation of risk. In UAE district cooling (Empower, Tabreed), minimum connection charges or take-or-pay structures ensure that the Provider recovers fixed costs from COD regardless of actual occupancy ramp-up. The absence of any take-or-pay or minimum revenue guarantee in the SBDC CA is a significant departure from regional market practice.

The Diversity Factor is an entirely novel concept in Saudi district cooling concessions with no equivalent in the Precedent CA, and its introduction represents a fundamental and permanent reduction of the Provider's revenue base by approximately 28-35%. The engineering rationale for a diversity factor is well-understood in HVAC system design: not all buildings in a district reach peak cooling demand simultaneously, so the central plant can be sized at less than the sum of individual building capacities. A diversity factor of 68.1% means the Client assumes that aggregate peak demand will be approximately 68% of the sum of individual building peak demands. However, while the diversity factor is an appropriate engineering concept for plant sizing, its application as a billing reduction is commercially unprecedented and deeply problematic. In every other district cooling concession — Saudi or international — the Provider bills based on connected capacity or contracted capacity, not on a statistically reduced capacity figure. The Provider incurs capital expenditure to install cooling capacity at each ETS based on the full ETS Maximum Cooling Capacity. The chiller plant, distribution pipework, heat exchangers, and control systems at each ETS are designed and costed for the full rated capacity. The Diversity Factor allows the Client to receive the benefit of full-capacity infrastructure while paying for only 65-72.55% of that capacity. The financial impact is staggering in its simplicity: for the Initial Stage with 23,499 RT of ETS Maximum Cooling Capacity, the billable base after Diversity Factor is 23,499 × 0.681 = 16,003 RT. This means the Provider must finance, build, and maintain infrastructure for 23,499 RT but can only bill for 16,003 RT — a permanent revenue haircut of 7,496 RT, equivalent to approximately SAR 30-50 million per annum in foregone Availability Charges alone. The interaction with the 4,000 RT BAC cap in years 1-2 (Issue #3) creates a double reduction: 4,000 RT × 0.681 = 2,724 RT of billable capacity per building. For a building with actual demand of 6,000 RT in year 1, the Provider delivers 6,000 RT of cooling but can only bill for 2,724 RT — a 54.6% revenue shortfall. The Diversity Factor also creates perverse incentives around plant sizing. If the Provider sizes the central plant based on the Diversity Factor (i.e., for 68.1% of aggregate BAC), and actual simultaneous demand exceeds this level, the Provider faces a Service Failure with potential KPI consequences (Issue #9) and ultimately Termination risk (Issue #50). But if the Provider sizes for full aggregate BAC to avoid this risk, it bears the capital cost of overcapacity that it can never bill for. There is no mechanism in the CA for the Diversity Factor to be adjusted if actual demand patterns differ from the assumed statistical profile. If occupancy patterns result in higher simultaneous demand (e.g., all buildings are offices with similar occupancy schedules rather than a mix of offices, retail, and residential), the 68.1% factor could be materially wrong, yet the Provider bears both the service delivery risk and the revenue suppression.

No Saudi district cooling BOOT concession reviewed — including DGCL/Diriyah Gate, KAFD, or KAIA — includes a Diversity Factor as a billing reduction mechanism. In international district cooling markets (Singapore, UAE, Qatar), diversity factors are used exclusively for plant sizing calculations and are never applied to reduce the billing base. The commercial standard is that each building pays based on its contracted or connected capacity regardless of system-wide diversity. Empower (Dubai) and Tabreed (Abu Dhabi) both bill on full contracted capacity with no diversity reduction. The introduction of the Diversity Factor in the SBDC CA appears to be an attempt by the Client to capture the engineering benefit of system diversity for its own account, rather than leaving this as a Provider efficiency gain (which is the universal market convention). This is a zero-sum transfer of value from Provider to Client with no precedent in the market.

The restructured Deemed Completion mechanism creates a bifurcated risk profile that is simultaneously beneficial and dangerous for the Provider, depending on which buildings are classified as anchor versus non-anchor. The beneficial aspect is clear: for non-anchor buildings, if the Client fails to deliver the building to a state where the ETS can achieve Commercial Operation by the Longstop Date, the Provider is deemed to have achieved COD and can begin billing. This protects the Provider from indefinite construction delay risk on non-anchor buildings. However, the mechanism contains several critical gaps. First, the carve-out of Anchor Building ETSs from the Deemed Completion mechanism means that delay to anchor buildings — which by definition represent the largest and most commercially significant buildings in the development — is not subject to deemed completion. If an anchor building is delayed beyond its Longstop Date, there is no automatic revenue protection for the Provider. The Provider has installed the full ETS infrastructure for the anchor building but cannot bill for it and has no deemed completion fallback. The financial impact of anchor building delay is disproportionate: anchor buildings typically represent 30-50% of total connected capacity. Second, the Deemed Commercial Operation Date triggers billing based on BAC, but the building may not physically be ready to receive cooling. The Provider is entitled to charge but may not be able to deliver cooling services because the building's secondary cooling systems, risers, or internal distribution have not been completed. This creates a phantom revenue entitlement — the Provider can invoice, but the Building Owner may dispute payment on the basis that no cooling can physically be consumed. The CA does not explicitly address whether the Building Owner's payment obligation is unconditional once Deemed COD is triggered, or whether it is conditional on the Provider actually being able to deliver cooling to the building's boundary point. Third, there is an interaction with the KPI regime (Issue #9): if the Provider is deemed to have achieved COD for a building but cannot actually deliver cooling because the building is incomplete, any subsequent service metrics that reference that building could be adversely affected. The Provider may be measured on service availability for a building it cannot physically serve. Fourth, the Longstop Date itself is a negotiated date that may include substantial float. If the Longstop Date is set too generously (e.g., 24 months after planned COD), the Provider bears extended construction and financing carry costs before deemed completion kicks in. The cost of carrying completed but non-billing infrastructure for 12-24 months while waiting for deemed completion is material — estimated at SAR 3-8 million per ETS in financing costs alone.

Deemed completion provisions are standard in GCC district cooling concessions and typically apply uniformly to all buildings. The Precedent CA (DGCL) applied deemed completion across all buildings without an anchor/non-anchor distinction. The carve-out of anchor buildings from deemed completion is unusual and appears to reflect the Client's position that anchor buildings are so critical to the masterplan that the Provider should not be entitled to bill on a deemed basis if the building is delayed — instead, the Provider should wait for actual completion. This is commercially unreasonable given that the Provider must size and install ETS infrastructure in advance of building completion. In Abu Dhabi district cooling concessions (Al Maryah Island, Saadiyat), deemed completion applies to all connected buildings with no exceptions, and payment obligations are unconditional from the deemed date.

The reduction of KPI thresholds from 50/90 to 30/60 represents a 40% tightening of the performance regime with no corresponding reduction in the severity or frequency of individual failure point allocations. This is not a proportional adjustment — it is a step-change in termination risk that fundamentally alters the operating risk profile of the concession. To understand the severity: if individual KPI failure events carry the same point values as the Precedent (typically 1-5 points per event depending on severity and duration), the Provider in the Precedent could sustain approximately 10-50 individual failure events before reaching the Warning threshold. Under the new CA, the Warning threshold is reached after 6-30 events — a dramatically smaller operational buffer. For the Persistent Breach threshold that triggers termination rights, the Precedent allowed approximately 18-90 events, while the new CA allows only 12-60. In a district cooling system serving 19+ buildings across a large urban masterplan, operational incidents are inevitable. Equipment failures, power supply interruptions, control system faults, and distribution network issues occur in every district cooling system globally. The question is not whether failure points will be accumulated, but whether the threshold provides sufficient headroom for normal operational variability. A 30-point Warning threshold in a 19-building system means that an average of fewer than 2 failure events per building per year triggers a Warning. At a 60-point Persistent Breach threshold, an average of approximately 3 failure events per building per year triggers termination. These are extraordinarily tight parameters for a district cooling system in a construction-phase masterplan where surrounding infrastructure is still being built, utility supplies may be intermittent, and building completion is staggered. The interaction with the Deemed Completion mechanism (Issue #7) compounds this risk: if the Provider is deemed to have achieved COD for a building that is not physically ready to receive cooling, any subsequent service failures at that building accumulate failure points even though the failures are attributable to the building's incomplete state rather than the Provider's systems. The interaction with the Diversity Factor plant-sizing dilemma (Issue #4) adds further risk: if the Provider sizes the plant to the Diversity Factor to optimize capital expenditure, any simultaneous demand exceeding the Diversity Factor level could result in supply shortfalls across multiple buildings simultaneously, generating cascading failure points that could breach the 30-point threshold in a single high-demand day. The termination consequence is severe: at 60 points, the Client can terminate for Provider Default, which triggers Termination Price C (the least favorable termination price for the Provider, excluding IRR-based equity components). The Provider therefore faces a regime where normal operational incidents, compounded by Client-side building delays and a structurally undersized billing base, could trigger a default termination at the worst possible price.

The Precedent CA's 50/90 thresholds are consistent with other Saudi district cooling concessions. In UAE district cooling concessions (Empower, Tabreed), KPI regimes typically feature even more generous thresholds, recognizing the operational complexity of multi-building district cooling networks. The 30/60 thresholds in the SBDC CA are the tightest KPI regime seen in any GCC district cooling BOOT concession. By comparison, KSA water and wastewater PPPs (which involve simpler single-plant operations) typically feature Warning thresholds of 40-60 points. Setting district cooling thresholds below water utility thresholds suggests a misunderstanding of the relative operational complexity. International best practice (ASHRAE, IDEA guidelines) recognizes that multi-building district cooling systems have inherently higher operational variability than single-building systems due to the distributed nature of the infrastructure.

The termination compensation regime is the ultimate credit backstop for lenders in a BOOT concession — it is the mechanism that ensures that if the concession fails for any reason, the Financing Parties recover their outstanding debt. The structural changes in the SBDC CA create material gaps in this credit backstop that go to the heart of the project's bankability. Starting with the Senior Creditor Claims definition: this is the foundation of all four Termination Prices and must, at minimum, cover the outstanding principal and accrued interest on senior debt facilities, hedging breakage costs, LC cash collateral requirements, and other financing costs. The definition must be crafted to capture all amounts that would become due and payable upon early termination of the financing arrangements, including swap close-out amounts, commitment fee breakage, and any penalty interest triggered by the termination. In the Precedent CA, Senior Creditor Claims included a floor equal to the higher of (a) the aggregate outstanding principal and accrued interest under all Senior Finance Documents, and (b) the fair market value of the debt (calculated to ensure lenders are not disadvantaged by below-market interest rates). The new CA's Senior Creditor Claims definition must be scrutinized to ensure this floor is preserved, as any reduction could result in lenders recovering less than their outstanding principal — a fatal flaw for debt bankability. The removal of a standalone Voluntary Termination price and its merger into Termination Price A is less concerning if the merged Price A provides equivalent or better compensation. However, the characterization matters: under many project finance frameworks, a lender's risk model distinguishes between voluntary termination (a creditworthy Client choosing to terminate, typically the lowest risk) and default termination (a dispute-driven termination, higher risk). Merging these categories could affect credit rating agency assessments and debt pricing. The Fixed Adjusted Net Equity and Political Event Net Equity components introduce IRR-based equity recovery calculations. These are inherently more complex and disputable than simple equity-at-cost recovery mechanisms. An IRR-based calculation requires agreement on the base case financial model, the applicable IRR, and the methodology for calculating the equity recovery. Disputes over these inputs can delay termination payments for years. More critically, the IRR-based approach means the equity recovery component is sensitive to the base case assumptions — and if the base case proves optimistic (due to Diversity Factor revenue suppression, BAC caps, or lower-than-projected demand), the IRR may never be achieved even in an operating scenario, making the termination compensation less meaningful. Termination Price C (Provider Default) is the most concerning from a lender perspective. If it covers Senior Creditor Claims only with no equity recovery, the Provider's shareholders lose their entire equity investment upon Provider Default. While this is commercially logical (the defaulting party should not profit from termination), the Senior Creditor Claims floor mechanism must be robust enough to ensure lenders recover 100% of outstanding debt plus costs. Any leakage — for example, if swap breakage costs are excluded or if the floor fails to account for accrued but unpaid interest — could result in a lender shortfall on Provider Default termination. This would make the project structurally unbankable, as no lender will accept the risk that a Provider operational default (particularly one driven by the tightened KPI regime at Issue #9) results in an under-recovery of senior debt.

The four-tier termination price structure (Client Default, Force Majeure, Provider Default, Construction Default) is consistent with Saudi PPP market practice and GCC BOOT conventions. The inclusion of IRR-based equity recovery is common in Saudi PPP concessions (ISTP, water PPPs) but requires careful calibration. The Precedent CA's approach — with a clear Senior Creditor Claims floor and separate Voluntary Termination category — is more closely aligned with international project finance standards (EPEC, World Bank PPP guidance). The merger of Voluntary Termination into Price A is acceptable provided the economic outcome is equivalent. The critical gap versus market standard is the absence of a government guarantee or Parent Company Support Agreement backing the Client's termination payment obligations (cross-reference Issue #1). Without such support, the Termination Prices are contractual entitlements against an undercapitalized SPV — a structural weakness that no amount of drafting refinement can fully cure.

The Local Content regime is an entirely new regulatory overlay that has no equivalent in the Precedent CA and introduces a category of risk that is fundamentally different from the operational and commercial risks traditionally managed in a BOOT concession. This is not a commercial negotiation point — it reflects the Saudi government's Saudization and local content policies under Vision 2030 — but the contractual implementation creates bankability concerns that must be addressed. The 49% Local Content Target is extremely ambitious for a district cooling concession. The core equipment in a district cooling system — centrifugal chillers, variable speed drives, heat exchangers, cooling towers, and control systems — is manufactured almost exclusively by international OEMs (Carrier/Trane, York/Johnson Controls, Daikin, Siemens). There is currently no Saudi manufacturer of large-capacity centrifugal chillers (>500 RT). The control systems (BMS, SCADA) are invariably supplied by international companies (Honeywell, Schneider, Siemens) with limited local manufacturing content. This means the 49% target must be achieved primarily through local content in civil works, piping, electrical installation, and operational workforce. For a capital-intensive, equipment-heavy project like district cooling, achieving 49% local content requires either (a) sourcing significantly more expensive local alternatives for equipment that is manufactured more cost-effectively abroad, or (b) inflating the local content measurement through creative accounting of soft costs and labor. Either approach increases project cost without corresponding revenue benefit. The LD penalty mechanism creates a direct P&L impact: for each percentage point below 49%, the Provider pays liquidated damages. If the achievable local content is realistically 35-40% (a reasonable estimate for a district cooling project), the annual LD exposure is 9-14 percentage points × LD rate per point. Depending on the LD rate, this could represent SAR 5-20 million per annum in penalties — a permanent drag on project returns that was not contemplated in the Precedent CA or in any base case financial model for a Saudi district cooling concession. More critically, Schedule 23 Part 5's escalation to Provider Default means that persistent Local Content underperformance — which may be driven entirely by supply chain constraints outside the Provider's control — can trigger termination at Termination Price C. The Provider could operate a technically flawless district cooling system, achieve perfect KPIs, and still face default termination because Saudi suppliers cannot manufacture centrifugal chillers. This conflation of supply chain policy compliance with operational default is commercially unreasonable and is not seen in any other Saudi PPP/BOOT concession. The measurement methodology in Schedule 23 is also critical: how is local content measured? Is it by value, by weight, by headcount? Does the methodology include supply chain tiers (i.e., is a Trane chiller assembled in Saudi Arabia from imported components counted as local content)? These definitional questions have massive financial consequences and must be resolved with certainty before Financial Close. The interaction with the financial model is particularly concerning: the base case model will project returns based on an assumed cost structure. If the Provider must pay higher prices for local content items (or pay LDs for shortfalls), the actual returns will be below the base case. This means the financial model's DSCR projections are overstated unless they incorporate a local content cost premium or LD provision — neither of which is standard in district cooling financial modeling.

Local Content requirements are increasingly common in Saudi government contracts following the issuance of the Local Content and Government Procurement Authority (LCGPA) regulations. However, the 49% target and the LD/default termination penalty structure are significantly more aggressive than current market practice for infrastructure PPPs. Saudi water PPPs typically include local content targets of 30-40% with softer enforcement mechanisms (reduced scoring in future bids, reporting requirements) rather than LDs and default termination. The ISTP concession includes local content provisions but at lower targets and without default termination consequences. International comparators: Abu Dhabi's ICV (In-Country Value) regime for oil & gas sets targets of 40-60% but applies primarily to procurement scoring, not contract termination. The SBDC CA's approach of making Local Content shortfall a termination event is at the extreme end of global practice.

The distinction between a lease and a sublease is of fundamental importance to the security package available to Financing Parties and therefore to the bankability of the project. Under Saudi law, a sublease is a derivative interest — it exists only so long as the head lease from which it derives remains in force. This creates a structural vulnerability that does not exist with a direct lease. First, the Provider's sublease terminates automatically if the Head Lease terminates or expires, regardless of whether the Provider is in default or has any responsibility for the Head Lease termination. If the Client (SBDC) defaults under the Head Lease — for example, by failing to pay rent to the Royal Commission — the Head Lease could be terminated, and the Provider's sublease would terminate as a consequence. The Provider would lose its right to occupy the land on which it has built and operates the district cooling infrastructure, through no fault of its own. This is a catastrophic risk for lenders: the entire physical asset base (chillers, distribution network, ETSs) becomes stranded on land the Provider no longer has the right to occupy. Second, the pledgeability of the sublease interest is legally uncertain under Saudi law. The Saudi Registered Real Estate Mortgage Law (enacted under Royal Decree M/49) permits the mortgage of real estate rights, including leasehold interests. However, the legal treatment of a sublease mortgage is less established than the mortgage of a direct lease. A mortgage of a sublease raises the question of whether the mortgagee (the Financing Parties' security agent) acquires a right superior to, equal to, or subordinate to the head lessor's rights. If the head lessor's rights are superior — which is the conventional position — the security interest is effectively subordinate to the Head Lease, and any enforcement of the mortgage security is subject to the Head Lease remaining in force. Third, the Financing Parties' step-in rights under the CA Direct Agreement (Schedule 20) may be impaired by the sublease structure. If the Financing Parties step in following a Provider Default, they step into the Provider's sublease interest. But if the Head Lease contains restrictions on sublessee assignment or transfer (which head leases commonly do), the step-in may require head lessor consent. If such consent is not obtained or is unreasonably withheld, the step-in fails and the Financing Parties cannot exercise their most fundamental credit protection mechanism. Fourth, the Head Lease term must be co-terminus with or longer than the sublease/concession term. If the Head Lease expires before the concession term, the sublease automatically terminates, and the Provider and its Financing Parties lose all rights to the project assets. The CA must contain a representation and warranty that the Head Lease term covers the full concession term plus any extensions. Fifth, there is a registration requirement: under Saudi law, leases exceeding one year must be registered at the General Authority for Real Estate. A sublease must similarly be registered, and the question arises whether a mortgage of a sublease can be registered in the same manner as a mortgage of a primary lease. Any registration deficiency could render the security interest unenforceable.

In the Precedent CA (DGCL/Diriyah Gate), the Provider receives a direct lease — a primary real estate interest that is not derivative of or subordinate to another interest. This is the standard structure in Saudi BOOT concessions where the government entity (or its subsidiary) holds the freehold/usufruct and grants a direct lease to the concessionaire. Direct leases are clearly pledgeable under the Saudi Registered Real Estate Mortgage Law and are the basis for real estate security in virtually all Saudi project finance transactions. The sublease structure in the SBDC CA appears to reflect the Client's own land position: SBDC does not own the land (SBF or the Royal Commission does), and SBDC holds only a head lease. This is a structural constraint rather than a negotiated position, but it does not relieve the parties of the obligation to ensure that the Provider's and Financing Parties' interests are adequately protected. In UAE district cooling concessions, master developers typically grant direct subleases with head lessor consents and non-disturbance agreements already in place, creating a de facto primary interest for the concessionaire.

This exemption eviscerates the Payment Security regime for what is likely to be the majority of Building Owners in the Sports Boulevard development. The Sports Boulevard masterplan is an SBF initiative — the buildings within it are being developed by SBF or its subsidiaries and affiliates. The initial buildings listed in Schedule 3 are predominantly SBF-related developments. This means that the Payment Security requirement — which exists to protect the Provider from Building Owner non-payment under CSAs — is effectively inapplicable to the core revenue base. The consequences cascade through the entire revenue and credit structure. The Provider delivers cooling services to affiliated Building Owners, invoices monthly Cooling Charges, and has zero security if those Building Owners fail to pay. The only recourse is contractual — a claim for damages against the defaulting Building Owner (an SBF affiliate SPV that may have minimal assets beyond the building itself) or escalation through the CA's dispute resolution mechanism. There is no letter of credit, no bank guarantee, no cash deposit, and no parent company guarantee standing behind these payment obligations. The interaction with the counterparty risk analysis (Issue #1) is direct: the Payment Security exemption means that SBF-affiliated Building Owners — the counterparties whose creditworthiness is most dependent on continued government funding of the Sports Boulevard project — are the very counterparties exempt from providing credit enhancement. This is precisely backwards from a credit perspective. The weakest counterparties receive the most favorable treatment. For lenders, this creates a revenue concentration risk: a large proportion of the Provider's revenue comes from affiliated counterparties with no payment security. If SBF faces funding difficulties and its subsidiaries cannot pay Cooling Charges, the Provider's revenue collapses without any security buffer. The Provider cannot draw on letters of credit or call on guarantees — it must pursue unsecured claims against potentially insolvent SPVs. The financial model impact is severe: lenders will need to stress-test a scenario where 50-70% of Building Owner revenue is unsecured. Under standard project finance conventions, unsecured revenue from low-rated or unrated counterparties requires significantly higher DSCR coverage (1.40x-1.50x vs 1.20x for secured revenue), which increases the equity requirement and reduces the project's return profile. The new CA also introduces Transferee Building Owner Non-Payment as a termination ground — meaning that if a building is transferred to a new owner who then fails to pay, this can trigger termination consequences. But if the original affiliated Building Owner is not required to provide Payment Security, there is no security to transfer to the replacement owner either. The entire chain is unsecured.

In the Precedent CA (DGCL), all Building Owners — including PIF affiliates — were required to provide Payment Security. This is the universal standard in GCC district cooling concessions. Empower (Dubai) and Tabreed (Abu Dhabi) require Payment Security from all connected customers regardless of affiliation, typically in the form of a bank guarantee or cash deposit equal to 2-3 months of estimated cooling charges. The exemption of affiliated Building Owners from Payment Security is unprecedented in the GCC district cooling market and would not be accepted by any project finance lender without substantial mitigating measures. Even in government-guaranteed off-take structures (e.g., Saudi ISTP), the government entity provides a separate payment guarantee rather than simply exempting itself from security requirements.

The CSA structure creates a fundamental tension in the project's credit architecture: the Provider's revenue comes not from the Client (SBDC) but from individual Building Owners through bilateral CSAs. The Client is the concession counterparty but is not the revenue counterparty. This fragmentation of the revenue stream across multiple Building Owner counterparties — each with its own creditworthiness, payment behavior, and dispute potential — creates a credit profile that is materially more complex and risky than a single-counterparty off-take structure. In the Precedent CA (DGCL), while the same CSA structure existed, the practical reality was that all initial buildings were DGCL/PIF-owned, creating de facto counterparty concentration in a high-credit-quality entity. In the SBDC CA, the Building Owner universe is more diverse: some buildings will be SBF affiliates (exempt from Payment Security per Issue #45), some may be third-party developers within the masterplan, and over time buildings may be sold to end-users who become Transferee Building Owners. Each counterparty transition introduces credit risk, operational risk (handover of secondary systems), and potential payment disruption. The Transferee Building Owner Non-Payment concept is a new risk category not present in the Precedent. When a building is sold, the buyer becomes the Building Owner and assumes the CSA obligations. If this buyer fails to pay Cooling Charges, the Provider has limited recourse: it can pursue the Transferee Building Owner (who may be a property investor with no relationship to SBF), but it cannot easily disconnect cooling services (as this would affect building occupants and potentially trigger KPI consequences). The Provider is trapped between non-payment by the Transferee Building Owner and service obligation penalties if it reduces service. The Client's role in this scenario is critical but unclear: does the Client guarantee that each Building Owner (including Transferee Building Owners) will pay? Is the Client obligated to step in and cover shortfalls? The CA must contain a clear Client backstop obligation for Building Owner defaults. Without this, the Provider bears counterparty risk for entities it did not select and cannot control. From a lender perspective, revenue fragmentation across multiple CSA counterparties requires a security structure that captures all payment streams — either through an account bank arrangement (where all CSA payments flow through a lender-controlled revenue account) or through individual Payment Security from each Building Owner. The affiliate exemption (Issue #45) removes half of this security architecture. The remaining third-party Building Owners may provide Payment Security, but the overall revenue stream is a patchwork of secured and unsecured components, making cash flow waterfall modeling significantly more complex and uncertain.

The CSA structure is standard in GCC district cooling concessions — it is the universal commercial model. However, in every comparable project, the credit framework addresses counterparty fragmentation through one or more of: (a) universal Payment Security (Empower, Tabreed); (b) master developer guarantee for all Building Owner obligations (common in UAE free zone developments); (c) government guarantee for minimum aggregate revenue (ISTP model); or (d) disconnection rights for non-paying Building Owners without KPI penalty (Empower standard terms). The SBDC CA provides none of these protections for affiliated Building Owners and introduces Transferee Building Owner risk without a corresponding Client backstop. This is below market standard for bankable district cooling concessions.

The expansion of Provider Default triggers from the Precedent CA to the new CA represents a cumulative tightening that significantly increases the probability of a default termination event over the concession term. The concern is not any single trigger in isolation but the aggregate effect of multiple new and tightened triggers operating simultaneously. The Provider now faces default exposure from three independently operating regimes: KPI performance (tightened from 90 to 60 points — see Issue #9), Local Content compliance (entirely new — see Issue #24), and Transferee Building Owner payment enforcement (entirely new). Each regime operates independently with its own measurement period, cure provisions, and escalation pathway. A Provider that is performing adequately on two of three regimes but marginally failing on the third still faces default termination. The cumulative probability of breaching at least one of three independent default triggers is significantly higher than the probability of breaching a single trigger. If each trigger has a 15% probability of being breached over the concession term (a reasonable estimate given the tightened KPI thresholds and the ambitious Local Content target), the probability of at least one breach is approximately 1 - (0.85)³ = 38.6%. Under the Precedent CA with a single KPI trigger at more generous thresholds, the equivalent probability might be 5-10%. The Transferee Building Owner Non-Payment trigger is particularly problematic because it penalizes the Provider for a third party's payment default. If a building is sold to a new owner who then fails to pay Cooling Charges, the Provider is expected to enforce the CSA against the Transferee Building Owner. If enforcement fails (perhaps because the Transferee is insolvent or disputes the charges), the Client can characterize this as a Provider Default — even though the Provider has no control over the Transferee's financial position and did not select the Transferee as a counterparty. The attribution requirement (where attributable to Provider's failure to enforce CSA) provides some protection, but the boundary between failure to enforce and inability to enforce is legally uncertain and likely to be disputed. The consequence of Provider Default is Termination Price C — the least favorable termination price, which provides Senior Creditor Claims coverage but no equity recovery (or limited equity recovery depending on the exact drafting). For the Provider's shareholders, this means total or near-total loss of equity. For lenders, it means reliance on Senior Creditor Claims being sufficient to cover all outstanding debt and financing costs — a proposition that depends entirely on the robustness of the Senior Creditor Claims definition (Issue #12). The cumulative effect is that the Provider operates in a permanently elevated state of default risk, with three independently operating guillotine mechanisms. This affects not only the probability of termination but also the Provider's operational behavior: management will be forced to allocate disproportionate resources to KPI monitoring, Local Content compliance, and Building Owner payment enforcement, potentially at the expense of operational efficiency and capital investment optimization.

In the Precedent CA (DGCL), Provider Default triggers were limited to KPI Persistent Breach (at 90 points), material unremedied breach, insolvency, abandonment, fraud, and Longstop Date failure. This is consistent with Saudi and GCC market standard for BOOT concessions. The addition of Local Content failure and Transferee Building Owner Non-Payment as standalone default triggers is unprecedented in GCC district cooling concessions. In international PPP practice (UK PFI, Australian PPP), provider default triggers are typically limited to service performance failures, financial defaults, and integrity events. Regulatory compliance failures (analogous to Local Content) are addressed through contractual remedies (LDs, penalties) rather than termination rights, recognizing that regulatory compliance is a continuing obligation that may fluctuate and should not trigger the nuclear option of default termination.

The pledgeability of the sublease interest is the linchpin of the Financing Parties' security package and therefore of the project's bankability. If the sublease cannot be effectively pledged, or if the pledge can be defeated by the head lessor's rights, the Financing Parties lose their primary real estate security and must rely solely on contractual assignment of the concession rights (which terminate on CA termination) and moveable asset pledges (which may have limited standalone value without the land interest). Under Saudi law, the legal framework for real estate security is governed primarily by the Registered Real Estate Mortgage Law (Royal Decree M/49, dated 1433H/2012), its implementing regulations, and the Real Estate Registration Law. The Mortgage Law permits the mortgage of real estate rights, including leasehold interests, provided the mortgage is registered with the competent authority (the General Authority for Real Estate). However, the Law was drafted primarily with reference to primary ownership and lease interests, and the treatment of sublease mortgages is not explicitly addressed. This creates legal uncertainty on several fronts. First, registration: the General Authority for Real Estate may require the head lease to be registered before a sublease can be registered, and may require the head lessor's consent to the registration of a mortgage over the sublease. If the head lessor (the Royal Commission for Riyadh City) does not consent or if administrative procedures do not accommodate sublease mortgage registration, the security interest may be unregisterable and therefore unenforceable against third parties. Second, priority: even if the sublease mortgage can be registered, its priority relative to the head lessor's rights is unclear. If the head lease is terminated (for Client default or otherwise), does the mortgage survive? The conventional position under Saudi law is that subsidiary rights terminate with the primary right from which they derive — meaning the sublease mortgage would terminate with the sublease, which terminates with the head lease. This circular vulnerability means the mortgage provides security only so long as the head lease remains in force — and the Financing Parties have no direct relationship with or control over the head lessor. Third, enforcement: if the Financing Parties need to enforce their mortgage (following a Provider Default and failed step-in), the enforcement mechanism under the Mortgage Law involves judicial sale or private sale. A judicial sale of a sublease interest raises practical difficulties: what bidder will acquire a sublease that (a) is subordinate to a head lease that could be terminated, (b) requires compliance with the CA's operational obligations, and (c) is subject to Client and potentially head lessor consent to transfer? The pool of potential purchasers is extremely limited, and the sale price will reflect these constraints. Fourth, the interaction with the CA Direct Agreement's step-in rights: the step-in mechanism assumes the Financing Parties (or their nominee) can step into the Provider's shoes, which includes stepping into the sublease. If the sublease requires head lessor consent for assignment (which head leases typically do), the step-in is conditional on obtaining such consent. If consent is withheld — even unreasonably — the Financing Parties' primary credit protection mechanism fails. The combined effect of these uncertainties is that the real estate component of the security package — which in a direct lease structure would be the most valuable and reliable security — is structurally impaired by the sublease construct. Lenders will need to commission a Saudi law legal opinion confirming the pledgeability of the sublease interest, the registration requirements, and the survival of the pledge on head lease termination. If this opinion cannot be delivered in satisfactory terms, the project may be structurally unbankable regardless of the commercial terms.

In the Precedent CA (DGCL), the Provider received a direct lease interest that is clearly pledgeable under Saudi law and has been successfully pledged in numerous Saudi project finance transactions. The direct lease structure is the market standard for Saudi BOOT/PPP concessions — all major Saudi project finance transactions (ISTP, Jubail 3A/3B IWP, Rabigh 3 IWP, Taiba/Qassim IPPs) involve direct lease or usufruct interests that are pledged to Financing Parties without the sublease complication. In UAE project finance, where sublease structures are more common due to the freehold/leasehold system, the practice is to obtain a Non-Disturbance Agreement from the head lessor and a legal opinion confirming sublease pledgeability — these are standard conditions precedent to financial close. The absence of these protections in the SBDC CA is a significant gap. Saudi Arabia's real estate security framework is relatively new and still developing. The General Authority for Real Estate's procedures for sublease mortgage registration have not been widely tested in project finance contexts. Lenders and their Saudi counsel will be conservative in their assessment of this risk.