Lead magnet / notices
FIDIC 28/84-day Notice Register
Connect the event, awareness date, notice, records, fully detailed claim and next procedural step into one controlled register.
28/84-day Notice Register
A template for controlling 28-day notices, 84-day fully detailed claims, evidence owner and decision trail.
- Event ID
A separate event number so notices, records and claims do not get mixed.
- Date of awareness
The date from which the 28-day notice period is controlled.
- Evidence owner
Owner for daily records, correspondence, photos, programme data and cost records.
- 84-day deadline
Control date for the fully detailed claim and follow-up submissions.
- Decision trail
Link to Engineer determination, DAAB, NOD and later dispute route.
Why this exists
FIDIC claims are lost to missed dates far more often than to weak arguments. Sub-Clause 20.2 allows 28 days for the notice and 84 for the fully detailed claim, and both run from the event rather than from the moment the team decided to deal with it. The register exists so that the awareness date is captured when the event happens instead of being reconstructed later from correspondence.
Who it is for
- Contract manager and claims specialist — own the register and the deadlines.
- Planner — links each event to the programme and the critical path.
- Project manager — sees from the register where the project is accumulating unnotified exposure.
How to run it on a project
- Open a row on the day of the event, not on the day someone decides to claim.
- In the date field record the awareness date you can evidence: a diary entry, an incoming letter, a minute.
- Review the register at the weekly meeting — an at-risk row must surface before the period expires.
- Tie each row to a specific clause: without a clause reference a notice may not be treated as one.
Questions
Does the register replace the notices themselves?
No. The register is a deadline-control tool, not a form of notice. The notice must be served separately, by the method and to the address set in Sub-Clause 1.3, identified as a notice and citing the clause. The register only ensures you remember to do it in time.
What about rows where the period has already been missed?
Do not delete them. The 2017 edition provides a route to challenge a time bar, and that route needs the factual chronology: when the event occurred, what the Engineer knew of it, and whether late notice caused the Employer prejudice. A deleted row removes exactly that evidence.