Construction Project Closeout: How GCC Contractors Recover Retention and Exit Projects Cleanly

The Closeout Trap: When Completion Is Not Really the End

Most GCC construction contracts define "completion" at the moment a Taking-Over Certificate (TOC) is issued. For contractors, that moment feels like the project is done. The site hands over, the main workforce demobilises, and attention shifts to the next job.

But the commercial and operational lifecycle does not end at the TOC. In many cases, the hardest part starts there.

On a SAR 180M residential project in Riyadh, the contractor achieved taking-over in month 18. By month 30 — twelve months into the Defects Liability Period — they were still carrying SAR 8.4M in unreleased retention, working through 340 open snag items, and waiting for the client to issue a final account determination. The site was closed. The cost was real.

Closeout failure is not a sign-off problem. It is a systems problem. And most contractors do not have one.

What Project Closeout Actually Involves

Project closeout spans three distinct phases, each with different commercial stakes.

Phase 1 — Handover (at TOC)

Completion of outstanding works and items on the punchlist
As-built drawings and O&M documentation submitted and approved
System commissioning certificates issued
Certificate of Taking Over issued by the client

Phase 2 — Defects Liability Period

Responding to client defect notices within the contractual timeframe
Tracking repair obligations through to verified completion
Distinguishing genuine contractor defects from client-caused damage or scope creep

Phase 3 — Final Account and Retention Release

Agreeing all variations still open at completion
Submitting and agreeing the final account statement
Releasing the first moiety (typically 50% of retention at TOC)
Releasing the second moiety (remaining 50% at DLP expiry)

Each phase has contractual deadlines, financial implications, and documentation requirements. Running them from email and a shared spreadsheet is how contractors lose money they already earned.

Punchlist Management: The Last Cost You Control

A punchlist at handover is normal. On large GCC projects, 200–500 items is not unusual. The question is not whether a list exists — it is whether you have a system to close it.

No ownership. Punchlist items are logged but not assigned to specific subcontractors or in-house trades with deadlines. Without named owners, items age indefinitely.

No cost link. If the subcontractor responsible for the defective item has been paid out and demobilised, recovery is either contractually enforced via performance bond or retention held — or it gets written off. Teams that do not track this let it become a write-off by default.

No structured tracking. The client issues new items by email; the contractor logs them somewhere no one updates; the client thinks nothing is happening. This erodes trust at exactly the moment you need client cooperation on the final account.

A structured snag register fixes all three: item number, description, location, responsible party, target date, status, verification method, and a link to the original defect notice. On a SAR 180M project, 340 snag items averaging SAR 1,200 each equals SAR 408,000 in direct closeout cost. If 15% become subcontractor disputes, that is SAR 61,200 in recoverable costs that disappear without documentation.

Defects Liability Period: Managing Obligations You Have Already Left the Site For

The DLP is a period — typically 12 months under FIDIC Clause 11, though Aramco and ROSHN routinely require 24 months — during which the contractor is obliged to repair defects at their own cost.

Defect notifications go untracked. The client emails a defect notice. It lands in someone's inbox. Two weeks later, it has not been actioned. Under FIDIC Clause 11.3, repeated failure to remedy defects gives the client the right to engage others and charge the cost directly from retention.

Defect cause is not documented. Many DLP defects are not genuine contractor defects — they are wear and tear, client misuse, or scope items added post-completion. Without contemporaneous records at handover (commissioning tests, system certificates, photographic evidence, operator training records), the contractor has no basis to dispute the liability.

Subcontractor DLP obligations expire at different times. If the GC's DLP runs 24 months but the MEP subcontractor's runs 12 months, the GC carries the MEP defect risk for the second year with no contractual recourse. These gaps need to be mapped at contract award, not discovered during an active defect.

A DLP tracking register should cover: notice date, defect description, contractual obligation, responsible party, mobilisation date, completion date, verification certificate, and whether the item is genuinely in scope or disputable.

Retention Release: The Cash That Stays Locked Longer Than It Should

Retention is the most predictable source of cash that contractors fail to recover efficiently.

