Termination for Convenience: When 30 Days Isn't Enough

Termination for Convenience: When 30 Days Isn't Enough

In the world of B2B contracts, the "Termination for Convenience" (TFC) clause is often treated as a standard off-ramp—a simple 30-day notice period that either party can invoke without cause. But in practice, this seemingly innocuous clause can become a legal landmine when the notice period fails to account for the realities of the underlying business relationship. As a transactional attorney, you've likely seen the fallout: a client forced to shutter operations because a key supplier walked away with only 30 days' notice, or a service provider left holding unpaid receivables after a customer terminated mid-project.

Under US common law, TFC clauses are generally enforceable as written, provided they are clear and unambiguous. However, courts will not rewrite a bad deal. If your client's contract only allows 30 days' notice for termination without cause, they are bound by it—unless the clause is unconscionable or violates public policy. The real issue is not enforceability; it's risk allocation. A 30-day TFC clause may be entirely appropriate for a month-to-month SaaS subscription, but it can be catastrophic for a multi-year infrastructure build or a complex supply chain arrangement.

When 30 Days Is a Trap

Consider a manufacturer that enters into a three-year agreement with a raw materials supplier. The supplier's TFC clause allows either party to terminate with 30 days' notice. Halfway through the term, the supplier exercises that right because it found a more lucrative buyer. The manufacturer now faces a production halt, with no legal recourse—the contract was clear. The manufacturer's only argument might be that the TFC clause was exercised in bad faith, but under US common law, most jurisdictions do not imply a duty of good faith in the exercise of an express contractual right unless the contract specifically requires it.

Another common scenario involves professional services. A consulting firm signs a one-year engagement to implement a new ERP system. The client's purchase order includes a 30-day TFC clause. After six months, the client terminates without cause, leaving the consulting firm with substantial sunk costs in personnel and software licenses. The firm cannot recover lost profits because the TFC clause explicitly eliminates liability for future fees. The result is a windfall for the terminating party and a loss for the service provider.

Negotiating a TFC Clause That Works

To avoid these outcomes, the key is to align the notice period with the parties' actual reliance interests. Here are practical drafting strategies to consider:

• Tiered Notice Periods. Instead of a flat 30 days, tie the notice period to the stage of performance. For example, 90 days during the first year of a multi-year deal, reducing to 60 days in subsequent years. This protects the non-terminating party's initial investment.
• Non-Cancellable Initial Term. Provide that the contract cannot be terminated for convenience during an initial period (e.g., the first 12 months). After that, either party may terminate with 60 or 90 days' notice. This ensures a minimum commitment while preserving flexibility.
• Wind-Down and Transition Obligations. Require the terminating party to cooperate with a reasonable transition plan during the notice period. This can include data migration, return of materials, or continued support at a negotiated rate.
• Reimbursement of Sunk Costs. If the TFC clause is triggered, require the terminating party to reimburse the other party for verifiable, non-recoverable costs incurred in reliance on the contract (e.g., dedicated equipment, pre-paid licenses, or specialized training).
• Limitation on TFC for Critical Suppliers. For contracts involving essential goods or services, consider removing the TFC clause entirely or replacing it with a "termination for cause only" provision. Alternatively, require the terminating party to pay a reasonable early termination fee.

Lessons from the Courts

Courts have consistently upheld TFC clauses that are clear and unambiguous, even when the result seems harsh. In U.S. for Use of M. DeMatteo Construction Co. v. M.E. Lyons Co., a subcontractor was terminated for convenience after 30 days' notice. The court enforced the clause, noting that the subcontractor had agreed to the risk of early termination. The only exception is where the terminating party acts in bad faith—but proving bad faith is notoriously difficult without explicit contractual language requiring it.

Practical Tip: When reviewing a TFC clause, ask your client: "If the other party terminates tomorrow, what is the minimum notice period you need to avoid a material business disruption?" The answer will often be far longer than 30 days.

Conclusion

The standard 30-day TFC clause is a default, not a best practice. For B2B relationships involving significant investment, long lead times, or irreplaceable services, 30 days is rarely enough. By negotiating tiered notice periods, transition obligations, and cost reimbursement provisions, you can transform a one-size-fits-all clause into a risk-appropriate tool. The goal is not to eliminate flexibility, but to ensure that when the off-ramp is taken, neither party is left stranded.