My programme now shows we will finish late: do I submit it?

What to do when an updated NEC programme forecasts completion after the Completion Date: honest submission, causes, notices and records.

Programmes and timeScenario3 min read

On this page
  1. The short answer
  2. What to do, step by step
  3. What to record
  4. What not to do
  5. When to get help
  6. Example
  7. Related guides

You have updated the programme and it now shows planned completion after the Completion Date. You are wondering whether to submit it, fix it first, or hold it back. This guide is written from the Contractor's side. A Subcontractor faces the same question with the Contractor as the recipient.

The short answer

Yes, you generally need to submit it. Clause 32.2 requires revised programmes at the intervals stated in the Contract Data and when instructed, and the programme should show the Contractor's honest plan. A planned Completion later than the Completion Date is not one of the four reasons the Project Manager can give for refusing a programme (31.3), and accepting it does not move the Completion Date or waive delay damages. Hiding a forecast late finish does not remove it, and it can undermine your position on compensation events and trust. What matters is that you explain the cause and notify any compensation event in time.

What to do, step by step

  1. Check the forecast is real. Test the logic, calendars and durations first. Many apparent overruns come from a broken link, a wrong constraint or a status date error. Use the clause 31 programme checklist and the P6 schedule health check.
  2. Find the cause. Separate delay caused by compensation events, by the Client or Project Manager, by third parties, and by your own performance. Keep each separate.
  3. Check your notifications. For anything you believe is a compensation event, check whether you have notified it. Clause 61.3 sets an eight-week limit from becoming aware (seven weeks under the NEC4 ECS), subject to its exceptions. Showing an event on a programme is not a notification of it. See missed the eight-week deadline.
  4. Look for recovery. Consider resequencing, extra resource or overlapping work. Only include recovery you will actually carry out and that does not breach the Scope.
  5. Give an early warning. A forecast delay to Completion or a Key Date is exactly the kind of matter early warning exists for (clause 15.1 in NEC4, 16.1 in NEC3). See do I give an early warning?.
  6. Write the narrative. State the forecast Completion, the gap, the causes and the actions. See writing a programme narrative.
  7. Submit through the communication system and chase a reply within the two weeks in clause 31.3.
  8. Keep the dates honest. Do not shorten durations to reach the Completion Date unless you genuinely intend to achieve them.

What to record

  • The programme version showing the late forecast and the version before.
  • The analysis of causes with dates and evidence.
  • Notifications of compensation events and early warnings, with dates.
  • Any instruction to change the order of work.
  • Recovery measures, with who agreed them.

What not to do

  • Do not change logic or durations to force the completion date back without a real basis.
  • Do not delay submitting while you hope things improve.
  • Do not mix claims language into the programme file.
  • Do not assume that a late forecast means you automatically get more time. Time is only added through assessed compensation events.
  • Do not assume it alone creates liability. Delay damages under Option X7 run from the Completion Date, not from planned Completion, so check the provisions in your contract and take advice.

When to get help

Use a planner when the cause is hard to separate, when a prospective delay analysis is needed or when recovery options are unclear. Use a commercial manager or legal adviser when delay damages, termination provisions or disputes are in view. See delay analysis basics and hiring a P6 NEC planner.

Example

A Contractor updates the programme in June. The forecast now shows completion three weeks after the Completion Date. Review shows two weeks come from a compensation event already notified, and one week from slow progress on its own work. It submits the programme with a narrative splitting the three weeks by cause, adds a recovery plan for the self-caused week, and gives an early warning for the remaining risk. It then checks the compensation event is still within its quotation process.

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

Was this useful?