What operational readiness actually requires

Operational readiness is one of the few terms in this field that everyone uses and nobody contests. A plant commissioning engineer means one thing by it. A facilities director moving four hundred people into a new building means another. A finance ministry taking on accrual reporting means a third, and would be surprised to be told the word applied.

That range is usually treated as loose talk. It is not. The same conditions hold in all three cases, because in all three an organisation has taken on something it must now run. What is missing is not a narrower definition. It is a specific one.

Seven conditions, already written down

ISO 55001:2024 sets out what an organisation needs in order to operate anything at all. Clause 7 lists seven: resources, competence, awareness, communication, documented information, data and information, and knowledge. Clause 8 then asks the organisation to plan and control the operation itself.

The one support condition that has a deadline attached to it

None of that was written about handover. It was written about running an asset management system, which is exactly why it is useful here. It describes the destination state without any assumption about who caused it or which contract paid for it.

Set the conventional handover pack against that list.

ISO 55001 Clause 7 requires	Arrives at handover	Must already be true of the organisation
Resources: budget, people, spares, support services (7.1)
Competence of the people who will operate it (7.2)
Awareness of what the operation is for (7.3)
Communication, internal and external (7.4)
Documented information (7.5)
Data and information about the asset (7.6)
Knowledge, retained and transferable (7.7)

Two of the seven. Clause 8 then asks the organisation to plan and control the operation itself, which is not a document either, and an organisation that has met two conditions out of seven has not been made ready. It has been sent the paperwork.

FIG. 01The seven support conditions of ISO 55001 Clause 7, against whether each one conventionally arrives in a handover pack. The two that arrive are the two that can be written down, which is not a coincidence.

As-built records satisfy documented information. The asset data satisfies data and information. That is two of seven on the mapping in Figure 01 above, and the five that are missing are the five that describe an organisation rather than a filing system.

Why the substitution is so stable

The obvious reading is that owners are careless. A better reading is that procurement is doing precisely what procurement can do.

A contract can require a document. It can specify its format, its schedule, its acceptance criteria, and the sum withheld until it arrives. It cannot require an organisation to have become competent, and it cannot oblige a workforce to have understood what the operation is for. Those are states, not deliverables, and there is no clause that produces them.

So the readiness requirement is written the only way it can be written, as a document schedule, and the document schedule is then discharged in full. Everyone involved has done what was asked. The condition the requirement was standing in for is never tested, which is the subject of a separate argument about who is entitled to declare readiness and whether anyone goes back to check.

Who tests readiness, and why the answer is usually nobody

The same seven conditions outside the fence line

The conditions are not specific to physical assets, and the clearest demonstration comes from a domain with no construction contract in it at all.

When a government moves from cash to accrual reporting, it acquires an obligation to maintain a class of records it has never maintained, on a basis its staff have not been trained in, using systems that were specified for something else. The IMF's technical guidance treats this as a question of preconditions rather than of method, and a 2025 note from the same source lists the ways the reform gets obstructed. Read that list against Clause 7 and it is nearly a mapping. Do not calculate the resources required. Ignore competency requirements, training and continuing professional development. Position the reform as purely technical and avoid the affected stakeholders. Skip adaptation to the institution's actual capacity. Avoid setting indicators and baselines.

Those are resources, competence, awareness, communication and measurement, arrived at independently, by people describing accounting reform rather than asset handover. The convergence is the argument. A conversion programme can deliver a compliant opening balance sheet and leave behind no function able to sustain it, in the same way and for the same reason that a project can deliver a commissioned asset and leave behind no organisation able to run it. In both cases the deliverable was specified and the state was assumed.

Could it be measured

Here the sourced ground runs out, and it is worth being explicit about where.

What the standards support is that readiness is examinable. NASA closes an Operational Readiness Review only when a panel accepts that hardware, software, personnel and procedures are in place to support operations, and the criteria for entering that review include training already delivered to operators, contingency products tested and installed at the site, a problem escalation process, and an emergency notification process naming who is to be called. That last item is worth sitting with. A formal readiness standard requires the phone numbers. The Infrastructure and Projects Authority runs the same idea as Gate 4, Readiness for Service, and keeps one definition while varying the evidence it seeks across infrastructure, transformation, defence and digital work.

So readiness can be assessed against criteria at a point in time. That is established. Whether it can be measured as a quantity afterwards is not.

Four candidates, all of which describe the organisation rather than the asset:

The interval between taking responsibility and reaching the service level the business case assumed. Ramp-up is already tracked in the process industries and almost nowhere in built assets, and a long ramp against a sound asset is an organisational finding.

Unplanned interruptions in the first operating period that are attributable to operator capability rather than to defect. Separating the two is difficult and contested, which is an argument for measuring it rather than against.

Continuity of the asset record. Whether the register handed over is still being maintained twelve months later, and whether anything that changed in the field reached it. A record that stops being updated was never adopted, only received.

Whether the escalation route worked the first time it was needed. Binary, cheap to observe, and it tests the part of readiness that no document demonstrates.

The honest difficulty with all four is that they are lagging. They report after the fact on a state that had to exist beforehand, which makes them useful for learning and useless as a gate. The corrective is the one the IMF note puts first: set the indicators and the baseline before the transition, not after, because an indicator nobody agreed in advance cannot be evidence of anything later.

What follows

If readiness is a state of the organisation, then the questions that matter are not about the handover pack at all. Who is accountable for each of the five conditions a contract cannot reach. When each was started, measured against when it was needed rather than against the construction programme. What evidence exists that any of them is true. And, for anything being procured now, whether the scope includes the capability to sustain the change or only the change itself.

That last question is the one most often missing, and it costs the most, because the answer arrives long after the programme that should have asked it has closed.

Sources. ISO 55001:2024, Clause 7 on support, listing resources, competence, awareness, communication, documented information, data and information, and knowledge, and Clause 8 on operational planning and control, as the clause titles appear in ISO's published contents. NASA, Operational Readiness Review entrance, review and exit criteria, in the NASA Software Engineering Handbook drawing on NPR 7123.1 and NPR 7120.5, for the panel exit condition that hardware, software, personnel and procedures are in place to support operations, and for the entrance criteria covering operator training, contingency products tested and installed, the problem escalation process and the emergency notification process. Infrastructure and Projects Authority, Gate Review 4: Readiness for Service, version 1.0, for the single gate definition and the separate core, infrastructure, transformation, defence and digital question sets. International Monetary Fund, Obstructing Public Sector Accounting Reform: the Top 10 pitfalls, PFM Blog, 25 August 2025, for the obstructions on resources, competency and training, stakeholder engagement, adaptation to institutional capacity, and indicators and baselines. Abdul Khan and Stephen Mayes, Transition to Accrual Accounting, IMF Technical Notes and Manuals TNM/09/02, September 2009, for the treatment of accrual transition as a question of preconditions.

Operational readiness has seven conditions. Handover delivers two.