NEC4 cashflow: why the programme is a financial instrument, not just a delivery plan
- Nov 29, 2025
- 13 min read
Updated: May 22
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
Seven months into a £35 million Option A water sector contract, a contractor was financing £4.2 million of working capital against a project whose bid had assumed less than half that. The work was on programme. The technical performance was sound. The client relationship was working. The cashflow position was not.
The finance director called it a payment timing problem. The commercial team called it slow certification. The planning lead called it the compensation events that were still in dispute. Each of them was partly right, and none of them had identified what the project was actually suffering from, which is a category error that runs through most UK NEC4 administration.
Cashflow on an NEC contract is not an outcome the finance team forecasts from the programme. It is a property of the programme itself, designed in at activity schedule structuring and either preserved or eroded by every subsequent programme decision. Treat it as a forecasting exercise and the working capital position drifts away from the bid assumption. Treat it as a design variable and the contract delivers the cashflow the bid was priced on.
This is not how most contractors run NEC4 projects, and the reason is structural. The planning function owns the programme. The commercial function owns certification. The finance function owns the cash forecast. The three meet weekly but rarely make decisions together. Programme acceptance, compensation event quotations and clause 32 revisions get treated as technical or contractual matters with cashflow consequences that someone else will project. By the time the consequences are visible in the finance report, the decisions that produced them are months old and uneconomic to reverse.
The reframe matters because NEC4 was designed for it. The contract ties payment timing to programme activities, compensation event valuation to the accepted programme at the dividing date, and certification rhythm to the revision cycle. Every cash event that the contractor will receive flows from a programme decision. Contractors who recognise this design the schedule around the cashflow profile they want, within the contract terms. Contractors who do not find themselves financing the gap between the bid assumption and what the programme has quietly delivered.
How NEC4 ties time to cash
Section 5 of the NEC4 ECC is where most analyses of cashflow begin. It is the right place to start technically and the wrong place to start strategically, because the payment clauses operate downstream of decisions that have already determined what the payments will be.
The strategic point of entry is the relationship between activity timing and payment timing. Under Option A, payment is triggered by activity completion. Under Options C, D and E, payment is based on Defined Cost incurred, which is itself a function of when activities are executed. In both cases, the programme decides when the contractor gets paid, not the payment clauses.
This produces three connected relationships that the strongest contractors design deliberately and the rest leave to default.
The first is activity timing. A programme that loads payment-generating activities late shifts the cashflow profile late. The same scope, brought forward where the technical sequence allows, shifts it earlier. Neither version changes the contract price; both change the working capital requirement. The strongest planning functions test sequence flexibility against the cashflow consequence before settling the programme logic.
The second is activity granularity. Twenty large activities produce twenty payment events. The same scope split into eighty smaller activities produces eighty. Granularity is not a technical decision. It is a cashflow decision that contractors typically delegate to the planner, who reasonably designs for operational management rather than for revenue recognition rhythm.
The third is the relationship between programme acceptance and compensation event valuation. Under clause 63.5, compensation events are assessed against the accepted programme current at the dividing date. A contractor with a current accepted programme can demonstrate prospective time impact, agree quotations faster and bring agreed values into the certification cycle sooner. A contractor whose accepted programme is months out of date cannot, and the cash arrives months later than it would otherwise.
These relationships compound. A poorly structured activity schedule, on an out-of-date accepted programme, in a project where compensation events are accumulating without prospective agreement, produces a cashflow profile worse than any of the three contributing factors would predict in isolation. The reverse is also true, and the reverse is what cashflow-disciplined contractors achieve.
The activity schedule is the financial instrument
On Option A projects, the activity schedule is the most consequential cashflow document the contractor will sign. It also tends to be the most under-designed. Most activity schedules get assembled late in the bid cycle from a template the planning team has adapted from the last project, with limited input from the commercial function and almost none from finance. The schedule that results broadly tracks the technical plan. It rarely tracks the cashflow position the bid was priced to deliver.
Four design principles separate activity schedules that function as financial instruments from those that do not.
Size activities to produce a continuous payment stream. Twenty activities of similar value, spread across the project, produce twenty payment events at roughly even intervals. Twenty activities of variable value, concentrated in particular phases, produce erratic payment events with working capital pressure in the gaps. The contract price is unchanged. The cashflow profile is not.
Distribute preliminaries proportionally to when they are actually incurred. Back-loading preliminaries to late-completing activities is a common pattern and a poor one. It means the contractor finances preliminaries through most of the project and only recovers them as the work approaches completion. Distributing preliminaries across time-related activities so that cost recovery tracks cost incurrence is not aggressive. It is operationally accurate and it reduces working capital by hundreds of thousands of pounds on most multi-year contracts.
Build payment-generating activities into the procurement stage of long-lead items. Major industrial work depends on equipment with 40-week lead times and substantial advance payments to suppliers. An activity schedule that only triggers payment on installation forces the contractor to finance the equipment through the whole procurement period. Including procurement-stage payment activities, where the contract allows, brings cost recovery into line with cost outflow and removes one of the largest concentrated working capital exposures from the project.
Use one breakdown across the activity schedule, the WBS and the cost reports. Three breakdowns means a monthly certification process that consumes a week of senior commercial time on reconciliation alone. One breakdown means certification is a verification exercise instead of a reconstruction exercise. The cashflow consequence is operational rather than commercial, but it is real. Every week saved on certification is a week of working capital not financed.
Done together, these four principles change the cashflow profile of an NEC4 contract without changing the contract price, the technical scope or the project programme. The working capital reduction across a multi-year contract typically runs to hundreds of thousands of pounds. The reduction in financing cost flows directly to project margin.
The article on Primavera P6 for NEC programmes covers the WBS and activity coding structures that make this design discipline operationally possible.
Compensation events as a working capital issue
Most contractors treat compensation events as a commercial issue with cashflow consequences for the final account. This understates the working capital impact during the project by an order of magnitude.
Three mechanisms drive the impact, and each is addressable through administration discipline.
The first is pre-agreement financing. When a compensation event arises, the contractor begins incurring costs before the project manager has agreed the value. Additional resources, accelerated work, alternative methods: all financed from working capital until agreement is reached. A £400,000 event that takes three months to agree adds £400,000 of working capital requirement for three months, on top of the underlying project. Across a portfolio of compensation events on a multi-year contract, the cumulative pre-agreement financing position can run into millions.
The second is the value gap when the project manager invokes clause 64. Where the contractor fails to submit a compliant quotation on time, or where the project manager judges the quotation incorrectly assessed, the resulting determination is typically 30 to 60 per cent lower than a properly prepared contractor quotation would have produced. This is not adversarial behaviour. It is the predictable result of an assessor working from incomplete information and defaulting to conservative assumptions. The cashflow consequence is direct: lower agreed values, lower payments, tighter working capital. The article on NEC4 clause 64 and project manager assessments covers the mechanism in detail.
The third is implementation timing. A compensation event agreed and implemented in month four enters the certification cycle from month four. An identical event implemented in month six enters the cycle two months later. On a single event the difference is modest. Across twenty events with average implementation lag of eight weeks versus sixteen weeks, the cashflow profile divergence is substantial even when the eventual total values are identical.
The composite effect is that the speed and quality of compensation event administration is a cashflow management discipline, not just a commercial one. Contractors who run the CE clock tightly, submit acceptance-optimised quotations within deadline and push events to agreement quickly produce working capital outcomes that contractors of equal technical capability cannot match if they let events accumulate.
The article on how to get NEC4 compensation event quotations agreed covers the quotation discipline, and the NEC4 compensation event time bar covers the eight-week procedural mechanism that interacts with all of this.
The accepted programme as a financial document
Clause 31 acceptance is read by most contractors as a procedural milestone. It is also the most underrated cashflow instrument in NEC4.
The connection is rarely flagged in contract guidance but it is consistent across live projects. Compensation event valuation depends on the accepted programme current at the dividing date. Without a current accepted programme, the contractor cannot demonstrate prospective time impact. Quotations are weaker, agreement is slower, clause 64 assessments become more likely. Each consequence is a cashflow consequence. Programme acceptance is therefore not a technical hurdle to be cleared once and forgotten. It is a financial document the contractor needs to keep in force.
There is a less visible second connection. Contractors with persistently weak programme administration tend to experience slower certification cycles and more disputes about progress measurement. The project manager who is not confident in the programme is not confident in the progress claim that derives from it. None of this is explicit in any clause. All of it produces real cashflow consequences over the project life.
The third connection is reputational. Contractors whose programmes get accepted on first or second submission, who maintain them current through clause 32 revisions and who update them against accurate progress data build the kind of relationship with the project manager that supports quicker certification, easier agreement on payment positions and less friction at month-end. This relationship does not appear in the contract. It appears in the bank statement.
The discipline is operational. The article on NEC clause 32 programme revision covers the revision rhythm that keeps the accepted programme current, and what the project manager checks when reviewing an NEC programme covers the acceptance test the programme has to pass.
Finance-based scheduling
The conceptual shift behind cashflow-disciplined NEC4 management is one most contractors have not yet made. Traditional programme management treats cashflow as an output of the schedule. The schedule is built to deliver the technical scope, the cashflow team forecasts the consequences. Finance-based scheduling reverses the relationship. The cashflow position the contractor wants becomes a design constraint the schedule is built to deliver, alongside the technical and contractual requirements.
This sounds abstract. In practice it expresses itself in four operational habits.
Activity sizing decisions get tested against cashflow implications, not just operational management. Sequence decisions consider payment timing where the contract allows the flexibility to choose. Compensation event implementation is aligned to cashflow rhythm where the agreed-in-principle work permits it. Programme revisions are used as cashflow renegotiation moments, not just as technical updates.
None of this requires unusual technical capability. It requires the planning function and the commercial function to make decisions together, with finance present at the decisions that materially affect the working capital position. The structural change is organisational rather than technical, which is why contractors find it harder than it should be.
What the discipline looks like on a live project
A contractor running the cashflow-smart approach shows a recognisable pattern.
At bid, the activity schedule has been modelled against the projected cashflow profile and adjusted where the contract allowed. The bid is priced on what the activity schedule will actually deliver, not on a generic cashflow assumption applied separately.
At programme acceptance, the submission meets clause 31.2 and gets accepted on first or second submission. The accepted programme supports the activity schedule structure designed at bid, and establishes the baseline that subsequent compensation events and revisions will reference.
Through delivery, the programme stays current through clause 32 revisions at the contract data interval. Each revision updates the activity schedule, refreshes the cashflow forecast and surfaces any cashflow optimisation the change has created. The cashflow position is reviewed weekly with commercial, monthly with senior management, and the planning function has direct accountability for the programme decisions that affect it.
Compensation events run on a tight clock. Quotations are acceptance-optimised and submitted within deadline. Clause 64 determinations are rare. The CE log shows a steady cadence of agreed events being implemented, generating a continuous additional payment stream alongside the base contract payments.
At month-end, certification is a verification exercise rather than a reconciliation exercise. The cashflow forecast for the next three months runs within 5 per cent variance, allowing the finance function to plan working capital precisely rather than carrying buffer capacity against forecasting uncertainty.
The cumulative effect across the project life is a working capital position smaller than peers running comparable work, and a financing cost saving that flows straight to project margin.
Why this matters now
The UK construction pipeline is the largest in a generation. The National Infrastructure and Service Transformation Authority pipeline published in March 2026 covers £718 billion of work across water, power, transport, defence and industrial sectors. Most of it is being procured under NEC, with the Procurement Act 2023 adding scrutiny on contractor delivery confidence and financial sustainability that previous regimes did not impose.
Two implications follow. The first is that bid evaluation increasingly weights working capital discipline. Contracting authorities have been burned by contractor insolvencies on major projects and are scrutinising financial robustness more carefully. Contractors with strong cashflow discipline visible across recent projects have a credibility advantage at bid stage. The signals come from references, from financial reporting, from published performance data under the Act's transparency provisions and from how bidders engage with the cashflow implications of their proposed programmes during clarification.
The second is that the work itself is cashflow-intensive in ways that punish weak management. AMP8 water capital delivery carries long programme durations, heavy preliminaries and complex commissioning gates that delay final payment. RIIO-3 power network work involves expensive long-lead equipment with extended procurement cycles. Industrial decarbonisation projects depend on commissioning-intensive handovers. Complex manufacturing facility construction requires validation-dependent payment release. Each of these characteristics makes cashflow management more demanding than general civils, and contractors who treat cashflow as a financial outcome rather than a programme property end up financing more working capital than the bid assumed.
The contractors who internalise the reframe will compete effectively in this pipeline. The contractors who do not will find that contracts producing healthy margins for cashflow-disciplined competitors produce margin erosion for them, even when delivery is technically successful. The differentiator is not the work. It is the cashflow approach to the work.
The discipline that protects margin
Under NEC4, the activity schedule is a financial instrument. Programme acceptance is a financial document. Compensation event administration is a working capital discipline. Clause 32 revisions are cashflow renegotiation moments. None of these descriptions are how most contractors think about the programme, and none of them require unusual technical capability to operationalise.
The contractors who do think about the programme this way design it deliberately around the cashflow position they want. They finance materially less working capital than peers running comparable work. The financing cost savings flow to margin. The reduced working capital exposure releases capacity for the next bid. Across a portfolio of NEC4 contracts, the compounding effect is substantial and the gap between disciplined contractors and the rest widens through the framework cycle.
The contractors who do not think about the programme this way produce the £35 million water sector pattern the article opened with. Cashflow that drifts from the bid assumption, finance directors blaming payment timing, commercial teams blaming certification, and a working capital position no one chose but every operational decision quietly produced. The cause is not any single failure. It is the absence of a financial frame on the planning decisions that are making cashflow happen, and the discipline that fixes it is not technically demanding. It is structural and organisational and it can be built inside a single project.
FAQ
Why is cashflow described as a property of the programme rather than an outcome?
Because NEC4 ties payment timing directly to programme activities. Under Option A, payment is triggered by activity completion. Under Options C, D and E, payment is based on Defined Cost incurred, which is a function of when activities are executed. Every cash event the contractor will receive flows from a programme decision. The framing matters because it shifts ownership of the cashflow outcome from the finance function to the planning and commercial functions together.
What is finance-based scheduling in NEC4 terms?
It is the discipline of treating the cashflow position the contractor wants as a design constraint on the schedule, alongside the technical scope and contractual milestones. Activity sizing, sequence decisions, compensation event implementation timing and programme revision rhythm all get tested against cashflow implications before being settled. The contractor still delivers the technical work, but the schedule that delivers it is designed to produce a working capital profile the bid was priced to support.
Why is the activity schedule structure so consequential under Option A?
Because under Option A, payment is triggered by activity completion. A contract structured as twenty activities produces twenty payment events. The same contract structured as eighty smaller activities produces eighty. The same scope and the same contract price, structured differently, produce materially different cashflow profiles. The activity schedule is therefore the most consequential single cashflow decision on most Option A NEC4 contracts.
How do compensation events affect cashflow during the project rather than at final account?
Through three mechanisms. Cost incurred before the event is agreed is contractor-financed, expanding working capital while agreement is pending. Clause 64 assessments by the project manager typically produce 30 to 60 per cent lower values than well-prepared contractor quotations would have, which reduces payment directly. Implementation timing affects when the agreed value enters the certification cycle, so faster agreement-to-implementation produces better cashflow timing. Across a portfolio of events on a multi-year contract, the cumulative effect is substantial.
What does cashflow-smart NEC4 scheduling actually look like in practice?
The planning function and the commercial function design the activity schedule together at bid stage, with finance involved in the decisions that materially affect working capital. The programme gets accepted on first or second submission. Clause 32 revisions update the cashflow forecast as well as the technical position. Compensation events run on a tight clock with acceptance-optimised quotations. Month-end certification is a verification exercise rather than a reconciliation exercise. The cashflow forecast runs within 5 per cent variance.
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.
Financing more working capital than your bid assumed on a live NEC4 project?
If the activity schedule is producing erratic payment events, if compensation events are accumulating without prospective agreement, or if the cashflow forecast is regularly variant from bid by more than 10 per cent, specialist NEC programme support designs the activity schedule, the WBS, the compensation event approach and the revision rhythm as an integrated cashflow design that protects working capital across the project life.
