Claims Substantiation in FIDIC: contemporary records and evidence architecture

FIDIC claims rarely fail only because the legal argument is weak. More often, the problem is simpler and harsher: the project team cannot connect the event, responsibility, causation and amount claimed into one verifiable story.

Substantiation is therefore not the final PDF prepared before a dispute. It is an evidence management system that starts on day one.

What has to be proved

In practical FIDIC logic, a claim usually rests on four pillars:

1. Contractual entitlement - the contract clause that gives a right to time, money or another remedy.
2. Event - what happened, when it happened, who was notified and how the event developed.
3. Causation - how the event affected time, resources, cost, sequence or productivity.
4. Quantum - how the amount was calculated and why those costs resulted from the event.

If one pillar is missing, the claim becomes a position letter. It may sound persuasive, but it is difficult for the Engineer, DAAB or tribunal to test.

Contemporary records are infrastructure, not archive

Contemporary records are records created at the time of the event or close to it. Their strength is that they do not look like a retrospective attempt to rewrite the story after conflict has already started.

A basic evidence architecture normally includes:

• daily site reports;
• labour and equipment logs;
• dated photos and videos linked to location and activity;
• correspondence with the Engineer and Employer;
• meeting minutes;
• instructions and RFI responses;
• updated programmes;
• progress records;
• cost records, timesheets, invoices and payroll evidence;
• separate notice and event registers.

The goal is not document volume. The goal is the chain: event -> notice -> impact -> record -> calculation -> claim.

A notice does not prove the claim

The article on the 28-day rule explains why timely notice matters. But notice is only the entry ticket. It preserves a right; it does not prove amount or causation.

After notice, the team should:

• open an event file;
• appoint an evidence owner;
• decide what data must be collected daily;
• link the event to activity IDs in the programme;
• separate direct costs from general complaints;
• maintain a chronology of instructions, decisions and consequences.

If this is not done immediately, the team will reconstruct the claim from memory months later. That is expensive and weak.

Claim narrative: make the story testable

A good claim narrative does not need to be long. It needs to be verifiable.

Useful structure:

1. Executive summary.
2. Contract basis.
3. Chronology.
4. Cause and effect.
5. Records matrix.
6. Time or cost analysis.
7. Relief sought and appendices.

The records matrix is especially important. It disciplines the claim: if a key assertion has no record, the team either supports it or removes it.

Common evidence failures

FIDIC projects often repeat the same mistakes:

• notice was sent but follow-up records were not collected;
• daily reports are too general to show impact;
• photos exist without date, location or activity link;
• programme updates do not reflect actual sequence;
• cost data mixes several causes;
• quantum is calculated without causation;
• the contractor uses a global claim instead of event-by-event analysis.

A global claim may feel convenient because “everything damaged the project”. To a reviewer, it often looks like an attempt to transfer the overall commercial result to the Employer without enough causal analysis.

Minimum records matrix

For every event, maintain a simple table:

Element	What to record
Event ID	Unique event number
Contract basis	Clause / Particular Conditions
Notice	date, addressee, letter reference
Affected activities	activity IDs in the programme
Site evidence	daily reports, photos, manpower/equipment logs
Cost evidence	invoices, timesheets, subcontractor records, payroll
Decision trail	instructions, approvals, determinations
Current status	open / submitted / agreed / disputed

This table does not replace the claim. It makes the claim manageable.

FAQ

Can a claim be proved without perfect records?

Sometimes, but the cost of proof rises sharply. The team has to reconstruct chronology from indirect evidence, giving the other side more room to attack the claim.

Should everything be stored?

No. A document dump is not an evidence system. Records need to be linked to events, activities, costs and decisions.

Who owns evidence architecture?

Usually the Contract Manager, Planner, Quantity Surveyor and site team share ownership. Lawyers help, but cannot replace daily project discipline.

Bridge Consult helps project teams build claim registers, records matrices and evidence architecture before a dispute becomes formal.

Sources and further reading

• Society of Construction Law, Delay and Disruption Protocol, 2nd Edition, February 2017.
• World Bank, Contract Management: Practice Procurement Guidance, Second Edition, May 2024.
• FIDIC, Conditions of Contract for Construction, 2017 edition.
• See also: The 28-day rule, EOT and delay analysis and Notice Register workflow.