Skip to content
P6 Schedule Analyticsby PlanAssure

Contract

NEC4 contract

Key Dates, submissions, the EW, PMI and CE registers, CE impact and clause 31/32 checks.

The NEC4 Contract tab keeps an Engineering and Construction Contract's records with the programme, in five views: Contract & Key Dates, Submissions, EW · PMI · CE, CE impact and Programme compliance. It's included in Team and Enterprise plans.

NEC4 Completion and Key Dates, each mapped to the activity that achieves it, with the margin in every loaded update.
Completion and Key Dates · demo programme

Contract & Key Dates#

Enter the Main Option, the starting date, the original and current Completion Date, the revision interval and the periods for replying to a programme. Map Completion, each Key Date, Sectional Completion and access date to the activity that achieves it, and each is shown beside the date P6 shows for it, in the open programme, the Accepted Programme and every loaded update, with the margin in calendar and working days. Nothing here moves the Completion Date: it changes when you enter it.

Time risk allowances (clause 31.2) are found by their names, or by the contract's own convention: an activity code value, a user defined field or a name pattern. For each Key Date and Completion the tab lists the allowances on the logic leading to it, their total and what's left. They're hatched in the Gantt.

Submissions#

Each loaded programme is a submission: when it was submitted, the Project Manager's reply and the reasons for not accepting it, as 31.3 requires them. A reply is due the reply period after submission; the Accepted Programme at any date is the latest accepted on or before it. A gap between submissions longer than the revision interval is flagged (32.2).

Early warnings, instructions and compensation events#

Registers for early warnings, Project Manager's instructions and compensation events, with owners, the dates each process turns on, the activities affected, and typed links between records seen from both ends. Notice periods are rules you set: a clock starts on one of a record's dates and stops when another is filled in. ECC's own (61.3, 61.4 and 62.3) can be added as a starting point. What is due lists every running clock against today.

The NEC4 registers: early warnings, instructions and compensation events, with the funnel from early warning to outcome.
The registers and the funnel

Above the registers, a funnel shows where each compensation event came from (an early warning, an instruction or notified directly) and how far it has got, with a donut of records by status and the clocks running: overdue, due within 14 days, or later. Highlight an event and its activities are highlighted in the Gantt and on the time-chainage chart.

CE impact#

For a compensation event, choose the programme to assess against (the Accepted Programme by default), the dividing date, the new activities with their links into the programme, and any changed remaining durations. The programme is recalculated with and without the fragnet; the difference in planned Completion and each Key Date is the result, in working days. Another event touching the same work is warned of, so the same delay isn't counted twice.

Programme compliance#

The compliance view assesses the programme against what clause 31.2 says it must show, the grounds in 31.3 for not accepting it, and the revised-programme requirements of 32.1 and 32.2.

Setting it up#

Enter from Contract Data part one:

  • the Completion Date, so planned Completion and terminal float can be measured;
  • the Key Dates, so each can be checked for a milestone;
  • the revision interval, so clause 32.2 can be checked when you've loaded successive programmes.

These are kept with the schedule, the tab reopens with them, and the Excel export assesses against them.

How items are judged#

Each item passes, fails, doesn't apply, or is marked check by hand with what to look for.

  • The programme as it stands now. Work under way counts at its forecast finish, not its frozen planned finish.
  • Practicable plans looks at hard constraints on remaining work and at links into open work that progress has broken. Out-of-sequence working that has since finished is as-built history, so it doesn't count.
  • Realistic plans checks the file was rescheduled after its last change: stored dates satisfy its own logic and keep unfinished work after the data date.
  • Wording. Some items look for activity names that mean what the clause means: an acceptance by someone else, not the Contractor's own review; information received from Others, not the Contractor's own design; a named time risk allowance, not an allowance of time for a task. Where nothing matches, the item is to be checked by hand, not failed, because a name search can't prove absence.
NEC4 programme compliance: clause 31 and 32 items marked pass, fail or check by hand.
NEC4 compliance · demo programme Rev 6

The items#

Clause 31.2: what the programme shows

  • The starting date, access dates and Key Dates.
  • The Completion Date and planned Completion, and the terminal float between them.
  • The order and timing of the operations, and of the work of the Client and Others.
  • Provisions for float and for time risk allowances.
  • The dates the Contractor needs access to parts of the Site, acceptances, Plant and Materials provided by the Client, and information from Others.
  • A statement of how the work is done, from the resources.
  • Health and safety requirements and contract procedures, and other information the Scope requires: to check by hand.

Clause 31.3: grounds for non-acceptance

  • Plans shown are practicable.
  • It shows the information the contract requires.
  • It represents the Contractor's plans realistically.
  • It complies with the Scope: to check by hand.

Clause 32.1: revised programmes

  • Actual progress on each operation, and its effect on the timing of the remaining work.
  • The effects of compensation events.
  • How delays and notified Defects will be dealt with.
  • Other changes proposed to the Accepted Programme: activities added and removed, and re-baselined dates, when a previous programme is loaded.

Clause 32.2: the revision interval

  • Revised programmes at no longer interval than the Contract Data states, checked across the data dates of the programmes you've loaded.

On the demo programme#

The demo passes 16 items, fails 3 and leaves 6 to check by hand. Its planned Completion is after the Completion Date, which is a clause 31.3 ground on its own: the programme shows no achievable Completion until it's recovered, or the Completion Date moves through implemented compensation events.