NEC4 compensation event time bar and the CE clock: clauses 61 and 62 explained
- Feb 25
- 19 min read
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
There is a category of contractual provision in NEC4 that operates differently from everything else in the contract. Most NEC provisions are commercial mechanisms with shades of grey: programmes can be more or less compliant, quotations can be more or less complete, mitigation can be more or less reasonable. The project manager's response to any of these is judgement-based, with reasons that can be tested and challenged.
The eight-week time bar in clause 61.3 is not like that. It is binary. The notification is either inside the eight weeks or outside it. If outside, the contractor's right to a change in the prices and the completion date for that compensation event disappears entirely. There is no judgement about how late, no proportionate reduction, no consideration of mitigating circumstances. The entitlement is gone, with one narrow exception that contractors rarely succeed in invoking.
This makes the eight-week time bar the most asymmetric provision in the entire NEC contract. Almost every other provision creates a spectrum of outcomes. The time bar creates a cliff. On one side of the cliff, the contractor's entitlement survives and the compensation event proceeds through assessment. On the other side, the entitlement is forfeit and the contractor carries the cost and time impact themselves.
This article explains the eight-week time bar and the wider clock that runs from notification through to implementation under clauses 61 and 62. It explains why the time bar is structurally different from other NEC provisions, what the narrow exception in clause 61.3 actually requires, and how contractors should organise their commercial administration around the asymmetric risk the provision creates. It is written for contractors who want to understand the time bar as a structural feature of the contract rather than as a deadline to manage.
Why the eight-week time bar is structurally different
Clause 61.3 of NEC4 ECC requires the contractor to notify a compensation event to the project manager within eight weeks of becoming aware of the event. If the contractor does not notify within eight weeks, the contractor is not entitled to a change in the prices, the completion date, or a key date as a result of the event, unless the project manager should have notified the event to the contractor but did not.
The provision contains four elements that together produce its asymmetric effect. First, the trigger is the contractor's awareness of the event, not the occurrence of the event. Awareness is a factual matter that the contractor can usually establish but the project manager can dispute. Second, the period is fixed at eight weeks, with no discretion for either party to extend it. Third, the consequence of late notification is forfeiture of the entitlement, not delay or reduction. Fourth, the only exception applies when the project manager should have notified but did not, which transfers the burden onto an event the contractor was not actually responsible for notifying in the first place.
Compare this to almost any other NEC provision. The four-week period for programme submissions has a deemed acceptance backstop. The three-week period for quotation submissions has an extension mechanism under clause 62.5. The two-week period for project manager response to programmes triggers a notification process and ultimately deemed acceptance. Each of these provisions has flexibility built into it. The eight-week time bar does not.
The asymmetry matters commercially. A contractor who misses a programme submission deadline by two weeks loses no entitlement; the programme is submitted late and the project manager reviews it. A contractor who misses an eight-week notification deadline by two days loses the entire entitlement on that compensation event. The same level of administrative slip produces wildly different commercial consequences depending on which deadline was missed.
This is not an accident of drafting. The eight-week time bar is one of the most discussed provisions in NEC commentary precisely because the drafters chose to make it absolute. The intention is to ensure compensation events are managed prospectively, while the facts are still fresh, the parties can act on the assessment, and the project remains controllable. A contractual mechanism with extension provisions and proportionate consequences would, the drafters reasoned, allow events to drift. Making the consequence absolute forces both parties to engage with events early.
The contractor who understands this asymmetry organises their commercial administration around the eight-week time bar with a level of discipline that other deadlines do not require. Missing other deadlines produces friction, additional work, or weaker positions. Missing the eight-week deadline produces total entitlement loss on that event. The two are not equivalent risks and should not be treated as such.
What "becoming aware" actually means
The clock does not start when the event occurs. It starts when the contractor becomes aware of the event. This distinction is important because the timing of awareness can differ significantly from the timing of the event, particularly for events that develop gradually or that affect parts of the works the contractor is not actively engaged with.
NEC's own guidance and the case law that has developed around clause 61.3 treat awareness as a factual question. The contractor became aware when a person within the contractor's organisation, with relevant authority and responsibility, knew or should have known that the event had occurred. This standard is generally interpreted to include knowledge held by site management, project management, and commercial leadership, not just the individual who first encountered the event physically.
The consequence is that contractors cannot rely on the most senior person in the organisation only becoming aware late to extend the eight-week period. If the site agent knew about the event on day one, the eight weeks runs from day one even if the commercial team did not learn about it until week six. This is why contractors who have a disciplined internal early warning and event identification process generally fare better on time bar disputes than those who rely on events being escalated only when they reach a particular threshold.
Documenting awareness is one of the most important administrative tasks on any NEC project. The moment an event surfaces, the contractor's internal record should capture the date the event was first identified, the person who identified it, the basis on which it was identified (instruction, drawing change, site condition, RFI response, third-party communication), and the contemporaneous documentation that supports the awareness date. This documentation is not for show. It is the evidence that determines whether the eight weeks has been met if the matter is later disputed.
The contractor who reaches week seven on an event without having properly documented awareness is in a difficult position. The notification can still be issued, but if the project manager later argues awareness occurred earlier than the contractor claims, the contractor's evidence base for the claimed awareness date may be weaker than it should be. This is not a hypothetical risk. Disputes about awareness dates are among the most common time bar arguments in NEC adjudication.
The Northern Ireland Housing Executive cases
The most significant judicial guidance on clause 61.3 came from two Northern Ireland cases involving the same parties: Northern Ireland Housing Executive v Healthy Buildings (Ireland) Ltd. The first instance decision in 2013 ([2013] NIQB 124) and the Court of Appeal decision in 2014 ([2014] NICA 27) addressed several aspects of how the eight-week time bar should be applied in practice.
The cases involved an NEC3 Professional Services Contract rather than the NEC4 Engineering and Construction Contract. The clause numbering and some specific wording differs between the contracts. The principles, however, apply across the NEC suite because the time bar mechanism is constructed similarly in each contract.
Two principles emerged from the Healthy Buildings decisions that contractors should understand.
First, the court treated instruction notices and compensation event notices as separate documents serving separate functions. An instruction is a contractual mechanism through which the project manager instructs work or changes. A compensation event notice is a contractual mechanism through which the contractor or the project manager notifies that an event has occurred which entitles the contractor to compensation. The two are not the same thing. An email containing an instruction, even one that clearly creates a change to the work, is not automatically a compensation event notice. The contractor cannot assume that the project manager's instruction itself triggers the contract's CE assessment process. The contractor must issue a separate notification under clause 61.3 unless the project manager has issued a notification of their own.
Second, the court engaged with the "should have notified" exception in clause 61.3, which provides that the time bar does not apply if the project manager should have notified the event to the contractor but did not. The exception is narrow and the burden of demonstrating it falls on the contractor. The exception protects contractors against project manager failures to notify clear-cut events that the contract requires the project manager to notify, but it does not give contractors a general escape route from the eight-week time bar.
The practical lesson from these cases is procedural. Contractors should issue compensation event notifications as separate, formal documents, clearly identified as such, with their own reference numbers, the relevant facts, and the supporting evidence. Notifications buried within general correspondence or assumed to be implicit in instructions are vulnerable to challenge. The contractor who treats clause 61.3 as a mechanism requiring its own discrete document protects against the procedural ambiguities the Healthy Buildings cases identified.
The "should have notified" exception and why contractors rarely win on it
Clause 61.3 contains one exception to the eight-week time bar: the bar does not apply if the project manager should have notified the event to the contractor but did not. This exception is the source of significant contractor optimism that is not well supported by either the contract wording or the case law.
The exception covers events that the contract requires the project manager to notify. Several compensation events under clause 60.1 are events that either party can notify, but some are events where the project manager is the natural notifying party because the event arises from a project manager instruction, an employer obligation, or a contract administration function. If the project manager fails to notify such an event, and the contractor does not notify it within eight weeks of becoming aware, the contractor can argue the time bar should not apply because the project manager should have notified.
In practice, this exception is genuinely available in a narrow band of circumstances. Events that arise from clear project manager instructions, where the instruction itself constitutes notification or where the project manager acknowledged the event would be a compensation event, can sometimes succeed on the exception. Events that arise from less clear circumstances, where the project manager's notification obligation is debatable, generally do not succeed.
The reason contractors rarely win on this exception is that the contract puts the burden on the contractor to demonstrate that the project manager should have notified. This is a positive case the contractor must build, with evidence about the contract obligations on the project manager, the facts of the event, and the project manager's awareness. The project manager's defence is usually straightforward: "I did not consider that I had a duty to notify because the event was not clearly within the events I am required to notify, and the contractor was the better-placed party to identify and notify it."
Contractors should not rely on the "should have notified" exception as a backstop for their own time bar discipline. The exception exists, but it is not a substitute for the contractor's primary obligation to notify within eight weeks. The contractor's commercial position is dramatically stronger when notification is timely and the exception is not relied upon.
The contractor who builds a project administration system that depends on the exception covering missed notifications has misunderstood the architecture of the time bar. The exception is a narrow protection for circumstances where the project manager's failure to notify is clear. It is not a fallback for contractor administrative drift.
Clause 62: the post-notification clock
Once a compensation event has been notified and accepted (or deemed accepted) as a compensation event, clause 62 controls the quotation and decision cycle. This is a different clock from the eight-week notification time bar, but it is part of the same overall sequence and contractors should understand it as a continuous process rather than as separate provisions.
Under clause 62.1, the project manager instructs the contractor to submit a quotation. The contractor has three weeks from that instruction to submit, unless an extension has been agreed under clause 62.5. Under clause 62.3, the project manager has the period for reply stated in the contract data (typically two weeks) to reply to the quotation. The reply can be: acceptance of the quotation, an instruction for a revised quotation under clause 62.4, a notification that the project manager will make their own assessment under clause 64, or notification that the proposed event is not a compensation event.
If the project manager fails to reply within the period for reply, clause 62.6 provides a mechanism for the contractor to notify the failure. If the project manager continues to fail to reply for two weeks after the contractor's notification, the quotation is treated as accepted and is then implemented. This deemed acceptance mechanism for compensation event quotations was added in NEC4 and was not present in NEC3.
The clause 62 clock matters because the same patterns of administrative drift that produce time bar problems on clause 61.3 also produce drift on clause 62. Quotations submitted late create grounds for clause 64 project manager assessment. Project manager replies that drift past the reply deadline create grounds for clause 62.6 notification. The article on NEC4 clause 64 covers the project manager assessment mechanism in detail.
The cumulative effect of running clauses 61 and 62 well is that compensation events flow through the contract cleanly: notified within eight weeks, quoted within three weeks of instruction, replied to within two weeks of submission, and either accepted or moved to revision or PM assessment with appropriate notice. The cumulative effect of running them poorly is a register of drifting events, weakened entitlement, and disputes about administrative process that distract from the substantive merit of each event.
The CE clock as an integrated tracker
The disciplines that prevent time bar problems and quotation drift cannot be operated through informal email-based tracking. The volume of dates, references, and decisions across a multi-year NEC project with twenty or more compensation events overwhelms any system that relies on individuals remembering deadlines.
The standard solution is what experienced NEC administrators call a CE clock: an integrated tracker that captures every date, reference, and decision for every compensation event from notification through to implementation. The CE clock is not just a register of compensation events. It is a real-time view of where each event sits in the contract's process, what the next deadline is, and what action is required from each party.
A properly constructed CE clock captures, for each event: the awareness date and the basis for the awareness date, the notification date and reference, the project manager's response (if any) and the date, the instruction to quote and the quotation due date, the quotation submission date and reference, any extension agreed under clause 62.5, the project manager's reply due date and the actual reply date, any failure to reply notice issued under clause 62.6 and the resulting deemed acceptance date, the implementation date and the final agreed value, and any links to programme revisions affected.
The CE clock is reviewed weekly. Any event approaching a deadline is flagged. Any event where a deadline has passed without action is escalated. The clock is the single source of truth for the contract's procedural status on compensation events.
For contractors with mature commercial administration, the CE clock is integrated into the wider project controls system. Programme revisions reference the CE clock for events that affect the schedule. Cost reports reference the clock for events that affect the cost forecast. The clock is the connective tissue between the contract's procedural mechanisms and the commercial position of the project. The article on NEC clause 32 programme revision covers the revision discipline that should reference the CE clock.
For contractors without that infrastructure, building a CE clock is one of the highest-return administrative investments available. A simple spreadsheet, properly maintained, captures most of the value. The cost of building it is hours. The cost of operating without it can run to entire compensation events lost to time bar.
What good notification looks like
The notification under clause 61.3 is a contractual document. Its purpose is to establish, for the contract record, that the contractor has notified the project manager of a compensation event within the required time period. The notification needs to be capable of standing on its own as evidence of the contractor's compliance with clause 61.3.
A good notification is brief but complete. It identifies itself clearly as a compensation event notification under clause 61.3, with its own reference number. It states the event in one or two sentences, with sufficient detail to identify what is being notified. It states the date of the event. It states the date the contractor became aware of the event. It identifies the supporting documentation: the instruction, drawing, RFI, site record, or other evidence that gave rise to the awareness. It requests the project manager's response: confirmation of the event as a compensation event, instruction to submit a quotation, or notification of the project manager's intended approach.
A good notification is not a quotation. The contractor is not required to have priced the event before notifying it. The contract's design is that notification happens early, while the facts are fresh and the assessment can be prospective, with the quotation following later. Contractors who delay notification while they price the event are misunderstanding the contract's architecture and exposing themselves to time bar.
A good notification is issued separately from other correspondence. It is not buried in an email chain about other matters. It is not an attachment to a progress report. It is its own document, clearly identified, with its own reference and its own filing in the project's contract correspondence record. The Healthy Buildings cases reinforce this discipline: the contract treats notifications as separate documents serving separate functions, and the contractor's position is significantly stronger when notifications are issued accordingly.
Notifications should be acknowledged. The contractor should issue the notification in a way that produces a clear acknowledgement of receipt, whether through CEMAR or another formal communication system, or through email with a delivery confirmation. The acknowledgement is part of the evidential record showing that the notification was received within the eight-week period.
What good quotation administration looks like
Once notified and accepted as a compensation event, the quotation under clause 62 is the substantive content of the contractor's case for change to the prices and the completion date. The quotation is what the project manager either accepts, instructs revised, or proceeds to assess themselves under clause 64.
A good quotation is decision-ready. It is structured to allow the project manager to read it, understand the basis of the assessment, identify any specific points of disagreement, and either accept or instruct revisions on a defined basis. A poor quotation requires the project manager to reconstruct the analysis themselves, which produces delay and creates grounds for clause 64 to be invoked.
The structural elements of a decision-ready quotation are covered in detail in the article on how to structure a time impact assessment under NEC4. At the highest level, the quotation should contain: a cover page identifying the event, the dividing date, and the decision requested; a numbered list of assumptions linked to evidence; a cost build-up using the schedule of cost components or the short schedule of cost components depending on the option; a time impact assessment showing the alterations to the accepted programme; an evidence index referencing the supporting documentation.
The submission should be formal. It should be issued under clause 13, with a clear submission date that triggers the project manager's reply period. It should not be a draft attached to an email asking for informal feedback. The contract's clock starts on formal submission, and contractors who use informal submissions in the hope of avoiding the formal review timeline are usually creating procedural ambiguity that ends up working against them.
The quotation should be consistent across its time and cost elements. If the time impact assessment shows six weeks of additional site activity, the cost assessment should include the cost of those six weeks of preliminaries and time-related plant. If the cost assessment includes resource peaks for additional crews, the time impact assessment should show the activities those crews are working on. Inconsistency between the two halves of the quotation is one of the fastest ways to lose credibility with the project manager.
Recovering from time bar exposure
Contractors sometimes find themselves with compensation events that should have been notified but were not, where the eight weeks has either passed or is about to pass. The instinct in these situations is often to notify late and hope the project manager does not invoke the time bar. This instinct is generally wrong.
The time bar is binary. Late notification is procedurally weak regardless of how late, but it does not eliminate every option the contractor has. The options depend on the specific facts.
If the eight weeks has clearly passed and there is no credible argument that the project manager should have notified the event, the entitlement is forfeit on that specific event. The contractor's options are limited to factual disputes about the awareness date. If the contractor can credibly argue that awareness occurred more recently than the project manager claims (because the relevant decision-maker did not become aware until later, for example), the eight-week period may not have actually expired. This is a factual argument that depends on documentation. Contractors who have not maintained reliable internal awareness records have weak positions on this.
If the eight weeks is about to pass and notification has not yet been issued, the contractor should issue the notification immediately, even if the analysis of the event is incomplete. A notification issued on day fifty-five with limited supporting information is better than a notification issued on day fifty-seven with full information. The notification can be expanded in subsequent correspondence. The notification cannot be back-dated.
If the contractor has an argument that the project manager should have notified, the argument should be made early and clearly. The "should have notified" exception is procedurally available but evidentially demanding. Contractors who raise the argument only after the project manager has invoked the time bar are in a weaker position than those who flag the argument in their notification or in early correspondence.
For contractors with multiple events potentially at risk of time bar, specialist NEC programme support provides systematic review and remediation. The cost of identifying and properly notifying borderline events is small. The cost of losing entitlement on those events through forfeiture is significant.
The argument in short
The eight-week time bar in NEC4 clause 61.3 is the most asymmetric provision in the entire contract. Almost every other provision creates a spectrum of outcomes through judgement, extension mechanisms, or proportionate consequences. The time bar creates a cliff. Notifications inside eight weeks preserve entitlement. Notifications outside eight weeks forfeit it entirely, with one narrow exception that contractors rarely succeed in invoking.
This asymmetry has two consequences for how contractors should organise their commercial administration.
First, the eight-week time bar deserves a level of administrative discipline that other NEC deadlines do not require. The consequences of missing other deadlines are recoverable. The consequences of missing the eight-week time bar are not. A CE clock that tracks awareness dates and notification deadlines as the highest-priority operational item, with weekly review and clear escalation triggers, is the minimum infrastructure for managing this risk.
Second, the contractor's response to the time bar should be structural rather than tactical. Treating each potentially time-barred event as a one-off problem to manage produces drift across the project. Treating the time bar as a structural feature of the contract that requires consistent process discipline produces a project where time bar issues rarely arise. The difference between the two approaches is not effort but organisation.
The Healthy Buildings cases established that compensation event notifications must be treated as separate, formal documents distinct from instruction notices and general correspondence. The "should have notified" exception is genuinely available in a narrow band of circumstances but is not a substitute for the contractor's primary obligation. The clause 62 quotation cycle continues the procedural discipline of clause 61 and produces its own opportunities for drift if not managed actively.
For contractors who maintain a CE clock, issue notifications as separate formal documents, build decision-ready quotations, and review the procedural status of every event weekly, the time bar is rarely a source of entitlement loss. For contractors who manage compensation events through informal correspondence and intermittent attention, the time bar is consistently the source of avoidable losses across the life of the project. The structural difference between these two approaches is small. The commercial difference is substantial.
FAQ
What is the NEC4 compensation event time bar?
The eight-week notification deadline in clause 61.3. The contractor must notify a compensation event to the project manager within eight weeks of becoming aware of the event. If the contractor does not notify within eight weeks, the contractor loses the right to a change in the prices, the completion date, or any key date for that event, with one narrow exception covering events the project manager should have notified but did not.
When does the eight-week clock start?
When the contractor becomes aware of the event, not when the event occurs. Awareness is a factual matter assessed against the knowledge held by relevant persons within the contractor's organisation, including site management, project management, and commercial leadership. Contractors cannot extend the eight weeks by relying on the most senior person only becoming aware later if site staff knew earlier.
What is the "should have notified" exception in clause 61.3?
The exception applies where the project manager should have notified the event to the contractor but did not. The exception is narrow. It covers events the contract requires the project manager to notify, typically events arising from clear project manager instructions or employer obligations. The contractor bears the burden of demonstrating that the project manager's notification obligation existed and was breached. The exception is genuinely available in some circumstances but contractors should not rely on it as a backstop for their own time bar discipline.
What happens if I miss the eight-week deadline?
The right to a change in the prices, the completion date, and any key date is forfeit on that compensation event. The forfeiture is binary, not proportionate. Late notification produces no recovery of entitlement, even by a small margin. The contractor's options after the deadline has passed are limited to factual disputes about the awareness date or arguments that the project manager should have notified.
Is the eight-week time bar in NEC3 the same as NEC4?
The eight-week period and the basic mechanism are the same. NEC4 clarified some elements of the wording but did not alter the structure of the time bar or the consequences of missing it. The Healthy Buildings cases, decided under NEC3, remain relevant guidance on the principles applied to NEC4 time bar disputes.
What is the deemed acceptance mechanism for quotations under NEC4?
Clause 62.6 of NEC4 provides that if the project manager fails to reply to a quotation within the period for reply, the contractor can issue a notification of the failure. If the project manager fails to reply within two weeks of the notification, the quotation is treated as accepted and is then implemented. This mechanism did not exist in NEC3 and is one of the significant procedural changes contractors should use actively.
How long does the contractor have to submit a quotation under clause 62?
Three weeks from the project manager's instruction to submit a quotation, unless an extension has been agreed under clause 62.5. The extension must be agreed before the original deadline expires, not after. If the contractor submits late without an agreed extension, the project manager can invoke clause 64 and assess the event themselves.
What records should the contractor keep to support time bar compliance?
For each event: the awareness date and the person who first became aware, the basis on which awareness arose (instruction, drawing, RFI, site record, or other evidence), the notification date and reference, contemporaneous correspondence about the event, and any acknowledgements of the notification's receipt. These records should be filed together as a single chronological record for each event, not scattered across general project correspondence. The article on NEC clause 31 programme acceptance covers the broader documentation discipline that supports this.
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.
Need a CE clock and time bar discipline established on a live project?
If compensation events are accumulating without timely notification, if the eight-week deadline is being approached without proper internal tracking, or if quotations are drifting past response deadlines without follow-up notices being issued, specialist NEC programme support builds the procedural infrastructure that protects entitlement and keeps the contract running on the contract's own clock.
