What a 'cure period' is and how it operates in practice

A cure period is the grace window that sits between a notice of breach and the actual end of a contract. It's the reason most termination-for-cause clauses don't operate on a hair trigger, and it's the reason most breach disputes drag on for weeks before anyone is legally out of the relationship.

Cure periods are everywhere in commercial contracts: SaaS agreements, MSAs, supply contracts, service contracts, leases. They're usually short, 10, 15, 30, sometimes 60 days, and they look like procedural boilerplate. They're not. The cure period is the mechanism that converts a private complaint into a formal legal process, and the point at which a dispute either resolves or escalates.

Most teams run into a cure period contract provision exactly once, during a moment of tension, and discover that the mechanics are less obvious than the clause made them sound. Here's how they actually work.

What the clause is doing

A typical cure period clause reads something like: "If either party materially breaches this Agreement, the non-breaching party may terminate upon written notice specifying the breach, provided that the breaching party fails to cure such breach within thirty (30) days of receiving such notice."

That sentence is stitching together four moving parts:

• A breach. Something the contract requires has not happened, or something it forbids has. The breach typically has to be material, trivial failures don't trigger cure-and-terminate rights.
• Written notice. The non-breaching party has to tell the breaching party what is wrong, in writing, through the notice mechanism the contract specifies.
• The cure window. A defined number of days during which the breaching party can fix the problem.
• Termination on failure to cure. If the window closes without the breach being fixed, termination becomes available.

The structure serves a purpose. Contracts are expensive to replace, and most commercial breaches are fixable, a missed report, a lapsed certification, a late payment, a missed SLA. Forcing the non-breaching party to give notice and wait prevents termination-by-ambush and gives both sides a structured path back to performance.

It also creates a record. If the relationship eventually ends up in front of an arbitrator or court, the notice-and-cure correspondence is the evidence of what was actually demanded and whether it was delivered.

How the clock starts

The cure period usually runs from receipt of the notice, not from sending. This detail matters more than it sounds like.

If the contract specifies notice by certified mail to a corporate legal address, the clock starts when the envelope is delivered, which may be three to five days after mailing. If the contract allows email notice to a named address, it typically starts when the email is sent, but some clauses require read receipt or acknowledgment.

A few patterns to watch for:

• Concurrent vs. sequential cure. Some clauses run the cure period inside a broader termination notice period (30-day notice, cure during those 30 days). Others require notice of breach, then a separate termination notice only if the cure fails. The difference is weeks.
• Cure period starts on notice, not on discovery. Sitting on a known breach while building a file does not advance the clock. Only the formal notice does.
• Tolling for disputed breaches. A few contracts pause the cure clock if the breaching party disputes whether a breach occurred. Most do not, the cure window runs regardless, and the breaching party has to choose between fixing the alleged breach under protest or accepting the termination risk.

When the clock starts and how it runs are details buried in the notice provisions of the contract, not in the termination section. Reading only the termination clause usually misses them.

What counts as a cure

The cure period says the breaching party can fix the breach. It usually doesn't say what "fix" means. In practice, three patterns recur:

The breach is a one-time failure. Something didn't happen that should have, a report wasn't delivered, a payment wasn't made, a deliverable was late. Cure here is usually straightforward: do the thing, document it, and the breach is cured.

The breach is ongoing. Something that should be happening continuously isn't. SLAs are being missed every week, a security control is offline, a reporting obligation has been ignored for months. Cure here is harder because stopping the ongoing failure may not be enough, some clauses require restoring the counterparty to the position they would have been in absent the breach, which can mean credits, make-good work, or remediation.

The breach is structural or irremediable. A license has been lost, a key person has left, an insolvency has occurred, a confidentiality breach has already disclosed protected information. Some breaches can't be undone, and cure periods for them are often either eliminated in the clause or become formalities, the notice goes out, the clock runs, and termination is effectively inevitable.

Well-drafted contracts often distinguish between curable and incurable breaches in the clause itself, with specific breaches (insolvency, confidentiality, IP infringement) carved out of the cure-and-terminate framework and made grounds for immediate termination. Older or more generic contracts lump everything together, which is where most disputes about "what does cure actually require" come from.

Where cure periods fail

A few failure modes are common enough to be worth naming.

Notice that doesn't meet the contract's requirements

The breach may be real and the cure deadline may have passed, but if the notice went to the wrong address, in the wrong form, or missing required content (like specifying the breach with particularity), the other side will argue the clock never started. This is the single most common technical defense to a cure-based termination.

Ambiguous breach descriptions

"You are in material breach of your obligations under this Agreement" is not a notice that starts a cure clock in most jurisdictions. The breaching party is entitled to know what specifically they are supposed to cure. Vague notices get treated as procedurally defective.

Partial cure

The breaching party fixes most of the problem but not all of it. Is the breach cured? It depends on whether the remaining failure is itself material. This is the most common source of post-cure disputes, and it's where good contracts define what "cure" looks like, full performance, retroactive credits, documented remediation, and weaker contracts leave it to interpretation.

Repeated breach

A breach gets cured. Six weeks later, the same breach happens again. Is a fresh cure period required, or does the history of prior breach eliminate the cure right? Some contracts address this directly ("no further cure periods after two prior cured breaches of the same obligation within twelve months"); most do not, and the answer gets litigated under general principles.

Cure during notice of termination, not cure before

Some clauses require the non-breaching party to first send a formal notice of termination, with the cure period running inside that notice period. Others require a separate cure notice, and only allow termination notice after the cure window closes. Mixing these up, sending the wrong notice at the wrong time, can invalidate the entire termination attempt.

How teams handle cure periods operationally

A few habits tend to correlate with clean outcomes:

• Log the cure period length alongside the notice deadline. Teams that track renewal notice windows carefully often forget that cure periods are a separate, shorter clock that can activate at any time during the contract term.
• Pre-draft notice templates. When a breach happens, the first 48 hours matter. Having a template that specifies the breach with particularity, references the correct contract section, and goes to the correct notice address avoids the technical defects that invalidate notices.
• Separate the commercial conversation from the legal one. During cure, the account manager is often still talking to the vendor while legal has sent a formal notice. Mixed signals during cure, "we're working on it together" while the clock is running, can undermine both the cure and the eventual termination.
• Document the cure attempt. If the breaching party is trying to cure, the cure itself generates evidence, delivered reports, remediation plans, paid invoices. Both sides should keep that record because it determines whether the cure was adequate.

None of this requires exotic process. It requires knowing which contracts have which cure periods, what the notice mechanics are, and who owns the clock when it starts running.

The bottom line

A cure period is not a courtesy. It's the structural bridge between a breach and a termination right, and it operates on mechanics, notice form, notice receipt, defined cure actions, that are easy to underestimate. The clauses look procedural because in most contracts they are. But when they matter, they matter completely: a correctly-invoked cure period leads to either resolution or clean termination. An incorrectly-invoked one leads to months of dispute about whether the notice was even valid.

The contracts you've already signed have whatever cure windows they have. What changes is how carefully the next one gets read, and whether the internal process for sending, tracking, and responding to cure notices is something that can survive a real dispute, not just a clean one.