FIDIC Programme and EOT Evidence on EU-Funded Projects
- Jun 27
- 9 min read
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
A practical guide for UK contractors moving into European work and for Baltic EPC and design-and-build teams on CEF-funded jobs. On EU-funded infrastructure the extension of time is won or lost on the FIDIC programme and the records behind it, and both have to survive a funding audit, not just the Engineer. This sets out what Sub-Clause 8.3 demands, how EOT and the notice regime work, and the standard a funded-project claim has to meet.
FIDIC is the contract of EU-funded infrastructure. The roads, rail, water and energy projects financed through the Connecting Europe Facility and the cohesion funds run on the Red and Yellow Books. The pipeline across the Baltic states, from Rail Baltica to the grid and generation work tied to synchronisation with the European network, is FIDIC territory. For a UK contractor, EU work means FIDIC work. For a Baltic EPC or design-and-build team, a CEF-funded job means delivering to a standard set as much by the funding audit as by the Engineer.
The 2017 Second Edition tightened the machinery, and the part that decides who keeps their margin is not the dispute clauses. It is the programme. Under FIDIC the programme is the evidential backbone of every extension of time and every prolongation cost. On a funded job it is also among the first things an auditor reads. A contractor who submits a thin programme, lets it drift out of date, or treats notices as paperwork for later has usually lost the entitlement before the delay arrives, and on EU money that loss can reach back into the grant.
This guide is contractor-facing and planning-led. The legal mechanics of FIDIC claims are covered exhaustively by law firms. What gets far less attention, and what decides whether those mechanics ever work in your favour on a funded project, is the programme and records discipline behind them.
Two audiences crossing into EU-funded FIDIC work
The first is UK contractors expanding into European projects. NEC fluency is an asset here, but it is not the contract on the table, and the FIDIC programme and claims regime works differently enough to catch a strong UK team out. The second is Baltic EPC and design-and-build firms delivering CEF-funded transport and energy work, often meeting the full weight of the 2017 form, and the funding audit behind it, at the same time. Both groups tend to deliver well on site and carry less FIDIC programme discipline than the contract assumes. Rail Baltica and the wider Baltic pipeline sit squarely in this space, though contract form there is a lot-by-lot question rather than a market-wide given, so treat FIDIC as the likely case to check, not the certainty.
The FIDIC programme obligation funded jobs hinge on: Sub-Clause 8.3
The Contractor submits an initial programme within 28 days of the notice of the Commencement Date. That window is tight, and the complaint that a proper programme takes longer to build carries no contractual weight. What goes in it is prescribed in far more detail than the 1999 form ever asked for: the Commencement Date and the Time for Completion of the Works and of each Section, the dates access to the Site is required, the critical path with float shown on logically linked activities, rest days and holidays, key delivery dates for Plant and Materials, and the order and timing of the work. Revised programmes have to show actual progress, the effect of any delays, and the Contractor's proposals to recover them. The programme must be built in the software named in the Employer's Requirements, which on most EU-funded jobs means Primavera P6.
Here is the point most teams miss. The Engineer does not approve the programme. Under Sub-Clause 8.3 the Engineer can only give notice of the extent to which it fails to comply, and must do so within 21 days of the initial programme or 14 days of a revised one. Stay silent past that window and the Engineer is deemed to have given a Notice of No-objection. The defined term Programme means precisely this: the one to which the Engineer has given, or is deemed to have given, that Notice of No-objection.
That deeming provision cuts both ways. A contractor who submits a strong, compliant programme and hears nothing has a Programme that now carries real weight as the agreed baseline. A contractor who submits a weak one and hears nothing has locked in the weakness. And a contractor who submits late, after employer-side delays have already started, hands the Engineer an opening to push those events into the baseline. Submit early, submit complete, and submit in the prescribed form. The discipline at day one sets the strength of every claim that follows.
How an extension of time is won and lost under FIDIC
The pattern is industry-wide, not a quirk of one project. Arcadis has tracked the causes of construction disputes worldwide for fifteen years, across regions that include the UK and continental Europe, and the same few sit at the top almost every year: failure to properly administer the contract, and incomplete or unsubstantiated claims. Not the engineering, and not whether the delay was real, but how the contract was run and how well the claim was evidenced. In the UK the average construction dispute now runs beyond £27 million and takes more than fourteen months to resolve. The figures move by region. The causes barely do. For a contractor on an EU-funded FIDIC job the reading is the one this guide turns on. The delay is rarely what loses the claim. The record is.
Sub-Clause 8.5 sets out the grounds for an extension of time, but FIDIC deliberately prescribes no method for assessing it. The Engineer makes a determination under Sub-Clause 3.7, acting neutrally and reaching a fair decision in the light of all the circumstances. There is no contractual delay-analysis methodology, no mandated window or as-planned-versus-as-built standard. The Engineer is persuaded by the record in front of them.
This is why the programme is the spine of the whole entitlement. An extension of time is an argument about cause and effect on the critical path, and that argument can only be made from a baseline that was credible, a sequence of updates that tracked reality, and a delay event tied to a measurable shift in Planned Completion. Where that chain exists, the determination tends to follow it. Where it does not, the contractor is asking the Engineer to take delay on trust, and on a funded job under audit, trust is in short supply.
The 28-day and 84-day time bars that end claims
FIDIC 2017 runs claims for time and money through Sub-Clause 20.2, and the time bars are unforgiving. A Notice of Claim is due within 28 days of the date the claiming Party became aware, or should have become aware, of the event. Miss it and the entitlement is gone: no extension, no additional payment, the other Party discharged. The fully detailed Claim, including a statement of the contractual or legal basis, follows within 84 days. Miss that and the notice lapses.
There is one piece of relief that contractors lean on too heavily. If the Engineer believes the notice was late, the Engineer has to say so within 14 days, and if the Engineer fails to give that notice the claim is treated as valid despite the lateness. That is a backstop, not a strategy. Noticing inside the 28 days, every time, is the only safe position, and the trigger for that habit is a live programme that surfaces the delay event the week it bites rather than the month the account is assembled. Contemporaneous records are not a claims-department task. They are a planning output, fed by the monthly update and the progress reporting the contract already requires.
Why EU and CEF funding raises the evidence bar
On a privately funded job the audience for a claim is the Engineer. On an EU or Connecting Europe Facility job the audience also includes the funding agency and its auditors, and the money is tied to dated deliverables. CEF grants are paid against milestones, and a slipped milestone is not just a programme problem, it is a reimbursement problem that can reach back into the grant. Claims on these projects are read against an audit standard: every assumption traceable, every delay event evidenced, every cost mapped to a record that stands on its own. The contractor who kept a clean, logic-linked programme and a disciplined record has an audit trail. The one who kept a bar chart and good intentions has an exposure, and on funded work that exposure is shared with the client, which is exactly why funders are starting to ask for independent programme assurance before they release the next tranche.
Bringing NEC-grade discipline into EU FIDIC delivery
There is a transferable skill here, and it runs from NEC into FIDIC rather than the other way. NEC forces habits that FIDIC rewards but does not spell out: explicit assumptions stated on the face of the programme, monthly updates that keep the logic live rather than just rolling the bars, and cause-and-effect narratives written close to the event. FIDIC tells you what to submit. Disciplined NEC practice tells you how to keep it provable for the eighteen months between submission and the claim that relies on it, and how to keep it audit-ready for a funder. For UK teams crossing over, the practical differences between FIDIC and NEC are worth understanding before the first programme is built, because the contract changes but the evidential logic does not.
Concurrent delay: the gap FIDIC leaves you to close
FIDIC 2017 does not solve concurrency. Sub-Clause 8.5 defers it to the rules stated in the Special Provisions, and where the Special Provisions say nothing, the entitlement is assessed as appropriate in all the circumstances. That is a gap a contractor has to close deliberately. Read the Special Provisions before tender, establish whether a concurrency rule has been written in, and where it has not, keep the record clean enough to argue the point on the facts. The widely used reference is the Society of Construction Law Delay and Disruption Protocol, but it is guidance, not a contract term, and it only helps a contractor whose records can carry the analysis.
What an audit-ready programme and claim contain
A compliant submission shows every Sub-Clause 8.3 information item in the prescribed software and form, a critical path traceable end to end, float that is disclosed rather than hidden, and assumptions stated openly, issued inside the 28 days through the route the Employer's Requirements specify. A surviving claim is a Notice inside 28 days, a fully detailed Claim inside 84 with the contractual basis stated, and a delay analysis driven off the accepted baseline and the contemporaneous updates, showing the effect on Planned Completion in clear cause-and-effect terms. On a funded job, add the audit layer: a record an external auditor could follow from event to entitlement without a meeting. None of that is invented at claim time. It is assembled from records the programme discipline was already producing.
What this means for UK and Baltic contractors
For the contractor, the programme is the highest-leverage document on a FIDIC job, and the leverage is realised at tender and in the first month, not at the claim. Rigour early pays back at every notice, every determination and every audit. For the UK firm, it is the difference between winning EU work and delivering it profitably. For the Baltic EPC, it is what turns a CEF-funded award into a clean final account rather than a contested one. And for funders and lenders, independent assurance that a programme and its records would survive both an Engineer's determination and a funding audit is becoming a service in its own right.
How NEC Planning Solutions supports FIDIC and EU-funded projects
NEC Planning Solutions Ltd is a UK-registered project controls consultancy, director-led, with senior accredited review on every output, working across NEC and FIDIC. The firm supports Red and Yellow Book projects on a remote engagement basis: Sub-Clause 8.3 programme preparation and assurance, extension of time and forensic delay analysis, notice and records discipline built to a funding-audit standard and independent merits review of claims before they are served. Recent FIDIC delivery includes a live carbon capture project.
Download the FIDIC EOT and Notice Readiness Checklist
A pre-claim gate covering the Sub-Clause 8.3 programme content, the 28-day and 84-day time bars, the records a determination and a funding audit need, and the concurrency check. Free, direct download, no sign-up.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BSc in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
