Extension of Time Applications That Fail on Procedure, Not Merit

Most refused extension of time applications involved a genuine delay. These are the procedural and analytical failures that lose the entitlement anyway.

An extension of time application has to do three things: satisfy the notice and particulars requirements, identify a relevant event the contract recognises, and demonstrate an effect on the completion date. Applications fail far more often on the first and third than on the second, and the failures below are all repairable before the submission is sent.

Why these keep happening

Applications tend to be written when the programme pressure has already become visible, which is usually some months after the first event. By then the notices are late, the records are patchy and several events have overlapped, so the submission becomes a narrative of everything that went wrong rather than a demonstration of one cause and one effect. An assessor receiving that document cannot grant anything specific, so the safe response is to refuse it and ask for particulars, which consumes another month.

1. Giving notice late or in the wrong form

Many forms require notice within a short period of the event occurring or becoming apparent, in a specified manner, and treat compliance as a condition of the entitlement. A notice given by email to the wrong recipient, or buried in a progress report, may not satisfy the clause even though everyone knew about the event.

• Avoid it by: Extract the notice provisions into a one page procedure listing the trigger, the period, the recipient and the required content, and issue notices as standalone documents.
• Proof it is closed: Each notice is a separate dated document addressed to the contractual recipient, with the clause cited.

What it costs you: An entitlement reduced or lost entirely on a procedural point, with the delay still unrecovered.

2. Submitting a global claim without cause and effect

A submission that lists many events, states the project is late by a total period and invites the assessor to grant it, fails because it does not link any cause to any part of the effect. Where it is practically possible to analyse the events individually, a global presentation tends to be rejected, and the rejection is hard to recover from because the work still has to be done afterwards.

• Avoid it by: Analyse each event against the programme, in sequence, and state the effect of each. Where events genuinely interact, show the interaction rather than aggregating it.
• Proof it is closed: Each claimed period of extension is attributed to an identified event with a stated critical path effect.

What it costs you: Months of delay in the assessment, and a weakened position when the properly analysed claim is finally produced.

3. Relying on a programme that was never accepted

An analysis performed against a programme the other party never accepted invites a dispute about the baseline before anyone reaches the substance. If the baseline was rejected, or was never formally accepted, that argument comes first and the delay analysis sits unexamined behind it.

• Avoid it by: Secure formal acceptance of the baseline at the start, and if acceptance was never given, address the baseline question explicitly in the submission rather than hoping it passes.
• Proof it is closed: A written acceptance of the baseline, or a reasoned section of the submission explaining the programme used and why.

What it costs you: The whole submission stalls on a question that should have been settled in month one.

4. Claiming delay to activities that had float

An application showing that an event delayed an activity, without showing that the activity was critical or became critical, has not demonstrated a delay to completion. This is the single most common analytical gap, and it is usually visible immediately to anyone reading the programme.

• Avoid it by: For each event, state the float on the affected activity at the time, whether the float was exhausted and when the activity became critical.
• Proof it is closed: The submission contains a float statement for every affected activity.

What it costs you: Refusal of the application and loss of credibility on the events that were genuinely critical.

5. Failing to update particulars for a continuing event

Where an event continues, many forms require interim particulars at intervals. A single submission at the end of a long event can be non compliant, and the assessment of the later part of the period can be refused even where the earlier part is accepted.

• Avoid it by: Diarise the interval the contract requires and issue updated particulars on that cycle until the event ends.
• Proof it is closed: A log showing particulars issued at the contractual interval throughout the event.

What it costs you: Partial recovery, with the later and often larger part of the period lost.

6. Mixing the time claim with the money claim

Time and cost are separate questions with different tests. A submission that moves between the two makes it impossible to assess either, and it invites the assessor to refuse the whole document rather than to grant the time and defer the cost. It also exposes the time analysis to objections that are really about quantum.

• Avoid it by: Submit the time analysis as a self contained document, with the cost consequences in a separate submission referenced to the period established.
• Proof it is closed: Two documents, each capable of being assessed without the other.

What it costs you: Delay to the time decision, which is the decision that affects the remaining programme.

7. Not pursuing a determination

An application that receives no response is often left to sit. Meanwhile the works continue, the records age and the people who knew what happened leave the project. Many forms impose obligations on the assessor to respond within a period, and the absence of a response has its own consequences.

• Avoid it by: Chase the determination in writing at the contractual interval, and record every request and response.
• Proof it is closed: A correspondence log showing the application, the chasers and the eventual determination or the absence of one.

What it costs you: An entitlement that quietly becomes unprovable through the passage of time.

A short check before you sign

• Every notice is a standalone dated document, inside the contractual period, to the correct recipient.
• Each claimed period of extension is attributed to a specific event with a critical path demonstration.
• The baseline programme used has been formally accepted, or the baseline question is addressed in the submission.
• A float statement exists for every affected activity at the time of the event.
• Interim particulars have been issued at the contractual interval for every continuing event.
• The time submission and the cost submission are separate and individually assessable.

If it has already happened

If an application has already been refused, do not resubmit the same document with a covering letter. Identify whether the refusal was procedural or analytical. If procedural, establish whether the contract allows the step to be taken again and what the consequence of the original failure actually is. If analytical, rebuild the submission event by event with the programme and the records, and present it as a fresh, properly particularised application. Requirements and remedies differ between forms and change over time, so take advice from a licensed legal adviser on the specific wording before deciding whether to resubmit or to escalate under the dispute procedure.

Domira builds and supervises projects across Saudi Arabia, and the commercial discipline above is how its projects stay inside their budget and their programme. Send the drawings, the contract or the site and Domira will tell you where the risk actually sits.