Completion describes the asset. Readiness describes the owner.

Two different things are settled at handover and they are routinely treated as one.

The first is whether the asset is finished: whether it was built as specified, whether the systems work, whether the documents exist. That question has a contract behind it, a date, a certificate, a payment consequence and a named person who signs.

The second is whether the organisation receiving it can operate it. That question has none of those things.

The instrument that tests, rather than records

Almost every handover control is documentary. A register is completed, a manual is submitted, a drawing is marked as-built. Each confirms that a document exists, which is a weaker claim than it looks.

Commissioning is the exception. The US General Services Administration, which builds and modernises federal offices and courthouses, describes it as a quality assurance process for validating that the building's systems meet the designer's intent and the owner's and tenants' requirements.

Read the second half of that. Commissioning does not validate against the drawings. It validates against what the owner said it needed. Which means the owner's requirements have to exist, in advance, in a form precise enough to test against.

That is the quiet condition on the whole exercise, and it is where most programmes fail before they start. A requirement written as high quality finishes cannot be commissioned. A requirement written as a temperature, a response time, a maximum downtime or an accessible isolation point can.

Why the information requirement has to be set at inception

, read: Handover is where the cost lands, and the Gulf is now taking deliveryHandover is where the cost lands, and the Gulf is now taking delivery

Even the testers drift

Commissioning is only as good as the guidance behind it, and guidance rots quietly.

When auditors examined GSA in 2019, its commissioning was still being conducted under a guide issued in 2005. The guide referenced the 2003 version of the LEED rating system while version 4.1 was current, and directed buildings to aim for LEED Silver at a time when GSA's own design standards required Gold. It also predated the move toward continuous monitoring through building automation systems, which is now how a large modern estate actually watches itself.

So an organisation that constructs continuously, and had every reason to keep its testing method current, let it fall roughly a decade and a half behind its own design standards. Nothing in the process reported this, because a commissioning guide has no expiry date and nothing fails when it is old. It was updated in 2020, after the audit.

The point is not the specific lapse. It is that the instruments used to prove readiness need their own assurance, and almost never get it.

The side nobody tests

Commissioning stops at the boundary of the asset. On the other side sits everything that determines whether the asset can be operated, and almost none of it is on the construction contract.

Consider what is required on the day an operator takes custody. Someone trained on this equipment, not equipment like it. A maintenance strategy that says what to do and when. A system holding the asset records, with the records loaded rather than delivered on a drive. Spares, with a policy on what to hold and what to source. Statutory permits and inspections in the operator's name. Insurance transferred. A named route for administering warranty claims, which is the mechanism most quickly lost and most expensive to lose.

Every one of those is the owner's to produce. Every one takes months. None appears on the contractor's programme, which is the only programme being tracked.

Who is entitled to declare it

There is a structural difficulty in how readiness gets asserted.

The party best placed to say the asset is ready is usually the party whose obligation ends the moment it is said. The party who will discover it was not ready has, in most delivery structures, no signature on the decision and frequently has not been recruited yet.

Contract drafting has moved on this. FIDIC's 2017 edition made the supply of as-built records, operation and maintenance manuals and training an express requirement of taking over under Sub-Clause 10.1, and required the Engineer to issue a Notice of No-objection on the records and the manuals. That is a genuine strengthening and it matters in a region where FIDIC based conditions are the norm.

But note the limit of what it fixes. It obliges the contractor to deliver, and it obliges the Engineer to have no objection. It does not ask whether the receiving organisation exists yet.

And afterwards, nobody looks

If readiness were being tested at all, the evidence would show up later, because the way to know whether a building works is to ask the people using it a year in.

That instrument exists. Under US budget guidance, a post occupancy evaluation should generally be conducted twelve months after a project is occupied, to establish how accurately it met its objectives and to improve the capital programming process through lessons learned.

Over the four years from 2014 to 2017, GSA conducted none. Not few: none, on any completed major construction project. Thirteen were commissioned from an external institute in 2018 and 2019, without a policy governing which projects were chosen or how findings reached the next project team. That policy arrived in September 2020.

Officials gave resource constraints as the reason, which is honest and is also the reason always given. An evaluation competes for budget against the next project, and the next project has a sponsor.

The same failure measured across an entire national portfolio

, read: Whether it was worth doing is the least evaluated questionWhether it was worth doing is the least evaluated question

What to examine, and when

The timing rule is the one that changes outcomes. A readiness review three months before taking over can still alter what is produced. The same review afterwards produces an inventory of what is missing, which is a different document with a different use.

• Ask to see the owner's requirements in the form commissioning will test them against. If they are adjectives, readiness cannot be demonstrated, only asserted.
• Ask who is entitled to declare readiness, and whether that person carries any consequence if it turns out to be wrong.
• Ask for the operations readiness programme as a dated plan with named owners, separate from the construction programme. Its absence is the finding, and absence is the normal case.
• Test the pack with a stranger. Whether a competent person who was not involved could operate the asset from what has been supplied is the only honest test, it costs almost nothing, and almost nobody runs it.
• Ask when the first post occupancy review is scheduled. If the answer is that none is, readiness was never going to be checked, only declared.

---

Sources. US Government Accountability Office, Federal Buildings: GSA Can Improve Its Communication about and Assessment of Major Construction Projects, GAO-20-144, December 2019, for the description of commissioning, the condition of the 2005 Building Commissioning Guide and its 2020 replacement, the Office of Management and Budget position on post occupancy evaluations, and the absence of any evaluation between 2014 and 2017. FIDIC, Conditions of Contract, 2017 edition, Sub-Clause 10.1, cited without a link because FIDIC publishes no free text of the conditions. ISO 55001:2024, Clause 8.1, operational planning and control, which the 2024 edition clarified to include life cycle management. ISO 19650-3, information management during the operational phase of assets.