Infrastructure AdvisoryThe moment the question stops being theoretical
Infrastructure changes hands. An organisation that has not held an asset before takes responsibility for operating and maintaining it, and does so knowing that not everything about it is resolved.
Some of what is unresolved is ordinary and expected. Some of it is not. And the practical difficulty is that at the moment of transfer these look very similar: a list of items, each with a description, each awaiting something.
What separates them is not their appearance in a schedule. It is the question of whose they now are — and that question is answered far more often by default than by decision.
Three things that look identical at the boundary
An open item, a deferred item and an accepted condition are three different positions.
An open item is something still to be done by someone, with the obligation to do it sitting where it always sat. A deferred item is something whose resolution has been postponed by agreement, usually with a route back to it. An accepted condition is something the receiving organisation has taken on, whether or not anyone framed it that way at the time.
Most transfer records distinguish two of the three at best. They record what exists and what is outstanding. They rarely record which of those three positions each item occupies, because at the point of transfer everyone involved knows — and knowing is not the same as recording.
The consequence appears later, and it appears as a cost.
Where a cost is recorded is not where responsibility for it belongs
This is the proposition the whole subject turns on.
Once an organisation is operating an asset, its systems record what it spends. They record it against the asset, against a work order, against a cost centre and against a period. What they do not record is why the organisation is the one spending it.
A condition that arrived with the asset produces expenditure in the receiving organisation’s ledger from the first day, because that organisation is the one that has to act. The ledger is not wrong. It is answering a different question from the one that matters: not who paid, but whose condition is this.
The two answers coincide most of the time. Where they do not, nothing in an accounting system will say so.
What has to be established, and when
The window in which attribution is straightforward is narrow, and it closes quietly.
At the point of transfer, the receiving organisation can usually establish what a condition is, what it was known to be, who knew it, what was expected to happen about it and on what basis it is being taken on. A year later, some of that is reconstruction. Three years later, some of it is unavailable.
The practical test is not whether an organisation intends to pursue anything. Most conditions are absorbed and should be. The test is whether the organisation could establish the position if it needed to — and whether it has decided, consciously, that it will not.
Recording an attribution is cheap at the boundary and expensive afterwards. That asymmetry, rather than any expectation of dispute, is the reason to do it.
The asymmetry of information
There is a structural imbalance at every transfer that no amount of diligence entirely removes.
The organisation handing an asset over knows what happened while it was being created — what was changed, what was substituted, what was decided under pressure and what was left. The organisation receiving it largely knows what it can see, plus what it has been told.
That imbalance is not evidence of bad faith and it is usually nobody’s fault. It is simply the shape of the situation, and it means the receiving organisation’s questions have to be better than its inspections. What was this expected to do? What has it been doing? What was decided about it, by whom, and does that decision still hold?
When a condition changes shape
An inherited condition rarely stays still.
It generates an inspection. The inspection finds something and generates an intervention. The intervention recurs. Eventually a component is replaced, or the operating arrangement around it changes permanently.
Each of those is a point at which the organisation is doing something new — and each is therefore a point at which the original question can be asked again cheaply, while the answer is still available. In practice the escalation is treated as continuation, and nobody asks. The activity grows and the attribution stays where it was never set.
Where that expenditure then feeds a forward cost position, it arrives carrying an assumption nobody made. What a model should be challenged on, and how, is a separate subject.
The decision point
Not every unresolved condition needs to be pursued, and most will not be. Absorbing a condition is frequently the right commercial answer as well as the right operational one.
But absorbing it should be a decision the organisation took, not a position it arrived at because the question was never put. At the boundary, and at each point where a condition changes shape afterwards, the receiving organisation should be able to say which of the three positions each item occupies, and why.
Where a cost is recorded is not necessarily where responsibility for that cost belongs. The organisation that cannot tell the difference will discover it eventually, usually at the least convenient moment and with the least evidence available.
Westheath is engaged where an organisation is taking infrastructure into operation and needs the boundary established before it is inherited.