Skip to content
Projects Advisors

The framework · 03.3 · Handover & Transition

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?

What goes wrong without it

Completion dates are visible, politically weighted and reported upwards. Information conditions are none of those things. When the two conflict, the information condition can give way, through a mechanism that is entirely legitimate and entirely undocumented in its consequence. The waiver is granted to protect a date and the cost of it appears years later in a different budget.

What to examine

4 tests

  1. Read the taking-over certificate against the conditions in the contract. List what was outstanding at the date of issue.
  2. For each outstanding item, find who accepted it and what was recorded about the consequence.
  3. Check whether the required Notice of No-objection on the as-built records and the manuals was given or deemed given, where the contract requires it.
  4. Establish whether any route to deemed taking over was relied on, and if so whether the information obligations were satisfied by another means.

Required by

  • FIDIC Conditions of Contract, 2017 edition, Sub-Clause 10.1, taking over the works, and Sub-Clause 10.3, interference with tests on completion.
  • ISO 21502:2020, Clause 6, covering project closure and transition.

How the method applies it

A record of the method: Lifecycle decision and conditions record, used at Certification and issue of the taking-over certificate.

direct The means produces evidence at least one of the tests above asks for. A reading, and labelled as one.

In the asset lifecycle methodThe steps of the two methods that this domain examines.

Cite this page

Projects Advisors, “03.3 Taking over, and what was waived to achieve it,” revised 2026-10-08, https://projects-advisors.com/framework/handover-and-transition/taking-over-conditions