What distinction does the publisher describe?
The NEC publisher's 23 June 2025 introduction distinguishes Completion and sectional Completion dates from Key Dates for specified conditions. It describes possible delay damages with option X7 and additional costs for missed Key Date conditions. The actual edition, selected options and amendments control the project.
Pre-bid Review is independent and is not affiliated with NEC. This article is not legal advice. Obtain qualified contracts and legal review before deciding exposure, enforceability, notice action or a proposed contractual position.
Sources: NEC Contracts: NEC4 ECC time provisions: an introduction for new NEC users, 23 June 2025
How should an electrical package milestone be classified?
Read the actual Contract Data, Scope, selected options and amendments together. Preserve their wording through a controlled reference rather than rename every date a deadline. A contractor's internal target does not become a contractual Key Date because it appears on a programme.
| Field | Evidence | Review action |
|---|---|---|
| Key Date | Exact condition and date from the contract | Identify the condition owner and consequence for review |
| Sectional Completion | Defined section and its Completion date | Check the selected contractual mechanism |
| Overall Completion | Whole-works Completion obligation | Keep it separate from a local work target |
| Programme activity | Planned activity and current programme revision | Check whether a contract obligation also applies |
| Conflict | Competing source, date or condition | Raise a clarification with a named reviewer |
Why does the condition matter as much as the date?
Illustrative example. A fictional electrical package has a condition to make a room available for another contractor on 12 May. A defined section has a separate Completion date of 30 May. The bid register keeps two rows and the exact condition references. It does not relabel both as section complete.
If the room-availability wording is unclear, the reviewer requests clarification of the required condition, access boundary and evidence. This illustration does not decide whether either obligation has been met or calculate damages. Do not attach an invented daily rate to the Key Date row.
What should the bid team resolve before accepting the programme basis?
Check that each contractual date is represented with the right condition and package interface. Record missing definitions, inconsistent dates and amendments affecting the selected options. Route the potential consequence to the authorised contracts reviewer rather than treating a planning label as a legal conclusion.
Keep the register linked to the actual accepted programme where applicable, while preserving contractual and planning dates as different evidence. This worksheet supports issue identification and does not amend the contract or excuse an obligation.
Common questions
What else should the bid team know?
Is every programme milestone a contractual Key Date?
No. Identify the actual contract source and condition.
Can a Key Date automatically be given a delay-damages rate?
Do not assume this. Have the actual contract mechanism and amendments reviewed.
Does this register establish a legal entitlement?
No. It is an administrative review aid and is not legal advice.