The compensation event notification (CEN): getting the notice right

A compensation event only enters the contract machinery when it is properly notified. Get that notice right — accurate, separate and on time — and the Prices, Completion Date and Key Dates can be put back where they belong. Get it wrong, or get it late, and the entitlement can quietly disappear.

The compensation event notification, almost universally shortened to the CEN, is the formal notice that starts the compensation event clock under the NEC3 and NEC4 Engineering and Construction Contract (ECC). It is the single most important administrative act in the whole change process: without a CEN, there is no event to assess, no quotation to price, and — eventually — no adjustment to the Prices or the dates. This article sets out who notifies, when, the eight-week time bar that catches the unwary, how the Project Manager must reply, and how the CEN differs from the two things South African teams most often confuse it with: the early warning and the quotation.

What the CEN actually is

A compensation event is an event, listed in clause 60.1 (and a few others), that is at the Client's or Project Manager's risk and which, if it occurs, entitles the Contractor to have the Prices, the Completion Date and any affected Key Dates assessed afresh. The CEN is the communication that formally puts such an event into the assessment process. It is not a request, not a claim letter, and not a negotiation — it is a contractual notice that says, in effect, “this thing has happened, and it is a compensation event.”

Because everything that follows — the Project Manager's reply, the instruction to quote, the quotation itself, and the eventual implementation — hangs off the CEN, the notice must be treated with care. It is given in a form that can be read, copied and recorded, communicated separately from any other notice, and it identifies the event clearly so there is no argument later about what was notified or when.

Who notifies — and why it depends on the event

NEC does not give the job of notifying to one party. It splits it according to where the event comes from, and this is the first thing to get right.

Where a compensation event arises from the Project Manager's or the Supervisor's own action — most obviously an instruction changing the Scope (the Works Information under NEC3), but also instructions to stop or not start work, changes to a Key Date, and similar acts — the Project Manager notifies the event to the Contractor at the time of giving the instruction or making the decision, and at the same time instructs the Contractor to submit a quotation. The Contractor does not need to lodge its own notice for these; the act that caused them carries the notification with it.

For every other compensation event — the ones that are not signalled by a Project Manager or Supervisor action — it is the Contractor who notifies. Think of physical conditions an experienced contractor would have judged to have a small chance of occurring, weather measured against the contract's thresholds, the Client failing to give access by the access date, or the Supervisor failing to carry out a test in time. These do not announce themselves through an instruction, so the burden sits with the Contractor to raise the CEN.

The eight-week time bar (clause 61.3)

This is the clause that costs Contractors money, and it deserves to be understood precisely. Under clause 61.3, the Contractor must notify a compensation event within eight weeks of becoming aware of the event. Miss that window and the consequence is severe: the Contractor is not entitled to a change in the Prices, the Completion Date or the Key Dates in respect of that event. The entitlement is not merely delayed — it is lost.

The eight-week time bar does not punish the event; it punishes the silence. An event that genuinely entitled the Contractor to time and money can be worth nothing at all simply because no one served the notice in time.

There is, however, one crucial carve-out — and it is worded differently in the two editions, so SA teams should know which contract they are on. Under NEC3 (clause 61.3) the time bar does not apply where the Project Manager should have notified the event to the Contractor but did not (the NEC3 carve-out names the Project Manager only). NEC4 reworded clause 61.3: the time bar does not apply where the event arises from the Project Manager or the Supervisor giving an instruction or notification, issuing a certificate, or changing an earlier decision. The underlying logic is the same in both — the contract will not let a party benefit from its own omission — but the NEC4 text is broader and more precisely drawn. Outside that carve-out, eight weeks is eight weeks, and it runs from awareness — not from the event itself, and not from when the consequences became painful.

The Project Manager's reply (clause 61.4)

