FIDIC contract and claims management training: Which capabilities do teams need?

Contract management is not a legal department’s filing activity. It is a daily management discipline shared by project leadership, planning, cost, design, site and commercial teams.

FIDIC contracts are used globally because they provide a structured system of roles, responsibilities and risk allocation. Yet the presence of the contract book on a shelf does not determine project performance. Success depends on translating that system into everyday decisions, communications and records.

Many training programmes proceed clause by clause. Participants learn the vocabulary, but return to site without clarity on who records a delay event, what a notice must contain, how programme impact should be demonstrated, or whether an Engineer’s instruction constitutes a variation. Knowledge has not become an organisational operating system.

Why clause teaching is not enough

A FIDIC contract is a network of linked obligations, time limits and decision points. The General Conditions, Particular Conditions, Employer’s Requirements, drawings, tender documents, programme and other contract documents must be read together. The book, edition, jurisdiction and governing law can also materially alter the process.

FIDIC’s Golden Principles emphasise preserving the participants’ roles, drafting Particular Conditions clearly, maintaining the risk-reward balance, setting reasonable time periods and using the agreed dispute-board mechanism. These principles show why training must answer not only “what does this clause say?” but also “how should the contractual system operate on this project?”

Eight capabilities project teams should build

1. Create the contract map

The team should be able to see the parties, the role and authority of the Engineer or Employer’s Representative, document precedence, key notices, decision periods and dispute steps in one project-specific map.

2. Read risk allocation

Teams need to understand which party carries a risk, whether that party can price and control it, and how the Particular Conditions alter the standard balance. Obligation, exception, timing and consequence must be read together.

3. Operate the notice discipline

The purpose, content, recipient, contractual communication channel and deadline for notices must be made project-specific. Protecting the commercial relationship and protecting contractual rights are not opposites. A timely, measured notice is often the start of early resolution.

4. Produce contemporaneous records

Daily reports, photographs, labour and equipment records, correspondence, minutes, programme updates and cost codes should support the same event chronology. A narrative written months later cannot replace reliable contemporaneous evidence.

5. Demonstrate time impact

Planning teams should do more than issue updated programmes. They need a shared language with site and contract teams on critical path, float, concurrent delay and mitigation. Not every delay changes completion; causation must be demonstrated.

6. Manage variations and cost impact

The team must distinguish instructions, design development, employer requests and correction of defects, while recording scope, quantity, price, time and productivity effects early. Variation control cannot sit with finance alone.

7. Build the claim as an evidence chain

A robust claim connects contractual basis, event, responsibility, causation, time effect, cost effect and remedy. Volume of documents does not substitute for a clear chain of proof.

8. Prevent and escalate disputes appropriately

Commercial reviews, early-warning registers, the Engineer’s agreement/determination process and, where applicable, DAAB/DAB mechanisms should be used at the right time. FIDIC positions dispute boards as an important route for dispute avoidance and resolution before arbitration.

One course should not be delivered identically to everyone

How should the programme be designed?

1. Needs assessment: identify the FIDIC book and edition, Particular Conditions, project stage, current issues and participant roles.
2. Project-document adaptation: bring real notices, instructions, programmes and variation examples into the classroom with confidentiality protected.
3. Role-based modules: follow a common foundation with tailored applications for leadership, site, planning-cost and contract teams.
4. Case simulation: ask participants to evaluate the same event from employer, contractor and Engineer perspectives, drafting the notice and decision.
5. Organisational tools: finish with a notice matrix, event register, variation log, claim checklist and escalation structure.
6. On-the-job reinforcement: review sample files and implementation indicators 30–60 days after the programme.

Measure behaviour, not attendance

Course impact should not be reduced to test scores or satisfaction surveys. More useful indicators include:

• The proportion of late or incomplete notices,
• Changes implemented without being recorded,
• Average time from event to commercial assessment,
• Use of a common event code by planning and cost teams,
• Age of outstanding Engineer/employer decisions,
• Reasons for variance between amounts claimed and agreed,
• Issues resolved before becoming formal disputes.

Seven questions for a tailored programme

1. Which FIDIC book, edition and Particular Conditions apply?
2. Which three processes create the most lost entitlement or cost?
3. Who owns notice, record, programme and cost data?
4. Do teams know the order of precedence of the contract documents?
5. Are variations tracked in a single organisational register?
6. Is there a follow-up and escalation process for Engineer/employer decisions?
7. Which behaviour indicator should improve after training?

FIDIC outcomes depend on the book, edition, Particular Conditions, project documents and governing law. This article is a general training framework, not project-specific contractual or legal advice.