5 Ways to Draft a Contract Clause Dealing With Delay in Performance

Note: This article is for general informational and drafting-education purposes only. Contract law can vary by state, industry, contract type, and facts, so businesses should consult qualified legal counsel before using any clause in a live agreement.

Delay in performance is one of those contract problems that sounds harmless until the deadline passes, the emails get spicy, and everyone suddenly becomes a philosopher of “reasonable time.” A supplier says the shipment is stuck. A contractor says the owner caused the delay. A software vendor says a third-party API exploded like a microwave burrito. Meanwhile, the customer wants delivery yesterday, and the contract has all the clarity of a fog machine at a middle-school dance.

That is why a well-drafted delay in performance clause matters. It does not magically prevent late delivery, missed milestones, supply-chain surprises, labor shortages, permit issues, storms, system outages, or vendor chaos. What it does is more valuable: it tells the parties what counts as a delay, who must give notice, when deadlines may be extended, whether money changes hands, and when the delayed party can terminate the contract.

In U.S. contract drafting, delay clauses often borrow ideas from force majeure provisions, “time is of the essence” clauses, liquidated damages, notice requirements, cure periods, and extension-of-time procedures. The goal is not to write the longest clause in the room. The goal is to write one that works when everyone is tired, annoyed, and reading it under fluorescent lighting.

Below are five practical ways to draft a contract clause dealing with delay in performance, with examples, drafting tips, and real-world experience notes you can adapt to commercial agreements, service contracts, construction contracts, supply contracts, technology agreements, and project-based deals.

1. Define What Counts as a Delay in Performance

A delay clause should start by answering a deceptively simple question: delayed compared to what? If the contract does not define the performance deadline, milestone, delivery schedule, or completion date, the delay clause has nothing solid to grab onto. That is like putting a smoke alarm in a house with no walls. Admirable effort, questionable engineering.

The clause should identify the exact obligations that are time-sensitive. These might include delivery of goods, substantial completion of work, payment milestones, launch dates, installation deadlines, approval windows, response times, or project handoffs. A vague phrase such as “Party shall perform in a timely manner” may sound polite, but it can create disputes because “timely” means different things to different people. To a customer, it may mean Friday at 5 p.m. To a vendor, it may mean “before the sun becomes a red giant.”

Drafting approach

A strong delay clause should connect delay to specific dates, schedules, or measurable events. For example:

“A delay in performance occurs when a Party fails to complete a material obligation by the applicable deadline, milestone date, delivery date, or completion date stated in this Agreement, the Statement of Work, or an approved project schedule.”

This language gives the parties a clear measuring stick. It also leaves room for multiple project documents, which is especially useful when the main agreement contains general terms and the details live in a statement of work, purchase order, work order, or project schedule.

When to use “time is of the essence”

If timely performance is truly critical, the contract may state that “time is of the essence.” This phrase signals that deadlines are material, not decorative. It is especially common in real estate contracts, construction agreements, manufacturing commitments, event contracts, and transactions where a late performance can destroy the value of the deal.

However, do not sprinkle “time is of the essence” everywhere like parmesan cheese. If every small administrative deadline is treated as essential, the contract may become too rigid and commercially unrealistic. A better approach is to specify which obligations are time-critical:

“Time is of the essence with respect to Supplier’s delivery of the Products by the Delivery Date and with respect to Customer’s payment obligations under Section 4.”

This avoids overkill. It tells a court, arbitrator, or angry project manager exactly which deadlines matter most.

2. Require Prompt Notice, Details, and Ongoing Updates

A delay clause without a notice requirement is like a weather app that reports yesterday’s thunderstorm. Interesting, but not very helpful. The non-delayed party needs to know about the delay early enough to reduce damage, adjust schedules, notify customers, find substitutes, or prepare for the next best option.

Notice language should answer five questions: who must give notice, when notice must be given, how notice must be delivered, what the notice must include, and whether updates are required. The more complex the project, the more important this becomes.

Drafting approach

“A Party affected by an actual or reasonably anticipated delay shall provide written notice to the other Party within five business days after becoming aware of the event causing the delay. The notice must describe the cause of the delay, the obligations affected, the expected duration, the steps being taken to mitigate the delay, and any requested extension of time. The affected Party shall provide reasonable updates until the delay is resolved.”

This clause does several useful things. It covers both actual delays and anticipated delays. It requires useful information, not just a dramatic one-line email saying, “We regret to inform you that things are bad.” It also creates a duty to provide updates, because delays often evolve. A one-week issue can become a one-month issue, and a one-month issue can become a conference call with too many vice presidents.

Should late notice destroy the claim?

