Navigating Capital Stack Risks for Large-Scale Infrastructure Feasibility

Introduction: Why the Capital Stack Demands Rigorous Feasibility Analysis

In large-scale infrastructure, the capital stack is more than a funding list—it's a risk allocation mechanism that can determine project survival. Every tranche of capital carries distinct return expectations, seniority, and control rights, and the feasibility phase is the last chance to align these layers before commitments lock in. This guide draws on widely shared professional practices as of April 2026; verify critical details against current official guidance where applicable. We focus on the decisions that experienced teams face: how to model risk across the stack, negotiate terms that preserve flexibility, and test scenarios that reveal hidden vulnerabilities.

A common mistake is treating feasibility as a purely technical exercise—engineering design, environmental impact, market demand—while underestimating how capital structure interacts with these factors. For example, a toll road project may show strong traffic projections, but if its debt service coverage ratio assumes 95% of projected revenue and a recession cuts traffic by 20%, the entire stack unravels. The senior lender may force a restructuring that wipes out equity, while mezzanine holders face deferral or conversion. Feasibility analysis must therefore model not just expected cash flows, but the behavior of each capital layer under stress.

We'll walk through the key risk categories: construction risk, revenue risk, regulatory risk, and financing risk. Each has different implications for different tranches. For instance, construction risk (cost overruns, delays) primarily threatens equity and subordinated debt, while senior lenders may be protected by completion guarantees. But if the guarantee is weak or the sponsor's balance sheet is thin, even senior debt faces impairment. The capital stack thus becomes a chain of dependencies, and feasibility analysis must test each link.

Defining the Capital Stack for Infrastructure

The capital stack typically includes senior debt (often 60-70% of project cost), subordinated debt or mezzanine (10-20%), equity (15-30%), and sometimes grants or concessional loans. Senior debt has first claim on cash flows and assets, lowest risk, and lowest return. Mezzanine is unsecured or subordinated, often with warrants or conversion features. Equity is the residual claimant, highest risk, and highest return. Feasibility analysis must evaluate whether the projected returns justify the risk for each layer, and whether the structure as a whole is robust to plausible adverse scenarios.

Why Feasibility Phase Is Critical

During feasibility, the project team can still adjust capital structure—adding a tranche of concessional debt, increasing equity cushion, renegotiating offtake agreements. Once financing closes, changes are costly and require unanimous consent. This is the moment to stress-test the stack with realistic downside scenarios, not just base case projections. Many projects that fail after construction could have been saved with a more resilient capital structure designed during feasibility.

Risk Allocation Across Capital Tranches: Who Bears What?

The central principle of capital stack risk is that each tranche has a different risk appetite and loss absorption capacity. Senior lenders prioritize repayment certainty; they impose covenants, require debt service reserves, and may demand completion guarantees. Mezzanine investors accept higher risk for higher yield, often taking a second lien or convertible notes. Equity sponsors are the first to lose money but also capture upside. Feasibility analysis must explicitly map how each risk event (cost overrun, revenue shortfall, regulatory change) flows through the stack.

For instance, consider a 500 MW solar farm with a capital stack of 70% senior debt, 15% mezzanine, 15% equity. The power purchase agreement (PPA) is fixed for 20 years, but a key risk is panel degradation or inverter failure reducing output by 10% after year 10. In the base case, debt service coverage ratio (DSCR) is 1.4x. Under the 10% output reduction, DSCR drops to 1.1x—still above the 1.0x default threshold, but mezzanine interest may not be fully paid. Equity returns fall from 12% to 4%. The mezzanine investor, who expected 9%, now gets 5% and may face deferral. This simple scenario shows how a moderate operational risk affects each layer differently.

Senior Debt: The Risk-Averse Anchor

Senior lenders conduct thorough due diligence, often requiring independent engineer reports, market studies, and legal opinions. They insist on covenants: minimum DSCR (e.g., 1.2x), loan life coverage ratio (LLCR), and reserve accounts. Their main risk is default, which is rare in well-structured projects but can occur if construction delays exceed the grace period or if revenue collapses. Feasibility must demonstrate that even under stressed conditions, senior debt service can be met. This often means sizing the loan conservatively—say, 60% of project cost instead of 70%—to leave a larger equity cushion for unexpected shocks.

