Owners do not hire contractors to be late, and contractors do not plan to miss milestones. Yet schedules slip, design details change, weather turns ugly, and the supply chain decides to take a nap just when you need switchgear. When a project runs long, the costs are very real: extended general conditions, lost rent, missed seasonal operations, and lenders who stop being patient. That is why most construction contracts tie time to money through liquidated damages and why public and sophisticated private owners insist on bonding to ensure performance and payment. Knowing how these two instruments work, and where they interact, can be the difference between a controlled risk and a project-ending dispute.
Liquidated damages in plain terms
Liquidated damages, usually called LDs, are the contract’s pre-agreed amount for each day or unit of delay beyond the agreed substantial completion date, unless the delay is excused. They are not a penalty. They are a forward-looking estimate of the owner’s probable losses if the project comes in late. Courts in most jurisdictions will enforce LDs if the amount was a reasonable estimate when signed and the actual damages would be difficult to quantify at that time.
That “when signed” qualifier matters. I once negotiated a student housing project with a proposed LD rate of 15,000 dollars per day. The owner’s pro forma showed peak rent at that level, but only for six weeks each fall. We settled at 6,500 dollars per day by tying the rate to lost monthly net operating income spread across a plausible delay period and by excluding certain non-critical amenities from the LD calculation if the beds were ready for occupancy. That discussion, with spreadsheets open on both sides, is exactly what supports enforceability later.
LDs also interact with incentives. A contract can carry LDs for delay and a bonus for early completion at the same per diem rate. It is a cleaner signal to the field than asymmetric sticks and carrots.
What LDs are not
LDs are not a catch-all remedy for every breach. They apply to late completion, not to defective work or safety incidents or lien claims. They usually kick in after the substantial completion date, not earlier. And they are not intended to overreach. Many states scrutinize LDs that exceed a reasonable estimate of harm. If the number looks like a pressure tactic untied to reality, it can be struck as a penalty.
They also are not a substitute for good scheduling. A reasonable LD clause will not save you if your procurement plan ignored 60-week lead times, or if you drove the critical path without float analysis. LDs price the time risk, they do not manage it.
How LDs tie to scheduling mechanics
Liquidated damages provisions live or die in the schedule section. Every LD clause should be paired with:
- A clear milestone for substantial completion and, if relevant, intermediate milestones for phasing or partial occupancy. Vague milestones invite arguments over what “complete” means. Requirements for a baseline critical path method schedule, logic ties, regular updates, and documented impacts. If you cannot show where the critical path moved, you will struggle to apportion delay and avoid LDs. A defined process for time extensions. Force majeure, unusually severe weather compared to historical norms, owner-directed changes, late design decisions, utility delays, and concealed conditions can entitle the contractor to time. Without a fair way to grant extensions, LDs become a blunt instrument and attract disputes.
Project teams that treat schedule updates as paperwork usually end up paying for it. On a healthcare project I managed, we tracked long-lead medical equipment within the CPM and created a separate submittal log tied to schedule activities. When a component was delayed at the factory, we had hard data to support a 21-day time extension and to avoid LDs. The owner was not thrilled, but the contract supported the outcome, and the relationship stayed intact.
Typical LD frameworks and numbers
Rates vary widely. On mid-market private jobs, LDs commonly fall in the 500 to 5,000 dollars per day range. On revenue-heavy assets, such as hotels, casinos, or student housing, 10,000 to 30,000 dollars per day is not unusual. Public projects sometimes set LDs via standardized schedules that scale with contract value. The right number depends on:
- Value at risk: expected lost revenue, extended financing costs, extended general conditions, and third-party penalties. Duration sensitivity: a retail store opening before the holidays carries different exposure than a warehouse in a soft market. Partial use: can the owner generate revenue with partial occupancy if a few areas remain incomplete?
Another common feature is a cap. Contracts often cap LDs at a percentage of the contract sum, commonly 5 to 10 percent. Caps recognize that beyond a point, the agreed estimate gives way to windfall. Owners resist caps on projects where downstream penalties are uncapped, like concession agreements with airports. Contractors, for their part, push for caps to keep risk insurable and financeable.
Excusable and compensable delay
LDs only apply to unexcused delay. Delays fall into three buckets:
- Excusable and compensable: the contractor gets time and money. Typical causes include owner-directed changes and late owner-furnished information. Excusable but not compensable: the contractor gets time but not money. Acts of God, strikes not caused by the contractor, epidemics, and unusually severe weather often fall here, though the specifics depend on the jurisdiction and contract form. Non-excusable: the contractor gets neither time nor money, which opens the door to LDs. Examples include poor planning, late submittals without good cause, and insufficient manpower.
The gray area is concurrency, when both owner-caused and contractor-caused delays happen at the same time. Most modern contracts and scheduling specifications expect a time-only remedy for concurrent delays, which shields the contractor from LDs during the overlap but denies compensation. This is where detailed logic and contemporaneous records matter far more than narrative emails after the fact.
Why LDs and bonding belong in the same conversation
Liquidated damages price the time risk. Bonds backstop performance and payment risks. If a contractor defaults or simply walks off, the owner’s LDs keep accruing even as they struggle to finish the job. A well-drafted performance bond gives the surety options to complete the project or pay the owner’s excess completion costs, and it often addresses delay damages and LDs in Axcess Surety the remedy set. Payment bonds, meanwhile, protect subs and suppliers down the chain and keep liens from clogging title.
Owners, lenders, and public agencies view LDs and bonds as complementary. LDs create accountability to finish on time. Bonds create the capacity to step in if the contractor cannot. On complex or high-value projects, you usually see both.
Understanding construction bonding requirements
Most public projects in the United States require bonding under state “Little Miller Acts,” which mirror the federal Miller Act. Private owners frequently require bonds when the contractor is not well-known, when the project is financing-driven, or when the schedule risk is acute. The common construction bonding requirements include the following contours, though specific thresholds and percentages depend on jurisdiction and contract terms:
- Bid bond, typically 5 to 10 percent of the bid price. It protects the owner if the apparent low bidder refuses to enter the contract or furnish required bonds. Performance bond, usually 100 percent of the contract price. It guarantees performance in accordance with the contract if the contractor defaults. Payment bond, usually 100 percent of the contract price. It guarantees payment to subs and suppliers to avoid liens and to keep the job supplied.
Some owners also require maintenance bonds for one to two years after completion, especially on infrastructure where warranty disputes are costly to litigate.
From the contractor’s side, bonding is not a formality. Sureties underwrite both the company and the project. They look at liquidity, backlog, work-in-progress schedules, historical profitability, management quality, and specific job risks. Growing too fast can stress bond capacity more than any single job. If your firm usually runs 20 million dollars in backlog and you take on a 15 million dollar fast-track job with tight LDs, expect your surety to ask pointed questions about cash flow, staffing, and schedule controls.
How sureties view liquidated damages
Sureties are conservative by design. They prefer predictable, bounded obligations. LDs that are reasonably set and capped are easier to underwrite than open-ended exposure. When the LD rate is high relative to contract value and duration, or when there is no cap, expect the surety to press for:
- A longer float to substantial completion or a realistic schedule narrative that shows how the team will meet the date. Force majeure language aligned with industry norms to avoid LDs being triggered by events outside the contractor’s control. An owner obligation to mitigate, such as accepting partial occupancy, out-of-sequence work, or temporary measures that allow revenue generation while final completion proceeds.
In claims, sureties analyze delay the way a court or arbitrator does. They look at critical path impact, timeliness of notice, change documentation, and concurrency. They do not simply write a check for LDs because the owner invoiced them. A common friction point arises when the owner declares default and demands LDs while also preventing continuation or supplementing the work without offering the surety options under the bond. The sequence matters. If you want surety cooperation, follow the bond’s notice and election process.
Drafting LD clauses that stand up
A defensible LD clause has a few hallmarks. First, it states the per diem amount and identifies exactly when LDs begin and end. Many contracts use substantial completion as the trigger, with LDs running until substantial completion is achieved. Some add a smaller daily amount for missing final completion within a defined period after substantial completion.
Second, it ties the rate to the project’s economics. If the project’s monthly net revenue at stabilization is 600,000 dollars, a 10,000 dollar per day LD rate looks reasonable. If the owner’s exposure is mainly extended architect and construction manager fees, a 1,500 to 3,500 dollar daily rate might be more appropriate. Putting this rationale on the record during negotiation, even in a brief recital, helps later.
Third, it preserves the contractor’s rights to time extensions for defined causes and outlines a straightforward claim process. Notices that must be delivered within 48 hours and supported by full CPM fragnet updates inside a week may sound efficient, but they are bait for denial rather than a path to resolution.
Finally, it addresses mitigation. If the owner can occupy, open to revenue, or otherwise benefit from partial completion, the contract should allow it and reduce LDs proportionally. I have seen owners forgo mitigation to preserve an LD claim, only to lose in arbitration because they failed to act reasonably.
The practical side of enforcing LDs
Owners rarely want to litigate LDs. They want the building open. As a result, LDs are often negotiated at the end of the job along with closeout items, change orders, and retention release. Smart contractors manage toward that reality from the start. They document excusable delays, forecast risks early, and keep the owner informed in writing.
Two practical tips matter. Do not wait until you are already late to seek a time extension. You gain credibility by forecasting an impact when the cause arises, not by retrofitting a claim file at the finish line. And separate time from money. If a change is issued, seek a time adjustment even if you plan to accelerate. You can always withdraw the time request if acceleration succeeds, but you cannot create record where none exists.
On a municipal library project, we agreed to waive LDs for a 19-day delay in exchange for the contractor’s agreement to split acceleration costs and to prioritize the children’s area for early occupancy. The city opened the children’s programs on time, donors stayed happy, and the rest of the building finished three weeks later. Everyone gave a little, and the paperwork reflected a practical settlement anchored to the LD framework.
When LDs and actual damages collide
Sometimes owners reserve the right to claim actual damages instead of LDs. That is rare and risky, because it undermines the purpose of LDs and can render them a penalty. More commonly, the contract says LDs are the owner’s sole remedy for delay, but only for delay. If the contractor’s late work also causes third-party penalties or liquidated damages owed by the owner to a landlord or agency, those can be addressed either within the LD rate or carved out explicitly with a cap. If you do not address pass-through liquidated damages, you invite duplication.
Another wrinkle comes with liquidated damages linked to specific systems. Data centers sometimes define LDs for missing mechanical completion, power-on, or achieving guaranteed levels of uptime. These are not purely time-based. They blend performance guarantees with schedule. When you see that mix, align the guarantees with testing protocols and commissioning responsibilities. Do not accept LDs for performance criteria you cannot control.
Coordinating LDs with subcontract agreements
General contractors who sign up for LDs and do not flow an appropriate share to key subs are volunteering to be the bank. Passing through LDs is not as simple as copying the clause. Courts scrutinize subcontracts for reasonableness and clarity. The better approach is to allocate responsibility in proportion to each trade’s critical path exposure, identify key milestone dates, and adopt a mechanism for back-charging LDs only if the sub’s delay is the sole cause of the missed date, with concurrency considered. I have used language that ties a subcontractor’s exposure to a negotiated daily rate capped at a percentage of the subcontract sum. Subs cooperate more when the risk is bounded and the path to avoiding it is clear.
Insurance and LDs
Standard commercial general liability policies do not cover LDs. They are a contractual obligation, not a covered occurrence. Builders risk might respond to certain delay-related costs if you purchase delay in startup or soft costs coverage, but that is a separate premium and typically requires a specific insured peril, such as a covered property loss, not a labor shortage or a late permit. If LD exposure is significant, the project’s risk register should consider whether insurance tools can offset portions of the schedule risk and whether the premium makes sense compared to the LD cap.
Lenders and bonding
Lenders read LD clauses before they sign loan agreements. They want assurance that the construction schedule aligns with the interest reserve and lease-up plan. Aggressive LDs without a reasonable path to time extensions can spook lenders, who fear a fight that stops the job. On the bonding side, lenders often require dual or tripartite agreements with the surety that limit the risk of the owner and surety fighting while loan covenants are ticking. If you are a developer, involve the lender when you set LDs and construction bonding requirements so the covenants harmonize.
Negotiation strategies that work
Treat LDs as a product of math and risk allocation, not of bravado. Show your work. Present a simple model of probable owner damages for delay, including a range based on different scenarios. Offer to index the LD rate to specific milestones, with higher rates where delay hurts more. Seek a global LD cap tied to contract value, then enforce lower caps on interim milestones. Agree to a cure period for short delays when the contractor is close to substantial completion and can finish without material harm.
On bonding, work with your surety early. Give them the draft contract, including LDs, as soon as you have it. Address their concerns in the document, Additional reading not in side letters that appear only after default, when they matter least. If you are an owner, allow reasonable alternatives, like parent guarantees or letter of credit support, if the contractor’s bond capacity is tight. For some private projects, a split approach works: full payment bond, performance bond at 50 to 75 percent, plus a guaranteed maximum price with a contingency and shared savings to keep alignment.
Common pitfalls and how to avoid them
A few mistakes repeat across projects despite the war stories.
- Vague completion definitions that spark debates over punch list versus substantial completion. Define what counts: life safety sign-offs, certificate of occupancy or temporary certificate, systems commissioned to a defined level, and owner access for intended use. Failure to integrate the LD framework into the schedule specification. If the scheduling section is boilerplate and does not require logic-based updates and fragnet analysis for changes, expect a fight over time extensions. Owner-caused delays with no documentation because the team wanted to “stay positive.” Optimism without recordkeeping converts excusable delay into expensive silence. Overly punitive LDs that scare bidders into adding heavy risk premiums or, worse, lead to good contractors walking away. Oversized LDs feel strong on paper and then come back as higher prices, thinner competition, and more claims. Bond claims triggered without following the bond. Performance bonds give the surety options. Skipping notice, replacing the contractor immediately, and then sending the bill often voids cooperation. If the project is burning, call the surety, put them on notice, and document every step, but follow the election process whenever possible.
The human factor in schedule risk
Contracts and bonds are tools. People build projects. On a winter school renovation, we faced a sequence squeeze when asbestos abatement took longer than planned. The contract allowed LDs if the school could not open by August. Instead of hiding, the GC brought trades, inspectors, and the owner’s facilities team into a weekly “war room” starting in March. We resequenced ceilings, split inspection packages, and authorized overtime early while still cost-effective. The owner granted a 12-day time extension for the abatement delay and agreed to partial occupancy. School opened on time. The LD clause never came into play because the team treated it as a backdrop, not as a stick.
That is the larger point. LDs and bonds allocate risk so that projects can proceed with clarity. They are not replacements for honest forecasting, disciplined scheduling, and early communication.
A focused checklist for owners and contractors
- Quantify, do not guess. Tie LD rates to credible damages and write down the rationale. Build the schedule spec. Require CPM with monthly updates, fragnet analysis for changes, and a clear time extension process. Cap exposure sensibly. Global caps for LDs improve enforceability and insurability. Align bonding with reality. Confirm bond capacity early, share draft contracts with the surety, and synchronize notice provisions. Keep records live. Notices, meeting minutes, look-ahead schedules, and correspondence are your shield against unfair LDs and your evidence if you need to enforce them.
Where to land
If you are drafting, resist the urge to make LDs do too much. Price the time risk fairly, preserve flexibility for excusable delays, and require the behaviors that keep everyone honest. If you are pricing work, view LDs and construction bonding requirements as part of your go, no-go screen. They shape staffing, sequencing, contingency, and the margin you need to carry the risk. The smoothest projects I have seen put these conversations on the table early, test them against the schedule and the pro forma, and then leave them alone while the team focuses on execution. The paper is there to keep the edges fair, not to run the job.