One drafting choice is whether failure to give timely notice completely bars relief. Some contracts say yes, especially in construction and government-related contracting where delay claims depend heavily on timely documentation. Other contracts take a softer approach and say late notice limits relief only to the extent the other party was prejudiced.

A balanced clause might say:

“Failure to provide timely notice shall not automatically waive the affected Party’s right to relief, except to the extent the delay in notice materially prejudices the other Party’s ability to mitigate, investigate, or respond to the delay.”

This language is often more commercially reasonable. It punishes real harm, not harmless paperwork sins. After all, a contract should not behave like a vending machine that eats your dollar because you pressed the button too gently.

3. Separate Excusable Delay From Non-Excusable Delay

Not every delay should be treated the same. A supplier who is late because a port closes after a government order is in a different position from a supplier who is late because it forgot to order materials. A contractor delayed by owner-caused design changes is not the same as a contractor who simply understaffed the job. Good drafting separates excusable delay, compensable delay, and non-excusable delay.

Excusable delay

An excusable delay is usually caused by events beyond the delayed party’s reasonable control and without that party’s fault or negligence. Common examples include natural disasters, fires, floods, epidemics, labor strikes not limited to the party’s own workforce, acts of government, embargoes, war, terrorism, utility failures, supply-chain interruptions, or other force majeure events.

A clause may say:

“A Party shall not be liable for delay in performance to the extent the delay is caused by an event beyond its reasonable control, without its fault or negligence, and not reasonably foreseeable or avoidable by commercially reasonable efforts.”

The phrase “to the extent” matters. It prevents a party from using a small delay event as a magic umbrella for unrelated poor performance. If a storm delays delivery by three days, the party should not receive a three-month vacation from the contract.

Compensable delay

A compensable delay occurs when one party causes delay and the other party suffers added cost. In construction, for example, an owner’s late site access, late approvals, or repeated design changes may justify both extra time and additional compensation. In service contracts, a customer’s failure to provide data, access credentials, equipment, or approvals may delay the vendor and increase costs.

Consider language such as:

“If Customer’s acts, omissions, delayed approvals, failure to provide required information, or changes in scope delay Vendor’s performance, Vendor shall be entitled to a reasonable extension of time and an equitable adjustment for documented additional costs directly caused by the delay.”

This is practical because it ties relief to causation and documentation. The party claiming additional money must show the delay actually caused the cost. “We feel delayed in our hearts” is not a damages model.

Non-excusable delay

A non-excusable delay is within the delayed party’s control or caused by its own fault. Examples may include poor planning, insufficient staffing, avoidable procurement failures, internal administrative problems, financial difficulty, or failure to manage subcontractors unless the contract says otherwise.

The clause can state:

“Delays caused by a Party’s lack of funds, internal staffing shortages, failure to manage its subcontractors or suppliers, or failure to plan for reasonably foreseeable conditions shall not constitute excusable delay unless expressly agreed in writing by the Parties.”

This prevents a party from stretching force majeure language beyond recognition. A force majeure clause should not become a hammock for ordinary business risk.

4. Explain the Consequences: Extensions, Liquidated Damages, and Caps

Once a delay occurs, what happens next? This is where many contracts fall apart. They identify delay events but do not explain the remedy. A strong delay clause should state whether the delayed party gets more time, whether damages apply, whether liquidated damages apply, whether liability is capped, and whether delay damages are the exclusive remedy.

Extension of time

For excusable delays, the most common remedy is an extension of time. The extension should match the actual impact of the delay, not the emotional impact. A clause might say:

“For each Excusable Delay, the affected deadline shall be extended only for the period of delay actually and directly caused by the Excusable Delay, plus a reasonable period for remobilization if applicable.”

The phrase “actually and directly caused” helps avoid inflated claims. The phrase “reasonable period for remobilization” is useful for construction, manufacturing, event production, and other work where restarting after interruption takes time.

Liquidated damages

Liquidated damages can be useful when late performance will cause harm that is difficult to calculate at the time of contracting. Instead of fighting later about the exact amount of loss, the parties agree in advance to a reasonable daily, weekly, or milestone-based amount.

For example:

“If Contractor fails to achieve Substantial Completion by the Completion Date, as extended under this Agreement, Contractor shall pay Owner liquidated damages in the amount of $1,000 per day for each day of unexcused delay, up to a maximum of 10% of the Contract Price. The Parties agree that actual damages would be difficult to determine and that the amount stated is a reasonable estimate of anticipated damages and not a penalty.”

This example includes several important pieces. It applies only after the completion date as properly extended. It applies only to unexcused delay. It includes a cap. It states that the amount is a reasonable estimate, not a penalty. That distinction matters because U.S. courts generally do not enforce penalties disguised as contract damages.

Caps and exclusive remedies

