The Employer Caused the Delay: Can a Late Notice Still Defeat Your Extension Claim?

A DIFC construction delay notice dispute can turn on the contract even where the employer caused the underlying delay. A clear notice condition may prevent an extension of time if it was not satisfied. Do not assume that proving employer responsibility also proves entitlement to a revised completion date.

The immediate task is to separate three records: what delayed the works, what notice was required, and what happened after the engineer decided the claim. This guide concerns DIFC-governed contractual analysis illustrated by a particular amended construction contract. It does not prescribe one notice period for every Dubai project or every FIDIC edition.

Question	Document to check	Potential confusion
When was the event known?	Instruction, access record or first affected programme	Waiting until the completion date is missed
Was initial notice required?	Executed notice and claims clauses	Assuming a progress report necessarily qualifies
When was the detailed claim due?	Claim particulars and continuing-event provisions	Treating every deadline as the same time bar
Was an engineer's decision challenged?	Decision and dissatisfaction procedure	Rearguing the event while missing a separate challenge step
Did the event affect completion?	Programmes and contemporaneous site records	Equating any delayed activity with completion delay

What does a DIFC construction delay notice protect?

Start with the consequence attached to the notice. Does the clause concern additional time, additional payment, both, or a particular category of claim? Then identify what must be communicated, to whom and when. A notice provision can sit in general conditions while its deadline or consequence is altered in the particular conditions.

The useful source is Panther Real Estate Development LLC v Modern Executive Systems Contracting LLC [2022] DIFC CA 016, decided on 12 May 2023. The contract used an amended FIDIC 1999 form. Its 28-day initial notice requirement was a condition precedent. The appeal also distinguished that requirement from the subsequent 42-day detailed claim and a separate 14-day dissatisfaction notice.

Those numbers are a warning to read the actual documents, not a ready-made calendar for your project. A contract manager working from an unamended form may miss the very amendment that decides the dispute. Put the executed general conditions, particular conditions and contract hierarchy together before preparing a view on entitlement.

For a current file, record the governing law, dispute forum and relevant contract version on the first page of the review. A project in Dubai is not, for that reason alone, governed by DIFC contract law. This article does not assess a different law's treatment of time bars. The starting point for a qualified adviser is the signed bargain and the law applicable to it.

Does employer responsibility mean the contractor gets more time?

Not necessarily. Responsibility for an event and satisfaction of the machinery for an extension are separate questions. Keeping them separate does not excuse an employer's conduct. It prevents a strong factual narrative from concealing a contractual obstacle that must be addressed directly.

Consider a hypothetical late design instruction. The instruction may have delayed procurement, but the claim still needs to identify when the contractor knew about the problem, which notice provision applied and what was sent. A convincing presentation of employer fault cannot supply a missing communication. Equally, a timely communication cannot prove that the event actually delayed completion.

Prepare two columns in the working file. In the first, list the employer acts said to have caused delay. In the second, identify the contractor's corresponding claims steps. Leave gaps visible. If there was no formal notice, identify any contemporary document relied on instead and explain why it may satisfy the actual wording. Do not relabel every meeting minute a notice simply because it mentions a difficulty.

For an employer reviewing the claim, use the same discipline. A time-bar argument should identify the trigger date and the particular omission, not merely assert that the claim is old. It remains important to preserve the employer's instructions, approvals and access records. They are relevant to assessing the event even where the notice issue may ultimately be decisive.

When should the notice clock be investigated?

Investigate it when the delaying event becomes apparent, not only when the final programme shows a missed handover. In Panther, the clock was tied to when the contractor became aware, or ought to have become aware, of the event or circumstance giving rise to the claim. Actual late discovery was therefore not the only relevant date. The Court considered the event's potential to delay completion and did not accept waiting until the completion date had actually passed.

A practical chronology should distinguish the instruction date, the date it reached the responsible team, the date an impact was first identified and the date notice was delivered. They may differ. Add the source for each date. An internal message saying that the issue will affect the completion programme can matter more than a later claim narrative saying the impact was only discovered months afterwards.

