NEC4: Early Warning or Compensation Event?

“Early warning or compensation event?” is the wrong question. They are not mutually exclusive and serve different purposes.

An early warning is used to manage the effects of a problem. The compensation event process determines whether an event changes the Prices, Completion Date or Key Dates and assesses those changes.

The same matter may need both processes. It may also need managing before anyone has enough information to decide whether it is a compensation event.

Managing the problem

Under the NEC4 Engineering and Construction Contract (ECC), clause 15.1 identifies matters which must be notified as early warnings. These concern possible increases to the total of the Prices, delay to Completion or meeting a Key Date, or impaired performance of the works in use. The team can also use the process to manage other project issues. The compulsory triggers do not define the limits of sensible project management, although contractual warnings and their consequences need to remain identifiable.

That work does not depend on establishing liability. A supplier’s difficulty may remain entirely the Contractor’s risk, but the project will still benefit from considering alternative supply or a different sequence. A problem for which the Client is responsible needs the same attention.

The people who can resolve the matter should begin discussing it promptly, rather than wait for the next scheduled early warning meeting. The Early Warning Register should record the agreed response, who will act and what remains unresolved. The meeting can then examine those decisions, consider wider effects and review progress. Neither the warning nor an agreed action establishes a right to additional time or money, and any required instruction or acceptance still needs to follow the contract.

Assessing time and cost

The compensation event procedure addresses the contractual consequences separately. Agreement that an event qualifies does not establish its price or show that the Completion Date must change.

A problem may have several causes. The assessment must identify the effects attributable to the compensation event and distinguish them from those remaining the Contractor’s liability. It also assumes that the Contractor reacts competently and promptly, so avoiding unnecessary disruption remains relevant to the assessment.

When both notifications are needed

An early warning is not a preliminary stage which must be completed before a compensation event can be notified. If the Contractor already believes that an event which has happened or is expected to happen is a compensation event, and the Project Manager has not notified it, the Contractor notifies under clause 61.3. It need not wait for an early warning meeting, a completed investigation or a detailed calculation of the effects.

Where both notices are required, they must be communicated separately in accordance with clause 13.7 and the contract’s communication arrangements. An early warning, register entry or discussion at a meeting does not replace a compensation event notification.

Clause 15.1 also says that early warning of a matter previously notified as a compensation event is not required. There is no need to issue a duplicate warning simply to complete a sequence of forms. The team can still use the early warning process and register to manage outstanding effects; notifying the compensation event does not make that cooperative work unnecessary.

For a Contractor-notified event such as the physical conditions in the example below, the usual eight-week time bar runs from awareness that the event has happened, not from a later conclusion about its contractual significance. An early warning does not stop that period running. Clause 61.3 contains an exception where the event arises from the specified instructions, notifications, certificates or changed decisions of the Project Manager or Supervisor. That exception does not cover every event involving the Client, and it is not a reason to delay notification.

Failure to give an early warning

A later compensation event notification does not excuse a warning which should have been given earlier. Under clause 61.5, if the Project Manager decides that the Contractor failed to give an early warning which an experienced contractor could have given, it states that decision in the instruction to submit quotations. Clause 63.7 then requires assessment as though the warning had been given. The assessment reflects the effects which timely action could have avoided; it is not an arbitrary deduction or automatic rejection of the whole compensation event.

Under Option C, cost which the Project Manager decides was incurred only because the Contractor failed to give a required early warning is Disallowed Cost. This payment consequence is distinct from the compensation event assessment. It requires a connection between the failure and the cost, rather than making every cost associated with the matter disallowed.

Unexpected ground conditions on Ironbark

The fictional Ironbark Recycled Water Scheme is a regional Australian utility project using ECC Option C. A pipeline, pumping station and balancing tank will supply an industrial estate from an existing treatment plant, which remains operational during construction and connection.

Suppose the Contractor encounters buried concrete while excavating a section of the pipeline trench. The site team does not yet know its full extent, what it forms part of or how difficult it will be to remove. It does know that the obstruction could increase cost and delay the work, so the Contractor gives an early warning.

The initial response

The Project Manager enters the matter in the Early Warning Register. The site team speaks promptly with the planner and relevant specialists, involving the Project Manager where a contractual decision is needed. They arrange trial pits to establish the extent of the concrete, consider suitable breaking Equipment and identify work which can proceed elsewhere. They do not wait for the next scheduled meeting to begin those enquiries.

The register records the actions and who will take them. A focused early warning meeting can be held with the relevant people where needed, and the regular meeting can examine the response and any unresolved effects. The outcome must reach the people carrying out the work, with any required contractual communications issued separately.

Notifying the compensation event

At the same time, the Contractor reviews the available Site Information and the other information relevant under clause 60.2. Absence of the concrete from a drawing would not, by itself, establish a compensation event. The test concerns conditions which an experienced contractor would have judged at the Contract Date to have such a small chance of occurring that it would have been unreasonable to allow for them.

For this example, the available information gives the Contractor grounds to believe that clause 60.1(12) applies. It notifies the compensation event while the trial pits and practical discussions continue, explaining what it has encountered and why it believes the event qualifies. The notice does not wait for confirmation of the full extent or a completed quotation.

The trial pits subsequently reveal substantial buried foundations. The Project Manager considers the notification and available information, agrees that it is a compensation event and instructs a quotation. Investigating and managing the conditions has continued throughout; neither activity depended on that agreement.

Continuing the work

The team arranges specialist Equipment and resequences the excavation, with actions reviewed through the early warning process. If a response requires a change to the Scope, the Project Manager issues the necessary instruction. The register records the response but does not itself change the Scope.

The initial investigation suggested that the obstruction could delay planned Completion by ten working days. With specialist breaking Equipment and excavation proceeding from the other end of the trench, the forecast delay is reduced to four working days.

The Contractor’s quotation assesses the additional cost and delay after allowing for that response. Under clause 60.1(12), only the difference between the conditions encountered and those for which it would have been reasonable to allow is taken into account. The cost of ordinary excavation and the effects of unrelated problems remain outside this assessment.

Assume the additional Defined Cost is assessed at AUD $36,000. With an illustrative fee percentage of 10%, the proposed increase to the Prices is AUD $39,600. These are the net effects of the event, not the entire cost of excavating that section.

The programme assessment, using the Accepted Programme current at the dividing date and taking account of intervening progress and events, shows that the compensation event delays planned Completion by four working days. In this example, the proposed change to the Completion Date is therefore also four working days. The change follows from the programme assessment, not simply from the number of days spent removing concrete.

When the Project Manager accepts the quotation, the compensation event is implemented. The Prices increase by AUD $39,600 and the Completion Date moves by four working days. Under Ironbark’s Option C, the increase adjusts the target. It is not added to the next payment as a separate sum: payment continues under its own provisions, including eligible Defined Cost and the Fee. The early warning discussions helped reduce the disruption; assessment and implementation established the contractual changes.

The early warning matter remains open if further action could still reduce its effects. Settling the time and cost assessment is no reason to stop managing the work.

The contractual provisions discussed here are those of the June 2017 NEC4 ECC incorporating the January 2023 amendments. The signed contract’s selected options, Contract Data and amendments must be checked.