Common Mistakes in FIDIC Claim Notices

FIDIC claim notices are often short documents, but they carry significant contractual weight. A notice is not a ceremonial letter. It is the gateway to entitlement, administration, assessment and dispute avoidance. In many projects the underlying event may be genuine, the impact may be real and the claimant may have a legitimate commercial position, yet the claim becomes vulnerable because the notice was late, vague, misdirected, unsupported or inconsistent with the contract.

FIDIC’s 2017 forms placed greater emphasis on notices, claims and procedural discipline than many users were accustomed to under earlier forms. FIDIC also emphasised greater clarity on notices and communications, separation of claims from disputes, and dispute avoidance mechanisms in its second edition contract suite. That reflects a wider trend in international construction contracting: entitlement is not only about what happened; it is also about whether the party followed the agreed process.

Project teams often assume that any letter complaining about delay, cost, obstruction or change is sufficient. It may not be. A compliant notice should identify that it is a notice under the relevant contract provision, describe the event or circumstance giving rise to the claim, indicate that the claimant considers itself entitled to time, cost or other relief, and be sent to the correct recipient through the correct contractual communication channel.

The words do not need to be theatrical, but they must be clear. A vague progress complaint, a meeting comment, a monthly report note or a general reservation of rights may be argued to constitute notice in some circumstances, but relying on that argument is not good administration. A disciplined project team should make the notice obvious.

Many FIDIC-based contracts require notice within a specified number of days after the claimant became aware, or should have become aware, of the event or circumstance. The exact trigger matters. Teams often measure from the wrong date. They may use the date of instruction, the date impact became obvious, the date of internal approval or the date commercial pressure became serious. The contract may instead require notice from awareness of the event or circumstance itself.

This is why early event identification is critical. A claim notice should not wait until the full delay analysis is complete. The notice preserves the position; the detailed claim develops the position. Waiting for certainty can destroy entitlement.

FIDIC claims often arise under multiple provisions. A late drawing may involve employer obligations, engineer’s instructions, variations, delay damages exposure, extension of time, cost, profit, or other relief. The notice should not be overloaded, but it should identify the contractual basis sufficiently. Where the event may engage several provisions, the claimant should reserve or identify the relevant routes without creating contradiction.

Poor clause referencing causes two problems. First, it allows the responding party to argue that the claim was not properly made. Second, it suggests that the claimant has not understood its own entitlement. That weakens credibility.

A notice should not simply say “delay caused by Employer” or “additional cost due to variation.” It should describe the event with enough factual precision to allow the recipient to understand the issue and investigate it. The notice should identify the instruction, drawing, access problem, authority issue, site condition, suspension, testing problem, late approval, changed requirement or other circumstance.

The claim can be developed later, but the event must be recognisable. A notice that hides the facts behind generic words invites rejection.

FIDIC procedures typically distinguish between initial notice and later particulars. The initial notice is time-sensitive and should preserve entitlement. The detailed submission should include the contractual basis, factual narrative, records, programme analysis, cost build-up and requested relief. Teams sometimes try to include everything in the initial notice and miss the deadline. Others send a notice and never follow with particulars. Both approaches create risk.

The best administration system tracks the claim lifecycle: notice issued, initial particulars due, interim updates due, final particulars due, determination status, agreement status and dispute escalation dates.

Contracts increasingly specify how notices must be served. Email may be acceptable for ordinary correspondence but not for formal notices. A project portal may be used for submittals but not contractual notices. A letter sent to a project manager may not be sufficient if the contract requires service on the Engineer, Employer or Contractor’s Representative at a stated address.

This is not bureaucracy. It is risk control. A notice protocol should be prepared at project start and made available to the project team.

FIDIC 2017 treats Employer and Contractor claims more equally than earlier practice sometimes suggested. Employers also need disciplined notices, particulars and determinations. An Employer seeking delay damages, cost recovery, defects-related relief or other contractual entitlement should not assume that its position is automatically protected. Procedural discipline cuts both ways.

A notice should trigger a record collection process. If a late design approval is notified, the team should collect the design register, correspondence, review comments, programme logic, affected workface records, manpower records and mitigation evidence. If this does not happen immediately, the later claim becomes harder and more expensive to prove.

Each claim notice should confirm:

• Contract name and project reference
• Clause or sub-clause relied upon
• Clear statement that the letter is a notice of claim
• Event or circumstance described with date and facts
• Relief potentially claimed: time, cost, profit, other
• Date of awareness or event start
• Immediate effects known at the time
• Reservation to provide further particulars
• Correct contractual recipient and delivery method
• Internal record collection trigger