Investment and Delivery · 8 minutes · Investment-vehicle analysis · Asset diagnostics · Risk allocation
Institutions rarely arrive at a structuring conversation without a preferred structure already in mind. A fund. A trust. A PPP. A concession. A pooled real-estate vehicle. Someone has seen it work elsewhere, and the question becomes how to build it here.
That sequence inverts the analysis. A vehicle is a mechanism for carrying particular assets, particular revenue, particular risks and particular obligations. Until those are described, there is nothing for the vehicle to be judged against.
The question is not which structure is best. It is which structure the assets, owners, revenue and obligations can actually support.
Four conditions determine what any structure will have to carry, and all four can be established before a vehicle is named.
An institution may hold an asset on its balance sheet and still be unable to contribute it to a vehicle. Title may be unregistered or contested. Use may be restricted by statute, heritage designation or an existing tenancy. Transfer may require an approval nobody has sought.
Control is the operative question: can this asset be committed, on what terms, and who has to agree?
Structures that mobilize capital depend on income. There is a large difference between rent currently collected, rent contractually committed, rent evidenced by comparable transactions, and rent assumed in a model.
Each of those belongs in a different confidence band, and a structure built on the fourth will behave very differently from one built on the first.
Some risks are tolerable at portfolio level and some are not. Contamination, structural failure, unresolved title and heritage obligations tend to be asset-specific, expensive and slow to resolve. Pooling spreads such a risk across investors who did not price it.
Where a risk is material and unresolved, the question is whether the structure isolates it or transmits it.
Public assets usually carry commitments that outlast the deal: access, affordability, heritage protection, local employment, continuity of a service. A structure that cannot hold those commitments has not solved the problem, whatever its financial return.
When the structure is chosen first, the analysis becomes advocacy. Evidence is gathered to support the preferred vehicle, uncomfortable asset facts are treated as implementation details, and the comparison against alternatives is either skipped or performed after the decision.
When conditions are established first, the comparison can be honest. Each structure is tested against the same evidence base, and the ranking carries its own reasoning: this structure ranks higher because of these conditions, and it would rank lower if these conditions changed.
A recommendation that cannot say what would change it is not a recommendation. It is a preference.
A structuring recommendation should be able to state, in plain terms:
That last item is the discipline. If the answer holds only under the most favourable assumptions, the institution should know that before it commits assets, budgets or political capital.
Structuring work sits at a specific evidence stage. Desk feasibility can rank options and identify what must be verified. Market-validated feasibility tests those assumptions with the parties who would have to participate. Transaction readiness is a different threshold again.
Confidence should rise as the evidence improves, and the ranking should be permitted to move when it does. A structure selected early and defended thereafter is a structure that stopped learning.
Model the vehicle before you build the vehicle.
Common Practice compares public, private and hybrid delivery structures before capital or institutional commitments are locked in — and leaves the model behind so the comparison can be rerun.
REIV Structurer — The decision product that runs this comparison: four structures, one evidence base, in three languages and multiple currencies.