Illiquid assets · room 11 of 13
The three sectors.
A sector is treated here as a set of constraints a structure has to be built against, and the three worked below each bind in a different place: in the specification, in the utility interface, and in the assembly of the position itself.
Nothing here is a view on the merits of any sector, asset or market. What is stated is what each constraint does to the entity chain, the consent calendar and the test that releases a drawdown. Positions are stated, with the source and grade of every input held in the file behind it, on the discipline set out at from the Gulf.
Where complexity arises · Illiquid assets · thirteen rooms
01 · Commercial
Sector
The exit standard is a term of the entry. It is not a finish.
Where the eventual buyer is an institution, admission to the exit runs on a published standard rather than on a negotiation, and the standard reaches the specification, the certifications and the file that evidences both. That makes the standard a structural input: it is fixed before the appraisal is built on it, and it cannot be added to the asset afterwards without paying the distance twice.
The structural consequence runs through three objects. The specification enters the delivery route, because the contract form has to carry it. The certifications enter the consent calendar, because they are gated and dated. The evidence enters the exit-conditions memorandum from the first month, because a record assembled at the end was built to a different standard from the one it will be read against.
The file is underwritten as hard as the concrete, and it is built from month one or it is rebuilt later.
Occupier requirements are specification terms, so they belong in the contract form rather than in a schedule of intent.
Compliance and certification are exit conditions with owners and dates, which puts them on the consent calendar.
Where an alternative use competes for the same ground, the site control instrument carries the timing risk, not the appraisal.
What we design is the chain that carries the answer: the specification inside the contract form, the certifications inside the consent calendar, and the evidence inside the drawdown test that the appointed monitor runs each cycle.
02 · Data centres
Sector
The dependency chain runs through the utilities. Ground is not the first link in it.
On this asset the binding lines are the grid connection, the water allocation, the defensibility of the environmental clearance and the order book for long-lead electrical equipment. Each is granted by a party outside the transaction, on a calendar the parties do not own, and each sits ahead of construction in the dependency chain rather than beside it.
That inverts the consent calendar and, with it, the financing. The utility lines become the serial spine that no quantity of resource shortens; the construction programme becomes a parallel line hanging off them; and the drawdown test has to be evidenced against utility milestones as well as against progress on the ground, because a structure that releases capital against build alone funds a building it cannot energise.
The connection date governs the completion date, so it belongs on the serial line of the consent calendar.
The water allocation is a separate grant with a separate owner, and it is a discretionary line, not a scheduled one.
Clearance defensibility reaches the financing, because a lender's own conditions read it before the site does.
Long-lead equipment converts a procurement decision into a schedule constraint, which puts it at the commitment gate rather than at delivery.
What we design is the calendar that holds them, with an owner and an expected date against every line, and a reporting specification that carries the four dates beside cost to complete for whichever monitor the manager appoints.
03 · Residential and township
Sector
The assembly problem precedes the construction problem.
Where a scheme has to be aggregated before it can be built, and township thresholds are measured in tens of hectares, the position is not one asset but a set of acquisitions that must all close. The entity chain therefore carries two problems at once, and the second cannot start until the first has finished. One hold-out plot reprices the whole scheme, and it does so through the site control instrument rather than through the appraisal.
Two statutory mechanics then sit on top. Buyer collections run through a separate project account and are released against certified progress, which makes the escrow a term of the cash-flow architecture rather than an administrative account. And each phase is treated as a separate project, so the phase map decides the exit test and the lock-in arithmetic at the same time, and it is cut once.
Assembly risk compounds quietly, and it lives in the site control instrument long before it reaches the programme.
Escrowed collections and delivery-date liability are statutory rather than contractual, so they cannot be drafted around.
The phase map answers to two masters: delivery logic and exit logic, and the two rarely want the same cuts.
A phase registered is a phase fixed, which puts the map at the entry gate rather than at the delivery gate.
What we design is the site control chain that holds an assembly together, the phase map cut for the exit test as well as for delivery, and a reporting specification that puts the regulator's register beside physical progress.
We are an independent specialist transaction-architecture firm. Nothing above is a view on the merits of any sector, asset or market: the exposure is chosen by the manager, and what is designed here is the architecture through which it can be implemented.


