NEC4 eight-week time bar: near-miss patterns

What you need to know

The standard trigger is becoming aware that the event happened.
Check the Project Manager notification exception.
Informal requests do not automatically establish a valid compensation event.
Weather events require the contractual measurement test.

A site record can help establish what happened and when, but it does not automatically notify a compensation event. The commercial team needs a process that turns relevant information into the correct contractual action.

Understand the rule and its exception

Standard NEC4 ECC clause 61.3 includes an eight-week time bar measured from the Contractor becoming aware that the event has happened. Do not replace that wording with “should reasonably have become aware” unless an applicable amendment makes that change. Awareness of the event and later recognition of its commercial significance are not necessarily the same date.

The standard exception concerns events the Project Manager should have notified. Check that obligation and the event’s facts rather than assume every communication from the Client removes the time bar. Different NEC forms and amendments may use different rules.

Where the time bar applies, late notification prevents changes to the Prices, Completion Date or Key Dates for that event. An early warning or a diary entry does not automatically substitute for the required compensation-event notification.

Pattern one: an informal request to change the work

In this illustrative scenario, a site team acts on a telephone request from someone described as the Project Manager’s assistant. The written instruction never arrives and the additional work appears in a later cost review.

First establish authority, what was requested, whether it changes Scope and whether a contractual instruction was given. An informal conversation is not automatically a valid instruction or compensation event. Equally, it does not automatically become time-barred merely because it was verbal: the facts and notification duties still need analysis.

Record the conversation promptly and seek the required instruction or confirmation through the contractual communication system. Escalate the potential event to the commercial team. A record helps evidence the conversation; it does not by itself confer authority or satisfy every communication requirement.

Pattern two: weather records without a contractual measurement check

A diary records several rain-affected pours. The team notices lost hours but has not checked the weather measurements specified in Contract Data.

Standard ECC clause 60.1(13) uses specified measurements within a calendar month and the contract’s statistical test. Repeated wet days or a programme delay alone do not establish the event. Use the relevant measurement location and historical comparison, then assess the effect under the contract.

Do not start a separate eight-week clock automatically on each wet day or claim that every daily entry proves a qualifying monthly weather event. Record daily effects while arranging a timely review of the completed measurement period and the date of awareness of the qualifying event.

Pattern three: developing design and Scope

Small design developments may accumulate before a cost review identifies extra expenditure. Determine which changes, if any, alter the contractual Scope and who is responsible for them. A difference from a tender assumption is not automatically a compensation event.

Separate individual events, instructions, dates and effects. Apply the appropriate notification obligation and time-bar exception to each. Do not assume that all additional expenditure is recoverable, or that all informal changes share one deadline.

Make the next action visible

Record facts, dates, people and source communications.
Identify the possible event and relevant contractual provision.
Check authority, communication requirements and any amendment.
Record the awareness date and the basis for it.
Assign notification and response actions to a named person.
Track early warnings separately from compensation events.

Software can help organise records and flag matters for review. It cannot guarantee that every event is detected, that a notification is valid or that entitlement exists. Human review remains necessary for the contract and facts.

See Gather’s time-bar guide and weather-event guide. These scenarios illustrate administrative risks; they are not reported customer outcomes.