Why Your Programme Is One of Your Strongest Commercial Tools

When I'm reviewing a project, one of the first things I ask to see is the programme. It helps me understand the scope of the works, how the project is intended to be delivered, and any potential exposure to Liquidated Damages (read alongside the contract).

It also gives me a clear picture of how the project is being managed and, more importantly, whether the contractor can demonstrate the impact if something changes on site. And let's be honest, there's a good chance it will.

One of the biggest challenges I've seen is that programmes are often produced simply to satisfy a contractual requirement, rather than being used as a strategic tool to manage the project. The reality is that when delays occur, the programme suddenly becomes one of the most important commercial documents on the job.

If it hasn't been updated, or no longer reflects what's happening on site, demonstrating entitlement to an Extension of Time becomes much more difficult.

Your Programme Is More Than a Planning Tool

A programme shouldn't just tell you what happens next. It should explain how the project is intended to be delivered. It should identify the sequence of works, the relationship between activities, key milestones, resource requirements and, most importantly, what is driving the completion date. Better to think of it as a commercial tool.

When a delay occurs, it becomes the evidence that demonstrates whether the event has actually affected completion. Without that evidence, you're relying on opinion rather than fact.

Understanding the Language of Delay

One advantage for project teams is understanding the terminology. It immediately puts you in a much stronger position.

These aren't just planning terms. They're the language used when discussing Extensions of Time, delay analysis and, ultimately, Liquidated Damages.

Critical Path

The critical path is the sequence of activities that determines the earliest possible completion of the project. A delay to an activity on the critical path is likely to delay Completion unless that delay is mitigated or recovered.¹

The important point is this. Not every delay affects completion.

When discussing an Extension of Time, the real question isn't:

"Did something get delayed?"

It's:

"Did that delay affect the critical path and delay Completion?"

Understanding what sits on the critical path helps you focus on what really matters.

Float

Float is the amount of time an activity can be delayed without affecting the project's Completion Date.¹

Think of it as flexibility within the programme rather than spare time. The Society of Construction Law (SCL) Delay and Disruption Protocol recognises that ownership of float has long been debated. Unless the contract expressly provides otherwise, the Protocol explains that an Employer Risk Event will generally only result in an Extension of Time once any remaining total float on the affected critical path has been exhausted.²

That might be one reason some contractors choose not to expose all of their internal planning contingency within the published programme. The published programme should always accurately reflect how the project will be delivered, but many contractors also maintain internal planning resilience to help manage risk.

Milestones

Not every important date is the Completion Date. Projects often include procurement milestones, sectional completions, commissioning activities and client handovers. Missing one of these dates doesn't always delay Completion immediately, but it can quickly create pressure elsewhere within the programme.

Understanding these milestones allows project teams to identify risks early and make informed commercial decisions before small issues develop into major delays.

Concurrent Delay

The SCL Delay and Disruption Protocol describes true concurrent delay as two delay events occurring at the same time, one an Employer Risk Event and the other a Contractor Risk Event, where both are effective causes of Delay to Completion.³

From my experience, many situations are labelled as concurrent delay when they simply aren't. That's why maintaining an accurate programme and keeping good records throughout the project is so important.

Extension of Time

An Extension of Time is the contractual mechanism that adjusts the Completion Date where a qualifying delay event has caused Delay to Completion. Its purpose is to protect the contractor from liability for Liquidated Damages where appropriate.⁴

An Extension of Time isn't awarded simply because something changed on site. The key question is whether a qualifying delay event caused Delay to Completion. That's where your programme becomes invaluable.

Your programme, site records, progress updates and contractual notices all work together to demonstrate the impact of the delaying event. It's not enough to say the project was delayed. You need to demonstrate how and why Completion was affected.

Most construction contracts identify specific events that may entitle a contractor to additional time. The exact events depend on the form of contract being used, but they are generally events that sit outside the contractor's control and may justify an adjustment to the Completion Date.

Liquidated Damages

Liquidated Damages are pre-agreed damages that may become payable where the contractor fails to complete the works by the contractual Completion Date and is not entitled to an Extension of Time.⁵

Liquidated Damages are often where the commercial consequences of poor programme management become apparent.

If Completion is delayed and you can't demonstrate entitlement to an Extension of Time, you may become liable for Liquidated Damages under the contract.

From my experience, contractors rarely lose Extension of Time claims because the delay didn't happen. More often, they lose because they can't demonstrate the impact of that delay on the programme. That's why I always encourage contractors to see their programme as much more than a planning exercise.

Some Considerations

Don't produce a programme just because the contract says you should.

Use it.

Review it.

Challenge it.

Update it.

Record progress against it.

And when things change, assess the impact straight away.

References

1. Society of Construction Law (2017). Delay and Disruption Protocol (2nd Edition) – principles relating to Critical Path, Float and Delay to Completion.

2. Society of Construction Law (2017). Delay and Disruption Protocol (2nd Edition), Core Principle 8 – Float as it relates to time.

3. Society of Construction Law (2017). Delay and Disruption Protocol (2nd Edition), Section 10 – True Concurrent Delay.

4. Society of Construction Law (2017). Delay and Disruption Protocol (2nd Edition) – principles relating to Extensions of Time and Delay to Completion.

5. Society of Construction Law (2017). Delay and Disruption Protocol (2nd Edition) and general principles of construction contract administration regarding Completion Dates and Liquidated Damages.