No Damage for Delay Clauses for Contractors

Learn when no-damage-for-delay clauses may hold up, when state law or exceptions may limit them, and what small contractors should document before signing.

Article

Time is money.

A no-damage-for-delay clause says time is all you get.

That sentence is why small contractors need to slow down before signing a GC subcontract, property-manager service agreement, tenant-improvement contract, or commercial maintenance form. The clause can look harmless because it does not say you caused the delay. It just says that if the job is delayed, interfered with, disrupted, suspended, resequenced, accelerated, or hindered, your only remedy is more time.

No extra labor.

No remobilization cost.

No standby.

No overtime.

No extended equipment rental.

No storage.

No price escalation.

No office overhead.

No impact cost.

For a small shop, that can turn a profitable job into a slow loss. You still carry payroll, trucks, insurance, rent, equipment, crew morale, supplier commitments, and a calendar slot you cannot sell twice.

The hard part is that these clauses are not automatically unenforceable. Some are enforceable. Some are limited by state law. Some have narrow exceptions. Some can be rewritten into a fair delay procedure. Some should make you walk away.

If the contract already has a broad delay paragraph, pull it into the same review pile as indemnity, backcharges, pay-if-paid, lien waivers, and lost-profits exposure. The broader redline checklist is in What to Cross Out in Big-Company Contract Templates Before You Sign. This article is the focused guide to no-damage-for-delay clauses.

What the clause means

A no-damage-for-delay clause usually says the contractor or subcontractor gets an extension of time, but no money, for delay.

The language may look like this:

"Contractor's sole and exclusive remedy for delay, disruption, interference, acceleration, suspension, resequencing, or hindrance shall be an extension of contract time. Contractor shall not be entitled to compensation, damages, overhead, profit, impact costs, inefficiency, acceleration costs, or other monetary relief for delay from any cause."

That is the rough business effect. The exact legal effect depends on the state, project type, public/private status, whether the clause covers the delay that actually happened, and whether an exception applies.

Do not confuse it with a normal schedule clause.

A normal schedule clause says dates may move when the job is delayed for reasons outside your control. A no-damage-for-delay clause says dates may move, but your added costs do not get paid.

Those are different risks.

The small-shop problem

Large contractors may have schedulers, delay experts, legal review, and enough volume to absorb a bad month. A two-truck HVAC shop, flooring installer, electrical subcontractor, roofer, plumber, painter, concrete crew, or remodeling sub usually does not.

Delay costs hit small shops in plain ways:

Delay eventDirect field impactPaperwork that should capture it
Owner has not cleared the work areaCrew loses half a day and returns laterWork order, photos, access notice
GC resequences the jobYour crew works out of order and loses productivityDaily report log, schedule notice
Other trade blocks your areaLabor waits, leaves, or comes back at overtimeDaily report, request for information
Customer changes selections lateMaterials get reordered and install shiftsChange order, supplier backup
Permit or inspection is delayed outside your controlCompletion and billing move outNotice, inspection record, revised schedule
Unpaid progress invoice stalls procurementYou cannot order the next material packageInvoice, statement of account, default notice
Hidden condition stops workScope, price, and schedule all changePhotos, RFI, construction change directive, change order

If the contract says you get only time, every one of those costs may become yours unless state law, the contract language, or the facts give you a way around the clause.

That is why the clause belongs in the price conversation before signing, not in a dispute folder six weeks later.

Are these clauses enforceable?

The honest answer is: sometimes.

Courts and statutes do not treat no-damage-for-delay clauses the same way everywhere.

Some states limit them by statute, especially on public construction work. California Public Contract Code Section 7102 limits no-damage-for-delay language in public-agency construction contracts and subcontracts when the contractee is responsible for unreasonable delay that was not within the parties' contemplation. Washington goes broader in RCW 4.24.360, treating certain construction-contract waivers of damages or equitable adjustment for unreasonable delay caused by the contractee, meaning the owner or customer side of the contract, as void and unenforceable. It still preserves notice requirements, dispute procedures, and reasonable liquidated damages.