Once a CEN lands — whether raised by the Contractor or self-notified through an instruction — the ball is in the Project Manager's court. Under clause 61.4, the Project Manager must reply within one week of the Contractor's notification (or a longer period if the Contractor agrees to it). In that reply the Project Manager decides whether the notified event is in fact a compensation event, and takes one of two routes:

• It is a compensation event — the Project Manager instructs the Contractor to submit a quotation, and the assessment process begins.
• It is not a compensation event — the Project Manager notifies the Contractor that the Prices, the Completion Date and the Key Dates are not to be changed, and must give the reasons. The decision is, broadly, that the event does not arise from one of the listed causes, has not happened, or has no effect on cost or time.

Either way, the Contractor receives a reasoned answer within a tight window, which keeps the change conversation moving rather than letting it fester unanswered — exactly the discipline NEC is built around.

What NEC4 added: deemed acceptance of the CEN

Under NEC3, if the Project Manager simply ignored a Contractor's CEN, the Contractor's main remedy was to escalate or dispute — the silence itself did not decide anything. NEC4 closed that gap with a deemed acceptance mechanism built into clause 61.4, mirroring the deemed-acceptance approach NEC4 introduced elsewhere.

The mechanism works in two steps. First, if the Project Manager does not reply to the Contractor's notification within the time allowed, the Contractor may notify the Project Manager of that failure. Second, if the Project Manager then still fails to reply within two weeks of that notification of failure, the Contractor's original notification is treated as accepted — the event is deemed to be a compensation event, and the process moves on to quotation. In short, a Project Manager who stays silent twice loses the argument by default.

1. The Contractor notifies a compensation event under clause 61.3 (within eight weeks of becoming aware).
2. The Project Manager fails to reply within the one-week period of clause 61.4.
3. The Contractor notifies the Project Manager of that failure to reply.
4. If the Project Manager still does not reply within two weeks, the event is treated as a compensation event (NEC4 only).

This is one of the clearest practical reasons SA teams running NEC4 should not let CENs sit unanswered: silence is no longer safe for the Project Manager, and a well-organised Contractor will use the two-step process to convert an ignored notice into an accepted one.

CEN versus early warning versus quotation

Three communications get muddled on site more than any others, and conflating them undermines the whole system. The distinction is worth stating bluntly.

• Early warning — this is about managing the risk. An early warning is given as soon as either party becomes aware of a matter that could increase the Prices, delay Completion or a Key Date, or impair performance. Its purpose is to get the matter onto the table early so the parties can meet and decide what to do about it. An early warning is not a CEN and does not, on its own, start the compensation event clock or create entitlement.
• Compensation event notification (CEN) — this is about claiming the time and money consequence. The CEN formally asserts that an event is a compensation event and pulls it into the assessment process under clauses 61.3 and 61.4.
• Quotation — this comes after the Project Manager has agreed (or it has been deemed) that the event is a compensation event and has instructed one. The quotation is the priced and programmed assessment of the event's effect; it is the answer, not the notice.

A practical trap follows from this: raising an early warning, however diligently, does not discharge the obligation to notify a compensation event. The two run on different tracks. A Contractor that early-warns a physical conditions problem but never serves a CEN can still be time-barred under clause 61.3. Treat the early warning as risk management and the CEN as the entitlement notice, and serve both where both are due.

Getting the notice right

The recurring theme is discipline: notices that are accurate (clearly identifying the event and the clause it falls under), separate (one CEN per event), and timely (well inside the eight-week window for Contractor-notified events, and replied to within one week by the Project Manager). On a South African contract where the same team may be juggling dozens of instructions, weather records and access issues across several work fronts, the failure mode is rarely a single dramatic mistake — it is the steady accumulation of events that were noticed but never formally notified, until the eight-week bar has quietly closed on them one by one.

Doing it well protects entitlement on the Contractor side and protects the Project Manager from deemed acceptance on the other. A CEN register that records what was notified, by whom, on what date, and what reply was given turns the compensation event process from a source of disputes into a predictable, auditable workflow.