Parties should decide whether delay damages are capped and whether liquidated damages are the exclusive remedy for delay. Without clarity, one party may argue that liquidated damages are only one remedy and that additional damages are still available. The other party may insist the agreed amount was meant to be the whole deal.

Sample language:

“Liquidated damages for delay shall be Customer’s sole and exclusive monetary remedy for Contractor’s unexcused delay, except for Contractor’s fraud, willful misconduct, abandonment, or breach of confidentiality obligations.”

This creates predictability while preserving remedies for serious misconduct. It also keeps the clause from becoming unfairly one-sided.

5. Add a Cure Period, Termination Right, and Mitigation Duty

Delay clauses should not focus only on blame. They should also create a path forward. Sometimes the right answer is more time. Sometimes it is money. Sometimes it is termination. Sometimes it is a rescue plan involving spreadsheets, coffee, and a project manager who has seen things.

Cure period

A cure period gives the delayed party a chance to fix the problem before termination. This is helpful when immediate termination would be commercially wasteful. For example:

“If a Party is in unexcused delay for more than ten business days, the non-delayed Party may provide written notice of default. The delayed Party shall have ten business days after receipt of the notice to cure the delay or submit a commercially reasonable recovery plan acceptable to the non-delayed Party.”

This language gives flexibility. Cure may mean finishing the task, adding resources, changing logistics, or submitting a realistic recovery schedule. A recovery plan is often better than a dramatic termination letter, especially when both parties still want the project completed.

Termination for extended delay

Some delays last too long. A force majeure event may continue for months. A project may become commercially pointless. A vendor may be unable to perform despite good intentions. The contract should say when delay becomes a termination right.

“If an Excusable Delay continues for more than sixty consecutive days, either Party may terminate the affected Statement of Work upon written notice, without further liability except for payment for conforming goods delivered or services properly performed before the effective date of termination.”

This gives both parties an exit ramp. It avoids trapping them in a contract that no longer makes business sense.

Mitigation duty

A good delay clause should require mitigation. The delayed party should use commercially reasonable efforts to reduce the delay and limit damage. The non-delayed party should also avoid making the loss worse when reasonable alternatives are available.

Sample language:

“Each Party shall use commercially reasonable efforts to mitigate the effects of any delay, including by considering reasonable substitute performance, alternate suppliers, revised sequencing, temporary workarounds, or other commercially practical measures.”

This language encourages problem-solving. It also discourages delay theater, where everyone performs outrage for the record but nobody actually fixes the issue.

Putting It Together: A Sample Delay in Performance Clause

Here is a practical sample clause combining the five drafting strategies above. It should be customized for the deal, industry, state law, and bargaining position.

“Delay in Performance. A delay in performance occurs when a Party fails to complete a material obligation by the applicable deadline, milestone date, delivery date, or completion date stated in this Agreement or an applicable Statement of Work. Time is of the essence only for those obligations expressly identified as time-critical in this Agreement.

A Party affected by an actual or reasonably anticipated delay shall provide written notice to the other Party within five business days after becoming aware of the event causing the delay. The notice must describe the cause, affected obligations, expected duration, mitigation efforts, and any requested extension of time. The affected Party shall provide reasonable updates until the delay is resolved.

A Party shall not be liable for delay to the extent caused by an event beyond its reasonable control, without its fault or negligence, and not reasonably avoidable through commercially reasonable efforts. Any affected deadline shall be extended only for the period of delay actually and directly caused by the excusable event, plus a reasonable remobilization period if applicable.

Delays caused by a Party’s lack of funds, internal staffing shortages, failure to manage subcontractors or suppliers, or failure to plan for reasonably foreseeable conditions shall not constitute excusable delay unless expressly agreed in writing.

If a Party is in unexcused delay for more than ten business days, the non-delayed Party may provide written notice of default. The delayed Party shall have ten business days to cure the delay or submit a commercially reasonable recovery plan. If the delayed Party fails to cure or provide an acceptable recovery plan, the non-delayed Party may exercise any remedies available under this Agreement, including termination of the affected Statement of Work.

Each Party shall use commercially reasonable efforts to mitigate the effects of any delay. If liquidated damages are stated in an applicable Statement of Work, they shall apply only to unexcused delay after giving effect to any approved extension of time and shall not operate as a penalty.”

Common Mistakes to Avoid When Drafting Delay Clauses

Mistake 1: Using vague words without standards

Words like “promptly,” “soon,” “reasonable,” and “timely” are useful only when the contract gives them context. If a deadline matters, state the date, period, or triggering event. A clause should reduce arguments, not provide new costumes for them.

Mistake 2: Forgetting causation

The delayed party should show that the event actually caused the delay. If the project was already three weeks late before the storm arrived, the storm should not get blamed for the whole mess. Causation language keeps the analysis honest.

