A warning that equipment may arrive late gives the project team an opportunity to respond while it can still change the arrangements. There may be time to expedite delivery or resequence the work without compromising testing. If the team waits until delivery is missed, those choices may no longer be available.
Giving the warning starts that response. The people who can resolve the matter need to speak and agree what will happen, considering the effects on time, cost and the required performance of the works. The Early Warning Register should record their decisions and keep the actions visible as the work proceeds. A notice followed by an entry saying 'discuss at next meeting' achieves little if the opportunity to act passes before the meeting takes place.
When warning is needed
Clause 15.1 of the NEC4 Engineering and Construction Contract (ECC) requires the Contractor and Project Manager to notify each other as soon as either becomes aware of a matter which could increase the total of the Prices, delay Completion, delay meeting a Key Date or impair the performance of the works in use. These effects are often described as time, cost and quality, although the last trigger refers specifically to performance in use.
The team does not need a completed delay analysis or an agreed price before giving a warning. It needs to explain the matter and why it could have one of those effects, using the information available at the time. The Contractor and Project Manager may also warn of other matters which could increase the Contractor's total cost. The early warning fundamentals article explains the notification requirements and contractual procedure.
Responsibility for the underlying problem does not determine whether a warning is needed. A Contractor should not keep a supplier problem to itself because it considers procurement to be its own risk. The Project Manager should not wait to warn of an emerging Client decision until an instruction has been prepared. Both may know something which the other needs in order to manage the work.
The compulsory triggers define when warning is required and when a failure can have contractual consequences. They do not define the limits of sensible project management. Other issues can be brought into the same process, with contractual warnings and their consequences kept identifiable.
Time cost and quality on Ironbark
The fictional Ironbark Recycled Water Scheme is a regional Australian utility project using ECC Option C. It includes a pipeline, pumping station and balancing tank supplying an industrial estate from an existing treatment plant, which remains operational during the work.
For this example, the pump supplier tells the Contractor that delivery may be three weeks later than expected. The pumps are needed for installation and testing before the planned connection to the operating treatment plant. The Contractor gives an early warning and identifies the affected activities. It neither waits for the supplier to confirm the delay nor assumes that a four-week delivery delay will cause the same delay to Completion.
The planner examines the current programme with the site team and treatment plant operator. They establish which preparatory work can continue and whether the connection arrangements allow any flexibility. The commercial team obtains the cost of expediting the original pumps and of any proposed resequencing. The team can then compare the available responses and their likely effects.
The supplier also proposes a pump which could arrive sooner. Its availability does not establish that it is suitable. The designers and commissioning team need to check its performance against the Scope, its compatibility with the controls and any effect on the installation. If the change requires acceptance or an instruction, the relevant contractual process still applies. A solution which protects the date but fails to deliver the required performance has not resolved the problem.
Suppose the team finds that expediting the original pumps and bringing some preparatory work forward will allow commissioning to proceed as planned. It must still check that the revised sequence leaves enough time for testing and does not create additional work elsewhere. The register records the agreed response and the person responsible for each action, including confirmation of delivery and the operator's connection arrangements. As the work proceeds, the team can check whether the response is achieving the intended result.
The warning allows the team to consider the delivery problem as a whole. Giving it does not, by itself, make the supplier's delay a compensation event or transfer the Contractor's procurement responsibility to the Client. Under Option C, payment of costs and the eventual sharing of any difference from the target remain subject to the contract, including the Defined Cost and Disallowed Cost provisions.
Notify first and work through the response
On Ironbark, the supplier, planner and relevant technical staff should begin those discussions when the problem arises. Waiting for the next scheduled early warning meeting could use up the time available to secure the pumps or revise the work. Equally, the Contractor should not delay its warning while it tries to assemble a complete solution. The notice alerts the other party while the necessary enquiries continue.
I would take the detailed discussion directly to the people who can contribute to it, involving the Project Manager or an appropriately authorised delegate when a contractual decision is needed. A focused meeting under clause 15.2 can be held promptly with the relevant participants. Early warning meetings do not have to be confined to a recurring slot in the calendar, with the whole team present for every technical question.
Working outside the regular meeting does not mean working off the record. The outcome should be recorded promptly and reach the people carrying out the work. Any required notice must still follow the contractual communication arrangements. An agreed technical response also needs the appropriate acceptance or instruction where the contract requires one, as discussed in submissions and responses.
Giving an early warning should not depend on first agreeing who will pay. That question may need to be resolved, but it should not prevent the team examining how to reduce the effects. Nor does an early warning replace a compensation event notification. The two procedures have different purposes, as explained in Early Warning or Compensation Event.
What happens when the Contractor fails to warn
By the time the Ironbark team learns that delivery has been missed, a replacement manufacturing slot may have gone and the operator may no longer be able to change the connection arrangements. The project is left dealing with effects which an earlier warning might have helped it avoid.
Where a compensation event is involved, failure to warn can affect its assessment. Under clause 61.5, if the Project Manager decides that the Contractor did not give an early warning which an experienced contractor could have given, the Project Manager notifies that decision in the instruction to submit quotations. Clause 63.7 then requires the compensation event to be assessed as if the Contractor had given the warning.
The assessment needs to consider what a timely warning would have allowed the team to do. If earlier notice would have enabled a different sequence or avoided an expediting cost, the assessed time or cost effect should reflect that. The provision does not give the Project Manager a general power to reject the whole compensation event or apply an arbitrary percentage reduction.
Whether a matter is a compensation event remains a separate question. Late delivery of the Contractor's own pumps does not become one because an early warning was missed. A matter which is a compensation event does not automatically cease to be one because the Contractor failed to warn, although its assessment may change under these provisions.
A missed warning can also affect payment through Disallowed Cost under the applicable main option. On Ironbark's Option C contract, cost which the Project Manager decides was incurred only because the Contractor failed to give a required early warning is Disallowed Cost. The connection between the failure and the cost matters. An invoice associated with the problem is not, for that reason alone, entirely disallowed.
For example, suppose the records establish that a late warning caused an additional expediting charge which an earlier warning would have avoided. That charge may fall within the early warning ground for Disallowed Cost. The ordinary cost of buying the pumps, which would have been incurred anyway, does not fall within that ground merely because the warning was late. This payment assessment is distinct from assessing a compensation event and its effect on the Prices. The applicable Disallowed Cost definition must be checked under the selected main option.
The records should establish when the Contractor became aware of the matter, when it notified and which responses were realistically available at each point. A later claim that 'something could have been done' needs to be tested against that evidence. The Project Manager also has an early warning duty, but these assessment and payment consequences concern the Contractor's failure. They are not matching financial sanctions against both roles.
One register for managing the project
I would use the Early Warning Register as the coordinating record for all project risks and issues, including those which have not yet shown an obvious time, cost or quality effect. This wider use should be agreed at the start, with contractual warnings distinguishable from other recorded matters. Adding a wider issue does not automatically attach the same financial consequences to it.
An environmental issue illustrates why this matters. If it is recorded only in an environmental register, someone may later copy it into the Early Warning Register when a programme effect emerges. It is still the same issue, but there are now two records to maintain and potentially two sets of actions. Recording it centrally from the outset allows its different effects to be considered together. Specialist assessments and statutory records can remain linked to the central entry rather than becoming competing action lists.
A useful entry explains the concern, identifies the affected work and records the response, with responsibility and a date for each action. It links to the programme or technical information where needed. Allocating an action does not change the contract's allocation of financial risk, and using a shared system does not remove the Project Manager's responsibilities for the register. The team needs one current account of what has been decided, without attempting to put every drawing or technical report into it.
Make the meeting useful
The regular early warning meeting should receive the current register and the outcomes of discussions already held. On Ironbark, the team should arrive knowing the supplier's latest position, the available responses and the decisions still needed. That leaves time to challenge assumptions, resolve competing demands and check that earlier actions have had the intended effect.
The meeting must still carry out the cooperative work required by clause 15.3. It should not simply endorse decisions made elsewhere. Someone may identify an effect which the smaller group missed, or the latest programme may show that the proposed response no longer protects commissioning. Unresolved matters need a decision by the appropriate person, rather than another entry saying that discussion will continue at the next meeting.
Under clause 15.4, the Project Manager revises and issues the register within a week of each early warning meeting. If a decision requires a change to Scope, the instruction is issued at the same time as the revised register. Agreed actions should reach the people carrying them out promptly, particularly where work is due before the next meeting. The team then needs to check the result before treating the matter as resolved. On Ironbark, confirmation of a delivery date leaves both delivery itself and the required tests to be completed.
In NEC4 operational workshops, I would work through these arrangements using the team's own issues and records. On Ironbark, the warning needs to lead to decisions which reach procurement and the site in time to protect commissioning. The register should allow anyone reviewing the matter to see what has been agreed, what remains outstanding and whether the response is working.
The contractual provisions discussed here are those of the June 2017 NEC4 ECC incorporating the January 2023 amendments. The signed contract's selected options, Scope, delegations and amendments must be checked.
