When should a contract include liquidated damages?

• A. When the contract requires rapid execution even for minor delays.
• B. When it’s difficult to measure actual damages for delays or nonperformance and a fair pre-estimate exists.
• C. Only for projects with critical path activities.
• D. In almost all cases regardless of damages.

Answer: (B)

Liquidated damages are a pre-set amount agreed in advance to compensate for a breach when calculating actual losses would be difficult. The key idea is to provide a predictable remedy and avoid disputes about proving every loss, but only if that pre-estimate is fair and reflects likely damages at the time the contract is formed.

This is why the best choice describes using liquidated damages when measuring actual damages for delays or nonperformance is hard, and a fair pre-estimate exists. In that situation, the clause helps both sides by avoiding uncertain, ongoing litigation over damages and by giving a clear, enforceable remedy.

Other scenarios aren’t the defining justification. For example, requiring swift completion or focusing only on projects with certain activities aren’t sufficient conditions—liquidated damages should tie to a genuine forecast of losses, not just speed requirements or a narrow project type. And using them in almost all cases regardless of damages would be inappropriate or potentially unenforceable where actual damages are easy to quantify or where penalties would be deemed unfair.