Worked structures

Worked structure eight · Structural Feasibility Review

Security the lender cannot take.

A lender agrees to lend against an asset, and the asset cannot be charged where it sits. Either the place it sits creates no interest of that kind over a thing of that kind, or the consent required to grant one belongs to a party who is not in the transaction and gains nothing by being helpful.

The package is then designed from what a forum could actually deliver, backwards, rather than from the schedule of instruments the credit paper already named.

01 · The transaction as it arrives

The credit paper names a thing. The place that thing sits has never heard of the interest.

Four arrivals. One is a sentence in a term sheet, one is a schedule drafted from a precedent written for a different country, one is a condition precedent nobody in the room can satisfy, and the fourth is the disguise the other three travel in.

At the term sheet, before an instrument exists

The cheapest of the four and the rarest. What the lender wants is still a sentence rather than a schedule, the entities are still choices, and the account has not been opened. A sentence is rewritten in an afternoon. A closing is not.

At the drafting of the security documents

The schedule arrives from a precedent that worked somewhere else. It is competent and properly drawn, and it grants an interest the place the asset sits does not create. The defect is invisible on a document list, where an unenforceable instrument and an enforceable one look identical.

At closing, as a condition precedent

Somebody has to produce a consent, and the party who holds it is not in the room and owes nothing to anybody in it. What arrives as an administrative step is a negotiation with a stranger who now knows the date.

The question as it is actually asked

Almost never "can this be secured". It arrives as a condition precedent list to be reviewed, a recovery assumption to be checked, or one line in a facility on which counsel in two countries have written different things. The structural question sits behind whichever of those came through the door, and it is the same question in all four.

The asset in this class is not exotic. It is an ordinary income-producing holding: land, a licensed operating business, a concession, an interest in a joint venture. What makes it this case is that the instrument the credit paper assumed either does not exist where the asset sits, or exists only on terms somebody outside the transaction controls.

No lender, borrower, asset, counterparty, value or date appears in this room. What transfers from one transaction to the next is the shape of the problem, and the shape is what is set down here.

02 · The structural problem

A package whose reach stops one tier above the thing it was written for.

Two statements decide what the security is worth, and they live in different documents held by different people. One is a fact about the place the asset sits. The other is a fact about the market the money came from. They meet on one page for the first time at enforcement.

Security is not a document list. It is the answer to one question: which court or process, in which country, would put a named person in possession of a named thing, and how long that takes. Every deed, schedule and notice is machinery for that one sentence, and a bundle assembled without it is a set of instruments with no destination.

The specific difficulty is a mismatch between two statements nobody puts side by side. On one side, the interests the place the asset sits actually creates over a thing of that kind, and the act that makes each of them count against a third party. On the other, the schedule of security the facility says it has. Where the first set is narrower than the second, the difference is not a drafting gap. It is the whole of the recovery.

Why the two stay apart

The first is an asset fact, produced by the system that governs the asset and by the register that records title to it. It is knowable on the day the asset is identified, by counsel qualified where the asset sits. Nobody asks, because the question belongs to a place nobody in the negotiation is sitting in.

The second is a credit fact. It sits in the term sheet, it is carried into the facility, and it came from a precedent, because a precedent is what a competent party reaches for while the commercial terms are still moving. By the time the schedule is drafted, the instrument named in it has already been described to a committee.

The gap is then held open by the way the work is divided. Counsel where the lending was approved reads the facility. Counsel where the asset sits reads a schedule sent across at the end. Nobody is asked to hold the whole route from a default to possession, because on the document list every instrument already looks like security.

The problem is not that the asset is hard to secure. Hard was priced. The problem is that the instrument was named before the place was read, and the recovery was approved on the name.

03 · What binds

Four of the six are made by a place, one by a party who is not in the room, and one by nobody at all.

Six constraints bind the package. Not one is created by the document that names it, and every one is knowable while the chain is still a drawing.

