What is a taking-over certificate, and what does it trigger?

What it triggers

Five things move at once, which is why the date is fought over so hard:

• Liquidated damages stop accruing. For a contractor running late, this is often the single largest number on the project.
• The defects liability period starts — so the clock on the contractor’s obligation to return and remedy begins here, not at practical completion of any individual element.
• Retention becomes partly releasable, typically the first half.
• Risk in the works generally passes to the employer, and with it the insurance obligations.
• The employer takes possession and can use the asset — which, for a hotel or a mall, is the day revenue starts.

The argument is never about whether it is finished

It is about the date, and about the test. Substantial completion is not "no outstanding items" — minor snags do not prevent it. Anything preventing beneficial use does. Between those two poles lies a very large amount of money.

Which is why the outstanding-works list attached to the certificate matters more than it looks. It converts an unanswerable question — "is this complete?" — into a tractable one: "is anything on this list preventing use?" That can be settled by walking the building.

And the trap: occupancy is not in your gift

A building with zero snags and no occupancy permission cannot be handed over. The completion-certificate chain — final authority inspections, conformity certification, occupancy permission — runs in series, at the end, with external bodies who did not agree to your handover date.

Everybody watches the snag list, because it is visible and has a burn-down chart. The certificate chain usually sits with one person in a spreadsheet, and it determines the date just as absolutely.