Skip to content
Glossary

Operational readiness

The state in which the organisation taking on an asset can actually operate it from the day it becomes responsible, across its people, resources, processes, systems, risk controls and compliance obligations.

Operational readiness is a property of the receiving organisation rather than of the asset. Commissioning establishes that the asset performs. Readiness establishes that somebody can run it, keep it safe and lawful, and absorb the consequences when it fails. Most of the work has to happen in parallel with delivery, because it cannot be done once the delivery organisation has gone.

ISO 55001:2024 sets out what an organisation needs in order to operate anything. Clause 7 requires resources, competence, awareness, communication, documented information, data and information, and knowledge. Clause 8 then requires the organisation to plan and control the operation itself. A conventional handover pack, meaning as-built records and operation and maintenance manuals, satisfies the documented information and the data requirements. It supplies none of the other five, because none of them is a document and none can be transferred by delivering one.

Readiness is examinable rather than declarable. 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 delivered to operators, contingency products tested and installed, a problem escalation process and an emergency notification process naming who is to be called. The Infrastructure and Projects Authority runs the same idea as Gate 4, Readiness for Service, holding one definition while varying the evidence it asks for between infrastructure, transformation, defence and digital work. Both treat readiness as a state tested against criteria before responsibility moves.

The same term, through four lenses

01

Project

the delivery team and the contract

The project treats readiness as a deliverable list, because a list is the part of it a contract can require. Manuals, training sessions, spares, keys: countable items with a completion status.

This is not cynicism, it is the limit of the instrument. A contract can compel the delivery of documents; it cannot compel the transfer of understanding, and the project is measured on the first.

Fixed by

FIDIC Conditions of Contract, 2017 edition, Sub-Clause 10.1, which makes as-built records, O&M manuals and training, where the contract calls for them, a condition of taking over.

Recorded in

The handover checklist and the training attendance records.

02

Engineering

design, commissioning and the technical record

Engineering reads readiness as commissioning completed: systems tested, performance demonstrated, defects listed and closed.

That establishes the asset performs, which is a genuine and expensive achievement, and says nothing about whether an organisation exists that can run it. Commissioning proves the machine; readiness is a property of the operator.

Fixed by

The commissioning plan and the tests on completion under FIDIC Sub-Clause 9.1, and, where the project is certified, the LEED fundamental commissioning and verification prerequisite.

Read the sources

Recorded in

The commissioning file and the defects list.

03

Finance

the accounts and the fixed asset register

Finance has no concept called readiness, and needs one. Its question is whether the asset is capable of operating in the manner management intended, which cannot be answered without reference to the organisation that will operate it.

A budget for the first year of operation is also a readiness condition wearing a finance label: without an approved operating budget covering maintenance, energy and staffing, separate from the project budget, the asset is not operable whatever its commissioning file says.

Fixed by

IPSAS 45, application guidance AG27, on availability for use as the trigger for depreciation. ISO 55001:2024, Clause 7.1, requiring the resources needed for the asset management system to be determined and provided.

Read the sources

  • IPSAS 45, property, plant and equipment2023, effective 1 January 2025; read 2026-09-01.Free in full, with its Basis for Conclusions in the same document. Replaced IPSAS 17 from 1 January 2025.
  • ISO 55001:2024, asset management system requirements2024 edition; read 2026-09-26.ISO’s product page: the publication details and ISO’s own summary of the standard, not the requirement text. The contents, foreword and introduction cited in this publication are taken from the standard’s preview pages hosted on the ANSI webstore, not from this page.

Recorded in

The approved operating budget, and the capitalisation decision.

04

Operations

the people who run and maintain it

For operations, readiness is the whole of it: resources, competence, awareness, communication, documented information, data and information, and knowledge, which is Clause 7 of ISO 55001 in order, plus the control of operation that Clause 8 requires.

A conventional handover pack satisfies the documented information and the data requirements. The other five are not documents and cannot be transferred by delivering one, which is the arithmetic that makes this entry worth reading: two conditions out of seven, and the two that are easiest to certify.

Fixed by

ISO 55001:2024, Clause 7 on support and Clause 8 on operation. NASA’s Operational Readiness Review criteria and the IPA Gate 4, Readiness for Service, question sets both test the same territory before responsibility moves.

Read the sources

Recorded in

A readiness assessment, if one was commissioned. Frequently nowhere.

Where the lenses part

  • Engineering against Operations

    Commissioning tests the asset against the owner’s stated requirements and is paid for, scheduled and independent. Readiness tests the owner, and on most building and infrastructure programmes it is examined by nobody, funded by nobody and on nobody’s critical path. The asymmetry is structural rather than negligent: one side of the boundary has an instrument and a budget, and the other has neither.

  • Project against Operations

    The project can only require what a contract can specify, which is documents and events. Five of the seven conditions are states of an organisation: people trained on this equipment, a named competent person for each critical system, term contracts mobilised, knowledge captured before the team disperses. Each has to be built in parallel with delivery, by the receiving organisation, because none of them can be done once the delivery organisation has gone.

  • Finance against Operations

    Finance settles a capability question at a date; operations discovers over the following year whether the capability was real. Where they part, the accounts have already recognised an operating asset and begun depreciating it, and the correction, if anyone makes one, is a change in estimate rather than an admission that the date was wrong.

What has to agree, and how you would know

The datumHeld byThe test
Who says the organisation is readyProject, OperationsAsk for the signature. A certificate that the asset is complete is not a statement that the organisation can operate it, and on most programmes the second signature does not exist. Its absence is the finding.
Training delivered against systems installedEngineering, OperationsTake the list of critical systems from the commissioning file and check, for each, that named people were trained on that equipment, not on equipment like it, with attendance recorded. NASA’s ORR entrance criteria ask for exactly this before the review can open.
Operating cost from day oneFinance, OperationsCheck that an operating budget for the first full year exists, is approved, and is separate from the project budget. Then check that the term contracts it funds are awarded and mobilised, not merely awarded: procurement takes months, and a contract that is not mobilised is not there on day one.

Sources

ISO 55001:2024, Clause 7 on support and Clause 8 on operation. NASA Software Engineering Handbook, entrance, review and exit criteria for the Operational Readiness Review, drawing on NPR 7123.1 and NPR 7120.5. Infrastructure and Projects Authority, Gate Review 4, Readiness for Service, version 1.0, for the core and sector-specific question sets. FIDIC Conditions of Contract, 2017 edition, Sub-Clauses 10.1 and 10.3 on taking over. ISO 19650-3, information management during the operational phase of assets.

Read the sources