The law of the place the asset sits, which decides what interests exist over a thing of that kind and what makes each count against a third party. The consent that belongs to a party outside the transaction: a register, a landlord, a licensor, a co-venturer, a counterparty with a change-of-control right. The law of the place the entity is incorporated, which decides what a taker may do on default. The perfection act and its period. The law of the account, and the route the payments take into it. And what the credit committee was told, which no document carries.

Each one, by source and by what can move it

The law of the place the asset sits

The system that governs the thing, and the register that records title to it. Unreachable by any choice of governing law, and the only constraint here no party can move at all. Read before the first draft, or by whoever enforces.

The consent held elsewhere

A register, a lease, a licence or an agreement signed by somebody else. Movable at a price, by asking early. The holder carries none of the transaction's timetable, so the price rises with every week the question is left.

The law of the place the entity sits

The place of incorporation of the company whose shares are charged. Movable at the drawing of the chain and fixed thereafter. It decides whether enforcement is an act or a process, and the model assumes one without saying which.

The perfection act and its period

The system that governs each item. A period that has run is not recovered by taking the step again, and a rank taken in order of receipt does not move. One date, in the week when several other things are also late.

The law of the account, and the flow

The place the account was opened, chosen by somebody who was not in the financing negotiation. Movable while it is still being opened. It decides what control the taker has over the balance, and what the account bank's rights do first.

What the committee was told

Nothing enforceable. No document carries it and no adviser holds it. It is enforced on the single day the recovery assumption is tested, and the distance between what was described and what exists is paid at once.

Five of the six can be produced from primary texts by somebody who knows which places to ask in. The sixth is produced from what a committee remembers being shown.

04 · The architectures considered

Four routes answer the request, and one of them reaches the asset.

Four architectures, and they are not four grades of one instrument. Each reaches a different thing, in a different forum, with a different number of steps between a default and possession.

Security over the shares of the entity that owns the asset, which reaches a shareholding rather than a thing. Security over the receivables and the account they arrive in, which reaches money. The local instrument, in whatever form that place creates, which alone reaches the asset. And a guarantee with a negative pledge, which reaches a person.

The first route is assumed more often than it is chosen, because on a chart it appears to reach everything beneath it. It does not. Enforcement replaces a shareholder. The asset stays where it was, subject to the consents always attached to it, and whoever now controls the entity uses them like anybody else.

What each one reaches, and what closes it

Security over the shares

Reaches the shareholding held by the entity above, read under the law of the place the company is incorporated, and nothing against the business beneath. Closed by the entity acquiring a second thing, by a change-of-control right the transfer triggers, and by a local rule on who may hold those shares at all.

Security over the receivables and the account

Reaches money, on the shortest route from a default to something spendable. Read under the law of the underlying contract or of the place the obligor sits, and the account under the law of the account. Closed by a notice given late, and by the payments quietly finding another account in the third year.

The local instrument

Reaches the asset itself, in the only forum that could ever deliver possession of it. Closed by nothing except its own terms, which is why it survives inattention. Ordinarily narrower and slower than the instrument the credit paper named, and requiring the consent held outside the transaction.

The guarantee and the negative pledge

Reaches a person rather than a thing. A right enforceable only in damages is a claim, not security, and on a document list the two are indistinguishable. Worth what the giver has, in a place the holder can reach, and worth nothing where the holder cannot.

The same problem drawn as a plate. The accented line is what the lender holds, and it stops at the tier above the asset.

A security package drawn over an asset that cannot be charged where it sits, with the share security marked as the load-bearing line. A fund vehicle holds the asset-owning entity, which holds title to the asset. The asset sits inside a perimeter marked as the zone where no interest is available, or where the consent to grant one is held elsewhere. The lender sits to the right. The load-bearing line is the share security: it runs from the lender to a collar around the asset-owning entity tier and stops there rather than entering the company, never reaching the tier below. Account security runs from the lender to a payment account, into which the payments the asset produces run across. Secured shares No interest, or a consent held elsewhere Holds Holds title Share security Guarantee Account security Payments Fund vehicle Grantor of the pledge The asset-owning entity Holds the asset, and nothing else The asset Title on a local register Support party Its own jurisdiction The lender Holds what it can reach Payment account The law of the account
The accented line is the security over the shares in the asset-owning entity. It stops at the collar around that tier, and nothing on the plate reaches into the lower perimeter. Count the steps from a default to possession of the thing itself: enforce against the shares and become the shareholder, replace the board, then sell the asset in the local forum on whatever consents that place attaches. Three steps, two of them outside the lender's control, and the only line crossing the lower perimeter carries money rather than property.