Mistake 3: Ignoring concurrent delays

Concurrent delay happens when two or more delay causes overlap. For example, the owner may be late with approvals while the contractor is also short on labor. Contracts should state how concurrent delays affect extensions, compensation, and liquidated damages. Without that language, the parties may end up arguing over delay math with the enthusiasm of people trapped in a group tax audit.

Mistake 4: Making liquidated damages look punitive

Liquidated damages should be a reasonable forecast of anticipated harm, not a revenge machine. Use a reasonable amount, include a cap when appropriate, and state that the amount is not a penalty. The more outrageous the number, the more likely it will attract a legal challenge.

Mistake 5: Treating force majeure as a copy-paste museum exhibit

Force majeure language should match the transaction. A software-as-a-service contract may need language for cloud outages, cyber incidents, third-party platforms, and data-center failures. A manufacturing contract may need language for raw materials, shipping lanes, port closures, and supplier allocation. A construction contract may need weather, site conditions, permits, inspections, and owner-caused delays. Copying a generic clause from an old contract is how today’s problem becomes tomorrow’s lawsuit.

Practical Experience Notes: What Actually Works in the Real World

In practice, the best delay clauses are not always the most aggressive. They are the clearest. A clause that says, “You are late, you pay, the end,” may feel satisfying during negotiation, but it may fail when the delay is caused by mixed events, owner interference, government orders, missing approvals, or an excusable disruption. Real projects are messy. The clause needs enough structure to handle that mess without turning every hiccup into a legal festival.

One useful experience is to draft delay language around project behavior, not just legal theory. Ask: What should the parties do on the first day of delay? Who sends notice? Who receives it? What information must be included? Who decides whether the schedule changes? How quickly must the parties meet? Can work be resequenced? Can substitute goods be accepted? Can temporary performance be used? These questions turn the clause into an operating manual instead of a decorative paragraph no one reads until disaster arrives wearing a name tag.

Another lesson is that documentation wins delay disputes. The party claiming delay should keep records showing when the delay started, what caused it, how it affected the critical path or delivery schedule, what mitigation steps were taken, and when the delay ended. In construction, that may mean daily reports, updated schedules, inspection logs, RFIs, change orders, weather records, and meeting minutes. In technology contracts, it may mean ticket histories, outage reports, dependency logs, access requests, API notices, and customer approval records. In supply agreements, it may mean carrier notices, allocation letters, customs updates, production reports, and alternate supplier quotes. A delay clause can require this documentation so the parties do not rely on memory, which is basically a hard drive made of pudding.

It is also smart to connect the delay clause with other parts of the contract. The force majeure clause, limitation of liability, termination clause, change order procedure, notice section, payment terms, service levels, and dispute resolution clause should all work together. If the delay clause says the vendor gets extra time, but the service-level clause says credits apply automatically for every missed deadline, the contract may create conflicting remedies. If the termination clause allows immediate termination for any missed milestone, but the delay clause gives a ten-day cure period, the parties may fight over which clause controls. Internal consistency is not glamorous, but neither is spending money to litigate a drafting contradiction.

Businesses should also be careful with approval delays. Many projects depend on one party reviewing documents, providing data, giving site access, approving designs, or responding to change requests. If the customer takes three weeks to approve something that should have taken three days, the vendor may be delayed through no fault of its own. A practical clause can state that deadlines are extended day-for-day for customer-caused delays, or that the schedule will be equitably adjusted when delayed approvals affect performance. This is especially helpful in website builds, custom software, manufacturing, construction, consulting, and marketing projects where client feedback can become the world’s slowest tennis match.

Finally, the clause should encourage early communication. Many delay disputes become expensive because a party waits too long to speak up. By the time the other side learns about the issue, the options are limited and trust has started packing its bags. A well-drafted clause pushes the parties to share bad news early, update each other regularly, and solve the problem while it is still manageable. That may not sound dramatic, but in contract management, boring is beautiful. Boring means the clause worked.

Conclusion

Drafting a contract clause dealing with delay in performance is not about predicting every possible disaster. It is about building a fair, practical system for deadlines, notice, excuses, extensions, damages, mitigation, cure, and termination. The best clauses do not merely say, “Don’t be late.” They explain what happens if lateness occurs, who must act, what proof is needed, and how the parties can keep the deal from sliding into chaos.

For most commercial contracts, the strongest approach is to define delay clearly, require prompt notice, separate excusable from non-excusable delay, specify remedies such as extensions or liquidated damages, and include a practical cure and termination process. That combination gives the parties flexibility without sacrificing accountability. In other words, it gives the contract a spine, a calendar, and a cup of coffee.