What does the NEC publisher guidance actually say?
NEC Contracts' article dated 2 April 2020 warns against relying on early warnings or poorly worded meeting minutes to demonstrate compensation event notification compliance. It discusses separate notifications under the applicable contract. This is publisher guidance for NEC contract administration, not a determination about a particular notice or every amended NEC form.
Pre-bid Review is independent and is not affiliated with NEC Contracts. This page is not legal advice. Check the exact contract form, edition, amendments and communication requirements with the responsible contracts professional and legal adviser.
Sources: NEC Contracts: Notifying Compensation Events, 2 April 2020
How should the pre-bid register keep the processes separate?
Record the actual source requirement in each row. Link related events without merging their statuses. Do not fill a deadline from a generic online summary or assume that the same recipient or system applies to both communications.
| Field | Early-warning row | Compensation-event row |
|---|---|---|
| Purpose | Risk or matter identified under actual contract | Event notification purpose under actual contract |
| Source | Applicable form, revision and amendments | Applicable notification requirement and amendments |
| Responsible role | Who prepares and authorises this communication | Who assesses and authorises the required notice |
| Trigger and timing | Actual requirement for this process | Separate actual trigger and time basis |
| Route | Approved recipient and communication route | Check whether the route is the same or different |
| Evidence | Issued record and actual response | Separate notification and delivery evidence |
| Status | Own current disposition | Never copied automatically from warning status |
What can an acknowledged warning leave unresolved?
Illustrative example. A fictional EPC team records warning EW-DEMO about delayed access. The recipient acknowledges it. The commercial register still has an open question about whether a separate event notification is required under the actual contract.
The warning acknowledgment is evidence that the warning was received, not an automatic answer to the separate notification question. The qualified reviewer assesses the contract requirement and records the authorised next action. The example does not determine entitlement, acceptance, time-bar compliance or an amount payable.
Preserve both references if a separate notification is issued. The common event reference helps a reviewer find the relationship while the two process records show what was actually communicated.
What should the bidder resolve before pricing the administration scope?
Identify the roles, system access and workflow needed for each required process. Treat a missing notification route, undefined owner or conflicting amended requirement as a clarification for authorised review. Separate the effort to manage a warning from the effort to prepare an event assessment.
Keep all contractual timing questions open until the actual source and qualified interpretation are recorded. This worksheet supplies no universal notice period and cannot validate a notice. Update the register when the governing contract package changes, retaining the previous basis.
Common questions
What else should the bid team know?
Does acknowledging a warning accept a compensation event?
Do not infer that. Record the actual event process and response separately.
May one event link to several communication records?
Yes. Preserve each record's purpose and status.
Does this article validate a contractual notice?
No. That requires the actual contract and qualified advice.
Primary sources
- Notifying Compensation Events, 2 April 2020NEC Contracts