Defects Liability Period Management: How GCC Contractors Track and Recover DLP Costs Without a Paper Trail

What FIDIC Clause 11 Actually Requires

When the Taking Over Certificate is issued on a SAR 250M residential complex in Riyadh, most project teams celebrate, close out their office files, and move the senior staff to the next job. The project is done — except it is not. A 24-month Defects Liability Period has just started, and somewhere between 200 and 600 defect notifications are coming.

The question is not whether defects will appear. They always do. The question is whether you have a system to track them, respond within contractual timeframes, recover costs from responsible subcontractors, and protect your second retention moiety from being eroded by a backlog nobody can see.

FIDIC Clause 11 gives the employer the right to notify defects during the DLP and require the contractor to rectify them at no cost. Three things matter operationally:

• Notification format. Defect notifications from the engineer or employer carry formal weight under Clause 11.1. Verbal or WhatsApp notifications do not — but your site team will accept them, start work, and later have no contractual evidence that the defect was employer-instructed rather than contractor-initiated.
• Response timelines. Clause 11.1 requires defects to be rectified "as soon as practicable." In practice, Aramco specifies 30 days for critical items. NEOM uses a tiered system: 48 hours for safety-impacting defects, 7 days for functional defects, 30 days for cosmetic issues.
• DLP extension. Under Clause 11.3, if the contractor fails to rectify within a reasonable time, the employer can extend the DLP. On a 24-month DLP, a Clause 11.3 extension can add another 12 to 24 months of retention exposure.

Most contractors handle this with a shared spreadsheet. By month 4, the spreadsheet is out of date. By month 12, nobody knows the status of 60% of notifications.

Five DLP Failure Modes

1. No Centralized Defect Register

Notifications arrive via email, WhatsApp, formal letters, and site visits. Without a single register, the same defect gets logged three times or not at all. The commercial director has no portfolio visibility.

2. Informal Acceptance of Verbal Instructions

Field teams fix defects on verbal instruction and never document that the work was performed, who carried it out, and what it cost. There is no basis for either a back-charge or a claim against the employer's extension rights.

3. Subcontract DLP Gaps

The main contract DLP might be 24 months. Your concrete subcontractor's DLP runs 12 months. A defect notification arrives in month 18. The concrete subcontractor is off the hook — and you absorb the rectification cost directly. This gap is almost never mapped at subcontract award — only discovered when it is too late.

4. Second Retention Release Blocked Without Visibility

The second moiety (typically 2.5% of contract value) is held until the Performance Certificate is issued after DLP expiry. On a SAR 200M contract, that is SAR 5M. Teams waiting for it do not know which specific items are blocking it, so they wait instead of acting.

5. Rectification Costs Not Tracked to Responsible Subcontractor

Even when rectification is completed, the cost goes to a miscellaneous project code. Nobody back-charges the responsible sub. Over a 24-month DLP on a SAR 300M project, this informally written-off cost can reach SAR 1.5 to 3M.

What a Proper DLP Register Tracks

A minimum viable DLP register captures eight fields per notification:

• Notification reference and date — from the engineer's formal letter
• Description and location — specific area, floor, element (not "leaking roof")
• Defect type — workmanship, material, design, or third-party damage
• Responsible subcontractor — which package is accountable at award
• Response deadline — calculated from notification date using the contract's specific requirement
• Rectification status — open, in progress, completed, or disputed
• Completion date and sign-off — who confirmed rectification and on what date
• Cost incurred — for back-charge calculation if the sub fails to rectify

The register should generate three outputs: an overdue list (notifications past response deadline), a back-charge pipeline (costs incurred against unresponsive subs), and a retention release tracker (outstanding items blocking the Performance Certificate).

The Subcontractor Back-Charge Chain

The DLP is where back-charge discipline delivers its highest return. When a responsible subcontractor fails to rectify within a reasonable period, you have the right to carry out the work at their cost — provided you issued a written instruction first. This is the step most contractors skip.

The typical pattern: field team calls the sub, the sub agrees to look at it, the sub does not show up for three weeks, the GC's own team fixes it, and there is no documentation that a formal instruction was ever issued. Back-charge denied. Cost absorbed.

A structured DLP workflow:

• Defect notification received and logged within 24 hours
• Written instruction issued to responsible sub within 3 working days — not a WhatsApp message
• Sub response confirmed or non-response formally logged
• If sub fails to respond within 7 days, mobilize own team and document all costs at market rates
• Back-charge notice issued with cost breakdown and supporting records
• Deduction from sub's final account or retention held

On a large GCC project, 60 to 70% of DLP defects are recoverable from subcontractors with a structured system. Without one, recovery rates drop to 20 to 30%.

Cash Flow During DLP: The Second Retention Moiety Problem

On a SAR 200M contract with 5% retention — 2.5% released at TOC, 2.5% held through DLP — the second moiety is SAR 5M. At a short-term financing rate of 6%, that is SAR 300K per year the contractor is paying on money that is contractually theirs.

Three conditions block the Performance Certificate:

• Outstanding defect notifications not yet rectified
• DLP extension triggered under Clause 11.3
• Open variation account not settled

A live DLP dashboard showing retention release status — specifically which items remain open and who owns them — compresses the time between practical completion of DLP obligations and formal Performance Certificate issuance. On a SAR 200M contract, recovering the second moiety two months early saves SAR 50K in financing cost. On a portfolio carrying SAR 40M in aggregate second-moiety retention across eight projects, the number becomes a CFO-level priority.

Portfolio DLP Management for Multi-Project GCs

The real challenge for GCC contractors is not managing one DLP on one project. It is managing overlapping DLPs across 10 to 15 completed projects simultaneously.

A SAR 1B GCC contractor with typical project values of SAR 50 to 200M might have 8 to 12 projects in DLP at any point. That is potentially 3,000 to 6,000 active defect notifications, managed by different resident engineers on different sites, under different subcontract packages with different response timeline requirements per client.

Portfolio visibility requires three things. First, an aggregate retention balance by project — what is due and when. Second, a cross-portfolio defect backlog by subcontractor, which exposes patterns: the concrete sub whose joints start cracking at month 15, the same MEP sub appearing across six simultaneous DLPs. Third, a Performance Certificate timeline forecast updated from live DLP register status.

The cross-project subcontractor view produces the most actionable prequalification data available. A sub who performs well during execution but is consistently unresponsive during DLP gets a lower prequalification score — and lower award ceilings on future projects. That commercial signal is lost entirely when DLP is managed in disconnected project-level spreadsheets.

Five Practical Starting Steps

1. Audit your current DLP portfolio. List every project currently in DLP, its expiry date, second retention balance, and number of open notifications. Most GCC contractors have never compiled this list. The aggregate retention balance is usually a surprise.

2. Build a register for your highest-exposure project first. Eight fields, no automation required initially. Weekly review slot. Start there before expanding to the full portfolio.

3. Map sub DLP expiry dates before the next TOC. Flag every gap where subcontract DLPs expire before the main contract. Address those gaps with contractual extension provisions at subcontract award — not after the defect notification arrives.

4. Issue all defect instructions in writing from this week. A WhatsApp confirmation is not a formal written instruction under FIDIC. Create a one-page defect instruction template your site team can issue in five minutes, and make it the only accepted format.

5. Track DLP rectification cost by responsible subcontractor. Even a manual cost code — "DLP rectification, sub name" — on your accounting system gives you the back-charge data you need. Cost visibility is what drives recovery.

The DLP is the part of the project that contractors stop managing the moment the TOC is issued. That is precisely why it costs them money they were contractually entitled to keep.