05 · The critical dependencies

A condition held for the life of the facility, not an item ticked at closing.

Three, and each is a state maintained over years rather than a document produced once. Each has an owner, a test and a date in the year, or it is not a dependency at all.

That the entity whose shares are charged holds the asset and nothing else, and goes on holding nothing else. A second asset acquired into it, a guarantee signed in its name, a lease taken in its name: each makes the shareholding a different thing from the one the recovery assumed, and none looks structural at the time.

That every consent the grant and the enforcement will need has been identified and its holder named. The two are separate consents and they are ordinarily conflated: permission to grant the interest is one question, and permission for the eventual transfer is another, asked of the same party in a worse week.

That the payments the asset produces go on arriving in the account that is charged. This is the only dependency that fails silently: a payment redirected elsewhere is an operational convenience with a good reason behind it, and the file that records it is not the security file.

What each costs to hold, and what it costs to restore

The first costs an annual question put to the borrower and answered in writing. Does the entity hold the asset and nothing else, has anything been signed in its name, and has anything changed about who may hold its shares. One date in the year.

Restoring it later is different work, because a thing already acquired into the entity cannot be unacquired without a transaction of its own, and that transaction needs consents from the same parties who are already the problem. The most that can be done late is to price the defect and disclose it.

The second costs a list drawn at the term sheet from documents already on the file. Drawn there, it is a set of letters written early. Drawn at closing, it is a set of requests made to strangers who now know the date.

The third costs a standing instruction and a statement read once a quarter. It is the cheapest of the three to hold and the only one that can be repaired completely, provided the repair happens before anybody defaults.

A dependency with no owner is not a dependency. It is a line in a recovery assumption with nobody's name against it.

06 · The architecture that survives

The enforcement sentence is written first, and every instrument in the bundle is judged against it.

What the constraints leave standing is not a preference between the four routes. It is an order of work, and a package that carries two routes rather than one, because a package with a single route is priced by whoever holds the consent that closes it.

The enforcement sentence is fixed before any instrument is drafted, in one paragraph, and every structural choice in the financing is judged against it: which person comes into possession of which thing, through which forum, in how many steps, and on what timetable the recovery assumption is entitled to rely.

The entity whose shares are charged is specified rather than inherited. It holds the asset and nothing else, and it is incorporated where security over its shares does something on default rather than beginning a process. The consent map is drawn at the term sheet, naming every party whose agreement the grant or the transfer will require. The payment flow is routed into the charged account at the outset, with notices given in the form each system requires and early enough to rank.

Where the asset itself genuinely cannot be charged, the architecture says so on its first page rather than in a schedule at the back. What the lender holds is a shareholding, a money flow and a promise. That is a coherent package. It is not the package the credit paper described, and the recovery assumption is rewritten to match it.

What the one sentence has to contain

It names the thing that would be taken, in terms a register would recognise rather than in terms a chart would. It names the forum that would order it, which is the place the property sits and not the place the contract was signed. It names the steps in order, because three steps and one step are two different recoveries. And it names the second route, held open beside the first, so that the party who controls the first is not the party who sets the price.

Holding the second route open is not free. A charged account carries its notices, its acknowledgements and its quarterly read. A local instrument carries its own counsel, its own registration and its own consent. What that buys is the removal of the fact that makes enforcement expensive: that one party knows it is the only party who has to say yes.

A package with one route is not a package with a risk in it. It is a recovery written by whoever holds the consent, on the day they discover they hold it.

07 · The implementation framework

Six items in order, and the signature on every one of them belongs elsewhere.

Written as dependency statements rather than as tasks, because the order is the part that is cheap to get right at the term sheet and impossible to correct after closing.

