Rates With Reasons: Making Liquidated Damages Defensible Before Delay Arrives
Photo: construction programme delay cost schedule documents, via img.freepik.com
Liquidated damages are often drafted as a single rate and a cap, then left to be argued about when the programme slips. That is a commercial choice, not a legal inevitability. A rate that cannot be connected to a genuine pre-estimate of delay cost is vulnerable. A schedule assembled after the event looks like a calculation of convenience rather than a forecast of loss.
The clause is not the evidence
The contract may contain a liquidated damages clause, but the clause does not prove that the rate is defensible. In UK law, the penalty rule asks whether the clause imposes a detriment out of all proportion to the innocent party's legitimate interest. The Supreme Court's decision in Cavendish Square Holding BV v Talal El Makdessi (2015) reframed that test, but it did not remove the need for commercial justification. A credible pre-estimate is part of that justification.
Build the schedule before delay
The schedule should be prepared when the contract is formed, not when the delay occurs. It should state the basis of the rate, the assumptions behind it and the period over which it is expected to apply. If the rate is expressed per day or per week, show how it was built up. If the cap is expressed as a sum or a percentage, show why it is proportionate to the likely exposure. The schedule should be read as a commercial forecast, not as a penalty.
Separate the cost components
A delay cost schedule is more persuasive when its components are visible. Depending on the project, the components may include loss of use, rent, financing costs, additional professional fees, head office overhead and lost profit. Avoid double counting. If a cost would have been avoided during the delay, record that. If mitigation reduces the loss, record that too. The aim is not to maximise the number. It is to produce a number that can be explained.
Test the cap
A cap should have a reason. It may reflect the expected delay period, the value of the affected facility or the level of risk accepted by the parties. Check whether the cap works with sectional completion, partial possession and extension of time provisions. Consider what happens if the delay is longer than the cap period. A cap that bears no relation to the likely loss is easier to challenge than one that is tied to a stated assumption.
Keep mitigation records
Mitigation records matter even where liquidated damages are agreed. They show that the innocent party acted commercially and that the delay was not simply allowed to run. Keep records of resequencing, acceleration, additional resources, alternative arrangements and any rejected mitigation. These records also help to align the delay cost schedule with the programme and the payment evidence.
Align the documents
The schedule should use the same dates and periods as the programme, the delay notices and the payment records. If the programme shows a delay from 1 March to 30 April, the schedule should not use a different window without explanation. If payment records show additional costs in a later period, explain the link. Consistency is not a cosmetic point. It is what makes the schedule readable as evidence.
Own the schedule
Give the schedule an owner, a version and a review date. Keep the assumptions under review as the project develops, but do not rewrite history to increase the rate. If the rate changes, record why and when. The commercial value of the schedule lies in its discipline: a rate with reasons, a cap with a basis and a record that can be read alongside the programme. That is a better position than a number that only appears after the delay.