Investment and Delivery · 8 minutes · Portfolio analysis · Risk ring-fencing · Sequencing
Pooling is attractive for good reasons. A portfolio diversifies income, spreads asset-specific risk across a larger base, reaches a scale that institutional capital can underwrite, and allows one management structure to serve many assets.
Ring-fencing is attractive for equally good reasons. A project-level structure contains its own risk, can be financed on its own merits, can fail without taking others with it, and can proceed while other assets are still unresolved.
Both arguments are sound. The question is which one the current portfolio has earned.
Pooling assumes assets can be treated as members of a portfolio. That assumption holds when the assets are broadly comparable in the ways that matter to an investor: use, revenue maturity, risk profile, control certainty and time to stabilisation.
Where those vary widely, a pool does not diversify risk so much as average it — and averaging is how one unresolved asset quietly prices the whole vehicle.
The tests are practical rather than theoretical.
A clear pass on all four is a strong argument for pooling. A clear failure on any one is usually an argument for keeping the asset separate until it is resolved.
Project-level structures are not free. Each one carries its own establishment cost, its own governance, its own financing negotiation and its own reporting. Several of them cost materially more to run than one vehicle, and they mobilize capital in smaller, more expensive parcels.
That cost is worth paying when it buys implementability. It is waste when the assets could have been pooled and were not.
In practice, portfolios are rarely uniformly ready. Some assets have clear title and observable income; others have unresolved control, unknown rehabilitation cost or no operating history.
A staged structure treats that unevenness as the design input rather than an inconvenience: de-risk the complex assets individually, establish operating evidence, and then test whether the stabilized ones should be pooled. Pooling becomes a later decision made with better evidence, instead of an early decision made with hope.
Staging is not indecision. It is sequencing the decision to match the evidence.
Programme-level coordination is often confused with pooling. A regeneration platform can set strategy, standards, infrastructure and sequencing across many assets while each asset is financed through its own structure.
That distinction matters when public objectives require coordination but the assets cannot yet support common financing. Coordination and capital do not have to arrive in the same vehicle.
A public conclusion on this question can be stated responsibly without overclaiming: what the evidence currently supports, at what stage, and what would have to be verified for the answer to move.
What should not be published is the appearance of certainty — indicative returns presented as realized, or a structural recommendation presented as a transaction decision.
Common Practice models portfolio structure, public contribution and risk allocation before transaction design — and builds the sequencing logic that follows.
REIV Structurer — Compare a pooled vehicle, a platform with project SPVs, a staged hybrid and conventional delivery — and see what would change the ranking.