Mezzanine and Subordinated Debt: The Buffer Zone

Mezzanine fills the gap between senior debt and equity. It typically has higher interest rates (12-15%) and may include payment-in-kind (PIK) features that allow interest to accrue rather than be paid in cash. The risk is that if cash flow is insufficient, mezzanine payments are deferred or converted to equity. Feasibility must model scenarios where mezzanine is not paid for several years, and assess whether the project can survive with accrued interest compounding. In some cases, mezzanine holders may take control if equity is wiped out.

Equity: The First Loss Piece

Equity is the residual claimant—it only gets paid after all other obligations are met. In exchange, equity holders capture any upside beyond debt service. Feasibility analysis must show that the expected equity return (IRR) compensates for the risk of total loss. A typical target is 12-15% for infrastructure, but this varies by risk profile. If the base case IRR is 10% but the downside case yields -5%, the project may be too risky for equity unless there is a strategic rationale (e.g., entering a new market).

Stress Testing the Capital Stack: Scenarios and Sensitivity Analysis

Stress testing is the core of feasibility. It involves modeling the capital stack under a range of adverse scenarios and observing which tranches absorb losses. Standard approaches include sensitivity analysis (changing one variable at a time) and scenario analysis (combining multiple shocks). For large-scale infrastructure, the most critical variables are: construction cost overruns (typically 10-30%), revenue shortfalls (due to lower demand, pricing pressure, or regulatory changes), and financing cost increases (interest rate hikes, wider credit spreads).

One team I read about (anonymized for confidentiality) was evaluating a greenfield port terminal. The base case assumed a 15% equity IRR. The sponsor initially proposed a capital stack with 75% senior debt, 10% mezzanine, 15% equity. Stress testing revealed that a 20% construction cost overrun combined with a 15% revenue shortfall in the first three years would push the DSCR below 1.0x, triggering a default. The mezzanine would convert to equity, diluting the original sponsors to 5% ownership. The team then adjusted the stack: they increased equity to 25%, reduced senior debt to 65%, and added a 10% standby equity facility. This improved the downside IRR to 6% and kept DSCR above 1.1x even under stress. The project proceeded, and although costs overran by 18%, the equity cushion absorbed the shock without default.

Building a Stress Test Model

A robust model includes: (1) a deterministic base case with detailed assumptions; (2) a set of stress variables with ranges (e.g., ±20% for revenue, ±15% for O&M costs); (3) correlation assumptions (e.g., cost overruns often coincide with revenue delays); (4) output metrics for each tranche: DSCR, LLCR, equity IRR, mezzanine yield. The model should also calculate the probability of each scenario, using historical data or expert judgment, and aggregate expected loss for each tranche. This helps in negotiating risk premiums and covenant levels.

Common Pitfalls in Stress Testing

One pitfall is using overly optimistic recovery rates. In a default, senior lenders may recover 70-90% of principal, but mezzanine recovery is often 30-50%, and equity near zero. Another pitfall is ignoring tail risks—extreme events like a pandemic or regulatory ban. While rare, these can wipe out the entire stack. Feasibility should include at least one severe scenario (e.g., 5-year recession) to assess survivability. Finally, teams often forget to model the dynamic response of the capital stack—for instance, if a covenant breach triggers a mandatory prepayment or equity injection. These features can either save the project or accelerate its collapse.

Comparing Financing Structures: Project Finance, PPP, and Corporate Finance

The choice of financing structure profoundly affects capital stack risk. Three common structures for large-scale infrastructure are project finance (non-recourse or limited recourse), public-private partnerships (PPP), and corporate finance (on-balance-sheet). Each has distinct risk allocation mechanisms, cost of capital, and feasibility requirements. Below is a comparison table summarizing key differences, followed by detailed discussion.

Project Finance: High Leverage, High Complexity

Project finance is common for large, standalone projects with predictable cash flows (e.g., toll roads, power plants). The capital stack is heavily leveraged, often 80-90% debt, with senior lenders relying on project revenues and contracts. Risks are allocated via off-take agreements (e.g., power purchase agreements), construction contracts (fixed-price, date-certain), and operating agreements. Feasibility must ensure that each contract is creditworthy and that the project can survive without sponsor support. The main risk is that a counterparty (e.g., offtaker) defaults, leaving the project without revenue. Stress testing should include counterparty credit downgrades.