Virginia Code Section 2.2-4335 addresses public construction contracts and voids clauses that waive a contractor's right to recover costs or damages for unreasonable delay caused by the public body, its agents, or employees when the causes are within their control. North Carolina General Statutes Section 143-134.3 says no contractual language limiting compensable damages for delays caused solely by the owner or its agent may be enforced in covered public construction contracts, while also clarifying that "owner or its agent" does not include prime contractors or their subcontractors.

Those examples do not create a national rule. They prove the opposite: the answer changes by state and contract type.

Private commercial subcontracts can be harsher. A New York Appellate Division decision from September 30, 2025, Henick-Lane, LLC v Stellar Mgt. Group, Inc., applied a no-damages-for-delay clause to change-order requests that were really based on obstruction, hindrance, delay, or changes in the work. The court also rejected the contractor's exceptions on those facts. In plain English: calling a delay cost "extra work" did not automatically get around the delay clause.

On the other side, California's Howard Contracting, Inc. v. G.A. MacDonald Construction Co. shows the public-contract limit in action. The court discussed Public Contract Code Section 7102 and delay claims tied to a city's failure to disclose known restrictions, obtain necessary permits, and provide timely access. That case is not your private service agreement, but it shows why state law and owner-caused delay facts matter.

The practical takeaway:

  • Do not assume the clause is unenforceable.
  • Do not assume it is absolute.
  • Do not rely on a general internet answer.
  • Do not sign it without knowing which side controls the likely delay risks.

The exceptions are narrow

Contractors often hear, "No-damage-for-delay clauses have exceptions."

That is true, but it can be a dangerous comfort.

Depending on the state, possible exceptions may involve:

  • bad faith;
  • fraud or concealment;
  • active interference;
  • willful, malicious, or grossly negligent conduct;
  • delays not contemplated when the contract was signed;
  • delay so extreme it looks like abandonment of the contract;
  • breach of a fundamental obligation;
  • statutes that protect delay costs on certain public projects;
  • contract language that excludes the specific delay from the no-damage rule.

Those exceptions are not magic words. You have to prove facts.

"The GC was disorganized" may not be enough. "The owner was slow" may not be enough. "The schedule moved a lot" may not be enough. Even a long delay may be treated as a risk you accepted if the contract clearly covered delays caused by changes, resequencing, other trades, access, or owner acts.

That is the core lesson from recent New York delay cases: if the clause expressly covers the kind of delay you suffered, and the delay does not fit a narrow exception, the clause can still block money.

Do not build your business plan around winning an exception later. Write the exception into the contract before the job starts.

Clauses that are too broad for a small shop

Slow down when the clause says delay from "any cause whatsoever."

That phrase tries to catch everything:

  • owner delay;
  • GC delay;
  • architect or engineer delay;
  • other trades;
  • late approvals;
  • site access problems;
  • permit delays;
  • inspection delays;
  • utility delays;
  • design errors;
  • hidden conditions;
  • changes in the work;
  • acceleration;
  • suspension;
  • resequencing;
  • interference;
  • inefficiency;
  • material delays;
  • labor impacts;
  • missed coordination;
  • unpaid invoices;
  • force majeure events.

A clause that broad may shift risks you do not price and cannot control.

Even worse, it may sit next to daily liquidated damages against you. That is the one-way version: if you are late, you pay; if they delay you, you only get more time. Pair that with broad backcharges and a pay-if-paid clause, and a small subcontract can trap cash fast.

Use Pay-When-Paid vs Pay-If-Paid for the payment-risk side. Use The Clause That Blocks "Lost Profit" Blowups on Small Jobs for downstream lost-profit exposure. Delay clauses often sit right between those two risks.

A fairer delay position

The clause does not have to disappear completely.

