When EOT Meets Acceleration: What Now?

Delays are expected on construction projects.

Acceleration is often presented as the solution.

But what is less discussed is what happens in between.

The moment when a project moves from entitlement to recovery.

From claiming time to giving it back.

This is where Extension of Time (EOT) meets acceleration.

And this is where risk quietly shifts.

This week, I was working with a contractor on a claim that sat precisely in that space.

The project had experienced a series of delays, some of which were clearly beyond the contractor’s control. At the same time, acceleration had been formally instructed.

Not suggested. Not implied. Instructed.

From a contractual perspective, that distinction matters. Under standard forms such as NZS 3910:2023, instructed acceleration carries a different implication. It opens the door to recovery. It recognises that additional effort is not simply voluntary, but required.

On the surface, this might appear straightforward.

There is delay. There is acceleration. Both have contractual pathways.

But when they occur together, the interaction between them becomes far more complex.

The starting point is usually clear.

A delay event occurs. The contractor identifies the cause, assesses its impact, and establishes entitlement to EOT. That process, if properly followed, determines whether the contractor is entitled to additional time and protection from liquidated damages.

Separately, acceleration is introduced as a response.

The principal requires the programme to be brought back on track. Additional resources are deployed. Sequences are adjusted. Time is compressed.

Individually, both mechanisms are well understood.

But when acceleration is instructed before the full effect of delay is resolved, a different set of questions begins to emerge.

In the case I was reviewing, the delay itself was not in dispute. The events were identifiable. Their impact on the programme could be demonstrated. There was a legitimate basis for EOT.

However, the programme that ultimately existed was no longer the same programme that reflected that delay.

Because acceleration had intervened.

Additional labour had been introduced. Activities had been resequenced. Productivity had increased. The contractor had taken steps—under instruction—to recover time.

This is where the interaction becomes critical.

Because acceleration does not remove delay. It responds to it.

But in doing so, it can alter how that delay is perceived, measured, and ultimately valued.

The first issue is one of visibility.

When acceleration is applied, the apparent impact of delay is reduced. The programme begins to recover. Completion dates may be brought back in line.

From an outcome perspective, the delay appears less significant.

But that does not mean the delay did not occur.

It means effort has been applied to overcome it.

And that effort carries cost.

If the analysis focuses only on the final programme position, without recognising the underlying delay and the effort required to mitigate it, there is a risk that both EOT entitlement and acceleration cost become blurred.

The second issue is one of interaction.

If a contractor is entitled to EOT, that entitlement establishes a new time position. It effectively adjusts the completion date to reflect the delay that was not their responsibility.

Acceleration, when instructed, operates against that position.

But if EOT is not properly assessed or formalised before acceleration is measured, there is a risk that the contractor is effectively accelerating against an unadjusted programme.

In other words, they are recovering time they may not have been required to recover.

This creates a fundamental tension.

Because the contractor may be entitled to additional time, instructed to reduce that time and required to demonstrate both positions simultaneously

The third issue is one of valuation.

Instructed acceleration is not simply about doing more work faster. It is about quantifying the additional cost incurred to achieve that outcome.

That may include:

• increased labour

• extended working hours

• additional plant and resources

• inefficiencies associated with resequencing

However, if the baseline against which acceleration is measured is not clearly defined, particularly in relation to EOT entitlement, then the valuation becomes uncertain.

Are the costs associated with overcoming contractor delay?

Or are they the costs of mitigating principal-caused delay?

Without clarity on entitlement, it becomes difficult to draw that line.

What became clear in this week’s case is that the challenge was not whether EOT or acceleration applied.

Both did.

The challenge was how they interacted.

More specifically, how to ensure that:

• delay entitlement was properly recognised

• acceleration was measured against the correct baseline

• and cost recovery reflected the true effort required

This is not a theoretical issue. It has direct commercial implications.

Because if EOT is understated, the contractor may appear to be responsible for more delay than they actually are.

And if acceleration is not properly linked to that entitlement, the contractor may not recover the full cost of the effort required to meet the programme.

This is where many claims become complicated.

Not because the principles are unclear, but because the sequence in which they are applied is not properly managed.

EOT and acceleration are often treated as parallel processes.

In reality, they are sequentially dependent.

Entitlement should inform the baseline.

The baseline should inform the measurement of acceleration.

When that sequence is reversed, the commercial position becomes distorted.

Across the industry, this situation is becoming more common.

Projects are under increasing pressure to maintain programme. Principals are less willing to accept delay, even when it is not the contractor’s responsibility. Acceleration is used as a tool to manage outcomes.

At the same time, the contractual mechanisms for dealing with delay remain.

And so, both processes are engaged, often at the same time.

But without careful alignment, they do not reinforce each other.

They compete.

The experience this week reinforced a key point:

The complexity is not in identifying delay. Nor is it in implementing acceleration.

The complexity lies in managing the relationship between the two.

Because when EOT meets acceleration, the outcome is not simply a matter of adding time or adding cost. It is a matter of defining what the project should have looked like, and what it took to change that outcome.

This requires more than technical understanding.

It requires clarity of thinking.

When delay occurs, the first question should always be one of entitlement:

• What time is the contractor entitled to?

  
  

Only once that position is understood should acceleration be considered.

• What effort is required to improve on that position?

• And critically, what is the basis upon which that effort will be measured and valued?

In practice, this is not always clean.

Projects move. Decisions are made in real time. Acceleration may be instructed before entitlement is fully resolved.

But that does not remove the need to separate the two conceptually.

Because without that separation, the risk is not just that entitlement is lost.

It is that it is redefined.

When EOT meets acceleration, the contractor is not simply responding to delay.

They are reshaping the outcome of the project. And unless that process is carefully structured, the commercial consequences will not reflect the reality of what has occurred.

Because in construction, the issue is not always whether time was lost.

Sometimes, it is whether the effort to recover it was properly understood.