{
  "query": "NEC4 contract auto-approval risks PM right to reject",
  "raw_results": [
    {
      "url": "https://gmhplanning.co.uk/nec-guidance-notes/ecc-clause-31-3-programme-acceptance/",
      "title": "ECC Clause 31.3 - Programme Acceptance - NEC Guidance Note",
      "content": "In terms of point 1, NEC4 now introduces a clearer sanction compared to that of NEC3. If there is no response to the submitted programme within two weeks, the Contractor may notify the Project Manager of the lack of their response. If the Project Manager fails to respond within a further week, the programme at that point would be “deemed accepted” under the contract. Under NEC3 the Contractor could only notify a compensation event for the lack of response under 60.1(1). This may have encouraged a reaction but was not a compensation event the Contractor could ever claim money against as in the meantime they would be proceeding with the works. This NEC4 sanction should ensure that the programme is responded to and at least gives the Contractor a clear contractual route if there is no [...] Whether a programme has been accepted or not is not a condition precedent for the Contractor proceeding with the works, i.e. Contractor can not refuse to work until such time that the programme is accepted. Equally important to recognise that if the Project Manager does not respond within two weeks of being issued then the programme is NOT instant deemed accepted. NEC4 requires a notification reminder before one week later the programme would be deemed accepted. There are no other deemed acceptance processes at all within the contract, other than three very specific conditions associated with the acceptance of compensation events quotations or notifications (which are considered in the compensation event section of these guidance notes).",
      "score": 0.5335682,
      "raw_content": null
    },
    {
      "url": "https://sypro.co.uk/blogs/how-to-clarify-effectively-instructions-and-proposed-instructions-under-nec4-ecc/",
      "title": "Instructions and Proposed Instructions under NEC4 ECC",
      "content": "For straight forward work, the NEC4 ECC gives Project Managers the authority to issue instructions under clause 14.3, allowing them to change the Scope of the works. However, where that change affects time or cost, it must also be notified as a compensation event under clause 61.1. This is then followed by a quotation request using clause 61.2. Missing any of these steps – or doing them out of order – risks confusion and non-compliance. One common mistake Dr Kings highlighted is when a compensation event is notified before the actual instruction has been issued, or when no instruction is given at all. In both cases, the communication lacks contractual standing. Both steps must be followed. [...] If the contractor misses the quotation deadline, the Project Manager is required to make their own assessment. If the Project Manager fails to respond within the agreed timeframe – and no extension has been granted – the quotation is automatically deemed accepted (if the reminder has been served by the contractor). These timelines are there to keep things moving and avoid disputes caused by inaction or ambiguity.\n\n### Bringing it all together with Sypro [...] Dr Kings recommends that these assumptions focus on the most likely or best-case scenario. Overly cautious or worst-case assumptions tend to inflate quotes and slow things down – often unnecessarily. A balanced approach, built on open communication and fair assumptions, helps ensure quotations are realistic and that risk is managed proportionately.\n\n### Keeping on top of compensation events\n\nThe compensation event process follows four distinct stages: notification, quotation, assessment and implementation. Under standard NEC4 timescales, Project Managers have one week to respond to a notified compensation event, contractors have three weeks to submit their quotation, and Project Managers then have two weeks to respond.",
      "score": 0.5248093,
      "raw_content": null
    },
    {
      "url": "https://www.pinsentmasons.com/out-law/guides/nec4-a-more-collaborative-approach",
      "title": "NEC4: a more collaborative approach",
      "content": "We will now look at the changes to the core clauses, options and dispute resolution mechanisms in NEC4 in more detail.\n\n### Core Clause 1: general\n\nCore clause 1 incorporates defined terms, interpretation, communications and ambiguities.\n\nThe previous 10.1 is now split in two. Mutual trust and cooperation is now at 10.2 while 10.1 simply states the obvious: that the parties must comply with the contract.\n\nAt 11.2(19), there is a new definition of subcontractor which excludes labour suppliers. This had been an issue in practice.\n\nHelpfully, 13.4 makes it clear that if the project manager (PM) rejects something in the contractor's programme, the PM must provide reasons \"in sufficient detail to enable the contractor to correct the matter\". [...] Disputes over what is legitimately 'defined cost' have often occurred, and the new clause is designed to tackle the not infrequent problem of costs being disallowed at a late stage following an audit by the client. It requires the contractor to notify the PM when each part of defined cost has been finalised, and then make records available for the PM to review. The PM must then accept or challenge costs within 13 weeks, subject to being allowed to request more records and consider the same within four weeks of receipt. Failing this, the contractor's assessment will be treated as correct. [...] A new compensation event is introduced where the PM notifies that a proposed instruction is not accepted. This is intended to deal with ensuring that contractors are paid for the time they spent working on the quotation. However, it seems to be quite a blunt tool which ignores the reason behind the PM requesting the proposed instruction in the first place.",
      "score": 0.5230555,
      "raw_content": null
    },
    {
      "url": "https://www.diales.com/en/news/nec4-treated-acceptance-and-dividing-date",
      "title": "NEC4 – Treated Acceptance and Dividing Date | Diales",
      "content": "With respect to a Project Manager who engages but still, for strategic purposes, refuses to accept programmes, Contractors should ensure that they keep forcing the issue both by following the timescales stipulated in clause 31 of the NEC4 alongside reminding the Project Manager that, by reference to Clause 14, they are not signing a blank cheque by accepting the programme.  Such a two-pronged persuasive attack may push previously reticent Project Manager's over the edge into accepting programmes.  Strategic refusal to accept programmes should then be taken up the food chain to senior management via Clause W1 or W2.  However, this should only be done when the Contractor is confident that its programme is fully compliant with Clauses 31.3 in that the programme is practicable, contains all [...] The NEC4 concept of “Treated Acceptance” (Clause 31.3) has been incorporated into the Contract to provide the Contractor with options (note “may notify”) when a Project Manager fails to respond to a programme which has been issued for acceptance.  The addition of the “Treated Acceptance” regime will assist the Parties when a Project Manager fails to respond (within the stipulated time) to a programme which has been issued for acceptance by helping to apply pressure within when dealing with a Project Manager who is reticent to engage with the Accepted Programme. [...] Some Project Managers (as above) avoid accepting programmes as a tactic, but others simply fail to understand what accepting a programme means.  The worry that accepting a programme thereby accepts revised liabilities and obligations is, in my opinion, unfounded as the Project Manager is protected by, including but not limited to, Clause 14.  This clause states that acceptance of any communication does not transfer liability away from the contractor to comply with his obligations under the contract.",
      "score": 0.46628717,
      "raw_content": null
    },
    {
      "url": "https://sypro.co.uk/blogs/the-ultimate-nec4-ecc-checklist-for-project-managers/",
      "title": "The ultimate NEC4 ECC checklist for Project Managers | Sypro",
      "content": "The NEC4 ECC is no different. Without diligent, proactive contract management, project teams risk serious consequences. Our practical checklist is designed to help project managers, contract administrators and site teams stay on top of their responsibilities across the contract lifecycle, reducing the risk of disruption and keeping things running efficiently.\n\n### Why contract administration matters\n\nIn our recent Knowledge Hub webinar, NEC4 drafter and co-author of NEC 3 / 4 Practical Solutions, Dr Stuart Kings reinforced just how important strong project management is. He warned that failure to follow NEC guidelines can lead to real consequences, including delays in payment and, in some cases, termination of the contractor’s obligations. [...] ### Managing early warnings and risk registers\n\nClause 15.2 sets the tone for proactive risk management. The Project Manager must prepare and issue the first early warning register within one week of the starting date and instruct the contractor to attend an early warning meeting within two weeks. These meetings, which can be held online or in person, offer a valuable opportunity to flag and discuss potential risks early – before they escalate into bigger issues.\n\nUsed well, they can also be a chance to review our NEC4 ECC checklist and identify areas where additional diligence or collaboration may be needed.\n\n### Subcontractor approvals and third-party sign-offs [...] The final assessment must be carried out either within four weeks of the ‘Defects Certificate’ or 13 weeks after the ‘Termination Certificate’. As this often happens long after practical completion – when original teams may have moved on – strong internal handovers and clear diary reminders are critical. Sypro can support this process by automating alerts and ensuring important deadlines don’t get missed.\n\n### Understanding secondary options and Z clauses\n\nSeveral secondary options in NEC4 can introduce additional requirements that project teams must stay on top of. Clause X4, for instance, requires a ‘Holding Company Guarantee’ to be provided within four weeks of contract signing – failure to meet this obligation gives the client the right to terminate under Clause 91.2.",
      "score": 0.46249792,
      "raw_content": null
    }
  ],
  "formatted": "Source: ECC Clause 31.3 - Programme Acceptance - NEC Guidance Note\nURL: https://gmhplanning.co.uk/nec-guidance-notes/ecc-clause-31-3-programme-acceptance/\nIn terms of point 1, NEC4 now introduces a clearer sanction compared to that of NEC3. If there is no response to the submitted programme within two weeks, the Contractor may notify the Project Manager of the lack of their response. If the Project Manager fails to respond within a further week, the programme at that point would be “deemed accepted” under the contract. Under NEC3 the Contractor could only notify a compensation event for the lack of response under 60.1(1). This may have encouraged a reaction but was not a compensation event the Contractor could ever claim money against as in the meantime they would be proceeding with the works. This NEC4 sanction should ensure that the programme is responded to and at least gives the Contractor a clear contractual route if there is no [...] Whether a programme has been accepted or not is not a condition precedent for the Contractor proceeding with the works, i.e. Contractor can not refuse to work until such time that the programme is accepted. Equally important to recognise that if the Project Manager does not respond within two weeks of being issued then the programme is NOT instant deemed accepted. NEC4 requires a notification reminder before one week later the programme would be deemed accepted. There are no other deemed acceptance processes at all within the contract, other than three very specific conditions associated with the acceptance of compensation events quotations or notifications (which are considered in the compensation event section of these guidance notes).\n\n---\n\nSource: Instructions and Proposed Instructions under NEC4 ECC\nURL: https://sypro.co.uk/blogs/how-to-clarify-effectively-instructions-and-proposed-instructions-under-nec4-ecc/\nFor straight forward work, the NEC4 ECC gives Project Managers the authority to issue instructions under clause 14.3, allowing them to change the Scope of the works. However, where that change affects time or cost, it must also be notified as a compensation event under clause 61.1. This is then followed by a quotation request using clause 61.2. Missing any of these steps – or doing them out of order – risks confusion and non-compliance. One common mistake Dr Kings highlighted is when a compensation event is notified before the actual instruction has been issued, or when no instruction is given at all. In both cases, the communication lacks contractual standing. Both steps must be followed. [...] If the contractor misses the quotation deadline, the Project Manager is required to make their own assessment. If the Project Manager fails to respond within the agreed timeframe – and no extension has been granted – the quotation is automatically deemed accepted (if the reminder has been served by the contractor). These timelines are there to keep things moving and avoid disputes caused by inaction or ambiguity. ### Bringing it all together with Sypro [...] Dr Kings recommends that these assumptions focus on the most likely or best-case scenario. Overly cautious or worst-case assumptions tend to inflate quotes and slow things down – often unnecessarily. A balanced approach, built on open communication and fair assumptions, helps ensure quotations are realistic and that risk is managed proportionately. ### Keeping on top of compensation events The compensation event process follows four distinct stages: notification, quotation, assessment and implementation. Under standard NEC4 timescales, Project Managers have one week to respond to a notified compensation event, contractors ha\n\n---\n\nSource: NEC4: a more collaborative approach\nURL: https://www.pinsentmasons.com/out-law/guides/nec4-a-more-collaborative-approach\nWe will now look at the changes to the core clauses, options and dispute resolution mechanisms in NEC4 in more detail. ### Core Clause 1: general Core clause 1 incorporates defined terms, interpretation, communications and ambiguities. The previous 10.1 is now split in two. Mutual trust and cooperation is now at 10.2 while 10.1 simply states the obvious: that the parties must comply with the contract. At 11.2(19), there is a new definition of subcontractor which excludes labour suppliers. This had been an issue in practice. Helpfully, 13.4 makes it clear that if the project manager (PM) rejects something in the contractor's programme, the PM must provide reasons \"in sufficient detail to enable the contractor to correct the matter\". [...] Disputes over what is legitimately 'defined cost' have often occurred, and the new clause is designed to tackle the not infrequent problem of costs being disallowed at a late stage following an audit by the client. It requires the contractor to notify the PM when each part of defined cost has been finalised, and then make records available for the PM to review. The PM must then accept or challenge costs within 13 weeks, subject to being allowed to request more records and consider the same within four weeks of receipt. Failing this, the contractor's assessment will be treated as correct. [...] A new compensation event is introduced where the PM notifies that a proposed instruction is not accepted. This is intended to deal with ensuring that contractors are paid for the time they spent working on the quotation. However, it seems to be quite a blunt tool which ignores the reason behind the PM requesting the proposed instruction in the first place.\n\n---\n\nSource: NEC4 – Treated Acceptance and Dividing Date | Diales\nURL: https://www.diales.com/en/news/nec4-treated-acceptance-and-dividing-date\nWith respect to a Project Manager who engages but still, for strategic purposes, refuses to accept programmes, Contractors should ensure that they keep forcing the issue both by following the timescales stipulated in clause 31 of the NEC4 alongside reminding the Project Manager that, by reference to Clause 14, they are not signing a blank cheque by accepting the programme. Such a two-pronged persuasive attack may push previously reticent Project Manager's over the edge into accepting programmes. Strategic refusal to accept programmes should then be taken up the food chain to senior management via Clause W1 or W2. However, this should only be done when the Contractor is confident that its programme is fully compliant with Clauses 31.3 in that the programme is practicable, contains all [...] The NEC4 concept of “Treated Acceptance” (Clause 31.3) has been incorporated into the Contract to provide the Contractor with options (note “may notify”) when a Project Manager fails to respond to a programme which has been issued for acceptance. The addition of the “Treated Acceptance” regime will assist the Parties when a Project Manager fails to respond (within the stipulated time) to a programme which has been issued for acceptance by helping to apply pressure within when dealing with a Project Manager who is reticent to engage with the Accepted Programme. [...] Some Project Managers (as above) avoid accepting programmes as a tactic, but others simply fail to understand what accepting a programme means. The worry that accepting a programme thereby accepts revised liabilities and obligations is, in my opinion, unfounded as the Project Manager is protected by, including but not limited to, Clause 14. This clause states that acceptance of any communication does not transfer liability\n\n---\n\nSource: The ultimate NEC4 ECC checklist for Project Managers | Sypro\nURL: https://sypro.co.uk/blogs/the-ultimate-nec4-ecc-checklist-for-project-managers/\nThe NEC4 ECC is no different. Without diligent, proactive contract management, project teams risk serious consequences. Our practical checklist is designed to help project managers, contract administrators and site teams stay on top of their responsibilities across the contract lifecycle, reducing the risk of disruption and keeping things running efficiently. ### Why contract administration matters In our recent Knowledge Hub webinar, NEC4 drafter and co-author of NEC 3 / 4 Practical Solutions, Dr Stuart Kings reinforced just how important strong project management is. He warned that failure to follow NEC guidelines can lead to real consequences, including delays in payment and, in some cases, termination of the contractor’s obligations. [...] ### Managing early warnings and risk registers Clause 15.2 sets the tone for proactive risk management. The Project Manager must prepare and issue the first early warning register within one week of the starting date and instruct the contractor to attend an early warning meeting within two weeks. These meetings, which can be held online or in person, offer a valuable opportunity to flag and discuss potential risks early – before they escalate into bigger issues. Used well, they can also be a chance to review our NEC4 ECC checklist and identify areas where additional diligence or collaboration may be needed. ### Subcontractor approvals and third-party sign-offs [...] The final assessment must be carried out either within four weeks of the ‘Defects Certificate’ or 13 weeks after the ‘Termination Certificate’. As this often happens long after practical completion – when original teams may have moved on – strong internal handovers and clear diary reminders are critical. Sypro can support this process by automating alerts and ensuring "
}