Public-Private Partnerships: Shared Risk with Government

PPPs involve a government concession where the private sector builds, operates, and transfers the asset. The capital stack often includes government subsidies or guarantees, reducing risk for private lenders. However, PPPs come with political risk—changes in government policy, tariff renegotiations, or early termination. Feasibility must include a robust legal framework and dispute resolution mechanism. The key metric is value for money: does the PPP deliver lower cost than public procurement? Risk transfer to the private sector must be real, not just nominal. Many PPPs have failed because the government retained demand risk (e.g., toll road traffic guarantees) that eventually required bailouts.

Corporate Finance: Simplicity but Balance Sheet Constraint

Corporate finance uses the sponsor's balance sheet to finance the project, often with a mix of corporate bonds and equity. This simplifies the capital stack (no special purpose vehicle, fewer covenants) but exposes the sponsor's entire credit profile to project risk. Feasibility must assess whether the sponsor can absorb losses without jeopardizing other operations. This structure is suitable for expansions of existing assets where the sponsor has strong credit. The downside is that it limits leverage and may not be feasible for very large projects without straining the balance sheet.

Negotiating Intercreditor Agreements: Protecting Each Layer's Interests

Intercreditor agreements (ICAs) govern the relationship between senior lenders, mezzanine investors, and equity sponsors. They define payment waterfall, standstill periods, cure rights, and enforcement actions. A well-negotiated ICA can prevent a minor cash flow hiccup from triggering a destructive liquidation. During feasibility, the project team should draft key ICA terms and test them under stress scenarios. Common provisions include: senior lender control over enforcement (mezzanine cannot accelerate without senior consent), mezzanine cure rights (the right to step in and cure a senior default), and equity standstill (equity cannot block a senior sale).

In one anonymized scenario, a renewable energy project experienced a six-month delay in commissioning due to grid connection issues. The senior lender issued a notice of default, threatening acceleration. The mezzanine investor had a 90-day cure right, but the equity sponsor lacked cash to inject more capital. The mezzanine used its cure right to pay the overdue interest, then negotiated a 12-month forbearance in exchange for a higher interest rate and warrants. This saved the project, but the original equity was heavily diluted. The key lesson: ICAs should explicitly address cure rights, forbearance conditions, and dilution mechanics to avoid chaos during stress.

Key ICA Terms to Negotiate

1. Payment Waterfall: Senior debt service first, then mezzanine interest, then mezzanine principal, then equity distributions. Ensure that excess cash flow after senior service can be used to pay mezzanine, not trapped in reserves. 2. Standstill Periods: Mezzanine should have at least 60-90 days to cure a senior default before senior can accelerate. Equity should have a shorter period (e.g., 30 days) to cure mezzanine defaults. 3. Enforcement Rights: Senior lenders typically control liquidation; mezzanine may have the right to purchase the senior debt at par (a "buyout" right) to take control. This can be a valuable option for mezzanine. 4. Covenant Subordination: Mezzanine must agree that its covenants are subordinated to senior covenants—meaning senior can waive certain mezzanine covenants without mezzanine consent. 5. Equity Contribution: In a cash sweep or mandatory prepayment, equity may be required to inject additional funds before senior takes enforcement action. This "equity cure" provision is common.

Common ICA Pitfalls

One pitfall is overly restrictive covenants that limit operational flexibility—for example, requiring senior consent for any new contract above $1 million. This can delay critical repairs or expansions. Another pitfall is ambiguous cure rights: the ICA may say mezzanine can cure, but not specify how (cash payment? waiver?). Disputes over interpretation can escalate to litigation. Finally, some ICAs allow senior lenders to amend the credit agreement without mezzanine consent, which can change the risk profile unexpectedly. Feasibility should include a legal review of the draft ICA, with stress tests to see how each party would behave in a crisis.

Step-by-Step Feasibility Framework for Capital Stack Risk

