Delay Damages and the Data Migration
NorthBank contracts with Alpha Tech to migrate its core banking data for $2.4 million, with completion due 1 March. Clause 12 provides: 'If Alpha fails to complete by the due date, it shall pay $50,000 per day of delay, up to 40% of the contract price, as agreed damages.' Clause 9 excludes liability for 'indirect or consequential loss, including loss of profit'. NorthBank fails to provide the required data-mapping file until 20 February; Alpha had warned that this would delay completion. Alpha completes on 31 March, 30 days late. NorthBank suffers a $1.2 million regulatory fine because it could not file its quarterly return on time, and loses $3 million in expected customer revenue. NorthBank refuses to pay the outstanding $600,000 contract price and claims the delay damages plus the fine and lost revenue. Alpha argues clause 12 is a penalty, clause 9 excludes the fine and lost revenue, and NorthBank's own delay excuses Alpha.
1. Is clause 12 enforceable as a liquidated damages clause or is it a penalty? Apply the genuine pre-estimate and legitimate-interest test.
Read the worked answer
Issue. Whether clause 12 is a penalty.
Rule. The modern test is whether the clause imposes a detriment out of all proportion to the innocent party's legitimate interest in performance, not merely whether it exceeds actual loss. A genuine pre-estimate is evidence but not decisive. Courts uphold clauses that protect a legitimate interest and are not extravagant.
Application. The contract price is $2.4m. $50,000 per day is about 2.08% of the price per day. For 30 days the formula gives $1.5m, but the cap is 40% ($960,000). NorthBank's actual loss includes a $1.2m regulatory fine, so the capped sum is not obviously disproportionate; it is less than the fine alone. Alpha's delay also caused operational disruption. The daily rate is high, but the cap and commercial context make it defensible as a genuine attempt to allocate risk. If Alpha can show that the rate was arbitrary and designed to coerce, the clause could be struck down; the burden is on Alpha.
Conclusion. Clause 12 is likely enforceable as liquidated damages, capped at $960,000, not a penalty.
2. Does clause 9 exclude the regulatory fine and lost customer revenue? Distinguish direct from consequential loss.
Read the worked answer
Issue. Whether clause 9 excludes the regulatory fine and lost customer revenue.
Rule. An exclusion clause is construed contra proferentem and against the background of the contract. 'Indirect or consequential loss' generally covers losses that are not the natural and direct result of the breach, or that arise from a subsequent transaction. Loss of profit expressly excluded is clear.
Application. The $1.2m regulatory fine arose because NorthBank could not file its quarterly return on time. That is an immediate and foreseeable consequence of late data migration, not a loss of profit. It is therefore arguably a direct loss, and clause 9 does not exclude it. The $3m lost customer revenue is expressly 'loss of profit' and is consequential; it falls within the exclusion. The clause does not exclude direct loss generally, only indirect or consequential loss and loss of profit. Alpha cannot rely on clause 9 to exclude the fine.
Conclusion. The fine is recoverable, subject to causation and mitigation; the lost revenue is excluded. If the fine is characterised as a consequence of NorthBank's own regulatory failure, Alpha may argue it is indirect, but on these facts it is direct.
3. What effect does NorthBank's failure to provide the data-mapping file have on Alpha's liability and on the delay damages?
Read the worked answer
Issue. Effect of NorthBank's failure to provide the data-mapping file.
Rule. A party cannot insist on a contractual completion date if it has prevented the other party from completing. The prevention principle may set time at large or entitle the contractor to an extension. Delay damages are not payable for delay caused by the employer.
Application. NorthBank failed to provide the file until 20 February, and Alpha warned that this would delay completion. The due date was 1 March. Alpha completed on 31 March, 30 days late. NorthBank's breach caused at least part of the delay. The court should apportion: the period attributable to NorthBank, roughly 20 February to 1 March, should not attract delay damages. If the contract has an extension-of-time mechanism, Alpha should have given notice; if not, the prevention principle may excuse the whole delay. Alpha continued performance, so it did not repudiate.
Conclusion. NorthBank's delay reduces or eliminates clause 12 damages for the affected period. The court should calculate the delay caused by NorthBank and award damages only for the remainder; if the whole delay was caused by NorthBank, the delay claim fails. The contract price remains payable, subject to set-off.