The Lighthouse Contract Protocols 2026

Balanced, court-savvy clauses: A field guide to pragmatic, cooperative business dealings.

A lighthouse photo by Carol M. Highsmith (Library of Congress)

With extensive case citations, pro tips, and other notes.

For students and business people: Use this book to help understand how companies work together to get business done quickly and smoothly.

For lawyers: Break free of hamster-wheel negotiation — and get deals done faster — by adopting selected Lighthouse protocols in a binding term sheet or LOI, to reduce costs and help guard against gamesmanship. (Especially useful in smaller matters.)

Creative Commons symbol for BY (attribution required) SA (share-alike)

By DC Toedt (about), professor of practice, University of Houston Law Center; member of the State Bars of Texas (active) and California (inactive). Working draft — saved 2026-01-31T17:51Z.   Copyright © 2024-26 D. C. Toedt III; see 1.1 below for Creative Commons authorization.

•  Example 1 – an instant NDA by email: Party A: "Let's use the LCP26 NDA Protocol — agreed?" Party B: "Yes."

•  Example 2 – a quick NDA negotiation by email: Discloser: "Let's use the LCP26 NDA Protocol and and Business Associate Agreement Protocol — does that work?" Recipient: "Could we add [a specified Recipient-playbook option]?" Discloser: "Done!"

•  Bonus: Many Lighthouse protocols are written in checklist-style format as an aid to legal review of conventional contract drafts.

IMPORTANT: Don't rely on this book as a substitute for legal advice from a licensed attorney. It's provided AS IS, WITH ALL FAULTS, with no warranties express or implied. Oh, and: I'm not your lawyer unless we've entered into a written engagement agreement.

Table of contents

1. Introduction

1.1. Creative Commons distribution license

by-sa.png

This book may be reproduced and/or distributed under the Creative Commons BY-SA license 4.0: Attribution required; share any revisions in the same way. See the CC license for details.

1.2. Target readerships

This book aims to serve readers in several categories:

  • If you're a law student:
    • You likely want to get a sense for how business deals are actually done in the real world — especially deals for smaller clients, whom you might represent sooner than later in your legal career.
    • You also want to know how, as a new lawyer, you can draft contract language that will pass muster with your supervising attorney and not someday result in a [hacked]-off client and/or malpractice carrier.
    • You might well wonder whether artificial-intelligence will ruin your chances of getting decent training after graduation because AIs are taking over more of the routine work of law-firm junior associates in drafting contracts and reviewing other parties' drafts.
  • If you're a lawyer, you probably value curated clauses that you can use as issue checklists and language sources.
  • If you're a lawyer's client, chances are that sometimes you have to read, understand, and actually carry out contracts.
  • In a contract dispute, all concerned will want to quickly and accurately grasp what the parties agreed to, including:
    • the parties' managers and even senior executives;
    • their litigation counsel;
    • judges and their law clerks, reading the contract "cold"; and
    • jurors (albeit rarely).

In writing the Lighthouse protocols and elsewhere in this book, I've tried to keep in mind:

  • What tasks will these different readers be taking on?
  • For each of those tasks: How can this book help the reader get the work done faster — better — cheaper? (Business folk might recognize this as perhaps an offshoot of one aspect of design thinking, reflected in the late professor Clayton Christiansen's question: What job is your customer buying your product for?)

1.3. Client goals for contracts

Most business people would agree that they usually care about:

  • getting contracts signed as quickly as possible, because the people involved have lots else to do;
  • guarding against unscrupulous behavior by The Other Side;
  • planning for a reasonable set of what-if contingencies; and
  • building resilient commercial relationships.

And when possible, businesses prefer dealing with counterparties —

  • who're agreeable to work with; and
  • who, when challenges arise, take reasonable positions and seek amicable solutions.

For example, customers want to do business with vendors who have proved their reliability as suppliers of goods and services — especially when things get tough, such as during the COVID-19 pandemic and the attendant supply-chain disruptions. See, e.g., Xiwen Bai, Jesús Fernández-Villaverde, et al., The Causal Effects of Global Supply Chain Disruptions on Macroeconomic Outcomes: Evidence and Theory, Nat'l Bur. of Econ. Research Working Paper 32098 (NBER.org 2024); Tacy Foster, Supply chain risk pulse 2025: Tariffs reshuffle global trade priorities (McKinsey.com 2025).

And vendors prefer dealing with customers who pay on time and who provide repeat business and favorable referrals.

In that vein: The global not-for-profit trade association World Commerce & Contracting* has as one of its stated purposes "… to transform contracts and the contracting process, such that they become instruments of fair dealing, that they themselves, and the process surrounding them, promote trust, [and] generate economic benefit …." *  WorldCC (formerly the International Association for Contract and Commercial Management) has some 80,000 members representing more than 20,000 companies across 180 countries.

Unfortunately, some lawyers forget that in day-to-day contract negotiations, what clients want is not to prevail on as many points as possible, but instead:

  • to get an "OK" contract signed as quickly as possible, so they can get on with the rest of their to-do list — this is true whether you're representing a vendor or a customer;
  • to try to minimize the legal spend; and
  • to have a good experience with the other company and its people — building mutual trust as reliable business partners who could work together again and who might have each other's backs in a crunch. (See also the discussion of trust at 31.39.)

Especially for business clients, the perfect is the enemy of the good. That can sometimes be jarring to lawyers, because we're professionally socialized to focus above all on our ethical duty of "zealous advocacy" for the client's position. We sometimes misinterpreted that duty as attempting to put the client in the absolute best possible litigation position, for every conceivable situation — no matter how much the attempt might delay getting the deal done and possibly leave a bad taste in everyone's mouth.

(On that last point, see possibly the greatest lawyer cartoon of all time.)

Students: The W.I.D.A.C. Rule applies here: When in doubt, ask the client.

The Lighthouse protocols aim to support these goals

1.4. About the author

Head shot of the author, D.C. Toedt III

I’m DC Toedt, a professor of practice at the University of Houston Law Center and a practicing attorney in Houston. I’m licensed in Texas (active), California (inactive), and the U.S. Patent and Trademark Office.

(People often ask: My full name is Dell Charles Toedt III; my German-origin last name is pronouced "Tate," in the same way as former House speaker John Boehner, pronounced "BAY-ner." Because of my Roman numeral III, my family has always called me "DC.")

As a lawyer, I "came up" at Arnold, White & Durkee, a 150-lawyer intellectual property litigation firm, where I was an associate and then a partner, and was eventually elected to the management committee. We were one of the largest such firms in the United States, with offices in six different cities with significant tech industries.

I left AW&D during the dot-com boom to become vice president and general counsel of BindView Corporation, a publicly-traded, 500-employee software company, with offices in six countries. As outside counsel, I’d helped the founders start the company and joined them full-time not long after the company went public. I served there — negotiating probably hundreds of contracts — until our "exit," when we were acquired by Symantec Corporation, the world leader in our field.

Since leaving BindView I've maintained a limited solo practice helping tech companies, both established and startups. In addition, since 2010 I've taught a contract-drafting course at UH — for which this book serves as the main reading — and since 2021, an annual IP-introduction course for Rice University MBA students.

Among other past publications, I was the lead author and editor of The Law and Business of Computer Software, a one-volume treatise.

I’ve been active in bar-association work throughout my career; I also work pro bono with certain nonprofit organizations.

Both my undergraduate degree (in math, with high honors, including extensive science coursework) and law degree (law review) are both from the University of Texas at Austin.

Between college and law school, I served five years in the U.S. Navy as a nuclear-reactor engineering officer, and as one of the officers of the deck underway, aboard the aircraft carrier USS Enterprise, with two extended "Westpac" deployments, paying back a full-ride Navy ROTC scholarship at UT Austin.

Any views I might express here are my own, of course, and not necessarily those of clients, former employers, etc., etc.

2. Business- and drafting philosophy

2.1. Freaky Friday terms: Breaking free of negotiation kabuki

2.1.1. Clients get impatient with the typical lawyer approach

As a young lawyer in a big law firm, I somehow picked up the notion that, when drafting any contract:

  • you load up your draft with a wish list of things that your clients would love to get — or that could someday give your client leverage over the other side — with an eye to planning for every worst-case scenario you can think of;
  • you send your draft to the other side — which sends it back to you, marked up with their wish list;
  • in all likelihood, you and the other party go back and forth, exchanging multiple drafts and possibly doing one or more conference calls;
  • finally, you compromise somewhere.

For both parties, the overall mindset there was: If you lead off by asking for the moon, in the end you'll get more of what you wanted. This can be seen in advice from the late negotiation guru Chester L. Karrass, whose unsmiling visage could be seen in airline-magazines ads for his training courses. Dr. Karrass's namesake organization still urges parties to anchor their negotiations by aiming high with "a [b]old [f]irst [o]ffer" and then bargaining down from there.

(And of course in much the same vein is Donald Trump's best-selling 1987 book The Art of the Deal.)

Where everyday contracts were concerned, I was quickly "counseled" about a different perspective almost as soon as I joined BindView Corporation as the company's first in-house lawyer. BindView had been a long-time client (I'd helped the founder to start the company). Suddenly I was handling all of the routine negotiations with customers about our standard contract form.

That turned out to be a big time drain. And not just for me: For our sales people, who'd commonly sit in on some of my legal-negotiation calls with their customers to keep an eye on things. Whenever we negotiated our standard contract with a customer, we usually ended up conceding the same points, over and over — like hamsters running in a wheel. I soon wondered whether this was really necessary.

And our sales people had better things to do, too: Especially as the end-of-quarter cutoff date drew near, they'd have much preferred to be working on closing more deals with other customers. (If I had a nickel for every time a sales person or senior exec had asked me: Can't we just use a short contract that's reasonable for both sides? …)

2.1.2. Treat the contract draft like a (separate) product offering

Every time you send a draft contract to another party, it's as though you're trying to 'sell' the other party on a product — i.e., the contract itself — which the other party might find itself having to use years later. That realization paid off for my former company, BindView: We wanted to break out of the negotiation hamster wheel as much as possible when negotiating customer contracts. Our C-suite management agreed to try something different:

  • Over several months, whenever we negotiated workable changes in our contract, we made similar changes to our standard contract as well (with approval from the business execs, of course).
  • This resulted in our contract being a 'product' in its own right — one that, out of the box, gave customers pretty much what they wanted. (And it did so in ways that we knew that we could support operationally (and, in my judgment, didn't significantly increase the company's legal exposure.)

Moreover: I made it clear to our sales people that I wouldn't even look at a customer's contract form until the sales team got me a five-minute phone call with the customer's contract people. I told the sales people that it was my job to try to sell the customer on our contract. (That alone helped speed up our sales cycle: Sometimes we ended up having to use the customer's contract after all. But that first call with the contract people gave both sides a sense of who they were dealing with; this helped each side assess what terms could be agreed to.)

2.1.3. 'User reviews' of our contract … from customers' lawyers

A side benefit of BindView's new approach was that our (re)balanced contract form helped sell our products: Customers' lawyers began to say how much they liked our contract. This helped to validate those customers' decision to do business with us.

I started making notes of the lawyers’ favorable comments. I quoted some of the comments (anonymously) on a cover page of our contract form. Here are just a few of those comments, which I posted online some years ago; all are from conference calls:

  • From an in-house attorney for a multinational health care company: "I told our business people that if your software is as good as your contract, we’re getting a great product." (!)
  • From an in-house lawyer at a U.S. hospital chain: "I giggled when I saw the 'movie reviews' on your cover sheet. I’d never seen that before: customers saying this was the greatest contract they’d ever seen. But the comments turned out to be true."
  • From a contract specialist at a national wireless-service provider: "I told my boss I want to give your contract to all of our software vendors and tell them it’s our standard contract, but I know we can’t do that." (!)
  • From an in-house attorney at a global media company: "This is a great contract. Most contracts might as well be written in Greek, but our business guys thought this one was very readable."

2.1.4. A sales force standing ovation

A few months after BindView had begun this transition to a customer-friendly contract form, we acquired a smaller software company by the name of Entevo. After we closed the acquisition, our sales organization brought Entevo's sales people to Houston for onboarding, including training in how to sell our software. During a break at one of those sales-training sessions, our VP of worldwide sales, David Pulaski (who said I could use his name in telling this story) stuck his head in my office.

David said he'd told our new sales reps that, unlike at Entevo, at BindView we did most of our deals on just a one-page sales quotation and our clickwrap license agreement, which was customer-friendly just like our negotiable contract form. David said that our new sales reps had given him a standing ovation.

Why the standing-O? Because our new sales reps remembered how at Entevo, they'd had to use a detailed contract form that had lots of vendor-protective legalese. Not surprisingly, Entevo's customers had often insisted on negotiating the contract's legal terms and conditions, which the CFO handled. (Entevo didn't have an in-house lawyer.) That had sometimes slowed up Entevo's getting deals signed, causing some grumbling among Entevo's sales people.

So when David told the our new reps about BindView's approach, the reps instantly recognized that their work had just gotten easier: For most BindView sales oppotunities, our new reps could just quote a price; reference our clear, fair set of terms; and get the deal signed — helping the reps to make their quotas and earn commissions and club trips for themselves .

David's story has stuck with me, helping inspire the framing of this book: Fair, readable agreements help to cut deal friction — especially for smaller-dollar transactions.

2.1.5. But was it a 'safe' contract?

You might wonder whether BindView ever experienced legal- or business problems from having a balanced, customer-friendly contract form. I’ll note only that:

  • With the CEO’s permission, I talked about our contract philosophy in continuing-legal-education (a.k.a. CLE) seminars, and even included a copy of our standard form in written seminar materials;
  • We basically-never had any kind of contract-related problem with a customer when we'd used our contract form; and
  • In due course we had a successful 'exit': Having navigated through the software industry's 'nuclear winter' after the dot-com crash, we were approched and acquired by Symantec Corporation, one of the world’s largest software companies and the global leader in our field.

2.1.6. The key: Freaky-Friday terms

Freaky Friday movie poster with Lindsay Lohan in a dark suit, high heels, and a pearl necklace, and Jamie Lee Curtis with spiky hair, a denim jacket, a short skirt, and knee-high boots with an electric guitar

A useful way to write sellable contracts is to put yourself in the shoes of The Other Side. Let's (provisionally) assume that a contract clause is serviceably balanced if it provides role-swappable terms: We could define that expression as terms that A wouldn't be averse to agreeing to if A were to find itself in B's shoes (or vice versa, obviously), in the manner of the Freaky Friday movies.

Image of poster for 1983 movie Trading Places, with photo of Dan Ackroyd at left and Eddie Murphy at right

Or for readers of a certain age: where A and B are like the characters played by SNL alumni Dan Ackroyd and Eddie Murphy in the 1983 movie Trading Places (which coincidentally also featured Jamie Lee Curtis, who starred in both of the Freaky Friday movies as well).

This approach is akin to the ancient "divide and choose" procedure. That's sometimes known as "you cut, I choose," by which children can evenly divide a cookie between them. A similar approach is often used in so-called "shotgun" buy-sell agreements and in last-offer arbitration; see Protocol 21.11 for a variation. (All these approaches are grounded in the Rawlsian veil of ignorance.)

2.1.7. Freaky-Friday contract terms allow for role-swapping

Here's another potential benefit: On two different occasions, having a Freaky-Friday contract helped BindView get deals done almost immediately when we were the customer, not the vendor:

  • On those two occasions, BindView was licensing another vendor's software for our internal use.
  • The other vendor wanted to use its own software license agreement, of course. But that license agreement had problems. It would have taken considerable revision and, presumably, legal negotiation for it to work for us as the customer.
  • So, we proposed to the vendor that instead we should just use BindView's standard software license agreement — but with BindView as the customer instead of as the vendor. We said we'd be happy to live with the same terms that we asked our customers to accept.

Each time, the other vendor reviewed our license agreement and quickly agreed to our trading-places proposal.

So in the LCP26, we'll use role-swappable terms as our reference benchmarks — as neutral "rules of the road" that contracting parties can agree that they'll follow. We do this on the premise that, when clients negotiate an everyday contract, what they usually want is:

  • to get a workable deal done (preferably using a readable contract), with a reliable business partner that has incentives to behave reasonably;
  • at a reasonable legal cost and on a reasonable timeline — but sooner is always better;
  • at an acceptable level of business risk, with protections appropriate to that risk, without trying to cover every. possible. contingency;
  • without trying to play games or big-foot The Other Side;
  • while signaling their own reliability as prospective business partners; and
  • building trust, not traps.

(All this can run somewhat counter to typical law-school training: We lawyers learn to adopt something of a worst-case, adversarial mindset — and we're often inclined to draft contracts accordingly.)

2.1.8. Counterexample: A Trump building lease backfires

(I wrote this particular section a few months before Donald Trump descended a golden escalator to announce his 2016 presidential campaign.)

The Trump Corporation ("Trump") has been a real-estate landlord, among other things. According to AmLaw Daily, years ago Trump's lawyers took one of the company's leases, changed the names, and used it for a deal in which Trump was the tenant and not the landlord. Later, though, Trump-as-tenant found that its lease-agreement form gave Trump's landlord significant leverage:

"The funny part of it is what one of his internal lawyers must have done years ago," [the landlord's president] says. "Normally Trump is the landlord, not the tenant. So what they did is they took one of their leases and just changed the names. And so it's not a very favorable lease if you're the tenant." Nate Raymond, Trump Misses Rent Payments …, http://goo.gl/B72TIr (AmLawDaily.Typepad.com) (accessed Apr. 27, 2015 but no longer online, not even at archive.org — the site host, Typepad, ceased operations).

Lesson: Contract drafters will often do well to heed advice similar to that of the song Coplas on the Kingston Trio's 1958 debut album, where the in-song patter "translated" the Spanish lyrics into English: Tell your parents not to muddy the water around us: They may have to drink it soon ….

2.1.9. Freaky-Friday terms can be safer for both the parties and the drafters

Role-swappable contract terms can also pay off if the parties' roles ever do get reversed and the business people think that it's safe to use the same contract.

Here's one typical example: In many cases, a two-way confidentiality agreement ("NDA") that protects each party's confidential information is likely to be signed sooner, because:

  • each negotiator presumably keeps in mind that today's disclosing party might be tomorrow's receiving party or vice versa; and so:
  • the two-way agreement is thus likely — but not guaranteed, see 2.1.10 — to be more balanced;
  • moreover, if the parties were ever to switch roles — with the parties agreeing that the original recipient should disclose its own information to the original discloser — then a two-way agreement can avoid (what the original recipient would regard as) disaster, as discussed at 5.3.34.3.

In contrast: With a one-way nondisclosure agreement, only the originally-intended discloser's information is protected. This means that any disclosures by the original recipient might be completely unprotected — resulting in the receiving party's losing its trade-secret rights in its information.

Example: That's pretty close to what happened to one trade-secret owner: The owner had signed a confidentiality agreement with another party, but that agreement protected only the other party's information. Consequently, said the court, the owner's disclosures of its own confidential information were unprotected. See Fail-Safe, LLC v. A.O. Smith Corp. 674 F.3d 889, 893-94 (7th Cir. 2012) (affirming summary judgment for other party).

It's not hard to imagine the thought process that the owner's business people's went through: "We need to disclose our information to you. We've already got an NDA in place. So sure, let's do it." But the NDA didn't do what the plaintiff needed.

(For more about the dangers of unrestricted disclosures of confidential information, see 5.3.11.)

2.1.10. Caution: A supposedly role-swappable draft can be biased

Any agreement that's nominally two-way could still be biased in favor of the drafting party.

Example: Suppose that Fred's drafter knows that Fred will be receiving Ginger's confidential information, but Fred won't be disclosing his own confidential information. In that situation:

  1. Representing Fred as Recipient, Fred's drafter might write a "two-way" (quote unquote) confidentiality provision that provides very little protection for anyone's confidential information, because that lack of protection won't hurt Fred as Recipient — at least not in the short term.
  2. Ginger, as Discloser, would therefore have to review the confidentiality provisions carefully to make sure it contained sufficient protection for her Confidential Information.
  3. Conversely, if Ginger's drafter is doing the drafting — knowing that Ginger will be disclosing her information to Fred, but she won't be receiving Fred's information — then Ginger's drafter might craft the confidentiality provision with burdensome requirements that Fred would have to review carefully.

2.2. Communication

The biggest cause of serious error in this business is a failure of communication. Construction executive Finn O'Sullivan, quoted in Atul Gawande, The Checklist Manifesto: How to Get Things Right (2009), at 70.

The single biggest problem in communication is the illusion that it has taken place. (Mis?)attributed to George Bernard Shaw.

Contents:

2.2.1. Business disasters from poor communication

In the world of contracts, parties not communicating has often resulted extra expense — and, sometimes, deadly consequences.

The Healthcare.gov initial rollout: One of the most-embarrassing project failures ever was the initial rollout of the Healthcare.gov Web site to implement the Affordable Care Act (a.k.a. "Obamacare"). One of the root causes was poor communication practice; the successful crash project to fix the site involved frequent communication among developers and other stakeholders. See, e.g., Government Accounting Office, Healthcare.gov[:] Ineffective Planning and Oversight Practices Underscore the Need for Improved Contract Management at 37 (July 2014); Joshua Bleiberg and Darrell M. West, A look back at technical issues with Healthcare.gov (Brookings.edu Apr. 2015); Robinson Meyer, The Secret Startup That Saved the Worst Website in America (TheAtlantic.com 2015); Jennifer Pahlka, Recoding America: Why Government Is Failing in the Digital Age and How We Can Do Better (2023).

The New York City subway's train-tracking system: A proposed upgrade to the dangerously-antiquated train-tracking system in New York subways ended up grotesquely incomplete and ‑overbudget. "A post-mortem by the Federal Highway Administration details how from the start, an agency which had had little experience with large 'systems' projects tried to wing it. For instance, the consulting firm tasked with developing the project plan … didn’t talk to the workers who would be maintaining the system until after it was designed …." James Somers, Why New York Subway Lines Are Missing Countdown Clocks (The Atlantic.com 2015) (emphasis added).

An extra $100K expense: Here's a less-costly example: In a project to reconstruct a bridge, a subcontractor spent more than $120,000 above the agreed price in trying to resolve an unexpected problem. During ensuing payment litigation, the relevant parties learned that if they'd just talked to one another, they likely would agreed to an alternative approach that would have saved over $100,000 of that extra cost — and that doesn't even take into account the time and money the parties spent in litigation. See Construction Drilling, Inc. v. Engineers Construction, Inc., 2020 VT 38 ¶¶ 6-7, 236 A.3d 193, 196-97 (2020) (affirming denial of subcontractor's breach-of-contract claim).

2.2.2. Worse: Death and destruction

When parties don't communicate, it can sometimes result in death, injury, and property damage. The world has seen tragic examples of failures in this regard:

– The 2025 Potomac River mid-air collision between an Army Black Hawk helicopter and an American Airlines commuter flight, killing all 67 people aboard both aircraft;
– The Three Mile Island nuclear accident;
– The Hyatt Regency walkway collapse;
Hurricane Katrina's ravaging of New Orleans.

All were caused at least in part by communications failures.

Professionals working in these and related fields are (with any luck) trained in experience-based lessons history that, as pilots say, have often been "written in blood." Gary S. Rudman, Checklist mentality … it’s a good thing (safety.af.mil 2012).

2.2.3. Benefits of regular, structured communications

Outcomes can be greatly improved — and sometimes, catastrophe averted — by habits of pre-planned communications, such as:

  • aircraft pilots check in with air traffic control at standard points in their flights;
  • in surgeries, the surgeons announce to their teams what they're doing;
  • in nuclear reactor operations, watchstanders at various equipment stations inform the central control desk whenever they're about to change configurations.

This is a subtext of the 2009 book The Checklist Manifesto (highly recommended reading, by way), by surgeon, Rhodes scholar, and MacArthur "genius grant" recipient Atul Gawande, M.D. That book grew out of Gawande's 2007 article in The New Yorker, recounting his visit to the construction site of the Russia Wharf, a 32-floor building in Boston (now called the Atlantic Wharf).

In that visit, Gawande learned that particular, time-specific communications were an important feature of the checklists used by the general contractor's construction executives:

While no one could anticipate all the problems, they could foresee where and when they might occur. The checklist therefore detailed who had to talk to whom, by which date, and about what aspect of construction —who had to share (or 'submit') particular kinds of information before the next steps could proceed.

The submittal schedule specified, for instance, that by the end of the month the contractors, installers, and elevator engineers had to review the condition of the elevator cars traveling up to the tenth floor.

The elevator cars were factory constructed and tested. They were installed by experts. But it was not assumed that they would work perfectly. Quite the opposite.

The assumption was that anything could go wrong, anything could get missed. What? Who knows? That’s the nature of complexity.

But it was also assumed that, if you got the right people together and had them take a moment to talk things over as a team rather than as individuals, serious problems could be identified and averted. Id. at 65-66; emphasis and extra paragraphing added.

To be sure: In many types of contract, such intensive communication might well be costly overkill. But more often, the problem is too little communication.

2.3. Form follows function (or should, at least)

2.3.1. Contracts are for people, not computers

The author of a popular contract style manual once opined — wrongly — that, apart from the opening recitals, "in a contract you don’t reason or explain. You just state rules." Ken Adams, More Words Not to Include in a Contract— “Therefore” and Its Relatives, at http://www.adamsdrafting.com/therefore/ (2008).

That view would be fine — if it weren't for a few inconvenient facts:

  1. Even in a business-to-business contract, it's people, not computers, who carry out obligations and exercise contract rights. Computers do exactly as they're told, but people? Not so much — at least not always reliably. (Note: So-called digital "smart contracts" are a very-different thing.)
  2. People can forget (sometimes "conveniently") what was agreed to before. This can be especially true when individuals' personal incentives — which often are hidden — are involved (see 27.3).
  3. As time goes on, people (and thus parties) can change their minds about what they regard important. "Buyer's remorse" is just one example of this phenomenon.
  4. A contracting party's circumstances can change after the contract is signed. If that happens, the party might want (or desperately need) to back out of the deal — see, e.g., Elon Musk's unsuccessful attempt to abandon his agreement to acquire Twitter.
  5. The people who originally negotiated the business terms might not be in the same jobs. Their successors might not know why the parties agreed to the terms that they did. And again, the successors might have a different view of what's important and which obligations to honor.

2.3.2. People sometimes need to be reminded — or persuaded

The upshot: The people who will carry out a contract will sometimes need to be reminded — or even persuaded — to do the specific things called for by a contract. (Examples and explanations, see 20.21.4.1, possibly stated in footnotes, see 8.20, can serve as useful reminders on that score.)

To be sure, the famous Strunck & White drafting guide counsels writers to "omit needless words." But the operative word there is needless. The contract drafter's mission includes helping remind the parties what they agreed to — and if necessary, to help persuade them to act accordingly. Sometimes, a few extra words of explanation in a contract can help.

2.3.3. Future readers will need to be brought up to speed

Let's not forget another important group of future readers: Judges, jurors, and arbitrators will sometimes be asked to enforce a contract in a lawsuit or arbitration. The vast majority of contracts never see the inside of a courtroom, but drafters must think about the possibility — again, without going overboard or putting the client in the position of being scared of its own shadow.

–  Clarity is the first criterion: It's much easier for a court to grant an early motion to dismiss a bogus contract claim if the contract language itself refutes the claim. [DCT TO DO: Pick an example.] Likewise, if a contract clearly states that A must take Action X, and A doesn't do so, then a court is more likely to grant at least partial summary judgment on liability.

–  Tone can be a factor: Like all of us, judges and jurors can be influenced by what they think is "fair." Sometimes, the phrasing of a contract's terms can make a difference in how judges and jurors react to the parties and to the positions they're taking. (We'll see examples during the semester.)

For both clarity and tone, sometimes a few extra words can pay off. How much is "a few" is a matter of judgment to be addressed case-by-case — when in doubt, Ask the Partner! (30.5).

2.4. The Great Rule: Serve the Reader!

The hallmark of good legal writing is that an intelligent layperson will understand it on the first read. Judge Gerald Lebovits, Free at Last from Obscurity: Achieving Clarity, 96 Mich. B.J. 38 (May 2017), SSRN: https://ssrn.com/abstract=2970873.

"To serve the client, serve the reader!" should be The Great Rule of All Legal Writing — keeping mind that clients on both sides of the table would often prefer not to be reading the contract at all: They have other things on their minds — such as getting the deal "done" and moving on to other matters — and so they're frequently un-fond of having to spend time on reading the "legalese" terms and conditions.

Contracts written in dense legalese are less effective at educating or persuading readers — and those are two key missions of every contract drafter. But who is the reader? There are many possibilities — both now and in the future:

  1. business people who need to get up to speed for negotiating the contract;
  2. business people who have to carry out the contract's obligations — and those might not be the same business people who were involved in the contract negotiation, so they might well be reading the contract "cold";
  3. lawyers for one or both parties, possibly new to representing their respective clients;
  4. (unfortunately sometimes:) judges and jurors.

Apropos of that last point: Certainly the vast majority of contracts never see the inside of a courtroom. But it can't hurt to do some little things to plan for that possibility, as long as it won't increase costs or delay getting to signature, because:

  • Courts are more likely to enforce clear terms. Example: A former employee sued a company — after having signed a severance agreement that included release language. The court granted the company's motion for judgment on the pleadings, noting that "[t]he Agreement is stated in clear and unmistakable terms that are understandable to the average individual. Accordingly, the release is enforceable …." Makarevich v. USI Ins. Services, LLC, No. 1:25-cv-10434-JEK, part I, slip op. (D. Mass. Jul. 14) (granting judgment on the pleadings against pro se former employee, but with leave to amend as to any post-release claims) (emphasis added); see also order of dismissal (Aug. 5, 2025).
  • Trial counsel prefer plain language in a contract, because plain language offers better "sound bites" for trial exhibits and for use in cross-examining witnesses.
  • Plain contract language can help guide the jury in jury deliberations because the contract will normally be part of the "real" evidence in the record that the jury gets to review — the same won't always be true of trial counsel's demonstrative exhibits (summaries, PowerPoint slides, etc.) that the judge might or might not allow to be taken back into the jury room.

2.5. The Spaghetti Rule: Short, single-subject paragraphs

2.5.1. Avoid "spaghetti" clauses!

Photo of plate of spaghetti

Surely you've read contract provisions that are written as long, tangled skeins of legalese. Let's call them "spaghetti clauses."

(In the software world, "spaghetti code" is a mildly-contemptuous epithet for unstructured, hard-to-maintain source code for computer programs, sometimes also known as "rat's nests" or "big balls of mud," as opposed to more-modular "ravioli code" or "macaroni code.") See generally Spaghetti code (Wikipedia.org).

As an example: Just glance at the following two-sentence excerpt from an airline merger agreement — 309 words in the first sentence and 64 words in the second one:

[4.3] (b) Neither the execution and delivery of this Agreement by Continental nor the consummation by Continental of the transactions contemplated hereby, nor compliance by Continental with any of the terms or provisions of this Agreement, will[:] (i) assuming (solely in the case of the Merger) that the Continental Stockholder Approval is obtained, violate any provision of the Continental Charter or the Continental Bylaws or (ii) assuming that the consents, approvals and filings referred to in Section 4.4 are duly obtained and/or made, (A) violate [x] any Injunction or, [y] assuming (solely in the case of the Merger) that the Continental Stockholder Approval is obtained, any statute, code, ordinance, rule, regulation, judgment, order, writ or decree applicable to Continental, any of the Continental Subsidiaries or any of their respective properties or assets or (B) violate, conflict with, result in a breach of any provision of or the loss of any benefit under, constitute a default (or an event which, with notice or lapse of time, or both, would constitute a default) under, result in the termination of or a right of termination or cancelation under, accelerate the performance required by, or result in the creation of any Lien upon any of the respective properties or assets of Continental or any of the Continental Subsidiaries under, any of the terms, conditions or provisions of any note, bond, mortgage, indenture, deed of trust, Continental License, license, lease, agreement or other instrument or obligation to which Continental or any of the Continental Subsidiaries is a party, or by which they or any of their respective properties or assets may be bound or affected, except, in the case of clause (ii), for such violations, conflicts, breaches, defaults, terminations, rights of termination or cancelation, accelerations or Liens that would not, individually or in the aggregate, reasonably be expected to have a Material Adverse Effect on Continental. Without limiting the generality of the foregoing, as of the date of this Agreement, Continental is not a party to, or subject to, any standstill agreement or similar agreement that restricts any Person from engaging in negotiations or discussions with Continental or from acquiring, or making any tender offer or exchange offer for, any equity securities issued by Continental or any Continental Voting Debt. From https://tinyurl.com/UAL-CAL (SEC.gov); bracketed lettering added — not that it helps much. See more before-and-after examples at the Digital.gov site.

This isn't just a question of aesthetic taste: The harder it is to read and understand a draft contract:

  • the longer it will take — and the more it will cost — for the parties to review (certainly), revise (probably), and sign it; and
  • the greater the odds that a future reader might "misunderstand" the language — perhaps intentionally so.

2.5.2. Go for scanability: One substantive point per short paragraph

Each paragraph in a contract should be short AND address a single point that might require significant discussion. If that means spinning off some of the draft verbiage into separate paragraphs, then so be it. Other things being equal:

  • Short paragraphs are easier for The Other Side to review. That will help speed up getting the contract to signature, which your client will almost always appreciate. (It might also earn your client just a bit of goodwill from The Other Side.)
  • Short paragraphs are better workaday tools for business managers, and, if necessary someday, for trial counsel and judges.
  • In the future, short paragraphs can be more-easily copied and pasted into a different contract without inadvertently messing up some other clause.

As a federal-government plain language guide explains:

Short paragraphs are easier to read and understand. Long paragraphs can discourage users from trying to understand your material.

* * *

There is nothing wrong with an occasional one-sentence paragraph.

Using short paragraphs is an ideal way to open up your writing and create white space. In turn, this makes your writing more inviting and easier to read. …

* * *

Limit each paragraph or section to one topic. This makes it easier for your audience to understand your information. Each paragraph should start with a topic sentence that captures the essence of everything in the paragraph.

Putting each topic in a separate paragraph makes your information easier to digest.

So: Do this when drafting a contract:

1.  Write as many short sentences and paragraphs — "sound bites," if you will — as are needed to cover the subject.

2.  If a sentence starts to run too long for easy reading — and we all do it — then break it up. Do likewise for run-on paragraphs.

Students: In our Contract Drafting course we'll do a number of in-class exercises where you'll work together in small groups to break up some real-world spaghetti clauses.

Even if the resulting draft happens to take up a few extra pages, your client likely will thank you for it.

To be sure: Short paragraphs weren't always welcome: In the days when contracts were printed out in hard copy, many lawyers intentionally used a "compressed" format — narrow margins, long paragraphs, small print — so as to fit on fewer pieces of paper.

But those days are long gone. Nowadays, pretty much everyone reviews and even signs contracts on a screen, not on paper. So the page length is far less important to negotiation than the readability of the text.

2.5.3. Background: Why do lawyers draft spaghetti clauses?

A holdover from lawyers dictating to secretaries? In traditionally-drafted contracts, the spaghetti-clause style (see 2.5.1) might well have come from the way lawyers drafted contracts, letters, etc., in the days before desktop computers and word-processing software.

When I was a brand-new lawyer, I knew a couple of ancient attorneys — or at least I thought they were ancient; I'm probably older now than they were then — who still dictated contract language to a secretary:

  • The secretary would take down the lawyer's words on a stenographer's pad, often using Pitman or Gregg shorthand.

    (Sometimes the attorney would instead use a tape recorder such as a Dictaphone and give the tape to the secretary to type up.)

  • If in mid-dictation the lawyer was struck by a new thought, he might well say, "semicolon; provided, however, that …."
  • The secretary would type up the lawyer's dictation on a typewriter — generally with no memory features, and likely with "flimsies" (carbon paper sets) to make additional copies.
  • Any editing of typed drafts had to be done with typewriter erasers and/or Wite-Out or Liquid Paper correction fluid.
  • Retyping was time-consuming and costly; you really didn't want to have to do it if you could avoid it.

So it's easy to see how spaghetti paragraphs came to be regarded as acceptable, even as a standard of practice. Ditto for "provided, however" interruptions in spaghetti paragraphs.

In the modern era, though: While anyone might sometimes draft a spaghetti clause, there's no excuse for leaving it that way instead of breaking up the clause into shorter sound bites.

Too busy? Another possible explanation comes from famed French sage Blaise Pascal, paraphrased in English as: "If I'd had more time, I'd have shortened this letter." Blaise Pascal, Lettre XVI, in Lettres provinciales, Letter XVI (Thomas M'Crie trans. 1866) (1656), available at https://tinyurl.com/PascalLetterXVI (WikiSource.org).

(That paraphrase is itself a simplification of Pascal's original, which could be translated as, "I made this-here [letter] longer because I haven't had the leisure to make it shorter.")

Like Pascal, contract drafters are usually time-constrained, having to juggle multiple projects. So they often don't really think about whether they're hurting their clients' interests by making their work less-readable.

Caution: Is a L.O.A.D. trying to sneak in an unfavorable term? For some spaghetti clauses, there might be a less-innocent explanation: Is it possible that a L.O.A.D. — a Lazy Or Arrogant Drafter — was secretly hoping to use the MEGO factor ("Mine Eyes Glaze Over") to sneak an objectionable term past the other party's contract reviewer? This actually happens sometimes. For example, in the estimable redline.net forum (for lawyers only, membership required):

  • A lawyer recounted how he once represented a novice writer who was looking for an agent, to help the writer deal with publishers, etc.
  • One agency expressed interest in representing the writer and sent over a contract for the writer to sign.
  • But: Buried in a long paragraph was language to the effect that any work that the writer produced while the agency was representing the writer would be owned by the agency (!!!), not the writer.

The lawyer naturally advised the writer, "DO NOT SIGN."

Is the drafter trying to feel more important? Some less-secure lawyers might imagine that by using dense legalese, they'll enhance their personal prestige as High Priests of the Legal Profession, privvy to secret legal knowledge that's out of ordinary mortals' reach. That seems a dubious proposition at best — and indeed a risible one.

2.6. The BLUF Rule: Bottom Line Up Front!

A useful rule of readability, borrowed from the U.S. military, is BLUF: Bottom Line Up Front. See, e.g., Kabir Sehgal, How to Write Email with Military Precision (HBR.com 2016), archived at https://perma.cc/B986-5DUY; the byline indicates that the article's author is a U.S. Navy veteran.

Contents:

2.6.1. Use BLUF for even slightly-longish clauses

Here's a contract provision that was litigated in a state court; following the lead of the famous Where's Waldo? children's books, let's play a short game of Where's the Action Verb? and then see if we can make it more readable:

BEFORE: (just scan this — there's no need to read it)

If any shareholder of the corporation for any reason ceases to be duly licensed to practice medicine in the state of Alabama, accepts employment that, pursuant to law, places restrictions or limitations upon his continued rendering of professional services as a physician, or upon the death or adjudication of incompetency of a stockholder or upon the severance of a stockholder as an officer, agent, or employee of the corporation, or in the event any shareholder of the corporation, without first obtaining the written consent of all other shareholders of the corporation shall become a shareholder or an officer, director, agent or employee of another professional service corporation authorized to practice medicine in the State of Alabama, or if any shareholder makes an assignment for the benefit of creditors, or files a voluntary petition in bankruptcy or becomes the subject of an involuntary petition in bankruptcy, or attempts to sell, transfer, hypothecate, or pledge any shares of this corporation to any person or in any manner prohibited by law or by the By-Laws of the corporation or if any lien of any kind is imposed upon the shares of any shareholder and such lien is not removed within thirty days after its imposition, or upon the occurrence, with respect to a shareholder, of any other event hereafter provided for by amendment to the Certificates of Incorporation or these By-Laws, [ah, here we finally get to the (wordy) "bottom line"] then and in any such event, the shares of this [c]orporation of such shareholder shall then and thereafter have no voting rights of any kind, and shall not be entitled to any dividend or rights to purchase shares of any kind which may be declared thereafter by the corporation and shall be forthwith transferred, sold, and purchased or redeemed pursuant to the agreement of the stockholders in [e]ffect at the time of such occurrence. The initial agreement of the stockholders is attached hereto and incorporated herein by reference[;] however, said agreement may from time to time be changed or amended by the stockholders without amendment of these By-Laws. The method provided in said agreement for the valuation of the shares of a deceased, retired or bankrupt stockholder shall be in lieu of the provisions of Title 10, Chapter 4, Section 228 of the Code of Alabama of 1975. From Lynd v. Marshall County Pediatrics, P.C., 263 So. 3d 1041, 1044-45 (Ala. 2018) (emphasis added).

This kind of writing brings to mind a savagely-funny Dilbert cartoon about lawyers.

Let's take a stab at converting the above spaghetti paragraph into short-BLUF format:

BEFORE: See above.

AFTER: (just scan this)

(a)     A shareholder's relationship with the corporation will be terminated, as specified in more detail in subdivision (b), if any of the following Shareholder Termination Events occurs:

      (1) the shareholder, for any reason, ceases to be duly licensed to practice medicine in the state of Alabama;

      (2) the shareholder accepts employment that, pursuant to law, places restrictions or limitations upon his continued rendering of professional services as a physician

      [remaining subdivisions omitted]

(b)     Immediately upon the occurrence of any event described in subdivision (a), that shareholder's shares:

      (1) will have no voting rights of any kind,

      [Remaining subdivisions omitted]

(Emphasis added.)

Surely the AFTER: version is the more readable of the two?

An even-worse example is reproduced in the footnote — masochists are welcome to read it, but others are free to skip it.1

2.6.2. Client benefit: BLUF clauses are more memorable

Researchers at MIT conducted an experimental study (led by a career-changing Harvard law graduate) of legalese comprehension. The study's results pointed to a chief villain in legalese: "center-embedded clauses" — i.e., sentences and paragraphs where the action verb is buried in a spaghetti paragraph (see 2.5). The researchers found that such clauses "inhibited recall to [an even] greater degree than other features" such as jargon and passive voice. Eric Martínez, Francis Mollica, and Edward Gibson, Poor writing, not specialized concepts, drives processing difficulty in legal language, Cognition (2022).

2.6.3. Example: A real-world contract clause in need of BLUF work

As another illustration, here's an example of a spaghetti clause that's in serious need of rework; it's from the merger agreement by which Hewlett-Packard (HP, Inc.) acquired well-known headset manufacturer Plantronics.

(Students, you can just skim this to get the idea.)

BEFORE:

SECTION 6.07 Indemnification and Insurance. (a) All rights to indemnification, exculpation from liabilities and advancement of expenses for acts or omissions occurring at or prior to the Effective Time now existing in favor of any individual (i) who is or prior to the Effective Time becomes, or has been at any time prior to the date of this Agreement, a present or former director or officer (including any such individual serving as a fiduciary with respect to an employee benefit plan) of the Company or (ii) in his or her capacity as a present or former director or officer of one or more of the Company Subsidiaries as of the date of this Agreement (each such individual in (i) and (ii), an “Indemnified Person”) as provided in, with respect to each such Indemnified Person, as applicable, (i) the Company Charter, (ii) the Company Bylaws, (iii) the organizational documents of any applicable Company Subsidiary in effect on the date hereof at which such Indemnified Person serves as a director or officer, as applicable, or (iv) any indemnification agreement, employment agreement or other agreement made available to Parent, containing any indemnification provisions between such Indemnified Person, on the one hand, and the Company and the Company Subsidiaries, on the other hand, [ah, here comes the action verb, finally!] shall survive the Merger in accordance with their terms and shall not be amended, repealed or otherwise modified in any manner that would adversely affect any right thereunder of any such Indemnified Person with respect to acts or omissions occurring at or prior to the Effective Time.

Let's rewrite subdivision (a) above, without using spaghetti and following the BLUF Rule:

  1. Short paragraphs, with just one negotiation point per paragraph — no spaghetti paragraphs; and
  2. Bottom Line Up Front.

Oh, and while we're at it, let's help guide the reader's eye by (judiciously) bold-facing a few key words:.

AFTER: (just skim this)

SECTION 6.07   Indemnification and Insurance.

(a)  See subdivision (c) below for definitions of particular capitalized terms. [Comment: Note the forward reference to subdivision (c).]

(b) If before the Effective Time, an Indemnified Person was entitled to Protection, then after the Effective Time, that person will continue to be entitled to Protection in the same manner as before.

(c) Definitions: For purposes of this section 6.07:

      "Company Entity" refers to each of the following: (1) the Company; and (2) any of the Company Subsidiaries existing as of the date of this Agreement.

      "Indemnified Person" refers to any individual who is, or prior to the Effective Time becomes, or has been at any time prior to the date of this Agreement, in one or more of the following categories:

            (1) a present or former director or officer of any Company Entity; and/or

            (2) any individual serving as a fiduciary with respect to an employee benefit plan of any Company Entity.

      "Protection," with respect to an Indemnified Person, refers to the Indemnified Person's right to be indemnified; to be released from liability; and/or to have expenses advanced; as provided in one or more "Protection Documents" (see below).

      "Protection Document" refers to each of the following, as applicable:

            (1) the Company Charter;

            (2) the Company Bylaws;

            (3) the organizational documents of any applicable Company Entity;

            (4) any agreement — including, without limitation, any indemnification agreement and/or employment agreement — that (A) establishes one or more rights to Protection for the Indemnified Person, and (B) was made available to Parent prior to the Effective Time.

Is there any doubt which version would be easier to read, understand, negotiate, and revise? Clearly, it's the After version.

And imaging the reader's task in reviewing and thinking about the Before version ….

2.7. Looking ahead to the Age of AI

Computer programs known as artificial intelligence, or "AI," are doing more contract drafting and contract review. And it's not just lawyers who are using AIs: It can be a lot less expensive for a client to have an AI generate a contract, or to review another party's contract draft, than to pay a lawyer to do it. For an everyday‑ or low-impact transaction, the client might well decide that this is an acceptable business risk. (I've begun to see glimpses of this in my own part-time law practice.)

This increasing use of AIs presents some challenges for law schools and law firms:

  • AI programs require human oversight, because those programs can sometimes "hallucinate." For example: In the courtroom arena, numerous lawyers have found themselves in trouble because they submitted AI-drafted briefs contaning bogus citations. This famously includes President Trump's former personal lawyer Michael Cohen when he sought a reduction in his prison sentence and supervised release.2

3. General provisions

3.1. Amendments in Writing Protocol

3.1.1. Prerequisite: Signed writing with clear title

What must happen to amend the Con­tract?

An amendment to the Con­tract is effective and binding only if all of the following requisites are met:

  • 1.  Each change to the Con­tract is clearly stated in a written modification document.
  • 2.  At least one of the following is true:
    • a. The modification document is clearly titled as an amendment; and/or
    • b. The circumstances unmistakably indicate that each bound party knew that the modification document was changing the Con­tract.
  • 3.  The modification document is signed by the party that is supposedly bound by the amendment.
Note

().  Subdivision 1: It's extremely common for contracts to require amendments to be in writing, to try to avoid "he said, she said" disputes in the future. But: In some jurisdictions, a court might disregard a writing requirement; this is discussed in more detail at 10.5.4.1. (This is addressed at § 3.1.3 below.)

Subdivision 2: If a document purports to be an "amendment," that fact should be immediately obvious to the reader. Otherwise, a party to a contract might (opportunistically) claim that some random document was, surprise!, an amendment to the contract — which has led to costly litigation.

Example: The buyer of an office complex tried, and failed, to assert that an estoppel certificate, signed by a tenant, had modified the tenant's lease. See Expo Properties, LLC v. Experient, Inc., 956 F.3d 217, 224 (4th Cir. 2020) (affirming summary judgment).

Providing a clear amendment title follows the Great Rule of Contract Drafting, namely To serve the client, serve the reader! (2.4). Drafters shouldn't assume that a party would spot a contract amendment that was contained in some other type of document that the party was being asked to sign.

The Con­tract could allow unilateral amendments by notice as provided in Protocol 15.1.

Subdivision 2: Certainly it's better if all parties sign an amendment document. But ordinarily in the U.S., the law requires only the signature of the party that's supposedly bound by the amendment. Example: The Seventh Circuit once noted: "The critical signature [in an amendment] is that of the party against whom the contract is being enforced, and that signature was present." (Emphasis added.) Hess v. Kanoski & Assoc., 668 F.3d 446, 453 (7th Cir. 2012) (emphasis added).

Relatedly: Under the (U.S.) Uniform Commercial Code's statute of frauds provision in UCC § 2-201, a written contract (for the sale of goods) must be signed "by the party against whom enforcement is sought …."

And: Here's a potential footgun: If a contract states that amendments must be signed by all parties, then a missing signature could render the entire amendment unenforceable, even if the omission was inadvertent. This was the result in more than one court case, illustrating the R.O.O.M. principle — Root Out Opportunities for Mistakes (or Misunderstandings. (Or if you prefer: R.O.O.F.: Root Out Opportunities for F[oul]-ups.)

Example: In Expo Properties, cited above, the tenant's lease explicitly required both the tenant and the landlord to sign any proposed amendments of the lease — but the "estoppel certificate" in question had been signed by the tenant only, so the lease was not modified to be more favorable to the landlord.

Example: JPMorgan Chase lent money to a borrower. The loan agreement specifically said that both parties were required to sign any modification. The borrower claimed that the loan agreement had been modified — but the court said that the modification was ineffective because JPMorgan Chase never did countersign it. See Taylor v. JPMorgan Chase Bank, NA, 958 F.3d 556 (7th Cir. 2020) (affirming summary judgment).

3.1.2. Prerequisite: Minimum signature authority

Who is authorized to sign an amendment for a party?

If A signs an amendment, then the amendment is binding on A if all of the following prerequisites are met:

☒  1.  The signature was by an individual who had apparent authority to sign on A's behalf.

☒  2.  The Con­tract itself does not clearly limit who can sign amendments for A.

☒  3.  B did not have other reason to know that the individual (the signer) did not actually have signature authority.

Note

A contract between A and B might explicitly limit who is allowed to sign amendments on behalf of A — this is to put B on notice that others individuals don't have authority to sign for A, even if the doctrine of "apparent authority" might suggest otherwise. See 29.5.3 for more discussion.

3.1.3. Claims of non-written amendments

The Writing-Requirement Challenges Protocol (10.5) is incorporated by reference as part of this Protocol.

3.1.4. Additional notes

3.1.4.1. Amendments vs. waivers

Parties considering an "amendment" to the Con­tract should consider whether what they really want is simply one party's waiver (see Protocol 3.18) of a particular right or obligation.

According to Black's Law Dictionary (the canonical English-language legal dictionary), an amendment is "[a] formal and usu. [usually] minor revision or addition proposed or made to a statute, constitution, pleading, order, or other instrument …."

Here's a hypothetical example: Imagine a contract between Alice and Bob. Suppose that the contract calls for Bob to take care of Alice's lawn; Bob's obligations include mowing the lawn each week, raking leaves in the autumn, etc.

Now suppose that on one particular day, Alice comes outside to talk to Bob when she arrives to mow the lawn.

  • If Alice says, "Hi Bob — I don't need the lawn mowed this week." That's known as a waiver, by Alice, of Bob's obligation for that occasion.
  • Or, Alice might say, "never mind, Bob, I don't need you to mow the lawn ever, because my teen-aged son wants to do it from now on — so let's talk about changing the contract to reduce what you have to do and also reduce what I pay you." If Bob agrees, that's known as an amendment of their contract.
3.1.4.2. Pro tip: Consider an "amended and restated agreement" instead

Drafters: If you'll be making extensive changes to a contract — or if there have already been multiple amendments to the same contract over time — then consider doing a complete "amended and restated" agreement, with that title.

Example: The title of one Enterprise Products Partners limited-partnership agreement is, "Seventh Amended and Restated Agreement of Limited Partnership of Enterprise Products Partners L.P." (emphasis added).

Caution: If doing an amended-and-restated agreement, you'll want to consider whether you could be wiping out a provision that your client might later want to rely on. Example: That was the result in a case where:

  • an earlier contract contained a payment guaranty;
  • an amended and restated contract didn't contain the guaranty.

Presumably this was to the chagrin of the creditor that, as a result, didn't get paid. See Electronic Merchant Systems v. Gaal, 58 F.4th 877 (6th Cir. 2023) (affirming dismissal of creditor's suit against guarantor for failure to state a claim).

3.1.4.3. Pro tip: Consider an amendment number and date

In the amendment's title, strongly consider including a series number and date — and perhaps even include a (brief) mention of the amendment's purpose — to leave a paper trail, reduce the chances of confusion, and make it easier for a reader to find the amendment when skimming a list of document titles.

Example:

    Amendment

    Amendment No. 1 to Asset Purchase Agreement (Increase of Purchase Price)

If making further amendments to Amendment No. 1 itself, consider:

    Amendment No. 1 to Amendment 1 to Asset Purchase Agreement ….

    Amendment No. 1.1 to Asset Purchase Agreement ….

This is especially important to consider when multiple amendments have occurred. Example: The members of a limited-liability company ("LLC") agreed to amend the LLC's operating agreement when its managing member resigned — that amendment was the ninth one. See Paul v. Rockport Group, LLC, No. 2018-0907-JTL (Del. Ch. Jan. 9, 2024) (granting summary judgment in favor of plaintiff, the LLC's former managing member).

3.1.4.4. Pro tip: Drafting signature blocks for amendments

For tips on drafting amendment signature blocks, see 3.16 and especially 29.4 — the format would likely be exactly the same as for the contract itself.

3.1.4.5. Other reading about amendment signatures

See also Protocol 3.15 (signature-document integrity) and Protocol 3.16 (signature mechanics).

3.1.4.6. Caution: Does the amendment include a release?

Sometimes a contract will be amended to resolve a disagreement between the parties. If that happens, a release might be drafted so broadly as to cause other rights to vanish.

Example: In a federal-government contracting case, fact issues precluded summary judgment whether a contract modification had effected a release of certain other claims, so that the contractor would be barred from asserting those other claims against the government. (The parties settled the case three months thereafter.) See Fortis Indus., LLC v. GSA, CBCA 7967, slip op. at 4-5 (Sept. 18, 2024), settled (Jan. 29, 2025).

3.1.4.7. Caution: Could there be other unwanted side effects?

Drafters of amendments should watch out for possible unwanted "side effects," in which an amendment to one provision turns out to affect one or more other provisions as well. This can be a particular problem when defined terms are used, as discussed in Kidd (stephens-bolton.com, undated).

This, incidentally, is one reason for contract drafters to follow the D.R.Y. Principle (see at 30.4) — that is, Don't Repeat Yourself, usually — to try to reduce such intra-draft "dependencies," and thus the possibility for inconsistent revisions to the draft during negotiations.

3.1.4.8. Make sure to file the signed amendment!

In ongoing business relationships, contracts might be amended multiple times. At some point in the future, it might be easy to overlook a previously-signed amendment — and then be caught by surprise in a future discussion (friendly or otherwise).

For that reason, parties should save any signed amendment document in a place where it will be noticed by later readers of the contract. (This should be a routine thing for businesses already.)

3.1.4.9. Caution: A casual writing could amend a contract

Technically, a binding written document amending the Con­tract could be an exchange of emails — or even an exchange of text messages. Example: In a lawsuit between a digital ad agency and one of its clients, an e-cigarette manufacturer, an IM exchange resulted in the manufacturer's having to pay the agency more than $1 million in additional fees:

  • The crux of the IM exchange started with a message from an account executive at the ad agency: "We can do 2000 [ad placement] orders/day by Friday if I have your blessing."
  • The e-cigarette manufacturer's VP of advertising responded: "NO LIMIT"
  • The ad agency's account executive responded: "awesome!"

That series of messages served to modify the parties' contract; as a result, the e-cigarette manufacturer had to pay the ad agency the additional fees. See CX Digital Media, Inc. v. Smoking Everywhere, Inc., No. 09-62020-CIV, slip op. at 8, 17-18 (S.D. Fla. Mar. 23, 2011).

3.1.4.10. Caution: A text-message amendment could be problematic

text-message amendment might not be a good idea because:

  • it might be overlooked by the relevant business people (see 3.1.4.8);
  • it might disappear; and
  • even if it didn't disappear, it might be legally ineffective in some jurisdictions, as discussed at 28.3.3.

Similarly, writing and signing an amendment on something like a Post-It note would be inadvisable, even though technically it'd be binding if it was otherwise sufficient.

3.1.4.11. Is there sufficient "consideration" for the amendment?

Applicable law might require "consideration" (see 32.7) for amendments to existing contracts. Generally speaking, this means that each side gets at least some benefit from the amendment.

3.1.4.12. Special case: Sales of goods under the UCC

In Article 2 of the (U.S.) Uniform Commercial Code — which in general applies to transactions that are predominantly for the sale of goods — section 2-209(2) provides as follows:

(1) An agreement modifying a contract within this Article needs no consideration to be binding.

(2) A signed agreement which excludes modification or rescission except by a signed writing cannot be otherwise modified or rescinded, but except as between merchants [basically, regular buyers and sellers of goods of the kind] such a requirement on a form supplied by the merchant must be separately signed by the other party.

(3) The requirements of the statute of frauds section of this Article (Section 2-201) [which requires certain contracts to be in writing] must be satisfied if the contract as modified is within its provisions.

(4) Although an attempt at modification or rescission does not satisfy the requirements of subsection (2) or (3) it can operate as a waiver.

(5) A party who has made a waiver affecting an executory portion [i.e., a not-yet-started portion] of the contract may retract the waiver by reasonable notification received by the other party that strict performance will be required of any term waived, unless the retraction would be unjust in view of a material change of position in reliance on the waiver.

3.2. Catch-Up Calls Protocol

Many clients would be pleased if their contract relationships could look a bit like what they see in many (fictional) TV dramas: Serious, competent professionals who team up in the service of common goals; collaboratively deal with disagreements and other adversities together; and with any luck, start to develop trusted, collegial relationships.

(Cue the Beach Boys: Wouldn't it be nice, to [work] together ….)

Contents:

3.2.1. Frequency of calls

How often must we do catch-up calls?

Under this Protocol: Each party participates in a catch-up call as stated in this Protocol whenever any party reasonably asks — for example, to deal with problems and/or ‑opportunities (existing or anticipated).

Note

().  Regular communication can be one of the best ways of keeping business dealings on track, as discussed at 2.2. For that reason, parties should consider discussing whether to schedule regular catch-up calls.

This is structured as a "Rule" because the "whenever any party reasonably asks" limitation would automatically impose a natural limit:

  • In a one-off transaction, there might never be reasonable grounds to invoke this Rule.
  • In an ongoing relationship, this Rule provides a built-in channel for structured communication.

3.2.2. Video conferencing

How will we do catch-up calls — in person? By phone? By video conference?

  1. The parties use video conferencing for catch-up calls unless otherwise agreed.
  2. If A asks for the catch-up call, THEN: A gets to choose the video-conferencing platform, as long as that platform is reasonably available to B.
Note

().  When it comes to choosing a video-conferencing platform — e.g., Zoom, Teams, etc. — presumably the parties will be able to agree on that much, even if their relationship is deteriorating or even becoming hostile.

Pro tip: Parties can conside screen-sharing for "whiteboarding," which reportedly is a key business practice at AI chipmaker Nvidia. See, e.g., Amanda Liang and Willis Ke, Jensen Huang breaks bureaucracy at Nvidia with whiteboard and flat management strategies (Digitimes.com 2024).

3.2.3. Participants

Who's expected to participate in catch-up calls?

  1. For each catch-up call, each party has appropriate people participate — on any given call, who that would be would depend on the circumstances.
  2. A is not considered to have breached the Con­tract just because a particular individual from A did not participate in a catch-up call.
Note

Subdivision 2: There seems to be little purpose for a hard-and-fast rule about who must participate, because that will vary with the parties and the situation — so let's be explicit about that, In the interest of avoiding satellite disputes.

3.2.4. SPUR Agenda

What wil we talk about on a catch-up call?

In any catch-up call, the parties follow any agreed agenda — including (where agreed) the SPUR Agenda:

  • Status, both good and bad — things done and left undone;
  • Plans — including contingency plans where relevant;
  • Uncertainties, such as unknowns; untested assumptions; upsides/downsides; and
  • Reports? (by email or otherwise; e.g., to document any agreements reached).

But the parties are free to follow any agenda they want.

Note

().  Structured communications can be helpful and even crucial (see 2.2.3); this section provides a bare-bones framework.

Pro tip: As a reminder: It will often make sense to circulate:

  • proposed agenda items; and
  • advance copies of relevant documents.

3.2.5. Documentation of agreements

What if something is agreed to in a catch-up call?

A catch-up call does not modify any party's rights or obligations under the Con­tract except as stated in Protocol 3.1 (amendments) and/or Protocol 3.18 (waivers) when applicable.

Note

This language is intended to make it a breach of the Con­tract to make such an assertion, with damages for the breach being the opposing party's attorney fees and costs (see 21.18.6).

3.2.6. Meeting minutes; written readouts

Does anyone take meeting minutes? If so, how are the minutes handled?

Meeting minutes for catch-up calls — and/or merely readouts — are encouraged but not required.

Note

().  The term "readout" is used in governmental affairs for one party's brief, unilateral, written summary of a call or meeting — see, e.g., the White House "readout" of a meeting between the presidents of the U.S. and China.

A readout should list:

  • significant points discussed, and
  • any decisions made.

These can be useful for follow-up and/or future reference — and, possibly, to help future readers (e.g., litigation counsel) to reconstruct a timeline of events.

A readout could be drafted jointly, for example while screensharing during a video call.

A party's unilateral readout might have evidentiary significance, for example if it qualified as a "business record" and thus as an exception to the rule excluding hearsay, such as Fed. R. Evid. 803(6). A court, however, would normally take into account the timeliness of any given readout — and of any proposals for correction and/or additions — in assessing the readout's evidentiary value.

An emailed readout could be along the lines of the following:

[Subject line:] Bob's readout of phone call of [DATE] about [SUBJECT]

Hi Alice; it was great talking to you on the Zoom call just now. Confirming part of our discussion:

1. We discussed [blah blah blah] ….

2. We decided [blah blah blah] ….

3.  [continue with additional numbered paragraphs as needed]

Please let me know if there's anything else we need to discuss about this.

Regards, Bob

Pro tip: Any email should have an informative subject line, for easier spotting while scanning an email folder. For a call summary, the subject line might be something along the lines of: "[PARTY NAME] readout of phone call of [DATE] about [SUBJECT]," as illustrated above.

Pro tip: If circulating a readout, try not to get into what lawyers call "letter-writing wars" about what was or wasn't said, or promised, or agreed to.

Pro tip: Some video-conferencing platforms allow shared notetaking. That could make it practicable for one participant to serve as notetaker — with others offering real-time comments — and then to circulate a copy of the notes after the call. (Caution: Any party doing this should check the video-conferencing platform's terms of service and privacy policy to see whether that could: • destroy trade-secret rights; • waive attorney-client privilege, or • illegally disclose personal information, e.g., personal health information or financial information.)

3.3. Entire Agreement Protocol

3.3.1. Complete, final, exclusive agreement

What counts as part of the Con­tract?

The Con­tract (together with any subsequent amendments in accordance with the Con­tract) is the parties' complete, final, and exclusive agreement concerning the subjects addressed.

Note

().  As a contract negotiation progresses, the parties will typically send a series of emails, texts, etc., written messages going back and forth — different drafts of the contract; emails; text messages; etc. Those will often have inconsistent terms: Party A might propose a provision, Party B will reject the proposal, and perhaps the parties will compromise on a modified proposal.

For that reason, contracts often include an entire-agreement statement — a.k.a. "merger clause," a.k.a. "integration clause," a.k.a. "zipper clause." They do this to emphasize that only the final, signed agreement will count.

What this means for parties: If you want anything to count as part of the Con­tract, in most jurisdictions you have to say it in the Con­tract — or in one of the exhibits or schedules (see § 3.3.2) or documents incorporated by reference (see § 3.7).

Caution: Under California law — consistent with what Professor Geoffrey Miller calls the state's "contextualist approach":

The parties can, of course, include merger or integration clauses in their contracts in an attempt to shore up the parol evidence rule; but while these are afforded substantial respect under California law, they are not conclusive but rather considered along with other evidence of contract integration. Even if an integration clause is present and respected as regards the original terms of the contract, moreover, California recognizes relatively easy modification by course of dealing among the parties. Geoffrey P. Miller: Bargaining on the Red-Eye: New Light on Contract Theory, NYU Law and Economics Research Paper No. 08-21, at 41-42 & nn.243-45 (footnotes omitted), available at SSRN: https://ssrn.com/abstract=1129805 or http://dx.doi.org/10.2139/ssrn.1129805.

Wording choice: The "complete, final, and exclusive" phrasing here is worded with an eye to section 2-202 of the (U.S.) Uniform Commercial Code, so as to exclude "evidence of any prior agreement or of a contemporaneous oral agreement" and "evidence of consistent additional terms" (often referred to as parol evidence).

3.3.2. Exhibits; schedules; material incorporated by reference

If the Con­tract has exhibits, schedules, appendixes, etc.: What status do those materials have?

  1. If any exhibits, schedules, appendixes, etc., are attached to the Con­tract, THEN: Those exhibits, etc., as part of the Con­tract, just as if they had been included in the body of the Con­tract itself.
  2. The same is true for any external materials are clearly incorporated by reference into the Con­tract.
Note

().  Many contracts include ancillary documents such as exhibits, schedules, appendixes, annexes, addenda, and the like. Some of these ancillary documents might be entirely external to the body of the contract and be incorporated by reference (concerning which, see 3.7).

The contract should made it clear that the parties intend for such ancillary documents to be deemed part of the contract. Otherwise, the parties might have to litigate the question of just what is and isn't part of the contract.

Incorporation by reference is addressed in more detail at Protocol 3.7.

3.3.3. Merger of prior discussions

Do the parties' communications leading up to the Con­tract count for anything?

  1. All prior discussions, agreements, and other communications concerning the subject matter of the Con­tract (whether written or oral) are considered as merged into the Con­tract — and thus as having replaced, for all purposes, by the Con­tract itself.
Note

In a nutshell: Nothing is agreed until everything is agreed — this is a formulation that's commonly used in, e.g., international trade negotiations.

3.3.4. REJECTION of certain terms in purchase orders, etc.

If the other party sends a P.O. or other document with 'fine print': Does that fine print count for anything in the Con­tract?

  1. This section applies when all of the following are true:
    1. In some matter that relates to the Con­tract, A sends B a document (the "Extra Document"): this could take the form of, e.g., a customer's request for proposal or ‑quotation; a vendor's sales quotation; a customer's purchase order; a vendor's order confirmation; an invoice, etc.
    2. A's Extra Document includes its own terms and conditions ("Extra Terms," a.k.a. 'fine print').
    3. B does not clearly accept A's Extra Terms.
  2. In that situation, B is deemed to have REJECTED A's Extra Terms — at least to the extent that the Extra Terms are in addition to, or different from, the terms of the Con­tract — except as provided in § 3.3.5 below.
Note

().  Subdivision 2's rejection language has in mind the so-called "Battle of the Forms," discussed at 28.8, which happens when a customer and a supplier exchange salvos of paper with mutually-exclusive terms and conditions in the fine print. Without rejection language, one party's fine-print terms might become binding on the other party.

What does "reject" mean here? It means that the Extra Terms are not part of the Con­tract, except as provided in § 3.3.5 below.

(Students: Be sure to read 28.8.)

3.3.5. Transaction details in Extra Documents

What if an Extra Document specifies business details for a transaction?

  1. The Con­tract might contemplate multiple transactions — for example, if the Con­tract is a master purchasing agreement — where transactions are to be documented by a purchase order, statement of work, or similar Extra Document ("Transaction Document").
  2. In that variation: Any clearly-agreed business details in the Transaction Document are part of the parties' agreement for the particular transaction in question — but only if:
    • those business details are clearly stated in the Transaction Document; and
    • the circumstances clearly indicate that the parties were agreeing to those business details.
  3. For purposes of subdivision 2: The term "agreed business details" refers to transaction-specific things such as quantity, price, delivery date, specific services to be provided, and the like — all as applicable to the transaction in question — but the term does not include the terms and conditions of the Con­tract.

3.3.6. Online user agreements?

What happens if a party throws an online agreement into the mix?

  1. Situation: This section applies if one or more of B's people is asked to agree to a "clickwrap" or "browsewrap" agreement at a Website or in computer software (the "Online Terms"), where the content of the Online Terms is controlled in substantial part by A.
  2. In that situation, B is deemed to REJECT any additional- or different terms, on any subject addressed in the Con­tract, that are contained in the Online Terms.
  3. But: Subdivision 2 does not mean that B rejects commercially-reasonable provisions in Online Terms concerning proper use of an online platform, computer software, or the like, so long as those provisions are not inconsistent with the Con­tract.
Note

Concerning clickwrap and browsewrap agreements, see generally 31.5.

3.3.7. Additional notes

3.3.7.1. One use case: When the Con­tract is replacing a prior oral agreement

One not-uncommon use case for an entire-agreement clause might be if parties enter into a written confidentiality agreement, or "NDA," to replace a previous, informal, oral agreement to keep information confidential.

(For more on this point, see § 5.3.3 and 5.3.34.3 in the Confidential Information Protocol (5.3).)

3.3.7.2. Multiple contracts might be read together ("integrated").

Courts have often held that:

… where two or more written instruments are executed as a part of one transaction such instruments should, when possible, be construed together.

And this rule adheres even where the instruments do not in terms refer to each other.

Where multiple instruments are executed at the same time and are intertwined by the same subject matter, the parol evidence rule does not prevent the court from considering both or all agreements together, notwithstanding the presence of an integration clause. Montes v. National Buick GMC, 2024 UT 42 ¶ 34, 562 P.3d 688, 696 (reversing court of appeals: separate arbitration agreement was part of a car-purchase contract, even though the latter had an integration clause) (cleaned up, extra paragraphing added).

3.3.7.3. Should "no external representations" be said, too?

Background: Even with an entire-agreement provision such as that of Protocol 3.3, sometimes a party to a contract (the "claimant") will claim:

  • that the claimant was "fraudulently induced" to enter into the contract, due to oral assurances or other statements made by another party; and
  • that the other party therefore should be legally liable, even if technically the contract hasn't been breached.

Entire-agreement provisions often include "there are no other representations" language such as that above.

And in some jurisdictions, such a no-other-representations statement might be enough to preclude a party from bringing a claim for fraudulent inducement.

Example: New York law sometimes treats such "no other representations" disclaimers as inherently barring reliance on alleged external representations, and thus as barring claims of misrepresentation. But that happens only in specific circumstances, such as a transaction between large, sophisticated parties. See, e.g., Century Pacific, Inc. v. Hilton Hotels Corp., 528 F. Supp. 2d 206, 229, 230-31 (S.D.N.Y 2007) (granting defendants' motion for summary judgment dismissing misrepresentation claims), aff'd, No. 09-0545-cv, slip op. (2d Cir. Nov. 25, 2009) (summary order).

For other circumstances, the express reliance waiver of Protocol 11.7 might be necessary.

3.3.7.4. Or: State an express acknowledgement of reliance?

In some circumstances, a contract drafter might want to explicitly state that a party is not waiving reliance on outside statements but instead is indeed relying on such representations. This happened in a Third Circuit case, where the contract in suit said, in part:

The financial terms set forth in this Agreement and other obligations assumed by SodexoMAGIC hereunder are based on conditions in existence on the date SodexoMAGIC commences operations, including by way of example [Drexel's] student population; labor, food and supply costs; and federal, state and local sales, use and excise tax.

In addition, each party has relied on representations regarding existing and future conditions and projections made by the other in connection with the negotiation and execution of this Agreement. SodexoMAGIC, LLC v. Drexel University, 24 F.4th 183, 215 (3d Cir. 2022) (partially reversing summary judgment; emphasis and alterations by the court, extra paragraphing added).

3.3.7.5. Lying about future intent: "Misrepresentation"?

In the Fourth Circuit's Harrell opinion, the court summarized:

Virginia law distinguishes between[:]

  • a statement that is false when made and
  • a promise that becomes false only when the promisor later fails to keep his word.

The former is fraud, the latter is breach of contract.

Thus, whether the Harrells can recover in tort for the permitting representation depends upon the nature of the statement.

  • A statement by DeLuca to the effect of "I have already obtained the necessary permit(s)" is either true or false when made—it does not hinge on any future action—so, if false, it can support a claim for fraud.
  • Compare that to a statement by DeLuca to the effect of "I will obtain all necessary permits." That is merely a promise to do something in the future. And while it might constitute breach of contract if he fails to follow through, it cannot sustain a claim for fraud. Harrell v. Deluca, 97 F.4th 180, 190 (4th Cir. 2024) (vacating and remanding judgment for further fact findings; cleaned up, lightly edited).

In footnote 7, the court noted a special case: "There is an exception to this categorical statement in cases where promises are made with a present intention not to perform them." (Cleaned up.)

Similarly, in its Albertsons opinion, Delaware's chancery court noted the difference between a factual misrepresentation and an alleged lie about future intentions:

The gravamen of Plaintiff's fraudulent inducement claim is that Albertsons lied about its "future intent" with respect to the operation of the business post-closing.

While anti-reliance language is needed to stand as a contractual bar to an extra-contractual fraud claim based on factual misrepresentations, an integration clause alone is sufficient to bar a fraud claim based on expressions of future intent or future promises. Shareholder Repr. Serv. LLC v. Albertsons Cos., No. 2020-0710-JRS, slip op. at text acc. nn.128-29 (Del. Ch. Jun. 7, 2021) (footnotes omitted, emphasis added).

(Hat tip: Glenn West.)

And as the Texas supreme court said in Stanley Boot:

To recover for fraud, Petitioners must prove: [list of usual elements omitted]. Because the representation in this case involves a promise to do an act in the future, Petitioners also had to prove that, at the time the Bank's representative made the promise, the Bank had no intention of performing the act. T.O. Stanley Boot Co. v. Bank of El Paso, 847 S.W.2d 218, 222 (Tex. 1992) (affirming court of appeals's reversal of judgment on jury verdict against bank; cleaned up, emphasis added, citations omitted).

3.3.7.6. An entire-agreement clause wouldn't defeat a fraudulent-inducement claim

An entire-agreement clause usually won't block a claim for fraudulent inducement to enter into the contract in the first place. For that, a drafter would have to include either an express reliance waiver (see Protocol 11.7) or — in some jurisdictions only — a simple statement that there are no external representations (see § 3.3.7.3).

3.3.7.7. Exhibits are (typically) standalone documents

A contract exhibit is generally a standalone document attached to (or referenced in) a contract. Exhibits are often used as prenegotiated forms of follow-on documents such as forms of real-estate deed.

Example: In a commercial real-estate contract between ABC and XYZ, the contract might well include, as an exhibit, an agreed form of warranty deed; the contract might say the following, for example:

… At the Closing (subject to Buyer's fulfillment of Buyer's obligations under this Agreement), Seller will deliver to Buyer a general warranty deed in substantially the form attached to this Agreement as Exhibit A.

(Emphasis added.)

Example: A master services agreement (MSA) might include, as an exhibit, a starter template for statements of work (SOW) to be undertaken under the MSA.

(Caution: The MSA should not require a SOW to be in the form of the SOW exhibit. That's because, for a particular project, the parties might use a different form of SOW but still want to use the MSA.)

Exhibit numbering: Contract exhibits are commonly "numbered" as Exhibit A, B, etc., but that's just a convention. Exhibits could alternatively be numbered with numerals, such as Exhibit 1, 2, etc., or even by reference to section numbers in the body of the contract (see the discussion of schedules below). The important thing is to make it easy for future readers to locate specific exhibits.

3.3.7.8. "Schedules" are often used to list exceptions

Schedules are commonly used in contracts for disclosures of exceptions to representations and warranties in the body of the contract.

Example: In the merger agreement between software giant Symantec Corporation and BindView Corporation (of which I was vice president and general counsel), BindView warranted, among other things, that:

Article 3
Representations and Warranties of the Company

 * * * 

3.2 Company Subsidiaries. Schedule 3.2 of the Company Disclosure Letter sets forth a true, correct [sic] and complete list of each Subsidiary of the Company (each a “Company Subsidiary”). …

Other than the Company Subsidiaries or as otherwise set forth in Schedule 3.2, the Company does not have any Company Subsidiary or any equity or ownership interest (or any interest convertible or exchangeable or exercisable for, any equity or ownership interest), whether direct or indirect, in any Person.

(Italics and extra paragraphing added.)

In other words:

  • The reps and warranties in the contract set forth a baseline reference point — a benchmark, a Platonic ideal ; and
  • the schedule(s) specify the ways (if any) in which the Company (in this case, BindView) did not conform to that benchmark status.

Schedule numbering: It's conventional to number each schedule according to the section in the body of the agreement in which the schedule is primarily referenced; in the example above, Schedule 3.2 has the same number as section 3.2 of the merger agreement in which that schedule is referenced.

3.3.7.9. Other materials: Appendixes, addenda, annexes

Other materials can be attached to a contract as appendixes, annexes, and addenda; there's no single standard or convention for doing so.

3.3.7.10. Caution: Check for consistency

A contract might include one or more addenda, appendixes, exhibits, etc., with additional terms that contradict provisions in the main body of the contract. Which would control?

In an Ohio case, the body of an oil-and-gas lease included an arbitration provision, but an exhibit to the lease stated:

If any of the following provisions conflict with or are inconsistent with the printed provisions or terms of this Lease, the following provisions shall control. * * *

22.  All Disputes Decided in Harrison County Courts — All disputes the parties are unable to resolve between themselves shall be subject to a civil lawsuit. The Courts in Harrison County, Ohio (Common Pleas and County) shall have exclusive jurisdiction over all disputes. Neither party shall be able to either file or remove a case to Federal Court. Denham v. Encino Energy, LLC, 2025 Ohio 1585 ¶ 5 (reversing and remanding denial of motion to compel arbitration).

A trial court denied a motion to compel arbitration, reasoning that the exhibit language meant what it said. But the state supreme court disagreed, asserting that "[a]n arbitration clause and a forum selection clause are not necessarily mutually exclusive because arbitration and litigation are not mutually exclusive." The court distinguished another case in which an addendum had explicitly ruled out arbitration. See id. ¶¶ 19, 21-22.

(DCT note: This strikes me as legislating from the bench by simply reading the "all disputes" language completely out of the addendum provision.)

3.4. Escalation (Internal) Protocol

3.4.1. Escalation trigger

When would this Protocol govern?

  1. This Protocol comes into play any time that:
    1. the parties disagree about a matter relating to the Con­tract; and
    2. the parties' working-level people do not resolve the disagreement on their own.
  2. If either party reasonably asks, then each party escalates the disagreement one level "up" in that party's organization as stated in this Protocol.
  3. But: IF: One party's CEO (by whatever title) is already involved, THEN: This Protocol does not require that party to escalate to its board of directors (or other highest governing body).
Note

().  Mandatory internal escalation of disagreements, for all parties to a contract, can help promote early resolution — before people get irritated and mulish and start to dig their heels in. This is due to a reality of life in the business world, pointed out by three notable contract scholars: "Superiors are unlikely to look with favor on subordinates who send problems up the line for resolution. The subordinates' job is to resolve problems, not escalate them." Ronald J. Gilson, Charles F. Sabel & Robert E. Scott, Contracting for Innovation: Vertical Disintegration and Interfirm Collaboration, 109 Colum. L. Rev. 431, 470, 481 (2009), archived at https://perma.cc/TYY2-423D.

Subdivision 2: It's unlikely that too many demands for escalation would ever be a problem that requires addressing in the Con­tract. That's because The Boy Who Cried Wolf would lose credibility with the other party — and perhaps with his- or her own boss.

Subdivision 3: For smaller companies, the CEO might already be involved, and companies' boards of directors generally don't want to get involved in non-strategic contract disputes.

3.4.2. Written position statements?

The parties should do one or more of the following things —

  1. Exchange written position statements, with the goal of helping the parties' respective managements to get a first-hand, unfiltered view of each other's position; and
  2. Exchange relevant documents as early as practicable, under Protocol 5.3 (confidential information) if so agreed.
Note

().  Subdivision 1: Even just the act of producing written position statements could help the parties' people figure out what their positions really are in the disagreement; that could speed up resolution.

Subdivision 2: If litigation were to ensue, B would likely get access to many of A's relevant, non-privileged documents anyway. So it'll often make sense to just "get on with it" — perhaps under a suitable confidentiality agreement — to save time and legal expense for all concerned.

Pro tip: For greater security, the parties could agree to set up some kind of home-grown "virtual dataroom" site with restricted access, such as a Google Docs or Dropbox folder, in lieu of sending documents as email attachments.

3.4.3. Escalation to neutral?

What if escalation doesn't resolve a disagreement?

If escalation under this Protocol does not resolve a disagreement, THEN: The parties should escalate to a neutral advisor as provided in Protocol 21.11.

3.4.4. Rule 408 confidentiality

Could A use B's escalation statements against in court?

Each party A treats the other party B's communications in the escalation as settlement discussions, and thus of limited admissibility in evidence, as stated in Rule 408 of the [U.S.] Federal Rules of Evidence, and the interpretations of that rule by U.S. federal courts.

(This is the case even if Rule 408 would not otherwise apply.)

Note

Students: If you've taken Evidence, you might remember that Rule 408(b) does allow statements in settlement negotiations to be offered in court for other purposes: "The court may admit this evidence for another purpose, such as proving a witness’s bias or prejudice, negating a contention of undue delay, or proving an effort to obstruct a criminal investigation or prosecution."

3.5. Exclusivity Explicitness Protocol

3.5.1. Explicit statement

Does the Con­tract create any exclusive rights for any party?

Under this Protocol, the Con­tract does not create any exclusive rights, anywhere at any time for anyone, unless the Con­tract clearly says so.

(That is: In the Con­tract, there is no implied grant of exclusivity, for anyone, about anything.)

Note

You'd think that if a contract was silent about whether either party had an "exclusive," there wouldn't be any question about that. But disputes have sometimes arisen when a party alleges that exclusivity was implied, as discussed at 3.5.2.

3.5.2. Additional notes

3.5.2.1. Silence about exclusivity has been interpreted both ways

A contract's silence about exclusivity could be interpreted as implicitly denying or granting exclusivity.

For example: Suppose that a manufacturer and a distributor enter into an agreement for the distributor to carry one of the manucturer's products in a given territory.

  • May the manufacturer grant similar rights to other distributors?
  • May the manufacturer engage in distribution activities itself? Or must the manufacturer work exclusively through the distributor?
  • Is the distributor's right exclusive in that territory? What about for that particular product?

Courts have gone both ways on those subjects:

Example: A Rhode Island company had a contract with the state to pick up human remains and transport them to the medical examiner’s office.

  • The contract said nothing about exclusivity.
  • To save money, the medical examiner’s office started having its own people pick up some of the remains; that cut into the company’s business.
  • The company sued the state, claiming that its remains pickup contract was exclusive — and thus (said the company) the ME’s office breached the contract by having its own people pick up remains.

The case went all the way to Rhode Island's supreme court — which affirmed a trial court's rejection of the company's exclusivity claim. See JPL Livery Services, Inc. v. Dept. of Admin., 88 A.3d 1134 (R.I. 2014) (affirming trial-court judgment).

Counterexample: A contract between a manufacturer and a Wisconsin dealership was silent about whether the dealer had exclusive rights; that silence — plus the dealer's de facto exclusivity for many years — drew the parties into several years of presumably-expensive litigation in federal court, culminating in what amounted to a final judgment after a jury trial. See Kaeser Compressors, Inc. v. Compressor & Pump Repair Services, Inc. 781 F. Supp. 2d 819 (E.D. Wis. 2011) (granting in part, but denying in part, manufacturer's motion for summary judgment); 832 F. Supp. 2d 984 (E.D. Wis. 2011) (findings, conclusions, and order of judgment).

Similarly, a gravel-mining lease in Alaska was silent as to whether it was exclusive; the state's supreme court held that the lease was ambiguous about whether it was exclusive — and on remand, the trial court found that the lease was indeed exclusive. See AAA Valley Gravel, Inc. v. Totaro, 219 P.3d 153, 160-61 (Alaska 2009) (vacating and remanding trial-court decision) (footnote omitted), after remand, 325 P.3d 529 (Alaska 2014) (affirming trial-court judgment).

3.5.2.2. Exclusivity can cause business problems

It should be obvious, but if a party commits to an exclusive deal with another party, the first party would be limiting its freedom to do business with others — even though that could turn out to be important in the future.

For example: An exclusivity clause might weaken a party's future resiliency against adverse events such as the COVID‑19 pandemic, dockworker strikes, and the like: An uncooperative vendor might try to wield an exclusivity clause against a desperate customer seeking alternative sources of goods, even though the supplier might not be able to deliver. True, the customer might be able to invoke force majeure, but that could be small comfort if it led to costly litigation with the supplier.

3.5.2.3. Exclusivity clauses can have teeth

Violating an exclusivity clause can lead to serious consequences. Example: In a New York case, e-commerce giant Amazon entered into a nonbinding letter of intent ("LOI") to negotiate a lease for space in a building on the Avenue of the Americas in New York City (the "Avenue building").

  • The LOI included an exclusivity clause prohibiting Amazon from negotiating for other local space during a stated exclusivity period.
  • But while Amazon and the Avenue building owner were negotiating the formal lease, Amazon not only secretly shopped elsewhere, it signed a lease for other space — leaving the Avenue building owner stuck with the cost of extensive renovations that Amazon had requested.

The trial court granted the Avenue building owner's motion for summary judgment that Amazon had breached the LOI. See DOLP 1133 Properties II LLC v. Amazon Corporate, LLC, 2020 N.Y. Slip Op. 30274(U), No. 653789/2014 (N.Y. Sup. Ct. Jan. 6, 2020) (partly granting Avenue building owner's motion for summary judgment); see also DOLP 1133 Properties II LLC v. Amazon Corporate, LLC, No. 653789/2014, slip op. at 8 (N.Y. Sup. Ct. Aug. 17, 2015) (denying most of Amazon's motion to dismiss).

There was doubtless a "political" angle to the case — and in litigation, political considerations can indeed matter: Not even a year beforehand, Amazon had backed out on its highly-visible selection of the borough of Queens as the location of its planned second headquarters. This followed intense community backlash after the selection was announced, which was widely reported in the press. See, e.g., J. David Goodman, Amazon Pulls Out of Planned New York City Headquarters, N.Y. Times, Feb. 14, 2019.

3.5.2.4. Exclusivity could imply a duty to negotiate in good faith

A nonbinding LOI for a private-equity investment agreement included both a statement of the parties' intent to draft a definitive agreement and an exclusivity provision precluding the investment target from engaging with other prospective investors. The deal fell apart, and litigation ensued; the federal court in Manhattan held that, for pleading-sufficiency purposes, the investiment target had plausibly alleged, in its counterclaim, that the private-equity firm breached an obligation to negotiate in good faith. See Cambridge Capital LLC v. Ruby Has LLC, 565 F. Supp. 3d 420, 441, 443 (S.D.N.Y. 2021) (denying that part of Cambridge Capital's motion to dismiss counterclaim), distinguished in 37celsius Capital Partners, L.P. v. Intel Corp., No. 24-2794, slip op. at 10-11 (7th Cir. Dec. 23, 2025) (affirming summary judgment in favor of Intel).

3.5.2.5. Third parties can be "spattered" by exclusivity claims

Consider the following hypothetical situation:

  • Two parties, which we'll call "Alice" and "Bob" (following a practice in the tech world), are negotiating a contract.
  • A third party, "Carol," comes along to offer Alice a better deal.

In that situation, Bob might try to claim that Alice had implicitly agreed to negotiate exclusively with Bob for some period of time. And that, perhaps, could result in Bob's suing Carol for tortious interference with Bob's contract with Alice.

Example: That's approximately what happened in the legendary Pennzoil v. Texaco case, where in a Houston state-court trial, Pennzoil won a jury verdict of some $29 billion (in 2025 dollars) against Texaco for tortiously interfering with what the jury and the courts found to be a binding memorandum of understanding between Pennzoil and Getty Oil. The size of the verdict, and the state-law requirement that Texaco post a appeal bond of the same amount, eventually forced Texaco to file for bankruptcy protection. See Texaco, Inc. v. Pennzoil Co., 729 S.W.2d 768 (Tex. App.—Houston [1st Dist.] 1986, writ. ref’d n.r.e.).

3.5.2.6. So: Explicitly address exclusivity, either way?

What all this means:

• When you're drafting a contract, and your client is granting certain rights to another party, then it might be "cheap insurance" to use an extra word or two to specify the extent (if any) to which the grant is exclusive — or just say "non-exclusive" if that's in fact the parties' intent.

• On the other hand: If your client is getting a right of some kind, you should seriously consider stating explicitly that the grant is indeed exclusive, again assuming that’s in fact the intent.

3.5.2.7. Perhaps be clear about negotiating with a replacement?

In a 2024 federal-court case, a battery manufacturer terminated an exclusive distribution agreement for uncured breach by the distributor and sued the distributor for breach. The distributor counterclaimed, alleging (among other things) that the manufacturer had itself breached the agreement by lining up a replacement distributor before the effective date of termination. The court dismissed the counterclaim, holding:

First, the exclusivity clause did not survive the termination of the contract. … Second, the plain language of the exclusivity clause does not prohibit C&D from negotiating with another party during the lifetime of the Agreement, nor does it prevent C&D from agreeing to enter into an agreement with a third party after the termination of the Agreement. C&D Techs., Inc. v. Elliott Auto Supply Co., No. 23-2608, slip op. at part III (E.D. Pa. Sept. 27, 2024) (emphasis added).

3.5.2.8. Oh, and: Keep a copy of the contract!

Example: The owner of the Stetson cowboy hat brand found itself faced with a lawsuit by one of its licensed manufacturers and distributors, claiming that the license was supposedly exclusive. Stetson denied the claim, but ironically, Stetson reportedly couldn't find a copy of the actual license agreement. See Jef [sic] Feeley, Stetson’s Iconic Cowboy Hat Triggers Dispute With Haberdasher (Bloomberg.com 2022) (paywalled), reprinted at Stetson hats suing distributor, says sales license not exclusive (NWAOnline.com 2022).

3.5.2.9. Further reading

For a very-useful list of bullet points to consider about possible exclusivity deals — including triggers for earning, or losing, exclusivity — see Gleason & Klaber (2024)

3.6. Government Subcontract Disclaimer Protocol

3.6.1. Certification

Could a party to the Con­tract find itself bound as a government subcontractor?

Under this Protocol:

  1. By signing the Con­tract, each party A represents (see Protocol 20.34) to the other party B that:
    • A is not a party to a contract with any governmental entity,
    • where the Con­tract could reasonably be interpreted as a subcontract to that (government) contract.
  2. Exception: A would not be liable to B for breach of subdivision 1 if A showed, by clear and convincing evidence, that B definitively knew, at the time that B entered into the Con­tract, that the statements by A in subdivision 1 were not true.
Note

().  This section is a "no surprises" provision; it has in mind that:

  • subcontracts to government contracts might include mandatory "flowdown" obligations as a matter of law (concerning flowdowns, see the brief notes at § 3.6.3); and
  • neither party wants to be surprised to learn that the Con­tract includes such flowdown obligations.

    Of course, entire books have been written about government contracting and subcontracting. This Protocol aims merely to help parties spot any need to address issues that could arise in such contracts.

    Note: This disclaimer is limited to government subcontracting. That's because when you have a contract between parties A and B, party A might legitimately think that it's none of B's business whether the contract is a subcontract to another contract between A and some third party C.

3.6.2. Government reporting requirements?

By signing the Con­tract, would any party be agreeing to comply with government-reporting requirements?

Unless the Con­tract clearly states otherwise, A confirms to B that, so far as A is aware, entering into the Con­tract will not obligate B to provide any government-required reports, representations, or certifications to B or anyone else — including any of B's direct- or indirect customers (governmental or otherwise) or suppliers.

Note

This section "riffs on" concepts in § 4.1.2 of a Cisco Indirect Channel Partner Agreement.

Of course, this section doesn't preclude another party from electing to provide such items voluntarily, in its sole discretion — and it'd often be a good idea for the parties to talk about it.

3.6.3. Rejection of flowdown obligations

Each party REJECTS any subcontract flowdown requirements that might otherwise apply by entering into (1) the Con­tract, or (2) any agreement unless clearly agreed otherwise in a signed writing that explicitly cites and overrules this Protocol.

Note

Background: The term flowdown can be relevant when a contract is between a customer and a so-called "prime" contractor that is expected to use subcontractors: Some such contracts require the prime contractor to "flow down" some of the prime contractor's obligations in all subcontracts, so that subcontractors will also be required to comply with those obligations — e.g., obligations concerning equal opportunity, safety, recordkeeping, conflicts of interest, anticorruption, and the like.

Depending on the law, a subcontractor could be subject to specific requirements imposed by statute or regulation, for example:

  • equal-opportunity reporting requirements;
  • affirmative-action obligations;
  • prohibitions of various employment practices;
  • restrictions of various kinds, e.g., on assignments;
  • requirements to keep various records.

3.7. Incorporation by Reference Protocol

3.7.1. Effect of incorporation

Under this Protocol: If material is incorporated by reference into the Con­tract or any related materials (each, a "Document"); THEN: The incorporated material is part of the Document, with the same force and effect as if the material had been reproduced in full in the body of the Document.

Note

Language origin: This Protocol is adapted in part from a clause in the (U.S.) Federal Acquisition Regulations; see Clauses Incorporated by Reference, 48 C.F.R. § 52.252-2.

3.7.2. Additional notes

3.7.2.1. Caution: Be careful what you incorporate

Drafters and reviewers should do an appropriate review of any material incorporated by reference, because the material likely will have the same force and effect as though it had been reproduced in the body of the document itself — possibly with unhappy results.

Example: An LOI-style term sheet (see Protocol 3.11 and its notes) incorporated by reference a confidentiality agreement ("NDA"; see Protocol 5.3). The NDA included an exclusion of various types of damages. The Seventh Circuit held that the exclusion — incorporated by reference into the LOI despite the plaintiff's objection — precluded the plaintiff from recovering expectation damages for breach. See 37celsius Capital Partners, L.P. v. Intel Corp., No. 24-2794, slip op. at 13-14 (7th Cir. Dec. 23, 2025) (affirming summary judgment in favor of Intel).

3.7.2.2. Incorporations "must be clearly and expressly identified"

Colorado's supreme court, citing other state supreme-court opinions, noted that:

… for contract terms outside the four corners of a contract to be incorporated by reference into the contract, the terms to be incorporated generally must be clearly and expressly identified. …

General or oblique references to a document to be incorporated, in contrast, are usually insufficient to support a finding that the document was incorporated by reference. French v. Centura Health Corp., 2022 CO 20, 509 P.3d 443, ¶ 30-31 (Colo. 2022) (reversing court of appeals; extra paragraphing added, citations omitted). The French case is described in a Washington Post article: See Timothy Bella, She expected to pay $1,337 for surgery. She was billed $303,709 (WashingtonPost.com May 19, 2022).

This general rule is likely to apply with special force in insurance policies. See, e.g., ExxonMobil Corp. v. Nat'l Union Fire Ins. Co., 672 S.W.3d 415 (Tex. 2023) (reversing and remanding appeals court's reversal of summary judgent in favor of Exxon).

And wording can matter, with much depending on the court. Example: The "Warranty" section of one contract stated: "For a complete list of our Terms & Conditions and Warranty details, please visit our website at [omitted]." Affirming denial of a motion for prevailing-party attorney fees, the First Circuit noted the general consensus that for external terms to be considered part of a contract, "the contract must clearly communicate that the purpose of the reference is to incorporate the referenced material into the contract." The court held that "[t]his section did not convey a clear message that, by accepting the offer, Holsum would agree to bind itself to further promises (including the fee-shifting term)." Holsum de Puerto Rico, Inc. v. ITW Food Equip. Grp., LLC , 116 F.4th 59, 68 (1st Cir. 2024).

Similarly: The Department of Veterans Affairs asked for quotes to lease an item of surgical equipment. One vendor's representative said, in a transmittal email, "I have attached the quote with the terms and conditions [which included mandatory exercise of renewal options by the VA]; this needs to be part of the contract." That wasn't enough to incorporate the vendor's terms and conditions into the contract, said the Federal Circuit:

The contract’s expressly incorporated FAR clauses provided the agency with complete discretion in exercising the option years. If Beacon Point intended to vary the terms of these FAR clauses by incorporating its Quote’s terms and conditions into the contract, it should have ensured that the contract expressly identified* that the Quote’s terms and conditions were incorporated into the contract. Beacon Point did not do so. Instead, Beacon Point accepted a contract that references the Quote but does not clearly communicate that the purpose of the reference was to incorporate the Quote’s terms into the contract. Thus, we hold that the contract does not incorporate by reference Beacon Point’s Quote. Beacon Pt. Assoc. v. Dept. of Veteran Affairs, 139 F.4th 1306, 1310 (Fed. Cir. 2025) (affirming dismissal of vendor's appeal of denial of claim).

Lesson: Drafters would be well-advised to err on the side of explicitness.

3.7.2.3. Incorporated material should be readily accessible

If you incorporate external material by reference, but the other party can't readily identify and find the material, then a court might hold that the external material isn't not part of the contract.

Example: A contract form for the sale of hardwood flooring did not successfully incorporate "Terms of Sale," mentioned in the form, said Oklahoma's supreme court, because the contract form gave no indication where to find the referenced terms "beyond doubt" but instead made "nothing more than a vague allusion" to the terms. Walker v. BuildDirect.com Technologies, Inc., 2015 OK 30, 349 P.3d 549, 551, 554 (2015) (on certification from 10th Circuit).

Pro tip: At the very least, provide a Web link — preferably a short, easily-typed one — where the additional incorporated terms can be found.

3.7.2.4. Attachment "for general reference" might not work

When you reference external material in a contract, you'll want to be very clear that you intend to incorporate the material by reference. Example: Illustrating this point, in Facilities Cost Mgmt. (Neb. 2015):

  • An architectural-services contract stated that "[t]he Architect’s Response to the District’s Request for Proposal is attached to this Agreement for general reference purposes including overviews of projects and services."
  • But the architect firm's response to the RFP wasn't attached to the contract — for that matter, the title wasn't even as stated in the contract provision.

Agreeing with the trial court, the state's supreme court held that "[t]he expression 'for general reference purposes,' interesting though it may be [!], contrasts with a provision, common in contract law, which incorporates another document by reference. … [The contract language] simply does not incorporate [the architect firm's] responses into the contract." Facilities Cost Mgmt. Group v. Otoe Cty. Sch. Dist., 291 Neb. 642, 653-54, 868 N.W.2d 67, 71, 75 (2015) (affirming partial summary judgment but reversing and remanding on other issue); after retrial, 298 Neb. 777, 906 N.W.2d 1 (2018).

Caution: It's not hard to see, though, how another court could have held that the contract did incorporate the architecture firm's guaranteed-maximum-price response. Still, the contract's drafters, who presumably worked for the school district, might have been more clear about their client's intent.

3.7.2.5. But a clear intent to incorporate might suffice

In Al Rushaid (5th Cir. 2014), the court held that a supplier's price quotation sufficiently incorporated by reference a standard-terms-and-conditions document published by the European Engineering Industries Association (the "ORGALIME"), which contained an arbitration provision.

– The supplier's price quotation didn't expressly incorporate the ORGALIME by reference; instead, the quotation stated, "Terms and conditions are based on the general conditions stated in the enclosed ORGALIME S2000." (Emphasis added.)

– The Fifth Circuit reviewed Texas law on the point, summarizing that "when the reference to the other document is clear and the circumstances indicate that the intent of the parties was incorporation, courts have held that a document may be incorporated, even in the absence of specific language of incorporation."

The appeals court concluded that "the district court erred in holding there was no agreement to arbitrate." Al Rushaid v. National Oilwell Varco, Inc., 757 F.3d 416, 420-21 (5th Cir. 2014) (reversing denial of motion to compel arbitration) (cleaned up, citations omitted, emphasis added). To similar effect, see CSI Aviation, Inc. v. Dept. of Homeland Security, 31 F.4th 1349, 1351 (Fed. Cir. 2022) (vacating administrative decision; commercial vendor's terms and conditions were incorporated by reference into GSA contract).

3.7.2.6. Mentioning part of a document might not incorporate all of it

Drafters should pay attention to just what portion or portions of another document are being incorporated by reference. That issue made a difference in a 2015 Second Circuit decision, where:

… Addendum 5 [to the contract in question] refers only to a single specific provision in [another agreement] — the non-compete clause.

Where, as here, the parties to an agreement choose to cite in the operative contract only a specific portion of another agreement, we apply the well-established rule that a reference by the contracting parties to an extraneous writing for a particular purpose makes it part of their agreement only for the purpose specified. VRG Linhas Aereas S/A v. MatlinPatterson Global Opportunities Partners II L.P., No. 14-3906-cv (2d. Cir. July 1, 2015) (nonprecedential summary order affirming denial of petition to confirm arbitration award) (cleaned up, formatting modified).

3.7.2.7. A party might deny having received referenced documents

In a 2014 Eighth Circuit decision:

– A buyer's purchase-order form referred to an external document with additional terms and conditions, and said the document would be provided on request.

– In a subsequent lawsuit, however, the seller denied having ever received the additional document.

That led to (what had to have been) an expensive court fight over whether an arbitration provision and an indemnification provision were part of the contract.

The case gives us a nice illustration of the Battle of the Forms; the Eighth Circuit ruled that the district court should have conducted a bench trial (no jury was demanded) to make findings of fact about just who had received what contract documents, and therefore just what terms were, or were not, part of the parties' contract under UCC § 2-207. Nebraska Machinery Co. v. Cargotec Solutions, LLC, 762 F.3d 737 (8th Cir. 2014).

Lesson: It's understandable that the buyer didn't want the hassle and expense of having to provide a hard copy of its additional terms and conditions form with every purchase order. Merely offering to provide a copy of the form, though, might well have been insufficient to bind the seller to its terms. The buyer could have put itself in a stronger position in court if it had posted the form on its Web site and then included a link to the form in its printed purchase order.

3.7.2.8. Pro tip: Incorporate everything needed

Failing to incorporate everything you want into a contract could result in losing rights your client thought it had. Example: In a 2024 Third Circuit decision:

–  Nationwide online used-car dealer Carvana tried unsuccessfully to compel arbitration of a class action brought by some of its buyers.

–  Carvana had included a separate arbitration agreement in the set of agreements signed by the buyers.

The district court court held, and the Third Circuit affirmed, that the arbitration agreement was unenforceable under Pennsylvania's Motor Vehicle Sales Finance Act ("MVSFA") because the buyer's installment-sale contract did not incorporate the arbitration agreement, as required by that statute:

Under Pennsylvania's MVSFA, a contract governing an installment sale must, inter alia: (1) be in writing; (2) contain all of the agreements between a buyer and an installment seller relating to the installment sale of the motor vehicle sold; and (3) be signed by the buyer and seller.

The statute creates a one-document rule for the installment purchases of vehicles requiring that all agreements between the parties must be incorporated into the RISC [Retail Installment Sale Contract]. …

Here, the arbitration agreements exist independently of the RISCs and are therefore unenforceable. Jennings v. Carvana, LLC, No. 22-2948, slip op. (3d Cir. Mar. 21, 2024) (nonprecedential; affirming denial of Carvana's motion to compel arbitration; cleaned up, emphasis and extra paragraphing added).

Carvana's brief had pointed out (at 3) that the district court refused to enforce the parties' arbitration agreement "because the RPA [Retail Purchase Agreement] incorporated the RISC and not the other way around." The district court took it as a given that an arbitration agreement could be incorporated by reference and did not have to be reproduced in the body of the RISC.

3.7.2.9. A purchase order might implicitly incorporate text

A California appeals court case considered a purchase order that a prime contractor had issued to a subcontractor:

–  The purchase order mentioned — but did not expressly incorporate by reference — a sales quotation that the subcontractor had previously sent to the prime contractor.

–  Further down in the purchase order, though, the P.O. language referred to "the contract documents described above or otherwise incorporated herein …." (Emphasis added.)

Applying the contra proferentem rule of contract interpretation (see 11.4), albeit without using that Latin phrase — and therefore construing the quoted term in favor of the subcontractor — the court held that the phrase, "described above or otherwise incorporated" had the effect of incorporating the subcontractor's sales quotation by reference into the prime contractor's purchase order. See Watson Bowman Acme Corp. v. RGW Construction, Inc., No. F070067, slip op. at 18, 21-22 (Cal. App. Aug. 9, 2016) (affirming, in pertinent part, judgment on jury verdict awarding damages to subcontractor). Oddly, that portion of the court's opinion was not certified for publication; the published version, which omits the discussion summarized above, is at 2 Cal. App. 5th 279, 206 Cal. Rptr. 3d 281, 283 n.*.

3.7.2.10. Incorporation fits with an entire-agreement clause

Example: In one case, the Seventh Circuit rejected an argument that incorporation by reference negated a contract's entire-agreement clause. Druckzentrum Harry Jung GmbH & Co. v. Motorola Mobility LLC, 774 F.3d 410, 416 (7th Cir. 2014) (affirming take-nothing summary judgment in favor of Motorola on Druckzentrum's claims for breach of contract and fraud).

3.7.2.11. Some pros and cons of incorporation by reference

An advantage: Drafting can sometimes be speeded up, and contracts shortened considerably, by incorporating external material by reference.

A classic example is the use of the INCOTERMS (International Commercial Terms), in purchase orders, to specify:

  • how goods are to be delivered; and
  • when title and the risk of loss will pass from the seller to the buyer.

(Concerning the INCOTERMS, see generally 13.6.)

A disadvantage: It might be tempting not to review material that is incorporated by reference into a document, even though the material will almost certainly have the same force and effect as though the material had been fully set forth in the body of the document itself.

Incorporation by reference can even turn an unenforceable contract into an enforceable one. Example: The Seventh Circuit held that a particular paragraph of a confidentiality agreement "was not enforceable by itself, but it could, as that paragraph expressly contemplated, combine with subsequent writings and/or conversations and/or conduct to become enforceable." R3 Composites Corp. v. G&S Sales Corp., 960 F.3d 935, 942 (7th Cir. 2020) (reversing and remanding summary judgment).

3.7.2.12. Tangential: Incorporation by reference in corporate charters?

In 2024, Delaware's chancery court rejected a claim that a governance agreement among a corporation's shareholders — which was not available to the public — was validly incorporated by reference into the corporation's charter (i.e., the corporation's articles of incorporation, or in Texas, its certificate of formation). See Seavitt v. N-Able, Inc., 321 A.3d 516, 524 (Del. Ch. 2024) (granting partial summary judgment that certain provisions in a corporation's charter were facially invalid).

3.8. Independent Contractors Protocol

3.8.1. Purely-contractual relationship

Under this Protocol: In their relationship under the Con­tract, the parties are independent contractors; they are not each other's partners, agents, or fiduciaries — at least not because of the Con­tract — except to the limited extent, if any, that the Con­tract clearly says so.

Note

().  A customer might want to include an independent-contractor declaration in its contract with a vendor. Typically, that's because the customer won't want —

  • to have to pay overtime to the vendor's employees if the vendor doesn't do so. That could end up being a big number. For example, a medical-staffing agency was held to have misclassified nurses as independent contractors. The agency — and, it appears, the agency's owner, individually — were liable for more than $9 million in unpaid overtime and statutory liquidated damages; See Chavez-DeRemer v. Medical Staffing of America, LLC, 147 F.4th 371 (4th Cir. 2025) (affirming district court judgment after seven-day nonjury trial).
  • to pay employment taxes for the vendor's employees; or
  • to be vicariously liable, under the doctrine of respondeat superior, for vendor errors, omissions, or other actions that harm others.

Moreover, the customer won't want the vendor and/or the vendor's employees to claim that they're eligible for benefits that its customer gives to its own employees. See Vizcaino v. Microsoft Corp., 97 F.3d 1187 (9th Cir. 1996), aff'd en banc, 120 F.3d 1006, 1010-12 (9th Cir. 1997); see also Nationwide Mut. Ins. Co. v. Darden, 503 U.S. 318 (1992) (ERISA incorporates traditional agency law criteria for identifying master-servant relationships); Elizabeth Chika Tippett, Employee Classification in the Sharing Economy, in Cambridge Handbook of Law and Regulation of the Sharing Economy at 3, text acc. n.22 (2017).

Caution: There might be contracts among parties that, in another context, are partners, agents, or fiduciaries of other parties. Those will require special care to keep those parties' obligations straight.

Partners: See 3.8.3.2. Fiduciary duty: See 3.8.3.3.

3.8.2. Certain off-limits actions

  1. Party A does not take any of the following actions (this is not an exhaustive list):
    1. make a promise, representation, or warranty, supposedly on behalf of any other party B, concerning the subject matter of the Con­tract; nor
    2. hold itself out as B's employee, agent, partner, joint venturer, division, subsidiary, branch, or other representative;
  2. In addition, A does not purport to take any of the following actions (again, not an exhaustive list):
    1. hire any individual to serve as B's another party's employee or agent;
    2. set working hours or working conditions for B's party's employees or agents (as distinct from setting access hours or on-site conditions for a work site of A;
    3. choose or assign any of B;s employees to perform a task relating to the Con­tract;
    4. direct or control the manner in which any of B's employees and/or agents performs work — as distinct from specifying the result to be accomplished by that work;
    5. remove any of B's employees and/or agents from work that B assigned to them;
    6. fire or otherwise discipline any of B's employees and/or agents;
    7. incur any debt or liability that is supposedly binding B.

3.8.3. Additional notes

3.8.3.1. A court might disregard an independent-contractors statement

A court might give little or no weight to a declaration such as that this Protocol; precedent from the (U.S.) Supreme Court makes it clear that "there is no shorthand formula or magic phrase" for independent-contractor status. NLRB v. United Insurance Co., 390 U.S. 254, 258 (1968).

Example: A three-judge panel of the Ninth Circuit held that under California law, the plaintiffs in a class-action suit, who were drivers for FedEx, were employees, not independent contractors. A concurring opinion noted, somewhat acidly:

Abraham Lincoln reportedly asked, "If you call a dog's tail a leg, how many legs does a dog have?" His answer was, "Four. Calling a dog's tail a leg does not make it a leg." … FedEx was not entitled to "write around" the principles and mandates of California Labor Law …. Alexander v. FedEx Ground Package Sys., Inc., 765 F.3d at 998 (9th Cir. 2014) (Trott, J., concurring) (edited, citations omitted).

3.8.3.2. Saying "we're not partners" tries to avoid a possible danger

().  This Protocol tries to put a Band-Aid® on a common business situation that theoretically could be dangerous (although my limited research didn't indicate that actual trouble ever happened):

  • When companies do business together, their people will often refer to each other as "partners."
  • This is especially true in the sales world, where the term "channel partner" typically refers to a reseller, distributor, systems integrator, etc. that operates in "the [sales] channel."

    Why might it be dangerous for parties to refer to themselves as "partners"? Because in the U.S., an important feature of partnership, for example under Texas statute, is that "… all partners are jointly and severally liable for all obligations of the partnership …." This statement is fairly typical and is essentially a verbatim adoption of section 306(a) of the Revised Uniform Partnership Act (1997). See Tex. Bus. Org. Code § 152.304 (exceptions omitted).

    So what counts as a "partnership"? The term is typically defined, for example in a Texas statute, as follows:

… an association of two or more persons to carry on a business for profit as owners creates a partnership, regardless of whether:

1.  the persons intend to create a partnership; or

2.  the association is called a "partnership," "joint venture," or other name. Tex. Bus. Org. Code § 152.051(b) (emphasis added, exceptions omitted); see also § 152.052 (rules for determining if partnership is created). This definition is essentially a verbatim adoption of section 101(6) of the Revised Uniform Partnership Act (1997).

This means that when two parties refer to themselves as partners, they could be setting themselves up to be fully responsible for each other's debts and liabilities.

Here's a hypothetical example: Fred and Ginger decide to give dancing lessons; they rent space in a "strip mall" shopping center and remodel it to serve as a dance studio. They don't form a corporation or limited-liability company (LLC); in fact, they do no paperwork at all, other than each of them signing the lease for the studio space. Fred and Ginger sometimes refer to each other as "my partner."

But then one Sunday afternoon, when the dance studio is closed, Fred gets in his car to run a few errands — and those errands include picking up supplies for the studio. Fred runs a red light, hitting and severely injuring a pedestrian in the crosswalk.

The pedestrian likely will sue not just Fred, but also Ginger — and on the hypothetical facts here, it's not impossible that Ginger could be personally liable for the full amount of the pedestrian's medical expenses, lost wages, and pain and suffering, even though Fred was the one who ran the red light.

3.8.3.3. Why disclaim "agent" or "fiduciary" status?

Disgruntled contracting parties can toss around fiduciary-duty claims. Example: In the D.C. Circuit's 2025 Goodrich case, after the stock market dropped in the early days of the COVID-19 pandemic, an investor ordered his wealth adviser to liquidate his entire portfolio — and then, after losing millions of dollars, he sued the adviser, claiming that the adviser had breached his fiduciary duty by failing to "explain every potential downside or loss that [the investor] ultimately experienced." The court affirmed the trial court's dismissal of the investor's claims; relevant here, the parties agreed that yes, the wealth adviser was a fiduciary, but the parties' investment agreement had limited the adviser's obligations. See Goodrich v. Bank of America N.A., 136 F.4th 347, 352 (D.C. Cir. 2025) (affirming dismissal).

So, § 3.8.1 is a guardrail term: You might not want to deal with a counterparty that might someday claim that you were the counterparty's "agent" or "fiduciary" and therefore legally obligated to give the counterparty's interests priority above the first party's own interests. Example: Such a claim occurred, for example, in a case in which New York's highest court rejected a claim of breach of fiduciary duty. See Pappas v. Tzolis, 20 N.Y.3d 228, 233-34 (2012).

Example: Delaware's chancery court rejected investors' fiduciary-duty claims when the contract in question had disavowed such duties:

The LLC Agreement also included broad waivers of the WP Investors’ fiduciary duties in four provisions. It stated that the WP Investors and their affiliates owed no fiduciary or other duties to the Company or its members beyond the duty to comply with the LLC Agreement. It further provided that each WP investor was permitted to "act exclusively in . . . its own interest and without regard to the interest of any other person," so long as it complied with the LLC Agreement. Khan v. Warburg Pincus, LLC, No. 2024-0523, slip op. at 4-5, text acc. nn.16-18 (Del. Ch. Apr. 30, 2025), aff'd w/o opinion, No. 236, 2025. (Del. Dec. 9, 2025). The chancery court also rejected the plaintiff's attempt to get around the fiduciary-duty waiver: "Because the limited liability agreement leaves no room for a quasi-fiduciary theory disguised as an implied covenant claim, this case is dismissed." Id., slip op. at 2.

Example: Similarly, in a Texas Business Court case, a minority member of an LLC brought a claim for breach of fiduciary duty against the LLC's majority member and sole manager, who had expelled the minority member. But the LLC's operating agreement (known in Texas as a "company agreement") stated that "no special relationship shall exist between any Manager and the Members, and no Member or Manager shall have any duty to any Member, whether fiduciary or otherwise, except as expressly set forth herein (or in other written agreements)." The court quickly disposed of the fiduciary-duty claim as precluded by the contract provision:

Under Texas law, courts must honor the contractual terms that parties use to define the scope of their obligations and agreements, including those that restrict fiduciary duties that might otherwise exist. This is especially true when the contractual limitation arises from an arms-length business transaction between sophisticated businesspeople. This principle adheres to Texas’s longstanding public policy of freedom of contract. Tall v. Vanderhoef, 2025 Tex. Bus. 15 ¶¶ 26-27 (granting, in part, defendant's motion to dismiss; cleaned up).

Caution: A court might disregard a proclamation that "they're not our agents!" if the facts show otherwise. As with independent-contractor status, merely saying "oh, no, there's no agency relationship here" won't make it so if the parties conduct themselves otherwise. Example: This was illustrated in DISH Network (2020), a Seventh Circuit case:

  • The trial court concluded that DISH Network and its agents had violated telemarketing statutes and regulations (some 65 million violations, apparently). The court imposed a penalty on DISH of $280 million (!).
  • In (mostly) affirming the judgment, the appeals court noted that "[t]he contract [between DISH and its representatives] asserts that it does not create an agency relation, but parties cannot by ukase negate agency if the relation the contract creates is substantively one of agency." United States v. DISH Network LLC, 954 F.3d 970, 975 (7th Cir. 2020) (citation omitted, emphasis edited).

    Caution: Even with a disclaimer like this, a court could find that a "fiduciary" relationship had arisen from the partiular facts, for example if one party "exercises excessive control" over another. This was illustrated in a case in which a federal district court denied lender-defendants' motions for summary judgment: The court said that "[i]f a lender exercises excessive control over a borrower, … a lender can assume the role of a fiduciary rather than a mere creditor" and that "the evidentiary record … cumulatively serve[s] to demonstrate, at the very least, a triable question of Wallis Bank assuming the role of fiduciary rather than mere creditor through myriad actions that demonstrate excessive control." Beaumont Lamar Apartments, LLC v. Wallis Bank, No. 4:23-cv-00341-O, slip op. at part III.B.2 (N.D. Tex. Feb. 6, 2024) (cleaned up, lightly edited).

3.8.3.4. BTW: A principal can (usually) act without using its agent

By the way ("BTW"): Suppose that Alice and Bob enter into a contract. If Alice is found to be Bob's "agent," then (in general) Alice may deal with third parties, e.g., Carol, on Bob's behalf and make contractual commitments to Carol that are legally binding on Bob.

(For that reason, in Bob's contract with Alice, Bob might want to state specifically that Alice isn't her agent, as in § 3.8.3.3.)

And now let's suppose that Alice and Bob agreed that Alice would be Bob's agent, and in fact, Bob's exclusive agent: Even under those circumstances, at least under Texas law, Bob would still be free to make a deal with Carol without getting Alice involved and without paying Alice any kind of commission.

Example: In a 2022 Texas case:

  • Two Houston lawyers wanted to change law firms; they engaged a recruiting firm, on an exclusive-agency basis, to find them new law-firm positions.
  • But the lawyers joined a law firm on their own, as a result of personal contacts, without going through the recruiting firm.
  • The recruiting firm sued the lawyers, seeking the commission that the recruiting firm would have earned if the lawyers had found another position through the recruiting firm instead of on their own.

The court rejected the recruiting firm's commission claim, citing Supreme Court of Texas authority about the distinction between an exclusive agency and an exclusive right to deal. See USPLC, LC v. Gaas, No. 01-20-00604-CV, slip op. at part C (Tex. App. Houston [1st Dist.] Aug. 30, 2022), citing Alba Tool & Supply Co. v. Indus. Contractors, Inc., 585 S.W.2d 662, 664 (Tex. 1979).

3.8.3.5. The Biden- and Trump administrations' tug-of-war guidance

In January 2024, the U.S. Department of Labor announced the finalization of a revised rule to undo a Trump adminstration last-minute definition of independent-contractor status:

The new "independent contractor" rule restores the multifactor analysis used by courts for decades, ensuring that all relevant factors are analyzed to determine whether a worker is an employee or an independent contractor.

The rule addresses six factors that guide the analysis of a worker’s relationship with an employer, including any opportunity for profit or loss a worker might have; the financial stake and nature of any resources a worker has invested in the work; the degree of permanence of the work relationship; the degree of control an employer has over the person’s work; whether the work the person does is essential to the employer’s business; and a factor regarding the worker’s skill and initiative.

The rule separately rescinds the [Trump administration's] 2021 Independent Contractor Rule that the department believes is not consistent with the law and longstanding judicial precedent. See News Release (DOL.gov 2024) (formatting edited); see generally, e.g., MacDonald et al. (Littler.com 2024).

The Biden DOL's announcement was not greeted with universal acclaim; as one management-side law firm posted, the final rule "skew[s] the inquiry in favor of employee status. … While on the one hand this [six-factor test] may seem to lead to greater flexibility, it blurs lines, leads to inconsistent results, and provides businesses and workers little of the clarity that rulemaking on worker status was supposed to provide." McKinley & Winnick (Seyfarth.com 2024).

Unsurprisingly, in 2025 the second Trump administration changed things yet again, as summarized by another management-side law firm:

As expected with a change in the White House, and as very recently foretold in Department of Labor court filings, the Trump DOL announced via a Field Assistance Bulletin on May 1 that it will no longer enforce a 2024 Biden-era independent contractor rule under the Fair Labor Standards Act (FLSA).

While this announcement does not formally rescind the Biden-era rule, the DOL explained that it will be reconsidering the rule, and it is virtually certain that the DOL will dramatically change or replace the rule when its review is completed. Michael Gotzler, DOL Hits Pause on Enforcement of Biden-Era Independent Contractor Rule, Suggests New or Changed Rule Forthcoming (Littler.com).

3.8.3.6. The Biden Administration's NLRB weighed in …

In 2021, the then-new general counsel of the National Labor Relations Board, Jennifer Abruzzo, appointed by President Biden that she intended to revisit a number of employer-friendly decisions from the Trump-era Board about independent-contractor status, notably including SuperShuttle DFW, Inc., 367 NLRB No. 75 (2019).

Then in 2023, the Board issued its Atlanta Opera decision (372 NLRB No. 95), overruling SuperShuttle DFW and holding that "in the context of weighing all relevant, traditional common-law factors, including those identified in the Restatement, the Board will also consider whether the evidence tends to show that the putative independent contractor is, in fact, rendering services as part of an independent business." The Board's Atlanta Opera decision was summarized by MacDonald & Veslinovic (2023).

At this writing (January 2026), I can't find anything online to indicate that the Trump 2.0 NLRB has taken action to revisit this issue. That's likely due to the fact that the Board currently doesn't have a quorum: President Trump purported to fire Biden-appointed Board member Gwynne Wilcox (he also fired the Board's general counsel Abruzzo) just a week after he returned to the White House.

3.8.3.7. The IRS's guidance

The [U.S.] Internal Revenue Service's Web site offers easy-to-read guidance about what the Service considers in determining whether someone is an employee — for whom the employer must pay certain taxes — or an independent contractor.

3.8.3.8. A California statute defines "employee" (vice contractor) status

In 2019, the California legislature enacted a statute, known as AB 5, which added a new section 2750.3 (later repealed) to the California Labor Code, setting out a three-part initial test for whether someone is an independent contractor instead of an employee. The statute, however — and a subsequent amendment — goes on to set forth carve-outs for certain occupations that are worth a careful review. The statutory list of carve-outs from AB 5 was expanded in a subsequent bill, AB 2257; see, e.g., Gross & Rodine (2019); Kim et al. (2020).

Example: Gig-economy companies Uber, Lyft, and others didn't take California's AB 5 lying down: They funded Proposition 22, a ballot initiative classifying certain app-based drivers as independent contractors. That initiative passed with more than 58% of the vote.

3.8.3.9. Caution: Check state- and even city laws and ordinances

Pro tip: Companies wanting to do business with freelance workers as "independent contractors" should check whether any state- or local laws might govern such dealings. Here's a ChatGPT link that might be helpful in your research.

California's Freelance Worker Protection Act gives certain "freelance workers" various protections by requiring written contracts, prompt payment, among other things. See Cal. Bus. & Prof. Code §§ 18100–18107.

Los Angeles has layered on its own ordinance, see Los Angeles Mun. Code Ord. No. 187782, including a model contract and a rules-and-procedures manual. (This might have been motivated in part by the extensive use of freelancers in the film- and music industries; see Scott (2023).)

Minneapolis implemented its own ordinance beginning in 2021, as noted by Kalk & Sandahl (2021).

New York City has its Freelance Isn't Free Act, Local Law 140 of 2016, which:

… establishes and enhances protections for freelance workers, specifically the right to:

  • A written contract
  • Timely and full payment
  • Protection from retaliation

The law establishes penalties for violations of these rights, including statutory damages, double damages, injunctive relief, and attorney’s fees. Copied and pasted from this summary published by the NYC Department of Consumer and Worker Protection.

3.9. Lawyer Involvement Protocol

The first thing we do is, let's kill all the lawyers. William Shakespeare, Henry VI, Part 2 Act IV, Scene II (by the murderous Dick the Butcher — which of course was an indirect compliment to lawyers' crucial role in civilized society).

Contents:

3.9.1. Lawyers upon request

  1. B provides A with current contact information for B's legal counsel (if any) whenever A makes a reasonable request In connection with a matter relating to the Con­tract.
  2. If B employs in-house counsel, then any such request by A for such contact information is deemed to be reasonable.
Note

().  Sometimes, party B's business people might refuse to get B's lawyers involved, or even to put party A in touch with B's lawyers. That could be due to embarrassment, or fear of what might get back to superiors — see the related discussion of this fear at Protocol 3.4 — or perhaps just a desire to save money on legal fees.

To help each party to deal with such situations, this Protocol gives B a bit of leverage: A can tell B's business people, "you do realize that by refusing to get your lawyer involved, you're in breach of contract for that alone, right?"

Subdivision 2: If B has in-house counsel, then any request by A to talk to B's in-house counsel is reasonable — not least because B's in-house counsel would always be free to cut off the discussion if A was being unreasonable.

3.9.2. Copying each other's clients

  1. If asked by either A or A's legal counsel: B instructs B's legal counsel (if any) not to object if one or more of A's lawyers open-copy B's business people on emails, texts, and other written communications.
  2. A's legal counsel always open-copy B's legal counsel when they copy B's business people .
  3. A's lawyer(s) don't copy B's business people in a manifestly-inappropriate way.
Note

().  Background: The context here is that, except in limited circumstances, ABA Model Rule 4.2 prohibits a lawyer from communicating directly with a party that the lawyer knows to be represented, in the matter in question, by another lawyer. But: This is clarified in Formal Opinion 503, issued in 2022 by an ABA standing committee on ethics; that opinion states that absent special circumstances, a "reply all" email is considered to have implicit consent.

DCT note: To be sure: It's a bad thing for one party's lawyer to try to exert undue influence on another party by going behind the back of the other party's lawyer. But: In commercial transactions, it could slow up the parties' dealings if B's lawyer insisted that A's lawyer not copy B's business people on emails.

That once happened to me: Another party's lawyer — a longtime sole practitioner — forbade me to open-copy his client on emails I sent to him, even when I was copying my own client on the email. He also refused to copy my client on his emails to me; that meant that I had to notice that my client hadn't been copied and then forward his emails to my client. Sheesh.

Moreover, that other lawyer originally sent his emails to me in encrypted form, which meant that I'd have had to create an account with some service I'd never heard of in order to get his emails decrypted. I put my foot down on that one, because it was indisputably overkill; he relented and sent his emails the usual way.

3.9.3. No attorney-fee obligation

The parties' agreement to this Protocol does not imply that B must pay or reimburse A's attorney fees if B asks for A's attorney(s) to get involved.

Note

This is intended as a guardrail — but some other provision might require such reimbursement.

3.11. Letter of Intent Protocol

Letters of intent ("LOIs") are quite common in merger- and acquisition ("M&A") transactions, but they're sometimes used in commercial transactions that have a long "take-off runway" before the final agreement will be signed. (See 3.11.6.1 for some reasons parties might use an LOI in a commercial transaction.)

3.11.1. The Con­tract as "LOI"

  1. When this Protocol is agreed to, the Con­tract is a partially-binding "letter of intent," or "LOI" — that is, a partial, strictly-preliminary, provisionally-agreed document concerning a possible future business arrangement (an "Arrangement") that the parties are discussing.
  2. Some of the Arrangement's material terms have not been agreed to by all parties.
Note

This section performs one of the most important functions of an LOI by helping to establish that A and B haven't yet agreed to be bound, because a binding LOI could have serious consequences. See, e.g., Stackpole Int’l Engineered Prods., Ltd.v. Angstrom Auto. Grp., 52 F.4th 274 (6th Cir. 2022) (affirming judgment on jury verdict that party had breached letter of intent).

Here's a Houston-famous (albeit tangential) example: Oil giant Texaco — a stranger to a corporate-acquisition transaction — learned this the (very) hard way in the 1980s, when a jury hit Texaco with a damages verdict of some $29 billion (in 2025 dollars) for swooping in and acquiring Getty Oil after Getty had signed what was ruled to be a binding "memorandum of understanding" (tantamount to an LOI) between Pennzoil and Getty Oil. See Texaco, Inc. v. Pennzoil Co., 729 S.W.2d 768 (Tex. App.—Houston [1st Dist.] 1986, writ. ref’d n.r.e.); see generally Robert M. Lloyd, Pennzoil v. Texaco, Twenty Years After: Lessons for Business Lawyers, 6. Transactions: Tenn. J. Bus. L. 321 (2005).

So by explicitly disclaiming any binding intent, an LOI can provide some breathing room. For additional discussion, see, e.g., Brown & Grinnell (2020) (real-estate LOIs); Jaskolka & Strnad (2020); Cathy Hwang, Faux Contracts, 105 Va. L. Rev. 1025, 1053-55 (2019) (summarizing interviews with numerous practicing attorneys).

3.11.2. Prerequisite: Final, signed, written agreement

No party is bound concerning the Arrangement unless and until all parties have signed and delivered a final, definitive written agreement (a "Final Agreement") that sets out all agreed, material terms.

Note

Colloquially: Nothing is agreed until everything is agreed. Court cases have made it pretty clear that language along these lines should usually be enough to keep prior written exchanges from being binding. See, e.g., Chalker Energy Partners III, LLC v. Le Norman Operating LLC, 595 S.W.3d 668, 670, 673 (Tex. 2020) (reversing court of appeals; in view of no-obligation clause in confidentiality agreement, subsequent email exchange fell short of a binding agreement); Energy Transfer Partners, L.P. v. Enterprise Products Partners, 593 S.W.3d 732 (Tex. 2020), affirming 529 S.W.3d 531 (Tex. App. Dallas 2017) (disclaimer in LOI precluded claim of de facto partnership).

  • Example: The Seventh Circuit observed that under Illinois law, "a document can be a contract without calling itself a contract; many letters of intent create contractual rights. But when a document says it isn't a contract, it isn't a contract." BPI Energy Holdings, Inc. v. IEC (Montgomery), LLC, 664 F.3d 131, 136 (7th Cir. 2011) (emphasis added).
  • Example: From a policy perspective: The Seventh Circuit explained the reason for not holding parties to be bound when they have explicitly stated their intent not to be bound: This frees the parties up to negotiate contracts one issue at a time "without the risk that a jury will think that some intermediate document is a contract, and without the fear that by reaching a preliminary understanding they have bargained away their privilege to disagree on the specifics." PFT Roberson, Inc. v. Volvo Trucks North America, 420 F.3d 728, 730, 733 (7th Cir. 2005) (Easterbrook, J.) (reversing denial of judgment as a matter of law in favor of defendant Volvo after jury verdict awarding plaintiff more than $5MM).

3.11.3. Some binding terms

Any terms in the LOI — if any — concerning the following subjects (listed alphabetically) are binding:

  1. confidentiality of the parties' discussions about the Arrangement; See Protocol 5.3.
  2. exclusivity of those discussions; See Protocol 3.5.
  3. expenses incurred in the parties' discussions; See Protocol 4.7 concerning expense reimbursement.
  4. forum selection, a.k.a. choice of forum; See Protocol 21.12.
  5. good-faith negotiation; See Protocol 9.7.
  6. governing law, a.k.a. choice of law; See Protocol 21.14.
  7. limitations of liability; See Protocol 21.18.
  8. no-shop; See Protocol 22.4.
  9. not soliciting each other's people; See Protocol 17.9.
  10. reliance waiver, a.k.a. outside statements don't count; See Protocol 11.7.
  11. remedy limitations; See Protocol 21.18.
  12. warranty disclaimers; and See Protocol [[#r-impl-warr-discl.
  13. any other terms that the LOI explicitly states are binding.
Note

().  Caution: When drafting an LOI, you don't want to say that nothing in the LOI is binding — there will very-likely be some LOI terms that the parties do want to be binding. Example: A California appeals court noted that a "collaborative law" agreement between a divorcing couple stated that none of the terms of the agreement were legally enforceable — which meant that the agreement's confidentiality provision was unenforceable. See Mueller v. Mueller, 102 Cal. App. 5th 593 (2024) (affirming family-court judgment).

Subdivision 5: See 28.6 (notes on agreements to negotiate in good faith).

3.11.4. Early start not binding

  1. This § 3.11.4 will apply if A starts early on its activities under the (contemplated) Arrangement.
  2. A's early start does not signify that A has agreed to enter into a partnership or other relationship with B.
  3. On the other hand: If the parties end up not entering into a Final Agreement for the Arrangement, THEN: B need not reimburse A in connection with A's early start unless the two parties clearly so agree in writing (such as: if the LOI clearly says so).
Note

This language addresses a possible (but unlikely) concern: Sometimes when parties sign an LOI, the parties' business people decide to "get going" before the lawyers finish the final, formal contract. For example: It's been said that in Hollywood, the process of making a movie will sometimes gets started — and even be finished — long before written agreements get signed, which might never happen. See, e.g., Jonathan M. Barnett, Hollywood Deals: Soft Contracts for Hard Markets, 64 Duke L.J. 605, part II (2015); Shuangjun Wang, Let’s Do Something New for Lunch: Re-evaluating Hollywood Handshake Deals (Berkeley.edu 2013).

That could lead to a holding that the parties' actions had the legal effect of creating a de facto or implied partnership — with the result that the parties had fidudicary obligations to each other under partnership law. See, e.g., Tex. Bus. Org. Code § 152.051, which defines partnership as "an association of two or more persons to carry on a business for profit as owners"; see also § 152.052 (rules for determining if partnership is created); Penney v. Penney, 355 So.3d 303 (Ala. 2021) (farm was property of implied family partnership to raise chickens).

Example: In an initial victory, a giant energy company successfully urged such a de-facto partnership claim to a Dallas jury after being jilted by its prospective partner in a pipeline project. The jury awarded the giant company more than $535 million, but that judgment was overturned on appeal because of a disclaimer in the parties' LOI. See Energy Transfer Partners, L.P. v. Enterprise Products Partners, 593 S.W.3d 732 (Tex. 2020), affirming 529 S.W.3d 531 (Tex. App.—Dallas 2017).

3.11.5. Ending the discussions

Unless the LOI clearly says otherwise, any party has the right to withdraw from the discussions of the Arrangement:

  • at any time,
  • temporarily or permanently,
  • for any reason or no reason,
  • in that party's sole and unfettered discretion,

without incurring any obligation or liability to any other party — under any theory, including any applicable implied covenant of good faith and fair dealing — for the withdrawal itself.

Note

Pro tip: This section allows any party to withdraw from discussions, but it does not say that "neither party is obligated to negotiate in good faith." The intent here is much the same, but the latter wording wouldn't look especially good to future readers — such as judges and jurors ….

3.11.6. Additional notes

3.11.6.1. Possible goals of an LOI

When two companies (A and B) enter into an LOI, they generally have one or more of the following things in mind:

1.  A and B want the LOI to serve as a convenient written discussion outline of a potential business arrangement as they're then currently contemplating it, and to set out agreed ground rules for their anticipated discussions about the potential arrangement.

2.  Sometimes LOIs arise from a personal business motivation: "Alice" and "Bob" — employees of A and B who're negotiating the deal — might feel pressure from their bosses to show that yes, yes, boss, we really are making progress, give us more time!

3.12. Material-Problems Disclosure Protocol

Some strategically-important types of contract include detailed representations and warranties along the lines of this Protocol. See, for example: • section 3.3(b) of the agreement and plan of merger between Capital One and Discover, from which this Protocol draws some of its concepts; and • the representations in Section 3 of the 2002 ISDA Master Agreement (as entered into by Bank of America and LKQ Corporation) (ditto).

3.12.1. A's confirmation

By entering into the Con­tract, A confirms that, so far as A is aware, A's entry into the Con­tract will not be a cause of "material problems" (defined below) for B except to the extent (if any) that A has already disclosed the same in writing to B.

Note

This is a fairly-weak confirmation, of the kind commonly known as a "knowledge rep" — see generally Protocol 20.34 (representation definition).

3.12.2. Investigation by A?

  1. The confirmation at § 3.12.1 does not say anything about whether A has made any particular investigation into the matter.
  2. The Con­tract does not obligate A to conduct any such investigation.
Note

().  The Con­tract could override this with a statement about what A has done or is to do — in the latter case, perhaps with a deadline, expense caps, etc.

Subdivision 2: A will want to check whether the law (e.g., securities laws) obligates A to do some sort of investigation.

3.12.3. Definition: "Material problem"

For purposes of this Protocol, the term "material problem" for B refers to anything whose effects — alone or in combination with other things — could reasonably be regarded as posing more than a non-trivial risk of significantly interfering with:

  1. B's carrying out B's obligations under the Con­tract, and/or
  2. B's exercise of B's rights under the Con­tract.
Note

().  This follows Ken Adams's suggestion of saying, "more than a non-trivial risk," discussed at 20.26. Granted, the use of "significantly interfering" is vague and open to dispute. But that seems like a worthwhile risk in this context.

For some possible examples of material problems, see 3.12.4.1 below.

3.12.4. Additional notes

3.12.4.1. Some examples of possible "material" problems

Let's use "Fred" and "Ginger" as names for hypothetical parties in listing a few examples of some the possible things that might concern Ginger:

1.  Ginger would want to know if a third party had the right to veto or otherwise control Fred's performance under the contract.

2.  Fred might not have told Ginger that the contract between Ginger and Fred would be a subcontract of a contract between Fred and a governmental entity — and that could result in Ginger unwittingly becoming, by law, bound by various "flowdown" obligations, discussed (briefly) at 3.6.3.

3.  Fred might not have told Ginger that he was currently the subject of a lawsuit by a third party that could prevent Fred from honoring his contractual obligations to Ginger.

4.  Fred might not have told Ginger that he was under an injunction (or judgment, or regulatory restriction) that could lead to trouble for Ginger.

5.  Fred might not have told Ginger that he (or perhaps some of his relevant employees) was:

  • subject to debarment or other exclusion from dealing with the U.S. Government, for example for Medicare fraud or the like;
  • barred under export-control laws, government sanctions, or the like.

5.  Fred might not have told Ginger that he had been doing business with a third party, "Harry," and that if Ginger and Fred entered into their contract, then Harry might sue Ginger for tortious interference. A tortious-interference lawsuit by a disgruntled party can have catastrophic results. Example: Oil giant Texaco (now part of Chevron) was hit with a damage award of some $10.5 billion, or more than $29 billion in 2025 dollars, for tortiously interfering with what the jury and the courts found to be a binding memorandum of understanding between Pennzoil (now part of Shell) and Getty Oil. See Texaco, Inc. v. Pennzoil Co., 729 S.W.2d 768 (Tex. App.—Houston [1st Dist.] 1986, writ. ref’d n.r.e.).

6.  Fred might not have told Ginger about facts indicating that Fred lacked the legal power to enter into their contract — meaning that if Fred were later to suffer buyer's remorse, he might later try to use his lack of legal power to void their contract.

7.  Fred might not have told Ginger that he knew he wasn't capable of carrying out his obligations under the contract. Example: In 2010, a court finding of similar conduct resulted in EDS, a giant U.S. computer-services company (later acquired by HP), settling a lawsuit with British Sky Broadcasting for some USD $460 million — more than four times the value of the contract between the parties. (See the discussion of this case at 20.34.6.7.) Regardless: As a practical matter, Ginger likely cares more about getting business done than with hypothetically being able to sue Fred someday. She might well prefer to know, early on, about Fred's incapability so she could consider looking elsewhere.

3.13. No-Conflict Confirmation Protocol

3.13.1. The Protocol

  1. When this Protocol is agreed to, each party A to the Con­tract confirms to each other party B that — so far as A is aware — A:
    1. is not a party to any "problematic" (as defined below) agreement with any third party;
    2. is not the target of any problematic claim, in litigation or otherwise; and
    3. is not subject to any problematic injunction, judgment, or regulatory restriction.
  2. In subdivision 1, a "problematic" thing is one whose effects — alone or in combination with other things — could reasonably be regarded as posing a risk of materially interfering with:
    1. any party's performance under the Con­tract, or
    2. B's exercise of B's rights under the Con­tract.
Note

().  This Option provides a "canary in the coal mine" to help the parties identify (and, ideally, address) certain problems before they sign the Con­tract.

Some strategically-important types of agreement include more-detailed representations and warranties of this general kind — see, for example, the (pretty-typical) reps and warranties in the merger agreement between United Airlines and Continental Airlines, from which some of the concepts in this Option are drawn.

The statements in this Protocolare representations, not warranties; see generally 16.2 for a discussion of the differences.

Subdivision 1.b: As an example: One possible problematic claim would be that a party's performance under the Con­tract would constitute tortious interference, on the part of any party to the Con­tract:

  • with a contract between the representing party and any third party, or
  • with the prospective economic advantage of any third party.

(See generally the Wikipedia discussion of tortious interference with contractual relationship or prospective economic advantage. A tortious-interference lawsuit can have catastrophic results, as happened in the Pennzoil v. Texaco case cited in the note to § 3.11.1.)

3.14. Notices Protocol

Where contracts are concerned, generally speaking a "notice" would be a communication to do something along the following lines: (1) to formally communicate a fact or opinion relevant to the Con­tract, for example, the fact that the contract had been assigned (see generally the commentary at Protocol 15.3); and/or (2) to formally invoke a specific right or obligation under the Con­tract, such as, for example: making a demand; exercising a right; or terminating the Con­tract.

3.14.1. Writing requirement

A notice relating to the Con­tract has no effect unless:

  1. the notice is in writing as provided in this Protocol; or
  2. non-written notices are expressly allowed by clearly-applicable law.
Note

Conceivably, a law might state that a party can give some kind of notice without having to do it in writing. (But none comes to mind at the moment.)

3.14.2. Notices by email, text

Notices relating to the Con­tract can be sent by text messages, and other forms of electronic communication unless the Con­tract (or clearly-applicable law) clearly says otherwise.

Note

().  Notice by email is quite common — but a few contracts still require hard-copy notice in one form or another (sometimes even by certified mail).

Parties should keep in mind that emails and especially text messages might disappear. (That's not a problem unique to electronic messages, of course.)

Alternative: "A notice by electronic message (email, text, instant message, etc.) will be of no effect; no party is to assert otherwise."

This Protocol doesn't make the categorical statement (found in some contracts) that notices by email or text message are ineffective, because that seems too extreme — but courts have enforced such provisions, for example in McGuire (N.Y. App. Div. 2021), where the court held that an email notice had been ineffective because the contract in question required notices to be sent by first-class mail. See McGuire v McGuire, 2021 N.Y. Slip Op. 04816, 197 A.D.3d 897, 900, 153 N.Y.S.3d 280 (N.Y. App. Div. 2021) (reversing partial summary judgment).

3.14.3. Readable language

A party is entitled to disregard a notice relating to the Con­tract unless at least one of the following is true:

  1. the notice is written in a language that the addressee's relevant people can read; or
  2. the notice includes a prominent, "get this translated!" alert in such a language.
Note

The language requirement for notices is informed by CEEG (10th Cir. 2010): An American retailer, under a contract with a Chinese manufacturer, received a notice of arbitration — in Chinese — but the retailer didn't get the notice translated until it was too late to avoid big problems, as discussed in the commentary to § 21.1.6.

3.14.4. Emojis in a notice?

Any party is entitled to disregard an emoji in a notice unless the emoji is shown to have — at the time of the notice — a clear, unambiguous meaning to relevant readers.

Note

().  Alternative: "Emojis in a notice have no effect."

The problem: Emojis in a notice could be problematic, because they might have multiple meanings. "Use your words!" is sound advice for contract notices, not least because emojis can be susceptible to disagreements about their meaning. See, for example:

  • The so-called "chocolate ice cream" emoji 💩, which, ahem, might not actually mean that; and
  • the so-called water emoji 💦 — as noted in Swanagan (W.D. Ky. 2023), "while water [emojis] may reference sexual relations, case law also confirms that water can also refer to methamphetamine in drug trafficking communications."

United States v. Swanagan, No. 4:22CR-00003-JHM (W.D. Ky. Jan. 3, 2023) (denying motion to suppress LEO's affidavit; citation omitted).

Still: People do sometimes use emojis in their writing. So: This section allows for the possibility that in some circumstances, it might make sense for emojis to be given effect in a notice under a contract.

But what if an emoji is ambiguous, as in the examples above? Let's play it safe: If an emoji in a notice could plausibly have more than one meaning, then let's treat it like a blank space — if doing that makes the notice incomplete or even incoherent, then so be it: The notice should have been clear.

(This takes a harder line than the contra proferentem rule of interpretation that ambiguities aren't ignored, they're construed against the drafter; see 11.4.)

For additional information about the legal effect of emojis, see the emoji-related blog entries of law professor Eric Goldman, such as Emoji Law Year-in-Review for 2023 (blog.ericgoldman.org).

3.14.5. Mandatory addresses for notice?

The Con­tract may specify whether one or more addresses for notice is required, in which case

Note

Pro tip: Many notices clauses specify mandatory addresses for notice; such provisions are often cumbersome and might be best avoided — although they might be appropriate in some circumstances, and moreover a court might look at the circumstances to determine whether a notice to the "wrong" address was ineffective, or was effective anyway, as discussed in the commentary at 3.14.13.5.

3.14.6. "Attention: [Position]" lines?

Hard-copy notices sent by mail, FedEx, etc., should include an "Attention:" line — which should specify a position, not just an individual.

Note

().  An "Attention: [Position]" line can help to reduce the chances of a notice going astray or falling through the cracks — for example:

  • an individual addressee might not be in the same job any more; and
  • the addressee's mailroom people might set aside the notice until they could figure out what to do with it — and they might never get around to it until too late. (Something close to this happened in CEEG (10th Cir. 2016), discussed in the commentary at § 21.1.6.)

    ABC Corporation (Attention: Jane Doe)

    ABC Corporation (Attention: Jane Doe, Vice President of Marketing)

    ABC Corporation (Attention: Vice President of Marketing)

Example: In American Casualty (3d Cir. 1994), the court held that "we join a growing line of cases prohibiting an insured from insisting that its insurer's underwriting department sift through a renewal application and decide what should be forwarded to the claims department on the insured's behalf." Am. Cas. Co. of Reading, Pa. v. Continisio, 17 F.3d 62, 69 (3d Cir. 1994)]

But: Any such requirement should be quite clear that the "Attention:" line is mandatory, not merely preferred. Example: In Landmark American Insurance (5th Cir. 2020):

  • The notice requirement in question (in an insurance policy) said merely: "Please send all claim information to: Attention: Claims Dept. [address]." The court held that this was precatory (that is, expressing a wish) and not mandatory, and so the insured's failure to send notice to the Claims Department did not automatically justify denial of coverage. Landmark Am. Ins. Co. v. Lonergan Law Firm, PLLC, No. 19-10385, slip op. (5th Cir. June 4, 2020) (reversing and remanding summary judgment in favor of insurance carrier) (unpublished).
  • The court added, though: "Even though we hold that Lonergan reported her claim under the Policy, we decline to reach the issue of whether she breached the Policy's notice conditions or whether any such breach may have prejudiced Landmark." (Emphasis added.)

Id. at part III (emphasis added).

3.14.7. Mandatory delivery methods?

The Con­tract may specify whether some particular means of delivery is required — or prohibited.

Note

().  Caution: By law, some types of contract might require — or bar — specific types of notice-delivery methods in particular situations and jurisdictions, as discussed at 3.14.13.2.

Parties should keep in mind that emails and especially text messages might disappear. (This is one of the points discussed at 3.14.13.2 — and it's not a problem unique to electronic messages, of course.)

Caution: Mandatory delivery methods might open the door to gamesmanship. Example: A colleague once told of receiving a notice, by FedEx, from another party to a contract. My colleague checked with in-house counsel at her (giant) company. The in-house counsel said, "We're going to ignore this notice, because the contract requires the notice to be mailed, and this one wasn't." Um … that's … not how things should work in a cooperative relationship — and courts generally won't go along with such game-playing except in limited circumstances; see the commentary at 3.14.13.5.

3.14.8. Required copies of notices?

  1. The Con­tract could specify whether anyone else is to get a separately-sent copy of notices, e.g., a copy to legal counsel.
  2. The Con­tract could also specify whether a separately-sent copy would, or wouldn't, be deemed notice.
Note

().  Copying the notified party's legal counsel on notices can be useful:

  • disputes can sometimes be resolved quickly if legal counsel are brought in sooner rather than later; and
  • the redundant "path" of sending a separate copy to legal counsel can help make sure that the notice gets through.

    Some drafters like to specify that a copy to legal counsel "shall not constitute notice." I'm on the fence whether that's a good idea — it might vary with the type of contract.

    Pro tip: If a party A doesn't know the name or address of party B's legal counsel, one way for A to send a copy of a notice to legal counsel would be to send a separate, paper copy of the notice to B, by certified mail or courier, specifically marked as, "Attention: Legal Counsel"; that way, the attention line should get the attention of B's mailroom personnel and help them route it accordingly.

    Pro tip: If a party wants to require a copy of a notice to be sent to a particular legal counsel, that party should consider specifying in the requirement that the copy to counsel must be sent separately, to provide an independent delivery path and thus reduce the likelihood of nondelivery.

3.14.9. Effectiveness: The Three Rs of Notice

  1. This § 3.14.9 Unless the Con­tract clearly states otherwise, any notice relating to the Con­tract is effective upon the earliest of the following (and only then):
    1. the addressee's receipt or refusal of the notice, or
    2. after reasonable but unsuccessful efforts at delivery,

in any such case, as shown by independent written confirmation (for example, a certified-mail receipt or a courier delivery report) or by the addressee's stipulation.

Note

().  Let's refer to this as the "Three Rs of Notice."

The preface, "Unless the Con­tract clearly states otherwise" accommodates the various provisions above about how the Con­tract can impose restrictions on notices.

3.14.10. Changes of address

  1. A advises B in writing of any change of address for notice under the Con­tract.
  2. Formal notice of an address change is not required.
Note

().  Subdivision 2 — alternative: "A party desiring to change its address for notice must do so by notice." This alternative, though, might be a bad idea, because it could lead to problems if a notices clause (1) required all notices to be sent by, for example, certified mail; and (2) required changes of address to be communicated in that way.

Pro tip: Contracting parties should be diligent about updating their address-for-notice records when they're told that another contracting party has changed its address.

Example: In J.M. Smucker Co. (8th Cir. 2014), the well-known food company ended up having to pay an extra year's rent on leased space because it used the wrong address to opt out of an automatic extension of the lease term.

Lesson: Figure out some kind of system for making sure your contract addresses are up to date. (And use some kind of calendar reminder system!)

Of possible interest: A notices hub. In July 2025 the International Swaps and Derivatives Association (ISDA), home of the ISDA Master Agreement, launched its ISDA 2025 Notices Hub and Protocol that:

… allows certain critical notices under the ISDA Master Agreement (and, over time, other notices and agreements) to be securely delivered and received online.

It also allows users to maintain and update their notice delivery details in a single location which their counterparties under the ISDA Master Agreement (and, over time, other agreements) can access.

3.14.11. "Written notice"

If the Con­tract uses terms such as, for example, "written notice" or "notice in writing" (emphasis added), it is a convenient reminder; it is not a signal that a non-written notice could be effective.

Note

This seeks to defuse a potential dispute under the contract-interpretation principle expresio unius est exclusio alterius ("to express one thing is to exclude others")

3.14.12. Option: Mailbox Rule

If this Option is specifically agreed to in the Con­tract, THEN: In addition to the Three Rs of Notice (see § 3.14.9), the addressee of any notice is (rebuttably) presumed to have been received the notice on the date three business days after the date that the notice is shown to have been deposited as follows:

  • in an official mail receptacle of the jurisdiction where the notice is sent,
  • in a sealed, properly-addresed envelope,
  • either (1) with first-class postage prepaid, or (2) in compliance with bulk-mail rules.
Note

().  This Protocol normally doesn't use the Mailbox Rule because the "Three Rs of Notice" approach in § 3.14.9 is a better fit for modern business practice. As a particular case, the third R — reasonable but unsuccessful attempts to deliver notice — handles the case where an addressee tries to evade notice.

What is the Mailbox Rule, exactly? In Stuart (Tex. App. 2015), the court explained the rule:

When a letter, properly addressed and postage prepaid, is mailed, there exists a presumption the notice was duly received by the addressee. This presumption may be rebutted by proof of non-receipt. In the absence of proof to the contrary, the presumption has the force of a rule of law. Stuart v. U.S. Nat'l Bank Ass'n, No. 05-14-00652-CV, slip op. at 4 (Tex. App. Dallas Oct. 28, 2015) (affirming foreclosure on home) (cleaned up, emphasis added); see also, e.g., Rosenthal v. Walker, 111 U.S. 185, 193-94 (1884).

The Mailbox Rule's presumption of receipt might even be imposed by statute. See, e.g., Mont. Code. Ann. 26-1-602, explained in Kenyon-Noble Lumber Co. v. Dependant [sic] Foundations, Inc., 2018 MT 308, 393 Mont. 518, 432 P.3d 133, 138 (2018) (affirming judgment based on failure to rebut presumption of receipt).

But: "unsupported, second-hand accounts [of mailing] cannot invoke the mailbox rule's presumption." Guerra (3d Cir. 2019). Guerra v. Consolid. Rail Corp., 936 F.3d 124, 137 (3d Cir. 2019) (affirming dismissal of plaintiff's complaint; plaintiff had provided insufficient evidence of timely mailing, to OSHA, of whistleblower complaint).

In a PayPal case, the Seventh Circuit explained:

In resolving a motion to compel arbitration, a court may apply the mailbox rule as a matter of law only where there exists no genuine dispute of material fact that the relevant communication was sent.

* * *

Under Illinois law, however, even where the presumption is triggered, if the intended recipient denies receipt, that denial rebuts the presumption. Whether the communication was in fact received must then be decided by a trier of fact. Kass v. PayPal Inc., 75 F. 4th 693, 703, 704 (7th Cir. 2023) (vacating and remanding order confirming arbitration award for trial of whether Kass had received notice of an amendment to PayPal terms of service imposing an arbitration requirement) (formatting modified).

(Formatting modified.)

But why not just always use the "Mailbox Rule"? For business-to-business contracts, when it comes to whether a particular notice has in fact been received, "that's a conversation we don't want to have" (to paraphrase one of my former students in another context). Example: The Third Circuit once observed:

In this age of computerized communications and handheld devices, it is certainly not expecting too much to require businesses that wish to avoid a material dispute about the receipt of a letter to use some form of mailing that includes verifiable receipt when mailing something as important as a legally mandated notice.

The negligible cost and inconvenience of doing so is dwarfed by the practical consequences and potential unfairness of simply relying on business practices in the sender's mailroom. Lupyan v. Corinthian Colleges, Inc., 761 F.3d 314, 322 (3d Cir. 2014) (emphasis and extra paragraphing added).

But for business-to-consumer ("B2C") contracts, the business might want to use the Mailbox Rule to provide that notices from the business are effective a certain number of days after mailing; that's likely to be the most cost-effective approach for such situations.

Pro tip: Drafters might want to adjust the time at which notice becomes effective under the Mailbox Rule, so as to match the expected postal delivery time — especially if the notice will be mailed from one country to another.

3.14.13. Additional notes

3.14.13.1. Be practical when it comes to imposing notice requirements.

It's not a good idea to impose overly-rigid notice requirements; consider what the circumstances might be when notice is appropriate — for example, less formality might well be appropriate when a party is notifying another of a safety issue.

Example: In a Texas case (which had a noteworthy final result on appeal):

  • A jury found that a contractor was given sufficient oral notice of serious safety violations, and that the customer had substantially (but not completely) complied with the contract's requirement that the customer give multiple written notices before being entitled to terminate the contract.
  • Based on the jury verdict, the trial court awarded the customer some $4 million in damages and attorney fees; an intermediate appeals court affirmed that judgment.
  • But the state supreme court reversed, holding that, because the contract specifically required three written notices, the contractor's actions were not enough. See, e.g., James Constr. Gp. v. Westlake Chem. Corp., 594 S.W.3d 722, 747-48 (Tex. App. Houston [14th Dist.] 2019) (evidence sustained jury verdict that contractor received sufficient notice of serious safety violations), rev'd, 650 S.W.3d 392, 396-97, 405-08 (Tex. 2022).
3.14.13.2. Would the law require a specific form or means of notice?

().  Caution: By law, some types of contract might require specific types of notice in particular situations and jurisdictions. Example: An Alaska statute requires notices from an insurer to be sent either by first-class mail with a certificate from the USPS, or by electronic mail with electronic confirmation of receipt by the intended recipient. See Alaska Stat. 21.36.260, cited in Travelers Property Casualty (Alaska 2025).

Caution: While an exchange of text messages can form a binding contract (see 28.3), parties should be judicious in sending notices by text messages, because text messages arguably have more potential to disappear than emails and FAXes. Tangentially, that's why California's Statute of Frauds requires written confirmation when texts and IMs are used to convey title to real property. See Cal. Civ. Code § 1624(d), discussed at 32.35.

3.14.13.3. Pro tip: Hard copy notice? Write the tracking number

For hard-copy notices, include the tracking number (certified mail, FedEx, etc.) on the notice itself. This can help forestall a claim by the addressee that the tracking number proved only that some document had been delivered and not necessarily the notice document.

The tracking number for the sample USPS "green card" below is near the bottom left of the card, just below the bar code.

Example: Just above the inside address of a letter, type: "Certified Mail No. [fill in], Return Receipt Requested" or "Via FedEx Waybill No. [fill in]."

See the following example (using a mocked-up letterhead) — note how the certified mail number is typed above the inside address:

Keep a photocopy of the notice (or other communication) with the tracking number on it; that can help forestall a later claim by the addressee that the tracking number proved only that some document had been delivered and not necessarily the notice document.

DCT comment: As a brand-new lawyer, I saw the following occur in a state-court hearing on a motion for summary judgment:

  • The lawyer for the party opposing summary judgment claimed not to have received the 21-day advance notice of the motion hearing (required under state rules).
  • The lawyer for the party seeking summary judgment — me, filling in at the hearing for a colleague at my firm — showed the judge a "green card" certified-mail receipt from the U.S. Postal Service.
  • The opposing lawyer admitted to the judge that yes, the signature on the green card was that of his assistant — but the opposing lawyer insisted that the receipt must have been for some other communication because, he continued to insist, he had never received the 21-day notice of the hearing.
  • There was no documentation connecting that particular green-card receipt to the notice of the hearing.
  • The judge gave the benefit of the doubt to the opposing lawyer who claimed he never received the notice of the hearing.

(Several years later, the opposing lawyer was disbarred, for unrelated reasons.)

3.14.13.4. Deadlines for notice?

Some contract provisions require notice to be given no later than a specified time; a court might enforce such a requirement.

Example: A longtime Pizza Inn franchisee had an option to renew the franchise term. The contract set a deadline for the franchisee to give notice that he wanted to exercise the option. The franchisee was two months late in giving his renewal notice, and Pizza Inn decided not to renew. The court ruled in favor of Pizza Inn, holding that:

  • Under Texas law, the holder of an option must strictly comply with the terms of the option, which in this case included the deadline for the franchisee to give his renewal notice; and
  • In the particular circumstances, the franchisee's tardy renewal notice did not qualify for what the court described as a very-narrow "equitable intervention" exception to the law's general rule requiring strict compliance with option terms. See Pizza Inn, Inc. v. Clairday, 979 F.3d 1064 (5th Cir. 2020) (reversing district court and rendering judgment for Pizza Inn).
3.14.13.5. Would notice received always be effective?

If a notice is shown to have been actually received, a court is likely to consider the notice to have been effective, even if the contractual notice requirements were not strictly followed; see, e.g., Elmen Holdings (5th Cir. 2023). See, e.g., Elmen Holdings, L.L.C. v. Martin Marietta Mat'ls, Inc., 86 F.4th 667, 679-80 (5th Cir. 2023) (affirming summary judgment in favor of plaintiff; citing Texas law) (email notice substantially complied with lease's requirement that notices must be either in person or by certified mail); Rose, LLC v. Treasure Island, LLC, 445 P.3d 860, 863-64 (Nev. App. 2019) (with extensive case citations).

But that won't always be the case. Example: In McGuire (N.Y. App. Div. 2021), the court held that an email notice had been ineffective because the contract in question required notices to be sent by first-class mail; see also James Constr. Gp. (Tex. 2022), discussed at 3.14.13.1 above. See McGuire v McGuire, 2021 N.Y. Slip Op. 04816, 197 A.D.3d 897, 900, 153 N.Y.S.3d 280 (N.Y. App. Div. 2021) (reversing partial summary judgment).

3.14.13.6. Consider what details should be required in a given notice.

Suppose that two parties, "Alice" and "Bob," are entering into a contract, and that under the contract, Bob is supposed to notify Alice if a certain event occurs. If Alice thinks it's important for the notice to include particular types of detail, it might be well to have that spelled out in the notification requirement, instead of relying on a simple "in reasonable detail" phrasing.

Example: In a UK case, a buyer of shares in a company gave notice to the seller that the buyer was invoking an indemnification provision under the purchase agreement. The court of appeals reversed a trial-court holding that the buyer's notice had not provided "reasonable detail" as required by the agreement. The court noted that "courts should not interpret such clauses as imposing requirements which serve no real commercial purpose unless compelled to do so by the language of the clause." Drax Smart Generation Holdco Ltd v Scottish Power Retail Holdings Ltd, [2024] EWCA Civ 477.

3.15. Signature Document Integrity Protocol

Once parties have agreed on the final versions of contract documents, they typically want everything signed up yesterday. It would slow things up (and cost more money) for the parties and their lawyers to feel they had to re-read the entire, final, "agreed" versions before signature, just to confirm that the other party hadn't surreptitiously altered the documents. Unfortunately, though, some jerk lawyers seem to like to play games by not redlining all their changes; see the discussion at 3.15.3.2.

3.15.1. Applicability to final signature documents

When this Protocol is agreed to, it applies whenever A signs a document (for example, a draft of the Con­tract) and sends it to B, where the circumstances clearly indicate that A and B had agreed on a final version of the document.

3.15.2. Confirmation: No final surreptitious changes

By sending B the signed document, A confirms to B that:

  1. that what is being sent is in fact the agreed final version, and
  2. that A did not make any changes to that version,

unless, in writing, A explicitly calls B's attention to the fact that changes were made.

Note

Concerning the choice of "confirms," see 3.15.3.4.

3.15.3. Additional notes

3.15.3.1. The business context

Modern business continues to be based at least in part on trust: Many parties would be put off if they felt they had to re-read every word and punctuation mark in the final draft of a contract.

But even so: A second-signing party might want some specific assurance that the first-signing party hadn't surreptitiously altered the agreed version(s); this Protocol helps to guard against such fraud.

(For "significant" contracts, of course it might still make sense to re-read the to-be-signed copy anyway, one last time, or at least to spot-check it.)

Granted, once a final version of a signature document has been agreed to, the overwhelming majority of lawyers and clients would never be so underhanded as to try to sneak in surreptitious changes. Doing so could damage a lawyer's reputation and possibly even lead to disciplinary action — and the client's business relationship with the other party might well be poisoned by surreptitious changes to an agreed final version of a document.

It's sad, though, that some signing parties have indeed surreptitiously changed signature documents; a few cases in point are discussed at 3.15.3.2 below.

3.15.3.2. Signature-document fraud does happen …

On occasion, a signer — or, more likely, an unscrupulous lawyer — will try to be sneaky:

Example: In Iowa, a husband and wife agreed to a mediated settlement of a divorce case. The wife's lawyer drafted an agreement and sent it to the husband's lawyer — who surreptitously added a provision giving his client certain additional child-custody rights — and it was the (surreptitiously) modified agreement that was signed. When this came to light, the husband's lawyer's license to practice law was suspended indefinitely (for that plus other offenses), with no possibility of reinstatement for at least two years. See Att'y Discipl. Bd. v. Leitner, 998 N.W.2d 627, 636, ¶ 28-45 (Iowa 2023), amended Feb. 19, 2024.

Example: A California appeals court scathingly reinstated a lawsuit in which the defendants were accused of surreptitiously substituting documents just before signature; the appeals court remarked that "these allegations state, quite literally, a textbook cause of action for fraud in the execution …." Munoz v. PL Hotel Group, LLC, 73 Cal. App. 5th 543, 547 (2022) (reversing dismissal), citing Rest.2d Contracts (1981) § 163, illus. 2, p. 444; subsequent proceeding sub nom. Munoz v. Patel, 81 Cal. App. 5th 761 (2022).

Example: A party surreptitiously altered a release before signature; the Sixth Circuit affirmed the trial court's judgment "reforming" the release, that is, revising the release after the fact. See Hand v. Dayton-Hudson, 775 F.2d 757 (6th Cir. 1985).

Example: I once served as an expert witness for a company in the summary-judgment phase of a noncompetition lawsuit. Omitting some details:

  • A longtime executive at the company surreptitiously altered the HR department's draft of a modified employment agreement that he was being asked to sign.
  • In the electronic document, the executive changed a two-year post-employment noncompetition covenant to a two-month covenant. He didn't flag that change — even though he did flag other changes in a different part of the 25-page document. (The executive's previous employment agreement had included a two-year noncompete.) The executive did this a second time with a revised draft with agreed changes (!).
  • In due course, the executive resigned from the company. He took his wife on a two-month European vacation. Upon his return, he started working for a competitor of his former company.
  • The company sued the executive for, among other things, breach of the noncompete clause in his employment agreement.
  • The executive moved for summary judgment dismissing the company's claim, on grounds that his putative two-month noncompete had expired, and that the company should have re-read the agreement version that the executive signed before the company countersigned it.

The court denied the executive's summary-judgment motion. The case settled soon afterwards.

(Some "inside baseball" for litigators: For the company's summary judgment response, I provided a written expert witness affidavit about how things commonly work in the business world when parties negotiate contract wording. My affidavit focused on common business practice in contract negotiation, not the law. That's because courts generally don't allow lawyers to testify as expert witnesses at trial about the law, as instructing the jury about the law is the exclusive province of the judge.)

Example: One supplier apparently tried to sneak a material, unmarked change into a supposedly-final version of a contract — and ended up essentially killing its customer relationship. See Nada Alnajafi, Hidden Redlines: How to Avoid Them and How to Respond to Them (ContractNerds.com 2023).

Example: On a lighter note: An Australian landlord could have used a redlining representation in its lease form: As a prank, a prospective tenant, reviewing the lease in electronic form, added a requirement that the landlord must provide birthday cake on the weekend nearest the tenant's birthday. The landlord didn't notice the insertion. See Ricky Raad, Tenant's additional clause takes the cake (Mondaq.com 2016).

In a LinkedIn discussion kicked off by Laura Frederick, numerous lawyers told tales of why they always run a compare-documents operation against redlines from other lawyers, because they'd been burned by [jerk] lawyers who redlined just some of their revisions.

3.15.3.3. … and a court might not save the day

A court might not come to the rescue of a contracting party that was deceived by a surreptitious change in wording.

Example: A Russian court reportedly enforced a "contract" created by a man who changed a bank's credit-card agreement, then successfully sued the bank when it didn't comply with the altered terms. See Nick Shchetko, Russian Man Turns Tables on Bank, Changes Small Print in Credit Card Agreement, Then Sues, Minyanville.com (2013).

Example: Delaware's chancery court refused to declare that a $3.5 million payment obligation was unenforceable on grounds that, allegedly, the obligation had been "quietly" inserted into settlement agreement. See Cambridge North Point LLC v. Boston & Maine Corp., No. C.A. No. 3451-VCS, slip op. (Del. Ch. June 17, 2010).

3.15.3.4. This Protocol provides a document-integrity representation (not a warranty).

This Protocol is worded as a confirmation, as opposed to a warranty, about signature-document integrity. That's intentional; here's why:

().  At the end of a fiscal quarter, a lot of contracts are likely to be in progress at once. (That's especially true in supplier-customer dealings.) Negotiators' time is a scarce resource; it has to be used economically.

Each party wants a reasonable amount of legal protection, of course. But as the shot clock runs down on the quarter, each party also wants to try to timely get ink on the signature lines.

Moreover, suppose that you're representing a supplier: The customer’s contract negotiator might not be a lawyer — and the last thing your sales people want is for the customer's negotiator to get nervous about the supplier's language take the path of least resistance, and simply put off signing the deal. A "confirmation" will likely comes across as softer than a warranty, and so might be less likely to trigger a visceral objection from the customer's people.

To be sure, as the equivalent of a representation, a confirmation would have different legal consequences than a warranty. But in many supplier-customer situations — particularly longer-term, high-dollar relationships such as major supply contracts and some software license agreements — the differences likely will be academic:

  • High-dollar suppliers are keenly interested in preserving their customer relationships if at all possible — they generally don’t want to file a lawsuit against a customer except as a last resort.
  • Customers like to have relationships with reliable suppliers.

    So, if either party were unintentionally to make a material change in the contract without marking it, the odds are high that the parties would try to work things out amicably.

In that situation, the mere existence of this representation clause would bestow a fair degree of moral- and bargaining leverage on the other party.

(It’s something that the other party's lawyer could go to his- or her counterpart with and ask, "can’t we do something about this?")

Whether the change in the contract was truly unintentional might well come down to witnesses' credibility. That would not be a comfortable situation for the party that had made the undisclosed change:

  • If a jury were to conclude that the party had intentionally sneaked in a material unmarked change in the contract, that likely would be fraud — giving rise among other things to the possibility of punitive damages.
  • That likely would give the innocent party even more bargaining power in negotiations to fix the contract wording.
3.15.3.5. Red flag if a party doesn't want to agree to this Protocol?

Caution: If a party objects to including this Protocol in a contract, it might well be something of a "red flag," possibly indicating that the objecting party might not be a good business partner.

The objecting party might be saying, in effect: We don't mind having to re-read the entire document you signed before we sign it to make sure you're not trying to cheat us — and we think you should have to do the same, to be sure we're not trying to cheat you.

And at best, the other side doesn't mind wasting everyone's time and money on re-reading something that shouldn't have to be re-read. At worst, the other side really does think it's OK to slip in surreptitious changes.

This has happened to me only twice that I can recall: A pretty-junior associate in a law firm, representing a counterparty in a contract negotiation, objected to a similar clause. I contacted the associate's supervising partner, who'd also been working on the deal with us — and who quickly overruled the associate, saying, "Oh no, of course we'll agree to this."

(The other time this happened, a different BigLaw firm was representing The Other Side: A partner in the firm simply rejected the signature-integrity clause, without explanation. My client wanted to make the deal happen, so I double-checked the final signed version — because I didn't trust the other side — and explained the situation to my client.)

3.16. Signature Mechanics Protocol

3.16.1. Definition: "Document"

In this Protocol, the term "document" refers to information —

  1. inscribed on paper (or some other tangible medium), or
  2. stored in an electronic or other medium and retrievable in perceivable form.
Note

This is a paraphrase of the definition of "record" in § 1-201(b)(31) of the Uniform Commercial Code.

3.16.2. Counterparts

If the parties sign the Con­tract and/or any related document — each, a "document" — in separate copies (known as "counterparts"), THEN: Each signed counterpart is considered an original of a single integrated document.

Note

Counterpart clauses are pretty-commonly used in contracts. (See the examples at LawInsider.) This language supports each party's getting its own, fully-signed "original" of a contract.

3.16.3. Signature forms

A document under the Con­tract could be signed, for example:

  1. by pen and ink on paper;
  2. with a computer mouse;
  3. with a stylus or finger on a tablet computer or other touchpad; and/or
  4. by typing characters on a keyboard.

3.16.4. Valid names

Any party may use any (non-deceptive) name when signing a document, including:

  1. a trade or assumed name, or
  2. a word, mark, or symbol,

as long as the party does so with the present intention to authenticate the document.

Note

This is adapted from § 3-401 of the Uniform Commercial Code.

3.16.5. Signature date confirmation

  1. This § 3.16.5 will apply whenever a party signs a document, where —
    1. the party's signature block includes date signed (no matter how that came to pass); and
    2. that date is present in the signature block at substantially the same time that the party signs the document.
  2. In that situation: By signing the document, the party is confirming that it is signing on the stated date, not before or after that date.
Note

().  A signature block could include the date signed:

  • as a result of the date being pre-typed, or
  • if the signer were to hand-write or personally type the date, or
  • if a machine were to fill in the signature date.

    Signers: Never backdate a contract for deceptive purposes, e.g., to be able to report a sale in an already expired financial period. That practice led to multiple senior executives of software giant Computer Associates being sent to prison — including its CEO and its general counsel.3

    Even if backdating a contract didn't land one in jail, it could can cause other problems. For example, a California court of appeals held that backdating automobile sales contracts violated the state's Automobile Sales Finance Act, although the state's supreme court later reversed. See Raceway Ford Cases, 2 Cal. 5th 161, 211 Cal. Rptr. 3d 244, 385 P.3d 397 (2016).

3.16.6. Electronic signatures

A signature by electronic means has the same effect as wet ink on paper.

Note

().  U.S. law explicitly law supports the use of electronic signatures, and U.S. courts now routinely honor electronic "signatures" (which are now common in England and Wales as well).4

Pro tip: Be able to prove up electronic signatures. Example: A California appeals court affirmed denial of an employer's petition to compel arbitration of a wage-and-hour claim by one of its employees. The arbitration agreement had an electronic signature, but according to the court, the employer had not sufficiently proved that the purported electronic signature on the arbitration agreement was in fact that of the employee. The court, in effect, provided contract professionals with a road map for taking steps up front that would later suffice to prove up an electronic signature in litigation.) Ruiz v. Moss Bros. Auto Group, Inc., 181 Cal. Rptr.3d 781, 232 Cal. App. 4th 836, 844-45 (Cal. App. 2014).

Example: Similarly, in a New Jersey case, the state supreme court ruled that a cell-phone service provider hadn't sufficiently proved that in fact it had sent an email to a customer containing terms of service with an arbitration clause. See Fazio v. Altice USA, 261 N.J. 90, 337 A.3d 304, 305-06 (2025) (reversing trial court's order compelling arbitration and remanding case for trial).

Caution: Under § 5(b) of the (U.S.) Uniform Electronic Transactions Act, parties must agree to electronic signatures — but that agreement "is determined from the context and surrounding circumstances, including the parties’ conduct." This § 3.16.6 is intended to "check the box" that the parties have indeed agreed to conduct transactions electronically.

Caution: State law might limit electronic signatures. Example: California law rules out "burying" an authorization to do electronic transactions in a standard form contract that isn't electronic (unless the standard form contract is "separate and optional"), and also rules out waivers of that provision. See Cal. Civ. Code § 1633.5(b) (emphasis and extra paragraphing added).

3.16.7. Signature-page delivery

  1. A may send B just a signed signature page of the Con­tract or related document, with the same effect as sending the entire signed document, if B does not object within a reasonable time.
  2. If the signed document went through multiple drafts, then the signature page should indicate the draft to which it belongs.
Note

().  Nowadays it's quite common for contracting parties, without leaving their offices, to sign separate copies of the contract; then, each party emails the other party a PDF of its signed signature page only.

Caution: As discussed at 29.9.1, if different parties sign different versions of the contract, a court might well hold that there was no "meeting of the minds" and therefore no enforceable contract.

3.16.8. Escrowed signatures

A party that has signed the Con­tract or related document may deliver the signed document (and/or the signed signature page(s)) to another party "in escrow," as long as the circumstances indicate that all relevant parties agreed to this.

Note

().  Many contracts are signed electronically by geographically-separated parties. For that reason, signature pages are sometimes delivered "into escrow," to be held by attorneys until specified events occur, such as payment. See 37celsius Capital Partners, L.P. v. Intel Corp., No. 24-2794, slip op. at 5 (7th Cir. Dec. 23, 2025) (affirming summary judgment in favor of Intel) (signature pages for agreement to sell Intel subsiciary held in escrow until buyer 37celsius came up with purchase price — which never did happen).

Signature-page escrow typically involves an attorney for A sending A's signed signature page to an attorney for B, who then holds the signed page it "in escrow" pending some specified event, such as A's receipt of payment or of B's own signed signature page. For more information, see, e.g., Anshu Pasricha and Thomas B. Romer, The MAC Digital Documentation Protocol: Best Practices to Effect eSignings and Closings for M&A (BusinessLawToday.org 2022) (a project of the ABA Business Law Section Mergers & Acquisitions Committee, Technology in M&A Subcommittee) (scan down to "Principle 3").

Fairly-elaborate signature escrow provisions such as this one can be found at the LawInsider.com site — although these are likely to be overkill in many situations.

Example: Here's an actual (anonymized) "signatures into escrow" email from a corporate acquisition deal in which I represented the seller:

D.C.,

Attached are [Buyer's] signature pages to be held in escrow pending their express release by our client at Closing.

[Buyer's counsel's name]

In this particular case, Buyer's counsel later released Buyer's signature pages from escrow with an oral statement, saying so on a Zoom call. (To be on the safe side, I confirmed the release in an email to Buyer's counsel.) Buyer then sent the wire transfer for the purchase price.

3.17. Signer Personal Confirmation Protocol

3.17.1. The Protocol

Each individual who signs the Con­tract is deemed to confirm that he or she has been duly authorized to do so.

Note

().  Suppose that "Alice" is designated to sign a contract on behalf of a party, and that the contract includes a personal representation by Alice that she has authority to sign on behalf of that party — but now suppose that Alice balks because she doesn't want to put herself on the hook in case she in fact doesn't have authority. That might be a sign that the other party should investigate whether Alice really does have authority to sign.

Caution: Even if a signer were to make a written representation that s/he had signature authority, that might not be enough — because legally the other side might be "on notice" that the signer does not have authority, as discussed in the next section.

3.18. Waivers in Writing Protocol

3.18.1. Writing requirement (with some flexibility)

A waiver of rights or obligations under the Con­tract has no effect unless:

  1. the waiver is clearly set out in a writing signed by the waiving party; or
  2. under the circumstances, the waiver could not reasonably be disputed.
Note

().  A "waiver" is a party's foregoing of a right, or the party's release of another party's obligation, for example under a contract. See generally Black's Law Dictionary (11th ed. 2019); see also the commentary at 3.1.4.1 for an explanation of the difference between a waiver and an amendment.

Alternative: "To be effective, a waiver of any right or obligation under the Con­tract must be in writing and signed by the waiving party."

Caution: A court might well disregard a written-waivers-only clause like this. See, e.g., ORP Surgical, LLC v. Howmedica Osteonics Corp., 92 F.4th 896, 913-14 (10th Cir. 2024) (affirming district-court finding of fact of nonwritten waiver despite contract's clause requiring written waivers).

3.18.2. Narrow construction of purported waivers

Waivers are effective: (1) only narrowly, and (2) on a one-time basis only, in either case unless a signed written waiver clearly states otherwise.

Note

().  When a waiver is drafted too broadly, it can do serious damage to a party's position. Example: This happened in a Delaware case, where an option grant to a company's consultant and board member allegedly stated that the grantee waived his right to two previous grants. The chancery court dismissed the consultant's lawsuit for failure to state a claim; reversing and remanding, the state supreme court ruled that ambiguity in the waiver language precluded dismissal at that stage:

Because we find that both parties have proffered reasonable interpretations of the Waiver, the agreement is ambiguous. The trial court cannot choose between two reasonable interpretations of an ambiguous contract in resolving a motion to dismiss. Dismissal is proper only if the moving party's interpretation is the only reasonable construction as a matter of law. See Terrell v. Kiromic Biopharma, Inc., No. 131, 2024 (Del. Jan. 21, 2025) (reversing and remanding dismissal of complaint) (footnote omitted).

Alternative (use with caution): "The extent of a waiver is to be determined by the circumstances and applicable law."

3.18.3. No revocation of waivers

A waiver of a right or obligation cannot be revoked unless the Con­tract (or the waiver itself) clearly says otherwise.

3.18.4. Agreed "no waiver" events?

The Con­tract may list one or more particular situations or events that would not constitute a waiver or estoppel.

Note

Example: Some leases expressly state that the landlord's acceptance of late rent won't waive the landlord's rights, nor estop the landlord from enforcing any provision of the lease. Example: The Texas supreme court declined to say that a nonwaiver provision could never be waived — but the court did hold that "waiver of a nonwaiver provision [cannot] be anchored in the same conduct the parties specifically agreed would not give rise to a waiver of contract right." Shields L.P. v. Bradberry, 526 S.W.3d 471, 474-75 (Tex. 2017) (emphasis added, footnote omitted); see also the court's extended discussion at 481-85

3.18.5. Attorney-fee liability

The Writing-Requirement Challenges Protocol (10.5) is incorporated by reference.

3.18.6. Additional notes

3.18.6.1. Pro tip: Be conspicuous with the word "WAIVES"

Suppose that (1) you're drafting a contract or other document, and (2) in some particular provision, you want to say that the other party (or even your own client) "waives" something. In that situation, it's a good idea to use bold-faced, all-capital letters for the word "WAIVES" (or waived, or waive, or waiver) — doing so can be "cheap insurance" to help persuade a judge, jury, or arbitrator, plus sometimes the applicable law might require waivers to be "conspicuous."

3.18.6.2. Pro tip: Confirm a non-written waiver with a quick email

().  In any situation where you might later want to claim a nonwritten waiver by another party, seriously consider sending an email, to an appropriate person at the other party, prominently stating that the other party is indeed waiving the right or obligation. That way, if you later show that the person in fact received your email, and the other party didn't object within a reasonable time, then your email could:

  • help discourage the other party from later denying the waiver, and
  • if necessary, help you prove the waiver to a court or arbitration tribunal.

    In any such email, it's never a bad idea to try to put the ball in the other party's court to speak up, such as: Hey, [OTHER PARTY], in our call today, thanks for agreeing that I don't need to do [whatever] — if I misunderstood you, please let me know immediately.

    Caution: When sending a waiver-confirmation email like this, Don't ask the other party to "agree" that the other party waived something — that's because if the other party never responds to your email, then it'd be harder for you to prove the other party's oral waiver. #MuscleMemory

3.19. Certain defined terms

3.19.1. Confirm

The terms "confirm" has the same meaning as represent; the noun form "confirmation" has the corresponding meaning.

Note

().  Some of the Lighthouse Protocols (e.g., Material-Problems Disclosure Protocol (3.12)) use the term "confirm" instead of "represent" because the latter is closer to the way normal people speak, as opposed to legalese.

See Protocol 20.34 for the meaning of represent.

3.19.2. Should

  1. When the Con­tract, and/or a writing relating to the Con­tract, states that a party A "should" take an action, it means that:
    1. A is encouraged to take the action, but the Con­tract does not obligate A to do so; and
    2. if A does not take the action, then A is encouraged to timely let B know (i) that A is not taking the action, and (ii) if appropriate, A's reasons, but the Con­tract does not obligate A to do either of those things.
  2. The term "should not" has the corresponding meaning for not taking an action.
Note

DCT note: In my experience, contracts seldom if ever use the term should for actions that are encouraged but not mandatory. This misses an opportunity for the parties to provide guidance to their operational-level people for dealing with particular situations. See also the definitions of SHOULD and SHOULD NOT in RFC 2119 of the Internet Engineering Task Force (1997).

("RFC" stands for "Request for Comments." RFCs are, in essence, the governing documents of the Internet.)

4. Payments

4.1. Acceleration of Payments Protocol

4.1.1. Applicability

  1. This Protocol presupposes that at some point in the future:
    1. one of the parties clearly identified in the Con­tract (referred to as a "Payer") is expected to owe money under the Con­tract to another clearly-identified party (a "Biller"); and
    2. the Payer's payments are expected to be due on dates that can be determined (for example, in accordance with payment terms, or on a specified schedule).
  2. When parties adopt this Protocol in the Con­tract, the Biller has the right to "accelerate" — that is, move up the due date(s) — of one or more of the Payer's payment obligations by following this Protocol (but not otherwise).
Note

().  Caution: In some jurisdictions, a contractual right to accelerated payments might be treated — and subject to critical scrutiny — as a form of liquidated damages. See CCP Golden/7470 LLC v. Breslin, No. 24-2731, part II.B.3, slip op. at 17, 20 (7th Cir. Dec. 3, 2025); see also Protocol 21.19 (liquidated damages).

For a much-longer acceleration clause, scroll down to § 11 of this General Loan Agreement, on file at SEC.gov.

Subdivision 2: The "(but not otherwise)" parenthetical is meant to block any Biller claim that the Biller can accelerate without complying with this Protocol.

4.1.2. Acceleration prerequisites

A purported acceleration has no effect unless all of the following prerequisites have been met:

  1. The Payer materially breached the Con­tract in one or more ways. (Here, the term "the breach" refers to any one or more of the breaches if more than one breach has occurred.)
  2. The breached provision of the Con­tract was for the Biller's benefit, as opposed to benefiting only the Payer and/or one or more third parties.
  3. The Biller gave the Payer notice of the breach.
  4. The Payer did not completely cure the breach when the relevant cure period ended. (There might not have been a cure period.)
Note

See also the following: Material breach: Protocol 18.6. Third-party beneficiaries: Protocol 11.8. Notices: Protocol 3.14. Cure periods: Protocol 18.6.1.3.

4.1.3. Acceleration procedure

  1. To accelerate, the Biller gives the Payer notice that clearly and prominently states both of the following:
    1. which of the Payer's payment obligations is being accelerated — with "all of them" being one possibility; and
    2. the date that the acceleration will take effect.
  2. The notice of acceleration has no effect if it does not also comply with:
    1. any other notice requirements of the Con­tract (if there are any); and
    2. any applicable requirement of law for acceleration.
Note

().  Subdivision 2.b: Notice of acceleration will probably be required by law. Example: New York state's highest court explained: "[for s]uch a significant alteration of the borrower's obligations … noteholders must unequivocally and overtly exercise an election to accelerate." Freedom Mtge. Corp. v. Engel, 37 N.Y.3d 1, 23, 146 N.Y.S.3d 542, 169 N.E.3d 912 (2021) (emphasis added).

When you're the Biller, don't make it a big mystery whether acceleration is or isn't happening.

  1. Not least, you want the parties — and the courts — to know whether your notice did or didn't start the clock running on the statute of limitations for foreclosure on collateral. Example: This was an issue in the Freedom Mortgage case cited above: The lender "won" — but it lost anyway, because it had to litigate the matter, which took time and cost money.
  2. While we're on the subject of statute-of-limitation periods (see 21.17) after acceleration: A Texas law resets the statute-of-limitations deadline clock after acceleration if "the accelerated maturity date is rescinded or waived in accordance with this section before the limitations period expires …." See Moore v. Wells Fargo Bank, N.A., 685 S.W.3d 843 (Tex. 2024), citing Tex. Civ. Prac. & Rem. Code § 16.038; see also U.S. Bank Trust N.A. v. Walden, 124 F.4th 314, 324-25 & n.5 (5th Cir. 2024) (citing § 16.038 in partially reversing and remanding summary judgment, granted in favor of bank that had purchased home loan and initiated foreclosure proceedings, because bank's notice to homeowners had unequivocally rescinded and abandoned acceleration).

4.1.4. Notice location

The Biller's notice of acceleration may be included in some other communication to the Payer (such as a notice of breach), as long as:

  1. The acceleration notice is very-near the beginning of the communication; and
  2. The acceleration notice complies with the Express Negligence Rule (see Protocol 14.3.4) of being both express and conspicuous.
Note

Possible override language: "A notice of acceleration will be of no effect unless it is a separate notice. The separate notice must have a prominent title, clearly indicating that one or more Payer payment obligations are being accelerated. The separate notice must comply with the notice requirement of the Con­tract."

4.1.5. Acceleration deadline

  1. This § 4.1.5 applies whenever the Biller's right to accelerate is triggered by a particular event — an "Event," which could include without limitation the occurrence of a particular date.
  2. The Biller's acceleration right expires automatically if the Biller's notice of acceleration has not become effective on or before the end of the day on the date 3 months after the date that the Biller first became entitled to accelerate for that Event.
  3. If the acceleration right expires for one Event, it does not affect any right that the Biller might have to accelerate for a different Event (which would have its own expiration date).
Note

().  This deadline is imposed because: (1) it usually wouldn't be fair for a Payer to have to live forever under a Sword of Damocles because the Payer failed to make a payment; and (2) if the Biller doesn't accelerate before the stated deadline, then as a practical matter, it's likely that the Payer's payment failure didn't harm the Biller that much.

Possible override: "The Biller may send a notice of acceleration at any time after the payment failure in question, with no deadline for the Biller to do so."

4.1.6. No other effects

The parties' respective other rights, remedies, and obligations under the Con­tract are not affected by an acceleration, nor by expiration of an acceleration right.

Note

Such other rights and obligations could include, for example:

  1. any remaining right that the Payer might have to cure the payment failure in question;
  2. the Biller's other available remedies for a payment failure — such as, for example (see Protocol 20.21), suing the Payer for the unpaid amount(s) and/or foreclosing on security interests in collateral (if any);
  3. any defenses (if any) that could otherwise be asserted to try to block enforcement of the payment obligation; that will be true whether the defense could be raised by the Payer or by some other party (e.g., a guarantor).

4.2. Advance Payment Demand Protocol

4.2.1. Applicability & prerequisites

When this Protocol is agreed to, then one party to the Con­tract (the "Biller" — which must be clearly identified in the Con­tract),

  • has the right — for good reason — to require payment in advance,
  • for goods, services, or anything else,
  • from another party (the "Payer" — which must likewise be clearly identified),
  • even if the Con­tract says that the Payer may pay at a particular time or on a particular schedule.
Note

().  If you're representing a vendor (the Biller), you might not want your draft of the Con­tract to adopt this Protocol.

Here's the "yes you would" scenario: One of your vendor client's customers (the Payer) proves to be a slow payer — see 4.4.11.1 for some famous examples — and at some point the vendor says, Enough already! This Protocol provides your vendor client with a framework for demanding payment in advance for future orders from that customer.

But here's the "maybe not" part: You should also think about whether to not propose adopting this Protocol in the Con­tract. That's because:

  • The law might already permit your vendor client to revert to cash-on-delivery ("C.O.D.") or advance-payment terms if the customer's late payments constituted a "material" breach of the contract (see the definition of material breach at Protocol 18.6.1.5 and its commentary).
  • Just raising the issue with the customer could have an unwanted, "poke the bear" side effect (see 8.14): It could remind the customer's contract negotiator to insist on revising the draft contract to override what the law says, in a way that might disadvantage your vendor client.

4.2.2. Possible instances of good reason

In appropriate circumstances, good reason for the Biller's demanding advance payment might include — without limitation — one or more of the following:

  1. The Payer was late more than once in making payments required in connection with the Con­tract.
  2. The Payer was significantly late — as reasonably determined by the Biller — with one or more such required payments.
  3. The Payer wants to place an unusually-large order.
Note

().  Whether you're representing a Biller or a Payer, it might not be a profitable use of your time to try to authoritatively define the term good reason in the Con­tract — other than perhaps including some safe-harbor examples stating that Particular Thing‑X is or isn't deemed good reason. For example:

  • The parties might never get into a dispute about advance payment, so deferring discussion of the term could help the parties to get the Con­tract signed more quickly.
  • Protocol 4.2 already provides for escalation of disputes; this follows the general guideline: If you don't want to (or just can't) specify the agreed outcome now, then consider specifying an agreed process to figure it out later.

    Moreover, as a practical matter, even without defining good reason, the Biller might hold some high cards: Depending on the parties' bargaining power, the Biller might simply refuse to do whatever the Payer was asking for unless the Payer complied with the Biller's new advance-payment requirement.

4.2.3. Advance warning

The Payer may treat the existing payment terms of the Con­tract as still being in effect unless — a reasonable time in advance — the Biller alerts the Payer (preferably but not necessarily in writing) that advance payment will be required.

Note

A reasonable time in advance might be as short as when an order is placed. Example: The Biller gets a purchase order from the Payer, but the Biller responds, "Hey, we're sorry, Payer, but in view of your payment history, we're going to have to ask for advance payment." That would depend on the circumstances.

4.2.4. Escalation

If either party asks: The parties escalate any dispute about what would constitute good reason and/or reasonable times for an advance-payment alert under this Protocol:

  1. first, to the parties' respective supervisors, as stated in Protocol 3.4 (internal escalation) and
  2. if that does not result in resolution, then (at either party's further request) to a neutral advisor, as stated in Protocol 21.11.

4.3. Audit Protocol

Trust, but verify – Russian proverb, often quoted by President Ronald Reagan (to the seeming irritation of his Soviet counterpart Mikhail Gorbachev).

Any time a party will be relying on information provided by another party, the first party should consider whether to ask for audit rights — fraud examiner Craig Greene asserts that "just as good fences make good neighbors, … audits produce good relationships."

(For some examples of real-world cases where audits proved useful, see 4.3.29.2.)

Contents:

4.3.1. Audit right

  1. This Protocol is presented in terms of one of its principal use cases, namely: when —
    • under the Con­tract, one party clearly identified in the Con­tract (the "Auditing Party")
    • will be making payments to another party (the "Recordkeeper")
    • where the payments are based on information contained in records maintained by the Recordkeeper (the "Records," defined at § 4.3.2 below).
  2. When this Protocol is part of the Con­tract, the Rec­ord­keep­er will allow the Auditing Party to have audits done in accordance with this Protocol.
  3. The parties could adopt this Protocol for use in situations not involving payments. If that happens, the parties will act generally in accordance with this Protocol, with any necessary modifications.
Note

().  In a pinch, a drafter might be able to just use "The Rec­ord­keep­er will allow the Auditing Party to have audits done in commercially-reasonable fashion, with escalation to a neutral in case of disagreement about reasonableness." That would defer discussion until a need arose.

Subdivision 3: The legalese term for this "necessary modifications" concept is the medieval Latin phrase mutatis mutandis, or, "necessary changes having been made."

4.3.2. Record maintenance

The Rec­ord­keep­er maintains "Records," namely records that (i) come within the scope of § 4.3.3 below, and (ii) evidence the following, when applicable under the Con­tract:

  1. labor, materials, and other items delivered to the Auditing Party, by or on behalf of the Rec­ord­keep­er, under the Con­tract;
  2. amounts billed to the Auditing Party, by or on behalf of the Rec­ord­keep­er, under the Con­tract;
  3. compliance with specific requirements of the Con­tract, on the part of the Rec­ord­keep­er (and that of the Rec­ord­keep­er's subcontractors, if any), including any reporting requirements, when the Con­tract states that such compliance may be audited;
  4. the relevant accounting procedures and practices; and
  5. any other clearly-agreed auditable matters.
Note

().  This section is adapted in part from the contract in suit in an Eleventh Circuit case. See Zaki Kulaibee Establishment v. McFliker, 771 F.3d 1301, 1308 n.13 (11th Cir. 2014) (reversing, as abuse of discretion, and remanding district court's denial of plaintiff's request for an accounting).

Auditable records could include, for example, documentation of the Rec­ord­keep­er's sales, where the Rec­ord­keep­er is, say:

  • a store in a commercial building, reporting its sales to a landlord for purposes of calculating agreed percentage-rent payments to the landlord; or
  • a licensee under a patent, reporting its sales to the owner of the patent, for purposes of calculating agreed running-royalty payments to the patent owner for use of the patented invention.

    Drafters: You might want to look over a long "laundry list" of specific types of documents that a party might want to require a contractor to maintain, published by the Association of Certified Fraud Examiners; it's undated and no longer available online but archived at https://perma.cc/HP6G-LEAA:

Such records shall include, but not be limited to, accounting records, written policies and procedures; subcontract files (including proposals of successful and unsuccessful bidders, bid recaps, etc.); all paid vouchers including those for out-of-pocket expenses; other reimbursement supported by invoices; ledgers; cancelled checks; deposit slips; bank statements; journals; original estimates; estimating work sheets; contract amendments and change order files; backcharge logs and supporting documentation; insurance documents; payroll documents; timesheets; memoranda; and correspondence.

4.3.3. Broad definition of "Records"

Except as otherwise stated in this Protocol or elsewhere in the Con­tract, the term "Records" encompasses all records:

  • in any form or storage medium,
  • that are maintained for the Rec­ord­keep­er, whether by the Rec­ord­keep­er or someone else.

4.3.4. Recordkeeping standards

The Rec­ord­keep­er maintains Records in accordance with: (a) any specific standards adopted in the Con­tract, or if none, then (b) commercially-reasonable standards.

Note

The Con­tract could also adopt Protocol 5.7 (more-specific recordkeeping requirements).

4.3.5. Deadline for requesting audits

The Rec­ord­keep­er honors an Auditing-Party request to audit a given Record if one or more of the following is the case:

  1. the Auditing Party asks for the audit, in writing, on or before the date three years after the last day of the calendar year in which the substantive content of the Record was most recently revised in any non-trivial way;
  2. the request is for clear good reason as specified at § 9.8.12; and/or
  3. the Record in question is still subject to a legally-enforceable record-retention period.
Note

This calendar-year countdown clock allows for easier computation of the relevant date(s). This could be important if litigation ever ensues — as was the case when the industrial giant Honeywell waited too long to audit royalties owed under a patent license agreement, and so the licensee wasn't obligated to true-up an underpayment of royalties that the audit revealed. See Honeywell Int'l, Inc. v. OPTO Electr. Co., No. 3:21-CV-00506 slip op. at introduction (W.D.N.C. Apr. 20, 2023) (granting partial summary judgment to defendant); see also id. at part III.A.1, text acc. n.6. Honeywell appealed but later dismissed the appeal, one imagines because the parties settled the case.

4.3.6. Allowable audit frequency

Unless clear good reason exists (see § 9.8.12), the Rec­ord­keep­er need not allow an audit to start any sooner than one calendar year after a previous audit ended — even for Records that were created or updated in the interim.

Note

In the worst case, constant audits would entail costs and disruption for the Rec­ord­keep­er. So, let's require a "decent interval" between audits. ¶ Concerning a calendar year, see § 20.8.

4.3.7. Advance notice of audits

The Auditing Party provides the Rec­ord­keep­er with reasonable advance notice of an audit.

Note

Advance notice of an audit gives the Rec­ord­keep­er a chance to collect and sort its records, remedy any inadvertent deficiencies, etc. — that can help lower the cost of the audit for all concerned. (Of course, if the Auditing Party has good reason to suspect fraud, then a surprise audit might well qualify as "reasonable.")

4.3.8. Permissible auditors

  1. The Auditing Party checks with the Rec­ord­keep­er, in advance, about who would do the audit.
  2. The Auditing Party does not try to use as an auditor:
    1. any individual or firm to whom the Rec­ord­keep­er reasonably objects within a reasonable time; nor
    2. any individual firm engaged on a contingent-fee basis unless the Rec­ord­keep­er affirmatively agrees in writing (regardless whether the Rec­ord­keep­er objects).
  3. In case the issue comes up: The Rec­ord­keep­er's silence about a proposed contingent-fee auditor does not mean that the Rec­ord­keep­er agrees to that auditor.
Note

().  Subdivision 1: It makes good business sense to let the Rec­ord­keep­er know who might go trawling through the Rec­ord­keep­er's books.

Subdivision 2.a: Any Big Four accounting firm would typically be considered a reasonable choice for auditors (as long as not paid on a contingent fee basis), but they don't come cheap.

Subdivisions 2.b and 3: Contingent-fee auditors would have a financial incentive to err on the side of "finding" errors. This could be especially problematic if the auditors' findings were agreed to be binding. Moreover disputes about a contingent-fee auditor's findings likely would be expensive and time-consuming for all concerned.

Danger of in-house auditors? Often, employees of the Auditing Party and its affiliates might not be considered reasonable auditors — but the Rec­ord­keep­er should consider agreeing anyway, to help keep costs down, because the Auditing Party might not want to bear the expense of having an outside auditor do the job, and instead might prefer to send in one of its own employees to "look at the books."

Use the Rec­ord­keep­er's own auditor? Contracts consultant John Tracy once suggested, in a LinkedIn discussion thread (membership required), that an auditing party should consider engaging the outside CPA firm that regularly audits the recordkeeping party's books. John says that this should reduce the cost of the audit and assuage the recordkeeping party's concerns about audit confidentiality; he also says that "the independent CPA will act independently rather than risk the loss of their [sic] license and accreditation and get sued for malpractice."

4.3.9. Required: Auditor commitments

The Auditing Party make sures that each auditor (individual and/or firm) is subject to a binding commitment to comply with the following requirements:

  1. Professional standards: Each auditor complies with customary professional standards for auditors or inspectors in the auditor's field of practice and jurisdiction.
  2. Confidetiality of Rec­ord­keep­er information: Each auditor preserves in confidence all Rec­ord­keep­er information learned the course of the audit, in generally the same manner as certified public accountants in the United States are required to do with their clients' confidential information.
  3. Strictly limited report to Auditing Party: No auditor discloses to the Auditing Party any more information of the Rec­ord­keep­er except reporting, in reasonable detail, any noncompliance with the Con­tract requirements that is indicated by the audit.
  4. Copy of audit report to Rec­ord­keep­er: The auditor promptly provides the Rec­ord­keep­er with a complete and accurate copy of the audit report (at no charge to the Rec­ord­keep­er).
Note

().  The Rec­ord­keep­er might be OK not bothering to have the auditors sign a formal agreement — if the auditors already have appropriate professional obligations that can be enforced by the Rec­ord­keep­er as a third-party beneficiary (on that subject, see Protocol 11.8) and not just by the Auditing Party. See, e.g., Rule 1.700 of the Code of Professional Conduct of the American Institute of Certified Public Accountants (2014, updated 2025) or its successor.

Subdivision 2: The Recordkeeper could try to get the auditor to agree to a detailed confidentiality agreement. But that might be an iffy proposition, and negotiating such an agreement could delay getting started.

Subdivision 3: The Auditing Party will want to hear — directly from the auditor(s) — whether an audit revealed any discrepancies. (Basic fairness dictates that the Rec­ord­keep­er also be informed if the auditor(s) conclude that discrepancies exist.)

Subdivision 4: The Rec­ord­keep­er will want a copy of the report directly from the auditor to help guard against the risk of deception by the Auditing Party. (See also 8.29.) The Auditing Party shouldn't object: if litigation ensued, the Rec­ord­keep­er's lawyers would likely get a copy from the auditor(s) in discovery — for settlement, sooner is better.

4.3.10. Times and places for audits

The Rec­ord­keep­er is free to specify reasonable times and places for requested audits, as long as the Rec­ord­keep­er:

  1. lets the auditor and the Auditing Party know a reasonable time in advance; and
  2. takes into account any input they might have.
Note

().  The idea is to mitigate disruption to the Recordkeeper's business: • Reasonable places would ordinarily include the location(s) where the Records are kept in the ordinary course of business, to help reduce audit costs and help auditors spot signs of tampering. • Reasonable times would normally be the regular working hours, at the relevant location, of the party having custody of the records. See, e.g., Hubbs at 4 (2012).

Sometimes the Rec­ord­keep­er might legitimately prefer to have the auditor(s) work at a different location, e.g., to avoid disruption to the Rec­ord­keep­er's business routine.

See also the escalation requirement.

4.3.11. Auditor workspace

The Rec­ord­keep­er makes available to the auditor — at no charge — standard business workspace in the Rec­ord­keep­er's facilities to the extent reasonably available to the Rec­ord­keep­er; this would normally include, for example, office-type facilities, in reasonable locations, with normal heating, air conditioning, restroom facilities, etc.

Note

It's not unheard of for a hostile recordkeeping party to force auditors to work in uncomfortable spaces.

4.3.12. Records as kept in ordinary course

The Rec­ord­keep­er arranges for the relevant Records to be made available to the auditor as those Records are kept in the ordinary course of business.

Note

Auditors might want to use the Rec­ord­keep­er's recordkeeping practices to inform what tests they do on the Records.

4.3.13. Party cooperation

  1. The Auditing Party and Rec­ord­keep­er work together in a professional manner with a view to expeditiously getting the audit done.
  2. The Rec­ord­keep­er directs its people to cooperate with auditors; this would include, for example, answering reasonable questions and providing access to documents in response to reasonable requests.
Note

().  Subdivision 1: You'd hope, and maybe even expect, that everyone involved in a contract-related audit would conduct themselves professionally. Unfortunately, that might not always be the case, for example if the parties had become antagonistic towards each other.

Subdivision 2: A neighborly contract party wouldn't let its people stonewall auditors or try to make their jobs more difficult.

4.3.14. Withholding from audit

  1. The Rec­ord­keep­er is free to withhold from audit any Records that contain or reveal:
    1. information subject to an attorney-client privilege or other legal immunity from discovery in litigation; and/or
    2. technical trade secrets of the Rec­ord­keep­er (and/or subcontractors of the Rec­ord­keep­er, if any).
  2. The Rec­ord­keep­er lets the Auditing Party know if it withholds Records under this section. (But the Rec­ord­keep­er need not go into detail — for example, the Rec­ord­keep­er need not produce a privilege log.)
Note

().  Subdivision 1.a: Concerning the attorney-client privilege, see 8.30.

Subdivision 1.b: Financial-type audits normally shouldn't require giving auditors access to technical trade secrets. For other types of audit, though, access to technical information might be appropriate and even necessary.

Subdivision 2: This falls under the general rubric of "Talk to each other!"

4.3.15. Permissible limiting of auditor access

  1. The Rec­ord­keep­er is free to set reasonable limits on auditor access to Rec­ord­keep­er facilities, computers, etc. (and those of Rec­ord­keep­er subcontractors, if any) to provide reasonable protection for privileged- or confidential information — but the Rec­ord­keep­er:
    1. lets the auditors and the Auditing party know about it a reasonable time in advance;
    2. takes into account any input that the auditors and the Auditing Party might have; and
    3. escalates any dispute on this point as stated in § 4.3.26.
  2. This section does not imply that the Auditing Party is entitled to access Rec­ord­keep­er facilities, computers, etc.

4.3.16. Finish-up deadline

  1. This section applies if an audit has not been completed within three months after the audit's start date, as that start date is reasonably reported by the auditor.
  2. The Rec­ord­keep­er may advise the Auditing Party — in writing — and, optionally, the auditor (whether or not in writing), that the audit must be completed no later than a reasonable, clearly-stated deadline.
  3. After that deadline passes, the Rec­ord­keep­er may stop allowing the Auditing Party's auditor to access the Records and to the Rec­ord­keep­er's facilities and people.
  4. This section likewise applies to Records, facilities, and people of Rec­ord­keep­er subcontractors (if any).
Note

().  Sometimes audits can go on seemingly forever — see, e.g., Rubin & Linskey (2022), recounting Donald Trump's assertions about the IRS's audits of his tax returns — so a Rec­ord­keep­er might well want to impose a completion deadline.

This section draws on concepts in paragraph 5(i) of the BookBaby terms of service.

Subdivision 2: A writing is required here to forestall disputes about whether a deadline was or wasn't communicated orally.

Subdivision 2: A reasonable deadline would be one that was communicated in advance.

4.3.17. Copy of audit report from auditor

The auditor promptly provides the Rec­ord­keep­er (at no charge) with a complete and accurate copy of the audit report.

Note

The Rec­ord­keep­er will want to get a copy of the auditor's report directly from the auditor, and not from the Auditing Party — this is reasonable, because it helps guard against the risk of deception by the Auditing Party.

The Auditing Party shouldn't object to this. That's because, if litigation were to ensue, then the Rec­ord­keep­er's lawyers would likely be able to get a copy directly from the auditor(s) anyway as part of the discovery process.

So: The earlier that the Rec­ord­keep­er does get such a copy, the earlier that the parties are likely to come to a settlement of the dispute.

4.3.18. Deadline for audit-report objections

  1. The Auditing Party and the Rec­ord­keep­er each state any objections they have to the audit report — in a reasonably-detailed writing to the other party — no later than the date three months after the date that the objecting party gets a copy of the audit report from the auditor.
  2. After that time, the audit report is final and binding on all parties except in cases of proven intentional fraud (as opposed to constructive fraud).
Note

().  If each party is satisfied with the audit report, that party will want to be able to "close the file" on the audit — and preclude later (and possibly-opportunistic) objections by the other party.

Source: This section draws on concepts from the BookBaby terms of service.

4.3.19. True-ups

  1. After each audit, the parties promptly true-up any discrepancies that are identified in the audit report.
  2. If the audit revealed a shortfall in a payment, where it was A's obligation to compute the amount of the payment, THEN:
    1. A includes, in its true-up payment, interest on the underpaid amount(s), at the Wall Street Journal's prime rate plus three percentage points — or if less, the maximum rate allowed by law — from the original date(s) due until paid; and
    2. Protocol 4.9 (interest charges) applies, including but not limited to its usury-savings provision.
Note

().  Subdivision 2.a: In a small way, charging interest on a party's underpayments will help discourage that party from "shorting" payments.

(Too-low an interest rate would give a party an incentive, albeit possibly a small one, to cheat.)

Subdivision 2.b: Concerning usury-savings clauses, see 4.15.6.

4.3.20. True-up as EXCLUSIVE REMEDY

A true-up is each party's EXCLUSIVE REMEDY for discrepancies unless the audit revealed (a) intentional fraud, or (b) material breach of the Con­tract, on the part of the other party to the Con­tract.

Note

().  Apropos of the exclusive-remedy provision (§ 4.3.20): In an "ordinary" audit, the whole point is to find and fix deficiencies, so an audit will usually end with a true-up to remedy any discrepancies revealed by the audit. But sometimes an audit will reveal things such as intentional overbilling that amounts to fraud. Example: A trucking company, over the course of three years, submitted 645 fraudulent invoices to a customer, accompanied by forged emails that supposedly showed pre-approval by the customer. See Contitech USA v. McLaughlin Freight Services, Inc., 91 F.4th 908, 911 (8th Cir. 2024).

In fraud cases like that, a true-up shouldn't be the exclusive remedy because that would create "moral hazard," i.e., an incentive for a party to roll the dice and engage in fraudulent behavior because the fraud might never be detected and the only downside would be to have to pay what you owe anyway.

As an example of moral hazard, here's a situation that can arise in enterprise software license agreements with unlimited use rights:

  • Instead of buying licenses for a fixed number of employees to use the software (for example), the customer is free to allow as many of its employees to use the software as desired.

    (Software could also be licensed based on other metrics, e.g., the number of transactions processed, the number of machine installations, etc.)

  • Periodically, e.g., quarterly, the customer does a true-up: The customer reports its software usage to the vendor and pays the agreed license fee for any new users.

Sometimes, though, the customer will intentionally underreport its software usage and underpay the license fees — which cheats the vendor out of legitimate revenue. That's why some software vendors periodically audit their customers to enforce the license payment terms. See, e.g., Oracle License and Services Agreement paragraph O; Barnett (2015).

In such a situation, without an exclusive-remedy limitation of liability, the vendor might want to be free to demand a greater measure of damages for the discrepancy revealed by the auditor's report if that were available by law — such as indirect damages resulting from copyright infringement if the audit showed that the Rec­ord­keep­er had used licensed software for more than it had paid for. (See also the related commentary at 4.13.8.15 concerning whether late payment could be regarded as infringement.)

4.3.21. Audit expenses

Each party pays its own audit-related expenses except as stated in this Protocol.

Note

In commercial contracts, auditing parties typically pay for their own audits (although that's not always the case). The exceptions below are standard practice.

4.3.22. Expense shifting for discrepancies

Upon request, the Rec­ord­keep­er promptly reimburses the Auditing Party, as provided in Protocol 4.7, for reasonable fees and expenses paid to the auditor by the Auditing Party if all of the following are true:

  1. the audit revealed a discrepancy in the Rec­ord­keep­er's favor;
  2. the discrepancy exceeded 5% — for the entire period being audited, not for some shorter interim period;
  3. the discrepancy occurred because of something that was the Rec­ord­keep­er's responsibility.
Note

().  Subdivision 1: See also the fee-shifting for fraud or material breach provision below.

Subdivision 2: The discrepancy threshold for audit-expense shifting will often be: • in the range between 3% and 7% for discrepancies in payments for royalties, percentage rent, and the like; and • perhaps 0.5% for discrepancies in billing for services.

Subdivision 3: Suppose that, for some reason, the Rec­ord­keep­er made a mistake, but the mistake was due to some fault on the part of the Auditing Party. (Example: A customer audits a service provider; the audit reveals that the customer underpaid the provider.) In such a situation, it wouldn't be fair for the Rec­ord­keep­er to have to reimburse the Auditing Party for the Auditing Party's audit expenses.

4.3.23. Expense shifting for fraud or material breach

  1. A promptly reimburses B for B's audit expenses (without regard to discrepancy levels) if the audit revealed or confirmed: (a) fraud, and/or (b) a material breach,
    • in either case: on the part of A and/or any of A's subcontractors (if any),
    • where the fraud or material breach adversely affected B.
  2. If B claims that an audit revealed fraud or material breach, in support of an assertion that the exclusive-remedy limitation of § 4.3.20 above does not apply, THEN: Whichever party prevails concerning that allegation is entitled to recover its attorney fees as provided in Protocol 21.2, even if the Con­tract would ordinarily say otherwise.
Note

().  Subdivision 1: This section doesn't authorize — but neither does it prohibit — the use of subcontractors by the Rec­ord­keep­er.

Subdivision 2: This is intended to create at least some incentive for the parties to settle such allegations instead of (expensively) pushing them through to a judgment.

4.3.24. Option: Recordkeeper Reimbursement

  1. This Option applies only if:
    1. the Con­tract clearly adopts this Option; and
    2. the Rec­ord­keep­er is not required to reimburse the Auditing Party's expenses of an audit under the Con­tract.
  2. The Auditing Party reimburses the Rec­ord­keep­er — and the subcontractors of the Rec­ord­keep­er, if any — for all reasonable expenses actually incurred by them in connection with the audit.
Note

Audits aren't cost-free for the Rec­ord­keep­er — who'll pay its expenses? "[A]udit provisions rarely address the apportionment of the costs incurred by the contractor or its subcontractors in facilitating the audit, managing the audit, reviewing and responding to the audit results, and other related activities …." Albert Bates, Jr. and Amy Joseph Coles, Audit Provisions in Private Construction Contracts …, 6 J. Am. Coll. Constr. Lawyers 111, 132 (2012).

4.3.25. Auditor retention of Record copies

If an auditor asks, THEN: The Rec­ord­keep­er provides the auditor with a reasonable number of copies of requested Records, at no charge, for the auditor to examine and retain in confidence.

Note

CPA firms and other auditors will normally want to retain copies of Records, in case questions are raised later whether their work was up to snuff. (Chances are that many of the records being audited will be in electronic form, in which case copying expense should be nominal.)

4.3.26. Escalation

If either party asks: The parties escalate, in accordance with Protocol 21.11, any disagreement about how this Protocol should be applied in connection with any proposed audit-related activity.

4.3.27. Incorporation of other LCP26 protocols

Thee following LCP26 provisions are incorporated by reference into this Protocol:

  1. Protocol 9.8 (inspections);
  2. Protocol 9.4 (computer-system access) (when such access is involved); and
  3. Protocol 9.13 (site visits) (ditto).
Note

This section helps avoid duplication by following the general "be modular" theme of this book.

4.3.28. Survival of audit-related provisions

After any termination or expiration of the Con­tract, the audit-related provisions of the Con­tract will continue in effect, as stated in Protocol 18.1 (survival), for matters that were subject to audit before termination or expiration, except as specifically provided otherwise in the Con­tract.

Note

It pays to be clear whether a contract's audit clause will survive the contract's demise; otherwise, the question might have to be expensively litigated. Example: A union lost its contractual right to audit a company's pension books under a collective-bargaining agreement ("CBA") because the company had terminated the CBA. See New England Carpenters Central Collection Agency v. Labonte Drywall Co., 795 F.3d 271 (1st Cir. 2015).

4.3.29. Additional notes

4.3.29.1. A shorter-form audit clause

Here's a condensed version of this Protocol:

Audits: (a) The Auditing Party may have commercially-reasonable audits conducted, from time to time, by independent outside auditors, of the Rec­ord­keep­er's non-privileged books and records documenting the Rec­ord­keep­er's performance of its obligations under the Con­tract. (b) Any disagreement concerning an audit are to be escalated internally by the parties and then, if necessary, to a neutral for a non-binding recommendation admissible as an expert report.

Or with (much) more detail, and still in single-paragraph format for easier copying and pasting:

Audits: (a) The Auditing Party may have commercially-reasonable audits conducted from time to time — upon reasonable advance notice — by commercially-reasonable independent auditors, and in strict confidence — of books and records of the Rec­ord­keep­er — in the form in which they are kept in the ordinary course of business — documenting the Rec­ord­keep­er's performance of its obligations under the Con­tract, excluding technical trade secrets as well as materials subject to the attorney-client privilege or other immunity from discovery. (b) The Rec­ord­keep­er will provide reasonable cooperation with the auditor(s) — including but not limited to directing the Rec­ord­keep­er's personnel to respond to reasonable questions from the auditor(s) (c) the parties will promptly "true-up" any discrepancy revealed in an audit, with interest on overcharges at the maximum rate allowed by law beginning on the date of each overcharge. (d) The Rec­ord­keep­er must reimburse the Auditing Party for the auditors' reasonable fees and expenses of an audit if that audit reveals a discrepancy, for which the Rec­ord­keep­er is responsible, of greater than 5% for the period being audited.

4.3.29.2. Examples of audit payoffs

Here are just a few examples of how audit rights either did pay off — or might have paid off.

•  As reported in the Wall Street Journal:

Publishing company Gannett Co. provided inaccurate information to advertisers for nine months, misrepresenting where billions of ads were placed, according to researchers who provided their findings exclusively to The Wall Street Journal. …

* * * 

In another example observed by a Wall Street Journal reporter, Capital One and American Red Cross bought ads that seemed as though they would appear on the Sarasota Herald-Tribune website, based on the information provided in the real-time auction. In fact, the ads ran on the website of Ruidoso News, a biweekly newspaper in New Mexico.

An American Red Cross spokeswoman said the organization was unaware of the issue.

Capital One didn’t respond to a request for comment.

(Extra paragraphing added.)

•  As reported in the New York Times: A woman was convicted of fraud for providing fake customer lists to JPMorgan Chase while selling her financial-aid startup company to the bank; she was sentenced to 85 months in federal prison. "Though the bank eventually pieced together the scheme after conducting its tests, its due diligence team failed to sniff out the fraud during the acquisition." Ron Lieber, Charlie Javice Sentenced to 85 Months in Prison for Fraud (NYTimes.com Sept. 29, 2025) (gift article).] Another observer noted: "JPMorgan enacted a third-party marketing company to verify [the startup company's] user data, but the third-party company primarily counted data fields instead of authenticating actual users." Abbie Staiger, Learning from JPMorgan's $175M Due Diligence Error (AFCE.com 2025).

And there was a knock-on effect: JPMorgan found itself being billed for some $60 million for the woman's legal fees — as the NY Times also reported: "JPMorgan said in a filing last month that Ms. Javice engaged five separate law firms, and that she and her lawyers have treated the original ruling forcing the bank to pay for her defense as a 'blank check to bill and expense whatever they please.' The stable of lawyers that she has used have also represented Elon Musk, Harvey Weinstein and Sam Bankman-Fried." Ron Lieber, She Took JPMorgan for $175 Million. That Doesn’t Include Her Restaurant Bills. (NYTimes.com Nov. 14, 2025) (gift article).] (Anticipating just this possibility, § 14.1.4 of {{{NAME Protocol 14.1 (Defense Against Claims Procedure Protocol) gives the defending party the right to control the defense.)

4.3.29.3. What sorts of things might might auditors look for?

In a 2003 article, fraud examiner Craig Green lists a number of things that such folks often look for, including, for example:

  • fictitious "shell entities" that submit faked invoices for payment;
  • cheating on shipments of goods, e.g., by shorting goods or sending the wrong ones;
  • cheating on service performance, e.g., by performing unnecessary services or by invoicing for services not performed;
  • billing at higher-than-agreed prices;
  • kickbacks and other forms of corruption;
  • and others. See Craig L. Greene, Audit Those Vendors (ACFE.com 2003).

For another overview of issues generally addressed in audit clauses, see a 2020 FTI article that suggests, among other things:

  • letting the auditor check completeness, "the right to verify that information excluded is correctly excluded, ie the completeness check"; and
  • "[r]eporting processes and the customer’s right to comment on audit findings."

4.4. Backup Payment Source Protocol

A Biller might be concerned whether its Payer will actually pay what it owes — that can be a particular concern for the Biller if the Biller expects to spend considerable money of its own "up front" for the Con­tract.

Contents:

4.4.1. Parties; scenario

When this Protocol is agreed to, it signifies that under the Con­tract a party clearly specified in the Con­tract (a "Payer") is expected to owe money to another clearly-specified party (a "Biller").

4.4.2. Requirement

If the Biller asks in writing, then the Payer promptly establishes — and continuously maintains in effect:

  • one or more arrangements,
  • with one or more backup payment sources,
  • to which the Biller can look to for payment,
  • in case the Payer does not pay on time.

Each such backup payment source is referred to here as a "Bank."

4.4.3. Expenses

  1. As between the Payer and the Biller, the Payer pays all expenses of backup-payment arrangements under the Con­tract.
  2. The Payer does not ask the Biller for reimbursement of those expenses without prominently reminding the Biller of the Payer's responsibility under this § 4.4.3.
Note

().  Subdivision 1: Backup-payment arrangements likely won't be free (see 4.4.11.6). Alternative: "The Biller must pay (or, upon request, reimburse the Payer for) all expenses of backup-payment arrangements under the Con­tract."

Subdivision 2: We don't want the Payer's people — motivated by budget constraints, KPIs, or whatever — to think, Why not ask the Biller for reimbursement: the worst that can happen is that the Biller says no, because good business partners don't do that to each other.

4.4.4. Biller's approval

  1. The Payer obtains the Biller's written approval of:
    1. each Bank; and
    2. each backup payment arrangement with each Bank.
  2. The Biller will not unreasonably withhold, delay, or condition its approval of a proposed Bank or backup payment arrangement.
  3. The Biller will be deemed to have approved the proposal if the Biller does not object to a proposed backup payment arrangement within a reasonable time.
  4. For emphasis: The Biller's actual- or deemed approval of a backup payment arrangement will not reduce the Payer's payment obligation(s) under the Con­tract.
  5. Protocol 12.2 (consent- or approval requests) is incorporated by reference into this Protocol.
Note

In deciding whether a particular backup-payment arrangement was acceptable, it'd normally be reasonable for the Biller to take into account, for example, some or all of the following things:

  1. Was the Bank in decent financial shape itself?
  2. Was the Bank was located somewhere that it wouldn't be a huge pain for the Biller to sue the Bank for payment if necessary?
  3. Would the backup-payment arrangement cover pro-rata payments for partial shipments of goods (and/or for services as performed)?
  4. Would order-cancellation or ‑termination charges be covered?
  5. Would the Bank reimburse the Biller if the Biller had to refund a Payer payment in bankruptcy proceedings — for example in settlement of a claim for refund of a "preference" payment (see 31.2.3)?

(The above list draws on ideas seen in § 2.2 of a General Electric terms-of-sale document, archived at https://perma.cc/8LRL-PFL3.)

4.4.5. Bank confirmation

For each backup-payment arrangement, the Payer has the Bank, within a reasonable time, provide the Biller with written confirmation that the agreed arrangement has been established.

Note

This is an example of where confirmations from third parties can (unfortunately) be useful, as discussed at 8.29.

4.4.6. Delay of performance

The Biller may hold off on incurring any further burden or expense under the Con­tract until the Biller has received the confirmation required by § 4.4.5.

Note

Relatedly, see Protocol 15.4 (adequate assurance of performance), which is derived from UCC § 2-609, which applies by its terms to a sale of goods.

4.4.7. Duration

The Payer keeps each backup-payment arrangement continuously in force for at least 6 months — or (with bankruptcy law in mind) for 15 months if the Payer is an "insider" of the Biller — after the latest to occur of the following:

  1. the last scheduled shipment of applicable ordered goods, if any;
  2. completion of all applicable ordered services, if any;
  3. the Biller's receipt of the final payment covered by the backup-payment arrangement; and
  4. any other events clearly specified in the Con­tract.
Note

These 6- and 15-month requirements stem from the fact that conceivably — even after the Payer has paid the Biller in full — the Payer could file for bankruptcy protection and then, under 11 U.S.C. § 547(b), demand that the Biller refund the final payment(s) as a "preference payment" (see 31.2.3).

4.4.8. Modifications

If: The Biller reasonably requests in writing, THEN: The Payer promptly arranges for:

  1. reasonable modification of the backup-payment arrangement; and
  2. confirmation of the modification — again, by the Bank, to the Biller.
Note

().  Whether or not a particular modification request was reasonable could depend on things such as (for example): • the Payer's payment history; • other fact(s) bearing on the Payer's present- and likely future ability and/or willingness to pay; and/or • any more-specific examples that are listed in the Con­tract (if any) as "safe harbor" reasons for the Biller to request a modification.

Subdivision 1: Depending on the circumstances, a requested modification to a backup-payment arrangement could include, for example, an increase in the coverage amount of the arrangement; an extension of the term of the arrangement; and/or changing to another Bank.

Pro tip: BILLER: If you're going to ask for changes to a backup-payment arrangement, you should consider proactively providing the Payer with reasonable detail and perhaps appropriate supporting documentation.

4.4.9. Escalation

If either party asks, the parties escalate disagreements about the reasonableness requirements of this Protocol:

  1. first, to supervisors as provided at Protocol 3.4; and
  2. if necessary, to a neutral advisor as provided at Protocol 21.11.
Note

See the commentary at the linked sections.

4.4.10. Option: Backup Payment Material Breach

If this Option is agreed to, THEN: The Payer's failure, for any reason, to timely provide, maintain, and/or modify, any backup-payment arrangement required by the Con­tract is considered a material breach on the Payer's part.

Note

The consequences of a material breach of contract can be significant; moreover, courts will generally defer to a contract's explicit statement that a particular type of breach would be "material," as discussed in more detail at Protocol 18.6. For that reason, the Biller might want the Payer to stipulate that the Payer's breach of its backup-payment obligations would indeed be material — thus giving the Biller a bit more leverage over the Payer in case of difficulties.

4.4.11. Additional notes

4.4.11.1. Not getting paid can sometimes be a real risk

In some deals, a party's prospect of not getting paid can be a non-trivial risk:

Example: At the start of the COVID-19 lockdown in 2020, Walmart entered into a "Supply Agreement" — basically, a framework agreement or master purchase agreement — with a company called K7.

  • Under the Supply Agreement, Walmart placed successive orders adding up to millions of bottles worth of hand sanitizer in bottles.
  • At first, Walmart "collected" the orders from K7's warehouse, as called for in the Supply Agreement, and paid K7 for them.
  • But as consumer demand tapered off, Walmart started failing both to pick up the orders — leaving K7's warehouse bulging with bottles — and also to pay K7 for them.

K7 sued Walmart for breach of contract. Walmart defended by claiming that the Supply Agreement didn't provide a quantity or price and so was unenforceable. The jury disagreed and awarded K7 more than $7 million; the Eighth Circuit affirmed judgment for that amount plus prejudgment interest and costs. See K7 Design Grp, Inc. v. Walmart, Inc., 143 F.4th 931 (8th Cir. Jul. 11, 2025) affirming No. 5:21-CV-5069 (W.D. Ark. Jul. 24, 2023) (entering judgment on jury verdict).

What seems to have sunk Walmart's case was that:

  • The parties' email exchanges, with specifics about the quantity and pricing, appear to have clearly met the UCC requirements for enforceability, despite Walmart's seemingly "strained" arguments to the contrary.
  • There was no dispute that the Walmart buyer who'd dealt with K7 (including those email exchanges) had the authority to place orders.
  • The Supply Agreement didn't specify any particular form that an "Order" had to take to be binding.

Apparently Walmart wasn't the only retailer that refused to take delivery or pay for hand sanitizer that it ordered during the pandemic: K7 also sued the Kroger grocery chain and, separately, Five Below, Inc., a Philadelphia-based chain of speciality discount stores, alleging much the same thing as in its Walmart case. See K7 Design Grp., Inc. v. Five Below, Inc., 540 F. Supp. 3d 508 (E.D. Pa. 2021) (denying Five Below's motion to dismiss).

After a five-day trial, a jury found for Five Below on all counts. See id., No. 21-1406 (E.D. Pa. Jun. 21, 2023) (awarding costs to Five Below).

Example: During the economic downturn accompanying the COVID-19 pandemic, the prominent retail chain Paper Source:

Later, Paper Source was purchased by the owner of the Barnes & Noble bookstore chain, an activist investment management fund, Elliott Investment Management. See Nadine El-Bawab, Barnes & Noble owner buys stationery retailer Paper Source out of bankruptcy (CNBC.com May 11, 2021).

Additional reading: Alicia Tuovila, Bankruptcy Explained: Types and How It Works (Investopedia.com 2022).

Example: A target company's assets were acquired by a newly-created subsidiary of the party that the target company had anticipated would be the buyer.

  • That newly-created subsidiary turned out to be judgment-proof, so the target company didn't get all the payments it bargained for.
  • Worse: The acquisition agreement evidently didn't provide any kind of backup payment source (see 4.4), such as a guaranty (see 4.8) of the subsidiary's payment obligations.

So, the target company lost. Northbound Group, Inc. v. Norvax, Inc., 795 F.3d 647, 650 (7th Cir. 2015) (cleaned up), affirming 5 F. Supp. 3d 956, 972-74 (N.D. Ill. 2013).

(This case also illustrates the importance of making sure the contract names the correct party or parties, as discussed at 20.1.7.2.)

Example: Over the years, various enterprises associated with Donald Trump have reportedly "stiffed" a large number of creditors. See, e.g., Igor Derysh, “Trump never pays his bills”: Truth Social reportedly stiffs contractor amid financial “disarray” (Salon.com Aug. 26, 2022); Charlie Gasparino and Eleanor Terrett, Trump's social media app facing financial fallout (FoxBusiness.com Aug. 25, 2022); Alexandra Berzon, Donald Trump’s Business Plan Left a Trail of Unpaid Bills (WSJ.com Jun. 9, 2016).

4.4.11.2. One common use: Avoiding subcontractor liens in construction projects

Here's a common use for backup-payment arrangements:

  • A landowner enters into a "prime contract" with a general contractor (or "prime") to get a building built.
  • The prime contract contemplates that the general contractor will hire, coordinate, and pay, various specialist subcontractors ("subs") to do various specific things such as demolish the existing building ("demo work"); pour a foundation for the new building; erect the building's frame and roof; install electrical wiring; install plumbing; and so on.

[DCT TO DO: Diagram showing payments by customer to contractor to subcontractor?]

The general contractor's obligation to pay its subs is important to the owner: If the general contractor were to fail to pay a sub, the law would likely allow the sub:

  • to demand payment from the owner — which likely has already paid the general contractor — and/or
  • to place a lien on the owner's property, thus placing a "cloud" on the owner's title and complicating the owner's life. See generally Mechanic's lien (Wikipedia.org); Mechanic's Lien Definition (Investopedia.com).

For that reason, in negotiating the prime contract with the general contractor, the owner might well require the general contractor to obtain "payment security" to make sure that the subs got paid.

(The prime contract likely would also require the owner to obtain financing from a bank or other lender, so that the general contractor would have assurance that it would be paid.)

4.4.11.3. What form(s) of backup payment might be used?

Here are a few possible backup sources of funding:

1.  A supplier could ask for a deposit — possibly into "escrow," to be held by a third party until stated conditions are met. See Protocol 4.5 (deposits) and its commentary; see also Escrow (Investopedia.com).

2.  A supplier could ask its customer to provide a standby letter of credit ("SLOC"): In return for a fee, a bank agrees to pay the amount due if the customer doesn't do so. (In effect, a SLOC is a prearranged line of credit for Biller with Payer's bank, with Payer being responsible for repaying the bank; see generally 4.19 for a court's explanation of how SLOCs work.)

3.  A supplier could ask its customer for a guaranty from a third party — concerning which, see Protocol 4.8.

4.  The supplier could ask to take a security interest in real estate or other property (tangible or intangible), referred to as "collateral" — but that could be burdensome for all concerned, as discussed at Protocol 4.21.

5.  A customer hiring a contractor could ask the contractor to buy a payment bond from an insurance carrier, typically referred to as a "surety." Then, if the contractor fails to pay its subcontractors, then the surety is responsible for paying any unpaid suppliers and subcontractors. See generally Payment bond (IRMI.com).

In fact, a customer deaing with a prime contractor will often negotiate to require the prime contractor to obtain a payment bond. The intent is to keep the prime contractor's unpaid subcontractors and suppliers from filing a mechanic's lien or materialman's lien (nowadays often referred to as a "supplier's lien") on the customer's project. See generally Mechanic's lien (Wikipedia.org).

Indeed: Under the federal Miller Act, a prime contractor working on a government project must furnish a bond; if the prime contractor fails to pay subcontractors, laborers, and/or suppliers for "labor" or "materials," then those payees can sue the bond provider (typically an insurance carrier). See United States ex rel. Dickson v. Fidelity & Deposit Co. of Md., 67 F.4th 182, 184 (Fed. Cir. 2023): The court affirmed a trial court's judgment that a project manager's work within the statutory limitation period was not "labor" and therefore could not be collected from a surety.

But: "A key difference between suretyship and insurance is that sureties do not expect to bear the risk of loss." That is, a surety that must pay out will usually try to recoup its payment(s) from its insured, that is, from the nonpaying contractor. United Prairie Bank v. Molnau Trucking LLC, No. A23-1478, slip op. at 9 n.5 (Minn. Jul. 16, 2025) (reversing and remanding affirmance of summary judgment). Note to students: This Minnesota opinion contains a useful primer on the basics of surety law, with citations. See id., slip op. at 8-10.

Here's a scenario involving the interplay between sureties and security interests (see item 4 above: Suppose that the surety on a payment bond has to pay a defaulting contractor's suppliers, etc. — but the contractor's assets are subject to a perfected security interest held by a lender, which itself is being stiffed by the contractor. Question: Who gets priority: the surety, or the unpaid lender? Minnesota's supreme court says it's the surety: "[T]hrough the doctrine of equitable subrogation, a performing surety has priority over a secured creditor as to contract funds created by the surety’s performance on its bond obligations." Id., slip op. at 2; see also id. at part II, slip op. at 14-21 (detailed analysis and citations).

6.  A customer hiring a contractor could ask the contractor to buy a performance bond, a.k.a. a contract bond, to have a backup pot of money available:

Performance bonds might be required of companies under government contracts, such as certain oil and gas leases granted by the U.S. Government. See 30 C.F.R. § 556.900, cited in Taylor Energy Co. v. United States, 975 F.3d 1303, 1307 (Fed. Cir. 2020) (affirming dismissal of complaint for failure to state a claim).

Caution: Performance bonds might well set forth prerequisites for a contractor to be paid by the surety; failure to comply with those prerequisites might result in nonpayment, as happened, for example, in a federal-court case in Massachusetts. See Arch Ins. Co. v. Graphic Builders, LLC, 519 F. Supp. 3d 54 (D. Mass. 2021); affirmed, 36 F.4th 12 (1st Cir. 2022).

7.  Relatedly: A prime contractor could purchase subcontractor default insurance (SDI) that would allow the prime contractor (but not the end-customer) to make a claim against the policy in case of a default by a subcontractor. See Andrew Gibson, Surety Bonds vs. Subcontractor Default Insurance (JDSupra.com 2021).

4.4.11.4. Just get a deposit instead?

One easy alternative to engaging a Bank would be for the Payer to provide the Biller with a deposit (concerning which, see Protocol 4.5).

4.4.11.5. Payer bankruptcy is a big reason for backup arrangements.

Bankruptcy law is a major reason that the Biller might want the Payer to keep backup-payment arrangements in place: Without such arrangements, if the Payer were to file for bankruptcy protection, then under U.S. law:

  • the Biller might end up recovering no more than pennies on the dollar in the bankruptcy proceedings; and
  • the Biller might be forced to refund, as a "preference" (see 31.2.3), some or all of any payment made by the Payer.

Consequently, the Biller would very much like to be able to demand payment from a backup payment source such as a bank, whose financial resources would thus serve as an alternative "pot of money" from which the Biller could reimbursement of any preference refund.

(For more on personal guaranties of commercial leases in the bankruptcy context, see generally Gordon, Spero, and Vath (2024).)

4.4.11.6. Backup payment arrangements aren't free of charge

().  When a bank or other financial institution agrees to serve as a backup payer, it's highly unlikely to do so for free, unless the arrangement is folded into some other credit arrangement that Payer already has with the bank — and if the Payer must pay for a backup-payment arrangement (as in Option A), then the Payer will likely consider that expense in determining, for example, whether to accept a particular supplier's bid for an order or project.

On the other hand, if the Biller, e.g., a supplier, must pay for a backup-payment arrangement (as in Opion B), then that expense will factor into Biller's pricing position.

In Option A, subdivision 2 is intended as a guardrail, to block an unscrupulous Payer from rolling the dice and asking the Biller for reimbursement anyway, on a theory of, let's give it a shot, the worst that can happen is they say "no." That's not the behavior of a reliable business partner (and it also creates what's known as "moral hazard").

Here's a tangential point to consider: When the Bank prices its fee for serving as a backup payer (a.k.a. a "surety"), the Bank will consider its own potential risk exposure: "[I]nsurers cannot seek reimbursement from their insureds for amounts paid out under the policy, whereas sureties can require reimbursement from the obligor (contractor) for any losses incurred by the surety under the bond." Colm Nelson, Ways to Guard Against Insolvency Risks (JDSupra.com 2022).

4.5. Deposits Protocol

Deposits are commonplace in business. For example: • A supplier of goods or services might want at least some assurance that it will in fact be timely paid — a deposit, paid up front, and/or on some kind of agreed schedule, provides some such assurance.• A home builder might want a customer to put up at least some of the necessary working capital, for example to buy the needed lumber and other materials.

Note: This Protocol sets out only basic steps for handling deposits that are provided. It's up to the parties and their drafters to negotiate and document, for example, what if any deposits would be needed; in what amounts; and when made.

Contents:

4.5.1. Parties: Biller and Payer.

  1. When this Protocol is agreed to, the parties follow it whenever, under the Con­tract, one party (the "Payer") provides a deposit that is anticipated to eventually be turned over to another party (the "Biller").
  2. Depending on the circumstances: A deposit could be money, or one or more other things, or both.
  3. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference.
Note

This wording is meant to cover the Payer's providing the deposit either (1) to the Biller itself, or (2) to a third-party depositary for the benefit of the Biller.

4.5.2. Refund of unused balances

The Biller arranges for a refund to the Payer of any remaining balance of the deposit, once all Clearly-Agreed uses of the deposit have been completed, unless clearly agreed otherwise in writing.

Note

Drafters should keep in mind the difference between a refundable deposit, on the one hand, versus (for example) an earnest-money deposit that, by agreement, would serve as liquidated damages and be non-refundable if the payer were to breach.

4.5.3. No interest

Unless the Con­tract clearly states otherwise, the Payer is not entitled to —

  1. interest on any monetary element of a deposit; nor
  2. any increase in any nonmonetary element of a deposit that might occur during the time of the deposit.
Note

().  Provisions for interest on deposits will generally be custom-drafted, so they're not included here.

Note that this Protocol doesn't rule out the Biller's getting interest on the deposit.

Subdivision 2: If a "deposit" takes the form of something that reproduces or creates other products such as animals, microbes, fruits, etc., then drafters should consider: (1) who will bear the associated expenses; and (2) who is entitled to possession and/or ownership of any resulting "increase" in the deposit.

Special case: When a lawyer accepts deposits from clients to cover the lawyer's fees and/or expenses, the law — or legal-ethics rules — might require the lawyer to keep the deposits in an "IOLTA account" with very-restrictive rules about what can be done with the deposited funds. (IOLTA stands for Interest On Lawyer Trust Accounts. See generally, e.g., IOLTA Overview (AmericanBar.org, undated).

4.5.4. Safekeeping arrangements

  1. The Biller makes commercially-reasonable arrangements for the safeguarding of each deposit.
  2. If the Payer asks, the Biller consult withs the Payer about the deposit-safeguard arrangements.
  3. The parties escalate, in accordance with Protocol 21.11, any disagreement about whether the actual- or proposed safeguarding arrangements comply with this Protocol.

4.5.5. Use of deposits

The Biller uses each deposit only for clearly-agreed purposes.

Note

().  This prohibits unauthorized diversion of deposit funds, such as allegedly happened, for example, with crypto-currency exchange FTX (among countless other examples).

Pro tip: In the Con­tract, drafters should be sure to specify the conditions under which the Biller is allowed to draw on the deposit — and especially the prerequisites for the Biller to use the deposit to pay amounts that the Biller believes to be due to the Biller.

4.6. Drawbacks Protocol

Generally speaking, a "drawback" is a refund of duties or fees that a country might charge on imports of goods if those goods are re-exported in forms specified by local law, as an incentive for creating jobs in the local economy. As journalist Binyamin Appelbaum explained, aluminum components in a car might have started out as bauxite (aluminum ore) that is "mined and refined in Jamaica, shipped to northern Quebec for smelting, then hammered into car parts in Alcoa, Tenn." Binyamin Appelbaum, American Companies Still Make Aluminum. In Iceland, New York Times, July 2, 2017, section BU, at 1 (NYTimes.com); see also, e.g., the definition of drawback in Supply Chain Glossary (scm-portal.net).

For more information about drawbacks, see, e.g.: • Drawback (an overview by U.S. Customs and Border Protection, CBP.gov); • Duty Drawback Guide (UPS.com); • Will Kenton, Drawback: What it Means, How it Works, Example (Investopedia.com).

4.6.1. Parties: Biller and Payer

When this Protocol is agreed to, it concerns one party (a "Payer") that, under the Con­tract, is anticipated to owe money to another party (a "Biller").

4.6.2. Entitlement?

As between the Payer and the Biller: The Payer is entitled to any drawbacks that might be available for purchases made under the Con­tract.

Note

As between the Payer and the Biller: This language takes into account that the Payer might have some arrangement that entitles a third party to seek and keep drawbacks. (That might not even be "a thing," of course.)

4.6.3. Responsibilities

  1. As between the Biller and the Payer, it is up to the Payer to seek any drawback (at the Payer's own expense).
  2. Whichever party is responsible for seeking drawbacks: Upon request, The other party provides the seeking party — whenever the seeking party reasonably asks — with originals and/or copies of any relevant documentation in the other party's possession (at no additional charge).
Note

Pro tip: Sometimes it might make more business sense to have the Biller submit and pursue drawback claims on behalf of the Payer.

4.6.4. No guarantee

Unless the Con­tract (or other written agreement) explicitly says so, the Biller does not guarantee that any drawbacks will be available.

Note

In some transactions, the availability of drawbacks might be a material part of the Payer's financial willingness to enter into the transaction. But that should be clearly stated in writing if it's going to be the case.

4.6.5. Escalation

If either party asks: The parties escalate, in accordance with the procedures at Protocol 21.11, any disagreement about the reasonableness of the Payer's request for drawback-related documentation and/or of the Biller's compliance with this Protocol.

Note

See the commentary at the cited Protocol.

4.7. Expense Reimbursement Protocol

Some contracts — by no means all — call for one party to reimburse another party's expenses incurred. This Protocol provides a workable balance between the parties' respective desires. Note: This Protocol doesn't itself require reimbursement of expenses — any such requirement would be included in the Con­tract.

Contents:

4.7.1. Parties: Biller and Payer

When this Protocol is agreed to, it applies when, under the Con­tract, a party clearly identified in the Con­tract (the "Payer") is to reimburse another clearly-identified party the "Biller").

4.7.2. Invoicing restriction

The Biller does not ask the Payer for reimbursement of an expense under the Con­tract if the Biller knows (or reasonably ought to) that either of the following is true:

  1. the expense is not one that is clearly authorized for reimbursement under the Con­tract; and/or
  2. the Biller has not yet actually incurred the expense on a nonrefundable basis — that is, the Biller will not ask for advance reimbursement;

without first getting the Payer's specific approval.

Note

().  This section doesn't merely say that the Payer doesn't have to pay ineligible reimbursement claims. Limited language like that could tempt an unscrupulous Biller to "roll the dice" and knowingly submit ineligible or unreasonable expenses, hoping that the Payer's accounts-payable people would just unwittingly pay the improper charges — as in, What's the worst that could happen? They don't pay — and maybe they will pay. See generally Tiffany Couch, Skimming and scamming: Detecting and preventing expense reimbursement fraud (AccountingToday.com 2018).

(This is a species of what's known as "moral hazard.")

Moreover, a mere declaration that ineligible reimbursement claims need not be paid wouldn't necessarily be treated as a contractual commitment not to seek ineligible reimbursements, so that doing so anyway would be a breach of the contract. (On this general subject, see Protocol 10.2.)

When is an expense "incurred"? Nebraska's supreme court noted: "There is ample authority … that one 'incurs' an expense only when there is a legal obligation to pay it." Avis Rent A Car System, Inc. v. McDavid, 313 Neb. 479, 486, 984 N.W.2d 632, 638 (2023) (reversing summary judgment; citations omitted).

4.7.3. No expense markup

The Biller does not mark up expenses for reimbursement unless the Con­tract expressly says this is allowed (e.g., in a cost-plus contract).

Note

Litigation can result when a contract is unclear about whether expense markup is or isn't allowed. Example: In a Fourth Circuit case, a payer sued a biller for fraudulent overcharging by marking up what the payer asserted should have been pass-through expenses. The court affirmed a summary judgment in favor of the biller — but the biller still had to litigate the matter in both the district court and on appeal. See Brainchild Surgical Devices, LLC v. CPA Global Ltd., No. 24-1450, part II.A.1, slip op. at 10-14 (4th Cir. Jul. 8, 2025) (affirming, in part, summary judgment in favor of biller CPA). ] When a contract is to be cost-plus, the contractor will generally be quite clear about it in the contract.

4.7.4. Original receipts

The Payer need not reimburse an expense if the Biller has not provided the Payer:

  1. (if the Payer so agrees:) with complete and accurate copies of receipts;
  2. otherwise, with unaltered originals of receipts.
Note

().  To help guard against financial fraud, companies' internal controls typically require that receipts accompany all requests for reimbursement — but fraudsters have been known to submit forged receipts and to modify original receipts, sometimes "on a grand scale."5

Some Payers might not need receipts for stated categories or for small amounts — but fraudsters have been known to intentionally break up expense-reimbursement requests into multiple requests. See generally Abigail Grenfell, Employee expense reimbursements: Legitimate or fraudulent? (MNCPA.org 2015).

"Fun" fact (not): Companies reimbursing expenses are now having to deal with realistic, fraudulent receipts created by AI chatbots. See Sarah Kessler, When It Comes to Spotting Fake Receipts, It’s A.I. vs. A.I., N.Y. Times, Sept. 8, 2025, p.B4.

4.7.5. Payer reimbursement policies

The Payer need not reimburse Biller-submitted expenses that do not comply with one or more particular requirements of the Payer's written reimbursement policy — but the Payer does reimburse such expenses if either or both of the following is true:

  1. the Payer's policy in question is not commercially reasonable in that regard considering the nature of the expense and its role in relation to the Con­tract; and/or
  2. (for any nonrefundable expense:) the Payer did not provide the Biller with the requirement, in writing, a reasonable time before the Biller became obligated to pay the expense.
Note

().  Customers' expense-reimbursement policies are likely to be an administrative pain for a supplier — especially if the supplier has many customers and must manage compliance with many different expense policies. But compliance by suppliers is often a practical necessity, especially when dealing with large corporate customers that by law must themselves comply with internal-controls requirements.

Pro tip: The Biller should consider consulting with the Payer if the Biller can't follow (or prefers not to follow) a Payer reimbursement policy for a particular expense.

4.7.6. Additional notes

4.7.6.1. Pro tip for Billers: Pre-clear certain expenses?

Advance agreement about "borderline" expenses can help to avoid later disputes.

But: Drafters for Billers should watch out for mandatory language such as that in a clause I once reviewed, in a customer's purchase-order fine print:

–  The clause in question required any supplier seeking reimbursement to "flag" any even-arguably borderline expenses.

–  Presumably, that requirement was to help avoid unpleasant surprises in reimbursement requests.

–  But a party incurring expenses probably wouldn't want to agree to a mandatory expense-flagging requirement — because a stingy reimbursing party could try to use a supposed flagging failure as an excuse to withhold reimbursement.

If a Payer wanted to insist on preapproval rights, it could ask for language such as the following:

Payer may opt not to reimburse Biller for any expense, not preapproved by Payer, in the following categories: [FILL IN].

Note that under the above language, a Biller would not be breaching the Con­tract if it didn't get preapproval: Instead, the Biller simply might not get paid — which likely would be plenty of motivation for the Biller to get preapproval.

4.7.6.2. Payers: Would paying an improperly-billed expense be a waiver?

Suppose that a Biller submits a request for reimbursement that doesn't comply with this Protocol, and Payer's accounts-payable people process the request and pay the reimbursement. In that situation, Payer should be able to recover the payment, or to take an "offset" against the next payment due, without having Biller object that Payer supposedly waived the noncompliance.

A Payer drafter could use language along the following lines to be explicit about this:

For the avoidance of doubt: If Payer reimburses an expense whose submission did not comply with a requirement of the Con­tract, then Payer's action is not a waiver by Payer of that contractual requirement unless the circumstances unmistakably indicate otherwise.

4.8. Guaranties Protocol

When a party expects to be paid by another party under a contract, sometimes it might not clear that the other party will be good for the money. In that situation, the prospective payee might want to consider asking for a guaranty from a third party that is likely to be able to pay up. Example: A famous example: Tech billionaire Larry Ellison offered to personally guarantee $40 billion of the $108 billion offered by Paramount Skydance — controlled by Ellison and his son David — for control of Warner Brothers Discovery.

This Protocol offers a streamlined, boiled-down version of some of the most important features (at least in my view) of many "in the wild" guaranties.

Spelling: In legal writing, especially in financial contexts, guaranty (as a noun; plural: guaranties) is a document that a party signs to guarantee (as a verb) payment of another party's debt. See Guarantee, Black's Law Dictionary 849, 850 (11th ed. 2019).

Contents:

4.8.1. Parties: Guarantor; Debtor; Creditor

When this Protocol is agreed to, it signifies that under the Con­tract:

  • one or more individuals or organizations — each of which must be clearly identified in the Con­tract — each, a "Guarantor" —
  • agrees to guarantee payment, by or on behalf of a "Debtor" —
  • of an amount due to become due (the "Debt") to a "Creditor";

that Guarantor commitment is referred to here as the "Guaranty."

Note

This Protocol doesn't itself create a guaranty — that'd be done in the body of the Con­tract.

4.8.2. Written payment request

  1. The Biller need not pay the Creditor unless and until the Creditor asks for payment in a writing (the "payment request") that includes (at least) the following information:
    1. reasonable details about the Debtor's failure to pay, including at least the amount due; the due date; and any applicable cure period;
    2. reasonable details about any corresponding, then-current Debt-collection expenses for which the Creditor expects to be reimbursed;
    3. itemized amount(s) that the Creditor wants the Guarantor to pay; and
    4. reasonable supporting documentation.
  2. The Creditor may have the payment request sent to the Guarantor before the end of the Debtor's applicable cure period — assuming there is a cure period (which in some circumstances might not be the case).
Note

().  Pro tip: Preferably, the payment demand should be by notice (see Protocol 3.14), to help avoid future disputes about whether and when the Guarantor should be deemed to have received the demand.

Subdivision 1.a through 1.d: The details mentioned here could be helpful if the Guarantor wanted to ask the Debtor — with which the Guarantor presumably has some sort of relationship — "Hey what gives?" and try to get the Debtor to pay.

4.8.3. Guarantor payment due date

The Guarantor pays the Creditor the entire amount(s) described in the Creditor's payment request — assuming § 4.8.2 above has been met and no other deal-breaker problems exist with the request — no later than the following:

  1. the end of the calendar day, in the Guarantor's relevant time zone, on the date five business days after the Guarantor receives the request; or
  2. if later: the date specified in the request.
Note

().  This is based on similar language used in the guaranty in suit in an Alabama supreme court decision. See Eagerton v. Vision Bank, 99 So. 3d 299, 305 (Ala. 2012).

For more-detailed language along these lines, see paragraph 10 of a Bank of America guaranty form, at https://tinyurl.com/BAGuaranty (sec.gov).

The Guarantor's payment due date might be a subject for negotiation in the guaranty agreement.

4.8.4. Reimbursement(s) by Guarantor

  1. The Guarantor also reimburses the Creditor, in the same manner as above and in accordance with Protocol 4.7 (expense reimbursement), for each of the following:
    1. any refund of previous payments that the Creditor credited to the Debtor — for example, because of alleged "preferences" in bankruptcy or counterfeited payment checks;
    2. all court costs and out-of pocket expenses in collecting past-due amounts of the Debt and/or in enforcing the Guaranty — including but not limited to attorney fees — that the Creditor reasonably incurs from time to time; and/or
    3. any other payments, covered by the Guaranty, that are made by the Creditor.
  2. For emphasis: The Guarantor reimburses the amounts stated in subdivision 1 above regardless whether the Creditor:
    1. was legally compelled to make the refund- or other payment in question;
    2. paid that refund, or made that other payment, to settle a claim for refund or -payment; and/or
    3. paid the refund, or made the other payment, to the Debtor itself and/or to the Debtor's estate in bankruptcy or other successor.
Note

().  See also 31.2.3 (preference payments in bankruptcy) and 4.13.8.5 (even certified checks can be counterfeited).

Subdivision 1.b is meant as a guardrail against possible Guarantor delaying tactics.

4.8.5. Unconditional

The Guaranty is unconditional and is a guaranty of payment, not of collection — so the Guarantor pays the Creditor as stated in this Protocol, whether or not the Creditor tried (successfully or otherwise) to collect the past-due payment from the Debtor — whether by filing a lawsuit or otherwise.

Note

().  An "unconditional guaranty" is a guaranty of payment, not of (eventual) collection of the Debt. As the Seventh Circuit explained: "Unlike a conditional guaranty, an unconditional guaranty does not require a creditor to attempt collection from the principal debtor before looking to the guarantor." Hovde v. ISLA Develpment LLC, 51 F.4th 771, 777 (7th Cir. 2022) (affirming dismissal of creditors' claim against guarantor on statute-of-limitations grounds) (cleaned up, emphasis added).

Note: In Texas, by statute, even a guarantor of payment (as opposed to of collection) would have the right to demand that the creditor — "without delay" — file a lawsuit against the debtor, absent which the guarantor is not liable for the guaranteed payment obligation. See Tex. Civ. Prac. & Rem. Code § 43.002.

4.8.6. Creditor signature not required

The Guarantor pays the Creditor as stated in this Protocol:

  1. whether or not the Creditor accepted and/or countersigned the Guaranty, and
  2. whether or not the Guarantor was notified that this had happened.
Note

A federal district court noted that creditors typically don't "accept" guaranties, nor give notice of doing so. See, e.g., US Bank Nat'l Ass'n v. Polyphase Elec. Co., No. 10-4881 (D. Minn. Apr. 23, 2012) (granting summary judgment that bank could enforce loan guaranties even though bank had not countersigned guaranties).

4.8.7. Effect of Debtor's bankruptcy

The Guarantor pays the Creditor as stated in this Protocol even if the Debtor sought, or successfully obtained, relief under bankruptcy law, or was made the subject of an involuntary proceeding in bankruptcy.

Note

Bankruptcy law is a major reason that the Creditor might want the Guarantor to guarantee the Debt: Without a guaranty, if the Debtor were to file for bankruptcy protection, then the Creditor might end up recovering no more than pennies on the dollar in the bankruptcy proceedings — moreover, as discussed at 31.2.3, under U.S. bankruptcy law the Creditor might be forced to refund as a "preference" some or all of any payment made by the Debtor.

4.8.8. Effect of Debtor subordination agreement

The Guarantor will pay the Creditor as stated in this Protocol even if the Debtor entered into a subordination agreement with a third party.

Note

().  Generally speaking, a "subordination agreement," between the Debtor and a third party (such as a lender other than the Creditor), is an agreement that requires the Debtor to fulfill particular prerequisites — such as by paying what the Debtor owes to the third party — before the Debtor pays some or all of the Debt.

Example: In a Seventh Circuit decision about a guaranteed debt:

  • The debtor had entered into a subordination agreement that prohibited the debtor from making certain payments until specified conditions were met.
  • Those conditions hadn't been met — so the debtor hadn't paid the creditor of the guaranteed debt.

The court held that, due to the debtor's subordination agreement, the guarantor wasn't yet liable either on the guaranteed debt. See Indigo Old Corp., Inc. v. Guido, 29 F.4th 856 (7th Cir. 2022) (Easterbrook, J.), affirming No. 19 C 7491, slip op. (N.D. Ill. Nov. 29, 2020) (granting guarantor's motion to dismiss under Fed. R. Civ. P. 12(b)(6)).

4.8.9. Guarantor creditworthiness certification

By signing the Guaranty, the Guarantor is representing and warranting to the Creditor that any creditworthiness information that the Guarantor provided to the Creditor (directly or indirectly) is complete, up to date, and accurate, in all material respects.

Note

().  The Creditor might well want the Guarantor to provide basic financial information, so that the Creditor could assess the Guarantor's ability to pay the Debt if necessary; updated financial statements from time to time; and perhaps even audited financial statements that met specified accounting standards. See generally Michael H. Friedman, Public Offerings of Guaranteed Debt and the SEC's Proposed Rule Changes (PepperLaw.com 2018), which discusses Rule 3-10(a)(1) of Regulation S-X.

(No such language is provided here, because banks and other major lenders will have their own language along these lines.)

Pro tip: Drafters representing Creditors should consider: (i) requiring updated Guarantor financial statements from time to time, perhaps even audited statements; and (ii) what "Plan B" provisions to include in the Guaranty in case the Guarantor's financial position were to slip below acceptable levels.

4.8.10. No general Guarantor liability

For emphasis: The Guarantor's liability under the Con­tract is limited to that stated for a guarantor unless the Guarantor sign the Con­tract in a manner that clearly indicates that the Guarantor is a party to the Con­tract in some other capacity.

Note

One hypothetical "unless" possibility comes to mind: The Guaranty might include some kind of restrictive covenant, such as a noncompetition‑ or nonsolicitation covenant, that binds the Guarantor.

4.8.11. Effect of multiple Guarantors

  1. This section applies if multiple individuals and/or organizations are clearly identified as Guarantors.
  2. Each Guarantor is liable to pay the Creditor the full amount under the Guaranty.
  3. BUT: Each Guarantor has the right of contribution from each other Guar­an­tor — meaning that if one Guar­an­tor A ends up paying more than A's equal share of what's owed to the Creditor, THEN: All other Guar­an­tors B, C, etc., are to reimburse A, pro rata, for the excess amount that A paid.
  4. Each Guarantor is entitled to the rights — and each is subject to the obligations — of a solo Guar­an­tor under the Con­tract.
Note

().  Background: When a contract has multiple Guar­an­tors, the Creditor will likely want to be able to proceed against any and all of multiple Guar­an­tors, as is convenient for the Creditor (and perhaps the Creditor's lawyers), for the full amount of the unpaid debt; see generally joint and several liability (law.cornell.edu).

Pro tip: If you're one of multiple Guar­an­tors and will be guaranteeing multiple Debts, it's a really good idea for you to be clear about the extent to which Guar­an­tors are liable for which obligations. DCT note: When my daughter was in college, she rented one bedroom in a four-bedroom, off-campus apartment with three friends. The landlord, of course, wanted the students' parents to guarantee payment of the rent. BUT: Each parent guaranteed payment only for that parent's child, not for any of the other students' bedrooms.

Subdivision 3's This "right of contribution" means that if one of several Guar­an­tors makes a payment under the Guaranty, then the paying Guar­an­tor is entitled to be reimbursed by all other Guar­an­tors for their pro-rata shares of the payment (generally, equal shares if not otherwise agreed). See generally contribution (law.cornell.edu).

4.8.12. No cap on Guarantor liability

The Guarantor's liability to the Creditor under the Guaranty extends to the full amount specified in this Protocol unless the Con­tract clearly provides for a cap on that liability.

Note

Professor Stephen Sepinuck, a noted authority on commercial law, suggests that a guarantor might want either: • to cap the amount of the guarantor’s liability, or • to cover only a specified portion or percentage of the debt. He adds: "From the creditor’s perspective, the former is clearly preferable and the latter should be avoided at all costs" because costly disputes could arise about how particular payments are to be allocated between the guaranteed portion and the non-guaranteed portion. See Stephen L. Sepinuck, Suggestions for Drafting Guaranties, The Transactional Lawyer, Oct. 2017, at 1, 2 (Gonzaga.edu), archived at https://perma.cc/QVY7-YNPH.

4.8.13. Effect of Debt modification

The Guarantor will automatically cease to be liable under the Guaranty if the Debt is modified — unless the Guarantor consented in writing to the modification.

Note

().  This simply restates the general rule — which typically is strictly applied by courts — that "a guarantor is discharged if, without his or her consent, the contract of guaranty is materially altered." See, e.g., Eagerton v. Vision Bank, 99 So. 3d 299, 305-06 (Ala. 2012) (modification of loan discharged guarantors from further obligations) (cleaned up; citations omitted).].

Caution: Some creditors' guaranty documents "write around" this general rule by stating otherwise — but: Just imagine how that could create problems for the Guarantor, perhaps leaving the Guarantor on the hook for far more than the Guarantor signed up for.

4.8.14. Adverse Debtor information

The Guarantor is not a "surety," and thus This Protocol does not obligate the Creditor to disclose, to the Guarantor, information (about the Debtor or otherwise) that might be adverse to the Guarantor's interests.

Note

This section addresses an issue that had to be litigated in Ohio, where the state supreme court said, "Ohio does not recognize the Restatement's view that a creditor has an affirmative duty to disclose facts that materially increase risk to a surety." Huntington Natl. Bank v. Schneider, 2025-Ohio-2920 (reversing court of appeals and reinstating summary judgment in favor of bank) (extra paragraphing added).

4.8.15. Limited Guaranty defenses

If the Debtor could assert one or more defenses to collection of the Debt specifically, as opposed to a general defense such as a discharge in bankruptcy, THEN: Unless the Con­tract specifically states otherwise, the Guarantor may assert those defenses — but no others — in any action to enforce the Guaranty.

Note

See the waiver option just below for an alternative.

4.8.16. Option: Guarantor Waiver of Defenses

If the Con­tract includes this Option, THEN: By agreeing to the Guaranty, the Guarantor WAIVES each of the following:

  1. any assertion that the Guarantor's obligations under the Guaranty are allegedly illegal, invalid, void, or otherwise unenforceable — this includes, without limitation, any defense of: waiver or release of the (unpaid) Debt; statute of limitations; res judicata; statute of frauds; fraud; incapacity; minority; usury; illegality; invalidity; voidness; or other unenforceability; where the claim or defense might otherwise be available to Debtor or to any other individual or organization that might be liable in respect of the Debt;
  2. any defense that the Guarantor might have pertaining to any part of the Debt, other than the defense that all obligations under the Debt were fully performed;
  3. any setoff that might be available to the Debtor or any other person liable under the Debt — whether or not on account of a related transaction;
  4. any assertion that the Creditor "elected its remedies" by taking action such as, for example, a nonjudicial foreclosure with respect to security for the Debt — this will be true even if the election of remedies resulted, or could result, in impairment or destruction of the Guarantor's right of subrogation and/or reimbursement against the Debtor; and
  5. any other circumstance that might otherwise absolve the Guarantor of any obligation under the Guaranty.
Note

().  Banks and other creditors often want guarantors to waive any defense to the debt — so that a bank could sue a guarantor to collect a debt even if the bank would be unable to enforce the debt against the debtor.

An "absolute" guaranty would likely waive the Guarantor's defenses to the Debt — that's why some drafters for creditors like for want guaranty language to start out, "[GuarantorName] absolutely and unconditionally guarantees …." The word absolutely could preclude the guarantor from contesting the validity of the underlying payment obligation (see § 4.8.15).

Example: A bankrupt company's CEO got nowhere in arguing that he shouldn't be liable on his personal guaranty of nearly $42 million that the company owed to a bank. The CEO asserted that the debt had been fraudulently incurred, without the CEO-guarantor's knowledge, by the since-deceased president of the company (a different individual). New York's highest court rejected the CEO's argument, holding that his allegations did not overcome the waiver of defenses and "absolute and unconditional" liability provision in the guaranty. See Cooperatieve Centrale Raiffeisen-Boerenleenbank, B.A. v. Navarro, 25 N.Y.3d 485, 36 N.E.3d 80, 15 N.Y.S.3d 277 (2015) (affirming reversal of summary judgment in favor of guarantors).

Counterexample: The federal bankruptcy court in the Southern District of New York held that liquidated-damages provisions in aircraft leases were unenforceable penalties and thus — as a matter of public policy — could not be enforced against the leases' guarantors any more than they could be enforced against the original debtors. See Moayedi v. Interstate 35/Chisam Road, LP, 438 S.W.3d 1, 3 (Tex. 2014).

In what could be a counterexample, the Seventh Circuit affirmed summary judgment that a guarantor's waiver of defenses did not waive the guarantor's right to assert the statute of limitations as a defense, because the statute affected only the legal enforceability of the guaranty without negating the underlying obligation. See Hovde v. ISLA Develpment LLC, 51 F.4th 771, 777 (7th Cir. 2022) (affirming dismissal of creditors' claim against guarantor on statute-of-limitations grounds).

True: in some circumstances, it might seem unfair to make the guarantor pay an unpaid debt. But if the guarantor waives defenses to the debt, a court will often give effect to that waiver and enforce payment anyway.

California provides statutory language that can be used for waivers of defenses to a debt; see Cal. Civ. Code § 2856.

Source note: Some of the defenses waived above are based on language of the respective guaranties in two cases from the highest courts of New York and Alabama, respectively. See Cooperatieve Centrale Raiffeisen-Boerenleenbank, B.A. v. Navarro, 25 N.Y.3d 485, 488, 36 N.E.3d 80, 15 N.Y.S.3d 277 (2015); and Eagerton v. Vision Bank, 99 So. 3d 299, 309 (Ala. 2012). See also, for example, paragraphs 1, 4, and 18 of a Bank of America guaranty form at https://tinyurl.com/BAGuaranty (sec.gov).

4.8.17. Additional notes

4.8.17.1. How strictly are guaranties construed — and in whose favor?

In at least some jurisdictions, courts interpret guaranties strictly against the creditor — often relying on the contra proferentem rule on the premise that the creditor drafted the guaranty language. See Extech Building Materials, Inc. v. E&N Construction, Inc., No. A-28-24, slip op. at 10, 12 (N.J. Dec. 2, 2025).

4.8.17.2. Must a contract with a guaranty have a separate signature line for the guaranty?

In drafting a contract that includes a guaranty obligation, the safest approach might be to include a separate signature line for the guaranty: A given jurisdiction might not have a bright-line requirement on that score, but it's still best to leave no room for doubt that a signer is undertaking the obligations of a guarantor. See Extech Building Materials, Inc. v. E&N Construction, Inc., No. A-28-24, slip op. at 15, 17 (N.J. Dec. 2, 2025) (reversing appeals court and reinstating summary judgment in favor of purported guarantor — declining to adopt a bright-line approach but suggesting a separate signature line).

4.8.17.3. Be clear that the document is a guaranty

A purported guaranty document should make it clear to a signer that the signer is undertaking the obligations of a guarantor. That didn't happen in Extech (N.J. 2025): A construction company's president signed a supplier's credit application that had one signature line. The signature line included the pre-printed phrase "(No Title)." New Jersey's supreme court held that this didn't make it clear to signers that they were personally guaranteeing payment to the supplier. See Extech Building Materials, Inc. v. E&N Construction, Inc., No. A-28-24, slip op. (N.J. Dec. 2, 2025)

4.8.17.4. Be clear whose and which obligations are guaranteed

A guaranty should be clear about just whose obligations are being guaranteed, because a creditor's aggressive position on this issue — possibly for an unrelated debt — could lead to litigation. See McLane Foodservice, Inc. v. Table Rock Restaurants, LLC, 736 F.3d 375 (5th Cir. 2013) (affirming judgment in favor of guarantor; guaranty did not extend to the debt in question).

4.8.17.5. Caution: Watch out for "buried" guaranty language

A standard-form contract might include guaranty language that the parties might not have specifically discussed but that could be enforceable against an individual who signs on behalf of a corporation or LLC. Example: This happened in a Florida case where:

  • A corporation, 688 Skate Park, was the tenant in a lease.
  • The signature block correctly listed 688 Skate Park as the party agreeing to the lease.
  • The lease was signed on behalf of 688 Skate Park by one Jay Turner "as its President."
  • Unfortunately for Mr. Turner, though, the lease form also included a statement that "the individual executing this Lease on behalf of said corporation, limited liability company or limited partnership, guarantees the obligations of Tenant hereunder."

The result: A Florida appellate court held that Mr. Turner could be personally liable on the lease. See Coleman v. 688 Skate Park, Inc., 40 So.3d 867 (Fla. App. 2010) (reversing district court's dismissal of landlord's suit against guarantor; emphasis added).

Example: Similarly, in a Mississippi supreme court case, a company president signed a commercial lease in his representative capacity — but the lease also contained language stating that the company personally and unconditionally guaranteed the company's financial obligations. This, said the supreme court (citing cases), had the effect of binding the company president to the lease's arbitration clause. See R.K. Metals, LLC v. E & E Co., No. 023-CA-00620-SCT, slip op. (Miss. Mar. 6, 2025) (affirming summary judgment).

4.8.17.6. Appendix: Additional reading (optional for students)

See generally the following:

–  Stephen L. Sepinuck, Suggestions for Drafting Guaranties, archived at https://perma.cc/QVY7-YNPH (discussing various waivers of defenses).

–  Joshua Stein and Elaine Wang, Revisiting The 24 Defenses Of The Guarantor — 24 Years Later, archived at https://perma.cc/DQ8H-NL3Q.

–  Christine Anchia Crousillat and Herman Lipkis, Types of Guarantees in Commercial Leases.

4.9. Interest Charges Protocol

Most people are familiar with interest charges — but some might not know that charging interest can trigger significant legal issues, possibly even involving the Biller's forfeiting its right to be paid the entire "principal" (amount due).

Contents:

4.9.1. Parties: Biller and Payer

This Protocol will apply when, under the Con­tract, a party clearly identified in the Con­tract (the "Payer") is late in paying an amount due to another clearly-identified party the "Biller").

4.9.2. Maximum interest rate

The Biller must not charge more than 5% per annum simple interest or the maximum rate allowed by law, whichever is less.

Note

().  Many (perhaps most) jurisdictions have enacted legislation setting maximum permissible interest rates, and also whether simple- or compound interest is permitted. Drafters of interest provisions should be sure to check applicable law for the maximum interest rate.

(The maximum rate might depend on whether the parties have agreed to a particular rate.)

The gap-filler interest rate of this Protocol (i.e., a rate charged in the absence of agreement) and the "simple interest" term (i.e., not compound interest) are written with the usury laws in Texas and New York in mind. See, e.g., N.Y. Banking Law § 14-a (16%); 1077 Madison Street, LLC v. Daniels, 954 F.3d 460 (2d Cir. 2020) (affirming summary judgment rejecting usury defense); Tex. Fin. Code § 302.002 (6%, beginning on 30th day after due date); N.Y. Gen. Oblig. Law §  5-501 (6%, but with exceptions).

The Texas supreme court has noted that: "The default rule in Texas accords with the general rule: absent clear and specific contractual or statutory authorization, compound interest is prohibited, and only simple interest is available." Samson Exploration, LLC v. Bordages, 694 S.W.3d 195, 203, text accompanying nn.51-52 (Tex. 2024) (reversing and remanding court of appeals judgment): Agreement's late-charge provision was "insufficiently clear and specific to constitute an express stipulation to compound interest. Thus, only simple interest is available …." (emphasis added, footnotes with extensive citations omitted).

4.9.3. Earliest accrual start date

The unpaid amount in question will not accrue interest, and the Biller will not charge interest, before the later of:

  1. 30 days past due, or
  2. the earliest date allowed by law.
Note

This is borrowed from a Texas statute — it's included out of an abundance of caution. See Tex. Fin. Code § 302.002.

4.9.4. Itemization

The Biller will clearly itemize each interest charge in the relevant invoice to the Payer as stated in Protocol 4.10 (invoices).

4.9.5. Usury savings

Protocol 4.15 (usury savings) is incorporated by reference.

4.9.6. Additional notes

4.9.6.1. Pro tip: Are interest-charge provisions even worth it?

To speed up negotiation, a drafter representing a Biller might not want to bother including an interest provision in the Con­tract, because:

  • Even without a contract provision, the law might allow the charging of interest on past-due amounts. For example, section 302.002 of the Texas Finance Code states in part: "If a creditor has not agreed with an obligor to charge the obligor any interest, the creditor may charge and receive from the obligor legal interest at the rate of six percent a year on the principal amount of the credit extended beginning on the 30th day after the date on which the amount is due. …"
  • Some customers have been known to announce, imperiously: We don't pay interest, period, and if you want our business, that's the way it is. And so even bringing up the subject of interest might "poke the bear" (see 8.14), i.e., cause the Payer to insist that the Con­tract instead prohibit the Biller from charging interest — and such a prohibition would likely override the law's allowance of interest charges.

So: For a Biller, this could be one of those times when silence (about interest charges) might be the better choice during negotiation of the Con­tract.

4.10. Invoices Protocol

Invoices are standard practice in business — and they might be required by anti-fraud internal controls accounting regulations. This Protocol sets out a protocol for invoicing — but it also takes into account that some contracts might be of a type where invoices aren't contemplated.

Contents:

4.10.1. Parties: The Biller and the Payer.

  1. When this Protocol is agreed to, the parties follow it whenever the Con­tract calls for one party (the "Payer") to pay one or more amounts to another party (the "Biller").
  2. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference.
Note

Much of this Protocol is phrased so that sending an invoice is not a compulsory requirement — it's simply a prerequisite for the Biller to get paid.

(Reminder: Not every requirement needs to be legally enforceable — sometimes commercial motivations will work just as well, as discussed in connection with the "Pathclearer" approach to contracting, discussed at 28.2.)

4.10.2. Invoice-timing restrictions?

If: (a) The Con­tract (or other written agreement between the Payer and the Biller) includes one or more timing prerequisites for invoicing; and (b) the Biller submits an invoice to the Payer where the invoice does not meet those timing prerequisites;

Then: The Payer may disregard the invoice.

Note

().  Such invoicing prerequisites could include, without limitation:

  • a schedule, based (for example) on calendar time and/or achievement of milestones; and/or
  • deadlines, either as specified dates or tied to other events.

The timing of invoice issuance can affect the parties' respective cash flows. For example:

  • It's not uncommon for suppliers to send invoices only after they finish their performance under the Con­tract, for example, upon delivery of ordered goods or completion of services performance — and it's also very typical for customers to prefer (even insist) on this.
  • BUT: In construction- and other services agreements, the service provider will often want to get some money up front — to pay for materials, ensure that it will be paid something even if the customer stiff the provider etc..
  • A service provider will also want to be paid as soon as possible after particular phases of the contracted work are completed — as opposed to waiting to be paid until all phases of the work is 100% complete.

    Some contracts will state when interim invoices are to be sent, e.g.:

    • every month (as is typically the case with law firms' invoices) or every fiscal quarter, and/or
    • when specified performance targets are reached, e.g., when a concrete foundation has been poured for a building under construction.

4.10.3. Invoice-submission deadlines?

If: (a) The parties agree in writing that invoices must be submitted on or before a stated deadline; (b) that agreement is both clear and prominent; and (c) an invoice is submitted after the stated deadline;

Then: The Payer may decide — in the Payer's sole and unfettered discretion — both: (A) whether to pay the invoice, and (B) the timing of any payment.

Note

().  If you're a Payer, you might well have a legitimate reason for imposing a deadline for invoice submission. For example, you could be concerned about having to "restate" financial results* for the relevant fiscal period, because such a restatement could be necessary if a late invoice were to materially alter the customer's already-reported results. See generally Investopedia, Restatement.

Note: For a public company, any restatement of reported financial results is a Bad Thing: It'd likely cause a sharp drop in the company's stock price, resulting from diminished investor confidence in the company's accounting practices. Example: This happened to one company, Calgon Carbon, reportedly because the company's general counsel didn't timely forward outside law-firm invoices to the company's accounting department — evidently causing the general counsel to lose his job.6

Caution: In some jurisdictions, a court might regard such a waiver provision as being a forfeiture — and as the Texas supreme court explained, generally under U.S. law, "[f]orfeitures are not favored … contracts are construed to avoid them." Fischer v. CTMI, LLC, 479 S.W.3d 231, 239 (Tex. 2016) (citations omitted).

4.10.4. Invoice language(s)

If: An invoice is not written in both: (1) the language of the Con­tract or another language that the payer's accounts-payable people can read; and (2) any other language required by applicable law;

Then: The Payer may reject the invoice, but must promptly let the Biller know that it is doing so, and why.

Note

().  Companies sometimes use bi- or even trilingual invoice forms.

Local tax law (for example) might require invoices to be written in the local language to facilitate audits by government tax authorities.

4.10.5. Reasonable submission method

If: The Con­tract does not specify how the Biller must submit invoices under the Con­tract;

Then: The Biller may submit invoices under the Con­tract by any commercially-reasonable means.

Note

().  Pro tip: It's probably not a good idea to lock down the invoicing method in the Con­tract: That would mean that a change to that procedure could require an amendment to the Con­tract. That'd likely be a pain.

Sure, as a practical matter, if a Payer paid an "improperly" submitted invoice, that'd likely be a waiver of the submission requirement in the Con­tract. But why set that up as a potential dispute?

And keep in mind that incentives matter, too: In a B2B context, the Biller will usually be motivated to go along with any (reasonable) request that the Payer makes about invoice submission request — because the Biller will (probably) care more about getting paid quickly than about insisting on using any particular method for submitting invoices.

Pro tip for Biller billing departments: Suppose that your contract with a big-fish Payer is silent about invoicing method. It might still be worth your time to check whether the Payer prefers any particular method of invoicing. For example, the Payer might use a particular electronic invoicing system and might prefer that its suppliers submit invoices that way.

Checking with the Payer in this way could help speed up your getting paid — thus improving your company's accounting metric known as "DSOs," i.e., days sales outstanding.

4.10.6. Addresses for invoices

If: The Biller does not timely specify (in writing) one or more required addresses for invoices under the Con­tract;

Then: The Biller may submit such invoices to any sensible address.

Note

().  Even if no specific address is required, the Biller might still want to check with the Payer for the Payer's preferred address for invoices to help get paid faster.

This uses the term "any sensible address" to impose a slightly-higher standard than just any old reasonable address.

4.10.7. Itemization prerequisites

If: An invoice does not itemize all of the following: (1) taxes, shipping, handling, and insurance; and (2) any other details specified in the Con­tract;

Then: The Payer: (A) may dispute the invoice and hold off on paying the invoice for a reasonable period, but (B) must promptly let the Biller it is doing so, and why.

Note

().  Caution: The Biller will want to consider not including, in the invoice, the Biller's bank-account information, especially if the invoice might be seen by others (e.g., by email, which could be forwarded and/or hacked). It's often better to provide bank-account information by phone or other, more-secure channel.

Caution — Payer: You'll want to act promptly if an invoice doesn't contain enough "substantive details" to allow for appropriate review. That's because a court might not be sympathetic if your contract didn't require such detail. Example: A Delaware trial court held that one payer had waited too long to object to an invoice's itemization — seemingly with an ulterior motive, according to the court — and so had lost its right to contest the invoice:

Nor is the Court persuaded that Trimble's obligation to timely dispute the invoices was nullified by the invoices' lack of substantive details. The Court accepts that Trimble may have been disadvantaged by being contractually required to dispute invoices with forty-five days when the invoices didn't provide many specifics to dispute.

But litigation is not an arena in which to bargain for new terms. Trimble's concern would have been better raised when the [contract] was negotiated in early 2020. Barring that, Trimble could have brought it up in response to any one of the dozens of invoices that Trimble approved and paid. Trimble didn't do so.

Instead, Trimble waited until it had reason to evade Section 5.1 to bemoan this supposed inequity. Outbox Sys., Inc. v. Trimble, Inc., No. N21C-11-123, part IV.A.1, slip op. (Del. Super. Ct. Apr. 30, 2024) (decision after trial) (not verbatim).

For some very-detailed requirements for itemizing invoices, see the appendixes below with excerpts from purchase-order terms published by Honeywell and by Walmart.

4.10.8. Expense-reimbursement requests

If: The Biller wants to invoice the Payer for a particular expenses or category of expenses — or otherwise ask the Payer (or its affiliates or its people) for reimbursement;

Then: The Biller will follow Protocol 4.7 (expense reimbursement).

Note

This section means to discourage the Biller from "rolling the dice" by submitting an invoice for nonreimbursable expenses and hoping that the Payer's accounts-payables people won't notice the discrepancy and instead will just pay the (improper) invoice.

4.10.9. Escalation of invoice disputes

The parties will escalate any dispute about an invoice as stated in Protocol 4.12 (invoice disputes), which is incorporated by reference.

4.10.10. Additional notes

4.10.10.1. Biller: Too many incorrect invoices could cause trouble.

Many (and even most) payers will require someone knowledgeable to approve payment of each invoice. But in a trusted business relationship, you shouldn't even be sending an invoice in the first place unless you have reason to think that in fact you're entitled to payment.

Repeated invoice problems shouldn't necessarily give rise to the payer accusing you of breach of contract or misrepresentation — but it could happen ….

4.10.10.2. Biller: Include a reminder of payment methods?

If the Con­tract specifies that the Payer must use one or more particular payment methods (or that the Biller would prefer a particular method), then it'd be a good practice for each invoice to include a suitable reminder of that fact.

4.10.10.3. Appendix: Honeywell invoicing requirements

Here's a set of Honeywell invoicing requirements — extra paragraphing has been added to break up the "spaghetti paragraph" (see 2.5).

13.  Invoicing and Payment

After each shipment made or service provided, Supplier will submit an invoice listing a description of the Goods provided and, as applicable, part numbers, quantity, unit of measure, hours, and the unit and total prices.

This invoice must match the corresponding Purchase Order pricing, quantities, and terms,

and must be sent to the invoice address listed on the Purchase Order.

All applicable taxes and other Government charges including, but not limited to, sales, use, or excise taxes; value added tax, customs duties, fees and all incidental charges including but not limited to royalties, selling commissions, nonrecurring engineering, or other incidental charges must be separately itemized and identified on the invoice.

The invoice must also include the following information in English, or in the destination country’s official language if required:

(a) name and address of Supplier and the Honeywell entity purchasing the Goods;

(b) name of shipper (if different from Supplier);

(c) Honeywell’s Purchase Order number(s);

(d) country of export;

(e) detailed description of the Goods;

(f) Harmonized Tariff Schedule number;

(g) country of origin (manufacture) of the Goods, or if multiple countries of origin, the country of origin of each part shipped;

(h) weights of the Goods shipped;

(i) currency in which the sale was made;

(j) payment terms;

(k) shipment terms used; and

(l) all rebates or discounts.

The invoice will be accompanied (if applicable) by a signed bill of lading or express receipt evidencing shipment.

Payment of an invoice does not constitute acceptance of the Goods

and is subject to appropriate adjustment should Supplier fail to meet the requirements of the Purchase Order.

Payment terms are net 120 days from receipt of a Honeywell-approved invoice unless otherwise stated on the face of the Purchase Order or other written agreement executed by both parties.

Invoices will not be approved unless they accurately reference conforming Goods received by Honeywell or services satisfactorily performed for Honeywell.

Payment will be scheduled for the first payment cycle following the net terms for the Purchase Order.

4.10.10.4. Appendix: Walmart invoicing instructions

Here's a set of Walmart invoicing requirements:

Invoices submitted to Walmart must have the following information:

  • Supplier Name / Address (as registered with Walmart)
  • Walmart Supplier Number (as provided on your Welcome email)
  • Invoice Number (must be unique, numeric and a maximum of 15 characters)
  • Invoice Date
  • Invoice amount
  • Invoice amount
  • PO being invoiced (one per Invoice / Credit Memo) – Invoices without a PO number will be rejected
  • Invoice amount
  • Walmart Business Contact (Your main point of contact for day-to-day work)
  • Invoice amount
  • Walmart Department Name
  • Detail of service / goods provided
  • Remittance Information
  • Contract Number

4.11. Pay When Paid / If Paid Protocol

4.11.1. Parties: Prime, Sub, and Customer.

  1. When this protocol is agreed to, it indicates that:
    • a clearly-identified party,
    • that is anticipated to be a payer under the Con­tract (the "Prime"),
    • expects one or more of its payment to another party (the "Sub"),
    • to be funded by one or more payments by (or on behalf of) a third party (the "Customer").
  2. For this purpose, a payment to the Prime from a bank or other third party, on behalf of the Customer, would count as a payment by the Customer.
Note

The terms Prime, Sub, and Customer are used here only for convenience — those party relationships are a typical, but nonexclusive, use case.

4.11.2. Prerequisites

The Prime may hold off on paying any amount that the Prime would otherwise owe to the Sub under the Con­tract until the Prime has been paid by the Customer — but this will be true only if the Prime does both of the following:

  1. the Prime must make commercially-reasonable efforts to collect the relevant payment(s) from the Customer; and
  2. the Prime must otherwise comply with this protocol.
Note

Subdivision 1's efforts obligation amounts to a "be a good neighbor" requirement, one that's sometimes seen in pay-when-paid provisions. See, for example, the contract language cited in an Ohio supreme court case; that language provided in part that "[t]he Architect shall exert reasonable and diligent efforts to collect prompt payment from the Owner." Transtar Electric, Inc. v. A.E.M. Electric Serv. Corp., 2014 Ohio 3095, 140 Ohio St. 3d 198, quoting Thos. J. Dyer Co. v. Bishop Int'l. Eng'g. Co., 303 F.2d 655, 659 (6th Cir. 1962).

(And in some jurisdictions, this "efforts" requirement might be an implied obligation under the law.)

4.11.3. No playing favorites

If the Prime has multiple Subs under a pay-when-paid or pay-if-paid arrangement for a particular Customer matter, THEN: The Prime will distribute each Customer-funded payment pro rata among all such Subs according to the amounts owed.

Note

This might be a point of negotiation, so this section is provided as a checklist item.

4.11.4. Outside due date

The Prime will pay each Sub invoice in question within a reasonable time on or after the invoice due date — even if the Prime itself has not yet been paid by the Customer — unless the option in § 4.11.5 below (pay if paid) is clearly agreed to in the Con­tract.

Note

().  In a paid-when-paid arrangement, the Prime should eventually pay up, regardless whether the Prime has been paid — otherwise, the arrangement would be a de facto pay-if-paid term.

Language choice: This section intentionally does not require the Payer to pay the Sub before the due date of the Sub's invoice, even if the Prime has already been paid.

4.11.5. Option: Pay If Paid

  1. This Option will apply only if:
    1. the Con­tract clearly adopts this Option; and
    2. the law does not prohibit pay-if-paid provisions under the circumstances.
  2. In that situation, the Prime is free to hold off on paying any amount that the Prime would otherwise owe to the Sub under the Con­tract unless and until the Prime has been paid by the Customer; and
  3. When this Option applies, the Sub ASSUMES THE RISK that the Sub would not be paid at all if the Customer did not pay the Prime.
Note

().  Pay-if-paid clauses might not be enforceable in some jurisdictions; see 4.11.7.3.

Subdivision 3: An explicit assumption of the risk of nonpayment might enhance the enforceability of a pay-if-paid provision. As one Texas court put it: "[T]he risk of non-payment by the owner on a construction contract is not shifted from the contractor to the subcontractor unless there is a clear, unequivocable and expressed agreement between the parties to do so." Gulf Constr. Co. v. Self, 676 S.W.2d 624, 630 (Tex. App–Corpus Christi 1984) (modifying judgment below: pay-if-paid clause did not shift risk of nonpayment from prime to sub).

But: Explicit language, using the exact words "pay if paid" or "assumes the risk of nonpayment" might not be strictly necessary for enforcement of a pay-if-paid clause; an equivalent phrase such as "condition precedent" might suffice. See, e.g., BMD Contractors, Inc. v. Fid. & Dep. Co., 679 F.3d 643, 645 (7th Cir. 2012) (affirming summary judgment in favor of issuer of payment bond because pay-if-paid clause was enforceable); Transtar Electric, Inc. v. A.E.M. Electric Serv. Corp., 2014 Ohio 3095, 140 Ohio St. 3d 193, 194 ("condition precedent" was sufficient).

4.11.6. Option: Nonpayment Performance Restriction

If: The Con­tract clearly adopts this Option;

Then: The Prime will not withhold payment from the Sub unless the Customer's failure to pay the Sub is clearly due solely and directly to the Customer's dissatisfaction specifically with the performance of the Sub.

Note

This Option is based on a suggestion by attorney Sam DeBaltzo.

4.11.7. Additional notes

4.11.7.1. Caution for Sub: Payment bonds wiped out?

In some jurisdictions, a pay-if-paid clause could mean that the Sub cannot seek payment from a backup payer, or "surety," such as a payment bond, if there is one. See BMD Contractors, Inc. v. Fid. & Dep. Co., 679 F.3d 643, 649 (7th Cir. 2012) (affirming summary judgment in favor of issuer of payment bond). See generally, e.g., Robert Cox, Pay-if-Paid Clauses: A Surety's Defense for Payment Bond Claims? (JDSupra.com 2019).

4.11.7.2. Pro tip for Subs: Ask for backup-payment arrangements?

If the Sub is going to agree to pay-if-paid terms with the Prime, then the Sub should consider asking the Prime to commit to maintaining "payment security" (see Protocol 4.4) for all amounts to be paid by the Prime — including, without limitation, amounts to be paid under any (accepted) purchase orders issued by the Prime under the Con­tract. (This represents what might be one of the most common "use cases" for payment security.)

The Sub might want the payment security to take the form of:

  • an irrevocable, unconditional letter of credit (see the notes at 4.19), or
  • a bank guarantee (see Protocol 4.8), or
  • a payment bond,

in any of these cases, on terms that are reasonably acceptable to (and perhaps approved in advance by) the Sub.

4.11.7.3. Appendix: Enforceability of pay-if-paid clauses

Here's a partial list, based solely on what I happen to have encountered in my reading — be sure to check the law in your particular jurisdiction of interest.

Various states restrict or prohibit pay-if-paid clauses, e.g., California, Illinois, Massachusetts, North Carolina, South Carolina, Virginia, and Wisconsin. See Dismas Locaria and Caleb McCallum, Even Federal Contractors and Subcontractors Should Pay Heed to State Law on Conditional Payment Clauses (JDSupra.com 2022).

Nevada's supreme court has noted that "pay-if-paid provisions, while not void per se, are unenforceable if they run contrary to the rights and requirements established under NRS 624.624-.630" (state-law statutory provisions governing payment of subcontractors, etc.) and thus are to be examined on a case-by-case basis. See Helix Elec. of Nevada, LLC v. APCO Constr., Inc., 138 Nev. Adv. Op. 13, 506 P.3d 1046, 1048 (Nev. 2022) (affirming district court; pay-if-paid provision was unenforceable).

New York appears to entirely ban pay-if-paid clauses. See West-Fair Elect. Contractors v. Aetna Cas. & Surety Co., 87 N.Y.2d 148, 158, 661 N.E.2d 967 638 N.Y.S.2d 394 (1995) (on certification from Second Circuit).

Ohio, on the other hand, has the opposite rule, allowing even pay-if-paid provisions. See Transtar Electric, Inc. v. A.E.M. Electric Serv. Corp., 2014 Ohio 3095, 140 Ohio St. 3d 193. The state supreme court's decision has been criticized for not addressing public-policy considerations. See Scott Wolfe, Jr., Ohio Supreme Court Gets Pay If Paid Decision Wrong, Hurts Subcontractors (ZLien.com 2014).

Texas, by statute, has regulated "contingent payment" clauses for certain construction subcontracts; such clauses are unenforceable if "unconscionable," with the statute also providing a safe harbor for contingent payers . See Tex. Bus. & Comm. Code § 56.001 et seq., especially § 56.054(b) (safe-harbor definition); see Solorzano v. Sage Comm'l Grp. LLC, 693 S.W.3d 689, 694–96 (Tex. App.—Houston [14th Dist.] 2024, pet. denied) (contingent-payment clause was unconscionable but payee had signed release of payer).

Virginia's SB-550 bans pay-if-paid and pay-when-paid provisions in certain construction subcontracts, as well as imposing seven- or 45-day payment deadlines in many cases. See generally James Harvey, Virginia’s New Construction Payment Terms (Part 1) and (Part 2) (JDSupra.com 2022).

4.12. Payment Disputes Protocol

Disagreements about invoices aren't uncommon: • Billers can make mistakes (or overbill). • Payers can misunderstand invoices. • Payers can intentionally stiff their vendors, perhaps citing "reasons" that might or might not be valid. (See the real-world examples mentioned at 4.4.11.1.) • The Payer might take an "offset" (see Protocol 4.13.5), that is, the Payer might reduce the amount it pays by an amount that's supposedly owed to the Payer by the Biller.

Contents:

4.12.1. Parties: Biller and Payer

This Protocol will apply in any dispute, between one party (a "Biller") and another (a "Payer"), concerning payment under the Con­tract.

4.12.2. Prompt alert

The Payer will promptly alert the Biller about any parts of an invoice that the Payer disputes.

Note

This Protocol doesn't require the Payer to give the Biller formal notice of the dispute. (Concerning formal notice, see Protocol 3.14.) Caution: In some jurisdictions, there might be a statutory deadline for the Payer to object to a Biller invoice, under what are known as "prompt payment acts." See, e.g., Peter Bilowz, Rhian Cull, and Molly Quinn, Owners Beware: Massachusetts Supreme Judicial Court Underscores Strict Adherence to Prompt Payment Act (JDSupra.com 2024); Joe Virene, Texas Legislature Expands Suspension Rights Under the Prompt Pay Acts (JDSupra.com 2023); Matt Viator, Know Your States Prompt Payment Act To Speed Up Construction Payments (LevelSet.com 2018).

4.12.3. Details and documentation

In the interest of quicker resolution of the dispute: The Payer will likewise promptly provide the Biller with:

  1. a succinct (but reasonably-detailed) written explanation of the Payer's then-current reason(s) for disputing the invoice; and
  2. (if the Biller asks:) copies of any relevant documentation in the Payer's posssession, custody, or control.
Note

This requirement should help discourage the Payer from simply ghosting the Biller, or just saying, It's wrong, you figure out why, we're not paying till you fix it.

4.12.4. Supplemental invoice

  1. If the Payer asks, the Biller will provide the Payer with a supplemental, partial invoice for undisputed or resolved-dispute items.
  2. The Payer will not assert that the Biller's providing a partial invoice, in itself was a concession by the Biller that the Biller was not owed the disputed amount.
Note

().  This section intentionally doesn't state when payment is due for the partial invoice, because that would depend on the circumstances surrounding the issuance of the partial invoice. A Payer might argue that it would serve the Biller right to allow the Payer to treat the partial invoice as a new invoice that has its own payment due date. But in many circumstances, that might well be too harsh for a cooperative relationship.

Pro tip: In each such partial invoice, the Biller should consider doing the following to speed up payment:

  • identifying the original invoice;
  • including reasonable notes to help any later reviewers — such as litigation counsel — to put together a narrative of events; and
  • reiterating that the partial invoice is not a concession about any disputed amounts.

4.12.5. Payer: Pay on time, absent a showing otherwise.

The Payer will pay on time (in accordance with any agreed payment terms) each invoiced item for which the Payer does not provide the Biller with substantial evidence that the item is inaccurate or unauthorized.

Note

The wording here is informed by item 8 of Sean Hogle's checklist of provisions for getting paid, at the redline.net lawyer forum.

4.12.6. Escalation

The parties will escalate any continuing dispute about an invoice as stated in Protocol 21.11.

4.13. Payment Terms Protocol

Contracts often talk about payment terms in very-abbreviated form, e.g., "net 30 days from receipt of invoice." This Protocol sets out default (i.e., benchmark) provisions in more detail.

Billers: See generally Sean Hogle's post, Checklist: must-have provisions for getting paid, at his (eminently-useful) redline.net site for lawyers.

Contents:

4.13.1. Parties: Biller and Payer

This Protocol will apply whenever, under the Con­tract, one party clearly identified in the Con­tract (a "Biller") is owed money by another party (a "Payer").

4.13.2. Invoice prerequisite

The Payer need not pay the Biller an amount due under the Con­tract until the Biller invoices the Payer as set out at Protocol 4.10.

Note

().  Invoices typically aren't required in "strategic" transactions such as real-estate sales and mergers and acquisitions — instead, the other party simply won't go ahead with the deal (e.g., sign the real-estate deed or the merger closing documents) until the agreed payment is received.

(In such transactions, sometimes an agreed payment will be received by an escrow agent (see 31.8) and then later passed on to the payee.)

Other types of contract — for example, IP license agreements — might require the Payer to pay without an invoice or other demand for payment.

But invoices are increasingly required even in contracts such as intellectual-property license agreements: The payer would be the licensee of the IP in question, and for example submits a report of its licensed sales to the IP owner or other licensor — possibly with a proposed computation of royalties (or other amounts) due; the IP owner then sends an invoice to the licensee.

In an employment contract, it'd be nonsensical to require the employee to provide the employer with an invoice for each paycheck. (It'd be a different story for a true consulting-agreement relationship, of course.)

For that matter: In the United States, the Fair Labor Standards Act might well make it illegal for an employer even to require an employee to turn in a timesheet as a prerequisite to getting paid. See, e.g., Can we hold an employee’s paycheck because he or she didn’t turn in a timesheet? (SHRM.org, undated).

Language choice — "the Payer need not pay": To reduce the potential for disputes, this section is intentionally phrased so that the Biller's failure to submit an invoice as required by the Con­tract is not a breach of the Con­tract — it merely means that the Payer needn't pay the invoice.

4.13.3. Payment due date

The Payer will cause each invoice under the Con­tract to be paid net 30 days after the Payer receives the invoice.

Note

().  When a contract says payment is due "net 30 days," it means that payment is due in full in 30 days.

The contract might also say, for example: "Payments: 2% 10 days, net 30 days"; this means that:

  • the paying party may deduct 2% as a discount for payment in full within 10 days, but
  • payment in full is due in any case within 30 days.

Here are a few net-X-days examples:

  • Net 30 days is pretty standard for payment for goods.
  • Net 45 days and even net 60 days are generally considered to be within the band of reasonableness (more or less).
  • Contractors and other service providers often ask for net 10 or net 15 day terms, or even "due on receipt" (not uncommon for law-firm invoices to clients).
  • Some customers demand net 75, net 90, and even net 120 days — GE reportedly did this at one point — essentially using their suppliers as grudging sources of interest-free working capital.

    Payment terms are often negotiated, because as a general rule:

    1. The Biller would like to be paid as soon as possible — the Biller has (presumably) earned the money, so it wants to be able to use that money for its business purposes; but
    2. The Payer, on the other hand, would prefer to hold onto its money for as long as possible, because that allows the Payer, in effect, to use (what rightfully is) the Biller's cash to finance Payer's operations — it's as though the Biller was making an interest-free loan to the Payer.

As an extreme example, one Honeywell purchase-order form states at paragraph 13 that:

Payment terms are net 120 days from receipt of a Honeywell-approved invoice unless otherwise stated on the face of the Purchase Order or other written agreement executed by both parties. …

Payment will be scheduled for the first payment cycle following the net terms for the Purchase Order. This Honeywell purchase-order form is archived at https://perma.cc/84BS-KYXB; emphasis and extra paragraphing added. For further discussion, see generally Joanne Simpson, Extended payment terms: who really pays the price? (IACCM.com 2016); Net D (Wikipedia.org).

4.13.4. Payment method

The Payer may use any commercially-reasonable means to pay an invoice.

Note

().  The Con­tract could specifically require payment, for example:

  • by check, perhaps on a specified bank, see 4.13.8.2;
  • by cashier's check, see 4.13.8.6;
  • by domestic Automated Clearing House ("ACH") transaction, see 4.13.8.4; or
  • by international wire transfer, see 4.13.8.7.

    The Con­tract could also specify:

  • that newer forms of payment are allowed, e.g., by Zelle (an inter-bank program) or Venmo; and/or
  • that certain forms of payment are not allowed, e.g., cash; checks drawn on banks in specified countries; Bitcoin or other so-called cryptocurrencies; etc.

4.13.5. Offsets

If: The Payer deducts an "offset" (or "setoff") from a payment;

Then: The Payer must not deduct more than a precisely-established amount that is clearly already due to the Payer from the Biller.

Note

().  The term offset (or setoff or set-off) generally refers to the payer's reducing the amount of a payment by an amount purportedly owed to the payer by the biller. This can sometimes be the subject of dispute. Example: Grocery retailer Kroger successfully offset nearly $1.8 million that Kroger owed to a trucking company because the trucking company had failed to comply with an indemnity obligation — the obligation was triggered when a subcontractor of the trucking company hit a minivan head-on, killing three people, leading to a lawsuit against various defendants including Kroger. See Diamond Transp. Logistics, Inc. v. Kroger Co., 101 F.4th 458 (6th Cir. 2024) (affirming summary judgment in favor of Kroger).

This Protocol doesn't address whether the Payer may or may not take offsets.

4.13.6. Payment disputes

Protocol 4.12 (invoice disputes) is incorporated by reference.

4.13.7. Other related payments?

The payments clearly identified or ‑contemplated in the Con­tract are the only ones that the Payer need make relating to the parties' dealings under the Con­tract unless: (1) the Payer has clearly agreed otherwise; or (2) the law clearly provides otherwise.

Note

().  This is a guardrail provision: It recognizes that parties have sometimes been known to get "creative" about their (alleged) entitlement to payment. Example: One such case arose between a British billionnaire's brother and a cousin, leading to litigation. The cousin's firm was to be paid a "success fee" if he sold the family's conglomerate — no sale ever happened, but the cousin demanded payment anyway. (Spoiler: the court said "no.") See Contra Holdings Ltd v Bamford [2023] EWCA Civ 374 ¶¶ 16, 42, discussed in Alexandra Kirby and Emily Watts, Drafters beware! Court of Appeal on the significance of express terms (JDSupra.com 2023).

Reminder: The Payer might have payment obligations other than those stated in the Con­tract.

4.13.8. Additional notes

4.13.8.1. A Biller might worry about theft of payments

A Biller might want to restrict Payer payments for fear of theft. Example: A sales agent in Mexico, employed by a New York-based exporter, accepted cash payments from a exporter customer in Mexico but failed to forward hundreds of thousands of dollars of those payments. See Vista Food Exchange, Inc. v. Comercial de Alimentos Sanchez, 147 F.4th 73 (2d Cir. Jul. 24, 2025) (reversing and remanding, in part, summary judgment dismissing exporter's breach-of-contract case against customer).

4.13.8.2. The Con­tract could specify a particular bank for checks

For payments by check, the Con­tract could require the check to be drawn on, for example:

  • a U.S. bank; or
  • a specifically-identified bank; or
  • any bank to which the Biller doesn't reasonably object in writing.
4.13.8.3. Caution: A bankrupt Payer's check might be frozen

When an ordinary check is written, the money stays in the Payer's account until the check is "presented" to the Payer's bank for payment. This means that the check might not clear if the Payer were to file for bankruptcy protection — because the bank is likely to freeze the Payer's account. See generally Check (Investopedia.com).

(These days, check clearance is almost always done electronically if the Biller uses a different bank than the Payer.)

4.13.8.4. Paying by ACH

Payment by automated clearing house ("ACH") is an electronic debit transaction in lieu of a check. See generally Automated Clearing House (ACH) (Investopedia.com); for international transactions, see SWIFT (Stripe.com).

Caution: As with payment by check (4.13.8.3), if the Payer files for U.S. bankruptcy protection before the check clears, then the check might never clear.

Caution: It's a bad idea to include, in the Con­tract itself, Biller's bank-account information for ACH transaction:

  • The Con­tract might someday be disclosed to others, such as in a due-diligence effort.
  • The Con­tract might someday become publicly available — such as the Payer's having to file the contract with the SEC as a "material agreement" but failing to ask for confidential treatment of the bank-account information.
  • It's not unknown for one party to expose another party's confidential information to the public by filing the information with the SEC.7 (See Option § 5.3.33.4 to Protocol 5.3 concerning confidential information, which addresses the possibility of such disclosures.)

In such a situation, the Biller's bank-account information could end up available to an unknown number of others.

A better way to do this is to say, in the Con­tract, that the Biller will separately provide wire-transfer information. (This should be done by secure means.)

4.13.8.5. Paying by certified check

A certified check is written by the Payer and drawn on the Payer's bank account, but the bank guarantees to the Biller that the bank has put a hold on Payer's account for the amount of the check. This means that the check shouldn't bounce if it can legally be paid. See Certified check (Investopedia.com).

Caution: With a certified check, the money stays in the Payer's account until the check clears; this means that the same bankruptcy issues exist as for regular checks (4.13.8.3).

Caution: Certified checks can be counterfeited, in which case the bank might not have to pay, and if the Biller cashes the check, the Biller might have to refund the money (that's probably in the bank's standard customer agreement that the Biller had to sign to open an account with the bank).

4.13.8.6. Paying by cashier's check

A cashier's check is written by the bank itself using funds in the Bank's own account, not the Payer's account: When writing that check, the bank transfers the stated amount of money from the Payer's account to the bank's own account. See Cashier's check (Investopedia.com).

(Note the difference between this and a certified check, discussed above.)

The Con­tract might specify what bank, or what type of bank, is to be used for a cashier's check.

Caution: Cashier's checks can be counterfeited, meaning that the Biller might be on the hook to refund the payment, as noted above.

4.13.8.7. Paying by wire transfer

Payment by wire transfer would give the Biller "immediately-available funds" that the Biller could immediately withdraw and spend if desired. See generally Wire transfer and Available funds (each at Investopedia.com); for international transactions, see also SWIFT (at Stripe.com).

Caution: As with ACH payments (see 4.13.8.4), don't include bank-account information in the contract itself.

4.13.8.8. Don't wait to long to challenge an invoice?

In this Protocol, § 4.12 doesn't set a fixed deadline for a Payer to challenge a Biller invoice. But the Payer shouldn't string the Biller along with unspecified grumbling about the invoice while withholding payment.

Example: In a Delaware case, the trial court held that a customer was liable for certain unpaid vendor invoices because the customer had complained about invoices, but the customer had not challenged the invoices within the time prescribed by the contract. The court observed: "Voicing displeasure and asking for accountability is not the same as challenging [the vendor's] right to payment." The court continued: "Trimble's right to directly challenge the invoiced amounts sunsetted pursuant to the [contract's] plain terms." Outbox Sys., Inc. v. Trimble, Inc., No. N21C-11-123, slip op. at part IV.A.1 (Del. Super. Ct. Apr. 30, 2024) (decision after trial).

Moreover, § 4.12's requirement of a timely explanation, in subdivision B, is just good-neighbor behavior: The Payer might be tempted not to say anything until the Biller asks, "hey, where's our money?" and/or to withhold all payment, in either case, as a cynical way of increasing the Payer's leverage and extending the payment terms. That kind of nickel-and-diming behavior, though, shouldn't happen in a trustworthy- and cooperative business relationship.

4.13.8.9. Payment usually wouldn't cancel other rights

It's pretty well established that when the Payer makes a payment under the Con­tract, that in itself doesn't limit any rights that the Payer might have concerning the subject of the payment — such as, for example, warranty rights against the Biller.

Example: Suppose that the Payer hasn't yet paid the Biller's invoice, and that the Payer and the Biller are having a dispute about something relating to the invoice, perhaps about the quality of the Biller's deliveries. The Payer could fear that paying the invoice might be interpreted as acceding to the Biller's position or otherwise prejudicing the Payer's rights. But that shouldn't be the case unless the Payer had clearly agreed otherwise.

4.13.8.10. Payer should consider paying under protest

In some jurisdictions, if someone pays an incorrect invoice without protest, it might not be possible to recover the overpayment. See James D. Abrams and Erica L. Cook, Voluntary Payment Doctrine: A Useful Affirmative Defense or Instrument of Evil? (AmericanBar.org.2016), archived at https://perma.cc/5HY2-9YD2/.

4.13.8.11. Use "baseball" arbitration for payment disputes?

Payment disputes are a quintessential example of how last-offer arbitration (a.k.a. "final offer" or "pendulum") can be used to promote settlement, as discussed at Protocol 21.11.

4.13.8.12. Caution: "Paid in full" check notations could be binding

From the other side of the coin: Question: What if you're a supplier and a customer sends you a partial payment that's marked "Payment in Full"? Answer: If you cash the check, you might very well be stuck — possibly losing out on a very-large amount due. See, e.g., Scott Wolfe, Jr., Are Checks with “Payment in Full” in Memo Line Legally Binding? … (Levelset.com 2019 & 2021); Sara Lipowitz, 'Paid in Full' Check Memo (Lawyers.com 2020).

Example: The insurance carrier United HealthCare of Texas found itself stuck with a $24,000 settlement of United's $2 million overpayment claim against a physicians' group:

  • United asserted that the physicians' group had been overpaid by some $2 million.
  • As a settlement offer, the physicians' group sent — to United's lockbox contractor, Wells Fargo — a check for $24,000, marked "Full and final payment" of the dispute. The physicians' group also sent copies of the settlement proposal to multiple United addressees, including United's in-house counsel.
  • As United's lockbox contractor, Wells Fargo automatically cashed the settlement check.

A Texas court held that United had ample notice that:

  • the check was part of a settlement proposal, and
  • had United exercised due diligence, it would have had ample time to stop its lockbox contractor, Wells Fargo, from cashing the check.

Therefore, said the court, United was bound by the settlement offer — and thus recovered only $24,000 of what United claimed had been United's $2 million overpayment to the physicians' group. See United Healthcare of Texas, Inc. v. Low-T Physicians Service, P.L.L.C., 660 S.W.3d 545 (Tex. App–2023) (affirming declaratory judgment).

4.13.8.13. In what order would payments be applied?

It'd be fairly typical for the Biller to apply payments under a contract to the Payer's then-unpaid payment obligations — in the order of date incurred — as follows:

– First: The money paid would be used to pay off any accrued but unpaid interest;

– Then: Any money left over would be applied to reduce the unpaid principal balance. See generally David Cook, The Interest Tail Wags the Profit Dog, Business Law News, Issue No. 3, 2014 (State Bar of California Business Law Section; available on-line to Section members).

Order-of-payment language is often seen in promissory notes and other loan documents, and sometimes in contract language allowing interest to be charged for past-due payments (concerning which, see 4.9).

4.13.8.14. Late payments could trigger advance-payment demands

See Protocol 4.2 and its commentary concerning demands for payment "up front" even if the Con­tract provides other payment terms.

4.13.8.15. Would late payment make the Payer an IP infringer?

In theory, being an IP infringer, due to late payment, could have serious financial consequences:

  • Suppose that a customer were late in paying the price of a patented- or copyrighted product purchased from a vendor.
  • The vendor could try to claim that the customer's unpaid use of the product constituted infringement of the vendor's intellectual-property rights — and that the customer therefore owed the vendor a portion of the customer's profits as indirect damages for the infringement, not merely as damages for breach of contract.

I'm not aware of any cases specifically on point. But some well-known companies have been hit with such profits-as-indirect-damages awards for analogous conduct, including for example the air-conditioning company Carrier,8 the MGM Grand Hotel,9 and the Allstate insurance company.10

4.13.8.16. Might Biller want to "factor" its accounts receivable?

Pro tip: If the Biller didn't want to wait so long for its money, it could consider factoring its accounts receivable, namely selling its invoice(s) to a third-party "factor" — but at a discount from face value. See generally Note.

(A strong-arming customer's purchase order form might purport to prohibit the Biller from factoring the customer's invoices.)

Relatedly, see the discussion of "pledges," to a creditor by a debtor, of the debtor's right to be paid under a contract, at 15.3.

4.14. Tax Responsibilities Protocol

4.14.1. Applicability

The parties will follow this Protocol whenever, in connection with the Con­tract, any potentially-taxable event occurs of the kinds described in this Protocol.

4.14.2. Specific taxes

Each party must see to it that all taxes assigned to that party below, if any, for the matter(s) being invoiced, are timely reported and remitted to all appropriate authorities:

  1. Biller: All sales- and value-added type taxes (see the definition at § 4.14.5), no matter where imposed.
  2. Payer: All use- and/or consumption-type taxes.
  3. Each party: All taxes on that party's own net income, profits, windfall profits, and the like.
Note

().  The term "see to it" recognizes that the parties might "hire out" some or all of their tax-related obligations.

Parties should consider confirming the jurisdictions where sales-, use-, value-added (VAT), and income taxes must be collected, reported, and paid — in the Internet age, that's not necessarily a trivial question. This question is especially germane because when tax authorities believe taxes to be due in connection with a transaction, they've been known to try to collect the taxes from anyone involved in the transaction. See generally Sales tax (Wikipedia.org) (includes links for value-added taxes and use taxes); Sales Tax 101 for Online Sellers (TurboTax.Intuit.com 2021).

It often will make more sense for the Payer to handle the necessary reporting- and remittance paperwork for use taxes — which nowadays is likely to be done over the Internet, of course (and possibly by an online service).

Tangentially: Sometimes a contract might call for a payment to be "grossed up" so that, after income taxes, the payment equals a specified amount; see 4.17 for discussion.

4.14.3. Tax-exempt certificate?

If: The Payer claims to be exempt from any tax to be reported and remitted by the Biller under the Con­tract;

Then: The Payer will timely provide the Biller with appropriate official tax exemption certificate(s) — otherwise, the Biller may charge the Payer all such taxes as applicable (if any), in which case the Payer will pay all such charges.

Note

Tax authorities are likely to be unimpressed by a claim of tax-exempt status without supporting evidence, which usually must take the form of an official certificate.

4.14.4. Related indemnity obligations

Each party A is to defend and indemnify each other party and each other party's Protected Group B from any claim — by a government authority, or otherwise — arising from A's allegedly not carrying out A's tax obligation(s) under the Con­tract.

4.14.5. Definition: Sales tax

For this purpose, the term "sales tax" (whether or not capitalized) refers to the following in any relevant jurisdiction:

  1. sales taxes;
  2. value-added taxes;
  3. excise taxes;
  4. other forms of ad valorem tax; and
  5. taxes equivalent to any of the foregoing.

4.14.6. Definition: Tax

In this Protocol (and otherwise in the Con­tract unless the context clearly indicates otherwise), the term "tax," whether or not capitalized:

  1. refers to any tax, assessment, charge, duty, levy, or other similar charge of any nature, imposed by any "taxing authority," defined below; but
  2. does not include a price charged by a taxing authority for any of the following: (i) services rendered by the taxing authority or a related entity, nor (ii) goods or other assets sold or leased by the taxing authority or a related entity.
Note

().  The definition of tax in § 4.14.6 draws on a variety of sources. See, e.g., Innophos, Inc. v. Rhodia, S.A., 10 N.Y.3d 25, 27-28 (2008), cited in Hughes Communications India Private Limited v. The DirecTV Group, Inc., 71 F.4th 141, 148 (2d Cir. 2023) (vacating and remanding summary judgment; citations omitted); section 3.5(e) of a 2006 Asset Purchase Agreement between Piper Jaffray Companies and UBS Financial Services, excerpted in David Zarfes & Michael L. Bloom, Contracts and Commercial Transactions (Wolters Kluwer Law & Business 2011).

Some parties might want to include an even more-detailed "laundry list" of possible taxes. Quite often, though, that will be overkill that just makes the Con­tract less readable.

Illustrating the breadth of the term tax: The Second Circuit concluded that a satellite TV license fee, charged by an Indian government agency, was a "Tax" as defined in a corporate spin-off contract, and therefore DirecTV was obligated to indemnify the spun-off company for the fee: "New York law requires indemnification agreements to be strictly construed; a court cannot find a duty to indemnify absent manifestation of an unmistakable intention to indemnify." Hughes Communications India Private Limited v. The DirecTV Group, Inc., 71 F.4th 141, 148 (2d Cir. 2023) (vacating and remanding summary judgment; citations omitted).

4.14.7. Definition: Taxing authority

In this Protocol (and otherwise in the Con­tract unless the context clearly indicates otherwise), the term "taxing authorithy," whether or not capitalized, refers to any authority (governmental or otherwise) that exercises the power to impose, regulate, or administer or enforce the imposition of taxes, whether that power is derived from law or is merely de facto.

Note

Under this definition, a taxing authority could be (without limitation) an armed gang that uses de facto power to collect payments in the nature of taxes.

4.15. Usury Savings Protocol

4.15.1. Parties: Biller and Payer

  1. The parties here are referred to as the "Biller" and the "Payer".
  2. The parties will follow this Protocol if unlawful interest is charged, by on behalf of the Biller, or paid by or on behalf of the Payer.
Note

Caution: This Protocol might be disregarded in some jurisdictions such as New York (see the note at § 4.15.3).

4.15.2. Amortization

Each party will treat all interest-like charges and payments as if they had been amortized (or otherwise spread over time) to the greatest extent not inconsistent with law — the intent here is to reduce the effective interest rate charged or paid, ideally below the maximum lawful rate.

Note

For usury-savings purposes, Texas law requires amortization or spreading to be done in accordance with the actuarial method, which "calls for interest amounts to be calculated for each payment period, based on the declining principal balance." American Pearl Grp., L.L.C. v. Nat'l Payment Sys., L.L.C., No. 24-0759, slip op. at 11 (Tex. May 23, 2025) (on certification from 5th Cir.).

4.15.3. Mistake?

Each party will treat any charging of interest, in excess of the maximum lawful rate, as the result of a mistake.

Note

().  This kind of importuning language ("charging the illegal interest was just a mistake!") can work in some jurisdictions such as Texas, which allow parties to reduce the chances of usury problems by agreeing in advance to take certain actions in case of unlawful interest charges. See generally Spence (SDLLaw.com 2020) (with extensive citations to Texas case law).

But such importunings might well have little or no effect in jurisdictions such as Michigan11 and New York12 (the latter of which apparently brushes off usury-savings clauses entirely, although New York's usury laws do contain significant exceptions).

The policy behind unenforceability of usury-savings clauses was explained by the District of Columbia Court of Appeals (which is not the federal D.C. Circuit):

It would run contrary to our usury statute to permit creditors to avoid its sting via savings clauses purporting to cap the loan’s interest rate to the maximum allowed by law. The animating force of usury statutes is to relieve the borrower of the necessity for expertise and vigilance regarding the legality of rates he must pay, putting that onus instead on the lender to set the rate in clear terms that are within the bounds of the law. Sloan v. Allen 323 A.3d 439, 444 (D.C. App. 2024) (cleaned up, formatting edited).

Likewise, Rhode Island's supreme court acknowledged that the state's usury statute was "draconian" and "strong medicine," because the legislature had put the risk of charging too high an interest rate onto the lender in "an inflexible, hardline approach to usury that is tantamount to strict liability …." The court affirmed a trial-court ruling that a commercial loan agreement for more than $400,000 was void as usurious. LaBonte v. New England Dev't R.I., LLC, 93 A.3d 537, 544 (R.I. 2014).

4.15.4. Refundable credit

  1. The Biller will promptly do the following whenever excess interest is charged or paid:
    1. issue the Payer a refundable credit, computed as stated in subdivision 2 below;
    2. apply the refundable credit first to any remaining principal balance; and
    3. refund any remaining amount of the credit.
  2. The amount of the refundable credit will be:
    1. the full amount of the excess interest charged and/or paid; plus
    2. interest, at the maximum legal rate, on any excess amount paid (not just charged), from the date of the payment until the date credited.
Note

().  This "first to any remaining principal balance" approach can be seen in a number of in-the-wild usury savings clauses. See, e.g., these clauses (LawInsider.com).

A variation on this idea seems to be OK in jurisdictions such as California. See Korchemny v. Piterman, 68 Cal. App. 5th 1032, 1042-43 (Cal. App. 2021) (affirming judgment of usury and awarding attorney fees); In re Dominguez, 995 F.2d 883 (9th Cir. 1993) (affirming bankruptcy court judgment that usury was successfully avoided by savings clause).

4.15.5. EXCLUSIVE REMEDY

The Payer, and anyone claiming to have rights "through" the Payer, will treat the right to a refundable credit under this Protocol as being the EXCLUSIVE REMEDY for the Payer's being charged, or paying, interest in excess of that allowed by law — unless the Payer shows, by clear and convincing evidence, that the Biller knew that the interest it was charging was unlawful.

Note

().  The term "through" the Payer means that some third party asserts that the third party has some sort of right by virtue of some relationship between the third party and the Payer. [DCT TO DO: Come up with an illustrative example?]

The "unless" exception is included to try to reduce "moral hazard" by creating a disincentive for the knowing charging of unlawful interest.

4.15.6. Additional notes

4.15.6.1. For usury purposes, not all charges are "interest" …

Not all charges for past-due amounts will be deemed "interest" under applicable law.

().  Here are a few examples of charges that were held not to constitute usurious interest under Texas law:

In Southwest Concrete (1990), California's supreme court ruled that the state's usury law does not cover interest charged on overdue commercial accounts. As explained in Sunstate (Cal. App. 2023), the contract at issue in Southwest Concrete, for rental of construction equipment, allowed the renter to be charged interest on late payments at 18% per year. The supreme court ruled that:

  • the state's usury law limits the interest payable for the loan or forbearance of money; and
  • the substance of the transaction did not have "as its true object the hire of money at an excessive rate of interest." Southwest Concrete Prods. v. Gosh Constr. Corp., 51 Cal.3d 701, 704, 798 P.2d 1247 (1990) (affirming court of appeals's affirmance of denial of motion for JNOV or new trial on grounds of usury), discussed in Sunstate Equip. Co. v. Eagle Environmental & Constr., No. A167708, slip op. (Cal. App. Dec. 15, 2023) (unpublished) (reversing trial court's award of only 7% interest).

    Relatedly: Some professional athletes have sold the right to receive a percentage of the athletes' future earnings in return for an upfront payment. Such an arrangement has been referred to as an "income purchase agreement," resembling a venture-capital investment agreement. For example:

  • As a minor leaguer, Fernando Tatis, Jr. received (reportedly) a $2 million advance from a buyer, Big League Advance (which was started by a former MLB pitcher) in exchange for 10% of his future earnings.
  • Tatis later signed a $340 million contract extension with the San Diego Padres — which would have entitled the buyer to more than $30 million from the arrangement.
  • Tatis sued to void the contract; at this writing, the suit is pending. See Timothy Hurley, The Cost of An Early Payday: Lessons from Tatis Jr.'s Advance Financing Agreement (JDSupra.com 2025); Associated Press, Padres' Tatis sues Big League Advance to void deal signed at 17 (ESPN.com 2025).
4.15.6.2. … but other charges might be deemed "interest"

Under New York law, "a stock conversion option that permits a lender, in its sole discretion, to convert any outstanding balance to shares of stock at a fixed discount should be treated as interest for the purpose of determining whether the transaction violates N.Y. Penal Law § 190.40, the criminal usury law"; and "if the interest charged on a loan is determined to be criminally usurious under N.Y. Penal Law § 190.40, [then] the contract is void ab initio …." Adar Bays, LLC v. GeneSYS ID, Inc., 37 N.Y.3d 320, 324 (2021), on certification from Second Circuit in 962 F.3d 86 (2d Cir. 2020), subsequent proceeding, Adar Bays, LLC v. GeneSYS ID, Inc., 28 F.4th 379 (2d Cir. 2022) (vacating and remanding summary judgment order).

4.15.6.3. Caution: A usury-savings clause should apply to all interest charges

A federal trial court in California held that a usury-savings clause operated only in the event of default in payment on promissory note and did not "unconditionally operate to limit the interest rate [on the note] to the maximum non-usurious rate." Consequently, the court denied the lenders' motion for summary judgment.

In re Village Concepts, Inc., slip op. at part V.H (E.D. Cal. Mar. 17, 2015) (cleaned up).

4.15.6.4. A lower price for cash might not be "interest"

By statute in Texas (and other jurisdictions), clearly offering a lower price for cash payment, as well as a higher credit- or time-based price, doesn't count as interest if the purchaser knowingly chose the higher price. See Spence, supra, at 27 (with extensive citations, including Tex. Fin. Code § 301.002(4)).

4.16. Earn-out payments (notes)

Here are some extremely rough notes:

Delaware: The implied covenant of good faith and fair dealing doesn't protect an earn-out recipient when the buyer rejected a good-faith-efforts obligation, saying that the implied covenant would govern, and the contract contained an integration clause: "If the Sellers' counsel and [the buyer's] counsel came to a separate agreement about the term the Sellers' counsel proposed [i.e., the implied covenant], that is precisely the kind of separate agreement that the parol evidence rule forecloses. Trifecta Multimedia Holdings Inc. v. WCG Clinical Services LLC, 318 A.3d 450, 458, 467-70 (Del. Ch. 2024) (granting, in part, defendants' motion to dismiss; footnotes omitted). See also the discussion of the "no reliance" issue in this case, at 11.7.6.2.

– A Vinson & Elkins recent-developments memo about some Delaware earnouts cases, mainly focusing on different versions of "use commercially-reasonable efforts" language that led to very-different results.

–  Earnouts are on the rise in M&A, per the WSJ (Jan. 2024). See also Maria Koury and Julian Landau-Sabella, Use of EBITDA in Earnouts Increased 22% in Two Years (JDSupra.com 2023).

–  "Todd J. Mortier invented a medical device. He sold it to LivaNova USA, Inc. in order to develop and bring to market. When LivaNova shut down the project, he sued. The district court granted summary judgment for LivaNova. Mortier appeals. … [T]his court affirms." Mortier v. LivaNova USA, Inc., 71 F.4th 1139, 1142-43 (8th Cir. 2023) (affirming summary judgment in favor of defendant LivaNova).

–  See the discussion of the Russell v. Zimmer, Inc. case at 31.7.4.

–  Jury Says No Breach, No Bad Faith, No $30M: GR Energy Services v. Odessa Pumps:

Those two pieces of the deal took centerstage over the past three weeks in Harris County District Judge Michael Gomez’s courtroom as a jury worked to discern two things: whether Odessa Pumps acted in bad faith in the way it managed Flex Flow to avoid having to pay the earnout, and whether GR violated the noncompete agreement through its communications with SpaceX about a potential pump deal.

Jurors deliberated for a few hours before determining Tuesday that Odessa Pumps had not acted in bad faith and that GR had not violated the noncompete agreement. They did not reach a third question, where GR had sought $29.8 million in damages for Odessa Pump’s alleged bad faith actions.

Odessa Pumps did not seek any damages on its noncompete claim against GR.

–  Example: Northbound Group v. Norvax was an earn-out dispute that illustrates the importance of making sure the contract names the correct party or parties, lest the actual named party turn out to be judgment-proof; see the discussion at 20.1.7.2.

–  New York evidently has a statute prohibiting what amount to earn-outs, i.e., fee splitting by licensed professionals, e.g., in connection with a sale of a dental practice. See Advanced Dental of Ardsley, PLLC v. Brown, 2024 NY Slip Op 03804, 229 A.D.3d 589, 215 N.Y.S.3d 426 (App. Div. 2024) (reversing denial of motion to dismiss).

4.17. Gross-up of payments, e.g., for taxes (notes)

In some contracts, it might be part of the parties' bargain for the paying party to "gross up" its payments to another party, so that the recipient's net amount received is equal to a stated amount.

Caution: It's not a matter of paying just the additional amount due for the tax on the underlying amount, but another additional amount to cover the tax on the first additional amount. The Investopedia entry Grossing up includes a "worked example" with hypothetical numbers for a company to gross up an employee's $100K salary to cover an income-tax rate of 20%: The company must pay the employee an additional $25K on top of the employee's $100K salary, not just an additional $20K, because the employee will owe income tax on the $20K amount as well.

Example: In the ISDA Master Agreement, a standardized contract in the financial world, section 2(d)(i) of the 2002 version (the most-recent version at this writing) requires gross-up of payments.

Example: As a non-tax example, a commercial landlord might charge the tenants of a building with a pro-rata share of the building's operating expenses based, not on actual percentage occupancy, but on 95% to 100% occupancy, so that the tenants, not the landlord, are covering those costs. (Of course, tenants might have a different opinion about whether the landlord should be able to offload, onto the tenants, a portion of the landlord's financial risk that part of the building might be sitting empty ….) See Lauren Beames and Laura Walda, "Grossing-Up" Operating Expenses in Commercial Leases (JDSupra.com 2023).

4.18. Hollywood accounting (notes only)

Suppose that A and B agree that A will share in the profits from B's business — after B deducts its expenses. This type of "net profit" is common in movie- and TV-series production deals, where actors, producers, and others get (percentage) "points" that can add up to large sums over time. See generally Wikipedia, Hollywood Accounting.

Obviously, in this type of arrangement, B has an incentive to take as many deductions from gross revenue as it can, to try to reduce its payout to A.

An online commenter once opined that in Hollywood:

Net points: These are about as valuable, and confer as much status, as collecting beads for taking your top off at mardi gras. Everyone gets them and they're never worth anything. Along with whatever fee an actor — or a director, producer, writer — gets for a film, they may get some net points thrown in.

What it means is a percentage of the profits of a movie after it has recouped all its costs. Since even the mafia envies the ability of studios to cook their books, movies never go into profit. Ever. There are all sorts of charges — production costs, marketing costs, distribution fees, fuck-you-because-we-say-so write-offs — that can make the biggest hit look like a dog. Gabriel Snyder, How Movie Stars Get Paid (archive.org, from the now-defunct Gawker.com 2009; extra paragraphing added). The Snyder piece provides a readable overview of how movie deals supposedly work for actors financially — but the Webpage has some kind of Javascript blanker, so try disabling Javascript or, on some browsers, click on the "X" near the Refresh button to stop the script immediately after refreshing the page.

That can produce bizarre results, as illustrated in the following examples.

• Example: Return of the Jedi. In 2009, actor David Prowse, a.k.a. Darth Vader in the Star Wars films, said that Lucasfilms had notified him that Return of the Jedi had still not made a profit, some 26 years after its initial release and grossing nearly half a billion dollars on a $32 million budget. (And that was probably before the incessant replaying of the film on cable TV.) See Derek Thompson, How Hollywood Accounting Can Make a $450 Million Movie 'Unprofitable' (TheAtlantic.com 2009).

• Example: The Walking Dead. In 2021, AMC Networks agreed to pay The Walking Dead co-creator Frank Daramount and his agency $200 million to settle claims that they had been underpaid as a result of "sweetheart deals" between the network and its affiliates. See AMC Networks Form 8-K report (filed Jul. 16, 2021); Eriq Gardner What the $200M ‘Walking Dead’ Settlement Says About TV’s Future (HollywoodReporter.com 2021).

• Example: In 2020, the creators of cult-classic movie This is Spinal Tap settled their fraud lawsuit agains French media group Vivendi and its StudioCanal division over Hollywood accounting. See Will Lavin, ‘This Is Spinal Tap’ creators and StudioCanal settle rights dispute (NME.com 2020); see also Robert Kolker, This Lawsuit Goes to 11 (Bloomberg.com 2017).

For more examples, see Wikipedia, Hollywood Accounting.

4.19. Letters of credit (notes only)

Note: The following discussion is drawn, largely verbatim but with light format editing, from the Southern District of New York's 2021 opinion in TC Skyward Aviation v. Deutsche Bank; no copyright is claimed in the opinion's text.

A letter of credit is an irrevocable promise to pay the beneficiary when the latter presents certain documents that conform with the terms of the credit letter. Its purpose is to facilitate international trade by reducing the risk of nonpayment in cases where credit is extended by interposing a known and solvent institution's credit for that of an unknown and potentially insolvent institution.

One of the expected advantages and essential purposes of a letter of credit is that the beneficiary will be able to rely on assured, prompt payment from a solvent party; necessarily, a part of this expectation of ready payment is that there will be a minimum of litigation and judicial interference, and this is one of the reasons for the value of the letter of credit device in financial transactions.

Ordinarily there are three separate and distinct contracts involved in a letter of credit transaction:

1.  the contract of the bank with its customer whereby it agrees to issue the letter of credit;

2.  the letter of credit itself; and

3.  the contract of sale between the buyer (who is also the person who procured the bank to issue the letter of credit) and the seller (who accepts and acts under the letter of credit by drawing drafts thereunder).

Independence principle: A letter of credit is independent from the underlying transaction that gave rise to it. The issuing bank's payment obligation to the beneficiary is primary, direct and completely independent of any claims which may arise in the underlying sale of goods transaction.

It is the complete separation between the underlying commercial transaction and the letter of credit that gives the letter its utility in financing transactions. This independence principle is predicated upon the fundamental policy that a letter of credit would lose its commercial vitality if, before honoring drafts, the issuer could look beyond the terms of the credit to the underlying contractual controversy or performance between its customer and the beneficiary.

Strict enforcement principle: Additionally, letters of credit are strictly enforced pursuant to their terms. Where a beneficiary's draw request complies with the terms of the letter of credit, the issuer's duty to pay is absolute, regardless of whether the buyer-account party complains that the goods are nonconforming. This rule of strict compliance finds justification in the bank's role in the transaction being ministerial, and to require it to determine the substantiality of discrepancies would be inconsistent with its function.

Fraud – a limited exception: Fraud is the well-established exception to the rules of independence and strict compliance under letter of credit law. Dishonor due to fraud is proper:

  • where a draw has no basis in fact and represents a fraud in the transaction, or
  • where a drawdown would amount to an outright fraudulent practice by the beneficiary.

However, because the smooth operation of international commerce requires that requests for payment under letters of credit not be routinely obstructed by pre-payment litigation, the fraud exception to the independence principle is a narrow one.

Under the "fraud in the transaction" defense, dishonor of a facially-conforming draw request is permissible only where the beneficiary's claim is clearly untenable. Similarly, a drawdown amounts to "fraud in the transaction" where the beneficiary has no basis in fact and thus the drawer has no bona fide claim to payment at all. Dishonor is permissible due to fraud where the beneficiary attempts to draw on a standby letter of credit when there is no plausible or colorable basis under the contract.

Note

See TC Skyward Aviation U.S., Inc. v. Deutsche Bank AG, 557 F. Supp. 3d 477, 485 (S.D.N.Y. 2021) (denying defendant's motion for summary judgment and granting plaintiff's cross-motion for summary judgment) (citations omitted, formatting altered for readability). See generally also Standby Letter of Credit (Investopedia.com); compare with Sight Letter of Credit (same). Hat tip: @NY_Contracts . [a]  DCT comment: That's not to say that a debtor won't try to stop a drawdown, as a debtor tried (unsuccessfully) in a Canadian case discussed in Brian Reid and Geoffrey Stenge, How Liquid is Your Letter of Credit? (JDSupra.com 2024).

4.20. Liens (rough notes only)

A lien can be thought of as a type of security interest in property. See the (brief) notes on that subject at 4.21.

Some liens are imposed by statute if the lienholder follows specified procedures. Example: A Washington-state statute requires residential contractors to give specific notice to homeowners about lien possibilities: See Rev. Code Wash. § 18.27.114.

4.21. Security interests ("liens") in collateral (notes only)

For a party expecting to be paid, an advantage of taking a security interest in collateral is that, if an amount due remains unpaid, then the payee can force a sale of the collateral and keep as much of the proceeds as is needed to pay the amount due, with any remaining proceeds going to the party that owed the money. See generally Security interest and Foreclosure (Investopedia.com).

But: In many cases, a security interest in collateral must be properly established and "perfected" — the manner of perfection depends on the nature of the collateral; it generally involves filing a notice of some kind in public records, so as to put the public on notice of the payee's security interest.

This means that two disadvantages of a security interest are:

  • Parties don't always get around to doing and/or filing the paperwork to perfect a security interest; and
  • Foreclosing on collateral costs time and money — especially if the collateral owner tries to get a court to stop the process, as sometimes happens.

Bottom line: A security interest is likely not the preferred payment security of choice for suppliers or other payees.

4.22. True-ups (notes)

True-up is business jargon for reconciling or balancing; a true-up is generally the end goal of a (routine) audit if the audit reveals that a party overpaid or underpaid.

Here are a few examples where true-ups likely would be in order:

  • a retailer, operating in leased store space in a shopping mall, underpays "percentage rent" (see Wikipedia) to its landlord;
  • a customer overpays a service provider because of billing errors by the provider;
  • a patent licensee underpays required "running royalties" to the patent owner. See generally, e.g., Patent Licensing Royalty Rates: Everything You Need to Know (UpCounsel.com 2020).

4.23. Lighthouse Payment Protocol List [to come]

[DCT comment: This will be a list of no-brainer Lighthouse protocols, to make it easy for drafters to adopt those protocols wholesale.]

5. Information handling

5.1. Archive Copy Retention Protocol

5.1.1. Parties: Retainer; Owner

  1. This Protocol presupposes that under the Con­tract, a specified party (a "Retainer") must return, turn over, or destroy one or more of the following:
    1. materials — hard copy, electronic, and otherwise — that were provided by another party (referred to for convenience here as the "Owner" even if the Owner technically is not an "owner" of the materials); and/or
    2. materials derived from materials provided by the Owner.
  2. None of the Options below in this Protocol will apply unless the Con­tract clearly adopts the specific Option in question.

5.1.2. Number of archive copies

The Retainer may maintain one set of the materials (along with a commercially-reasonable number of backups) as archive copies, but the Retainer must do so as stated in this Protocol.

Note

The Retainer's right to maintain backups of archive copies could be especially important in the case of electronic archive copies, where backups commonly happen automatically.

5.1.3. Retention duration

The Retainer may maintain archive copies indefinitely, so long as the requirements of this Protocol continue to be met.

Note

It might be a bad idea to limit the retention period of archive copies. For example, in the case of electronic copies, it might be difficult and costly to locate and purge the copies — and their backups.

5.1.4. Location of copies

The Retainer may maintain the archive copies in one or more commercially-reasonable locations of the Retainer's choice, as long as those choices are consistent with this Protocol (including, if applicable, any specific limitations on such locations stated in the Con­tract).

5.1.5. Required security precautions

The Retainer is to take — at a minimum — prudent security measures to protect the archive copies.

Note

In some circumstances, the parties might want to be more specific in the Con­tract about minimum security measures.

5.1.6. Outside storage organizations

The Retainer is free to use one or more reputable storage organizations for custody of archive copies, but only under suitable written contracts that require the storage organization to comply with the Retainer's archive-copy obligations under the Con­tract.

Note

Alternative: To rule out the use of outside custodians, see Option 5.1.16 — but from the perspective of expertise and cost, an outside storage organization might be a better choice than the Retainer's keeping the archive copies itself.

5.1.7. Owner input about security

  1. IF: The Owner asks from time to time; THEN: The Retainer must consult with the Owner about the Retainer's archive-copy security measures.
  2. Subdivision 1 does not require the Owner to change those measures unless the measures did not comply with the requirements of the Con­tract.)
Note

Consultation: See 8.27.

5.1.8. Off-limits Retainer actions

Unless the Owner agrees otherwise in writing (in the Con­tract or elsewhere), the Retainer must not do any of the following things in respect of the archive copies and any Owner confidential information contained in them:

  1. allow anyone to access to the archive copies;
  2. disclose the information to anyone;
  3. use the information;
  4. allow anyone, or knowingly assist anyone, to engage in any unauthorized disclosure, use, or access of the information; nor
  5. confirm to anyone whether or not particular information is contained in the archive copies;
Note

These restrictions are also typical for confidentiality agreements, a.k.a. "NDAs," as discussed at § 5.3.20 of Protocol 5.3.

5.1.9. Special case: Independent possession

The Retainer may disclose or use information in archive copies — but must not confirm the content of the copies — if the Retainer can clearly show that the Retainer independently possesses the information as provided at § 5.3.8 of Protocol 5.3 (Confidential Information).

Note

().  This section is worded so as not to authorize the Retainer to confirm to others that the archive copies contain the information in question.

"Clearly show": See 20.11 and 5.3.36.7.

5.1.10. Authorized disclosures

Unless clearly agreed otherwise, the Retainer may disclose information in archive copies (subject to any restrictions in applicable law) only as follows:

  1. to the Retainer's people, and personnel of an outside archive custodian under this Protocol (if any), as needed to maintain the archive copies;
  2. to the limited extent clearly authorized by law, for example by the (U.S.) Defend Trade Secrets Act;
  3. in response to a subpoena, search warrant, etc. — but only in accordance with § 5.3.22 of Protocol 5.3 (confidential information) and/or
  4. to the extent (if any) that the Owner so agrees in writing.

5.1.11. Authorized access

Unless clearly agreed otherwise, the Retainer may allow access to the archive copies from time to time only in one or more of the following ways:

  1. by the Retainer's people who maintain the archive copies (if the Retainer is maintaining the copies);
  2. as agreed in writing by the Owner — including, but not limited to, for uses authorized by the Con­tract; and/or
  3. in connection with a disclosure permitted under the Con­tract.

5.1.12. Authorized use

Unless clearly agreed otherwise, the Retainer may use information contained in the archive copies only for one or more of the following purposes:

  1. determining the Retainer's continuing rights and/or obligations under the Con­tract;
  2. causing and monitoring the parties' compliance with their respective obligations;
  3. documenting the parties' past- and present interactions relating to the Con­tract;
  4. reasonable testing of the accuracy of the archive copies; and/or
  5. as otherwise agreed in writing by the Owner.

5.1.13. Option: Use for Retainer's Business Purposes

  1. If this Option is clearly agreed to, then the Retainer may access and use archive copies as the Retainer sees fit in the Retainer's sole and unfettered discretion — but solely for the Retainer's internal business purposes — as long as the Retainer otherwise restricts use as stated in the Con­tract.
  2. The Owner and Retainer will escalate, as provided at Protocol 21.11, any dispute about what constitutes "internal business purposes" under subdivision 1.
Note

Caution: What constitutes "internal business purposes" could be open to dispute.

5.1.14. Option: "Have-Used" Rights

If this Option is clearly agreed to, THEN: The Retainer may allow one or more third parties to use information in archive copies in the same way(s) as the Retainer, but only:

  • solely for the Retainer's benefit,
  • under a written agreement restricting use and disclosure,

except as allowed by the Con­tract.

Note

Incidental third-party benefit would be permissible, for example if the Retainer paid the third party for services permitted under this Protocol. Concerning "have-used" rights, see 31.18.

5.1.15. Option: Access List for Archive Copies

If this Option is clearly agreed to, THEN: If the Owner reasonably asks from time to time, the Retainer is to provide the Owner with a complete and accurate list of all persons who have had access to archive copies that are maintained by‑ or for the Retainer.

Note

Caution: The Retainer might well object to providing a list of people who had access to archive copies, on grounds that: (1) it could be burdensome, and (2) it might tempt the Owner to put its nose too far into the Retainer's business.

5.1.16. Option: No Outside Custodians

If this Option is clearly agreed to, THEN: The Retainer itself is to maintain all archive copies (i.e., with the Retainer's own employees).

Note

().  This Option would override § 5.1.6 above.

Caution: It could be suboptimal, for both the Retainer and the Owner, to require the Retainer to maintain archive copies itself. That's because:

  • The Retainer might not have the same kind of professional-grade security infrastructure and -protocols as would an appropriate outside custodian, and
  • As a result, that might be more costly for the Retainer than simply engaging an outside custodian.

5.1.17. Option: Only Outside Custodians

  1. If this Option is clearly agreed to, THEN: The Retainer must use an outside archive custodian — approved in advance by the Owner — for all archive copies.
  2. If the Retainer asks for such approval, THEN:

The Owner must not unreasonably withhold, condition, or delay such approval.

The Owner may grant or withhold approval in the Owner's sole discretion.

Note

().  Caution: Outside custodians for archive copies would be an extra expense — but that might well be more cost-effective than the Retainer's trying to maintain the archive copies itself.

Consent: See 12.2.

Subdivision 2 — discretion generally: See 9.6.

5.1.18. Additional notes

5.1.18.1. The business context

().  In some contracts, one party will provide proprietary information to another party, but will expect the information to be returned or destroyed later. An archive-copies clause will often be used there — for example, in the information-purge provisions at Protocol 5.4 — which in turn are likely to be used in conjunction with confidentiality obligations such as Protocol 5.3. (Some of the provisions of this Protocol are adapted from their counterparts in Protocol 5.3.)

5.1.18.2. Examples of archive-copy materials retained

Here are few possible examples of materials for which a Retainer might retain archive copies:

  1. electronic documents;
  2. "hard copies";
  3. photographs and video / audio-visual recordings, including, for example, those made to document events and/or tangible objects.

5.2. Business Associate Agreement Protocol

In certain circumstances in the United States, service providers and others that deal with "protected health information" ("PHI") on behalf of a "covered entity" (e.g., health-care providers) must sign a so-called business associate agreement ("BAA") to protect the PHI. This is required by rules promulgated under two federal statutes, the Health Insurance Portability and Accountability Act ("HIPAA") and the HITECH Act (Wikipedia.org).

Contents:

5.2.1. Applicability & parties

When this Protocol is adopted, it signifies that one party to the Con­tract (the "Business Associate") is a "business associate" of another party to the Con­tract (the "Covered Entity"), as the quoted term is defined in 45 C.F.R § 160.103.

Note

Not every recipient of protected health information ("PHI") will be a "business associate" — which means that a business-associate agreement won't be required for every disclosure of protected health information. See 78 Fed. Reg. 5566, 5574 (Jan. 25, 2013), excerpted at the footnote.13

5.2.2. Adoption of HHS Model BAA (as modified)

All parties are to comply with the Model Business Associate Agreement published by the U.S. Department of Health and Human Services (archived at https://perma.cc/57BP-KAPJ) (the "HHS Model BAA"), as modified by this Protocol.

Note

Instead of reinventing the wheel, this Protocol simply adopts the HHS Model BAA (archived at https://perma.cc/57BP-KAPJ), with a few tweaks. That should help the parties speed up their legal review and get to signature sooner. The HHS Model BAA seems to cover the same bases as in the Sample Business Associates Agreement Provisions published by HHS on January 25, 2013 ("HHS Sample BAA Provisions"). See http://goo.gl/0OYWs, which is a shortened link for a page at www.hhs.gov.

5.2.3. Effectiveness of notices

All parties are to treat any notice given under the HHS Model BAA as being effective only upon receipt, refusal, or after reasonable but unsuccessful attempts at delivery, as shown by independent written evidence (e.g., a human email response or a delivery service's confirmation).

Note

This "Three Rs" approach is borrowed from Protocol 3.14, because the HHS Model BAA's notices provision (section 18) is somewhat open-ended.

5.2.4. Use of "de-identified" PHI

  1. Unless clearly agreed otherwise, the Con­tract does not prohibit the Business Associate using and/or disclosing "de-identified" (a.k.a. "anonymized") protected health information ("PHI") that the Business Associate obtains and/or creates under the Con­tract.
  2. For this purpose "de-identified information" means information that cannot practicably be used to identify any individual nor obtain any individual's health information.
Note

().  So-called "de-identified" protected health information can be commercially valuable — but its use might be subject to legal restrictions.

Seeing a need, some vendors have produced specialized "clean room" software that anonymizes consumer data. See generally, e.g., this HHS guidance on de-identifying PHI; Patience Haggin, Advertisers Turn to ‘Clean Rooms’ to Keep Consumer Data Private (WSJ.com).

Caution: De-identified protected health information isn't the same as aggregated PHI, which this Protocol doesn't address. Under HHS regulations, a business associate may use aggregated PHI only in limited circumstances. The HHS definition of data aggregation provides as follows:

Data aggregation means, with respect to protected health information created or received by a business associate in its capacity as the business associate of a covered entity[:] the combining of such protected health information by the business associate with the protected health information received by the business associate in its capacity as a business associate of another covered entity, to permit data analyses that relate to the health care operations of the respective covered entities. 45 C.F.R. § 164.501 (emphasis and bullets added).

As pointed out by a healthcare lawyer: "Per the regulations and commentary, the 'data aggregation' exception would not apply unless (1) the data aggregation is for the covered entity’s healthcare operations, not the business associate’s own purposes; and (2) the BAA expressly authorizes the business associate to perform the data aggregation services." Kim Stanger, Business Associates' Use of Information for Their Own Purposes (HollandHart.com 2019) (emphasis added).

5.2.5. Electronic PHI

The Business Associate is to comply with regulatory requirements for electronic PHI as part of its compliance with the business-associate agreement.

Note

For those requirements, see Subpart C of 45 CFR Part 164.

5.2.6. Flowdowns of other automatic PHI obligations

The Business Associate is to comply with applicable flowdown requirements (if any).

Note

Under 45 CFR § 164.528, a covered entity must account to individuals for PHI disclosures; if you're a business associate, those obligations are largely "flowed down" to you. (For more on flowdown requirements, see 3.6.3.)

Moreover, if you're a business associate:

  • you also must comply with certain requirements of Subpart E of 45 CFR Part 164 that apply to the covered entity — see generally the table of contents of Subpart E as listed at the Cornell Legal Information Institute Website.
  • you're required to ensure — in accordance with 45 CFR §§ 164.502(e)(1)(ii) and 164.308(b)(2), as applicable — that any subcontractors that create, receive, maintain, or transmit protected health information on your behalf have agreed to the same restrictions, conditions, and requirements that apply to you with respect to such information;
  • under 45 CFR § 164.410, if you become aware of uses or disclosures of PHI that aren't provided for by the parties' contract, then you're required to report it to the covered entity. This includes, for example:
    • breaches of unsecured PHI;
    • any security incident of which you become aware;
    • any demand by a governmental entity for disclosure of PHI.

(See also § 5.3.22 in Protocol 5.3, which addresses how subpoenas, etc., for confidential information are to be handled.)

5.2.7. Duration of PHI obligations

If the business-associate relationship or ‑agreement ends (whether by expiring or by being terminated), that in itself will not end the Business Associate's obligations under the agreement to safeguard PHI that was:

  • received from the covered entity, or
  • created, maintained, or received by the business associate on behalf of the covered entity.

5.2.8. Additional notes

5.2.8.1. You might have to return or destroy PHI

Locating, extracting, and returning PHI could be a major, costly burden and so should be planned for accordingly.

5.2.8.2. Caution: A HIPAA violation could lead to federal monitoring

If you're a business associate and you suffer a data breach ("get hacked"), you could find yourself in the cross-hairs of the federal government.

Example: In 2023, the Department of Health and Human Services ("HHS") announced a settlement with MedEvolve, Inc., a business associate that provides software services to covered health care entities, after a MedEvolve server was found to have exposed protected health information of more than 230,00 individuals on the internet. According to the HHS press release:

The potential HIPAA violations in this case include[:]

  • the lack of an analysis to determine risks and vulnerabilities to electronic protected health information across the organization, and
  • the failure to enter into a business associate agreement with a subcontractor.

MedEvolve paid HHS $350,000 and agreed to implement a corrective action plan — and it also agreed to being monitored by HHS for two years and to provide annual- and incident-based reports. U.S. Department of Health and Human Services, Press Release, HHS Office for Civil Rights Settles HIPAA Investigation with Arkansas Business Associate MedEvolve Following Unlawful Disclosure of Protected Health Information on an Unsecured Server for $350,000 (HHS.gov 2023).

5.2.8.3. Caution: You could be inspected for compliance

When you're a business associate, you're required to make your internal practices and its books records available for compliance inspections by the Secretary of the U.S. Department of Health and Human Services.

(You could try negotiating to conduct the inspection in accordance with Protocol 9.8, inspections, and Protocol 4.3, audits.)

5.2.8.4. Appendix: Links to further reading

The U.S. Department of Health and Human Services maintains: • a frequently-asked questions site (FAQ); • an unofficial compilation of "all the HIPAA regulatory standards in one document" • a "HIPAA for Professionals" page of links.

The U.S. Center for Medicare and Medicaid Services has a booklet, HIPAA Basics for Providers: Privacy, Security, & Breach Notification Rules.

Healthcare attorney Kim Stanger has a 2023 piece, Business Associate Agreements: Requirements and Suggestions

Apple's iCloud terms of service, at https://www.apple.com/legal/internet-services/icloud/ (accessed Oct. 31, 2025), provide as follows at section I.C:

If you are a covered entity, business associate or representative of a covered entity or business associate (as those terms are defined at 45 C.F.R § 160.103), You agree that you will not use any component, function or other facility of iCloud to create, receive, maintain or transmit any “protected health information” (as such term is defined at 45 C.F.R § 160.103) or use iCloud in any manner that would make Apple (or any Apple Subsidiary) your or any third party’s business associate.

5.2.8.5. Appendix: Selected definions in federal regulations

For convenience, here are links to some key definitions: • Breach; • "business associate" at 45 CFR § 160.103; • "covered entity" at 45 CFR § 160.103; • Data aggregation; • Designated record set; • Disclosure; • Health care operations; •  "HIPAA Rules" refers to the Privacy, Security, Breach Notification, and Enforcement Rules at 45 CFR Part 160 and Part 164.; • Individual; • Minimum necessary (also here); • Notice of privacy practices; • Protected health information; • Required by law; • Security incident; • Subcontractor; • Unsecured protected health information; • Use

5.3. Confidential Information Protocol

They're everywhere — and they help build deals: Surely the most-common type of contract has to be the confidentiality agreement — commonly referred to (imprecisely) as an "NDA," for "nondisclosure agreement," although NDAs pretty-much always contain more obligations than nondisclosure. As we'll see in the notes below, confidentiality agreements are enforceable at common law and/or by statute in the U.S. and many other countries.

Students: Be sure to read the background reading at 5.3.34 (for both Disclosers and Recipients), 5.3.35 (for Disclosers), and 5.3.36 (for Recipients).

Contents:

5.3.1. Definitions: Discloser; Recipient

A to the Con­tract will have the obligations of a "Recipient" of Confidential Information of B to the Con­tract, referred to as a "Discloser," but only if:

  1. the Con­tract clearly says so, or
  2. the circumstances unmistakably indicate that B agreed to comply with this Protocol concerning A's Confidential Information — in which case B will be the Recipient.
Note

().  Intent: This is intended to avoid possibly-severe future problems for the Recipient if: (1) the parties initially agree that only the other party's information will be protected; but (2) the parties later decide to switch roles but don't realize that their NDA doesn't cover that situation.

A genuine two-way agreement is always best: Under the definition in this § 5.3.1, this Protocol would be usable both in a one-way agreement (where only one party wants to be bound by confidentiality obligations) and in a two-way agreement. (Concerning two-way agreements, see the additional discussion at 5.3.34.3 and, more generally at 2.1.)

This reverses an oft-used approach to NDA drafting: We don't "lock in" the definitions of Discloser and then Recipient; instead, we define Recipient as any party that has agreed — in the Con­tract itself, or otherwise — to treat particular information in confidence, to guard against inadvertent disasters later, as discussed at 5.3.34.3.

Caution: Both the Recipient and the Discloser might be subject to other confidentiality obligations, possibly by operation of law — see, e.g.:

  • Business associate agreements (5.2): confidential obligations are required by law in certain cases involving protected health information;
  • Export controls (31.9): the law restricts disclosure of certain categories of information, with possible criminal penalties for violation;
  • Privacy laws (5.6).

    Subdivision 1: Under this Protocol, both the Discloser and the Recipient must be parties to the Con­tract, because:

  • it wouldn't be a great idea for a Discloser to assert, out of the blue, that some unsuspecting third party was supposedly bound by confidentiality obligations; and
  • neither would it be good for an outsider to assert that it qualified as a Discloser and therefore the parties to the Con­tract had misappropriated the outsider's confidential information.

    Subdivision 1: We say nothing here about the Discloser's owning Confidential Information — in that regard, we follow the (federal) Defend Trade Secrets Act, in which, an owner (of a trade secret) is defined as "the person or entity in whom or in which rightful legal or equitable title to, or license in, the trade secret is reposed …." 18 U.S.C. § 1839(4) (emphasis added); see, e.g., Advanced Fluid Systems, Inc. v. Huber, 958 F.3d 168, 177 (3d Cir. 2020) (affirming judgment of trade-secret misappropriation).

State-law adoptions of the Uniform Trade Secrets Act, however, generally refer to a "possessor" of information, not an "owner." See Snyder v. Beam Technologies, Inc., 147 F.4th 1246, 1255-55 (citing cases).

5.3.2. Protection prerequisites

Unless otherwise required by law (for example, for protected health information), the Recipient's obligations under this Protocol will apply only to information ("Confidential Information" or sometimes "Discloser Confidential Information") for which the Discloser took — and continues to take — reasonable measures to keep the information confidential.

Note

().  Language choice: This section draws on the (U.S.) Defend Trade Secrets Act (DTSA), 18 U.S.C. § 1839(3), which was modeled in part on the state-law Uniform Trade Secrets Act (UTSA), which has been adopted in nearly all U.S. states. See generally, e.g., BakerHostetler, Comparing the Defend Trade Secrets Act and the Uniform Trade Secrets Act (JDSupra.com 2016).

Under the law in most jurisdictions, the Discloser (usually) must take reasonable precautions to protect its confidential information — otherwise the information won't be eligible for trade-secret protection in the first place, as discussed in the note to § 5.3.11.

Here are some commonly-used security measures for confidential information: These examples are drawn in part from on Amy E. Bergeron, For Good Reason: “Reasonable Measures” in Recent Trade Secret Law (BakerBotts.com 2021).

  • Keep hard copies in locked offices and/or in locked file cabinets.
  • Require passwords (and, increasingly, two-factor authentication or passkeys) to access computer networks.
  • Use role-based permissions on computer networks; for example, marketing people might not need to see — and so perhaps shouldn't have access to — technical information, and vice versa.
  • Be careful about the increasingly-popular practice of "BYOD" (Bring Your Own Device), especially if it will be difficult to get an employee to delete confidential information from a personal phone or computer when leaving the company. Example: The Eleventh Circuit affirmed a ruling that a company had destroyed its rights in certain trade secrets when it adopted a loose BYOD policy with its employees. See Yellowfin Yachts, Inc. v. Barker Boatworks LLC, 893 F.3d 1279, 1299, 1300-01 (11th Cir. 2018) (affirming summary judgment).
  • When an employee quits or is fired or laid off: Quickly cut off the employee's access to computers and networks, and direct the employee to delete confidential informtion from personal devices. Example: Google executive Anthony Levandowski left the company to found a self-driving truck startup company, Otto (later acquired by Uber). On his way out the door, Levandowski "downloaded thousands of [trade-secret Google] files onto his personal laptop. He also admitted downloading a variety of files from a corporate Google Drive repository." (DOJ press release.) Levandowski pleaded guilty to trade-secret theft and was sentenced to 18 months in prison (but was pardoned by President Trump on the morning of the day Trump left office in his first term). In addition to the criminal charges against Levandowski, Google sued both him and Uber in civil court; the parties eventually settled the case.
  • Consider using security cameras in appropriate places.

    Note: Fort-Knox security measures usually aren't necessary. Example: The Tenth Circuit once remarked that "there always are more security precautions that can be taken. Just because there is something else that Luzenac could have done does not mean that their efforts were unreasonable under the circumstances. … Whether these [specific] precautions were, in fact, reasonable, will have to be decided by a jury." Hertz v. Luzenac Group, 576 F.3d 1103, 1113 (10th Cir. 2009) (cleaned up; citations omitted).

Example: In one case, the defendants, Meta and Princeton University, moved for summary judgment that the plaintiff's exposure on its Web site of the alleged trade secrets was enough to defeat any claim for trade-secret misappropriation. The court, though, held that the robotic "scraping" of the plaintiff's Web site — initiated by Princeton University researchers in violation of the Web site's terms of service — was a factor in denying summary judgment about whether the plaintiff had taken sufficient protective measures, and so a full-blown trial would be needed to determine that issue. See UAB "Planner5D" v. Meta, No. 3-19-cv-03132, 2021 WL 1405482 (N.D. Cal. 2023), part II.D.3; see also the court's 2019 factual summary; the case was settled in 2025.

A confidentiality legend, by itself, might not suffice as reasonable secrecy measures. Example: A federal court in San Antonio held that "the only reasonable measure plaintiffs allegedly took to keep the information secret was a confidentiality statement at the bottom of an email. A boilerplate confidentiality statement does not constitute a reasonable measure to keep secrecy—especially when [the plaintiff] used the phrase "may contain information that is confidential." Academy of Allergy & Asthma in Primary Care v. Quest Diagnostics, Inc., No. 5:17-cv-1295-RCL, slip op. at part III.D (W.D. Tex. Mar. 31, 2022) (granting Quest's motion to dismiss trade-secret claim for failure to state a claim upon which relief can be granted), on remand from 998 F. 3d 190, 199 (5th Cir. 2021) (reversing district court's dismissal, on limitation grounds, of trade-secret claims; cleaned up, case citations omitted).

Importantly: Whether a company took reasonable measures to protect its confidential information will often be a jury issue. As a result, if there's enough evidence of such measures to allow a jury to conclude that the measures were indeed reasonable, then (in American practice) neither the trial judge nor the appellate court will disturb the jury's conclusion, even if a different conclusion might also have been reasonable. See, e.g., Trinseo v. Harper, No. 24-20460, part II.B.1.a, slip op. at 19-21 (5th Cir. Jan. 21, 2026) (affirming trial court's denial of co-defendant KBR's motion for judgment as a matter of law after jury verdict of misappropriation of trade secrets).

5.3.3. Protected Disclosure Window

The Recipient need not treat otherwise-eligible Discloser information as Confidential Information unless the Discloser, directly or indirectly, first made the information accessible to the Recipient during the two years after effective date (the "Protected Disclosure Window").

Note

This will provide the Recipient with some reasonably-visible "channel markers" showing which Discloser information is protected under this Protocol.

5.3.4. Unrelated information not covered

For otherwise-eligible information to qualify as Confidential Information, the Discloser must initially make the information available to the Recipient (directly or indirectly) in connection with the Con­tract — as opposed to in connection with other business dealings.

Note

This carve-out could lead to disputes if the Discloser and Recipient have multiple dealings. But it seems worth the risk to avoid having the Recipient ambushed, long after the parties have wrapped up their dealings under the Con­tract, by sudden claims that other Discloser information was subject to confidentiality obligations.

5.3.5. Expiration date (with trade-secret exception)

  1. Except as stated below, the Recipient's obligations of secrecy precautions, non-use, and non-disclosure (see §§ 5.3.19 through 5.3.21) will expire at the end of the day local time on the date three years after the effective date of the Con­tract.
  2. By complying with subdivision 3 below, the Discloser may exclude information in the following categories from expiration under § 5.3.5 above:
    1. The information must qualify as a "trade secret," as defined in the U.S. Defend Trade Secrets Act ("DTSA"), not merely as confidential; and/or
    2. The information must be the confidential information of a third party, where the Discloser is bound (by agreement or by law) by legally-enforceable confidentiality obligations.
  3. To exclude confidential information from expiration, the Discloser must:
    1. at any time before expiration: provide the Recipient with a writing that, with reasonable prominence and particularity, designates the information as being excluded from expiration; and
    2. respond — accurately and with reasonable particularity — to any reasonable Recipient questions about the designation.
  4. IF: The Discloser's written designation under subdivision 3 above takes place after the information in question has been initially made accessible to the Recipient: THEN: That designation must take the form of notice under Protocol 3.14.
Note

().  Background: A Discloser likely won't want the Recipient's confidentiality obligations to expire for economically-valuable confidential information, because that would almost surely destroy the Discloser's legal rights in the information (see the note below). This exclusion from expiration is a "sunset" provision that tries to compromise between the parties' interests, as discussed in the note below.

Subdivision 3.b: A designation by the Discloser could happen during initial disclosure, for example by labeling a written copy of the information as a trade secret.

Subdivision 4's notice requirement is meant to increase the chances that the Recipient will actually become aware of a catch-up designation of non-expiration.

Shouldn't even trade-secret confidentiality obligations expire? The Discloser is likely to balk at across-the-board expiration of the Recipient's confidentiality obligations. That's because such broad expiration would likely destroy the Discloser's legal rights in any trade secrets that the Discloser had provided under the NDA, i.e., information that gave the Discloser an economic advantage from its secrecy. That could be a serious concern.

Example: In a case peripherally involving Facebook, the Ninth Circuit reversed a trial-court's judgment awarding $30 million for breach of an NDA because the NDA's confidentiality obligations had unambiguously ended two years after NDA was signed due to a "sunset" provision in the NDA itself. See BladeRoom Grp. Ltd. v. Emerson Elec. Co., 20 F.4th 1231 (9th Cir. 2021).

Other cases are to like effect. Example: In a Commerzbank AG case, the SDNY noted that: "Once a third party's confidentiality obligation … expires, so does the trade secret protection." Structured Capital Solutions v. Commerzbank AG, 177 F. Supp. 3d 816, 835-36 (S.D.N.Y. 2016) (Rakoff, J., granting summary judgment for Commerzbank on plaintiff's trade-secret claim; citing cases) (emphasis added). See also, e.g., Analog Technologies, Inc. v. Analog Devices, Inc., 105 F.4th 13 (1st Cir. 2024) (granting motion to dismiss); DB Riley, Inc. v. AB Eng'g Corp., 977 F. Supp. 84, 91 (D. Mass. 1997) (denying preliminary injunction against alleged trade-secret misappropriation).

And of course, for both trade secrets and other Confidential Information, the Recipient's obligations would automatically end if, at any time, the information in question were to come with one of the Confidential Information exclusion categories starting at § 5.3.

Caution: Even after expiration of confidentiality obligations under the Con­tract, other law concerning, e.g., privacy or export controls might still restrict the Recipient's use- and/or disclosure of information.

Why not just say that all information is a trade secret? A Discloser might assert that all confidential information that the Discloser makes available to a Recipient should be presumed to be a trade secret. The Fourth Circuit rejected a manufacturer's urging that all confidential information that the manufacturer had disclosed to a distributor should be presumed to be a trade secret; the court cited the business- and economic mischief that could result from opportunistic claims of misappropriation. Sysco Machinery Corp. v. DCS USA Corp., 143 F.4th 222, 230-31 (4th Cir. 2025) (affirming dismissal of trade-secret claim for failure to state a claim upon which relief can be granted)

A compromise: In this Protocol, § 5.3.5 provides a "sunset" as a compromise that attempts to balance the parties' competing interests:

  • A Recipient, for its own business efficiency, will likely want to have its confidentiality obligations expire on an easily-determinable date. That way, after that "sunset" date, the Recipient won't have to worry about whether particular "ordinary" confidential information is still subject to such obligations, because it won't have to think about the question.
  • For trade secrets, § 5.3.5 gives the Discloser a reasonable opportunity to exclude valuable information from the expiration of the Recipient's confidentiality obligations. That section's written-designation requirement is based on court holdings that someone claiming trade-secret rights must specify just what information supposedly constitutes a trade secret.14

    When should confidentiality obligations expire? For non-trade-secret information, confidentiality obligations could expire, for example:

  • on the date X years after all copies of the information have been returned or destroyed; or
  • on the date X years after the effective date of termination or expiration of the Con­tract — this latter alternative can be problematic, however, because the Con­tract per se might not have an expiration date, and the parties might forget to terminate it.

    Why not just have all confidentiality obligations be perpetual? Caution: The law might invalidate perpetual confidentiality obligations — at least for non-trade-secret confidential information. See Meta Platforms, Inc. v. Bright Data Ltd., No. 23-cv-00077-EMC, slip op. (N.D. Cal. Jan. 23, 2024) (citing cases).

On the other hand: The Eighth Circuit affirmed a holding that defendants had breached a seemingly-perpetual contractual confidentiality obligation that read, "I shall never, either during my employment with the Company or thereafter, directly or indirectly use . . . confidential information acquired in the course of my employment activities." Crabar/GBF, Inc. v. Wright, No. 23-3335, slip op. at 8 (8th Cir. Jun. 24, 2025) (emphasis and ellipsis by the court).

5.3.6. Third-party information

  1. This § 5.3.6 will apply if the Discloser makes information of one or more third parties available to the Recipient.
  2. The Recipient will treat that third-party information as Confidential Information to the same extent — but subject to the same exclusions — as if the information were that of the Discloser.
  3. BUT IF: Any other party asserts that the Discloser breached a contract or broke the law in providing that third party's information to the Recipient; THEN: The Discloser will defend and indemnify the Recipient and the Recipient's Protected Group against any claim arising out of that assertion.
Note

().  Background: Protection of third-party confidential information in this manner is a not-uncommon feature of confidentiality agreements.

Subdivision 3: Here the term "any other party" isn't intended to be limited to the third party whose information was provided — the term encompasses, for example, a government authority in a case where the Discloser provided a third party's protected health information to the Recipient.

5.3.7. Confidentiality of parties' dealings

  1. The (non-public) fact, status, and financial terms of the parties' dealings together are the Confidential Information of each of them — even if only one party is designated in the Con­tract as the Discloser.
  2. *Unless clearly agreed otherwise or explicitly required or permitted by law: As an exception to subdivision 1, each party is free to disclose to others no more than the fact that the parties have entered into an unspecified agreement that includes confidentiality provisions — each such disclosure:
    1. must be for good reason; and
    2. must be on a one-by-one basis and not in a general- or public announcement.
Note

().  Background: For various business reasons, parties often want the mere fact that they are in discussions to remain confidential, let alone the details of their dealings. Their motives might include, for example: • wanting to keep pricing information secret from competitors; or • not wanting to trigger a bidding war in a prospective merger- or acquisition transaction. (Public information about the parties' dealings would of course not be Confidential Information.)

().  Wording can matter here: Caution: Drafters should carefully consider the wording of a confidentiality-of-dealings clause. Incautious wording could fail to protect what a party is really concerned about.

Example: Something like that seems to have happened in a Texas case: A woman agreed to settle a wrongful-death claim against a doctor who had treated the woman's daughter. The settlement agreement barred the woman from talking about the settlement, but it didn't restrict her discussion of the doctor's alleged malpractice. See Joselevitz v. Roane, No. 14-18-00172-CV, slip op. at n.3. (Tex. App.–Houston [14th Dist.] Mar. 31, 2020) (affirming take-nothing summary judgment dismissing doctor's breach-of-contract and defamation claims against woman) (mem. op.)

A secrecy-of-dealings clause would likely be enforced: Clauses requiring parties' contract terms to be kept confidential have been enforced. Example: The Delaware chancery court held that a party had materially breached an agreement by publicly disclosing the agreement's terms in violation of a confidentiality clause — thereby justifying the other party's termination of the agreement. See eCommerce Indus., Inc. v. MWA Intelligence, Inc., No. 7471-VCP, part II-A, text acc. notes 117 et seq. (Del. Ch. Oct. 4, 2013).

Counterexample: On the other hand, a party's breach of a confidentiality-of-dealings clause might not be considered "material." For example, Delaware's supreme court held that in a patent license agreement, a provision requiring the terms of the license to be kept confidential was not material, because the gravamen of the contract was the patent license, not the confidentiality provision; as a result, when the licensee publicly disclosed the royalty terms, the patent owner was not entitled to terminate the license agreement for material breach. See Qualcomm Inc. v. Texas Instr. Inc., 875 A.2d 626, 628 (Del. 2005) (affirming holding of chancery court).

Similarly, Amazon was found liable for breaching a letter of intent to negotiate a lease of a commercial building in Manhattan. On summary judgment, the court noted: "Paragraph 27 prohibited Amazon from disclosing the LOI and the parties' negotiations to third-parties" (text accompanying n.1) but that "[t]hough the confidentially provision was also breached, it did not result in additional out-of-pocket damages, making the breach academic." DOLP 1133 Properties II LLC v. Amazon Corporate, LLC, 2020 N.Y. Slip Op. 30274(U), No. 653789/2014, slip op. at n.4 (N.Y. Sup. Ct. Jan. 6, 2020) (partly granting Avenue building owner's motion for summary judgment).

Secrecy of dealings: Could government authorities object? Government authorities might object to confidentiality-of-dealings clauses, for example in employment-agreement forms that call for the employee to keep confidential all information about salary, bonus, and other compensation; see 5.3.35.3 for a detailed discussion.

5.3.8. Exclusion of information acquired in other ways

  1. Excluded: Information independently possessed: Confidential Information does not include information that falls into one or more of the following categories (but see subdivision 2 below concerning proof requirements):
    1. a third party provided the Recipient with the information — at any time — without violating an obligation of confidence that benefited the Discloser; or
    2. the Recipient possessed the information before the Discloser made the information available to the Recipient; or
    3. the Recipient independently developed the information — at any time — without referring to or otherwise using Confidential Information.
  2. Corroboration requirement: If the Recipient offers testimony of one or more of the Recipient's own people (or of one or more other "interested witnesses") to try to show that information comes within one or more of the categories of subdivision 1, THEN: That testimony will be entitled to no weight — and the Recipient is not to assert otherwise — unless the Recipient also provides reasonable corroborating evidence to support the testimony.
Note

Juries can be skeptical of self-serving claims of independent possession. So Recipients should watch for (and save) corroborating evidence in that vein; see 5.3.36.7.

Note

"Use of … independently possessed information is no more a misappropriation than is use of one's independent invention, against which trade secret law does not offer protection." Texas Advanced Optoelectronic Solutions, Inc. v. Renesas Electronics America, Inc., 895 F.3d 1304, 1313 (Fed. Cir. 2018) (reversing, in part, judgment on jury verdict of trade-secret misappropriation) (cleaned up, citation omitted).

5.3.9. Exclusion of public information

At any given time, Confidential Information does not include information that has been been published (including for example by patenting) or otherwise made publicly available, by anyone (other than the Recipient, in violation of the Con­tract).

Note

().  Under the law, this is pretty much a given — see 5.3.36.3.

Caution: Don't say "public domain": When listing exclusions from confidential-information status, you don't want to refer to information that's "in the public domain." That's because particular information might not be confidential, but it might still not be "public domain" due to:

  1. restrictions on use of the information, for example under patent law, pharmaceutical regulations, etc.; and/or
  2.  restrictions on disclosure of the information, for example, under:
    • copyright law's restrictions on making and/or distributing copies of eligible "works of authorship";
    • privacy law; and/or
    • export-controls law, which prohibits disclosure of certain "technical data" (defined broadly) to non-U.S. persons.

5.3.10. Exclusion of readily-ascertainable information

The term Confidential Information does not include information that, at the relevant time, is or was:

  1. generally known, or
  2. readily ascertainable without the use of improper means,

in either case by people within the circles that normally deal with the kind of information in question.

Note

().  The language of this exclusion is adapted from the definition of trade secret in the Defend Trade Secrets Act ("DTSA"), at 18 U.S.C. § 1839(3); see 5.3.36.5.

The phrase "people within the circles …" is adapted from the UK's 2018 draft regulations implementing the EU Trade Secrets Directive (2016/943) at 19, archived at https://perma.cc/PHT8-DQFJ.

Importantly: Whether an alleged trade secret was "readily ascertainable" will often be a jury issue. As a result, if there's enough evidence of such measures to allow a jury to conclude that the answer is "no," then (in American practice) neither the trial judge nor the appellate court will disturb the jury's conclusion, even if a different conclusion might also have been reasonable. See, e.g., Trinseo v. Harper, No. 24-20460, part II.B.1.b, slip op. at 21-22, text acc. n.12 (5th Cir. Jan. 21, 2026) (affirming trial court's denial of co-defendant KBR's motion for judgment as a matter of law after jury verdict of misappropriation of trade secrets).

5.3.11. Exclusion of information freely provided to others

At any given time, Confidential Information does not include information that the Discloser has made available to one or more others without confidentiality obligations comparable to those of the Con­tract.

Note

().  If a Discloser makes particular information available to others without a confidentiality agreement (or some other enforceable obligation of confidence), then it's almost a certainty that the information won't be treated as eligible to be Confidential Information. Here are a few examples:

Students: You can just skim these examples.

Example: The Weather Channel ("TWC") successfully defeated a trade-secret lawsuit brought by a former TWC supplier of event-related information because the supplier had itself posted the information on the supplier's own Web site. See Events Media Network, Inc. v. The Weather Channel Interactive, Inc., No. 13-03, slip op. at 16 (D.N.J. Feb. 3, 2015) (granting relevant aspects of Weather Channel's motion for summary judgment) (emphasis added).

Example: An NDA, signed by other parties, didn't bind the defendant Prudential Financial, which had not signed the NDA. See Novus Group, LLC v. Prudential Financial Inc., 74 F.4th 424, 426 (6th Cir. 2023) (affirming summary judgment in favor of Prudential).

Example: A trade-secret plaintiff had provided the supposedly-confidential information to prospective franchisees on Zoom calls without confidentiality agreements. See Smash Franchise Partners, LLC v. Kanda Holdings, Inc., No.  2020-0302, slip op. at 28 (Del. Ch. Aug. 13, 2020) (denying preliminary injunction in relevant part).

Example: A company's employment agreement said merely that the employee would have access to confidential information but did not impose any obligation on the employee concerning the information. See CGB Diversified Services, Inc. v. Baumgart, 504 F. Supp. 3d 1006, 1018 (E.D. Mo. 2020) (granting motion to dismissin relevant part).

Example: A financial firm had disclosed its supposed trade secrets, concerning a particular financial strategy, under an agreement that had explicitly authorized disclosure of the strategy "to any and all persons, without limitation of any kind," so as to avoid adverse consequences under U.S. tax law. See Structured Capital Solutions v. Commerzbank AG, 177 F. Supp. 3d 816, 832, 833-35 (S.D.N.Y. 2016) (Rakoff, J., granting summary judgment against Structured Capital in relevant part; citing cases).

Example: A party had signed an NDA — but the NDA protected only the other party's information. See Fail-Safe, LLC v. A.O. Smith Corp. 674 F.3d 889, 893-94 (7th Cir. 2012) (affirming summary judgment).

Example: Defense contractor Lockheed Martin won a $54 million trade-secret verdict (in 2025 dollars), but then had it taken away after it came to light that Lockheed had disclosed its trade secrets in question to a competitor without restrictions. See Lockheed Martin Corp. v. L-3 Comm. Integrated Sys. L.P., No. 1:05-CV-902-CAP (N.D. Ga. March 31, 2010) (granting L-3's motion for new trial); see also this blog entry of Apr. 6, 2010 by "Todd" (Todd Harris?) at the Womble Carlyle trade secrets blog.

Example: A supplier gave specific price-quote information to a customer without any sort of confidentiality obligation. See Southwest Stainless, LP v. Sappington, 582 F.3d 1176, 1189-90 (10th Cir. 2009) (reversing judgment of misappropriation of trade secrets).

Example: In an oddball case, an individual, one Snyder, made the … amazing decision to sue his former employer, Beam Technologies, for allegedly misappropriating "his" trade secret in a customer list that he had downloaded from another former employer, Guardian. The court affirmed summary judgment in favor of Beam Technologies, on grounds that no reasonable jury could conclude that Snyder had taken reasonable precautions to protect "his" information. See Snyder v. Beam Technologies, Inc., 147 F.4th 1246, 1250, 1256 (10th Cir. 2025) (affirming summary judgment). The court declined to affirm summary judgment that Snyder did not "own" a trade secret in the Guardian customer list, because Colorado's Uniform Trade Secrets Act required only possession, not ownership; see id. at 1254-55 (citing cases) and the "owner" notes at § 5.3.1.)

Example: In a dictum, the Supreme Court of the United States observed: "If an individual discloses his trade secret to others who are under no obligation to protect the confidentiality of the information, his property right [in that trade secret] is extinguished." Ruckelshaus v. Monsanto Co., 467 U.S. 986, 1002 (1984) (lightly edited).

Counterexample: Christopher (1970) represents perhaps an extreme case of a court holding that leaving trade-secret information out in the open, where it could be observed from the air, did not constitute failing to take reasonable precautions:

–  Chemical manufacturer DuPont built a plant near Beaumont, Texas.

–  During the construction, DuPont employees noticed a small plane circling the site.

–  The company's investigation led to father-and-son photographers who had been hired, by an unknown party, to overfly — in public, unrestricted airspace — and photograph the site, allegedly for the purpose of gaining information about a highly-secret DuPont process for producing methanol.

The district court ruled that DuPont had stated a cause of action against the photographers; affirming, the Fifth Circuit harumphed that: "To require DuPont to put a roof over the unfinished plant to guard its secret would impose an enormous expense to prevent nothing more than a school boy's trick." See E. I. duPont deNemours & Co. v. Christopher, 431 F.2d 1012, 1016-17 (5th Cir. 1970) (affirming denial of motion to dismiss and for summary judgment).

Professor Lynda Oswald notes that "half a century later, we have not seen another published trade secret misappropriation case like Christopher in which the defendants were liable despite having broken no law and having breached no contract or confidential relationship."

5.3.12. Exclusion of Toolkit Items

For purposes of this Protocol, Confidential Information does not include "Toolkit Item," namely any concept, idea, invention, strategy, procedure, architecture, or other work (each, an "item"), where all of the following are true:

  1. the Recipient created the item, wholly- or partly, while the Recipient was: (a) working with Confidential Information, and/or (b) otherwise performing the Recipient's obligations under the Con­tract; BUT
  2. the item is not specific to, nor unique to, the Discloser or the Discloser's business; AND
  3. the item itself does not include — nor does it otherwise reveal or clearly suggest — any of the Discloser's Confidential Information.
Note

When a vendor's customer provides its confidential information to the vendor, it should almost go without saying that the vendor should keep the customer's information confidential.

BUT: Unfortunately for vendors, some customer-drafted clauses in this vein can overreach, argubly precluding the vendor provider from using any information the vendor develops during the engagement for any other purpose.

SO: This section seeks a balance between the parties' competing interests.

For additional discussion, see Protocol 23.6.2.11 (IP ownership) and Protocol 23.6.1.4 (Toolkit Item exclusion from ownership transfer).

5.3.13. Exclusion of general knowledge & skills

  1. Background: One or more of the Recipient's people might improve their general knowledge, skills, and experience in the general field(s) of Discloser Confidential Information (or otherwise), as a result of their exposure to that information.
  2. With that in mind: Nothing in this Protocol requires the Recipient's people to limit what they do with that improved general knowledge, etc., so long as they otherwise comply with the obligations of this Protocol.
Note

().  The wording of this exclusion is inspired by § 3 of an AT&T nondisclosure agreement, archived at http://perma.cc/G974-2ZH5; that section states: "… use by a party's employees of improved general knowledge, skills, and experience in the field of the other party's proprietary information is not a breach of this Agreement."

Professor Hrdy points out that excluding general knowledge and skills from confidentiality protection (see § 5.3.13) is "a paradox that runs to the heart of trade secret law: employers are encouraged to communicate trade secrets to employees, but this information loses protection if it becomes part of those employees’ unprotectable general knowledge, skill, and experience." Camilla A. Hrdy, The General Knowledge, Skill, and Experience Paradox, 60 B.C. L. Rev. 2409, 2409 (2019).

Caution: If you're a Recipient, this general-knowledge exclusion might sound good — but it could be troublesome later. Often, it might be hard to determine, on the particular facts, whether the safe harbor applied.

Example: A company sued a former employee for misappropriation of the company's trade-secret information; the former employee tried, but failed, to persuade the court that he had merely used his general knowledge and skills, as opposed to misappropriating his former employer's trade-secret information. See Brightview Group, LP v. Teeters, 441 F. Supp. 3d 115, 133-34 (D. Md. 2020) (granting preliminary injunction; emphasis added); subsequent proceeding, No. 19-2774, slip op. (D. Md. Mar. 26, 2021) (granting plaintiff's motion for summary judgment and permanent injunction).

Example: Relatedly: The Eighth Circuit affirmed a Minnesota federal district court's ruling that "a non-disclosure provision is treated as a non-compete covenant if it prohibits the former employee from using, in competition with the former employer, the general knowledge, skill, and experience acquired in former employment." J.V. & Sons Trucking, Inc. v. Asset Vision Logistics, LLC, 121 F.4th 690, 698 (8th Cir. 2024) (cleaned up, citations omitted, emphasis added).

5.3.14. Secret-sauce exception

If one or more individual items of information do not qualify as Confidential Information, but a particular selection and/or combination of the items does meet the eligibility requirements of this Protocol, THEN: The Recipient is to treat that selection or combination as Confidential Information.

Note

A number of courts have held that "secret sauce" selections and combinations of non-secret information can be eligible for trade-secret protection. You're doubtless familiar with the concept, e.g., from these well-known examples:

•  There's the formula for making Coca-Cola — although that's been described as largely a marketing strategy: According to a former Pepsi CEO's memoir, supposedly the company's food chemists were readily able to reverse-engineer the formula; Pepsi's then-CEO claimed that it took the company's food chemists only a week to reverse-engineer the Coke formula and produce a drink that was essentially identical to The Real Thing. See Roger Enrico and Jesse Kornbluth, The Other Guy Blinked: How Pepsi Won [sic] the Cola Wars (1986).

•  Consider the Kentucky Fried Chicken "secret blend" of 11 herbs and spices: That's also perhaps mainly a marketing strategy (supposedly, the key ingredient is white pepper).

More secret-sauce examples:

–  Insurance policyholder data, compiled into a spreadsheet; See Allstate Ins. Co. v. Fougere, 79 F.4th 172, 176 (1st Cir. 2023).

–  Proprietary flowcharts showing publicly-available information in a useful form; See AirFacts, Inc. v. de Amezaga, 909 F.3d 84, 88-89, 96-97 (4th Cir. 2018).

–  Meat-packing information, commonly-known but selected and compiled; See Tewari De-Ox Sys., Inc., v. Mountain States/Rosen, L.L.C., 637 F.3d 604, 613-14 (5th Cir. 2010) (citing cases).

–  A "winning combination" of known, generic software programs; See Integrated Cash Mgmt. Servs., Inc. v. Digital Transactions, Inc., 920 F.2d 171, 174 (2d Cir. 1990).

5.3.15. Marked information

  1. The Recipient will treat Discloser information as Confidential Information if the information is marked — in suitably-prominent fashion — as confidential; do so until such time (if any) as the information is shown to be within one or more exclusions from confidentiality (see the exclusion items beginning at § 5.3.9).
  2. The Discloser may do (timely) catch-up marking as provided at § 5.3.16.
Note

().  Background: Marking of confidential information is one of the classic ways for a Discloser to show (indirectly) that it took reasonable precautions to protect the information — but quite reasonably, Disclosers prefer not to have marking be a hard-and-fast requirement. ¶ The term "suitably-prominent fashion" would ordinarily mean readily calling attention to the confidential status of the information.

Caution: Requiring marking of confidential information is not the best idea. To be sure, marking documents as "Confidential" is always a good practice. But when a confidentiality provision requires marking — even with catch-up marking allowed — it might undesirably raise the bar for the Discloser, possibly with significant ill effect: If for some reason a particular Discloser document wasn't marked, then a court might well summarily reject the Discloser's claim of confidentiality. Example: This happened in a case involving software giant SAP, as well as in a case involving Houston's own Compaq Computer Corp. (which is now part of Hewlett-Packard). See Teradata Corp. v. SAP SE, 570 F. Supp. 3d 810, 826-28 (N.D. Cal 2021) (granting SAP's motion for summary judgment on technical trade secret claim); Convolve, Inc. v. Compaq Computer Corp., 527 Fed. Appx. 910 No. 2012-1074, slip op. at part II.A.2 (Fed. Cir. 2013) (nonprecedential); see also Gemisys Corp. v. Phoenix American, Inc., 186 F.R.D. 551, 558-60 (N.D. Cal. 1999).

That's why here we set up presumptions to encourage the Discloser to mark its Confidential Information — but we don't make marking an absolute requirement, so long as the information in question bears other indicia of confidentiality.

Caution: The Discloser shouldn't go overboard in marking non-confidential information, because that could backfire: If the Discloser were to go crazy with a CONFIDENTIAL stamp and mark obviously-nonconfidential information as confidential, that could hurt the company's credibility in claiming that other, marked information was confidential.

And worse: Marking nonconfidential information as confidential — and then suing for misappropriation of the alleged trade secrets — could lead to a finding of bad-faith litigation. See Jesse M. Coleman and Kevin Green, Not All Documents Labeled Confidential Actually Are: Texas Jury Finds $23M Trade Secret Case Was Brought in Bad Faith (Seyfarth.com 2023), discussing Teligistics Inc. v. Advanced Personal Computing Inc., No. 2019-15000, 190th District Court of Harris County, Texas.

Another benefit of marking: According to two courts, confidentiality markings, standing alone, are likely to be enough — at least at the pleading stage — to support the Discloser's contention that it took reasonable steps to maintain secrecy. See Samuel Sherbrooke Corporate, Ltd v. Mayer, No. 24-2173, part III.A, slip op. at 9 (4th Cir. Nov. 18, 2025) (reversing and remanding judgment on the pleadings for trade-secret defendant), citing InteliClear, LLC v. ETC Glob. Holdings, Inc., 978 F.3d 653, 660 (9th Cir. 2020) (reversing and remanding summary judgment for trade-secret defendant).

5.3.16. Catch-up marking

The Discloser may retroactively mark information as confidential after giving the Recipient access to the information, but only by doing both of the following things within a reasonable time after the initial unmarked access:

Note

This section provides a compromise that takes into account some of the practical realities of disclosures of confidential information: • Sometimes the Discloser's marking of Confidential Information might fall through the cracks; and • for some Confidential Information, the Discloser might make the information available to the Recipient via, for example, an unmarked written disclosure; an oral disclosure; a tour of a factory floor or the like; or a product demonstration.

  1. causing the Recipient to be provided with a marked written version of the information — this could be a reasonably-detailed written summary; and
  2. giving the Recipient notice that the marked written version was provided.
Note

This notice requirement both alerts the Recipient and provides a paper trail to document the fact for future reference.

5.3.17. Information in Discloser files

If the Recipient initially gained access to particular Discloser information in one or more of the Discloser's own files (hard copy, digital, or otherwise), THEN: The Recipient will treat that information in the same way as if the information were marked as Confidential Information, whether or not the information is in fact so marked.

Note

Sometimes the Discloser will be letting the Recipient have access to the Discloser's own internal files. When that's the case, the Discloser shouldn't have to worry about achieving perfect compliance in putting confidentiality markings on everything that the Recipient might encounter in those files.

5.3.18. Likely-confidential information

If reasonable people in the relevant trade or business would recognize particular Discloser information as likely to be confidential, THEN: The Recipient will treat that information as Confidential Information.

Note

This is often seen in Discloser-drafted forms. ¶ The terms "reasonable people" and "likely confidential" are of course pretty vague. That could result in proof burdens in litigation. But it seems a worthwhile risk for the resulting benefit in reduced day-to-day burden in paperwork- and tracking.

5.3.19. Recipient secrecy measures

The Recipient will take the following measures to preserve the secrecy of Discloser Confidential Information within the Recipient's possession, custody, or control:

Note

It's pretty much "a must" for the Discloser to require the Recipient to take protective measures — otherwise, the Discloser will likely forfeit its trade-secret rights in the Confidential Information, as discussed in the notes to 5.3.11. ¶ Possession, custody or control: See also this article.

  1. at least prudent measures; and
  2. any other specific measures required by the Con­tract.
Note

Possible secrecy measures: See the notes to § 5.3.2.

Note

().  What would constitute prudent Recipient measures would likely depend on the circumstances. Prudent measures:

  • should normally be read as requiring more than mere reasonable efforts;
  • is arguably less vague than commercially-reasonable efforts (concerning which, see Protocol 9.2); but
  • doesn't go as far as requiring best efforts — a standard that can be problematic, for reasons discussed in the notes to Protocol 9.1.

    Caution: At trial in a lawsuit, the Recipient's secrecy measures might not be considered "prudent" if those measures aren't at least as protective of Discloser Confidential Information as the measures that the Recipient uses for the Recipient's own confidential information of comparable significance. BUT: That doesn't mean that the Recipient's own measures are to be used as the standard for what constitutes prudent measures.

5.3.20. Prohibited Recipient actions

Except as [BROKEN LINK: clear-agrd] by the Discloser, the Recipient must not do any of the following:

  1. use Confidential Information;
  2. disclose Confidential Information to others;
  3. reproduce Confidential Information;
  4. translate Confidential Information;
  5. reverse-engineer Confidential Information or use it in reverse-engineering anything else — this is intended as a WAIVER of any right that the Recipient might otherwise have by law to engage in reverse engineering;
  6. remove the Discloser's confidentiality markings (if any);
  7. use Confidential Information in training a large language model ("LLM") or other artificial-intelligence system;
  8. try to do anything listed in any of subdivisions 1 through 7; nor
  9. authorize anyone else — or knowingly allow or ‑help anyone else — to do anything listed in subdivisions 1 through 8 above.
Note

().  Including language along these lines is another "must" for NDAs — otherwise, the Discloser will likely forfeit its trade-secret rights in the Confidential Information; this is discussed in more detail in the notes to 5.3.11.

Subdivision 5: See the discussion of reverse engineering at 31.31.

5.3.21. Derivatives

The Recipient will treat "derivatives" of Confidential Information in the same way as the Recipient is required to do for Confidential Information itself — for this purpose, the term derivatives refers to things such as analyses; compilations; forecasts; interpretations; notes; reports; studies; summaries; and similar materials; when:

  1. they contain, or are based on, Confidential Information, and
  2. they're prepared by, for, or on behalf of, the Recipient.

5.3.22. Subpoenas, etc.

  1. The Discloser has no objection to the Recipient's disclosure of Confidential Information, in a strictly-limited way, in response to compulsory legal process,as long as the Recipient takes the actions in this § 5.3.22.
  2. Here, "compulsory legal process" refers to (for example) a subpoena, search warrant, or other order, issued by competent legal authority, where noncompliance could result in adverse action such as jailing.
  3. Ordinarily: The Recipient will alert the Discloser immediately upon being served with compulsory legal process that demands production of Confidential Information.
  4. But: The Recipient may use discretion about whether and when to alert the Discloser in either of the two following situations:
    1. a governmental authority (e.g., law enforcement) asks the Recipient not to inform the Discloser; and/or
    2. alerting the Discloser would violate applicable law.
  5. If the Recipient does alert the Discloser under subdivision 3, THEN: The Recipient will provide reasonable cooperation with any efforts by the Discloser to limit or otherwise seek protection for such compulsory disclosures — but only to the extent that the Discloser asks for such cooperation.
  6. In any case: The Recipient must not disclose more than the minimum Confidential Information required to respond to the compulsory legal process.
  7. In case questions arise:
    1. This § 5.3.22 does not authorize the Recipient to make non-compulsory disclosures of Confidential Information — for example, in public filings with the Securities and Exchange Commission (SEC) — that possibility is addressed at Option 5.3.33.4.
    2. Discloser information would not be excluded from Confidential-Information status just because the information became the subject of compulsory legal process.
Note

().  A Recipient that's targeted with a search warrant or subpoena should have a reasonable amount of flexibility in dealing with law enforcement and other officials, without having also to worry that it would be hit with, say, punitive damages in a subsequent Discloser lawsuit for violating the NDA.

Subdivision 3: When information is subpoenaed or subject to a search warrant, the information's secrecy can often be protected by court order (which litigators call a "protective order"). As a result, the Discloser wouldn't want the information to automatically be excluded from Confidential-Information status entirely, just because a subpoena, a search warrant, etc., had been issued.

Subdivision 5: What counts as "reasonable" Recipient cooperation with the Discloser, in defending against a subpoena or other compulsory process, might depend in part on the extent to which the Discloser agreed to bear any significant associated Recipient expenses.

5.3.23. Check-ins?

The Recipient is encouraged (but not required) to consult with the Discloser if the Recipient ever believes that particular Discloser information comes within within one or more of the exclusions from Confidential Information status in this Protocol.

Note

This is one of the "Pick up the phone!" suggestions intended to help parties identify and resolve potential disputes as early as possible.

5.3.24. Authorized uses

As far as the Discloser is concerned, the Recipient can utilize Confidential Information — only during the term of the Con­tract, and only as provided by this Protocol — as reasonably necessary for any or all of the following purposes:

  1. deciding whether to enter into another agreement with the Discloser;
  2. performing the Recipient's obligations, and/or exercising the Recipient's rights, under the Con­tract; and/or
  3. any other purpose specified by the Con­tract or otherwise agreed in writing by the Discloser.
Note

().  Caution: Applicable law might impose other restrictions on the Recipient's actions with Confidential Information, e.g., in the case of privacy laws protecting, e.g., protected health information or personal financial information (see 5.6), or export-controlled information (see 31.9).

Many confidentiality-agreement forms require the drafter to fill in the "Purpose" for which the Recipient is allowed to use Confidential Information. Drafters, however, can sometimes neglect to fill in the blank. For that reason, this section "pre-clears" some of the most-common use cases.

Subdivision 2 supports using this Protocol in a larger agreement in which confidentiality provisions are only a part, not the main point.

Pro tip: In some circumstances, the Recipient might want to negotiate for "have-used" rights (see 31.18), that is, the right to allow specified third parties (e.g., contractors) to use Confidential Information for the Recipient's benefit.

5.3.25. Authorized disclosures

  1. As far as the Discloser is concerned, the Recipient may disclose Confidential Information — during the term of the Con­tract, and only as provided by this Protocol — to the Recipient's employees, officers, directors, and other individuals holding comparable positions in the Recipient if the Recipient is not a corporation (collectively, "individuals"), so long as the Recipient complies with this § 5.3.25.
  2. Each such individual must be bound by legally-enforceable confidentiality obligations — in a written agreement, or otherwise — that cover the Confidential Information in question.
  3. The Recipient must disclose information to those individuals only on a need-to-know basis in connection with an authorized use, disclosure, or translation of the Confidential Information.
  4. The Recipient must instruct each such individual about the Recipient's confidentiality obligations (and thus the individual's own obligations) concerning the Confidential Information, under the Con­tract and/or by law.
Note

().  Subdivision 1: In case the Discloser additionally wants to require the Recipient to enter into written agreements even with Recipient employees, etc., see the optional language for that purpose at Option 5.3.32.6.

But Entering into a written confidentiality agreement with employees, etc., might not be necessary. That's because (at least in the U.S.) the Recipient's employees, officers, and directors would normally be legally bound to preserve the Recipient's confidential information — and thus, by implication, the Discloser's Confidential Information — even without a written confidentiality agreement.

That said: Many, many employers do require employees to indeed sign written confidentiality agreements, either separate agreements or as part of a larger employment agreement.

5.3.27. Copies & translations

The Discloser has no objection to the Recipient's making copies and/or translations of Confidential Information (or have them made by contractors under suitable obligations of confidence), but only during the term of the Con­tract, and only as follows:

  1. copies and translations that are reasonably necessary for authorized uses and disclosures;
  2. archive copies in accordance with Protocol 5.1; and
  3. reasonable routine backup copies of electronically-stored Confidential Information.
Note

This section explicitly authorizes copies and translations of Confidential Information to be made by Recipient contractors. Example: In Great Minds (2d Cir. 2018), FedEx Office successfully asserted that a Creative Commons license, which prohibited "commercial" use, nevertheless allowed FedEx to charge schools for making copies of licensed materials: The court held that the copying by FedEx, for school districts, still qualified as noncommercial under the Creative Commons, even though FedEx had charged the school districts for making the copies, because the license did not exclude such copying. See Great Minds v. FedEx, 886 F.3d 91 (2d Cir. 2018) (affirming dismissal under Fed. R. 12(b)(6)).

5.3.28. Marking of copies & translations

  1. If the Recipient makes (or has made) copies and translations of Confidential Information, AND: The Discloser source document(s) containing that Confidential Information included confidentiality markings; THEN: The Recipient is to see to it that those confidentiality markings — translated if appropriate — are included in the copies and translations.
  2. To illustrate, here are some hypothetical examples when a Discloser source document includes a single confidentiality notice at the beginning of the document:
    1. Situation: The Recipient makes a copy of only selected portions of a Discloser source document. Action: The Recipient must have that copy marked with the same confidentiality notice.
    2. Situation: The Recipient arranges for those copied portions to be translated into French. Action: The Recipient must have the translated portions marked with the same confidentiality notice, also translated into French.

5.3.29. Recipient compliance with law

  1. The Recipient must comply with applicable law in all of the Recipient's activities involving Confidential Information — including, for example, laws concerning privacy; export controls; and insider trading.
  2. This legal-compliance obligation will not expire — this is an exception to the expiration provision in § 5.3.5.
Note

().  Privacy law: See Protocol 5.6.

Export controls: See ¶ 31.9.

5.3.30. Recipient indemnity obligations

  1. The Recipient will defend and indemnify the Discloser and the Discloser's Protected Group against any harm, where the harm is alleged to arise from:
    1. any of the Recipient's own activities under this Protocol, and/or
    2. any activities by someone else to whom the Recipient made Discloser Confidential Information available.
  2. This indemnity- and defense obligation will not expire (this is an exception to the expiration provision in § 5.3.5).

5.3.31. RELEASE of Discloser

By entering into the Con­tract, the Recipient RELEASES — in advance — each person within the scope of the indemnity of § 5.3.30 from any liability arising from any activity covered by that indemnity.

5.3.32. Discloser playbook

5.3.32.1. Option: Return or Destroy Obligation

If this Option is agreed to: The Recipient is to follow Protocol 5.4 (purge of materials) if the Discloser so requests in writing — but the Recipient need do so only if the Discloser's request occurs within a reasonable period following the termination or expiration of the Con­tract.

Note

See the commentary to Information Purge Protocol (5.4).

5.3.32.2. Option: Required Recipient Cooperation
  1. If this Option is agreed to, the Recipient is to provide reasonable assistance,
    • whenever the Discloser asks,
    • in investigating,
    • and/or taking legal action against third parties concerning,
    • possible unauthorized use and/or disclosure of Confidential Information to which the Recipient had access.
  2. But: The Recipient is not to take any action on its own against a third party — apart from the Recipient's own employees and/or contractors, if applicable — unless the Discloser specifically so requests.
  3. Any assistance that the Recipient provides under this Option would normally be at the Discloser's expense — but that might change if the Recipient was responsible, directly or indirectly, for the unauthorized use and/or disclosure.
  4. In deciding what the Recipient would do to provide assistance to the Discloser, the Recipient may take into account any applicable attorney-client privilege or other privilege to which the Recipient is entitled.
Note

Subdivision 2: A Recipient could, for example, take disciplinary action against a Recipient employee that was, say, planning to leave the Recipient and start a company using the Discloser's confidential information.

5.3.32.3. Option: Recipient's Third-Party Responsibility
  1. If this Option is agreed to, it will govern whenever both of the following are true:
    1. a third party — including but not limited to the Recipient's employees — obtains or otherwise accesses Confidential Information from the Recipient, whether directly or indirectly; and
    2. the third party uses, discloses, and/or copies Confidential Information in a manner that is not permitted by the Con­tract.
  2. The Recipient must defend and indemnify the Discloser and the Discloser's Protected Group from any harm to the Discloser's interests arising from the third party's action, to the same extent as would be required for the Recipient's own use, disclosure, or copying of the Confidential Information.
  3. For emphasis: The Recipient's obligation under this Option is not limited to indemnifying only claims against the Discloser.
Note

().  This is set out as an Option, and not as part of Protocol 5.3, because it might apply only in limited situations. (A Recipient might push back if asked to agree to this Option, but the Discloser will usually want "one throat to choke" — a trite but still-useful expression.)

Subdivision 2 This contemplates (without limitation) the situation in which an employee of the Recipient quits her job and, in a new job — or a new venture — uses the Discloser's Confidential Information.

Subdivision 3: For more on this "first-party" obligation, see 14.3.5.

5.3.32.4. Option: Discloser's Right to Restraining Order

If this Option is agreed to: The Discloser has the right to seek a restraining order a restraining order against the Recipient's unauthorized use or disclosure of Confidential Information in accordance with applicable law.

Note

().  This Option uses the better-known term "restraining order" instead of (for example) "preliminary injunction" because the latter phrasing is likely to be less familiar to non-lawyers.

See also Protocol 21.10 (equitable relief) and Protocol 21.4 (bond waiver).

5.3.32.5. Option: Recipient's Whistleblower Obligation
  1. If this Option is agreed to: The Recipient is to promptly alert the Discloser to any potential unauthorized use or disclosure of Confidential Information of which the Recipient becomes aware, even if the Recipient might be (or is) at fault.
  2. For emphasis: The Recipient is to report suspected activity by one or more of:
    1. one or more of the Recipient's employees, whether or not their actions were or are in the scope of their employment with the Recipient; and/or
    2. any other party to which the Recipient provides Confidential Information, whether or not as authorized by the Con­tract.
Note

().  Some Recipients might be reluctant to agree to the whistleblower obligation of this Option, because it would mean that:

  • the Recipient's failing to blow the whistle on one's own potential "issues" with Confidential Information — or those of a Recipient contractor — would technically be a breach of contract by the Recipient;
  • if it turned out that there wasn't actually a problem, then the Discloser's damages for the Recipient's technical breach would presumably be nil or nominal, but
  • the Recipient's technical breach still might trigger a prevailing-party attorney-fee clause (see 21.2),
  • and that in turn could force the Recipient to pay the Discloser's perhaps-exorbitant legal expenses — even though the Discloser had suffered no real-world harm. Example: Something like this happened in a factually-complex — and, frankly confusing — California case. See Elation Sys. Inc. v. Fenn Bridge LLC, 71 Cal. App. 5th 958, slip op. at 23-25 (Cal. App. Nov. 22, 2021) (unpublished portion of opinion that vacated and remanded award of attorney fees to prevailing defendants).

    Still: A Recipient should at least be open to agreeing to this Option, because it's consistent with the "communicate!" theme of this book.

5.3.32.6. Option: Written Confidentiality Agreement Requirement
  1. If this Option is agreed to, it will apply — if requested by the Discloser — whenever the Recipient anticipates providing Confidential Information to any person (including but not limited to the Recipient's employees) (each, a "Downstream Recipient").
  2. The Recipient must not provide Confidential Information to any Downstream Recipient unless the Recipient and the Downstream Recipient enter into a written confidentiality agreement in which the Downstream Recipient commits to complying with substantially the same confidentiality obligations as apply to the Recipient under the Con­tract.
  3. If the Discloser asks, THEN: The Recipient is to provide the Discloser with a copy of the signed confidentiality agreement — but see also subdivisions 4 and 5 below.
  4. The Recipient may redact that copy of the signed confidentiality agreement — to a reasonable extent — so that the Discloser will not have access to the Recipient's own confidential information and/or that of the Downstream Recipient.
  5. The Recipient and the Discloser are to escalate any persistent disagreement about such redactions if either of of them asks, as provided at Protocol 21.11.
Note

().  This Option is sometimes proposed by Disclosers, but it will often be overkill when it comes to the Recipient's employees, members of Recipient's board of directors, and others associated with Recipient who are required to maintain confidentiality as a matter of law. See, e.g., Adnet v. Soni, 66 F.4th 510, 517-18 (4th Cir. 2023) (reversing and remanding summary judgment; a reasonable jury could find that former employees had breached their duty of loyalty by preparing to compete with their then-employer while still employed).

Subdivision 3: Providing signed copies of confidentiality agreements might be burdensome for the Recipient, but sometimes the Discloser might feel it has a genuine need for such copies.

Subdivision 4: The reasonableness requirement for redaction has in mind that some government documents are sometimes supposedly declassified in redacted form but with a risible number of redactions.

5.3.32.7. Option: Confidential Information Segregation Requirement

If this Option is agreed to: The Recipient is to segregate all Confidential Information — if and when the Discloser so requests in writing to particular information — with a view to:

  1. providing additional secrecy protection, and
  2. facilitating any return or destruction that might be required by the Con­tract (if any).
Note

An obligation to segregate Confidential Information could well be unduly burdensome on the Recipient. But: Even without a contractual obligation to do so, the Recipient might want to segregate Confidential Information anyway, without committing to do, because that could save considerable trouble down the road.

Example: In a Texas case, a jury awarded $53 million (in 2025 dollars) for misappropriation of trade secrets — perhaps significantly, a representative of the defendant had falsely assured the trade-secret owner that the defendant had returned or destroyed the information. See S.W. Energy v. Berry-Helfand , 491 S.W.3d 699, 708 (Tex. 2016). The Texas supreme court vacated the damages award and remanded for a new trial; in a subsequent SEC filing, the defendant disclosed that the parties had settled the case.

5.3.32.8. Option: Inspections for Confidentiality Compliance
  1. If this Option is agreed to, it will govern at any time that the Recipient has, or might have, Confidential Information in its possession.
  2. The Recipient must allow the Discloser to cause reasonable inspections to be conducted, from time to time, of the Recipient's relevant properties and premises (tangible, electronic, and otherwise).
  3. The Discloser must not use any such inspection and its results (nor allow such use) for any purpose other than to confirm that the Recipient is complying with its confidentiality obligations under the Con­tract.
  4. Protocol 9.8 (inspections) and, where applicable, Protocol 9.4 (general rules for computer-system access), are incorporated by reference.
  5. The Recipient must include appropriate flow-down provisions for this Option in any agreement under which the Recipient makes Confidential Information accessible by a third party. (For emphasis: This subdivision 5, in itself, does not authorize the Recipient to use subcontractors, but neither does it prohibit the Recipient from doing so.)
Note

().  Subdivision 2 follows the maxim that you get what you INspect, not what you EXpect (see 9.8). Caution: The Recipient might be extremely reluctant to agree to this Option — especially if the Recipient and the Discloser are (or might become) competitors or are somehow associated with competitors — e.g., a vendor Recipient might be concerned that a customer Discloser might pass on the vendor's own confidential information to a competing vendor.

Subdivision 3 could help assuage possible Recipient concerns that the Discloser might want to use an "inspection" for corporate-espionage purposes — for example, to help a competitor of the Recipient that the Discloser was considering doing business with.

Subdivision 5: For more about flow-down obligations, see generally 3.6.3.

5.3.32.9. Option: Recipient's Indemnity Obligation

If this Option is agreed to: The Recipient must defend and indemnify the Discloser and the Discloser's Protected Group against any claim, by a third party, arising out of:🔗

  1. the Recipient's use of Confidential Information, and/or
  2. the Recipient's disclosure of Confidential Information to other parties,

whether or not the Recipient's relevant use and/or disclosure of Confidential Information was of a kind contemplated by the Con­tract.

Note

().  As with any defense- and indemnity obligation, the Discloser should consider proposing that the Recipient agree to maintain insurance as backup funding for the obligation (remember the "I&I" mnemonic), as discussed at 31.21.

Even without a contractual insurance requirement, the Recipient should consider: • making sure it has appropriate insurance coverage of its own to support its indemnity obligations, and • trying to negotiate a cap on its indemnity liability.

5.3.32.10. Option: Recipient's Assignment-Consent Requirement
  1. If this Option is agreed to, the Recipient must not assign the Con­tract without the Discloser's prior written consent.
  2. Protocol 15.3 (assignment consent) is incorporated by reference into this Option.
Note

().  Whether an assignment-consent obligation would work for the Recipient would depend in part on how long the Recipient was expected to possess the Discloser's Confidential Information and how long the Recipient's confidentiality obligations would last — and in a long-term confidentiality agreement, such an obligation could undesirably give the Discloser a strategic veto over the Recipient's business prospects, as discussed at 15.3.5.1.

Moreover: An assignment-consent obligation might not even be necessary except as a "for the avoidance of doubt" provision. That's because (at least arguably) as a matter of law, confidentiality agreements might not be assignable, as discussed at 15.3.7.4 and 15.3.7.5.

Pro tip: If a Recipient were asked to agree to an assignment-consent obligation, the Recipient could consider countering by proposing Option 15.3.5.1 (exception for asset-disposition transactions), for reasons discussed there.

5.3.33. Recipient playbook

5.3.33.1. Option: Recipient-to-Acquirer Disclosure Right
  1. If this Option is agreed to, it will govern if the Recipient contemplates engaging in a merger, spin-off, or similar "Transaction." with one or more "Transaction Prospects," namely the following:
    1. a prospective acquirer of substantially all assets of (1) the Recipient'sbusiness as a whole, or (2) the portions of the Recipient's business to which the Con­tract relates;
    2. a prospective acquirer of substantially all of the Recipient's shares (if the Recipient is a corporation or similar organization) or of equivalent ownership interest under applicable law (if the Recipient is an organization that does not have shares); and/or
    3. a party (or an affiliate of a party) with which the Recipient anticipates engaging in a merger, or similar transaction.
  2. As long as this Option continues to be complied with, the Recipient and/or any Transaction Prospect may provide the Discloser's Confidential Information — only to those qualifying under this Option — to any Adviser or Transaction Prospect (each, a "Downstream Recipient") as follows:
    1. to the employees, board members, attorneys, accountants, and other professional advisers — these categories of individuals are referred to generically for convenience as "Advisers" — of the Transaction Prospect; and
    2. to the Recipient's own Advisers.
  3. The Recipient must not disclose Discloser Confidential Information to any Downstream Recipient unless, in each particular case, the Downstream Recipient:
    1. has a legitimate need to know in connection with the possible transaction; and
    2. has a legal duty — by contract, or as a matter of law or comparable professional governance standards, e.g., in an attorney-client relationship with the possibility of disbarment — to preserve the information in confidence in accordance with this Option.
  4. The Recipient must not provide Discloser Confidential Information to a Transaction Prospect unless the following prerequisites have been met:
    1. The Transaction Prospect must agree with the Recipient, in writing, to comply with this Option concerning the Discloser's Confidential Information.
    2. If the Discloser asks, THEN: The Recipient must promptly provide the Discloser with a copy of the signed confidentiality agreement between the Recipient and the Transaction Prospect.
  5. The Recipient may reasonably redact the copy provided under subdivision 4.b to delete or conceal information that does not concern the Transaction Prospect's confidentiality obligations that would benefit the Discloser.
  6. The Recipient must make sure that any disclosure to a Transaction Prospect or its Advisers under this Option is done in one or more secure physical- and/or online data rooms — each of which must be under the Recipient's control.
  7. The Recipient must take prudent measures to keep the Transaction Prospect (and the Recipient's and the Transaction Prospect's respective Advisers), absent the Discloser's agreement, from doing any of the following:
    1. making copies of the Discloser's Confidential Information, and/or
    2. providing Confidential Information to others not authorized by the Con­tract.
  8. Neither the Recipient nor the Transaction Prospect need inform the Discloser:
    1. that a transaction might occur;
    2. the status of negotiations for the transaction; nor
    3. any details about the possible transaction.
  9. The Discloser must preserve in strict confidence — and neither use nor disclose — non-public information that the Discloser obtains about the discussions between the Recipient and the Transaction Prospect.
Note

().  Subdivision 6: In M&A transactions, either physical or, more likely, online data rooms are commonly used for due diligence disclosures.

Subdivision 7: In a transaction of this kind, the (prospective) buyer and its Advisers will likely want to create a record of their "due diligence" in the transaction. This would usually including keeping their own archive copies (see Protocol 5.1) of documents inspected — possibly including the Discloser's Confidential Information.

Possible alternative: If the data room is provided by a trusted third party with its own confidentiality obligations to the Discloser, then the Transaction Prospect might be satisfied by getting a contractual commitment to maintain archive copies for the Transaction Prospect.

Subdivision 8: In some especially-sensitive circumstances, the Discloser might want to restrict access to Confidential Information, for example by requiring all such access to be in a secure physical data room with no ability to make or take away copies — even requiring people to leave their phones and other recording devices outside the data room — much as in a SCIF used for secret national-security information, about which Wikipedia has some useful general information. See generally Sensitive compartmented information facility (Wikipedia.org); concerning online data rooms, see Virtual data room (Wikipedia.org).

5.3.33.2. Option: Recipient-to-Contractor Disclosure Right
  1. If this Option is agreed to, the Recipient is free to disclose Confidential Information to the Recipient's suppliers and contractors (so-called "have-used rights"), but only where all of the following are true:
    1. the disclosure must be solely for use by the supplier or contractor for the Recipient's direct benefit;
    2. the Recipient must first obtain a written confidentiality agreement from the relevant supplier or contractor; and
    3. that confidentiality agreement must contain confidentiality provisions — clearly (and, preferably, expressly) benefiting the Discloser — that are substantially identical to those of Protocol 5.3.
  2. The Con­tract could address the extent — if any — to which other persons are prohibited from being given access to Confidential Information.
Note

().  Background: In today's modern economy, a Recipient might need "have-used rights," discussed in more detail at 31.18.

Caution: Some confidentiality agreements categorically allow disclosure to the Recipient's (outside) consultants and advisors. But from the Discloser's perspective, it's usually better for such rights to be negotiated on a case-by-case basis — because recipient contractors have been known to misappropriate discloser information in developing a competitor to the discloser's product line. See, e.g., Computer Sciences Corp. v. Tata Consultancy Servs. Ltd., No. 24-10749, part III.A.1, slip op. at 12-15 (5th Cir. Nov. 21, 2025) (affirming jury verdict of $168 million against Tata but remanding for modification of scope of permanent injunction); cf. ECIMOS, LLC v. Carrier Corp., 971 F.3d 616 (6th Cir. 2020) (affirming, in relevant part, judgment on $5 million jury verdict against Carrier for allowing Carrier contractor to develop competitor to vendor's software).

Caution: The Discloser might want to try to negotiate for a provision such as the Option of § 5.3.32.6, requiring the Recipient to provide the Discloser with copies of its agreements with such suppliers and/or contractors to verify that those agreements include the required confidentiality provisions. Otherwise, the Discloser might find itself unable to sue a supplier or contractor that innocently used Discloser information — this evidently happened in a First Circuit case where an end-customer's insurance carrier found itself unable to recover damages from a supplier's supplier that had suffered a data breach. See Axis Ins. Co. v. Barracuda Networks, Inc., No. 24-1920, part II.B, slip op. at 3, 8-9 (1st Cir. 2025) (affirming summary judgment in favor of vendor whose system suffered data breach).

5.3.33.3. Option: Discloser's Secrecy Representation

If this Option is agreed to: The Discloser represents to the Recipient that the Discloser has not made any Confidential Information available to any third party without confidentiality obligations that are substantially the same as those of the Con­tract.

Note

().  Background: In entering into an NDA, the Recipient might want some assurance that the Discloser isn't merely blowing smoke about the alleged confidentiality of the information to be disclosed. This Option is modeled on a clause that was relevant in an Eleventh Circuit case: "Silikal represents and warrants that it has not disclosed the formula for 1061 SW resin or sold or distributed 1061 SW resin, directly or indirectly, to anyone other than AcryliCon during the pendency of the Silikal/AcryliCon relationship." AcryliCon USA, LLC v. Silikal GmbH, 985 F.3d 1350, 1358 n.11 (11th Cir. 2021).

To reduce the chances of alarming the Discloser, in this Option the Discloser is asked only to represent the secrecy of its information, as opposed to also warranting it. (For more about the distinction between the two, see 16.2.)

5.3.33.4. Option: Recipient Public-Filings
  1. If this Option is agreed to: The Recipient may include Confidential Information in a legally-required submission to a regulatory agency or other governmental body, but only as stated in this Option.
  2. The Recipient will do the following for any inclusion of Confidential Information in a filing that could become available to anyone other than relevant government officials:
    1. consult with the Discloser, so as to give the Discloser a reasonable opportunity to seek an order for confidential treatment or comparable relief;
    2. not disclose more Confidential Information, in any such filing, than the minimum required to comply with the law.
  3. If the Discloser asks: The Recipient will cooperate in any efforts by the Discloser to limit the disclosure, and/or to obtain legal protection for the information to be disclosed — this is to be in the same manner as if the proposed disclosure were in response to a compulsory legal demand as provided in § 5.3.22 (subpoenas, etc.).
  4. If the Discloser asks: The Recipient will reimburse the Discloser, in accordance with Protocol 4.7, for reasonable expenses incurred by the Discloser in any efforts under this Option.
  5. The Discloser will treat nonpublic information about the Recipient's prospective filing as the Recipient's Confidential Information in the same way that the Recipient must treat the Discloser's Confidential Information.
Note

().  Caution: If a Recipient were to include a Discloser's Confidential Information in a public filing (for example, a public company's periodic reports filed with the Securities and Exchange Commission), it likely would destroy the Discloser's trade-secret rights in the information. This was implictly noted, for example, by the U.S. Supreme Court in its 1984 Ruckelshaus v. Monsanto opinion (at 1011-12 & n.15), in which the Court remarked that the EPA's disclosure of Monsanto pesticide test data would destroy Monsanto's trade-secret rights in that data.

Confidential treatment orders are sometimes available to protect confidential portions of filings with the Securities and Exchange Commission; see generally the Investopedia article on requests for confidential-treatment orders. ¶ This one of the "pick up the phone!" (see 2.2) suggestions to help the parties designed to try to identify and resolve potential disputes as early as possible. and

Pro tip: Drafters considering this Option would do well to carefully read then-Chancellor Strine's careful opinion in a bitter corporate dispute on this point. See Martin Marietta Materials, Inc v. Vulcan Materials Co., 56 A.3d 1072 (Del. Ch.) (Strine, C. enjoining MMM, for four months, from pursuing proxy contest for Vulcan Materials due to MMM's violation of NDA), aff'd, 68 A.3d 1208 (Del. 2012) (en banc).

5.3.33.5. Option: Recipient's Residuals-Rights

If this Option is agreed to:

  1. The Recipient will not be liable to the Discloser under this Protocol — for compensation or otherwise — if the Recipient makes unaided use of Confidential Information "residuals," defined below, as stated in this Option.
  2. In this context, the term "residuals" refers to ideas, concepts, know-how, techniques, and similar information, where each of the following is shown by clear and convincing evidence:
    1. the information was retained in the unaided memory of one or more of the Recipient's people; and
    2. none of those people intentionally memorized the information for that purpose.
  3. The parties desire that this Option be interpreted narrowly, because it is intended only to mitigate the potential for costly and time-consuming disputes that could arise from inadvertent breach of the Recipient's confidentiality obligations under the Con­tract.
  4. For emphasis: This Option does not:
    1. relax any restriction of the Con­tract on the Recipient's disclosure of Confidential Information; nor
    2. give the Recipient any license under any patent, copyright, or other intellectual-property right that you own or could otherwise assert against the Recipient.
Note

().  Background: Some recipients of confidential information — cough, Microsoft — have been known to demand "residuals rights" of this kind, as discussed in the extended comments below.

Disclosers likely will — and often should — push back or at least ask for carve-outs for particularly-sensitive categories of information, e.g., details of technology; pricing; key personnel; and similar categories. See generally Kapoor & Yaghoubi (MorganLewis.com 2017).

Caution: To say the least, this could be a tricky evidentiary problem — for both sides, as discussed in the note below.

Subdivision 1 — here's an example of a Microsoft residuals clause: "Each party agrees that the use of information retained in Representatives’ unaided memories in the development or deployment of the parties’ respective products or services does not create liability under this Agreement or trade secret law, and each party agrees to limit what it discloses to the other accordingly."

Here's another example of residuals language, apparently from some kind of venture-capitalist agreement form, that I must have run across somewhere (I can't remember where and don't have notes):

The Company acknowledges that our and our affiliates' review of Proprietary Information will inevitably enhance our and such affiliates’ knowledge and understanding of the business of the Company in a way that cannot be separated from its other knowledge, and the Company agrees that such knowledge and understanding shall not restrict us or such affiliates in connection with our or their consideration or effectuation of any other investments or our or their serving on the boards of such investments.

Subdivision 2.b — proof problems: Suppose that the Discloser claimed that a Recipient staffer — let's call that person "Rebecca" to keep with the "R" initial — had improperly used Confidential Information, but Rebecca said, goodness gracious, of course I didn't intentionally memorize the information; how could you even suggest such a thing! This might all come down to whether the trier of fact (the judge or jury) believed Rebecca's testimony — and what kind of evidence could the parties put on concerning that issue.

Example: That was a central factual issue in a bitter corporate lawsuit: In a hostile takeover bid, did the prospective acquirer improperly use confidential information about the target, in violation of a previous confidentiality agreement between the parties, or not? Delaware's then-Chancellor Strine concluded that the prospective acquirer had in fact used the confidential information: "Once things are learned and done, it is difficult to unlearn and undo them, especially when the old information is still being circulated." See Martin Marietta Materials, Inc v. Vulcan Materials Co., 56 A.3d 1072, 1098 (Del. Ch.) (Strine, C.), aff'd, 68 A.3d 1208 (Del. 2012) (en banc).

In our above hypothetical, "Robin" might be able to demonstrate unaided retention by reciting or summarizing the information orally, without notes or prompting. The Discloser might be able to refute that testimony could be refuted if someone else personally saw Robin studying the information and committing it to memory.

Subdivision 3 — caution: A broad scope of residuals rights could complicate trade-secret litigation. This seems to have happened in a case involving Google, which was a principal target of claims that the company's "Project Loon" — experimenting with providing wireless Internet service using high-altitude balloons orbiting the Earth — had allegedly misappropriated the trade secrets of another company, Space Data. See Space Data Corp. v. X, No. 16-cv-03260-BLF (N.D. Cal. Jul. 14, 2017): The case reportedly was settled just before trial; see Albarazi (2019) (paywalled).

For a narrow-interpretation approach similar to that of subdivision 3, see section 11.5 on page 44 of this Delta Airlines request for proposal, also posted at the lawyer-only site redline.net. Here's the residuals-interpretation clause:

11.5   Notwithstanding any other provision in this Agreement, Designer shall have the right to retain, use and disclose, without accounting to Owner, any of Designer’s Residual Knowledge.

"Residual Knowledge" shall mean and include information not specifically generated for this Project, such as design details, and the type that Applicable Law would permit an employee of Designer to retain and use in subsequent employment with a third party.

This exception to the obligations of confidentiality and non-use shall be narrowly construed, is intended only to alleviate the possibility of inadvertent breach of this Agreement arising from routine, unaided memory retention by employees of Designer and is not intended to permit Designer to use or disclose information known to Designer to be Work Product or Confidential Information subject to this Agreement.

(Emphasis and extra paragraphing added.)

The Recipient should consider consulting with the Discloser before invoking this Option; this is one of the pick up the phone! opportunities to identify and, ideally, resolve potential disputes as early as possible.

Language sources: Some of the language of this Option was inspired by a residuals clause found "in the wild" by Colorado lawyer Cynthia Abesa; for a couple of other, more-detailed wordings, see a post by Sean Hogle in the same discussion thread at his (highly-recommended) redline.net site for lawyers.

5.3.34. Additional notes for both parties

5.3.34.1. "Trade secrets" vs. "ordinary" Confidential Information

().  In the U.S., a "trade secret" is particular confidential information that derives independent economic value from secrecy; this is provided in both:

In court, the Discloser would likely have to prove the economic value of its alleged trade secrets, and that the value came from the secrecy of the information in question. Example: In one case, the Fourth Circuit held that "part of [the plaintiff's] obligation was to come forward with evidence that its seventy-five alleged trade secrets had value because they remain secret. Proof of value untethered to value derived from secrecy does not show an alleged trade secret’s independent economic value." Synopsys, Inc. v. Risk Based Security, Inc., 70 F. 4th 759, 772 (4th Cir. 2023) (affirming summary judgment in favor of defendant Synopsys) (emphasis in original).

In the U.S., various statutory remedies are available to possessors of "trade secrets" under the laws cited just above.

Drafters should keep in mind that "Confidential Information" can encompass more than just "trade secrets" that provide economic advantage. Example: The Northern District of California noted that "a defendant may breach a contract for disclosing confidential information that does not constitute a trade secret." Albert's Organics, Inc. v. Holzman, 445 F. Supp. 3d 463, 476 (N.D. Cal. 2020) (denying, in part, defendant's motion to dismiss).

Here's an edge case: If information has no economic value unless it becomes public, then the information can't be a trade secret — so held the court in a case where a company tried unsuccessfully to claim trade-secret protection for a contractual addendum (or "rider") that could be added to a standard annuity agreement to provide enhanced wealth-transfer benefits to the purchaser of the annuity. See Novus Group, LLC v. Prudential Financial Inc., 618 F. Supp. 3d 657, 666-67 (D. Ohio 2022) (granting Prudential's motion for summary judgment on Novus Group's trade-secret claim), affirmed on other grounds, 74 F.4th 424 (6th Cir. 2023). The Novus case was decided under Ohio's version of the Uniform Trade Secrets Act, whose definition of "trade secret" is substantially the same as that of the federal Defend Trade Secrets Act.

Tangentially: Two leading IP scholars have argued that "[a] company can 'abandon' its trade secrets by failing to derive economic value from keeping them secret"; in such a case, conceivably information could lose its trade-secret status but still remain Confidential Information. See Camilla A. Hrdy & Mark A. Lemley, Abandoning Trade Secrets, 73 Stanford L. Rev. 1 (2021) (emphasis added).

5.3.34.2. Negative know-how can qualify

Negative know-how can be Confidential Information. The concept was pithily summarized up by legendary inventor Thomas Edison, who is widely quoted as having said, "I have not failed. I've just found 10,000 ways that won't work." That kind of knowledge could have economic value and thus could be a trade secret if maintained in confidence.

But: Negative know-how is one of those areas where proof of secrecy and value of the negative know-how itself will be especially important. Example: A federal district court in New York City observed (arguably in a nonbinding dictum) that "[i]t is difficult to see how negative trade secrets consisting of unsuccessful efforts to develop trade secrets and experimental dead ends can have independent economic value when the end result of the process, the positive trade secrets, have in fact been uncovered." Zirvi v. Flatley, 433 F. Supp 3d 448, 465 (S.D.N.Y. 2020) (dismissing complaint with prejudice) (formatting modified, citations omitted), aff'd by summary order, No. 20-546-cv (2d Cir. Dec. 11, 2020) (affirming on statute-of-limitations grounds).

5.3.34.3. Caution: Always ask for a two-way NDA

Let's return to our course hypothetical where small-company MathWhiz is trying to get a consulting contract from a potential customer, Gigunda: As a big company, Gigunda might want MathWhiz to sign a "one-way" NDA that protects only Gigunda's information. That way, Gigunda wouldn't have to worry about keeping MathWhiz's information confidential. Question: Can the NDA accommodate Gigunda's wish, while still providing at least some protection for MathWhiz? The above language offers one possibility.

In the real world, the NDA likely would indicate which party's or parties' information would be protected. And the NDA might explicitly indicate that MathWhiz's confidential information won't be made available to Gigunda. This could be because MathWhiz wants to be clear that it won't be disclosing its trade secrets to Gigunda (at least not before a deal is signed). But it could also be that Gigunda wants to be clear that Gigunda is not agreeing to be bound by confidentiality obligations for whatever information MathWhiz does provide.

(Caution: By law, each party might still have other confidentiality obligations for information provided by the other party, for example under laws protecting the privacy of personal information or under export-control laws. See the discussions at Protocol 5.6 (privacy) and 31.9 (export controls).)

BUT: Even if MathWhiz and Gigunda originally intended for only Gigunda to disclose its confidential information to MathWhiz, their NDA should preferably still be two-way, not one-way. Here's why:

  • Later, the parties' business people might decide it'd be good for MathWhiz to reveal certain of its own confidential information to Gigunda.
  • And those business people — without checking with "the lawyers" — might well assume, wrongly, that "we have an NDA in place so sure, let's do it."

But that's not OK — at least not from MathWhiz's point of view:

  • The existing, one-way NDA was drafted to protect only Gigunda's information, not MathWhiz's.
  • That, in turn, means that Gigunda has no confidentiality obligations with respect to MathWhiz's information.
  • And so, MathWhiz's unprotected provision of trade secrets to Gigunda will likely destroy MathWhiz's legal rights in those trade secrets. Example: Something close to that actually happened to a recipient in a Seventh Circuit case. See Fail-Safe, LLC v. A.O. Smith Corp., 674 F.3d 889, 893-94 (7th Cir. 2012) (affirming summary judgment for defendant).

To accommodate the above concern, this § 5.3.1 allows for MathWhiz and Gigunda to use a one-way NDA, initially protecting only Gigunda's information, to also protect MathWhiz's information. This provides flexibility for the parties: Assuming that Gigunda did agree to confidentiality obligations for MathWhiz's information, it'd be easy for MathWhiz to get Gigunda to indicate that agreement in writing, e.g., in an email.

And also later, if all else failed, MathWhiz could try to show that the circumstances indicated that Gigunda did in fact consent to receiving MathWhiz's information in confidence; here are two possibilities:

  • The parties' emails, while not explicitly saying, "Gigunda agrees," might still clearly indicate that Gigunda gave such consent;
  • Mary Marvel (MathWhiz's CEO) could email someone in authority at Gigunda to confirm an oral agreement that the NDA would apply to MathWhiz's information, with Gigunda not timely objecting and acting consistently with such an agreement; or
  • Gigunda's oral agreement might be confirmed by some disinterested third party (which seems unlikely).
5.3.34.4. Two-way NDA terms are usually more balanced — but not always

Other things being equal, a supposedly "two-way" agreement, one that applies equally when either party plays a particular role — here, MathWhiz and Gigunda as Disclosers and Recipients — is likely (but not guaranteed) to be more balanced.

But: An agreement that's nominally two-way can still be biased in favor of the drafting party. Example: Suppose that Gigunda's lawyer (i) is doing the drafting, and (ii) knows that Gigunda will be getting access to MathWhiz's confidential information but not the other way around. In that situation:

–  Recipient Gigunda's lawyer might write a nominally two-way confidentiality provision that in fact provides very little protection for discloser MathWhiz's information, because Gigunda's lawyer wants to "win the negotiation" for Gigunda. (This desire to "win" is an occupational hazard for lawyers.)

–  As a result, MathWhiz's lawyer would have to review the confidentiality provisions carefully to make sure it contained sufficient protection for MathWhiz's information.

Conversely, if it's discloser MathWhiz's lawyer who's doing the drafting, then the confidentiality provisions might contain requirements that recipient Gigunda's lawyer would have to review carefully to be sure that the provisions wouldn't impose too much of a burden on Gigunda.

5.3.34.5. Other reading materials

For a quick, checklist-style overview of possible negotiation issues in NDAs, Myron Rabij, NDAs: 10 Key Points & Questions to Consider Ahead of the Deal (JDSupra.com 2023).

See also Protocol 5.2 (business associate agreement) concerning personal health information, commonly referred to as "PHI."

For venture-capital dealings, see Cynthia Abesa's post at the members-only site redline.net: NDAs with VCs for evaluating a potential investment or acquisition (2024).

5.3.35. Additional notes for Disclosers

5.3.35.1. What kinds of confidentiality measures should the Discloser take?
5.3.35.2. Include a "laundry list" of types of Confidential Information?

Some drafters (your author isn't one of them) also like to include a long "laundry list" of specific categories information that can qualify as confidential information. But:

  • There's arguably little need — or none at all — for such a list, given the breadth of the definition of Confidential Information in this Protocol.
  • Including such a list marginally increases the reader's "cognitive burden" (a fancy name for workload) and thus can slow up the contract-negotiation process.
  • From the Discloser's perspective: You wouldn't want the Recipient to try to claim that particular information wasn't in one of the listed categories, and so (the Recipient argues) the information supposedly doesn't qualify as Confidential Information, notwithstanding the "not of limitation" language.

But if you do want such a list, you can get some ideas from the following footnote.15

5.3.35.3. Disclosers: Tell employees about their whistleblower rights — and don't ask them to waive those rights

Section 5.3.26 addresses the Recipient's possible need to disclose Confidential Information in either of the following situations:

  • the disclosure falls in one of the categories of disclosure that is immune from liability under, and/or expressly authorized by, the Defend Trade Secrets Act, Title 18, Section 1833(b) of the United States Code; and/or
  • the disclosure is affirmatively authorized by law or regulation, for example applicable labor- or employment law — including the law in a growing number of states, especially in the wake of the #MeToo movement, as summarized in a 2021 law-firm article. See, e.g., Taylor Bleistein, Doreen Martin, and Keith Olsen, The List of States Regulating Non-Disclosure Provisions Continues to Grow (JDSupra.com 2024).

DCT note: I'm editing this section in February 2025, when it remains to be seen what changes will be needed as a result of the second Trump adminstration's sidelining of the NLRB by firing its chair, other Democratic-appointed member, and general counsel.

Caution: In employment-related agreements, the (U.S.) National Labor Relations Board (NLRB or "Board") has been known to be hostile to NDA-type provisions that could be interpreted as insufficiently explaining to employees their right to engage in concerted action under the National Labor Relations Act, as seen in a 2019 Advice Memorandum from the Board's general counsel, concerning a non-disparagement clause in a law firm's employment agreement. See Advice Memorandum dated Nov. 13, 2019, in Case No. 14-CA-227644, discussed in this law firm memo.

Likewise, the Board has traditionally been hostile to contractual confidentiality restrictions that purport to limit employees' discussions of wages and working conditions. See Nat'l Labor Rel. Bd. v. Long Island Assoc. for AIDS Care, 870 F.3d 82, 88-89 (2d Cir. 2017) (affirming Board ruling).

An undated Board Web page — still on the site at this writing — states:

Under the National Labor Relations Act (NLRA or the Act), employees have the right to communicate with their coworkers about their wages, as well as with labor organizations, worker centers, the media, and the public. Wages are a vital term and condition of employment, and discussions of wages are often preliminary to organizing or other actions for mutual aid or protection. Office of General Counsel, National Labor Relations Board, Your Right to Discuss Wages (NLRB.gov, undated).

And in recent years with Democratic majorities on the NLRB, the Board has taken the position that:

[under] the Board’s recent decision in McLaren Macomb, … the Board returned to longstanding precedent holding that employers violate the National Labor Relations Act when they offer employees severance agreements that require employees to broadly waive their rights under the Act. … [S]everance agreement provisions that could violate the Act if proffered, maintained, or enforced, includ[e] confidentiality, non-disclosure, and non-disparagement, among others. Office of Public Affairs, National Labor Relations Board, NLRB General Counsel Issues Memo with Guidance to Regions on Severance Agreements (NLRB.gov March 22, 2023) (emphasis added).

At least before the second Trump administration came into office, the Federal Trade Commission's antitrust lawyers weren't letting the NLRB have all the fun: In a 2023 announcement, the FTC's Bureau of Competition warned that it regarded confidentiality agreements and employer-notification requirements as "imped[ing] Bureau investigations" and so "are contrary to public policy and therefore unenforceable." The announcement explained:

Although exact terms vary, the following general types of contract provisions can impede Bureau investigations:

  • confidentiality agreements,
  • nondisclosure agreements, and
  • notice-of-agency-contact provisions. …

The exact terms and conditions may vary, but these restrictions and requirements can all have the same chilling effect on individuals’ willingness to speak voluntarily with Bureau staff. That chilling effect impedes the Federal Trade Commission’s ability to carry out its statutory mandate. Federal Trade Commission, Bureau of Competition, Contracts That Impede Bureau of Competition Investigations 1, 2 (FTC.gov June 15, 2023) (extra paragraphing and bullets added).

Restrictions on corporate whistleblowers could attract unwanted attention from the Securities and Exchange Commission: In 2024, the SEC announced that it had settled big-dollar civil claims against Wall Street firms J.P. Morgan, D.E. Shaw, and others (but probably couch change to some of the settling defendants) for entering into agreements that restricted whistleblower claims. See SEC press release 2024-7, J.P. Morgan to Pay $18 Million for Violating Whistleblower Protection Rule (SEC.gov 2024); SEC press release 2023-213, SEC Charges D. E. Shaw with Violating Whistleblower Protection Rule (SEC.gov 2023); see also SEC press release 2024-118 (various public companies agree to pay a total of more than $3 million in civil penalties); Amanda Brown and Heather Raun, SEC implements new level of scrutiny for employment agreements and separation agreements under whistleblower protection rule (EmploymentLawWatch.com 2023).

It might not be enough for a contract to include a disclaimer: In 2023, the SEC also announced that it had settled civil charges against Monolith Resources, LLC for using a form of separation that:

… stated that "nothing in this agreement is intended to limit in any way your right or ability to file a charge or claim with any federal, state, or local agency," but the agreement also took away an employee’s right to recover a monetary award for filing a claim with, or participating in an investigation or action by, a governmental agency.

(Emphasis added.) Without admitting liability, Monolith consented to the entry of a cease-and-desist order and agreed to pay a civil penalty of $225,000.

Note that in the U.S., an online service provider's disclosure of non-content customer information to legal authorities could be immune from liability under 18 U.S.C. § 2703(e) no matter what the contract's confidentiality provisions might say.

5.3.35.4. Pro tip: Asking for an NDA might scare a recipient

Depending on the circumstances, the business benefit of asking another party for an NDA might be outweighed by the risk that the other party might be scared off by the request, out of concern that the NDA would give the first party a weapon with which to sue the other party — triggering the expense and burden of litigation and the risk of making a bad impression on a jury — if the relationship were to go south.

Example: In Celeritas (Fed. Cir. 1998), a federal-court jury in Los Angeles awarded a one-man startup company more than $117 million (in 2025 dollars) against aerospace conglomerate Rockwell International for breaching a confidentiality agreement. The parties had entered into the NDA to discuss a possible royalty-bearing license for data-compression technology for which the man had filed a patent application. Rockwell's position was that the man's innovation consisted of well-known engineering techniques and so royalty payments weren't warranted. The jury didn't buy it; on appeal, the Federal Circuit ruled that the man's patent was indeed invalid in view of the prior art, but the court declined to overturn the jury's finding that Rockwell had breached the NDA. See Celeritas Technologies Ltd. v. Rockwell Int'l, Inc., 150 F.3d 1354, 1359 (Fed. Cir. 1998). Disclosure: I was part of Rockwell's trial team in that case..

This illustrates why big companies are often highly-reluctant to sign NDAs, especially with startups or other smaller companies.

So in terms of "deal psychology," a prospective Discloser's best bet might be to hold off on asking the prospective Recipient sign an NDA, and instead — for the time being — to provide the Recipient only with information that wouldn't seriously harm Discloser if it were to become public or get into the hands of a competitor. That would allow the parties to defer negotiating an NDA until the Recipient had become more comfortable with the idea, and with the Discloser.

5.3.35.5. Special case: Disclosure to venture capitalists, etc.

Amplifying the discussion in 5.3.35.4: Potential investors in a company might be reluctant to sign a nondisclosure agreement ("NDA"). In particular, venture capitalists ("VCs") often flatly refuse to sign NDAs with prospective portfolio companies, because they don't want to risk saying "no" to a company about investing, only to be sued years later for allegedly disclosing the company's technology to someone else.

Of course, it's not as if recipients never, ever acquire confidential information under an NDA and then use the information anyway. Amazon's venture-capital arm supposedly did that to small tech companies DefinedCrowd, LivingSocial, and others, according to press reports. See Dana Mattioli and Cara Lombardo, Amazon Met With Startups About Investing, Then Launched Competing Products (WSJ.com Jul. 23, 2020).

But even so: As a practical matter, going without an NDA with non-corporate venture capitalists might not be a bad bet, because:

  • You can try to be very, very selective about what you disclose without an NDA, so that you're not giving away the "secret sauce" (see § 5.3.14) of your idea.
  • Individual "angel" investors and others generally do have one or two other things on their minds. They generally see lots of entrepreneurs who are convinced they've got a world-beating "unicorn" idea. You'll probably be lucky to get these investors to pay attention for two minutes. Ask yourself how likely it is that they'll want to take your idea and spend time and money building a business without you.
  • Contracts aren't the only thing that discourage bad behavior. If an investor stole someone's idea, and if word got around, then that investor might later find it hard to get other people to talk to him.

You have to decide what risks you want to take. Your business might fail because an investor steals your idea and beats you to market. Or it might fail because you can't raise the money you need to get started.

By analogy: It's sort of like having to take a trip across the country, and you have to decide whether to fly or drive:

  • If you flew, there's a risk you could die in a plane crash flying from one side of the country to the other, and you'd be contributing to greenhouse gases. See, e.g., Mark Miodownik, I Won’t Feel Good About Flying Until the Airlines Solve This (NYTimes.com 2024).
  • But if you were to drive the same route, your risk of dying in a car crash has been estimated as being something like 65 times greater than if you flew — and you'd still be contributing at least somewhat to greenhouse gases, possibly even more so than flying. See, e.g., Climate change: Should you fly, drive or take the train? (BBC.com 2019).

As the old saying goes, you pays your money and you takes your choice.

Pro tip: If your client will be dealing with venture capitalists, you might want to check out the redline.net clauses for VC disclosure.

5.3.35.6. NDA overbreadth could be problematic

In a case under Puerto Rican law, the First Circuit cited prior decisions from the mainland United States holding that "overly broad confidentiality agreements constitute unreasonable restraints on trade which unduly restrict the free flow of information necessary for business competition and are thus unenforceable." TLS Mgmt. & Marketing Serv., LLC v. Rodriguez-Toledo, 966 F.3d 46, 57-60 (1st Cir. 2020) (reversing judgment in favor of former employer) (cleaned up).

5.3.36. Additional notes for Recipients

5.3.36.1. Recipient Best-Practice #1: Be choosy

When dealing with other parties in contract situations, you'd be well-advised to be choosy about accepting the other party's confidential information — and to consider using "protection" in the form of a confidentiality agreement that includes appropriate exclusions such as those in Protocol 5.3.

Example: It can be dangerous to acquire confidential information of a competitor, for example in merger negotiations, even under a confidentiality agreement ("NDA"). That's because if a deal doesn't come to pass, the "owner" of the confidential information might later claim that the recipient made improper use of the target company's confidential information. Something like this happened in a 2021 Ninth Circuit case in which Facebook was caught in the middle. See BladeRoom Grp. Ltd. v. Emerson Elec. Co., 20 F.4th 1231 (9th Cir. 2021).

See also the discussion at 5.3.35.4 of the Celeritas v. Rockwell case, where a one-man startup company scored a $117 million verdict (in 2025 dollars) against a defense contractor.

5.3.36.2. Use a nonconfidentiality agreement?

A prospective Recipient might want to ask the Discloser to enter into a nonconfidentiality agreement that states explicitly that the Recipient has no confidentiality obligations concerning the Discloser's information. For years, toy companies and car companies have required "off the street" submitters of ideas to sign such agreements; see, e.g., section 7 of Mattel's Web terms of service.

5.3.36.3. Publication destroys confidentiality

().  Publication — of which patenting is one form — is one way in which allegedly-confidential information can be conclusively disqualified from confidentiality status. As the SDNY noted: "It is axiomatic that a plaintiff cannot recover for the misappropriation of a trade secret if he revealed that secret in a published patent or patent application." Broker Genius, Inc. v. Zalta, 280 F. Supp. 3d 495, 518 (S.D.N.Y. 2017) (citations omitted); DVD Copy Control Ass'n Inc. v. Bunner, 116 Cal. App. 4th 241, 10 Cal. Rptr. 3d 185, 194 (2004) (information about DVD content scrambling, widely published on the Internet).

Likewise, when computer-program source code is part of a U.S. copyright registration filing, the code (generally) is publicly available from the Copyright Office and so cannot be a trade secret. See Capricorn Mgmt. Sys., Inc. v. GEICO, No. 15-CV-2926, slip op. at part IV.B (E.D.N.Y. Mar. 16, 2020).

Example: A Taiwanese machine-tools manufacturer sued its former U.S. distributor for allegedly misappropriating the manufacturer's trade secrets. The manufacturer, as part of its legal strategy, registered more than 20 technical drawings with the U.S. Copyright Office — without redacting (blacking out) any parts of the drawings. The court had no difficulty concluding that by doing so, the manufacturer had "extinguished" any trade-secret rights it had in the content of the drawings. See Sysco Machinery Corp. v. DCS USA Corp., No. 24-1675, slip op. at 3, 8-9 (4th Cir. 2025) (affirming dismissal of trade-secret claim for failure to state a claim upon which relief can be granted).

(The court also rejected the manufacturer's claim that manufacturing

5.3.36.4. But: "Publication" might be field-specific.

The fact that information is included in a publication known to those who work in one particular field won't necessarily destroy the information's trade-secret status in "an entirely different field from the one to which the publication was addressed." Masimo Corp. v. True Wearables, Inc., No. 2021-2146, slip op. at part II.A (Fed. Cir. Jan. 24, 2022) (nonprecedential; affirming preliminary injunction against former employee of plaintiff and his new company) (emphasis added).

5.3.36.5. Exclusion of "readily-ascertainable" information — what could qualify?

().  It can be challenging — read: costly — to litigate the fact-specific question whether particular information does or doesn't qualify as "readily ascertainable." Here are some cases in which parties had to (expensively) litigate whether particular allegedly-trade-secret information was "readily ascertainable" and therefore ineligible for legal protection:

Example: A federal appeals court threw out a $22 million jury verdict against cosmetics giant L'Oréal for "willful or malicious" misappropriation of an alleged trade secret (involving the use of maleic acid during bleaching) because the purported trade secret wasn't eligible to be treated as such, as the information was "readily ascertainable by proper means" in a number of previously-issued patents and published patent applications. See Olaplex, Inc. v. L’Oréal USA, Inc., No. 20-1382, part III.A.1, slip op. at 10-14 (Fed. Cir. May 6, 2021) (reversing denial of judgment as a matter of law as to trade-secret misappropriation) (non-precedential).

Example: A New York appeals court held that "to the extent the features identified by plaintiffs were readily ascertainable from the publicly-available Rendezvoo website, they are not protectable trade secrets." Schroeder v. Pinterest Inc., 133 A.D.3d 12, 29, 17 N.Y.S.3d 678, 2015 NY Slip Op 07232 (N.Y. App. Div. 2015) (citations omitted).

Example: A federal appeals court ruled that, under Texas law, a discloser's information lost its trade-secret status because the information had become readily ascertainable through reverse engineering of the discloser's publicly-released; this was true even though the receipient had not itself reverse-engineered the product. See ams-OSRAM USA Inc. v. Renesas Electrs. America, Inc., 133 F.4th 1337, 1347-48 (Fed. Cir. 2025) (reversing district court's finding about the date that a particular trade secret had become readily ascertainable). (Hat tip: Cynthia Abesa.)

Counterexample: A jury didn't buy a defendant's argument that particular alleged trade secrets were "public or general knowledge in the industry." See Harbor Business Compliance Corp v. Firstbase IO Inc., 152 F.4th 516, 530-31 (3d Cir. 2025).

"Improper means"? The federal Defend Trade Secrets Act gives examples of improper means (at 18 U.S.C. § 1839(6), concerning "readily ascertainable") as "(A) includ[ing] theft, bribery, misrepresentation, breach or inducement of a breach of a duty to maintain secrecy, or espionage through electronic or other means; and (B) does not include reverse engineering, independent derivation, or any other lawful means of acquisition[.]"

For a head-scratching outlier example of what one court said was improper means, see the discussion at Note of the Fifth Circuit's Christopher case, where the court affirmed a ruling that DuPont could sue photographers who'd been hired, by an unknown party, to overfly — in public, unrestricted airspace — and photograph a chemical-plan site that was under construction site.

Probably to the regret of businesses, the Act doesn't seem to provide any "safe harbors" for proper means. But the U.S. Supreme Court commented, in the (IP-)famous 1974 Kewanee Oil case, that "a trade secret law … does not offer protection against discovery by fair and honest means, such as by independent invention, accidental disclosure, or by so-called reverse engineering …." Kewanee Oil Co. v. Bicron Corp., 416 U.S. 470, 476 (1974). (Emphasis added.) For more on reverse engineering, see generally 31.31.

5.3.36.6. Would breach of a confidentiality agreement be considered "improper means" of acquiring a trade secret?

Under subdivision (6)(B) of 18 U.S.C. § 1839, "breach … of a duty to maintain secrecy" is one form of "improper means" of ascertaining a trade secret — but the answer under state law might be different (or might not be), as addressed in several court cases.

Example: A Texas appellate court held that under Texas law, "[a] post-acquisition breach of a confidentiality or nondisclosure agreement … cannot support an improper means finding as a matter of law." Title Source, Inc. v. HouseCanary, Inc., 612 S.W.3d 517, 531 (Tex. App. San Antonio 2020, pet. denied) (reversing, in part, judgment on jury verdict of trade-secret misappropriation; cleaned up, emphasis added).

But then two weeks later, the Fifth Circuit held (in an unpublished opinion) that under Texas law, "a breach of a duty to maintain secrecy is a way of establishing improper means …." Hoover Panel Systems, Inc. v. HAT Contract, Inc., No. 19-10650, part II (5th Cir. June 17, 2020) (per curiam, unpublished: reversing and remanding summary judgment in favor of accused misappropriator; emphasis added, citations omitted).

An attorney points out that the Fifth Circuit's Hoover Panel holding "raises a potential Erie concern," in that federal courts sitting in diversity (i.e., the Fifth Circuit) are supposed to apply state law as interpreted by state courts. Paul Devinsky, Improper Use of Voluntarily Communicated Trade Secrets Sufficient to Maintain Action for Misappropriation in Texas (IPUpdate.com Jul. 1, 2020).

5.3.36.7. Pro tip: Seek and save corroborating evidence of independent possession!

When a Recipient gets sued for misappropriating Confidential Information, one standard Recipient defense is to claim, "Oh, well, we already knew that information!" or "Well, yeah, we learned that from the Discloser, but we developed our own version!" Juries can be skeptical of such claims, to the point of rejecting them altogether.

Example: A federal-court jury awarded a software vendor $152 million because the defendant — one of the vendor's customers — had helped a vendor competitor to reverse-engineer the vendor's software product, which violated of the software's license agreement. The jury evidently didn't believe the vendor competitor's claim that it had developed its own software without using the vendor's trade secrets. See ResMan, LLC v. Karya Prop. Mgmt. LLC, No. 4:19-CV-00402, slip op. (E.D. Tex. Aug. 5, 2021) (final judgment) (reducing damage award to $62.5 millon to eliminate duplicate recoveries); Natalie Posgate, Two Houston companies hit with $152 million verdict in intellectual property case (HoustonChronicle.com Mar. 19, 2021); Blake Brittain, ResMan ends up with $62 mln in trade-secret win after $152 mln verdict (Reuters.com Aug. 13, 2021).

Example: A jury evidently didn't believe a recipient's claim of having independently developed information about "sweet spots" in oil and gas reservoirs; the jury awarded the discloser more than $40 million. See S.W. Energy v. Berry-Helfand , 491 S.W.3d 699, 708 (Tex. 2016). On appeal, the damages award was vacated and remanded for a new trial; in an SEC filing in February 2017, the recipient disclosed that the parties had settled on a confidential basis.

Example: A federal-court jury in Los Angeles awarded a one-man startup company more than $117 million (in 2025 dollars) because the jury found that defense contractor Rockwell had breached a confidentiality agreement with the startup company. Rockwell insisted that its engineers had independently developed the technology in question, but post-trial juror interviews confirmed that the jurors simply didn't buy Rockwell's story. See Celeritas Technologies Ltd. v. Rockwell Int'l, Inc., 150 F.3d 1354, 1359 (Fed. Cir. 1998). DCT note: I was part of Rockwell's trial team in that case.

Example: A company (the "customer") engaged another company (the "vendor") to produce "white label" business-compliance software for the customer to use with its own customers. Disputes arose about the scope of the project; eventually the customer ditched the vendor and soon came out with its own software. Unhappy with events, the vendor sued the customer for misappropriation of the vendor's trade secrets; the customer responded that it had developed the information itself, but the jury didn't buy it, awarding the developer some $25 million in damages. See Harbor Business Compliance Corp v. Firstbase IO Inc., 152 F.4th 516 (3d Cir. 2025). The appeals court affirmed the liability judgment but held that the $25 million damage award had to be reduced by $11 million because it double-counted the disgorgement of the defendant's profits. See id. at 535-37.

Lesson: Recipients of allegedly-confidential information should plan to document independent possession of the information:

  • by preserving documentary evidence of having received the information from another source; and
  • by using "clean room" techniques to document independent development of the information.

To help prove prior knowledge of information, the Recipient should consider notifying the Discloser — promptly and in writing — if the Discloser provides the Recipient with information that the Recipient already knew. (This might be overly burdensome on the business, though.)

But: The Recipient probably should push back against any request by the Discloser to make such notification a contractual requirement. Example: In a New York federal-court case, the parties' contract included such a notification requirement, but the recipient didn't comply with the requirement; that contributed to the court's denial of the recipient's motion for summary judgment. See Structured Capital Solutions v. Commerzbank AG, 177 F. Supp. 3d 816, 831 (S.D.N.Y. 2016) (Rakoff, J.).

5.3.36.8. Pro tip: Write up an "invention disclosure" beforehand?

Pro tip: Before agreeing to receive confidential information, the Recipient could consider getting its relevant engineers, etc., together to write up internal "invention disclosure statements" to document their existing knowledge of projects in the works. (Hat tip: Dr. Louise Levien.)

5.3.36.9. Or: Just defer discussion of confidential information?

As a negotiation possibility, a prospective Recipient could consider asking Discloser to agree to defer — for the time being — giving Recipient access to confidential information, with the understanding that later the parties could revisit the question.

5.3.36.10. The tension in excluding acquired "general knowledge and skills"
5.3.36.11. Push back against requests for individual employee NDAs?

In some cases, a Discloser might try to demand that each Recipient employee, etc., must personally sign an individual confidentiality agreement with the Discloser (see the optional clause language at Protocol) — thus exposing the employee to personally being sued by the Discloser merely for doing his- or her job.

(If a Recipient's counsel rejects such a Discloser demand, at least for routine matters the Discloser often won't push the point.)

Why might this be important? Because:

1.  Lawsuit plaintiffs will sometimes sue defendants' employees individually, perhaps to try to muscle the employees into cooperating against their employers, e.g., in discovery matters.

Example: The State of Oregon once sued Oracle over alleged problems in implementing the state's Obamacare exchange system; the state sued not just Oracle itself, but also various Oracle employees personally — including a demand that an Oracle technical manager personally pay the state $45 million (!).(17.6)

2.  The Recipient likely will not want its employees to feel conflicted about their obligations to the Recipient, versus their personal exposure to possible liability from a lawsuit by the Discloser.

5.3.36.12. Might the Recipient someday want to publicly file Discloser Confidential Information?

If a Recipient public filing might require disclosure of Discloser Confidential Information, then the Recipient might want to propose including, in the Con­tract, the public-filings protocol at Option 5.3.33.4.

5.3.36.13. Push back against a return-or-destroy requirement?

See the commentary to Information Purge Protocol (5.4).

5.3.36.14. Danger: Noncompetition provisions in NDAs

Example: A UK lawyer signed a confidentiality agreement relating to a group of law firms' representation of plaintiffs in the Volkswagen "Dieselgate" engine emissions matter. The NDA included what amounted to a noncompetition covenant (concerning which, see generally 22.5), which barred the lawyer's firm from representing other plaintiffs in the matter for six years. The UK Supreme Court affirmed enforcement of the noncompete. See Harcus Sinclair LLP v. Your Lawyers Ltd. [2021] UKSC 32.

Note: In the U.S., such a lawyer- and law-firm noncompetition covenant might well be unenforceable as violating the clients' right to choose their counsel. See American Bar Association, Model Rules of Professional Conduct 5.6: "A lawyer shall not participate in offering or making: (a) a partnership, shareholders, operating, employment, or other similar type of agreement that restricts the right of a lawyer to practice after termination of the relationship, except an agreement concerning benefits upon retirement …."

Example: A California appeals court ruled that a confidentiality clause in an employment agreement was so broad as to amount to a noncompetition clause (concerning which, see 22.5) and therefore was unenforceable. See Brown v. TGS Mgmt. Co., LLC, 57 Cal. App. 5th 303, 317–20, 271 Cal. Rptr. 3d 303 (Cal. App. 2020) (reversing confirmation of arbitration award).

5.3.36.15. Danger: Invention-assignment provisions

Example: A Stanford University researcher was sent to get training from a colleague at an outside company, Cetus (later acquired by Roche). The Stanford researcher signed a "Visitor Confidentiality Agreement" that assigned, to Cetus, the researcher's future rights in any inventions developed as a consequence of the researcher's work at the outside company. As a result, Stanford found itself having to share ownership of a patent — one that evidently was important enough to litigate all the way to the U.S. Supreme Court (on a tangential issue). See Bd. of Trs. of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 583 F.3d 832 (Fed. Cir. 2009), aff'd as to a tangential issue, 563 U.S. 776, 131 S. Ct. 2188, 2194-95 (2011).

(That case is also discussed at 23.6.1.9 concerning the difference between a "present assignment" of future IP rights and an agreement to assign such rights in the future.)

5.3.36.16. Danger: Employee nonsolicitation provisions

It's not unheard of for an NDA to state that the Recipient must not try to "poach" any Discloser employee; see 17.9 for more details and cautions.

5.4. Information Purge Protocol

Possessors of information "owned" by another party should think carefully before agreeing to return or destroy the information, such as at Protocol 5.3.32.1 (return of confidential information), not least because purging can be costly and time-consuming.

Contents:

5.4.1. Applicability of this Protocol

All parties: When the Con­tract includes this Protocol, it will govern in any situation in which, under the Con­tract, a party indicated in the Con­tract (the "Possessor") is to return or destroy particular information of another indicated party (the "Owner").

Comment

().  This Protocol might be used as part of a confidentiality agreement, in which at some point in time a recipient must purge the discloser's information from the recipient's electronic- and hard-copy files. See, for example: • 5.3 (confidential information) and • 5.2 (Business Associate Agreement).

Caution: Possessors should think carefully before agreeing to return or destroy information they receive, for reasons discussed at 5.4.14.

5.4.2. Defininition: "Purge" (of information) requires commercially-reasonable efforts

Possessor: For purposes of this Protocol, when you're required to "Purge" information, it means that you're to promptly make commercially-reasonable efforts to return or destroy all Target Materials in your possession, custody, or control — except as otherwise provided in this Protocol.

Comment

().  Concerning "possession, custody, or control," see 20.30.

Under this Protocol, it's not an absolute requirement for the Possessor return or destroy Target Materials, because that could be burdensome and costly for the Possessor. But in some cases, the Possessor might consider it an acceptable business risk to agree to an absolute requirement — the thinking could be that, if the Possessor were to miss returning or destroying a copy, the Owner's resulting damages might be minimal. (DCT note: I've had clients decide that this was the case.)

Caution: If the Possessor did agree to an absolute requirement, but then failed to comply with it, then that failure could give the Owner a cudgel with which to bash the Possessor as a scofflaw.

Pro tip: The Possessor might want to consider segregating Target Materials to reduce the burden and expense of compliance with a purge obligation — and the Owner might even want to propose requiring such segregation, possibly using Option 5.3.32.7. take the steps described in this Protocol to return or destroy all copies and other tangible embodiments ("Target Materials") of the information in your possession, custody, or control.

5.4.3. Purging is required upon written request (with a deadline)

Possessor: Purge information if:

  1. the Owner, in writing, asks you to do so;
  2. any other Purge prerequisites in the Con­tract are satisfied; and
  3. you receive (or refuse) the Owner's Purge request no later than 30 days after termination or expiration of the Con­tract.
Comment

().  Subdivision 1: This section follows the R.O.O.M. Principle: Root Out Opportunities for Mistakes (or, Misunderstandings). Without an upon-request feature, the Possessor's busy people could easily forget (or never be aware in the first place) that the Possessor was contractually obligated to purge information. This could harm not just the possessor but the owner as well:

  • If the possessor were to forget to comply with the return-or-destruction obligations, then the owner might use that fact to bash the possessor as a scofflaw in front of a judge or jury — this seems to have been a factor in the Federal Circuit's 2020 SiOnyx decision.16
  • On the other hand, suppose that the owner were to fail to follow up to confirm the possessor's return or destruction of the information (e.g., by failing to ask for a certificate of return or destruction). A third party, learning about that failure, might try to use the owner's failure to support an argument that the owner had failed to take reasonable precautions to preserve the secrecy of its information — and thus that the information had lost its confidentiality status.

    Subdivision 2: Prerequisites for Purging might include, for example, achievement of certain milestones in the parties' transaction or relationship.

    Subdivision 3: This section also follows the Sunset Principle: It's always a good idea for a contract drafter to consider whether particular rights and/or obligations should come to an end.

5.4.4. Exception: Electronic materials

Possessor: You don't have to return or destroy electronic Target Materials.

Comment

().  In many situations, a blanket obligation to return or destroy documents might not be practical, especially where electronic information is concerned.

Consider, for example, the problem of litigation discovery of electronically-stored information, or "ESI": Anyone who has gone through that process can attest to the burden and expense of even just identifying the information that might need to be returned or destroyed.

Moreover, the inconvenience and expense of purging that information from the Possessor's electronic data systems would be even worse.

5.4.5. Exception: Emails and other messages

Possessor: Except as otherwise provided in this Protocol, you don't have to destroy emails, text messages, and similar messages containing Target Materials.

Comment

This exception is provided because in the modern era, emails and other messages provide a paper trail of parties' dealings — which can serve as vital evidence in disputes. Moreover, attempting to surgically delete Target Materials from such messages would usually be costly, impracticable, and even impossible.

5.4.6. Exception: System backups can be (securely) maintained as usual

Possessor: Except as otherwise provided in this Protocol, you don't have to destroy system-backup copies containing Target Materials, created as part of your commercially-reasonable regular IT practices — but those IT practices must include secrecy measures comparable to those required by the Con­tract (with appropriate adjustments for the circumstances).

Comment

This exception is provided because finding and identifying electronically-stored documents can be burdensome and costly — as can be attested by anyone who has gone through litigation discovery of electronically-stored information, or "ESI."

5.4.7. Exception: Archive copies can be kept (securely)

Possessor: Except as otherwise provided in this Protocol, you don't have to purge archive copies containing Target Materials — but those copies must be retained in strict confidence and used only for archival purposes as set out in Protocol 5.1.

Comment

The Possessor will likely want to retain — and perhaps should try to insist on retaining — archive copies of Target Materials. That's because the Possessor might someday want to be able to check its archive copies to confirm — or refute — later claims by the Discloser that the Possessor was misappropriating information that allegedly had been provided to the Possessor by the Discloser; just such a situation arose in Healthcare Resources, a Florida federal-court case.17

5.4.8. Owner personnel can't use the above exceptions

Possessor:

  1. The above exceptions to this Protocol's purge requirements don't apply — other than as stated at subdivision 2 below — if you're an employee or individual contractor of the Owner.
  2. But: Even you're an employee or contractor of the Owner, you don't need to purge Target Materials that are retained solely for the purpose of:
    1. reasonably-anticipated disclosure permitted by law under § 5.3.26, and/or
    2. responding to a then-pending compulsory legal process under § 5.3.22, of Protocol 5.3.
Comment

An employee (or individual contractor) might be obligated by an employment agreement or company policy: (1) to turn in all company computers, phones, tablets, and other devices upon termination of employment; and/or (2) to purge company information from the employee's personal devices.

5.4.9. Continued obligations remain for retained materials

Possessor: Continue to comply with the obligations of the Con­tract — e.g., confidentiality obligations, if applicable — for any copies or other embodiments of Target Materials that aren't purged, until such time (if any) as those obligations no longer apply.

Comment

Confidentiality obligations could expire with the passage of time; see § 5.3.5.

5.4.10. Upon request: Certify compliance

Possessor: If the Owner so requests in writing within a reasonable time after the return-or-destruction request, THEN: Promptly provide the Owner with a written certificate of your compliance with this Protocol — noting any known areas of noncompliance.

Comment

Caution: This certification requirement could be dangerous to the Possessor: Suppose that it later turned out that the Possessor didn't completely return or destroy Target Materials: That fact could later help persuade a jury that the Possessor misappropriated the confidential information by secretly using it after having supposedly returned it.

–  Example: In Southwest Energy, a 2016 Texas case that ended up at the state's supreme court, a jury awarded $53 million (in 2025 dollars) to a discloser of confidential information — likely in part because one representative of the recipient had retained copies of some of the information despite a return-or-destroy NDA requirement and the recipient's assurance that the recipient had complied with the requirement.18

–  Example: In another case, a long-running lawsuit in Texas was motivated in part by a return certificate that had been signed by a recipient of confidential information signed.19

5.4.11. Check before destroying copies?

Possessor:

  1. You should consider advising the Owner, in writing and in advance, if you plan to destroy "hard copies" (e.g., printouts) of Target Materials to be Purged.
  2. But you don't have to turn over hard copies of Target Materials unless you and the Owner have clearly agreed otherwise — for example by agreeing to Option 5.4.12 below.
Comment

This to be neighborly is in case the Owner doesn't have its own copies of Target Materials and would like to have the Possessor's copies that would otherwise be destroyed. It also fits into the general "Pick up the phone!" motif of this book.

5.4.12. Opt-In: Mandatory Check Before Destruction

This Opt-In will apply only if clearly agreed to in writing.

Possessor:

  1. Make reasonable efforts to advise the Owner, in advance and in writing — it could be by email, for example — that you intend to destroy hard copies of Target Materials, e.g., printouts, etc.
  2. Don't destroy any such hard copies unless:
    1. the Owner indicates in writing that the Owner doesn't need the copies in question; or
    2. the Owner doesn't respond to your advice (see subdivision 2) on or before the date ten business days after: (i) the Owner receives or refuses that advice, or (ii) when your reasonable efforts to advise the Owner are unsuccessful.
  3. If the Owner asks: Turn over those hard copies to the Owner, at no charge (but you're free to require the Owner to pay, or reimburse you, for reasonable out-of-pocket charges for shipping and/or insurance, and to hold off on the turnover until the Owner does so).
Comment

This Opt-In makes mandatory the "good neighbor" encouragement above, but only as to "hard copies," not electronic copies.

(But a good-neighbor Possessor would be willing to discuss the latter with the Owner.)

5.4.13. Opt-In: Written Purge Certification Upon Request

Possessor:

  1. This Opt-In will apply only if clearly agreed to in writing and the Owner asks in writing — within a reasonable time after the Purge requirement of this Protocol has become applicable — for you to certify that you've complied with the Purge requirement.
  2. Make a reasonable inquiry to check how well you've complied with the Purge requirement.
  3. Provide the Owner with a written certificate of compliance that:
    1. notes any known compliance exceptions;
    2. notes whether and how each exception is authorized by the Con­tract — unless doing so is prohibited by applicable law or otherwise authorized by the Con­tract, for example if the Possessor provided copies to one or more law-enforcement authorities that have requested that the Owner not be told;
    3. is signed (possibly electronically) by someone having authority to make a binding commitment on behalf of the Possessor (or by the Possessor him- or herself if an individual).
  4. You should consider:
    1. circulating the draft certificate to your relevant people for their review; and
    2. sending an unsigned draft of the certificate to the Owner for possible feedback.
5.4.13.1. Comment

().  This Opt-In has several benefits — mainly for the Owner: It makes it easier for the Owner to manage its contract rights; it gives the Possessor an incentive to do a good job in complying with the return-or-destruction requirement; and it helps the parties — before a dispute arises — to identify specific areas that might need attention, and thus possibly help to avoid the dispute in the first place.

But: A certification requirement would also give the Owner ammunition to blast the Possessor with a "they lied!" accusation, if it turned out that Possessor had overlooked returning or destroying some specimens of the Owner's information.

5.4.14. Additional notes

5.4.14.1. The law might require the possessor to keep copies

Suppose that the possessor created the documents in question for the owner. In that situation, the possessor might want — or even be legally required — to maintain its own records of what it created.

5.5. Privacy Commitment (by Customer) Protocol

5.5.1. Lighthouse Protocol

5.5.1.1. Applicability

When agreed to, this Protocol sets forth actions taken by a party indicated in the Con­tract (the "Customer") as being a customer of services or technology of another party (the "Provider").

Note

Providers of "software as a service" ("SaaS") sometimes want clauses like this in their contracts, such as at section 3.4 of the SalesForce.com Main Services Agreement.

5.5.1.2. Customer's compliance obligation

Customer:

  1. Comply with any data privacy laws that are relevant to your activities under the Con­tract.
  2. For this purpose, the term data privacy law includes, without limitation, obtaining any consents that might be needed for you to manage personal data, to the extent that any such consent is required by law.
Note

See the (relatively-short) discussion of privacy laws at 5.6 and its commentary.

5.5.1.3. Possible registration- and/or fees compliance

Customer: When required by law, do related things (at your own expense) such as, for example:

  1. registering as a "data controller" with a local privacy data office; and/or
  2. paying a related fee.
Note

For a discussion of the effect of an acknowledgement, see 11.2 and its commentary.

5.5.1.4. Consent to certain Provider data activities

Customer: The Provider may collect, store, and use personal data of your people as stated in the Provider's privacy policy.

5.5.1.5. Responsibility for "external" privacy paperwork

Customer: As between you and the Provider, you're responsible for any "external" privacy paperwork associated with your access to personal data, such as (for example) registration of any data controller(s) (if any) that you engage to handle particular matters.

Note

Concerning the "As between …" language, see 32.4.

5.6. Privacy Law Definition

5.6.1. Lighthouse Protocol

5.6.1.1. Definition

In this Protocol, the term "Privacy Law" is treated as referring to any applicable law concerning the privacy, security, or processing of personal information — including without limitation the law in jurisdictions where personal information was collected.

5.6.2. Additional notes

5.6.2.1. The business context

Privacy law is increasingly important in the age of e-commerce; contracting parties are well-advised to become familiar with those laws and/or to engage counsel experienced in that field.

Students: You're expected to know that privacy law is most definitely "a thing" — and in many jurisdictions, one with big, sharp teeth in the form of large fines for violation, and possibly even criminal penalties. See, e.g.: • Ryan Browne, Europe’s privacy overhaul has led to $126 million in fines — but regulators are just getting started (CNBC.com Jan. 19, 2020); • Federal Trade Commission, FTC Imposes $5 Billion Penalty and Sweeping New Privacy Restrictions on Facebook (FTC.gov Jul. 24, 2019); • Adam Satariano, Google Is Fined $57 Million Under Europe’s Data Privacy Law, New York Times, Jan. 21, 2019.]

For a list of privacy laws, see 5.6.2.3. Caution: The list might well be out of date already — businesses should check with experienced counsel.

5.6.2.2. Appendix: Prerequisites for collecting personal information?

Caution: When a company (a "Collector") collects personal information of an individual, applicable privacy laws might require the Collector to do some or all of the following:

  1. disclose to the individual:
    • what types of information the Collector collects;
    • what the Collector might do with the information;
    • how long the Collector might keep the information;
    • whether the Collector will sell the information to others;
  2. take reasonable security measures to protect the information;
  3. alert the individual in cases of security breach (actual or, sometimes, potential)
  4. report security breaches to government authorities;
  5. purge the information upon request (the "right to be forgotten")
5.6.2.3. Appendix: Selected privacy laws

The giant global law firm DLA Piper maintains an online handbook and downloadable PDF, Data Protection Laws of the World, at Data Protection Laws of the World.

The following list is adapted from an underwriting agreement filed with the SEC effective Aug. 5, 2020, with a Form 8-K report by a company named "1847 Goedeker Inc."

Caution: The law in this area is evolving rapidly, so readers should definitely consult experienced counsel.

Privacy Laws include, for example, the following:

  • the California Consumer Privacy Act of 2018 ("CCPA") and the California Privacy Rights Act ballot initiative of 2020 (a.k.a. Proposition 24); see also California Privacy Protection Agency, [Proposed] California Consumer Privacy Act Regulations (CCPA.CA.gov 2022);
  • the Children’s Online Privacy Protection Act ("COPPA");
  • the Computer Fraud and Abuse Act ("CFAA");
  • the Controlling the Assault of Non-Solicited Pornography and Marketing Act of 2003 ("CAN-SPAM Act");
  • the Electronic Communications Privacy Act;
  • the European General Data Protection Regulation ("GDPR");
  • the Fair Credit Reporting Act ("FCRA");
  • the Fair and Accurate Credit Transaction Act ("FACTA");
  • the Family Educational Rights and Privacy Act ("FERPA");
  • the Federal Trade Commission Act;
  • the Gramm-Leach-Bliley Act ("GLBA");
  • the Health Insurance Portability and Accountability Act of 1996 ("HIPAA"), as amended and supplemented by the Health Information Technology for Economic and Clinical Health Act ("HITECH Act") of the American Recovery and Reinvestment Act of 2009;
  • the Telemarketing and Consumer Fraud and Abuse Prevention Act (TCFAP");
  • the Telephone Consumer Protection Act ("TCPA").

5.7. Recordkeeping Protocol

5.7.1. Parties: Recordkeeper and Beneficiary.

  1. When parties agree to this Protocol, they are to proceed as stated here when a party clearly identified in the Con­tract (the "Rec­ord­keep­er") is to cause records to be kept to document, for example:
    1. the Rec­ord­keep­er's performance under the Con­tract,
    2. to the extent applicable, the rights, under the Con­tract, of another party (the "Beneficiary").
  2. The records required under subdivision a are referred to here as "Records."

5.7.2. Required Records; standards.

The Rec­ord­keep­er must cause all Records:

  1. to comply with commercially-reasonable standards for the nature of the Records in question; and
  2. to be complete and accurate in all material respects.
Note

().  Subdivision 1: Depending on the type of Records, "commercially-reasonable standards" might encompass professional- or industry standards.

Subdivision 2: Some drafters require records to be "true and correct," but that seems both redundant and incomplete; see the further discussion of this subject at 32.38.

5.7.3. Required Record-creation period [FIX] must be created during the term of the Con­tract.

The Rec­ord­keep­er will cause Records to be created during the specified time period.

5.7.4. Required Record-preservation period.

The Rec­ord­keep­er is to cause all Records to be preserved:

  1. as required by law; and
  2. if longer: until the completion of any timely-commenced audit.
Note

See the additional discussion at 31.30.3. • See also Protocol 4.3.

5.7.5. Required related reports?

This Protocol may address whether the Rec­ord­keep­er is required to make reports relating to Records or their contents.

Note

See generally 31.30 for possible reporting requirements.

6. Pricing

6.1. Consumer Price Index (CPI) Definition

Unless clearly agreed otherwise, "Consumer Price Index" and "CPI" each refer to the All Items Consumer Price Index — All Urban Consumers ("CPI-U"), as published from time to time by U.S. Bureau of Labor Statistics.

Note

().  Background: The problem of multiple CPIs. Some contracts include inflation-adjustment clauses that lock in agreed pricing levels for a specified time period — but allowing the vendor to increase pricing by no more than X% per year (let's say) or by the corresponding increase in CPI, whichever is greater (or sometimes, whichever is less).

The problem is, there are multiple "CPIs"; sometimes, after the contract is signed, the parties could disagree about which CPI should be used. Depending on the purpose of the inflation adjustment, the CPI-U measure might or might not be the best specific index to use; see the commentary below for other possibilities.

For convenience and certainty, when a contract just says (for example) "price increases no greater than CPI," this Protocol specifies one of them as the "default" adjustment index.

There are also other inflation adjustment indexes such as, for example:

  • CPI-W, Consumer Price Index for Urban Wage Earners and Clerical Workers;
  • Regional CPIs;
  • other specialty CPIs for, e.g., airline fares; college tuition; household energy; medical care; motor fuel; used cars and trucks; and others.

    Which index to use? As explained in a FAQ page of the Bureau of Labor Statistics (archived version of question 15, now listed under "Is the CPI the best measure of inflation?"):

Various indexes have been devised to measure different aspects of inflation. Inflation has been defined as a process of continuously rising prices or, equivalently, of a continuously falling value of money.

  • The CPI measures inflation as experienced by consumers in their day-to-day living expenses;
  • the Producer Price Index (PPI) measures inflation at earlier stages of the production process;
  • the International Price Program (IPP) measures inflation for imports and exports;
  • the Employment Cost Index (ECI) measus inflation in the labor market; and
  • the Gross Domestic Product (GDP) Deflator measures inflation experienced by both consumers themselves as well as governments and other institutions providing goods and services to consumers.

There are also specialized measures, such as measures of interest rates. The "best" measure of inflation depends on the intended use of the data. The CPI is generally the best measure for adjusting payments to consumers when the intent is to allow consumers to purchase at today's prices, a market basket of goods and services equivalent to one that they could purchase in an earlier period.

(Emphasis, extra paragraphing, and bullets added.)

6.2. Pricing Adjustments Protocol

When a prospective customer enters into an ongoing master purchase agreement with a vendor, the customer often wants the vendor to agree to limit how much the vendor can increase its pricing. This often requires more than a little negotiation — for example, of customer concessions such as:

  • committing to a certain level of "spend," possibly per year or per quarter;
  • maintaining the contract for a certain amount of time; and/or
  • a fee for early termination, akin to what cell-phone providers often require in return for discounted pricing.

6.2.1. Parties: Vendor and Customer.

When this Protocol is agreed to, the parties follow it whenever the Con­tract limits the ability of a party (the "Provider") to adjust the pricing that the Vendor charges to another party (the "Customer"):

Note

For this purpose, "Customer" could be a reseller or other channel partner.

  • in connection with transactions under the Con­tract — for example, for goods, services, or other things,
  • during a specified time period — the term of the Con­tract if not otherwise specified.

6.2.2. Price adjustments will not be retroactive.

Any adjustments in the Vendor's pricing will not apply to any Customer order that the Vendor has already accepted unless the burdened party — the Customer, for price increases; the Vendor, for price decreases — has clearly agreed otherwise in writing.

Note

The burdened party wouldn't be wild about "retrading the deal" for existing purchases.

6.2.3. Option: One-Month Price Increase Alert Requirement

  1. If the Con­tract clearly agrees to this Option, THEN: During the term of the Con­tract, the Vendor will alert the Customer, at least the specified time in advance, in writing by any reasonable means, of any upcoming pricing increases that the Vendor is planning that would affect Customer orders under the Con­tract that the Vendor has not yet accepted.
  2. In each such alert, the Vendor will clearly state the following:
    1. the date on which the price increase will go into effect; and
    2. any other information required by the Con­tract.
  3. If the Customer places an order after such an alert, but before the stated effective date of the pricing increase, THEN: The Vendor will see to it that the order is invoiced at the lower price.
Note

().  This Option is phrased as requiring an "alert," as opposed to requiring notice (concerning which, see Protocol 3.14).

This Option doesn't require the Vendor to alert the Customer about upcoming price decreases. That's because:

  1. The Customer will generally be happy to have price decreases go into effect immediately, without advance notice and thus without a waiting period.
  2. The Customer's main desire would be for advance notice of a pricing increase for budget-planning purposes, and to let the Customer make purchases before the increase goes into effect.

    True: The Customer might like to hear about upcoming price decreases. That would allow the Customer to defer non-urgent purchases that it might otherwise have made at the higher price.

But the Vendor would likely object to being required to let anyone know in advance about upcoming price decreases, because:

  1. The Vendor might not know in advance that it would be cutting prices; and
  2. The Vendor wouldn't want to have to wait out an advance-notice period, because that could hurt the Vendor's ability to make sales at the old, higher pricing — especially if word leaked to other customers. That'd be akin to the Osborne Effect that's famous in the tech world for having purportedly destroyed one of the first portable-computer companies in the early 1980s: Osborne prematurely announced a future model, resulting in plummeting sales of the existing model. (The Wikipedia article lists other examples of such vendor experiences.)

In any case, the Customer likely would prefer to have the Vendor's price cuts take effect immediately, to give the Customer maximum budget flexibility.

And finally, the Customer might be satisfied with this Option, requiring advance notice of increases, in lieu of a more-restrictive pricing clause. That might be especially true if the Customer had other options for acquiring the Vendor's goods or services — if the Vendor's price increases were too much for the Customer's tastes, then the Customer could perhaps just take its business elsewhere (assuming switching costs were not a major consideration).

6.2.4. Option: Price-Increase Limit

If the Con­tract clearly agrees to this Option, THEN: During the entire term of the Con­tract, the Vendor will not increase the pricing it charges to the Customer:

  1. more often than once per calendar year; nor
  2. by more than 999% for any given calendar year.
Note

The risibly-high "999% per year" is included here as an attention-getter for drafters and to give vendors some negotiation room. ¶ Some provisions along these lines might say, for example, "nor 2. by more than than X% or the increase in CPI-U since the last price change, whichever is [lower | higher]." (See generally Protocol 6.1 [CPI definition] and its commentary.) Note: Providers will generally want "X% or CPI, whichever is higher," while customers will want "X% or CPI, whichever is lower." Caution: In some provisions of this kind, price increases are tied to increases in a published benchmark — so what would happen if the benchmark were no longer published? Example: That happened in an Eleventh Circuit case, where a contract's pricing-escalation clause was ruled unenforceable because the clause was tied to an agreed benchmark but the benchmark was no longer being published. See Southern Coal Corp. v. Drummond Coal Sales, Inc., 25 F.4th 864, 873 (11th Cir. 2022) (rejecting mutual-mistake argument).

6.2.5. Option: Only Generally-Applicable Price Increases

If the Con­tract clearly agrees to this Option, THEN: During the term of the Con­tract, the Vendor will not increase the prices charged to the Customer for goods or services covered by the Con­tract except as part of — and by a percentage no greater than the percentage of — a price increase to the Vendor's customers generally for comparable items. The "for comparable items" concept can also be seen in so-called "most favored customer" provisions, discussed at 13.1.]

Note

This Option might satisfy a customer that was comfortable with allowing market pressure to constrain a vendor' price increases. This Option could also address any fear the customer might have that a vendor might retaliate against the customer, for example because the customer was looking to become independent of the vendor. Example: Such retaliation allegedly happened to a fuel-cell manufacturer in New York state; the parties settled the ensuing lawsuit, as reported in a business newspaper. See Robin K. Cooper, Plug Power settles lawsuit with hydrogen vendor Air Products (BizJournals.com May 6, 2021) (paywalled), and Plug Power sues Air Products over 'draconian elevated prices' (BizJournals.com Apr. 2, 2021) (paywalled).

6.2.6. Option: Straight Cost-Increase Pass Through

  1. If the Con­tract clearly agrees to this Option, THEN: During the term of the Con­tract, if the Vendor's relevant costs increase, the Vendor is free to pass the increase on to the Customer in the Vendor's pricing.
  2. When passing cost increases on to the Customer in this way, the Vendor must not add a markup unless:
    1. the Con­tract clearly says so; or
    2. the Customer so agrees in writing.
  3. If the Customer so requests, then the Vendor must provide the Customer with reasonable documentation to support the Vendor's intended princing increase.
  4. The Customer must treat all information that the Vendor provides under subdivision 3 as the Vendor's Confidential Information in accordance with Protocol 5.3 (Confidential Information).
Note

().  This is a stripped-down version of price increase pass-through clauses that are sometimes seen in ongoing master purchase agreements.

Subdivision 5 is an example of a party saying, in effect, We'll be happy to do X if you ask, but we need you to ask — if for some reason we don't do X on our own initiative, we don't want that to be a breach of contract.

6.2.7. Option: Sole-Discretion Pricing Increases

If the Con­tract clearly agrees to this Option, THEN: For the avoidance of doubt, the Vendor is not restricted in its ability to adjust its pricing, from time to time, in its sole discretion (defined at Protocol 9.6).

Note

A customer certainly wouldn't want to include this option in a contract — and a vendor might not want to include it either, because doing so might call attention to the issue ("poke the bear," see 8.14) and provoke the customer to demand restrictions on the vendor's ability to raise prices.

6.2.8. Option: Pricing Lock-In

If the Con­tract clearly agrees to this Option, THEN: During the term of the Con­tract, all pricing for transactions under the Con­tract will be as stated in the Con­tract (including without limitation in any relevant schedule, exhibit, etc.).

Note

Caution: Drafters representing vendors should be very careful if they're asked to combine a locked-in price period with an "evergreen" automatic extension of the lock-in period; see the commentary at 15.5.11.3 for a real-world story in which one of my clients had agreed to such a combination for a particular customer — only to find later that, for that customer, the vendor was locked in to (what became) an outdated price schedule for ten years.

7. Ambiguity: Sources & solutions

7.1. What is "ambiguity" in a contract?

Courts are pretty much agreed that a contract term is ambiguous if it is susceptible to two or more reasonable interpretations that can't be resolved by the usual tools of interpretation (known as "canons of construction," discussed at 7.7:

[A] contract is ambiguous only when the application of pertinent rules of interpretation to the face of the instrument leaves it genuinely uncertain which one of two or more meanings is the proper meaning….

In other words, if after applying established rules of interpretation to the contract it remains reasonably susceptible to more than one meaning it is ambiguous, but if only one reasonable meaning clearly emerges it is not ambiguous.

The interpreting court must decide[: (1)] whether the meaning of the text read in context is genuinely uncertain or [(2)] whether one reasonable meaning clearly emerges. Bd. of Regents of Univ. of Tex. Sys. v. Idexx Labs., Inc., 691 S.W.3d 438, 443-44 (Tex. 2024) (cleaned up, emphasis and extra paragraphing added) (reversing court of appeals: in context, royalty-rate provisions in university's patent-license agreement were not ambiguous); on remand, No. 14-20-00699-CV, slip op. (Tex. App. —Houston [14th Dist.] Apr. 3, 2025). (After remand, the appeals court affirmed the trial court's judgment.)

7.2. Some specific ambiguity examples

7.2.1. Date-related terms: Are they sufficiently definite?

Caution: Be careful about using vague terms that can trigger disputes.

Example: The term "consummated" sales led to what must have been a costly lawsuit over a finder's fee for helping land a federal contract: A court ruled that the finder's-fee agreement did not require the resulting federal contract to be "performed" during a particular time period in order for the transaction to be "consummated" — instead, the fact that that the contract was signed during the relevant time period was enough, and so the finder's fee was therefore due and owing. See Fed Cetera, LLC v. Nat'l Credit Servs., Inc., 938 F.3d 466 (3d Cir. 2019).

Example: Honeywell sued an electronics company over royalties owed under a patent-license agreement. The agreement allowed Honeywell to conduct an audit, but the audit had to be "conducted" within one year of the "Effective Date" of the agreement. A district court held that "the audit performed here occurred, in whole or in part, outside the one-year period." Honeywell Int'l, Inc. v. OPTO Electr. Co., No. 3:21-CV-00506 slip op. at introduction (W.D.N.C. Apr. 20, 2023) (granting partial summary judgment to defendant); see also id. at part III.A.1, text acc. n.6. At this writing, Honeywell's appeal is pending at the Federal Circuit (No. 24-1144).

12 midnight: Suppose that our fictional client MathWhiz (32.8.3) has signed a lease for office space, where it is the tenant. And suppose also that the lease says the following:

Tenant will vacate the Premises no later than 12 midnight on December 15; Tenant's failure to do so will be a material breach of this Agreement.

(Bold-faced emphasis added.)

Now suppose that a MathWhiz representative calls you up and says that they can't move out before 10:00 a.m. on December 15.

QUESTION At that time, on that day: • Would MathWhiz still have 14 hours left in which to finish moving out? • Or would MathWhiz already in material breach because it didn't move out by the previous midnight? In other words: Does "by midnight" mean before midnight at the start of the day, or before midnight at the end of the day?

Ripple-effect business complications can arise from such potential ambiguities — in the December 15 example above, the landlord might have already re-leased the premises to a new tenant, with a promise that the new tenant can move in on that date.

This illustrates a useful drafting principle: W.I.D.D. – When In Doubt, Define! (see 7.9.3). We could do that by being more explicit about 12 midnight, as is done at Protocol 13.15.2 (stating when a "Partnership Term" ends).

QUESTION: How would you rewrite the "Tenant will vacate the Premises no later than 12 midnight on December 15 …." sentence to resolve this ambiguity?

"Within X days of Y": Does that mean before Y, or after? From the NY Times, about improvements in training junior doctors to intubate infants:

ntubation is a delicate procedure requiring the insertion of a breathing tube into a trachea or windpipe. * * *

We randomized these trainees into two groups. The first group received supervision from senior clinicians while intubating infants, which is routine. The second group — the “coaching” arm of the trial — also received supervision while intubating infants, but in addition, they got targeted coaching by a senior clinician within an hour of that intubation. Stephen G. Flynn, Raymond S. Park, Pete G. Kovatsis, and Anupam B. Jena, The Hack Doctors Should Take From Pop Stars and Quarterbacks (NYTimes.com 2025) (formatting edited).

QUESTION: Did this additional "targeted coaching" occur within the hour before intubation, or within the hour after it?

Lesson: Better to say, "within an hour before (or after) …."

(DCT note: I intentionally left out the next sentence from the quote: "This warm-up took only five to 10 minutes and involved the trainee reviewing and practicing on an infant manikin the steps required to intubate a baby safely" — does that clarify the meaning?)

7.2.2. "May not" — does that mean might not, or must not?

Example: From a newspaper advice column responding to a question about a property settlement in a divorce: "Maryland and Florida are not community-property states, meaning the assets may not be distributed 50/50 …." QUESTION: Does this mean those states prohibit 50-50 distributions? (Spoiler: No.)

To avoid possible confusion:

  • Use may to indicate permission: ABC may delay payment until December 31.
  • Use might to indicate possibility: It might rain tomorrow.

This can be summarized in the acronym MPMP: May for Permission, Might for Possibility.

Or: Consider could instead of might, as in It could rain tomorrow.

7.2.3. Party obligations, reps, warranties: Who's accountable?

To place accountability where it belongs, obligations, warranties, and representations should be phrased so that they're made by individual parties, not by multiple parties jointly — use each party when appropriate.

Let's use representations as an illustrative example:

EXAMPLE:

    Both Parties represent that they are not subject to any exclusion order barring them from federal-government contracts.

    Each Party represents that it is not subject to any exclusion order barring it from federal-government contracts.

The problem: In the first example above, conceivably the "Both parties represent" phrasing could provide an opening for an aggressive lawyer to claim that the doctrine of "mutual mistake" supposedly excused a misrepresentation. The claim might not succeed — but let's (try to) not leave any openings for that sort of tactic.

(It might be another story if two parties were to be jointly and severally liable to a third party for something.)

7.3. Why ambiguity is (usually) a bad thing

If a potential ambiguity comes to light after a contract is signed, each party might have new, self-interested reasons — such as changed circumstances, or different people calling the shots — to argue for interpreting the provision in a way that disadvantages the other party. That in turn can lead to disputes and even lawsuits.

And there might well be a lot of money riding on whether a court concludes that a contract term is or isn't ambiguous.

Example: In Plains Exploration (Tex. 2015), the losing party ultimately missed out recovering the roughly $44 million that it had claimed it was owed under the contract in suit, because the state's supreme court concluded that the relevant contract language unambiguously ruled out the losing party's claim. Plains Explor. & Prod. Co. v. Torch Energy Advisors Inc., 473 S.W.3d 296, 305 (Tex. 2015).

Example: As discussed in the comments to Protocol 20.2, in Apache Corp. (Tex. 2023), a lawsuit over the meaning of the word "from" resulted in a party not being entitled to some $180 million. See Apache Corp. v. Apollo Exploration, LLC, 670 S.W.3d 319, 321 (Tex. 2023) (reversing and remanding court of appeals).

Example: In Dahua Tech. (1st Cir. 2025), an employee's severance agreement with his company called for the company to pay the employee "monthly severance payments … in the amount of $680,000 for sixteen (16) [sic] months …."

  • After much litigation, culminating in an 11-day (!) bench trial, a federal trial court in Massachusetts held that this called for each monthly payment to be $680,000; rejecting the company's request to reform the contract on grounds of mutual mistake, the trial court entered judgment for the employee in the amount of $10,200,000, plus prejudgment interest.
  • The First Circuit, though, concluded that "the inartfully drafted severance provision [was] ambiguous" and that "[i]n our view, the Release Agreement made no such unambiguous promise"; the court remanded the case to the trial court to resolve the ambiguity on the basis of extrinsic evidence. See Dahua Tech. USA, Inc. v. Zhang, 138 F.4th 1, 5, 9 (1st Cir. 2025).

Example: In Offshore Drilling (5th Cir. 2010), an off-shore drilling rig was severely damaged by fire while in drydock in Galveston for maintenance:

  • The drilling rig's owner and the drydock owner disputed which of the two parties had had "control" of the rig at the time of the fire.
  • The intended meaning of "control" was important because under the parties' agreement, if the drilling rig's owner had control at the time of the fire, then the drydock owner was not financially responsible for the fire damage.
  • Needless to say, the meaning of "control" was hotly contested (as it were …).

The trial court held that the term "control" was unambiguous, and granted summary judgment that, on the undisputed facts, the rig owner, not the dock owner, had been in control at the time of the fire. The appeals court affirmed; thus, the parties were spared the expense, inconvenience, and uncertainty of a trial on the issue of control of the rig. See Offshore Drilling Co. v. Gulf Copper & Mfg. Corp., 604 F.3d 221 (5th Cir. 2010) (affirming summary judgment in relevant part).

Of course, the drilling-rig owner would certainly have preferred to go to trial and take its chances with a jury, versus losing on summary judgment before the trial even started.

But for the drydock owner, not having to go to trial was most assuredly a win.

7.4. Disagreement doesn't automatically mean ambiguity

In Plains Exploration (Tex. 2015), the Texas supreme court noted that "[m]ere disagreement over the interpretation of an agreement does not necessarily render the contract ambiguous." Plains Explor. & Prod. Co. v. Torch Energy Advisors Inc., 473 S.W.3d 296, 305 (Tex. 2015).

To like effect, the same court noted in Finley Resources (Tex. 2023):

mere breadth of a disputed term does not perforce equate to ambiguity. An unmodified term that invokes many different definitions could, of course, be so broad in the abstract that it is vague and ambiguous, but a contract is ambiguous only if it is subject to more than one reasonable interpretation after the pertinent rules of construction have been applied.

If contract language can be given a certain or definite legal meaning when considered as a whole, and in light of the objective circumstances surrounding its execution, the contract is not ambiguous and must be construed as a matter of law. Finley Resources, Inc. v. Headington Royalty, Inc., 672 S.W.3d 332, 340 (Tex. 2023) (affirming court of appeals reversal and rendering of judgment; cleaned up, emphasis and extra paragraphing added).

7.5. Vagueness is one type of ambiguity — but maybe leave it be?

7.5.1. What is "vague"?

As one type of potential ambiguity, a term is vague if its precise meaning is uncertain.

A classic example is the term tall: If you say that someone is tall, you could be referring to that a third-grader who is tall for his- or her age but is still very-much shorter than the general adult population.

Another classic example of vagueness is the word cool; depending on the season and the locale, the term could refer to a wide range of temperatures. For example, suppose that, at 2 p.m. on an August day, the temperature is 80ºF: • In Houston, it'd be unseasonably cool (compared to our usual temperatures then). • In Point Barrow, Alaska, the locals would likely think 80ºF was a real scorcher. Similarly, a parent could feel an ailing child's forehead and report that the skin was cool, which would probably mean around 98ºF; this would have a different meaning than urging the child to wear a sweater because it was cool outside, probably around 60ºF or so.

[DCT TO DO: Venn diagram — vagueness as a subset of ambiguity]

7.5.2. A term could be both vague and have multiple meanings

In English-speaking families with teens or tweens at home, parents know that the word cool can have multiple meanings: Apart from the above temperature example, cool could be used to indicate approval — or scorn.

Let's look at another example, this time a silly one. Consider the following provision in a contract for a home caregiver:

Nurse will visit Patient's house each day, check her vital signs, and give her cat food.

The sentence above could conceivably take on any of three meanings:

1.  Nurse is to put a bowl of food down for Patient's cat each day.

2.  Nurse is to deliver cat food to Patient when Nurse visits.

3.  Nurse is to feed cat food to Patient. (OK, that one might be a stretch.)

In addition, the sentence above might also be vague if it turned out that Patient had more than one cat.

Moreover, meanings #1 and #2 above are vague in another sense as well: The term cat food encompasses wet food, dry food, etc.

7.5.3. Is vagueness worth fixing?

Vagueness is not necessarily a bad thing. Parties might be confident that, if a question ever arises, it'll be clear (or can be expeditiously determined) just what was intended by, say, the term reasonable efforts, and so it wouldn't be the best use of time to try to agree on a precise definition of what was and wasn't required.

Analogously: In response to comments made about proposed financial-disclosure requirements, in 1969 the Securities and Exchange Commission declined to get more specific about the meaning of the term line of business:

[I]n view of the numerous ways in which companies are organized to do business, the variety of products and services, the history of predecessor and acquired companies, and the diversity of operating characteristics, such as markets, raw materials, manufacturing processes and competitive conditions, it is not deemed feasible or desirable to be more specific in defining a line of business.

Management, because of its familiarity with company structure, is in the most informed position to separate the company into components on a reasonable basis for reporting purposes.

Accordingly, discretion is left to the management to devise a reporting pattern appropriate to the particular company's operations and responsive to its organizational concepts.

SEC Securities Act Release No. 4988 (Jul. 14, 1969), quoted in A. A. Sommer Jr., SEC "Line of Business" Reporting Requirements, 44 St. John's L. Rev. 926, 931 (1970) (emphasis and extra paragraphing added). Mr. Sommer was a prominent securities lawyer who served as an SEC commissioner, among other positions. (Hat tip:

But: Too-vague a term might lead to an agreement being held unenforceable. Example: In Smith (Idaho 2024), a state supreme court affirmed a divorce court's holding that, in a divorce settlement agreement, the term "[s]pousal support shall be reviewed every two years" was "so vague, uncertain, indefinite, and incomplete that it is unenforceable." Smith v. Smith, No. 50184 (Id. Dec. 19, 2024).

So here's a rule of thumb: Vagueness isn't always worth fixing — but a vague term is always worth taking a look at to see if it should be replaced by a more-precise term.

7.6. Emphasis on words can create ambiguity

Emphasis on words can change sentence meaning. Example: In the following sentence (from Facebook), try reading the sentence aloud seven times — once for each word in the sentence — emphasizing successive words each time.

I never said she stole my money.

Examples (emphasis added):

  • I never said she stole my money.
  • I never said she stole my money.
  • I never said she stole my money.

etc.

Another example:

I didn’t buy you twelve red roses.

7.7. Resolving ambiguity (step 1): Canons of construction

Sometimes parties to a contract will dispute the meaning of a contract provision. In the U.S., if the dispute goes to court, the trial judge uses a one- or possibly-two step process in resolving the dispute. This section discusses the first step;  7.8 addresses the second step, which might or might not be needed.

The trial judge makes the first pass at determining the meaning of a disputed provision, using the usual rules of contract interpretation (see below). The goal is to see if the case can be decided quickly (and thus less expensively), via a party's motion to dismiss on the pleadings or a motion for summary judgment.

If the trial judge concludes that this first-pass review has produced a definite meaning for the disputed provision, then the judge will declare that meaning. This means that there won't be the need for a trial to establish the meaning of that particular provision. But conceivably the appellate court might have a different view about the provision's proper interpretation: The appeals court might conclude that the provision is indeed ambiguous, in which case the appeals court might well send the case back to the lower court for a trial to determine the provision's meaning.

In Plains Exploration (Tex. 2015), the Texas supreme court recapped some of the general ground rules — sometimes known as the "canons of construction" — for how this works; to better Serve The Reader, I've recast the court's discussion into short, single-subject paragraphs:

Absent ambiguity, contracts are construed as a matter of law.
[DCT comment: That is, it's the trial judge — not the jury — who construes the contract, but the appeals court is free to overrule the trial judge].

In construing a written contract, our primary objective is to ascertain the parties' true intentions as expressed in the language they chose.

We construe contracts from a utilitarian standpoint bearing in mind the particular business activity sought to be served, and avoiding unreasonable constructions when possible and proper.

To that end, we consider the entire writing and giving effect to all the contract provisions so that none will be rendered meaningless.

No single provision taken alone is given controlling effect; rather, each must be considered in the context of the instrument as a whole.

We also give words their plain, common, or generally accepted meaning unless the contract shows that the parties used words in a technical or different sense.

While extrinsic evidence of the parties' intent is not admissible to create an ambiguity, the contract may be read in light of the circumstances surrounding its execution to determine whether an ambiguity exists.

Consideration of the surrounding facts and circumstances is simply an aid in the construction of the contract's language and has its limits.

The rule that extrinsic evidence is not admissible to create an ambiguity obtains even to the extent of prohibiting proof of circumstances surrounding the transaction when the instrument involved, by its terms, plainly and clearly discloses the intention of the parties, or is so worded that it is not fairly susceptible of more than one legal meaning or construction. Plains Explor. & Prod. Co. v. Torch Energy Advisors Inc., 473 S.W.3d 296, 305 (Tex. 2015) (formatting modified, citations omitted).

7.7.1. Context can matter

The Texas supreme court noted that "a primary determinant of meaning is context. For that reason, language that might evoke multiple meanings if read in isolation will often be made more precise by its contextual use. …" Finley Resources, Inc. v. Headington Royalty, Inc., 672 S.W.3d 332, 340 (Tex. 2023) (affirming court of appeals reversal and rendering of judgment; emphasis added).

7.7.2. Expressio unius: The drafters knew how to say X — and they didn't

When interpreting contract language, courts sometimes resort to a principle summarized by the Latin phrase expressio unius est exclusio alterius, which can be translated as, to express one thing is to exclude others.

In Wells Fargo (2d Cir. 2018), the court provided an example: "By expressly foreclosing certain proceedings from arbitration, the parties in these cases strongly implied that every other controversy or dispute remains subject to arbitral resolution." Wells Fargo Advisors, LLC v. Sappington, 884 F. 3d 392, 396 (2d Cir. 2018) (affirming denial of Wells Fargo's petition to compel individual arbitration instead of class arbitration) (emphasis added).

The same principle is sometimes used in interpreting statutes and regulations. In John Wiley & Sons (2d Cir. 2018), the same appeals court elaborated:

… the interpretive canon of expressio unius est exclusio alterius instructs that Congress's expression of one or several items in an enumerated list typically reflects an intent to exclude another left unmentioned.

  • In the Copyright Act, Congress expressly provided a cause of action for infringement only for legal or beneficial owners of one of the six enumerated exclusive rights under a copyright.
  • The right to sue is conspicuously absent from the list of exclusive rights.

[Thus, the] plain language of the Act does not authorize infringement actions by mere assignees of the bare right to sue …. John Wiley & Sons, Inc. v. DRK Photo, 882 F. 3d 394, 405 (2d Cir. 2018) (affirming summary judgment) (formatting modified).

Likewise, in Trump (D.C. Cir. 2024), the court of appeals used what amounts to the same principle (minus the Latin) in affirming rejection of former President Trump's claim of immunity from prosecution for alleged crimes committed while he was in office:

The Framers knew how to explicitly grant criminal immunity in the Constitution, as they did to legislators in the Speech or Debate Clause. Yet they chose not to include a similar provision granting immunity to the President. … United States v. Trump, 91 F.4th 1173, 1201 (D.C. Cir.) (cleaned up, formatting revised), vacated and remanded, 603 U.S. 593, 144 S. Ct. 2312 (2024).

Famously, of course, in Trump the Supreme Court took a very-different view of the merits of the presidential-immunity issue: The Court's majority did not address the D.C. Circuit's "the Framers knew how" reasoning, while in contrast Justice Sotomayor largely based her dissent on that reasoning. See 144 S. Ct. at 2357, part III.A (Sotomayor, J., dissenting).

7.7.3. Ejusdem generis and noscitur a sociis: Known by the company they keep

Courts sometimes look to a principle of interpreting language that's referred to as ejusdem generis ("eh-USE-dem GENerous"). As one online legal dictionary explains, "if a law refers to automobiles, trucks, tractors, motorcycles, and other motor-powered vehicles, a court might use ejusdem generis to hold that such vehicles would not include airplanes, because the list included only land-based transportation." Nolo’s Plain-English Law Dictionary (law.cornell.edu).

Contract drafters can avoid application of ejusdem generis to contract language by using the term "including but not limited to" (emphasis added), or by simply defining "including" in that way, as then-Judge Alito pointed out in a Third Circuit decision: "By using the phrase 'including, but not limited to,' the parties unambiguously stated that the list was not exhaustive …. [and so] the doctrine of ejusdem generis is inapplicable." Cooper Distributing Co., 63 F.3d at 280 (3d Cir. 1995) (Alito, J.; citations omitted, formatting edited); see also, e.g., Eastern Air Lines, 532 F.2d at 988-89 (5th Cir. 1976); Scott & Triantis at 850 & n.100 (2006)

Concerning ejusdem generis, the Supreme Court offered this in Fisher (2024):

One way to discern the reach of an “otherwise” clause is to look for guidance from whatever examples come before it.

Two general principles are relevant.

First, the canon of noscitur a sociis teaches that a word is given more precise content by the neighboring words with which it is associated. That avoids ascribing to one word a meaning so broad that it is inconsistent with the company it keeps.

And under the related canon of ejusdem generis, a general or collective term at the end of a list of specific items is typically controlled and defined by reference to the specific classes that precede it.

These approaches to statutory interpretation track the common sense intuition that Congress would not ordinarily introduce a general term that renders meaningless the specific text that accompanies it.

To see why, consider a straightforward example. A zoo might post a sign that reads, “do not pet, feed, yell or throw objects at the animals, or otherwise disturb them.” If a visitor eats lunch in front of a hungry gorilla, or talks to a friend near its enclosure, has he obeyed the regulation? Surely yes.

  • Although the smell of human food or the sound of voices might well disturb gorillas, the specific examples of impermissible conduct all involve direct interaction with and harassment of the zoo animals.
  • Merely eating or talking is so unlike the examples that the zoo provided that it would be implausible to assume those activities were prohibited, even if literally covered by the language.

The idea is simply that a general phrase can be given a more focused meaning by the terms linked to it. That principle ensures—regardless of how complicated a sentence might appear—that none of its specific parts are made re- dundant by a clause literally broad enough to include them. For instance, a football league might adopt a rule that players must not “grab, twist, or pull a facemask, helmet, or other equipment with the intent to injure a player, or otherwise attack, assault, or harm any player.” If a linebacker shouts insults at the quarterback and hurts his feelings, has the linebacker nonetheless followed the rule? Of course he has. The examples of prohibited actions all concern dangerous physical conduct that might inflict bodily harm; trash talk is simply not of that kind. Fischer v. United States, 603 U.S. 480, 144 S. Ct. 2176, 2183-84 (2024) (vacating and remanding D.C. Circuit decision about one count of conviction of "Jan. 6" defendant) (cleaned up, formatting edited).

7.7.4. Other canons of construction

In interpreting contract language, judges can look to still-more canons of construction:

–  Specific terms normally take precedence over general terms.

–  A term stated earlier in a contract is given priority over later terms.

–  The rule of the last antecedent — for example: A federal criminal statute included a mandatory ten-year minimum sentence in cases where the defendant had previously been convicted of "aggravated sexual abuse, sexual abuse, or abusive sexual conduct involving a minor or ward." Writing in Lockhart (U.S. 2016), a majority of the Supreme Court held that the minor-or-ward qualifier in the just-quoted provision applied only to abusive sexual conduct, not to sexual abuse; as a result, a defendant was subject to the ten-year mandatory minimum sentence for sexual abuse against an adult. Lockhart v. United States, 577 U.S. 347, 136 S. Ct. 958, 962 (2016).

–  BUT: The series-qualifier principle might weigh against the rule of last antecedent. Dissenting in Lockhart, Justice Kagan argued: "Imagine a friend told you that she hoped to meet 'an actor, director, or producer involved with the new Star Wars movie.' You would know immediately that she wanted to meet an actor from the Star Wars cast—not an actor in, for example, the latest Zoolander." Id., 136 S. Ct. at 969 (Kagan, J., dissenting).

For additional background reading, see generally, e.g.: •  Vincent R. Martorana, A Guide to Contract Interpretation (ReedSmith.com 2014); • James J. Sienicki and Mike Yates, Contract interpretation: how courts resolve ambiguities in contract documents (Lexology.com 2012: https://goo.gl/ZGkwJu).

7.8. Resolving ambiguity (step 2): A trial, for fact-finding

If applying the above canons of construction doesn't resolve the dispute, then the disputed provision is indeed ambiguous. When that happens, (in the U.S.) the trial judge is not allowed to grant a quick judgment: Instead, the court must conduct a trial (if the parties are lucky, a trial on just that one issue) so that the "trier of fact" — a jury, or perhaps the judge him‑ or herself — can evaluate the parties' evidence and make factual findings about the meaning of the disputed provision.

Importantly: At least in U.S. jurisdictions, an appeals court isn't likely to overrule such a factual determination by a jury or a trial-court judge. The Seventh Circuit explained:

The district court's job was to look at extrinsic evidence and determine what the agreement was. It did that.

Our job is to decide if the district court's view of that evidence was clearly erroneous (or legally wrong). …

The argument, 'The Borrowers' position was supported by the evidence presented at trial but our interpretation is way, way better' is a nonstarter. We are looking to correct error, not reward elegance. BKCAP, LLC v. CAPTEC Franchise Trust 2000-1, 688 F.3d 810, 813-14 (7th Cir. 2012) (emphasis in original, extra paragraphing added).

7.9. What does this mean for contract drafters?

Spotting and fixing potential ambiguities in a contract before the contract is signed should be a prime goal of all contract drafters and reviewers.

To adapt an in-class comment by one of my former students (in a different context), determining the meaning of an ambiguous term in a signed contract is "a conversation we don't want to have."

In a 2017 article, a New York City judge noted: "President and later Chief Justice Taft got it right, though in the negative: 'Don't write so that you can be understood; write so that you can't be misunderstood.'" Gerald Lebovits, Free at Last from Obscurity: Achieving Clarity, 96 Mich. B.J. 38 (May 2017), SSRN: https://ssrn.com/abstract=2970873 (emphasis added, footnote omitted).

7.9.1. How to spot ambiguities in your drafts?

Two main possibilities, and maybe a third:

  1. Ideally: Have someone else review your draft with fresh eyes.
  2. Or: Put the draft aside for awhile and re-read it later; chances are that you'll spot something you didn't before.
  3. Or: You could try giving your text to an LLM (a type of AI, e.g., ChatGPT, Gemini, Perplexity, Claude, etc.) and asking the LLM to look for ambiguities — but you'll want to be very careful not to reveal client information to the LLM because the LLM might store the information away for future use. (For this option, you'll want to think about getting "informed consent" from the client — and you probably should first check with your supervising partner.)

7.9.2. The A.T.A.R.I. Rule: Avoid The Argument: Rewrite It! (usually)

That's It. That's the tweet (so to speak).

But why usually?

Answer: Because there are (rare) times when you might not want to fix an ambiguity, as discussed in more detail at 7.9.4.

7.9.3. The W.I.D.D. Rule: When In Doubt, Define!

Savvy contract drafters prefer not to roll the dice about whether a court will apply the above principles in a way that favors the drafter's client. So: An extremely-useful general principle of contract drafting is, W.I.D.D. – When In Doubt, Define!.

But don't go overboard — see #3 in Bryan Garner's LawProse Lesson #442: Guidelines for Legal Definitions (2024): "If you create a defined term, then use it. (You know how often this rule is broken.)"

7.9.4. But: Strategically, an ambiguity might be better left in place

The A.T.A.R.I. Rule (7.9.2) and W.I.D.D. (7.9.3) are great rules of thumb — but neither of them is a hard-and-fast rule; a drafter should think strategically before deciding whether to revise a potentially-ambiguous contract term during negotiations.

•   Did your side draft the potentially-ambiguous language? Then yes, fix it — especially if the draft hasn't yet been sent to the other side. That's because under the doctrine of contra proferentem (11.4), a court might resolve the question in favor of the other side because your side was responsible for the ambiguity.

•   Did the other side draft the potentially-ambiguous language? If yes, then you might not want to say anything about it, in the hope that contra proferentem (11.4) would result in an interpretation favorable to your client.

If you didn't have the superior bargaining position, it might be especially tempting to keep mum about a potential ambiguity: If you were to "poke the bear" (8.14) — that is, call the other side's attention to the issue — then the other side might wake up and ask for something that's even worse for your client. (See 8.14 for examples.)

One study of contract forms recounted an email from a lawyer who worked in private-equity transactions:

There are occasions where, if I had asked for clarity, I’d have gotten a clause that disadvantaged my client. In such a case, because the ambiguous language retained value for my client, I probably would not push for clarity. Tara Chowdhury, Faith Chudkowski, and Mitu Gulati, The Form Knows Best, 79 U. Mia. L. Rev. 607, 613 (2025) (quoting email; footnote omitted), available at https://repository.law.miami.edu/umlr/vol79/iss4/3.

BUT: Later, the other side might be able to show that you noticed, but failed to raise, an ambiguity created by the other side's drafter — and under those circumstances, the other side might try to argue that, because your client "laid behind the log," your client should be held to have waived any benefit that it might otherwise have accrued from the contra proferentem doctrine.

And pragmatically: If you don’t ask the other side to correct an ambiguity that they created, then you might be setting up your client for an expensive, burdensome, future fight — a fight that perhaps might have been avoided with clearer drafting — and it might have been better to have that fight before the contract is signed, while your client still had the option to walk away.

The W.I.D.A.C. Rule also applies here: When In Doubt, Ask the Client (and/or your supervising attorney), and be ready with a recommendation, including your reasons — also, be sure to confirm the decision with the client with a quick email. (See 30.5 for more on this.)

7.10. What if The Other Side balks at fixing an ambiguity?

It's been known to happen that, during contract negotiations, A asks to rewrite an ambiguity, but B's lawyer says, there's no need to rewrite it, because the courts construe it the way you say.

Is that good enough — should A just accept B's assertion? Very possibly not:

  • In a dispute, B's lawyers will argue (often shamelessly) for whatever interpretation seems good to them at the time — regardless of what was previously said by B.
  • A will be reluctant to risk having a court hold that, by not insisting on clarifying the ambiguity, A waived its own preferred interpretation of the language.
  • On the other hand: B might be stuck with its prior assertion to A, on estoppel grounds or analogously to contra proferentem (see 11.4).

This will ultimately come down to how A's business people — advised by counsel — judge the overall business risk.

7.11. Optional further reading about ambiguity

Some amusing examples of ambiguity can be read at the Wikipedia article on Syntactic ambiguity, at https://goo.gl/6zmrH5

See also numerous categorized case citations by KPMG in-house attorney Vince Martorana, at A Guide to Contract Interpretation (ReedSmith.com 2014).

7.12. Ambiguity: Exercises & discussion questions

  1. A contract term is ambiguous when the term is amenable to [BLANK].
  2. In litigation, when a contract provision has multiple plausible meanings, and the parties' intended meaning can't be determined by conventional rules of interpretation, then that determination will be made by: A) the judge; B) the jury; C) one or more other officials.
  3. Consider the following sentence: "Alice says that Bob is cold." Is this more likely to be considered vague, ambiguous, or both?
  4. Consider the following sentence: "Alice says that Bob's forehead feels warm." Is this more likely to be considered vague, ambiguous, or both?
  5. What is a principal danger of an ambiguous contract term?
  6. FACTS: In a contract draft prepared by The Other Side, you see a term that's vague — it says that Argon must pay The Other Side a certain amount by a certain date, but doesn't specify the time of day for that deadline. QUESTION: Is this worth asking The Other Side to fix? Discuss your reasoning.
  7. MORE FACTS: In this contract, Argon is located in Vancouver, Canada and The Other Side (which drafted the contract) is located in Houston. The contract states that the amount Argon must pay is $1 million. QUESTION: Is this an issue? If so, is it worth burning up negotiation time by asking The Other Side to fix it? Discuss your reasoning.
  8. MORE FACTS: In the above situation, Argon really wants to get the contract to signature as soon as possible, like yesterday. You've tentatively concluded that it's not worth raising either of the above points (time of day and amount due) with The Other Side. QUESTION: To be on the safe side and keep your malpractice-insurance carrier happy, what might you want to do about these points before sending your markup to The Other Side?
  9. If all else fails in trying to interpret a contract provision, what Latin maxim will courts often follow, and what does it mean?
  10. The term "12 midnight on January 21" refers to the next minute after 11:59 p.m. on: A)  January 20; B) January 21; C) can't tell from this text alone.
  11. The Latin phrase for "against the offeror" is [BLANK].

7.13. Ambiguity: Drills

  1. TEXT, from The Kinks' famous song Lola (play the relevant clip on YouTube): "Well I'm not the world's most masculine man | But I know what I am and I'm glad I'm a man | And so is Lohhh-lahhh ….." QUESTION: When the artists sing, "And so is Lola," what exactly is Lola? EXERCISE: How that lyric line could be clarified? (Don't worry about rhyme or meter.)
  2. TEXT, from a Maureen Dowd column in the NY Times, March 5, 2016: "Like Bill Clinton, Trump talks and talks to crowds. … [H]e creates an intimacy even in an arena that leaves both sides awash in pleasure." (Emphasis added.) QUESTION: What, exactly, leaves both sides awash in pleasure? How could this be clarified?
  3. TEXT, from Donald Trump: "My daughter, Ivanka, just arrived in South Korea. We cannot have a better, or smarter, person representing our country." From Jonathan Chait: "That second sentence can really be read a couple ways." [DCT comment: It'd be better to say "a couple of ways."] From Gary Schroeder: "Also, the use of commas implies that she is his only daughter."
  4. TEXT, from a tweet: "I’ve sworn to defend and uphold our Constitution 11 times." QUESTION: What exactly does "11 times" refer to — defending and upholding the Constitution 11 times, or swearing to do so? EXERCISE: Rewrite to clarify.
  5. TEXT, adapted from an arbitration award I was writing (and caught myself): "Ms. Doe and her coworker Jane Roe were separately interviewed by John Doe and Becky Bow." QUESTION: How many separate interviews were conducted — two? four? EXERCISE: Rewrite to clarify.
  6. TEXT, from a tweet encouraging attendance at an anti-lockdown protest in Maine: "[T]here will be a caravan around the Capitol … Monday. … Remain in your vehicles but masks, bandanas, flags and signs on cars are encouraged." QUESTION: In your view, why are caravaners being encouraged to put masks and bandanas on cars? QUESTION: How could this be rewritten to clarify?
  7. TEXT, from an obituary: "Pamela went to heaven surrounded by family whom she loved …." QUESTION: What possibilities does this line evoke in your minds?
  8. TEXT, from this tweet by ABC Channel 13 (Houston): "Suspected Houston-area pedophile accused of assaulting 16-year-old arrested in Canada." QUESTION: What are some possible interpretations of this tweet? How could it be clarified?
  9. TEXT: Spotted in a Facebook group: "My eight year old just asked me if Bingo is the name of the farmer or the dog. And now I am questioning everything I thought I knew about life." (Credit: @whitneyhemsath.)
  10. TEXT, from Erin Johnston, Not All at Once, And Not All Alone, ABA Journal, Nov. 2018, at 14: "My success [as a Kirkland & Ellis litigation partner] has not been the result of a perfectly-executed master plan. But I can say that I have unapologetically asked for what I needed and was pleasantly surprised by the responses I received. No one above me assumed they knew what I wanted, or that what I wanted would always be the same. At times I turned down opportunities to avoid travel or to focus on my family; other times I chose to take that trip or work long hours. …" (Emphasis added.) QUESTION: What are two possible meanings of the italicized portion? QUESTION: How could the italicized portion be clarified?
  11. Ambiguous: This sign. More clear: This sign.
  12. TEXT, from a presidential tweet of April 3, 2017: "Such amazing reporting on unmasking and the crooked scheme against us by @foxandfriends. …" (Hat tip: Chris Richardson.) QUESTION: What are two possible interpretations of this tweet?
  13. TEXT, from a Facebook post by Stanford law professor Mark Lemley: "Things I appear to like more than my Facebook friends: 1. Pants." QUESTION: What are the two possible meanings here?
  14. TEXT, from this BBC.com article: "Nestle has announced that it will pay Starbucks $7.1bn (£5.2bn) to sell the company's coffee products." QUESTION: QUESTION: Which company will sell which company's coffee? How could this be clarified?
  15. TEXT, from a BBC News tweet: "Belgium court clears three doctors accused of unlawfully poisoning a woman whose life they helped to end in landmark trial." QUESTION: What exactly happened at the "landmark trial"?
  16. TEXT: "A hypothetical leak could occur, he said, if officials believed Clinton was not being prosecuted for political reasons." (Emphasis added.) (From a Politico piece titled FBI could leak Clinton email investigation, Grassley warns.) QUESTION: There are two possible meanings of the italicized portion of the above sentence. Discuss.
  17. TEXT, from an article in The Guardian: "There will be plush lecture theatres with thick carpet, perhaps named after companies or personal donors." ( Martin Parker, Why we should bulldoze the business school, The Guardian, Apr. 27, 2018 (https://perma.cc/F5N6-46RE).) QUESTION: What, exactly, is named after companies or personal donors? QUESTION: How could this sentence be rewritten to clarify it?
  18. TEXT, from an arbitration award that I was writing (and caught myself): "Ms. Doe and her coworker Jane Roe were separately interviewed by Human Resources manager John Doe and Becky Bow." QUESTION: How many people were interviewed, by how many people?
  19. TEXT, from a Hacker News discussion: "You should only short term trade with your 401k." QUESTION: How can this sentence be clarified by simply moving words around? (There are two possible meanings.)
  20. TEXT: "The temptation for progressives to resist pushing their own concrete policy agenda is compelling, especially since doing so gives the other side ammunition for criticism …." (From Joel Berg, It's Policy, Stupid — Why progressives need real solutions to real problems, Washington Monthly, Apr. 10, 2017.) QUESTION: In the quotation, the bold-faced "doing so" refers to what, exactly — pushing a policy agenda, or resisting pushing an agenda? EXERCISE: Rewrite to clarify.
  21. TEXT, from this tweet by then-president Donald Trump: "'Federal Judge throws out Stormy Danials lawsuit versus Trump. Trump is entitled to full legal fees.' @FoxNews Great, now I can go after Horseface and her 3rd rate lawyer in the Great State of Texas. She will confirm the letter she signed! She knows nothing about me, a total con!" AND: This response by a liberal-leaning columnist: "While we’re on the topic, can we talk about the comma in the very last sentence?"
  22. TEXT, from [ADD LINK:] Sheryl Sandberg's employment agreement: "[Y]our Employment will not infringe the rights of any other person." QUESTION: From a drafting-technique perspective, what's wrong with this provision?
  23. TEXT, from a Paul Krugman column: "What Freedom House calls illiberalism is on the rise across Eastern Europe. This includes Poland and Hungary, both still members of the European Union, in which democracy as we normally understand it is already dead." QUESTION: Where is democracy supposedly already dead — just Poland and Hungary, or the whole EU?
  24. TEXT, from the Washington Post: "[Jake] Tapper said that [Kellyanne] Conway’s boss, the president, has been the subject of numerous sexual assault allegations and has said that those women lied about them." QUESTION: Who, exactly, said "those women lied" — was it Tapper, or Conway's boss? How could this be clarified?
  25. TEXT, from this tweet: "Man trampled to death by elephant trying to take a SELFIE". EXERCISE: Rewrite.
  26. TEXT: See the strip of July 17, 2017. EXERCISE: Rewrite.
  27. TEXT: "WASHINGTON (AP) – A Russian billionaire close to President Vladimir Putin said Tuesday he is willing to take part in U.S. congressional hearings to discuss his past business relationship with President Donald Trump's former campaign chairman, Paul Manafort." (AP.com) QUESTION: Who exactly is willing to take part in U.S. congressional hearings? QUESTION: How could this be clarified?
  28. TEXT: See this Pearls Before Swine cartoon. (The author, Stephan Pastis, is a non-praticing lawyer.) QUESTION: How could the first panel's wording be "improved"?
  29. TEXT, from a Facebook posting: "A man's success has a lot to do with the kind of woman he chooses to have in his life. (Pass this on to all great women.)" QUESTION: What's another, grossly-sexist interpretation of this quote? (Please don't be offended by this example; we're learning here to spot — and fix — unintentional ambiguities that can be subject to intentional, motivated misinterpretation.)
  30. TEXT, In honor of Rosh Hashana (fall semester) or Passover (spring semester), from Joshua Rothman in The New Yorker: "My grandmother is ninety-three and, to my knowledge, has never kept kosher." QUESTION: Is there any way the bold-faced part could be misinterpreted — perhaps intentionally? QUESTION: How could this be rewritten to clarify?
  31. TEXT (from a dispute that I arbitrated): A contract states that payments remaining past due more than 30 days after the due date will bear interest at “a rate per annum equal to the prime rate published by the Wall Street Journal on the business day before the date on which such interest begins to accrue, changing with each change in such published rate, plus two percent (2%)." FACTS: On the relevant date, the Journal's published U.S. prime rate was 4.00%. QUESTION: On its face, from a drafting style perspective, what's wrong with this interest-rate provision? QUESTION: What interest rate should be applied to the late payment — 6%, or 4.08%? QUESTON: How could the interest-rate language be clarified?
  32. TEXT: In November 2018, former president Barack Obama said "a challenge of working in the White House is not always getting credit 'when nothing happens. And nothing happening is good," Obama said, to laughs." (From here.) QUESTION: What's another possible meaning of the italicized portion — a meaning that might also have triggered laughter? (Hint: Think of who was occupying the Oval Office at the time.)
  33. TEXT: Adapted from my church's Easter Sunday service booklet of a few years ago (with the family's name changed): "Easter flowers and decorations are given | to the glory of God | and in memory of their grandmother Jane Doe | In honor of all Christians, | Especially those persecuted/ | By the Doe family." QUESTION: How could this be fixed with just one additional character?
  34. FACTS: 1. Alice and Bob enter into a referral agreement; under that agreement, Alice must pay Bob a finder's fee for every contract that Alice "consummates" with anyone referred to her by Bob during a specified time period. 2. During the specified time period, Bob refers Carol to Alice. Before the specified time period ends, Alice signs a contract with Carol; BUT: Alice doesn't actually begin performing her obligations under the contract with Carol until after the specified time period ends. 3. Alice claims that she therefore doesn't owe Bob a finder's fee for her contract with Carol. QUESTION: What result? QUESTION: How could the finder's-fee agreement have been clarified? SOURCE: Fed Cetera, LLC v. Nat’l Credit Servs., Inc., 938 F.3d 466 (3d Cir. 2019) (reversing and remanding summary judgment in favor of "Alice").
  35. TEXT, from Spanski Enterprises, Inc. v. Telewizja Polska S.A., No. 19-4066 (2d Cir. Oct. 29, 2020) (nonprecedential summary order affirming judgment below): "The term of this Agreement is 25 (twenty-five) years and it comes into effect on the date of its signing. TVP and SEI may extend its term by subsequent 10 year periods." QUESTION: May either party extend the term, or must both? QUESTION: How could this be clarified? QUESTION: Do you see any other drafting "fail"? (In Q3, note how the question mark is outside the closing quotation mark, because the question mark isn't part of the quotation.)
  36. TEXT, from the Wikipedia page about Michigan Governor Gretchen Whitmer: "Gretchen Esther Whitmer (born August 23, 1971) is an American politician serving as the 49th governor of Michigan since 2019." QUESTION: Has Michigan really had 49 governors since 2019? QUESTION: How could this be rewritten to clarify?
  37. TEXT, from a WaPo story about two announced Nobel laureates in economics: "The two men will receive a cash award of 10 million Swedish krona, worth a bit more than $1.1 million." QUESTION: How much will each man receive?
  38. TEXT, from the Washington Post: "Rep. Sean Patrick Maloney (D-N.Y.) walked [acting ambassador to Ukraine William] Taylor through his U.S. Military Academy and military career, including that he was No. 5 in a class of 800 and took a tough infantry assignment in Vietnam, in an apparent effort to embarrass Republicans." QUESTION: Who, exactly, did what, "in an apparent effort to embarrass Republicans"? How could the ambiguity be fixed?
  39. TEXT, from this church sign: "Don't Let Worries | Kill You | Let The Church | Help"

8. Street smarts: Tricks of the trade

8.1. Conspicuousness (notes on what not to do)

8.1.1. Business context

In some jurisdictions, certain types of clauses might not be enforceable unless they are "conspicuous." For clauses in this category, courts typically want extra assurance that the signers knowingly and voluntarily assented to the relevant terms and conditions.

Example: Under the "express negligence" doctrine in Texas law (see 14.3.4), an indemnity provision that purports to protect a party from the consequences of its own negligence must not only be expressly stated, it must also be "conspicuous" in accordance with the Uniform Commercial Code standard. See Dresser Indus., Inc. v. Page Petroleum, Inc., 853 S.W.2d 505, 508-09 (Tex. 1993) (adopting UCC's standard of conspicuousness for express-negligence indemnification doctrine).

8.1.2. All-caps ≠ "conspicuous" – and might be dangerous?

Contract drafters sometimes put entire paragraphs into all-capital letters in the hope of making them "conspicuous." The reader has probably seen examples of this particular disorder in warranty disclaimers and limitations of liability.

But keeping the all-caps going for line, after line, after line, can be self-defeating. A Georgia supreme court justice noted that the drafter of a contract in suit had made the justice's job more difficult — which is not a good look, to put it mildly:

No one should make the mistake of thinking, however, that capitalization always and necessarily renders the capitalized language conspicuous and prominent.

In this case, the entirety of the fine print appears in capital letters, all in a relatively small font, rendering it difficult for the author of this opinion, among others, to read it.

Moreover, the capitalized disclaimers are mixed with a hodgepodge of other seemingly unrelated, boilerplate contractual provisions — provisions about, for instance, a daily storage fee and a restocking charge for returned vehicles — all of which are capitalized and in the same small font. Raysoni v. Payless Auto Deals, LLC, 296 Ga. 156, 766 S.E.2d 24, 27 n.5 (2014) (reversing and remanding judgment on the pleadings) (emphasis and extra paragraphing added).

In a similar vein, the Ninth Circuit noted acerbically:

Lawyers who think their caps lock keys are instant "'make conspicuous" buttons are deluded. … A sentence in capitals, buried deep within a long paragraph in capitals will probably not be deemed conspicuous.

Formatting does matter, but conspicuousness ultimately turns on the likelihood that a reasonable person would actually see a term in an agreement. In re Bassett, 285 F.3d 882, 886 (9th Cir. 2002) (cleaned up, emphasis and extra paragraphing added).

One more: In what might have been a subtle rebuke to the drafter(s) of a contract in suit, the Supreme Court of Texas reproduced an indemnification clause from the contract and added a footnote: "This text appeared in all capital letters in the original, but we have normalized the capitalization for readability." Wagner v. Apache Corp., 627 S.W.3d 277, 280 n.1 (Tex. 2021) (affirming reversal of refusal to compel arbitration; emphasis added).

Even worse, drafting a long block of text in all-caps might actually hurt the drafter's own client. Here's a tweet [since deleted] by Boston-area tech lawyer turned entrepreneur Luis Villa: "Love to see an ALL CAPS AND BOLD section of a contract that is so typographically painful to read that the company’s lawyers didn’t actually proof it, and made a substantive error in my favor as a result." (Emphasis added.)

The drafting tips here, of course, are:

  1. Be judicious about what you put in all-caps.
  2. Don't use too-small a font for language that you want to be conspicuous.

8.1.3. A pathological "don't do this!" example

If you want an example of what NOT to do to make something conspicuous, just glance at (don't even try to read) the following abomination, which is near the very front of a real-estate purchase agreement for a Dallas-area "gentlemen's club":

Section 1.02. Disclaimer and Indemnity. THE PROPERTY SHALL BE CONVEYED AND TRANSFERRED TO PURCHASER “AS IS, WHERE IS AND WITH ALL FAULTS”. EXCEPT FOR THE REPRESENTATIONS, WARRANTIES AND COVENANTS OF SELLER SET FORTH IN ARTICLE V OF THIS AGREEMENT, SELLER DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS, EXPRESS OR IMPLIED, AS TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, DESIGN, QUANTITY, QUALITY, LAYOUT, FOOTAGE, PHYSICAL CONDITION, PERATION, COMPLIANCE WITH SPECIFICATIONS, ABSENCE OR LATENT DEFECTS OR COMPLIANCE WITH LAWS AND REGULATIONS (INCLUDING, WITHOUT LIMITATION, THOSE RELATING TO HEALTH, SAFETY AND THE ENVIRONMENT) OR ANY OTHER MATTER AFFECTING THE PROPERTY AND SELLER SHALL BE UNDER NO OBLIGATION WHATSOEVER TO UNDERTAKE ANY REPAIRS, ALTERATIONS OR OTHER WORK OF ANY KIND WITH RESPECT TO ANY PORTION OF THE PROPERTY. FURTHER, PURCHASER SHALL INDEMNIFY, DEFEND AND HOLD HARMLESS SELLER AND SELLER’S REPRESENTATIVES FROM AND AGAINST ANY CLAIMS OR CAUSES OF ACTION ARISING OUT OF THE CONDITION OF THE PROPERTY BROUGHT BY ANY OF PURCHASER’S SUCCESSORS OR ASSIGNS, OR ANY THIRD PARTY, AGAINST SELLER OR SELLER’S REPRESENTATIVES. INFORMATION PROVIDED OR TO BE PROVIDED BY SELLER IN RESPECT OF THE PROPERTY WAS OBTAINED FROM A VARIETY OF SOURCES. SELLER HAS NOT MADE AN INDEPENDENT INVESTIGATION OF SUCH INFORMATION AND MAKES NO REPRESENTATIONS AS TO THE ASSURACY OR COMPLETENESS THEREOF. PURCHASER HEREBY ASSUMES ALL RISK AND LIABILITY RESULTING FROM THE OWNERSHIP, USE, CONDITION, LOCATION, MAINTENANCE, REPAIR OR OPERATION OF THE PROPERTY, WHICH PURCHASER WILL INSPECT AND ACCEPT “AS IS”. IN THIS REGARD, PURCHASER ACKNOWLEDGES THAT (a) PURCHASER HAS NOT ENTERED INTO THIS AGREEMENT IN RELIANCE UPON ANY INFORMATION GIVEN TO PURCHAWSER PRIOR TO THE DATE OF THIS AGREEMENT, INCLUDING, BUT NOT LIMITED TO, PROMOTIONAL MATERIALS OR FINANCIAL DATA , (b) PURCHASER WILL MAKE ITS DECISION TO PURCHASE THE PROPERTY BASED UPON PURCHASER’S OWN DUE DILIGENCE AND INVESTIGATIONS, (c) PURCHASER HAS SUCH KNOWLEDGE AND EXPERIENCE IN REAL ESTATE INVESTIGATION TO EVALUATE THE MERITS AND RISKS OF THE TRANSACTIONS PROVIDED IN THIS AGREEMENT, AND (d) PURCHASER IS FINANCIALLY ABLE TO BEAR THE ECONOMIC RISK OF THE LOSS OF SUCH INVESTMENT AND THE COST OF THE DUE DILIGENCE AND INVESTIGATIONS UNDER THIS AGREEMENT. IT IS UNDERSTOOD AND AGREED THAT THE PURCHASE PRICE HAS BEEN ADJUSTED BY PRIOR NEGOTIATION TO REFLECT THAT THE PROPERTY IS SOLD BY SELLER AND PURCHASED BY PURCHASER SUBJECT TO THE FOREGOING. Disclaimers similar to the foregoing in form satisfactory to Seller as well as Seller’s reservation of the mineral estate shall be inserted in any and all documents to be delivered by Seller to Purchaser at Closing. This example is from the SEC's EDGAR Web site.

If you're wondering who's responsible for this piece of [work], the names and addresses of the parties' counsel are included in the addresses for notice in section 10.03 of the purchase agreement.

8.1.4. The UCC definition of conspicuousness

The [U.S.] Uniform Commercial Code doesn't apply to all types of transaction, nor in jurisdictions where it has not been enacted. Still, the UCC's definition of "conspicuous," such as in section UCC § 1-201(10) (Texas version) nevertheless provides useful guidance:

"Conspicuous," with reference to a term, means so written, displayed, or presented that a reasonable person against which it is to operate ought to have noticed it.

Whether a term is "conspicuous" or not is a decision for the court.

Conspicuous terms include the following:

(A) a heading in capitals equal to or greater in size than the surrounding text, or in contrasting type, font, or color to the surrounding text of the same or lesser size; and

(B) language in the body of a record or display in larger type than the surrounding text,

or in contrasting type, font, or color to the surrounding text of the same size,

or set off from surrounding text of the same size by symbols or other marks that call attention to the language. Tex. Bus. & Com. Code § 1.201(10) (emphasis and extra paragraphing added).

Courts often adopt the UCC standard for conspicuousness, as explained in the next section.

8.1.5. Courts tend to focus on "fair notice"

In a non-UCC context, the Supreme Court of Texas held that — apart from a possibly-significant exception for litigation-settlement releases — an indemnity provision protecting the indemnitee from its own negligence must be sufficiently conspicuous to provide "fair notice." The supreme court adopted the conspicuousness test stated in the UCC (quoted above), explaining:

This standard for conspicuousness in [Uniform Commercial] Code cases is familiar to the courts of this state and conforms to our objectives of commercial certainty and uniformity. We thus adopt the standard for conspicuousness contained in the Code for indemnity agreements and releases like those in this case that relieve a party in advance of responsibility for its own negligence.

When a reasonable person against whom a clause is to operate ought to have noticed it, the clause is conspicuous.

For example, language in capital headings, language in contrasting type or color, and language in an extremely short document, such as a telegram, is conspicuous. Dresser Indus., Inc. v. Page Petroleum, Inc., 853 S.W.2d 505, 508-09 (Tex. 1993) (citations omitted, emphasis and extra paragraphing added).

The court also pointed out that the fair-notice requirement did not apply to settlement releases: "Today's opinion applies the fair notice requirements to indemnity agreements and releases only when such exculpatory agreements are utilized to relieve a party of liability for its own negligence in advance." Id., 853 S.W.2d at 508 n.1 (emphasis added).

What counts as "conspicuous" will sometimes depend on the circumstances. In still another express-negligence case, the Texas supreme court said that the indemnity provision in question did indeed provide fair notice because:

The entire contract between Enserch and Christie consists of one page; the indemnity language is on the front side of the contract and is not hidden under a separate heading.

The exculpatory language and the indemnity language, although contained in separate sentences, appear together in the same paragraph and the indemnity language is not surrounded by completely unrelated terms.

Consequently, the indemnity language is sufficiently conspicuous to afford "fair notice" of its existence. Enserch Corp. v. Parker, 794 S.W.2d 2, 8-9 (Tex. 1990) (extra paragraphing added).

8.1.6. Proven actual knowledge might be enough for conspicuousness

In Dresser, the Texas supreme court noted an exception to the conspicuousness requirement: "The fair notice requirements are not applicable when the indemnitee establishes that the indemnitor possessed actual notice or knowledge of the indemnity agreement." Dresser, 853 S.W.2d at 508 n.2 (emphasis added, citation omitted).

Note especially the italicized portion of the quotation, which implies that the burden of proof of actual notice or knowledge is on the party claiming indemnification from its own negligence.

In contrast: A federal district judge in Houston granted Enron's motion to dismiss Hewitt Associates' claim for indemnity, on grounds that the contract in question did not comply with the conspicuousness requirement of the "express negligence" rule, namely that an agreement to indemnify a party for the consequences of the party's own negligence must be both express and conspicuous).The judge surveyed prior cases in which actual knowledge (of an indemnity clause) had been sufficiently established, including by ways such as:

  • evidence of specific negotiation, such as prior drafts;
  • through prior dealings of the parties, for example, evidence of similar contracts over a number of years with a similar provision;
  • proof that the provision had been brought to the affected party's attention, e.g., by a prior claim. See Enron Corp. Sav. Plan v. Hewitt Associates, LLC, 611 F.Supp.2d 654, 673-75 (S.D. Tex. 2008).

8.2. Safe harbors: Useful for vague terms

The term "safe harbor" is sometimes used to denote one, non-exclusive way of definitively complying with a requirement; the term is used in, for example, tax law and securities law. See generally, e.g.: • 15 U.S.C. § 77z-2 and § 78u-5 (safe harbors for forward-looking statements); Stephen Fishman, Landlords Must Be In Business to Claim the 20% Pass-Through Tax Deduction (Nolo.com); Safe harbor (Investopedia.com).

Here's a hypothetical example: A lease states that Tenant must pay Landlord: (i) by a cashier's check drawn on a U.S. bank, or (ii) by other payment method reasonably acceptable to Landlord. Here, the first option can be thought of as a safe harbor: Other payment methods might be OK, but Tenant knows that a cashier's check can be used.

We can also define "reverse safe harbors," i.e., things that are clearly out-of-bounds, such as the prohibition on "unreasonable use" of computer systems at § 9.4.6.

8.3. Proxy standards can simplify performance assessment

8.3.1. Example: In a services agreement, required staff qualifications might be more assessable than staff performance.

In a services agreement, a requirement for personnel qualifications can both reduce the likelihood of performance problems and make life simpler for customers to monitor performance — and to seek a remedy for problems that do arise.

Scenario: Suppose that you, the reader, are considering signing a contract with Scalpels 'R Us, LLC, a medical practice, to do lifesaving surgery on a loved one.

  • At a minimum, you'd want to know that the actual surgeon — the specific individual who'd be cutting into your loved one's body — was trained and qualified for the work, right? You wouldn't be satisified with a mere promise from Scalpels 'R Us that "we guarantee that the work will be done correctly, so please don't bother your little head with who will actually perform the surgery."
  • If things were to go wrong, you might well have the legal right to sue Scalpels 'R Us for monetary compensation (damages).
  • But that might be small comfort if the surgeon's screw-up had permanently injured your loved one (or worse).

So: An explicit personnel-qualifications requirement can serve as a reminder to Scalpels 'R Us about whom the provider should pick to do the surgery.

To be sure: A given services project might not be as important as surgery on a loved one. But the expense and inconvenience of work gone wrong can still be a pain in the [neck].

So, for similar reasons, services agreements often include requirements that the services be performed by individuals who are trained and qualified to do the work.

Example: W.L. Gore, the manufacturer of Gore-Tex fabrics, sued both PeopleSoft and Deloitte Consulting for allegedly botching a major software roll-out — one of W.L. Gore's accusations was that Deloitte had promised to assign people to the project who were experienced in the use of PeopleSoft's software, but instead Deloitte had supposedly assigned newbies who "repeatedly consulted PeopleSoft handbooks and called PeopleSoft's customer-service hotline for guidance." See Elizabeth MacDonald, W.L. Gore Alleges PeopleSoft, Deloitte Botched a Costly Software Installation (WSJ.com 1999) (gift article; cleaned up). Unsurprisingly, the parties subsequently settled the case. See Peter Buxbaum, See You In Court (ComputerWorld.com 2001).

Example: In a Houston court of appeals decision, a contractor's repeated safety violations led the customer to meet with a vice president of the contractor and to ask that the contractor's site manager be replaced. The customer eventually terminated the contract because of the contractor's repeated safety problems — and successfully sued the contractor for damages. See James Constr. Gp. v. Westlake Chem. Corp., 594 S.W.3d 722, 749 (Tex. App.—Houston [14th Dist.] 2019) (affirming judgment on jury verdict awarding damages to customer in suit against contractor), aff'd as to a different issue, 650 S.W.3d 392 (Tex. May 20, 2022).] ]

Another reason to include a qualifications clause: Returning to our Scalpels 'R Us hypothetical, suppose that things did indeed go wrong during your loved one's surgery.

  1. A lay jury, untrained in medical science, might have a tough time judging whether or not the surgical procedure had been performed correctly.
  2. So, a "qualifications" clause provides an alternative "proof path" for the injured party: If it turned out that the surgeon didn't possess the necessary training, that would be its own breach of the contract, independent of whether the surgeon did or didn't do the work correctly.

8.3.2. Analogy: Failure of proof of patent infringement

Example: The owner of a pharmaceutical patent, Bristol-Myers Squibb, lost an infringement lawsuit against a defendant because the patent had been drafted in a way that made it physically impossible to show that infringement was taking place:

•  For Bristol to prove infringement at trial, the patent's wording required Bristol to show that, when a patient took the competitor's drug, that drug was converted into a particular chemical compound — in the patient's stomach.

•  Reversing the trial court, the Federal Circuit court remarked that Bristol had simply failed to carry its burden of proof on that point:

We turn next to the question of whether Bouzard monohydrate is actually found in the stomach of patients who ingest cefadroxil DC. One answer is that no one knows — the scientific fact appears to be that there is no known way to actually sample the contents of patients' stomachs at the precise moment and conduct the x-ray diffraction analyses required to ascertain if all 37 lines described in the patent are present. * * *

… Zenith is correct that there was a failure of proof as to whether any crystals, assumed to form in the stomach from ingested cefadroxil DC, literally infringe the '657 claim. In the absence of evidence comparing the '657 claim with the cefadroxil DC after ingestion Bristol has failed to establish any infringing use and therefore we must reverse the district court's conclusion that Zenith's sale of cefadroxil DC induces infringement of the '657 patent. Zenith Labs., Inc. v. Bristol-Myers Squibb Co., 19 F.3d 1418, 1422, 1423 (Fed. Cir. 1994) (reversing judgment of infringement).

8.3.3. Analogy: The per se rule in antitrust law.

antitr-vert-horiz-ct

8.3.4. Analogy: Simplifying a mathematical formula.

High-school algebra students are taught to look for ways of simplifying formulae to make them easier to compute. We can usefully take a similar approach in formulating standards of contract performance.

Example: Consider the formula y = (x2)−3) / (x^2−9​)

8.4. Sunset provisions: Don't draft eternal rights or obligations

It's almost always worth at least considering whether a particular right — or obligation — should have an explicit "sunset" date, i.e., a date certain (or a date-determinable) when the right or obligation comes to an end.

Example: Suppose that ABC Corp. is negotiating a confidentiality agreement under which ABC will be receiving confidential information of XYZ Inc. for a stated purpose. In that situation, ABC might want its confidentiality obligations to come to an end automatically in X number of years, so that it won't have to think about and manage those obligations after that time.

(See § 5.3.5 of the Confidential Information Protocol for more on this particular example.)

8.5. Tables and charts: Better than narrative?

Instead of long, complex narrative language, use tables and charts wherever possible.

Here's a simple example of complex narrative language:

If it rains less than 6 inches on Sunday, then A will pay $3.00 per share, provided that, if it it rains at least 6 inches on Sunday, then A will pay $4.00 per share, subject to said rainfall not exceeding 12 inches, [etc., etc.

Here's the same provision, in table form:

A will pay the amount stated in the table below, based on how much rain falls on Sunday:

AMT. OF RAIN PAYMENT DUE
Less than 6 inches $3.00 per share
At least 6 inches
but less than 12 inches
$4.00 per share

For an example "in the wild," see § 3.12 of this this Pfizer-Rigel collaborative research and license agreement:

3.12     MILESTONE PAYMENTS FOR LICENSED PRODUCTS. Pfizer shall pay Rigel, within sixty (60) days of the completion of each event set forth below ("Event"), the payment listed opposite that Event. [remainder of spaghetti clause omitted]

3.12.1     HUMAN HEALTH PRODUCT

EVENT AMOUNT (DOLLARS)  
(i) Submission of INDA or initiation of human clinical testing in any country (whichever occurs first) $1,000,000.00[a]  
(ii) Commencement of Phase III human clinical trials in any country $2,000,000.00  
(iii) NDA/PLA Filing in any country for human use $4,000,000.00 ^{[a]} DCT note: In the "Amount (Dollars)" column, it'd be better to write $1 million, $2 million, etc. ]

Or you could even try the following, using a bullet-point format:

A will pay the amount stated in the table below, based on how much rain falls on Sunday:

  • Amount of rain: Less than 6 inches.
    Payment due: $3.00 per share
  • Amount of rain: At least 6 inches but less than 12 inches.
    Payment due: $4.00 per share

Which one would you rather read if you were reviewing the contract?

8.6. Title: How will a title look in a list?

8.6.1. Why does it matter? (Might be a needle in a haystack)

Imagine that you're looking at a simple list of titles of a particular company's contracts —

  • Perhaps you're doing due diligence for a financing- or merger transaction and reviewing a long list of the target company's existing contracts.
  • Perhaps you're doing a document review for a lawsuit or arbitration and looking at a similarly-long list of contracts.

Consider the following styles of title:

8.6.2. Title style 1: The word "Agreement" by itself — don't

Title style 1 below is simplicity itself. But it's not especially informative when seen as part of a list of agreement titles:

  Agreement

Example: See an "Agreement" between Amazon and Drugstores.com — you guessed it, the title is simply "Agreement," as in the title just above.

8.6.3. Title style 2: More information

A more-expansive style is fairly typical for contracts:

Agreement and Plan of Merger

8.6.4. Title style 3: Too much information?

A third style is more informative still — but it might be overkill:

AGREEMENT AND PLAN OF MERGER
by and among
Nippon Steel North America, Inc.,
2023 MERGER SUBSIDIARY, INC.,
solely as provided in Section 9.13 of this Agreement,
Nippon Steel Corporation
and
United States Steel Corporation

Dated as of December 18, 2023

The example of title style 3, incidentally, is from the "Agreement and Plan of Merger" (that's the customary title for such contracts) under which Nippon Steel was to acquire U.S. Steel until the transaction was blocked by the U.S. Government.

Caution: From title style 3, be careful about including "Dated as of …" in the title because the contract date might change but the old date might be inadvertently left in the document — especially if there's a rush to get to signature; this would violate the Don't Repeat Yourself principle and could lead to trouble, as discussed at 30.4.

8.6.5. A "listable" condensed title format

Consider drafting a title in a compressed format such as the following, with:

  • shorthand abbreviations for the parties' names; and
  • just the year for the date:

Confidentiality Agreement: MathWhiz-Gigunda (2025)

That would help the title stand out in a list, such as:

– Confidentiality Agreement: MathWhiz-Gigunda (2025)
– Services Agreement: MathWhiz-Gigunda (2025)
– Statement of Work: MathWhiz-Acme (2024)
– Referral Agreement: MathWhiz-SalesRUs (2023)

You get the idea.

8.7. Updates - don't count on them (notes)

This is an example of following the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings): It's dangerous to state in a contract that parties will update anything periodically, because they very well might not. See, e.g., Peter Sluka, A Lifeline for the Stale “Schedule A” (JDSupra.com 2023) (perma.cc) - reviewing cases in which "the contract" stated that the parties would annually update a schedule of assets for use in case of a business divorce, but they never did do any updates ]

8.8. Wording problems to avoid

8.8.1. Provided, that …: Don't. Just don't.

(This is of a piece with the Spaghetti Rule.)

Instead of prolonging a sentence with "provided, that …": Break the provision into separate sentences (or even separate paragraphs).

Example:

    Alice will pay Bob USD $100 no later than December 25; provided, however, that if Alice pays Bob no later than December 21, the amount to be paid will be $75.

    (1) Except as provided in subdivision (2) below, Alice is to pay Bob USD $100 no later than December 25.

(2) If Alice pays Bob no later than December 21, then the amount to be paid will be $75.
[This is an exception to the active-voice rule because the sentence already says "Alice pays …." Consider also using a table.]

Another example: Take a look at section 2.15 of the contract by which Verizon took over Yahoo: It makes you want to cry out, "My kingdom for a period!"

(a) (i) Each material lease or sublease (a “Lease”) pursuant to which Seller (to the extent related to the Business) or any of the Business Subsidiaries leases or subleases real property (excluding all leases or subleases for data centers) (the “Leased Real Property”) is in full force and effect and Seller or the applicable Business Subsidiary has good and valid leasehold title in each parcel of the Leased Real Property pursuant to such Lease, free and clear of all Encumbrances other than Permitted Encumbrances, except in each case where such failure would not, individually or in the aggregate, reasonably be expected to have a Business Material Adverse Effect and (ii) there are no defaults by Seller or a Business Subsidiary (or any conditions or events that, after notice or the lapse of time or both, would constitute a default by Seller or a Business Subsidiary) and to the Knowledge of Seller, there are no defaults by any other party to such Lease (or any conditions or events that, after notice or the lapse of time or both, would constitute a default by such other party) under such Lease, except where such defaults would not, individually or in the aggregate, reasonably be expected to have a Business Material Adverse Effect.

Instead, follow the Spaghetti Rule (2.5): Break the provision into separate sentences (or even separate paragraphs).

Example:

    Alice will pay Bob USD $100 no later than December 25; provided, however, that if Alice pays Bob no later than December 21, the amount to be paid will be $75.

    Alice is to pay Bob: (1) USD $75 if paid no later than December 21; or (2) in any case, $100 no later than December 25.

The Verizon-Yahoo sentence calls to mind the early English translations of some of the Christian gospels, which literally translated the Greek conjunction καί (kai, "and") instead of using it as a separator, almost a punctuation mark, as the Greek-language authors had done — which led to some interesting run-on translations. See, e.g., Multifunctionality of δέ, τε, and καί (chs.harvard.edu; undated).

See, for example, the Gospel of Mark, chapter 10, verses 33-34, in an almost-literal, word-for-word translation from the Greek "original":

Lo, we go up to Jerusalem and the Son of Man shall be delivered to the chief priests and to the scribes and they shall condemn him to death and shall deliver him to the nations and they shall mock him and scourge him and spit on him and kill him and the third day he shall rise again.

(Emphasis added.) The King James Version's translation of that passage, published in 1611, didn't change much:

Saying, Behold, we go up to Jerusalem; and the Son of man shall be delivered unto the chief priests, and unto the scribes; and they shall condemn him to death, and shall deliver him to the Gentiles:

And they shall mock him, and shall scourge him, and shall spit upon him, and shall kill him: and the third day he shall rise again.

Contrast the above translations with the modern New International Version (NIV) translation of the same passage:

"We are going up to Jerusalem," he said, "and the Son of Man will be delivered over to the chief priests and the teachers of the law. They will condemn him to death and will hand him over to the Gentiles, who will mock him and spit on him, flog him and kill him. Three days later he will rise."

And from The Message:

He took the Twelve and began again to go over what to expect next. "Listen to me carefully. We’re on our way up to Jerusalem. When we get there, the Son of Man will be betrayed to the religious leaders and scholars. They will sentence him to death. Then they will hand him over to the Romans, who will mock and spit on him, give him the third degree, and kill him. After three days he will rise alive."

The two shorter-sentence translations seem more readable, right?

Go ye and do likewise ….

8.8.2. Review — meaning what, exactly?

Idaho's supreme court affirmed a divorce court's holding that, in a divorce settlement agreement, the term "[s]pousal support shall be reviewed every two years" was "so vague, uncertain, indefinite, and incomplete that it is unenforceable." Smith v. Smith, No. 50184 (Id. Dec. 19, 2024).

8.9. Reduce - better than "minimize"

A cautious drafting approach is to use the term reduce in lieu of minimize, against the chance that an adversary might later claim that "minimization" didn't actually occur, i.e., that the reduction that was actually achieved was not the greatest amount of reduction possible.

(Ditto for using the term increase, or enhance, in lieu of maximize.)

8.10. Reviewing drafts from The Other Side

Many contract drafters spend at least as much time reviewing others' draft contracts as they do in drafting their own. Here are a few pointers.

1.  Do ask the other side for an editable Microsoft Word document. And if you send the other side a draft or a redline, don't send a PDF or a locked Word- or PDF document — doing so implicitly signals a lack of trust; between lawyers especially, it's more than a little lacking in professional courtesy.

2.  Do save your own new draft immediately: Open the other party's draft in Microsoft Word and immediately save it as a new document whose file name reflects your revision. Example of file name: "Gigunda-MathWhiz-Services-Agreement-rev-2020-08-24.docx"

3.  Do add a running header to show the revision date: Add a running header to the top right of every page of your revision to show the version date and time (typed in, not an updatable field) (and matching the date in the file name). Example of running header: "REV. 2020-08-24 18:00 CDT" (note the use of military time for clarity).

4.  Don't revise the other side's language just for style: It's not worth spending scarce negotiation time — and it won't go over well with either the other side or the client — to ask the other side to change things that don't have a substantive effect.

Example: Suppose that the other side's draft contract leads off with "WITNESSETH" and a bunch of "WHEREAS:" clauses. As a well-trained drafter, you'd prefer to have a simple background section without all the legalese (see 29.3 for more details). Let it be: If the other side's "WHEREAS:" clauses are substantively OK, don't revise those clauses just because you (properly) prefer to use a plain-language style.

5.  But do break up "spaghetti clause" provisions in another party's draft to make the provisions easier for your client to review — and to help you to do a thorough review with lower risk of the MEGO factor ("Mine Eyes Glaze Over"). After you save a new Word document (see #2 above), do the following:

  • Double-space the entire text (except signature blocks and other things that should be left in single-space) if not that way already.
  • Break up long sentences, as explained in more detail at 8.11.8.

6.  And do add an explanation for the added white space: In the agreement title at the top of the draft, add a Word comment bubble along the lines of the following:

To make it easier for my client to review this draft, I'm taking the liberty of double-spacing it and breaking up some of the longer paragraphs.

(It's hard for another lawyer to object to your doing something to make things easier for your client, right?)

The author has been doing this for years and has only once gotten pushback on that point from the original drafter — in fact, the parties pretty much always end up eventually signing a double-spaced version with broken-up paragraphs, as opposed to the original wall-of-words format.

7.  Never gratuitously revise another party's draft to favor the other party — even if your revision seems to make business sense — and certainly not if the revision might someday put your client at a disadvantage or give up an advantage.

Example: Suppose that this time your client MathWhiz is a customer, not a vendor. A vendor that wants to do business with MathWhiz has sent MathWhiz a draft contract. The draft calls for MathWhiz to pay the vendor's invoices "net 90 days" — that is, the vendor expects MathWhiz to pay in full in 90 days.

  • You know that vendors like to be paid as soon as they can, so you suspect that the vendor's 90-day terms are a mistake, perhaps left over from a previous contract; i.e., the vendor's contract drafter might have taken a previous contract and changed the names, but without changing the 90-day terms to, say, 45-day terms.
  • You know that MathWhiz, like all customers, pretty-much always prefer to hold onto its cash for as long as they can — not least because delaying payment can give a customer a bit of extra leverage over its suppliers.
  • You also know that MathWhiz usually pays net-45 and is even willing to pay net-30 if the other terms are acceptable.

Let it be — don't take it on yourself to unilaterally change the vendor's net-90 terms to net-45, because that would require MathWhiz to pay the vendor's invoices earlier than the vendor asked in its draft contract.

The vendor's drafter might later embarrassedly confess to having overlooked the net-90 terms and ask to change it to net-30. That gives MathWhiz an opportunity to be gracious, which will usefully signal to the vendor that MathWhiz might well be a Good Business Partner (which most companies like to see).

This is also a lesson about the possible danger of reusing an existing contract without carefully reviewing it to identify — and possibly strip out — any concessions that were made in the course of previous negotiations.

8.11. Reviewing? Help The Other Side — but not too much

Many contract drafters spend at least as much time reviewing others' draft contracts as they do in drafting their own. Here are a few pointers.

Important: Many of these tips — but not all — apply equally to reviewing a "precedent" contract from your law firm, as in, if the partner giving you the drafting assignment tells you to "start with the contract from the XYZ deal that we did last year." (Also important: When this is the case, keep in mind that in the XYZ deal, your firm's client might have made concessions that your client in the new deal doesn't want to make, at least not to start.)

8.11.1. Do ask the other side for an editable Microsoft Word document

And if you send the other side a draft or a redline, don't send a PDF or a locked Word- or PDF document — doing so implicitly signals a lack of trust; between lawyers especially, it's more than a little lacking in professional courtesy.

8.11.2. Do save to a new draft immediately

Open the other party's draft in Microsoft Word and immediately save it as a new document whose file name reflects your revision.

Example of file name: "Gigunda-MathWhiz-Services-Agreement-rev-2020-08-24.docx"

8.11.3. Do add a running header to show the revision date

Add a running header to the top right of every page of your revision to show the version date and time (typed in, not an updatable field) (and matching the date in the file name). Example of running header: "REV. 2020-08-24 18:00 CDT" (note the use of 24-hour time for clarity).

8.11.4. Do add marginal line numbers

To make discussion easier on a markup call with screen-sharing, use Microsoft Word's line-numbering feature with continuous line numbering — that is, numbering continues sequentially on each new page. You'll save time because it's easier to refer to "line X" than to "section 14.3(a)(2)(F)."

Here's a (sanitized) example from an actual draft NDA:

You might want to print the draft to PDF and circulate that along with the Word document, so that everyone has the same line numbering in the PDF. (Sometimes Microsoft Word seems to display things differently on different computers.)

8.11.5. Redline your changes

Always use "Track Changes" in Microsoft Word (or whatever word processor you use). See 3.15 for why it's vital to do this to avoid legitimately angering the other side.

To show how redlining typically works, consider a hypothetical contract negotiation between two parties whose lawyers are "Fred" and "Ginger," respectively:

  1. Fred emails Ginger Version 1 of a draft agreement, very preferably as an editable Microsoft Word document — it's bad form to email the other side a PDF or a locked Word document.
  2. Using Microsoft Word, Ginger revises Version 1 using Word's "Track Changes" feature (alternatively, Word's "Compare Documents" feature) to show the proposed changes, then saves the revised document as Version 2.
  3. Ginger emails her (revised) Version 2 to Fred.
  4. Fred repeats what Ginger did to create a new Version 3 and emails Version 3 to Ginger.
  5. Rinse and repeat until Fred's and Ginger's respective clients have reached agreement.

Pro tip: It can also be helpful to explain, in comments — for example, in Microsoft Word comment bubbles — the reasoning behind specific changes, to save time in negotiation conference calls.

Pro tip: In the final, signature version, drafters should consider including, in the "general provisions," a certification that neither party has made surreptitious changes to the signature version (see Protocol 3.15).

8.11.6. Don't do The Other Side's job for them

Never gratuitously revise another party's draft to favor the other party:

  • not even if your revision seems to make business sense; and
  • certainly not if the revision might someday put your client at a disadvantage or give up an advantage.

(This is different from the "hamburger for the guard dog" rule at 8.21.)

Example: Suppose that this time:

  • Your client MathWhiz is a customer, not a vendor.
  • A vendor that wants to do business with MathWhiz has sent MathWhiz a draft contract.
  • The draft calls for MathWhiz to pay the vendor's invoices "net 90 days" — that is, the vendor expects MathWhiz to pay in full in 90 days; see 4.13.3. (That'd be really unusual for a vendor contract form.)
  • You know that vendors like to be paid as soon as they can. You suspect that the vendor's 90-day terms are a mistake, perhaps left over from a previous contract: The vendor's contract drafter might have taken a previous contract and changed the names, but without changing the 90-day terms to, say, 45-day terms.
  • You know that MathWhiz, like all customers, pretty-much always prefer to hold onto its cash for as long as they can — not least because delaying payment can give a customer a bit of extra leverage over its suppliers.
  • You also know that MathWhiz usually pays net-45 and is even willing to pay net-30 if the other terms are acceptable.

Let it be — don't take it on yourself to unilaterally change the vendor's net-90 terms to net-45. You don't want to raise the bar 8.13 for MathWhiz by requiring MathWhiz to pay the vendor's invoices earlier than the vendor had even asked for in its own draft contract.

To be sure: The vendor's drafter might later embarrassedly confess to having overlooked the net-90 terms and ask to change it to net-30. That's no bad thing:

  • It gives MathWhiz an opportunity to ask for a concession in return.
  • It also gives MathWhiz an opportunity to be gracious. Graciousness can send the message that MathWhiz might well be a Good Business Partner — and most companies like dealing with Good Business Partners.

This is also a lesson about the possible danger of reusing an existing contract without carefully reviewing it to identify — and possibly strip out — any concessions that were made in the course of previous negotiations. (See 30.2 for more on this subject.)

8.11.7. Don't revise the other side's language just for style

It's not worth spending scarce negotiation time — and it won't go over well with either the other side or the client — to ask the other side to change things that don't have a substantive effect.

Example: Suppose that the other side's draft contract leads off with "WITNESSETH" and a bunch of "WHEREAS:" clauses. As a well-trained drafter, you'd prefer to have a simple background section. You'd have left out the legalese. (See 29.3 for more details.)

Let it be: If the other side's "WHEREAS:" clauses are substantively OK, then don't revise those clauses just because you (properly) prefer to use a plain-language style.

8.11.8. But do break up "spaghetti paragraph" provisions

Another party's draft is likely to have long spaghetti paragraphs (2.5). That might be accidental — or perhaps not.

So, break up spaghetti paragraphs into short, BLUF sound bites:

  • It'll make the clauses easier for your client to review.
  • It'll also help you to do a thorough review with lower risk of the MEGO factor ("Mine Eyes Glaze Over").

Expand single-spaced paragraphs: After you save a new Word document (see 8.11.2 above), use 1.5-line spacing, or even double-spacing, for the entire text if not that way already.

(Exception: Stick with single-spacing for signature blocks and other text blocks that would look strange with more line spacing.)

Break up long sentences, as explained in more detail at 2.5.

(For an example of how that might look, see the screen shot at 8.11.4.)

Add an explanation for the added white space: In the agreement title at the top of the draft, add a Word comment bubble along the lines of the following:

To make it easier for my client to review this draft, I'm taking the liberty of double-spacing it and breaking up some of the longer paragraphs, without redlining those particular changes.

It's hard for another lawyer to object to your doing something to make things easier for your client, right?

(Again, for an example of how that might look, see the screen shot at 8.11.4.)

DCT note: I've been doing this for many years and have only twice gotten pushback on that point from The Other Side. For that matter, the parties pretty much always end up eventually signing a double-spaced version with broken-up paragraphs, as opposed to the original spaghetti-clause format.

8.11.9. Don't delete emailed drafts

First drafts and redlined revised drafts are almost universally exchanged by email. Here's why you should always keep every draft sent to, or by, (i) the other side of a deal or (ii) your client:

  1. Email storage space is cheap.
  2. Deleting emails relating to a transaction or relationship means that you don't have a complete documentary history — and the other side might have emails that you don't, possibly giving them an advantage.
  3. If you think you've deleted "problematic" emails, Murphy's Law — "anything that can go wrong, will go wrong" — says you could be deluding yourself: Someone else could have a copy (possibly forwarded), and/or there could be backup copies somewhere that would turn up in litigation; it's far better to have your own complete set.
  4. In litigation, it's low-hanging fruit for the other side to accuse your client of destruction of evidence ("spoliation"):
    • Trial counsel love to be able to make such accusations, because jurors might not understand the complexities of the case, but they will understand "Cover-up!!"
    • If a judge gives jurors an adverse-inference instruction about your client's spoliation of evidence, that can be big trouble.
    • And in an extreme spoliation case, the judge might take even-more drastic action such as precluding certain claims and/or defenses or even striking your client's pleadings.

8.11.10. Pro tip: Explain revisions, using Word comment bubbles

It can also be helpful to explain, in comments — for example, in Microsoft Word comment bubbles — the reasoning behind specific changes, to save time in negotiation conference calls.

8.11.11. Review questions

1.  Come up with a list of (up to) five noteworthy points in this section 8.11.

2.  Did anything in this chapter remind you of anything you've ever experienced (or just seen) yourself?

8.12. R.O.O.M.: Root Out Opportunties for Mistakes

R.O.O.M. = Root Out Opportunities for Mistakes (or, Misunderstandings)

Example: Consider the tragic collision near Reagan National Airport in Washington D.C., between an Army helicopter and an American Airlines flight, killing everyone aboard both aircraft. The New York Times reports:

One error did not cause the worst domestic crash in the United States in nearly a quarter-century. Modern aviation is designed to have redundancies and safeguards that prevent a misstep, or even several missteps, from being catastrophic. On Jan. 29, that system collapsed.

“Multiple layers of safety precautions failed that night,” said Katie Thomson, the Federal Aviation Administration’s deputy administrator under President Joseph R. Biden Jr.

(Alternatively: R.O.O.F. = Root Out Opportunities for F[oul]-ups)

8.13. Raising the bar: Be careful!

A well-meaning contract drafter might write lofty standards of business conduct. Those standards might, in practice, turn out to be tough for the client to comply with — or even to remember. This can come back to bite the client, as shown in the examples below.

8.13.1. Tilly's Inc. doesn't comply with its own too-strict amendment requirement for employment agreements

Example: Multiple-signature requirements: Tilly's, Inc. and World of Jeans & Tops, Inc. ("Tilly's") had an employee sign an employment agreement (the "2001 employment agreement").

  • The 2001 employment agreement included a provision requiring arbitration of disputes (concerning arbitration, see 21.1), but the arbitration provision had a carve-out for statutory claims, meaning that the employee was allowed to file a lawsuit for such claims in court and didn't need to arbitrate them.
  • Importantly for our purposes here: The 2001 employment agreement also stated that any modifications to the agreement's terms would need the signatures of three company executives: The president, senior vice president, and director of human resources.
  • Fast forward to 2005: The company had its employees sign an acknowledgement of receipt of an employee handbook containing a revised arbitration provision — which didn't contain the carve-out for statutory claims and thus was more favorable to the company.
  • But the employees' signed acknowledgements didn't contain the three executive signatures needed to modify the 2001 employment agreement. (I'd guess that the company's HR people simply didn't remember that three signatures were required.)
  • So: Because the company had previously set the bar so high for modifying the 2001 employment agreement, the company found itself facing high-stakes, class-action litigation, whereas it had thought that it would be arbitrating individual, low-stakes claims, one by one. See Rebolledo v. Tilly's, Inc., 228 Cal. App. 4th 900, 924, 175 Cal. Rptr. 3d 612 (Cal. App. 4th Div. 2014) (affirming denial of motion to compel arbitration).

To like effect, in a 2025 California case:

  • A worker signed an employment agreement that included a mandatory arbitration provision that included a prohibition of class-action arbitration.
  • At the end of the document, the agreement form said, "The parties acknowledge and agree [sic] that each has read this agreement carefully and understand that by signing it, each is waiving all rights to a trial or hearing before a judge or jury of any and all disputes and claims subject to arbitration under this agreement."
  • The company never signed the worker's agreement.
  • After leaving the company, the worker filed a class-action lawsuit alleging wage-and-hour violations .
  • The company move to compel arbitration and to strike the class-action claims.

The district court ruled that the arbitraiton agreement was not binding on the worker because the company hadn't signed the agreement; the appeals court affirmed. See Pich v. LaserAway, LLC, No. B331219, slip op. at 5-7 & n.4 (Cal. App. Jan 28, 2025) (unpublished; affirming denial of motion to compel arbitration, citing cases).

8.13.2. Confidential information could be left unmarked

If a confidentiality agreement is drafted to favor the recipient of information, the agreement might state that discloser information isn't considered confidential if the information isn't marked as such when provided to the recipient. That's dangerous because:

  • the NDA didn't need to be so strict about marking; and
  • in more than one case, such NDA strictness about marking resulted in the discloser forfeiting any chance of asserting trade-secret rights in the information it provided to the recipient (see the notes at § 5.3.15).

8.13.3. Information might not be purged

Example: Information-purge requirements: Confidentiality agreements often require the party receiving confidential information to purge — return or destroy — all copies of the information in its possession upon termination of the agreement. That's dangerous because the recipient might forget to do the purge; moreover, a complete purge might be costly and burdensome, not to mention depriving the recipient of a record copy of what it received from the discloser. (See 5.4 for more details and suggestions for dealing with these problems.)

8.13.4. Blank spaces might not get filled in

Example: Blank spaces, not filled in: See if you can avoid leaving blank spaces to be filled in — such as the effective date of the Con­tract, see 29.4.2 — because Murphy's Law ("anything that can go wrong, will go wrong") says that the parties will forget to fill in the blank.

Example: Spaces to be initialed, that aren't: Here's a variation on the blank-spaces problem: A contract drafter might add blank lines by particular provisions, to be initialed by one or more signers to acknowledge understanding tose provisions — but what if a signer doesn't initial in the spaces provided? (See 29.6.2 for more discussion of this problem.)

These examples illustrate the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings).

8.14. Poking the bear: Not a great idea

Do you really need that clause you want to propose? Or could it backfire on you?

8.14.1. The Conan O'Brien example

Some of you might remember that TV talk-show host Conan O'Brien's stewardship of The Tonight Show (now hosted by Jimmy Fallon) proved disappointing to NBC. - The network decided to move former host Jay Leno back into the 11:35 p.m. (Eastern) time slot and bump Conan back to 12:05 a.m. This led Conan to want to leave the show and start over on another network — but if he had, he would arguably have been in breach of his contract with NBC.

Conan's contract apparently did not state that The Tonight Show would always start at 11:35 p.m. Conan's lawyers were roundly criticized for that alleged mistake. But then wiser heads pointed out that Conan's lawyers might have intentionally not asked for a locked-in start time:

–  The Tonight Show had started at 11:35 p.m. for decades; Conan's lawyers could have plausibly argued that this start time was part of the essence of The Tonight Show, and thus was an implied part of the contract.

–  Suppose that Conan's lawyers had asked for the contract to lock in the 11:35 p.m. start time of The Tonight Show — but that NBC had refused. A court might then have interpreted the contract as providing that NBC had at least some freedom to move the show's start time.

–  And for that matter, NBC might have responded by demanding a clause affirmatively stating that NBC was free to choose the start time for The Tonight Show. Given that NBC had more bargaining power than Conan at that point, Conan might then have had no choice but to agree, given that he wanted NBC to appoint him as the host of the show. And in that case, there'd be no question that NBC had the right to push the start time of the show back to 12:05 p.m.

Ultimately, Conan and NBC settled their dispute; the network bought out Conan's contract for a reported $32.5 million. This seems to suggest that NBC was concerned it might indeed be breaching the contract if it were to push back The Tonight Show to 12:05 a.m. as it wanted to do.

As an article in The American Lawyer commented:

"Sometimes in contract negotiations it's better not to ask," says Jonathan Handel ….

* * *

… If O'Brien had asked that the 11:35 p.m. time slot be spelled out in any agreement—and had NBC refused—the red pompadoured captain of "Team Coco" would be in a weaker position in the current negotiations.

"If you ask and are refused, or even worse, if you ask and the other side pushes for a 180, such as a time slot not being guaranteed, you can end up with something worse," [attorney Jonathan] Handel adds.

Without having their hands bound by language in the contract on when "The Tonight Show" would air, O'Brien's lawyers are in a better position to negotiate their client's departure from NBC. Brian Baxter, Legal Angles Abound as Conan-NBC Standoff Nears Endgame (AmLaw Daily Jan. 19, 2010) (extra paragraphing added) ] It could well be that Conan's lawyers did an A-plus job of playing a comparatively-weak hand during the original contract negotiations with NBC.

The lesson: Be careful what you ask for in a contract negotiation — if the other side rejects your request but you do the deal anyway, that sequence of events might come back to haunt you later.

Note

8.14.2. The law might be on your side if you stay silent.

The scene:

  • You're in a contract negotiation, representing The Good Guys Company.
  • The other side, Nasty Business Partner Inc., insists on requiring The Good Guys to get NBP's consent before assigning the agreement.
  • Nasty Business Partner has all the bargaining power; the Good Guys decide they have no choice but to go along.

Trying to salvage the situation, you ask Nasty Business Partner for some additional language: "Consent to assignment may not be unreasonably withheld, delayed, or conditioned." But Nasty Business Partner refuses. Have you just hurt your client?

In some jurisdictions — by no means all — The Good Guys might otherwise have benefited from a default rule that Nasty Business Partner Inc. had an implied obligation not to unreasonably withhold consent to an assignment of the contract; see Note for discussion.

But you asked for an express obligation — only to have Nasty Business Partner reject the request — and The Good Guys signed the contract anyway.

A court might therefore conclude that the parties had agreed that Nasty Business Partner would not be under an obligation not to unreasonably withhold its consent to assignment — that NBP could grant or withhold its consent in its sole discretion. That's pretty much what happened in two different state supreme-court cases, one in Alabama and the other in Oregon. See Shoney's LLC v. MAC East, LLC, 27 So.3d 1216, 1220-21 (Ala. 2009); Pacific First Bank v. New Morgan Park Corp., 876 P.2d 761 (Or. 1994).

8.15. No: When you just can't say it

Your client might not have the bargaining power to get its way in contract negotiations. When that's the case, you have to try to come up with other ways to help protect the client's legal- and business interests.

Imagine, for example, that your client is a customer that is negotiating a master purchasing contract with a vendor.

  • Your customer client would love to flatly prohibit the vendor from raising prices without the customer's consent. But the vendor's negotiators won't go along with such a prohibition.
  • The vendor would love to have the unfettered discretion to raise your customer client's prices whenever the vendor wants. But your client's business people are insisting on having at least some protection on that score.

What to do? In no particular order, here are some approaches that you could try.

8.15.1. Non-discrimination language?

A non-discrimination requirement at least brings a bit of overall-market discipline into the picture.

Example: "Provider will not increase the prices it charges to Customer except as part of a non-targeted, across-the-board pricing increase by Provider, applicable to its customers generally, for the relevant goods or services."

Comment: The Provider might want to qualify this language, so as to limit how general a price increase must be before it can be applied to the Customer.

8.15.2. Advance warning, or -consultation?

An advance-warning or advance-consultation requirement can buy time for its beneficiary to look around for alternatives (assuming of course that the contract doesn't lock in the beneficiary somehow, for example with a minimum-purchase requirement or a "requirements" provision).

Example: Provider will give Customer at least X [days | months] advance notice of any increase in the pricing it charges to Customer under this Agreement.

8.15.3. Transparency requirement?

Requiring a party to provide information justifying its action, upon request, can force that party to think twice about doing something, even though it technically is free to do it.

Here's an example:

If requested by Customer within X days after notice of a pricing increase, Provider will seasonably provide Customer with documentation showing, with reasonable completeness and accuracy, a written explanation of the reason for the increase, including reasonable details about Provider's relevant cost structures relevant to the pricing increase.

Customer will maintain all such documentation in confidence any non-public information in such explanation, will not disclose the non-public information to third parties, and will use it only for purposes of making decisions about potential purchases under this Agreement.

Comment Note the if-requested language, which relieves the vendor from the burden of continually managing this requirement — although a smart vendor would plan ahead and have the required documentation ready to go.

8.15.4. Draw the thorn from the lion's paw?

When a party makes tough contract demands, it could be because the party has been burned before. Institutionally, it may still "feel the pain" of a bad experience; its response is to roar at other counterparties.

The counterparty being roared at can try to find out why the lion is roaring. If it can identify the source of the pain, it might be able to figure out another way to make it better, without undertaking burdensome obligations. (The allusion here, of course, is to the ancient folk tale about Androcles and the lion.)

8.15.5. Cap the financial exposure for the onerous provision?

A party with bargaining power will often demand that its counterparty agree to an onerous provision. In response, the counterparty could ask the first party to agree to a dollar cap on the amount of the counterparty's resulting financial exposure, e.g., capping the amount of money that the counterparty would be required to spend or the liability that it might someday face.

If the first party agrees, the onerous provision might look less dangerous to the counterparty than it would with the prospect of unlimited expense and/or liability.

(This is a variation on the old saying: When in doubt, make it about money.)

8.15.6. Impose time limits?

When a party asks its counterparty to agree to an onerous contract provision, the counterparty might try to make its business risk more manageable by imposing time limits on the onerous provision, such as:

  • specified start- or end dates; and/or
  • specified duration(s).

For example, if a party demands an oppressive indemnity obligation, the counterparty might counter by asking for a time limit on claims covered by the indemnity.

Or if a party demands a cap on pricing increases, or a most-favored-customer clause, the counterparty could counter with time limits on those as well.

8.15.7. Explain why the provision hurts the demanding party?

A counterparty can to try to explain to a demanding party why, in the long run, the onerous provision being demanded would ultimately cause problems for the demanding party.

8.15.8. Package as part of a premium offering?

Suppose that a smallish supplier is regularly asked by its customers to agree to an onerous contract provision (e.g., an extended warranty). If the supplier plans ahead, it can package the onerous provision as part of a higher-priced premium offering — with the relevant contract language being written in a way the supplier knows it can support.

This approach has a distinct advantage: The bargaining over whether to give a customer the premium offering is no longer about legal T&Cs: it becomes a negotiation about price. This means the supplier's legal people might not even have to get involved — which often can be crucial when sales people are working hard to close deals before the shot clock runs down on the fiscal quarter.

Another advantage: The supplier might well score points with customers for anticipating their needs and offering a solution for them.

A third advantage: Some customers are far less price-sensitive than they are service-sensitive, in that they're willing to pay more if they feel they're getting premium treatment. (Airlines sell a lot of first‑ and business-class seats, whose high prices supposedly subsidize lower-cost fares for us peasants back in steerage.)

8.15.9. Maybe it's simply worth the business risk?

The supplier and its lawyer should assess the actual business risk of agreeing to the customer's request — in the real world it might not be as big a problem as the supplier imagines.

That's always the client's call, of course — but for legal matters, the client might want the lawyer's view about what's being asked; I often use the phrase, "[The provision in question] probably represents an acceptable business risk."

Caution: In such a situation, the lawyer should pay attention to whether s/he is being asked to give legal advice or business advice; the latter could jeopardize the attorney-client privilege (8.30).¯

8.16. Own-goal clauses

A drafter can sometimes inadvertently harm a client by "cleverly" including onerous provisions to benefit the client — but then when the roles later do get reversed, the client gets impaled, so to speak, on the onerous provisions.

8.16.1. Example: Tilly's raises the bar — and then fails to clear it

Tilly's, Inc. and World of Jeans & Tops, Inc. ("Tilly's") had an employee sign an employment agreement (the "2001 employment agreement") containing an arbitration provision. See Rebolledo v. Tilly's, Inc., 228 Cal. App. 4th 900, 924, 175 Cal. Rptr. 3d 612 (Cal. App. 4th Div. 2014) (affirming denial of motion to compel arbitration).

  • The 2001 employment agreement included a carve-out for statutory claims (which thus could be brought in court, not in arbitration).
  • Importantly: The 2001 employment agreement also stated that any modifications to the agreement would need the signatures of three executives: The company's president; senior vice president; and director of human resources.
  • Then in 2005, the company had its employees sign an acknowledgement of receipt of an employee handbook containing a different arbitration provision — which didn't contain the carve-out for statutory claims.

If that different arbitration provision had gone into effect, then Tilly's would have had more protection from employee class-action lawsuits.

BUT: The signed 2005 acknowledgement didn't contain the three executive signatures needed to modify the 2001 employment agreement.

Summing up: Tilly's had set the bar very high for modifying the 2001 employment agreement — but then it hadn't cleared the bar itself to give itself more protection against employee class-action litigation. So, the company found itself facing high-stakes litigation by a class of employee plaintiffs — whereas it had thought it would be arbitrating low-stakes claims on a one-by-one basis.

(For more about class-action waivers in arbitration provisions — which was Tilly's intention in the 2005 acknowledgement — see Option 21.1.23.)

8.17. Optional - does that mean opt-in, or -out?

DCT note: I once reviewed a supplier's terms-of-service Web page with a provision addressing the insurance coverage that the supplier agreed to maintain. The provision's heading was "INSURANCE [OPTIONAL]"

Question: Did this mean that the supplier was required to obtain insurance unless the customer agreed otherwise? Or vice-versa?

8.18. Humility (in drafting) (notes)

Judges seem to appreciate a bit of verbal (as in, relating to words) humility in contracts; they’ve been known to look askance at high-handed statements in contracts that purport to bind courts such as, e.g., "the parties hereby elect not to be bound by any state laws" (when maritime law would apply). See, e.g., Barranco v. 3D Sys. Corp., 952 F.3d 1122, 1130 (9th Cir. 2020) (parties can’t contractually force a court to grant an injunction) (citing cases); AM General Holdings LLC v. The Renco Group, Inc., No. 7639-VCN, slip op. at 10, text acc. nn.19-20 (Del. Ch. Dec. 29, 2015) (same).

8.18.1. Example: Agreed injunctive relief

In its Barranco opinion, the Ninth Circuit rejected the notion that a court was required to issue an injunction if the parties had agreed to it.

We hold that the terms of a contract alone cannot require a court to grant equitable relief. In doing so, we adopt the accepted rule of our sister circuits that have addressed the question. Barranco, 952 F.3d at 1130 (citing cases); see also, e.g., Steven Gordon, Non-Disclosure Agreements and Trade Secrets: 12 Points to Consider (JDSupra.com 2021).

Likewise, the Delaware chancery court disregarded a contractual stipulation of irreparable harm:

Parties sometimes … agree that contractual failures are to be deemed to impose the risk of irreparable harm. Such an understanding can be helpful when the question of irreparable harm is a close one.

Parties, however, cannot in advance agree to assure themselves (and thereby impair the Court’s exercise of its well-established discretionary role in the context of assessing the reasonableness of interim injunctive relief) the benefit of expedited judicial review through the use of a simple contractual stipulation that a breach of that contract would constitute irreparable harm.

[In footnote 20 the court added:] In part, this is simply a matter that allocation of scarce judicial resources is a judicial function, not a demand option for litigants. AM General Holdings LLC v. The Renco Group, Inc., No. 7639-VCN, slip op. at 10, text acc. nn.19-20 (Del. Ch. Dec. 29, 2015) (denying request for preliminary injunction) (footnotes omitted, extra paragraphing added).

Relatedly: In a different context, another court noted: "Since federal courts are not rubber stamps, parties may not, by private agreement, relieve them of their obligation to review arbitration awards for compliance with § 10(a) [of the Federal Arbitration Act]." Hoeft v. MVL Group, Inc., 343 F.3d 57, 64 (2d Cir. 2003) (reversing vacatur of arbitration award) (emphasis and extra paragraphing added). Accord: In re Wal-Mart Wage & Hour Employment Practices Litigation, 737 F.3d 1262, 1267-68 (9th Cir. 2013).

Similarly, Delaware's supreme court affirmed a court of chancery holding that a "conclusive and binding" provision in a corporation's charter was invalid under Delaware corporate law because, said the supreme court, the provision "strips the Court of Chancery of its authority to apply established standards of review to breach of fiduciary duty claims." CCSB Fin. Corp. v. Totta, 302 A.3d 387, 400 (Del. 2023); see also, e.g., Kodiak Bldg. Partners, LLC v. Adams, No. 2022-0311-MTZ, slip op. (Del. Ch. Oct. 6, 2022) (denying Kodiak's motion for preliminary injunction; contract's language stating that "its restrictive covenants are reasonable, and waiving a defense that they are not, does not preclude this Court from performing the reasonableness analysis our law mandates"). #+end_quote .

8.18.2. Example: Agreed motions to seal

Similarly, parties should not count on getting a court to rubber-stamp their request to order filed documents to be "sealed," that is, kept from public access. For example, the Fifth Circuit implicitly criticized a district court (while nonetheless affirming summary judgment) because the lower court had granted a broad agreed protective order, which had the effect of sealing documents:

Judicial records belong to the American people; they are public, not private, documents.

Certainly, some cases involve sensitive information that, if disclosed, could endanger lives or threaten national security. But increasingly, courts are sealing documents in run-of-the-mill cases where the parties simply prefer to keep things under wraps.

This is such a case. The secrecy is consensual, and neither party frets that 73 percent of the record is sealed. But we do, for three reasons.

First, courts are duty-bound to protect public access to judicial proceedings and records.

Second, that duty is easy to overlook in stipulated sealings like this one, where the parties agree, the busy district court accommodates, and nobody is left in the courtroom to question whether the decision satisfied the substantive requirements.

Third, this case is not unique, but consistent with the growing practice of parties agreeing to private discovery and presuming that whatever satisfies the lenient protective-order standard will necessarily satisfy the stringent sealing-order standard.

Below, we review the interests at stake and the exacting standard for sealing that protects those interests. Then, we explain the concerns raised by the sealings in this case. Le v. Exeter Finance Corp., 990 F.3d 410, 417-18 (5th Cir. 2021) (affirming summary judgment dismissing fired employee's breach-of-contract claim) (cleaned up, extra paragraphing added).

Basically the same explanation was offered by the federal district court for the Southern District of New York, in a decision in which the court:

  • granted the parties' joint motion to enter a consent judgment confirming an arbitration award, but
  • denied the parties' motion to seal documents:

Here, the Exhibits — the Final Arbitration Award, the Partial Final Arbitration Award, and the [Master Services Agreement] between the parties — directly affect the adjudication of the Petition, and are therefore judicial documents.

That the Court need not decide the merits of the Petition does not change the fact that the Exhibits are judicial documents.

Moreover, because the information contained in the Exhibits directly affects the adjudication of the Petition, a strong presumption of public access applies. Susquehanna Int'l Grp. Ltd. v. Hibernia Express (Ireland) Ltd., No. 21 Civ 207, slip op. (S.D.N.Y. Aug. 11, 2011) (granting with leave to submit revised motion) (cleaned up, emphasis added); see also, e.g.: XPO Intermodal, Inc. v. American President Lines, Ltd., No. 17-2015, slip op. (D.D.C. Oct. 16, 2017) (denying motion to seal documents in action to confirm arbitration award, with leave to submit revised motion); Total Recall Technologies v. Luckey, No. C-15-02281, slip op. (N.D. Cal. Mar. 25, 2021) (denying motion to seal; "If the parties wanted to proceed in total privacy, they should have arbitrated this dispute [sic]. Instead, they brought this dispute to a public forum that belongs to the people of the United States, not TRT or Facebook. The United States people have every right to look over our shoulder and review the documents before the Court.").

On the other hand: As noted at 21.1.33.7, the Second Circuit held that:

… the presumption of public access to judicial documents is outweighed here by the Federal Arbitration Act’s strong policy in favor of enforcing arbitral confidentiality provisions and the impropriety of counsel’s attempt to evade the agreement by attaching confidential documents to a premature motion for summary judgment. Abelar v. IBM Corp. (In re IBM Arbitration Litigation), 76 F.4th 74, 78 (2d Cir. 2023) (affirming trial court's granting of IBM's motion to seal documents) (emphasis added).

8.18.3. Example: Preclusion of class actions

In a Ninth Circuit decision, the ride-share company Uber sought mandamus to defeat a preliminary "centralization" decision in a class-action lawsuit; the court rejected Uber's assertion that Uber's arbitration agreement precluded the Judicial Panel on Multidistrict Litigation ("JPML") from ordering "centralization" of the claims against Uber:

Where a federal statute vests a court with the power (or duty) to act of its own accord, a private agreement cannot bind the court and the agreement is entitled to only so much consideration as provided for by Congress. Forum selection clauses neatly illustrate this rule. A forum selection clause cannot eliminate a district court’s jurisdiction to hear a suit. … Rather, courts enforce forum selection clauses because the general change-of-venue statute, 28 U.S.C. § 1404(a) requires that such agreements be considered in the venue analysis.

Uber Technologies, Inc. v. U.S. Judicial Panel on Multidistrict Litigation, No. 23-3445, slip op. at 18 (9th Cir. Mar. 10, 2025) (cleaned up; citations omitted).

8.18.4. Example: Confessions of validity of noncompetes

A court might well disregard a contractual statement that a noncompetition covenant was acknowledged to be valid and enforceable. Example: As Delaware's chancery court noted in its Kodiak opinion:

The RCA's language stating its restrictive covenants are reasonable, and waiving a defense that they are not, does not preclude this Court from performing the reasonableness analysis our law mandates. Kodiak cannot rely on those provisions to evade review and establish a reasonable probability of success on the merits.

After analyzing the contract's reasonableness under the common law test, I find the RCA's restrictive covenants in Sections 1 and 2 are unreasonable, and consequently unenforceable.

Accordingly, Kodiak has failed to demonstrate a reasonable likelihood of success on the merits of Counts I and II. Kodiak Bldg. Partners, LLC v. Adams, No. 2022-0311-MTZ, slip op. (Del. Ch. Oct. 6, 2022) (denying Kodiak's motion for preliminary injunction; extra paragraphing added).

8.18.5. But some drafters just don't get it …

Some drafters don't seem to appreciate the need for verbal humility. Consider the following imperious language in a Bank of America guaranty:

17.  … The court shall, and is hereby directed to [!], make a general reference pursuant to California Code of Civil Procedure Section 638 to a referee (who shall be a single active or retired judge) …. Archived at https://tinyurl.com/BAGuaranty (sec.gov); emphasis added.

This is more than a little presumptuous, no? The above language doesn't comport well with the cited California statute, which appears to leave it up to the discretion of the trial judge to decide whether or not to grant a request for appointment of a referree. See Cal. Code of Civ. P. § 638

Somewhat less imperiously is section 24 of of a Honeywell purchase-order form, apparently from February 2014:

The amount of insurance carried in compliance with the above requirements is not to be construed as either a limitation on or satisfaction of the indemnification obligation in this Purchase Order. … Archived at https://perma.cc/84BS-KYXB (emphasis added).

Similar language can be found in section 30 (independent contractors) and section 37 (waivers) of the same Honeywell purchase-order form.

And to like effect, see the discussion at 28.5 of the King v. McLaren Health case from Michigan, where an employment application included a six-month deadline on the individual's ability to sue the company: "Should a court determine that this period of time is unreasonable, the court shall [sic] enforce this provision as far as possible and shall [sic] declare the lawsuit or claim barred …."

8.19. Industry-standard terminology

When you're drafting a contract, you'll want to try to avoid coining your own non-standard words or phrases to express technical or financial concepts. If there's an industry-standard term that fits what you're trying to say, use that term if you can. Why? For two reasons:

  • First, someday you might have to litigate the contract, and so:
    • You'll want to make it as easy as possible for the judge (and his- or her law clerk) and the jurors to see the world the way you do. In part, that means making it as easy as possible for them to understand the contract language.
    • The odds are that the witnesses who testify in deposition or at trial likely will use industry-standard terminology. So the chances are that the judge and jurors will have an easier time if the contract language is consistent with the terminology that the witnesses use—that is, if the contract "speaks" the same language as the witnesses.
  • Second, and perhaps equally important: The business people on both sides are likely to be more comfortable with the contract if it uses familiar language, which could help make the negotiation go a bit more smoothly.

8.19.1. Exercises and discussion questions

8.19.1.1. Basic questions
  1. Who are some of the people who might someday read: (i) the draft contract; (ii) the signed contract — and what will they likely be hoping to accomplish?
  2. FACTS: MathWhiz's CEO asks you to draft a short contract in which MathWhiz will do some data-analysis for a longtime client.
    • The CEO says that she and her contact at the client have agreed on all the details in a series of Zoom calls.
    • The CEO has drafted a detailed "term sheet," with bullet points outlining the agreed business- and technical details; her client contact has reviewed the term sheet and said it's fine.
    • The client contact doesn't want to get his company's lawyers involved, so the MathWhiz CEO has asked you whether "the contract" could be drafted as just a short email that she will send to the client contact, with the term sheet attached.
    • QUESTION: What do you advise the MathWhiz CEO, and why? How would you advise her, and why?
  3. True or false: Contract drafters should avoid including explanations of particular terms. EXPLAIN.
  4. FACTS: You're drafting a contract for MathWhiz; the company's CEO tells you there's a fair chance that the contract might be litigated in the not-too-distant future. QUESTION: How might the Strunck & White injunction, "Omit needless words," apply in this situation?
  5. MORE FACTS: Continuing with #4, MathWhiz's CEO also thinks that the other party to the contract is likely to be acquired in the next year or so — by whom exactly, the CEO doesn't know — and that it'd likely be an "acqui-hire" in which many of the other party's senior executives and -managers would be let go (with their stock options and a severance package) as no longer needed. QUESTION: What if anything might you do differently in drafting the contract?
  6. What are the two essential components of a contract drafter's mission?
  7. FACTS: You are drafting a contract for MathWhiz and are getting ready to send it to MathWhiz's CEO, Mary Marvelous. QUESTION: Name two reasons that Mary will likely prefer that the contract be written in plain language.
  8. MORE FACTS: MathWhiz is considering filing a lawsuit for breach of another contract that you didn't draft. The breached provision is a "wall of words" that's full of legalese. QUESTION: Name two reasons that MathWhiz's trial counsel might wish that the breached provision had been written in plain language.
  9. In the context of contract drafting, what's a "L.O.A.D."?
  10. What's one of the most important ways of avoiding being a L.O.A.D.?
  11. Based on whatever experience you've had so far — personal and/or professional — would you prefer to review a contract with (i) fewer pages with dense paragraphs, or (ii) more pages but shorter paragraphs and more white space? EXPLAIN.
  12. What does BLUF mean?
  13. What's "the MEGO factor"?
  14. Name two advantages of putting a contract's key business details into a schedule, perhaps at the front of the contract.
8.19.1.2. Exercise: Stanford-Tesla lease intro

Refer to the Stanford-Tesla lease at 29.2.2:

  1. Is "Commercial Lease" the proper term, or should it be "Commercial Lease Agreement"? (Hint: Look up the definition of lease in Black's Law Dictionary.)
  2. Why state that the Lease is entered into "as of July 25, 2007"?
  3. Why do you think the names of the parties are capitalized?
  4. What might be some of the pros and cons of including this kind of "Basic Lease Information" at the beginning of the agreement document, instead of including it "in-line" in the appropriate section(s) of the agreement?
  5. To what extent is the "Each item in this Article 1 incorporates …" worth including?
  6. What could go wrong with the italicized portion, "to the extent there is any conflict …"?
  7. Note the mention of the Glossary in the last sentence of the first paragraph — where are some other places to include definitions for defined terms? (Hint: See 32.11.)
  8. Any comments about the way the "Term: Five (5) years" portion is stated? How about the way that the Base Rent amounts are stated?

8.20. Footnotes in contracts?

Suppose that, after intense negotiations, a particular contract clause ends up being written in a very specific way. Consider including a footnote at that point in the contract, explaining how the language came to be what it is. Future readers — your client's successor, your client's trial counsel, a judge — might thank you for it.

DCT note: When I was in-house at BindView, our standard enterprise license agreement form was extremely customer-friendly (this was intentional, to help us get to signature sooner). But at first I still had to spend a lot of time explaining to customers' lawyers why the agreement form included certain terms.

To save negotiation time, I added a fair number of explanatory footnotes to our license-agreement form. The footnotes seemed to reduce, by quite a lot, the amount of time needed for "legal" negotiations.

Needless to say, our business people were please to get deals to signature sooner.

And interestingly, customers' lawyers hardly ever asked us to delete the footnotes before contract signatur.

With footnotes left in, if the contract were ever litigated (which never once happened), the footnotes would be available to be read:

  • by opposing counsel;
  • by the judge's law clerk;
  • by the judge him- or herself; and
  • by one or more of the jurors.

That'd be no bad thing.

To be sure: In litigation, hindsight you might wish you hadn't said what you did in the footnotes. But that could happen with any provision or phrasing in the contract.

What's important here is that the overwhelming majority of contracts never see the inside of a courtroom. So, on balance it's likely that the client will get more overall business benefit from including footnotes — if doing so will help get the client's contracts to signature sooner.

8.21. Hamburger for the guard dog?

This rule is related to the Freaky Friday rule: Sometimes you'll find yourself drafting the contract, or perhaps you'll be proposing to add a significant new section to another party's draft. In either situation, it can pay to include a clause of a kind that you know the other side will insist on getting, because you can draft it to your client's advantage.

EXAMPLE: Suppose that you're drafting a contract under which your client must pay The Other Side a percentage of its (your client's) sales.

The contract might be a commercial real-estate lease for a store in a shopping mall, where each quarter your client (the tenant) must report to the landlord (the mall owner) the amount of the tenant's gross sales at the store. Your client would then have to pay the landlord, not just a fixed base rent for the store, but also a specified percentage of the store's gross sales. This is known as percentage rent.

Often the shopping-mall landlord will have superior bargaining power and will insist on using its own lease form. And that lease form will almost certainly include an audit provision such as that of Protocol 4.3: The audit provision would give the landlord the right to have the tenant's sales records audited, to confirm whether or not the tenant has paid the correct amount of percentage rent.

But if you're drafting the lease form — for example, if the landlord is inexperienced compared to your client the tenant — then you might be tempted to omit an audit clause from your draft lease. Your reasoning could be that landlord's contract reviewers might not think to ask for an audit provision, and it's not your job to remind them — which is certainly true.

But consider these points:

–  It might be wishful thinking (or delusional) to imagine that the landlord's contract reviewer won't notice the absence of an audit clause — the reviewer could well be an expert who knows exactly what to look for and what to demand.

–  Suppose that the landlord's contract reviewer were to see a reasonable audit clause in your draft. He or she might well mentally check the box — yup, they've got an audit clause, it's not perfect for us but it'll do, let's move on — and not make significant changes to your wording. That'd be a win for you, not least because it'd one less thing to have to spend precious time negotiating.

–  You might be better off setting a friendly tone with an audit clause that you know your client the tenant can live with — and then, if the landlord makes unreasonable change requests, you can try standing on principle to reject the requests. (See also 8.15 for when you just can't say no to an unreasonable request.)

–  Suppose that the landlord's drafters really don't know what they're doing: Chances are you'll get them to signature faster — and you'll be laying a foundation for a trusted relationship — if your draft seems to address the landlord's "legitimate needs and greeds" in a reasonable way along with your own client's needs. (BUT: Don't go overboard with this.) "Legitimate needs and greeds" is a phrase used by the renowned intellectual-property attorney Tom Arnold (1923-2009). See Tom Arnold, Basic Considerations in Licensing, in Recent Developments in Licensing at 6-22 (American Bar Association Section of Patent, Trademark, and Copyright Law 1981), quoted in Homer O. Blair, Overview of Licensing and Technology Transfer, 8 N.C. J. Int'l L. 167, 190 (1982). Tom, the founding partner of my former law firm, was a mentor and friend; I've included a brief remembrance at 28.2.

–  Finally: This rule applies only when you're the drafter, not the reviewer. As discussed at 8.11.6, when you're reviewing the other side's draft contract, it's not your job to propose provisions that could disadvantage your client and that The Other Side didn't think to ask for.

8.22. Hand-grenade clauses can get thrown back at you

A few years ago, a new client of mine was negotiating a fairly-large transaction with a prospective customer. The client's sales team had sent the customer the company's then-standard contract form, which I hadn't drafted.

  • The client's contract form included a forum-selection provision requiring all litigation to take place exclusively in Houston, which was the client's headquarters city. (Concerning forum selection, see Protocol 21.12.)
  • The customer's lawyer saw the forum-selection clause and said it needed to be reversed, so that the exclusive forum would be the customer's home city — let's say that was Cleveland.
  • That contract change wouldn't have been great for my client. Sure, it was unlikely that the client would get into litigation with any customer. But still, being forced to litigate in Cleveland would have been costly and inconvenient.
  • The client's sales people said this was an important sale and that the company was willing to concede the forum-selection point.
  • Somewhat surprisingly, the customer's lawyer went along with my suggestion that we just drop the forum-selection clause entirely, instead of agreeing to Cleveland as the exclusive forum — the lawyer might not have realized that this could have turned out to be a significant concession.20

Lesson (mixing the metaphors here): Don't "poke the bear" (see 8.14) by lobbing a hand-grenade clause that the bear could throw back at you — and leave your client worse off than having no clause at all.

8.23. False imperatives: Whose throat to choke?

A "false imperative" is a provision in a contract — commonly written in passive voice, see 32.1 — where the provision proclaims that something is to be done, but leaves it unclear just who is responsible for making it happen.

Here's a hypothetical example — consider an apartment lease that says:

The apartment shall be regularly serviced by a professional pest-control service.

Who's responsible for making sure this happens? Is it the landlord, or the tenant? Either one seems plausible.

Context can matters (see 7.1); if the pest-control requirement is in a section titled, e.g., "Tenant's responsibilities," then that would likely resolve the question.

But it's better to assume that in a lawsuit or arbitration, "someone" might try to quote the requirement out of context. (Nah: Lawyers would never do that — would they?)

You could think of a false imperative as being like baseball players who let an easily-catchable fly ball drop to the ground between them — because each player assumes that "someone else" will get it, and so no one "calls it."

Example: This comes up in real life: In a Houston case, a limited-partnership agreement provided that a partner was to be paid money, but the agreement used the passive-voice "shall be paid." This led to presumably-costly litigation over just who was supposed to make the payment — was it the limited partnership, or the general partner?

Here's another example of a false imperative, this one hypothetical — suppose that:

  • A real-estate developer enters into a construction agreement with a general contractor;
  • Under the construction agreement, the contractor is to build a building;
  • Because of the nature of the building site, special safety procedures will be needed for all personnel coming on the site;
  • The construction agreement says simply: "All Developer personnel are to be trained in special safety procedures for the Building Site."

This arguably leaves unclear just who is responsible for training the developer's personnel in the special safety procedures — as before, other portions of the construction agreement might shed light on the question, but that's not the ideal situation.

A useful business expression (albeit a bit trite from overuse) is One Throat to Choke!

Drafting lesson: Even in cases where passive voice might be appropriate: Try not to leave any room for doubt about who is responsible for making Item X happen, or for preventing Event Y from happening. As a judge in New York City once opined: "The hallmark of good legal writing is that an intelligent layperson will understand it on the first read." Gerald Lebovits, Free at Last from Obscurity: Achieving Clarity, 96 Mich. B.J. 38 (May 2017), SSRN: https://ssrn.com/abstract=2970873 (also quoted at 2.4).

8.24. Bright(er) lines: Use to replace vague standards?

Vague language can sometimes lead to trouble if the vagueness can lead to disputes about whether particular rights or obligations have been triggered. Here are a few examples.

  • Example: In Fed Cetera (3d Cir. 2019), a particular referral agreement stated that a referring party would be paid a commission by a supplier whenever the supplier "consummated" a transaction with a referred customer during a stated time period. For one referred transaction, the supplier signed a contract with a referred customer during the stated time period, but nothing else happened until after the time period had ended. This led to litigation whether the transaction had been "consummated" during the time period, and thus whether the referring party was entitled to a commission for that transaction. See Fed Cetera, LLC v. Nat’l Credit Servs., Inc., 938 F.3d 466 (3d Cir. 2019) (reversing and remanding summary judgment).
  • Example: in Akorn v. Fresenius (Del. 2018), the parties had to litigate the meaning of a contract's being "executed" instead of "signed," because the former could be interpreted as the contract's being performed by the parties. See Akorn, Inc. v. Fresenius Kabi AG, No. 2018–0300–JTL, text accompanying n.333 (Del. Ch. Ct. Oct. 1, 2018), aff'd, 198 A.3d 724 (Del. 2018).

    Lesson: Refer to a more-certain date, such as: • the date the contract was signed; • the date of the invoice; • the date payment was collected.

  • Example: A large U.S. exporter of liquid natual gas (LNG) had to arbitrate whether a "start date" had occurred in a contract with Shell — if the start date had occurred, then the exporter would have been restricted in its ability to sell into spot markets at higher prices than under the contract. The problem was that the "start date" was tied to completion of a Louisiana liquefaction facility, and apparently it wasn't entirely clear whether "completion" had occurred. The exporter ended up winning the arbitration. See Press release, Venture Global Statement on Shell Arbitration Decision (Aug. 12, 2025); Alistair Calvert, John Gilbert, and Adam Quigley, Shell v Venture Global: Commissioning a Dispute (Aug. 27, 2025).

    Lesson: Be clear that a right or obligation does or doesn't start, or does or doesn't end.

  • Example: In McGinnis (Ohio App. 2024), a tenant leased a house with an option to purchase; the relevant option language was as follows. The tenant didn't give notice by a stated date; the landlord concluded that the tenant's option to purchase had therefore expired. But the trial court and appellate court disagreed, because (they said) that point wasn't clear: "If the parties had intended for missing the June 1, 2021 deadline to result in termination of the purchase option, their agreement easily could have said so. But it did not." McGinnis v. Conley, 2024 Ohio 482 ¶ 16 (Ohio App.).

    Lesson: Likewise, don't write that notice must be "given" by a certain date; instead, say that notice must be "received" or "effective" (if effectiveness is defined) or "sent" by that date.

8.24.1. If a bright line isn't feasible: Neutral escalation?

There might be some situations where bright-line standards aren't practicable or even desired. For those situations, consider the following to give parties an incentive to be reasonable about settlement:

  • Escalation to a neutral advisor, along the lines of Protocol 21.11; or
  • Expert determinations, as often seen in construction contracts. See, e.g., Peter Godwin, David Gilmore, Emma Kratochvilova, Mike McClure, and Conal McFadyen, Expert Determination: What, When And Why?, at https://perma.cc/2NJN-GHS2 (Mondaq.com 2017).

8.25. Clean sheet of paper (start with)? Usually, no.

It's seldom if ever a good idea to start drafting a contract (or even just a clause) from scratch. That's especially true when you're relatively new at contract drafting.

–  Good clauses and forms will serve as a something like an operating manual for the parties' dealings, identifying what-if cases that can arise and providing instructions (or at least guidance) in how to handle those cases.

–  Even mediocre clauses and forms will serve as something of a checklist of issues that the drafter should consider addressing; that's important because we humans are all prone to overlooking "stupid stuff." (See the discussion of checklists at 32.5.)

8.26. Combat Barbie: Consider using "distractor" terms

Military people learn early that when preparing for inspection, you don't want to make everything perfect. That's because the inspector will keep looking until he (or she) finds something — because if the inspector doesn't find anything, his superior might wonder whether the inspector really did his job.

The trick is instead to make everything pretty squared away — but then [mess] things up just a little bit. That way, the inspector will have something to find and report to his superior, thus avoiding questions whether the inspector really inspected.

Illustrating the point: In an online forum, a British lawyer, who had graduated from Sandhurst (the UK equivalent of West Point), told the following story, paraphrased here: At Sandhurst (as is also true at U.S. military academies), first-year cadets are hounded relentlessly by upper-class cadets during their first few weeks. One such first-year cadet, who was female, did a good job of squaring away her bunk and gear for inspection.

But then, before the inspection the cadet carefully placed a "Combat Barbie" doll on her bunk. Of course, when it came the cadet's turn to be inspected, the inspectors immediately noticed her egregious insult to good military order; they promptly began "counseling" her about the unmilitary appearance of her bunk area.

That played right into the cadet's hands: As it happened, the inspectors' "counseling" took up their entire alloted time for that cadet's inspection. And this saved the cadet quite a bit of trouble: Without the distracton of Combat Barbie, the inspectors might instead have used their time to trash the cadet's bunk area, leaving her gear strewn all over the floor, and ordering her to restore the environment as "additional training."

A similar "distractor" psychology can sometimes work in drafting a contract: Be sure to give the other side's reviewer something to ask to change, if for no other reason than to give the reviewer something to report to her boss or client as having been spotted and fixed, thanks to the reviewer's commendable diligence.

But make it a fairly minor point; otherwise, the reviewer and her client might dismiss you as naïve — and worse, they might start to question whether your client was a suitable business partner.

Example: If you're a supplier, consider specifying payment terms of net-20 days, and be prepared to agree immediately to net-30 days if asked. But don't specify net-5 days, which in many situations would risk branding you as naive about "how things are done."

Addendum: For similar examples from the corporate world, see the stories by commenters in a Hacker News discussion.

8.27. Consultation in lieu of consent? (notes)

Sudden, unexpected moves by one party to a contract can make the other party nervous. Example: The business relationship between a service provider and a customer could be damaged if the service provider were to suddenly replace a key person assigned to the customer's work without advance notice.

The usual, sledge-hammer approach to dealing with this problem is to contractually require the provider to obtain the customer's prior consent before taking such an action.

  • The provider, though, will usually push back against such a consent requirement — the provider will be reluctant to give the customer a veto over how it runs its business.
  • Moreover, it could be a management burden for the provider to have to check every customer's contract to see what internal management decisions required prior customer approval.

As an alternative (and compromise), the provider might be willing to commit to consulting with the customer before taking a specified action that could cause heart­burn for the customer. That way, the customer would at least get notice, perhaps an explanation, and an opportunity to be heard, which could make a big difference in the customer's reaction and to the parties' business relationship.

Example: A services contract could say that, for example, "Except in cases of emergency, Service Provider will consult with Customer at least ten business days in advance of replacing Service Provider's supervisor in charge of the Project." That would at least get the parties talking to one another, which can help avoid strains in their business relationship.

Of course, a party would also have to keep track of its consultation commitments, just as much as for its consent obligations.

8.28. Demonstrative exhibits: Build them into the contract?

Remember the cliché about a picture being worth a thousand words? Nowhere is that more true than the courtroom. That's why in litigation, lawyers and expert witnesses often use so-called demonstrative exhibits — diagrams, time lines, charts, tables, sketches, etc., on posters or PowerPoint slides — as teaching aids to help them get their points across to the jury during testimony and argument.

In a lawsuit, the jurors might or might not be allowed to refer to the parties' demonstrative aids while they're deliberating.

•  Jurors normally take "real" exhibits — like a copy of the contract in suit — into the jury room with them and refer to them during deliberations.

•  Judges, however, sometimes won't allow the jury to take demonstrative exhibits with them, on the theory that the jurors are supposed to decide the case on the basis of the "real" evidence and not on documents created solely for litigation by the lawyers.

True, in U.S. federal-court cases, Rule 1006 of the Federal Rules of Evidence allows summaries and the like to be admitted into evidence. Trial judges, however, have significant discretion over evidentiary matters; if a particular judge were to decide that a particular demonstrative aid should not be given to the jury for use in its deliberations, that'd normally the end of that discussion. See, e.g., Allen Hinderaker & Ian McFarland, Demonstrative Evidence Under the Rules: The Admissable and Inadmissable (MerchantGould.com 2015), discussing Fed. R. Evid. 611 and 1006.

So: If you plan ahead when drafting a contract, your client's trial counsel might later be able to sneak a demonstrative aid or two into the jury room through the back door — no, through the front door, but at the back of the contract — as "real" evidence, not just as a demonstrative exhibit, to help the jurors understand what the parties agreed to.

Ask yourself: Is there anything we'd want the jurors to have tacked up on the wall in the jury room — for example, a time line of a complex set of obligations? If so, think about creating that time line now, and including it as an exhibit to the contract. The exhibit will ordinarily count as part of the "real" evidence; it should normally be allowed back into the jury room without a fuss.

Of course, before the contract is signed the parties would have to agree to include your stealth demonstrative exhibit in the contract document. But their reviewing your exhibit for correctness could be a worthwhile exercise — and if their review makes them realize they don't agree about something, it's usually better if they find that out before they sign.

And to be sure, there's always the risk of unintended consequences: The demonstrative exhibit you create today might not create the impression you want to create in a jury room years from now. But that's always a risk even when you write the contract itself.

Your time line, chart, summary, diagram, etc., doesn't necessarily have to be a separate exhibit: modern word processors make it simple to include such things as insets within the body of the contract. (I used to do just that decades ago when writing patent-invalidity or -noninfringement opinions, a.k.a. "freedom to operate" or "FTO" opinions, for clients: I'd prepare the PowerPoint slides that I'd want to use if I were testifying as an expert witness, and then I'd insert those slides as insets in the body of the opinion itself. Happily, none of those opinions were ever the subject of litigation, at least so far as I know. )

8.28.1. Provide an opt-out right?

By notice to all other parties to the dispute, any party may unilaterally opt out of any or all of the steps in [DESCRIBE] at any time before all parties have started the step in question.

Such an opt-out right should give parties more comfort about agreeing to a dispute-resolution mechanism before they know what a particular dispute would be about.

This opt-out right is modeled on a similar opt-out right in the mediation requirement in Rule R-10 of the Commercial Arbitration Rules of the American Arbitration Association.

8.29. Confirmations – get from third party? (notes)

Getting confirmation from an independent source relates to the principle that you get what you INspect, not what you EXpect, as discussed at 9.8.

When two parties enter into a contract — let's call them "Fred" and "Ginger" — they might want independent confirmation of information provided by the other party, instead of taking the other party's word for it.

Example: Suppose that under the contract, Ginger is supposed to arrange for a third party, "Harry," to provide one or more benefits for Fred if Fred so requests — such as, for example:

  • Harry's guaranty to pay Fred what Ginger owes him if Ginger doesn't pay on time;
  • an insurance policy (see 31.21) to support Ginger's indemnity obligation;
  • a payment bond, under which Harry agrees to pay Ginger's subcontractors if Ginger fails to pay them, so that the subcontractors won't put a lien on Fred's property.

In that situation, suppose that, in due course, Ginger reports to Fred that yes, she has indeed made the necessary arrangements with Harry to provide Fred with the agreed benefit.

Should Fred take Ginger's word for it? Quite possibly not; it might be better for the contract to require Ginger to get Harry to confirm to Fred, in writing, that Ginger has in fact made the necessary arrangements. Otherwise:

  • Ginger might neglect to make such arrangements with Harry; that could leave Fred stuck without the benefits that Harry was supposed to provide him — for example, without insurance to cover Ginger's indemnity obligation if Ginger didn't have the money to do so herself.
  • Worse: If Ginger is a shady character, she might be tempted to lie — to state falsely that she had made the arrangements with Harry — or even to provide Fred with a forged- or otherwise-fraudulent confirmation, purportedly from Harry.
  • The law might give Fred more rights against Harry if Harry provides Fred with confirmation.

This concern is reflected in some Lighthouse provisions such as the following (possibly among others):

  • § 4.3.17 of Protocol 4.3 states that after an audit, the recordkeeper is entitled to get a copy of the auditor's report directly from the auditor.
  • Under Option 17.5.19 of Protocol 17.5 (background checks), contact information for personal references is to be obtained independently.
  • § 3.14.9 of Protocol 3.14 (notices) requires independent confirmation of receipt of notice in most cases.
  • In § 4.4.5 of Protocol 4.4 (backup payment sources), confirmation of a backup-payment arrangement must come from the bank or other financial institution.

8.30. Attorney-client privilege (rough notes)

8.30.1. Caution — watch out for possible privilege waivers

Even inadvertent disclosure of privileged documents to others — including others within the client's own organization — could result in permanent waiver of the privilege under typical rules of evidence. See, e.g., Fed. R. Evid. 502, Attorney-Client Privilege and Work Product; Limitations on Waiver; see also, e.g., Legal Information Institute, Attorney-Client Privilege (law.cornell.edu).

Worse: The waiver could extend broadly as a "subject-matter waiver."

If a waiver occurs, both the client's people and counsel might have to produce documents and testify about their confidential discussions — which would not make the client particularly happy ….

8.30.2. Pro tip: Privilege legends

When sending a potentially-privileged email or other document to a client, consider prominently marking it with a legend such as (for example) "CONFIDENTIAL: ATTORNEY-CLIENT PRIVILEGE." That way, if litigation were ever to take place:

  • The legend will help the client's litigation counsel to spot documents that should be withheld from production to avoid waiver of the privilege (see above).
  • Moreover, for emails and other electronic documents, the client's litigation counsel will likely use special software to search the client's computer systems for documents that must be produced to the other side; a privilege legend will help the software to flag particular documents for review.

8.30.3. Privilege logs

When documents are produced in litigation, the producing party will generally withhold documents that might be subject to the privilege; depending on local rules and the court's case-management order, the producing party might be required to produce a "privilege log," namely a list of documents withheld from production on privilege grounds, generally with specific categories of descriptive information. See generally, e.g., Travis S. Hunter and Sara M. Metzler, Is It Privileged? A Young Lawyer’s Guide to Preparing a Privilege Log in Commercial Litigation (AmericanBar.org 2018).

8.31. Cheap insurance in drafting

"Cheap insurance" is a metaphor for small, low-cost habits or actions that might never pay off — but that can help avoid big problems later. An example from everyday life is when you get home, putting your keys in the same place every time, to reduce the chances that you'll forget where you put them. As a character in a Pulitzer Prize-winning novel said: "These dull habits sometimes pay off." Herman Wouk, The Caine Mutiny, ch. 10.

Here are a few contract-drafting examples:

–  Try not to leave big blank spaces on a page of a contract, in case an unscrupulous person later uses one of those blank spaces to insert additional details that weren't agreed to. Sure, maybe you can later prove the forgery, but it might well be better to use a guardrail clause (or, more crudely: apply some schmuck repellent).

–  Consider putting the word WAIVE and its variations (waives, waived, waiver, etc.) in bold-face all caps, in case a jurisdiction requires it for conspicuousness (3.18.6.1).

–  Consider whether to include "for the avoidance of doubt" clauses as a guardrail against "creative" contract interpretations, e.g., concerning assignment consent at discretion (Option 15.3.6.1). BUT: Consider also whether including such a clause would "poke the bear" — causing the other side to notice and insist on rewording in a manner not to your liking (see 8.14).

Caution: Don't go overboard — that's how contract forms grow, and grow, and grow …. Remember that people will have to read everything you add to a contract. Don't turn your contract into shovelware.

9. Performance standards

9.1. Best Efforts Definition

9.1.1. Applicability if agreed to

  1. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference., it applies any time that the Con­tract requires a party (the "Obligated Party") to use "best efforts."
  2. In case a question arises: This Protocol itself does not impose any "efforts" requirement of any kind.
Note

Contracting parties will sometimes decide that a best-efforts obligation is an acceptable business risk that can help them get the contract to signature sooner. Depending on the jurisdiction, though, a court might not share the view of best efforts stated in this Definition. This means that it can be useful to define the term, so that the definition will serve as something of a guardrail. (W.I.D.D.: When In Doubt, Define!)

9.1.2. Required level of effort

The Obligated Party must diligently use reasonable efforts to achieve the stated objective.

Note

().  This draws on the Restatement of Agency, which states in part that best efforts is "a standard that has diligence at its essence …." Restatement (Second) of Agency § 13, comment a (1957); see also, e.g., Nat'l Data Payment Sys., Inc. v. Meridian Bank, 212 F. 3d 849, 855 (3d Cir. 2000) (Alito, J., affirming summary judgment that plaintiff had not shown that defendants had failed to use best efforts).

This section seeks to steer clear of differing court views that have arisen, with some U.S. courts seemingly equating best efforts with mere reasonable efforts — contrary to what business people are likely to think they're getting in a best-efforts clause. See, e.g., Scott-Macon Securities, Inc. v. Zoltek Cos., Nos. 04 Civ. 2124 (MBM), 04 Civ. 4896 (MBM), part II-C (S.D.N.Y. May 11, 2005) (citing cases).

Example: New York courts might equate best efforts with merely making reasonable efforts in good faith. See Soroof Trading Development Co. v. GE Fuel Cell Sys. LLC, 842 F. Supp. 2d 502, 511 (S.D.N.Y. 2012) (citing cases).

9.1.3. Certain burdensome efforts not required

A best-efforts obligation does not require the Obligated Party to do any of the following things (not an exhaustive list):

  1. make any unreasonable effort;
  2. harm the Obligated Party's own lawful interests in any non-trivial way;
  3. act as a fiduciary for another party;
  4. make every possible reasonable effort; nor
  5. actually succeed in achieving the stated objective.
Note

().  Caution: These carve-outs might be factually complex — and thus costly to litigate if the parties were to get into a dispute about whether a party really did use its "best" efforts.

Subdivision 2 borrows from Bloor (2d Cir. 1979), where the court remarked that a best-efforts obligation "did not require Falstaff [Brewing Co.] to spend itself into bankruptcy to promote the sales of Ballantine [beer] products …." Bloor v. Falstaff Brewing Corp., 601 F.2d 609 (2d Cir. 1979) (affirming holding that Falstaff had breached its best-efforts obligation).

Subdivision 3 is meant as a guardrail against aggressive claims of the kind made in a California case in which the court rejected the plaintiff's contention that "'best efforts' means the efforts required of a fiduciary[.]" California Pines Property Owners Assn. v. Pedotti, 206 Cal. App. 4th 384, 393-95, 141 Cal. Rptr. 3d (Cal. App. 2012); see also Tigg Corp. v. Dow Corning Corp., 962 F.2d 1119 (3d Cir. 1992), where the court held that, in a contract with an exclusive-dealing arrangement, "[t]he obligation of best efforts forces the buyer/reseller to consider the best interests of the seller and itself as if they were one firm."

Subdivision 4This disavows one line of contrary court decisions, discussed at 31.7.9.

Subdivision 5: Of course, there'd be no need for a best-efforts obligation if the parties agreed to require achieving the stated objective — in such a case, presumably the Con­tract would just say that.

9.1.4. Input from other party encouraged

The Obligated Party should consider consulting the other party about whether the Obligated Party could satisfy a best-efforts obligation by taking a particular course of action — especially a course of action not yet started.

Note

This is one of those areas where the Pick up the phone! general motif of this book can pay dividends. ¶ On the other hand: This is also one of those areas where you might not want to poke the bear — because if you raise the question with the other side, you might not like the answer you get ….

9.1.5. Escalation of certain disputes

If either party asks, the parties must escalate any dispute about what would satisfy a best-efforts obligation —

  1. first, to supervisors, as stated in Protocol 3.4; and
  2. then, at either party's further request, to a neutral advisor, as stated in Protocol 21.11.

9.2. Commercially-Reasonable Efforts Definition

Many business people probably think they have a pretty good idea what the term "commercially-reasonable efforts" means. In court, though, the term doesn't have a settled, standard meaning, as discussed below. This Protocol therefore proposes some general guidelines to help determine what's required — and what's not required — of a party that commits to using commercially-reasonable efforts.

9.2.1. Obligated Party

Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference., it will apply whenever a party (the "Obligated Party") is required to use "commercially-reasonable efforts" (with or without a hyphen) to achieve a stated goal.

9.2.2. Required: Prudent efforts

Obligated Party: Make efforts that prudent people — experienced in the relevant area of business — would generally regard as constituting reasonable efforts for the circumstances in question.

Note

Here we follow IBM's lead in defining commercially-reasonable efforts in the way that it did in one of its state-government IT contracts, in Indiana v. IBM. That particular contract (seemingly drafted by IBM) defined commercially reasonable efforts (somewhat circularly) as: "taking commercially reasonable steps [sic] and performing in such a manner as a well managed entity would undertake with respect to a matter in which it was acting in a determined, prudent, businesslike and reasonable manner …." Indiana v. IBM Corp., 4 N.E.3d 696, 716 n.12 (Ind. App. 2014) (reversing trial court in pertinent part), aff'd, 51 N.E.3d 150 (Ind. 2016).

9.2.3. Certain efforts not required

Obligated Party: When the Con­tract requires you to use commercially-reasonable efforts, it doesn't mean that you have to do any of the following things (which is not an exhaustive list):

  1. make any unreasonable effort;
  2. harm your own lawful interests in any non-trivial way;
  3. make every possible reasonable effort; nor
  4. actually succeed in achieving the stated objective.
Note

().  This section provides some guardrails against aggressive arguments by litigation counsel.

Subdivision 2 addresses an issue raised in a California federal court, which opined that "it is an absurdity to suggest a reasonable business entity would contractually obligate itself to operate [making commercially-reasonable efforts] without regard to its business interests"; in a later ruling, the court, reviewing (sparse) precedent, held that the obligated party could permissibly take into account "its own economic business interests" in taking action. Citri-Lite Co. v. Cott Beverages, Inc., 721 F. Supp. 2d 912, 923-26 (E.D. Cal. 2010) (footnote omitted; citing several cases from various jurisdictions); subsequent decision, No. 1:07-cv-01075, slip op. at 45 (E.D. Cal. Sept. 30, 2011) (findings of fact and conclusions of law; citing cases), aff'd, No. 11-17609 (9th Cir. Nov. 21, 2013) (unpublished).

Subdivision 3 seeks to "write around" a seeming suggestion by Delaware's supreme court, in its 2017 Williams Cos. v. Energy Transfer Equity decision, that commercially-reasonable efforts requires the making of all reasonable efforts. See Williams Cos. v. Energy Transfer Equity, L.P., 159 A.3d 264, 272 (Del. 2017); see also Shareholder Repr. Svcs. LLC v. Alexion Pharma., Inc., No. 2020-1069-MTZ (Del. Ch. Sept. 5, 2024) (holding, after a seven-day trial, that Alexion breached a contractual requirement to use commercially reasonable efforts); Fortis Advisors LLC v. Johnson & Johnson, No. 2020-0881-LWW (Del. Ch. Sept. 4, 2024) (same, after ten-day trial). ] Curiously, the Williams Cos. court reached its conclusion even though the contract elsewhere had used the term reasonable best efforts — the court didn't address whether, under the contract-interpretation principle of expressio unius, exclusio alterius, the parties were presumed to have intended for the two terms to have different meanings

Also in Williams Cos. (in a dissent on other grounds), Chief Justice Strine opined that commercially reasonable efforts is "a comparatively strong" commitment, one that is only "slightly more limited" than best efforts. See id. at 276 & n.45 (Strine, C.J., dissenting) (citation omitted).

9.3. Cooperation Standard Protocol

9.3.1. Definition

When the Con­tract adopts this Protocol and says that the parties are to "cooperate" (whether or not capitalized), it means that the parties are to work together in good faith, and in a reasonable manner, in pursuit of a specified goal; the term "cooperation" has the corresponding meaning.

Note

This definition is provided to support parties who want to "kick the can down the road" (granted, that might be an overused expression) by deferring discussion of issues when they're reasonably confident that they'll be able to work things out between them.

9.3.2. Escalation of certain disputes

If either party asks, the parties are to escalate any disagreement about whether a proposed course of action would satisfy the requirements of this Protocol in accordance with the procedures at Protocol 21.11.

Note

See the discussion of escalation at § 21.11.

9.4. Computer-System Access Protocol Protocol

This Protocol draws on numerous online "terms of service" such as, for example, Amazon's AWS agreement (which might have changed since this writing).

9.4.1. Applicability; parties

When this Protocol is agreed to, it will govern whenever a "User," defined below, of a party (an "Accessing Party") accesses a "Host System," also defined below, of another party (a "Host").

Note

This Protocol itself doesn't authorize anyone to access any Host System — it only states ground rules for any such use. ¶  Caution: This Protocol isn't intended as a "code of conduct"; were it otherwise, and if Protocol 9.5 were also agreed to, then the remedies for breach of this Protocol would be limited — and that's not the intent here.

9.4.2. Definitions

  1. "Host System" refers to, for example, a workstation; network; email system; telephone system; or other similar system — generically, a "host system" (lower case) — maintained by or for a Host. (These aren't intended as limiting examples.)
  2. "User" refers to an individual or computer system employed by a Accessing Party (or otherwise under the Accessing Party's control) that engages in accessing (or trying to access) any Host System.
  3. For easier reading, Users might sometimes be referred to here as "Accessing Party Users" or "the Accessing Party's Users."
Note

Subdivision 1: Here, the term "maintained by or for a Host" is meant to encompass host systems that are owned, operated, leased, etc., by a Host, for example as self-hosted or as hosted on a platform such as Amazon's AWS, Microsoft's Azure, Google's Cloud Platform, Oracle's Cloud, etc.

9.4.3. Accessing Party's compliance obligations

The Accessing Party will see to it that the Accessing Party's Users comply with this Protocol — this is to include, for example, appropriately instructing those Users in their obligations under this Protocol.

9.4.4. Accessing Party's indemnity obligations

The Accessing Party will defend and indemnify the Host and the Host's Protected Group from any harm arising from use, by any of the Accessing Party's Users, of any Host System, where that use did not conform to the requirements of the Con­tract (including but not limited to this Protocol).

Note

The Accessing Party might be responsible anyway for its Users' actions, under the legal doctrine of respondeat superior. Still, it's useful to spell it out in the Con­tract so that the Accessing Party will see it without having to go to the law books.

9.4.5. User sign-up information and proof of identity must be accurate

  1. Each User must make sure:
    1. that all sign-up information that the User submits to a Host System is complete and accurate; and
    2. that any identity-verification information that the User submits is authentic — for example, proof that the User actually is who the User purports to be.
  2. The Accessing Party must do the same for any User sign-up information or identity-verification information that the Accessing Party causes to be submitted to a Host System.
Note

().  Subdivision 1 doesn't require sign-up information to be provided. (But the Host System might not allow access otherwise.)

Subdivision 1.a: Note the use here of "complete and accurate," not "true and correct" (see 32.38).

Subdivision 2 has in mind that an Accessing Party might "bulk-upload" User information to a Host System.

Caution: If a company employee provided false sign-up information, that could prove hugely costly to the company. Example: A giant software vendor had a customer in common with one of its competitors. One of the vendor's employees logged into the competitor's Web portal — using credentials that he'd obtained by falsely stating that he worked for the customer. (The competitor had previously refused the vendor's request to be given its own access to the Web portal.) That was part of a cascade of events leading to a jury verdict of nearly $1 billion against the vendor, later reduced on appeal to $280 million plus prejudgment interest. See Epic Systems Corp. v. Tata Consultancy Servs. Ltd., 971 F.3d 662, 669 (2020) (affirming judgment on jury verdict against Tata for compensatory damages but remanding for reduction of punitive-damages award under state-law cap); id. at 685-86 (employee's false identification as customer employee was a factor supporting award of punitive damages); affirmed after remand, No. 22-2420 (7th Cir. 2023) (nonprecedential disposition).

9.4.6. Prohibited: Unreasonable use

Users must not make unreasonable use of any Host System — including but not limited to those listed at § 9.4.11.

Note

Of course it's hard, in advance, to define "unreasonable" use of a Host System, so let's provide a "reverse safe harbor" (see 8.2)

9.4.7. Required: Prudent malware protection (at all times)

  1. Each User must maintain prudent malware protection for any laptop, workstation, smartphone, tablet, terminal, etc., with which the User accesses Host System.
  2. This obligation is not limited to times when the User is actually accessing a Host System.
Note

().  Subdivision 1: Prudent malware protection will certainly evolve over time, because modern life is a never-ending arms race between tech companies and their users, on the one hand, and criminals.

Subdivision 2 takes into account that at any time, "sleeper" malware could infect the User's equipment , even when not accessing a Host System.

9.4.8. Other applicable Lighthouse protocols

Each User must comply with the following Lighthouse protocols at all times while accessing any Host System:

Note

Here we adopt other Lighthouse protocols so that we don't engage in possibly-dangerous duplication of language. (See the D.R.Y. Principle — Don't Repeat Yourself — discussed at § 30.4.)

  1. Protocol 9.13 (site visits), because access to a Host System is considered one kind of site visit;
  2. any other relevant provisions of the Con­tract;
  3. normal professional standards of conduct for host-system usage;
  4. any other usage policies of the Host that are timely communicated to the User — this could happen orally and/or in writing, and possibly on an ongoing- and/or as-needed basis instead of inundating the User with all the policies at once; and
  5. privacy-related laws and Host rules concerning personal information accessible via any Host System.

9.4.9. Allowed: Host monitoring of Users' access

The Accessing Party and each User are each deemed to consent to the Host's doing any and all of the following things — which would be solely for the Host's benefit:

  1. monitoring any User's access to any Host System;
  2. having a third party engage in such monitoring; and/or
  3. temporarily- or permanently suspending any User's access in case of suspected- or demonstrated violation of this Protocol.

9.4.10. Special case: U.S. Government Users

  1. This section applies if a User accesses a Host System in the User's capacity as an officer, employee, or agent of the U.S. Government.
  2. The Host System is made available to the User as a commercial item, commercial computer software, commercial computer software documentation, and/or technical data, as applicable, as the italicized terms are defined the Federal Acquisition Regulations (FARs) and/or the Defense Federal Acquisition Regulations (DFARs).
Note

Subdivision 1 — "[i]n the User's capacity as an officer, etc. ….": This takes into account the case where a government employee is accessing a Host System while acting in his- or her private capacity. (In such a case this section would seem to be irrelevant; there might be edge-or corner cases of possible concern, but I'm hard-pressed to think of any.)

Government contracting is beyond the scope of this book. For some basics on government contracting, see, e.g., Jeff Schwartz, Doug Hibshman & Austen Endersby, The Federal Contractor’s Guide to Data Rights (2021).

9.4.11. Appendix: Some likely-unreasonable activities

Unreasonable use of a Host System would almost certainly include any of the following, alone or in combination (this is not intended as an exhaustive list):

  1. deception in any form, including but not limited to spoofing, for example, disguising the origin of any transmission sent via the Host System or any network associated with it;
  2. defamation — commonly understood as including libel (written defamation) and slander (oral defamation);
  3. illegal activity, including but not limited to deployment of ransomware and other theft;
  4. infringement of others' rights, including but not limited to use or reproduction of information or other content owned by someone else without the owner's permission;
  5. invasion of privacy, including but not limited to doxxing, that is, publicly identifying or publishing private information about (someone) especially as a form of punishment or revenge (see Merriam-Webster.com);
  6. knowing or reckless introduction of malware, including but not limited to bots, corrupted files, crawlers, hoaxes, keystroke recorders, ransomware, Trojan horses, and viruses;
  7. nuisiance, including but not limited to use in any manner that, in the Host's judgment, unreasonably burdened the Host System, any network associated with it, or any other network associated with the Host — this could include, for example (but not as a limitation), bandwidth usage that the Host judged to be excessive;
  8. obscenity according to the standards in the geographic community where the User accessed the Host System;
  9. unsolicited bulk email creation, transmission, and/or use — this particular prohibition is intended to encompass, without limitation, junk mail, "spam," and multi-level marketing ("MLM") solicitations; and/or
  10. violation of any other acceptable-usage policy that the Host might publish from time to time — the Host would of course have to give the User and/or the Accessing Party reasonable notice if it did publish such a policy;
  11. allowing anyone else to use the User's access credentials to access the Host System;
  12. using someone else's credentials to access the Host System;
  13. impersonating someone else in connection with the Host System;
  14. establishing multiple user accounts to engage in one or more prohibited‑ or restricted activities;
  15. falsely pretending to represent another individual or entity in connection with the Host System;
  16. accessing anyone else's information stored on the Host System without proper authorization;
  17. tracing any information about, or owned by, any other user of the Host System — this would include, without limitation, personal identifying information and financial information of other users;
  18. interfering with anyone else's use of the Host System;
  19. selling or leasing access to the Host System;
  20. probing or attempt to defeat or bypass security measures, access-control filters or -blocks, or other mechanisms built into the Host System to enforce limitations such as (for example) time, geography, etc.;
  21. making, distributing copies of, or creating derivative works based on, any content, data, or other information provided via the Host System, other than: (i) the Accessing Party's own content, or (ii) as expressly authorized in writing by the Host or other owner of the content;
  22. otherwise infringing anyone else’s copyright, trademark, trade secret, or other intellectual property right in the course of using the Host System;
  23. disassembling, decompiling, or otherwise reverse-engineering any aspect of the System;
  24. use of a bot, screen scraper, Web crawler, or similar method to access the Host System or any content stored at the Host System, or otherwise accessing the Host System using any method other than the user interface provided by the Host;
  25. use of the Host System for high-risk activities — such as, without limitation, the operation of nuclear facilities, air traffic control, life-support systems, and/or the sole delivery of emergency communications — where the use, or failure, of the Host System could lead to death, personal injury, or environmental damage (unless the Con­tract clearly provides otherwise);
  26. attempting to do something prohibited by the Con­tract, whether or not the attempt is successful;
  27. inducing, soliciting, allowing, or knowingly helping anyone else to do something prohibited by the Con­tract, whether for the User's or Accessing Party's own benefit or otherwise.

9.5. Code of Conduct Compliance Protocol Protocol

Business context: A customer might legitimately ask that a prospective vendor contractually commit to abiding by a "code of conduct." See, e.g., Levi Strauss & Co.'s 23-page, Worldwide Code of Business Conduct. .

But some customer codes of conduct can be overreaching and overbearing — possibly trampling on the vendor's own legitimate interests and giving the customer unfair leverage in unrelated disputes.

And for a vendor, managing compliance with many customers' different codes of conduct can be a pain (see the note to § 9.5.2 below).

So, this Protocol puts "fences" around the customer's code of conduct, to help the customer and the supplier to postpone discussion of specific practices that the customer might strongly prefer or even insist on.

9.5.1. Definitions: Vendor; Customer

In this Protocol, "Vendor" refers to a party to the Con­tract where the Con­tract contemplates that the party will be providing goods and/or services to (or on behalf of, or at the direction of) another party, the "Customer."

Note

This section is worded to account for the situation where the Vendor isn't actually the one that provides goods and/or services to the Customer.

9.5.2. Applicability if agreed to

  1. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference..
  2. This Protocol will apply if, in the Con­tract or otherwise, the Customer promulgates a code of conduct (the "Code") that the Vendor is to follow.
  3. This Protocol will apply —
    1. even if the Customer's Code has a different title such as "policy manual" or "supplier handbook," and
    2. even the Code takes the form of, or was derived from, a general industry standard or practice.
Note

A commentator noted a few specific potential concerns about codes of conduct:

Audit provisions in P2P [private-to-private] Codes are often unrestricted in scope and lack protections for such concerns as confidentiality, waiver of attorney-client privilege, or competition-law exposure. …

Zero-tolerance prohibitions on investment in suppliers by public officials or their families are not unheard of[.

Some P2P Codes require notification if any of the business partner’s employees or their relatives have any financial interest in the code’s sponsor — all this in this age of public companies, mutual funds and 401Ks. …

Breach of any of these unrealistic requirements could be used as grounds for a pretextual contract termination, or withholding of payment.

Scott Killingsworth, The Privatization of Compliance, at 8 n.36 (SSRN.com 2014) (emphasis and extra paragraphing added).

9.5.3. Precedence

  1. This Protocol will take precedence over any inconsistent provision in the Con­tract, or in the Code, unless the Con­tract explicitly refers to this Protocol and clearly indicates that this Protocol will be of lower precedence.
  2. For example: Even if the Con­tract or the Code requires the Vendor to strictly comply with the Code, it would be enough for the Vendor to do as stated in this Protocol.
Note

The Vendor should consider consulting the Customer if an issue comes up that might implicate the Code, to try to identify and resolve potential disputes as early as possible.

9.5.4. Off ramps from strict Code compliance

The Vendor is free not to comply with one or more requirements in the Customer's Code if one or more of the following are true:

  1. the Customer does not require such compliance by the Customer's other suppliers and other relevant counterparties generally — see § 9.5.5 concerning the Vendor's right to verify this;
  2. the Vendor reasonably concludes that compliance with the Code requirement in question would require the Vendor to break the law (or run any significant risk of doing so);
  3. the Vendor shows that the Code requirement in question clearly deviates unreasonably from standard business practice in the relevant line of business;
  4. the Customer changes the Code in a way that would materially alter the Con­tract — for example, by imposing materially-greater costs (or other burdens) on the Vendor; and/or
  5. the Customer does not provide the Vendor with the Code requirement in question on a timely basis — in writing, in language that would not be seriously confusing to reasonable people in the Vendor's position. (A direct, "jump cite" link to an understandable, publicly-available document would normally suffice.)
Note

().  Background: This section provides specific "off ramps" for suppliers that would find it too burdensome to comply with particular requirements of customers' codes of conduct.

Subdivision 1 takes advantage of what might be thought of as "market forces" — if the Customer can't get its other suppliers to agree to comply with a given Code requirement, then that gives the Vendor more leverage in pushing back against being forced to comply.

Subdivision 2: The term "reasonably concludes" qualifier is vague, but it should get the parties talking.

Subdivision 4 addresses the situation where the Customer, wanting an excuse to terminate a multi-year contract, unilaterally demands that the Vendor comply with costly new Code requirements. (Posited by Sean Hogle at redline.net; see his comment of Sept. 4, 2025.)

Subdivision 5: The "not be seriously confusing" requirement is intended as a guardrail: The Vendor doesn't want the Customer playing "gotcha" games with carelessly- or deliberately-obfuscated Code requirements. True: The nonconfusing language requirement does leave the door open to future disputes. But the phrasing of the requirement puts a nontrivial burden of proof on the Vendor.

Subdivision 5: Just what would constitute a "timely" basis for providing the Code requirement might be open to debate, but the parties would at least be able to talk about it. (This could be a particular concern if the Customer were to demand that the Vendor agree to comply with the Customer's future changes to its code of conduct— for another approach to the future-revisions problem, see a discussion at redline.net.)

Negotiation tip: If the Customer is adamant in rejecting one or more of these off ramps, the Vendor could consider seeking to change the economics of the Con­tract — in other words, "make it about money."

9.5.5. Allowed: Verification of general Code use

The Vendor has the right — at reasonable intervals, and upon reasonable notice — to have an independent firm of certified public accountants (CPAs) do the following in accordance with Protocol 4.3 (audits and inspections, with confidentiality obligations):

  1. inspect a representative sample of the Customer's other relevant contracts from time to time; and
  2. report to the Vendor whether the Customer really does contractually require the Customer's other relevant counterparties to comply with the Code, as a whole and/or as to one or more particular Code requirements.
Note

The Customer might be tempted to say to the Vendor, Just trust us: All of our suppliers have agreed to our code of conduct. But this is one of those times where the nuclear-Navy saying comes to mind: You get what you INspect, not what you EXpect (see 9.8).

9.5.6. Not required: Perfect Code compliance

As a safe harbor, the Vendor would be deemed to have complied with the Customer's Code if, whenever the Customer reasonably asks:

  1. the Vendor conducts a reasonable review of the Code — together with one or more of the Customer's people, if either party asks;
  2. the Vendor gives good-faith consideration to whether the Vendor's business practices were a "good fit" for the Code (or could reasonably be adjusted to be a good fit); and
  3. the Vendor and the Customer consult togegther, if either party asks, about any particular business-related practices that the Code indicates that the Vendor is to follow (or not follow).
Note

().  Customer codes of conduct often are drafted by lawyers and others who don't appreciate the burden and cost of full compliance. So, this section outlines what would be enough in many circumstances.

Some might wonder if there are too many "reasonable" and "good faith" qualifiers in this section, leaving too many matters open for interpretation. But for this Protocol, that's likely to be preferable to spending time negotiating about unlikely — or unknowable — future events.

9.5.7. Code agreement ≠ certification of compliance

The Vendor's agreement to follow the Customer's Code is not a representation or warranty that all of the Vendor's relevant business practices would necessarily meet (or have met) with the Customer's approval.

Note

This is a guardrail clause, to try to dissuade "creative," 20-20 hindsight arguments in the future by the Customer's litigation counsel.

9.5.8. Customer's termination right

If the Vendor does not cure a noncompliance with the Customer's Code within a reasonable time after the Customer calls the Vendor's attention to the noncompliance via any reasonable means, THEN: The Customer has the right to terminate the Con­tract — but on a going-forward basis only, and in accordance with the termination general provisions at Protocol 18.9  — by giving the Vendor notice to that effect in accordance with Protocol 3.14.

Note

This section addresses what the Customer often really wants, which might be simply the ability to announce that the Customer has cut ties with the Vendor. That's been seen this in cases involving, for example, Kanye West and Kevin Spacey.21 See also Protocol 18.8, addressing termination for reputation risk. ¶ In some circumstances, a "reasonable" cure period might be no cure period.

9.5.9. EXCLUSIVE REMEDY (usually)

  1. Other than termination as set forth above, the Customer must not take (nor attempt to take) any other action against the Vendor for violating the Customer's Code unless the Customer can clearly show one or more of the following:
    1. the Vendor's action (or inaction) that failed to comply with a Code requirement would have been a breach of the Con­tract even if the Vendor had not agreed to comply with the Code; and/or
    2. the Con­tract as negotiated by the parties — not just the Code, and not just the Con­tract in a form that the Customer provided to the Vendor, for example, in the fine print of the Customer's purchase order or other document — clearly and specifically says that the Customer may sue the Vendor for breach of the Con­tract even if the Vendor breaches only the Code.
  2. For emphasis: The Customer's obligation in this section extends (without limitation) to the Customer's not doing (and not attempting to do) any of the following in response to the Vendor's noncompliance with the Code:
    1. filing suit against the Vendor;
    2. demanding arbitration; and/or
    3. withholding payment that would otherwise be due.
Note

().  This section seeks to balance the parties' legitimate interests.

Subdivision 1: The "must not take any other action" phrase here is included so that if the Customer tried to do otherwise in court or in arbitration, that attempt would itself constitute a breach of the Con­tract, for which the Vendor's damages would include attorney fees for contesting the attempt.

Subdivision 1.b allows the parties to override this exclusive-remedy provision, but they have to be both very intentional and very clear about it.

Subdivision 2: The intent here is to position the Vendor to seek a quick dismissal of any legal action that the Customer might bring in spite of the prohibition of this Protocol.

9.5.10. Sunset of termination right

The Customer's right to terminate under this Protocol will expire automatically if the Customer's notice of termination to the Vendor has not become effective in accordance with Protocol 3.14 on or before the earlier of the following:

  1. the date 60 days after the date that the Customer first became aware, by any means, of the earliest event that supposedly constituted a Code breach (the "Triggering Event"); or
  2. if earlier, the date six months after the date of that Triggering Event, regardless when the Customer learned — or should have known — about it.
Note

().  A termination deadline seems fair, so that the Vendor doesn't have to live with a Sword of Damocles hanging over its head after a Code violation.

Subdivision 1: It's reasonable to give the Customer a fairly-long period to decide whether the Triggering Event is going to be a problem.

Subdivision 2: Six months seems reasonable as a final cut-off date: If Customer has been able to tolerate Vendor's Code breach for that long, then it seems logical that the Customer hasn't been significantly harmed by the breach, and thus it'd be reasonable for the right to terminate to expire.

9.5.11. No effect on other accrued rights

If the Customer does terminate for a Code breach under this Protocol, THEN: The termination will not affect either party's other accrued rights and obligations under the Con­tract, if any, including without limitation the following:

Note

The parties' (canceled) future rights and obligations could include, e.g., the following: • any post-termination right that the Customer might have to buy goods or services from the Vendor at stated pricing or at a stated discount; and/or • any post-termination obligation that the Customer might have to buy goods or services from the Vendor during any particular time.

  1. the Customer's warranty rights for products and/or services obtained from the Vendor, if any; and
  2. the Vendor's payment rights for already-completed sales, if any.

9.5.12. Survival of this Protocol after termination

If the Customer does terminate for a Code breach, then this Protocol will continue in effect as stated in Protocol 18.1 (survival) except as specifically provided in this Protocol.

9.6. Discretion Definition

9.6.1. Definition

  1. Without more, "discretion" means reasonable discretion while acting in good faith.
  2. "Sole discretion" is unfettered and absolute; the actor may act as the actor see fit — taking into account no more than the actor's own interests and desires as the actor then perceives them — without the need to show any justification to anyone (as long as the actions are lawful, of course).
Note

().  In some U.S. jurisdictions, a party's discretion might be constrained by an implied obligation of reasonableness, or perhaps of good faith. Han v. United Continental Holdings, Inc., 762 F.3d 598 (7th Cir. 2014) (applying Illinois law). For more discussion of this point in the context of assignment-consent clauses, see the commentary at 15.3.6.1 and Note.

Subdivision B This borrows from the business-judgment rule that is applied to directors of a corporation, albeit without the other duties that bind directors, most notably the duties of loyalty and care. See generally, e.g., Lindsay C. Llewellyn, Breaking Down the Business Judgment Clause (Winston.com 2013), archived at https://perma.cc/TR7G-CNU8. ]

Caution: Even if a contract uses terms such as sole and unfettered discretion, a court might still harshly second-guess the actor if the circumstances seem egregious, as discussed at 9.6.2.2.

9.6.2. Discretion: Additional notes

9.6.2.1. The business context

Contracts often use the terms discretion, sole discretion, unfettered discretion, and reasonable discretion; this Protocol seeks to provide clear meanings for the underlying word discretion — while recognizing that courts might impose their own meanings, as discussed below.

9.6.2.2. "Sole and unfettered discretion" might not mean quite that

().  A New York appeals court took a jaundiced view of a party's position about a "sole and absolute discretion" clause in an agreement, noting that:

[E]ven where one has an apparently unlimited right under a contract, that right may not be exercised solely for personal gain in such a way as to deprive the other party of the fruits of the contract.

Thus, even an explicitly discretionary contract right may not be exercised in bad faith so as to frustrate the other party's right to the benefit under the agreement. Shatz v. Chertok, 180 A.D.3d 609, 610, 117 N.Y.S.3d 239, 2020 NY Slip Op 1383 (N.Y. App. Div.) (affirming denial of motion to dismiss complaint for breach of fiduciary duty; cleaned up, citation omitted, extra paragraphing added).

In the UK, there is case law indicating that discretion must be exercised in good faith and not arbitrarily, capriciously, or irrationally. See generally James Brown, Cathay Pacific Airways Limited v. Lufthansa Technik AG - the extent to which contractual rights be limited by considerations of good faith or a duty to act “rationally”? (HaynesBoone.com 2020) discussing Cathay Pacific Airways Limited v. Lufthansa Technik AG, [2020] EWHC 1789 (Ch); Barry Donnelly and Jonathan Pratt, Are you obliged to act reasonably?, in the In-House Lawyer, June 2013, at 20, https://perma.cc/H9HW-7KDA.

Analogously: In the context of judicial discretion, in a case Halo Electronics (U.S. 2016), concerning certain statutory trial-court discretion in patent cases, the Supreme Court noted that:

Discretion is not whim. In a system of laws discretion is rarely without limits, even when the statute does not specify any limits upon the district courts' discretion.

A motion to a court's discretion is a motion, not to its inclination, but to its judgment; and its judgment is to be guided by sound legal principles.

Thus, … a district court's discretion should be exercised in light of the considerations underlying the grant of that discretion. Halo Elecs., Inc. v. Pulse Elecs., Inc., 136 S. Ct. 1923, 1931-32 (2016) (cleaned up, citations omitted, extra paragraphing added). This concerned a trial court's statutory discretion, in "exceptional" cases, to increase the damages for patent infringement.

9.6.2.3. More explanation of permissible discretion factors can help

It can be helpful for a contract to explain the factors that can be permissibly taken into account in exercising discretion. Example: In a Second Circuit case:

  • An energy supply company was sued for breach of contract for allegedly failing to charge competitive rates for electricity.
  • The company's agreement form provided for a variable monthly rate that the company would set at its discretion; the agreement "listed several factors guiding that discretion, including 'market-related factors' and [the company's] 'costs, expenses and margins.'"

The court affirmed summary judgment in favor of the company because the plaintiff "received what was promised under the plain terms of the agreement …."

9.6.2.4. Edge case: An illusory contract

In a Texas case, a sale-and-purchase letter agreement gave a buyer the "sole discretion" to close a purchase transction (after doing due diligence about the purchase). A state court held that this unfettered walk-away right made the agreement contract illusory and unenforceable, as long as there was no separate consideration for the walk-away right. See Maverick Nat. Resources, LLC v. Glenn D. Cooper Oil & Gas, Inc., No. 02-23-00183-CV, slip op. (Tex. App.–Fort Worth Jun. 13, 2024).

9.7. Good Faith Definition

9.7.1. What's required for "good faith"?

The term "good faith" refers to conduct that: (1) is honest in fact; and (2) comports with reasonable commercial standards of fair dealing in the trade.

Note

().  Contract drafters sometimes explicitly set out good faith as a standard of performance of conduct. But as the Supreme Court observed in Northwest, Inc. (2014), "it does not appear that there is any uniform understanding of the doctrine's precise meaning." This means that agreeing to a good-faith standard could set the stage for costly litigation in the future.

This definition is a blend of:

  • Restatement of Contracts (Second) § 205, which states: "Every contract imposes upon each party a duty of good faith and fair dealing in its performance and its enforcement";
  • Uniform Commercial Code ("UCC") § 1‑304, which imposes a duty of good faith on all contracts and duties within the UCC; and
  • UCC § 2-103(b), which — for purposes of sales of goods — defines good faith (in the case of a merchant) as "honesty in fact and the observance of reasonable commercial standards of fair dealing in the trade."

    Students: Be sure to read 9.7.2.1.

    Note: This Definition doesn't itself impose any duty of good faith on any party.

9.7.2. Good faith Definition: Additional notes

9.7.2.1. Would the law impose a general duty of good faith?

It depends:

().  Unlike the law in many other states, Texas law doesn't impose a general duty of good faith and fair dealing in contractual relationships. As explained in Subaru (Tex. 2002), in that state, such a duty arises only in specific, limited circumstances: "A common-law duty of good faith and fair dealing does not exist in all contractual relationships. Rather, the duty arises only when a contract creates or governs a special relationship between the parties." Subaru of America, Inc. v. David McDavid Nissan, Inc., 84 S.W.3d 212 (Tex. 2002) (cleaned up, citations omitted); see also, e.g., Hux v. Southern Methodist University, 819 F.3d 776, 781-82 (5th Cir. 2016) (affirming dismissal of former student's tort claim against professor); Barrow-Shaver Resources Co. v. Carrizo Oil & Gas, Inc., 590 S.W.3d 471, 491 (Tex. 2019) (affirming court of appeals and declining to read a reasonableness qualifier into a consent-to-assign provision) (citing numerous cases); Garner v. Jack in the Box Inc., No. 02-23-00276-CV, slip op. part V.E (Tex. App—Fort Worth Oct. 9, 2025) (affirming take-nothing JNOV in favor of Jack in the Box).

Somewhat similarly, Delaware law takes a cautious approach in applying the implied covenant of good faith and fair dealing; as the state's supreme court explained:

Under Delaware law, sophisticated parties are bound by the terms of their agreement. Even if the bargain they strike ends up a bad deal for one or both parties, the court’s role is to enforce the agreement as written. …

There are, however, instances when parties fail to foresee events not covered by their agreement or defer decisions to later. No contract, regardless of how tightly or precisely drafted it may be, can wholly account for every possible contingency.

Subject to the express terms of the agreement, when gaps in an agreement lead to controversy, the court has in its toolbox the implied covenant of good faith and fair dealing to fill in the spaces between the written words. …

The implied covenant, however, is a cautious enterprise. … It cannot be invoked when the contract addresses the conduct at issue. The implied covenant should not have been deployed in this case. There was no gap to fill in the Agreement. Glaxo Group Ltd. v. DRIT LP, 248 A.3d 911, 919-20 (Del. 2021) (reversing, in part, trial-court judgment) (cleaned up, formatting revised). To similar effect, see case=7352410918828249241 Health Solutions, Inc. v. Pharma. Research Assoc., Inc., 891 S.E.2d 100 (N.C. 2023), part IV.B.1 (affirming dismissal of breach-of-contract claim).

California's implied covenant can't be used to "retrade the deal," as explained in Guz (Cal. 2000):

But while the implied covenant requires mutual fairness in applying a contract's actual terms, it cannot substantively alter those terms.

If an employment is at will, and thus allows either party to terminate for any or no reason, the implied covenant cannot decree otherwise.

Moreover, although any breach of the actual terms of an employment contract also violates the implied covenant, the measure of damages for such a breach remains solely contractual.

Hence, where breach of an actual term is alleged, a separate implied covenant claim, based on the same breach, is superfluous.

On the other hand, where an implied covenant claim alleges a breach of obligations beyond the agreement's actual terms, it is invalid. Guz v. Bechtel National, Inc., 24 Cal. 4th 352, 358, 8 P.3d 1089, 1110 (2000) (emphasis in original, extra paragraphing added); see also id., 24 Cal. 4th at 373-77; Derby v. City of Pittsburg, No. 16-cv-05469-SI, slip op. part V (N.D. Cal. Feb. 23, 2017) (citing Guz in granting defendant's motion to dismiss implied-covenant claim).

9.7.2.2. Disclaiming a good-faith obligation could be tricky

To be on the safe side, some drafters might be tempted to disclaim the implied covenant of good faith and fair dealing. But imagine how that could look to a judge or juror if the disclaimer were to be worded badly:

Neither party will be obligated to act in good faith nor to abide by any particular standard of fair dealing.

To the extent that an implied covenant of good faith and fair dealing applies by law, each party is to be conclusively deemed to have complied with that covenant if the party otherwise complied with the requirements of this Agreement.

9.7.2.3. Caution: Watch out for agreements to negotiate in good faith

An express agreement to negotiate in good faith can be enforceable — thus, an otherwise-nonbinding term sheet could still obligate the parties to negotiate in good faith to get the deal done, and a party's failure to do so could result in liability for breach of that obligation. This happened, for example, in a case where the Delaware supreme court where the court affirmed an award of $113 million in damages for breach of a term sheet's requirement that the parties negotiate in good faith. See SIGA Technologies, Inc. v. PharmAthene, Inc., 32 A.3d 1108 (Del. 2015) (en banc); see also, e.g., Cambridge Capital LLC v. Ruby Has LLC, 565 F. Supp. 3d 420, 440-41 (S.D.N.Y. 2021) (denying motion to dismiss: plaintiff had plausibly pled enough facts to support a claim of breach of agreement to negotiate in good faith in letter of intent) (citing cases). [DCT TO DO: SEE ALSO THE GEOFFREY MILLER PIECE CITED IN GOV. LAW, at 9-10, about the differences between NY law and California law.] ]

9.8. Inspections Protocol Protocol

You get what you inspect, not what you expect. – Attributed to Admiral Hyman G. Rickover, USN (1900-86), the father of the nuclear Navy (in which I served my ROTC scholarship payback time between college and law school).

Inspections can be costly, but they can also be useful and even necessary to avoid tragedy (see 2.2.2 for examples caused in part by lack of inspection or other second-checking). This Protocol provides inspection ground rules to help contracting parties keep their projects from derailing.

9.8.1. Parties: The Inspecting Party and the Host.

  1. When agreed to, this Protocol entitles a party (or parties) clearly so indicated in the Con­tract (each, an "Inspecting Party") to have an inspection conducted —
    • of relevant premises, books, records, or other tangible- or intangible materials,
    • of another clearly-indicated party (or parties), each, a "Host"),
    • by one or more individuals (each such individual, an "Inspector"); and/or
    • by one or more more machines.
  2. For convenience, this Protocol uses the singular term "Inspector" in this Protocol, even for cases where there are multiple Inspectors.
Note

In many contexts, inspectors of physical materials use machines to run tests.

9.8.2. Reasonable advance notice is needed for an inspection.

The Inspecting Party is to give the Host the stated advance notice of each requested inspection.

9.8.3. Inspections can be done only at reasonable intervals.

The Inspecting Party is not to ask for inspections except at the stated intervals.

Note

Too-frequent inspections could be burdensome and costly for the Host.

9.8.4. The Host can make reasonable decisions about inspection details.

The Inspecting Party is to to let the Host make the stated decisions about the timing and similar details of an inspection — as long in doing so, the Host consults with the Inspecting Party and the Inspector (unless there's good reason for the Host not to do so).

9.8.5. The Inspector will have reasonable access.

The Host is to give the Inspector reasonable access to all facilities, equipment, and information in the Host's possession, custody, or control — as that term is used used in federal-court litigation in the United States — where those things:

  1. are reasonably related to the subject of the inspection, and
  2. do not come within one or more of the exceptions at § 9.8.7 below.
Note

The term possession, custody, or control is familiar to litigators in the U.S.; under Fed. R. Civ. P. 26(a)(1)(A)(ii) and 34(a)(1), any relevant document within a party's possession, custody, or control would be fair game for production. See generally, e.g., Tess Blair and Tara S. Lawler, Possession, Custody or Control: A Perennial Question Gets More Complicated (2018).

9.8.6. The Host is to provide reasonable cooperation.

The Host is to instruct the Host's people to provide reasonable cooperation with the Inspector, including (without limitation):

  1. answering, completely and honestly, all reasonable questions from the Inspector; and
  2. noting any known limitations of their answers.

9.8.7. The Host can withhold certain information.

The Host has the right to withhold from the Inspectors, in the Host's sole discrection, some or all of the following "off-limits" information:

  1. information that, under applicable law, the Host would not have to turn over to another party in litigation, for example due to attorney-client privilege, work-product immunity, or any other applicable privilege;
  2. trade secrets; and/or
  3. any other categories of off-limits information that are specifically agreed to in the Con­tract.
Note

().  Subdivision 1: In the U.S., privileged information might completely lose its privileged status if provided to an outside party — and thus could have to be disclosed to future litigation adversaries. See, e.g., Texas Young Lawyers Association, Attorney-Client Privilege (TexasBar.com 2013).

Subdivision 2: Trade secrets could cause legitimate concern for a Host that supplies goods or services: Suppose that a competing supplier tells a Host customer, hey, Customer, why don't you let us "inspect" the Host for you, at no charge, and we'll tell you what we could do better. It's not hard to see how this could devolve into messy litigation. (See also Protocol 5.3 concerning confidential information.)

9.8.8. Professional conduct expected

Each party and that party's people must comply with the following:

  1. Protocol 9.13 (site visits) during any visits to another party's physical premises or computer system; and
  2. Protocol 9.4 (computer-system access) when accessing another party's computer system(s) and similar systems.

9.8.9. Inspectors' additional conduct standards

Each Inspector must do the following:

  1. conduct him- or herself in a professional manner at all times while interacting with the Host, the Host's personnel, and the Host's facilities, records, etc.; and
  2. comply with any generally-accepted standards — both procedural and substantive — for the relevant type of inspection.
Note

Such generally-accepted standards could include, for example, GAAP and/or IFRS rules; electrical- or plumbing codes; AICPA rules; etc.

9.8.10. Escalation

The Host and the Inspecting Party are to escalate, as provided in Protocol 3.4 and if necessary, Protocol 21.11, any disagreement about how any imprecise term in this Protocol should be applied. Examples:

  1. what is required for reasonable access; and
  2. what would constitute significant lack of cooperation.
Note

This allows the parties — if desired — to defer in-the-weeds discussions.

9.8.11. Certain confidentiality obligations apply.

  1. This section applies to the Inspecting Party and and each Inspector, each referred to here as a "Recipient."
  2. The Recipient must preserve in confidence, as the Host's confidential information, all non-public information — maintained by or on behalf of the Host and/or its affiliates and agents — to which the Recipient gains access via any inspection under this Protocol.
  3. The Inspector is not to disclose to the Inspecting Party — unless the Host first agrees otherwise in writing — any more information derived from the inspection than the following:
    1. whether the inspection revealed a discrepancy reportable under the Con­tract, and if so,
    2. the size and general nature of the discrepancy (if applicable),
  4. The Recipient is not to use the Host's confidential information except to the extent necessary for:
    1. correction of any discrepancies identified in the inspection for which the Recipient bears any responsibility (if any); and/or
    2. enforcement of the Inspecting Party's rights under the Con­tract.

9.8.12. Definition: Good reason.

For purposes of this Protocol and other inspection-related provisions of the Con­tract, the term "good reason" includes without limitation any one or more of the following:

  1.  significant lack of cooperation by the Host; and/or
  2. the discovery of substantial evidence of: (i) fraud, and/or (ii) material breach of the Con­tract, in either case by (or attributable to) the Host.

9.8.13. Survival of this Protocol

The inspection-related provisions of the Con­tract, including but not limited to those of this Protocol:

  1. will survive any termination or expiration of the Con­tract — but only as to matters that would have been subject to inspection before termination or expiration; and
  2. will remain subject to all deadlines and other limitations stated in the Con­tract.
Note

Having inspection provisions survive termination (or expiration) could be important, as discussed in the notes to § 4.3.28.

9.8.14. Option: Host Flowdown Requirement

  1. If this Option is agreed to, THEN: The Host is to see to it that, in any subcontract that the Host enters into under the Con­tract, the subcontractor is legally obligated to do the following:
    1. let the Inspecting Party conduct inspections (including but not limited to audits, where applicable) as provided in the Con­tract;
    2. let the subcontractor to deal directly with the Inspecting Party and Inspector in that connection; and
    3. include substantially the same requirements in any sub-subcontract that the subcontractor enters into.
  2. Note: This Option does not otherwise address whether, nor how, any party may engage subcontractors.
Note

See generally the discussion of "flowdowns" at 3.6.3.

9.8.15. Additional notes

9.8.15.1. Why inspections might be necessary

People are human, and so [foul]-ups happen even when people have the best of intentions.

  • Sometimes people get in over their heads.
  • Sometimes people misunderstand the instructions they're given — possibly because the other people who gave the instructions didn't state them clearly (perhaps because those other people are themselves in over their heads).
  • Sometimes people cut corners, perhaps because they'd prefer to do other things (or they're under pressure to save time or money, or they have too much on their plates).
  • Sometimes people suffer a brain cramp, i.e., a momentary mental lapse.
  • Sometimes people lie, or cheat, or steal.

These all-too-human tendencies can have severe adverse consequences in a contract engagement.

9.8.15.2. A few historical examples — some of them tragic

Here are some examples of why inspections can be appropriate and even urgently necessary:

NYC building crane collapse: In 2008, seven people were killed, and numerous others were injured, in the collapse of a building crane in New York City. The accident was attributed to sloppy work — and, presumably, a lack of inspection of the work — in erecting the crane. Both criminal charges and civil actions were brought against various people and companies. See, e.g., John Eligon, Rigging Contractor Is Acquitted in the Collapse of a Crane (NYTimes.com 2010).

Falsified earthquate safety data: A Japanese firm "admitted to doctoring earthquake safety data for buildings across the country, including some venues for the 2020 Tokyo Olympics." This represented "only the latest example of corner cutting and data fudging by Japanese firms. … industrial giant Kobe Steel admitted it falsified information on products sold to major brands including Boeing and Toyota, while care [sic] maker Nissan had to halt production after problems in its inspection process emerged." See, e.g., Junko Ogura and James Griffiths, Tokyo 2020 Olympics venues linked to earthquake safety data scandal (CNN.com Oct. 20, 2018).

Nuclear submarine loss: In April 1963, the American nuclear-powered submarine USS Thresher sank during post-shipyard sea trials, killing all 129 people aboard. While the cause is still debated, the Navy's initial investigation concluded that the sinking had likely resulted from defective work (on non-reactor systems) by shipyard personnel. In response, the Navy (instigated by Admiral Rickover) implemented the SUBSAFE program of rigorous inspection and testing of all materials and workmanship involved in building submarines, and the same for nuclear-reactor systems in Navy surface ships. See generally USS Thresher (SSN 593) (Wikipedia.org).

NASA spacecraft loss: In 1962, NASA destroyed its Mariner 1 probe to Venus just five minutes after liftoff because the rocket was moving erratically. NASA later determined that the handwritten instructions for programming the rocket's guidance system included equations that contained the symbol "R" (for "radius"). This R, though, should have been R̄ ("R-bar"), i.e., an average of data. Because of this, the guidance-system software was incorrectly coded. That — plus a hardware glitch — caused the rocket to veer off course. See Mariner 1 (Wikipedia.org).

The Mariner 1 and Thresher accidents, in particular, illustrate the value of following the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings). Tragically appropriate here, a Navy version of this principle might be R.O.O.F., in which F[oul]-ups is substituted for Mistakes.

The SUBSAFE program, implemented in response to the Thresher disaster, is discussed above. Likewise, concerning Mariner 1, a Smithsonian Institute Web page points out that:

The [Mariner 1] disaster revealed a critical need to thoroughly debug software before launch. NASA also learned that software can be engineered so that small errors do not impact safety. Thanks to NASA's corrective actions, several Apollo lunar modules safely landed on the Moon despite minor software "bugs."

9.8.15.3. Inspections can identify and fix other problems, too

In 2022, the federal government found numerous instances in which commercial Medicare insurance plans — which can increase their profits by denying claim coverage — were refusing to pay for health care that they should have paid for.

9.9. Reasonable Definition

9.9.1. Safe harbor

  1. The term "reasonable" (whether or not capitalized), as an adjective, refers to something fair; proper; moderate; sensible; as viewed from the perspective of persons having ordinary ability and skill in the relevant field(s) who take into account the relevant circumstances.
  2. Upon request by any involved party: Any disagreement whether prospective action would be reasonable is to be addressed in accordance with Protocol 3.4 (internal escalation) and, if that doesn't resolve the disagreement, with Protocol 21.11 (escalation to neutral advisor).
Note

().  Many contracts defer detailed discussion of performance standards by saying, in effect, that A will do Such-and-Such in a "reasonable" manner. This Definition seeks to add some clarity to what that means in a business context — and to provide a streamlined mechanism for addressing disagreements on that score.

This definition draws on:

  • Black's Law Dictionary 1518 (11th ed. 2019); and
  • the patent-law concept of persons having ordinary skill in the art, applicable in assessing whether a claimed invention would have been obvious (and therefore unpatentable) at the time it was invented; see 35 U.S.C. § 103.

9.10. Reasonable Efforts Definition

9.10.1. Definition

  1. The term "reasonable efforts" to achieve a goal refers to such efforts as would satisfy prudent persons who, in the conduct of their own affairs, sought to reach that goal for their own benefit.
  2. At either party's request, the parties will escalate, as stated at Protocol 21.11, any persistent disagreement about what future efforts would qualify as "reasonable" in the circumstances.
Note

().  This Definition is adapted from the definitions of "reasonable assurances" and "reasonable detail" in a U.S. statute requiring certain issuers of securities to keep books and records and maintain internal controls. See 15 U.S. Code § 78m(b)(7). • For related reading, see 9.1 (best efforts); 9.2 (commercially-reasonable efforts); and 9.7 (good faith).

Pro tip: When a party is obligated to use reasonable efforts, it can make sense to err on the side of doing more than just what that party sees as the bare minimum. That's because: • the other party — or a future judge or jury — might think that the bare minimum required more than what the party did; and • doing more than just the bare minimum would help show the party's good faith — always a good idea, both for business relationships and in litigation.

9.11. Responsible Definition

9.11.1. Definition

  1. The term "responsible" — in the sense of being responsible or taking responsibility, and whether or not the term is capitalized — refers to action that is both reasonable and conscientious.
  2. As one illustrative example: To make responsible efforts to achieve an objective means to make at least such efforts as a reasonable person would make in a conscientious attempt to achieve that objective.
Note

().  Sometimes in negotiations, parties A and B won't be able to agree that B will in fact succeed in taking action X, but:

  • A will want B to make more of a commitment than simply "reasonable efforts" (see 9.10) or even "commercially-reasonable efforts" (see 9.2); but
  • B is unwilling to make the even-stronger commitment to use "best efforts" (see 9.1).

For those situations, this Definition gives drafters a way to express that concept verbally (i.e., in words) as responsible efforts.

The term responsible is perhaps vague, but it's not unknown in the law. Example: Martin Marietta Materials (2012): The Delaware chancery court, in describing the duration of a preliminary injunction, referred to it as a "responsible period," albeit shorter than the period to which the claimant arguably would have been entitled. Martin Marietta Materials, Inc v. Vulcan Materials Co., 56 A.3d 1072, 1147 (Del. Ch. 2012), aff'd, 68 A.3d 1208 (Del. 2012) (en banc).

9.12. Satisfactory Definition

9.12.1. Definition

  1. The meaning of the term satisfactory, when used in the context such as satisfactory to A, depends on the context.
  2. If the Con­tract calls for A's satisfaction as to matters generally regarded as reasonably objective in nature — such as, for example, commercial value or quality — then:
    1. the standard is what would be satisfactory to a reasonable person in the circumstances; and
    2. A must not unreasonably assert that A is not satisfied.
  3. If the Con­tract calls for A's satisfaction in matters of taste or aesthetics, then A need only act honestly and in good faith in deciding whether or not it is satisfied.
  4. If the Con­tract calls for A's satisfaction in A's sole discretion or similar language, then the standard applicable to discretion will apply (see 9.6).

9.12.2. Additional notes

Federal judge Richard Posner once explained how "satisfaction" issues are adjudicated:

Suppose the manager of a steel plant rejected a shipment of pig iron because he did not think the pigs had a pretty shape. The reasonable-man standard would be applied even if the contract had an "acceptability shall rest strictly with the Owner" clause, for it would be fantastic to think that the iron supplier would have subjected his contract rights to the whimsy of the buyer's agent.

At the other extreme would be a contract to paint a portrait, the buyer having reserved the right to reject the portrait if it did not satisfy him. Such a buyer wants a portrait that will please him rather than a jury, even a jury of connoisseurs, so the only question would be his good faith in rejecting the portrait. Morin Building Prods. Co. v. Baystone Constr., Inc., 717 F.2d 413, 415 (7th Cir. 1983) (Posner, J.; affirming judgment on jury verdict awarding subcontractor unpaid amount when General Motors rejected subcontractor's work on aesthetic grounds) (formatting revised). See the following footnote for additional citations.22

9.13. Site Visit Protocol Protocol

9.13.1. Applicability of this Protocol

  1. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference., it applies when one or more "people" — defined below; each, a "Visitor") of a party (a "Visiting Party") — accesses or attempts to access (referred to as a "Site Visit") a "Host Site," defined below.
  2. For emphasis: This Protocol does not itself authorize anyone to access a Host Site: it only states ground rules for any case in which such access occurs.
Note

().  When one party "P" enters into a contract with another party "OP," it's not uncommon for P's people to visit an OP worksite and/or access an OP computer system. This Rule lays out a basic framework for such events.

Caution: This Rule isn't intended as a "code of conduct"; were it otherwise, and if Protocol 9.5 were also agreed to, then the remedies for breach of this Rule would be limited — and that's not the intent here.

Subdivision a: For readability, Visitors are sometimes referred to here as the Visiting Party's Visitors.

9.13.2. Definitions

For purposes of this Rule:

  1. The term "Host Site" refers to:
    1. any physical premises of another party (the "Host"); and/or
    2. any computer system, network, or other system of the Host — concerning which, see also Protocol 9.4 (computer-system access).
  2. The terms "people" and "personnel" of a party refers to the following:
    1. for an individual party: the party him- or herself;
    2. for an organizational party (a corporation, LLC, etc.): the party's officers, directors, employees, members, managers, and other individuals in similar positions; and
    3. others acting under the party's direction in furtherance of the party's activities relating to the Con­tract.
Note

Here's a hypothetical example of the extent of the term "people": (1) At a Host-Party site, one of the Visiting Party's people, Valerie, is repairing a valve of a piping system. (2) Valerie asks a passing Host-Party employee, Hans-Peter: Hey, would you please hand me that wrench? Hans-Peter does so. (3) In that scenario, Hans-Peter counts as "Visiting-Party people" for purposes of handing Valerie the wrench, but not for any other purpose — so if, seconds later, Hans-Peter were to punch someone in the mouth, Hans-Peter would not be considered "Visiting-Party people" for that purpose.

(Why include this example? Because clients and courts have sometimes found such "worked examples" to be useful, as discussed at 20.21.4.3.)

9.13.3. Who is responsible for Visitors' actions?

The Visiting Party is to see to it that its Visitors comply with this Rule — this includes, for example, appropriately instructing them in their obligations under this Rule.

9.13.4. Might evidence of Visitor employability be needed?

If reasonably requested by the Host, the Visiting Party is to timely provide the Host with reasonable evidence of legal employability on-site for Visitors who access the Host's physical premises.

Note

Evidence of Visitor employability could be an especially-salient concern for both parties during Donald Trump's second term in the White House — and for the Host in particular if the Host had previously entered into a non-prosecution agreement after being caught employing aliens not having the legal right to work. Such a situation arose in 2018 with a branch of waste-disposal giant Waste Management, Inc., as explained in a Department of Justice press release. (Note: U.S. law already requires most if not all employers to verify that their employees have the right to work in this country.)

9.13.5. What compliance obligations do individual Visitors have?

The Visiting Party is to see to it that each of its Visitors complies, at all times during any Site Visit, with the following:

  1. this Rule;
  2. such other reasonable Host-Site rules and policies as the Host timely communicates to the Visiting Party and/or to the Visitor;
  3. prudent safety practices;
  4. Protocol 9.4, which deals with computer-system access, whenever a Visitor has access to a Host system;
  5. reasonable standards of professional conduct; and
  6. applicable law — including but not limited to export-control law — and other prohibitions on access by certain categories of individuals.
Note

See generally 31.9 concerning export controls.

9.13.6. What if an unsafe situation arises?

If a Visitor becomes aware of an actual- or potential unsafe situation at a Host Site, THEN that Visitor is to take prudent action in response to the situation — which normally would include promptly attempting to alert and/or consult with the Host.

9.13.7. Indemnity obligation for unlawful conduct

  1. Each party "A" is to defend and indemnify each other party and each other party's Protected Group "B" from "unlawful conduct," defined below, on the part of A and/or any of A's people, at any time during a Site Visit by a Visiting Party (whether that be A or B).
  2. For this purpose, "unlawful conduct" is intended to be interpreted broadly, encompassing, without limitation, any and all of the following types of conduct:
    1. (if A is the Host:) denying access to the Host Site to one or more Visitors for an impermissible reason, for example, on grounds of race, etc.;
    2. other unlawful discrimination;
    3. unlawful retaliation; and
    4. other tortious conduct by A's people.
Note

Subdivision b.3 has in mind things such as (for example) forcing a worker to leave a site in retaliation for refusing sexual advances, complaining about discriminatory treatent, etc.

9.13.8. Each party is to bear its own expenses of site visits.

As between the parties, each party is to cover all out-of-pocket expenses incurred by that party's people in connection with a Site Visit — without reimbursement by any other party to the Con­tract or its people — unless clearly agreed otherwise in writing.

Note

Concerning "As between the parties," see the discussion at 32.4.

9.13.9. Indemnity obligation against third-party claims

Each party "A" is to defend and indemnify each other party and each other party's Protected Group "B" against any claim • by any third party (including but not limited to the other party's own people) • arising from misconduct by any of A's people • in connection with a site visit by A's people to a B site or vice versa.

10. Governance

DCT comment: These protocols are arranged (mostly) alphabetically, for easy adoption in a short-form contract ("the Con­tract") to help streamline drafting, review, and negotiation.

Contents:

10.1. Adoption of LCP26 Provisions Protocol

DCT comment: I can't say this is a frequently-used provision; I'm putting this Protocol here for reader convenience.

10.1.1. Effect of Adopting Lighthouse Provision(s)

  1. This Protocol sets out what happens when the parties agree to a contract ("the Con­tract") that adopts one or more of the following (each, a "Lighthouse Provision"):
    1. this Governance (this "Protocol") without being more specific;
    2. a specific Lighthouse Protocol; and/or
    3. an "Option."
  2. The Con­tract could adopt a Lighthouse Provision:
    1. by incorporating it by reference, either explicitly or in some other way that is clear to the reader;
    2. by stating that the Provision is adopted; or
    3. in any other reasonable manner.
  3. Exception: See § 10.1.8 concerning the status of Lighthouse Options.

10.1.2. Adoption is a binding commitment

When a contract (the "Contract") adopts a Lighthouse Protocol, each party is agreeing to follow that Protocol as a mandatory obligation — with any variations specified in the Con­tract — just as if the Protocol had been written out word-for-word in the Con­tract itself.

(In legalese, the Protocol is "incorporated by reference.")

10.1.3. If this Governance is adopted

When this Protocol is adopted, the Lighthouse protocols provisions in it are incorporated by reference in the Con­tract — but, to reiterate, not any Option unless the Con­tract explicitly says so.

10.1.4. "Will" means "must" (ditto: "shall" and "is to")

  1. For a more-collaborative and business-friendly tone: If a Lighthouse Protocol uses the term "will," in connection with a party's action, it has the same meaning as must — and the same is true for "shall," "is to," and "are to."
  2. As a hypothetical example: "A will take Action X" mean that A has committed, and is required, to take Action X.
Note

In many cases I much prefer the term will (or, is to), and not must or shall, when writing contract obligations for business reasons. That's especially true when I'm representing a vendor of goods or services that's dealing with a customer or potential customer. That's because the terms will and is to seem to have a more-collaborative and less-imperious tone than must or shall, which can help foster a successful long-term relationship or even just a one-shot transaction.

Example: In one court case, a franchise agreement used by the Days Inn hotel chain used will for the franchisee hotel operator's obligations:

8.1 Independent of your obligation to procure and maintain insurance, you will indemnify, defend and hold the Indemnitees harmless ….

8.2 You will respond promptly to any matter …. You will reimburse the Indemnitee …. Days Inns Worldwide, Inc. v. 4200 Rose Hospitality LLC, No. 2:22-cv-04822, slip op. at part I.A (D.N.J. Aug. 25, 2025) (granting, in part, Days Inns motion for partial summary judgment; unpublished) (emphasis added).

To be sure, this isn't a major point. But in sales, minor points can make a difference, and sometimes be decisive whether a sale will be made.

10.1.5. Permissive or suggestive terms

  1. The terms can do X and free to do X or OK to do X have the same meaning as may do X.
  2. In some places, the Lighthouse protocols include terms phrased, e.g.:
    • as permission (such as, "A may take Action X" or "A can take Action X");
    • as a reminder;
    • as a pro tip;
    • as a suggestion (such as, "the parties should consider taking Action X"); or
    • as a preference (such as, "the parties should preferably take Action X [do something]").

Such permissive terms do not create any binding obligation, on any party, even when the parties agree to follow the Lighthouse protocols in question.

Note

Subdivision 1: The Lighthouse protocols sometimes use can and free to because the phrase Party A may do X might come across as imperious and unneighborly.

Subdivision 1 — DCT comment: I prefer not to use may for a possibility; instead, use may solely for permission and might solely for possibility. (See 7.2.2 for slightly longer discussion.)

10.1.6. NOT A SUBSTITUTE for licensed legal advice

All concerned: If you use this book in any manner, you are acknowledging, per Protocol 11.2, that: (1) this book is not a substitute for legal advice, from a licensed attorney, about your specific situation, and you are not to rely on it as such; and (2) your use does not establish an attorney-client relationship between you and any author, editor, publisher, etc. of this book.

Note

().  DCT comment: In colloquial terms, YMMV ("your mileage may vary"), and the author(s), etc., of this book aren't your lawyer(s).

This Protocol is intentionally written in second-person ("you") form for greater emphasis and reader impact.

10.1.7. Larger type for Lighthouse protocols and Option operative text

The binding, operative text of each Lighthouse Protocol (such as this § 10.1.7) and Option is presented in a larger, sans-serif font.

Note

For those interested in Web-design details, the operative text of the Lighthouse Provisions (such as that of this § 10.1.7) is "set" in the Arial font, with CSS fallbacks to other sans-serif fonts.

10.1.8. Options must be specifically adopted

A Lighthouse Option applies only if the Con­tract itself clearly adopts that particular provision.

Note

Most of the Options in this book have headings that are phrased to allow easy adoption in the Con­tract by simply saying, e.g., "The Lighthouse Option: Unapproved Subcontractors (§ 13.15.29) is incorporated by reference." or "The following Lighthouse optional provisions are incorporated by reference: [LIST]."

10.1.9. Other text: Nonbinding commentary

Text in a smaller, serif font is a non-binding author's note.

Note

This note is an example — it's set in the Georgia font, with CSS fallbacks to other serif fonts.

Important note to students: In your reading assignments, be sure to read the notes.

10.1.10. Placeholder text: Variables for possible negotiation

Some words or phrases are presented in bold-face brown (as in this example text) as placeholder terms that one or more parties might want to try to negotiate. Those words or phrases are binding as presented — that is, if their respective Lighthouse Provisions are included in the Con­tract — if the Con­tract does not clearly state otherwise.

Note

Here's a hypothetical example: "Payment terms are net 30 days." This symbology helps call attention to terms that parties might want to negotiate.

10.1.11. Placeholder names

Some Lighthouse Provisions use A and B as party placeholder names when it does not matter which party is which.

Note

().  Subdivision 1: The placeholder names "A" and "B" are used here because they're likely to be already familiar to lawyers and law students, who've doubtless seen those letters used as placeholder party names in, e.g., the Restatement (Second) of Contracts.

Some notes use the placeholder names Alice and Bob, which are well-known in communications-network technology and elsewhere in the tech world. Other notes use the placeholder names Fred and Ginger — contracting parties could do worse than to strive for the coordinated adeptness of the legendary dance partners and film stars Fred Astaire and Ginger Rogers.

10.1.12. What if the Con­tract just adopts the LCP26 book?

If the Con­tract adopts this LCP26 book — that is, incorporates it by reference — without being more specific, THEN: Each party is agreeing to follow the Lighthouse protocols listed below, but no others unless specifically mentioned in the Con­tract: [TO COME]

10.2. Contrary Positions Protocol

Aggressive lawyers, for a variety of self-interested reasons — notably, wanting to please their clients by telling the clients what they (the clients) want to hear  — will sometimes try to argue that a contract provision doesn't really mean what it says. That can significantly increase the time and cost of resolving disputes. So: This Protocol — modeled on Rule 11 of the Federal Rules of Civil Procedure — seeks to discourage such opportunistic behavior by establishing consequences for it.

10.2.1. Applicability if adopted

If this Protocol is adopted, it will govern if — in any lawsuit or other dispute relating to the Con­tract — a party (the "Asserting Party" asserts a position contrary to an express- or unmistakably-implied term of the Con­tract (referred to here as the "Contrary Assertion").

Note

DCT note: I haven't seen, in actual contracts, language along the lines of this Protocol. But drafters might want to consider it, for the reasons discussed in the notes following the language below.

10.2.2. Liability for attorney fees

  1. The Asserting Party will pay (or reimburse) all attorney fees and costs incurred — by any other party to the dispute — in contesting the Contrary Assertion, extending through the date that the Asserting Party formally withdraws its assertion as stated in § 10.2.3 below.
  2. The Asserting Party is responsible for all such attorney fees no matter what stage the dispute is at when the other party incurs the attorney fees in question, including but not limited to appeals.
Note

Without language such as this, a limitation of liability (e.g., a damages cap or an exclusion of consequential damages) might be held to constitute merely a waiver and not a breachable covenant. That was the central issue in two Texas supreme court cases in the same year — with opposite outcomes. Compare James Constr. Grp., LLC v. Westlake Chem. Corp., 650 S.W.3d 392, 415-18 (Tex. 2022) (5-4, reversing court of appeals: contract's exclusion of consequential damages was not really a covenant not to seek them, so customer did not breach by seeking such damages) with id. at 425 (Boyd, J., dissenting in part: parties' agreement that "no claim shall be made" for consequential damages constituted covenant not to sue for such damages) and Transcor Astra Group S.A. v. Petrobras America Inc., 650 S.W.3d 462, 483 (Tex. 2022) (9-0, reversing court of appeals: party breached contract by asserting fraud claims despite contract's reliance disclaimer). Conceivably, in Transcor Astra, the court might have regarded dispute-settlement agreements as warranting special treatment, having noted that "Texas law encourages parties to resolve their disputes by agreement …." Id. at 473.

10.2.3. Formal withdrawal turns off liability meter

To stop incurring liability for attorney fees under § 10.2.2, the Asserting Party must formally withdraw the Contrary Assertion, either:

  1. in a writing communicated to both the other party and the tribunal, or
  2. orally, on the record in a proceeding of the tribunal.

10.2.4. Examples of covered assertions:

The following are (non-limiting) examples of actions, assertions, or claims by an Asserting Party that would be contrary to the Con­tract and thus would trigger this Protocol:

  1. seeking consequential damages (see Protocol 21.5) if the Con­tract excludes the Asserting Party's recovery of such damages;
  2. seeking damages in excess of an agreed "cap" or other monetary limitation (concerning which, see Protocol 21.7);
  3. asserting a purported right, or a purported obligation, that had previously been waived (see Protocol 3.18);
  4. asserting a claim that the Asserting Party had previously released;
  5. asserting that a notice took effect at a time inconsistent with the notice provisions stated in the Con­tract (concerning which, see Protocol 3.14);
  6. asserting that the Con­tract or a related document was amended or otherwise modified in a manner inconsistent with the amendment provisions of the Con­tract (see Protocol 3.1);
  7. asserting that an action was timely if taken after a deadline stated in the Con­tract or a related document (for example, a statement of work);
  8. asserting that the governing law is that of some jurisdiction other than as stated in a governing-law clause (see Protocol 21.14);
  9. filing a lawsuit or arbitration in a forum inconsistent with a forum-selection clause (concerning which, see Protocol 21.12).
Note

This section "writes around" the holding in James Construction Group, discussed in the note to § 10.2.2 above.

10.3. Defined-Terms List Protocol

10.4. Other Necessary Actions Protocol

10.4.1. Each party's obligation

Each party must take the following actions — when clearly necessary or ‑appropriate to further the clear purpose of the Con­tract — if the other party asks from time to time, namely:

  1. sign and deliver one or more other relevant documents, and
  2. take one or more other relevant actions.
Note

This Protocol and language like it are sometimes seen in merger- and acquisition agreements; they're not often seen in everyday commercial agreements but could be useful in that context.

10.4.2. Escalation of certain disputes

If either party asks, the parties will escalate any dispute about the reasonableness of a request under § 10.4.1 in accordance with the procedures at Protocol 21.11.

Note

Chances are that a disagreement of this nature would get resolved fairly soon into an escalation.

10.5. Writing-Requirement Challenges Protocol

A party to a contract might want to try to skirt a writing requirement — e.g., a requirement that amendments and/or waivers be in writing. Toward that end, the party might claim that the writing requirement was itself waived in some manner other than a writing. (This is discussed at length at 10.5.4.1.) This Protocol is meant to give such a party a reason to think twice before doing so.

10.5.1. Applicability

When This Protocol is agreed to, it applies when A asserts:

  1. that B supposedly waived an otherwise-applicable writing requirement, in the law, or in the Con­tract, such as that of Protocol 3.1, and
  2. that B did that waiver in some manner other than through a signed writing.

10.5.2. Required: Heightened proof

A's assertion that B waived the writing requirement is to be given no effect unless:

  1. A proves that B actually did waive the writing requirement itself; and
  2. A's proof on that point is by heightened evidence as provided in Delaware law.
Note

Delaware law allows a party to assert that a written-amendment requirement was orally waived — but the asserting party must meet a heightened standard of proof (see 10.5.4.2).

10.5.3. Attorney fee liability for challenges

If the applicable law does not allow waivers of the writing requirement in question, and/or A fails to prove its waiver assertion as required by § 10.5.2, THEN: A must pay B's attorney fees incurred in contesting A's waiver assertion.

Note

This section is designed to encourage A to think twice before making its assertion of a writing-requirement waiver.

10.5.4. Additional notes

10.5.4.1. A court might — or might not — disregard a contractual writing requirement

(Students, you can just skim this section.)

Here's a business problem: Sometimes parties to a contract, in the course of their dealings will agree orally to modify the contract, or to waive a contract requirement. Of course, the parties should follow up with written documentation of the modification. But that doesn't always happen — even when the contract specifically requires such a writing.

Even when a contract clearly says that amendments must be in writing, in litigation a party might claim that the parties orally agreed to waive that writing requirement.

This doctrine is illustrated in a century-old New York precedent — for mnemonic purposes, we'll call it the "Cardozo Rule," after its author, later a Supreme Court justice — parties are free to orally waive a contractual requirement that amendments and waivers must be in writing, subject to any possible impact of the statute of frauds (see 32.35):

Those who make a contract, may unmake it.

The clause which forbids a change may be changed like any other.

The prohibition of oral waiver, may itself be waived.

Every such agreement is ended by the new one which contradicts it.

What is excluded by one act, is restored by another.

You may put it out by the door, it is back through the window.

Whenever two men [sic] contract, no limitation self-imposed can destroy their power to contract again [to amend the first contract]. Beatty v Guggenheim Exploration Co., 225 N.Y. 380, 387-88 (1919) (Cardozo, J.), quoted in Israel v. Chabra, 12 N.Y.3d 158, 163-64, 878 N.Y.S.2d 646, 906 N.E.2d 374 (2009) (cleaned up, extra paragraphing added).

And some other jurisdictions will likewise let parties at least argue that a writing requirement was orally waived. New Zealand and Singapore are two examples. See Savvy Vineyards 3552 Ltd. v. Kakara Estate Ltd., [2014] NZSC 121, ¶ 112, discussed in Jeremy Bell-Connell and Hayden Wilson, No oral modification clauses need a closer look in New Zealand (JDSupra 2021); Lim v Hong, [2021] SGCA 43, discusssed at Julian Bailey and Matthew Secomb, Singapore goes its own way on ‘no oral modification’ clauses (JDSupra 2021).

10.5.4.2. Piercing a contractual writing requirement might require heightened proof.

().  In contract cases, Delaware law (grudgingly) allows a party to assert that the parties orally agreed to waive an amendments-in-writing requirement. (See the discussion of the "Cardozo Rule" at 10.5.4.1.)

But Delaware law also says that the asserting party must meet a heightened evidentiary burden, because the state's law disfavors such assertions. See, e.g., Tunney v. Hilliard, No. 1317, letter op. at 14 & n.16 (Del. Ch. Aug. 20, 2008), aff’d, 970 A.2d 257 (Del. 2009).

Example: Massachusetts law allows such claims; this was noted in a federal court opinion, which allowed a contractor's lawsuit over a purported equity grant to move forward, but with a veiled warning about the proof requirement:

A provision that an agreement may not be amended orally but only by a written instrument does not necessarily bar oral modification of the contract.

Whether an oral modification occurred can be inferred from the conduct of the parties and from the attendant circumstances of the case.

The proponent of the oral modification must present evidence of sufficient force to overcome the presumption that the integrated and complete agreement, which requires written consent to modification, expresses the intent of the parties. Hoffman v. Thras.io Inc., 538 F. Supp.3d 196, 206 (D. Mass. 2021) (denying relevant part of motion to dismiss, citing cases; cleaned up, emphasis and extra paragraphing added).

Similarly, under California law, even if a contract does contain an amendments-in-writing requirement, a party can try to claim that the requirement was orally waived — but the party must specifically prove that the waiver happened.

Example: In a case out of Hollywood, the parties fought over how to share the profits from the TV series Home Improvement. Long story short:

  • An appeals court ruled that a jury must decide whether the Disney company had orally waived or agreed to modify an incontestability provision in the contract in suit — whether by words or by conduct.
  • But (said the court): The plaintiffs would still have to specifically prove that Disney had in fact waived the requirement. See Wind Dancer Production Group v. Walt Disney Pictures, 10 Cal. App. 5th 56, 62, 215 Cal. Rptr. 3d 835 (2017); id., 10 Cal. App. 5th at 78-79, citing California Civil Code § 1698(d).

    To be sure: It might seem strange to adopt a state's law for one specific provision in a contract. But it's not unprecedented, as discussed at 21.14.5.17.

10.5.4.3. And a writing requirement might well be enforced.

(Students, you can just skim this section too.)

In New York, the Cardozo Rule has (largely) been overruled by statute; see N.Y. General Obligations Law 15-301(1), which provides that: "A written agreement … which contains a provision to the effect that it cannot be changed orally, cannot be changed by an executory agreement unless such executory agreement is in writing and signed[:] [i] by the party against whom enforcement of the change is sought or [ii] by his agent." (Emphasis and bracketed text added.)

In some other U.S. jurisdictions, courts will likewise uphold contractual requirements that amendments and waivers must be in writing. See, e.g., DeValk Lincoln Mercury, Inc. v. Ford Motor Co., 811 F.2d 326, 334 & n.2 (7th Cir. 1987); to like effect, see Ryan Companies U.S., Inc. v. FDP WTC, LLC, No. 20-1366, slip op. (Iowa App. Jan. 12, 2022) (unpublished; reversing, in part, judgment awarding breach-of-contract damages to contractor).

Example: The UK's Supreme Court once cited the Cardozo Rule but expressly rejected it. The court concluded that "the law should and does give effect to a contractual provision requiring specified formalities to be observed for a variation." Rock Advert. Ltd v MWB Bus. Exch. Ctrs. Ltd, [2018] UKSC 24 ¶¶ 7, 10.

10.5.4.4. Pro tip: Do some kind of written confirmation

A good #MuscleMemory habit: Any written confirmation of a purported oral waiver is better than none. It's far, far better to confirm an amendment to the Con­tract — even with a minimalist writing such as an email exchange or even just an unanswered text — than to rely on fallible human memory. As the Ninth Circuit once noted in another context (a dispute concerning an alleged transfer of copyright ownership): "It doesn't have to be the Magna Charta; a one-line pro forma statement will do." Effects Assoc., Inc. v. Cohen, 908 F.2d 555, 557 (9th Cir. 1990).

11. Contract interpretation

11.1. Contract Interpretation Protocol

contra-prof

r-no-contra-rule

11.2. Acknowledgements Effect Protocol

Many contracts are drafted by one party to state that one or both parties "acknowledges" something or another. That generally has a specific legal effect, recapped in this Protocol.

11.2.1. Waiver of proof

When a party A acknowledges a statement of fact and/or law relating to the Con­tract (the "Statement"), THEN: The acknowledgement has the following effects:

  1. A is agreeing that the Statement is true for all purposes relating to the Con­tract.
  2. A is also WAIVING — that is, A is agreeing to dispense with — any requirement that another party to the Con­tract B must produce evidence to support the Statement.
Note

().  Caution: If you sign a contract with an "acknowledgement" in it, you might be making a significant concession that could bite you later; see 11.2.3.6 for discussion.

Subdivision 2: See also Protocol 3.18 (waivers).

11.2.2. Sticky nature of acknowledgements

Depending on the applicable law, A might not be able to withdraw or modify A's acknowledgement of a Statement without B's agreement.

Note

Caution: See 11.2.3.2 for an example of a company that found itself stuck with significant financial obligations under a patent license because what the company had "acknowledged" in the license agreement.

11.2.3. Additional notes

11.2.3.1. Why include acknowledgements in a contract?

Having a party "acknowledge" one or more things in a contract can save time and money by pre-establishing agreed facts for future litigation. This can help parties save the time and cost that might otherwise be needed to "prove up" those facts, because in the U.S., an "acknowledgement" in the body of a contract is much like an admission in litigation. But: A party might be stuck with its acknowledgements — to its detriment ….

(Not quite the same: "Notarizing" a document, discussed at 29.7.)

11.2.3.2. You could be stuck with an acknowledgement

If your client acknowledges something in a contract, it could lock the client into a position that the client might later want to modify or even disavow based on updated information. That's because an acknowledgement in a contract is much like an admission in a lawsuit — and in U.S. federal cases, the trial judge has discretion to allow a party to back away from a previous admission, under Rule 36(b) of the Federal Rules of Civil Procedure.

Example: A German company, Peiker Acustic, developed and sold technology for hands-free cell phone use. Peiker signed a contract with Cellport Systems to be licensed under certain Cellport patents.

  • In the license agreement, Peiker "acknowledged" that two particular Peiker products came within the scope of the patent claims. (That's the point of saying that an acknowledgement could be of a statement of law.)
  • Later, though, Peiker changed its mind and tried to back away from that acknowledgement, claiming that those products weren't covered by the patent after all, and thus that Peiker shouldn't have to pay royalties for them.

Peiker won in the trial court, which said that the acknowledgement in the license agreement was merely a "rebuttable presumption."

On appeal, though, the Tenth Circuit reversed and remanded as to that part of the case, holding that Peiker did indeed have to pay royalties on those products. See Cellport Sys., Inc. v. Peiker Acustic GmbH & Co., KG, 762 F.3d 1016, 1022-23 (10th Cir. 2014) (reversing and remanding trial-court judgment in part).

11.2.3.3. Caution: An "acknowledgement" might create binding obligations

"Acknowledging" terms and conditions in a contract might be interpreted as assenting to and agreeing to be bound by those terms and conditions. This would likely be the case, though only if the acknowledgement was reasonably clear about the binding effect. Pro tip: Drafters, in this situation (as in so many others), it's often better to err on the side of in-your-face explicitness.

Example: An employee was held to have agreed that his employer would own certain intellectual property that the employee created, because the employee had clicked on an "acknowledge" button for the employer's invention-assignment agreement. See Apprio, Inc. v. Zaccari, 104 F.4th 897, 907 (D.C. Cir. 2024).

Counterexample: A state supreme court held that what an employee had acknowledged (i.e., a directive to read a new policy) hadn't modified the employee's pre-existing employment contract — consequently, arbitration wasn't required. See Lampo v. Amedisys Holding, LLC, 445 S.C. 305, 914 S.E.2d 139 (2025) (reversing and remanding court of appeals decision).

Example: A client of a Royal Bank of Canada investment-banking unit signed the bank's standard customer agreement.

  • The customer agreement included a first-person statement in which the client said, "I agree that all transactions with respect to any such Account shall be subject to the following terms."
  • Among those "following terms" was that the customer's transactions with the bank would be "subject to" external rules, including FINRA rules.

Citing numerous cases, the Eighth Circuit held that such "I agree" and "subject to" language was an acknowledgement that put the client on notice of how transactions would be handled — even though that language didn't constitute a contractual commitment by the bank to handle transactions in that way. See Luis v. RBC Capital Markets, LLC, 984 F.3d 575, 580 (8th Cir. 2020) (citing numerous cases), affirming 401 F. Supp. 3d 817 (D. Minn. 2019) (summary judgment dismissing clients' breach-of-contract claims against bank).

Example: Cisco, a global networking-technology conglomerate, once used a set of "standard terms and conditions of purchase" to accompany purchase orders submitted to suppliers. In those Cisco T&Cs, section 1 states as follows:

Supplier's electronic acceptance, acknowledgement of this Purchase Order, or commencement of performance constitutes Supplier's acceptance of these terms and conditions. (Bold-faced emphasis added.) Archived at https://perma.cc/SD47-YCHU, discussed briefly at 13.9.12.4.

So: Suppose that a supplier receives one of those Cisco POs, and a supplier representative responds by email, "got it, thanks." According to Cisco's T&Cs, the supplier might have legally agreed to all of Cisco's terms.

11.2.3.4. An acknowledgement invites reliance.

As discussed at 16.2 (and illustrated in the "Hill of Proof" diagram at 16.2.2): Suppose that B wants to claim that, by signing a contract with a particular statement in it — let's call it the "Statement" — A had made a false representation. Technically, for B to meet its burden of proof, it must show:

  1. that B had in fact relied on the Statement;
  2. that A had intended for B to rely on the Statement;
  3. that under the circumstances, B reliance on the Statement was reasonable.

As a practical matter, if the contract stated that A acknowledged the Statement — e.g., the statement about patent coverage in the Cellport contract above — then B would likely have a much-easier time making all of these showings.

11.2.3.5. Who might be bound by an acknowledgement?

In some circumstances, a party that didn't sign the Con­tract might be bound by it, for example as a so-called third-party beneficiary (concerning which, see Protocol 11.8).

11.2.3.6. Pro tip: Don't be a [jerk] in drafting acknowledgements.

Some inexperienced drafters include statements in which another party "acknowledges" a supposed fact that would be against that party's interest, big time. Here's an overreaching example of a kind that's sometimes seen in confidentiality agreements ("NDAs"), along with a possible edit:

  Recipient acknowledges that Discloser would be irreparably harmed by a breach or threatened breach of Recipient's confidentiality obligations under this Agreement.

  Recipient acknowledges that Discloser could be irreparably harmed by a breach or threatened breach of Recipient's confidentiality obligations under this Agreement.

(Emphasis added.)

Note the change from "would" to "could be irreparably harmed." If you're the Discloser-drafter here, your hope is (presumably) that the Recipient would overlook the "would be irreparably harmed" language. That'd amount to the Recipient's unthinkingly waiving the Discloser's burden of proof in seeking a preliminary injunction or comparable relief (see 21.10).

That, though, would likely slow up getting to signature: Diligent Recipient counsel, confronted with this kind of language, would probably do one or more of the following:

  • be at least mildly irritated at Discloser's counsel for the obnoxious drafting; and
  • change "would be …" to "could be irreparably harmed" as shown above; or
  • delete the equitable-relief acknowledgement entirely — this would be an example of Discloser's drafter having (unwisely) "poked the bear," see 8.14.

11.3. Certifications Definition

Some contracts require one party to "certify" in writing that the certifying party has complied with specified contract obligations; see, e.g., Information Purge Protocol (5.4). What does that mean?

11.3.1. Multiple functions of certifications

If A certifies a statement, whether in the Con­tract or in a related document, then unless the certification clearly states otherwise, A is doing the following things for the benefit of each other party to the Con­tract B:

  1. warranting that the statement is true;
  2. representing that — so far as A is aware — (a) the statement is true, and (b) no one has asserted otherwise;
  3. representing that A caused a reasonable investigation to be made before A made the certification; and
  4. acknowledging that B: (i) is entitled to rely on the certification, and (ii) will be doing so.
Note

().  Subdivision 1 and 2: See the discussion of representations and warranties (and the difference between them) at 16.2.

Subdivision 3 is to give other parties to the Con­tract some comfort that the certifying party actually knows what it's talking about in making the certification.

Subdivision 4 is included because a party alleging misrepresentation must usually prove (among other things) that the party relied on the representation and that its reliance was reasonable; this subdivision makes both of these things clear.

11.3.2. Additional notes

11.3.2.1. Upside of a certification requirement

When you're the certifying party, a certification requirement can:

  • give you an incentive to do a good job in complying with the relevant contract obligations; and
  • help you to identify specific areas that might need attention before a dispute arose — and thus possibly help to avoid the dispute in the first place.
11.3.2.2. Possible downside

Your certification would give the other party ammunition with which to blast you with a "they lied!" accusation, if it were to turn out that you'd overlooked something and thus your certification was incomplete or inaccurate.

(See 20.34.6.7 for more about how trial lawyers like to use "they lied!" in litigation, because non-expert judges and jurors will understand lying, whereas they might or might not fully understand the merits.)

11.4. Contra Proferentem Waiver Option

Contra proferentem means, approximately, "against the offeror." It's a Latin phrase, used as shorthand for how — if a contract provision is capable of two or more plausible meanings — then a court might interpret the provision in favor of the party that didn't draft the provision. Note to students: Learn to spell contra proferentem — you'll be seeing it!

11.4.1. Waiver

Each party agrees — and no party may assert otherwise — that the Con­tract is to be interpreted as though its wording resulted from the parties' informed negotiation of that wording, without applying the interpretive doctrine of contra proferentem ("against the offeror").

Note

Contra proferentem can come into play if a potential ambiguity in particular contract language can't be resolved by other conventional methods — e.g., by consulting other language in the contract, and/or by considering extrinsic evidence such as course of dealing and usage in the trade. When that occurs, courts will often resolve the matter by interpreting the language against the party that drafted it and thus is "to blame" for the problem.

(But: If a contract provision isn't ambiguous, then contra proferentem won't come into play in the first place.)

11.4.2. Additional notes

11.4.2.1. Why courts (sometimes) use the contra proferentem doctrine

The policy basis for contra proferentem was explained by the Supreme Court:

Respondents drafted an ambiguous document, and they cannot now claim the benefit of the doubt. The reason for this rule is to protect the party who did not choose the language from an unintended or unfair result. Mastrobuono v. Shearson Lehman Hutton, Inc., 514 U.S. 52, 62-63 (1995) (reversing 7th Circuit) (citations and footnotes omitted).

The contra proferentem principle is roughly analogous to the well-known "I cut, you choose" approach that is seen, for example, in what are sometimes called "shotgun" buy-sell agreements. See, e.g., Divide and choose (Wikipedia.org); Spice (2017) (application to gerrymandering).

11.4.2.2. Who might want to disclaim contra proferentem – and why

A party to a contract might have sufficient bargaining power that the party can successfully insist on using its own contract form in dealing with other parties. When that's the case, that party (i.e., the party with the bargaining power) might try to include a waiver of the contra proferentem doctrine in its contract form.

11.4.2.3. Caution: Disclaiming contra proferentem can cause problems.

In some jurisdictions, courts readily enforce contra proferentem disclaimers; Delaware is such a jurisdiction. See Texas Pacific Land Corp. v. Horizon Kinetics LLC, 306 A.3d 530, 549 (Del. Ch. 2023) (Laster, V.C.), aff'd w/o opinion, 314 A.3d 685 (Del. 2024).

To similar effect is a Tenth Circuit case in which the court applied New Jersey law and the contract language in question was: "The Parties acknowledge that this Agreement is the result of negotiations so neither Party shall avail itself of any rule of construction that would resolve ambiguities against a drafting party." ORP Surgical, LLC v. Howmedica Osteonics Corp., 92 F.4th 896, 921 n.14 (10th Cir. 2024).

But: Suppose that a court or arbitrator concluded that there was no way to resolve an ambiguity in a contract, other than by applying the contra proferentem principle — but the parties had agreed that contra proferentem was not to be used. The results in that situation might be unpredictable:

  • The tribunal might disregard the contra proferentem prohibition and apply the principle anyway to resolve the ambiguity; or
  • the tribunal might rule that the ambiguous provision could not be enforced — which in some circumstaces might jeopardize the enforceability of the entire contract. Hat tip: Jonathan Ely, in a comment in a LinkedIn group discussion (group membership required).
11.4.2.4. Courts use contra proferentem only as a last resort

Courts generally won't apply contra proferentem unless both the following are true:

First: A particular provision in a contract must appear to be "ambiguous" — that is, there must be two or more potentially-plausible meanings for the provision.

(For more on ambiguity in contracts, see 7.)

If a contract provision clearly isn't ambiguous — for example, if one of the party-asserted meanings simply isn't plausible — then the contra proferentem doctrine won't come into play in the first place.

Second: The seeming ambiguity must not be capable of being resolved by other conventional methods — for example, by consulting other language in the contract and/or by considering extrinsic evidence such as course of dealing and usage in the trade. As the U.S. Supreme Court explained:

The [contra proferentem] rule applies only as a last resort when the meaning of a provision remains ambiguous after exhausting the ordinary methods of interpretation.

At that point, contra proferentem resolves the ambiguity against the drafter based on public policy factors, primarily equitable considerations about the parties' relative bargaining strength. …

Unlike contract rules that help to interpret the meaning of a term, and thereby uncover the intent of the parties, contra proferentem is by definition triggered only after a court determines that it cannot discern the intent of the parties.

When a contract is ambiguous, contra proferentem provides a default rule based on public policy considerations; it can scarcely be said to be designed to ascertain the meanings attached by the parties.

Like the contract rule preferring interpretations that favor the public interest, contra proferentem seeks ends other than the intent of the parties. Lamps Plus, Inc. v. Varela, 587 U.S. 176, 139 S. Ct. 1407, 1417 (2019) (reversing and remanding Ninth Circuit's affirmance of order compelling class-wide arbitration) (cleaned up, emphasis in original, extra paragraphing added).

11.4.2.5. Other policy considerations can outweigh contra proferentem

Based as it is on public-policy considerations, the contra proferentem principle can be trumped by other policies. The (U.S.) Supreme Court explicitly so held in a decision where the Ninth Circuit had applied contra proferentem to an ambiguous arbitration provision and determined that the parties had implicitly agreed to class-wide arbitration (see generally the commentary at 21.1.23). The Court would have none of it, with the majority remarking that "[s]uch an approach is flatly inconsistent with the foundational FAA principle that arbitration is a matter of consent." Lamps Plus, 139 S. Ct. at 1418.

11.4.2.6. Special case: Standard form contracts

The contra proferentem principle might be especially important when interpreting an ambiguous provision of a standard form contract. In 2021, the Delaware chancery court explained that if a contract isn't negotiated, then: "Extrinsic evidence … cannot speak to the intent of all parties to the agreement." Bandera Master Fund LP v. Boardwalk Pipeline Partners, LP, No. 2018-0372, slip op. at 111 (Del. Ch. Nov. 12, 2021) (after bench trial, holding that general partner was liable for nearly $690 million in damages; ambiguous provisions in limited partnership agreement are construed against the general partner) (emphasis added); rev'd on other grounds, 288 A.3d 1083, 1134-35 (Del. 2022) ("this extrinsic evidence may provide a view of what occurred in the periphery").

11.4.2.7. Related: "No drafting history" clauses might be enforced

Example: Delaware's Vice Chancellor Laster provided an extensive review of case law in enforcing the "No Drafting History" provision that was found at the end of the following contract clause:

Each party and its counsel cooperated and participated in the drafting and preparation of this Agreement,

and any and all drafts relating thereto exchanged among the parties will be deemed the work product of all of the parties and may not be construed [sic; see 8.18 on humility in drafting] against any party by reason of its drafting or preparation.

Accordingly, any rule of law or any legal decision that would require interpretation of any ambiguities in this Agreement against any party that drafted or prepared it is of no application and is hereby expressly waived by each of the parties,

and any controversy over interpretations of this Agreement will be decided without regard to events of drafting or preparation. See Texas Pacific Land Corp. v. Horizon Kinetics LLC, 306 A.3d 530, 549 (Del. Ch. 2023) (emphasis by the court, extra paragraphing added), aff'd w/o opinion, 314 A.3d 685 (Del. 2024).

11.5. Knowledge Definition Option

This Option is adapted from commonly-used definitions in merger- and acquisition agreements, such as the merger agreement between software giant Symantec Corporation and BindView Corporation.

11.5.1. Basic definition: Knows, etc.; aware

  1. When this Option is agreed to, it will apply whenever the Con­tract (or any related document) includes a covenant (i.e., a promise), a representation, or a warranty — each, a "Statement" — where the Statement:

    1. refers to "knowledge" of or about Thing X on the part of a specified individual or organization, and/or
    2. asserts that the individual or organization "knows" Thing X (or knew, or will know, etc., Thing X),

    in connection with a matter related to the Con­tract.

  2. The term "so far as [a person] is aware" about Thing X is a Statement about Thing X.
Note

Subdivision 2 – DCT comment: I prefer to say "so far as A is aware," instead of "to A's knowledge." That's because I could conceive of someone trying to argue that the latter version includes an implicit representation by A that A actually has knowledge. (I've never heard of anyone trying do make such an argument, but the former version is cheap insurance.

11.5.2. Actual knowledge; timing

  1. Each of the knowledge-related terms quoted in § 11.5.1 refers to actual knowledge — at the time in question — about Thing X, as opposed to imputed knowledge.
  2. Those terms do not encompass things that a hypothetical prudent individual would have or should have known (whether in the ordinary course of carrying out the hypothetical individual's duties or otherwise).

11.5.3. Who must possess the knowledge

Where an organization is concerned, each of the terms quoted in § 11.5.1 above refers to knowledge on the part of one or more individuals having substantial operational responsibility, on behalf of the organization, in the matter in question.

11.5.4. No particular investigation implied

Unless the Statement itself clearly says otherwise, none of the terms quoted in § 11.5.1 is intended to imply that the Statement was made after any particular investigation.

11.6. Past Dealings Disclaimer Option

11.6.1. Disclaimer

No party may assert that the parties' past dealings have the effect of modifying or supplementing the Con­tract.

Note

().  Language like that of this Protocol is sometimes seen in companies' "canned" standard forms, e.g., in customers' purchase-order terms and conditions and sellers' terms of sale.

Caution: Agreeing to this Agreement could later put a party at a disadvantage in possibly-unpredictable ways.

11.7. Reliance Waiver Option

In jurisdictions such as Texas, an entire-agreement clause in a contract (see Protocol 3.3) might not be enough to defeat a party's subsequent claim that the party was fraudulently induced into entering into the contract — in such jurisdictions, an express waiver of reliance on statements outside the contract would be required (and in some cases might not be enough even then).

Contents:

11.7.1. WAIVER

When this Option is part of the Con­tract, each party specified is a "Waiving Party" for purposes of this Option unless otherwise specified.

Note

Some drafters might want to make this a one-way waiver, in which only one party is waiving reliance.

11.7.2. No reliance on Outside Statements

  1. By signing the Con­tract, each Waiving Party confirms:
    1. that the Waiving Party is not relying on any alleged "Outside Statement," defined in subdivision 2 — and WAIVES any such reliance — in deciding to enter into the Con­tract;
    2. that the Waiving Party is capable — on its own and/or with any desired independent professional advice — of evaluating and understanding the terms, conditions and risks of the Con­tract and the transaction(s) contemplated by the Con­tract; and
    3. that the Waiving Party understands and accepts those terms, conditions, and risks.
  2. For purposes of this waiver, an "Outside Statement" is any statement of fact or opinion — including but not limited to a representation — where the representation:
    1. is made by (or attributable to) a party to the Con­tract other than the Waiving Party; but
    2. is not set forth in the Con­tract itself (including but not limited to its attachments, exhibits, schedules, etc., if any).
Note

This Protocol draws in part on a disclaimer that was successfully invoked by the Bank of America in an Eighth Circuit case. See Bank of America, N.A. v. JB Hanna, LLC, 766 F.3d 841, 856 (8th Cir. 2014) (affirming summary judgment in favor of bank). Hat tip: Brian Rogers.

11.7.3. Limits on reliance waiver

  1. This Option does not waive any party's reliance on any representation, warranty, or other statement in the Con­tract itself; this includes (but is not limited to) any that are set forth in attachments, exhibits, materials incorporated by reference, etc.
  2. But: This Option does not affect any express waiver of reliance on a particular representation, etc., that is stated in the Con­tract.

11.7.4. Other Waiving-Party agreements

  1. The Waiving Party does not rely on any alleged Outside Statement in deciding to enter into the Con­tract.
  2. The Waiving Party does not make any claims inconsistent with this Option.
  3. The Waiving Party intends for the other party or parties to the Con­tract — when they enter into the Con­tract — to rely on the Waiving Party's waiver, certifications, and agreements in this Protocol.
Note

().  Subdivision 2: See Protocol 10.2 (attorney fees for contrary positions).

Subdivision 3: See 20.34.6.2 (significance of reliance statement).

11.7.5. Special provision under California law

Each Waiving Party WAIVES the benefits (if and to the extent available) of Section 1542 of the California Civil Code, which states: "A general release does not extend to claims that the creditor or releasing party does not know or suspect to exist in his or her favor at the time of executing the release and that, if known by him or her, would have materially affected his or her settlement with the debtor or released party."

Note

This section is included out of an abundance of caution, in case the reliance waiver of this Protocol is considered an "advance release" under California law; see generally the discussion at 21.30.2.

11.7.6. Additional notes

11.7.6.1. Why include a reliance waiver?

Unlike some entire-agreement clauses, a reliance waiver could defeat a misrepresentation claim. That's why reliance waivers are often paired with entire-agreement clauses:

  • In an entire-agreement clause, a statement that "there are no other representations" might not be enough to defeat a claim of fraudulent inducement to enter into the contract.
  • But: Under the law in many U.S. jurisdictions, a contracting party (the "claimant") that claims misrepresentation by the other side normally would have to prove, among other things, that it reasonably relied on the alleged misrepresentation.
  • That gives the other side's contract drafter a reason to include an express waiver of reliance, which would (or at least should) make it unreasonable per se for the claimant to rely on the the alleged misrepresentation — because, by promising not to rely on outside statements, the claimant stipulated that such reliance would not be reasonable (although some courts will disregard a reliance waiver if it appears that the other party out-and-out lied).

Here's a hypothetical example: Suppose that the following takes place:

–  Fred and Ginger enter into a contract for Ginger to sell Fred a house located several hundred miles away from either of them.

–  In the contract, Ginger represents to Fred that the house is in good condition, but does not warrant it.

–  After the closing, the house turns out to be a wreck.

Even though Ginger didn't warrant the condition of the house, Ginger might be liable for misrepresentation. For Fred to succeed with a misrepresentation claim, though, he would have had to "hit the checkpoints" along the way up the Hill of Proof (see 16.2.2) for some additional elements of proof: Fred would have to show (probably among other things) that he had reasonably relied on Ginger's representation.

Of course, Fred might well have a powerful incentive to prove his reasonable reliance: If he could establish Ginger's liability for misrepresentation, then he might be able:

  • to rescind the contract, and/or
  • perhaps even to recover punitive damages from Ginger; See, e.g., Huy Fong Foods, Inc. v. Underwood Ranches, LP, 66 Cal. App. 5th 1112, 1126, 281 Cal. Rptr. 3d 757 (2021) (affirming $23 million jury verdict for breach of contract and fraud).

neither of those remedies would normally be available in a breach-of-warranty action.

So Ginger will want to head off accusations that she lied — planning ahead, she might want to include, in the contract, a statement that Fred isn't relying on any representations by Ginger. That way, if Fred were to sue Ginger for misrepresentation, a judge might very well rely (so to speak) on the disclaimer and summarily toss out Fred's claim by dismissing it on the pleadings. When a reliance disclaimer is sufficiently clear — and especially when the contracting parties are big enough to take care of themselves — many courts might well give effect to the disclaimer under freedom-of-contract principles. See, e.g., IBM v. Lufkin Industries, LLC, 573 S.W.3d 224, 226 (Tex. 2019) (reversing court of appeals and rendering judgment for IBM on Lufkin's fraudulent-inducement claims because of contractual disclaimer of reliance and totality of the circumstances, but setting aside jury verdict for IBM on Lufkin's contract claims and remanding for new trial); West Loop Hosp., LLC v. Houston Galleria Lodging Assocs., LLC, 649 S.W.3d 461, 489 (Tex. App.–Houston [1st Dist.] 2022, pet. denied) (affirming summary judgment dismissing plaintiff's fraud claim).

11.7.6.2. Caution: Express "no reliance" language might be necessary.

Under Texas law, the "no reliance" language above is important for drafters to understand. That's because, in the oft-cited Italian Cowboy Partners (2011), the state's supreme court explained:

Pure merger clauses, without an expressed clear and unequivocal intent to disclaim reliance or waive claims for fraudulent inducement, have never had the effect of precluding claims for fraudulent inducement. …

There is a significant difference between a party[:]

  • disclaiming its reliance on certain representations, and therefore potentially relinquishing the right to pursue any claim for which reliance is an element, and
  • disclaiming the fact [sic] that no other representations were made.

 * * *

We have repeatedly held that to disclaim reliance, parties must use clear and unequivocal language. this elevated requirement of precise language helps ensure that parties to a contract — even sophisticated parties represented by able attorneys — understand that the contract's terms disclaim reliance, such that the contract may be binding even if it was induced by fraud.

Here, the contract language was not clear or unequivocal about disclaiming reliance. For instance, the term "rely" does not appear in any form, either in terms of relying on the other party's representations, or in relying solely on one's own judgment.

This provision stands in stark contrast to provisions we have previously held were clear and unequivocal. Italian Cowboy Partners, Ltd. v. Prudential Ins. Co., 341 S.W. 3d 323, 333-37 (Tex. 2011) (reversing court of appeals; merger clause did not preclude tenant's claim that landlord had fraudulently induced lease agreement by misrepresenting condition of property) (quotation edited for readability). The court provided a three-column table, contrasting different clauses.

DCT comment: It could be argued that these two disclaimers — a disclaimer of external representations, versus a disclaimer of reliance on external representations — logically amount to exactly the same thing (you can't rely on a representation that doesn't exist). The Italian Cowboy Partners quotation above suggests that in the Texas supreme court's view, a disclaimer of extrinsic representations, standing alone, is insufficiently explicit and "in your face" to alert the other side about what it was being asked to give up.

Delaware law likewise requires anti-reliance language in order to preclude a fraud claim. As the Chancery Court explained: "[A]n integration clause, standing alone, is not sufficient to bar a fraud claim; the agreement must also contain explicit anti-reliance language" — except that "an integration clause alone is sufficient to bar a fraud claim based on expressions of future intent or future promises." Trifecta Multimedia Holdings Inc. v. WCG Clinical Services LLC, 318 A.3d 450, 458 (Del. Ch. 2024) (denying, in part, defendants' motion to dismiss; footnotes omitted).

Colorado law is to the same effect: "[T]he mere fact of a merger clause does not effect a waiver of the tort claim. And unlike [a prior case] in which the court found that a merger clause precluded a fraudulent-inducement claim because it disproved reliance as a matter of law, the merger clause here says nothing about reliance." See City of Fort Collins v. Open Int'l, LLC, No. 24-1152, part I.B, slip op. at 17-18 (10th Cir. Jul. 23, 2025) (affirming judgment on jury verdict of fraudulent inducement by contractor) (cleaned up, citations omitted).

Pro tip: If you're drafting a contract where the law will be that of a jurisdiction such as Texas or Delaware or Colorado, it's likely to be important to include an explicit reliance waiver — but that might be a "red flag" that causes the other party to wonder whether your client is trustworthy ….

11.7.6.3. Fraud claims might survive even a no-reliance provision

Suppose that Ginger claims that Fred misrepresented facts to induce Ginger to enter ito a contract, and that Fred's misrepresentation wasn't merely negligent, but intentional. AND: Suppose also that the contract contains a no-reliance clause. In such a situation, Fred should not hold out much hope that a court would summarily toss out Ginger's fraudulent-inducement claim against him; the judge might very well insist on a full trial. See generally Andrew M. Zeitlin & Alison P. Baker, At Liberty to Lie? the Viability of Fraud Claims after Disclaiming Reliance (GMLaw.com 2013); see also Neal A. Potischman, Stephen Salmon, Alyse L. Katz, John A. Bick, Kirtee Kapoor and Lawrence Portnoy, Will Anti-Reliance Provisions Preclude Extra-Contractual Fraud Claims? Answers Differ In Delaware, New York, And California (Mondaq.com 2016).

That might be even more true if the plaintiff was not "sophisticated" and/or was not represented by counsel in the transaction in question. See, e.g., Carousel's Creamery, L.L.C. v. Marble Slab Creamery, Inc., 134 S.W.3d 385 (Tex. App.–Houston [1st Dist.] 2004) (reversing and remanding directed verdict for defendant on negligent-misrepresentation claim).

Counterexample: Delaware's chancery court held that when a party allegedly made a representation in a contract, knowing it to be false, the contract's anti-reliance and non-recourse clauses would not bar a fraud claim. Recalling a scene from the classic movie Butch Cassidy and the Sundance Kid, the court ruled:

… while contractual limitations on liability are effective when used in measured doses, the Court cannot sit idly by at the pleading stage while a party alleged to have lied in a contract uses that same contract to detonate the counter-party’s contractual fraud claim. That’s too much dynamite. Online Healthnow, Inc. v. CIP OCL Investments, LLC, slip op. at 4 (Del. Ch. Aug. 12, 2021) (denying defendants' motion to dismiss), citing ABRY Partners V, L.P. v. F & W Acquisition LLC, 891 A.2d 1032 (Del. Ch. 2006).

Another counterexample: The Bank of America once sold a foreclosed home subject to an "as-is" disclaimer — but the bank stated that it had "little or no direct knowledge" of problems, when in fact the bank's people knew that there were serious mold problems. A Wisconsin appeals court affirmed judgment on a jury verdict in favor of the buyer, saying that:

There was sufficient evidence to support the jury's verdict that the Bank made a deceptive statement concerning the sale of the property [namely, that the bank had little or no direct knowledge of the condition of the house] with the intention of inducing the sale of the property and that Fricano suffered a loss as a result of that representation.

The “as is” and exculpatory clauses in the parties' contract do not, as a matter of law, relieve the bank/seller of liability under § 100.18(1) for its deceptive representation in the contract which induced agreement to such terms. We affirm. Fricano v. Bank of America NA, 366 Wis.2d 748, 875 N.W.2d 143, 146 (2015) (emphasis added).

11.7.6.4. Reliance waivers are often found in M&A agreements.

In merger- and acquisition ("M&A") deals, reliance disclaimers are often used; as explained by a leading corporate scholar-practitioner, this is because one party, typically the seller –

… doesn't want to be deceived by the buyer into entering into an agreement (with agreed caps on liability) based on something that may or may not have been said by someone that is not written in the agreement, and of which the selling shareholders may not even be aware,

and that the buyer may determine to use post closing to make a claim not subject to the cap.

And this is particularly true for the private equity seller concerned about post closing certainty in distributing proceeds to its limited partners. Glenn D. West, Private Equity Sellers Must View "Fraud Carve-outs" with a Gimlet-Eye, Weil Insights, Weil's Global Private Equity Watch (2016) (emphasis and extra paragraphing added).

According to a 2019 American Bar Association study, summarized by an M&A lawyer:

Express non-reliance provisions are increasingly common in merger and acquisition transactions, and have tripled in prevalence over the six ABA studies since 2009. These provisions have become the majority approach, appearing in 63% of agreements in 2019.

Fraud carve-outs are increasingly seen in non-reliance provisions, showing a steady and pronounced increase since 2015—from 2% to 17% to 54%. Daniel Avery, Non-Reliance and NOR Provisions (JDSupra 2021), summarizing American Bar Association Section of Business Law, 2019 Private Target Deal Points Study (AmericanBar.org) (ABA member login required).

Delaware courts (where a high proportion of M&A-related disputes are litigated) are likely to hold parties to the terms of their non-reliance disclaimers — but as one experienced corporate practitioner has noted, "even when fraud claims premised upon extra-contractual representations have been precluded by a non-reliance clause, the express written representations can sometimes provide a basis for a claim of fraud, at least at the motion to dismiss stage." Glenn D. West, Recent Delaware Cases Illustrating How Uncapped Fraud Claims Can and Cannot Be Premised Upon Written Representations (PrivateEquity.Weil.com 2020) (emphasis added).

11.7.6.5. What if the alleged representation is contradicted by the Con­tract itself?

The Texas supreme court observed that "reliance upon an oral representation that is directly contradicted by the express, unambiguous terms of a written agreement between the parties is not justified as a matter of law." In that case:

  • An oil-well operator, negotiating a lease with the owner of a mineral interest, allegedly represented orally that the operator intended to drill on the lease and that it wasn't in the busines of "flipping" mineral interests.
  • But later the operator did indeed flip the mineral interest — so the owner sued, alleging fraudulent misrepresentation.
  • The owner had a problem: The parties' agreement gave the operator "an unqualified right to transfer the lease rather than drill. This unqualified transfer right, clearly expressed in writing and agreed to by [the owner], directly contradicts the notion that [the operator] bound itself orally not to transfer the lease and instead to drill."

The trial court granted summary judgment in favor of the operator; an appellate court reversed, but the state supreme court reversed again, reinstating the summary judgment. See Roxo Energy Co., LLC v. Baxsto, LLC, 713 S.W.3d 404 (Tex. 2025), followed in Evans Resources, LP v. Diamondback E&P, LLC, No. 11-24-00107-CV, part II.B, slip op. at 13-14 (Tex. App —Eastland Oct. 23, 2025) (affirming summary judgment in favor of operator).

11.8. Third-Party Beneficiaries Protocol

American law allows third parties to assert rights as "third-party beneficiaries" of a contract — if the signatory parties intended for that to be the case; see generally, e.g., Third-Party Beneficiary (Wikipedia.org). For that reason, it's useful to be clear about the parties intent.

11.8.1. No third-party beneficiaries unless explicitly stated.

No party intends for any other individual or organization (each, a "person") to benefit under the Con­tract except incidentally — and thus no other person is meant to have any enforceable rights under the Con­tract — unless the Con­tract expressly says so.

11.8.2. Additional notes

11.8.2.1. The difference between incidental and intended beneficiaries

"Incidental" third-party beneficiaries under a contract are different from "intended" third-party beneficiaries — the former can't expect to be able to sue successfully a signatory party for breach of the contract.

Example: In its 2016 Lubrizol opinion, the Seventh Circuit affirmed a summary judgment in favor of an additive supplier that had been sued by a distributor's end-customer — i.e., by the supplier's customer's customer. The court noted that the end-customer was not an intended third-party beneficiary of the contract between the supplier and the distributor; "[o]therwise a consumer would be a third-party beneficiary of any sales contract between a supplier of a good and a distributor of the good to the consumer." Am. Comm'l Lines, LLC v. Lubrizol Corp., 817 F.3d 548, 551 (7th Cir. 2016) (Posner, J., affirming summary judgment) (emphasis and extra paragraphing added).

11.8.2.2. Caution: Be consistent about third-party beneficiaries

Inconsistency about third-party beneficiaries can lead to litigation. Example: In the aftermath of a sale of eight hospitals, an affiliate of the seller claimed to be an intended beneficiary of an indemnity provision in the parties' contract; in 2020 the Delaware chancery court denied the buyer's motion to dismiss the indemnity claim on grounds that the contract in question was ambiguous whether the indemnity provision was negated by a disclaimer of third-party beneficiaries. See CHS/Community Health Sys., Inc. v. Steward Health Care Sys. LLC, No. 2019-0165 (Del. Ch. Aug. 21, 2020). (Hat tip: Glenn D. West.)

11.8.2.3. Some other points to consider

–  A contract might provide that third-party benefits are not assignable (15.3.6.5).

–  Third-party beneficiaries might have to arbitrate contract-related disputes if the contract contains an arbitration provision (21.1.33.18).

–  An IP licensee's contractor or supplier might be a third-party beneficiary of the license's grant of permission to use the IP in question (5.1.14).

–  A contract between "Alice" and "Bob" might require that Alice's subcontractors enter into written agreements with Alice that explicit name Bob as a third-party beneficiary (13.15.30).

12. General operations

12.1. Lighthouse General Operations Protocol [to come]

12.3. Professional Conduct Protocol

This Protocol sets out basic "professional" conduct standards that seem to be widely observed (or at least paid lip service) in the business world.

12.3.1. Professional conduct is required

Each party is to take reasonable measures, on a continuing basis, to cause that party's "staff members," defined below, to conduct themselves in a lawful, professional manner in all activities under the Con­tract.

12.3.2. What individuals are to follow this Protocol?

For purposes of this Protocol, a party's "staff members" are the following:

  1. the party's employees;
  2. others under the party's control at the time in question; and
  3. the staff members of the party's subcontractors, if any. (This Protocol doesn't address whether the Con­tract allows, or prohibits, your use of subcontractors.)
Note

For additional discussion of subcontractors, see 31.43.

12.3.3. Eahc party: Deal with any related third-party claims

  1. Each party A is to defend and indemnify each other party and each other party's Protected Group B against any claim by a third party — even if A has always taken prudent measures under § 12.3.1 — where the claim arises primarily from:
    • alleged tortious- or unlawful conduct,
    • by one or more of A's staff members,
    • in activities relating to the Con­tract.
  2. In case of doubt: In subdivision A, the term "each other party" refers to each other party to the Con­tract.

12.3.4. Professional conduct: Additional notes

12.3.4.1. Reading: Introduction: A hypothetical example

Here's a hypothetical example of when the defense- and indemnity obligations of this Protocol would come into play:

  1. Let's say that you enter into a contract with another party.
  2. Now let's say that one of the other party's employees were to engage in unprofessional conduct — for example, harassment — that adversely affects one of your employees.
  3. Subsequently, your harassed employee sues you, claiming that the other party's employee created a hostile work environment — and that you're legally liable.

This isn't an idle concern: The U.S. Equal Employment Opportunity Commission ("EEOC") has taken the position that "The employer will be liable for harassment by non-supervisory employees or non-employees over whom it has control (e.g., independent contractors or customers on the premises), if it knew, or should have known about the harassment and failed to take prompt and appropriate corrective action." See also, e.g., EEOC v. Skanska USA Bldg., Inc., No. 12-5967, slip op. at part II.A (6th Cir. Dec. 10, 2013) (reversing summary judgment; general contractor that in fact controlled subcontractor's employees could be liable for race-based hostile work environment created by employees) (unpublished).

(At this writing, in February 2025, the above-cited EEOC Web page states that "The information on this webpage is being reviewed for compliance with the law and [Trump] executive orders and will be revised." [Emphasis added.])

In that situation, this Protocol requires the other party to defend and indemnify you against the claim by your employee.

And the same would be true if you were being sued by an unrelated third party, and not by one of your own employees, for conduct by the other party's employee. That's a potential concern because the third party's lawyers might be very "creative" about legal theories with which to try to drag you into the litigation in the hope of getting you to pay some money to go away (i.e., to settle out).

12.3.4.2. Why bother with this Protocol?

The express defense reference in this Protocol has some business significance: Suppose (for example) that:

  • one of the other party's employees allegedly broke the law as part of the Con­tract, in a manner for which the other party was responsible under, say, the doctrine of respondeat superior; and
  • as a result, a third party made a claim — civil, or criminal — against you.

If the other party didn't have an express defense obligation, such as that of this Protocol, then you'd likely have to "front" your own legal expenses, even though the other party's noncompliance with the law might constitute a breach of the Con­tract if the Con­tract required compliance. 23

12.3.4.3. What might "professional" behavior look like?

A party's professional-conduct obligation would typically include the following (as examples):

  • When on-site at another party's physical- or virtual site: Following such reasonable rules and policies as the other party timely communicates;
  • Following prudent safety practices;
  • Complying with reasonable standards of personal conduct;
  • Complying with applicable law.

Professional behavior would also normally include following Protocol 9.13 (site visits) and Protocol 9.4 (computer-system access) when engaged in activities covered by those provisions.

12.3.4.4. What would be unprofessional behavior?

Unprofessional behavior would typically include, for example, one or more of the following:

  • criminal behavior;
  • denying access to a job site for a reason prohibited by applicable law (for example, on grounds of race, etc.);
  • otherwise discriminating against someone for any reason prohibited by applicable law; and/or
  • other unlawful conduct against someone — this could take the form of, for example, sexual harassment; other tortious conduct; and/or other conduct prohibited by law.
12.3.4.5. Get more specific about which laws?

Some drafters might want to provide a list of particular law(s) that must be complied with. Here are a few examples of categories (listed alphabetically):

12.3.4.6. Oh, and: Try to avoid getting in each other's way

Just as a matter of professional courtesy (and productive business dealings), parties should make reasonable efforts to avoid interfering with each other at any site where both parties' personnel are present — but that's not included in this Protocol in the interest of (trying for) brevity.

13. Sales

13.1. Most-favored customer (notes only)

Most-favored-customer clauses aren't really susceptible to standardized rules, so we won't try here (at least for now).

13.1.1. Examples of most-favored-customer language

Section 12 of a Honeywell purchase order terms-and-conditions document, archived at https://perma.cc/CUV6-NKTY, sets forth a fairly-typical most-favored-customer clause ("MFC") clause and price-reduction clause ("PRC").

12. Price: Most Favored Customer and Meet or Release

[a] Supplier warrants that

  • the prices charged
  • for the Goods delivered under this Purchase Order
  • are the lowest prices charged by Supplier
  • to any of its external customers
  • for similar volumes of similar [sic] Goods.

[b] If Supplier charges any external customer a lower price for a similar volume of similar Goods, Supplier must

  • notify Honeywell
  • and apply that price to all Goods ordered under this Purchase Order.

[Comment: The above language doesn't limit the price-reduction obligation to goods ordered in the future. Conceivably, Honeywell could try to argue that the obligation applied retroactively as well, requiring refunds for past orders — a court, though, might interpret the language as limited to future orders, under the contra proferentem principle discussed at § 11.4.]

[c] If at any time before full performance of this Purchase Order

  • Honeywell notifies Supplier in writing
  • that Honeywell has received a written offer from another supplier
  • for Goods similar [sic] to those to be provided under this Purchase Order
  • at a price lower than the price set forth in this Purchase Order,
  • Supplier must immediately meet the lower price for any undelivered Goods.

If Supplier fails to meet the lower price Honeywell, at its option, may terminate the balance of the Purchase Order without liability.

(Extra paragraphing, bullets, and bracketed text added.)

In a Notre Dame Law Review article, two Skadden Arps lawyers offer other examples of MFC language:

–  "Contractor warrants that the price(s) are not less favorable than those extended to any other customer (whether government or commercial) for the same or similar articles or services in similar quantities."

–  "The Contractor certifies that the prices, warranties, conditions, benefits and terms are at least equal to or more favorable than the prices, warranties, conditions, benefits and terms quoted by the Contractor to any customers for the same or a substantially similar quantity and type of service."

–  "The Contractor warrants that prices of materials, equipment and services set forth herein do not exceed those changed by the Contractor to any other customer purchasing the same goods or services under similar conditions and in like or similar quantities."

Mitchell S. Ettinger and James C. Altman, Compliance with Most Favored Customer Clauses: Giving Meaning to Ambiguous Terms While Avoiding False Claims Act Allegations, 90 Notre Dame L. Rev. Online 1, 4-5 (2015) (emphasis added).

13.1.2. Dangers of a most-favored-customer clause for suppliers

For a supplier, a most-favored-customer clause and price-reduction clause in a customer contract can be both dangerous and a major compliance burden. For example, the software giant Oracle Corporation once paid just shy of $200 million to settle a U.S. Government lawsuit — sparked by a whistleblower claim — that Oracle had overbilled the Government by knowingly charging federal customers more than allowed by an MFC clause in Oracle's federal-government contract over some eight years, according to a Department of Justice press release. See the following: • U.S. Department of Justice press release, Oracle Agrees to Pay U.S. $199.5 Million to Resolve False Claims Act Lawsuit - Largest False Claims Act Settlement Obtained by General Services Administration (Justice.gov Oct. 6, 2011) (extra paragraphing added) • Andrew Harris and David Voreacos, Oracle Settles U.S. Agency Overbilling Case for $199.5 Million (Bloomberg.com Oct. 6, 2011) (paywalled), which says in part: "The U.S. …. claimed Oracle gave companies discounts of as much as 92 percent, while the government’s cuts ranged from 25 to 40 percent." ]

(The Oracle-employee whistleblower who reported the breach to the government collected $40 million, according to the DOJ press release.)

The case also attracted class-action plaintiffs, who sued Oracle and the members of its board directors. Various class-action lawsuits were consolidated in the Northern District of California; the cases were apparently settled on terms requiring that Oracle adopt some corporate-governance measures and pay $1.9 million in attorney fees. See Jessica Dye, Oracle investor sues over $200 million settlement (Reuters.com 2012).; Stipulation of Settlement, In re Oracle Corp. Deriv. Litigation, No. C-11-04493-RS (May 28, 2013). (I've not been able to confirm positively that the stipulation of settlement was approved by the court.).

In another case (in which my then-law firm was involved, although I wasn't), semiconductor chip maker Texas Instruments settled its patent-infringement lawsuit with Samsung in part because Samsung discovered that Texas Instruments had breached a most-favored-licensee provision in a previous patent-license agreement between the two companies — according to Samsung, when the parties had negotiated the previous license agreement, TI had fraudulently told Samsung that Samsung was getting as good a deal as any other TI licensee for the relevant patent, when apparently that proved not to be the case. See Evan Ramstad, Texas Instruments Reaches Agreement With Samsung (WSJ.com Nov. 27, 1996), archived (behind paywall) at https://perma.cc/PAC5-9VNU; David Beck, The Trial Lawyer: What it Takes to Win at 235-36 (American Bar Association 2006), excerpt at https://goo.gl/ad33DQ.

Both the danger and the compliance burden arise from the fact that business people doing transactions with other customers often won't remember that they must comply with the MFC and PRC clauses in the earlier customer contract.

And if the business people do remember the MFC and PRC clauses, they might choose to ignore it, to roll the dice that they won't get caught.

Violating the MFC clause in a U.S. Government contract (a "GSA schedule") can lead to severe consequences, possibly including "government claims, prosecution under the False Claims Act (FCA), terminations for cause and suspensions and debarments to name a few." See Most Favored Customer Clause (GovContractAssoc.com, undated).

13.1.3. Who really is pushing for the MFC clause?

When a supplier is asked for an MFC commitment, it helps to try to identify the specific "constituency" within the customer's organization that is asking for the commitment. It could be that it's only the procurement- or sourcing people — who often are are charged with squeezing suppliers — are reflexively pushing for an MFC commitment as an "insurance policy" to help protect their own jobs, whereas the actual business customer is fine with the pricing that the supplier has quoted.

13.1.4. Dealing with customer MFC requests

When a customer asks a supplier for an MFC commitment, the supplier can try to limit the commitment. For example:

–  Try to limit the MFC commitment to pricing currently offered to other customers, without a "lookback" to prior sales — be very clear that the MFC commitment is going-forward only, not retroactive. Example: In a Texas case, the owner of a patent for check-processing technology had to refund $69 million to its licensee JPMorgan Chase because, the court found, the license agreement's most-favored-licensee provision was retroactive. See JP Morgan [sic] Chase Bank, N.A. v. DataTreasury Corp., 823 F.3d 1006 (5th Cir. 2016) (affirming district-court judgment).

–  Put a time limit on the MFC commitment, so that the commitment expires in, say, three months.

–  Add on-going performance prerequisites — for example, if the customer fails to make stated minimum purchases per quarter [or whatever], then the MFC and PRC provisions will go away (that is, cease to be effective).

–  Try to avoid a future price-reduction obligation of the kind seen in paragraph [b] of the Honeywell language quoted above.

–  Include limiting qualifiers for "same" and "similar" products and services.

–  Limit the universe of other customers that are used for comparison — as an (absurd) illlustrative example, an MFC clause could say something like, "This is the best pricing we're offering today to companies headquartered in Montana whose corporate names begin with the letter 'Y.'" (This brings to mind a line from a Kingston Trio concert album that I listened to as a teenager: "We'd like to introduce one of the finest bass players on stage at this time.")

–  Don't obligate the supplier's affiliates to the MFC commitment — Sean Hogle, moderator of the redline.net online forum for lawyers, notes: "[M]ake sure the clause doesn't rope in affiliates (ie, 'Vendor and its affiliates warrant that the prices charged hereunder are as or more favorable ….'). Capturing affiliates in the MFN [most-favored nation] clause is problematic in the M&A context, as any potential acquiror (and its affiliates) could become subject to the clause upon closing of the acquisition, depending on the structure of the deal." See redline.net posting of Oct. 12, 2019 ]

A U.S. Government manual for contracting officers (purchasers) sets out some factors that suppliers can use to try to limit an MFC clause:

(e) When establishing negotiation objectives and determining price reasonableness, compare the terms and conditions of the … solicitation with the terms and conditions of agreements with the offeror’s commercial customers.

When determining the Government’s price negotiation objectives, consider the following factors:

(1) Aggregate volume of anticipated purchases.

(2) The purchase of a minimum quantity or a pattern of historic purchases.

(3) Prices taking into consideration any combination of discounts and concessions offered to commercial customers.

(4) Length of the contract period.

(5) Warranties, training, and/or maintenance included in the purchase price or provided at additional cost to the product prices

(6) Ordering and delivery practices.

(7) Any other relevant information, including differences between the … solicitation and commercial terms and conditions that may warrant differentials between the offer and the discounts offered to the most favored commercial customer(s).

For example, an offeror may incur more expense selling to the Government than to the customer who receives the offeror’s best price,

or the customer (e.g., dealer, distributor, original equipment manufacturer, other reseller) who receives the best price may perform certain value-added functions for the offeror that the Government does not perform.

In such cases, some reduction in the discount given to the Government may be appropriate.

If the best price is not offered to the Government, you should ask the offeror to identify and explain the reason for any differences.

Do not require offerors to provide detailed cost breakdowns. General Services Acquisition Manual § 538.270 (acquisition.gov) (emphasis and extra paragraphing added).

–  Develop a protocol for cross-checking pending transactions against MFC requirements; train relevant personnel to use the protocol. (This could be a pain for the business people, though.) See Ettinger and Altman, supra, at 11; see also id. at part III (other suggestions for dealing with customer requests for MFC clauses).

13.1.5. Additional reading about MFC clauses (optional)

Students: These links are provided for convenient future reference; you don't need to read the linked items.

See generally:

13.2. Price fixing (notes)

13.2.1. Resale price maintenance is (now) judged by a rule of reason

From the Federal Trade Commission:

Reasonable price, territory, and customer restrictions on dealers are legal.

Manufacturer-imposed requirements can benefit consumers by increasing competition among different brands (interbrand competition) even while reducing competition among dealers in the same brand (intrabrand competition).

  • For instance, an agreement between a manufacturer and dealer to set maximum (or "ceiling") prices prevents dealers from charging a non-competitive price.
  • Or an agreement to set minimum (or "floor") prices or to limit territories may encourage dealers to provide a level of service that the manufacturer wants to offer to consumers when they buy the product.

These benefits must be weighed against any reduction in competition from the restrictions.

Until recently, courts treated minimum resale price policies differently from those setting maximum resale prices. But in 2007, the Supreme Court determined that all manufacturer-imposed vertical price programs should be evaluated using a rule of reason approach.

According to the Court, "Absent vertical price restraints, the retail services that enhance interbrand competition might be underprovided. This is because discounting retailers can free ride on retailers who furnish services and then capture some of the increased demand those services generate."

Note that this change is in federal standards; some state antitrust laws and international authorities view minimum price rules as illegal, per se. United States Federal Trade Commission, Manufacturer-imposed Requirements (FTC.gov, undated) (formatting edited for improved readability).

But: In a famous Justice Department lawsuit against tech-giant Apple and a slew of legacy book-publishing houses, the Second Circuit held (over a dissent) that "to insist that the vertical organizer [i.e., Apple] of a /horizontal price-fixing conspiracy may escape application of the per se rule[] … is based on a misreading of Supreme Court precedent, which establishes precisely the opposite."

13.2.2. Price fixing by competitors can lead to prison time

In the United States, "horizontal" price-fixing among competitors is per se illegal under section 1 of the Sherman Act and can call down the wrath of government prosecutors and plaintiffs' lawyers.

Corporate executives have gone to prison for price-fixing. Example: The former chief executive officer of Bumble Bee Foods was sentenced to more than four years in prison and a $100,000 criminal fine for his leadership role in a three-year antitrust conspiracy to fix prices of canned tuna; the company pleaded guilty and was sentenced to a $25 million fine — and co-conspirator StarKist was sentenced to the statutory maximum $100 million fine. See Press Release, United States Department of Justice, Former Bumble Bee CEO Sentenced To Prison For Fixing Prices Of Canned Tuna (June 16, 2020).

According to the New York Times, the tuna price-fixing scheme came to light when a food wholesaler in New York noticed that prices for canned tuna were staying the same even though the price of raw tuna were dropping; this led to lawsuits by the wholesaler and by grocers such as Walmart, Target, and Kroger. See Sandra E. Garcia, Former Bumble Bee C.E.O. Is Sentenced in Tuna Price-Fixing Scheme, New York Times, June 16, 2020 ]

What kinds of inter-company dealings can be deemed "price fixing"? The U.S. Federal Trade Commission explains:

Price fixing is an agreement (written, verbal, or inferred from conduct) among competitors that raises, lowers, or stabilizes prices or competitive terms.

Generally, the antitrust laws require that each company establish prices and other terms on its own, without agreeing with a competitor. When consumers make choices about what products and services to buy, they expect that the price has been determined freely on the basis of supply and demand, not by an agreement among competitors.

When competitors agree to restrict competition, the result is often higher prices. Accordingly, price fixing is a major concern of government antitrust enforcement.

A plain agreement among competitors to fix prices is almost always illegal, whether prices are fixed at a minimum, maximum, or within some range.

Illegal price fixing occurs whenever two or more competitors agree to take actions that have the effect of raising, lowering or stabilizing the price of any product or service without any legitimate justification.

Price-fixing schemes are often worked out in secret and can be hard to uncover, but an agreement can be discovered from "circumstantial" evidence.

  • For example, if direct competitors have a pattern of unexplained identical contract terms or price behavior together with other factors (such as the lack of legitimate business explanation), unlawful price fixing may be the reason.
  • Invitations to coordinate prices also can raise concerns, as when one competitor announces publicly that it is willing to end a price war if its rival is willing to do the same, and the terms are so specific that competitors may view this as an offer to set prices jointly.

Not all price similarities, or price changes that occur at the same time, are the result of price fixing. On the contrary, they often result from normal market conditions.

  • For example, prices of commodities such as wheat are often identical because the products are virtually identical, and the prices that farmers charge all rise and fall together without any agreement among them.
  • If a drought causes the supply of wheat to decline, the price to all affected farmers will increase.
  • An increase in consumer demand can also cause uniformly high prices for a product in limited supply.

Price fixing relates not only to prices, but also to other terms that affect prices to consumers, such as shipping fees, warranties, discount programs, or financing rates. … United States Federal Trade Commission, Price Fixing (accessed June 21, 2020) (formatting altered).

13.3. Requirements contracts (notes)

The following discussion draws heavily from a Michigan supreme court opinion, in a requirements-contract case involving an automotive-parts supplier. I've used a free hand in editing the text and have omitted most citations. No copyright is claimed in the text of the court's opinion. See MSSC, Inc. v. Airboss Flexible Products Co., 999 N.W.2d 335, 338-41 (Mich. 2023) (Statute of Frauds requires quantity to be ascertainable). The supreme court repeatedly cited, among other sources, Jason Killips, Section 2-201 Isn't Optional: Option Provisions, Requirements Contracts, and Cadillac Rubber, 41 Mich. Bus. L. J. 46 (2021). See also Higuchi Int'l Corp. v. Autoliv ASP, Inc., 103 F.4th 400 (6th Cir. 2024) (citing Airboss in reversing preliminary injunction requiring supplier to continue selling automotive parts at original prices: parties' writings did not establish an enforceable requirements contract).

Under Michigan law, contracts for the sale of goods—including supplier contracts—are governed by the Uniform Commercial Code (the UCC).

The UCC contains a statute-of-frauds provision that governs which agreements must be in writing. That section provides:

Except as otherwise provided in this section, a contract for the sale of goods for the price of $1,000.00 or more is not enforceable by way of action or defense unless there is a writing sufficient to indicate that a contract for sale has been made between the parties and signed by the party against whom enforcement is sought or by his or her authorized agent or broker.

A writing is not insufficient because it omits or incorrectly states a term agreed upon[,]

but the contract is not enforceable under this subsection beyond the quantity of goods shown in the writing. Mich. Comp. L. § 440.2201(1) (emphasis and extra paragraphing added). Note: In Texas, the price trigger for the statute of frauds is $500, not $1,000 as in Michigan.

The second sentence allows for some terms to be missing or incorrect but provides that a court can only enforce the contract up to the quantity set forth in writing — in other words, quantity is the only essential term required by the statute of frauds.

If an agreement for the sale of goods contains a quantity, then the agreement satisfies the statute of frauds.

  • When a contract fails to include a quantity term, parol evidence—that is, evidence outside the contract itself cannot be offered to supply a missing quantity term.
  • In contrast, when a contract provides a quantity term but fails to express details sufficient to determine the specific or total quantity, it may be explained or supplemented by parol evidence.

The UCC allows for a contract's quantity to be measured "by the output of the seller or the requirements of the buyer…." This provision allows for parties to enter into contracts that provide a quantity term but lack specificity as to the total of goods agreed upon. MCL 440.2306(1).

Two types of contracts fall under this provision: Output contracts and requirements contracts. Both are commonly used between suppliers. Today we formally recognize a third type of contract: a release-by-release contract.

  • An "output contract" defines quantity by the supply provided by the seller.
  • In contrast, a "requirements contract" is a contract that defines quantity by reference to the buyer's requirements.

In agreements between a buyer and supplier-seller, requirements contracts are often created by an umbrella agreement, which is also referred to as a "blanket purchase order." This umbrella agreement sets forth the terms governing items such as price, length of the contract, warranty details, indemnification, and termination.

[A federal district court opinion] describes a Tier-1 supplier's supply agreement which set forth the terms and conditions for all purchase orders of a particular part or program during the life of the agreement and against which the buyer issued four purchase orders.

Notably, a blanket purchase order itself doesn't require the seller actually to manufacture or ship: That obligation arises when the buyer issues a document referred to as a shipment‑, production‑, or release order against the blanket purchase order.

Most importantly, in a requirements contract, the terms of the blanket purchase order also dictate that the buyer will obtain a set share of its total need from the seller — such as "all requirements of the buyer"). This phrase satisfies the quantity term required by the statute of frauds.

To supplement this general term, the buyer will typically later issue "releases" to let the seller know its specific short-term requirements.

Finally, similar to requirements contracts, some agreements are governed by a blanket purchase order that sets the overall contract terms, and the buyer issues subsequent releases that set forth the specific quantity the buyer needs.

But:

  • Unlike a requirements contract, the blanket purchase order doesn't set forth the share of the buyer's need to be purchased from the supplier.
  • Instead, the purchase order is more appropriately thought of as an umbrella agreement that governs the terms of future contract offers: Although the seller isn't bound to accept future orders in the same manner as with a requirements contract, the seller is bound by the terms agreed to in the purchase order when future releases are issued and accepted.

These agreements are also known as "release-by-release" contracts. Such contracts are structured so that their overarching terms are enforceable only once a firm quantity is stated — and that happens only when a release is issued and accepted.

The key difference between a requirements contract and a release-by-release contract rests in the level of mutual obligation between the parties and the risk each party bears.

  • A requirements contract assures the seller that the buyer will be a customer for the length of the contract, but the seller cannot reject future orders for the length of the contract.
  • In contrast, under a release-by-release contract, the parties' contractual obligations can expire in short order if the buyer doesn't issue a new release or the seller doesn't accept a release.

So: The seller isn't guaranteed future business from the buyer, but on the other hand the buyer won't know in advance whether the seller will accept a future order or instead will reject it.

13.4. Round-trip sales transactions (notes)

Round-trip sales transactions are those in which, in essence, one company says to another, You'll buy my stuff, but I'll buy enough of yours to cover your cost. (It's sometimes referred to as "buying revenue.") This type of deal can be a species of securities fraud, and can get companies and individuals sued by the SEC and/or by securities plaintiffs and even imprisoned.

Example: The SEC explained the basics of round-trip transactions in a press release charging Time Warner (then AOL, a.k.a. America OnLine) with the practice, a charge that eventually cost Time Warner nearly $3 billion (extra paragraphing has been added for readability):

[AOL] effectively funded its own online advertising revenue by giving the counterparties the means to pay for advertising that they would not otherwise have purchased.

To conceal the true nature of the transactions, the company typically structured and documented round-trips as if they were two or more separate, bona fide transactions, conducted at arm's length and reflecting each party's independent business purpose.

The company delivered mostly untargeted, less desirable, remnant online advertising to the round-trip advertisers, and the round-trip advertisers often had little or no ability to control the quantity, quality, and sometimes even the content of the online advertising they received.

Because the round-trip customers effectively were paying for the online advertising with the company's funds, the customers seldom, if ever, complained.

AOL / Time Warner almost immediately settled with the SEC for $300 million.

Even that wasn't the end of Time Warner's troubles: The company later settled a related class-action lawsuit for $2.65 billion.

In a different case, the FBI announced:

The former chief executive officer and chairman of the board of Homestore.com was sentenced this afternoon to 4½ years in federal prison for presiding over a scheme to commit securities fraud by artificially inflating the publicly traded company’s advertising revenue to appear to be more profitable to Wall Street analysts.

* * *

[The CEO] pleaded guilty in January to one count of conspiracy to commit securities fraud through fraudulent, “round-trip” transactions that were designed to artificially inflate Homestore’s revenue ….

In the round-trip deals, Homestore paid millions of dollars to vendors for products and services that Homestore did not need or never used. The sole reason for paying the vendors was to start a circular flow of funds that would improperly return to Homestore as revenue. …

(Emphasis and extra paragraphing added.)

See also a discussion of key red flags in round-tripping strategies.

More recently, Nvidia "regularly makes equity investments in AI startups that are also its customers. Like the mythical ouroboros, the snake that eats itself, the AI economy turns equity investments from Nvidia and other companies into purchases of their own products, effectively self-funding their own record revenues. So what happens when this recirculation can’t cover for the lack of massive amounts of available cash for the planned AI buildout?" Bryan McMahon, The AI Ouroboros (Prospect.org Oct. 15, 2025).

13.5. Merchants under the UCC: A buyer can be one too

In some situations it can matter whether a party is considered a "merchant." As used in U.S. commercial law, the term merchant generally includes not only regular sellers of particular types of goods, but also buyers who regularly acquire such goods.

The Uniform Commercial Code states as follows in UCC § 2-104(1):

“Merchant” means a person [i] who[:] deals in [i.e., not just sells] goods of the kind or [B] otherwise by his occupation holds himself out as having knowledge or skill peculiar to the practices or goods involved in the transaction or [ii] to whom such knowledge or skill may be attributed by his employment of an agent or broker or other intermediary who by his occupation holds himself out as having such knowledge or skill.

(Emphasis and bracketed text added.)

To like effect is UCC § 2-205, which refers to "[a]n offer by a merchant to buy or sell goods …."

Federal judge Richard Posner once explained the use of the term merchant as being different than common parlance:

Although in ordinary language a manufacturer is not a merchant, “between merchants” is a term of art in the Uniform Commercial Code. It means between commercially sophisticated parties …. Wisconsin Knife Works v. Nat’l Metal Crafters, 781 F.2d 1280, 1284 (7th Cir. 1986) (Posner, J.) (citations omitted).

And still again is the UCC definition's commentary, apparently reproduced in Nebraska Uniform Commercial Code § 2-104.

Other cases and commentators have reached the same conclusion.

Note

Both sellers and buyers can be merchants: See, for example, the following: Brooks Peanut Co. v. Great Southern Peanut, LLC, 746 S.E.2d 272, 277 n.4 (Ga. App. 2013) (citing another case that cited cases); Sacramento Regional Transit v. Grumman Flxible [sic], 158 Cal. App.3d 289, 294-95, 204 Cal. Rptr. 736 (1984) (affirming demurrer), in which the court held that a city’s transit district, which had bought buses from a manufacturer, was a merchant within the meaning of § 2-104; Douglas K. Newell, The Merchant of Article 2, 7 Val. U. L. Rev. 307, 317, part III (1973).

13.6. Incoterms (notes)

13.6.1. A very-useful drafting tool in sales of goods

Contract drafters can (and often should) use the INCOTERMS 2020 three-letter options to instantly specify things such as responsibility for freight charges, insurance, and export- and customs clearance, in addition to passage of title (that is, ownership) and risk of loss.

For example, a customer's purchase-order form might say:

Shipping, etc.: DDP (Incoterms 2020).

Or: A supplier's terms of sale might say:

Shipping, etc.: EXW (Incoterms 2020).

13.6.2. The three-letter codes serve as negotiation shorthand

What do these three-letter codes mean? At either extreme:

  • EXW (Ex Works) means, in essence, that the supplier will make the goods available for pickup at the supplier's place of business, but everything from that point on is the customer's job.
  • DDP (Delivered Duty Paid) is the other extreme: The supplier will deliver the goods to the customer's place of business with all formalities taken care of and all charges paid.

In between are a number of other options for transferring title and risk of loss, such as:

  • FCA: Free Carrier (named place of delivery)
  • CPT: Carriage Paid To (named place of destination)
  • CIP: Carriage and Insurance Paid to (named place of destination)
  • DPU: Delivered At Place Unloaded (named place of destination)
  • DAP: Delivered At Place (named place of destination)

and others.

The Australian global logistics firm Henning Harders provides a useful graphic depiction of how risk of loss shifts under the various INCOTERMS options.

13.6.3. Risk of loss shifting can be quickly specified

Photo: Gaetan Lee - Creative Commons BY 2.0.

When goods are transported, it could be important to nail down the precise time at which risk of loss of the goods shifts from one party to another. Here's a not-so-hypothetical example:

  • "Supplier," in Asia, ships thousands of rubber ducks to "Customer" in, say, California.
  • The ducks are all packed in a standard 40-foot shipping container, as called for by the contract.
  • The shipping container is transported first by truck; then by rail; then by sea; and finally again by truck to Customer's location in California.

True, title will pass at some point in the journey; when that happens, Customer, not Supplier, will now own the rubber ducks (and thus typically can direct what is to be done with them).

But importantly, risk of loss will also pass at some point in the journey — quite possibly at different point. The INCOTERMS three-letter abbreviations (see 13.6, plus 13.8.8) contain succinct terms for when risk of loss will pass from a seller to a customer.

Let's see how risk of loss might play out. Suppose that, for our shipment of rubber ducks:

  • During the sea voyage a storm causes the shipping container to be washed overboard and to break open, sending the ducks floating away in different directions.
  • If risk of loss had passed to Customer before that time, then Supplier would have no responsibility for replacing the rubber ducks.
  • Insurance (see 31.21) can — for a price — mitigate such risks; the parties' choice of INCOTERMS rule will establish who has responsibility for obtaining and paying for insurance.

Why is this a not-so-hypothetical example? Because in basically this way, thousands of plastic yellow "rubber ducks," red beavers, blue turtles, and green frogs were once lost at sea during a Pacific Ocean storm. (Some of the toys eventually drifted thousands of miles — with the silver-lining benefit that the loss of the toys made possible some significant oceanographic research by tracking where the toys eventually washed ashore.) See Friendly Floatees (Wikipedia.org). ]

13.6.4. Choose INCOTERMS wisely: Excise taxes, etc. can be non-trivial

Who must pay excise taxes and similar import duties can be a non-trivial issue, so choosing the right INCOTERMS rule can be important. Example: In Texas Truck Parts (5th Cir. 2024):

  • A Houston wholesaler had paid (under protest) some $1.9 million in excise tax on truck tires that the wholesaler had bought from Chinese manufacturers.
  • The wholesaler sought a refund of the excise tax, claiming that under U.S. tax law, the Chinese manufacturers were the "importers" of the tires and therefore were responsible for paying the tax.

It didn't work: The court held that on the facts, the wholesaler was the beneficial owner — and thus the "importer" — of the tires, and so the wholesaler was responsible for paying the excise tax. See Texas Truck Parts & Tire, Inc. v. United States, 118 F.4th 687 (5th Cir. 2024) (reversing summary judgment).

13.7. Commissions (on sales) (rough notes)

13.7.1. The "procuring cause doctrine" for commission eligibility

As explained by the state's supreme court, Texas law applies a fairly-simple rule to commission payments if the parties' contract doesn't specify otherwise:

When a seller agrees to pay sales commissions to a broker (or other agent), the parties are free to condition the obligation to pay commissions however they like.

But if their contract says nothing more than that commissions will be paid for sales, Texas contract law applies a default rule called the "procuring-cause doctrine." Under that rule, the broker is entitled to a commission when a purchaser was produced through the broker’s efforts, ready, able and willing to buy the property upon the contracted terms. Perthuis v. Baylor Miraca Genetics Labs., LLC, 645 S.W.3d 228, 231 (Tex. 2022) (reversing court of appeals and reinstating judgment on jury verdict awarding unpaid commissions to terminated sales executive; procuring-cause rule applied even though executive's employment was "at will") (formatting modified). See also 18.2 (at-will relationships).

A dissenting opinion argued that:

The Court’s adoption of this default rule [the "procuring-cause doctrine"] threatens the expectations of at-will employers and employees who have agreed to a commission structure but, for whatever reason, failed to reduce it to writing with perfect clarity.

They will be surprised to learn that, under the default rule the Court adopts today, an at-will salesperson is entitled to commissions for any sale—here, perhaps hundreds or thousands of sales—a jury determines the salesperson “set in motion.”

And they will be stunned to learn that, under the default rule, the entitlement to commissions may extend years after their employment relationship ended. Id. at 244-45 (Huddle, J., dissenting) (extra paragraphing added, emphasis in original).

13.7.2. But: The contract can override the procuring-cause doctrine

Example: A equipment-rental company, which wanted to sell itself, signed an engagement letter with a business broker.

  • The engagement letter specifically stated that the company would owe the broker a commission if the company completed a sale transaction within an 18-month "tail period" after any termination of the engagement.
  • Due to the COVID-19 pandemic, the rental company put its sale efforts on hold and terminated the engagement letter.
  • A year later, the rental company re-engaged with a prospective buyer, which had previously declined to buy.
  • This time, the prospect agreed to buy. The sale was closed 15 months after termination of the broker's engagement — i.e., during the 18-month tail period.

The broker sued the rental company for its commission; affirming summary judgment in favor of the broker, the court held that:

  • Under Texas supreme court precedent, the specific 18-month tail period in the engagement letter overrode the procuring-cause doctrine under state law, which provided only a "default" (i.e., a gap-filler provision).
  • Consequently, said the court, the rental company did indeed owe a commission to the broker — even though the broker had not been involved with the sale transaction. Catalyst Strategic Advisors, L.L.C. v. Three Diamond Capital SBC, L.L.C., 93 F.4th 870 (5th Cir. 2024) (affirming summary judgment).

Drafting tip: When putting together a written commission plan, consider using one or more roadblock clauses to make it abundantly clear when commissions are or are not owed.

13.8. Order Fulfillment Protocol

This Protocol addresses delivery issues that are typically covered in "the fine print" of customers' purchase-order forms and — often in very different ways See the remarkably different terms and conditions proffered by Honeywell when it is a buyer, at https://perma.cc/CUV6-NKTY, versus Honeywell's terms when it is a vendor, at https://perma.cc/5MB9-H6VK.] — in vendors' terms of sale.

13.8.1. Parties: Customer and Vendor.

  1. This Protocol will apply whenever, under the Con­tract, specified parties — referred to as the "Customer" and "Vendor" respectively — agree to conduct one or more transactions such as, for example,
    1. one or more sales or other deliveries of tangible- or nontangible goods, equipment, or other deliverables; and/or
    2. the performance of services.
  2. Each such transaction agreement is referred to as an "Order."
Note

This Protocol is worded to take into account that the Customer might not be an end-customer of the Vendor, but instead could be a reseller, a distributor, etc. (The parties could address that possibility in the Con­tract.)

13.8.2. Packaging and labeling

  1. The Vendor must cause deliverables to be appropriately packaged and labeled for shipment and delivery — this includes, without limitation, compliance with:
    1. any requirements of law (including for example any required country-of-origin labeling); and
    2. any specific packaging- and/or labeling instructions in the Order.
  2. If the Customer provides the Vendor with a purchase-order number or other identifier for the Order, THEN: The Vendor must have that identifier included on shipping labels, shipping documents, and Order-related correspondence.
Note

().  Background: Anyone who has ever bought prepackaged food at a U.S. grocery store will know that packaging and labeling of goods can be a non-trivial affair, often regulated by government authorities.

In some circumstances, the Vendor might want to consult with the Customer about packaging and labeling.

13.8.3. Agreed delivery times are somewhat flexible.

  1. The Vendor must have the deliverables delivered in the time frame stated in the Order (if any).
  2. If an Order states a specific delivery time, THEN: The Vendor will not be liable if the actual delivery time is early or late, as long as:
    1. the early-or-late variation is not unreasonable under the circumstances, and
    2. the Order does not clearly state otherwise — for example, by stating that "time is of the essence."
Note

().  This is phrased to account for the fact that in many cases, the Vendor might use a third-party carrier to actually make the delivery. Possible override: "The Vendor will endeavor to cause delivery …." (Leave out the italics, usually.)

Subdivision 2: If the Customer wants to insist that delivery timing is critical — as in, for example, "just in time" manufacturing — then the Order can say so. ¶ See generally the commentary on "time is of the essence" at 25.3.8.

13.8.4. Partial deliveries are OK unless otherwise specified.

The Vendor is free to make multiple, partial deliveries unless the Order clearly specifies otherwise.

Note

().  Background: The Vendor might prefer to be free to ship ordered goods as they're finished, without waiting for the entire order to be completed.

On the other hand, the Customer might want its deliveries to be all-or-nothing, so that Customer's people won't have to spend extra time dealing with partial deliveries.

13.8.5. Substituted deliverables are OK — within limits.

  1. The Vendor is free to substitute equivalent deliverables, but only as stated in this section.
  2. The Vendor will not provide substitute deliverables unless the substituted deliverables:
    1. would be accepted in the trade as legitimately equivalent to the ordered deliverables; and
    2. meet all functional specifications stated in the Order (if any).
  3. The Vendor must advise the Customer of any substitutions, in writing and at a reasonable time. (That normally means no later than the scheduled time for delivery, if there is a scheduled time.)
Note

Possible override: "The Vendor may not substitute different deliverables for those specified in an Order without the Customer's prior written consent."

13.8.6. The Customer may reject substituted deliverables (for a time).

  1. Unless the Customer has agreed in writing to a substitution of deliverables, the Customer is free to reject substituted deliverables, as long as:
    1. the Customer does so within the time stated in subdivision B; and
    2. the Customer's conduct indicates acceptance of the substituted deliverables.
  2. If the Customer does not reject substituted deliverables on or before the date 14 days after the date of delivery, THEN: The Customer will be deemed to have accepted the substituted deliverables in lieu of the originally-agreed deliverables.
Note

().  Background: Giving the Customer a (time-limited) right to reject "surprise" substituted goods will give the Vendor an incentive to get Customer's sign-off before shipping such goods.

The Uniform Commercial Code's § 2-613 addresses substituted goods only in the context of a "casualty" to goods identified when the contract is made.

13.8.7. The Customer may redirect delivery — within limits.

  1. The Customer is free to direct the Vendor to divert a delivery of goods to a third party — even after the Vendor has shipped the ordered goods — but only as stated in this section.
  2. The Vendor is free to decline to redirect the delivery if the Vendor has reasonable grounds to object to the redirection.
  3. If the Vendor asks the Customer within a reasonable time, THEN: The Customer must pay, or reimburse the Vendor for, any additional expenses that the Vendor incurs that were reasonably associated with a redirected delivery under this § 13.8.7.
Note

().  The Vendor might have a reasonable basis for objecting to delivering to a specified third party; for example: (1) the shipment might already be on its way and not divertable; (2) the third party might be in a location — or be — subject to export-controls restrictions (see 31.9); (3) the deliverables might be unlawful at the proposed new delivery address, for example, alcoholic beverages or drugs at a location where such goods were illegal.

Subdivision 3: The Vendor's additional out-of-pocket expenses could include, for example, shipping charges; insurance premiums; outside-counsel legal fees for special cases; etc. ¶ The Vendor might reasonably want the Customer to pay up-front the cost of the redirected delivery.

13.8.8. Title and risk of loss will pass per INCOTERMS 2020 DDP—Delivered Duty Paid.

If the Order does not specify otherwise, THEN: Delivery will be governed by the stated provisions, including but not limited to its provisions for passage of title and risk of loss.

Note

For convenience, we use here a standard INCOTERMS 2020 three-letter option: By doing so, we automatically specify details such as responsibility for freight charges, insurance, and export- and customs clearance, in addition to passage of title and risk of loss. ¶ As a default measure (and in keeping with this book's service-to-others orientation), by adopting the INCOTERMS DDP rule, this section puts the onus on the Vendor to get the goods or other deliverables to the Customer's door, so to speak, unless otherwise agreed.

13.8.9. Discussion questions

  1. What are some pros and cons of spelling out, in the contract, the information that a customer must submit in an order?
  2. What are some pros and cons of:
    1. having each order become an addition to the master agreement, versus
    2. having each order be a separate agreement that incorporates the master agreement by reference.
  3. Why might a vendor want a quotation to have an expiration date?
  4. What are some pros and cons of allowing orders to be modified orally and not requiring written modifications?

FACTS: You represent a vendor. A customer wants its "affiliates" to be listed in the preamble as parties to the agreement, e.g., "The parties are ABC Inc. ('Provider') and XYZ Inc. and its affiliates ('Customer')."

QUESTIONS: (numbering is continued before)

  1. As the Vendor's lawyer, what do you think of this — what do you think the Customer really wants?
  2. How might you structure the contract to accommodate the Customer's likely desires — and to protect the Vendor?
  3. What are the INCOTERMS? What does "EXW" mean?

13.9. Purchase Orders Protocol

For anti-fraud internal controls purposes, a company of any size will likely be unwilling to accept goods or services, nor pay an invoice, unless the company has first issued a "purchase order" authorizing the transaction.

13.9.1. Parties: Vendor and Customer

  1. This Protocol Many aspects of the process described in this Protocol are similar to the way that procurement for the U.S. generally works, as implemented for example in the Federal Acquisition Regulations. See Legal effect of quotations, 48 C.F.R. § 13.004; see also, e.g., Eric E. Johnson, Formation of a Contract under the UCC (undated; part of an in-progress online casebook). ] will apply whenever, under the Con­tract, a party (the "Customer") issues a purchase order (as that term is commonly understood in the U.S., referred to here as an "Order") to acquire one or more items from another party (the "Vendor").
  2. This Protocol is considered part of the Order — that is, the terms of this Protocol are "incorporated by reference" into the Order — regardless whether the Order itself says so.
  3. The terms of this Protocol take precedence over any inconsistent terms in the Order unless the Order expressly and conspicuously says that this Protocol — by name — is being overridden.
Note

().  Subdivision A: The "whenever, under The Con­tract" phrase has in mind that under a vendor-customer master purchase agreements, one or more affiliates (see Protocol 20.1) of the customer might have the right to make purchases under the master agreement. ¶ The term "one or more items" encompasses goods (tangible or intangible), services, and/or other items such as, for example, license rights.

Subdivision C should give parties some flexibility to customize their deals. (See 8.1 for notes on conspicuousness.)

13.9.2. The Vendor may decide how Orders are submitted.

Unless the Con­tract clearly says otherwise: The Vendor is free to decide:

  1. the means and maner by which the Customer is to submit Orders; and
  2. what information is to be included with an Order.

13.9.3. An Order might not be binding on the Vendor (yet).

Just because the Customer sends an Order to the Vendor, that does not commit the Vendor to the Order unless:

Note

This Protocol is set up so that the Order is itself just an offer by the Customer.

  1. the Order is submitted in response to a Vendor sales quotation (a "Quote"; see Protocol 13.12); and
  2. the Quote clearly says either:
Note

Lawyers will recognize this subdivision as a 'translation' of UCC § 2-206(1), which says: "(1) Unless otherwise unambiguously indicated by the language or circumstances[:] (a) an offer to make a contract shall be construed as inviting acceptance in any manner and by any medium reasonable in the circumstances[.]" (Emphasis added.)

  1. that the sales quotation itself is an offer [and thus can be accepted]; or
  2. that the Customer may accept the Quote by submitting a purchase order.

13.9.4. An Order can specify how it is to be accepted.

  1. An Order could specify (in writing, obviously) that the Order can be accepted by the Vendor only in some particular manner, for example by written notification.
  2. Otherwise, though, the Vendor is free to accept an Order in any manner that is not prohibited by law.
Note

In some cases involving the sale of goods, an oral acceptance might not be enough to create a binding contract; see the discussion of the Statute of Frauds at 32.35.

13.9.5. The Vendor is free to decline any Order (normally).

The Vendor is free to decline to accept any Order unless the parties have clearly agreed otherwise in writing.

Note

Possible override: In a master purchase agreement, the Customer might want to override this section, possibly with language along the following lines: "The Vendor must accept any Order that is submitted in accordance with the requirements of the Con­tract." (For more on this concept, see the discussion at 13.3 concerning requirements contracts.)

13.9.6. Vendor silence doesn't imply Order acceptance.

If the Vendor does not respond to an Order, it does not mean that the Vendor has implicitly accepted the Order.

Note

This is a roadblock provision.

13.9.7. An unaccepted Order expires in three months.

If an Order that does not state an expiration date, THEN: The Order, if not accepted, will expire at the end of the stated period after the date of the Order — or, for an undated Order, the stated period after the date the Vendor received the Order — at which point the Vendor will no longer be able to accept the Order without the Customer's written approval.

Note

This tracks with § 13.12.5 (expiration of sales quotes) and with UCC § 2-205.

13.9.8. Customer: Beginning work on an Order doesn't commit the Vendor.

  1. If the Vendor starts but does not complete the action called for by an Order, and the Vendor does not otherwise accept the Order, THEN: The Vendor's incomplete action, in itself:
    1. will not be an acceptance of the Order, and
    2. will not obligate the Vendor to complete the action.
  2. If the Vendor neither accepts an Order nor completes the action called for by the Order, THEN: The Vendor's action referred to in subdivision A will be at the Vendor's own risk and expense unless the Con­tract clearly says otherwise.
Note

().  Background: Under the law, if the Customer sends the Vendor a purchase order for goods or services, and the Vendor ships the goods or performs the services without any accompanying "legal" paperwork of its own, then any "legal" terms in the Customer's purchase order might well be binding on the Vendor as a "unilateral contract," as discussed at 13.9.12.4.

On the hand, if the Vendor does respond with its own terms, then it'd likely cause a "Battle of the Forms" as discusssed at 28.8.

If an Order is for the sale of goods (in most of the U.S.), then UCC § 2-206 would come into play, allowing orders to be accepted by "prompt or current shipment …."

Pro tip: The Con­tract could address how the parties will proceed if the Customer were to change its mind about the Order before the Vendor's performance was complete.

13.9.9. Each Order is a separate contract.

Unless the Con­tract clearly states otherwise: Each accepted Order is a separate contract that incorporates the Con­tract by reference — including but not limited to this Protocol — whether or not the incorporation is explicit.

Note

().  Alternative: Each accepted Order will be considered an addition to the Con­tract and not as a separate contract.

Caution: From the Vendor's perspective, the above alternative would likely be unwise for everyday commercial orders because: (1) a default in one order could jeopardize the entire contract through "cross-default"; and (2) every new order could silently ratchet up the amount any contractual damages caps, each time increasing the vendor's financial risk.

Example: Suppose that a customer and a vendor entered into a master purchase agreement that capped the vendor's liability for damages at "the amounts paid or payable under the Con­tract." If every purchase order was an addition to the contract, then the damages-cap amount would grow over time as more purchase orders were placed and filled. The vendor wouldn't be wild about that — although the customer certainly wouldn't mind it.

Tangentially: In a decision about specific damages-cap language, an English court ruled that "the correct interpretation is that there is a single cap in the Clause, as Wipro contends, and not separate caps for each claim." Drax Energy Solutions Ltd. v. Wipro Ltd., [2023] EWHC 1342 ¶ 24, 56-74, 79 (TCC).

13.9.10. The Customer needn't pay for past-due affiliates' Orders (unless guaranteed).

Whenever one of Customer's affiliates places an Order under the Con­tract — which might or might not be expressly contemplated by the Con­tract:

  1. the Customer need not pay for that affiliate Order, if the affiliate fails to do so, unless the Customer guarantees payment in writing — in which case Protocol 4.8 (guaranties) is incorporated by reference; but
  2. the Vendor is free to accept or reject that Order.
Note

().  Background: When a big Customer enters into a "master purchase agreement" with a Vendor, the Customer often wants the agreement to allow "affiliates" of the Customer to place Orders on the same terms and conditions and with the same pricing. (The U.S. Government "GSA Schedule" is one example; see 31.17 for a brief discussion.) For those situations, this section sets expectations about payment.

Subdivision 1 puts the burden on the Vendor to check the separate creditworthiness of the Customer's affiliates that place Orders under the Con­tract.

  • That could be a significant concern, as discussed in more detail at 20.1.7.4.)
  • Absent a Customer guaranty of affiliate payment, the Vendor might want to defer or decline an Order from a Customer affiliate if the Vendor had one or more reasonable concerns about, for example: (1) the affiliate's ability to pay (see above); and/or (2) the legality of accepting or fulfilling the Order — for example, export-control laws or sanctions orders might prohibit the Vendor from accepting or fulfilling an order from a particular Customer affiliate; see generally 31.9.

13.9.11. Option: Customer's Change-Order Right

  1. If this Option is agreed to, THEN: Subject to the restrictions in this Option, the Customer is free to unilaterally make changes to an agreed Order for goods or services in one or more of the following aspects:
    1. specifications (for goods and/or services);
    2. designs and drawings (for items to be specially manufactured);
    3. shipment method (for goods and/or deliverables resulting from services);
    4. packaging method(s);
    5. quantity of goods or other deliverables;
    6. time or place of delivery of goods or other deliverables;
    7. timetable for services to be rendered; and/or
    8. quantity of services; that is, the Customer may require more- or fewer services than stated in the Order.
  2. A Customer's proposed unilateral change to an Order under subdivision A will automatically take effect — even without the Vendor's agreement — unless both of the following things happen:
    1. the Vendor sends the Customer a written objection to the proposed change; and
    2. the Customer receives the Vendor's written objection within ten business days after the Vendor received the change proposal.
  3. The Vendor is entitled to consider the Customer as bound by the change proposal if the individual issuing the change on the Customer's behalf had at least apparent authority to do so — unless the Con­tract clearly limits such authority.
Note

Change management is a Big Thing in master purchase agreements, as discussed at 13.9.12.6.

13.9.12. Additional notes

13.9.12.1. An overview of the purchase-order process

Students, be sure to read this:

When a vendor sells products or services to a large, "enterprise" corporate customer, the sales contract typically comes into being via the following mating dance, illustrated by this ladder diagram:

1.  If the (prospective) customer and the vendor haven't dealt with each other before, then the customer might send the vendor a request for information ("RFI") and/or a request for quotation ("RFQ").

(Or: If the customer wants a more-detailed proposal for the customer's specific needs, and perhaps a quotation, the customer might instead send the vendor a request for proposal, known as an "RFP.")

The customer might send the vendor an RFQ out of the blue. But often this happens because a vendor sales representative has "pitched" the vendor's products and/or services — and for big-ticket sales to large companies ("enterprise sales"), the overall "sales cycle" will often take weeks or months.

The RFQ might be a formal document labeled "Request for Quotation" or some such.

Or, the RFQ might be just an email or oral statement to the vendor by someone working for the customer: "OK, send me a quote."

2.  In response, the vendor's sales rep sends the customer a "sales quotation" or "quote" — concerning which, see the sales-quote protocol at Protocol 13.12.

3.  If and when the customer decides to buy, the customer sends the sales rep an order form such as a so-called "purchase order" or "PO"; typically, this will be an "offer" to purchase, which the vendor can "accept" or not. (Purchase orders are the subject of this Protocol.)

At this juncture, the vendor and customer might negotiate legal terms and conditions ("T&Cs"). Such legal negotiations often take awhile, especially if one side or another makes unreasonable demands. The vendor's sales people and the customer's relevant business users might get impatient — and blame "Legal" for the delay and their resulting frustration.

4.  If there won't be negotiation of the legal T&Cs, then:

4.1  The vendor's sales rep might ask the vendor's relevant people to do what's called for in the PO — e.g., ship the requested goods, perform the requested services — and send the customer an invoice. When that happens, the parties have entered into what's known as a "unilateral contract"; the customer's PO was an offer, which the vendor accepted by performance. (See 13.9.12.4 for more discussion.)

4.2  Or: The sales rep — before getting the vendor's performance started — might respond with another document, often called an "order confirmation." When this happens, the parties have entered into a so-called "Battle of the Forms," whose effects are discussed in more detail at 28.8.

[DCT TO DO? CREATE A LADDER DIAGRAM TO ILLUSTRATE THIS PROCESS?]

5.  Caution: Sometimes a vendor (or an individual sales rep) might be in danger of missing its sales-target number for a fiscal quarter. In that situation, the vendor might get a cooperative customer to place a so-called "round trip order," where the customer places an order with the vendor but the vendor places an offsetting order for the customer's goods or services.

This type of deal can be a species of securities fraud, and can get companies and individuals sued by the SEC and/or by securities plaintiffs and even imprisoned; see 13.4 for examples.

13.9.12.2. The parties' business processes might impede sales

Customers and vendors sometimes have business processes that they would like to have followed, with, e.g., minimum- or maximum order sizes.

And sometimes a customer that submits an order to a vendor will want to change the order, or even cancel it entirely.

It makes good business sense for the parties to have an agreed process in place for handling such situations.

13.9.12.3. Caution to Vendor: Don't sign a PO or order confirmation …

Vendors will want to train their front-line people not to sign a customer's purchase order — nor should a customer sign a vendor's order confirmation. At a minimum, doing so might create messy issues about whose contract terms apply, and those issues could require costly litigation to straighten out. Example: This happened in a COVID-era case from the Fourth Circuit.

  • A vendor of COVID-19 test kits sent a "purchase order" [sic] to a Florida government agency that wanted to buy test kits.
  • The agency's director signed the PO — but other email correspondence on the same day indicated that the terms and conditions were not completely agreed after all.
  • The Fourth Circuit observed (perhaps tongue in cheek): "After that [sic!], the parties’ dealings get messy." Global Innovative Concepts, LLC v. Florida Div. of Emerg. Mgmt., 105 F.4th 139, 142 (4th Cir. 2024) (vacating and remanding denial of state agency's federal sovereign-immunity motion to dismiss).
13.9.12.4. Caution to Vendor: Filling a "PO" might agree to its terms

In U.S. law schools, first-year students learn that a so-called unilateral contract can be formed without signatures from both parties if an unrevoked, otherwise-eligible offer is accepted by performance.

Example:

  • Alice's cat "Fluffy" goes missing.
  • Alice posts handbills on light poles, offering a $100 reward for Fluffy's safe return.
  • Bob finds Fluffy and returns her to Alice.
  • Bob's "performance" constitutes completion of the contract, and Alice must pay Bob the reward money.

So: In U.S. jurisdictions, when a customer sends a vendor a purchase order ("PO"), the PO might well count as an offer to enter into a contract, and the offer likely could be accepted by performance, i.e., by filling the PO — making the PO's terms and conditions part of "the contract" between the parties.

Example: Consider the following language from the giant networking-technology company Cisco's "Standard Terms and Conditions of Purchase – United States" § 1 (archived at https://perma.cc/SD47-YCHU).

Vendor's electronic acceptance, acknowledgement of ths Purchase Order, or commencement of performance constitutes Vendor's acceptance of these terms and conditions.

So: Suppose that Cisco sends a PO to the Vendor, and that in response, the Vendor simply ships goods to Cisco, without doing anything else — specifically, without sending the Vendor's own "paper" that pro forma rejected the Cisco terms. Under those circumstances, the Vendor might well find itself bound by Cisco's terms — which would almost surely be more onerous to the Vendor than would the Vendor's own terms and conditions.

(If the Vendor did send its own rejection, then the Vendor and Cisco would likely find themselves in what's known as the Battle of the Forms, discussed at 28.8.)

13.9.12.5. Other copy-and-paste language for Orders

Drafters can consider the following language options are provided in case the parties want to adapt one or more of them for use in the Con­tract:

The Customer may submit an order of any size.

or:

The Vendor may decline an order for goods or other deliverables if the ordered quantity of any single stock-keeping unit (SKU) is less than [insert quantity].

or:

The Vendor may decline an order where the aggregate order price is less than [insert amount], exclusive of taxes, shipping, and insurance.

Sometimes, when negotiating a master purchase agreement, the Vendor and the Customer might have a bit of a tug-of-war over the Vendor's autonomy in accepting Customer orders:

  • At one end of the spectrum, the Vendor might want to be free to reject any order for any reason or no reason.
  • At the other extreme, the Customer might want to require the Vendor to accept any Customer order whatsoever.

Drafters can adapt one or more of the following optional terms as desired. Caution: It should be apparent that several of the options below are mutually inconsistent.

The Vendor will not decline any order.

or:

The Vendor will not unreasonably decline an order.

(The above option, of course, raises the possibility of disputes about what constitutes unreasonable declining of an order. Such disputes should be escalated in accordance with 21.11.)

or:

The Vendor may decline any proposed order in its sole discretion; in case of doubt, here, decline has the same meaning as reject.

or:

If the Customer fails to pay amounts due to the Vendor when due, THEN the Vendor may decline subsequent proposed orders by the Customer until all such past-due amounts have been paid.

or:

The Vendor is deemed to have accepted an order, and to have waived its right to decline or otherwise reject the order, if the Vendor has not declined the order in writing within [fill in time] after the Vendor receives the order.

What about the Vendor's revoking of acceptance? Consider the following:

If the Customer has failed to pay one or more amounts due to the Vendor, THEN the Vendor may revoke its acceptance of the Customer's orders that the Vendor previously accepted but has not yet filled or completed.

or:

The Vendor may not revoke its acceptance of an order.

or:

The Vendor may revoke its acceptance of an order, but only under the following circumstances: [describe].

Caution: Some of the optional terms below might be mutually exclusive, so be sure to read each one carefully to avoid choosing conflicting options.

The Customer may cancel an accepted order for goods that are not to be specially manufactured for the order — but the Customer may do so only before the Vendor has shipped the goods — by sending a written cancellation advice to the Vendor.

and/or:

No Customer cancellation of a Vendor-accepted order will be effective if the order is for goods that will be specially manufactured for the order, but the Customer may cancel an order for other goods — only before the Vendor has shipped the goods — by sending a written cancellation advice to the Vendor.

or:

No Customer cancellation of a Vendor-accepted order for services will be effective.

and/or:

No Customer cancellation of a Vendor-accepted order for goods will be effective.

and/or:

A Vendor-accepted order for goods or other deliverables will not be deemed canceled unless the Vendor receives a written cancellation request, signed by an authorized representative of the Customer, no later than [specify the deadline].

and/or:

If the Customer cancels an order for goods or other deliverables, THEN the Vendor may invoice the Customer for, and the Customer will pay, a cancellation fee in the amount of [specify the amount].

13.9.12.6. Change orders can be tricky for parties to manage:

().  When a customer has a lot of buying power, its own standard purchase-order forms might well give the customer the right to unilaterally modify any order, with the modification becoming binding on the vendor if the vendor doesn't object within a certain period.

In that vein, this Protocol draws extensively on ideas in section 17 of a (very) customer-biased Honeywell purchase order form, reproduced in the appendix at 13.9.12.7 — but this section provides a simpler approach than the Honeywell version, which calls for "equitable adjustment" to pricing and/or delivery dates.

(U.S. Government contracts sometimes use a similar equitable-adjustment approach.)

Caution: Suppose that the Customer asks for a costly change but the Vendor doesn't follow an agreed procedure to ask for an increase in price: In such a situation, the Vendor might be stuck for the extra cost, as happened in an (unpublished) 2022 Iowa appeals court decision. See Ryan Companies U.S., Inc. v. FDP WTC, LLC, No. 20-1366, slip op. (Iowa App. Jan. 12, 2022) (reversing, in part, judgment awarding breach-of-contract damages to contractor) (unpublished).

Subdivision B.2: For the change not to take effect, the Customer must receive the Vendor's objection within the stated time. That is: The "Mailbox Rule" (discussed at 3.14) won't apply here.

Subdivision C: See generally the discussion of apparent authority at 29.5.3. Possible override language for the Con­tract: "Only an authorized procurement representative of [Customer] may agree to a change order."

13.9.12.7. Appendix: Honeywell change-order language

For those interested in really-detailed change-order language, see the  "spaghetti paragraph" language at section 17 of a Honeywell purchase order form, archived at https://perma.cc/84BS-KYXB.

13.10. Referrals Protocol

One way that a supplier might grow its "channel" (i.e., a network of outside relationships to promote sales) is to agree to pay another party a commission for referrals that turn into sales.

Caution: In some circumstances, "commission" might be a euphemism for "bribe" and, if so, could very well be a criminal offense that renders one or both parties liable for criminal fines and/or imprisonment.24

13.10.1. Parties: Vendor and Associate

  1. When this Protocol is agreed to, it signifies that under the Con­tract a party indicated in the Con­tract (the "Vendor") is to pay commissions to another party (the "Associate"):
    1. on sales by the Vendor to one or more customers (each, a "Prospect"),
    2. in a stated Territory (defined below),
    3. where the Prospect is referred to the Vendor by the Associate.
  2. This relationship between the Vendor and the Associate is a "Channel Partnership" as referred to at 13.15, which includes certain additional definitions and is incorporated by reference into this Protocol.

13.10.2. Commission Rate: 0.001%. Territory: One city block, all markets.

Commissions will accrue:

  • at the stated rate (the "Commission Rate"),
Note

Of course this particular Commission Rate is ridiculously low, and the Territory is ridiculously small — both are included for "fault tolerance" in case drafters neglect to specify otherwise.

  • of "Eligible Sales," defined at § 13.10.3 below,
  • that the Vendor makes during the "Partnership Term" (see 13.15.2),
  • but before the relevant "cliff deadline" (see § 13.10.5),
  • and subject to termination as to any particular referral (see § 13.10.7),
  • to any Prospect whose principal place of business has a mailing address no farther than the stated distance from the mailing address of the Associate's principal place of business. (the "Territory").

13.10.3. "Eligible Sales": Only certain sales.

Commissions will accrue only on the Vendor's sales of Vendor Offerings, to Prospects that the Associate refers to Vendor, where each of the requirements in the following paragraphs is satisfied, in addition to other requirements specified in the Con­tract ("Eligible Sales"):

  1. The Prospect has substantial operations in the Territory — the Vendor's determination on that point is final and binding.
  2. The Prospect was referred to the Vendor by the Associate during the Partnership Term — not before, not after.
  3. It is not against the law for the Prospect to acquire the relevant Vendor Offering(s) in the Territory.
  4. The Prospect is not a competitor of the Vendor, unless the Vendor gives its prior written consent.
  5. The Prospect did not have had a previous connection or relationship with the Vendor at the time of the Associate's initial referral — the Vendor's determination on that point is final and binding.
Note

().  This section assumes that the Vendor will want to pay commissions only for referrals that are genuinely useful for building out the Vendor's customer base.

Subdivision 1: The "substantial operations" criterion is one of those that likely can be safely left up to the Vendor to determine — because if the Vendor is too stingy in that regard, then it risks finding itself getting fewer and fewer referrals from that Associate.

Subdivision 2: A "sunset" for commission obligations can be extremely useful for certainty, which business people often value highly. Example: In a Massachusetts case, a court held that a particular referral agreement — which didn't put a time limit on a commission obligation — required payment of commissions on sales to two customers for as long as the seller continued to do business with those particular customers. See Prism Grp., Inc. v. Slingshot Techs. Corp., 104 Mass. App. Ct. 785, 245 N.E.3d 740 (2024) (affirming judgment after non-jury trial).

Subdivision 3: Legal restrictions on a Prospect's acquiring the Vendor's offerings could include, for example: (1) A Prospect might be on the Consolidated Screening List of parties to whom certain exports (including disclosures of information) are restricted by the U.S. Government. (2) In a given territory, the Vendor's offerings might be illegal to sell to persons under a certain age — for example, in years gone by, different U.S. states had different ages at which individuals could buy tobacco and alcoholic beverages (but now there's uniformity thanks to federal law). U.S. federal law prohibits sales of tobacco products to individuals under 21 years old, and it punishes states that allow sales of alcoholic beverages to those under 21 by reducing federal highway funding to those states.

Subdivision 4: The Vendor might rightly be concerned about unwittingly providing competitors with access to (for example) trade-secret computer software.

().  Subdivision 5: Any lack of clarity on this point could result in costly litigation. Example: In an English case, a tech company engaged an investment bank to help the company obtain financing. As it turned out, the company obtained financing from the parent company of the tech company. The bank demanded a "success fee" anyway — but the court's answer was "no." See Kigen (UK) Ltd. v NOR Capital Ltd., [2024] EWHC 3164 (Ch), ¶¶ 90-91.

On the other hand: Purely-commercial incentives should keep the Vendor from being too aggressive in determining that it had a prior relationship with a Prospect — otherwise, the Associate might simply stop referring prospects at all.

13.10.4. A sale is "made": Upon signing a binding contract.

For commission-eligibility purposes, any given Vendor sale to a Prospect is considered "made" on the date that the Vendor and the Prospect enter into a binding contract (which might or might not be the (putative) effective date of that contract).

Note

Caution: Be careful about using potentially-ambiguous terms such as "when a sale is consummated," because that could lead to costly litigation over the meaning of the term. Example: In one Third Circuit case, the court ruled that a finder's-fee agreement did not require the resulting contract to be "performed" in order for the transaction to be "consummated," and so a finder's fee was indeed due and owing for the transaction in question. See Fed Cetera, LLC v. Nat'l Credit Servs., Inc., 938 F.3d 466 (3d Cir. 2019).

13.10.5. "Sell-by" date for any referral: One year after the referral.

A sale to a Prospect is not eligible for a commission if the first Eligible Sale to that Prospect is "made" more than the stated time after the Associate's initial referral of the Prospect to the Vendor.

Note

The underlying idea here is that not all referrals are "good" referrals, from the Vendor's perspective — if the Vendor is unable to make an initial sale to a prospect on or before the cliff deadline, then the Vendor shouldn't have pay commissions for any sales to that prospect.

13.10.6. Commission cut-off-date: One year after first sale to referral.

A sale to a Prospect is not eligible for a commission if the Vendor enters into a binding contract for that sale more than the stated time following the first Eligible Sale to that Prospect.

Note

().  This section recognizes that as time goes on, and the Vendor (presumably) makes more sales to a referred Prospect, the sales will be less and less a result of the Associate's referral of the Prospect, and more and more a result of the Vendor's own success in dealing with the Prospect.

This section also gives the Associate an incentive to keep drumming up more new business for the Vendor, instead of "farming" commissions on old referrals.

Referral agreements should be clear on this point, because otherwise litigation might ensue from Associates wanting to get one last commission. See, e.g., MAK Tech. Holdings Inc. v Anyvision Interactive Tech. Ltd., 42 N.Y.3d 570 (2024) 249 N.E.3d 1194, 225 N.Y.S.3d 174 (2024) (reversing Appellate Division; plaintiff was not entitled to $1.25 million fee for transaction consummated eight months after "Term" of parties' agreement expired).

13.10.7. Phase-outs of commissions instead: If stated in the Con­tract.

In lieu of the all-or-nothing "cliff" cut-offs of § 13.10.5 and § 13.10.6, the Con­tract could provide for a phase-out period, with progressively-lower commission rates as time goes on.

Note

This might be preferable for the Associate, because as the relevant "sunset" date approached for a particular referral, the Vendor might feel it would do better financially by delaying sales until after the sunset date had passed.

13.10.8. Commission exclusions: Taxes, shipping, & insurance

Separately-itemized charges for taxes, shipping, and insurance are not eligible for commissions.

Note

This exclusion is pretty customary — but it should not be interpreted as excluding additional fees and other charges imposed and kept by the Vendor. (Two familiar examples: Checked-bags fees imposed by airlines, and "resort fees" charged by hotels). ¶ Concerning taxes, see Protocol 4.14 (tax responsibilities).

13.10.9. Commission payment due date: 30 days after collection EOQ.

  1. The Vendor must pay the Associate any commission(s) earned by the Associate, in full, no later than the stated time after the end of the Vendor's fiscal quarter in which the Vendor collects the associated invoiced sale price(s).
  2. In case of doubt: The Associate need not submit an invoice for commission payments to the Vendor.
Note

().  This gives the Vendor time to close its books for the quarter — and, sensibly, it makes the Associate wait to be paid until the Vendor is paid.

Note that the due date for a particular commission payment might turn out to be after commissions end for the referred customer in question under § 13.10.6.

Concerning invoices generally, see Protocol 4.10.

13.10.10. Deductions for possible returns: Allowed (within limits).

  1. When computing commissions due on sales, the Vendor may deduct from sales a reasonable allowance for returns — as long as those deductions conform to the Vendor's then-generally-effective return policy.
  2. The Vendor may determine its return policy in its sole discretion (defined at Protocol 9.6) from time to time, but the Vendor is to apply the return policy consistently for purposes of this Protocol.
Note

Caution: Keep in mind that under this Protocol, the Vendor normally doesn't have to pay commissions until after the relevant sales proceeds have been collected, thus reducing the Vendor's risk. The Vendor might well risk angering the Associate — which might be shortsighted on the Vendor's part — if the Vendor tried to claw back a commission from an Associate that felt that the commission had already been earned, and that the return was the Vendor's problem, not the Associate's.

13.10.11. Commission clawbacks for unpaid invoices: Allowed.

  1. This section applies if all of the following are true:
    1. The Vendor pays a commission before the Vendor collects payment for the relevant transaction;
    2. The Vendor is unable to collect the transaction payment after reasonable efforts — in case of doubt, those efforts need not include filing suit or initiating arbitration; and
    3. The Vendor did not take a deduction for a return allowance as provided in § 13.10.10.
  2. In that case, the Vendor may, at its option, do one or more of the following:
    1. deduct the amount of the paid commission from future commissions owed (if any); and
    2. after such deductions (if any): ask the Associate to refund any remaining portion of the paid commission, without interest, in which case the Associate must promptly refund that remaining portion.
Note

See the commentary to § 13.10.10. ¶ As a practical matter, it might be tricky for the Vendor to get the Associate to refund an already-paid commission.

13.10.12. No other payments to Associate for referrals.

In case of doubt, the Con­tract sets out the exclusive, aggregate right to compensation of the following — collectively, the "Associate Group" — in respect of any transaction of the type addressed in this Protocol:

  1. the Associate;
  2. the Associate's affiliates (if any); and
  3. the personnel of each of them.
Note

This is intended as a roadblock — but it's possible that the parties might have other payment arrangements that are documented by separate contracts.

13.10.13. Vendor sales records: Required.

The Vendor will keep records to support commission amounts due under the Con­tract in accordance with Protocol 5.7, which is incorporated by reference

13.10.14. Commission statements to Associate: Required.

With each commission payment, the Vendor is to provide the Associate with a complete and accurate written statement of the amount(s) due, with reasonable supporting detail.

Note

The term "complete and accurate" is far better than "true and correct," as discussed at 32.38.

13.10.15. Associate audit rights: Yes, per RPM protocol.

The Associate may have the Vendor's commission statements audited in accordance with the audit protocol at Protocol 4.3, which is incorporated by reference.

Note

A recordkeeping requirement and an audit requirement will often go "hand in hand," for reasons discussed in the commentary of Protocol 4.3 (audit protocol).

13.10.16. Referrals: Additional notes

13.10.16.1. Two special cases: Lawyer- and investor referrals

Special case #1: In the U.S., legal-ethics rules impose strict limits on lawyers ability to pay or receive commissions for client referrals. See generally, e.g., Rob George, The Ethics of Referrals, Part 1, Part 2, and Part 3 (TLIE.org 2023).

Special case #2: If the referral fee is being paid for introducing a potential investor to a company, then under U.S. securities law, the person doing the referring might have to register as a "broker." See Michael Blane & Richard A. Friedman, SEC Revisits ‘Finder’ Exemption: Potential Impacts for Small Businesses and the Capital Markets (CorporateSecuritiesLawBlog.com 2025).

13.11. Resale Protocol

Many, many products (and services) are not sold directly by their manufacturers (or at least not exclusively directly), but indirectly via one or more layers of resellers. This Protocol sets out basic provisions for reseller agreements. Such reseller relationships can be important for suppliers looking to grow their "sales channels."

13.11.1. Parties: Vendor and Reseller

The parties anticipate that one party specified in the Con­tract (the "Reseller") will, under the Con­tract, do the following:

Note

The term "Reseller" could encompass a variety of different functions such as distributors, wholesalers, and retailers.

  1. acquire one or more products, services, and/or other items (the "Vendor Offerings") of another specified party (the "Vendor"), and
  2. resell the Vendor Offerings in a specified "Territory" (see below).

13.11.2. The Sales-Channel Partnership Protocol also applies

The relationship between the Reseller and the Vendor is a "Channel Partnership" as referred to at Protocol 13.15, which (1) includes certain basic definitions, and (2) is incorporated by reference into this Protocol.

Note

See the commentary at Protocol 13.15.

13.11.3. Territory: One-half-mile radius around Reseller address.

The term "Territory" refers to the stated distance around the street address of the Reseller's principal place of business.

Note

Of course this particular "placeholder" Territory is ridiculously small; it's included for "fault tolerance" in case drafters neglect to specify otherwise. (The Reseller is extremely unlikely to agree to this IRL, "In Real Life.")

13.11.4. Reseller's discount: 0.001%.

During the Partnership Term, the Reseller is entitled to acquire Vendor Offerings directly from the Vendor at the stated discount from the Vendor's then-current, published list price that is applicable in the Territory.

Note

As with the Territory definition, this is a ridiculously-low "placeholder" discount.

13.11.5. The discount & territory are Vendor confidential information.

The percentage and/or amount of the Reseller's discount, and the definition of the Reseller's Territory, are the confidential information of the Vendor; the Reseller will not reveal that information (nor confirm it) to third parties — including but not limited to other suppliers — without the Vendor's prior written consent.

Note

The parties might want to include Protocol 5.3 (confidential information protocol) in the Con­tract as well.

13.11.6. Payment terms to Vendor: Net 30 from invoice receipt.

If the Reseller buys Vendor Offerings directly from the Vendor, THEN: The Reseller will pay as stated in the heading of this § 13.11.6 and in accordance with Protocol 4.13 (payment terms).

Note

This § 13.11.6 doesn't address whether the Reseller is required to buy Vendor Offerings from the Vendor at all, or perhaps exclusively. (Caution: In some contexts — for example, a franchise agreement — such a mandatory-sourcing requirement could trigger antitrust questions, for example whether the requirement constituted an unlawful tying arrangement; see generally the Federal Trade Commission's fact sheet on tying arrangements.)

13.11.7. The Vendor has no pricing authority for Reseller sales.

As between the Vendor and the Reseller, the Vendor has no authority to determine the prices that the Reseller charges to the Reseller's customers.

Note

The Vendor might be tempted to try to prohibit the Reseller from discounting Vendor's products or services. But that kind of "retail price maintenance" ("RPM," sometimes known as "vertical price fixing"; see 13.2.1) could lead to issues under antitrust law. Consequently, many businesses prefer to stay away from the possible litigation burden and expense by simply not engaging in RPM. See generally, e.g., Matthew L. Powell, A Primer on Resale Price Maintenance, Mich. B.J., Aug. 2017, at 20.

13.11.8. The Reseller will not alter Vendor Offerings.

The Reseller must not package, repackage, modify, or otherwise alter any Vendor Offering, in any way, without the Vendor's prior written consent, including but not limited to the following:

  1. removing or altering of any legend or notice — for example, copyright- or trademark notices and the like — and/or warnings or user instructions from any Vendor Offering itself or associated promotional materials, user documentation, etc.;
  2. opening any sealed package in which any part of a Vendor Offering comes to the Reseller — including, for example, a software license code in a sealed envelope;
  3. separating components of a Vendor Offering, for example for for individual sale.
Note

().  In some cases, the Vendor won't really care whether the Reseller modifies the Vendor's goods — but some such modifications could result in the Vendor's getting dragged into lawsuits against the Reseller by the Reseller's customers.

If the Vendor owned intellectual-property rights in a Vendor Offering, then the Vendor also might not want the Reseller creating "derivative works" without permission.

13.11.9. Reseller customers will get Vendor-standard warranties.

  1. For Vendor Offerings, the Vendor must honor substantially the same warranty terms — if any — for the Reseller's customers as it would for the Vendor's own relevant customers.
  2. Subdivision 1 does not preclude the Vendor:
    1. from providing different warranty terms for its customers in different geographic- or market-segment territories; nor
    2. from offering no warranty for a given Vendor Offering.
Note

This section gives the Reseller's customers essentially-equal status with the Vendor's own comparable customers. (It's also meant as a guardrail, to dissuade the Reseller — or the Reseller's customers — from claiming that the Vendor must do more for the Reseller's customers than for the Vendor's own customers.)

13.11.10. The Vendor will indemnify certain warranty claims.

The Vendor will defend and indemnify the Reseller and the Reseller's Protected Group from any claim — by any of the Reseller's customers that acquired (directly or indirectly) a Vendor Offering from the Reseller — if the claim arises out of an alleged breach of any Vendor warranty concerning that Vendor Offering.

Note

Pro tip: As with any indemnity obligation, the Reseller might want to check out the Vendor's financial ability to comply with the obligation — and possibly negotiate to have the Vendor maintain one or more backup sources of funding (such as insurance) for that purpose.

13.11.11. Customer support: Level 1: Reseller. Levels 2 and 3: Vendor.

During the Partnership Term, the Reseller and Vendor will provided Levels 1 through 3 support (defined at § 13.14.1) as stated for the Reseller's customers for Vendor Offerings.

Note

The Vendor will normally be very interested in making sure that the Reseller's customers are properly supported in their use of Vendor Offerings, because that will affect the reputation of both the offerings and the Vendor — especially in this era of online reviews and social-media word of mouth. ¶ On the other hand, the Vendor might well want at least some of the cost and burden of providing basic customer support to be taken on by the Reseller, as part of what the Vendor is "paying for" by giving the Reseller a price discount. (This could be a point for negotiation.)

13.11.12. The Reseller will follow Vendor customer-support guidelines.

When the Reseller provides support for its customers, the Reseller will follow any reasonable written- and oral guidance for customer support that the Vendor provides to the Reseller, so long as that the guidance is not inconsistent with the Con­tract.

Note

In crafting technical-support guidance, the Vendor would normally want to specify that the Reseller must promptly contact the Vendor if the Reseller is unable to deal with a particular support challenge within a given amount of time — because if a Reseller customer were unhappy with the support the customer received from the Reseller, that fact could reflect badly on the Vendor Offerings and/or on the Vendor's brand.

13.11.13. Reseller servicing of Vendor Offerings must meet standards.

  1. This section will apply if the Reseller engages in repair or other servicing of Vendor Offerings.
  2. The Reseller will use parts of equal or better quality than original.
  3. The Reseller will not offer or provide as "new" any Vendor Offering that the Reseller has repaired after a customer returned it, unless the Vendor specifically agrees in writing.
  4. For emphasis: This section in itself does not authorize, require, or prohibit, the Reseller's servicing of Vendor Offerings.
Note

It's not uncommon for both suppliers and resellers to offer "refurbished" products that have been returned by customers. This subdivision gives the Vendor some control over whether and how the Reseller does so.

13.11.14. The Reseller will support any Vendor recalls.

  1. If the Vendor issues a recall of any Vendor Offering, THEN: The Reseller must provide reasonable cooperation with the Vendor (and with the Vendor's designees) in connection with the recall.
  2. At either party's request: The parties must escalate any disagreement about what would constitute the Reseller's reasonable cooperation under subdivision A as provided in Protocol 21.11.
Note

What would constitute "reasonable" cooperation could depend in part on whether the Vendor agreed to reimburse the Reseller for reasonable out-of-pocket external expenses actually incurred by the Reseller in providing such cooperation.

13.11.15. The Reseller will support its own warranties (if any)

This Protocol does not preclude the Reseller from offering additional- or more-favorable warranties (or other commitments) to the Reseller's own customers concerning Vendor Offerings — but if the Reseller does so, it will be at the Reseller's own risk and expense.

Note

This phrasing was chosen so as not to imply that the Vendor was somehow "authorizing" the Reseller's activity — conceivably, such an implication might have downstream liability implications for the Vendor if a Reseller customer were to sue the Reseller for breach of the Reseller's additional warranty and also sue the Vendor on some kind of negligent-authorization theory or other "creative" rationale.

13.11.16. The Reseller has certain indemnity obligations of its own.

The Reseller will defend and indemnify the Suplier and the Suplier's Protected Group against any claim by a third party that arises out of acts or omissions on the Reseller's part that relate to Vendor Offerings, other than a claim that the Con­tract unambiguously makes the responsibility of the Vendor.

Note

Pro tip: As with any indemnity obligation, the Vendor should consider negotiating to have the Reseller maintain insurance as backup funding for the obligation (and the Reseller should consider doing so anyway).

13.11.17. Reseller customers' rights will continue after termination.

The ending of the Channel Partnership between the Reseller and the Vendor, whether by expiration or other termination, will not reduce the Vendor's obligations — if any — to the Reseller's customers concerning Vendor Offerings.

Note

This section should give the Reseller some comfort that the Vendor won't just abandon the Reseller's customers after termination of the Reseller's relationship with Vendor — but often, that should be practically a given, because the Vendor will want to transition those customers into a direct relationship with the Vendor or over to a different reseller.

13.11.18. The Reseller has IP-infringement responsibilities.

If the Reseller suspects that unauthorized use, copying, distribution, or modification of a Vendor Offering might be occurring, THEN: The Reseller will proceed as stated at Protocol 23.4 (protocol for dealing with potential infringement of IP rights).

13.11.19. The Vendor reserves all other Vendor-Offering rights.

As between the Reseller and the Vendor, the Vendor reserves all rights concerning Vendor Offerings that are not specifically granted by the Con­tract — that reservation extends (without limitation) to all copyrights, patent rights, trademark and service mark rights, trade secret rights and other intellectual property rights in Vendor Offerings.

Note

Concerning the phrase "[a]s between," see 32.4.

13.11.20. The Vendor is not responsible for the Reseller's business position.

The Vendor has no responsibility — financial or otherwise, under any theory:

Note

This originated in a court case I once read, where a manufacturer terminated its contract with a supply-chain partner — as allowed by their contract — and in response, the partner sued the manufacturer, claiming that the manufacturer had knowingly allowed the partner to become dependent on the manufacturer's business, or something like that. (Unfortunately, the case citation seems to have disappeared along the line, and I wasn't able to find the cite in earlier drafts.)

  1. for any dependence that the Reseller's business might have on being able to sell Vendor Offerings; nor
  2. for any harm that might result to the Reseller from the ending, for whatever reason, of the Reseller's relationship with the Vendor,

and the Reseller WAIVES any claim to either effect.

13.11.21. Software offerings have certain other terms.

  1. This section will apply in respect of any Vendor Offering that includes one or more types of license for the use of software (the "Software"), including but not limited to licenses to use software-as-a-service, or "SaaS."
  2. Protocol 13.11.30 (software-specific items) is incorporated by reference into this Protocol for each Vendor Offering within the scope of subdivision A.

13.11.22. Option: Reseller Minimum Inventory

The Reseller will keep a minimum quantity of Vendor Offerings in inventory as follows: [DESCRIBE].

13.11.23. Option: Reseller Maximum Inventory

The Reseller will not keep more than [AMOUNT] of Vendor Offerings in inventory without the Vendor's prior written consent.

13.11.24. Option: Reseller Retail Sales Authorization

For emphasis: This Protocol does not preclude the Reseller from offering and/or selling Vendor Offerings from physical premises (for example, in stores).

13.11.25. Option: Reseller Retail Sales Prohibition

To the extent not inconsistent with applicable law — especially but not exclusively antitrust- and competition law — the Reseller agrees not to offer or sell Vendor Offerings from physical premises (for example, in stores) without the Vendor's prior written consent.

13.11.26. Option: Reseller Supply Source Limitation

To the extent not inconsistent with applicable law — especially but not exclusively antitrust- and competition law — the Reseller is not to acquire Vendor Offerings from sources other than Vendor.

13.11.27. Option: Reseller Redistribution Prohibition

To the extent not inconsistent with applicable law — especially but not exclusively antitrust- and competition law — the Reseller is not to provide Vendor Offerings to others for resale or redistribution.

13.11.28. Option: Reseller Delivery Responsibility

As between the Reseller and the Vendor, the Reseller is responsible — at the Reseller's own expense and risk — for the following:

Note

Concerning the phrase "[a]s between," see 32.4

  1. acquiring any physical Vendor Offerings; and
  2. arranging for all storage and/or delivery to the Reseller's customers.
Note

This Option likely wouldn't apply in so-called "drop shipping" arrangements, where the Reseller communicates an end-customer order to the Vendor, whereupon the Vendor ships the ordered goods directly to the end-customer.

13.11.29. Option: Post-Termination Closings

After any termination of the Channel Partnership — other than for material breach by the Reseller — the Reseller may try to close any pending sales for five business days after the effective date of termination.

Note

Some resellers will want to be able to close out their not-yet-completed deals. (But this Option might not be necessary if the Reseller has sufficient advance notice of termination.)

13.11.30. Resale: Software Supplement Protocol

13.11.30.1. Applicability of this Protocol

This Protocol will apply in connection with any Vendor Offering that includes one or more types of license for the use of software (the "Software"), including but not limited to licenses to use software-as-a-service, or "SaaS."

Note

Software is often "sold" (that is, licensed) through resale channels; this Protocol adds ground rules for that case — drafters should consider adopting this Protocol in any reseller relationship where the Reseller will be dealing with the Vendor's computer software.

13.11.30.2. The Reseller will refer its customers for Vendor provisioning.

Unless otherwise directed by the Vendor, the Reseller will refer all of the Reseller's customers for the Software to a Vendor-designated provisioning system for signing up for access to (and licensing of) the Software.

Note

When the Vendor Offerings include SaaS, the Reseller will almost certainly want the Vendor to provide the necessary customer onboarding — and the Vendor will typically insist on doing so.

13.11.30.3. Reseller customers might have to agree to Vendor terms.

The Vendor is free to require the Reseller's customers to agree to the Vendor's then-current terms and conditions as a prerequisite for their being able to install and/or use the Software.

Note

The Vendor will typically want Reseller customers to agree to, for example: • an end-user license agreement ("EULA"); • terms of service or ‑use ("TOS"); and/or • a privacy policy.

13.11.30.4. The Reseller will "push" any Vendor software updates
  1. This section will apply if the Vendor releases a superseding version of the Software.
  2. If so requested by the Vendor, the Reseller must promptly encourage all of the Reseller's customers to acquire and install the superseding version — but the Reseller is not responsible for making sure that the Reseller's customers actually do so.
Note

Subdivision 1: The phrase "superseding version" would commonly include things such as updates, bug fixes, and the like.

Where SaaS (Software as a Service) is concerned, updating would normally be handled directly by Vendor, hence the "If so requested by Vendor" qualification here.

13.11.30.5. The Reseller has limited use rights for the Software.
  1. The Reseller is free to use the Software — as limited by subdivision 2 — solely for purposes of the following:
    1. demonstrations to, and training of, customers and/or clients, existing or prospective;
    2. testing; and/or
    3. internal training of the Reseller's personnel to support the Reseller's Software sales operations.
  2. Note: The Reseller's authorization in subdivision 1 extends only as follows:
    1. to the Software in executable form only; and
    2. in compliance with the Vendor's applicable terms and conditions.
Note

().  The "solely for purposes …" phrase rules out the Reseller's use the Software in other ways — such as, for example, production use for the Reseller's own benefit, and/or service-bureau use for the benefit of any Reseller customer — without the appropriate separate license(s) from the Vendor. (This is not just a theoretical concern.

DCT note: This is not an imaginary issue: I once served as an expert witness in a case in which a software vendor's customer used the vendor's software to offer services to the customer's own customers — thus potentially depriving the vendor of license sales to those other customers. As usually happens in such litigation, the parties settled the dispute before trial.

13.11.30.6. The Reseller may make limited copies of the Software.
  1. The Reseller is free to make a reasonable number of copies of the Software for purposes of backup, disaster recovery, and disaster testing.
  2. The Reseller's activities under subdivision 1 must be done in accordance with commercially-reasonable IT practices.
Note

Unlike some ill-considered provisions, this section does not limit the Reseller to making just one backup copy, which simply wouldn't be practicable (nor would it usually be prudent).

13.11.31. Reseller relationships: Additional notes

13.11.31.1. Real-world example: An "in the wild" reseller agreement

For a pretty-detailed example of a reseller agreement "in the wild," see the Cisco Indirect Channel Partner Agreement (SEC.gov); see also the various Options accompanying this Protocol.

13.11.31.2. Reseller relationships can end badly.

Caution: Reseller relationships can work well. But over time — and as parties' personnel and strategic plans change — even once-successful relationships can deteriorate and ultimately devolve into costly, time-consuming litigation. This can be seen in a Tenth-Circuit case that arose "from the breakdown of a profitable business relationship that ended with a cohort of disgruntled employees jumping ship from one company to the other." ORP Surgical, LLC v. Howmedica Osteonics Corp., 92 F.4th 896, 902 (10th Cir. 2024).

13.12. Sales Quotes Protocol

In sales by a vendor to a large-ish customer, a common part of the sales cycle is for a sales representative, or "rep," to send the customer a sales quotation, or "quote" (or, sometimes, "quote sheet"). If the terms are to the customer's liking, the customer will respond with a purchase order (discussed at Protocol 13.9). (The vendor's sending of a quote will often be preceded by the customer's sending a request for proposal ("RFP") or a request for quotation ("RFQ").)

This Protocol runs in parallel with applicable law in some jurisdictions; drafters can use it to establish more certainty about the ground rules for sales discussions.

13.12.1. Parties: Vendor and Customer

  1. This Protocol will apply whenever, under the Con­tract, a party (the "Vendor") provides a sales quotation or comparable document (each, a "Quote") to another party (the "Customer").

13.12.2. Terms of Quote

  1. The terms of this Protocol are considered part of the Quote — that is, this Protocol is "incorporated by reference" (see Protocol 3.7) into the Quote — even if the Quote itself does not say so.
  2. The terms of this Protocol take precedence over any inconsistent terms in the Quote unless the Quote expressly and conspicuously says that this Protocol — by name — is being overridden.
Note

().  See also Protocol 3.3 (entire agreement), along with 28.8 concerning the effect of additional terms in purchase orders, etc.

Subdivision 2 borrows its "express" and "conspicuous" requirements from the Express Negligence Rule (see 14.3.4). It gives parties some flexibility to customize their deals. (See also 8.1 for notes on conspicuousness.)

13.12.3. Catalogs, etc., aren't binding on the Vendor.

The Vendor's advertisements, catalogs, price lists, quotations, and similar documents are not "offers," so the Customer cannot "accept" them either.

Note

This tracks the law in the U.S. and many other jurisdictions: A vendor's advertisement or catalog is generally considered not to be an offer itself that can be accepted — instead, it's an "invitation to treat," that is, an invitation to others asking them to make an offer, which the vendor can then accept, as discussed generally in a Wikipedia article.

13.12.4. A Quote won't "lock in" the Vendor (normally).

When the Vendor sends the Customer a Quote, the Quote is not an "offer" — and so, the Customer cannot unilaterally form a binding contract by accepting the Quote, which the law might otherwise let the Customer do — unless:

  1. the Quote itself clearly says so; or
  2. the Vendor agreed to that, in writing.
Note

().  This section borrows from how procurement for the U.S. Government generally works: Under the Federal Acquisition Regulations, quotations are not offers, orders are. See Legal effect of quotations, 48 C.F.R. § 13.004. ] For similar terms, see section 1 of a Honeywell terms-of-sale document.

Subdivision 2: The "agreed to that, in writing" phrase is intended to serve as a mini-version of the Statute of Frauds: It wouldn't be good for the Vendor and the Customer to get into a dispute about whether the Vendor's sales representative supposedly said orally that the Quote was indeed an offer, or that the Customer could accept the quotation by simply sending in a purchase order.

13.12.5. Expiration of Quotes

Whether or not a Quote qualifies as an "offer": The Quote will expire — and so if the Quote is an "offer," the Customer will no longer be able to accept it — at the end of the business day on the date three months after (a) the date of the Quote itself, or (b) the date of the Customer's receipt of the Quote, if the Quote is undated (so as not to penalize the Customer for the Vendor's failure to date the Quote), in either case unless:

  1. the Quote explicitly says otherwise in writing, or
  2. the Quote is an offer and the Vendor has received the Customer's written acceptance of the offer.
Note

().  Background: A Vendor will usually want a quote to expire because the Customer might take its time deciding whether or not to buy — then, as time passes:

  • The Vendor might stop offering the product or service that's the subject of the quote;
  • the Vendor might raise its prices above those stated in the Quote; and/or
  • the Vendor might decide, for whatever reason, that it no longer wants to deal with that Customer at all — perhaps because the Vendor has decided that the Customer is going to be too much trouble to work with, or perhaps the Vendor has engaged a reseller for the territory (see 13.11) and now wants the Customer to deal with the reseller instead of directly with the Vendor.

(The Vendor could have other reasons, of course.)

The three-month gap-filler expiration date for Quotes is a mirror of the three-month "gap filler" rule of UCC § 2-205 for purchase orders; in addition, three months is substantially equal to one fiscal quarter, which generally fits in with standard accounting practices.

Pro tip: To serve the reader — not least, the Customer — the Vendor should consider putting a specific expiration date on each Quote (e.g., "This quotation will expire on December 25, 20xx") instead of making the reader compute the expiration date.

Subdivision 2: By requiring receipt of acceptance of a quote by the Vendor, this subdivision intentionally goes against the "Mailbox Rule" (see 3.14.9), under which certain contract-related communications are deemed effective when mailed.

13.12.6. Withdrawal of a pending Quote

The Vendor is free to withdraw or modify a Quote, even if the Quote qualifies as an "offer," until such time (if any) as the Vendor receives the Customer's timely, written acceptance — the Mailbox Rule for acceptance of an offer will not apply to the Quote.

Note

().  If a Quote isn't an offer, then of course the Vendor would be free to modify the Quote at any time, even if the Customer were to submit an order based on the Quote.

The "Vendor receives … written acceptance" term is likewise intended to negate the Mailbox Rule, under which an offer would be deemed accepted, and a binding contract would be formed, as soon as the Customer mailed the acceptance to the Vendor.

Pro tip: Obviously, a sales-savvy Vendor would be reluctant to unilaterally modify a pending Quote that a prospective Customer is in the process of considering.

13.13. Defect Correction Protocol

Defect correction comes up all the time in contracts for services, for the sale of goods, for licensing softaware, and probably other contexts as well. This Protocol sets out a fairly-standard "Three Rs" approach — repair, replace, or refund — for dealing with (purported) defects in goods or services.

13.13.1. Parties: Vendor and Customer

This Protocol provides a protocol by which a party clearly indicated in the Con­tract (referred to for convenience as the "Vendor"):

  • will correct defects in goods or services,
  • that are provided to another party (the "Customer"),
  • by the Vendor and/or by a third party,
Note

Concerning "and/or by a third party": The allegedly-defective goods or services might actually have been provided by a party other than the Vendor, for example (hypothetically) by a reseller of the Vendor's goods. Or, the "Vendor" might be a service company engaged by a manufacturer to make repairs on the manufacturer's products.

  • under the Con­tract.

13.13.2. Definition: What counts as a "defect"?

For purposes of this Protocol, the term "defect" (whether or not capitalized) refers to any failure, by one or more deliverables and/or services provided under the Con­tract, to comply with agreed written specifications.

Note

Agreed written specifications could be set forth, for example: • in the Con­tract itself; • in an agreed purchase order for goods — see also Protocol 3.3 concerning additional or different terms in purchase orders; and/or • in an agreed statement of work for services.

13.13.3. The Customer has three months to report a defect.

The Customer's rights, and the Vendor's obligations, under this Protocol apply only to (purported) defects: • that are reported, in writing, • by the Customer or on the Customer's behalf, • to the Vendor or to the Vendor's designee, • on or before the end of the stated time period after whichever of the following dates is applicable:

  1. the date of delivery of the relevant deliverable, if the defect is in a deliverable, or
  2. completion of the relevant service.
Note

Concerning deadlines generally, see Protocol 20.16. ¶ Concerning months, see Protocol 20.27

Note

The Vendor will want to establish a deadline as a cutoff date for defect-correction obligations — but the Customer, of course, will want to make sure that the cutoff date is far enough ahead that defects are reasonably certain to become apparent.

13.13.4. Vendor: Follow "the Three Rs" of corrective action.

The Vendor will take one or more of the following actions for each timely-reported defect:

Note

We use the "Three Rs" motif here to help drafters and parties remember the basic structure of this approach. (Ditto with the Three Rs of Notice in Protocol 3.14.)

  1. Repair: The Vendor will correct the defect if commercially practicable; see also § 13.13.7 below concerning the possible approaches to repairing; and/or
  2. Replace: The Vendor will replace a defective deliverable with a non-defective one that meets the agreed specifications, or in the case of services, redo the defective service(s); and/or
  3. Refund: If the reported defect is material and the Customer so requests within a reasonable time, THEN: The Vendor will promptly issue a refundable credit for the relevant deliverable(s) and/or service(s).
Note

This materiality provision gives the parties some flexibility while still providing protection for the Customer.

13.13.5. The Vendor may use its judgment how to proceed.

The Vendor is free to exercise its judgment in choosing:

  1. whether to try to repair and/or replace the defect as provided above, and
  2. the timing of those action(s),

as long as the Vendor otherwise complies with this Protocol.

Note

Caution: This Vendor flexibility might be a Very Bad Thing for the Customer if the Customer is counting on having the Vendor's products or services available in emergencies or other important matters. For such situations, the Customer might well want to discuss detailed contingency plans for various what-if scenarios.

13.13.6. The Vendor has 30 days to fix the defect after receiving the Customer's report.

  1. The Vendor will complete any repair or replacement above on before the end of 30 days after the Vendor receives the defect report.
  2. If the Vendor does not comply with subdivision A, THEN: The Vendor will cause any refund to be made (as stated in § 13.13.4) promptly upon the Customer's written request and return of the relevant deliverable(s).
Note

A refund is required only if requested by the Customer, because the Customer might prefer to keep the relevant deliverable(s).

13.13.7. What could "repair" consist of?

Repair of a defect could include, without limitation, one or more of the following:

  1. actual repair of a defective deliverable;
  2. in the case of services, correction of defective work;
  3. delivery of a commercially-reasonable workaround for the defect, if the Vendor reasonably determines that repair or correction would be impracticable or not cost-effective.

13.13.8. Escalation

If the parties reach an impasse about what the Vendor is supposed to do under this Protocol, THEN: They will escalate the dispute in accordance with in Protocol 21.11, if either party asks.

Note

This is another use case for the neutral-advisor escalation protocol of Protocol 21.11.

13.13.9. Vendor: Pay for all defect-correction work.

As between the Vendor and the Customer, the Vendor is to cover all of its expenses of actions taken, by the Vendor or on its behalf, under this Protocol — without asking the Customer for reimbursement — unless otherwise agreed in writing.

Note

Many services-type contracts (e.g., building-construction contracts) explicitly call for the Customer to pay some or all expenses. When that's to be the case, the Con­tract, statement of work, etc., should clearly say so. (See also the expense-invoicing restriction in Protocol 4.10.8.)

13.13.10. The Vendor has flexibility if it cannot reproduce a reported defect.

  1. If the Vendor is unable to reproduce the reported defect through commercially-reasonable efforts, THEN: The Vendor need not take any further action under this Protocol.
  2. In some circumstances, the Vendor might be unable to reproduce a defect, but might still choose to replace the deliverable in question, and/or to arrange for the Customer to get a refund. If that happens, THEN:
    1. the Vendor's action will be considered a commercial decision by the Vendor, to further the Vendor's own business interests; and
    2. the Customer will not assert that the Vendor was conceding or acknowledging anything by the Vendor's action.
Note

().  Reproducibility language like this is often included in license agreements for complex software, where the vendor might not be able to reproduce a bug that shows up only in a particular customer's installation.

The Customer might want to try to negotiate for the right to require the Vendor to provide a refund (within a short time after delivery) even in cases where the Vendor is unable to reproduce the defect.

13.13.11. The Vendor doesn't guarantee future performance (unless so stated).

  1. In agreeing to this Protocol, the Vendor is not warranting or guaranteeing the future performance of any repaired- or replaced deliverable unless the Con­tract clearly says otherwise.
  2. The Vendor is, however, committing to take the actions stated in this Protocol if a deliverable, as delivered, fails to comply with any applicable Vendor warranty.
Note

().  This section reflects the sometimes-crucial distinction between (1) a warranty that goods as delivered will conform to certain standards, with a cutoff date for the customer to report defects — that's the approach of this Protocol; versus (2) a warranty that, for a stated period of time in the future, the goods will conform to certain standards of performance.

That distinction can sometimes determine whether a customer has timely filed a lawsuit for breach of warranty, or whether instead the suit is barred under the relevant statute of limitations, as discussed at 31.40.8.

13.13.12. EXCLUSIVE REMEDIES

Unless the Con­tract clearly states otherwise:

  1. the Vendor's obligations set forth in this Protocol are the Vendor's only obligations — and the EXCLUSIVE REMEDIES available to the Customer and/or to anyone claiming "through" the Customer — for any defect in goods or other deliverables or in services; and
  2. the Customer must not seek to hold the Vendor liable otherwise — and the same goes for the Vendor's affiliates, subcontractors, and their respective people.🔗
Note

Vendors are very prone to include exclusive-remedy provisions like this in their terms of sale. ¶ The term "anyone claiming 'through' the Customer" will be familiar to lawyers and law students.

13.14. Customer Support Protocol

13.14.1. Support Levels Definition

A party that commits to providing "Level X support" (or equivalently "Tier X support"), where X is a number (generally 1, 2, or 3), is responsible for the following:

Level 1: Routine basic support for a product or service; it entails providing customers, where applicable, with:

  1. compatibility information,
  2. installation assistance,
  3. general usage support,
  4. assistance with routine maintenance; and/or
  5. basic troubleshooting advice.

Level 2: More-in-depth attempts to confirm the existence, and identify possible known causes, of a defect in a product or an error in a service that is not resolved by Level 1 support.

Level 3: Advanced efforts to identify and/or correct a defect in a product or an error in a service.

Note

This Definition can come into play in reseller agreements, when allocating responsibility for end-customer support between a supplier and a reseller. See generally, e.g.: • Chrissy Kidd and Joe Hertvik, IT Support Levels Clearly Explained: L1, L2, L3, and More (BMC.com 2019); • Wikipedia, Technical support.

13.15. Sales-Channel Partnerships General Provisions

For many companies that sell things, the so-called "sales channel" is an important aspect of business; this Protocol sets out typical ground rules. The term "the channel" is sometimes used as a generic descriptor of a supplier's arrangements with resellers; service providers; value-added resellers (a.k.a. VARs); distributors; wholesalers; brokers; agents; and perhaps referral sources.25 This Protocol sets out ground rules that would be common to both reseller agreements (13.11) and referral agreements (13.10).

13.15.1. Parties: Vendor and Partner

This Protocol will apply in any "Channel Partnership," that is, any relationship under the Con­tract where:

  1. a party (the "Vendor") is anticipated to be supplying one or more goods (tangible or intangible) and/or services (each, a "Vendor Offering," defined below); and
  2. another party (the "Partner" — that term is used only in a business-colloquial sense, not to signify a partnership in the legal sense) is anticipated to be engaging in a related activity such as, without limitation:

    (a)  acquiring and reselling Vendor Offerings; and/or

    (b).  referring potential customers and/or clients to the Vendor.

Note

In this Protocol we use the term "Partner" in the colloquial sense — as is commonly done in the business world — and not as indicating a general partnership in the legal sense. At least in theory, using the term "channel partner" that could be dangerous, because legally, "general partners" are jointly and severally liable for debts and liabilities that they incur in the course of the partnership's business. For a hypothetical example of such a possibility, see 13.15.32.3.

13.15.2. Definitions: Vendor Offerings; Territory; Partnership Term

  1. The definitions below apply unless clearly agreed otherwise in writing.
  2. "Territory" refers to the city limits of the city of the Partner's initial address for notice, for all markets;
  3. The "Partnership Term":
    1. lasts for two years, beginning on the effective date of the Con­tract and ending at 12:00 midnight the end of the day on the same date the specified period later; and
    2. expires automatically, without extension, unless both parties agree in writing to an extension — but see also the extension option at 13.15.22 below.
  4. "Vendor Offerings" refers to all Vendor products (tangible and intangible) and services that Vendor makes available to be offered in the Territory during the Partnership Term.
Note

().  Subdivision 2: Obviously the geographic- and market-segment limits of the "Territory" would often be a subject for discussion.

Subdivision 3: The desirable initial duration of the Partnership Term will depend on many business- and economic factors, including but not limited to whether the partnership is exclusive. (Some drafters might even want to specify a time zone in which the Partnership Term ends.)

Pro tip: If the Vendor provides a broad range of products and/or services, it might make business sense to limit the Partner's rights so that the Partner will focus on a particular Vendor product- or service line.

13.15.3. The Partner has no exclusive rights.

  1. Unless clearly agreed otherwise in writing, the Partner does not have any kind of exclusivity in the Channel Partnership.
  2. Protocol 3.5 (exclusivity explicitness requirement) is incorporated by reference.
Note

Drafters should be sure to review the commentary about exclusivity at Protocol 3.5.

13.15.4. Partner is not a Vendor agent

Unless clearly agreed otherwise in writing, the Partner: (A) is not the Vendor's agent, and (B) must conduct itself accordingly.

Note

It'd be a significant decision for the Vendor to designate the Partner as the Vendor's "agent, as discussed at 13.15.32.2.

13.15.5. Partner confidentiality obligations

  1. The Partner must preserve in confidence any non-public confidential information of the Vendor to which the Partner gains access under the Con­tract.
  2. The economic terms of the Channel Partnership (for example, if the Partner gets a discount from the Vendor) are the Vendor's confidential information (and not necessarily the only such information).
  3. The Vendor does not have confidentiality obligations about the Partner's information unless clearly agreed otherwise in writing.
Note

The Vendor might provide the Partner with confidential information about (for example) the Vendor's future plans — the Partner should expect to have to keep such information in confidence.

Subdivision 2: The Vendor likely wouldn't want others — including but not limited to other actual- or prospective channel partners, as well as prospective customers — to know what kind of business deal the Vendor made with the Partner, e.g.: • what discount the Vendor is giving to a reseller Partner — see Protocol 13.11 (reseller protocol); or • what commission the Vendor will be paying to a referral Partner — see Protocol 13.10.

Subdivision 3: In some channel-partnership relationships, the Partner might provide the Vendor with the Partner's own confidential information — in such a case, the Partner would likely want to negotiate appropriate confidentiality provisions such as those of Protocol 5.3.

13.15.6. The parties will publicly say only certain things about their dealings.

The Partner and the Vendor are each free to publicly disclose the fact that the parties are in the Channel Partnership, but only as follows:

  1. only during the Partnership Term;
  2. only in an accurate, non-misleading way; and
  3. only without disclosing confidential information subject to the confidentiality provisions of the Con­tract.
Note

().  Subdivision 1 It's not unheard of for a former channel partner to continue holding itself out as such, notwithstanding that the vendor had terminated the relationship; this language gives each party an explicit contractual requirement to enforce in such a case. Example: BindView once had to deal with such a situation: We had terminated our relationship with a European reseller, but the reseller continued to hold itself out as (supposedly) still representing us. (A polite but firm letter resolved the matter.)

Subdivision 2: Example: A "reseller" purchased a manufacturer's battery chargers and resold them on Amazon — falsely identifying itself to Amazon as the manufacturer's authorized reseller. See NOCO Co. v. OJ Commerce, LLC, 35 F.4th 475 (6th Cir. 2022).

13.15.7. The Reseller will use only Vendor trademarks for Vendor Offerings.

  1. In referring to Vendor Offerings, the Partner will use only Vendor-designated logos, trademarks, service marks, and/or trade names (collectively, "marks").
  2. In case of doubt: The Partner will use the Vendor's marks:
    1. only during the Partnership Term;
    2. only to identify Vendor Offerings; and
    3. in accordance with any commercially-reasonable instructions that the Vendor provides concerning use of the Vendor's marks — or if the Vendor does not provide such instructions, then the Vendor will use those marks in a commercially-reasonable manner.
Note

().  Background: In some commercial arrangements, the Vendor might provide "white-label" products to the Partner that the Partner sells under its own brand, but any such arrangement should be specifically agreed to in writing. See generally White-label product (Wikipedia.org).

Subdivision 2: Under trademark law, the Vendor must "police" others' use of the Vendor's trademarks, etc.; this section accordingly puts "fences" around the Partner's right to use those marks. (Related reading: Protocol 23.2 – trademark license protocol.)

13.15.8. The Vendor will handle its end-customer warranty obligations.

The Vendor will handle — at the Vendor's own expense — all aspects of end-customers' claims under the Vendor's warranties for Vendor Offerings, unless clearly agreed otherwise.

Note

The Partner likely would be less than eager to deal in the Vendor's goods or services, or to make referrals to the Vendor, if there was any significant chance that the Partner could be sued by end customers because the Vendor breached one of the Vendor's warranties; hence, this section.

13.15.9. The Partner has no power to expand the Vendor's warranties.

The Partner will not purport — on the Vendor's behalf — to expand or extend any Vendor warranty-like obligations for Vendor Offerings.

Note

The Partner could offer its own warranties to the Partner's customers, as a kind of value-add. That's because a "warranty" is really just a conditional covenant — that is, a promise that if the warranted thing turns out not to be true, then the warranting party will take specified action. • For further reading about warranties in general, see 31.40.3.

13.15.10. The Con­tract could set out Partner performance standards.

The Con­tract (or other written agreement) could set forth minimum performance standards that the Partner will meet.

13.15.11. The Vendor has options if the Partner does not meet performance standards.

If the Partner fails to meet any agreed performance standard, THEN: The Vendor is free, in its sole discretion (defined at Protocol 9.6), to do one or more of the following, in any sequence and/or in any combination:

Note

For an extended discussion of possible Partner performance standards — and the business downside of keeping the Channel Partnership active, but in a non-exclusive status — see the appendix at 13.15.32.4.

  1. put the Partner on a performance-improvement plan (see generally Protocol 15.6);
  2. wholly- or partly end the Partner's exclusivity — if any (see § 13.15.3);
  3. temporarily- or permanently reduce the Partner's rights, and/or the Territory (if any); and/or
  4. terminate the Channel Partnership, either immediately or triggered by the Partner's not achieving goals specified in a performance-improvement plan — in case of doubt, such a termination would not be "at will" or "for convenience" (see generally § 13.15.26).

13.15.12. Vendor changes to its line of offerings

  1. The Vendor is free to add to, modify — and/or cease to offer — one or more of the Vendor Offerings at any time in the Vendor's sole discretion.
  2. The Vendor may solicit the Partner's input in about Vendor Offerings, but the Vendor is not obligated to do so.
  3. For the avoidance of doubt: The Vendor would have no liability to the Partner for any change that the Vendor made to one or more Vendor Offerings or to the Vendor's line of offerings, unless the change breached an express requirement of the Con­tract.
Note

().  Some might assume that of course the Vendor can make changes to its line of offerings. But a creative lawyer for the Partner might try to argue that the Vendor was somehow obligated to obtain the Partner's consent — which the Partner might be happy to grant in return for cough a modest payment or other concessions.

Consultation about change is (usually) a Good Thing. But not consulting shouldn't be a breach, absent a clear agreement otherwise.

13.15.13. Vendor control of its sales negotiations

  1. The Vendor will controls its sales negotiations with the Vendor's own customers.
  2. Any assistance that the Partner might provide in any such Vendor negotiations would be:
    1. only at, and solely to the extent of, the Vendor's request and direction;
    2. at the Partner's own expense and risk; and
    3. without additional compensation to the Partner..
Note

().  This section would apply mainly when the Channel Partnership involves Partner making referrals to the Vendor. If the Partner is a reseller of Vendor Offerings, then presumably the Partner would control its own sales negotiations.

In some cases, the Vendor might positively welcome the Partner's assistance in making a sale. But: The Vendor will still want the right to determine whether — and to what extent — the Partner will provide such assistance.

13.15.14. The Reseller is pass along any feedback about Vendor Offerings

  1. The Partner will pass on to the Vendor any feedback that the Partner receives — or conceives — about Vendor Offerings.
  2. For purposes of this Protocol, "feedback" refers to any and all suggestions, comments, opinions, ideas, or other input:
    1. concerning any Vendor Offering, and/or
    2. for additions, deletions, improvements, or other changes, to some or all of Vendor's line of offerings.
Note

Feedback from "the channel" can be extremely important in helping the Vendor to improve Vendor Offerings; such feedback might come from the Partner or from end-customers.

13.15.15. The Vendor may use feedback (or not).

The Vendor is free to use, or not, any or all feedback (defined at § 13.15.14) as the Vendor sees fit, without obligation — financial or otherwise — to the Partner.

Note

Pro tip: The Vendor will want to keep in mind the possibility that in some circumstances, third parties might have intellectual-property rights in feedback ideas, such as: • copyright; • patent rights; • trade-secret rights (see Protocol 5.3), although that seems unlikely unless the Vendor has entered into some kind of confidentiality agreement that benefits the third party.

Note

13.15.16. The Vendor will not attribute Partner feedback to the Partner.

The Vendor will not identify the Partner as a source of feedback (defined at § 13.15.14), nor imply that the Partner endorses the Vendor or any Vendor Offering, without the Partner's prior written consent.

13.15.17. Each party will comply with applicable law.

The Partner and the Vendor will each comply with applicable law whenever engaging in Channel Partnership-related activities that could affect the other party.

Note

If the Partner claimed that the Vendor allegedly failed to comply with some applicable law — or vice versa — the claimant would still have to prove that it was harmed by the noncompliance ("no harm, no foul").

13.15.18. Each party is responsible for certain third-party claims.

  1. The Partner and the Vendor must defend and indemnify each other and each other's Protected Group against third-party claims concerning matters that are the protecting party's responsibility under this Protocol.
  2. For the avoidance of doubt: For this purpose, the term "third-party claims" includes, without limitation, claims by employees and by government authorities.
Note

().  This section would apply if a third party were to make a claim against the Vendor or the Partner where the claim is based on what the third party asserted was: (i) some fault, of any kind, or (ii) strict liability, in either case on the part of the other party. This is a fairly-standard arrangement — but in some one-sided agreements, only one party is obligated to defend (and, often, indemnify) the other party.

As with any indemnity- or defense obligation, the protected party should consider bargaining to require the defending party to maintain appropriate insurance coverage as a "backup pot of money" to cover that obligation.

(Here's a mnemonic, adapted from the military's vulgar update to "R&R," rest and recuperation: "I&I" — whenever you see indemnify, always think at least briefly about insurance.)

13.15.19. No subpartners without Vendor consent

  1. Without the Vendor's prior written consent, the Partner must not purport to engage any "subpartner" — namely, any individual or organization that, under contract with the Partner, would carry out some or all of the Partner's obligations, and/or exercise some or all of the Partner's rights, under the Con­tract. (The Partner's own officers and employees do not count as partners.)
  2. The Vendor is free to grant or withhold such consent in its sole discretion (defined at Protocol 9.6).
  3. Protocol 12.2 (consent requests) is incorporated by reference into this § 13.15.19.
Note

().  Subdivision 2: Whether or not to allow the Partner to engage subpartners at all — and if so, which subpartners — is something over which the Vendor is likely to want to maintain fairly-tight control. That's because the Vendor's public image could be affected by a subpartner's actions or inactions.

Pro tip: The Vendor might want to do at least some due diligence on a prospective subpartner — so whenever requesting the Vendor's consent to the appointment of a prospective subpartner (a "prospect"), the Partner should typically expect to be asked to provide the Vendor with the following information: • the identity of the prospect; • evidence that the prospect has sufficient training and experience to carry out its duties as a subpartner in a manner that wouldn't reflect adversely on the Vendor; and • such background information about the prospect as the Vendor might reasonably request; this could include, for example, the results of a background check, if so requested by the Vendor.

13.15.20. Option: Partner Marketing Consultation Requirement

To reduce the chances of mutual interference between the Vendor's and the Partner's marketing activities, the Partner will consult the Vendor in advance about the Partner's proposed marketing activities concerning Vendor Offerings.

Note

Note that this Option requires only advance consultation, not advance approval.

13.15.21. Option: Termination as EXCLUSIVE Remedy

  1. The Vendor's right to terminate the Channel Partnership is the Vendor's EXCLUSIVE REMEDY for any failure by Partner to meet the agreed performance requirements (after any agreed cure- or performance-improvement period).
  2. The Partner will not assert otherwise.
Note

See the commentary at 21.18.6.

13.15.22. Option: Automatic One Year Opt-Out Extensions

  1. The Partnership Term will be automatically extended for an unlimited number of successive "evergreen" extension periods, each of the stated time, or as otherwise clearly agreed in writing.
  2. If not otherwise agreed, this Option is "opt-out"; that is, either party may cancel an automatic extension, on or before the Partnership Term's then-current expiration date, in accordance with Protocol 15.5.
  3. But: If the parties agree in writing that this Option is to be "opt-in" (e.g., by so stating in the Con­tract), then the automatic extension will occur only if either party gives the other party written notice to that effect; the notice must be effective on or before the Partnership Term's then-current expiration date.
Note

Pro tip: As with any automatic extension, parties should be sure to calendar the opt-out or opt-in deadline. Otherwise, a party could find itself stuck in a relationship that it would really have preferred to walk away from, as discussed in the commentary at 15.5.11.3.

13.15.23. Option: Partner Customer Data Reports

  1. At the times stated in subdivision 2 of this Option, the Partner must provide the Vendor with complete and accurate data about the Partner's transactions and prospective transactions involving Vendor Offerings.
  2. Unless otherwise agreed in writing, the Partner must provide such data:
    1. no later than 30 days after the end of each calendar quarter;
    2. whenever reasonably requested by the Vendor from time to time; and
    3. at the end of the Partnership Term.
  3. In case of doubt: The Partner's obligations in this Option are subject to any restrictions imposed by law (for example, privacy laws).
Note

().  In the modern economy, customer data can be invaluable to manufacturers and others in the supply chain (or, really, the supply web). The Vendor therefore might want to try to get the Partner to agree to something like this Option. But: If the Vendor has other [legitimate] ways of obtaining data from the Partner's customers — e.g., software onboarding; warranty registrations; frequent-user clubs; and the like — then the Vendor might not need to get the Partner to commit to providing customer data.

Subdivision 1: The phrase complete and accurate is used instead of true and correct, for reasons discussed at 32.38.

13.15.24. Option: Partner's Extra-Territorial Restrictions

[EDIT TO SUIT:] During the Partnership Term, the Partner will not do any of the following:

Note

If the Partner's Territory (see 13.15.2) will be limited, then it might be well for the Con­tract to explicitly prohibit activity by the Partner outside that Territory — but it might require discussion whether such a prohibition would be workable for the Partner from a business perspective. ¶ The parties might want to discuss whether any post-term restrictions would be appropriate — and legally binding. (See the discussion of noncompetition covenants at 13.15.25.)

  1. solicit sales to, or provide support for, any customer for Vendor Offerings if that customer has significant operations outside the Territory;
  2. establish or maintain facilities for supporting customers' use of Vendor Offerings if such use is reasonably likely to occur outside the Territory; or
  3. make any Vendor Offering available to any individual or organization if the Partner knows, or reasonably should know, that the Vendor Offering will be taken, installed, or used outside the Territory.

13.15.25. Option: Partner's Noncompete

  1. Both during and for one year after the end of the Partnership Term, the Partner will not participate in, nor acquire any interest in, any enterprise that offers or promotes a product or service that competes within the Territory with any Vendor Offering, unless the Vendor gives its prior written consent.
  2. Protocol 22.5 (noncompete protocol) is incorporated by reference.
Note

Caution: Noncompetion covenants can be tricky and definitely should not be adopted without legal advice — not least because in some circumstances a noncompete can lead to trouble for the party that putatively benefits from it — but the above is a bare-bones version. (For a bit more information about noncompetes, see the commentary to Protocol 22.5.)

13.15.26. Option: Termination at Will Restrictions

  1. Beginning one year after the effective date of the Con­tract, either party is free to terminate the Channel Partnership at will upon 30 days' notice in accordance with Protocol 18.2 unless the Con­tract — or applicable law — clearly provides otherwise.
  2. Otherwise, neither party may terminate the Channel Partnership "at will" or "for convenience."
Note

().  In some contracts, this Option might not be needed. That's because under the law in many jurisdictions, "a contract of indefinite duration is terminable at will unless the contract states expressly and unequivocally that the parties intend to be perpetually bound." Compania Embotelladora Del Pacifico, S.A. v. Pepsi Cola Co., 979 F.3d 239, 245, 246 (2d Cir. 2020) (affirming summary judgment in favor of PepsiCo) (cleaned up, citations omitted, emphasis and extra paragraphing added). To similar effect, see also, e.g., Glacial Plains Coop. v. Chippewa Valley Ethanol Co., 912 N.W.2d 233, 236 (Minn. 2018) (reversing lower courts).

Subdivision 2 — caution: If one party is going to have the right to terminate the Channel Partnership at will, the other party should carefully consider putting appropriate "fences" around that right, so that the other party does not: • get caught unawares and left in the lurch, and/or • not be able to recoup its investment in the relationship. (For additional discussion about some of the business implications of termination at will, see the commentary to Protocol 18.2.)

Caution: The Vendor should keep in mind that in some jurisdictions, the law prohibits a manufacturer from terminating certain dealerships without "good cause." For example, in Texas, see the Fair Practices of Equipment Manufacturers, Distributors, Wholesalers, and Dealers Act; Section 57.154 of that statute provides something of a "safe harbor" list of things that are deemed to constitute good cause, as well as a short list of things that are not good cause. See Tex. Bus. & Com. Code § 57.153, discussed in Fire Protection Service, Inc. v. Survitec Survival Products, Inc., 649 S.W.3d 197 (Tex. 2022) (on certification from 5th Cir.; statute did not violate Texas constitution's prohibition of retroactive laws).

13.15.27. Option: No Termination at Will

Neither party may terminate the Channel Partnership "at will" or "for convenience" unless the Con­tract clearly provides otherwise.

Note

See the commentary at 13.15.26.

13.15.28. Option: WAIVER of Franchise Laws

  1. In entering into the Con­tract, no party intends to create a relationship that would be subject to laws governing franchises and/or business opportunities.
  2. In connection with the Con­tract, each party WAIVES any rights or claims under laws governing franchises and business opportunities or similar laws.
Note

Caution: In some jurisdictions, this purported waiver will be unenforceable or even void; see, e.g., Cal. Corp. Code § 31512: "Any condition, stipulation or provision purporting to bind any person acquiring any franchise to waive compliance with any provision of this law or any rule or order hereunder is void." (Even so, language like this clause is sometimes seen in contracts.)

13.15.29. Option: Unapproved Subcontractors

The Partner will not engage subcontractors without the Vendor's prior written authorization, which the Vendor is free to grant or withhold in its sole discretion (defined at Protocol 9.6).

Note

For additional discussion about subcontractors, see 31.43.

13.15.30. Option: Acceptable Subcontractor Agreements

  1. The Partner will enter into a subcontractor agreement with each (if any) subcontractor.
  2. Each such subcontractor agreement is to do at least the following:
    1. impose at least the same restrictions and obligations on the subcontractor as the Con­tract does on the Partner — this would normally include, without limitation, prohibiting the subcontractor from appointing sub-subcontractors without the Vendor's prior written consent;
    2. unambiguously state that the Vendor will have no liability to the subcontractor in connection with the subcontractor agreement;
    3. terminate automatically, without the need for action by the Vendor, at the end of the Partnership Term; and
    4. unambiguously state that the Vendor is a third-party beneficiary of the subcontractor agreement.
  3. For the avoidance of doubt: If the Vendor reviews and/or approves any form of subcontractor agreement, it will be solely for the Vendor's own benefit and not that of the Partner, the subcontractor, or any other individual or organization.
Note

Concerning third-party beneficiaries in general, see Protocol 11.8.

Note

13.15.31. Option: Partner's Subcontractor Responsibility

  1. As between the Partner and the Vendor, the Partner is solely responsible for all aspects of each of the Partner's subcontractor agreements.
  2. The Partner will defend and indemnify the Vendor and the Vendor's Protected Group against any claim by:

    1. a subcontractor, and/or
    2. any other third party,

    in either case where the claim arises out of acts or omissions of any party to a subcontractor agreement — other than a claim (if any) that the Con­tract unambiguously makes the responsibility of the Vendor.

Note

().  The Vendor won't want to be dragged into disputes between the Partner and its subpartners — or between subpartners and third parties, such as end customers — so this section requires the Partner to handle any such disputes on its own.

Pro tip: Insurance? As with any indemnity obligation, the Vendor should consider proposing that the Partner must maintain insurance (see 31.21) as backup funding (see 4.4) for the obligation.

13.15.32. Sales channel: Additional notes

13.15.32.1. The Vendor and Partner will want to do business planning:

Ideally, the Con­tract should spell out, for example, whether the Partner will do one or more of the following:

  • act in a sales capacity such as (for example) a reseller, distributor, wholesaler, or broker for the Vendor; and/or
  • refer one or more potential customers to the Vendor and/or to the Vendor's designee.

For a fairly-detailed list of specific business issues to consider negotiating, see an article by two lawyers from a Northern California law firm that apparently represents participants in the wine industry — the article focuses on wine distribution channels, but the general principles will very-likely apply broadly to just about any product channel. See Nate Garhart and Matthew Lewis, Life Is Too Short for Bad Wine Distribution Agreements: 10 Key Considerations (JDSupra.com 2023).

13.15.32.2. An "agent" Partner would have significant authority for the Vendor.

().  In some types of channel partnerships, the general idea would be for the Partner to act as the Vendor's "agent" in the Territory — but that could have significant legal consequences, such as:

  • The Partner might well have the legal authority to act in the Vendor's name and to make commitments that were binding on the Vendor.

    Example: A sales agent in Mexico, employed by a New York-based exporter, accepted cash payments from a exporter customer in Mexico but failed to forward hundreds of thousands of dollars of those payments — and a jury question existed whether the sales agent had authority, on behalf of the exporter, to modify or waive a written contract requirement that the customer's payments be wired to the exporter in New York (not paid in cash). See Vista Food Exchange, Inc. v. Comercial de Alimentos Sanchez, No. 22-2660, part II.C.1, slip op. at 35 et seq. (2d Cir. Jul. 24, 2025) (reversing and remanding, in part, summary judgment dismissing exporter's breach-of-contract case against customer).

  • The Vendor could be "vicariously liable" for the agent-Partner's acts and omissions.

    See also 3.8.2 for Partner activities that could be inconsistent with this requirement.

13.15.32.3. "Channel partner" - a dangerous name? (Maybe not.)

Here's a hypothetical example:

  • Fred signs up Ginger to be a reseller of Fred's widgets.
  • On his Website, Fred refers to Ginger as one of his "channel partners."
  • At a time that Ginger is engaged in promoting Fred's products, she gets into a traffic accident and injures a third party, Thierry.

Of course, Thierry might sue Ginger, but if Fred has more money than Ginger, then Thierry's lawyer might also try to sue Fred for what Ginger did. Thierry's likely legal theory would be that when Fred publicly referred to Ginger as a "channel partner," it had the effect of an admission by Fred that Fred and Ginger were legally in a "partnership," and therefore Fred was jointly and severally liable for the harm that Ginger caused whenever she took action in connection with the partnership's business.

Houston lawyer Temi Siyanbade offers another example: Suppose that "Susie" and "Bob" go into business as partners, and (without Susie's knowledge) Bob buys a car under the business name. If Bob falls behind on the payments, Susie likely would be responsible for the payments. Temi Siyanbade, Eliminate this P-word from Your Business Vocabulary (or Use Protection) (toslegal.com 2017).

On the other hand, the present author has never heard of a case (and cursory research found none) in which the term "channel partner" led to liability.

For the risk-averse, the term "channel associate" might theoretically be safer — but that term seems to be more of a mouthful, and so people might be less likely to use it than simply "partner."

13.15.32.4. Appendix: Possible minimum Partner performance standards

().  Reseller agreements, referral agreements, and other channel-partner contracts sometimes set forth minimum performance requirements for the channel partner. That's because the Vendor likely wouldn't want to continue the relationship if the Partner wasn't performing.

Some examples of possible performance standards include the following:

  • minimum number of customers successfully closed by the Vendor or Partner, to promote market penetration for the Vendor's products and/or services;
  • minimum dollar volume of actual sales, to end customers, of the Vendor's offerings;
  • minimum dollar revenue to the Vendor in a stated period — such a provision likely would also say that, if the Partner didn't successfully make its dollar-revenue quota for the period, then Partner could simply write a check to the Vendor for the difference; this could be thought of as a type of "take or pay" arrangement; see generally Take or Pay (Investopedia.com). Caution: Take-or-pay can be disadvantageous to the Vendor, as discussed at 31.38.1;
  • sending X number of the Partner's people to the Vendor's sales training;
  • attending X number of industry events per quarter or per year;
  • hosting X number of marketing-related events;
  • using commercially-reasonable efforts in promoting sales of Vendor Offerings within the Territory.

Ideally, the Con­tract should specify what would happen if the Partner were to fail to perform to agreed performance requirements — this could include, for example (and after any cure period specified in the Con­tract), the Vendor's having the right (by notice) to terminate the Channel Partnership, and with it, the Partner's rights (on a going-forward basis.

Pro tip: The Vendor should keep in mind that it might want to grant some other partner an exclusive right in the Territory — but if the Vendor were to terminate Partner A and then sign a deal with Partner B, the terminated Partner A could claim that the termination was improper; see 18.9.2.4 for examples of some cases where similar things have happened.

As time goes on, the Partner's performance standards could be made more stringent, to provide the Partner with an initial "break-in" period.

Performance standards could also provide for additional compensation to the Partner if the Partner overachieves the stated performance targets.

Parties could also consider specifying some kind of performance improvement plan, as provided at Protocol 15.6; this could entail some kind of adjustment to the economics, e.g., a reduction in a reseller's discount or a referral source's commission rate.

14. External threats

14.1. Defense Against Claims Procedure Protocol

(See also Indemnity Procedure Protocol (14.3).)

14.1.1. Applicability of this Protocol

When this Protocol is agreed to, it will govern when the Con­tract calls:

  • for one party (the "Defender") to defend (equivalently, "provide a defense for")
  • one or more other individuals and/or organizations (each, a "Named Person") that is clearly indicated, expressly or otherwise, in the Con­tract
  • against one or more specified categories of claim by a third party.
Note

().  This Protocol synthesizes language often seen in contracts about how an obligated party is to conduct defense proceedings and/or settlement negotiations.

The Named Person and the categories of claim might be expressly named in the Con­tract, or clearly indicated there by reasonably-specific criteria.

14.1.2. Persons entitled to defense

The Defender is to provide a defense for each of the following individuals and organizations — each, a "person" — as stated in this Protocol; each is referred to (individually) as a "Beneficiary" (sometimes as the Beneficiary):

  1. the Named Person;
  2. each affiliate of the Named Person, if any; and
  3. for each person within subdivisions 1 and/or 2: Each of that person's respective employees, officers, directors, shareholders (in that capacity), general- and limited partners, members, managers, and other persons occupying comparable positions.
Note

This list of Named Persons is fairly standard but might need to be customized for particular situations.

14.1.3. Required: A competent and diligent defense

The Defender is to arrange — at the Defender's own expense — for each Beneficiary to be provided:

  • with a timely, competent, and diligent defense against the claim,
  • by licensed, suitably-experienced and -reputable legal counsel,
  • to whom the Beneficiary doesn't timely object for good reason.
Note

().  The "timely, competent, and diligent defense" requirement simply mirrors the general legal-ethics rules for lawyers.

The "licensed, suitably-experienced and -reputable" language is vague, but it implicitly warns that, say, a traffic-ticket lawyer might not be suitable to defend against, say, a "bet the product line" warranty claim.

14.1.4. Control of the defense

If the Defender advises the Beneficiary (whether explicitly or implicitly) that it will provide a defense, THEN: The Defender will have the exclusive power and exclusive authority to control the defense of the claim — albeit with some limitations as stated below — for as long as the Defender provides a defense that meets the requirements of this Protocol.

Note

().  If the Defender "steps up" and provides a defense, then the Defender should be able to control the defense. Otherwise, the Beneficiary-hired lawyer — knowing it won't be the Beneficiary that will eventually be paying the bills — might be tempted to put on a costly, overly-thorough ("gold-plated") defense that the lawyer might not have done otherwise.

Example: JPMorgan Chase found itself being billed for some $60 million for the legal fees of a woman who was sentenced to seven years in prison for defrauding JPMorgan when she sold her company to the bank. As the NY Times reported: "JPMorgan said in a filing last month that Ms. Javice engaged five separate law firms, and that she and her lawyers have treated the original ruling forcing the bank to pay for her defense as a 'blank check to bill and expense whatever they please.' The stable of lawyers that she has used have also represented Elon Musk, Harvey Weinstein and Sam Bankman-Fried." Ron Lieber, She Took JPMorgan for $175 Million. That Doesn’t Include Her Restaurant Bills. (NYTimes.com Nov. 14, 2025).

This section doesn't require the Beneficiary to formally tender the defense to the Defender. Relatedly, in Johansen (1st Cir. 2024) a contract's defense provision required only "the opportunity for complete control of the defense and settlement thereof by the indemnifying party[.]" Johansen v. Liberty Mutual Ins. Co., 118 F.4th 142, 150 (1st Cir. 2024) (affirming grant of Liberty Mutual motion for summary judgment; cleaned up, citations omitted).

14.1.5. Can the Beneficiary involve its own lawyers?

The Beneficiary has the right to use separate counsel to monitor the defense. If the Beneficiary does so, then:

  1. the Beneficiary and the Defender are to instruct their respective counsel to provide reasonable cooperation with each other in the defense; and
  2. the Defender will not be responsible for any fees, expenses, or professional performance by the Beneficiary's counsel except as provided at § 14.1.6 below.
Note

().  In many cases where the Defender must defend the Beneficiary:

  • The Defender is likely to want to have its own regular legal counsel be the ones to represent the Beneficiary and run the defense.
  • But the Beneficiary might reasonably want its own counsel to keep an eye on what the Defender's lawyers are doing — even though, under legal ethics in the U.S. (and probably in other jurisdictions as well), an attorney's loyalty is owed to the client, not to a third party that's paying the bills, so that the Defender's legal counsel will be ethically obligated to be loyal to the Beneficiary.

    A different situation would be one in which a conflict of interest exists, discussed just below at 14.1.4.

14.1.6. Could the Beneficiary take over the defense?

  1. If a conflict of interest arises that precludes the Defender's counsel from representing the Beneficiary in the defense, THEN: The Beneficiary has the right to assume control of the defense.
  2. If the Beneficiary does assume control of the defense, THEN: The Defender is to reimburse the Beneficiary for reasonable attorney fees that the Beneficiary incurs in conducting the defense, in accordance with Protocol 4.7 (expense reimbursement).
  3. If the Defender and the Beneficiary do not agree whether a conflict of interest exists, THEN: In the interest of standardization, that question is to be determined in accordance with New York law and legal-ethics rules.
Note

This section is informed by a standard legal-ethics rule (in the U.S.): A's lawyer usually cannot also represent B in the same litigation if the two parties have conflicting interests.

14.1.7. What must the Beneficiary not admit?

  1. The Beneficiary must not admit anything, nor waive any right, that is relevant to the claim, at any time that the Defender has the right to control the defense against the claim, unless the Defender has given its prior written consent.
  2. The Defender is not to unreasonably withhold, delay, or condition its consent to the Beneficiary's admission of facts relevant to the claim.
Note

().  Admissions and stipulations to factual matters can greatly streamline litigation (and arbitration), so factual admissions should be made as required.

On the other hand, admissions as to legal conclusions could seriously screw up the Defender's defense of the Beneficiary and so shouldn't be countenanced without the Defender's consent.

In this Protocol, we intentionally don't address what would happen if the parties couldn't reach agreement about about a Beneficiary request to admit or waive something. That's because the specific circumstances would likely make too big a difference to try to prescribe a rule in the abstract.

14.1.8. Beneficiary: Cooperate in the defense

The Beneficiary is to provide reasonable cooperation with the Defender and the Defender's counsel in defending against the claim as follows:

  1. if, and as reasonably requested by, the Defender;
  2. whether or not the Beneficiary asked for (or even wanted) a defense against the claim; and
  3. including but not limited to providing the Defender and/or the Defender's counsel with all reasonably-requested information.
Note

The reasonableness qualifier here should provide some flexibility for both parties, e.g., to help protect the Beneficiary's attorney-client privilege.

14.1.9. The Defender might have to pick up the Beneficiary's attorney fees

The Defender is to pay (or reimburse) all reasonable attorney fees incurred by the Beneficiary:

  1. in defending against the claim at any time that the Defender does not provide a defense, and/or
  2. in enforcing, against the Defender, the Beneficiary's right to a defense,

except to the extent (if any) stated otherwise in this Protocol or elsewhere in the Con­tract.

Note

The Beneficiary will likely incur attorney fees in defending against the claim if the Defender balks at providing a defense (or simply drags its feet). The Beneficiary will also likely incur attorney fees if the Beneficiary has to take legal action against the Defender for failing to provide a defense. In that situation, the Beneficiary should be able to expect to be made whole by the Defender. This is based on a suggestion in Nicole Leath and Michael Piccolo, Why Attorneys’ Fees Belong in Indemnity Provisions in Commercial Real Estate Contracts (JDSupra.com 2025).

14.1.10. Who pays any resulting monetary awards?

The Defender is to pay any and all final, no-longer-appealable monetary awards, entered against the Beneficiary, resulting from the claim; this includes (but is not limited to) damage awards and attorney-fee awards.

🔘 The Defender has no obligation to pay any monetary award resulting from the claim.

Note

Many Beneficiaries will find Option A to be preferable because it gives the Defender an economic incentive to provide a solid defense.

14.1.11. Does the Defender have any other indemnity responsibility?

The Defender's payment obligation under § 14.1.10 does not require the Defender to otherwise reimburse ("indemnify") the Beneficiary for expenses or harm resulting from the claim or adverse judgment.

14.1.12. What if the Beneficiary delays in advising the Defender?

If the Beneficiary does not timely advise the Defender about the claim's existence and provide reasonable details about it, THEN:The Defender is free to take the Beneficiary's delay into account — to a reasonable extent — in conducting the defense.

Note

This is a more-balanced approach than releasing the defense obligation entirely — that can happen, for example, in some insurance policies, in which the Beneficiary (the insured) loses any right to defense or indemnity if the Beneficiary doesn't advise the Defender (the insurance carrier) of the claim within a specified time period (often 30 days).

Example: In a Delaware chancery-court case, the buyer of a company failed to notify the company's sellers of a government claim against the company. The buyer also didn't give the sellers an opportunity to participate in the company's defense against the government's claim. As a result, the buyer was precluded from tapping a $100 million escrow of money from the purchase price, which the parties had set aside to fund payment of indemnified claims. See LPPAS Representative, LLC v. ATH Holding Co., LLC, No. 2020-0241-KSJM (Del. Ch. May 2, 2023) (partially granting, but partially denying, seller's motion summary judgment).

14.1.13. Does it matter if the Beneficiary might be at fault?

Whenever the Con­tract requires the Defender to defend a Beneficiary against third-party claims in particular circumstances, the Defender is to do so:

  1. even if the claim in question allegedly resulted from the Beneficiary's own negligence, and
  2. even if the Beneficiary would not be entitled to indemnity against the claim if the claim were successful.
Note

This section tries to avoid the type of litigation that can result from imprecise contract language — such as happened in a case involving the Omni hotel chain and a valet-parking contractor, concerning a settled personal-injury lawsuit that arose when a customer tripped over a curb. See Caruso v. Omni Hotels Mgmt. Corp., 61 F.4th 215 (1st Cir. 2023) (vacating judgment below and directing entry of judgment for Omni).

14.1.14. What if Beneficiary doesn't want a defense?

  1. This section will apply if the Beneficiary:
    1. declines a defense;
    2. does not ask for a defense; or
    3. tries to halt or obstruct an in-progress defense, against a claim,
  2. In such a situation:
    1. The Defender has the right, in its sole discretion, to defend against the claim anyway, on the same terms as if you'd asked for a defense;
    2. The Beneficiary is to provide the same cooperation with the Defender as though the Beneficiary had asked for a defense; and
    3. The Defender need not indemnify (that is, reimburse) the Beneficiary for harm, losses, or expenses, of any kind, arising from or relating to the claim, even if the Con­tract would have otherwise required indemnity.
Note

().  The Defender might find it desirable to defend the Beneficiary against a claim even if Beneficiary itself was uninterested because the Beneficiary felt it had little or no real skin in the game.

Here's a hypothetical example:

  • A patent owner sues a supplier's customer for using a supplier's products, on grounds that the products supposedly infringe the patent.
  • The customer is indifferent, because the customer can get by without using the supposedly-infringing products.
  • But the supplier might care very much: an adverse judgment in favor of the patent owner might have adverse consequences for the supplier, e.g., under some form of res judicata or collateral estoppel.

So: This section requires the Beneficiary to provide reasonable cooperation in any event. Of course, just what constitutes "reasonable" cooperation might depend in part on the nature and extent of the Beneficiary's potential liability exposure.

14.1.15. Can the Defender settle the claim?

  1. The Defender the right to settle the claim (in whole or in part) on behalf of the Beneficiary, but only as limited by this section.
  2. The Beneficiary will not be bound by any settlement by the Defender if the settlement purports to do any of the following without the Beneficiary's prior written consent:
    1. restricting or placing conditions on the Beneficiary's otherwise-lawful activities; or
    2. requiring the Beneficiary to take any action — other than making one or more payments of money to one or more third parties, where the Defender fully funds each such payment in advance, with no recourse against the Beneficiary; or
    3. encumbering any of the Beneficiary's assets; or
    4. including or requiring any admission or other statement on the Beneficiary's part; or
    5. calling for the entry of a judgment inconsistent with any of subdivisions 1 through 4 above. (Concerning consent judgments, see also § 14.1.16 below)
Note

().  Some contracts — especially insurance policies — give the "Defender" (the insurance carrier) essentially complete control over settlement of third-party claims. That could result in the carrier's settling a claim for terms that the carrier found acceptable, THEN seeking repayment from the protected person, who, ahem, might have a very-different view of the settlement's acceptability. See, e.g., Hanover Ins. Co. v. Northern Building Co., 891 F. Supp. 2d 1019, 1026 (N.D. Ill. 2012) (granting summary judgment awarding damages and attorney fees to insurance company), aff'd, 751 F.3d 788 (7th Cir. 2014).

Obviously, this has considerable potential for a conflict of interest, so this Protocol puts fences around the Defender's ability to settle a claim.

14.1.16. Can the Defender agree to a consent judgment?

The Defender is free to agree to a consent judgment on the Beneficiary's behalf, as part of a settlement with the claimant, but only if the consent judgment does not contain any term inconsistent with the restrictions on on the Defender's settlement authority in section  14.1.15.

Note

In intellectual-property cases, the settlement of a claim will sometimes include the entry of a consent judgment, which typically is a settlement agreement that is "acknowledged in open court and ordered to be recorded, but it binds the parties as fully as other judgments" — meaning the possibility of contempt-of-court sanctions for noncompliance. See Judgment (under the subheading consent judgment), Black's Law Dictionary 1007 (11th ed. 2019); see generally, e.g., Herbert Hovenkamp, Mark Janis, and Mark A. Lemley, Anticompetitive Settlement of Intellectual Property Disputes, 87 Minn. L. Rev. 1719 (2003).

14.1.17. Can the Beneficiary settle the claim?

The Beneficiary has the right to settle the claim, but if the Beneficiary does so without the Defender's prior written consent, THEN: The Beneficiary will have WAIVED, and RELEASED the Defender from, any further defense- or indemnity obligations to the Beneficiary for that claim unless the Defender unreasonably withheld its consent to the settlement.

14.1.18. Are there limits on the Defender's obligations?

The Defender's obligations under this Protocol are subject to the same exclusions and limitations as those stated in Protocol 14.3.

14.1.19. Additional notes

14.1.19.1. Demands for defense can pop up unexpectedly

Contractual defense obligations can become especially important if a catastrophic event occurs, such as an oil-well blowout — and if the relevant contract has been assigned (see 15.3), then things can get even more, let's just say, interesting — see, e.g., the contract diagram reproduced in a Fifth Circuit opinion in the aftermath of a catastrophic 2013 oil-well blowout in the Gulf of Mexico. See Certain Underwriters at Lloyd’s, London v. Axon Pressure Prods. Inc., 951 F.3d 248 (5th Cir. 2020). ].

14.1.19.2. Hypothetical examples of defense obligation

Here are a couple of hypothetical but typical examples of contractual defense obligations:

1.  A customer sends a vendor a purchase order for specified goods. The purchase order's detailed terms and conditions require the vendor to defend the customer against any claim that the goods infringe the intellectual-property rights of any third party.

2.  A master services agreement calls for the service provider to conduct background checks on certain provider personnel. The agreement states that the provider must defend the customer against any claim that a background check was conducted in a way that violated applicable privacy law.

14.2. Force Majeure Protocol

In limited circumstances, the law allows parties to contracts to invoke the doctrine of "force majeure" as defenses to excuse their failure to timely meet their contractual commitments. This Protocol establishes a procedure for parties to do so.

Caution: Force majeure is an area where the law can vary, so contract drafters should be familiar with recent developments in the law — or consult experienced counsel — especially in the wake of the COVID-19 pandemic and the attendant supply-chain disruptions. See, e.g., Pillsbury Winthrop Shaw Pitman LLP, Tour de Force: Force Majeure in Civil Law Jurisdictions – A Superior Force Majeure Doctrine? (JDSupra.com 2020); Tour de Force: Do the Current Economic Conditions Caused by COVID-19 Constitute a Force Majeure Event? (2020).

14.2.1. Each party can invoke force majeure.

When this Protocol is agreed to, each stated party — referred to in this protocol as the "Affected Party" or "AP" — may assert force majeure, in accordance with this Protocol, to excuse a failure to timely perform the Affected Party's obligations under the Con­tract.

Note

Force-majeure clauses drafted by a vendor or supplier will sometimes protect just the vendor or supplier and not the customer. But this protocol is drafted to be a Freaky Friday clause with the idea that it should work the same way even if the parties were to trade places.

14.2.2. Certain prerequisites must first be met.

The Affected Party will not be liable for not carrying out obligations under the Con­tract if all of the following things are the case:

  1. the Affected Party invokes force majeure as stated in this protocol at a reasonable time — which could be before or after the relevant force majeure situation or -situations, depending on the circumstances;
  2. the Affected Party's nonperformance was actually caused (directly or indirectly) by the force majeure; and
  3. the Con­tract does not specify otherwise for the particular circumstances.
Note

().  Subdivision 1: In some circumstances it might be best for a party to invoke force majeure in advance — for example, if a hurricane were approaching or a pandemic were erupting — to give both parties a chance to prepare and, with any luck, to prevent or at least mitigate the expected ill effects.

Subdivision 2: Example: A California appeals court affirmed a summary judgment that a brew pub couldn't use the COVID-19 pandemic as an excuse for not paying rent to its landlord: the brew pub — which was part of a large chain of restaurants and bars — could have paid its rent notwithstanding the pandemic. West Pueblo Partners, LLC v. Stone Brewing Co., LLC, 90 Cal. App. 5th 1179, 1188-90 (Cal. App. 2023). The court reviewed COVID-era case law from other jurisdictions as well.

Example: Similarly, an appeals court held that a Texas-based natural gas pipeline company would have to prove, at trial, that its curtailment of gas deliveries to a customer had in fact been caused by emergency government orders issued in response to 2021's Winter Storm Uri, which reportedly came within minutes of plunging nearly the entire state of Texas into a weeks-long blackout. The customer asserted that the pipeline company's curtailment had been caused instead by the customer's invocation of its contractual option to sell back its right to the gas deliveries. The customer claimed that because of its sell-back, the pipeline company supposedly owed the customer some $100 million — which the pipeline company had refused to pay, citing force majeure. See Freeport LNG Marketing, LLC v. Kinder Morgan Texas Pipeline LLC, No. 14-22-00864-CV, slip op (Tex. App–Houston [14th Distr.] Apr. 15, 2025) (reversing and remanding summary judgment in favor of pipeline company). Hat tip: J. McLean Bell.

Counterexample: On the other hand, in another case arising from Winter Storm Uri, a federal-court jury in Houston found that natural-gas producer Marathon Oil Company had shown that its failure to deliver gas to Koch Energy Services came within (and was excused by) the contract's force majeure clause. See Press release, AZA Defeats $123.7 Million Breach of Contract Claim in First Major Winter Storm Uri Natural Gas Trading Jury Trial (AZALaw.com May 6, 2025); see also Marathon Oil Co. v. Koch Energy Servs., LLC, No. 4:21-CV-1262 (final judgment); cf. Mieco, L.L.C. v. Pioneer Nat. Resources USA, Inc., 109 F.4th 710, 713-16 (5th Cir. 2024) (affirming district court's interpretation of contract's force-majeure clause as not requiring performance to have been literally impossible, nor as requiring Pioneer to purchase gas on the spot market as opposed to gas it produced itself).

14.2.3. Payment failure will be excused only in certain circumstances.

The Affected Party cannot use force majeure as an excuse for not timely paying an amount due under the Con­tract, unless the Affected Party's failure is or was due to generalized failure — beyond the Affected Party's control — in all reasonably-available payment systems, such as (for example):

  1. all reasonably-available banks are closed by government edict;
  2. all of the following are true: (a) substantially all of the Affected Party's assets that the Affected Party could use for payment are trapped or stranded in one or more failed banks, (b) the Affected Party had no reason to anticipate that this would happen, and (c) the Affected Party could not move enough assets to make the payment; or
  3. substantially all electronic systems generally used for commercial payments are "down" — e.g., ACH and/or SWIFT — whether because of technical reasons, governmental action, sabotage, or other cause. (This must include all systems that the Affected Party normally uses for that purpose.)
Note

().  In the West Pueblo Partners decision cited above, the California appeals court affirmed a summary judgment that a brew pub — which was just a small part of the pub operator's business — "was not delayed or interrupted in its ability to pay rent by its COVID-related financial difficulties." West Pueblo Partners, LLC, supra (emphasis added); cf. Red Tree Investments, LLC v. Petróleos de Venezuela, S.A., 82 F.4th 161, 163, 171 (2d Cir. 2023) (affirming summary judgment, rejecting PDVSA's assertion that its failure to make certain payments, amounting to more than USD $500 million, should be excused because of U.S. sanctions against the company). See also, e.g., the comments to Ken Adams, Excluding from a "Force Majeure" Provision Inability to Comply with a Payment Obligation (Adamsdrafting.com 2012).

Subdivision 1: Generalized bank closings happened, for example, in 1933 during the Great Depression.

Subdivision 2: Trapped- or stranded assets likely happened to some depositors in March 2023, after the failure of the Silicon Valley Bank, among others.

Subdivision 3: In 2015 and 2016, the SWIFT banking network was hacked by a gang of cybercriminals, known as APT 38, resulting in the theft — among others — of more than USD $100 million from the Bangladesh central bank. See generally SWIFT banking hack (Wikipedia.org).

14.2.4. Definition: Force majeure

The term "force majeure" refers to any situation — which could be an event, or a series of related- and/or independent events — in either or both of the following two categories:

  1. the situation is of a specific type listed in the Con­tract as constituting force majeure — if any — or a situation of a similar kind or nature, in any case regardless whether or not the situation was foreseeable at the time the parties entered into the Con­tract; and/or
  2. the situation was unforeseeable at the time the parties entered into the Con­tract, whether or not similar to a specific type that's listed in the Con­tract.
Note

().  This definition is largely based on the general law; it's adapted from a Fifth Circuit approach as adopted by the Texas court of appeals in Houston. See TEC Olmos, LLC v. ConocoPhillips Co., 555 S.W.3d 176, 182 (Tex. App.—Houston [1st Dist.] 2018, pet. denied) (citing cases).] Also, it's intentionally located at the end of this protocol, instead of right at the outset. That's because anecdotal evidence suggests that this can help speed reader comprehension, according to Tim Cummins, the former head of a global association of contract professionals. See Tim Cummins, Change does not have to be complicated (July 21, 2014).

Caution: In New York and possibly in some other jurisdictions, it might be necessary to include a "laundry list" of specific types of situation that the parties intend to qualify as force majeure — and a catch-all such as the "of a similar kind or nature" phrase here might not work. See Kel Kim Corp. v. Central Markets, Inc., 70 N.Y.2d 900, 902-03 (1987) (insurance-industry crisis did not excuse commercial tenant's failure to renew insurance as required by lease), quoted in JN Contemporary Art LLC v. Phillips Auctioneers LLC, 29 F.4th 118, 124 (2d Cir. 2022) (COVID-19 pandemic qualified under contract's force-majeure clause).

Moreover, in New York the force majeure event must actually render performance impossible, not merely uneconomical. See generally Andrew Lucano, Performance under Contracts Governed by New York Law in the Face of the COVID-19 Pandemic (Seyfarth.com 2020). See also the commentary to Protocol 20.25 (meaning of include).

At the invaluable redline.net forum for lawyers, forum moderator Sean Hogle points out that "New York force majeure law for vendors and service providers is brutal. … You need a list. The doctrine will excuse performance under New York law only if the force majeure clause specifically includes the event or occurrence that prevents a party’s performance. Without a list, the clause is basically a dead letter."

14.2.5. Force majeure: Option protocols

14.2.5.1. Option: Similar Defenses Allowed As Well
  1. If this Option is agreed to: The fact that the Affected Party is allowed to invoke force majeure under the Con­tract does not imply that the Affected Party cannot assert an impossibility- or impracticability defense — at least, to the extent that applicable law (common law, statutory, or otherwise) would let the Affected Party do that without the Con­tract's force-majeure provisions. This Option is meant to "write around" the possibility that in some jurisdictions, "the doctrine of impossibility … governs only if the parties have not drafted a specific assignment of the risk otherwise assigned by the provision." Commonwealth Edison Co. v. Allied-General Nuclear Serv., 731 F. Supp. 850, 855 (N.D.Ill. 1990) (Posner, J., sitting by designation). Hat tip: Samuel Mercer.
  2. But: Just because this Option is not agreed to (if that is the case), it does not imply that the parties agreed to preclude the Affected Party from asserting one or more of such defenses.
14.2.5.2. Option: Force-Majeure Termination Right

If this Option is agreed to: Either party may terminate all parties' going-forward obligations under the Con­tract if the aggregate effect of force majeure:

  1. is material in view of the Con­tract as a whole; and
  2. lasts longer than 60 days after a party first duly invoked force majeure.
Note

This limitation is adapted from a master services agreement between IBM and the State of Indiana, which was the subject of extended litigation. See Indiana v. IBM Corp., 51 N.E.3d 150, 153 (Ind. 2016), after remand, 138 N.E.3d 255 (Ind. 2019).

14.2.5.3. Option: Force-Majeure Status Reports
  1. If this Option is agreed to, it will apply if:
    1. a party invokes force majeure; and
    2. another party to the Con­tract, affected by the invocation, requests status updates.
  2. The party invoking force majeure is to provide the requesting party with reasonable information to other parties to the Con­tract — from time to time, as the invoking party reasonably determines — about the invoking party's efforts, if any, to remedy and/or mitigate the effect of the force majeure.
  3. If another party (the "recipient") acquires non-public force-majeure status information from a party invoking force majeure, THEN the recipient is to do the following:
    1. treat that information as the invoking party's confidential information;
    2. use reasonable measures to preserve the secrecy of the information; and
    3. not use the information except in good faith for purposes reasonably relating to the recipient's exercise of its rights, or performance of its obligations, under the Con­tract.
Note

If a supplier invokes force majeure, and as a result the supplier's customers experience disruptions in their own businesses — as happened during the COVID-19 pandemic — then some customers might understandably hope to get periodic status reports from the supplier. Periodic catch-up calls (see Protocol 3.2) can serve that purpose, but some customers might want something more scheduled; this Option offers one possibility.

14.2.5.4. Option: Provider Allocation – Discretion or Proportionality
  1. If this Option is agreed to, it will apply whenever both of the following are true:
    1. under the Con­tract, a party (the "Provider") is required to supply goods or services to another party (the "Customer"); and
    2. the Provider both (1) invokes force majeure, and (2) experiences shipping delays as a result of one or more force-majeure situations, whether or not of the type invoked.
  2. If the Con­tract specifies "Discretion" for this Option, THEN: The Provider is to allocate the Provider's available goods or services to the Customer and its other customers (if any) as the Provider sees fit in its reasonable discretion.
  3. If the Con­tract specifies "Proportional" or "Proportionality" for this Option, THEN: The Provider is to allocate the Provider's available goods or services so that the Customer receives at least the same proportion of those goods and/or services as the Customer would have received in the absence of the force-majeure situation.
Note

().  If a provider suffers shortages because of a force-majeure event, and it has commitments to multiple customers, then how should the provider's available stock (and/or production capacity) be allocated among those customers? This Option allows for two different answers.

It might be a challenge — or simply impracticable — to assess the extent of a provider's compliance with the Proportionality configuration for this Option.

14.2.5.5. Option: Mitigation and Remediation Discretion
  1. When a party invokes force majeure, the other party is not obligated to make any particular efforts to mitigate or remediate the effects of the invoked force majeure.
  2. If the other party does try to mitigate or remediate the effects of force majeure, it will be for that party's benefit only, not that of the invoking party.
Note

().  Note that there are two distinct possibilities presented in this Option: One for mitigation, one for remediation.

Caution: Some customers might want their suppliers to commit to using "best efforts" to mitigate or remediate the effects of force majeure. A supplier, however, might be reluctant to agree to a best-efforts commitment because different courts might define that term in different ways and the likelihood of being second-guessed after the fact, as discussed in the commentary to Protocol  9.1 (best efforts definition). An example of such a force-majeure mitigation commitment can be seen in section 4 of a Honeywell purchase-order form, apparently from February 2014 (archived at https://perma.cc/84BS-KYXB).

14.2.5.6. Option: Extension of Expiring Right

If this Option is agreed to, and one or more properly-invoked force majeure situations make it impracticable or impossible for the invoking party to timely exercise a right under the Con­tract, THEN: The invoking party's time for exercising that right will be deemed extended for the duration of the resulting delay.

Note

This Option addresses what could be regarded (depending on your perspective) as a gap in many force-majeure clauses. Example: New York's highest court held that the force-majeure clause in question "does not modify the habendum clause and, therefore, the leases terminated at the conclusion of their primary terms" despite the occurrence of force majeure. Beardslee v. Inflection Energy, LLC, 25 N.Y.3d 150, 153, 31 N.E.3d 80, 8 N.Y.S.3d 618 (2015) (on certification from Second Circuit).

14.2.5.7. Option: Economic Force-Majeure

If this Option is agreed to, AND: It would be unreasonably costly for an invoking party to avoid (or to have avoided) a failure of timely performance resulting from one or more force-majeure situations, THEN: The invoking party is considered not to be reasonably able to avoid (or to have avoided) the failure.

Note

().  Without this Option, a court might be skeptical about force-majeure claims. Example: A Houston-based court of appeals held that "[b]ecause fluctuations in the oil and gas market are foreseeable as a matter of law, it [sic] cannot be considered a force majeure event unless specifically listed as such in the contract." TEC Olmos, LLC v. ConocoPhillips Co., 555 S.W.3d 176, 184 (Tex. App.—Houston [1st Dist.] 2018, pet. denied) (emphasis added).

For some examples of contract clauses with "economic force-majeure" clauses, see LawInsider.com.

14.2.5.8. Option: Mandatory Advance Alerts of Force Majeure

If this Option is agreed to: Each party is to promptly alert each other party if the former concludes that a substantial risk exists that it might have to invoke force majeure.

Note

Including language like this in a contract might give a counterparty an excuse motivate a counterparty to sue a party that had invoked force majeure, on grounds that the invoking party supposedly hadn't "promptly" alerted the counterparty to the danger.

14.2.5.9. Option: Effect of Subcontractor Failure
  1. If this Option is agreed to, it will apply if:
    1. a party does not timely perform its obligations (or exercise its rights) under the Con­tract; and
    2. the party's failure to do so was due to a failure of a subcontractor or supplier of the party.
  2. The party's performance failure will be excused on force-majeure grounds only if the party shows that both of the following things are true:
    1. the failure by the subcontractor or supplier must otherwise qualify as one or more force-majeure situations under the Con­tract; and
    2. it must not have been reasonably possible for the party to timely obtain, from one or more other sources, the relevant goods or services that were to have been provided by the subcontractor or supplier.
Note

This Option is a limited version of a type of provision seen in some customers' standard terms of purchase: A customer generally won't want to hear that a provider of goods or services failed to perform because of a subcontractor's failure; metaphorically, the customer would likely say, "hey, that's on you, Provider."

14.2.5.10. Option: Detailed List of Possible Force-Majeure Events

If this Option is agreed to, the following (non-exclusive) alphabetical list of event types are conclusively deemed to qualify as force-majeure events unless the Con­tract clearly states otherwise: • Act of a public enemy. Act of any government or regulatory body, whether civil or military, domestic or foreign, not resulting from violation of law by the invoking party. Act of war, whether declared or undeclared, including for example civil war. Act or omission of the other party, other than a material breach of this Agreement. Act or threat of terrorism. • Blockade. Boycott. • Civil disturbance. Court order. • Drought. • Earthquake. Economic condition changes generally. Electrical-power outage. Embargo imposed by a government authority. Epidemic or pandemic. Explosion. • Fire. Flood. • Hurricane. • Insurrection. Internet outage. Invasion.• Labor dispute, including for example strikes, lockouts, work slowdowns, and similar labor unrest or strife. Law change, including any change in constitution, statute, regulation, or binding interpretation. Legal impediment such as an inability to obtain or retain a necessary authorization, license, or permit from a government authority. • Nationalization. • Payment failure resulting from failure of or interruption in one or more third-party payment systems. Public health emergency. • Quarantine. • Riot. • Sabotage. \Solar flare. Storm. Supplier default.• Telecommunications service failure. Tariff imposition. Transportation service unavailability. Tornado. • Weather in general.

Note

().  Some drafters like to list specific types of events that can excuse non-performance. (DCT note: I generally don't do that.) The list above is drawn from various agreements.

Caution: Under New York law, and possibly that of some other jurisdictions, it might be necessary for the Con­tract to include a "laundry list" of specific force-majeure events.

Some of the above items are in bold-faced type because they are not-uncommonly subject to negotiation.

The above list doesn't include the so-called "act of God" because of the vagueness of that term.

Some customers' procurement organizations feel they can push around their suppliers without consequence. For example, in April 2022, "Stellantis' new purchase contracts declare[d] 'all future events are deemed foreseeable' by suppliers, yet require[d] price reductions when any savings are found." Noting this astonishingly-brazen move, a Harvard Business School professor mused, "One has to wonder if anyone could foresee the events of the past two years," i.e., the COVID-19 pandemic and the protracted Russian invasion of Ukraine. Willy C. Shih, In Uncertain Times, Big Companies Need to Take Care of Their Suppliers (HBR.edu 2022).

(Stellantis later backed off and reverted to its previous terms and conditions.) See Stellantis Reverses Course on Contract Terms (UHY-us.com 2022).

The professor continued:

OEMs should recognize that a major benefit of having multiple suppliers is resiliency, and while competition between them will ensure fair pricing, it should not be used as a tool to drive a race to the bottom.

Some firms already have a more enlightened view. For decades, Toyota has ensured that it understands a supplier’s costs and then negotiates prices without repeated rounds of threats. It also works with individual suppliers to improve their productivity and performance.

"You can sit and have conversations. They actually care," the CEO of one [supplier] company told me. "I don’t have the potential to make as much money [with them], but the business is really solid, very stable."

* * *

Healthy suppliers are a big part of a more resilient supply chain — one that can adapt in this rapidly changing world. Willy C. Shih, In Uncertain Times, Big Companies Need to Take Care of Their Suppliers (HBR.edu 2022).

14.3. Indemnity Procedure Protocol

Many, many contracts require one or another party to indemnify another party in specified circumstances. The term means to reimburse for losses and/or expenses; the noun form is indemnity. See generally Indemnify, Black's Law Dictionary 918 (11th ed. 2019).

See also the additional notes at 14.3.13 and Defense Against Claims Procedure Protocol (14.1).

14.3.1. The parties: The Payer and the Beneficiary.

This Protocol will apply whenever the Con­tract requires a party (referred to as the "Payer") to indemnify — that is, to pay or reimburse — another individual or organization (the "Beneficiary") for specified claims, losses, and/or expenses.

Note

Relatedly: Hold harmless is generally regarded as a synonym for indemnify, as discussed in the commentary to Protocol 20.24.

14.3.2. The Con­tract could limit the amount of an indemnity obligation.

Payer: Your financial obligation for indemnity under the Con­tract isn't limited to a particular amount unless the Con­tract clearly says so.

Note

A contractual limitation of liability likely won't limit a contractual indemnity obligation, because the former applies only to breaches of the contract, while the latter is an express obligation under the contract. See David Tollen, Limits of Liability Don’t Work for Indemnities (TechContracts.com 2020).

14.3.3. Payer: Also provide a claim defense.

Payer:

  1. This section will apply if:
    1. the Con­tract requires you to indemnify the Beneficiary for losses and expenses resulting from specified third-party claims; but
    2. the Con­tract is silent about whether you must defend the Beneficiary against such claims.
  2. In those circumstances: Provide the Beneficiary with a defense against the claim, in accordance with Protocol 14.1.
Note

The law, especially in California, might impose a rule like that of this section.26 Other jurisdictions don't, though27 — so the drafter should check the relevant jurisdiction(s).

14.3.4. The Express-Negligence Rule applies.

The Payer doesn't have to indemify (reimburse) the Beneficiary for losses and/or expenses that result from the Beneficiary's own negligence or gross negligence, unless:

  1. the Con­tract expressly and conspicuously says so; and
  2. applicable law doesn't prohibit that kind of indemnity.
Note

().  The Texas supreme court has repeatedly held that:

[An indemnity provision] in a contract which fails to satisfy either of the fair notice requirements when they are imposed is unenforceable as a matter of law.

One fair notice requirement, the express negligence doctrine, requires that the intent of the parties must be specifically stated in the four corners of the contract.

The other requirement, of conspicuousness, mandates that something must appear on the face of the contract to attract the attention of a reasonable person when he looks at it.

Language may satisfy the conspicuousness requirement by appearing in larger type, contrasting colors, or otherwise calling attention to itself.

However, if both contracting parties have actual knowledge of the plan's terms, an agreement can be enforced even if the fair notice requirements were not satisfied. Storage & Processors, Inc. v. Reyes, 134 S.W.3d 190, 192 (Tex. 2004) (affirming court of appeals's reversal of summary judgment in favor of employer: employee's release of claims in benefit plan did not satisfy fair-notice requirements) (cleaned up, lightly edited).)

Some Texas lawyers used the term "express negligence doctrine" as a shorthand expression encompassing both the fair-notice requirements of being express and conspicuous, See, e.g., Byron F. Egan, Indemnification in M&A Transactions for Strict Liability or Indemnitee Negligence: The Express Negligence Doctrine, U. Texas Sch. of Law 10th Annual Mergers & Acquisitions Inst. (2014).] even though case law seems to separate those two requirements. See Dresser Industries, Inc. v. Page Petroleum, Inc., 853 S.W.2d 505, 507 (Tex. 1993) (fair-notice requirement applies to releases as well as to indemnities); Mission Clay Products, LLC v. L.A. Fuller & Sons Constr., Ltd., No. 07-24-00251-CV, slip op. (Tex. App.–Amarillo Jul. 24, 2025) (affirming trial-court holding that indemnity clause was unenforceable).] More recently,

See also the following extended discussions:

  • conspicuousness: 8.1
  • (for Texas students) the Texas Oilfield Anti-Indemnity Act: 14.3.13.11.

14.3.5. An indemnity obligation doesn't cover the Beneficiary's own claims.

An indemnity obligation doesn't obligate the Payer to indemnify (reimburse) the Beneficiary for the Beneficiary's own claims against the Payer (or anyone relating related to the Payer) unless the particular indemnity- or defense language clearly says otherwise.

Note

().  This section is intended to deal with an apparent split in the case law as to whether an indemnity obligation must be "unmistakably clear" that the obligation does or does not cover claims between the parties themselves.28

Caution: Suppose that an indemnity clause provision requires A to indemnify B if A breaches its contract obligations. A court could well hold that the provision was a first-party indemnity clause — at least on the subject of attorney fees.

Example: This happened in a Federal Circuit case where a confidentiality agreement (a.k.a. "NDA") called for the parties to "hold harmless the other against any and all damage, losses or liability (including reasonable attorneys' fees) suffered by the other as a result of any breach of the representations, warranties, and agreements set forth herein." (Emphasis added.) The court affirmed a trial-court holding that this indemnity language — as a so-called first-party clause — overrode the "American Rule" for attorney fees (see Option), allowing the successful plaintiff to recover its attorney fees for pursuing its breach-of-contract claims. See ams-OSRAM USA Inc. v. Renesas Elecs. America Inc., 133 F.4th 1337, 1356 (Fed. Cir. 2025) (affirming trial court's award of attorney fees). (Hat tip: Matt Dedon in a post at the redline.net site.)]

Counterexample: On the other hand, the Tenth Circuit reached the opposite conclusion in a case where the indemnification provision contained similar breach-oriented language. See ORP Surgical, LLC v. Howmedica Osteonics Corp., 92 F.4th 896, 918-21 (10th Cir. 2024) (reversing district court's award of attorney fees; indemnification provision was at best ambiguous about first-party coverage).

14.3.6. The Beneficiary must try to "mitigate" (cut its losses).

The Payer doesn't have to indemnify the Beneficiary for harm to the extent that both of the following are true:

  1. the Beneficiary knew, or should have known, of the possibility of the harm before the harm occurred, and
  2. the Beneficiary have avoided (or mitigated) the harm by commercially-reasonable efforts.
Note

().  The intent of this section is to reduce "moral hazard" by giving the Beneficiary an incentive to take reasonable steps to reduce its damages.

Note: A Beneficiary might be under such an obligation anyway — but the law isn't necessarily clear on that point, as discussed in the commentary to Protocol 14.3.9.

14.3.7. The Payer must pay up promptly.

Payer: Pay each covered loss and expense — or if applicable, reimburse the Beneficiary for the loss or expense — promptly after the Beneficiary presents you with:

  1. a written request for payment or reimbursement, together with
  2. reasonable supporting evidence documenting the existence, nature, and amount of the covered loss or expense.
Note

().  This is intended to discourage a Payer from dragging its feet, possibly in an attempt to gain leverage over the Beneficiary.

Concerning expense reimbursement, see 4.7.

14.3.8. The Payer can audit the Beneficiary's claims.

If the Payer asks, the Beneficiary must allow the Payer to have the Beneficiary's supporting evidence audited in accordance with Protocol.

Note

The supporting-evidence requirement and audit right is basically an anti-fraud measures, as discussed in the commentary to Protocol (audits).

14.3.9. Is anything not reimbursable here?

Unless the Con­tract expressly specifies otherwise, the Payer need not defend or indemnify the Beneficiary against any claim, loss, or expense where one or more of the following is true:

  1. that arises because the Beneficiary is obligated to indemnify and/or defend a third party;
  2. that result from the Beneficiary's gross negligence or willful misconduct;
  3. that fall in the category of consequential damages — that is, atypical damages, i.e., damages that would not have been expected to occur in the usual course — that arise from, or relate to, an otherwise-covered event; and/or
  4. that would have been unforeseeable at the time the parties entered into the Con­tract;
Note

().  Subdivision 1: This might be a point for negotiation.

Subdivision 2 would probably be the default mode under the law in most U.S. jurisdictions. The rationale is that allowing a party to shuck off liability for its own willful misconduct would create moral hazard and be against public policy.

Subdivision 3's exclusion of consequential damages is meant to avoid positioning a reimbursing party as an insurer for another party's unusual losses, etc., unless the parties have affirmatively specified otherwise.

Why include this? Because in Anglo-American jurisprudence, damages for breach of contract are generally limited to those that are not only foreseeable, but within the contemplation of both parties as possibly occurring in the usual course; this section does the same for indemnity obligations. See also the discussion of consequential damages at Protocol 21.5.

Subdivision 4: While liability for breach of contract is generally limited to foreseeable lossses, practitioner-scholar Glenn West has suggested that the same might not be true for a contractual indemnity obligation. See generally Glenn D. West, Consequential Damages Redux …, 70 Bus. Lawyer 971, 998 (Weil.com 2015) ("VI. Overlaying the Concept of Indemnification for Losses on the Contract Damages Regime"), archived at https://perma.cc/D2HC-Z5XD.

14.3.10. It doesn't matter if the Payer wasn't at fault.

The Beneficiary doesn't have to prove that the Payer was negligent (or otherwise at fault) for the Beneficiary to be entitled to payment of, or reimbursement for, a covered loss or expense, unless the indemnity obligation itself, by its clear terms, extends only to the Payer's own negligence or other fault.

Note

This is generally how the law works anyway. See A.M. Welles, Inc. v. Montana Materials, Inc., 2015 MT 38, 378 Mont. 173, 342 P.3d 987, 989, ¶¶ 10-11 (2015) (reversing denial of summary judgment in favor of reimbursed party; citing cases).

14.3.11. The Con­tract could impose an indemnity claim deadline.

If the Payer wants the Beneficiary to have a deadline for making an indemnity claim — or a sunset for the indemnity obligation generally — THEN: The Con­tract must clearly say so.

Note

().  This is a "sunset" provision, akin to how insurance policies frequently include deadlines for the insured to report third-party claims to the insurance carrier.

Example: Such a deadline proved fatal to Harvard University's claim for coverage of some of its legal-defense costs in the famous SFFA litigation, which ultimately led to the Supreme Court's holding that race-based affirmative action in college admissions was a violation of the Equal Protection Clause. See Harvard Coll. v. Zurich American Ins. Co., 77 F.4th 33 (1st Cir. 2023) (affirming summary judgment dismissing Harvard's claim against excess-insurance carrier). Harvard's excess-insurance claim was for expenses incurred in a high-profile case that ended up at the (U.S.) Supreme Court, in Students for Fair Admissions, Inc. v. President & Fellows of Harvard Coll., 600 U.S. 181, 143 S. Ct. 2141 (2023).

Drafters for prospective indemnity beneficiaries should think carefully before agreeing to such a "sunset" date for indemnity obligations; that's especially true for indemnities concerning situations that might not come to light for years, such as claims arising from unseen pollution and other environmental problems. This is discussed in detail in Laurence S. Kirsch and Nathan J. Brodeur, Structuring Corporate and Real Estate Transactions to Minimize Environmental Risk, 60 Conf. Consumer Fin. L. Qtrly Rep. 179, 191 (2006).

14.3.12. The Con­tract could require indemnity-insurance coverage.

Unless the Con­tract clearly says otherwise, the Payer has the right to decide, in the Payer's sole discretion, whether to carry insurance to cover the Payer's indemnity obligation(s) to the Beneficiary under the Con­tract.

Note

().  Any time you propose a clause requiring another party to indemnify your client, it's important to think about whether also to propose asking the other party to agree to maintain insurance (see 31.21) to provide a backup source of funding for the indemnity obligation.

These two subjects, indemnification and insurance — or "I&I" for short — should go hand in hand. (See the bawdy military version of that expression, from what Americans refer to as the Vietnam war.)

Here's why:

  • Suppose that Fred contractually commits to indemnifying Ginger if certain things happen.
  • But when one of those things happen, and Ginger wants Fred to indemnify her, it turns out that Fred has no money or other assets, at least none to which Ginger could successfully lay claim in court.
  • In that situation, Ginger would very likely be unable to get any meaningful compliance from Fred — and she might even have to deal with the challenges of a bankruptcy filing by Fred.

AND: The reverse is true if you're reviewing a clause that would require your client to indemnify another party: Consider suggesting to your client that the client check with its insurance broker, to increase the chances that the client has appropriate coverage — and to reduce the chances that the disgruntled client might sue you for for failing to make that suggestion, hoping to recover from your malpractice insurance.

Caution: As the Fifth Circuit explained: "The Texas Oilfield Anti-Indemnity Act ('TOAIA') voids indemnity agreements that pertain to wells for oil, gas, or water or to mineral mines, unless the indemnity agreement is supported by, inter alia, liability insurance" — and the Payer's liability for indemnity is limited to the dollar amount of insurance that the Payer is contractually required to maintain, even if the Payer happens to maintain more insurance than that. See Cimarex Energy Co. v. CP Well Testing, L.L.C., 26 F. 4th 683, 685 (5th Cir. 2022) (affirming summary judgment in favor of Payer); see also Century Surety Co. v. Colgate Operating, L.L.C., 116 F.4th 345 (5th Cir. 2024), which, according to one commentator, diverges from Cimarex Energy; see Thomas Donaho, The 5th Circuit’s Second Thoughts on Oilfield Indemnity Limitations (JDSupra.com 2025).

Concerning reps and warranties insurance ("RWI"), see generally Maier (2022), which cites some pending litigation in this area. Emily Maier, Reps & Warranties: Spring 2022 Trends to Watch (BusinessLawToday.org 2022).

14.3.13. Additional notes

14.3.13.1. An indemnity obligation should be unmistakably stated

The Second Circuit noted that "New York law requires indemnification agreements to be strictly construed; a court cannot find a duty to indemnify absent manifestation of an unmistakable intention to indemnify." The appeals court concluded that DirecTV was obliged to indemnify a spun-off company for a satellite TV license fee charged by an Indian government agency, because the license fee was an indemnifiable "Tax" as defined in the parties' contract. Hughes Communications India Private Limited v. The DirecTV Group, Inc., 71 F.4th 141, 148 (2d Cir. 2023) (vacating and remanding summary judgment; citations omitted).

14.3.13.2. Caution: Indemnity-trigger wording can be crucial

An indemnification provision might be worded in such a way as to force a protected party to jump through some proof hoops. Example: Nissan's North America operation bought brake assemblies and parts from Continental Automotive. The brakes on one Nissan failed, apparently due in part to bad design choices by Nissan engineers (and a technical error in Continental-supplied software). Three people in another car were killed. Hit with a $24 million jury verdict, Nissan demanded indemnity (reimbursement) from Continental Auto Parts.

But the indemnity language in Nissan's purchase order said (in relevant part):

8.  … Seller’s liability shall also include … damages or cost arising from claims of personal injury or property damages caused directly or indirectly by defective parts supplied by Seller.

Nissan argued: "Paragraph 8 requires Continental to indemnify Nissan for expenses arising from claimed defects in Continental parts." (Emphasis in court's opinion.)

Continental responded that it would be liable under paragraph 8 for "actual—not alleged—defects in its products, and then only when the actual defect is to blame for the harm to Nissan."

Affirming summary judgment for Continental, the Sixth Circuit ruled:

By the terms of the contract, the district court held, Continental must indemnify Nissan where Continental’s defective parts caused injury or property damage. Nissan could establish this either by (1) showing a preclusive finding that a Continental defect caused a relevant injury or (2) litigating that issue in the first instance in the indemnification action.

We agree with this assessment of the contract. And we agree that because Nissan did neither, it cannot recover. Nissan N. Am., Inc. v. Continental Auto. Sys., 92 F.4th 585, 591 (6th Cir. 2024) (emphasis and extra paragraphing added).

Whoops.

14.3.13.3. Caution: Watch for the "express negligence doctrine"

Students in Texas and California: This is important.

Section 14.3.4 reflects the so-called "express negligence doctrine" in jurisdictions such as California and Texas: Even if Ginger is contractually obligated to indemnify Fred against losses, Ginger need not indemnify Fred from losses caused by Fred's own negligence or gross negligence unless the contract expressly and conspicuously so states. See, e.g., Crawford v. Weather Shield Mfg. Inc., 44 Cal. 4th 541, 552 (2008); Dresser Industries v. Page Petroleum, Inc., 853 S.W.2d 505, 508 (Tex. 1993) (conspicuousness requirement); Ethyl Corp. v. Daniel Constr. Co., 725 S.W.2d 705, 708 (Tex. 1987) (express-negligence doctrine). See generally, e.g., Byron F. Egan, Indemnification in M&A Transactions for Strict Liability or Indemnitee Negligence: The Express Negligence Doctrine (JW.com 2014), archived at http://perma.cc/RS63-FWKE.

Note: In Texas, advance releases of negligent conduct must likewise be both express and conspicuous; in its 1993 Dresser Indus. v. Page Petroleum decision, the Texas supreme court held that "the fair notice requirements of conspicuousness and the express negligence doctrine apply to both indemnity agreements and to releases in the circumstances before us …." Dresser Industries v. Page Petroleum, Inc., 853 S.W.2d 505, 509 (Tex. 1993) (emphasis added).

Similarly, California courts distinguish between "active negligence" and "passive negligence" in the context of a contractual release or exemption from liability:

Caution: In some places, an indemnity obligation — other than in an insurance policy — might be flat-out unenforceable to the extent it purports to protect a party from its own negligence. See, e.g., Ashley II of Charleston, L.L.C. v. PCS Nitrogen, Inc., 409 S.C. 487, 490-92, 763 S.E.2d 19 (S.C. 2014).

And in some jurisdictions, "anti-indemnity" statutes nullify certain indemnity obligations outright. See Anti-Indemnity Statutes, in Gordon Rees Scully Mansukhani, 50 State Legal Matrices for 2024 (grsm.com).

14.3.13.4. Indemnity obligations can have serious implications

A contractual right to be indemnified can have serious financial implications, especially if a catastrophic event occurs — an indemnifying party might find itself on the hook for millions of dollars. Example: In a 2018 decision, the Nebraska supreme court affirmed an indemnification award of $108.9 million after an explosion in a food-processing plant that killed 3 people and injured more than 60 others. Jacobs Eng'g Group Inc. v. ConAgra Foods, Inc., 301 Neb. 28, 917 N.W. 2d 435, 444 (2018). ]

And if the relevant contract has been assigned, things can get even more "interesting." Example: See the diagram of the interparty relationships and their indemnity obligations, in a 2020 Fifth Circuit decision in the aftermath of an oil-well blowout in the Gulf of Mexico. See Certain Underwriters at Lloyd’s, London v. Axon Pressure Prods. Inc., 951 F.3d 248 (5th Cir. 2020).

Even with only an implied indemnity obligation, the extent of liability could be significantly greater than anticipated. Example: An English couple contracted with a tour operator for a 15-day vacation package in Sri Lanka, including air fare and hotel. During their stay at the hotel, the wife was raped by a hotel maintenance worker. The UK Supreme Court held that the tour operator was liable for breach of contract — the contract said in part:

[W]e will accept responsibility if due to fault on our part, or that of our agents or suppliers, any part of your holiday arrangements booked before your departure from the UK is not as described in the brochure, or not of a reasonable standard, or if you or any member of your party is killed or injured as a result of an activity forming part of those holiday arrangements. … X v. Kuoni Travel Ltd., [2021] UKSC 34, paras. 2, 50 (reversing judgment of court of appeal) (emphasis added, citations omitted).

Notably, the supreme court held that the tour operator was directly liable for breach of contract, and that vicarious liability was not relevant.

14.3.13.5. A statute of limitations or ‑repose might not apply

Consider the following hypothetical situation:

  • You're a provider of construction-related services. As part of your contract with a customer, you agree to indemnify the customer against any damages or other harms that result from your services.
  • Something bad happens because of what you provided to the customer — but not until after the applicable statute of repose has already run from when you finished the project.

    (In contrast to a statute of limitations, a statute of repose cuts off liability at a specified date, even if no injury has yet occurred.)

Question: Are you, the service provider, off the hook? Possibly not. In a Massachusetts case, the state's highest court consider a situation such as the one described in our hypothetical above:

  • An architecture firm (the "architects") contracted with Boston University ("BU") to design a new, artificial-turf athletic field for BU. The field was to be be located above an underground parking garage, which the architects would also design.
  • The contract included a specifically-negotiated indemnity obligation: If the architects' negligence resulted in defects in the field's design, then the architects would have to indemnify BU for any and all resulting expenses.
  • And sure enough: In the parking garage under the athletic field, it turned out that seasonal changes in the weather led to the joists' expanding and contracting. (Remember, this was Boston.) The architects' design for the field hadn't taken that into account, so the field sagged in places; this made the field unsafe to use for sports events.
  • The school went ahead and fixed the problems with the field and sent the bill to the architects — who declined to pay.
  • The relevant statute of repose imposed a deadline of six years to bring a action for negligence.
  • More than six years after the field first opened, BU sued the architects for breach *of the indemnification provision.*

The court held that the state's statute of repose did not bar BU's contract claim for indemnity, in essence because that claim had accrued when the architects refused to honor the indemnity provision. See Trustees of Boston Univ. v. Clough, Harbour & Assoc., LLP, 495 Mass. 682. 255 N.E.3d 596 (Mass. 2025) (reversing summary judgment in favor of architects).

Pro tip: Consider trying to negotiate "sunset" time limits on all indemnity obligations.

14.3.13.6. Pro tip: When might an indemnity clause be advisable?

It can make sense to ask The Other Side of the Deal for a defense-and-indemnity obligation any time A might get sued by a third party because of something that B might have done (or failed to do).

For example, it might make sense for A to ask B for an indemnity obligation if A is one of the following:

  • a manufacturer that engages a reseller to sell the manufacturer's products to end-customers, where the reseller's people will be dealing with customer employees — and those customer employees conceivably might sue Argon for something that the reseller did to sell Argon's products;
  • a vendor that agrees to pay commissions to a referral source for customer referrals;
  • a service provider that engages an agency to perform background checks on key personnel in jurisdictions where consent is legally required;
  • a customer that allows a provider's people to come onto the customer's site, or to access the customer's computer system;
  • a university laboratory that provides vaccine-manufacturing instructions to a Big Pharma drug manufacturer.

In each of these cases, A might want B to agree to a defense-and-indemnity obligation to protect the client from third-party claims arising from B's misconduct — whether that misconduct is, say, a car accident that injures a bystander; sexual assault or harassment of a customer employee; etc.

On the other side of the coin: A reseller that agrees to "rep" a manufacturer's products might want the manufacturer to agree to defend and indemnify against warranty- and product-liability claims concerning those products. The same might be true for a party that signs a contract with the manufacturer to be paid commissions for customers referred to the manufacturer; on that subject, see the Referrals Protocol (13.10).

14.3.13.7. Who can best bear the risk?

In some transactions, one party will be far better able to bear the financial risks of the parties' dealings together. In such a transaction, the "smaller" party might to see if the larger party will agree to defend and indemnify the smaller party against claims, even if the smaller party was allegedly at fault, as part of their overall economic bargain.

Example: a small geophysics analysis firm does Big Data number-crunching to help oil-and-gas "majors" locate likely deposits. If an error by the small firm could allegedly cause significant harm to third parties, then the small firm might ask for a major to indemnify and defend the small firm against claims over a specified maximum.

This is also the concept behind "baskets" for losses. (31.3)

(Caution: The express-negligence rule might well apply; see 14.3.4.)

14.3.13.8. A "volunteer" (normally) can't claim indemnity for a settlement.

Suppose that:

  • "Fred" is contractually obligated to indemnify "Ginger" against third-party claims;
  • "Harry" threatens Ginger with a lawsuit;
  • Ginger pays Harry to go away; and
  • Ginger claims that Fred must reimburse her for what she paid to Harry.

QUESTION: Is Ginger correct?

Nebraska's supreme court explained the general rule:

[W]hether the party seeking indemnity paid [to] a third party under legal obligation is a central question in determining if an obligation to indemnify arises by operation of law. This has obvious ramifications when a party claims a right to indemnity by operation of law after settling a claim with a third party.

In that circumstance, a party seeking indemnity must generally prove that it was actually liable for the underlying claim. The indemnitee must not be a mere volunteer who has settled the underlying claim when there was no exposure to legal liability that obligated him or her to do so; if an indemnitee had no liability for the loss in the inception, then any payment made by the indemnitee is considered purely voluntary and not subject to indemnification.

Many courts have recognized an exception to the general rule …. This exception applies in cases in which the would-be indemnitor is provided notice of the underlying claim against the indemnitee and declines an opportunity to assume the defense.

But in order for this exception to apply, the party seeking indemnity must still show[:]

  • that it was potentially liable and
  • that the settlement amount was reasonable in light of that potential liability.

While these rules govern indemnification obligations imposed by law, parties are free to create separate or additional indemnification obligations by agreement.

So, for example, parties can, by contract, alter the common law rules on indemnity by calling for indemnification in the absence of underlying liability between the indemnitee and the injured party. Avis Rent A Car System, Inc. v. McDavid, 313 Neb. 479, 483-84 (2023) (reversing summary judgment in favor of Avis and remanding with instructions to grant summary judgment in favor of car renter) (formatting modified).

14.3.13.9. Special case: N.Y. landlord-tenant law

In New York, agreements that purport to exempt landlords from liability for negligence are void under General Obligations Law § 5-321. Moreover, under that law, "[p]lacing a requirement upon a tenant-lessee to procure insurance does not relieve the landlord of the effects of [that law]." On Point Window Treatment, Inc. v. 208 Clinton Place, LLC, 2024 NY Slip Op 50241 (N.Y. Sup. Ct. Mar. 10, 2024) (denying landlord's motion to dismiss).

It's a different story when it comes to indemnification against liability to third parties, backed by insurance (there's that "I&I" thing again; see Protocol 14.3.12):

… where, as here, the liability is to a third party, General Obligations Law § 5-321 does not preclude enforcement of an indemnification provision in a commercial lease negotiated at arm's length between two sophisticated parties when coupled with an insurance procurement requirement.

In such circumstances, the landlord is not exempting itself from liability to the victim for its own negligence. Rather, the parties are allocating the risk of liability to third parties between themselves, essentially through the employment of insurance, and the courts do not, as a general matter, look unfavorably on agreements which, by requiring parties to carry insurance, afford protection to the public. Castano v. Zee-Jay Realty Co., 2008 NY Slip Op 8081 (N.Y. App. Div. Oct. 21, 2008) (granting motion for summary judgment requiring tenant to indemnify landlord against trip-and-fall claim by third party; cleaned up, emphasis and extra paragraphing added).

14.3.13.10. Special case: Construction-contract indemnity statutes

[TO COME]

14.3.13.11. Special case: Texas Oilfield Anti-Indemnity Act

The Fifth Circuit explained in 2022: "The Texas Oilfield Anti-Indemnity Act ('TOAIA') voids indemnity agreements that pertain to wells for oil, gas, or water or to mineral mines, unless the indemnity agreement is supported by, inter alia, liability insurance." Moreover, noted the court, under the TOIAA the indemnifying party's liability for indemnity is limited to the dollar amount of insurance that the indemnifying party is contractually required to maintain, even if the indemnifying party happens to maintain more insurance than that. See Cimarex Energy Co. v. CP Well Testing, L.L.C., 26 F. 4th 683, 684-85 (5th Cir. 2022) (affirming summary judgment in favor of indemnifying party). Relatedly, see the commentary at 14.3.4.

14.4. Protected Group Definition

14.4.1. Applicability if agreed to

If this Definition is adopted in the Con­tract, it concerns the "Protected Group" of an individual and/or organization clearly specified in the Con­tract as being the beneficiary of:

  1. a defense and/or indemnity obligation; and/or
  2. a limitation of liability;

each such individual and organization is referred to as a "protected party."

Note

This is a convenience definition for use in, for example, various defense and indemnity clauses and limitations of liability.

14.4.2. Who is covered by the term?

For each protected party, the term Protected Group refers to the following individuals and organizations:

  1. the protected party itself;
  2. the protected party's affiliates, if any;
  3. any other individuals or organizations specified in the Con­tract; and
  4. the protected party's respective employees, officers, directors, shareholders (in that capacity), general- and limited partners, members, managers, and other persons occupying comparable positions, all as applicable.

14.4.3. Can you provide an example?

As a hypothetical illustration, suppose that ABC Corporation (a made-up name) is referred to by the shorthand term "ABC" — in that situation, the term "the ABC Protected Group" would refer to ABC's Protected Group, as defined above.

Note

Note the use of an illustrative example here, to help "serve the reader"; see 20.21 for additional discussion of the benefits of examples.

15. Occasional events

15.1. Amendments by Notice Option

You've surely seen Web site terms of service that say (among other things), "we can amend these terms any time we want by giving you X days advance notice." At least in U.S. jurisdictions, such amendment provisions will be enforced — if they're done correctly.

15.1.1. Parties: The Amender and the other party.

Under this Protocol, a party clearly identified in the Con­tract — and only that party, referred to here as the "Amender" — has the right to modify the Con­tract unilaterally by giving reasonable advance notice to another party, but only as stated in this Protocol.

Note

().  Caution: Here are two examples of jurisdictions where unilateral amendments by notice might not be enforceable:

15.1.2. Advance notice requirement

  1. To amend the Con­tract unilaterally, the Amender gives the other party reasonable advance notice of the proposed amendment, in accordance with Protocol 3.14 and the specific requirements of this Protocol — otherwise, the (purported) unilateral amendment will have no effect.
  2. In case the question arises: Changing the terms of service at a Web site, without more, doesn't count as notice.
Note

().  How much advance notice to require for a unilateral amendment might be a subject for negotiation — and possibly limited by legal restrictions, e.g., if consumers or employees are involved.

Caution: Consumer contracts might have special notice requirements. For perhaps-dated reviews of case law addressing what might be required to qualify as sufficient notice to consumers of unilateral amendment, see generally Robert V. Hale II, Recent Developments in Online Consumer Contracts, 71 Bus. Lawyer 353 (2016); Juliet Marie Moringiello and John E. Ottaviani, Online Contracts: We May Modify These Terms at Any Time, Right? (AmericanBar.org 2016). (Links not provided because for some reason these links crash Acrobat.)

Subdivision 2: You've probably seen companies' Website terms of service ("TOS") that assert — with astonishing brazenness — that it's supposedly your job to check the TOS every time you use the site, just in case the company has decided to change anything in those terms. Fortunately for common sense, that doesn't seem to be how it works. See, e.g., Douglas v. United States District Court ex rel. Talk America Inc., 493 F.3d 1062, 1066 (9th Cir. 2007). Accord: Heckman v. Live Nation Entertainment, Inc., 120 F.4th 670, 682 (9th Cir. 2024) (affirming holding that arbitration agreement and its delegation agreement were unconscionable); Stover v. Experian Holdings, Inc., 978 F.3d 1082 (9th Cir. 2020) (affirming order compelling arbitration; consumer could not claim benefit of new agreement terms when she had not received notice).

15.1.3. Required content of advance notice

A notice of (unilateral) amendment isn't effective unless it clearly and prominently states the following:

  1. at least one specific action that the other party could take to opt out of the amendment — such as, for example, terminating one's user account or perhaps terminating the Con­tract itself; and
  2. the deadline for the other party to take such opt-out action, failing which, the amendment will go into effect.
Note

Caution: Not opting out could be treated as acceptance of the amendment — but it might not be if a court deems the notice of amendment to have been insufficient. See, e.g., Land v. IU Credit Union, 218 N.E.3d 1282, 1290-91 (Ind. 2023) (affirming court of appeals's reversal of order compelling arbitration).

15.1.4. Required placement of amendment statement

A notice of amendment also isn't effective unless the statement that the Con­tract is being amended is explicit, prominent, and substantially at the beginning of the notice. The idea is that a reasonable reader in the other party's position must be able to quickly grasp that the notice is about an upcoming change to the Con­tract.

Note

A notice of unilateral amendment should be explicit that the Con­tract is being amended, lest a court hold otherwise. Example: A state supreme court held that when an employee had clicked on an online "acknowledge" button, what the employee had acknowledged was a merely directive to read a new policy requiring arbitration — not an agreement to modify the employee's pre-existing employment contract. See Lampo v. Amedisys Holding, LLC, 445 S.C. 305, 914 S.E.2d 139 (2025) (reversing and remanding court of appeals decision).

15.1.5. No retroactive effect

An amendment by notice under this Protocol doesn't alter any party's respective pre-amendment rights and obligations under the Con­tract.

Note

If a unilateral amendment doesn't state that it operates on a going-forward basis only, then a court could well hold that the contract itself was "illusory" and thus unenforceable; see the cases cited at 15.1.7.1. Pro tip: If you really want retroactive effect, then consider doing an agreed written amendment, discussed at Protocol 3.1.

15.1.6. Escalation

All parties escalate, as stated in Protocol 21.11, any dispute about:

  1. whether a unilateral-amendment notice under this Protocol was sufficient; and/or
  2. whether the proposed unilateral amendment goes beyond what the Con­tract allows.

15.1.7. Additional notes

15.1.7.1. Caution: A no-limits amendment right could kill the whole contract

A court might hold that a contract was "illusory" — and thus that the entire contract was unenforceable — if the contract says that a party has the right to change its terms unilaterally and retroactively, at least if the party doesn't give the other party sufficient advance notice and the right to opt out. Such an unenforceability ruling could have serious ripple effects, as discussed in the examples below.

Example: A customer sued Blockbuster (remember them?) for allegedly violating the customer's privacy rights; she sought class-action status.

  • Blockbuster moved to compel individual, case-by-case arbitration, as required in the Blockbuster on-line terms of service.
  • The customer opposed the motion — doubtless because for her lawyers, many onesie-twosie arbitration proceedings would be much less economically attractive to them than class arbitration would be.

The court denied Blockbuster's motion to compel arbitration, on grounds that the company's terms of service were "illusory" — because the unilateral amendment didn't include a so-called Halliburton exception, discussed below — and therefore was unenforceable under the relevant state law. See Harris v. Blockbuster, Inc., 622 F Supp. 2d 396, 400 (N.D. Tex. 2009), citing In re Halliburton Co., 80 S.W.3d 566 (Tex. 2002) (discussed below). See also Carey v. 24 Hour Fitness USA, Inc., 669 F.3d 202 (5th Cir. 2012) (employee handbook was "illusory" as contract because company had the right to change it, so arbitration agreement in handbook was unenforceable); see generally Illusory promise (Wikipedia.org).

Relatedly: Ticketmaster's arbitration agreement and its delegation agreement were held to be unconscionable, because Ticketmaster's terms of service permitted retroactive modification. See Heckman v. Live Nation Entertainment, Inc., 120 F.4th 670, 682-83 (9th Cir. 2024).

Now think about what else could result from a court's holding about an "illusory" contract: One or both parties might lose protection that the contract might otherwise have provided, such as for example an arbitration clause with class-action waiver; a forum-selection or governing-law clause; a limitation of liability; and so on.

Pro tip: Parties presumably would always be free to agree to amend the Con­tract with retroactive effect — but then of course it wouldn't be a unilateral amendment ….

Pro tip: A "going forward only" limitation might well save a unilateral-amendment clause from invalidation. Example: A court held that an employer had the right to terminate its arbitration agreement with employees, but the termination would not apply to claims that had accrued before the amendment. See Lizalde v. Vista Quality Markets, Inc., 746 F.3d 222, 224 (5th Cir. 2014) (reversing district court's denial of employer's motion to compel arbitration of employee's claim for on-the-job injury).

To somewhat-similar effect, the Uber ride-sharing terms of service of April 4, 2022 (last visited May 13, 2022) states, in the penultimate paragraph of section 1, that amendments by Uber are effective after notice, which arguably implies no retroactive effect:

… Unless Uber says otherwise in its notice, the amended Terms will be effective immediately and your continued access to and use of the Services after Uber provides such notice will confirm your acceptance of the changes. If you do not agree to the amended Terms, you must stop accessing and using the Services.

(Emphasis added.)

Example: Somewhat more-restrictively: A majority of the North Carolina supreme court held that a unilateral-amendment provision in a credit union's terms of service — which the credit union used to add an arbitration requirement — sufficiently complied with the state's implied covenant of good faith and fair dealing; the unilateral-amendment provision required advance notice and an opportunity to opt out and "the changes [to add arbitration] reasonably relate to subjects discussed and reasonably anticipated in the original agreement." Canteen v. Charlotte Metro Credit Union, 900 S.E.2d 890, 896 (N.C. 2024).

But two dissenting judges in that case objected that, by unilaterally adding the arbitration provision, the credit union "single-handedly deprived [the customer] of her constitutional right to a jury trial on her claims and the ability to defray the burden of vindicating that right through a class action. To make matters worse, the modification’s language—drafted and adopted by CMCU alone—left [the customer] without an avenue to opt out of arbitration and the class action waiver." But this was a dissent, of course, so the dissenters' views didn't prevail. Id. at 898 (Riggs, J., dissenting).

On the other hand, an express going-forward limitation would likely forestall an illusoriness argument. Example: In Halliburton (Tex. 2002), the Texas supreme court held that an employer could unilaterally impose a change the terms of at-will employment to require arbitration of disputes, as long as: (i) the employer gave advance notice; and (ii) the change didn't apply to claims against the employer where the employer had already been given notice of the claim. See In re Halliburton Co., 80 S.W.3d 566, 569-70 (Tex. 2002); see also, e.g., Watch House Int'l, LLC v. Nelson, 815 F.3d 190 (5th Cir. 2016) (reversing and remanding order compelling arbitration) (lack of advance-notice requirement rendered unenforceable a unilateral-amendment provision); Lizalde v. Vista Quality Markets, 746 F.3d 222 (5th Cir. 2014), where a federal trial court denied a party's motion to compel arbitration, but an appellate court reversed.

This, incidentally, raises the question whether the unilateral-amendment provision would be enforceable in the Uber ride-sharing terms of service of April 4, 2022, reproduced in 15.1.7.1, because that provision states that unilateral amendments are effective immediately upon notice.

15.1.7.2. Caution: Be able to "prove up" the fact of notice

A party that might send out notices of unilateral amendment should consider whether the party's email system and procedures can produce evidence that will persuade a judge or jury that a notice was actually sent to a particular customer, user, etc.

Example: A court vacated an order confirming an arbitration award against a PayPal customer who'd brought a claim against the company. The court remanded for a trial about whether the customer had in fact consented to PayPal's unilateral amendment to its terms of service, which had added an arbitration requirement. This fact issue arose because the customer — by sworn declaration — denied having seen the amended user agreement and claimed never to have received an email about it. As a result, a trial was necessary, so that the fact-finder (presumably a jury) could get to the bottom of the matter. Kass v. PayPal, Inc., 75 F.4th 693 (7th Cir. 2023).

(DCT comment: What odds would you give that a local jury would side with PayPal on that point?)

And this judicial skepticism could persist even through trial. Example: A federal court in California ruled that Dropbox had failed to unilaterally amend its terms of service (to add an arbitration requirement). Why? Because, said the court, Dropbox had not shown, by a preponderance of the evidence, that in fact Dropbox had given notice of the amendment, where the user denied having opened or read the notice email that Dropbox sent.

(DCT comment: This is an example of how in court, "truth is a happy accident" — what matters is evidence.)

The court said:

There is nothing in the record to suggest that Plaintiff could not use the service until he indicated his assent, that he would have been advised of new terms and conditions while using Defendant’s services, or that Defendant ever tracked whether Plaintiff had opened its email.

Even if the email alone could be considered “reasonably conspicuous notice,” Plaintiff took no action to unambiguously manifest his assent…

Given the complete lack of evidence of notice within Defendant’s service itself, Plaintiff’s ongoing use of the service is irrelevant to determining whether he had actual or constructive notice of the post-2011 terms of service.

(Extra paragraphing added.) Sifuentes v. Dropbox, Inc., No. 20-cv-07908-HSG, slip op. at 7 (N.D. Cal. Jun. 29, 2022) (denying Dropbox's motion to compel arbitration) (extra paragraphing added).

Professor Eric Goldman, an authority in this area, described the decision as "troubling" and said:

If you want to absolutely ensure that the TOS [terms of services] amendment sticks, you need users to click in assent. Good luck with that; but any lighter process is taking your chances. Eric Goldman, Dropbox’s TOS Amendment Fails (And If This Opinion Stands, Yours Will Too)–Sifuentes v. Dropbox (blog.ericgoldman.org 2022).

Example: An Uber driver in Georgia murdered one of his passengers. (You think that might have influenced the court's thinking?) The passenger's mother sued Uber for wrongful death. In the Georgia trial court, Uber successfully moved to compel arbitration, but an appellate court reversed and remanded, holding that a triable question existed whether the deceased passenger had in fact received updated terms and conditions from Uber — and thus had implicitly assented to arbitration by continuing to use the Uber service. That's because "neither the affidavit nor the exhibits provided by Uber list the email address to the which email was sent. … There is also no record evidence that the email was delivered to Thornton." (Emphasis added.) Thornton v. Uber Technologies, Inc., 858 S.E.2d 255 (Ga. App. 2021) (reversing and remanding order compelling arbitration of wrongful-death claim against Uber) (emphasis added).

Counterexample: New York's highest court essentially "blessed" a process that Uber had used to amend its online terms of service to incorporate an arbitration provision — which presumably included Uber's having preserved its electronic records that showed the following:

… The updated terms were available for recipients’ review by clicking on any of three hyperlinks appearing in the email. It is undisputed that plaintiff received and opened this email on January 15, 2021.

… Immediately beneath this was a large black button labeled "Confirm." It is undisputed that plaintiff checked the box and clicked the "Confirm" button. See Wu v. Uber Technologies, Inc., 43 N.Y.3d 288, 292-93, 260 N.E.3d 1060 (2024) (affirming denial of motion to stay arbitration and affirmance of order compelling arbitration) (emphasis added).

.

15.1.7.3. Caution: Possible bad PR?

Unilateral amendments to terms of service can lead to bad publicity. Example: Zoom ran into a public-relations buzzsaw when it unilaterally modified its terms of service to allow the company to train AI models on customers' information. See, e.g., Evan Schuman, Zoom goes for a blatant genAI data grab; enterprises, beware (Computerworld.com 2023); Jai Vijayan, Following Pushback, Zoom Says It Won't Use Customer Data to Train AI Models (DarkReading.com 2023).

15.2. Assignee Reasonable Assurance Protocol

15.2.1. Applicability: Assignment of the Con­tract

When this Protocol is agreed to, it applies if a party to the Con­tract (the "Assigner" or the "predecessor") assigns the Con­tract to another party (the "New Party") — and thus another party to the Con­tract (a "Remaining Party") is faced with dealing with the New Party instead of with the Assigner.

Note

This Protocol is modeled on UCC § 2-210(5) — it offers a compromise position for when one party wants the right to consent to the other party's assigning the contract, but the other party wants to stay free to assign. (Relatedly, see Assurance of Performance Protocol (15.4).)

15.2.2. Right to request assurance of performance

  1. The Remaining Party may give the New Party notice, in accordance with Protocol 3.14, that unambiguously asks the New Party for reasonable assurance that the New Party will successfully carry out the Assigner's obligations under the Con­tract.
  2. The Remaining Party's right to ask the New Party for assurance under this Protocol will expire automatically unless the Remaining Party's notice to the New Party asking for assurance becomes effective on or before the date 30 days after the Remaining Party first learned, via any means, of the assignment.
Note

Effectiveness of notice: See Protocol 3.14.

15.2.3. Termination right

  1. If the New Party does not provide the Remaining Party with such reasonable assurance on or before 30 days after the effective date of the notice asking for assurance, THEN: The Remaining Party may terminate the Con­tract — on a going-forward basis only — by giving notice to that effect.
  2. The termination will be effective as soon as the Remaining Party's termination notice to the New Party becomes effective.
  3. The Remaining Party is free to include a notice of termination as part of its notice asking for assurance.

15.2.4. Expiration of termination right

The Remaining Party's termination right under this Protocol will automatically expire on the date 30 days after the end of the period for the New Party to provide the Remaining Party with assurance.

Note

Expiration ("sunset") clauses generally: See 8.4.

15.2.5. Termination as EXCLUSIVE REMEDY (usually)

  1. The Remaining Party's right to terminate under this Protocol is the Remaining Party's EXCLUSIVE REMEDY for the New Party's failure to provide reasonable assurance.
  2. Such a termination would not affect any claim by either party for some other breach of the Con­tract.

15.2.6. Escalation

The parties are to escalate any dispute about the reasonableness under this Protocol as stated in Protocol 21.11.

15.4. Assurance of Performance Protocol

15.4.1. Prerequisites for invoking this Protocol

If A to the Con­tract ever has reasonable grounds to doubt whether a party B to the Con­tract would meet B's commitments under the Con­tract, THEN: A is free to ask B, in writing, for adequate assurance on that point.

Note

().  This Protocol is modeled on the requirement of adequate assurance of performance, in UCC § 2-609, which applies by its terms to a sale of goods.

A comparable common-law doctrine recognized by some jurisdictions — but not all: Virginia's supreme court declined to join the states recognizing a common-law right to adequate assurance; the court labeled the common-law version as "a modern innovation by the American Law Institute" in the ALI's Restatement (Second) of Contracts § 251. Under Wild Skies, Inc. v. Nat'l Rifle Ass'n, No. 240683, slip op. at 8-9 (Va. May 29, 2025) (affirming court of appeals's holding that Virginia doesn't recognize common-law doctrine of adequate assurance) (citing cases).

15.4.2. Possible work stoppage

  1. If A does ask B for assurance as stated in § 15.4.1, THEN: A is free, at the same time, (temporarily) suspend A's own performance under the Con­tract — unless, that is:
    1. it would be commercially unreasonable for A to suspend its performance under the circumstances; or
    2. A has already gotten what it bargained for under the Con­tract in relevant respects.
  2. If A suspends its own performance, THEN: A must promptly let B know that A is suspending its performance, before B reasonably relies on an assumption (express or implicit) that A was continuing to do what the Con­tract required A to do.
Note

().  As noted above, this is modeled on the requirement of adequate assurance of performance in UCC § 2-609.

Subdivision 1.a: Apropos of commercial reasonableness, see the discussion of commercially-reasonable efforts at Protocol 9.2.

Subdivision 1.b: As a simple hypothetical example, suppose that:

  • the Con­tract calls for Painter to paint Customer's factory interior, and for Customer to indemnify Painter in respect to any injuries that Painter's employees might suffer on the job that are caused by Customer's own people or machinery;
  • Customer pays Painter in full, in advance;
  • But Painter hear rumors that Customer might be having financial difficulties, so Painter wonders whether Customer is "good for" its indemnity obligation.

In that situation — because Painter has already been paid in full — it's likely only fair that Painter do the paint job, instead of stopping work just because someday Customer might not be able to meet its indemnity obligations in a scenario that might never actually arise.

On the other hand: If the painting work would be taking place where Customer's people or machinery really could injure Painter's people, then Painter might well be justified in asking for assurance under this Protocol.

(Alternatively, since "only money" is involved for Customer's indemnity obligation, Painter might try to negotiate to have Customer buy insurance (see 31.21) or establish some other backup payment source (see Protocol 4.4).

15.4.3. Termination right (for limited time)

  1. This § 15.4.3 applies if B does not provide A with the requested reasonable assurance within a reasonable time — not to exceed 30 days — after receiving A's written request for assurance.
  2. In that scenario, A can treat B's failure as B's repudiation of the Con­tract — in legal parlance, as B's "anticipatory breach" of the Con­tract.
Note

Repudiation of a contract is a type of breach of contract, known as "anticipatory breach." See, e.g., Under Wild Skies, Inc. v. Nat'l Rifle Ass'n, 915 S.E.2d 514, 517-19 (Va. 2025) (summarizing Virginia law).

"To prevail on an anticipatory breach claim under Texas law, a plaintiff must establish each of the following elements: (1) an absolute repudiation of the obligation; (2) a lack of a just excuse for the repudiation; and (3) damage to the non-repudiating party." Penthol, L.L.C. v. Vertex Energy Operating, L.L.C., 149 F.4th 504, 509-10 (5th Cir. 2025) (affirming district court finding that one party's letter to another party did not constitute an absolute repudiation of their contract) (cleaned up).

15.5. Evergreen Renewals Protocol

15.5.1. Definitions: Evergreen Period; renewal; extension

  1. If the Con­tract doesn't specify an Evergreen Period, then the term of the Con­tract is the Evergreen Period.
  2. In case the question comes up: For purposes of this Protocol, the term extension has the same meaning as renewal.
Note

().  An Evergreen Period might be, for example, the term of a relationship, e.g., for employment or channel partnership, when clearly so stated in the Con­tract.

Subdivision 2 has in mind the Eighth Circuit's holding in its 2012 AMC case, discussed in the comment at § 15.5.7.

15.5.2. Evergreen Option: Opt-out, not opt-in

  1. Each renewal of the Evergreen Period goes into effect automatically unless an eligible party opts out — but if the Con­tract clearly says otherwise, then renewal doesn't go into effect unless an eligible party opts in.
  2. The term "Evergreen Option" refers to the right to opt-out or opt-in, as applicable to this Protocol.
Note

().  From a business perspective, there's a critical potential difference between an opt-in option to renew, which requires action to continue as before, versus — as here — an opt-out option to terminate, which requires action not to continue as before. This difference was crucial in North Dakota's 2014 Smucker case, where the well-known food company Smucker got stuck paying nearly $280,000 in rent and utilities for a lease that it didn't want because it was late in exercising its option to terminate an automatic renewal. See Commercial Resource Group, LLC v. J.M. Smucker Co., 753 F.3d 790, 794 (8th Cir. 2014) (reversing and remanding summary judgment in favor of Smucker).] (Lesson: Use some kind of calendar reminder system!)

Caution: Drafters should check whether the Federal Trade Commission has any regulations affecting consumer renewals — in 2024 the FTC tightened up its existing rule about "negative option" (opt-out) automatic renewals for consumers, but the Eighth Circuit vacated the action for failure to follow statutory procedural requirements. See Custom Comms., Inc. v. FTC, 142 F.4th 1060 (8th Cir. 2025).

15.5.3. Eligible Party: Who can exercise the option

Either party (each, an "Eligible Party") has the right — in that party's sole discretion — to exercise the Evergreen Option.

Note

The "sole discretion" language is intended to forestall any claim that a decision to opt out must comply with any kind of duty of good faith and/or fair dealing. The Supreme Court of Canada once surveyed U.S. cases on this point in its 2015 Bhasin opinion. See Bhasin v. Hrynew, 2014 SCC 71 [2014] 3 S.C.R. 495, ¶ 91. Caution: In 2015, an Ontario trial court held (in a nonbinding dictum) that Bhasin "does not stand for the (extreme) proposition that under no circumstances does a 'sole discretion' contract renewal power have to be exercised reasonably." Data & Scientific Inc. v. Oracle Corp., 2015 ONSC 4178 (CanLII).

15.5.4. Actions to exercise Evergreen Option; deadline

Eligible Party: To exercise the Evergreen Option, give notice to that effect, to all other parties, in accordance with Protocol 3.14 — and do it so that the notice becomes effective no later than one month before the then-current expiration date of the Evergreen Period.

(Otherwise, the Evergreen Option will permanently expire as of the end of the then-current expiration date.)

Note

().  Who can exercise: Often, a party with bargaining power (e.g., a big customer dealing with a smaller supplier) will want to be the only one that has the right to exercise the Evergreen Option.

Caution: In some cases a statute might impose a minimum opt-out notice period

  • Example: A Minnesota statute, Minn. Stat. § 325E.37 § 3, requires at least 90 days' advance notice of non-renewal of certain sales-representative agreements.
  • Example: In the UK, specific requirements apply to subscription contracts with consumers. See generally Micaela Bostrom and Michiko Jo, The UK’s new requirements for subscription contracts with consumers – DMCC Bill Deep Dive Part 3 (JDSupra.com 2023).

    Pro tip: Some parties might want to negotiate the exercise deadline to take into account the circumstances — for example, if it would take a party some time to find and spin up a replacement contract relationship.

15.5.5. Maximum renewal duration?

  1. Unless the Con­tract clearly states otherwise, each renewal of the relevant Evergreen Period will be for the lesser of:
    1. the initial duration of the Evergreen Period; and
    2. one year.
  2. Example: A six-month Evergreen Period would be automatically renewed for successive six-month terms, without a break.
  3. Example: A three-year Evergreen Period would be automatically renewed for successive one-year terms (if the Con­tract didn't state otherwise), likewise without a break.
Note

().  This puts an upper limit on the duration of an automatic extension because too-long an automatic-extension period can be problematic, as discussed in the cautionary tale at 15.5.11.3. (The parties are of course free to affirmatively agree to any extension they want.)

Pro tip: Perhaps the initial renewal(s) could be of different durations — for example, in some contractual relationships, a first renewal might be relatively short, to give the parties a chance to find out what it's like working together; then if neither party opted out, subsequent renewals could be of longer duration.

15.5.6. Limit on number of successive renewals?

Unless otherwise agreed, the Evergreen Period will continue renewing indefinitely as provided in this Protocol, with no upper limit on the number of successive renewals.

15.5.7. Contract terms during renewal?

Unless otherwise agreed, any opt-out renewal under this Protocol — because the renewal would be automatic, without party action — will be on the same terms and conditions as before.

Note

Subdivision 2: This Protocol sometimes uses the term renew as a common business vernacular — but in some jurisdictions, a "renewal" right might require a party to renegotiate the terms and conditions as a condition of being able to exercise an option to renew.

Example: In the Eighth Circuit's 2012 AMC Showplace case:

  • The AMC movie theater chain's option to extend its lease of space in a Minnesota shopping center was literally labeled "Option to Extend," and "on the same terms and conditions" except for certain rent adjustments.
  • The court, though, held that this was really an option to renew — and that under state-court precedent, this in turn gave the landlord the right to demand new terms.
  • This, said the court, was "because the terms of the option period were not reasonably ascertainable from the existing lease [sic]." See Camelot LLC v. AMC ShowPlace Theatres, Inc., 665 F.3d 1008, 1009 (2012) (8th Cir. 2012) (affirming summary judgment for landlord).

DCT comment: The Eighth Circuit's reasoning seems more than a little strained.

15.5.8. Day-to-day if mandatory deadline reminder not sent

  1. This section will apply if the Con­tract requires A to send B a written reminder of an option deadline, but A doesn't do so.
  2. The automatic renewal will go into effect if it would otherwise do so — but only on a day-to-day basis.
  3. B can belatedly opt out of further day-to-day renewals of the Evergreen Period by so advising A in writing, effective when so stated in that written advice.
  4. B's belated opt-out right will be EXCLUSIVE REMEDY for A's failure to send B the reminder.
Note

This is provided because some customers will want their vendors to take on the burden of remembering (that is, calendaring) the option deadline date.

15.5.9. Option: Fee for Early Opt-Out

  1. Scenario: This Option — which applies only if clearly agreed to in the Con­tract — presupposes that one party (the "Leaving Party"), authorized by the Con­tract to opt out of an otherwise-automatic renewal, does so before 50 YEARS after the effective date of the Con­tract.
  2. Leaving Party: To opt out of the automatic renewal, you must do the following:

    1. Give the other party notice to that effect, as provided in Protocol 3.14; and
    2. Pay the other party, in immediately-available funds,🔗 an early-opt-out fee of USD $1 TRILLION — do so no later than exactly 11:59.00 p.m. UTC on the then-current expiration date of the Evergreen Period.

    Otherwise, the automatic renewal will go into effect — and your right to opt out of that renewal will permanently expires — without further action by any party.

  3. In case the question comes up: Payment of the early-opt-out fee of this Option is a form of alternative performance and not liquidated damages.
Note

().  This Option is inspired by an analogous provision in the First Circuit's 2014 Foodmark case, where the Ninth Circuit affirmed a summary judgment that a Canadian food distributor owed a U.S. marketing firm a fee for electing not to renew the parties' "evergreen" agreement. See Foodmark, Inc. v. Alasko Foods, Inc., 768 F.3d 42 (1st Cir. 2014).

Obviously the default values here are so absurd as to be laughable — that's to get drafters' attention.

Subdivision 5: For an extended discussion of alternative performance versus liquidated damages, see 21.19.1.3.

15.5.10. Option: No Evergreen Renewal After Assignment of the Con­tract

  1. Scenario: If this Option is agreed to, then automatic renewal under this Protocol won't occur at any time after an assignment of the Con­tract by any party specified in the Con­tract.
  2. In case the question comes up: This Option doesn't authorize assignment of the Con­tract but neither does it prohibit assignment.
Note

().  This Option is inspired by § 4.3 of a 2007 real-estate lease between Stanford University (landlord) and Tesla (tenant), which states in part: "The Extension Option is personal to Tenant and shall be inapplicable and null and void if Tenant assigns its interest under this Lease …."

See also Protocol 15.3 (assignment consent).

15.5.11. Additional notes

15.5.11.1. The business context

In many long-term business arrangements, the parties want regular opportunities to reevaluate whether to continue the arrangement — but they also want the arrangement to continue as before if no one wants to change it. By adopting this Protocol in the Con­tract, drafters can provide such an opportunity, on either an opt-out or opt-in basis.

Caution: By law, some jurisdictions restrict automatic extension or renewal of certain contracts (often consumer-facing) unless specific notice requirements are met — for example, a New York statute, NY Gen. Bus. L. art. 29-BB, requires clear and conspicuous disclosure of automatic renewal terms in consumer service contracts. See David O. Klein, New York To Implement New Auto-Renewal Law (Mondaq.com 2020).

From the other side of the table, a Minnesota statute, Minn. Stat. § 325E.37 § 3, regulates termination of sales-representation agreements — the statute requires 180 days notice of intent not to renew [sic] a sales-rep agreement that doesn't have a definite term. See Minn. Stat. § 325E.37 § 3; discussed in Engineered Sales Co. v. Endress A. Hauser, Inc., 980 F.3d 597, 599-600 (8th Cir. 2020) (reversing and remanding summary judgment).

If this will be an issue for one of your deals, you'll want to look up where the law stands in the relevant jurisdiction(s). See, e.g., Beth Bolen Chun, Salim Rashid, and Gonzalo E. Mon Auto-Renewal Laws: 2025 Round Up (KelleyDrye.com).

15.5.11.2. Pro tip: Be explicit when opting in or out!

In Massachusetts, a commercial tenant found itself owing more than $800,000 in liquidated damages under the tenant's lease with its landlord:

  • The lease had an automatic-extension provision, with a stated time limit for the tenant to opt out of an extension by notice to the landlord.
  • The tenant had email- and oral discussions with the landlord about opting out the automatic extension, but "never gave definitive written notice . . . or even clear oral notice" that the tenant was opting out. Innovation Pharmaceuticals Inc. v. Cummings Properties, LLC, 105 Mass. App. Ct. 1143, 265 N.E.3d 617 (2025) (affirming judgment below).

Relatedly: In J.M. Smucker Co. (8th Cir. 2014), the well-known food company ended up having to pay an extra year's rent on leased space because it used the wrong address to opt out of an automatic extension of the lease term.

*

15.5.11.3. Pro tip: Be sure to calendar opt-in and ‑out deadlines.

Parties agreeing to evergreen-extension clauses should be sure to calendar the deadline for opting out of an automatic extention, lest they find themselves losing valuable rights because of a strictly-construed opt-in deadline  — as once happened to a Pizza Inn franchisee See Pizza Inn, Inc. v. Clairday, 979 F.3d 1064 (5th Cir. 2020) (reversing district court's equitable excusing of missed deadline and jury's award of damages to franchisee).] — or being stuck with pricing concessions for many years longer than anticipated.

Example: DCT note: One of my software-vendor clients once found itself in such an unhappy situation: In one customer contract (from before my time), the vendor had agreed to lock in — for what ended up being a total of ten years — the initial, steeply-discounted pricing it had extended to one very-large customer, because the vendor hadn't calendared an automatic renewal at the five-year point.

15.6. Performance Improvement Plan Procedure Protocol

15.6.1. The parties: The Company and the Associate

When this Protocol is agreed to, it applies when:

  1. one party (the "Company") asserts that another party to the Con­tract (the "Associate") is failing to meet agreed performance standards under the Con­tract;
  2. the Company contemplates terminating its relationship with the Associate; and
  3. the Company proposes to give the Associate a last chance in the form of an agreed performance-improvement plan (a "Plan").
Note

().  Here we intentionally use the term "Associate" to encompass more than just employees; the term encompasses, e.g., contractors, resellers, and referral sources (to name a few).

The "last chance" concept in subdivision 3 comes from labor‑ and employment law: Especially when employees are represented by a union, so-called last chance agreements ("LCAs") are sometimes used, to largely the same effect as a PIP. See, e.g., Janice Holdinski, Meeta Bass and Susan Bauman, Last-chance Agreements: Expert Insights from Labor Arbitrators (adr.org 2024); Greg Ossi, Last Chance Agreements Require Careful Drafting to Avoid Arbitration (Venable.com 2006).

15.6.2. Required: Notice that "you're on plan"

  1. To kick off this Protocol, the Company is to give the Associate notice, in accordance with Protocol, to the effect that the Associate is being "put on plan."
  2. The on-plan notice must specify, in reasonable detail, the following:
    1. in what respect(s) the Associate has failed to meet previously-agreed performance requirements, and
    2. what action the Associate must take, on what time line, to remedy the failure(s) and thus be eligible to continue the Associate's relationship with the Company under the Con­tract.
Note

Basic fairness dictates that the Associate should be advised that he/she/it is being put "on plan."

The requirement for notice under the Con­tract is to leave a paper trail documenting the fact of the notice.

15.6.3. Consultation about Plan

The Company should consider consulting with the Associate about the Plan before sending the on-plan notice — but the Company gets to decide, in its sole discretion, whether and how much to consult.

15.6.4. Procedure for disagreements about the on-plan notice

  1. If the Associate has an issue with the specificity of the Company's on-plan notice, THEN: The Company is to consult with the Associate to a reasonable extent to try to resolve the issue.
  2. In the end, the Company gets to decide, in its reasonable discretion, whether the Company's on-plan notice was sufficiently detailed.
Note

The Company is given the final say because it'd be undesirable for (say) a bitter, fired employee to start (or complicate) a lawsuit or arbitration by claiming that he or she wasn't given a sufficiently-detailed notice about his or her performance deficiencies. But the Company is still held to the familiar judicial-management standard of abuse of discretion.

15.6.5. Consequences of failure to meet Plan

  1. If the Associate does not meet the Plan requirements, THEN: That will be a material breach of the Con­tract (see 18.6: Termination for Material Breach Protocol) of the Con­tract, whether or not the Associate regards the failure as material.
  2. The Associate is not entitled to a second chance to meet the plan requirements — that is, there will be no cure period for the material breach — except at the Company's sole discretion.
Note

The performance-improvement plan is itself the "cure period," so there's no reason for the Associate to have (yet another) cure period if it fails to comply with the plan. (But this doesn't rule out disputes over whether in fact there's been a failure to comply with the plan.)

15.6.6. Additional notes

15.6.6.1. The business context

Performance-improvement plans are usually seen in employment relationships, but they're not unknown in ongoing business-to-business ("B2B") relationships. This Protocol serves as a framework for developing and implementing a PIP that has at least a decent chance of success — defined as, the employee or supplier not getting fired.

15.6.6.2. "We're putting you on plan": Is that really code for "find another job"?

For an employee or channel partner, "being put on plan" is decidedly Not A Good Thing: In the workplace, it's generally regarded as a tacit signal that the employee is going to be fired, with the company hoping to make itself bulletproof against a subsequent lawsuit by the employee.

•  Writing at Forbes.com in 2018, an experienced HR executive said: "a manager only puts you on a Performance Improvement Plan when they want to get rid of you. Instead of a Performance Improvement Plan, it should be called This is the First Step Toward Firing You Plan, because that is what's happening." Liz Ryan, The Truth About 'Performance Improvement Plans' (Forbes.com 2016).

•  See also a wife's 2024 account of her husband's unsuccessful effort to keep his job by participating in Amazon's Pivot program — that company's version of a PIP — which sounds fairly brutal. See My husband went through the Amazon Pivot process. It was crushing to watch him cry over losing his job. (BusinessInsider.com 2024). See also the Hacker News discussion of the article, with links to other Amazon Pivot stories ]

•  Another writer — not entirely convincingly — was more optimistic : "While the seriousness of them shouldn’t be ignored, if you are put on a PIP, know that all hope is not lost. You have the power to turn your performance around–and save your job!" Michelle Y. Costello, Your Boss Put You On A Performance Improvement Plan, Now What? (FastCompany.com 2018).

16. Representations and warranties

16.1. Implied-Warranties Disclaimer

Under the law in many jurisdictions, some vendors, service providers, and others are deemed to implicitly "warrant" certain things (see the discussion at 16.1.6). Many of those implied warranties can be "disclaimed" — that is, negated by a statement saying, in effect, no, we're not warranting that particular thing. This Protocol provides disclaimer language for drafters to consider.

16.1.1. Each party disclaims all "Implied Warranties."

When this Protocol is agreed to, each specified party — sometimes referred to here as "you" — DISCLAIMS any and all implied warranties, representations, conditions, and terms of quality (each, an "Implied Warranty") for goods or services to be provided by or on behalf of that party under the Con­tract, except as otherwise stated in the Con­tract.

Notes

().  Representations and warranties: See § 16.2 for a discussion of the similarities and differences between the two.

"Conditions" and "terms of quality" are from UK law, as discussed at 16.1.6.4.

Implied warranties for goods: See 16.1.6.1 and 16.1.6.2. For services: See 16.1.6.3.

16.1.2. Broad coverage

This Protocol applies whether or not any purported Implied Warranty is claimed to have arisen: (1) by law; (2) by an alleged custom, practice, or usage in the trade; and/or (3) by an alleged course of dealing or performance by the parties themselves.

16.1.3. Some illustrative examples

A disclaimer of Implied Warranties extends, without limitation, to Implied Warranties about one or more of the following:

  1. merchantability (as defined in UCC § 2-314) of goods;
  2. fitness of goods for a particular purpose (ditto), whether or not the disclaiming party or any of its suppliers or affiliates know, have reason to know, have been advised, or are otherwise in fact aware of any such purpose;
  3. quiet enjoyment;
  4. noninfringement (but any express warranty of noninfringement in the Con­tract would be unaffected);
  5. absence of viruses or other malware in software;
  6. results;
  7. workmanlike performance or -effort (but see any express warranty of performance, such as that of 25.3 if applicable);
  8. quality;
  9. non-interference;
  10. accuracy of content;
  11. correspondence to description (an English formulation, roughly analogous to the implied warranty of merchantability).

16.1.4. No effect on any express warranties

A disclaimer of one or more Implied Warranties does not affect any express warranty, representation, or other factual commitment that's clearly stated in the Con­tract.

Note

Unfortunately, contract reviewers sometimes need to be reminded that a disclaimer of implied warranties doesn't affect any express warranties in the Con­tract. DCT comment: More than once, when representing a supplier, I've encountered a contract reviewer for a customer who inappropriately deleted a disclaimer of implied warranties — even when the disclaimer included an explicit carve-out for express warranties, such as in the language above. (Makes you wonder ….)

16.1.5. No effect on implied warranty of title to goods sold

A disclaimer of one or more Implied Warranties will not affect any implied warranty of title to tangible goods, whether under Uniform Commercial Code § 2-312 or otherwise.

Note

().  Where goods are concerned, the implied warranty of title, in UCC § 2-312, requires that any disclaimer of that warranty must be expressly stated.

From a business perspective this makes sense: As a hypothetical example, even if Ginger were to sell Fred a car "as is," Fred should still be entitled to assume that Ginger isn't trying to palm off stolen property.

Note: This carve-out is limited to implied warranties of title. It doesn't encompass implied warranties of noninfringement, which are disclaimed by this Protocol.

16.1.6. Additional notes

16.1.6.1. Implied warranties for sales of goods can arise automatically

In the U.S., article 2 of the Uniform Commercial Code (adopted in all states except Louisiana) provides a number of implied warranties that sellers are deemed to make when they sell "goods," namely the following:

  • an implied warranty of clean title, "free from any security interest or other lien or encumbrance of which the buyer at the time of contracting has no knowledge," under UCC § 2-312(1);
  • an implied warranty of noninfringement of third-party rights, under UCC § 2-312(3) —
    • but only if the seller is "a merchant regularly dealing in goods of the kind";
    • and with an exception if the buyer furnishes specifications and the infringement;
  • an implied warranty of merchantability, under UCC § 2-314, with a definition that could be paraphrased as, in essence, goods that a reputable merchant would be willing to offer to the public under the contract description; and
  • an implied warranty of fitness for the buyer's particular purpose, under UCC § 2-315, but only if "the seller at the time of contracting has reason to know any particular purpose for which the goods are required and that the buyer is relying on the seller's skill or judgment to select or furnish suitable goods …."; whether this prerequisite was met, of course, could be a disputed fact issue, resulting in expensive litigation.
16.1.6.2. UCC implied warranties for goods can be disclaimed

In the (U.S.) Uniform Commercial Code, section 2-316 (governing sales of goods) specifically allows sellers to disclaim warranties that are not expressly stated in the contract, with some limits:

(2) Subject to subsection (3), to exclude or modify the implied warranty of merchantability or any part of it the language must mention merchantability

and in case of a writing must be conspicuous,

and to exclude or modify any implied warranty of fitness the exclusion must be by a writing and conspicuous.

Language to exclude all implied warranties of fitness is sufficient if it states, for example, that "There are no warranties which extend beyond the description on the face hereof."

(3) Notwithstanding subsection (2)

(a) unless the circumstances indicate otherwise, all implied warranties are excluded by expressions like "as is", "with all faults" or other language which in common understanding calls the buyer's attention to the exclusion of warranties and makes plain that there is no implied warranty; and

(b) when the buyer before entering into the contract has examined the goods or the sample or model as fully as he desired or has refused to examine the goods there is no implied warranty with regard to defects which an examination ought in the circumstances to have revealed to him; and

(c) an implied warranty can also be excluded or modified by course of dealing or course of performance or usage of trade.

(Emphasis and extra paragraphing added.)

16.1.6.3. Will there be an implied warranty of workmanlike performance?

Where services are concerned, drafters should be aware that — in some states, in some circumstances — the law might automatically impose a warranty of "workmanlike" performance (see the definition at Protocol 25.8) or something close to it. See, e.g., Fed. Ins. Co. v. Winter, 354 S.W.3d 287, 291-94 (Tenn. 2011) (citing numerous authorities but not defining workmanlike).

Implied warranties of workmanlike performance will typically come into play especially in connection with the sale of a new residence. The imposed warranty might even be non-waivable and/or non-disclaimable. For example:

  • Home construction: Forty-three states provide an implied warranty of habitability for new residences, according to a decision by Utah's supreme court, while three other states provide a warranty of workmanlike manner. See generally Davencourt at Pilgrims Landing Homeowners Association v. Davencourt at Pilgrims Landing LC 30, 2009 Utah 65, 221 P.3d 234, 250 (reversing dismissal of implied-warranty claim; "in every contract for the sale of a new residence, a vendor in the business of building or selling such residences makes an implied warranty to the vendee that the residence is constructed in a workmanlike manner and fit for habitation").
  • Repairs of tangible goods or property: In its Melody Homes decision, the Texas supreme court held that an implied warranty of good and workmanlike performance extends to repairs of tangible goods or property. See Melody Home Mfg. Co. v. Barnes, 741 S.W.2d 349 (Tex. 1987); see also the commentary at 16.1.
16.1.6.4. Watch out for special disclaimer requirements in England, etc.

The disclaimer of implied conditions and terms of quality, at § 16.1.1, is a nod to the law in England, Wales, and Northern Ireland (not "UK law"; see the commentary at 21.12.9.13).

Example: In one English case, an oil seller failed to disclaim those things and learned (to its regret) that its disclaimer of (only) implied warranties didn't shield it from liability. See KG Bominflot Bunkergesellschaft Für Mineralöle mbh & Co KG v. Petroplus Marketing AG, [2009] EWHC 1088, ¶ 49 (Comm).

16.1.6.5. Some services might come with implied warranties

This is discussed in the commentary at 25.3 (performance standards for services).

16.1.6.6. Representations can be deemed to be UCC warranties

Suppose that in a contract for the sale of goods in the U.S., the seller only represents that Fact X is true, without using the word warranty: That representation can itself be a warranty, because under UCC § 2-313(1):

(a) Any affirmation of fact or promise made by the seller to the buyer

  • which relates to the goods
  • and becomes part of the basis of the bargain

creates an express warranty that the goods shall conform to the affirmation or promise.

(b) Any description of the goods which is made part of the basis of the bargain creates an express warranty that the goods shall conform to the description.

(c) Any sample or model which is made part of the basis of the bargain creates an express warranty that the whole of the goods shall conform to the sample or model.

(Emphasis and extra paragraphing added.)

Of course, it might be hotly disputed whether "the basis of the bargain" included a particular affirmation of fact, description of the goods, or sample or model.

Because the representation is (putatively) an express warranty, it likely can't be "disclaimed" as such (but see 20.34.6.5 concerning waivers of reliance on representations).

16.1.6.7. Pro tip: Be specific about what's disclaimed?

Courts seem to have more sympathy for a reliance disclaimer if, in the words of the Second Circuit, the disclaimer "tracks the substance of the alleged misrepresentation." The court reversed a lower court's dismissal of a claim under federal securities law, but the underlying principle might well apply in contract cases as well. See Caiola v. Citibank, NA, 295 F.3d 312, 330 (2d Cir. 2002) (reversing dismissal of claim under federal securities law) (citing cases).

16.1.6.8. Initial the disclaimer?

If there's a concern that a party might someday try to repudiate its reliance disclaimer, it can't hurt to have that party separately initial the contract as close as possible to the disclaimer.

Example: In a New York case, an estranged married couple reconciled — temporarily, as it turned out.

  • During their reconciliation, the wife voluntarily dismissed her three pending lawsuits against the husband, and they signed a settlement agreement to that effect.
  • But then the couple separated again, and the wife sued the husband again, this time claiming that he had fraudulently induced her to dismiss her other lawsuits by promising that he would return to her and permanently resume their marital relationship.
  • Unfortunately for the wife, the settlement agreement she signed included a reliance disclaimer, which she had specifically initialed; as the court acidly noted: "There is no allegation in the complaint that plaintiff did not read or did not understand the agreement; in fact, she initialed the agreement in the margin opposite the very paragraph disclaiming the alleged representation." See Cohen v. Cohen, 1 A.D.2d 586 (N.Y. App. Div. 1956) (per curiam; affirming dismissal of complaint for insufficiency) (emphasis added).

Caution: If a line is provided for a party to initial a reliance disclaimer (or any other specific term), counsel for the other party should make sure that the disclaiming party actually does initial the line. Otherwise, the other party might have an even worse problem: the uninitialed line could help persuade a judge or jury that the allegedly-disclaiming party really did overlook the disclaimer; that's just the opposite of what the other party wanted.

16.1.6.9. The law might invalidate certain implied-warranty disclaimers

Some states do not allow companies to sell consumer products "as is"; in those states, sellers have implied-warranty obligations that cannot be avoided. And the federal Magnuson-Moss Act prohibits a company from disclaiming implied warranties (see 16.1.6.1) for any consumer product if the company offers a written warranty for the product or sells a service contract for it.

(The above paragraph is adapted in part from the Federal Trade Commission's Businessperson's Guide to Federal Warranty Law (FTC.gov 2006); no copyright claimed in the FTC's text.)

Note: State personal-injury and product-liability law could render a seller liable for selling a defective or dangerous product that causes death or personal injury, even if the seller sells the product "as is."

16.2. Representations vs. warranties (notes)

16.2.1. Introduction

When parties do business together, each party generally presupposes that certain things were true in the past, or are true now, or will be true at some point in the future. But sometimes those presuppositions turn out to be wrong.

With that in mind, it's often prudent for parties to divide up the responsibility for making sure that specified things were — or are — or will be — as planned. This can include provisions for parties representing certain things and/or warranting certain things, as discussed in this chapter.

Each representation or warranty basically does two things:

  1. It sets out a particular factual state of affairs that one party (or both) wants to be true; and
  2. it allocates, as between the parties — but does not in itself reduce — the risk, i.e., responsibility for the consequences if the state of affairs turns out not to be true.

But: Representations and warranties have different proof requirements and — upon proof of specified facts — different available remedies.

16.2.2. Ninja Warrior: "The Hill of Proof"

The Hill of Proof

Let's consider a hypothetical example: Ginger wants to sell her car to Fred; suppose that she represents — or perhaps warrants, or perhaps both — that her car has never been in an accident [past fact] and is in good working order [present fact].

But now suppose that after Fred takes delivery of the car and drives it, he learns that it has significant mechanical problems, and he wants to sue Ginger (probably in small-claims court) for damages.

To help visualize how this works, think in terms of the American Ninja Warrior TV show, with an evidentiary “Hill of Proof” (see above) that plaintiff Fred must "climb" in making his claim(s) against defendant Ginger:

–  As plaintiff, Fred starts out at the bottom of the Hill of Proof.

–  As Fred clambers up the Hill of Proof, he tries to "hit" various evidentiary checkpoints along the way.

–  The “prizes,” i.e., the remedies available to Fred, are positioned at different points up the hill.

(“The Hill of Proof” sounds like something from a Harry Potter novel, no?)

This is simply a visual depiction of how the law generally works.

Representations vs. warranties: An English court decision, Sycamore Bidco v. Breslin, highlighted the difference between representations and warranties. See Sycamore Bidco Ltd v Breslin & Anor [2012] EWHC 3443 (Ch) (2012), discussed in, e.g.: Raymond L. Sweigart and Christopher D. Gunson, ‘Reps’ and Warranties: One Could Cost More Than the Other Under English Contract Law (PillsburyLaw.com 2013); and Glenn D. West, That Pesky Little Thing Called Fraud: An Examination of Buyers’ Insistence Upon (and Sellers’ Too Ready Acceptance of) Undefined “Fraud Carve-Outs” in Acquisition Agreements, 69 Bus. Lawyer 1049, 1058 n.47 (2014).

For extensive additional citations in this area, see Professor Tina Stark's scholarly pummeling of the misguided notion that representations and warranties amount to the same thing, which she offered in two comments on Ken Adams's blog. See also an earlier piece on the same subject by Stark, also responding to an Adams essay. Tina Stark, Nonbinding Opinion: Another view on reps and warranties, Business Law Today, January/February 2006.

16.2.3. Seller strategy 1: Offer a warranty only?

Suppose that our defendant Ginger only warranted a fact, but she did not represent it. For example, suppose that Ginger sold her car to plaintiff Fred, and she suspected — but she didn’t know for sure — that the engine was going to need work.

In that case, Ginger might:

  • warrant, but not represent, that the car was in good working order, and
  • limit plaintiff Fred's remedy to defendant Ginger’s reimbursing Fred for up to, say, $200 in repair costs.

In that situation, at trial the only three evidentiary checkpoints that plaintiff Fred would need to reach would be the following:

  1. that defendant Ginger warranted a statement of past or present fact, to use Tina Stark’s formulation [I’ll leave out future facts for now]. — here, Ginger’s statement is “the car is in good working order”;
  2. that Ginger's statement was false — her car, as delivered to Fred, turned out to need some significant work; and
  3. that Fred incurred damages as a result, i.e., repair costs.

If, at the trial, plaintiff Fred can successfully get past those three evidentiary checkpoints, then he will be entitled to recover warranty damages (generally, benefit-of-the-bargain damages) for defendant Ginger's breach of warranty — but in this case, limited by the contract to $200 in repair costs.

And that’s it; without more, Fred needn't prove that he reasonably relied on Ginger's warranty — but neither will he be entitled to tort-like remedies for fraudulent inducement or negligent misrepresentation, such punitive damages and/or rescission, i.e., unwinding the contract, as he would on the left side of the Hill.

16.2.4. Seller strategy 2: Offer a representation only?

Let’s change up the hypothetical once more: Suppose that Ginger had no reason to think her car had any problems, but she also didn’t want to bear any risk that it did have problems. In that case, Ginger might represent, but not warrant, something like the following: "So far as I know, the car is in good working order, but I'm not a mechanic and I haven't had it checked out by a mechanic."

In that situation, if the car did turn out to have problems, then plaintiff Fred would have to hit all five checkpoints on the Hill of Proof (16.2.2) to recover any damages from defendant Ginger; the first three alone wouldn't be enough because Ginger didn't warrant that the car was in good condition — even though the first three would be enough if Ginger had/ warranted good condition.

16.2.5. Buyer strategy: Ask for both a rep and a warranty!

But now suppose that defendant Ginger both represented and warranted the statement of fact, i.e., that her car was in good working order. And then suppose that plaintiff Fred successfully hits the first three evidentiary checkpoints on the Hill of Proof (16.2.2). In that situation, Fred can try to keep going to hit two more checkpoints, namely:

  1. that Fred in fact relied on Ginger's representation and that Ginger intended for Fred to do so — chances are good that both of these will be practically a given, because why else would Fred's representation have been expressly set forth in the contract that Ginger signed; and
  2. that Ginger made the false representation intentionally (or possibly, in some jurisdictions, was negligent or reckless in doing so). This scienter element is often the biggie, from a proof perspective.

If plaintiff Fred can successfully hit both of these additional evidentiary checkpoints on the Hill of Proof (and if defendant Ginger fails to show that Fred's reliance on her representation was unreasonable), then Fred would be additionally entitled to more “prizes,” namely tort-like remedies such as rescission and perhaps punitive damages.

(Defendant Ginger might try to prove that Fred's reliance was unreasonable under the circumstances, which could defeat Fred's misrepresentation claim — but that might be a risky strategy.)

At trial, plaintiff Fred might well assert both breach of warranty and fraudulent inducement or negligent misrepresentation. That way, if Fred proves unable to show scienter on defendant Ginger's part, then he can still fall back on his warranty claim.

The same would be true if Ginger could persuade the factfinder that Fred's reliance on her (mis)representation was unreasonable: Fred would lose on his claim for fraudulent inducement or negligent misrepresentation, but he might still be able to win on his warranty claim.

16.2.6. Pro tip: Which is better for your client?

So, here's a rule of thumb:

  1. A party that is asked to represent or warrant something (such as a seller) will always want to consider whether only to warrant the thing or only to represent it; this might well vary depending on the party's actual knowledge and the potential financial exposure if the represented- or warranted thing turns out not to be true.
  2. In contrast, any party asking for a representation or warranty (such as a buyer) will always want to push for both a representation and a warranty, so as to give that party more flexibility in litigation — see the two sides of the Hill of Proof at 16.2.2 — in case the represented- or warranted thing turns out to be false.

This suggests the following strategy for drafting with a future trial in mind:

  • If a party "P" is being asked to represent and warrant some fact — say, if P is a supplier being asked for a commitment about its products or services — then a drafter representing P should consider whether P should try to only represent the fact or to warrant the fact.

    (As a matter of negotiation strategy P might eventualy end up agreeing to do both. But as a drafter, it’s worth giving some thought to the question.

  • On the other hand, if your client is asking someone else to represent and warrant a fact — say, if you're a customer asking for a commitment from a supplier — then you’ll want to ask for the contract language to include both a representation and a warranty.

    (Argon might not have the bargaining power to insist on getting both — but if it does, then having both could give the client more flexibility if litigation should ever come to pass.)

Why would a customer ask for both a representation and a warranty? Because "they lied!" is a stinging charge, as discussed at 20.34.6.7 — and when a big contract fails, trial counsel will pretty much always try hard to find opportunities to accuse the other side of having misrepresented facts. Doing so can work, sometimes spectacularly well: Jurors and even judges might not understand the nuances of the dispute, but they will definitely undertand the accusation that "they lied!"

16.2.7. Buy insurance for representations & warranties?

If a party is asked — or is asking another party — to make representations and warranties, it might be desirable to investigate whether insurance coverage is available for those reps and warranties. See generally, e.g.:, Daniel Avery, Representations & Warranties Insurance (JDSupra 2021); Eric Jesse, Reps & Warranties Insurance: Five Myths Dispelled (JDSupra.com 2020), archived at https://perma.cc/9FWX-3HSH; Joseph Verdesca, Paul Ferrillo, and Gabriel Gershowitz, Representations and Warranties Insurance: What Every Buyer and Seller Needs to Know (Weil.com 2016), archived at https://perma.cc/RSU3-66V3.

17. People

17.1. Training - (notes)

17.1.1. Training repayment agreements - caution

In 2024, Colorado "put[] into place a law to toughen protections for employees who are subject to abusive contracts ostensibly requiring repayment to employers for education and training expenses upon termination of employment, commonly referred to as 'TRAPs' (Training Repayment Agreement Provisions)." See Robyn Marsh, Marcus Mintz and Michael Wexler, Colorado Amends Non-Compete Law To Address Potential Abuses of Training Repayment Agreement Provisions (TRAPS) (TradeSecretLaw.com 2024).

17.1.2. Details to address

When a contract requires a party to provide training, it should set forth specific details about the training, such as the following (as appropriate):

  1. contact information for lead representatives for each party;
  2. specific courses to be offered;
  3. physical location(s) of training, if any;
  4. minimum- and maximum class size;
  5. scheduling;
  6. required trainee qualifications (prerequisites);
  7. logistical support to be provided by the party whose people are being trained;
  8. registration deadline;
  9. cancellation- and refund policy;
  10. any fee(s) that the training provider will charge, including but not limited to:
    • any minimum fee (and how many attenders does that cover);
    • any per-person fee;
    • materials charges, if any;
  11. reimbursement of the training provider's expenses (see generally Protocol 4.7);
  12. payment deadlines (see generally 4.13).

17.2. Severance agreements (raw notes)

Journalists refer to notes such as these as "saving string."

From Wright v. Eugene & Agnes E. Meyer Foundation, 68 F.4th 612 (D.C. Cir. May 23, 2023) (lightly edited for formatting):

WILKINS, Circuit Judge:

Plaintiff Dr. Terri Wright is the former Vice President of Program and Community of the Eugene and Agnes E. Meyer Foundation, a non-profit that promotes social and racial equity in the Washington D.C. area. In that role, Wright was responsible for the Foundation’s community engagement efforts, grant-making, and collective action strategy.

She received largely positive feedback during her tenure, but less than two years after she was hired, the CEO of the Foundation, Nicola Goren, fired her for purported interpersonal and communication-related issues. Wright, who is African-American, believes these stated reasons were pretext to mask discriminatory animus.

Seeking to avoid litigation, Wright and the Foundation signed a severance agreement, under which Wright agreed to release employment-related claims against the Foundation and its employees, and which contained a mutual non-disparagement clause.

But roughly a month after Wright was fired, Goren told another leader in the non-profit space that Wright was let go because she was “toxic,” created a “negative environment,” and that two-thirds of the Foundation staff would have quit if Wright had stayed.

Wright sued the Foundation and Goren for breaching the severance agreement, for doing so in a racially discriminatory manner in violation of 42 U.S.C. § 1981, and for defaming her.

The District Court dismissed all three claims.

  • It first found that the non-disparagement clause obligated the Foundation only to direct its employees not to disparage Wright, leaving the Foundation and its officers and employees free to in fact disparage her.
  • Second, and as a result, the District Court found that Wright’s § 1981 claim failed because it was based on a breach of the severance agreement.
  • Lastly, the District Court found that Goren’s statements were protected by the common interest privilege, as they were made in her capacity as the Chair of the Board of a separate non-profit organization to the CEO of that organization.

We hold that the District Court erred in dismissing all three claims.

  • As to Wright’s breach of contract claim, the non-disparagement clause could reasonably be interpreted to preclude the Foundation from disparaging Wright, and dismissal under Federal Rule of Civil Procedure 12(b)(6) [for failure to state a claim even if all pleaded facts are assumed to be true] is therefore inappropriate.
  • As to her § 1981 claim, we find that she has plausibly alleged a prima facie case that the Foundation, through Goren, breached the severance agreement due to racial animus.
  • And lastly, because Wright has plausibly alleged that Goren’s statements were made with reckless disregard for the truth and for discriminatory reasons, they are not protected by the common interest privilege, which requires a showing of good faith on the part of the speaker.

* * * 

The crux of Wright’s claim is that implicit in the Foundation’s promise to “direct” certain officers, directors, and employees to not disparage her was a promise that the Foundation itself would also not disparage her, at least through the statements of its CEO and President who signed the Agreement.

Thus, Wright argues, the Foundation breached the Severance Agreement when Goren disparaged her in her conversation with Dr. Henson.

In Defendants’ view, the Foundation’s duty began and ended with its promise to “direct” its employees; neither the Foundation, nor its directors or any other employee, had a corresponding or continuing duty to not disparage Wright.

We find that the Severance Agreement, read as a whole, is ambiguous and reasonably capable of Wright’s interpretation.

17.3. Stay-or-pay (brief notes)

For employment agreements entered into on or after January 1, 2026, California's Assembly Bill 692 (signed into law October 13, 2025) severely limits a company's ability to require an employee to repay a debt if the employee leaves the company before X amount of time has passed.

The bill also gives employees a private right of action against companies that violate the new law; a winning employee is entitled to the greater of actual damages or $5,000.

17.4. Recruiting (someday)

17.4.1. Recruiting - points to consider:

Here's a list of subheadings in a contract posted by an anonymous redline.net member:

1.  No poaching of Client’s staff.

2.  No fee owed for candidates that client notified recruiter was already a candidate or staff, or that was recruited without candidate consent, or that was skipped.

3.  Confidentiality protections for the client. If the agency insists on a mutual confidentiality clause, make sure that candidate referrals are not CI if the candidate is described by (b) above.

4.  Duty to screen.

5.  No third party beneficiaries.

6.  Termination by client for convenience.

7.  Obligation to find a replacement if candidate is fired (other than due to RIF) or resigns within a defined period of employment.

8.  Refund remedy if agency fails to find a replacement for a candidate that resigned or was fired.

9.  Non-exclusive.

10.  Equal opportunity.

11.  No out-of-pocket expenses; only compensation is what's set out in the agreement.

17.5. Background Checks Protocol

It's not unusual for customers to want their service providers to run background checks on key personnel. The goal is normally to identify people with criminal records, drug problems, or other indicia of potential trouble that could cause operational- or legal problems.

17.5.1. Parties: Vendor and Customer

In this Protocol, the term "Vendor" refers to:

  1. a party that, under the Con­tract, will provide services to another specified party, referred to for convenience here as the "Customer"; and/or
  2. any other party clearly indicated in the Con­tract, whether or not providing services under the Con­tract.

17.5.2. Required background checks

When this Protocol is adopted, the Vendor will have commercially-reasonable background checks conducted — in advance of staffing as described in this Protocol — on each Specified Individual.

Note

().  This uses the vague-but-practical standard of commercial reasonableness — not least because it gives the Vendor an incentive to err on the side of being clearly "in the band" for that standard.

This Protocol is designed for general usage, so for convenience, we use the defined term Vendor because it's commonly a service provider that is asked to run background checks on its people. But other types of contracting party might be asked to have background checks run on its people as well.

  • Example: A manufacturer or distributor of potentially-dangerous software or other critical goods might also be asked to run background checks on its relevant people.
  • Example: For a party whose people will have access to another party's trade secrets, the other party might want to restrict access to individuals who have had background checks.

    Depending on the circumstances, parties might agree that some or all of the following should be checked in connection with a background check:

1.  Driving-record check: A check of records of accidents; driver's-license status; driver's-license suspensions or revocations; traffic violations; and driving-related criminal charges (e.g., DUI).

2.  Education verification: Confirmation of dates of attendance, fields of study, and degrees earned. Education checks are sometimes used because résumé padding is not an uncommon occurrence.

Example: The chief spokesman of Walmart resigned after the retail giant learned that he had falsely claimed to have graduated from college, when in fact he had not finished his course work; ditto the former dean of admissions at MIT.

3.  Employment verification: A check of of start- and stop dates and titles of employment for the past seven years or the past two to five employers, whichever results in more employers being checked.

4.  Liens: A check of records of tax- and other liens; civil judgments; and bankruptcy filings (to provide a better indication of any past financial difficulties of the checked individual).

5.  Personal reference check: Telephone- or in-person interviews with at least three personal references, seeking information about the following characteristics of the individual:

  • ethics;
  • work ethic;
  • reliability;
  • ability to work with others (including, for example and where relevant, peers, subordinates, superiors, customers, and suppliers);
  • strengths;
  • areas with room for improvement;
  • personality.

6.  Professional license verification: Verification that an individual who claims to have a professional license (e.g., doctor, lawyer, engineer, etc.):

  • does in fact have such a license; and
  • is in good standing with the relevant licensing body — because it's not impossible that someone claiming to be a doctor, lawyer, CPA, etc., might not be in good standing.

7.  Residence address verification: A check of dates of residence addresses for the past seven years (to reduce the risk of the checked individual's seeking to evade a criminal-records check by omitting a residence address).

17.5.3. Definitions: Criminal-History Check; Criminal History

  1. The term "Criminal-History Check" refers to a commercially-reasonable check for evidence whether an individual has ever engaged in any of the following:
    1. any felony;
    2. violence of any kind, including but not limited to sexual violence;
    3. child- or elder abuse;
    4. materially-deceitful conduct, including but not limited to fraud; and/or
    5. acts of moral turpitude.
  2. The term "Criminal History" refers to not-insubstantial evidence that an individual has engaged in any conduct of the kind listed in subdivision 1 above.
Note

().  A criminal-history check would typically include a nationwide check of records of arrests, convictions, incarcerations, and sex-offender status. Criminal-history records checks in basic form seem to be available from any number of Web sites at low cost, including from government agencies such as the FBI and/or the Texas Department of Public Safety.

Subdivision 2: This definition doesn't require a criminal conviction; see the discussion of this subject in the commentary to §  17.5.9, which imposes staffing restrictions when a criminal-history concern is revealed.

Pro tip: Drafters could consider whether to require that subjects of background checks must be asked to submit fingerprints to confirm their identity (and guard against imposters).

Caution: Under pre-Trump administrations, the U.S. Equal Employment Opportunity Commission (EEOC) filed lawsuits against employers who allegedly "violated Title VII of the Civil Rights Act by implementing and utilizing a criminal background policy that resulted in employees being fired and others being screened out for employment …." EEOC Press Release (2013).

The EEOC also took the position that a blanket prohibition against using personnel with criminal records could be alleged to have a disproportionate impact on racial- or ethnic minorities and thus to be illegal in the United States. See EEOC Enforcement Guidance (2012).

But the second Trump administration has been taking a chainsaw to DEI programs ("diversity, equity, and inclusion"), so drafters and their counsel should check the latest developments.

Caution: Entirely aside from the federal government's shifting position, some states — and even some cities — might likewise restrict an employer's ability to rely on criminal background information in making employment-related decisions.

Drafters should pay particular attention to the law in California, New York, Massachusetts, Illinois, and Pennsylvania (not necessarily an exhaustive list). This is because in recent years the practice of automatically disqualifying people with criminal convictions has come under fire from government regulators and the plaintiff's bar as being potentially discriminatory (the so-called "ban the box" movement).

For one list of states and cities with ban-the-box laws, see Avery (2019).

17.5.4. Definition: Critical Activity

For purposes of this Protocol, the term "Critical Activity" refers to any activity under the Con­tract, where the activity is expected to involve one or more of the following:

  1. access to one or more of the Customer's computer systems; data; or confidential information;
  2. the possibility of death or bodily injury to any employee, contractor, customer, licensee, or invitee of the Customer; and/or
  3. the possibility of significant loss of (or other significant damage to) tangible or intangible property of the Customer.
Note

Some drafters might want to expand this section to encompass loss or damage to third parties' property, and/or to economic loss.

17.5.5. Definition: Drug Check; Drug Concern

  1. The term "Drug Check" refers to a commercially-reasonable check for evidence that an individual makes use of one or more of the following:
    1. illegal drugs;
    2. alcoholic beverages to excess; and/or
    3. prescription drugs other than in accordance with a lawfully-issued prescription.
  2. The term "Drug Concern," refers to not-insubstantial evidence of drug use as described in subdivision 1 above.
Note

().  These definitions are pretty broad, because if a background check indicates that a person might have a drug-misuse problem — or even took certain prescription medications — then tighter restrictions could appropriate for certain activities. (This is an area where contract terms might need to be fine-tuned to fit the parties' needs.)

As with the definition of Criminal History, this definition of Drug Concern in Protocol 17.5.5 uses the term not-insubstantial evidence instead of substantial evidence because the latter term (1) is more vague, and (2) might be less-recognizable to non-lawyer readers, than the former term.

Companies should be cognizant of disability laws such as the Americans with Disabilities Act, which might affect a company's ability to deny employment because of medically-prescribed drug use.

And companies might want to consider the possible effect on employee morale of asking them to take a drug test — and what they might have to do if a valued employee were to bust the test. (As the saying goes: Be careful about asking a question if you're not prepared to deal with the answer.)

17.5.6. Definition: Restricted Activity

For purposes of this Protocol, the term "Restricted Activity" refers to any activity that, in the context of the Con­tract:

  1. entails access, by the Specified Individual, to premises, equipment, employees, suppliers, and/or customers, of the Customer; but
  2. does not rise to the level of a Critical Activity.
Note

This definition is meant to encompass activities of a less-sensitive nature than Critical Activities, because sometimes the Customer might want background checks for such activities.

17.5.7. Definition: Specified Individual

  1. The term "Specified In­div­id­u­al" refers to each of the Vendor's employees, and each employee of the Vendor's contractors and/or subcontractors, if any, who will be performing one or more "Critical Activities" and/or "Restricted Activities," each as defined in this Protocol.
  2. For purposes of this Protocol, the term Specified Individual does not include:
    1. any employee of the Customer, nor
    2. any employee of any licensee, invitee, or other contractor of the Customer.
Note

It likely won't make sense to require checks for everyone working for the Vendor in connection with the contract. And after a problem had arisen, we don't want a finger-pointing Customer or other party to claim, with 20/20 hindsight, that one of its own employees, customers, etc., should have been treated as a Specified Individual and therefore should have been background-checked by the Vendor.

17.5.8. Prior consultation for certain staffing

The Vendor will consult with the Customer, before staffing an individual to a position, whenever all of the following are the case:

  1. the proposed staffing position requires a background check under this Protocol;
  2. prudence suggests further inquiry in view of the individual's background-check results — including (but not limited to) the specific prohibition cases mentioned below; and
  3. the individual would be staffed to any Critical- or Restricted Activity.
Note

This seek a balance between safety and flexibility: It doesn't give the Vendor carte blanche to use potentially-problematic individuals, but neither does it give the Customer an absolute veto in all circumstances.

17.5.9. Customer consent for Critical-Activity staffing

If a Specified Individual's background check indicates Criminal History and/or Drug Concern, THEN: The Vendor will not staff that individual for any Critical Activity without the Customer's express prior written consent.

17.5.10. Customer objections to Restricted-Activity staffing

If the Customer timely objects, on reasonable grounds, to a Specified Individual — during or after the advance consultation required by § 17.5.8 — THEN: The Vendor will not staff that individual for any Restricted Activity without the Customer's express prior written consent.

Note

Here, the Customer's right to timely object on reasonable grounds is intentionally vague; the intent is to encourage the parties to work together cooperatively.

17.5.11. Vendor's continued responsibility

For the avoidance of doubt: The Vendor will not be relieved of its responsibilities under the Con­tract just because the Customer did or did not object to one or more of the Vendor's staffing proposals under this Protocol.

17.5.12. Vendor's expense responsibility

As between the Vendor and the Customer: The Vendor is responsible for out-of-pocket expenses of background checks under the Con­tract unless the Customer clearly agrees otherwise in writing.

Note

As between: See 32.4.

17.5.13. Vendor's indemnity obligation

The Vendor will defend and indemnify the Customer and the Customer's Protected Group from any claim, by any third party, to the extent that the claim arises from the conduct of any background check covered by this Protocol.

Note

The term "by any third party" would encompass, for example, claims by governmental authorities.

Note

().  Here, the term "any claim" would encompass, for example, any claim that alleges one or more of the following:

  1. that the Specified Individual didn't consent to the background check;
  2. that whoever did the check didn't comply with an applicable privacy law;
  3. that the Specified Individual wasn't timely notified about a decision using information from the background check as required by law (for example, a credit-reporting law); and/or
  4. that the Vendor and/or an agent of the Vendor, in doing the background check, allegedly violated the law in some other way — if the Vendor were to screw up a background check on an individual (e.g., if the Vendor violates the sometimes-tricky law in this area), then it wouldn't be surprising for the individual's attorney to sue the Customer in addition to the Vendor, on the theory that maybe the Customer would pay something to make the lawsuit go away.

Example: As one example, see the troubles caused by a contractor to bookseller Barnes & Noble in the Hebert case, discussed in the commentary at Option 17.5.16.

Pro tip: Any mention of indemnification should automatically trigger at least the mental question — for each party's drafter(s) — is insurance appropriate to provide a backup source of funds?

(Consider the bawdy reminder mnemonic " "I&I," retooled to stand for indemnity and insurance.)

See also the general discussion of insurance at 31.21.

17.5.14. Escalation

If either party asks, the parties will escalate any dispute about the Vendor's staffing proposals under this Protocol:

  1. first, to supervisors as provided at Protocol 3.4; and
  2. if necessary, to a neutral advisor as provided at Protocol 21.11.

17.5.15. Option: Background Checks Short-Form Clause

(a) Whenever [fill in party name] (the "Vendor") assigns personnel for potentially-sensitive activities under the Con­tract (as defined in subdivision (b) below), the Vendor will have commercially-reasonable background checks conducted beforehand. (b) For purposes of subdivision (a) above, the term "potentially-sensitive activities" would ordinarily include, for example, any activity involving access to: (1) the Customer's premises, equipment, and/or computer network(s); (2) the Customer's confidential information; (3) the Customer's employees; and/or (4) in the context of the Con­tract, the Customer's suppliers and customers.

Note

For easier copying-and-pasting, this short-form clause is condensed into a single paragraph — even though it comes close to violating the Spaghetti Rule (2.5) by almost being a "spaghetti clause" instead of a "macaroni clause."

17.5.16. Option: Credit Check Requirement

The Vendor will have each background check include standard credit reporting from all major credit bureaus serving the jurisdiction in question.

Note

().  Caution: Credit checks, if not done correctly, can get a checking party in trouble under the [U.S.] Fair Credit Reporting Act ("FCRA"). Noncompliance with background-check consent requirements has hit some well-known companies with sizable settlement payouts. See, e.g., Gettings et al. (2015) (Chuck E. Cheese — $1.75 million) and Lebowitz (2014) (Publix — $6.8 million).

One particular procedural requirement comes up regularly in class-action lawsuits: Section 1681b(b)(2)(A) of the FCRA, which states that, with certain very-limited exceptions:

… a person may not procure a consumer report, or cause a consumer report to be procured, for employment purposes with respect to any consumer, unless—

(i) a clear and conspicuous disclosure has been made in writing to the consumer

at any time before the report is procured or caused to be procured,

in a document that consists solely of the disclosure,

that a consumer report may be obtained for employment purposes; and

(ii) the consumer has authorized in writing … the procurement of the report by that person. Hat tip: Remson (2014).

Caution: Willful violation of the FCRA disclosure requirement entitles the consumer to recover "statutory damages ranging from $100 to $1,000 per violation, punitive damages, and attorney fees." Syed v. M-I, LLC, 853 F.3d 492, 497 (9th Cir. 2017) (cleaned up).

Caution: If an FCRA consent form contains anything other than the mandated disclosure — even in a footnote — the requester is in danger of being labeled a willful violator, with consequences as stated just above. Example: A California appeals court reversed a summary judgment in favor of Barnes & Noble, on grounds that a reasonable jury could find that the company acted willfully by asking a job applicant to sign a consent form provided by a background-checking company, because the consent form included a footnote with a disclaimer of warranties and advice to employers to seek their own legal advice. See Hebert v. Barnes & Noble, Inc., 78 Cal. App. 5th 791, 796, 796 (2022); see also Syed, 853 F.3d at 497-98 (9th Cir. 2017) (consumer consent form included liability waiver by consumer).

17.5.17. Option: Criminal-History Check

The Vendor will have each background check include a Criminal-History Check.

17.5.18. Option: Drug-Check

The Vendor will have each background check include a Drug Check.

17.5.19. Option: Independently-Sourced Contact Information

For personal reference checks, the Vendor will have the reference's contact information obtained from a source independent of the Specified Individual.

17.5.20. Additional notes

17.5.20.1. Pro tip: Get consent anyway?

It might be prudent to obtain a checked individual's consent to a background check even if the law doesn't require consent: If the individual were to learn of an unconsented background check, the individual's displeasure might go viral on social media, especially given today's heightened sensitivity to privacy concerns.

BUT: If you ask for consent, you should be prepared for the answer to be "no" — and then what? (See 12.2.11.1.)

17.5.20.2. Are background checks actually useful?

It's been suggested that background checks on people who have lived in California might not provide employers with much real-world benefit, that that the time and money might be better spent on searching applicants' social media. In part, that's due to recent changes in California law, Senate Bill 731, which have resulted in automatic sealing of certain felony-conviction records and in limits on what employers can do with conviction information. See Yaffe & Gordon (2022); hat tip: Cynthia Abesa at the lawyer-forum redline.net.

17.6. Employee Protection Protocol

17.6.1. This Protocol is binding only if the parties agree to it.

  1. When this Protocol is agreed to, the parties follow it whenever both of the following are true:
    1. A makes, or considers making, a claim arising out of or relating to the Con­tract against B, whether the claim is made by suing B in court or otherwise; and
    2. B has one or more employees or other "Associates," defined at § 17.6.4 below.
  2. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol

17.6.2. Suing each other's employees is off-limits

  1. By signing and delivering the Con­tract, A WAIVES and RELEASES, in advance, each claim that A might have against B's Associates — in their capacity as Associates — where the claim arises out of or relates to the Con­tract or any transaction or relationship resulting from the Con­tract.
  2. Moreover: In entering into the Con­tract, A certifies that A is not relying, and will not rely, on any statement or silence by an Associate of B in the Associate's personal capacity, with respect to some or all of the following:
    1. B's performance under the Con­tract; nor
    2. any representation or warranty made in, or in connection with, or as an inducement for the Claimant to enter into, the Con­tract.
Note

().  Subdivision A: The bold-faced and all-caps phrases are for "conspicuousness" in case that's required by applicable law — as it might be in Texas, for example, as discussed in the commentary at 14.3.4.

Subdivision A: This waiver and release might not provide that much protection for employees who themselves are truly bad actors; see the additional discussion at 17.6.5.4.

Subdivision B — "in the Associate's personal capacity": Of course, if an Associate were to sign the Con­tract in his or her personal capacity — for example, as a guarantor — then this Rule wouldn't prevent A from making a claim against the Associate for the Associate's own breach(es) of the Associate's specific obligations under the Con­tract.

See the discussion of reliance waivers at Protocol 11.7.

17.6.3. This Protocol applies broadly

A intends for the waiver and release in this Rule to apply very broadly — without limitation, to any claim based on any doctrine or theory of:

Note

().  The legalese terms are shorthand for various legal doctrines familiar to lawyers.

Caution: Different jurisdictions might well approach these doctrines in different ways.

17.6.4. Definition: Protected "Associates"

For purposes of this Protocol, the term "Associate" of B refers to the following:

  1. any employee of B;
  2. any individual contractor of B who, as a practical matter, is functioning as an employee of B;
  3. an officer, member of the board of directors, shareholder, or incorporator of B if B is a corporation;
  4. a manager or member of B, if B is a limited-liability company ("LLC");
  5. a limited partner of B, if B is a limited partnership;
  6. someone holding a comparable position in another type of organization; and
  7. an agent, attorney, or accountant engaged by B.

17.6.5. Additional notes

17.6.5.1. Example: Oregon sues Oracle mid-level manager for $45MM

Example: In 2014, the state of Oregon filed a $3 billion lawsuit against Oracle Corporation and six Oracle employees personally, in the wake of the failed attempt to develop Oregon's health-insurance exchange under the Affordable Care Act a.k.a. Obamacare.

  • The six employees sued included five executives at the vice-president level and higher — as well as a technical manager who was accused of having conducted a fraudulent demo of the new system's capabilities.
  • The state sought "only" some $45 million from the technical manager, as well as amounts ranging from $87 million to $267 million from various Oracle executives.

To be sure, high-profile lawsuits like this typically settle before trial. Not least, this is because the elected officials who bring or authorize the lawsuits would prefer to trumpet a "victory" instead of rolling the dice with the court.

And sure enough, Oregon's lawsuit against Oracle was settled — Oracle agreed to pay Oregon $25 million in cash and provide the state with another $75 million in technology.

Example: Such cases don't always settle: In IBM (2019), the state of Indiana sued IBM for allegedly botching the building of a new system for administering the state's welfare programs. That lawsuit dragged on for nearly ten years and ended (more or less) with a judgment against IBM for some $78 million. (In that case, the government apparently didn't sue individual IBM personnel.) See Indiana v. IBM Corp., 138 N.E.3d 255 (Ind. 2019).

(The questionable nature of the damages award — according to a dissenting opinion by a state supreme court justice — is discussed at 21.5.8.3.)

17.6.5.2. Example: Perdue Farms sues a truck driver — and its own gate guards(!)

Example: Perdue Farms (2024): A truck driver, making a chemical delivery to a Perdue Farms poultry-processing plant, told the plant's gate guards (who worked for a security contractor) that he was delivering bleach. But the driver was seriously mistaken: The bill of lading said, correctly, that the delivery was of aluminum chloride, a corrosive hazardous.

The gate guards didn't check the bill of lading; they told the driver to put the "bleach" in the bleach tank. The resulting chemical reaction caused significant damage to the facility: "Fog and foam erupted from the tank into the plant, filling multiple rooms and damaging equipment. Perdue had to shut down its plant for 'multiple days' to clean the plant and salvage its equipment."

Perdue sued the trucking company; the security company; and the driver and three gate guards personally. Perdue apparently did so to try to escape a forum-selection clause in the security-company's contract with Perdue, which designated the federal district court in Maryland — where Perdue was incorporated and had its headquarters — as the exclusive forum for any disputes relating to that contract.

The Indiana supreme court would have none of it: "[W]e reject [Perdue's] strategic pleading to avoid the forum-selection clause by suing the [security company's] Indiana-based employees individually. Second, we decline to apply the forum-selection clause to the plaintiff's claims against the individual employees. These employees (unlike their employer) are not parties to the forum-selection clause, and they are not in privity with their employer." Perdue Farms, Inc. v. L&B Transport, LLC, 239 N E.3d 842, 844-45 (Ind. 2024) (emphasis and extra paragraphing added).

17.6.5.3. Why might a party sue another party's employees?

In a contract lawsuit, a plaintiff might name one or more of the defendant's employees, etc., as co-defendants. Possible reasons:

  1. The plaintiff might feel that the defendant company had too-few assets that could be seized to satisfy a judgment, but that the individual co-defendants personally owned substantial assets.
  2. The plaintiff's litigation counsel might want to try to rattle the defendant's employees and pressure them to cooperate as witnesses against their employers; this is akin to the way that criminal prosecutors will sometimes bring charges against low-level employees to try to "flip" them.
17.6.5.4. How much protection would this Protocol really provide?

This Rule would preclude some "fraudulent inducement" claims involving alleged fraudulent representations outside the contract — but not, perhaps, claims of "contractual fraud," i.e., "a knowingly false contractual representation …." AmeriMark Interactive, LLC v. AmeriMark Holdings, LLC, No. N21C-12-175 MMJ CCLD, text acc. n.12 (Del. Supr. Ct. Nov. 3, 2022).

Nor would this Protocol likely protect an individual against tort-based claims. The Texas supreme court explained:

Independent of the vicarious liability that may be imposed on corporate shareholders and officers based on veil-piercing theories, we have also long held that corporate agents are personally liable for their own fraudulent or tortious acts even though they were acting on behalf of the corporation. Keyes v. Weller, 692 S.W.3d 274, 279 (Tex. 2024) (cleaned up).

The state supreme court affirmed reversal of a summary judgment that had dismissed fraud claims by two plaintiffs against two individual defendants; those defendants were members, and had acted as agents, of a limited liability company. The affirmance meant that the two individual defendants would have to return to the trial court and defend against the plaintiffs' fraud claims.

In another case, the Texas supreme court noted that "the fact that an individual was acting in a corporate capacity does not prevent the individual from being held personally liable for the harm caused by those [tortious] acts [committed by the individual]." Transcor Astra Group S.A. v. Petrobras America Inc., 650 S.W.3d 462, 478-79 (Tex. 2022) (reversing court of appeals; reliance disclaimer in settlement agreement barred fraud claims).

But even so: To keep parties' employees out of the line of fire in disputes, contractual protective language, along the lines of this Rule would certainly be better than nothing.

17.6.5.5. Ethics note: Should a lawyer look out for the client's employees?

Let's assume that it's a lawyer who is drafting or reviewing a contract on behalf of an organization. The lawyer has no professional obligation to make sure that the company's employees are protected from personal liability.

But it’s normally not a conflict of interest for the lawyer to simultaneously keep an eye out for the interests of clients' employees as well as for the interests of the client. (See also 29.4.3 for a similar point in the context of drafting contract signature blocks.)

Caution: A lawyer might find herself dealing with an employee of a client company in a situation where the interests of the employee and the company diverge or even conflict. One example might be an investigation of possible criminal conduct such as deceptive backdating of a contract, discussed at 29.1.9.

Whenever that happens, the lawyer should consider whether she should affirmatively advise the employee, preferably in writing, that she’s not the employee’s lawyer and that the employee should consider engaging separate counsel — conceivably, the company's lawyer might even have an ethical obligation to do so.

17.6.5.6. Appendix: Non-recourse language "in the wild"

See the following footnotes for non-recourse clauses used in real-world contracts, one from a Delaware case,29 the other from a New York case.30

17.6.5.7. Related: The Himalaya clause, from maritime practice

This Protocol is akin to the so-called Himalaya clause, which has its origins in maritime practice; it draws on ideas proposed by noted corporate-law practitioner Glenn West and a coauthor. In an email exchange with me on August 8, 2012, Mr. West commented: "Both sides of the transaction have the same general interest in protecting the integrity of the entity-specific nature of the contract; and if they don't, [West's] clause smokes that out and there is a real discussion about guarantors." See Glenn D. West & Natalie A. Smeltzer, Protecting the Integrity of the Entity-Specific Contract: the "No Recourse Against Others" Clause-Missing or Ineffective Boilerplate?, 67 Bus. Lawyer 39, 71-72 (2011).

17.7. Employees' Non-Waivable Rights Protocol

17.7.1. Lighthouse Protocol

17.7.1.1. Prohibition

Each party: Don't treat the Con­tract as impeding any employee, of any party to the Con­tract, from exercising a right that, by law, can't be waived — such as, for example, any applicable right of an employee:

  1. to speak out about workplace conditions;
  2. to make "whistleblower" disclosures to governmental authorities; and/or
  3. to discuss or disclose information about unlawful acts in the workplace — such as (without limitation) harassment, or discrimination, or other conduct that the employee has reason to believe is unlawful.

17.7.2. Additional notes

17.7.2.1. The business context

Employers have been known to try to use confidentiality agreements (and confidentiality provisions in employment agreements and settlement agreements) to keep workers from speaking publicly about workplace condition or cooperating with law-enforcement authorities. But federal- and state government agencies often take the position that such agreements and provisions are unlawful. See Melissa Osipoff Camire and George A. Reeves III, Congress Voids Sexual Harassment NDAs: 10 Things Employers Need to Know (fisherphillips.com 2022) (discussing the federal Speak Out Act, enacted in 2022).

Pro tip: This is one of those areas where, in some circumstances, advice of knowledgeable legal counsel could be especially helpful — and possibly even crucial.

This Protocol might not convince a court if the parties behave differently, but at least it's something.

17.7.2.2. What kind of employee-protection laws might be in play here?

This Protocol has in mind such laws as:

Pro tip: Consider checking whether a relevant jurisdiction for the Con­tract has a comparable law.

17.7.2.3. The NLRB's (pre-Trump) position

The Biden-era National Labor Relations Board took the position (along with some courts) that a contractual requirement of silence about workplace conditions — and even proffering such requirements to employees — violates section 7 of the National Labor Relations Act, at 29 U.S.C. § 157; in enforcing the specific decision, the Sixth Circuit declined to address the Board's position on that point. See McLaren Macomb and Local 40 RN Staff Council, OPEIU, 372 NLRB No. 58 (Feb. 21, 2023), enforced, NLRB v. McLaren Macomb, No. 23-1335, slip op. at part III.C, text acc. nn.3-4 (6th Cir. Sept. 19, 2024) (unpublished).

Likewise, in another Biden-era case, the NLRB filed a complaint on similar grounds against an Ohio-based company that operated "medical clinics and spas providing outpatient non-surgical aesthetic services" in Cincinnati and in Schofield, Wisconsin. A link to a PDF of the complaint in Harper Holdings, LLC, d/b/a/ Juvly Aesthetics can be found at Epstein Becker & Green, P.C., NLRB Issues Complaint Against Company For Maintenance And Enforcement Of Noncompete And Non-Solicit Provisions (NatLawReview.com 2023).

17.7.2.4. The SEC's position

In addition, similar positions have been taken by the Securities and Exchange Commission (SEC) and the Federal Trade Commission (FTC), as discussed at 5.3.35.3.

17.8. People Definition

Each party In respect to any individual or organization ("A"), treat the term A's "people" (whether or not capitalized) as referring to any individual who, at the time in question, falls into one or more of the following categories:

  1. an employee of A;
  2. an officer or director of A (if A is a corporation);
  3. a holder of a comparable position (if A is an organization of another type, such as a limited liability company); and/or
  4. any other individuals expressly specified in the Con­tract, if any.
Note

().  This is a convenience definition, to avoid having to list (possibly repeatedly) all of the above categories.

See also Affiliate Definition (20.1).

17.9. Nonsolicitation of Employees Protocol

17.9.1. The: Parties: The Protected Party and the Obligated Party

This Protocol concerns parties to the Con­tract, referred to respectively as the "Protected Party" — whose specified employees are "off limits" as stated below — and the "Obligated Party" clearly identified as such in the Con­tract.

Note

().  Drafting suggestion: In the Con­tract, explicitly state which party is which.

The business context: A party to a contract might worry that another party to a contract could try to "poach" the first party's employees who knew the first party's trade secrets. Example: That was an issue in a dispute that led to Syntel Sterling (2d Cir. 2023). The first party therefore might want the other party to commit to not doing so — especially after the contract expires or is terminated. See Syntel Sterling Best Shores Mauritius Ltd. v. TriZetto Group Inc., 68 F.4th 792 (2d Cir. 2023).

Caution: Nonsolicitation covenants of all stripes can be problematic and even dangerous; this is one area where it's important to check the law of the relevant jurisdiction.

17.9.2. Definition – Nonsolicitation Period

When agreed to, this Protocol applies during the "Nonsolicitation Period," which: (1) begins on the effective date of the Con­tract; and (2) ends at 12 midnight at the end of the day on the date "one year" after termination or expiration of the Con­tract.

Note

().  Drafters will very-likely want to custom-tailor the definition of Nonsolicitation Period.

You might not be able to enforce a nonsolicitation provision if you don't include a "sunset date." Example: In Brown & Root (La. App. 2024), the court affirmed partial summary judgment that "the non-solicitation of employees provision of a separation agreement violative of established public policy" because it did not include "any durational limit." The court also affirmed the trial court's refusal to blue-pencil (that is, reform) the non-solicitation provision because "reform of this Agreement would require fashioning a reasonable term for Promise Number 9 where the entire Agreement is purposely silent as to any term." Brown & Root Indus. Svcs., LLC v. Farris, 392 So.3d 424 (La. App.) (affirming partial summary judgment), writ denied, 395 So.3d 1183 (La. 2024).

17.9.3. Recruiting restriction

Obligated Party: During the Nonsolicitation Period, don't solicit for employment any employee of the Protected Party who, in any significant way, was involved in the Protected Party's activities under the Con­tract.

Note

().  As with noncompetition clauses (see 22.5), the enforceability of nonsolicitation clauses varies considerably by (U.S.) state; drafters should definitely do their homework and/or consult legal counsel.

And parties should be very cautious about so-called "no-hire" clauses, as opposed to no-solicit clauses — the former have led to unwanted attention from the U.S. Department of Justice, as discussed at 22.2.

17.9.4. Exception: Ordinary general recruiting

Obligated Party: Your nonsolicitation obligation under this Protocol doesn't cover help-wanted advertisements and recruitment searches that:

  1. are directed to the general public (or particular segments of the general public, e.g., to people having particular skills); and
  2. don't specifically target employees of the Protected Party.
Note

This exception for non-targeted general recruiting activities is widely used.

17.9.5. Partial exception: Fired- or laid-off employees

Obligated Party: For any Protected-Party employee whose employment is terminated by the Protected Party, your nonsolicitation obligation under this Protocol will end at the end of the day on the date one month after the employee's last day of that employment.

Note

This exception is less-often seen than that of § 17.9.4, but it often makes business sense.

17.9.6. Survival of this Protocol

  1. Obligated Party: Your nonsolicitation obligations under the Con­tract will continue in effect even if the Con­tract itself, or your business relationship with the Protected Party under the Con­tract, is terminated or expires.
  2. In case of doubt: This section isn't intended to expand or limit any other survival provision in the Con­tract.
Note

This section is informed by an analogous holding, in the Eighth Circuit's 2021 Miller decision, that a noncompetition provision in an employment agreement didn't survive termination of that agreement. See Miller v. Honkamp Krueger Fin. Servs., Inc., 9 F.4th 1011 (8th Cir. 2021) (reversing and vacating preliminary injunction).

18. Termination

18.1. Survival of Certain Terms Protocol

Survival clauses can be important to parties; here are a couple of examples:

  • Parties have seen their trade-secret rights in confidential information be destroyed when their confidentiality agreements (a.k.a. "NDAs") expired and did not provide for the recipients' confidentiality obligations to continue in effect (see 5.3.5).
  • If a contract allows a party to audit another party's books, termination or expiration of the contract could immediately mean no more audits — not even for transactions that occurred during the term of the contract. Example: This happened to a union whose collective-bargaining agreement ("CBA") with an employer was terminated. See New England Carpenters Central Collection Agency v. Labonte Drywall Co., 795 F.3d 271 (1st Cir. 2015).

18.1.1. Lighthouse Protocol

18.1.1.1. Certain terms survive termination or expiration

Unless the Con­tract clearly says otherwise, termination or expiration of the Con­tract doesn't terminate any provision of the Con­tract (if any) that falls in one or more the following categories; all such provisions survive any such termination or expiration:

  1. attorney fees and expenses — and those terms (if any) will also survive the entry of a judgment, arbitration award, or other decision in a contested proceeding;
  2. audits;
  3. confidentiality;
  4. defense against third-party claims;
  5. dispute management;
  6. indemnification;
  7. insurance requirements;
  8. intellectual-property ownership;
  9. non-competition;
  10. non-solicitation;
  11. representations, warranties, and disclaimers of the same;
  12. warranty rights.
18.1.1.2. Existing claims for breach survive

Claims for breach of the Con­tract before termination or expiration will also survive.

18.1.1.3. How long will these terms survive?

Each surviving term will continue in effect for the lesser of (i) 30 years, (ii) any time limit stated in the provision itself, and (iii) the maximum time allowed by law.

Note

Caution: Perpetual survival clauses might be problematic, as discussed at 18.1.2.4.

18.1.2. Additional notes

18.1.2.1. The wording of a survival clause could be crucial

Example: In an Eighth Circuit case, an employee of a company terminated her employment agreement, as the agreement expressly allowed her to do. To the company's surprise, the termination had the side effect of terminating the employee's contractual obligation not to compete with the company. That's because the noncompetition covenant stated that it would survive termination of employment, but it didn't say that it'd survive termination of the employment agreement — so, when the employment agreement was terminated, the employee's noncompetition obligation died with it. See Miller v. Honkamp Krueger Fin. Svcs., Inc., 9 F.4th 1011 (8th Cir. 2021) (vacating preliminary injunction).

18.1.2.2. Caution: "By their nature" survival clauses are vague

Some agreements include a survival provision along the following lines:

All other provisions of this Agreement that, by their nature, should extend beyond termination or expiration of this Agreement will survive any such termination or expiration.

Such language, however, could be dangerously vague.

18.1.2.3. Are there any unwitting exceptions?

Example: In a Pennsylvania federal-court case, a company fired an employee, then later sued her for allegedly breaching various obligations in her employment agreement (confidentiality, noncompetition, nonsolicitation). But there was a problem: The survival clause in the employment agreement stated:

Upon termination, all obligations of [the company] and Employee under this Agreement will cease as of the date of termination. Employee's obligations under Sections 5 and 6 and under Exhibit B shall survive willful termination of employment by Employee only.

The court granted summary judgment in favor of the former employee, dismissing the company's claims against her. EMC Outdoor, LLC v. Stuart, No. 17-5172, (E.D. Pa Mar. 31, 2021) (extra paragraphing added).

18.1.2.4. A perpetual survival clause might be unenforceable

The following is adapted — cleaned up and with very-light format editing — from the court's order (with extensive citations) in Meta Platforms, Inc. v. Bright Data Ltd., No. 23-cv-00077-EMC, part III.A.4.f.i, slip op. at 28-29 (N.D. Cal. Jan. 23, 2024). In that order, Judge Chen granted partial summary judgment that Facebook's prohibition of Web-data "scraping" did not bar such scraping after termination of Facebook user account. The opinion includes extensive citations. No copyright is claimed in the opinion text.

Courts disfavor the application of a survival clause which purport to extend in perpetuity. The U.S. Supreme Court has advised that courts should not construe ambiguous writings to create lifetime promises.

California courts have applied this presumption against perpetual agreements to various contexts, holding, for instance, in real estate contexts that a construction conferring a right in perpetuity will be avoided unless compelled by the unequivocal language of the contract.

For this reason, courts generally hold that, for a survival clause to be valid and enforceable, the clause must be limited in scope as to its geography and duration.

Courts have invalidated or limited the scope of perpetuity provisions in other contexts as well. [Citations to cases involving perpetual nondisclosure covenants omitted.]

Survival clauses are generally limited to conduct that arises out of or shares a nexus to, the agreement.

* * *

The structure of the Terms thus supports Bright Data's construction of the survival clause as an enforcement mechanism, not an independent creator of lifetime bans.

* * *

It would be absurd that someone who opens a Facebook account for seconds, or even minutes, before deleting that account would be permanently giving up important legal rights the rest of society enjoys, and that they too enjoyed just minutes before, with no opportunity to ever get them back. While visitors to Facebook would not be contractually barred from automated scraping of public information, a user who briefly signs up with Facebook for entirely legitimate reasons would be barred for life from that same conduct. [At text acc. n.7.]

18.1.2.5. Further reading

See generally Jeff Gordon, Night of the Living Dead Contracts (2008).

18.2. Termination At Will Protocol

18.2.1. Each party may terminate at will.

If the Con­tract clearly adopts this Protocol, THEN: Each party (each, a "Terminating Party") is free terminate "at will" or "for convenience" (the two quoted terms are intended to be essentially synonyms) one or more of the following:

  1. the Con­tract, and/or
  2. one or more transactions or relationships resulting from the Con­tract.

18.2.2. The Con­tract could restrict termination at will.

Absent a clear restriction in the Con­tract, the Terminating Party is free to terminate:

  1. at any time before the Con­tract has expired or otherwise been terminated; and
  2. in the Terminating Party's sole discretion.

18.2.3. Additional notes

18.2.3.1. Caution: Termination at will might be a bad business idea

An at-will termination provision might not make business sense — a Harvard Business Review article (co-authored by an economics Nobel laureate) points out that:

Termination-for-convenience clauses create perverse incentives for suppliers to not invest in buyer relationships.

"A 60-day termination for convenience translates to a 60-day contract," one CFO at a supplier told us. "It would be against our fiduciary responsibility to our shareholders to invest in any program for a client with a 60-day termination clause that required longer than two months to generate a return."

The implications for innovation are obvious. "Buyers are crazy to expect us to invest in innovation if they do the math." David Frydlinger, Oliver Hart, and Kate Vitasek, A New Approach to Contracts, Harv. Bus. Rev., Sept.-Oct. 2019 (emphasis and extra paragraphing added), archived at https://perma.cc/T2TJ-3ENN.

18.2.3.2. Customer termination at will could cause problems for a Vendor

Suppose that a services provider ("Vendor"), upon agreeing to a statement of work, had invested money to find, recruit, and train extra people to do the work.

Or perhaps the Vendor had invested in extra equipment that would be needed.

In either of these cases, a sudden termination at will by the Customer could leave the Vendor stuck with:

  • the salaries of the extra workers who would now be unable to earn revenue from the Customer's project and might not have other billable work to do; and/or
  • the costs of the extra equipment.
18.2.3.3. Negotiate restrictions on termination at-will?

If your client will be making a significant investment of time or money in the Con­tract, then you might want to try to negotiate restrictions on the other party's right to terminate at will, so as to allow your client at least some minimum time in which to try to recoup at least some part of that investment.

Such restrictions could include, for example:

1.  imposing a minimum advance notice requirement;

2.  allowing termination at will only (for example):

  • after a certain amount of time has elapsed, or no sooner than an earliest permissible date, or after specified milestones were reached — this might allow a vendor to recover some of its up-front investment from the customer's payments;
  • a minimum advance-notice period — in the case of a services agreement, this would give the provider some time to try to find other work for the provider's people who were assigned to the customer's project (and thus help avoid layoffs); and/or
  • after one or another party has achieved specified performance targets;
  • if the terminating party pays a specified early-termination fee; and/or
  • for good reason (preferably but not necessarily specified in the Con­tract).
18.2.3.4. Legally, at-will termination might be "the rule"

In a dispute between Pepsi Cola and one of its independent bottlers, the Second Circuit noted:

Under New York law, it is well settled that a contract of indefinite duration is terminable at will unless the contract states expressly and unequivocally that the parties intend to be perpetually bound. …

If it appears that no termination date was within the contemplation of the parties, or that their intention with respect thereto cannot be ascertained, the contract will be held to be terminable within a reasonable time or revocable at will . . . .

Contracts of exclusive agency and distributorship are terminable at will in the absence of an express provision of duration. … Compania Embotelladora Del Pacifico, S.A. v. Pepsi Cola Co., 979 F.3d 239, 245, 246 (2d Cir. 2020) (affirming summary judgment in favor of PepsiCo) (cleaned up, citations omitted, emphasis and extra paragraphing added). To similar effect, see also, e.g., State v. Dovetel Communication, LLC, No. S25A0635, slip op. (Ga. Sept. 30, 2025) (reversing and remanding declaratory judgment in favor of broadband internet service providers: contracts between providers and state were terminable at will by state); Glacial Plains Coop. v. Chippewa Valley Ethanol Co., 912 N.W.2d 233, 236 (Minn. 2018) (reversing lower courts).

(Drafters should consider what would constitute "a reasonable time" and "reasonable notice" in assessing what might be desired by way of restrictions on termination at will.)

Counterexample: Concerning a contract for sharing songwriting royalties for songs by the 1970s band Supertramp: The Ninth Circuit held that the band's two principal songwriters could not terminate the contract at will — and thus stop sharing their songwriting royalties with other band members and the band's manager — because under California law, the contract had an implied term, to wit: as long as the songs continued to generate royalties. The opinion extensively discusses factors that the court regarded as establishing an implied term. See Thomson v. Hodgson, 150 F.4th 1097, 1103-06 (9th Cir. 2025) (reversing judgment on jury verdict for defendants and remanding with direction to enter judgment for plaintiffs on issue of liability).

The opinion also mentions how copyright royalties typically work in the music business — which led to the band members' entering into the contract in suit because the two songwriting members were making a lot more money than the other members and the manager. See id., 150 F.4th at 1107.

(Judge Wardlaw's law clerk — or perhaps the judge herself — might be a Supertramp fan: The introduction to the opinion is sprinkled with the band's song titles.)

18.2.3.5. But: At-will termination might be restricted by law

The law might provide some contractual fences around an automatic termination-at-will right; as the Second Circuit noted in its Pepsi decision:

… In some circumstances, New York law imposes a reasonable-duration requirement on exclusive distribution agreements that are otherwise terminable at will.

Such a requirement may arise in circumstances such as these where a distributor must invest in equipment, materials, and other assets to perform its obligations under the contract. Compania Embotelladora, 979 F.3d at 245, 246 (2d Cir. 2020) (cleaned up, citations omitted, emphasis added).

Relatedly: A termination at will might be held to violate the implied covenant of good faith and fair dealing — if that implied covenant is recognized in the jurisdiction in question. Example: In Davidson Oil (10th Cir. 2024), the City of Albuquerque was a party to a requirements contract in which Davidson Oil would supply all of Albuquerque's needs for gasoline and diesel fuel at a fixed price.

  • When fuel market prices dropped, Albuquerque exercised a termination for convenience provision in its contract with Davidson Oil.
  • But Davidson Oil had entered into hedge contracts to cabin its own risk from market fluctuations — and the city knew this.
  • Davidson Oil sued the city for breach of the implied covenant of good faith and fair dealing.

The court affirmed summary judgment awarding Davidson Oil the value of the hedge contracts. Davidson Oil Co. v. City of Albuquerque, 108 F.4th 1226 (10th Cir 2024).

(Reminder to students, Texas doesn't have a general implied covenant of good faith and fair dealing.)

In fact, termination at will might be prohibited by law, for example by "hometown" protective legislation. As one example, the Minnesota Termination of Sales Representatives Act imposes restrictions on a manufacturer's right to terminate a sales representative. Minn. Stat. § 325E.37 discussed in Engineered Sales Co., 980 F.3d 597 (8th Cir. 2020).

Moreover, some countries might restrict a party's right to terminate a contract. See Bailly & Haranger (2020) (French law; archived at https://perma.cc/4QB4-5BV9).

18.2.3.6. Special case: Click-to-cancel for online agreements?

In October 2024 the Federal Trade Commission announced a new "click to cancel" rule, to take effect in the spring of 2025, "that will require sellers to make it as easy for consumers to cancel their enrollment as it was to sign up." At this writing (late March 2025), it's unclear whether the FTC — now dominated by Republican appointees — will modify or repeal this rule in the face of pressure from corporate interests.

18.3. Termination for Change of Control Protocol

18.3.1. Either party may terminate for a change of control.

Either party, referred to as "the Terminating Party," may terminate the Con­tract if the other party has a "change of control" (as defined below).

Note

A party to a contract might want the right to terminate the contract (or a purchase order, or a statement of work, etc.) if the other party undergoes a "change of control" — for example being acquired by one of the terminating party's competitors.

This could be especially true if the contract calls for the terminating party to share its trade secrets or other proprietary information with the other party, because of the fear that the acquiring competitor might gain access to the terminating party'sinformation.

18.3.2. Termination is effective upon notice.

Termination will be effective immediately when the Terminating Party's notice of termination to the other party becomes effective in accordance with Protocol 3.14.

18.3.3. Deadline for change-of-control termination

On any occasion when the Terminating Party has the right to terminate under this Protocol, the Terminating Party WAIVES that right for that occasion — and the Terminating Party must not assert otherwise — if the Terminating Party's notice of termination to the other party has not become effective on or before the later of:

  1. three months after the date that the Terminating Party first learned, via any source, or reasonably should have known, that the other party's change of control had become effective; or
  2. six months after the effective date of the change of control.
Note

().  This deadline forces the terminating party to make up its mind. It follows the maxim that contract rights and obligations should generally have a "sunset," so as not to be indefinitely hanging over other parties' heads.

Subdivision 1's deadline is written as "three months" after learning of the event, instead of "90 days," to spare the reader from having to count days. On that subject, see the definition of month at Protocol 20.27.

The countdown clock starts ticking on subdivision 1's termination deadline when the terminating party first learns of the triggering event affecting the other party. To be sure: The terminating party might prefer for its termination countdown clock to start running only upon formal notice of the triggering event from the other party. That, though, might be too burdensome for the other party to manage.

In contrast: Subdivision 2's "outside" termination deadline has in mind that if the terminating party hasn't seen fit to terminate within the stated period — for example, because the terminating party simply hasn't noticed any material ill effects from a triggering event — then perhaps the terminating party right to terminate ought to quietly go away.

18.3.4. The voting-power trigger for a change of control is 50%.

For purposes of this Protocol, the term "change of control" refers solely to a change of ownership of the power to vote more than 50% of the voting power entitled to vote for members of a party's board of directors (or equivalent body in a non-corporate organization).

Note

Some clauses of this type have even lower thresholds for terminating for a change of control.

18.4. Termination for Insolvency Protocol

18.4.1. Lighthouse Protocol

18.4.1.1. Either party can terminate under this Protocol.

If the Con­tract clearly says so: Each party (each, a "Terminating Party") is free to terminate the Con­tract, effective immediately upon notice to the other party in accordance with Protocol 3.14, if one or more of the following things occurs:

  1. the other party ceases to do business in the normal course;
  2. the other party becomes insolvent;
  3. the other party admits in writing its inability to meet its debts or other obligations as they become due;
  4. the other party makes a general assignment for the benefit of creditors;
  5. the other party files a voluntary petition for protection under the bankruptcy laws or similar laws of the relevant jurisdiction, or to effect a plan or other arrangement with creditors;
  6. the other party becomes the subject of an involuntary petition under the bankruptcy laws (or a similar petition or other filing under the laws of the relevant jurisdiction), and the same is not vacated, released, dismissed, stayed, reversed or otherwise overturned, or bonded off before the end of 60 days after the date of the petition or other filing; or
  7. the other party has a receiver, administrative receiver, administrator, liquidator, trustee in bankruptcy, or similar functionary in the relevant jurisdiction, appointed for the other party's business or assets.
Note

Subdivisions 5 through 7: See the notes at 31.2 about the effect of bankruptcy on contracts under the (U.S.) Bankruptcy Code of 1978.

18.6. Termination for Material Breach Protocol

18.6.1. Lighthouse Protocol

18.6.1.1. Either party can terminate under this Protocol.

If the Con­tract clearly adopts this Protocol, THEN: By following the procedure in this Protocol, the specified party (the "Terminating Party") is free to terminate the Con­tract if another party materially breaches that party's its obligations under the Con­tract.

Note

().  This Protocol fleshes out a general doctrine under American law, namely that a material breach by one party excuses the other party from continuing to perform its own obligations under the contract. See, e.g., Walmart, Inc., v. Cuker Interactive, LLC, 949 F.3d 1101, 1111-12 (8th Cir. 2020) (affirming judgment on jury verdict in favor of Cuker).

Pro tip: It might be feasible to leave out a material-breach termination provision. That's because at common law, if a party breaches a contract in a way that deprives the other party of its reasonably-anticipated benefit from the contract, then the other party may suspend its own future performance. See, e.g., Earth Power A/C and Heat, Inc. v. Page, 604 S.W.3d 519, 524 (Tex. App.–Houston [14th Dist.] 2020) (reversing and rendering to restore jury verdict, awarding attorney fees to contractor per contract). ]

In contrast, if a breach is not material, then the other party must continue performing (but may sue for damages for the breach). See id.

Still, many contracts spell out this right anyway so as not to leave it up to "interpretation" of the contract — which could result in costly, time-spending "creative" lawyering by one or both parties. Such contracts generally state that if a breaching party doesn't cure a material breach in a stated amount of time, then the other party may terminate the contract.

Caution: Absent a contract provision such as this Protocol, under the general law the other party might not necessarily be able to terminate the contract — as opposed to suspending its own performance — just because of the first party's material breach; that could depend on all the surrounding circumstances.

Caution: This Protocol uses the phrase "the Terminating Party" and not "the non-breaching party." The latter term can cause serious problems if both parties are in breach, as discussed at 18.9.2.2.

Note that under section 18.9.1.1 of Protocol 18.9, the Terminating Party could terminate just a purchase order, statement of work, etc., instead of terminating the Con­tract as a whole.

18.6.1.2. The Terminating Party gives notice of breach.
  1. Before terminating for material breach, the Terminating Party gives the breaching party notice of the breach as provided at Protocol 3.14.
  2. The notice of breach states at least the following:
    1. the circumstances of the breach, in reasonable detail (as the Terminating Party then understands the circumstances); and
    2. how long the Terminating Party asserts that the cure period will be (if any), as set forth at § 18.6.1.3 below.
Note

Sometimes a breaching party won't dispute that it's in breach. But it still makes sense to require notice, to fix the start of the putative cure period, if any (see the next section).

18.6.1.3. Cure periods — if any — vary with the type of breach.
  1. The Terminating Party loses its right to terminate (and so it doesn't try to do so) if the materially-breaching party has cured the breach, and advised the Terminating Party of the same in writing — e.g., via email or text — with reasonable supporting evidence, no later than the following times after the effective date of the Terminating Party's notice of breach:
    1. Nonpayment of an amount due under the Con­tract: Five business days.
    2. Missed deadline for which the Con­tract unambiguously states, in effect, that time is of the essence: No cure period.
    3. Other, curable missed deadline stated in the Con­tract: Five business days.
    4. Other, curable breach: Ten business days.
    5. Breach that clearly is not capable of being cured: No cure period.
    6. Other? The Con­tract could specify other cure periods for breach, including but not limited to the types of breach listed in this section 18.6.1.3.
  2. If a material breach is of a kind that's listed above as having no cure period, THEN: The Terminating Party could terminate immediately by notice if desired.
Note

().  The cure periods listed here are fairly typical of those in negotiated contracts.

Pro tip: Drafters should consider avoiding one-size-fits-all cure periods, e.g., "30 days after the notice of breach."

18.6.1.4. A separate notice of termination is (normally) required.
  1. To terminate for material breach, the Terminating Party gives the breaching party notice of termination which describes, with reasonable specificity:
    1. the basis for termination, and
    2. the putative effective date of termination.
  2. Exception: If the breach is of a type that clearly can't be cured (or that is agreed not to have a cure period), THEN: The notice of breach could also state that termination is effective immediately.
Note

().  Pro tip: A notice of termination should be clear that it is a termination notice. That's because neither party will want to have to litigate whether a particular communication qualified as a termination notice, as happened in the First Circuit's New England Carpenters case, discussed in the comment to section 4.3.28 (survival clause) of Protocol 4.3 (audit protocol).

Subdivision 2: The parties might disagree over whether a particular breach was or wasn't curable. The "clearly can't be cured" language tries to address this possibility — but the parties could just as easily disagree about that, too.

18.6.1.5. The Con­tract could stipulate that particular breaches would be "material."
  1. If the Con­tract states (in effect) that a certain type of breach will be material, THEN: Each party treats that statement as conclusive (and doesn't assert otherwise).
  2. If the parties don't agree whether a particular type of breach of the Con­tract was (or would be) "material," THEN: in determining the materiality of such a breach, the parties take into account the factors listed in the Restatement (Second) of Contracts § 241 (or its successor, if any):
    • considering the Con­tract as a whole; and
    • with no single factor necessarily being decisive.
18.6.1.6. Multiple small breaches could add up to a material breach.

In appropriate circumstances, if the breaching party develops a track record of multiple non-material breaches — related or not, cured or not — THEN: Those non-material breaches could collectively add up to a material breach of the Con­tract when considering the Con­tract as a whole.

Note

At some point, a party might respond to a series of non-material breaches by (figuratively) slapping the table and saying, "Enough is enough!" Example: Language to that effect is found in section 16.3.1(1)(c) of the master service agreement in the Indiana v. IBM case cited above. See Indiana v. IBM, 51 N.E.3d at 155.

Example: Retail giant Walmart found itself liable for breach of a contract with a digital marketing agency company that Walmart had hired to make a Walmart-related Web site software-development company for a fixed fee; the Eighth Circuit noted that:

Walmart failed to make the second contract payment on time.

It continually demanded that Cuker take on additional tasks and threatened to withhold payment for in-scope work if Cuker did not comply. …

There is more than sufficient evidence in this record from which a reasonable jury could find that Walmart materially breached the contract and thereby excused Cuker's performance under the contract. Walmart, Inc., v. Cuker Interactive, LLC, 949 F.3d 1101, 1111-12 (8th Cir. 2020) (affirming judgment on jury verdict in favor of Cuker).

18.6.1.7. There could be a deadline for terminating for material breach.

The Con­tract could impose a deadline for terminating for material breach.

Note

The breaching party might argue that it shouldn't have to live forever under a Sword of Damocles for a breach — and that if the terminating party can't be bothered to terminate before an agreed deadline, then the breach likely didn't harm the terminating party that much.

18.6.1.8. The right to terminate could be lost even with no stated deadline.

Even without an agreed termination deadline, the law might consider the Terminating Party to have waived, or otherwise lost its right, to terminate for material breach.

Note

().  If a party keeps doing its job under the Con­tract even after a material breach by the other side, then a court might hold that first party has waived its right to terminate. Example: In its 2024 Outbox Systems opinion, the Fourth Circuit noted that:

… the general rule that one party's uncured, material failure of performance will suspend or discharge the other party's duty to perform does not apply where the latter party, with knowledge of the facts, either[:]

  • performs or indicates a willingness to do so, despite the breach, or
  • insists that the defaulting party continue to render future performance. Outbox Sys., Inc. v. Trimble, Inc., No. N21C-11-123, slip op. at part VI.A.2, text acc. n.114 (Del. Super. Ct. Apr. 30, 2024) (decision after trial; cleaned up, lightly edited).

Relatedly: If you want to terminate because the other party is in material breach, but you yourself are in breach, then you might not be able to use the "but they breached first!" argument — i.e., that the other party's "first material breach" justified your own material breach — if the you waived that possibility. This was an issue, for example, in the Fourth Circuit's 2024 Remy Holdings case. See, e.g., Remy Holdings Int'l, LLC v. Fisher Auto Parts, Inc., 90 F.4th 217, 230-34 (4th Cir. 2024) (citing Virginia law; affirming summary judgment and rejecting Remy's contention that Fisher had waived first-material-breach defense).

18.6.1.9. A party terminate for breach even if it continues its own performance.

The Terminating Party may terminate for material breach — even if the Terminating Party continues its own performance under the Con­tract — if it does so within a reasonable time.

Note

This section addresses one what-if possibility, explained by the Illinois supreme court in its 2023 Hawthorn Woods opinion:

¶ 52 All of this is to say that, following a material breach, the injured party reaches a fork in the road: it may either[:]

  • continue the contract (retain its benefits of the bargain and sue for damages) or
  • repudiate the agreement (cease performing and sue for damages).

If the party elects to continue with the contract, it cannot suspend performance later and then claim it had no duty to perform based on the first material breach.

  • This election converts the material breach to a "partial" breach.
  • The injured party may sue for any damages caused by the partial breach, but having elected to keep the contract in force, the injured party must continue to perform the contract on pain of likewise incurring liability for a breach. PML Devel. LLC v. Village of Hawthorn Woods, 2023 IL 128770 226 N.E.3d 1163, 1175-76 (2023) (partially reversing and remanding trial-court judgment; presentation edited).
18.6.1.10. Termination (usually) isn't an exclusive remedy for the breach.

Unless the Con­tract expressly states otherwise: Termination, in and of itself, won't preclude the Terminating Party from seeking other remedies against the breaching party for the breach(es) that led to termination (to the extent consistent with the Con­tract and the law).

Note

Note the phrasing, will not preclude, so as not to (arguably) imply that other remedies are indeed available to the terminating party — that's because other remedies might otherwise indeed be precluded by the Con­tract (see Protocol 21.18) and/or by the law.

18.6.2. Additional notes

18.6.2.1. When would a breach be incurable?

In a UK case, the court of appeal reviewed case law about what might cause a breach of contract to be incapable of remedy, using some colloquial phrases such as "putting the genie back in the bottle." See Kulkarni v Gwent Holdings, Ltd., [2025] EWCA Civ 1206 ¶¶ 111-14 (affirming judgment that breach was capable of remedy).

18.7. Termination for Personnel Changes Protocol

18.7.1. The {Protocol

18.7.1.1. Either party may terminate under this Protocol.

If the Con­tract clearly adopts this Protocol, THEN: The stated party (each, a "Terminating Party") is free to terminate the Con­tract — by notice to the other party in accordance with Protocol 3.14 — after any material change among the supervisory personnel of the other party who are directly and materially involved in the other party's performance under the Con­tract.

Note

A customer might want to use this Protocol in a contract with a small-company or startup-company supplier whose ability to continue to perform might be called into question if too many closely-involved key people were to leave. But the customer's right to do so should probably "sunset" in relatively-short order, so as to avoid unfair disruption to the supplier.

18.7.1.2. There's a deadline for termination under this Protocol.

On any occasion when the Terminating Party has the right to terminate under this Protocol, the Terminating Party WAIVES that right — for that occasion — if the Terminating Party's notice of termination to the other party hasn't become effective on or before the later of:

  1. ten business days after the date that the Terminating Party first learned, via any source, or reasonably should have known, of the most-recent change of the other party's personnel in question; or
  2. six months after the most-recent personnel change in question.
Note

Subdivision 2 is another example of putting a "sunset" on a right: If — after that much time has passed — the terminating party hasn't seen fit to terminate because of the personnel change, then it seems unlikely that the terminating party is actually being harmed by the change.

18.8. Termination for Reputation Risk Protocol

18.8.1. The {Protocol

18.8.1.1. Each party may terminate under this Protocol.
  1. If this Protocol is clearly agreed to, THEN: The specified party (the Terminating Party) is free to terminate the Con­tract —
  2. effective immediately upon notice to the other party in accordance with Protocol 3.14,
  3. if the Terminating Party reasonably determine that one or more "Reputation Risk Actions," defined at § 18.8.1.2 below,
  4. previously taken by the other party or any of the other party's affiliates,
  5. have created a not-insubstantial risk
  6. to the Terminating Party's business reputation, and/or that of any of the Terminating Party's own affiliates.
Note

In today's global economy, "offshore" companies do a great deal of manufacturing for U.S. and European firms. Those companies might not always comply with First-World standards of safety, employee treatment, and the like, which could result in adverse publicity for the offshore companies' customers.

Example: Apple and HP were forced to deal with news stories about worker suicides in factories owned by the giant Chinese electronics contract manufacturer Foxconn.

Example: Longtime Subway sandwich shop pitchman Jared Fogle agreed to plead guilty to child-pornography charges, among others. Subway had previously suspended its relationship with Fogle. The case, along with the attendant bad publicity for the already-troubled Subway, is a sad reminder of the value of including an appropriate "termination for business reputation risk" clause in a contract of that nature.

Some similar stories are summarized in the following footnote:31

18.8.1.2. Definition: What would qualify as a "Reputation Risk Action"?

For purposes of this Protocol, the term "Reputation Risk Action" refers to any action (for this purpose including omissions) or series of actions, whether related or unrelated, where the action is (i) intended by the actor, or (ii) reasonably likely, to do one or more of the following:

  1. libel or slander another person;
  2. put another person in a false light;
  3. threaten, embarrass, harass, or invade the privacy of another;
  4. impersonate another or promote, encourage, or assist in, such impersonation;
  5. offend a reasonable person on racial- or ethnic grounds;
  6. engage in conduct prohibited by law, including for example the U.S. Foreign Corrupt Practices Act;
  7. encourage activities prohibited by law, including (for example) bribery; identity theft; child pornography; and terrorism;
  8. engage in tortious conduct; and/or
  9. mistreat a person, or promote, assist in, or encourage such mistreatment.
Note

The above "laundry list" of Reputation Risk Actions is adapted from language used in a number of on-line terms of service; see Zachary West, Morality clauses in domain registration (zacwe.st 2011).

18.8.1.3. This Protocol doesn't require any action by any party.

This Protocol establishes only the Terminating Party's conditional right to terminate the Con­tract; in itself, this Protocol doesn't obligate either party to do, or not do, anything.

18.8.1.4. No contract liability for Reputation Risk Action alone.

No party would be liable under the Con­tract, in damages or otherwise, for any Reputation Risk Action that does not otherwise breach the Con­tract — but this doesn't rule out possible liability on other grounds (for example, for tortious behavior and/or criminal action).

Note

For discussion of this point (in the context of "codes of conduct"), see 9.5.9.

18.8.1.5. There's a deadline for termination under this Protocol.

On any occasion when the Terminating Party has the right to terminate under this Protocol, the Terminating Party WAIVES that right — for that occasion — if the Terminating Party's notice of termination to the other party hasn't become effective on or before the later of:

  1. the date three months after the date that the Terminating Party first learned, via any source, or reasonably should have known, of the most-recent Reputation Risk Action; or
  2. the date six months after the date of that most-recent action.

Terminating Party: On any occasion when you have the right to terminate under this Protocol, you'll lose that right — for that occasion — if your notice of termination to the other party hasn't become effective on or before exactly 12 midnight at the end of the day on:

  1. the date ten business days after the date that you first learn, via any source, or reasonably should have known, of the most-recent Reputation Risk Action; or
  2. the date three months after the date of that most-recent action.
Note

This is another "sunset" provision — see the discussion at 18.7.1.2

18.9. Termination General Provisions

Every contractual relationship will come to an end eventually: by the completion of the transaction; by expiration with the passage of time; by the "disappearance" of one or both parties; or by the action of one or both parties. This Protocol sets out fairly-standard general ground rules for any termination or expiration.

(Pro tip: Contracting parties should ideally try to plan for orderly winding up of their relationship by considering what actions — by whom — each party might want to have happen.)

18.9.1. Lighthouse Protocol

18.9.1.1. Termination needn't be all-or-nothing.

Each party: Unless the Con­tract clearly states otherwise: Any time that you have the right to terminate the Con­tract, you could instead terminate one or more of the following specific items, to the extent that such items exist under the Con­tract:

  1. a transaction, for example, a purchase order or a statement of work for services;
  2. a grant, for example, a leasehold interest or a license;
  3. a relationship, for example, a distributorship; and/or
  4. the exclusivity of a grant.
Note

().  Background: Drafters should think about whether termination of the Con­tract is what the client really wants, as opposed to just terminating selected rights and/or obligations under the Con­tract.

Subdivision 4 — caution: It might be undesirable to terminate just the exclusivity of a grant or relationship, e.g., the exclusivity of a reseller relationship, while leaving the underlying reseller relationship in place on a nonexclusive basis: The continued existence of the nonexclusive relationship would preclude the grantor from offering a new exclusive grant.

18.9.1.2. Certain wrap-up actions might be agreed to.

Each party: The Con­tract could require (or allow) you to take certain specific actions, or to have other specific rights or obligations, upon a termination.

(This would be in addition to any provisions subject to a survival provision in the Con­tract.)

Note

This is a reminder to drafters to consider wrap-up provisions such as those in Protocol 18.11.

18.9.1.3. Expiration would count as a termination.

All parties:

  1. If the Con­tract expires — or, if applicable, a transaction, grant, or relationship under the Con­tract expires — the expiration would have the same effect as a termination unless it was otherwise unambiguously clear from the context.
  2. For this purpose, the term expiration includes, without limitation, automatic expiration due to a party's exercising a right to opt out of an automatic-extension or ‑renewal provision.
Note

This is intended as a guardrail against future "creative" arguments to the contrary. Example: One example of expiration-as-termination attracted considerable local publicity in a 2020 case in the San Francisco Bay Area in California, where:

  1. The NBA's Golden State Warriors basketball team elected not to exercise an option to renew the team's lease of the Oakland-Alameda County Coliseum, where the team had played for years.
  2. An arbitrator held that the lease's expiration due to nonrenewal was tantamount to a termination by the Warriors.
  3. That termination triggered an obligation for the team to continue making payments on debt incurred by the government agency that owned the Coliseum.

The arbitrator's award was upheld by a district court, whose decision was affirmed on appeal. See Oakland-Alameda Cty. Coliseum Auth. v. Golden State Warriors, LLC, 53 Cal. App. 5th 807, 267 Cal. Rptr. 3d 799 (2020).

18.9.1.4. Notice of expiration isn't needed.

Each party: You don't have to give another party notice of an upcoming expiration unless the Con­tract clearly says otherwise.

Note

Pro tip: Even if there's no requirement to give notice of expiration, it might well be a good customer-relations practice for a vendor to give such notice anyway, to increase the chances of getting a renewal and/or to "upsell" the customer.

18.9.1.5. Termination will have certain automatic effects.

Each party: Any termination would automatically do the following unless the Con­tract clearly provided otherwise:

  1. it'd cancel all of your relevant, respective, post-termination rights and obligations;
  2. it'd cancel any right that any party has to continue performance of its relevant pre-termination obligations; and
  3. not affect any party's claim for pre-termination breach, nor any related rights or remedies.
Note

Drafters will want to consider "survival" provisions such as Protocol 18.1.

Note

This is a "savings clause" inspired by a Delaware case in which the court held that the wording of the contract's no-liability clause — "the obligations of the parties shall terminate and there shall be no liability on the part of any party with respect thereto" — had the effect of waiving claims for breach of the contract; the state's supreme court affirmed in a one-word order. Yatra Online, Inc. v. EBIX, Inc., No. 2020-0444 (Del. Ch. Aug. 30, 2021) (cleaned up, emphasis added), aff'd w/o opinion, 276 A.3d 476 (Del. 2022).

Note

Subdivision 2 is inspired by a Michigan supreme court case in which the court's recitation of facts noted that "Miller-Davis gave Ahrens notice of default, terminated Ahrens's right to perform the contract, and demanded the bonding company perform under the bond." Miller-Davis Co. v. Ahrens Constr., Inc., 495 Mich. 161, 848 N.W.2d 95, 99 (2014) (emphasis added).

18.9.1.6. Termination alone wouldn't create liability.

Each party: You won't be liable to another party solely because of termination of the Con­tract in accordance with its termination provisions, unless the Con­tract clearly specifies otherwise — for example (hypothetically) if the Con­tract requires you to pay a specified amount to another party in case of termination before a stated time.

Note

A terminating party might still be liable: (1) under other provisions of the Con­tract; (2) for breaching one or more of its obligations under the Con­tract; and/or (3) for wrongfully terminating the Con­tract when the terminating party wasn't entitled to do so — see the discussion of "own goal" wrongful termination at 18.9.2.4.

18.9.1.7. Other grounds for termination can be cited later.
  1. This section will apply if:
    1. a party terminates the Con­tract, or a transaction or relationship under the Con­tract, for a stated reason (e.g., an alleged breach); but
    2. it turns out that the stated reason was not valid — for example, if a court finds that the terrminating party failed to prove an alleged breach and/or that the breach didn't give rise to a right to terminate.
  2. In that situation, the terminating party has the right to assert, as backup grounds, any other reason that, at the time of termination, would also have allowed the terminating party to terminate under the Con­tract or the law (e.g., if the terminating party could have terminated at will).
Note

This section provides a terminating party with a backup position in case its original reason for termination doesn't pan out. That could be handy to keep the original termination from being held to have been itself an "own goal" breach of contract. See Southland Metals, Inc. v. American Castings, LLC, 800 F.3d 452 (8th Cir. 2015) (affirming judgment on jury verdict that defendant had breached contract by terminating when it didn't have the right to do so).] (For more discussion of "own goal" wrongful terminations, see 18.9.2.4.)

18.9.1.8. Option: Termination Cross-Default Right

Each party: If this Option is agreed to, and you terminate one transaction, grant, or relationship for material breach by another party, THEN: You're free, in your sole discretion, to terminate some or all other uncompleted transactions, grants, or relationships between you and the breaching party.

Note

Background: This section sets up a type of "cross-default" right. Suppose that a supplier breaches its obligations under a purchase order, and the breach entitles the customer to terminate that purchase order. In such a situation, the customer might want to "pull the plug" entirely on its relationship with the supplier, terminating all pending purchase orders and not just the one where the supplier is currently in breach.

18.9.2. Additional notes

18.9.2.1. Termination could have undesired side effects.

A right to terminate the Con­tract could have unexpected (and undesired) results; for example:

In a California case, a former employee quit her job — which had the effect of revoking the arbitration agreement in her employment agreement. See Vazquez v. SaniSure, Inc., 101 Cal. App. 5th 139 (2024) (affirming denial of former employer's motion to compel arbitration; employee's quitting her job had the effect of revoking arbitration provision in employment agreement).

Example: In the 8th Circuit's 2021 Miller case, an employee terminated her employment agreement — which that agreement expressly allowed her to do. To the employer's surprise, though, the termination had the side effect of terminating the employee's obligation not to compete with her former employer, because the noncompetition covenant stated that it would survive termination of employment, not that it would survive termination of the employment agreement. Miller v. Honkamp Krueger Fin. Servs., Inc., 9 F.4th 1011 (8th Cir. 2021) (reversing and vacating preliminary injunction) (quotation edited for readability).

Example: In the Ninth Circuit's BladeRoom case, the "sunset" termination of a confidentiality agreement (a.k.a. nondisclosure agreement a.k.a. "NDA") resulted in a disclosing party's loss of its right to enforce agreed confidentiality obligations against a recipient of confidential information — and the overturning of a $30 million jury verdict in the disclosing party's favor. BladeRoom Grp. Ltd. v. Emerson Elec. Co., 11 F.4th 1010, amended, 20 F.4th 1231 (9th Cir. 2021); see also the extended discussion of this point at 5.3.5.

Tangentially: The wording of a merger agreement's termination clause wiped out a party's breach-of-contract claims; as the court explained:

In the Effect of Termination Provision, the parties agreed that, "[i]n the event of any termination of this Agreement, the obligations of the parties shall terminate and there shall be no liability on the part of any party with respect thereto," with limited exceptions not relevant here. Yatra Online, Inc. v. EBIX, Inc., No. 2020-0444 (Del. Ch. Aug. 30, 2021) (cleaned up, emphasis added).

18.9.2.2. Pro tip: Don't say "non-breaching party"

If a contract authorizes a party to terminate because of the other party's breach, the authorization should refer to that party as "the terminating party" or "the other party," not as "the non-breaching party." Example: In the Silicon Valley Powertech case (N.D. Cal. 2014), the contract in suit gave the "non-breaching party" the right to terminate; the court held that the party that had purported to terminate the contract didn't have the power to do so — because that party was itself in breach, of a different contract provision, and therefore had done an "own-goal breach" itself by purporting to terminate (for more such own-goal examples, see 18.9.2.4 below). See Powertech Tech., Inc. v. Tessera, Inc., No. C 11-6121 CW, slip op. at part I.A, II.A (N.D. Cal. Jan. 15, 2014) (on summary judgment).

18.9.2.3. Motive: Termination to dump a counterparty?

A party might look for a supposed material breach of contract as a reason — or a fabricated excuse — to terminate that contract and take up with another, more-lucrative party. That motivation might well have been at work in the 4th Circuit's Hess Energy case cited at 18.9.2.4 below, where "Lightning acknowledged that its purpose in signing [a contract with a new party] was to obtain a better price than it had obtained from Hess Energy." Hess Energy, 276 F.3d at 648 (4th Cir. 2002).

18.9.2.4. Caution: Don't do an own-goal termination for material breach

As mentioned at 18.9.2.2 above, improper termination of a contract for breach could itself be an "own goal" breach of contract.

(A widely-used dictionary, Merriam-Webster.com, defines "own goal" as: "1 chiefly British : a goal in soccer, hockey, etc., that a player accidentally scores against his or her own team [¶] 2 chiefly British something that one does thinking it will help him or her but that actually causes one harm[.]")

Imagine this:

  • You want to get out of a contract.
  • You conclude that the other side has materially breached the contract.
  • You send a notice of breach, but the other side fails to cure the breach (or perhaps you claim that the breach is incurable).
  • So, you send a notice of termination.

But then the other side files a counterclaim — and in litigation, counterclaims pretty much always happen.

In the end, a court holds that the other party's breach wasn't "material" after all — as a result, you didn't have the right to terminate, and so your termination was a repudiation of the contract, and thus a breach in itself.

Example: In Southland Metals (8th Cir. 2015), an iron foundry terminated a contract with a reseller — allegedly for material breach — but also because the foundry wanted to organize an internal sales force (in other words, to move its sales efforts in-house). The reseller sued for breach, both because it denied having itself breached and because the foundry supposedly didn't follow the contract's notice-and-cure termination procedure. A jury awarded the reseller for nearly $4 million in damages for improper termination; the Eighth Circuit affirmed judgment on the verdict. See Southland Metals, Inc. v. American Castings, LLC, 800 F.3d 452 (8th Cir. 2015).

Other cases have been to similar effect.32

18.9.2.5. Proof of damages from a material breach would still be required

A party might breach a contract but then be held not liable because the other party failed to prove its damages case, i.e., the dollar amount by which the other party was harmed by the breach.

Example: This happened in SwiftAir (Cal. App. 2022), where the court affirmed a take-nothing judgment in favor of Southwest Airlines, on grounds that jury found SwiftAir didn't meet its burden of proving that Southwest's breach of a particular contract (a beta-test agreement) had caused SwiftAir's alleged damages. See SwiftAir, LLC v. Southwest Airlines Co., 77 Cal. App. 5th 46, 291 Cal. Rptr. 3d 895 (2022) (affirming denial of judgment notwithstanding verdict and awarding Southwest its costs on appeal).

18.9.2.6. Possible post-termination actions

Post-termination actions could include, for example, the following:

  • final deliveries of goods; intangibles, e.g., reports; and work in progress, as in Protocol 25.5
  • issuance of final invoices
  • payment of outstanding amounts
  • return of confidential information, if applicable (see Protocol 5.4);
  • continuing confidentiality obligations (see Protocol 5.3);
  • preparation and signing of intellectual-property assignment documents (see Protocol 23.6);
  • a provider's obligation to help a customer transition to another provider (see Protocol 25.5).

Relatedly, drafters can also consider Termination Wrap Up Protocol (18.11), which allows parties a limited period of time after termination to complete certain pending business.

18.10. Termination Prohibition Protocol

18.10.1. The {Protocol

18.10.1.1. Termination is prohibited

If this Protocol is clearly agreed to, THEN: Neither party may terminate or rescind the Con­tract, no matter what the circumstances — if the other party breaches the Con­tract, the first party's EXCLUSIVE REMEDY will be an action at law for damages, and any purported termination will be of no effect.

Note

Terms such as this Protocol can often be seen in some long-term services agreements, such as so-called "software as a service" agreements and outsourcing agreements, in which a provider is to take over important functions of the customer's internal operations. When a customer enters into such a long-term agreement, it might well want to prohibit the supplier from terminating the contract (generally while preserving the customer's right to do so).

18.11. Termination Wrap Up Protocol

18.11.1. The XXX}

18.11.1.1. Parties: The Requester and the other party

This Protocol will apply in any situation in which:

  1. A "Relationship" — defined at § 18.11.1.2 — between one party (the Requesting Party) and another party, comes to an end, whether by expiration or termination; and
  2. The other party clearly agrees in writing — for example, by agreeing to this Protocol in the Con­tract — that the Requesting Party may have a transition period (over and above any notice period that preceded the Relationship's ending) in which to wrap up the other party's in-progress transactions in the Relationship.
Note

().  Every human relationship comes to an end eventually — bar none. So, prudence suggests planning for an orderly "shut-down" of the relationship.

(By analogy: "Graceful exit" is part of the ethos of computer programming: When an app or other software shuts down — or encounter a fatal bug — it should do so in an orderly manner, without inadvertently crashing — or locking up — the phone, tablet, or computer.)

To that end, this Protocol provides contracting parties with a way for, say, a reseller of a manufacturer's "widgets" to wind up its then-pending sales deals with prospective end-customers if the reseller's contract with the manufacturer comes to an end.

The terms of this Protocol are based on various agreements that the author has negotiated over the years.

18.11.1.2. Definition: What counts as a Relationship?

For purposes of this Protocol, the term "Relationship" refers to one or more of the following:

  1. a relationship (lower-case r), such as for example a reseller- or referral relationship, that is clearly indicated in the Con­tract as being subject to this Protocol; and/or
  2. an authorization, for example, a grant of one or more rights such as a license, likewise clearly indicated; and/or
  3. the Con­tract itself, if the Con­tract does not expressly specify such a relationship or authorization.
18.11.1.3. The Wrap-Up Period is ten business days.

If not otherwise agreed in writing, the Requester's Wrap-Up Period:

  1. begins on the date that the Relationship formally comes to an end; and
  2. ends at 12 midnight, local time, the end of the day on the date the stated time thereafter.
18.11.1.4. What kind of wrap-up activities are allowed?

During the Wrap-Up Period, except as otherwise stated in this Protocol, the Requester is free to attempt to complete any then-pending transactions that:

  1. the Requester was allowed to do under the Con­tract before the end of the Relationship; but
  2. after that time, are prohibited to the Requester, by the Con­tract and/or by law.
18.11.1.5. The same terms and conditions govern Wrap-Up Activities.

The Requester's wrap-up activities under this Protocol would be governed by the same terms of the Con­tract as would have applied before the end of the Relationship.

18.11.1.6. No Wrap-Up Period if the Requester is in material breach.

The Requester doesn't have a Wrap-Up Period, and doesn't engage in wrap-up activities, if the Requester is in material breach of the Con­tract when the Relationship ends.

18.11.1.7. The other party can track wrap-up transactions.

If so requested by the other party, THEN: Not later than two business days after the date that the Relationship ends, the Requester furnishes the other party with a complete written list of pending transactions that the Requester hopes to complete during the Wrap-Up Period, to help the other party confirm that the Requester isn't using the Wrap-Up Period to develop new business.

18.11.1.8. The other party can ask for evidence of wrap-up eligibility.

If the other party asks concerning a particular wrap-up transaction, THEN: The Requester furnishes the other party with evidence, reasonably satisfactory to the other party, that the Requester had in fact been actively engaged in negotiating that transaction before the end of the Relationship.

19. Software-related provisions

Contents:

20. Defined terms: General-purpose

20.1. Affiliate Definition

20.1.1. Parties: A; B

  1. Two "persons" (see Protocol 20.29) A and B are affiliates to the extent (and only to that extent) stated in this Protocol or as otherwise clearly stated in the Con­tract.
  2. For this purposed, a "person" could be either an individual or an organization.
Note

For the most part, this Protocol simply summarizes how the law works in the United States. This is seen, for example, in SEC Rule 405, whose text is similar to what's seen in other sources.

20.1.2. Affiliate status through "control" relationship

For purposes of the Con­tract, two persons A and B are affiliates:

  1. if A controls B (as defined below), directly or indirectly;
  2. if A and B are under common control, that is, they're each under the direct- or indirect control of a third person; or
  3. if the Con­tract clearly says they are, even if they are not otherwise affiliates under subdivisions 1 and 2 above.
Note

Here are some real-world example of affiliates under the control and common control branches in the above text:

Both Google and YouTube are subsidiaries of "parent company" Alphabet Inc. — so:

  • Alphabet and Google are affiliates of each other under subdivision 1 because Alphabet controls Google; ditto for Alphabet and YouTube;
  • Google and YouTube are affiliates of each other under subdivision 2 because they're both under the common control of Alphabet.
  • Fitbit is a subsidiary of Google, so Fitbit is an indirect subsidiary of Alphabet as well as a direct subsidiary of Google.
  • Fitbit is likewise an affiliate of YouTube because of their common control by Alphabet.

20.1.3. Control from selection power for more than 50% of board

If B is an organization, then A would control B under this Protocol if A had the legally-enforceable power to elect or appoint the stated proportion of the members of B's principal governing body ("board") who have the right to vote to approve or disapprove a proposed board action.

Note

().  As is pretty typical, the 50% number in this Protocol uses the basic majority-rule notion to define control by voting power. But: Contract drafters should think about why they're defining the term affiliate — different reasons might warrant changing the 50% number.

Voting power definition: 20.39.

20.1.4. Class-based voting?

For purposes of determining affiliate status: If an organization B's voting shares are divided into classes, THEN: For A to control B, A would need the requisite voting-power percentage in each of those classes.

Note

Class-based voting is "a thing," especially in some parts of the tech world: In a few cases, tech-company founders have reserved "supershare" classes for themselves and thus continue to control the company even after it has gone public (see, e.g., the Investopedia discussion).

20.1.5. Types of "management power"

For purposes of determining affiliate status, A would control an organization B if A had the legally-enforceable power — for example, by an enforceable contract — to direct B's affairs.

Note

().  Caution: Some contracts' definitions of affiliate refer to de facto "control relationships" — without defining what would qualify. That's generally not a good idea, even though that concept can be found in U.S. securities regulations such as , SEC Rule 405 (whose text is similar to what's seen in other sources).

Pro tip: In the UBS Securities case discussed below, lack of a clear contractual definition of control led to a $17 million legal-malpractice verdict against a blue-chip NYC law firm for failing to nail down the definition to its client's hindsight liking.

In a regulatory context, just plain "management power," without the "legally-enforceable" part, might be acceptable, despite its vagueness. But in a commercial context, the vagueness of the generic term could lead to expensive, time-consuming litigation.

Example: In Offshore Drilling (5th Cir. 2010), the parties were forced to litigate which party had "control" of a vessel that was destroyed by fire — and thus which party or parties should be liable for damages. The outcome isn't important for our purposes here, just that the dispute was certainly costly to the parties. See Offshore Drilling Co. v. Gulf Copper & Mfg. Corp., 604 F.3d 221 (5th Cir. 2010).

Example: In UBS Securities (N.Y. App. 2010), the uncertain meaning of "control," as used in a contract, meant that the parties had to litigate whether investment bank UBS was entitled to a $10 million fee from a company, Red Zone, headed by Daniel Snyder, the owner of what was then called the Washington Redskins NFL team. See UBS Securities LLC v. Red Zone LLC, 77 A.D.3d 575, 578, 910 N.Y.S.2d 55 (N.Y. App. Div. 1st Dept. 2010).

A knock-on effect of the UBS lawsuit was that Red Zone scored a $17 million legal-malpractice verdict against its blue-chip NYC law firm for failing to nail down the definition of control to Red Zone's hindsight liking. See Red Zone LLC v. Cadwalader, Wickersham & Taft LLP, 45 Misc.3d 672, 994 N.Y.S.2d 764 (N.Y. Sup. Ct. 2013), aff'd, 2014 NY Slip Op 4570, 118 A.D.3d 581 988 N.Y.S.2d 588 (N.Y. App. Div. 1st Dept. 2014).

20.1.6. Possible gain or loss of affiliate status

A non-affiliate of a person could become an affiliate by qualifying as such. Conversely, an existing affiliate of a person could lose that status if circumstances were to change.

Note

Drafters might want to consider about what should happen in case of a change of affiliate status, e.g., because an existing affiliate gets sold to another company. Example: Suppose that:

  • A and B enter into a contract under which B is obligated to do certain things for A's affiliates (e.g., grant special pricing, or allow access to B's trade secrets).
  • And now suppose that A acquires a new affiliate — namely one of B's competitors, which acquired ownership of A in a merger transaction.

Clearly B might be unhappy about having to share its trade secrets with its competitor, so B's drafter(s) should keep that possibility in mind.

Example: Ellington v. EMI Music involved the estate of the legendary musician Duke Ellington. New York's highest court held that: "Absent explicit language demonstrating the parties' intent to bind future affiliates of the contracting parties, the term 'affiliate' includes only those affiliates in existence at the time that the contract was executed." Ellington v. EMI Music Inc., 24 N.Y.3d 239, 246 (2014) (affirming dismissal of complaint).

Counterexample: In GTE Wireless (1st Cir. 2003), the First Circuit held that a company, Cellexis, had breached a settlement agreement not to sue GTE (now part of Verizon) or its affiliates when it sued a company that, at the time of the settlement agreement, had not been a GTE affiliate, but that later became an affiliate. The court reasoned that when read as a whole, the contract language clearly contemplated that future affiliates would also be shielded by the covenant not to sue. See GTE Wireless, Inc. v. Cellexis Intern., Inc., 341 F.3d 1, 5 (1st Cir. 2003). Likewise: Mey v. DIRECTV, LLC, 971 F.3d 284, 286 (4th Cir. 2020) (reversing denial of motion to compel arbitration; DirecTV became an "affiliate" of AT&T Mobility and thus was a beneficiary of a consumer arbitration clause). Contra: Revitch v. DIRECTV, LLC, 977 F.3d 713, 717 (9th Cir. 2020) (affirming denial of motion to compel arbitration).

20.1.7. Additional notes

20.1.7.1. The business context: Why it might matter

Sometimes contracting parties will care about what constitutes an "affiliate" of a party, because —

  • The contract might give certain rights to "affiliates" of one or another party. This could be, for example, the right to acquire goods or services on the same terms as in the contract. [DCT TO DO: Find examples in master service agreements / master purchase agreements]
  • The contract might also impose obligations on a party, where those obligations are tied in somehow with affiliates of one or another party (e.g., an obligation to be financially responsible for actions of an affilate).

In either situation, it might be important to know just who qualifies as an affiliate of the relevant party at the relevant time or times.

Alphabet affiliates

Here are some real-world example of affiliates under the control and common control branches in the above text:

Both Google and YouTube are subsidiaries of "parent company" Alphabet Inc. — so:

  • Alphabet and Google are affiliates of each other under subdivision 1 because Alphabet controls Google; ditto for Alphabet and YouTube;
  • Google and YouTube are affiliates of each other under subdivision 2 because they're both under the common control of Alphabet.
  • Fitbit is a subsidiary of Google, so Fitbit is an indirect subsidiary of Alphabet as well as a direct subsidiary of Google.
  • Fitbit is likewise an affiliate of YouTube because of their common control by Alphabet.
20.1.7.2. Caution: Which is the correct contracting party?

In corporate "families," different affiliates can share variations on the same name. Example: The global technology company Apple has subsidiaries including Apple Sales International Ltd. and Apple Operations International Ltd., both of which were directly involved in a decision by the European Court of Justice that Apple owed Ireland some €13 billion (USD $14.4 billion).

Not naming the correct company as a party to the contract could end up being financially disastrous for one or more other parties. Example: In a Seventh Circuit case:

  • The plaintiff, which we'll call "Target," was having business difficulties and badly wanted to be acquired by the defendant, "Buyer."
  • When Target entered into the acquisition agreement, the other named party was not Buyer, but Buyer Sub, a newly-created subsidiary of Buyer, which was to acquire Target's assets and pay Target the purchase price in the form of an earnout.
  • Evidently, Target couldn't get Buyer to guarantee Buyer Sub's payment obligations (see Protocol 4.8) — and sure enough, later a dispute arose over payments that Buyer Sub had withheld.
  • Target went to court for the withheld payments; it sued not just Buyer Sub — which had no assets and so was judgment-proof — but also Buyer, i.e., the parent company of Buyer Sub.

Buyer successfully sought summary judgment dismissing it from the case; in affirming, the Seventh Circuit court didn't even reach the merits: "It goes without saying that a contract cannot bind a nonparty. If [Target] is entitled to damages for breach of contract, it cannot recover them in a suit against [Buyer] because [Buyer] was not a party to the contract." Quoting one of its prior cases, the appellate court also implicitly noted that Buyer had not guaranteed Buyer Sub's payment obligations; the trial court had previously noted that "[Target] has offered no evidence that [Buyer] agreed to be liable for [Buyer Sub's] debts, obligations, and liabilities …." Northbound Group, Inc. v. Norvax, Inc., 795 F.3d 647, 650, 653 (7th Cir. 2015) (cleaned up, emphasis added), affirming 5 F. Supp. 3d 956, 972-74 (N.D. Ill. 2013).

(This situation — a party enters into a relationship, but it turns out not to be with the intended other party — recalls the famous tale of Jacob, Leah, and Rachel in Genesis chapter 29.)

Example: In a Delaware chancery-court case, employees of an LLC were granted equity interests in the LLC's parent company. The employees' equity agreement included a covenant not to compete with the parent company, but said nothing about not competing with the LLC itself, i.e., the actual employer. The Delaware chancery court held that the covenant didn't prevent the employees from leaving and going to work for a competitor of the employer. See Frontline Technologies v. Murphy, No. 2023-0546 (Del. Ch. Aug. 23, 2023).

20.1.7.3. Caution: Don't list a party to the Con­tract as "ABC Corp. and affiliates"

It's usually a bad idea for a contract's preamble to state that the contract is between (for example) "ABC Corporation ('Customer') and its affiliates and XYZ Inc. ('Supplier').

Why might that even come up? Well, suppose that ABC is negotiating a master purchase agreement with XYZ. Not unusually, ABC wants its various affiliates to be able to place orders with XYZ on the same master agreement, so that the affiliates won't have to incur the cost and delay of renegotiating terms and conditions with XYZ.

It'd be easy — and ABC might ask — to recite, in the master purchase agreement, that the parties are as quoted above. But that's not a great idea, unless each ABC affiliate actually signs the agreement as a party, committing, on its own, to upholding the obligations in the master purchase agreement. Experienced commentators seem to agree. See, e.g., Mark Anderson, Don't Make Affiliates parties to the agreement (2014); Ken Adams, Having a Parent Company Enter Into a Contract "On Behalf" of an Affiliate (2008).

Thus, a safer practice would be to state the specific rights and obligations that affiliates have under the contract, instead of making them parties.

Example: In a Massachusetts case, a contract listed one of the parties as Uber Brasil "and its Affiliates"; a trial court held that this was a factor in determining that the parent company, Uber Technologies [U.S.], was an intended third-party beneficiary of the contract's forum-selection agreement. See Zemcar Inc. v. Uber Techs., Inc., No. 2484CV01525-BLS2, slip op. at 15 (Mass. Super. Jan. 29, 2025) (denying, in relevant part, motion to dismiss trade-secret claim because of forum selection clause; footnote omitted, emphasis and extra paragraphing added).

Example: Consider the Fifth Circuit's NOV decision, in the appeals court reversed and remanded a summary judgment that had held that a which the issue whether a contracting party had authority to bind one of its affiliates. See National Oilwell Varco, L.P., v. Auto-Dril, Inc., 68 F.4th 206, 218 & nn.2-3 (5th Cir. 2023) (reversing and remanding summary judgment in relevant part); id. at 222 (Richman, C.J., dissenting in relevant part). At this writing (May 2025), I couldn't find a Web site for Auto-Dril.

Example: In an English High Court (trial court) case, the contract between a tech company and an investment-banking firm included what the court referred to as "an oddity" in its drafting: "[T]he opening words of the Agreement contemplate [the investment bank] acting for [the tech company] and 'its affiliates', … who are all collectively defined as the 'Company.'" That was one of a many complications in the court's task of determining whether the (ambiguous) contract required the tech company to pay the investment bank a success fee when the tech company raised capital from its parent company, not from any third party referred by the investment bank. (The court ultimately concluded that the answer was "no.") Kigen (UK) Ltd. v NOR Capital Ltd., [2024] EWHC 3164 (Ch), ¶¶ 28, 90-91.

20.1.7.4. Caution: Will the contracting party pay what it owes?

When a contract addresses affiliates' rights, it might include language such as the following, adapted from the real-life Master Supply & Purchasing Agreement of one subsidiary of the alarm company ADT Corporation:

Each Affiliate shall only be liable for those obligations expressly set forth in the Purchase Order to which it is a party. In no event will Buyer be liable for any of the obligations or liabilities of any Affiliate pursuant to this Agreement.

In such a situation, the supplier might want to consider doing one or both of the following:

  • Put in the draft contract a provision that the supplier may reject an affiliate's order — ideally for any reason or no reason, but at a minimum if the supplier has reasonable concerns about the affiliate's ability to pay; and/or
  • Get the (solvent) parent company, or some other specific, creditworthy affiliate of the named customer, to guarantee payment of all orders when a customer affiliate is the buyer (see § 13.9.10).

This could turn out to be important. Example: In a California case:

  • A dispute arose between Huy Fong, a famed manufacturer of sriracha hot sauce, and Underwood Ranches, a pepper grower, because Huy Fong wanted Underwood to deal with a newly-created Huy Fong subsidiary, Chilico.
  • Chilico, though, "did not have the assets to ensure that Underwood would be paid and Huy Fong refused to guarantee the Chilico contract."
  • The dispute turned bitter, with the parties suing each other.

In the end, it worked out sort-of OK for Underwood: After years of costly litigation, a California jury awarded Underwood $13 million in compensatory damages and $10 million for fraud.

But the case illustrates why parties and their contract drafters should consider the risk of doing business with the "wrong" company in a corporate "family." See Huy Fong Foods, Inc. v. Underwood Ranches, LP, 66 Cal. App. 5th 1112, 1119, 281 Cal. Rptr. 3d 757 (2021).

Relatedly, see also the discussion of the Northbound lawsuit at 20.1.7.2.

20.1.7.5. Could the Con­tract bind a non-signatory affiliate?

An affiliate of a contracting party might be bound by the contract if:

  1. the contracting party — or the person signing on behalf of that party — controlled the affiliate, and
  2. the contract stated that the contract will benefit the affiliate.

Example: Delaware's chancery court reached the conclusion summarized above in a case where:

  • the contract in suit stated that it was creating a strategic alliance for the contracting party and its affiliates, and
  • the contract had been signed by the president of the contracting party, who was also the sole managing member of the affiliate.

The court held that the affiliate was bound by — and had violated — certain restrictions in the contract. Medicalgorithmics S.A. v. AMI Monitoring, Inc., No. 10948-CB, slip op. at 3, 52-53, 2016 WL 4401038 (Del. Ch. Aug. 18, 2016).

20.2. After (or from) Definition

Definition

Defining by example: Each party treats a time period of, say, one year after (or from) June 30, 20x4 as ending at exactly 12:00:00 midnight, in the relevant time zone, at the beginning of June 30, 20x5.

Note

().  The precise end time of an "after" or "from" period could have significant consequences. Example: In Apache Corp. (Tex. 2023), involving an oil-drilling lease, the Texas supreme court held that a relevant time period had expired on January 1, not December 31 — for a difference in damages of some $180 million; the court's opinion recapped prior efforts to define "after," going back to Texas's pre-statehood days. See Apache Corp. v. Apollo Exploration, LLC, 670 S.W.3d 319, 321 (Tex. 2023) (reversing and remanding court of appeals).

Concerning defining by example, see 20.21.4.2.

20.3. All Definition

Definition

The term "all" means just that.

Note

().  The Sixth Circuit pointed out that a requirement to list examples "would generate litigation rather than prevent it …." Ward v. Shelby County [Tenn.], 98 F.4th 688, 691 (6th Cir. 2024) (reversing district court; release of "any and all claims" barred claim).

But lawyers have been known to make the contrary argument; in Wohlt (Ind. 2023), Indiana's supreme court remarked that the only posslble exception would be if a party pleaded and proved mutual mistake or fraud. See Wohlt v. Wohlt, 245 N.E.3d 611 (Ind. 2024), affirming 222 N.E.3d 964 (Ind. App. 2023) ("all" meant "all").

20.4. And/Or Definition

Definition

  1. The term "and/or" means the inclusive or, that is, "one or more of the things listed here."
  2. As a hypothetical example: The phrase, "The parties expect to meet on Tuesday, Wednesday, and/or Thursday" means that the parties expect to meet on one or more of the listed days, not just on one and only one of them.
  3. For emphasis: This Definition does not mean that the term or, by itself, is necessarily the exclusive or — that would be determined in accordance with applicable principles of interpretation.
Note

().  A problem with using the term "or" alone is that, in some circumstances, a court might read "or" as being tantamount to "and." Example: As the court noted in Capital Finance (D. Md. 2019):

Maryland law recognizes that the word "and" may unambiguously require a disjunctive reading in light of the character of the contract in which it appears. … Conversely, the word "or" may require a conjunctive reading. Capital Finance, LLC v. Rosenberg, 364 F. Supp. 3d 529, 545-46 (D. Md. 2019) (citing cases; emphasis added), aff'd in relevant part, No. 19-1202, slip op. (4th Cir. 2020) (unpublished).

Example: The Delaware chancery court held that in context, the term "and" in a contract provision must be read as "or"; affirming, the state supreme court provided an extensive review of precedent concerning and and or. See Weinberg v. Waystar, No. 2021-1023-SG (Del. Ch. Jul. 6, 2022) (granting summary judgment), aff'd , 94 A.3d 1039 (Del. 2023).

Example: In Pulsifer (U.S. 2024), the U.S. Supreme Court had to decide whether a particular federal criminal statute used the word "and" in the conjunctive or disjunctive sense. See Pulsifer v. United States , 601 U.S. 124 (2024).

So: It can be useful to say and/or to be clear what's meant.

Amusingly, the term and/or has provoked scorn from some purists, as well-documented by Professor Robbins. See Ira P. Robbins, “And/Or” and the Proper Use of Legal Language, 77 Md. L. Rev. 311 (2018).

Granted, it's possible to use and/or inappropriately, as with any term. See,, e.g., Wayne Schiess, In the land of the Andorians (UTexas.edu 2013).

But as Professor Robbins correctly notes:

And/or, however, is not ambiguous at all. It has a definite, agreed-upon meaning: when used properly, the construct signifies “A or B or both.”

In most areas of law, there is simply no compelling reason to avoid using and/or. The term is clear and concise. It derives criticism mainly from instances in which people use it incorrectly. Robbins, cited above, at 311, emphasis and extra paragraphing added.

Moreover, trying to ban and/or entirely is almost surely a bootless errand: In real life, drafters will continue to use and/or because of its utility or through force of habit.

So the better practice might well be: Just define the term — as here — and stop worrying about it. (W.I.D.D. — When In Doubt, Define!)

Ken Adams, author of A Manual of Style for Contract Drafting, usefully suggests that, when dealing with a list of three or more items, it's better to write, "one or more of A, B, and C."

Another alternative: In the final paragraph of Carley Foundry (Minn. App. 2010, unpublished), a state-court judge — no slave to brevity, it seems — excoriated the use of and/or as "an indolent [!] way to express a series of items that might exist in the conjunctive, but might also exist in the disjunctive"; the judge proclaimed that a drafter could instead "express a series of items as, A, B, C, and D together, or any combination together, or any one of them alone." Um … sure, Your Honor … Carley Foundry, Inc. v. CBIZ BVKT, LLC, No. A09-1018, slip op. (Minn. App. 2010) (unpublished),

20.5. As-Is Protocol

Some contracts (probably many of them) state that goods and/or services are being provided "AS IS," or perhaps "AS IS, WHERE IS, WITH ALL FAULTS" This Protocol sets out a definition of what that should mean.

20.5.1. Basic definition

  1. Scenario:
    1. one party (the "Vendor") provides another (the "Customer") with something, referred to here as a "Widget"; and
    2. the Con­tract states that the Widget is provided "as-is."
  2. In that scenario: The Vendor's "as-is" statement automatically disclaims all implied warranties, representations, conditions, and terms of quality (each, generically, an implied "Warranty") about the Widget.
  3. For this purpose, it does not matter:
    1. whether the term "as-is" includes a hyphen or is capitalized — although in some circumstances the law might require the term to be "conspicuous";
    2. whether the purported Warranty is implied in fact or implied by law; nor
    3. whether the Widget is classified as goods; services; equipment; license rights; or anything else.
Note

().  Subdivision 2's disclaimer of implied conditions and terms of quality is a nod to the law of England, Wales, and Northern Ireland. Example: In a High-Court case, an oil seller learned — presumably to its dismay — that its contractual disclaimer of (only) implied warranties wasn't enough to shield the seller from liability under implied conditions; the court said, "If the failure to use the word "condition" renders [the contract's disclaimer] of little or no effect, so be it. The sellers agreed to the wording of [the disclaimer] … and must live with the consequences." See KG Bominflot Bunkergesellschaft Für Mineralöle mbh & Co KG v. Petroplus Marketing AG, [2009] EWHC 1088, ¶ 49 (Comm). (Pro tip: Don't call it "UK law"; see 21.12.9.13.)

Subdivision 3.a: For more about conspicuousness, see 8.1.

20.5.2. No effect on express written warranties

Continuing with the above scenario: The Vendor's "as-is" disclaimer does not negate any any express, written Warranty stated in the Con­tract.

Note

Of course, an express Warranty wouldn't be an implied Warranty — sometimes, though, contract reviewers overlook this fact.

20.5.3. No effect on implied warranty of title to goods

  1. Continuing with the above scenario: If the Widget is classified as "goods," THEN: Notwithstanding the Vendor's as-is disclaimer, the Vendor is still implicitly warranting to Customer that the Vendor either:
    1. owns the goods; or
    2. is otherwise legally entitled to engage in the sale, lease, or other transaction with the Customer concerning the Widget.
  2. On the other hand: The Vendor is not warranting that the Widget does not infringe any third-party intellectual-property rights — on that general subject, see § 20.5.4 below.
Note

().  Background: Even when a buyer is acquiring goods "as is," the buyer still should be entitled to presume that it's not buying stolen goods.

Subdivision 1 is modeled on the implied warranty of title for goods in UCC § 2-312.

Subdivision 2 is intended as a guardrail against "creative" arguments that an implied warranty of title is supposedly a warranty of noninfringement; for language on that subject, see Protocol 23.5 and its commentary.

20.5.4. Some effect: Third-party IP rights

Continuing with the above example: If the Vendor provides goods (defined very broadly) or services to another party on an "as is" basis, the Vendor is nevertheless implicitly representing (see Protocol 20.34) to the Customer that:

  1. the Vendor is not aware of any suggestion that the goods or services — as delivered to (or at the direction of) the Customer — might infringe on any patent, copyright, or other intellectual-property right (each, an "IP right") of a third party — but the Vendor is not representing that the Vendor has done any particular research or investigation on that subject; and
  2. so far as the Vendor is aware, no third party has asserted to the Vendor that the goods or services infringe an IP right of the third party.
Note

This seems like a reasonable good-neighbor approach.

20.6. Board Definition Definition (board of directors)

Definition

The terms "board of directors" and "board" refer generically to the principal governing body of an organization, such as (without limitation) the board of directors of an American corporation.

Note

This definition is provided for drafter convenience, because in the United States and some other jurisdictions, a corporation is governed by what's known as a board of directors, with the corporate officers and managers acting under the direction of that board — but other forms of organization might have other types of governing body, such as a board of trustees, of managers, etc.

20.7. Business Day Definition

Definition

The term business day (whether or not capitalized) refers to Monday through Friday except days that banks in New York City are generally closed.

Note

Depending on the city and country chosen for bank closings, the definition in the text could eliminate a lot of what Americans might think of as "work days," as discussed in Sariego (2020).

20.8. Calendar Year Definition

20.8.1. Definition

  1. The calendar year 2030 (whether or not the words are capitalized):
    1. begins at exactly 12:00 midnight — that is, 12:00:00.0000 at the beginning of January 1 of that year; and
    2. ends at exactly 12:00 midnight at the end of December 31 of that year (i.e., just after 11:59:59.9999 on that date).
  2. If multiple time zones are potentially relevant, THEN: In the interest of avoiding ambiguity, the 12:00 midnight is in the time zone of the latest occurrence of the stated time on the date in question.

    Hypothetical example: If both California time and Tokyo time are relevant, then a mention of 12:00 midnight at the end of the day on December 31 would refer to that time in California. (In Tokyo, it would already be 4:59 p.m. on January 1.)

  3. Calendar-year periods:
    1. A period of one calendar year beginning on (for example) July 1 ends at exactly 12:00 midnight at the beginning of July 1 in the following year.
    2. A period of one calendar year following (for example) June 30 ends at exactly 12 midnight at the end of June 30 in the following year.
    3. Leap years: If a calendar-year period begins on February 29 (that is, on a leap day), then that period ends at exactly 12 midnight at the beginning of March 1 of the following year.
  4. Unless clearly agreed otherwise, the Western (Gregorian) calendar is to be used for all calendar-year determinations.
Note

().  Subdivision 1.a: The precision of this use of "12:00.00 midnight" is to forestall disputes about whether, say, 20 seconds after 12 midnight would still count as 12 midnight; this happened — with opposite results — in a pair of Canadian cases discussed at 20.20.

Subdivision 2: For reader convenience, this section intentionally duplicates the time-zone provision of Protocol 20.37 (time of day), even though that goes against the Don't Repeat Yourself guideline discussed at 30.4.

Subdivision 3.c: People with February 29 birthdays can no doubt relate.

Subdivision 4: Some Islamic countries or other places might do business on a (non-Gregorian) lunar calendar; see generally Adams (2013) and the reader comments there.

20.9. Change of Control definition [TO DO]

20.9.1. Rough notes

It's fairly common for the term "change of control" to refer solely to a change of ownership of the power to vote more than 50% of the voting power entitled to vote for members of a party's board of directors (or equivalent body in a non-corporate organization).

From the lawyer site redline.net (requires an account), an (anonymous) poster provided a somewhat-onerous change of control clause, which the poster described as, "taken from a well-known and large Silicon Valley law firm, from their flagship Technology License Agreement template–so [it] must be good, right?" Here it is:

"Change of Control" of Licensee means a transaction or series of related transactions resulting in:

(a) the acquisition of ownership, directly or indirectly, beneficially or of record, by any individual, entity or group, of equity interests representing more than 50% of the aggregate ordinary voting power or beneficial interest represented by the issued and outstanding equity interests in Licensee;

(b) the consummation by Licensee or any direct or indirect parent of Licensee of a merger or consolidation with any other entity or any other such group; or

(c) the transfer, sale, assignment, exclusive license, or other disposition of all or substantially all of Licensee’s or any direct or indirect parent of Licensee’s tangible or intangible assets, personnel, technology, equipment, business, equity interest, or voting interest relating to this Agreement.

Licensee shall notify Licensor in writing of a Change of Control within thirty days of its occurrence.

This Agreement will terminate at any time immediately upon written notice by Licensee following a Change of Control. [Huh? What does this mean?]

(Formatting lightly edited.)

20.10. Claim Definition

The term "claim," whether or not capitalized, refers to any request or demand —

  • whether in written- and/or oral form;
  • in any form;
  • in any forum;
  • by one or more individuals and/or organizations, including for example government authorities;
  • for damages; an injunction; and/or any other form of legal- or equitable relief;
  • including but not limited to counterclaims and cross-claims.
Note

().  It might not be necessary to define the term claim, because most lawyers would probably agree on its meaning. But when there's money at stake or advantage to be gained, lawyers can be really good at arguing that the term claim shouldn't encompass counterclaims, cross-claims, third-party claims, and the like.

This definition draws on ideas set out in Youngblood & Flocos (2010).

When appropriate, drafters should consider specifying written claims, to avoid putting a hair trigger on provisions that depend on claims being made, e.g., defense requirements.

A claim could be set forth, for example, in a written communication such as, for example, a letter, an email, a text, etc.; and/or in a filing with, or a submission to, a tribunal of competent jurisdiction.

Concerning counterclaims, see generally 21.23.

20.11. Clear and Convincing Evidence Definition

  1. When this Protocol is agreed to, the parties will follow it whenever the Con­tract or the law requires an assertion to be supported by "clear and convincing evidence."
  2. The asserting party will offer evidence that's sufficient to produce, in the mind of the fact-finder, a firm conviction that the assertion is highly likely to be true — otherwise, the assertion will be conclusively deemed not to have been proved.
Note

().  Some contracts require certain facts to be proved by clear and convincing evidence; that's the standard used in civil litigation for claims of, e.g., fraud. It's useful to define the term in a contract in case the relevant jurisdiction doesn't follow U.S. law on that point. See, e.g., Scott & Triantis (2006) at 867 & n.166; Huy Fong Foods, Inc. v. Underwood Ranches, LP, 66 Cal. App. 5th 1112, 1126, 281 Cal. Rptr. 3d 757 (2021).

(By comparison: In the United States, criminal charges generally must be proved by evidence "beyond a reasonable doubt" — that is, before the government may imprison someone, the government's prosecutors must put on evidence that, in the view of both a neutral judge and a neutral jury, rises to that level of proof.)

Subdivision 2 is a paraphrase, in somewhat-plainer language, of the standard set out by the U.S. Supreme Court. See Colorado v. New Mexico (1984), quoted in 9th Cir. Mod. Jury Instr. 1.7.

20.12. Clearly Agreed Definition

  1. For a thing to be "clearly agreed" or "clearly agreed to" by a party (which is said to "clearly agree"), the party's agreement to the thing must be:
    1. stated in the Con­tract itself;
    2. stated in a writing signed by the party; and/or
    3. otherwise shown by clear and convincing evidence — which must include, without limitation, reasonable corroboration of statements by interested persons.
  2. Any claim that this Protocol was waived (so that a different standard is to govern) must be supported by heightened proof as stated in Delaware law.
Note

Drafters could (judiciously) use this definition to give parties somewhat-more flexibility than purporting to impose strict writing requirements — which a court might disregard anyway, as discussed at 10.5.4.1.

20.13. Consider Definition

This definition supports various provisions that call for a party to "consider" doing something or another — notably, checking with The Other Side about a matter (see Pick up the phone!).

  1. If this Protocol is agreed to, it will govern any case where the Con­tract calls for a party A to "consider" doing something ("Thing X").
  2. It is up to A to decide — in A's sole discretion — whether, when, where, and how to do Thing X.
  3. A need not meet any particular standard when considering whether to do Thing X — for example, A's "process" need not rise to any particular level of investigation or diligence.
  4. A's consideration of Thing X will be solely for A's benefit, not for the benefit of any other party.
Note

Subdivision 2 — sole discretion: See Protocol 9.6.

20.14. Contract-Related Claim Definition

The term "Contract-Related Claim" refers broadly to any claim, obligation, liability, or cause of action — each, a "Claim" — arising out of or relating to one or more of the following:

  1. the Con­tract;
  2. the negotiation, execution, performance, or breach of the Con­tract;
  3. any representation or warranty made in, in connection with, or as an inducement to, the Con­tract; and/or
  4. any transaction or relationship resulting from the Con­tract.
Note

().  This Definition is provided purely for convenience; it's used, for example, in Protocol 17.6 (non-recourse against party employees).

In the first part of this definition, the word any is underlined to stress that it encompasses all claims, etc. whether, for example —

  1. arising in contract or in tort;
  2. arising in law or in equity; and/or
  3. created or granted by a constitution, statute, regulation, order precedent, or other governmentally-enforceable policy.

20.15. Days Definition

  1. Calendar days: The term day refers to a calendar day, as opposed to a business day (§ 20.7) unless otherwise clear from the context.
  2. Periods: Defining by example: A period of five days, beginning on January 1, ends at exactly 12 midnight, in the relevant time zone, at the end of the day on January 5.
Note

().  Subdivision 2: Note the use of an illustrative example, as discussed at 20.21.

Concerning time zones, see Protocol 20.37.

Pro tip: When drafting, consider saying, e.g., "three months" (defined at Protocol 20.27) instead of "90 days" to make it easier for readers to quickly figure out when the period ends. (Consider that a period of 30 business days would be around six weeks, not one month.)

Caution: See 20.2 concerning the dangers of time periods "after" or "from" a stated date.

20.16. Deadline Definition

If the Con­tract states a deadline date, but not the time, marking the end of a specified period, THEN the period ends at exactly 12 midnight at the end of the stated deadline date.

Note

This definition simply provides a benchmark reference point; drafters can vary it as desired.

20.17. Deliverable Definition

  1. The term "deliverable" refers to any of the following that is to be delivered to a party (the "Customer") under the Con­tract:
    1. any tangible goods, and
    2. any intangible information, no matter how transmitted or stored.
  2. For purposes of this Protocol, a deliverable could take the form of the Customer's own goods or information that another party has transformed and/or otherwise processed under the Con­tract.
Note

This is a convenience definition, offered because the meaning of deliverable is sometimes subject to dispute. Example: That meaning was one of many issues litigated in an Eighth Circuit case in which the court affirmed judgment on a jury verdict that Walmart had stolen trade secrets of a software developer. See Walmart, Inc., v. Cuker Interactive, LLC, 949 F.3d 1101, 1110 (8th Cir. 2020).

20.18. Effective Date Protocol

In many cases, a contract will state that certain rights and obligations are tied to the "effective date" of the contract. Example: A confidentiality agreement might state that the agreement protects only confidential information that's disclosed to the recipient during a stated number of months after the agreement's effective date.

In addition, it's not uncommon for contracting parties to want to "backdate" their agreement — a typical example is backdating a confidentiality agreement, as discussed at 20.18.2.2.

(Caution: Don't backdate a contract for deceptive purposes — see 29.1.9 about possible jail time for doing that.)

20.18.1. Lighthouse Protocol

20.18.1.1. If effective date is stated

If an effective date is stated in the Con­tract, then that's it.

If the Con­tract clearly states that the Con­tract is effective as of a specified date (or as of some date that could be computed in a specified way), THEN: Each party treats that as the effective date of the Con­tract.

(The same is true if the capitalized term "Effective Date" is used.)

Note

There are various ways that a contract can state an effective date. I prefer the approach of this Protocol because it's "cheap insurance" against problems that can arise with other commonly-used styles, as discussed at 20.18.2.1.

20.18.1.2. If the Con­tract dated

If the Con­tract is simply "dated," then that's the effective date.

If the Con­tract does bear a date — for example, by saying, "This Agreement is dated [date]," or the Con­tract is a dated letter agreement — but it doesn't explicitly state that that's the effective date, THEN: Each party treats the Con­tract as having implicitly stated its effective date as set out in § 20.18.1.1 above.

20.18.1.3. Otherwise: Last date signed.

If the Con­tract doesn't clearly state when it is effective, THEN: Each party treats the effective date of the Con­tract as the date that the Con­tract is signed by the last party whose signature is needed to make the Con­tract a legally-binding contract — this can be shown by the circumstances.

20.18.2. Additional notes

20.18.2.1. Some other approaches to the effective date

But: Many drafters prefer to include a specific effective date, or to include a blank to be filled in. Students: It's normally not worth changing if someone else has drafted it this way; when that happens, you have to be careful that the final, signed document doesn't misstate the date signed.

The last-date-signed approach of this Protocol has its advantages, as discussed below:

    This Agreement is effective the last date written on the signature page.

    This 'Agreement' is made, effective the last date signed as written below, between ….

    This Agreement is dated December 31, 20XX, between …. [does that mean it's effective then?]

    This Agreement is made December 31, 20XX, between …. [what if that's inaccurate?]

    This Agreement is dated ………….. [a blank underscored line] between …. [what if no one remembers to fill it in? R.O.O.M.!]

20.18.2.2. Backdating a contract could be OK — or could lead to prison ….

Signing a contract that is "backdated" to be effective as of an earlier date might well be OK. (This is referred to in Latin legalese as nunc pro tunc, or "now for then.") The contract itself should make it clear that parties are doing this, to help forestall later accusations that one or both parties had an intent to deceive.

Example: Suppose that "Alice" discloses confidential information to "Bob," a potential business partner, after Bob first orally agrees to keep the information confidential. Alice might well want to enter into a written nondisclosure agreement with Bob that states the agreement and its confidentiality obligations are effective as of the date of Alice’s oral disclosure.

To that end, Alice and Bob could include language in the Con­tract along the following lines:

This Agreement is being signed on the date(s) indicated in the signature blocks, but it will be effective as of [date]; the parties intend that this Agreement will confirm, and replace, an oral confidentiality agreement entered into by the parties during discussions on or about that date.

Caution: Falsely stating the signature dates (as opposed to the effective date of the contract) could be problematic, and even lead to prison time, as discussed at 3.16.5.

20.19. Encouraged Definition

Each party: When the Con­tract says that you're "encouraged" to take (or not take) an action, the Con­tract doesn't require you to take (or not take) the action.

Note

().  As (hopefully) helpful prompts, some of the Protocols state that one or more parties are "encouraged" to take an action, e.g., when the parties are encouraged to escalate a disagreement about a particular matter.

See also the definition of should, which has an essentially-identical meaning.

20.20. Ending Time Definition

20.20.1. Definition

  1. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference., it applies if the Con­tract states that a time period, a right, an obligation, etc., will end or expire on a specified day.
  2. Unless otherwise stated, that ending or expiration will take place at exactly 12:00:00 midnight at the end of the specified date.
  3. The time zone of that end or expiration will be that of the time zone where the relevant actor, or the action to be taken, is located (or, if applicable, is required to be located) at that time.
Note

().  Precision in end times can be important — when a deadline for action is 11:00 a.m., and the action happens at precisely 11:00:30 a.m., is it untimely? In two real cases of this kind, two different Canadian courts came up with opposite answers.33 So: This Protocol sets out a default rule, which the parties are of course free to vary.

Pro tip: Another time-zone possibility would be to use Coordinated Universal Time, which is basically Greenwich Mean Time with a few technical differences; see generally the Wikipedia article Universal Time.

Time zones are also addressed at Protocol 20.37 (time of day definition).

20.21. Examples Definition

20.21.1. Definition

When an example is used in the Con­tract or related documents, it is for purposes of illustration — and is not intended to be limiting — unless the context makes it unmistakably clear to the contrary.

Note

A longer, negotiated contract might include a section on how to interpret the language, such as section 9.4 of the merger agreement between United Airlines and Continental Airlines, at https://tinyurl.com/UAL-CAL (SEC.gov), reproduced in the following footnote.34

20.21.2. No expressio unius implication

It does not matter if the Con­tract sometimes uses a longer phrase (such as, "by way of example and not limitation") instead of simply, "for example"; in particular, such longer phrases don't imply — and no party is to assert — that shorter phrases (such as, "for example") have a different meaning under the interpretative principle of expressio unius est exclusio alterius.

Note

See the discussion of expressio unius, etc., at 7.7.2.

20.21.3. No ejusdem generis implication

No party is to ask a court or arbitrator to use the contract-interpretation principle of ejusdem generis to limit the meaning of a term that is illustrated by examples.

Note

See the discussion of ejusdem generis at 7.7.3.

20.21.4. Additional notes

20.21.4.1. Include "worked examples" for faster comprehension?

Your contract might contain a complex formula or some other particularly tricky provision. If so, consider including a hypothetical example or sample calculation — preferable a simple one — to "talk the reader through" how the formula or provision is intended to work.

Following that advice, here's a simple example in which subdivisions c and e show both examples and sample calculations. (This is a model provision, not the law.)

  1. Day refers to a calendar day, as opposed to a business day.
  2. A period of X days:
    1. begins on the specified date, and
    2. ends at exactly 12 midnight (see subdivision d concerning time zones) at the end of the day on the date X days later.
  3. Example: Suppose that a five-day period begins on January 1 — that period ends at exactly 12 midnight at the end of January 6.
  4. For purposes of subdivision b, the term 12 midnight refers:
    1. to local time if only one time zone is relevant,
    2. otherwise, to the latest occurrence of 12 midnight on the date in question.
  5. Example: Suppose that both California time and Tokyo time are relevant; in that case, 12 midnight at the end of the day on January 1 refers to 12 midnight at the end of the day on January 1 in California (when it would be mid-afternoon on January 2 in Tokyo).

(These examples could be put in footnotes, as discussed at 8.20.)

In one case, Rhode Island's supreme court rejected a borrower's argument that a lender had miscalculated a particular amount owed, because the calculation exactly matched one of the illustrative examples in a disclosure statement — signed by the borrower — in the relevant loan document. See Guilmette v. PHH Mortgage Services Corp., No. 2024-208, slip op. at 10 (R.I. Jul. 2, 2025) (affirming summary judgment).

In another case, the drafters of $49 million of promissory notes would have been well served to include a sample calculation to illustrate one of their financial-term definitions. The court specifically mentioned particular calculations that the lender had submitted with its motion for summary judgment; if the promissory-note drafters had thought to include one or two sample calculations in the body of the contract itself, then by being forced to work through those sample calculations, the drafters and their client(s) might well have spotted the problems with the promissory-note language in time to fix it before signature. See BKCAP, LLC v. CAPTEC Franchise Trust 2000-1, 572 F.3d 353, 355-57, 359 (7th Cir.2009) ("BKCAP-1") (reversing and remanding summary judgment) after remand, 688 F.3d 810 (7th Cir. 2012) (affirming judgment in favor of borrowers after bench trial).

20.21.4.2. Examples can speed up reader comprehension

Examples are one of the most effective teaching tools. That's significant here because one of the principal goals of any contract is to educate the parties' business people — and, possibly, future judges and jurors — about just what the parties have agreed.

An MIT note points out: "[I]n the field of law, worked examples have been used to teach students how to reason through legal cases and construct legal arguments, while worked examples have similarly been used to assist learners in understanding negotiation strategies." Worked Examples (MIT.edu, undated; citations omitted), archived at https://perma.cc/2TYJ-ECFY.

One professor of education asserts that:

… When a student forms a concept from its examples, he or she knows more than the definition of a term (e.g., river: he or she also knows some vivid examples of the concept that add flesh to a bare-bones definition, such as the Mississippi, the Amazon, the Yangtze, and the Volga). This is deep conceptual learning rather than superficial knowledge of a vocabulary word. Walter Parker, Concept Formation (TeachingHistory.org).

Moreover, you've doubtless seen examples in well-written user manuals.

20.21.4.3. Examples can help business people spot drafting errors

Examples can speed up legal review of a complex formula or some other particularly tricky provision — and help make sure the drafter(s) accurately captured the parties' agreement. So in any such case, drafters should consider including a hypothetical example or sample calculation that "talks through" how the formula or provision is intended to work — such as in the definition of day at 20.15.

(Alternatively, an example could be put in a footnote, as discussed at 8.20.)

Example: In a Seventh Circuit case, the drafters of $49 million of promissory notes would have been well served to include a sample calculation to illustrate one of their financial-term definitions:

  • The court observed that the plain language of the promissory notes "would produce absurd results" and that while the language was clear, "it is nonetheless ambiguous because it makes no economic sense."
  • The court specifically mentioned that the "absurd results" were proved by the example calculations that the lender had submitted to the court with the lender's motion for summary judgment, but that were not part of the promissory notes. See BKCAP, LLC v. CAPTEC Franchise Trust 2000-1, 572 F.3d 353, 355-57, 359 (7th Cir.2009) ("BKCAP-1") (reversing and remanding summary judgment) after remand, 688 F.3d 810 (7th Cir. 2012) (affirming judgment in favor of borrowers after bench trial).

Now imagine that — during the deal negotiations — the drafters of the promissory notes had thought to include one or two such example calculations in the body of the notes. The drafters and their client(s), by being forced to work through those example calculations, might well have spotted the problems with the language in time to fix the problems before signature.

This is an example of following the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings).

20.22. Free (to do X) Definition

  1. Defining by example: When the Con­tract says that a party "P" is "free" to take (or not take) Action A, it has the meaning set forth in this Protocol.
  2. The Con­tract doesn't prohibit P from taking (or not taking) Action A — and P's decision in that regard is within P's sole discretion unless the Con­tract clearly says otherwise.
  3. No other party to the Con­tract "OP" is to assert that P is liable under the Con­tract — nor under any other cause of action in law or equity — if P does take (or doesn't take) Action A.
  4. No third-party beneficiary to the Con­tract (if any), and no person claiming under or through OP in respect of the Con­tract, is to make any such assertion.
  5. BUT: The statement in the Con­tract that P is free to take (or not take) Action A isn't a categorical statement that P would never be liable to others, under some such other cause of action, if warranted by the circumstances.
Note

This is a guardrail definition; it's included because "Party PP is free to take Action A" is more collegial than the (somewhat-officious) term, "Party PP may take Action A" — even though the latter is a few letters shorter.

DCT note: My (adult) daughter once gave me a Father's Day card — the front said, "Thanks for being my dad." The inside said: "You may continue." I laughed out loud — it was such a daughter thing.

20.23. Government Authority Definition

20.23.1. Definition

  1. The terms "government authority" and "governmental authority" refer to any individual or group, anywhere in the world, that exercises governmental- or regulatory power.
  2. The terms should normally be read as including, as applicable and without limitation:
    1. any agency; authority; board; bureau; commission; court; department; executive; executive body; judicial body; legislative body; or quasi-governmental authority,
    2. at any level, for example, state, federal or local.
  3. The governmental- and regulatory power referred to here is intended to include, without limitation, administrative; executive; judicial; legislative; policy; regulatory; and/or taxing power.
Note

This is a convenience definition — which doesn't address whether government authority includes irregular bodies such as militias and insurgencies that exercise de facto power in particular territories.

20.24. Hold Harmless Definition

20.24.1. Definition

The term "Hold harmless" (whether or not capitalized) has the same meaning as indemnify (defined at Protocol 14.3).

Note

This definition reflects what seems to be a consensus by legal-writing experts and most courts: The term hold harmless is the second part of the doublet indemnify and hold harmless — it doesn't impose any separate obligation apart from indemnify.

As explained by preeminent legal lexicographer Bryan Garner: "The evidence is overwhelming that indemnify and hold harmless are perfectly synonymous. The first is Latinate, the second Anglo-Saxon. And it would be possible to multiply 20th- and 21st-century authorities to this effect." See Bryan A. Garner, indemnify [sic], 15 Green Bag 2d 17, 21 (2011), archived at http://perma.cc/4VBV-FDJS; see also Bryan A. Garner, Garner's Dictionary of Legal Usage 443-45 (2011), http://goo.gl/LdVxN; see also Adams v. Atkinson, No. SC-2024-0528 (Ala. May 16, 2025).

True: This would seem to go against the usual rule that courts try to construe contracts so as to give effect to each provision, without ignoring any as "surplusage." But Garner addresses this problem in his Green Bag piece, at 22.

20.25. Including Definition

20.25.1. Definition

  1. The word "including" (whether or not capitalized) means "including, but not limited to" unless clearly stated otherwise.
  2. The same is true for similar phrases such as including, without limitation, possibly with parentheses instead of commas or even with no internal punctuation — these are illustrative, non-limiting examples, of course.
  3. In case a question comes up: Even if a document uses the term "including but not limited to," the shorter term including, by itself, still has the meaning stated in this Definition.
Note

().  This Definition seeks to "write around" the principle of ejusdem generis ("eh-USE-dem GENerous"), discussed at 7.7.3.

Subdivision B is kinda meta ….

Subdivision C is intended as a guardrail against the principle known as expressio unius est exclusio alterius, "to express one thing is to exclude others," discussed at 7.7.2.

For additional notes in this general area, see 7 (ambiguity).

20.26. Material (breach, etc.) (notes)

().  It's not uncommon for a contract — with an eye to future litigation — to include a stipulation about what can constitute a material breach (not unlike a liquidated-damages clause). Generally, the drafter is planning for the case where the other party breaches the contract, to make it easier for the drafter's client to terminate the contract and make the termination stick in court, without having to extensively litigate whether the breach is "material" or not.

Example: A real-estate lease might state that the tenant's failure to pay rent when due, after notice and an opportunity to cure, is a material breach that would allow the landlord to terminate the lease. Courts will often give effect to such contractual stipulations about materiality.

Example: In its Indiana v. IBM decision, Indiana's supreme court held that under state's law, the contract's specification of agreed standards of materiality took precedence over a Restatement of Contracts analysis: "… when a contract sets forth a standard for assessing the materiality of a breach, that standard governs. Only in the absence of such a contract provision does the common law, including the Restatement, apply." Indiana v. IBM Corp., 51 N.E.3d 150, 153 (Ind. 2016).

Subdivision 2: The "as a whole" language is modeled on section 16.3.1(1)(A) of the master service agreement in the Indiana v. IBM case, cited above.

Caution: Subdivision 2 might well reduce the likelihood of getting summary judgment about the materiality or immateriality of a partiuclar breach, because the "as a whole" requirement could be intensely factual.

In non-breach contexts, something is often considered material (for example, material information) if a substantial likelihood exists that a reasonable person would consider the thing important in making a relevant decision. See, e.g., Basic Inc. v. Levinson, 485 U.S. 224, 231-32 (1988) (defining material in the context of securities law).

Contract-drafting maven Ken Adams suggests not using the term "material," and instead using either "more than trivially" or "dealbreaker": "Using dealbreaker is novel, and it might seem awkward or insufficiently sober, but given the pervasive legalistic blather long inflicted on readers of traditional contract drafting, you should at least consider deploying a no-nonsense neologism." Kenneth A. Adams, The Word Material Is Ambiguous in Contracts, Why That’s a Problem, and How to Fix It, SCRIBES J. Legal Writing 83, 99 (AdamsDrafting.com 2023).

20.27. Month Definition

20.27.1. Definition

  1. Unless the Con­tract clearly states otherwise, the term "month" refers to calendar months.
  2. Defining by example: Unless the Con­tract specifies otherwise, a stated number of months after a par­tic­u­lar date will end as follows:
    1. One month after January 15 is February 15.
    2. One month after January 29, 30, or 31 is February 28 (or February 29 in a leap year).
    3. One month after February 28 (or February 29 in a leap year) is March 31.
    4. One month after April 30 is May 31.
    5. One month after May 30 is June 30; two months after May 30 is July 30.
Note

().  In some places, the provisions of this book measure time in months instead of days — e.g., three months instead of 90 days — to spare the reader from having to count days over a multi-month period; this Definition is provided for greater precision and to help try to avoid later disputes.

Note the use of examples, for reasons discussed at 20.21.

20.28. Party Definition

20.28.1. Definition

In case of doubt: The term "party" (whether or not capitalized) refers only to those individuals and organizations that are signatory parties to the Con­tract unless the context clearly requires otherwise.

Note

This Definition is provided for clarity; it ties in with Protocol 11.8 (third party beneficiaries).

20.29. Person Definition

The term person refers to: (1) a natural person, also referred to sometimes as an "individual"; and/or (2) an organization — of any kind — such as (for example) a corporation, a partnership, a limited liability company, a nonprofit association, etc.

Note

In this definition, we see the same underlying concepts as in U.S. securities law, which states:

The term “person” means an individual, a corporation, a partnership, an association, a joint-stock company, a trust, any unincorporated organization, or a government or political subdivision thereof. As used in this paragraph the term “trust” shall include only a trust where the interest or interests of the beneficiary or beneficiaries are evidenced by a security. 15 U.S.C. § 77b(a)(2).

Similarly, section 1-201(27) of the Uniform Commercial Code states:

(27)  "Person" means an individual, corporation, business trust, estate, trust, partnership, limited liability company, association, joint venture, government, governmental subdivision, agency, or instrumentality, public corporation, or any other legal or commercial entity.

20.30. Possession, Custody, or Control Definition

20.30.1. Definition

The term "possession, custody, or control" has the meaning used in federal-court litigation in the United States.

Note

This Definition is modeled on the initial-disclosure rule for federal-court litigation: Under Fed. R. Civ. P. 26(a)(1)(A)(ii) and 34(a)(1), any relevant document within a party's possession, custody, or control would be fair game for mandatory production. Moreover, if a party might use a document to support its claims or defenses in the dispute, then the document would be "relevant" unless the anticipated use of the document would be solely for impeachment. See generally, e.g., The Sedona Conference, Commentary on Rule 34 and Rule 45 "Possession, Custody, or Control,"” 17 Sedona Conf. J. 467 (2016).

20.31. Recklessness Definition

When a contract addresses the subject of recklessness, it's typically by way of "carve-outs" from a party's rights, for example, by saying: • in a limitation of liability, that a party's liability (e.g., for breach) won't be limited after all if it behaved recklessly, as discussed at 21.7.8.3; and/or • that a protected party won't be entitled to defense against a third-party claim, nor to indemnity against harm, if its own recklessness was the cause of the claim.

20.31.1. Definition

A person (the "actor") acts recklessly when:

  1. the actor: • consciously disregards • a substantial and unjustifiable risk • that harm to another will result • from the actor's conduct; and
  2. the risk of harm disregarded is of such a nature and degree that — considering the nature and purpose of the actor's conduct and the circumstances known to the actor — the disregard of the risk involves a gross deviation from the standard of conduct with which a reasonable person would comply in the actor's situation.
Note

().  This definition is based on Model Penal Code 2.02(c), as implemented in, e.g., Tex. Pen. Code 6.03(c). In the First Amendment context, the Supreme Court of the United States has used a substantially-identical definition of reckless. See Counterman v. Colorado, 600 U. S. _  _, No.  part II.B, slip op. at 11 (2023) (citing cases).

Some of the terms used here — such as substantial and unjustifiable risk and gross deviation — are of course vague and likely to be the subject of "debate" (spelled: l-i-t-i-g-a-t-i-o-n).

20.31.2. Additional notes

Cross-references:

  • 14.1 (claim defense protocol)
  • 21.15 (gross negligence definition)
  • 14.3 (indemnity protocol)
  • 21.18 (limitations of liability general provisions).

20.32. Record (as noun) Definition

Records Definition (noun)

The term "record" (preferably but not necessarily capitalized), in the context of documents and the like, refers to books, documents, and other information stored in any tangible- or intangible medium regardless of type, without regard to whether they are in written; graphic; audio; video; or other form.

Note

This definition is adapted from the (U.S.) Federal Acquisition Regulations, Contractor Records Retention, 48 C.F.R. § 4.703(a) (which contains additional requirements about retention and storage of records).

20.33. Relating to Definition

In case of doubt: The term "relating to" something — e.g., as part of the phrase "arising out of or relating to this Agreement" — is to be understood as:

  • based upon,
  • arising out of,
  • directly or indirectly resulting from or in consequence of, or
  • in any way involving,

the thing in question.

Note

().  This wording is adapting from the language of an insurance policy that was litigated in Zaftr Inc. (E.D. Pa. 2025). See Zaftr Inc. v. Kirk, No. 24-2702, slip op. (E.D. Pa. Oct. 29, 2025) (granting insurance carrier's motion for summary judgment: claimed loss was clearly excluded by policy terms) (citing Pennsylvania- and Third-Circuit case law).

See also the notes at 32.2.

The term "arising out of or relating to" is usually interpreted broadly by courts — as the Tenth Circuit explained concerning similar wording:

Courts have generally interpreted language such as "arising from or in connection with" quite expansively.

To say that a dispute is one "arising from or in connection with maintenance performed by Williams" is to say that it had some causal connection to—that it originated from, grew out of, or flowed from—such maintenance. Dodson Int'l Parts, Inc. v. Williams Int'l Co., 12 F.4th 1212, 1220-21 (10th Cir. 2021) (extra paragraphing added, extensive citations omitted).

Note

This seems to be the law in at least some jurisdictions. See Zaftr Inc. v. Kirk, No. 24-2702, slip op. (E.D. Pa. Oct. 29, 2025) (granting insurance carrier's motion for summary judgment: claimed loss was clearly excluded by policy terms) (citing Pennsylvania- and Third-Circuit case law).

The term "relating to" is relatively broad (compared with the narrower "arising out of") but it's not of unlimited scope: In the context of determining the scope of an arbitration agreement, in 2017 the Ninth Circuit noted:

And though we have recognized that the phrase 'relate to' is broader than the phrases 'arising out of' or 'arising under,' … "related to" marks a barrier by indicating some direct relationship; otherwise the term would stretch to the horizon and have no limiting purpose …. United States and Nevada ex rel. Welch v. My Left Foot Childrens Therapy, LLC, 871 F.3d 791, 798 (9th Cir. 2017) (cleaned up, citations omitted).

In 2023, Delaware's chancery court had this to say:

This Court has considered the connector "relating to" to be paradigmatically broad. Indeed, the term "relating to" is one of the far-reaching terms often used by lawyers when they wish to capture the broadest possible universe. Given its breadth, a provision that extends to matters "relating to" an agreement encompasses *any issues that touch on contract rights or contract performance." Intrepid Investments, LLC v. London Bay Capital, LLC, No. 12077, slip op. at text acc. nn.67-74. (Del Ch. Jun. 21, 2023) (cleaned up, footnotes omitted, emphasis added). Hat tip: Ken Adams (AdamsDrafting.com).

Following this principle, the Delaware court held that the plaintiff's new claims for fraudulent transfer were barred by the res judicata effect of a judgment in a prior lawsuit between the parties in New York's courts, because:

  • The plaintiff's new fraudulent-transfer claims did not "touch on" the rights and performance of an LLC operating agreement, which included a forum-selection clause requiring litigation in Delaware of any claim "arising out of or relating in any way to this [Operating] Agreement."
  • The plaintiff therefore could have brought the fraudulent-transfer in the New York lawsuit, not merely in Delaware.
  • Consequently, the new fraudulent-transfer claims were barred by the res judicata effect of the results in the New York lawsuit.

On the other hand, said the Delaware court, the plaintiff's new claims for tortious interference were not barred by res judicata from the New York lawsuit because the tortious-interference claims did "touch on" the rights and performance of the LLC operating agreement, and so the claims were subject to the operating agreement's forum-selection clause, and thus could not have been brought in the New York lawsuit.

Variation: In 2023, the First Circuit noted (in a dictum) that a third-party claim might "arise from" an indemnifying party's act but not be "caused" by the act. See Caruso v. Omni Hotels Mgmt. Corp., 61 F.4th 215, 223 (1st Cir. 2023) (vacating judgment below and directing entry of judgment for Omni) (dictum; observin that "'arises from' in the [contract in suit] carries materially the same meaning as 'caused by'").

20.34. Representation Definition Protocol

Business context: A contract will sometimes state that a party "represents" a fact, or perhaps that the party "represents and warrants" the fact. Legally, though, the verb represent and its noun form representation can be significantly different than the verb warrants and its noun form warranty. Students: Be sure to read 16.2 (basics of reps and warranties), especially the discussion of the "Hill of Proof" at 16.2.2.

20.34.1. A represention asserts truth + reasonable basis.

Unless limited by § 20.34.2 below: When a party "RP" (for "Representing Party") makes a representation, RP thereby asserts the following:

  1. that — so far as RP is aware at the time RP makes the representation — the represented fact is true; and
  2. that RP has a reasonable basis for making the assertion as stated.
Note

This places the burden on the representing party RP to disavow that it has a reasonable basis for its representation; see the additional discussion at 20.34.6.8.

20.34.2. Each other party may rely on both assertions.

Whenever RP represents the truth of a matter in the Con­tract itself, RP thereby acknowledges (see § 11.2) that that one or more other signatory parties to the Con­tract are rebuttably presumed to reasonably rely — for a serious purpose — on RP's assertion both (1) of the represented fact itself, and (2) that RP's having a reasonable basis for the assertion.

Note

().  If the parties hadn't intended a representation to be relied on, presumably they wouldn't have stated the representation in the Con­tract itself. (The reliance issue is discussed in more detail at 20.34.6.2.) But: Because the presumption of reliance on a representation is rebuttable, the representing party RP can try to show that, under the circumstances, it was unreasonable for the other party to rely on the representation, for example, because the other party had reason to know that the representation was incorrect.

The reliance "for a serious purpose" language is modeled on the famous holding in Basic Industries (1988), by the (U.S.) Supreme Court, in the area of securities law: "Because most publicly available information is reflected in market price, an investor's reliance on any public material misrepresentations, therefore, may be presumed for purposes of a Rule 10b-5 action." Basic Inc. v. Levinson, 485 U.S. 224, 247 (1988).

20.34.3. The Con­tract could limit misrepresentation liability.

If clearly so stated in the Con­tract, a representation may limit one or more of:

  1. the represented fact;
  2. RP's basis for the representation;
  3. the signatory parties to the Con­tract that are entitled to rely on those things; and/or
  4. the representing party's liability for misrepresentation.

20.34.4. A representation may limit who may rely.

Defining by example: If a representation is phrased in terms similar to, "Alice represents to Bob," then only Bob may rely on that representation.

Note

Concerning defining by example, see 20.21.4.2.

20.34.5. New York law will govern this Protocol.

In the interest of uniformity: Any dispute relating to whether RP's representation was allegedly negligent, reckless, or intentional is to be decided under the substantive law of New York, regardless what law might govern the dispute in any other respect.

Note

New York law (discussed at at 16.2.2) is specified here as a uniform gap-filler. The parties can of course specify a different law in the Con­tract. (See the commentary at 21.14.5.17 concerning the notion of choosing a law to govern one specific section of a contract.)

20.34.6. Additional notes

20.34.6.1. Overview: What is a "representation"?

A representation is generally understood as a statement of past- or present fact (and, rarely, of future fact).

(Contrast with a warranty, which could also include future fact; see

Whether a party that makes a representation will be liable for misrepresentation will depend on whether the party can prove a number of facts, discussed at 16.2.2 above.

( The "past or present fact" formulation is suggested by Professor Tina Stark [RIP 12/21/2025] in her highly-regarded Drafting Contracts textbook.)

20.34.6.2. Extra proof requirements over warranties

If you haven't already, take a look at the "Hill of Proof" diagram for representations and warranties, at 16.2.2, reproduced here for convenience:

As seen in the upper portion of the Hill of Proof: If Ginger represents a fact to Fred, and Fred later wants to sue Ginger for misrepresentation:

1.  Fred must show that he relied on Ginger's representation — but that usually won’t be a heavy burden if the representation is explicitly stated in the contract; in fact, Minnesota's supreme court held in 2014 that "a claim for breach of a contractual representation of future legal compliance is actionable under Minnesota law without proof of reliance." Lyon Fin. Serv., Inc. v. Illinois Paper & Copier Co., 848 N.W.2d 539, 540 (Minn. 2014) (on certification from 7th Circuit) (emphasis added).

And in a 2020 case, the Seventh Circuit, applying Illinois law, held that: "The warranty sued on here was part of the parties' agreement, so the plaintiff did not need to prove further reliance." Abellan v. Lavelo Prop. Mgmt. LLC, 948 F.3d 820, 832-33 (7th Cir. 2020) (emphasis added).

2.  Fred must also show that his reliance on Ginger's representation was reasonable under the circumstances — again, the chances are that reasonableness of reliance would be presumed, but perhaps Ginger could show that reliance was unreasonable because Fred should have seen that the representation was problematic. See, e.g., JPMorgan Chase Bank v. Orca Assets GP, 546 S.W.3d 648 (Tex. 2018) (on the specific facts of the case, "red flags" made it unreasonable for plaintiff to rely on bank's alleged misrepresentations).

3.  And Fred must show that Ginger acted negligently, or recklessly, or even intentionally (i.e., fraudulently), in making the (mis)representation — i.e,. he must show that Ginger acted with scienter, discussed in more detail below.

If Fred can prove up these additional elements — over and above the elements required to prove breach of warranty — then he might well be entitled to tort-like remedies that would not normally be available for a plain breach of contract or warranty, such as punitive damages and/or rescission of the contract. See, e.g., Nami Resources Co., L.L.C. v. Asher Land & Mineral, Ltd., 554 SW 3d 323, 328 (Ky. 2018) (vacating award of punitive damages for what was essentially a breach of contract); Lucarell v. Nationwide Mut. Ins. Co., 2018 Ohio 15, 152 Ohio St. 3d 453, 97 N.E.3d 458: "Ohio common law provides that punitive damages may not be awarded for breach of contract, no matter how willful the breach." (Citations omitted.) ]

In some jurisdictions, punitive damages might be available if the defendant's conduct would have been tortious outside the context of a contract. See, e.g., Van Rees v. Unleaded Software, Inc., 2016 CO 51 ¶ 19, 373 P.3d 603, 608 (Colo. 2016); N.Y. Univ. v. Cont'l Ins Co., 87 N.Y.2d 308, 315-16, 662 N.E.2d 763 (1995).

20.34.6.3. Proof requirements for fraudulent misrepresentation

If Fred wants to prove that Ginger committed fraud, New York law is fairly typical: “The elements of a cause of action for fraud require a material misrepresentation of a fact, knowledge of its falsity, an intent to induce reliance, justifiable reliance by the plaintiff and damages." Eurycleia Partners, LP v. Seward & Kissel, LLP, 12 N.Y.3d 553, 559, 910 N.E.2d 976, 883 N.Y.S.2d 147 (2009) (citations omitted).

Similarly, under Texas law, the Texas supreme court explained in its 2011 decision in Italian Cowboy Partners:

The elements of fraud are:

(1) that a material representation was made;

(2) the representation was false;

(3) when the representation was made, the speaker[:]

  • knew it was false or
  • made it recklessly without any knowledge of the truth and as a positive assertion;

(4) the speaker made the representation with the intent that the other party should act upon it;

(5) the party acted in reliance on the representation; and

(6) the party thereby suffered injury. Italian Cowboy Partners, Ltd. v. Prudential Ins. Co., 341 S.W. 3d 323, 337 (Tex. 2011) (emphasis and extra paragraphing added, citation omitted).

Note the absence here of a requirement that the plaintiff prove that the reliance was justified or reasonable; this is one respect in which Texas law differs from New York law (discussed just above).

20.34.6.4. Proof requirements for negligent misrepresentation

Fred might settle for proving negligent misrepresentation by Ginger; note the as the Second Circuit explained in 2012:

… under New York law, the plaintiff must allege that (1) the defendant had a duty, as a result of a special relationship [such as privity of contract–DCT], to give correct information; (2) the defendant made a false representation that he or she should have known was incorrect; (3) the information supplied in the representation was known by the defendant to be desired by the plaintiff for a serious purpose; (4) the plaintiff intended to rely and act upon it; and (5) the plaintiff reasonably relied on it to his or her detriment. Anschutz Corp. v. Merrill Lynch & Co., 690 F.3d 98, 114 (2d Cir. 2012) (granting motion to dismiss claim of negligent misrepresentation; cleaned up, citations omitted), quoted in Kortright Capital Partners LP v. Investcorp Investment Advisers Ltd., 257 F. Supp. 3d 348, 355 (S.D.N.Y. 2017) (denying motion to dismiss claims of negligent misrepresentation).

Somewhat similarly, in Texas as in many other states, the courts follow Restatement (Second) of Torts § 552 (1977) in defining negligent misrepresentation as:

(1) the representation is made by a defendant in the course of his business, or in a transaction in which he has a pecuniary interest;

(2) the defendant supplies ‘false information’ for the guidance of others in their business;

(3) the defendant did not exercise reasonable care or competence in obtaining or communicating the information; and

(4) the plaintiff suffers pecuniary loss by justifiably relying on the representation. Federal Land Bank Ass'n of Tyler v. Sloane, 825 S.W.2d 439, 442 (Tex. 1991) (affirming judgment for prospective borrowers on jury verdict of negligent misrepresentation by bank loan officer; extra paragraphing added), followed in McCamish, Martin, Brown & Loeffler v. F.E. Appling Interests, 991 S.W.2d 787, 791 (Tex. 1999) (claim against attorneys by non-client) and Grant Thornton LLP v. Prospect High Income Fund, 314 SW 3d 913, 920 (Tex. 2010) (investors’ claim against auditors).

It bears noting that "California courts have expressly rejected that requirement [of privity of contract or other a special relationship], holding that negligent misrepresentation claims may be brought angainst any person who negligently supplies false information for the guidance of others in their business transactions and intends to supply the information for the benefit of one or more third parties." Anschutz Corp., 690 F.3d at 113 (cleaned up; emphasis added).

20.34.6.5. Can fraudulent-inducement claims be precluded?

One way to preempt a possibe fraud-in-the-inducement claim is for the contract to disclaim external representations. But: This requires a bit more work than simply disclaiming warranties that aren't stated expressly in the contract.

  • That's generally because, understandably, a court is likely to be reluctant to let a party off the hook if it appears that the party was untruthful, or even merely negligent, in what it said to another party.
  • What drafters do to (try to) preclude later claims of misrepresentation is to include reliance waivers; see generally 11.7: Reliance Waiver Option.
20.34.6.6. Pro tip: Don't use represents to commit to future action

Contract drafters shouldn't use the term represents to indicate that a party will take or abstain from action — commitments to future action should instead be written as promises (covenants).

    Ginger represents that she will pay Fred $1 million.

    Ginger represents and warrants that she will pay Fred $1 million.

    Ginger will pay Fred $1 million.

    Ginger represents that she will not use Fred's confidential information except as stated in the Con­tract.

    Ginger will not use Fred's confidential information except as stated in the Con­tract.

(Leave out the italics, usually.)

Why? Consider the first example above: If Ginger failed to pay Fred, she might try to claim that she should not be liable for nonpayment because when she made the representation, she had no reason to believe that she would not make the payment. A court might treat such a "representation" as a simple promise, but the drafter would do all concerned a disservice by not making the obligation explicit and unconditional. See Lyon Fin. Serv., Inc. v. Illinois Paper & Copier Co., 848 N.W.2d 539 (Minn. 2014) (on certification from 7th Circuit) (holding that "a claim for breach of a contractual representation of future legal compliance is actionable under Minnesota law without proof of reliance").

20.34.6.7. Trial lawyers love misrepresentation claims: "They lied!"

In a contract dispute, an aggrieved party might well claim that another party "fraudulently induced" the aggrieved party into entering into the contract by making supposedly-false statements that weren't set out in the contract itself. This often happens in complex business- and technology cases, where a non-expert fact finder, such as a judge or juror, might not fully understand the details of a case — but she probably would understand the simple claim "they lied!"

Bryan Garner points this out in his famed dictionary of legal usage:

[S]ome parties to a contract don’t want merely a guarantee that so-and-so will be so in the future; they also want an eye-to-eye statement (representation) that the thing is so now. If it later turns out not to have been so when the representation was made, the party claiming breach can complain of a lie.

If only a warranty were in place, the breaching party could simply say, “I’ll make good on your losses—as I always said I would—but I never told you that such-and such was the case.” Hence representations and warranties. Bryan A. Garner, Representations and warranties, Garner’s Dictionary of Legal Usage (3d ed. 2011) (quotation lightly edited), quoted in Ken Adams, Revisiting “Represents and Warrants”: Bryan Garner’s View (AdamsDrafting.com 2011).

Fraud claims can also turn a relatively-straightforward business dispute into an expensive lawyer tangle, with lots of discovery requests and motion practice that increase costs for all concerned.

The following sections offer a few real-world examples:

Example: British Sky Broadcasting v. EDS: British Sky Broadcasting ("Sky") contracted with EDS to develop a customer relationship management (CRM) software system. The project didn't go as planned, and Sky eventually filed suit. In the (non-jury) trial:

  • The judge concluded that EDS had made fraudulent misrepresentations when one of EDS's senior UK executives, wanting very much to get Sky's business, lied to Sky about EDS's analysis of the amount of elapsed time needed to complete the initial delivery and go-live of the system.
  • A limitation-of-liability clause in the EDS-Sky contract capped the potential contract damage award at £30 million.
  • By its terms, though, that limitation of liability did not apply to fraudulent misrepresentations. See BSkyB Ltd. v. HP Enterprise Services UK Ltd., [2010] EWHC 86 (TCC), paras. 194-196, 372-389.

In early June 2010, EDS reportedly agreed to pay Sky some US$460 million — more than four times the value of the original contract — to settle the case. See Jaikumar Vijayan, EDS settles lawsuit over botched CRM project for $460M, Computerworld, June 9, 2010 ]

Example: In 2020, the Southern District of New York confirmed a €643 million arbitration award for fraudulent inducement to enter into a contract for the sale of a business. The arbitral tribunal had remarked that, "This is a case of true and pervasive fraud, where the active participants did not inadvertently stumble into mistakes, but rather took systematic steps to mislead Claimants and then to try to cover their trail." The limitation of liability in the contract (a damages cap) applied only to the seller's indemnity obligation, not to fraud claims. See Precision Castparts Corp. v. Schulz Holding GmbH & Co. KG, No. 1:20-cv-03029 (S.D.N.Y. July 20, 2020); see generally 21.18

Example: Oregon v. Oracle: We see another example of "they lied!" in the 2014 $3 billion civil suit filed by the state of Oregon against software giant Oracle Corporation, in which the second paragraph of the complaint said, in its entirety:

Oracle lied to the State about the “Oracle Solution.”

Oracle lied when it said the “Oracle Solution” could meet both of the State’s needs with Oracle products that worked “out-of-the-box.”

Oracle lied when it said its products were “flexible,” “integrated,” worked “easily” with other programs, required little customization and could be set up quickly.

Oracle lied when it claimed it had “the most comprehensive and secure solution with regards to the total functionality necessary for Oregon.” Extra paragraphing added. For a related federal case, see Oracle America, Inc. v. Oregon Health Ins. Exch. Corp., 80 F. Supp. 3d 1168 (2015) (disposing of various motions; recapping factual history at 1169).

Moreover, the state named various Oracle managers and executives, personally, as co-defendants in a multi-million lawsuit over a failed software development project, with the state suing one Oracle technical manager for $45 million (!).

The lawsuit was later settled — Oracle agreed to pay Oregon $25 million in cash and provide the state with another $75 million in technology.

Here's a wild speculation, based on zero evidence: It seems possible that the state sued the individuals personally to try to motivate them to cooperate with the state, akin to when criminal prosecutors bring indictments against all kinds of people to encourage them to cooperate in return for dismissal or a lighter sentence.

Example: A software developer found itself having to defend against a customer's claim that the developer had not only breached its contract but also that the developer induced the customer to enter into the contract "with false promises of its capabilities to perform web-related services." The Colorado supreme court held that those allegations "state a violation of a tort duty that is independent of the contract" and thus should not have been dismissed under the economic-loss doctrine. See Van Rees v. Unleaded Software, Inc., 2016 CO 51 ¶ 3, 373 P.3d 603, 605 (Colo. 2016).

20.34.6.8. Pro tip: Disclaim investigation of representations?

Protocol 20.34 explicitly states that a party making a representation is also certifying that the party has a reasonable basis for the representation. This is to try to forestall parties from recklessly making representations about things of which they know not.

(Compare with Rule 11(b) of the Federal Rules of Civil Procedure, which states that a person signing a federal-court pleading is certifying the contents "to the best of the person's knowledge, information, and belief, formed after an inquiry reasonable under the circumstances ….")

This could end up being important. Example: In 2019, a natural-gas provider was hit with a judgment for some $9 million for fraudulent inducement and negligent misrepresentation, because (the court found) the provider had recklessly represented to a customer that the provider had certain capabilities, when the provider "did not do any investigation as to whether [it] could satisfy this obligation …."35

Here's a hypothetical example: Suppose that Ginger is selling Fred a used car that she has been keeping in a garage in another city; she wants to represent, but not warrant, that the car is in good working order. She could phrase her representation in one of two basic ways:

–  Phrasing 1: Ginger says, "I represent that the car is in good working order." Under 20.34, Ginger is implicitly making an ancillary representation, namely that she has a reasonable basis for her main representation that the car is in good working order, perhaps because she recently drove it or had it checked out by a mechanic.

–  Phrasing 2: "So far as I know, the car is in good working order." By using the phrase so far as I know, Ginger should be held to have implicitly disclaimed any such ancillary representation.

(Ginger could make the disclaimer of Phrasing 2 even strongly by saying, for example: "So far as I know, the car is in good working order, but it's been sitting in the garage for years and I have no idea what kind of shape it's in.")

20.34.6.9. Pro tip: Be careful about saying, "to my knowledge …"

Some representations use phrasing such as "to [party name's] knowledge, X is true" — this is unwise, in the present author's view, because it could be argued to mean that the representing party is implicitly representing that it does indeed have knowledge that X is true. That argument should not prevail, but (to paraphrase a former student) that's a conversation we don't want to have.

20.35. Shall Definition

20.35.1. "Shall" is mandatory, not permissive

  1. Protocol 10.1 (explaining the use of different fonts, etc.) is incorporated into this Protocol by reference., it applies for the avoidance of doubt unless the context clearly and unmistakably requires otherwise.
  2. Terms such as "A shall take Action X" mean that A is required to take Action X.
  3. Likewise, terms such as "B shall not take Action Z" means that B is prohibited from taking Action Z.
Note

Probably the majority of contracts (at least those drafted in the U.S.) use the term shall to impose obligation. But that might not always be the case, because in some contexts, "shall" might be treated as tentative or optional; see 20.35.2.

Stylistically, a plain-language drafting guide published by a coalition of (U.S.) federal employees says: "Besides being outdated [sic], 'shall' is imprecise. It can indicate either an obligation or a prediction." Federal Plain Language Guidelines at 25 (PlainLanguage.gov 2011) (emphasis added).

(Update January 2026: The PlainLanguage.gov Web site has been taken offline and replaced by comparable content at digital.gov.)

20.35.2. Shall Definition: Additional notes

20.35.2.1. Shall as optional?

In interpreting certain statutes, the Supreme Court has sometimes treated shall as indicating optional action. See Smith v. Spizzirri, No. 22–1218, 601 U. S. __, slip op. at 4 (May 16, 2024) (reversing and remanding Ninth Circuit decision). See also Florida v. Georgia, 585 U.S. __, 138 S. Ct. 2502, 2511, 2520 (2018); Town of Castle Rock v. Gonzales, 545 U.S. 748 (2005); Gutierrez de Martinez v. Lamagno 515 U.S. 417, 433 n.9 & accompanying text (1995); id. at 439 & n.1 (Souter, J., dissenting).

Likewise, in some other English-speaking countries, in some contexts the term shall might be construed as tentative or optional, not as mandatory. See, e.g., a New Zealand legislative drafting guide ("'Shall' is less and less commonly used, partly because it is difficult to use correctly. 'Shall' is now rarely used in New Zealand legislation …. 'Must' should be used in preference to 'shall' because it is clear and definite, and commonly understood") and an Australian legislative-drafting guide, at ¶ 83 (from archive.org).

Example: In a 2020 case the D.C. Circuit held that shall was indeed mandatory in a contract's forum-selection clause — but the court seemed to think that the contrary argument wasn't frivolous. See D&S Consulting, Inc. v. Kingdom of Saudi Arabia, 961 F.3d 1209, 1213-14 (D.C. Cir. 2020) (affirming dismissal).

20.36. Should Definition

20.36.1. Definition

  1. As (hopefully) helpful prompts, some of the Protocols state that a party "should" take an action, or often, "should consider" taking an action. Such statements
  2. In a Protocol, a statement that a party "should" take some action means that in principle the action is likely to be a good idea, but the party has no obligation to take the action.
  3. Similarly, a statement in a Protocol that a party "should not" take an action means that the Protocol doesn't preclude a party from taking the action, even if the action might not necessarily be the best course in a given situation.

20.37. Time of Day Definition

20.37.1. Definition

  1. A specified time of day refers to the exact time. Hypothetical example: If a stated deadline for submitting a bid is 5 p.m., and a party submits a bid at 0.01 second after exactly 5:00.00 p.m., THEN: That bid is late.
  2. A time of day refers to the following (in the interest of standardization) unless clearly agreed otherwise in writing:
    1. to local time if only one time zone is relevant,
    2. otherwise, to the time, on the date in question, in the time zone of:
      [ x ] the latest occurrence of the stated time.
      [    ] the earliest occurrence of the stated time.
  3. As a hypothetical example:
    1. Alice, in Honolulu, and Benjiro, in Tokyo, enter into a contract.
    2. The contract specifies a particular deadline of 12 midnight at the end of the day on January 1, but does not specify the time zone for the deadline.
    3. In that situation, the deadline expires at 12 midnight at the end of the day on January 1 in Honolulu, when it is early evening on January 2 in Tokyo.
Note

().  Contractual rights and obligations can sometimes turn on the time of day, about which the Texas supreme court has said that "contractual clarity is often every bit as important when talking about time as about anything else." Apache Corp. v. Apollo Exploration, LLC, 670 S.W.3d 319, 321 (Tex. 2023) (reversing and remanding court of appeals).

Concerning ending time, see Protocol 20.20.

Subdivision C: These hypothetical names are adapted from the tech world's "Alice and Bob."

For additional examples, see the comments at 20.20.

Concerning hypothetical examples generally, see 20.21.4.2.

Exercise

FACTS:

  1. "Buyer" and "Seller" have entered into a master purchase agreement ("MPA").
  2. Under the MPA, Buyer can send purchase orders to Seller, at steeply-discounted pricing, but that pricing lasts only until December 31.
  3. On December 31, Seller leaves work at her usual quitting time of 6:00 p.m. (Let's assume that Buyer and Seller are in the same time zone.)
  4. That evening, Buyer emails a purchase order to Seller, stating the discounted pricing. Seller's email system records Buyer's email as having arrived at 11:59 p.m.
  5. Neither Buyer nor Seller go to work or check their emails on New Year's Day.
  6. On January 2, Seller sees Buyer's purchase-order email for the first time; she emails Buyer to say, sorry, you're too late, your steep discount expired, and the higher pricing applies.
  7. Buyer is not happy and complains about it; Seller isn't happy to have to deal with a disgruntled customer.

QUESTION 1: Should Buyer get the steeply-discounted price?

QUESTION 2: Could the MPA drafters have averted this situation — and the resulting dent in the parties' business relationship?

20.38. Timely Definition

20.38.1. Definition

  1. An action relating to the Con­tract is timely (or "seasonable") if the action is taken:
    1. at or within the specific time agreed, if any; or
    2. if no specific time is agreed, then at or within a reasonable time.
  2. A party's failure to timely perform an action when required by the Con­tract would be a breach of the Con­tract, but not a material breach (see the definition in Protocol 18.6), unless clearly agreed otherwise.
Note

().  This definition borrows from the definition of of seasonably in UCC 1-205. (Some modern readers seem not to be familiar with the term seasonably.)

Subdivision B: See generally Time is of the essence (law.cornell.edu).

20.39. Voting Power Definition

20.39.1. Definition

  1. Defining by example: Consider a corporation, having a board of directors whose members are elected by holders of voting shares.
  2. For that corporation, 50% of the "Voting Power" of the corporation refers to one or more of the following legally-enforceable rights: (see 20.39.2):
    1. the right to vote at least 50% of the voting shares of each class of shares entitled to vote; and/or
    2. the right to select at least 50% of the members of the board of directors.
Note

().  Voting power can matter in, for example:

  • whether two individuals and/or organizations are "affiliates" (see Protocol 20.1);
  • what counts as a "change of control" (see Protocol 20.9);
  • the scope of a "no-shop clause" in a merger- or acquisition agreement (see Protocol 22.4).

    Subdivision B.1: Shares of corporations are often divided into "classes" with different classes perhaps having different voting rights. For a hypothetical illustration, see the following footnote;36 see also Protocol 20.6 (board of directors definition).

20.39.2. How can voting-power rights arise?

The rights referred to in § 20.39.1 above can arise:

  1. by ownership of shares or comparable interests;
  2. by contract, for example, a voting trust or voting agreement; and/or
  3. by a provision in the articles of incorporation or equivalent document in the relevant jurisdiction, for example a certificate of formation.
Note

Subdivision 1: Ownership of voting shares (or of comparable interests in non-corporate organizations) is perhaps the most common way of holding voting power.

20.39.3. What about non-corporation organizations?

This Agreement will apply in similar fashion to organizations of any other type (including without limitation not-for-profit organizations).

20.40. Willful Definition

20.40.1. Applicability if agreed to

When agreed to, this Protocol will apply in any case where the Con­tract uses the term willful concerning action or conduct — for example, a /willful act or willful action or willful conduct or willful misconduct or willful neglect.

Note

When a contract contains a limitation of a party's liability, the limitation often includes a "carve-out" to the effect that liability is not limited if the party is guilty of "willful misconduct."

{{{Similarly, indemnification provisions such as Protocol 14.3 often exclude indemnity coverage for the same.

20.40.2. Definition

The term "willful" (or its variant spelling wilful) refers to action or conduct ("Action") where all of the following are true:

  1. the Action would be tortious, and/or criminal, if someone (an "Actor") were to take the Action outside the context of a contract;
  2. at the relevant time, the Actor knew, or should have known, of tortious- and/or criminal nature of the Action; and
  3. the Actor took (or continued) the Action either intentionally or recklessly (concerning the latter, see Protocol 20.31).
Note

This Definition draws on New York law,37 as well as various definitions in contracts that I've reviewed over the years. For other judicial definitions, see the following footnote:38

20.40.3. Would intentional breach be "willful"?

For emphasis: If the criterial of this Protocol are not met, it is not "willful" for a party to intentionally not perform one or more of its obligations under the Con­tract.

Note

This is a guardrail clause.

21. Litigation, arbitration, & other dispute provisions

21.1. Arbitration Protocol

None of the Options below will apply unless the Con­tract clearly adopts the specific Option.

21.1.1. Mandatory arbitration

  1. When this Protocol is agreed to, each party must use binding arbitration, as set forth in this Protocol (or as otherwise stated in the Con­tract), to resolve any dispute that relates in any way to the Con­tract.
  2. For this purpose, the term "the Arbitration" refers to an arbitration under the Con­tract.
Note

Caution: A "one-way" arbitration provision might be held unenforceable and even unconscionable. Example: A company's arbitration agreement with its employees was unconscionable because it required arbitration of the type of claims that the employee was likely to bring, while allowing the company to sue in court over many types of claim that the company was likely to bring. See Silva v. Cross Country Healthcare, Inc., No. B337435, slip op. at 21-22 (Cal. App. Jun. 13, 2025) (affirming denial of employer’s motion to compel arbitration).

21.1.2. Arbitration of all claims and defenses

Arbitration under this Protocol is required no matter what the underlying legal- and/or equitable claims or defenses might be in the dispute in question — for example, for claims and defenses that are based in contract, tort, unjust enrichment, fraud, fraudulent inducement to enter into the Con­tract, etc.

21.1.3. Arbitration of statutory- and constitutional claims

Arbitration under this Protocol is required even for those disputes in which one or more claims and/or defenses arises under a statute and/or constitutional provision.

Note

In the U.S., arbitration can be required for statutory- and constitutional claims — if the contract is sufficiently specific. See, e.g., 14 Penn Plaza LLC v. Pyett, 556 U.S. 249 (2009) (yes), distinguished by Ibarra v. UPS, 695 F.3d 354, 356 (5th Cir. 2012) (no).

21.1.4. Certain non-parties bound, too

This Protocol binds each party that signs the Con­tract or is otherwise bound by law.

Note

Concerning "is otherwise bound by law," see the discussion (with numerous case examples) at 21.1.33.18.

21.1.5. Option to litigate small claims instead

  1. Option: If the claim in question is a "small claim," THEN: Instead of arbitrating the claim, a party A can, for a limited time go to a small-claims court when that would be allowed by applicable law in the absence of an arbitration agreement.
  2. Limits: A may do so only in a small-claims court — no matter what the court is called in the relevant law — and only in accordance with:
    1. the restrictions in this Protocol; and
    2. any other relevant provisions in the Con­tract, for example a forum-selection provision.
  3. Waiver: A will WAIVE its right to take a case to small-claims court (and so A will not try to do so), if either of the following is true:
    1. A itself asked for the claim to be arbitrated; or
    2. in an arbitration requested by B, A participated in any way other seeking to dismiss or stay the arbitration proceedings.
  4. Court decision: Neither party will ask the arbitrator to decide — and the arbitrator has no power to decide — whether the case may be taken to small-claims court; that will be for a court to decide, even if the parties have otherwise delegated authority to the arbitrator, for example by agreeing to Option.
Note

().  Given the costs likely to be associated with arbitration, it makes sense to allow "small" claims to be heard in small-claims courts, created by state law, which are generally less costly than courts of "general jurisdiction," for example, by allowing a company to be represented by a non-lawyer.

Generally, small-claims courts are allowed by law to hear only cases where the amount in controversy is no more than a specified "jurisdictional limit"; at this writing, the limit is $10,000 in New York and California and $20,000 in Texas.

Subdivision 3: It'd be unfair for one party, after participating in arbitration, to do an Emily Litella and say, "Never mind!" forcing the other party to shift gears to working on a small-claims lawsuit instead — likely with duplicated effort.

Subdivision 4 — no power: See 21.1.33.15. Arguably, an arbitrator shouldn't be the one to determine whether a small-claims election is valid — that's because the arbitrator would likely have a financial interest in keeping the case in arbitration.

21.1.6. Required: Notice of proceedings — in English

  1. This section will apply if a party:
    1. initiates an arbitration against one or more other parties; and/or
    2. initiates court proceedings, relating to such an arbitration, that could bind any such other party.
  2. The initiating party must arrange for each such other party to immediately be given a reasonably-detailed notice of the initiated action — this notice must be written:
    1. in English; and/or
    2. in another language that can be read by most of that other party's senior management and other relevant employees.
Note

This language requirement seeks to avoid a possibility analogous to one that actually arose — and caused costly problems for — an American retailer in an arbitration with a Chinese supplier in CEEG (10th Cir. 2010):

  • The American retailer missed (what an American court found to be) a crucial deadline in a payment-dispute arbitration with a Chinese manufacturer. Why? Because the Chinese manufacturer's notice of the demand for arbitration had been in Chinese — even though the parties' agreement and their previous dealings had all been in English.
  • The Chinese manufacturer won the arbitration and sought to enforce the arbitration award in a Colorado court.

The American retailer caught a break: The Colorado court refused to confirm the resulting arbitration award — even though normally the court likely would have done so as a matter of routine — on grounds that the Chinese-language notice of the arbitration was not reasonably calculated to apprise the retailer of the arbitration proceedings; an appellate court affirmed. See CEEG (Shanghai) Solar Science & Tech. Co. v. Lumos LLC, 829 F.3d 1201 (10th Cir. 2016), affirming No. 14-cv-03118 (D. Colo. May 29, 2015).

21.1.7. Rules and procedural law for U.S. cases: AAA and California

The Arbitration will be governed by the rules and law below for cases seated in any jurisdiction subject to United States law ("U.S. cases"), as follows:

  1. the Commercial Arbitration Rules of the American Arbitration Association ("AAA");
  2. the arbitration (procedural) law of California; and
  3. the Federal Arbitration Act where applicable by law, but solely for any necessary gap-filling.
Note

().  The "seat" of the arbitration: See 21.1.32.5.

The Commercial Arbitration Rules of the American Arbitration Association are a typical "default" standard in the U.S.; the AAA also has: • rules for expedited cases; • rules for appeals of arbitrator awards to an appellate panel of arbitrators; and • special rules for consumer arbitrations.

For consumer arbitration, the AAA has a special set of rules — but those rules require the parties' arbitration agreement to comply (or be modified to comply) with the AAA's due-process standards, failing which the AAA can decline to accept the arbitration and either party can go to court. Example: A company found itself in court, instead of in arbitration, when the company rejected the AAA's request that the company modify its consumer arbitration agreement to remove a damages limitation. The AAA thereupon declined to accept the case, as provided in the AAA's relevant rules — which left the consumer-plaintiff free to pursue litigation in court. See Hernandez v. MicroBilt Corp., 88 F.4th 215 (3d Cir. 2023) (affirming denial of motion to compel arbitration).

The JAMS Streamlined Arbitration Rules have been praised by some arbitrators as effective; JAMS also has a set of international arbitration rules.

The International Institute for Conflict Prevention and Resolution (CPR) rules are favored by some.

For a brief comparison of various rules, see Anderson (IPDraughts.wordpress.com 2012).

For a more-detailed comparison of arbitration rules in the U.S. (AAA, JAMS, and CPR), see Kramer (ArbitrationNation.com 2013).

California law: See 21.1.26.

21.1.8. Rules and procedural law for non-U.S. cases: ICDR and England

The Arbitration will be governed by the rules and law below for cases seated in any jurisdiction not subject to United States law, as follows:

  1. the arbitration rules of the International Centre for Dispute Resolution ("ICDR," the international division of the AAA); and
  2. English arbitration (procedural) law.
Note

().  The "seat" of the arbitration: See 21.1.32.5.

Different rules arbitration rules are often used in non-U.S. cases. See, for example:

•  The International Arbitration Rules of the International Centre for Dispute Resolution ("ICDR," the international division of the AAA) are said to be based on the UNCITRAL Rules (mentioned below) but with administration features included. See generally Guzman & Kelleher (2014).

•  The LCIA Arbitration Rules of the London Court of International Arbitration (LCIA) are popular in international arbitrations.

•  The ICC arbitration rules of the International Chamber of Commerce (ICC) are believed to be among the most popular world-wide, in part because the arbitration award prepared by the Arbitral Tribunal will be scrutinized, before being released to the parties, by the ICC's International Court of Arbitration. Others, though, believe that these putative ICC benefits must be weighed against the likely cost of an ICC arbitration. See, e.g., Latham & Watkins, Guide to International Arbitration, ch. IV.

•  The UNCITRAL arbitration rules don't provide for administration of the arbitration; to some drafters, this is a serious deficiency, for reasons discussed in the notes at § 21.1.10.

•  The World Intellectual Property Organization (WIPO) has published arbitration rules and expedited arbitration rules.

•  CIETAC rules of the China International Economic and Trade Arbitration Commission

•  HKIAC rules of the Hong Kong International Arbitration Centre

•  SIAC rules of the Singapore International Arbitration Centre

•  For international arbitration, see Gans and Billing (CorporateCounsel.com), with a chart — possibly outdated — of selected key aspects of different rules.

(Hat tip: Arbitrator Kiran Gore for the China- and Singapore links)

Subdivision 2: English procedural law is very-commonly used for transnational arbitrations.

Fun fact: According to one Second-Circuit panel, it'd supposedly be unusual, indeed "exceedingly rare," for an arbitration agreement to designate an arbitration procedural law that was different from that of the arbitration venue. That, though, might well strike some experienced arbitrators as contrary to what they've seen in practice — for example, English arbitral law is routinely agreed to for international arbitrations even when the arbitration proceedings are to be conducted elsewhere. Molecular Dynamics, Ltd. v. Spectrum Dynamics Med. Ltd., 143 F.4th 70, 83 n.10 (2d Cir. 2025) (affirming dismissal of petition to enforce arbitration award; arbitration agreement's choice of enforcement forum doesn't confer subject-matter jurisdiction).

21.1.9. Choice of rules, not forum

For emphasis: The parties' agreement to arbitration rules is a choice of rules, not of forum. This means, for example, that arbitration would still be required even if the organization promulgating those rules were to decline to participate in the Arbitration.

Note

This seeks to avoid having the arbitration agreement thrown out entirely if (for example) the agreed rules require administration by a particular institution but that institution declines to serve.

21.1.10. Administrator: AAA or ICDR

  1. The Arbitration is to be administered by:
    1. the American Arbitration Association ("AAA"), if the case is seated in any geographic location that is subject to U.S. law; or
    2. the International Centre for Dispute Resolution ("ICDR," the international division of the AAA) otherwise.
  2. The arbitrator is to serve as "backup" administrator if, for any reason, the agreed administrator declines to administer the Arbitration; whenever doing so, the arbitrator will act:
    1. as stated in the arbitration rules; and
    2. for situations not covered by those rules, in accordance with the arbitrator's sound discretion, in (generally) the way judges administer lawsuits.
Note

().  Subdivision 1 — "seat" of the arbitration: See 21.1.32.5.

Arbitration requires a number of administrative chores such as scheduling of calls and hearings, etc. It's usually more cost-effective for an institution to handle such administrative chores than it would be for the arbitrator to charge for his- or her time to do so.

Experienced arbitrator Gary McGowan — previously a founding name partner of leading national litigation boutique Susman & McGowan, now Susman Godfrey LLP — points out some other advantages of using an arbitration administrator such as the AAA:

  • "AAA's vetting process formalizes disclosures of potential conflicts/biases and thus minimizes [sic; reduces] the likelihood of a flawed proceeding."
  • In addition, a party might have a complaint about an arbitrator, for example a perception that the arbitrator is biased toward another party. It will usually be better if the complaining party can take its complaint to an arbitral institution, than to risk angering the arbitrator by raising the complaint with the arbitrator himself.
  • And "a competent administrator will goad an arbitrator who is not moving the proceeding apace." Gary McGowan, 12 Ways to Achieve Efficiency and Speed in Arbitration, Corporate Counsel (Apr. 22, 2013) (now paywalled).

    And according to Sherby (2010), "the conventional wisdom is that it is easier to enforce an award given by an arbitral institution than one given by an ad hoc arbitrator" — this makes a certain sense, because, in the eyes of a court, the involvement of a known-quantity arbitral institution would likely give an arbitration proceeding and award a bit of extra legitimacy.

    In the U.S., a commonly-used administrator is the American Arbitration Association ("AAA") or its international division, the International Centre for Dispute Resolution; other arbitration-administration organizations are also available. (Disclosure: For some ten years I served on the AAA's panel of commercial arbitrators.)

    A number of arbitration-administration organizations are available, such as: • JAMS; • the International Institute for Conflict Prevention and Resolution (CPR); • the London Court of International Arbitration (LCIA); • the International Court of Arbitration of the International Chamber of Commerce.

    For international arbitrations, according to a 2021 survey by Queen Mary University of London and the U.S.-based international law firm White & Case LLP (2021), the five most preferred arbitral institutions are the ICC; Singapore International Arbitration Centre (SIAC); Hong Kong International Arbitration Centre (HKIAC); LCIA; and China International Economic and Trade Arbitration Commission (CIETAC).

21.1.11. One arbitrator

If the parties do not agree otherwise, a single arbitrator is to preside over the Arbitration unless the agreed arbitration rules:

  1. call for a different number of arbitrators, or
  2. allow for non-neutral arbitrators.
Note

().  Three arbitrators are likely to be more than three times as expensive as just one. That's because three arbitrators will necessarily spend (billable) time conferring with each other, reviewing drafts of written decisions, etc.

But: For some cases, the reassurance of having three arbitrators, reducing the chances of one arbitrator "going rogue," could be worth the added expense. That could be especially true in view of the limited appealability of arbitration awards (discussed at 21.1.33.15).

Under typical arbitration rules:

–  A multi-member arbitration panel would designate, by majority vote, one of their number as the panel chair.

(Majority vote is typical of arbitration rules for panel decisions; see, e.g., AAA Rule R-46 and LCIA Rule 26.3.)

–  The chair would have the power to resolve any procedural disputes without consulting the full panel — absent objection by any party or by any other member of the panel.

(Allowing the chair of the arbitration panel to decide procedural disputes is based on concepts from AAA Rule R-46 (which are a bit convoluted); for that reason, some parties might prefer to follow LCIA Rule 5.6 (which calls for the chair to be appointed by the LCIA).)

–  The panel would make all other panel decisions by majority vote.

21.1.12. Arbitrator neutrality

Each arbitrator is to be independent and impartial.

Note

Arbitration rules usually call for a single arbitrator to be independent and impartial, e.g., under the AAA's Commercial Rule R-19.

Sometimes, parties agree that each party will appoint one non-neutral arbitrator and a third arbitrator will be neutral; see, e.g., AAA Rule R-19(b).

Rarely — if the parties have so agreed — a single, non-neutral arbitrator will decide the case, as happens in some professional sports collective-bargaining agreements that provide for a senior authority figure in one of the parties to serve as arbitrator; such an arbitrator arguably would not be neutral.

Example: In the Deflategate case, which centered on legendary (U.S.) National Football League quarterback Tom Brady: The court rejected Brady's objection to having NFL commissioner Roger Goodell sit as the arbitrator in Brady's challenge of his four-game suspension. The court held, in essence, that the players' union and the team owners had known full well the consequences of their arbitration agreement and that they could have bargained to do things differently. See NFL Mgmt. Council v. NFL Players Ass'n, 820 F.3d 527, 548 (2d Cir. 2016) (reversing district court judgment and remanding with instructions to confirm award confirming disciplinary action against Brady).

Example: More than two decades early, New York's highest court held that under state law, the state's public policy doesn't prohibit an alternative dispute resolution ("ADR") provision that authorizes an employee of a party to a contract dispute — in that case, an employee of a particular city agency — to make "conclusive, final, and binding decisions on all questions arising under the contract," even when the employee was personally involved in the dispute:

Westinghouse chose, with its business eyes open, to accept the terms, specifications and risk of the bid contract, including the ADR clause. …

Without doubt, Westinghouse understood the implications of the ADR clause prior to undertaking its business and legal risks under the whole of the multimillion dollar agreement. To allow it, after the fact, to secure the assistance and power of the courts to relieve it of a particular procedural provision, while retaining the benefits of the rest of the publicly bid public works contract, is not compelled by our precedents and would have destabilizing commercial law consequences. Westinghouse Elec. Corp. v. N.Y. City Transit Auth., 82 N.Y.2d 47, 50, 54, 623 N.E.2d 531, 603 N.Y.S.2d 404 (1993) (on certification from Second Circuit), subsequent proceeding, 14 F.3d 818 (2d Cir. 1994) (affirming denial of Westinghouse's contract claim against city).

Counterexample: The Second Circuit court sustained a ruling that three former NFL coaches were entitled to litigate their statutory racial-discrimination claims against the New York Giants in a class-action lawsuit instead of arbitration, because the NFL's contractual dispute resolution procedure — giving unilateral authority to the league commissioner — was "arbitration in name only." Flores v. NY Giants, Inc., 150 F.4th 172, 182 (2d Cir. 2025) (affirming denial of motion to compel arbitration). The court distinguished the Deflategate ruling because "[t]here, we conducted a very limited review of an arbitration award under the Labor Management Relations Act, not the FAA. The rights at issue [there] were contractual, not federal statutory rights, and they were subject to arbitration according to the terms of a collectively bargained for arbitration agreement." (Cleaned up.) Id. at 181 n.72 (cleaned up).

Counterexample: In a professional-boxing case, the First Circuit held that, under the applicable Puerto Rican law, the arbitration provision in the World Boxing Organization's agreement with boxers was unconscionable because it gave the WBO the power to select the arbitrator. The appeals court remanded the case for consideration of a savings clause that might allow arbitration to go forward anyway with an arbitrator appointed by the district court. See Trout v. Organización Mundial de Boxeo, Inc., 965 F.3d 71, 82 (1st Cir. 2020), on remand, 662 F. Supp. 3d 158 (D.P.R. 2023) (severing appointment provision and directing parties to submit claim to arbitration).

Counterexample: The Seventh Circuit invalidated, as unconscionable, of an arbitration provision, in an employment agreement between a drinking establishment and an employee, because (among other infirmities), the arbitration provision gave the bar the right to choose the arbitrator. On appeal, with the bar's agreement but over the employee's objection, the appeals court directed the trial court to choose an arbitrator, as provided by the Federal Arbitration Act, and to order the parties to arbitrate. See Campbell v. Keagle Inc., 27 F.4th 584 (7th Cir. 2022) (vacating and remanding refusal to compel arbitration).

21.1.13. Arbitrator appointment: Per the agreed rules

Each arbitrator is to be appointed in accordance with the agreed arbitration rules — or, as a backup method, as provided by law.

Note

().  In the typical selection process, the arbitration administrator (e.g., the AAA) presents the parties with a list of candidates and for parties to strike unacceptable candidates; this is seen in, e.g., AAA Commercial Rule R-13.

Absent a backup method for selecting an arbitrator, a court might refuse to compel arbitration if the agreed selection method failed — at this writing, that's the subject of a circuit split among U.S. federal courts. See Frazier v. Western Union Co., 377 F. Supp. 3d 1248, 1265-66 (D. Colo. 2019) (citing cases).

Arbitrators would generally have the qualifications specified in the arbitration rules; if an arbitration administrator is used (e.g., the AAA), the administrator will typically maintain a pre-screened roster of neutral arbitrators.

But the Con­tract could specify particular qualifications, and even different arbitrator qualifications for different types of dispute. Example: In one Tenth Circuit case, the parties' arbitration agreement specified different arbitrator qualifications for energy-related disputes versus accounting disputes. See BP America Product. v. Chesapeake Explor. (10th Cir. 2014) (affirming a variety of orders by the district court).

21.1.14. English language

Unless all involved agree otherwise, all written and oral communications relating to the Arbitration are to be in English. This includes, for example, all proceedings, notices, and arbitrator decisions relating to the Arbitration.

Note

Pro tip: For the arbitration language, consider the country where an arbitration award might need to be enforced. That's because, under Article IV.2 of the 1958 New York Convention, a sworn translation of the award might be needed, which could result in extra expense and delay.

21.1.15. No jury

In case of doubt: By agreeing to arbitration, each party WAIVES any right that the party might otherwise have to a jury trial for any matter being addressed in the Arbitration.

Note

().  The word "WAIVE" is in bold-faced all-caps for conspicuousness (see 8.1) as "cheap insurance" in case there's a conspicuousness requirement for jury waivers that would apply to arbitration agreements.

Background: Juries aren't used in arbitration. And outside the arbitration context, advance waivers of jury trials are very likely to be held unenforceable in California, Georgia, and North Carolina, as explained at 21.16.4. Consequently, there have been cases where a party, no longer willing to arbitrate, has tried to set aside a pre-dispute arbitration agreement (e.g., in an employment agreement) on grounds that the arbitration agreement was unenforceable..

But where the Federal Arbitration Act applied, the Act would arguably preempt any state-law prohibitions of advance jury waivers. This thinking comes from the Supreme Court's Concepcion (2011) opinion, where the Court held that federal law preempted a California supreme court decision that declared arbitration provisions in certain cases to be unenforceable if they did not allow for classwide arbitration. See AT&T Mobility LLC v. Concepcion, 563 U.S. 333, 131 S. Ct. 1740 (2011).

Example: The Nevada supreme court held that the Federal Arbitration Act did indeed preempt a state statute imposing certain requirements on arbitration agreements. See MMAWC, LLC v. Zion Wood Obi Wan Trust, 135 Nev. Adv. Op. 38, 448 P.3d 568 (2019).

Counterexample: New Jersey's supreme court held that an arbitration provision was unenforceable because the provision did not expressly waive jury trial; to the surprise of some observers (including me), the U.S. Supreme Court declined to hear the losing side's appeal. See Atalese v. US Legal Serv. Group, LLP, 219 N.J. 430 99 A.3d 306 (2014).

Tangentially: In an Uber-related case, a Pennsylvania appeals court ruled — perhaps with an eye to just such a federal-preemption argument — that state law required all jury-trial waivers (not just those in arbitration agreements) to be supported by a showing that the waiving party had "unambiguously manifested [its] assent" to the waiver. Consequently, said the court, an arbitration provision in "browse-wrap" terms of service, used by ride-sharing service Uber, was unenforceable. See Chilutti v. Uber Techs., Inc., 2023 PA Super 126, 300 A.3d 430.

21.1.16. Limits on arbitrator's power

Unless the parties to the Arbitration clearly agree otherwise: In addition to any other limits stated in this Protocol (or elsewhere in the Con­tract), the arbitrator has no power to do any of the following things:

  1. grant relief clearly inconsistent with the Con­tract or with applicable non-arbitration law; nor
  2. render an award that would be subject to being reversed or vacated, on one or more grounds, if rendered as a judgment by a United States district court following a trial to the court without a jury; nor
  3. act as amiable compositeur or ex aequo et bono.
Note

().  There's a perception in some quarters that arbitrators can run amok, i.e., "go rogue." Part of this comes from the traditional doctrine that arbitrators are allowed to act as "amiable compositeur" and "ex aequo et bono," referring to the arbitrator's deciding the case "according to the equitable and good" — as perceived by the arbitrator, of course.

Example: Some observers believed that the arbitrators went too far in a software-copyright dispute between competitors IBM and Fujitsu — in that case, the arbitrators ultimately ordered IBM to provide its operating-system source code and other secret information to Fujitsu; and ordered Fujitsu to pay significant money to IBM for the privilege. See David E. Sanger, Fight Ends For I.B.M. And Fujitsu, NY Times, Sept. 16, 1987. For more background on that IBM-Fujitsu dispute, see a student note: Anita Stork, The Use of Arbitration in Copyright Disputes: IBM v. Fujitsu, 3 Berkeley Tech. L.J. 241 (1988). (Ms. Stork is now a prominent antitrust litigator.)

And worse, under U.S. law, the opportunities to appeal an adverse arbitration award could be very limited unless the agreement to arbitration limits the arbitrator's power (see the notes at 21.1.26 for additional discussion of that point).

DCT comment: From what I've seen, most arbitrators seem to stick to the law and the contract. Not least, that's because — wanting to be hired again and to get referrals from satisfied counsel — arbitrators can be reluctant to anger either side's counsel, which could happe if they render an award that doesn't make sense to the losing counsel. See Thomas J. Stipanowich, Arbitration: The New Litigation, 2010 Ill. L. Rev. 1.

Pro tip: Instead of cabining the arbitrator's power, consider expressly allowing the arbitrator to act as amiable compositeur and ex aequo et bono. (But many parties won't want to agree to that in advance before they know who the arbitrator will be, so this section contemplates delaying that decision.)

Non-jury trials: See generally, e.g., Harold P Weinberger, Norman Christopher Simon, and Samantha Vanessa Ettari, Bench Trials (Federal) (AmericanBar.org 2021).

Amiable compositeur or ex aequo et bono: See generally, e.g., Alexander J. Belohlavek, Application of Law in Arbitration, Ex Aequo et Bono and Amiable Compositeur (2013).

21.1.17. Examples of unauthorized arbitrator actions

For emphasis: The arbitrator has no power to do any of the following things (without limitation):

  1. disregard any provision in the contract or the law that limits any party's liability, such as a damages cap or an exclusion of certain remedies; and/or
  2. disregard an agreed deadline for a party to commence a claim in court or elsewhere — this includes (but is not limited to) an agreement to a shortened statutory deadline, known as a "limitation period."
Note

Absent specific language preserving the statute of limitations (see generally 21.17), an arbitrator might be able to ignore the statute and allow a party to proceed with an expired claim — and there might be little or nothing that the opposing party could do about it. See Kramer (2016) and the commentary at 21.1.26 concerning an enhanced right of appeal.

21.1.18. Forum(s) for enforcement of arbitration awards

Once the arbitrator has issued any award in the Arbitration, any party can go to court to confirm the award, and to have the resulting court judgment (or order) judicially enforced against another party, in any court that has "jurisdiction" (i.e., the legal authority to hear the case) over the subject matter and the other party.

Note

().  By law, arbitration awards "are not self-enforcing and must be given force and effect by being converted to judicial orders by courts; these orders can confirm and/or vacate the award, either in whole or in part." D.H. Blair & Co., Inc. v. Gottdiener, 462 F.3d 95, 104 (2d Cir. 2006) (cleaned up).

To illustrate, here's a hypothetical situation:

  • "Alice" agrees to arbitrate a dispute with "Bob" over whether Alice owes Bob money.
  • The arbitrator decides in Bob's favor and rules that Alice must pay Bob, let's say, $1,000.
  • Alice refuses to pay Bob as directed by the arbitrator's award.

Now, Bob can't just stroll into Alice's bank and ask a teller to hand him $1,000 from Alice's account: Bob must instead go to:

  • a court in a jurisdiction where Alice can lawfully be sued anyway (i.e., Alice is "subject to personal jurisdiction" there); OR
  • a court in a jurisdiction where Alice has agreed that she can be sued and that otherwise has "subject-matter jurisdiction" to hear Bob's case.

Whichever court that is: Bob will ask the judge (with no jury) to "confirm" the award under the Federal Arbitration Act (in Title 9 of the U.S. Code) or, in international cases, by treaty (the New York Convention).

Alice, on the other hand, will likely ask the judge to vacate the award.

Assuming Bob succeeds in getting the judge to confirm the award and enter judgment: Bob can have that judgment "executed" — that is, then Bob can get law-enforcement authorities to confiscate enough of Alice's money and other assets to satisfy the judgment.

Some arbitration provisions address which court(s) will have such power, perhaps with language such as the following:

Any arbitration award under the Con­tract may be confirmed and enforced [only?] in a court having jurisdiction in [fill in location].

This is a type of forum-selection provision; for more on that subject generally, see Protocol 21.12.

Caution: State law might provide that agreement to arbitrate in the state constitutes consent to jurisdiction — or even exclusive jurisdiction — in the courts of the state to enter judgment on the arbitration award; moreover, such a statute might purport to confer exclusive jurisdiction in the courts of that state. See, e.g., Cal. Code of Civ. P. § 1293 (consent to jurisdiction); Conn. Gen. Stat. § 52-407zz(b); Nev. Rev. Stat. § 38.244 (exclusive juriscdiction).

Note: A federal district court can confirm an arbitration award only if — on the face of the confirmation petition itself — the court has an independent basis for subject-matter jurisdiction such as diversity of the parties; it's not enough that the Federal Arbitration Act applies. See Badgerow v. Walters, 596 U.S. 1, 142 S. Ct. 1310 (2022) (FAA doesn't independently confer subject-matter jurisdiction).

For that reason, if diversity is indeed the only basis for subject-matter jurisdiction, then a federal court has no power to confirm an arbitration award of zero dollars (i.e., a "defense verdict" award) because the required amount in controversy for diversity jurisdiction won't be met. See Tesla Motors, Inc. v. Balan, 134 F.4th 558 (9th Cir. 2025) (vacating order confirming "defense verdict" award in favor of Tesla and remanding with instructions to dismiss).

Relatedly: In 2025 the Second Circuit held that an arbitration agreement's choice of enforcement forum doesn't confer subject-matter jurisdiction for federal district court to vacate an award. See Molecular Dynamics, Ltd. v. Spectrum Dynamics Med. Ltd., 143 F.4th 70 No. 24-2209, slip op. at 31-35 (2d Cir. Jul. 2, 2025) (affirming dismissal of petition to vacate arbitration award).

21.1.19. Consequences of unsuccessful challenge

  1. This section applies apply if any of the following occurs:
    1. A takes B to court to enforce a final arbitration award because B did not comply with the award, or
    2. in court, B unsuccessfully challenges one or more of: (a) the award, or (b) the parties' arbitration agreement.
  2. In any of those situations, B is to pay A's attorney fees) incurred in connection with those court proceedings, including (without limitation) attorney fees for any related appeals.
Note

().  There's case law to the effect that, under the "American Rule" for attorney fees, a party that wins an arbitration case will be denied attorney fees for the court enforcement proceedings, even if entitled to recover fees for the arbitration proceeding itself. See, e.g., Zurich American Insurance Co. v. Team Tankers A.S., 811 F.3d 584 (2d Cir. 2016).

Caution: In some circumstances, a provision allowing attorney fees along these lines might be found unconscionable. See Ramirez v. Charter Comms., Inc., 16 Cal. 5th 478, 495-507 (2024), on remand, 108 Cal. App. 5th 1297 (2025) (determining that unconscionable provisions in arbitration agreement were not severable and consequently affirming trial court's refusal to compel arbitration). (Hat tip: Hunter Pyle.)

21.1.20. Termination not precluded

In case of doubt: The parties' agreement to arbitrate does not limit — but neither does it expand — any right that a party would otherwise have to terminate:

  1. the Con­tract, and/or
  2. a transaction or relationship governed by the Con­tract.
Note

This seeks to disavow one court's holding that "the presence of an arbitrability clause [in employment agreement] … implies for-cause termination protections, notwithstanding a state law at-will doctrine to the contrary." Warfield v. ICON Advisers, Inc., 26 F.4th 666, 670 (4th Cir. 2022) (citing cases; emphasis edited).

21.1.21. Government action not precluded

For emphasis: The parties' agreement to arbitrate does not mean that a party may not bring a matter to the attention of government authorities; neither does it mean that such authorities would not be be able to act in the matter.

Note

This language draws on ideas from section 12.3 of a New York Times terms of service document dated May 10, 2024, as well as precedent from the Supreme Court. See EEOC v. Waffle House, Inc., 534 U.S. 279 (2002) (arbitration agreement doesn't bar EEOC from acting) and Gilmer v. Interstate/Johnson Lane Corp., 500 U.S. 20 (1991) (arbitration agreement doesn't bar filing a charge with the EEOC).

21.1.22. Survival of arbitration requirements

If the Con­tract expires or is otherwise terminated, for any reason, THEN: The parties' agreement to arbitrate will continue in effect for any and all disputes that accrued before the termination or expiration became effective.

Note

Depending on the wording of the arbitration requirement, there's case law going both ways about whether the arbitration requirement would survive if the contract containing the requirement were to expire or be terminated. See, e.g., Vazquez v. SaniSure, Inc., 101 Cal. App. 5th 139 (2024) (employee's quitting her job had the effect of revoking arbitration provision in employment agreement).

21.1.23. Option: Class-Action Arbitration Prohibition

  1. When this Option is agreed to, the parties DO NOT AGREE to arbitrate any case in which a party does, or attempts to do, any of the following:
    1. consolidate any claim with claim(s) of any other party;
    2. purport to act as a representative of other claimants; and/or
    3. purport to act as a private attorney general, whether under a statute allowing such action, sometimes referred to as "PAGA claims," or otherwise.
  2. The arbitrator has no power to decide any dispute about whether either party is attempting to act contrary to this Option; any dispute in that regard is to be decided by a court that has jurisdiction.
  3. The parties' agreement to this Option is "material" — without this Option, one or both parties would not have agreed to arbitration at all.
Note

().  Especially in consumer- and employment cases, counsel for claimants in arbitration sometimes try to consolidate claims and handle them as they would a class-action lawsuit. That can make economic sense for all concerned — but it can be tricky in view of Supreme Court holdings.

Specifically: In the Supreme Court's 2010 Stolt-Nielsen opinion by Justice Alito, the Court held that class arbitration is not permitted under the Federal Arbitration Act unless the parties expressly agreed to it, because "class-action arbitration changes the nature of arbitration to such a degree that it cannot be presumed the parties consented to it by simply agreeing to submit their disputes to an arbitrator." The Court went on to catalog ways in which class arbitration differs from the traditional, one-on-one variety. Stolt-Nielsen SA v. AnimalFeeds Int'l Corp., 559 U.S. 662, 130 S. Ct. 1758, 1775-76 (2010) (Alito, J.).

Subdivision 2: It's very likely better for a judge, not an arbitrator, to decide whether class arbitration is or isn't allowed by an arbitration agreement. That's because, if the arbitrator gets to decide whether the parties agreed to class-action arbitration, then the arbitrator might well have a personal incentive to err on the side of "finding" that class arbitration was indeed agreed to — and there'd likely be little recourse in court to try to get such a finding reversed.

But under the (U.S.) Federal Arbitration Act, one of the very-few grounds on which a federal court may vacate an award in arbitration is that "the arbitrators exceeded their powers …." under 9 U.S.C. § 10(a)(4). (See also Option 21.1.26, providing for enhanced appeal of an arbitration award.)

Unfortunately, arbitrators have been known to "find" an agreement to class arbitration even though the contract said nothing of the sort — I've personally seen that happen, albeit not in any case I was involved in  — yet still have the "finding" be upheld by a reviewing court, as though Stolt-Nielsen had never been decided.

In all likelihood, such an arbitrator genuinely wants to help the parties resolve all of the pending claims quickly and fairly. But you can see the obvious conflict of interest here: By "finding" agreement to class arbitration, the arbitrator will get more work, for a longer time, and bill more fees, than for doing just one, single-party arbitration, and so the arbitrator has an economic incentive to make such a "finding."

And under the Supreme Court's Oxford Health Plans decision, if an arbitration agreement delegates to the arbitrator the decision whether class arbitration is allowed, then the arbitrator's decision about class-action arbitrability can't be overruled by a court except on extremely-limited grounds.

Example: An arbitration provision in an employment agreement — drafted by the employer's counsel, of course — authorized arbitration of "all remedies which might be available in court." An arbitrator interpreted this language as implicitly allowing class arbitration, largely on grounds that "[t]he breadth of claims the agreement covered, compared to the relatively few it exempted, suggested to the arbitrator that the parties made a conscious choice not to exclude class arbitration." Upholding a lower court's confirmation of the award, the Fifth Circuit held that "whatever the merits of the arbitrator's analysis here, it is enough that he focused on the arbitration clause's text, analyzing (whether correctly or not makes no difference) the scope of both what it barred from court and what it sent to arbitration." Sun Coast Resources, Inc. v. Conrad, 956 F.3d 335, 337-38 (5th Cir. 2020) (cleaned up, emphasis added).

So: Instead of leaving the class-arbitration decision power open to debate, this Option expressly takes that power out of the arbitrator's hands — in part to perhaps provide grounds on which a court could vacate an arbitrator's decision.

Caution: This Option's prohibition of class-action arbitration might be unenforceable if used to try to prevent class-action relief authorized by statute, e.g., under the Employee Retirement Income Security Act (ERISA). See, e.g., Williams v. Shapiro, No. 24-11192, part III.B, slip op. at 13-17 (11th Cir. Dec. 15, 2025) (affirming denial of defendants' motion to compel arbitration of ERISA claims in lieu of class-action litigation; citing cases from other circuits).

For more discussion and pro tips about class arbitration, see the additional notes beginning at 21.1.33.9.

21.1.24. Option: Delegation of (Most) Arbitrability Decisions

  1. When this Option is agreed to: Except as clearly provided otherwise in the Con­tract, the arbitrator decides all disputes about arbitrability, including for example the following:
    1. whether the parties' agreement to arbitrate was duly entered into but is nevertheless unenforceable;
    2. whether a particular dispute comes within the scope of the arbitration agreement; and
    3. whether the arbitration agreement conflicts with a party's non-waivable legal rights.
  2. If a question arises whether a party seeking arbitration has waived arbitration: That question may be decided by the arbitrator or by a court of competition jurisdiction that is timely presented with the question.
  3. But: A court of competent jurisdiction has the sole power to decide any dispute about:
    1. whether the parties agreed to arbitrate in the first place; and/or
    2. whether this section is a valid delegation of authority to the arbitrator.
Note

().  For the arbitrator to have the power to decide arbitrability disputes, the arbitration agreement itself must clearly and unmistakably delegate those specific decisions to the arbitrator, said the Supreme Court. When that happens, the arbitrator will decide the arbitrability question — and a court will likely defer to the arbitrator's decision on that point. See First Options of Chicago, Inc. v. Kaplan, 514 U.S. 938, 942 (1995) (reversing court of appeals and holding that agreement in question did not give arbitrator power to determine arbitrability); Berkeley Cty. School Dist. v. HUB Int'l Ltd., 130 F.4th 396, 403 (4th Cir. 2025) (reversing district court and remanding with instructions to compel arbitration).

Many arbitration rules include a delegation provision: if an arbitration agreement adopts such rules, then the delegation agreement might follow automatically. See, e.g., (what is now) Rule R-7(a) of the American Arbitration Association's Commercial Arbitration Rules, a previous version of which were the agreed rules in Henry Schein, Inc. v. Archer & White Sales, Inc., 586 U.S. 63 (2019), on remand, 935 F.3d 274, 283 (5th Cir. 2019) (holding that "the parties have not clearly and unmistakably delegated the question of arbitrability to an arbitrator"), cert. dismissed as improvidently granted, 592 U.S. 168 (2021); Wu v. Uber Technologies, Inc., 43 N.Y.3d 288, 260 N.E.3d 1060 (2024) (affirming denial of motion to stay arbitration and affirmance of order compelling arbitration) (citing Henry Schein, Inc.).

On the other hand: If there are two arguably-conflicting agreements — one that requires all controversies to be heard in a particular court, the other that contains an arbitration provision — then a court will determine which agreement controls on that point. This came up in a case where sweepstakes rules contained an exclusive forum-selection clause while the associated online terms of service required arbitration — this illustrates the importance of careful drafting. See Coinbase, Inc. v. Suski, 602 U. S. 143 (2024) (affirming 9th Circuit).

But: If a party claims that it never agreed to arbitration in the first place, then the arbitration clause's adoption of particular arbitration rules won't be enough to delegate the arbitrability dispute. See VIP, Inc. v. KYB Corp., 951 F.3d 377, 385-86 (6th Cir. 2020) (affirming denial of motion to compel arbitration).

And if the arbitration agreement itself refers only to specified disputes and not to all disputes, or if that agreement includes carve-outs, then a court might find that the agreement does not "clearly and unmistakably" delegate arbitrability decisions — even when the agreed arbitration rules might suggest otherwise. See Aramark Services Inc. Group Health Plan v. Aetna Life Ins. Co., No. 24-40323, slip op. at 8-13 (5th Cir. 2025) (affirming denial of motion to compel arbitration); DDK Hotels, LLC, v. Williams-Sonoma, Inc., 6 F.4th 308, 319-21 (2d Cir. 2021) (same).

A party's too-extensive participation in court proceedings could result in a waiver of its right to demand arbitration. This happened in a case between the founder of the Papa John's pizza chain and the chain's former public-relations in connection with the founder's departure after making highly-publicized comments. (Unusually, the Sixth Circuit framed the issue in terms of the PR firm's having "defaulted on its right to arbitrate disputes ….") See Schnatter v. 247 Group, LLC, 155 F.4th 543, 555 (6th Cir. 2025) (affirming denial of defendant's motion to compel arbitration); see also id. at 551 n.3 (reframing the waiver issue as one of default) (citations omitted).

Subdivision 2 — caution: A court might hold that the delegation agreement was unconscionable. See Heckman v. Live Nation Entertainment, Inc., 120 F.4th 670 (9th Cir. 2024) (affirming holding that arbitration agreement was unconscionable).

21.1.25. Option: Nondelegation of Arbitrability Authority

When this Option is agreed to, any disagreement whether or not a particular dispute must be arbitrated is decided by a court of competent jurisdiction and not by the arbitral tribunal, even if the applicable arbitration rules state otherwise.

Note

Obviously this is the opposite of Option 21.1.24.

21.1.26. Option: Enhanced Right of Appeal

  1. When this Option is agreed to, any party may challenge an arbitration award in court as provided in California's arbitration law; this will be true:
    1. even if the Con­tract specifies a different choice of law for the Con­tract generally and/or for one or more other issues; and
    2. even if the Federal Arbitration Act would otherwise limit such challenges.
  2. If a court, properly hearing a challenge to the Arbitration, holds that this right of enhanced appeal is invalid or otherwise unenforceable — in a final judgment with no possibility of further appeal — THEN: Option 21.1.27 (jettison of arbitration agreement) will automatically apply.
Note

().  Subdivision 1: Drafters can keep in mind a possibility for enhanced appellate review, even if federal law wouldn't allow it: In part IV of its Hall Street decision, the Supreme Court expressly left open the possibility that enhanced review might be available under some other authority, such as state law or (in the case of court-annexed arbitrations) a court's inherent power to manage its docket.

And some states do allow parties also to agree on expanded appeal rights in arbitration; this section takes advantage of that possibility by allowing reversal or vacating of an arbitrator's action on the same basis as for a non-jury trial ("bench trial") in the U.S.

Example: In Cable Connection (Cal. 2008), California's supreme court ruled that, in proceedings under the arbitration acts of their respective states, the parties were free to agree to enhanced judicial review; years later, this holding allowed the NBA's Golden State Warriors team to appeal (unsuccessfully) an arbitration ruling in favor of the Oakland-Alameda County Coliseum Authority. See Cable Connection, Inc. v. DirecTV, Inc., 44 Cal.4th 1334, 82 Cal. Rptr. 3d 229, 190 P.3d 586 (2008); Samuelian v. Life Gens. Healthcare, LLC, No. G061911 (Cal. App. 2024); Oakland-Alameda Cty. Coliseum Auth. v. Golden State Warriors, LLC, 53 Cal. App. 5th 807, 267 Cal. Rptr. 3d 799 (2020), pet. denied (affirming confirmation of arbitration award against the Warriors); see also the 2024 amendment to Cal. Code Civ. P. § 1283, signed by Gov. Newsom. California's statute also has a separate section 1297.11 et seq. concerning international arbitrations. (In a non-California case, of course, the parties' agreement to California arbitration law might not be effective to allow compulsory discovery from non-party witnesses.)

Example: Texas's arbitration law allows a similarly-expansive right of appeal if agreed by the parties. See Tex. Civ. Prac. & Rem. Code §§ 171.050 and 171.051, cited in Nafta Traders, Inc. v. Quinn, 339 S.W.3d 84 (Tex. 2011).

Counterexample: Tennessee's supreme court held that an arbitration agreement's expansion of the scope of judicial review was invalid and thus the entire arbitration agreement was rescinded. (That case was the inspiration for Option 21.1.27.) See Pugh's Lawn Landscape Co. v. Jaycon Dev. Corp., 320 S.W.3d 252 (Tenn. 2010) (vacating judgment confirming arbitrator's award), citing Arnold v. Morgan Keegan & Co., 914 S.W.2d 445 (Tenn. 1996) (state arbitration statute did not allow for expanded appeal by agreement).

Subdivision 2: "[A] court properly hearing a challenge to the Arbitration": This is an informal version of the legalese requirement that the court in question must have "jurisdiction" to hear the challenge.

21.1.27. Option: Jettison of Arbitration

  1. When this Option is agreed to, the parties follow it if both of the following are true:
    1. the parties' agreement to arbitrate specifies one or more provisions as "jettison triggers" (or words to that effect);
    2. one or more such jettison-trigger provisions is finally held, by a court or other body of competent jurisdiction, to be unenforceable, with no further possibility of appeal; and
    3. the parties do not agree otherwise — for example, by agreeing to a settlement of their dispute.
  2. A may jettison, that is, rescind, the parties' arbitration agreement by giving B clear notice to that effect no later than five business days after the final holding described above.
  3. If A does timely jettison arbitration as provided in this Option, then:
    1. Whatever actions the arbitrator previously took, in the way of a partial- or complete "final award," are automatically "vacated," that is, set aside and of no effect; and
    2. The status of any interim actions of the arbitrator is to be determined by the court if not otherwise agreed.
  4. If P does jettison arbitration under this Option, then either A or B may bring an action to litigate, in a court having jurisdiction, one or more of the claim(s) that were being arbitrated, but only if both of the following are true:
    1. at the time of the original demand for arbitration, the deadline had not yet expired, under an applicable statute of limitations, for the filing of a court action presenting the substance of those claim(s); and
    2. the claim(s) are asserted in that court no later than ten business days after the final holding described above — in effect, the statute of limitations will hve been tolled until then.
Note

This Op-In is motivated by a Tennessee case in which the state supreme court held that the parties' agreement to expanded judicial review was invalid, and the parties presumably would not have agreed to arbitration without the expanded judicial review, so (according to the court) the arbitration agreement had to be rescinded. See Pugh's Lawn Landscape Co. v. Jaycon Dev. Corp., 320 S.W.3d 252 (Tenn. 2010) (vacating judgment confirming arbitrator's award), citing Arnold v. Morgan Keegan & Co., 914 S.W.2d 445 (Tenn. 1996) (state arbitration statute did not allow for expanded appeal by agreement).

21.1.28. Option: Severability of Arbitration Provisions

If one or more portions of the parties' agreement to arbitrate are held to be unenforceable, by a tribunal of competent jurisdiction, THEN: Those particular portion(s) are automatically severed from the agreement to arbitrate.

Note

The severability of arbitration provisions has been an issue in several cases. See, e.g., Williams v. Shapiro, No. 24-11192, part III.B, slip op. at 17 (11th Cir. Dec. 15, 2025) (affirming denial of defendants' motion to compel arbitration of ERISA claims in lieu of class-action litigation; express terms of arbitration provision precluded severance of unenforceable class-action prohibition); Trout v. Organización Mundial de Boxeo, Inc., 662 F. Supp. 3d 158 (D.P.R. 2023) (compelling arbitration after severing arbitrator-selection provision), on remand from 965 F.3d 71, 82 (1st Cir. 2020); Ramirez v. Charter Comms., Inc., 16 Cal. 5th 478, 495-507 (2024), on remand, 108 Cal. App. 5th 1297 (2025) (determining that unconscionable provisions in arbitration agreement were not severable and consequently affirming trial court's refusal to compel arbitration); Westmoreland v. Kindercare Education LLC, 90 Cal. App. 5th 967, 972, 976, 307 Cal. Rptr. 3d 554 (2023) (affirming denial of renewed petition to compel arbitration: by its terms, arbitration provision was invalid because arbitration agreement itself precluded severance of PAGA waiver that was held to be unenforceable).

21.1.29. Option: No Punitive Damages in Arbitration

The arbitrator has no power to award — and no party will seek — punitive damages, exemplary damages, multiple (e.g., treble) damages, or similar relief.

Note

().  This Option addresses the fear among some lawyers that an arbitrator might go overboard in awarding "punies," given the relatively-few opportunities there'd be to appeal such an award (see Option 21.1.26). For similar language, see Wells Fargo Bank, N.A. v. WMR e-PIN, LLC, 653 F.3d 702 (8th Cir. 2011) (affirming confirmation of award, albeit for procedural reasons).

This prohibition is phrased without the qualifier, "to the maximum extent permitted by law" — otherwise, the arbitrator might be able to award punitive damages anyway. See Stark v. Sandberg, Phoenix & von Gontard, P.C., 381 F.3d 793, 800 (8th Cir. 2004).

Pro tip: Another possibility could be to allow punitive damages but limit them to some agreed multiple of the contract price or of actual damages. See generally, e.g., Gino J. Rossini, Constitutional Limits of Punitive Damages Awards (2023).

21.1.30. Option: Punitive Damages in Arbitration

The arbitrator has the power to award punitive damages to the extent not inconsistent with the arbitration rules and applicable law.

Note

See the notes at 21.1.29.

21.1.31. Option: Limited Punitive Sanctions in Arbitration

The arbitrator has no power to award — and no party will seek — punitive sanctions against a party, in respect of an issue (or multiple issues) being arbitrated, in the form of: (1) preclusion of otherwise-admissible evidence; nor (2) entry of judgment concerning the issue.

Note

No power: See 21.1.33.15.

Note

().  Absent this restriction, "American Arbitration Association Rule 47(a) provides that an 'arbitrator may grant any remedy or relief that the arbitrator deems just and equitable and within the scope of the agreement of the parties.' That broad authority includes the power to impose sanctions." Telecom Business Solution , LLC v. Terra Towers Corp., No. 23-7312(L), slip op. (2d Cir. Apr. 23, 2025) (nonprecedential summary order affirming confirmation of award; citation omitted).

This Option addresses a concern raised in a case where an arbitrator, in effect, (1) struck a respondent's pleadings as a sanction for fabrication of evidence, and (2) awarded the claimant more than $600 million; the award was upheld by Minnesota's supreme court. See Seagate Technology, LLC v. Western Digital Corp., 854 N.W.2d 750, 760 n.7 (Minn. 2014) (with extensive case citations).

21.1.32. Additional notes: Pro tips for drafters

21.1.32.1. Arbitration Clause (condensed version)

Here's a short-form arbitration provision — it'd be slightly harder to read but easier to copy and paste into a draft contract; for commentary, see the counterpart sections of the long-form Protocol 21.1.

(a) Binding arbitration in the English language, before a single neutral arbitrator, is to be used for all disputes relating in any way to the Con­tract. (b) This arbitration requirement specifically includes, but is not limited to, claims of fraudulent inducement and those relating to statutory- and/or constitutional rights. (c) The arbitration is to be conducted in accordance with: (1) for U.S.-seated cases: (i) California procedural law; (ii) the Federal Arbitration Act for any necessary gap-filling; and (iii) the Commercial Arbitration Rules of the American Arbitration Association ("AAA"); and (2) for other cases: English procedural law and the arbitration rules of the International Centre for Dispute Resolution.

21.1.32.2. Maybe don't require a separate signature for arbitration?

Unless specifically required by law, it's not a great idea to include separate lines for a separate signature (or initials) for an arbitration agreement. That's because it's too easy for a party to forget — or intentionally fail — to sign or initial there. That could lead to a dispute about whether the party in fact agreed to the arbitration provision — which in turn could lead to costly litigation, perhaps with unpredictable outcomes. See, e.g., Mertens v. Benelux Corp., No. 24-50954 (5th Cir. 2025) (denying motion to compel arbitration: employer didn't sign standalone arbitration agreement, so class-action lawsuit could proceed); Recinos v. SBM Site Services, LLC, No. A151253, slip op. (Cal. App. Aug. 10, 2018) (denying motion to compel arbitration because employees had not signed separate signature line for arbitration provision) (citing cases). But see Anderson v. Pitney Bowes, Inc., No. C-04-4808, slip op. at 5-6 & n.7 (N.D. Cal. May 4, 2005) (holding that arbitrator, not court, would determine whether arbitration requirement was valid because arbitration provision called for arbitrator to decide disputes about arbitrability) (see the discussion of such "delegation" clauses at 21.1.24 and in the commentary to the "non-delegation" option at 21.1.25).

21.1.32.3. Caution: Be explicit if ruling out arbitration

The body of an oil-and-gas lease included an arbitration provision that was seemingly negated by a provision in an exhibit to the lease, which stated:

If any of the following provisions conflict with or are inconsistent with the printed provisions or terms of this Lease, the following provisions shall control. * * *

22.  All Disputes Decided in Harrison County Courts — All disputes the parties are unable to resolve between themselves shall be subject to a civil lawsuit. The Courts in Harrison County, Ohio (Common Pleas and County) shall have exclusive jurisdiction over all disputes. Neither party shall be able to either file or remove a case to Federal Court.

(Emphasis added.) Denham v. Encino Energy, LLC, 2025 Ohio 1585 ¶ 5 (reversing and remanding denial of motion to compel arbitration).

A trial court denied a motion to compel arbitration, reasoning that the exhibit language meant what it said. But the state supreme court disagreed, asserting that "[a]n arbitration clause and a forum selection clause are not necessarily mutually exclusive because arbitration and litigation are not mutually exclusive." (Emphasis mine.) The court distinguished another case in which an addendum had explicitly ruled out arbitration.

(DCT note: This strikes me as legislating from the bench by simply reading the "all disputes" language completely out of the addendum provision.)

21.1.32.4. Local law might restrict arbitration locations

Example: In Texas, if a contract relates broadly to real property located in Texas and is entered into after September 1, 2025, then (with certain exceptions) an arbitration provision that requires arbitration in another state is void as against public policy — ditto for forum-selection clauses requiring litigation in the courts of another state, and governing-law provisions that choose the law of another state. See Tex. Bus. & Comm. Code ch. 272, amended by H.B. 2960.

(Under the former version of the statute, a state court of appeals held that if the forum-selection clause included a waiver of voidability, then that waiver would be enforced; three years later, the Legislature responded by changing the wording to preclude that result.) The previous version of the statute was cited in In re MVP Terminalling, LLC, No. 14-21-00399-CV, slip op. (Tex. App—Houston [14th Distr.] Aug. 23, 2022) (conditionally granting mandamus proceeding; by entering into subcontract, subcontractor had contractually waived its statutory right to void forum-selection clause).

21.1.32.5. What's the "seat" of the arbitration?

The "seat" of an arbitration is the geographic location where legally the arbitration is deemed to take place (even though many arbitrations are done by videoconference or, if in person, in other convenient locations). The seat of an arbitration can have significant procedural implications, such as in determining the arbitral law.

The seat of an arbitration is often agreed upon by the parties. But it might not make sense to lock down the arbitration seat in advance, because that's a decision that might be better negotiated in the actual event.

(If disputing parties can't agree on an arbitration location, the arbitration rules might well specify how the location is to be determined.)

According to a 2021 survey by Queen Mary University of London and the U.S.-based international law firm White & Case LLP, "[t]he five most preferred seats for arbitration are London, Singapore, Hong Kong, Paris and Geneva."

Three Hong Kong-based lawyers assert that that their city is well-suited as a seat for arbitration with companies in China (PRC) because:

  • Uniquely among Chinese cities, Hong Kong retains its common-law system;
  • Judicial filing fees don't increase with the amount of the claim; and
  • "Given its status as a Special Administrative Region of the People's Republic of China and as a separate jurisdiction from Mainland China, Hong Kong is in the unique position of being the only jurisdiction outside of Mainland China to have a number of mutual arrangements with Mainland China for judicial assistance covering various aspects of civil and commercial disputes." Sherlin Tung, Alex Ye, and Gary Leung, Why Hong Kong remains an ideal place to resolve your commercial disputes (WithersWorldwide.com 2024). See also Guide to Leading Arbitral Seats and Institutions (KLGates.com 2012).

Caution: Before agreeing to arbitrate in Hong Kong, parties and counsel would want to carefully consider the then-current geopolitical situation and assess the potential "pros and cons" of physically going to Hong Kong, not just from a business perspective but also from a personal standpoint.

21.1.33. Additional notes: Pro tips for company lawyers

21.1.33.1. Arbitration is increasingly B2C, not B2B

Binding arbitration started out as a procedure to resolve disputes in business-to-business ("B2B") contracts. But arbitration requirements are increasingly found in business-to-consumer ("B2C") contracts — sometimes with terms that decidedly advantage the business.

Moreover (as discussed at 21.1.33.3), nowadays many drafters of B2B contracts seem to want to avoid arbitration because it's said to offer "the worst of both worlds," with most of the expense of litigation but without broad discovery rights and few avenues to appeal an adverse outcome.

21.1.33.2. Caution: Be able to "prove up" agreement to arbitration

Suppose we have the following situation:

  • A vendor purportedly sends an email to a customer with terms and conditions for a sale.
  • The vendor's T&Cs include, among other things, a jury-trial waiver and arbitration clause.
  • The customer never responds to the email — but does proceed with the purchase.

Would the customer be bound by the jury waiver and arbitration clause as part of a unilateral contract? Example: In a New Jersey case, the state supreme court ruled that the answer could be yes — but the vendor (a cell-phone service provider) hadn't sufficiently proved that in fact it had sent the email to the customer. See Fazio v. Altice USA, 261 N.J. 90, 337 A.3d 304 (2025) (reversing trial court's order compelling arbitration and remanding case for trial).

Relatedly: A consumer contracted to buy electricity from a provider:

  • About three weeks later, the provider sent the consumer a package containing a form with new dispute resolution terms — including an arbitration provision.
  • The consumer never signed the form.
  • Two years later, the consumer sued the provider for breach and deceptive business practices.
  • The trial court denied the provider's motion to compel arbitration, on grounds that the consumer hadn't had notice of the arbitration provision.

The Second Circuit affirmed, on grounds that "[(i)] the provider] failed to present the arbitration provision in a clear and conspicuous way, and [(ii)] a reasonable person would not have believed that submitting payments constituted assent." (Emphasis added.) Sudakow v. CleanChoice Energy, Inc., 153 F.4th 280, 282 (2d Cir. 2025) (affirming denial of motion to compel arbitration) (emphasis added); see also Cruz v. Tapestry, Inc., 113 Cal. App.5th 943 (2025) (same day, same result, decided on similar grounds).

21.1.33.3. Is arbitration really cheaper than a lawsuit?

Some companies prefer arbitration over litigation because — when properly managed — arbitration can cost less money and take less time than court proceedings.

(For arbitration-management suggestions, see my arbitration streamlining article — I sometimes serve as an arbitrator in tech-contract and IP disputes — as well as my preferred arbitration procedures.)

Moreover, for transnational arbitrations: Because of the international treaty on arbitration (the New York Convention), if a case is arbitrated in Country A, it's often easier for the winning party to get a court in Country B to enforce the arbitrator's award (e.g., by ordering seizure of the losing party's assets located in Country B) than it would be if the case had been litigated in Country A.

But: On the other hand, some parties regard arbitration as the worst of both worlds. Noted academic authority Tom Stipanowich has suggested that —

  • Arbitration has been "captured" by litigation counsel who, for reasons of their own, prefer to agree with their counterparts to run arbitration proceedings in the same expensive- and time-consuming ways as they're familiar with in court (that tracks with my own experience as an arbitrator); and
  • Arbitrators — mindful of getting future business and referrals from litigation counsel — can be reluctant to anger counsel in a case by overruling their procedural agreements, even though doing so would help to keep costs down in the case. See Thomas J. Stipanowich, Arbitration: The New Litigation, 2010 Ill. L. Rev. 1.
21.1.33.4. Companies: Pay your arbitration fees!

If a company demands arbitration but then fails to pay related fees (e.g., from the American Arbitration Association or other institution), that could result in the company being forced back into court for litigation — and possibly class-action litigation.

Example: A worker sued her former employer on several grounds. The company moved to compel arbitration. The parties initially agreed to a stay of the lawsuit pending arbitration. Later, the company was six days late in paying a third invoice for arbitration fees. This apparently was because the company's counsel had been caught up in an unspecified "natural disaster" that forced her and her family to evacuate their home. With a distinct lack of sympathy, the worker successfully moved to withdraw from arbitration and proceed with the lawsuit, as authorized by section 1281.98 of the state's code of civil procedure, so the company ended up in litigation after all. See Colon-Perez v. Security Indus. Specialists, Inc., 108 Cal. App. 5th 403, 409-10, 413, 421 & n.12, 329 Cal. Rptr. 3d 342 (2025) (affirming trial court's actions).

BUT: Just a few months later, in a 5-4 decision — based on harmonizing with nonforfeiture principles so as to avoid "equal footing" preemption by the Federal Arbitration Act — California's supreme court expressly disapproved of the earlier case and similar cases, on grounds that in enacting section 1281.98, "the Legislature sought to deter companies and employers from engaging in strategic nonpayment of arbitration fees; we find no indication that it intended to strip companies and employers of their contractual right to arbitration where nonpayment of fees results from a good faith mistake, inadvertence, or other excusable neglect." The supreme court remanded the case for determination whether an employer's failure to pay arbitration fees was excusable. Hohenshelt v. Superior Court, No. S284498, slip op. at 2 (Cal. Aug. 11, 2025) (emphasis in original).

Example: In a strange case (that your author is mulling over), seven ex-employees of Twitter (laid off in the wake of Elon Musk's acquisition of the company) petitioned to compel Twitter to pay the JAMS arbitration fees because JAMS refused to proceed without payment. In the Southern District of New York, Judge Rakoff granted the petition to compel arbitration, but the Second Circuit reversed and remanded. The appeals court strongly hinted that the petitioners should instead have either fronted the JAMS fees themselves — or asked JAMS to terminate the arbitration and then sue Twitter in court. See Frazier v. X Corp., No. 24-1948, slip op. at 4, 31 & n.10 (2d Cir. Sept. 2, 2025).

21.1.33.5. How much discovery is available in arbitration?

In U.S. litigation, parties' counsel get to take extensive "discovery" as a matter of right; typically, this takes the form of compulsory production of documents and compulsory depositions, i.e., witness interviews under oath.

But in arbitration, the applicable arbitration rules generally allow for very little such discovery, at least not without the arbitrator's approval.

One exception: California's arbitration law allows depositions and other discovery, including from third parties. See the 2024 amendment to Cal. Code Civ. P. § 1283, signed by Gov. Newsom; see generally, e.g., Barbara A. Reeves, Arbitration discovery rights in California: What you need to know (AdvocateMagazine.com 2023).

(In a non-California case, of course, the parties' agreement to California arbitration law might not be effective to allow compulsory discovery from non-party witnesses.)

Another: Texas's arbitration law likewise allows broad discovery rights. See Tex. Civ. Prac. & Rem. Code §§ 171.050 and 171.051.

(As a practical matter, parties' counsel very often agree to exchange discovery; this can run up the bills for arbitration to where the expense is comparable to litigation, as discussed at 21.1.33.3.)

21.1.33.6. Who could grant preliminary injunctive relief?

().  In an arbitration, each party would be free to ask a court (or other tribunal having jurisdiction) for preliminary injunctive relief; that would normally be true even if the arbitration rules allowed the arbitrator to grant preliminary relief.

If a party did ask for relief from a court, etc., that in itelf shouldn't be held to waive whatever right the party has to require arbitration of other matters in the case.

Caution: Drafters of arbitration provisions should be very careful about stating that a party is authorized to seek other forms of equitable relief from a court when the party would otherwise have to arbitrate its claims for such relief. Such other (unauthorized) forms of equitable remedies could include, e.g., specific performance, rescission, and disgorgement. Example: In a California case, a party was allowed to litigate its claims for those particular remedies, instead of arbitrating them, because of a similar carve-out in their arbitration agreement for "claims seeking injunctive or other equitable relief." Eminence Healthcare, Inc., v. Centuri Health Ventures, LLC, 74 Cal. App. 5th 869, 879-80 (Cal. App. 2022) (affirming denial of motion to compel arbitration).

Pro tip: If a party asks an arbitrator to grant preliminary injunctive relief, that party should consider also asking the arbitrator to specify that such a grant is intended to be a partial final award. Otherwise, even if enhanced appeal of an arbitration award were agreed to (see Option 21.1.26), a court might nevertheless dismiss an appeal of an arbitrator's preliminary injunction, on grounds that it was not an "award" and thus that the court did not have jurisdiction to review the injunction. See, e.g., Kirk v. Ratner, 74 Cal. App. 5th 1052 (2022) (dismissing appeal from trial court's dismissal of petition to vacate arbitrator's preliminary injunction).

21.1.33.7. Caution: Arbitrations might not be confidential

().  Confidentiality in arbitration won't necessarily be automatic. That's true even though a primary reason parties opt to arbitrate their disputes in the first place is often to try to avoid having their business affairs made public in court proceedings.

The agreed arbitration rules might independently require confidentiality, possibly in the arbitrator's discretion.

  • Example: Rule R-24(a) of the Commercial Arbitration Rules of the American Arbitration Association allows the arbitrator to impose secrecy requirements in connection with the pre-hearing exchange of confidential information and the admission of confidential evidence at the hearing.
  • Article 30 of the LCIA Arbitration rules of the London Court of International Arbitration automatically provide for secrecy of arbitration proceedings.

The arbitral law and/or the applicable substantive law might also require confidentiality, e.g., if personal health information or export-controlled information is involved. For example, apparently English arbitration law implies a duty of confidentiality in arbitration proceedings — and a failure to maintain confidentiality, where required, could result in the imposition of severe sanctions or the institution of legal proceedings against the discloser by other parties to the arbitration. See generally Chantal du Toit, Reform of the English Arbitration Act 1996: a nudge towards reversing the presumption of confidentiality (PracticalLaw.com 2017).

Caution: A court being asked to enforce an arbitration agreement might not honor even an agreed confidentiality requirement — that's because of the strong presumption of public access to court proceedings and documents filed or used in court. See, e.g., XPO Intermodal, Inc. v. American President Lines, Ltd., No. 17-2015, slip op. (D.D.C. Oct. 16, 2017) (denying motion to seal documents in action to confirm arbitration award, with leave to submit revised motion); Susquehanna Int'l Grp. Ltd. v. Hibernia Express (Ireland) Ltd., No. 21 Civ 207, slip op. (S.D.N.Y. Aug. 11, 2011) (granting with leave to submit revised motion).

Caution: Too-strict a confidentiality requirement in an arbitration agreement might cause enforceability problems for the arbitration agreement itself — especially in employment-related cases. See Davis v. O'Melveny & Myers, 485 F.3d 1066, 1078-79, 1084 (9th Cir. 2007) (reversing and remanding order that dismissed complaint and compelled arbitration); Brown v. TGS Mgmt. Co., LLC, 57 Cal. App. 5th 303, 317–20, 271 Cal. Rptr. 3d 303 (Cal. App. 2020) (reversing confirmation of arbitration award).

21.1.33.8. Can a party change its mind about arbitrating?

Sometimes a contract will include an agreement to arbitrate, but then when a dispute arises, one party will refuse to participate or will try to block arbitration. When that happens, the party that wants arbitration will usually go to court and seek an order compelling arbitration.

(This Protocol allows one, limited exception: For a limited time, either party may elect to take the dispute to a small-claims court in lieu of arbitrating.)

21.1.33.9. Precluding class arbitration — a costly mistake?

Option 21.1.23's prohibition of class arbitration could be disastrous financially if a company found itself having to pay arbitration fees for hundreds or even thousands of coordinated individual arbitration claims:

–  Suppose that an arbitrator determines that class arbitration between a company and its employees (or its customers, its "independent contractors," etc.) is not allowed.

–  Later, a court might find itself compelled to accept the arbitrator's determination, however that determination comes out (see 21.1.26).

–  This might mean that if the arbitrator decides against class arbitration, the company could find itself on the hook for millions of dollars in individual arbitration fees. Courts tend not to sympathize with companies that use class-arbitration waivers — making it costly for employees or customers to arbitrate individually — but that then try to get out of paying the required arbitration fees. Numerous cases — involving well-known companies such as Amazon, Twitter, and Uber — are cited in the following note (which is optional reading for students):

Note

Arbitration class-action fees cases — Amazon: see Sara Randazzo, Amazon Faced 75,000 Arbitration Demands. Now It Says: Fine, Sue Us (WSJ.com June 1, 2021). DoorDash: See Nicholas Iovino, DoorDash Ordered to Pay $9.5M to Arbitrate 5,000 Labor Disputes (CourthouseNews 2020). Postmates: Adams v. Postmates, Inc., 414 F. Supp. 3d 1246, 1251-52 & n.2 (N.D. Cal. 2019) (granting order compelling arbitration). Samsung: See Wallrich v. Samsung Elec. America, Inc., 106 F.4th 609, 619 (7th Cir. 2024) (reversing order compelling arbitration; plaintiff consumers had failed to adduce evidence, as opposed to mere allegations, that consumers had in fact agreed to arbitration). Twitter: See Daniel Wiessner, Twitter stalling hundreds of ex-workers' legal cases: lawsuit (reuters.com Jul. 3, 2023); Mike Masnick, Twitter’s Lawyers Admit They’re Overwhelmed As Nearly 2000 Laid Off Employees File Arbitration Claims (TechDirt.com Jun. 16, 2023); Reuters, Twitter's laid-off workers cannot pursue claims via class-action lawsuit, judge rules (reuters.com Jan. 17, 2023). Uber: Uber Tech., Inc. v. American Arbitration Assn., Inc., 204 AD 3d 506, 510, 167 N.Y.S.3d 66, 2022 NY Slip Op 02503 (N.Y. App. Div.) (affirming denial of Uber's motion to enjoin AAA from issuing any additional invoices and prohibit AAA from closing any open arbitrations due to Uber's refusal to pay AAA's invoice).

For a useful overview of mass-arbitration challenges for consumer-facing companies, see Allison Schoenthal, Jeffrey Simes, W. Kyle Tayman, and Matthew Wisnieff, Mass Arbitration: The Risk Lurking in Consumer Agreements (JDSupra.com 2025).

21.1.33.10. Can mass arbitrations be run effectively?

The American Arbitration Association has developed supplemental rules for mass arbitration, which "were developed specifically to streamline the administration of large volume filings involving the same or related party, parties, and party representatives" by following a "[t]echnology-focused approach to case management."

Likewise, the JAMS arbitration provider has rules for mass arbitration.

AT&T's October 2022 customer service agreement sets out a detailed procedure (in section 1.3.2.7) for "Administration of Coordinated Arbitrations." The linked customer service agreement is archived at https://perma.cc/DYC6-T9WM.

Example: Similarly, in 2023, genetic testing company 23andMe changed its terms of service to require customers to use a "mass arbitration" procedure, "after reports revealing that attackers accessed personal information of nearly 7 million people — half of the company’s user base — in an October hack." Pranav Dixit, 23andMe frantically changed its terms of service to prevent hacked customers from suing (engadget.com 2023), discussing the 23andme terms of service.

21.1.33.11. Allow opting out of a class-arbitration prohibition?

Some companies include opt-out provisions in their arbitration agreements, especially in employment agremeents and customer agreements.

  • Opting out of arbitration would preserve an employee's or customer's right to bring class-action litigation.
  • And many people might not actually bother to opt out: A Bloomingdale's employee failed to timely opt out of arbitration when given the chance; she was held to have waived her right to litigate in court. Johnmohammadi v. Bloomingdale's, Inc., 755 F.3d 1072, 1074 (9th Cir. 2014) (affirming grant of Bloomingdale's motion to compel arbitration of employee's claim and dismissal of her class-action suit).

But the opposite result occured in another case: Indiana's supreme court held that a credit union member's faiure to opt out and her subsequent inaction were not enough to constitute her acceptance of an arbitration agreement and class-action prohibition. See Land v. IU Credit Union, 218 N.E.3d 1282, 1290-91 (Ind. 2023) (affirming court of appeals's reversal of order compelling arbitration).

21.1.33.12. Or: Maybe just allow class arbitration?

At this writing, we don't really know which if any of the above "hybrid" approaches will be accepted by courts. As noted in a 2025 law-firm Web publication:

At least one court has tentatively blessed a variant of this approach, but in so doing, noted that if the process leads to undue delay in resolution of claims, it may ultimately be deemed unconscionable.

Whether these provisions will stand up in the end is undetermined, but regardless, they represent an imperfect solution, and may do little to avoid the enormous costs of ultimately resolving large numbers of individual arbitrations.

Christian Auty, Amy de La Lama, Merrit Jones, and Daniel Rockey, Is Your Company Vulnerable to a Mass Arbitration Attack? What It is and How to Prevent It (JDSupra.com 2024).

So: Some parties might want to allow class arbitration, perhaps using language such as the following:

Class arbitration: Class-, collective-, and private-attorney-general arbitration are permitted in accordance with the Supplementary Rules for Class Arbitrations of the American Arbitration Association.

Parties agreeing to class arbitration might also want to agree to an enhanced right of appeal, as stated in Option 21.1.26.

21.1.33.13. Tangential: Would a waiver of class actions in court be given effect?

Example: Citing decisions from several jurisdictions, a federal district court ruled that, in the absence of an arbitration agreement, a purported waiver of state-law class action remedies was contrary to the state's public policy and so was unenforceable. Metcalfe v. Grieco Hyundai LLC, No. 22-378, slip op. (D.R.I. Oct. 3, 2023) (denying motion to strike class-action allegations or to dismiss) (citing cases).

Counterexample: New Jersey's supreme court, also citing other states' decisions, ruled just the opposite, namely that class-action waivers in consumer contracts were not per se contrary to public policy, but they could be unenforceable if found to be unconscionable. Pace v. Hamilton Cove, 258 N.J. 82, 317A.3d 477, 487-89 (2024). No. A-4, 088302, slip op. at part III.B.2 (N.J. Jul. 10, 2024) (reversing and remanding appeals court; tenants' class-action waiver in apartment lease agreements was enforceable).

Counterexample: California's supreme court stated (in what appears to have been a nonbinding dictum) that "the law in California is that class action waivers in consumer contracts of adhesion are unenforceable, whether the consumer is being asked to waive the right to class action litigation or the right to classwide arbitration." Discover Bank v. Superior Ct., 36 Cal. 4th 148, 113 P.3d 1100 (2005) (reversing court of appeal).

21.1.33.14. Other SCOTUS class-arbitration cases

In addition to Stolt-Nielsen, the Supreme Court has handed down other rulings about class- and collection-action arbitration, such as the following:

–  Lamps Plus: "[T]he FAA similarly bars an order requiring class arbitration when an agreement is not silent, but rather 'ambiguous' about the availability of such arbitration. … Courts may not infer from an ambiguous agreement that parties have consented to arbitrate on a classwide basis. The doctrine of contra proferentem cannot substitute for the requisite affirmative contractual basis for concluding that the parties agreed to class arbitration." Lamps Plus, Inc. v. Varela, 139 S. Ct. 1407, 1419 (2019) (reversing and remanding Ninth Circuit's affirmance of order compelling class-wide arbitration; cleaned up); see also, e.g., Davis v. Nordstrom, Inc., 755 F.3d 1089, 1092-94 (9th Cir. 2014) (reversing denial of Nordstrom's motion to compel employee to arbitrate her claims individually and not as a class).

–  Italian Colors Restaurant: The Act preempts state law barring enforcement of a class-arbitration waiver — thus, if you agree to a contractual waiver of class arbitration, you're likely to be stuck with the waiver, even if your cost of individually arbitrating a federal statutory claim would exceed the amount you might recover if you succeed with your claim. See American Express Co. v. Italian Colors Rest., 570 U.S. 228 (2013) (reversing Second Circuit).

21.1.33.15. "No power": Very-limited appeals under federal arbitration law

In the U.S., the Federal Arbitration Act generally will apply in cases involving or affecting interstate commerce "absent clear and unambiguous contractual language to the contrary" in which the contract "expressly references state arbitration law." BNSF R.R. Co. v. Alston Transp., Inc., 777 F.3d 785, 790-92 (5th Cir. 2015) (vacating district court's vacatur of arbitration award and remanding with instructions to reinstate award; citations omitted).

As the First Circuit observed:

While parties to an arbitration contract may contemplate enforcement under state statutory or common law rather than the FAA, we have emphasized that FAA displacement can occur only if the parties have so agreed explicitly. As such, the mere inclusion of a generic choice-of-law clause within the arbitration agreement is not sufficient to support a finding that contracting parties intended to opt out of the FAA's default regime for vacatur of arbitral awards. Ribadeneira v. New Balance Athletics, Inc., 65 F.4th 1, 13 (1st Cir. 2023) (reversing vacating of arbitration awards; cleaned up), cited in Durant v. Alerion Yachts, LLC, No. 24-12569, slip op. (D. Mass. May 9, 2025) (granting motion to confirm arbitration award but rejecting movant's request to modify award). Hat tip: Mark Kantor.

Under the Act, arbitration awards are largely unappealable in federal court except on very limited grounds — including that "the arbitrators exceeded their powers." 9 U.S.C. § 10(a)(4).

(That's the motivation for the language, "the arbitrator will have no power …" in various places of this Protocol.)

In Hall Street (U.S. 2008), the Supreme Court held that — when the sole authority for an arbitration proceeding is the Federal Arbitration Act — courts may not entertain a challenge to the award except on the limited, misconduct-based grounds provided in section 10 of the Act. See Hall Street Associates, L.L.C. v. Mattel, Inc., 552 U.S. 576, 128 S. Ct. 1396 (2008).

Later, in Oxford Health Plans (U.S. 2013), the Court explained:

Because the parties bargained for the arbitrator's construction of their agreement, an arbitral decision even arguably construing or applying the contract must stand, regardless of a court's view of its (de)merits.

Only if the arbitrator acts outside the scope of his contractually delegated authority — issuing an award that simply reflects his own notions of economic justice rather than drawing its essence from the contract — may a court overturn his determination.

So the sole question for us is whether the arbitrator (even arguably) interpreted the parties' contract, not whether he got its meaning right or wrong. Oxford Health Plans LLC v. Sutter, 569 U.S. 564, 133 S. Ct. 2064 (2013) (affirming denial of motion to vacate arbitrator's approval of class action; reformatted). For other cases, see the footnote.39

The Court went on:

Nothing we say in this opinion should be taken to reflect any agreement with the arbitrator's contract interpretation, or any quarrel with Oxford's contrary reading. All we say is that convincing a court of an arbitrator's error—even his grave error—is not enough.

So long as the arbitrator was "arguably construing" the contract — which this one was — a court may not correct his mistakes under § 10(a)(4). The potential for those mistakes is the price of agreeing to arbitration.

As we have held before, we hold again: It is the arbitrator's construction of the contract which was bargained for; and so far as the arbitrator's decision concerns construction of the contract, the courts have no business overruling him because their interpretation of the contract is different from his. The arbitrator's construction holds, however good, bad, or ugly.

In sum, Oxford chose arbitration, and it must now live with that choice. Oxford agreed with Sutter that an arbitrator should determine what their contract meant, including whether its terms approved class arbitration. The arbitrator did what the parties requested: He provided an interpretation of the contract resolving that disputed issue.

His interpretation went against Oxford, maybe mistakenly so. But still, Oxford does not get to rerun the matter in a court. Under § 10(a)(4), the question for a judge is not whether the arbitrator construed the parties' contract correctly, but whether he construed it at all. Because he did, and therefore did not "exceed his powers," we cannot give Oxford the relief it wants. We accordingly affirm the judgment of the Court of Appeals. Id., 133 S. Ct. at 2070-71 (cleaned up, paragraphing edited).

More than a quarter century earlier, though, the Court held that a court can set aside an arbitration award that violates an explicit public policy — but the Seventh Circuit later noted that the public policy "must be well defined and dominant, and is to be ascertained by reference to the laws and legal precedents and not from general considerations of supposed public interests." See W.R. Grace & Co. v. Rubber Workers, 461 U.S. 757 (1983); Zimmer Biomet Holdings, Inc. v. Insall, 108 F.4th 512, 517 (7th Cir. 2024) (affirming confirmation of arbitration award of post-patent-expiration royaties) (cleaned up).

And under California law, as summarized by a state appeals court in TGS Mgmt. (Cal. App. 2020), an arbitrator will exceed her powers — and thus have her award subject to being vacated — if the award "violates a party's unwaivable statutory rights or that contravenes an explicit legislative expression of public policy." Brown v. TGS Mgmt. Co., LLC, 57 Cal. App. 5th 313, 271 Cal. Rptr. 3d 303 (Cal. App. 2020) (reversing confirmation of arbitration award) (citations omitted).

But: Are there limits to what an arbitrator can do in "interpreting" the contract? Example: On that issue turned the outcome in a case where "the My Pillow guy," Mike Lindell, offered a $5 million reward to anyone who could definitively prove that the 2020 presidential election hadn't been interfered with by Chinese hackers:

  • A three-arbitrator panel unanimously found that the reward's claimant, Zeidman, had proved his case and was entitled to the money under the published challenge rules; a federal district court confirmed the panel's award.
  • But the Eighth Circuit held that the arbitrators' interpretation of a crucial term in the contest rules had strayed into rewriting the contract — thus exceeding their powers. The court reversed the confirmation of the award and remanded to the district court. See Zeidman v. Lindell Management LLC, 145 F.4th 820 (8th Cir. 2025).

At this writing, the claimant's petition for certioari review, seeking to overturn the Eighth Circuit's decision, is pending at the Supreme Court.

DCT comment: Purely from a workload-management perspective, it seems quite short-sighted for courts to prohibit enhanced appeals of arbitration awards by agreement. That's because:

  • parties are always free not to agree to arbitration — which means that their disputes likely would end up in court; and
  • surely, a busy trial judge would prefer to deal with a relatively simple case where some other "judge" — i.e., the arbitrator — had already done the work of managing the pre-trial proceedings; hearing witness testimony; reviewing exhibits and other evidence; and writing an award, so that the trial judge need only sit as a reviewing court.
21.1.33.16. Can parties agree to no arbitration appeals?

Tangentially: Some arbitration agreements take the opposite tack, stating that the arbitrator's decision will be final, binding, and not reviewable at all by a court. But U.S. courts probably won't go along with that: Courts have noted that "[s]ince federal courts are not rubber stamps, parties may not, by private agreement, relieve them of their obligation to review arbitration awards for compliance with § 10(a) [of the FAA]." MVL Group (2d Cir. 2003); accord, Wal-Mart (9th Cir. 2013). Hoeft v. MVL Group, Inc., 343 F.3d 57, 64 (2d Cir. 2003) (reversing, for unrelated reasons, vacatur of arbitration award); accord, In re Wal-Mart Wage & Hour Employment Practices Litigation, 737 F.3d 1262, 1267-68 (9th Cir. 2013).

On slightly-different facts, however, both the Fourth and Tenth Circuits held that arbitration provision can properly waive appellate review of a trial court's confirmation of an award. See Beckley Oncology (4th Cir. 2021); MACTEC (10th Cir. 2005). See Beckley Oncology Assoc., Inc., v. Abumasmah, 993 F.3d 261, 264-65 (4th Cir. 2021), citing MACTEC, Inc. v. Gorelick, 427 F.3d 821, 830 (10th Cir. 2005).

21.1.33.17. Arbitration clauses in online agreements

Online terms of service often require arbitration of disputes; courts have generally enforced such requirements. See, e.g., Granados v. LendingTree, LLC, No. 3:22-CV-00504 (W.D.N.C.), slip op., part II.1.a (Feb. 1, 2023) (magistrate judge recommendation to grant motion to compel arbitration), adopted, slip op. (Mar. 28, 2023).

But: A court held that an arbitration agreement in Uber's "browse-wrap" terms of service was not enforceable because it did not "unambiguously manifest" the user's assent to waive the constitutional right of trial by jury. See Chilutti v. Uber Techs., Inc., 2023 PA Super 126, 300 A.3d 430.

And online agreements seem to be especially vulnerable to unconscionability holdings in consumer-friendly jurisdictions such as California. See Heckman v. Live Nation Entertainment, Inc., 120 F.4th 670 (9th Cir. 2024) (affirming holding that online arbitration agreement was unconscionable).

21.1.33.18. Appendix: Would arbitration be binding on a non-signer?

().  Generally, a party doesn't have to arbitrate disputes if it didn't agree to arbitrate; as far back as 1960, in United Steelworkers the (U.S.) Supreme Court described arbitration as "a creature of contract." United Steelworkers of Am. v. Am. Mfg. Co., 363 U.S. 564, 570 (1960); see also Hall Street Associates, L.L.C. v. Mattel, Inc., 552 U.S. 576, 128 S. Ct. 1396 (2008) (using the term in summarizing appellant's argument).

Example: The Texas supreme court held that an officer of a limited-liability company (LLC) who had signed a contract on behalf of the company was not personally bound by the contract's forum-selection clause. Rieder v. Woods, 603 S.W.3d 86 (Tex. 2020).

But: Under Texas law, even a party that didn't sign a contract containing an arbitration provision might have to arbitrate disputes arising under the contract:

Federal courts have recognized that contract law and agency principles can bind a non-signatory to an arbitration agreement under the following theories: (1) incorporation by reference, (2) assumption, (3) agency, (4) alter ego, (5) equitable estoppel, and (6) third-party beneficiary. Wagner v. Apache Corp., 627 S.W.3d 277, 285-86 (Tex. 2021) (affirming reversal of refusal to compel arbitration of indemnity claim; nonsignatory assignees' assumption of contract caused them to be bound by arbitration provision).

Example: Family members of a Texas homeowner wanted to sue the builder of the home; the supreme court ruled that, because the family members had accepted benefits under the construction contract, the family members could be forced to arbitrate their claims against the builder under an arbitration provision in that contract. See Taylor Morrison of Tex., Inc. v. Ha, 660 S.W.3d 529, 532-33 (Tex. 2023) (reversing court of appeals's affirmance of denial of petition to compel family members to arbitrate); see also Lennar Homes of Tex. Land & Constr., Ltd. v. Whiteley, 672 S.W.3d 367 (Tex. 2023) (reversing court of appeals and rendering judgment confirming arbitration award against subsequent purchaser). Hat tip: Frank Carroll (Winstead.com).

Example: A man's nephew bought tickets and took the man to see a "WrestleMania" show — who allegedly lost most of his hearing in one ear from pyrotechnics that were set off during the show. Affirming a WWE motion to compel the man to arbitrate his negligence claim, the Fifth Circuit said that the nephew acted as the uncle's agent for purposes of assenting to an arbitration agreement that had been presented when the nephew bought the tickets online: "An individual who permits a third party to present a ticket for admittance to an event on his behalf is bound by the terms and conditions governing the use of that ticket." To similar effect was another case brought by spectators injured at an NFL game; see Washington Commanders (4th Cir. 2024). World Wrestling Entertainment, Inc. v. Jackson, 95 F.4th 390 (5th Cir. 2024) (affirming motion to compel arbitration). To similar effect was another case brought by spectators injured at an NFL game; see Naimoli v. Pro-Football, Inc. (Washington Commanders), 120 F.4th 380 (4th Cir. 2024) (vacating, reversing in part, and remanding denial of motion to compel arbitration).

Example: The Fifth Circuit reversed a trial court's refusal to compel arbitration, holding that, regardless whether California or Texas law applied, equitable estoppel principles prevented the plaintiff companies from avoiding arbitration, even though those companies had not signed the contract containing the arbitration agreement. See Cure & Assocs., P.C. v. LPL Financial, LLC, 118 F.4th 663 (5th Cir. 2024).

Example: The Texas supreme court held that when a contract was assigned to successors, and those successors assumed the contract, those successors were bound by the contract's arbitration provision. See Wagner v. Apache Corp., 627 S.W.3d 277, 286 n.3 (Tex. 2021) (nonsignatory assignees' assumption of contract caused them to be bound by arbitration provision).

Example: Going even further: Nevada's supreme court ruled that, in appropriate circumstances, one nonsignatory to an arbitration agreement could compel another nonsignatory to arbitrate. See RUAG Ammotec GmbH v. Archon Firearms, Inc., 139 Nev. Adv. Op. 48, 538 P.3d 428 (Nev. 2023) (reversing and remanding denial of motion to compel arbitration).

Counterexample: In an "edge case," a worker was "staffed" to Phillips 66, which was a customer of the worker's employer. The worker sued Phillips 66 for overtime pay. The worker's employment agreement with his employer included an arbitration provision, so Phillips 66 tried to use that to compel arbitration. But the Fifth Circuit said nope: "The issue is not whether [the employee] has an arbitration agreement with anyone — it is whether he has an agreement to arbitrate with the party he is suing, Phillips 66." Which he hadn't, said the court. Hinkle v. Phillips 66 Co., 35 F.4th 417, 420 (5th Cir. 2022) (cleaned up, emphasis added).

Counterexample: A court held that the active-voice wording of an arbitration clause — basically, that the parties must arbitrate disputes — was binding only on the parties that signed the contract, and so non-signatory parties were free to go to court, even though the dispute had arisen in connection with the contract in question. See Madorskaya v. Frontline Asset Strategies, LLC, No. 19-CV-895 (E.D.N.Y. 2021).

21.1.34. Additional notes: In general

21.1.34.1. What typically happens in an arbitration?

In a typical arbitration proceeding:

  • One arbitrator presides at an evidentiary hearing where the disputing parties put on witnesses and offer their exhibits, as in a court trial.
  • After considering the parties' evidence, the arbitrator renders a binding decision, known as an "award."
  • If a party (typically the losing party) doesn't comply with the award voluntarily, then the other party can go to court to have the award "confirmed," which in effect turns the award into an enforceable judgment of the confirming court.
  • Usually, the court won't look especially hard at "how the sausage was made" in producing the award.
21.1.34.2. An arbitrator isn't a "judge"

In standard business- and consumer arbitrations, each case is decided by a privately-engaged arbitrator, not by a publicly-employed judge.

(Some arbitrators are retired judges, but they still act in a private capacity, not an official one.)

The only times an actual judge would be involved would be:

  • If a party didn't want to arbitrate, then there might be court proceedings in which a judge decided whether or not to compel arbitration.
  • if a party refused to comply with an arbitration award, then the other party would likely go to court to confirm and enforce the award.
21.1.34.3. Some dispute-resolution procedures aren't "arbitration"

Example: A California court held that a "review committee" procedure in an employer's "Employee Guide" did not constitute an agreement to arbitrate, because "a third party decision maker and some degree of impartiality must exist for a dispute resolution mechanism to constitute arbitration." Cheng-Canindin v. Renaissance Hotel Associates, 50 Cal. App. 4th 676, 687 (1996).

Example: In a non-arbitration case, a Delaware Chancery Court judge, on his own initiative, stayed (that is, suspended) the court proceedings between a former director of a biotechnology company and the company itself. The basis for the stay was that, under the biotech company's stock-option agreement, the parties' dispute about the interpretation of the agreement was required to be submitted to a committee of the company's board of directors. (The judge later granted the company's motion to dismiss on grounds that Terrell had waived his rights to any unexercised options.) See Terrell v. Kiromic Biopharma, Inc., No. 2021-0248, slip op. (Del. Ch. Jan. 20, 2022).

And mediation is often mistaken for arbitration — but a mediator generally has no authority at all except to try to help parties reach a settlement agreement, typically by "shuttle diplomacy."

Finally, expert determination is not arbitration, for reasons discussed at 21.27.

21.1.34.4. American courts have changed their tune about arbitration

Arbitration used to be disfavored by U.S. courts, but Congress and (repeatedly) the Supreme Court have instructed lower courts to reverse that stance, for example:

The [Federal Arbitration Act] was enacted in 1925 in response to widespread judicial hostility to arbitration agreements. … [The Act reflects] both a liberal federal policy favoring arbitration and the fundamental principle that arbitration is a matter of contract. In line with these principles, courts must place arbitration agreements on an equal footing with other contracts and enforce them according to their terms. AT&T Mobility LLC v. Concepcion, 563 U.S. 333, 131 S. Ct. 1740, 1745-46 (2011) (cleaned up, emphasis added).

Note: As discussed at 21.1.34.5, Congress later prohibited compulsory arbitration for some types of claim.

Many states' laws likewise strongly favor arbitration. Example: The Texas supreme court noted: "Once a valid arbitration agreement is established, a strong presumption favoring arbitration arises and we resolve doubts as to the agreement’s scope in favor of arbitration." Wagner v. Apache Corp., 627 S.W.3d 277, 285 (Tex. 2021) (affirming reversal of refusal to compel arbitration of indemnity claim) (cleaned up).

21.1.34.5. Some arbitration requirements might be legally prohibited

Here are some examples of disputes in the U.S. where compulsory arbitration — mandated by contract before a dispute even arises — might be prohibited by law:

1.  Sexual-assault or -harassment claims: In March 2022, President Biden signed the Ending Forced Arbitration of Sexual Assault and Sexual Harassment Act of 2021, H.R. 4445 (now 9 U.S.C. § 401) which amended the Federal Arbitration Act to ban enforcement of pre-dispute agreements that would compel arbitration of claims of sexual assault or sexual harassment.

2.  California employment- and consumer arbitration: In California, the statute known as A.B. 51 prohibits many employers from requiring mandatory arbitration of claims under the California Fair Employment and Housing Act and certain related statutes.

The California statute drew opposition, and a federal district court preliminarily enjoined enforcement of the statute on grounds of preemption by the Federal Arbitration Act; after an initial appeal and then reconsideration, the Ninth Circuit affirmed. See Chamber of Commerce v. Bonta, 62 F.4th 473 (9th Cir. 2023) affirming Chamber of Commerce v. Becerra, 438 F. Supp. 3d 1078 (E.D.Cal. 2020).

Relatedly: California's S.B. 940 adds new section 1799.208 to the Civil Code; the new section prohibits sellers from requiring consumers to agree to arbitration outside of California, or under any other jurisdiction's substantive law, if the consumer's claim arises in California; consumers can void such requirements and recover their attorney fees for doing so.

And for yet another California law: As summarized in the legislative counsel's digest: For "consumer use agreements," S.B. 82 "limit[s] the dispute resolution terms and conditions [in the agreement] to the use, payment, or provision of the good, service, money, or credit provided by the consumer use agreement," and "make[s] a waiver of these provisions void and unenforceable[.]" (Commenters are expecting federal-preemption challenges.)

3.  Corporate whistleblower claims: Drafters working in the financial-services arena should check the Dodd-Frank Act's prohibition of mandatory arbitration of Sarbanes-Oxley Act "whistleblower" claims; see generally the Supreme Court's decision concerning the required elements of proof. See Murray v. UBS Securities, LLC, 601 U.S. 23 (2024) (reversing and remanding 2d Cir.).

4.  Franken Amendment and government contracts: Government contractors and subcontractors should check the so-called Franken Amendment for its restrictions on arbitration clauses in employment agreements relating to certain government contracts. (The Franken Amendment apparently survived the GOP's takeover of Congress and the White House in the 2016 election, but it might be less relevant now in view of the 2022 enactment of HR 4445, discussed at subdivision 1 above.)

5.  Moreover, in July 2014, President Obama signed Executive Order 13673 — later disapproved by the Republican-controlled Congress and then revoked by the Trump Administration — stating that in federal government contracts for more than $1 million, "contractors [must] agree that the decision to arbitrate claims arising under Title VII of the Civil Rights Act of 1964 or any tort related to or arising out of sexual assault or harassment may only be made with the voluntary consent of employees or independent contractors after such disputes arise"; the order includes a flowdown requirement for subcontracts for more than $1 million.

(The Obama executive order included out exceptions for (i) the acquisition of commercial items or commercially available off-the-shelf items; (ii) collective bargaining agreements; and (iii) some but not all arbitration agreements that were in place before the employer placed its bid for the government contract in question.)

6.  Car dealership franchise agreements: Federal law provides that in franchise agreements between automobile manufacturers and their dealers, pre-dispute arbitration agreements are unenforceable. Interestingly, the law also states that: "Notwithstanding any other provision of law, whenever arbitration is elected to settle a dispute under a motor vehicle franchise contract, the arbitrator shall provide the parties to such contract with a written explanation of the factual and legal basis for the award." 15 U.S.C. § 1226(a)(2).

7.  Lending to military: If your client provides credit to active-duty military personnel or their eligible dependents, be sure to check the regulations that implement the Military Lending Act: Those regs essentially negate any agreement to arbitrate consumer credit disputes between lenders and such borrowers. The regulations don't seem to distinguish between pre-dispute and post-dispute agreements to arbitrate — even though the statute itself appears to make just such a distinction. See 10 U.S.C. § 987(e)(3), implemented in 32 C.F.R. § 232.9(d); see generally, e.g., Steines, part II.B (11th Cir. 2024) (reviewing legislative history).

8.  Livestock & poultry production: Federal regulations governing livestock and poultry production impose restrictions on certain contracts mandating the use of arbitration. Under these regulations, such contracts must include, on the signature page, a specifically-worded notice, in conspicuous bold-faced type, allowing the producer or grower to decline arbitration; moreover, the Secretary of Agriculture seems to have the power to review agreements to determine "whether the arbitration process provided in a production contract provides a meaningful opportunity for the poultry grower, livestock producer, or swine production contract grower to participate fully in the arbitration process." 9 C.F.R. § 201.218.

9.  Home mortgage loan claims (overruled by Congress): In the Truth in Lending regulations, Regulation Z was amended to prohibit pre-dispute arbitration clauses in mortgages secured by dwellings — but that regulation was overturned in 2017 by the GOP Congress and President Trump under the Congressional Review Act (CRA), which prohibits reissuing an overturned rule in substantially the same form without specific congressional authorization. See Arbitration Agreements, 82 Fed. Reg. 33,210 (Jul. 19, 2017) (amending Regulation Z), revoked due to congressional disapproval, 82 Fed. Reg. 55,500 (Nov. 22, 2017). (See generally Regulation Z (Investopedia.com).) See generally Congressional Research Service, The Congressional Review Act (CRA): A Brief Overview (Congress.gov 2023).

Relatedly: The Second Circuit, citing cases, held that if a party were forced to arbitrate a non-arbitrable claim, it could cause irreparable harm, and that would bear on whether it would be appropriate to issue a preliminary injunction against arbitration. See Resource Grp. Int'l v. Chishti, 91 F.4th 107, 115-16 (2d Cir. 2024).

And even if a contract itself is alleged to be void for illegality, a U.S. court will likely enforce an arbitration-delegation provision contained in the contract. See Zirpoli v. Midland Funding, LLC, 48 F.4th 136 (3d Cir. 2022) (reversing denial of motion to compel arbitration).

10.  Certain transportation workers' employment agreements: The first section of the Federal Arbitration Act itself includes a carve-out for "contracts of employment of seamen, railroad employees, or any other class of workers engaged in foreign or interstate commerce." 9 U.S.C. § 1, discussed in Silva v. Schmidt Baking Distribution, LLC, No. 24-2103, part III, slip op. at 9-11, 17 (2d Cir. 2025) (vacating and remanding order compelling arbitration: contracts with LLCs — formed by formerly W-2 employee delivery drivers — were subject to the carve-out of § 1)

21.1.34.6. Who decides whether arbitration was even agreed to?

It could be that one party denies having agreed to arbitration in the first place — for example, because no agreement to arbitrate was ever properly formed. When that happens, the chances are that the court will insist on deciding whether the parties in fact agreed to arbitrate. See, e.g., Ahlstrom v. DHI Mortgage Co., 21 F.4th 631 (9th Cir. 2021) (reversing and remanding district court order that dismissed putative class-action complaint and ordered arbitration) (citing cases from the Supreme Court and other appellate courts).

On that point, the Supreme Court has held that any challenge specifically to the delegation agreement will be heard by the court, not by the arbitrator; see the discussion at 21.1.24.

21.1.34.7. Arbitration of PAGA claims

California's Private Attorneys General Act (PAGA), at Cal. Labor Code §§ 2698 - 2699.6, essentially deputizes employees to act on behalf of the state in pursuing civil actions against employers that violate the state's Labor Code.

Caution: This is one of those areas where — if PAGA claims are a significant possibility — contract drafters should consult counsel about the latest developments. See, e.g., LaCour v. Marshalls of Calif., LLC, No. A170191, slip op. (Cal. App. Dec. 23, 2025) (affirming denial of employer's motion to compel arbitration).

Some gig-economy workers have sued their companies under PAGA. In response, some companies like Uber have sought to compel arbitration under their contracts with the workers. But California courts have held that for purposes of determining standing to bring a PAGA claim, the threshold question whether such a worker is an "employee" or an "independent contractor" is for the court to determine and cannot be delegated to an arbitrator. See, e.g., Winns v. Postmates, Inc., 66 Cal. App. 5th 803 (Cal. App. 2021) (affirming denial of motion to compel arbitration of PAGA claim); Rosales v. Uber Tech., Inc., 63 Cal. App. 5th 937, 942-45, 278 Cal. Rptr. 3d 285 (2021) (citing cases).

Example: A California court held that, under the Supreme Court's Viking River Cruises decision, "arbitration agreements between employers and employees that require arbitration of the individual portion of a PAGA claim are enforceable, but arbitration agreements that require arbitration (or waiver) of the representative portion [i.e., the private-attorney-general portion] of a PAGA claim are not enforceable." Piplack v. In-N-Out Burgers [sic], 88 Cal. App.5th 1281, 1288 (2023), citing Viking River Cruises, Inc., v. Moriana, 596 U.S. 639, 142 S. Ct. 1906 (2022).

Example: In another 2023 California decision, in an Uber driver's lawsuit against that company, California's supreme court held that "an aggrieved employee who has been compelled to arbitrate claims under PAGA that are premised on Labor Code violations actually sustained by the plaintiff maintains statutory standing to pursue PAGA claims arising out of events involving other employees." Adolph v. Uber Technologies, Inc., 14 Cal. 5th 1104, 1114 (2023) (reversing court of appeals and remanding; emphasis added).

Example: The Ninth Circuit cited the California supreme court's Adolph case in a former employee's lawsuit against Lowe's Home Centers. See Johnson v. Lowe's Home Centers, LLC, 93 F.4th 459 (9th Cir. 2024) (vacating district-court order).

21.2. Attorney Fees Protocol

21.2.1. Parties; applicability

When this Protocol is agreed to, it will apply in any "Proceeding" — that is, in any lawsuit, arbitration (if arbitration is agreed to), or other contested proceeding, of any nature, relating to the Con­tract — between A and B.

Note

Relating to: See 20.33.

21.2.2. Prevailing-party entitlement to attorney fees

  1. If A is the "prevailing party" in the Proceeding — as determined by law — THEN: B will reimburse A for:

    1. A's "attorney fees," as defined below; and
    2. A's "costs," as that term is commonly understood in U.S. courts,

    for all stages of the Proceeding, unless the Con­tract clearly provides otherwise.

  2. Which party is the prevailing party is to be determined as provided by law.
Note

().  Subdivision 1.a: This overrides the "American Rule" for attorney fees: Each party must bear its own attorney fees — unless a contract or statute provides otherwise (see 21.2.6.5). (Drafters could use Option 21.2.5.1 to adopt the American Rule.)

Subdivision 1.b: Courts often award "costs" even when not awarding attorney fees; costs typically include charges such as court filing fees; arbitration-administration fees; deposition- and transcript charges; and the like.

Subdivision 2: Some courts have held that, if the putatively winning side was awarded neither monetary damages nor equitable relief, then that party isn't considered the prevailing party for purposes of an award of attorney fees. See, e.g., Intercontinental Group Partnership v. KB Home Lone Star LP, 295 S.W.3d 650 (Tex. 2009).

21.2.3. Definition: Attorney fees

  1. For purposes of the Con­tract, the term "attorney fees" — whether or not capitalized, and with or without an apostrophe — refers to all reasonable professional fees and -expenses, of any kind, paid or owed by a party, at all stages of the dispute.
  2. Likewise, the term encompasses (without limitation) such fees and expenses paid to or for one or more attorneys; law firms; and testifying- and/or consulting experts.
Note

A federal court held that the term "reasonable attorney fees" (emphasis added), in a contract's indemnification provision, was not indefinite and therefore didn't invalidate the entire contract. See Days Inns Worldwide, Inc. v. 4200 Rose Hospitality LLC, No. 2:22-cv-04822, slip op. at part III (D.N.J. Aug. 25, 2025) (citing cases and granting, in part, Days Inns motion for partial summary judgment; unpublished).

21.2.4. Fees on fees

The prevailing party is likewise entitled to recover attorney fees and costs incurred in enforcing its right to recover attorney fees and/or costs under this Protocol.

Note

This section seeks to "write around" the general rule precluding recovery of "fees on fees" — that is, a prevailing party can't recover attorney fees incurred in enforcing the contract's attorney-fee provision — unless the provision clearly says otherwise. See, e.g., 1046 Munras Properties, L.P. v. Kabod, 2025 COA 71, No. 24CA0934, slip op. ¶ 40-41 (Colo. App. 2025) (citing numerous cases from various jurisdictions; attorney-fee provision allowed fees-on-fees recovery). Contra: Park Union Condominium v. 910 Union St., LLC, 2019 NY Slip Op. 31994(U) part 1 (N.Y. Sup. Ct.) (fees on fees not recoverable).

21.2.5. OPT-IN TERMS

None of the Options below will apply unless the Con­tract clearly adopts the specific Option.

21.2.5.1. Option: American Rule for Attorney Fees

If this Option is agreed to, THEN: A WAIVES any right that A might have to be reimbursed by B for attorney fees — even if a law or rule would otherwise have given A that right for the dispute in question.

Note

The so-called American Rule for attorney fees is the general rule in U.S. jurisdictions: Each party must bear its own attorney fees — unless a contract or statute provides otherwise. See, e.g., Paul Elton LLC v. Rommel Delaware, LLC, No. 2019-0750, slip op. (Del. Ch. Mar. 16, 2022) (denying motion for attorney fees). In some jurisdictions, there might be a "special circumstances exception" to the American Rule that would allow recovery of attorney fees even without a contract provision to that effect. But such an exception might be a tough sell to a court.

21.2.5.2. Option: Texas Rule for Attorney Fees

If this Option is agreed to, AND A successfully asserts a claim against B for breaching the Con­tract — but not if A successfully defends against such a claim — THEN: A is entitled to recover, from B, the attorney fees and costs that A incurred in asserting the claim.

Note

().  This "Texas Rule" is modeled on section 38.001 of the Texas Civil Practices and Remedies Code — which doesn't allow a party to recover attorney fees for successfully defending against a claim for breach of the Con­tract. See, e.g., Polansky v. Berenji, 393 S.W.3d 362, 368 (Tex. App.—Austin 2012) (reversing and rendering award of attorney fees to defendant that prevailed against breach-of-contract claim; citations omitted).

A similar rule is used in some contracts, allowing not a prevailing party per se, but a "non-breaching party" that successfully sues for breach, to recover fees. Example: In an Illinois case, a contract's attorney-fee provision read: "Either party shall be entitled to recover from the other party any and all costs and expenses, including reasonable attorney’s fees, in successfully enforcing the terms and provisions of this Agreement." See Price v Carri Scharf Trucking, Inc., No. 24-2481, slip op. at 4, 14-15 (7th Cir. Jun. 13, 2025) (affirming district court's refusal to award attorney fees to prevailing defendant); see also, e.g., Southern Coal Corp. v. Drummond Coal Sales, Inc., 25 F.4th 864, 876 (11th Cir. 2022) (Carnes, J., concurring in the judgment reversing and remanding district court's rejection of claim for attorney fees).

Caution: When drafting a provision like this, it's wise to refer to the breach-of-contract plaintiff, not as the non-breaching party, but instead as, say, the "contract claimant." Doing so would address the situation that occurred in Powertech (N.D. Cal. 2014), where the contract in suit included a termination-for-breach provision that referred to the right of the non-breaching party to terminate. That wording, said the court, meant that the party that had purported to terminate the contract didn't actually have the power to do so — because that party was itself in breach, of a different contract provision. On that reasoning, a breach-of-contract plaintiff could lose its claim for attorney fees because the plaintiff was itself in breach of some contract provision. See Powertech Tech., Inc. v. Tessera, Inc., No. C 11-6121 CW, slip op. at part I.A (N.D. Cal. Jan. 15, 2014) (on summary judgment).

In California and Oregon, the law might well automatically transform such a one-sided attorney-fee clause into a prevailing-party clause, as discussed at 21.2.6.7.

Pro tip: If your client might be more likely to be the defendant in a dispute, and if Texas law will apply, then your client might want to override the Texas Rule using a prevailing-party clause (see 21.2). On the other hand, if your client wants the Texas Rule to apply, it might want to include this Option in the contract.

21.2.5.3. Option: Attorney Fees in Motion Practice
  1. If this Option is agreed to, AND A prevails against B in a motion, interlocutory appeal, or other interim proceeding, THEN: A is entitled to be reimbursed, by B, for the reasonable attorney fees that A incurred for the interim proceeding.
  2. If B later ends up being the prevailing party in the action as a whole, THEN: B nevertheless will not be entitled:
    1. to a refund of what B paid under subdivision A of this Option; nor
    2. to recover B's own attorney fees for the interim proceeding.
Note

().  This has in mind that one of the major expenses in any lawsuit or arbitration is attorney fees for interim proceedings such as motion practice — e.g., motions filed with the court or arbitrator to compel discovery; for preliminary injunctions; for summary judgment, etc.

Much of the expense of motion practice comes from a seeming article of faith among litigation counsel, along the lines of the saying attributed to Walter Gretzky, father of hockey legend Wayne Gretzky: You miss 100% of the shots you don’t take. For litigation counsel, Gretzky père's dictum could be paraphrased as: You’ll be denied on 100% of the motions (and oppositions) that you don’t file. The problem, of course, is that in situations like this, when a party's litigation counsel "takes the shot," it inflicts burden, expense, and delay on the other party and the court — too often, to no real purpose.

Oh, sure: Courts' rules of procedure typically "require" lawyers and parties to play nice. A judge could impose sanctions for bad behavior.

But in reality, judges seldom impose sanctions on parties or on lawyers, even for behavior that might seem egregious.

And a lawyer's concern about being sanctioned will sometimes be outweighed by concern that an angry client will think ill of the lawyer for supposedly not doing enough to "smite" the other party. Yes, smiting is "a thing": Sometimes a party to a lawsuit will want to inflict pain on its adversary even more than it wants to put the lawsuit behind it — even if, on balance, doing so would be more costly than a quick settlement. This can happen in divorce- and child-custody cases, but it's been known to happen in business litigation, too.

(Psychological research has suggested that humans and other species are willing to punish perceived bad behavior by others, even when doing so results in personal cost. Researchers have conjectured that, over millennia, such behavior has been "programmed" by natural selection due to the evolutionary advantages of the group cohesion that can be fostered by such "costly punishment.") See, e.g., Robert Boyd, Herbert Gintis, Samuel Bowles, and Peter J. Richerson, The evolution of altruistic punishment, Proceedings of the Nat'l Academy of Sciences (2003); Kimmo Eriksson et al., Perceptions of the appropriate response to norm violation in 57 societies (Nature.com 2021).

So, by contractually providing for awards of attorney fees in motion practice, drafters can help encourage the parties and their lawyers to be reasonable in the positions they take along the way.

21.2.5.4. Option: Attorney Fees for ADR Nonparticipation
  1. If this Option is agreed to, it wil govern whenever, in any such proceeding:
    1. B tries to block the proceeding in court, or
    2. B does not participate in good faith even to a minimal extent.
  2. If B later ends up losing the dispute, then B will pays (or reimburse) all of A's attorney fees for the entirety of the dispute in question, at all stages, including but not limited to appeals.
  3. Moreover, even if B ends up winning the dispute, B still will not be entitled to recover its own attorney fees from A, even if B would otherwise be entitled to do so.
  4. The types of dispute-resolution proceeding contemplated by this Option include, for example, arbitration; mediation; escalation (whether internal or to a neutral advisor); and mini-trial, each when called for by the Con­tract.
Note

().  This is designed to incentivize compliance with any provision of the Con­tract requiring the parties to participate in one or more dispute-resolution proceedings. That could be important in bitter lawsuits where one party wants to "smite" the other (see the discussion at 21.2.5.3).

Background: At almost any point in an arbitration (or other alternative dispute resolution ("ADR") proceeding), a party that desired to delay the proceedings might go to court to challenge the propriety of the ADR proceeding. To combat such tactics, it can be useful to give a delaying party some "skin in the game"; awarding fees against a party that does so is suggested in a 2013 article by experienced arbitrator Gary McGowan (now behind a paywall).

This Option is informed by some real-world contract provisions that played roles in lawsuits between the parties; the intent is to provide an economic disincentive to help discourage a party from "blowing off" contractual dispute-resolution provisions. Courts have upheld contract provisions along these lines:

Example: A contract for the sale of real estate included a provision that "if a party does not agree first to go to mediation, then that party will be liable for the other party's legal fees in any subsequent litigation in which the party who refused to go to mediation loses …." Wuestenberg v. Rancourt, 2020 ME 25, 226 A.3d 227, 232 ¶ 18 (2020) (cleaned up).

Example: A state appeals court reversed a trial court's award of attorney fees to a prevailing defendant, on grounds that the parties' contract required mediation but the defendant had refused to participate the mediation. See Cullen v. Corwin, 206 Cal. App. 4th 1074, 142 Cal. Rptr. 3d 419 (2012); see also, e.g., Lange v. Schilling, 163 Cal. App. 4th 1412 (2008) (reversing award of attorney fees to prevailing plaintiff); Rivas v. CBK Lodge General Partner, LLC, No. 3:19-CV-01948 (M.D. Pa. Jul. 27, 2021) (granting motion to dismiss a defendant's third-party complaint for indemnification under a contract, on grounds that the defendant had not complied with a mediation requirement in the contract).

Counterexample: A prevailing party had initially refused to mediate as required by the contract in suit. But later — and crucially, before the lawsuit was filed — that party had relented and offered to mediate the dispute. A state appeals court reversed a trial court's refusal to award attorney fees. See Evleshin v. Meyer, No. H051869, slip op. (Cal. App. Nov. 6, 2025).

Counterexample: The Seventh Circuit held that: "Because the contract between Technical Security and EPI does not specify who must seek mediation and when, we cannot resolve this dispute on the record before us. We therefore vacate the district court’s entry of summary judgment for EPI and remand for further proceedings." Tech. Security Integration, Inc. v EPI Techs, Inc., 126 F.4th 557, 559 (7th Cir. 2025) (vacating and remanding summary judgment; emphasis added).

Tangentially: A winning party was denied attorney fees under an analogous clause, on grounds that the winning party never asked for mediation (as required by the contract) and thus the losing party had not refused to mediate. See Thompson v. Cloud, 764 F.3d 82, 92 (1st Cir. 2014) (affirming lower-court decision).

21.2.5.5. Option: Attorney Fees for Unproved Accusations
  1. When this Option is agreed to, it will govern if, in any dispute relating in any way to the Con­tract:
    1. A accuses B to the Con­tract — and/or B's affiliates, or the people of any of them — of criminal conduct, fraud, and/or breach of fiduciary duty relating to the Con­tract or the parties dealings under the Con­tract; but
    2. A does not prove the accusation with the degree of proof required by law or, if higher, by the Con­tract.
  2. In that situation, A is to pay, or reimburse, all of the attorney fees incurred by or on behalf of the accused in defending against A's accusation.
  3. "Tie goes to the runner": In any case of a close call about whether A is to reimburse particular attorney fees under this Option, then the answer is yes: A is to do so.

21.2.6. Additional notes

21.2.6.1. The "American Rule" for attorney fees
  • When agreed to, the prevailing-party provision in Option 21.2.5.1 overrides the American Rule.
  • The so-called American Rule for attorney fees is the general rule in U.S. jurisdictions: Each party must bear its own attorney fees — unless a contract or statute provides otherwise. See, e.g., Paul Elton LLC v. Rommel Delaware, LLC, No. 2019-0750, slip op. (Del. Ch. Mar. 16, 2022) (denying motion for attorney fees). In some jurisdictions, there might be a "special circumstances exception" to the American Rule that would allow recovery of attorney fees even without a contract provision to that effect. But such an exception might be a tough sell to a court.
21.2.6.2. Indemnity language might be an exception

One possible contractual exception to the American Rule — even without a prevailing-party provision such as Option 21.2.5.1 — is if a contract includes indemnity language (see Protocol 14.3) requiring indemnity against harm resulting from breach of the contract.

Example: In ams-OSRAM (Fed. Cir. 2025), a confidentiality agreement (a.k.a. "NDA") called for the parties to "hold harmless the other against any and all damage, losses or liability (including reasonable attorneys' fees) suffered by the other as a result of any breach of the representations, warranties, and agreements set forth herein." The plaintiff successfully sued the defendants for, among other things, breach of the NDA's confidentiality obligations. A federal appeals court affirmed a trial-court holding that this indemnity language — as a so-called first-party clause — overrode the American Rule and entitled the successful plaintiff to recover its attorney fees for pursuing its breach-of-contract claims. See ams-OSRAM USA Inc. v. Renesas Elecs. America Inc., 133 F.4th 1337, 1356 (Fed. Cir. 2025). (Hat tip: Matt Dedon in a post at the redline.net site.)

21.2.6.3. Attorney-fee awards can be big

An attorney-fee award can dwarf the rest of a judgment; when a contract contains a prevailing-party attorney fees clause, the losing party could find itself on the hook for attorney fees that far exceed the amount originally in controversy.

Example: In the hotly-contested GT Issa Construction (Tenn. 2021), a home builder was found to have breached a contract with a homeowner; the builder was ordered to pay damages of $6,800 — plus more than $200,000 in attorney fees under the contract's prevailing-party attorney fee clause. See GT Issa Constr., LLC v. Blalock, No. E2020-00853-COA-R3-CV, slip op. (Tenn. App. Nov. 23, 2021) (affirming judgment on jury verdict).

Caution: Some parties — for example, a large, wealthy, litigious company that's contracting with a much-smaller one — might be adamant that each party will always pay its own attorney fees; that's because the large, wealthy company wants to be able to use the cost of litigation as a way of subtly pressuring the smaller one to settle on favorable terms. To that end, parties that wanted to contractually impose the American Rule could use language such as in Option.

21.2.6.4. Attorney fees can discourage fighting a contract provision

().  Protocol 10.2 has in mind that Trying to back out of a contract's agreed "policy statement" (to use Ken Adams's term) should be a no-no because it often results in needless expense and delay in resolving disputes for the parties. Unfortunately, though, the law doesn't really discourage over-the-top arguments about contract language — in fact, in recent years the Texas supreme court has taken what appear to be inconsistent positions on this issue, Compare James Constr. Grp., LLC v. Westlake Chem. Corp., 650 S.W.3d 392, 415-18 (Tex. 2022) (reversing court of appeals; contract's exclusion of consequential damages was not a covenant not to seek such damages) with Transcor Astra Group S.A. v. Petrobras America Inc., 650 S.W.3d 462, 483 (Tex. 2022) (reversing court of appeals; reliance disclaimer in settlement agreement barred fraud claims and so attorney-fee award was not an abuse of discretion): "By asserting claims it had agreed never to assert, Petrobras broke the promise it made in the settlement agreement and caused Astra to incur substantial fees and costs to enforce that promise" (emphasis added).] although in Jones (5th Cir. 2025), the court held that attempting to rescind a contract to avoid payment was itself a breach. See Jones v. City of Hutto, No. 24-50096, part III.D, slip op. at 20 (5th Cir. Oct. 7, 2025).

The "withdraws the contrary assertion' language in Protocol 10.2 is based (very) loosely on the procedures set forth at Rule 11(c) of the Federal Rules of Civil Procedure, with which U.S. federal-court litigators are familiar.

Here are a few hypothetical examples of possible such contrary assertions:

  1. A seeks to recover consequential damages from B (see 21.5) when the Con­tract excludes such recovery;
  2. A seeks monetary relief from B in excess of an agreed "cap" (see Protocol 21.7)
  3. A asserts a purported right, or a purported obligation on B's part, that A had waived (see Protocol 3.18)
  4. A asserts that a notice took effect at a time inconsistent with the notice provisions stated in the Con­tract (see Protocol 3.14)
  5. A asserts that the Con­tract or a related document was amended or otherwise modified in a manner inconsistent with the amendment provisions of the Con­tract (see Protocol 3.1)
  6. A asserts that an action taken by A was timely even though A took the action after a deadline stated in the Con­tract or a related document (for example, a statement of work).
21.2.6.5. Statutes might allow recovery of attorney fees

By statute, Congress and various state legislatures have allowed or even required awards of attorney fees to specified classes of prevailing parties, thus overriding the "American Rule" that normally controls (see 21.2.5.1).

Example: U.S. antitrust law requires "a reasonable attorney's fee" to be awarded to "any person who shall be injured in his business or property by reason of anything forbidden in the antitrust laws …." 15 U.S.C. § 15(a). This statute was applied in O'Bannon (9th Cir. 2018), where the court affirmed an award of more than $40 million in attorney fees to a group of current and former student athletes — the athletes had sued the NCAA over a then-existing rule that prohibited student athletes from being paid for use of their names and likenesses in advertising and video games. See O'Bannon v. NCAA, No. 09-3329 (N.D. Cal. Mar. 31, 2016), aff'd, 739 F. App'x 890, No. 16-15803 (9th Cir. Jun. 29, 2018) (unpublished). The district court had reduced the original fee award of nearly $46 million, granted by a magistrate judge; see 114 F. Supp. 3d 819 (N.D. Cal. 2015) (magistrate judge award). See also, e.g., Dan Whateley and Ashley Rodriguez, How NIL deals and brand sponsorships are helping college athletes make money (2024).

Example: Under Cal. Civ. Code § 1021.9, a "specialized" California statute (as in, benefiting a particular class of politically-important special interests):

In any action to recover damages to personal or real property resulting from trespassing on lands either under cultivation or intended or used for the raising of livestock, the prevailing plaintiff shall be entitled to reasonable attorney’s fees in addition to other costs, and in addition to any liability for damages imposed by law.

As explained by a California appeals court: "The statute is intended to ensure that farmers are able to protect their land from trespassers through civil litigation." Kelly v. House, 47 Cal. App.5th 384, 390 (Cal. App. 2020) (reversing denial of statutory attorney fees).

A 2009 report by the Congressional Research Service lists a number of federal statutes of this nature.

21.2.6.6. One-sided attorney-fee clauses might well be enforced

Some contracts contain unilateral attorneys' fee clauses; for example, a real-estate lease might state that the landlord can recover its attorney fees if it has to sue the tenant, while remaining silent as to whether the tenant can ever recover its attorney fees. Such unilateral clauses might well be given effect by courts. See, e.g., Allied Indus. Scrap, Inc., v. OmniSource Corp., 776 F.3d 452 (6th Cir. 2015), discussing Wilborn v. Bank One Corp., 906 N.E.2d 396 (Ohio 2009). In the Wilborn case cited by the Sixth Circuit, the state's supreme court had affirmed dismissal of a lawsuit by borrowers against lenders; the court rejected the borrowers' claim that a unilateral attorneys' fee clause, in a residential mortgage loan agreement form, should be held void as contrary to public policy.

(In a lease, the American Rule (21.2.5.1), combined with such a fee-shifting provision, would normally mean that the tenant could not recover, even if it were the prevailing party in a suit brought by the landlord — unless a statute provided otherwise, as in the California Rule discussed at 21.2.6.7.)

21.2.6.7. CA, OR, (partly) NY: Any fee clause is "prevailing party"

California Civil Code § 1717 provides, in essence, that any one-way attorney fees provision (as is sometimes seen in consumer-facing contract forms) is to be treated as a prevailing-party provision; moreover, attorney fees under that section cannot be waived. Much the same is true in Oregon, and New York has a similar rule for consumer contracts. See, e.g., Elation Sys. Inc. v. Fenn Bridge LLC, 71 Cal. App. 5th 958, slip op. at 23-25 (Cal. App. Nov. 22, 2021) (unpublished portion of opinion that vacated and remanded award of attorney fees to prevailing defendants); Or. Rev. Stat. § 20.096; NY Gen. Obl. Law § 5-327(2).

21.2.6.8. Alaska's unusual attorney-fees rule

Under Alaska R. Civ. P. 82, a prevailing party is entitled to recover its attorney fees, with the amount of the fee being a percentage of the judgment (on a sliding scale with different brackets for different outcomes, and subject to possible adjustment by the trial judge).

21.2.6.9. Attorney fees in Delaware shareholder lawsuits

Delaware law allows awards of attorney fees in certain shareholder lawsuits even when the shareholder might not qualify as a prevailing party "where: (1) the suit was meritorious when filed; (2) the defendants took an action that produced a corporate benefit before the plaintiffs obtained a judicial resolution; and (3) the suit and the corporate benefit were causally related." Anderson v. Magellan Health, Inc., 298 A.3d 734, 739-40 (Del. Ch. 2023) (awarding $75,000 in attorney fees to shareholder's counsel but not the $1.1 million requested).

21.2.6.10. North Carolina's "up to 15%" rule

A North Carolina statute states that a promissory note and various other forms of indebteness can require payment of attorney fees as a percentage of the "outstanding balance" (a defined term), with a ceiling (or "haircut") of 15% of the outstanding balance. See N.C. Gen. Stat. § 6-21.2, discussed in Colorado Bankers Life Ins. Co. v. Academy Financial Assets, LLC, 60 F.4th 148, 152-56 (4th Cir. 2023) (district court did not err in following plain language of statute and imposing a 15% fee award of just over $6 million without requiring evidence of attorney’s actual billings or usual rates).

21.2.6.11. Spelling: Where's the apostrophe???

This book uses the simpler term attorney fees, about which lexicographer Bryan Garner observes: "Although inelegant, attorney fees is becoming more common — presumably to avoid making a decision on [where to put] the apostrophe altogether." LawProse Lesson #115: Is it attorney’s fees or attorneys’ fees?, citing Garner’s Dictionary of Legal Usage 94 (3d ed. 2009); compare • 42 U.S.C. § 1988 (civil rights statute), which uses "a reasonable attorney's fee"; with • 28 U.S.C. § 1927, which provides for awards of excess "attorneys' fees" against attorneys who "multiplies the proceedings in any case unreasonably and vexatiously …."

It's possible that Garner's spelling choice could be catching on: As one data point, the (U.S.) Defend Trade Secrets Act, enacted in 2016, uses "attorney fees" in a provision that requires employers to advise their employees (and individual contractors and consultants) of the individuals' whistleblower rights, as discussed at 5.3.35.3. See 18 U.S.C. § 1833(b)(3)(A), (b)(4).

For a lighthearted review of "authorities" about the apostrophe, see Estate of Gentry (S.D. Tex. 2023). See Est. of Gentry v. Hamilton-Ryker IT Sols., LLC, No. 3:19-cv-00320, slip op. at n.2 (S.D. Tex. Aug. 7, 2023) (Andrew M. Edison, M.J., recommending grant of attorney fees), adopted in its entirety (Aug. 24, 2023) (hat tip: Debra Cassens Weiss).

21.3. Blue-Pencil Request Protocol

21.3.1. Applicability

  1. When this Protocol is agreed to, the parties follow it in any situation in which a court, agency, arbitation panel, or other tribunal of competent jurisdiction (the "Tribunal") holds that a provision of the Con­tract is invalid, void, or otherwise unenforceable.
  2. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol
Note

A so-called "blue-pencil clause" might be used with, e.g., a noncompetition clauses, asking the court to modify an unenforceable provision to make it enforceable — but some courts will refuse, as discussed in the commentary at § 21.3.2.

21.3.2. Modification request

The Tribunal is respectfully requested (if a court or other governmental body), or directed (if an arbitration panel), to reform the defective provision — if practicable — to the minimum extent necessary to cure the defect, while still giving effect to the intent of the defective provision.

Note

().  Note the difference between the tribunal being requested vs. directed:

  • On one hand, parties to a contract can generally direct an arbitrator or arbitration panel to do blue-penciling. That's because arbitration is "a creature of contract"; an arbitrator's power stems solely from the parties' agreement and any agreed rules.

    (As a practical matter, though: If an arbitrator were to disregard even an explicit blue-pencil request, a court might be unwilling to do anything about it; see the notes to § 21.1.33.15.)

  • In contrast, parties to a contract can't "direct" a court to do anything, as discussed at 8.18.

    Whether a court will honor a blue-pencil request might well vary with the jurisdiction.

Example: New York's highest court allowed the state's courts to engage in blue-penciling of restrictive covenants in noncompetition covenants, but only if:

  • the employer demonstrates an absence of overreaching, coercive use of dominant bargaining power, or other anti-competitive misconduct,
  • but has in good faith sought to protect a legitimate business interest,
  • consistent with reasonable standards of fair dealing. BDO Seidman v. Hirshberg, 93 N.Y.2d 382, 395, 712 N.E.2d 1220, 690 N.Y.S.2d 854 (1999) (reversing refusal to partially-enforce accountant's post-employment restrictive covenant; citation omitted, formatting modified).

But courts in some other jurisdictions will refuse to engage in blue-penciling of a contract even if contract specifically authorizes it. In those jurisdictions, the courts say, in effect, You people should have drafted the contract correctly — don't expect us to fix your mistake.

Example: Delaware's supreme court declined to write a bright-line rule one way or another about blue-penciling — but the court upheld the state chancery court's refusal to blue-pencil the noncompetition and nonsolicitation covenants in question. Sunder Energy LLC v. Jackson, 332 A.3d 472, 488, text accompanying n.128 (Del. 2024).

21.4. Bond Waiver Protocol

21.4.1. Waiver

In any action relating to the Con­tract, each party (referred to here as the "Movant") WAIVES any requirement, in law or otherwise, that the Movant post a bond as a prerequisite for obtaining a preliminary injunction, temporary restaining order, or similar interim relief against another party (the "Respondent").

Note

This Protocol specifies that each party waives the bond requirement. But it's far more likely that anyone drafting such a clause would specify that only the other party waived the requirement. ¶ Incidentally, this Protocol relates to preliminary injunctions — a party that successfully obtains a permanent injunction after a final hearing will generally not be required to post a bond. See Michael T. Morley, Erroneous Injunctions, 71 Emory L. J. 1137 at 1164 & n.186 (2022).

21.4.2. Additional notes

21.4.2.1. Background: When and why a bond must be posted

In American law, when a party (the "movant") seeks a preliminary injunction or temporary restraining order, the movant typically must post security — usually in the form of a bond, commonly issued by an insurance carrier. The reason is to be sure that a pot of money is available to compensate the restrained party in case the preliminary injunction turns out to have been wrongly granted. See generally, e.g., Fed. R. Civ. P. 65(c); Tex. R. Civ. P. 684; Thomas E. Patterson, Handling the Business Emergency, ch. 3 (American Bar Association 2009), excerpted at http://goo.gl/ak7Mt (books.google.com).

21.4.2.2. A hypothetical example

Big companies sometimes want smaller ones to waive any requirement for a bond in connection with a motion for preliminary- or permanent injunction — but that can be a bad idea for the waiving party, as discussed in the comments below.

Consider the situation where, hypothetically, you're a small vendor trying to make a sale to a giant conglomerate:

  • As usual, the giant conglomerate insists on using its own purchase-order form (concerning which, see 28.8).
  • And that PO form allows the giant conglomerate to seek a preliminary injunction against you in various circumstances — as well as proclaiming that you, the vendor, waive the bond requirement.

From the congomerate's perspective, your bond waiver would save their legal department a bit of trouble in rustling up a bond, should the conglomerate ever decided to seek a preliminary injunction against you for (allegedly) breaching the the contract.

So should you, the vendor, agree to the waiver? Ideally, no, for the reasons discussed below — although it might be an acceptable business risk.

21.4.2.3. Caution: Agreeing to a bond waiver could be dangerous

Any party asked to agree to a bond waiver should think hard about it. Suppose that events play out like this:

  • The big company successfully obtains a preliminary injunction forbidding you from doing whatever is upsetting the big company.
  • This interferes greatly with your business — possibly even putting you out of business.
  • Then later, it turns out (perhaps after a full trial) that the preliminary injunction shouldn't have ben granted after all.

If you'd previously waived the bond requirement, then you'd have no recourse for the wrongful injunction.

Example: The Supreme Court once noted: "A party injured by the issuance of an injunction later determined to be erroneous has no action for damages in the absence of a bond" (citations omitted). See W.R. Grace & Co. v. Rubber Workers, 461 U.S. 757, 770 n.14 (1983), explained in Mallet & Co. v. Lacayo, 16 F.4th 364, 390-93 (3d Cir. 2021) (vacating and remanding preliminary injunction); see also, e.g., Ofer Grosskopf and Barak Medina, Remedies for Wrongfully-Issued Preliminary Injunctions: The Case for Disgorgement of Profits, 32 Seattle L. Rev. 903, 908-09 & nn.25-26 (2009).

Of course, a court might not give effect to a contractual bond waiver.

  • Example: In a Delaware chancery-court case, Vice Chancellor Glasscock imposed a bond requirement notwithstanding a contractual waiver, noting that "although this Court has enforced bond waivers when granting motions for preliminary injunctions, the existence of such a waiver does not bind the Court." Steward Health Care Sys. LLC v. Tenet Bus. Servs. Corp. (Del. Ch.) (footnotes omitted), aff'd w/o opinion, 311 A.3d 806 (Del. 2023).
  • Example: In a California case, an employment agreement stated that the company, but not the employee, was entitled to injunctive relief, and without posting a bond (on the subject of a bond waiver, see Protocol 21.4). An appeals court regarded this as a factor in the agreement's unconscionability. See Silva v. Cross Country Healthcare, Inc., No. B337435, slip op. at 22-23 (Cal. App. Jun. 13, 2025) (affirming trial court’s order finding employer’s arbitration agreement unenforceable and denying employer’s motion to compel arbitration) (citing cases).

But as the saying goes, hope is not a plan — a prospective respondent might be taking a considerable business risk by gambling that a court would disregard a bond waiver.

21.5. Consequential Damages Exclusion Protocol

It can be worthwhile to define "consequential" damages, because the term's vagueness, and its different meanings in different jurisdictions, can lead to costly and perhaps-avoidable litigation.

21.5.1. Definition: Consequential damages

When this Protocol is agreed to: In all matters relating to the Con­tract, the term "consequential damages" refers to a monetary award to compensate a party for harm resulting from a breach of the Con­tract, where at the time the Con­tract was entered into (or, if the Con­tract is a master agreement, the time the relevant transaction was agreed to), all of the following were true:

  1. the harm was not generally foreseeable — that is, reasonable people, experienced in the relevant area of business, would not have expected the harm, in the ordinary course of things, to be a probable result of the breach — and so the breaching party normally would not have been liable for that harm; and
  2. the breaching party nevertheless knew or had reason to know of special circumstances that made the harm reasonably likely to result from breach, and so the breaching party would be liable for the harm.
Note

().  This Protocol follows the general approach of the classic English case, Hadley v. Baxendale, discussed in more detail at 21.5.8.7.

Subdivision 2 could be thought of as "Well, you should have foreseen it!" harm — as in, experienced people would be at least mildly surprised that the harm in question would have occurred from the breach.

The term atypical damages seems a more-apt label than consequential damages, because the latter is kind of a dumb name (see 21.5.8.11). But of course it'd likely be a fool's errand try to change generations of lawyer-speak.

Pro tip: Some practioners (I'm not one of them) like to include a detailed "laundry list" of highly-specific categories of excluded damages, such as the example at 21.5.8.5.

21.5.2. Prerequisite for consequential-damages liability

A breaching party could be liable for consequential damages if — in a writing communicated to the breaching party at substantially the time the parties entered into the Con­tract — the other party:

  1. expressly identified particular types of special circumstance of the kind described at § 21.5.1; and
  2. clearly indicated that the other party expected the breaching party to be responsible for any damages for breach that were associated with such special circumstances (or, that such damages would not be subject to the exclusion of this Protocol).
Note

().  This exception borrows from a clause proposed at the redline.net forum for lawyers.

The written-communication prerequisite could be met by stating the required information in the Con­tract itself.

For this purpose, a statement of work under a master services agreement could count as "the Con­tract."

21.5.3. Exclusion of consequential damages

  1. When This Protocol is agreed to: A party breaching the Con­tract WILL NOT BE LIABLE for "consequential damages," as defined at § 21.5.1, resulting from the breach. This will be true even if — whether at the time of forming the Con­tract or before the breach — the breaching party actually knew or should have known of special circumstances as described above.
  2. For emphasis: The other party WAIVES, and must not seek, such damages from the breaching party.
Note

().  Some contract drafters reflexively exclude liability for consequential damages, likely because of the term's vagueness, as one way for the parties to allocate their respective risks by agreement. But: Parties might well be better served by one or more damages caps instead (see 21.5.8.4).

"The other party … must not seek, such damages": See the discussion in the commentary at Protocol 21.18.6: In one case, the Texas supreme court held that a waiver of consequential damages was not a covenant not to seek such damages; see also Option 10.2, which provides for awards of attorney fees against parties that take positions contrary to provisions such as this one.

21.5.4. Certification: No known-but-undisclosed special circumstances.

Each A certifies, to each B, that, so far as A is aware, there are no "special circumstances," of the kind referred to in § 21.5.2 above, that could give rise to A's incurring consequential damages if B were to breach the Con­tract.

Note

This section is inspired by Ken Adams's suggestion of a certification (a suggestion that he subsequently refined).

21.5.5. Permitted reliance on this exclusion

Each A acknowledges, with the effect stated at Protocol 11.2 (acknowledgement definition):

  1. that each B is relying on A's agreement to this Protocol as a "material" element — that is, an important part — of the economic bargain between the parties that is reflected in the Con­tract; and
  2. that it is reasonable for B to rely on A's agreement.
Note

See 11.7 for discussion of why the question of reliance can be an issue in contract-related disputes.

21.5.6. Particular case: "Collateral" lost profits.

The exclusion of consequential damages means that:

  1. if a party harmed by another party's breach of the Con­tract, the harmed party will not be able to recover any profits from the harmed party's collateral business arrangements that were lost as a result of the breach; but
  2. the harmed party can recover its (proven) lost profits that were a direct and probable result of the breach, and thus that would constitute (what are sometimes called) "general" or "direct" damages.
Note

().  In some consequential-damages exclusions, "lost profits" — without the limitation to collateral business arrangements — are listed as specific examples of excluded damages. But in Biotronik (N.Y. 2014), New York's highest court, after reviewing case law, held that — on the facts of the particular case — "lost profits were the direct and probable result of a breach of the parties' agreement and thus constitute general damages" and thus were not barred by a contract's limitation-of-liability clause. Biotronik A.G. v. Conor Medsystems Ireland, Ltd., 22 N.Y.3d 799, 801-02, 11 N.E.3d 676, 988 N.Y.S.2d 527 (2014) (emphasis added); see also Glenn D. West, Consequential Damages Redux: An Updated Study of the Ubiquitous and Problematic "Excluded Losses" Provision in Private Company Acquisition Agreements, 70 Bus. Lawyer 971, 992 (Weil.com 2015); Thomas H. Warren, W. Jason Allman & Andrew D. Morris, Top Ten Consequential Damages Waiver Language Provisions to Consider (2012).

Some other courts have issued similar rulings. For example: In Sweet Additions (11th Cir. 2025), the court held that an exclusion of incidental- and consequential damages, including "lost profit," did not apply to "lost profits and the costs of substitute products to the extent that those damages are direct and otherwise satisfy the provision’s total cap on recoverable damages." See Sweet Additions Ingredient Processors, LLC v. Meelunie America, Inc., 139 F.4th 1217, 1128-29 (11th Cir. 2025) (vacating and remanding $1.4 million judgment in favor of buyer of tapioca powder against supplier; see also Reid Hospital & Health Care Services, Inc. v. Conifer Revenue Cycle Solutions, LLC, 8 F.4th 642, 644 (7th Cir. 2021) (reversing summary judgment): A consequential-damages exclusion didn't apply — the contract in suit was for revenue collection, and the revenue lost due to breach "would have been the direct and expected result of Conifer’s failures to collect and process that revenue as required under the contract"; Tractebel Energy Mktg., Inc. v. AEP Power Mktg., Inc., 487 F.3d 89, 109-110 (2d Cir. 2007) (reversing judgment, after bench trial, denying plaintiff its lost profits).

Tangentially: In Endless River (6th Cir. 2025), a trial court granted JMOL for the defendant, vacating a jury verdict of $18.3 million in favor of the plaintiff: The court ruled that the plaintiff's claim for lost profits was barred by the contract's exclusion of consequential damages, "including but not limited to loss of good will and lost profits or revenue" (capitalization normalized). (The trial court noted that "[t[he parties recognize" that the applicable law, in that case Illinois, distinguished between lost profits when claimed as consequential damages versus when claimed as direct damages.)

On appeal, the Sixth Circuit declined even to address the lost-profits exclusion question: in an unpublished decision, the panel said it hadn't been convinced that the testimony of the plaintiff's damages expert — which had been the only damages evidence offered by the plaintiff — amounted to a measurement of lost profits. The court nevertheless affirmed the JMOL on the alternative ground that the plaintiff's damages testimony lacked relevance and reliability; the panel made it clear that it would have reversed the trial judge's Daubert ruling, which had allowed the expert testimony. See Endless River Techs. LLC v. TransUnion LLC, No. 1:18 CV 936, slip op. at 6 (N.D. Ohio Jan. 3, 2023) (granting JMOL to defendant), aff'd on alternative grounds, No. 23-3087, No. 23-3087, slip op. at 2, 10-11 n.3, and 16-17 (6th Cir. Jan.  Ohio 2023).

21.5.7. Inclusion of general liability-limitation Protocol

Protocol 21.18 (general provisions for limitations of liability) is incorporated by reference.

Note

Incorporation by reference is explained at Protocol 3.7.

21.5.8. Additional notes

21.5.8.1. Some economics of consequential-damages exclusions

In Severn Peanut (4th Cir. 2015), applying North Carolina law, the court explained some facts of life to customers that negotiate services contracts containing consequential-damages exclusions. This took place in a case where:

  • While doing an $8,400 job, a fumigation company had improperly applied a dangerous pesticide to a peanut dome owned by the plaintiff — this led to "fire, an explosion, loss of approximately 20,000,000 pounds of peanuts, loss of business, and various cleanup costs"; the plaintiff's total losses amounted to some $19 million.
  • The peanut company (and its insurer) filed suit against the fumigation company, but the trial court granted summary judgment in favor of the fumigation company because the company's contract excluded consequential damages.

The appeals court affirmed, explaining:

[Customers] faced with consequential damages limitations in contracts have two ways to protect themselves.

First, they may purchase outside insurance to cover the consequential [sic] risks of a contractual breach [by the supplier],

and second, they may attempt to bargain for greater protection against breach from their contractual partner.

Severn [the plaintiff] apparently did take the former precaution — it has recovered over $19 million in insurance proceeds from a company whose own business involves the contractual allocation of risk.

But it did not take the latter one, and there is no inequity in our declining to rewrite its contractual bargain now. Severn Peanut Co. v. Industrial Fumigant Co., 807 F.3d 88, 92 (4th Cir. 2015) (affirming summary judgment in favor of service provider that had caused millions of dollars to its customer's facility) (formatting altered).

21.5.8.2. Consequential damages can be big

Consequential damages can be grossly disproportionate to the value of the underlying contract. Example: In 2024, the notorious Crowdstrike outage — caused by an error in an update to CrowdStrike's cybersecurity software — caused millions of computer systems around the world to crash, with estimated economic damage of some USD $10 billion, including cancellation of thousands of scheduled airline flights. Reportedly, CrowdStrike's license agreement limited customers' remedies to a refund of fees paid, but many big customers, such as Delta Airlines, weren't accepting that, and notified CrowdStrike that it should prepare for litigation.

Students: Just skim the rest of this section's examples.

Example: Noted practitioner-commentator Glenn West has observed:

In 1984, an Atlantic City casino entered into a contract with a construction manager respecting the casino’s renovation. The construction manager was to be paid a $600,000 fee for its construction management services. In breach of the agreement, completion of construction was delayed by several months. As a result, the casino was unable to open on time and lost profits, ultimately determined by an arbitration panel to be in the amount of [$14.5 million]. There was no consequential damages waiver in the contract at issue in this case. Glenn D. West, Consequential Damages Redux: An Updated Study of the Ubiquitous and Problematic "Excluded Losses" Provision in Private Company Acquisition Agreements, 70 Bus. Lawyer 971, 984 (Weil.com 2015) (formatting altered, footnote omitted).

Example: In Australia, an opthmalmologist, a Dr. Kitchen, wrongfully terminated his service agreement with an eye clinic. The service agreement didn't include an exclusion of consequential damages. The Supreme Court of Queensland held him held liable for the clinic's lost profits and other amounts, in the total sum of more than AUD $10 million. See Vision Eye Institute Ltd v Kitchen, [2015] QSC 66, discussed in Jodie Burger and Viva Paxton, Australia: A stitch in time saves nine: How excluding consequential loss could save you millions (Mondaq.com 2015).

Example: In Ohio, a contractor agreed to gut and remodel a building for use as a neighborhood bar. The contractor didn’t do so by the agreed completion date — which caused the customer, a would-be bar owner, to miss the November-December holiday season. The court agreed with the bar owner that the contractor’s conduct had been "reckless" — and that caused the breach to fall within an explicit carve-out from the contract’s exclusion of consequential damages. As a result, the court affirmed an award of the bar owner’s lost profits. See Bakhshi v. Baarlaer, 2021 Ohio 13, No. 28767, slip op. ¶¶ 68-69 (Ohio App. 2021).

Example: From a corporate press release: A Taiwan company, TSMC, manufactures computer chips. It recently learned that "a batch of photoresist [a light-sensitive material used in 'etching' circuits onto chips] from a chemical supplier contained a specific component which [sic] was abnormally treated, creating a foreign polymer in the photoresist." BOTTOM LINE: "This incident is expected to reduce Q1 revenue by about US$550 million …."

Example: Here's a dated but famous example from 1999: A botched software implementation at Hershey caused it to be unable to deliver some $100 million of Hershey's Kisses for Halloween — the biggest candy "season" of the year. See, e.g., Thomas Wailgum, 10 Famous ERP Disasters, Dustups and Disappointments (ComputerWorld.com 2009).

Now imagine that you were the supplier that provided the software to Hershey, or that provided the photoresist to the chip manufacturer: How would you like to have to litigate which damages were "direct" and which were "consequential"?

21.5.8.3. Consequential-damages claims can complicate litigation

Students: Read the IBM example below, then just skim the rest of this section.

Discerning the difference between excluded consequential damages and recoverable "general" damages can sometimes be difficult; courts are often forced to parse sometimes-needlessly complex contract language and lawyer arguments to determine which is which.

Classifying particular types of damages as consequential or "direct" — a poor choice of names, IMHO — might be a very subjective exercise. Example: Consider an Indiana appellate court's 2018 decision in the long-running Indiana v. IBM litigation — in a second trial (on remand) over a failed computer-system acquisition, the trial judge held that:

–  IBM had to pay for a replacement computer system that the state acquired after IBM was fired, known as the "Hybrid" system — even though the Hybrid system was an upgrade from the system that IBM had agreed to build; and

–  The additional cost of the upgrade, said the trial judge, was properly classified as direct [sic] damages resulting from IBM's breach — and thus was subject to an agreed cap of $125 million — and not as consequential damages, which would have been subject to a much-lower cap of $3 million.

The trial judge's decision was affirmed on appeal. See IBM v. Indiana, 112 N.E.3d 1088, 1100-01 (Ind. App. 2018), summarily aff'd, 138 N.E.3d 255 (Ind. 2019).

But: Dissenting on the upgrade-as-direct-damages issue, a state supreme court judge argued unsuccessfully that:

[I]t was not IBM's breach but the State's decision to switch to the different, more expensive Hybrid system that caused the State to incur these additional expenses. The State's additional, Hybrid-related costs are at most consequential damages, not direct damages. 138 N.E.3d 255 at 261 (Slaughter, J., dissenting in part, concurring in part)

Students: You can just skim the rest of this section.

Example: In a (debatable) ruling, the New Hampshire supreme court affirmed a trial-court holding that a customer's cost of recreating lost data, necessitated by its outsourcer's alleged mistakes that caused the loss of the data, were "consequential" damages and therefore not recoverable because of an exclusion clause in the contract. See Mentis Sciences, Inc., v. Pittsburgh Networks, LLC, 243 A.3d 1223 (N.H. 2020).

(Less debatably, the court came out the same way on the customer's claim for damages for its inability to bid on certain government contracts due to the unavailability of the lost data.)

21.5.8.4. Pro tip: Use a damages cap instead?

Some experienced practictioners (including me) believe that a more-sensible approach will sometimes be to do the following:

  • not bother with an exclusion of consequential damages, because of the proof difficulties summarized above; and
  • instead, agree to a damages cap (see 21.18), so as to cut the Gordian knot — or to be like Indiana Jones in the streets of Cairo:

21.5.8.5. Reasons not to include a "laundry list" of exclusions

Some drafters like to include a detailed "laundry list" of highly-specific categories of excluded damages, such as the examples below.

My usual practice is to provide such a laundry list only cautiously and selectively, because doing so generally entails the drafter's figuratively crossing his- or her fingers —

  1. that courts will interpret the laundry list as the drafter hoped; and
  2. that in drafting the list, the drafter won't inadvertently omit one or more categories of damages that later proves important. (Relatedly: See also the discussion of the doctrine of ejusdem generis at 20.25.)

The following list of categories of damages to be excluded have been compiled from various agreement forms, but the list should be reviewed carefully, as some could be a bad idea in particular circumstances:

  • incidental damages — which are defined in sections 2-710 (seller's incidental damages) and 2-715 (buyer's consequential damages) of the Uniform Commercial Code;
  • punitive, exemplary, or special damages — which normally would not be available in a pure breach-of-contract case but might be available under other theories, for example in tort;
  • indirect damages;
  • breach of statutory duty;
  • business interruption;
  • loss of business or of business opportunity;
  • loss of competitive advantage;
  • loss of data;
  • loss of privacy;
  • loss of confidentiality [Editorial comment: This exclusion would normally be a really bad idea, at least from the perspective of a party disclosing confidential information];
  • loss of goodwill;
  • loss of investment;
  • loss of product;
  • loss of production;
  • loss of profits from collateral business arrangements;
  • loss of cost savings;
  • loss of use;
  • loss of revenue;
  • wasted expenditure;
  • reduced value of stocks, bonds, goods, commodities, or other assets.

For a summary of cases addressing such "laundry lists" in U.S., English, and Australian courts, see a 2015 article by noted scholar-practitioner Glenn West. See Glenn D. West, Consequential Damages Redux: An Updated Study of the Ubiquitous and Problematic "Excluded Losses" Provision in Private Company Acquisition Agreements, 70 Bus. Lawyer 971, 987-91 (Weil.com 2015).

Concerning wasted expenditure, see the 2022 English case of Soteria Insurance v IBM UK — which seems to have been a sad tale of an IT project gone sideways — where the court of appeal held that an contract's exclusion of "loss of profit, revenue, [and] savings" did not protect IBM from being held liable for its customer's "wasted expenditure" resulting from IBM's wrongful repudiation of the contract. Soteria Ins. Ltd. v. IBM UK Ltd., [2022] EWCA Civ 440, ¶ 2, summarized in Edward Lucas, A good day for wasted expenditure (JDSupra.com 2022). ]

21.5.8.6. Caution: Unconscionability of an exclusion?

Courts will sometimes hold that exclusions of consequential damages are "unconscionable." Indeed, UCC § 2-719(3) specifically says:

Consequential damages may be limited or excluded unless the limitation or exclusion is unconscionable.

Limitation of consequential damages for injury to the person in the case of consumer goods is prima facie unconscionable

but limitation of damages where the loss is commercial is not.

(Extra paragraphing added.)

Example: Procura (2019): This lawsuit involved a failed project to install computer software. A federal district court in Minnesota refused to give effect (at least initially) to a consequential-damages exclusion that benefited the vendor, because the court deemed the exclusion to be unconscionable. See Prairie River Home Care, Inc. v. Procura, LLC, No. 17-5121 (D. Minn. Jul. 10, 2019) (denying motion to dismiss claim for consequential damages).

21.5.8.7. Origins: The influence of Hadley v. Baxendale

This Protocol essentially follows the rule in the landmark 1854 English case of Hadley v. Baxendale (the "corn mill crankshaft case"). Hadley has been much remarked on over the decades; the opinion and its progeny are still relied on in American courts and likely studied by most if not all American law students. In Hadley:

–  A corn mill in Gloucester utilized a steam engine to clean and grind corn.

–  The steam engine's crankshaft broke.

–  The mill owners were informed that to have a new crankshaft made, they would have to ship the broken shaft to a manufacturer in Greenwich so that the new one could be made to the same dimensions, using the broken one as a pattern.

–  The mill owners shipped off the broken crankshaft, but the carrier was five days late in delivering the broken crankshaft to the manufacturer.

The corn mill's owners sued the carrier for, among other things:

  • the profits that the corn mill would have earned during the mill's extra "down time" caused by the carrier's delay in shipping the broken crankshaft; and
  • the wages that the corn mill's owners had to pay their idle employees during that extra down time.

In an opinion by Sir Edward Hall Alderson, Baron of the Exchequer (i.e., a judge of an English commercial court), the Hadley court reasoned as follows:

Now we think the proper rule is such as the present is this:

Where two parties have made a contract which one of them has broken, the damages which the other party ought to receive in respect of such breach of contract should be such as may fairly and reasonably be considered either arising[:]

  • naturally, i.e., according to the usual course of things, from such breach of contract itself, or
  • such as may reasonably be supposed to have been[:]
    • in the contemplation of both parties,
    • at the time they made the contract,
    • as the probable result of the breach of it.

Now, if the special circumstances under which the contract was actually made were communicated by the plaintiffs to the defendants, and thus known to both parties, [then] the damages resulting from the breach of such a contract, which they would reasonably contemplate, would be the amount of injury which would ordinarily follow from a breach of contract under these special circumstances so known and communicated.

But, on the other hand, if these special circumstances were wholly unknown to the party breaking the contract, [then] he, at the most, could only be supposed to have had in his contemplation the amount of injury which would arise generally, and in the great multitude of cases not affected by any special circumstances, from such a breach of contract.

For such loss would neither have flowed naturally from the breach of this contract in the great multitude of such cases occurring under ordinary circumstances, nor were the special circumstances, which, perhaps, would have made it a reasonable and natural consequence of such breach of contract, communicated to or known by the defendants. … See Hadley v. Baxendale, [1854] EWHC Exch J70 (formatting lightly edited for readability).

Some American courts have tried reformulating the Hadley rule, as discussed at 21.5.8.10, but this Protocol sticks to the traditional Hadley formulation.

21.5.8.8. The Restatement simply looks at foreseeability

On the subject of consequential damages, the Restatement (Second) of Contracts uses types of foreseeability to differentiate between general damages and consequential damages.

First are general damages, which, to be recoverable, must have been foreseeable to others generally:

Loss that results from a breach in the ordinary course of events is foreseeable as the probable result of the breach.

Such loss is sometimes said to be the "natural" result of the breach, in the sense that its occurrence accords with the common experience of ordinary persons. …

The damages recoverable for such loss that results in the ordinary course of events are sometimes called "general" damages. Restatement (Second) of Contracts § 351, "Unforeseeability And Related Limitations On Damages," comment b (citations omitted, emphasis and extra paragraphing added).

Next, are so-called consequential damages, namely uncommon or out-of-the-ordinary damages that nevertheless, at the time the parties entered into the contract, were foreseeable by the breaching party due to special circumstances and thus would be recoverable unless excluded:

If loss results other than in the ordinary course of events, there can be no recovery for it unless it was foreseeable by the party in breach because of special circumstances that he had reason to know when he made the contract. …

The damages recoverable for loss that results other than in the ordinary course of events* are sometimes called "special" or "consequential" damages.

These terms are often misleading, however, and it is not necessary to distinguish between "general" and "special" or "consequential" damages for the purpose of the rule stated in this Section. Id. (ditto).

21.5.8.9. Study aid: A consequential-damages flow chart

Study suggestion: Hand-copy the flow chart below, because research has shown that handwritten notes help with both comprehension and retention.

21.5.8.10. Some courts have tried to redefine "consequential damages"

Some American courts have tried different ways of defining consequential damages, but it's not clear that these redefinitions are helpful.

Example: The Eleventh Circuit remarked that "[t]he key distinction between direct damages and consequential damages is that the former compensate for the value of the promised performance, while the latter compensate for additional losses incurred as a result of the breach." AcryliCon USA, LLC v. Silikal GmbH, 985 F.3d 1350, 1369 (11th Cir. 2021) (summarizing Georgia law; emphasis added).

Example: In a similar vein, the Fourth Circuit ventured that "[c]onsequential or special damages for breach of contract …. are distinguished from general damages, which are based on the value of the performance itself, not on the value of some consequence that performance may produce." Severn Peanut Co. v. Industrial Fumigant Co., 807 F.3d 88, 90-91 (4th Cir. 2015) (cleaned up, emphasis added). Accord: Mentis Sciences, Inc., v. PIttsburgh Networks, LLC, 243 A.3d 1223, 1228 (N.H. 2020).

This distinction seems unhelpful, though: Arguably, "the value of the performance itself" is the value of the consequences to be produced — no more and no less. As Harvard Business School professor Theodore Levitt famously put it:

People don't want to buy a quarter-inch drill. They want a quarter-inch hole! Quoted in Clayton M. Christensen, Scott Cook and Taddy Hall, What Customers Want from Your Products (HBS.edu 2006).

Similar thoughts had been expressed previously, e.g., "When you buy a razor, you buy a smooth chin—but you could wear a beard." Quoted in No One Wants a Drill. What They Want Is the Hole (QuoteInvestigator.com 2019).

Perhaps the focus of the value of the performance would be more useful if it were phrased as the market value of the performance itself, i.e., the value that others, not in the plaintiff's particular circumstances, would theoretically pay for the performance.

Example: The Supreme Court of Texas espoused a variation on the Hadley approach, where the court held that:

Direct damages are the necessary and usual result of the defendant's wrongful act; they flow naturally and necessarily from the wrong. …

Consequential damages, on the other hand, result naturally, but not necessarily. El Paso Marketing, L.P. v. Wolf Hollow I, L.P., 383 S.W.3d 138, 144 (Tex. 2012) (cleaned up, formatting altered), quoting Arthur Andersen & Co. v. Perry Equip. Corp., 945 S.W.2d 812, 816 (Tex. 1997).

For cases decided under Texas law, the state supreme court's test thus replaces Hadley's "usual course of things" with "necessary and usual."

It's unclear, though, how helpful the Texas court's reformulation would be to trial counsel hoping to prove (or refute) a case, or to a jury seeking to distinguish recoverable from unrecoverable damages.

21.5.8.11. "Consequential damages" isn't the best name

I wish (but I'm not holding my breath) that the legal community could agree to rename "consequential damages" as something like "atypical damages" — both are clunky, but at least the latter one conveys the essence of the concept: While unforeseeable damages are never recoverable, it's possible for damages to be foreseeable in one of two different ways:

  • because, in the ordinary course without any special circumstances, reasonable people would have foreseen the damages possibility; and/or
  • because, at the time that the parties entered into the contract, the defendant had some other reason to foresee such damages; as the Texas supreme court held: "When one party has given notice of the consequences of breach at the time of contracting, no further inquiry into the foreseeability of those consequences is required"; Signature Indus'l Servs., LLC v. Int'l Paper Co., 638 S.W.3d 179, 192 n.8 (Tex. 2022).

And of course, if neither of the above conditions is shown to be true, then the damages simply aren't recoverable, period (at least under U.S. law). See id. at 184 (reversing court of appeals and rendering judgment against plaintiff because "legally insufficient evidence supported the award of consequential damages").

21.6. Corroborating Evidence Definition

21.6.1. Applicability

When this Protocol is agreed to, all concerned follow it in any situation where a party is required (by the Con­tract or the law) to provide corroborating evidence for an assertion.

21.6.2. Rule of reason

Whether the asserting party has provided sufficient corroboration is governed by (what courts refer to as) a "rule of reason," with each case being decided on its own facts.

Note

This specific language is adapted from a federal-court case, which in turn is based on the Supreme Court precedent that's discussed at 21.6.3.4. See TransWeb v. 3M Innov. Prop., 812 F.3d 1295, 1301 (Fed. Cir. 2016), citing Washburn & Moen Mfg. Co. v. Beat ‘Em All Barbed-Wire Co., 143 U.S. 275, 284 (1892) (known as The Barbed Wire Patent case).

21.6.3. Additional notes

21.6.3.1. Introduction

In some lawsuits, the outcome can turn on "swearing matches" in which the judge and/or jury must decide which witness's testimony they believe. The law, however, has long recognized that if a witness has a stake in the outcome — known as an "interested" witness — then his- or her testimony might be unreliable.

That's why, for certain important matters, the law requires that such testimony must be supported by corroborating evidence. The corroboration requirement takes into account that interested witnesses might "describe [their] actions in an unjustifiably self-serving manner …. The purpose of corroboration [is] to prevent fraud, by providing independent confirmation of the [witness's] testimony." Sandt Technology, Ltd. v. Resco Metal & Plastics Corp., 264 F.3d 1344, 1350 (Fed. Cir. 2001) (affirming relevant part of summary judgment; as a matter of law, inventor provided sufficient corroboration of date of invention) (cleaned up). ]

21.6.3.2. Why require corroboration (sometimes)?

Courts recognize that human beings are far from perfect in perceiving and remembering events:

  • We have active imaginations.
  • We sometimes "catch" only part of what we see and hear.
  • At times we misunderstand what they do see or hear.
  • We often jump to conclusions before it's appropriate.
  • And our stories can mutate in the retelling, especially with the passage of time.

Example: In a Ninth Circuit age-discrimination decision, an IRS employee was fired for having engaged in unauthorized access to information about people she knew. The employee claimed that she was fired because of her age — but the only evidence the employee produced was her own statement about things that a manager had allegedly said. Affirming summary judgment against the employee, the Ninth Circuit held that "uncorroborated and self-serving testimony" was not enough to establish a genuine issue of material fact about whether her firing had been based on pretextual reasons. Opara v. Yellen, 57 F.4th 709, 726 (9th Cir. 2023) (affirming summary judgment).

21.6.3.3. Some real-life examples

Here are a few more real-life examples of flawed human memory; all but the Beatles story below are adapted from a 2004 essay of mine:

Example: Did the Beatles play twice at Shea Stadium? Bob Smeaton, the director of "The Beatles Anthology" series, recounted an episode in which George Harrison was convinced that the Beatles had played just one 1966 concert at Shea Stadium, not two — even after being shown film footage that proved otherwise:

“George says, ‘We didn’t play Shea Stadium twice,’” Smeaton said. “I said, ‘George, you did.’ He says, ‘Look, Bob, I was in the band; you weren’t.’ I says, ‘George, I’ve got the footage.’ So we showed him, and George says, ‘You know what? I’m still convinced we didn’t play Shea Stadium again in ’66.’” Ben Sisario, How the Beatles Got Their Hooks Into Gen X and Never Let Go, N.Y. Times, Nov. 26, 2025, p.C1 (NYTimes.com).

Example: The imagined red beret: In 1972, during "The Troubles" in Northern Ireland, David Tereshchuk, then a junior TV journalist, was caught up in a protest that unexpectedly turned violent. British paratroopers suddenly fired on the mostly-Catholic crowd — killing 14 of them. The incident became known as Bloody Sunday.

Writing decades later, Tereshchuk recounted that "One recollection is stronger than any other – a soldier in a red beret, down on one knee, leveling his self-loading rifle toward me and shooting." (Emphasis added.) But, Tereshchuk goes on, "as all the photographs clearly demonstrate, he was wearing a helmet." Tereshchuk concluded that "I was simply wrong." Tereshchuk ends his essay with this: "And yet, even with an indisputable set of photographs in front of me, I close my eyes and still see a red beret." David Tereshchuk, An Unreliable Witness, NY Times Magazine, Jan. 28, 2001, p. 66 (emphasis added).

Example: My dad the (alleged) daredevil pilot: My late father was an Iowa farm boy turned Air Force fighter pilot who served in the Korean War. He seldom talked about the war itself — but he did tell of how, not long after his return, he flew a routine training mission that took him near his tiny home town, where he planned to spend the night with his parents. Dad said he made a pass over the town, waggled his wings, and headed for the airport in a nearby city.

After landing, Dad made his way to his folks' house and walked into town. Someone told him about all the excitement that had occurred earlier in the day: An unknown pilot had repeatedly buzzed the town, flying back and forth along the main street — so low that the plane went right under the telephone wires — scaring everyone half to death.

Dad had done no such thing (or at least so he said ….). But the other guy — who, if I remember Dad's tale correctly, had not even seen the event — was utterly convinced of it: In just half a day and one or two retellings, the story had mutated.

Example: The misremembered court opinion: When I was a new lawyer, a senior partner — one of the leading intellectual-property litigators in the U.S. — sent me to the firm's library to look for a particular court opinion. The case, he said, had involved A and B in a specific appeals court where years before the partner had been a judicial clerk; the court's holding, said the partner, had been such-and-such.

I searched and searched the case books. All I could find was a case involving Party A and Party C (not B), and the court's holding had been the exact opposite of what the partner had believed.

I reported this information back to the partner, showing him the court's opinion. His response was, in essence, "that's crazy, that's not the way the law is." But there was no mistaking it: The partner had remembered the case, not the way it actually turned out, but the way he thought it should have turned out.

Human psychology is just that way. Lawyers have to deal with that in every lawsuit. There can be no reasonable dispute about it.

21.6.3.4. The SCOTUS pedigree for requiring corroboration

The U.S. Supreme Court explained the need for corroboration of self-interested statements in a famous 19th-century case concerning a patent for a type of barbed wire:

We have now to deal with certain unpatented devices, claimed to be complete anticipations of this patent, the existence and use of which are proven only by oral testimony.

In view of the unsatisfactory character of such testimony, arising from

  • the forgetfulness of witnesses,
  • their liability to mistakes,
  • their proneness to recollect things as the party calling them would have them recollect them,
  • aside from the temptation to actual perjury,

courts have not only imposed upon defendants the burden of proving such devices, but have required that the proof shall be clear, satisfactory and beyond a reasonable doubt.

[Comment: Patent law in the U.S. now requires only "clear and convincing evidence" on this point, not proof "beyond a reasonable doubt."]

Witnesses whose memories are prodded by the eagerness of interested parties to elicit testimony favorable to themselves are not usually to be depended upon for accurate information. Washburn & Moen Mfg. Co. v. Beat ‘Em All Barbed-Wire Co., 143 U.S. 275, 284 (1892) (known as The Barbed Wire Patent case) (emphasis, extra paragraphing, and bullets added).

In modern terms, such claims must be established by "clear and convincing evidence" — see Protocol 20.11 — and not "beyond a reasonable doubt," which is the highest standard of proof, used in criminal cases. See generally Microsoft Corp. v. i4i Ltd. P'ship, 564 U.S. 91 (2011) (reaffirming requirement of clear and convincing evidence to prove facts supporting defense of patent invalidity).

21.6.3.5. What sorts of thing could qualify as corroboration?

Depending on the circumstances, corroborating evidence could include, for example (and not limited to):

  • contemporaneous documents such as emails and texts; and/or
  • testimony from witnesses who don't have a stake in the outcome.

21.7. Damages Caps General Provisions Protocol

21.7.1. Applicability of this Protocol

If parties agree to follow this Protocol, it will apply in any situation where a damages cap is agreed to in writing.

Note

().  Damages caps are quite common in contracts — especially contracts drafted by suppliers.

See 21.7.8.2 for sample language for various forms of damages cap.

A damages cap could be agreed to:

  • in the Con­tract itself; and/or
  • in some other document, possibly (for example) in a purchase order or statement of work under the Con­tract.

And a damages cap could be stated as:

  • fixed amount;
  • variable amount, perhaps changing over time or in different circumstances; and/or
  • computable amount, e.g., a multiple of some number such as a contract price.

21.7.2. Protected persons

Unless the damages cap itself clearly says otherwise, the cap will protect each party to the Con­tract and its Protected Group (defined at Protocol 14.4).

21.7.3. Covered forms of liability

Except as otherwise provided in this Protocol, an agreed damages cap will apply:

  1. to all forms of monetary recovery sought — including without limitation monetary awards of damages, costs, and/or attorney fees; and
  2. no matter what legal principle or other theory of liability is involved, including without limitation NEGLIGENCE and GROSS NEGLIGENCE.
Note

Bold-faced type and all-caps are used here to make these terms conspicuous, just in case the "express-negligence rule" in Texas and some other jurisdictions were to be held to apply, as discussed at 14.3.4.

21.7.4. Aggregate effect

Unless the Con­tract clearly states otherwise, a damages cap will limit the cumulative liability on the part of the specified party and its Protected Group together, for all claims against all of them together, over all time, and not per-person, per-project, or or per-claim.

21.7.5. Claims for set-off?

An agreed damages cap is to be applied before determining the effect of any applicable liability set-offs.

Note

().  Setoffs (or offsets) are discussed at subdivision 4.13.5 of Protocol 4.13 (payment terms).

An English court of appeal called this before-the-setoff rule the "commercial common sense" approach. See Topalsson GmbH v. Rolls-Royce Motor Cars Ltd., [2024] EWCA Civ 1330 at ¶¶ 22-20 (reversing trial-court judgment on that point).

Example: To illustrate the operation of this set-off section, consider the following hypothetical example:

  1. The Con­tract is hypothetically between "Alice" and "Bob" and states that Bob's liability to Alice is capped at $100.
  2. In a first lawsuit relating to the Con­tract, Alice wins a judgment against Bob for $70 in damages and $10 in attorney fees and costs.
  3. Bob's other party's appeals are unsuccessful, so Bob eventually pays Alice the $80 total liability amount.
  4. Later, in a different lawsuit relating to the Con­tract, Bob is found liable to Alice for $350; again, Bob's appeals are unsuccessful.
  5. So: Because of the agreed damages cap, Bob's liability to Alice in the second lawsuit is not $350, but $20 — that is, the difference between the $80 that Bob previously paid to Alice (as a result of the first lawsuit) and the $100 damages cap.

21.7.6. Exclusions from damages cap

Unless clearly agreed otherwise in writing, a damages cap does not limit any of the following:

  1. amounts to be paid under the Con­tract "in the ordinary course";
  2. amounts to be paid (if any) for: (a) defense against third-party claims, and/or (b) indemnity obligations;
  3. damages arising from intentional fraud (as opposed to fraud resulting from recklessness);
  4. damages for intentional or reckless breach of confidentiality obligations under the Con­tract, if any;
  5. damages for willful misconduct, as defined at Protocol 20.40;
  6. damages for death or other physical injury to an individual, in the case of consumer goods;
  7. awards of attorney fees; nor
  8. costs of court and/or of other proceedings (e.g., costs of arbitration if arbitration is agreed to).
Note

().  This is a cheap-insurance (see 8.31) provision, even though under the law it might not be necessary to state it explicitly. Damages caps — exclusion of amounts due: See, e.g., IHR Security, LLC v. Innovative Bus. Software, Inc., 441 S.W.3d 474, 479 (Tex. App.–El Paso 2014) (affirming, in part, summary judgment: limitation of liability in software license agreement "does not purport to limit IHR's liability in the event it breaches the License Agreement by refusing to pay for goods and services provided by IBS"); Fujitsu Services Ltd. v. IBM United Kingdom Ltd., [2014] EWHC 752 (TCC) ¶. 52 (2014) ("[t]he law of contract draws a clear distinction between a claim for payment of a debt and a claim for damages for breach of contract").

Subdivision 2: Caps on defense- and indemnity liability are very often a point of negotiation — but they could be made the subject of a separate cap, e.g., limiting a party's general liability to X (where X is some dollar amount) but limiting the party's liability for defense and indemnity to, say, 3X.

Subdivision 3: See the discussion at 21.7.8.3.

Subdivision 4 This affects reckless breaches of confidentiality obligations, not just intentional ones, in the interest of helping to deter "moral hazard."

Subdivision 6's exclusion is based on UCC § 2-719(3), which provides in part: "Limitation of consequential damages for injury to the person in the case of consumer goods is prima facie unconscionable …."

To similar effect is a U.S. statute dating back to 1936 concerning maritime liability, which prohibits "[t]he owner, master, manager, or agent of a vessel transporting passengers between ports in the United States, or between a port in the United States and a port in a foreign country [from contractually limiting liability] for personal injury or death caused by the negligence or fault of the owner or the owner’s employees or agents." 46 U.S.C. 30527(a); hat tip: Prof. John F. Coyle. ]

Subdivision 7: See Protocol 21.2 (attorney fees) and its commentary.

21.7.7. Other provisions incorporated

Protocol 21.18 (limitation of liability general provisions), is incorporated by reference into this Protocol.

Note

For an explanation of incorporation by reference, see Protocol 3.7.

21.7.8. Additional notes

21.7.8.1. Prelude: How are contract damages determined?

As a review of aspects of the first-year Contracts course in law school, here's a brief summary from a federal appeals court decision:

The goal of measuring damages for a breach-of-contract claim is to provide just compensation for any loss or damage actually sustained as a result of the breach.

[1]  The normal measure in such cases is the benefit of the bargain, which seeks to place the injured party in the economic position it would have been in had the contract been performed, i.e., expectancy damages.

[2]  Alternatively, a plaintiff may seek reliance damages, which are measured by the amount necessary to compensate that party for a loss already suffered.

Put another way, reliance damages seek to put the injured party in the position he would have been in had he not relied on the promise.

[2A]  Out-of-pocket reliance damages measure the difference between the value the buyer has paid and the value of what he has received.

Such damages include expenditures made by the aggrieved party in preparing to perform or in performance. National Oilwell Varco, L.P., v. Auto-Dril, Inc., 68 F.4th 206, 216-17 (5th Cir. 2023) (reversing and remanding summary judgment in relevant part; cleaned up, formatting edited) (King, J.).

21.7.8.2. Illustrative examples of damages-cap wording

Here are a few hypothetical examples of damages-cap provisions, written in terse language:

(a)  ABC's liability for breach is capped at 2X: This means that ABC would not be liable for — and no other party may seek — more than two times the amount paid or payable to ABC.

Caution: A damages cap could limits recovery to amounts paid — which could be minimal or even nothing. That happened in an Eighth Circuit case: A customer paid a software provider an initial fee and was supposed to pay more in the future. After the customer unilaterally terminated the contract (because reasons), the provider sued for the unpaid future payments — but the court granted summary judgment for the customer because the contract limited the rejected each party's liability to the fees paid, not those amount payable. See Baldwin Hacket & Meeks, Inc. v. Early Warning Services, LLC, No. 23-3502, slip op. at 4 (8th Cir. Aug. 29, 2025) (affirming summary judgment in favor of customer).

(b)  ABC's liability for breach is capped at 3X on a 12-month lookback: This means that ABC would not be liable for, and no other party may seek, more than three times the amount that ABC was paid (or was owed), in the 12-month period just before the earliest event giving rise to the liability, regardless whether the other party knew or should have known that the event had occurred. (Hat tip: Tommy Porter at the redline.net lawyers-only site; login required.)

(c)  Damages cap: 2X the total contract value: This means that neither party would be liable, and no other party may seek, more than two times the total amount to be paid under the contract, for example, in fees for services or payment for goods.

21.7.8.3. Carve-outs for fraud, willful misconduct, etc.?

Damages-cap provisions sometimes include carve-outs for gross negligence; willful misconduct; recklessness; and fraud — that way, if the plaintiff can show that the defendant engaged in carved-out (mis)conduct, then the cap's upper limit on a damage award would not apply, and the plaintiff could recover damages in excess of the cap.

Example: Fraud carve-out: In the aftermath of a software-development project gone pear-shaped, a supplier, EDS (a UK-based unit of HP) found itself settling a contract dispute with British Sky Broadcasting for some USD $460 million — more than four times the value of the original contract — because an English judge found that an EDS executive had lied to Sky about EDS's capabilities, and thus the contract's limitation of EDS's liability to £30 million was lifted because of an express carve-out for fraud in the limitation. See the extended discussion of this and similar cases at 20.34.6.7.

Example: Recklessness carve-out: In Ohio's Bakhshi bar-owner case:

  • A contractor agreed to gut and remodel a building for use as a neighborhood bar.
  • The contractor failed to do so by the agreed completion date.
  • This caused the customer, a would-be bar owner, to miss the November-December holiday season.
  • The court agreed with the bar owner that the contractor’s conduct had been “reckless” — causing the breach to fall within a stated carve-out from the contract’s exclusion of consequential damages.

The court affirmed an award of the bar owner’s lost profits. See Bakhshi v. Baarlaer, 2021 Ohio 13 ¶¶ 68-69 (Ohio App. Jan. 8, 2021).

NOTE: Delaware law distinguishes between "intentional fraud," sometimes stated as "deliberate fraud," versus reckless misrepresentation — the latter doesn't require proof of an intent to deceive. See Express Scripts, Inc. v. Bracket Holdings Corp., 248 A.3d 824, 825 (Del. 2021) (reversing and remanding trial court judgment on jury verdict).

Example: On a motion to dismiss, a Facebook user's claim that the company had engaged in intentional misconduct was part of the court's rationale for rejecting the company's assertion that its terms of service precluded the user's claim. See Doe v. Meta Platforms, Inc., No. 22-cv-03580, slip op. at part V.A (N.D. Cal. Sept. 7, 2023) (denying that part of defendant's motion to dismiss).

21.7.8.4. Caution: Watch out for "gross negligence" carve-outs

A carve-out for "gross negligence" could leave it up to a jury to decide whether a defendant had engaged in gross negligence, as opposed to ordinary negligence. This happened in California's Epochal Enterprises case:

  • A commercial landlord leased dilapidated greenhouse buildings to a tenant.
  • The landlord knew that the buildings might have asbestos but didn't tell the tenant.
  • After asbestos was found in one of the leased buildings, the tenant stopped paying rent, vacated the premises, and sued the landlord.
  • The jury awarded damages to the tenant — but citing an exclusion clause in the lease, a trial court granted "JNOV" for the landlord notwithstanding the verdict.

The court of appeals reversed the JNOV, holding that the jury was presumed to have found that the landlord had acted with gross negligence — which was the subject of a carve-out in the lease's limitation of liability. See Epochal Enterprises, Inc. v. LF Encinitas Properties, LLC, 99 Cal. App. 5th 44, 317 Cal. Rptr. 3d 573 (2024).

21.7.8.5. How might parties negotiate liability limitations?

When a supplier and a customer are each represented in a contract negotiation by an experienced professional, the negotiators' conversation about limitations of liability might go something like this:

  • Customer: Hey, Supplier, why should we agree to limit your liability? Aren't you willing to stand behind your product (or service)?
  • Supplier: Of course we are. But what we're providing is a product (or service). We're not selling you an insurance policy, and our pricing reflects that fact. AND: Please keep in mind that even if we were providing insurance, every insurance policy ever written has limits on what the carrier will pay out in case of a loss.

For a useful diagrammatic view of these basic party positions, see the 2017 PowerPoint slides provided by Chicago lawyers Brian Heidelberger and Monique (Nikki) Bhargava. Brian Heidelberger and Monique (Nikki) Bhargava, Negotiating Limitation of Liability Provisions in Agency-Client Agreements (Winston.com 2017).

21.7.8.6. Different damages caps for different purposes?

A contract could provide for different damages caps for:

  • different breaches or types of breach (see 21.7.8.7 immediately below for some possibilities);
  • different time periods, for example, different damages caps for before and after X months after the effective date of the Con­tract (see 21.7.8.8 below for some possibilities); and/or
  • different geographical areas.
21.7.8.7. Pro tip: Try risk-by-risk limitations

Contract drafters can often speed up discussions of liability limitations by breaking up generic boilerplate language into more-concrete statements of risks that are of particular concern, which the parties can focus on more readily.

One technique that works well is to list specific categories of risk and, for each category, state what if any liability limits are agreed. The categories of risk could include, for example, the following:

  • Personal injury
  • Tangible damage to property (not including erasure, corruption, etc., of information stored in tangible media where the media are not otherwise damaged)
  • Erasure, corruption, etc., of stored information that could have been avoided or mitigated by reasonable back-ups
  • Other erasure, corruption, etc., of stored information
  • Cost of repair or replacement
  • Lost profits from any of the above
  • Lost revenue from any of the above
  • Indemnity obligations
  • Infringement of another party's IP rights (including without limitation rights in confidential information)
  • Willful, tortious destruction of property (including without limitation intentional and wrongful erasure or corruption of computer programs or -data)

To be sure, if the non-drafting party won't care much about the limitation of liability anyway, then including such detailed limitation language could actually hinder the overall negotiations.

But remember, by hypothesis we're talking about contract negotiations in which the limitation language is indeed going to be carefully negotiated — in which case this kind of systematic approach will almost always make sense.

21.7.8.8. Pro tip: Negotiate variable limitations of liability?

Exclusions of consequential damages (see 21.5) and damage-cap amounts (see 21.7) don't necessarily have to be carved in stone for all time. The parties could easily agree to vary them, either as time passed or as circumstances changed.

Example: Suppose that —

  • A software vendor is negotiating an enterprise license agreement with a new customer for a mature software package.
  • The customer has successfully completed a pilot project, but it hasn't rolled out the software for enterprise-wide production use.
  • Knowing how tricky a production roll-out can sometimes be, the customer is concerned about the vendor's insistence on excluding all 'consequential' damages, whatever that really means. (See the commentary to 21.5: Consequential Damages Exclusion Protocol for a review of the difficulty of determining what constitutes "consequential damages.")

Our vendor might try offering:

  • to waive the consequential-damages exclusion entirely during, say, the customer's first three months of production use of the software,
  • subject to an agreed dollar cap on the vendor's aggregate liability for all damages — which might be a higher dollar amount than at other times, as discussed below.

This approach could make the customer more comfortable that the vendor is 'standing behind its software' during the roll-out phase.

In theory, certainly, the vendor would be exposed to additional liability risk during those first three months. But the business risk might be eminently worth taking.

Remember, we're assuming that the software is mature, that is, most of its significant bugs have already been corrected. This means that the vendor might be willing to take on the additional theoretical risk — which in any case would go away after three months — in order to help close the sale.

Example: As another illustration, perhaps such a vendor could agree that the damages cap would be, say:

  • 4X for any damages that arise during, say, the first three months of the relationship, or possibly until a stated milestone has been achieved;
  • 3X during the nine months thereafter; and
  • 2X thereafter.

In the 4X / 3X / 2X language, X could be defined: as a stated fixed sum; as the amount of the customer's aggregate spend under the contract in the past 12 months, 18 months, etc.; in any other convenient way.

The details in the above examples aren't important; the point is that sometimes 'standard' limitation-of-liability language is too broad to allow the parties to specify what they really need.

Negotiators might have more success if they drilled down into the language.

21.7.8.9. Excluding incidental damages isn't a great idea

Contracting parties might not want to agree to exclude "incidental damages," which are generally defined as reasonable expenses reasonably incurred by a party incident to a breach or delay by another party.

See generally UCC § 2-710 (seller's incidental damages) and UCC § 2-715(1) (buyer's incidental damages). Of course, UCC Article 2 applies only to sales of goods, and will not apply at all in non-U.S. countries. Still, the same basic concepts of incidental damages might also apply to sales of services, etc.

It has been observed that: "Although incidental damages are often included in the laundry list of waived damages, it is often advisable to remove them [from the list of exclusions] since the right to recover incidental damages may encourage mitigation efforts." Thomas H. Warren, W. Jason Allman, & Andrew D. Morris, Top Ten Consequential Damages Waiver Language Provisions to Consider (ACC.com 2012).

21.8. Damages Proof Requirement Protocol

21.9. Equitable Relief Disclaimer Protocol

When agreed to, this Protocol will apply whenever a party breaches the Con­tract.

21.9.1. EXCLUSIVE REMEDY

  1. When this Protocol is part of the Con­tract, the EXCLUSIVE REMEDY available to A for a breach of the Con­tract by B will be for A to recover damages — that is, monetary compensation — from B as provided by law.
  2. For that reason:
    1. A will not ask a court (or other body) to enter a restraining order, injunction, or other equitable relief against B or B's affiliates; and
    2. A WAIVES any such relief.
Note

().  This sort of provision is apparently seen in some performance contracts between movie studios and acting talent. See, e.g., Ryan Linn, Controlling the Spotlight: Promotional Clauses in Performance Contracts (2025).

The terms EXCLUSIVE REMEDY and WAIVES are in bold-faced all-caps for conspicuousness (see 8.1).

Subdivision 2.a — "A will not ask ….": See 21.18.6.

21.10. Equitable Relief Stipulation Protocol

21.10.1. Stipulation

If A materially breaches the Con­tract in a way that is irreparably harming the interests of B or threatens to do so; and/or if such a breach appears imminent, THEN: B will be entitled to a preliminary injunction (or similar equitable relief) against A, upon a proper showing as required by applicable law.

Note

().  This Protocol says only that the other party will be entitled to seek injunctive relief, not that the other party will be entitled to the relief sought.

To be sure: Drafters of confidentiality agreements and similar contracts sometimes include flat statements that the drafting party is entitled to injunctive relief.

– Such clauses, however, are often obnoxiously overreaching.

–  Moreover, courts will often ignore such peremptory statements, as discussed at 8.18 — and possibly even find them unconscionable.

Example: In a California case, an employment agreement stated that the company, but not the employee, was entitled to injunctive relief, and without posting a bond (on the subject of a bond waiver, see Protocol 21.4). An appeals court regarded this as a factor in the agreement's unconscionability. See Silva v. Cross Country Healthcare, Inc., No. B337435, slip op. at 22-23 (Cal. App. Jun. 13, 2025) (affirming trial court’s order finding employer’s arbitration agreement unenforceable and denying employer’s motion to compel arbitration) (citing cases).

It's a non-trivial task for a claimant to prove that it would be irreparably injured — and the claimant might not succeed in carrying its burden of proof. Example: In one federal case, a patent owner obtained a preliminary injunction against a would-be competitor. The undisputed facts, though, showed that even in the best-case scenario, the competitor would not be ready to launch its product until several years after the patent had expired. The Federal Circuit overturned the preliminary injunction, on grounds that the patent owner had failed to provide "non-speculative evidence" that it would be irreparably harmed by the competitor's actions. See Incyte Corp. v. Sun Pharm. Indus., Ltd., No. 25-1162, slip op. at 5-6 (Fed. Cir. May 7, 2025).

So: A potential future target of an injunction request might not want to stipulate to the fact, as opposed to just the possibility, of irreparable harm. Such a stipulation could well absolve the claimant from what might otherwise be a significant challenge of proof.

Consequently, if you're reviewing a contract, and you're asked to agree to language in this category, then you should pay careful attention to the exact wording, because it could end up significantly disadvantaging your client.

(See also the commentary to Protocol 21.4 (bond waivers), which likewise can be dangerous to a party that might have to defend against a motion for preliminary injunction or similar equitable relief.)

21.10.2. Equitable relief: Additional notes

21.10.2.1. Legal background: The plaintiff's burden of proof

We're talking here about two main categories of relief from a court: An order for specific performance, or an injunction. Each of those things is, in essence, a court order that the other party must do or not do something — on pain of punishment for contempt of court. (Some forms of such relief might have different labels, e.g., a restraining order.)

If a party were to stipulate to such relief — or stipulate to the existence of "irreparable injury" — then that stipulation likely would waive away a major part of what would otherwise be a significant burden of proof for the drafting party.

In the U.S., any party asking for such a court order generally must show — not merely allege — that, among other things, the party has suffered or is likely to suffer "irreparable injury" that could not be adequately compensated by a monetary award.

The Supreme Court of the United States explained how this works:

According to well-established principles of equity, a plaintiff seeking a permanent injunction must satisfy a four-factor test before a court may grant such relief.

A plaintiff must demonstrate:

(1) that it has suffered an irreparable injury;

(2) that remedies available at law, such as monetary damages, are inadequate to compensate for that injury;

(3) that, considering the balance of hardships between the plaintiff and defendant, a remedy in equity is warranted; and

(4) that the public interest would not be disserved by a permanent injunction.

The decision to grant or deny permanent injunctive relief is an act of equitable discretion by the district court, reviewable on appeal for abuse of discretion. eBay Inc. v. MercExchange, L.L.C., 547 U.S. 388, 391 (2006) (describing traditional four-factor test in context of patent-infringement injunctions) (citations omitted, emphasis and extra paragraphing added). For a useful catalog of things that might qualify as irreparable injury – if proved – see Paige Bartholomew, Commercial Division Judge Reaffirms "Most Critical" Element for Injunctive Relief: Irreparable Harm (JDSupra 2020); scroll down to its list of bullet points.

21.10.2.2. Caution: Contractual stipulations to irreparable harm have been enforced

Example: Then-chancellor Strine of the Delaware chancery court (later chief justice of the state's supreme court) relied in part on a similar clause in granting a four-month injunction against one company's hostile takeover bid targeting another company:

In Delaware, parties can agree contractually on the existence of requisite elements of a compulsory remedy, such as the existence of irreparable harm in the event of a party's breach, and, in keeping with the contractarian nature of Delaware corporate law, this court has held that such a stipulation is typically sufficient to demonstrate irreparable harm. Martin Marietta Materials, Inc v. Vulcan Materials Co., 56 A.3d 1072, 1144-45 (Del. Ch.), aff'd, 68 A.3d 1208 (Del. 2012) (en banc) (footnotes with extensive citations omitted).

21.10.2.3. See also: Bond waivers

Relatedly, see Protocol 21.4 (bond waivers) and its commentary.

21.11. Escalation (External) Protocol

21.11.1. When to escalate

For any disagreement relating to the Con­tract: The parties will escalate the disagreement to a neutral advisor, as stated in this Rule, whenever any party reasonably asks — after they first escalate internally (unless otherwise agreed) in accordance with Protocol 3.4.

Note

().  Like internal escalation under Protocol 3.4, this Protocol aims to increase the chances of early settlement of disputes — and thus to help avoid costly litigation — by giving parties and their counsel a "sanity check" before positions harden and relationships suffer.

This Protocol's reasonableness requirement can serve as a guardrail against a wealthier party's attempts to bully another party by inappropriate demands for escalation (e.g., repetitive demands, or demands concerning trivial disagreements).

21.11.2. Selection of advisor

If the parties do not agree on a neutral advisor within a reasonable time, THEN: Either party is free to ask the American Arbitration Association ("AAA") (or other agreed source) to appoint one.

Note

().  The American Arbitration Association ("AAA"), or some other agreed third party, can appoint a neutral for escalation if the parties' can't come to agreement; see also 21.1.10 for other arbitration administrators that might help with appointing a neutral.

The parties could consider agreeing in advance to a list of acceptable neutrals; in some cases, the parties might even want to agree to engage a specific neutral at the time they enter into the Con­tract — this could be along the general lines of an expert engineering dispute resolution board, as is sometimes used in complex construction projects.

21.11.3. Exchange of documents?

Preferably, the parties will exchange relevant documents as provided in Protocol 3.4.2 (internal escalation) — but this Protocol does not require either party to agree to do so.

21.11.4. Exchange of first settlement proposals

  1. Each party will provide the other party with one or more written, first-round proposals to resolve the dispute, on a schedule set by the neutral.
  2. Each such first-round proposal by a party is just a suggestion for further discussion — it is not a firm offer by that party to settle on the proposed terms unless the proposal itself clearly says otherwise.
Note

().  Subdivision 1 is phrased as a requirement, not a suggestion, because:

  • the requirement isn't onerous: as a practical matter, an uncooperative party could simply provide an outlandish first-round proposal; and
  • a requirement could be useful to help overcome party inertia.

    Two experienced arbitrators in New York City point out that successive rounds of settlement proposals can nudge each party into assessing whether the other party's proposal might look better to the neutral. This can nudge each party into (re)considering the reasonableness of that party's position — and thus, in turn, improve the odds of settlement. See Edna Sussman and Erin Gleason, Everyone Can Be a Winner in Baseball Arbitration: History and Practical Guidance (sussmanadr.com), in N.Y. State Bar Association, New York Dispute Resolution Lawyer, Spring 2019, at 30, archived at https://perma.cc/QW76-C7BB.

    The contents of each party's proposal would of course be up to that party, but could include, for example, terms for allocating (i) fees and expenses charged by the neutral; and/or (ii) the parties' respective attorney fees.

    Each party could provide alternative proposals to try to advance the prospect of settlement. Example: Such an approach seems to have been used in a federal court case, involving an organization at MIT, where by agreement, the trial judge served as a baseball-style mediator [sic] who chose between the parties' final settlement offers. The court's opinion noted that: "Each side could submit two positions, but I encouraged counsel to limit its submission to one or two positions and instructed each side to submit the same number of positions. I would then adopt one of the positions." Brandt v. MIT Development Corp., 552 F. Supp. 2d 304 n.6 (D. Conn. 2008).

    A party could submit an "exploding" proposal that is deemed withdrawn at a stated time if not agreed to as part of the first round.

21.11.5. Exchange of final proposals

  1. Each party will provide the other party with one or more written, final-offer proposals, in the same general manner as the first-round proposal(s).
  2. Each party will also provide the neutral with a copy of the party's final-round proposal(s), if any.
  3. If a party does not provide any final-round proposal, THEN: The only consequence will be to limit the neutral's choice of a final proposal under § 21.11.10.
Note

().  This is likewise a mandatory requirement because If one party doesn't provide a final-offer proposal, the only consequence would be to limit the neutral's choices under § 21.11.10.

If no party submitted any final proposal at all, that'd amount to the parties' agreement not to escalate that particular disagreement under this Protocol (in which case the neutral would presumably send the parties a final invoice).

Subdivision 2: The parties' copying the neutral on their final-round proposals will help the neutral to get a sense of which party is being reasonable in its proposals; this will be of use later.

Caution: A possible alternative is known as "night baseball," in which the neutral isn't told what the parties are proposing, but simply states which party wins. DCT comment: My own thinking is that night baseball would be less-effective than giving the neutral the whole picture, so that the neutral can offer comments and suggestions about how to bridge the gap between the parties' settlement positions.

21.11.6. Video conference

  1. The neutral will schedule, convene, and preside at a video conference between the parties to address the dispute.
  2. The neutral will use reasonable discretion in deciding things such as scheduling; conference management; whether to allow recording of the video conference; and other administrative details, to the extent that the parties do not agree on them.
Note

().  If scheduling proved to be a problem, the neutral would have the final say on that point, as long as the neutral's decision wasn't unreasonable.

See also § 21.11.18 (privileged status of escalation discussions).

21.11.7. Senior-management participation?

  1. Each party will consider having someone from the party's senior management take part in the video conference with the neutral, to provide a possibly-broader perspective on the dispute.
  2. Subdivision 1 does not require either party to agree to senior-management participation.
  3. If a senior-management representative from A did not participate, that would not preclude B's representative from participating.
Note

().  A mini-trial to senior-management representatives might well be the most-effective approach to resolving the dispute. So said the head of litigation for a global Fortune 500 company, a seasoned trial lawyer, at a continuing legal education (CLE) panel discussion in Houston (which I moderated).

Why might senior management make a difference? As two Australian lawyers pointed out: "Bringing in senior management will focus the minds of the parties on the bottom line, and allows senior decision makers who are not caught up in the underlying dispute to approach the situation taking commercial reality into account." Faith Laube and Toby Blyth, Expert determination clauses in contracts — are they worth it? (MyBusiness.com.au), archived at https://perma.cc/T2FP-D9BZ.

21.11.8. Mini-trial presentations

At the video conference, the neutral will give each party a reasonable opportunity to do a brief, "closing argument" presentation concerning the dispute, in the same general manner as for a mini-trial.

Note

().  Each party would make a presentation during the video conference, in the style of a closing argument in a lawsuit, succinctly summarizing the party's position and any supporting evidence. But each party is free not to make a presentation, or for that matter not to participate in the video conference at all.

It's helpful for the proceeding to generally follow the mini-trial rules published by the International Institute for Conflict Prevention and Resolution ("CPR").

The neutral would decide whether to allow recording of the video conference if the parties disagreed on that point.

The neutral would allocate presentation time roughly equally between the parties.

The neutral would normally manage the conference in roughly the same way that a federal judge might manage a closing argument.

(The neutral will presumably rein in a party whose presentations — after reasonable warning and opportunity to cure — are repetitive or unproductive.)

Usually, the video conference wouldn't continue for more than roughly 90 minutes. (The neutral and the parties could of course agree otherwise.)

21.11.9. Neutral comments

The neutral is welcome to express some or all of the neutral's thoughts about any of the parties' proposals (1) to both parties together, and/or (2)  to each party separately, subject generally to the ethical guidelines applicable in mediations.

Note

().  The neutral's comments could include suggestions for bridging any remaining gap(s) between the parties. That's because this Protocol uses a hybrid of two different approaches to ex parte communications: (1) In mediation, "shuttle diplomacy" is an often-used feature, with the mediator trying to broker a deal. (2) In contrast, in litigation and conventional arbitration, it's almost always considered improper and unfair for the judge or arbitrator to engage in private, "ex parte" communications with one of the parties to the dispute.

Moreover, § 21.11.11 allows, after the neutral chooses the winning proposal, for the neutral to do something akin to a "mediator's proposal" in mediation.

True: Mediator proposals are regarded skeptically by some mediators. But the neutral will already have chosen one of the party proposals and announced that choice to the parties, along with a brief explanation. So a neutral's proposal at that point seems likely to present fewer potential dangers. See generally, e.g., Martin Quinn, Mediator’s proposals: God’s gift to mediation, or a betrayal? (JAMSADR.com 2014) (discussing pros and cons); Wynne S. Carvill, The Danger of Mediator's Proposals (JAMSADR.com 2020).

21.11.10. Neutral's choice

  1. Promptly after the parties have concluded their presentations — and in any case before the neutral adjourns the video conference — the neutral will:
    1. choose one of the parties' final proposals that the neutral regards as "closest to the pin" (to use a golf term) of an optimal resolution of the disagreement — without modification;
    2. tell the parties which final proposal has been chosen — that proposal is referred to below as the "winning proposal"; and
    3. briefly explain to the parties the reason(s) for the choice.
  2. If only one party submitted only one final proposal, then that proposal automatically becomes the winning proposal.
  3. The party submitting the winning proposal is referred to below as the "winning party," with the other party being the "losing party."
  4. The neutral will proceed as stated in this § 21.11.10 even if only one party participated in the video conference after agreeing to the scheduling of the video conference (or at least being duly notified of it).

21.11.11. Neutral's recommendation?

  1. After the neutral chooses the winning proposal and so informs the parties, the neutral is welcome, in the neutral's sole discretion, to provide the parties — together — with the neutral's recommendation as to what the neutral then believes would be an appropriate resolution to the dispute.
  2. If the parties agree to the neutral's recommended resolution, THEN:
    1. That resolution automatically becomes a final, binding arbitration award by consent, enforceable in the same manner as arbitration awards generally.
    2. The neutral will confirm the parties' agreement in the quick after-conference email that the neutral sends under § 21.11.13.
Note

().  Subdivision 1: See the comment at § 21.11.9 about the neutral's offering opinions.

Subdivision 2.a: There seems to have been only a couple of reported court cases in which a party sought to judicially enforce an arbitration award that was entered by consent of the parties — in both cases, the courts confirmed the awards. See Transocean Offshore Gulf of Guinea VII Ltd. v. Erin Energy Corp., No. H-17-2623, slip op. part V.A (S.D. Tex. Mar. 12, 2018) (granting motion to confirm consent award), following Albtelecom SH.A v. UNIFI Commc'ns, Inc., No. 16 Civ. 9001 (S.D.N.Y. May 30, 2017) (same); see generally Laura A. Kaster, Consent or Agreed Awards and the New York Convention—What Is the Status? (2018).

Subdivision 2.a: See § 21.1.18 for discussion of judicial enforcement of arbitration awards.

21.11.12. Binding outcome?

  1. Before adjourning the video conference, the neutral will ask the losing party whether that party accepts the winning proposal.
  2. The losing party is free to defer answering.
  3. If the losing party does accept the winning proposal in writing — e.g., by email or text at the conclusion of the video conference — THEN:
    1. the winning proposal — in its entirety — automatically becomes an arbitration award, binding on all parties; and
    2. either party may seek to confirm and enforce the award in any court having jurisdiction.
Note

The losing party also has the right to confirm and enforce the winning proposal in case the winning party "pulls something" contrary to the award. (See also § 21.1.18 concerning arbitration confirmation and enforcement.)

21.11.13. Neutral's initial report

  1. As soon as possible after adjourning the video conference, the neutral will send both parties, by email, a short after-conference report that:
    1. states which was the winning proposal;
    2. omits any details of that proposal (other than as appropriate to identify the proposal) unless the parties agree otherwise;
    3. states whether the losing party accepted the winning proposal during the video conference (or the parties otherwise agreed to a resolution); and/or
    4. states whether the parties agreed to a resolution recommended by the neutral under § 21.11.11.
  2. To help streamline any subsequent court proceedings, the neutral's report is prima facie evidence about anything it says; no party asserts otherwise.
Note

Subdivision 1.c is intended as a guardrail, to try to block any "buyer's remorse" action on the part of a losing party that initially accepted the chosen proposal but then had second thoughts.

21.11.14. Opt out

  1. This § 21.11.14 will apply if the losing party doesn't agree in writing to accept the winning proposal (see § 21.11.12 above).
  2. The losing party is free to send a written rejection of the winning proposal to both the neutral and the winning party — but: If the losing party's written rejection is not received, by at least one of the winning party and the neutral, no later than the end of the day on the date two days after the adjournment of the video conference, THEN: The losing party has automatically accepted the winning proposal, with binding effect as stated in § 21.11.12 above.

21.11.15. Neutral's follow-up report

  1. This section will apply if:
    1. the losing party does not accept the winning proposal or the neutral's proposed resolution (if any); and
    2. the neutral has not otherwise heard, from both parties, that the parties have settled the dispute, on or before the date five business days after the adjournment of the video conference.
  2. In that situation: The neutral will expeditiously provides both parties with a brief follow-up written report that summarizes:
    1. the neutral's then-current reason(s) for choosing the winning proposal; and
    2. if applicable, the neutral's own recommendation for a resolution.
  3. The neutral's follow-up report can include, in the neutral's sole discretion:
    1. discussion of more topics than were discussed at the video conference or in the neutral's preiminary report under § 21.11.13; and/or
    2. a new recommendation for a resolution.
Note

Subdivision 3 allows for the possibility that the neutral might have further thoughts, or even change her mind, after the video conference. That might be unlikely to happen, but if it did, the neutral would likely make a new recommendation for a resolution — and presumably the parties would give it respectful consideration.

21.11.16. No other neutral power

This Protocol does not give the neutral any other power to decide the parties' dispute unless the parties clearly agree otherwise in writing.

Note

See the discussion in the arbitration Protocol at § 21.1.16.

21.11.17. Admissibility of neutral's report

  1. If litigation later ensues concerning the dispute (or, if agreed, arbitration), the neutral's follow-up report under § 21.11.15 will be admissible in evidence in its entirety, including all recommendations for resolution proposed by the neutral, if any — and neither party will oppose admission if the other party asks.
  2. The neutral's follow-up report will have the same status as a report of a court-appointed expert under Rule 706 of the Federal Rules of Evidence.
  3. Each party is free to ask for admission of only designated excerpts from the neutral's follow-up report, in essentially the same manner as designation of deposition excerpts under Rule 32 of the (U.S.) Federal Rules of Civil Procedure.
Note

This aims to provide each party with additional motivation to be reasonable about settlement positions if the neutral provides a written report under § 21.11.15 above: If the parties don't settle, and the winning party wants to introduce the neutral's report, then the judge or jury or arbitrator will get to read what the neutral had to say. See generally J. Gregory Sidak, Court-Appointed Neutral Economic Experts, 9 J. Competition L. & Econ. 359 (2013).

21.11.18. Privileged status of discussions

To promote openness and candor in the escalation: Neither party will seek to introduce the escalation proceedings into evidence in other proceedings, e.g., litigation — other than the winning party's final proposal and the neutral's written report — except as permitted by Rule 408 of the [U.S.] Federal Rules of Evidence, and the interpretations of that rule by U.S. federal courts; this is the case even if Rule 408 would not otherwise govern.

21.11.19. Confidentiality designations

  1. This section will apply if, as part of the escalation, one or more other parties (each, a "Discloser") provides another party (each, a "Recipient") with access to the Discloser's nonpublic information that is timely designated in writing as confidential.
  2. The Recipient will treat that Discloser information as the Discloser's Confidential Information — and, if applicable, as a trade secret of the Discloser — as provided in Protocol 5.3, subject to the limitations and exclusions stated there.

21.11.20. Party expense responsibility

Unless clearly agreed otherwise:

  1. Each party is responsible for that party's own escalation-related expenses, without reimbursement from any other party to the Con­tract.
  2. Subdivision 1 does not mean that a party cannot be reimbursed under some other arrangement, e.g., from an insurance policy.

21.11.21. Neutral's fees and expenses

  1. The parties will timely pay — in equal shares — all fees and expenses invoiced to them by the neutral, and/or by an appointing organization, in connection with:
    1. the escalation itself; and
    2. any aftermath, for example, if the neutral were to be asked — by anyone — or compelled to produce documents or to testify in subsequent litigation or arbitration relating to the dispute.
  2. If A does not timely pay its share of neutral-related expenses under subdivision 1, THEN:
    1. B will pay the nonpaying party's unpaid share; and
    2. A will immediately reimburse B for what B paid for A's unpaid share, together with: (1) interest at the maximum rate allowed by law, plus (2) any reasonable attorney fees incurred by B in connection with (i) getting A to pay its share, and/or (ii) seeking repayment.

21.11.22. Neutral immunity

For reasons similar to judicial and arbitrator immunity: Neither party will ever sue the neutral (for defamation or otherwise), nor otherwise takes any action against the neutral, concerning any statements made, by anyone, in the escalation proceedings itself and/or in any aftermath proceedings (including without limitation in the neutral's written report).

21.11.23. Unsuccessful disqualification attempts

  1. Nothing that the neutral says or does in a proceeding under this Protocol will be grounds for disqualifying the neutral from serving in the neutral role unless a party shows — by clear and convincing evidence — that the neutral is incurably and unfairly biased against that party or for the other party.
  2. Given the nature of the escalation process of this Protocol: If the neutral offers provisional views about the merits of the case, that will not serve as evidence of the neutral's bias.
  3. If a party — referred to as the "movant" — tries to disqualify the neutral for bias, but the movant does not clear the bar set out in subdivisions 1 and 2 above, THEN:
    1. the movant will pay the other party's attorney fees for the disqualification proceedings — and those of the neutral, if any — at all stages including appeals; and
    2. the movant will not assert that the neutral must recuse him- or herself primarily because of the failed disqualification attempt.
Note

().  This section is intended as a "Do Not Enter" against a known type of cynical delaying tactic in arbitration: A party thinks it's going to lose on the merits, so it runs to the nearest courthouse to try to disqualify the arbitrator for bias — typically citing "reasons" that might well amount to just so much [expletive]. Example: DCT comment: That seems to be the case when fired CNN anchor Chris Cuomo sought to get a JAMS arbitrator disqualified on grounds that, more than 20 years before as a law-firm lawyer, the arbitrator had handled one small matter for CNN and the arbitrator's then-firm (the Paul Hastings law firm) had represented CNN in more matters. The trial court rebuffed Cuomo's attempt; the appellate division unanimously affirmed, awarding CNN its costs. See Cuomo v. JAMS, Inc., No. 2024-02157 (N.Y. App. Div. Oct. 7, 2025) (affirming summary judgment in favor of JAMS).

Subdivision 2: All judges, arbitrators, jurors, and other neutrals are human. As a case goes along, they inevitably tend to form (provisional) views about the merits — they're simply expected to withhold judgment until all the evidence is in. So, it normally wouldn't be evidence of bias if a neutral's provisional views of the merits happened to favor one party or another.

Subdivision 3.a's fee-shifting provision is intended to get each party to stop and think before deciding to try to disqualify the neutral.

21.11.24. Survival of this Protocol

This Rule will remain in effect, for already-arisen disputes, even if, in one way or another, the Con­tract comes to an end.

Note

Concerning survival of terms generally, see the Survival of Certain Terms Protocol (18.1).

21.11.25. Additional notes

21.11.25.1. Last-offer arbitration can create powerful incentives to be reasonable.

This Protocol borrows key, compromise-promoting features from last-offer arbitration as used in baseball salary disputes. Such arbitration very often results in early settlement, because each party has a powerful incentive to be reasonable:

  • The arbitrators must choose one of final proposals put forward by the parties; and
  • An unreasonable proposal would likely cause the arbitrators to choose the other party's proposal, even if just as the lesser of two evils.

As a baseball writer once put it, baseball arbitration is "designed to produce a settlement, not a verdict." Thomas Gorman, The Arbitration Process – the Basics, in Baseball Prospectus (2005) (http://perma.cc/CZR4-9XC7) (emphasis added).

In the same vein:

  • In a federal court case in Connnecticut, involving an organization at MIT, the trial judge, acting as a "mediator" by agreement, remarked that "each side therefore had an incentive to set forth a position that was as reasonable as possible." Brandt v. MIT Development Corp., 552 F. Supp. 2d 304 n.6 (D. Conn. 2008).
  • And in another case, a Missouri appellate court noted that final-offer arbitration "is designed to motivate each party to negotiate in good faith and attempt to compromise in order to create a final offer that the arbitrator will select as most reasonable." Kagan v. Master Home Products Ltd., 193 S.W.3d 401, 406 & n.5 (Mo. App. 2006) (citation omitted).
21.11.25.2. Another precedent: Valuation appraisals

The Delaware chancery court described another dispute-resolution procedure that's sometimes seen in valuation disputes:

That procedure calls for the parties to agree on an appraiser to value the plaintiff's share of the transaction proceeds.

If the two sides can't agree … then each side picks an appraiser.

After each appraiser prepares a valuation, the appraisers meet and attempt to reach agreement on a valuation.

If the appraisers can't agree … then the two appraisers pick a third appraiser.

That [third] appraiser chooses one of the two valuations, which establishes the amount due. * * *

[The agreed procedure stated that the third appraiser] "shall select from the determinations of the two [appraisers] the determination that it believes to be most correct, which shall then become final, conclusive and binding on the parties hereto." Paul v. Rockport Group, LLC, No. 2018-0907-JTL, slip op. (Del. Ch. Jan. 9, 2024) (Laster, V.C., granting summary judgment in favor of plaintiff) (emphasis and extra paragraphing added).

21.11.25.3. Last-offer arbitration has a great real‑world settlement track record …

Historical data suggest that final-offer arbitration works very, very well to promote settlement of baseball salary disputes: If I'm reading the statistics correctly, there were a total of approximately 1,000 arbitration-eligible players for the years between 2018 and 2022; in those years, the settlement rate ranged between 89% and 96% — with 100% settlement in 2022. See Arbitration Tracker 2018, 2019, 2020, 2021, and 2022. (For the years 2023 through 2025, the results aren't set out in table form for convenient analysis, but those results seem to have exhibited similar success rates.)]

True: Baseball salary disputes involve a comparatively-narrow range of relevant factors. But read on:

21.11.25.4. … and not just in baseball

Here are some non-baseball examples where baseball-style "final offer" arbitration has been used to resolve disputes:

–  Protective orders in litigation, as set forth in (what's known as) Susman Agreement No. 7 (or 9, or 11, depending on the list you read), pioneered by the Susman Godfrey firm;

–  market price of green anode coke, see Rain CII Carbon, LLC v. ConocoPhillips Co., 674 F. 3d 469 (5th Cir. 2012);

–  determining fair-market rent in future lease periods, see California Union Square L.P v. Saks & Co. LLC, 71 Cal. App. 5th 136, 139 (2021);

–  amounts due under an asset purchase agreement, see Moore v. Omnicare, Inc., 118 P. 3d 141 (Idaho 2005);

–  binding mediation [sic] of a lawsuit, see Bowers v. Raymond J. Lucia Companies, Inc., 142 Cal. Rptr. 3d 64, 206 Cal. App. 4th 724, 729-30 (2012) (by agreement, mediator selected one of parties' respective settlement final offers);

–  claims under a natural gas retail service alliance agreement, where the court said that "the parties have tied the hands of the arbitrators, requiring them to select without changing among remedies presented, i.e., the best of a bad lot," Scana Energy Marketing, Inc. v. Cobb Energy Mgmt. Corp., 576 S.E.2d 548, 553 (Ga. App. 2002);

–  disputes involving video-programming distributors, under an FCC-approved merger agreement, see United States v. AT&T, Inc., 916 F.3d 1029, 1034-35 (D.C. Cir. 2019) (refers to provision in Comcast-NBC Universal merger agreement allowing distributors to submit disputes to baseball arbitration, and to Turner Broadcasting's offer to do the same with approximately 1,000 distributors); see also Suppl. Stmt. of United States in Support of Entry of Final Judgment, United States v. Comcast Corp., No. 1:11-cv-00106, at 3 n.4 (D.D.C. Aug. 5, 2011), cited in United States v. Comcast Corp., 808 F. Supp. 2d 145, 149 n.2 (D.D.C. 2011);

–  compensation in the Deepwater Horizon litigation, see In re Deepwater Horizon, 785 F.3d 986, 989 & n.1 (5th Cir. 2015) (determination of compensation under settlement agreement after Gulf of Mexico drilling-rig disaster);

–  royalties for an invention, see Kagan v. Master Home Products Ltd., 193 S.W.3d 401 (Mo. App. 2006);

–  price of shares subject to right of first offer, see OneBeacon Ins. Co. v. Plant Insulation Co., No. C 14-01200 (N.D. Cal. Aug. 18, 2014);

–  amount of "cover" damages to be paid by subcontractor that failed to perform as agreed, see Clayco, Inc. v. Food Safety Group, Inc., No. 4:20-mc-00739 (E.D. Mo. Mar. 8, 2021).

DCT note: Back when I was a partner in a large IP-litigation firm, three times in one year — for three different lawsuits, for three different clients — the parties agreed to my proposal that we use baseball-style arbitration; in each case, the parties promptly settled.

And an anecdote from a friend: At a conference in the same time frame, Jackie Daunt [who gave me permission to use her name], then a partner at a leading Silicon Valley firm (and now retired), told me that she routinely put baseball-arbitration clauses into her clients' contracts. One of those clients got into a dispute, causing the client's CEO to exclaim angrily, "G**d*mn it, Jackie, that means I have to be reasonable!" Jackie responded, "Exactly." And of course the dispute was settled — sooner than it might otherwise have been.

(In a recent email to me, Jackie remarked that baseball arbitration "penalized someone who was unreasonable and, as you highlighted in your story, led to faster, cheaper and fairer resolutions of disputes. Probably the very reason it never became popular.")

21.11.25.5. What sorts of dispute might qualify for escalation?

Prime candidates for escalation to a neutral advisor would be any actual controversy, relating to the Con­tract, concerning any of the following:

  1. numbers, for example, how much one party is to pay another; and/or
  2. imprecise requirements under the Con­tract — for example, what would constitute reasonable efforts in a given situation. disagreement relating to the Con­tract.

(The mention of an "actual controversy" has in mind the requirements of the Declaratory Judgment Act, discussed at 21.24. That's because it might not be reasonable to demand costly escalation to a neutral if there's no actual controversy to escalate.)

Here are some examples of disagreements that would almost surely qualify for escalation under this Protocol:

  1. the amount(s) of one or more sums that, under the Con­tract, one party is to pay to another party — because disputes about numbers are the classic use case of the baseball-arbitration aspect of this Protocol, as discussed at 21.11.25.3.
  2. whether particular action (as yet untaken) would satisfy an imprecise requirement under the Con­tract such as, for example, a requirement to make "reasonable efforts" or "commercially-reasonable efforts" (see Protocol 9.2) or "best efforts" (see Protocol 9.1);
  3. whether a party has "good reason" to take or not take a particular action, where the Con­tract allows the party to take or not take the action if good reason exists.

Of course, the parties could always agree to follow this Protocol for other disagreements.

21.12. Forum Selection Protocol

21.12.1. Definition: Agreed Forum

This Protocol presupposes that the Con­tract clearly specifies one or more particular forums for litigation, each, an "Agreed Forum." (The Con­tract could do this explicitly, or clearly-but-implicitly.)

Note

().  It's not uncommon for a contract to provide that litigation "arising from" the contract — and perhaps even litigation merely "relating to" the contract — may be brought, or even must be brought and maintained, in a specified forum such as a particular state or city, or even (in the case of New York City) a particular borough. Such a forum-selection provision might or might not be enforceable — and it might not be the best idea anyway — as discussed in the reading beginning at 21.12.9 below.

To choose a forum, drafters could consider permissive language such as the following: "Any dispute arising out this Agreement may be brought in any state- and/or federal court having jurisdiction in [LOCATION], as stated in more detail in the LCP26 Forum Selection Protocol."

Caution: See the commentary at 21.12.9.2 and 21.12.9.3 for potentially-dangerous wording choices.

Caution: Even proposing a forum-selection clause to a party with superior bargaining power could be "poking a bear," as discussed at 21.12.9.18.

21.12.2. Definition: Action

For purposes of this Protocol:

  1. the term "Action" refers to a lawsuit or other form of contested action in any dispute arising out of the Con­tract; and
  2. the term "sue" refers to bringing an Action.
Note

The choice of "arising out of the Con­tract" is intentional because the quoted term is more limited than "relating to the Con­tract," and it might well not be a great idea to lock in a forum for future disputes that are related only distantly to the contract.

Example: Ride-sharing company Uber was sued by a contractor for both breach of contract and misappropriation of trade secrets. Uber asked the court to transfer the case to transferred to Brazil, because the contract (for a pilot project) was with Uber's Brazilian subsidiary and included a forum-selection provision for Brazil. A Massachusetts trial court granted Uber's motion to transfer for the contract-related claims, but not for the statutory trade-secret claims. See Zemcar Inc. v. Uber Techs., Inc., No. 2484CV01525-BLS2, slip op. at 17 (Mass. Super. Jan. 29, 2025) (denying, in relevant part, motion to dismiss trade-secret claim because of forum selection clause; footnote omitted, emphasis and extra paragraphing added).

Example: In another Massachusetts case, a federal court held that a contract's forum-selection clause didn't apply to claims asserting common-law and statutory rights. The clause read as follows:

Any action or proceeding seeking to enforce any provision of, or based on any right arising out of, this Agreement must be exclusively brought against either of the Parties in the courts of the State of New Jersey. Moxie Apparel, Inc. v. Lakhani, No. 1:24-cv-12711, slip op. (D. Mass. May 19, 2025) (denying defendant's motion to dismiss).

21.12.3. Any Action may take place in an Agreed Forum

A can sue B in the Agreed Forum — regardless where B happens to be geographically located —

  1. to the extent the law doesn't prohibit doing so;
  2. but not if the Con­tract (if any) requires arbitration for the matter in question.
Note

().  Subdivision 1: The law might regulate forum-selection provisions in particular circumstances. Example: Under a California statute (Cal. Code Civ. Pro. § 116.225), "An agreement … establishing a forum outside of California for an action arising from an offer or provision of goods, services, property, or extensions of credit primarily for personal, family, or household purposes that is otherwise within the jurisdiction of a small claims court of this state is contrary to public policy and is void and unenforceable." (Emphasis added; hat tip: Sean Hogle at the lawyer forum redline..)

Concerning the interplay between forum-selection provisions and arbitration provisions, see § 21.12.7 below, as well as § 21.12.9.7 in Protocol 21.1 (arbitration).

21.12.4. Non-exclusive unless clearly agreed otherwise

A may sue B in a forum other than the Agreed Forum — and vice versa, of course — unless the Con­tract clearly says otherwise (for example, by stating that the Agreed Forum is exclusive).

21.12.5. Restrictions if exclusivity clearly agreed

  1. The parties will follow this section if the Con­tract does clearly say that an Agreed Forum is exclusive.
  2. A will not sue B in any forum other than the Agreed Forum.
  3. If A does sue B in the Agreed Forum, THEN: B will not try to transfer the Action elsewhere.
Note

().  Subdivision 1: See the discussion at § 21.12.6 immediately below of consequences for violating an exclusive-forum provision.

Subdivision 3 is adapted from a suggestion at the lawyers-only redline.net forum. Motions to transfer are fairly-common in U.S. federal-court litigation, typically "[f]or the convenience of parties and witnesses," under the governing federal statute, 28 U.S.C. § 1404; such motions are generally left to the discretion of the trial-court judge. See, e.g., In re Samsung Electronics Co., 2 F.4th 1371, 1379 (Fed. Cir. 2021) (granting petition for writ of mandamus to compel transfer).

21.12.6. Consequences of violation

  1. The parties will follow this section if A takes action inconsistent with the exclusivity of an Agreed Forum under § 21.12.5, AND B successfully contests A's action.
  2. A will reimburse B for B's reasonable attorney fees and court costs in contesting A's action.
  3. And even if A ends up being the prevailing party in the proceeding as a whole:
    1. B need not repay A for that that reimbursement,
    2. nor need B reimburse A for A's own relevant attorney fees in that contest proceeding.
Note

().  Subdivision 2 takes on "the conventional wisdom among judges[, which] has long been that money damages are not available for breach of a forum selection clause." John F. Coyle and Tanya J. Monestier, Limits on Damages for Breach of a Forum Selection Clause, Abstract (SSRN.com 2025).

But: Delaware's Vice Chancellor Laster held that "[a] party protected by a forum selection clause can reasonably expect [1] not to have to litigate a foreclosed forum and [2] not to incur expenses doing so. An injunction or dismissal enforcing the forum selection clause fulfills the first expectation. A damages award measured by the expenses incurred in the foreclosed forum fulfills the second expectation." Namdar v. Fried, No. 2024-0535, part II.B, slip op., text acc. nn.25-34 (Del. Ch. Jun. 6, 2025) (denying motion to dismiss claim for damages for breach of forum-selection clause) (Laster, V.C.) (bracketed numerals added).

21.12.7. Override by arbitration agreement, etc.

Even if the Con­tract designates an Agreed Forum, A doesn't sue B in the Agreed Forum if the Con­tract requires the particular dispute in question to be resolved by other means — such as, for example, by arbitration.

Note

As discussed at 21.12.9.8, there's a split in the circuits whether an explicit, exclusive forum-selection provision in a contract will override an arbitration provision in a prior- or "background" agreement.

21.12.8. Survival of this Protocol

In case of doubt: The parties continue to follow this Protocol even if the Con­tract is terminated or expires, and whether or not the Con­tract includes other survival provisions.

Note

Concerning survival clauses generally, see Protocol 18.1 and its commentary.

21.12.9. Additional notes

21.12.9.1. Legal background

In Atlantic Marine (2013), the (U.S.) Supreme Court explained that in the United States, federal courts will routinely enforce forum-selection clauses "unless extraordinary circumstances unrelated to the case clearly disfavor a transfer." Atlantic Marine Construction Co., Inc. v. United States District Court, 571 U.S. 49, 134 S. Ct. 568, 575, 187 L. Ed. 2d 487 (2013) (holding that transfer, not dismissal, was appropriate; emphasis added); see also The Bremen v. Zapata Off-Shore Co., 407 U.S. 1 (1972) (reversing and remanding Fifth Circuit decision; international contract's selection of London Court of Justice as exclusive forum was not unenforceable).

Earlier, the First Circuit had noted:

… a forum selection clause should be enforced unless the resisting party can show[:]

[i] that enforcement would be unreasonable and unjust, or

[ii] that the clause was invalid for such reasons as fraud or overreaching or

[iii] that enforcement would contravene a strong public policy of the forum in which suit is brought, whether declared by statute or by judicial decision. Rivera v. Centro Medico de Turabo, Inc., 575 F.3d 10, 18 (1st Cir. 2009) (affirming dismissal of action based on forum-selection clause; cleaned up, bracketed material and extra paragraphing added), in part quoting Bremen, 407 U.S. 1, 10, 15 (1972). See also, e.g., Lakeside Surfaces, Inc. v. Cambria Company, LLC, 16 F.4th 209 (6th Cir. 2021) (reversing and remanding dismissal of Michigan-filed lawsuit: Michigan Franchise Investment Law trumped forum-selection clause that specified Minnesota choice-of-forum clause).

Likewise, state courts in the U.S. generally honor forum-selection provisions; for example, in Paul Business Systems (Va. 1990), Virginia's supreme court explained that a forum-selection provision would be enforced "unless the party challenging enforcement establishes that such provisions are unfair or unreasonable, or are affected by fraud or unequal bargaining power." Paul Business Systems, Inc. v. Canon U.S.A., Inc., 97 S.E.2d 804, 807-08 (Va. 1990) (affirming dismissal of complaint) (emphasis added, extensive citations and internal quotation marks omitted).

21.12.9.2. Caution: Don't say "the courts of" a jurisdiction

It's not a good idea to say that the parties agree to have suits heard in the courts "of" the specified forum location. That's because a U.S. court might find that such language precluded the defendant from removing the suit from state court — the courts "of" the forum state — to federal court.

Example: This happened, for example, in a case where the Fifth Circuit affirmed a federal district court's remand of a removed case to state court in Houston — even though diversity of citizenship existed — because the contract's forum-selection clause required suits to be "brought before the district courts of Harris County, Texas[.]" Dynamic CRM Recruiting Solutions, L.L.C. v. UMA Educ., Inc., 31 F.4th 914 (5th Cir. 2022), esp. at 922 nn.27-32 (citing numerous cases). See also, e.g., Smart Comms. Collier Inc. v. Pope Cty. Sheriff’s Office, 5 F.4th 895 (8th Cir. 2021) (affirming dismissal of federal-court lawsuit because forum-selection clause required litigation in Arkansas state courts) (citing cases); Grand View PV Solar Two, LLC v. Helix Electric, Inc., 847 F.3d 255, 258 (5th Cir. 2017) (affirming remand to state court after removal); Doe 1 v. AOL, LLC, 552 F.3d 1077, 1081-82 (9th Cir. 2009) (per curiam).

21.12.9.3. Caution: What if there's no federal court there?

A contract required litigation to be in Linn County, Oregon. When one of the contracting parties sued the other one, the defendant removed the case to federal court. But as it happens, there's no federal courthouse located in that county. Consequently, said the Ninth Circuit, the federal trial court correctly remanded the case to state court. See City of Albany v. CH2M Hill, Inc., 924 F.3d 1306, 1307, 1308 (9th Cir. 2019) (affirming remand to state court).

Lesson: If you want your client (and the other side, of course) to be able to remove to federal court, be sure that your forum-selection clause refers to "the state- and federal courts having jurisdiction in" the specified place, versus "in" the specified place.

21.12.9.4. Caution: "shall be subject to" might mean exclusivity

In an English case:

  • A Hong Kong freight forwarder used its standard bill-of-lading form in accepting cargo for shipment from China to Venezuela.
  • The form provided in part that "[t]his Bill of Lading and any claim or dispute arising hereunder shall be subject to English law and the jurisdiction of the English High Court of Justice in London."

The UK Court of Appeal, after reviewing case law concerning similar language, held that the bill of lading's wording conferred exclusive jurisdiction on the English courts. See Hin-Pro International Logistics Limited v Compania Sud Americana De Vapores S.A. [2015] EWCA Civ 401 ¶¶ 4, 61-78 (emphasis added). (Hat tip: English lawyer Mark Anderson, who in his write-up makes additional observations about the case.).

21.12.9.5. Be careful what you wish for in an exclusive-forum clause

Asking for — or insisting on – a forum-selection clause might fall into the category of "be careful what you wish for," because the courts in the forum state might decide matters differently than what you expected. A Massachusetts company learned a painful lesson in that regard when some of its New York employees filed a lawsuit against the company, as discussed at 21.14.5.3.

21.12.9.6. Tactical disadvantage of an exclusive-forum clause?

An exclusive-forum clause might be tactically disadvantageous — consider this not-so-hypothetical example:

  • You're helping to negotiate a contract between "Ginger" and "Fred."
  • Your draft contract is a tough one; among other things, it contains an exclusive-jurisdiction forum clause that requires all litigation to be conducted in Ginger's home-court jurisdiction.
  • At some point after signing the contract, Ginger wants to seek a temporary restraining order or preliminary injunction against Fred. (That might be, for example, because Fred appeared to be violating a confidentiality clause requiring him to keep Ginger's information secret.)

In that situation, Ginger might well be better off tactically by suing Fred in Fred's own home jurisdiction, because:

  • In kicking off the lawsuit, it's likely that Ginger will be able to complete the necessary service of process on Fred more quickly in Fred's own "home court" than in Ginger's jurisdiction.
  • If Ginger must go to court to compel Fred to produce documents or witnesses, Fred would probably have a harder time resisting an order from a judge in Fred's own home jurisdiction.
  • Even if Ginger were successful in getting a court to issue an injunction affecting Fred, the injunction likely wouldn't take effect until it had been formally served on Fred, and that service of process might well be quicker and easier in Fred's home jurisdiction.
  • If Fred violated the injunction, Ginger probably would be able to haul him back more quickly into court for contempt proceedings in his own home jurisdiction.
  • BUT: By insisting on an exclusive-jurisdiction forum selection clause, Ginger might have precluded suing Fred in Fred's home jurisdiction.

Lesson: Ginger should think twice before insisting that Fred agree to exclusive jurisdiction in Ginger's home court.

21.12.9.7. An arbitration clause might have forum-selection implications

Some states' arbitration laws provide that agreement to arbitrate in the state constitutes consent to jurisdiction in the co1urts of the state to enter judgment on the arbitration award. This is the case in California, for example, under Cal. Code of Civ. P. § 1293.

And such a statute might purport to confer exclusive jurisdiction in the courts of that state, as seen in Connecticut and Nevada. See Conn. Gen. Stat. § 52-407zz(b); Nev. Rev. Stat. § 38.244.

21.12.9.8. An exclusive-forum clause could trump an arbitration clause

An explicit exclusive forum-selection provision in a contract might be held to trump an arbitration provision, such as Protocol 21.1, in a prior- or "background" agreement, such as the arbitration provision in the rules of the Financial Industry Regulatory Authority ("FINRA"), a self-regulatory organization. At this writing there's a split in the circuits on that point:

–  The Second and Ninth Circuits have held that an exclusive forum-selection clause does trump the arbitration provision in the FINRA rules. (But as discussed below, a later Ninth Circuit case implicitly called that holding into question.) See Goldman, Sachs & Co. v. Golden Empire Schools Financing Authority, 764 F.3d 210 (2d. Cir. 2014), in which the appeals court affirmed a trial court's grant of Goldman's motion to enjoin FINRA arbitration, on grounds that the forum-selection clauses in the parties' agreements superseded the arbitration provision (hat tip: Michael Oberman); see also Goldman, Sachs & Co. v. City of Reno, 747 F.3d 733, 736 (9th Cir. 2014), where the appeals court reversed a denial of preliminary injunction and final judgment on the same grounds. Accord: The Resource Group Int'l Ltd. v. Chishti, No. 23-286, slip op. (2d Cir. Jan. 22, 2024) (vacating and remanding denial of motion to enjoin arbitration); Suski v. Coinbase, Inc., 55 F.4th 1227 (9th Cir. 2022) (affirming denial of motion to compel arbitration) (exclusive forum-selection clause in later-accepted "official rules" superseded delegation clause in arbitration agreement contained in previous user agreement).

–  In a similar vein was a decision by Hawai'i's supreme court, in a case where a condominium purchase agreement stated that venue for litigation would be in a specified court in Hawai'i, but the purchase agreement incorporated a condominium declaration, which contained an arbitration clause. The court ruled that this inconsistency meant that the arbitration clause was unenforceable. (The court also held that the arbitration clause was unconscionable because it prohibited discovery and punitive damages.) See Narayan v. Ritz Carlton Dev. Co., 100 Haw. 343, 400 P.3d 544 (2015).

–  But in contrast, the Fourth Circuit held that an exclusive forum-selection clause did not trump the arbitration clause in the FINRA rules, on grounds that the forum-selection clause referred to litigation, not arbitration, and "we believe that it would never cross a reader's mind that the [forum-selection] clause provides that the right to FINRA arbitration was being superseded or waived." UBS Fin. Servs., Inc. v. Carilion Clinic, 706 F.3d 319, 329-30 (4th Cir. 2013); see also UBS Sec. LLC v. Allina Health Sys., No. 12–2090, 2013 WL 500373 (D. Minn. Feb. 11, 2013) (following Carilion Clinic). / ]

–  Likewise, the Ninth Circuit held that, in Uber's user agreement, the exclusive-forum provision was not incompatible with an arbitration provision, because the forum-selection provision was intended "to identify the venue for any other claims that were not covered in the arbitration agreement." Mohamed v. Uber Techs., Inc., 848 F.3d 1201, 1209 (9th Cir. 2016) (reversing, in part, denial of motion to compel arbitration).

21.12.9.9. Caution: Forum selection could preclude administrative action

Example: In a Federal Circuit decision:

–  A confidentiality agreement between the parties — we'll call them A and B — contained a forum-selection provision that expressly required any action challenging the validity of A's patents to be filed in federal court in Delaware.

–  Notwithstanding this requirement, B filed administrative challenges to the patents (known as "petitions for inter partes review," or IPRs) in the U.S. Patent and Trademark Office (USPTO).

The Federal Circuit held that the forum-selection provision should have been given effect, and that the trial court should have enjoined B from pursuing the IPRs. See Nippon Shinyaku Co. v. Sarepta Therapeutics, Inc., 25 F.4th 998 (Fed. Cir. 2022) (reversing and remanding denial of preliminary injunction).

(This was the opposite result from that in the Kannuu v. Samsung case discussed at 21.12.9.19.)

21.12.9.10. Use multiple, territory-specific choices of forum?

Some companies’ boilerplate terms include territory-specific choices of forum (and law). Example: Here’s a territory-specific forum provision from Carson Wagonlit Travel (now CWT):

18.1  This Agreement shall be exclusively governed by the exclusive laws of [sic] and all disputes relating to this Agreement shall be resolved exclusively in[:]

(i) England and Wales and governed by English law if the Seller’s registered office is located in the Europe, Middle East, Africa (EMEA) region;

(ii) Singapore if the Seller’s registered office is located in Asia Pacific (APAC) region; or

(iii) the State of New York, USA if the Seller’s registered office is located the Americas region. Archived at https://perma.cc/6RJK-57EM (emphasis and extra paragraphing added).

21.12.9.11. Caution: In Massachusetts, assets might be "attached" pretrial

If a contract specifies Massachusetts as the forum state for litigating disputes, the defendant might find that its bank account and other assets have been "attached" even before trial if the plaintiff can show a likelihood of success on the merits. See Shep Davidson, When an Out-of-State Company Can Be Sued in Massachusetts and Why You Should Care (2013).

21.12.9.12. Pro tip: Advise a client in writing about forum selection?

Example: An English sports executive signed an employment agreement with an Indian company to serve as the company's CEO. Long story short, the employment agreement didn't include a forum-selection provision to specify England, vice India, as the venue for any litigation. Things went badly, and the executive sued the Indian company, in India, for breach of his employment contract. But the Indian court proceedings took so long that the Indian company became insolvent, and in the end, the executive got nothing, apart from bills for some £1 million in legal fees from his counsel — so he successfully sued his law firm for malpractice for failing to advise including a forum-selection clause in the draft contract because of the notorious slowness of Indian courts. See Wright v. Lewis Silkin LLP, [2016] EWCA Civ 1308 ¶¶ 17-18, 39, 46 ]

21.12.9.13. For "UK courts" [sic] don't make this rookie mistake

A rookie mistake is to refer to "the courts of the United Kingdom," or "the courts of Great Britain," because the UK has three separate legal systems: England and Wales; Scotland; and Northern Ireland; and, since devolution, Wales, as explained in (separate) articles by English practitioners. See Tom Bolam, Country Clarity in Contract Law (Fladgate.com 2021); Greenwoods Legal LLP, Choice of law and jurisdiction: "England and Wales" and Brexit (Greenwoods.co.uk 2018).

And at the (very-useful) lawyers-only forum redline.net, British attorney David Hill writes:

To make things really complicated, although the jurisdictions [in the UK] are distinct, the court system is more 'united' so for your court jurisdiction clause (which should always be paired with the choice of law clause) the correct form is 'the courts of England and Wales' (or Scotland, or Norther[n] Ireland)!

See also the commentary at 21.14.5.9 concerning governing-law clauses when parties agree that the laws of one of the UK's separate countries or provinces (England, Wales, Scotland, Northern Ireland) are to apply.

21.12.9.14. Caution: China could be a special case

As explained in a 2019 post by Seattle-based lawyer Dan Harris, anyone drafting a contract with a Chinese counterparty should consider:

  • whether the contract meets the language- and governing-law requirements of Chinese law to make the contract enforceable by a Chinese court; and
  • if not, whether the counterparty has sufficient reachable assets in a more-friendly jurisdiction (because Chinese courts purportedly won't enforce foreign judgments or arbitration awards). See generally Dan Harris, China Contracts That Work (2019 & 2024).
21.12.9.15. Caution: Russia has a special anti-sanctions law

Anyone dealing with a contract counterparty in Russia needs to consider whether it might get caught in the crossfire of that country's so-called Lugovoy Law, which was enacted in response to international sanctions to punish various actions by the Russian government as well as specified non-state actors — and which threatens serious penalties against violators.

  • The Lugovy Law purports to allow sanctioned parties to sue in Russian courts — that's the case even when the parties have agreed to forum-selection clauses that would have required the disputes to be heard elsewhere.
  • But some courts outside of Russia have refused to go along: They've entered injunctions prohibiting parties in their cases from going to Russian courts to enforce the Lugovy Law. See generally Rinat Gareev, Russia’s Lugovoy Law and the Battle for Jurisdiction (TLBlog.com 2025).
21.12.9.16. Require lawsuits to be brought in the defendant's home jurisdiction?

Some contracts require any litigation against a given party to be brought in that party's home jurisdiction — so in a contract between "Fred" who lives in France and "Ginger" who lives in Georgia:

  • if Fred wanted to sue Ginger, he'd have to file the lawsuit in Georgia;
  • conversely, if Ginger wanted to sue Fred, she'd have to file in France.

Here's an example of such a clause "in the wild":

EXCLUSIVE FORUM SELECTION: Any action arising out of or relating to this Agreement, or any transaction or relationship resulting from it, is to be initially brought, and subsequently maintained, exclusively in the courts having jurisdiction in the following respective cities: (i) [CITY], England if [CUSTOMER NAME] and/or any of its personnel are defendants in the action as originally brought; and (ii) Houston, Harris County, Texas if [SUPPLIER] and/or any of its personnel are defendants in the action as originally brought.

21.12.9.17. Not agreeing to a forum up front could be costly …

If contracting parties don't specify a forum for their disputes, they could be letting themselves in for a fact-intensive court dispute over whether a lawsuit would be proper in a particular state chosen in the heat of a dispute. As a rule, this would mean that the parties could count on having to pay lawyers for depositions, document production, brief-writing, and oral argument, both in the trial court and when the losing party appealed. That's because the existence of "personal jurisdiction" often lies in the eye of the beholder — i.e., a court — unless the parties have previously agreed between themselves on that score. Example: This can be seen in a New York case where extensive litigation was required to address the forum question. See New York v. Vayu, Inc., 39 N.Y.3d 330, 206 N.E.3d 1236, 186 N.Y.S.3d 93, 2023 NY Slip Op 00801 (2023) (reversing and remanding dismissal of complaint).

21.12.9.18. But: Proposing a forum might be poking a bear

Suppose that you're drafting a contract and are thinking about where contract-related disputes might be litigated:

  • If you don't include a forum-selection clause in a draft contract (and thereby "roll the dice" about the forum for future lawsuits), then it's at least possible that The Other Side might not even raise the issue.
  • On the other hand: If you do propose a forum clause — and The Other Side has more bargaining power — then The Other Side might insist on "flipping" the provision to mandate its own preferred forum. When that happens, possibly the best you can hope for is for The Other Side to agree simply to drop the forum clause entirely.

That happened in one contract negotiation for a routine commercial deal in which I represented a Houston-based vendor:

  • The vendor was using a contract patched together by its business people before they became a client of mine.
  • The vendor sent the contract to a prospective customer that had significantly-more bargaining power — and that was based in, let's say Cleveland — but also had significant operations in Houston.
  • The vendor's contract form included a forum-selection provision requiring all litigation to take place exclusively in Houston.
  • The customer's lawyer — in Cleveland — saw the forum-selection clause, and said nope, all litigation has to be in Cleveland. That wouldn't have been good for the Houston-based vendor, because litigating in Cleveland would have been costly and inconvenient.

Fortunately, the customer's lawyer went along with my suggestion that we just drop the forum-selection clause entirely. The other lawyer evidently didn't realize that on the facts, this could have turned out to be a win for the vendor, because:

  • Without a forum-selection stipulation, the customer likely wouldn't have been able to sue the vendor in Cleveland at all, because the courts in that city would almost certainly wouldn't have had personal jurisdiction over the vendor. (Of course, that wouldn't have stopped the customer from filing suit anyway, which would have meant that the vendor would have to spend money to get the case dismissed or transferred.)
  • In contrast, the vendor would have been able to sue the customer in Houston because of the customer's significant operations there — the customer's lawyer apparently didn't tumble to the fact that he was making a potentially-big concession.
21.12.9.19. Why only "arising out of the Con­tract"?

Drafters should be careful about specifying an exclusive forum for proceedings "relating to" the parties' agreement, as opposed to the narrower "arising out of" the agreement as used in this Protocol.

Example: In Kannuu Pty Ltd. (2021), the Federal Circuit's decision involved a general, exclusive forum-selection provision, which had caused the parties to have to litigate whether Samsung could challenge the validity of a patent in an administrative proceeding in the U.S. Patent and Trademark Office, known as an "inter partes review" or "IPR" instead of in the agreed exclusive-forum court. Spoiler: Both the trial- and appeals courts said "yes." Kannuu Pty Ltd. v. Samsung Elec. Co., 15 F.4th 1101 (Fed. Cir. 2021) (affirming denial of motion for preliminary injunction); cf. DexCom, Inc. v. Abbott Diabetes Care, Inc. , 89 F.4th 1370 (Fed. Cir. 2024) (affirming denial of preliminary injunction; wording of exclusive forum-selection provision allowed filing of IPR).

But: An even-broader forum selection provision led to the opposite result, as discussed at 21.12.9.9.

Example: Consider the following (hypothetical) possibility:

  • Provider, a company headquartered in Providence (Rhode Island), licenses its software to Customer, in Cumberland (Maryland). (The city names here were chosen for matching initials.)
  • As with many drafter-favoring contracts, Provider's standard software license agreement requires that any litigation "arising out of or relating to" the agreement must be brought in Providence, Provider's home city.
  • One day, though, Customer rolls out its own software product that performs some of the functions of Provider's software — and Customer's new software bears a trademark that's confusingly similar to Provider's own trademark.

In that situation:

  • If Provider wanted to sue Customer for trademark infringement, then Provider might well want to bring the lawsuit in Cumberland because of the better availability of relevant witnesses and documents.
  • But: Provider might not be able to sue Customer in Cumberland — as Provider would prefer to do in these particular circumstances — because the license agreement required all disputes relating to the license agreement to be brought in Provider's home city of Providence.
21.12.9.20. Don't be wishy-washy about forum selection

In one contract that I reviewed for a client, a forum-selection clause stated that "disputes are to be resolved in [a particular court]." This is almost a canonical example of a false imperative; Rebecca Tradewell, an attorney for the Wisconsin Legislative Reference Bureau, explains that a better way to word such a provision is to state it in terms of a positive obligation: "Any dispute arising out of … must be brought and maintained in [the court in question]." See Becky Tradewell, Food Shall Be Pure: Using "shall" carefully for clearer laws (NSDL.org 2013).

21.12.9.21. Would a forum-selection clause imply a choice of law?

For extensive discussion and research notes, see a posting at the Transnational Litigation Blog. See Chukwuma Okoli, Forum Selection Agreements as Indicators of Implied Choice of Law (tlblog.org 2024).

21.12.9.22. A court might not honor a choice of an "improper" forum

In many American states, a venue statute specifies the location where a lawsuit must be brought; typically, this will be either the county where the plaintiff resides or the county where the defendant resides.

But if a contract's forum-selection clause specifies a county that doesn't meet the statutory requirement, then a court might refuse to enforce the forum selection. Example: This happened in a North Carolina case; the court, though, did note that "a forum selection clause which favored a court in another State was enforceable …." A&D Envt'l Serv., Inc. v. Miller, 770 S.E.2d 755, 756 (N.C. App. 2015) (affirming denial of defendant's motion to enforce forum-selection clause) (emphasis in original, citation and internal quotation marks omitted).

Another example: Under a California statute (Cal. Code Civ. Pro. § 116.225), "[a]n agreement entered into or renewed on or after January 1, 2003, establishing a forum outside of California for an action arising from an offer or provision of goods, services, property, or extensions of credit primarily for personal, family, or household purposes that is otherwise within the jurisdiction of a small claims court of this state is contrary to public policy and is void and unenforceable." (Hat tip: Sean Hogle at the lawyer forum redline.net.) For more about California's extensive legislative treatment of forum-selection clauses, see John F. Coyle, Forum Selection Clauses in California (TLBlog.com 2025).

21.12.9.23. Forum selections might be disregarded for policy reasons

Courts will sometimes refuse to honor a contract's forum-selection clause if the clause offends a strong public policy of the forum location. Here are a few real-world examples.

Example: A group of users of the America OnLine ("AOL") service sued AOL in California and sought class-action status.

  • The AOL user agreement required all disputes to be litigated in Virginia.
  • Citing the forum-selection clause, a federal district court in California dismissed the case but said it could be re-filed in Virginia state courts, as required by the user agreement.
  • The federal appeals court disagreed, holding that California had a strong public policy favoring class-action relief — and noting that the requested relief was not available in Virginia state courts.
  • Therefore, said the appeals court, "the forum selection clause in the instant member agreement is unenforceable as to California resident plaintiffs bringing class action claims under California consumer law." Doe 1 v. AOL, LLC, 552 F.3d 1077, 1084 (9th Cir. 2009).

Example: Relatedly, California Labor Code § 925 "prohibits an employer from requiring an employee who resides and works in California to agree to a provision requiring the employee to adjudicate outside California a claim arising in California." Zhang v. Superior Court (Zhang v. Dentons US LLP), 85 Cal. App. 5th 167, 171 (2022) (denying mandamus).

Counterexample: In a California case, a Delaware corporation's certificate of incorporation and bylaws included a mandatory forum-selection provision that designated Delaware's Chancery Court — where a jury trial wouldn't be available — as the exclusive forum for certain litigation. California's supreme court held that the lack of the right to a jury trial wasn't enough — at least not standing alone — to deny enforcement of the forum-selection provision, even though advance jury-trial waivers are constitutionally unenforceable in California courts:

Forum selection clauses serve vital commercial purposes and should generally be enforced. At the same time, courts may properly consider whether enforcement of a forum selection clause would violate public policy.

California has a strong public policy, based on the California Constitution, in favor of the right to trial by jury.

But California’s strong public policy protects the jury trial right in California courts, not elsewhere. It does not speak to the availability of the jury trial right in other forums.

A forum selection clause is not unenforceable simply because it requires the parties to litigate in a jurisdiction that does not afford civil litigants the same right to trial by jury as litigants in California courts enjoy. EpicentRX, Inc. v. Sup. Ct. of San Diego Cty, No. S282521, slip op. at 2 (Cal. Jul. 21, 2025) (reversing and remanding denial of mandamus) (extra paragraphing added).

Counterexample: Likewise, in a Texas supreme court case:

  • AutoNation, a Florida-based car dealer, filed suit, in Florida, against a former employee who lived in Texas and had worked for the car dealer there.
  • The former employee's employment agreement contained a choice-of-law clause calling for Florida law to apply, together with a forum-selection clause requiring any litigation to take place in Florida.
  • Before learning of the Florida action, the former employee sued the car dealer in Texas, seeking a declaratory judgment that the non-competition covenant of the employment agreement was unenforceable under prior Texas supreme court precedent.

Granting a writ of mandamus, the Texas supreme court ruled that while it was not questioning the validity of its prior precedent, it would still enforce the "freely negotiated" [sic] forum-selection clause to allow first-filed suit in Florida to proceed. In re AutoNation, Inc., 228 S.W.3d 663 (Tex. 2007).

QUESTION: On the AutoNation facts, what are the odds that the Florida court would have applied Texas law, given that the contract included a Florida choice-of-law clause?

Example: In a Sixth Circuit case, the contract in suit was between a Michigan countertop fabricator and a Minnesota manufacturer of stone slabs used to make countertops. The contract's forum-selection provision required all lawsuits to be brought in a Minnesota state court. The Michigan company filed suit in a federal district court in Michigan. The trial court granted the Minnesota company's motion to dismiss, citing the contract's forum-selection clause, but the appeals court reversed, on grounds that Michigan Franchise Investment Law invalidated the clause. See Lakeside Surfaces, Inc. v. Cambria Company, LLC, 16 F.4th 209 (6th Cir. 2021) (reversing and remanding dismissal of Michigan-filed lawsuit).

Example: A California appeals court held that the state's usury laws, while complicated, represented a fundamental public policy of the state that trumped a loan agreement's forum-selection provision. See G Companies Management, LLC v. LREP Arizona LLC, 88 Cal. App. 5th 342 (2023) (reversing order enforcing forum-selection clause). For additional discussion and case citations, see generally Paulo B. McKeeby, Solving the Multi-State Non-Compete Puzzle Through Choice of Law and Venue (2012). (For more on usury law, see 4.15.6.) ]

Example: In Texas, if a contract relates broadly to real property located in Texas and is entered into after September 1, 2025, then (with certain exceptions) a forum-selection clause requiring litigation in the courts of another state is void as against public policy — ditto for governing-law clauses choosing the law of another state, and arbitration clauses requiring arbitration in another state. Under the former version of the statute, a state court of appeals held that if the forum-selection clause included a waiver of voidability, then that waiver would be enforced; three years later, the Legislature responded by changing the wording to preclude that result. See Tex. Bus. & Comm. Code ch. 272, amended by H.B. 2960. The previous version of the statute was cited in In re MVP Terminalling, LLC, No. 14-21-00399-CV, slip op. (Tex. App—Houston [14th Distr.] Aug. 23, 2022) (conditionally granting mandamus proceeding; by entering into subcontract, subcontractor had contractually waived its statutory right to void forum-selection clause).

21.12.9.24. Could a "closely-related" non-signatory be bound?

Example: As explained by the Fifth Circuit: Under the "closely-related" doctrine, non-signatories to the contract might be bound by — and conversely, might be able to enforce — a forum-selection clause "where, under the circumstances, the non–signatories enjoyed a sufficiently close nexus to the dispute or to another signatory such that it was foreseeable that they would be bound." Franlink Inc. v. BACE Services, Inc., 50 F.4th 432, 439 (5th Cir. 2022) (cleaned up, extensive citations omitted).

Counterexample: The Texas supreme court held that a company's CEO was not personally bound by a contract's forum-selection provision just because the CEO had signed the contract on behalf of the company. See Rieder v. Woods, 603 S.W.3d 86 (Tex. 2020) (reversing and remanding court of appeals decision).

Counterexample: In Firexo (6th Cir. 2024), the appeals court essentially rejected the "closely related" doctrine — after extensive analysis, including analogizing to arbitration law — but ultimately ducked the question on grounds that the parties' choice of English law precluded resort to the doctrine. See Firexo, Inc. v. Firexo Group Ltd., 99 F.4th 304, 327-29 (6th Cir. 2024) (reversing and remanding dismissal, with extensive citations).

Counterexample: Arizona's supreme court rejected the "closely related" doctrine on grounds that "under Arizona law, third-party beneficiaries must be explicitly named in the contract to enforce the contract’s provisions," and the defendant was not a named beneficiary and so could not rely on the contract's forum-selection provision. See Henderson v. Moskowitz, No. CV-24-0215-PR, slip op. at 6 ¶ 14 (Ariz. Nov. 28, 2025) (affirming trial court denial of defendant's motion to dismiss).

See also an extensive 2021 survey by two law professors. See John F. Coyle and Robin Effron, Forum Selection Clauses, Non-Signatories, and Personal Jurisdiction, 97 Notre Dame L. Rev. 189 (2021) (criticizing closely-related doctrine and proposing reforms).

21.12.9.25. Idaho's idiosyncratic approach ….

Example: In an Idaho case, a contract expressly required arbitration in Dallas, but the state's supreme court held that the contract's choice of Texas law required arbitration in Idaho. See T3 Enterprises, Inc. v. Safeguard Bus. Sys., Inc., 164 Idaho 738, 435 P.3d 518, 528-30 (2019).

Example: And later, the same court held that a contract's choice of California law required arbitration in Idaho — this, even though the contract expressly required arbitration to be in California:

We hold that California law requires an examination of the public policy of the forum in which suit is brought, and that the forum selection clauses at issue violate the strong public policy of the State of Idaho. We affirm the district court’s ruling that claims arising from the parties’ purchase agreement and LLC agreement must be arbitrated in Idaho. Off-Spec Solutions, LLC v. Transp. Investors, LLC, 168 Idaho 734, 487 P.3d 326 (2021).

Editorial comment: It'd be one thing if the Idaho court had tossed out the contracts' respective choice-of-law provisions as well as the choice-of-forum provisions, on grounds that otherwise, the parties' bargained-for results would have violated Idaho public policy as expressed in Idaho's choice-of-forum statute. See Idaho Code § 29-110, quoted in Off-Spec Solutions, slip op. at 7.

But let's just say it's … unusual to assert that California's or Texas's law somehow requires an Idaho court to concern itself with Idaho's public policy.

Drafting lesson: If doing business with an Idaho company, don't expect your forum-selection provision to be given effect by an Idaho court — so be prepared to race to your preferred courthouse if it looks as though litigation is on the horizon.

21.12.9.26. Texas business courts - like Delaware's chancery court?

In September 2024, a new form of Texas state court, limited to business cases and with appeals heard by a new court of appeals in Austin, opened for business. See generally, e.g., the Vinson & Elkins memo Everything You Need to Know About Texas’s Business Courts.

21.13. Fraud Proof Protocol

  1. When this Protocol is agreed to, the parties follow it whenever, the parties will follow it whenever A alleges fraud — however labeled — arising out of or otherwise relating to the Con­tract, under any legal- or equitable theory.
  2. A will do the following:
    1. plead the allegation with the particularity required by Federal Rule of Civil Procedure 9(b);
    2. prove the allegation by clear and convincing evidence (as defined at Protocol 20.11); and
    3. offer reasonable corroboration (defined at Protocol 21.6) of any testimony by an interested witness.
  3. A WAIVES any allegation of fraud that are not proved as required by subdivision A above.
  4. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol
Note

().  Lawyers, and even clients, can sometimes casually throw around allegations of fraud, for tactical reasons discussed in more detail at 20.34.6.7. Such allegations can make litigation (and arbitration) much more complicated and costly. To streamline legal proceedings when fraud-like allegations are made, this Protocol is intended to lock in the usual American standard of proof in civil cases.

Subdivision A.1: This clear-and-convincing evidence requirement is based on typical rules in the U.S. See, e.g., Riley Hill Gen. Contractor, Inc. v. Tandy Corp., 303 Or. 390, 737 P.2d 595, 597 (1987) (affirming court of appeals in reversing and remanding for new trial); Rudman v. Cowles Comms., Inc., 30 N.Y.2d 1, 10 (1972) (affirming dismissal of fraud claim); New York Pattern Jury Instruction 3:20, cited in H.J. Heinz Co. v. Starr Surplus Lines Ins. Co., No. 15cv0631, slip op. at 5 (W.D. Pa. Oct. 30, 2015) (adopting clear and convincing evidence standard for jury instructions).

Subdivision 2.c: For discussion of this corroboration requirement, see the commentary at Protocol 21.6.

Subdivision 3: This waiver is a signal to any court or arbitrator that's considering a fraud claim covered by this Protocol.

21.14. Governing Law Effect Protocol

21.14.1. This Protocol is binding only if the parties agree to it.

  1. When this Protocol is agreed to, the parties follow it whenever the Con­tract clearly says that the law of a particular stated geographic location or jurisdiction will apply (or govern, or similar wording). That is referred to here as the law that will "apply" or "govern."
  2. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol
Note

().  It's quite common for contracts to specify a law to govern the contract as a whole, or possibly just one specific clause of a contract. That's because under the "party autonomy rule" in the United States (and some other jurisdictions), parties can agree — within limits — that their contract will be governed by the law of another jurisdiction. See Great Lakes Insurance SE v. Raiders Retreat Realty Co., 601 U.S. _, 144 S. Ct. 637 (2024) (reversing 3d Cir., upholding maritime contract's choice of New York law): "Applying federal maritime law in this case, we conclude that choice-of-law provisions in maritime contracts are presumptively enforceable, with certain narrow exceptions not applicable here."

For a partial survey of different approaches to governing-law clauses taken by various state courts, see a 2026 piece by Professor Coyle — who notes that "The State of Kentucky appears to be the only one whose courts ignore choice-of-law clauses when determining which law to apply." John F. Coyle, Idiosyncratic Approaches to Enforcing Choice-of-Law Clauses (tlblog.org 2026).

21.14.2. Substantive law; no renvoi

On substantive matters, the "Governing Law" will be the substantive law that applies in the stated geographic jurisdiction —

  1. as that (substantive) law is applied in disputes, between residents of that jurisdiction, concerning matters that happen entirely within that jurisdiction, and
  2. without regard to that jurisdiction's choice-of-law rules — for emphasis, the parties want here to rule out application of the legal doctrine of renvoi.
Note

Subdivision 2: To illustrate how renvoi (French for "send back") works, let's consider the following hypothetical example:

  1. Two giant oil companies company — let's call them Flexxon and Blevron — each have operations in New Orleans but are headquartered in Houston.
  2. The two companies enter into a contract under which they will explore for oil.
  3. The contract is negotiated in Louisiana, and all the work under the contract is to take place in Louisiana.
  4. But the contract between the companies calls for Texas law to apply, because Flexxon and Blevron are both headquartered in Houston and their lawyers are more familiar with Texas law.

On these facts, Texas choice-of-law rules might call for the application of Louisiana law in a lawsuit, because Louisiana might be the state with the closest relationship to the parties' dealings. See generally, e.g., Conflicts of laws in the United States (Wikipedia.com).

That's why subdivision 2 includes the phrase, "without regard to … choice-of-law rules" phrase; this is known as disclaiming renvoi. See, e.g., American Ins. Co. v. Frischkorn, 173 F. Supp. 2d 514, 520-21 (D. W. Va. 2001) ("This Agreement shall be governed by and construed in accordance with the laws of the State of California applicable to disputes occurring entirely within such State."); Brill v. Regent Communications, Inc., 12 N.E.3d 299, 306-08 (Ind. App. 2014) (citing cases) ("This Agreement shall be interpreted and the rights of the parties determined under the laws of the Commonwealth of Virginia without regard to the conflict of law provisions thereof").

21.14.3. Applicable disputes

The Governing Law will apply in any dispute arising out of or relating to:

  1. the Con­tract itself, and/or
  2. any transaction or relationship resulting from the Con­tract.
Note

().  applies broadly to "any dispute arising out of or relating to" (see § 32.2) certain things. But if instead a choice-of-law clause is drafted more narrowly — for example, to cover only to the interpretation and enforcement of a contract — then the chosen law will probably not be applied to tort-based claims such as claims of misrepresentation, e.g., of fraudulent inducement to enter into the contract.

Example: In a Massachusetts case, a married couple brought an arbitration claim against its investment firm.

  • The parties' contract contained a choice of Massachusetts law, but that choice of law applied only to the interpretation and enforcement of the contract, not to related claims.
  • The client’s claims against the investment firm included not only contract claims, but also claims under a Pennsylvania unfair-trade-practices statute.

An arbitrator held that, because the contract's choice-of-law provision didn't apply to noncontract claims, the Pennsylvania statute's remedies were available to the client.

The arbitrator awarded treble damages under the Pennsylvania statute; a trial court in Massachusetts upheld the (sizeable) arbitration award. See Family Endowment Partners, L.P. v. Sutow, No. 2015 CV 1411- BLS1 (Mass. Superior Ct. Nov. 16, 2015) (confirming arbitration award); relatedly, see Pat Murphy, $48M arbitration award vs. investment advisor upheld (McCarter.com 2015). See also, e.g., ACI Worldwide Corp. v. KeyBank N.A., No. 1:17-cv-10662-IT, slip op. at 5-7 (D. Mass. Sept. 30, 2020) (contractual choice of law didn't apply to fraudulent-inducement claim).

Example: As discussed at 21.14.5.13:

  • A Maine-based sales representative's employment agreement included a California choice-of-law provision.
  • That provision, though, said only that "[t]he terms of this [agreement]" are to be "governed by and construed and enforced" under California law.
  • The company failed to pay commissions on certain sales; the sales rep sued, with the lawsuit including a non-contract claim (quasi-contract, to be precise).

A federal appellate court held that the sales rep's non-contract claim did not require construction or enforcement of the terms of the agreement — and so Maine law, not California law, would govern that claim.

As a result, the sales rep won, not only commissions, but also treble damages and attorney fees under a Maine statute. Dinan v. A Networks, Inc., 764 F.3d 64 (1st Cir. 2014) (vacating trial-court judgment that applied California law after jury verdict in favor of sales rep).

Example: A Canadian software company had drafted its end user license agreement ("EULA") with too-narrow a choice of Canadian law. As a result, the company found itself forced to defend one customer's federal class-action lawsuit in Chicago instead of in Victoria, British Columbia as specified in the EULA. The U.S. court noted that the EULA’s governing-law provision applied only to the EULA per se and didn't encompass the plaintiff’s Illinois-law claims; this, said the U.S. court, tipped the balance in favor of keeping the case in Chicago. Beaton v. SpeedyPC Software, No. 13-cv-08389 (N.D. Ill. June 5, 2015) (denying defendant’s motion to dismiss for forum non conveniens) (subsequent history omitted — see 907 F.3d 1018 (7th Cir. 2018)).

The term any transaction or relationship … is modeled on an arbitration-agreement provision that has been litigated at least twice. See Sherer v. Green Tree Servicing LLC, 548 F.3d 379, 382-83 (5th Cir. 2008), citing Blinco v. Green Tree Servicing LLC, 400 F.3d 1308, 1310 (11th Cir. 2005).

21.14.4. Procedural law for lawsuits and other disputes

The relevant procedural law is whatever the Governing Law says it would be.

Note

A contract's choice of governing law will generally apply only to substantive law, not to procedural matters — such as, notably, statutes of limitation setting deadlines for filing lawsuits. See, e.g., Integrity Global Security, LLC v. Dell Marketing LP, 579 S.W.3d 577, 587 (Tex. App.–Austin 2019) (reversing summary judgment that limitation period had expired).

21.14.5. Additional notes

21.14.5.1. Choose New York law? California law

Very much worth a read:

The differences between New York and California contract law turn out to align with the formalist/contextualist distinction in contract theory.

  • New York judges are formalists. Especially in commercial cases, they have little tolerance for attempts to rewrite contracts to make them fairer or more equitable, and they look to the written agreement as the definitive source of interpretation.
  • California, on the other hand, is more willing to reform or reject contracts in the service of morality or public policy; it places less emphasis on the written agreement of the parties and seeks instead to identify the contours of their commercial relationship within a broader context framed by principles of reason, equity and substantial justice.

Both approaches to contract law are commendable. Both serve important social goals and employ sophisticated and well-reasoned doctrines in the service of those ends. This article takes no position on whether one is better than the other.

What is clear, however, is that contracting parties do take a position on this question. The testimony of the marketplace — the verdict of thousands of sophisticated parties whose incentives are to maximize the value of contract terms – is that New York’s formalistic rules win out over California’s contextualist approach.

As predicted by theory, sophisticated parties prefer formalistic rules of contract law. Geoffrey P. Miller: Bargaining on the Red-Eye: New Light on Contract Theory, NYU Law and Economics Research Paper No. 08-21, at 5-6 (2008) (cleaned up, presentation edited), available at SSRN: https://ssrn.com/abstract=1129805 or http://dx.doi.org/10.2139/ssrn.1129805.

21.14.5.2. Delaware law strongly favors "freedom of contract"

Delaware law gives parties wide latitude to enter into contracts as they see fit — the state's courts are very reluctant to put a thumb on the scale without a compelling reason. In RSUI Indem. (Del. 2021), the state's supreme court quoted an oft-cited chancery-court decision about party autonomy:

When parties have ordered their affairs voluntarily through a binding contract, Delaware law is strongly inclined to respect their agreement, and will only interfere upon a strong showing that dishonoring the contract is required to vindicate a public policy interest even stronger than freedom of contract.

Such public policy interests are not to be lightly found, as the wealth-creating and peace-inducing effects of civil contracts are undercut if citizens cannot rely on the law to enforce their voluntary-undertaken mutual obligations. RSUI Indem. Co. v. Murdock, 248 A. 3d 887, 903 (Del. 2021) (cleaned up, extra paragraphing added).

21.14.5.3. Caution: A governing-law clause might backfire

Specifying a particular law that you want to govern your contract, or your contractual relationship, could lead to unexpected — and possibly-undesired — results. Here are some real-world examples:

Example: A group of individuals, working in New York as couriers for a Massachusetts-based company, sued the courier company in Massachusetts for unpaid overtime. The company had drafted its contract form to specify that Massachusetts law would apply and that all litigation must be in Massachusetts. So, these New-York based couriers claimed to be entitled to the protection of Massachusetts statutes governing independent contractors, wages, and overtime. The Massachusetts supreme court held that it would not be unfair to enforce the courier company’s own forum-selection and governing-law choices against the company. See Taylor v. Eastern Connection Operating, Inc., 465 Mass. 191, 988 N.E.2d 408 (2013) (vacating trial court's dismissal of case and remanding for further proceedings).

Example: A Florida-based, remote-working employee of a Massachusetts company successfully sued the company's CEO — personally — for more than $100,000 in unpaid wages and expense reimbursements, among other amounts. The employee did so under a Massachusetts statute that created the right of action, in part because the remote worker's employment agreement stated that Massachusetts law applied. See Dow v. Casale, 83 Mass. App. Ct. 751, 989 N.E.2d 909, 913 (2013) (affirming summary judgment in favor of former employee).

Example: A federal court in Oklahoma, considering the same Massachusetts statute, dismissed the class-action claims filed by two remote employees; in that case, the employment agreement didn't include a choice-of-law provision. See Goode v. Nuance Communications, Inc., No. 17-CV-00472-GKF-JFJ, slip op., text acc. n.5 (N.D. Okla. Jul. 10, 2018).

Example: In a franchise-dispute case, the Ontario court of appeals held that Ontario law — which gave franchisees specific rights — applied even to franchisees outside Ontario because the franchise agreement specified that Ontario law would apply. See 405341 Ontario Ltd. v. Midas Canada Inc., 2010 ONCA 478 paras. 40-45.

Counterexample: A federal district court in San Francisco held that Uber drivers working outside California could not sue the company for violation of a California wage-and-hour statute, even though the drivers’ contract with Uber included a California choice-of-law clause, on grounds that the relevant statutes didn't apply extraterritorially. See O’Connor v. Uber Tech., Inc., 58 F. Supp. 3d 989, 1003-06 (N.D. Cal. 2014) (granting judgment on the pleadings). (The extensive subsequent proceedings in that case aren't relevant here; see O'Connor v. Uber Tech., Inc., 904 F.3d 1087 (9th Cir. 2018).).

21.14.5.4. A governing-law clause could decide the outcome of a case

A pharmaceutical company owned a patent but did a "Samson in the temple" move to the patent. Why did it do that? Because it had entered into an agreement with another pharma firm that required it to pay royalties on its own product, and it wanted to get out from under that obligation. (To explain further would require getting into the weeds of patent law, and it's not important in any case.) The contract between the two pharma companies stated that Delaware law would govern.

The other firm sued for breach of the implied covenant of good faith and fair dealing. But the Delaware supreme court said, basically, tough: Under Delaware's "contractarian" approach, said the court, "[t]he implied covenant … is a limited and extraordinary legal remedy and not an equitable remedy for rebalancing economic interests that could have been anticipated. It cannot be invoked when the contract addresses the conduct at issue." Glaxo Group Ltd. v. DRIT LP, 248 A.3d 911, 919-20 (Del. 2021) (reversing, in part, trial-court judgment) (cleaned up).

LESSON: A choice-of-law clause could be important.

21.14.5.5. Limit the choice of law to "interpretation" or "enforcement"?

Section 21.14.3 is a broad one — contrasting with narrower language such as in a Second Circuit case:

Under New York law, in order for a choice-of-law provision to apply to claims for tort arising incident to the contract, the express language of the provision must be sufficiently broad as to encompass the entire relationship between the contracting parties.

In the case at hand, the choice-of-law provision in the parties' mortgage document stated only that "[t]his Mortgage shall be governed by and construed in accordance with the laws of the Commonwealth of Massachusetts."

We see no way such language can be read broadly enough to apply to fraudulent misrepresentation. Thus, the district court properly looked to the jurisprudence of New York to determine the body of law properly applicable to the present controversy. Krock v. Lipsay, 97 F.3d 640, 645 (2d Cir. 1996) (cleaned up).

More recently, from the Southern District of New York:

Here, the Agreement's choice-of-law provision provides the governing law only for the contract. It states: "This Agreement shall be governed by, and construed under, the laws of the State of Delaware, all rights and remedies being governed by said laws."

Plaintiff argues that the "all rights and remedies" phrase broadens the scope of the clause and reflects an intent to apply Delaware law to extra-contractual claims. However, when read in context, that language is explanatory, indicating that the substantive law of Delaware will apply exclusive of its choice of law principles.

The provision expressly provides that "This Agreement" is what is governed by Delaware law. * * * Accordingly, New York law governs the tortious interference claim. Manbro Energy Corp. v. Chatterjee Advisors, LLC, No. 20 Civ. 3773 (LGS), part III.A, slip op. (granting motion to dismiss tortious-interference claim).

And from the Fifth Circuit:

The parties' choice of law clause provides that: "[t]his Agreement shall be construed under the laws of the State of California." * * *

The parties' narrow choice of law clause does not address the entirety of the parties' relationship, however, and hence does not end our inquiry. Caton's other claims for relief involve the tort duty of good faith and fair dealing and a claim for restitution under quantum meruit, and, as such, do not arise out of the contract. Because the choice of law clause does not address the general rights and liabilities of the parties, we must return to Texas choice of law rules to determine which law applies. Caton v. Leach Corp., 896 F.2d 939, 942, 943, 949 (5th Cir. 1990) (affirming summary judgment against tort claim for wrongful discharge: in employment relationships, Texas law does not recognize tort duty of good faith); see also, e.g., Indep. Fin. Grp., LLC v. Quest Trust Co. No. H-21-2125, § 1 (S.D. Tex. Dec. 21, 2022) (Bray, M.J., recommending grant of summary judgment dismissing claims) (custodial agreement stated that it "shall be governed by and construed under the applicable laws of the state of Texas"), adopted (S.D. Tex. Jan.25, 2023) (Hughes, J.) (overruling objections).

21.14.5.6. Which governing law to choose?

Drafters wondering which governing law to choose should give some thought to the specifics of the laws being considered.

  • Several years ago, I started a choice-of-law cheat sheet for U.S. states that might be helpful (although I haven't worked on it in a long time).
  • In international transactions, a party from a jurisdiction with a civil code (e.g., continental Europe; Latin America) might be reluctant to agree to the law of a common-law country (e.g., England and its former colonies), or vice versa. In that situation, the UN CISG, discussed at 21.14.5.11, might be an acceptable "neutral" choice.
  • English law is often chosen for multi-national transactions. See, e.g., Melanie Willems, English Law – a Love Letter (mondaq.com 2014), which contrasts England’s common-law foundation with the civil law found on the Continent ]
  • Different laws might be suited for different industry categories. See generally Thierry Clerc, International Contracts: From choosing applicable law to settling disputes (EuroJuris.net 2016), archived at https://perma.cc/U54S-QMBH.
  • Choosing the law in a given country might require, in case of dispute, translation into whatever language is used in the lawsuit or arbitration; that can add to the expense.
21.14.5.7. Choose the law of the agreed forum?

If the parties are also going to agree to a choice of forum — about which see 21.12 — then they might want to choose the law of that agreed forum as their agreed governing law. That could increase the chances of having their choice of law enforced in a dispute.

For example: the parties might agree to New York law, in part to take advantage of the statutory provision validating clauses requiring amendments to be in writing in certain contracts (see 3.1 and its commentary). A New York court would seem to be more likely to give effect to that provision, and thus to an amendments-in-writing clause, than might a court in another jurisdiction.

21.14.5.8. Territory-specific choice of law?

Some companies’ boilerplate terms include territory-specific choices of law (and forum selections). For example, here’s a territory-specific governing law provision from Carson Wagonlit Travel (now CWT), archived at https://perma.cc/6RJK-57EM.

18.1  This Agreement shall be exclusively governed by the exclusive laws of [sic] and all disputes relating to this Agreement shall be resolved exclusively in[:]

(i) England and Wales and governed by English law if the Seller’s registered office is located in the Europe, Middle East, Africa (EMEA) region;

(ii) Singapore if the Seller’s registered office is located in Asia Pacific (APAC) region; or

(iii) the State of New York, USA if the Seller’s registered office is located the Americas region.

(Emphasis and extra paragraphing added.)

21.14.5.9. Pro tip: The UK as a special case

A rookie mistake is to refer to "the laws of the United Kingdom" or "the laws of Great Britain," because the UK has four separate legal systems: England; Scotland; Northern Ireland; and, since devolution, Wales. At the (very-useful) lawyers-only forum redline.net, British attorney David Hill writes: "[R]eferring to 'the laws of the United Kingdom' is a giant flashing neon sign …. If in any doubt, just go with 'the laws of England'." Emphasis added; see also Tom Bolam, Country Clarity in Contract Law (Fladgate.com 2021); Greenwoods Legal LLP, Choice of law and jurisdiction: "England and Wales" and Brexit (Greenwoods.co.uk 2018).

Relatedly: See 21.12.9.13 concerning forum-selection clauses to specify litigation in the UK.

21.14.5.10. Caution: China-involved contracts could be a special case

A guide published by an international law firm includes an extended discussion of choice-of-law provisions under Chinese law. See Herbert Smith Freehills LLP, Dispute resolution and governing law clauses for China-related commercial contracts 8-16 (Lexology.com 2020).

A law professor at the Chinese University of Hong Kong writes that:

Chinese courts have long been said to display a "homeward trend" in applying Chinese law, the lex fori, instead of foreign law in foreign-related civil litigations. Coined by Nussbaum in 1932, the term "homeward trend" refers to “a tendency to arrive, if possible, at the application of domestic law” in the courts’ judicial search for the applicable legal system.

This homeward trend is frequently criticized by commentators, who regard it as a form of local protectionism. It damages the credibility of Chinese courts and erodes the confidence of foreign investors. In addition, it encourages forum shopping and causes unfairness to defendants. King Fung Tsang, An Empirical Study on Choice of Law in China: A Home Run?, 21 Wash. U. Global Studies L. Rev. 339, 341-42 (2023).

Some years ago at the China Law Blog, Dan Harris asserted that as a practical matter, Chinese courts:

  • will not enforce a contract unless the contract is written in Chinese and the governing law is Chinese;
  • will not enforce judgments of other nations' courts in contract lawsuits; and
  • are unlikely to enforce arbitration awards from non-Chinese jurisdictions.

See generally Dan Harris, China Contracts That Work (2014), archived at https://perma.cc/DY8W-2CAY

21.14.5.11. Exclude the U.N. CISG, and/or UCITA?

It's not uncommon for contracting parties to exclude, e.g., the United Nations Convention on Contracts for the International Sale of Goods ("U.N. CISG" or "Vienna Convention"). That convention, in some ways, amounts to an international version of the U.S. Uniform Commercial Code, with nontrivial differences, surveyed in a Wikipedia article. See generally the Wikipedia article on the U.N. CISG; for a comparison of the UCC and the CISG, see John C. Tracy, UCC and CISG (Jul. 5, 2011).

Professor John Coyle reports that when American companies' contracts mention the CISG at all, the vast majority exclude the CISG, with only a tiny fraction explicitly adopting it. Moreover, "[a] substantial number of U.S. attorneys have no idea that the CISG exists. These attorneys are unaware that they must opt out of the treaty if they want their international sales contracts to be governed by domestic sales law." John F. Coyle, CISG Opt-Outs and Party Intent (TLBlog.com 2022).

Another possible exclusion is the Uniform Computer Information Transactions Act ("UCITA"), which is (was?) a controversial proposed uniform law that was enacted only in Maryland and Virginia, and but otherwise appears to be a dead letter. See generally the Wikipedia article on UCITA ]

21.14.5.12. How do U.S. courts decide what law to apply?

Let's illustrate with an example in which a contract lawsuit is brought in a court in a given state — for example, a court in New York state. The judge will naturally apply the law of that state (that is, New York law) unless one or another party asserts that the law of a different jurisdiction should apply. Then it's up to the asserting party to convince the judge that New York law allows the other jurisdiction's law to govern.

–  If no party raises the governing-law issue, then the (New York) court likely will apply New York law, on grounds that the parties waived application of another jurisdiction's law.

Example: Suppliers in Argentina sued a buyer of food products, operating in New York, for payment of $100,000 in past-due invoices On the facts, the U.N. Convention on Contracts for the International Sale of Goods ("CISG," discussed briefly at 21.14.5.11 ) clearly applied — but no one seems to have made that point, so the court applied New York law without comment. See Salteña S.A.U. v. Ercomar Imports Internacional Corp., No. 21-CV-4675, slip op. at part IV.A (E.D.N.Y. May 22, 2024) (granting default judgment against buyer), discussed in John F. Coyle, Overlooking the CISG (TLBlog.com 2024). See also Clayton P. Gillette, Implicit Exclusion of CISG (law.nyu.edu 2011).

–  If federal law doesn't govern, and the contract states that State A's law will apply, then a judge in State B will probably go along with that statement — that is, unless the statement is inconsistent with a fundamental policy of State B's law; see 21.14.5.13 for more details.

–  If the contract doesn't specify a choice of law, one or another party might still assert that another jurisdiction's law should apply. In that situation, many courts follow the Restatement (Second) of Conflict of Laws to determine just which law to apply.

Example: The Tenth Circuit concluded that Colorado would follow the Restatement; in a very-readable exposition, the court explained why, in the court's view, Colorado's law governed an advance waiver and release agreement. (This took place in a tragic case in which an outdoor-adventure participant, trying to rappel from a quarry, got stuck hanging upside down on the rope and died from positional asphyxia.) See Hamric v. Wilderness Expeditions, Inc., 6 F.4th 1108, 1125-28 (10th Cir. 2021) (affirming summary judgment in favor of wilderness outfitter based on advance release).

21.14.5.13. A court might disregard a problematic choice of law …

A court might not give effect to a governing-law clause in a contract if doing so would lead to a result that contravened a fundamental public policy of the law of the jurisdiction in which the court sits. Here are some examples:

Example: An employment agreement between a New York company and a New York-based employee included a non-solicitation provision, as in, no soliciting our customers after you leave the company. The employment agreement said that Florida law would apply, because the New York company was a subsidiary of a Florida-based company. New York state's highest court ruled that the enforceability of the non-solicitation provision was to be judged by New York law, not Florida law — even though the employment agreement said otherwise. See Brown & Brown, Inc. v. Johnson, 25 N.Y.3d 364, 34 N.E.3d 357, 12 N.Y.S.3d 606 (2015) (affirming, in pertinent part, judgment that choice-of-law clause was unenforceable in respect to non-solicitation clause).

Example: A medical-device sales representative quit his job in Arizona and started working for a direct competitor of his former company. The company filed a lawsuit in federal court in Arizona, seeking to enforce a non-competition covenant that was contained in the sale rep's employment agreement with the company. In the lawsuit, the company asked the court for an immediate temporary restraining order (TRO) to prohibit the sales rep from working for the company's competitor. The court, though, refused to grant the restraining order requested by the company:

  • The court recognized that the employment agreement's governing-law clause specified that the law of Washington state would apply (not the law of Arizona).
  • But, said the court: On this subject, the laws of Arizona gave more weight to employees' right to earn a living than did Washington-state law — and that was an area of fundamental public policy for Arizona law.

Consequently, the court refused to give effect to the agreement's choice of Washington-state law; the court went on to hold that, under Arizona law, the sales rep's non-competition covenant was unenforceable, regardless of whether it might be enforceable under Washington-state law. See Pathway Medical Technologies, Inc. v. Nelson, No. CV11-0857 PHX DGC (D. Ariz. Sept. 30, 2011); see also, e.g., LS3, Inc. v. Cherokee Federal Solutions, L.L.C., No. 20-cv-03555 (D. Colo. Sept. 29, 2021) (granting motion to dismiss lawsuit by former employer to enforce noncompetition covenant against former employees and their new employer).

Example: A California truck driver filed a lawsuit, in federal court in California, against the Texas-based trucking company for which he worked. The driver's claim was that the trucking company was violating California employment law by not paying overtime and not reimbursing certain expenses. The driver's contract with the company, though, specified that Texas law would apply; the contract also asserted that the driver was an independent contractor, not an employee of the trucking company. A federal appeals court held that:

  • State courts in California would not give effect to the contract's choice of Texas law, but instead would apply California law;
  • Under California law (said the federal appeals court), in reality the driver was an employee of the trucking company and not an independent contractor, no matter what the contract purported to say.

Thus, said the court, the driver could properly sue the trucking company in California for violating California employment law, notwithstanding the contract's contrary provisions. See Narascyan v. EGL Inc., 616 F.3d 895 (9th Cir. 2010) (reversing district court holding).

Example: A Maine-based sales representative was employed by a California company. The sales rep's employment agreement included a California choice-of-law clause. The company failed to pay commissions on certain sales. A federal appeals court held that Maine law governed — and therefore the sales rep was entitled, not only to back commissions, but also to treble damages and attorney fees under a Maine statute. See Dinan v. A Networks, Inc., 764 F.3d 64 (1st Cir. 2014) (vacating trial-court judgment that applied California law after jury verdict in favor of sales rep).

Example: In two … unusual holdings in different cases, the Idaho supreme court ruled that a contractual choice of a non-Idaho state's law, and a requirement that all disputes be heard in that state, somehow required the dispute to be heard … in Idaho. See the discussion at 21.12.9.25.

Example: In a scholarly opinion by then-judge Gregg Costa, the Fifth Circuit (a federal appeals court) recounted:

A contract for the leasing and servicing of drilling equipment includes a mutual indemnity agreement that complies with Texas law but would be unenforceable under Wyoming’s blanket ban.

Although the agreement states that Texas law will govern, most of the work performed under the contract occurred in Wyoming with none in Texas.

And indemnity is being sought for a Wyoming lawsuit filed by a Wyoming resident injured in a Wyoming oilfield operated by a Wyoming business.

We must decide whether the Texas or Wyoming Oilfield Anti-Indemnity Act applies. See Cannon Oil and Gas Well Services, Inc. v. KLX Energy Services, L.L.C., 20 F.4th 184, 186 (5th Cir. 2021) (emphasis and extra paragraphing added).

The court affirmed summary judgment that Wyoming law did indeed apply.

21.14.5.14. … or maybe not …

Contrary to the above examples, a court might give effect to a contract's choice of law even if a party claimed that the choice contravenes a fundamental public policy.

For example, the Texas supreme court held that it was permissible for ExxonMobil to choose New York law for its employee stock-option and restricted-stock programs, because multi-national companies should be able to choose the laws they want to follow, in the interest of uniformity. See Exxon Mobil Corp. v. Drennen, 452 S.W.3d 319 (Tex. 2014).

(OK, the "choose the laws they want to follow" part does overstate the Texas supreme court's holding just a bit, but not by much; the court arguably opened the door for corporations to purport to impose onerous terms and conditions on their employees while using a choice-of-law clause to strip the employees of their legal protections.)

21.14.5.15. A statute might explicitly negate a contractual choice of law

In a given jurisdiction, a statute might require a court of that jurisdiction to disregard a contract's choice of law. Example: In the Minnesota Termination of Sales Representatives Act, the state legislature declared that contractual choice-of-law provisions that violate a specified subdivision of the Act are void and unenforceable. See Engineered Sales Co. v. Endress + Hauser, Inc., 980 F.3d 597 (8th Cir. 2020) (reversing and remanding summary judgment), citing Minn. Stat. § 325E.37.

Example: In Texas, if a contract relates broadly to real property located in Texas and is entered into after September 1, 2025, then (with certain exceptions) a governing-law clause that chooses the law of another state is void as against public policy — ditto for forum-selection clauses requiring litigation in the courts of another state, and arbitration clauses requiring arbitration in another state. Under the former version of the statute, a state court of appeals held that if the forum-selection clause included a waiver of voidability, then that waiver would be enforced; three years later, the Legislature responded by changing the wording to preclude that result. See Tex. Bus. & Comm. Code ch. 272, amended by H.B. 2960. The previous version of the statute was cited in In re MVP Terminalling, LLC, No. 14-21-00399-CV, slip op. (Tex. App—Houston [14th Distr.] Aug. 23, 2022) (conditionally granting mandamus proceeding; by entering into subcontract, subcontractor had contractually waived its statutory right to void forum-selection clause).

21.14.5.16. Some governing-law examples in the wild

Example: In Cardoni, from the Fifth Circuit, Texas law was to govern "[a]ll questions concerning the validity, operation and interpretation of this Agreement and the performance of the obligations imposed upon the parties hereunder[.]" Cardoni v. Prosperity Bank, 805 F.3d 573, 578 (5th Cir. 2015).

Example: In American Insurance, heard by the federal court in West Virginia, the governing law clause was: "This Agreement shall be governed by and construed in accordance with the laws of the State of California applicable to disputes occurring entirely within such State." American Ins. Co. v. Frischkorn, 173 F. Supp. 2d 514, 520-21 (D. W. Va. 2001).

Example: From an Indiana appeals court in Brill: "This Agreement shall be interpreted and the rights of the parties determined under the laws of the Commonwealth of Virginia without regard to the conflict of law provisions thereof." Brill v. Regent Communications, Inc., 12 N.E.3d 299, 306-08 (Ind. App. 2014) (citing cases).

21.14.5.17. Could there be multiple Governing Laws?

It might seem strange to specify a choice of law to govern one particular provision in a contract, such as 3.1 (amendments), but it’s not unheard of. For example:

–  The 1988 update to the Restatement (Second) of Conflicts of Laws states that "the parties may choose to have different issues involving their contract governed by the local law of different states." The comment cites a 1980 Maryland supreme court case in which loan documents for a real-estate project adopted local Maryland law for interest- and usury issues but New York law for others. See Restatement (Second) of Conflicts of Laws, comment i to § 187, citing Kronovet v. Lipchin, 288 Md. 30, 415 A.2d 1096 (1980).

–  In its famous Akorn (2018) decision, the Delaware chancery court observed: "The parties … chose Delaware law to govern the Merger Agreement (excluding internal affairs matters governed by Louisiana law) ….." Akorn, Inc. v. Fresenius Kabi AG, No. 2018–0300–JTL, slip op. at 11 n.14 (Del. Ch. Ct. Oct. 1, 2018), aff'd, 198 A.3d 724 (Del. 2018).

–  The European Union’s Rome I Regulation on contractual obligations states in Article 3.1 that "… By their choice the parties can select the law applicable to the whole or to part only of the contract." (Emphasis added.)

–  An international contract might specify that it is to be governed by the laws of, say, Brazil, but that any arbitration is to be "seated" in England, which might well mean that the arbitration proceedings would be governed by English law. That was precisely the holding of an English court of appeals in a 2012 decision. See Sulamerica CIA Nacional De Seguros SA & Ors v Enesa Engenharia SA & Ors, [2012] EWCA Civ 638, discussed in Sherina Petit and Marion Edge, The governing law of the arbitration agreement Q&A, in Norton Rose Fulbright, Int’l Arbitr. Rpt. 2014 – issue 2.

21.14.5.18. Further reading (optional)

A magisterial treatment can be found in an article by professor John F. Coyle. See John F. Coyle, The Canons of Construction for Choice of Law Clauses, 92 Wash. L. Rev. 631, 648-55 (2017).

In a 2024 blog post, Professor Coyle noted that the non-disclosure agreement between Donald Trump (using a pseudonym) and Stormy Daniels had a "unilateral" or "one-way" governing law clause:

… I had never come across a contract that contained a unilateral choice-of-law clause until last month, when Symeon Symeonides referenced this clause in the non-disclosure agreement between Donald Trump and Stormy Daniels: "This Agreement . . . shall in all respects be construed, interpreted, enforced and governed by the laws of the State of California, Arizona or Nevada at [Trump]’s election." John F. Coyle, Unilateral Choice-of-Law Clauses (tlblog.com 2024) (emphasis added).

21.15. Gross Negligence Definition

21.15.1. Definition

The term "gross negligence" refers to conduct that evinces a reckless disregard for or indifference to the rights of others — tantamount to intentional wrongdoing, and differing in kind, not only in degree, from ordinary negligence.

Note

().  When a contract contains a limitation of a party's liability, the limitation often includes a "carve-out" to the effect that liability is not limited if the party is guilty of gross negligence. Similarly, indemnification provisions such as Protocol 14.3 often exclude indemnity coverage for gross negligence. So it'd be useful to have a reference definition:

This Protocol adopts a middle-ground standard set out by the Court of Appeals of New York (that state's highest court), as discussed in the notes below at 21.15.3.1; see the other notes below for standards used in some other jurisdictions.

21.15.2. Proof requirement

Whenever A alleges that B engaged in gross negligence, A must prove the allegation by clear and convincing evidence (as defined at Protocol 20.11), failing which A WAIVES the allegation.

Note

See the discussion in the commentary to Protocol 20.11 (clear and convincing evidence definition).

21.15.3. Gross negligence: Additional notes

21.15.3.1. Why follow New York's definition here?

This Definition is based on New York law in relation to limitations of liability, because that law seems to strike something of a middle ground:

It is the public policy of this State, however, that a party may not insulate itself from damages caused by grossly negligent conduct. This applies equally to contract clauses purporting to exonerate a party from liability and clauses limiting damages to a nominal sum. …

Gross negligence, when invoked to pierce an agreed-upon limitation of liability in a commercial contract, must smack of intentional wrongdoing. It is conduct that evinces a reckless indifference to the rights of others. Sommer v. Federal Signal Corp., 79 N.Y.2d 540, 554 (1992) (cleaned up).

21.15.3.2. The higher bar of Texas's definition

In Texas, a statute sets the bar for gross negligence quite high, for purposes of liability for punitive damages:

(11) "Gross negligence" means an act or omission:

(A) which when viewed objectively from the standpoint of the actor at the time of its occurrence involves an extreme degree of risk, considering the probability and magnitude of the potential harm to others; and

(B) of which the actor has actual, subjective awareness of the risk involved, but nevertheless proceeds with conscious indifference to the rights, safety, or welfare of others. Tex. Civ. Prac. & Rem. Code 41.001(11), cited in, e.g., Marsillo v. Dunnick, 683 S.W.3d 387, 392-93 (Tex. 2024) (cleaned up, formatting lightly edited; reinstating summary judgment dismissing malpractice claim against physician who had treated snakebite in accordance with standard protocols). This statutory definition is used in § 41.003 of the same code, which conditions any award of punitive damages on a showing, by clear and convincing evidence, of fraud, malice, or gross negligence

Tangentially: The Texas supreme court has held that the statutory term "willful and wanton negligence" meant at least gross negligence. See Marsillo, supra, 683 S.W.3d at 391-92.

21.15.3.3. California's definition: Too vague?

In California, the state's supreme court noted that gross negligence "long has been defined in California and other jurisdictions as either a want of even scant care or an extreme departure from the ordinary standard of conduct." City of Santa Barbara v. Janeway, 41 Cal. 4th 747, 62 Cal. Rptr. 3d 527, 161 P.3d 1095 (2007) (cleaned up, emphasis added).

As in New York, the law in California prohibits limiting liability for gross negligence. See, e.g., City of Santa Barbara v. Superior Court, 41 Cal. 4th 747, 777, 62 Cal. Rptr. 3d 527, 161 P.3d 1095 (2007), where the state's supreme court held that "public policy generally precludes enforcement of an agreement that would remove an obligation to adhere to even a minimal standard of care," cited in In re Facebook, Inc., 402 F. Supp. 3d 767, 800 (N.D. Cal. 2019) (denying motion to dismiss claim that "plausibly allege[d] gross negligence").

21.15.3.4. Would federal law (U.S.) be relevant?

Tangentially: In the federal-court litigation over the notorious "BP oil spill" in the Gulf of Mexico, a federal district court wrote at length about the definition of gross negligence in the context of a federal statute; the court held that proof of reckless conduct wasn't needed for a showing of gross negligence (much as in the California definition discussed above). See In re: Oil Spill by the Oil Rig "Deepwater Horizon" in the Gulf of Mexico, on April 20, 2010, 21 F. Supp. 3d 657, 732-34 ¶¶ 481 et seq., esp. ¶¶ 494 & n.180, 495 (E.D. La. 2014) (findings of fact and conclusions of law).

21.16. Jury Trial Waiver Protocol

21.16.1. WAIVER

Each party WAIVES any right that the party might have to a trial by jury for any dispute arising out of the Con­tract.

Note

In the U.S., the Seventh Amendment to the U.S. Constitution guarantees the right to a jury trial in all "common law" cases (there's also a $20 claim amount). Many contracts, though, state that this right is waived; when a party wants to include a jury-trial waiver in a contract, the party typically doesn't want the expense and uncertainty of being judged by a semi-random group of citizens who likely won't be particularly knowledgeable about the subject matter.

21.16.2. Certification

Each party certifies that the party has not relied — and it promises that it will not rely — on anyone's alleged statement that this waiver would not be enforced.

Note

See the discussion of reliance waivers at Protocol 11.7.

21.16.3. Broad applicability

This Protocol will abide by this Protocol to the greatest extent not specifically prohibited by law.

21.16.4. Additional notes

21.16.4.1. Advance jury-trial waivers are closely scrutinized

In a 2023 decision involving Pizza Hut, the Fifth Circuit explained the historical importance of the right to trial by jury under the Seventh Amendment, and the "utmost care" that must be used in assessing a purported waiver of that right, which must be given "voluntarily and knowingly based on the fact of the case."

21.16.4.2. Caution: Some states ban pre-dispute jury waivers

In California, Georgia, and North Carolina, pre-dispute waivers of jury trial are almost certainly unenforceable (although a waiver after a lawsuit has been filed will likely be given effect).

21.16.4.3. Would an arbitration agreement preempt state law?

If the Federal Arbitration Act applies, then a state's prohibition of advance jury waivers might be preempted, as discussed at 21.1.15.

(Arbitration can be expensive as well, as discussed in the commentary at 21.1.33.3; more and more companies are taking that into account in deciding whether to require consumers and employees to agree to arbitration.)

21.17. Limitation-Shortening Protocol

21.17.1. Applicability if agreed to

  1. When this Protocol is agreed to, the parties follow it whenever any claim is made "relating to" the Con­tract — the quoted term is intended to be a broad one, encompassing a very-wide range of claims.
  2. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol
Note

Subdivision A: Concerning "relating to," see 20.33 ("relating to" is broader than "arising out of").

21.17.2. Commencement deadline: One year after accrual

  1. To assert a claim relating to the Con­tract in a lawsuit or other action, the claimant commences the action no later than the specified time after the claim "accrues," as stated in section 21.17.3.
  2. If the claimant doesn't commence the action within that time, then the claimant is conclusively deemed to have WAIVED the claim.
Note

().  Caution: Depending on the jurisdiction, to "commence" a lawsuit might require, not just that an action be filed within that time, but that a summons and complaint be served as well. (Something similar could be true for arbitration.)

Caution: Check the applicable jurisdiction for limits on just how much the limitation period (i.e., the deadline for filing suit) can be shortened. Example: Michigan's supreme court ruled that a 180-day limitation period in an employment agreement might be unenforceable: "While contractually shortened limitations periods are generally permitted, they require further analysis before enforcement where, as here, a non-negotiated boilerplate agreement is an adhesion contract between an employer and an employee." Rayford v American House Roseville I, LLC, No. 163989, slip op. (Mich. Jul. 31, 2025) (reversing and remanding court of appeals decision).

Subdivision B: Concerning waivers, see Protocol 3.18.

21.17.3. When does accrual happen?

Except as otherwise stated in this Protocol, a claimant's right to bring a claim will accrue upon the first event occurs that gives rise to the claim — even if the claimant doesn't then suspect that the claimant might have a claim.

Note

This section tracks the law in many jurisdictions — but not all, and not under all circumstances — under which, for deadline purposes, a claim of wrongdoing "accrues" at the time of the wrongdoing itself, even if the claimant then had no way of knowing that the claimant might be entitled to bring a lawsuit. See, e.g., Deutsche Bank Nat'l Trust Co. v. Flagstar Capital Markets Corp., 32 N.Y.3d 139, 145-46, 12 N.E.3d 1219, 88 N.Y.S.3d 96 (2018) (affirming dismissal of claim as untimely).

And even where a "discovery rule" applies, a party wanting to file suit must do so within the limitation period after it knows or should know about the possibility of asserting a claim; "inquiry notice doesn’t require that the plaintiff see a fire; it only requires that a plaintiff smell smoke." Mission Integrated Technologies, LLC v. Clemente, No. 24-1932, slip op. at 13-14 (4th Cir. 2025) (affirming summary judgment dismissing various claims and counterclaims); see also id. at 19-21 (plaintiff's fraud claim was subject to discovery rule).

21.17.4. Extension if required by law

If the time specified in the Con­tract for bringing an action is shorter than the time allowed by applicable law, THEN: That time will be automatically extended to the minimum allowable time.

Note

This is intended to be a "savings" clause, to prevent a contract's shortening of the limitation period from being tossed out entirely (and thus having the gap-filler limitation period apply) if the contractual limitation period is too short to pass muster.

21.17.5. Option: Discovery Rule

If this Option is agreed to, AND IF the Con­tract clearly states that the "discovery rule" will apply for one or more categories of claim, THEN: Any claim in any of those categories will accrue only when the claimant first suspected — or reasonably should have suspected — that there might be grounds to make the claim.

Note

().  This section is based on California: under the so-called "discovery rule," a claim for alleged wrongdoing doesn't accrue — and thus the clock doesn't start ticking on the claimant's right to file a lawsuit — until the claimant first had, or reasonably should have had, a suspicion of wrongdoing. See, e.g., Miller v. Bechtel Corp., 33 Cal. 3d 868, 663 P.2d 177 (1983) (affirming summary judgment on limitation grounds), discussed in Jolly v. Eli Lilly & Co., 44 Cal. 3d 1103, 1111, 751 P.2d 923 (1998) (same).

But: Some jurisdictions might not allow parties to adopt the discovery rule, as discussed at 21.17.7.2 below.

21.17.6. Survival of this Protocol

This Protocol will survive termination or expiration of the Con­tract.

Note

On survival clauses generally, see Protocol 18.1.

21.17.7. Additional notes

21.17.7.1. Introduction

In probably the vast majority of jurisdictions, the legislative body has enacted a "statute of limitations" and/or "statute of repose" to set a deadline for bringing a lawsuit after a claim "accrues." But: Often, the law allows parties to a contract to agree to a shortened limitation period in which a claim can be brought, subject to certain limits.

Example: Section 2-275(a) of the Uniform Commercial Code allows parties to a contract for the sale of goods to shorten the limitation period for claims of breach of contract, but not to less than one year ]

21.17.7.2. Can a limitation period be extended by agreement?

Some contracts try to extend, not shorten, the limitation period for a party (usually just one party) to bring contract-related claims, e.g., by stating that the cause of action won't "accrue" until specified events have occurred.

–  That won't work in New York: Under that state's law (which often governs M&A agreements), when a contract contains "reps and warranties," a limitation period for breach of contract begins on the date of the misrepresentation or breached warranty — and parties may not use a contractual "accrual clause" to state that the limitation period won't begin to run until specified conditions precedent have been met. New York's Court of Appeals (that state's highest court) explained this in a 2015 decision. See ACE Securities Corp. v. DB Structured Products, Inc., 25 N.Y.3d 581, 36 N.E.3d 623, 15 N.Y.S.3d 716 (2015) (affirming dismissal of complaint as untimely). ACE Securities was followed in Deutsche Bank Nat'l Trust Co. v. Flagstar Capital Markets Corp., 32 N.Y.3d 139, 12 N.E.3d 1219, 88 N.Y.S.3d 96 (2018) (affirming dismissal of complaint as untimely), discussed in Jennifer Fiorica Delgado, Is New York or Delaware More Protective of the Freedom to Contract? Two Important New York Decisions on the Accrual of Breaches of Representations and Warranties May Shed Light (JDSupra.com 2022).

(The court distinguished cases in which future performance was warranted, as opposed to when the warranty is about a present state of affairs; this is discussed in more detail at 31.40.8.)

–  In contrast, Delaware law might allow parties to agree to just such a postponement of the "accrual" of the claim, as explained decision by that state's chancery court. See Bear Stearns Mtg. Funding Trust 2006-SL1v. v. EMC Mtg. LLC, No. 7701 (Del. Ch. Jan. 12, 2015) (on reconsideration, partially granting motion to dismiss on limitation grounds).

In fact, under a 2014 Delaware statutory amendment, when a written contract involves at least $100,000, the contract may extend the limitation period “provided [the claim] is brought prior to the expiration of 20 years from the accruing of the cause of such action." 10 Del. Code § 8106(c), discussed in Jennifer Fiorica Delgado, supra.

21.17.7.3. Restarting accrual for reps and warranties with a bring-down certificate

Much contract-related litigation arises from claims of breach of representations and warranties (see 16.2) made in contracts.

This is especially relevant in asset sales, mergers, and similar transactions, where the contract typically contains representations and warranties — which under the contract will often be stated to have been made both (i) on the date of signing of the contract; and (ii) on the date of closing the transaction.

The latter possibility might be because, at the closing, the representing party is typically required by the contract to sign and deliver a so-called "bringdown certificate" — otherwise, the other party won't be obligated to close the deal. See, e.g., section 7.2(a) of the Agreement and Plan of Merger under which Capital One is acquiring Discover Bank:

7.2 Conditions to Obligations of Capital One and Merger Sub. The obligation of Capital One and Merger Sub to effect the Merger is also subject to the satisfaction, or waiver by Capital One, at or prior to the Effective Time, of the following conditions:

(a) Representations and Warranties. The representations and warranties of Discover set forth in Section 3.2(a) and Section 3.8(a) … shall be true and correct [*] [sic] … in each case as of the date of this Agreement and as of the Closing Date as though made on and as of the Closing Date …. Capital One shall have received a certificate dated as of the Closing Date and signed on behalf of Discover by the Chief Executive Officer or the Chief Financial Officer of Discover to the foregoing effect.

(Emphasis added.)

[*] Students: In this course, do not write "true and correct" in your assignments, for reasons discussed at 32.38.

21.17.7.4. Fraudulent concealment could "toll" the limitation period (i.e., stop the clock)

The following is a "cleaned up" quotation, essentially verbatim, from the Delaware supreme court's Schurder opinion. From LGM Holdings, LLC v. Schurder, No. 314, 2024, slip op. at 22-23, text accompanying nn.58-65 (Del. Apr. 22, 2025) (reversing and remanding trial court's dismissal of complaint as time-barred) (cleaned up, paragraphing edited).

Under the doctrine of fraudulent concealment, a statute of limitations can be disregarded when a defendant has fraudulently concealed from a plaintiff the facts necessary to put the plaintiff on notice of the truth. Under this doctrine, a plaintiff must allege an affirmative act of "actual artifice" by the defendant that either prevented the plaintiff from gaining knowledge of material facts or led the plaintiff away from the truth.

Where a plaintiff has proved that the defendant fraudulently concealed facts necessary to put the plaintiff on notice, the statute of limitations or survival period governing a claim will be tolled. Tolling suspends or stops the running of a limitations period—it is analogous to a clock stopping and then restarting. The rationale for this doctrine is to disallow a defendant from taking advantage of his own wrong in preventing a plaintiff from filing a timely suit in the courts.

Fraudulent concealment does not, however, toll a statute of limitations or survival period indefinitely. Delaware courts have consistently held that the doctrine of fraudulent concealment does not toll a statute of limitations or survival period beyond the point where the plaintiff was objectively aware, or should have been aware, of facts giving rise to the wrong. Put differently, the limitations period begins to run when the plaintiff is objectively aware of the facts giving rise to the wrong, i.e. on inquiry notice.

21.17.7.5. A really-detailed limitation-period clause

For an example of a really-detailed limitation-period provision, see an article by practitioner-scholar Glenn West, riffing on a provision in a Delaware supreme court case:

Notwithstanding anything herein to the contrary, the obligations to indemnify, pay, reimburse, compensate, and hold harmless a Person pursuant to this ARTICLE IX in respect of a breach of representation or warranty, covenant, or agreement shall terminate on the applicable survival termination date (as set forth in Section  9.1(a)), unless an Indemnified Party shall have made a claim for indemnification pursuant to Section 9.2 or Section 9.3, prior to such survival termination date, as applicable, including by delivering an Indemnification Claim Notice or Third-Party Indemnification Claim, as applicable, to the Indemnifying Party.

The Parties specifically and unambiguously intend and agree that

(a) the survival periods that are set forth in this Section 9.1(a) shall replace any statute of limitations that would otherwise be applicable;

(b) the timely delivery of an Indemnification Claim Notice or Third-Party Indemnification Claim, as applicable, to the Indemnifying Party pursuant to Section 9.2 or Section 9.3 shall be an express condition precedent to the obligations to indemnify, pay, reimburse, compensate, and hold harmless a Person pursuant to the ARTICLE IX;

(c) time shall be of the essence in the delivery of an Indemnification Claim Notice or Third-Party Indemnification Claim, as applicable, to the Indemnifying Party pursuant to Section 9.2 or Section 9.3; and

(d) the survival periods, and the timing and content of an Indemnification Claim Notice or Third-Party Indemnification Claim, as required by this ARTICLE IX, were a material part of the agreed exchange made by the Parties in entering into this Agreement.[37]

See Glenn D. West, A Crack in Delaware’s Contractarianism: The Survival Clause, Claims Notices, and the Law’s Abhorrence of Forfeitures (BusinessLawToday.org 2025) (archived at https://perma.cc/B4XB-NG4Q) (scroll down to Some Possible Additions to the Survival Clause in the text accompanying n.35), discussing Thompson Street Capital Partners IV, L.P. v. Sonova U.S. Hearing Instruments LLC, No. 166, 2024 (Del. Apr. 28, 2025) (reversing and remanding chancery-court dismissal).

21.17.7.6. Sue in a state with a longer limitation period? (A "borrowing statute" might bar it.)

Some states have enacted statutes to preclude a local court from hearing a dispute, arising in a different state, where the statute of limitations has already expired in that different state. Professor Coyle quotes an Idaho statute to that effect:

When a cause of action has arisen in another state or territory, or in a foreign country, and by the laws thereof an action thereon cannot there be maintained against a person by reason of the lapse of time, an action thereon shall not be maintained against him in this state. Idaho Code § 5-239, quoted in John F. Coyle, Demystifying Borrowing Statutes (TLBlog.org 2025), which is adapted from his forthcoming article in the Florida Law Review.

21.18. Limitations of Liability General Provisions Protocol

21.18.1. Applicability if agreed to

When this Protocol is agreed to, it (this Protocol) will govern whenever the Con­tract includes one or more "limitations of liability," namely any one or more of the following (without limitation):

  1. a disclaimer of one or more warranties (see Protocol 16.1);
  2. a cap on damages and/or other monetary relief (see Protocol 21.7), including but not limited to attorney fees (see Protocol 21.2), possibly with different caps for different classes of liability;
  3. an exclusion of one or more specified types of monetary relief, including but not limited to consequential damages 1(see Protocol 21.5), when applicable; and
  4. an exclusion or limitation of any other types of remedy, including but not limited to injunctive relief (see Protocol 21.10).
Note

().  Drafters of limitation-of-liability clauses will often go into some detail about how broadly the parties intend for the clause to apply. To save time and money (for both the drafter and the other side's reviewer), the following clause provides a standardized statement to that effect.

Categories of liability caps are becoming "a thing," especially when it comes to liability for data breaches. Example: Authors from one of the largest Canadian law firms noted:

1.  Separate liability caps. One of the most significant findings of the [recent] study was the widespread use of separate liability caps for data breaches.

  • About 75% of agreements imposed a cap on data-related liability,
  • and of those, 65% featured a distinct cap for data issues.

This approach reflects the heightened risk of data breaches while avoiding unlimited liability, allowing parties to bridge the gap between a general limitation of liability and the reality of potentially catastrophic data losses. Alexandra Luchenko, Ellie Marshall, Robert Percival, and Karl Qin, Data Liability in Technology Contracts: Insights from Recent Trends, item 1 (JDSupra.com 2025) (extra paragraphing and bullets added).

21.18.2. Parties' informed decisions

In agreeing to limitations of liability as part of the Con­tract (or as part of a purchase order or work order that incorporates the Con­tract), the parties:

  1. recognize that one party could fail to perform one or more of its relevant obligations — a "breach";
  2. understand that the breach could cause harm ("damage") to the other party; and
  3. have taken into account the associated business- and other risks; the economics; and other considerations relevant to the Con­tract.
Note

This § 21.18.2 is modeled on the introduction to the limitation of liability in Alabama Aircraft (11th Cir. 2025). See Alabama Aircraft Indus., Inc. v. Boeing Co., 133 F.4th 1238, 1245 (11th Cir. 2025) (reversing and remanding dismissal of AAI's complaint).

21.18.3. Persons protected

Unless the Con­tract clearly states otherwise, each limitation of liability in the Con­tract will apply to each of the following (each, a "Protected Person"):

  1. each signatory party to the Con­tract;
  2. that party's "affiliates," as defined in U.S. Securities and Exchange Commission regulations; and
  3. the officers, directors, managers, members, employees, shareholders, and other individuals holding similar positions, in each organization within the scope of this section 21.18.3.
Note

This section explicitly states that individual employees (and others) are protected by any limitations of liability in the Con­tract, which could be important. Example: The State of Oregon once sued Oracle over alleged problems in implementing the state's Obamacare exchange system. The state sued not just Oracle itself, but also various Oracle employees personally — including a demand that an Oracle technical manager personally pay the state $45 million (!). (This is discussed in more detail at 17.6.)

21.18.4. All claims for relief are covered by this Protocol.

Unless clearly stated otherwise in the Con­tract (or by law), each limitation of liability in the Con­tract (if any) applies to all claims for relief:

  1. regardless of the label given to the relief, such as, for example, "consequential damages" (see Protocol 21.5), "special damages" or "exemplary damages" or "punitive damages" or "disgorgement" or "attorney fees" or "costs"; and
  2. whether the purported basis for the relief is grounded in contract law; negligence or other tort law; unjust enrichment; promissory estoppel; or any other principle of law or equity.
Note

().  Note: In Protocol 21.7 (damages caps), § 21.7.6 states that a damages cap does not limit claims for specified monetary amounts.

This section explicitly mentions not only contract claims but also tort-based claims and any other. Example: This is inspired by a partial failure of a limitation of liability in Facebook's terms of service after a data breach, because the imitation of liability there did not even mention negligence, "let alone unequivocally preclude liability for negligence." Bass v. Facebook Inc., 394 F. Supp. 1024, 1037, 1038 (N.D. Cal. 2019) (granting in part, but denying in part, Facebook's motion to dismiss).

Similarly: In a trade-secret case, where aircraft manufacturer Boeing was a defendant, the Eleventh Circuit held that the contract's limitation of liability provision covered various forms of damages but did not cover the plaintiff's claim for unjust enrichment. See Alabama Aircraft Indus. Inc. v. Boeing Co., No. 20-11141, slip op. at part II.D (11th Cir. Apr. 4, 2025)

Local law might make limitations of liability unenforceable in particular circumstances. Example: California's supreme court held that state law precluded contractually limiting liability for "willful injury to the person or property of another" — in this case, alleged tortious interference with contractual relations. See New England Country Foods, LLC, v. Vanlaw Food Prods., Inc., No. S282968, slip op. (Cal. Apr. 24, 2025) (on certification from 9th Cir.), citing Cal. Civ. Code § 1668.

21.18.5. Limitations of liability are "material."

Each limitation of liability in the Con­tract is a fundamental part of the parties' bargain; in deciding to enter into the Con­tract on the agreed terms, each party has relied on the limitations of liability stated in the Con­tract.

Note

Explanations such as in the above text can be helpful in explaining to a court why the parties reached the particular agreement that they did. Example: Such an explanation seems to have paid off for a defendant in a Tenth Circuit case, where the court noted that "in the License Agreement itself, they [the parties] explained the reason for their decision to limit the damages available in the event of breach …." SOLIDFX, LLC v. Jeppesen Sanderson, Inc., 841 F.3d 827, 837 (10th Cir. 2016) (vacating and remanding judgment on jury verdict); after remand, No. 18-1082, slip op. at 12-13 (10th Cir. Aug. 4, 2020) (unpublished; reiterating the point in affirming trial-court judgment in relevant part).

21.18.6. No seeking of inconsistent relief

Each party specifically agrees never to seek relief that is inconsistent with any limitation of liability stated in the Con­tract:

  1. even if some or all agreed limited remedies failed of their essential purpose; and
  2. even if the liable party and/or its agents knew, at the relevant time, of special circumstances, for example, circumstances giving rise to the possibility or even the high probability of such damages.
Note

().  This section is intended to make it a rule that, if the other party did seek excluded damages, that would itself be a breach of contract. That way, any party that does seek such excess damages would be breaching the express covenant — and potentially liable for damages itself. (See the additional discussion at 10.2.)

Active voice is used here in view of a Texas supreme court's holding that seemed to go out of its way to find that passive-voice language to that effect was merely a waiver of consequential damages, not a covenant not to seek such damages. See James Constr. Grp., LLC v. Westlake Chem. Corp., 594 S.W.3d 722, 763 (Tex. App.—Houston [14th Dist.] 2019), aff'd in pertinent part, 650 S.W.3d 392, 415 (Tex. 2022).

Subdivision 1: It's useful to address the "failed of their essential purpose" issue because that issue has sometimes arisen in litigation.

In the Uniform Commercial Code, section 2-719(2) provides: "Where circumstances cause an exclusive or limited remedy to fail of its essential purpose, remedy may be had as provided in this Act." This means that in an Article 2 case for the sale of goods, if providing a correction or workaround for a defect is the customer's exclusive remedy, but the provider is unable to make good on doing so, then in some jurisdictions, all limitations of liability might be out the window — including for example an exclusion of consequential damages or a cap on damages. See Sanchelima Int'l, Inc. v. Walker Stainless Equipment Co., 920 F.3d 1141 (7th Cir. 2019) (affirming negation of consequential-damages exclusion), which discusses this point with citations; Hawaiian Tel. Co. v. Microform Data Sys., 829 F.2d 919, 923-24 (9th Cir. 1987) (affirming award of consequential damages); RRX Industries, Inc. v. Lab-Con, Inc., 772 F.2d 543, 547 (9th Cir. 1985) (affirming negation of consequential-damages disclaimer; "each case must stand on its own facts"); Prairie River Home Care, Inc. v. Procura, LLC, No. 17-5121 (D. Minn. Jul. 10, 2019) (denying motion to dismiss claim for consequential damages because limited remedies had failed).

Not all jurisdictions follow this guideline, though. See Appalachian Leasing, Inc. v. Mack Trucks, Inc., 234 W. Va. 334 765 S.E.2d 223, 232 (2014) (reversing and remanding, on other grounds, summary judgment in favor of truck manufacturer; "where an express warranty fails of its essential purpose thereby allowing the buyer to pursue remedies and damages under … [the] Uniform Commercial Code, the seller’s exclusion of consequential damages from the express warranty remains in effect, unless the exclusion is unconscionable") (emphasis added).

Subdivision 2 — "special circumstances": See the discussion at Protocol 21.5 (consequential damages).

21.18.7. Assumption of certain related risks

Each party KNOWINGLY ASSUMES THE RISK that it might suffer damages in excess of amounts excluded, capped, or otherwise limited by the Con­tract.

Note

"Assumption of the risk" language of this kind can sometimes help persuade a court to enforce the parties' bargain, even though the party that assumed the risk is trying to get out of that bargain.

21.19. Liquidated-Damages Protocol [to come]

To be drafted

21.19.1. Additional notes

21.19.1.1. Business background: Why contracts sometimes specify liquidated damages

The term "liquidated damages" refers to an approach where parties to a contract stipulate, at the time they enter into the contract, what "dollar amount" of damages is to be awarded in case of a breach of the contract. That way, if a breach does happen, in theory the parties needn't litigate the amount of the monetary recovery.

Relying on freedom-of-contract principles, courts in the U.S. will enforce a liquidated-damages clause if the clause genuinely represents a reasonable advance estimate of the amount of damages that would be suffered in case of breach.

As then-Judge Richard Posner said in a 2004 opinion: "One could even think of a liquidated damages clause as a partial settlement, as in cases in which damages are stipulated and trial confined to liability issues. And of course settlements are favored." See, e.g., American Consulting, Inc. v. Hannum Wagle & Cline Engineering, Inc., 136 N.E.3d 208 (Ind. 2019) (affirming, in pertinent part, summary judgment that liquidated-damages clause was unenforceable; remanding for trial of claim for actual damages).

Liquidated damages? Penalty? Which is it?

The Supreme Court of Ohio once explained the difference between liquidated damages and penalties:

[A penalty is] a sum inserted in a contract, not as the measure of compensation for its breach, but rather as a punishment for default, or by way of security for actual damages which may be sustained by reason of nonperformance, and it involves the idea of punishment.

A penalty is an agreement to pay a stipulated sum on breach of contract, irrespective of the damage sustained. Its essence is a payment of money stipulated as in terrorem of the offending party,

  • while the essence of liquidated damages is a genuine covenanted pre-estimate of damages.

The amount is fixed and is not subject to change;

  • however, if the stipulated sum is deemed to be a penalty, it is not enforceable
  • and the nondefaulting party is left to the recovery of such actual damages as he can prove. Boone Coleman Constr., Inc. v. Village of Piketon, 2016 Ohio 628 (Ohio), ¶ 17 (reversing holding that liquidated-damages clause in a public road construction contract was an unenforceable penalty; formatting edited), on remand, 2016 Ohio 1557 (Ohio App.).
Saying "and not as a penalty" won't convince a court

In some contracts, the liquidated-damages provision proclaims that the party breaching the contract will pay a stated amount as liquidated damages and not as a penalty. See, e.g., section 10.5.2 of the 2000 "Agreement" between Amazon and Drugstores.com, which states in part:

10.5.2  Liquidated Damages for Breach. Upon termination by ACI for drugstore.com's breach pursuant to Section 10.2, drugstore.com will immediately pay ACI, as liquidated damages, and not as a penalty, such amount as mutually agreed [sic] by the Parties.

Upon termination by drugstore.com for ACI's breach pursuant to Section 10.2, ACI will immediately pay, as liquidated damages, and not as a penalty, such amount as mutually agreed [sic] by the Parties.

(Emphasis and extra paragraphing added.) And yes, "Agreement" is the title of the contract — which isn't especially helpful, is it?

It's even worse than that: By not specifying how the amount of damages is to be computed, the drafters made this clause worthless — not to mention that the "such amount as mutually agreed" language makes the clause an unenforceable agreement to agree (see 28.7).

Many courts, however, simply ignore such "not as a penalty!" language as self-serving, in roughly the same vein as "Pay no attention to that man behind the curtain!" from the movie The Wizard of Oz.

Example: A California appellate court noted that "public policy [about liquidated damages] may not be circumvented by words used in a contract; that whether or not a particular clause is a penalty or forfeiture or a bona fide provision for liquidated damages depends upon the actual facts existing at the time the contract is executed …." Purcell v. Schweitzer, 224 Cal. App. 4th 969, 974 169 Cal. Rptr. 3d 90 (2014).

21.19.1.2. Basic issues for liquidated-damages drafters

Drafters looking to create a liquidated-damages provision should think about the following:

  • Which party could be liable for liquidated damages?
  • What type(s) of breach would result in liability for liquidated damages? (Example: Delay in completion.)
  • How much would the liquidated damages be? Fill in a reasonable estimate of the damages that would be suffered from the specified type(s) of breach; this will require need some thought, for reasons discussed in the additional notes below.

And just saying "such amount as the parties agree" almost certainly won't cut it, because it'd be an unenforceable agreement to agree; see 28.7.

For language setting forth liquidated damages calculated per day of delay, see Federal Acquisition Regulations § 52.211.11.

Liquidated damages based on revenue, not profit, might be enforceable. Example: See RSA 1 L.P. v. Paramount Software Assoc., Inc., 793 F.3d 903 (8th Cir. 2015) (affirming summary judgment awarding liquidated damages; applying Texas law).

21.19.1.3. Pro tip: Use an alternative performance standard instead?

Drafters might want to consider setting up an alternative-performance structure instead of liquidated damages. For example:

–  Example: What amounts to an early-termination fee was upheld in a 2014 First Circuit case, where the court of appeals affirmed a summary judgment that Alasko, a Canadian food distributor, owed Foodmark, a U.S. marketing firm, a fee for electing not to renew the parties' "evergreen" agreement. See Foodmark, Inc. v. Alasko Foods, Inc., 768 F.3d 42 (1st Cir. 2014).

–  Example: A California appeals court reversed and remanded a summary adjudication that certain payment provisions in a contract were an unenforceable penalty; the court held that "the trial court erred because More-Gas's motion for summary adjudication failed to eliminate the possibility that the contractual provisions in question were instead valid provisions for alternative performance." McGuire v. More-Gas Investments, LLC, 220 Cal. App. 4th 512, 163 Cal. Rptr. 3d 225 ]

–  Example: Washington state's supreme court ruled that an early termination fee in a cell-phone service agreement was "an alternative performance provision and not a liquidated damages clause." Minnick v. Clearwire US LLC, 275 P.3d 1127, 1129 (Wash. 2012).

– Example: California's supreme court agreed that a cotenancy provision in a shopping center real-estate lease — allowing a tenant to pay a reduced rent in certain instances — was valid as alternative performance. (Part I of the court's opinion sets out a detailed discussion of the business background of cotenancy provisions.) See JJD-HOV Elk Grove, LLC v. Jo-Ann Stores, LLC, No. S275843, slip op. (Cal. Dec. 19, 2024) (affirming court of appeal and trial court).

–  Example: But: A California court ruled that Sprint that "Plaintiffs introduced contemporaneous Sprint internal documents referring to the ETF as a '$150 contract penalty fee,' and as a 'Penalty or Contract Cancellation Fee.'" Pro tip: This case points out an obvious lesson for drafters and clients: Don't use the word penalty when referring to fees. Cellphone Fee Termination Cases, 193 Cal. App.4th 298, 306, 122 Cal. Rptr.3d 726 (2011).

21.19.1.4. Second-look courts want reasonable correlation with actual damages

Caution counsels contract drafters to assume that their liquidated-damages clauses will be judged by a court in a so-called "second look" jurisdiction.

The difference between the "second look" approach and that used by "single look" courts was explained by Massachusetts's highest court:

–  In a "single look" jurisdiction, "a liquidated damages clause will be enforced if (1) the actual damages resulting from a breach were difficult to ascertain at the time the contract was signed; and (2) the sum agreed on as liquidated damages represents a reasonable forecast of damages expected to occur in the event of a breach."

–  In contrast, in "second look" jurisdictions, courts consider "the circumstances at the time of the breach …. allow[ing] for an after-the-fact adjustment to avoid a windfall for the party not committing the breach by assessing the reasonableness against the actual damages resulting from the breach."

The court reiterated that Massachusetts is a single-look jurisdiction, because:

[With a single-look analysis:] By assigning a specific value to a contract breach ahead of time, a liquidated damages clause has the potential to promote certainty, resolve disputes efficiently, and, notwithstanding the instant case, avoid litigation.

In contrast, the second look approach encourages an aggrieved party to bring suit and attempt to show evidence of damage due to a contract breach.

That is, under the second-look approach, the parties must fully litigate (at great expense and delay) that which they sought not to litigate.

For this reason, we have squarely rejected the second look approach.

* * * 

When parties agree in advance to a sum certain that represents a reasonable estimate of potential damages, they exchange the opportunity to determine actual damages after a breach, including possible mitigation, for the peace of mind and certainty of result afforded by a liquidated damages clause.

In such circumstances, to consider whether a plaintiff has mitigated its damages not only is illogical, but also defeats the purpose of liquidated damages provisions. Cummings Prop., LLC v. Hines, 492 Mass. 867, 868, 872 (2023) (cleaned up, formatting revised).

Texas is a second-look jurisdiction. the Supreme Court of Texas held that for a liquidated-damages clause to be enforceable:

  • actual damages must be difficult to estimate, and the agreed liquidated damages must be a reasonable forecast of the actual damage; but also:
  • if in practice the actual damages and the agreed liquidated damages end up being too far apart, then the liquidated-damages provision will be struck down as a penalty.

In that case, the Texas supreme court noted that the highest actual damages supported by the evidence was $6 million, but the liquidated-damages amount assessed by the court below was $29 million. The court said that this was an unacceptable disparity: "When the liquidated damages provisions operate with no rational relationship to actual damages, thus rendering the provisions unreasonable in light of actual damages, they are unenforceable." FPL Energy, LLC, v. TXU Portfolio Management Company, L.P., 426 S.W.3d 59,69-70, 72 (Tex. 2014) (reversing court of appeals and holding that liquidated-damages provision was unenforceable) (emphasis added, citations omitted).

Example: To like effect, the Seventh Circuit rejected a claim for liquidated damages for breach of a confidentiality provision in a settlement agreement:

  • The liquidated-damages provision required a payment of $10,000 for each unauthorized disclosure of the terms of the settlement agreement.
  • The party accused of breaching the confidentiality provision had included detailed information about the settlement in a franchise disclosure document that was distributed to about 2,000 people, not all of whom were required by law to be given a copy.
  • The plaintiff sued for liquidated damages of 2,000 times $10,000, or $20 million.

Applying Texas law, the trial court held that this was unreasonable, because the plaintiff had not proven that she had suffered any harm at all, let alone $20 million worth. The Seventh Circuit affirmed; Judge Posner said that, "when there is an unbridgeable discrepancy between liquidated damages provisions as written and the unfortunate reality in application, we cannot enforce such provisions." Caudill v. Keller Williams Realty, Inc., 828 F.3d 575, 577 (7th Cir. 2016) (internal quotation marks and citation omitted), quoting FPL Energy, supra; see also Atrium Medical Center, LP v. Houston Red C LLP, 595 S.W.3d 188, 198 (Tex. 2020) (affirming court of appeals).

New York is also a second-look jurisdiction, as explained by that state's highest court in affirming the unenforceability of a liquidated-damages provision:

Under our well-established rules of contract, the Surrender Agreement’s liquidated damages provision does not fairly compensate plaintiff for defendant’s delayed installment payments.

The provision calls for a sum more than sevenfold the amount due if defendant had complied fully with the Surrender Agreement. We cannot enforce such an obviously and grossly disproportionate award without offending our State’s public policy against the imposition of penalties or forfeitures for which there is no statutory authority. Trustees of Columbia Univ. v. D'Agostino Supermarkets, Inc., 36 N.Y.3d 69, 80, 162 N.E.3d 727, 138 N.Y.S.3d 498 (2020) (cleaned up, emphasis and extra paragraphing added).

Example: As another example of what not to do: In an Indiana case, the state supreme court affirmed striking down the liquidated-damages clauses in question for breach of an employment agreement's post-employment covenant. The covenant required the employee agreed not to solicit the employer's customers or recruit the employer's employees; the court summarized those clauses:

He agreed that if he breached this agreement and such a breach resulted in termination, withdrawal or reduction of a client's business with ASI, he would pay liquidated damages in an amount equal to 45% of all fees and other amounts that ASI billed to the customer during the twelve months prior to the breach.

The contract further precluded Knowles from causing an employee to end their employment with ASI, and if he breached this provision, he agreed to pay liquidated damages equal to 50% of the employee's pay from ASI during the twelve months prior to the breach.

Day and Lancet, who were both resident project representatives at ASI, also executed agreements that precluded them from hiring or employing ASI employees. They agreed that if they breached their agreements, they would pay liquidated damages in an amount equal to 100% of that employee's pay from ASI during the twelve months prior to breach.

The court did not see much correlation between the liquidated damages and the actual damages that the non-breaching party was likely to have suffered. American Consulting, Inc. v. Hannum Wagle & Cline Eng'g, Inc., 136 N.E.3d 208, 209-10, 212 (Ind. 2019) (affirming, in pertinent part, summary judgment that liquidated-damages clause was unenforceable; remanding for trial of claim for actual damages) (formatting edited).

Notice the "hill of proof" here:

  • The plaintiff first must "get up the hill" (discussed at 16.2.2) by showing what things looked like to the parties at the time the agreement was made;
  • If the plaintiff is successful, the defendant can still try to "force the plaintiff off the hill" by showing that as things turned out, there was an "unbridgeable discrepancy."
21.19.1.5. So: Don't be ridiculous in hindsight

Continuing the theme explored above: It can be dangerous to set a liquidated-damages amount that — in hindsight — ends up being ridiculously disproportionate to the "real" damages.

21.19.1.6. But some courts still say: No Monday-morning quarterbacking

In contrast to the holdings discussed above, some courts discourage the use of hindsight in assessing liquidated-damages provisions. Example: In a case involving a public-works contract, the Ohio supreme court explained:

{¶ 35} We reaffirm that Ohio law requires a court, when considering a liquidated-damages provision, to examine it in light of what the parties knew at the time the contract was formed.

If the provision was reasonable at the time of formation and it bears a reasonable (not necessarily exact) relation to actual damages, the provision will be enforced.

{¶ 36} This prospective or "front end" analysis of a liquidated-damages provision focuses on the reasonableness of the clause at the time the contract was executed rather than looking at the provision retrospectively, i.e., ascertaining the reasonableness of the damages with the benefit of hindsight after a breach.

The prospective approach properly focuses on whether[:]

(1) the parties evaluated, at the time of contract formation, the probable loss resulting from delay in completing the construction,

(2) the parties clearly intended to use liquidated damages in case of a delay because actual damages would be difficult to ascertain, and

(3) [in per-diem cases,] the parties reached an agreement as to a per diem amount for delays.

[P]rospective analysis resolves disputes efficiently by making it unnecessary to wait until actual damages from a breach are proved and eliminates uncertainty and tends to prevent costly future litigation.

The reasonableness of the forecast or estimate in a liquidated-damages provision is usually determined in view of the facts known at the time of contracting, and not at the time of the breach or delayed completion. Boone Coleman Constr., Inc. v. Village of Piketon, 2016 Ohio 628 (Ohio), ¶ 35-36 (reversing holding that liquidated-damages clause in a public road construction contract was an unenforceable penalty; quotation altered, extensive citations omitted), on remand, 2016 Ohio 1557 (Ohio App.).

In the same case where he talked about liquidated damages as "a partial settlement," Judge Richard Posner mused:

Indeed, even if damages wouldn't be difficult to determine after the fact, it is hard to see why the parties shouldn't be allowed to substitute their own ex ante determination for the ex post determination of a court. Damages would be just another contract provision that parties would be permitted to negotiate under the general rubric of freedom of contract. XCO Int'l, Inc. v. Pacific Scientific Co., 369 F.3d 998, 1001 (7th Cir. 2004) (Posner, J.).

Judge Posner's view was quoted in a dissent by an Indiana supreme court justice, who argued that:

Rather than condemning such [liquidated] damages when judges conclude they are facially problematic, courts should get out of the business of deciding whether the parties' estimate of the harm underlying liquidated damages is reasonable. … This approach to liquidated damages here would have the virtue of honoring the parties' freedom of contract, including their settlement of a disputed issue it has taken our Court more than a year to resolve. American Consulting, Inc. v. Hannum Wagle & Cline Engineering, Inc., 136 N.E.3d 208, 220 (Ind. 2019) (Slaughter, J., dissenting in part). (quotation altered).

21.19.1.7. Pay attention to the scope of a liquidated-damages clause

Example: In a Connecticut case, a contract required a contractor to clean up an industrial site by a certain deadline; the contract also required the contractor to pay liquidated damages in a specified amount for every day of delay. The appeals court held that this did not preclude the customer from recovering additional damages that were not attributable to delay. See New Milford v. Standard Demolition Services, Inc., 212 Conn. App. 30, 274 A.3d 911, 943 (2022).

21.19.1.8. Disgorgement of profits ≠ "liquidated damages"

Example: The Eleventh Circuit reviewed a provision in a confidentiality agreement to the effect that, if a party received confidential information from a discloser and violated the agreement's restrictions, then the recipient must pay the discloser all of the recipient's profits arising from the violation. Affirming a lower-court decision, the court held that:

The formula employed in § 5 of the MCA [Mutual Confidentiality Agreement] is not a reasonable method for approximating the probable loss because it is based entirely on the breaching party’s profits, and not on the injury suffered by the non-breaching party. … This discrepancy directly contravenes the traditional principle of contract law that damages should put the injured party in the position he would be in had the contract been performed. The liquidated damages provision here stands that principle on its head because it places SIS, the nonbreaching party, in a far better position than it would have been if the contract had never been breached by Stoneridge.

For example, under § 5 of the MCA, SIS is entitled to “all forms of compensation or benefits which [Stoneridge] directly or indirectly realizes as a result of such breach.” This liquidated damages provision therefore resembles a disgorgement remedy, meaning that it permits a plaintiff to recover the defendant’s profits from breach, even if they exceed the provable loss to the plaintiff from the defendant’s defaulted performance, which is not an available remedy for breach of contract under Georgia law.

Because § 5 of the MCA gives SIS all direct or indirect profits earned by Stoneridge irrespective of the actual profits that SIS lost, it does not provide a reasonable pre-estimate of the probable loss.

This liquidated damages provision instead functions more like a penalty than a reasonable pre-estimate of the probable loss. … SIS, LLC v. Stoneridge Holdings, Inc., No. 21-13567, slip op. at part II.B, pp.12-13 (11th Cir. Jan. 12, 2023) (per curiam, affirming judgment on jury verdict; cleaned up, formatting modified).

21.19.1.9. Will particular statutes govern liquidated damages?

Drafters should check whether a relevant jurisdiction might have statutory constraints on liquidated damages. For example, section 92.019 of the Texas Property Code restricts a residential landlord's right to charge late fee for late rent payment, in terms that sound very much like liquidated damages:

(a) A [residential] landlord may not charge a tenant a late fee for failing to pay rent unless:

      (1) notice of the fee is included in a written lease;

      (2) the fee is a reasonable estimate of uncertain damages to the landlord that are incapable of precise calculation and result from late payment of rent; and

      (3) the rent has remained unpaid one full day after the date the rent was originally due.

(b) A late fee under this section may include an initial fee and a daily fee for each day the rent continues to remain unpaid. Tex. Prop. Code § 92.019.

Example: The Fifth Circuit, making an Erie guess about how Texas courts would interpret the statute, held that "a reasonable estimate" did not require a landlord to engage in advance in any kind of process to develop the estimate. Cleven v. Mid-America Apt. Communities, Inc., 20 F.4th 171, 177 (5th Cir. 2021) (reversing and remanding class certification).

21.19.1.10. Ideas for computing liquidated damages

See Michael D. Jefferson, Should Commercial Owners Require Liquidated Damages? (DWT.com 2024), also at JDSupra.com.

21.20. Service of Process Streamlining Protocol

21.20.1. Service by certain forms of notice How may legal process be

To the extent not prohibited by law: In any dispute arising out of or relating to the Con­tract, any party to the Con­tract may cause legal process to be served upon another party to the Con­tract:

  1. by notice by certified mail or established independent courier with written confirmation of delivery by the delivery service; and/or
  2. by any other method permitted by law.
Note

().  "Service of process" is something that happens in litigation. Common examples are:

  1. a summons and complaint to kick off a lawsuit, and
  2. a subpoena ordering an individual or company to produce documents and/or to testify at a deposition or at trial.

    Service of legal process is generally done by law-enforcement officers, or in some cases by commercial process servers, who file a report that they have completed serving the person in question.

    The U.S. federal system allows relatively-simple service of process, as described in the Federal Rules of Civil Procedure. See generally Fed. R. Civ. P. 4(c) through 4(m) (service of summons and complaint) and 45 (service of subpoena).

    It's well-established that parties can agree to a streamlined procedure. See, e.g., Rockefeller Tech. Investments (Asia) VII v. Changzhou SinoType Tech. Co., Ltd., 9 Cal. 5th 125, 143-33 (2020); examples of such real-life provisions can be seen at LawInsider.com ]

21.20.2. Service by email?

In itself, this Protocol neither authorizes nor prohibits service of process by email — whether that would be permissible is to be determined by applicable law.

Note

Service of process by email might be allowed by court rule (perhaps requiring court permission) as an alternative form of service, for example under Rule 4(f)(3) of the Federal Rules of Civil Procedure.

Example: In 2023, a New York state appeals court affirmed a default judgment of more than $10 million against an individual securities-fraud defendant who had been served with process by email. See NMR e-Tailing LLC v Oak Inv. Partners, 2023 NY Slip Op 02830, 216 A.D.3d 572, 190 N.Y.S.3d 311 (App. Div. 1st Dept.).

Example: In 2018, the Southern District of New York granted a motion, by a group of educational publishers, to allow service of process by email against foreign online retailers who sold counterfeit textbooks via storefronts on eBay, in violation of the publishers' copyright and trademark rights. See Elsevier, Inc. v. Siew Yee Chew, 287 F. Supp. 3d 374 (S.D.N.Y. 2018) (citing cases); see also, e.g., Sulzer Mixpac AG v. Medenstar Indus. Co., No. 15 Civ. 1668, slip op. (S.D.N.Y. Nov. 30, 2015) (same).

Counterexample: In a 2021 Eleventh Circuit case, the court held that emailing a "courtesy copy" of a legal process document was not enough to effect timely service under the relevant statute, absent express written consent by the recipient to being served in that manner. See O’Neal Constructors, LLC v. DRT America, LLC, 991 F.3d 1376 (11th Cir. 2021) (affirming confirmation of arbitration award and denial of motion to vacate).

21.21. Settlement Discussion Limited Admissibility Protocol

21.21.1. Applicability if agreed to

When this Protocol is agreed to, the parties follow it whenever the parties engage in discussions to settle an actual controversy between them.

Note

().  Background: When parties do, or could, get into a lawsuit or arbitration, they'll often explore settlement possibilities — but they might play their cards close to the vest, for fear of having their words quoted back at them at trial, which might make it more difficult for the parties to reach agreement about a settlement.

So, this Protocol seeks to encourage frank and open discussion of settlement possibilities by strictly limiting the admissibility of certain statements made in such discussions, in the same general manner as Rule 408 of the [U.S.] Federal Rules of Evidence.

For discussion of the "actual controversy" requirement, see the commentary to Protocol 21.11.25.5 (escalation to neutral).

21.21.2. Limts on admissibility

The parties will use each other's statements (concerning the controversy) only as provided in Rule 408 of the [U.S.] Federal Rules of Evidence except as otherwise agreed — even if Rule 408 would not govern in the particular circumstances.

Note

Federal Rule 408 has a long history and seems to be widely accepted as a sensible approach.

21.21.3. Broad applicability

In case of doubt, this Protocol covers, without limitation:

  1. communications during escalation of a dispute, whether internal or to a neutral advisor; and
  2. the results of any evaluation by a neutral.

21.21.4. Survival after termination

This Protocol will survive any termination or expiration of the Con­tract.

Note

See also Protocol 18.1 concerning survival generally.

21.22. Settlement Offer Rejection Protocol

21.22.1. Covered disputes

In the interest of getting disputes settled more quickly and at lower cost: When this Rule is part of the Con­tract, it will apply in any "Dispute," namely any litigation or arbitration arising out of or relating to:

  1. the Con­tract, and/or
  2. any transaction or relationship resulting from the Con­tract.
Note

().  In litigation, sometimes a party will reject a settlement offer, but then when all is said and done, the final outcome turns out not to be even as favorable to the refusing party as the settlement offer — and when that happens, considerable time and money has been largely wasted by the parties and by the court.

So: This Protocol is intended to create incentives for a party to think long and hard before rejecting a settlement offer that invokes this Protocol.

Example: In 2018, Grammy Award-winning singer-songwriter Tracy Chapman, perhaps best known for her 1988 hit song "Fast Car" — which 35 years later became a country-music number one and CMA Song of the Year winner when covered by Luke Combs — sued hip-hop star Nicki Minaj, alleging that Minaj's song "Sorry" infringed the copyright in anothe Chapman song, "Baby Can I Hold You." Eventually Minaj made an offer of judgment under Rule 68, proposing to settle the case by paying Chapman $450,000; Chapman accepted the offer. See Anastasia Tsioulcas, Tracy Chapman Wins Lawsuit Against Nicki Minaj (NPR.org Jan. 8, 2021).

This § 21.22.1 is intended to make it clear that this Rule is to be applied broadly.

The term any transaction or relationship … is modeled on a provision in an arbitration agreement that has been litigated at least twice. See Sherer v. Green Tree Servicing LLC, 548 F.3d 379, 382-83 (5th Cir. 2008), citing Blinco v. Green Tree Servicing LLC, 400 F.3d 1308, 1310 (11th Cir. 2005).

21.22.2. Triggers: Prerequisites for this Protocol

This Rule will apply whenever:

  1. a party (the "Offering Party") makes an offer (the "Settlement Offer"), to another party, to settle a dispute relating to the Con­tract; and
  2. the offer clearly states, in effect, that it (the offer) is subject to this Rule.
  3. the other party (the "Rejecting Party") doesn't timely accept the Settlement Offer; and
  4. the final outcome in the dispute is not at least 10% more favorable to the rejecting party than the Settlement Offer.
Note

().  Subdivision 2: The "clearly states" requirement is intended to prevent a party from being ambushed by another party's after-the-fact claim that (for example) a vague prior settlement proposal from the other party was supposedly a Settlement Offer under this Rule.

().  Subdivision 4: The 10% figure allows a slight margin of error for a rejecting party — unlike Federal Rule 68, which provides no such margin of error. (Florida and Georgia use a 25-percentage-point margin of error, while New Jersey and Texas provide a 20-percentage-point margin.)

21.22.3. Consequences of rejection

  1. The Rejecting Party will pay or reimburse the Offering Party for all attorney fees (see 21.2 that the Offering Party incurred in the dispute after making the Settlement Offer.
  2. Upon request by the Offering Party: The tribunal, in its discretion, may order the Rejecting Party to post a bond, in an amount sufficient to cover the estimated amount of those attorney fees.
  3. If — for any reason — the Rejecting Party does not timely post the required bond, THEN the parties hereby jointly request that the tribunal issue an order striking the Rejecting Party's relevant claims, counterclaims, and/or defenses and entering judgment in favor of the Offering Party.
Note

Subdivision 2: The "tribunal" would be the court in a lawsuit, or (if applicable) the arbitrator(s) in an arbitration proceeding.

21.22.4. Procedural ground rules: Fed. R. Civ. P. 68

Matters of timing and other procedural issues concerning the Settlement Offer are to be governed in the general manner provided for an offer of judgment under Rule 68 of the [U.S.] Federal Rules of Civil Procedure (with any necessary change being made) to the extent the parties do not agree otherwise in writing.

Note

This section borrows from Rule 68 of the Federal Rules of Civil Procedure because that rule's provisions cover the required ground reasonably well and are familiar to (U.S.) counsel.

21.22.5. Survival of this Rule

The parties' agreement to this Rule will survive any termination or expiration of the Con­tract, regardless whether the Con­tract contains other survival provisions.

Note

See also Protocol 18.1 (survival).

21.22.6. Additional notes

21.22.6.1. Motivation: Lawyers are often over-confident about their cases

Lawyers can often be overly-optimistic about their prospects at trial, as pointed out in a 2020 article by an experienced in-house counsel:

One study found that when plaintiffs rejected a settlement in favor of going to trial, they fared worse than the settlement offer 61 percent of the time.

When plaintiffs were wrong, it cost an average of US$43,000. In other words, the settlement offer the plaintiff rejected was, on average, US$43,000 more than the amount awarded at trial.

Defendants, while faring worse at trial than the rejected offer only 24 percent of the time, paid more dearly for being wrong — US$1.1 million on average. * * * 

… Lawyers may be particularly susceptible to optimism bias because of their ethical duty to zealously advocate for their clients, causing them to more readily adopt narratives that support their client’s best arguments and theories, potentially blinding them to other, possibly more important, believable, or persuasive narratives. Brian W. Jones, With the Advancement of Predictive Analytics, Consider Using FRCP 68 During Litigation, ACC [Association of Corporate Counsel] Docket, Oct. 2020, at 56, 60, 61 (ACCDigitalDocket.com) (footnotes omitted, emphasis and extra paragraphing added).

21.22.6.2. Some states use similar rules

A somewhat-better approach than Federal Rule 68 is New Jersey Court Rule 4:58, which shifts not just court costs but also attorney fees. (The New Jersey rule, however, applies only when exclusively-monetary relief is sought; this Protocol doesn't contain such a restriction.)

To like effect are the various branches of Iowa Code chapter 677; concerning that statutory scheme, Iowa's supreme court noted: "When, as here, the plaintiff recovers less at trial than the amount of the offer, the statute bars recovery of its attorney fees incurred after the rejected offer to confess." NCJC, Inc. v. WMG, L.C., 960 N.W.2d 58, 59 (Iowa 2021) (affirming court of appeals): see also id. at 64-65 (reviewing case law).

An empirical study published in 2006 by two law professors suggests that the New Jersey rule seems to encourage early settlement and to reduce attorneys' fee expenses, without affecting the size of the damage award for cases that do go to trial. See Albert Yoon and Tom Baker, Offer-of-Judgment Rules and Civil Litigation: An Empirical Study of Automobile Insurance Litigation in the East, 59 Vanderbilt L. Rev. 155 (2006).

Georgia and Florida have fee-shifting statutes similar to New Jersey's, as does Texas. See Ga. Code Ann. § 9-11-68; Fla. Stat. § 768.79; Tex. Civ. Prac. & Rem. Code ch. 42. In 2011, the Texas Legislature tightened the limits on the amount of fees and expenses that could be recovered, which is now capped at the amount of the jury verdict, as explained in this article.

21.22.6.3. Related: Compulsory arbitration for small-dollar disputes

A related concept is implemented in Arizona's compulsory-arbitration program for small-dollar disputes:

  • In any civil case where the amount in controversy is less than an amount set by court rule (not more than $65,000), the court is normally required to send the case to arbitration.
  • Relevant here: A party that 'loses' the arbitration can still demand a trial de novo in court. If the result of the trial de novo, however, is not at least 23% (??) better than the arbitration award, then the party demanding the trial must pay (i) the arbitrators' fee, and (ii) the other side's costs and attorney fees and expenses for the trial de novo. See Arizona Rev. Stat. 12-133.

The Arizona compulsory arbitration statute has come under criticism; a pilot program giving parties an alternative option for a shortened courtroom trial, known as FASTAR, is in progress at this writing. See Christian Fernandez, Arizona’s Compulsory Arbitration Program: Is It Time for a Reform? (ArizonaStateLawJournal.org 2019).

21.23. Counterclaims (notes)

When you really, really want to sue The Other Side, keep in mind that that their lawyers will try very, very hard to come up with some kind of counterclaim to give you, the plaintiff, some "skin in the game," i.e., something to lose, to boost The Other Side's settlement leverage. The Other Side's counterclaims might eventually be dismissed — but they might lead to a big judgment against you; Either way, you'd be forced to spend time and money defending against the counterclaims.

Example: In a Houston trial:

  • A general contractor sued a land developer for failing to pay for work performed.
  • The land developer counterclaimed against the contractor and its owner for, among other things, tortious interference in seeking to sabotage the project.
  • After six-week trial, the jury rendered a take-nothing verdict against the contractor (the original plaintiff).
  • And on the counterclaim, the jury awarded the defendant developer $17.5 million in punitive damages — this was against the plaintiff contractor's owner personally — as well as $8 million in actual damages and up to $7 million in attorney fees. See Adolfo Pesquera, Bad Day for Plaintiff: $32.5M Houston Verdict on Counterclaims (Law.com 2023; paywalled); see also a post by the law firm that won at trial, Jury Awards AZA Client Mid Main $32.5 Million in Midtown Construction Case (azalaw.com 2023).

21.24. Declaratory Judgment Act (notes)

The federal Declaratory Judgment Act, 28 U.S.C. § 2201(a), states in part:

In a case of actual controversy within its jurisdiction … any court of the United States … may declare the rights and other legal relations of any interested party seeking such declaration, whether or not further relief is or could be sought. Quoted in MedImmune, Inc. v. Genentech, Inc., 549 U.S. 118, 127 S.Ct. 764, 770 (2007) (alterations by the Court).

In a 2007 case, the Court noted:

Aetna and the cases following it do not draw the brightest of lines between those declaratory-judgment actions that satisfy the case-or-controversy requirement and those that do not.

Our decisions have required that the dispute be definite and concrete, touching the legal relations of parties having adverse legal interests; and that it be real and substantial and admit of specific relief through a decree of a conclusive character, as distinguished from an opinion advising what the law would be upon a hypothetical state of facts.

Basically, the question in each case is whether the facts alleged, under all the circumstances, show that there is a substantial controversy, between parties having adverse legal interests, of sufficient immediacy and reality to warrant the issuance of a declaratory judgment. Id., 127 S. Ct. at 771 (cleaned up, emphasis and extra paragraphing added).

21.25. Efficient breach (rough notes)

[NEEDS WORK]

"Efficient breach" is the notion that, at least in the eyes of the law, it's OK for you to intentionally breach a contract, as long as you're willing to pay for the other party's resulting damages. (On the other hand, the other party — and others who hear about it — might not want to do business with you if you're someone who can't be relied on to stand behind the contractual commitments you make.)

DCT note: I ran into a related issue a few years ago with a small, software-company client that:

  • was being acquired by a big Silicon Valley company, the "buyer"; and
  • had a significant, ongoing contract with another very-big company, the "customer."

The contract — which I hadn't been involved in negotiating — was on an over-aggressive customer standard form; it said that my client couldn't even reveal to others the existence of the client's contract with the customer, let alone of the terms of the contract.

My client's contract with the customer was "material" for my client, but likely wouldn't have been material for either the customer or the buyer.

My client told its prospective buyer, in vague terms, that there was a contract that the buyer would be entitled to review under the terms of the acquisition agreement. But the buyer didn't want to reveal to anyone that the buyer was looking to acquire my client, so the client didn't approach its customer to get permission to disclose the contract to the buyer.

So the question was: Could my client reveal the existence of its customer contract to the buyer, during the buyer's due diligence, without the customer's consent — notwithstanding the prohibition in the contract?

My client decided to take an "efficient breach" position: The client revealed a redacted version of the contract to its buyer, on the theory that if my client's customer took the position that this was a breach of the contract by my client, then the customer's damages would be nominal at best. 

Things worked out fine: My client was acquired by its buyer; the client eventually told its customer about the disclosure of the redacted contract, and the customer didn't have a problem with it.

The UK Supreme Court has noted that "[c]ontract law permits efficient breach and the defendant may therefore profit from its wrong." King Crude Carriers SA v. Ridgebury November LLC, [2025] UKSC 39 ¶ 78, summarized in Alex Firth, Deemed Fulfilment of a Condition Precedent? An Unbelievable Fiction! (JDSupra.com).

21.26. Exclusive remedies (rough notes only)

21.26.1. Exclusive remedies must be clearly designated as such

A Texas appeals extensively quoted prior Texas cases:

Remedies provided for in a contract may be permissive or exclusive. The mere fact that the contract provides a party with a particular remedy does not, of course, necessarily mean that such remedy is exclusive.

A construction that renders the specified remedy exclusive should not be made unless the intent of the parties that it be exclusive is clearly indicated or declared.

An intent to provide an exclusive remedy may be clearly indicated with terms stating that the remedy is the "only," "sole," or "sole and exclusive" remedy. …

In the absence of such limiting terms or some other language which displaces the remedies that might otherwise be available, courts uniformly hold that a party may pursue any remedy that the law affords in addition to the remedies provided in the contract. GRCDallasHomes LLC v. Caldwell, 619 S.W.3d 301, 306-07 (Tex. App.–Fort Worth 2021, pet. denied) (cleaned up, presentation revised, extensive citations to Texas law omitted).

21.26.2. Defect correction can be an "exclusive remedy" …

Under section 2-719 of the [U.S.] Uniform Commercial Code, a contract for the sale of goods can specify that a remedy is exclusive (but there are restrictions and exceptions to that general rule).

A real-world example of this supplier approach is found in the First Circuit's 2014 BAE v. SpaceKey decision:

  • A supplier delivered lower-quality integrated circuits ("ICs") to a customer than had been called for by their contract. The supplier had previously alerted the customer in advance that the ICs in question would not conform to the agreed specifications; the customer accepted the ICs anyway. (The customer later asserted that it assumed the supplier would reduce the price.)
  • The customer refused to pay for the nonconforming ICs.
  • The supplier terminated the contract and sued for the money due to it.
  • The customer counterclaimed — but it did not first invoke any of the contract's specified remedies, namely repair, replace, or credit (as opposed to refund).

For that reason, the trial court granted, and the appellate court affirmed, summary judgment in favor of the supplier. BAE Sys. Information & Electr. Sys. Integration, Inc. v. SpaceKey Components, Inc., 752 F.3d 72 (1st Cir. 2014).

21.26.3. Exclusive remedies in M&A agreements

When one company (buyer) acquires another (seller), the contract pretty much always contains certain representations and warranties by the seller.

–  The seller might want the contract also to include an exclusive-remedies provision — that way, if any of the seller's reps and warranties turn out to be inaccurate, then the buyer's exclusive remedies will be for the seller to indemnify (reimburse) the buyer for (foreseeable) losses caused by the inaccuracy unless the buyer can prove fraud.

–  The buyer might want just the opposite, namely a statement that indemnification is not the buyer's exclusive remedy.

See generally Daniel Avery, Indemnification as an Exclusive Remedy (JDSupra.com 2020) (includes sample language), archived at https://perma.cc/TU3H-4YYU, and his updated article: https://www.jdsupra.com/legalnews/indemnity-caps-updated-3047030 /

21.27. Expert determinations (very-rough notes only)

Agreeing to binding, neutral, expert determination of a factual issue — for example, determining the amount of percentage rent that a store in a mall owes to its landlord — can help parties streamline dispute resolution.

Importantly, expert determination and arbitration are not the same thing; in one case, the Third Circuit vacated and remanded an order compelling arbitration of an earn-out dispute, because the parties' contract called for expert determination of the dispute. Sapp v. Indus. Action Svcs., LLC, 75 F.4th 205 (3d Cir. 2023) (cleaned up, extra paragraphing added); see also, e.g., Andrew Judkins, Expert determination (2023).

The following explanation is adapted from the Sapp court's opinion; no copyright is claimed in the opinion text.

Arbitration and expert determination, in most states, are two distinct forms of private alternative dispute resolution that produce binding results. They have similarities, leading some commentators to call them "close cousins" and some courts struggling to apply the differences between them.

Despite these similarities, the fundamental difference between the two methods is the type and scope of authority that is being delegated by the parties to the decision maker.

–  On the one hand, arbitration occurs when the parties intend to delegate to the decision maker authority to decide all legal and factual issues necessary to resolve the matter. The arbitrator functions like a judge in a judicial proceeding.

For example, like a judge, the arbitrator cannot meet with either party alone and must afford parties the due process protections of adversarial proceedings.

After resolving all factual and legal questions in a formal process that mirrors a judicial proceeding, the arbitrator can award a legal remedy, such as damages or injunctive relief, that courts will enforce.

–  By contrast, experts decide narrower issues using a less formal process. Under this method, the parties appoint a person or entity with specialized knowledge, usually of a technical nature, to determine a confined issue.

The authority of an expert is limited to its mandate to use its specialized knowledge to resolve a specified issue of fact and does not extend to making binding decisions on issues of law or legal claims. It makes its decision without following court-like procedures: there are usually no pleadings, evidentiary hearings, or the taking of witness testimony.

Rather than rely only on evidence submitted by the parties, an expert will often conduct its own investigation and request from the parties the information it needs to resolve the factual issue.

As relevant here [i.e., in the case being appealed], accounting firms are commonly relied on as experts to resolve questions about post-merger financial schedules.

* * *

In a Delaware trial-court case: Del. Super. Ct. 2024: Pazos v. AdaptiveHealth LLC: "Pursuant to those procedures, an independent accountant was tasked with resolving the parties’ post-closing calculations dispute. The agreement’s provisions state that the independent accountant’s determination is final and binding upon the parties, absent manifest error." Slip op. at 14: Accountant True-Up Mechanism.

What's "manifest error"? P.17, TAN 96:

A manifest error has been referred to as a plain and obvious error, or an error which is obvious or easily demonstrable without extensive investigation. Too, manifest error should be confined to errors which are obviously capable of affecting the determination. [Cleaned up, citations and footnotes omitted.]

At 18-19 n.102:

In resolving any disputed item, the Independent Accountant may not assign a value to any item greater than the greatest value for such item claimed by either Party or less than the smallest value for such item claimed by either Party. The Independent Accountant shall determine and include in its report an award of the costs of its review and report based on the extent to which the Parties prevail in such matter. By way of illustration, if the items in dispute total in amount to $1,000 and the Independent Accountant awards $600 in favor of Seller’s position, 60% of the costs of its review would be borne by Buyer and 40% of the costs would be borne by Seller. Buyer and Seller shall make available to the Independent Accountant all relevant books and records relating to the calculations submitted and all other information reasonably requested by the Independent Accountant.

At 19 n.103:

… According to Ms. Pazos, the Court can simply re-calculate and enter judgment. See id. While it might be more efficient, the Court cannot substitute its own decision-making for that of the expert where the parties specifically bound themselves by contract for the use of an expert to settle disputes. The Court’s role is limited here to determining whether manifest errors occurred— not determining the post-closing payment calculations themselves. See Tenenbaum Living Tr., 682 F.Supp.3d at 355 (“A manifest error clause avoids [the peril of a court’s erroneous financial computations] by requiring courts not to make such determinations themselves but rather to defer to qualified experts selected by the parties.”); id. (“for manifest error clauses to properly serve their function, they must preclude courts from reexamining the substantive correctness of the determination to which the clause applies”).

* * *

Del. Super. Ct. 2024: AM Buyer LLC v. Argosy Investment Partners IV, L.P.:

At p.6, TAN 22:

The findings and determinations of the Independent Accountant as set forth in its written report shall be deemed final, conclusive and binding upon the Parties and shall not be subject to collateral attack for any reason, other than fraud or clear and manifest error. The Parties shall be entitled to have a judgment entered on such written report in any court of competent jurisdiction. [Footnote omitted.]

At p.18, TAN 87:

Following the Delaware Supreme Court’s decision in Terrell v. Kiromic Biopharma, Inc.87 and the Court of Chancery’s decision Penton Business Media Holdings, LLC v. Informa PLC,88 Delaware courts have applied the “authority test” to determine whether parties have opted for arbitration.89 “The test turns primarily on the degree of authority delegated to the decision-maker.”90 In a plenary arbitration, the arbitrator has authority “to decide all legal and factual issues necessary to resolve the matter.”91 By contrast, an expert determination is typically limited “to deciding a specific factual dispute concerning a matter within the special expertise of the decision maker, usually concerning an issue of valuation.”92

* * *

In a 2019 decision, Delaware's chancery court explained that : "Expert determination provisions are fundamentally different from arbitration provisions. The former limit the scope of the third-party decision maker’s authority to factual disputes within the decision maker’s expertise. The latter typically confers upon the third-party decision maker broad authority similar to that of judicial officers." Ray Beyond Corp. v. Trimaran Fund Mgmt., LLC, No. 2018-0497-KSJM, slip op. at 2, text acc. n.2 (Del. Ch. Jan. 29, 2019) (McCormick, V.C., denying motion for judgment on the pleadings seeking to specifically enforce dispute resolution provision): "The Merger Agreement designates the independent accountant an expert, not an arbitrator." (Cleaned up.) See also id. at 16-22 (extended explanation with citations).

Avoid litigation: When two party-appointed appraisers (or other experts) is used, be sure to state explicitly that if the two of them don't agree, and thus they appoint a third appraiser, then their majority vote will be determinative — don't just say "the three shall determine" the matter. Norfolk Southern R.R. Co. v. Zayo Grp., LLC, 87 F.4th 585 (4th Cir. 2023) (affirming judgment confirming non-unanimous panel determination, of amount of rent to be paid, as binding arbitration award), citing Hobson v. McArthur, 41 U.S. (16 Pet.) 182, 192-93 (1842).

(Or better yet: Have each party-appointed appraiser provide an appraiser, and if they can't agree, then a third appraiser chooses between the two appraisers — this was the approach used in a Delaware chancery-court case. See Paul v. Rockport Group, LLC, No. 2018-0907-JTL, slip op. (Del. Ch. Jan. 9, 2024) (Laster, V.C., granting summary judgment in favor of plaintiff), discussed at 21.11.25.2.

Green v. McClive, No. 2023-0139-MTZ (Del. Ch. 2024): An LLC's operating agreement said: "Other Business Ventures. The Managers and the Members may engage in or possess a significant interest in other business ventures of any nature and description, independently or with others." The vice chancellor said that this provision "offers no clear waiver of the duty of loyalty to permit the usurpation of corporate opportunities, and I cannot read one in."

Also the need for a reliance waiver (11.7) under Texas law, and the express negligence rule (14.3.4).

21.28. Mediation (notes)

Drafting tips:

Critical Mediation Provision Drafting Tips

The following three tips can help avoid a result like Healy:

First, use express “condition precedent” language. Explicitly state that mediation is a “condition precedent” to litigation or arbitration. Avoid ambiguous terms like “endeavor” or provisions that allow inconsistent actions, such as simultaneously requesting mediation and filing suit.

Second, prohibit filing until mediation concludes. Clearly define when mediation is considered “complete” — whether through mediator declaration of impasse, expiration of a specific timeframe, or mutual agreement. This eliminates ambiguity about when parties may proceed to litigation.

Third, establish consequences for noncompliance. Include provisions allowing parties to recover attorneys’ fees if they must move to dismiss a prematurely filed action. This reinforces the mandatory nature of the mediation requirement. Jamey Collidge, Robert Gallagher, and Patrick Zancolli, Court Rules Mediation Clause Lacks Condition Precedent Language: Key Lessons for Construction Contracts (JDSupra.com 2025), discussing Healy Long & Jevin, Inc. v. CQSA Construction, LLC, No. 25-3156, slip op. (E.D. Pa. Nov. 18, 2025) (denying motion to dismiss; "endeavour" mediation language was not mandatory).

21.29. Principal place of business (notes)

Background: For various reasons — e.g., plaintiff convenience, congenial law, friendly juries — a plaintiff that wants to sue a corporation might bring the lawsuit in the local courts of a particular state, e.g., Texas, Delaware, California etc. But:

  • If the plaintiff is a citizen of one state and the corporation is a a "citizen" of another state (other than the state where the lawsuit was brought), then the corporation can "remove" the lawsuit to federal court. The federal court would then hear the case under the court's "diversity jurisdiction," as provided in the U.S. Constitution's Article III, section 2, clause 1.
  • Congress has fleshed out the diversity concept by legislating that, for diversity purposes, a corporation is a "citizen" of the state where it's incorporated and (if different) the state of its "principal place of business." See 28 U.S.C. § 1332(c)(1)

But what does "principal place of business" mean, exactly: The state where the corporation has its physical headquarters? The state where the corporation does the mosst business? Something else?

In Hertz Corp. (U.S. 2010), resolving a circuit split, the Supreme Court adopted the Seventh Circuit's "nerve center" approach:

We conclude that "principal place of business" is best read as referring to the place where a corporation's officers direct, control, and coordinate the corporation's activities. It is the place that Courts of Appeals have called the corporation's "nerve center."

And in practice it should normally be the place where the corporation maintains its headquarters — provided that the headquarters is the actual center of direction, control, and coordination, i.e., the "nerve center," and not simply an office where the corporation holds its board meetings (for example, attended by directors and officers who have traveled there for the occasion). Hertz Corp. v. Friend, 559 U.S. 77, 92-93, 130 S. Ct. 1181, 1192 (2010) (vacating remand to state court; Hertz Corp.'s "nerve center" was in New Jersey even though the company did the most business in California) (cleaned up).

21.30. Releases from liability (notes only)

21.30.1. Why a "release"?

To release another party from a claim is, in essence, to withdraw the claim, or as explained in Black's Law Dictionary: "The relinquishment or concession of a right, title, or claim …." Release, Black's Law Dictionary (10th ed. 2014).

Releases are generally used to get rid of existing claims, but some contracts include purported advance releases of future claims.

Caution: Drafters will want to check applicable law to determine whether this advance release of claims concerning future events is enforceable; this is discussed in an undated article by lawyer Michael Amaro. See Michael L. Amaro, Pre-Event Waivers and Releases - A Comparative Review of Current State Laws (archive.org) (undated, saved Jun. 16, 2019 ).

21.30.2. California's special law for releases of unsuspected claims

When releases are concerned, California law favors so-called "level playing fields," as exemplified by section 1542 of the California Civil Code:

A general release does not extend to claims that the creditor or releasing party does not know or suspect to exist in his or her favor at the time of executing the release and that, if known by him or her, would have materially affected his or her settlement with the debtor or released party.

Caution: I've seen release language that purports to waive this California law; I haven't researched the extent to which it's enforceable for future claims — it's possible that a California court might disregard this advance waiver as contrary to public policy.

21.30.3. Statutes might affect releases

The Uniformed Services Employment and Reemployment Rights Act (USERRA) has special requirements for releases of claims under that statute. 38 U.S.C. § 4302.

From a Sixth Circuit case:

The relevant language here is that Ward agreed to release "any and all claims whatsoever" as to his termination. Those words speak for themselves: to know that the release applied to Ward's USERRA claim, one needed to know only that it was a claim.

The district court was mistaken to conclude otherwise. The court reasoned that, since the release did not call out Ward's USERRA claim specifically, the release did not apply to it.

But the law does not require contracting parties to enumerate, one by one, all the objects they intend a particular clause to reach. That kind of requirement would generate litigation rather than prevent it—by opening the door to disputes later about whether an item was described clearly enough, for example, or about circumstances not expressly foreseen at the time of signing.

When the parties intend to settle "any and all claims," rather, the law allows them to say precisely that. Ward v. Shelby County 98 F.4th 688, 691 (6th Cir. 2024) (paragraphing modified, emphasis added).

21.30.4. Advance releases might have special rules

–  In California, the state supreme court held that an advance release of the city of Oakland for liability for negligence was unenforceable under Cal. Civ. Code § 1668, enacted in 1872. That section states in its entirety: "All contracts which have for their object, directly or indirectly, to exempt any one from responsibility for his own fraud, or willful injury to the person or property of another, or violation of law, whether willful or negligent, are against the policy of the law." The plaintiff, a cyclist, was injured when he hit a pothole in the street and claimed that the city had violated its statutory duty to maintain the streets. See Whitehead v. City of Oakland, No. S284303, slip op. (Cal. May 1, 2025) (reversing summary judgment in favor of city).

–  In Texas, advance releases of negligent conduct must follow the "express negligence rule," that is, an advance release must be both express and conspicuous. See, e.g., Dresser Industries v. Page Petroleum, Inc., 853 S.W.2d 505, 509 (Tex. 1993) (emphasis added); Transcor Astra Group S.A. v. Petrobras America Inc., 650 S.W.3d 462 (Tex. 2022), discussing a release in a settlement agreement.

More from the Texas supreme court:

"A release involves a voluntary relinquishment, while a forfeiture connotes a consequence imposed as a penalty." Finley Resources, Inc. v. Headington Royalty, Inc., 672 S.W.3d 332, 339 & n.16 (Tex. 2023) (affirming court of appeals reversal and rendering of judgment; a release of "predecessors" meant corporate predecessors, not predecessors in title).

Even so, to avoid unintentionally losing valuable rights against unnamed—and perhaps unknown—wrongdoers, we have long said that a release will discharge only those persons named or identified with such descriptive particularity that their identity or connection to the released claims is not in doubt.

The requirement of specific identification is not met unless the reference in the release is so particular that a stranger could readily identify the released party. Id. at 339 & n.18.

A release is a contract, so we construe it as such. When a contract’s meaning is disputed, our primary objective is to ascertain and give effect to the intentions the parties have objectively manifested in the written instrument. Id..

21.30.5. Caution: Releases might wipe out unintended legal rights

21.31. Settlement agreements (notes only)

21.31.1. Watch out for nondisclosure obligations, etc.

In cases of sexual harassment, workplace discrimination, and the like, many settlement agreements have required the complainant to keep quiet, both about the settlement and about the conduct that led to the underlying complaint. BUT: A number of states have enacted legislation restricting or even prohibiting such nondisclosure requirements ("NDAs"). As explained by attorneys at the Littler Mendelson firm:

New York is not alone. A growing number of other states have also passed laws that significantly restrict or prohibit employers’ use of NDAs when resolving claims of sexual harassment. California, Illinois, Maryland, [Maine,] Nevada, New Jersey, Oregon, Tennessee, Vermont, Virginia, and Washington have all enacted legislation that restrict an employer’s use of NDAs. California, Nevada, and New Jersey now prohibit NDAs altogether when resolving a sexual harassment claim.

These new laws do not restrict the right of the parties to agree to keep confidential the terms of a settlement agreement, the amount paid, or the fact that such an agreement exists. Rather, the laws target the parties’ agreement not to disclose the underlying harassment allegations. Emily Haigh and David M. Wirtz, #MeToo: In Defense of Nondisclosure Agreements (Littler.com 2020).

In 2023, New York enacted even-stricter legislation rendering certain provisions unenforceable in a settlement agreement for claims of discrimination, discriminatory harassment, and retaliation. See Robert Hingula, New Year, New Severance and Settlement Agreement Rules for New York (JDSupra.com 2024).

And from an attorney at the Foley & Lardner firm:

Effective June 9, 2022, Washington State enacted what is likely the broadest ban on company use of non-disclosure and non-disparagement (NDA) provisions. The new Washington statute called the “Silence No More” Act, bans NDAs related to all forms of workplace discrimination as well as wage and hour violations and conduct that is “recognized as against a clear mandate of public policy.”

The Act specifically prohibits agreements containing non-disclosure and non-disparagement provisions that restrict applicants, employees, and independent contractors from openly discussing conduct or a legal settlement involving conduct that the applicant, employee, or contractor “reasonably believed” was illegal discrimination, harassment, retaliation, a wage and hour violation, a sexual assault, or conduct that is “against a clear mandate of public policy.

While the Washington law contains these broad restrictions, note that it does not prohibit employers from requiring the amount paid in settlement of any claim to be kept confidential. Essentially, this means that any settlement of a claim can only prohibit discussion of the amount of settlement, not the facts that lead to the settlement. Additionally, employers can still protect trade secrets, proprietary information, or confidential information that does not involve illegal conduct. Carrie Hoffman, Several States have Enacted Broad Ban on Non-disclosure Agreements (Foley.com 2022).

21.31.2. Nothing is agreed until everything is agreed?

It can be useful for a settlement agreement to state that nothing is agreed until everything is agreed; for a case where that would have been useful, see a 2022 Federal Circuit' decision, where the appeals court, reversing the district court (with one judge dissenting), held that a particular version of a settlement agreement was binding. PlasmaCAM, Inc. v. CNCElectronics, LLC, 24 F.4th 1378 (Fed. Cir. 2022) (reversing district court). (Newman, J. dissented.) ]

21.31.3. Include a thou-shalt-not-sue provision?

A settlement agreement should preferably contain an explicit agreement that the plaintiff (or would-be plaintiff) won't sue the other party — that way, if the plaintiff does file suit, and the other party gets the case tossed on grounds of settlement, then the other party should be able to recover its attorney fees as damages for the breach of the agreement not to sue.

Why be so specific? Because there's apparently a split among different jurisdictions as to whether such an explicit "covenant not to sue" is required, as explained by Virginia's supreme court in a 2021 decision. See Bolton v. McKinney, 855 S.E.2d 853, 855-57 (Va. 2021) (reversing lower court's refusal to award attorney fees; reviewing case law).

21.31.4. Be clear about non-reliance

When parties enter into an agreement to settle a dispute, it can be advantageous for the agreement's background section to be clear that the parties were not relying on each other's representations; they could use language such as 11.7: Reliance Waiver Option for that purpose. Doing so can help to forestall at least some subsequent fraud claims. Cf. Pappas v. Tzolis, 20 N.Y.3d 228, 982 N.E.2d 576, 958 N.Y.S.2d 656 (2012) (plaintiff's own pleadings made it clear that it would not have been reasonable for plaintiff to rely on defendants' alleged fraudulent statements).

21.32. Sovereign immunity (very-rough notes)

If a country's ambassador signed a commercial loan agreement with a bank, and the agreement contained a choice-of-law and choice-of-forum clause, would that be enough to waive the country's sovereign immunity against judicial enforcement of the agreement? In a D.C. federal-court case, a magistrate judge concluded that the bank had not shown that the ambassador had actual or apparent authority to waive sovereign immunity. See John F. Coyle, Who Has the Authority to Waive Sovereign Immunity Via Contract? (TLBlog.com 2025), discussing Qatar National Bank v. Govt. of Eritrea, No. 21-cv-436, slip op. (D.D.C. May 14, 2025) (Upadhyaya, M.J., rec'g denial w/o prejudict of bank's motion for default judgment against Eritrea).

21.33. Specific performance (notes only)

[DCT TO DO: ADD THIS TO THE INJUNCTIVE-RELIEF PART]

21.33.1. Specific performance doesn’t always preclude a damages award

When a seller tries to back out of a contract to sell real property (or, sometimes, other property), the buyer might sue for specific performance to compel the seller to sell. Ordinarily, a grant of specific performance would preclude an accompanying award of damages for breach of the contract.

BUT: The Texas supreme court announced "a narrow set of circumstances" in which certain damages are recoverable even when specific performance is also granted:

We hold that, while an award of specific performance usually precludes a monetary award, there is a narrow set of circumstances in which a breach of a contract for the sale of real property may be remedied by specific performance and a monetary award of reasonable, foreseeable expenses directly traceable to the delay in performance and, in cases where the purchaser breaches, incurred in connection with the seller’s care and custody of the property during such delay. White Knight Development, LLC v. Simmons, No. 23-0868, slip op. at 2 (Tex. Jun. 13, 2025) (reversing court of appeals).

22. Restrictive covenants

22.1. Nondisparagement Protocol

22.1.1. Lighthouse Protocol

22.1.1.1. The Obligated Party: Each party.

In this Protocol, the term "Obligated Party" refers to each party.

Note

Prohibitions such as those of this Protocol are sometimes seen in contracts — but they can lead to governmental challenges, as discussed below.

22.1.1.2. Prohibition

Obligated Party: Don't make, to any third party, any disparaging statement:

  1. about any other party to the Con­tract; nor
  2. about the products, services, or business practices of that other party.
Note

Concerning the term "third party," see the exceptions at 22.1.1.5 below.

22.1.1.3. Required: Instruction to employees

Obligated Party: Instruct your people (defined at 17.8) to comply with your obligations under this Protocol.

Note

In the D.C. Circuit's 2023 Wright case (extensively quoted at 17.2), the court held that a severance agreement's nondisparagement instruction obligation, akin to this one, could plausibly be interpreted as also prohibiting the former employer itself and its CEO from disparaging the former employee. See Wright v. Eugene & Agnes E. Meyer Foundation, 68 F.4th 612 (D.C. Cir. May 23, 2023) (reversing dismissal of former employee's claims).

22.1.1.4. Broad prohibition

Obligated Party: Your obligation under this Protocol extends to disparaging statements of fact as well as of opinion — and not just false- or misleading statements of fact.

Note

These might be points of contention in some contract negotiations — moreover, it might even be unlawful to require another party to agree to such terms in, e.g., employment agreements. See, e.g., the Illinois Workplace Transparency Act, 820 Ill. Compiled Stat. 96, discussed at Illinois enacts new, broad-reaching employment legislation aimed at combatting discrimination, harassment, and retaliation (NixonPeabody 2019); see also Jennifer Schilling, Kerri Feczko, and Dinora Orozco, Overview of Recent Amendments to the Illinois Workplace Transparency Act (Littler.com 2025).

22.1.1.5. Exception: Complaints to the other party

Obligated Party: You're free to make legitimate complaints relating to the Con­tract to any of the following when involved in the parties' dealings together under the Con­tract:

  1. the other party;
  2. the other party's affiliates; nor
  3. the officers, employees, distributors, resellers, and agents of the other party or any of its affiliates.
Note

().  This exception only makes sense: A party to a contract shouldn't wonder whether a nondisparagement clause would prohibit expressing unhappiness to the other party, etc., about the other party's performance or other conduct.

This section is worded to take into account an Illinois supreme court holding that a competitor's sending psuedonymous defamatory emails about a company and its products to the company's officers and board members was defamatory. The state supreme court quoted the circuit court's decision: "a corporation is not only concerned with its reputation to the outside world. Just as employees care about their reputation within the corporation, the corporation cares about its reputation among its own employees—be they high-ranking executives, lower-level workers, or nonemployee directors"; reviewing case law, the court asserted that a majority of jurisdictions follow this approach. See Project44, Inc. v. FourKites, Inc., 2024 IL 129227, 240  N.E.3d 471 ¶¶ 13, 22-27 (cleaned up).

22.1.1.6. Legally-immune communications

Obligated Party: You're free to provide information to others in any case where the law affirmatively says it's OK to do so, even when there's a contractual prohibition such as that of this Protocol.

Note

Some jurisdictions might limit a party's ability to enforce a disparagement prohibition — or even make it unlawful to require agreeing to such a prohibition; see the examples at 22.1.2.5.

22.1.2. Additional notes

22.1.2.1. Some real-world examples

Here are couple of examples of disparagement prohibitions that were successfully asserted against parties:

Example: Group founder and reputed billionaire Vinod Gupta sold his company but later was found to have violated a nondisparagement clause in his buyout agreement when he said to a reporter that the company "[has] no leadership, no brains and their product is obsolete." In 2020, the Eighth Circuit upheld a $10 million judgment against Gupta for breach of contract (plus breach of a confidentiality clause). See InfoGroup v. DatabaseLLC, 956 F.3d 1063, 1068 (8th Cir. 2020) (affirming denial of judgment as a matter of law after jury verdict against Gupta) (extra paragraphing added).

Example: Reality-show producers often demand that cast members sign agreements with nondisparagement clauses. In 2020, the producers of The Bachelorette won a $120,000 arbitration award against designated-villain cast member Luke Parker for making allegedly "negative or disparaging comments"; the arbitration award was confirmed in a California court. Andy Denhart, Bachelorette villain ordered to pay producers $120,000, archived at https://perma.cc/5HJ3-6G4G (RealityBlurred.com Oct. 12, 2020); see also the petition to confirm arbitration award in NZK Productions, Inc. v. Parker, No. 20STCP02088 (Cal. Sup. Ct. June 6, 2020).

22.1.2.2. Even a "no names" disparagement might have to have a trial.

The federal district court in Rhode Island noted that a party might violate a non-disparagement clause, even without naming the target of the disparagement, if others could "connect the dots" and figure out the identity of the party being disparaged. Denying the accused disparager's motion for summary judgment, the court held that a trial would be necessary to determine the connect-the-dots question. See Toray Plastics (America), Inc. v. Paknis, No. 18-672 (D.R.I. Aug. 16, 2022) (denying, in pertinent part, accused disparager's motion for summary judgment) ]

22.1.2.3. Pro tip: Consider the "Streisand effect."

A disparagement prohibition could lead to bad publicity. Consider the so-called Streisand effect: When the legendary singer-actress tried to suppress unauthorized photos of her residence, the resulting viral Internet publicity resulted in the photos being distributed even more widely — thus defeating her purpose.

22.1.2.4. Would there be any provable damages from disparagement?

A Delaware trial court held: (i) that a company's former CEO had breached a nondisparagement clause contained in his separation agreement with the company, but (ii) that the company had failed to prove non-speculative damages from the breach: "In Delaware, damages for a breach of contract must be proven with reasonable certainty. Recovery is not available to the extent that the alleged damages are uncertain, contingent, conjectural, or speculative." See Feenix Payment Sys., LLC v. Blum, No. N21C-05-099, slip op. at part V, text acc. n.128 (Del. Super. Ct. May 29, 2024) (cleaned up, footnote omitted).

22.1.2.5. Appendix: A partial list of disclosure-authorizing laws

Here are some examples of state- and federal laws restricting disparagement prohibitions:

–  The Defend Trade Secrets Act, at Title 18, Section 1833(b) of the United States Code, expressly authorizes certain disclosures of information (see § 5.3.26 for more information).

–  In California, Cal. Civ. Code § 1670.8 prohibits such disparagement provisions in consumer contracts — with civil penalties for violation. (The limitation to consumer contracts is probably why the Bachelorette disparagement prohibition, cited at 22.1.2.1, wasn't held to be unenforceable.)

–  Also in California, Cal. Gov. Code § 12964.5 provides in part:

(a) It is an unlawful employment practice for an employer, in exchange for a raise or bonus, or as a condition of employment or continued employment, to do either of the following: … (2)(A) For an employer to require an employee to sign a nondisparagement agreement or other document that purports to deny the employee the right to disclose information about unlawful acts in the workplace, including, but not limited to, sexual harassment.

(An exception is provided for negotiated settlements where the employee is given notice and has an opportunity to be represented by an attorney.)

The Federal Trade Commission has said that:

The Consumer Review Fairness Act makes it illegal for companies to include standardized provisions that threaten or penalize people for posting honest reviews.

For example, in an online transaction, it would be illegal for a company to include a provision in its terms and conditions that prohibits or punishes negative reviews by customers.

(The law doesn’t apply to employment contracts or agreements with independent contractors, however.) Federal Trade Commission, Consumer Review Fairness Act: What Businesses Need To Know (FTC.gov Feb. 2017; extra paragraphing added). The text of the Act is codified at 15 U.S.C. § 45b.

And a federal district court in Florida granted the FTC's motion for summary judgment that a "gag clause" binding customers of the defendants' weight-loss products was an unfair practice in violation of Section 5 of the FTC Act. The court later ordered the defendants to pay $25 million to the FTC "as equitable monetary relief, including consumer redress and disgorgement of ill-gotten gains" for false advertising. See FTC v. Roca Labs, Inc., 345 F. Supp. 3d 1375, 1393-97 (M.D. Fla. 2018) (summary judgment as to liability); No.  8:15-cv-2231-T-35TBM, slip op. at 18 (M.D. Fla. Jan. 4, 2019) (final judgment).

The (U.S.) National Labor Relations Board took the position that a lawsuit by an employer to enforce a contractual non-disparagement provision would be partly preempted by the National Labor Relations Act, and that the employer's continued prosecution of the lawsuit after receiving a warning letter from the NLRB would violate the Act. Nat'l Labor Rel. Bd., Advice Memorandum (Strange Law Firm), March 4, 2019.

22.2. No-hire clauses (notes only)

No-hire clauses — as opposed to no-solicitation clauses, see 17.9 — can pose significant legal dangers; for that reason, we won't consider any transaction rule on that subject.

Example: In January 2025, the Federal Trade Commission entered into a consent-order agreement with building services contractor Planned Building Services and its affiliates ("Planned"); the order directed Planned to stop enforcing no-hire agreements that limited the ability of residential and commercial building owners from hiring Planned's building-service workers.

Example: In December 2024, the Federal Trade Commission "ordered building services contractor Guardian Service Industries, Inc. (Guardian) to stop enforcing a no-hire agreement that prohibits building owners and managers from hiring Guardian’s employees." Then-commissioner Andrew Ferguson — now the FTC chair — dissented on (what I'd call) technical grounds, while agreeing that no-hire clauses could be illegal.

Example: In 2010, the U.S. Department of Justice extracted a five-year antitrust consent decree preventing Adobe, Apple, Google, Intel, Intuit, and Pixar from entering into agreements not to solicit each others' employees (with certain exceptions). According to the DOJ, such agreements "eliminated a significant form of competition to attract highly skilled employees, and overall diminished competition to the detriment of affected employees who were likely deprived of competitively important information and access to better job opportunities."

Since then, the Antitrust Division has tried — generally without success, at least so far — to criminally prosecute companies and executives who allegedly engaged in similar behavior. See Eric Akira Tate and Cooper J. Spinelli, No-Poach Case Alert: DOJ’s No-Poach Strategy Dealt Another Blow As Court Tosses Case Before It Reaches Jury (MoFo.com 2023).

A 2021 article by attorney Edward G. Winsman offers "5 Employer Takeaways to Enforce No-Hire Agreements."

22.3. Nonsolicitation of customers (rough notes only)

Some employment agreements state that if the employee leaves the company, the employee is prohibited from soliciting the (now-former) employer's customers for a stated period of time. At least in some jurisdictions, courts treat such clauses more leniently than they do noncompetition covenants, especially if the prohibition extends only to customers with which the former employee worked directly.

Example: In its 2023 NuVasive decision, the First Circuit affirmed a Boston federal judge's decision to order a former medical-device sales representative to pay his former employer more than $1.7 million, in:

  • damages for violating noncompetition and customer-nonsolicitation obligations in his employment agreement; and
  • attorney fees for spoliation of evidence by failing to preserve text messages. See NuVasive, Inc. v. Day, 77 F.4th 23 (1st Cir. 2023).

In that case, the nonsolicitation obligation included the following language quoted by the district court:

The NuVasive PIIA additionally includes a non-solicitation clause (Section VI) and a non-competition clause (Section VII).

Both clauses include provisions extending the terms of the clauses for one year following the termination of Defendants' engagement with NuVasive.

The non-solicitation clause provides that Defendants agree not to "solicit, entice, persuade, induce, call upon or provide services to any of the Customers . . . accounts or clients that [they] worked with, had responsibility or oversight of, provided services related to, or learned significant information about during [their] employment (or other association) with [NuVasive] for any purpose other than for the benefit of [NuVasive]."

"Customers" refers to "hospitals (including but not limited to surgery centers and other healthcare institutions and their employees), payers (including but not limited to insurance companies and third party billers), and physicians (or other health care practitioners including but not limited to the employees of any surgeon or other healthcare practitioners) who use, order or approve the use of ordering of [NuVasive] products or services." NuVasive, Inc. v. Day, No. 19-cv-10800, slip op. at part IV.A (D. Mass. Feb. 18, 2021) (granting partial summary judgment of breach of contract against former employee; cleaned up, formatted edited).

By its terms, the Massachusetts Noncompetition Agreement Act excludes customer-nonsolicitation agreements from the statute's coverage, along with confidentiality agreements; invention-assignment agreements; garden-leave agreements; and forfeiture agreements that aren't triggered by competition.) Mass. Gen. L. c. 149 § 24L(a) (definition of "noncompetition agreement"); Miele v. Foundation Medicine, Inc., No. SJD-13697 (Mass. Jun. 13, 2025) (answering certified question and remanding to trial court: "a forfeiture clause triggered by a breach of a nonsolicitation agreement does not constitute a 'forfeiture for competition agreement' subject to the act") (emphasis added).

22.4. No-Shop Protocol

No-shopt clauses are quite common in corporate acquisitions: Once a prospective buyer of a company has spent the time and money to check out a potential acquisition target, the buyer doesn't want the target's management going off and looking for a higher price. (But as discussed at § 22.4.4, the target company's board of directors could be legally obligated to seek a higher price.)

22.4.1. Definitions

In this Protocol:

"Buyer" refers to a party that, in substance, is an acquiring party in a Transaction.

"Competing Transaction" refers to any transaction, or series of related transactions, involving the Seller (defined below), that is similar in nature to the Transaction — the term includes, without limitation, the following if the Transaction relates to a merger or acquisition in which the Seller is involved:

  1. any merger, consolidation, share exchange, or other business combination involving the Seller or the Seller's business or assets;
  2. any disposition of a substantial portion of the Seller's assets, whether by sale, lease, license, pledge, mortgage, exchange, or otherwise; and/or
  3. (if the Seller is an organization:) any sale, exchange, or issuance of shares of stock (or, if applicable, of convertible securities) that, in the aggregate, represent a substantial portion of the voting power of the Seller as an organization.

"Involved Seller Representative" refers to any Seller Representative who is actively involved in the parties' discussions concerning the Transaction.

"Seller" refers to a party that, in substance, is a seller in a Transaction.

"Seller Representative" refers to any accountant, agent, attorney, director, employee, financial advisor, investment banker, officer, or other representative of the Seller or any affiliate of the Seller.

"Shop the Deal", and corresponding terms such as Shopping the Deal, refer to the Seller's taking of any action that could reasonably be interpreted as having the purpose or effect of exploring, setting up, furthering, or finalizing a Competing Transaction. The term includes (without limitation) any one or more of the following:

  1. initiating or soliciting discussion about a potential Competing Transaction; and/or
  2. furnishing information (public or nonpublic) to a prospective party to a potential Competing Transaction.

"Transaction" refers to the sale (of assets or other things), merger, or other transaction that is contemplated in the Con­tract.

Note

In the definition of Competing Transaction, the term "similar in nature" might be too vague for some drafters, but in many transactions it's likely to be considered acceptably precise.

22.4.2. Seller's specific obligations

  1. This section applies except as stated in § 22.4.4 below.
  2. The Seller will not Shop the Deal before termination (if any) of the Con­tract.
  3. The Seller will not authorize (nor direct) any Seller Representative (nor any other party) to take any action that's inconsistent with your obligations under this Protocol.
  4. The Seller will timely direct, in writing, each Involved Seller Representative not to take any action inconsistent with your obligations under this Protocol.

22.4.3. Comms: Interest from other parties

If the Seller receives one or more inquiries or proposals received concerning possible Competing Transactions, THEN: The Seller will promptly advise the Buyer, in writing, of each such inquiry or proposal — including relevant details to a commercially-reasonable extent.

Note

().  This heads-up requirement will allow the Buyer to monitor any third-party activity that might affect the Transaction, and to consider whether and how to respond to such activity.

Caution: The Seller might not want to be obligated to give the Buyer all the details concerning third-party expressions of interest.

22.4.4. Fiduciary out

  1. Nothing in this Protocol is meant to stop the Seller from Shopping the Deal if the Seller's board of directors (defined at 20.6), acting on advice of counsel, reaches one or more of the following conclusions:
    1. that a potential Competing Transaction proposed by a third party — if completed — would be more favorable to the Seller's stockholders (or comparable interest owners) than the Transaction; or
    2. that Shopping the Deal is necessary or advisable for the Seller's board to comply with its fiduciary duties under applicable law.
  2. Comms: The Seller will advise the Buyer in writing, at least 48 hours beforehand, that the Seller intends to invoke the fiduciary-out exception of this section.
  3. For the avoidance of doubt: The Seller is not required to disclose, to the Buyer, the detailed content of the advice from the Seller's legal counsel or other advisers concerning the possibility of a fiduciary out.
Note

().  In a merger-or-acquisition ("M&A") deal, the Seller will often insist on including a "fiduciary-out" clause in the contract. That's because the Seller's board of directors might have a fiduciary duty to the seller's shareholders, requiring the board to consider, and even accept, better offers than the deal.

A fiduciary-out clause will typically also allow a Seller not only to shop the deal (if an unsolicited offer comes along) but to terminate an existing acquisition agreement, e.g., if a better offer comes along. Example: See sections 5.2 and 7.8 of the 2023 Agreement and Plan of Merger under which oil-and-gas giant Chevron agreed to acquire Hess Corporation. See Richard Presutti, Matthew Gruenberg and Andrew Fadale, Private Equity Buyer/Public Target M&A Deal Study: 2015-17 Review (law.harvard.edu 2018).

The parties' drafter(s) would need to address the termination issue separately in the Con­tract, because the termination prerequisites might well be subject to serious negotiation.

22.4.5. Termination and breakup fees?

The Con­tract could provide for:

  1. a "fiduciary out" right for the Seller to terminate the Transaction if the Seller were to get a better offer; and/or
  2. a breakup fee, to a specified party in the event of termination;

but this Protocol itself does not provide for either.

Note

().  In merger- and acquisition ("M&A") agreements, breakup-fee provisions are usually closely negotiated; they typically provide for a seller to pay the buyer a breakup fee if the seller exercises its fiduciary-out option.

Example: When Microsoft acquired LinkedIn in 2016, LinkedIn was contractually obligated to pay Microsoft a breakup fee of $725 million if LinkedIn terminated the parties' agreement in order to accept a "superior proposal," which was defined at page 98 of LinkedIn's proxy statement filed with the Securities and Exchange Commission. (But the deal did go through, with Microsoft acquiring LinkedIn.)

For examples of breakup-fee contract language, see this entry at AfterPattern.com, as well as section 10.5 of the 2023 Agreement and Plan of Merger under which oil-and-gas giant Chevron agreed to acquire Hess Corporation.

For a study of then-recent breakup-fee size, see Houlihan Lokey, 2022 Transaction Termination Fee Study (HL.com).

22.5. Noncompetition Protocol

Noncompetition obligations are common in employment agreements of corporate executives, and sometimes of non-executive people. But state law can severely restrict the enforceability of such obligations — and even penalize companies for requiring them.

22.5.1. Applicability

  1. When this Protocol is agreed to, it will apply to each Obligated Party that is clearly identified in the Con­tract as being subject to this Protocol.
  2. In case a question arises:
    1. An identification of an Obligated Party in the Con­tract is not meant to imply that any other person is subject to this Protocol, whether or not the other person is affiliated or associated with the Obligated Party.
    2. If the Con­tract identifies more than one Obligated Party, THEN: Each Obligated Party is (separately) subject to this Protocol.

22.5.2. Off-limits activities

(Capitalized terms are defined below.)

During the Noncompete Period, the Obligated Party will do any of the following things within the Noncompete Territory unless the Con­tract expressly provides otherwise:

  1. engage or participate, in any manner or in any capacity, in any Competing Business;
  2. invest in, or lend money to, any other individual or organization that proposes or plans to do anything prohibited by the noncompetition obligations of the Con­tract except as provided at § 22.5.5 below;
  3. knowingly assist any other individual or organization to do anything prohibited by the noncompetition obligations of the Con­tract;
  4. engage or participate in any of the things listed in subdivisions 1 through 3:
    1. directly or indirectly; nor
    2. for the Obligated Party's own benefit or that of someone else.

22.5.3. Key definitions

In this Protocol:

  1. "Noncompete" refers to the noncompetition obligations of this Protocol and any other noncompetition obligations under the Con­tract.
  2. "Noncompete Period" refers to the period that:
    1. begins upon the effective date of the Con­tract; and
    2. ends at midnight at the end of the day on the date one day after the Business Relationship End.
  3. "Noncompete Territory" refers to:
    1. the circular geographic area, with a radius of ten feet, centered on the principal place of business of the Company; and
    2. all market segments within that geographic area.
  4. "Company" refers to the individual(s) and/or organization(s) clearly identified in the Con­tract as beneficiaries of the Noncompete.
Note

().  These definitions are those most likely to be negotiated; the gap-filler values here are intentionally ridiculous.

Subdivision 3.a — principal place of business: See 21.29.

Subdivision 4 — caution: Drafters should be sure to identify the specific company or companies that are to be protected by the Noncompete, lest they end up with an unenforceable obligation — as happened to a holding company in Delaware's Frontline case, as discussed at 22.5.12.11.

22.5.4. Other definitions

  1. "Business Relationship" refers to the direct- or indirect business relationship between the Obligated Party and the Company — this could be, without limitation, an Employment relationship or a Transaction.
  2. The "Business Relationship End" will occur at the earliest of the following:
    1. in the case of Employment, on the last day of the Obligated Party's employment in question;
    2. in the case of a Transaction, at the closing of the Transaction; and
    3. in any case, upon the termination or expiration of the Con­tract (but see also 22.5.10 concerning survival of the Noncompete).
  3. Engaging in a "Competing Business" refers to competing with — and/or preparing to compete with — any Protected Business.
  4. "Employment" refers to a Business Relationship where the Obligated Party is an individual who is employed by the Company or by an affiliate of the Company. (For emphasis: The Employment could end even if the Con­tract does not, and vice versa.)
  5. "Protected Business" refers to any business in which, during the Business Relationship, both of the following were true:
    1. the Company: (a) engaged in the business, and/or (b) demonstrably made active preparations to enter the business; and
    2. the Obligated Party: (a) participated in the Company's business and/or active preparation, and/or (b) had access to the Company's confidential information concerning that business and/or active preparation.
  6. "Transaction" refers to a merger, asset sale, or similar transaction, in which (directly or indirectly) the Company and the Obligated Party are both involved.
Note

().  Subdivision 1: The Business Relationship between the Obligated Party and the Company could be indirect if, for example: (i) one company (the "target") is acquired by another; and (ii) as part of the deal, the Obligated Party is an executive of the target company who agrees not to compete with the acquiring company for a specified period of time.

Subdivision 2: The Business Relationship End is defined to make it relatively easy to determine when the Noncompete would expire. Otherwise, the Noncompete might be unenforceable, as happened in Texas's Central States Logistics case discussed at 22.5.12.12.

22.5.5. Limited exception for stock ownership

  1. For any given organization engaging in any Competing Business, the Noncompete does not prohibit the Obligated Party from purely-passively owning, directly or findirectly, no more than 5% each of publicly-traded equity securities of the organization.
  2. For this purpose, equity securities includes (without limitation) securities convertible into equity securities or exercisable or exchangable into equity securities.
  3. As a hypothetical example:
    • The Obligated Party owns 2% of the publicly-traded common stock of an organization that engages in a Competing Business.
    • The Obligated Party also owns warrants that are convertible into a total 2.9% of the common stock.
    • That adds up to 4.9% — which is under the 5% limit.
Note

Subdivision 1: The "publicly-traded" aspect is intended to keep the Obligated Party from serving as, e.g., an angel- or venture-capital investor in a competing business.

22.5.6. No acquiring of control of Obligatred Party by competitor

During the Noncompete Period, the Obligated Party will not let him‑, her‑, or itself become controlled (as defined at Protocol 20.1) by any individual or organization that engages (or, so far as the Obligated Party is aware, contemplates engaging) in any Competing Business.

Note

().  This is listed separately from § 22.5.2 because it's likely to be a negotiation point.

Example: The Delaware chancery court held that a company violated a noncompetition covenant when it was acquired by, and thus became an affiliate of, a competitor. See Symbiont.io, Inc. v. Ipreo Holdings, LLC, No. 2019-0407, slip op. (Del. Ch. Aug. 13, 2021).

22.5.7. Tolling of Noncompete Period for noncompliance

  1. This section will apply if the Company successfully asserts, before a court or arbitrator, that the Obligated Party did not comply with the Noncompete.
  2. In any such case, the Noncompete Period will be tolled (that is, extended) by the period —
    1. beginning when the Obligated Party began the noncompliance; and
    2. ending when the Obligated Party's counsel reports in writing to the court (or arbitrator, if applicable) that the Obligated Party ceased the noncompliance.
Note

().  The rationale here is to help the Company get the benefit of its bargain in case the Obligated Party defies the noncompetition restrictions. Absent a tolling provision like this, a court might well take the position that a noncompete could no longer be enforced if its term had ended during the course of the litigation. See, e.g., Daneshgari v. Patriot Towing Servs., LLC, 864 S.E.2d 710, 712-13 (Ga. App. 2021) (citing cases).

Some courts, though, seem to be conservative in applying tolling provisions of this kind. Example: In Minnesota's Petitti case, a state appeals court reversed and remanded a temporary injunction, on grounds that the trial court's application of a tolling provision had impermissibly expanded the scope and duration of the underlying noncompetition covenant. See Medtronic, Inc. v. Petitti, No. A18-0010, slip op. (Minn. App. Jul. 23, 2018) (unpublished).

This section isn't limited to extending an injunction, just in case a court or arbitrator awards damages for violation of the Noncompete but doesn't enjoin violation (e.g., by refusing to honor the tolling provision of this section).

22.5.8. Blue-pencil request if this Protocol is unenforceable

  1. The Obligated Party acknowledges (with the effect stated at Protocol § 11.2) that the noncompetition obligations under the Con­tract are reasonable and help to protect the Company's legitimate business interests.
  2. The Obligated Party therefore WAIVES any defense or other assertion to the contrary that the Obligated Party might otherwise be able to offer.
  3. As a fallback, though: If a tribunal of competent jurisdiction nevertheless determines that one or more of the noncompetition obligations set forth in the Con­tract are unreasonably broad or otherwise unenforceable under applicable law, THEN:
    1. The Obligated Party hereby agrees that the tribunal's determination will not be binding beyond the geographic area in which the tribunal has jurisdiction.
    2. In addition, the Obligated Party and the Company jointly request that the tribunal "blue-pencil," that is, reform, the noncompetition obligation — solely for purposes of enforcement within the geographic area of the tribunal's jurisdiction — to the minimum extent required to render it enforceable within that area.
  4. Protocol 21.3 (blue-pencil request) is incorporated by reference into this § 22.5.8.
Note

Subdivision 1: This confession of validity might be brusquely dismissed by a court — that happened in the Delaware chancery court's Kodiak case, discussed at 8.18.4.

Subdivision 3.b's blue-pencil request might suffer a similar fate, as happened in the same case.

22.5.9. Obligated Party: Ask your lawyer about this Protocol

The Obligated Party acknowledges that, in agreeing to the noncompetition obligations of the Con­tract, the Obligated Party had the opportunity to consult with legal counsel of the Obligated Party's choice concerning those obligations.

Note

().  See also the certification of legal-review competion at § 3.10 of Protocol 3.16 (Signature Mechanics Protocol.

Concerning the legal effect of acknowledgements, see 11.2.

22.5.10. Survival of noncompetition obligations

  1. The Obligated Party's noncompetition obligations under the Con­tract will continue in effect until the end of the Noncompete Period — even if the Con­tract itself, or the Business Relationship, is terminated or expires.
  2. In case of doubt: This section is not intended to expand, nor to limit, any other survival provision in the Con­tract.
Note

This survival clause seeks to avoid the result in an Eighth Circuit's case where an employee quit her job and terminated her employment agreement, as expressly allowed by that agreement: The appeals court held that by terminating her employment agreement, the employee had also unilaterally terminated her noncompetition obligation. See Miller v. Honkamp Krueger Fin. Servs., Inc., 9 F.4th 1011 (8th Cir. 2021) (reversing and vacating preliminary injunction).

22.5.11. Option: Exception for Fired- or Laid-Off Employees

  1. If this Option is part of the Con­tract, it will apply only if all of the following are true:
    1. the Obligated Party is an individual who is an employee of the Company — not an individual contractor; and
    2. the Obligated Party's employment is terminated by the Company.
  2. If that happens, then the Obligated Party's noncompetition obligations under the Con­tract will end at the same time as the Obligated Party's employment with the Company.
Note

().  This exception is is regarded by some as a sensible one, taking employees' legitimate interests into account.

This exception doesn't address whether a resignation by an employee might amount to a "constructive termination" by the Company and thus qualify for the exception of this subdivision. See generally, e.g., Deborah C. England, Constructive Discharge: Were You Forced to Resign? (Nolo.com, undated).

22.5.12. Additional notes

22.5.12.1. The business context

Noncompetition covenants are seen in employment agreements (sometimes) and in corporate-acquisition agreements (often). This Protocol is set up to accommodate noncompetition covenants in both employment agreements and other contracts such as M&A agreements.

22.5.12.2. Caution: Noncompetes for employees might not be enforceable

The enforceability of post-employment noncompetition covenants in the United States is changing rapidly, especially when it comes to low-wage workers. Drafters of noncompetition covenants for employees should definitely be (or consult) experienced legal counsel. See generally, e.g., Michael Wexler, Katherine Perrelli, and Robert Milligan, 50 State Desktop Reference - What Businesses Need to Know about Non-Competes and Trade Secrets Law - 2024 (JDSupra.com).

Post-employment noncompetes are essentially prohibited in California, as discussed just below. And they're highly restricted in some other states, as discussed at 22.5.12.6.

(The California-based global law firm Morrison Foerster, affectionately known in legal circles as "MoFo," has a useful 2025 update on that subject.)

22.5.12.3. California's per-se prohibition for post-employment agreements

Famously, a California statute has been interpreted as a per-se rule prohibiting virtually all post-employment noncompetition covenants. See Cal. Bus. & Prof. Code § 16600.

(Business-to-business noncompetes, however, are subject to a rule of reason. See Ixchel Pharma, LLC v. Biogen, Inc., 9 Cal. 5th 1130, 1150 (2020) (on certification from Ninth Circuit) (rule of reason).

Exception: In California, a noncompete in a contract for the sale of all of a person's interest in a business (in various "flavors") might be permitted by an statutory exception to the general prohibition. The same could be true in the case of dissolution or dissociation from a partnership. See Cal. Bus. & Prof. Code §§ 16601, 16602.

Relatedly: A California employment agreement purported to require assignment of post-employment inventions. A federal appeals court held that the assignment requirement was, effectively, a noncompetition covenant that was unenforceable under a separate provision of California law. See Whitewater West Industries, Ltd. v. Alleshouse, 981 F.3d 1045 (Fed. Cir. 2020) (reversing judgment after bench trial), citing Cal. Bus. & Prof. Code § 16600.

22.5.12.4. What if both California and another state are involved?

It sometimes happens that an employee of a non-California company is subject to a noncompete, then quits to join a California competitor of the former employer. In that situation, a 2024 California statute can come into play:

16600.5. (a) Any contract that is void under this chapter is unenforceable regardless of where and when the contract was signed.

(b) An employer or former employer shall not attempt to enforce a contract that is void under this chapter regardless of whether the contract was signed and the employment was maintained outside of California.

(c) An employer shall not enter into a contract with an employee or prospective employee that includes a provision that is void under this chapter.

(d) An employer that enters into a contract that is void under this chapter or attempts to enforce a contract that is void under this chapter commits a civil violation.

(e) (1) An employee, former employee, or prospective employee may bring a private action to enforce this chapter for injunctive relief or the recovery of actual damages, or both.

(2) In addition to the remedies described in paragraph (1), a prevailing employee, former employee, or prospective employee in an action based on a violation of this chapter shall be entitled to recover reasonable attorney’s fees and costs. Cal. Bus. & Prof. Code § 16600.5.

Counterexample: In the First Circuit's DraftKings case, involving the Massachusetts-based online gambling company:

  • The employment agreement of a DraftKings employee included both a noncompete and a Massachusetts choice of law clause.
  • The employee relocated to California just ahead of quitting and going to work for a competitor.

The First Circuit affirmed a Massachusetts federal court's injunction enforcing the noncompete. (The facts and analysis are more complicated than that, but they're likely of little or no interest to contract drafters). See DraftKings Inc. v. Hermalyn, 118 F.4th 416 (1st Cir. 2024) affirming 732 F. Supp. 3d 84 (D. Mass. 2024).

22.5.12.5. California also has an employee-notification requirement

In 2023 California enacted a law requiring employers:

to notify current and former employees (who were employed after January 1, 2022, whose contracts include a noncompete clause, or who were required to enter a noncompete agreement, that does not satisfy an exception to this chapter) in writing by February 14, 2024, that the noncompete clause or agreement is void. The law makes a violation of these provisions an act of unfair competition pursuant to California’s unfair competition law. Robert B. Milligan, Golden State Crackdown on Non-Competes: California Enacts Second Non-Compete Law To Curtail Use of Non-Competes With Employees (TradeSecretLaw.com 2023); see also Robert B. Milligan, New California Non-Compete Law Furthers the State’s Employee Mobility Protections and Seeks to Void Out of State Employee Non-Compete Agreements (TradeSecretLaw.com 2023).

22.5.12.6. Post-employment noncompetes in some other states

Caution: The following list might well be out of date; drafters of noncompetition covenants should definitely check the law in the relevant state(s).

–  Colorado invalidates noncompetition covenants outside of certain specific areas — and the state recently criminalized certain conduct that could include employers' attempts to enforce post-employment noncompetition covenants. See Dawn Mertineit, Colorado Criminalizes Attempts to Curb Competition (TradeSecretLaw 2022).

–  Delaware's supreme court has held that a forfeiture clause that didn't preclude competition can be enforced: "When sophisticated actors … agree that a departing partner will forfeit a specified benefit should he engage in competition with the partnership, our courts should, absent unconscionability, bad faith, or other extraordinary circumstances, hold them to their agreements." Cantor Fitzgerald, L.P. v. Ainslie, 312 A.3d 674, 677 (Del. 2024) (reversing chancery court).

–  In 2021, the District of Columbia enacted a ban on most post-employment noncompetes; the ban includes civil penalties, a private right of action, and anti-retaliation provisions. See Ban on Non-Compete Agreements Amendment Act of 2020, Act Number A23-0563, 68 D.C. Register 782 (Jan. 15, 2021) (browsable PDF); Risa B. Boerner, What You Need to Know About Washington, D.C.'s Non-Compete Agreements Ban (AmericanBar.org Dec. 15, 2021) (ABA members only).

–  In Florida, the CHOICE Act (2025) explicitly validates specified post-employment noncompetes (and garden-leave provisions) lasting up to four years [!] — with no requirement to be geographically reasonable, but with procedural prerequisites — for employees earning more than twice the annual mean wage in the relevant county. The same applies to independent contractors, but licensed health-care practitioners are excluded. See generally Raquel Ramirez Jefferson, Florida's CHOICE Act Transforms Noncompete and Garden Leave Agreements (JDSupra.com 2025).

–  Effective in 2022, Illinois amended its noncompetition law to add significant substantive- and procedural restrictions. See, e.g., Sarah E. Flotte and Benjamin Prager, Major Changes to Illinois’ Non-Compete and Non-Solicit Laws: Company Agreements Likely Require Revision (PerkinsCoie March 1, 2022).

And an Illinois appellate court explained: "Illinois courts have repeatedly held that there must be at least two years or more of continued employment to constitute adequate consideration in support of a restrictive covenant. This rule is maintained even if the employee resigns on his own instead of being terminated." Fifield v. Premier Dealer Services, Inc., 993 N.E.2d 938, 943-44 (Ill. App. 2013) (affirming declaratory judgment that noncompetition covenant was unenforceable) (citations omitted, emphasis added).

–  Massachusetts also imposes restrictions on post-employment noncompetes, both generally and for specified professions. See Mass. General Laws c.149 § 24L; see generally Massachusetts law about noncompetition agreements (Mass.gov, undated): "A compilation of laws, cases and web sources on employee noncompetition law by the Trial Court Law Libraries." ]

–  Oregon: Under the state's S.B. 169, effective on January 1 2022 noncompetes must be in writing; can be for no more than 12 months; and can be used only with employees who earn at least USD $100,533 or more annually (adjusted for inflation). Noncompetes not meeting these requirements are void, not merely voidable. See Jonathan Rue and Elizabeth White, Effective Use of Non-Solicitation and Confidentiality Agreements in Oregon After S.B. 169 (JDSupra.com 2022).

–  By statute, Texas allows noncompetes, but only subject to certain prerequisites, for example, the noncompete provision must be ancillary to an otherwise-enforceable contract; it must be reasonable in time, geographic scope, and operating scope; and it must be supported by separate consideration. See Zach Wolfe, Wolfe on Texas Non-Compete Litigation, or, My Big Fat Texas Non-Compete Paper (2021). The author reviews: • the current Texas non-compete statute, starting at page 14 of the paper; • what he refers to as the Five Year Rule about what constitutes a reasonable time period; and • case law concerning reasonable geographic- and operating scope.

–  In 2025, the Texas Legislature amended the state's noncompetition law to impose additional restrictions on noncompetes for the health-care professionals. See S.B. 1318, summarized in Jesse M. Coleman and Reeves Gillis, Lone Star Limitations — Texas Further Narrows the Use of Non-Competes with Medical Professionals (TradeSecretsLaw.com 2025).

For additional information, it'd be highly advisable to do a Google search about specific states of interest.

22.5.12.7. Federal-law enforceability issues?

At the federal level, the Federal Trade Commission, under chair Lina Khan, adopted a Noncompete Rule that essentially banned post-employment noncompetes. In response, several business organizations sued in federal court and obtained a preliminary injunction forbidding enforcement of the rule. See Ryan LLC v. FTC, 746 F. Supp. 3d 369 (N.D. Tex. 2024) (granting motion for preliminary injunction against FTC's Noncompete Rule). At this writing (July 2025), the FTC's appeal is pending at the Fifth Circuit, case no. 24-10951.

Moreover, in early 2022 the Treasury Department took a hard look at noncompetition agreements and proposed that the Justice Department start to use antitrust law to "disciplin[e] the use and abuse of restrictive employment agreements, including non-compete agreements …." U.S. Dept. of the Treasury, The State of Labor Market Competition 28, 47, 51, 54 (Treasury.gov Mar. 7, 2022); see also U.S. Dept. of Justice, Press Release, Justice Department and National Labor Relations Board Announce Partnership to Protect Workers (Justice.gov Jul. 26, 2022).

At this writing, it's not completely clear what position the second-term Trump administration will take on noncompetition covenants. A law firm memo summarizes:

  • The Trump administration is seeking to pause the FTC’s pursuit of appeals of two district court decisions that blocked the FTC’s rule banning noncompetes, suggesting an expected shift in the government’s approach to the rule.
  • Despite the motions to stay, and though the FTC may not pursue any further formal rulemaking on the issue, FTC Chairman Andrew N. Ferguson is continuing to emphasize his view that noncompete agreements potentially harm competition in labor markets. Tobias E. Schlueter and Zachary V. Zagger, Trump Administration Halts Appeals of Rulings Blocking FTC Noncompete Ban (Ogletree.com 2025).
22.5.12.8. How long can a noncompete permissibly last?

Even in those jurisdictions that allow enforcement of post-employment noncompetes, the noncompetition covenants must be "reasonable" in time.

DCT note: My general impression about noncompete periods is that:

  1. For post-employment noncompetition covenants, one year is likely to be a reasonably-safe bet in many jurisdictions;
  2. For post-acquisition noncompetition covenants, two- to four years seems not-uncommon.
22.5.12.9. The requirement of reasonable scope

Noncompetes must be reasonable not just in time, but also in geographic- and market scope.

To be sure, in a global economy, many modern noncompetition covenants prohibit competition anywhere in the world. But that can raise red flags, especially for largely-local enterprises.

22.5.12.10. The requirement of a legitimate business interest

Noncompetition covenants must also be supported by a legitimate business interest in restraining competition, such as protection of a company's confidential information or its brand identity. Example: The latter consideration can be seen in the Second Circuit's "Hayley Page" decision involving the originator of that line of bridal apparel. See JLM Couture, Inc. v. Gutman, 24 F.4th 785 (2d Cir. 2022) (affirming, in relevant in part, preliminary injunction against social-media "influencer").

22.5.12.11. Caution: Get the details right

In a Delaware case, an employment agreement's noncompetition covenant barred employees from competing with the holding company. But the noncompete didn't prohibit employees from competing with their actual former employer, which was a subsidiary of the holding company. So, the former employer was unable to enforce the noncompete against the now-former employees. Vice Chancellor Will remarked: "This case presents a textbook example of why parties should ensure their contracts say what they mean and mean what they say." Frontline Techs. Parent, LLC v. Murphy, No. 2023-0546-LWW, slip op. (Del. Ch. Aug. 23, 2023) (granting former employees' motion to dismiss), discussed in Glenn D. West, Distinguishing Between Ownership of an Entity and the Entity Itself (PrivateEquity.Weil.com 2023).

22.5.12.12. Caution: Be sufficiently specific

If it's not easy, that might invalidate the noncompete. Example: In a Texas case, a noncompete period was written to run for 24 months "following the Carrier's last contact with any client or client[s] of Broker …." A Houston court of appeals ruled that the noncompete was unenforceable because: "… there is no means for [the Carrier] to know when it has had its last contact with any client or clients of [the Broker]. Because [the Carrier] cannot determine when the time of the covenant not to compete has ended, it cannot be enforced as written." Central States Logistics, Inc. v. BOC Trucking, LLC, 573 S.W.3d 269, 277 (Tex. App–Houston [1st Dist.] 2018) (reversing judgment below about noncompete provision and rendering take-nothing judgment against plaintiff; citations omitted).

22.5.12.13. Would a federal court enforce state law about non-competes?

A Ninth Circuit case illustrates a "circuit split," i.e., a split among different federal appellate courts as to how federal courts should deal with state laws concerning noncompetition and forum selection:

  • A contract between a New Jersey company and a California employee contained a post-employment noncompetition covenant.
  • The contract also required any litigation between the company and the employee to take place in New Jersey.
  • The employee quit the New Jersey company and goes to work for one of the company's competitors.
  • The competitor-new employer competitor filed a preemptive lawsuit in federal court in California seeking a declaratory judgment that under California law, both the employee's noncompetition covenant and the forum-selection provision are unenforceable.
  • The (former) employer moved to transfer the lawsuit to New Jersey.

The federal district court in California denied the motion, citing California's ban on such forum-selection provisions; the Ninth Circuit affirmed. See DePuy Synthes Sales, Inc. v. Howmedica Osteonics Corp., 28 F.4th 956 (9th Cir. 2022) (affirming denial of motion to transfer), discussed in Sarah Tishler, Forum Selection Clauses Head To The Supreme Court (JDSupra.com 2022); cert. denied, 143 S. Ct. 536 (2022). Additional reading: See 21.12.9.22.

22.5.12.14. Will both parties need to sign a noncompete?

In an Alabama case, the state's supreme court affirmed summary judgment that a employee's noncompetition covenant — set forth in a separate, later-signed addendum to the employment agreement — was unenforceable because it was not signed by the employer, whereas a state statute required signature by all parties because of the nature of the noncompetition covenant. See Amanda Howard Real Estate, LLC v. Lee, 387 So. 3d 120, 123-24 (Ala. 2023) (corr. Aug. 15, 2023) (affirming summary judgment).

22.5.12.15. "Garden leave": Salary during noncompete period?

A prospective employee who is asked to sign a noncompete provision might want to try to bargain to be paid, in case of termination, some or all of the employee's pre-termination compensation while the employee sits out the noncompete period. This is referred to in the UK as "garden leave" and is now a requirement in Massachusetts for post-employment noncompetes. See Mass. Gen. L. ch. 149 § 24(c)(vii); Garden leave (Wikipedia.org).

22.5.12.16. Include specific examples of prohibited activities?

Some drafters might feel the need (perhaps obsessive) to list specific activities that an employee is prohibited from engaging in at a new, competing, employer; the following have been harvested from various noncompetition clauses at LawInsider:

  • officer, director, manager (at any level), employee, partner, member (of LLC)
  • advisor, agent, consultant, contractor, distributor, joint venturer, manufacturer's representative, sales representative, service provider
  • owner, co-owner, investor
  • lender, guarantor, creditor
22.5.12.17. Noncompetes in a sales of a business get a slightly-different analysis

In some jurisdictions, it's different when you're selling a business than when you're "just" an employee agreeing not to compete with your employer after your employment ends.

For example, by statute, California's outright ban on post-employment noncompetes doesn't apply in certain situations:

Any person who sells the goodwill of a business,

or any owner of a business entity selling or otherwise disposing of all of his or her ownership interest in the business entity,

or any owner of a business entity that sells (a) all or substantially all of its operating assets together with the goodwill of the business entity, (b) all or substantially all of the operating assets of a division or a subsidiary of the business entity together with the goodwill of that division or subsidiary, or (c) all of the ownership interest of any subsidiary,

may agree with the buyer to refrain from carrying on a similar business within a specified geographic area in which the business so sold, or that of the business entity, division, or subsidiary has been carried on,

so long as the buyer, or any person deriving title to the goodwill or ownership interest from the buyer, carries on a like business therein.

See Cal. Bus. & Prof. Code § 16601 (broken up — this could definitely use BLUF editing).

A California appeals court — rejecting an arbitrator's contrary ruling about the law, as allowed by the arbitration agreement — held that, when a business owner sells only part of the business, the per-se prohibition of § 16600 doesn't apply; the court went on, however, to say that a rule-of-reason analysis is still required. See Samuelian v. Life Generations Healthcare, LLC, 104 Cal. App. 5th 331, 353-56 (reversing trial-court confirmation of arbitration award), modified, 104 Cal. App. 5th 1296a (2024). Hat tip: Cooper J. Spinelli, Eric Akira Tate, and Zoe E. Escarcega Non-Compete Round Up- FTC, NLRB, California and Delaware (MoFo.com 2025). Concerning enhanced appeals of arbitration awards, see the notes at Option 21.1.26.

But that doesn't mean a court will rubber-stamp a merger-and-acquisition noncompete; as noted by the Delaware chancery court: "The acquirer's valid concerns about monetizing its purchase do not support restricting the target's employees from competing in other industries in which the acquirer also happened to invest." Kodiak Bldg. Partners, LLC v. Adams, No. 2022-0311-MTZ, slip op. at part II.A.2, text acc. nn.67 et seq. (Del. Ch. Oct. 6, 2022) (denying Kodiak's motion for preliminary injunction; extra paragraphing added, footnote omitted).

22.5.12.18. Noncompete pay- and equity forfeitures might be a different story

This is an area where I've seen references to court holdings, but I haven't yet dug into the law in different jurisdictions. This is another area where lawyers should definitely check the law in the relevant jurisdiction(s), and nonlawyers should definitely get legal advice.

Here are some initial notes:

().  Delaware's supreme court held that Cantor Fitzgerald, a global financial services firm, wasn't precluded from enforcing a noncompete provision that called for departing limited partners to forfeit their partnership interests if they chose to compete with Cantor within two years after leaving the firm:

When sophisticated actors avail themselves of the contractual flexibility embodied in the Delaware Revised Uniform Limited Partnership Act—a statute that is expressly designed "to give maximum effect to the principle of freedom of contract and to the enforceability of partnership agreements"—and agree that a departing partner will forfeit a specified benefit should he engage in competition with the partnership, our courts should, absent unconscionability, bad faith, or other extraordinary circumstances, hold them to their agreements. Cantor Fitzgerald, LP v. Ainslie, 312 A.3d 674, 677 (Del. 2024) (reversing and remanding chancery-court; cleaned up).

The state supreme court later advised the Seventh Circuit that its Cantor holding wasn't restricted to the limited-partnership context; the court said that the same "employee choice" doctrine would allow forfeiture of equity grants by a plant manager, formerly employed by an auto-salvage and recycled-parts company, who moved to a competitor. See LKQ Corp. v. Rutledge, 337 A.3d 1215 (Del. 2024) (en banc), responding to 96 F.4th 977, 987 (7th Cir. 2024); subsequent proceeding, 126 F.4th 1247 (7th Cir. 2025) (reversing and remanding district court's summary judgment in favor of Rutledge).

Counterexample: In another Delaware case: After a company was acquired, a longtime employee signed an equity agreement with the acquiring company.

  • The equity agreement included a noncompete — but it also said that the equity grant would automatically be forfeited if the employee breached the noncompete.
  • There was no other consideration for the noncompete (e.g., no right to continued employment by the acquiring company).
  • The employee indicated his desire to leave the acquiring company; negotiations for his exit were unproductive.
  • Eventually the company fired the employee, purportedly for cause, and sued the now-former employee for violating the noncompete.

Delaware's chancery court — held that the automatic equity forfeiture had dissolved the employee's noncompete obligation for lack of consideration (and implicitly distinguished Cantor on that basis). See North American Fire Ultimate Holdings LP v. Doorly, No. 2024-0023-KSJM, slip op. at n.33-34 & accompanying text (Del. Ch. Mar. 7, 2025) (granting former employee's motion to dismiss).

(One wonders whether North American Fire and Cantor Fitzgerald might indicate a clash of views between Delaware's chancery court and supreme court.)

Massachusetts enacted a statute that subjects forfeiture-for-competition agreements to the same exacting standards as "classic" noncompetes. See Massachusetts Noncompetition Agreement Act, Mass. Gen. L. c. 149 § 24L(a).

Relatedly: By its terms, the Massachusetts noncompete statute excludes employee- and customer-nonsolicitation agreements from the statute's coverage, along with confidentiality agreements; invention-assignment agreements; garden-leave agreements; and forfeiture agreements that aren't triggered by competition. See id. (definition of "noncompetition agreement"); Miele v. Foundation Medicine, Inc., No. SJD-13697 (Mass. Jun. 13, 2025) (answering certified question and remanding to trial court: "a forfeiture clause triggered by a breach of a nonsolicitation agreement does not constitute a 'forfeiture for competition agreement' subject to the act") (emphasis added).

23. Intellectual property

23.1. Patent infringement basics (notes)

23.1.1. The claims of a patent are what determine infringement

People sometimes get all worked up about the fact that a patent describes X or Y or Z that can be found in prior art.

What matters for infringement purposes, however, is not so much what the patent describes, as what it claims. The exact wording of the patent claims will be crucial.

23.1.2. Each claim in a patent is a separate infringement checklist

You can also think of each individual claim in a patent as being a separate infringement checklist: At trial, the patent owner’s lawyers and expert witness(es) will methodically talk the jury through that claim (and probably others as well), putting on evidence to show that every claim element is present in what the defendant is doing.

Here are a couple of canonical hypothetical examples (simplified — they do not address the doctrine of equivalents):

Claim 1: A seating structure comprising:

(a) a substantially-horizontal seating platform, and

(b) at least three legs extending generally downward from the seating platform.

* * * 

Claim 5: A chair comprising:

(a) a substantially-horizontal seating platform; and

(b) four legs extending generally downward from the seating platform.

In these examples:

  • A three-legged stool with a back support would infringe our hypothetical claim 1 above, because all of the checklist elements in that claim are present in the three-legged stool. Importantly, the additional presence of the of the stool's back support is irrelevant.
  • In contrast, a three-legged stool would not infringe hypothetical claim 5 above, because that claim requires an infringing chair to have four legs.

23.1.3. Patent-claim interpretation is often a big deal

Very often, patent owners and accused infringers engage in expensive legal battles over "claim construction," that is, the proper interpretation of different words and phrases in a patent claim. In the examples above, such a battle might break out over whether the term "seating platform" encompasses a camp chair with a soft, foldable cloth seat.

As a general rule, a given word or phrase in a claim will be interpreted in light of considerations such as the following:

  • the ordinary meaning of the term in the relevant art(s);
  • any special meaning stated by the inventor in the patent’s written description — the inventor is free to be his- or her own lexicographer;
  • how the term was used in the back-and-forth correspondence between the inventor and the patent examiner, referred to as the ‘prosecution history’ of the patent application;
  • whether a particular meaning is required — other things being equal, a narrower interpretation that will preserve the patentability of the claim will be preferred over a broader interpretation that would result in the claim being invalidated by prior art. (If this issue comes up during the prosecution of the patent application, the patent examiner is supposed to require the applicant to amend the claim to eliminate the ambiguity.)

23.1.4. Only one patent claim need be proved infringed

As long as the patent owner proves that at least one claim is infringed, and the defendant doesn’t prove that the infringed claim(s) are invalid, then the defendant is liable for infringement.

Suppose hypothetically that the example claims above were actually in an unexpired patent, and that they were not proved to be invalid.

In that case, anyone who made, used, sold, offered for sale, or imported a three-legged stool would be liable for infringement, even though the stool infringed only claim 5 and not claim 1.

Here's an analogy: Imagine that the claims of a patent are like arrows in a quiver, and that a hostile archer (a patent owner) were to shoot several arrows in your direction:

  • Some arrows might clearly be going to miss you; those are analogous to patent claims that you clearly don't infringe. (This assumes a judge and/or jury agrees that these arrows have missed you, which isn't always a given.)
  • But suppose that some of the arrows in flight appear on their way to hitting you somewhere on your body. It's up to you to try to knock down all of those arrows before they hit you.

23.1.5. Important: You can infringe a patent without knowing it

A patent can be infringed by someone who isn't even aware that the patent exists. This is unlike the case for copyright infringement (which requires copying of protectable "expression") and trade-secret misappropriation (which requires having had access to the trade secret).

23.2. Trademark License

23.2.1. Applicability; parties

When this Protocol is agreed to, it presupposes that a party clearly specified in the Con­tract (the "Mark Owner") is agreeing in the Con­tract not to take legal action against another clearly-specified party (the "User") for using one or more specified trademarks, service marks, trade names, designs, and/or trade dress ("Marks") of the Mark Owner — that agreement is referred to here as the "Trademark License".

Note

().  This Protocol draws on ideas found in a trademark license agreement form of The University of Texas at Austin (my alma mater), which for many years has been one of the most successful collegiate brand merchandisers.40

For a readable overview of some basic trademark-law concepts, see Justice Kagan's opinion in the "Bad Spaniel" parody case: Jack Daniel's Properties, Inc. v. VIP Products LLC, 599 U. S. 140, 143 S. Ct. 1578, 1583 (2023).

23.2.2. Placeholder business terms

As a drafting checklist, the following "placeholder terms" apply except to the extent that the Con­tract specifies otherwise:

  1. What "Licensed Marks" are licensed? None.
  2. What is the "Territory" of the Trademark License? Only the city in which the User's initial address for notice is located, in all market segments.
  3. How long will the Trademark License last ("Trademark License Term")? The term of the Con­tract.
  4. What specific User goods and/or services are licensed ("Licensed Items")? None.
  5. Must the User conform to any detailed specifications for Licensed Items? None specified.
  6. Must the User conform to any detailed usage requirements for Licensed Marks? None specified.
  7. Is the Trademark License exclusive, in the Territory or any part of it (e.g., a geographic- or market segment)? No.
  8. May the User grant sublicenses for the Licensed Marks? No.

23.2.3. Grant of Trademark License

  1. The Mark Owner grants the User the Trademark License.
  2. For emphasis: The Mark Owner does not grant the User any other right, title, or interest in any Licensed Mark (nor in any other intellectual-property right owned or assertable by the Mark Owner) unless the Con­tract expressly says so.

23.2.4. What usage style(s) are allowed?

The User must comply with any specific style requirements for use of the Licensed Mark(s) that are set forth (or incorporated by reference) in the Con­tract, for example, color schemes, fonts, etc. — and in the absence of such specific style requirements, the User must use the Licensed Mark(s) only in styles conforming to both:

  1. the Mark Owner's then-current use of the Licensed Mark(s), and
  2. generally-accepted good commercial practice.

23.2.5. What marking is required?

Whenever displaying or otherwise using any Licensed Mark, the User must include appropriate notice(s) and/or marking consistent with applicable trademark law or otherwise specified by the Mark Owner, for example:

  1. the "®" (r-in-a-circle) symbol for registered marks; or
  2. the "™" or "SM" symbol for unregistered trademarks and service marks, respectively.
Note

R-in-a-circle: Concerning the "®" (r-in-a-circle) symbol, see generally 15 U.S.C. § 1111.

23.2.6. What usage specimens must be provided?

Whenever the Mark Owner reasonably so requests in writing from time to time: The User is to provide the Mark Owner, at no charge, with representative specimens of: (i) Licensed Items, and (ii) any other uses of Licensed Marks by the User such as, without limitation, advertisements.

Note

Trademark usage specimens: This is meant to give the Mark Owner the right to monitor all uses of Licensed Marks by the User, especially those that might not be authorized.

23.2.7. What would happen if the Mark Owner modified a Licensed Mark?

If the Mark Owner, from time to time, modifies any Licensed Mark and advises the User in writing of the modification, THEN the User must begin using the modified Licensed Mark, in lieu of the previous form, as soon as practicable afterwards.

23.2.8. What inspections of usage may the Mark Owner have done?

The Mark Owner may, from time to time, cause the following to be inspected — by the Mark Owner, or by another inspector reasonably acceptable to the User — to check for compliance with this Protocol; in addition, Protocol 9.8 (inspections) will apply to any such inspections on the User's premises:

  1. the User's use and/or display of the Licensed Marks; and/or
  2. only if specifically stated in the Con­tract or otherwise agreed: The User's facilities for making products that will bear Licensed Marks, for quality-control purposes.

23.2.9. Who may claim the trademark benefit of the User's use?

Any use of a Licensed Mark by the User will count as establishing ownership of that Licensed Mark by the Mark Owner, not the User.

Note

Benefit of trademark use: This section derives from some technical aspects of trademark law that are beyond the scope of this discussion.

23.2.10. What if a third party challenges a Licensed Mark?

Protocol 23.7 will govern any situation in which a third party:

  1. might be infringing a Licensed Mark; and/or
  2. challenges the validity or enforceability of the Mark Owner's rights in any Licensed Mark.

23.2.11. How would local registrations of Licensed Mark(s) be handled?

If (and only if) the Mark Owner so requests in writing, the User will take any steps that the Mark Owner reasonably considers necessary to do one or more of the following:

  1. register any Licensed Mark in the Territory (at the Mark Owner's expense);
  2. maintain or renew any registration of a Licensed Mark in the Territory (at the Mark Owner's expense); and/or
  3. prepare and file any registered-user registration required by applicable law for the User's use of Licensed Mark(s) in the Territory (at the User's expense).
Note

Trademark registrations, etc.: See generally World Intellectual Property Organization, Introduction to trademark law and practice § 9.5 (2d ed. 1993); see also the sample registered-user language at LawInsider.

23.2.12. What if\, by law\, the User acquires rights in the Licensed Mark?

This section will apply if, by law in any jurisdiction, the User acquires (or otherwise owns or comes to own) any right or other interest in a Licensed Mark.

  1. By the act of entering into the Con­tract, the User is also — effective at that time — assigning, that is, permanently transferring, all such rights to the Mark Owner, (23.6.1.9) without the need for any further action in that regard by either the User or the Mark Owner.
  2. At that same time, the User is likewise transferring to the Mark Owner all associated goodwill registrations, applications for registration, and rights to sue for infringement (if any).
  3. In case additional "paperwork" is needed in that regard: The User is to comply with the ownership-transfer and -confirmation provisions of Protocol 23.6.

23.2.13. What kinds of legal-type action may the User not take?

Unless the Mark Owner gives its prior written consent — which is up to the Mark Owner to grant or withhold, in the Mark Owner's sole discretion – the User must not, anywhere, do (nor attempt to do) any of the following:

  1. challenge the Mark Owner's rights in any Licensed Mark;
  2. challenge the legal protectability of any Licensed Mark;
  3. challenge the validity of any registration or application for registration, owned or approved by the Mark Owner, for any Licensed Mark;
  4. use any Licensed Mark, or any confusingly similar variation, in the User's corporate name or trade name;
  5. apply for registration or recordation of (i) any Licensed Mark, or (ii) the Trademark License;
  6. apply for registration of any Mark confusingly similar to any Licensed Mark;
  7. attempt to register any Web address (URL) that contains any Licensed Mark or any distinguishing feature of a Licensed Mark;
  8. attempt to register any Web address (URL) that is confusingly similar to any Licensed Mark;
  9. purport to grant, or to record or otherwise perfect, a security interest (or comparable lien-type interest) in, or to otherwise encumber, (i) any Licensed Mark; (ii) the Trademark License; and/or (iii) any registration or application for registration, anywhere, relating to any Licensed Mark;
  10. take any action that could invalidate or jeopardize any registration or application for registration of any Licensed Mark; and/or
  11. purport to assign the Trademark License — any such purported assignment will be void.

23.2.14. What if the User does take one of those prohibited legal-type actions?

If the User takes any of the actions prohibited by section 23.2.13, THEN The Mark Owner may — in its sole discretion — terminate the Trademark License; the termination will be effective immediately upon notice in accordance with Protocol 3.14.

23.2.15. Does the Mark Owner make any warranties about a Licensed Mark?

Unless the Con­tract unambiguously says otherwise: The Mark Owner DISCLAIMS any representation, warranty, condition, or term of quality, to the effect —

  1. that any Licensed Mark is legally protectable against use by others; or
  2. that the User's use of the Licensed Mark(s) under the Con­tract will not infringe the rights of one or more third parties.

23.2.16. What uses may the User not make of Licensed Marks?

The User must not use any Licensed Mark, nor any confusingly similar variation of any Licensed Mark:

  1. in any manner that is misleading or otherwise deceptive;
  2. in any manner that would, in the Mark Owner's sole judgment, be offensive to a relevant segment of the population;
  3. in any manner could otherwise diminish the reputation of the Mark Owner, its Marks, or its goods and/or services;
  4. on, or in promoting, Licensed Items that do not meet standards stated or referred to in the Con­tract;
  5. to mark and promote any goods or services other than Licensed Items;
  6. in advertising or promotion outside the Territory.

23.2.17. What else may the User not do concerning Licensed Marks?

The User must not:

  1. use any Licensed Mark in any manner except as authorized by the Con­tract;
  2. modify any Licensed Mark; nor
  3. include any Licensed Mark, nor any distinguishing feature of a Licensed Mark, as a feature or design element of any other Mark;
  4. use any Mark, other than Licensed Mark(s), on, or in connection with, Licensed Items — this section, however, does not preclude the User from using its own name or its genuine trade name in advertising its business;
  5. permit, encourage, or knowingly help, any other individual or organization to take any of the actions prohibited by this Protocol;
  6. establish, maintain, or staff facilities: (i) specifically for supporting customers' use of Licensed Items bearing any Licensed Mark if such customer use is reasonably likely to occur outside the Territory; nor (ii) outside the Territory for distributing Licensed Items bearing any Licensed Mark.

23.2.18. What is to happen to tangible Licensed Items upon termination?

If the Mark Owner so requests in writing upon any termination or expiration of the Trademark License, THEN the User, at its own expense, is promptly: (i) do one or more of the following, as selected by the User, and (ii) certify completion in writing to the Mark Owner:

  1. deliver to the Mark Owner all tangible Licensed Items bearing any Licensed Mark;
  2. permanently remove all Licensed Mark(s) from such Licensed Items; and/or
  3. destroy all Licensed Items bearing any Licensed Mark.

23.2.19. The User is responsible for its own business liabilities

The User must defend and indemnify the Mark Owner and the Mark Owner's Protected Group against any third-party claim arising out of or relating to:

  1. the User's business, including but not limited to any third-party claim of (i) product liability for Licensed Items; and/or (ii) infringement of third-party intellectual property rights by Licensed Items; and/or
  2. any breach of the Con­tract by the User.

23.2.20. No use of any Licensed Mark in the User's Web addresses\, etc.

  1. The User is not to establish any Internet domain name, subdomain, or path that: (i) contains any Licensed Mark or any variation thereof, and/or (ii) is confusingly similar to any Licensed Mark.
  2. If the User does so at any time, then the User must immediately transfer the same to the Mark Owner.
  3. As hypothetical examples: (20.21.4.2) If "Whizbang" is a Licensed Mark, then: • www.whizbang.com would be a domain name; • whizbang.example.com would be a subdomain; • www.example.com/whizbang would be a path; • each would contain the Licensed Mark; and substituting "whyzbang" for "whizbang" would (likely) be confusingly similar to the Licensed Mark.

23.2.21. Required: Immediate cessation of objected-to uses

If, at any time — by notice to the User in accordance with Protocol 3.14 — the Mark Owner objects to one or more particular uses of a Licensed Mark by the User as violating any of the prohibitions of this Protocol, THEN the User must, at its own expense:

  1. stop that use of the Licensed Mark;
  2. work with the Mark Owner to determine a suitable course of remediation;
  3. if reasonably determined by the Mark Owner: take one or more of the actions described at section 23.2.23.

23.2.22. The Mark Owner may seek injunctive relief

The Mark Owner may seek preliminary- and/or permanent injunctive relief against the User for violation of this Protocol. (21.10)

23.2.23. All use must stop upon termination

Upon expiraton or other termination of the Trademark License (for any reason), the User must immediately stop all use of the Licensed Mark(s) — other than use that would not violate applicable trademark law in the absence of a license, for example, so-called nominative use.

Note

Nominative trademark use: Example: A former distributor of Taser® energy weapons and cartridges ("LHB") went into business refurbishing and selling used Taser-brand weapons, holding itself out as an "Authorized TASER dealer" when it was not. In a series of orders, a federal district court in Nevada granted summary judgment and a permanent injunction against LHB, holding that LHB had exceeded the bounds of nominative use of the Taser mark. See the final order in Axon Enterpr., Inc. v. Luxury Home Buyers, LLC, No. 2:20-cv-01344-JAD-VCF (D. Nev. Mar. 8, 2024), as well as 683 F. Supp. 3d 1136 (D. Nev. 2023); ECF 79 (D. Nev. Jan. 16, 2024) (granting summary judgment in part); and ECF 95 (stipulation and order for permanent injunction).

23.2.24. Option: Specific Mark Owner Approval Required

If the Con­tract contains or otherwise agrees to this Option, THEN the User must not use any Licensed Mark, in advertising materials or otherwise, without the Mark Owner's specific approval of the proposed use.

Note

Specific use approval required: For an even more-detailed approval requirement, see page 2 of The University of Texas System's trademark license form, reproduced at https://tinyurl.com/UTTrademarkLicense.

23.2.25. Option: Automatic Approval Absent Objection

If the Con­tract contains or otherwise agrees to this Option, THEN the Mark Owner will be deemed to have approved a proposed specific use of a Licensed Mark if the Mark Owner has not advised the User, in writing, of the Mark Owner's disapproval on or before the end of ten business days after the Mark Owner's receipt of the proposal.

23.3. IP definitions

"IP" is an abbreviation for intellectual property, which is intended to be a collective term for one or more "IP assets"; each term (whether or not "asset" is capitalized) refers broadly to:

  1. approaches, concepts, developments, discoveries, formulae, ideas, improvements, inventions, know-how, methodologies, plans, procedures, processes, techniques, and technology, whether or not patentable;
  2. artwork, audio materials, graphics, icons, music, software, writings, and other works of authorship;
  3. designs, whether or not patentable or copyrightable;
  4. trademarks, service marks, logos, trade names, and the goodwill associated with each;
  5. trade secrets and other confidential information;
  6. mask works; and
  7. all other forms of intellectual property recognized by law.

23.3.1. Definition: IP right

"Intellectual-property right" and "IP right" (whether or not capitalized) refer broadly to any right — existing under any form of intellectual-property law or industrial-property law (see the illustrative list below) — to exclude others from utilizing one or more of intellectual property assets, at a relevant time, in a relevant location. The terms include, without limitation:

  1. the right to seek monetary- and/or injunctive (or other equitable) relief — in any judicial, administrative, or other forum having jurisdiction in a relevant location — for present or past infringement of any right referred to in this 23.3.1;
  2. all rights (whether registered or unregistered) in, or arising under laws concerning IP assets (see 23.3 above);
  3. any application then pending for such a right (where applicable), including without limitation an application: • for a patent, or • to register a copyright or trademark;
  4. any right to file such an application; and
  5. any right to claim priority for such an application.
Note

().  Some forms of IP right can arise automatically (in most jurisdictions) without the need for application or registration with government authorities. Examples include copyrights, trademark rights, and trade-secret rights — but not patent rights, which require actual issuance of a patent after a detailed examination of the application by a patent examiner.

For some of those automatic rights, registration might be required to take advantage of certain legal remedies. For example:

  • A copyright claim in a "United States work" must be registered with the Copyright Office — and the registration must be issued, not just applied for — before the copyright owner can file an infringement lawsuit (although upon registration the copyright owner can recover damages for infringement beginning at the date the registration application was filed). See 17 U.S.C. § 411(a); Fourth Estate Public Corp v. Wall-Street.com, LLC, 586 U.S. 296, 139 S. Ct. 881 (2019).
  • Federal registration of a trademark gives the mark's owner certain presumptions, i.e., that the mark is eligible for legal protection, etc.; those presumptions can greatly simplify (and reduce the cost of) the trademark owner's proving up its case in a trademark-infringement lawsuit. See 15 U.S.C. § 115.
23.3.1.1. Definition: IP Owner
  1. "IP Owner", in the context of an IP license, refers to a party A that licenses another party B under one or more IP rights, whether or not A technically "owns" the IP rights.
  2. Similarly, "ownership" of IP, and related terms such as "own" (whether or not capitalized) refer to legal- and equitable ownership of that IP under any law, anywhere in the world, relating to IP.
Note

().  This Protocol uses the term Owner and not Licensor to reduce the opportunities for written- and oral misstatements: Owner is more distinct, visually and audibly, from Licensee.

(This is another example of following the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings). If you've ever seen a well-drafted apartment lease, you might have noticed how it probably uses the terms Landlord and Tenant, as opposed to Lessor and Lessee.)

23.4. IP Infringement by Others

23.4.1. Lighthouse Protocol

23.4.1.1. Scenario & definitions
  1. Scenario: This Protocol applies when both of the following are true:
    1. a party to the Con­tract (referred to as the "Owner") owns — or can otherwise legally assert — one or more intellectual-property rights (see the definition at 23.3.1) concerning one or more "Offerings" of goods, services, and/or other items; and
    2. any other party to the Con­tract (the "Reporter") suspects that unauthorized use, copying, distribution, or modification of an Offering (collectively, "Unauthorized Activities") might be taking place.
  2. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol
Note

().  License agreements of various kinds will typically address what's supposed to happen if a third party does things that are supposed to require a license. (The licensee won't want to be making payments to the licensor if third parties are getting away without doing so.)

This Protocol spells out a sensible protocol for handling potential infringements by third parties; it's pretty much how such situations are typically handled. Here's a hypothetical example:

  • "Alice" licenses "Bob" under Alice's patent.
  • Under the license agreement, Bob is to pay Alice royalties on Bob's sales of "widgets" that are covered by the claims of Alice's patent. (For this purpose, the claims of Alice's patent are what matter, for reasons discussed beginning at 23.1.)
  • A third party, "Carol," makes widgets that compete with Bob's widgets and are also covered by Alice's patent claims.
  • Unlike Bob, Carol doesn't pay royalties to Alice; that means Carol has lower costs than Bob, giving her a competitive advantage over Bob.

In that situation, Bob will understandably want Alice to "do something!" about Carol.

This Protocol uses the term "Owner" even though a party granting an IP license might not actually own the IP in question. For example, by law an exclusive licensee of a patent or copyright might itself be able to grant licenses.

23.4.1.2. The Reporter reasonably cooperates with the Owner's Policing Efforts.

In any scenario described in 23.4.1.1, the Reporter —

  1. promptly advises the Owner of the situation;
  2. provides the Owner and/or its representatives (for example, legal counsel) with all relevant information reasonably requested about the Unauthorized Activities; and
  3. provides reasonable cooperation with any efforts by, or on behalf of, the Owner to prevent, stop, or limit the Unauthorized Activities ("Policing Efforts").
Note

The extent to which the Reporter's requested cooperation is considered "reasonable" would usually depends (in part) on (i) the likely expense of such cooperation, and (ii) the extent to which Owner agrees to bear that expense.

23.4.1.3. Disagreements about cooperation are escalated.

The parties escalate any disagreement about the reasonableness of requested cooperation as stated at Protocol 21.11.

Note

This is one of those areas where disputes can often be nipped in the bud by providing incentives that encourage parties to take reasonable positions, as discussed in the commentary to Protocol 21.11..

23.4.1.4. The Reporter doesn't take action independently.

The Reporter doesn't undertake any Policing Efforts of its own without the Owner's prior written approval.

Note

It could be, ahem, awkward for the Reporter to try to undertake Policing Efforts on its own; the Owner will want to maintain control of the situation.

23.5. IP Infringement Warranty Protocol

23.5.1. Lighthouse Protocol

23.5.1.1. The parties: The Vendor and the Customer.
  1. This Protocol will govern when:
    • one party to the Con­tract (a "Vendor")
    • clearly represents and/or warrants to another party to the Con­tract — for convenience, each such party is referred to here as a "Customer" —
    • that one or more specified products and/or services — each, a "Covered Item," defined in § 23.5.1.2 below —
    • does not infringe intellectual property rights of a third party.
  2. Any such representation and/or warranty is referred to as an "Infringement Warranty," and is defined further in this Protocol.
  3. If this Protocol is listed in the Con­tract, it means that:
    1. the parties expect a clearly-indicated party to be a Vendor; and
    2. that party (i.e., the Vendor) is making the Infringement Warranty to another clearly-indicated party as a Customer.
Note

This Protocol is offered as a shortcut for drafters, as an alternative to the long, dense infringement-warranty terms that can be so painful to review and negotiate.

See also the general discussion of representations and warranties — and the differences between them — at 16.2.

23.5.1.2. An Infringement Warranty starts upon delivery.

An Infringement Warranty applies only to the "Covered Products" and/or "Covered Services" (each, a "Covered Item"), namely one or more products and/or services —

  1. as delivered to the Customer under the Con­tract, by the Vendor or with the Vendor's authorization (e.g., via a Vendor-authorized reseller); or
  2. as otherwise clearly agreed in writing by the Vendor.
Note

().  The warranty of this Protocol extends to Covered Items as delivered, as opposed to warranting the items' future performance; see the discussion of this topic at 31.40.8.

Drafters might want to consider whether an Infringement Warranty should apply:

  • solely to goods and/or services provided directly or indirectly by the Vendor itself, e.g., goods manufactured by the Vendor and sold via a distribution channel; or
  • also to goods and services manufactured and/or distributed by others.
23.5.1.3. Only the Customer is protected by an Infringement Warranty.

For emphasis: Unless the Con­tract clearly says otherwise, an Infringement Warranty benefits only the Customer and not any third party — and for this purpose, the term "third party" includes (without limitation) any affiliate of the Customer.

Note

This exclusion is intended to help avoid possible collusion between the Customer and its affiliates. (See also 11.8 (third-party beneficiaries).

23.5.1.4. An Infringement Warranty covers copyrights, trade secrets, and patents.

An "Infringement Warranty" consists solely of the following — each as limited by the terms of this Protocol — unless clearly agreed otherwise in writing:

  1. a Copyright Warranty, defined at 23.5.1.5; and
  2. a Trade Secret Warranty, also defined at 23.5.1.5; and
  3. a Patent Warranty, defined in 23.5.1.6.
Note

Separating (and naming) the components of an Infringement Warranty allows drafters to refer to them individually if desired.

23.5.1.5. Definition: Copyright Warranty; Trade Secret Warranty
  1. A Copyright Warranty or Trade Secret Warranty is a warranty that the making of the Covered Item didn't involve the following:
    1. For a Copyright Warranty: Infringement of a third party's copyright.
    2. For a Trade Secret Warranty: Misappropriation of a third party's trade secret.
  2. For emphasis: Subdivision 1 refers to copyrights and trade secrets under the laws of any jurisdiction anywhere in the world.
Note

The Copyright- and Trade-Secret Warranties each has a broader scope than the Patent Warranty (23.5.1.6). Why is that? In a nutshell:

  1. To infringe someone's copyright, the Vendor would have to copy "protected expression" that's contained in the copyrighted work, which implies direct- or indirect access to the work.
  2. Likewise, to misappropriate someone's trade secret, the Vendor would have to have had direct- or indirect access to the trade secret, under conditions indicating that the Vendor had a duty, by agreement or otherwise, to preserve the trade secret in confidence.
23.5.1.6. Definition: Patent Warranty
  1. A Patent Warranty is a warranty that, so far as the Vendor is aware — but see subdivision 3 below — the Covered Item doesn't infringe any "Patent Right," namely any valid and enforceable claim of a utility patent or design patent that is owned or otherwise assertable by a third party anywhere in the world.
  2. In addition, if the Vendor unambiguously provides the Customer (perhaps indirectly, e.g., via a reseller) with instructions for using a Covered Item (for example, in a user manual), THEN: The Patent Warranty also applies, as stated in subdivision 1, to the use of the Covered Item, by the Customer and/or by other any users unambiguously specified in the Con­tract, in accordance with those instructions.
  3. But: The Vendor doesn't represent or warrant that the Vendor has conducted any particular search or other investigation about any Patent Warranty unless the Vendor clearly states otherwise in writing.
Note

().  The Patent Warranty is narrower than the Copyright- and Trade-Secret Warranties because a Covered Item could infringe an issued patent — or a future patent — without the Vendor's even knowing that the patent exists. This means that the Vendor can more readily warrant against claims of infringement of third-party copyrights or misappropriation trade secrets than it can against infringement of patents; hence, different scopes for the two warranties.

Subdivision 1: For a discussion of the differences between a utility patent and a design patent, see generally the U.S. Patent and Trademark Office's discussion of "Types of patent." Cf. also the World Industrial Property Organization's discussion of "Utility models."

Subdivision 2 addresses the possibility that the Customer could infringe a patent claim by using a Covered Item. That's because (U.S.) patent law makes it an infringement to make, use, or sell something that comes within the scope of an issued claim (among other infringements) without the permission of the patent owner. See 35 U.S.C. § 271(a), as well as the discussion of patent infringement at 23.1. ] For example, in the case of Monsanto's post-emergence herbicide Roundup®, the claims of Monsanto's initial patent were directed to "A herbicidal method which comprises contacting a plant with a herbicidally effective amount of a compound of the formula …."; that was because the compound itself, N-(phosphonomethyl)glycine ("glyphosate"), was in the prior art. (Later Monsanto patents were addressed to improvements in the chemistry.)

Subdivision 3: For its own risk-assessment purposes, the Vendor might want to consider commissioning its own "freedom to operate" patent investigation and an opinion of counsel, to provide the Vendor with at least some comfort on in this regard — because a Covered Item might infringe a patent without the Vendor (or anyone in the industry) even knowing that the patent exists. Such investigations and legal opinions can be costly, but if there's a lot at stake, that cost might be worthwhile. For additional discussion, see generally, e.g.: • Linda J. Thayer, When Is a "Freedom to Operate" Opinion Cost-Effective?, Today's General Counsel (2013), archived at https://perma.cc/R7BB-9VVT (the author is a partner in the Finnegan Henderson firm, one of the leading intellectual-property law firms in the United States); • World Intellectual Property Organization, IP and Business: Launching a New Product: freedom to operate (wipo.int 2005).

23.5.1.7. An Infringement Warranty doesn't apply to Customer-provided specifications.
  1. This section applies to any claim of infringement where both of the following are true:
    1. the claimed infringement arises from a Covered Item's compliance with a written- or oral specification; and
    2. the Customer provided that specification to the Vendor (or one or more third parties did so on the Customer's behalf).
  2. The Vendor's Infringement Warranty doesn't extend to any claim of infringement of the kind described in subdivision 1.
  3. If the Customer asserts that a Covered Item complied with an oral Customer specification, that assertion won't be effective unless the Customer supports it with clear and convincing evidence.
Note

This section mirrors the general law in the U.S. in the Uniform Commercial Code § 2-312(3), which provides as follows:

Unless otherwise agreed a seller who is a merchant [see 13.5] regularly dealing in goods of the kind warrants that the goods shall be delivered free of the rightful claim of any third person by way of infringement or the like but a buyer who furnishes specifications to the seller must hold the seller harmless against any such claim which arises out of compliance with the specifications."

(Emphasis added.)

23.5.1.8. An Infringement Warranty might not cover "combination" infringements.

An Infringement Warranty doesn't extend to any claim of infringement where both of the following are true:

  1. the claim is that the infringement lies in a combination of (i) a Covered Item, with (ii) one or more other products (tangible or intangible) and/or services; and
  2. there's no claim of infringement concerning: (a) the Covered Item itself, nor (b) the use of the Covered Item apart from the combination.
Note

Caution: The warranty disclaimer of this section might not be enough to save the Vendor from liability to a patent owner for "contributory infringement," which can be expensive and time-consuming to litigate. See generally 35 U.S.C. § 271(c) and Contributory infringement (Law.Cornell.edu).

23.5.1.9. Three types of "stop use" events could trigger the Vendor's remedy obligations.

Scenario: The Vendor complies with the remedy provisions in § 23.5.1.10 below if one or more of the following "Triggering Events" occurs:

  1. A court of competent jurisdiction enjoins the Customer from using a Covered Product as a result of a "Covered Infringement Claim" — namely, an infringement claim covered by an Infringement Warranty — and for any reason the Vendor doesn't have the injunction stayed or overturned; and/or
  2. The Vendor gives notice to the Customer that the Vendor has settled a Covered Infringement Claim on terms that call for the Customer to stop using a Covered Product; and/or
  3. The Vendor gives notice to the Customer that the Vendor determined (in your reasonable judgment) that the Customer should stop using a Covered Product because of a Covered Infringement Claim.
Note

These three items are basic "stop use" events that might occur in an IP infringement case.

23.5.1.10. The Vendor's remedy obligations are Plans A through C.
  1. Scenario: If a Triggering Event occurs in respect of a Covered Product, THEN: The Vendor proceeds in accordance with one or more of Plans A through C below.

    Plan A – modification or replacement: The Vendor tries to modify or replace the Covered Product with a non-infringing substitute that, in all respects material to the Con­tract, performs the same functions as the replaced deliverable.

    Plan B – license: The Vendor tries to procure for the Customer — at the Vendor's expense — a license to continue using the Covered Product under the IP right that's the basis for the infringement claim.

    Plan C – refund: If the Vendor is unable to follow Plan A or Plan B, or the Vendor judges that neither Plan A nor Plan B is commercially feasible, THEN: The Vendor —

    (i) advises the Customer to stop using the deliverable; and

    (ii) give the Customer a refund in an amount computed as specified at § 23.5.1.11 below.

  2. The Vendor gets to choose — in the Vendor's sole discretion — which of the above Plan or Plans to follow, and their sequence, as long as the Vendor follows at least one of those Plans.
Note

Plans A through C seem to be generally accepted as a sensible protocol for suppliers to follow in case of a Triggering Event.

23.5.1.11. The Customer refund would be computed as stated here.
  1. If the Vendor proceeds under Plan C above, THEN: The Vendor issues the Customer a refundable credit as stated in this section.
  2. The amount of the refund is:
    • the amount paid by the Customer (directly or indirectly) for the Covered Product and/or its use, as applicable,
    • reduced pro rata to reflect amortization on a straight-line monthly basis of that paid amount over the time period stated in subdivision 3 or subdivision 5 below as applicable.
  3. If the refund is for a permanent right to use a Covered Item — for example, a deliverable sold outright, or a fee for a paid-up perpetual use license — THEN: The amortization period is 36 months (based on the 36-month IRS depreciation period for computer-software licenses). Hypothetical example: Suppose that:

    1. the Customer paid a one-time fee of $400 for the permanent right to use the Covered Product; and
    2. you proceed under Plan C at the end of Month 9, i.e., ¼ of the way through the (36-month) amortization period.

    In that situation, the refund will be $300, i.e., ¾ of the $400 paid by the Customer.

  4. If the refund is for a temporary period of entitlement relating to a Covered Item — for example, a limited-time license, or a software maintenance subscription period — THEN: The amortization period will be the entire duration of that temporary period of entitlement. Hypothetical example: Suppose that:

    1. the Customer paid a one-time fee of $100 for the right to use a Covered Product for one year; and
    2. the Vendor proceeds under Plan C at the end of Month 9, i.e., ¾ of the way through the one-year period.

    In that situation, the refund is $25, i.e., ¼ of the $100 paid by the Customer.

23.5.1.12. The Vendor isn't responsible for Customer post-refund use.
  1. Scenario: This section applies if the Vendor proceeds under Plan C (refund) at section 23.5.1.10 above.
  2. The Vendor won't be responsible for any infringing use of a Covered Item, by you or any other user authorized by the Con­tract — this will start after a short-but-reasonable time for you to conduct (or direct) a prompt, orderly transition away from the use in question ("post-transition infringing use").
  3. You must defend and indemnify the Vendor and the Vendor's Protected Group against any claim of infringement arising from any such post-transition infringing use of the Covered Item.
Note

This section represents a sensible compromise: If the Vendor gives the Customer a refund for a deliverable that's accused of infringement, then the Vendor shouldn't be expected to be responsible for any subsequent, potentially-infringing use of the deliverable.

23.5.1.13. These are the EXCLUSIVE WARRANTIES and REMEDIES concerning infringement.
  1. An Infringement Warranty states the EXCLUSIVE TERMS of any and all Vendor warranties concerning infringement of third-party rights by one or more Covered Items — for emphasis, all other warranties, representations, conditions, and terms of quality relating to infringement and any Covered Item are:
    1. DISCLAIMED by the Vendor; and
    2. WAIVED by each party that might make a claim against the Vendor.
  2. The remedies stated in this Protocol are the Customer's EXCLUSIVE REMEDIES to which the Customer is entitled — from the Vendor or any person affiliated with the Vendor:
    1. for any breach of an Infringement Warranty; and/or
    2. for any other alleged- or actual infringement of third-party intellectual property rights by, or attributable to, the Vendor.
Note

See also the discussion of implied-warranty disclaimers at 16.1.

23.5.1.14. Option: No Inconsistent Third-Party Assertions
  1. If this Option is agreed to in the Con­tract, it applies to each Copyright-, Trade Secret, and/or Patent Warranty provided by the Vendor (if any).
  2. The Vendor represents — solely to the Customer — that, so far as the Vendor is aware, no party has asserted that any Covered Item fails to comply with any part of the Infringement Warranty.
Note

This Option might provide a Customer with modest additional assurance about the infringement issue. That would be especially true if the Covered Item has been on the market for awhile: If a third-party infringement claim was out there somewhere, chances are that the claim would have surfaced already.

23.6. IP Ownership

23.6.1. Lighthouse Protocol

23.6.1.1. Scenario: IP is created
  1. This Protocol describes the parties' rights and obligations when —
    1. one or more parties indicated in the Con­tract is involved in creating new subject matter under the Con­tract; and
    2. the new subject matter could include "IP," as defined in Protocol 23.3, which is incorporated by reference.
  2. The Adoption of LCP26 Provisions Protocol (10.1) is incorporated by reference into this Protocol
Note

().  This Protocol sets out pretty-standard procedures for dealing with ownership of intellectual property, with:

1.  baseline default rules about who owns what (unless the Con­tract says otherwise); and

2.  procedures for confirmation and/or transfers of ownership.

Caution: A party assigning IP rights might not want to give up trademark rights, as discussed at 23.6.2.9.

For extensive additional background information about the legal rules governing IP ownership, see 23.6.2.1 (patents); 23.6.2.2 (copyrights); and 23.6.2 (other additional notes).

23.6.1.2. Ownership of pre-existing IP doesn't change.

Unless the Con­tract clearly says otherwise: The Con­tract doesn't transfer ownership, nor does it entitle any party to demand that another party transfer ownership, of any pre-existing IP.

Note

().  Note that under U.S. law, transfers of IP ownership generally must be in signed writings. See 17 U.S.C. § 261 (transfers of patent ownership) and 17 U.S.C. § 201(d) (transfers of copyright ownership).

Even if ownership of IP is not transferred, a court might find that a contract granted an implied license to pre-existing IP and even newly-created IP; see the discussion at 23.6.2.12.

23.6.1.3. Newly-created IP (if any) is owned by its creators.

As between the parties, unless clearly agreed otherwise:

  1. each party owns whatever IP that it creates on its own under the Con­tract (if any);
  2. the parties jointly own — in equal, undivided interests — any IP that they jointly create under the Con­tract (see also below concerning joint works); and
  3. as between the parties, IP created by any party under the Con­tract is not a "work made for hire."
Note

().  Concerning the language, "as between the parties," see 32.4. Here, that language recognizes that other factors — such as preexisting contracts — might affect ownership of newly-created IP.

Subdivision 1 could be overriden with language such as: "[Party name] will own any and all intellectual property that is newly created in the performance of the Con­tract by either party." QUESTION: Should Toolkit Items (23.6.1.4) be excluded from such an override?

Subdivision 2: Joint creation of intellectual property can occur, for example, in services-type contracts and in collaboration agreements of various kinds, e.g., R&D joint-venture agreements. Who is to own jointly created IP will sometimes be a negotiation point. For additional discussion, see the commentary at § 23.6.1.5.

Caution: See the commentary at § 23.6.1.9 for the tale of how Stanford University was surprised to find that it shared joint ownership of an HIV-related patent with a biotechnology company, Roche Molecular Systems, because a Stanford researcher had signed a "visitor NDA" at Roche's predecessor; that NDA gave Roche ownership of whatever the researcher came up with "as a consequence" of his access to Roche.

Caution: Claims of joint creation of IP can be fact-intensive and thus costly to litigate — as illustrated by the Stanford v. Roche case and Omni MedSci cases discussed the commentary at § 23.6.1.9, and also by BASF Plant Science (Fed. Cir. 2022), where the appeals court reversed a trial-court judgment, following a jury verdict, that the defendant co-owned a particular patent and thus wasn't liable for infringing the patent in suit; the appeals court held that BASF had asserted "an unreasonable view" of what level of contribution by BASF would qualify the company as a joint owner. See BASF Plant Science, LP v. Commonwealth Scientific & Indus. Research Org., 28 F.4th 1247, 1269-71 (Fed. Cir. 2022).

Subdivision 3 is pretty much what the law would say in any case. (This is potentially-significant because a "work made for hire" under copyright law is owned upon creation by the employer, not by the individual, as discussed in more detail at 23.6.2.3 and 23.6.2.4.)

Even if ownership of newly-created IP is not transferred, a court might find that a contract granted an implied license to the newly-created IP, as discussed at 23.6.2.12.

23.6.1.4. Ownership of newly-created "Toolkit Items" doesn't change.

Even if other IP is transferred under the Con­tract, ownership of "Toolkit Items" won't change, even if created under the Con­tract; the quoted term refers to any concept, idea, invention, strategy, procedure, architecture, or other work (each, an "Item"), when —

  1. the Item is, in whole or in part, created by a party in the course of performing under the Con­tract;
  2. (if the creating party is a provider performing services for a customer:) the Item isn't specific, and/or isn't unique, to the customer and its business; and
  3. the item doesn't encompass Confidential Information, as defined in Protocol 5.3, of another party.
Note

"Toolkit Items" are treated specially here because sometimes a customer will take the (overreaching) view, "if we paid for it, we own it, even if we have no real use for it — which makes little sense economically, as discussed at 23.6.2.11.

23.6.1.5. For jointly-owned IP, each party has both use‑ and license rights.

The stated party or parties are free to authorize others to use jointly-created IP, in any manner that would be allowed to the authorizing party itself under the Con­tract, including without limitation:

  1. use of the IP for the authorizing party's benefit; and
  2. use of the IP for the user's own benefit as a licensee of the authorizing party.
Note

().  See the discussion in the comments to § 23.6.1.6.

Subdivision 1 is an example of what's sometimes referred to generically as "have-made rights." Example: In Great Minds (2d Cir. 2018) (which wasn't a joint-ownership case), schools paid FedEx Office to make copies of materials that were licensed under a Creative Commons license that prohibited "commercial use." The court held that the copying by FedEx still qualified as noncommercial, even though FedEx had charged the schools for making the copies: "[U]nder long-established principles of agency law, a licensee under a non-exclusive copyright license may use third-party assistance in exercising its license rights unless the license expressly provides otherwise." Great Minds v. FedEx Office & Print Servs., Inc., 886 F.3d 91, 94 (2d Cir. 2018).

23.6.1.6. Joint owners need not share proceeds from their use or licensing.

If A makes use of (and/or licenses) IP that A jointly created with B, THEN: A doesn't have to share profits with B, nor otherwise account to B, for A's use and/or licensing.

Note

().  Under U.S. law, on the patent side: Unless otherwise agreed in writing, each co-inventor of joint invention may use and/or license the invention with no obligation to account to — i.e., share proceeds with, or pay a royalty to — any other co-inventor. See 35 U.S.C. § 262.

On the other hand, on the copyright side: While the co-owners of a joint work may make use of the work as they see fit, they must account to one another from their uses of the work unless they agree otherwise in writing.

Example: As an illustration of this principle of copyright law, the hit song Let the Good Times Roll was putatively authored by one Leonard Lee; he and his heirs were paid more than $1 million in royalties during the relevant time period. But Lee's childhood friend Shirley Goodman won a lawsuit in which she alleged that she was the co-author of the song — and the court awarded her one-half of those royalties. See Goodman v. Lee, 78 F.3d 1007 (5th Cir. 1996).

Example: Another copyright case involved the 1967 hit song A Whiter Shade of Pale by the British rock group Procol Harum: In 2009, the group's organist, Matthew Fisher, prevailed in the House of Lords (now the UK Supreme Court) on his claim that he should have been listed as a co-author of the song as released, because the Bach-like vamp that he played on the organ during the recording session — instantly recognizable to those of us "of a certain age" — was an addition to the original composition.

–  The Lords agreed that Fisher had waited too long (38 years) to claim his share of past royalties.

–  But the Lords affirmed a judgment below that Fisher was entitled to a 40% share of ownership in the musical copyright in the song, and thus presumably to that share of future royalties. See Fisher v. Brooker, [2009] UKHL 41. Click https://www.youtube.com/watch?v=Mb3iPP-tHdA to hear the song and the organ vamp ]

23.6.1.7. Non-transferrable moral rights, etc., have a no-cost license.

If, by law, any moral rights or other intellectual property rights in the specified IP cannot be assigned, THEN: Effective immediately when the parties enter into the Con­tract, the party possessing such non-assignable right(s) grants to the Owner a perpetual, irrevocable, worldwide, royalty-free, fully transferable license, under all such non-assignable rights.

Note

This moral-rights provision is an anchor-to-windward provision — but it might not always be effective; see generally the Wikipedia entry on moral rights.

23.6.1.8. Each party maintains suitable agreements with employees, etc.
  1. Each party other than the Owner ensures that its relevant employees, and its subcontractors (if any), have signed appropriate written agreements sufficient to enable that other party to comply with any obligations that the other party has under this Protocol.
  2. Where applicable, such agreements are also "notarized" (acknowledged) by the signer(s).
  3. For the avoidance of doubt: subdivision 1 in itself doesn't authorize (nor does it prohibit) the use of subcontractors by any party.
Note

().  A customer might not need for a supplier's employees to be bound by written agreements to cause the employee's work product to be owned by the customer (at least under U.S. law). DCT note: See generally this annotated flowchart that I did some years ago.

In contrast, a subcontractor of a contractor likely would indeed need to sign an IP-ownership agreement in order to transfer ownership to the contractor's customer.

What if, for some reason, the parties never took care of this bit of paperwork? An implied license from the subcontractor to the Owner might still "save the day," as discussed at 23.6.2.12 — but the associated litigation would likely be an expensive headache for all concerned.

Concerning "notarization," see 29.7.

Caution: In most of the United States, courts will generally enforce agreements between companies and their employees, requiring the employees to assign inventions that are created during the period of employment. See, e.g., Apprio, Inc. v. Zaccari, No. 22-7057, slip op. (D.C. Cir. Jun. 21, 2024) (affirming summary judgment that employer owned IP rights in code developed by an employee during employment, where the code made use of Microsoft Excel macros that the employee had developed before employment). ] BUT:

23.6.1.9. Any future IP rights in question are transferred upon signing the Con­tract.
  1. Scenario: This section applies if, under the Con­tract:
    1. an individual or organization (the "Owner") is to be the owner of specified intellectual property that will be or might be created in the future, but
    2. by law, the specified IP is or might be owned by another individual or organization (referred to here as "ABC"), as opposed to being automatically owned by the Owner upon creation.
  2. By entering into the Con­tract, ABC assigns to the Owner — effective immediately upon ABC's entry into the Con­tract — all right, title, and interest in all such specified, future-created IP.
  3. If, by law, any such right, title, and/or interest can't be assigned now for future IP creations as in subdivision 2 above, THEN at the Owner's request at any time, ABC promptly assigns to the Owner all such right, title, and interest in the specified IP (see also 23.6.1.10 concerning written documentation of the assignment).
Note

The issue addressed in this section has been crucial in several important patent cases. Example: In 2009, Stanford University found itself being only a joint owner, not the sole owner, of a patent relating to the treatment of HIV / AIDS significant biotech invention by a team of its researchers:

  • A Stanford researcher spent some time at a company, Cetus, later acquired by Roche, to obtain technical training.
  • The Stanford researcher signed a "visitor NDA" with Cetus.
  • The visitor NDA contained "hereby assigns" language, under which the researcher made apresentassignment of any rights in future inventions that he helped to invent "as a consequence" of his visit to Cetus;
  • In contrast, the researcher's already-existing agreement with Stanford stated that the researcher would assign his rights in future inventions.

The Federal Circuit held that the Cetus agreement's "hereby assigns" language took precedence over the Stanford agreement's future-assignment provision — even though Stanford and the researcher had entered into the latter agreement before the researcher entered into the Cetus agreement. That, shall we say, complicated life for Stanford in regard to that particular patent. See Bd. of Trs. of the Leland Stanford Junior Univ. v. Roche Molecular Sys., Inc., 583 F.3d 832 (Fed. Cir. 2009), aff'd as to a tangential issue, 563 U.S. 776, 131 S. Ct. 2188, 2194-95 (2011).

Relatedly: A co-inventor's employment agreement required her to assign patent rights in the future, but she never did so for the patent in suit — and her "will assign" agreement was not enough to give her employer the required standing to sue for infringement of the patent. See Advanced Video Tech. LLC v. HTC Corp., 879 F.3d 1314 (Fed. Cir. 2018) (affirming dismissal for lack of standing).

In the same vein but with a different result: A federal appeals court held that the University of Michigan's bylaws did not constitute a "present assignment" of the professor's future invention rights, and so the professor's company (started while he was on unpaid leave) owned the patent and could sue Apple for patent infringement. See Omni MedSci, Inc. v. Apple Inc., 7 F.4th 1148, 1151-52 (Fed. Cir. 2021) (affirming refusal to dismiss patent-infringement suit against Apple for lack of standing on the part of Omni MedSci).

Also relatedly: An administrative judge initially found that the media-device company Roku didn't own an interest in a patent because a co-inventor of the patent, employed by the company, had only promised to assign his patent rights to the company. The International Trade Commission reversed, finding that a different document, signed by the employee, did constitute a present assignment of "expectant rights." Roku, Inc. v. Int'l Trade Comm'n, 90 F.4th 1367, 1373 (Fed. Cir. 2024) (affirming Commission finding).

23.6.1.10. Each party provides other written IP transfer documents upon request.
  1. Scenario: This section applies whenever A is required to "assign" intellectual property in or under the Con­tract to B.
  2. Action: If B asks, A permanently and irrevocably transfers all ownership of the IP, in writing, to B and B's successors and assigns.
Note

This is an "upon request" obligation, on the principle that B is more likely to be paying attention — and it shouldn't be deemed a breach of contract for A not to remember to provide a written assignment without a request.

23.6.1.11. Each party provides other confirming documents if asked.

If A makes a reasonable request from time to time, THEN: B causes appropriate additional documents to be signed and delivered to A to establish, and/or confirm, A's rights in specified IP as stated in this Protocol.

Note

Such documents could include, without limitation: patent applications; copyright- or trademark registration applications; and assignment documents.

23.6.1.12. Confirming documents are written broadly.

Any written transfer- or confirmation of ownership under § 23.6.1.11 above is drafted (and deemed) to encompass, as applicable to the type of IP in question:

  1. any and all patent applications for any portion of the specified IP, no matter when filed — this includes, without limitation, all original, continuation, continuation-in-part, divisional, reissue, foreign-counterpart, or other patent applications;
  2. any and all patents issuing on each patent application described in subdivision 1;
  3. the right to claim priority in, to, or from (i) each patent application described in subdivision 1, and (ii) each patent described in subdivision 2;
  4. any and all registrations for the copyright or trademark rights (if any) in the specified IP;
  5. any and all applications to register the copyright or trademark rights (if any) in the specified IP;
  6. any other intellectual property rights, of whatever nature, in the specified IP, together with any applications for, or issued registrations for, the same; and
  7. the right to recover, and to bring proceedings to recover, damages and any other monetary awards, and/or to obtain other remedies, in respect of infringement or misappropriation of any item listed in any of subdivisions 1 through 6 above, whether the infringement or misappropriation was committed before or after the date of the transfer of ownership.
Note

Subdivision 7: Under U.S. law, the right to sue for past infringement must be specifically transferred in writing; it's not enough to assign the patent without specifically mentioning the right to sue. See Arachnid, Inc. v. Merit Indus., Inc., 939 F.2d 1574, 1579 n.7 (Fed. Cir. 1991) (reversing judgment below: plaintiff did not have the right to sue defendant for infringement occuring before patent owner had acquired "legal" title to the patent, as opposed to "equitable" title).

23.6.1.13. New owners pay any ownership-transfer expenses.

As between the former owner and the new owner, the new owner pays for preparing and filing any such documents unless otherwise agreed in writing.

Note

This is standard practice; see also 4.7 (expense reimbursement).

23.6.1.14. No additional compensation for ownership transfers.

For the avoidance of doubt: No party gets any additional compensation for doing the things required by this Protocol, over and above any compensation clearly stated in the Con­tract.

Note

This is intended as a guardrail.

23.6.1.15. Option: Co-Owner Participation in Infringement Lawsuits

If the Con­tract includes this Option, THEN: Upon request, all other co-owners of IP join in any one co-owner's actions against infringers of the associated IP rights.

Note

().  For patents, as a general rule, a co-owner of a U.S. patent cannot sue for infringement unless the other co-owner(s) also join the lawsuit as co-plaintiffs. See STC.UNM v. Intel Corp., 754 F.3d 940 (Fed. Cir. 2014) (affirming dismissal, for lack of standing, of patent-infringement lawsuit by one of two co-owners of patent), citing Ethicon, Inc. v. United States Surgical Corp., 135 F.3d 1456 (Fed. Cir. 1998).

For copyrights, the rule is different: Any co-owner can file an infringement suit, and the court has the power to compel joinder of other co-owners. See 17 U.S.C. § 501(b); see generally John M. Neclerio and Urmika Devi, Joint Ownership of Patents, Copyrights and Trade Secrets in the United States (DuaneMorris.com 2011).

23.6.1.16. Survival of IP-ownership provisions

All rights and obligations of this Protocol survive any termination or expiration of the Con­tract for IP created before termination or expiration.

Note

See also 18.1 (survival).

23.6.2. Additional notes

23.6.2.1. Background: Patent ownership

In the United States, the general rules about patent ownership can be summarized as follows:

–  Inventors initially own the legal rights (if any) to their inventions. See generally 35 U.S.C. § 111(a)(1) (inventor may apply for patent), § 118 (application may be filed by person to whom inventor has assigned, or is obligated to assign, the invention).

–  Joint inventors ("co-inventors") of an invention jointly own the invention. See 35 U.S.C. § 262; see also the notes to the joint-ownership provisions, beginning at 23.6.1.5.

–  Transfers of patent ownership (or exclusive licenses) generally must be in writing. See 35 U.S.C. § 261.

–  An employee who was "hired to invent" or "set to experimenting" will usually be considered to have an implied obligation to assign the invention rights to the employer. See, e.g., Teets v. Chromalloy Gas Turbine Corp., 83 F.3d 403, 408-09 (Fed. Cir. 1996); Miller v. GTE Corp., 788 F. Supp. 312 (S.D. Tex. 1991). (Disclosure: In Miller, the present author represented GTE, which later became Verizon).

But in a Nebraska federal case, a company was found not to have set its former employees to experimenting, and therefore the company didn't own the rights in anew product that the former employees developed at a startup company that they founded. See Farmers Edge Inc., v. Farmobile LLC, 970 F.3d 1027, 1032 (8th Cir. 2020) (affirming summary judgment in favor of defendant); REXA,Inc. v. Chester, No. 20-2953 slip op. at 24 (7th Cir. Jul. 28, 2022) (former employee had not been specifically directed to develop an actuator; affirming summary judgment in favor of former employee). / ]

23.6.2.2. Background: Copyright ownership

In the United States, the general rules about copyright ownership can be summarized as follows:

–  The "author" of a copyrighted work initially owns the copyright; joint authors likewise co-own their jointly created work. See 17 U.S.C. § 201(a).

–  For copyright purposes, an employer is considered the "author" of a copyrighted work if the work is a "work made for hire." See 17 U.S.C. § 201(b) and the detailed discussion beginning at 23.6.2.3.

–  Transfers of copyright ownership (including transfers of the individual exclusive rights that, together, comprise a copyright) must be in writing. See 17 U.S.C. § 201(d).

–  But a simple writing for ownership transfer will suffice — as the Ninth Circuit noted: "It doesn't have to be the Magna Charta; a one-line pro forma statement will do." Effects Assoc., Inc. v. Cohen, 908 F.2d 555, 557 (9th Cir. 1990) (affirming summary judgment).

23.6.2.3. Work-made-for-hire status for employees?

If a copyrighted work is created by an employee who is working within the "scope of employment," then the employer is considered the "author," and thus the (initial) owner, of the work. See 17 U.S.C. § 101 (definition of "work made for hire").

In a unanimous opinion in Community for Creative Non-Violence v. Reid, Justice Marshall set out a "nonexhaustive" list of traditional factors that are to be considered, under the general common law of agency, in determining whether an individual author is or isn't working within the scope of employment; the list focuses on the extent to which the putative employer has the right to control the means and manner by which the author creates the work; "[n]o one of these factors is determinative." Community for Creative Non-Violence v. Reid 490 U.S. 730, 751-52 (1989) citing Restatement of Agency § 220(2).

23.6.2.4. When can a contractor's work be a "work made for hire"?

A different situation arises when a party engages a nonemployee to create a copyrightable work: The hiring party can be considered the "author" of the work, but only if both of the following things are true:

A.  the work must be "specially ordered or commissioned" for use in one of the following nine statutory categories:

1.  a contribution to a collective work,
2.  a part of a motion picture or other audiovisual work,
3.  a translation,
4.  a supplementary work (see below),
5.  a compilation,
6.  an instructional text (see below),
7.  a test,
8.  answer material for a test, or
9.  an atlas;

AND:

B.  the actual author(s) and the commissioning party must agree, in a written agreement — which should be signed before the work is created, as discussed below — that the work will be a work made for hire. See 17 U.S.C. § 101 (definition of "work made for hire").

The Supreme Court has said that these statutory categories represent a conscious compromise by Congress as to when the rights of non-employee authors can be permanently appropriated in advance by hiring parties, and so: "Strict adherence to the language and structure of the Act is particularly appropriate where, as here, a statute is the result of a series of carefully crafted compromises." Community for Creative Non-Violence v. Reid, 490 U.S. 730, 749 n.14 (1989).

(Note that rights assigned to a hiring party, as opposed to rights owned from the outset by virtue of hiring party’s “authorship,” can be reclaimed by author or heirs 35 years after assignment, as discussed at 23.6.2.7.)

Section 101 of the statute further provides that:

  • a “supplementary work,” as used in the above laundry list, is a work prepared for publication as a secondary adjunct to a work by another author for the purpose of introducing, concluding, illustrating, explaining, revising, commenting upon, or assisting in the use of the other work, such as forewords, afterwords, pictorial illustrations, maps, charts, tables, editorial notes, musical arrangements, answer material for tests, bibliographies, appendixes, and indexes; and
  • an “instructional text” is a literary, pictorial, or graphic work prepared for publication and with the purpose of use in systematic instructional activities.
23.6.2.5. Work-made-for-hire agreements can be a good idea

It's clear from the above discussion that:

–  If a copyrightable work is created by an employee working within the scope of his or her employment, then a work-made-for-hire agreement won't be needed — but it's still a very good idea, to help educate all concerned and as a just-in-case provision, especially if "recapture" might someday be a possibility (discussed at 23.6.2.7).

–  For non-employee works, a work-made-for-hire agreement is "a must" under U.S. law if the hiring party wants the work to qualify as a work-made-for-hire. (And if the work doesn't fit into one of the statutory categories listed above, then the work won't be a work made for hire, no matter what the parties' agreement might say.)

–  In case a work doesn't qualify as a work made for hire, language such as that of 23.6.1.9 (present assignment of future rights) can serve as a backstop provision.

23.6.2.6. When must a work-for-hire agreement be signed?

The Copyright Act doesn't say whether a work-made-for-hire agreement must be signed before the work is created, or whether it can be signed afterwards to confirm a prior agreement; the courts are split on that subject, as summarized in 2019 by the influential Second Circuit in Estate of Kauffmann. Estate of Kauffmann v. Rochester Inst. of Tech., 932 F.3d 74, 77 (2d Cir. 2019) (reversing district court judgment; movie reviews were not works made for hire).

23.6.2.7. Work-for-hire status and copyright-recapture rights

Work-for-hire status makes a difference in the long term: In the U.S., if an author transfers or licenses a copyright and the work is not a work made for hire, then (years later) the author or his or her heirs will have a window of time in which they can terminate the transfer or license and, in essence, "recapture" the author's ownership of the U.S. copyright. See 17 U.S.C. § 201(b) (ownership of work made for hire); 17 U.S.C. § 203 (termination of copyright transfers and licenses); see also the Copyright Office explanation as well as Margo E. Crespin, A Second Bite of the Apple: A Guide to Terminating Transfers Under Section 203 of the Copyright Act (AuthorsGuild.org, undated).

This issue has come up for some famous songwriters, e.g., Paul McCartney, who sought to revoke his transfer of his U.S. song copyrights; his lawsuit reportedly was settled. See, e.g., Stan Soocher and Scott Graham, Paul McCartney's Suit over Songs' Recapture Rights (LawJournalsNewsletters.com 2017); Ashley Cullins, Paul McCartney Reaches Settlement With Sony/ATV in Beatles Rights Dispute (HollywoodReporter.com 2017). For other examples of well-known copyrights being recaptured, see Stephen K. Rush, A Map Through the Maze of Copyright Termination: Authors or Their Heirs can Recapture Their Valuable Copyrights (NVLawLLP.com, undated).

Some publishers and studios reportedly demand that when an author signs a deal, the author must agree that, following a termination years later, the company will have a right of first negotiation and/or a right of last refusal. The statute, however, provides that "a further grant, or agreement to make a further grant, of any right covered by a terminated grant is valid only if it is made after the effective date of the termination" or after the notice of termination has been sent; it's unclear whether a pre-termination right of first negotiation or last refusal would qualify. [DCT TO DO: Right of First Refusal, First Negotiation] See 17 U.S.C. § 203(b)(4).

23.6.2.8. So: Include "work made for hire" language in creator contracts?

As in so many areas of law and business, the answer to the question, should the contract include work-made-for-hire language?, is a firm, definitive "it depends." (That's a joke.)

In some situations where intellectual property is to be (or might be) created, the hiring party might want the contract to state that the IP will be a "work made for hire," in part so that the human author won't have the right to recapture the ownership after 35 years have elapsed (as Paul McCartney did), as discussed at 23.6.2.7.

Reminder: Merely saying that something will be a work made for hire isn't enough to make it so, as discussed above.

23.6.2.9. Ownership of trademarks?

If a party is assigning IP rights in a technology, an assignment of trademark rights might or might not be part of the deal as contemplated by the parties. That's because the assigning party likely won't want to give up control of its "brand" — especially when a service provider will continue in business.

23.6.2.10. Shouldn't a services customer always own newly-created IP? (No.)

().  Under some services agreements, the Provider could create new IP. Sometimes the Customer assumes that it (the Customer) will naturally own any IP created "on my dime" — even when some of the new IP (which we assume created by the Provider) is something that the Provider definitely wants to reuse for other customers, and the Customer has no particular use for it.

But under U.S. law, the Customer won't always own whatever the Provider creates on the Customer's dime: With limited exceptions:

  1. an author or inventor owns the intellectual-property rights in his- or her creations;
  2. likewise as between the Provider and its Customer, the Provider — not the Customer — owns the work product of the Provider's employees (typically because of invention-assignment agreements between the Provider and the employees, but often as a matter of law).

Normally, if the Provider's employees create copyrighted works or other intellectual property in the course of their work (for example, a website or a software package), the Provider will typically want to own the intellectual-property rights — in large part so that the Provider can reuse its work for future customers.

In general, this Provider-favoring practice is economically desirable because:

  1. The Provider's current Customer D gets the benefit of the "toolkit" work that the Provider did for past Customers A, B, and C. This lowers the Provider's internal costs for doing its work for current Customer D, which in turn enables the Provider to offer a lower price to Customer D.
  2. In return, Customer D "pays it forward" by accepting that the Provider will own its toolkit work product and thus will later have the right to reuse the toolkit (except for Customer D's confidential information) for future Customers E, F, G, etc.

    To be sure: In some circumstances it might make more sense for the Customer to own the resulting IP. For example:

  3. the Customer might engage a software developer to design and build a new software package that the Customer wants to use in its business;
  4. and so, quite understandably, the Customer wants to own the copyright and other IP rights in the new software; that way:

    • the Customer can seek a competitive advantage over others in the Customer's line of business; and
    • the Customer can hire other providers to continue development of the new software, without being stuck with the (first) Provider (which might go out of business, etc.).

    Concerning "As between the parties," see 32.4.

23.6.2.11. Special case: Ownership of "custom" computer software

The situation: A customer hires a software developer as an independent contractor to create custom software for the customer's business. The relationship eventually breaks down. QUESTION: Who owns the copyright in the software: The developer, or the customer?

If the contract says only that the software is to be a "work made for hire" but the software doesn't fit into one of the nine statutory categories listed above (see 23.6.2.4), then the parties can settle in for some expensive litigation. See, e.g., the cases summarized at 23.6.2.12.

In the present author's experience, a reasonable compromise is the following, which is reflected in this Protocol:

–  The customer owns any newly-created IP that's unique to the customer's business or that involves the customer's confidential information;

–  The software developer owns all other IP created by the developer, so that the developer is free to reuse that IP in working for other customers.

Why this compromise? Because when a software developer, graphic artist, or other creator is developing IP for a customer:

  • The pricing quoted by the IP creator will be determined in part by the IP creator's ability to reuse IP previously created for past customers;
  • consequently, if the current customer insists on owning any IP that's created on the customer's dime, then the IP creator is likely to insist on revisiting the pricing and other economic terms of the deal.
23.6.2.12. An implied license might save the day for a hiring party

A hiring party might not be in a hopeless position simply because the work it paid to have created was not a "work made for hire" nor a joint work and the hiring party cannot obtain an assignment. The hiring party might well be able to assert at least a use right in the created work, and possibly even more than that. Selected cases are described in the following footnote — students, just briefly scan this section to get the basic idea.

Example: Asset Marketing (9th Cir. 2008): An independent contractor computer programmer sued his client for copyright infringement because the client had continued to use software developed by the programmer after the parties' relationship deteriorated. The Ninth Circuit affirmed summary judgment that the programmer could not assert his copyrights against the client, on grounds that the programmer had implicitly granted the client "an unlimited, non-exclusive, implied license to use, modify, and retain the source code" of the software. See Asset Marketing Systems, Inc. v. Gagnon, 542 F. 3d 748, 750 (9th Cir. 2008).

Example: Graham (1998): The Second Circuit vacated and remanded a copyright infringement award, on grounds that the infringement defendant was an implied licensee. See Graham v. James, 144 F.3d 229, 235, 238 (2d Cir.1998) (software created by contractor was not work made for hire but was orally licensed nonexclusively).

Example: Effects Associates (1990): A movie producer commissioned special-effects footage for a horror movie but didn't pay for it. The Ninth Circuit rejected a claim that the producer was therefore a copyright infringer, holding that the movie producer had orally been granted an implied non-exclusive license (and thus the copyright owner's action for nonpayment would have to be for breach of contract, not copyright). The court noted pointedly that the dispute over copyright would not have arisen had the parties reduced their agreement even to a one-line writing. See Effects Assoc., Inc. v. Cohen, 908 F.2d 555, 557 (9th Cir. 1990) (affirming summary judgment: copyright had not been orally transferred to alleged infringer, but actual copyright owner had implicitly granted a nonexclusive license to defendant).

Example: Oddo (1984): Two men entered into a partnership to write and publish a book about restoring Ford F-100 pickup trucks; one man was to write and edit the book, while the other was to provide the money and run the business. But the two men had a falling-out, so the business guy had someone else finish the book. The Ninth Circuit held that the author had implicitly given the partnership a license to use the manuscript, “for without a license, [the author's] contribution to the partnership venture would have been of minimal value.” Oddo v. Ries, 743 F.2d 630, 634 (9th Cir. 1984).

Example: Millennium (2015): A federal court in Colorado held that a video production company had granted an implied license allowing its client, a Mercedes-Benz dealership, to use an advertisement. Millennium, Inc. v. SAI Denver M. Inc., No. 14-cv-01118, slip op. (D. Colo. Apr. 20, 2015) (granting summary judgment), citing Graham and Effects Assoc. / ]

Example: Holtzbrinck Publ. (2000): The parent company of Scientific American magazine commissioned a consultant to develop programming for the magazine's Web site. The Southern District of New York granted partial summary judgment that the company had an irrevocable non-exclusive license to the programming. See Holtzbrinck Publishing Holdings, L.P. v. Vyne Communications, Inc., No. 97 CIV. 1082 (KTD), 2000 WL 502860 at *10 (S.D.N.Y., Apr. 25, 2000).

Example: Yojna (1987): An outside software contractor, at the request of a hospital corporation and its subsidiary, developed a computer program for hospital information management. A federal district court held that the outside contractor was the owner of the software, but the subsidiary had a perpetual, royalty-free license to use and sublicense the program, including the right to unrestricted access to source code for purposes of developing new versions and enhancements. The court also held that the license was an exclusive license within the health-care industry. See Yojna, Inc., v. American Medical Data Systems, Inc., 667 F. Supp. 446 (E.D. Mich. 1987).

Example: Latour (2014): Columbia University won summary judgment, in the Southern District of New York, that the university had an implied license to use material by a former interim faculty member. See Latour v. Columbia University, 12 F. Supp. 3d 658, 662 (S.D.N.Y. 2014).

Example: Numbers Licensing (2009): An outside contractor sued a former customer for infringing the copyight in software developed by the contractor; a federal court in Washington state held that the software was not a work made for hire, and therefore its copyright was owned by the contractor — but the customer had an implied license. See Numbers Licensing LLC v. bVisual USA Inc., 643 F. Supp. 2d 1245, 1252-54 (E.D. Wash. 2009) (denying motion for preliminary injunction).

The UK apparently has similar implied-license doctrine. See, e.g., Helme v Maher, [2015] EWHC 3151 (IPEC) (holding that plaintiff had granted implied license to defendant); see generally, e.g., License, sell or market your copyright material (UK.gov 2014).

But: Some courts have held that employers do not have such rights in works created by their employees. Selected cases:

Example: A former employee of a company had written a computer program in part on company time and in part on his own time. The Fourth Circuit held that if the employee was the owner of the copyright in the computer program, then the company would have had only a nonexclusive license to use the program, which would be revocable absent consideration. The court disapproved a holding below that the company had a "shop right" in the software; it noted that Congress had expressly declined to import the shop right doctrine from patent law into copyright law. See Avtec Systems, Inc. v. Peiffer, 21 F.3d 568, 575 n.16 (4th Cir. 1994), vacating and remanding 805 F. Supp. 1312 (E.D. Va. 1992), on remand 1994 U.S. Dist. LEXIS 16946 (E.D. Va. Sept. 12, 1994).

Example: A former employee of a  transit authority, who worked as a schedule writer, had developed scheduling software "in his spare time on the job and at home" but had kept the source code and passwords as secrets from his employer. The employee resigned to take another job and offered the transit authority a use license for an annual fee; his supervisor "fired" him, unsuccessfully demanded that he turn over his source code and passwords, called in the district attorney to have him arrested for "extortion" and "destruction of computer programs," and advised his new employer that the former employee was under investigation for extortion. A state appeals court implicitly held that the transit authority didn't have a license to use the scheduling software. See Kovar v. Southeastern Michigan Transportation Authority, slip op., No. 101761 (Mich. App. Oct. 4, 1989), reprinted in Comp. Industry Lit. Rptr. 10,317 (Oct. 23, 1989).

And: a customer won't always win an implied-license dispute. Example: In what appears to have been an early "fintech" case, a financial-services firm used custom-developed software to run its business. The software was developed by an outside contractor, but the firm and the contractor never entered into a written contract. When the parties' relationship ran aground over economic issues, the financial-services firm continued to use and modify the software. The contractor sued, and the firm defended on grounds that it either owned the software or had an implied license to continue using and developing it. On a motion to dismiss, the Southern District rejected the financial-services firm's arguments. The case apparently has no subsequent history, so presumably the parties somehow settled their dispute. See Logicom Inclusive, Inc. v. W.P. Stewart & Co., No. 04 Civ. 0604, slip op., part IV.A.3 (S.D.N.Y. Aug. 9, 2004) (denying motion to dismiss).

23.7. IP Rights Challenges

23.7.1. Defined terms

  1. Protocol 23.3 (IP definitions) is incorporated by reference into this Protocol.
  2. "Owner IP Right" refers to any IP right of an Owner (defined at 23.3.1.1 of Protocol 23.3) that is relevant to the Con­tract.
  3. "Challenge": See 23.7.2 below.
  4. "Other Party" refers to any other party to the Con­tract.
Note

().  It's not unheard of for a licensee of intellectual property to be faced with a third party's legal- or business challenge to the licensed IP rights. When that happens, the licensor — referred to here as the "Owner" — will generally want to control the response to the challenge, because the Owner will generally have more "skin in the game." On the other hand, the licensee will generally want the Owner to be responsible for costs of the challenge.

Toward that end, the following draws on ideas found in the trademark license agreement form of The University of Texas at Austin, which is discussed in more detail in the introductory commentary to Protocol 23.2.

Paragraph 2: Under U.S. law, the "Owner" might possibly be an exclusive licensee instead of the "record owner" of the IP in question.

23.7.2. Applicability of this Protocol

  1. When this Protocol is part of the Con­tract, it will govern if a third party engages in one or more of the following activities — each of which is referred to as a "Challenge" — in respect of any Owner IP Right:
    1. the third party putatively infringes the Owner IP Right; and/or
    2. the third party disputes — in any judicial, administrative, or other forum, anywhere in the world — the validity and/or enforceability of the Owner IP Rights.
  2. For purposes of subdivision 1, the term "third-party dispute" could include, without limitation, the filing and/or maintaining of one or more of the following types of action, in any forum anywhere in the world:
    1. a pre-grant opposition to an application for the Owner IP Right — for example, an opposition to an application for a patent or for a trademark registration;
    2. an affirmative defense or counterclaim of invalidity or unenforceability of the Owner IP Right;
    3. a petition for an inter partes review of a patent, and/or
    4. a petition to cancel a trademark- or copyright registration.
  3. The foregoing is not necessarily a complete list of possible types of IP challenge.

23.7.3. Non-Owner's reporting and cooperation obligation

  1. This section will apply if any Other Party becomes aware of any Challenge to one or more Owner IP Rights.
  2. The Other Party must promptly advise the Owner, in writing, about the Challenge.
  3. The Other Party must provide the Owner (and the Owner's counsel) with reasonable information and cooperation concerning the Challenge, on an ongoing basis.
  4. The Other Party on must not take any action to address the Challenge without first getting the Owner's written approval — but this does not preclude the Other Party from taking action to avoid adverse consequences to its own interests from the Challenge, for example modifying a product or service of the Other Party (assuming the modification does not infringe any Owner IP Right).
Note

What would qualify as an unreasonable Owner request for cooperation could depend in part on the likely expense involved and whether Owner would agree to bear the expense.

23.7.4. Owner control of responsive action

As between the parties, it will be up to the Owner, in the Owner's sole discretion, to decide what action(s) to take, if any, to investigate and deal with any Challenge to the Owner IP Rights, except to the extent, if any, that the Con­tract provides otherwise.

Note

The Owner will certainly want to maintain control of the response to the Challenge.

23.7.5. Confidentiality rules?

In any Challenge to Owner IP Rights, one or both of the Owner and the Other Party may designate information in its posssession as Confidential Information, in which case Protocol 5.3 (confidential information) will govern.

Note

If litigation ensues, this section might be superseded by a protective order entered by the court.

23.7.6. Owner responsibility for Challenge costs

  1. As between the Owner and the Other Party, the Owner will bear all costs and expenses of any proceeding in which the Challenge to the Owner IP Right is to be decided.
  2. Subdivision 1 applies at all phases of a Challenge proceeding, including but not limited to any appeals.
  3. For purposes of subdivision 1:
    1. The term "proceeding" refers to litigation; arbitration; and administrative actions such as, without limitation, inter-partes review actions; and
    2. The term "costs" refers to court costs; arbitration administration fees; attorney fees and -expenses; and similar charges — but specifically not including internal costs or expenses incurred by the Other Party.
  4. The Other Party is not obligated to fund or reimburse any Owner expense in respect of the Challenge unless the Con­tract clearly says otherwise.
Note

This section should provide some comfort to Other Parties.

Subdivision 1: For discussion of the phrase "as between," see 32.4.

23.7.7. Owner entitlement to monetary recovery

  1. In any proceeding concerning the Challenge, as between the Owner and the Other Party, the Owner will be entitled to any monetary awards that might be made against any third party.
  2. For emphasis, subdivision 1 extends, without limitation, to any awards of damages, profits, costs, and/or attorney fees.
Note

().  In some agreements, the Owner and the Other Party might agree to divide monetary recoveries among them.

An agreement to split monetary recoveries might be especially likely if the Other Party were to fund the costs of responding to the Challenge — in which case the parties might agree that:

(1) a high percentage of the recovery would go to the Other Party until the Other Party had recouped its out-of-pocket expenses; and then

(2) the balance of the recovery would then be split between the Owner and the Other Party (with the allocation to be negotiated).

23.8. License Definitions (for IP)

  1. "License" (as a verb, and whether or not capitalized) refers to the making, by an Owner, to a Licensee, of a binding commitment in which the Owner agrees as stated in this 23.8.
  2. "IP-Triggering Activities" refers to engaging in activities that could inge one or more IP rights of the Owner ("Owner IP rights").
  3. "IP infringement claim" refers to the assertion, by the Owner, in a court or similar forum, that one or more IP-Triggering Activities by the Licensee infringes (or if engaged in, would infringe) one or more such Owner IP rights.
  4. "IP License" (as a noun, and whether or not capitalized) refers to an Owner's agreement not to make any IP infringement claim against Licensee on account of the Licensee's engaging in IP-Triggering Activities.
  5. "Licensee" (whether or not capitalized) refers to a party granted an IP license by an Owner.
  6. In case of doubt, an IP license does not "authorize" the Licensee to engage in any particular activity.
Note

().  Subdivision 2: IP-Triggering Activities could include, for example, the making, using, selling, copying, distributing, importing, publicly performing, or publicly displaying, of one or more things, or creating derivative works based on the one or more things.

Subdivision 4 reflects the fact that, without more (e.g., exclusivity, technology transfer, etc.), an IP license is nothing more than the Owner's covenant not to sue the Licensee for infringing the Owner's relevant IP rights. Cf. Ortho Pharmaceutical Corp. v. Genetics Institute, Inc., 52 F.3d 1026, 1031-32 (Fed. Cir. 1995) (affirming dismissal of patent-infringement case; nonexclusive licensee did not have standing to sue).

Subdivision 6: Even with an IP license, the Licensee might be subject to other restrictions, imposed by law or otherwise. Here's a simple example: Imagine (i) that an Owner is a pharmaceutical-research company that owns a patent for a new type of anti-viral medication, and (ii) that a Licensee is a Big-Pharma drug manufacturer. Just because the Owner grants the Licensee a license under the patent, it might well still be illegal for the Licensee to start making or selling the medication without getting, say, FDA approval.

24. Rules: M-O

Contents:

25. Services

25.1. Services: Charges and Billing Protocol

This Protocol provides an SOP for billing services if the parties haven't agreed to a different billing arrangement.

25.1.1. Invoice submission schedule

The Vendor will cause invoices for payment under a statement of work to be issued as follows:

  1. For services where a payment schedule is specified in the statement of work: As set forth in the statement of work.
  2. For fixed-price services: One-half when all parties have signed the statement of work – to be treated as a deposit under Protocol 4.5 – and the balance upon completion of the services.
  3. For time- and/or materials-based billing: Once per month, in arrears.
Note

().  Concerning invoices generally, see Protocol 4.10.

Subdivision 3: "In arrears" means that invoices are sent after the end of the period being billed, as opposed to "in advance," when invoices are sent up front.

Subdivision 3: A statement of work will often specify the payment schedule. Sometimes, though, parties neglect to include such information; for such cases, this Protocol sets forth some fairly typical gap-filler terms.

Generally speaking, the Vendor and the Customer will want payments to be scheduled so as to reduce their downside risk in case the other side fails to deliver:

  • The Vendor, of course, will want to be paid as soon as possible, with the Customer (i) paying some portion of the money up front to cover the Vendor's expenses, so that the Vendor won't have to put its own cash at risk; and (ii) making interim progress payments as milestones are achieved— in part, so that the Vendor can stop work if the Customer doesn't pay (see 25.1.4).
  • The Customer, on the other hand, would prefer to hang on to its money until the Vendor has finished its work — and perhaps even longer, to be sure that the Vendor fixes any glitches that arise after completion. (That's why retainage of, say, 10% of the total price for a short period of time is not uncommon.)

Some providers might want to negotiate for a deposit to be applied to future invoices, in which case Protocol 4.5 would apply.

25.1.2. All-inclusive charges

The Vendor will not bill the Customer (nor anyone associated with the Customer) for fees or expenses relating to the statement of work, over and above the Vendor's agreed compensation as set forth in the statement of work.

Note

().  Vendors providing services generally incur expenses such as materials, rental of specialized equipment, and the like.

  • Some statements of work might call for the Vendor to bill those expenses to the Customer.
  • Other, "total price" statements of work might require the Vendor to absorb those expenses as part of the Vendor's fee for services.

    Customers often prefer the total-price approach — that is, if they're comfortable that the total price doesn't include too much padding for expenses. (In a competitive-bidding situation, that is likely to be less of a concern for a customer.)

    The parenthetical means that the Vendor isn't to bill, e.g., another Customer contract, a Customer affiliate or employee, etc.

25.1.3. Payment terms

Customer will pay each Vendor invoice net 10 days from receipt of invoice, or as otherwise agreed, in accordance with Lighthouse Protocol 4.13.

Note

().  Net-10-day terms (see generally 4.13.3) seem to be fairly typical for services agreements, especially for smaller service providers; in some cases the payment terms are "due on receipt."

Pro tip: The Vendor might want to propose including • Protocol 15.4 (adequate assurance of performance) and/or •  Protocol 4.4 (backup payment sources).

25.1.4. Vendor's "pencils down" option

  1. This section will apply if the Vendor does not timely receive an invoiced payment.
  2. The Vendor may suspend work — its own or, if applicable, that of one or more subcontractors, if any — pending receipt of payment, but only after giving reasonable advance notice to the Customer.
  3. The Vendor has no responsibility for any financial impact or other harm to the Customer that results from the Vendor's suspension of work under this section.
Note

().  Suspension of work — or, "pencils down!" as the administrator of my former law firm used to say about clients with past-due accounts — is sometimes just about the only leverage that a provider has against a slow-paying customer.

And if the Vendor's intellectual property ("IP") is being licensed to the Customer, and the Customer fails to pay an amount due, then the Provider might want eventually to be able to "drop the hammer" by suspending the Customer's right to use the IP — and thereby making the Customer an infringer of the Vendor's IP rights, giving rise to the possibility of significantly-greater damages liability than merely not paying.

(See also the related discussion at 4.13.8.15, raising the question whether continued use of a deliverable without paying could constitute IP infringement.)

Caution: Sometimes the service in question might be critical to Customer's operations — in which case Customer might want to prohibit the Vendor from suspending the services without "due process" such as notice and an opportunity to cure; see, e.g., Option 25.18 for sample language.

Examples of such mission-critical services could include:

  • so-called software as a service ("SaaS");
  • cloud computing services such as Amazon Web Services ("AWS"); and
  • employee-management services such as those provided by Insperity.

25.1.5. Required: Appropriate billing records

  1. This section will apply if the Vendor is to be paid for services based on information maintained by the Vendor and to which the Customer does not have independent access — for example, if the Vendor charges by the hour.
  2. In such cases, the Vendor will keep records that meet the following standards:
    1. the records will be reasonably sufficient to support the Vendor's invoices, for example, time records; and
    2. the records will be maintained in a commercially-reasonable form, with a view toward facilitating audits of the Vendor's records (and thus making audits less costly for all concerned).
Note

().  Background: Some service projects are priced by multiplying a billing rate by the time spent by the provider's personnel. For such a project, the customer might be concerned that timesheet data could be faked, or simply mistaken. The Customer therefore might want to include, in the contract, requirements that the Vendor set up systems to record and maintain data that can be used to corroborate timesheet data, such as by incorporating Protocol 5.7. See, e.g., Time and materials (Wikipedia.com); Cost-plus pricing (Wikipedia.com).

Subdivision 2.a: Such records could include, for example, time cards; access-card records; and even biometric data, as discussed in a 2020 article. See generally, e.g., Glenn Haley, Warning from the U.K. court against rubber-stamping timesheets (JDSupra.com 2020).

25.1.6. Customer's audit right

Whenever the Vendor is required to keep billing records under § 25.1.5, the Customer may have the records audited in accordance with Protocol 4.3.

Note

Concerning "commercially reasonable," see the related discussion of commercially-reasonable efforts at 9.2.

25.1.7. Vendor's flow-down obligation

  1. If the Vendor uses subcontractors, then the Vendor is to ensure that subcontractors agree to the same recordkeeping- and audit provisions as apply to the Vendor.
  2. For the avoidance of doubt: This section in itself neither authorizes nor prohibits the use of subcontractors.
Note

Subdivision 2 is a guardrail provision.

25.2. Services: Licenses and Permits Protocol

Protocol 25.2 allocates responsibility for the licenses and/or permits that will often be required in a services project:

  • for the work itself, e.g., building permits; and
  • for the Customer to use any resulting deliverables (if any).

That can be important not just in services work but in other types of transaction as well, as discussed at 25.2.5.1.

25.2.1. Vendor responsibility: Licenses and permits for work

Unless otherwise agreed, the Vendor will obtain any:

  • building permits,
  • contractor- and other professional licenses, and
  • all other authorizations, of any kind,

that are needed for the activities that constitute performance of the services.

Note

Caution: Even starting work without a license could be very costly to the Vendor, as discussed in more detail at 25.2.5.3

25.2.2. Customer responsibility: Any licenses for use of deliverables

Unless otherwise agreed, the Customer will obtain:

  • any licenses (for example, patent licenses) and other authorizations,
  • that are needed for use of the deliverables (if any),
  • by the Customer and its agents and/or contractors,

other than for such use by the Vendor and the Vendor's agents and/or subcontractors.

Note

().  Caution: Services contracts sometimes include a warranty by the vendor that, in performing the services, the vendor will not infringe any third party's IP rights.

  • The vendor might even warrant that the deliverables themselves do not infringe third-party IP rights.
  • For that matter, under the (U.S.) Uniform Commercial Code, UCC § 2-312, a "merchant" seller of goods (not services) implicitly warrants the goods' noninfringement. From UCC § 2-312: "(3) Unless otherwise agreed a seller who is a merchant regularly dealing in goods of the kind warrants that the goods shall be delivered free of the rightful claim of any third person by way of infringement or the like …." see also the discussion at 13.5 concerning who is a "merchant." ]

But: Such vendor warranties might not protect the customer from third-party infringement claims arising from the customer's use of the deliverables, which is a distinct issue. Example: Under U.S. patent law, use of a patented product or method, without permission of the patent owner, would infringe the patent. See 35 U.S.C. 271 (a), (g).

Even under the Uniform Commercial Code, the responsibility for infringement might rest with the customer, not the provider, because UCC § 2-312 also says: "(3) … a buyer who furnishes specifications to the seller must hold the seller harmless against any such claim which arises out of compliance with the specifications."

So: In any services contract, both the vendor and the customer should give some thought to whether any third-party intellectual-property licenses or other authorizations might be needed for the customer to be able to use the deliverables. Such "use" authorizations could include, without limitation, patent licenses and regulatory licenses.

As one hypothetical example, suppose that a service provider is a pharmaceutical laboratory that is licensed to manufacture controlled substances such as opioids. It might be perfectly legal for the lab to whip up a custom batch of an opioid-based medication for a licensed physician — but in many countries the physician would need to be state-licensed to practice medicine and federally-licensed to dispense such medications. See generally, e.g., Maureen Malone, How to Obtain a DEA License for Physicians (Chron.com, undated).

25.2.3. Each party responsibility: Its related third-party claims

Each party responsible for obtaining a particular authorization under this Protocol will do the following:

  1. defend (as defined at Protocol 14.1) the other party and its Protected Group against any claim made by the third party; and
  2. indemnify (that is, reimburse), as stated in Protocol 14.3, the other party and its Protected Group for all foreseeable damages, expenses, and losses resulting from the third-party claim.
Note

Subdivision 1: A defense obligation might arise a matter of law – or it might not — from the indemnity obligation of subdivision 2, as discussed in the commentary to Protocol 14.3.3.

Subdivision 2 probably duplicates applicable law, in that indemnification for foreseeable damages (that is, reimbursement) is likely to be just bog-standard damages for breach of contract, specifically for the indemnifying party's failure to obtain the license and/or permit that it agreed to obtain. But it can't hurt to be specific — not least as a helpful reminder to the parties' business people.

Caution: While liability for breach of contract is limited to foreseeable lossses, it's been suggested that the same might not be true for a contractual indemnity obligation, absent a specific contractual provision capping the amount that must be spent to fulfill that obligation. See generally Glenn D. West, Consequential Damages Redux …, 70 Bus. Lawyer 971, 998 (Weil.com 2015) ("VI. Overlaying the Concept of Indemnification for Losses on the Contract Damages Regime"), archived at https://perma.cc/D2HC-Z5XD

25.2.4. Suspension of work for disagreement about licenses & permits

  1. This section will apply if:
    1. the Vendor believes that a particular authorization is necessary, but
    2. the Customer disagrees and wants the Vendor to proceed without that authorization.
  2. The Vendor will not be in breach of the Con­tract if — with prompt notice to the Customer — the Vendor suspends the relevant work until such time, if any, as the parties reach agreement or the Vendor obtains the authorization in question.
  3. If the parties are not able to come to agreement on that point, then they will escalate the dispute in accordance with Protocol 21.11.
Note

This section addresses the situation in which, say: (1) the Vendor thinks that a particular authorization is needed for a project, but (2) the Customer doesn't want to take the time or spend the money to obtain the authorization; and (3) the Vendor doesn't want to go forward without the authorization, for fear that the Vendor would incur legal liability.

25.2.5. Additional notes

25.2.5.1. Licenses and permits: The business context

Clearly allocating responsibility for licenses and permits can be important in all kinds of transactions, services and otherwise: Example: In one Seventh Circuit case:

  • An export shipment of onions bound from the U.S. to Honduras had to be returned to the U.S. — and ended up spoiling — instead of being delivered to the buyer, because no one had arranged to have the onions had passed the required inspection for plant-borne pests and diseases.
  • Of course, the parties started pointing fingers at each other, saying in effect, that was YOUR job.
  • The total price of the onion shipment was just over $24,000, plus an additional $21,000 in shipping charges for the return trip to the U.S. — sadly, the parties almost certainly spent far more than that in litigating who was responsible for the dropped ball. See F.C. Bloxom Co. v. Tom Lange Co., 109 F.4th 925 (7th Cir. 2024), affirming 642 F.Supp.3d 775 (C.D. Ill. 2022) (granting summary judgment).
25.2.5.2. What kinds of licenses and permits might be required, and who is to procure them?

For some services projects, the law might require, for example:

  1. an occupational license for the provider, e.g., a contractor license; and/or
  2. a permit for specific work itself, a building permit.

In probably the vast majority of tranactions, the Vendor takes on the job of obtaining these work authorizations. That normally makes sense, because the Vendor will presumably know the ropes of getting the permits better than the Customer.

25.2.5.3. Caution: Even starting work without a license could be costly

Imagine that you're a service provider — and now imagine that for a particular project, you don't have all your required licenses and permits in place, at all times. That could give your customer the legal right to "stiff" you, and even to demand that you repay money you've already been paid.

For example: Under a California statute, a contractor might forfeit its right to be paid if it undertakes work required to be done by a licensed contractor (e.g., certain construction- or remodeling work), but does not itself have the proper license(s) at all times while performing the work.

Example: In a California case, a subcontractor had not obtained the required license when it prepared initial shop drawings and did other preliminary work. In the trial court, the subcontractor won a judgment for more than $220,000 in unpaid invoices, but on appeal the subcontractor lost because it hadn't been licensed while doing the preliminary work. See Great West Contractors, Inc., v. WSS Industrial Construction, Inc., 162 Cal. App. 4th 581, 76 Cal. Rptr. 3d 8 (2d Dist. 2008), applying Cal. Bus. & Prof. Code § 7031.

Moreover, under a 'disgorgement' amendment to the California statute, such a contractor might have to repay any payments it did receive for the work.

A similar Tennessee statute is a bit less draconian: "Any contractor required to be licensed under this part who is in violation of this part or the rules and regulations promulgated by the board shall not be permitted to recover any damages in any court other than actual documented expenses that can be shown by clear and convincing proof." Tenn. Code Ann. § 62-6-103(b); cf. The Fifth Day, LLC v. Bolotin, 72 Cal. App. 4th 939 (2d Dist. 2009) (reversing summary judgment that party was barred from recovering compensation for services; party was not a "contractor" within the meaning of the statute).

The corresponding Georgia statute likewise includes certain exceptions that can allow an unlicensed residential contractor to recover, but in one lawsuit, an appeals court held that the contractor did not qualify for the exceptions. See Fleetwood v. Lucas, 840 S.E.2d 720, 722 (Ga. App. 2020) (reversing judgment in favor of unlicensed contractor).

Washington state has a registration requirement. Example: In one case, a homeowner hired a worker to refinish the homeowner's hardwood floors. The homeowner ended up unhappy with the work and refused to pay the worker. The worker sued, but was "poured out" of court because she had not registered with the state as required by statute. See Dobson v. Archibald, 523 P.3d 1190 (Wash. 2023) (affirming summary judgment in favor of homeowner), citing Wash. Rev. Code § 18.27.020.

(Incidentally, the Washington statute makes it a criminal offense (a "gross misdemeanor") to "[a]dvertise, offer to do work, submit a bid, or perform any work as a contractor without being registered as required by this chapter[.]")

25.2.5.4. Will the proper person be licensed for services?

Service providers should be sure that the proper individual, or the proper organizational party, is both licensed and named in the contract. Getting that wrong could lead a customer to try to stiff the provider. Example: In a California case, a construction contract (allegedly) mistakenly listed an unlicensed contractor as the party that would do renovation work on a movie/restaurant. This led the owner to refuse to pay. When the contractor sued for payment, the trial court threw out the lawsuit, on grounds that the wrong party was supposedly licensed. Rescuing the contractor, the court of appeals reversed, holding that "Despite the mistake in the written contract, Rosedale and Movie Grill knew, intended and agreed that, in fact, Panterra GP would act as the general contractor and would perform the work contemplated by the agreement. And, indeed, that is what happened." The parties could have avoided the issue by getting the contract right. Panterra GP, Inc. v. Super. Ct. of Kern Cty (Rosedale Bakersfield Retail VI, LLC), 74 Cal. App. 5th 697, 702 (2022) (reversing order sustaining demurrer and directing that demurrer be overruled).

25.2.5.5. A customer might be vicariously liable for a provider's IP infringement

In a Ninth Circuit case, Rearden LLC, a producer of facial motion-capture software, sued the Walt Disney Company, alleging that one of Disney’s visual effects contractors had made unauthorized copies of Rearden's software during production of Disney’s 2017 live-action film Beauty and the Beast. Relevantly here:

  • The jury found Disney vicariously liable for its contractor's copyright infringement, awarding Rearden actual damages of just over $250,000.
  • The trial court overturned the verdict and granted judgment as a matter of law, on grounds that Rearden had not (in the court's view) introduced sufficient evidence at trial of Disney’s practical ability to stop or limit its contractor's directly-infringing conduct.
  • The Ninth Circuit reversed on that point, concluding that Rearden had indeed introduced legally sufficient evidence at trial to support the jury's verdict. After affirming the judgment below in all other respects, the appellate court remanded, presumably for entry of judgment on the jury verdict and damage award. See Rearden, LLC v. Walt Disney Co., No. 24-3970 at part III.A and III.B, slip op. at 19-25 (9th Cir. Sept. 11, 2025). ]
25.2.5.6. Would use of deliverables violate the law?

It should be apparent that a services provider can't necessarily warrant that the customer's use of deliverables won't violate applicable law.

Example: Suppose that a freelance software developer is engaged by a customer to write a computer program that scans the customer's network in search of security gaps.

  • Such a computer program might also be usable for nefarious purposes — most obviously, scanning someone else's network in an attempt to break in.
  • It follows that the software developer would not want to warrant that the customer's use of the computer program would not infringe any third-party rights.

25.3. Services: Performance Protocol

25.3.1. Complete, safe, professional performance

  1. The Vendor will see to it that the services specified in the statement of work are performed:
    1. as set forth in the statement of work,
    2. from start to finish,
    3. in accordance with: (i) the agreed written statement of work; and (ii) any clearly-relevant industry- or professional standards;
    4. in a safe, diligent, and "professional" manner (defined in subdivision 2 below),
    5. all at the Vendor's own expense except as clearly agreed otherwise in writing.
  2. For purposes of this Protocol, the term "professional" refers to work that would be considered proficient by individuals who have the knowledge, training, and/or experience necessary for the successful practice of the relevant trade or occupation.
Note

().  Subdivision 1: The phrase, "see to it" takes into account that the Vendor might well be a prime contractor that engages subcontractors to do various phases of the work. (Note that in some such contracts that are customer-biased, the prime contractor might have to get the customer's approval before using subcontractors at all, or before using any particular subcontractor; see [DCT TO DO: LINK].)

Note that this performance standard is phrased as a covenant, that is, a promise, and not as a representation or warranty, for reasons discussed in the commentary at 16.2.

Subdivision 1.b: The "start to finish" language has in mind that when a customer hires a service provider, the customer generally wants the provider to "just handle it."

Subdivision 1.d's definition of "professional" is adapted from the Supreme Court of Texas's definition of workmanlike. See Melody Home Mfg. Co. v. Barnes, 741 S.W.2d 349, 354 (Tex. 1987), quoted in Ewing Constr. Co. v. Amerisure Ins. Co., 420 S.W.3d 30, 37 (Tex. 2014) (responding to certified question from Fifth Circuit).

Relatedly: In some circumstances in some jurisdictions, the law might impose an implied warranty of workmanlike performance (concerning which, see 16.1.6.3).

Subdivision 1.d: Some service providers might balk at using the term professional or even workmanlike performance because they fear the term could be ambiguous. But any standard of performance of services is likely to involve factual determinations in litigation or arbitration, so it's hard to see how one is more- or less favorable than the other.

Subdivision 1.d: Caution: Some customers want language such as, in accordance with the highest professional industry standards. For a service provider, though, this is arguably the worst of all worlds: Not only is the phrase vague, but the provider might as well hang a "Kick Me!" sign on its own back, because anything less than perfection would be open to cricitism in court — much as can be the case with the term best efforts (concerning which, see the definition at Protocol 9.1).

25.3.2. Suitably qualified- and trained people

The Vendor will see to it that the services are performed only by people — whether working for the Vendor or for any Vendor subcontractor:

  1. who have been suitably trained for their roles and have appropriate experience and supervision; and
  2. who are legally eligible to be employed in the relevant capacity under applicable laws governing, for example, (a) immigration, and (b) export controls.
Note

().  Setting out standards for services people can: (1) reduce the likelihood of problems; (2) make project monitoring easier for the Customer; and (3) simplify litigation and other dispute resolution if a project goes south — see the additional discussion at 8.3.1.)

Caution: It's crucial to comply with export-control laws: Providing certain types of information to non-U.S. persons, even when they are located in the U.S., can result in criminal liability and imprisonment — as a University of Tennessee professor found out to his dismay, as discussed at 31.9.

25.3.3. Vendor control of "means and maner" of work

As between the Vendor and the Customer, the Vendor has the exclusive right — and the exclusive responsibility — to control the means and manner by which the services are performed.

Note

().  Language such as this is typically included to bolster the argument (by the Customer, usually) that the Vendor and its personnel are not Customer employees; see generally the commentary to Protocol 3.8 (independent contractors).

Concerning "As between the Vendor and the Customer," see 32.4.

25.3.4. Procurement of all materials, etc.

Unless the statement of work clearly says otherwise, the Vendor will take care of the timely acquisition, installation, and maintenance of whatever might be needed for performance of the services, including but not limited to the following:

  1. necessary materials, including but not limited to equipment and/or tools;
  2. suitable workspace;
  3. electrical power;
  4. computer hardware and -software;
  5. Internet- and other communications capabilities;
  6. safety equipment for the Vendor's people; this would include, for example, any necessary personal protective equipment (PPE); and
  7. all other tangible- and intangible items needed to meet the Vendor's performance responsibilities.
Note

().  When the Customer hires the Vendor, the Customer generally doesn't want to be continually asked by the Vendor's workers, "hey, do you happen to have a ball-peen hammer," and so on.

(Of course, as long as the Customer is agreeable, the Vendor's occasionally asking the Customer for things shouldn't be a problem in a cooperative business relationship.)

For an example of similar language, see a 2021 federal court case, where "[t]he subcontract further required Defendant to provide all necessary materials, labor, equipment, supplies, and services to diligently prosecute its work in accordance with the progress schedule." Clayco, Inc. v. Food Safety Group, Inc., No. 4:20-mc-00739, slip op. at 1 (E.D. Mo. Mar. 8, 2021) (granting motion to confirm arbitration award of "cover" damages to be paid by subcontractor that failed to perform as agreed).

25.3.5. Prep and clean-up at Customer sites

Unless the statement of work clearly says otherwise, the Vendor will see to any necessary preparation- and clean-up of work areas at any Customer site where services are performed.

Note

Some customers want explicit language to this effect in their services contracts.

25.3.6. Defects

  1. This section will apply if the Customer reports to the Vendor that one or more defects exists in services and/or deliverables under a statement of work.
  2. The Vendor (primarily) and the Customer (with limited obligations) will address the reported defects in accordance with the "Three Rs" protocol — in a nutshell: repair, replace, or refund — at Protocol 13.13.
Note

In some specialized situations, the parties might want to lay out more-detailed plans of action for dealing with defects in deliverables — possibly in the form of a "contingency table." Here's a hypothetical example of a contingency-table format for addressing defects in deliverables — it's sanitized from an actual software-development contract that I once negotiated for a client):

nil

25.3.7. Customer cooperation

  1. This section will apply if the Vendor makes any reasonable request for relatively-minor cooperation by Customer in connection with a statement of work.
  2. The Customer will provide the requested cooperation — but to be clear: the Vendor remains responsible for completing the work except as clearly agreed otherwise.
  3. Whether a request for cooperation is reasonable might depend in part on whether the Vendor offers to pay or reimburse the Customer for associated expenses.
Note

In many situations the Customer might well have to do something as simple as (for example) opening a locked gate to allow the Vendor's personnel to come onto the Customer's premises.

25.3.8. Time not "of the essence" (usually)

  1. This section will apply if the Vendor misses a deadline or other target date set forth in an agreed statement of work.
  2. The Vendor's missing of such a target date is a breach of the Vendor's obligations under the statement of work, but the breach is not necessarily a "material" breach — that is, time is not "of the essence" for that deadline — unless the statement of work clearly says so.
Note

Concerning "material breach," see generally the definition at Protocol 18.6.

25.4. Services: Statements of Work Protocol

25.4.1. Parties: Vendor and Customer

  1. When this Protocol is agreed to, it signifies that under the Con­tract one party (referred to as the "Vendor") is to provide specified services for another party (the "Customer").
  2. For purposes of this Protocol, the term "party" refers to a party to the Con­tract unless the context clearly and unmistakably indicates otherwise.

25.4.2. Prerequisite: Signed statements of work

A signed, written, statement of work:

  1. sets out the Vendor's exclusive responsibility for providing services under the Con­tract; and
  2. sets out the Customer's exclusive responsibility for paying for services under the Con­tract.
Note

Starting a services project without at least an agreed, high-level, written statement of work can be risky to both the service provider and the customer. Not least, this is because the lack can lead to costly, time-consuming litigation.

Example: In a California case about one of the Fast & Furious movies, a state appeals court gave the parties a mild scolding for not having signed at least a short-form written agreement, as they'd done in previous movies. The court noted pointedly that for previous releases in the F&F franchise, the parties had needed only two-page contracts, because those contracts had simply adopted an earlier written agreement with a few modifications. See Moritz v. Universal City Studios LLC, 54 Cal. App. 5th 238 (Cal. App. 2020) (affirming denial of defendant's motion to compel arbitration in lieu of litigation).

25.4.3. The Con­tract takes precedence — usually

A statement of work will override the Con­tract only if the statement of work noticeably states — at or near its beginning — that one or more provisions of this Protocol are being overridden.

Note

().  For greater business flexibility, a statement of work should be able to override the Con­tract — but to protect both parties, a party shouldn't "bury" a substantive change to the Con­tract deep within a statement of work.

This section is worded so that:

  • a single such noticeable statement would suffice; and
  • the statement need not specify the overridden provisions.

The idea is simply to alert the party reviewing the statement of work that the drafting party seeks to override the Con­tract.

Caution: Drafters should check the underlying services agreement (e.g., a master services agreement) to be sure that the services agreement doesn't preclude modification by a statement of work. Example: A federal court in Louisiana held that a damages cap in an agreed statement of work did not apply because the contract itself said, "[n]othing contained in any Work Order will be construed to change or amend the terms and conditions of this Contract." See Planet Construction J2911 LLC v. Gemini Ins. Co., No. 2:21-CV-01075, slip op. at part III.B, text acc. nn.15-16 (W.D. La. Jul. 20, 2023).

25.4.4. Limited use of external evidence

  1. The Vendor and/or the Customer may offer extrinsic evidence to supplement or explain — but not modify — a statement of work.
  2. If the extrinsic evidence includes any contested testimony by someone having an interest in the matter — for example, if the Vendor claims that the Customer orally agreed to a price increase, or if the Customer claims that the Vendor orally agreed to a price cut — then the party offering the testimony must support it with reasonable corroboration.🔗
  3. Neither party is to assert that extrinsic evidence can be used to contradict the statement of work.
Note

().  Background: For smaller projects, the parties' statements of work might be, um, sparse; for that reason, this Protocol allows for a statement of work to be fleshed out by extrinsic evidence (a.k.a. "parol" evidence). The language of this section is modeled closely on section 2-202 of the Uniform Commercial Code. By its terms, § 2-202 applies only to contracts for the sale of goods, but the approach is useful here as well.

Subdivision 3: Tangential to this no-contradiction requirement: In an Eighth Circuit case, the court observed that evidence of usage in the trade could not be used to add "an entirely new provision" to the contract in question. Dakota Energy Coop., Inc. v. East River Elec. Power Coop., Inc., 75 F.4th 870, 877 (8th Cir. 2023) (affirming summary judgment).

25.4.5. SOWs as separate contracts

Each statement of work under the Con­tract is to be considered a separate contract that:

  1. is independent of any other statement of work, if any, and
  2. incorporates the Con­tract by reference — including but not limited to this Protocol, whether or not the incorporation is explicit.
Note

Alternative: "Each statement of work under the Con­tract is to be considered an addition to the Con­tract and not as a separate contract."

(See the comment at 13.9.9 for why this section doesn't use the above alternative approach.)

25.4.6. No guarantee of minimum work

Unless the Con­tract expressly states otherwise, the Con­tract does not entitle the Vendor to a certain minimum amount of work or compensation over and above that set forth in one or more agreed statements of work.

Note

This section seeks to roadblock a vendor's claim that a customer had supposedly agreed to give the vendor a certain minimum amount of billable work or of compensation but failed to do so. Such claims have been known to happen. See Gulf Eng'g Co. v. Dow Chem. Co., 961 F.3d 763, 766-67 (5th Cir. 2020) (reversing denial of partial summary judgment and rendering judgment in favor of Dow); Bus. Sys. Eng’g v. IBM, 547 F.3d 882 (7th Cir. 2008), affirming 520 F. Supp. 2d 1012 (N.D. Ill. 2007) (granting summary judgment dismissing subcontractor's claim that IBM had supposedly promised $3.6 million of work to the subcontractor); James Constr. Grp., LLC v. Westlake Chem. Corp., 650 S.W.3d 392, 397 (Tex. 2022).

25.4.7. Vendor assumption of risk about conditions "on the ground"

  1. In connection with the amount of work that the Vendor is to perform and the Vendor's cost of of such work: The Vendor ASSUMES THE RISK that the relevant existing conditions are NOT as contemplated in the statement of work.
  2. In case a question comes up: The Vendor is not assuming the risk of any harm to the Customer from those conditions not being as so contemplated.
Note

The Vendor's responsibility for verifying the initial conditions "on the ground" would mean that the Vendor likely wouldn't be paid for unexpected extra work, Example: An excavation company didn't visit a site, where it was to dig a foundation and remove dirt, even though the contract included a representation by the excavation company that it had done so. The excavation company ended up having to remove far more dirt than it had anticipated — and it failed in its attempt to recover its extra costs. See D2 Excavating, Inc. v. Thompson Thrift Constr., Inc., 973 F.3d 430 (5th Cir 2020): See also, e.g., Nova Group/Tutor-Saliba v. United States, 87 F.4th 1375 (Fed. Cir. 2023) (affirming rejection of contractor's claim for additional compensation for alleged differing site conditions; contract documents had disclosed to contractor that unpredictable conditions and possible obstructions would be encountered).

Relatedly: It's not uncommon for the need for extra work to be discovered late. A contractor might believe that its customer had orally agreed to pay for late-arising extra work. But that doesn't mean a trial court would be convinced that the oral promise actually happened. And in the U.S. court system, it'd be very difficult to convince an appellate court to overrule a trial-court finding on that point (to say nothing of a jury verdict) if the finding wasn't an unreasonable view of the evidence. See, e.g., Shift Services, LLC, v. Ames Savage Water Solutions, LLC, 2023 ND 237, 999 N.W.2d 210, 212-13 (affirming dismissal of breach of contract claim: while contrary evidence might have been provided at trial, record supported trial court's finding that parties did not agree to modify their original agreement).

(Presumably a smart vendor, in pricing the proposed work, would take this "investigation risk" into account.)

25.4.8. Change orders: In writing

  1. An agreed statement of work between the Vendor and the Customer can be modified only as provided in this Protocol.
  2. A statement of work can be modified by an agreed, written "change order" as provided at Protocol 3.1.
  3. A statement of work can also be modified by an agreed oral change order if the parties' oral agreement is prominently summarized in a confirming email that:
    1. is promptly sent by one party,
    2. is clearly shown to have been received by the other party, and
    3. is not objected to by the other party — likewise in writing — within a reasonable period of time.
Note

().  This section takes the same general approach as Protocol 3.1 (amendments). That approach is especially appropriate for statements of work, which can "evolve" as a project progresses, increasing the importance of leaving a paper trail.

Subdivision 3: A reality of the business world is that on occasion, parties will agree orally to a change order, but then they never get around to confirming the change in writing.

Example: In an Alaska case, "[a] contractor hired a subcontractor to undertake part of the construction of a remote bridge. The initial scope of the contracted work soon changed. Neither the contractor nor the subcontractor kept detailed records of the changes and their associated costs. Years after the project was completed, the subcontractor sued for damages, claiming that it had not been paid for the work it completed." Johnson v. Albin Carlson & Co., No. S-18615, slip op. at 2 (Alaska Jun. 13, 2025) (affirming district court judgment in part, reversing and remanding in part) (emphasis added).

What's relevant here isn't whether the subcontractor got paid, but the fact that the parties had to litigate the case all the way to the state supreme court — which sent the case back to the trial court for further (doubtless-costly) proceedings.

Subdivision 3: By providing a specific protocol for such oral change orders, this section seeks to "write around" court rulings that agreed writing requirements for change orders can be orally waived. Example: An electrical subcontractor successfully sued a prime contractor for payment for extra work without a written change order — even though the subcontract seemed emphatically to rule out payment in the absence of such a written change order. The trial court held, and the appellate court agreed, that the prime contractor effectively waived the change-order requirements by virtue of the interactions between the project manager — who had "apparent authority" — and the subcontractor. See Patriot Constr., LLC v. VK Elec. Servs., LLC, 257 Md. App. 245, 290 A.3d 1108, 1117 (2023) (affirming award to subcontractor); cf. Menard, Inc. v. DiPaolo Industr. Develop't, LLC, 2023-Ohio-1188, ¶ 15 (Ohio App. Apr. 10, 2023) (reversing summary judgment in part; genuine issue of material fact existed as to whether writing requirement for change orders had been waived).

Example: To like effect, see a Washington-state case in which the court mostly affirmed judgment on a jury verdict that the builder of a 41-story condominium tower was entitled to some $30 million in additional payments (including attorney fees) because the owner had waived the strict change-order procedures in the construction contract. See Skanska USA Bldg. Inc. v. 1200 Howell St., LLC, No. 58950-8-II, slip op. at 35 (Wash. App. Jan. 22, 2025) (unpublished, affirming judgment on jury verdict in pertinent part).

Subdivision 2: Not sending a written message, confirming an oral change order, doubtless hurt the case of a subcontractor that unsuccessfully sought (among other things) $40,000 for additional "glazed tile work," because the trial court found that the subcontractor's sole testifying witness wasn't credible in view of the witness's mistakes and inconsistency with documentation. See Citi Bldg. Renovation, Inc. v. Neelam Constr. Corp., 2020 NY Slip Op 51575(U), 70 Misc.3d 1204(A) (Sup. Ct., NY Cnty., Dec. 9, 2020).

25.4.9. Apparent authority for change-order approval

A modification to a statement of work may be agreed to by a party only by someone with at least apparent authority — that is, unless the Con­tract or the statement of work specifically limited who could agree to modifications.

Note

Some signature-authority restrictions are shown in the following footnote.41 Caution: A court might hold that such signature-authority restrictions were waived. See, e.g., Patriot Constr., supra, 290 A.3d at 1117.

25.4.10. Obligations of Vendor personnel

  1. The Vendor will see to it that each individual involved in performing services under the Con­tract is legally bound by personal obligations that are sufficient to support any corresponding obligations that the Vendor has under the Con­tract.
  2. Example: The individuals' personal obligations referred to in subdivision 1 include, without limitation, any applicable obligations of:
    1. of confidentiality and/or
    2. to assign ownership of inventions.
  3. For the avoidance of doubt:
    1. The Vendor's obligations under subdivision 1 apply to the relevant employees of both the Vendor and the Vendor's subcontractors (if any); but
    2. This section neither authorizes nor prohibits the Vendor's use of subcontractors.
Note

This often won't be an issue in routine services agreements, but some customers like to have similar language in their contracts involving customers' confidential information, or when the service provider might be creating intellectual property that the customer will own or be licensed to use.

25.4.11. Party rights in any resulting new IP

  1. This section will govern unless clearly agreed otherwise in the relevant statement of work.
  2. Any intellectual property, or "IP," that is newly created in the course of the statement of work ("New IP") will be owned as stated in Protocol 23.6.
  3. The Customer will have a license (as defined at Protocol 23.8), under the Vendor's IP rights in any such New IP, to use the New IP in a manner consistent with the statement of work.
  4. If a statement of work clearly says that the Customer will own any such newly-created IP, then the parties will follow the procedures in Protocol 23.6 to confirm the Customer's ownership.
Note

Background: Sometimes, in the course of performing agreed services, the Vendor's people will produce new intellectual property, a.k.a. "IP." An overreaching Customer might insist on owning all such IP, but the Vendor will often push back on such demands. (For more discussion, see the commentary in the protocols cited below.)

25.4.12. Other Lighthouse protocols incorporated by reference

The following Lighthouse protocols are incorporated by reference:

  • Services: Licenses and Permits Protocol (25.2)
  • Services: Performance Protocol (25.3)
  • Services: Charges and Billing Protocol (25.1)
  • Site Visit Protocol Protocol (9.13) (if any party's personnel will be physically present at premises controlled by another party to the Con­tract)
  • Computer-System Access Protocol Protocol (9.4) (if any party's personnel will access one or more computers or network controlled by the another party to the Con­tract)
  • IP Infringement Warranty Protocol (23.5) (if a third party asserts that a deliverable under a statement of work infringes intellectual property rights assertable by the third party)
  • Services: Termination Protocol (25.5)

25.4.13. Escalation

The parties will address any dispute between them about a statement of work by escalation to a neutral as stated in Protocol 21.11.

Note

Disputes about statements of work are certainly not unknown; this happened, for example:

  • when IBM undertook to replace the software used by the State of Indiana to administer the state's welfare program; See Indiana v. IBM Corp., 51 N.E.3d 150, 153 (Ind. 2016), after remand, 138 N.E.3d 255 (Ind. 2019).
  • when another IBM project, this one for an English insurance company, evidently went off the rails; See Soteria Ins. Ltd. v. IBM UK Ltd., [2022] EWCA Civ 440, ¶ 2, summarized in Edward Lucas, A good day for wasted expenditure (JDSupra.com 2022).
  • when software giant Oracle undertook to develop a computer system to implement an "Obamacare" exchange for the State of Oregon — and the state sued not just Oracle itself, but several individual Oracle mid-level managers, as discussed at 17.6. The parties eventually settled, with Oracle agreeing to pay Oregon $25 million in cash and provide the state with another $75 million in technology.

This escalation requirement therefore seeks to channel the parties into a sensible dispute-resolution process in the interest of trying to avoid costly- and time-consuming litigation or arbitration.

25.5. Services: Termination Protocol

When a statement of work is terminated, it's not unlikely that the Customer is "pulling the plug" — typically because of dissatisfaction with the Vendor's work — and might still want the project to be finished, but by another provider. When that's the case: • the Customer will want the Vendor to be explicitly obligated to turn over all undelivered deliverables and work-in-progress; but • the Vendor won't want the Customer to try to obtain concessions by inappropriately withholding final payments.

25.5.1. Precedence of this Protocol

When this Protocol is included in the Con­tract, it will apply any time that a statement of work ("SOW") expires or is otherwise terminated except to the extent (if any) that the parties specifically agree otherwise — in a signed writing — either:

  1. in the SOW — but the SOW must explicitly override this Protocol by name (not merely via a general statement of precedence); or
  2. at substantially the time of termination.
Note

Subdivision 1 addresses the situation where the customer's SOW form says, in effect, "this SOW will control no matter what the vendor's contract form says."

25.5.2. Prompt final Vendor deliveries

In addition to anything else specified in the SOW, the Vendor will promptly deliver the following to the Customer (or to the Customer's designee):

  1. all completed deliverables and work-in-progress that are called for by that SOW — those, however, remain subject to any agreed restrictions on providing them to competitors of the Vendor;
  2. any materials (e.g., equipment) that were provided or paid for by (or on behalf of) the Customer for use in connection with that SOW;
  3. any Customer-owned data that was provided by or on behalf of the Customer;
  4. any Customer-owned data that was generated by or on behalf of the Vendor in connection with that BSOW; and
  5. one or more final invoices for the SOW.
Note

This can function as a sort of post-termination checklist for the Vendor (and Customer).

25.5.3. Prompt Vendor removal of its property

In addition to anything else specified in the SOW, the Customer:

  1. will allow the Vendor to remove, from Customer-controlled premises, any Vendor-furnished tangible property (e.g., equipment, raw materials), except to the extent that the SOW explicitly contemplated that particular property would be left behind; and
  2. will not interfere with such attempts by the Vendor to remove Vendor property from premises controlled by third parties — such interference could include, for example, declining to approve removal if a third party checks with the Customer about it.
Note

Customers have been known to lock Vendors out of Customer premises and, in effect, use Vendor property as a hostage for leverage in bargaining.

25.5.4. Prompt final payments

  1. The Customer will pay any final amounts due in accordance with the agreed payment terms to the extent not inconsistent with any payment prerequisites in the SOW.
  2. In case the question comes up: Customer's payment obligations under subdivision 1 above include, without limitation, the following payment obligations to the extent applicable:
    1. paying amounts due under all then-pending Vendor invoices; and
    2. paying amounts due under the Vendor's subsequent final invoice(s), if any, for previously unbilled services and (if applicable) reimbursable expenses.
Note

Hypothetical example: Suppose that —

  • the SOW says that the Customer will pay Amount A after a particular Milestone M is achieved; and
  • Milestone M hasn't happened when the SOW is terminated (or expires).

In that situation, the Customer is free not to pay Amount A

25.5.5. General cooperation in wrapping up

Each party will provide commercially-reasonable cooperation with the other party in completing the wrap-up of the SOW.

25.6. Services: SOW Termination for Material Breach

  1. Either party may terminate a statement of work for an uncured material breach by the other party in accordance with Protocol 18.6.
  2. Unless clearly agreed otherwise, the right to terminate of a statement of work for material breach is in addition to any other recourse available to the terminating party under the Con­tract, the SOW, or the law — but subject to any agreed limitations of liability.
Note

Possible override language: See Option 25.18 (no suspension of services), which the Customer might want if the Vendor is providing mission-critical services for the Customer's business.

Subdivision 2 is a guardrail against a Vendor's trying to argue to the contrary.

25.6.1. Option: No Confidentiality Obligations

For the avoidance of doubt: Neither party has any confidentiality obligations relating to the services unless clearly stated in the Con­tract, the BSOW, and/or the applicable law.

Note

This is likely to be overkill for many services agreements.

25.6.2. Option: Confidentiality Obligations

When this Option is agreed to, each party must preserve in confidence the confidential information of the other party in accordance with Protocol 5.3.

25.6.3. Option: Post-Termination Confidentiality Obligations

In case of doubt: Upon any termination or expiration of a statement of work, each party will continue to honor any agreed confidentiality obligations.

Note

This is a comfort clause sometimes wanted by parties that expect to disclose confidential information.

25.6.4. Option: Expiration as a Form of Termination

For purposes of post-termination obligations, expiration of a statement of work will be considered a form of termination.

Note

See also § 18.9.1.3 (expiration counts as a type of termination).

25.7. Services: Substantial Completion Definition

25.7.1. Definition

  1. This Protocol applies in connection with a statement of work for services (see § 25.4).
  2. The term substantial completion has the meaning stated in the Code of Federal Regulations ("CFR") at 48 C.F.R. § 552.211-70(a)(2) and (a)(3), as in effect at the time that the Con­tract or the relevant statement of work is agreed to.
  3. In that CFR definition of substantial completion, the term "Government" is to be read as referring to Customer, and "Contractor" as referring to the Vendor
Note

().  Subdivision 2: The cited Code of Federal Regulations definition states:

(2) There may be different completion dates required for different phases or portions of the work, as established in the contract.

However, the work shall be deemed 'substantially complete' if and only if the Contractor has completed the work and related contract obligations[:]

  • in accordance with the contract documents,
  • such that the Government may enjoy the intended access, occupancy, possession, and use of the entire work[,]
  • without impairment due to incomplete or deficient work, and
  • without interference from the Contractor's completion of remaining work or correction of deficiencies in completed work.

(3) In no event shall the work be deemed 'substantially complete' if all fire and life safety systems are not tested and accepted by the authority having jurisdiction, where such acceptance is required under the contract."

(Emphasis and bullets added.)

For a more-detailed discussion, see generally Alex Benarroche, Substantial Completion in Construction: Why It Matters (2020).

25.8. Services: Workmanlike Definition

25.8.1. Pragmatic meaning

  1. The term "workmanlike," whether or not capitalized, refers to work that successful practitioners would judge as competent, skilled, and indicating proficiency, but not necessarily innovative, exceptional, or outstanding.
  2. The term "good and workmanlike" has the same meaning.
Note

().  This definition looks to the real world of successful practice in the field in question to serve as a yardstick (or meter stick).

The term "proficient" could be thought of as "competent and skilled but not necessarily innovative or outstanding."

  • An online dictionary published by from Cambridge University Press, defines proficient as "skilled and experienced" (dictionary.cambridge.org).
  • From dictionary.com: Proficient means "well-advanced or competent in any art, science, or subject; skilled" (dictionary.com).
  • Merriam-Webster goes further, however, defining proficent as "able to do something to a higher than average standard : SKILLED" (merriam-webster.com).

25.8.2. Additional notes

25.8.2.1. The business context

Some services agreements require the service provider to ensure that the agreed work is performed in a "workmanlike manner" or "good and workmanlike manner." To many readers, however, those terms might be unknown or at best only vaguely familiar. And in a contract-related lawsuit, it could be important for the term to have as precise a definition as practicable.

25.8.2.2. Language origin

This Definition is adapted from one announced by the Supreme Court of Texas in Melody Home Manufacturing (1987): "We define good and workmanlike as that quality of work [i] performed by one who has the knowledge, training, or experience necessary for the successful practice of a trade or occupation and [ii] performed in a manner generally considered proficient by those capable of judging such work." Melody Home Mfg. Co. v. Barnes, 741 S.W.2d 349, 354 (Tex. 1987) (cleaned up), quoted in Ewing Constr. Co. v. Amerisure Ins. Co., 420 S.W.3d 30, 37 (Tex. 2014) (responding to certified question from Fifth Circuit).

25.8.2.3. Similar: "Good Industry Practices"

The LawInsider.com site has a collection of definitions of Good Industry Practice:

Here's one (slightly reformatted):

Good Industry Practices means[:]

  • the practices that would be adopted by,
  • and the exercise of that degree of care, skill, diligence, prudence and foresight
  • that reasonably would be expected from,
  • a competent contractor in the international oil and gas industry
  • experienced in performing work
    • similar in nature, size, scope and complexity to the Work
    • and under conditions comparable to those applicable to the Work,
  • where such work is subject to,
    • and such contractor is seeking to comply with,
    • the standards and codes specified in the Contract
    • or (to the extent that they are not so specified) such national or international standards and codes as are most applicable in the circumstances,
    • and the applicable Law.
25.8.2.4. Would summary judgment be available?

Any given dispute about whether work was performed to a workmanlike standard might require costly proceedings — for example, expert testimony, with written expert reports and perhaps depositions — about some or all of the following issues:

•  What is the relevant trade or occupation?

•  What constitutes "successful" practice of that trade or occupation?

•  Just how much knowledge, training, or experience is required for successful practice?

•  What kind of work regarded as "proficient" by people who have those qualifications? See generally Fed. R. Evid. 702 (opinion testimony from expert witnesses).

This means that if the parties' respective experts had not-unreasonable disagreements about any of the above questions — highly likely — then a summary judgment, based on undisputed material facts, would likely be unavailable, and a trial, possibly to a jury would be necessary. See, e.g., Fed. R. Civ. P. 56 (summary judgment).

25.8.2.5. Pro tip: Adding specific, measurable metrics can help – a lot

So: Contract drafters having an eye to possible future disputes would be well-advised to include a reasonable set of measurable metrics, the accomplishment of which would (ideally) not be subject to dispute. Example: The painting contractor either did, or did not, put down two coats of Pantone 17-5104 Ultimate Gray paint and clean up all spills.

Caution: It's possible to get overly-specific and thus delay negotiation — or worse, to be overly-specific about things that the parties aren't quite sure of just yet and thus might have to spend time changing later.

25.9. Option: Customer Further Development of Deliverables

  1. If this Option is included in the Con­tract, it will apply whenever the Vendor will be furnishing one or more deliverables to the Customer.
  2. The Vendor will not assert any intellectual-property right in an attempt to prevent the Customer from doing any of the following when the Customer does so in accordance with the Con­tract:
    1. modifying or otherwise continuing development of any deliverable; and/or
    2. having the same done by others on behalf of the Customer.
  3. But: Whether the Vendor is required to provide support for its deliverable, after someone else has modified it, is up to the Vendor's sole discretion.
  4. The Customer will see it that any deliverable-related modification- or development activity under this Option, by the Customer or on the Customer's behalf, does not violate:
    1. applicable law such as (without limitation) export-controls laws;
    2. any unrelated rights assertable by the Vendor such as (without limitation), intellectual-property rights, if any;
    3. any applicable third-party rights, e.g., patent rights or copyrights; nor
    4. any additional restrictions unambiguously agreed to in writing.
Note

().  Subdivision 2: If the Customer hires the Vendor to build something, the Customer generally won't want to be forever locked into using the same Vendor to improve- or build on it. But: The Customer's further development might violate the Vendor's intellectual-property rights, e.g., if building on the Vendor's work product constitutes creating a "derivative work" of a copyrighted work of authorship created by the Vendor.

Subdivision 2 does not state that the Customer's further development is "authorized," because further development might be affected by other restrictions, e.g., third-party IP rights and/or government regulation. (See the commentary at 12.2.)

Subdivision 3 addresses the (likely) Vendor concerns that:

  1. the Vendor doesn't want to take responsibility for fixing other developers' screw-ups;
  2. the Vendor might prefer that it be paid for futher development; and
  3. the Vendor likely wouldn't want its trade secrets and other confidential information revealed to possible competitors.

25.10. Option: Customer Ownership of IP

  1. If this Option is agreed to in writing, THEN: As between the Customer and the Vendor, it is the Customer, not the Vendor, that will own the intellectual-property rights, if any, in and to any deliverables that are created:
    • in the performance of the Vendor's obligations under a statement of work,
    • by one or more employees of the Vendor (and/or of the Vendor's subcontractors, if any).
  2. The Vendor will timely disclose to the Customer all technology and other intellectual property to be owned by the Customer under the statement of work; each such disclosure is to be:

    1. in writing, and
    2. in as much detail as the Customer reasonably requests,

    so that the Customer becomes aware that it is entitled to ownership of specific Vendor work product and determine what if any legal protection might be available.

  3. If so requested by the Customer, the parties will follow Protocol 23.6 to help establish, confirm, and/or register the Customer's ownership claim(s) under this Protocol.

().  Concerning IP ownership resulting from the services (and its economics), see generally 25.4.11.

Subdivision 2 addresses the fact that it's not entirely unheard of for a Vendor employee or contractor: • to have an idea for an innovation; • to be required, by contract or by law, to assign the idea to the employer or Customer; but • to withhold the idea anyway, in the hope of developing and commercializing it.

25.11. Option: Customer Scope-Reduction Right

  1. If this Option is agreed to, THEN: The Customer has the right, in its sole discretion, to reduce the extent of the work required under any statement of work (sometimes referred to as "de-scoping" of the work).
  2. In case of doubt: The Customer's de-scoping right extends, without limitation, to reassigning work to a service provider other than the Vendor, for any reason or no reason.
  3. For any work item being de-scoped by the Customer under this Protocol:
    1. If the statement of work sets out itemized compensation for that work item, then the Vendor's compensation will be reduced by that itemized amount.
    2. Otherwise, the Vendor's compensation will be reduced equitably, with any persistent disagreements being addressed by (non-binding) escalation to a neutral advisor in accordance with Protocol 21.11.
Note

().  Construction contracts sometimes address whether the owner, or the prime contractor, can remove contracted work from a contractor or subcontractor and either reassign the work to another party or simply do the work itself. See Julian Bailey, Michael Turrini, and Mark Sanders, Descoping of works: what is the employer entitled to do? (WhiteCase.com 2017), archived at https://perma.cc/29BS-C9G6. See generally, e.g., Frederic Akiki and Julian Bailey, Descoping: Can the omission of works constitute a breach of contract? (JDSupra 2020).

This Option follows the guideline, "If you can't agree in advance about outcome, then try to agree about process," in this case the process being escalation.

Appendix: See the Honeywell change-order language reproduced at 13.9.12.7 for an example of Customer-drafted terms that give the Customer considerable authority to impose change orders on the Vendor.

25.12. Option: Customer Termination at Will

  1. If this Option is agreed to in writing, THEN: The Customer may terminate a statement of work at will — that is, in the Customer's sole and unfettered discretion — effective immediately upon written notice to the Vendor.
  2. If the Customer does terminate a statement of work at will, then:
    1. the Customer will be conclusively deemed to have complied with any applicable standard of reasonableness or good faith; and
    2. each party will comply with Protocol 25.5 (services termination general provisions).
  3. In case of doubt, this Option neither authorizes nor prohibits termination of a statement of work at will by the Vendor.
  4. If used in a termination provision in the Con­tract or a statement of work, the term "for convenience" has the same meaning as "at will."
Note

().  Caution: Sometimes, a services Customer will want the right to terminate a statement of work "at will" or "for convenience." For many situations, that might be entirely sensible — but it could cause problems for the Vendor in the form of unrecoverable costs (past and/or future), as discussed at 18.2.3.2.

The Customer probably won't want the Vendor to have the right to terminate at will, because that could leave the Customer in the lurch in an emergency or other important situation. Example: In November 2025, financial giant Fidelity Investments sued Broadcom — the parties later settled the case — for "threatening to cut ​off [Fidelity's] access to [Broadcom] software that had become central to ‌the financial firm's systems, creating a risk of outages and trading disruptions."

25.13. Option: Withholding of Post-Termination Payments

If this Option is agreed to, THEN: Upon termination of a statement of work, the Customer need not pay the Vendor's final invoice(s) for then-unbilled services, if any, until the Vendor has complied with its applicable post-termination obligations for that statement of work, if any.

Note

Some customers might want this Protocol to give them more leverage in a termination situation.

25.14. Option: Customer's Additional Permit Responsibilities

If this Option is agreed to, THEN: The Customer must obtain the following "specialty" authorizations for the services: [LIST].

Note

Some types of work might need specialty permits or licenses — as a made-up example, suppose that: • the Vendor is to paint a room, but • the room is part of the intensive-care unit at a hospital, and • in the particular jurisdiction, that type of painting work requires a special authorization from health authorities. (Again, this is just a made-up example.) In that situation, the parties might want to negotiate who should obtain those particular permits and licenses. Additional reading: Benjamin Criswell and Tim McMahan, Drafting Real Estate Documents With Project Permitting in Mind (JDSupra.com 2024).

25.15. Option: Final-Payment Adjustment for Material Breach

  1. This Option will apply if the Customer terminates a statement of work for material breach by the Vendor.
  2. The Customer's final payment obligation will be appropriately adjusted, based on the circumstances.
  3. The parties will address any disagreement about such an adjustment by escalation as stated at Protocol 21.11.
Note

It's not uncommon for services projects to end badly, with customers demanding "adjustment" to the money paid and/or owed; for examples, see the commentary at Protocol 25.4.13.

25.16. Option: No Charge for Deliverables Use

If this Option is agreed to, the Vendor will not ask for payment from the Customer for the Customer's use of a deliverable resulting from services under the Con­tract.

Note

If the Customer is a "nervous Nellie," the Customer might want language like the above, so as to be absolutely certain that the Vendor wouldn't try to charge the Customer more than agreed.

25.17. Option: No Deliverables Use by Others

If this Option is agreed to, THEN: The Customer will not allow others (including without limitation the Customer's other contractors) to use deliverables provided by or on behalf of the Vendor under a statement of work — not even if such use by others is for the Customer's own business purposes.

Note

In one type of services project, the Vendor is a software developer, where the Vendor creates a custom version of the Vendor's own software package for a particular Customer, and the Vendor retains the ownership rights in the custom version. In such a situation, the Vendor might well want to preclude the Customer from allowing third parties to use the software, for economic reasons and/or to preserve the Vendor's trade-secret rights in the software.

25.18. Option: No Vendor Withholding of Services

If this Option is agreed to, THEN:

  1. The Vendor acknowleges the importance to the Customer of timely uninterrupted services under the Con­tract.
  2. The Vendor does not not suspend providing those services — even for nonpayment or other material breach by the Customer — without giving the Customer at least ten business days' prior written notice in accordance with Protocol 3.14.
Note

().  Subdivision 1: The prefatory "importance" language is included to educate and persuade future readers — such as party executives and, possibly, judges and jurors — about the Customer's concern. Such language can be very helpful for that situation, as noted in the Tenth Circuit's 2016 SOLIDFX v. Jeppesen Sanderson Inc. case discussed at 21.18.5.

Sean Hogle suggests that if a customer insists on including a continuation-of-services provision along these lines, the vendor should try to include time limits "so that the vendor is not stuck indefinitely providing goods or services for free."

Example: In November 2025, financial giant Fidelity Investments sued Broadcom — the parties later settled the case — for "threatening to cut ​off [Fidelity's] access to [Broadcom] software that had become central to ‌the financial firm's systems, creating a risk of outages and trading disruptions."

25.19. Option: Customer-Requested Personnel Changes

  1. If this Option is agreed to, THEN: Except as provided in subdivision 2: Whenever the Customer reasonably requests it, the Vendor will remove and replace any individual under the Vendor's control from performing services under the Con­tract.
  2. The Vendor need not do so if the removal would be unlawful in the United States and/or at the relevant location (e.g., unlawfully-discriminatory or -retaliatory reasons).
  3. Apart from the good-cause exception in subdivision 4 below, the Vendor may bill the Customer for all time and out-of-pocket expenses needed to bring a replacement up to speed when an individual is removed at the Customer's request under this Option, at the regular agreed rate or rates specified in the relevant statement of work.
  4. Exception: The Vendor will not bill for such time or expenses if the Customer's removal request was for good cause; if the parties disagree about whether good cause exists, THEN: The parties will address the disagreement by escalation as stated at 21.11.
  5. If any such removed individual complains — or sues the Vendor, in any forum, alleging — that the removal was unlawful, THEN:
    1. The Customer will defend and indemnify the Vendor and the Vendor's Protected Group against the claim; and
    2. The Customer will not assert that, by complying with the Customer's removal request, the Vendor (i) agreed that the removal was lawful, nor (ii) waived the Customer's defense- and indemnity obligations under this Protocol.
Note

().  Customers' service-agreement forms often include language giving the Customer the right to demand that the service provider kick someone off a project.

Subdivision 2 – caution: It's not unheard-of for a bad-actor Customer representative to demand that a Vendor-employee be kicked off a project, for example — • because the Customer representative was biased against people of the Vendor-employee's race, ethnicity, etc.; or • to retaliate against the Vendor-employee for rebuffing sexual advances.

Subdivision 4: Whether "good cause" exists is sometimes disputed. Example: A contractor's repeated safety violations led the customer to ask that the contractor's site manager be replaced. The contractor did replace its site manager, but the customer eventually terminated the contract because of the safety problems and successfully sued the contractor for damages. See James Constr. Gp. v. Westlake Chem. Corp., 594 S.W.3d 722, 749 (Tex. App.—Houston [14th Dist.] 2019) (affirming judgment on jury verdict awarding damages to customer in suit against contractor), aff'd in pertinent part, 650 S.W.3d 392, 415 (Tex. 2022).

25.20. Option: Stipulated Vendor Material Breaches

  1. If this Option is agreed to, THEN: Any of the following breaches by the Vendor — if proved — would be "material" for purposes of the Con­tract:
    1. The Vendor does not timely start to perform the services, if: (i) the parties have clearly agreed in writing that a specific start time is important, and (ii) the Customer terminates the statement of work before the Vendor does start performance.
    2. The Vendor clearly and permanently abandons performance.
    3. The Vendor temporarily suspends performance, if the Con­tract or the statement of work prohibits suspension.
    4. The Vendor does not timely complete the services, in compliance with the standards set forth in the Con­tract and/or the statement of work, if the parties have clearly agreed in writing that timeliness of completion is important.
  2. For the avoidance of doubt, this Option does not rule out the possibility that other types of breach by the Vendor might also be material.
Note

As discussed in more detail at section 18.6.1.5, courts generally go along with contractual stipulations that particular breaches are to be considered "material."

25.21. Option: Vendor Availability for Meetings

  1. If this Option is agreed to, THEN: The Vendor will make itself reasonably available from time to time for meetings and phone calls concerning the services as reasonably requested by the Customer.
  2. In case of doubt: The Vendor’s participation in any such meetings will be "on the clock," that is, billable at the regular rate or rates agreed to for the services in question.
Note

This is set up as an option, and not a rule, because the Vendor will often have an economic incentive to make itself available to the Customer — but that won't always be the case, because the Customer's business could be less important to the Vendor than that of the Vendor's other customers.

25.22. Option: Vendor Background Checks

  1. If this Option is agreed to, it will apply whenever, in connection with a statement of work:
    1. an individual is employed by the Vendor (and/or the Vendor's subcontractors, if applicable); and
    2. the invidual will have access to (i) the Customer's physical premises and/or (ii) the Customer's computer system(s).
  2. The Vendor will see to it that the individual — before gaining such access — has had a background check completed, with satisfactory results, in accordance with Protocol 17.5.
  3. To help avoid out-of-date background information, each background check under this Option is to have been completed no earlier than two years before the latest date on which the relevant statement of work was agreed to by all parties.
Note

().  In potentially-sensitive situations like this, the Customer might want to require background checks on the relevant Vendor personnel. (See also the background-checks protocol at Protocol 17.5 and its commentary.)

Subdivision 3: Depending on the circumstances, this two-year time frame might be a subject for discussion by the parties.

25.23. Option: Vendor Confidentiality Obligations

If this Option is agreed to: The Vendor will preserve the Customer's confidential information in confidence in accordance with Protocol 5.3.

Note

In some services agreements, the Vendor might gain access to: • confidential information of the Customer itself; • confidential information of the Customer's own customers; and/or • personal information that's legally protected under applicable privacy law. But: On the other side of the coin, in some services agreements, the Customer might gain access to confidential information of the Vendor, e.g., in the form of the Vendor's proprietary computer software or data.

25.24. Option: Vendor Mitigation of Schedule Slips

  1. If this Option is agreed to, it will apply if:
    1. a statement of work clearly states that a particular milestone: (i) is material, and (ii) must be completed by a specified date; and
    2. that milestone is not completed by the specified date.
  2. The Vendor will make efforts that are reasonable under the circumstances:
    1. to mitigate any harm resulting from the delay; and
    2. to get the work back on schedule.
Note

().  In some fields (e.g., software development), it's pretty difficult for a service provider to accurately estimate how long a project will take. That, in turn, means that schedule slips are not uncommon. It's never a bad idea for contract drafters to try to plan around this reality; consequently, drafters might want to consider language such as this option.

Subdivision 2 does not require "best efforts," for reasons discussed in the commentary at Protocol 9.1.

25.25. Option: Vendor Withholding of Final Deliveries

If this Option is agreed to, AND: The Vendor's already-sent invoices — for any statement of work — are past due when any statement of work is terminated, THEN: The Vendor may delay delivery of some or all post-termination deliverables, for some or all statements of work, until all of the Vendor's past-due invoices are paid in full.

Note

This gives the Vendor at least a bit of ammunition with which to respond if the Customer were to decide to withhold payment as a means of increasing its termination leverage.

26. Index

26.1. Index of protocols

[A work in progress]

A     B     C     D     E

F     G     H     I     J

L     M     N     O     P

R     S     T     U     V-W

26.1.1. Index: A

  • Acceleration of Payment Protocol (4.1)
  • Acknowledgements Protocol (11.2)
  • Advance Payment Demands Protocol (4.2)
  • Affiliate Definition (20.1)
  • Amendments by Notice Protocol (15.1)
  • Amendments in Writing Protocol (3.1)
  • Arbitration Protocol (21.1)
  • Archive Copy Retention (5.1)
  • As-Is Protocol (20.5)
  • Assignee Reasonable Assurance (15.2)
  • Assignment Consent Protocol (15.3)
  • Assurance of Performance (15.4)
  • Attorney Fees Protocol (21.2)
  • Audit Protocol (4.3)

26.1.2. Index: B

  • Background Checks (17.5)
  • Backup Payment Source Protocol (4.4)
  • Best Efforts Definition (9.1)
  • Blue-Pencil Protocol (21.3)
  • Board Definition Definition (board of directors) (20.6)
  • Bond Waiver Protocol (21.4)
  • Business Associate Agreement (5.2)

26.1.3. Index: C

  • Catch-Up Calls Protocol (3.2)
  • Certifications Definition (11.3)
  • Claim Definition (20.10)
  • Clear and Convincing Evidence Definition (20.11)
  • Clearly Agreed Definition (20.12)
  • Code of Conduct Compliance Protocol (9.5)
  • Commercially-Reasonable Efforts Definition (9.2)
  • Computer-System Access (9.4)
  • Confidential Information Protocol (5.3)
  • Consent Requests Protocol (12.2)
  • Consequential Damages Exclusion Protocol (21.5)
  • Consider Definition (20.13)
  • Consumer Price Index (CPI) Definition (6.1)
  • Contra Proferentem Waiver Protocol (11.4)
  • Contract RPM Adoption Protocol (10)
  • Contract-Related Claim Definition (20.14)
  • Contrary Positions Protocol (10.2)
  • Cooperation Definition (9.3)
  • Corroborating Evidence Definition (21.6)

26.1.4. Index: D

  • Damages Caps General Provisions Protocol (21.7)
  • Defect Correction Protocol (13.13)
  • Defense against Claims Protocol (14.1)
  • Definitions & other meanings: Miscellaneous (20)
  • Deliverable Definition (20.17)
  • Deposits Protocol (4.5)
  • Discretion Definition (9.6)
  • Disparagement Prohibition (22.1)
  • Drawbacks Protocol (4.6)

26.1.5. Index: E

  • Effective Date Protocol (20.18)
  • Employee Protection Protocol (17.6)
  • Employees' Non-Waivable Rights (17.7)
  • Encouraged Definition (20.19)
  • Entire Agreement Protocol (3.3)
  • Equitable Relief Disclaimer Protocol (21.9)
  • Equitable Relief Stipulation Protocol (21.10)
  • Escalation (Internal) Protocol (3.4)
  • Escalation to Neutral Advisor Protocol (21.11)
  • Evergreen Renewals Protocol (15.5)
  • Examples Definition (20.21)
  • Exclusivity Explicitness Protocol (3.5)
  • Expense Reimbursement Protocol (4.7)

26.1.6. Index: F

  • Force Majeure Protocol (14.2)
  • Forum Selection Protocol (21.12)
  • Fraud Proof Protocol (21.13)

26.1.7. Index: G

  • Good Faith Definition (9.7)
  • Governing Law Protocol (21.14)
  • Government Authority Definition (20.23)
  • Government Subcontract Disclaimer Protocol (3.6)
  • Gross Negligence Definition (21.15)
  • Guaranties Protocol (4.8)

26.1.8. Index: H

  • Hold Harmless Definition (20.24)

26.1.9. Index: I

  • Implied-Warranties Disclaimer (16.1)
  • Including Definition (20.25)
  • Incorporation by Reference Protocol (3.7)
  • Indemnity Protocol (14.3)
  • Independent-Contractors Protocol (3.8)
  • Information Purge Protocol (5.4)
  • Inspections (9.8)
  • Interest Charges Protocol (4.9)
  • Invoices Protocol (4.10)
  • IP Definitions (23.3)
  • IP Infringement by Others (23.4)
  • IP Ownership (23.6)
  • IP Rights Challenges (23.7)
  • IP Infringement Warranty (23.5)

26.1.10. Index: J

  • Jury Trial Waiver Protocol (21.16)

26.1.11. Index: L

  • Lawyer Involvement Protocol (3.9)
  • Letter of Intent Protocol (3.11)
  • Limitation-Shortening Protocol (21.17)
  • Limitations of Liability General Provisions Protocol (21.18)

26.1.12. Index: M

  • Material-Problems Disclosure (3.12)

26.1.13. Index: N

  • No-Shop (22.4)
  • Noncompetition (22.5)
  • Nonsolicitation of Employees (17.9)
  • Notices Protocol (3.14)

26.1.14. Index: O

  • Offsets Protocol (4.13.5)
  • Order Fulfillment Protocol (13.8)

26.1.15. Index: P

  • Past Dealings Disclaimer Protocol (11.6)
  • Pay When Paid / Pay If Paid Protocol (4.11)
  • Payment Disputes Protocol (4.12)
  • Payment Due Date Protocol (4.13)
  • People Definition (17.8)
  • Performance Improvement Plan Protocol (15.6)
  • Possession, Custody, or Control Definition (20.30)
  • Pricing Adjustments Protocol (6.2)
  • Privacy Commitment (by Customer) (5.5)
  • Privacy Law Definition [FIX] (5.6)
  • Professional Conduct (12.3)
  • Protected Group Definition (14.4)
  • Purchase Orders Protocol (13.9)

26.1.16. Index: R

  • Reasonable Definition (9.9)
  • Recklessness Definition (20.31)
  • Record (as noun) Definition (20.32)
  • Records Definition (noun) (20.32)
  • Referrals Protocol (13.10)
  • Relating to Definition (20.33)
  • Reliance Waiver Protocol (11.7)
  • Representation Definition Protocol (20.34)
  • Representations of Signing Parties Protocol (3.13)
  • Resale Protocol (13.11)
  • Resale: Software Supplement Protocol (13.11.30)
  • Responsible Definition (9.11)

26.1.17. Index: S

  • Sales-Channel Partnerships General Provisions (13.15)
  • Satisfactory Definition (9.12)
  • Service of Process Streamlining Protocol (21.20)
  • Services Charges and Billing Protocol (25.1)
  • Services Framework Protocol (25.4)
  • Services Licenses and Permits Protocol (25.2)
  • Services Performance Protocol (25.3)
  • Services Termination Protocol (25.5)
  • Services options: Customer playbook ([BROKEN LINK: serv-cust-pb])
  • Services options: Vendor playbook ([BROKEN LINK: serv-plbk-prov])
  • Settlement Discussion Admissibility Protocol (21.21)
  • Settlement Offer Rejection Protocol (21.22.3)
  • Shall Definition (20.35)
  • Shotgun Buy-Sell [to come] (31.41)
  • Should Definition (20.36)
  • Signature Document Integrity Protocol (3.15)
  • Signature Mechanics Protocol (3.16)
  • Site Visits Protocol (9.13)
  • Substantial Completion Definition (25.7)
  • Support Levels Definition (13.14.1)

26.1.18. Index: T

  • Tax Responsibilities Protocol (4.14)
  • Termination At Will Protocol (18.2)
  • Termination General Provisions (18.9)
  • Termination Prohibition (18.10)
  • Termination Wrap Up Protocol (18.11)
  • Termination for Change of Control Protocol (18.3)
  • Termination for Insolvency (18.4)
  • Termination for Legal Violation (18.5)
  • Termination for Material Breach (18.6)
  • Termination for Personnel Changes (18.7)
  • Termination for Reputation Risk (18.8)
  • Third-Party Beneficiaries Protocol (11.8)
  • Trademark License (23.2)

26.1.19. Index: U

  • Usury Savings Protocol (4.15)

26.1.20. Index: V

  • Vendor Quotations Protocol (13.12)

26.1.21. Index: W

  • Waivers in Writing Protocol (3.18)
  • Will (as "must") Definition (10.1.4)
  • Willful Definition (20.40)
  • Workmanlike Definition (25.8)
  • Writing-Requirement Challenge Protocol (10.5)

27. What-if planning (notes only)

[Note to my law students: You can just skim this chapter; you won't be tested on it, but you might find it useful in the future.]

If you don't know where you're going, you might not get there. – Yogi Berra.

Be Prepared. – Scout Motto.

Plans are worthless; planning is everything. – Dwight D. Eisenhower.

[N]o plan of operations extends with any certainty beyond the first contact with the main hostile force. – Helmuth von Moltke the Elder (often paraphrased as "no plan survives first contact with the enemy").

Contents:

27.1. Clients want their lawyers to think ahead

Clients expect their contracts to reflect some foresight about a reasonable set of what-if contingencies. They love it when their lawyers know the business as well as the law. And one of the big complaints clients have about lawyers (especially junior ones) is that "they just don't understand the business!"

But it seldom works for a client or senior lawyer to say: Learn the business, kid! Um: How, exactly?

Nor is it productive to add, Just ask questions! — because it might not be obvious what questions should be asked.

"Be a hitter, Johnny!" isn't helpful: Here's an analogy: In the 1990s, I helped coach my son's Little League baseball teams. In the early years of tee-ball played by six-year-olds, I'd sometimes hear a mom in the bleachers shouting "Be a hitter, Johnny!" when her little boy came up to bat. (And yes, and it was pretty much always moms doing this from the bleachers, not dads.)

But "be a hitter!" isn't actionable advice. What little Johnny really needs is to be coached in what to do: Hold the bat this way. Plant your feet that way. And so on.

With that in mind: This book tries to show chapter presents a series of questions, with handy mnemonic acronyms, to help contract professionals and their clients:

  • identify threats and opportunities that might need to be addressed in a contract;
  • develop action plans to prepare for and respond to those threats and opportunities; and
  • flesh out the details of the desired actions;

all with the goal of drafting practical contract clauses.

Example: Some years ago, late-night host Stephen Colbert — and his agent — showed that there's more to contract drafting than just putting words on the page. This was back when Colbert, as his "character," was hosting the Comedy Central show that made him famous, The Colbert Report.

When Colbert's contract with Comedy Central was up for renewal, he and his agent apparently negotiated to have successive contract terms expire at the same time as David Letterman's contracts with CBS. That way, if Letterman ever decided to retire, Colbert would be able to leave his existing show and throw his hat in the ring to take over Letterman's The Late Show on CBS. And of course that's just what happened: By prior planning, Colbert was able to seize an important opportunity, instead of remaining tied up by an existing contract. See Bill Carter, Colbert Will Host ‘Late Show,' Playing Himself for a Change, New York Times, Apr. 11, 2014, at A1.

27.2. Don't assume a can-opener

Assuming away problems (a.k.a. wishful thinking) can be dangerous. But some people are prone to it — including business people. Contract negotiators should keep this in mind in brainstorming scenarios and action plans.

Example: Where will the money come from? When drafting a critical contract obligation for the other side — for example, an indemnity obligation — consider imposing additional requirements to be sure that there's money somewhere to fund the obligation, such as:

  • an insurance policy;
  • a third-party guaranty;
  • a letter of credit from a bank or other financial institution;
  • or even taking a security interest in collateral that could be seized and sold to raise funds.

Apropos of wishful thinking, there's an old joke about economists that seems to have been first published in 1970:

  • A physicist, a chemist, and an economist are shipwrecked on a desert island. They have nothing to eat and get very hungry.
  • A pallet full of cans of food washes up on the beach. But our castaways have nothing to use to open the food cans.
  • The physicist and the chemist each propose ways of opening the cans: Dropping them from a coconut tree; heating them in a fire till they explode; and the like.
  • The economist has a simpler solution: "We'll assume we have a can opener." See Wikipedia, Assume a can opener, quoting Kenneth E. Boulding, Economics as a Science at 101 (McGraw-Hill 1970).

27.3. Incentives can matter. A lot.

Berkshire Hathaway's late vice-chairman Charles Munger famously said, "Never a year passes but I get some surprise that pushes a little further my appreciation of incentive superpower. * * * Never, ever, think about something else when you should be thinking about the power of incentives." Charles T. Munger, The Psychology of Human Misjudgment (fs.blog), archived at https://perma.cc/LNG7-JG6Y.

When drafting a contract, it can pay dividends to give some thought to how to manage the so-called "agency costs" that can arise from these personal interests and incentives of individual players. That's because when disputes arise, the involved individuals will naturally want to protect their own interests, such as: • not having fingers pointed at them; • being thought of by their side as a committed team player who's willing to fight to win, not a defeatist who throws in the towel; • protecting their bonus, their commission, their pay raise, their promotion, etc. See generally Agency cost (Wikipedia.org); a somewhat more-readable presentation is at Agency Costs (Investopedia.com).

These desires can manifest themselves in a variety of ways; a skilled contract drafter will try to help the client channel these incentives — on both sides — and manage individuals' expectations and incentives.

27.4. T O P   S P I N    S N O T S:  Identifying threats and opportunities

The acronym T O P   S P I N can help planners to identify threats and opportunities of potential interest. (The acronym is inspired by the business concept of SWOT analysis, standing for Strengths, Weaknesses, Opportunities, and Threats.)

The first part of the acronym, T O P, refers to the threats and opportunities that can arise in the course of the different phases of the parties' business relationship — those phases can themselves be remembered with the acronym S N O T S: Startup; Normal Operations; Trouble; and Shutdown.

The second part of the acronym, S P I N, reminds us that various threats and opportunities can be presented by one or more of the following:

• S: The participants in the respective supply chains in which the contracting parties participate, both as suppliers and as customers, direct and indirect. If the parties are "Alice" and "Bob," then we can think of Alice's and Bob's respective supply chains as forming a capital letter H, as illustrated below.

A block capital letter H with the word "Contract" in the center, "Alice" and "Bob" in the left-center and right-center of the H; on each of the vertical arms of the H,  "Supplier," "Supplier's supplier," "Customer's customer"; outside of each vertical arm of the H, the words "Interveners" and "Nature"

• P: The individual people involved in the supply chains — all of whom have their own personal motivations and interests.

• I: Interveners such as competitors; alliance partners; unions; governmental actors such as elected officials, regulators, taxing authorities, and law enforcement; the press; and acquirers. Don't forget the individual people associated with an intervener, all of whom will have personal desires, motives, and interests.

• N: Nature, which can cause all kinds of threats and opportunities to arise in a contract relationship. Example: As of this writing, Google Scholar shows more than 500 reported court opinions involving force-majeure issues and the COVID-19 pandemic. (See generally the LCP26 force-majeure clause at 14.2.)

27.5. I N D I A   T I L T: Deciding on responsive actions

Once planners have compiled a list of threats and opportunities of interest, they should think about the specific actions that might be desirable — or perhaps specific actions to be prohibited ­— when a particular threat or opportunity appears to be arising. Many such actions will fall into the following categories:

• I: Information to gather about the situation in question;

• N: Notification of others that the threat or opportunity is (or might be) arising. Refer to the SPIN part of the TOP SPIN acronym above for suggestions about players who might be appropriate to notify.

• D:  Diagnosis, i.e., confirmation that the particular threat or opportunity is real, as opposed to being an example of some other phenomenon (or just a false alarm).

• I: Immediate action, e.g., to mitigate the threat or to seize the opportunity.

• A: Additional actions, e.g., to remediate adverse effects or take advantage of the opportunity.

ICE-CREAM EXAMPLE:  Consumers have been known to become ill, and a few have died, after eating ice cream that, during manufacturing, became contaminated with listeria bacteria. The grocery store's planners might want to use the I N D I A checklist to specify in some detail how the ice-cream manufacturer is to respond to such reports, with requirements for notifying the grocery store; product recalls; and so on.

Some plans are likely to require advance preparation. Planners can use the T I L T part of the acronym to decide whether any of the following might be appropriate:

• T:  Acquisition of tools — such as equipment, information, consumables, etc. — for responding to the threat or opportunity.

• I:  Acquisition of insurance (or other backup sources of funding).

• L: Posting of a lookout, that is, putting in place a monitoring system to detect the threat or opportunity in question.

• T:  Training of the people and organizations who might be called on to respond to the threat or opportunity.

27.6. W H A L E R analysis: Fleshing out the action plans

In specifying actions to be taken, planners will often want to go into more detail than just the traditional 5W + H acronym (standing for Who, What, When, Where, Why, and How). Planners can do this using the acronym W H A L E R:

• W:  Who is to take (or might take, or must not take) the action.

• H:  How the action is to be taken, e.g., in accordance with a specified industry standard.

• A:  Autonomy of the actor in deciding whether to take or not take the action.  Depending on the circumstances, this might be:

  • No autonomy:  The action in question is either mandatory or prohibited, with nothing in between.
  • Total autonomy:  For the action in question, the specified actor has sole and unfettered discretion as to whether to take the action.
  • Partial autonomy:  The decision to take (or not take) the action must meet one or more requirements such as:
    • Reasonableness — be careful: that can be complicated and expensive to litigate;
    • Good faith — ditto;
    • Notification of some other player, before the fact and/or after the fact;
    • Consultation with some other player before the fact; or
    • Consent of some other player (but is consent not to be unreasonably withheld?  A claim of unreasonable withholding of consent could itself be one more thing to litigate.)

• L:  Limitations on the action — for example, minimums or maximums as to one or more of time; place; manner; money; and people.

• E:  Economics of the action, such as required payment actions (each of which can get its own W H A L E R analysis), and backup funding sources.

• R:  Recordkeeping concerning the action in question (with its own W H A L E R analysis).

27.7. The "bow tie method": A diagrammatic approach

A more-complicated approach to identifying and planning for risks is the so-called "bow tie" method, developed by oil-and-gas giant Shell and later adopted in other industries. See, e.g., the detailed explanation (with examples) in Julian Talbot, Risk BowTie Method (JulianTalbot.com 2020), archived at https://perma.cc/ATN7-FGAU; see also the Hacker News discussion at https://news.ycombinator.com/item?id=24130809.

The bowtie method of diagramming risks and consequences is reminiscent of Feynman diagrams in the world of physics. See generally, e.g., Frank Wilczek, How Feynman Diagrams Almost Saved Space (QuantaMagazine.org 2016). (Wilczek is a Nobel Prize-winning physicist and MacArthur Foundation "genius grant" recipient who was once a colleague of Richard Feynman.)

27.8. Finally, ask the investigator's all-round favorite question

When I was a junior lawyer at Arnold, White & Durkee, I worked a lot with partner Mike Sutton. One of the many things Mike taught me was that when interviewing or deposing a witness, a useful, all-purpose question consists of just two words:  Anything else?

That same question can likewise help contract planners get some comfort that they've covered the possibilities that should be addressed in a draft agreement.

(For the Jeopardy! game at the end of the semester: this is the answer to "What is Professor Toedt's favorite two-word question?" We'll see who has read this far ….)

28. Contract formats & styles

28.1. Traditional contract styles

Contracts can be found in various traditional styles. For example:

•  Lots of contracts are simple lists of numbered paragraphs. Example: Here's a short-and-sweet confidentiality agreement; this is an annotated version of a contract that I reviewed for a client, with redlining and comment bubbles.

•  Merger & acquisition agreements are among the longer ones you'll see, with "Article" and "Section" headings. Example: See, e.g., the "Agreement and Plan of Merger" (that's the customary title for such contracts) under which Nippon Steel was to acquire U.S. Steel until the Biden Administration blocked the transaction — but then the Trump Administration allowed the merger to go forward with the United States receiving a "golden share."

•  Somewhere in the middle, complexity-wise, are online agreements such as that for customers of Amazon Web Services.

28.2. Letter agreements

Letter agreements can be useful as binding contracts because they're (often) simpler yet still get the job done. That can sometimes be appealing to business people, who aren't fond of spending time negotiating traditional contract language.

Employment agreements are often done as offer letters; see, e.g., Sheryl Sandberg's employment agreement at Facebook. (Students: We'll be studying portions of this agreement during the semester.) Likewise was the 2006 letter agreement for consulting services between Ford Motor Company and British financial wizard Sir John Bond; it consisted of an introduction, six bullet points, and a closing.

A four-sentence NDA letter agreement: In the early 1980s I was a fairly-new associate at Arnold, White & Durkee, then one of the largest IP-litigation firms in the United States. One day, Tom Arnold, the senior name partner, assigned me to draft a confidentiality agreement (commonly known as a "nondisclosure agreement, or "NDA") for a friend of his, "Bill," who was going to be disclosing a business plan to Bill’s friend "Jim."

Tom always thought in practical terms, aiming to figure out the best, most cost-effective way to achieve what the client really needed and wanted. Probably not coincidentally, during World War II Tom had served as a Navy officer aboard a battleship and an aircraft carrier — a role in which real-world pragmatism is prized.

For this NDA project, Tom instructed me not to draft a conventional contract for his friend. Instead, the NDA was to take the form of a short letter. I don't remember exactly what my draft said, but it was along approximately the following lines:

Dear Jim,

This confirms that I will be telling you about my plans to go into business [raising tribbles, let's say] so that you can evaluate whether you want to invest in the business with me.

You agree that unless I say it's OK, you won’t disclose what I tell you about my plans to anyone else, and you won’t use that information yourself for any other purpose.

You won't be under this obligation, though, to the extent that the information in question has become public, or if you get the information from another legitimate source.

If this is agreeable, please countersign the enclosed copy of this letter and return it to me. I look forward to our working together.

Sincerely yours,

Bill

When I’d prepared a draft, I showed it to Tom and asked him, um, isn’t this pretty sparse? Tom agreed that yes, it was sparse — but:

  • The signed letter would be a binding, enforceable contract: Bill could use the letter to go to court — and get to a jury — if his friend Jim breached it, which both Bill and Tom judged to be a very low risk.
  • Equally important to Bill: Jim would probably sign the letter immediately because as an experienced businessman, Jim would quickly recognize the letter as a reasonable NDA — plus, he had reason to trust that his friend Bill wouldn't try to take advantage of him.
  • On the other hand, if Bill had asked Jim to sign a conventionally-drafted confidentiality agreement, full of typical legalese, then Jim likely would have asked his lawyer to review the agreement, "just to be on the safe side, y'know?"
  • And if Jim's lawyer had gotten involved, that would have delayed things — not just by the amount of time it took Jim's lawyer to review the agreement, but for the parties to negotiate any changes that Jim's lawyer might have requested, because lawyers so often spot things that supposedly "need" changing ….

That early experience was an eye-opener: It showed that contracts aren’t magical written incantations — they’re just simple statements of simple things.

The experience was also a lesson in a fundamental truth: Business clients are often far more interested in being able to sign an "OK" contract ASAP — accepting that it will entail what they judge to be an acceptable business risk — than they are in signing a theoretically-better contract, but having to wait around to do so.

The Pathclearer letter-agreement approach. A similar approach to getting to signature quickly, for low-risk business contracts, was dubbed "Pathclearer" by the in-house counsel who developed it at Scottish & Newcastle, a brewery in the UK. That approach entailed the following:

  1. Use short letter agreements instead of long contracts, and
  2. Rely on the general law and commercial motivations — i.e., each party's ability to walk away, coupled with each party's desire to keep working with a proven-good supplier or customer — to fill in any remaining gaps in coverage. See Steve Weatherley, Pathclearer: A more commercial approach to drafting commercial contracts, Practical L. Co. L. Dept. Qtrly, Oct.-Dec. 2005, at 40.

28.3. Emails, texts, and signed term sheets

28.3.1. Signed term sheets could be binding

In U.S.-style jurisdictions, a signed term sheet would be legally binding as a contract if it contains the usual elements: Meeting of the minds (offer and acceptance), capacity, consideration (see § 32.29). Example: A 1.5-page "Binding Term Sheet" between Louisiana State University and its later-fired head football coach — signed while the coach was married — was found to be legally enforceable. As a result, under the state's community-property laws, the coach's former wife was entitled to half of the coach's $17 million severance payment. See Orgeron v. Orgeron, No. 2024-C-00676, slip op. at 5-6 (La. Jun. 27, 2025) (reversing district court).

28.3.2. Emails exchanges as contracts

Some might be surprised that in the United States (and the UK, and probably other jurisdictions), you can form a legally-binding contracts by exchanging emails. A number of examples are listed in the footnote — students, you can just scan the list for general familiarity; you won't be tested on the details.42

Moreover, an email exchange could serve to evidence a binding oral contract, even if the emails didn't in themselves establish the existence of a contract — assuming of course that the oral contract wasn't barred by the Statute of Frauds (recapped at 32.35). See Gibson Foundation, Inc. v. Norris, No. 24-1763 (1st Cir. Nov. 20, 2025) (affirming judgment on jury verdict that a rhinestone-adorned piano that had belonged to flamboyant entertainer Liberace had been loaned — not gifted — to a pianist); cf. Nusbaum v. E-Lo Sportswear LLC, No. 17-cv-3646 (KBF), slip op. at 9 (S.D.N.Y. Dec. 1, 2017) (granting former employee's motion for summary judgment; emails established meeting of the minds).

Of course, an email exchange wouldn't create a binding contract if the content of the emails failed to meet the usual requirements of establishing a meeting of the minds on all material terms, consideration, and an agreement to be bound (see § 32.29). BUT: If your client is intending not to be bound, then it's best to encourage the client to stay well away from the edge of the cliff — e.g., by including "this isn't binding!" language such as that of § 3.11.2 in Protocol 3.11 (letters of intent).

28.3.2.1. Example: A quick, low-risk deal

Email contracts can be especially useful when the parties are mainly interested in having something in writing. Example: A client of mine and one of its customer agreed on terms for a small matter. Let's call my client "MathWhiz" and the customer "Gigunda," to conform to our class hypothetical. The parties "signed" the final, negotiated version of a contract by email. They were willing to do this because it was a small matter and the parties' relevant business people had previously worked together while employed by other companies.

Here's how we did it:

Step 1: Gigunda's in-house lawyer, "Gina," and I agreed to a final draft of the contract. I saved the final draft as a PDF.

Step 2: With Gina's prior concurrence, I sent the following email to the pre-designated executives of each company — "Mary" for my client MathWhiz and "George" for Gigunda. Of course I copied Gina (Gigunda's lawyer), along with some other business people involved in the negotiation to keep them in the loop.

Here’s the text of my email, lightly edited — the first line below is the subject line:

SIGNATURE REQUEST: Gigunda-MathWhiz Project Agreement

MARY and GEORGE: Per Gina's’s email (below), please do a Reply to All with the text "Agreed" to confirm that MathWhiz and Gigunda and have agreed to the attached Project Agreement, reflecting agreed revisions.

GINA: As previously discussed by email, the attachment is a PDF of the redline that you sent on Sept. XX, with no other changes [see the "Pro tip" below], and with the redlines left in place so that Mary can see the agreed variations from MathWhiz's standard agreement form.

Thanks,

–DC

[my signature block]

(Emphasis added.)

Step 3: Mary and George promptly emailed back "Agreed." Under the law pretty much everywhere in the U.S. (see the citations in the preceding footnotes), this created a binding contract — and the parties didn’t have to go to the trouble of wet-ink signature, nor did they have to use a document-signature service.

Pro tip: Note that in my email above, I proactively confirmed to Gigunda's lawyer Gina that I’d made no other changes to the draft that the customer’s lawyer and I had agreed on. This small professional courtesy helps speed up the signature process, because one lawyer will generally take another lawyer's word for something like this. (BUT: If the occasion offers, ask me in class about a somewhat-embarrassing situation that happened to me as a new lawyer.)

28.3.2.2. Downsides of emails as contracts

Email exchanges don't seem to be used as contracts very often in practice. There are a couple of possible reasons for that.

1.  First, parties often neglect to file emails in an organized fashion. If that happened with an email contract, a party might forget about the contract.

2.  And if a party forgot about an email-exchange contract, then perhaps one day the party might find itself:

  • in breach of the contract — and ambushed by the other party's claim for damages; and/or
  • not claiming a benefit, and perhaps losing the benefit as a result (e.g., if there was a contractual deadline).

3.  Finally, parties (and lawyers) often prefer the comfort of having a separate, signed document that looks like a contract.

So: Parties often prefer contracts to be a bit more formal. BUT: As we saw in the real-world MathWhiz and Gigunda example above, parties might still be willing to use an email exchange as "the contract" in a transaction where:

  • No one expects the transaction to be a big deal.
  • The parties want something in writing "just in case."
  • The parties don't want to spend a lot of time or money on a traditional contract.
28.3.2.3. Signatures on email contracts

For an email exchange to form a binding contract, the emails must include "signatures" for each party. Those can (usually) take the form of email signature blocks, and even names in email "From" fields. For an extensive discussion of authority on this point, see Khoury v. Tomlinson, 518 S.W.3d 568, 575-77 (Tex. App. [1st Dist.] 2017, no pet.) (holding that "from" field sufficed as a signature but reversing and remanding on other grounds). One court held that a "from" field can suffice as a signature, but also held that on the particular facts of that case, the "from" field in the email in question did not act as a signature for an attached document (and also that the parties had not agreed to transact their business electronically). See SN4, LLC v. Anchor Bank, FSB, 848 N.W.2d 559 (Minn. App. 2014).

(For more on contract signature blocks, see 29.4.)

28.3.2.4. Pro tip: Consider a disclaimer in your email signature block

DCT comment: Because of the established law discussed above, I've long included a disclaimer in email signature blocks; at this writing (mid-2025), the disclaimer reads as follows:

Unless expressly stated otherwise in this message itself, this message is not intended to serve as assent to any agreement or other document, even one accompanying this message.

28.3.3. Text-message conversations: Binding?

Even a very-terse exchange of text messages or instant messages ("IM") can create a binding contract, if the exchange would otherwise qualify as such.

Example: An IM exchange between a digital ad agency and an electronic cigarette manufacturer served as a binding agreement to increase the ad a gency's budget for placing online ads for the e-cigarettes. The crux of the IM exchange started with a message from an account executive at the ad agency: "We can do 2000 [ad placement] orders/day by Friday if I have your blessing." The manufacturer's VP of advertising responded: "NO LIMIT." The account executive responded: "awesome!" That series of messages served to modify the parties' contract — as a result, the manufacturer had to pay the ad agency more than a million dollars in additional fees. See CX Digital Media, Inc. v. Smoking Everywhere, Inc., No. 09-62020-CIV, slip op. at 8, 17-18 (S.D. Fla. Mar. 23, 2011); see also, e.g., Moe's Home Collection, Inc. v. Davis Street Mercantile, LLC, No. 05-19-00595-CV, slip op. at 6-10 (Tex. App.—Dallas June 6, 2020) (binding agreement to sell an entire warehouse of furniture)..

BUT: A text-message or IM conversation won't be binding as a contract if the usual prerequisites aren't met — e.g., offer, acceptance, consideration. See, e.g., iWTNS, Inc. v. MotionMobs, LLC, No. SC-2024-0591, slip op. (Ala. Aug. 22, 2025) (reversing and remanding district-court order: text message was a counteroffer, not acceptance).

Caution: When it comes to real-estate contracts, California's version of the Statute of Frauds states that: "An electronic message of an ephemeral nature that is not designed to be retained or to create a permanent record, including, but not limited to, a text message or instant message format communication, is insufficient under this title to constitute a contract to convey real property, in the absence of a written confirmation that conforms to the requirements of [citation omitted]." Cal. Civ. Code § 1624(d) (emphasis added).

28.4. Master agreements: Frameworks for later contracts

().  Master agreements typically don't themselves obligate either party to engage in transactions, but instead serve as a reference document containing terms and conditions for specific purchase orders or work orders. See, e.g., James Constr. Grp., LLC v. Westlake Chem. Corp., 650 S.W.3d 392, 397, text acc. n.2 (Tex. 2022) (master agreement did not obligate Westlake Chemical to assign any work to James Construction).

The Eighth Circuit once observed that "Texas law permits contracts that set the guidelines for future agreements to become enforceable at the point that those future contracts are created. These contracts are not binding alone, but set out the rules of the game in the event the parties decide to play ball. They are valid and enforceable under Texas laws, so long as the parties enter into the agreements contemplated in the original contract." J.V. & Sons Trucking, Inc. v. Asset Vision Logistics, LLC, 121 F.4th 690, 695-96 (8th Cir. 2024) (citations omitted, formatting edited).

Note: A master agreement might state that some particular provisions are indeed binding, just as can an otherwise-nonbinding letter of intent. See, e.g., the list of potentially-binding LOI provisions at § 3.11.3.

Some trade associations and similar groups have published standard form contracts that serve much the same purpose as a master agreement. See, for example:

28.5. Employment applications can form a binding contract

In a Michigan case, an individual filled out an employment application. Among other things, the application included language that imposed a six-month deadline on the individual's ability to sue the company. After working for some seven years, the employee resigned, citing discrimination, and — 14 months later — filed a lawsuit against the company.

The company moved to dismiss the lawsuit, citing the six-month limitation period in the employment application. The trial court granted the motion to dismiss, and the appeals court affirmed, holding: "In this case, plaintiff agreed to the provision in his employment application, which constitutes part of his employment contract." King v. McLaren Health Corp., No. 36615, slip op. at part II.A (Mich. App. Jan. 30, 2025) (affirming dismissal of former employee's lawsuit) (unpublished; citations omitted).

28.6. Agreements to "negotiate in good faith" can be enforceable

Business people and drafters can sometimes be tempted to say, in a contract, "we haven't agreed on this yet, but we'll negotiate it in good faith." (That might be especially likely if the issue in question hasn't yet come up, e.g., a future contingency of some kind.) Agreements to negotiate in good faith are generally enforceable under U.S. law. See, e.g., Cox Communications, Inc. v. T-Mobile US, Inc., 273 A.3d 752, 764 & n.81 (Del. 2022): "Delaware law recognizes that obligations to negotiate in good faith are not worthless."

Agreements to negotiation in good faith fall in the category that Delaware law recognizes as a "Type II" preliminary agreement:

Type I agreements are firm obligations where the parties agree on all terms and contemplate memorializing the agreement in a formal document,

while Type II agreements reflect the parties' commitment to negotiate together in good faith in an effort to reach final agreement within the scope that has been settled in the preliminary agreement. 37celsius Capital Partners, L.P. v. Intel Corp., No. 24-2794, slip op. at 10 (7th Cir. Dec. 23, 2025) (affirming summary judgment in favor of defendant Intel) (citations omitted, formatting edited); see also, e.g., Cambridge Capital LLC v. Ruby Has LLC, 565 F. Supp. 3d 420, 440-41 (S.D.N.Y. 2021) (denying motion to dismiss: plaintiff had plausibly pled enough facts to support a claim of breach of agreement to negotiate in good faith in letter of intent) (citing cases).

Food-for-thought question: In determining whether a party had in fact complied with a good-faith negotiation, what kinds of evidence might be relevant? What could or should parties do to preserve such evidence?

28.7. Agreements to agree are pretty-much worthless legally

Business people and drafters can sometimes be tempted to say, in a contract, "we don't know what we want to do about Issue X, so we'll leave that for later." That might, or might not, cause problems later.

In U.S. jurisdictions, an "agreement to agree" in a contract is not enforceable.

BUT: That's distinct from the situation in which a contract is materially complete but has "open terms" that a court can readily calculate or discern; in the latter situation, the contract is enforceable if it otherwise qualifies as such under the law, e.g., the Statute of Frauds (recapped at 32.35). See, e.g., Bich v. WW3 LLC, 130 F.4th 623, 633 (7th Cir. 2025) (affirming summary judgment: parties' writings were not enough to satisfy Statute); Phytelligence, Inc. v. Wash. State Univ., 973 F.3d 1354, 1360-62 (Fed. Cir. 2020) (affirming summary judgment: contract in question was an unenforceable agreement to agree, and not an otherwise-enforceable agreement with open terms).

Relatedly: A statement in a contract that something will happen later "only after" the parties "mutually agree" on something is likely to be held a condition precedent — i.e., a prerequisite — and not an unenforceable agreement to agree nor an agreement to negotiate in good faith. See Endeavor Natural Gas III, LLC v. Comanche Maverick Ranch Investments, LP, No. 14-24-00639-CV, slip op. (Tex. App—Houston [14th Dist.] Nov. 4, 2025 (affirming summary judgment; citing cases).

28.8. Purchase orders as contracts

Contracts can arise when parties send each other terms-and-conditions documents — a.k.a. "throw paper at each other" — in the course of doing a transaction. This can cause problems when conflicting terms exist in the parties' respective paper.

Contents:

28.8.1. The paper flow of a typical purchase

When a corporate customer makes a significant purchase, it's essentially a universal practice for the customer's procurement people to send the vendor a purchase order. Typically, the customer insists that the vendor's invoice must include the purchase-order number — if the invoice doesn't have a PO number, then the customer's accounts-payable department generally just won't pay the invoice. These are routine internal-controls measures for customers; they're almost-uniformly implemented by customers to help prevent fraud.

Often (but not always) the customer's purchase order will have been preceded by the vendor's sending the customer a sales quotation proposing to sell specific goods and/or services, at a stated price, with stated delivery terms.

Here's a swim-lane diagram, produced by ChatGPT (with a lot of back-and-forth instructions for corrections):

Swim-lane diagram showing paper flow in a purchase transaction with customer sending vendor a request for quote and so on

28.8.2. Problems with legal fine print

When a customer sends a purchase order to a vendor, the purchase-order form might well include legal fine print added by the customers lawyers. Those lawyers want to protect their client as much as possible, so they can be inclined to load the document with terms and conditions. In a customer's PO, the legal fine print might include, e.g.:

  • expansive vendor warranties;
  • long statute-of-limitations provisions;
  • onerous indemnity requirements;
  • various "acknowledgements" (see 11.2) to give the customer leverage over the vendor in litigation (and thus in settlement negotiations);

and so on. See, e.g., a Honeywell purchase-order form archived at https://perma.cc/CUV6-NKTY. For a customer-oriented checklist of "gap-filler" PO terms that vendors might find objectionable — which would often lead to time-consuming negotiations and delays — see Stephen Gillen, AI and Your Purchase Order Form (JDSupra.com 2025).

And vendors aren't always innocent parties in this little dance; oh, no. It's not uncommon for a vendor's initial sales quotation (inviting a purchase order) to state that all customer orders are subject to acceptance in writing by the vendor. Then, when the customer does send a purchase order, the vendor responds with a written "order confirmation." Often, the order confirmation that itself contains detailed terms and conditions — some of which might directly conflict with the terms in the customer's purchase order. See, e.g., a Honeywell terms-of-sale document archived at https://perma.cc/5MB9-H6VK.

Even vendor invoices might contain terms and conditions that the vendor might try to assert someday as constituting the contract — even though the customer might reasonably counter that "the contract" was formed and its terms locked in — long before the vendor sent its invoice.

28.8.3. Pro tip: Reject the other side's fine-print terms?

A customer's purchase order will often reject any terms in the vendor's order confirmations, invoices, etc. (You'll remember from the 1L Contracts course that A's rejection of B's offer means that no contract is formed on the offer.) Similarly, vendors' sales quotes, order confirmations, etc., often reject the customer's purchase-order terms. In effect, these rejections say, only our terms and conditions will apply, sport — your terms won't count, no matter what happens. Both of the above-cited Honeywell forms include such rejection language.

This kind of language is motivated by section 2-206 of the (U.S.) Uniform Commercial Code. That section states, in part, that for sales of goods:

(1) Unless otherwise unambiguously indicated by the language or circumstances[,]

(a) an offer to make a contract shall be construed as inviting acceptance in any manner and by any medium reasonable in the circumstances …. UCC § 2-206 (emphasis added).

Lesson: Drafters asked to prepare standard forms of this kind should strongly consider whether to include "We reject your terms!" language along these lines.

28.8.4. Battle of the Forms: When each party's paper rejects the other's terms

In real-world dealings, what practical impact will result from these Pythonesque statements in parties' transaction paper? This is important because the parties' people might not even notice the legal fine print in these dueling forms. Instead, what could easily happen is something like the following:

  • The vendor's sales people process the purchase order and send it to the order-fullfilment department.
  • The vendor's order-fulfillment department ships the ordered goods — along with a confirmation of sale document and an invoice.
  • The customer's receiving department takes delivery of the ordered goods and puts them into inventory, distributes them to end users, or whatever.
  • The customer's receiving department forwards the vendor's invoice to the customer's accounts-payable department, which in due course pays the invoice.
  • Neither party signs the other's paper.

So whose terms and conditions will govern — those of the customer, or those of the vendor? Neither has agreed to the other's terms and conditions. But clearly the parties have conducted themselves as though they had a contract.

This sort of situation is known as the "Battle of the Forms." It's expressly contemplated by UCC § 2-207. (It's sometimes experienced in common-law situations as well.)

Under the "Drop-Out Rule" in UCC § 2-207(3), when the parties are merchants (see 13.5):

  • whatever terms are common to the parties' respective contract forms is part of "the contract"
  • all other terms in both parties' contract forms drop out — left on the cutting-room floor, if you will; and
  • the UCC's gap-filler terms also apply.

Before we look at the text of the Drop-Out Rule, it might be helpful to study this Venn diagram of how the Rule works:

UCC § 2-207(3) Venn diagram


And now here's the text of UCC § 2-207(3):

(3) Conduct by both parties which recognizes the existence of a contract is sufficient to establish a contract for sale although the writings of the parties do not otherwise establish a contract.

In such case the terms of the particular contract consist of[:] [i] those terms on which the writings of the parties agree, together with [ii] any supplementary terms incorporated under any other provisions of this Act. Emphasis and bracketed text added; see generally the discussion of the "Battle of the Forms" by Brian Rogers at https://tinyurl.com/BattleFormsBrianRogers, along with his diagram at https://tinyurl.com/BattleFormsDiagram.

So: In our hypothetical situation above, our parties have engaged in conduct that recognizes the existence of a contract: Goods have been ordered, delivered, and paid for. Under the Drop-Out Rule, the terms of the parties' contract are:

  • whatever "matching" terms exist in the parties' respective forms, plus
  • the UCC's default provisions. See, e.g., Axiall Canada, Inc. v. MECS, Inc., No. 21-30105, slip op. part III (5th Cir. Jun. 14, 2023) (affirming denial of motion to compel arbitration because parties' paper did not have arbitration provision in common) (per curiam, unpublished).

28.8.5. Caution: The UN CISG uses the "last-shot rule" instead

It'd be a very-different analysis of the Battle of the Forms under the UN Convention on Contracts for the International Sale of Goods (UN CISG) The CISG follows the so-called "last shot" rule, which the Seventh Circuit summarized as: "The terms of the contract are those embodied in the last offer (or counteroffer) made prior to a contract being formed." The court affirmed a judgment below that "because Illinois Trading never expressly assented to the attorney's fees provision in VLM's trailing invoices, under the Convention that term did not become a part of the parties' contracts." VLM Food Trading Int'l, Inc. v. Illinois Trading Co., 811 F.3d 247, 250-51 (7th Cir. 2016) (cleaned up).

28.8.6. Selected bibliography

(Students: This additional reading is optional.)

See generally:

–  Battle of the Forms – UCC and common-law variations

–  Purchase order (Wikipedia)

–  Brian Rogers, Battle of the Forms Explained (Using a Few Short Words) (blog entry March 1, 2012).

–  Marc S. Friedman and Eric D. Wong, TKO'ing the UCC's 'Knock-Out Rule', in the Metropolitan Corporate Counsel, Nov. 2008, at 47.

For an eye-glazing set of "battle of the forms" facts, see BouMatic LLC v. Idento Operations BV, 759 F.3d 790 (7th Cir. 2014) (vacating and remanding dismissal for lack of personal jurisdiction) (Easterbrook, J.).

An existing teaching case is Northrop Corp. (7th Cir. 1994): The buyer's purchase order stated that the vendor's warranty provision was of unlimited duration, but the vendor's acknowledgement form stated that the vendor's warranty lasted only 90 days. The trial court held, the appellate court agreed, that both of those provisions dropped out of the contract, and therefore the buyer was left with a UCC implied warranty of "reasonable" duration. See Northrop Corp. v. Litronic Industries, 29 F.3d 1173, 1189 (7th Cir. 1994).

29. Bookends: The front and back

29.1. Preambles (classic style): Useful information up front?

29.1.1. Illustration: A hypothetical example

Here's an example of a traditional preamble for a contract, in the usual very-compact form:

Purchase and Sale Agreement
for 2012 MacBook Air Computer

This "Agreement" is between (i) Betty’s Used Computers, LLC, a Texas limited liability company ("Buyer"), with its principal place of business and its initial address for notice at 1234 Main St, Houston, Texas 77002; and (ii) Sam Smythe, an individual residing in Houston, Harris County, Texas, whose initial address for notice is 4604 Calhoun Rd, Houston, Texas 77004 ("Seller"). This Agreement is effective the last date written on the signature page.

Let’s look at this preamble piece by piece: The included information is intended to make life easier on trial counsel if litigation should ever occur.

29.1.2. Defining "this Agreement"

Many drafters would repeat the title of the agreement in all-caps in the preamble, thusly: "THIS PURCHASE AND SALE AGREEMENT (this "Agreement") …."

But a shorter approach might be safer:

THIS PURCHASE AND SALE AGREEMENT (this "Agreement") ….

This "Agreement" ….

This is because:

– It’s doubtful that anyone would be confused about what "This 'Agreement'" refers to; and

– The shorter version reduces the risk that a future editor might (i) revise the title at the very top of the document but (ii) forget to change the title in the preamble. This is an example of the rule of thumb: Don’t Repeat Yourself, or D.R.Y., discussed at 30.4.

(In the second bullet point just above, notice how the first, long-ish sentence is broken up (i) with bullets, and (ii) with so-called "romanettes," that is, lower-case Roman numerals, to make the sentence easier for a contract reviewer to skim. This follows the maxim: To serve the client, serve the reader.)

29.1.3. Choose shorthand names for the parties, e.g., "Buyer" and "Seller"

In its preamble, our hypothetical contract defines the terms Buyer and Seller instead of repeatedly the parties’ names, Betty and Sam.

… Betty's Used Computers, LLC, a Texas limited liability company ("Betty") ….

… Betty's Used Computers, LLC, a Texas limited liability company ("Buyer") ….

This is because:

  • Shorthand names for the parties can make it easier on future readers … such as a judge … to keep track of who’s who: Someone scanning the contract "cold" might wonder, "now what's Betty's role in this again?" Calling her Buyer will instantly answer that question.
  • Shorthand names also make it easier for the drafter to re-use the contract as a starting point for a future deal by just changing the names at the beginning, e.g., changing Betty's Used Computers, LLC to Bob's BBQ Tools, Inc.

Sure, global search-and-replace can work, but it’s often over-inclusive. For example: Automatically changing all instances of Sam to Sally might result in the word samples being changed to sallyples.

29.1.4. Defined terms: Bold type, quotation marks, parentheses

In the example above, note how the preamble defines the terms Agreement, Buyer, and Seller: These defined terms are:

  • in bold-faced type;
  • surrounded by quotation marks; and
  • in parentheses.

… a Texas limited liability company (Buyer), ….

… a Texas limited liability company ("Buyer"), ….

These things help to make the defined terms stand out to a reader who is skimming the document looking for the definition of a particular defined term ("hmm, where did I see that definition of Buyer?").

When drafting "in-line" defined terms like this, it’s a good idea to highlight them in this way; this makes it easier for a reader to spot a desired definition quickly when scanning the document to find it.

NOTE: If you also have a separate definitions section for defined terms, it’s a good idea for that definitions section to include cross-references to the in-line definitions as well, so that the definitions section serves as a master glossary of all defined terms in the agreement. (See also 32.11 for more discussion of defined terms.)

29.1.5. The Agreement is "between" the parties

Our preamble says that the contract is between the parties — not by and between the parties, and not among them.

This Agreement is by and between ….

This Agreement is between ….

True, many contracts say "by and between" instead of just "between." The former, though, sounds like legalese, and the latter works just as well.

For contracts with multiple parties, some drafters will write among instead of between; that’s fine, but between also works.

(This is one of those "don't change another party's draft" style points; see 8.11.)

29.1.6. Preferred: State some details about the parties (in case of litigation)

Our preamble states certain details about the parties, such as where Betty's Used Computers, LLC is organized (Texas) and Sam's county of residence.

When a party to a contract is a corporation, LLC, or other organization, it’s an excellent idea for the preamble to state both:

  • the type of organization, in this case "a limited liability company"; and
  • the jurisdiction under whose laws the organization was formed, in this case "organized under the laws of the State of Texas."

Stating these facts in the preamble can provide several benefits:

– It reduces the chance of confusion in case the same company name is used by different organizations in different jurisdictions … imagine how many "Acme Corporations" or "AAA Dry Cleaning" there must be in various states.

– It helps to nail down at least one jurisdiction where the named party is subject to personal jurisdiction and venue, saving future trial counsel the trouble of proving it up. For example: Sam, our seller, would have a hard time objecting to being sued in Texas, because the preamble recites that he's a resident of Texas.

– Moreover: Stating the parties' residences helps to establish whether U.S. federal courts have diversity jurisdiction. (That's a U.S. concept that might or might not be applicable elsewhere.)

Some drafters prefer a longer version:

Betty’s Used Computers, LLC, a Texas limited liability company ….

Betty’s Used Computers, LLC, a limited liability company organized under the laws of the State of Texas ….

Including the jurisdiction of organization can simplify a litigator’s task of "proving up" the necessary facts: If a contract signed by ABC Corporation recites that ABC is a Delaware corporation, for example, then an opposing party generally won’t have to prove that fact; that's because ABC will usually be deemed to have "acknowledged" it (see 11.2), that is, stipulated to the fact in advance.

This particular hypothetical agreement is set up to be between a limited liability company, or "LLC," and an individual. See 29.4 for more about signature blocks for organizations.

29.1.7. Maybe: Principal place of business and initial notice address

Our preamble states some geographical information about the parties, with the same goals as stated at 29.1.6 just above:

Principal place of business: Stating Betty’s principal place of business helps trial counsel avoid having to prove up the court’s personal jurisdiction and the citizenship of the party for diversity-jurisdiction purposes. For example, a Delaware corporation whose principal place of business was in Houston would almost certainly be subject to suit in state court in Houston.

(Note: As discussed at 21.29, the Supreme Court has held that, for purposes of federal diversity jurisdiction, the principal place of business is corporation's "nerve center," that is, "the place where a corporation's officers direct, control, and coordinate the corporation's activities," which usually will be the corporation's headquarters. Caution: Conceivably this might not be the case under the law of a given state, e.g., under the state's venue statute establishing where a corporation can be sued in state court as opposed to federal court. )

Residence: Likewise, if a party to a contract is an individual, then stating the individual’s residence helps to establish personal jurisdiction over him or her and the proper venue for a lawsuit against the individual.

County: Stating the county of an individual’s residence might be important if the city of residence extends into multiple counties.

For example: Houston is the county seat of Harris County. But just because Sam lives in Houston doesn’t automatically mean that he can be sued in the county’s courts in downtown Houston. That’s because Houston’s city limits extend southward into Fort Bend County and northward into Montgomery County. Sam might live in the City of Houston but in one of those other counties, and so he might have to be sued in his home county — e.g., Richmond (Fort Bend County) or Conroe (Montgomery County), vice Houston (Harris County).

Initial addresses for notice: It’s convenient to put the parties’ initial addresses for notice in the preamble. That way, a later reader won’t need to go paging through the agreement looking for the notice provision. Doing this also makes it easy for contract reviewer(s) to verify that the information is correct.

29.1.8. State the effective date in the preamble? (Preferably: No.)

The above preamble affirmatively states the effective date; that’s usually unnecessary unless the contract is to be effective as of a specified date.

(Many drafters like to include the effective date anyway; it's normally not worth changing if someone else has drafted it this way.)

The last-date-signed approach:

This Agreement is effective the last date written on the signature page.

This Agreement is made, effective the last date signed as written below, between ….

In reviewing others’ contract drafts, you’re likely to see some less-good possibilities, such as:

This Agreement is made December 31, 20XX ….

This Agreement is dated December 31, 20XX ….

(Emphasis added.)

The first, "is made" version above is problematic: What if the parties sign on a different date or dates than December 31? The contract's very first words (after the title) would be a misstatement. At a minimum, it's not a good look; at worst, it could be an intentional attempt at deceptive backdating (see below).

The second, "is dated" version above is problematic in a different way: What exactly does it mean to say that a contract is "dated December 31"? You might as well say that the contract "is purple."

BUT: When you're reviewing a contract that has the effective date stated in this way, it's a judgment call whether you want to change it — maybe ask the partner first (30.5)?

29.1.9. A contract could be backdated — but not the signatures

It might be just fine to state that a contract is effective as of a different date than the signature dates.

This Agreement is made on the last date written on the signature page, but is effective as of [fill in date].

EXAMPLE: Alice discloses confidential information to Bob after Bob first orally agrees to keep the information confidential; they agree to have the lawyers put together a written confidentiality agreement. That written agreement might state that it is effective as of the date of Alice’s oral disclosure.

(Alice and Bob would not want to backdate their actual signatures, though.)

Caution: Never backdate a contract for deceptive purposes, e.g., to be able to book a sale in an earlier period; as discussed at 3.16.5, that practice has sent more than one corporate executive to prison — including at least one giant company's in-house general counsel.

29.1.10. Include the parties’ affiliates as "parties"? (Almost certainly not.)

Some agreements, in identifying the parties to the agreement on the front page, state that the parties are, say, ABC Corporation and its Affiliates. That’s generally a bad idea unless each such affiliate actually signs the agreement as a party and therefore commits on its own to the contractual obligations. See 20.1.7.3 for more details.

This Agreement is between (i) ABC Corporation, a Delaware corporation, and its Affiliates … and (ii) XYZ Inc., a New York corporation ….

This Agreement is between (i) ABC Corporation, a Delaware corporation … and (ii) XYZ Inc., a New York corporation …. ABC's "Affiliates" have certain rights and obligations under this Agreement as stated below.

29.1.11. Is country-specific information required? (Possibly.)

Some countries require contracts to include specific identifying information about the parties, e.g., the registered office and the company ID number. This is worth checking for contracts with parties or operations in such countries.

29.1.12. Naming the "wrong" party can kill legal rights

Be sure you’re naming the correct party as "the other side" — or consider negotiating a guaranty (see Protocol 4.8) from a solvent affiliate.

Failing to name the correct corporate entity could leave your client holding the bag. This seems to have happened in a Seventh Circuit case, case, discussed at 20.1.7.2, where the plaintiff had entered into a contract with what turned out to be a judgment-proof subsidiary of the parent company that it had thought it was dealing with.

29.1.13. Does each party have the legal capacity to contract?

Depending on the law of the jurisdiction, an unincorporated association or trust might not be legally capable of entering into contracts.

If a contract is purportedly entered into by a party that doesn’t have the legal capacity to do so, then conceivably the individual who signed the contract on behalf of that party might be personally liable for the party’s obligations.

29.2. Preamble (streamlined): Tables, for quicker reading

29.2.1. Put signature blocks, etc., up front?

In the example signature blocks immediately below, you'll see that the signature blocks are in a table at the front of the agreement — along with the parties' respective initial addresses for notice. This makes the agreement more user-friendly, because:

  • the reader can see at a glance whether the reader is looking at the signed agreement;
  • the parties' types- and states of organization are provided, for reasons discussed at 29.1.6;
  • the parties' (initial) addresses for notice are conveniently located — the reader doesn't need to rummage through the document to find a notice address; and
  • the drafter doesn't have to hunt through the document looking for text that needs to be updated.
A screen shot of the first page of a contract with the signature blocks and certain key information just after the top of the document

29.2.2. Schedules at the front: Worksheets for deal-specific "variables"

Also for drafter- and reader convenience: In any contract form, it's never a bad idea to put deal-specific details up front in a "schedule" — which could be thought of as a worksheet for drafting and negotiation. That way:

  • A drafter using the contract form can change key details by focusing on just the up-front terms in the worksheet.
  • If a vendor's contract form specifies net-30 payment terms, but the vendor knows that some customers will want longer to pay, then the parties can get to signature sooner if the payment terms are in the worksheet.

So: Consider putting the details of such terms in a "schedule," either at the front of the document or at the beginning of the clause in question.

Example: See the following excerpt from a real-estate lease between Stanford University (landlord) and Tesla (tenant), where I've added extra paragraphing and bold-facing:

COMMERCIAL LEASE

THIS LEASE is entered into as of July 25, 2007 (the “Effective Date”), by and between THE BOARD OF TRUSTEES OF THE LELAND STANFORD JUNIOR UNIVERSITY, a body having corporate powers under the laws of the State of California (“Landlord”), and TESLA MOTORS, INC., a Delaware corporation (“Tenant”).

1.  BASIC LEASE INFORMATION. The following is a summary of basic lease information.

Each item in this Article 1 incorporates all of the terms set forth in this Lease pertaining to such item and to the extent there is any conflict between the provisions of this Article 1 and any other provisions of this Lease, the other provisions shall control.

This table format can:

  • give the business people an "executive summary" of terms in which they're likely to be especially interested;
  • speed up review and editing of the draft; and
  • in the future, make it easier and safer to re-use the contract form as the starting point for a new contract, with less risk of having old terms appear in the new contract — as an embarrassing real-life example, see the screw-up in the Brexit agreement summarized at 30.2).

(This principle is an example of the R.O.O.M. Principle: Root Out Opportunities for Mistakes.)

Another example: The Texas Apartment Association Lease form contains the main "business terms" on the first page.

(See Quick tour: An apartment lease for a lookup exercise about this form.)

29.3. Background section of the Con­tract: No more "Whereas"!

29.3.1. Style tip: Don't do "Witnesseth" and "Whereas"

Note to students: Like all purely-style tips, this particular style tip isn't worth making a big deal about if you're reviewing a draft prepared by The Other Side (see 8.11). And if your supervising partner has a preference, then (normally) just do it that way (see 30.6).

Modern contract drafters avoid using the archaic words "WITNESSETH" and "Whereas.” For an example of what not to do, see the following example from a routine commercial real-estate purchase agreement:

Don't bother reading the text below, just get a sense of how it looks.

THIS REAL ESTATE PURCHASE AND SALE AGREEMENT (this "Agreement") is made and entered into by and between WIRE WAY, LLC, a Texas limited liability company ("Seller"), and RCI HOLDINGS, INC., a Texas corporation ("Purchaser"), pursuant to the terms and conditions set forth herein.

W I T N E S S E T H:

WHEREAS, Seller is the owner of a certain real property consisting of approximately 4.637± acres of land, together with all rights, (excepting for mineral rights as set forth below) , title and interests of Seller in and to any and all improvements and appurtenances exclusively belonging or pertaining thereto (the "Property") located at 10557 Wire Way, Dallas (the "City"), Dallas County, Texas, which Property is more particularly described on Exhibit A attached hereto and incorporated herein by reference; and

WHEREAS, contemporaneously with the execution of this Agreement, North by East Entertainment, Ltd., a Texas limited partnership ("North by East"), is entering into an agreement with RCI Entertainment (Northwest Highway), Inc., a Texas corporation ("RCI Entertainment"), a wholly owned subsidiary of Rick's Cabaret International, Inc., a Texas corporation ("Rick's") for the sale and purchase of the assets of the business more commonly known as "Platinum Club II" that operates from and at the Property ("Asset Purchase Agreement"); and

WHEREAS, subject to and simultaneously with the closing of the Asset Purchase Agreement, Seller will enter into a lease with RCI Entertainment, as Tenant, for the Property, dated to be effective as of the closing date, as defined in the Asset Purchase Agreement (the "Lease") attached hereto as Exhibit B and incorporated herein by reference; and

WHEREAS, subject to the closing of the Asset Purchase Agreement, the execution and acceptance by Seller of the Lease, and pursuant to the terms and provisions contained herein, Seller desires to sell and convey to Purchaser and Purchaser desires to purchase the Property.

NOW, THEREFORE, for and in consideration of the premises and mutual covenants and conditions contained herein, and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties hereto agree as follows:

This isn't the easiest to understand.

The above example has other problems, in addition to its use of archaic "Whereas" clauses: Because of the "as follows" language at the end of the last paragraph quoted above, it could be argued — which means aggressive counsel might well try to argue — that the parties did not agree to the Whereas clauses. (This is discussed in more detail at 29.3.3.)

29.3.2. Use the "Background" section to set the stage

Instead of "Recitals" — or worse yet, W H E R E A S clauses — you're better off describing the background in a (numbered) "Background" section of the contract.

As a general proposition, the Background section should just set up the story: Explain to the future reader, in simple terms — with short sentences and paragraphs — just what the parties are doing, so as to help future readers get up to speed more quickly.

As a horror story, consider the WHEREAS example quoted at 29.3.1 above:

  • Good luck trying to figure out what's really going on — there seems to be some kind of business roll-up going on, with a sale and leaseback of real estate and maybe other assets, but that's not at all clear.
  • Now imagine that you're a judge or a judge's law clerk who's trying to puzzle out the story.
  • Worse: Imagine that you're a juror trying to make sense of this transaction.

Somewhat better is the following excerpt is from a highly publicized stock purchase agreement in the tech industry, rewritten into background-section form below:

BEFORE:

WHEREAS, concurrently with the execution and delivery of this Agreement, Seller and Yahoo Holdings, Inc., a Delaware corporation (the “Company”), are entering into a Reorganization Agreement substantially in the form attached hereto as Exhibit A (the “Reorganization Agreement”), pursuant to which Seller and the Company will complete the Reorganization Transactions at or prior to the Closing; Stock Purchase Agreement by and among Yahoo! Inc. and Verizon Communications Inc. dated as of July 23, 2016, https://tinyurl.com/VerizonYahooAgreement.

AFTER REWRITE:

1.  Background

1.01  At the same time as this Agreement is being signed, Seller and Yahoo Holdings, Inc., a Delaware corporation (the “Company”), are entering into a Reorganization Agreement.

1.02  Under the Reorganization Agreement, Seller and the Company are to complete certain "Reorganization Transactions" at or prior to the Closing.

1.03  The Reorganization Agreement is in substantially the form attached to this Agreement as Exhibit A.

Notice the shorter, numbered, single-topic paragraphs, discussed in more detail at 2.5.

29.3.3. A contract's background statements might be binding

Different jurisdictions might treat background statements differently. For example:

–  California Evidence Code § 622 provides: "The facts recited in a written instrument are conclusively presumed to be true as between the parties thereto, or their successors in interest; but this rule does not apply to the recital of a consideration." (Emphasis added.)

–  BUT: In Maryland: "Contracts often contain recitals: provisions that do not make binding promises but merely recite background information about factual context or the parties' intentions. Maryland law recognizes the general principle that such recitals are not binding and, while they may aid the court in interpreting the contract's operative terms, cannot displace or supplement operative terms that are clear." Sprint Nextel Corp. v. Wireless Buybacks Holdings, LLC, 938 F.3d 113, 127 (4th Cir. 2019) (vacating and remanding partial summary judgment) (emphasis added).

And in a 2022 decision, the Court of Federal Claims observed:

Whereas clauses are not contractual; they are recitations laying out the background understandings of the parties.

Thus, in the face of ambiguity, they may be used to interpret the meaning the parties attached to the operative words.

But they can do even more. They tell us the assumed facts and purposes of the parties. Rather than only coming into play given ambiguous language, they also may be considered in determining whether language is clear in the first place.

But what they may not do is create ambiguity where the words have only one permissible meaning. THR Enterpr., Inc. v. United States, No. 20-558C, slip op. (Ct. Fed. Cl. Jun. 8, 2022) (granting defendant's motion for judgment on the pleadings; cleaned up, emphasis and extra paragraphing added).

29.3.4. A statement of one party's intent might not be binding

A naked statement of one party's subjective intent in entering into the contract might not bind another party. Example: That happened in Sprint Nextel, in which:

  • The cell-phone service provider offered "upgraded" phones to its customers at steep discounts when customers renewed their contracts — the discounts were so steep that the customers paid less than what the phones would bring on the used-phone market.
  • Seeing a business opportunity, another company, Wireless Buybacks, bought upgraded phones from Sprint customers and resold them at a profit.
  • Sprint sued Wireless Buybacks for tortious interference with Sprint's contracts with its customers; Sprint claimed that its customer contract prohibited resale because it said in part: "Our rate plans, customer devices, services and features are not for resale and are intended for reasonable and non-continuous use by a person using a device on Sprint's networks." (Emphasis added.)
  • The trial court found that this language unambiguously barred resale of the phones by Sprint customers; the court granted partial summary judgment for Sprint.

On appeal, however, the Fourth Circuit held that the contract language "is a background statement of intent, not an enforceable promise not to resell Sprint phones." Sprint Nextel Corp. v. Wireless Buybacks Holdings, LLC, 938 F.3d 113, 127 (4th Cir. 2019) (vacating and remanding partial summary judgment; emphasis added).

29.3.5. Don't put rights & obligations in the Background

Inexperienced contract drafters will sometimes put specific rights and/or obligations in a Background section. That's a bad idea for the reasons discussed above.

    Example 1: One of the author's students once wrote in the Background section: "For all purposes, the Data is owned by Client and is provided to Contractor for completion of services under this Agreement."

COMMENT: This shouldn't go into the Background section, but instead in a substantive section, for example in a section about ownership of intellectual property.

    Example 2: Another student wrote: "Client will pay Contractor as stated in this Agreement."

COMMENT: This shouldn't be in the Background section, because the payment provisions would (or at least should) speak for themselves — moreover, readers would naturally assume that Client would pay Contractor, so there was no need to include that fact in the Background section.

    Example 3: Still another student wrote: "The parties have agreed that Client will compensate Provider with a flat monthly fee of $20,000 for up to 200 staff hours of work per month, with additional work hours being billed at $150 per hour."

COMMENT: This would work only if the Background section was the only place that the specific compensation details were discussed, so as not to violate the D.R.Y. (Don't Repeat Yourself) guideline discussed at 30.4.

    Example 4: A student wrote: "Client and Service Provider enter into the Agreement for the term of one year from the effective date of the Agreement."

COMMENT: This is another item that would go into a substantive provision further down in the contract, not into the Background section.

29.3.6. (Skim:) Some other student "background" efforts

Note to students: This section will give you an idea of some minor errors that can arise in drafting a background section.

1.  A student used "WHEREAS" several times.

COMMENT: That's OK if the partner wants it, but it's archaic.

2.  A student described one of the parties, "Mary" (the CEO of our hypothetical MathWhiz LLC) as an "expert."

COMMENT: Not a great idea (for Mary): The other side might argue later that Mary had held herself out as an expert when she really wasn't, and that this supposedly constituted fraud in the inducement.

3.  Several students wrote variations on, e.g., "Gigunda desires for MathWhiz to analyze data, and MathWhiz desires to do so."

COMMENT: Not the best phrasing, because the rest of the contract can speak for itself — and in any case, the parties' subjective desires don't enter into contract interpretation except in cases of a lack of meeting of the minds or mutual mistake.

29.4. Signature blocks — how to draft them (notes)

Contracts generally get "signed" in some fashion; under U.S. law, contract signatures can take a variety of forms, as discussed in the commentary below.

Note: As first-year law students learn, a so-called unilateral contract can be formed without signatures from both parties if an unrevoked, otherwise-eligible offer is accepted by performance. Example: Alice posts handbills on light poles, offering a $100 reward for the return of her missing cat, "Fluffy." If Bob finds Fluffy and returns her to Alice, then Bob's performance constitutes completion of the contract and obligates Alice to pay Bob the reward money.

Contents:

29.4.1. Precede with a concluding paragraph? (Nah.)

Some conventional contracts, with the signature blocks at the end of the contract, precede the signature blocks with a concluding paragraph such as the following:

    To evidence the parties’ agreement to this Agreement, each party has executed and delivered it on the date indicated under that party’s signature.

    AGREED:

Concluding paragraphs such as the first option above aren't needed. Here's why:

  • First, it's overkill: There are other ways of proving up that The Other Side in fact delivered a signed contract to you — for starters, the fact that you have a copy in your possession that bears (what at least purports to be) The Other Side’s signature.
  • Second, at the instant of signature, a past-tense statement that each party "has delivered" the signed contract is technically inaccurate — and even more so at the moment when the first signer affixes his (or her) signature.

But: If you see this kind of language in a draft prepared by the other side, then don't change it (as discussed in 8.11).

29.4.2. Signature dates

DCT note: I usually draft signature blocks with blanks for the signers to hand-write the date signed; see the example shown at 29.2.1.

It's usually better not to type in the expected date of signature. That's because one or more parties might sign on a different date. Moreover, if signature is delayed, a pre-typed signature date could help an unscrupulous signer to passively — but still fraudulently — backdate the contract (see 29.1.9).

    "Signed on the dates indicated below"

    "Signed December 12, 20xx"

For similar reasons relating to backdating, it's better not to type a purported date in the preamble:

    "This Agreement is made effective the last date signed, as handwritten in the signature blocks, between …."

    "This Agreement is made effective December 31, 20xx between …."

    "This Agreement is made December 31, 20XX, between …."

Relatedly: I also try to avoid leaving a blank space in the preamble for the effective date:

    "This Agreement is made December [an underlined space], 20XX, between …."

That's because the parties might well neglect to fill in the date, meaning that the contract gets signed with the blank space still there.

(This is an example of the R.O.O.F. principle: Root Out Opportunities for [Foul]-ups!)

29.4.3. Corporate- and LLC signature blocks

The signature blocks shown at 29.2.1 (repeated below) are for different types of organization — on the left is a signature block for when the signer’s name and title are known; on the right, when not:

• Note that each of those signature blocks starts out with the word "AGREED:" in all-caps and followed by a colon — possibly including the abbreviation for the signing party, shown as "Licensor" and "Licensee" above.

• Each organization’s signature block lists the organization’s full legal name followed by the word "by" and a colon.

• Date signed: Each signer should hand-write the date signed, for reasons discussed at the commentary to 29.1.9.

• Printed name blank line: In signature blocks with blank lines, be sure to include a space for the printed name, because the signatures of some people are difficult to read.

• Title: In any signature block for an organization, be sure to include the signer’s title, to establish a basis for concluding that the signer has authority to sign on behalf of the organization; if the employee’s title includes the word "president," "vice president," "manager," or "director" in the relevant area of the business, that might be enough to establish the employee’s apparent authority (concerning which, see 29.5.3).

29.4.4. Signature blocks for individuals

If an individual is a party to the contract, the signature block can be just the individual’s name under an underscored blank space.

Example:

AGREED:

………………………………
Jane Doe

………………………………
Date signed

But you might not know the individual signer’s name in advance, in which case you could use the following format:

AGREED:

………………………………
Signature

………………………………
Printed name

………………………………
Date signed

29.4.5. How to set forth signers' names in signature blocks

The examples below are more or less a convention, but it's usually a good idea to defer to the individual signer's preference.

Jane Doe

Ms. Jane Doe

Jane Doe, Esq. (even if Jane is a lawyer)

Jane Doe, Ph.D. (even if Jane holds that degree)

Jane Doe, M.D. (physicians do seem to like including those post-nominal letters)

29.4.6. Special case: Signature block for a limited partnership

In many U.S. jurisdictions, a limited partnership might be able to act only through a general partner, in which case a signature block for the limited partnership might need to include the general partner’s name. And the general partner of a limited partnership might very well be a corporation or LLC; in that case, the signature block would be something like the following:

AGREED: ABC LP, by:
ABC Inc., a Texas corporation,
general partner, by:

………………………………
Ronald R. Roe,
Executive Vice President

………………………………
Date signed

On the other hand, in some jurisdictions, a limited partnership might be able to act through its own officers; for example, Delaware’s limited-partnership statute gives general partners the power "to delegate to agents, officers and employees of the general partner or the limited partnership …." Del. Code § 17-403(c) (emphasis added).

In such cases, the signature block of a limited partnership might look like the signature block of a corporation or LLC, above.

Caution: A limited partner who, acting in that capacity, signs a contract on behalf of the limited partnership could be exposing herself to claims that she should be held jointly and severally liable as a general partner. (Of course, some general partners also hold limited-partnership investment interests and thus are limited partners in addition to being general partners.)

29.4.7. Include company titles for client relations, too

Including company titles is highly advisable to help establish apparent authority, as discussed above. But there's another reason to do so: If your client is a company, then some individual human, typically an officer or manager of the company, will be signing on behalf of the client. In that situation, the client’s signature block in the contract should normally state that it’s the company that is signing the contract, not the individual human in his- or her personal capacity — with the attendant personal liability.

To be sure, if your client is the company and not the human signer, then technically you’re under no professional obligation to make sure that the human signer is protected from personal liability. But it’s normally not a conflict of interest for you to simultaneously look out for the human signer as well as for the company; doing that can give the human signer a warm fuzzy feeling about you, which is no bad thing.

Caution: A lawyer might find herself dealing with an employee of a client company in a situation where the interests of the employee and the company diverge or even conflict. One example might be an investigation of possible criminal conduct such as deceptive backdating of a contract (discussed at 29.1.9). In circumstances such as those, the lawyer should consider whether she should affirmatively advise the employee, preferably in writing, that she’s not the employee’s lawyer — conceivably, the lawyer might even have an ethical obligation to do so.

29.4.8. Try to keep signature blocks on the same page

DCT note: I like to keep all of the text of a signature block together on the same page (which might or might have other text on it). That looks more professional than having a signature block spill over from one page onto the next. This can be done using Microsoft Word’s paragraph formatting option, "Keep with Next."

29.4.9. Should counsel sign for clients? (Usually: No.)

A lawyer for a party entering into a contract normally won’t want to be the one to sign the contract on behalf of her client, because:

FIRST: Signing a contract for a client could later raise questions whether, in the negotiations leading up to the contract, the lawyer was acting as a lawyer or as a business person. This could be an important distinction: in the latter case, the lawyer’s private communications with her client might not be protected by the attorney-client privilege and thus might be subject to discovery by third parties (which is never a good look, in terms of client relations).

SECOND: From a client-relations perspective, if your client's contract later "goes south," you might not want your signature on the contract. Example: The general counsel of pharmaceutical giant Novartis was painfully reminded of this after he signed a consulting contract with Michael Cohen, formerly the personal lawyer for Donald Trump; as a result, the GC lost his job when the contract attracted unwanted publicity to the company. See Prashant S. Rao and Katie Thomas, Novartis’s Top Lawyer is Out Amid Furor Over Payments to Michael Cohen (NYTimes.com May 16, 2018) (emphasis added).

29.4.10. Terms after the signature block?

Any provisions after the signatures should be clearly incorporated by reference Example: In a Kentucky case, a for-profit school used a one-page contract.

  • The basic terms and signature blocks were on the front of the page.
  • Additional terms and conditions — including an arbitration provision — were on the back of the page, as part of what the state supreme court described as "a sea of plain-type provisions dealing with tuition refunds, curriculum changes, … and arbitration." (Emphasis in original.)

Citing a state statute requiring signatures to be at the end of an agreement, the supreme court said that the arbitration clause was not part of the school's agreement. See Dixon v. Daymar Colleges Group, LLC, 483 S.W.3d 332, 345-46 (Ky. 2015) (affirming denial of motion to compel arbitration).

(See also Protocol 3.7, concerning incorporation by reference.)

29.5. Signature authority (notes)

29.5.1. The business context

Suppose that Alice signs a contract on behalf of ABC Corporation. The contract is with XYZ Inc. Question: Is it reasonable for XYZ to assume that Alice's signature makes the contract binding on ABC? The answer will depend on whether Alice had authority to do so — either actual authority or apparent authority.

29.5.2. Lack of signature authority can kill a contract

A party might not be able to enforce a contract if the person who signed on behalf of the other party did not have authority to do so. This happened, for example, in a federal-contracting case:

  • An ammunition manufacturer signed several nondisclosure agreements (NDAs) with the U.S. Government and, under the NDAs, disclosed allegedly-trade-secret technology to the government.
  • The manufacturer later sued the government for breaching the NDAs by disclosing and using the trade secrets without permission.
  • Under the applicable regulations, the specific individuals who signed the NDAs on behalf of the government did not have authority to bind the government.

The court majority held that the government was not bound by some of the NDAs — and thus the government was not liable for its disclosure and use of the manufacturer's trade secrets. A dissenting judge argued that the senior Army officer who signed a particular NDA had at least apparent authority [discussed at 29.5.3]; therefore, said the judge the government should have been bound by the NDA. See Liberty Ammunition, Inc. v. United States, 835 F.3d 1388, 1401-02 (Fed. Cir. 2016); id. at 1403-05 (Newman, J., dissenting).

Here’s another example from the Illinois supreme court: A landlord sued its defaulting tenant, a union local. The landlord won a $2.3 million judgment against the union in the trial court, only to see the award thrown out in the state supreme court. Why? Because in signing the lease, the union official had not complied with the requirements of the state statute that authorized an unincorporated association to lease or purchase real estate in its own name. See 1550 MP Road LLC v. Teamsters Local No. 700, 2019 IL 123046, 131 N.E.3d 99.

29.5.3. Apparent authority can save the day … but for whom?

Typically under the law in the U.S., anyone with apparent authority may sign a contract (or an amendment to a contract) on behalf of a party.

Note: Apparent authority can arise only from some action on the part of the person supposedly granting authority; it can't arise solely from the actions of the person taking the action.

Hypothetical example:

  • Alice negotiates a contract with Bob, but the contract is between Bob and Carol.
  • Alice signs the contract — but she does so purportedly as Carol's agent.

In that situation, Carol won't be bound by the contract unless she has given Bob reason to believe that Alice had authority to represent Carol. See, e.g., Caribbean Sun Airlines Inc. v. Halevi Enterprises LLC, No. 199, 2024 (Del. Jan. 21, 2025) (reversing trial-court judgment).

Example: The Fifth Circuit affirmed a bankruptcy-court holding that an LLC was not bound by a contract to sell the LLC's future receivables: While the contract was signed by one of the LLC's members, the LLC's operating agreement imposed procedural hurdles for that member to enter the company into transactions — and the member didn't have apparent authority because the LLC had done nothing to give the impression that the member had authority. See Spin Capital LLC v. Jet Oilfield Services, No. 25-50206 (5th Cir. Dec. 4, 2025) (affirming district court's affirmance of bankruptcy-court judgment).

29.5.4. Consider ruling out apparent authority (more or less)

A contract can generally negate apparent authority to sign by clearly putting the parties on notice that only certain people have authority to agree to amendments.

Such language is often seen, e.g., in car dealers' sales contracts, requiring manager- or vice-presidential signature on amendments — presumably, the purpose is to preclude buyers from claiming that a low-on-the-totem-pole sales representative had agreed to non-standard terms. Such language typically says, in all-caps, something along the lines of, "NO PERSON HAS AUTHORITY TO MODIFY THESE WARRANTIES ON BEHALF OF THE DEALER EXCEPT A VICE PRESIDENT OR HIGHER."

Here's a hypothetical example from our MathWhiz-Gigunda simulation:

Gigunda WILL NOT BE BOUND by this Agreement unless it is signed by its vice president for research.

So: Some drafters might want to be explicit about who does not have signature authority — and perhaps: authority to sign specific things — to help preclude another party from claiming to have relied on the apparent authority of other would-be signers.

29.5.5. A company's internal signature policies won't matter

A corollary to the above is that a party's internal signature-authority policies likely won't matter if the party has given the outside world sufficient reason to believe a particular individual has authority to sign and hasn't notified the other party otherwise. Example: Something like happened, for example, in a Tenth Circuit case in which a company claimed — unsuccessfully — that it was supposedly not bound by a contract signed by one of its executive vice presidents ("EVPs"). See Digital Ally, Inc., v. Z3 Tech., LLC, 754 F.3d 802, 809, 812-14 (10th Cir. 2014).

In another case, a fired employee sued his former company, claiming that he had been promised a bonus by the company's  "vice president of operations," who was the son of the company's owners. In the lawsuit, the fired employee conceded that the son did not have actual authority to promise a bonus, but argued instead — and a jury agreed — that the son had apparent authority. On appeal, the appellate court noted that:

Texas law recognizes that a company's placement of an officer or employee in a certain position will provide the agent with apparent authority to bind the company in usual, customary, or ordinary contracts that a reasonable person would view as being consistent with an agent's scope of authority in that position. Elaazami v. Lawler Foods, Ltd., No. 14-11-00120-CV, slip op. at part III (Tex. App. Houston [14th Dist.] Feb. 7, 2012) (citing cases; emphasis added).

29.5.6. An "officer" title won't necessarily indicate signature authority

The Restatement (Third) of Agency notes that just because a person holds the title of president or vice president of a company, that doesn't mean the person necessarily has authority to make commitments on behalf of the company. See Restatement (Third) of Agency § 3.03 cmt. e(4) (2006), quoted in Elaazami v. Lawler Foods, Ltd., No. 14-11-00120-CV, slip op. at n.6 (Tex. App—Houston [14th Dist.] Feb. 7, 2012) (reversing judgment notwithstanding verdict; company's vice president of operations had apparent authority [see 29.5.3] to make oral promise of bonus payment to later-fired employee).

29.5.7. The gold standard: A board resolution — but not for everyday

The gold standard of corporate signature authority is probably a certificate, signed by an officer of the corporation, that the corporation’s board of directors has granted the signature authority.

You’ve probably seen paperwork that includes such a certificate if you’ve ever opened a corporate bank account. The resolution language — which is invariably drafted by the bank’s lawyers— normally says something to the effect that the company is authorized to open a bank account with the bank in question and to sign the necessary paperwork, along with many other things the bank wants to have carved in stone. See this example of a corporate board resolution and officer certificate (contracts.OneCLE.com).

But a large- or publicly-traded company won't want to bother its board approval to get approval for for routine contracts or other everyday business.

Pro tip: When I was in-house, we sometimes had to provide board resolutions for bank signature cards and things like that. So with our outside corporate counsel's blessing, we came up with this workaround:

  • The CFO (chief financial officer) was a board member; I was the secretary of the corporation, in addition to being vice president and general counsel, and thus was also an officer of the corporation.
  • The full board adopted a resolution that (1) created a subcommittee of one, namely the CFO, and (2) delegated, to that subcommittee, the power to approve bank board resolutions that had been approved by the company's general counsel (me).
  • So, whenever a bank asked for a board resolution: If I was OK with the resolution, the CFO would initial the signature line for the certificate of adoption; then I'd sign the certificate and return it to the bank. (Or maybe it was the other way around — I don't remember exactly.)

That approach worked: I don't recall that we ever got any pushback from a bank or otherwise had any trouble from the approach. (I doubt anyone at a bank ever looked at anything other than whether there was ink on the signature line and a title indicating that the signer was an officer, and so mentally "checked the box.")

29.5.8. Special case: Legal limits on signature authority

By statute, a contract with an LLC or other organization might not be enforceable, even if signed by an "officer" or by a "manager." That could be especiall true if publicly-available articles of organization expressly deprive the signer of such authority — thus putting the public "on notice" of the lack of authority.

Example: This happened in Spin Capital (5th Cir. 2025): A member of an oilfield-services LLC, one Owen, held a 43% ownership interest in the company. Owen signed a contract to sell $4.5 million of the LLC's future receivables to a financing company for $3 million. The LLC's operating agreement stated that Owen could not enter the LLC into transactions without the consent of at least one of the LLC's other members. The Fifth Circuit affirmed dismissal of the financing company's claim against the LLC on grounds that Owen did not have actual authority to commit the LLC to the sale, and the LLC had done nothing to indicate that Owen had apparent authority. See Spin Capital LLC v. Jet Oilfield Services, No. 25-50206 (5th Cir. Dec. 4, 2025) (affirming district court's affirmance of bankruptcy-court judgment).

Example: This happened in a Utah case where:

  • One manager of a two-manager LLC signed an agreement granting, to a tenant, a 99-year lease on a recreational-vehicle pad and lot.
  • But there was a problem: The LLC’s publicly filed articles of organization stated that neither of the two company’s managers had authority to act on behalf of the LLC without the other manager’s approval.

A state appeals court held that the tenant had been on notice of the one manager’s lack of authority to grant the lease on just his own signature alone — and so the lease was invalid. See Zions Gate RV Resort, LLC v. Oliphant, 2014 UT App 98, 326 P.3d 118, 121 ¶ 8, 122-23. The court remanded the case for trial as to whether the LLC had later ratified the lease.

29.5.9. Or, just take the risk on signature authority?

DCT note: I once represented a MathWhiz-like client that was negotiating an agreement with a Gigunda-like customer.

  • Gigunda's attorney filled in a name and title for Gigunda's signer: It was a fairly-senior Gigunda individual contributor with a Ph.D degree. We'll call her "Sarah" (not her name).
  • In a private email to a MathWhiz senior executive, I raised the question of Sarah's authority to sign the agreement.
  • The MathWhiz executive responded that he'd had been dealing exclusively with Sarah in negotiating the agreement and understood why Gigunda wanted her to sign the agreement.
  • The MathWhiz executive added that Sarah's boss (whom the MathWhiz executive knew well) had been copied on all of the emails going back and forth.
  • The MathWhiz executive also said that MathWhiz had a longstanding good history with Gigunda.

After learning all of the above, my recommendation to MathWhiz was that we not ask Gigunda to have someone else sign the agreement (i.e., someone other than Sarah), because:

  • doing so might offend Sarah;
  • it would very-likely delay getting to signature;
  • it'd produce little or no real reduction in MathWhiz's business risk.

MathWhiz did as I recommended, accepting Sarah's signature as being on behalf of Gigunda. (It worked out fine: The parties carried out the contract to everyone's satisfaction.)

29.6. Initialing pages and/or provisions – trouble?

29.6.1. The law might require initials for particular provisions

Some contract drafters like to include, in the margins, blank lines for parties to initial particular provisions. This might be required by law to make particular types of provision enforceale; for example, as discussed in the commentary at 3.1.4.12, section 2-209(2) of the (U.S.) Uniform Commercial Code provides as follows:

(2) A signed agreement which excludes modification or rescission except by a signed writing cannot be otherwise modified or rescinded, but except as between merchants such a requirement on a form supplied by the merchant must be separately signed by the other party.

(Emphasis added.)

29.6.2. Maybe don't include lines for initialing particular provisions?

As an example of the "Don't Needlessly Raise the Bar for Your Client" Principle (see 8.13): Unless specifically required by law, it's not a great idea to include separate lines for initialing a particular provision of a contract. That's because it's too easy for a party to forget (or intentionally fail) to initial the provision; that could lead to a dispute about whether the party in fact agreed to the non-initialed provision — which in turn could lead to costly litigation, perhaps with unpredictable outcomes.

(See 21.1.32.2 for examples.)

29.6.3. Initialing pen-and-ink changes

In the modern era of electronic documents and signatures, it's not often that parties make handwritten changes on a paper copy of a contract. If that's to be done, however, each party's signer should initial and date each such change.

For an example of changes made in red comment bubbles in a PDF document, see a 2019 blog post by Ken Adams — where a commenter points out that the changes should have been initialed, otherwise it might be tough to prove that the changes were part of the signed document.

[TO DO someday: Image]

29.6.4. Initialing each hard-copy page?

Suppose that "Alice" is signing a hard copy of a contract, whether for herself or on behalf of her company. It's not the worst idea (but not strictly necessary) for Alice to initial the hard copy at the bottom-right corner of each page and keep a photocopy of the entire contract with the initialed pages. That can be useful if, for example:

  • different parties sign different versions of the contract, which has been known to happen, as discussed at 29.9.1; or
  • another party surreptitously changes the contract language after Alice signs, and then claims that Alice agreed to the change — that, too, has been known to happen, as discussed at Protocol 3.15 — in which case Alice can produce her photocopy of the pages she initialed, without the surreptitious change.

29.7. Notarizing a document

29.7.1. One form of "notarizing" means acknowledging that you signed.

A document such as a deed to real property might include, after the signature blocks, a space for a notary public (or other official) to sign a certificate that the signer:

  1. appeared before the notary;
  2. presented sufficient evidence to establish his or her identity (e.g., a driver's license, a passport, etc.); and
  3. stated to the notary that he or she (the signer) signed the document.

(The other common form of notarizing is the jurat, or oath by the signer, discussed at 29.7.3.)

29.7.2. A notary acknowledgement reduces the chance of forgery.

When a document signer "acknowledges" his- or her signature as summarized above, the certificate and official seal of the notary public (or other authorized official) serve as legally-acceptable evidence that the signer's signature isn't a forgery — that is, evidence that the signed document is authentic. This is sometimes referred to as making the document self-authenticating or self-proving.

And indeed, the law likely requires a certificate of acknowledgement by an authorized official if the document is to be recorded in the public records so as to put the public on notice of the document's contents.

Example: Suppose that "Alice" is selling her house.

–  To do so, Alice will pretty much always sign a deed and give the signed deed to "Bob," the buyer.

–  Bob will normally want to take (or send) the signed deed to the appropriate government office to have the deed officially recorded — that way, under state law, third parties will be on notice that Bob now owns Alice's house.

But how can the government office, or for that matter a later title researcher, know for sure that "Alice's" signature on the deed to wasn't a forgery?

The answer is that under the laws of most states, Alice's deed to Bob won't even be eligible for recording in the official records unless the deed includes an acknowledgement certificate — signed by a notary public or other authorized official — that Alice complied with the three numbered requirements at the beginning of this subclause.

(And if Alice signed the deed in a special capacity, such as executor of her father's estate, then the notary's certificate will usually say that, too.)

This acknowledgement procedure allows the civil servants who must record Alice's deed to look at the deed and have at least some confidence that the signature on it isn't a forgery.

(A notary acknowledgement also makes it considerably difficult for Alice to later try to disavow her signature.)

In some jurisdictions, Alice is not required to actually sign the deed in the presence of the notary; she need only state to the notary that yes, she did in fact signed the deed. See generally Kelle Clarke, Notary Essentials: The Difference Between Acknowledgments And Jurats (NationalNotary.org 2020).

29.7.3. Must the document's signer swear to its truth?

Not usually: The type of notary certificate we're discussing here — an "acknowledgement" — is a different type of certificate than a jurat. When a jurat is used in a document, the notary or other official certifies that the signer of the document personally declared — after first promising to tell the truth, under penalty of perjury — that the document's contents were true.

29.7.4. What wording must appear in a notary acknowledgement?

State law usually specifies just what wording must appear in an acknowledgement signed before a notary. For example, under Texas law, an individual's signature can be acknowledged using a short form:

State of Texas

County of xxx

This instrument was acknowledged before me on (date) by (name or names of person or persons acknowledging).

[notary signature block and seal]

29.7.5. The notary must (usually) keep a permanent record

Once Alice has done as required, the notary will sign the certificate and imprint a seal on the deed. The notary might do this with a handheld "scruncher" that embosses the paper of the deed, or instead with an ink stamp; this will depends on the jurisdiction.

Typically, the notary is also required to make an entry in a journal to serve as a permanent record. Pro tip: It's useful to confirm that the notary in fact did this — a family friend of the present author once won a lawsuit by getting a notary to admit, on cross-examination, that she (the notary) had not made such an entry in the "well-bound book" that was then required by state law.

(State law might allow some or all of this process to be done electronically.)

29.7.6. Other officials might also be able to "notarize"

By statute, certain officials other than notaries public* are authorized to certify the authenticity of signatures in certain circumstances. For example, Texas law gives the power to certify signature acknowledgements:

  • to district-court and county-court clerks, and
  • (in certain limited cases) to commissioned officers of the U.S. armed forces,

among others. See Tex. Civ. Prac. & Rem. Code § 121.001.

*  Incidentally, it's not "notary publics" — the noun notary is pluralized as notaries, the adjective public is left alone. (It's the same with attorneys general.)

29.7.7. Notaries can't serve if they have a conflict of interest.

A notary public generally can't sign a certificate if the notary has a conflict of interest, e.g., notarizing something for an immediate-familly member. See generally, e.g., American Society of Notaries, Conflicts of Interest (2008).

But under Texas law, when a notary public is an employee of a corporation, the notary is allowed to certify the acknowledgement of a signature on a document in which the corporation has an interest, unless the employee is a shareholder who owns more than a specified percentage of the stock of the corporation. See Tex. Civ. Prac. & Rem. Code § 121.002.

29.7.8. A flawed notarization can cause problems.

Parties will want to double-check that the notary "does the needful" (an archaic but useful expression) to comply with statutory requirements.

Example: a New York case, Michelle and Gary Galetta signed a prenuptial agreement.

  • When Gary filed for divorce some years later, Michelle challenged the prenup.
  • The court, agreeing with Michelle, voided the prenup, because the notary certificate for Gary's signature didn't recite that the notary public had confirmed his identity — even though it was undisputed that the couple's signatures were authentic, and there was no accusation of fraud or duress.
  • The state's highest court said that the notarization requirement was important because it "necessarily imposes on the signer a measure of deliberation in the act of executing the document." Galetta v. Galetta, 21 N.Y.3d 186, 189-90, 191-92, 991 N.E.2d 684, 969 N.Y.S.2d 826 (2013) (affirming summary judgment that prenup was invalid).

29.7.9. Lawyers might not want to notarize client documents

In many states it's easy to become a notary public. Some lawyers themselves become notaries so that they can certify the authenticity of clients' signatures on wills, deeds, and the like.

Keep in mind, though: If a lawyer notarizes a document, then the lawyer might be called someday to testify in a court proceeding about a signed document. For example, the lawyer-notary might have to explain how he or she confirmed the signer's identity if that information isn't stated in the lawyer's notary records. That in turn might disqualify the lawyer from being able to represent the client whose signature was certified.

(As a practical matter, though, that one point might not be too much of an issue, because the lawyer might already have to testify by virtue of having participated in the events leading up to the signing of the document.)

Note

See, e.g., Tex. Civ. Prac. & Rem. Code § 121.001; Tex. Discipl. R. Prof. Conduct 3.08 ("Lawyer as Witness").

29.7.10. Notarization by videoconference?

Drafters needing a notary certificate should check whether applicable law requires a personal appearance before a notary (or other official), or whether that can be done remotely by videoconference. See generally National Notary Association, Remote Notarization: What You Need to Know (nationalnotary.org Jun. 23, 2020) (showing states with remote-notary laws). For a survey of remote notarization laws, see Brett J. Natarelli, Madelaine A. Newcomb, and A. Paul Heeringa, Notarization and Property Recording Requirements in the Age of Social Distancing, 76 Bus. Lawyer 607, 611 (AmericanBar.org 2021).

Remote notarization was an issue during the COVID-19 pandemic, during which the Texas governor announced an emergency suspension of some laws and authorized notarization of certain wills and real-estate documents. See Texas Secretary of State, Notice of Suspension of Statutes (sos.state.tx.us, undated); also this order (notarization of real-estate instruments).

29.8. Side letters: Caution!

When a supplier and customer sign a sale contract, it can be tempting also to have the supplier provide the customer with a "side letter" that gives the customer the right to return the product and get a refund. That, though, could get the customer ensnarled in a securities fraud case against the supplier; that, in turn, could disqualify the customer from utilizing some securities-offering procedures — as well as hindering the future employment prospects of the individuals involved.

Example: In 2003, the SEC announced that it had filed a civil lawsuit against a former customer sales executive who allegedly placed a $7 million order with a supplier — with a secret side letter giving the customer the right to cancel its purchase.

Example: In 2007, a former CEO was sentenced to four years in prison for securities fraud that included, among other things, the use of secret side letters to "cook the books." See Ex-Enterasys CEO sentenced to four years (NHBR.com 2007); see also, e.g., Joel M. Cohen and Mary Kay Dunning, Does that settle it? Well, maybe not, Nat'l L.J., Apr. 9, 2012 (GibsonDunn.com) (scroll down to "Obligations and Risks"); Boris Feldman, What to do When You Find the Side Letter: Guidelines for CEO’s, CFO’s, and Audit Committee Members in Investigating Accounting Fraud (BorisFeldman.com).

29.9. Signatures: More pro tips

29.9.1. Caution: Are all signed pages "final"? (Use a running header)

().  It's very common for parties in separate locations to manually sign separate copies of a paper contracts and then to email a PDF image (or, old-school, to FAX) just their signed signature pages to each other. If only the signed signature pages of a contract will be exchanged, the parties should make sure it's clear that everyone is signing the same version of the document — otherwise, the contract might not be binding.

Example: Not doing this proved fatal to a party's case in Delaware, where the parties had exchanged signature pages — but the pages were from two different drafts, only one of which included the crucial provision (a noncompetition covenant). The chancery court held that there had been no meeting of the minds — and thus there was not a valid contract. See Kotler v. Shipman Assoc., LLC, No. 2017-0457-JRS (Del. Ch. Aug. 27, 2019) (rendering judgment for company).

Pro tip: To help establish which draft of a document is which: Strongly consider including, on each page of the Con­tract, a running header or -footer that identifies the document and its version.

Example: In a draft confidentiality agreement between ABC Corporation and XYZ LLC, a running header could read "ABC-XYZ Confid. Agrmt. ver. 2019-03-01 15:00 CST" — where the date and time at the end are hand-typed, and not in a "field" that the word processing software will automatically update.

(Including such a running header can also help avoid confusion when the parties are discussing a draft of the agreement, by allowing the parties to make sure that everyone is looking at the same draft.)

29.9.2. Set a deadline for signature?

A document could state a deadline for signature by one or more specified parties, so that the document would not be binding on any party unless each such specified party has signed and delivered the document: • to each other party stated in the deadline • on or before the close of business, at that other party's place of business, on the stated deadline date.

This is based on a September 2021 suggestion by an anonymous commenter at redline.net (a lawyers' online forum), who notes that "[this] is standard practice in real estate contracts where the buyer submits a signed contract to the seller."

29.9.3. Afterwards: Combine all signed pages into one document?

It's a good idea to combine • the PDF of the unsigned agreement, and • the PDFs of the signed signature pages, into a single "record copy" PDF.

Then: Email the combined, record-copy PDF to all concerned: The email will serve as a paper trail to help establish the authenticity of the record copy.

29.9.4. Signatures checklist

Here's a checklist of selected signature-related items for contract drafters and reviewers — of course, this checklist isn't a substitute for advice from a licensed attorney:

  • Are all parties are signing the same, final version of the document? (29.9.1)
  • Does each signature block correctly state either: (i) the signing party's full legal name, such as "ABC, Inc., a Texas corporation," or (ii) a previously-defined "nickname" for the party, such as "Buyer"? (29.4.3 through 29.4.6)
  • For each organization that is a party to the contract: Does the signature block includes the title of the individual signer within the organization, such as "Vice President of Business Development," to help establish the apparent authority of that individual signer to bind the organization?
  • In addition, does the contract itself not state that only certain people have authority to sign on behalf of one or more parties — either that, or such a person is signing on behalf of each such party? (29.5.4).
  • Does each party's signature block includes a blank line labeled "Date signed," not just "Date"? (29.4.2).

Does the law, and/or a party's publicly-filed organizational documents, restrict who has authority to sign on behalf of a particular type of organizational party (trust, LLC, etc.)? (29.5.8)

30. Drafting: Key readability rules

… the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old [contract terms] as part of the effort to write new [contract terms]. … [Therefore,] making it easy to read makes it easier to write. Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship. Martin was writing about software but it's just as true about contracts.

Contents:

30.1. Plain language is "a thing" elsewhere

The trend toward plain language isn't limited to purely-legal documents. Contract drafters can learn from legendary investor Warren Buffett:

When writing Berkshire Hathaway’s annual report, I pretend that I’m talking to my sisters. I have no trouble picturing them: Though highly intelligent, they are not experts in accounting or finance. They will understand plain English, but jargon may puzzle them. My goal is simply to give them the information I would wish them to supply me if our positions were reversed. To succeed, I don’t need to be Shakespeare; I must, though, have a sincere desire to inform. U.S. Securities and Exchange Commission, Plain English Handbook at 2 (Aug. 1998) available at https://goo.gl/DZaFyT (sec.gov) (emphasis added).

30.2. Copy-and-paste: Dangerous when mindless

Don't just copy and paste language from an old contract without thoroughly reviewing it: At a minimum, any reader who's paying attention will stop short and wonder, what?

Example: One very-public "fail" on that score occured in the UK's negotiation of its Brexit deal; as reported by the BBC:

References to decades-old computer software are included in the new Brexit agreement, including a description of Netscape Communicator and Mozilla Mail as being "modern" services. Experts believe officials must have copied and pasted chunks of text from old legislation into the document. The references are on page 921 of the trade deal, in a section on encryption technology.

It also recommends using systems that are now vulnerable to cyber-attacks. The text cites "modern e-mail software packages including Outlook, Mozilla Mail as well as Netscape Communicator 4.x." The latter two are now defunct — the last major release of Netscape Communicator was in 1997. See Cristina Criddle, Brexit deal mentions Netscape browser and Mozilla Mail (BBC.com Dec. 29, 2020) (formatting edited); see also, e.g., Ben Quinn, Obsolete software from 1990s features in Brexit deal text (TheGuardian.com Dec. 29, 2020).

30.3. Cross-references: Don't mess them up!

30.3.1. Word-processing software isn't always reliable

Another readability gotcha: Don't assume that word-processing software will reliably update a document's "automatic" internal cross-references between sections when editing the document to add new sections.

Example:

  • The original, correct cross-reference is, "See section 14.3" (where the number 14.3 is inserted by the software to match the section number).
  • During editing, a new section is added between section 8 and section 9.
  • This means that section 14.3 should now be section 15.3 — but don't count on it. (See below for a real-life example where a similar occurrence changed the course of a court case.)

That's one reason why this book is not written in Microsoft Word — but perhaps things are different now than when I started this project several years ago ….

30.3.2. Courts notice errors in cross-referencing

Example: In a Delaware contract lawsuit, a pair of screwed-up cross-references in the contract led to major problems for the parties. One of the parties — the father of another party — had signed the contract only for purposes of two, referenced sections of the contract — including "Section 7.5." Unfortunately for Dad, there was no Section 7.5 in the contract. So, the court deferred until trial the question of Dad's liability under the contract — meaning that Dad would have to incur the expense, burden, and uncertainty of trying the case. Labyrinth, Inc. v. Urich, No. 2023-0327, part II.B.2, slip op. at text accompanying nn.248, 255 (Del. Ch. Jan. 25, 2024).

The screwed-up cross-references also hurt the plaintiff — one of them led to the court's refusing to grant preliminary injunctive relief against the son-defendant for allegedly breaching a noncompetition covenant. See id. at part II.C, text accompanying n.261.

Great: More expense and uncertainty for all concerned, because the drafters (presumably) relied on word-processing software to update their cross-references — which shouldn't be a problem, but there you go. (Hat tip: Matthew Dedon, who posted an alert at the invaluable lawyer site redline.net.)

Example: In a 2024 UK court of appeals case, the court noted acidly that "The Agreement is riddled with cross-referencing errors of the most basic kind." Topalsson GmbH v Rolls-Royce Motor Cars Ltd., [2024] EWCA Civ 1330 at n.2.

30.3.3. Use special software to check cross-references?

I've not used any of these products, so YMMV (Your Mileage May Vary):

•  Contract Companion by Litera looks for cross-referencing errors, among other things. The company seems to have a lot of related products.

•  CrossCheck365 appears to be a Microsoft Word add-in that will • use an "Expando" feature to turn "spaghetti clauses" into "macaroni" (breaking up wall-of-words clauses into outlines); and • check cross-references.

(DCT note: Long ago I briefly knew one of the company's people, lawyer Steve Gullion, which I learned when he reached out to me after I posted the above software references in the daily class plan for my Contract Drafting course. Steve noted that "we have a two-minute video that's just about the Expando feature: https://www.youtube.com/watch?v=26N-SZ605kw".)

30.4. Don't Repeat Yourself (D.R.Y.) in critical areas

30.4.1. D.R.Y. for numbers

Don’t spell out a number in words and then restate the number in numerals. Example:

    More than three hundred million (300,000,000) people live in the United States.

    More than 300,000,000 people live in the United States.

    More than 300 million people live in the United States.

This is an example of what software people call "D.R.Y. — "Don't Repeat Yourself." It can be a very expensive mistake if: • a term is revised during negotiation, but • the revision is not made in every place that the term occurs.

Some real-world examples are set out below.

Example: In a Delaware case, a party lost its rights under an intellectual-property license agreement because it cured a breach, but did so too late:

  • The license agreement allowed the other party to terminate if a material breach was not cured within "fifteen (30) days" after notice of the breach. (Emphasis added.)
  • The breaching party initially refused to cure the breach, so the non-breaching party terminated the agreement shortly after 15 days had elapsed from the notice of breach.
  • The breaching party had a change of heart after receiving the notice of termination and proceeded to cure the breach.
  • The court said, in effect, "sorry, too late" — because the word fifteen took precedence over the numerals 30.

Example: In a Texas case, a D.R.Y. mistake once cost a bank $693,000:

  • The bank sued to recover $1.7 million from defaulting borrowers and their guarantor.
  • In the trial court, the bank won a summary judgment to collect from the guarantor.
  • Unfortunately for the bank, the appeals court reversed, because the loan documents referred to the amount borrowed as "one million seven thousand and no/100 ($1,700,000.00) dollars" (capitalization modified, emphasis added).
  • The appeals court held that, under standard interpretation principles, the words, not the numbers, controlled; thus, the amount guaranteed was only $1.007 million, not $1.7 million. See Charles R. Tips Family Trust v. PB Commercial LLC, 459 S.W.3d 147 (Tex. App.–Houston [1st Dist.] 2015) (reversing and remanding summary judgment in favor of bank).

(You probably wouldn't want to be the junior associate or paralegal who oversaw the document preparation in that case.)

Example: One of my clients was contemplated being acquired. A potential acquiring party proposed a confidentiality agreement (a.k.a. nondisclosure agreement a.k.a. NDA).

  • The text said, in part: "… said [confidentiality] obligations shall survive for a period of five (3) years from the later of the following: …."
  • I fixed the inconsistency even though I hadn't created it. (For more on whether to fix others' ambiguities, see 7.9.4.)

Example: From a tweet: A legal-review software product flagged the term "One Million, Seven Hundred and Fifty Million Dollars ($1,750,000) of Security Deposits …."

Pro tip: Here's an example of one way to avoid the D.R.Y. problem:

    Bob will pay Alice one hundred thousand dollars ($100,000.00) for the House, with fifty percent (50%) due upon signing of this Agreement.

    Bob will pay $100,000 for the House, with 50% due upon signing of this Agreement. (Note how the ".00" is omitted from the dollar amount because it's not needed.)

30.4.2. D.R.Y. for fill-in details ("variables")

If you're using a schedule (see 29.2.2) to specify deal-specific, fill-in-the-blank details — the names of the parties; the sale price of an asset; the rent for a lease, etc. — then:

  1. define a term for each of those details, e.g., "Buyer," "Purchase Price," etc; and
  2. elsewhere in the document, use that defined term exclusively (perhaps with a cross-reference to the schedule).

Example:

SCHEDULE:

Buyer: ABC Corporation
Seller: XYZ Inc.
Purchase Price: USD $100 million†

* * *

    ABC will pay XYZ USD $100,000,000.

    The Buyer will pay the Seller the Purchase Price.

Note the spelling out of "million"

30.4.3. But some repetition can be useful

Repetition can be used (cautiously) to emphasize a point. Part of the contract drafter's mission is to remind and persuade (see 2.3), not merely to slavishly follow drafting guidelines like this one.

30.5. The "partner check-in rule"

As a junior lawyer, there will be times when you will — and should — be uncertain about what to do in a contract draft, or how to phrase something. For example:

• When drafting a contract for a client, you might wonder whether to include a forum-selection clause (see Protocol 21.12), because doing so might poke the bear, leading to problems in negotiation (the other side might repond by insisting that their home city be the exclusive forum instead).

• In reviewing another party's draft contract, you might see that the draft includes a forum-selection provision that requires all litigation to take place exclusively in the other side's home jurisdiction; you wonder whether the client will be OK with that.

To keep your client and your supervising partner happy (not to mention your malpractice carrier) here's what you do:

1.  Check in with your supervising partner — or, if you're the person who deals with the client, check in with the client — about the issue that concerns you, which here is the forum-selection provision.

Important: Have a well-thought-out recommendation for what to do about the issue of concern, with reasons for your recommendation. This is true even if the recommendation is limited to advising the client to consider Factors X, Y, or Z in making a decision. That will give the partner or client a concrete proposal to consider, instead of just wondering about the issue in the abstract. (Also, superiors and clients tend to think, not unreasonably: Bring me [proposed] solutions, not just problems.)

BUT: Don't just pick up the phone and call the partner or client every time an issue pops into your head. No one likes to be repeatedly interrupted with questions. Instead:

  1. Make a list of things to discuss with the partner or client.
  2. Schedule a meeting or phone call (or Zoom- or Teams call).
  3. Use your list as an agenda — perhaps sending it to the client or partner in advance.

Pro tip: In Microsoft Word, you can add comment bubbles in the margin of a draft contract. Those comment bubbles can then be used as the discussion agenda during what's known as a "page-turn" conference call, where the participants go page by page through a draft contract or other document. (Ditto for discussing comments with the other side during a negotiation call.)

2.  Then, document that you advised the client or partner — in matter-of-fact, non-defensive language — either:

  • in an email to the partner or client, and/or
  • in Word comment bubbles in a draft that you sent to the partner or client, as discussed in the pro tip above.

Here's a real-life example: A startup-company client's CEO — let's call him "Bob" — once asked me to review a draft confidentiality agreement ("NDA") that had been sent to him by a potential customer, a giant, globally-known company that we'll call XYZ Corporation. At the time, I'd been working with Bob for many years at several different companies. Here's the email I sent Bob about XYZ's NDA form, only lightly edited — and the bold-faced type is pretty much what I did in the email to help Bob skim the text:

Hi Bob — BLUF (Bottom Line Up Front) [see 2.6]: This NDA is probably OK for what you need here, but there are a few things you might want to consider, and that we can discuss if you want.

1.  XYZ has included its infamous "residuals clause" [see 5.3.33.5] in this NDA, which is basically a blank check for XYZ to use whatever information you give them them — in section xx, it says:

"Neither of us can control … what our representatives will remember, even without notes or other aids. We agree that use of information in representatives’ unaided memories in the development or deployment of our respective products or services does not create liability under this agreement or trade secret law, and we agree to limit what we disclose to the other accordingly." (Emphasis added.)

BUSINESS QUESTION: Are you OK with giving XYZ that kind of permission for what you'll be disclosing to them?

2.  Any litigation would have to be in [XYZ's headquarters city].

Meh.

3.  There's no requirement that a recipient must return or destroy confidential information.

I'm fine with that; I've come to think that omitting such a requirement is the most-sensible approach. [See 5.4.]

Otherwise XYZ's draft looks OK.

Notice what I did here: After a quick BLUF headline, I pointed out three issues — in numbered paragraphs — for which I wanted Bob's input, and I made recommendations as to the second two; Bob would ultimately make the decisions what business risks to accept.

This took a tiny bit more time for me to write. But it Served the Reader by making Bob's job easier.

Epilogue: Bob emailed me back and asked for a phone conference with him and another executive from his company. That time, I didn't follow up with an email to confirm the plan of action we'd agreed on, but if I had done so, the confirming email might have been along the following lines:

Bob, confirming part of our phone conversation today: XYZ NDA has an exclusive forum-selection provision that requires all litigation to be in [city]; under the circumstances I think that's probably an acceptable business risk.

Please let me know if you'd like to discuss this any further.

(Emphasis added.) Note how, in the first sentence, I left a paper trail for future litigation counsel, recording the facts: (i) that Bob and I had a phone conversation, and (ii) when that conversation occurred, which would help litigators construct a timeline of events — an important part of any lawsuit.

Note also my use of the term "probably an acceptable business risk," signaling that this was a business judgment for Bob to make.

IMPORTANT: Be careful about how you phrase your emails and other comments to the client or partner: Assume that anything you put in writing might someday be read by an adversary and possibly used against your client — or against you — in litigation.

Sure, in some circumstances the attorney-client privilege should protect at least some of your written comments from discovery. But the privilege has its limits; moreover, the privilege can be waived — possibly inadvertently — or the privilege might even be pierced (e.g., by the crime-or-fraud exception).

30.6. The "partner preference rule"

Students: When you're new to law practice and it comes to purely-stylistic preferences, do it the way your supervising partner wants.

Suppose you're a new lawyer in a law firm:

  • A partner in your firm assigns you to draft a contract.
  • In reviewing your draft, the partner tells you to write out, for example, one million seven hundred thousand dollars ($1,700,000.00), instead of the simpler $1.7 million — even though this book strongly recommends against doing so (messing this up once cost a Dallas-area lender $693,000, as explained at "Don't Repeat Yourself" at 30.4).

You can and should alert the partner to the potential problem with the partner's instruction. But if the partner still wants to do it that way, don't fight the partner over this — it's not a hill to die on, and you could annoy the partner and perhaps even harm your career prospects at the firm.

There'll be plenty of time to use your own preferred style as you get more experienced and the partners increasingly trust you to handle things on your own — and especially if you start to bring in your own clients.

In the meantime, of course, you'll have to be extra-careful not to make the kind of mistakes that can result from some of these suboptimal style practices, as discussed in this book.

30.7. Perfect is the enemy of good enough - but …

When it comes to contracts, clients tend overwhelmingly to believe that "perfect" is the enemy of "good enough." Most clients generally would far prefer to get an "OK" contract that covers the reasonably-likely contingencies, and get it signed quickly; they don't want to waste calendar time (nor to pay your legal fees), to get a gold-plated contract that covers unlikely and/or low-risk possibilities.

Of course, part of the problem is that hindsight is 20-20: If an "unlikely" possibility in fact comes to pass and causes problems for the client, guess where fingers might well be pointed for not having covered that possibility in the contract? No one said law practice was always easy ….

30.8. Consider Q&A subheadings to identify specific scenarios

30.8.1. Introduction

Here's a scalable, repeatable way to write contract clauses as easier-reading "sound bite" sections: As an aid to thinking —

  1. figure out what specific user-scenario questions are answered by the clause; and
  2. use those questions as possible the subheadings for separate sound-bite sections about the scenarios — write the subheadings (usually) as the questions themselves, or (sometimes) as succinct answers or at least summaries of the answers.

30.8.2. A real-world example

As a before-and-after illustration, let's break up the following real-world spaghetti clause, which is from the merger agreement where Hewlett-Packard (HP, Inc.) acquired well-known headset manufacturer Plantronics.

(Students, feel free to just skim this to get the idea.)

BEFORE:

SECTION 1.01   The Merger.  On the terms and subject to the conditions set forth in this Agreement, and in accordance with the General Corporation Law of the State of Delaware (the “DGCL”), Merger Sub shall be merged with and into the Company at the Effective Time. At the Effective Time, the separate corporate existence of Merger Sub shall cease and the Company shall continue as the surviving corporation (the “Surviving Corporation”) and shall succeed to and assume all the rights and obligations of Merger Sub in accordance with the DGCL. At the election of Parent, any direct or indirect wholly owned subsidiary of Parent may be substituted for Merger Sub as a constituent corporation in the Merger, in which event the parties shall execute an appropriate amendment to this Agreement in order to reflect the foregoing; provided that in no event shall the Company be required to amend this Agreement in any manner that would reasonably be expected to prevent, impair or delay the Closing or otherwise reduce the Merger Consideration or impair the other benefits expected to accrue to the holders of Company Common Stock pursuant to the transactions contemplated by this Agreement. The Merger, and the other transactions contemplated by the Transaction Agreements are referred to in this Agreement collectively as the “Transactions.”

AFTER, with Q&A subheadings:

SECTION 1.01   The Merger.

1.01(a)  When will the Merger take effect?

The Merger will take effect at the Effective Time [defined elsewhere].

1.01(b)  What will happen to Merger Sub when the Merger takes effect?

When the Merger takes effect:

(1)  Merger Sub will be merged with and into the Target;

(2)  The Target shall will continue as the surviving corporation (the “Surviving Corporation”); and

(3)  Merger Sub's separate corporate existence shall will cease.

1.01(c)  What will happen to Merger Sub's assets, etc.?

When the Merger becomes effective, the Target will succeed to all the rights, and assume all the obligations, of Merger Sub in accordance with the DGCL [Delaware General Corporation Law].

1.01(d)  Could the Buyer switch Merger Sub with another subsidiary?

The Buyer may elect to replace the Merger Sub, as a party to the Merger, with any other direct or indirect wholly owned subsidiary of the Buyer; if that occurs, then that other subsidiary will be merged into the Target instead of Merger Sub.

1.01(e)  An appropriate amendment will be needed if a replacement does occur

If Merger Sub is replaced with another Buyer subsidiary as provided in subdivision (d), THEN: The parties will negotiate and sign an appropriate amendment to this Agreement in order to reflect the replacement.

1.01(f)  Are there limits on what the Target
must agree to in the replacement amendment?

The Target need not agree, in the replacement amendment to this Agreement, to any change that would reasonably be expected:

(1) to prevent, impair or delay the Closing or otherwise reduce the Merger Consideration, nor

(2) impair the other benefits expected to accrue to the holders of Target Common Stock pursuant to the transactions contemplated by this Agreement.

Writing in this style will doubtless seem awkward — at first. But soon you'll get the hang of it.

And if you want, you can later edit the subheadings into a conventional terse format.

30.8.3. Advantage: Better spotting and thinking through "what if" situations

There's another potential advantage of Q&A subheading format: When you phrase a subheading as a question, it prompts the reader to think of other possible answers — more so than simply presenting an answer. That's likely to be useful in doing the "business planning" for a contract.

It also seems likely that posing a question helps the reader more-quickly grasp the topic of the relevant clause or section, reducing the reader's cognitive burden. See Izaias Cavalcanti, The psychology that makes people skip reading contracts – and how to change it (WorldCC.com 2025).

Tangentially: Amazon reportedly does product- and service development with a "work backwards from the customer experience" approach, doing the business planning by writing and refining mock press releases and frequently-asked questions documents; Amazon refers to this as the company's "PR/FAQ" approach. See Colin Bryar and Bill Carr, Working Backwards: Insights, Stories, and Secrets from Inside Amazon ch. 5 (2021), by two longtime Amazon senior executives, now co-founders of Working Backwards LLC), excerpted at An insider look at Amazon's culture and processes (AboutAmazon.com); Werner Vogels, AWS Lambda turns 10: A rare look at the doc that started it (AllThingsDistributed.com 2024) (case study by Amazon's chief technology officer).

(For more on business planning in contract negotiation, see 27.)

30.8.4. Should I rewrite another party's draft in this way?

Nah — that'd likely just offend the other lawyer, which isn't a great way to start a negotiation. (Instead, just break up long spaghetti clauses as shown above; see 8.11.8 for more on revising other parties' drafts.)

31. Field notes: Legal matters

Contents:

31.1. Antitrust law basics

31.1.1. Introduction: The Sherman Act, section 1

The following draws heavily from the Ninth Circuit's opinion in Aya Healthcare Servs., Inc. v. AMN Healthcare, Inc., 9 F.4th 1102, 1109-09 (9th. Cir. 2021) (affirming summary judgment applying rule of reason in dismissing antitrust claim under Sherman Act § 1; plaintiff failed to establish existence of genuine issue of material fact whether no-solicitaiton provision had a substantial anticompetitive effect that harmed consumers in relevant market). I've used a free hand in editing the text and have omitted most of the extensive citations. No copyright is claimed in the text of the court's published opinion.

31.1.2. What conduct does Section 1 prohibit?

Section 1 of the Sherman Act [named after Sen. John Sherman, pictured] bars "[e]very contract, combination in the form of trust or otherwise, or conspiracy, in restraint of trade or commerce among the several States."

31.1.3. But doesn't every contract "restrain" trade?

Yes — but the Supreme Court has interpreted Section 1 to outlaw only unreasonable restraints.

31.1.4. What are "horizontal" vs. "vertical" restraints?

Restraints subject to Section 1 are generally categorized as horizontal or vertical:

  • A horizontal restraint is an agreement among competitors on the way in which they will compete with one another.
  • Vertical restraints are restraints imposed by agreement between firms at different levels of distribution.

31.1.5. How do courts assess the reasonableness of restraints?

Courts employ two different standards to determine whether a particular restraint is unreasonable:

1.  The first standard involves a factual inquiry commonly known as the "rule of reason." The rule of reason weighs legitimate justifications for a restraint against any anticompetitive effects.

Nearly every vertical restraint is assessed under the rule of reason.

We conduct a fact-specific assessment to distinguish between:

  • restraints with anticompetitive effect that are harmful to the consumer and
  • restraints stimulating competition that are in the consumer's best interest.

2.  The second standard is the per se standard, which recognizes that a small group of restraints are unreasonable per se because they always or almost always tend to restrict competition and decrease output. Such agreements or practices are conclusively presumed to be unreasonable because of their pernicious effect on competition and lack of any redeeming virtue.

Typically only horizontal restraints qualify as unreasonable per se.

However, not all horizontal restraints are analyzed pursuant to the per se standard.

DCT note: In late 2024, a federal district court held that "algorithmic pricing" of apartment rents, facilitated by a provider of revenue-management software, was part of a horizontal conspiracy that was subject to the per-se rule: "The combination and conspiracy allegedly involved (a) a set of vertical agreements between Yardi Systems, Inc., and each individual [apartment-owner] lessor defendant for the use of Yardi's revenue management software, (b) a continuing horizontal agreement between and among the lessor defendants to provide their commercially sensitive information to Yardi, to use Yardi's revenue management software, and to implement the recommendations generated, and (c) a shared understanding that Yardi would use the information provided to recommended rental rates above what would be earned in a competitive market." See Duffy v. Yardi Systems, Inc., 758 F. Supp. 3d 1283, 1289 (W.D. Wash. 2024) (denying defendants' joint motion to dismiss).

Relatedly: In August 2024, the Department of Justice and the attorneys general of eight states filed a civil antitrust lawsuit against RealPage Inc. alleging similar conduct.

The notion of a "rule of reason" is the opposite of a "per-se rule" or "bright-line rule," and means that the outcome might be affected by differences in facts (or in online parlance: YMMV, Your Mileage May Vary). See generally Rule of reason (Wikipedia.org).

In a 2024 paper, professors Mark Lemley, of Stanford Law,) and Michael Carrier, of Rutgers Law, argue in effect that the rule of reason might be just window dressing (my words):

Given that the rule of reason is often said to be at the center of antitrust law, and that balancing is at the heart of the rule of reason, it is quite surprising to discover that courts almost never do any actual balancing of harms and benefits.

Indeed, balancing has become so rare that in the Supreme Court’s two most recent articulations of the rule of reason test, it omitted the actual balancing of anticompetitive harms and procompetitive benefits altogether! Mark A. Lemley and Michael A. Carrier, Rule or Reason? The Role of Balancing in Antitrust Law (SSRN.com 2014) (extra paragraphing added).

31.1.6. What sorts of "horizontal" restraints might be OK?

Under the "ancillary restraints" doctrine, a horizontal agreement is exempt from the per se rule, and analyzed under the rule-of-reason, if it meets two requirements.

These requirements are that the restraint must be (1) subordinate and collateral to a separate, legitimate transaction, and (2) reasonably necessary to achieving that transaction's pro-competitive purpose.

"Naked restraints" are categorically not "ancillary restraints." Thus, naked horizontal restraints are always analyzed under the per se standard.

A restraint is naked if it has no purpose except stifling of competition.

Some examples of these restraints include agreements among actual or potential competitors to fix prices or divide markets.

31.1.7. One type of "section 1 violation": Unlawful (horizontal) price-fixing

Sometimes it might seem tempting to agree with a competitor to divvy up customers, or to keep your prices at an agreed level, or to take turns submitting the winning bid in response to customers' requests for proposal ("RFPs").

Those activities, though, can lead to indictment and prosecution by federal- or state authorities for violation of the antitrust laws.

Example: The German airline Lufthansa and the British airline Virgin Atlantic blew the whistle on a price-fixing scheme by a total of 21 non-U.S. airlines, including British Airways, Qantas, and Korean Air. The U.S. Department of Justice prosecuted, resulting in

  • a total of some $1.7 billion in fines; and
  • four airline executives being sentenced to prison terms in the U.S. (link) (link)

Authorities might go for low-hanging fruit: Instead of trying to prove up an antitrust violation (a complex task), they might bring charges of obstruction of justice, akin to prosecuting Al Capone for tax evasion.

Example: A British executive, after being extradited to the U.S., was sentenced to 18 months in prison and a $25,000 fine for conspiring to obstruct a price-fixing investigation (link).

For more information the Department of Justice has a useful antitrust primer that explains many of the relevant concepts.

31.1.8. Vertical- and hybrid price-fixing might be OK …

The following discussion is adapted from Winn-Dixie Stores, Inc. v. Eastern Mushroom Mktg. Coop., Inc., 81 F.4th 323, 328 (3d Cir. 2023); no copyright is claimed in the opinion text:

Not every agreement to restrain trade violates the antitrust laws. Because some cases are more obvious than others, the law has evolved to use different tests depending on the closeness of the question.

  • At one end of the spectrum are arrangements that can be condemned as illegal per se, or—as in the case of horizontal agreements—at least so likely to be unlawful that just a "quick look" is enough to recognize that anticompetitive effects may be presumed.
  • At the other end of the spectrum are arrangements that are plainly lawful.
  • And in between lie the vast majority, where careful scrutiny is necessary to decide.

In this category—which includes purely vertical agreements, as well as hybrid agreements — the "quick-look" approach is inapt, and the plaintiff has the initial burden of showing anticompetitive effect under the "rule of reason."

The central—and dispositive—question in this case is which framework applies.

Appellant Winn-Dixie Stores brought suit against Appellees—the Eastern Mushroom Marketing Cooperative, Inc. (EMMC), its individual mushroom farmer members, and certain downstream distributors—claiming their price-fixing agreement violated § 1 of the Sherman Act. 15 U.S.C. § 1.

The District Court instructed the jury to apply the "rule-of-reason" test, and the jury returned a verdict in Appellees' favor.

Winn-Dixie contends this was error, and had the judge applied the "quick-look" approach and instructed the jury to simply presume anticompetitive effects, it would have found Appellees' agreement to be an unlawful restraint of trade. As plaintiff, Winn-Dixie understandably would have preferred the lower burden of proof.

But because this hybrid scheme involved myriad organizational structures with varying degrees of vertical integration, the Court was right to apply the rule of reason.

And because, under that more searching inquiry, the evidence at trial was sufficient to sustain the jury's verdict, we will affirm the judgment in favor of Appellees.

Emphasis, extra paragraphing, and bullets added.

31.1.9. … but might not be worth the hassle

Let's suppose that a client wants you to draft an agreement with vertical price fixing a.k.a. resale price maintenance.

Sure, such an agreement might be legal.

But even so, litigating the issue might cost the client a lot of time and money.

Does the client really want to take the chance?

31.2. Bankruptcy Code of 1978 (notes)

31.2.1. The automatic stay against termination (etc.)

Consider the situation where A wants to terminate its contract with B. Under section 365(e)(1) of the (U.S.) Bankruptcy Code of 1978, if B files a petition for protection under the bankruptcy laws — or if B's creditors file an "involuntary" petition against B — then that filing creates an "automatic stay," prohibiting A from taking any of several forms of contract termination (as well as various other actions).

The rationale here is that termination of a contract could jeopardize the orderly reorganization or liquidation of B's business. In the bankruptcy proceeding, B is referred to as the "debtor," and B's business and assets are referred to as "the estate" of the debtor.

(The basics of this subject are usefully explained in Robert L. Eisenbach III, Are "Termination On Bankruptcy" Contract Clauses Enforceable? (Cooley.com 2007), https://perma.cc/PV6N-VFTC.)

Even though such termination-for-bankruptcy provisions are unenforceable in the U.S., lawyers keep including them in contracts anyway. The usual rationale is that U.S. bankruptcy law might not apply (e.g., in a non-U.S. transaction), and who knows, Congress might repeal that part of the Code (unlikely).

As an "in the wild" example of such a provision, see a Honeywell purchase-order form at http://perma.cc/CUV6-NKTY, which states as follows:

The solvent party [sic] may terminate this Purchase Order upon written notice if the other party becomes insolvent or if any petition is filed or proceedings commenced by or against that party relating to bankruptcy, receivership, reorganization, or assignment for the benefit of creditors.

Pro tip: Don't say that "the solvent party may terminate," as in the Honeywell example just above, because if the terminating party is also insolvent, then a court might hold that the party wasn't entitled to terminate — and so the termination was itself an "own goal" breach of the contract — as discussed in more detail in the commentary at § 18.6.1.1.

31.2.2. Ipso-facto terminations are likewise unenforceable

Likewise unenforceable under 11 U.S.C. § 365(e)(1) are so-called ipso-facto clauses, where the debtor's entering into bankruptcy proceedings would automatically terminate the contract (with certain exceptions in subsection (e)(2)). For an example and extensive citations, see a paper (undated) at the Web site of the Bryan Cave law firm.

31.2.3. Preference-payments refunds in bankruptcy

Here's a not-uncommon situation, especially during economic downturns:

  • A customer places an order with a supplier.
  • In due course, the customer pays the supplier's invoice in due course.
  • But: Within the next 90 days, the customer files for protection under the bankruptcy laws.

In that situation, the supplier might be compelled by law to refund Customer's invoice payment; this is referred to as an "avoidable preference." See, e.g., Coles v. Glaser, 2 Cal. App. 5th 384, 389, 205 Cal. Rptr.3d 922 (2016) (with extensive citations). See also, e.g.: Patricia Dzikowski, The Bankruptcy Trustee and Preference Claims (Nolo.com; undated); Kathleen Michon, Pre-Bankruptcy Payments to Creditors: Can the Trustee Get the Money Back? (Nolo.com; undated); the guaranty language in Cooperatieve Centrale Raiffeisen-Boerenleenbank, B.A. v. Navarro, 25 N.Y.3d 485, 488, 36 N.E.3d 80, 15 N.Y.S.3d 277 (2015).

To be sure: The supplier would have the right to contest its obligation to refund the customer's payment, for example by showing that the payment was made in the ordinary course of business. But contesting a preference action can be difficult and costly; that's because, under bankruptcy law, the supplier would have to successfully jump through some evidentiary hoops to show that it was entitled to keep the customer's payment.

And in any event, as a practical matter many avoidable-preference cases are settled; in the above situation:

  • The customer's "estate" (a bankruptcy term) would likely settle for less than a complete refund of what the customer had paid the supplier.
  • In return, the supplier would give the customer a partial refund so as to avoid the expense and hassle of jumping through the required proof hoops in bankruptcy court.

That's where the supplier would want to be able to invoke a third party's guaranty of payment: In many guaranties, the guarantor would be on the hook to reimburse the supplier for the supplier's refund to the customer — and probably for the supplier's associated legal expenses as well, if the guaranty said so. (For an example of bankruptcy-reimbursement language along similar lines, see paragraph 7 of a Bank of America guaranty form.)

31.3. Baskets for losses (notes)

In some transactions such as mergers and acquisitions, so-called "baskets" are used to allocate responsibility for losses and claims, with responsibility not triggered until losses reach a stated amount. See generally, e.g., Dan Avery, What's Market: Indemnity Baskets (GoulstonStohrs.com).

31.3.1. The deductible basket

To illustrate, let's use a hypothetical example with made-up numbers for a so-called "deductible basket":

AGGREGATE LOSSES:
Less than $100: Buyer is responsible.
$100 and up: Seller is responsible

Here's a variation on the deductible basket:

AGGREGATE LOSSES:
Less than $100: Buyer is responsible.
$100 to $10,000: Seller is responsible.
More than $10,000: Buyer is responsible.

31.3.2. The tipping (or first-dollar) basket

Another variation is the so-called "tipping basket" (sometimes called the "first-dollar basket"):

AGGREGATE LOSSES:
Less than $100: Buyer is responsible.
$100 and up: Seller is responsible, for all losses (even the first $100).

31.4. Buy-sell agreements (rough notes)

A "buy-sell" procedure is related to the ancient "divide and choose" procedure, sometimes known as "I cut, you choose," by which children can evenly divide a cookie between them.

Something like this procedure is seen in the Book of Genesis, when Abram (later Abraham) and his kinsman Lot agree to separate, and by agreement, Abram allows Lot to choose which part of the Promised Land to claim and settle in. See Gen. 13:8-10; see also, e.g., Abraham and Lot's conflict.

Buy-sell agreements are often used for breakups of small companies. Suppose that a company has two owners, "Fred" and "Ginger," who find that they can no longer get along. A buy-sell agreement requires (let's say) Fred to offer to buy out Ginger's share of the company so that she'll be the one to exit the business and leave Fred as the sole owner — but then Ginger gets to decide whether —

  • to accept Fred's buy-out offer and leave the business; or
  • instead, to require Fred to sell out to her — on the terms that Fred had proposed to her.

This gives Fred a powerful incentive to offer fair terms to Ginger — because if Fred's terms aren't fair, then Ginger can turn the tables on him and kick him out of the business instead of exiting the business herself.

A buy-sell agreement is somewhat akin to baseball arbitration, which likewise encourages parties to make fair offers to settle disputes, as discussed at 21.11.

Optional further reading:

  • Both buy-sell agreements and last-offer arbitration ("baseball arbitration"; see Protocol 21.11) could be thought of as examples of what the late philosopher John Rawls referred to as "the veil of ignorance."
  • Mahler (2017) urges not including provisions for the accepting party to demand revision of the price.

31.5. Click-wrap and browse-wrap agreements (notes)

31.5.1. Background

1.  "Click-wrap agreements": When a user installs software on a computer, or signs up for an online service, very often the user must click on a button or link that says (in effect) "I agree"; the click purportedly signifies that the user — and the user's company — are agreeing to detailed terms and conditions.

2.  "Browse-wrap agreements": An online service might also include a purported agreement that the user supposedly agrees to: (i) by continuing to take an action, e.g., continuing to browse a Web site, or (ii) by not taking other action, e.g., by not leaving a Web site.

For convenience, here we'll refer to the terms of either type of agreement as simply "Wrap Terms."

31.5.2. Some case law

The enforceability of click-wrap and browse-wrap agreements has been often litigated; see generally the posts of law professor Eric Goldman — who knows pretty much what there is to be known on this subject — and his colleagues at his Technology & Marketing Law Blog.

For a UK perspective, see the court of appeal's discussion in Parker-Grennan (UK App. 2024), discussed by Blest & Shaw (2024).

Often, Wrap Terms will be unobjectionable, addressing matters such as not making unreasonable use of an online service, not trying to steal other users' data, and the like.

But sometimes, Wrap Terms will be like a supplier's order confirmation, setting out the supplier's wish list for ground rules — and sometimes a supplier's click-wrap or browse-wrap agreement will contain terms and conditions that affect the parties' negotiated deal.

So, in § 3.3.6 of Protocol 3.3, the "are rejected" language is intended to preclude Wrap Terms from becoming part of the Con­tract when they address matters that are covered (explicitly or implicitly) in the Con­tract.

31.5.3. Wu v. Uber: A road map to enforceability?

In its Wu v. Uber opinion, New York's highest court blessed the process that Uber used to amend its online terms of service to incorporate an arbitration provision:

We now turn to the application of these principles to Uber's January 2021 terms of use. Only a few days before plaintiff purportedly agreed to the terms, she received the following email:

The headline of the email, "Updated Terms of Use," and the large text immediately beneath it clearly informed plaintiff that she would soon "be asked to review and agree to [Uber's] updated terms [of use]."

Moreover, the email specifically advised plaintiff that the terms would include, among other subjects, "changes to the Arbitration Agreement."

The terms were accessible through several hyperlinks, including a large black button at the very top of the email specifically labeled "Review terms," and the text "Terms of Use" in the first line of the first paragraph, which was distinguished from the black text surrounding it by the signature blue font indicating a hyperlink.

Finally, the text of the email expressly advised plaintiff how she could manifest assent to the terms, i.e., by tapping "Confirm" on a pop-up window that would automatically appear when she opened the Uber application on her smartphone. The email was written in plain language.

Only a few days later, Uber's January 2021 terms of use were presented to plaintiff by means of a clickwrap process*—a means of acquiring binding assent from consumers that has been *widely upheld by courts across the country.

As previewed in the email, plaintiff was presented with the following pop-up screen when she opened the Uber app on her smartphone:

The headline and the larger text in the center of the screen—"We've updated our terms" and "We encourage you to read our updated Terms in full"—*clearly advised* plaintiff that she was being asked to agree to a contract with Uber.

The terms themselves were again made accessible by a hyperlink on the words "Terms of Use," which were formatted in large, underlined, blue text.

A reasonably prudent user would have understood from the color, underlining, and placement of that text, immediately beneath the sentence "encourag[ing]" users to "read [the] updated Terms in full," that clicking on the words "Terms of Use" would permit them to review those terms in their entirety.

Finally, Uber provided plaintiff with an unambiguous means of accepting the terms by including a checkbox, "Confirm" button, and bolded text expressly stating that, "By checking the box, I have reviewed and agree to the Terms of Use."

It is undisputed that plaintiff checked and box and clicked the "confirm" button. Wu v. Uber Techs., Inc., 43 N.Y.3d 288, 292-93, 260 N.E.3d 1060, 2024 NY Slip Op. 05869 (cleaned up, emphasis and extra paragraphing added).

31.6. Consumer contracts (notes)

DCT note: This is where I'm "saving string" for possible future use.

Anthony Glosson and Ross Speier, Mind the Fine Print: CFPB Warns Against Use of Unenforceable Terms and Conditions (JDSupra.com 2024).

31.7. Efforts clauses (notes)

31.7.1. Why do drafters use "efforts" clauses?

Contract drafters often say that a party will make [something] efforts:

  • when they don't want to take the time to negotiate a specific standard of performance — especially if their clients simply don't know what the standard should be in as-yet undetermined future circumstances, and they don't want to spend the time to try to figure it out;
  • in the case of commercially reasonable efforts: to emphasize that the term requires what business people would regard as reasonable efforts and - as an alternative to the stronger commitment of best efforts (see Protocol 9.1).

31.7.2. Problem: The lack of clarity in the case law

In Delaware's 2024 Fortis Advisors case, Vice Chancellor Will noted that "there is no agreement in case law over whether [efforts clauses] create different standards. Delaware courts have viewed variations of efforts clauses—particularly those using the term 'reasonable'—as largely interchangeable." Fortis Advisors LLC v. Johnson & Johnson, No. 2020-0881-LWW, slip op. at text acc'g n.350 (Del. Ch. Sept. 4, 2024).

Likewise, in the 2010 Citri-Lite case, a federal court in California noted that that "[t]here is no settled or universally accepted definition of the term commercially reasonable efforts." Citri-Lite Co. v. Cott Beverages, Inc., 721 F. Supp. 2d 912, 926 (E.D. Cal. 2010) (denying defendant's motion for summary judgment; cleaned up). After trial, the court elaborated on this observation, with citations; see findings of fact and conclusions of law after bench trial, slip op. at 45, aff'd, No. 11-17609 (9th Cir. Nov. 21, 2013) (unpublished).

Similarly, the Southern District of New York — after extensively reviewing case law — remarked that "New York case law interpreting other efforts clauses, including best efforts and reasonable efforts clauses, is anything but a model of clarity." Holland Loader Company, LLC v. FLSMidth A/S, 313 F. Supp. 3d 447, 469 (S.D.N.Y. 2018) (after bench trial, holding that defendant had failed to use commercially-reasonable efforts).

31.7.3. Would (a quick) summary judgment be available? (Maybe not.)

It will often be "a factually intense issue" whether a party has complied with an obligation to exert particular efforts — and thus it frequently happens that a court will deny summary judgment, necessitating a costly trial, as happened in Citri-Lite, cited above, and in other cases. See also, e.g., MY Imagination, LLC v. M.Z. Berger & Co., No. 17-1218 (6th Cir. Feb. 16, 2018) (reversing and remanding summary judgment in favor of defendant); Organo Gold Int'l v. Aussie Rules Marine Serv. Ltd., 416 F. Supp. 3d 1369 (S.D. Fla. 2019) (denying summary judgment in case involving golfer Greg Norman); PPD Enterpr., LLC v. Stryker Corp., No. 4:16-CV-0507 (S.D. Tex. Nov. 1, 2017) (denying summary judgment).

31.7.4. Inward vs. outward focus: A real-world example

Example: In a 2023 Seventh Circuit decision, the contract in suit provided an example of an extremely-detailed definition of "commercially reasonable efforts"; that definition focused "inward" on the buyer's own practices, as opposed to an "outward" focus on industry standards for what would be done by similarly-situated business. See Russell v. Zimmer, Inc., 82 F.4th 564, 566-70 (7th Cir. 2023) (affirming dismissal for failure to state a claim upon which relief could be granted).

31.7.5. Use "comparables"? (Maybe not.)

Industry standards or other "comparables" might not be helpful: In a 2024 Delaware case, the contract in suit defined "commercially reasonable efforts" as "the exercise of such efforts and commitment of such resources by a company with substantially the same resources and expertise as [the defendant], with due regard to the nature of efforts and cost required for the undertaking at stake." Vice Chancellor Glasscock characterized this definition as "unusual" and remarked that "[a]fter trial, I find this method unworkable; no exemplar companies operate under the actual conditions of Defendants, who, I note, are also different from one another as to their circumstances." Himawan v. Cephalon, Inc., No. 018-0075, text acc. nn.44, 165 (Del. Ch. Apr. 30, 2024) (holding that defendants had not breached their obligation to comply with contract's commercially-reasonable efforts provision).

The court went on:

"Due regard" for the "efforts and costs" means that Defendants may eschew development where the circumstances reasonably indicate, as a business decision, that they not go forward. This includes all the costs and risks involved, including the milestone payments and the opportunity costs faced by Defendants, as evidenced by the provision that the reasonableness be measured against the actions expected of a company with "substantially the same resources and expertise" as the buyer.

That is, if a reasonable actor with faced with the same restraints and risks would go forward in its own self-interest, the buyer is contractually obligated to do the same. Id. (emphasis in original, extra paragraphing added).

31.7.6. Pro tip: Agree to a process instead?

Outside of the context of efforts, a party seeking to prove (or disprove) the reasonableness of a transaction, contract term, decision, etc., might want to focus on the process by which the transaction, etc., came into being. Example: In its 1990 West Texas Transmission decision, the Fifth Circuit remarked that "[w]here two sophisticated businesses reach a hard-fought agreement through lengthy negotiations, it is difficult to conclude that any negotiated term placed in their contract is commercially unreasonable." West Texas Transmission, LP v. Enron Corp., 907 F.2d 1554, 1563 (5th Cir. 1990) (affirrming district court's refusal to grant specific performance of right of first refusal) (extensive citations omitted).

This suggests that, when it comes to commercially-reasonable efforts, if parties can't (or don't want to take the time to) specify what outcome they want, then perhaps they could agree instead to a reasonable process that they will use later to decide what the outcome will be, such as the escalation clause at Protocol 21.11.

31.7.7. Whose burden is it to define the extent of efforts required?

A party that sues for breach of an efforts obligation might need to adduce specific evidence to educate the court about just what level of effort was required to meet the obligation in the particular circumstances — failing which, the court might dismiss the claim.

Example: The SDNY explained: "When the term 'commercially reasonable efforts' is not defined by the contract, courts in this district require the party seeking to enforce the efforts provision to establish the objective standard by which the breaching party's efforts are to be judged, in the context of the particular industry." Holland Loader Company, LLC v. FLSmidth A/S, 313 F. Supp. 3d 447, 472 (S.D.N.Y. 2018) (plaintiff proved breach of commercially-reasonable-efforts obligation but failed to sufficiently prove damages). See also, e.g., Shane Campbell Gallery, Inc. v. Frieze Events, Inc., No. 20-1535-cv (2d Cir. Dec. 17, 2020) (affirming summary judgment dismissing claim of breach (non-precedential summary order)); Tendyne Holdings, Inc. v. Abbott Vascular, Inc., No. 18-1070 (D. Del. Jun. 28, 2019) (granting Abbott's motion to dismiss); Terumo Americas Holding, Inc. v. Tureski, 251 F. Supp. 3d 317, 327-28 (D. Mass. 2017) (granting summary judgment dismissing claim of breach); Netologic Inc. v. Goldman Sachs Group, Inc., 2018 NY Slip Op 31409 (granting defendant's motion for summary judgment).

31.7.8. Some practical dangers of best-efforts obligations

Parties that agree to include a best-efforts obligation in a contract can get into costly disputes about whether particular actions satisfied the obligation. That's because:

–  With the benefit of plenty of time and 20-20 hindsight, litigation counsel — coached by a paid expert witness — will second-guess the choices that the obligated party made.

–  Then it might be up to randomly-selected jurors to decide the best-efforts question — and because jurors often aren't familiar with the relevant business environment, they might end up deciding, in part, on the basis of which witnesses they liked best.

31.7.9. Are "all reasonable efforts" required?

In its much-noted Williams Cos. decision, Delaware's supreme court held that "reasonable best efforts" required all reasonable steps. See Williams Cos. v. Energy Transfer Equity, L.P., 159 A.3d 264 (Del. 2017). The supreme court held that Williams Cos.'s counterparty Energy Transfer had indeed breached its obligation to make such efforts, but also that Energy Transfer had shown that its breach did not have a material effect.

All reasonable efforts is reportedly a common formulation in the UK and Australia as well. See generally, e.g., Menelaus Kouzoupis and Margaux Harris, "Best endeavours" vs "reasonable endeavours": Not two sides of the same coin (SHLegal.com 2020); Shawn C. Helms, David Harding, and John R. Phillips, Best Efforts and Endeavours – Case Analysis and Practical Guidance Under U.S. and U.K. Law (JonesDay.com 2007).

British Columbia's supreme court used the term "leaving no stone unturned." See Atmospheric Diving Systems Inc. v. International Hard Suits Inc., 1994 CanLII 16658, ¶¶ 63, 71-72 (BC SC), 89 B.C.L.R. (2d) 356 (reviewing English and Canadian case law).

BUT: The Seventh Circuit once remarked that "We have found no cases … holding that 'best efforts' means every conceivable effort …." Triple-A Baseball Club Assoc. v. N.E. Baseball, Inc., 832 F.2d 214, 228 (7th Cir. 1987).

Likewise, the First Circuit's California Pines opinion (citing the Second Circuit's Bloor opinion) held that: "Best efforts does not mean every conceivable effort. It does not require the promisor to ignore its own interests, spend itself into bankruptcy, or incur substantial losses to perform its contractual obligations." See also Coady Corp. v. Toyota Motor Distributors, Inc., 361 F.3d 50, 59 (1st Cir. 2004) (affirming rejection of dealership's claim that Toyota distributor had failed to use best efforts; citation omitted), likewise cited in California Pines. ]

Sometimes the discussion might be academic: A Texas court once remarked: "As a matter of law, no efforts cannot be best efforts." CKB & Assoc., Inc. v. Moore McCormack Petroleum, Inc., 809 S.W.2d 577, 581-82 (Tex. App.–Dallas 1990). (affirming summary judgment that defendant had failed to use its best efforts; citing Bloor).

31.7.10. Enforceability: Best efforts to do what?

A best-efforts clause might be unenforceable if it doesn't indicate the desired object of the efforts with sufficient clarity to allow a court to assess the obligated party's performance.

Example: In a Texas case, the buyer of a company had agreed, as part of the purchase agreement, to make earn-out payments to the seller; the buyer also committed to use its best efforts to operate the acquired business "in a manner that maximizes the Earn-Out Payments …." Affirming summary judgment in favor of the buyer, the court ruled that this best-efforts provision was unenforceable because "the contract at issue here lacks a clear set of guidelines against which [the buyer's] best efforts can be measured," and that what the contract did say on that score "is not enough to go on …." Spain v. Phoenix Elec. Co., No. 01-22-00656-CV, slip op. (Tex. App.–Houston [1st Dist] Mar. 7, 2024, no pet.).

Example: The Fifth Circuit threw out a fraudulent-inducement jury verdict against a party alleged to have never intended to use its best efforts to promote sales of specified products: "Because the 'best efforts' clause is too indefinite and vague to provide a basis for enforcement, the [plaintiff's] claim for fraudulent inducement, as a matter of law, cannot rest on the alleged breach of this clause coupled with an alleged intent not to perform." Kevin M. Ehringer Enterprises, Inc. v. McData Servs. Corp., 646 F.3d 321, 326 (5th Cir. 2011) (reversing judgment on jury verdict; citation omitted).

Counterexample: A party agreed to use best efforts to file and make effective a securities registration statement "as promptly as practicable" and "in the most expeditious manner possible." The Fifth Circuit held that this was sufficiently definite to support a claim for breach of the best-efforts obligation. See Herrmann Holdings Ltd. v. Lucent Techs., Inc., 302 F.3d 552, 559-61 (5th Cir. 2002) (reversing and remanding dismissal for failure to state a claim).

31.7.11. A use case: Best efforts and exclusivity

Best-efforts obligations are especially common when one party grants another party exclusive rights, for example exclusive distribution rights or an exclusive license under a patent, trademark, or copyright. Example: In one case, the Third Circuit held that, in a contract with an exclusive-dealing arrangement, "[t]he obligation of best efforts forces the buyer/reseller to consider the best interests of the seller and itself as if they were one firm." Tigg Corp. v. Dow Corning Corp., 962 F.2d 1119 (3d Cir. 1992) (affirming on liability issues but reversing and remanding for new trial on damages).

31.7.12. Could analogies be useful to explain best efforts?

To many business people, it might seem self-evident that when a contract uses the term best efforts, it calls for "something more" than mere reasonable efforts — otherwise, why bother even saying best efforts? That is to say:

  • Reasonable efforts will cover a range of possibilities;
  • best efforts refers to somewhere near the top of that range.

By analogy: On major U.S. highways, the speed-limit signs often include both maximum and minimum speeds of (say) 70 mph and 45 mph:

  • Let's stipulate that those two speeds establish the upper- and lower bounds of reasonableness.
  • Now, suppose hypothetically that a trucking company agreed that its driver would use her "best efforts" to drive a shipment of goods from Point A to Point B on such a highway.
  • In good weather with light traffic, driving at 55 mph — that is, 10 mph above the minimum speed but 15 mph below the maximum speed — might qualify as reasonable efforts, but likely not as best efforts.

Or to use a sports analogy: Best efforts means bring your "A" game, not your "C" game, even though C is a passing grade in (U.S.) schools, and arguably is equivalent to reasonable efforts.

31.7.13. "Comparables" might be a good yardstick for best efforts

On the best-efforts front: So-called comparables could be used in measuring compliance with a best-efforts obligation could be whether the obligated party had done what it had done in other, similar transactions; this can be seen in a Seventh Circuit opinion:

The term "best efforts" is a familiar one in contract parlance, and its meaning is especially plain in a case such as this where the promisor has similar contracts with other promisees. In such a case "best efforts" means the efforts the promisor has employed in those parallel contracts where the adequacy of his efforts have not been questioned. If Olympia worked as hard for Racine as it did for its other, but noncomplaining, customers, then it was using its best efforts within the meaning of the contract. Olympia Hotels Corp. v. Johnson Wax Dev. Corp., 908 F 2d 1363, 1373 (7th Cir. 1990) (Posner, J.) (reversing judgment below in part and remanding for new trial).

31.7.14. Some other best-efforts business considerations

Asking for best efforts can make business sense:

  • Sure, there's some legal uncertainty associated with a best-efforts commitment.
  • But from a business perspective it can make good sense to ask the other side for such a commitment anyway: a party that makes a best-efforts commitment — to the extent that it later thinks about that commitment at all — will at least be aware that it might well have to make more than just routine, day-to-day, "reasonable" efforts. That alone might be worthwhile to the party asking for the commitment.

On the other hand: Agreeing to make best efforts could lead to trouble: If you commit to a best-efforts obligation, and the other side later accuses you of breaching that obligation, and you can't settle the dispute, then you're likely to have to try the case instead of being able to get rid of it on summary judgment. That's because:

  • As noted above: If a problem arises, then no matter what you did or didn't do, the other side's lawyers and expert witness(es), with 20-20 hindsight, will argue that there were X number of things that you supposedly could have done to achieve the agreed goal but didn't, and so you necessarily failed to use "best" efforts, Q.E.D.
  • It might be difficult or impossible to get summary judgment that you didn't breach the best-efforts obligation, in which case you're likely to have to go to the trouble and expense of a full trial or arbitration hearing. The judge or arbitrator could well say that the question involves disputed issues of material fact — those issues would have to be resolved by witness testimony and cross-examination about such things as industry practices; the then-existing conditions; etc. According to the rules of procedure in many jurisdictions, that will require a trial and will not be able to be done in a summary proceeding. Your motion for summary judgment would then likely be denied.
  • The tribunal, after hearing the evidence, could find that in fact you did not use your best efforts. If that were to happen, you'd likely have a very hard time convincing an appeals court to overturn that finding.

31.7.15. Could more-precise language work better?

Contract drafters considering a best-efforts obligation should consider stating:

  1. as specifically and un-vaguely as possible: just what the best efforts are supposed to try to do;
  2. clear, specific actions that the obligated party is allowed to take — or required to take — in complying with the best-efforts obligation;
  3. particular considerations that the obligated party could take into account in deciding what specific actions to take; and/or
  4. safe-harbor (but non-mandatory) actions that, if timely taken, would be conclusively deemed to satisfy a best-efforts obligation.

But again: Clients and drafters might not want to spend the time negotiating such things in advance, especially when they're not sure what the relevant circumstances might be in the future.

31.7.16. Optional: Further reading about best efforts

See also: • Protocol 9.10 (reasonable efforts); • Protocol 9.2 (commercially-reasonable efforts); •  Thau (2021), a student law-review note offering what seems to be a pretty-thorough review of "efforts" case law. See Charles Thau, Is This Really The Best We Can Do? American Courts’ Irrational Efforts Clause Jurisprudence And How We Can Start To Fix It, 109 Georgetown L.J. 665 (2021).

In a 2008 blog posting, Ken Adams seemed to insist that best efforts is in essence a synonym for reasonable efforts, and that therefore drafters should abjure the former term in favor of the latter. See Kenneth A. Adams, What the Heck Does "Best Efforts" Mean? (adamsdrafting.com 2008).

To be sure, Ken does have at least some support in the case law for his position, as discussed at 9.1.2. But that arguably amounts to lawyers telling clients, for no good reason: No, you can't do your deal the way you want, because I say so. That seems to seriously overstep the service role of a lawyer or other drafter.

31.8. Escrow (crude notes only)

Signatures in escrow (M&A)

Escrowed funds after an M&A deal

The buyer of a company failed to notify the company's sellers of a government claim against the company, and didn't give the sellers an opportunity to participate in defending against the claim. As a result, the buyer was precluded from tapping a $100 million escrow of money from the purchase price, which the parties had set aside to fund payment of indemnified claims. See LPPAS Representative, LLC v. ATH Holding Co., LLC, No. 2020-0241-KSJM (Del. Ch. May 2, 2023) (partially granting, but partially denying, seller's motion summary judgment). READ THIS FOR A DESCRIPTION OF HOW ESCROWS WORK ]

Escrow for real estate

31.9. Export controls (notes)

The export-controls laws in the U.S. are a bit complicated, but it’s extremely important for companies and counsel to get a handle on them.

Here are a couple of examples of "exports" that might be surprising:

  • Disclosure of controlled technical data to a foreign national in the U.S. can constitute an "export" that requires either a license or a license exception.
  • Emailing controlled technical data to a U.S. citizen located in a foreign country could constitute an export of the data.

Want to do a few years in federal prison? Just do an "export" of technical data witout the required export license (or an applicable license exception). And even without prison time, you could be heavily fined and/or denied export privileges.

Example: The Ninth Circuit upheld an 85-month prison sentence for a Los Angeles-based electrical engineer for exporting to China, without an license, electronic devices to amplify microwave signals, and for evading national security controls in having the devices manufactured. The offense arose out of Shih’s collaboration with engineers in China in conducting research for a Chinese enterprise that develops military weapons. United States v. Shih, No. 23-3718 (9th Cir. 2024).

Example: A dual citizen of the U.S. and Iran was sentenced to 30 months in prison, and agreed to pay a $50,000 fine, after pleading guilty to conspiring to illegally export finance-related technology to Iran; according to a Department of Justice press release:

As set forth in court papers, by providing the Government of Iran and end users in Iran with sophisticated, top-tier U.S. electronic equipment and software, the defendant and his co-conspirators enabled the Iranian banking system to operate more efficiently, effectively, and securely.

In doing so, the defendant and his co-conspirators likely helped strengthen Iran’s economy and provided faster and more secure access to funds that enable the Government of Iran to further priorities including its nuclear program and terrorist agenda — exactly what the U.S. sanctions against Iran were intended to prevent. U.S. Department of Justice, U.S. Citizen Sentenced to 30 Months in Prison for Conspiring to Provide Electronic Equipment and Technology to the Government of Iran (justice.gov Feb. 9, 2023); see also Brandon Vigliarolo, American jailed for smuggling controlled tech to Iran (TheRegister.com Feb. 10, 2023).

Example: A 71-year old emeritus university professor was sentenced to four years in prison for export-controls violations. The professor had been doing research, under an Air Force contract, relating to plasma technology designed to be deployed on the wings of remotely piloted drone aircraft. Apparently, his crime was to use, as part of the project staff, two graduate students who were Iranian and Chinese nationals respectively. (It almost certainly didn’t help that the professor was found to have concealed those graduate students' involvement from the government.) Tennessee emeritus professor imprisoned for export violations: See Bloomberg.com 2012: https://goo.gl/gfvGhR; FBI.gov 2012: https://goo.gl/jtZR7C. ]

Even without prison time, violation of export-controls regulations can lead to external oversight of a violator's business. Example: 2021, Honeywell voluntarily reported that it had illegally provided foreign countries — including China — with engineering prints for parts used in a variety of weapon systems, including the F-35 Joint Strike Fighter, Apache helicopters, and Tomahawk missiles. Honeywell's settlement with the government imposed some specific compliance-monitoring requirements, requiring Honeywell to hire an external compliance officer. Charging document; Press release: U.S. Department of State Concludes $13 Million Settlement of Alleged Export Violations by Honeywell International, Inc. (May 3, 2021).

For additional information on export controls, see, e.g.:

31.10. Extraordinary circumstances (rough notes)

Rarely, "extraordinary circumstances" might justify a departure from customary professional practice. In any situation in which a party asserts that extraordinary circumstances exist(ed); it'd be appropriate to consider the following questions, possibly among others:

  • Does the situation qualify as force majeure (see 14.2)?
  • Are the circumstances shown by clear and convincing evidence (see 20.11)?
  • How much advance warning of the situation did (or do) the parties have?
  • To what extent could — and did — the parties consult each other about the situation?
  • What else could one or both parties have done (or still do) in response to the situation?

31.11. False Claims Act (cursory note)

9th Cir: Hendrix v. J-M Mfg. Co. (qui tam case, 2023).

31.12. Federal contracting and subcontracting (links only)

Government contracting is beyond the scope of this document; for some basics, see an article by lawyers from the Fox Rothschild firm.

Jeff Schwartz, Doug Hibshman & Austen Endersby, The Federal Contractor’s Guide to Data Rights (FoxRothschild.com 2021).

Falsely certifying that you're a woman-owned business can bring criminal penalties.

See Press Release, U.S. Department of Justice, Jury Convicts Former NASA Subcontractor of Fraud (Justice.gov Aug. 4, 2021); Megan Benevento, Jury Convicts Former NASA Subcontractor of Fraud … (JDSupra 2021).

31.13. Foreign Corrupt Practices Act (rough notes)

Bribing foreign "officials" can lead to prison time under the U.S. Foreign Corrupt Practices Act (FCPA).

See generally the 2020 resource guide issued by the Criminal Division of the U.S. Department of Justice and the Enforcement Division of the U.S. Securities and Exchange Commission, at https://www.justice.gov/criminal-fraud/file/1292051/download.

Example: In January 2024, German software giant SAP agreed to pay some $98 million to settle civil charges that the company violated the Foreign Corrupt Practices Act by hiring intermediaries to bribe government officials in South Africa and other countries.

Here's how the Department of Justice describes the basic workings of the FCPA, with bulleting added: (link):

… the anti-bribery provisions of the FCPA prohibit[:]

  • the willful use of the mails or any means of instrumentality of interstate commerce
  • corruptly
  • in furtherance of any offer, payment, promise to pay, or authorization of the payment of money or anything of value to any person,
  • while knowing that all or a portion of such money or thing of value will be offered, given or promised, directly or indirectly,
  • to a foreign official to influence the foreign official in his or her official capacity, induce the foreign official to do or omit to do an act in violation of his or her lawful duty,
  • or to secure any improper advantage
  • in order to assist in obtaining or retaining business for or with,
  • or directing business to,
  • any person.

The Department of Justice has published a resource guide about the FCPA.

Example: Deutsche Bank agreed to pay more than $130 million to resolve the U.S. Government’s investigation into violations of the FCPA and a separate investigation into a commodities fraud scheme. "The charges arise out of a scheme to conceal corrupt payments and bribes made to third-party intermediaries by falsely recording them on Deutsche Bank’s books and records …." U.S. Department of Justice, Deutsche Bank Agrees to Pay over $130 Million to Resolve Foreign Corrupt Practices Act and Fraud Case (Jan. 8, 2021).

Example: Honeywell International took a charge of USD $160 million (with no tax benefit) as the company's estimate of its probable loss in connection with investigations by the U.S. Department of Justice (DOJ), the Securities and Exchange Commission (SEC) and the Brazilian authorities concerning the FCPA and similar Brazilian laws. See Honeywell's press release filed with the SEC as part of a report on Form 8-K, Oct. 22, 2021.

Example: Goldman Sachs admitted to conspiring to violate the FCPA with a scheme to pay over one billion dollars in bribes to high-ranking government officials in Malaysia and Abu Dhabi and agreed to pay more than $2.9 billion as part of a coordinated resolution with criminal and civil authorities in the United States, the United Kingdom, Singapore, and elsewhere. See U.S. Department of Justice, Goldman Sachs Resolves Foreign Bribery Case And Agrees To Pay Over $2.9 Billion (Oct. 22, 2020).

Example: The owner of a Hawaii-based engineering and consulting company was sentenced to 30 months in prison for his involvement in an international bribery conspiracy. See U.S. Department of Justice, U.S. Executive Sentenced to Prison for Role in Conspiracy to Violate Foreign Corrupt Practices Act (May 14, 2019).

Example: Albert “Jack” Stanley, formerly the chairman and CEO of Fortune 500 company KBR, was sentenced to 30 months in prison for participating in a decade-long scheme to bribe Nigerian government officials to obtain engineering, procurement and construction (EPC) contracts and for conspiring to commit mail and wire fraud as part of a separate kickback scheme. See U.S. Department of Justice, Former Chairman and CEO of Kellogg, Brown & Root Inc. Sentenced to 30 Months in Prison for Foreign Bribery and Kickback Schemes (Feb. 23, 2012).

31.14. Forfeiture (notes only)

"A release involves a voluntary relinquishment, while a forfeiture connotes a consequence imposed as a penalty." Release of "predecessors" meant corporate predecessors, not predecessors in title. Finley Resources, Inc. v. Headington Royalty, Inc., 672 S.W.3d 332, 339 & n.16 (Tex. 2023) (affirming court of appeals reversal and rendering of judgment).

31.15. Franchises

From a tweet:

Let’s talk briefly about franchisor insurance. Did you know that there is liability coverage available to franchise systems and their officers?

Below is an example of a franchising services policy endorsement purchased by a startup. Upon review, insurers have some “outs” and may fight coverage of certain claims in the gray between covered and excluded claims; however, the insurer’s obligation to provide zors with a defense (a free litigator) to a franchisee claim is broader than coverage. Franchisor coverage up to $1M plus general liability is about $1K per month as a premium. Could be worth having in addition to on-call franchise counsel that focuses on compliance.

Seems that the insurance industry needs to catch up with the times referencing “Uniform Franchise Offering Circular” in 2024 more than 16 years after that term has been replaced with Franchise Disclosure Document. Would an insurer deny a claim related to the “FDD” without reference to a UFOC? Probably no but the change in policy language should be made.

Hope this is helpful to someone. DMs open for questions.

31.16. Government contracting (reserved)

Cybersecurity requirements: article

31.17. GSA contracts (a.k.a. "GSA schedules") (notes)

Here's a federal-court summary of how GSA contracts work — which is in pretty much the same manner as a master purchasing agreement (see 28.4). The summary is adapted largely verbatim from a federal court decision; no copyright claimed in the court's decision. See CSI Aviation, Inc. v. Dept. of Homeland Security, 31 F.4th 1349, 1351 (Fed. Cir. 2022) (vacating administrative decision; commercial vendor's terms and conditions were incorporated by reference into GSA contract) (cleaned up and reformatted slightly).

Under the Federal Supply Schedule Program, the General Services Administration (GSA) acts as the contracting agent for the federal government and negotiates base contracts with suppliers of commercial products and services.

These base (or schedule) contracts streamline the acquisition process for federal agencies and allow them to take advantage of the flexible and dynamic commercial market-pricing environment, so all federal customers, regardless of size or location, can place orders directly with contractors and receive the same services, convenience, and pricing.

The Federal Supply Schedule Program closely mirrors commercial buying practices. But, instead of evaluating prices head to head in a competitive environment, GSA assesses pricing as it relates to the offeror's commercial selling practices.

  • An offeror submits a completed commercial sales practices sheet along with supporting documentation that discloses commercial pricing, market participants, sell price, and terms and conditions for the offeror's "most favored customer" in a competitive environment.
  • Relying on this information and in accordance with the Federal Acquisitions Regulations (FAR), a GSA contracting officer determines whether the pricing is "fair and reasonable" not as it relates to the competitive environment but as it relates to the offerror's commercial selling practices.

Should the contracting officer accept the offer, the Federal Supply Schedule Program allows executive agencies to issue orders for those commercial products pursuant to the underlying GSA contract.

31.18. Have-used rights (notes)

"Have-used" rights might be important to a party ("licensee") that is authorized to use another party's trade secret, patented invention, copyrighted work of authorship, or other asset. For that reason, the licensee might want to negotiate to allow the licensee's contractors to use the IP or other asset in question.

Example: In Great Minds (2d Cir. 2018), certain schools paid FedEx Office to make copies of materials licensed by a nonprofit organization under a Creative Commons license (referred to in the decision as a "public license") that prohibited "commercial use." The copyright holder sued FedEx, claiming that FedEx's copying was "commercial" and so was not authorized under that license. But the Second Circuit, affirming dismissal of the claim, held that the copying by FedEx still qualified as "noncommercial," even though FedEx had charged the schools for making the copies:

The public license does not explicitly address whether licensees may engage third parties to provide commercial services that assist the licensees in furthering their own noncommercial uses.

We hold that a copyright holder must state in its license any limitation it might wish to impose precluding such an engagement. We decline to infer any such limitation in Great Minds' public license, and therefore AFFIRM the District Court's judgment.

* * *

[U]nder long-established principles of agency law, a licensee under a non-exclusive copyright license may use third-party assistance in exercising its license rights unless the license expressly provides otherwise. Great Minds v. FedEx Office & Print Servs., Inc., 886 F.3d 91, 92, 94 (2d Cir. 2018) (affirming dismissal under Fed. R. Civ. P. 12(b)(6) for failure to state a claim upon which relief can be granted).

31.19. Hill of Proof (cross-reference)

31.20. Note Implied covenant of good faith and fair dealing (notes)

Delaware: The implied covenant of good faith and fair dealing doesn't protect an earn-out recipient 🔗 when the buyer rejected a good-faith-efforts obligation, saying that the implied covenant would govern, and the contract contained an integration clause: "If the Sellers' counsel and [the buyer's] counsel came to a separate agreement about the term the Sellers' counsel proposed [i.e., the implied covenant], that is precisely the kind of separate agreement that the parol evidence rule forecloses. Trifecta Multimedia Holdings Inc. v. WCG Clinical Services LLC, 318 A.3d 450, 458, 467-70 (Del. Ch. 2024) (granting, in part, defendants' motion to dismiss; footnotes omitted). See also the discussion of the "no reliance" issue in this case, at 11.7.6.2.

31.21. Insurance (rough notes only)

31.21.1. No general fiduciary duty of insurer (in Texas)

Under Texas law, an insurance carrier doesn't owe a general fiduciary duty to its insured, and so would not be liable for providing the insured with a policy containing the requested coverage instead of recommending higher policy limits. See Century Surety Co. v. EC & SM Guerra, LLC, 5:23-CV-01215, slip op. (W.D. Tex. Aug. 21, 2025) (Farrer, Mag. J.) (recommending grant of insurance carrier's motion for summary judgment in declaratory-judgment action) (citations omitted), adopted (Sept. 5, 2025) (Rodriguez, J.).

31.21.2. Claim-notification time limits can be crucial

Insurance policies generally impose deadlines for the insured to notify the carrier (the insurance company) of a potential claim. Failure to meet those deadlines can result in loss of coverage.

Some jurisdictions are stricter than others on that point. For example, when the policy is of the claims-made type, the "majority view" is that, if the claim was made during the policy period but after a shorter stated deadline, then the carrier must show that it was prejudiced by the insured's failure to meet the stated deadline. As explained by the Eleventh Circuit:

The majority of courts who have opined on this issue have applied the notice-prejudice rule, which establishes that when an insured provides notice within the policy period of a claims-made policy (the first type of notice), and breaches only the requirement that it also provide notice within a specified period of time (the second type of notice), coverage is not automatically lost.

Instead, the insurer needs to show prejudice in order to bar coverage: "Most courts have applied the notice-prejudice rule to traditional claims-made policies that require notice or reporting to the insurer 'promptly' or 'as soon as practicable.'"

L. Squared Indus., Inc. v. Nautilus Ins. Co., No. 23-13031, slip op. at 11 (11th Cir. Oct. 15, 2025) (per curiam; citations omitted). The court noted a Texas supreme-court holding to similar effect. See id. at 11-12.

But the court also predicted, based on analogous precedent, that when an insured missed the (shorter) stated reporting deadline, Florida courts would establish a rebuttable presumption of prejudice to the carrier. On that basis, the court affirmed summary judgment that the insured had failed to rebut the presumption. See id. at 14-15.

31.21.3. A notice period might run from an occurrence, not a claim

Some liability-insurance policies state that a prerequisite for coverage is for the insured to notify the carrier within a specified time of an occurrence that might give rise to liability, not of realizing that someone has made or could make a claim. See, e.g., A. B. v. Barrow, No. 24-13138, slip op. (11th Cir. Jan. 7, 2026) (affirming summary judgment: Sexual abuser's insurance carrier was not liable to child victim for $10 million verdict for invasion of privacy because victim did not show an excuse for abuser's 58-month delay in notifying carrier of occurrence).

31.21.4. Gaps in coverage can cause trouble.

The 96th-16th St. case in New York City arose in the course of building a four-home condominium project in Gowanus, Brooklyn. (At this writing, one unit is for sale for just under $1.5 million.)

  • An employee of a subcontractor of the general contractor was injured when a scaffold collapsed.
  • The injured employee sued (among others) the owner of condominium complex.
  • The owner tried to get coverage under the owner's general commercial liability ("GCL") policy.
  • But the GCL carrier denied coverage, citing an exclusion for "Injury to Employees, Workers, or Contracted Persons of Insureds or Contracted Organizations."

The Southern District of New York granted summary judgment in favor of the insurance carrier. 96-16th St., LLC v. Penn-Star Ins. Co., No. 24-cv-1064 (MKV), slip op. (S.D.N.Y. Sep. 26, 2025) (granting insurance carrier's motion for summary judgment), discussed in Daniel Lund III, Mind the Gap! (JDSupra.com).

Lessons:

  1. In almost any kind of contract, strongly consider recommending to the client that the client check with its insurance broker to see whether any additional coverage is appropriate.
  2. When recommending this to the client, do it in writing, e.g., in a quick, informal email, to leave a paper trail.
  3. When drafting or negotiating a services contract for the customer: Consider including specific, mandatory insurance requirements for the contractor with:
    • a requirement that the insurance carrier must furnish the customer with a certificate of additional-insured status before the contracctor starts work;
    • a statement that the contractor's failure to procure the insurance would entitle the customer to "pull the plug" for material breach by the contractor; and
    • a backup provision allowing the customer to procure the insurance — at the contractor's expense — if the contractor doesn't timely do so.

The 2025 96th-16th St. case in New York City arose from a condominium construction project in Brooklyn. An employee of a subcontractor of the general contractor was injured when a scaffold collapsed. The employee sued the project owner, among others. The owner tried to get coverage under the owner's general commercial liability ("GCL") policy. But the GCL carrier denied coverage, citing an exclusion for "Injury to Employees, Workers, or Contracted Persons of Insureds or Contracted Organizations."

31.21.5. Sample language favoring a customer or client

Here's Section 7.3 of a 2014 As-Needed Product Supply Agreement for laboratory instrumentation and associated software, between Agilent Techologies, Inc., and the City of San Diego (with extra paragraphing added):

7.3 Insurance. Contractor shall procure and maintain for the duration of the contract insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the work hereunder and the results of that work by Contractor, his agents, representatives, employees or subcontractors. Contractor shall provide, at a minimum, the following:

7.3.1 Commercial General Liability. Insurance Services Office Form CG 00 01 covering CGL on an “occurrence” basis, including products and completed operations, property damage, bodily injury, and personal and advertising injury with limits no less than $1,000,000 per occurrence.

If a general aggregate limit applies, either the general aggregate limit shall apply separately to this project/location (ISO CG 25 03 or 25 04) or the general aggregate limit shall be twice the required occurrence limit.

[DCT note: Drafters should check to be sure that the ISO forms listed in this excerpt are the current versions.]

7.3.2 Commercial Automobile Liability. Insurance Services Office Form Number CA 0001 covering Code 1 (any auto) or, if Contractor has no owned autos, Code 8 (hired) and 9 (non-owned), with limit no less than $1,000,000 per accident for bodily injury and property damage. [DCT note: See the note above about checking for outdated form versions.]

7.3.3 Workers' Compensation. Insurance as required by the State of California, with Statutory Limits, and Employer’s Liability Insurance with limit of no less than $1,000,000 per accident for bodily injury or disease.

7.3.4 Professional Liability (Errors and Omissions). For consultant contracts, insurance appropriate to Consultant’s profession, with limit no less than $1,000,000 per occurrence or claim, $2,000,000 aggregate.

If Contractor maintains broader coverage and/or higher limits than the minimums shown above, City requires and shall be entitled to the broader coverage and/or the higher limits maintained by Contractor. [DCT note: This could be significant in Texas cases, as discussed at 14.3.13.11 concerning the Texas Oilfield Anti-Indemnity Act.]

Any available insurance proceeds in excess of the specified minimum limits of insurance and coverage shall be available to City.

DCT note: Consider also: • cyber insurance • reps and warranties insurance • excess- or umbrella coverage.

7.3.5 Other Insurance Provisions. The insurance policies are to contain, or be endorsed to contain, the following provisions:

7.3.5.1 Additional Insured Status. The City, its officers, officials, employees, and volunteers are to be covered as additional insureds on the CGL policy with respect to liability arising out of work or operations performed by or on behalf of Contractor including materials, parts, or equipment furnished in connection with such work or operations.

General liability coverage can be provided in the form of an endorsement to Contractor’s insurance (at least as broad as ISO Form CG 20 10 11 85 or if not available, through the addition of both CG 20 10, CG 20 26, CG 20 33, or CG 20 38; and CG 20 37 if a later edition is used). [DCT note: See the note above about checking for outdated form versions.]

7.3.5.2 Primary Coverage. For any claims related to this contract, Contractor’s insurance coverage shall be primary coverage at least as broad as ISO CG 20 01 04 13 as respects the City, its officers, officials, employees, and volunteers. [DCT note: See the note above about checking for outdated form versions.]

Any insurance or self-insurance maintained by City, its officers, officials, employees, or volunteers shall be excess of Contractor’s insurance and shall not contribute with it.

7.3.5.3 Notice of Cancellation. Each insurance policy required above shall provide that coverage shall not be canceled, except with notice to City. [DCT note: Folk wisdom among some attorneys is many insurance carriers generally won't commit to doing more than endeavoring to provide notice of cancelation.]

7.3.5.4 Waiver of Subrogation. Contractor hereby grants to City a waiver of any right to subrogation which the Workers’ Compensation insurer of said Contractor may acquire against City by virtue of the payment of any loss under such insurance. [DCT note: A waiver of subrogation means, generally, that Contractor's insurance carrier: (i) must pay for insured losses even if the losses were the City's fault; and (ii) cannot sue City to recoup the carrier's payments for such losses that were the City's fault; see 31.21.7 for additional discussion.]

Contractor agrees to obtain any endorsement that may be necessary to affect this waiver of subrogation, but this provision applies regardless of whether or not the City has received a waiver ofsubrogation endorsement from the insurer.

7.3.5.5 Claims Made Policies (applicable only to professional liability). The Retroactive Date must be shown, and must be before the date of the contract or the beginning of contract work.

Insurance must be maintained and evidence of insurance must be provided for at least five (5) years after completion of the contract of work.

If coverage is canceled or nonrenewed, and not replaced with another claims-made policy form with a Retroactive Date prior to the contract effective date, Contractor must purchase “extended reporting” coverage for a minimum of five (5) years after completion of work.

7.4 Self Insured Retentions. Self-insured retentions must be declared to and approved by City.

City may require Contractor to purchase coverage with a lower retention or provide proof of ability to pay losses and related investigations, claim administration, and defense expenses within the retention. The policy language shall provide, or be endorsed to provide, that the self-insured retention may be satisfied by either the named insured or City.

7.5 Acceptability of Insurers. Insurance is to be placed with insurers with a current A.M. Best’s rating of no less than A-VI, unless otherwise acceptable to City. [DCT note: See AM Best (Investopedia.com).]

City will accept insurance provided by non-admitted, “surplus lines” carriers only if the carrier is authorized to do business in the State of California and is included on the List of Approved Surplus Lines Insurers (LASLI list).

All policies of insurance carried by non-admitted carriers are subject to all of the requirements for policies of insurance provided by admitted carriers described herein.

7.6 Verification of Coverage. Contractor shall furnish City with original certificates and amendatory endorsements or copies of the applicable policy language effecting coverage required by this clause.

All certificates and endorsements are to be received and approved by City before work commences.

However, failure to obtain the required documents prior to the work beginning shall not waive Contractor’s obligation to provide them.

City reserves the right to require complete, certified copies of all required insurance policies, including endorsements required by these specifications, at any time.

7.7 Special Risks or Circumstances. City reserves the right to modify these requirements, including limits, based on the nature of the risk, prior experience, insurer, coverage, or other special circumstances.

7.8 Additional Insurance. Contractor may obtain additional insurance not required by this Contract.

7.9 Excess Insurance. All policies providing excess coverage to City shall follow the form of the primary policy or policies including but not limited to all endorsements.

7.10 Subcontractors. Contractor shall require and verify that all subcontractors maintain insurance meeting all the requirements stated herein, and Contractor shall ensure that City is an additional insured on insurance required from subcontractors.

For CGL coverage, subcontractors shall provide coverage with a format at least as broad as the CG 20 38 04 13 endorsement. [DCT note: See the note above about checking for outdated form versions.]

31.21.6. How insurance defense-coverage disputes work

The following is cleaned up from an opinion by Judge James Ho in Windermere Oaks Water Supply Corp. v. Allied World Specialty Ins. Co., 67 F.4th 672, 674-75 (5th Cir. 2023) (affirming summary judgment in favor of insured); no copyright is claimed in the opinion text.

In a diversity case involving the interpretation of a contract, we apply the substantive law of the forum state.

Under Texas law, insurance policies are interpreted in accordance with the rules of construction that apply to all contracts generally.

The insured bears the initial burden of showing that there is coverage, while the insurer bears the burden of proving the applicability of any exclusions in the policy.

In construing a contract, a court’s primary concern is to ascertain the intentions of the parties as expressed in the instrument. As with any other contract, the parties’ intent is governed by what they said. We look at the language of the policy because we presume parties intend what the words of their contract say.

Under Texas’s so-called "eight-corners rule," the insurer’s duty to defend is determined by comparing the allegations in the plaintiff’s complaint to the policy provisions, without regard to the truth or falsity of those allegations and without reference to facts otherwise known or ultimately proven.

When applying the rule, we give the allegations in the complaint a liberal interpretation.

In case of doubt as to whether or not the allegations of a complaint against the insured state a cause of action within the coverage of a liability policy sufficient to compel the insurer to defend the action, such doubt will be resolved in the insured’s favor.

Or as this court has previously summed it up: When in doubt, defend.

31.21.7. Subrogation - what is it?

DCT note: In Carter v. Pulte Home Corp., 52 Cal. App.5th 571 (2020), the court summarized the law of subrogation in that state. The description below is adapted from the court's opinion (at 578), with citations omitted.

Subrogation is the substitution of another person in place of the creditor or claimant to whose rights he or she succeeds in relation to the debt or claim.

In the case of insurance, subrogation takes the form of the right of an insurance company (the "carrier") to be put in the position of the carrier's customer (the "insured").

If the carrier pays its insured for a loss caused by a third party, then the carrier can sue the third party to recover the carrier's payment (as well as the insured's deductible).

The subrogated carrier is said to "stand in the shoes" of its insured, because the carrier has no greater rights than the insured, and it's subject to the same defenses that the third party could assert against the insured.

Thus, a carrier can't acquire by subrogation anything to which the insured doesn't already have rights.

Subrogation goes even farther: As now applied, the doctrine of equitable subrogation is broad enough to include every instance in which one person, not acting as a mere volunteer or intruder, pays a debt for which a third party is primarily liable, and which in equity and good conscience should have been taken care of by the third party.

For another summary, see a very-readable explanation of key business points for insureds, by Pillsbury Winthrop lawyers Clark Thiel and Alexis Wansac: Subrogation 101 (and Why Should I Care?) (JDSupra.com 2023).

In some contracts, a waiver of subrogation might be unconscionable; see Bennett (JDSupra 2024), discussing American Commerce Ins. v. Eastern Fuel (Conn. Super. Ct. 2024).

DCT note: As a personal example, one evening in July 1984 my Honda Accord was T-boned at an intersection by a fast-moving pickup truck that ran the red light — and whose driver had no insurance. I wasn't hurt but my car suffered significant damage.

My insurance carrier, USAA, paid to have my car repaired, and for a rental car. USAA then hired a sole-practitioner lawyer to sue the pickup truck's drive — who didn't file an answer and so had a default judgment entered against him. The lawyer promptly had the judgment recorded in the courthouse records; the amount of the judgment covered USAA's payments and my deductible.

Not long afterwards, the pickup truck's driver contacted the lawyer to work out a payment plan. (If I recall correctly, the driver had found that the recorded judgment was preventing him from getting credit.) The driver made monthly payments until the judgment was paid off, at which point the lawyer filed a release of the judgment.

31.21.8. Additional-insured status (notes)

In a particular policy, "Additional Named Insured" was held to have a different meaning than "(additional) Named Insured," for purposes of determining whether the additional insured can assert a claim for loss of rental income and soft costs resulting from construction delays. BCC Partners, LLC v. Travelers Prop. Cas. Co., 140 F.4th 465 (8th Cir. 2025) (affirming summary judgment in favor of insurance carrier).

31.21.9. Miscellaneous insurance-related topics

Insurance for reps and warranties: 16.2.7.

Payment bonds, performance bonds: See item 4.4.11.3 and item 4.4.11.3 of 4.4.11.3.

Cyber-insurance for ransomware might become less available: Cyberscoop article in the wake of the Colonial Pipeline ransomware incident

31.22. Lawyer BS [notes; in progress]

Lawyers are (in)famous for making arguments about contract meaning that are just utter BS. And only seldom do courts ever call them on such arguments — probably because lawyers' ethical duty of zealous advocacy gets inflated into an excuse for bad behavior.

Example: In Days Inn Worldwide (D.N.J. 2025), a federal court held that the term "reasonable attorney fees" in an indemnification provision was not indefinite, rejecting the defendant's contrary argument:

Instead, [the defendants] argue the entire indemnification provision must be held unenforceable due to vagueness or ambiguity because "reasonable attorneys' fees" is not explicitly defined, and that the entire License Agreement becomes null and void as a result of this undefined essential term.

However, such a holding is neither supported by case law, as courts routinely uphold similar indemnification clauses, nor do Defendants point the Court to any analogous situation where the use of "reasonable attorneys' fees," without definition, rendered such a provision unenforceable, much less an entire contract. Days Inns Worldwide, Inc. v. 4200 Rose Hospitality LLC, No. 2:22-cv-04822, slip op. (D.N.J. Aug. 25, 2025) (granting, in part, Days Inns motion for partial summary judgment; unpublished) (cleaned up, citations omitted, extra paragraphing added).

Client pressure: In Bandera Master Fund (Del. 2025), a Baker Botts partner "appeared to be caught between his law partners, who were hesitant about various essential elements of [a particular legal opinion that the client wanted], and his client …." who wanted the opinion. The court of chancery savaged the Baker Botts opinion, holding that the firm had rendered its opinion in bad faith to give a forceful client the result it wanted, awarding nearly $690 billion in damages and interest for breach of contract. A 3-2 majority of the state's supreme court affirmed the chancery court's findings on that issue as supported by competent evidence (but reversed and remanded on other issues). See Bandera Master Fund LP v. Boardwalk Pipeline Partners, LP, part I.G, slip op. at 24, 30, 47-56 (Del. Dec. 10, 2025).

31.23. Leases for real property (notes)

Checklist: Kaplan (2024).

31.24. Licenses - Notes [reserved]

An "irrevocable" license can still be terminated by agreement of the parties: Uniloc 2017 LLC v. Google LLC, No. 21-1498, slip op. at 9 (Fed. Cir. Nov. 4, 2022) (reversing and remanding dismissal of patent-infringement suit) (citing cases).

31.25. LLC operating agreements (links to examples)

Prince's heirs - LLC operating agreement excerpts from litigation: McMillan v. Nelson (Del. Ch. 2024)

Section 6.2, titled “Duties of the Managing Members,” provides that:

The Managing Members shall be responsible for the day- to-day management of the Company’s business and affairs and shall devote such time and effort to the Company as shall reasonably be required for its welfare and success. The Managing Members shall coordinate meetings, conference calls, and communicate as reasonably required subject to a meeting once every other meeting [sic]. With respect to contractual and legal matters handled by the Managing Members, McMillan shall provide and make the final decision on such business and legal matters. Specifically, except as otherwise limited in this Agreement, the Managing Members are authorized to own, hold, manage, administer, operate, lease, sell, exchange, pledge, encumber, transfer, purchase, grant options related to, and otherwise deal with the Company assets in Delaware or any other state on behalf of the Company, except as otherwise provided in Section 6.3. In the event any Managing Member fails to be able to perform his responsibilities or fails to provide day-to-day management of the Company, such Managing Member can be removed and/or replaced by the vote of the Members subject to the remaining Managing Member’s mutual consent . . . .53 Section 6.5, titled “Members Who Are Not a Managing Member” provides: A Member who is not a Managing Member shall not participate in the control of the Company’s affairs and shall have no right or authority to act for or to bind the Company. The Member hereby consents to the exercise by the Managing Members of the powers conferred by this Agreement and to the employment, when and if the same is deemed necessary or advisable, of such brokers, agents, accountants, attorneys, and such other advisors as the Managing Members may determine to be appropriate for the management of the Company business, subject to consultation with all the Members.54

Section 6.3, titled “Limitations on Authority of Managing Members,” identifies 28 actions over which Non-Managing Members have a say. As to nine of the 28 actions, consent of 100% of the Members’ Percent Interest is required.55 As to the remaining 19, the agreement provides that: “Notwithstanding the provisions of Section 6.2 above: (a) the consent of at least sixty-six and two thirds percent (66 2/3 %) of the Percentage Interests then held by the Members shall be required to do any of the following: . . .”56 The list of 19 actions includes: “Amend this Agreement, except as otherwise provided in Section 6.2.”57

Plaintiffs interpret these provisions collectively to prohibit a Non-Managing Member from participating in the control of the Company or seeking to bind the Company, including by amending the LLC Agreement and proposing agenda items.[58]

[And the court agrees: Trying to amend the LLC agreement violates the management clause!]

Section 5.3 provides:

The Members shall meet no less than required under the Act and shall meet every other month to provide meaningful input and consultation on matters related to the Company. During the Member Meetings, the Members shall have the right to review the then current bank statements of the Company.[62]

The language "meaningful input and consultation" is a marked departure from words like "direction" or "control" and emphasizes the limited and advisory role that Non-Managing Members play under the parties' contractual scheme. It is also a marked departure from the specific right set out in the second sentence of Section 5.3—to review then-current bank statements. The second sentence reflects that the drafters of the LLC Agreement knew how to grant affirmative rights to Non-Managing Members, but failed to do so in the way that Defendants suggest.

* * *

Contrary to Defendants' assertion, Section 13.3 does not support their interpretation of Section 6.3(a)(19). Section 13.3 is a formalities clause that sets forth the mechanics for an amendment to the LLC Agreement pursuant to Section 6.3(a)(19)—that is, one approved by the Managing Members with the consent of 66 2/3% of the Percentage Interests. Any such amendment must be in writing and signed by at least 66 2/3% of the Members' Percent Interests for it to be valid and binding. It does not confer on the Non-Managing Members the power to unilaterally propose and adopt amendments. Nor does it trump Section 6.5 and the prohibition on non-Managing Members binding the Company as Defendants purported to do by amending the LLC Agreement.

DCT note: I haven't looked at these in any detail.

Series LLC operating agreement

Burlington Northern Santa Fe, LLC (2009) (sole member)

Exelon (2019) (ditto)

90210 Management Co., LLC (Hilton) (2018) (sole member but with provisions for others) (part of an offering).

Doubletree (2019; Arizona law)

Curio Management LLC (2017; Delaware; Hilton is the managing member)

Hampton Inn (2018, Delaware, Hilton)

JFC LLC (2013; MN - Pilgrim's Pride)

Masterworks 057 - acquire a single work of art

Engagement letter for brokers to find investors

31.25.1. Topics for LLC operating agreement

31.25.1.1. Jimerson Birr law firm

From here:

Strategy #1 Consider Hypotheticals Scenarios

Writing a list of hypothetical scenarios that would impact the operations of an LLC can allow members to solve problems before they ever occur.

Members should consider making a list of hypothetical scenarios that could affect the LLC or its members, including situations such as death, divorce, or a member disappearing to Tahiti.

After making a list of hypothetical scenarios, members should discuss the desired result and incorporate provisions needed to achieve that result into the operating agreement.

Planning for every situation will always remain impossible. However, drafting an operating agreement that considers specific situations can allow members to solve problems before they arise in the future.

Strategy #2 Consider the Tax Implications

LLCs are the most flexible legal entity available. LLCs can have (and frequently do have) tax statuses different from their legal entity status.

Under the default tax rules, LLCs with more than one member are taxable as a partnership, and LLCs with a single member are taxable as a disregarded entity. However, LLCs can also elect to be taxable as a C corporation or an S corporation (when eligible). Therefore, operating agreements should incorporate tax-specific provisions that reflect the intended tax status and comply with applicable tax code provisions.

Strategy #3 Consider Voting Rights

LLCs provide tremendous flexibility with member voting.

A common technique when structuring an LLC and writing an operating agreement is to create different classes of equity that provides different voting rights to members.

For example, an operating agreement can include provisions that issues Class A equity and Class B equity, with members owning Class A equity having greater rights, sole voting rights, or no voting rights.

Operating agreements can also allow classes of equity to vote only on specific matters.

Other than major LLC decisions (merger, sale, etc.), members of an LLC are free to alter their voting rights through an operating agreement.

Strategy #4 Consider the Exit

Every member of an LLC will have an exit. There are various types of exit events that need to be considered when drafting an operating agreement, including redemptions, dissolutions and wind-downs, and interest sales.

Exit planning can get tricky when exit terms are not included into the operating agreement, forcing members to negotiate and resolve matters amongst themselves.

Having defined terms in the operating agreement that provides clear terms and procedures will ensure members can exit the LLC as quickly, efficiently, and fairly as possible.

Strategy #5 Consider Restrictive Covenants

Employment agreements frequently include restrictive covenants. However, operating agreements can impose similar restrictive covenants upon managers or members.

For example, an operating agreement can prohibit members from soliciting employees, competing with the LLC, or disclosing confidential information.

Although the Florida Revised Limited Liability Company Act provides some restrictions on competition, operating agreements can be drafted to include restrictive covenants that impose greater or lesser restrictions on members or managers.

Operating agreements can also provide the LLC with specific remedies following a breach that may not otherwise be available under the law.

Strategy #6 Consider Deadlocks

Manager or member voting deadlock can render LLC operations impossible. However, operating agreements can include specific deadlock-breaking mechanisms that allow deadlocks to be decided based on procedures that were previously agreed upon by the members.

Members are free to get creative with their deadlock provisions and can utilize any tie-breaking mechanism they can think of, such as coin flips, rounds of golf, or having a 3rd party decide the issue.

Incorporating deadlock provisions into an operating agreement will ensure that the LLC can still function even when its members or managers cannot agree.

Strategy #7 Consider Ownership

LLC members are often individuals. However, LLC interests can also be owned by entities, trusts, other legal entities, or spouses as tenants by the entireties.

Considering the potential advantages and disadvantages of each ownership type must be considered when drafting an operating agreement and structuring an LLC.

Ensuring the operating agreement has the language needed to effectuate the desired ownership structure is critical to preserve flexibility and avoid potential challenges in the future.

31.25.2. Google Doc from LLC University

31.27. Mutual mistake (rough notes)

In 1L Contracts class, we all learned about about the doctrine of mutual mistake, under which a court might decline to enforce a contract if both parties made the same mistake about an important underlying fact.

But the mistake must be mutual; as the Eleventh Circuit explained in a 2022 decision, courts will not intervene on behalf of a party that failed to do its homework or that accepted sloppy contract language:

Drummond argues that the mutual mistake here was that the parties thought that BHP always set the quarterly benchmark price, when in fact, prior to entering the Agreement, companies other than BHP had set the quarterly benchmark price. However, this does not appear to be an issue of a mutual mistake, but rather a lack of due diligence by these sophisticated parties before entering the Agreement. …

At best, this was a unilateral mistake on the part of Drummond. The only apparent mutual mistake here was a poorly drafted contract. Therefore, Drummond’s claim for equitable reformation fails. Southern Coal Corp. v. Drummond Coal Sales, Inc., 25 F.4th 864, 873 (11th Cir. 2022) (affirming, in relevant part, judgment that pricing-adjustment clause was unenforceable because agreed benchmark was no longer published; rejecting mutual-mistake argument).

31.28. Predecessors (note)

Release of "predecessors" meant corporate predecessors, not predecessors in title. See Finley Resources, Inc. v. Headington Royalty, Inc., 672 S.W.3d 332, 339 & n.16 (Tex. 2023) (affirming court of appeals reversal and rendering of judgment). "The syntactic use of 'predecessors' thus connotes a prior connection to the corporate entities themselves, not the land." Id. at 343 ]

31.29. Recordation - necessary? (starter notes)

Drafters should consider whether the law might require (or simply permit) recording certain types of contract in the public records, so as to put third parties on notice. EXAMPLE:

–  Membership campgrounds: An Oregon statute, Or. Rev. Stat. §§ 94.953–989, imposes requirements for recordation (among other things) for sales of "membership campground contracts." See Adelsperger v. Elkside Dev. LLC, 373 Or. 621 (2025) (reversing court of appeal and reinstating jury verdict in favor of campground members against purchaser of campground), citing Or. Rev. Stat. 94.986(1).

–  Leases: Various state laws allow, or require, recordation of certain leases or of a "memorandum of lease." EXPERIMENT: In May 2025, I asked Google's Gemini large language model (LLM) to put together a report, which includes a summary table at the bottom; USE AT YOUR OWN RISK.

31.30. Reporting requirements (notes)

Introduction

Many business dealings require parties to depend on information provided by other parties. For some such contract relationships, one party might want to propose that the other side keep specified records. This could be important because, for example:

  • In the saying, trust, but verify (discussed in the introduction to Protocol 4.3), a contractual right to audit a party's books and records might be of little value if the contract doesn't also specify what kind of records are to be kept.
  • The party asking for records to be kept might be required to do so by law or by a flowdown obligation.
  • If the other party is reluctant to agree to reasonable recordkeeping requirements, it could be a red-flag warning that the other party is sloppy in other areas.

31.30.1. What kind of transactions might call for recordkeeping standards?

Here are a couple of common examples:

–  A commercial lease might require the tenant to pay not just a base rent, but also a percentage of gross revenue, which the tenant must record and periodically report to the landlord. See generally the Wikipedia article Percentage rent.

–  A technology license agreement might require the licensee to pay the licensor a royalty computed as a percentage of the licensee's gross- or net sales involving the licensed technology, as reported periodically by the licensee. See generally the Wikipedia article Royalty payment.

31.30.2. What kind of records might have to be kept?

Depending on the circumstances, the Con­tract could require a party to keep, for example: Sales journals; purchase-order journals; cash-receipts journals; general ledgers; and inventory records.

31.30.3. How long should records be required to be kept?

Parties might want to consider adapting the standard record-retention periods found in the [U.S.] Federal Acquisition Regulations; for that purpose, language could be considered along the following lines: See, e.g., Contractor Records Retention, 48 C.F.R. §§ 4.703(a)(1), 4.705.

1.  The Rec­ord­keep­er must cause each of the Records to be maintained for at least the period that the record would be required to be maintained under the (U.S.) Federal Acquisition Regulations ("FARs"), Contractor Records Retention, 48 C.F.R. Subpart 4.7.

2.  For clarity: This section is intended merely as a convenient shorthand reference in lieu of setting out the cited substantive record-retention terms; the parties do not intend to imply or concede that the Con­tract and/or their relationship are in fact subject to the FARs.

31.30.4. Pro tip: Consider also reporting requirements

Parties could consider some or all of the reporting requirements:

Reporting requirements: When parties agree that one party is to provide reports, drafters can consider including custom provisions that address issues such as:

  1. how often a party must make periodic reports;
  2. what sorts of events could trigger a nonperiodic report;
  3. when are reports due, e.g., within X days after the end of a month; a quarter; a year; or some specified type of event;
  4. what information must be included in a report;
  5. whether any particular method is to be used to generate the reports, e.g., using specific auditing software to collect and summarize electronic data;
  6. whether reports must be certified, and if so: • what the certification should say; and • who should "sign" the certification — this could be an internal certifier and/or an independent body such as an accounting firm; and
  7. what if any supporting documentation must be provided with reports.

31.30.5. Other record-related possibilities

Drafters can consider also whether to propose:

  1. audit rights such as at 4.3;
  2. inspection rights such as at 9.8; and/or
  3. periodic status conferences and check-in calls as in 3.2.

31.31. Reverse engineering (notes)

When a party to a confidentiality agreement expects to disclose "hidden" confidential information (for example, computer programs in executable form), that party will often want the confidentiality agreement to prohibit reverse engineering of the hidden information.

31.31.1. What is reverse engineering?

"Reverse engineering" of a product can take the form, generally, of one or more of disassembling the product to study its design, and/or operating the product and observing its behavior, then using that information to try to figure out what's going on inside.

See generally Reverse engineering and Black box (each, Wikipedia.com).

Reverse engineering is normally not considered "improper means" for discovering a "trade secret." See 18 U.S.C. § 1839(6) (definition of improper means), discussed at 5.3.10.

31.31.2. Software license agreements often prohibit reverse engineering

If you've ever installed any software on a computer, you've probably been asked to click on "I agree" to assent to the terms of a software license agreement. Many software license agreements prohibit "reverse-engineering" of the software; for example, a Microsoft Office license agreement

See https://tinyurl.com/MSOutlookLicenseTerms (emphasis added). ] states in part /

2.  Installation and Use Rights. …

Restrictions. The manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not: …

(vi)  reverse engineer, decompile, or disassemble the software, or attempt to do so, except if the laws where you live (or if a business, where your principal place of business is located) permit this even when this agreement does not. In that case, you may do only what your law allows; …

(Emphasis added.)

31.31.3. U.S. courts will enforce contracts' reverse-engineering prohibitions …

Waivers of reverse-engineering rights are routinely enforced in the U.S., on grounds that a recipient is free to contractually bargain away those rights. Example: A Houston property-management company was hit with a $152 million jury verdict (later reduced to $62.5 millon to eliminate duplication), and barred from developing property-management software for two years. The company was found to have reverse-engineered a software vendor's product in violation of a prohibition in the license agreement — the jury evidently didn't believe the property-management company's claim that it developed its own software without using the vendor's software. (A co-defendant software company that had participated in the reverse engineering was barred for four years.) See ResMan, LLC v. Karya Prop. Mgmt., LLC, No. 4:19-CV-00402, slip op. (E.D. Tex. Aug. 5, 2021) (final judgment); Natalie Posgate, Two Houston companies hit with $152 million verdict in intellectual property case (HoustonChronicle.com Mar. 19, 2021); Blake Brittain, ResMan ends up with $62 mln in trade-secret win after $152 mln verdict (Reuters.com Aug. 13, 2021). See also, e.g.: Davidson & Associates v. Jung, 422 F.3d 630, 639 (8th Cir. 2005), following Bowers v. Baystate Technologies, Inc., 320 F.3d 1317, 1323-26 (Fed. Cir. 2003); Meridian Project Sys., Inc. v. Hardin Construction Co., 426 F. Supp. 2d 1101 (E.D. Cal. 2006); Deepa Varadarajan, The Trade Secret-Contract Interface, 103 Iowa L. Rev. 1543, 1568-70 (2018) (discussing contractual elimination of reverse-engineering rights).

31.31.4. … but UK and EU courts might not

In a case involving a genteel turf battle between U.S. and UK courts, a UK software company, World Programming Ltd., wanted to compete with American statistical-software maker SAS Institute:

  • World Programming acquired a low-cost "learning edition" of the SAS software.
  • To install, the software, World Programming clicked on an "I agree" button to assent to the terms of SAS's end-user license agreement ("EULA"). World Programming then studied the SAS software, in effect reverse-engineering it, to help World Programing develop its own competitive software.
  • A federal jury in North Carolina found World Programming liable for fraudulent inducement and awarded SAS $26 million in damages — which was trebled to some $79 million under a state law. See SAS Institute, Inc. v. World Programming Ltd., 874 F.3d 37 (4th Cir. 2017), cert. denied, 139 S.Ct. 67 (2018).
  • But that wasn't the only aspect of the case: The parties filed competing lawsuits, with litigation in U.S. federal courts in North Carolina and California as well as in the UK, where courts held that the reverse-engineering prohibition in SAS's end-user license agreement ("EULA") was unenforceable in the EU under the European Union Software Directive. See SAS Institute, Inc. v. World Programming Ltd., 952 F.3d 513, 518 (4th Cir. 2020) (recounting the case's history); SAS Institute, Inc. v. World Programming Ltd., [2020] EWCA Civ 599 (same), permission to appeal granted, Feb. 26, 2021, appeal and cross-appeal withdrawn by consent of parties (SupremeCourt.UK, undated).

Counterexample: In an English case, IBM UK won a case against a group of related companies for reverse engineering of IBM software in violation of a prohibition in the license agreement; the court postponed ruling on the amount of damages to be awarded, but did award IBM its costs, with an initial payment of £20 million pending further proceedings. See IBM UK Ltd. v. LzLabs GmbH, [2025] EWHC 532 (TCC), summarized by two of IBM's lawyers in the case, Matthew Lavy KC and Laura Wright, and perhaps more usefully by lawyers at the Jones Day firm. Among the defendants, in his personal capacity, was John Moores, a software entrepreneur and former owner of the San Diego Padres. ]

31.31.5. The law might affirmatively protect reverse engineering

For a useful overview of the legal status of reverse engineering in the U.S., see a 2021 article by technology consultant Rahul Vijh.

Rahul Vijh, Reverse Engineering and the Law: Understand the Restrictions to Minimize Risks (IPWatchdog.com 2021).

31.32. Reverse triangular merger (notes only)

A common structure for acquisition transactions is the so-called reverse-triangular merger, which is explained in GSE Consulting (11th Cir. 2023) at 1200:

The standard reverse triangular merger proceeds as follows:

  1. an acquiring company creates a transitory subsidiary,
  2. that subsidiary merges into a target company,
  3. and then that target company survives as the new subsidiary of the acquiring company.

Formatting modified; see also Reverse Triangular Merger Definition (Investopedia.com).

31.33. Right of first refusal (raw notes)

DCT TO DO: Include an exception for intra-family transfers - Ashley Wagner, Structuring Right of First Refusal Clauses: Dos and Don’ts to Avoid Legal Landmines (JDSupra.com 2025)

"a bona fide third party unrelated and unaffiliated with [the] Bank": Gotlib v. FDIC, 24-CV-8197 (RA), slip op. at 2 (S.D.N.Y. Aug. 11, 2025) (granting FDIC's motion to dismiss claim for breach of right-of-first-option clause)

When oil giant Chevron acquired Hess Corporation, Chevron's competitor ExxonMobil sought to exercise a right of first refusal ("ROFR") to acquire Hess's stake in the oil and gas reservoir known as the Stabroek block, located in the Atlantic Ocean off Guyana in northern South America. An International Chamber of Commerce arbitration tribunal rejected ExxonMobil's claim, along with that of the China National Offshore Oil Corporation ("CNOOC"): The arbitration panel is thought to have ruled that under the contract's wording, the ROFR was not triggered by Chevron's acquisition of Hess. See Nadine Amr, Sophie Freelove, Louise Woods, and Honor Soames, The Stabroek JOA Arbitration: Is It Time to Revisit JOA Change in Control Provisions? (JDSupra.com).

31.34. Note Security requirements (to do)

31.35. Note Severability of contract provisions (notes only)

The concept of severability addresses the question: If one part of a contract — such as some or all of an arbitration provision — is held to be invalid or otherwise unenforceable, will the rest of the contract likewise be unenforceable? "Severability" means that a court or other tribunal can ditch (so to speak) the unenforceable part of the contract and proceed with dealing with the rest of the contract.

Whether to agree to severance of an invalidated provision is always an issue worth pondering, because from the perspective of a given party, the invalidated provision might be critical to the value of the entire agreement.

31.36. Source-code escrow (crude notes only)

https://www.jdsupra.com/legalnews/source-code-escrow-how-to-streamline-a-6703974: Use Git, have the escrow agent walk through the build process using a video call.

31.37. Note Successors (to a contracting party) (notes)

Assume a contract between parties A and B:

  • One possible successor to A could be a third party, C, to which A "assigns" the contract (see 15.3).
  • Or, if B files for bankruptcy protection, then under U.S. law a successor to B might be what's known as the "bankruptcy estate." See generally Bankruptcy Basics Glossary (USCourts.gov).

31.38. Take-or-pay (very-crude notes)

An additional payment was provided for in the SAA: "If Speedcast d[id] not meet the Minimum RGU Commitment" in any given year, it was obligated to pay a "Shortfall Amount." The shortfall payment was calculated by a formula using the amount by which Speedcast fell short of its commitment to sign up new customers or switch them from other services to the FX services. The parties refer to this as the "take-or-pay" obligations. In re Speedcast Int'l Ltd. (Inmarsat Global Ltd. v. Speedcast Int'l Ltd.), 76 F.4th 372, 374 (5th Cir. 2023) (affirming denial of plaintiff's claim in bankruptcy court, on grounds that claim had been released under a prior settlement agreement) (cleaned up).

31.38.1. "Take or pay" in a channel agreement could hurt a supplier

The Vendor's take-or-pay arrangement with Reseller might not serve the Vendor's desire to penetrate a market by making sales to actual customers.

And even worse, consider this hypothetical:

  • Reseller makes a deal with Vendor A for exclusive rights to sell Vendor A's widgets in a particular territory, with a take-or-pay arrangement but no other obligation to "push" Vendor A's widgets.
  • Reseller approaches a competing Vendor B with an offer: Hey, Vendor B: If you'll cover my take-or-pay payment obligations to Vendor A, then I won't make any effort to sell Vendor A's widgets, and instead I'll sell your widgets; that way, because I've got exclusivity for Vendor A's widgets, it follows that you won't have Vendor A as a competitor in the territory at all.

Depending on the economics, competing Vendor B might find such a lock-out proposal to be an attractive way of eliminating competition from Vendor A in the territory.

True, such a lock-out deal between Reseller and the competing Vendor B might create antitrust issues. But antitrust lawsuits are slow, complex, and most of all, expensive; Vendor A would likely prefer simply not to agree to an exclusive take-or-pay arrangement in the first place.

A take-or-pay arrangement could create less-threatening problems for Vendor A: Suppose that competing Vendor B offered to pay Reseller and/or its sales people an extra bonus (often known as a "spiff") for selling Vendor B's widgets. That would give Reseller's sales people an incentive to give preferential treatment to Vendor B's widgets. See Spiff (Wikipedia.org).

31.39. Trust: Is it worth trying to build it?

31.39.1. Contracting parties generally prefer trustworthy counterparties

A "meta" goal of this book is to give parties — both vendors and customers — some tools —

  • to help them identify prospective counterparties that might be less than reliable business partners; and
  • to signal their own reliability.

This stems from a contract lawyer's primary mission, which (in the author's view) is to help the client:

  • not just steer clear of the various "rocks and shoals" that can disrupt — or even sink — a business deal; but
  • also advance the client's short- and long-term business goals.

So consider the business motivations of vendors and their customers:

  • On the whole, vendors strongly prefer to get repeat business from good customers who have a track record of timely payment. That's because getting new customers is costly and time-consuming — new customers have to be found, qualified, and convinced to buy — plus, there's always the financial risk that a new customer could turn out to be a deadbeat that doesn't pay its bills.
  • Similarly, customers generally prefer to work with reliable vendors who've demonstrated that they'll "be there" for their customers. This was brought home, for example, in the wake of the COVID-19 lockdown and attendant supply-chain disruptions, as well as the West Coast shipping strike threat.

We can paraphrase how a team from leading consulting firm Deloitte put it during the COVID-19 pandemic: When a company has good relationships with its providers, those providers can usefully be thought of as almost like external departments of the company itself. See Jim Kilpatrick, Jennifer Brown, Ryan Flynn, Aaron Addicoat, and Pierre Mitchell, Deloitte Global 2021 Chief Procurement Officer Survey (deloitte.com).

So, when drafting a contract, lawyers for both vendors and customers can do their clients a service by keeping those long-term business goals in mind.

31.39.2. Earned trust can pay off: The NBA's COVID-19 experience

While this isn't strictly a contract case: Sports fans will remember how in July 2020, a few months into the COVID-19 pandemic lockdown, the NBA resumed its interrupted season in a quarantined "bubble" at Disney World in Florida; the teams continued playing there all the way through the playoffs — and saved the billions of dollars in TV revenue that would have been lost if the season had been canceled.

Notably:

Adam Silver’s "collaborative" approach to being [NBA] commissioner really paid dividends in 2020, and the bubble should be remembered as one of the signature moments of his tenure.

Without a strong working relationship between the NBA and the National Basketball Players Association, the bubble could have popped before it got off the ground or as soon as the players came to terms with being physically trapped in Disney World.

Billions of dollars were at stake, and the two sides pulled off the endeavor despite many complications. Washington Post journalist Ben Golliver, quoted in Joe Vardon, The NBA bubble, 5 years later (NYTimes.com Jul. 30, 2025) (emphasis and extra paragraphing added).

31.40. Warranties (notes)

31.40.1. A warranty is basically a conditional covenant.

If you haven't already, take a look at the "Hill of Proof" diagram for representations and warranties, at 16.2.2, reproduced here for convenience:

The noun warranty and the verb warrant can be thought of as:

  • a statement of past, present, or future fact,
  • made by a party (the "warranting party"),
  • that a specified state of affairs exists, or existed, or will exist,
  • at or during a specified time — normally, the time at which the warranting party formally assents to the document containing the warranty;
  • where the warranting party promises that if the warranted statement is shown to be (or have been) untrue, THEN — regardless whether the warranting party was or was not at fault for the untruth —
    1. the warranting party will take one or more actions clearly specified in the contract — if any; or
    2. if the contract doesn't specify such actions, then the warranting party will reimburse the warranty beneficiary (or -beneficiaries) for the foreseeable, ordinary-course, economic losses that are incurred by the warranty beneficiary as a result of the untruth of the warranted statement. This "foreseeable, ordinary-course economic losses" phrase draws on the well-known English case of Hadley v. Baxendale, discussed in the commentary to Protocol 21.5.

Like a [BROKEN LINK: rep-defn], a warranty is a particular type of statement that, if false, can lead to liability — but the resemblance largely ends there, because a warranty has a different legal effect than a mere representation (as explained in more detail at 16.2).

A warranting party's obligations under a warranty would be subject to any applicable exclusions of remedies or other limitations of liability stated in the contract (21.7.8.7).

31.40.2. Implied warranties can arise by law

Under the law, a party might be deemed to have made implied warranties. Example: If Fred sells his car to Ginger without clearly saying otherwise, then the chances are extremely high that Fred will be deemed to have implicitly warranted to Ginger that yes, he does own the car (that is, he's not purporting to sell someone else's car).

Implied warranties can arise in various ways; see generally Implied warranty (law.cornell.edu).

31.40.3. Breach of warranty: Less to prove — but fewer remedies

At bottom, a warranty is a particular type of covenant, specifically, a conditional covenant. As shown at the "Hill of Proof" drawing at 16.2.2, a plaintiff must check fewer boxes to prove breach of warranty than to prove misrepresentation — but successful proof of breach of warranty typically results in fewer "rewards" in the form of remedies that can be had in court or in arbitration. See Fed. Ins. Co. v. Winter, 354 S.W.3d 287, 293 (Tenn. 2011), quoting Black's Law Dictionary at 1725 (9th ed.2009).

31.40.4. For warranties, reliance and scienter need not be proved.

As seen on the right side of the Hill of Proof (16.2.2), if Fred sues Ginger for breach of warranty, he needn't show that he reasonably relied on Ginger's warranty — nor that Ginger acted negligently, recklessly, or deceptively — but simply that:

1.  Ginger made a warranty;

2.  a warranted fact proved untrue, and

3.  Fred suffered damages as a result.

Example: A leading case on point is CBS v. Ziff-Davis, from the Court of Appeals of New York (that state's highest court), which in essence characterized a warranty as akin to an insurance policy, a contractual commitment to assume certain risks:

[A warranty is] an assurance by one party to a contract of the existence of a fact upon which the other party may rely. It is intended precisely to relieve the promisee of any duty to ascertain the fact for himself. It amounts to a promise to indemnify the promisee for any loss if the fact warranted proves untrue …. CBS, Inc. v. Ziff-Davis Publishing Co., 75 N.Y.2d 496, 503, 553 N.E.2d 997, 1001 (1990) (quotation modified for readability), quoting Metropolitan Coal Co. v Howard, 155 F.2d 780, 784 (2d Cir 1946) (Learned Hand, J.). Cf. CITGO Asphalt Ref. Co. v. Frescati Shipping Co., 589 U.S. _  _, 140 S. Ct. 1081, 1088-89 (2020) (Sotomayor, J.) (maritime law).

Example: Applying Illinois law, the Seventh Circuit held that: "The warranty sued on here was part of the parties' agreement, so the plaintiff did not need to prove further reliance." Abellan v. Lavelo Prop. Mgmt. LLC, 948 F.3d 820, 832-33 (7th Cir. 2020), citing, among others, CBS v. Ziff-Davis. See generally Matthew J. Duchemin, Whether Reliance on the Warranty is Required in a Common Law Action for Breach of an Express Warranty, 82 Marq. L. Rev. 689 (1999).

Caveat: A different situation might be presented if — before the contract was signed — the warranting party disclosed facts indicating that a warranty in the contract was inaccurate. See Merrill Lynch & Co. Inc. v. Allegheny Energy, Inc., 500 F.3d 171, 186 (2d Cir. 2007) (reversing and remanding dismissal of counterclaim for breach of warranty; under New York law, where seller disclosed facts that would constitute a breach of warranty, but buyer closes with full knowledge and acceptance of those inaccuracies, then buyer cannot later be said to believe it was purchasing seller's promise respecting the truth of the warranties); Rogath v. Siebenmann, 129 F.3d 261, 264-65 (2d Cir. 1997) (vacating and remanding partial summary judgment that seller had breached contract warranty; emphasis and extra paragraphing added).

31.40.5. Breach of warranty vs. breach of contract

The Fifth Circuit explained the difference between a breach of contract and a breach of warranty (under the Texas version of article 2 of the Uniform Commercial Code):

Breach of contract and warranty claims are distinct causes of action under Texas law and provide for different remedies, and Texas law forbids conflating breach of warranty and breach of contract.

A breach of contract claim exists when a party fails to deliver the goods as promised. Damages are only permitted under a breach of contract cause of action when [i] the seller has failed to deliver the goods, [ii] the buyer has rejected the goods, or [iii] the buyer has revoked his acceptance.

  • Texas law allows a buyer to revoke acceptance of a good if the good was accepted without knowledge of the nonconformity and `acceptance was reasonably induced either by the difficulty of discovery before acceptance or by the seller's assurance.
  • If a buyer retains and uses, alters, or changes the goods, it will be found to have accepted them. …

[A] breach of warranty claim … arises when a seller delivers nonconforming goods.

The UCC recognizes that breach of contract and breach of warranty are not the same cause of action.

The remedies for breach of contract are set forth in Texas Business and Commerce Code section 2.711, and are available to a buyer where the seller fails to make delivery.

The remedies for breach of warranty, however, are set forth in section 2.714, and are available to a buyer who has finally accepted goods, but discovers the goods are defective in some manner.

Thus, the critical factor in whether the buyer has a breach of contract or breach of warranty claim is whether the buyer has finally accepted the goods. Baker Hughes Process & Pipeline v. UE Compression, L.L.C., 938 F.3d 661, 666-67 (5th Cir. 2019) (affirming summary judgment dismissing Baker Hughes's claims) (formatting revised).

31.40.6. Pro tip: Be careful just what you warrant

Recall that a warranty is in effect an insurance policy against the occurrence of a future event — even if the future event is someone else's fault. In a British Columbia case:

  • A supplier sold water pipes to a customer for use in a construction project designed by the customer. The pipes conformed to the customer's specifications — in other words, the supplier delivered what the customer ordered. But flaws in the customer's design led to problems.
  • The contract's warranty language stated that the supplier warranted that the pipes were "free from all defects arising at any time from faulty design" (emphasis added).

The trial court ruled in favor of the supplier because the design problem was the customer's fault — but the appeals court reversed, holding that the supplier was liable because of its warranty, saying:

[24] North American was obliged to deliver pipe in accordance with the appellant’s specifications. North American agreed to do so.

Quite separately, it warranted and guaranteed [sic] that if it so supplied the pipe, it [sic; the pipe] would be free of defects arising from faulty design. These are separate contractual obligations. The fact that a conflict may arise in practice does not render them any the less so.

The warranty and guarantee provisions reflect a distribution of risk.

* * * 

[34] Clauses such as 4.4.4 distribute risk. Sometime they appear to do so unfairly, but that is a matter for the marketplace, not for the courts.

There is a danger attached to such clauses. Contractors may refuse to bid or, if they do so, may build in costly contingencies. Those who do not protect themselves from unknown potential risk may pay dearly. …

Parties to construction or supply contracts may find it in their best interests to address more practically the assumption of design risk. To fail do to so merely creates the potential for protracted and costly litigation. Greater Vancouver Water Dist. v. North American Pipe & Steel Ltd., 2012 BCCA 337, ¶ 24, 32 (CanLII) (extra paragraphing added).

BUT: In 2021, Texas enacted legislation for real-estate construction and repair work that — with certain exceptions — could immunize contractors from liability for damage caused by defects in designs provided by others, effectively codifying what's known as the Spearin doctrine. See Tex. Bus. & Com. Code ch. 59, codifying S.B.219; see also the discussion of the Spearin doctrine by Rose Tanner and Paul Sonderegger, Project owners can effectively combat contractors’ efforts to use the Spearin Doctrine as a sword with strategic planning beforehand (ThompsonCoburn.com 2022), archived at https://perma.cc/H8SH-YRXR.

As a Texas lawyer pointed out: "Chapter 59 expressly provides that it cannot be waived. Thus, any attempt by contractors and owners to contractually agree to waive the provisions of Chapter 59 will be void." Megan Healy Schmid, Texas Contractors No Longer Bear Risk for Defects in Owner-Furnished Designs (JDSupra.com Mar. 9, 2022).

31.40.7. Who can benefit from a warranty in a contract?

Generally, if a contract warranty does not clearly identify its beneficiaries, the warranty should benefit only the other party (or if more than one, all other relevant parties) to the contract.

Likewise, if a warranty does clearly identify its beneficiaries, then the warranty should normally benefit only those specific individuals and organizations so identified (absent overriding provisions of law in the jurisdiction).

The usual rules governing claims of third-party-beneficiary status would presumably apply; see generally the commentary at 11.8.

Pro tip: A warranting party ABC that wants to limit the potential beneficiaries should consider using language such as, "ABC warrants to XYZ that …."

Pro tip: A party that wanted its own affiliates, etc., to benefit from a warranty should make that clear in the warranty language itself. Here's a hypothetical example: "ABC warrants to XYZ and XYZ's Affiliates that …."

31.40.8. Warranting a present or future fact? (It might matter.)

Drafters of representations and warranties should be careful to be clear just what is being represented warranted: Is it a present fact, or is it a future fact? The distinction can be important because in many jurisdictions:

–  The "clock" for the statute of limitations will not start to tick for a warranty of future performance (for example, a warranty that a car will not have any mechanical problems for X years or Y miles) until the warranty failure is discovered;

–  In contrast, for a warranty of present fact — for example, that goods as delivered are free from defects — the clock starts ticking at delivery.

For example, in its 2019 Kenworth of Indianapolis opinion, Indiana's supreme court noted that:

Under the UCC, a party's cause of action accrues (thus triggering the limitations period) upon delivery of goods.

However, if a warranty explicitly guarantees the quality or performance standards of the goods for a specific future time period, the cause of action accrues when the aggrieved party discovers (or should have discovered) the breach.

This is known as the future-performance exception. Kenworth of Indianapolis, Inc., v. Seventy-Seven Ltd., 134 N.E.3d 370, 374 (Ind. 2019) (extra paragraphing added).

And in its 2015 ACE Securities opinion — rejecting a claim that a contract had validly extended the statutory limitation period — New York's highest court distinguished cases in which future performance was warranted. See ACE Securities Corp. v. DB Structured Products, Inc., 25 N.Y.3d 581, 595-96 & n.3, 36 N.E.3d 623, 15 N.Y.S.3d 716 (2015) (affirming dismissal of complaint as untimely).

31.40.9. Caution: Consumer warranties have special requirements.

Some states do not allow companies to sell consumer products "as is"; in those states, sellers have implied-warranty obligations that cannot be avoided. And the federal Magnuson-Moss Act prohibits a company from disclaiming implied warranties (see 16.1.6.1) for any consumer product if the company offers a written warranty for the product or sells a service contract for it.

(The above paragraph is adapted in part from the Federal Trade Commission's Businessperson's Guide to Federal Warranty Law (FTC.gov 2006); no copyright is claimed in the FTC's text.)

And state product-liability law could render a seller liable for selling a defective or dangerous product that causes death or personal injury, even if the seller sold the product "as is."

31.40.10. Warranties: An issues checklist for business planners

Drafters should consider the following issues:

1.  What exact past, present, or future fact will a party "warrant"?

2.  Would the warranting party prefer to make a representation about the warranted fact instead of a warranty? See 20.34.6.7 for discussion.

(BUT: The party that is to benefit from the warranty will always prefer that the warranting party do both: Represent, and warrant.)

3.  Will the warranting party be warranting —

  • a present fact (for example, when a seller warrants the condition of goods as delivered)?
  • a future fact (e.g., when a seller warrants that goods will perform in a certain way for a stated period of time)? This can make a difference for when the statute of limitations begins to run for a claim of breach of warranty, as discussed at 31.40.8.

4.  What exactly does the warranting party commit to do if a warranted fact turns out not to be true — anything specific, such as the Three Rs? (Repair, Replace, or Refund)?

  • If the contract is silent on that point, then the warranting party would liable in damages for any breach of the warranty.

5.  Are there any time limits to the warranting party's obligation? For example: Warranty issues must be reported to the warranting party within X days after delivery.

6.  Are there any monetary limits to the warranting party's obligation? For example:

  • Cap: The warranting party will not be liable for more than $XXX if a warranted fact turns out to be untrue; or
  • Basket: The warranting party will not be liable for breach of warranty until the resulting damages exceeds $XXX, (31.3) at which point:
    • Deductible basket: The warranting party will be liable only for damages in excess of that amount (known as a "deductible basket"); or
    • Tipping- or first-dollar basket: The warranting party will be liable for all damages after the specified amount has been reached.

31.40.11. Warranty: Is it a "guarantee"?

Colloquially the terms "warranty" and "guarantee" are alike, but technically there are some differences; see the commentary accompanying 4.8: Guaranties Protocol.

31.41. Shotgun Buy-Sell [link to example]

As one example of a so-called shotgun buy-sell agreement, see § 7.7 of Operating Agreement of Quarry Properties, L.L.C. at the SEC's EDGAR Web site.

31.42. Sole (rough notes)

31.42.1. "Sole and exclusive" – what does it mean?

See https://www.adamsdrafting.com/sole-and-exclusive/

MTA Canada Royalty (Del. Super. Ct. 2021, text acc. nn.19-39): The court interpreted an exclusive license agreement as plausibly prohibiting the licensor from selling to Home Depot, and therefore denied the licensor's motion to dismiss.

31.42.2. "Sole cost and expense" – what does it mean?

Accountants apparently distinguish between cost and expense:

A cost might be an expense or it might be an asset.

An expense is a cost that[:]

  • has expired or
  • was necessary in order to earn revenues.

We hope the following three examples will illustrate the difference between a cost and an expense. … What is the difference between cost and expense? (AccountingCoach.com, undated; formatting altered).

31.43. Subcontracts (very-rough notes)

31.43.1. Basics: What is a "subcontractor"?

Let's illustrate the subcontractor concept with a simple example. Suppose that a would-be homeowner buys an old house (a "tear-down") in a desirable neighborhood and wants to put up a new house on the site. After obtaining architectural plans:

  • The owner will typically hire a prime contractor, which is commonly referred to as the general contractor, or "GC," to actually get the house built.
  • The general contractor will in turn engage various other companies such as: • a demo company to demolish the old house and clear the site; • a foundation company to pour a new foundation; • a framing company to erect the frame of the house; • a roofing company; etc.
  • Each of these other companies is referred to as a subcontractor or "sub"; the subs will normally deal only with the general contractor and not with the owner.

31.43.2. Should subcontracting be allowed?

That will depend on the parties and the situation. Sometimes one party might want —

  • to prohibit the other party from using subcontractors at all, or
  • to require the other party:
    • to obtain the first party's prior written consent to any use of subcontractors, or
    • to get the first party's approval of the specific subcontractor(s) to be used, or
    • to notify the first party before using subcontractors, or
    • to impose specific obligations (e.g., confidentiality obligations) on any subcontractor(s), e.g., in the form of specific terms in a written subcontract;
    • to provide the first party with a copy of each written subcontract (possibly redacted to black out confidential information).

31.43.3. Can a construction subcontractor sue the owner?

From an article by New York attorney Bradley Pollina:

The typical arrangement on most construction projects is that the property owner or developer engages the services of a general contractor or construction manager, which in turn subcontracts the work out to the various trades pursuant to a number of subcontracts.

Under this standard arrangement, subcontractors seeking payment for their work are generally limited to recovering funds from the general contractor or construction manager, as that is the party they contracted with.

Generally, under such an arrangement, there is no basis for an unpaid subcontractor to sue the property owner or developer for nonpayment because there is no contract between them.

(The obvious exception is a mechanic’s lien foreclosure action, where unpaid subcontractors, among others, can directly pursue a claim against the real property at issue, even where they do not have a contract with the owner.)

Bradley Pollina, Owner Liability To Construction Subcontractors In Contract Or Quasi-Contract (JDSupra 2021) (formatting altered).

31.43.4. Prompt-payment laws can bite prime contractors that don't pay

Example: In a 2021 Ohio case, a subcontractor successfully sued a contractor for an underpayment of some $20,000. Under the state's prompt-payment law, the contractor also had to pay the subcontractor's attorney fees, amounting to nearly $65,000 — or more than three times the underlying liability. See Atlas Piers NEO v. Summit Construction Co., Inc., 2021-Ohio-2024 (affirming judgment after bench trial). ]

31.43.5. Contractor liability for subcontractor employee wages

Wage theft, where companies fail to pay their low-wage employees what they're owed, is by no means unheard of. "a study by the University of Texas and Workers Defense Project, an advocacy group, found that 1 in 5 construction workers are the victims of wage theft, the practice of denying workers pay or benefits rightfully owed them."

Rebecca Carballo, Construction workers claim wage theft at Sheldon ISD project, Houston Chronicle, Jan. 10, 2021, at B1, col. 1. ("ISD" stands for Independent School District, which is how public schools are organized in Texas.) /

32. Drafting notes

Contents:

32.1. Active voice preference (notes)

[See my note at the end of this section about its sources.]

Strive to use active voice where possible. Active voice gets to the point by putting the actor first.

Look at the following before-and-after examples:

    A song was sung by her.

    She sang a song.

But sometimes passive voice is better — for example, if the doer or actor of the action is unknown, unimportant, obvious, or better left unnamed.

Here are more hypothetical examples:

  • The part is to be shipped on 1 June. (If the actor is unclear or unimportant.)
  • Presidents are elected every four years. (The actors are obvious.)
  • Christmas has been scheduled as a workday. (The actor is better left unsaid.)

And clear, forceful, active-voice language might be inappropriate in diplomacy, in political negotiations, or in contract negotiations.

(In the original, the above sentence said "… may be inappropriate," but it’s better to stick with "might be": Use "may" for permission, "might" for possibility, as discussed at  7.2.2.)

But: Be careful not to let sloppy passive-voice drafting become a harmful false imperative (8.23).

Sources: This section "steals” from various U.S. Government sources —

This "theft" is legal, incidentally because under 17 U.S.C. § 105, copyright is not available for works that were created by officers or employees of the U.S. Government in the course of their official duties; as required by the statute, I state that I'm not claiming any copyright in those sources. See generally Copyright status of work by the U.S. government (Wikipedia.org).

In the course of official duties: Perhaps there could be an argument about the extent to which these various federal employees were not acting in the scope of their official duties when they created their plain-language document. This might be much the same as the way that the legendary Admiral Hyman Rickover, father of the nuclear Navy (in which I served), successfully claimed copyright in his speeches about education. Rickover's result, though, came only after extensive litigation, including a trip to the Supreme Court. See Public Affairs Associates, Inc. v. Rickover, 268 F. Supp. 444 (D.D.C. 1967) (again denying declaratory judgment to publisher), on remand from 369 U.S. 111 (1962), reversing and remanding (on case-or-controversy grounds) 284 F.2d 262 (D.C. Cir. 1960) (holding that Rickover's speeches had lost their copyrights due to unrestricted publication), reversing 177 F. Supp. 601 (D.C.D.C. 1959) (denying declaratory judgment to publisher because Rickover held copyrights).

32.2. Arising out of or relating to [something]

The term "arising out of or relating to" is usually interpreted broadly by courts.

Example: In Citgo (2d Cir. 2025), the court explained:

Insurance contracts ordinarily require that there be some causal link between the claimed loss and an enumerated set of covered events, and that causal link usually will come in the form of either a but-for or proximate causation requirement.

A but-for cause is the cause without which the event could not have occurred. There can be multiple but-for causes.

A proximate cause in the insurance context, by contrast, is "a single event or peril that directly causes a loss without which the loss would not have occurred.

In other words, but-for causation sweeps more broadly than proximate causation. Citgo Petroleum Corp. v. Ascot Underwriting Ltd., No. 24-0227-cv, part III.A, slip op. (2d Cir. Oct. 28, 2025) (affirming jury verdict awarding $54.2 million in damages to Citgo; insurance policy covered seizure of cargo of crude oil by Venezuelan authorities under insurrection provision in policy) (cleaned up, extra paragraphing added).

Example: "To say that a dispute is one 'arising from or in connection with maintenance performed by Williams' is to say that it had some causal connection to—that it originated from, grew out of, or flowed from—such maintenance. Dodson Int'l Parts, Inc. v. Williams Int'l Co., 12 F.4th 1212, 1220-21 (10th Cir. 2021) (cleaned up; extensive citations omitted).

Example: "The phrase 'arising from' requires only but-for causation (not proximate causation) …." Zaftr Inc. v. Kirk, No. 24-2702, slip op. (E.D. Pa. Oct. 29, 2025) (granting insurance carrier's motion for summary judgment: claimed loss was clearly excluded by policy terms) (citations of Pennsylvania- and Third-Circuit case law omitted).

The term "relating to" is relatively broad (compared with the narrower "arising out of") but it's not of unlimited scope: In the context of determining the scope of an arbitration agreement, in 2017 the Ninth Circuit noted:

And though we have recognized that the phrase 'relate to' is broader than the phrases 'arising out of' or 'arising under,' … "related to" marks a barrier by indicating some direct relationship; otherwise the term would stretch to the horizon and have no limiting purpose …. United States and Nevada ex rel. Welch v. My Left Foot Childrens Therapy, LLC, 871 F.3d 791, 798 (9th Cir. 2017) (cleaned up, citations omitted).

In 2023, Delaware's chancery court had this to say:

This Court has considered the connector "relating to" to be paradigmatically broad. Indeed, the term "relating to" is one of the far-reaching terms often used by lawyers when they wish to capture the broadest possible universe. Given its breadth, a provision that extends to matters "relating to" an agreement encompasses *any issues that touch on contract rights or contract performance." Intrepid Investments, LLC v. London Bay Capital, LLC, No. 12077, slip op. at text acc. nn.67-74. (Del Ch. Jun. 21, 2023) (cleaned up, footnotes omitted, emphasis added). Hat tip: Ken Adams (AdamsDrafting.com).

Following this principle, the Delaware court held that the plaintiff's new claims for fraudulent transfer were barred by the res judicata effect of a judgment in a prior lawsuit between the parties in New York's courts, because:

  • The plaintiff's new fraudulent-transfer claims did not "touch on" the rights and performance of an LLC operating agreement, which included a forum-selection clause requiring litigation in Delaware of any claim "arising out of or relating in any way to this [Operating] Agreement."
  • The plaintiff therefore could have brought the fraudulent-transfer in the New York lawsuit, not merely in Delaware.
  • Consequently, the new fraudulent-transfer claims were barred by the res judicata effect of the results in the New York lawsuit.

On the other hand, said the Delaware court, the plaintiff's new claims for tortious interference were not barred by res judicata from the New York lawsuit because the tortious-interference claims did "touch on" the rights and performance of the LLC operating agreement, and so the claims were subject to the operating agreement's forum-selection clause, and thus could not have been brought in the New York lawsuit.

Variation: In Caruso (1st Cir. 2023), the court noted (in a dictum) that a third-party claim might "arise from" an indemnifying party's act but not be "caused" by the act. See Caruso v. Omni Hotels Mgmt. Corp., 61 F.4th 215, 223 (1st Cir. 2023) (vacating judgment below and directing entry of judgment for Omni) (dictum; observing that "'arises from' in the [contract in suit] carries materially the same meaning as 'caused by'").

32.3. Artificial intelligence [very-rough notes]

From Armand Zottola, Have You Updated Your End User License Agreement (EULA) for 2025?:

License Grant and Restrictions

Define license scope with precision. Scope? Include whether access is for internal use only, per seat, by region, etc. Match the language to your actual product delivery model

Add explicit restrictions. Common examples include prohibitions on reverse engineering, circumvention, scraping, or use for competitive benchmarking

AI Licensing, Ownership, and Legal Compliance Usage

AI-specific licensing. If AI-generated output is involved, clarify who owns it, what can be done with it, and whether it is for internal or commercial use

Disclose AI use. Laws in Utah and Tennessee, by example, may require disclosure of AI-generated content

Clarify use of customer data for AI training. State law(s), such as California's, may require transparency around datasets used for model training

Define ownership of AI inputs and outputs. Address whether customer prompts, user-generated content, or resulting outputs are owned by the customer or vendor or are shared

Limit reliance and define risks. Include disclaimers for hallucinations, bias, or errors in generative outputs, and require human oversight where necessary

Comply with evolving state usage laws. Colorado (2024) and Maryland are enacting high-risk AI regulations

32.4. As between the parties (notes)

The term "as between the parties" is used in various places to indicate that third parties are not necessarily bound by — nor favored under — what the Con­tract says.

Example: As discussed at 29.3.3, California Evidence Code § 622 provides that (with certain exceptions), "[t]he facts recited in a written instrument are conclusively presumed to be true as between the parties thereto, " meaning that third parties would not be bound by the recital.

32.5. Checklist benefits: Everyone forgets "stupid stuff"

Why use checklists? Because even the most-competent professional will sometimes miss things — and such a lapse, if not caught in time, could have grave consequences. This was catastrophically illustrated in a 1935 prototype test flight of the legendary B-17 "Flying Fortress" bomber:

  • Before takeoff, the highly-experienced pilots and their crew neglected to make sure that wind-gust locks had been removed from certain control surfaces such as rudders and ailerons; those locks kept the control surfaces from moving while the plane was on the ground.
  • In the resulting crash, both pilots were killed — the U.S. Army's chief of flight testing and Boeing's chief test pilot. See Atul Gawande, The Checklist (NewYorker.com 2007) (archive.org copy).

(People have been killed by similar errors — failure to remove wind-gust locks — as recently as 2021.)

Those and other bitter lessons led to aviation's emphasis on checklists as a crucial backup to fallible human memory: Pilots are trained to complete a checklist before every flight (and at other important times too).

As a U.S. Air Force officer once wrote: "The majority of the notes, warnings, and cautions [in these checklists] have been written in blood." Gary S. Rudman, Checklist mentality … it’s a good thing (safety.af.mil 2012).

32.6. Conditions precedent, a.k.a. "prerequisites"

Texas's supreme court explained in 2022:

A covenant is an agreement to act or refrain from acting in a certain way.

A breached covenant gives rise to a cause of action for damages,

and a material breach excuses the other party from performance.

It is a fundamental principle of contract law that when one party to a contract commits a material breach of that contract, the other party is discharged or excused from further performance.

By contrast, a condition precedent is an event that must happen or be performed before a right can accrue to enforce an obligation,

and if an express condition is not satisfied, then the party whose performance is conditioned is excused from any obligation to perform [that particular obligation]. James Constr. Gp. v. Westlake Chem. Corp., 650 S.W.3d 392, 396-97, 415 (Tex. 2022) (affirming relevant part of judgment below awarding damages for breach) (cleaned up; presentation modified).

32.7. Consideration (as in, value) (notes)

Consideration is something studied by every first-year law student in the U.S. and similar jurisdictions, because in those jurisdictions a contract ordinarily requires at least some kind of "consideration" to be binding. See, e.g., 1464-Eight, Ltd. v. Joppich, 154 S.W.3d 101 (Tex. 2004) (nonpayment of the recited nominal consideration doesn't preclude enforcement of the parties' written option agreement) (extensively reviewing case law).

Example:: In reversing a summary judgment, the Fifth Circuit held that an email exchange between Wells Fargo and Occidental Petroleum was not a contract, even though a different agreement between the parties was a contract:

Though Wells Fargo unambiguously agreed to transfer the stock between January 6 and January 10, Occidental offered nothing in exchange. In other words, Wells Fargo received no benefit from the e-mail exchange; nor did Occidental suffer any detriment. Accordingly, the December 2019 e-mail chain, standing alone, did not create an enforceable contract. Occidental Petroleum Corp. v. Wells Fargo Bank , N.A., 117 F.4th 628, 637 (5th Cir. 2024) (emphasis added), affirming 622 F. Supp. 3d 495 (S.D. Tex. 2022) (granting summary judgment for Occidental on other grounds).

Amendments to an existing contract will often require consideration (mentioned but not discussed at 3.1.4.11).

[SEE ALSO THE GEOFFREY MILLER PIECE CITED IN GOV. LAW, at 13-16, about the differences between NY law and California law.

32.8. Contract Drafting course: Notes for students

32.8.1. The drafter- and reviewer's role as "transaction navigator"

As a contract drafter (or reviewer), you're much like a passenger in a car, truck, or other vehicle, whose driver — your client — wants your help in:

  • scoping out the available routes to the desired destination;
  • knowing the "rules of the road"; and
  • thinking about "what if?" contingencies such as traffic jams, engine trouble, bad weather, hijackers, etc.

To be sure: You won't necessarily plan for every conceivable contingency — that's how contracts tend to metastasize into the much-hated tomes of unreadable legalese.

But you have to know what's out there — and then exercise some professional judgment about how to propose a plan for the client's "journey."

32.8.2. Lighthouse "translation" exercises: Active-learning study aids

You've probably read that active learning leads to better comprehension and retention than passive reading or even highlighting — see, e.g., the Johns Hopkins Web page, Active Versus Passive Learning.

Toward that end, many of this book's descriptions of business protocols are written as "Protocols." This framing provides students with a study aid: When they translate a Protocol into conventional, deal-specific contract language, it'll help them more-actively engage with the underlying business- and legal concepts.

Here's a simplified example:

  • Lighthouse Protocol: "Payer is to pay each Biller invoice net 30 days from invoice receipt."
  • Student drafting-exercise translation (for the MathWhiz-Gigunda simulation): "Gigunda: Pay each MathWhiz invoice, in full, no later than 30 days after you receive the invoice."

To be sure, this probably doesn't seem very active. But even a little bit of mentally working with the material is helpful.

32.8.3. Hypothetical facts for the semester's simulations

This book started life, and continues, as assigned reading for the law-school course in contract drafting that I've taught since January 2010 — in recent years, as a simulation course. in contract drafting — at the University of Houston Law Center.

Many of the exercises and classroom-discussion questions in our course are set in the context of an evolving relationship between two companies that are based on several of my own present- and past client representations over the years. Students will "represent" one or the other of these (fictional) companies, namely the following:

MathWhiz: Our fictional client, "MathWhiz LLC," is based in Houston.

  • MathWhiz is headed by its founder and CEO "Mary Marvel."
  • Mary is an expert in analyzing seismic data to predict where oil or natural gas deposits might be; she "came up" in the industry working for major oil companies, then started her own company.
  • "LLC" stands for "limited liability company," which is not the same as a "corporation."
  • We don't know whether MathWhiz was formed in Texas, as opposed to Delaware, Nevada, or some other jurisdiction. (Note: Corporations are "incorporated" in a particular jurisdiction, while LLCs, limited partnerships, and other legal entities are generally referred to as being "formed" or "organized" — be sure to keep that straight.)
  • MathWhiz's business has grown; the company now employs several junior analysts, and also selectively subcontracts work to others (usually, longtime friends or colleagues of Mary's) to do specialized tasks.

Gigunda: One of MathWhiz's own clients is (the equally-fictional) "Gigunda Energy," a global oil-and-gas company headquartered in California — again, not necessarily formed nor based in California.

  • We don't (yet) know what kind of business organization Gigunda is; we also don't know Gigunda's actual legal name — that will be relevant when it comes to drafting the preamble.
  • Gigunda has a significant campus in Houston — that could be relevant if a forum-selection clause (see Protocol 21.12) ends up being discussed.
  • Gigunda expects to collect seismic data, over a period of about a year, from a potential oil field in Outer Mongolia.
  • Gigunda wants to hire MathWhiz to analyze the seismic data.

Assumptions: We'll assume that:

  • Both MathWhiz and Gigunda, most of the people are reasonable, cooperative, collegial.
  • Each party recognizes that this won't always be the case in the future.
  • Each party therefore wants to guard against future opportunistic‑, unscrupulous‑, or predatory behavior by the other party.

32.9. Contract forms

32.9.1. Contract forms: Whose to use?

If you're a small company, a quick way to kill a deal is to insist on using your contract form.

For reasons good and bad, big companies and law firms often want to use their contract forms, not yours — even when those contract forms might be gravely flawed. See generally Tara Chowdhury, Faith Chudkowski, and Mitu Gulati, The Form Knows Best, 79 U. Mia. L. Rev. 607, 618 (2025) ("The reliance on the market-standard forms reflects a broader aversion to altering familiar templates, regardless of underlying flaws or legal developments"), available at https://repository.law.miami.edu/umlr/vol79/iss4/3; Glenn D. West, The Form Doesn’t Know Anything: A Response to Chowdhury, Chudkowski & Gulati, 79 U. Mia. L. Rev. 628, 635 (2025) ("the pressure to accept what market studies supposedly demonstrate as 'market terms' is extremely powerful"), available at https://repository.law.miami.edu/umlr/vol79/iss4/4.

Certainly it's important to offer to draft the contract. And if the big company reeaally wants to do a deal with you, then you might get away with insisting on controlling the typewriter.

But bad things can happen, though, if you simply fold your arms and refuse to negotiate the other side's contract paper:

  • Even if the big company's negotiators grudgingly agree to work from your draft contract, they'll start off thinking that your company is less than cooperative (which isn't great for the business relationship).
  • Then later, when you ask for a substantive concession that's important to you, they may be less willing to go along.
  • And in any case, their agreement to use your contract form, in their minds, will be a concession on their part, meaning that you now supposedly owe them a concession.

For a vendor lawyer, there's another danger in insisting on using your own contract form: Your client's sales people might blame their lack of progress on you. Sales folks are always having to explain to their bosses why they haven't yet closed Deal X. Your insistence on using your contract form gives them a ready-made excuse: They can tell their boss that you're holding up the deal over (what they think is) some sort of petty legal [nonsense]. Even if that's not the whole story, it's still not the kind of tale you want circulating among your client's business people — and among their in-house lawyers ….

32.9.2. Contract forms: What about law-firm form files?

32.9.2.1. Ask the partner about prior agreements

When getting a drafting assignment from a partner (or a senior associate, or some other supervisor), always ask whether there's a recent actual contract that you should use as a starting point.

  • Caution: An existing contract will often reflect prior concessions that were made by one or more parties during negotiations. This means that when drafting a new contract, you should carefully review the existing contract's terms and determine whether that's really where you want to start this project.
  • Caution: Lawyers even at blue-chip law firms aren't infallible, so you won't want to conclusively presume that the existing contract is of A+ quality in every detail.
32.9.2.2. Law firm form files — how good are they?

Law firms often try to maintain form files. But seldom does anyone get paid or otherwise receive meaningful reward for doing that drudgery. So the quality and currency of law firm form files can be dicey.

32.10. Contractions in contracts?

Contractions and other accessible language are slowly catching on in legal-related writing. For example, here's a comment at plainlanguage.gov:

While many legal authorities say that contractions don’t belong in legal writing, Bryan Garner, a leading authority on legal writing, advocates their use as a way to make legal writing, including opinions and rules, less stuffy and more natural. Contractions make your writing more accessible to the user.

Research shows that that they also enhance readability.

(Extra paragraphing added, parenthetical citation omitted.)

Ross Guberman, another legal-writing guru, notes that fully 63% of judges surveyed either are OK with contractions in parties' briefs or simply don't care.

And a couple of Supreme Court justices regularly use contractions in their opinions. See, e.g., Pulsifer v. United States 601 U.S. 124, 144 S. Ct. 718, 729 n.5 (2024) (Kagan, J.); id., 144 S. Ct. at 743 (Gorsuch, J., dissenting); Alexander v. South Carolina Conf. of NAACP, 602 U.S. 1, 144 S. Ct. 1221, 1270 (2024) (Kagan, J., dissenting); Niz-Chavez v. Garland, 593 U.S. 155, 141 S. Ct. 1474, 1479 (2021) (Gorsuch, J.).

32.11. Defined terms: Best practices

Defined terms can be quite useful — not least because they allow drafters to change the definition for, say, "Purchase Price" to reflect a new dollar figure, without having to revise the dollar figure multiple times throughout the contract.

32.11.1. Defined-terms formatting

When defining a term, put the term itself in bold-faced type and quotation marks (and possibly parentheses) to make it stand out on the page and screen — that will help the reader who comes across the defined term and wonders, "what exactly does [defined term] mean?" and goes looking for the definition.

Examples:

    This Agreement is between MathWhiz LLC ("MathWhiz") ….

    This Agreement is between MathWhiz LLC ("MathWhiz") ….

    The term "Affiliate" refers to ….

    The term "Affiliate" refers to ….

BUT: Don't bold-face other uses of the defined term:

    MathWhiz is to deliver the Deliverables to Gigunda no later than the time stated in the Statement of Work.

    MathWhiz is to deliver the Deliverables to Gigunda no later than the time stated in the Statement of Work.

If using a defined term before the definition occurs, consider using a forward reference:

MathWhiz is to deliver the Deliverables (defined at Section XX) to Gigunda no later than the time stated in the Statement of Work.

32.11.2. Some benefits of "in-line" definitions

It's often convenient to include definitions "in-line" with the substantive provisions in which they are used; see, for example, the way that "Buyer" and "Seller" are defined in 29.1.

When you keep definitions together with their substantive provisions in this way, it makes it easier for future drafters to copy and paste an entire contract article or section into a new contract.

32.11.3. Have a separate section for general definitions?

It's also common to use a separate “general definitions” section and to place it in one of three spots in the contract:

  1. right after the Background section — this is perhaps the most-common practice;
  2. at the back of the contract, just before the signature blocks or as an appendix after the signature blocks: there's some evidence (albeit "N=1," i.e., one data point) that this could save parties time in negotiation;43 or
  3. in a separate exhibit or schedule (which can be handy if using the same definitions for multiple documents in a deal).

32.11.4. Pro tip: Include definition cross-references

In some contracts you might have both "in-line" definitions and a separate general-definitions section. In that situation, you should seriously consider serving future readers by including, in the separate general-definitions section, appropriate cross-references (in their proper alphabetical spots) to the in-line definitions.

That way, the general-definitions section does additional duty as a master index of defined terms.

32.11.5. Don't put substantive terms in definitions

See #4 in Bryan Garner's [Seven] Guidelines for Legal Definitions (2024):

Avoid burying substantive rules within definitions.

    For example, "'Labor' means an employer, contractor, or contractor’s assistant, provided that the contractor obtains the appropriate work order before hiring an assistant and completes the work in timely fashion."

(Emphasis and red X added.)

32.11.6. Other style preferences for defined terms

The following are some personal style preferences that help enhance readability (in my view):

– Use the phrase refers to instead of means: The former often just sounds better in different variations. See the following example (where bold-faced type is used to highlight differences and not to set off defined terms):

Confidential Information means information where all of the following are true ….

"Confidential Information" refers to information where all of the following are true ….

[MORE TO COME?]

32.11.7. Don't bother numbering alphabetized definitions

If you alphabetize your defined-terms section (as you should), there's no need to number the paragraphs. The purpose of numbering contract paragraphs is easy referencing, both internally and in later documents. That purpose is sufficiently served just by having the definitions in alphabetical order.

Example: Ken Adams gives an example of a real-world contract that contained so many defined terms, in alphabetically-lettered paragraphs, that the paragraphs went from (a), (b), (c), etc., all the way to (cccccccccc), that is, with ten "c" letters. Just imagine trying to cite that in a cross-reference or a legal brief. See Ken Adams, Deranged Definition-Section Enumeration (AdamsDrafting.com 2020).

32.11.8. Capitalization consistency is important for defined terms

It’s a really good idea to be consistent about capitalization when drafting a contract. If you define a capitalized term but then use a similar term without capitalization, that might give rise to an ambiguity in the language — which in turn might preclude a quick, inexpensive resolution of a lawsuit

That kind of bad news happened in a New York case:

  • The defendant asserted that the plaintiff’s claim was barred by the statute of limitations and therefore should be immediately dismissed.
  • The plaintiff, however, countered that the limitation period began to run much later than the defendant had said.

The court held that inconsistency of capitalization of the term "substantial completion" precluded an immediate dismissal of the plaintiff's claim — and so the presumably-costly litigation would continue. See Clinton Ass’n for a Renewed Environment, Inc., v. Monadnock Construction, Inc., 2013 NY Slip Op 30224(U) (denying defendant’s motion to dismiss on the pleadings).

Similarly: In a particular insurance policy, the term "Additional Named Insured" was held to have a different meaning than "(additional) Named Insured," for purposes of determining whether the additional insured can assert a claim for loss of rental income and soft costs resulting from construction delays. BCC Partners, LLC v. Travelers Prop. Cas. Co., 140 F.4th 465 (8th Cir. 2025) (affirming summary judgment in favor of insurance carrier).

One more example: In a UK lawsuit, a construction project experienced flooding, and the parties fought over who was potentially liable for the flooding. The case turned on whether, in the relevant contract, the term "practical completion," when uncapitalized, had the same meaning as the same term when it was capitalized. The court held that the capitalized‑ and uncapitalized terms did not have the same meaning; as result, a sprinkler-system subcontractor was potentially liable for the flooding. See GB Building Solutions Ltd. v. SFS Fire Services Ltd., (2017) EWHC 1289, discussed in Clark Sargent, Antonia Underhill and Daniel Wood, Ensure That Defined Terms Are Used Consistently; Ambiguity Can Be Costly (Mondaq.com 2017).

32.12. Divide and choose (cross-reference)

See 31.41

32.13. For the avoidance of doubt: A useful guardrail

There are those who scorn the phrase "for the avoidance of doubt"; for example, Ken Adams proclaims, "How’s this for a categorical statement: Never use for the avoidance of doubt." But the phrase can be a useful guardrail (see 32.16) against "creative" lawyer arguments about how a preceding term should be interpreted. The phrase is basically a thinly-polite way of warning opposing counsel, don't even think about trying to argue X.

Example: Protocol 9.1 states what is required of a party that agrees to use its "best efforts" to achieve a particular goal. Then, it goes on to say, "[f]or the avoidance of doubt," that the party need not do specific things (e.g., make any unreasonable effort or harm the party's own lawful interests). Example: The Texas supreme court rendered a take-nothing judgment — reversing a $100M jury verdict for punitive damages against Mercedes-Benz USA — because, the court said, the plaintiff's fraudulent-inducement claim was conclusively negated by the contract's express terms, which included some avoidance-of-doubt terms (while not using the phrase).

32.14. Gaps: Does it matter if you leave them?

Contracts sometimes set out alternative prerequisites for when a particular right or obligation will kick in. When doing so, keep in mind that if you omit a possibility, it could cause problems — as happened in one Fourth Circuit decision:

  • The contract in suit stated that a contractor was entitled to be paid by a real-estate developer if the contractor "obtain[ed] the Approvals for the Proposed Use [of specified property] …."
  • But: The contract also stated when the contractor would be entitled to payment: (i) if the developer sold the property or (ii) acquired a building permit — but not if the developer did neither.

The district court granted partial summary judgment that the contractor was entitled to be paid on an "unjust enrichment" basis; then, after a non-jury trial, the district court set the amount of payment.

The majority of the Fourth Circuit panel agreed and affirmed the district court's ruling — but: A dissenting judge argued that:

  • The developer's interpretation of the contract language was also reasonable, namely that the contractor was not entitled to be paid — under any theory — unless and until the property was either sold or developed.
  • And that (said the dissenting judge) meant that the contract language was ambiguous — which in turn meant that the district judge should have conducted an evidentiary hearing and made a determination of the parties' intent when they entered into the contract. The dissenting judge would have vacated the trial judge's partial summary judgment ruling and remanded for a hearing on that point. See Byron Martz v. Day Development Company, L.C., 35 F.4th 220 (4th Cir. 2022).

The parties dodged a bullet here, because an evidentiary hearing on this point would have been costly: The parties' counsel would have had to sift through the emails and other documentation relating to the negotiations; take the depositions of the people who were involved in the negotiations; and (possibly) hire one or more expert witnesses to try to persuade the trial judge.

32.15. Gouge (noun)

"Gouge" is a U.S. Navy term for key information, things you need to know to get the job done and/or stay out of trouble. The Perplexity GPT defines the term thusly:

In the U.S. Navy, the term "gouge" refers to critical information, tips, or insider knowledge that is shared informally among personnel. It is often considered essential for understanding the nuances of Navy life and operations. The gouge can include anything from practical advice on how to handle specific tasks or situations to the unofficial but crucial details that help sailors navigate their careers more effectively.

Here are some key points about the term "gouge" in the U.S. Navy:

  • Inside Information: Gouge is essentially the "inside scoop" or "straight dope" that provides the necessary information one needs to succeed in various situations within the Navy.
  • Informal Channel: This information is typically passed through informal channels, often referred to as the "gouge train," where experienced personnel share their knowledge with newer members.
  • Critical Tips and Tricks: It includes critical tips and tricks that are not always found in official manuals or training materials but are vital for practical success.
  • Cultural Significance: The term is deeply embedded in Navy culture, particularly in aviation and among midshipmen at the Naval Academy, where sharing the gouge is a common practice to help peers.

In summary, "gouge" in the U.S. Navy context is the valuable, often unofficial information that helps sailors and officers perform their duties more effectively and navigate the complexities of Navy life.

32.16. Guardrail provisions (notes)

It can be useful for a contract to explicitly rule out an argument that the other side might someday make. Example: In 2018 the Texas supreme court rendered a take-nothing judgment — throwing out a jury verdict awarding $100 million in punitive damages to a Mercedes dealer against Mercedes-Benz USA — because the dealer's fraudulent-inducement claim was conclusively negated by the contract's express terms. The supreme court summed up its holding and rationale:

The issue here is whether Carduco’s belief that Mercedes had promised the McAllen [sales] area to it was justified in light of the parties’ written agreement. Because that agreement[:]

  • approved and identified only Harlingen as Carduco’s dealership location,
  • provided that Carduco could not move, relocate, or change any dealership facilities without Mercedes’s prior written consent
  • provided that Carduco’s right to sell cars in any specific geographic area was nonexclusive, and
  • stated that the agreement was not intended to limit Mercedes’s right to add new dealers in the area,

we conclude that the parties’ written agreement directly contradicts Carduco’s alleged belief and thereby negates its justifiable reliance as a matter of law.

The court of appeals’ judgment affirming the award of actual and punitive damages is accordingly reversed and judgment rendered that Carduco take nothing. Mercedes-Benz USA, LLC v. Carduco, Inc., 583 S.W.3d 553, 554-55 (Tex. 2018) (emphasis, bullets, and extra paragraphing added).

A number of Lighthouse clauses are guardrail provisions — or more crudely, schmuck repellent; they're meant to dissuade aggressive counsel from trying to argue the contrary. For example:

32.17. Handwritten- vs. typewritten notes

32.18. Hereunder, etc.: Nope …

Try very hard to avoid legalese terms such as hereby, hereunder, thereunder, and the like. Such terms can be offputting to some nonlawyers, who might unconsciously assume that the terms have secret meanings comprehensible only to those who've been initiated into the Sacred Mysteries of The Law.™

Example:

a party's failure to comply with its obligations hereunder

a party's failure to comply with its obligations under this Agreement

32.19. List Consistency Rule (for drafters)

In lists, you should be able to delete any item in the list and still have the sentence make sense grammatically. Here's a very-simple example (adapted from a government plain-language manual): See Plain Language in the Legal Profession (PlainLanguage.gov, undated).

The police officer:

(a)  told us to observe the speed limit; and

(b)  we should dim our lights.

If you deleted (a), then grammatically, the remaining list would read: "The police officer we should dim our lights." Which makes no sense.

Let's try again:

    The police officer:

(a)  told us to observe the speed limit; and

(b)  asked us to dim our lights.

Much better.

32.20. List Orphan Rule (for drafters)

See the markup below:

    1.  Within 60 days after the last day of an applicable Earn-Out Year, Purchaser shall:

      (a) prepare a statement reflecting its Calculation of the Annual Earn-Out Payment for each Earn-Out Year, for five years.

2.  [More language]

    1.  Within 60 days after the last day of an applicable Earn-Out Year, Purchaser shall prepare a statement reflecting its Calculation of the Annual Earn-Out Payment for each Earn-Out Year, for five years.

2.  [More language]

32.21. List Parallelism Rule

In lists, you should be able to delete any item in the list and still have the sentence make sense grammatically.

Here's an example in a multi-paragraph style (from a student in a past semester):

c) Earn-Out Provision [THIS IS BAD DRAFTING]

          i. Within 60 days after the last day of an applicable Earn-Out Year, Purchaser shall:

                    a) prepare a statement reflecting its Calculation of the Annual Earn-Out Payment for each Earn-Out Year, for five years.                           i) For example, following Earn-Out Year three the Annual Earn-Out Payment Calculation would be applicable to year three only.

                    b) The year 5 statement must in addition include:

                          i) reasonable supporting documents, and

                          ii) a Payment to Seller.

Note how syntactically the b) subdivision doesn't fit as part of the list of "c) Earn-Out Provision" — the b) subdivision reads, in effect, "… Purchaser shall The year 5 statement must in addition include …"; this doesn't make sense as a sentence.

DCT REWRITE OF JUST THIS PART [but leaving the numbering style as it was]:

c) Earn-Out Provision

          i. Within 60 days after the last day of an applicable Earn-Out Year, Purchaser shall :_ +a) prepare a statement reflecting its Calculation of the Annual Earn-Out Payment for each Earn-Out Year, for five years.

                          (For example, following Earn-Out Year three the Annual Earn-Out Payment Calculation would be applicable to year three only.)

          b) ii. The year 5 statement must in addition include:

                          i) (A) reasonable supporting documents, and

                          ii) (B) a that years's Earn-Out Payment to Seller.

32.22. List-Caps Rule

Don't capitalize the first words of list-item verbs.

(This assumes that the "list" isn't a series of complete sentences.)

    2.06. Referral Term. The “Referral Term”:

(1)  Begins upon the effective date of this Referral Agreement; and

(2)  Ends at the end of the day on the date two years after that.

    2.06. Referral Term. The “Referral Term”:

(1)  begins upon the effective date of this Referral Agreement; and

(2)  ends at the end of the day on the date two years after that.

Why? Because conceptually, the entire list is a single, complete sentence, and (in English, at least) you wouldn't capitalize ordinary words in the middle of a sentence.

32.23. List-Numbering Rule (for drafters)

Don't use "1.1" etc. for list items.

Example:

    8.  Rent: Each month, Alice will pay Bob the following:

              8.1  base rent of $100; and

              8.2  percentage rent of 5% of Alice's gross sales for the previous month.

    8.  Rent: Each month, Alice will pay Bob the following:

              (1)  base rent of $100; and

              (2)  percentage rent of 5% of Alice's gross sales for the previous month.

Or, if the list items are short, they could be combined into a single line:

    8.  Rent: Each month, Alice will pay Bob: (1) base rent of $100; and (2) percentage rent of 5% of Alice's gross sales for the previous month.

… perhaps with "romanettes" (lower-case Roman numerals in parentheses), thusly:

    8.  Rent: Each month, Alice will pay Bob: (i) base rent of $100; and (ii) percentage rent of 5% of Alice's gross sales for the previous month.

32.24. Lists - include them, or not?

Maybe not: Instead of providing a possibly-incomplete list, could you just say "all [something]"? (See 20.3.)

32.25. Microsoft Word

32.25.1. Microsoft Word key features

[Students: Items 1-5 are fair game for testing; the remaining items are nice to know but won't be tested.]

1.  The safest way to format a paragraph without corrupting the document and crashing the Word program is to format the style of the paragraph, not the individual paragraph itself. See, e.g., The Styles advantage in Word (https://goo.gl/v8Jbej); Item 3 in the 2013 list of tips to avoid crashing Word, by John McGhie (https://goo.gl/VxqJKs). NOTE: McGhie's tip no. 2 is to avoid Track Changes, but I've never had a problem with that — at least so far as I know ….

2.  To create a heading, use Heading styles: Heading 1, Heading 2, etc.

3.  Headings can be automatically numbered by using the Bullets and Numbering feature under Format. The following apply mainly to the formatting of styles, but can be used with caution to format individual paragraphs:

4.  On rare occasions, to adjust the line spacing within a specific paragraph, use the menu sequence: Format | Paragraph | Indents and Spacing | Spacing (almost smack in the middle of the dialog box on a Mac).

5.  To adjust the spacing between paragraphs, use the menu sequence: Format | Paragraph | Indents and Spacing menu. Don’t use a blank line to separate paragraphs — adjust the spacing instead. See generally Practical Typography: Spacing Between Paragraphs (PracticalTypography.com: https://goo.gl/vNjeKF).

6.  To keep one paragraph on the same page with the following paragraph (which is sometimes useful), use the menu sequence Format | Paragraph | Line and Page Breaks | Keep with Next.

Here are some other tips:

7.  A table of contents can be useful in a long contract. To create a table of contents, in the References tab, use the Table of Contents dropdown box and select Custom Table of Contents.

8.  Tables can sometimes be useful in contracts. To remove the borders from a table (the way Word normally creates them), first use the menu sequence: Table | Select | Table. Then use the menu sequence: Format | Borders & Shading | Borders | None.

9.  To copy and paste a short snippet from a Web page into a Microsoft Word document without messing up the formatting of the paragraph into which you’re pasting the snippet, use the menu sequence: Edit | Paste Special | Unformatted text. (Alternatively: Edit | Paste and Match Formatting.)

32.26. Notwithstanding anything to the contrary …. (draft notes)

This is from HNA Holdings 422 Fulton (GP) LP v TSCE 2007 422 Fulton GP, LLC, 2025 NY Slip Op 31121(U) (Comm'l Div.).

•  Section 3.02(e) of a nearly-200-page limited-partnership agreement says, "Notwithstanding anything to the contrary herein …" (emphasis added).

–  AND: Section 6.01(e) itself starts out in a similar — but not identical — fashion: "Notwithstanding anything to the contrary in this Agreement …" (emphasis added).

–  BUT: For the facts in question, § 6.01(e) of the agreement turns out to conflict with § 3.02(e).

QUESTION: Which takes precedence?

(See also the summary in Peter Mahler, Court's Decision in High Stakes Case Cuts Through the “Fog of Dueling ‘Notwithstanding’ Clauses” (JDSupra.com 2025).)

32.27. Numbers Rules

These are style rules, not hard-and-fast requirements, so:

  • Again: If your supervisor (e.g., law-firm partner) prefers one way over another, then do it that way (see 30.6).
  • Don't make purely-stylistic revisions in another party's draft contract, for reasons discussed at 8.11.

32.27.1. One through ten, then 11, 12, 13, etc.

1.  Spell out the numbers one through ten; use numerals for 11, 12, 13, etc. EXCEPTION: For payment terms, it's "net 10 days," not "net ten days" (see generally 4.13.3). Some style guides say to spell out numbers one through nine. See also When Should I Spell Out Numbers? (Grammerly.com).

2.  Both in the same sentence? Consider using just numbers: The quiz will contain between 8 and 12 questions.

3.  Don’t start a sentence with numerals; either spell out the numerals in words or (preferably) rewrite the sentence.

42 was Douglas Adams’s answer to The Ultimate Question of Life, the Universe, and Everything.

According to the late novelist Douglas Adams, the answer to The Ultimate Question of Life, the Universe, and Everything is … 42.

32.27.2. Exception: Numbers at the start of a sentence

Usually spell out numbers at the start of a sentence — but consider rewriting the sentence.

Example (using percentages; see also the percentages rule below):

    90% (approximately) of baseball salary disputes are resolved by settlement due to the arbitration process without having to actually go to arbitration.

    Ninety percent (approximately) of baseball salary disputes are resolved by settlement due to the arbitration process without having to actually go to arbitration.

[Even better:]

    Approximately 90% of baseball salary disputes are resolved by settlement due to the arbitration process without having to actually go to arbitration.

32.27.3. Exception: Numbers in payment terms

Use digits for payment terms, e.g., "net 10 days" or "net 5 days" (see 4.13.3).

Examples:

    Payment is due net ten days.

    Payment is due net 10 days.

32.27.4. Exception: Numbers as percentages

Usually use digits for percentages. But: Spell out a percentage if it’s at the beginning of a sentence — or better sstill, just use numbers and rewrite the sentence to avoid starting with the percentage.

Example: 30% Thirty percent of the proceeds will be donated to charity.

Better: Of the proceeds, 30% will be donated to charity.

32.27.5. Exception: Numbers in clock time

Time is written with digits: 5:00 p.m. not five p.m.

32.27.6. Exception: Numbers in series

From Strunk & White, The Elements of Style ch. IV (1920) (copyright expired):

Do not spell out dates or other serial numbers. Write them in figures or in Roman notation, as may be appropriate.
–  August 9, 1918
–  Rule 3
–  Chapter XII
–  352nd Infantry

32.27.7. Million, billion, trillion – but not thousand

Example: More than 300,000,000 300 million people live in the United States.

Example: Alice will pay Bob $5 thousand $5,000.

32.27.8. Money

1.  Don't say "in United States dollars" if there's no possibility of confusion. (If you feel the need to be clear that dollars refers to U.S. dollars, you can do that in your definitions & usages section; see 32.11.)

2.  If currency confusion is a possibility, then use ISO 4217 currency abbreviations such as USD, as in: Buyer will pay USD $30 million. (The USD abbreviation goes where indicated, not after the numbers.)

3.  Don't spell out dollar amounts in words. Example: Alice will pay Bob five thousand dollars $5,000.

4.  Omit zero cents unless relevant. Example: Alice will pay Bob $5,000.00 $5,000. But: Alice will pay Bob $3,141.59.

32.28. Offer letters [TO DO] (crude notes for now)

Numbered paragraphs are handy (for future referencing).

In a letter, stick to "you" and "the Company" as the pronouns — it'd look really funny for a letter to refer to "the Company" and "the Employee."

Consider an "exploding offer" (deadline for returning countersigned copy or signing electronically).

Definitely mention that the employee would (or might?) have to sign other agreements, e.g.:

  • confidentiality agreement
  • invention-ownership agreement
  • arbitration agreement

Concerning "signing and returning a copy": Nowadays this would be done electronically, e.g., via DocuSign, Adobe Acrobat, etc.

32.29. Offer, acceptance, etc.

(Law students: This should be just a review of key points from your 1L Contracts course.)

An agreement will typically be legally binding as a contract if it meets the usual requirements, such as:

  1. There must be a "meeting of the minds," generally in the form of an offer by one party that is accepted by another party.
  2. "Consideration" must exist; roughly speaking, this means that the deal must have something of value in it for each party — and the "something" can be most anything of value, including for example:
    • a promise to do something in the future, or
    • a promise not to do something that the promising party has a legal right to do; this is known as "forbearance."
  3. Both parties must have the legal capacity to enter into contracts — a child or an insane person likely would not have legal capacity, nor might some unincorporated associations.

Caution: In some circumstances, a showing of consideration might not be necessary, such as in a "contract under seal" under English law and in the doctrine of promissory estoppel, both of which are beyond the scope of this essay.

Note: In some jurisdictions, the mere fact that a contract is in a signed writing might be sufficient consideration. Example: The Tennessee supreme court cited a state statute stating that "[a]ll contracts in writing signed by the party to be bound, or the party's authorized agent and attorney, are prima facie evidence of a consideration," and noted that "the party claiming a lack of consideration for a validly executed contract has the burden of overcoming this presumption." The court held that an educational company's contractual promise to produce as many pharmaceutical continuing-education programs "as is feasible" constituted sufficient consideration, and thus the contract was not illusory. See Pharma Conference Education, Inc. v. State, 703 S.W.3d 305, 312 (Tenn. 2024) (reversing and remanding dismissal of breach-of-contract claim), citing Tenn. Code Ann. § 47-50-103 (emphasis added).

32.30. Online forms: Any good?

Thousands of contract forms are available online from commercial companies that screen and curate contracts filed with the U.S. Securities and Exchange Commission EDGAR Web site. Some of these commercial sites include:

Other sites such as RocketLawyer.com and LegalZoom.com offer forms, but it's hard to know what their quality is, nor whether they take into account the "edge cases" that sometimes crop up in real-world situations.

If you want to search the SEC's EDGAR Web site yourself, it helps to know that many if not most contracts will be labeled as Exhibit 10.something (and possibly EX-4.something) under the SEC's standard categorization. This means that the search terms "EX-10" (and/or "EX-4") can help narrow your search.

Example: A quick search and scan turned up the 2019 separation agreement between CBS Corporation (the TV network) and its now-former chief legal officer.

Pro tip: Online contract forms are best relied on as sources of ideas for issues to address. The clause language isn't necessarily what you'd want to use in a contract for a client.

Pro tip: In some contracts you find online, the "Notices" provision might include the names and addresses of the parties' outside counsel — if counsel are in name-brand firms, that might give you increased confidence. Example: In the real-estate lease between Stanford University (landlord) and Tesla (tenant), the counsel to be notified for Stanford was a partner at Bingham McCutchen, a large Boston-based firm (which later closed its doors when hundreds of its lawyers left to join the Morgan Lewis firm).

32.31. Oral contracts can be binding — but …

There's an old law-student joke that an oral contract isn't worth the paper it's printed on. But that's not quite true: Oral contracts are "a thing," and long have been.

32.31.1. Oral, not verbal

This book generally uses the term oral contract, not verbal, because:

  • Strictly speaking a written contract is also "verbal," that is to say, "of, relating to, or consisting of words." See Verbal (adjective).
  • On the other hand, contracts made by, say, gestures, such as on an old-fashioned stock-exchange or commodities trading floor, would not be verbal.
  • We'll leave to experts, such as Professor Eric Goldman, the question whether an agreement expressed exclusively in "emojis," see 3.14.4, would qualify as a "verbal" agreement.

32.31.2. When would an oral agreement be enforceable?

Whether an oral agreement is enforceable as a contract depends on the evidence that's brought before the court; enforceability basically depends on two things:

  1. The contract cannot be of a type that, by law (the Statute of Frauds), must be in writing (see the discussion at 32.35); and
  2. The jury,* after hearing the witness testimony and weighing the evidence, must find that there was, in fact, an oral agreement — and what the terms were in that agreement.

    (* Or the judge in a nonjury trial, or the arbitrator in an arbitration.)

The evidence could include a series of emails and/or text messages — which might not be enough to be binding in themselves as a written contract, but they can provide evidentiary support for a jury verdict that an oral contract was reached.

Example: In an Idaho supreme court case, a jury held that an employer had breached an oral agreement to make a severance payment to a terminated employee. See Hawes v. Western Pacific Timber LLC, 477 P.3d 950, 963 (Id. 2020) (affirming judgment on jury verdict).

Example: A small Texas company fired its accounting director as part of a corporate reorganization. The fired employee sued for breach of an alleged oral promise to pay him a bonus. The fired employee testified under oath that he had been promised, by the company's vice president of operations, that he would get a bonus — not merely that he might get a bonus. The company apparently didn't offer any contrary testimony. The jurors believed the employee and rendered a verdict in his favor; the trial court granted judgment notwithstanding the verdict, but an appeals court reversed and reinstated the jury verdict. See Elaazami v. Lawler Foods, Ltd., No. 14-11-00120-CV, slip op. at part III (Tex. App—Houston [14th Dist.] Feb. 7, 2012) (citing cases).

Incidentally, under Texas law, the fired employee was also entitled to recover his attorney fees for bringing the lawsuit, under section 38.001 of the Texas Civil Practice & Remedies Code, discussed at 21.2.5.2. See Elaazami, cited above, at part V (rendering judgment that Elaazami was entitled to attorney fees and remanding for determination).

32.31.3. Would just an oral contract be safe? (Maybe not.)

While oral contracts can be enforceable as discussed above, they can be dangerous — suppose that:

  • Party A claims that Party A and Party B entered into an oral contract.
  • Party B might disagree that the parties entered into a contract at all, or might simply disagree about the terms of the alleged contract.

Almost by definition, much will depend on witness testimony at trial — and which witnesses the jury believes. See the examples discussed at 32.31.2 above.

Now recall that under standard American legal principles — including the Seventh Amendment to the U.S. Constitution:

  • It's the exclusive province of the jury to assess witness credibility and to weigh the evidence — that is, to sort through inconsistent testimony, documents, etc., and decide which is entitled to more weight and which to less weight.
  • Then, if a reasonable jury could have reached the verdict that the actual jury did, then the actual jury's verdict must stand. (There are limited exceptions to that rule, none of which is important here.)

That's why many businesses strongly prefer written contracts.

32.31.4. Oral contracts have resulted in big-bucks jury verdicts

Example: In a Minnesota case with modestly-complicated facts, a jury awarded a bank $1.9 million for breach of an oral agreement to buy assets. See Vermillion State Bank v. Tennis Sanitation, LLC, 969 N.W.2d 610, 623 (Minn. 2022) (id. at 623).

Example: In a Missouri case, a manufacturer of farm machinery terminated its oral agreement with a reseller. The jury found that the oral agreement had given the terminated reseller an exclusive territory; the jury awarded $5.8 million to the reseller for breach of contract and violation of the state's good-cause dealership termination statute. See S&H Farm Supply, Inc. v. Bad Boy, Inc., 25 F.4th 54 (8th Cir. 2021).

32.31.5. Louisiana's special case

A Louisiana statute provides that "When, in the absence of a legal requirement, the parties have contemplated a certain form [of contract], it is presumed that they do not intend to be bound until the contract is executed in that form." La. Civ. Code Ann. art. 1947 (1985), quoted in CAM Logistics, L.L.C. v. Pratt Indus., Inc., No. 24-30806, slip op. at 9 (5th Cir. 2025) (affirming summary judgment: alleged oral agreement to three-year warehouse lease was unenforceable) (citations omitted).

32.31.6. Use a written contract to replace an informal oral agreement?

As addressed at 3.3, parties will sometimes use a written agreement to confirm — and replace —a prior oral agreements. The "replace" part can be useful: The oral agreement could well be binding in itself, but the parties might disagree about what was agreed; this could easily resut in expensive litigation, so it's better to replace the oral agreement with a written one.

32.32. Paragraph-numbering preference

  1. Strongly consider using the paragraph numbering scheme in this template Word document. (That's for the paragraph numbering only; in the Word document, the table style used for the preamble and signature blocks is for illustration purposes.)
  2. Don't use more than two unnumbered paragraphs per numbered subsection: Doing so makes it harder for readers to quickly find specific unnumbered paragraphs; imagine seeing a reference to "the ninth grammatical paragraph in section 3.2" — and then having to count the paragraphs: "one, two, three, four …."
  3. Preferably: Avoid Roman-numeral outline numbering I., A., 1., etc. If a skimming reader saw, e.g., "4. Blah blah blah," she might have to scroll way up to see that it's section VIII.F.4; better to have it be section 8(f)(4).

32.33. Precatory language (rough notes)

The statement, "Buyer would like the Right of First Refusal on the sale of abutting lot if ever sold," …. expresses the buyer’s wish to engage in a future transaction. This expression of a wish does not create the necessary manifestation of mutual assent to be bound by the provision." … Thus, "would like" is a precatory phrase that is insufficient to create a binding contractual provision. Keegan v. Estate of Bradbury, 2025 ME 13, slip op. ¶¶ 5-6 (Maine Feb. 11, 2025) (emphasis added).

32.34. Speed-up rules

  1. Draft short, single-subject paragraphs (2.5)
  2. Draft Freaky Friday terms that would work if roles were reversed (2.1)
  3. Reviewing a draft: Help the other side — but not too much (8.11).
  4. Hamburger for the guard dog? See 8.21.

32.35. Statute of Frauds: Some types of contract must be in writing

For public-policy reasons, the law will not allow some oral agreements to be enforced — in effect, the law says: For this type of contract, we want to be very sure that the parties really, truly did agree. So we're not going to just take one party's word for it: Even that party swears under oath that the parties did agree, we still want to see it in writing.

This public policy is reflected in the Statute of Frauds, which says, in various versions, that certain types of contract are not enforceable unless they're documented in signed writings — or unless one of various exceptions applies, which we'll discuss (only very briefly) at 32.35.2.

32.35.1. MY LEGS: A Statute of Frauds mnemonic

Many law students learn the mnemonic "MY LEGS" to help remember what types of contract are covered by the Statute of Frauds:

M - Marriage: Prenuptial agreements and other contracts relating to marriage must be in writing (and, in some jurisdictions, must meet other requirements, such as each spouse being represented by his- or her own legal counsel, or the prenup being notarized, as discussed at 29.7.8).

Y - Year: Agreements that cannot be performed within one year, such as an agreement to employ someone for, say, two years (this usually excludes contracts that don't specify any duration at all). BUT: An agreement that reasonably could be performed within a year is likely not within the Statute, even if it turned out that the agreement actually did take longer than a year to perform. See the extended discussion of this topic, as analyzed under Texas law, in Chase v. Hodge, 95 F.4th 223, 228-29 (5th Cir. 2024) (affirming summary judgment that Statute of Frauds barred enforcement of alleged "gentleman's agreement of ownership" of LLC) (citing Texas cases).

L - Land: Agreements that call for transfer of an ownership interest of land (or similar interests in land such as an easement).

E - Executor: Agreements in which the executor of a will agrees to use the executor's own money to pay a debt of the estate.

G - Goods: Agreements for the sale of goods for $500.00 or more (the exact amount might vary).

S - Surety: Agreements in which one party agrees to act as a surety (guarantor — see Protocol 4.8) for someone else's debt.

32.35.2. Exceptions to the Statute of Frauds

Even an oral agreeent that's subject to the Statute of Frauds might be enforceable if one of various exceptions applies, such as partial performance — those exceptions are mostly beyond the scope of this discussion.

Caution: When it comes to real-estate contracts, California's version of the Statute of Frauds states that: "An electronic message of an ephemeral nature that is not designed to be retained or to create a permanent record, including, but not limited to, a text message or instant message format communication, is insufficient under this title to constitute a contract to convey real property, in the absence of a written confirmation that conforms to the requirements of [citation omitted]."

Massachusetts's version of the Statute of Frauds contains an express exemption for "a contract to pay compensation for professional services of an attorney-at-law or a licensed real estate broker or real estate salesman acting in their professional capacity." See Mass. Gen. L. ch. 259, § 7, cited in Huang v. Ma, No. SJC-13325, slip op. (Mass. Feb. 2, 2023) (reversing summary judgment).

(DCT note: Gee, I wonder how that exception came to be enacted into law — d'ya suppose lawyers and real-estate brokers make any political contributions to state legislators?)

32.36. Streamlining sentences

It’s too easy to let a sentence get fat and sloppy. Here are a few examples:

BEFORE AFTER
They made the decision to give their approval. They decided to approve it.
Or: They approved it.
The team held a meeting to give consideration to the issue. The team met to consider the issue.
Or: The team considered the issue.
We will make a distribution of shares. We will distribute shares.
We will provide appropriate information to shareholders. We will inform shareholders.
We will have no stock ownership of the company. We will not own the company’s stock.
There is the possibility of prior Board approval of these investments. The Board might approve these investments in advance.
The settlement of travel claims involves the examination of orders. Settling travel claims involves examining orders.
Use 1.5 line spacing for the preparation of your contract draft. Use 1.5 line spacing to prepare your contract draft.
  Better: Use 1.5 line spacing for your draft contract.

32.37. They: Plural only (in a contract)

In contracts, don't use "they" as a gender-neutral singular pronoun — if necessary, repeat the noun in question.

(This isn't meant as a political statement, but as advice on reducing the chances — too early in your career — of attracting unfavorable attention from partners, clients, etc., who might dislike the term for whatever reason.)

Here's an example, inspired by a clause in a merger agreement that allowed one party to terminate the agreement if a government authority issued a blocking order and the terminating party was unsuccessful at getting the order removed:

    The Party seeking to terminate this Agreement under this Section must show that they used their best efforts to remove the Blocking Order.

    The Party seeking to terminate this Agreement under this Section must show that the Party used best efforts to remove the Blocking Order.

32.38. True and correct: Don't

You might see — and be tempted to draft — contract language such as (hypothetically): "ABC certifies that each statement in its request for expense reimbursement is true and correct." See, e.g., the merger agreement under which United Airlines acquired Continental Airlines, in which section 7.2(a) states in part that United was not obligated to close the acquisition unless "the representations and warranties of Continental set forth in Section 4.8(a) shall be true and correct [sic] on the date of this Agreement …." ]

What does that mean, exactly? In my view, it's sloppy to talk about something being "true and correct," because:

  • It's arguably redundant — is there a difference between true and correct? If so, what is that difference? Maybe "true" means accurate and "correct" means that it conforms to some standard — but what's that standard? To paraphrase one of my former students: That's a conversation we don't want to have. See also the discussion of "doublets," intentional use of synonyms derived from different languages such as "indemnify and hold harmless," in the commentary at 20.24.
  • The phrase true and correct sometimes won't go far enough: Let's assume that the statement: Jane was in the room is accurate, in that Jane was indeed in the room, but leaves a gap (see 32.14) because it doesn't indicate whether or not others were also at the meeting.

Perhaps in an archaic sense the term true might be interpreted broadly to mean materially complete and accurate. But there seems to be little reason to take a chance that a judge would see it that way,

The phrase complete and accurate does the job better. Say that instead.

33. Exercises for Contract Drafting course

33.1. Exercise: Selling a used computer (part 1)

Students: We'll do this exercise in class; feel free to look it over in advance.

FACTS: Let's assume you have an elderly, childless Uncle Ed who has no legal background.

•  Uncle Ed wants to sell his used, high-end, mid-2012 Macbook Air laptop computer. (He's still sharp as a tack and wants to "move up" to a more-powerful machine to use some of the latest AI technology.)

•  Uncle Ed wants to get $275 for his 2012 machine (which at this writing is actually close to the going rate) and to sell the computer "as is."

•  After Uncle Ed mentioned on Facebook that he wants to sell his computer, one of his high-school acquaintances, "Dale," contacted him and said he wants to buy the computer.

•  Uncle Ed and Dale were never close in high school; they haven't seen each other since graduation some 50 years ago.

•  Uncle Ed has asked you what to do to make sure he's "protected."

QUESTION 1: Is a written contract legally necessary? Practically necessary? Explain your thinking.

QUESTION 2: Would your answer to #1 be any different if Dale was Uncle Ed's closest friend, going all the way back to their high-school days?

QUESTION 3: Assuming Uncle Ed does want to have something in writing, what form could that writing take? (Be creative!)

QUESTION 4: On paper, make a bullet-point list of the "minimal" topics that such a written agreement should include. (Part of your job is to try to think of what could go wrong, and, with your client, to decide whether it's worth trying to address those risks in your draft contract.)

You'll probably think, "I don't like this, because I don't know what the [something] I'm doing — and you're probably right about that. But it's OK: That's a feature (of the pedagogy), not a bug.

Relatedly: See 28.2 concerning a four-sentence confidentiality agreement, between business friends, in letter form.

33.2. Exercise: Selling a used computer (part 2)

Students: We'll do this exercise in class; feel free to look it over in advance.

Draft a short contract for the sale:

  • Use short, single-subject, "sound bite" paragraphs, with active voice whenever possible. (For more on this subject in a future reading assignment, see 2.5.)
A traffic sign with the word LEGALESE inside a red circle with a red diagonal slash through it, all on a white background
  • Use language that the parties themselves would almost certainly understand. (Eschew — err, abjure — err, avoid legalese wherever possible.)

Footnotes:

1

A worse BLUF example: The following single-paragraph clause is from the merger agreement by which Hewlett-Packard (HP, Inc.) acquired well-known headset manufacturer Plantronics; it clocks in at 928 words (!) and addresses some 10 or 11 (!) separate discussion points:

(b) For six years after the Effective Time, Parent and the Surviving Corporation (jointly and severally) shall indemnify and hold harmless all Indemnified Persons with respect to acts or omissions occurring at or prior to the Effective Time to the fullest extent that the Company or the applicable Company Subsidiary would be permitted to do so by the DGCL or, if any such Company Subsidiary is not organized in Delaware, the applicable Law of organization of such Company Subsidiary, in the event of any threatened or actual claim, suit, action, proceeding or investigation (a “Claim”), whether civil, criminal or administrative, based in whole or in part on, or arising in whole or in part out of, or pertaining to (i) with respect to the present and former directors and officers of the Company that are Indemnified Persons, (A) the fact that the Indemnified Person is or was a director (including in a capacity as a member of any board committee), officer, employee or agent of the Company, any of the Company Subsidiaries or any of their respective predecessors or (B) this Agreement or any of the transactions contemplated hereby, and (ii) the fact that such Indemnified Person is or was a director or officer of any Company Subsidiary and his or her respective actions or omissions in his or her capacity as a director or officer of one or more of the Company Subsidiaries, in each case whether asserted or arising before, on or after the Effective Time, against any losses, claims, damages, liabilities, costs, expenses (including reasonable attorney’s fees and expenses in advance of the final disposition of any claim, suit, proceeding or investigation to each Indemnified Person (to the extent required or, in the case of advancement, permitted by the DGCL, upon delivery to Parent of an unsecured, interest‑free undertaking by or on behalf of such Indemnified Person to repay such amount if it shall ultimately be determined that such Indemnified Person is not entitled to be indemnified)) and all judgments, fines and, subject to the remainder of this Section 6.07(b), amounts paid in settlement of or in connection with any such threatened or actual Claim. Neither Parent nor the Surviving Corporation shall settle, compromise or consent to the entry of any judgment in any threatened or actual Claim for which indemnification could be sought by an Indemnified Person hereunder, unless such settlement, compromise or consent includes an unconditional release of such Indemnified Person from all liability arising out of such Claim or such Indemnified Person otherwise consents (not to be unreasonably withheld, conditioned or delayed) in writing to such settlement, compromise or consent. Parent and the Surviving Corporation shall cooperate with an Indemnified Person in the defense of any matter for which such Indemnified Person is indemnified hereunder; provided, however, that Parent or its applicable Subsidiary may, at its option and expense, assume and control the defense of any Claim with one counsel for all similarly situated Indemnified Persons subject to such Claim, if such counsel is reasonably acceptable to a majority of the Indemnified Persons who may be entitled to indemnification for such Claim; provided that, if such Claim commenced after the date hereof and prior to the Effective Time and relates to this Agreement, the Merger or the fiduciary duties of the board of directors of the Company, then at the election of a majority of such Indemnified Persons, such counsel shall be the counsel of record prior to the Effective Time for such Claim; provided further that any Indemnified Person may fully participate at its own expense in the defense of such Claim through separate counsel of its own choosing; and provided further that if, in the reasonable opinion of counsel of any Indemnified Person, there is a conflict of interest between such Indemnified Person and Parent or its applicable Subsidiary, or because of Parent or its applicable Subsidiary’s failure to defend for a period of 60 days any such Claim, any such Indemnified Person shall have the right to select separate counsel of its own choosing to participate in the defense of such Claim on its behalf, and the reasonable costs and expenses (including reasonable attorneys’ fees) of defending such Claim shall be indemnified by Parent and the Surviving Corporation to the extent otherwise indemnifiable hereunder. If Parent or its applicable Subsidiary so assumes the defense of any Claim for such Indemnified Persons pursuant to the foregoing sentence, none of Parent or any of its Subsidiaries will be liable to such Indemnified Persons for any defense costs or expenses (including attorneys’ fees and expenses) subsequently incurred by the Indemnified Persons in the defense of such Claim (but excluding, for the avoidance of doubt, any other losses, claims, damages, liabilities, costs or other expenses therefrom, including from the disposition of any such Claim, that are subject to indemnification pursuant to this Section 6.07). Neither an Indemnified Person nor the Parent, the Surviving Corporation of any of its Subsidiaries shall settle, compromise or consent to the entry of any judgment in any threatened or actual Claim for which indemnification could be sought without the prior written consent of Parent, in the case of the Indemnified Persons, or the Indemnified Persons, in the case of Parent, the Surviving Corporation or any of its Subsidiaries (in each case, such consent not to be unreasonably withheld, conditioned or delayed). Each Indemnified Person shall reasonably cooperate with Parent and its applicable Subsidiaries, at Parent’s sole expense, in the defense of any matter for which such Indemnified Person could seek indemnification hereunder.

2

See United States v. Cohen, 724 F. Supp. 3d 251 (S.D.N.Y. 2024) (declining to impose sanctions on Cohen and his attorney for submitting "fake" case citations obtained by Cohen using Google Bard); see also, e.g., Benjamin v. Costco Wholesale Corp., 779 F. Supp. 3d 341 (E.D.N.Y. 2025) (imposing $1,000 sanction on time-pressured and repentant attorney for submitting reply brief and sworn declaration with "phony" case citations that attorney did not check); Mata v. Avianca, Inc., 678 F. Supp. 3d 443 (S.D.N.Y. 2023) (imposing $5,000 penalty on attorneys for submitting "fake" citations to non-existent opinions, then doubling down when challenged; ordering attorneys to write letters to each judge falsely identified as author of fake opinion).

  • Oversight requires experience. For many lawyers, that experience came over years of repeated drafting, reviewing, and revising of contracts, with senior lawyers reviewing their work, building up mental muscle memory.
  • But this kind of hands-on training of junior lawyers might become less common as clients increasingly use AI tools to draft and review contracts. (It's not unlike how the decline of jury trials in small cases led to fewer and fewer junior lawyers getting invaluable first-chair trial experience.)

So: How can junior lawyers grow into competent judges of AI work-product quality? This book gives contract newcomers a way to begin acquiring "artificial experience" (a term my late dad, a fighter pilot and then human-factors psychologist in the U.S. Air Force, would sometimes use).

3

The former CEO of software giant Computer Associates, Sanjay Kumar, served nearly ten years in federal prison for securities fraud through, among other things, backdating sales contracts (NY Times). Kumar was also fined $8 million and agreed to settle civil suits by surrendering nearly $800 million (NY Times). Kumar wasn't the only executive at Computer Associates (now known as just CA) to get in trouble for backdating. All of the following went to prison or home confinement: – the CFO: seven months in prison, seven months home detention (NY Times); the general counsel: two years in prison, and also disbarred (court opinion); the senior vice president for business development: ten months of home confinement (NY Times); the head of worldwide sales: seven years in prison (WSJ).

All of this mess came about because the Computer Associates executives orchestrated a huge accounting fraud: On occasions when the company realized that its quarterly financial numbers were going to miss projections, it "held the books open" by backdating contracts signed a few days after the close of the quarter. This practice was apparently referred to internally as the "35-day month." According to CA, all the sales in question were legitimate and the cash had been collected; the only issue was one of the timing of "revenue recognition," to use the accounting term.

  • The company had recorded the sales on its books ("booked the sale") a few days earlier than was proper under generally-accepted accounting principles, or "GAAP."
  • But that was enough to put the sales revenue into an earlier reporting period than it should have been.
  • And that, in turn, was enough to send all those CA executives to prison. (CA press release).

Likewise, the former CFO of Media Vision Technology was sentenced to three and a half years in federal prison because his company had inflated its reported revenues, in part by backdating sales contracts. Because of the inflated revenue reports, the company's stock price went up, at least until the truth came out, which eventually drove the company into bankruptcy.

4

Electronic signature laws: See generally the federal Electronic Signatures in Global and National Commerce Act ("E-SIGN Act"), 15 U.S.C. § 7001 et seq., which provides in part (subject to certain stated exceptions) that, for transactions "in or affecting interstate or foreign commerce," electronic contracts and electronic signatures may not be denied legal effect solely because they are in electronic form.

At the U.S. state level, 47 states, the District of Columbia, and Puerto Rico, and the U.S. Virgin Islands have adopted the Uniform Electronic Transactions Act ("UETA"). The remaining three states — Illinois, New York, and Washington — have adopted their own statutes validating electronic signatures. See, e.g., Naldi v. Grundberg, 80 A.D.3d 1, 908 N.Y.S.2d 639 (N.Y. App. Div. 2010).

UK law allows electronic signatures as well — see [UK] Law Commission, Electronic Execution of Documents (2019), at https://perma.cc/UCQ7-U94M.

Looking at the specific case of Texas law: Under the definition of signature at § 1.007 of the Texas Business Organizations Code, "a writing has been signed by a person when the writing includes, bears, or incorporates the person's signature. A transmission or reproduction of a writing signed by a person is considered signed by that person …."

5

Hanover Am. Ins. Co. v. Tattooed Millionaire Ent., LLC, 974 F.3d 767, 773 (6th Cir. 2020) (in insurance-fraud scheme, owner of famed House of Blues admitted engaging in what court described as "forgery [of receipts] on a grand scale") (the owner was later sentenced to 27 months in federal prison); see also, e.g., Saad v. SEC, 980 F.3d 103, 104 (D.C. Cir. 2020) (affirming broker-dealer's permanent bar from FINRA-associated employment for misappropriating employer funds, including falsifying an expense report and forging receipts), prior proceeding, 718 F.3d 904, 906 (D.C. Cir. 2013) (broker-dealer did not contest culpability); United States v. Daniels, No. 8:21-cr-287-VMC-CPT, slip op. (M.D. Fla. Jul. 13, 2023) (denying defendant's motion for new trial after conviction for identity theft and other counts; co-conspirator had claimed reimbursement for $1,100 using forged receipt); White & Case LLP v. Kim, 2022 NY Slip Op 33631(U) (denying, in part, defendant's motion to dismiss: law firm claimed that former legal assistant had routinely submitted false reimbursement requests, some with forged receipts); State v. Ganz, 2015 NY Slip Op 25438, 50 Misc. 3d 79, 84 24 N.Y.S.3d 486 (App. Div. 2015) (affirming, in part, school employee's conviction for criminal possession of forged instrument — employee had altered expense receipts and submitted them for reimbursement).

6

Late-submitted invoices: In 2006, Calgon Carbon Corporation, a New York Stock Exchange company, learned that some $1.4 million in outside-counsel invoices hadn't been properly recorded as expenses for the relevant financial periods.

Calgon Carbon's accounting department didn't properly record the law firm invoices on the company's books because the company's general counsel, i.e., the company's chief in-house lawyer, hadn't processed the invoices. (DCT note: I'm pretty sure I read an article, which I can't find, to the effect that the general counsel had stuck the invoices in his desk drawer instead of submitting them to the accounting department as he should have done.)

The law firm's invoices were significant in amount — and when the invoiced amounts were properly recorded as expenses for the relevant periods, the company had to restate its financial results for three different quarterly reporting periods.

The day after Calgon Carbon announced its restated numbers, the company's share price dropped by more than 24%, on something like eight times normal trading volume. (Calgon Carbon's historical share price can be found at Investing.com.) See an SEC filing about Calgon Carbon's then-forthcoming restatement (Mar. 27, 2006); see also Rick Stouffer, Calgon Carbon profits fall (TribLive.com Mar. 29, 2006 ).

The Calgon Carbon general counsel apparently lost his job because of this: On the same day that the company announced its restatement, it also announced publicly that "the employment contract between the Company and [its general counsel] was terminated in connection with [his] leaving the employ of the Company." See an SEC filing on the same day as the company's restatement filing, along with an article, Calgon Carbon releases lawyer, reports more losses (TribLive.com Mar. 28, 2006).

7

See, e.g., Martin Marietta Materials, Inc v. Vulcan Materials Co., 56 A.3d 1072 (Del. Ch.) (Strine, C.), aff'd, 68 A.3d 1208 (Del. 2012) (en banc).

8

The air-conditioning company Carrier was found to have infringed the copyright in computer software, which Carrier had licensed from a software vendor, by having a third party create workalike software and then ceasing to pay the original vendor.

The relevance here is that a jury awarded the vendor $5 million — or 2.2% of Carrier's total profits for the period in question — as "disgorgement" copyright damages. See ECIMOS, LLC v. Carrier Corp., 971 F.3d 616 (6th Cir. 2020) (affirming judgment on jury verdict in relevant part). A separate damage award for breach of contract was reduced on appeal; see id. at 644.

9

At the MGM Grand Hotel ("MGM") casino in Las Vegas, the casino's "Hallelujah Hollywood" floor show was found to infringe the copyright in the Broadway musical Kismet because:

  • MGM was licensed to use the Kismet material for the movie of the same name, and for elevator music.
  • MGM was not licensed to use the material for a floor show.

The resulting damage award against MGM for copyright infringement included 2% of MGM's profits from the hotel operations as a whole, including profits from the casino itself. See Frank Music Corp. v. Metro-Goldwyn-Mayer, Inc., 886 F.2d 1545 (9th Cir. 1989) (Frank Music II).

Inside baseball for litigators: From an evidentiary perspective, it didn't help MGM's case that MGM's annual report had praised the infringing floor show's contribution to MGM's hotel- and casino operations, saying that "the hotel and gaming operations … continue to be materially enhanced by the popularity of the hotel's entertainment[, including] 'Hallelujah Hollywood,' the spectacularly successful production revue…." Frank Music I, 772 F.2d 505, 517 (9th Cir. 1985) (some alterations by the court).

10

In 2025, Allstate spun off a line of business (for $2 billion). The spun-out business continued to use software that Allstate had previously licensed from a vendor. The vendor promptly sued Allstate and others for $80 million, alleging direct and indirect copyright infringement. See Stephen Gillespie, Use of Software by Divested Business After Spinout Brings $80,000,000 Lawsuit.

11

"Enforcing a usury savings clause in this circumstance would undermine Michigan's usury laws because it would nullify the statutory remedies for usury, thereby relieving lenders of the obligation to ensure their loans have a legal interest rate." Soaring Pine Capital Real Estate & Debt Fund II, LLC v. Park Str. Grp. Realty Svcs., LLC, 511 Mich. 89, 999 N.W.2d 8, 11 (2023) (reversing and remanding court of appeals' affirmance of summary judgment; cleaned up, extra paragraphing added).

12

Usury-savings clauses unenforceable in New York: See American E Group LLC v. Livewire Ergogenics Inc., No. 1:18-cv-3969, slip op. at 1 (S.D.N.Y. Jan. 28, 2020); see also id. at part III.C at 12 & n.13 (extensive citations of N.Y. case law).

For a detailed review of the history of New York's usury law, see the Adar Bays opinion by the state's highest court, which held that if interest charged on a loan to a corporate borrower is determined to be criminally usurious, then the contract is void ab initio (Latin for "from the outset"). See Adar Bays, LLC v. GeneSYS ID, Inc., 37 N.Y.3d 320, 325, 179 N.E.3d 612 157 N.Y.S.3d 800, 2021 NY Slip Op 05616 (2021) (on certification from 2d Cir.), subsequent proceeding, Adar Bays, LLC v. GeneSYS ID, Inc., 28 F.4th 379 (2d Cir. 2022) (vacating and remanding summary judgment order).

13

In its January 2013 comments in the Federal Register concerning this part of the rule, the Department of HHS had this to say:

Disclosures by a business associate pursuant to § 164.504(e)(4) and its business associate contract for its own management and administration or legal responsibilities do not create a business associate relationship with the recipient of the protected health information because such disclosures are made outside of the entity’s role as a business associate.

However, for such disclosures that are not required by law, the Rule requires that the business associate obtain reasonable assurances from the person to whom the information is disclosed that[:]

  • it [the information] it will be held confidentially and used or further disclosed only as required by law or for the purposes for which it was disclosed to the person[;] and
  • the person [i.e., the recipient of the information] notifies the business associate of any instances of which it is aware that the confidentiality of the information has been breached.

78 Fed. Reg. 5566, 5574 (Jan. 25, 2013) (formatting lightly edited).

14

See, e.g., DeWolff, Boberg & Assoc., Inc. v. Pethick, 133 F.4th 448, 452-53 (5th Cir. 2025) (affirming summary judgment dismissing former employer's claims; employer failed to distinguish between public- and non-public information and failed to identify what specific information constituted a trade secret); accord, Double Eagle Alloys, Inc. v. Hooper, 134 F.4th 1078, 1088 (10th Cir. 2025) (same — even though the former employee had downloaded 2,660 digital files from his company computer to an external storage device); cf. Syntel Sterling Best Shores Mauritius Ltd. v. TriZetto Group Inc., 68 F.4th 792 (2d Cir. 2023), part II.A (2d Cir. 2023) (affirming trial court judgment and declining to overturn jury's implicit finding that trade-secret owner had sufficiently identified its trade secrets).

15

Confidential Information detailed list: Here's a pretty-detailed list of possible types of Confidential Information to consider as a starting point for a custom list; it's harvested from various agreements that I've reviewed over the years:

The term Confidential Information encompasses, by way of example and not of limitation, the following types of information when the information is otherwise eligible under this Agreement: Algorithms. Audit reports. Biological materials. Business plans. Business records. Circuit records. Commercial information. Compounds. Computer programs. Contracts. Construction records. Data-center designs. Designs. Diagrams. Documents. Draft publications. Drawings. Engineering records. Financial information. Financial projections. Financial statements. Forecasts. Formulas. Hardware items. Ideas. Interpretations. Invention disclosures. Leases. Machine-readable data. Maps. Market projections. Marketing information. Methods. Offers. Operational data. Opinions. Patent applications (when unpublished). Plans. Pricing information. Procedures. Processes. Product development plans. Product information programs. Projections. Proposals. Research data. Research plans. Samples. Server-configuration designs. Source code for computer programs. Specifications. Strategies. Tax bills. Technical information. Technical reports. Technological developments. Test data. Title reports.

16

See SiOnyx LLC v. Hamamatsu Photonics K.K., 981 F.3d 1339, 1343, 1344 (Fed. Cir. 2020) (affirming judgment after jury verdict that defendant had breached NDA; recipient didn't return confidential information as required by NDA).

17

See Healthcare Resources Mgmt. Gp., LLC, v. EcoNatura All Healthy World, LLC, No. 9:20-cv-81501, slip op. at parts V.A.4 and V.A.5 (S.D. Fla. Oct. 27, 2021) (granting summary judgment that plaintiff had shown no evidence that plaintiff had actually disclosed, to co-defendants, plaintiff's alleged trade secrets).

18

See S.W. Energy v. Berry-Helfand , 491 S.W.3d 699, 708 (Tex. 2016).

19

See Natalie Posgate, 13 Years Later, Trade Secrets Legal Battle Is Over … Almost (TexasLawbook.net 2021) (paywalled). The case seems to have been Texas Advanced Optoelectronic Solutions, Inc. v. Renesas Electronics America, Inc., 895 F.3d 1304, 1313 (Fed. Cir. 2018) (reversing, in part, judgment on jury verdict of trade-secret misappropriation) (cleaned up, citation omitted); after remand, ams-OSRAM USA Inc. v. Renesas Electronics America, Inc., 133 F.4th 1337 (Fed. Cir. 2025) (mostly affirming monetary awards but vacating and remanding computation of prejudgment interest),

20

The customer's lawyer might not have realized that this was a win for my client: Without a Cleveland forum-selection stipulation, the customer likely wouldn't have been able to sue the client in Cleveland at all, because the courts in Cleveland likely wouldn't have had personal jurisdiction over the client.

Of course, that wouldn't have stopped the customer from filing suit anyway — which would have meant that the client would have to spend time and money in trying to get the case dismissed or transferred.

In contrast, my client would have been able to sue the Cleveland-based (prospective) customer in Houston, because the customer had significant operations in Houston.

The customer's lawyer apparently didn't tumble to the fact that, by agreeing to drop the forum-selection clause, he was making a potentially-big concession.

21

Example: Various companies — Adidas, Gap, TJ Maxx, Foot Locker, and more — dropped Kanye West (now legally known as "Ye") because of comments he made in tweets, on TV shows, etc.

Example: Actor Kevin Spacey was dropped by his publicist and his agency after Spacey was accused of sexual assault and other misconduct (he was later found not liable in a Manhattan civil lawsuit and then acquitted of criminal charges by an English jury); Spacey was also removed from his starring role in the Netflix series House of Cards.

Example: Similarly, in a Fifth Circuit case, an investment advisor was fired from her company after she sent a Skype message to her office manager — which went viral — concerning candidates for an open receptionist position: "I specifically said no blacks. I’m not a prejudiced person, but our clients are 90 per­cent white, and I need to cater to them, so that interview was a complete waste of my time." Cure & Assocs., P.C. v. LPL Financial, LLC, 118 F.4th 663, 667 (5th Cir. 2024).

22

"Satisfactory" cases: See also, e.g.:

  • Caradigm USA LLC v. PruittHealth, Inc., 964 F.3d 1259, 1269 (11th Cir. 2020);
  • J.D. Cousins & Sons, Inc. v. Hartford Steam Boiler Inspection & Ins. Co., 341 F.3d 149, 153 (2d Cir. 2003) (disagreeing that subjective, good-faith standard applied but affirming on grounds that inspector's conduct was objectively reasonable);
  • Doubleday & Co., Inc. v. Curtis, 763 F.2d 495, 500-01 (2d Cir. 1985) (ruling that actor Tony Curtis was obligated to return $50,000 advance because he submitted what the publisher regarded as an unpublishable manuscript for a second novel as a follow-up to his successful first novel);
  • Turner v. Ewing, 625 S.W.3d 510, 520 (Tex. App.—Houston [14th Dist.] 2020) (affirming judgment on jury verdict that homeowners owed damages and attorney fees to builder);
  • Rudzik Excavating, Inc. v. Mahoning Valley Sanitary Distr., 2017 Ohio 8630, 101 N.E.3d 38, 47 ¶ 53 (Ohio App. 2017) (affirming sanitary district's denial of motion for directed verdict; issue of fact existed as to whether district's engineer's determination was objectively reasonable) (cleaned up, citations omitted);
  • 2-5 Corbin on Contracts § 5.33;
  • 13 Williston on Contracts § 38:22, cited in Kenneth A. Adams, A Manual of Style for Contract Drafting § 13.722 (4th ed. 2017).
23

See Trone Health Services, Inc. v. Express Scripts Holding Co. 974 F.3d 845, 851-52 & n.4 (8th Cir. 2020) (citing cases, but holding that, for other reasons, plaintiffs had not stated a claim for relief); Smith v. JPMorgan Chase Bank, NA, No. 12-40816, slip op., text acc. n.2, 519 Fed. Appx. 861, 864 (5th Cir. Mar. 22, 2013) (affirming summary judgment in favor of bank), citing a collection of cases in Franklin v. BAC Home Loans Servicing, LP, No. 3:10-CV-1174-M, slip op. at n.14 (N.D. Tex. Jan. 26, 2011) (Lynn, J., partially granting motion to dismiss).

24

See, e.g.: • U.S.: See 18 U.S.C. § 201 (prohibiting bribing of federal officials); Racketeer Influenced and Corrupt Organizations (RICO) Act, 18 U.S.C. §§ 1961-1968; Foreign Corrupt Practices Act (for foreign sales involving U.S. companies and their foreign affiliates); False Claims Act (for sales to the government); • UK: See Bribery Act 2010. • See also Mark F. Mendelsohn, The Anti-Bribery and Anti-Corruption Review: USA (TheLawReview.co.uk 2020), which is extensively footnoted and appears to be quite thorough; it seems to be an excerpt from a book of the same title

25

Here are a few real-world examples of channel partnership agreements: • Cisco Indirect Channel Partner Agreement (SEC.gov); • Partner with HubSpot (Hubspot.com); Microsoft Partner Network (Microsoft.com); • Salesforce Partner Program (Salesforce.com).

26

Even in California, A's duty to defend B might not apply if A "can conclusively show by undisputed facts that plaintiff's action is not covered by the agreement." See, e.g., Cal. Civ. Code 2778(3); Crawford v. Weather Shield Mfg. Inc., 44 Cal. 4th 541, 553 (2008); Centex Homes v. R-Help Constr. Co., 32 Cal. App. 5th 1230, 1237 (2019), citing Montrose Chemical Corp. v. Superior Court, 6 Cal. 4th 289, 298, 861 P.2d 1153 (1993).

27

As Dentons partner Stafford Matthews pointed out in a 2014 LinkedIn discussion thread (membership required): "Under the common law of most states, including New York and Illinois for example, an indemnitor generally has no duty to defend unless the contract specifically requires such defense." (Emphasis added.) Mr. Matthews was responding to one of my comments in that discussion thread; he cited case law from New York and from the Seventh Circuit. See Bellefleur v. Newark Beth Israel Med. Ctr., 66 A.D.3d 807, 809 (N.Y. App. Div. 2d Dep't 2009); CSX Transp. v. Chicago & N. W. Transp. Co., 62 F.3d 185, 191-192 (7th Cir. 1995).

For a comparison of Texas, California, and New York law on this point (with citations), see an article by a Morgan Lewis partner. See Jared Wilkerson, Real-World Litigation Impacts of Contract Clauses in Energy Contracts: Clarity of Indemnity Provisions (JDSupra.com 2022).

28

First-party vs. third-party indemnity obligations: Extensive case-law citations can be found in the parties' briefs in an unsuccessful petition to the Texas supreme court in Claybar v. Samson Exploration LLC, No. 09-16-00435-CV (Tex. App.—Beaumont 2018, pet. denied). For more recent treatments, see also AGK Sierra de Montserrat, L.P. v. Comerica Bank, 109 F.4th 1132 (9th Cir. 2024) (reversing district court's award of attorney fees; California law is first-party only); Jacobson Warehouse Co. v. Schnuck Markets, Inc., 13 F.4th 659, 670 (8th Cir. 2021) (affirming judgment after a jury trial; indemnity clause covered only third-party claims, and so an indemnity carve-out from contract's exclusion of consequential damages did not apply to limit first-party losses); Schneider Nat'l Carriers, Inc. v. Kuntz, No. N21C-10-157-PAF, slip op. part II.C, text acc. nn.297 et seq. (Del. Super. Ct. Apr. 25, 2022) (contract's attorney-fee provision "clearly and unambiguously reflects the parties' intent that it applies to first-party claims").

29

Non-recourse language from a Delaware case:

Except to the extent expressly set forth otherwise in the Confidentiality Agreement,

(a) no past, present, or future stockholder, member, partner officer, director, manager, employee, incorporator, agent, attorney, or Representative of the Acquired Companies or the Seller or any of their respective Affiliates and

(b) no past, present, or future stockholder, member, partner officer, director, manager, employee, incorporator, agent, attorney, or Representative of the Buyer or its Affiliates[,]

shall have be deemed to[:]

(i) have made any representations or warranties, express or implied, in connection with the Transactions, or

(ii) have any personal Liability to the Buyer for any obligations or Liabilities of any Party under this Agreement for any claim based on, in respect of, or by reason of, the Transactions.

Except to the extent expressly set forth otherwise in the Confidentiality Agreement,

all claims, obligations, liabilities or cause of action (whether in Contract or in tort, in law or in equity) that may be based upon, in respect of, arise under, out or by reason of, be connected with, or relate in any manner to this Agreement, or the negotiation, execution or performance of this Agreement,

may be made only against the Parties to this Agreement.

It is further understood that any certificate or certification contemplated by this Agreement and executed by an officer of a Party shall be deemed to have been delivered only in such officer's capacity as an officer of such Party (and not in his or her individual capacity) and shall not entitle any Party to assert a claim against such officer in his or her individual capacity. AmeriMark Interactive, LLC v. AmeriMark Holdings, LLC, No. N21C-12-175 MMJ CCLD (Del. Supr. Ct. Nov. 3, 2022) (extra paragraphing added) .

30

Non-recourse language from a New York case:

Owner's obligations hereunder are intended to be the obligations of Owner and of the corporation which is the sole general partner of Owner only and no recourse for any obligation of Owner hereunder, or for any claim based thereon or otherwise in respect thereof, shall be had against any incorporator, shareholder, officer or director or Affiliate, as such, past, present or future of such corporate general partner or any limited partner of Owner, or against any direct or indirect parent corporation or Owner or any other subsidiary or Affiliate of any such director indirect parent corporation or any incorporator, shareholder, officer or director, as such, past, present or future, of any such parent or other subsidiary or Affiliate. Iberdrola Energy Projects v. Oaktree Capital Mgmt. L.P., 2024 NY Slip Op 03798, 231 A.D.3d 33, 35-36 216 N.Y.S.3d 124 (App. Div.) (affirming dismissal of complaint: Non-recourse provision barred majority of plaintiff's claims against defendants, and plaintiff's fraud claim, which would otherwise have survived nonrecourse provision, was not sufficiently pleaded).

31

Termination for reputation risk:

Example: A manufacturer and distributor of Stetson cowboy hats was sued for antitrust violations by a retailer. The retailer was upset because, during the COVID-19 pandemic, the retailer's owner had posted, to the retailer's Instagram account, a photograph depicting a yellow Star of David image with the words "Not Vaccinated." The Stetson distributor thereupon cut off sales to the retailer. The case later settled. See Complaint, HatWrks, LLC v. RHE Hatco, Inc., No. 3:22-cv-00068 (M.D. Tenn. Feb. 1, 2022); Mike Leonard, Stetson Distributor Settles Retailer’s Suit Over Holocaust Post (BloombergLaw.com 2022) (paywalled).

Example: Walmart and other retailers were confronted with a similar problem when a clothing factory in Bangladesh burned, killing over 100 people.

Example: Walgreens ended its relationship with troubled blood-testing company Theranos. (NYTimes.com); the company's founder, Elizabeth Holmes, was later sentenced to 11 years in federal prison for defrauding investors.

Example: Car manufacturer Hyundai terminated one of its dealerships because the New York attorney general had obtained a court judgment against the dealership for having engaged in fraudulent and illegal business practices. See Giuffre Hyundai, Ltd. v. Hyundai Motor America, 756 F.3d 204 (2d Cir. 2014).

Example: The Twin Peaks "breastaurant" organization terminated the franchise of a restaurant in Waco, Texas, after a shootout between rival motorcycle gangs left nine dead. "The company laid the blame on the managers of the Waco franchise who 'chose to ignore the warnings and advice from both the police and our company, and did not uphold the high security standards we have in place to ensure everyone is safe at our restaurants.'" (CNN.com).

32

Own-goal termination:

Example: A party terminated a contract for what it claimed was a material breach by the other party, but the appellate court held that the breach wasn't material — and this, said the court, assumed that the other party's actions were a breach at all; so, said the court, the alleged breach didn't justify termination. See Hess Energy Inc. v. Lightning Oil Co., 276 F.3d 646, 649-51 (4th Cir. 2002) (reversing summary judgment). The Hess Energy case is also discussed at 18.9.2.3, concerning assignment without consent as a material breach.

Example: In a Houston case, Earth Power A/C:

  • A geothermal HVAC contractor breached a contract with a homeowner, whereupon the homeowner stopped paying the contractor.
  • A jury found that both parties had thereby breached.
  • But: The contractor's prior breach didn't excuse the homeowner's failure to pay, because (said the appeals court) the evidence didn't conclusively establish the materiality of the contractor's breach.
  • Consequently, the homeowner was still on the hook to pay the contractor — despite the contractor's prior breach. See Earth Power A/C and Heat, Inc. v. Page, 604 S.W.3d 519, 524 (Tex. App.–Houston [14th Dist.] 2020) (reversing and rendering to restore jury verdict, awarding attorney fees to contractor per contract).

Example: In an Indiana federal-court case:

  • Two brothers entered into a contract — negotiated by the 25-year-old son of one of the brothers — to buy more than three million eggs per week from an agri-business.
  • The arrangement didn't work out, putatively due to reduced demand for eggs.
  • The brothers and son/nephew repudiated the contract and sued the agri-business for a declaratory judgment and for damages.
  • The agri-business counterclaimed, and the jury sided with the agri-business, awarding it more than $1.5 million in damages.

(This case provides yet another illustration of the general rule: If you want to sue someone, you'd better be prepared for the counterclaim — because there usually will be a counterclaim.) See Rexing Quality Eggs v. Rembrandt Enterprises, Inc., 360 F. Supp. 3d 817 (S.D. Ind. 2018) (granting, in part, agri-business's motion for summary judgment that brothers were liable for breach), subsequent proceeding, 953 F.3d 998, 1000 (7th Cir. 2020) (affirming dismissal of subsequent case, summarizing jury verdict in first case).

33

Ending time: Example: A company's bid for a construction contract was time-stamped as having been submitted at 11:01 a.m.; the deadline was 11:00 a.m. Technical analysis indicated that the time clock was fast, and that the actual time of the bid submission was sometime between 11:00 a.m. and 11:01 a.m. British Colombia's supreme court held that the bid was untimely. See Smith Bros. & Wilson (B.C.) Ltd. v. B.C. Hydro, 30 BCLR (3d) 334, 33 CLR (2d) 64 (1997).

Counterexample: In another case, on the other hand, contract bids were due no later than 1 p.m. The winning bid was submitted at 1 p.m. and 30 seconds. The Ontario court of appeals held that the bid was timely submitted because the clock had not yet reached 1:01 p.m. See Bradscot (MCL) Ltd. v. Hamilton-Wentworth Catholic District School Board, 42 O.R. (3d) 723, [1999] O.J. No. 69 ]

34

See this spaghetti-clause section, which I've broken up, from the merger agreement between United Airlines and Continental Airlines, at https://tinyurl.com/UAL-CAL (SEC.gov):

9.4   Interpretation.  When a reference is made in this Agreement to an Article or Section, such reference shall be to an Article or Section of this Agreement unless otherwise indicated. [DCT comment: It's archaic legalese to use "such reference shall be to …" instead of simply "the reference is to …."]

The table of contents, index of defined terms and headings contained in this Agreement are for reference purposes only and shall not affect in any way the meaning or interpretation of this Agreement. [DCT comment: Where headings are concerned, this "principle" is nothing more than a crutch for incompetence — when a judge has to determine the meaning of a contract term, why shouldn't she be able to rely on a heading?]

Any capitalized term used in any Exhibit but not otherwise defined therein shall have the meaning assigned to such term in this Agreement.

Whenever the words “include,” “includes” or “including” are used in this Agreement, they shall be deemed to be followed by the words “without limitation.”

The words “hereof,” “hereto,” “hereby,” “herein” and “hereunder” and words of similar import when used in this Agreement shall refer to this Agreement as a whole and not to any particular provision of this Agreement.

The term “or” is not exclusive.

The word “extent” in the phrase “to the extent” shall mean the degree to which a subject or other thing extends, and such phrase shall not mean simply “if.”

The definitions contained in this Agreement are applicable to the singular as well as the plural forms of such terms.

Any agreement, instrument or Law defined or referred to herein means such agreement, instrument or Law as from time to time amended, modified or supplemented, unless otherwise specifically indicated.

References to a person are also to its permitted successors and assigns.

Unless otherwise specifically indicated, all references to “dollars” and “$” will be deemed references to the lawful money of the United States of America.

The term “made available” and words of similar import means that the relevant documents, instruments or materials were[:]

(A) posted and made available to the other party on the Intralinks due diligence data site, with respect to United, or on the Bowne due diligence data site, with respect to Continental, as applicable, maintained by either company for the purpose of the transactions contemplated by this Agreement, prior to the date hereof, or

(B) publicly available by virtue of the relevant party’s filing of a publicly available final registration statement, prospectus, report, form, schedule or definitive proxy statement filed with the SEC pursuant to the Securities Act or the Exchange Act, prior to the date of this Agreement.

No provision of this Agreement will be interpreted in favor of, or against, any of the parties to this Agreement by reason of the extent to which any such party or its counsel participated in the drafting thereof or by reason of the extent to which any such provision is inconsistent with any prior draft of this Agreement, and no rule of strict construction will be applied against any party hereto.

The United Disclosure Schedule and the Continental Disclosure Schedule, as well as all other schedules and all exhibits hereto, will be deemed part of this Agreement and included in any reference to this Agreement.

The United Disclosure Schedule and the Continental Disclosure Schedule set forth items of disclosure with specific reference to the particular Section or subsection of this Agreement to which the information in the United Disclosure Schedule or Continental Disclosure Schedule, as the case may be, relates;

provided, however, that any fact or item that is disclosed in any section of the United Disclosure Schedule or the Continental Disclosure Schedule so as to make its relevance[:]

(i) to other representations made elsewhere in the Agreement,

(ii) to the information called for by other sections of the United Disclosure Schedule or the Continental Disclosure Schedule or

(iii) to the annexes or exhibits to this Agreement reasonably apparent[,]

shall be deemed to qualify such representations or to be disclosed in such other sections of the United Disclosure Schedule, the Continental Disclosure Schedule or the annexes or exhibits to this Agreement, as the case may be, notwithstanding the omission of any appropriate cross-reference thereto;

provided further that, notwithstanding anything in this Agreement to the contrary, the inclusion of an item in either such disclosure schedule as an exception to a representation or warranty will not be deemed an admission that such item represents a material exception or material fact, event or circumstance or that such item has had or would reasonably be expected to have a Material Adverse Effect on United or Continental, as the case may be.

This Agreement will not be interpreted or construed to require any Person to take any action, or fail to take any action, if to do so would violate any applicable Law.

References to the “other party” or “either party” will be deemed to refer to United and Merger Sub, collectively, on the one hand, and Continental, on the other hand.

All electronic communications from a Person shall be deemed to be “written” for purposes of this Agreement.

35

Rainbow Energy Marketing Corp. v. American Midstream (Alabama Intrastate) LLC, No. 17-24591 slip op. at 10, ¶ 54 (Harris Cty. [Tex.] Dist. Ct. Jul. 29, 2019) (findings of fact and conclusions of law, reproduced in appendix to appellant's amended brief filed Dec. 21, 2020).

36

Class-based voting: As a hypothetical example, let's assume that:

  • A Corporation has three different classes of voting shares, with 100 voting shares Class A; 900 voting shares in Class B; and 10,000 non-voting shares in Class C; and
  • A Corp.'s relevant governing document states that a board candidate would not be elected unless both the Class A shares and the Class B shares voted in favor of the candidate. (Depending on the jurisdiction, the governing document might be the articles of incorporation, or it might be the bylaws.)

In that situation, more than 50% voting power of A Corp. would consist of the power to vote at least 51 out of the company's 100 Class A shares and at least 451 out of the 900 Class B shares. (The Class C non-voting shares don't matter here.)

37

Willful — New York law: New York's highest court looked to the doctrine of ejusdem generis in holding that, in context (in connection with a carve-out to a limitation of liability), the contractual term willful acts referred to tortious conduct, not merely to mere intentional nonperformance of the contract. See, e.g., Metropolitan Life Ins. Co. v. Noble Lowndes Int'l, Inc., 84 N.Y.2d 430, 438, 643 N.E.2d 504, 618 N.Y.S.2d 882 (1994).

38

Willful — other judicial definitions: The meaning of willful came under review in a 1998 U.S. Supreme Court decision that arose because section 523(a)(6) of the Bankruptcy Code provides that debts from "willful and malicious injury" are not dischargeable in bankruptcy. The Court held that, in context, the term willful requires a showing of intent to cause injury, not merely intent to take the action that resulted in the injury. See Kawaauhau v. Geiger, 523 U.S. 57, 61-62 (1998).

Then in 2016, in a patent-infringement case, the Court held that the term willful infringement refers to "[t]he sort of conduct [that] has been variously described in our cases as willful, wanton, malicious, bad-faith, deliberate, consciously wrongful, flagrant, or—indeed—characteristic of a pirate." Halo Elecs., Inc. v. Pulse Elecs., Inc., 579 U.S. 93, 136 S. Ct. 1923, 1932 (2016).

BUT: In 2007, in a case under the Fair Credit Reporting Act, the Supreme Court held that in that context, the term "willful" violation encompassed reckless violations. See Safeco Ins. Co. v. Burr, 551 U.S. 47, 127 S. Ct. 2201, 2208-09 (2007) (reversing and remanding; "GEICO did not violate the statute, and while Safeco might have, it did not act recklessly").

One Texas appellate court has held that "willful misconduct means deliberate mismanagement committed without regard for the consequences. * * *  [W]illful misconduct does not require a subjective intent to cause harm[.]" Apache Corp. v. Castex Offshore, Inc., 626 S.W.3d 371, 381 (Tex. App.—Houston [14th Dist.] 2021, no pet. hist.) (affirming judgment on jury verdict against Apache: exculpatory clause did not limit Apache's liability because of its so-called "willful misconduct"), citing [dubiously, in my view] Mo-Vac Serv. Co. v. Escobedo, 603 S.W.3d 119, 125-26 (Tex. 2020) (reversing court of appeals and rendering take-nothing judgment that under Texas worker's compensation statute, employer was not liable for truck driver's accidental death, and worker-compensation insurance was exclusive remedy, because evidence did not support claim that employer believed accident was substantially certain to occur).

On the other hand, in Delaware, the term "requires a showing of intentional wrongdoing, not mere negligence, gross negligence or recklessness." Bandera Master Fund LP v. Boardwalk Pipeline Partners, LP, No. 2018-0372, slip op. at 169 (Del. Ch. Nov. 12, 2021) (cleaned up, citations omitted; after bench trial, holding that general partner was liable for nearly $690 million in damages) (Google Scholar copy), rev'd on other grounds, Boardwalk Pipeline Partners LP v. Bandera Master Fund LP, 288 A.3d 1083, 1123 (Del. 2022) ("[a] degree of uncertainty is not enough to show that Wang engaged in willful misconduct").

39

To like effect, see: U.S. Trinity Energy Servs., L.L.C. v. SE Directional Drilling, L.L.C, 135 F.4th 303 (5th Cir. 2025) (affirming denial of petition to vacate arbitration award and granting motion to confirm award); Quality Custom Dist'n Svcs. LLC v. Teamsters Local 710, 131 F.4th 597 (7th Cir. 2025) (affirming denial of motion to vacate arbitration award in which arbitrator interpreted collective-bargaining agreement's "Act of God" provision as not encompassing state governor's orders closing certain businesses during COVID-19 pandemic); BNSF R.R. Co. v. Alston Transp., Inc., 777 F.3d 785, 790-91 (5th Cir. 2015) (vacating district court's vacatur of arbitration award and remanding with instructions to reinstate award; citations omitted).

40

Trademark licensing by UT Austin: For example: "Texas football took in $32 million in royalties, licensing and sponsorships during the 2017-18 athletic year, according to the most recent audited data." Brian Davis, Texas athletics signs new 12-year, $96 million deal with Collegiate Licensing Company (HookEm.com 2019) (a site maintained by the Austin American-Statesman newspaper). The UT Austin trademark license agreement form referenced here can be found at https://tinyurl.com/UTTrademarkLicense. DCT note: I received both my undergraduate- and law degrees from UT Austin — and I surmise (but intentionally haven't tried to confirm) that the principal author(s) of the license agreement form were some of my former law partners in Arnold, White & Durkee's Austin office, who, back in the day, did pretty much all of UT's trademark work as far as I know.

41

Here's some possible language to limit who's authorized to sign statement-of-work change orders:

A written change order must be signed on behalf of [specify party name] by [describe, e.g., an officer of that party at the vice-president level or higher].

Only an authorized procurement representative of Customer may agree to a change order.

(This borrows a concept from section 17 of a Honeywell purchase-order form archived at https://perma.cc/84BS-KYXB.)

or:

Only an authorized fulfillment representative of the Vendor may agree to a change order.

Such override language is sometimes seen in boilerplate forms. For example, a car dealership might well ask its customers to sign a contract that explicitly states that the sales person doesn't have authority to offer a better warranty. (That's another case of trying to avoid future "he said, she said" disputes about what was allegedly promised.)

42

Emails have been held to establish binding contracts in numerous cases, such as: settlement of a state-tax dispute: see Hohl Motorsports, Inc. v. Nevada Dept. of Taxation, 563 P.3d 306 (Nev. 2025) (reversing and remanding petition for judicial review of tax determination; unpublished) (the P.3d citation is to the two-word order reversing and remanding; the link is to the court's opinion); the sale of real property: see Perkins v. Royo, No. C080748, slip op. (Cal. App.—3d Dist. Mar. 6, 2018) (affirming judgment on jury verdict) (unpublished); the sale of goods: see, e.g., J.D. Fields & Co., Inc. v. Shoring Engineers, 391 F. Supp. 3d 698, 703-04 (S.D. Tex. 2019) (denying motion to dismiss for lack of personal jurisdiction; emails — including one with a signed sale quotation — established a contract for sale of steel piping that incorporated general terms & conditions containing enforceable mandatory forum-selection clause); an agreement to design and produce materials for a construction project in Saudi Arabia: see Gage Corp., Int'l v. Tamareed Co., 2018 WI App 71 (2018) (per curiam, affirming judgment on jury verdict; unpublished); a sale of 88 rail freight cars: see APB Realty, Inc. v. Georgia-Pacific LLC, 889 F.3d 26 (1st Cir. 2018) (vacating dismissal; complaint stated a claim for breach of contract formed by email); a broker's commission for a real-estate transaction: see Newmark & Co. Real Estate Inc. v. 2615 E. 17 St. Realty LLC, 80 A.D.3d 476,  477-78, 914 N.Y.S.2d 162 (N.Y. App. 2011); an employment agreement including nine months' severance pay in case of termination — here, though, the court said: "While the series of emails does not qualify as a signed writing, under the Winston factors, they form a binding contract" because "[t]he emails demonstrate a 'meeting of the minds' on essential terms" and under New York law "[a] contract does not need to be signed to be binding on the parties." Nusbaum v. E-Lo Sportswear LLC, No. 17-cv-3646 (KBF), slip op. at 9 (emphasis added) (S.D.N.Y. Dec. 1, 2017) (granting former employee's motion for summary judgment); a compromise of a past-due bill for legal fees: see Preston Law Firm v. Mariner Health Care Management, 622 F.3d 384 (5th Cir. 2010) (reversing district court; emails created binding compromise); settlement of a lawsuit: see, e.g., Dharia v. Marriott Hotel Services, Inc., No. CV 18-00008 HG-WRP, slip op. (D. Haw. Jun. 28, 2019) (enforcing email agreement to mediator's settlement proposal); Jarvis v. BMW of North America, LLC, No. 2:14-cv-654-FtM-29CM, slip op. (M.D. Fla. 2016) (granting motion to enforce settlement agreement; citing Florida and 11th Cir. cases); JBB Investment Partners Ltd. v. Fair, No. A152877, slip op. (Cal. App.—1st Dist. Jun. 4, 2019) (affirming grant of motion to enforce settlement agreement and imposing sanctions for frivolous appeal) (unpublished); Martello v. Buck, No. B285001, slip op. (Cal. App. 2d Dist. Mar. 1, 2019) (affirming dismissal of lawsuit pursuant to settlement agreement reached by email); Amar Plaza, Inc. v. Rampart Properties, Inc. , No. B254564, slip op. (Cal. App.—2d Div. Feb. 29, 2016) (granting motion to dismiss appeal; emails established that parties had reached binding settlement agreement) (unpublished); Forcelli v. Gelco Corp., 109 A.D.3d 244, 72 N.Y.S.2d 570 (N.Y. App. Div. 2013); Williamson v. Delsener, 59 A.D.3d 291, 874 N.Y.S.2d 41 (N.Y. App. 2009) (enforcing settlement agreement).

43

On his blog, IACCM founder and president Tim Cummins told of an IACCM member whose company saved hours of negotiating time — up to a day and a half per contract — by moving the definitions section from the front of its contract form to an appendix at the back of the document. He recounted that "by the time the parties reached 'Definitions', they were already comfortable with the substance of the agreement and had a shared context for the definitions. So effort was saved and substantive issues were resolved." Tim Cummins, Change does not have to be complicated (July 21, 2014).