A schedule shows when work should happen. A contract determines what happens when it does not.
Project teams often separate planning from contract administration.
Planners update the program.
Project managers chase milestones.
Commercial teams manage claims.
Legal advisers become involved when delay turns into dispute.
The Week 11 material and supplied AS 4000—1997 show why that separation is risky. Time provisions connect progress obligations, notices of delay, extensions of time, overlapping causes, practical completion, liquidated damages and delay damages.
The strategic lesson is clear:
Time is not merely a scheduling variable. It is a contractual system with financial consequences.
The Strategic Context
A project can be late for many reasons.
The contractor may underperform.
The principal may provide late access or information.
A design change may alter sequencing.
Weather may affect work.
A latent condition may disrupt progress.
Two causes may overlap.
The contract determines which events create entitlement and what procedures must be followed.
The schedule supplies the evidence of effect.
Neither system is sufficient alone.
A contractual entitlement without credible schedule evidence is weak.
A well-maintained program without timely contractual notices may also be insufficient, depending on the agreement.
What Leaders Commonly Misread
The first mistake is treating EOT claims as an end-of-project exercise.
Delay evidence degrades quickly. Logic, resources, contemporaneous decisions and mitigation actions need to be captured while events are occurring.
The second is assuming any delay justifies an extension.
The supplied AS 4000—1997 historically distinguishes qualifying causes and requires evidence of causation and extent.
The third is assuming the contractor should simply accelerate to absorb delay.
Acceleration consumes resources, may reduce productivity and can itself create cost or risk.
The fourth is believing liquidated damages are purely a legal remedy unrelated to schedule governance.
They are tied directly to the contractual completion regime.
The fifth is failing to distinguish the date for practical completion from the actual date of practical completion.
Reframing the Issue
Delay governance should operate through a time-entitlement chain:
Event → Notice → Causation → Program effect → Mitigation → Entitlement → Adjusted completion date → Financial consequence
If one link is weak, the decision becomes harder to defend.
This chain also exposes why good schedule management is a commercial capability.
The program should not simply report slippage. It should help explain:
- which activity was affected;
- whether it was critical;
- what float existed;
- what mitigation occurred;
- what other delay causes overlapped;
- how completion was affected.
Strategic Analysis
The supplied AS 4000—1997 historically requires prompt notice where a party becomes aware of something likely to cause delay and contains a defined EOT claim mechanism. It also addresses overlapping qualifying and non-qualifying causes and gives the superintendent a role in assessment.
Those historical mechanisms should not be assumed current or universally applicable. Contract amendments and current Australian law must be checked. [FACT CHECK REQUIRED]
The management principle remains strong:
Delay should be analysed as causation, not merely variance.
A dashboard showing “14 days behind” is not enough.
Leadership needs to know why, who controls the cause, what the contract says, whether the critical path moved and what decision is required.
Acceleration
The Week 11 teaching material cautions that acceleration should be contractually supported and may require a specific procedure.
This is important.
There are different operational scenarios:
- the contractor accelerates voluntarily to recover its own delay;
- the principal directs acceleration where the contract permits;
- the parties negotiate acceleration following an excusable delay;
- pressure to maintain the original date creates a disputed constructive-acceleration argument.
Current Australian legal treatment must be independently verified before publication as legal guidance. [FACT CHECK REQUIRED]
The executive principle is to avoid informal acceleration.
If additional resources or resequencing are required to preserve a date, the commercial basis should be explicit.
Strategic Analysis: Delay Decisions Should Preserve Optionality
When a project falls behind, leadership often feels pressure to choose immediately between accepting delay and forcing recovery.
That binary framing is too narrow.
Other options may include resequencing, partial access, additional shifts, alternative suppliers, sectional completion, temporary works, scope deferral or negotiated acceleration. Each option carries different cost, risk and contractual consequences.
A hypothetical production-line relocation may be delayed because a supplier cannot deliver one critical component. The project could wait, air-freight a substitute, resequence installation, complete unaffected areas first or commission temporarily around the missing component. A schedule-only discussion may focus on dates. A contract-and-value discussion compares the cost and consequence of each path.
The same principle applies to EOT decisions. Granting an extension can clarify the contractual completion date, but it may also affect liquidated-damages exposure, stakeholder commitments and downstream interfaces. Refusing an extension without sound evidence may preserve a nominal date while increasing dispute risk.
Leadership should therefore preserve optionality until causation and consequences are understood.
The strongest response to delay is not always the fastest physical recovery. It is the recovery strategy that protects the project's highest-value outcome while maintaining a defensible contractual position.
Decision Framework
Use six tests for material delay events.
Event
What happened, and when?
Responsibility
Which party controls or bears the event under the contract?
Criticality
Did it affect the critical path or only consume float?
Evidence
What contemporaneous records support causation and duration?
Mitigation
What reasonable action was taken to reduce delay?
Consequence
Does the event affect EOT, delay damages, liquidated damages or acceleration?
This framework should be applied while the event is current.
From Strategy to Execution
Immediate action: connect the delay register to the live program, correspondence and variation system.
Medium-term capability building: train project controls and commercial teams to analyse delay jointly rather than sequentially.
Long-term strategic positioning: use portfolio delay data to distinguish contractor-performance problems from recurring principal-caused or design-caused delay.
Time governance should improve procurement and project planning, not only resolve claims.
Signals to Monitor
Watch for retrospective EOT claims, programs updated without preserving baseline logic, repeated principal instructions to “recover the time” without commercial treatment, unexplained concurrency, liquidated-damages exposure growing without executive visibility, or delay notices sitting outside the project-controls system.
Another warning sign is a project team that can report schedule variance but cannot explain contractual entitlement.
Questions for the Leadership Team
- What caused the current delay?
- Did it actually affect the contractual completion path?
- Were notices issued when required?
- What mitigation was attempted?
- Are multiple causes overlapping?
- Are we requesting acceleration without defining its commercial basis?
- What financial exposure follows from the current completion forecast?
Closing Perspective
Time is one of the clearest examples of why contract management and project controls cannot be separated.
The schedule describes the delivery system.
The contract assigns consequences.
Strong governance connects them before delay becomes dispute.
Related article: Liquidated Damages or Penalty? Pricing Delay and Breach Risk Before It Happens
Related article: Claims Begin with Evidence, Not Lawyers
Related article: Practical Completion Is a Transfer Point, Not the Finish Line
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.