Liquidated damages are most useful when they make the consequences of delay predictable, not when they are used to frighten a contractor into finishing.
The Week 12 notes describe liquidated and ascertained damages as a predetermined amount payable following a specified breach, particularly late completion. They emphasise three source propositions: LAD should reflect anticipated loss, should not operate as a penalty and can provide certainty to both employer and contractor.
The supplied 1999 LAD paper by Tony Ma and Patrick Lam develops the same commercial rationale. It argues that a pre-agreed delay amount can compensate the employer, give the contractor visibility of exposure and avoid later disputes about actual loss.
Those legal formulations are historical and should not be treated as a complete statement of current Australian penalty law. [FACT CHECK REQUIRED]
The strategic idea is still strong: LAD is a risk-pricing mechanism.
The Strategic Context
Late completion creates uncertainty.
The principal may suffer lost revenue, additional financing cost, extended project-management cost, temporary accommodation, operational disruption or delayed public benefit.
The contractor faces uncertainty about the scale of that exposure.
Without a pre-agreed mechanism, the parties may need to prove and debate actual loss after delay occurs.
LAD attempts to convert some of that uncertainty into an agreed price of late completion.
This can improve decision-making before the contract is signed.
The contractor can price the risk.
The principal can understand the commercial consequence.
The project team can connect schedule exposure to financial exposure.
What Leaders Commonly Misread
The first mistake is setting LAD as a negotiating weapon.
A deliberately oppressive amount may create legal risk and almost certainly creates pricing consequences.
The second is selecting a percentage because it is “standard”.
The Week 12 LAD paper includes historical rules of thumb for smaller projects, but it also demonstrates why loss differs materially by asset type. A hotel, manufacturing facility and public infrastructure project do not generate the same consequences from delay. filecite-style source omitted in artifact by design
The third is assuming LAD removes the need to manage time.
It does not.
A principal that causes delay or fails to administer EOT properly may weaken its own position.
The fourth is assuming LAD always represents the principal's maximum possible delay exposure or automatically replaces every other remedy.
That depends on the contract and current law. [FACT CHECK REQUIRED]
Reframing the Issue
LAD should be designed around this question:
What reasonably foreseeable economic consequence does late completion create for this specific asset and business model?
That requires understanding the project as an investment, not merely a construction contract.
For a rental property, delay may defer rent.
For a manufacturing facility, delay may defer productive capacity.
For infrastructure, loss may appear through extended project cost, service disruption or delayed public benefit rather than direct revenue.
For a sale development, timing may affect settlement or financing.
The source paper uses historical formulas to illustrate these differences. Those formulas should not be republished as universal current methods. [FACT CHECK REQUIRED]
Strategic Analysis: LAD Is a Two-Sided Risk Allocation
LAD is often discussed as protection for the principal.
It also gives the contractor information.
A known daily exposure can be priced, mitigated and governed.
A vague future claim for actual damages may be much harder to evaluate.
This means an intelligently designed LAD clause can reduce transaction cost for both parties.
But the amount affects behaviour.
If LAD is unrealistically low, it may not reflect material delay consequence.
If it is unrealistically high, tenderers may add risk premiums, reduce appetite or challenge the provision.
The best amount is therefore not the highest defensible amount.
It is the amount that accurately supports the agreed allocation of delay risk.
Operability Matters
The Week 12 notes also stress that an LAD clause needs careful drafting, definite dates and compliance with contractual procedures.
That is important because LAD is not merely a number.
It is a system connecting:
- contractual completion date;
- EOT mechanism;
- rate of damages;
- certification or deduction process;
- waiver considerations;
- actual administration.
If the date is uncertain, the EOT process is broken or the principal has caused unaddressed delay, the LAD mechanism may not operate as intended.
Current AS 4000 procedures and current Australian law must be verified before publication as legal guidance. [FACT CHECK REQUIRED]
Strategic Analysis: LAD Should Align with Governance, Not Replace It
A well-calculated LAD rate can still fail to create value if project governance is weak.
If EOT decisions are delayed, if completion dates are not controlled or if principal-caused delay is not recorded, the project may rely on LAD as leverage rather than as a clear contractual consequence.
This creates adversarial behaviour and weakens the very certainty LAD is intended to provide.
Leaders should therefore connect LAD governance to three live controls:
- the current contractual completion date;
- approved and pending EOTs;
- the forecast date of practical completion.
Together, these show both legal exposure and operational trajectory.
The board or executive team does not need clause-level detail every month, but it should understand whether delay exposure is increasing, whether the date remains defensible and whether management action can still change the outcome.
LAD works best when it is the final consequence of a disciplined time system, not the first response to schedule pressure.
Decision Framework
Use the LAD Integrity Test.
1. Loss logic
What loss pathway is the rate intended to approximate?
2. Evidence
What business or project data supports the estimate?
3. Proportionality
Does the amount reflect consequence rather than punishment?
4. Date integrity
Is there a clear and enforceable completion-date system?
5. Administration
Can the project comply with the required notice, certification and deduction process?
6. Market effect
How will tenderers price the exposure?
A sound LAD design should pass all six tests.
From Strategy to Execution
Immediate action: require the procurement team to document the commercial basis for LAD before tender release.
Medium-term capability building: link LAD calculations to the business case and project benefits rather than selecting a standard daily rate.
Long-term strategic positioning: review actual delay outcomes against pre-tender assumptions so future LAD settings become evidence-based.
Signals to Monitor
Watch for LAD inserted without supporting calculation, rates copied from unrelated projects, contracts with LAD but weak EOT mechanisms, project teams threatening LAD before delay entitlement is assessed, or tenderers pricing large risk allowances because the amount is disproportionate.
Another warning sign is a board or executive team unable to explain what economic loss the LAD amount represents.
Questions for the Leadership Team
- What loss is this LAD rate intended to approximate?
- What evidence supports it?
- Is it proportionate to the asset's economics?
- Can principal-caused delay be administered through the EOT mechanism?
- Are we using LAD as certainty or as pressure?
- How will the rate affect tender pricing?
- What should future projects learn from actual delay outcomes?
Closing Perspective
Liquidated damages should convert uncertainty into a rational commercial position.
They work best when they are tied to real consequence, supported by evidence and integrated with a credible completion-date system.
Punishment is not the objective.
Predictability is.
Related article: How Leaders Should Set Liquidated Damages Without Guessing
Related article: When Time Goes at Large: How the Completion Date Can Lose Its Commercial Force
Related article: Liquidated Damages or Penalty? Pricing Delay and Breach Risk Before It Happens
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.