A FIDIC claim is often won or lost before the formal submission is written. Project teams may know that an event has caused delay or cost, yet lose entitlement because notice was late, the contractual basis was unclear, or the evidence never connected the event to the financial result. Knowing how to draft FIDIC claims means turning a project problem into a disciplined, contract-based case that can withstand review by the Engineer, Employer, dispute board, or tribunal.
For contractors, developers, and project executives, the objective is not to produce a lengthy narrative. It is to secure the contractual remedy available under the governing FIDIC form while protecting the commercial position throughout the project.
Start With the Contract, Not the Complaint
Every claim must begin with the executed contract. Do not rely on a standard description of the FIDIC Red, Yellow, or Silver Book. The Particular Conditions, amendments, tender clarifications, Employer’s Requirements, and agreed procedures may change both entitlement and procedure.
First identify the applicable edition. Under the 1999 forms, a contractor’s claim procedure is generally associated with Sub-Clause 20.1, while the Engineer’s determination is addressed under Sub-Clause 3.5. The 2017 forms contain a more detailed claims framework under Clause 20 and a revised determination process. These differences matter. Notice requirements, time bars, contemporaneous-record obligations, and the sequence for detailed claims cannot be assumed from another project or another edition.
Then identify the legal route to relief. A delayed drawing, for example, may engage provisions addressing late instructions, variations, Employer risk, exceptional events, or extensions of time. The facts may support more than one clause, but the claim should not become a catalogue of possibilities. State the primary basis, explain why it applies, and preserve alternative grounds where the facts genuinely justify them.
A strong opening position answers four questions immediately: what happened, which provision was triggered, what relief is sought, and when the relevant event occurred.
How to Draft FIDIC Claims Around Entitlement
The best claims follow a clear chain: contractual duty, breach or qualifying event, effect on performance, and remedy. If one link is missing, the other side has room to challenge the claim.
Begin with a short executive statement. Identify the project, contract, claim reference, relevant dates, the party responsible for the event, and the relief requested. Be precise about whether the contractor seeks an extension of time, additional payment, cost, profit where contractually recoverable, or a combination of these remedies.
Next, set out the factual chronology. This is not a diary of every project difficulty. Include the events that establish cause and effect: the instruction requested, the date it was due, the date it was received, the work affected, mitigation steps taken, and the resulting impact. Reference correspondence, meeting minutes, drawings, site records, schedules, and photographs by document number and date.
The contractual analysis should follow the facts, not precede them. Quote only the wording necessary to establish entitlement, then apply that wording to the evidence. A claim that simply repeats contractual clauses looks formulaic. A claim that explains exactly how the Employer’s act prevented timely execution is much harder to dismiss.
Avoid language that overstates the case. Saying an event “caused all delay” may create an unnecessary credibility problem where concurrent delay, contractor performance issues, or downstream disruption also existed. A commercially effective claim identifies uncertainty, addresses competing causes, and states the analysis on which recovery is based.
Treat Notice as a Separate Deliverable
Notice is not a preliminary formality. Under many FIDIC contracts, it is a condition tied to entitlement. A detailed claim submitted months later may not cure a defective or late notice.
The notice should be issued as soon as the claiming party becomes aware, or should have become aware, of the event or circumstance. It should identify the relevant clause, describe the event sufficiently to alert the receiving party, reserve the right to time and money, and request any contractual action needed from the Engineer or Employer.
Do not wait until the full quantum is known. At the notice stage, the project team may only know that the event is likely to affect time or cost. That is enough to protect the position if the notice is contractually compliant. Follow it with updates and the fully detailed claim within the contractual timeframe.
Maintain a notice register. It should track the event, clause, notice deadline, issue date, receipt evidence, detailed-claim deadline, and determination status. On a live project, this simple control can prevent substantial entitlement from being lost through administration.
Prove Causation Before Quantifying Loss
A claim for additional payment is not established merely because costs increased after an Employer-risk event. The claim must show that the event caused the claimed impact and that the impact was not otherwise absorbed, avoided, or caused by the contractor.
For delay claims, use the accepted project schedule as the starting point. Identify the affected activities, explain whether they were on the critical path, and demonstrate the actual or prospective movement to completion. The appropriate delay method depends on the project stage, the available records, and the contractual dispute context. A prospective analysis may be suitable for a live request for an extension of time; a retrospective analysis may be required once actual progress is known.
The method matters less than transparency. Assumptions, logic links, calendar settings, updates, and changes to the baseline should be disclosed. A schedule analysis that cannot be replicated will carry limited weight in a contested determination or arbitration.
For cost, connect each category to the event. Site overheads, prolongation costs, idle labor, equipment, disruption, rework, financing, and subcontractor claims each require their own evidentiary path. Use payroll, invoices, plant logs, timesheets, subcontractor notices, accounting records, and site reports. Where actual costs are incomplete, explain the contractual and factual basis for any estimate rather than presenting a broad percentage as if it were proof.
Mitigation belongs in the claim as well. Describe reasonable steps taken to reduce delay or cost, such as resequencing works, seeking instructions, deploying alternative resources, or adjusting procurement. Mitigation is not an admission that the contractor caused the event. It demonstrates competent project management and helps establish that the claimed loss is reasonable.
Build the Evidence File While the Project Is Live
Contemporaneous records are more persuasive than recollection prepared for a dispute. They also reduce the time and cost of preparing a detailed claim.
The project team should preserve a controlled claim file from the first notice. At a minimum, it should contain the contract and amendments, notices, correspondence, instructions, schedules and updates, daily reports, progress photographs, meeting minutes, resource records, cost documents, and relevant subcontractor material. Keep the file organized by event rather than by document type alone. A decision-maker should be able to move from an event to its contractual basis, evidence, impact analysis, and quantum without searching through unrelated material.
There is a balance to strike. Sending every document ever produced can hide the strongest evidence. A well-drafted claim uses a concise main narrative and a disciplined set of appendices. The narrative tells the case. The appendices prove it.
Ask for a Determination That Can Be Granted
Close the submission with a specific request. State the number of days sought, the amount claimed, the valuation basis, applicable tax treatment where relevant, and any adjustment to the Time for Completion or Contract Price. If the claim remains interim because effects are ongoing, say so clearly and identify the next update date.
Request a determination under the correct contractual mechanism and reserve rights without turning the closing into a threat. The purpose is to create a decision-ready record, not merely to signal dissatisfaction.
A claim should also be consistent with the project’s wider strategy. A contractor may need immediate cash-flow relief, protection of completion-date exposure, or preservation of a position for a later dispute. Those objectives influence the level of detail, timing of expert analysis, and approach to negotiation. They do not justify departing from the contract.
When substantial money, completion exposure, or public-sector scrutiny is involved, early legal and claims support can help align notices, correspondence, schedules, and settlement discussions before positions harden. Sora & Associates advises businesses in complex construction and FIDIC disputes where procedural discipline and commercial strategy must work together.
The most effective FIDIC claim is not the one with the most pages. It is the one that gives the decision-maker a clear contractual route to grant relief, supported by records that make the alternative difficult to defend.