FIDIC & Extension of Time Kit
When to use it
When claiming time: combine several events without double counting, track notice deadlines, keep concurrency out of time, and estimate the claim and damages.
Concurrent delay: a period both parties caused; it usually does not earn full compensation.
What you get after purchase
- Three events on one day axis: overlapping days counted once and float used once; concurrency reduces compensation, not time.
- Notice (28 days) and detailed-claim (42/84 days) status per event at a fixed review day, with procedurally secure versus claimed extension.
- Money claim: time cost, plant, head office, profit where allowed and documented disruption, with three damages scenarios, acceleration value and three charts.
- 37 inputs, six metrics, five tables and three charts: three events with start, duration, category, notice and detailed-claim deadlines at a fixed review day; a day union without double counting, secure versus claimed extension, a detailed money claim, damages and acceleration. Not an entitlement decision.
- Bilingual 8-sheet Excel: controls, 20-item 1999/2017 checklist, 40-event register with deadlines and references, a 730-day axis preventing double counting, entitlement, damages and acceleration, and a decision sheet with three charts; incomplete data blocks totals.
- Gift book: FIDIC Contracts & Dispute Resolution Reference.
A fixed-number teaching example, open to everyone before purchase, so you can see how it works.
Supporting your chances of success
This kit combines precise calculations with guidance and organisation to help you work towards your goal. We help you organise inputs, understand options and assess strengths and risks, then suggest practical steps suited to its subject — such as pricing, cash flow or marketing.
Guidance supports decisions, not guaranteed success; estimates depend on the accuracy of your inputs.
Understand the kit step by step
The kit reviews an extension-of-time claim the way the Engineer will: several events on one day axis, notice and detailed-claim deadlines measured at a fixed review day, then cost and damages risk. The result is an organised estimate, not an entitlement decision; that rests with the Engineer under Sub-Clause 3.7 (2017) or 3.5 (1999) and your legal adviser.
What to prepare before starting
Prepare the approved programme updated before each event, events as days from commencement, awareness, notice and detailed-claim days with letter references, float, concurrent delay, daily site and plant costs, delay damages, the cap and the contract price.
From information to a decision
- Choose the edition and set a fixed review day; never rely on the day the file is opened.
- Enter each event: start, duration, whether critical and its risk category (time and cost, with profit, time only, or contractor risk).
- Check notice status (28 days from awareness) and detailed claim (42 days in 1999, 84 in 2017); a late or missed event stays in the claimed figure but leaves the procedurally secure one.
- Read the union of critical days: overlap counted once, float used once, and concurrency deducted from compensable days, not from the extension.
- Build the money claim: time cost, plant and head office, profit only for days of events whose clause allows it, and non-critical disruption only with comparison records.
- Compare damages in three scenarios (claimed accepted, at-risk rejected, no extension) against the cap, then judge acceleration by damages avoided versus its cost.
A simple example to explain the idea
Example: three events (late drawings 20–50, exceptional weather 40–60, Engineer's variation 70–85), float 10, concurrency 8 days, review day 120. Critical days without repetition are 55 (10 overlap removed), so the claimed extension is 45 days. The weather notice went after 34 days, leaving a procedurally secure 35 days. Compensable days are 37 (45 less 8) and the claim is 419,975 (time cost 296,000, plant 74,000, head office 18,500, profit 6,475, disruption 25,000); the secure claim is 313,225. For a 60-day forecast delay at 12,000/day: 180,000 with the claimed extension, 300,000 if at-risk days are rejected and 720,000 with none. Accelerating 10 days for 90,000 saves 120,000.
These figures are illustrative, not approved prices or guaranteed forecasts; they may differ from the worked example below.
How to interpret and use the result
The gap between claimed and secure is your procedural risk; address it with written reasons for lateness. Claim minus damages is a negotiating indicator, not set-off. Damages reaching the cap do not end the risk, as termination rights may open.
A common mistake to avoid
Do not rely on the figures without a documented programme impact analysis, never apply profit or head office by formula alone, and never accelerate at your cost days you are claiming without a written agreement. Particular Conditions and governing law may change time limits and concurrency rules.
Reading the detailed operating plan
37 inputs, six metrics, five tables and three charts: three events with start, duration, category, notice and detailed-claim deadlines at a fixed review day; a day union without double counting, secure versus claimed extension, a detailed money claim, damages and acceleration. Not an entitlement decision.
Gift book with the kit
FIDIC Contracts & Dispute Resolution Reference
After payment you choose the book edition — bilingual or English — and it is added to your library with the kit.
Have a quotation or claim?
Check it with the quote and claim checker before you sign.
Open the checker
