Scenario: the plant has been in commercial production for five months with steady revenue — but on paper the project is still “not handed over”: the owner refuses to issue the Taking-Over Certificate (TOC), citing a punch list of outstanding defects, while withholding the completion payment and not starting the warranty clock. The contractor says the owner is using the TOC as commercial leverage. TOC-refusal disputes are disputes over a project’s “status boundary” — before TOC and after TOC are two different legal worlds. This article analyses when refusal is legitimate, when it is abuse, and the “deemed taking-over” effect when the owner already uses the works.
What does the TOC change legally — why do both sides “hold” it?
The taking-over certificate is the status-switching milestone in EPC/construction contracts: from the TOC moment, risk of damage to the works passes from contractor to owner (except contractor-responsibility defects), the warranty/defects-liability clock starts running, delay LDs stop accumulating, completion-linked payments unlock, and performance security may be reduced/released per the clauses. Because the TOC touches money, risk and time simultaneously, both sides have motives to “hold” it: the contractor wants an early TOC to stop LDs and unlock payments; the owner wants a late TOC to keep leverage over defect repairs and cash. TOC conditions typically include: substantial completion, passing performance tests within permitted tolerances, complete as-built documentation, and a punch list containing only defects not affecting safe/basic operation with a cure schedule.
When is TOC refusal legitimate, and when is it abuse?
Legitimate refusal: objective conditions unmet — the works have not passed core performance tests, outstanding defects affect safety or designed operability, mandatory operation documentation is incomplete — in these cases issuing a TOC would be irresponsible, and the owner may refuse with a written statement of each unmet condition. Abusive refusal has recognisable signs: refusal reasons keep shifting each time the contractor cures the old ones; cited defects are minor cosmetic items not affecting operation yet used to block the entire certificate; the owner has put the works into full commercial operation while still declaring “taking-over conditions unmet”; and the TOC hold comes with extra-contractual commercial demands (price cuts, unconditional warranty extensions). Where the abuse pattern is clear, the contractor has two weapons: the deemed taking-over mechanism in many standard forms — owner use of the works for production deems that part taken over with full legal consequences — and the right to take the TOC-eligibility dispute to the dispute mechanism for a status declaration.
Practical resolution: split “used parts” from “defective parts” and discipline the punch list
The operating solution veteran projects use to avoid total TOC deadlock: (1) partial taking-over — issue TOCs for systems/areas already compliant and operating, isolating remaining defects into a separate list with cure milestones and retention proportionate to the defect value, instead of holding 100% of payment for 2% of defects; (2) a disciplined punch list — every defect classified (A: operation-blocking — cure before TOC; B: cure within a post-TOC period), with an owner, a deadline and a close-out confirmation method; an unclassified punch list is a perfect delay tool and bad evidence for both sides; (3) performance milestones decided by test data — whether performance tests pass is determined by measurements in test records, with an independent verifier where the parties disagree — because “a feeling of not yet” is not a legal basis to refuse a certificate the contract has quantified in parameters.
Frequently asked questions
How is refusal to issue the taking-over certificate (TOC) handled?
Test the contract’s TOC conditions: substantial completion, performance tests passed within tolerance, as-built documents, and a punch list with only operation-neutral defects. Refusal must state each unmet condition; if the owner already operates the works commercially, the contractor can invoke deemed taking-over and ask the dispute mechanism to declare the taking-over status.
What if the owner uses the plant but won’t issue the TOC?
Many EPC forms carry a deemed taking-over mechanism: once the owner puts the works into production use, the used portion is deemed taken over — risk passes, warranty starts, and delay LDs stop accruing for that part. The contractor should record the use with minutes, operating data and a formal notice the moment use begins.
How does the punch list affect the TOC?
A proper punch list does not block the TOC if remaining defects do not affect safe/basic operation and carry a cure schedule — TOC with a punch list is standard practice. The list must classify defects (operation-blocking vs post-TOC cure), assign responsibility and close-out deadlines; blocking the whole certificate over minor items is an abuse sign.
How does the TOC relate to warranty and delay LDs?
The TOC starts the warranty/defects-liability period and stops delay-LD accrual; risk of damage also passes to the owner from the TOC (except contractor defects). An owner delaying the TOC without grounds artificially prolongs all three mechanisms — which is why refusals are scrutinised hard for their stated basis.
This article has been quality-reviewed by the FLAW AI Legal Council