Begin with the revenue mechanism
Build–Operate–Transfer structures shift initial delivery and operating obligations to a project company for a defined concession period. The core question is not whether the facility can be built. It is who pays, for what service, under which volume and quality assumptions, and what happens when those assumptions change.
Lenders test payment security, tariff indexation, minimum-volume mechanisms, currency exposure and termination compensation before relying on engineering projections.
Connect clinical demand to capacity
A hospital bed count, laboratory throughput or manufacturing nameplate capacity is not a demand forecast. The model needs referral patterns, payer mix, procurement behaviour, ramp-up, downtime, consumable availability and workforce constraints. Oversized assets burden tariffs; undersized assets fail public-service objectives.
Capacity should be phased against observable demand triggers with expansion rights protected in the site and utility master plan.
Allocate risks to controllable parties
Land access, permits, utilities, demand, foreign exchange, construction, technology performance and change in law should each have a named owner and relief mechanism. A generic force-majeure clause cannot substitute for project-specific allocation.
The public counterparty should not carry equipment-maintenance risk it cannot control, while the project company should not absorb sovereign approval delays without a defined remedy.
Design the transfer from day one
At concession end, the asset must meet a defined condition. Handback surveys, residual-life requirements, maintenance reserves, data ownership, staff transition and spare-parts obligations therefore belong in the original model.
A bankable BOT package aligns technical standards, performance deductions, lifecycle CAPEX and handback criteria with the financial model.
Investor checklist
- Payment source and security mechanism verified
- Demand and ramp-up assumptions independently tested
- Currency and indexation treatment defined
- Relief, termination and change-in-law rules modelled
- Handback condition and lifecycle reserve specified
This briefing is a decision framework, not legal, regulatory or financial advice. Requirements vary by jurisdiction, product and facility scope. Certification and market authorisation remain subject to competent-authority decisions.
Test the bankability of a BOT concept
Translate the briefing into a project-specific scope, responsibility map and feasibility workplan.