Liquidated Damages vs. Late Fees in Construction Contracts

Two provisions in construction contracts get conflated in casual conversation but serve different purposes and carry different enforceability risks. Liquidated damages (LDs) are a pre-negotiated dollar amount that the contractor pays the owner for each day the project is late in completing. Late fees are interest-style charges on overdue invoices — the contractor charges them to the owner when payments don't come through on time. They can both show up in the same contract, and each has its own legal framework.

Understanding the difference isn't just semantic. A contract that treats a late-fee clause like an LD clause is asking for an enforceability challenge. An owner trying to apply an LD provision to late payment, or a contractor trying to charge LDs for slow change-order approval, is likely to be disappointed in court.

What Liquidated Damages Actually Are

Liquidated damages are an agreed-upon daily dollar amount payable by the contractor to the owner if the project finishes late. The amount is negotiated into the contract at execution and typically expressed as "$X per calendar day (or working day) of delay beyond the contract completion date, as extended by any owner-caused delays."

LDs exist because proving actual damages from construction delay is hard. If a hotel opens 30 days late, the owner's lost revenue is arguably calculable, but only with significant evidence about occupancy, rate, and market conditions. LDs substitute a pre-agreed number for that litigation. Rather than prove exact damages after the fact, the parties agree up front what a reasonable per-day figure would be.

The Enforceability Test for LDs

Courts enforce LD clauses if two tests are met: the actual damages from delay must be difficult to estimate at contract signing, and the LD amount must be a reasonable forecast of those damages — not a penalty. If the LDs are set so high that they look punitive rather than compensatory, courts may strike them down as an unenforceable penalty.

In practice, this means LD rates are tied to some rational basis. For an office building, LDs are often tied to the owner's carry cost (debt service, insurance, utilities, lost rent) per day of delay. For a retail project, they're tied to projected daily sales loss. For an infrastructure project, they may be tied to the cost of extended owner oversight plus lost asset use. A rate calculated from a credible analysis is defensible; a round number pulled from the air is more vulnerable.

How Excusable Delays Work

LDs apply only to contractor-caused delay. If the delay is owner-caused (late drawings, late owner decisions, differing site conditions, changes to scope), or force majeure (weather, acts of God, pandemics, and similar), the contractor gets a time extension and LDs don't start running until the extended completion date.

This is why schedule impact analysis — time impact analysis, window analysis, as-planned vs. as-built, the various CPM-based techniques — matters so much on a late project. Every day of delay has to be attributed to a party, and the portion attributable to the contractor is the portion exposed to LDs. Fuzzy attribution favors the contractor; precise attribution favors the owner. A delay claim with soft analysis rarely wins an LD argument.

Concurrent Delay and Its Effect

When both parties contributed to delay on the same day — an owner change order is in review while the contractor is also behind on a pour — courts treat concurrent delay variously. Some jurisdictions say the contractor gets time extension with no LDs (neither side is clean on that day). Some say they split. A well-drafted contract addresses concurrent delay explicitly so the default rule doesn't control.

For the finance team on the contractor side, concurrent delay tracking is one of the highest-leverage activities in an LD-exposed project. Documenting owner delays contemporaneously — dated requests for information, change order timelines, responses — builds the evidence to offset LDs.

Mutual Liquidated Damages

Some contracts include reciprocal LDs — the owner pays the contractor for certain types of delays, like late payment-application approvals. These are less common but negotiable in tight markets. The reciprocal clauses typically tie a dollar amount to delayed owner actions that affect the contractor's float, and they keep the LD framework symmetrical rather than one-sided.

Mutual LDs are sometimes worked into contracts for the simple reason that they discipline both sides. Owners who might otherwise slow-walk pay-app review find the carrying cost of their own delay appearing on a statement.

Late Fees on Invoices

Late fees are a different animal. They're interest or interest-like charges on invoices that haven't been paid within the contract's payment terms. A contractor's subcontract or master agreement might say "Payments due 30 days after invoice submission; amounts unpaid after that incur interest at 1.5% per month." That 1.5% per month is a late fee.

Late fees are usually authorized both by contract and by state prompt payment acts. Most state prompt-payment statutes specify a statutory interest rate for payments that miss the deadline — typically prime plus 1% to 2%, though it varies by state. If the contract rate and the statutory rate differ, the higher rate usually applies for public projects; for private projects the contract rate governs.

Unlike LDs, late fees aren't a forecast of damages — they're a time-value-of-money compensation. Courts enforce them routinely at rates within reason (1% to 2% per month is routinely enforced). Above that, some states' usury rules may come into play and the clause gets scrutinized like a high-interest loan.

When Does Each Apply?

The Overlap Between Them

The overlap happens when a contract is late because of owner payment problems. If the owner is slow to pay, the contractor's cash gets tight, supplier relationships strain, and the project slows. The delay is owner-caused, not contractor-caused — so LDs don't apply to the contractor. In fact, the contractor is now owed late fees on unpaid invoices, time extensions to completion, and potentially a claim for extended general conditions.

Documenting this chain — delayed owner payment on date X caused subcontractor Y to slow mobilization, which caused schedule impact Z — is the work that converts an abstract frustration into a legally meaningful claim. Without that documentation, the contractor's argument that the delay was owner-caused has no teeth.

AP Treatment of Each

LDs get deducted from the contractor's final payment. They're typically calculated at substantial completion, reconciled against owner-caused-delay offsets, and netted against the amount otherwise payable on the final pay application. AP has to reflect this on the final payment as a separate line ("LD per Section X.Y, 28 days × $5,000/day = $140,000") rather than silently reducing the payment.

Late fees get added to the invoice balance owed. On the contractor's accounts-receivable side, they accrue as interest income (or discount income in the owner's books). Calculating them precisely requires tracking the exact days each invoice was overdue and applying the correct rate. Many contractors calculate and bill late fees on a rolling basis at month-end rather than as a separate instant charge, which simplifies the reconciliation.

Bottom Line

Liquidated damages compensate owners for project delay and are enforceable when they reflect a reasonable forecast of actual damages. Late fees compensate contractors for delayed invoice payment and are enforceable at contract or statutory rates. They aren't interchangeable: an owner trying to withhold payment as "late-fee like" under an LD clause is on weak ground, and a contractor trying to apply LDs to slow invoice approvals is off the edge of the contract. Understanding each — and drafting contracts that handle them distinctly — avoids the category-error disputes that eat up legal fees on projects that should have closed out cleanly.