How we work · the whole arc
The lifecycle.
A transaction runs from an objective somebody states to a structure somebody operates, and the run is longer than any single party ever sees. This page sets the whole of it out in order, names the party that owns each stage, and marks the two points at which the work changes hands.
Six movements, fourteen stages, two handovers. Six of the fourteen sit with this firm: five of them run early and consecutively, and the sixth returns once at stage 11, after the first handover has already moved the work elsewhere. The rest of the arc is the longer part of the lifecycle, and it runs without us.
01 · The arc
How we workFrom a stated objective to an operating structure is six movements. Two of them open on a handover, and the arc never crosses back.
Read at this height a transaction has a shape most parties never see whole, because each of them joins at a different point and leaves at a different one. The manager is present at the first movement, at the fourth where the route is adopted, and at the sixth for as long as the vehicle lives. Counsel joins at the fifth and stays into the sixth. The administrator arrives at the sixth, after every choice it will be operating for years has already been made.
- 01 Intent Stage 01. The manager states the exposure it wants. Nothing structural is settled, and every route is still available.
- 02 Diagnosis Stages 02 and 03. The problem is identified rather than assumed, and what already binds is read as it stands. It is frequently not the problem that was brought.
- 03 Architecture Stages 04 to 06. Routes are drawn to the same depth, compared on the same axes, and then attacked to find where each one fails.
- 04 Decision Stage 07. The manager adopts a route. This is the pivot of the whole arc, and the manager is the party that takes it.
- 05 Validation Stages 08 to 11. Counsel, tax advisers and the regulated firms give formal positions, each in its own name. Handover
- 06 Execution Stages 12 to 14. The transaction is conducted, and the structure is then operated for as long as the vehicle exists. Handover
A marked movement opens on a handover. Work crosses to a party who acts in its own name and signs for what it does, and it does not cross back inside the same transaction without reopening the movement before it. There are exactly two.
The implementation framework sits across the seam between the fifth movement and the sixth. It is drawn while validation is running rather than after it, because half of what it has to sequence is the validation itself: which position has to be given before which appointment can be made, and which appointment has to exist before which step can be taken.
The four movements before the first handover decide what gets built. The two after it build it and then run it, and they hold almost the whole of the calendar. That asymmetry is the reason the early movements repay the attention they are rarely given.
Four movements decide what is built. Two build it, and the structure is afterwards read by people who were present at none of them.
02 · The fourteen stages
The method in fullFourteen stages run in order. Each closes on something the next one needs.
The six movements open out into fourteen stages. The order is not administrative. An answer that arrives after the point at which it could have changed anything does the work of no answer at all, and the point in question is nearly always a stage that closed weeks earlier.
Six of the fourteen sit with this firm, and they are the six moves of the method carrying their lifecycle numbers: define is stage 02, map is stage 03, design is stage 04, compare is stage 05, stress-test is stage 06, mobilise is stage 11. Numbers on this page count the whole arc, so they run ahead of the numbers the method uses for itself. The gap between the two blocks of six is the first handover.
- 01 The economic objective What exposure the transaction is meant to produce, stated so that it can be tested against a structure. Ownership or economic participation. Control or none. Income or appreciation. What duration, what liquidity, what risk characteristic. Exposure to real estate names a sector rather than an objective, and closing that distance is the whole of the first stage.
- 02 The structural diagnosis What the problem actually is. The question a manager brings is often not the question the transaction has: a query about a jurisdiction resolves into a question about an instrument, a query about a vehicle resolves into a question about who may subscribe to it. The stage closes when the question the engagement will answer can be written in one sentence and tested against a structure.
- 03 The constraint map What already binds, read as it stands rather than as intended. The fund constitution, the delegations, the side letters already signed, the facility papers, the appointments already made, the domiciles already fixed. Most of what constrains a structure is sitting in documents the manager has signed, and every one of them is read before anything is drawn.
- 04 The candidate architectures The routes that could produce the stated exposure, drawn to the same depth so that they can be set beside one another: entities, jurisdictions, vehicles, instruments, ownership relationships, financing, governance and administration. Three or four routes, each finished. Not one preferred route with alternatives sketched thinly behind it.
- 05 The comparison Every route read against the same thirteen axes, set out in full under the method. Reading all thirteen against all of them is what makes the differences visible: the route that is simplest to stand up is rarely the route that is simplest to exit, and until both readings sit on one page a manager is choosing between two strengths without seeing what each one gives up to hold the other. Three routes are not an answer until it can be said why they differ and what each one forecloses.
- 06 Failure points and sequence Each surviving route is then attacked with the eight questions, every one of them aimed at an assumption rather than at the drawing. What falls out is not a verdict on the route. It is a set of dependencies: which answer has to exist before which choice can be made, and which choice cannot be revisited once something downstream has been built on it. Those dependencies fix the order in which everything still open has to be resolved.
- 07 The structural decision The manager adopts a route. This is the pivot of the arc: what precedes it is analysis, and everything after it implements a decision the manager has taken. Because the choice is made against routes that were drawn rather than described, it can still be explained years later, to an incoming general counsel or to a purchaser asking why the structure looks the way it does.
- 08 The legal position Appointed counsel gives the formal legal position on the structure as adopted, in its own name and on its own authority: whether it is lawful as drawn, what the documents will have to say, and what each of them will bind. The questions reach counsel already separated, each carrying the provision that raises it.
- 09 The tax position The manager's tax advisers state the position of the holding chain in each jurisdiction it crosses. Every place the chain crosses a border was marked on the drawing with what turns on it structurally; what the answer is at that junction is a formal position taken by the adviser who will stand behind it in front of an authority.
- 10 The regulated activity Which activity inside the transaction requires a permission, in which territory, and which authorised firm carries it on. Arranging deals, dealing, advising on the merits of an investment and managing assets are named activities held by named firms in their own names. The appointment has to be in place before the step that needs it rather than after, and lateness at that interface is rarely recoverable inside the same transaction.
- 11 The implementation architecture What has to exist before the transaction can be conducted: which entities, which appointments, which approvals, which documents, in what order and against which dates. This is the implementation framework. It is drawn while validation is running, because the sequence it fixes includes the validation, and a framework written after the positions are in has sequenced nothing.
- 12 The documentation Counsel drafts. Entities are constituted, registers are opened, appointments are executed, and the conditions precedent are listed and then satisfied one by one. Everything that binds anybody is signed at this stage, by a party the manager appointed and in that party's own name.
- 13 The transaction, conducted The regulated counterparties act: the approach, the negotiation, the instruction, the purchase or the sale, each under the permission that covers it. This is the movement the whole of the arc has been preparing for, and every step in it belongs to the firm whose permission covers that step.
- 14 The structure, operated The administrator runs what was drawn: the register, the calls, the allocations between vehicles, the valuation basis, the reporting cycle, the filings and the audit. It runs for as long as the vehicle exists, which is ordinarily longer than the transaction that created it and longer than anybody planning that transaction pictures.
Stages 02 to 06 are one continuous run: each opens on what the one before it closed, and none of them can be lifted out without the rest losing an input. Stage 11 is the return leg. The eight remaining stages are held by parties who sign for what they do, and they are the eight that produce every fact the transaction is finally made of.
The six early stages are the ones where a change is still a redraft. After them a change is a withdrawal, a re-execution or an amendment, which is why they are taken in this order and not in the order the pressure arrives.
03 · Who holds each stage
Decision ownershipFourteen stages, six parties. Every stage has exactly one owner, and the shape of the second column is the boundary.
Decision ownership maps thirteen decisions to the party that takes each one. This plane counts something else. The rows are not decisions but stages of work, in the order they run, so the two tallies are not comparable and are not meant to be: a party can hold a stage without holding a decision inside it, and can hold a decision inside a stage another party is doing the work of. The marked cell is the party that does the work in that stage and signs for what comes out of it.
| Stage · owner | The manager | This firm | Appointed counsel | Tax advisers | Regulated counterparties | Administrators |
|---|---|---|---|---|---|---|
| 01 · The economic objective | The manager | |||||
| 02 · The structural diagnosis | This firm | |||||
| 03 · The constraint map | This firm | |||||
| 04 · The candidate architectures | This firm | |||||
| 05 · The comparison | This firm | |||||
| 06 · Failure points and sequence | This firm | |||||
| 07 · The structural decision | The manager | |||||
| 08 · The legal position | Appointed counsel | |||||
| 09 · The tax position | Tax advisers | |||||
| 10 · The regulated activity | Regulated counterparties | |||||
| 11 · The implementation architecture | This firm | |||||
| 12 · The documentation | Appointed counsel | |||||
| 13 · The transaction, conducted | Regulated counterparties | |||||
| 14 · The structure, operated | Administrators |
The second column is unbroken from stage 02 to stage 06, disappears for four stages, and returns once at stage 11. That gap is the first handover. The four stages inside it are owned by parties who give their positions in their own names, and nothing in the architecture is settled by us while they are running.
The manager holds two stages, and they are the two that decide everything else: what the transaction is for, and which route is taken. Nothing in the arc moves either of them. The four stages between them exist so that the second is a choice rather than an acceptance.
The plane is read in two directions. Down a column it says what a party can be instructed to do; along a row it says who has to have finished before the next stage can begin.
04 · The first handover
The blueprintThe first handover carries the architecture into validation. What crosses is a decided transaction and a framed list of questions.
It falls between stage 07 and stage 08, and it is the harder of the two. Until it, the transaction is a set of options held between the manager and this firm. After it, positions are given in named parties' own names, and moving the architecture means asking somebody to withdraw something they have already put their name to.
After the route is adopted, not before. Validation aimed at four routes puts professional attention on options rather than on a transaction, and it produces four conditional answers where one definite answer was needed. The order is not a convenience: a formal position can only be given on a structure that somebody has decided to build.
The blueprint, in the nine views it is drawn in. What decides whether the crossing works is not the contents but the finish. A drawing at one scale, with every constraint attached to the instrument that creates it and every assumption held apart from every finding, can be validated as it stands. A drawing short of that is reconstructed before it can be read, and the reconstruction is done by the party you appointed to validate it, working from a version of the transaction it has assembled itself.
Everything up to here is written in the conditional. Everything after it is written by parties who are accountable for being right. That is the real content of the handover: the transaction stops being a comparison of possibilities and becomes a set of positions somebody can be held to, and the drawing has to be finished enough to carry that weight.
Three validations run in parallel and they arrive at different speeds. Each answer is read back into the whole drawing rather than into the part that raised it, the routes set aside stay live in the file in case one of them is needed, and the sequence is kept current so that an answer landing late does not silently reorder everything downstream of it.
The authority to conclude anything. Whether the structure is lawful as drawn is counsel's to state. What the tax position is, in a named jurisdiction, is the tax adviser's. Whether an activity sits inside a permission is settled by the firm that holds the permission. Those three answers are the point of the movement, and each of them belongs to the party that signs it.
Where a validation answer and the structural analysis differ, the file improves rather than stalls. The disagreement lands on a recorded reason, because the route was drawn with the constraint that shaped it attached, and a difference about a cited constraint is a question two disciplines can actually resolve.
Counsel receives a decided transaction and a framed list of questions. The legal work is not shortened by that; what changes is the distance between the transaction and the question counsel is being asked about it.
05 · The second handover
Execution-readinessThe second handover carries the implementation framework into execution. Four parties take it up, and between them they hold every stage that is left.
It falls between stage 11 and stage 12. The first handover asked other parties to give positions; this one asks them to act, and the difference is that after it the transaction begins producing facts instead of views.
It is taken when the conditions of execution-readiness are met rather than when a date arrives. What each party needs in hand before it can act is set out there. What follows here is the other half of the same fact: which stage of the arc each of the four opens, and what changes for that party the moment it does.
- Appointed counsel
Opens stage 12, and closes every question still open when it does. Drafting is a closing mechanism: a point the architecture left unsettled gets settled by whoever holds the pen, on the day the clause needs a word in it. So the questions that are still open at this handover are, precisely, the structural decisions counsel is about to be left to take.
- The regulated counterparties
Open stage 13, each under its own permission. What the sequence gives each of them is position rather than instruction: which step it is being asked to take, which step has to have happened before it, and which of the two is still reversible.
- The administrator
Opens stage 14 and then holds it for the life of the vehicle. The question it is asked at this point is whether it can operate what has been drawn, which is a question it can answer. An answer of no here returns the work to a drawing. The same answer after the first close returns it to the holders.
- The manager
Instructs all three. Each decision that remains carries the date it has to be taken by and the step that stays blocked until it is, because an instruction is only possible where the decision behind it has an owner who already knows the decision is theirs.
Some of the steps that follow cannot be taken a second time on different facts. Which ones those are, and where they fall in the sequence, is drawn at the one-way doors. The reason they are marked before the handover rather than during it is that a step of that kind discovered in flight is a step that has already been taken.
Before this handover the transaction produced options. After it, the transaction produces facts, and the two are not the same material to work with.
06 · Where the arc turns back
When the structure does not workAn arc drawn as a straight line is a drawing of a transaction nobody has done. Validation sends work back, and the file is built so that it lands somewhere.
A position given by a party accountable for it is exactly the input that ought to be able to move an architecture. So the drawing is built to take one: the routes set aside stay live in the file, the constraint behind every choice stays attached to that choice, and the sequence is kept as a working document rather than a record of what was once intended.
One answer, three ways back into the drawing
- 01 An answer arrives Counsel returns a position on a point that was framed as a question. A tax adviser reads a junction differently from the way the structure assumed. A counterparty declines a step, or accepts it only on a condition nobody built into the sequence.
- 02 What decides where it lands Whether the answer touches a parameter inside the chosen route, or touches the reason the route was chosen over the others. The first is an amendment to a drawing. The second is a return to the stage where the choice was made. The two are handled differently, because the first is absorbed inside the sequence and the second reopens it.
02 · the point of divergence · the same answer meets the architecture at one of three depths
03a
It confirms the route
- 03a.iThe assumption becomes a finding and moves out of the assumptions list
- 03a.iiThe question is closed in the file with the party who closed it named against it
- 03a.iiiThe sequence continues from the next unresolved dependency
The commonest outcome and the least interesting. What it buys is that the structure now rests on a position somebody signed rather than on a reading nobody was accountable for.
03b
It changes a parameter
- 03b.iA domicile moves, an instrument changes character, a consent becomes conditional
- 03b.iiThe change is read across the whole drawing rather than into the layer that raised it
- 03b.iiiEvery dependency touching the changed part is re-tested, and the sequence is redrawn
The dangerous outcome, because it looks small. An answer absorbed in one leg of a structure and nowhere else is how two legs of the same fund come to run on different assumptions without anyone noticing.
03c
It removes the route
- 03c.iThe constraint that the route depended on turns out to bind the other way
- 03c.iiThe work returns to stage 04, to the other routes drawn there to the same depth
- 03c.iiiThe comparison is re-run with the new constraint added to the axes
This is what the record of rejected routes is for. A return to a route already drawn, already compared and already carrying the reason it was set aside is a re-reading. A return to a blank sheet is a restart.
There is a fourth outcome, and it is the one nobody sequences for: the constraint binds every route, and the transaction as posed is not structurally viable. That is a different subject, and it is set out at when the structure does not work rather than compressed into a branch here.
A return to stage 01, the economic objective, is rarer and more consequential than any of the three. It happens when no architecture produces the stated exposure and the exposure itself has to move. Changing the objective changes the whole set of structures available, which is why the objective is written down in testable form at the first stage rather than assumed from the conversation that opened the matter.
A route that survives validation untouched was probably not attacked hard enough at stage 06. The purpose of drawing three routes is that the second one is already drawn on the day the first one fails.
07 · After we stop
Exit architectureThe longest part of the lifecycle happens after our work ends. Every event in it is the consequence of a stage nobody in the room at the time will be present for.
The structural stages are short and the operating life is not. A structure drawn for the closing has been drawn for the briefest part of its own existence, and every party that reads it afterwards reads it for a different purpose than the one it was drawn under. Eight events follow, each traced back to the stage that decided it.
Counsel drafts, and every place the architecture left a question open is a place the drafting will close it. A question that reaches drafting unanswered gets answered by whoever holds the pen, which means a structural decision taken by a party appointed to record decisions rather than to make them. Traced back to stage 06, where the route was attacked: the question that was not raised there is the question the drafting invents an answer to.
The list is the sequence restated as obligations. Each condition is a step one party has to complete before another can act, and the ones that fail are almost always the ones with no party named against them. Traced back to stage 11, where the sequence was drawn: a condition without an owner is a condition somebody discovers on the day it blocks the closing.
Entities are formed and a legal person appears on a register somebody else keeps. From that moment the jurisdiction chosen at stage 04 stops being a choice and becomes a fact with a filing calendar, an authority and a set of continuing obligations attached to it. Nothing about that is reversible in the way a drawing is.
Capital moves along the route that was drawn. Every border the flow crosses was marked as a junction when the routes were drawn and given a position at stage 09, and the junction now goes live in the direction the executed documents fixed rather than the direction the model assumed. The two are not always the same direction.
A valuation basis, a reporting cycle and an audit. All three were settled by the choice of vehicle and the choice of domicile at stage 04, and neither of those choices was made by the party that now has to satisfy them. This is the first point at which the structure is examined by somebody with no interest in defending it.
Each class receives what the documents promised it. Where two classes sit in parallel vehicles, the allocation logic written at stage 04 is being applied for the first time by an administrator who was not present when it was written, working from documents that have to say it clearly enough to be followed without explanation.
A new holder, a further side letter, a change to the facility, an asset added to the chain. Every amendment is read against the architecture or it is read against nothing, and the second is how a structure acquires two inconsistent answers to the same question and carries both of them for years.
The last stage tests the first ones. Whether the interest can be sold, to whom, under which law, with which consents, and whether security can be released in the forum the asset actually sits in, were all decided by ownership and instrument choices taken before a single party was appointed. An ownership route that creates a problem at exit creates it years after everybody who designed it has moved on.
One consequence runs through all eight. The structure is read, in the end, by people who were in none of the rooms where it was decided: a new general counsel, an incoming administrator, an auditor, a purchaser's diligence team, occasionally a court. What each of them can reconstruct is limited to what the architecture and the documents actually say, which is why the record of what was rejected and why is kept in the file after the engagement ends.
The part of the lifecycle this firm holds is the short one. The part that reads what was drawn is the long one, and it is the part the drawing has to survive.
08 · The boundary the arc draws
Our roleThe boundary is not a paragraph at the foot of a page. It is the shape of one column in a plane fourteen rows deep.
Stated as a claim, a boundary is a promise about restraint. Drawn as a plane it is something a manager can test, row by row, against what it actually receives. Six stages of fourteen, two handovers, and after the second one a narrow standing on the design and nothing wider.
Six stages of the fourteen. The diagnosis, the constraint map, the routes, the comparison, the failure points and the sequence, and then the implementation architecture that carries all six across the second handover. Every one of the six closes on a drawing, and a drawing is a thing the next party in the arc can disagree with in writing.
A decided transaction and a framed list of questions, with the provision that raises each one attached to it. The opinion, the drafting and every position that gets signed are counsel's, on counsel's own authority.
The implementation framework and the drawing it sequences. The transaction is conducted, and the structure afterwards operated, by the firms whose business that is and whose permissions cover it. Every regulated activity inside the transaction is theirs in every territory it touches, from the first approach to the last.
What the transaction is for, which route is taken, which parties are appointed, and by when. Nothing in the arc moves any of those. Stages 02 to 06 exist so that the second of them is decided while it is still a choice, and stage 11 so that the third and fourth are decided in time to matter.
Questions about the design, on the four heads set out at the handover. That is a narrow standing and it is the accurate one, because by then the transaction belongs to the parties conducting it and the structure to the parties operating it.
The independence follows from the same shape. Every signature the transaction produces belongs to a party the manager appointed, and every route in the comparison is drawn by a firm that stands the same distance from all of them, which is what lets stage 05 be a comparison rather than a case for an answer already preferred.
The arc does not end with us, and it was never going to. What can be settled is that the eight stages after ours begin from one drawing rather than from five separate assumptions about the same transaction.
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