Do not assume that uncertainty over the final number of days means nothing can be communicated. Ask what the initial notice actually requires. A developing event and a fully quantified claim are different things. Where the event continues, check the contract's provisions for interim particulars and final substantiation rather than inventing a fresh start date every week.

For recurring problems, avoid a single undifferentiated entry labelled late approvals. Identify each approval package, the required information, the contractual or planned response date, actual receipt and affected activities. This makes it possible to assess whether events belong together or require distinct treatment. The classification is a question for the relevant contract and evidence, not a convenience chosen after a deadline has expired.

Give each event a stable reference that survives later revisions. For example, use a separate record for a delayed lift specification and another for restricted access to the loading area. Cross-reference them if they interact, but retain their different source documents. Record who prepared each chronology entry and whether that person has direct knowledge. When a date is disputed, show both positions instead of silently selecting the date most favourable to your claim. This helps the project team identify the disagreement that needs investigation before its lawyers or planners build an analysis on an unreliable starting point.

Can meeting minutes or an email count as the notice?

They may be relevant, but their existence is not enough. Compare their content and delivery with the notice clause. Identify whether the document explains the event, communicates the intended claim where required, and reaches the person designated by the contract. The answer should come from the actual instrument, not from the document's friendly or formal appearance.

A progress email may describe delay without asserting an entitlement. A letter may assert an entitlement but omit the event relied on. A detailed claim might have been sent to a project manager while the contract specifies the engineer. These are reasons to inspect the original communication, its recipients and attachments. They are not universal rules that a particular label or format always succeeds or fails.

Keep proof of transmission and receipt. If an electronic project portal was used, preserve the relevant submission record and its status rather than only a downloaded PDF. Where an attachment was replaced, retain both versions with clear dates. Do not alter historical subject lines or merge separate communications into a document that appears to have existed at the time.

Common mistake. Saying that everyone knew the site was delayed without identifying the communication relied on as notice, the clause it was meant to satisfy and the evidence that it reached the proper recipient.

Is missing the detailed claim deadline equally fatal?

Do not assume so. Panther treated the 42-day detailed-claim provision differently from the initial 28-day notice condition. Both periods ran from awareness, or required awareness, of the relevant event, not one period after the other. The detailed-claim clause also allowed another period proposed by the contractor and approved by the engineer. The Court accepted the contractor's argument about the different consequences, while still dismissing its appeal because the correction did not change the result on the other issues.

For your contract, mark the express consequence of each missed step. Some provisions expressly remove entitlement. Others concern the material available to assess a claim, or prejudice caused by delay in providing it. The judgment does not make detailed claims optional. Its significance is that different language can produce different consequences within the same claims process.

Prepare the best available substantiation promptly even if one deadline is disputed. Explain what is complete, what remains unavailable and why. Keep the underlying programme files and source records attached to the calculation. A retrospective report can help analyse evidence, but it should not conceal that an earlier submission lacked necessary detail.

Three distinctions should remain visible in the claim register.

What if the engineer has already rejected the extension?

Read the decision provisions immediately. Under the amended clause considered in Panther, a notice of dissatisfaction within 14 days was a separate condition for challenging the engineer's determination. That was a contractual mechanism specific to the agreement, not a general DIFC appeal deadline.

A claims team can focus on proving the delay and overlook this second clock. Put the engineer's determination into the chronology as a new event. Record its date, receipt, subject matter and whether it decides the entire claim or only part. Compare any response with the specified dissatisfaction procedure and recipient.

Do not assume that ongoing meetings reopen a determination. Look for what was actually agreed or directed. If the engineer asks for further information, establish whether the existing determination remains in place and whether the contract still requires a protective response. Obtain advice promptly where the status is unclear. A courteous acknowledgment is not necessarily the challenge the contract requires.

Keep each determination tied to the event and claim it addresses. A later decision on another variation does not necessarily replace an earlier decision on access delay. This indexing task is unglamorous, but it prevents the team from treating several different determinations as a single continuing conversation.

