NEC rail projects tend to be built around fixed access windows, so a small slip can lose a slot that won't come round again for weeks. That makes the programme, access dates, Key Dates and fast decisions the parts of the contract that matter most.
The conditions are those of the Engineering and Construction Contract (ECC), usually with substantial client-specific requirements in the Scope and Z clauses. This page doesn't describe any client's own rules, so read yours first. It covers general points under NEC4 ECC and is part of the guide to managing NEC contracts.
Access windows in contract terms
The contract has no special concept for a rail possession or similar closed access window. It deals with these through ordinary tools, so you need to decide which tool each window uses.
| Approach | How it works | Effect if the window is lost |
|---|---|---|
| Access date in the Contract Data | Sets when each part of the Site becomes available | Late access past the later of that date and the Accepted Programme date: 60.1(2) |
| A constraint in the Scope | Sets the working times and conditions, including who applies for them | Changing it by instruction: 60.1(1). Missing it by the Contractor's own fault: the Contractor's cost |
| A shown item on the Accepted Programme | The Contractor shows when it needs access (31.2) | Relevant to 60.1(2) and to assessing delay |
| A Key Date | Sets a Condition to be met before a date, such as being ready for a commissioning slot | Possible cost recovery under 25.3 |
| Client decision to cancel | An instruction to stop or not start the work | 60.1(4) |
The labels in your documents matter. Agree at the start how a cancelled or overrunning window will be treated, and put the answer in the first 30 days list. See Key Dates and access dates.
A worked example
A fictional station platform extension, with illustrative figures. A weekend closure is shown on the Accepted Programme for week 20. The next suitable closure is week 28.
- Week 18: the Contractor learns that another party's works on the same weekend might conflict. It issues an early warning.
- Early warning meeting, same week: options are discussed, including a smaller scope in a shorter window.
- Week 19: the closure is withdrawn. The Project Manager looks at why: if the Client's other contractor is working outside the Scope's times or conditions, 60.1(5) may apply. If access is simply not given, it may be 60.1(2). If the Project Manager instructs the change, 60.1(4) or 60.1(1) may apply.
- Quotation: the effect on planned Completion of the eight-week wait, the costs of rebooked labour, and a further alternative with a shorter weeknight sequence (62.1).
Compare that with an overrun caused by the Contractor's own failed lift. It would be the Contractor's risk, and there's probably no compensation event. If Option X7 applies, delay damages may follow, along with any extra cost under a Key Date (25.3). The Contractor needs to record exactly what caused an overrun, in near real time.
Replies at speed
A period for reply measured in weeks is awkward where a decision has to be made before a closure on Saturday. So:
- Agree a fast-track route for urgent decisions, with named people and a process for out-of-hours work. Don't rely on it to change the contract. Put any real change to reply periods in writing, and take advice.
- Use proposed instructions sparingly when time is tight, since the Contractor can't act on one until it's actually instructed (65.1).
- Use 61.6 assumptions where the effect is too uncertain to forecast. Correct them if they prove wrong, via 60.1(17).
Testing and commissioning
Rail assets often need to be tested and brought into use in stages before Completion.
- Check the Scope for what counts as Completion. A section brought into use early may be a take-over under 35.2, unless the Scope makes that use an exception, and that can bring 60.1(15) into play. See Completion under NEC.
- Show test dates on the programme, with who attends and what each one relies on.
- Notify tests in time for them to be attended (41.3). Delays by the Supervisor can lead to 60.1(11).
- Consider the interfaces with signalling and other systems, which may be done by Others. Show the sequence on the programme, and the conditions the Scope sets for them.
Records worth extra care
- A log for each access window: planned, granted, start, handback, and any time lost, with reasons
- Competence and access records for individuals where the Scope requires them, since lost time for missing paperwork is usually the Contractor's risk
- A note of who was present when a decision was made on a night shift
The general rules are in keeping a clear audit trail.
Related guides
- Managing NEC Contracts: A Practical Guide
- NEC on Water Projects
- NEC on Energy and Nuclear Projects
- NEC on Building Projects
- An NEC Guide for Consultants
- NEC on Highways Projects
See how this works in practice
Click through Contract Status with sample contracts: raise the notice, reply to it, and watch both sides of one record.
Take the guided tour Book a demo
Get free NEC templates, use the free NEC tools or download free NEC templates.
This guide is general information in our own words, not legal advice. Your contract and its Contract Data always govern. NEC, NEC3 and NEC4 are trade marks of Thomas Telford Ltd; Contract Status is not affiliated with or endorsed by NEC.