Notice Clauses: The Procedural Traps That Kill Good Entitlements

A notice clause can turn a sound claim into nothing. The failures that recur on every project, what each costs, and the administrative habits that prevent them.

Notice provisions exist so that the other party learns about a problem in time to do something about it. Many are drafted as conditions that must be satisfied before an entitlement arises, which means a late or defective notice can extinguish a claim on facts nobody disputes. The failures below are administrative, repetitive and entirely preventable.

Why these keep happening

Notices are usually the responsibility of whoever is busiest. The event occurs, the site team deals with the practical problem, and the contractual step is remembered a fortnight later when the commercial team hears about it. By then the period has expired, the notice is given anyway, and the parties spend the next year arguing about whether the clause was a condition of the entitlement. The fix is mechanical: a short list of the notice obligations, a single owner, and a weekly habit of asking whether anything happened that requires one.

1. Not knowing which clauses require notice

A construction contract can contain a dozen or more notice obligations, with different triggers, periods, recipients and content requirements, scattered across the conditions. Nobody satisfies obligations they have not read, and the particular conditions often amend the standard periods.

• Avoid it by: At mobilisation, extract every notice obligation into one table with the clause, the trigger, the period, the recipient and the required content.
• Proof it is closed: The notice table exists, is on the project server and was reviewed by both the commercial and the site teams.

What it costs you: Entitlements lost on clauses nobody on the project knew existed.

2. Misjudging when the clock started

Periods usually run from when the event occurred or when the party became aware of it, not from when its effect was understood or quantified. Waiting until the consequences are clear is the most common reason a notice is late, and it feels responsible at the time.

• Avoid it by: Give notice on the facts available, stating that particulars will follow. A notice does not need to quantify anything to be valid.
• Proof it is closed: The notice date is within the period measured from the event, and the particulars follow separately.

What it costs you: A notice given a few days outside the period, which is enough under a strict clause.

3. Sending the notice to the wrong person or by the wrong means

Contracts specify the recipient and often the method and address for notices. A notice to the resident engineer where the clause names the employer representative, or by email where the clause requires delivery to an address, can fail even though everyone received it.

• Avoid it by: Put the correct recipient, address and method from the contract on the notice table, and use a standard notice template that includes them.
• Proof it is closed: Each notice shows the contractual recipient and method, with proof of delivery retained.

What it costs you: A valid claim defeated on service, which is the most avoidable failure of all.

4. Burying the notice inside another document

A paragraph in a progress report, a line in meeting minutes or a comment in a transmittal is not usually a notice, even where it describes the event accurately. The other party is entitled to know that a contractual step is being taken, and a notice has to be identifiable as one.

• Avoid it by: Issue every notice as a separate document, headed as a notice, citing the clause, with its own reference number.
• Proof it is closed: A numbered notice register exists, with each entry a standalone document.

What it costs you: An argument about whether notice was given at all, which consumes months and is often lost.

5. Omitting the content the clause requires

Clauses often specify what the notice must contain: the event, the date, the clause relied on, the works affected and sometimes an estimate of the effect. A notice missing a required element can be treated as defective, and the defect may not be curable once the period has passed.

• Avoid it by: Build a template from the clause itself, with a field for every element it requires, and complete every field.
• Proof it is closed: Each notice can be checked against the clause requirements element by element.

What it costs you: A technically defective notice that gives the other party a complete answer to the claim.

6. Failing to repeat notices for a continuing event

Where an event continues, many contracts require further or updated notices and particulars at intervals. A single notice at the outset can cover only the initial period, leaving the later and often larger part of the effect unsupported.

• Avoid it by: Diarise the interval the clause requires and issue the update whether or not anything has changed, recording the current position each time.
• Proof it is closed: The notice register shows updates at the contractual interval throughout each continuing event.

What it costs you: Partial recovery, with the bulk of the period lost on a procedural point.

7. Treating notices as hostile and avoiding them

Project teams often resist giving notices because they feel adversarial and might damage a working relationship. The consequence is that entitlements accumulate unprotected, and when the relationship deteriorates for other reasons, nothing can be recovered.

• Avoid it by: Agree at mobilisation that notices are administrative rather than confrontational, and issue them routinely so that no single notice carries a signal.
• Proof it is closed: Notices are issued regularly from the first month, not in a cluster when a dispute begins.

What it costs you: A portfolio of unprotected entitlements that becomes worthless the moment the relationship fails.

A short check before you sign

• A notice table listing every obligation, trigger, period, recipient, method and content requirement is in use.
• One named person owns the notice register and reviews it weekly.
• Every notice is a standalone, numbered, clause referencing document with proof of delivery.
• Notices are issued on the facts available rather than held until the effect is quantified.
• Continuing events have updates at the contractual interval.
• The register shows a steady pattern of notices from mobilisation, not a sudden cluster.

If it has already happened

If a notice has been missed, establish first whether the clause is genuinely a condition of the entitlement or merely a procedural requirement, because the two have very different consequences and the answer depends on the wording and the governing law. Then consider whether any later event restarted a period, whether the other party conduct is relevant, and whether an alternative route to the same recovery exists under a different clause. Rules in this area change and turn on precise wording, so this is the point to instruct a licensed legal adviser rather than to send further correspondence that may make the position worse.

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.