Working under NEC on rail projects: possessions, Key Dates and commissioning

How NEC treats rail access windows, lost possessions, urgent decisions, testing and commissioning, with a worked example and the records to keep.

NEC by sector4 min read

On this page
  1. In plain English
  2. Five ways a window can appear in the contract
  3. Worked example
  4. Deciding at speed
  5. Testing and commissioning
  6. Records to guard carefully
  7. Related guides

Railway programmes are built around fixed windows of access. Miss one and the next may be many weeks off, so a minor slip can turn into a major delay. For that reason your programme, access dates, Key Dates (dates by which a stated condition must be met) and speed of decision matter more here than on most work. The terms are the NEC4 Engineering and Construction Contract (ECC), usually with extensive client-specific rules in the Scope and Z clauses. This page does not describe those, so read your own first.

In plain English

NEC has no special rule for a possession. It handles closed access windows through ordinary tools, and you need to know which tool your contract uses for each one, because that decides who pays when a window is lost.

Five ways a window can appear in the contract

  • An access date in the Contract Data. It sets when each part of the Site becomes available. Access is late only if it is past the later of that date and the date on the Accepted Programme (60.1(2)).
  • A constraint in the Scope. It sets working times and conditions, including who applies for them. If the Project Manager (the person the Client appoints to run the contract day to day) changes it by instruction, 60.1(1) is the route. If you miss it through your own fault, the cost is yours.
  • An item on the Accepted Programme. You show when you need access (31.2). It matters for 60.1(2) and for measuring delay.
  • A Key Date. It sets a condition to be met before a date, such as being ready for a commissioning slot. Recovery of cost may be possible under 25.3.
  • The Client cancelling. An instruction to stop or not to start falls under 60.1(4).

Settle at the start how a cancelled or overrunning window will be treated, and put it on your first four weeks list. See Key Dates and access dates.

Worked example

A fictional signalling cabinet renewal. The Accepted Programme relies on a night possession in week 12, and the next suitable one is a month later.

  • Week 10: the contractor spots that a track-patrol contractor is also booked for the same night. It raises an early warning.
  • Early warning meeting: the parties consider swapping to a shorter scope of work, or moving to a mid-week slot.
  • Week 11: the possession is withdrawn. The Project Manager (the person the Client appoints to run the contract day to day) works out why. If another contractor of the Client overran outside the Scope's stated times, 60.1(5) is the likely route. If access was simply not provided, 60.1(2). If the Project Manager ordered the change, 60.1(1) or 60.1(4).
  • Quotation: it prices the delay to planned Completion, the idle and rebooked labour, and an alternative that uses shorter mid-week shifts.

If the same slot had been lost because the contractor's own crane failed, the loss would stay with the contractor. There is probably no compensation event, but delay damages (with Option X7) or extra cost against a Key Date may follow. In either case, write down what caused the loss while it is fresh.

Deciding at speed

A reply period measured in weeks is no use when a decision is needed before Saturday night.

  • Agree a fast route for urgent decisions, with named people and an out-of-hours process. That does not alter the contract, so put any real change to reply periods in writing and take advice.
  • Be careful with proposed instructions when time is tight: you cannot act on one until it is actually instructed (65.1).
  • Use assumptions in a quotation (61.6) where the effect is too uncertain to forecast, and correct them through 60.1(17) if they prove wrong.

Testing and commissioning

Rail assets are usually proved in stages before Completion, so plan for that.

  • Look in the Scope for the definition of Completion. Bringing a section into use early can amount to a take-over (35.2) unless the Scope carves that out, and that engages 60.1(15). See completion and take-over.
  • Put every test on the programme with the people who must attend and what each test needs first.
  • Give enough notice that the Supervisor can attend (41.3). If the Supervisor is late, 60.1(11) can apply.
  • Signalling and telecoms interfaces are often done by Others. Show their sequence and the Scope's conditions on your programme.

Records to guard carefully

  • A log per possession: what was booked, what was granted, start time, handback time, hours lost and reasons.
  • Competence and access passes for individual workers where the Scope demands them. Time lost to missing paperwork is normally the contractor's.
  • A note of who was present for each night-shift decision.

The wider habits are in keeping records under NEC.

This guide is general information, not legal advice. Check it against your contract.

Was this useful?