For many small private jobs, the fair position is:

  • the contractor is responsible for delays caused by its own failure to perform;
  • the customer or GC is responsible for delays caused by its changes, late decisions, denied access, unpaid approved invoices, unsafe site conditions, or other people it controls;
  • delays outside both parties' control give time extensions and a mitigation procedure;
  • money is available only for documented added costs, not speculative business losses;
  • acceleration requires a written change order before overtime or extra crews are used;
  • notice is required within a stated number of days;
  • the customer still gets a reasonable remedy for contractor-caused delay;
  • neither side waives non-waivable rights under state law.

In document terms, that belongs in the contract agreement, supported by a precise statement of work, a clean quote estimate, crew-level work orders, and signed change orders.

If the job is a true construction subcontract, tie the same rule to the construction contract agreement, daily reports, RFIs, payment applications, construction change directives, and lien-waiver workflow.

The carveouts to ask for

If the other side refuses to delete the clause, ask for carveouts.

Start with these:

Owner or GC-caused delay. You get time and documented direct costs when the other side causes delay through denied access, late approvals, late selections, site unreadiness, failure to coordinate, owner-directed changes, or other acts within its control.

Other trades. You should not eat cost for delays caused by trades you do not control. If the GC controls site coordination, the GC should carry that coordination risk or at least give time and documented cost relief.

Changes in work. A change order should adjust scope, price, and time. Do not let the contract say all delay or inefficiency from changed work is included in the original price.

Concealed or differing conditions. Rot, bad wiring, failed substrate, unknown utilities, hidden structural problems, and bad site conditions should trigger a stop-document-price workflow. Pair this with When the Plans Don't Match the Field.

Suspension or standby. If the owner or GC tells you to stop, hold crew available, keep equipment on site, or return later, the cost should be documented and payable where state law and the contract allow.

Acceleration. If they want you to recover schedule by adding labor, overtime, shift work, expedited shipping, or weekend work, that should be a signed change order.

Unsafe conditions. You should not have to keep working in an unsafe condition to preserve your schedule rights. Use a job hazard analysis or safety inspection checklist where field risk changes.

Nonpayment. If approved progress payments are late, the delay clause should not force you to keep financing the job for free. Use the notice process in Cure Periods, Notice of Default, and the Right to Cure.

Force majeure. Weather, evacuation orders, supplier shutdowns, utility outages, and other external events need a documented delay procedure. The storm-season version is in How an "Acts of God" Clause Protects Roofers in Hurricane Season.

You may not get every carveout. But if the customer or GC refuses all of them, your price should reflect that. A normal price does not carry abnormal delay risk.

What delay costs should be named

If the contract allows money for some delays, name the categories.

Small shops do not always need a forensic delay claim. They need the contract to recognize ordinary added cost:

  • demobilization and remobilization;
  • standby labor;
  • return trips;
  • extended equipment rental;
  • storage;
  • temporary protection;
  • material escalation after customer-caused delay;
  • restocking or re-delivery fees;
  • overtime or acceleration requested by the customer or GC;
  • supervision time;
  • permit or inspection rebooking fees;
  • documented extended general conditions where applicable;
  • supplier cancellation or hold charges;
  • reasonable admin time for delay notices, coordination, and revised schedules.

Then separate those from losses you are not accepting.

For example, you may agree that customer-caused delay triggers documented remobilization and storage cost, but not unlimited lost profits, tenant rent, business interruption, or third-party penalties unless specifically priced and accepted. That keeps your delay clause aligned with your limitation-of-liability clause.

The notice rule matters

Many statutes and contracts preserve notice requirements even when they limit no-damage-for-delay clauses.

That means a contractor can be right about the delay and still lose the money claim by missing the notice procedure.

Your delay notice should be short and factual:

  1. Identify the job, contract, and affected work.
  2. State the event causing delay.
  3. State who controls the event, if known.
  4. State the date the delay started.
  5. State the expected schedule impact, if known.
  6. State the expected cost impact, if known.
  7. State what you are doing to reduce the delay.
  8. Request written direction, access, approval, payment, or a change order.
  9. Reserve rights under the contract where appropriate.

Do not wait until the invoice.

Put field facts in the daily report log, work order notes, photos, delivery tickets, emails, and inspection records. Use a request for information when the delay is caused by missing direction, design conflict, site conflict, or unclear scope. Use a construction change directive only when the contract and project workflow actually support that tool.

