Construction Liquidated Damages: What They Are and How to Defend Against Them

A liquidated damages (LD) clause is a contract provision that fixes the amount of damages owed by the contractor for each day the project is completed beyond the contractual completion date. Rather than requiring the owner to prove actual delay damages in litigation, the parties agree in advance to a daily rate — liquidating (settling) the uncertainty of what delay costs in advance. LD clauses are among the most significant financial provisions in any construction contract, and they are also among the most frequently contested. A contractor facing LD exposure on a major delay needs to understand the legal enforceability of the clause, what defenses are available, and how the delay analysis is conducted to determine how many LD days actually apply.

What Liquidated Damages Are — and Are Not

The core purpose of an LD clause is to provide certainty. When a hospital can't open on schedule, the owner's actual damages — lost revenue, extended staff costs, patient diversion, carrying costs on construction financing — are real but difficult to prove and quantify in litigation. The LD clause replaces that proof requirement with an agreed daily amount. Both parties know from day one what a delay day costs.

How LD Rates Are Set

Owners (and their attorneys) set LD rates by estimating the daily cost of not having the building available for its intended use. Common components of an LD rate calculation:

Typical LD rates in commercial construction range from $1,000/day on small projects to $50,000+/day on large healthcare or mission-critical facilities. The rate is stated in the contract and becomes the daily exposure from the day after the contractual completion date until substantial completion (or the date the owner takes beneficial occupancy).

The Critical Path and Delay Causation

An LD clause does not automatically apply to every day the project runs late. The owner must establish that the contractor's delay caused the critical path to slip — meaning that but for the contractor's delay, the project would have completed on time. This requires a delay analysis:

• • As-planned vs. as-built analysis: Compare the original CPM schedule (as-planned) against the actual sequence and timing of work (as-built). Identify where delays occurred, how long they lasted, and whether they were on the critical path.
• • Impacted as-planned: Start from the as-planned schedule and insert actual delay events to show their impact on the completion date.
• • Time impact analysis (TIA): The prospective method — used during construction to evaluate the schedule impact of specific events as they occur. TIAs submitted with time extension requests are the primary contemporaneous record of delay causation.
• • Windows analysis: Divide the project into discrete time windows and analyze delay causation within each. Most rigorous but most expensive — typically used in arbitration or litigation on large projects.

The burden of proof typically rests with the owner to establish that the contractor's delay caused a specific number of days of critical path delay. The contractor then bears the burden of establishing excusable or compensable delays that offset LD exposure.

Time Extension Defenses

The primary defense against LD claims is demonstrating that the contractor is entitled to a time extension — additional contract days that reduce or eliminate the LD period. Time extensions fall into two categories:

Concurrent Delay

Concurrent delay occurs when both a contractor-caused delay and an owner-caused delay affect the critical path during the same time period. The legal treatment of concurrent delay varies by jurisdiction and contract language:

• • Traditional US rule: When contractor and owner delays are truly concurrent (both independently would have caused the same delay), the contractor gets a time extension but no additional compensation — and the owner cannot assess LDs for that period. Neither party is compensated for a period where both contributed to the delay.
• • Apportionment approach: Some jurisdictions and contracts apportion concurrent delay — allocating LD exposure and time extensions in proportion to each party's contribution to the delay. This requires a granular delay analysis that isolates the cause and duration of each contributing delay event.
• • Proving concurrency: The contractor bears the burden of proving owner-caused concurrent delay. This requires the same delay analysis framework — critical path, as-built records, contemporaneous documentation of owner actions. Unsubstantiated claims of concurrent delay rarely succeed.

Force Majeure and COVID-Era Precedent

Force majeure clauses excuse delay caused by events entirely outside both parties' control — wars, government shutdowns, pandemics, natural disasters. Construction contracts typically include force majeure as a category of excusable delay. The COVID-19 pandemic generated substantial litigation over what constitutes a force majeure event in construction, with courts generally requiring:

• • The event must be truly unforeseeable at contract execution — not just difficult or expensive.
• • The event must directly cause the delay, not merely increase the cost of performance.
• • The contractor must have mitigated delays where possible — a force majeure claim fails if the contractor could have worked around the event with reasonable effort.
• • Notice requirements still apply — most contracts require prompt written notice of force majeure events.

No-Damage-for-Delay Clauses

Many public contracts and some private contracts include a no-damage-for-delay (NDFD) clause — a provision stating that the contractor's sole remedy for owner-caused delay is a time extension, with no entitlement to additional compensation for extended general conditions, lost productivity, or other delay costs. NDFD clauses are controversial and their enforceability varies by state:

• • Several states (California, Oregon, Virginia) have statutes limiting or voiding NDFD clauses on public projects.
• • Courts in most states will enforce NDFD clauses but recognize exceptions for active interference, fraud, abandonment, and delays so extensive they were unforeseeable at contract execution.
• • On private work, NDFD clauses are generally enforceable but should be flagged and negotiated before signing — they shift significant financial risk to the contractor for owner-caused delays.

Negotiating LD Provisions Before Signing

The best time to address LD exposure is before contract execution. Strategies:

• Cap total LD exposure. Negotiate a cap on total LDs — often 5–15% of the contract value. Without a cap, LDs can theoretically exceed the contract value on a long delay. Most sophisticated owners will accept a cap.
• Negotiate the LD rate against a documented justification. Request the owner's basis for the daily rate. If the rate appears disproportionate to actual harm, push back with your own analysis. A rate set with documentation is also harder to challenge in court — which benefits both parties.
• Define "substantial completion" precisely. LDs typically stop accruing at substantial completion, not final completion. Ensure the contract defines substantial completion clearly — tied to certificate of occupancy or beneficial occupancy, not to punch list completion. An ambiguous substantial completion definition can extend LD exposure by months.
• Include early completion bonuses. If the owner is requesting a compressed schedule with LD exposure, negotiate a mirror bonus for early delivery — this aligns incentives and provides upside for schedule performance.
• Build schedule float into the CPM and protect it. Owner-consumed float is a common source of LD disputes. Negotiate language that the schedule float belongs to the project (not exclusively to either party) and that owner-directed changes affecting float are compensable delays.