Can the prevention principle or good faith rescue the claim?

They should not be treated as automatic rescue arguments. Panther rejected the attempt to use employer prevention and good faith to bypass the clear notice machinery in that contract. The available extension mechanism was not made ineffective merely because the contractor had failed to operate it.

This is a description of the Court's reasoning on that agreement and the law applied to it. It is not a statement that good faith is irrelevant to every construction dispute. Nor does it answer whether a particular employer agreed a different deadline, gave a binding waiver or induced a specific course of action. Those are separate issues requiring their own pleaded basis and evidence.

If you say the employer agreed not to insist on notice, identify the actual words, speaker, authority and date. Distinguish a promise to review the merits from an agreement to abandon a contractual defence. Send the complete exchange to your adviser, including qualifications. An isolated reassuring sentence can look different when read with the request it answered.

A useful case assessment should identify both the primary route and any alternative route. The primary route might be timely notice. The alternative might be a fact-specific argument about the parties' later conduct. Do not blend them into a vague assertion that the result would be unfair. The factual requirements and risks may differ materially.

How do I show that the event delayed completion?

Start with the programme that was actually in use, then connect the event to the affected activities and completion. A delay to one activity is not necessarily a delay to the completion date. The distinction is important where other work could proceed, float existed or the activity was already affected by another problem.

Ask the planning team to identify the baseline, updates and assumptions used in its analysis. Preserve native files as well as readable exports. Record whether an update was accepted, disputed or simply circulated. A diagram made for litigation should be traceable to source data rather than presented as though it were a contemporaneous site document.

For each event, match the analysis to site diaries, labour records, procurement communications and instructions. If a critical component arrived late, identify the planned and actual delivery dates and what work depended on it. If design information was missing, identify the relevant drawings and why the affected work could not reasonably proceed with what was available.

Ask an expert to test the weaknesses too. What changes if the claimed activity had available float? What if a contractor-responsible delay already controlled completion? What assumptions depend on missing records? These questions make the report more useful for settlement and litigation. An impressive chart does not remove the need to explain what its dates and links represent.

Do I need a delay expert, and who controls the evidence?

The need for expert evidence depends on the actual issues. A short dispute over receipt of a notice may not require a large delay analysis. A disputed critical path across a changing programme may require technical help. Define the question before commissioning the report and distinguish private advice from evidence proposed for court.

The current RDC Part 31 requires permission to call an expert or put an expert report in evidence. It also states the expert's overriding duty to the Court and the need for independent, objective assistance. Paying the expert does not make the expert an advocate for the payer's preferred programme.

Provide adverse records as well as supportive ones. If an internal programme shows a different sequence from the claim model, ask the expert to address it. Tell the expert which facts are agreed, disputed or assumed. Where records are missing, the report should not present a reconstruction with unjustified certainty.

For electronic preservation, RDC 28.1-28.2 expressly includes electronic communications and metadata within its document framework. Preserve the project system's structure and available source material. That is not permission to take confidential records from unrelated projects or to demand unrestricted access to the opponent's systems.

What happens to delay damages if the completion date was not extended?

Check the agreed damages provision and the completion date that remains operative under the contract. Panther rejected the proposition that employer-caused delay necessarily removed delay damages despite the missed notice conditions. It did not establish that every daily rate in every contract is enforceable regardless of wording or evidence.

Separate the calculation from the entitlement dispute. Identify the applicable daily rate, cap, period claimed and any contractually relevant completion or termination date. Mark disputed dates clearly. If the demand includes further completion costs or other losses, separate those items instead of treating everything as one undifferentiated delay penalty.

For a hypothetical calculation only, 20 days at AED 5,000 per day produces AED 100,000 before any applicable contractual cap or adjustment. That multiplication does not establish that 20 days are chargeable. If the proper period is disputed, show alternative calculations with the assumption written beside each one. This makes a settlement discussion more useful than arguing over a headline total.

