How to Run Downside Cases Before Bank Outreach

How to Run Downside Cases Before Bank Outreach

A project should enter banker outreach with the downside cases already understood. If every material risk is discovered for the first time in lender diligence, the sponsor loses credibility and negotiating leverage.

The technical framework referenced in How to Run Downside Cases Before Bank Outreach includes World Bank PPP Financial Viability Guidance and IFC Project Finance in Developing Countries.

How Project Finance Downside Cases Works

The model should isolate lower revenue, higher operating cost, delay, capex overrun, interest-rate movement, refinancing stress and any sector-specific risk. The objective is to see which scenario breaches coverage, consumes reserves or requires sponsor support before a bank asks the same question.

For project finance downside cases, the model is part of the financing documentation rather than a presentation tool. Every major ratio, drawdown, reserve, repayment and distribution assumption should be capable of reconciliation to the term sheet and eventually to the finance documents.

The model supporting How to Run Downside Cases Before Bank Outreach should also show how a delay or downside changes lender protections. A covenant is only useful if the spreadsheet can calculate it consistently at the required testing dates.

What to Test Before Execution in How to Run Downside Cases Before Bank Outreach

• 1. revenue downside.
• 2. operating-cost stress.
• 3. construction delay.
• 4. capex overrun.
• 5. interest-rate stress.
• 6. refinancing risk.
• 7. combined downside.

Documents to Prepare for How to Run Downside Cases Before Bank Outreach

For project finance downside cases, the first document set should be sufficient to let a banker, adviser or credit committee reproduce the central financing assumptions rather than rely on verbal explanations.

• base case.
• sensitivity table.
• downside scenarios.
• liquidity bridge.
• reserve schedule.
• sponsor support analysis.
• covenant headroom table.

How the Model Supports the Credit Agreement for How to Run Downside Cases Before Bank Outreach

For How to Run Downside Cases Before Bank Outreach, each covenant and funding condition should have a visible model input, calculation or test. The model should produce the same economic answer a lender expects from the loan-document definitions, including cash waterfalls, reserve movements and distribution restrictions.

Common Failure Modes in How to Run Downside Cases Before Bank Outreach

• Using hard-coded outputs in How to Run Downside Cases Before Bank Outreach instead of formula-driven calculations that can be audited.
• Calculating covenant ratios for project finance downside cases differently from the financing-document definitions.
• Omitting liquidity consequences when a condition precedent delays a draw in How to Run Downside Cases Before Bank Outreach.
• Running sensitivities for project finance downside cases without showing the effect on debt service, reserves and distributions.

FAQ About Project Finance Downside Cases — How to Run Downside Cases Before Bank Outreach

Who uses project finance downside cases after financial close?

The borrower, agent, lenders and advisers may all rely on outputs from How to Run Downside Cases Before Bank Outreach for covenant testing, drawdowns, distributions, reserve calculations and amendments.

Should project finance downside cases include downside cases?

Yes. How to Run Downside Cases Before Bank Outreach should make lender sensitivities reproducible and show the effect on debt service, reserves, liquidity and covenant headroom.

Why do conditions precedent matter in project finance downside cases?

Conditions precedent determine whether scheduled financing is actually available. How to Run Downside Cases Before Bank Outreach should therefore reflect the liquidity consequence of delayed or failed funding conditions.