The mechanics under FIDIC Clause 14.9 are clear: first half released on the Taking-Over Certificate; second half released on DLP expiry and issue of the Performance Certificate. In practice, both releases get delayed — and the delays are rarely unavoidable.

First moiety delays often trace to documentation shortfalls at handover. The TOC is issued, but the client ties the retention release to O&M manual submission, as-built drawing approval, or commissioning certificate sign-off. If those documents are being chased three months after handover, SAR 4M in retention sits idle.

Second moiety delays are worse. The Performance Certificate is issued only when the client is satisfied that all DLP defects have been addressed. If the DLP register is poorly managed, unresolved items become leverage.

For a SAR 150M project with 10% retention (SAR 15M), each month of delayed release costs approximately SAR 75,000–100,000 in financing cost at current GCC lending rates. Across a portfolio of six projects carrying SAR 80M in aggregate retention, this is a commercial management decision, not a back-office function.

A retention register should track per contract: total retention amount, first moiety trigger and release conditions, second moiety trigger and DLP expiry date, actual release dates, and days variance to contractual schedule.

Final Account Settlement: Closing the Commercial Loop

The final account is the agreement between contractor and client on the total amount due — including all variations, adjustments, and claims — for the completed works.

Under FIDIC Clause 14.11, the contractor submits a draft final statement within 56 days of receiving the Performance Certificate. In practice, final account settlement on large GCC projects takes 6–18 months. Three things extend the timeline:

Open variations. Contractors who close off variation pricing during execution reach the final account with 5–8 items to resolve. Contractors who defer all pricing to closeout walk in with 40–60 items — and the client's commercial team has moved on to the next project.

Missing notice trail. Under FIDIC Clause 20.2 (2017 edition), claims require contemporaneous notices and detailed supporting records. If notices were not issued during construction, commercially valid claims become legally vulnerable at final account.

No consolidated claims position. The project manager knows which claims exist. The commercial director knows the numbers. Legal knows the FIDIC basis. Bringing these three sources into a single final account position — with full supporting records — is slow when everything lives in email threads.

A final account tracker follows each item from original entitlement through notice, pricing, submission, client response, and agreed amount — giving the commercial team a live view of what is open, agreed, and at risk.

The Closeout Records That Protect You After Handover

Certain records have commercial value only at closeout — but they need to have been generated throughout the project.

Taking-Over Certificate package: commissioning test results, system performance records, operator training completion, spare parts delivery receipts. These define the baseline condition at handover and are the contractor's defence against DLP claims for systems that were working at TOC.

As-built drawing register: version-controlled record of what was actually built, cross-referenced to approved drawings and RFI outcomes. NEOM and Aramco projects require native CAD/BIM-linked as-builts. Generating these from memory six months after handover is expensive and inaccurate.

Claims documentation bundle: all EOT claims with supporting daily records, resource deployment logs, delay event correspondence, and FIDIC notices. Built contemporaneously, this is the most commercially valuable document set the project produces.

Subcontractor final accounts: agreed amounts per subcontract, any outstanding claims, and release of obligations. Leaving subcontract final accounts open is how main contract retentions get disputed two years after the project is otherwise settled.

Five Closeout Actions You Can Take This Week

Construction project closeout does not require a new system. It requires applying existing project data to closeout workflows before the site team demobilises.

Audit your DLP expiry calendar. List every active project, its TOC date, DLP duration, and DLP expiry. Flag anything expiring in the next 90 days where second moiety retention has not been released.
Build a punchlist register with owners. For every project approaching or past TOC, create a structured snag register with named responsible parties and target close dates.
Map open variations against the final account. List every variation approved-in-principle but not yet commercially agreed. Assign a commercial owner and a resolution timeline before handover.
Check your retention release conditions. For each first and second moiety release due, identify exactly what documentation conditions are blocking it — and who is responsible for those actions.
Consolidate your claims file. Before site records are archived or team members reassigned, gather the contemporaneous record for any live EOT or cost claim: daily reports, resource logs, correspondence, FIDIC notices.