FIDIC 28-day claim notice: is a late claim automatically lost?

The safe answer is: treat the 28-day limit as a hard deadline and never plan to rely on an exception. Under the 2017 Red and Yellow Books, a party claiming additional payment, an extension of time or another time/money entitlement within the Clause 20 procedure must give a Notice of Claim as soon as practicable and no later than 28 days after it became aware, or should have become aware, of the event or circumstance. The wording is deliberately severe because FIDIC wants claims to be surfaced while records can still be preserved and the project can still be managed around the event.

One major 2017 change is symmetry. The Clause 20 claims process applies to both Employer and Contractor claims, whereas the 1999 forms treated the parties through different provisions. That matters operationally because the Employer's team also needs a notice discipline; claim management is not something that only the Contractor has to systemise. A project that tracks only contractor notices but does not track Employer entitlements, deductions, delay-related positions or Defects Notification Period issues is not administering the 2017 framework as a two-sided process.

A recurring mistake is to assume that a programme update, progress report, meeting minute or ordinary email is automatically a contractual Notice of Claim. Under the 2017 drafting, notices are intentionally formalised. The communication should clearly operate as a Notice, identify the event or circumstance giving rise to the claim and follow the contract's communication requirements. Progress records are extremely important evidence, but they should not be used as a substitute for the formal notice mechanism. The practical rule is simple: if the team thinks an event may create entitlement, issue the contractual notice and continue developing the evidence separately.

The point many summaries miss is that the 2017 procedure does not end with the sentence 'late means lost'. If the Engineer considers the Notice of Claim to have been given late, the Engineer is required to give a notice to that effect within the contractual response period — commonly described as 14 days under the 2017 forms — with reasons. If the Engineer does not give the required notice, the Notice of Claim is treated as valid under the contractual mechanism, although the other party may still raise its disagreement for determination. This is not permission to submit late. It is a contract-administration safeguard that makes the Engineer's own deadlines important as well.

The initial notice is only the start. Under the 2017 claims procedure, a fully detailed claim is generally required within 84 days after the party became aware, or should have become aware, of the event or circumstance, unless another period is agreed under the contract. The submission should describe the event, state the contractual and/or other legal basis, identify the contemporaneous records relied upon and provide detailed particulars of the money or time claimed. A team that sends the 28-day notice but then fails to develop the contractual basis, cause-and-effect analysis, programme impact and cost substantiation has protected the doorway but not built the claim.

What if the notice really was late? Sub-Clause 20.2.5 of the 2017 framework provides a route for the circumstances of late submission to be considered during agreement or determination. Factors may include prejudice to the other party and evidence that the other party already knew about the event, circumstance or contractual basis. That is why good progress reports and contemporaneous records can still matter to a late-notice argument even though they are not substitutes for the Notice itself. The important distinction is that this is a potential contractual relief mechanism, not an entitlement to ignore the time bar. A party should assume the deadline will be enforced unless the contract administrator determines otherwise under the actual signed terms.

The engineering solution to most notice failures is not better argument after the deadline; it is a better project-control system before the deadline. Every potential claim event should enter a live register with an awareness date, notice deadline, responsible owner, contractual basis, records required, programme impact and commercial status. Site instructions, delayed information, access restrictions, design changes, testing failures, authority delays and interface conflicts should be reviewed routinely for entitlement implications. Gokbilge Engineering's project-management and engineering-consulting services support this operational layer by connecting schedule, scope, interface, technical correspondence and change control so that contract events are identified early and documented coherently. Legal entitlement and governing-law advice should be confirmed with qualified counsel.

This article explains FIDIC contract administration from an engineering and project-delivery perspective. It is not legal advice. The signed contract, Particular Conditions, applicable law and the exact FIDIC edition/reprint always govern the project.