
Stage 03 · The Lifecycle
Handover & Transition
A short seam, with long consequences.
The stage
What happens at this stage
Handover can be run as a completeness exercise. Documents are indexed, certificates are signed, keys change hands. The 2017 FIDIC forms strengthened what that requires: where the contract calls for as-built records, operation and maintenance manuals or training, Sub-Clause 10.1 makes the works not ready for taking over until the required Notices of No-objection on the records and the manuals have been given or deemed given and the required training has been completed. A Defects Notification Period of one year, unless the contract says otherwise, then begins.
There appears to be a way past it. Victoria Tyson of Howard Kennedy reads the redrafted Sub-Clause 10.3 as allowing deemed taking over, where tests on completion have been interfered with, even without those documents. That is one practitioner’s reading rather than settled law, and it may never be tested. It is worth knowing before relying on the clause.
All of that is necessary and none of it is sufficient. A contract can compel the delivery of documents. It cannot compel the transfer of understanding, and understanding is what operations actually needs.
This publication reads the gap as structural rather than as anyone’s fault. The party holding much of the delivery knowledge may be approaching the end of its obligations just as the receiving organisation begins to depend on that knowledge, and the incentive to share it weakens as those obligations run out.
The discipline that addresses this has a name: operational readiness. A plant that cannot be run on the day it is finished is an obvious failure, which gives the process industries a direct reason to plan for readiness. Where a building, property or civil infrastructure programme starts readiness work only at commissioning, it is too late to change what is being produced. Operational readiness run as a commissioning activity is a checklist. Run from inception, it is a specification.
What goes wrong
What typically goes wrong
Everything required is delivered, and nothing needed is transferred.
As-built information records what was drawn rather than what was installed.
Late changes are documented commercially but never reflected in the operating record.
The operating team is assembled after the handover it should have specified.
Operational readiness is treated as a commissioning task at the end rather than a requirement set at the beginning.
The Defects Notification Period expires before anyone has operated the asset through a full cycle of conditions.
Questions to ask
Questions worth asking
Could a competent stranger operate this asset from the information we have been given?
What did we accept because it was on the list, rather than because it was usable?
Which decisions were made during construction that we cannot now reconstruct?
What will we discover in month eighteen that somebody knew in month six?
The framework
What to examine at handover
These domains from the assurance framework belong to this stage. Each names a question with a checkable answer and the published requirement or reasoning on which it rests.
5 domains
03.1
Information transfer against stated requirements
Was what was delivered tested against what was asked for, by someone who will have to use it?
View03.2
Knowledge, as distinct from information
Has anyone captured why the asset is the way it is, and what was accepted rather than resolved?
View03.3
Taking over, and what was waived to achieve it
Were the contractual conditions for taking over actually met, and where they were not, who agreed to proceed and on what record?
View03.4
Recognition onto the asset register
Can the thing that was built be traced to the thing that appears on the balance sheet, in both directions?
View03.5
Operational readiness of the organisation
Does an organisation exist that is capable of operating this asset on the day it is handed over, with people in post?
View
The domains in full, with sources The method’s steps at this stage
Writing
Writing on handover
12 articles
- A delivered file is not an accepted recordA handover contract can test that the information arrived and that the Engineer had no objection to it. That proves receipt. It does not prove that the data passed a schema, that its identifiers reconcile with the finance and maintenance records, or that the receiving system can run a transaction on it. Those are three further tests, and where a contract's information conditions end at delivery and absence of objection, each can fail while those information obligations are performed in full.13 min read
- The project crosswalk reaches capitalisation. What survives it?NASA requires a project work breakdown structure to correlate exactly through seven levels to the financial accounting structure, and EXPRO's cost and commitment procedure reconciles the project cost report to the corporate general ledger on a named form with a named owner. Both requirements are scoped to the project. The Saudi Ministry of Finance's asset manual then has finance allocate the project's cost to assets and components at capitalisation. None of the public documents reviewed here says the project's identifiers stay on the asset record after that.17 min read
- The evidence finance needs is in a file finance never seesAccounting asks one question at handover, whether the asset is capable of operating as management intended, and answers it with a certificate written for a different purpose. The document that actually tests capability, against the owner's stated requirements, with dates and measurements, is the commissioning file. The two are produced for different purposes and routed to different functions, so they do not meet.6 min read
- The only test the building ever getsCommissioning is the one assurance instrument that measures instead of reads. The standards that require it price its independence in tiers, publish their reasons, and there is a 1,500-building dataset that says what the money buys. It also says less than it used to, which is worth understanding rather than hiding.11 min read
- Operational readiness has seven conditions. Handover delivers two.The phrase travels across an office move, a production line, a hospital wing and a finance function taking on a new reporting basis, and it survives the journey by meaning nothing specific in any of them. ISO 55001 already makes it specific, and the arithmetic that falls out is uncomfortable.7 min read
- The date a project becomes an asset is not the date on the certificateThere is a moment when a capital project stops being expenditure and starts being an asset, and it is an accounting entry with a date on it. The standard sets a capability test for that date. Practice mostly uses whichever certificate is nearest, and the two are not the same day.8 min read
- Completion describes the asset. Readiness describes the owner.Commissioning is the one handover instrument that tests rather than documents, and it tests the building against the owner's stated requirements. Everything on the other side of the boundary, whether the owner can actually run the thing, has no instrument that tests it, no budget line of its own, and no place on the critical path.7 min read
- Under FIDIC, taking over comes before acceptanceUnder FIDIC 2017, taking over and contractual acceptance of the works are separate. At taking over the owner takes possession and may begin operating; Sub-Clause 11.9 makes the Performance Certificate the document that constitutes acceptance, and it follows a Defects Notification Period of one year unless the Contract Data states otherwise. A general law-firm summary lists what can change at practical completion or taking over: the contractor's insurance of the works ends, the risk of loss transfers, exposure to delay damages stops, and, where the contract provides for it, retention and the performance bond can begin to release. Where they do, much of the hold on the contractor loosens just as the owner's exposure begins.9 min read
- At handover, every review arrives after the leverage has goneAssurance at this stage is triggered by the event that ends the ability to do anything about it. A review three months before taking over can still change what gets produced. The same review afterwards can only describe what is missing, and describing what is missing is not assurance, it is an inventory of the loss.6 min read
- Knowledge has a departure dateClause 7.7 is new in the 2024 edition and it is the one requirement with a deadline the others do not have. Knowledge is held by people, people leave, and on a programme moving from delivery to ownership the people holding it are employed by somebody else on a contract that is ending.7 min read
- The competence you need is not in the asset management functionClauses 7.1 to 7.4 read like human resources boilerplate and get skipped on the way to the interesting parts. They are where the system either becomes real or stays a document, because the decisions that determine asset outcomes are taken in finance, procurement and operations.7 min read
- Handover is where the cost lands, and the Gulf is now taking deliveryThe gap between what a contractor delivers and what an owner can operate has been measured properly once, more than 20 years ago and on another continent. Of the 15.8bn a year it found, 9.0bn fell on owners and operators, after everyone else had gone. The region now taking delivery at scale has no equivalent number.9 min read
Tools
Tools for handover
Each runs in your browser, states its basis and names its sources. Nothing you enter leaves the page.
6 tools
- AssessmentOperational readiness checkPut the questions a readiness review will ask, condition by condition, and name the blockers with their references. The percentage counts your answers; the blockers apply a rule.
- CalendarWhat follows the certificate, and whenEnter one completion or taking-over date and get every consequential date under your contract regime, each computed from the clause that sets it.
- TemplateWarranty register builderA warranty register that dates every item from its own taking over rather than the project’s, and works out the expiry dates itself.
- TemplateTurnover package composerWhat has to change hands at taking over, grouped by what it is for rather than by who produced it, with what depends on each item and how to tell whether it is any good.
- AssessmentCommissioning arrangement checkDescribe who your commissioning provider works for and when they were designated, and see where LEED places the arrangement in the edition you choose, v5 or v4, what that position cannot detect, and what commissioning costs on your own project.
- CatalogueThe question bankEvery question this publication asks, drawn from the framework and the articles, filtered by stage and by source, printable. Runs at every stage.
Reference
Terms this stage relies on
8 terms
- TermOperational readinessThe 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.
- TermAs-built recordsThe record of what was actually constructed, as distinct from what was designed, handed to the owner as a condition of taking over.
- TermTaking overThe contractual event under FIDIC at which the Engineer certifies that the works are complete, apart from any minor outstanding work and defects listed in the certificate. The governing contract determines when any defects period starts and when care of the works and the risk of loss or damage pass. It is not acceptance: under the 2017 edition only the Performance Certificate constitutes acceptance of the works.
- TermDefects Notification PeriodThe period after taking over during which the employer may notify defects in the works and the contractor is obliged to return and rectify them, called the Defects Liability Period in older forms.
- TermAmerican National StandardA standard approved by ANSI as having been developed under its Essential Requirements: ten due-process criteria about how a document is made, none of which concerns what it costs to buy.
- TermCapital work in progressThe account holding a project’s accumulated cost during construction, before the completed asset is transferred to property, plant and equipment and depreciation begins.
- TermTesting and commissioningThe pair of activities that prove an installed asset works: testing checks an item or system against stated criteria, and commissioning is the managed process that verifies the systems work together to meet the owner’s requirements.
- TermPunch listThe list, made near completion, of work that is incomplete or does not conform to the contract, each item to be corrected and then checked off; also called a snag list.

The seam that follows · Handover to operation
Between handover and operations, the asset stops being a project and becomes an operating responsibility, carrying costs, obligations and, where applicable, revenue.
687certificates
to ISO 55001 worldwide in 2024, against 1,474,118 to ISO 9001. Certificates are not conformance, and many organisations apply a standard without certifying; what has not scaled is certification.
Source · The ISO Survey of Management System Standard Certifications, 2024