Notice Requirements Under FIDIC: Why Timing Matters

A construction team can be factually right and procedurally weak at the same time.

That is why notice management deserves more attention than the usual advice to “send a letter within 28 days.” Under FIDIC-based contracts, the relevant question is not only whether notice was sent. It is whether the correct notice was issued, by the correct party, to the correct recipient, in the required form, within the applicable time, and followed by the required particulars and records.

The exact procedure depends on the FIDIC edition, form and Particular Conditions. Always work from the signed contract.

The 28-day period is not a filing target

Under the 1999 suite, Sub-Clause 20.1 introduced a 28-day period for the Contractor’s notice of claim. The 2017 suite reorganised claims and disputes and contains more detailed procedures, but the importance of prompt notification remains.

FIDIC has publicly clarified in relation to the 2017 suite that the 28-day period runs from when the claiming Party became aware, or should have become aware, of the event or circumstance—not from the later date on which the event happens to become critical to completion.

That distinction is commercially important.

Suppose access to an area is unavailable on 1 March, but the affected activity does not become critical until April. Waiting until April because “there is no delay yet” may create a notice problem. The notice protects the position while the actual time or money effect is still developing.

Why contracts require early notice

A notice is not only a procedural trap. Properly used, it performs several project-management functions:

• identifies the event while facts are fresh;
• gives the other party an opportunity to investigate;
• allows mitigation before the impact grows;
• triggers record-keeping;
• separates the event from normal project noise;
• creates a contemporaneous contractual position; and
• supports timely determination rather than a retrospective surprise.

FIDIC’s 2017 forms also introduced an Advance Warning mechanism. FIDIC has explained that early warnings are intended to help minimise and mitigate claims and disputes.

A well-run project therefore treats notices as risk communication, not as an act of aggression.

Step 1: identify the trigger

The first control is the awareness date.

For every potential event, record:

• date the event occurred;
• date the project team first knew of it;
• date the relevant contractual team became aware;
• date it reasonably should have been recognised as potentially claim-relevant; and
• source record establishing that date.

Possible trigger records include instructions, rejection letters, access records, late drawings, meeting minutes, progress reports, site photographs and correspondence.

Do not wait for the quantum or delay analysis to be complete before recording the trigger.

Step 2: use the correct contractual communication

A normal email may communicate a fact without satisfying the contract’s definition of a Notice.

Review the notice/communications clause for:

• required written form;
• whether the document must be identified as a “Notice”;
• nominated recipient;
• copy requirements;
• address;
• electronic document management platform;
• authorised representatives;
• language; and
• deemed-receipt rules.

The 2017 FIDIC suite strengthened the formal distinction between Notices and other communications. That makes disciplined document labelling and routing particularly important.

A project should not discover during a dispute that a commercially important email was sent to the wrong person or never constituted the required contractual notice.

Step 3: describe the event, not the entire claim

The first notice is generally an event-preservation document, not the final expert report.

It should clearly identify:

• the event or circumstance;
• relevant dates;
• affected work or obligation;
• the fact that time and/or money may be affected;
• the contractual provision where required or useful; and
• reservation of the relevant entitlement.

Avoid two extremes.

A notice that says only “we reserve all rights” may be too vague to perform the contractual function. At the other end, waiting to quantify every impact before notifying can make the notice late.

The practical standard is: enough information to identify the event and the position, issued early enough to preserve the procedure.

Step 4: separate notice from substantiation

One of the most common administration failures is treating the initial notice as the claim—or treating the later detailed claim as if it cures a missed notice.

Create separate controls for:

1. initial notice;
2. contemporary records;
3. interim particulars for continuing events;
4. fully detailed claim;
5. updates and responses;
6. determination;
7. dissatisfaction/dispute steps where applicable.

The dates may differ by edition and Particular Conditions. The claims register should therefore calculate deadlines from the actual signed contract.

Step 5: manage continuing effects

Many construction events do not have a neat start and finish.

Restricted access may continue. A design approval may remain outstanding. A change may evolve through multiple instructions. A government restriction may affect productivity over months.

For continuing effects, maintain a live event file showing:

• status;
• affected areas;
• records being collected;
• programme impact;
• cost codes;
• mitigation actions;
• notices already issued; and
• next contractual update date.

This prevents the final claim from becoming a retrospective exercise in reconstructing six months of project history.

Common notice failures

“The Employer already knew.”

Actual knowledge may be relevant under some laws and factual circumstances, but it is a poor substitute for contractual compliance. A contract may require formal notice precisely so the event is processed in a defined way.

“It is in the progress report.”

A progress report may identify a problem but may not satisfy the contract’s formal notice requirements.

“We will notify once the impact is certain.”

The time bar can run before the full consequence is known. Early notice and later substantiation are different tasks.

“The instruction is obvious.”

Even where an instruction is clear, the contract may separately require notice of the time or cost consequence.

“The planner is handling it.”

Notice management is multidisciplinary. Planning may identify delay; engineering may identify the instruction; commercial may identify cost; contracts must control the procedural route.

Build a Notice Control Matrix

A live notice register should include at least:

Automated reminders help, but the quality of the register depends on correct event identification and contractual interpretation.

Timing protects more than entitlement

Prompt notice also improves the evidence.

When a project records an event contemporaneously, it becomes easier to establish:

what happened → what work was affected → what was planned → what changed → what mitigation was attempted → what time and cost followed

That is a much stronger position than building a claim years later from memories and incomplete folders.

The practical message is simple: on a FIDIC project, notice management is not clerical administration. It is part of the project’s commercial control system.