Write the enforcement sentence before the security schedule is drafted. Draw the reach map, item by item and place by place, from the primary texts rather than from the precedent. Choose the holding form against the sentence. Fix the perfection calendar. Route the payments into the charged account, and diarise the test that keeps them there.

The signatures belong elsewhere, as they should. Local security counsel in each jurisdiction of entity, register, account and asset states what interests that system creates and what act makes each one count. The perfection and priority opinions confirm that each step was taken in the form its system requires and inside its period. The insolvency analysis tests the package where it is tested most searchingly, and the lender runs its own credit process. Our work is the enforcement sentence, the reach map, the four routes drawn to the same depth, and the flow test.

The sequence, and what each step depends on

  1. 01 The enforcement sentence, written Depends on nothing except the parties stating what possession would look like and who would hold it. The only step with no precondition, and the one most often taken last.
  2. 02 The reach map, drawn from the primary texts Depends on counsel qualified in each place of entity, register, account and asset. One row per item: what interest exists, what act perfects it, inside what period, and what a taker may then do.
  3. 03 The holding form, chosen against the sentence Depends on both of the above, and is the one-way step. Where the share route is taken, the entity is specified now: what it holds, where it is incorporated, and what it may sign.
  4. 04 The perfection calendar, fixed Depends on the reach map being complete before closing. Each act, each place, each period, and the order the register receives them in. Neither a period that has run nor a rank already taken is recovered by repeating it.
  5. 05 The flow test, diarised and owned Depends on a named person rather than on a plan. Are the payments still arriving in the charged account, does the entity still hold nothing else, and has any consent holder changed.
  6. 06 The handover to the parties who sign Depends on the five above being on one page. Each adviser then receives a question already framed for the place they are qualified in.

The order is the whole of it. Each of these six is cheap in the sequence written above and expensive in any other.

08 · What this case generalises to

Wherever the instrument is named before the place is read, the bundle is a document list with the destination missing.

Four families of transaction share the shape of this one. In each, something a question at the beginning would have established is established instead by an outcome at the end.

Any asset whose own system does not create the interest assumed

Land where the charge available to a foreign taker is narrower than the one the precedent grants, a licence that cannot be assigned, a concession that answers to the body that granted it. The structural response is to reach the wider set of remedies through what may be transferred rather than through what may be charged.

Any consent held by a party outside the transaction

A landlord, a licensor, a joint venture partner, a counterparty with a change-of-control right, a register with an approval step. None of them carries the transaction's timetable. The response is the same: identify the holder at the term sheet, ask early, and treat the answer as a structural fact rather than a condition precedent.

Any protection that can only ever sound in damages

A guarantee, a negative pledge, a covenant, a contractual veto, an indemnity, a comfort letter. Each belongs in the bundle under its own name rather than on a list headed security. Count instead the items over which a named person could be put in possession of a named thing.

Any recovery assumption built on a timetable nobody read

An appropriation modelled as a same-week act where the place supervises a sale over months. A receivable modelled as cash where the obligor was never notified. A judgment modelled as an outcome where execution has to be sought somewhere it never has been. The error is not the number. It is that nothing in the file records which timetable the number assumed.

The engagement that answers this class is a Structural Feasibility Review: the enforcement sentence, the reach map drawn from the primary texts, the four routes compared to the same depth, and the flow test that keeps more than one of them alive. It stops where the signatures start.

Every fact that decides what the security is worth is knowable while the chain is still a drawing. Afterwards the same fact only explains the result.

Written as a type · no party, no value and no date · stated as at August 2026

Write to us.

Complex transactions fail at the interfaces between otherwise workable components. We resolve the structural complexity between investment intent and transaction execution.

Write to us

Bayswater Transflow Engineering Ltd. Private limited company registered in England & Wales. Company No. 16277213. Registered office 128 City Road, London, EC1V 2NX. Modern Slavery Statement registered with the UK Home Office registry.

Nothing on this website is an offer, a recommendation, or a view on the merits of any investment. It is directed only at persons who fall within an exemption under the Financial Services and Markets Act 2000 and the Financial Promotion Order 2005, and it must not be acted on by anyone else. The full terms of access are on the legal page.