If you challenge the amount as excessive or otherwise unenforceable, ask for a current-law assessment specific to the governing law and clause. This guide does not supply a current statutory reduction test. A complaint that missing a notice was a small mistake is different from evidence about the harm and amount associated with failure to complete on time.

What does the later history of Panther add?

The appeal was not the final document in the project dispute. A 7 July 2024 consent order recorded a settlement sum and provided for closure upon payment. The order does not itself prove that payment occurred. It should not be described as an appellate reversal of the notice analysis.

That distinction matters when using a judgment in correspondence. A later settlement can resolve the parties' financial position without rewriting an earlier legal ruling. Conversely, reading only an earlier judgment can give a misleading picture of the final commercial outcome. Cite the proposition the judgment actually supports and acknowledge relevant later procedural history.

For your own dispute, keep negotiations on a separate track from compliance with the existing contract and court timetable. A willingness to negotiate does not establish an agreed suspension of either. Ask expressly about any necessary extension and record the answer. Do not infer an agreement simply because both teams continue discussing the final account.

What should the contractor and employer prepare next?

The most useful first deliverable is a short event-and-notice register with links to the source documents. It should allow another reader to reconstruct the sequence without relying on the memory of the person who prepared it. Keep legal conclusions separate from the factual entries so that both can be revised honestly.

1. Confirm the executed form, amendments, governing law and dispute provisions.
2. List each event and the earliest supported knowledge date.
3. Identify the initial notice, detailed claim and delivery evidence separately.
4. Record every engineer determination and any required dissatisfaction response.
5. Connect each claimed period to programme and site evidence.
6. Reconcile time entitlement, money entitlement and damages calculations as separate questions.
7. Obtain advice on gaps before sending admissions, abandoning claims or agreeing a final account.

Use three decision files to organise the assessment without prejudging its result.

Selected official sources were checked on 29 September 2026. The later-history search found the 2024 consent order, but was not a certification of the complete court file. The notice periods discussed above belong to the amended contract considered in Panther. A current dispute needs review of its own agreement and applicable law.

Key takeaway. Prove the delay and audit the claims process in parallel. Employer responsibility, timely notice, a challenge to the engineer and a supported calculation answer different questions.

Frequently Asked Questions

Does employer delay automatically entitle me to an extension? No. The contract's claims machinery can matter independently of who caused the event.

Does every FIDIC contract require notice within 28 days? Do not assume that. Panther concerned an amended 1999 form. Check the executed edition and amendments.

Can I wait until completion is actually late? No such waiting period was accepted in Panther. Its clause turned on when the contractor knew, or ought to have known, of the event giving rise to the claim.

Is the detailed claim deadline the same as initial notice? Not necessarily. Panther distinguished the consequences of the 42-day detailed claim from the 28-day initial notice.

Will good faith automatically excuse a missed notice? No. Panther rejected that attempt to bypass the clear provisions before the Court. Other fact-specific arguments require separate assessment.

Can an earlier notice preserve my challenge to the engineer? Do not assume so. Check any separate dissatisfaction procedure and its deadline after the determination.

Can I simply file my planner's report? Court expert evidence requires permission under RDC Part 31. Obtain directions and distinguish expert opinion from factual project records.

Does Panther's later settlement erase the appeal? The identified consent order records settlement and conditional closure, not a reversal of the appellate notice reasoning.

This article is for general informational purposes only and does not constitute legal advice. Consult a qualified advocate for advice on your specific situation.

Related Guides

See the Dubai and DIFC commercial-contracts section and these related guides.

• Fit-out defects and payment disputes
• Property handover delay and refund disputes
• Unpaid service invoices

Related Guides

Our DIFC commercial contracts page covers payment, suspension, termination, guarantees and shareholder disputes under DIFC-law agreements.

• DIFC fit-out dispute: defects remain and the contractor wants payment
• Old DIFC Debt: Check the Deadline Before Waiting for Payment
• The storage facility was unavailable: can I claim delay costs in DIFC?