This framework provides a systematic process for evaluating capital stack risk during the feasibility phase. It can be adapted to any large-scale infrastructure project. The goal is to identify the weakest link in the stack and strengthen it before financing closes. Each step involves quantitative analysis, qualitative judgment, and stakeholder alignment.

Step 1: Define Base Case and Key Assumptions

Start with a detailed financial model: projected revenues, operating costs, capital expenditures, financing structure (amounts, interest rates, repayment schedules). Document all assumptions—inflation, tariff escalation, demand growth, construction timeline. Use conservative estimates for base case (e.g., 80% of projected demand). Ensure the model is transparent and can be easily modified for stress testing.

Step 2: Identify Risk Factors and Probabilities

List all material risks: construction (cost overrun, delay), revenue (demand shortfall, price decline), regulatory (policy change, permit revocation), financing (interest rate hike, credit downgrade), and operational (technical failure, labor dispute). For each risk, estimate a plausible range (e.g., cost overrun of 10-30%) and a probability (e.g., 20% chance of >15% overrun). Use historical data from similar projects or industry benchmarks, but adjust for project specifics. Avoid using precise numbers that sound like fabricated statistics; instead, use ranges and qualitative labels (low, medium, high).

Step 3: Model Stress Scenarios

Create at least three stress scenarios: (a) moderate stress (single risk materializes, e.g., 15% cost overrun), (b) severe stress (two risks combined, e.g., cost overrun + 10% revenue shortfall), (c) extreme stress (three or more risks, e.g., cost overrun, revenue shortfall, and interest rate hike). For each scenario, calculate DSCR, LLCR, equity IRR, and mezzanine yield. Identify which tranche fails first (e.g., DSCR below 1.0). Determine if the capital stack can absorb losses without default—e.g., through equity injection, reserve drawdown, or mezzanine deferral.

Step 4: Evaluate Capital Stack Resilience

Assess whether the capital stack can survive the severe scenario without a liquidity crisis. Key metrics: minimum DSCR above 1.0x, equity IRR above 0%, mezzanine yield above 0%. If any metric fails, consider adjustments: increase equity cushion, reduce leverage, add a reserve facility, or negotiate a sponsor guarantee. Also test the impact of covenant breaches—e.g., if DSCR falls to 0.9x, does the senior lender declare default? If so, the project may be forced into restructuring even if cash flow recovers later. Consider adding covenant cushions (e.g., DSCR covenant at 1.05x instead of 1.2x) if senior lender agrees.

Step 5: Negotiate Terms Based on Stress Results

Use stress test results to negotiate capital stack terms. For example, if the severe scenario shows mezzanine interest deferral, mezzanine investors may demand a higher coupon or conversion rights. If equity returns are too low in the base case, equity may push for lower leverage or a higher tariff. The feasibility report should present these findings to all stakeholders, facilitating transparent discussions. Document the agreed-upon adjustments and update the model accordingly.

Step 6: Document and Review

Produce a feasibility report that includes: capital stack structure, risk matrix, stress test results, and mitigation measures. Have it reviewed by independent experts (e.g., technical advisor, financial advisor). Obtain sign-off from all parties. This report becomes the basis for financing agreements. Revisit the analysis if material changes occur (e.g., new regulation, technology shift).

Real-World Scenarios: Lessons from Practice

The following anonymized scenarios illustrate common capital stack failures and how feasibility analysis could have prevented them. They are composites drawn from widely reported industry patterns, not specific projects.

Scenario 1: The Optimistic PPA Assumption

A solar project in a developing country secured a 20-year PPA with a state-owned utility at a fixed tariff. The capital stack was 75% senior debt, 10% mezzanine, 15% equity. Feasibility assumed the utility would always pay on time. However, the utility faced financial difficulties and began delaying payments by 90-120 days. The project's cash flow became erratic, and the DSCR fell below 1.0x for three consecutive quarters. The senior lender issued a default notice. The mezzanine investor attempted to cure but could not cover the cumulative shortfall. The project entered restructuring, with senior lenders taking a 10% haircut and mezzanine converting to equity. The equity was wiped out. The lesson: feasibility should include a counterparty credit risk assessment and model delayed payments. A simple solution would have been a debt service reserve fund sized to cover six months of debt service, or a requirement for the utility to post a letter of credit.