PDF-ready lead magnet

FIDIC Claims Playbook

A compact contractor playbook: what to do in the first days after an event, how to protect notice, which records to collect and how to build the claim file.

Working structure

01

Event control

Record the event, date of awareness, affected activities, source party and potential time/cost impact.

02

Notice discipline

Check the 28-day notice, recipient, channel, authorised representative and Particular Conditions requirements.

03

Evidence register

Collect daily records, photos, site instructions, RFIs, minutes, correspondence, programme updates and cost records.

04

EOT path

Connect the event to critical path, baseline, updates, mitigation and concurrency analysis.

05

Quantum path

Separate prolongation, disruption, direct cost, overheads, plant/labour, substantiation and audit trail.

06

DAAB readiness

Keep chronology, entitlement map, notices, evidence bundle and decision log in one claim file.

14-day sprint after the event

Claim control sprint

  1. Day 0–1: open event file and issue internal alert.
  2. Day 1–3: draft notice and verify service requirements.
  3. Day 3–7: lock baseline/update programme and record affected activities.
  4. Day 7–10: collect site records, photos, instructions and cost signals.
  5. Day 10–14: prepare entitlement note, evidence gaps and next action owner.

Claim file spine

Notice registerChronologyEntitlement mapProgramme evidenceQuantum workbookDAAB bundle

This is a practical FIDIC.uz resource, not legal advice. Real disputes require contract wording, Particular Conditions and project facts.