Why this keeps happening.
We have read files from banks, funds, developers and state corporations. The sectors differ. The symptoms differ. The causes repeat.
Six reasons the file does not hold
- Siloed documentation
- A file is assembled, not written: consultants, engineers, the sponsor's finance team and lawyers each contribute a part and are accountable only for that part. The divergence comes from the division of labour, not from intent.
- Optimism as input
- Volumes, prices and timing are each set at their most favourable value. One by one, the assumptions can be defended; together, they add up to a project without a single bad year. The sponsor's approval process rarely questions the combination.
- Security treated as a formality
- Payments are approved by the project team; guarantees are handled by lawyers and the back office. No control makes the first conditional on the second, so an advance can go out on a signed contract alone. The lender learns of the exposure once it already exists.
- Revenue assumed, not contracted
- Before an asset is built, customers are reluctant to commit to volumes. The model still needs revenue, so expressions of interest are turned into throughput — and the distance between interest and obligation is never priced.
- Engineering costs invisible to finance
- The model is often frozen before the surveys are finished. What the engineers find later — ground conditions, seismic requirements, the real cost of a grid connection — arrives as technical reports in technical language, and never makes its way back into the numbers.
- No independent seat at the table
- The contractor controls the schedule, the budget and the information. The lender sees the file, not the site. The divergence reaches the lender last, and is paid for at a premium.