A simple delay notice example

Keep the tone calm.

We are sending notice that our electrical rough-in work in Area B is delayed because the wall framing and fireblocking required before our installation are incomplete. Our crew was scheduled for May 6 and arrived at 7:15 a.m.; the area was not ready for electrical rough-in. We are available to resume after Area B is released. This delay may affect our completion date and may require remobilization or standby cost under the contract. Please confirm the revised access date and whether we should hold crew for this work or release them to another project.

That notice is stronger than "you are delaying us."

It says what happened, when, where, why it affects work, what decision is needed, and what cost may follow.

When an extension of time is enough

Sometimes the other side's position is not unreasonable.

An extension of time may be enough when:

  • the delay does not add real cost;
  • the crew can move to another job without loss;
  • material pricing is locked;
  • equipment is not sitting idle;
  • no remobilization is required;
  • the customer does not demand acceleration;
  • the schedule is flexible;
  • the delay is caused by a neutral event outside both parties' control;
  • the job is small enough that fighting over delay cost is not worth it.

That is why the goal is not "never accept time-only relief."

The goal is to avoid accepting time-only relief for delays that create real cost and are caused by people or decisions you do not control.

When to walk away

Some clauses are too much for a small shop.

Be ready to walk if the contract says:

  • you owe liquidated damages for being late, but get no money for owner or GC delay;
  • you must accelerate at your cost after delays you did not cause;
  • the GC can resequence, suspend, supplement, or backcharge you without notice or proof;
  • all delay, disruption, inefficiency, impact, and acceleration costs are included in the price;
  • you waive delay claims in every lien waiver or payment application;
  • you must continue working through nonpayment without preserving prompt-payment, lien, bond, or stop-work rights;
  • the clause applies even to bad faith, active interference, concealment, or delays outside the parties' contemplation, to the extent state law would otherwise protect you;
  • the other side will not identify the schedule, access plan, predecessor work, or decision deadlines before signing.

That is not just contract language. That is a pricing problem.

If the customer wants you to insure their schedule and absorb everyone else's delays, the job is not priced like ordinary trade work anymore.

What to check before signing

Before you sign, answer these questions:

  1. Is the project public or private?
  2. Which state's law governs the contract?
  3. Does that state limit no-damage-for-delay clauses for this type of project?
  4. Does the clause apply to delays caused by the owner, GC, architect, engineer, other trades, utilities, inspectors, suppliers, or force majeure?
  5. Does the clause allow money for any delay costs, or only time?
  6. Does the contract require written notice within a certain number of days?
  7. Does the payment application or lien waiver release delay claims if you sign it?
  8. Does the contract let the other side order acceleration?
  9. Does the contract preserve stop-work or cure rights for nonpayment?
  10. Does your price include the delay risk you are accepting?

If the answer to number 10 is no, the clause needs a redline, a higher price, or a pass.

The rule to remember

A no-damage-for-delay clause is not just legal filler.

It decides who pays when the schedule breaks.

For small contractors, the safe operating rule is simple:

  • identify delay risk before signing;
  • carve out delays caused by the other side, other trades, denied access, changes, nonpayment, unsafe conditions, and concealed conditions;
  • keep force majeure separate from owner-caused delay;
  • name the delay costs that can be recovered;
  • give written notice early;
  • document field impact every day it continues;
  • use change orders for acceleration, resequencing, standby, and added cost;
  • do not sign payment paperwork that quietly releases delay claims you still need.

More time is useful only when time solves the problem.

When delay burns labor, equipment, materials, cash flow, or another job slot, the paperwork has to say who pays for that cost before the job starts.

Sources


This article is for general information and is not legal, tax, insurance, safety, or compliance advice. Verify contract, delay, acceleration, liquidated-damages, lien, prompt-payment, public-project, state-law, licensing, and insurance rules with your attorney, state contractor board, local authority having jurisdiction, insurance adviser, or CPA before acting.