{
  "query": "NEC contract PM response deadline consequences for overdue NCEs",
  "raw_results": [
    {
      "url": "https://www.gatherinsights.com/en/nec4/response-periods",
      "title": "NEC4 Response Periods: Complete Deadlines Guide",
      "content": "2. Treating the period for reply as a fixed contract term. The period for reply is a Contract Data entry. On projects where it has been set to three or four weeks rather than the standard two, significant time passes before a response is overdue. Always check Contract Data Part 1 at the start of the project, not when you think a deadline has been missed.\n\n3. Assuming the PM's non-response means rejection. Under clause 61.4, the PM's silence on a CE notification within one week means the notification is accepted — the opposite of rejection. Treating silence as a cue to drop the CE and move on is commercially damaging. Document the notification, note the PM's failure to respond, and proceed with the quotation. [...] No. The eight-week notification requirement under clause 61.3 applies only to the Contractor. Events arising from PM or Supervisor actions — instructions, notifications, certificates, or changed decisions — are not subject to the Contractor time bar. The PM notifies these events under clause 61.1. Where the PM has its own response obligations (clauses 61.4 and 62.6), missed deadlines create deemed acceptance consequences rather than loss of entitlement. The PM does not lose the ability to assess a CE by missing their response window; they lose the ability to reject what the Contractor has submitted.\n\n### Can NEC4 response periods be extended? [...] Gather tracks PM response deadlines automatically alongside Contractor notification deadlines. When the PM's two-week quotation response window is approaching expiry, the commercial team is alerted before it closes — so the clause 62.6 notification can be issued at the right moment, not missed entirely.\n\n## Five Common Mistakes with NEC4 Response Periods\n\n1. Only tracking Contractor deadlines. The eight-week time bar receives most attention because missing it destroys entitlement. But the PM has its own response deadlines with their own consequences. Teams that track only Contractor obligations miss the commercial value of PM deadline failures. The deemed acceptance provisions in clauses 61.4 and 62.6 exist specifically to be used.",
      "score": 0.7336813,
      "raw_content": null
    },
    {
      "url": "https://www.hka.com/article/approach-to-delay-analysis-involving-nec-contracts/",
      "title": "Approach to Delay Analysis involving NEC Contracts",
      "content": "Both steps require acceptance by the Project Manager, so if historically acceptance was not given, then it is not considered appropriate to use the latest programme or progress update in question.\n\n### Importance of the Notice of Compensation Event (NCE)\n\nDelay to completion may be a consequence of any compensation event.\n\nThe expectation of the NEC3 Contract is that any compensation event will be subject of prior notice of compensation event (NCE) by the parties: [...] The Project Manager will be required to issue an NCE to the Contractor, for example, if he intends to issue an instruction changing the works information (clause 61.1);\n The Contractor will be required to issue an NCE to the Project Manager within 8 weeks of it becoming aware that an event has caused or is expected to cause delay (clause 61.3).\n\nWhen viewed retrospectively in adjudication proceedings, in my experience adjudicators look at the precise wording in the original NCE. It is therefore imperative that when undertaking a delay analysis, that when the analyst articulates the nature of the compensation event and how this might impact the intended planned sequence of works, that it is consistent with the description as provided within the original NCE. [...] For example, an item of design information is due to be issued to a Contractor by a certain deadline. That deadline is missed and because the design information is required for its works on site, the Contractor will issue an NCE as the lack of information is now preventing the progress of the works on site. However, it may not be known to the Contractor when the outstanding  information is likely to be delivered, so when issuing the NCE he can only speculate. The delay analyst has the benefit of hindsight as to when the design information was issued, so by way of a ‘sense check’, can model the compensation event to give a more precise assessment of its impact.\n\nThis approach has been accepted by adjudicators.\n\n### Sourcing as built data from accepted programmes",
      "score": 0.61695945,
      "raw_content": null
    },
    {
      "url": "https://www.neccontract.com/news/do-what-nec4-ecc-says-or-face-the-%E2%80%98enforcement-clauses%E2%80%99?srsltid=AfmBOoqt3xEZitMMiLVz2qa596kKt_DIqrZygf_NzNSELgo01zUUOFMC",
      "title": "Do what NEC4 ECC says or face the ‘enforcement clauses’ | News | NEC Contracts",
      "content": "| 62.3 | Project manager to respond within 2 weeks to a quotation from the contractor. | 62.6 | The contractor may remind the project manager if they have not responded within the 2 week period. This gives the project manager another 2 weeks. Failure to respond within the further 2 week period means the project manager is deemed to have accepted the quotation. | [...] | 61.3 | Contactor to notify compensation events when they happen. | 61.3 | If the contractor does not notify within 8 weeks of becoming aware of the event, there is no change to the prices, the completion date or any key dates. This does not apply to compensation events that the project manager should have notified under clause 61.1. |\n| 61.4 | Project manager to respond within 1 week to a contractor notification of an event. | 61.4 | The contractor may remind the project manager if they fail to respond with the week. This gives the project manager another 2 weeks to respond. Failure to respond within the further 2 week period means the project manager is deemed to have accepted that the event was a compensation event and instructed a quotation. | [...] | 30.1 | Contractor to achieve completion by the completion date. | X7 | The contractor must pay the delay damages in the contract data if option X7 has been included. There is no discretion for the project manager: if the contractor is late, the project manager includes the delay damages in the assessment of the amount due. This applies to the whole of the works and to sections if option X5 is included. |",
      "score": 0.6083387,
      "raw_content": null
    },
    {
      "url": "https://coniston-associates.co.uk/take-notice-a-brief-guide-to-nec-contract-notices/",
      "title": "Take Notice! - A Brief Guide to NEC Contract Notices - Coniston Construction Associates Ltd - Construction Lawyers, Commercial & Contract Specialists",
      "content": "So, the consequences of the Contractor failing to issue the appropriate early warning can theoretically be serious and substantial.\n\nThe NEC’s approach here is that the contractor would be motivated by the financial consequences of clause 63.7 to identify problems at the earliest possible opportunity, and then to actively contribute to providing solutions.\n\nAny failure of a Project Manager to give early warning is not expressly referred to within the Contract. However, such failure could result in an increase in cost or time, or reduction in quality, all of which disadvantage Client. The NEC assumes that, as the Project Manager is acting for the Client, he is expected to be conscientious and give an early warning notice when matters arise.\n\n### Notices of Compensation Events [...] It is vital for the Contractor to be familiar with clause 61.3. Where a Contractor fails to notify the Project Manager of a compensation event within 8 weeks of becoming aware of the event, clause 61.3 prevents his right to claim an adjustment to the Prices and the Completion Date (unless it is an event which the Project Manager should have notified to the Contractor). Hence, clause 61.3 is a condition precedent, operating as a time bar to the Contractor’s entitlement to any time and cost consequences of the compensation event. [...] Clause 62.3: Within two weeks of receiving a Contractor’s quotation, the Project Manager must respond. If the Project Manager accepts the quotation, he must issue a notification to confirm this. Alternatively, the Project Manager can notify he will be making his own assessment, or he could instruct the Contractor to submit a revised quotation.\n\nClause 62.5: The Project Manager has the power to grant more time for the submission of quotations. However, an extension can only be granted before the original time limit for submitting the quotation has expired.",
      "score": 0.46089602,
      "raw_content": null
    },
    {
      "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 a Contractor",
      "content": "THE 7 PITFALLS\n\nPitfall 1: Failing to notify within the contractual time limits\n\nWhat it looks like\n\nThe team waits until the impact is fully known, or until the issue is “resolved”, then notifies late.\n\nWhy it hurts\n\nUnder NEC time bar is not theoretical. Under clause 61.3, if the contractor fails to notify a compensation event within 8 weeks of becoming aware of the event (subject to the clause 61.1 exception where the PM should have notified), there may be no change to Prices, Completion Date or Key Dates.\n\nNEC’s own guidance is explicit that the 8 weeks runs from awareness of the underlying event, not from realising it is a “compensation event”.\n\nWhat to do instead\n\nTreat CE notification as a planning control, not a QS task. [...] Use a programme extract that clearly shows the impacted chain as it existed on the Accepted Programme at the dividing date.\n\nIf the Accepted Programme is badly out of date, follow NEC’s own practice note approach: agree a programme to use for the assessment, or the PM may assess under clause 64.\n\nPitfall 4: Submitting quotations without a programme story\n\nWhat it looks like\n\nA cost build-up plus paragraphs. The time impact is asserted, not demonstrated.\n\nWhy it hurts\n\nNEC4 is meant to be prospective and logic-driven. Without a programme story, the PM cannot validate “time consequences” in a controlled way, so the quotation cycles.\n\nFix: the CE Decision Pack\n\nYou do not need a long document. You need a consistent one.\n\nCE Decision Pack contents: [...] Pitfall 6: Inaccurate cost forecasting and missing time-related logic\n\nWhat it looks like\n\nThe quotation is based on actuals only, or it forgets time-related prelims, disruption logic, and risk allowances. Alternatively, everything is bundled into one “global” number with no traceability.\n\nWhy it hurts\n\nIf the PM cannot see the cost logic, they will challenge it. If the programme story is weak, you will struggle to justify prolongation and disruption as consequences.\n\nFix: cost the CE like a forecast, not a claim\n\nBuild a simple structure:\n\n Defined cost forecast by resource and work package\n Time-related cost tied to a clear change in planned Completion or Key Dates\n Risk allowance with a rationale aligned to competent and prompt mitigation, as NEC practice notes expect\n\nPractical tip",
      "score": 0.4581311,
      "raw_content": null
    }
  ],
  "formatted": "Source: NEC4 Response Periods: Complete Deadlines Guide\nURL: https://www.gatherinsights.com/en/nec4/response-periods\n2. Treating the period for reply as a fixed contract term. The period for reply is a Contract Data entry. On projects where it has been set to three or four weeks rather than the standard two, significant time passes before a response is overdue. Always check Contract Data Part 1 at the start of the project, not when you think a deadline has been missed. 3. Assuming the PM's non-response means rejection. Under clause 61.4, the PM's silence on a CE notification within one week means the notification is accepted — the opposite of rejection. Treating silence as a cue to drop the CE and move on is commercially damaging. Document the notification, note the PM's failure to respond, and proceed with the quotation. [...] No. The eight-week notification requirement under clause 61.3 applies only to the Contractor. Events arising from PM or Supervisor actions — instructions, notifications, certificates, or changed decisions — are not subject to the Contractor time bar. The PM notifies these events under clause 61.1. Where the PM has its own response obligations (clauses 61.4 and 62.6), missed deadlines create deemed acceptance consequences rather than loss of entitlement. The PM does not lose the ability to assess a CE by missing their response window; they lose the ability to reject what the Contractor has submitted. ### Can NEC4 response periods be extended? [...] Gather tracks PM response deadlines automatically alongside Contractor notification deadlines. When the PM's two-week quotation response window is approaching expiry, the commercial team is alerted before it closes — so the clause 62.6 notification can be issued at the right moment, not missed entirely. ## Five Common Mistakes with NEC4 Response Periods 1. Only tracking Contractor deadlines. The eight-week time bar re\n\n---\n\nSource: Approach to Delay Analysis involving NEC Contracts\nURL: https://www.hka.com/article/approach-to-delay-analysis-involving-nec-contracts/\nBoth steps require acceptance by the Project Manager, so if historically acceptance was not given, then it is not considered appropriate to use the latest programme or progress update in question. ### Importance of the Notice of Compensation Event (NCE) Delay to completion may be a consequence of any compensation event. The expectation of the NEC3 Contract is that any compensation event will be subject of prior notice of compensation event (NCE) by the parties: [...] The Project Manager will be required to issue an NCE to the Contractor, for example, if he intends to issue an instruction changing the works information (clause 61.1); The Contractor will be required to issue an NCE to the Project Manager within 8 weeks of it becoming aware that an event has caused or is expected to cause delay (clause 61.3). When viewed retrospectively in adjudication proceedings, in my experience adjudicators look at the precise wording in the original NCE. It is therefore imperative that when undertaking a delay analysis, that when the analyst articulates the nature of the compensation event and how this might impact the intended planned sequence of works, that it is consistent with the description as provided within the original NCE. [...] For example, an item of design information is due to be issued to a Contractor by a certain deadline. That deadline is missed and because the design information is required for its works on site, the Contractor will issue an NCE as the lack of information is now preventing the progress of the works on site. However, it may not be known to the Contractor when the outstanding information is likely to be delivered, so when issuing the NCE he can only speculate. The delay analyst has the benefit of hindsight as to when the design information was issued, \n\n---\n\nSource: Do what NEC4 ECC says or face the ‘enforcement clauses’ | News | NEC Contracts\nURL: https://www.neccontract.com/news/do-what-nec4-ecc-says-or-face-the-%E2%80%98enforcement-clauses%E2%80%99?srsltid=AfmBOoqt3xEZitMMiLVz2qa596kKt_DIqrZygf_NzNSELgo01zUUOFMC\n| 62.3 | Project manager to respond within 2 weeks to a quotation from the contractor. | 62.6 | The contractor may remind the project manager if they have not responded within the 2 week period. This gives the project manager another 2 weeks. Failure to respond within the further 2 week period means the project manager is deemed to have accepted the quotation. | [...] | 61.3 | Contactor to notify compensation events when they happen. | 61.3 | If the contractor does not notify within 8 weeks of becoming aware of the event, there is no change to the prices, the completion date or any key dates. This does not apply to compensation events that the project manager should have notified under clause 61.1. | | 61.4 | Project manager to respond within 1 week to a contractor notification of an event. | 61.4 | The contractor may remind the project manager if they fail to respond with the week. This gives the project manager another 2 weeks to respond. Failure to respond within the further 2 week period means the project manager is deemed to have accepted that the event was a compensation event and instructed a quotation. | [...] | 30.1 | Contractor to achieve completion by the completion date. | X7 | The contractor must pay the delay damages in the contract data if option X7 has been included. There is no discretion for the project manager: if the contractor is late, the project manager includes the delay damages in the assessment of the amount due. This applies to the whole of the works and to sections if option X5 is included. |\n\n---\n\nSource: Take Notice! - A Brief Guide to NEC Contract Notices - Coniston Construction Associates Ltd - Construction Lawyers, Commercial & Contract Specialists\nURL: https://coniston-associates.co.uk/take-notice-a-brief-guide-to-nec-contract-notices/\nSo, the consequences of the Contractor failing to issue the appropriate early warning can theoretically be serious and substantial. The NEC’s approach here is that the contractor would be motivated by the financial consequences of clause 63.7 to identify problems at the earliest possible opportunity, and then to actively contribute to providing solutions. Any failure of a Project Manager to give early warning is not expressly referred to within the Contract. However, such failure could result in an increase in cost or time, or reduction in quality, all of which disadvantage Client. The NEC assumes that, as the Project Manager is acting for the Client, he is expected to be conscientious and give an early warning notice when matters arise. ### Notices of Compensation Events [...] It is vital for the Contractor to be familiar with clause 61.3. Where a Contractor fails to notify the Project Manager of a compensation event within 8 weeks of becoming aware of the event, clause 61.3 prevents his right to claim an adjustment to the Prices and the Completion Date (unless it is an event which the Project Manager should have notified to the Contractor). Hence, clause 61.3 is a condition precedent, operating as a time bar to the Contractor’s entitlement to any time and cost consequences of the compensation event. [...] Clause 62.3: Within two weeks of receiving a Contractor’s quotation, the Project Manager must respond. If the Project Manager accepts the quotation, he must issue a notification to confirm this. Alternatively, the Project Manager can notify he will be making his own assessment, or he could instruct the Contractor to submit a revised quotation. Clause 62.5: The Project Manager has the power to grant more time for the submission of quotations. However, an extension can\n\n---\n\nSource: 7 Common Pitfalls When Managing NEC4 Compensation Events as a Contractor\nURL: https://www.necplanningsolutions.co.uk/post/7-common-pitfalls-when-managing-compensation-events-in-nec4-as-a-contractor\nTHE 7 PITFALLS Pitfall 1: Failing to notify within the contractual time limits What it looks like The team waits until the impact is fully known, or until the issue is “resolved”, then notifies late. Why it hurts Under NEC time bar is not theoretical. Under clause 61.3, if the contractor fails to notify a compensation event within 8 weeks of becoming aware of the event (subject to the clause 61.1 exception where the PM should have notified), there may be no change to Prices, Completion Date or Key Dates. NEC’s own guidance is explicit that the 8 weeks runs from awareness of the underlying event, not from realising it is a “compensation event”. What to do instead Treat CE notification as a planning control, not a QS task. [...] Use a programme extract that clearly shows the impacted chain as it existed on the Accepted Programme at the dividing date. If the Accepted Programme is badly out of date, follow NEC’s own practice note approach: agree a programme to use for the assessment, or the PM may assess under clause 64. Pitfall 4: Submitting quotations without a programme story What it looks like A cost build-up plus paragraphs. The time impact is asserted, not demonstrated. Why it hurts NEC4 is meant to be prospective and logic-driven. Without a programme story, the PM cannot validate “time consequences” in a controlled way, so the quotation cycles. Fix: the CE Decision Pack You do not need a long document. You need a consistent one. CE Decision Pack contents: [...] Pitfall 6: Inaccurate cost forecasting and missing time-related logic What it looks like The quotation is based on actuals only, or it forgets time-related prelims, disruption logic, and risk allowances. Alternatively, everything is bundled into one “global” number with no traceability. Why it hurts If the PM "
}