{ "query": "NEC4 compensation event assessment without early warning sanction rules", "raw_results": [ { "url": "https://www.necplanningsolutions.co.uk/post/7-common-pitfalls-when-managing-compensation-events-in-nec4-as-a-contractor", "title": "7 Common Pitfalls When Managing NEC4 Compensation Events as ...", "content": "Why it hurts under NEC4\n\nIf the contractor failed to give an early warning of an event that becomes a compensation event, the PM can state that when instructing a quotation (clause 61.5), and the CE is assessed as if the early warning had been given (clause 63.7). In practice, that can reduce the CE assessment.\n\nAlso, NEC guidance is clear that compensation events are assessed assuming the contractor acts promptly and competently (63.7). Waiting for agreement before acting can backfire commercially.\n\nFix\n\nLink EWNs to CEs in your registers.\n\nWhen an EWN is issued, log dated mitigation actions and decision-by dates.\n\nReflect mitigation in the programme, even if it is provisional. A mitigation that is not planned is rarely treated as credible. [...] No. Early warning and compensation event notification are separate processes. Issuing an Early Warning does not replace a CE notice, so a contractor can still lose entitlement if the CE itself is not notified in time. However, failing to give an early warning can still reduce the assessment because the CE may be assessed as if the contractor had warned earlier and mitigated promptly.\n\nWhich programme should be used to assess a compensation event under NEC4? [...] | 4. Quotation submitted without a programme story | Spreadsheet plus narrative, no impacted chain | Endless “revise and resubmit” | Decision Pack: programme extract, assumptions, evidence index |\n| 5. Early Warnings not used properly | EWN forgotten, no risk reduction actions | Lower assessment under 63.7 | EWN linked to CE, mitigation actions logged and programmed |\n| 6. Forecast cost done badly | Actuals only, no risk, no time-related cost logic | Money left on the table | Forecast based build-up tied to programme and mitigation |\n| 7. Weak audit trail | Missing contemporaneous records and version control | Negotiated down, delayed payment | Evidence index, strict file naming, programme version register |", "score": 0.75464433, "raw_content": null }, { "url": "https://www.linkedin.com/posts/walkerben1_nec4-early-warning-5-common-misconceptions-activity-7292574630127517696-niye", "title": "You give EW by notifying as soon as you become… | Ben Walker", "content": "Great stuff Ben…. In my NEC training I always say don’t ever say ‘early warning’ and ‘compensation event’ in the same sentence… of course, without an early warning 1-may be some disallowed costs coming your way or 2-Compensation events might be assessed at a lesser value! As to your post (with 25+ years of project experiences) 1-chance of the PM sending an early warning = 5% (unless it’s warning about a contra-charge!!) 2-chance of client entering anything in data part one about risks = 5% (same applies to entries in data part two too!) 3-the amount of early warnings I’ve seen “rejected” = far too many to mention !! Everyone - early warnings are a good thing - risk management is a good thing - avoiding and mitigating risks (and the consequences) is a good thing! Nice post Ben ! [...] Reply 25 Reactions 26 Reactions\n\nJamie Orme 10mo \n\n Report this comment\n\nThe \"i didnt submit an early warning or compensation event on time because we were waiting for costs\" is one of them grinds my gears issues\n\nLike Reply 3 Reactions 4 Reactions\n\nSylvia K W. 10mo \n\n Report this comment\n\nGreat list of misconceptions. Too many NEC users assume they must respond to EWNs in the period of reply, something that's really not a requirement under the contract but has creeped into use because of the various contract management systems.\n\nLike Reply 3 Reactions 4 Reactions\n\nDanny Jones 10mo \n\n Report this comment [...] ⚠️ NEC4 early warning - 5 common misconceptions. ⚠️ ❌Must notify an early warning (EW) before notifying a compensation event (CE).❌ 💡Not true. -You give EW by notifying as soon as you become aware of any matter that ‘could …’. This procedure deals with uncertainty. -If you believe the matter is a CE, then notify a CE. Early warning of a matter for which a CE has previously been notified is not required. -However, it can be helpful to notify any residual uncertainty and take advantage of the collaborative procedure and register. ❌Matters listed in Contract Data part one for inclusion in the Early Warning Register are at the risk of the Client.❌ 💡Incorrect. -The Early Warning Register (EWR) is not a contract document and does not exist prior to Contract Date. The EWR is a management tool.", "score": 0.73868835, "raw_content": null }, { "url": "https://www.gatherinsights.com/en/nec4", "title": "NEC4 Contracts: The Complete UK Guide - Gather Insights", "content": "### What are compensation events in NEC4?\n\nCompensation events are the mechanism within NEC4 contracts that allows the contractor to adjust prices, the Completion Date, or Key Dates when certain specified events occur that are not the contractor's fault. The standard NEC4 Engineering and Construction Contract (ECC) lists 21 compensation events under Clause 60.1. These include instructions that change the Scope, failure to provide site access, physical conditions the contractor could not have reasonably foreseen, and weather measurements exceeding defined thresholds. The contractor must notify most compensation events within eight weeks of becoming aware that the event has occurred, or they lose their entitlement to additional time and money.\n\n### What is the NEC4 eight-week time bar? [...] ### What is the dividing date in NEC4?\n\nThe dividing date is a key concept introduced in NEC4 for assessing compensation events. It separates actual work done from forecast work not yet done. For compensation events arising from Project Manager instructions, the dividing date is the date of the instruction. For other events, it is the date of the compensation event notification. The accepted programme current at the dividing date forms the baseline for assessment: actual costs before the dividing date are used as recorded, while costs after the dividing date are forecast. This prevents assessments from becoming moving targets as administrative delays occur.\n\n### What is Disallowed Cost under NEC4? [...] ## NEC4: Programme - Getting it working for you\n\nExpert analysis of NEC4 programme management covering acceptance consequences, compensation events, time risk allowance, and practical tips for project teams.\n\nView Webinar\n\n\n\n## NEC4: Notifying compensation events and instructing quotations\n\nNEC4 compensation event notification and quotation instruction explained. Expert guidance on Clause 61 and 62 procedures.\n\nView Webinar\n\n\n\n## NEC4: Assessing compensation events part 2 - Price\n\nPart 2 of our NEC4 CE assessment series. Master price assessment, defined cost calculations, and fee application under Option A-E contracts.\n\nView Webinar\n\n\n\n## NEC4 - Taming Commercial Chaos | NEC People Conference 2025 London", "score": 0.67063034, "raw_content": null }, { "url": "https://www.pbctoday.co.uk/news/planning-construction-news/the-nec-4-ecc-contract-notifying-compensation-events-and-early-warnings/118114/", "title": "The NEC 4 ECC Contract: Notifying compensation events and early ...", "content": "Whilst the Contractor had up to 8-weeks to notify this compensation event, he proceeded to carry out work without complying with the requirement of clause 15.1. Upon discovery of the unforeseen structure, the Contractor failed to give early warning to the Project Manager regarding the unforeseen subterranean structure that “could increase the total of the Prices …”\n\nThis should have been done as soon as the Contractor discovered the structure. But, instead, the Contractor elected to wait 7-weeks to notify the compensation event and proceeded to just carry on with the works needed to remove the structure. [...] Alternatively, the Project Manager, perhaps by further reference to the design team and the Client, may have concluded that the structure could remain where it is, instructing that the planned works in that location be carried out somewhere else instead … as such, nothing needed to be done to remove the existing structure.\n\nSo, by failing to give the early warning, the costs incurred by the Contractor in excavating the structure were all “Disallowed Cost,” as the Contractor failed to “give an early warning which the contract required it to give” – hence, the assessment of the compensation event is £0.00. I.e., all costs incurred in excavating the structure did not need to be incurred. Further, no extension of time became due. [...] ### Failure to give an early warning – No money, no additional time?\n\nUnder clause 60.1(12), what happens when a Contractor encounters an unforeseen subterranean structure that, noting NEC 4 clause 60.2, was not in the Site Information or publicly available information, was not obtainable from a visual inspection of the site, and was not, in any event, something that an experienced contractor could have reasonably anticipated?\n\nFor the sake of argument, let us assume that all boxes are ticked as per clause 60.1(12) and the related clause 60.2 and hence that this is a compensation event. Now what? The Contractor has up to 8-weeks to notify it as such.", "score": 0.6493346, "raw_content": null }, { "url": "https://necstorageprod.blob.core.windows.net/mediacontainer/nec/media/nec/products/events/ap%20ug%20conferences%20and%20workshops/presentations/presentations2015/09-pm_dga-managing-risks-and-compensation-events.pdf", "title": "[PDF] Managing Risks and Compensation Events – A Practical Case Study", "content": "If the Project Manager decides that the Contractor has not assessed the compensation event correctly in a quotation and he does not instruct the Contractor to submit a revised quotation. In this case he knows the Contractor has not taken on board the fact, and is unlikely to do so, that he did not give an early warning. Project Timeline – Week 27 Did the Contractor give an early warning? 66 Clause 63.5 (Assessing Compensation Events) If the Project Manager has notified the Contractor of his decision that the Contractor did not give an early warning of a compensation event which an experienced contractor could have given, the event is assessed as if the Contractor had given early warning. The Project Manager will say that if he had been told via an early warning about the utility company [...] stated in the Works Information. Project Timeline – Week 27 Did the Contractor give an early warning? 64 NO! – So when the Project Manager requests a quotation: Clause 61.5 If the Project Manager decides that the Contractor did not give an early warning of the event which an experienced Contractor could have given, he notifies this decision to the Contractor when he instructs him to submit quotations. Why does he do this? Project Timeline – Week 27 Did the Contractor give an early warning? 65 When the Project Manager receives the quotation: Clause 62.3 …The Project Manager replies within two weeks…His reply is • A notification that he will be making his own assessment Clause 64.1 The Project Manager assesses a compensation event • If the Project Manager decides that the Contractor has not [...] no retrospective analysis of concurrent contractor delays Compensation Events - Assessments • Assessments are to include cost and time risk allowances “for matters which have a significant chance of occurring and are at the Contractor’s risk…” (clause 63.6) • Assessments assume that – the Contractor reacts competently and promptly to the compensation event – any Defined Cost and delay is reasonably incurred – the Accepted Programme can be changed (cl. 63.7) • Cost based on Schedule of Cost Components (HK amended) Effect of implementing compensation events • Assessments are not revised if a forecast they were based on shown to be wrong – cl. 65.1 • Idea is once a quotation is agreed the parties are bound by it whether it is right or wrong. • But, PM may state “assumptions” for a", "score": 0.50476116, "raw_content": null } ], "formatted": "Source: 7 Common Pitfalls When Managing NEC4 Compensation Events as ...\nURL: https://www.necplanningsolutions.co.uk/post/7-common-pitfalls-when-managing-compensation-events-in-nec4-as-a-contractor\nWhy it hurts under NEC4 If the contractor failed to give an early warning of an event that becomes a compensation event, the PM can state that when instructing a quotation (clause 61.5), and the CE is assessed as if the early warning had been given (clause 63.7). In practice, that can reduce the CE assessment. Also, NEC guidance is clear that compensation events are assessed assuming the contractor acts promptly and competently (63.7). Waiting for agreement before acting can backfire commercially. Fix Link EWNs to CEs in your registers. When an EWN is issued, log dated mitigation actions and decision-by dates. Reflect mitigation in the programme, even if it is provisional. A mitigation that is not planned is rarely treated as credible. [...] No. Early warning and compensation event notification are separate processes. Issuing an Early Warning does not replace a CE notice, so a contractor can still lose entitlement if the CE itself is not notified in time. However, failing to give an early warning can still reduce the assessment because the CE may be assessed as if the contractor had warned earlier and mitigated promptly. Which programme should be used to assess a compensation event under NEC4? [...] | 4. Quotation submitted without a programme story | Spreadsheet plus narrative, no impacted chain | Endless “revise and resubmit” | Decision Pack: programme extract, assumptions, evidence index | | 5. Early Warnings not used properly | EWN forgotten, no risk reduction actions | Lower assessment under 63.7 | EWN linked to CE, mitigation actions logged and programmed | | 6. Forecast cost done badly | Actuals only, no risk, no time-related cost logic | Money left on the table | Forecast based build-up tied to programme and mitigation | | 7. Weak audit trail | Missing contempor\n\n---\n\nSource: You give EW by notifying as soon as you become… | Ben Walker\nURL: https://www.linkedin.com/posts/walkerben1_nec4-early-warning-5-common-misconceptions-activity-7292574630127517696-niye\nGreat stuff Ben…. In my NEC training I always say don’t ever say ‘early warning’ and ‘compensation event’ in the same sentence… of course, without an early warning 1-may be some disallowed costs coming your way or 2-Compensation events might be assessed at a lesser value! As to your post (with 25+ years of project experiences) 1-chance of the PM sending an early warning = 5% (unless it’s warning about a contra-charge!!) 2-chance of client entering anything in data part one about risks = 5% (same applies to entries in data part two too!) 3-the amount of early warnings I’ve seen “rejected” = far too many to mention !! Everyone - early warnings are a good thing - risk management is a good thing - avoiding and mitigating risks (and the consequences) is a good thing! Nice post Ben ! [...] Reply 25 Reactions 26 Reactions Jamie Orme 10mo Report this comment The \"i didnt submit an early warning or compensation event on time because we were waiting for costs\" is one of them grinds my gears issues Like Reply 3 Reactions 4 Reactions Sylvia K W. 10mo Report this comment Great list of misconceptions. Too many NEC users assume they must respond to EWNs in the period of reply, something that's really not a requirement under the contract but has creeped into use because of the various contract management systems. Like Reply 3 Reactions 4 Reactions Danny Jones 10mo Report this comment [...] ⚠️ NEC4 early warning - 5 common misconceptions. ⚠️ ❌Must notify an early warning (EW) before notifying a compensation event (CE).❌ 💡Not true. -You give EW by notifying as soon as you become aware of any matter that ‘could …’. This procedure deals with uncertainty. -If you believe the matter is a CE, then notify a CE. Early warning of a matter for which a CE has previously been notified is not requir\n\n---\n\nSource: NEC4 Contracts: The Complete UK Guide - Gather Insights\nURL: https://www.gatherinsights.com/en/nec4\n### What are compensation events in NEC4? Compensation events are the mechanism within NEC4 contracts that allows the contractor to adjust prices, the Completion Date, or Key Dates when certain specified events occur that are not the contractor's fault. The standard NEC4 Engineering and Construction Contract (ECC) lists 21 compensation events under Clause 60.1. These include instructions that change the Scope, failure to provide site access, physical conditions the contractor could not have reasonably foreseen, and weather measurements exceeding defined thresholds. The contractor must notify most compensation events within eight weeks of becoming aware that the event has occurred, or they lose their entitlement to additional time and money. ### What is the NEC4 eight-week time bar? [...] ### What is the dividing date in NEC4? The dividing date is a key concept introduced in NEC4 for assessing compensation events. It separates actual work done from forecast work not yet done. For compensation events arising from Project Manager instructions, the dividing date is the date of the instruction. For other events, it is the date of the compensation event notification. The accepted programme current at the dividing date forms the baseline for assessment: actual costs before the dividing date are used as recorded, while costs after the dividing date are forecast. This prevents assessments from becoming moving targets as administrative delays occur. ### What is Disallowed Cost under NEC4? [...] ## NEC4: Programme - Getting it working for you Expert analysis of NEC4 programme management covering acceptance consequences, compensation events, time risk allowance, and practical tips for project teams. View Webinar ## NEC4: Notifying compensation events and instructing quotations NEC4\n\n---\n\nSource: The NEC 4 ECC Contract: Notifying compensation events and early ...\nURL: https://www.pbctoday.co.uk/news/planning-construction-news/the-nec-4-ecc-contract-notifying-compensation-events-and-early-warnings/118114/\nWhilst the Contractor had up to 8-weeks to notify this compensation event, he proceeded to carry out work without complying with the requirement of clause 15.1. Upon discovery of the unforeseen structure, the Contractor failed to give early warning to the Project Manager regarding the unforeseen subterranean structure that “could increase the total of the Prices …” This should have been done as soon as the Contractor discovered the structure. But, instead, the Contractor elected to wait 7-weeks to notify the compensation event and proceeded to just carry on with the works needed to remove the structure. [...] Alternatively, the Project Manager, perhaps by further reference to the design team and the Client, may have concluded that the structure could remain where it is, instructing that the planned works in that location be carried out somewhere else instead … as such, nothing needed to be done to remove the existing structure. So, by failing to give the early warning, the costs incurred by the Contractor in excavating the structure were all “Disallowed Cost,” as the Contractor failed to “give an early warning which the contract required it to give” – hence, the assessment of the compensation event is £0.00. I.e., all costs incurred in excavating the structure did not need to be incurred. Further, no extension of time became due. [...] ### Failure to give an early warning – No money, no additional time? Under clause 60.1(12), what happens when a Contractor encounters an unforeseen subterranean structure that, noting NEC 4 clause 60.2, was not in the Site Information or publicly available information, was not obtainable from a visual inspection of the site, and was not, in any event, something that an experienced contractor could have reasonably anticipated? For the sake\n\n---\n\nSource: [PDF] Managing Risks and Compensation Events – A Practical Case Study\nURL: https://necstorageprod.blob.core.windows.net/mediacontainer/nec/media/nec/products/events/ap%20ug%20conferences%20and%20workshops/presentations/presentations2015/09-pm_dga-managing-risks-and-compensation-events.pdf\nIf the Project Manager decides that the Contractor has not assessed the compensation event correctly in a quotation and he does not instruct the Contractor to submit a revised quotation. In this case he knows the Contractor has not taken on board the fact, and is unlikely to do so, that he did not give an early warning. Project Timeline – Week 27 Did the Contractor give an early warning? 66 Clause 63.5 (Assessing Compensation Events) If the Project Manager has notified the Contractor of his decision that the Contractor did not give an early warning of a compensation event which an experienced contractor could have given, the event is assessed as if the Contractor had given early warning. The Project Manager will say that if he had been told via an early warning about the utility company [...] stated in the Works Information. Project Timeline – Week 27 Did the Contractor give an early warning? 64 NO! – So when the Project Manager requests a quotation: Clause 61.5 If the Project Manager decides that the Contractor did not give an early warning of the event which an experienced Contractor could have given, he notifies this decision to the Contractor when he instructs him to submit quotations. Why does he do this? Project Timeline – Week 27 Did the Contractor give an early warning? 65 When the Project Manager receives the quotation: Clause 62.3 …The Project Manager replies within two weeks…His reply is • A notification that he will be making his own assessment Clause 64.1 The Project Manager assesses a compensation event • If the Project Manager decides that the Contractor has not [...] no retrospective analysis of concurrent contractor delays Compensation Events - Assessments • Assessments are to include cost and time risk allowances “for matters which have a significant c" }