Common Draft: Pretty-Fair Contract Terms (unfinished draft)
Build trust, not traps: Savvy, respectful protocols for resilient business dealings. Annotated and explained.
By Dell C. "D.C." Toedt III, member of the State Bars of Texas and California; professor of practice, University of Houston Law Center (About me)
TO NAVIGATE, click (repeatedly) on the headings at left.
This book presents a study of collaborative business practices, distilled from court-watching and client experience into sensible, standardized clauses. (This is an interim working draft, still being edited. This Web page was generated Apr. 24, 2025 05:52 Houston time.
Cooperative clients and their lawyers could get deals done sooner by considering using selected Common Draft clauses for their contracts.
The main clauses are designed so that many parties could agree to them even if the parties swapped roles, as in the Freaky Friday movies — which has sometimes happened.
Law students:
This book provides nearly all of the readings for the author's Contract Drafting course at the University of Houston Law Center.
Lawyers:
Feel free to draw from the Common Draft clauses in your client work, or use them as a foundation for your internal form library. Consider whether you could use just an agreed term sheet as "the contract," incorporating selected Common Draft clauses clauses by reference.
Parties:
Ask your lawyers about speeding up your negotiations by having a short business term sheet "be" the contract, skipping the conventional legalese.
With:
Clear explanations — to help students learn how business works
Case studies: Courtroom tales of contract "fails" (some of them epic)
Curated links to law firms' online client memos
Tips for drafters, to help future readers do their their jobs
A "Resilience Rider" (to come), with special jerk-detector clauses
IMPORTANT NOTE to the reader: Don't rely on this book as a substitute for legal advice from a licensed attorney. It's provided AS IS, WITHALL FAULTS. Your author is a lawyer, but your reading or using this book doesn't make me your lawyer.
Written agreements protect all stakeholders when business ventures turn sour.Bich v. WW3 LLC, No. 24-1627. slip op. at 15 (7th Cir. Mar. 10, 2025) (affirming summary judgment: emails and draft agreements showed at most an agreement to agree and did not rise to the level of written evidence of a land conveyance sufficient to satisfy the statute of frauds).
This (draft) book is a work in progress; it's a textbook for your author's Contract Drafting course, and some lawyers use it as a resource.
This book assumes at least some familiarity with basic contract law, of the kind one hopes that lawyers and upper-division law students will remember at least dimly from their 1L Contracts course.
This book's clauses, options, and notes provide succinct lessons from real-life contracts and "deal crashes," i.e., court cases. They show fair-dealing approaches that can help parties: • get business done together; • keep their contracts out of court; • demonstrate their trustworthiness (while guarding against the unscrupulous); and • build resilient commercial relationships —all while getting to signature sooner.
Students: See the semester's [BROKEN LINK: rdg-list] ([BROKEN LINK: rdg-list]), with links, which is arranged week-by-week. The specific readings are arranged alphabetically by topic, to speed up dictionary-like lookups in the future.
1.2. "But we've never done it that way!"
In college, I had a full-ride ROTC scholarship from the U.S. Navy, so I owed the Navy several years of active-duty service. I served my payback time as a nuclear-trained surface warfare officer (the Rickover program), with three years of sea duty aboard the aircraft carrrier USS Enterprise.
The head of the reactor department was one of the smartest people I've ever known. On the reactor-department office bulletin board, he posted a list of Great Naval Quotes that he did not want his people to use. If memory serves:
Item 1 on that list was: "But we've never done it that way!"
And item 2: "But we've always done it that way!"
The department head's point: Past practice is no substitute for thinking — about the mission; the specific goals; and how best to accomplish them.
This book tries to take a fresh look at how lawyers and their clients get contracts to signature:
It draws lessons from hundreds of reported court cases that involved "deal crashes," i.e., contracts that went awry for the parties.
It's also informed by my own experience as a partner in a BigLaw litigation law firm, and then as the vice president and general counsel of a publicly-traded, medium-sized software company, which (as outside counsel) I'd helped the founder to start and grow.
In this book, we'll examine court-savvy ways to help cooperative, fair-minded parties to get contracts drafted, reviewed, negotiated, and signed — faster.
1.3. Creative Commons distribution license
This document may be reproduced and/or distributed under the Creative Commons BY NC SA license 4.0: Attribution required; noncommercial only; share any revisions in the same way. See the CC license for details.
In addition: The Common Draft clauses alone may be distributed on a commercial basis under the Creative Commons BY ND license 4.0. (This doesn't include the notes and comments.)
Document-assembly vendors: Feel free to contact me about other arrangements for distribution of clauses and notes together on a commercial basis.
1.4. About the author
I’m Dell Charles “D. C.” Toedt III; I'm a practicing attorney in Houston and a professor of practice at the University of Houston Law Center. I’m licensed to practice law in Texas and California, and am registered in the U.S. Patent and Trademark Office.
My German-origin last name is pronouced "Tate," in the same way as former House speaker John Boehner ("BAY-ner"). I'll answer to either "Dell" or "D.C." — family and friends have called me the latter since I was born (because of my Roman numeral).
I was formerly a partner and member of the management committee at Arnold, White & Durkee, a 150-lawyer intellectual-property boutique litigation firm, one of the largest such firms in the United States, with offices in six different cities with significant tech industries.
I left AW&D 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 founder to start the company. I served there until the company’s successful “exit” when we were acquired by Symantec Corporation, the world leader in our field.
I’ve been active in bar-association work throughout my career; I also work pro bono with certain nonprofit organizations.
In between college and law school, I did my ROTC scholarship payback time as a U.S. Navy nuclear engineering officer (the Rickover program) and surface warfare officer, including three years of sea duty, with two overseas deployments, aboard the nuclear-powered aircraft carrier USS Enterprise.
My undergraduate degree (in math, with high honors) and law degree (law review) are both from the University of Texas at Austin.
If this Clause is agreed to, it will apply when the Contract allows a party (the "Biller") to accelerate the due date(s) of future payment(s) by another party (the "Payer").
Comment
Lenders, landlords, and other creditors will sometimes want the right to "accelerate" — that is, move up the due date of — a payer's future payments if the payer breaches its contractual obligation(s). This Clause spells out a typical scenario under which a "Biller" might want to accelerate a "Payer's" payment obligations, for example for uncured material breach.
As one possible example, the Biller and Payer might be a bank that has made a loan to a borrower.
2.1.2. Gap-filler prerequisite: Uncured material breach
If the Contract does not specify when the Biller may accelerate, then the Biller may do so only if:
the Payer has materially breached one or more provisions of the Contract that benefit the Biller; and
the Payer did not cure all such such breaches before the end of the cure period (if any) specified by the Contract after notice of breach from the Biller.
Benefiting the Biller: Conceivably a multi-party agreement would obligate the Payer: (i) to pay the Biller, and (ii) to take other action benefiting a third party but not the Biller. In the latter situation, we wouldn't expect the Biller to be able to accelerate the Payer's payment obligations.
2.1.3. Specific notice of acceleration is required.
To accelerate, the Biller must give the Payer notice that clearly states the following:
which of the Payer's payment obligation(s) are being accelerated — with all such obligations being one possibility if warranted by the facts and the Contract terms; and
the effective date of the acceleration.
The acceleration notice may be included in a notice of breach, but only if the acceleration notice is express and conspicuous.
Comment
When a Biller wants to accelerate a Payer's future payment obligation, the Biller will likely be required by law to give a clear notice to the Payer.
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." See 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).
2.1.4. A right to accelerate expires three months after it arises.
For each particular occasion for which the Contract gives the Biller the right to accelerate: That right will expire — for that occasion only — if the Biller's notice of acceleration has not become effective on or before the stated time after the date on which the Biller first became entitled to accelerate for that payment failure.
Comment
A. Possible override: "The Biller may send its notice of acceleration any time after the payment failure in question; there is no deadline for the Biller to do so."
B. Rationale: This Clause imposes an acceleration deadline because it usually wouldn't be fair for a Payer to have to live forever under a Sword of Damocles because it failed to make a payment. Moreover, if the Biller doesn't accelerate before the stated deadline, then the Payer's payment failure likely didn't harm Biller that much.
C. Wording choice: Expiration of the Biller's acceleration right for one particular occasion wouldn't affect any right that the Biller might have to accelerate on other occasions (if any).
A. The Payer wouldn't have to immediately pay amount(s) that the Payer could show were not properly subject to being accelerated.
B. Acceleration wouldn't affect the parties' other rights, remedies, and obligations under the Contract (unless the Contract said otherwise, of course). Here some examples of other rights and remedies that wouldn't be affected by an acceleration of payment obligations under this Clause:
any remaining right that the Payer might have to cure the payment failure in question;
the Biller's other available remedies for a payment failure — such as, for example, suing the Payer for the unpaid amount(s) and/or foreclosing on security interests in collateral (if any);
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).
2.1.5.2. For Billers: Pro tips for acceleration notices
Billers: Consider the following to reduce the chance of disputes:
1. It's best if your notice of acceleration states just which payment due date(s) are being moved up (or would be moved up if payment is not made); and – the new due date(s).
2. It might also be helpful if the notice of acceleration explained, in reasonable detail, why the payment due date(s) in question are being accelerated.
3. You might want to include the notice of acceleration as part of a notice of payment failure — if you do that, then the part of the notice that mentions acceleration will preferably be conspicuous.
4. Caution: Be very clear about whether acceleration is or isn't happening, so that the parties will know whether or not the notice started the clock running on the statute of limitations for foreclosure on collateral. Example: In a 2021 decision, New York's highest court addressed a lender's warning letter to a debtor.
The warning letter said, in effect "you're in default, and we might accelerate if you don't pay up."
The court held that the letter did not satisfy the requirement of an "unequivocal overt act" to accelerate — and thus did not start the clock running on the lender's deadline, under the statute of limitations, to invoke remedies such as foreclosure. The court explained:
Noteholders should be free to accurately inform borrowers of their default, the steps required for a cure and the practical consequences if the borrower fails to act, without running the risk of being deemed to have taken the drastic step of accelerating the loan [and starting the clock running on the statute of limitations].
Even in the event of a continuing default, default notices provide an opportunity for pre-acceleration negotiation---giving both parties the breathing room to discuss loan modification or otherwise devise a plan to help the borrower achieve payment currency, without diminishing the noteholder's time to commence an action to foreclose on the real property, which should be a last resort.
(But the lender "lost" anyway, because it had to litigate the matter.)
5. While we're discussing limitation periods: A Texas statute, Tex. Civ. Prac. & Rem. Code § 16.038, 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 …." This was explained by the Texas supreme court in a 2024 decision. See Moore v. Wells Fargo Bank, N.A., 685 S.W.3d 843 (Tex. 2024); 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).
2.1.5.3. Appendix: Other forms of acceleration clause
Some acceleration provisions go into much more detail than is set out in this Clause. See, for example, this long acceleration clause in a loan agreement: It provides a "laundry list" of 13 specific events that can trigger the bank's right to accelerate:
The Bank has the right to immediately cease or reduce the credit line issued to the Borrower, or shorten the loan period, or deem all principal and interest due, if one of the following occurs in relation to the debts owed by the Borrower to the Bank:
(1) When the Borrower fails to repay the debt or to amortize principal in accordance with its agreements, or refuse to honor or make payments when due for any of its debts to the Bank or to any financial institution;
(2) When applying for settlement under the bankruptcy law, voluntary or involuntary bankruptcy, voluntary or involuntary restructuring of the company or being refused by the Taiwan clearing house, closing of business or liquidating debts;
(3) When failing to provide guarantee as originally agreed;
(4) Upon the death of the Borrower and the heir disclaims inheritance;
(5) When a criminal sentence is issued and the majority of assets have been confiscated;
(6) When the Borrower, the Guarantor, the representative of the Borrower or the Guarantor, actual beneficiary, or those exercising control over the Borrower or the Guarantor is found to be subject to economic sanctions, or be deemed or investigated terrorist or organization by foreign governmental or international anti-money laundering organization, or is found to be on the list of sanctions announced by the Ministry of Justice of the Republic of China;
(7) When the Borrower fails to pay for the interest of any debt owed to the Bank or any financial institution;
(8) When any collateral are sealed or lost or reduced in value, or due to the deteriorated financial status of the issuing company of the collateral, situations involving insufficient security, poor credit of the Guarantor or termination of guarantee, and failure to replace the collateral or failure of the Guarantor to repay part of principal after being requested by the Bank to do so;
(9) In relation to the debt owed by the Borrower, when the actual use of funds differs from the purpose approved by the Bank or the business, credit, assets have adverse changes that may detrimentally affect the credit claim of the Bank;
(10) When subject to compulsory execution, provisional attachment, provisional injunction or other preservation, exposing the Bank to the risk of not being able to be repaid;
(11) When the Borrower is found to be dishonest or withholding information or conducting other acts not in good faith in its statements of facts or in its provision of documents during its correspondence with the Bank;
(12) When the Borrower or the Guarantor do not cooperate with the inspection, refuse to provide information related to the actual beneficiary of the Borrower or the Guarantor or the person exercising control, or refuse to cooperate in explaining the actual nature and purpose of the transaction or the source of funds;
(13) When the Borrower fails to comply with the commitment to maintain certain standards of financial status during the loan period, or other covenants or undertakings stated in the transaction documents with the Bank.
For situations stipulated in the clauses (1)–(6) above, the Bank does not need to give prior notice or provide a grace period for remedying the situation; for situations stipulated in clauses (7)–(13) above, the Bank shall give notice or provide a grace period for remedying the situation.
(Emphasis added.)
On the other hand, an example of a more-streamlined acceleration clause can be found in another loan agreement; that clause states, in its entirety: "If any payment obligation under this Note is not paid when due, the remaining unpaid principal balance and any accrued interest shall become due immediately at the option of the Lender."
If agreed to, this Clause will apply in any case where both of the following are true:
the Contract contemplates that one party (the "Biller") can expect payment from another party (the "Payer") for goods, services, or something else; and
the Contract also provides that the Payer may pay at a particular time, for example, net 30 days.
Comment
A. As a typical example: A customer might prove to be a slow payer — see 2.4.9.3 for some famous examples — and at some point the supplier might say, Basta! (Italian for Enough!). This Clause sets out a protocol for the supplier to demand payment in advance for future orders.
For good reason, the Biller may require payment in advance instead of whatever payment terms were contemplated in the Contract.
Comment
A. It might not be a profitable use of drafters' and clients' time to try to define the term good reason in the Contract — other than perhaps including some safe-harbor examples stating that Particular Thing‑X is deemed good reason. For example:
A dispute about advance payment might never arise, so deferring discussion of the term can help the parties to get the Contract signed more quickly; and
This Clause already provides for escalation of disputes, following the rule, 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.
B. But see 2.2.5.1 for discussion of some possible specific cases that could constitute "good reason" for demanding advance payment.
2.2.3. The Biller must give reasonable advance warning
To require payment in advance, the Biller must so advise the Payer a reasonable time in advance — otherwise, any previously-agreed and still-effective payment arrangements will continue in effect.
Comment
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."
2.2.4. The parties are to escalate disputes about such warnings.
If the parties disagree about what would constitute good reason and/or reasonable times for advance-payment warnings under this Clause, then at either party's request, the parties will escalate the dispute:
at either party's further request: to a neutral advisor as provided in Clause 6.4.
Comment
This Clause requires escalation of disputes about advance payment only if a party asks. That's because, as a practical matter, the Biller would hold some high cards: the Biller presumably would simply refuse to do whatever the Payer was asking for unless the Payer complied with the Biller's new advance-payment requirement.
2.2.5. Additional notes (not part of this Clause)
2.2.5.1. Some possible examples of "good reason"
In appropriate circumstances, "good reason" for demanding advance payment could include, for example:
The Payer was late more than once in making payments required in connection with the Contract.
The Payer was significantly late with one or more such required payments — obviously the phrase "significantly late" is open to interpretation and thus to dispute; still, including the phrase gives the Biller some room to try to protect itself from game-playing by the Payer.
The Payer is placing an unusually-large order.
The Biller has other good reason to require payment in advance.
2.2.5.2. Caution to Billers: Would this "poke the bear"?
So as not to delay getting to signature, a drafter representing a supplier should think about whether not to include this Clause in a contract for a customer. That's because:
The law might already permit the supplier 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 at Clause 7.33.4.4 and its commentary); and
Raising the issue with the customer might "poke the bear" (see 30.12), i.e., it could remind the customer's contract negotiator to insist on editing the draft contract to override what the law says, in a way that might disadvantage the supplier.
When this Clause is agreed to, it presupposes that:
under the Contract, a party (the "Auditing Party") is to pay another party (the "Recordkeeper") in amounts, and/or at times, that are based on information contained in records maintained by the Recordkeeper; and/or
the Contract otherwise clearly specifies the Auditing Party, the Recordkeeper, and the auditable records.
Comment
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 2.3.31.2.)
2.3.2. The Auditing Party may have commercially-reasonable audits done.
When requested by the Auditing Party, the Recordkeeper is to allow commercially-reasonable audits to be conducted, on behalf of the Auditing Party, of "Records" (defined below), in accordance with the procedures in this Clause.
Comment
Tangential to commercially-reasonable audits, see the definition of commercially-reasonable efforts at Clause 7.15.
2.3.3. "Records" definition: Specific things may be audited.
Except as otherwise agreed, for purposes of this Clause the term "Records" refers to records, in any form or storage medium, where all of the following are true:
the records are not subject to an attorney-client privilege or other legal immunity from discovery in litigation; 9.8
the records confirm the Recordkeeper's performance and billing under the Contract;
the records are maintained by (or for, or on behalf of) the Recordkeeper under the Contract. and
Comment
Auditable records could include, for example, documentation of the Recordkeeper's sales, where the Recordkeeper 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.
A sample right-to-audit clause, published by the Association of Certified Fraud Examiners sets out a long "laundry list" of specific types of documents that a party might want to require a contractor to maintain:
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.
2.3.4. Technical-trade-secret materials may be withheld from audit.
If the Recordkeeper so chooses, the Auditing Party will not be entitled to audit records that contain or reveal the Auditing Party's technical trade secrets.
Comment
This might have to be negotiated. 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.
2.3.5. Certain records must be maintained.
The Records maintained by or for the Recordkeeper (and, if applicable, subcontractors of the Recordkeeper) are to include, without limitation, all records sufficient to provide commercially-reasonable documentary support for each of the following, when applicable under the Contract:
labor, materials, and other items delivered to the Auditing Party under the Contract;
amounts billed to the Auditing Party under the Contract;
compliance with specific requirements of the Contract, including but not limited to any reporting requirements, when the Contract states that such compliance may be audited;
the relevant accounting procedures and practices; and
any other clearly-agreed auditable matters.
Comment
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).
2.3.6. Reasonable recordkeeping is required.
The Recordkeeper is to maintain the Records in accordance with commercially-reasonable practices.
Comment
Drafters: Consider also adopting Clause 8.55 (recordkeeping requirements).
2.3.7. Reasonable advance notice is required.
The Auditing Party is to give the Recordkeeper reasonable advance notice of any audit being requested — the intent here is to give the Recordkeeper a chance to collect and sort its records, remedy any inadvertent deficiencies, etc., which will help lower the cost of the audit for all concerned.
Comment
A. Of course, the Recordkeeper could take advantage of advance notice to try to cover up outright fraud. But if the Auditing Party clearly has [BROKEN LINK: inspec-gr] to suspect that something is amiss, then a surprise audit might well qualify as "reasonable" advance notice.
B. "Reasonable advance notice": See Clause 7.41 (reasonable definition).
C. "Good reason": See 8.37.1.1 in Clause 8.37 (inspections).
2.3.8. Audit requests are subject to a three-year cut-off date.
In the absence of clear good reason: 8.37 The Recordkeeper need not allow an audit of a particular Record after the later of the following dates:
the end of any legally-enforceable record-retention period for that Record (if any); and
the end of the specified time following the end of the calendar year in which the substantive content of the Record was most recently revised.
Comment
A. At some point it makes sense for the Recordkeeper not to have to support an audit for old Records. So, this section provides a "sunset" for the audit right for particular Records, on a rolling basis.
B. It's probably pretty typical to require keeping records for a minimum of three years; the calendar-year end allows for easier computation of the relevant date(s).
2.3.9. Audits are allowed only every 12 months.
In the absence of clear good reason, the Recordkeeper need not allow an audit that would start any sooner than the specified time after the end of a previous audit — even of Records that were created or updated in the interim.
Comment
A. In many cases, the Recordkeeper wouldn't want to be supporting constant audits (which would entail costs and disruption for the Recordkeeper). So, let's require a "decent interval" between audits.
B. "Good reason": See 8.37.1.1 in Clause 8.37 (inspections).
2.3.10. The Recordkeeper gets a say in who may serve as auditors.
The Auditing Party is to use only auditors who are reasonably 7.41 acceptable to the Recordkeeper — but the Recordkeeper must provide the Auditing Party with any objections to a proposed auditor within a reasonable time.
Comment
A. Understandably, the Recordkeeper will want to be choosy about who gets to poke around in the Recordkeeper's records.
B. Big Four? Except as discussed below, any Big Four accounting firm would typically be considered a reasonable choice for auditors — but they don't come cheap.
C. Contingent-fee auditors — objectionable? Some recordkeepers would quickly object to an auditor working on a contingent-fee basis. That's because contingent-fee auditors might be tempted to err on the side of "finding" errors. (That could be especially problematic if the auditors' findings were agreed to be binding, and in any case disputes about the auditors' findings likely would be expensive and time-consuming for all concerned.)
D. Danger of in-house auditors? Often, employees of the Auditing Party and its affiliates might not be considered reasonable auditors — but the Recordkeeper 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."
E. Use the Recordkeeper'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."
F. Talk to each other! This is one of those areas where communication can help.
G. "Reasonably acceptable": See Clause 7.41 (reasonable definition).
2.3.11. Auditors must commit to complying with this Clause.
The Auditing Party must obtain a legally-binding commitment from the auditor to comply with the requirements of this Clause indicated as applying to the auditor.
Comment
The Recordkeeper 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 Recordkeeper and not just by the Auditing Party.
2.3.12. The Recordkeeper has the final say on (reasonable) "when and where" of audits.
The Recordkeeper — in consultation with the Auditing Party — may designate reasonable times and places for requested audits, with a view to reducing and/or mitigating the attendant disruption to the Recordkeeper's business.
Comment
Reasonable times and places for an audit would ordinarily include, for example, the location or locations where the Records are kept in the ordinary course of business — to help reduce audit costs and help auditors spot signs of tampering; see, e.g., Hubbs at 4 (2012) —during the regular working hours, at that location, of the party having custody of the records.
(Sometimes, though, the Recordkeeper might legitimately prefer to have the auditor(s) work at a different location, e.g., to avoid disruption to the Recordkeeper's business routine.)
2.3.13. Auditors are to have reasoanble access to Records and personnel.
The Recordkeeper is to arrange for the relevant Records to be made available to the auditor as the Records are kept in the ordinary course of business.
In consultation with the auditors, the Recordkeeper may set reasonable limits on auditors' access to the party's facilities, computers, etc., with a view to balancing protection of the Recordkeeper's legitimate interests in privileged- or confidential information, while still advancing the audit.
Comment
The escalation requirement of section 2.3.28 would kick in if a dispute were to arise here.
2.3.14. Required: Professional cooperation
All involved in an audit are to cooperate in a professional manner with a view to expeditiously getting the audit done.
Comment
One would hope (and expect) that everyone involved in an audit would conduct themselves professionally. But that might not be the case if for some reason the parties are antagonistic towards each other.
2.3.15. The Recordkeeper has specific cooperation obligations.
In cooperating in an audit, the Recordkeeper is to do the following unless clear [BROKEN LINK: inspec-gr] exists to do otherwise:
make reasonable working facilities available to the auditors — including without limitation standard office-type facilities in reasonable locations with normal heating, air conditioning, restroom facilities, etc.;
direct the Recordkeeper's people to provide reasonable cooperation with the auditors, including but not limited to answering reasonable questions asked by the auditors; and
provide the auditor(s) with a reasonable number of copies of requested Records, at no charge, for retention.
Comment
Suitable workspace: It's not unheard of for a hostile recordkeeping party to force auditing-party auditors to work in uncomfortable spaces.
Answering questions: A good business partner wouldn't stonewall the auditors or try to make their jobs more difficult.
2.3.16. After three months, the Recordkeeper can set a cut-off date.
This section will apply if an audit has not been completed within the specified time after the audit's start date, as reasonably reported by the auditor.
The Recordkeeper may give notice to the Auditing Party that the audit must be completed no later than a reasonable deadline clearly stated in that notice.
After that deadline passes, the Recordkeeper may stop allowing the auditor to access the Records and the Recordkeeper's facilities and people.
The same applies to Records, facilities, and people of any Recordkeeper subcontractors (if any).
Comment
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 Recordkeeper might well want to impose a completion deadline. This Option draws on concepts in paragraph 5(i) of the BookBaby terms of service.
2.3.17. Other requirements are incorporated by reference
In addition, in connection with the audit, all involved in the audit are to comply with the following:
2.3.18. Auditors may retain archive copies of Records.
The Recordkeeper is to allow the auditor to retain archive copies of Records in confidence as stated at section 2.3.18.
Comment
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.
2.3.19. Auditors must comply with confidentiality obligations.
Each auditor must preserve in confidence all Recordkeeper information learned in the course of the audit, in the same manner as the auditor must do for confidential information of the auditor's clients under standards for certified public accountants in the United States.
Comment
The Recordkeeper could try to get the auditor to agree to a detailed confidentiality agreement. But that might be an iffy proposition, so this Clause aims to keep it simple — independent accounting firms will usually have at least some ethical confidentiality obligations; see, for example, Rule 1.700 of the Code of Professional Conduct of the American Institute of Certified Public Accountants (2014, updated 2020) or its successor.
2.3.20. The auditor must limit what it discloses to the Auditing Party.
The auditor is not to disclose to the Auditing Party any more information of the Recordkeeper except reporting, in reasonable detail, any noncompliance with the Contract that is revealed by the audit.
Comment
Obviously, the Auditing Party will want to hear, directly from the auditor(s), whether an audit revealed any discrepancies. (Basic fairness dictates that the Recordkeeper also be informed if the auditor(s) conclude that discrepancies exist.)
2.3.21. The Recordkeeper is to receive a copy of the audit report.
The auditor is to promptly provide the Recordkeeper (at no charge) with a complete and accurate copy of the audit report.
If the Auditing Party provides such a copy to the Recordkeeper, then the auditor need do so only if requested by the Recordkeeper.
Comment
The Recordkeeper 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. (See generally the commentary at 11.9.)
The Auditing Party shouldn't object to this, because if litigation were to ensue, then the Recordkeeper'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 Recordkeeper does get such a copy, the earlier that the parties are likely to come to a settlement of the dispute.
2.3.22. Objections to an audit report have a three-month deadline.
If either party wants to object to an audit report, that party must state those objections to the other party in a reasonably-detailed writing within the stated time after receiving a copy of the audit report from the auditor — otherwise, the audit report will be deemed final and binding on all parties except in cases of proven fraud.
Comment
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.
2.3.23. A true-up is to take place after each audit.
The Recordkeeper and Auditing Party are to promptly true-up any discrepancies identified in the audit report.
If the audit revealed underpayment(s) that were the fault of the paying party, then the true-up payment is to include interest on the underpaid amounts, 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.
If interest is charged or paid, then Clause 2.11 will apply.
Comment
H. What's a "true-up"? A true-up is generally the end goal of a (routine) audit if the audit reveals that a party overpaid or underpaid. That is, in business jargon, the term true up means, in effect, to reconcile or balance.
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;
I. What if an underpayment was the biller's fault? It wouldn't be appropriate for a paying party to have to pay interest on an underpayment that was caused by an error by the other party — for example, if a customer underpaid a supplier because the supplier's invoices to the customer had errors that were the supplier's doing.
J. Interest charge on underpayment: In a small way, charging interest on underpayments will help discourage paying parties from "shorting" their payments.
K. What interest rate should apply? Parties might want to negotiate a lower interest rate for true-up underpayments than the maximum legal rate. On the other hand, too-low an interest rate would give a party an incentive (albeit possibly a small one) to cheat.
L. Usury savings clause: See generally the discussion at 2.11.6.2.
2.3.24. A true-up will usually be the exclusive remedy for discrepancies.
A true-up will be the EXCLUSIVE REMEDY for any discrepancies revealed by an audit — except in cases where the audit reveals fraud or material breach.
Comment
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 — in which case a true-up shouldn't be the exclusive remedy because that would create moral hazard, i.e., an incentive to roll the dice because fraud might never be detected. Example: In an Eighth Circuit case, 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).
M. An exclusive-remedy limitation of liability after an audit could benefit, say, a software customer that "inadvertently" used more licensed software than the customer had paid for; the limitation would help protect the customer against a software vendor that diligently enforced its license terms (cough, Oracle). See, e.g., Oracle License and Services Agreement, ¶ O; Barnett (2015).
N. Such a vendor might want to be free also 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 Recordkeeper had used licensed software for more than it had paid for. (See also the related commentary at 2.14.10.16, providing that late payment is not infringement.)
2.3.25. Each party is responsible for its own audit expenses — usually.
Each party is responsible for its own audit expenses except as stated in this Clause.
Comment
In commercial contracts, auditing parties typically pay for their own audits (although that's not always the case). The exceptions below are standard practice.
2.3.26. The expense-shifting threshhold for discrepancies is 5%.
The Recordkeeper will promptly reimburse the Auditing Party, as provided in Clause 2.9, for reasonable fees and expenses paid to the auditor by the Auditing Party if all of the following are true:
the audit revealed a discrepancy in the Recordkeeper's favor;
the discrepancy exceeded the stated percentage — for the entire period being audited, not for some shorter interim period; and
the Recordkeeper was responsible for the discrepancy.
Comment
A. Audit-expense-shifting threshold: 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.
B. Recordkeeper responsibility: Suppose that, for some reason, the Recordkeeper 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 Recordkeeper to have to reimburse the Auditing Party for the Auditing Party's audit expenses.
2.3.27. Expense-shifting could also happen for fraud or material breach.
The Recordkeeper will likewise reimburse the Auditing Party if the audit reveals (i) fraud, or (ii) a material breach, in either case:
on the part of the Recordkeeper; and/or
on the part of one or more of the Recordkeeper's subcontractors, where the subcontractor's fraud or material breach adversely affected the Auditing Party.
Comment
This subdivision doesn't authorize — but neither does it prohibit — the use of subcontractors by the Recordkeeper.
2.3.28. Escalation of audit-related disputes is required
The Recordkeeper and Auditing Party are to escalate, as stated in Clause 6.4, any disagreement about how this Clause should be applied in connection with any proposed audit-related activity.
2.3.29. Option: Reimbursement of Recordkeeper's Expenses
If the Contract adopts this Option, and the Recordkeeper is not required to reimburse the Auditing Party's expenses of an audit under the Contract, then the Auditing Party will reimburse the Recordkeeper — and the subcontractors of the Recordkeeper, if applicable — for 100% of all reasonable expenses actually incurred by them in connection with the audit.
Comment
Audits aren't cost-free for the Recordkeeper; will its expenses be covered? "[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).
2.3.30. Survival of audit-related provisions
After any termination or expiration of the Contract, the audit-related provisions of the Contract will continue in effect, as stated in Clause 5.1 (survival), for matters that were subject to audit before termination or expiration, except as specifically provided otherwise in the Contract.
Comment
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, as happened for example in a First Circuit case involving a company's collective-bargaining agreement ("CBA") with a labor union, where the court held that termination of the CBA had cut off the union's right to audit the company's contributions to various pension funds. (The result might well have been different if the audit provision included a survival clause such as that of this Clause.) See New England Carpenters Central Collection Agency v. Labonte Drywall Co., 795 F.3d 271 (1st Cir. 2015).
2.3.31. Additional notes (not part of this Clause)
2.3.31.1. Appendix: Shorter-form audit clauses
Here's a condensed version of this Clause:
Audits:(a) The Auditing Party may have commercially-reasonable audits conducted, from time to time, by independent outside auditors, of the Recordkeeper's non-privileged books and records documenting the Recordkeeper's performance of its obligations under the Contract. (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 Recordkeeper — in the form in which they are kept in the ordinary course of business — documenting the Recordkeeper's performance of its obligations under the Contract, excluding technical trade secrets as well as materials subject to the attorney-client privilege or other immunity from discovery. (b) The Recordkeeper will provide reasonable cooperation with the auditor(s) — including but not limited to directing the Recordkeeper'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 Recordkeeper must reimburse the Auditing Party for the auditors' reasonable fees and expenses of an audit if that audit reveals a discrepancy, for which the Recordkeeper is responsible, of greater than 5% for the period being audited.
2.3.31.2. Examples of audit rights that paid off
Here are just a couple of 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.)
2.3.31.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;
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."
2.4. Backup Payment Sources Protocol Clause
Motivation: When a party ("Biller") expects to be owed money by another party ("Payer"), the Biller might be concerned whether the 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 Contract.
For that reason, it's not uncommon for a Biller to negotiate for the Payer to put in place some backup-payment arrangements — a.k.a. "payment security" — to shift at least some of the risk of nonpayment onto some third party such as a guarantor (see Clause 2.10) or a bank letter of credit (see 18.1).
When this Clause is agreed to, it will apply whenever requested by a clearly-specified party to the Contract (the "Biller") to another clearly-specified party to the Contract (the "Payer").
2.4.2. The Payer is to make arrangements for backup payment sources.
The Payer is to promptly establish, and continuously maintain in effect, one or more arrangements with one or more backup payment sources (each source, a "Bank") to pay amounts that come due to the Biller under the Contract, in case the Payer does not pay on time.
As between the Payer and the Biller, the Payer is to bear all expenses of establishing and maintaining the backup payment arrangements.
The Payer is not to seek reimbursement of such expenses without prominently pointing out to the Biller's relevant people (e.g., accounts-payable personnel) that the Biller has not agreed to reimburse such expenses.
Comment
A. Subdivision 2: 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, 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, then that expense will factor into Biller's pricing position.
B. Tangentially: 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).
C. Subdivision 3: An unscrupulous Payer might be tempted to ask for reimbursement, in the hope that the Biller's accounts-payable people wouldn't notice the discrepancy and instead would just pay.
2.4.3. The Biller gets reasonable approval rights over the arrangements.
The Payer is to obtain the Biller's prior written approval of:
each Bank; and
each backup payment arrangement with each Bank.
The Biller must not unreasonably withhold, delay, or condition its approval of a Bank, nor of such an arrangement.
Comment
In deciding whether a particular backup-payment arrangement was acceptable, the Biller could reasonably take into account, for example, the following (without limitation):
the financial condition of the individual or organization agreeing to serve as the backup payer (i.e., the Bank);
whether the Bank was in a jurisdiction that would be convenient to the Biller for purposes of enforcing the Biller's right to payment (e.g., U.S. banks only, federally-chartered U.S. banks only, etc.);
the extent to which the arrangement covered:
pro-rata payments required under orders for goods as shipped and/or for services as performed; and
payment of any cancellation- or termination charges under such orders; and
whether the Bank would reimburse the Biller for any Biller refund of a Payer payment in proceedings under bankruptcy- or comparable laws, for example in settlement of a claim for refund of a "preference" payment (see 2.10.4). 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.
2.4.4.The Bank must confirm the arrangement to the Biller.
For each backup-payment arrangement, the Payer is to have the Bank, within a reasonable time, provide the Biller with written confirmation that the agreed arrangement has been established.
Comment
For the reasoning behind this requirement, see 11.9.
2.4.5. The Biller may wait to start work until confirmation.
In the interest of reducing the Biller's contractual risk: The Biller need not incur any burden or expense under the Contract until the Biller has received the confirmation required by section 2.4.4.
Comment
Relatedly, see the requirement of adequate assurance of performance, in UCC § 2-609, which applies by its terms to a sale of goods.
2.4.6. Arrangement modifications might be required.
If the Biller reasonably requests in writing, the Payer is to promptly arrange for reasonable modification of the backup-payment arrangement (and confirmation to the Payer by the Bank).
Comment
A. 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 listed in the Contract (if any) as "safe harbor" reasons for the Biller to request a modification.
B. 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.
C. Pro tip: If the Biller asks for changes to a backup-payment arrangement, the Biller should consider proactively providing the Payer with reasonable detail and perhaps appropriate supporting documentation.
2.4.7. Arrangement disagreements are to be escalated.
At either party's request, the parties will escalate disagreements about the reasonableness requirements of this Clause:
if necessary, to a neutral advisor (see Clause 2.3.1).
Comment
See the commentary at the cited sections.
2.4.8. Option: Backup Payment Failure as Material Breach
If this Option is agreed to in the Contract, then any failure by the Payer to timely provide, maintain, and/or modify, any backup-payment arrangement required by the Contract would be considered a material breach.
Comment
Failure = material breach? 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 7.33. 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.
2.4.9.1. 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 Clause 2.6 (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 18.1 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 Clause 2.10.
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 Clause 24.1.
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).
The surety will usually try to recoup its payment(s) from its insured, that is, from the nonpaying contractor.
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).
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.
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:
to fund a party's performance of its contractual obligations;
to guarantee availability of materials needed for the work (this is known as a supply bond); and/or
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 inTaylor Energy Co. v. United States, 975 F.3d 1303, 1307 (Fed. Cir. 2020), where the court affirmed dismissal of Taylor Energy's complaint, on grounds that it failed to state a legally-cognizable 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 2021 federal-court case in Massachusetts. See Arch Ins. Co. v. Graphic Builders, LLC, 519 F. Supp. 3d 54 (D. Mass. 2021), where the court granted summary judgment that a general contractor was not entitled to collect on subcontractor's performance bond; the decision was affirmed at 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, as suggested in a 2021 article. See Andrew Gibson, Surety Bonds vs. Subcontractor Default Insurance (JDSupra.com 2021).
2.4.9.2. 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 Clause 2.6).
2.4.9.3. Some real-world examples of billers getting "stiffed"
In some deals, a party's prospect of not getting paid can be a non-trivial risk:
Example: During the economic downturn accompanying the COVID-19 pandemic, the prominent retail chain Paper Source loaded up on inventory from its small-business suppliers, ordering unusually-large quantities of merchandise — and then, in effect, tore up the bills by filing for bankruptcy protection. As reported by the Washington Post, "Paper Source ordered more from The Card Bureau in a 60-day period than it had in all of 2020." Shortly afterwards, Paper Source filed for bankruptcy protection — the legal effect of which was to allow Paper Source (mostly) to stiff its suppliers, likely paying them something like pennies on the dollar.1
Example: In the Seventh Circuit's Northbound Group case, the plaintiff company's assets were acquired by a newly-created subsidiary of the party that the plaintiff company had anticipated would be the buyer; that subsidiary turned out to be judgment-proof, but the acquisition agreement evidently didn't provide any kind of backup payment source (see 2.4), such as a guaranty (see 2.10) of the subsidiary's payment obligations. Northbound Group, Inc. v. Norvax, Inc., 795 F.3d 647, 650 (7th Cir. 2015) (cleaned up), affirming5 F. Supp. 3d 956, 972-74 (N.D. Ill. 2013).
(This illustrates the importance of making sure the contract names the correct party or parties, as discussed at discussion at 7.2.4.)
2.4.9.4. One common use: Avoiding construction liens
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.
[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.)
2.4.9.5. How long should backup-payment arrangements be kept?
The Biller might want the Contract to include language along the following lines:
The Payer is to keep each backup-payment arrangement continuously in force for at least six months after the latest to occur of the following:
the last scheduled shipment of applicable ordered goods, if any;
completion of all applicable ordered services, if any;
the Biller's receipt of the final payment covered by the backup-payment arrangement; and
any other events clearly specified in the Contract.
Note that this language requires the Payer to keep the backup-payment arrangements in place even after the Biller has received final payment. That's because conceivably the Payer could file for bankruptcy protection and then demand that the Biller refund the final payment(s) as a "preference payment" (see 10.3.3).
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 the Biller might end up recovering no more than pennies on the dollar in the bankruptcy proceedings — moreover, under U.S. bankruptcy law, the Biller might be forced to refund, as a "preference" (see 10.3.3), some or all of any payment made by the Payer. Consequently, the Biller very much like to be able to demand payment from a backup payment source such as a bnk, 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).
2.5. Consumer Price Index (CPI) Definition
Some contracts include inflation-adjustment clauses that lock in agreed pricing levels for a specified time period — but allowing the supplier 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 2.5.1.1 for other possibilities.
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.
Comment
For convenience and certainty, if the Contract just says (for example) "price increases no greater than CPI," this Clause specifies CPU-U as the gap-filler adjustment index.
As explained in a FAQ page of the Bureau of Labor Statistics (see question 15):
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.
(Extra paragraphing and bullets added.)
2.5.1.2. Could other inflation indexes be better?
There are also other inflation adjustment indexes such as, for example:
CPI-W, Consumer Price Index for Urban Wage Earners and Clerical Workers;
When this Clause is agreed to, the parties are to follow it whenever a party (a "Biller"), or the Biller's agent, receives a deposit under the Contract for the account of another party (the "Payer").
Comment
Caution: This Clause sets out only basic steps for handling deposits that are provided. It's up to the parties and their drafters to negotiate, for example, how many deposits would be needed, in what amounts, and when.
2.6.2. Deposits must be used only as agreed.
The Biller is to see to it that the deposit is used only for clearly agreed purposes.
Comment
A.
This section seeks to roadblock (or, at least, discourage) diversion of deposit funds, such as allegedly happened, for example, with crypto-currency exchange FTX (among countless other examples).
B.
Pro tip: In the Contract, 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.
2.6.3. To what extent are deposits refundable?
[ x ] The Biller is to see to it that any remaining balance of a deposit is refunded to the Payer (or returned, if the deposit is something other than money) when all Clearly-Agreed uses of the deposit have been completed. [ ] Deposits are nonrefundable unless all prerequisites specified in the Contract have been met.
Comment
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.
2.6.4. Will a deposit bear interest?
This section will apply unless the Contract clearly states otherwise.
Monetary deposits will not bear interest.
For non-monetary deposits, the Payer is not entitled to any increase in the deposit that might occur during the time of the deposit.
Comment
A. Section 2: Provisions for interest on deposits will generally be custom-drafted, so they're not included here.
B. Section 2 — special case for lawyers: If you accept deposits from clients, consider whether you'll be required to keep those deposits in special trust accounts, known as IOLTAs.
C. Section 3: 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 is to bear the associated expenses; and (2) who is entitled to possession and/or ownership of any resulting "increase" in the deposit.
– 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 (or on an agreed schedule) provides some such assurance.
– A contractor might want a customer to put up at least some of the necessary working capital, for example to buy materials needed to manufacture contracted-for goods.
– Apartment renters are no doubt familiar with security deposits required by landlords.
– Real-estate purchase contracts often require the buyer to deposit part of the purchase price "into escrow" (concerning which, see generally [BROKEN LINK: escrow-cmt]) as "earnest money"; in certain circumstances, the earnest money might be forfeited if the buyer doesn't close the purchase.
2.6.5.2. IOLTA: Interest On Lawyer Trust Accounts
If 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.)
Generally, a deposit into an IOLTA account does earn interest — but the interest is aggregated and given to charity, not individually to the client that paid the advance deposit. The theory is that any one client's deposit is likely to earn too little in interest to justify the cost of managing it. See generally, e.g., IOLTA Overview (AmericanBar.org, undated).
Trivia: The term "IOLTA account" is redundant, of course. It's the same as, for example, "ATM machine" or "PIN number" or "please RSVP" or "the hoi polloi."
2.7.1. The Payer is entitled to claim any available drawbacks.
As between the Payer and the Biller, the Payer is entitled to seek, and keep, any drawbacks that might be available (if any) for the matter(s) being invoiced by the Biller.
Comment
A. 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).
B.
As between: 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.)
2.7.2. The Biller is to provide copies of its relevant paperwork.
At the Payer's request (and at no additional charge), the Biller is to provide the Payer with originals and/or copies of any documentation reasonably requested by the Payer to help the Payer claim a drawback for the matter being invoiced.
2.7.3. The Payer is to handle applications for drawbacks.
As between the Payer and the Biller, it is the Payer's responsibility to submit and pursue any drawbacks that the Payer wants to claim.
Comment
A. Pro tip: Sometimes it might make more business sense to have the Biller submit and pursue drawback claims on behalf of the Payer.
B. Concerning "As between the Payer and the Biller," see 9.6.
2.7.4. The Payer is to bear any drawbacks-related expenses.
As between the Payer and the Biller, the Payer is to bear all expenses of seeking drawbacks.
Comment
Concerning "As between the Payer and the Biller," see 9.6.
2.7.5. Drawback-related disagreements are to be escalated.
If any party asks, all parties are to escalate any disagreement about the reasonableness of a Payer request for documentation in accordance with Clause 6.4.
Comment
See the commentary at the cited clause.
2.7.6. The Biller makes no guarantees about drawbacks.
Unless the Contract explicitly says so, the Biller makes no commitment that any drawback(s) will be available for the matter(s) being invoiced.
Comment
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.
2.8. 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 6.3.7.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.
– "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 8.16.4.
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 7.2.4.
– 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).
2.9. Expense Reimbursement Protocol Clause
Some contracts — by no means all — call for one party to reimburse another party's expenses incurred; this Clause provides a workable balance between the parties' respective desires.
When the Contract adopts this Clause, a party clearly identified in the Contract (the "Payer") is to reimburse another clearly-identified party the "Biller") as stated in this Clause.
Comment
Note: This Clause doesn't itself require reimbursement of expenses; any such requirement would be included in the Contract.
2.9.2. Only authorized, actually-incurred expenses are to be submitted.
The Biller is not to ask the Payer for reimbursement of an expense under the Contract — at least not without first getting the Payer's specific approval — if the Biller reasonably should know that either of the following is true:
the expense is not one that is authorized for reimbursement under the Contract; and/or
the Biller has not yet actually incurred the expense on a nonrefundable basis (that is, the Biller is not to ask for advance reimbursement).
Comment
A.
No asking for unauthorized reimbursement: This section doesn't merely say that the Payer need not pay ineligible reimbursement claims, because such limited language could tempt a fraudster Biller to roll the dice and knowingly submit ineligible or unreasonable expenses, in the hope that the Payer's accounts-payable people might unwittingly pay the improper charges. See generally Tiffany Couch, Skimming and scamming: Detecting and preventing expense reimbursement fraud (AccountingToday.com 2018).
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. (On this general subject, see Clause 8.23.)
B. Incurred expenses only: 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).
2.9.3. Expense markups must be expressly agreed to.
The Biller is not to mark up expenses for reimbursement unless the Contract expressly allows the Biller to do so (e.g., in a cost-plus contract).
Comment
When a contract is to be cost-plus, the contractor will generally be quite clear about it in the contract.
2.9.4. Receipts are required — originals, if requested.
This section will apply unless the Payer has clearly indicated that receipts are not required for particular amounts and/or categories of expenses.
The Payer need not reimburse an expense if the Biller has not provided the Payer:
with originals of receipts, if the Payer has asked for originals; or
otherwise, with complete and accurate copies of receipts, with or without a request.
Comment
A. To help guard against financial fraud, companies' internal controls typically require that receipts accompany all requests for reimbursement.
B. Section 1: For "small" expenses, the Payer might not want to bother with receipts, original or otherwise — 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). >
2.9.5. The Payer may impose expense-reimbursement policies
The Payer need not reimburse submitted expenses that do not comply with one or more particular requirements of the Payer's written reimbursement policy — but the Payer is required to reimburse if one or both of the following is true:
the requirement in question is not commercially reasonable, considering the nature of the expense and its role in relation to the Contract; and/or
(for any nonrefundable expense:) the Payer did not provide the Biller with the requirement a reasonable time before the Biller became obligated to pay the expense.
Comment
A. 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.
B. Pro tip: The Biller should consider consulting with the Payer if the Biller can't or won't follow a Payer reimbursement policy for a particular expense.
2.9.6.1. Pro tip for Billers: Pre-clear certain expenses with the Payer?
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 Contract 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.
2.9.6.2. Would paying an improperly-billed expense be a waiver?
Suppose that a Biller submits a request for reimbursement that doesn't comply with this Clause, 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" (see Clause 2.14.5) 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 Contract, then Payer's action is not a waiver by Payer of that contractual requirement unless the circumstances unmistakably indicate otherwise.
2.10. Guaranty Protocol Clause
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. This Clause offers a streamlined, boiled-down version of some of the most important features (at least in my view) of many "in the wild" guaranties.
2.10.1. If this Clause is agreed to, when would it apply?
If this Clause agreed to, it presupposes that one or more individuals or organizations clearly identified in the Contract — each, a "Guarantor" or "you" — guarantees 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."
Comment
This Clause doesn't itself create a guaranty require the Payer to provide a deposit; that'd be done in the Contract.
2.10.2. The Creditor must ask for payment in writing.
The Guarantor need not pay an amount under the Guaranty until the Creditor asks for payment in writing (the "payment request").
If the payment request is made by notice (see Clause 6.9), then the request is considered to have been received by the Guarantor no later than when the notice becomes effective.
The Creditor is free to have the payment request sent 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).
Comment
A. This makes sense: A Guarantor can't reasonably be expected to pay up without being asked, and any such request should be in writing for obvious reasons.
B. Pro tip: Preferably, the payment demand should be by notice (see Clause 6.9), to help avoid future disputes about whether and when the Guarantor should be deemed to have received the demand.
2.10.3. The Creditor's payment request must provide reasonable details.
The Creditor's payment request must include (at least) the following information:
reasonable details about the Debtor's failure to pay, including at least the amount due; the due date; and any applicable cure period;
details about any corresponding, then-current Debt-collection expenses for which the Creditor wants to be reimbursed;
itemized amount(s) that the Creditor wants the Guarantor to pay; and
reasonable supporting documentation.
Comment
The details mentioned in the text 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.
2.10.4. The Guarantor's payment is due in five business days.
The Guarantor is to pay the Creditor the entire amount(s) described in the Creditor's payment request — assuming no deal-breaker problems with the request — no later than the stated time after the Guarantor receives the request.
2.10.5. The Creditor need not sign the Guaranty.
The Guarantor's payment is due as stated in this Clause: (i) whether or not the Creditor accepted and/or signed the Guaranty, and (ii) whether or not the Guarantor was notified that this had happened.
Comment
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).
2.10.6. The Creditor may look to the Guarantor independently.
The Guarantor's payment is due as stated in this Clause whether or not the Creditor tried (successfully or otherwise) to collect the past-due payment from the Debtor, by filing a lawsuit or otherwise — that is, the Guaranty is "unconditional" and is a guaranty of payment, not of collection;
Comment
A. 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).
B. 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.
2.10.7. The Debtor's bankruptcy would not excuse the Guarantor.
The Guarantor's payment is due as stated in this Clause even if the Debtor sought, or successfully obtained, relief under bankruptcy law, or was made the subject of an involuntary proceeding in bankruptcy; and
Comment
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 10.3.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.
2.10.8. A Debtor's subordination agreement would make no difference.
The Guarantor's payment is due as stated in this Clause even if the Debtor entered into an agreement with a third party that subordinated the Debt — that is, the third-party agreement required the Debtor to fulfill specified prerequisites, for example by paying the third party before the Debtor paid some or all of the Debt.
Comment
This subordination-defeating provision has in mind a Seventh Circuit decision in which (long story short) the debtor had entered into a subordination agreement that prohibited the debtor from paying the debt, and as a result, the guarantor was not yet liable. See Indigo Old Corp., Inc. v. Guido, 29 F.4th 856 (7th Cir. 2022) (Easterbrook, J.), affirmingNo. 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)).
2.10.9. The Guarantor must also reimburse certain Creditor payments.
The Guarantor must also reimburse the Creditor for each of the following:
any refund of previous payments that the Creditor credited to the Debtor — for example, 7.27 because of alleged "preferences" in bankruptcy 10.3.3 or counterfeited payment checks; 2.14.10.6
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
any other payments, covered by the Guaranty, that are made by the Creditor.
For emphasis: The Guarantor must reimburse the amounts stated in subdivision 1 regardless whether the Creditor:
was legally compelled to make the refund- or other payment in question;
paid that refund, or made that other payment, to settle a claim for refund or -payment; and/or
paid the refund, or made the other payment, to the Debtor itself and/or to the Debtor's estate in bankruptcy or other successor.
2.10.10. The Guarantor certifies its creditworthiness information.
By signing the Guaranty, the Guarantor represents and warrants to the Creditor that any creditworthiness information provided to the Creditor by the Guarantor (directly or indirectly) is complete, up to date, and accurate, in all material respects.
Comment
A. 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.)
B. 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.
2.10.11. There is no general Guarantor liability under the Contract.
For emphasis: The Guarantor's liability under the Contract is limited to that stated for a guarantor unless the Guarantor signs the Contract in a manner that clearly indicates that the Guarantor is a party to the Contract in some other capacity.
2.10.12. Each of multiple Guarantors is fully liable under the Guaranty.
This section applies if multiple individuals and/or organizations are clearly identified as "Guarantors."
Each Guarantor is jointly and severally responsible for paying the Creditor under the Guaranty.
Each Guarantor has the right of contribution from each other Guarantor.
Each Guarantor is entitled to the rights, and subject to the obligations, of a solo Guarantor under the Contract.
Comment
A. When a contract has multiple Guarantors, the Creditor will likely want to be able to proceed against any and all of multiple Guarantors for the full amount of the unpaid debt; see generally joint and several liability (law.cornell.edu).
B. Pro tip: If you're one of multiple Guarantors and will be guaranteeing multiple Debts, it's a really good idea for you to be clear about the extent to which Guarantors are liable for which obligations.
For example: When your author's 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.
C. Section 3: The "right of contribution" means that if one of several Guarantors makes a payment under the Guaranty, then the paying Guarantor is entitled to be reimbursed by all other Guarantors for their pro-rata shares of the payment (generally, equal shares if not otherwise agreed). See generally contribution (law.cornell.edu).
2.10.13. Any Guarantor liability limits must be clearly agreed.
The Guarantor's liability under the Guaranty extends to the full amount specified in this Clause unless the Contract clearly provides for a cap on that liability.
Comment
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. Sepinuck 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.
2.10.14. Modification of the Debt would (usually) cancel the Guaranty.
[ x ] 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.
[ ] The Guarantor's liability under the Guaranty will remain in full force if the Debt is modified.
Comment
A. The above "default option" 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." Some creditors' guaranty documents "write around" this general rule. 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).
B. Just imagine how the second option in the text could create problems for the Guarantor: The Debtor and Creditor agree to a modification that leaves the Guarantor on the hook for more than the Guarantor signed up for.
2.10.15. Would the Guarantor ever be excused from payment?
[ x ] 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 the Guarantor may assert those defenses — but no others — in any action to enforce the Guaranty.
[ ] By agreeing to the Guaranty, the Guarantor WAIVES each of the following:
any claim or defense 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;
any claim or defense that the Guarantor might have pertaining to any part of the Debt, other than the defense of discharge of the Debt by full performance;
any setoff available to the Debtor or any other such person liable — whether or not on account of a related transaction;
any defense arising out of an election of remedies by the Creditor 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
any other circumstance that might otherwise absolve the Guarantor of any obligation under the Guaranty.
Comment
A. 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.
B. 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. (Some examples (and counterexamples) are discussed in an appendix at 2.10.16.6.)
C. California provides statutory language that can be used for waivers of defenses to a debt; see Cal. Civ. Code § 2856.
2.10.16.1. Caution: An "absolute" guaranty limits the Guarantor's defenses
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 section 2.10.15).
2.10.16.2. Caution: Whose obligations are guaranteed?
A guaranty should be clear about just whose obligations are being guaranteed, because a creditor's aggressive position on this issue could lead to litigation. For an especially-aggressive case of a creditor suing on a guaranty to try to cover an unrelated debt, see a 2013 Fifth Circuit case. See McLane Foodservice, Inc. v. Table Rock Restaurants, LLC, 736 F.3d 375 (5th Cir. 2013).
2.10.16.3. 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).
2.10.16.4. Spelling: Guarantee? Guaranty?
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).
2.10.16.5. Appendix: Additional reading (optional for students)
Example: The Fifth Circuit peremptorily dismissed a guarantor's attempt to assert equitable defenses, because the guarantor "clearly waived any right to interpose defenses that belonged to [the debtor]." N. Am. Svgs. Bk. v. Nelson, 103 F.4th 1088, 1095 (5th Cir. 2024) (affirming summary judgment in favor of lender).
Example:The CEO of a bankrupt company 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).
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).
2.11. Interest Charges Clause
Most people are familiar with interest charges. Some might not know that there are significant legal issues involved.
When this Clause is agreed to, it allows — and prescribes the procedure for — one party (the "Biller") to charge interest to another party (the "Payer") on past-due amount owed by the Payer.
2.11.2. Any interest charges are to be itemized in invoices.
The Biller is to include the interest charge (clearly itemized and labeled as such) in an invoice to the Payer.
The Payer is to pay any lawful, invoiced interest as stated in Clause 2.12 (payment terms).
2.11.3. The maximum permitted rate is 5% p.a. simple interest.
The Biller is not to charge the Payer more than simple interest or the maximum rate allowed by law, whichever is less — keeping in mind that the maximum rate might depend on whether the parties agree to a particular rate.
Comment
A. Simple interest as default rule: "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).
B. "Gap-filler maximum interest rate: This gap-filler interest rate (i.e., a rate charged in the absence of agreement) and the "simple interest" term (i.e., not compound interest) has in mind the usury laws in Texas and New York. 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).
2.11.4. Interest charges may not start until 30 days past due.
The Biller is not to charge interest sooner than the later of: (i) the stated start date, or (ii) the earliest date allowed by law.
2.11.5. Usury savings: Procedure for handling excess interest.
This section will apply if unlawful interest is charged by on behalf of the Biller — or paid by or on behalf of the Payer.
All interest-like charges and payments are to be treated 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.
The interest in excess of the maximum lawful rate is to be treated as having been charged or paid by mistake.
The Biller is to promptly: (i) give the Payer a refundable credit, computed as stated below; (ii) apply the refundable credit first to any remaining principal balance; and (iii) refund any remaining amount of the credit.
The amount of the refundable credit is to be: (i) the full amount of the excess interest charged and/or paid; plus (ii) (if excess interest was paid (not just charged:) interest, at the maximum legal rate, on that excess amount paid, from the date of the payment until the date credited.
The Payer's right to a refundable credit under this Clause is the Payer's EXCLUSIVE REMEDY for 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.
Comment
A. Concerning the legal background of usury-savings clauses such as this one — and their unenforceability in some jurisdictions — see 2.11.6.2.
B. Section 4: 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).
C. Section 6 — knowing charging of unlawful interest: This exception to the exclusive-remedy provision is included to try to reduce "moral hazard" by creating a disincentive for the knowing charging of unlawful interest.
2.11.6. Additional notes (not part of this Clause)
2.11.6.1. Are interest-charge provisions even worth it?
To speed up negotiation, a drafter representing a Biller might not want to include an interest provision in the Contract, 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," i.e., cause the Payer to insist that the Contract 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 Contract.
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 New York, which apparently brushes off usury-savings clauses entirely (although the state's usury laws contain significant exceptions). 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).
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).
Michigan: The state's supreme court held :
[I]n determining whether a loan agreement imposes interest that exceeds the legal rate, a usury savings clause is ineffective if the loan agreement otherwise requires a borrower to pay an illegal interest rate. This is so even if some of the interest is labeled something else, such as a "fee" or "charge."
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.
In short, a lender cannot avoid the consequences of contracting for a usurious interest rate simply by including a savings clause in the contract.
Relatedly, a New York intermediate appellate court observed that "where a loan agreement is usurious on its face, usurious intent will be implied and usury will be found as a matter of law." Roopchand v. Mohammed, 154 A.D.3d 986, 988-89, 62 N.Y.S.3d 514, 2017 NY Slip Op 07476 (N.Y. App. Div. 2017) (affirming summary judgment dismissing suit to collect on promissory note) (cleaned up).
Likewise, the District of Columbia Court of Appeals (which is not the federal D.C. Circuit) observed:
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.
A usury savings clause will not save a usurious transaction when a note is usurious on its face, that is, when the savings clause is directly contrary to the explicit terms of the contract, or when there is no evidence of the lender attempting to effectuate the savings clause.
That is why many jurisdictions have ruled that usury savings clauses, like the one Sloan relies upon here, can never operate to rescue an otherwise facially usurious rate.
In short, it is contrary to public policy to enforce a usury savings clause if the interest provided in the loan agreement is otherwise facially usurious at the time of contracting.
Sloan v. Allen 323 A.3d 439, 444 (D.C. App. 2024) (cleaned up, formatting edited).
2.11.6.3. 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:
A cable-TV provider's administrative fee, charged for late bill payment. See Garcia v. Texas Cable Partners, L.P., 114 S.W.3d 561 (Tex. App.—Corpus Christi 2003) (affirming summary judgment in favor of cable company) (citing cases); see also, e.g., Gomez v. Niemann & Heyer, L.L.P., No. 1:16-CV-119-RP (W.D. Tex. Oct. 7, 2016) (denying motion to dismiss claims against debt-collector law firm; citing Garcia) (see also earlier order explaining background).
2.11.6.4. 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.
2.11.6.5. … 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).
2.11.6.6. 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, does not 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)).
When this Clause is agreed to, the parties will follow it whenever the Contract calls for one party (the "Payer") to pay one or more amounts to another party (the "Biller").
2.12.2. Invoices are required for payment (usually).
Unless the Contract clearly indicates otherwise, the Payer need not pay the Biller until the Payer provides the Biller with an invoice in accordance with this Clause.
Comment
A. Invoices are standard practice in business — and they might be required by anti-fraud internal controls accounting regulations.
B. But an invoice might *not be required: This Clause sets out a procedure for invoicing — but it also takes into account that some contracts might be of a type where invoices aren't contemplated; see 2.12.6.1 for additional discussion.
C. 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 Contract is not a breach of the Contract — it merely means that the Payer needn't pay the invoice.
2.12.3. Invoices must itemize taxes, and other details.
The Payer may dispute, and not pay, an invoice to the extent that the invoice does not itemize: (1) any charges for taxes, shipping, handling, and/or insurance; and/or (2) any other details specified in the Contract.
Comment
A. A customer will want reasonable invoice details, the better to spot and dispute questionable charges.
B. For some very-detailed invoicing requirements, see excerpts from purchase-order terms published by Honeywell, at 2.12.6.10, and by Walmart, at 2.12.6.9.
C. 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.
2.12.4. Invoices must be written in specific language(s).
The Payer may dispute, and not pay, an invoice to the extent that the invoice is not written in:
the language of the Contract or another language that the payer's accounts-payable people can read; and
any other language required by applicable law.
Comment
A. Subdivision 2: Local tax law (for example) might require invoices to be written in the local language to facilitate audits by government tax authorities.
B. Companies sometimes use bi- or even trilingual invoice forms.
2.12.5. The Contract may specify invoicing schedules and deadlines.
2.12.6.1. Billers: Sometimes invoices aren't required
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. (Sometimes an agreed payment will be received by an escrow agent, not by you.)
And: In an employment contract, it'd be nonsensical to require the employee to provide the employer with an invoice for each paycheck.
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.
2.12.6.2. Billers: Too many incorrect invoices can be a problem
Biller: 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 ….
2.12.6.3. Billers: Check the Contract for specific payer billing instructions.
To speed up payment, it might be worth the biller's 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 — or even insist — that its suppliers submit invoices that way.
2.12.6.4. Billers: Include a reminder of payment methods?
If the Contract specifies that one or more particular payment methods may — or must — be used, then it'd be a good practice for each invoice to include a suitable reminder of that fact.
2.12.6.5. Billers: Check the Contract for when invoices are to be sent.
A. The timing of invoice issuance can affect the parties' respective cash flows:
It's fairly typical for suppliers to send invoices only after they finish their performance under the Contract, 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, etc.) and be paid as soon as possible after particular phases of the work are completed, as opposed to waiting to be paid until the work is 100% complete.
B. In the latter case, the Contract will typically 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 the foundation has been poured for a building under construction.
2.12.6.6. Billers: Check the Contract for invoice-submission deadlines.
A payer might have a legitimate reason for imposing a deadline for invoice submission. For example, you might 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.
And for a public company, a restatement of reported financial results is a Very Bad Thing — a restatement can lead to a sharp drop in the company's stock price, resulting from diminished investor confidence in the company's accounting practices. This happened to one company, Calgon Carbon, because the company's general counsel didn't timely forward outside law-firm invoices to the company's accounting department.2 (See generally Investopedia, Restatement.)
To impose a strict deadline for invoice submission, a drafter could consider the following optional language:
Late-Invoice WAIVER Option: If an invoice is submitted after an agreed-in-writing submission deadline, then that invoice is WAIVED by the Biller — that is, the invoice need not be paid unless and until the Payer decides (in its sole and unfettered discretion) to do so.
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).
2.12.6.7. Payers: Be flexible about invoicing methods?
Payer: It's probably not a good idea to lock down the invoicing method in the Contract: That would mean that a change to that procedure could require an amendment to the Contract. That'd likely be a pain.
Sure, as a practical matter, if you paid an "improperly" submitted invoice, that'd likely be a waiver of the submission requirement in the Contract. But why set that up as a potential dispute?
And keep in mind that, in a B2B context, the biller will usually be motivated to go along with any (reasonable) request that you make 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.
2.12.6.8. Payers: Don't delay asking for more invoice detail
Payer: You'll want to act promptly if an invoice doesn't contain enough "substantive details" to allow for appropriate review. A Delaware trial court held that a payer had waited too long:
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, slip op. at part IV.A.1 (Del. Super. Ct. Apr. 30, 2024) (decision after trial) (cleaned up, extra paragraphing added).
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.
When this Clause is agreed to, it indicates that a clearly-identified party that is anticipated to be a payer under the Contract (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").
Comment
A. Party names: The terms Prime, Sub, and Customer are used here only for convenience — those party relationships are a typical, but nonexclusive, use case.
B. Third-party payer: For this purpose, a payment to the Prime from a bank or other party, on behalf of the Customer, would count as a payment by the Customer.
2.13.2. To delay payment, the Prime must meet certain prerequisites.
The Prime may hold off on paying any amount that the Prime would otherwise owe to the Sub under the Contract until the Prime has itself paid by the Customer — but this will be true only if the Prime does both of the following:
Subdivision 1: This obligation amounts to a "be a good neighbor" requirement, one that's sometimes seen in pay-when-paid provisions (and, in some jurisdictions, might be an implied obligation under the law in any case). 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, quotingThos. J. Dyer Co. v. Bishop Int'l. Eng'g. Co., 303 F.2d 655, 659 (6th Cir. 1962).
2.13.3. Tthe Prime may not "play favorites" among multiple Subs.
If the Prime has multiple Subs under a pay-when-paid or pay-if-paid arrangement for a particular Customer matter, then the Prime must distribute each Customer-funded payment pro rata among all such Subs according to the amounts owed.
Comment
This might be a point of negotiation, so the above gap-filler section is provided as a checklist item.
2.13.4. The Prime must eventually pay, even if the Customer never does.
The Prime must pay each Sub invoice in question within a reasonable time on or after the invoice due date — even if the Prime itself has not been paid by the Customer — unless the option in section 2.13.5 below (pay if paid) is clearly agreed to in the Contract.
Comment
A. 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.
B. 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.
2.13.5. Option: Pay-If-Paid
This Option will apply only if:
the Contract clearly adopts this Option; and
the law does not prohibit pay-if-paid provisions under the circumstances.
The Prime may hold off on paying any amount that the Prime would otherwise owe to the Sub under the Contract unless and until the Prime has been paid by the Customer.
The Sub ASSUMES THE RISK that the Sub will not be paid at all if the Customer does not pay the Prime.
Comment
A. Subdivision 1.b: Pay-if-paid clauses might not be enforceable in some jurisdictions; see 2.13.7.3.
B. 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 contractor to subcontractor).
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).
2.13.6. Option: Nonpayment Only for Sub's Poor Performance
If the Contract clearly adopts this Option, then the Prime must 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.
2.13.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).
2.13.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 Clause 2.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 Contract. (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 18.1), or
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).
Texas, by statute, has regulated "contingent payment" clauses for certain construction subcontracts. See Tex. Bus. & Comm. Code § 56.001 et seq., especially § 56.054.
Virginia'sSB-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).
2.14. Payment Terms Clause
Payment terms are usually specified in very-abbreviated form, e.g., "net 30 days from receipt of invoice"; this Clause goes into more detail.
To be paid under the Contract, the Biller is to send an invoice 2.12 to: [ x ] whatever address the Payer has indicated is acceptable. [ ] the specific address designated in the Contract. [Drafters: Fill in.]
2.14.2. The Payer is to promptly check each invoice.
The Payer is to check each invoice promptly after receiving it. (See also the dispute provisions beginning at section 2.14.6 below.)
2.14.3. Payment is due net 30 days after receipt of invoice.
The Payer is to see to it that the Biller receives payment no later than the stated time after: [ x ] the Payer's receipt of the invoice. [ ] the date of the invoice as indicated on the invoice.
Comment
Tying a payment due date to the Payer's receipt of the invoice is (usually) fair because the Biller typically controls invoice submission.
2.14.4. Any commercially-reasonable means of payment may be used.
The Payer is to use, as the means of payment: [ x ] any commercially-reasonable means. [ ] other [specify in the Contract].
Comment
The Contract could specifically require payment, for example:
by check, perhaps on a specified bank, see 2.14.10.3;
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., checks drawn on banks in specified countries; Bitcoin or other so-called cryptocurrencies; etc.
2.14.5. Procedure for Payer to take an "offset"
If the Payer takes an "offset" (or "setoff"), the amount of the offset must not be more than a precisely-established amount that is clearly already due to the Payer from the Biller — unless the Biller has clearly agreed otherwise in writing.
Comment
What is an offset (or setoff)? 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).
Language choice — precise amount already due: This restriction aims to dissuade the Payer from trying to play games.
Silence about offsets? This section shouldn't be interpreted as either authorizing nor asz prohibiting offsets. (Some vendor-biased contracts might go even farther and explicitly prohibit a customer from taking offsets — and some customer-biased contracts might explicitly allow offsets.)
2.14.6. Process for disputing an invoiced amount
If for any reason the Payer does not pay the full amount of an invoice, then the Payer is to provide the Biller — no later than the nominal payment due date — with the following:
a reasonably-detailed written explanation of the Payer's position; and
copies of any relevant documentation, whether or not specifically asked for by the Biller.
Comment
Deadline for disputing payments: This deadline for challenging an invoice should deter the Payer from stringing 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, this requirement of a timely explanation 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.
Language choice: Written explanation of dispute: This language does not require formal notice (see Clause 6.9).
2.14.7. The Payer may ask for a supplemental, undisputed invoice
If the Payer asks, the Biller is to provide the Payer with one or more supplemental invoices containing only undisputed or resolved-dispute charges from a previous invoice.
Comment
In each supplemental invoice, the Biller should preferably consider:
identifying the original invoice; and
including reasonable notes, to help any later reviewers — such as litigation counsel — to put together a narrative of events.
2.14.8. Supplemental-invoice payments are due on the original date.
The Payer is to pay any such supplemental invoice expeditiously, and unless impossible, no later than the putative due date of the original invoice.
Comment
A Payer might counter that it would serve the Biller right to allow the Payer to treat the supplemental 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.
Note: When the Biller provides the Payer with a supplemental invoice, that shouldn't be interpreted as a concession by the Biller that the Biller wasn't owed the disputed amount.
2.14.9. No other payments are required under the Contract.
For emphasis: The payments clearly identified or ‑contemplated in the Contract are the only ones to which the Biller is entitled under the Contract unless:
the Payer clearly agrees otherwise; or
the law clearly provides otherwise.
Comment
This is a "roadblock" provision, recognizing 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 cousin: 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).
2.14.10. Additional notes (not part of this Clause)
Good morning — I'm calling to follow up on my emails, plural, about your past-due invoices; can you please tell me what the holdup is?
–Most suppliers, to at least some of their customers at some point, probably.
Payment disagreements 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.
When a Payer doesn't pay the entire amount — or even any amount — of a Biller invoice, the shortfall could occur, for example: • because the Payer believes that the Biller has incorrectly billed the Payer; or • because the Payer takes an offset, that is, reduces the amount paid by an amount supposedly owed by the Biller.
2.14.10.2. Biller- and Payer preferences about payment terms
Payment terms are often negotiated, because as a general rule:
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
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.
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.3
2.14.10.3. The Contract could specify a bank for payment by check
For payments by check, the Contract 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 does not reasonably object in writing.
2.14.10.4. 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.)
2.14.10.5. ACH payments
Payment by automated clearing house ("ACH") is an electronic debit transaction in lieu of a check. See generally Automated Clearing House (ACH) (Investopedia.com).
Caution: As with payment by check, (2.14.10.4), 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 Contract itself, Biller's bank-account information for ACH transaction:
– Suppose that the Contract were to be disclosed to others (such as in a due-diligence effort) or to 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. Example: This happened, for example, in a 2012 Delaware supreme court case.4
– 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 Contract, that the Biller will separately provide wire-transfer information. (This should be done by secure means.)
2.14.10.6. Payment 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 (2.14.10.4).
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).
2.14.10.7. Payment 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 Contract 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.
2.14.10.8. Payment 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).
Caution: As with ACH payments (see 2.14.10.5), don't include bank-account information in the contract itself.
2.14.10.9. Payment usually wouldn't cancel other rights
It's pretty well established that when the Payer makes a payment under the Contract, 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.
2.14.10.10. Caution: Prompt-payment statutes could impose deadlines
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."5
2.14.10.11. Payer should consider paying under protest
2.14.10.12. 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 Clause 6.4.
2.14.10.13. 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).
2.14.10.14. 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 2.11).
2.14.10.15. Late payments could trigger advance-payment demands
See Clause 2.2 and its commentary concerning demands for payment "up front" even if the Contract provides other payment terms.
2.14.10.16. 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.
Your author is not aware of any cases specifically on point. But some well-known companies have been hit with such profits-as-indirect-damages awards.6
2.14.10.17. 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 14.1.
(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 8.4.
2.15. Pricing Adjustments
When a prospective customer enters into an ongoing master purchase agreement with a supplier, the customer often wants the supplier to agree to limit how much the supplier can increase its pricing. This often requires more than a little negotiation.
This Clause, including any of its specifically-agreed options, will apply when a party (the "Supplier") charges money, to another party (the "Customer"), in connection with transactions under the Contract — for example, for goods, services, or other things.
2.15.2. Price adjustments will not be retroactive.
Any adjustments in the Supplier's pricing will not apply to any Customer order that the Supplier has already accepted unless the burdened party (the Customer for increases, the Supplier for decreases) has clearly agreed otherwise in writing.
Comment
The burdened party would not be wild about "retrading the deal" for existing purchases.
2.15.3. Option: Advance Alerts for Pricing Increases
If the Contract clearly agrees to this Option, then during the term of the Contract, the Supplier is to alert the Customer at least 30 days advance, in writing by any reasonable means, of any upcoming Supplier pricing increases that would affect Customer's orders under the Contract.
Each such alert is to state clearly:
the date on which the price increase is to go into effect; and
any other information required by the Contract.
The Supplier is to see to it that any order placed by Customer after such an alert, but before the stated effective date of the price increase, is to be invoiced at the lower price.
Comment
A. The notification requirement of subdivision 1 is phrased as an "alert," as opposed to notice under Clause 6.9.
B. This Option doesn't require advance alerts of upcoming price decreases, for reasons discussed at 2.15.9.
2.15.4. Option: Price-Increase Limits
If the Contract clearly agrees to this Option, then during the entire term of the Contract, the Supplier is not to increase the pricing it charges to the Customer:
more often than once per calendar year; nor
by more than 200% for any given calendar year.
Comment
Subdivision 2: The risibly-high "200% per year" is included here as an attention-getter for drafters and to give suppliers 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]."
Note:Suppliers will generally want "X% or CPI, whichever is higher," while customers will want "X% or CPI, whichever is lower." (See generally Clause 2.5, CPI definition, and its commentary.)
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).
2.15.5. Option: Increases Only as Generally Applicable
If the Contract clearly agrees to this Option, then during the term of the Contract, the Supplier is not to increase the prices charged to the Customer for goods or services covered by the Contract except as part of — and by a percentage no greater than the percentage of — a price increase to the Supplier's customers generally for the same items.
Comment
This Option might satisfy a customer that was comfortable with allowing market pressure to constrain a supplier's price increases.
This Option could also address any fear the customer might have that a supplier might retaliate against the customer, for example because the customer was looking to become independent of the supplier. 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 supplier Air Products (BizJournals.com May 6, 2021) (paywalled), and Plug Power sues Air Products over 'draconian elevated prices' (BizJournals.com Apr. 2, 2021) (paywalled).
2.15.6. Option: Straight Pass-Through of Cost Increases
If the Contract clearly agrees to this Option, then during the term of the Contract, if the Supplier's relevant costs increase, the Supplier may pass the increase on to the Customer in the Supplier's pricing.
When passing cost increases on to the Customer in this way, the Supplier may not add a markup unless:
the Contract clearly says so; or
the Customer so agrees in writing.
If the Customer so requests, the Supplier is to provide the Customer with reasonable documentation to support the Supplier's intended princing increase.
The Customer must treat all information that the Supplier provides under subdivision c as the Supplier's Confidential Information in accordance with Clause 8.18 (Confidential Information).
Comment
This is a stripped-down version of price increase pass-through clauses that are sometimes seen in ongoing master purchase agreements.
2.15.7. Option: Sole-Discretion Pricing Increases
If the Contract clearly agrees to this Option, then for the avoidance of doubt, the Supplier is not restricted in its ability to adjust its pricing, from time to time, in its sole discretion (defined at Clause 7.23).
Comment
A customer certainly wouldn't want to include this option in a contract — and a supplier might not want to include it either, because doing so might call attention to the issue ("poke a bear," see 30.12) and provoke the customer to demand restrictions on the supplier's ability to raise prices.
2.15.8. Option: Pricing Lock-In
If the Contract clearly agrees to this Option, then during the term of the Contract, all pricing for transactions under the Contract will be as stated in the Contract (including without limitation in any relevant schedule, exhibit, etc.).
Comment
Caution: Drafters representing suppliers 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 6.6.4 for a real-world story in which one of your author's clients had agreed to such a combination for a particular customer — only to find later that, for that customer, the supplier was locked in to (what became) an outdated price schedule for ten years.
2.15.9. Notes: Why no advance notice of price decreases?
A. Option 2.15.3 doesn't require advance notice to the customer of upcoming price decreases. That's because:
The customer will generally be happy to have price decreases go into effect immediately, without advance notice and a waiting period.
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.
B. True: The customer might want advance notice of a price decrease, so that the customer could defer purchases that it would have otherwise made at the higher price.
But the supplier would likely object to having to let anyone know in advance about upcoming price decreases, because:
The supplier might not know in advance that it would be cutting prices; and
The supplier would not want to have to wait out an advance-notice period, because that could hurt the supplier's ability to make sales at the old, higher pricing — especially if word leaked to other customers. This would 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, which prematurely announced a future model, resulting in plummeting sales of the existing model. (The Wikipedia article lists other examples of such supplier experiences.)
C. In any case, the customer likely would prefer to have the supplier price cuts take effect immediately, to give the customer maximum budget flexibility.
D. And finally, the customer might be satisfied with Option 2.15.3, 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 supplier's goods or services — if the supplier'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).
When this Clause is agreed to, the parties will follow it whenever, in connection with the Contract, any potentially-taxable event occurs of the kinds described in this Clause.
2.16.2. The parties here are the "Biller" and the "Payer."
In this Clause, the parties are referred to as the "Biller" and "Payer", respectively (and self-explanatorily).
2.16.3. The Biller is to deal with all sales taxes.
The Biller is to arrange for timely reporting and remitting, to all appropriate authorities, all sales taxes, if any, for the matter(s) being invoiced.
Comment
A. "Arrange for:" This recognizes that the parties might "hire out" some or all of their tax-related obligations.
B. 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).
2.16.4. Definition: Sales tax
For this purpose, the term "sales tax" (whether or not capitalized) refers to the following in any relevant jurisdiction: • sales taxes; • value-added taxes; • excise taxes; • other forms of ad valorem tax; and • taxes equivalent to any of the foregoing.
2.16.5. Claims of tax exemption require an official certificate.
If the Payer claims to be exempt from sales- and similar taxes, then the Payer is to timely provide the Biller with appropriate official tax exemption certificate(s) — otherwise, the Biller is entitled to charge the Payer, in which case the Payer is to pay, any applicable sales tax.
Comment
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.
2.16.6.Use taxes, etc., are the Payer's responsibility.
The Payer is to arrange for timely reporting and paying any use- and/or consumption-type taxes for the matter(s) being invoiced.
Comment
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).
2.16.7. Each party is responsible for its own income taxes, etc.
Each party is to arrange for reporting and payment of any tax based on the party's own net income, profits, or similar basis (as just one example, any so-called windfall profits tax).
Comment
Sometimes a contract might call for a payment to be "grossed up" so that, after income taxes, the payment equals a specified amount; see [BROKEN LINK: taxes-gross-up] for discussion.
2.16.8. Indemnity obligations for tax-related claims
Each party "P" is to defend and indemnify each other party "OP" and its Protected Group from any claim arising from P's allegedly not carrying out P's tax obligation(s) under the Contract — whether the claim is by a government authority or otherwise.
2.16.9. Definition: What counts as a "tax"?
In this Clause (and otherwise in the Contract unless the context clearly indicates otherwise), the term "tax," whether or not capitalized:
refers to any tax, assessment, charge, duty, levy, or other similar charge of any nature, imposed by any "taxing authority," defined below; but
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.
B. Subdivision 1: 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 Contract less readable.
C. Subdivision 2: 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).
2.16.10. Definition: What counts as a "taxing authority"?
In this Clause (and otherwise in the Contract 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.
Comment
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.
In many lawsuits (and arbitrations), attorney fees can end up being the biggest expense. Prevailing-party attorney fee clauses are not uncommon in contracts; they're sometimes referred to generically as "Loser Pays" or the "English Rule" (where it's the standard) or the "Everywhere But America Rule."
This Clause will apply in any lawsuit or other proceeding relating to the Contract.
Comment
The term "relating to" is pretty broad; see the link above.
3.1.2. Is anyone entitled to recover attorney fees from another party?
The following party is entitled to recover its "attorney fees" and its "costs," each as defined below, for all stages of the proceeding unless the Contract clearly provides otherwise:
[ x ] The prevailing party, determined as provided by law, may recover its attorney fees and costs.
[ ] (American Rule:) Each party is responsible for its own attorney fees except as otherwise provided by law. 3.1.5
[ ] (Texas Rule:) A party that successfully asserts a claim for breach of the Contract may recover its attorney fees and costs, but not a party that successfully defends against such a claim. 3.1.6
[ ] Each party is responsible for its own attorney fees, even if the law would allow a party to recover its fees. 3.1.11.2
Comment
Determining just what constitutes a prevailing party can be very fact-specific: 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); see also a slide used in a June 2020 CLE Webinar on "Commercial Contract Pitfalls" by Locke Lord attorneys Janet E. Militello and Brandon F. Renken.
3.1.3. Definition: Attorney fees
For purposes of the Contract, 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; and
encompasses, without limitation, such fees and expenses paid to or for one or more attorneys; law firms; and testifying- and/or consulting experts.
Comment
To apostrophe, or not? 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 8.19.12.4. See 18 U.S.C. § 1833(b)(3)(A), (b)(4).
If the Contract requires a party to pay or reimburse another party's attorney fees, then the recoverable amounts also include the other party's "costs" in the dispute, as that term is commonly understood by lawyers, such as court filing fees; arbitration-administration fees; deposition- and transcript charges; and the like.
Comment
Courts often award "costs" even when not awarding attorney fees.
3.1.5. Option: American Rule for Attorney Fees
If this Option is clearly agreed to in the Contract, then each party WAIVES any right it might have — and therefore it will not seek — to be reimbursed by the other party for its attorney fees, even if a law or rule would otherwise have entitled that party to do so for the dispute in question.
Comment
A. The American Rule 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).
B. In some jurisdictions there might be a "special circumstances exception" to the American Rule — but that exception could be a tough sell to a court.
3.1.6. Option: Texas Rule for Attorney Fees
If this Option is clearly agreed to in the Contract, then a party that successfully asserts a claim for breach of the Contract — but not a party that successfully defends against such a claim — is entitled to recover its attorney fees and costs incurred in asserting the claim.
Comment
This Option is modeled on section 38.001 of the Texas Civil Practices and Remedies Code — which does not allow a party to recover attorney fees for successfully defending against a claim for breach of the Contract. 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. Something like it was seen — but not relied on by the court — in an Eleventh Circuit case. See 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: If drafting a provision like this, consider referring to the breach-of-contract plaintiff, not as the non-breaching party, but instead as, say, the "contract claimant." That's because in a Northern District [of California] case, 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 did not 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 3.1.11.4.
• Pro tip: If a party thinks it might be more likely to be the defendant in a dispute, and that Texas law will apply, then that party might want to override the Texas Rule using a prevailing-party clause (see 3.1). On the other hand, if the party wants the Texas Rule to apply, it might want to include this Option in the contract.
3.1.7. Option: Attorney Fees in Motion Practice
If this Option is clearly agreed to in the Contract, then it will apply when a party prevails in an interim proceeding with another party such as, for example, motion practice and/or an interlocutory appeal.
In such a situation, that prevailing party is entitled to recover, from the other party, the prevailing party's reasonable attorney fees for the interim proceeding.
If the other party later ends up being the prevailing party in the action as a whole, that other party is not entitled to a refund of amounts it paid under subdivision 2, nor to being reimbursed for its attorney fees for the interim proceeding.
Comment
Attorney fees in motion practice can be a major, usually-unrecoverable expense in a lawsuit or arbitration. ("Motion practice" refers to 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: The rules of procedure typically "require" lawyers and parties to play nice. And a judge could impose sanctions for bad behavior.
But in reality, judges seldom impose sanctions. And realistically, a lawyer's concern about being sanctioned will often be far outweighed by the lawyer's fear of losing the case — and/or the fear that an angry client might think that the lawyer isn't doing enough to smite the client's adversary.
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.
3.1.8. Option: Attorney Fees for ADR Nonparticipation
If this Option is clearly agreed to in the Contract, then it will apply, as an incentive to participate in dispute-resolution proceedings. if in or more dispute-resolution proceedings, of any kind, that are called for by the Contract:
a party "P" tries to block in court, or
P simply fails to participate in good faith even to a minimal extent.
If OP is the prevailing party in the dispute, then P must pay (or reimburse) all of OP's attorney fees for the entirety of the dispute in question, at all stages, including but not limited to appeals.
Moreover, P will not be entitled to recover its own attorney fees even if P would otherwise be entitled to do so.
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 Contract.
Comment
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. 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: In a Maine case, 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: In a California case, 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: "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: In a First Circuit case, 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).
3.1.9. Option: Attorney Fees for Contrary Positions
This Option will apply only if:
this Option is clearly agreed to in the Contract; and
in a lawsuit or other dispute (an "action"), a party ("P") asserts a position that is contrary to an express- or unmistakably-implied term of the Contract.
P must pay (or reimburse) all attorney fees 3.1 and costs incurred in the action, by any other party to the Contract that contests P's assertion, through with the date (if any) that P withdraws its contrary assertion in question.
Comment
A. Trying to back out of a contract's agreed "policy statement" (to use Ken Adams's term) should be a no-no (makes it so) because it often results in needless expense and delay in resolving disputes for the parties.
B. Unfortunately, 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) withTranscor 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).
C. Here are a few hypothetical examples of possible such contrary assertions:
A party ("P") seeks to recover consequential damages from another party ("OP") (see 3.2) even though the Contract excludes such recovery;
P seeks monetary relief from OP in excess of an agreed "cap" (see Clause 3.3)
P asserts a purported right, or a purported obligation on OP's part, that P had waived (see Clause 8.68)
P asserts that a notice took effect at a time inconsistent with the notice provisions stated in the Contract (see Clause 6.9)
P asserts that the Contract or a related document was amended or otherwise modified in a manner inconsistent with the amendment provisions of the Contract (see Clause 6.1)
P asserts that an action taken by P was timely even though P took the action after a deadline stated in the Contract or a related document (for example, a statement of work).
D. Subdivision 2: The "withdraw[al]' language in this Option 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.
3.1.10. Option: Attorney Fees for Unproved Accusations
If this Option is clearly agreed to in the Contract, then it will apply if, in any dispute relating in any way to the Contract:
a party "P" accuses another party to the Contract "OP" — and/or OP's affiliates, or the people of any of them — of criminal conduct, fraud, and/or breach of fiduciary duty relating to the Contract or the parties dealings under the Contract; but
P does not prove the accusation with the degree of proof required by law or, if higher, by the Contract.
In that situation, P must pay, or reimburse, all of the attorney fees incurred by or on behalf of the accused in defending against the accusation.
If any uncertainty exists about whether particular attorney fees come within the scope of this Option, the uncertainty is to be resolved in favor of the accused.
Comment
Parties and/or their counsel sometimes accuse the other party of fraud, breach of fiduciary duty, and the like; in part, that's because jurors can relate to "they lied!" and might use it as a simple, Gordian-knot way of quickly deciding a complex dispute.
Unfortunately, except in egregious cases, there's hardly ever any downside for parties or lawyers to throw around such claims. That means that a lawyer, seeking to please an angry client, might be tempted to think, Why not — it might work, and what have we got to lose? (This could be said to be a species of moral hazard.)
So: This Option seeks to create some such downside.
3.1.11. Additional notes (not part of this Clause)
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 a hotly-contested 2021 Tennesee case, a home builder was found to have breached a contract with a homeowner; the builder was ordered to pay damages of $6,800 — plusmore 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 3.1.5.
3.1.11.2. 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 section 3.1.5).
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 a 2016 case, in which a federal district court in California awarded 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.
3.1.11.3. 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), discussingWilborn 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,3.1.5 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 3.1.11.4.)
3.1.11.4. California, Oregon, (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).
3.1.11.5. 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).
3.1.11.6. 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).
3.1.11.7. 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 inColorado 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).
This Clause will apply if clearly agreed to in the Contract.
Comment
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 3.2.9.4).
3.2.2. Definition: "Consequential damages" means atypical damages.
In all matters relating to the Contract, the term "consequential damages" refers to a monetary award to compensate a party for harm resulting from a breach of the Contract, where all of the following are true:
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; but:
the harm was specially foreseeable to the breaching party — that is, at the time of entering into the Contract, the breaching party knew (or should have known) that, due to special circumstances, the harm was nevertheless reasonably likely to result from breach.
Comment
A. It's worth defining "consequential" damages: The term's vagueness, and its different meanings in different jurisdictions, can lead to costly and perhaps-avoidable litigation.
(Atypical damages seems a more-apt label than consequential damages — which is kind of a dumb name, incidentally; see 3.2.9.11. But of course any attempt to change ages of lawyer-speak would likely be quixotic.)
B. Pro tip: Some practioners (your author is not one of them) like to include a detailed "laundry list" of highly-specific categories of excluded damages, such as the example at 3.2.9.5.
C. Foreseeable to the breaching party: This uses the general approach of the classic English case, Hadley v. Baxendale, discussed in more detail at 3.2.9.7.
3.2.3.Neither party will be liable for consequential damages.
The stated party WILL NOT BE LIABLE for consequential damages — that is, for atypical damages — resulting from breach of the Contract.
For emphasis: Each party WAIVES — and agrees not to assert any claim — seeking to recover any such damages for breach from any other party to the Contract.
Comment
A. Subdivision 2: See the discussion in the commentary at Clause 3.12.1.5: In one case, the Texas supreme court held that a waiver of consequential damages was not a covenant not to seek such damages.
B. See also Option 3.1.9, which provides for awards of attorney fees against parties that take positions contrary to provisions such as this one.
3.2.4. Only expressly-stated special circumstances would be different.
The exclusion of this Clause would apply even if — whether at the time of forming the Contract or before the alleged breach — that the breaching party actually knew or should have known of special circumstances as described above, unless the Contract expressly identified particular special circumstances and stated that damages resulting from those circumstances would not be subject to the exclusion of this Clause.
Comment
This exception borrows from a clause proposed at the redline.net forum for lawyers.
3.2.5. Certification: No party knows of any such special circumstances.
Each specified party CERTIFIES that, so far as the certifying party is aware, there are no "special circumstances," of the kind referred to in section 3.2.4 above, that could give rise to the certifying party's incurring atypical damages as a result of any other party's breach of the Contract.
Each party acknowledges that each other party is actually, and reasonably, relying on the parties' agreement to this Clause as a "material" element (that is, an important part) of the economic bargain reflected in the Contract.
Comment
See 8.57 for discussion of why the question of reliance can be an issue in contract-related disputes.
Concerning the effect of an acknowledgement, see Clause 7.1.
3.2.7. Particular case: "Lost profits" might or might not be excluded.
This Clause's exclusion of consequential damages:
excludes, without limitation, lost profits from collateral business arrangements, but
does not exclude lost profits that were a direct and probable result of a breach of the Contract and thus constitute general damages.
Comment
In some consequential-damages exclusions, "lost profits" — without the limitation to collateral business arrangements — are listed as specific examples of excluded damages. But 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; some other courts have issued similar rulings.7
3.2.8. Certain general provisions for liability limitation are incorporated.
Clause 3.12 is incorporated by reference into this Clause.
3.2.9.1. Economics of consequential-damages exclusions
Applying North Carolina law, the Fourth Circuit 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).
3.2.9.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.
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 — causing 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 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"?
3.2.9.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) 2020 ruling from the Internet age, 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.)
3.2.9.4. Pro tip: Use a damages cap instead?
Some experienced practictioners (including your servant) believe that a more-sensible approach will sometimes be:
not to bother with an exclusion of consequential damages, because of the proof difficulties summarized above; and
3.2.9.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.
Your author's 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 —
that courts will interpret the laundry list as the drafter hoped; and
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 7.32.)
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;
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).
3.2.9.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).
3.2.9.7. Origins: The influence of Hadley v. Baxendale
This Clause 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.
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 3.2.9.10, but this Clause sticks to the traditional Hadley formulation.
3.2.9.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).
3.2.9.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.
3.2.9.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: In AcryliCon USA (2021), 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, in Severn Peanut (2013), 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!
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 in a 1997 decision, 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.
For cases decided under Texas law, the court's Arthur Andersen 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.
3.2.9.11. "Consequential damages" isn't the best name
Your author wishes (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).
finally, if neither of the above conditions is shown to be true, then the damages simply aren't recoverable, period. See id. at 184 (reversing court of appeals and rendering judgment against plaintiff because "legally insufficient evidence supported the award of consequential damages").
When this Clause is agreed to, it will apply in any situation where a damages cap is agreed to in writing.
Comment
Damages caps are quite common in contracts — especially contracts drafted by suppliers.
A damages cap could be agreed to: • in the Contract itself; and/or • in some other document, possibly (for example) in a purchase order or statement of work under the Contract.
And damages cap could be stated as: • a fixed amount; • a variable amount, perhaps changing over time or in different circumstances; and/or • a computable amount, e.g., a multiple of some number such as a contract price.
3.3.1.2. What forms of monetary award are covered by a damages cap?
Except as otherwise provided in this Clause, an agreed damages cap will apply to all forms of monetary recovery sought — including without limitation monetary awards of damages, costs, and/or attorney fees.
3.3.1.3. What forms of liability are covered by a damages cap?
Except as otherwise provided in this Clause, an agreed damages cap will apply no matter what legal principle or other theory of liability is involved, including without limitation NEGLIGENCE and GROSS NEGLIGENCE.8
Comment
Neglgence and gross negligence: Those terms are in bold all-caps to make them conspicuous, just in case the "express-negligence rule" in Texas and some other jurisdictions were to be held to apply, as discussed at 3.9.5.
3.3.1.4. Damages caps apply in the aggregate
Unless the Contract clearly states otherwise, a damages cap will limit the cumulative liability on the part of the specified party and its Protected Group (defined at 7.40), for all claims against all of them together, over all time, and not per-person, per-project, or or per-claim.
Comment
Example of aggregated damages claims: To illustrate the operation of this section, consider the hypothetical example:
The Contract is hypothetically between two parties, "Alpha" and "Bravo"; it states that Alpha's liability to Bravo is capped at $100.
In a first lawsuit relating to the Contract, Alpha is found liable to Bravo for $70 in damages and $10 in attorney fees and costs.
Alpha's appeals are unsuccessful, so Alpha eventually pays Bravo the $80 total liability amount.
Later, in a different lawsuit relating to the Contract, Alpha is found liable to Bravo for $350; again, Alpha's appeals are unsuccessful.
Because of the agreed damages cap, Alpha's liability to Bravo in the second lawsuit is not $350, but $20 — that is, the difference between the $80 that Alpha previously paid to B (as a result of the first lawsuit) and the $100 damages cap.
3.3.1.5. How would claims for set-off be handled?
An agreedam-cap aggreg
d damages cap is to be applied before determining the effect of any applicable liability set-offs.
Comment
Setoffs (or offsets) are discussed at section 2.14.6 of Clause 2.14. 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).
3.3.1.6. Are any amounts not subject to a damages cap?
Unless clearly agreed otherwise in writing, a damages cap does not limit any of the following:
amounts to be paid under the Contract — including, without limitation, amounts to be paid (if any) for:9 (i) defense against third-party claims, 3.4 and/or (ii) indemnity obligations. 3.9
damages arising from intentional fraud (as opposed to fraud resulting from recklessness); 3.3.4
damages for intentional or reckless breach of confidentiality obligations under the Contract, if any;10
costs of court and/or of other proceedings (e.g., costs of arbitration if arbitration is agreed to).
Comment
Exclusion of amounts due is a "cheap insurance" (11.3) provision, even though under the law it might not be necessary to state it explicitly. 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 paymelim-liab-excl
nt of a debt and a claim for damages for breach of contract").
Exclusion of defense- and indemnity obligations: This cap on defense- and indemnity liability is very often a point of negotiation — but it 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.
Exclusion of reckless breach: This affects reckless breaches of confidentiality obligations, not just intentional ones, in the interest of helping to deter "moral hazard."
Injury, etc.: This damages-cap 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.
3.3.1.7. Other provisions incorporated
Clause 3.12 (limitation of liability general provisions) is incorporated by reference into this Clause.
3.3.2. 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.
3.3.3. 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.
(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.
3.3.4. 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 3.15.8.
Example:Recklessness carve-out: In a 2021 Ohio 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, causing 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 does not 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 in 2023, 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).
3.3.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).
3.3.6. Different damages caps for different purposes?
A contract could provide for different damages caps for:
different breaches or types of breach (see 3.3.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 Contract (see 3.3.8 below for some possibilities); and/or
different geographical areas.
3.3.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.
3.3.8. Pro tip: Negotiate variable limitations of liability?
Exclusions of consequential damages (see 3.2) and damage-cap amounts (see 3.3) 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 3.2: Consequential Damages Exclusion Clause 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.
3.3.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 generallyUCC § 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."
This Clause synthesizes language often seen in contracts about how an obligated party is to conduct defense proceedings and/or settlement negotiations.
This Clause governs when, under the Contract, one party (the "Defender") is required to defend (equivalently, "provide a defense for") another individual or organization (the "Named Person") that is clearly indicated (expressly or otherwise) in the Contract, against one or more specified categories of claim by a third party.
3.4.1.2. Who is entitled to defense?
The Defender is to provide a defense for each of the following as stated in this Clause; each is referred to (individually) as a "Beneficiary" (sometimes as the Beneficiary):
the Named Person;
each individual and organization (each, a "person") that is an affiliate of the Named Person, if any; and
for each person in 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.
Comment
Specificity? The Named Person and the categories of claim might be expressly stated in the Contract, or clearly indicated there by reasonably-specific criteria.
3.4.1.3. Required: A competent and diligent defense
The Defender is to arrange for the 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 does not timely object for good reason.
Comment
Timely, competent and diligent defense: This simply mirrors the general legal-ethics rules for lawyers.
Comment
Licensed, suitably-experience and -reputable: This 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.
3.4.1.4. May the Beneficiary hire other counsel?
The Beneficiary is entitled to use separate counsel to monitor the defense; if the Beneficiary does so, then:
the Beneficiary and the Defender are to instruct their respective counsel to provide reasonable cooperation with each other in the defense; and
neither the Defender nor the Defender's counsel is responsible for any fees, expenses, or professional performance by the Beneficiary's counsel except as provided at [BROKEN LINK: def-ben-ctrl][BROKEN LINK: def-ben-ctrl] below.
Comment
Separate monitoring counsel: 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. This will often be the case — 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 [BROKEN LINK: def-ctrl].
3.4.1.5. Who will be in charge of the claim defense?
If the Beneficiary advises the Defender of the claim as provided in this Clause, then the Defender has 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 Clause.
Comment
Defender control of defense: This section doesn't require the Beneficiary to formally tender the defense to the Defender. Relatedly, in a First Circuit case, the contract's defense provision required only "the opportunity for complete control of the defense and settlement thereof by the indemnifying party[.]" See 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).
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.
3.4.1.6. Could the Beneficiary ever take over control of the defense?
If a conflict of interest arises that precludes the Defender's counsel from representing the Beneficiary in the defense, then:
the Beneficiary is entitled to assume control of the defense;
the Defender is to reimburse the Beneficiary for reasonable attorney fees that the Beneficiary incurs in conducting its defense, in accordance with Clause 2.9 (expense reimbursement); and
if the parties 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.
Comment
Conflicts of interest: This section is informed by a standard legal-ethics rule (in the U.S.): Party A's lawyer usually cannot also represent Party B in the same litigation if the two parties have conflicting interests.
3.4.1.7. The Beneficiary must not make non-factual admissions or waivers
The Beneficiary is not to make non-factual admissions or waivers relevant to the claim, at any time that the Defender is entitled to control the Beneficiary's defense against the claim, unless the Defender gives its prior written consent.
Comment
No non-factual admissions, etc.: 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 should not be countenanced without consent.
3.4.1.8. The Beneficiary must 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:
if, and as reasonably requested by, the Defender;
whether or not the Beneficiary asked for (or even desired) a defense against the claim; and
including but not limited to providing the Defender and/or the Defender's counsel with all information reasonably requested for the defense.
Comment
Reasonable cooperation in the defense: This reasonableness requirement allows some flexibility for both parties, e.g., to help protect the Benefiiary's attorney-client privilege.
3.4.1.9. The Defender is responsible for any monetary awards
The Defender is to pay any and all final, no-longer-appealable monetary awards, entered against the Beneficiary, resulting from the claim — unless clearly agreed otherwise, the Defender's responsibility:
extends (but is not limited to) damage awards and attorney-fee awards; but
encompasses only monetary awards and not complete indemnity from the consequences of the claim or adverse judgment.
3.4.1.10. What if the Beneficiary delays 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 will be entitled to take the delay into account — to a reasonable extent — in conducting the defense.
Comment
Delay in asking for defense: 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 does not 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).
3.4.1.11. What if the Beneficiary might be at fault?
For emphasis: If the Contract requires the Defender to defend a Beneficiary against third-party claims in particular circumstances, then the Defender is to do so:
even if the claim in question allegedly resulted from the Beneficiary's own negligence, and
even if the Beneficiary would not be entitled to indemnity against the claim if the claim were successful.titled to indemnity against the claim if the claim were successful.
Comment
If the Beneficiary is at fault: 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).
3.4.1.12. What if the Beneficiary does not want a defense?
If the Beneficiary declines a defense; does not ask for a defense; or even tries to halt or obstruct an in-progress defense; then:
the Defender may, in its sole discretion, defend against the claim anyway, on the same terms as if the Beneficiary had requested a defense;
the Beneficiary is to provide the same cooperation with the Defender as though the Beneficiary had asked for a defense; and
the Defender need not indemnify (that is, reimburse) the Beneficiary for losses or expenses, of any kind, arising from or relating to the claim, even if the Contract would have otherwise required reimbursement.
Comment
An unasked-for or unwanted defense? 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.
One possible 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 products. • But the supplier might care very much, because 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 — but just what constitutes "reasonable" cooperation might depend in part on the nature and extent of the Beneficiary's potential liability exposure.
3.4.1.13. May the Defender settle the claim?
The Defender is free to settle the claim (in whole or in part) on behalf of the Beneficiary, but the Defender has no authority to settle the claim, and is not to purport to do so — and the Beneficiary will not be bound by any supposed settlement — if the settlement purports to do any of the following without the Beneficiary's prior written consent:
restricting or placing conditions on the Beneficiary's otherwise-lawful activities; or
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
encumbering any of the Beneficiary's assets; or
including or requiring any admission or other statement by the Beneficiary; or
calling for the entry of a judgment inconsistent with any of subdivisions a through d above. (Concerning consent judgments, see also [BROKEN LINK: def-cons-jmt].)
Comment
Defender's settlement authority: 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 Clause puts fences around the Defender's ability to settle a claim.
3.4.1.14. May the Defender commit the Beneficiary to a consent judgment?
The Defender is free to agree to a consent judgment on behalf of the Beneficiary, 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 [BROKEN LINK: def-sett-ctrl].
Comment
Consent judgments — Defender's settlement authority: 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).
3.4.1.15. May the Beneficiary settle the claim?
The Beneficiary may settle the claim on its own — but if the Beneficiary does so without the Defender's prior written consent, the Beneficiary will automatically have WAIVED, and to have RELEASED the Defender from, any further defense- or indemnity obligations for that claim unless the Defender unreasonably withheld its consent to the settlement.
3.4.1.16. The Defender's obligations have limits
The Defender's obligations under this Clause are considered a type of indemnity obligation under Clause 3.9 — that means, without limitation, that the exclusions and limitations of that Clause will apply equally to this Clause.
3.4.2. 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 8.4), 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). .
3.4.3. 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.
A party's nonperformance will be excused if the party invokes force majeure as stated in this Clause — but only if the invoking party shows all of the following things to be true:
The party's nonperformance must have in fact resulted (directly or indirectly) from the force majeure.
The party must invoke force majeure at a reasonable time — which could be before12 or after the relevant force majeure situation or -situations, depending on the circumstances.
The Contract must not specify otherwise for particular circumstances.
Comment
Resulted from the force majeure:Example: A California appeals court affirmed a summary judgment that a brew pub could not rely on the COVID-19 pandemic to excuse its nonpayment of rent to its landlord because the brew pub — which was part of a large chain of restaurants and bars — could have paid its rent notwithstanding the pandemic; the court reviewed COVID-era case law from other jurisdictions as well. See West Pueblo Partners, LLC v. Stone Brewing Co., LLC, 90 Cal. App. 5th 1179, 1188-90 (Cal. App. 2023).
When to invoke force majeure: 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.
3.5.1.2. Can force majeure excuse payment failure?
Force majeure will not excuse a party's failure to timely pay an amount due unless the payment failure is due to generalized failure — beyond the invoking party's control — in all reasonably-available payment systems, such as, for example:
all reasonably-available banks are closed by government edict; or
substantially all of the invoking party's assets that could be used for payment are trapped or stranded in one or more failed banks, and the invoking party (i) had no reason to anticipate that this would happen, and (ii) no ability to move such assets; or
substantially all systems generally used for commercial payments are "down" — this must include all systems that the invoking party generally uses for that purpose.
Comment
Payment failure as force majeure? In the West Pueblo Partners decision cited above, the court affirmed a summary judgment that a brew pub — which was 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).
Generalized bank closings happened, for example, in 1933 during the Great Depression.
Trapped- or stranded assets likely happened to some depositors in March 2023, after the failure of the Silicon Valley Bank, among others.
3.5.1.3. Definition: What can qualify as "force majeure"?
The term "force majeure" refers to any situation — an event, or a series of related- and/or independent events — in one or both of the following two categories:
the situation is of a specific type listed in the Contract as constituting force majeure — if any — or a situation of a similar kind or nature, in any case regardless whether the situation was foreseeable at the time the parties entered into the Contract; and/or
the situation was unforeseeable at the time the parties entered into the Contract, whether or not similar to a specific type that is listed in the Contract.
Comment
Definition of force majeure: This section 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 in TEC Olmos (2018). See TEC Olmos, LLC v. ConocoPhillips Co., 555 S.W.3d 176, 182 (Tex. App.—Houston [1st Dist.] 2018, pet. denied) (citing cases).
Why is this definition at the end of this Clause? This definition of force majeure is intentionally located at the end of this Clause, 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" (see the examples below) at Option 3.5.2.12) 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. See also the commentary to Clause 7.32 (meaning of include). 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 inJN 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).
When this Option is agreed to, the fact that a party may invoke force majeure under the Contract does not imply that the party may not assert an impossibility- or impracticability defense, to the extent that applicable law (common law, statutory, or otherwise) would allow the party do so even without the Contract's force-majeure provisions.
But: Neither would the absence of this Option in the Contract imply that the parties intended to preclude a party from asserting one or more of such defenses.
Comment
Force majeure option — other defenses allowed: This Option is intended to "write around" the possibility that, as Judge Posner put it, "the doctrine of impossibility is an 'off-the-rack' provision that 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
3.5.2.2. Option: Force-Majeure Termination
When this Option is agreed to: Either party may terminate all parties' going-forward obligations under the Contract if the aggregate effect of force majeure:
is material in view of the Contract as a whole; and
lasts longer than 60 days after a party first duly invoked force majeure.
Comment
Force-majeure termination option — materiality question: 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).
3.5.2.3. Option: Force-Majeure Status Reports
1.When this Option is agreed to, it will apply if:
a party invokes force majeure; and
another party to the Contract, affected by the invocation, requests status updates.
Comment
Force-majeure option — status updates: 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 Clause 8.12) can serve that purpose, but some customers might want something more scheduled; this Option offers one possibility.
3.5.2.4. What must the invoking party do?
The party invoking force majeure is to provide the requesting party with reasonable information to other parties to the Contract — 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.5.2.5. What must other parties do with status updates?
If another party (the "recipient") receives non-public force-majeure status information from a party invoking force majeure, then the recipient is to do the following:
treat that information as the invoking party's confidential information;
use reasonable measures to preserve the secrecy of the information; and
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 Contract.
3.5.2.6. Option: Provider Allocation – Discretion or Proportionality
When this Option is agreed to, it will apply whenever both of the following are true:
under the Contract, a party (the "Provider") is required to supply goods or services to another party (the "Customer"); and
the Provider both (i) invokes force majeure, and (ii) experiences shipping delays as a result of one or more force-majeure situations, whether or not of the type invoked.
If the Contract 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.
If the Contract 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.13
Comment
Force majeure option — Provider's allocation discretion? 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.
Force majeure option — proportional allocation? It might be a challenge — or simply impracticable — to assess the extent of a provider's compliance with the Proportionality configuration for this Option.
3.5.2.7. Option: Mitigation and Remediation Discretion
When this Option is agreed to:
No party is obligated to make any particular efforts to mitigate or remediate the effects of the invoked force majeure.
If a party does try try to mitigate or remediate the effects of force majeure, that party's efforts in that regard will be for that party's own benefit only.
Comment
Force majeure option — mitigation vs. remediation: 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 Clause 7.7 (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).
3.5.2.8. Option: Extension of Expiring Right
When this Option is agreed to: If one or more properly-invoked force majeure situations make it impracticable or impossible for the invoking party to timely exercise a right under the Contract, then the invoking party's time for exercising that right will be deemed extended for the duration of the resulting delay.
Comment
Force majeure option — extension of expiring right; 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).
3.5.2.9. Option: Economic Force-Majeure
When this Option is agreed to: If 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.
Comment
Force majeure option — economic factors: 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 examples of contract clauses with "economic force-majeure" clauses, see LawInsider.com.
When this Option is agreed to: Each party must promptly alert each other party if the former concludes that a substantial risk exists that it might have to invoke force majeure.
Comment
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.
3.5.2.11. Option: Effect of Subcontractor Failure
If this Option is agreed to, it will apply if:
a party does not timely perform its obligations (or exercise its rights) under the Contract; and
the party's failure to do so was due to a failure of a subcontractor or supplier of the party.
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:
The failure by the subcontractor or supplier must otherwise qualify as one or more force-majeure situations under the Contract; and
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.
Comment
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."
3.5.2.12. Option: Detailed List of Possible Force-Majeure Events
When 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 Contract 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.
Comment
Force majeure option — detailed "laundry list": Some drafters like to list specific types of events that can excuse non-performance. (Your author generally doesn'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 to include such a "laundry list" in the Contract, as discussed in a footnote at section [BROKEN LINK: fmajdefn].
Why bold face type? Some of the above items are in bold-faced type because they are not-uncommonly subject to negotiation.
Acts of God? The above list does not include the so-called "act of God" because of the vagueness of that term.
3.5.3. Force majeure: Additional reading
Some procurement organizations feel they can push around their suppliers without consequence. From April 2022:
Stellantis' new purchase contracts declare "all future events are deemed foreseeable" by suppliers, yet require price reductions when any savings are found.
Noting this Stellantis move, a Harvard Business School professor (in 2022) 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. 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.
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 below.
3.6.1. Definition: "Agreed Forum" — when would this Clause come into play?
This Clause presupposes that the Contract clearly specifies one or more particular forums for litigation (each, an "Agreed Forum").
Comment
Note: 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 Common Draft Forum Selection clause."
Caution: See the commentary at 3.6.9.1 and 3.6.9.2 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 3.6.9.16.
3.6.2. Definition: "Action" — to what disputes does this Clause apply?
For purposes of this Clause, the term "Action" refers to a lawsuit or other form of contested action in any dispute arising out of the Contract.
Comment
The choice of "arising out of the Contract" is intentional because it's more limited than "relating to the Contract," 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. 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).
3.6.3. Any Action may be brought in the Agreed Forum
A party to the Contract may bring an Action in the Agreed Forum, regardless where the defendant is geographically located: (i) to the extent not prohibited by law, and (ii) except as otherwise required by an arbitration provision in the Contract (if there is one). 3.6.9.6
Comment
Agreed Forum prohibited by law? The law might regulate forum-selection provisions in particular circumstances. Example: Under a California statute (Cal. Code Civ. Pro. § 116.225), "An 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.)
3.6.4. May an Action may be brought elsewhere?
Any party may bring an Action in another forum unless the Contract clearly specifies otherwise — for example, by stating that the Agreed Forum is exclusive.
3.6.5. What if the Contract does say that the Agreed Forum is exclusive?
If the Contract unambiguously states that the Agreed Forum is exclusive, then:
No party is to bring an Action concerning the dispute in question in any forum other than the Agreed Forum; and
No party is to seek to transfer an Action from the Agreed Forum if brought there.
Comment
Motions to transfer: Subdivision c is adapted from a suggestion at the lawyers-only redline.net forum. Motions to transfer are not uncommon 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).
If a party "Alpha" does either of the things specified in section 3.6.5and another party "Bravo" files a motion (or other proceeding) to transfer, dismiss, or enjoin the proceeding (or in opposing the transfer request, then:
Alpha is to reimburse Baker for Baker's reasonable attorney fees and court costs in that motion; and
Alpha's reimbursement obligation under subdivision d.1 will apply even if Alpha ends up being the prevailing party in the proceeding.
3.6.7. This Clause won't overrule an arbitration agreement.
Even if the Contract designates an Agreed Forum, that does not mean that a party may bring an Action in the Agreed Forum if the Contract requires the dispute in question to be resolved by other means, such as, for example, arbitration.
Comment
As discussed at 3.6.9.7, 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.
3.6.8. Survival: This Clause will still apply after termination.
In case of doubt, this Clause will continue in effect even if the Contract is terminated or expires, and whether or not the Contract includes other survival provisions. 5.1
3.6.9.1. 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 Dynamic CRM Recruiting (2022), in which 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).
3.6.9.2. Caution: What if there's no federal court there?
Example:CH2M Hill (2019): The contract in question required litigation to be in Linn County, Oregon. When one party sued the other party, 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).
Drafting 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.
3.6.9.3. Caution: "shall be subject to" might mean exclusivity
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.
3.6.9.4. 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 in Taylor v. Eastern Connection Operating, Inc., discussed at 3.7.4.
3.6.9.5. 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.
3.6.9.6. 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.
3.6.9.7. 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 Clause 8.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 is 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 alsoGoldman, 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 2015 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 alsoUBS Sec. LLC v. Allina Health Sys., No. 12–2090, 2013 WL 500373 (D. Minn. Feb. 11, 2013) (following Carilion Clinic). /
• Likewise, in Mohamed (2016), 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).
3.6.9.8. Caution: Forum selection could preclude administrative action
Example: In Nippon Shinyaku (2022), a Federal Circuit decision: See Nippon Shinyaku Co. v. Sarepta Therapeutics, Inc., 25 F.4th 998 (Fed. Cir. 2022) (reversing and remanding denial of preliminary injunction).
• 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.
(This was the opposite result from that in the 2021 Kannuu v. Samsung case discussed at 3.6.9.17.)
3.6.9.9. 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.
3.6.9.10. 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).
3.6.9.11. Pro tip: Advise a client in writing about forum selection?
Example: In a 2023 Texas supreme court decision, a Texas-based law firm and one of its partners were sued for malpractice by a former corporate client for allegedly failing to seek some $1 million in damages in a motion for default judgment in a previous lawsuit against a former employee of the client. Based on the facts recited in the supreme court's opinion, it seems entirely possible that that the law firm made a particular tactical decision in litigation — quite possibly with the then-client's approval — but apparently the firm did not protect itself by documenting the same, for example in an email to the client. See USA Lending Group, Inc. v. Winstead PC, 669 S.W.3d 195 (Tex. 2023) (reversing dismissal for failure to state a claim).
If the law firm had emailed the client to document that the firm had made such a tactical decision — especially if the email also documented that the firm had consulted the client in advance about the decision — then the firm's prospects in a malpractice lawsuit would have been enhanced considerably.
Example:Wright (2016): 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
3.6.9.12. 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).
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 3.7.10 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.
3.6.9.13. 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).14
3.6.9.14. 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.
3.6.9.15.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 Vayu, Inc. (2023), in New York's highest court; the facts of that case aren't important here, other than that extensive litigation was required to address the forum question.15
3.6.9.16. 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: • One party "Alpha" was using a contract patched together by business people. Alpha sent the contract to a prospective customer that had significantly-more bargaining power. • Alpha's contract form included a forum-selection provision requiring all litigation to take place exclusively in Alpha's home city. • 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. That wouldn't have been good for Alpha, because litigating in the other city would have been costly and inconvenient.
Fortunately, the customer's lawyer went along with the suggestion by Alpha's lawyer to 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 Alpha, because: • Without a forum-selection stipulation, the customer likely would not have been able to sue Alpha in the customer's home city at all, because the courts in that city would almost certainly not have had personal jurisdiction over Alpha. (Of course, that wouldn't have stopped the customer from filing suit anyway, which would have meant that Alpha would have to spend money to get the case dismissed or transferred.) • In contrast, Alpha would have been able to sue the customer in Alpha's home city, because the customer had significant operations in that city. The customer's lawyer apparently didn't tumble to the fact that he was making a potentially-big concession.
3.6.9.17. Why only "arising out of the Contract"?
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 Clause.
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."16
But: An even-broader forum selection provision led to the opposite result, as discussed at 3.6.9.8.
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.
3.6.9.18. 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).
3.6.9.19. Would a forum-selection clause imply a choice of law?
For extensive discussion and research notes, see Okoli (2024).17
3.6.9.20. A court might not honor a choice of an "improper" forum
In many American states, a 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 does not meet the statutory requirement, then a court might refuse to enforce the forum selection. Example: This happened in a North Caroline 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).
3.6.9.21. 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 California appeals court denied mandamus to compel dismissal of a shareholder lawsuit, where:
the defendants' motion to dismiss was based on a forum-selection clause designating Delaware's Chancery Court, but
the plaintiffs would not have had the right to a jury trial there:
The defendants sought dismissal of the case based on mandatory forum selection clauses in EpicentRx’s certificate of incorporation and bylaws, which designated the Delaware Court of Chancery as the exclusive forum to resolve shareholder disputes like the present case.
The trial court declined to enforce the forum selection clauses after finding that litigants do not have a right to a civil jury trial in the Delaware Court of Chancery and, therefore, enforcement of the clauses would deprive EpiRx of its inviolate right to a jury trial in violation of California public policy.
We agree with the trial court that enforcement of the forum selection clauses in EpicentRx’s corporate documents would operate as an implied waiver of EpiRx’s right to a jury trial—a constitutionally-protected right that cannot be waived by contract prior to the commencement of a dispute.
Thus, we conclude the trial court properly declined to enforce the forum selection clauses at issue, and we deny the defendants’ request for writ relief.
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 AutoNation, the Texas supreme court's decision produced a very different outcome:
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:Franchise investment law: 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:Usury law: 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 2.11.6.2.)
3.6.9.22. Legal background
Example: 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."18
Example: In Rivera (2009), the First Circuit 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.19
Example: Likewise, state courts in the U.S. generally honor forum-selection provisions; for example, in Paul Business Systems (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."20
3.6.9.23. "Closely-related" non-signatories might be bound
Example: As explained by the Fifth Circuit in Franlink, Inc. (2022): 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."21
Counterexample: In Rieder (2020), 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.22
3.6.9.24. Idaho's idiosyncratic approach ….
Example: In T3 Enterprises (2019), a contract expressly required arbitration in Dallas, but the Idaho supreme court held that the contract's choice of Texas law required arbitration in Idaho.23
Example: And later, in Off-Spec Solutions (2021), the Idaho 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.24
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.25
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.
3.6.9.25. 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.26
3.7. Governing Law
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."
This Clause is designed the case where the Contract clearly states that the law of a particular stated location or jurisdiction will apply, govern, or similar wording — all are referred to here as the law that will "apply" or "govern."
3.7.1.2. What substantive law will apply?
On substantive matters, the "Governing Law" will be the substantive law that applies in the stated geographic jurisdiction:
as applied in disputes, between residents of that jurisdiction, concerning matters occurring entirely within that jurisdiction,
without regard to that jurisdiction's choice-of-law rules; for emphasis, the parties intend here to rule out application of the legal doctrine of renvoi. 3.7.14
3.7.1.3. What types of dispute will the Governing Law govern?
The parties intend for the Governing Law to apply in any dispute arising out of or relating to: 3.7.6 (i) the Contract itself, and/or (ii) any transaction or relationship resulting from the Contract.
Comment
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), citingBlinco v. Green Tree Servicing LLC, 400 F.3d 1308, 1310 (11th Cir. 2005).
3.7.1.4. What procedural law will govern lawsuits and other disputes?
The relevant procedural law is to be determined as provided by the Governing Law.
Comment
Substantive vs. procedural law: 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).
3.7.2. Choose New York law? California law? Delaware 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.
3.7.3. 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 one case, the state supreme court quoted an oft-cited chancery-court decision:
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.
3.7.4. 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).).
3.7.5. 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.
3.7.6. Limit the choice to "interpretation" or "enforcement"?
Section [BROKEN LINK: gov-law-arise] applies broadly to "any dispute arising out of or relating to" 9.5 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. In that case, an arbitrator held that, because the contract's choice-of-law provision didn't apply to noncontract claims, the Pennsylvania statute was 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 3.7.15, a Maine-based sales representative's employment agreement included a California choice-of-law provision — but that provision stated only that "[t]he terms of this [agreement]" are to be "governed by and construed and enforced" under California law. When the company failed to pay commissions on certain sales, the sales rep's lawsuit against the company included 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, and therefore the sales rep was entitled, not only to commissions, but also to treble damages and attorney fees under a Maine statute. Dinan v. Alpha 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)).
3.7.7. 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, your author 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 3.7.12, 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
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.
3.7.8. Choose the law of the agreed forum?
If the parties are also going to agree to a choice of forum — about which see 3.6 — 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 6.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.
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.)
3.7.10. 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 3.6.9.12 concerning forum-selection clauses to specify litigation in the UK.
3.7.11. Caution: China-involved contracts could be a special case
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.
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
3.7.13. 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 3.7.12 ) 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 3.7.15 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).
3.7.14. No renvoi – what's that?
Section [BROKEN LINK: GovLawWhich] is intended to rule out applying the doctrine of renvoi. To illustrate how renvoi works, let's consider the following hypothetical example:
Two giant oil companies company — let's call them Flexxon and Shelron — each have operations in New Orleans but are headquartered in Houston.
The two companies enter into a contract under which they will explore for oil.
The contract is negotiated in Louisiana, and all the work under the contract is to take place in Louisiana.
But the contract between the companies calls for Texas law to apply, because Flexxon and Shelron 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 section [BROKEN LINK: GovLawWhich] 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").
3.7.15. 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. Alpha 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 3.6.9.24.
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.
The court affirmed summary judgment that Wyoming law did indeed apply.
3.7.16. … 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.)
3.7.17. 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), citingMinn. Stat. § 325E.37
3.7.18. Some governing-law examples in the wild
Example: In Cardoni (2015), 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 (2001), 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 (2014): "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).
3.7.19. 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 6.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.
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."
As discussed in the commentary below, in many situations the law presumes that a particular party, by entering into a contract, implicitly makes certain promises
Each party (sometimes referred to as "you") DISCLAIMS11.11 any and all implied warranties, representations, 3.17 conditions, and terms of quality 3.8.5 (each, an "Implied Warranty") for goods 3.8.2 or services 3.8.4 to be provided by or on behalf of that party under the Contract, except as otherwise stated in the Contract.
3.8.1.2. How broad is this disclaimer?
This Clause applies whether or not any purported Implied Warranty is claimed to have arisen:
by law;
by an alleged custom, practice, or usage in the trade; and/or
by an alleged course of dealing or performance by the parties themselves.
3.8.1.3. What are some examples of things disclaimed?
Here are some (non-limiting 7.32) Implied Warranties — not express ones —that are disclaimed by this Clause:
merchantability (as defined in UCC § 2-314) of goods;
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;
quiet enjoyment;
noninfringement (but any express warranty of noninfringement in the Contract would be unaffected);
absence of viruses or other malware in software;
results;
workmanlike performance or -effort 3.8.4(but see any express warranty of performance, such as that of 4.11 if applicable);
quality;
non-interference;
accuracy of content;
correspondence to description (an English formulation, roughly analogous to the implied warranty of merchantability).
3.8.1.4.Express warranties not disclaimed
For emphasis: The parties' agreement to this Clause does not disclaim any express warranties, representations, or other factual commitments that are clearly stated in the Contract.
Comment
Unfortunately, contract reviewers sometimes need to be reminded that a disclaimer of implied warranties doesn't affect any express warranties in the Contract.
In fact, more than once, when representing a supplier, your author has 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 ….)
3.8.1.5. Implied warranties of title not disclaimed
For emphasis: Neither does the parties' agreement to this Clause disclaim any implied warranty of title to tangible goods, whether under Uniform Commercial Code § 2-312 or otherwise.
Comment
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, of course; as an 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 Clause.
3.8.2. 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.
3.8.3. 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.)
3.8.4. 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 Clause 4.13) 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 3.8.
3.8.5. Watch out for special disclaimer requirements in England, etc.
The disclaimer of implied conditions and terms of quality, at section [BROKEN LINK: impl-discl-uk], is a nod to the law in England, Wales, and Northern Ireland (not "UK law"; see the commentary at 3.6.9.12).
3.8.6. Some services might come with implied warranties
This is discussed in the commentary at 4.11 (performance standards for services).
3.8.7.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 3.15.6 concerning waivers of reliance on representations).
3.8.8. 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).
3.8.9. 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.
3.8.10. 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 3.8.2) for any consumer product if the company offers a written warranty for the product or sells a service contract for it.
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."
This Clause will apply whenever the Contract 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.
Comment
Definition of indemnify: The verb indemnify means to reimburse for losses and/or expenses resulting from one or more specified categories of event; the noun form is indemnity. See generally Indemnify, Black's Law Dictionary 918 (11th ed. 2019). Relatedly: Hold harmless is generally regarded as a synonym for indemnify, as discussed in the commentary to Clause 7.31.
3.9.1.2. Is there a limit on the amount of an indemnity obligation?
The Payer's financial obligation for indemnity under the Contract is not limited to a particular amount unless the Contract clearly says so.
Comment
No cap on indemnity liability: 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).
3.9.1.3. Must the Payer also defend the Beneficiary?
If the Contract requires the Payer to indemnify the Beneficiary for losses and expenses resulting from specified third-party claims; but the Contract is silent about whether the Payer must defend the Beneficiary against such claims; then the Payer must provide the Beneficiary with a defense against the claim, in accordance with Clause 3.4.
Comment
Obligation to defend against indemnified claims? If a contract requires A to indemnify B against a third-party claim, then the law, especially in California, might require A also to defend B against the claim — even if the agreement didn't expressly include such a requirement. But: 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), citingMontrose Chemical Corp. v. Superior Court, 6 Cal. 4th 289, 298, 861 P.2d 1153 (1993).
On the other hand, 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 your author's 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).
The Payer is not required to indemnify a Beneficiary for losses and/or expenses that result from the Beneficiary's own negligence or gross negligence, unless:
the Contract expressly and conspicuously so states; and
applicable law does not prohibit such indemnity.
Comment
Important for students: See the following extended discussions:
(for Texas students) the Texas Oilfield Anti-Indemnity Act: 3.9.12
3.9.1.5. Must first-party claims be indemnified?
For the avoidance of doubt: An indemnity obligation does not obligate the Payer to indemnify the Beneficiary for the Beneficiary's own claims against the Payer unless the particular indemnity- or defense language clearly specifies otherwise.
Comment
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. Extensive case-law citations can be found in the parties' briefs in an unsuccessful petition to the Texas in Claybar v. Samson Exploration LLC, No. 09-16-00435-CV (Tex. App.—Beaumont 2018, pet. denied).27
3.9.1.6. The Beneficiary must try to mitigate its harm
The Payer is not required to indemnify a Beneficiary for harm to the extent that both of the following are true:
the Beneficiary knew or should have known of the possibility of the harm before the harm occurred, and
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 is not necessarily clear on that point, as discussed in the commentary to Clause 3.9.1.12.
3.9.1.7. The Payer is to promptly pay indemnity obligations
The Payer is to pay each covered loss and expense — or if applicable, reimburse the Beneficiary for the loss or expense — promptly after the Beneficiary presents the Payer with:
a written request for payment or reimbursement, together with
reasonable supporting evidence documenting the existence, nature, and amount of the covered loss or expense. 2.9
Comment
This is intended to discourage a Payer from dragging its feet, possibly in an attempt to gain leverage over the Beneficiary.
3.9.1.8. The Payer may audit indemnity supporting evidence
The Beneficiary is to allow its supporting evidence to be audited (if the Payer asks) in accordance with Clause.
Comment
The supporting-evidence requirement and audit right is basically an anti-fraud measures, as discussed in the commentary to Clause (audits).
3.9.1.9. Are the Beneficiary's indemnity obligations covered\, too?
The Payer is not obligated to defend or indemnify the Beneficiary against any claim, loss, or expense if the same arises only because the Beneficiary is obligated to indemnify and/or defend a third party.
3.9.1.10. The Beneficiary's serious misconduct is excluded
The Payer is not obligated to indemnify the Beneficiary for losses or expenses resulting from the Beneficiary's gross negligence 7.30 or willful misconduct. 7.53
Comment
This exclusion would probably be the default mode under the law in most U.S. jurisdictions, on the basis that allowing a party to shuck off liability for its own willful misconduct would create moral hazard and be against public policy.
3.9.1.11. The Beneficiary need not prove that the Payer was at fault
For emphasis: The Beneficiary is not obligated 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 negligence or other fault.
Comment
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).
3.9.1.12. "Consequential damages" are not indemnifiable
The Payer is not obligated to defend or indemnify the Beneficiary for so-called consequential damages 3.2.2 — 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 unless the Contract expressly specifies otherwise.
Comment
This exclusion is designed 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 Clause 3.2.
(The next section, on foreseeability, addresses a related topic.)
3.9.1.13. Unforeseeable losses are not covered
The Payer is not obligated to defend or indemnify the Beneficiary for unforeseeable losses unless the Contract clearly says otherwise for the particular class of loss.
Comment
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
3.9.1.14. Would an indemnity obligation ever expire?
If clearly so stated in the Contract or in applicable law: The Payer is not obligated to defend or indemnify the Beneficiary in response to any notice or request for the same that is received by the Payer on or after the stated time.
Comment
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 more detail in Kirsch & Brodeur (2006). See 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).
3.9.1.15. Must the Payer carry supporting insurance coverage?
Unless the Contract clearly provides otherwise, the Payer may decide, in the Payer's sole discretion, whether to carry insurance to cover the Payer's indemnity obligation(s) under the Contract.
Comment
Pro tip:Any time that you're drafting an obligation for another party to indemnify your client, consider whether to include a contractual requirement that the other party must also obtain insurance to cover the indemnity obligation — otherwise, if and when the time comes, the other party might not have the financial wherewithal to comply with its indemnity obligation.
The reverse is also true: If your client is agreeing to indemnify another party, then consider advising the client to check whether the client's insurance coverage is sufficient to support the indemnification obligation. (Ideally, you'll provide that advice in writing, e.g., in a quick email, so that you can demonstrate later than you raised the issue with the client.)
Caution: As 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" — 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).
3.9.1.16. Is there a deadline for requesting indemnity?
The Contract may state a deadline for the Beneficiary to notify the Payer of a potentially-indemnifiable claim — if the Beneficiary misses a clearly-stated such deadline, then:
the Payer is not obligated to defend or indemnify the Beneficiary in respect of that claim; and
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).
3.9.2. "I&I" - insurance for indemnity obligations?
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, 3.10 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.
3.9.3. 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).
3.9.4. 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.
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. See Frittelli, Inc. v. 350 North Canon Drive, LP, 202 Cal. App. 4th 35, 48 (2011) (cleaned up; citations omitted, extra paragraphing added).
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).
3.9.6. 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.
3.9.7. 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 Argon might get sued by a third party because of something that The Other Side might have done (or failed to do).
For example, it might make sense for Argon to ask for an indemnity obligation if Argon 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, Argon might want The Other Side to agree to a defense-and-indemnity obligation to protect the client from third-party claims arising from The Neon'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 or referral source that agrees to "rep" a manufacturer's products might want the manufacturer to agree to defend and indemnify the first party against warranty- and product-liability claims.
3.9.8. 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. 10.4
(Caution: The express-negligence rule might well apply; see 3.9.5.)
3.9.9. 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).
3.9.10. 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: 3.9.2
… 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).
3.9.11. Special case: Construction-contract indemnity statutes
[TO COME]
3.9.12. 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 3.9.5.
3.10.1. Sample language favoring a customer or client
Here is 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.
[Author's 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. [Author's 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. [Author's note: This could be significant in Texas cases, as discussed at 3.9.12 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.
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). [Author's 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. [Author's 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. [Author's 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. [Author's 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 3.10.3 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. [Author's 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. [Author's note: See the note above about checking for outdated form versions.]
3.10.2. How insurance defense-coverage disputes work
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.
3.10.3. Subrogation - what is it?
Author's 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).
Author's 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.
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
3.11.2. Clause text
When this Clause is agreed to in writing:
3.11.2.1. How will this Clause apply?
Except as otherwise stated, this Clause will govern all claims "relating to" 9.5 the Contract — which is intended to be a broad term, encompassing a very-wide range of claims.
3.11.2.2. What is the deadline for commencing a lawsuit?
For any claim relating to the Contract, the claimant has one year after "accrual" of the claim the specified time after the claim "accrues," as stated in section 3.11.2.5, in which to "commence" a lawsuit, an arbitration (if agreed to), or other action.
Comment
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.)
3.11.2.3. What if the claimant misses that deadline?
If the claimant does not commence the action within the agreed time, then the claimant is conclusively deemed to have *WAIVED the claim.
If the time specified in the Contract for bringing a lawsuit or arbitration is shorter than the time allowed by applicable law, then that time will be automatically extended to the minimum allowable time.
Comment
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.
3.11.2.5. "Accrual": When would the clock start running on the deadline?
Except as otherwise stated in this Clause, 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 does not then even suspect that it might have a claim.
Comment
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).
3.11.2.6. Would the "discovery rule" extend the deadline?
If the Contract clearly states that the "discovery rule" will apply for one or more categories of claim, then such a claim will not accrue until the time that the claimant first suspected — or reasonably should have suspected — that the claimant might have grounds to make the claim.
Comment
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 inJolly 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 3.11.3 below.
3.11.2.7. Survival
This Clause will survive termination or expiration of the Contract.
Comment
Concerning survival clauses generally, see Clause 5.1.
3.11.3. 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.
(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 3.18.7.)
• 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
3.11.4. 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 3.17) 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 25.5.
3.12. Limitations of Liability General Provisions
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.
This Clause will govern whenever the Contract includes one or more "limitations of liability," namely any one or more of the following (without limitation):
a cap on damages and/or other monetary relief, 3.3 including but not limited to attorney fees; 3.1
an exclusion of one or more specified types of monetary relief, including but not limited to consequential damages, 3.2 when applicable; and
an exclusion or limitation of any other types of remedy, including but not limited to injunctive relief. 8.29
3.12.1.2. Which party or parties are protected by this Clause?
Unless the Contract clearly states otherwise, each limitation of liability in the Contract will apply to each of the following (each, a "Protected Person"):
each signatory party to the Contract;
that party's "affiliates," as defined in U.S. Securities and Exchange Commission regulations; and
the officers, directors, managers, members, employees, shareholders, and other individuals holding similar positions, in each organization within the scope of this section [BROKEN LINK: lim-liab-per].
Comment
Employee protection: This section explicitly states that individual employees (and others) are protected by any limitations of liability in the Contract, 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 (!) — as discussed in more detail at 8.28.
3.12.1.3. What forms of relief are covered by this Clause?
Unless clearly stated otherwise, each limitation of liability in the Contract (if any) applies to all claims for relief:
regardless of the label given to the relief, such as, for example, "consequential damages" 3.2 "special damages" or "exemplary damages" or "punitive damages" or "disgorgement" or "attorney fees" or "costs"; and
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.
Comment
Note: In Clause 3.3 (damages caps), section 3.3.1.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) (
3.12.1.4. Limitations of liability are "material"
Each limitation of liability in the Contract is a fundamental part of the parties' bargain; in deciding to enter into the Contract on the agreed terms, each party has relied on the limitations of liability stated in the Contract.
Comment
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).
3.12.1.5. No party is to seek inconsistent relief
Each party specifically agrees never to seek relief that is inconsistent with any limitation of liability stated in the Contract:
even if some or all agreed limited remedies failed of their essential purpose; 3.12.2 and
even if the liable party and/or its agents knew, at the relevant time, of special circumstances 3.2 relating to the claim, for example, circumstances giving rise to the possibility or even the high probability of such damages.
Comment
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 3.1.9.)
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).
3.12.1.6. Each party assumes other associated risks
Each party KNOWINGLY ASSUMES THE RISK that it might suffer damages in excess of amounts excluded, capped, or otherwise limited by the Contract.
Comment
"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.
3.12.2. If limited remedies were to fail: Then what?
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").
3.13.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).
3.13.1.1. 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.).
3.13.1.2. 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 9.1).
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).
3.13.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 9.1.
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).
3.13.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 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).
3.13.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.
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), quotingFPL 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.
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 3.17.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."
3.13.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.
3.13.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.
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.
3.13.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).
3.13.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).
3.13.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.
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).
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 (PrindleLaw.com) (undated).
Caution: This waiver of California law appears in some contracts, but the author has not 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.
3.14.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 Ward v. Shelby County [TN] No. 22-6054 (6th Cir. Apr. 11, 2024): "Any and all claims" means just that; there's no need to enumerate them. "
3.14.4.Advance releases might have special rules
In Texas, advance releases of negligent conduct must follow the "express negligence rule," that is, an advance release must be both express and conspicuous.
"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 (Tex. 2023).
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. (Tex. 2023).
3.14.5. Caution: Releases might wipe out unintended legal rights
Introduction: 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: Read 3.17 (basics of reps and warranties), especially the discussion of the "Hill of Proof" at 3.17.2.
Unless limited by section 2 below: When a party "RP" (for "Representing Party") makes a representation, RP thereby asserts the following:
that, so far as RP is aware 3.15.9 at the time RP makes the representation, the represented fact is true; and
that RP has a reasonable basis for making the representation as stated.
Comment
Reasonable basis: 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 3.15.9.
3.15.1.2. May others rely on the representation?
Whenever RP represents the truth of a matter in the Contract itself, RP thereby acknowledges 7.1 that that one or more other signatory parties to the Contract are rebuttably presumedto reasonably rely — for a serious purpose — on both of the following:
RP's representation itself; and
RP's assertion about RP's having a reasonable basis for the representation.
Comment
Rebuttable presumption: 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.
Reliance: If the parties hadn't intended a representation to be relied on, presumably they wouldn't have stated the representation in the Contract itself. (The reliance issue is discussed in more detail at 3.15.3.)
Reliance for a serious purpose: This section 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).
3.15.1.3. Can a representation be limited?
A representation may limit one or more of:
the represented fact;
RP's basis for the representation; and/or
the signatory parties to the Contract that are entitled to rely on those things.
3.15.1.4. What if a representation is made "to" a specified party?
Defining by example: 30.10.2 If a representation is phrased in terms similar to, "Alice represents to Bob," then only Bob may rely on the representation.
3.15.1.5. New York law will govern this Clause
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 other respects.
Comment
This section is informed by New York law (discussed at at 3.17.2), which is specified as a uniform gap-filler. The parties can of course specify a different law in the Contract. (See the commentary at 3.7.19 concerning the notion of choosing a law to govern one specific section of a contract.)
3.15.2. 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 3.17.2 above.
( The "past or present fact" formulation is suggested by Professor Tina Stark in her highly-regarded Drafting Contracts textbook.)
3.15.3. Extra proof requirements over warranties
Example: The Second Circuit explained that to prove misrepresentation:
Under New York law, the plaintiff must allege that[:]
(1) the defendant had a duty, as a result of a special relationship [i.e., privity of contract or something close to it], 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), quoted inKortright 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) (cleaned up, citations omitted, emphasis and extra paragraphing omitted, bracketed italicized material added).
As seen on the upper left side of the Hill of Proof (see 3.17.2): If Fred wants to sue Ginger for misrepresentation:
1. Fred must show that he in factrelied 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).
2. Fred must also show that his reliance on Ginger's representation was reasonable under the circumstances — 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, however, 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).
3.15.4. 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
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).
3.15.5. Proof requirements for negligent misrepresentation
Fred might settle for proving negligent misrepresentation by Ginger; 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.
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.
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).
3.15.6. 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 8.57: Reliance Waiver Clause.
3.15.7. 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.
[ x ] Ginger will pay Fred $1 million.
[ ] Ginger represents that she will not use Fred's confidential information except as stated in the Contract.
[ x ] Ginger will not use Fred's confidential information except as stated in the Contract.
(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").
3.15.8. 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.
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 3.12
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.”
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).
3.15.9. Pro tip: Disclaim investigation of representations?
Clause 3.15 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 …." 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).
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 3.15, 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.")
3.15.10. 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.
Each partyrepresents, to each other party, that the statements in this Agreement are true.
Comment
A. This Agreement provides a "canary in the coal mine" to help the parties identify (and, ideally, address) certain problems before they sign the Contract.
B. Note that the statements in this Agreement are representations, not warranties; see generally See the discussion at 3.17. for a discussion of the differences.
C. Some strategically-important types of agreement include more-detailed representations and warranties of this general kind. See, for example, the merger agreement between United Airlines and Continental Airlines, at https://tinyurl.com/UAL-CAL (SEC.gov), from which some of the concepts in this Agreement are drawn.
3.16.2. No known conflicts
Each party represents, to each other party, that — so far as the representing party is aware — the representing party:
is not a party to any problematic (as defined below) agreement with any third party;
is not the target of any problematic claim, in litigation or otherwise; and
is not subject to any problematic injunction, judgment, or regulatory restriction.
Here, 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 any party's (i) performance under the Contract or (ii) exercise of its rights under the Contract.
As an example: One possible problematic claim would be that a party's performance under the Contract would constitute tortious interference, on the part of any party to the Contract:
with a contract between the representing party and any third party, nor
with the prospective economic advantage of any third party.
Comment
See generally the Wikipedia discussion of tortious interference with contractual relationship or prospective economic advantage.
A tortious-interference lawsuit can have catastrophic results. Example: Oil giant Texaco was hit with a jury verdict of more than $29 billion (2025 dollars) for tortiously interfering with what the jury and the courts found to be a binding memorandum of understanding between Pennzoil and Getty Oil. This led to Texaco's having to file for bankruptcy protection, and ultimately settling for nearly $10 billion (ditto). The case ultimately settled for more than $8 billion in 2024 dollars, reportedly making Pennzoil's lead counsel Joe Jamail a billionnaire because of his contingent-fee agreement. See Texaco, Inc. v. Pennzoil Co., 729 S.W.2d 768 (Tex. App.—Houston [1st Dist.] 1986, writ. ref’d n.r.e.); Tamar Lewin, Pennzoil-Texaco Fight Raised Key Questions, N.Y. Times, Dec. 19, 1987.
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 (3.15) or warranty (3.18) basically does two things:
It sets out a particular factual state of affairs that one party (or both) wants to be true; and
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.
3.17.2. Ninja Warrior: Two paths up "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 Fred must "climb" in making his claim(s) against Ginger:
– As plaintiff, Fred starts out at the bottom of the Hill of Proof, equidistant between the "representation" claim on the left side of the hill and the "warranty" claim on the right side.
– As Fred clambers up the Hill of Proof, he tries to "hit" various evidentiary checkpoints along the way, with his left hand (on the representation-claim side) or his right hand (on the warranty-claim side).
– 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; for citations and additional discussion, see the respective discussions of representations (3.15) and warranties (3.18).
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; for an earlier piece on the same subject by Stark, also responding to an Adams essay. See Tina Stark, Nonbinding Opinion: Another view on reps and warranties, Business Law Today, January/February 2006.
3.17.3. Strategy: Offer a warranty only?
Suppose that Ginger only warranted a fact, but she did not represent it. For example, suppose that Ginger sold her car to Fred, and she suspected, but 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 Fred's remedy to Ginger’s reimbursing Fred for up to, say, $200 in repair costs.
In that situation, at trial Fred would be trying to climb the right side of the above Hill of Proof (3.17.2). The only three evidentiary checkpoints that Fred would need to reach, in reaching out with his right hand toward that side of the Hill, would be the following:
Proof that 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”;
Proof that Ginger's statement was false — her car, as delivered to Fred, turned out to need some significant work; and
Proof that Fred incurred damages as a result, i.e., repair costs.
If, at the trial, Fred can successfully get past those three evidentiary checkpoints on right side of the Hill of Proof, then he will be entitled to recover warranty damages (generally, benefit-of-the-bargain damages) for 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.
3.17.4. Strategy: 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 Fred would have to hit all six checkpoints on the left side of the Hill of Proof (3.17.2) to recover damages from Ginger; the first three alone, on both the left- and right sides, would not be enough — even though the first three would be enough if Ginger had warranted the car’s good condition.
3.17.5. Strategy: Ask forboth a rep and a warranty?
But now suppose that Ginger both represented and warranted the statement of fact, i.e., that her car was in good working order. And then suppose that Fred successfully hits the first three evidentiary checkpoints on the left- and right sides of the Hill of Proof (3.17.2). In that situation, Fred can try to keep going to hit still more checkpoints on the left side of the Hill, namely:
Proof that Fred in fact relied on Ginger's representation — that will probably be almost a given, of course, by virtue of the representation’s being expressly set forth in the contract;
Proof that Fred's reliance was reasonable — ditto, although Ginger could try to prove that Fred's reliance was not reasonable under the circumstances; and
Proof that Ginger intended for Fred to rely on Ginger's representation — ditto; and
Proof that Ginger made the false representation intentionally (or possibly, in some jurisdictions, was negligent or reckless in doing so). This is usually the biggie, from a proof perspective.
If Fred can successfully hit all of these additional evidentiary checkpoints on the left side of the Hill of Proof (and if 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.
At trial, Fred might well assert both breach of warranty and fraudulent inducement or negligent misrepresentation. That way, if Fred proves unable to show scienter on 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 would fail, but he might still be able to win on his warranty claim.
3.17.6. Pro tip: Which is better for your client?
So, here's a rule of thumb:
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.
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 3.17.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 3.15.8 — 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!"
3.17.7. Buy insurance for representations & warranties?
3.18.1. A warranty is basically a conditional covenant
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 —
the warranting party will take one or more actions clearly specified in the contract — if any; or
if the contract doesn't specify any 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. In subdivision 2, the "foreseeable, ordinary-course economic losses" phrase draws on the well-known English case of Hadley v. Baxendale, discussed in the commentary to Clause 3.2.
Like a representation, 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 3.17).
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 (3.3.7).
3.18.2.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 3.17.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).
3.18.3. For warranties, reliance and scienter need not be proved.
As seen on the right side of the Hill of Proof (3.17.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 ….
Caveat: A different situation might be presented if — before the contract was signed — the warranting partydisclosed 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).
3.18.4. 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.
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.
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).
3.18.6. 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 8.66.
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 …."
3.18.7. 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, 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.
And in a decision 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).
3.18.8. 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 3.8.2) for any consumer product if the company offers a written warranty for the product or sells a service contract for it.
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."
3.18.9. 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 3.17.6 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 3.18.7.
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, 10.4 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.
3.18.10. Warranty: Is it a "guarantee"?
Colloquially the terms "warranty" and "guarantee" are alike, but technically there are some differences; see the commentary accompanying 2.10: Guaranty Protocol Clause.
If this Clause is agreed to, a party clearly indicated in the Contract (referred to for convenience as the "Provider") is to correct defects in goods or services, • provided to another party (the "Customer"), • by the Provider and/or by a third party, • under the Contract.
Comment
A. 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 Clause sets out a fairly-standard "Three Rs" approach — repair, replace, or refund — for dealing with (purported) defects in goods or services.
B. "by a third party": The allegedly-defective goods or services might actually have been provided by a party other than the Provider, for example (hypothetically) by a reseller of the Provider's goods. Or, the "Provider" might be a service company engaged by a manufacturer to make repairs on the manufacturer's products.
4.1.0.2. Definition: What counts as a "defect"?
For purposes of this Clause, the term "defect" (whether or not capitalized) refers to any failure, by one or more deliverables and/or services provided under the Contract, to comply with agreed written specifications.
Comment
Agreed written specifications could be set forth, for example: • in the Contract itself; • in an agreed purchase order for goods — see also Clause 6.3 concerning additional or different terms in purchase orders; and/or • in an agreed statement of work for services.
4.1.0.3. Is there a deadline for reporting a defect?
The Provider's obligations under this Clause apply only to (purported) defects that the Customer reports, in writing, to the Provider (or to the Provider's designee), on or before the end of 90 days after whichever of the following dates is applicable:
the date of delivery of the relevant deliverable, if the defect is in a deliverable, or
completion of the relevant service.
Comment
The Provider will want to establish a deadline as a cutoff date for their 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.
4.1.0.4. "Three Rs": What action(s) must the Provider take?
For any timely-reported defect, the Provider is to cause one or more of the following actions to be taken:
Repair: Correct the defect if that is commercially practicable; see also section 4.1.0.5 below;
Replace: 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
Refund: Cancel any unpaid invoice calling for the Customer to pay the relevant deliverable(s) and/or service(s), and refund any amounts that the Customer already paid under one or more such invoices.
The Provider may choose (i) which of the above actions to take, and (ii) the timing of those action(s), each in the Provider's sole discretion, so long as the Provider otherwise complies with this Clause.
4.1.0.5. What could count as "repair" of a defect?
Repair of a defect could include, without limitation, one or more of the following:
actual repair of a defective deliverable;
in the case of services, correction of defective work;
delivery of a commercially-reasonable workaround for the defect, if the Provider reasonably determines that repair or correction would be impracticable or not cost-effective.
4.1.0.6. Must the Provider meet any deadlines?
The Provider is to complete any repair or replacement above on before the end of 30 days after the Provider receives the defect report.
The Provider is to cause any refund to be made promptly after the time has expired for repair or replacement.
4.1.0.7. Who will pay for defect-correction efforts?
As between the Provider and the Customer, the Provider is responsible for all expenses of any actions taken under this Clause — without reimbursement from the Customer unless the Customer has otherwise agreed in writing.
Comment
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 Contract should clearly say so.
4.1.0.8. What if the Provider cannot reproduce the defect?
The Provider's obligations under this Clause apply only to defects that the Provider is able to reproduce through commercially-reasonable efforts.
For emphasis: If the Provider is unable to reproduce a defect, yet still elects to replace the deliverable in question, and/or to arrange for the Customer to get a refund, then:
the Provider's action is to be considered a commercial decision by the Provider, to further the Provider's own business interests; and
the Customer is not to assert that the Provider was conceding or acknowledging anything by it.
Comment
A. Reproducibility language like this is often included in license agreements for complex software, where the supplier might not be able to reproduce a bug that shows up only in a particular customer's installation.
B. Pro tip: The Customer might want to try to negotiate for the right to demand a refund (within a short time after delivery) even for cases where the Provider is unable to reproduce the defect.
4.1.0.9. Does the Provider guarantee future performance?
In agreeing to this Clause, the Provider is not warranting or guaranteeing the future performance of any deliverable.
The Provider is committing to take the actions stated in this Clause if a deliverable fails to comply with a warranty about the state of the deliverable as delivered.
Comment
This section reflects the sometimes-crucial distinction between:
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 Clause; versus
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 3.18.7.
4.1.0.10. Are these the Customer's exclusive remedies?
If so stated in the Contract, the Provider's obligations set forth in this Clause are the Provider'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.
Comment
A. Providers are very prone to include exclusive-remedy provisions like this in their terms of sale.
B. The term "anyone claiming 'through' you" will be familiar to lawyers and law students.
When this Clause is agreed to, it will govern whenever, in connection with the Contract, a party clearly identified in the Contract (the "Supplier") is to cause one or more items — tangible or intangible, and including but not limited to services — to be delivered to another clearly-identified party (the "Customer") to fulfill an order from the Customer that the Supplier has accepted (the "Order"). [Drafting suggestion: Fill in specific party names here.]
Comment
This Clause addresses delivery issues that are typically covered in "the fine print" of customers' purchase-order forms and — often in very different ways — in suppliers' terms of sale.
Example: 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 supplier, at https://perma.cc/5MB9-H6VK.
4.2.1.2. Title and risk of loss will pass per: DDP
Unless the Order clearly specifies otherwise, the Customer will become the owner of the goods, and the risk of loss of tangible goods will shift to the Customer, in accordance with INCOTERMS 2020 DDP (Delivered Duty Paid).
Comment
By specifying INCOTERMS 2020 "DDP" as the default provision, this Clause puts the onus on the Supplier to get the goods to the Customer's door (unless otherwise agreed); see 17.2 for additional discussion of this subject.
4.2.1.3. What packaging and labeling are required?
The Supplier is to have all deliverables packaged and labeled for shipment and delivery in a commercially-reasonable manner that's appropriate for the circumstances.
Note: Packaging and labeling of goods might also be subject to regulation by government authorities; as one example, consider the calorie-and-nutrition labels found on the packaging for foods sold in the U.S.
4.2.1.4. Are partial deliveries OK?
The Supplier is free to make partial deliveries unless the Order clearly specifies otherwise.
Comment
A. The Supplier might want to be able to ship goods as they're finished, without waiting for the entire order to be completed.
B. 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.
4.2.1.5. May the Supplier substitute equivalent deliverables?
The Supplier may may substitute equivalent deliverables, but only as stated in this section.
The substitute deliverables must meet all functional specifications stated in the Order (if any).
The Supplier must timely advise the Customer, in writing, of any substitutions — this would normally mean no later than the scheduled time for delivery (if any).
Comment
Drafters could override this section with language such as the following: "Supplier may not substitute different deliverables for those specified in an Order without Customer's prior written consent."
4.2.1.6. May the Customer reject substitute deliverables?
Unless the Customer has agreed in writing to the substitution:
the Customer may reject substituted deliverables, but
the Customer must do so on or before the date 14 days after the date of delivery, otherwise the Customer will be deemed to have accepted the substituted deliverables.
Comment
Giving the Customer a (time-limited) right to reject "surprise" substituted goods will give the Supplier an incentive to get Customer's sign-off before shipping such goods.
4.2.1.7. May the Customer require redirection of delivery?
The Customer may direct the Supplier to make a delivery to a third party — even after the Supplier has accepted the Order — but only as stated in this section.
The Supplier need not make the redirected delivery if the Supplier has reasonable grounds for objection.
The Customer must pay, or reimburse the Supplier for, any additional expense reasonably associated with any redirected delivery requested by the Customer.
Comment
A. The Supplier might have a reasonable basis for objecting to delivering to a specified third party; for example:
the shipment might already be on its way and not divertable;
the third party might be in a location — or be — subject to export-controls restrictions (see 13.11);
the deliverables might be unlawful at the proposed new delivery address, for example, alcoholic beverages or marijuana for a location where such goods were illegal.
B. The Supplier's additional out-of-pocket expenses could include, for example, shipping charges; insurance premiums; outside-counsel legal fees for special cases; etc.
4.3. Resale Channel
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 Clause sets out basic provisions for reseller agreements. Such reseller relationships can be important for suppliers looking to grow their "sales channels."
Contents:
When this Clause is adopted in the Contract, it means that a party specified in the Contract (the "Reseller") is expected:
to acquire, and,
in a specified "Territory" (see below), resell,
one or more products, services, and/or other items of another specified party (the "Supplier").
Comment
A. The term "Reseller" could encompass a variety of different functions such as distributors, wholesalers, and retailers.
B. 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 Clause.
4.3.1.2. Channel Partnership terms also apply
The relationship between the Supplier and the Reseller is a "Channel Partnership" as referred to at Clause 4.5, which (i) includes certain basic definitions, and (ii) is incorporated by reference into this Clause.
The term "Territory" refers to the one-half-mile radius around the mailing address of the Reseller's principal place of business.
The Reseller may acquire Supplier Offerings directly from the Supplier at a discount of 0.001% from the Supplier's then-current, published list price that is applicable in the Territory.
Comment
Of course this particular Territory is ridiculously small, and the Reseller's Discount is ridiculously low. Both are included for "fault tolerance" in case drafters neglect to specify otherwise. (The Reseller is extremely unlikely to agree to these terms IRL, "In Real Life.")
4.3.1.4. May the Reseller reveal its Seller "deal" details?
The percentage and/or amount of the Reseller's discount is the confidential information of the Supplier; the Reseller is not to reveal that information (nor confirm it) to third parties — including but not limited to other suppliers — without the Supplier's prior written consent.
Comment
The parties might want to include Clause 8.18 (confidential information protocol) in the Contract as well.
4.3.1.5. When must the Reseller pay the Supplier?
The Reseller is to pay for Supplier Offerings that the Reseller acquires from the Supplier net 30 days from receipt of the Supplier's invoice, as stated in more detail at Clause 2.14 (payment terms).
Comment
This phrasing allows for the possibility that the Reseller might acquire Supplier Offerings from sources other than the Supplier, such as from other resellers or distributors.
4.3.1.6. Who has pricing authority for the Reseller's sales?
For emphasis: As between the Reseller and the Supplier, the Supplier has no authority to determine the prices that the Reseller charges to its customers.
Comment
The Supplier might be tempted to try to prohibit the Reseller from discounting Supplier's products or services. But that kind of "retail price maintenance" ("RPM," sometimes known as "vertical price fixing"; see 22.7.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.
4.3.1.7. The Supplier's consent is required for repackaging, modification, etc.
The Reseller must not package, repackage, modify, or otherwise alter any Supplier Offering, in any way, without the Supplier's prior written consent.
For emphasis: The prohibition against "modify[ing]" Supplier Offerings extends (without limitation) to the removal or alteration of any legend or notice — for example, copyright- or trademark notices and the like — and/or warnings or user instructions from any Supplier Offering itself; promotional materials; user documentation; etc.
If any part of a Supplier Offering came to the Reseller in a sealed package — including, for example, a software license code in a sealed envelope — then the term "otherwise alter" would encompass the Reseller's opening the package.
If a Supplier Offering came to the Reseller in separable components, then the term "repackage" would encompass the Reseller's separating the components (possibly for individual sale).
Comment
A. In some cases, the Supplier won't really care whether the Reseller modifies the Supplier's goods — but some such modifications could result in the Supplier's getting dragged into lawsuits against the Reseller by the Reseller's customers.
B. And if the Supplier owned intellectual-property rights in a Supplier Offering, then the Supplier might not want the Reseller creating "derivative works" without permission. Here are a couple of (nonlimiting) examples to illustrate prohibited Reseller modifications:
4.3.1.8. The Supplier will honor its standard warranty
The Supplier is to honor substantially the same Supplier Offering warranty terms for the Reseller's customers as the Supplier does for the Supplier's own customers of the same Supplier Offering(s) in the Territory.
The Supplier is to defend and indemnify the Reseller from any claim — by any Reseller customer that acquired a Supplier Offering from the Reseller — if the claim arises out of an alleged breach of a Supplier warranty concerning that Supplier Offering.
Comment
A. This section:
gives the Reseller's customers essentially-equal status with the Supplier's own customers; and
precludes the Reseller (or its customers) from claiming that the Supplier must do more for the Reseller's customers than for the Supplier's own customers.
B. Pro tip: As with any indemnity obligation, the Reseller might want to check out the Supplier's financial ability to comply with the obligation — and possibly negotiate to have the Supplier maintain one or more backup sources of funding (such as insurance) for that purpose.
4.3.1.9. Who will provide technical support for Reseller customers?
This section applies during the Partnership Term.
The Reseller is to provide Level 1 support (defined at 8.64) for the Reseller's customers for Supplier Offerings.
In providing such support, the Reseller is to follow any reasonable written- and oral guidance for customer support that the Supplier causes to be provided to the Reseller, to the extent that the guidance isn't inconsistent with the Contract.
The Supplier is to provide Level 2 and Level 3 support for those Reseller customers.
Comment
A. The Supplier will normally be very interested in making sure that end-customers for the Supplier's products are properly supported.
B. On the other hand, the Supplier might well want at least some of the cost and burden of providing basic customer support to be taken on by the Reseller. (That could be a point to be negotiated along with the discount that Reseller will receive.)
C. In crafting technical-support guidance, the Supplier would normally want to specify that the Reseller must promptly contact the Supplier 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 Supplier Offerings and/or on the Supplier's brand.
4.3.1.10. What standards must be met by Reseller repairs?
This section applies if the Reseller engages in repair or other servicing of Supplier Offerings.
The Reseller must use parts of equal or better quality than original.
The Reseller must not offer or provide as "new" any Supplier Offering that the Reseller has repaired after customer return unless the Supplier specifically agrees in writing.
For emphasis: This section in itself does not authorize, require, or prohibit, the Reseller's servicing of Supplier Offerings.
Comment
It's not uncommon for both suppliers and resellers to offer "refurbished" products that have been returned by customers. This subdivision gives the Supplier some control over whether and how the Reseller does so.
4.3.1.11. The Reseller must support Supplier recalls
If the Supplier issues a recall of any Supplier Offering, then the Reseller is to provide reasonable cooperation with the Supplier (and with the Supplier's designees) in connection with the recall.
At either party's request, any persistent disagreement about what would constitute reasonable cooperation under subdivision a is to be addressed by (non-binding) escalation as stated at Clause 6.4.
Comment
What would constitute "reasonable" cooperation could depend in part on whether the Supplier agreed to reimburse the Reseller for reasonable out-of-pocket external expenses actually incurred by the Reseller in providing such cooperation.
4.3.1.12. Any additional warranties would be the Reseller's responsibility
Absent good reason, the Supplier would not object to the Reseller's offering additional- or more-favorable warranties or other commitments to the Reseller's customers (at the Reseller's own risk and expense).
Comment
This phrasing was chosen so as not to imply that the Supplier was somehow "authorizing" the Reseller's activity — conceivably, such an implication might have downstream liability implications for the Supplier if a Reseller customer were to sue the Reseller for breach of the Reseller's additional warranty and also sue the Supplier on some kind of negligent-authorization theory or other "creative" rationale.
4.3.1.13. The Reseller's indemnity obligation
The Reseller must defend and indemnify the Suplier and its Protected Group against any claim by a third party that arises out of acts or omissions of the Reseller relating to Supplier Offerings, other than a claim that the Contract unambiguously makes the responsibility of the Supplier.
Comment
Pro tip: As with any indemnity obligation, the Supplier should consider negotiating to have the Reseller maintain insurance as backup funding for the obligation (and the Reseller should consider doing so anyway).
4.3.1.14. What happens to the Reseller's customers upon termination?
The ending of the Channel Partnership, by expiration or other termination, will not affect any then-established rights or obligations of the Reseller's customers concerning Supplier Offerings.
Comment
This section gives the Reseller some reassurance that the Supplier won't abandon the Reseller's customers after termination of the Reseller's relationship with Supplier — but often, that should be practically a given, because the Supplier will want to transition those customers into a direct relationship with the Supplier or over to a different reseller.
4.3.1.15. The Reseller must report possible IP infringement
If Reseller suspects that unauthorized use, copying, distribution, or modification of a Supplier Offering might be occurring, then The Reseller is to proceed as stated at Clause 8.40 (protocol for dealing with potential infringement of IP rights).
4.3.1.16. The Supplier reserves other rights about its Offerings
As between the Supplier and the Reseller, the Supplier reserves all rights concerning Supplier Offerings that are not specifically granted by the Contract.
The Supplier's reservation of rights in subdivision a extends (without limitation) to all copyrights, patent rights, trademark and service mark rights, trade secret rights and other intellectual property rights in Supplier Offerings.
4.3.1.17. Reseller responsibility for its dependence
The Reseller acknowledges that the Supplier has no responsibility —
for any dependence that the Reseller's business might have on Supplier Offerings; nor
for any harm that might result to the Reseller from the ending of the Supplier-Reseller relationship;
and the Reseller WAIVES any claim to either effect.
Comment
See generally the commentary to Clause 7.1 (acknowledgement definition).
4.3.1.18. Additional terms for software- and SaaS offerings
This section applies in respect of any Supplier 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."
Clause 4.4 (software-specific items) is incorporated by reference into this Clause for each Supplier Offering within the scope of subdivision a.
The Reseller is to keep a minimum quantity of Supplier Offerings in inventory as follows: [DESCRIBE].
Option: Reseller Maximum Inventory
The Reseller is not to keep more than [AMOUNT] of Supplier Offerings in inventory without the Supplier's prior written consent.
Option: Reseller Retail Sales Authorization
For emphasis: The Reseller may offer or sell Supplier Offerings from physical premises (for example, in stores) when otherwise permitted by the Contract.
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 Supplier Offerings from physical premises (for example, in stores) without the Supplier's prior written consent.
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 Supplier Offerings from sources other than Supplier.
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 Supplier Offerings to others for resale or redistribution.
Option: Reseller Delivery Responsibility
As between the Reseller and the Supplier, the Reseller is responsible for:
acquiring any physical Supplier Offerings; and
arranging for all storage and/or delivery to the Reseller's customers.
The Reseller's activities under subdivision a will be at the Reseller's own expense and risk.
B. This Option likely wouldn't apply in so-called "drop shipping" arrangements, where the Reseller communicates an end-customer order to the Supplier, whereupon the Supplier ships the ordered goods directly to the end-customer.
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.
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.)
4.3.2. Reseller relationships can be tricky
Reseller relationships can work well, but over time — and as the parties' management personnel and strategic plans change — even once-successful relationships can deteriorate and ultimately end into expensive, time-consuming litigation. This can be seen in a Tenth-Circuit decision whose holdings are of less interest to us than the fact that the case 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 (10th Cir. 2024).
4.4. Resale — Software Supplement
Software is often "sold" (that is, licensed) through resale channels; this Clause adds ground rules for that case.
Contents:
4.4.0.1. When would this Supplement come into play?
When This Clause is agreed to in the Contract, it will apply in connection with any Supplier 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."
Comment
Drafters should consider adopting this Clause in any reseller relationship where the Reseller will be dealing with the Supplier's computer software.
4.4.0.2. Who would provision Reseller's customers?
Unless otherwise directed by the Supplier, the Reseller will refer all of its customers to any Supplier-provided provisioning system for the Reseller's customers to sign up for access to (and licensing of) the Software.
Comment
When the Supplier Offerings include SaaS, the Reseller will almost certainly want the Supplier to provide the necessary customer onboarding — and the Supplier will typically insist on doing so.
4.4.0.3. Reseller customers must agree to Supplier's terms
The Supplier may require the Reseller's customers to agree to the Supplier's then-current terms and conditions as a prerequisite for being able to install and/or use the Software.
Comment
The Supplier will typically require customers to agree to, for example: • an end-user license agreement ("EULA"); • terms of service or ‑use ("TOS"); and/or • a privacy policy.
4.4.0.4. What must the Reseller do about software updates?
This section will apply if the Supplier releases a superseding version of the Software.
If so requested by the Supplier, the Reseller is to promptly encourage all of Reseller's customers to install and acquire the superseding version.
Comment
A. The phrase "superseding version" would commonly include things such as updates, bug fixes, and the like.
B. Where SaaS (Software as a Service) is concerned, updating would normally be handled directly by Supplier, hence the "If so requested by Supplier" qualification here.
4.4.0.5. How may the Reseller use the Software?
The Reseller may use the Software (as limited by subdivision b) solely for purposes of the following:
demonstrations to, and training of, customers and/or clients, existing or prospective;
testing; and/or
internal training of the Reseller's personnel to support the Reseller's Software sales operations.
The Reseller's authorization in subdivision a extends only as follows:
to the Software in executable form only; and
in compliance with the Supplier's applicable terms and conditions.
Comment
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 Supplier. (This is not just a theoretical concern: Your author once served as an expert witness in a case in which a software supplier's customer used the supplier's software to offer services to the customer's own customers — thus potentially depriving the supplier of license sales to those other customers. As usually happens in litigation, the parties settled the dispute before trial.)
4.4.0.6. What Software copies may the Reseller make?
The Reseller may make a reasonable number of copies of the Software for purposes of backup, disaster recovery, and disaster testing.
The Reseller must conduct its operations under subdivision a in accordance with commercially-reasonable IT procedures.
Comment
Unlike some ill-considered provisions, this section does not limit the Reseller to making just one backup copy, which simply wouldn't be practicable.
4.5. Sales Channel Partnerships
The term "[sales] 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.
Here are a few real-world examples of channel partnership agreements:
This Clause sets out ground rules that would be common to both reseller agreements (4.3) and referral agreements (8.56).
For many companies that sell things, the so-called "sales channel" is an important aspect of business; this Clause sets out typical ground rules.
This Clause will govern in any "Channel Partnership," that is, any relationship where:
a party (the "Supplier") is anticipated to be supplying one or more goods (tangible or intangible) and/or services (each, a "Supplier Offering," defined below) under the Contract; and
another party (the "Partner" — using that term only in a business-colloquial sense — is anticipated to be engaging in a related activity such as (without limitation):
(i) acquiring and reselling Supplier Offerings; and/or
(ii). referring potential customers and/or clients to the Supplier.
Comment
A. Business planning: Ideally, the Contract 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 Supplier; and/or
refer one or more potential customers to the Supplier and/or to the Supplier's designee.
For a fairly-detailed list of specific business issues to consider negotiating, see a 2023 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 are broadly applicable 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).
B. The term "Partner" is used here colloquially, as commonly used 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 4.5.3.1.
4.5.1.2. Definitions: Supplier Offerings; Territory; Partnership Term
The definitions below apply unless clearly agreed otherwise in writing.
"Territory" refers to the city limits of the city of the Partner's initial address for notice;
The "Partnership Term":
will last two years, beginning on the effective date of the Contract and ending at 12:00 midnight the end of the day on the same date the specified period later; and
will not be extended unless both parties agree in writing to an extension — but see also the extension option at 4.5.2.3 below.
"Supplier Offerings" refers to all Supplier products (tangible and intangible) and services that Supplier makes available to be offered in the Territory during the Partnership Term.
Comment
A. Subdivision 2: Obviously the geographic- and market-segment limits of the "Territory" could be a subject for discussion.
B. 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.)
C. Pro tip: If the Supplier 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 Supplier product- or service line.
4.5.1.3. No exclusivity unless expressly stated
Unless clearly agreed otherwise in writing, the Channel Partnership non-exclusive for both the Partner and the Supplier, as set forth in more detail at Clause 6.7 (which is incorporated by reference here).
Comment
Drafters should be sure to review the commentary about exclusivity at 6.7.
4.5.1.4. The Partner is not the Supplier's agent
Unless clearly agreed otherwise in writing, the Partner is not the Supplier's agent and is to conduct itself accordingly.
Comment
A. In some types of channel partnerships, the general idea would be for the Partner to act as the Supplier'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 Supplier's name and to make commitments that were binding on Supplier; and
the Supplier could be "vicariously liable" for the Partner's acts and omissions.
B. See also 6.8.2 for Partner activities that could be inconsistent with this requirement.
4.5.1.5. Certain Supplier information is confidential
The Partner must preserve in confidence any confidential information disclosed by the Supplier.
The economic terms of the Contract are Supplier's confidential information (not necessarily the only such information).
The Supplier will not have confidentiality obligations about Partner information unless clearly agreed otherwise in writing.
Comment
A. The Supplier might provide the Partner with confidential information about (for example) the Supplier's future plans — the Partner should expect to have to keep such information in confidence.
B. Subdivision 2: The Supplier 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 Supplier made with the Partner, e.g.:
what discount the Supplier is giving to a reseller Partner — see Clause 4.3 (reseller protocol); or
what commission the Supplier will be paying to a referral Partner — see Clause 8.56.
C. Subdivision 3: In some channel-partnership relationships, the Partner might provide the Supplier with the Partner's own confidential information — in such a case, the Partner would likely want to negotiate appropriate confidentiality provisions.
D. Drafters should consider also including Clause 8.18 (confidential information protocol) in the Contract.
4.5.1.6. Going public with the relationship is OK
Each party may publicly disclose the fact of the parties' relationship in the Channel Partnership, but only as follows:
only without disclosing confidential information subject to the confidentiality provisions of the Contract.
Comment
A. It's not unheard of for a former channel partner to continue holding itself out as such, notwithstanding that the supplier had terminated the relationship; this language gives each party an explicit contractual requirement to enforce in such a case.
B. Example: The present author once had to deal with just such a situation on behalf of a client, where the client terminated its relationship with a European reseller, but the reseller continued to hold itself out as (supposdly) representing the client.
C. 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).
4.5.1.7. The Partner must comply with trademark guidelines
The Partner must use only Supplier-designated logos, trademarks, service marks, and/or trade names (collectively, "marks") to refer to Supplier Offerings.
In case of doubt: The Partner may use the Supplier's marks:
only during the Partnership Term; and
only to identify Supplier Offerings.
The Partner must comply with any commercially-reasonable instructions that the Supplier provides concerning use of the Supplier's marks.
Comment
A. Under trademark law, the Supplier must "police" others' use of the Supplier's trademarks, etc.; this section accordingly puts "fences" around the Partner's right to use those marks.
B. In some commercial arrangements, the Supplier 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).
C. Related reading: Clause 8.67 (trademark license protocol)
4.5.1.8. The Supplier will comply with trademark guidelines
The Supplier — at its own expense — is to handle all aspects of end-customers' claims under the Supplier's warranties for Supplier Offerings unless clearly agreed otherwise.
Comment
The Partner would likely be less than eager to deal in the Supplier's goods or services, or to make referrals to the Supplier, if there was any significant chance that the Partner could be sued by end customers because the Supplier breached one of the Supplier's warranties; hence, this section.
4.5.1.9. The Partner may not expand the Supplier's warranty obligations
The Partner must not purport — on the Supplier's behalf — to expand or extend any Supplier warranties for Supplier Offerings.
Comment
Under this Clause, the Partner isn't allowed to change the Supplier's warranties — but 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 3.18.2.
4.5.1.10. Would the Partner be subject to any performance standards?
The Contract (or other written agreement) may set forth minimum Partner performance standards.
If the Partner does not meet any such agreed performance standard, then the Supplier, in its sole discretion (defined at Clause 7.23), may do one or more of the following, in sequence and/or in combinations:
put the Partner on a performance-improvement plan (see generally 8.51);
wholly- or partly terminate the Partner's exclusivity (if any; see generally 6.7);
temporarily- or permanently reduce the Partner's rights in the Territory (if any); and/or
terminate the Channel Partnership, either immediately or if the Partner does not achieve the goals specified in a performance-improvement plan — in case of doubt, such a termination would not be "at will" or "for convenience" (see generally 4.5.2.7).
Comment
For an extended discussion of possible Partner performance standards, see generally the appendix at 4.5.3.2.
4.5.1.11. The Supplier may modify its offerings
The Supplier may add to, modify, and/or cease to offer, one or more of the Supplier Offerings at any time in the Supplier's sole discretion.
The Supplier may solicit the Partner's input in that regard but need not do so.
For the avoidance of doubt: The Supplier would have no liability to the Partner for any change that the Supplier made to one or more Supplier Offerings or to the Supplier's line of offerings unless the change breached an express requirement of the Contract.
Comment
A. Some might assume that of course the Supplier can make changes to its line of offerings. But a creative lawyer for the Partner might try to argue that the Supplier 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.
B. Subdivision 2: Consultation about change is (usually) a Good Thing. But not consulting shouldn't be a breach, absent a clear agreement otherwise.
4.5.1.12. The Supplier will control its sales negotiations
The Supplier will control the Supplier's sales negotiations with the Supplier's own customers unless clearly agreed otherwise.
Any assistance provided by the Partner in any such negotiations is to be:
only at, and solely to the extent of, the Supplier's request and direction; and
at the Partner's own expense (unless expressly agreed otherwise by the Supplier).
Comment
A. This section would apply mainly when the Channel Partnership involves Partner making referrals to the Supplier. If the Partner is a reseller of Supplier Offerings, then presumably the Partner would control its own sales negotiations.
B. In some cases, the Supplier might positively welcome the Partner's assistance in making a sale. But: The Supplier will still want the right to determine whether — and to what extent — the Partner is to provide such assistance.
4.5.1.13. The Partner is to pass on any feedback
The Partner is to pass on to the Supplier any feedback it receives, or conceives, about Supplier Offerings.
The Supplier may use, or not use, any or all such feedback as the Supplier sees fit, without obligation — financial or otherwise — to the Partner.
The Supplier may not identify the Partner as the source of the feedback, nor imply that the Partner endorses the Supplier or any Supplier offering, without the Partner's prior written consent.
For purposes of this Clause, "feedback" refers to any and all suggestions, comments, opinions, ideas, or other input:
concerning any Supplier Offering, and/or
for additions, deletions, improvements, or other changes, to some or all of Supplier's line of offerings.
Comment
A. Feedback from "the channel" can be important in helping the Supplier to improve Supplier Offerings; such feedback might come from the Partner or from end-customers.
B. Pro tip: The Supplier will want to keep in mind the possibility that third parties might have intellectual-property rights in feedback ideas.
4.5.1.14. Legal compliance is required
Each party is to comply with applicable laws whenever engaging in Channel Partnership-related activities.
Comment
If the Partner claimed that the Supplier 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").
4.5.1.15. Each party has a defense obligation
Each party is to defend (in accordance with Clause 3.4) the other party's Protected Group (defined at Clause 7.40) against third-party claims concerning matters that are the defending party's responsibility under this Clause.
For the avoidance of doubt: For this purpose, the term "third-party claims" includes, without limitation, claims by employees and by government authorities.
Comment
A. This section would apply if a third party were to make a claim against the Supplier 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.
B. 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.
C. 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.)
4.5.1.16. Bringing on subpartners requires consentsubpartners
Without the Supplier's prior written consent, the Partner must not engage subcontractors — referred to here as "subpartners" — to carry out some or all of the Partner's obligations, and/or exercise some or all of the Partner's rights, under the Contract.
The Supplier may grant or withhold such consent in its sole discretion (defined at Clause 7.23).
Comment
A. Whether or not to allow the Partner to engage subpartners at all — and if so, which subpartners — is something over which the Supplier is likely to want to maintain fairly-tight control. That's because the Supplier's public image could be affected by a subpartner's actions or inactions.
B. Pro tip: The Supplier might want to do at least some due diligence on a prospective subpartner — so whenever requesting the Supplier's consent to the appointment of a prospective subpartner (a "prospect"), the Partner should typically expect to be asked to provide the Supplier 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 Supplier; and
such background information about the prospect as the Supplier might reasonably request; this could include, for example, the results of a background check, if so requested by the Supplier.
To reduce the chances of mutual interference between the Supplier's and the Reseller's marketing activities, the Reseller is to consult the Supplier in advance about the Reseller's proposed marketing activities concerning Supplier Offerings.
In case the question comes up: This Option requires only advance consultation and not advance approval.
4.5.2.2. Option: Termination as Supplier's EXCLUSIVE Nonperformance Remedy
The Supplier's right to terminate the Channel Partnership will be the Supplier's EXCLUSIVE REMEDY for any failure by Partner to meet the agreed performance requirements (after any agreed cure- or performance-improvement period).
The Partnership Term will automatically be extended for successive "evergreen" periods, each of the time stated in the heading of this Option (or as otherwise agreed).
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 Clause 6.6.
If the parties agree in writing that this Option is to be "opt-in" (e.g., by so stating in the Contract), then the automatic extension will occur only ifeither 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.
Comment
As with any automatic extension, parties should be sure to calendar the opt-out or opt-in deadline. Otherwise, a partycould find itself stuck in a relationship that it would really have preferred to walk away from, as discussed in the commentary at 6.6.4.
4.5.2.4. Option: Partner Customer Data Reports (Quarterly)
At the times stated in subdivision b of this Option, the Partner is to provide the Supplier with complete and accurate data about the Reseller's transactions and prospective transactions involving Supplier Offerings.
Unless otherwise agreed in writing, the Reseller is to provide such data:
no later than 30 days after the end of each calendar quarter;
whenever reasonably requested by the Supplier from time to time; and
at the end of the Partnership Term.
In case of doubt: The Reseller's obligations in this Option are subject to any restrictions imposed by law (for example, privacy laws).
Comment
A. In the modern economy, customer data can be invaluable to manufacturers and others in the supply chain (or, really, the supply web). The Supplier therefore might want to try to get the Reseller to agree to something like this Option.
B. If the Supplier has other [legitimate] ways of obtaining data from the Reseller's customers — e.g., software onboarding; warranty registrations; frequent-user clubs; and the like — then the Supplier might not need to get the Reseller to commit to providing customer data.
C. Subdivision 1: The phrase complete and accurate is used instead of true and correct, for reasons discussed at 25.5.
[EDIT TO SUIT:] During the Partnership Term, the Partner must not:
solicit sales to, nor provide support for, any customer for Supplier Offerings if that customer has significant operations outside the Territory;
establish or maintain facilities for supporting customers' use of Supplier Offerings if such use is reasonably likely to occur outside the Territory; nor
make any Supplier Offering available to any individual or organization if the Partner knows, or reasonably should know, that the Supplier Offering will be taken, installed, or used outside the Territory.
Comment
A. If the Partner's Territory (see 4.5.1.2) is to be limited, then it might be well for the Contract 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.
B. Subdivision (1): The parties might want to discuss whether any post-term restrictions would be appropriate — and legally binding. (See the discussion of noncompetition covenants at 4.5.2.6.)
4.5.2.6. Option: Partner's Noncompete Obligation
Both during and for one year after the end of the Partnership Term, the Partner must 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 Supplier Offering, unless the Supplier gives its prior written consent.
Clause 8.47 (noncompete protocol) is incorporated by reference.
Comment
A. 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.
B. For (a bit) more information about noncompetes, see the commentary to Clause 8.47.
4.5.2.7. Option: Restriction on Termination at Will
Beginning one year after the effective date of the Contract, either party may terminate the Channel Partnership at will upon 30 days' notice in accordance with Clause 5.3 unless the Contract clearly provides otherwise.
Otherwise, neither party may terminate the Channel Partnership "at will" or "for convenience."
Comment
A. 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).
B. So: 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.
C. For additional discussion about some of the business implications of termination at will, see the commentary to Clause 5.3.
D. Caution: The Supplier 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 inFire 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).
4.5.2.8. Option: No Termination at Will
Neither party may terminate the Channel Partnership "at will" or "for convenience" unless the Contract clearly provides otherwise.
4.5.2.9. Option: WAIVER of Franchise- and Business-Opportunity Laws.
In entering into the Contract, no party intends to create a relationship that would be subject to laws governing franchises and/or business opportunities.
In connection with the Contract, each party WAIVES any rights or claims under laws governing franchises and business opportunities or similar laws.
Comment
A. 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."
B. Even so, language like this clause is sometimes seen in contracts.
The Partner must not engage subcontractors without the Supplier's prior written authorization, which the Supplier may grant or withhold in its sole discretion (defined at Clause 7.23).
Comment
For additional discussion about subcontractors, see [BROKEN LINK: subk-cmt].
The Partner must enter into a subcontractor agreement with each (if any) subcontractor.
Each such subcontractor agreement must do at least the following:
impose at least the same restrictions and obligations on the subcontractor as the Contract does on the Partner — this would normally include, without limitation, prohibiting the subcontractor from appointing sub-subcontractors without the Supplier's prior written consent;
unambiguously state that the Supplier will have no liability to the subcontractor in connection with the subcontractor agreement;
terminate automatically, without the need for action by the Supplier, at the end of the Partnership Term; and
unambiguously state that the Supplier is a third-party beneficiary of the subcontractor agreement.
For the avoidance of doubt: If the Supplier reviews and/or approves any form of subcontractor agreement, it will be solely for the Supplier's own benefit and not that of the Partner, the subcontractor, or any other individual or organization.
Comment
Concerning third-party beneficiaries in general, see Clause 8.66.
4.5.2.12. Option: Partner Responsibility for Subcontractor Performance
As between the Partner and the Supplier, the Partner is solely responsible for all aspects of each of the Partner's subcontractor agreements.
The Partner must defend and indemnify the Supplier's Protected Group against any claim by:
a subcontractor, and/or
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 Contract unambiguously makes the responsibility of the Supplier.
Comment
A. The Supplier 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.
B. Pro tip: Insurance? As with any indemnity obligation, the Supplier should consider proposing that the Partner must maintain insurance (see 3.10) as backup funding (see 2.4) for the obligation.
4.5.3.1. "Channel partner" - a dangerous name? (Maybe not.)
[fnHere'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."
4.5.3.2. Appendix: Possible minimum Partner performance standards
A. Reseller agreements, referral agreements, and other channel-partner contracts sometimes set forth minimum performance requirements for the channel partner. That's because the Supplier likely wouldn't want to continue the relationship if the Partner wasn't performing.
B. Some examples of possible performance standards include the following:
minimum number of customers successfully closed by the Supplier or Partner, to promote market penetration for the Supplier's products and/or services;
minimum dollar volume of actual sales, to end customers, of the Supplier's offerings;
minimum dollar revenue to the Supplier 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 Supplier 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 Supplier, as discussed at [BROKEN LINK: take-pay-disadv-cmt];
sending X number of the Partner's people to the Supplier's sales training;
attending X number of industry events per quarter or per year;
C. Ideally, the Contract 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 Contract), the Supplier's having the right (by notice) to terminate the Channel Partnership, and with it, the Partner's rights (on a going-forward basis.
D. Pro tip: The Supplier should keep in mind that it might want to grant some other partner an exclusive right in the Territory — but if the Supplier 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 5.2.5 for examples of some cases where similar things have happened.
E. As time goes on, the Partner's performance standards could be made more stringent, to provide the Partner with an initial "break-in" period.
F. Performance standards could also provide for additional compensation to the Partner if the Partner overachieves the stated performance targets.
G. Parties could also consider specifying some kind of performance improvement plan, as provided at Clause 8.51; 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.
4.6. Sales Quotations
In sales by a supplier 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 Clause [BROKEN LINK: purch-ord-rule]).
(The supplier'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 Clause largely restates applicable law in some jurisdictions; drafters can use it to establish more certainty about the ground rules for sales discussions.
Cross-references: See Clause 6.3 (entire agreement), along with 10.5 concerning the effect of additional terms in purchase orders, etc.
If this Clause is adopted in the Contract in the Contract:
it will govern whenever, under the Contract, a party (the "Supplier") provides a sales quotation or comparable document (each, a "Quote") to another party (the "Customer");
its terms are incorporated by reference into the Quote; and
its terms take precedence over any inconsistent terms in the Quote.
4.6.1.2. Would a Quote be binding if "accepted" by the Customer?
A Quote is not an "offer," and so the Customer cannot form a binding contract by accepting the Quote — unless:
the Quote itself clearly says so; or
the parties otherwise so agree in writing.
Comment
The approach in this section reflects how procurement for the U.S. Government generally works, as spelled out in the Federal Acquisition Regulations: Quotations are not offers, orders are. See Legal effect of quotations, 48 C.F.R. § 13.004.
Subdivision 2: The "otherwise agree in writing" phrase is intended to serve as a mini-version of the Statute of Frauds: It wouldn't be good for the Supplier and the Customer to get into a dispute about whether the Supplier'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.
4.6.1.3. Could the Supplier's catalogs, etc., be binding if "accepted"?
For emphasis: The Supplier's advertisements, catalogs, price lists, quotations, and similar documents are likewise not "offers."
Comment
This tracks the law in the U.S. and many other jurisdictions: A supplier's advertisement or catalog is generally considered, not an offer itself that can be accepted, but instead is an "invitation to treat," that is, an invitation to others asking them to make an offer, which the supplier can then accept, as discussed generally in a Wikipedia article.
4.6.1.4. May the Supplier modify or withdraw a Quote?
The Supplier may withdraw or modify a Quote[a] — even if the Quote qualifies as an "offer"[b] — until such time (if any) as the Supplier receives[c] the Customer's timely written acceptance.
Comment
[a] Obviously, a sales-savvy Supplier would be reluctant to unilaterally modify a pending Quote that a prospective Customer is in the process of considering.
[b] If a Quote isn't an offer, then of course the Supplier would be free to modify the Quote at any time, even if the Customer were to submit an order based on the Quote.
[c] The "receives" term is 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 Supplier.
4.6.1.5. Would an "offer" Quote expire? When?
A Quote that does qualifies as an "offer" will expire — assuming that the Supplier has not yet received[a] a written acceptance of the offer — on the date three months[b] after the Quote's date[c] if the Quote does not say otherwise in writing.[d]
Comment
[a] By requiring receipt of acceptance of a quote by the supplier, this subdivision intentionally goes against the "Mailbox Rule" that certain contract-related communications are deemed effective when mailed. (See 6.9.9 for a discussion of the Mailbox Rule.)
[b] The three-month gap-filler expiration date for Quotes is a mirror of the 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.
[c] If a Quote does not specify its own date, then that date should be the date that the Quote was received by the Customer, so as not to penalize the Customer for the Supplier's failure to date its Quotes.
[d] The Supplier will probably want to put a specific expiration date on each Quote because the Customer might take its time deciding whether or not to buy — then, as time passes, filling the Customer's order, based on a long-forgotten Quote, might be challenging for reasons such as those discussed at 4.6.2.1.
4.6.2. Additional notes
4.6.2.1. Why the Supplier want quotes to expire?
A Supplier would want its quotes to expire because (possibly among other reasons):
The Supplier might stop offering the product or service that's the subject of the quote;
The Supplier might raise its prices; and/or
The Supplier might decide, for whatever reason, that it no longer wants to deal with that Customer at all — perhaps because the Supplier has decided that the Customer is going to be too much trouble to work with, or perhaps the Supplier has engaged a reseller for the territory (see 4.3) and now wants the Customer to deal with the reseller instead of directly with the Supplier.
4.7. Services: General provisions
Services agreements can be pretty intricate. This Clause tries to cover some of the most common terms in a modular fashion.
When this Clause is agreed to in the Contract, the parties contemplate that, under the Contract, one party (referred to as the "Provider") will provide specified services for another party (the "Customer").
For purposes of this Clause, the term "party" refers to a party to the Contract unless the context clearly and unmistakably indicates otherwise.
4.7.1.2. The statement of work is "it" for each project.
An agreed, written, statement of work:
sets out the Provider's exclusive responsibility for providing services under the Contract; and
sets out the Customer's exclusive responsibility for paying for services under the Contract.
Comment
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:Moritz (Cal. App. 2020): In a lawsuit about one of the Fast & Furious movies, a state appeals court gave the parties a mild scolding for not having done at least a short-form agreement, as they had 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 contract 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).
4.7.1.3. But the Contract takes precedence — usually.
A statement of work will override the Contract only if the statement of work noticeably states — at or near its beginning — that one or more provisions of this Clause are being overridden.
A single such noticeable statement will 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 Contract.
Comment
A. For greater business flexibility, a statement of work should be able to override the Contract — but to protect both parties, this section aims to prevent a party from burying a substantive change to this Clause deep within a statement of work.
B. 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:Planet Construction (W.D. La. 2023): 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).
4.7.1.4. External evidence can supplement or explain a SOW, but not modify it.
The Provider and/or the Customer may offer extrinsic evidence to supplement or explain a statement of work.
If the extrinsic evidence includes any contested testimony by someone having an interest in the matter — for example, if the Provider claims that the Customer orally agreed to a price increase, or if the Customer claims that the Provider orally agreed to a price cut — then the party offering the testimony must support it with reasonable corroboration.
Neither party is to assert that extrinsic evidence can be used to contradict the statement of work.
Comment
A. For smaller projects, the parties' statements of work might be, um, sparse; for that reason, this Clause allows for a statement of work to be fleshed out by extrinsic evidence (a.k.a. "parol" evidence).
B. 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.
C. Concerning the reasonable-corroboration requirement in subdivision 2, see 7.18.
D. Tangential to the no-contradiction requirement of subdivision 3: In 2023 the Eighth Circuit 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).
4.7.1.5. Each SOW is a separate contract.
Each statement of work under the Contract is to be considered a separate contract, independent of any other statement of work (if any), unless both parties clearly agree otherwise in writing.
Comment
See 8.54.8 for further discussion of why this Clause takes this approach.
4.7.1.6. There's no guarantee of minimum work or -payment.
Unless the Contract expressly states otherwise, the Contract does not entitle Provider to a certain minimum amount of work or compensation over and above that set forth in one or more agreed statements of work.
Comment
This is a roadblock provision; it's included because it's not unheard of for a service provider to claim that a customer had supposedly agreed to give the provider a certain minimum amount of billable work or of compensation.
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), affirming520 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).
4.7.1.7. The Provider assumes the risk of scoping out the conditions "on the ground."
In connection with the amount of work that the Provider must to to perform the services and the Provider's cost of of such work: The Provider ASSUMES THE RISK that the relevant existing conditions are NOT as contemplated in the statement of work.
In case a question comes up: The Provider is not assuming the risk of any harm to the Customer from those conditions not being as so contemplated.
Comment
A. The Provider's responsibility for verifying the initial conditions "on the ground" would mean that the Provider likely wouldn't be paid for unexpected extra work even if the Customer orally promised to pay after discovering the need for the 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).
B. Presumably a smart Provider, in pricing the proposed work, would take this "investigation risk" into account.
4.7.1.8. Change orders will only be effective by clear agreement.
An accepted order between Provider and Customer is modifiable only by agreement of (at least) the party sought to be bound — such a modification is referred to as a "change order."
No party is to assert that a change order has been agreed without offering, as evidence:
the other party's written agreement to the change order; or
clear and convincing evidence of the other party's agreement to the change order — with reasonable corroboration of any testimony by interested parties.
Comment
A. 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. For that reason, this section takes the same general approach as Clause 6.1 (amendments). That approach is especially appropriate for statements of work, which can "evolve" as a project progresses.
B. Subdivision 1: By requiring agreement only by the party sought to be bound, this section follows the general philosophy reflected at Clause 6.1.
Override: "A written change order must be agreed to by all parties to the statement of work." (This could be problematic, for reasons discussed at 30.15 in relation to needlessly "raising the bar" for the parties.)
4.7.1.9. Apparent authority is enough to approve a change order.
Anyone with "apparent authority" may agree to modify a statement of work — that is, unless the Contract or the statement of work specifically limited who could agree to modifications.
4.7.1.10. Disputes about SOWs are to be escalated.
The parties will address any dispute between them about a statement of work by escalation to a neutral as stated in Clause 6.4.
Comment
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 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 8.28; the parties settled, with Oracle agreeing to pay Oregon $25 million in cash and provide the state with another $75 million in technology.
This section 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.
4.7.1.11. Who is to get any required licenses and permits?
4.7.1.13. The Provider must "paper up" its personnel obligations.
The Provider is to see to it that each individual involved in performing services under the Contract is legally bound by personal obligations that are sufficient to support any corresponding obligations that the Provider has under the Contract.
Example: The individuals' personal obligations referred to in subdivision 1 include, without limitation, any applicable obligations of:
of confidentiality and/or
to assign ownership of inventions.
For the avoidance of doubt:
The Provider's obligations under subdivision 1 apply to the relevant employees of both the Provider and the Provider's subcontractors (if any); but
This section neither authorizes nor prohibits the Provider's use of subcontractors.
Comment
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.
4.7.1.15. Site-visit and computer-access compliance
If any party's personnel will be physically present at premises controlled by another party to the Contract, then the parties will follow Clause 8.63.
If any party's personnel will access one or more computers or network controlled by the another party to the Contract, then the parties will follow Clause 8.17.
Comment
See the commentary to the listed provisions.
4.7.1.16. Ownership of resulting new IP
This section will govern unless clearly agreed otherwise in the relevant statement of work.
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 Clause 8.39.
The Customer will have a license (as defined at Clause 8.38.4), under the Provider's IP rights in any such New IP, to use the New IP in a manner consistent with the statement of work.
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 Clause 8.39 to confirm the Customer's ownership.
Comment
See the commentary there.
4.7.1.17. Procedure for IP infringement claims by third parties
This section will apply if a third party asserts that a deliverable under a statement of work infringes intellectual property rights assertable by the third party.
The Provider and Customer will address the third party's assertion as set forth in Clause 8.36, with the Provider being the "Supplier."
4.7.2.1. Courts might ignore writing requirements for change orders.
Caution: Courts are sometimes willing to hold that writing requirements for change orders have been 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. 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; cleaned up).
4.7.2.2. Send a confirmation email for oral change orders?
A. To play it safe, each party that wants to rely on a change to a statement of work should assume that only a written modification agreement would be given effect. At the very least, it'd be good for one party to send the other party an email summarizing the agreed modification and confirming that both parties agreed to it — that way, if the other party doesn't object within a reasonable time, the email will help corroborate that the parties did in fact agree orally to the modification.
B. Pro tip: An email confirmation of an agreed change order might be safer than a text message, because text messages might end up being deleted automatically after a certain number of days — see also 25.2, about California law's citation of that reason for excluding text messages from serving as written agreements in certain real-estate matters.
Example:Not sending such a confirming message 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 was not 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).
C. It's not uncommon for the need for extra work to be discovered in the course of doing the agreed work. A contractor might believe that its customer had orally agreed to pay for the extra work — but a court might not share that belief and thus might decline to award damages for nonpayment. Example:Shift Services (N.D. 2023). Shift Services, LLC, v. Ames Savage Water Solutions, LLC, 2023 ND 237 (affirming dismissal of breach of contract claim).
A. Drafters could try to roadblock arguments about apparent authority with language such as the following, to refute claims of reasonable reliance on the supposed apparent authority:
A written change order must be signed on behalf of [specify party name] by an officer of that party at the vice-president level or higher.
or:
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 Provider 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.)
B. Caution: A court might hold that such specific-authority requirements were waived. See, e.g., Patriot Constr., supra, 290 A.3d at 1117
4.8. Services: Charges and Billing
This Clause provides an SOP for billing services if the parties haven't agreed to a different billing arrangement.
Contents:
4.8.0.1. The Provider is to submit invoices as agreed
Provider is to cause invoices for payment under a statement of work to be issued as follows:
For services where a payment schedule is specified in the statement of work: As set forth in the statement of work.
For fixed-price services:One-half when all parties have signed the statement of work – to be treated as a deposit under Clause 2.6 – and the balance upon completion of the services.
For time- and/or materials-based billing:Once per month, in arrears.
Comment
A. On the general subject of invoices, see Clause 2.12.
B. A statement of work will often specify the payment schedule. Sometimes, though, parties neglect to include such information; for such cases, this section sets forth gap-filler terms.
C. Generally speaking, the Provider 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 Provider, 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 Provider's expenses, so that the Provider 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 Provider can stop work if the Customer doesn't pay (see 4.8.0.3).
The Customer, on the other hand, would prefer to hang on to its money until the Provider has finished its work — and perhaps even longer, to be sure that the Provider 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.)
D. Some providers might want to negotiate for a deposit to be applied to future invoices, in which case Clause 2.6 would apply.
E. Subdivision 3: "In arrears" means that invoices are sent after the end of the period being billed, as opposed to "in advance."
4.8.0.2. Payment terms
Customer is to pay each Provider invoice net 10 days from the Customer's receipt of the invoice, or as otherwise agreed, in accordance with Clause 2.14.
Comment
Net-10-day terms (see generally 20.1) seem to be fairly typical for services agreements, especially for smaller service providers; in some cases the payment terms are "due on receipt."
4.8.0.3. The Provider has the right to go "pencils down!"
This section will apply if the Provider does not timely receive an invoiced payment.
The Provider may suspend work — its own or, if applicable, that of one or more subcontractors — pending receipt of payment, but only after giving reasonable advance notice to the Customer.
The Provider has no responsibility for any financial impact or other harm to the Customer that results from the Provider's suspension of work under this section.
This section, in itself, neither authorizes nor prohibits Provider's use of subcontractors.
Comment
A. Suspension of work — or, "pencils down!" as the administrator of the present author's former law firm used to say for clients with past-due accounts — is sometimes just about the only leverage that a provider has against a slow-paying customer.
B. Caution: Sometimes the service in question might be critical to Customer's operations — in which case Customer might want to prohibit Provider from suspending the services without "due process" such as notice and an opportunity to cure; see, e.g., Option 4.12.2.15 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.
The Provider is not to bill the Customer for fees or expenses relating to the statement of work, over and above the Provider's agreed compensation as set forth in the statement of work.
In case the question comes up: Neither is the Provider allowed to bill anyone associated with the Customer, e.g., a Customer affiliate or employee, except as permitted by the statement of work.
Comment
A. Services providers generally incur expenses such as materials, rental of specialized equipment, and the like. Some statements of work might call for the provider to bill those expenses to the customer. Other, "total price" statements of work might require the provider to absorb those expenses as part of the provider's fee for services.
B. 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.)
4.8.0.5. Billing records?
This section will apply if the Provider is to be paid for services based on information maintained by the Provider and to which the Customer does not have independent access — for example, if the Provider charges by the hour.
The Provider is to keep records that meet the following standards:
the records are to be reasonably sufficient to support the Provider's invoices, for example, time records; and
the records are to be maintained in a commercially-reasonable form, with a view toward facilitating audits of the Provider's records (and thus making audits less costly for all concerned).
Comment
A. 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.
B. The Customer therefore might want to include, in the contract, requirements that the Provider set up systems to record and maintain data that can be used to corroborate timesheet data, such as by incorporating Clause 8.55. See, e.g., Time and materials (Wikipedia.com); Cost-plus pricing (Wikipedia.com).
c. Such data-collection systems 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).
4.8.0.6. Customer audit right?
Whenever the Provider is required to keep billing records under section 4.8.0.5, the Customer may have the records audited in accordance with commercially-reasonable practices — for example as described in Clause 2.3.
Comment
Concerning "commercially reasonable," see the related discussion of commercially-reasonable efforts at 7.15.
4.8.0.7. Subcontractor billing records
If the Provider uses subcontractors, then the Provider is to ensure that subcontractors agree to the same recordkeeping- and audit provisions as apply to the Provider.
For the avoidance of doubt: This section in itself neither authorizes nor prohibits the use of subcontractors.
Comment
Subdivision 2 is a roadblock provision.
4.9. Services: Licenses and Permits
This Clause 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.
This can be important in all kinds of transactions, services and otherwise: In one 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. Needless to say, 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 fly ball. See F.C. Bloxom Co. v. Tom Lange Co., 109 F.4th 925 (7th Cir. 2024), affirming642 F.Supp.3d 775 (C.D. Ill. 2022) (granting summary judgment).
4.9.0.1. The Provider is responsible for building permits, contractor licenses, etc.
Unless otherwise agreed, the Provider is to obtain any building permits, contractor- and other professional licenses, and all authorizations, of any kind, needed for the performance of the services.
Comment
A. For some services projects, the law might require, for example:
an occupational license for the provider, e.g., a contractor license; and/or
a permit for specific work itself, a building permit.
B. In probably the vast majority of tranactions, the Provider takes on the job of obtaining these work authorizations. That normally makes sense, because the Provider will presumably know the ropes of getting the permits better than the Customer.
C. Caution: Even starting work without a license could be very costly to the Provider, as discussed in more detail at 4.9.1.1
4.9.0.2. The Customer is responsible for any licenses, etc., to use deliverables.
Unless otherwise agreed, the Customer is to obtain any licenses (for example, patent licenses) and other authorizations needed for use of the deliverables — if any — other than for such use by the Provider and the Provider's agents and/or subcontractors.
4.9.0.3. Each party is to take care of related third-party claims.
Each party responsible for obtaining a particular authorization under this Clause is to do the following:
defend (as defined at Clause 3.4) the other party and its Protected Group against any claim made by the third party; and
indemnify (that is, reimburse), as stated in Clause 3.9, the other party and its Protected Group for all foreseeable damages, expenses, and losses resulting from the third-party claim.
Comment
A. 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 Clause 3.9.1.3.
B. 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.
C. Caution: While liability for breach of contract is limited to foreseeable lossses, Glenn West has suggested that the same might not be true for a contractual indemnity obligation, absent a specific contractual provision. 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
4.9.0.4. Procedure for disagreement about a license or permit
This section will apply if:
the Provider believes that a particular authorization is necessary, but
the Customer disagrees and wants the Provider to proceed without that authorization.
The Provider will not be in breach of the Contract if — with prompt notice to the Customer — the Provider suspends the relevant work until such time, if any, as the parties reach agreement or the Provider obtains the authorization in question.
Comment
A. This section provides a procedure for dealing with the situation in which, say:
a service provider thinks that a particular authorization is needed for a project;
but the Customer doesn't want to take the time or spend the money to obtain the authorization;
and the Provider doesn't want to go forward without the authorization, for fear that the Provider would incur legal liability.
B. If the parties aren't able to come to agreement on the point, then they should consider invoking the escalation protocol at Clause 6.4.
4.9.1.1. 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), citingWash. 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[.]")
4.9.1.2. Will the proper person be licensed for services?
Service providers should be sure that the proper individual, or the proper organizational party, is licensed. Example: In a California decision, a construction contract (allegedly) mistakenly listed an unlicensed contractor as the party that would do renovation work on a movie/restaurant, which led the owner to refuse to pay; the court of appeals held 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." 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).
4.9.1.3. Customers should procure their own patent licenses, etc.
A. Caution: Services contracts sometimes include a warranty by the provider that, in performing the services, the provider will not infringe any third party's IP rights.
The provider 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 19.3 concerning who is a "merchant." ]
But: Such provider 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."
B. So: In any services contract, both the provider 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.
C. 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).
4.9.1.4. 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.
4.10. Services: Optional terms
The following provisions will apply in the Contract only to the extent that the Contract expressly so states.
Either party (if the Contract or statement of work does not clearly state otherwise) may terminate a statement of work for an uncured material breach by the other party in accordance with Clause 5.7.
Unless clearly agreed otherwise, termination of a statement of work for material breach will be in addition to any other recourse available to the terminating party under the Contract, the statement of work, or the law (subject to any agreed limitations of liability).
Comment
A. Possible override language: See Option 4.12.2.15 (no suspension of services), which the Customer might want if the Provider is providing mission-critical services for the Customer's business.
B. Subdivision 2 is a "roadblock" provision, to discourage the Provider from trying to argue to the contrary.
4.10.2. Option: No Confidentiality Obligations
For the avoidance of doubt: Neither party has any confidentiality obligations relating to the services unless the Contract and/or the statement of work unambiguously says so.
Comment
This is likely to be overkill for many services agreements.
4.10.3. Option: Each Party's Confidentiality Obligations
Each party is to preserve in confidence the confidential information of the other party in accordance with Clause 8.18.
4.10.4. Option: Confidentiality Obligations After Termination
In case of doubt: Upon any termination or expiration of a statement of work, each party will continue to honor any agreed confidentiality obligations.
4.10.4.1. Comment
This is a comfort clause sometimes wanted by parties that expect to disclose confidential information.
4.10.5. Option: Expiration of a Statement of Work as Termination
For purposes of post-termination obligations, expiration of a statement of work will be considered a form of termination.
Comment
Sometimes this can be a disputed point. (Author's note: I thought I'd saved a citation to a court case on point, but I can't find it in my notes.)
Provider will see to it that the services are performed:
from start to finish;
in a safe, diligent, and "professional" manner (defined in subdivision 2 below),
as set forth in the statement of work,
in accordance with: (i) the agreed written statement of work; and (ii) any clearly-relevant industry- or professional standards;
all at the Provider's own expense except as clearly agreed otherwise in writing.
For purposes of this Clause, 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.
4.11.2. Comment
A. Subdivision 1: The phrase, "see to it" takes into account that the Provider 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 [TO DO: LINK].)
B. Subdivision 1: 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 3.18.
C. Subdivision 1.a: 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."
D. Subdivision 2'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 inEwing Constr. Co. v. Amerisure Ins. Co., 420 S.W.3d 30, 37 (Tex. 2014) (responding to certified question from Fifth Circuit).
E. Subdivision 2 — 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 Clause 7.7).
F. Subdivision 2: 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.
G. Relatedly: In some circumstances in some jurisdictions, the law might impose an implied warranty of workmanlike performance (concerning which, see 3.8.4).
4.11.3. Personnel suitably trained, employable, etc.
The Provider will see to it that the services are performed by people:
who have suitable training, experience, and supervision; and
are legally eligible to be employed in the relevant capacity under (without limitation) applicable laws governing (i) immigration, and (ii) export controls.
4.11.4. Comment
A. A requirement for personnel qualifications can make life simpler for customers in case of problems. Example: Suppose that you, the reader, are considering signing a contract with Scalpels 'R Us, LLC, to do lifesaving surgery on a loved one.
At a minimum, you'd want to know that the actual surgeon, the specific individual who would be opening up 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 right, and so you shouldn't concern yourself 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).
An explicit personnel-qualifications requirement can serve as a reminder to Scalpels 'R Us about whom the provider should pick to do the surgery.
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.
B. Example: 1999, 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."
C. Example: In a 2019 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).] ]
D. 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.
A lay jury, untrained in medical science, might have a tough time judging whether or not the surgical procedure had been performed correctly.
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.
E. Subdivision 2 — caution: See the discussion at 13.11 concerning the critical importance of complying with export-control laws, because 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 ….
4.11.5. Provider procurement of materials, etc.
Unless the statement of work clearly states otherwise, the Provider will see to the timely acquisition, installation, and maintenance of whatever might be needed for performance of the services, including but not limited to the following:
necessary materials, including but not limited to equipment and/or tools;
suitable workspace;
electrical power;
computer hardware and -software;
Internet- and other communications capabilities;
safety equipment for the Provider's people; this would include, for example, any necessary personal protective equipment (PPE); and
all other tangible- and intangible items needed to meet Provider's performance responsibilities.
4.11.6. Comment
A. When the Customer hires the Provider, the Customer generally doesn't want to be continually asked by the Provider'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 Provider's occasionally asking the Customer for things shouldn't be a problem in a cooperative business relationship.)
B. 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."
4.11.7. Provider site prep and clean-up
The Provider is to see to any necessary preparation- and clean-up of work areas at any Customer site where services are performed.
4.11.8. Comment
Some customers want explicit language to this effect in their services contracts.
4.11.9. Defect handling
This section will apply if the Customer reports to the Provider that one or more defects exists in services and/or deliverables under a statement of work.
The Provider (primarily) and the Customer (with limited obligations) are to address the reported defects in accordance with the "Three Rs" protocol — in a nutshell: repair, replace, or refund — at Clause 4.1.
4.11.10. Comment
In some specialized situations, the Customer might want to lay out more-detailed plans of action for dealing with defects in deliverables — possibly in table form, such as the following hypothetical example (which is sanitized from an actual software-development contract negotiated for a client by the present author):
4.11.11. Provider control of "means and manner"
As between the Provider and the Customer, the Provider has the exclusive right — and the exclusive responsibility — to control the means and manner by which the services are performed.
4.11.12. Comment
A. Language such as this is typically included to bolster the argument (by the Customer, usually) that the Provider and its personnel are not Customer employees; see generally the commentary to Clause 6.8: Independent-Contractor Clause.
B. Concerning "As between the Provider and the Customer," see 9.6.
4.11.13. Reasonable Customer cooperation is required.
This section will apply if the Provider makes any reasonable request for relatively-minor cooperation by Customer in connection with a statement of work.
The Customer is to provide the requested cooperation — but to be clear: the Provider remains responsible for completing the work except as clearly agreed otherwise.
Whether a request for cooperation is reasonable might depend in part on whether the Provider offers to pay or reimburse the Customer for associated expenses.
4.11.14. Comment
In many situations the Customer might well have to do something as simple as (for example) opening a locked gate to allow the Provider's personnel to come onto the Customer's premises.
4.11.15. "Time is of the essence"?
This section will apply if the Provider misses a deadline or other target date set forth in an agreed statement of work.
The Provider's missing of such a target date is a breach of Provider'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.
4.11.16. Comment
Concerning "material breach," see generally the definition at Clause 7.33.
This section 4.12 will apply if a statement of work is terminated (including, for this purpose, expiration), except to the extent (if any) that the parties agree otherwise in writing either:
in the statement of work, or
at substantially the time of termination,
that is, not in either party's pre-printed terms.
Comment
This section 4.12 reflects the reality that when a statement of work is terminated, it's not unlikely that the Customer is "pulling the plug" — typically because of dissatisfaction with the Provider'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 Provider to be explicitly obligated to turn over all undelivered deliverables and work-in-progress; but
the Provider won't want the Customer to try to obtain concessions by inappropriately withholding final payments.
4.12.0.2. Deliveries upon termination
In addition to anything else specified in the statement of work, the Provider is to promptly deliver the following to the Customer (or to the Customer's designee):
all completed deliverables and work-in-progress that are called for by that statement of work — those, however, remain subject to any agreed restrictions on providing them to competitors of the Provider;
any materials (e.g., equipment) that were provided or paid for by (or on behalf of) the Customer for use in connection with that statement of work;
any Customer-owned data that was provided by or on behalf of the Customer;
any Customer-owned data that was generated by or on behalf of the Provider in connection with that statement of work; and
one or more final invoices for the statement of work.
Comment
This can function as a sort of post-termination checklist for Provider (and Customer.
4.12.0.3. Customer obligations upon termination
In addition to anything else specified in the statement of work, the Customer is to do the following:
pay any final amounts due in accordance with the agreed payment terms — except as provided at section 4.12.0.4 below; and
allow the Provider to remove, from Customer-controlled premises, any Provider-furnished materials (e.g., equipment), except to the extent that the statement of work clearly contemplated that particular materials would be left behind.
In case the question comes up: Customer's payment obligations under subdivision a.1 above include, without limitation, the following to the extent applicable:
paying amounts due under all then-pending Provider invoices; and
paying amounts due under the Provider's subsequent final invoice(s), if any, for previously unbilled services and (if applicable) reimbursable expenses.
4.12.0.4. Exceptions to Customer's final-payment obligation
The Customer's payment obligation under section 4.12.0.3 above would apply only to the extent it is not inconsistent with any payment prerequisites in the statement of work.
Hypothetical example: Suppose that:
the statement of work says that the Customer will pay Amount A after a particular Milestone M is achieved; and
Milestone M has not happened when the statement of work is terminated (or expires).
In that situation, the Customer need not pay Amount A.
4.12.0.5. General cooperation in wrap-up
Each party is to provide commercially-reasonable cooperation with the other party in completing the wrap-up of the statement of work.
4.12.1. Services options: Provider playbook
The following provisions will apply in the Contract only to the extent that the Contract expressly so states.
4.12.1.1. Option: Suspension of Customer's Rights for Nonpayment
The Customer's failure to pay any amount required by the applicable statement of work — after expiration of the relevant cure period, if applicable — will automatically suspend the Customer's rights concerning the relevant deliverable.
4.12.1.2. Comment
A. If Provider's intellectual property ("IP") is being licensed to Customer, and Customer fails to pay an amount due, then Provider might want eventually to be able to "drop the hammer" by suspending Customer's right to use the IP — and thereby making Customer an infringer of Provider's IP rights, giving rise to the possibility of significantly-greater damages liability than merely not paying.
B. See also the related discussion at 2.14.10.16 (stating that late payment does not in itself result in IP infringement).
4.12.1.3. Option: No Use of Deliverables by Others
The Customer is not to allow others (including without limitation the Customer's other contractors) to use deliverables provided by or on behalf of the Provider under a statement of work — not even if such use by others is for the Customer's own business purposes.
4.12.1.4. Comment
In one type of services project, the Provider is a software developer, where the Provider creates a custom version of the Provider's own software package for a particular Customer, and the Provider retains the ownership rights in the custom version.
In such a situation, the Provider might well want to preclude the Customer from allowing third parties to use the software, for economic reasons and/or to preserve the Provider's trade-secret rights in the software.
4.12.1.7. Option: Provider Withholding of Final Deliveries
This Option will apply if the Provider's already-sent invoices — for any statement of work — are past due when any statement of work is terminated.
In that situation, the Provider may delay delivery of some or all post-termination deliverables, for some or all statements of work, until all of the Provider's past-due invoices are paid in full.
4.12.1.8. Comment
This gives the Provider 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.
4.12.2.1. Option: Stipulated List of Provider Material Breaches
Any of the following breaches by the Provider — if proved — would be "material" for purposes of the Contract:
The Provider 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 Provider does start performance.
The Provider clearly and permanently abandons performance.
The Provider temporarily suspends performance, if the Contract or the statement of work prohibits suspension.
The Provider does not timely complete the services, in compliance with the standards set forth in the Contract and/or the statement of work, if the parties have clearly agreed in writing that timeliness of completion is important.
For the avoidance of doubt, this Option does not rule out the possibility that other types of breach by the Provider might also be material.
4.12.2.2. Comment
As discussed in more detail at section 7.33.1, courts generally go along with contractual stipulations that particular breaches are to be considered "material."
4.12.2.3. Option: Personnel Changes at Customer Request
Except as provided in subdivision 2: Whenever the Customer reasonably requests it, the Provider is to remove and replace any individual under the Provider's control from performing services under the Contract.
The Provider 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).
Apart from the good-cause exception in subdivision 4 below, the Provider 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.
Exception: The Provider is not to 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 dispute is to be addressed by (non-binding) escalation as stated at 6.4.
If such a removed individual complains — or sues the Provider, in any forum, alleging — that the removal was unlawful, then:
The Customer is not to assert that, by complying with the Customer's removal request, the Provider (i) agreed that the removal was lawful, nor (ii) waived the Customer's defense- and indemnity obligations under this Clause.
4.12.2.4. Comment
A. Customers' service-agreement forms often include language giving the Customer the right to demand that the service provider kick someone off a project.
B. Caution: It's not unheard-of for a bad-actor Customer representative to demand that a Provider-employee be kicked off a project, for example —
because the Customer representative was biased against people of the Provider-employee's race, ethnicity, etc.; or
to retaliate against the Provider-employee for rebuffing sexual advances.
C. Subdivision 4: Whether "good cause" exists is sometimes disputed. Example: In a 2019 Houston court of appeals decision, 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).
4.12.2.5. Option: Customer Further Development of Deliverables
This Option presupposes that the Provider will be furnishing one or more deliverables to the Customer.
The Provider is not to 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 Contract:
modifying or otherwise continuing development of any deliverable; and/or
having the same done by others on behalf of the Customer.
But: Whether the Provider is required to provide support for its deliverable, after someone else has modified it, is up to the Provider's sole discretion.
The Customer is to see it that any deliverable-related modification- or development activity under this Option, by the Customer or on its behalf, does not violate:
applicable law such as (without limitation) export-controls laws;
any unrelated rights assertable by the Provider such as (without limitation), intellectual-property rights, if any;
any applicable third-party rights, e.g., patent rights or copyrights; nor
any additional restrictions unambiguously agreed to in writing.
4.12.2.6. Comment
A. If the Customer hires the Provider to build something, the Customer generally won't want to be forever locked into using the same Provider to improve- or build on it. But: The Customer's further development might violate the Provider's intellectual-property rights, e.g., if building on the Provider's work product constitutes creating a "derivative work" of a copyrighted work of authorship created by the Provider.
B. This Option 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 8.21.)
C. Subdivision 3 addresses the (likely) Provider concerns that:
The Provider doesn't want to take responsibility for fixing other developers' screw-ups;
The Provider might prefer that it be paid for futher development; and
The Provider might be concerned about revealing the Provider's trade secrets to other developers.
4.12.2.7. Option: Termination at Will by Customer
The Customer may terminate a statement of work "at will" (synonym: "for the Customer's convenience") effective immediately upon written notice to the Provider.
If the Customer does terminate a statement of work at will, then each party is to comply with Clause 4.12.
In case of doubt, this Option neither authorizes nor prohibits termination at will of a statement of work by the Provider.
4.12.2.8. Comment
A. 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.
B. On the other hand, many Customers probably won't want a services Provider to have the right to terminate at will, possibly leaving the Customer in the lurch for something important.
C. Caution: Providers should be wary of Customer termination at will. That's because a sudden termination at will by the Customer might leave the Provider holding the bag for unrecoverable costs (past and/or future).
For example:
Suppose that the Provider, upon agreeing to a statement of work, had invested money to find, recruit, and train extra people to do the work.
Or perhaps the Provider 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 Provider 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.
D. Pro tip: Because of the problems discussed just above, the Provider might want to try to negotiate limits on the Customer's right to terminate a statement of work at will, such as (for example):
an earliest permissible date for termination-at-will, so that the Customer's payments would cover at least some of the Provider's investment(s);
a minimum advance-notice period, for the same reason, and to give the Provider time to find other work for the provider's people who were assigned to the Customer's project; and/or
an early-termination fee that the Customer must pay if the Customer were to terminate at will before specified dates and/or milestones were reached.
4.12.2.9. Option: Customer Ownership of IP
As between the Customer and the Provider, it is the Customer, not the Provider, that will own the intellectual-property rights, if any, in and to any deliverables that are created:
in the performance of the Provider's obligations under a statement of work,
by one or more employees of the Provider (and/or of the Provider's subcontractors, if any).
The Provider is to 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:
in writing, and
in as much detail as the Customer reasonably requests,
so that the Customer becomes aware that it is entitled to ownership of specific Provider work product and determine what if any legal protection might be available.
If so requested by the Customer, the parties will follow Clause 8.39 to help establish, confirm, and/or register the Customer's ownership claim(s) under this Clause.
4.12.2.10. Comment
A. Concerning IP ownership resulting from the services (and its economics), see generally 4.7.1.16.
B. Subdivision 2 addresses the fact that it's not entirely unheard of for a Provider 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.
4.12.2.11. Option: Background Checks Requirement
This Option will apply to each individual who, in connection with a statement of work:
is employed by the Provider (and/or the Provider's subcontractors, if applicable); and
will have access to (i) the Customer's physical premises and/or (ii) the Customer's computer system(s).
The Provider is to see to it that each such individual — before gaining such access — has had a background check completed, with satisfactory results, in accordance with Clause 8.6.
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.
4.12.2.12. Comment
A. Sometimes the Provider's people will be gaining access to very-sensitive Customer information, or to potentially-vulnerable Customer facilities. Often, in such situations the Customer might want to require background checks on the relevant Provider personnel. (See also the background-checks protocol at Clause 8.6 and its commentary.)
B. Subdivision 3: Depending on the circumstances, the two-year time frame might be a subject for discussion by the parties.
4.12.2.13. Option: Provider Availability for Meetings
The Provider is to make itself reasonably available from time to time for meetings and phone calls concerning the services as reasonably requested by the Customer.
In case of doubt: The Provider’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.
4.12.2.14. Comment
This is set up as an option and not a rule. That's because the Provider will often have an economic incentive to make itself available to the Customer — but not always, because the Customer's business could be less important to the Provider than that of the Provider's other customers.
4.12.2.15. Option: No Suspension of Services by Provider
This Option is agreed to because of the importance to the Customer of timely uninterrupted services under the Contract.
The Provider must 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 Clause 6.9.
4.12.2.16. Comment
The prefatory language, "… because of the importance …," 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 3.12.1.4.
4.12.2.17. Option: Customer Right to Reduce Work Scope
The Customer retains 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" that work).
In case of doubt: The Customer's de-scoping right extends, without limitation, to reassigning work to a service provider other than the Provider, for any reason or no reason.
For any work item being de-scoped by the Customer under this Clause:
If the statement of work sets out itemized compensation for that work item, then the Provider's compensation is to be reduced by that itemized amount.
Otherwise, Provider's compensation is to be reduced equitably, with any persistent disagreements being addressed by (non-binding) escalation in accordance with Clause 6.4.
B. Subdivision 3 follows the guideline, "If you can't agree in advance about outcome, then try to agree about process."
C. Subdivision 3 — appendix: See the Honeywell change-order language reproduced at 8.54.11.5 for an example of Customer-drafted terms that give the Customer considerable authority to impose change orders on the Provider.
4.12.2.19. Option: Provider Mitigation of Schedule Slips
This Option will apply if:
A statement of work clearly states that a particular milestone: (i) is material, and (ii) must be completed by a specified date; and
that milestone is not completed by the specified date.
The Provider must make efforts that are reasonable under the circumstances:
to mitigate any harm resulting from the delay; and
to get the work back on schedule.
4.12.2.20. Comment
A. 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.
In fact: There's an old joke in the software world that "The first 90 percent of the code [i.e., the software being developed] accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time." See Ninety-ninety rule (Wikipedia.com) (attributed to Tom Cargill of Bell Labs).
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.
B. Subdivision 2 does not require "best efforts," for reasons discussed in the commentary at Clause 7.7.
The Provider is to preserve the Customer's confidential information in confidence in accordance with Clause 8.18.
4.12.2.22. Comment
A. In some services agreements, the Provider 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.
B. But: On the other side of the coin, in some services agreements, the Customer might gain access to confidential information of the Provider, e.g., in the form of the Provider's proprietary computer software or data.
4.12.2.23. Option: No Charge by Provider for Customer's Deliverables Use
The Provider is not to seek payment from the Customer for the Customer's use of a deliverable resulting from services under the Contract.
4.12.2.24. Comment
If the Customer is a "nervous Nellie," the Customer might want language like the above, so as to be absolutely certain that the Provider wouldn't try to charge the Customer more than agreed.
4.12.2.25. Option: Customer Withholding of Post-Termination Payments
Upon termination of a statement of work, the Customer need not pay the Provider's final invoice(s) for then-unbilled services, if any, until the Provider has complied with its applicable post-termination obligations for that statement of work, if any.
4.12.2.26. Comment
Some customers might want this Clause to give them more leverage in a termination situation.
4.12.2.27. Option: Final-Payment Adjustment for Material Breach
This Option will apply if the Customer terminates a statement of work for material breach by the Provider.
The Customer's final payment obligation is to be adjusted appropriately, based on the circumstances.
Any disagreement about such an adjustment is to be addressed by (non-binding) escalation as stated at Clause 6.4.
4.12.2.28. Comment
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 Clause 4.7.1.10.
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. (The term "good and workmanlike" means the same thing.)
4.13.2.1. Business context: A practical, real-world standard
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.
4.13.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 inEwing Constr. Co. v. Amerisure Ins. Co., 420 S.W.3d 30, 37 (Tex. 2014) (responding to certified question from Fifth Circuit).
The term "proficient" could be thought of as "competent and skilled but not necessarily innovative or outstanding." An online dictionary, from Cambridge University Press, defines the term as "skilled and experienced" (dictionary.cambridge.org). From another: "well-advanced or competent in any art, science, or subject; skilled" (dictionary.com). • One online dictionary, however, goes further, defining the term as "able to do something to a higher than average standard : SKILLED" (merriam-webster.com).
4.13.2.3. A practical, real-world standard
The above definition of workmanlike looks to the real world of successful practice in the field in question to serve as a yardstick (or meter stick).
4.13.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).
4.13.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.
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 8.18.24).
• 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).
5.1.1.1. What terms will survive termination or expiration?
Unless the Contract clearly says otherwise, each provision of the Contract (if any) that falls in one or more the following categories will survive any termination or expiration of the Contract:
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;
audits;
confidentiality;
defense against third-party claims;
dispute management;
indemnification;
insurance requirements;
intellectual-property ownership;
non-competition;
non-solicitation;
representations, warranties, and disclaimers of the same;
warranty rights.
5.1.1.2. What about claims for breach before termination or expiration?
Claims for breach of the Contract before termination or expiration will also survive.
5.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. 5.1.5
5.1.2. The wording of a survival clause could be crucial
Example: In the Eighth Circuit's 2021 Miller decision, an employee terminated her employment agreement, as that agreement expressly allowed her to do. To the employer's surprise, the termination had the side effect of terminating her contractual obligation not to compete with her former employer. That's because the noncompetition covenant stated that it would survive termination of employment, but it did not state that it would survive termination of the employment agreement — so, when the employment agreement was terminated, the noncompete died with it. See Miller v. Honkamp Krueger Fin. Svcs., Inc., 9 F.4th 1011 (8th Cir. 2021) (vacating preliminary injunction).
5.1.3. 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.
5.1.4. 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).
5.1.5. 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.]
Every contractual relationship will come to an end eventually: by the completion of the transaction, the passage of time, the disappearance of one or both parties, or the action of one or both parties. So, contracting parties should ideally try to plan for orderly winding up of their relationship by considering what actions each side might want to require the other party to take. Toward that end, this Clause sets out fairly-standard ground rules for termination or expiration.
A party "T" that has a right to terminate the Contract may instead terminate one or more of the following specific items, to the extent that such items exist under the Contract:
transactions, for example, a purchase order or a statement of work for services;
grants, for example, a leasehold interest or a license;
relationships, for example, a distributorship; and/or
exclusivity of a grant.
Comment
Terminate just a transaction, etc.? Drafters should think about whether termination of the Contract is what the client really wants, as opposed to just terminating selected rights and/or obligations under the Contract.
Comment
Terminating just exclusivity? 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.
5.2.1.2. What rights and obligations would exist after termination?
The Contract may require one or more parties to take certain actions, or to have other rights or obligations, upon a termination.
5.2.1.3. Expiration counts as a type of termination
In case of doubt:
Any expiration of the term of the Contract — or, if applicable, expiration of a transaction, grant, or relationship under the Contract — will have the same effect as a termination unless otherwise unambiguously clear from the context.
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 provision.
A notice of an upcoming expiration is not needed for the expiration to be effective unless the Contract clearly requires otherwise — for example, with an evergreen-extension provision. 6.6
5.2.1.4. What general effects would termination have?
Any termination would:
cancel the parties' relevant, respective, post-termination rights and obligations, except to the extent (if any) that the Contract provides otherwise — for example in a survival provision such as 5.1;
cancel any right a party has to continue performance of its relevant pre-termination obligations; and
not affect any party's claim for pre-termination breach, nor any related rights or remedies, except to the extent, if any, that the Contract clearly provided otherwise.
Comment
Cancelation of right to continue performance: This 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).
Comment
No effect on pre-termination breach, etc.": 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).
5.2.1.5. Would any party be liable for the termination itself?
Neither party will owe another party money solely because of termination of the Contract in accordance with its termination provisions, unless the Contract clearly specifies otherwise — for example (hypothetically) if the Contract requires a terminating party to pay a specified fee in case of termination before a stated time.
Comment
No liability for termination per se: This doesn't mean that a party might not be liable: (1) under other provisions of the Contract; (2) for breach of an obligation under the Contract; and/or (3) for wrongfully terminating the Contract when the terminating party wasn't entitled to do so — see "own goal" wrongful termination at 5.2.5.
5.2.1.6. A terminating party may later invoke backup grounds for termination
If a party terminates the Contract, or a transaction or relationship under the Contract, for a stated reason (e.g., an alleged breach); but the stated reason later is found not to have been applicable (e.g., a court finds that an alleged breach was not proved and/or did not give rise to a right to terminate); then the termination is to be deemed to have been made for any other reason that, at the time of termination, would also have allowed termination under the Contract (e.g., if the terminating party could have terminated at will).
Comment
Alternative grounds for termination: This 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).
(For more discussion of "own goal" wrongful terminations, see 5.2.5.)
5.2.1.7. Option: Termination Cross-Default Right
If this Option is agreed to, and a party "TP" is entitled to terminate one transaction, grant, or relationship for material breach by another party "BP," then TP may, in its sole discretion, terminate some or all other uncompleted transactions, grants, or relationships between TP and BP.
Comment
Termination 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.
5.2.2. Could termination have undesired side effects?
A right to terminate the Contract could have unexpected (and undesired) results; for example:
Example: An employee terminated her employment agreement — as that agreement expressly allowed her to do. To the employer's surprise, that had the effect of terminating her 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: 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 8.18.24.
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.
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." That's because in one case, the contract's termination-for-breach provision referred to the right of the non-breaching party to terminate. That, said the court, meant that the party that had purported to terminate the contract did not have the power to do so — because that party was itself in breach, of a different 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).
5.2.4. Motive: Termination for "breach" to chase after another partner?
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 Hess Energy v. Lightning Oil case cited at 5.2.5 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).
5.2.5. Caution: Don't do an own-goal termination for breach
Improper termination of a contract for breach could itself be an "own goal" breach of contract.
(A widely-used dictionary 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" (Merriam-Webster.com).)
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 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, and thus a breach in itself.
Example: This was the result in a case where a party that terminated a contract was held liable for millions of dollars in damages for doing so. See Southland Metals, Inc. v. American Castings, LLC, 800 F.3d 452 (8th Cir. 2015) (affirming judgment on jury verdict).
Example: In another case, 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. 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 5.2.4, concerning assignment without consent as a material breach.
Example: In a Houston case:
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. 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) (edited).
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).
5.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 Clause 4.12
issuance of final invoices
payment of outstanding amounts
return of confidential information, if applicable (see Clause 8.19.1);
continuing confidentiality obligations (see Clause 8.18);
preparation and signing of intellectual-property assignment documents (see Clause 8.39);
a provider's obligation to help a customer transition to another provider (see Clause 4.12).
Relatedly, drafters can also consider Termination Wrap Up (5.11), which allows parties a limited period of time after termination to complete certain pending business.
5.2.7. Golden State Warriors: An example of expiration vs. termination
One example of expiration-as-termination attracted considerable local publicity in a 2020 case in the San Francisco Bay Area in California, where:
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.
An arbitrator held that the lease's expiration due to nonrenewal was tantamount to a termination by the Warriors.
That termination triggered an obligation for the team to continue making payments on debt incurred by the government agency that owned the Coliseum.
A party clearly specified in the Contract (each party, if not otherwise specified) may terminate "at will" or "for convenience" — the two quoted terms are intended to be essentially synonyms — the following:
the Contract, and/or
one or more transactions or relationships resulting from the Contract.
5.3.1.2. Are there any limits on termination at will?
Absent a clear restriction in the Contract, a party entitled to terminate at will may do so:
at any time before the Contract has expired or otherwise been terminated; and
5.3.2. Caution: Would agreeing to this this 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."
5.3.3. Negotiate restrictions on termination at-will?
A party that will be making a significant investment of time or money in the Contract might want to try to negotiate restrictions on the other party's right to terminate at will, so as to allow the investing party 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;
after one or another party has achieved specified performance targets;
if the terminating party pays a specified buyout fee; and/or
for good reason (preferably but not necessarily specified in the Contract).
5.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. …
(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.)
5.3.5. 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: 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 Tenth Circuit 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).
(Author's note: As a 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.37discussed inEngineered Sales Co., 980 F.3d 597 (8th Cir. 2020).
5.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.
5.4. Termination for Change of Control
A party to a contract "T" might want the right to terminate the contract (or a purchase order, or a statement of work, etc.) if the other party "OP" undergoes a "change of control" — for example being acquired by one of T's competitors.
This could be especially true if the contract calls for TP to share its trade secrets or other proprietary information with OP party, because of the fear that T's acquiring competitor might gain access to T's information.
5.4.1.1. Who may terminate for a change of control?
Either party, referred to as "TP," may terminate the Contract if the other party, "OP," has a "change of control" (as defined below).
5.4.1.2. When would the termination take effect?
Termination will be effective immediately when TP's notice of termination to OP becomes effective in accordance with Clause 6.9.
5.4.1.3. Is there a deadline for termination?
If not sooner exercised, T's right to terminate under this Clause will expire automatically 5.5.1.2 if TP's notice of termination to OP has not become effective on or before:
three months after the date that TP first learns, via any source, or reasonably should have known, that OP's change of control has become effective; or
six months after the effective date of the change of control.
Comment
Termination deadline: The party that underwent a change of control might argue that it shouldn't have to live forever under a Sword of Damocles — and that if the terminating party can't be bothered to terminate before the stated deadline, then the change of control likely didn't harm the terminating party that much.
5.4.1.4. What would constitute a change of control?
For purposes of this Clause, the term "change of control" refers 5.4.2 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).
5.4.2. Comment: A longer definition of "change of control"
At the lawyers-only site redline.net (recommended!), an anonymous poster says: "[The following] clauses are taken from a well-known and large Silicon Valley law firm, from their flagship Technology License Agreement template–so they must be good, right?" (Um ….)
"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.
(Lightly edited.)
5.5. Termination for Insolvency
See the notes at 10.3 about the effect of bankruptcy on contracts under the (U.S.) Bankruptcy Code of 1978.
5.5.1. Clause text
When this Clause is agreed to in writing:
5.5.1.1. Applicability of this Clause
A party clearly identified in the Contract ("T") may terminate the Contract, effective immediately upon notice to the other party ("OP"), if one or more of the following things occurs:
OP ceases to do business in the normal course;
OP becomes insolvent;
OP admits in writing its inability to meet its debts or other obligations as they become due;
OP makes a general assignment for the benefit of creditors;
OP files a voluntary petition for protection under the bankruptcy laws 10.3 or similar laws of the relevant jurisdiction, or to effect a plan or other arrangement with creditors;
OP 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
OP has a receiver, administrative receiver, administrator, liquidator, trustee in bankruptcy, or similar functionary in the relevant jurisdiction, appointed for OP's business or assets.
5.5.1.2. Is there a deadline for termination?
If not sooner exercised, T's right to terminate under this Clause will expire automatically if TP's notice of termination to OP under section [BROKEN LINK: termin-br-events] above has not become effective in accordance with Clause 6.9 on or before the later of the following:
the date three months after the date that TP first learned, via any source, or reasonably should have known, of the most-recent event coming within one or more of the categories listed in section [BROKEN LINK: termin-br-events] above; or
if earlier, the date six months after the date of that most-recent event, regardless when, or whether, TP learned or should have known about that event.
Comment
Three-month termination period: This forces the terminating party TP 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.
Comment
Three-month deadline: This 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 Clause 7.34.
Comment
Start of "shot clock" for termination: This termination period starts when TP first learns of the triggering event affecting the other party OP.
To be sure: TP might prefer for its termination countdown clock to start running only upon formal notice of the triggering event from OP. That, though, might be too burdensome for OP to manage.
Comment
Six-month deadline: This "outside" termination deadline has in mind that if TP hasn't seen fit to terminate within that time — for example, because TP simply hasn't noticed any material ill effects from a triggering event — then TP's right to terminate should lapse.
5.6. Termination for Legal Violation
This Clause gives a party the right to cut off contractual relations with another party if the other party violates the law; that might be useful to the first party for investor-relations purposes or possibly to maintain good relations with law enforcement.
5.6.1. Clause text
When this Clause is agreed to in writing:
5.6.1.1. Which party may terminate under this Clause?
Either party, referred to as "TP," may terminate the Contract, effective immediately upon notice of termination to the other party, "OP," if TP reasonably determines that OP has committed any act or omission that satisfies both of the following prerequisites:
OP's act or omission must violate one or more applicable laws; and
because of the violation, OP's act or omission is likely to materially and adversely affect TP's interests.
5.6.1.2. Is there a deadline for termination?
If not sooner exercised, T's right to terminate under this Clause will expire automatically if its notice of termination has not become effective under Clause 6.9 on or before:
the date ten business days after the date that TP first learned, via any source, or reasonably should have known, of the most-recent event coming within one or more of the categories listed in section [BROKEN LINK: termin-legal-trig] above; or
if earlier, the date 30 days months after the date of that most-recent event, regardless when, or whether, TP learned or should have known about that event. 5.5.1.2
5.6.1.3. Option: Cure Period for Legal Violation
If the Contract clearly adopts this Option, then T's termination for legal violation by OP will have no effect if OP cures both the violation of law and all effects of the violation before the end of five business days after the violation began — otherwise, TP may terminate without giving OP an opportunity to cure.
Comment
Option: Cure period for legal violation: This is an option because it's hard to predict in advance whether a cure period would be appropriate for a violation of law, and so it seems unwise to make it part of the standard term.
5.7.1.1. Which party may terminate under this Clause?
Either party, referred to as "TP," may terminate the Contract by following the procedure in this Clause if the other party, "BP" materially breaches its obligations under the Contract.
Comment
TP: No snickering, please. Caution: This Clause 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. Example: In a California case, a contract's termination-for-breach provision referred to the right of the non-breaching party to terminate. That, said a federal district court, meant 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 provision in the contract. 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).
Comment
Terminate just particular transactions? Note that under section [BROKEN LINK: termin-trans] of Clause 5.2, the terminating party TP could terminate just a purchase order, statement of work, etc., instead of terminating the Contract as a whole.
5.7.1.2. Notice of breach is required
Before terminating for material breach, TP must give BP notice of the breach as provided at Clause 6.9; the notice of breach must state at least the following:
the circumstances of the breach, in reasonable detail (as TP then understands the circumstances); and
how long TP asserts that the cure period will be (if any), as set forth at section [BROKEN LINK: termin-breach-cure-period] below.
Comment
Notice of breach to start the clock ticking: Sometimes a breaching party B won't dispute its breach, but it still makes sense to require notice, to fix the start of the putative cure period, if any (see the next section).
5.7.1.3. How long does the breaching party have to cure the breach?
The terminating party TP may not terminate if the breaching party BP has cured the breach, and advised TP of the same in writing (e.g., via email or text), no later than the following times have elapsed after the effective date of TP's notice of breach to BP:
Nonpayment of an amount due under the Contract: Five business days.
Missed deadline for which the Contract unambiguously states, in effect, that time is of the essence: No cure period.
Other, curable missed deadline stated in the Contract: Five business days.
Other, curable breach:Ten business days.
Breach that clearly is not capable of being cured:No cure period; immediate termination by notice is allowed.
Other? The Contract may specify other cure periods for breach, including but not limited to the types of breach listed in this section [BROKEN LINK: termin-breach-cure-period].
Comment
Cure periods: 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."
5.7.1.4. A separate notice of termination is normally required
To terminate for material breach, the terminating party TP must give the breaching party BP notice of termination; that notice must describe, with reasonable specificity:
the basis for termination, and
the putative effective date of termination.
Comment
Notice of termination — 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 a First Circuit decision, discussed in the comment to section [BROKEN LINK: audit-surv] (survival clause) of Clause 2.3 (audit protocol).
5.7.1.5. What if the breach is not curable?
If the breach is clearly incapable of cure, then the notice of breach and the notice of termination may be the same notice.
5.7.1.6. Is there a deadline for termination for breach?
If not sooner exercised, T's right to terminate under this Clause will expire automatically if TP's notice of termination to BP has not become effective within six months after the end of the cure period (if any).
Comment
Termination deadline: 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 the stated deadline, then the breach likely didn't harm the terminating party that much.
5.7.1.7. Is termination an exclusive remedy for the breach?
Unless the Contract expressly states otherwise: Termination, in and of itself, will not preclude the terminating party TP from seeking other remedies against the breaching party BP for the breach(es) that led to termination (to the extent consistent with the Contract and the law).
Comment
Termination not exclusive remedy: 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 Contract (see Clause 3.12) and/or by the law.
5.7.2. Comment? Is this Clause actually needed?
At common law, if a party "BP" breaches a contract in a way that deprives the other party "T" of its reasonably-anticipated benefit from the contract, then TP 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 the breach is not material, then the other party must continue performing but may sue for damages for the breach. See id.
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 BP does not cure a material breach in a stated amount of time, then TP may terminate the contract.
5.8. Termination for Personnel Changes
A customer might want to use this Clause 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.
Either party, referred to as "TP," may terminate the Contract following any material change among the supervisory personnel of the other party, "OP," who are directly and materially involved in OP's performance under the Contract.
5.8.1.2. Is there a deadline for termination?
If not sooner exercised, TP's right to terminate under this Clause will expire automatically if TP's notice of termination to OP has not become effective in accordance with Clause 6.9 on or before:
ten business days after the date that TP first learns, via any source, or reasonably should have known, of the most-recent change of OP's personnel in question; or
30 days after the most-recent personnel change in question.
5.9. Termination for Reputation Risk
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.
Either party, referred to as "TP," may terminate the Contract — effective immediately upon TP's notice of termination to the other party, "OP," if TP reasonably determines that one or more "Reputation Risk Actions," defined at section [BROKEN LINK: termin-rep-risk-defn] below, previously taken by OP or any of OP's affiliates, have created a not-insubstantial risk to the business reputation of TP and/or of any of TP's own affiliates.
Comment
Examples of reputation-based terminations: Here are some examples from the news — students, you can just skim these:
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: 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: 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).
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.
5.9.1.2. Definition: What would qualify as a "Reputation Risk Action"?
For purposes of this Clause, 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:
libel or slander another person;
put another person in a false light;
threaten, embarrass, harass, or invade the privacy of another;
impersonate another or promote, encourage, or assist in, such impersonation;
offend a reasonable person on racial- or ethnic grounds;
engage in conduct prohibited by law, including for example the U.S. Foreign Corrupt Practices Act;
encourage activities prohibited by law, including (for example) bribery; identity theft; child pornography; and terrorism;
engage in tortious conduct; and/or
mistreat a person, or promote, assist in, or encourage such mistreatment.
Comment
Reputation Risk Actions: 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).
5.9.1.3. Does this Clause require any action by any party?
This Clause establishes only the terminating party TP's conditional right to terminate the Contract; in itself it does not obligate either party to do, or not do, anything.
5.9.1.4. Would the other party OP be liable in damages?
No party will be liable under the Contract, in damages or otherwise, for any Reputation Risk Action that does not otherwise breach the Contract — but this does not rule out possible liability on other grounds (for example, for tortious behavior and/or criminal action). 8.14.8
5.9.1.5. Is there a deadline for termination under this Clause?
If not sooner exercised, a party TP's right to terminate under this Clause will expire automatically if TP's notice of termination to the other party OP has not become effective under Clause 6.9 at 12 midnight at the end of the day on:
the date ten business days after the date that TP first learns, via any source, or reasonably should have known, of the most-recent Reputation Risk Action; or
the date three months after the date of that most-recent action.
5.10. Termination Prohibition
Terms such as this Clause 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).
5.10.1. Clause text
5.11. Termination Wrap Up
Every human relationship comes to an end eventually, and so prudence suggests planning for an orderly "shut-down" of the relationship. To that end, this Clause 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 Clause are based on various agreements that your author has negotiated over the years.
A "Relationship," defined at section [BROKEN LINK: wrap-rel-defn], between a requesting party, referred to as "R," and another party, "OP," comes to an end, whether by expiration or termination; and
OP clearly agrees in writing — for example, by agreeing to this Clause in the Contract — that R may have a transition period (over and above any notice period that preceded the Relationship's ending) in which to wrap up R's in-progress transactions in the Relationship.
5.11.1.2. Definition: What counts as a Relationship?
For purposes of this Clause, the term "Relationship" refers to one or more of the following:
a relationship, such as for example a reseller- or referral relationship, that is clearly indicated in the Contract as being subject to this Clause; and/or
an authorization, for example, a grant of one or more rights such as a license, likewise clearly indicated; and/or
the Contract itself, if the Contract does not expressly specify such a relationship or authorization.
5.11.1.3. Definition: How long would the Wrap-Up Period last?
The "Wrap-Up Period":
begins on the date that the Relationship formally comes to an end; and
ends at the end of the day on the date ten business days thereafter, if not otherwise agreed in writing.
5.11.1.4. What kind of wrap-up activities are allowed?
During the Wrap-Up Period, except as otherwise stated in this Clause, the requesting party R may attempt to complete any then-pending transactions that:
were allowable under the Contract before the end of the Relationship; but
after that time, are prohibited, by the Contract and/or by law.
5.11.1.5. What terms and conditions would govern the Wrap-Up Activities?
The wrap-up activities under this Clause will be governed by the same terms of the Contract as would have applied before the end of the Relationship.
5.11.1.6. What if a party is in material breach?
The requesting party R will not have a Wrap-Up Period, and may not engage in wrap-up activities, if R is in material breach of the Contract when the Relationship ends.
5.11.1.7. The requesting party is to furnish a List of wrap-up transactions upon request
If so requested by the other party OP, then not later than two business days after the date that the Relationship ends, the requesting party R is to furnish OP with a complete written list of pending transactions that R hopes to complete during the Wrap-Up Period, to help OP confirm that R is not using the Wrap-Up Period to develop new business.
5.11.1.8. The requesting party must confirm wrap-up eligibility upon request
If the other party OP so requests concerning a particular wrap-up transaction, then the requesting party R is to furnish evidence, reasonablysatisfactory to OP, that R had in fact been actively engaged in negotiating that transaction before the end of the Relationship.
When this Clause is agreed to, an amendment to the Contract will be effective only:
as stated in this Clause; or
to the extent — if any — that the Contract expressly states otherwise.
Comment
A. Disputes about oral contract modifications can arise because, for example: • human memory is fallible — sometimes very much so; • people tend to remember things the way they want to remember them; • people can sometimes shade the truth — or even flat-out lie — if they think it will help them.
B. All these things are especially true as time passes after an event — often it's because the parties' circumstances have changed and what they want now is not the same as what (they thought) they wanted then. (These widespread human failings are discussed in more detail at 7.18.)
C. For that reason, contracts typically include provisions like this Clause, requiring amendments to be in writing; this is to try to forestall after-the-fact disputes about whether the parties orally agreed to modify the contract. But: Will a court enforce such a written-amendments requirement? See the additional reading beginning at 6.1.7.8.
D. Pro tip: For an extensive amendment, consider drafting a replacement version of the Contract, with a title such as, "Amended and Restated [title of the Contract]," as discussed at 6.1.7.3.
6.1.2. A written amendment is required
For an amendment to the Contract to be binding, the amendment must be clearly stated in a written document (the "amendment document").
Comment
In some jurisdictions, a party could claim and prove that such an amendments-in-writing provision was waived and that a non-written amendment was to be given effect; see the discussion at 6.1.7.8.
6.1.3. The amendment title must be immediately informative.
The amendment document must have a title that clearly indicates that the Contract is being amended.
Comment
A clear amendment title will "Serve the Reader!" 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 could lead to costly litigation. See, e.g., Expo Properties, LLC v. Experient, Inc., 956 F.3d 217, 224 (4th Cir. 2020) (affirming summary judgment in favor of office-complex tenant, on grounds that estoppel certificate, signed by tenant, had not modified the tenant's lease).
Providing a clear amendment title follows the One Great Rule of Contract Drafting, namely Serve the Reader! (30.1.1). Drafters shouldn't assume that parties would notice a contract amendment contained in some other type of document that they're being asked to sign.
Pro tip: In the amendment's title, consider including a series number and date — and perhaps even include a (brief) mention of the amendment's purpose — to 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
[ x ] Amendment No. 1, Dated December 25, 202x, to Asset Purchase Agreement (Increase of Purchase Price)
If making further amendments to Amendment No. 1 itself, consider:
Amendment No. 2 No. 1.1, Dated December 31, 202x, to Asset Purchase Agreement
6.1.4. The amendment must be signed by each party sought to be bound.
The amendment document must be signed on behalf of each party that is to be bound by the amendment.
Comment
A. Caution — maybe don't require all parties to sign an amendment? 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).
B. Sure: It's usually better if all parties sign the amendment document. But the law in the U.S. ordinarily requires the signature of just the party that's supposedly bound by the amendment. Example: In a 2012 case, the Seventh Circuit said,"The critical signature is that of the party against whom the contract is being enforced, and that signature was present. Hess v. Kanoski & Assoc., 668 F.3d 446, 452-53 (7th Cir. 2012) (emphasis added).
C. 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 …."
D. If parties did want to require both signatures on an amendment, that could be stated in the contract using override language such as: "Any agreed amendment to this Agreement must be signed by all parties to this Agreement."
E. For tips on drafting amendment signature blocks, see 6.11 and especially 24.4 — the format would likely be exactly the same as for the contract itself.
6.1.5. Anyone with apparent authority can sign an amendment.
The signature of each party signing an amendment must be by an individual who has at least apparent authority to do so unless the Contract clearly limits who has such signature authority.
Comment
A. Which individual(s) should have to sign amendments? Typically under the law in the U.S., anyone with apparent authority may sign an amendment on behalf of a party — but a contract could limit who has apparent authority.
B. Caution: Any limitation on who can sign amendments should usually phrased in terms of a position title and not the name of a specific individual. That's because, at some unknown point in the future, the specific individual in question might no longer be available to sign amendments, because reasons. (The title of the position would of course have to be customized for each contract, or each contract form.)
Here's a hypothetical example from our MathWhiz-Gigunda simulation (see [BROKEN LINK: hypo-facts]); as a drafter, you'd of course change the names appropriately:
MathWhiz WILL NOT BE BOUND — and Gigunda is not to assert otherwise — by any alleged amendment to or waiver of this Agreement unless the amendment or waiver is in writing and signed by [ ] Mary Marvel [ x ] MathWhiz's chief executive officer.
See also the discussion at 30.15 of the danger of "raising the bar" — and jeopardizing enforceability — by requiring more signatures than necessary and then not getting all of the "required" signatures.
6.1.6. Claims of oral waiver of this Clause require heightened proof.
If a party asserts that the parties waived the writing requirements of this Clause, then the asserting party must support its assertion by heightened proof that the alleged waiver in fact occurred, as provided in Delaware law.
Comment
This issue comes up sometimes, as discussed at 6.1.7.8.
6.1.7.1. How formal must an amendment document be?
Technically, a binding written document amending the Contract could be an exchange of emails — or even an exchange of text messages.
Example: This happened in a Florida lawsuit between a digital ad agency and one of its clients, an e-cigarette manufacturer, resulting in the manufacturer having to pay the agency more than $1 million dollars 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 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).
Caution: A text-message amendment might not be a good idea because:
it might be overlooked by the relevant business people;
it might disappear; and
even if it didn't disappear, it might be legally ineffective in some jurisdictions, as discussed at 25.2.
For the same reason, an amendment on something like a Post-It note would be inadvisable, even though technically it'd be binding if it was otherwise sufficient.
6.1.7.2. Is an amendment needed? Or just a waiver?
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 …."
Imagine a contract between two parties whom we'll call "Fred" and "Ginger." Suppose that the contract calls for Ginger to take care of Fred's lawn; Ginger's obligations include mowing the lawn each week, raking leaves in the autumn, etc.
Now suppose that on one particular day, Fred comes outside to talk to Ginger when she arrives to mow the lawn.
If Fred says, "Hi Ginger — I don't need the lawn mowed this week." That's known as a waiver, by Fred, of Ginger's obligation for that occasion.
Or, Fred might say, "never mind, Ginger, 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 Ginger agrees, that's known as an amendment of the contract.
6.1.7.3. Pro tip: Consider an "amended and restated agreement"
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.
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: This happened in a Sixth Circuit case where an earlier contract contained a payment guaranty, but an amended-and-restated contract did not; 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).
6.1.7.4. Be sure to save the signed amendment document!
Save any signed amendment document in a place where it can be readily found later. (This should be a routine thing for businesses already.)
Here's why: Imagine, in a contract legal dispute, that you made a particular argument, based on the contract text. But then the other side informs you that you'd previously signed an amendment to the contract that fatally undermines your argument. Both you and your client had forgotten about the amendment — but sure enough, the other side had a signed copy ….
6.1.7.5. 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: This is an issue (at this writing) in a pending federal-government contracting case, where fact issues precluded summary judgment whether a contract modification effected a release of certain other claims the contractor was asserting against the government. See Fortis Indus., LLC v. GSA, CBCA 7967, slip op. at 4-5 (Sept. 18, 2024).
6.1.7.6. Caution: Could there be 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 (that is, Don't Repeat Yourself, usually) to try to reduce such "dependencies" — and thus the possibility for inconsistent revisions during negotiations — between different provisions in a contract.
6.1.7.7. Is there sufficient "consideration"?
Applicable law might require "consideration" (see 11.10) for amendments to existing contracts. Generally speaking, this means that each side gets at least some benefit from the amendment.
6.1.7.8. Can a written-amendment clause be orally waived?
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. For example, Massachusetts law allows such claims, as noted in a federal court opinion allowing a contractor's lawsuit over a purported equity grant to move forward:
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, extra paragraphing added).
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 28.5.2):
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].
Delaware law likewise allows a party to assert that a written-amendment requirement was orally waived — although that party must meet a heightened evidentiary burden; see the discussion at 6.1.7.10
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. 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, citingCalifornia Civil Code § 1698(d).
6.1.7.9. But: A written-amendment clause might well be enforced.
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. 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: In a 2018 case, the UK's Supreme Court cited but expressly rejected the Cardozo Rule, concluding 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.
6.1.7.10. Why Delaware law for claims of oral amendment?
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. Delaware law (grudgingly) allows this. But it also says that if a party wants to assert that a written-amendment requirement was orally waived, then that party must meet a heightened evidentiary burden, because the state's law disfavors such claims. 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).
Massachusetts law works in a somewhat-similar fashion to that of Delaware when it comes to amendment-in-writing requirements. See Hoffman v. Thras.io Inc., 538 F. Supp.3d 196, 206 (D. Mass. 2021) (denying relevant part of motion to dismiss, citing cases).
It might seem strange to adopt a law for one specific provision. But it's not unprecedented, as discussed at 3.7.19.
6.1.7.11. 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.
6.2.1. The specified party may unilaterally amend the Contract by giving notice.
When this Clause is agreed to, a party clearly specified in the Contract may unilaterally amend the Contract, but only as stated in this Clause.
Comment
A. 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, those amendment provisions will be enforced — if they're done correctly.
B. It'd be unusual for a contract to allow either party to amend unilaterally — though when you think about it, that might make for smoother evolution of a contractual relationship than letting either party terminate at will.
C. Caution: In some jurisdictions, a unilateral-amendment provision might be unenforceable by law.
6.2.2. Reasonable advance notice of a unilateral amendment is required.
The amending party must give the other party reasonable advance notice 6.9 that an amendment to the Contract is being proposed.
Comment
How much advance notice to require for a unilateral amendment might be a subject for negotiation — and might be subject to legal restrictions, e.g., if consumers or employees are involved; see 6.2.6.3 for more discussion.
Caution: Just changing Website terms probably won't be enough notice; see 6.2.6.1.
6.2.3. A notice of unilateral amendment must be clear, prominent, and at the beginning.
The amendment notice's statement that an amendment is being implemented must be clear, prominent, and at the beginning of the notice, so that a reasonable reader would quickly grasp what the notice is about.
Comment
A notice of unilateral amendment should be explicit that the Contract is being amended, lest a court hold otherwise. Example: In a South Carolina employment dispute, a company sent an email to its employees asking them to click on an online "acknowledge" button; the accompanying text said that the employee was acknowledging a company mandate that employees read a new policy requiring binding arbitration of disputes. One employee clicked on the "acknowledge" button, then five years later was fired and sued the company, which moved to compel arbitration. The state supreme court held that what the employee had acknowledged — i.e., a directive to read the new policy — had not modified the employee's pre-existing employment contract and so arbitration was not required. See Lampo v. Amedisys Holding, LLC, Op. No. 28265, slip op. (S.C. Mar. 5, 2025) (reversing and remanding court of appeals decision).
6.2.4. The amendment notice must state two specific things
The amendment notice must state — clearly and prominently — the following:
at least one specific action that the other party may take to opt out of the amendment; and
the deadline for the other party to take such opt-out action.
Comment
Subdivision 1: Typical opt-out actions for unilateral amendment include, for example, terminating one's user account or perhaps terminating the Contract itself.
6.2.5. Disagreements about unilateral-amendment notices are to be escalated.
If the parties disagree about the sufficiency of the amendment notice, then the parties will escalate the dispute:
6.2.6.1. Just changing Website terms probably won't suffice
For agreements posted to a Website (such as "terms of service"), more than one court opinion has held that changing the agreement at the Website isn't enough for a unilateral amendment.
Comment
See 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); Rodman v. Safeway Inc., No. 11-cv-03003-JST part III-C (N.D. Cal. Dec. 10, 2014) (granting motion for summary judgment that Safeway had overcharged on-line customers).
6.2.6.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: In a Seventh Circuit case, the court vacated an order confirming an arbitration award against a PayPal customer who had 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:
… PayPal does not have a more specific record of sending that email notice [of PayPal's unilateral amendment] to Kass or whether it was received, bounced back, or disappeared into cyberspace.
Kass denied that she had ever received or known of the 2012 amendment to the User Agreement. By sworn declaration, Kass testified that she had never seen the amended User Agreement posted to PayPal’s website, that she did not receive an email notifying her of the amendment, and that she had never seen, known of, or agreed to the 2012 User Agreement with its mandatory arbitration clause. * * *
Whether she [Kass] was subject to mandatory arbitration under the 2012 User Agreement depends on whether Kass received an email from PayPal notifying her of that amendment. This is a question of fact that must be resolved by a trier of fact, not summarily by the court considering only the paper record.
What odds would you give that a local jury would side with PayPal on that point?
Example: In another case, 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 it gave notice of the amendment, where the user denied having opened or read the notice email that Dropbox sent. 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.
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.
Example: In a Georgia case, an Uber driver murdered one of his passengers. (You think that might have influenced the court's decision?) 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." 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).
6.2.6.3.Consumer contracts might have special requirements
For a perhaps-dated review of case law addressing what might be required to qualify as sufficient notice to consumers of unilateral amendment, see generally two 2016 ABA articles (probably paywalled, limited to ABA members). See 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).
6.2.6.4. 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 Blockbuster customer (remember them?) sued the company for allegedly violating her privacy rights and sought class-action status.
Blockbuster moved to compel individual, case-by-case arbitration, as required in the Blockbuster on-line terms of service.
Harris 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.
A federal court in Texas 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 — and therefore was unenforceable under the relevant state law. 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 at6.2.6.7; see generally Illusory promise (Wikipedia.org). Cf. Heckman v. Live Nation Entertainment, Inc., 120 F.4th 670, 682-83 (9th Cir. 2024) (affirming holding that arbitration agreement and its delegation agreement were unconscionable; Ticketmaster's terms of service permitted retroactive modification).
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.
Example: A former employee of 24 Hour Fitness filed a lawsuit against the gym company.
The company moved to compel arbitration, citing an arbitration provision in the company's employee handbook.
The court affirmed a holding that 24 Hour Fitness's arbitration provision was unenforceable because the company reserved the right to change the employee handbook at will.
That, in turn, meant that the handbook was "illusory" — and consequently, the arbitration provision was ineffective and the former employee's case would be tried in court instead of being heard privately by an arbitrator. Carey v. 24 Hour Fitness USA, Inc., 669 F.3d 202 (5th Cir. 2012).
Pro tip: Parties presumably would always be free to agree to amend the Contract 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: In a Fifth Circuit case, the 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. 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: In a North Carolina case, a majority of the state's 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." See Canteen v. Charlotte Metro Credit Union, 900 S.E.2d 890, 896 (N.C. 2024).
(Two dissenting judges in that case objected that, by unilaterally adding the arbitration provision, the credit union "single-handedly deprived [the credit union's 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.") Id. at 898 (Riggs, J., dissenting).
6.2.6.5. Would non-U.S. law restrict unilateral amendments?
Drafters should check their specific jurisdictions for whether unilateral amendments could be unenforceable. Here are two examples:
• UK: In the UK, the Digital Markets Competition and Consumer Act "sets out new rules for traders offering subscription contracts. These rules aim to protect consumers from unwanted subscriptions and ensure they have clear rights and easy methods to exit contracts." Caroline Hobson, Leo Spicer-Phelps, and Claire Temple, Government Reveals New Proposals for Incoming Subscription Contracts Regime Under DMCC Act (JDSupra.com 2024).
As a research aid, here are some other cases concerning unilateral amendments:
Example: A credit union sent one of its members an arbitration addendum to the member's account agreement. Indiana's supreme court held that, under the circumstances, the credit union's notice of the addendum was insufficiently noticeable (so to speak), and so the member's silence was not enough to indicate her assent to the arbitration addendum. See Land v. IU Credit Union, 218 N.E.3d 1282 (Ind. 2023) (reversing and remanding trial court's order compelling arbitration). Hat tip: Holland & Knight, Mandatory Arbitration and Class Action Waivers by Amendment: Easier Said Than Done (JDSupra.com 2023).
Example: In Halliburton, 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 did not 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 6.2.6.4, because that provision states that unilateral amendments are effective immediately upon notice.
6.3. Entire Agreement Clause
A modern contract negotiation will typically involve a lot of written messages going back and forth — different drafts of the contract; emails; text messages; etc., often with inconsistent terms as the negotiation progresses. For that reason, contracts often include an entire-agreement statement to emphasize that only the final, signed agreement will "count."
The Contract — with any subsequent amendments in accordance with the Contract — is the parties' complete, final, and exclusive agreement concerning the subjects addresed in it.
Comment
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).
6.3.2. *Will the parties' prior statements still count?
All prior communications among the parties, in any form, about the subject of the Contract are deemed "merged into" (and thus superseded by) the Contract.
Comment
Caution 1: Even with a "merger clause" like this, courts might still use previous discussions to shed light on the parties' intended meaning of terms in a contract; see the discussion at 17.6.
Caution 2: A merger clause usually won't block a claim for fraudulent inducement to enter into the contract; for that, a drafter would have to include either an express reliance waiver (8.57) or — in some jurisdictions only — a simple statement that there are no external representations (6.3.7.1).
6.3.3. What about prior oral agreements (if any)?
Same answer.
Comment
One not-uncommon use case for this Clause might be if parties enter into a written confidentiality agreement, or "NDA," to replace a previous, informal, oral agreement to keep information confidential.
6.3.4. What about exhibits, schedules, etc.?
Any exhibits, schedules, etc., that are attached to or clearly-incorporated into the Contract are deemed part of the Contract itself.
6.3.5. What status will purchase orders, etc., have?
For transactions under the Contract, any additional- or different terms in a purchase order, order confirmation, invoice, and the like are rejected by all other parties and are not part of the Contract.
Comment
A. The "any additional or different terms … are rejected" language above is to prevent the conflicting fine print in the parties' various form documents from becoming part of the Contract — and perhaps overriding the parties' negotiated agreement.
B. Students: Be sure to read about the so-called "Battle of the Forms" (10.5) in which a customer and a supplier "throw paper" at each other with lots of mutually-repugnant fine print.
6.3.6. Would an online agreement override the Contract?
Deal-related terms in click-wraps, browse-wraps, etc., are rejected, and not part of the Contract, unless the Contract clearly states otherwise.
Subdivision a does not rule out having an online agreement impose terms and conditions — not inconsistent with the Contract — concerning the use of an online platform, software, or the like.
Comment
A. One party should not be able to "retrade the deal" by claiming that an online agreement superseded a "signed" agreement; see the discussion at 11.5.
B. The term "Deal-related terms" is vague, of course, but it's flexible and succinct.
6.3.7.1. Should "no external representations" be said, too?
Background: Even with an entire-agreement provision such as that of this Clause, 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 such as this Clause (a.k.a. merger clauses or zipper clauses) often include "there are no other representations" language such as that aboe.
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. This law was explained by the Southern District of New York in Century Pacific (2007). 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).
6.3.7.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.
Delaware law likewise requires anti-reliance language in order to preclude a fraud claim. As the Chancery Court explained in Trifecta Multimedia (2024): "[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).
Pro tip: If you're drafting a contract where the law will be that of a jurisdiction such as Texas, 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 ….
Editorial comment: In the context of a fraudulent-inducement analysis, don't these two disclaimers — a disclaimer of external representations, and a disclaimer of reliance on external representations — logically amount to exactly the same thing? The quotation above suggests that in the Texas supreme court's view, a disclaimer of extrinsic representations, standing alone, was insufficiently explicit and "in your face" to alert the other side about what it was being asked to give up.
– Another counterexample: In Fricano (2015), the Bank of America 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.
6.3.7.3. Or: 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 SodexoMAGIC (2022), 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).
6.3.7.4. Lying about future intent: "Misrepresentation"?
In Harrell (2024), the Fourth Circuit 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 Albertsons (2021), 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.
And as the Texas supreme court said in T.O. Stanley Boot Co. (1992):
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).
the parties will escalate disagreements to a neutral advisor, as stated in this Clause, whenever any party reasonably asks — after internal escalation in accordance with Clause 6.5.
Comment
This reasonableness requirement for an escalation request should help provide a roadblock against a wealthier party's attempts to bully another party by inappropriate demands for escalation (e.g., repetitive demands, or demands concerning trivial disagreements).
6.4.2. Who will serve as the neutral advisor?
Either party may ask the American Arbitration Association to appoint a neutral advisor if the parties do not agree on one within a reasonable time.
Comment
A. 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 [BROKEN LINK: arb-admin] for other arbitration administrators that might help with appointing a neutral.
B. For escalation to a neutral, the parties could consider agreeing in advance to a list of acceptable neutrals. In some cases, the parties might want to agree to engage a specific neutral at the time they enter into the Contract; this could be along the general lines of an expert engineering dispute resolution board as sometimes used in complex construction projects. (Shameless plug: For appropriate cases, your author would be pleased to be considered as a neutral advisor for escalation under this Clause.)
6.4.3. Consider exchanging documents
The parties are strongly encouraged to exchange relevant documents as provided in Clause 6.5 (internal escalation).
Comment
See the comments about internal escalation at Clause 6.5.
6.4.4. First step: The parties exchange initial proposals
On a schedule set by the neutral (if not otherwise agreed), the parties are strongly encouraged to exchange one or more written, first-round proposals to resolve the dispute.
Any proposal provided by a party in this first round would be merely a suggestion for further discussion — not a firm offer to settle on the proposed terms — unless the proposal itself clearly states otherwise.
The contents of each party's proposal are up to that party.
A party proposal could include, for example, terms for allocating (i) fees and expenses charged by the neutral; and/or (ii) the parties' respective attorney fees.
As part of this first round, each party is free to provide multiple proposals.
A party may submit an "exploding" proposal that is withdrawn at a stated time if not agreed to as part of the first round.
Comment
Alternative proposals appear to have been used in a 2008 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).
6.4.5. Next: The parties exchange final-offer proposals
On a schedule set by the neutral (if not otherwise agreed), each party is to provide the other party with one or more written, final-offer proposals. This is to be done in the same general manner as the first-round proposal(s).
Each party is to provide the neutral with a copy of the party's final-round proposal(s).
If a party does not provide a final-offer proposal, the only consequence will be to limit the neutral's choices as provided below.
Comment
A. 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.
B. Copying the neutral on the parties' second proposals will help the neutral to get a sense of which party is being reasonable in its proposals; this will be of use later.
C. 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; your author's current thinking is that this 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.
6.4.6. Next: A short, video "mini-trial"
The neutral is to schedule, convene, and preside at a video conference between the parties to address the dispute.
The neutral may use his- or her reasonable discretion concerning scheduling, "hearing management," and other administrative matters.
One such administrative matter is whether to allow a party to record the video conference.
Comment
A. Subdivision a: See 6.4.22.6 for a detailed discussion of the administrative "mechanics" of the video conference.
B. Subdivision b: Most neutrals would ordinarily defer to the parties' agreement on administrative matters — within reason.
6.4.7. Bring senior management?
Each party is encouraged to have a senior-management representative participate in the video conference with the neutral, to provide a possibly-broader perspective on the dispute.
Comment
See the discussion of senior-management participation at 6.4.22.7.
6.4.8. Parties may do mini-trial presentations
At the video conference, the neutral is to 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.
The neutral is free to rein in presentations that seem repetitive or unproductive after reasonable warning.
The neutral is free to express view(s) about any party's proposal; the neutral may do so to both parties together, and/or (borrowing from mediation practice:) to either party separately — perhaps including suggestions for bridging any remaining gap(s) between the parties.
B. Subdivision b: Some might be concerned that a neutral's comments could create an impression of bias on the part of the neutral. But all judges, arbitrators, and other neutrals are human, so they inevitably tend to form provisional views — they're simply expected to withhold judgment until all the evidence is in.
Unless otherwise agreed, the neutral is free — before, during, and after the video conference — to discuss the dispute privately (this is known as "ex parte" communication) with each party, without the presence of the other party or its counsel, subject generally to the ethical guidelines applicable in mediations.
Comment
In mediation, "shuttle diplomacy" is an established feature.
6.4.10. Next: The neutral chooses one proposal
The neutral is to do the following, promptly after the parties have concluded their presentations — and in any case before adjourning the video conference:
choose one of the "live" (proposed and not expired or withdrawn) party proposal(s); see subdivision b below;
announce the choice to the parties; and
briefly explain the reason(s) for the choice; and
in the neutral's sole discretion: give the parties the neutral's own recommendation as to what the neutral regards as potentially being the most-sensible resolution to the dispute.
The neutral's choice is to be of the party proposal that the neutral regards as "closest to the pin" (in golf terms) of an optimal resolution of the disagreement.
The party that submitted the neutral's chosen proposal is referred to here as the "winning party," the other party as the "losing party."
Comment
A. This is worded so that the neutral can make a choice even if one party didn't submit any proposals and/or didn't participate in the video conference.
B. Of course, if only one party submitted only one proposal, then the neutral's freedom of action would be limited — but not entirely gone, as discussed below.
6.4.11. What if no party submits a proposal?
If no party submits any proposal at all, then that constitutes the parties' agreement not to escalate that particular disagreement under this Clause (and the neutral should submit a final invoice).
6.4.12. Next: The neutral sends a confirming email
As soon as possible after adjourning the video conference, the neutral is send the parties a short email confirming:
which proposal the neutral chose — but omitting any details of that proposal; and
whether the losing party accepted the chosen proposal during the video conference (or the parties otherwise agreed to a resolution).
The neutral's confirming email is prima facie evidence of whether the losing party agreed to the neutral's choice of proposal — and it may be rebutted only by clear and convincing evidence, timely offered, including but not limited to reasonable corroboration of any statement by an interested party.
Comment
A. Subdivision a should help roadblock any "buyer's remorse" action on the part of a losing party that accepted the chosen proposal but then had second thoughts.
B. Pro tip: A party that disagrees with the neutral's confirming email would be well-advised to "speak up" immediately.
6.4.13. Next: The neutral sends a written report (if no settlement)
This section will apply if:
the losing party did not accept the neutral's choice of proposal; and
the neutral has not heard from both parties that they have settled the dispute by the date on or before five business days after the adjournment of the video conference.
In that case, the neutral is to expeditiously provide the parties with a brief written report that summarizes:
the neutral's reason(s) for choosing the chosen proposals; and
if applicable, the neutral's own recommendation.
6.4.14. No other neutral power (unless expressly agreed)
No other neutral power: For emphasis: The neutral has no other power to decide the parties' dispute unless the parties clearly agree otherwise in writing. 8.2.14.
Comment
6.4.15. The neutral's written report may be used in litigation
This section is intended to provide each party with additional motivation to be reasonable about settlement positions if the neutral provides a written report under section 6.4.13 above.
In any subsequent litigation (or, if agreed, arbitration) concerning the dispute, neither party will oppose the admission into evidence of the neutral's written report — but only in its entirety — if the other party so requests, with the status of a report of a court-appointed expert under Rule 706 of the Federal Rules of Evidence.
Comment
Unlike baseball-style arbitration, in an escalation under this Clause the neutral's choice isn't binding. Each party, though, has an incentive to go along with the neutral's choice of proposal: Otherwise, a judge or jury or arbitrator would hear what the neutral had to say — and that can have a compelling influence. See generally J. Gregory Sidak, Court-Appointed Neutral Economic Experts, 9 J. Competition L. & Econ. 359 (2013).
6.4.16. The neutral is immune from claims about the escalation
For reasons similar to judicial immunity, neither party is to sue the neutral, nor otherwise take any action against the neutral, concerning any statements made, by anyone, in the escalation or its aftermath (including without limitation in the neutral's written report).
For emphasis: This immunity for the neutral will apply to any claim of any nature whatsoever — including but not limited to defamation — concerning both the escalation and any "aftermath" (litigation or, if agreed, arbitration).
6.4.17. Rule 408 applies
Each party's escalation-related communications with the other party, and those of the neutral with each party, are not admissible in evidence in other proceedings (e.g., litigation) 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.
6.4.18. Confidentiality
This section will apply if, in connection with the escalation, one party ("Alpha") provides another party ("Bravo") with access to Alpha's other party's non-public information that is designated in writing as confidential.
Bravo is to treat that information as Alpha's confidential information, as stated in more detail at Clause 8.18, unless Bravo clearly shows that Bravo independently acquired the information.
Comment
See generally the discussion of exclusions from confidential status, at 8.20.6.5.
6.4.19. the parties will evenly split the neutral's expenses
the parties will timely pay, in equal shares, all fees and expenses invoiced by the neutral, and/or by an appointing organization, in connection with the escalation or its aftermath.
If either party ("Alpha") does not timely pay its share of neutral-related expenses under subdivision a, then:
the other party ("Bravo") is to pay Alpha's share; and
Alpha must immediately repay Bravo, together with: (i) interest at the maximum rate allowed by law, plus (ii) reasonable attorney fees in connection with Bravo's seeking repayment.
Comment
A. Subdivision a: Expense-sharing would entail each party's paying its share of the the fees and expenses billed by the neutral, as well as any amount(s) charged by (e.g.), the AAA.
B. Subdivision a — "aftermath": The parties would share the neutral's fees and expenses if, in subsequent proceedings (litigation or, if agreed, arbitration) the neutral were to be asked (by anyone) or compelled to produce documents or to testify.
6.4.20. the parties will bear their own escalation expenses
Each party is responsible for its own escalation-related expenses, without reimbursement from the other party.
Comment
This is worded to account for the possibility that a party might be entitled to expense reimbursement under other arrangements, e.g., from an insurance policy.
6.4.21. Survival of this Clause
This Clause will survive any end of the Contract for already-arisen disputes.
Clause 6.4 is intended 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 the parties' positions harden and relationships suffer.
Clause 6.4 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.
Tangentially: On the subject of "the lesser of two evils," the Candorville comic strip of May 7, 2024, by Pulitzer Prize-winning cartoonist Darrin Bell, had one character ask another: "You'd be voting for the lesser of two evils. Why would you want to do that?" The response: "Because the lesser of two evils is better than the worse 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).
6.4.22.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 and 2024, the results are not set out in table form for convenient analysis but seem to have exhibited similar success rates.)
True: Baseball salary disputes involve a comparatively-narrow range of relevant factors. But read on:
6.4.22.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; For an earlier version of the Susman Agreements with extensive commentary (in which the protective-order agreement is no. 11), see Stephen D. Susman and Johnny W. Carter, Better Litigating Through Pre-trial Agreements, Litigation, vol. 38, no. 1 at 26 (Fall 2011); see also Daniel P Elms, Susman Agreements: Clarity for the Rules of Civil Procedure (AmericanBar.org 2023).
– 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 inUnited 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).
– 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).
A personal anecdote: Back when your author 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.
Another anecdote: In the same time frame, "Jane" [a pseudonym] was a lawyer friend who was a partner at one of the leading Silicon Valley law firms. Jane 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, "Goddamn it, Jane, that means I have to be reasonable!" Jane responded, "Exactly." And of course the dispute was settled — sooner than it might otherwise have been.
6.4.22.5. What sorts of dispute might qualify for escalation?
Prime candidates for scalation to a neutral advisor would be any actual controversy,† relating to the Contract, concerning any of the following:
numbers, for example, how much one party is to pay another; and/or
imprecise requirements under the Contract — for example, what would constitute reasonable efforts in a given situation. disagreement relating to the Contract.
† The mention of an "actual controversy" has in mind the requirements of the (U.S.) Declaratory Judgment Act (discussed at 12.1). That's because it might not be reasonable to demand (expensive) 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 Clause:
the amount(s) of one or more sums that, under the Contract, one party is to pay to another party — because disputes about numbers are the classic use case of the baseball-arbitration aspect of this Clause, as discussed at 6.4.22.3.
whether particular action (as yet untaken) would satisfy an imprecise requirement under the Contract such as, for example, a requirement to make "reasonable efforts" or "commercially-reasonable efforts" (see Clause 7.15) or "best efforts" (see Clause 7.7);
whether a party has "good reason" to take or not take a particular action, where the Contract allows the party to take or not take the action if good reason exists.
Of course, the parties could always agree to follow this Clause for other disagreements.
6.4.22.6. Mechanics of the escalation video conference
If the parties don't settle their dispute based on their first-round or final-offer proposals, then the neutral would convene, and presides at, a video conference at which the parties can make presentations about their proposals.
A. If scheduling proved to be a problem, the neutral would have the final say on that point, as long as the neutral's decision isn't unreasonable.
B. 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.
C. The neutral would decide whether to allow recording of the video conference. (The parties could agree otherwise if they wanted.)
D. The neutral would allocate presentation time roughly equally between the parties.
E. The neutral should manage the conference in roughly the same way that a federal judge might manage a closing argument.
F. Usually, the video conference shouldn't continue for more than roughly 90 minutes. (The neutral and the parties could of course agree otherwise.)
6.4.22.7. Why involve senior management in the video conference?
If the parties haven't settled their disagreement by the time they do a video conference with the neutral, then each party should consider involving one or more representatives of their respective senior managements in the video conference. This would work in generally the same way as for a "mini-trial."
Why involve senior management? Because 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).
Two Australian lawyers pointed out that "[b]ringing 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.
When senior management people participate, the proceeding should generally follow the mini-trial rules published by the International Institute for Conflict Prevention and Resolution ("CPR") or other agreed rules.
6.5. Escalation to Supervisors Clause
Mandatory internal escalation can help promote early settlement of disagreements. That's because "[s]uperiors 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.
6.5.1. Disagreements must be escalated upon request.
Whenever either party asks, disagreements between the parties will be escalated to supervisors in each party, as stated in this Clause.
Comment
Too-many demands for escalation seems unlikely to be a problem that requires addressing in the Contract, because The Boy Who Cried Wolf will lose credibility with the other party — and perhaps with his- or her own boss.
6.5.2. Escalation need go "up" only one level at most.
Disagreements are to be escalated one level "up" in each party's management (and higher if agreed).
But a party need not escalate a disagreement any higher than the party's CEO (or individual holding a comparable position).
Comment
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.
6.5.3. Recommended: Exchange written position statements.
Preferably, the parties will start the escalation by exchanging written position statements, with the goal of helping each party's management to get a first-hand, unfiltered view of the other party's position.
Comment
Even merely producing written position statements might help the parties' people figure out what their positions really are in the disagreement; that could speed up resolution.
6.5.4. Escalation might not resolve the disagreement.
If escalation under this Clause doesn't resolve the parties' disagreement, then the parties will discuss the possibility of escalating to a neutral advisor (see 6.4), but neither party is required to agree to such escalation.
6.5.5. Use in court of statements in escalation is restricted.
To encourage candid discussion, the parties will treat each other's communications in the escalation as provided in Rule 408 of the [U.S.] Federal Rules of Evidence, and the interpretations of that rule by U.S. federal courts. (This is true even if Rule 408 would not otherwise govern.)
Comment
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."
6.5.6. Consider early document exchange
The parties are strongly encouraged to exchange relevant documents as early as practicable.
If so agreed, the document exchange is to be done under a written confidentiality agreement ("NDA"), containing terms such as those of Clause 8.18.
To reduce opportunities for costly "satellite litigation," no such NDA will be binding on either party unless the NDA is: (i) in writing, and (ii) signed by the party that is purportedly bound by it.
Comment
A. If litigation were to ensue, each party would likely get access to many of the other party's relevant, non-privileged documents anyway. So it will often make sense to just get on with it — perhaps under a suitable confidentiality agreement — to save time and legal expense for all concerned.
B. Subdivision 2: Pro tip: For greater security, the parties could agree to set up some kind of virtual dataroom site with restricted access, e.g., a Google Docs or Dropbox folder, in lieu of sending documents as email attachments.
If this Clause is adopted in the Contract, then an otherwise-expiring "Evergreen Period" specified in the Contract will be automatically renewed as stated in this Clause.
Gap-filler: If the Contract does not specify an Evergreen Period, then the Evergreen Period is the term of the Contract.
Comment
A. 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 Clause in the Contract, drafters can provide such an opportunity, on either an opt-out or opt-in basis.
B. 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 Contract.
C. This Clause uses the term renew as a common business vernacular, but in some jurisdictions that term might come with strings attached (which this Clause tries to write around); see the discussion at 6.6.12.1.
6.6.2. Notice is required to opt out of (automatic) renewal.
By default, the renewal of the Evergreen Period will be "opt-out" — that is, the renewal will go into effect automatically unless an eligible party opts out — unless the Contract clearly specifies that the renewal is to be "opt-in," in which case an eligible party must opt in for the renewal to take effect.
The term "Evergreen Option" refers to the right to opt-out or opt-in as stated in this Clause.
Comment
There's a critical potential difference between an option to renew and — as here — an option to terminate what would otherwise be an automatic renewal. The well-known food company J.M. Smucker learned that lesson in a North Dakota case, where it got stuck paying nearly $280,000 in rent and utilities for a lease that it didn't want after it was late in exercising its option to terminate an automatic renewal. Lesson: Use some kind of calendar reminder system!
In its J.M. Smucker opinion, the Eighth Circuit explained:
The lease in this case contained an option to terminate, not simply a lease cancellation provision. While the original lease provided an option to renew the lease for up to three years, the amendment to the lease made renewal automatic and termination optional. …
As an option to terminate the lease, the cancellation provision must be strictly construed and requires exact compliance. Also, as a matter of law, time is of the essence to the option.
Given the significant differences between a standard lease cancellation provision and an option to terminate, we find the district court erred in failing to treat the cancellation provision in this case as an option to terminate.
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) (cleaned up, emphasis and extra paragraphing added).
6.6.3.Any party may exercise the Evergreen Option by giving notice.
The stated party (or parties) in that party's sole discretion, may exercise the Evergreen Option by giving notice to that effect, in accordance with Clause 6.9, to all other parties.
Comment
A. 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.
B. The above "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. In Bhasin (2014), the Supreme Court of Canada surveyed U.S. cases on this point. 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 the Bhasin case "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).
6.6.4. The Evergreen Option has a deadline for exercise of ten business days before expiration.
To exercise the Evergreen Option, the exercising party's notice of its exercise under section 6.6.3 must be effective no later than the stated time before the then-current expiration date of the Evergreen Period.
Comment
A. Some parties will want to adjust the opt-out deadline to take into account the circumstances — for example, if it would take the other party time to find and spin up a replacement contract relationship.
B. Caution: Opt-in and opt-out deadlines might be regulated by law, as discussed at 6.6.12.2.
C. Caution: 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 righs — or being stuck with past agreements for longer than they anticipated. Example: One of your author's software-vendor clients once found itself in such an unhappy situation: In a contract from before my time, the vendor had agreed to lock in — for a total of ten years — the initial, steeply-discounted pricing it had extended to a particular very-large customer, because the vendor hadn't calendared an automatic renewal at the five-year point.
6.6.5. Terms and conditions will be the same upon renewal.
Any renewal or extension under this Clause — being automatic without affirmative party action — will be on the same terms and conditions as before unless both parties agree otherwise.
For emphasis: A party's failure to object to a proposed change to terms and conditions does not constitute the party's agreement to the proposal (unless the Contract allows for unilateral amendment by the proposing party).
Comment
A. Subdivision 1: The parties would be free to amend the Contract (see Clause 6.1) in connection with an extension, of course.
B. Subdivision 2: Perhaps a party with unilateral-amendment rights (see Clause 6.2), if any, could do some sort of contingent notice of opt-in or opt-out, combined with a proposal for unilateral amendment.
6.6.6. The renewal duration is limited to a maximum of one year.
Unless the Contract clearly states otherwise, each renewal of the relevant Evergreen Period will be for the lesser of: (i) the initial duration of the Evergreen Period; and (ii) the stated period.
Example: A six-month Evergreen Period would be automatically renewed for successive six-month terms, without a break.
Example: A three-year Evergreen Period would be automatically renewed for successive one-year terms (if the Contract does not state otherwise), likewise without a break.
Comment
A. This section puts an upper limit on the duration of an automatic extension (the parties are of course free to affirmatively agree to any extension they want). That's because too-long an automatic-extension period can be problematic, as discussed in the cautionary tale at 6.6.4.
B. Pro tip:Initial renewals 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.
6.6.7. The Contract may limit the number of successive automatic renewals.
The Contract may limit the maximum number of automatic renewals, but this Clause does not do so.
6.6.8. Recommended: Evergreen reminder
This section presupposes that the Contract does allow one party, referred to (for convenience only) as the "Customer," but does not allow the other party, referred to (ditto) as the "Supplier," to opt out of, or opt into, automatic renewal of the Evergreen Period.
The Supplier should consider sending a written reminder of each upcoming automatic-renewal option deadline to be sent to the Customer — which preferably should be received or refused by the Customer, or undeliverable after reasonable efforts: (i) no earlier than 60 days, and (ii) no later than 30 days, before the upcoming automatic-renewal date.
Comment
This section falls in the general category of, "try to put the burden on the other party to calendar important dates and send out reminders."
6.6.9. Procedure if a mandatory evergreen reminder is not sent
This section will apply if:
the Contract requires a written reminder to be sent as described in § 6.6.8;
the Supplier does not timely provide such a reminder, and
the prerequisites in this Clause for automatic renewal are otherwise met.
The automatic renewal will go into effect, but only on a day-to-day basis.
The Customer may belatedly opt out of further day-to-day renewals of the Evergreen Period by so advising the Supplier in writing, effective when so stated in that written advice.
The Customer's belated opt-out right is the Customer's EXCLUSIVE REMEDY for the Supplier's failure to send the reminder.
Comment
This is provided because some customers will want their suppliers to take on the burden of remembering (that is, calendaring) the option deadline date.
6.6.10. Option: Fee for Early Opt-Out
If this Option is agreed to, it presupposes that a party (the "LeavingParty"), authorized to opt out of an automatic renewal, does so before 50 YEARS after the effective date of the Contract.
The Leaving Party is to pay the other party an early-opt-out fee of USD $1 TRILLION.
The early opt-out fee is due no later than exactly 11:59.00 p.m. UTC on the then-current expiration date of the Evergreen Period.
If the Leaving Party does not timely pay the early opt-out fee, then the automatic renewal will go into effect — and the Leaving Party's right to opt out of the renewal will expire — with no further action by any party.
In case the question comes up: Payment of the early-opt-out fee of this Option is intended as a form of alternative performance and not as liquidated damages.
Comment
A. This Option is inspired by an analogous provision in a 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).
B. Obviously the default values here are so absurd as to be laughable — that's to get drafters' attention.
C. For an extended discussion of alternative performance versus liquidated damages, see 3.13.3.
6.6.11. Option: No Evergreen Renewal After Assignment
If this Option is agreed to, then automatic renewal under this Clause will not occur at any time after an assignment of the Contract by either party.
In case of doubt: This Option does not authorize, neither does it restrict, assignment of the Contract.
Comment
A. 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 …."
The word "renewal" seems to be the common vernacular among business people (and even lawyers). But: The word "renewal" might require a party to renegotiate as a condition of being able to exercise an option to renew. That happened in Camelot LLC (2012), where the Eighth Circuit held that the AMC movie theater chain's option to extend its lease of space in a Minnesota shopping center — literally labeled "Option to Extend," and "on the same terms and conditions" except for certain rent adjustments — was really an option to renew, which gave the landlord the right to demand new terms. Camelot LLC v. AMC ShowPlace Theatres, Inc., 665 F.3d 1008, 1011-12 (2012) (8th Cir. 2012).
(As I noted at the time in a blog post, the most parsimonious explanation of the court's holding could be that AMC simply got home-towned.)
Counterexample: Citing Black's Law Dictionary, the Third Circuit held that a "renewal" of an insurance policy "requires continuation of coverage on the same, or nearly the same, terms as the policy being renewed." Indian Harbor Ins. Co. v. F&M Equip., Ltd., 804 F.3d 310, 315 (3d Cir. 2015) (cleaned up, footnote omitted).
6.6.12.2. Caution: The law might regulate opt-out or opt-in deadlines
A. 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.
B. If a contract requires a party to opt in to automatic extension (as opposed to the opt-out default approach of this Clause), then a court might strictly enforce the deadline for opting in; this happened, for example, in the Fifth Circuit's Pizza Inn (2020), where a restaurant franchisee blew the deadline for exercising a renewal option and Pizza Inn declined to allow renewal. 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).
6.6.12.3. Caution: Some jurisdictions might restrict evergreen provisions
By law, some jurisdictions restrict automatic extension or renewal of certain contracts (often consumer-facing) unless specific notice requirements are met. For example: As of 2021, a New York statute requires clear and conspicuous disclosure of automatic renewal terms in consumer service contracts, as summarized in a number of law-firm memos.
And on the other side of the coin: A Minnesota statute, Minn. Stat. § 325E.37 § 3, regulates termination of sales-representation agreements; it requires 180 days notice of intent not to renew [sic] a sales-rep agreement that does not have a definite term. Minn. Stat. § 325E.37 § 3; discussed inEngineered Sales Co. v. Endress A. Hauser, Inc., 980 F.3d 597, 599-600 (8th Cir. 2020) (reversing and remanding summary judgment).
This Clause will apply except to the extent — if any — that the Contract clearly says otherwise.
6.7.2. What — if anything — is exclusive about the Contract?
Nothing about the Contract is exclusive to either party.
6.7.3. Must either party share profits or otherwise "account"?
No party A to the Contract is required:
to share revenues or profits with any other party B to the Contract; nor
to otherwise account to B for A's activities relating to the Contract.
Comment
In this context, the term "accounting" has a special meaning that's seen in, for example, U.S. copyright law, which requires that co-owners of a copyright in a work of authorship, unless they agree otherwise, must "account" to one another for their uses of the work — basically, this means sharing profits and/or royalties; see generally the commentary to Clause 8.39.6.
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.
6.7.4.2. Silence might be interpreted either way
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: The 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).
Counterexample: 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).
6.7.4.3. 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 supplier 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.
6.7.4.4. 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.
6.7.4.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 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.).
6.7.4.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.
6.7.4.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.
6.7.4.8. Oh, and: Keep a copy of the f[ine] 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). (NWAOnline.com is the Web site of the Northwest Arkansas Democrat-Gazette, not of the gangsta-rap hip-hop group N.W.A.).
6.7.4.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)
6.8. Independent-Contractor Clause
Contracts often declare that the parties are "independent contractors." Typically, such declarations are an attempt to avoid having a court hold that a contractor is eligible for benefits that its customer gives to its employees; that the customer must pay employment taxes; or that the customer is vicariously liable to third parties for the contractor's errors and omissions in the same way as it might be for those of an employee under the principle of respondeat superior.
But as discussed in the additional commentary, saying so will not necessarily make it so, and a court might disregard such a declaration.
6.8.1. The parties intend to be independent contractors.
All parties intend for their relationship under the Contract to be that of independent contractors — not partners, agents, or fiduciaries — except to the limited extent (if any) that the Contract clearly says so.
Comment
This declaration of intent is also meant to try to forestall claims of "partnership" liability for each other's businesses (see 6.8.4.2) as well as claims of the heightened duties that a fidicuary or agent has towards toward the principal (see 6.8.4.3).
6.8.2. Each party is to conduct itself accordingly.
Each party is to conduct itself consistently with independent-contractor status under the Contract.
Each party "Alpha" is to defend and indemnify each other party and its Protected Group against any third-party claim arising from alleged conduct on Alpha's part that is inconsistent with this Clause.
Comment
Subdivision 1 is an affirmative obligation, intended to make it a breach of contract for a party to behave inconsistently with independent-contractor status.
6.8.3. Examples of independent-contractor obligations
The following actions — not an exclusive list — would normally be "off limits" for independent contractors:
making a promise, representation, or warranty, supposedly on behalf of another party, concerning the subject matter of the Contract;
holding one's self out as an employee, agent, partner, joint venturer, division, subsidiary, branch, or other representative of another party;
hiring any individual to supposedly be an employee or agent of another party;
setting the working hours or working conditions of another party's employees or agents;
selecting or assigning any employee of another party to perform a task;
directing or controlling the manner in which any employee or agent of another party performs his- or her work — as distinct from specifying the result to be accomplished by that work;
removing any employee or agent of another party from a work assignment;
firing or otherwise disciplining any employee or agent of another party;
incurring any debt or liability that is supposedly binding on another party.
6.8.4.1. A court might disregard an independent-contractors statement
A court might give little or no weight to a declaration such as that this Clause; 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; in that case, 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 ….
6.8.4.2. Saying "we're not partners" tries to avoid a possible danger
A. This Clause tries to put a Band-Aid® on a common business situation that theoretically could be dangerous (although the present author's 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."
B. 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).
C. 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.
D. 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.
6.8.4.3. Why disclaim "agent" or "fiduciary" status?
A. This section aims to roadblock future claims that one party was supposedly another party's "agent" or "fiduciary" and therefore legally obligated to give the other party's interests priority above the first party's own interests. 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).
B. On the other hand, an "agent" relationship might be called for in some channel-partner agreements.
C. 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 to the tune 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).
D. 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 2024 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).
6.8.4.4. BTW: A principal can (usually) act without using its agent
By the way ("BTW"): Suppose that Fred and Ginger enter into a contract. If Fred is found to be Ginger's "agent," then (in general) Fred may deal with third parties, e.g., Billy, on Ginger's behalf and make contractual commitments that are binding on Ginger. (For that reason, in Ginger's contract with Fred, Ginger might want to state specifically that Fred isn't her agent, as in section 6.8.4.3.)
And now let's suppose that Fred and Ginger agreed that Fred would be Ginger's agent, and in fact, Ginger's exclusive agent: Even under those circumstances, at least under Texas law, Ginger would still be free to make a deal with Billy without getting Fred involved and without paying Fred 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), citingAlba Tool & Supply Co. v. Indus. Contractors, Inc., 585 S.W.2d 662, 664 (Tex. 1979).
6.8.4.5. The Biden-era Labor Department's guidance
In January 2024, the U.S. Department of Labor announced the finalization of a revised rule to undo the Trump Adminstration's 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.
Editorial comment: The Biden DOL's announcement was not greeted with universal acclaim; as one management-side law firm posting aptly noted, 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).
6.8.4.6. The Biden Administration weighed in …
In 2021, the then-new National Labor Relations Board general counsel, Jennifer Abruzzo, appointed by President Biden, indicated 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. See 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).
This section is being edited on January 20, 2025; it remains to be seen what if anything the second Trump Administration will do with these Biden Administration policies.
6.8.4.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.
6.8.4.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 a ballot initiative, Proposition 22, classifying certain app-based drivers as independent contractors; the initiative passed with more than 58% of the vote.
6.8.4.9. Caution: Check state- and even city laws and ordinances
Companies wanting to do business with freelance workers as "independent contractors" should check whether any state- or local laws might govern such dealings. As noted by Kalk & Sandahl (2021), for example, beginning in January 2021:
The Minneapolis Freelance Worker Protections Ordinance requires businesses, and even some individuals, to enter into written agreements with particular requirements with most freelance workers.
Companies that breach those agreements can face stiff penalties from the City in addition to breach-of-contract and other statutory damages.
Companies, particularly those that are app-based, often design their business plan around an independent contractor model and are especially likely to feel the Ordinance's impact.
(Extra paragraphing added.)
In Los Angeles, the Freelance Worker Protection Ordinance, which went into effect in July 2023, might have been motivated in part by the extensive use of freelancers in the film- and music industries. For a summary, see Scott (2023).
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.
Any notice under the Contract must be in writing.
Comment
In many contracts, "notice" is required to trigger specified rights and/or obligations; this Clause aims to reduce the potential for after-the-fact "he said, she said" disputes about whether notice was or was not given at a particular time.
6.9.2. Notices must be in a language readable by the addressee party.
The notice — or at least a prominent, "get this translated!" alert — must be written in a language that the addressee's relevant people can read.
Comment
This requirement is informed by the experience of a party that received a notice of arbitration in Chinese but didn't get the notice translated until it was too late to avoid big problems, as discussed in the [BROKEN LINK: ArbLang] clause.
6.9.3. Emojis will (usually) have no effect.
The other party is entitled to disregard any emoji in the notice unless it is clearly shown that, at the time of the notice, there was essentially zero question about the meaning of that emoji.
Comment
Emojis can be susceptible to disagreements about their meaning, but people do use them, so this Clause tries to accommodate that brute fact; see the discussion at 6.9.10.3.
6.9.4. Details for notice may be specified in the Contract.
The Contract may set out one or more of the following:
one or more required addresses for notice;
any required "Attention:" line in a hard-copy notice (which would be a good idea in any case);
any required means of delivery; and
any required copies, e.g., to legal counsel.
Comment
A. To reduce the chances of notices going astray, a party expecting to receive notices might want the Contract to specify that notices must be sent to the attention of a specific position or department (preferably not an individual); see 6.9.10.4 and 6.9.10.2 for discussion.
B. This Clause 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 a 2021 New York case, where the court held that notice by email was 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).
C. Caution: While an exchange of text messages can form a binding contract (see 28.1), 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 28.5.2.
D. When a notice is sent under the Contract, it's a good idea to send a copy to the attention of the notified party's legal counsel (but this Clause doesn't make it mandatory); see 6.9.10.6 for further discussion.
6.9.5. Effective date: "The Three Rs of Notice"
Unless otherwise agreed, notice will be effective (only) upon the earliest of receipt or refusal by the addressee, or after reasonable but unsuccessful efforts at delivery to the addressee, in any case as supported by (i) independent written confirmation — for example, certified-mail receipt or courier delivery report — or (ii) the addressee's stipulation.
Three Rs of Notice: If the parties have explicitly agreed to the Mailbox Rule in section 6.9.9, then receipt is presumed as stated there.
Otherwise, the notice's receipt, refusal, etc., is considered to have occurred only when
Comment
This "Three Rs of Notice" approach conforms to modern business practice; the old-fashioned Mailbox Rule (see section 6.9.9) can cause too many problems in business-to-business dealings, as discussed in the commentary at 6.9.10.7.
6.9.6. No party will try to evade notice.
A party may not attempt to evade notice.
Comment
Enough said.
6.9.7. Changes of address for notice are to be in writing.
Each party is to advise the other party, in writing, of any change in the first party's address for notice.
Comment
Formal notice of the change of address might be a good idea, but it isn't mandatory.
See 6.9.10.5 for an example of bad things that can happen if a notice gets sent to an outdated address.
6.9.8. "Written notice" means the same thing.
If in some places the Contract uses terms such as (for example) "written notice" or "notice in writing" (emphasis added), that's simply a convenient reminder, not a signal that non-written notice could be effective.
6.9.9. The "Mailbox Rule" must be specifically agreed to.
If the Contract clearly states that "the Mailbox Rule" will apply, then notices are rebuttably presumed to have been received on the date three business days after being deposited: • in an official mail receptacle of the jurisdiction where the notice is sent, • in a sealed, properly-addresed envelope, • either with first-class postage prepaid or in compliance with bulk-mail rules.
Comment
The Mailbox Rule isn't a great idea for B2B contracts; see the discussion at 6.9.10.7.
6.9.10. Additional notes (not part of this Clause)
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 Contract, for example, the fact that the contract had been assigned (see generally the commentary at Clause 8.4); and/or (2) to formally invoke a specific right or obligation under the Contract, such as, for example: making a demand; exercising a right; or terminating the Contract.
6.9.10.2. Use an "Attention:" line in a hard-copy notice
When sending notice in "hard copy" by mail, FedEx, etc., it's best to include an "Attention:" line — which should specify a position, not just an individual:
[ ] ABC Corporation (Attention: Jane Doe)
[ x ] ABC Corporation (Attention: Jane Doe, Vice President of Marketing)
This can help to reduce the chances of a notice going astray or falling through the cracks — this could happen, for example, if: • an individual addressee was no longer in the same job; and • the addressee's mailroom personnel set aside the notice until they could figure out what to do with it — and might never get around to that.
6.9.10.3. Emojis — allowed, but …
A. "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 one court noted, "while water [emojis] may reference sexual relations, case law also confirms that water can also refer to methamphetamine in drug trafficking communications."
B. Still: The brute fact is that people do sometimes use emojis in text messages and emails, and on occasion, in other written communications. So let's at least allow for the possibility that in some circumstances, it might make sense for emojis to be given effect in a notice under a contract.
C. But what if an emoji is ambiguous, as in the examples above? Just as with the contra proferentem rule (see 8.22), if an emoji in a notice is ambiguous — that is, the emoji could plausibly have more than one meaning — then the ambiguity should be resolved against the party that used the emoji in the notice, on the theory that that party could and should have been more clear.
United States v. Swanagan, No. 4:22CR-00003-JHM (W.D. Ky. Jan. 3, 2023) (denying motion to suppress LEO's affidavit; citation omitted).
6.9.10.4. Specify an address for notice?
A. A party might want to specify that notices must be sent to a specific position or department. One possible use case: An insurance policy will typically require the insured, within a specified time, to notify the carrier of claims made against the insured; the notice provision might specifically require that the notice be sent to the carrier's claims department, in which case the insured would not comply with the notice requirement merely by listing the claim in a policy-renewal application.
Example: The Third Circuit 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."
B. But any such mandatory-address language should indeed clearly be mandatory. Example: In one Fifth Circuit decision:
– 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 the term "Please" 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.
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."
C. 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, as discussed above.
Example: One of the present author's business friends once told of receiving a notice, by FedEx, from another party to a contract. • The 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."
That's … not how things should work. (And courts generally won't go along with such game-playing except in limited circumstances; see the commentary at section 2.3.1.)
A. Some contracts require formal notice of a change of address; that might be a bad idea, because it could lead to problems if a notices clause (i) required all notices to be sent by, for example, certified mail; and (ii) required changes of address to be communicated in that way.
B. 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: The well-known food company J.M. Smucker leased space in a commercial building in North Dakota. The lease term would automatically renew on July 1 of each year — which meant that nearly $280,000 in rent and utilities would have to be paid over the coming renewal year — unless Smucker gave notice, before the previous January 1 (i.e., six months in advance), that Smucker didn't want to renew the lease.
Five years later, the landlord sent Smucker a change-of-address notice. Evidently, though, the admin people at Smucker didn't update the company's records on that score.
Three years after that, Smucker decided not to renew the lease. On December 22, Smucker sent — to the landlord's old address — the required non-renewal notice; the next day, December 23, Smucker received an "undeliverable" notice from FedEx. This was Christmas time; Smucker waited until January 4 to send a replacement notice.
Outcome: Smucker ended up having to pay rent and utilities for an extra year for the space it was no longer using and didn't want.
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!)
6.9.10.6. Send a copy to the notified party's counsel?
A. Copying the notified party's legal counsel on notices can have two benefits:
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.
B. Some drafters like to specify that a copy to legal counsel "shall not constitute notice."
C. 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.
D. 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.
E. Some parties specify that a copy to the notified party's counsel does not constitute notice; I'm on the fence whether that's a good idea (it might vary with the type of contract).
6.9.10.7. Use the Mailbox Rule? (Probably not for B2B contracts.)
A. What is the Mailbox Rule, exactly? As one Texas court explained:
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.
The Mailbox Rule's presumption of receipt might even be imposed by statute.
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.
B. 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 the author's former students in another context).
Example: In 2014, the Third Circuit 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.
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.
C. 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 is to be mailed from one country to another.
Comment
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).
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).
Comment
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).
6.9.10.8. Consider the context 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 noteworthy final result on appeal, a Texas 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.
6.9.10.9. 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. Example: 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 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.)
6.9.10.10. 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: In a 2020 Fifth Circuit decision, 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.
6.9.10.11. 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.
But that won't always be the case. Example: In 2021 a New York appellate court held that a party's sending notice by email had been ineffective because the parties' contract required notices to be sent by first-class mail.
Example: In a 2022 decision by the Texas supreme court:
– A construction contract set forth a procedure for termination; the procedure stated that that if the project owner wanted to fire the contractor and recover damages for default, the owner had to give three, separate, written notices.
– The owner gave only one of the three notices in writing; the other two notices were oral.
– A jury found (among other things) that the owner had "substantially complied" with the termination protocol; the trial judge entered judgment largely on that verdict, and a court of appeals affirmed on that point.
– The state's supreme court, though, ruled that — given the particular wording of the contract's termination protocol — strict compliance with the protocol was indeed required, and that substantial compliance was not enough.
Comment
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).
6.9.10.12. 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 2024 UK case, the 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 held:
50. Whether a notice is sufficient to satisfy the requirements of any given clause must depend primarily on the language of the clause. Commercial parties are free to impose whatever requirements they wish. However, where they use broad and general terms such as 'the nature of the claim' and 'in reasonable detail', those requirements should be interpreted in the light of the commercial purposes of such clauses, including those identified in [a prior case].
It is important that Notice of Claim clauses should not become a technical minefield to be navigated, divorced from the underlying merits of a buyer's claim.
While a seller's interest will always be to knock the claim out if it can on the technical ground that the notice is insufficient, 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.
51. … [P]arties do not normally give up valuable rights without making it clear that they intend to do so.
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.
When agreed to, this Clause will apply when both of the following are the case:
the parties have clearly indicated, orally or in writing, that the Contract or other document (the "Signature Document") has been finalized and is ready for signature, and
a party P signs the Signature Document and sends it to another party OP.
6.10.2. The signing party certifies no undisclosed changes to the agreed final version
By signing and sending the Signature Document to OP, the party P represents to B that what P is sending is the previously-agreed final version, without changes, unless P explicitly alerts OP, in writing, that changes were made.
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 Clause 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 6.10.3.2 below.
6.10.3.2. Signature-document fraud does happen …
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: Your author 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: He changed a two-year post-employment noncompetition covenant to a two-month covenant — and 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.)
In due course, the executive resigned from the company, took his wife on a two-month European vacation — and 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 motion; the case settled soon afterwards.
Some "inside baseball" for litigators: For the company's 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, not the law, because courts generally don't allow lawyers to testify as expert witnesses at trial about the law — it's the exclusive province of the judge to instruct the jury about the law.
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).
6.10.3.3. A document-integrity representation (not a warranty)
This is a representation about signature-document integrity, not a warranty. That's intentional; here's why:
A. At the end of a fiscal quarter, a lot of sales contracts are likely to be in progress at once. 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.
B. 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 representation clause often comes across as "softer" than a warranty clause, and so might be less likely to trigger a visceral objection from the customer's people.
C. To be sure, a representation can 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.
D. 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?")
E. 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.
6.10.3.4. … 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: 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).
6.10.3.5. What if a party doesn't want to agree to this Clause?
Caution: If a party objects to including this Clause 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 once that I can recall: A 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 quickly overruled the associate and said, "Oh no, of course we'll agree to this."
6.11.1. Counterparts: Parties can sign separate copies
the Contract and related documents — each, a "document" — may be separately signed in separate copies ("counterparts") if desired.
Comment
A. It's common for each party to want its own, fully-signed "original" of a contract; the above language provides for that.
B. If hard copies are going to be manually signed, see 24.4 for suggestions on how to draft the signature blocks to avoid possible challenges later.
6.11.2. Just signed signature pages can be delivered.
A signed document may be delivered by delivering just the signed signature page, but only if the circumstances clearly establish which version of the document was signed — for example, with a manually-typed date code (i.e., one that does not automatically update itself) in a running header on each page of the document.
Comment
A. Nowadays it's quite common for the parties, in different locations, to sign separate copies of a contract and for each party to email the other party a PDF of its signed signature page only; the above language supports this practice.
B. Caution: As discussed at 6.11.6.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.
6.11.3. Electronic signatures are agreed to.
The Contract and any related document may be signed and/or delivered electronically.
Comment
See the discussion of electronic signatures at 13.3.
6.11.4. Signed documents may be escrowed.
Any party may deliver signed documents (and/or signed signature pages) into escrow if the circumstances indicate that the parties so agreed at the time.
Comment
A. Signature-page escrow typically involves an attorney for one party P receiving a signed signature page from another party OP, but holding it "in escrow" pending some specified event, such as OP's receipt of payment or of own P's signed signature page. 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").
Example: Here's an actual anonymized email from a corporate acquisition deal in which your author represented the seller, a software company that I'd helped the founder to start a few years earlier:
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.
B. More-elaborate signature escrow provisions such as this one can be found at the LawInsider.com site. (These are likely to be overkill in many situations.)
6.11.5. Signers certify that they've read and understood the document.
If a party P signs a document and delivers it to another party OP, then P is acknowledging:
that P had a sufficient opportunity to read the document, to ask for clarification, and to consult P's own legal counsel if desired; and
that, in deciding whether or not to sign, P was not entitled to rely — and did not rely — on advice from OP's legal counsel or other adviser.
6.11.6. Additional notes (not part of this Clause)
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.
Caution: 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: For that reason, a signature page should preferably be tied to a specific version of the Contract by including, on each page of the Contract, 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 an automatically-updating "field." (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.)
6.11.6.2. Pro tip: 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.
This Clause will apply whenever, in the Contract or a related document, a party acknowledges a statement of fact and/or of law (the "Statement").
Comment
Why use acknowledgements? Having a party "acknowledge" one or more things in a contract can be useful to establish 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.
7.1.1.2. What effect does the acknowdgement have?
When a party acknowledges a Statement, that party:
is agreeing that the Statement is true for purposes relating to the Contract, and
WAIVING8.68 any requirement that would otherwise require a party to the Contract (other than the acknowledging party itself) to produce evidence to support the Statement.
Comment
Who could take advantage of an acknowledgement? This Clause waives any requirement of proof that would apply to a(nother) party to the Contract. That's because it'd be pretty open-ended for an acknowledging party to agree that any random stranger to the Contract could take advantage of the acknowledgement.
7.1.1.3. Can an acknowledgement be withdrawn?
Applicable law will govern whether party may later contradict, modify, or withdraw an acknowledgement of a Statement.
Comment
How "stuck" would an acknowledging party be? An acknowlegement could lock a party into a position that it might later want to modify or even disavow based on updated information. The above language follows the general rule in, e.g., U.S. federal-court cases, where the trial judge has discretion to allow a party to back away from a previous admission, under Rule 36(b) of the (U.S.) Federal Rules of Civil Procedure.
7.1.2. Case study: Stuck with patent royalty obligations
Example: In a Tenth Circuit case:
A German company, Peiker, contracted for a license under certain patents.
In the license agreement, Peiker had "acknowledged" that two of its 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:
But [certain other contract language] does not prevent the parties from agreeing that a royalty is due on a non-infringing product if doing so would benefit the convenience of the parties.
And we do not see anything in the License Agreement that can transform Peiker's acknowledgments to rebuttable presumptions. See I Oxford English Dictionary 108 (2d ed. 1989) (defining "acknowledge" as "to recognize or admit as true").
The Colorado Supreme Court has held that acknowledgements, when included in a formal contract, can be "the best kind of evidence." Because the parties acknowledged that all products falling within the terms of 1.17(i) utilize technology, designs, or architectures covered by one or more of the claims included in the Licensed Patents, no infringement analysis is necessary. By its own force, the contract requires Peiker to pay royalties on those products included in sections 1.17(i) and 3.5 of the License Agreement.
7.1.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.
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: In a South Carolina employment dispute:
A company sent an email to its employees asking them to click on an online "acknowledge" button; the accompanying text said that the employee was acknowledging a company mandate that employees read a new policy requiring binding arbitration of disputes.
One employee clicked on the "acknowledge" button — then, five years later, she was fired and sued the company, which responded by moving to compel arbitration under the "new" prolicy.
The state supreme court held that what the employee had acknowledged — i.e., a directive to read the new policy — hadn't modified the employee's pre-existing employment contract; consequently, arbitration was not required. See Lampo v. Amedisys Holding, LLC, Op. No. 28265, slip op. (S.C. Mar. 5, 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 agreed with the Second Circuit's holding 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), affirming401 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.
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.
7.1.4. An acknowledgement invites reliance
As discussed at 3.17 (and illustrated in the "Hill of Proof" diagram at 3.17.2): Suppose that another party OP wants to claim that the acknowledging party P made a false representation. OP must show:
that OP relied on the representation, and
that OP's reliance was reasonable.
But if AP acknowledged the statement in a contract with OP, then OP would likely have a much-easier time making both of those showings.
7.1.5. 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. Here's an overreaching example of a kind that's sometimes seen in confidentiality agreements ("NDAs"):
Recipient acknowledges that Discloser would be irreparably harmed by a breach or threatened breach of Recipient's confidentiality obligations under this Agreement.
The intent here is presumably for Recipient to waive Discloser's burden of proof in seeking a preliminary injunction or comparable relief (see 8.29).
This would slow up getting the NDA signed, because confronted with such an acknowledgement clause in the draft NDA, many Recipient counsel would probably:
delete this equitable-relief acknowledgement entirely, or
change "would be …" to "could be irreparably harmed" — AND
be irritated at Discloser's counsel for the obnoxious drafting.
7.1.6. Appendix: Some other acknowlegement examples "in the wild"
10. Representations, Warranties and Guarantees[sic]. a. … Vendor acknowledges and agrees [sic] that it shall be a breach of its representation, warranty and guarantee if any Goods are in violation of any Laws at any time, including after the sale of such Goods by Vendor to Purchaser. … Vendor acknowledges that its obligations under this paragraph are an appropriate allocation of risk between Vendor and Purchaser.
1. Employee Acknowledgment. Employee has been provided with, and hereby acknowledges receipt of, a Prospectus for the Plan, which contains, among other things, a detailed description of the Other Share-Based Awards provisions of the Plan. Employee further acknowledges that he or she has read the Prospectus, the Plan and this Agreement (including the Jurisdiction-Specific Addendum), and that Employee understands the provisions thereof.
(Emphasis added.)
7.1.7. Not quite the same: Notarized acknowlegements
An acknowledgement in a notary certificates (a.k.a. "notarization") will generally have somewhat-similar effect, in that someone signing a document:
usually must provide identification to the notary public (or other official); and
states to the notary that he or she (the signer) in fact signed the document that's being notarized.
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. • Pro tip: Keep in mind that non-parties might sometimes be affected by this Definition, as discussed at 7.2.7.
the Contract otherwise clearly says that they are.
Comment
How is "affiliate" usually defined? For the most part, this Clause 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.
7.2.1.2. Affiliate status can arise through control
Two persons are affiliates if:
one person "controls" the other (as defined below), directly or indirectly; or
the two persons are under common control, that is, under the direct- or indirect control of a third person. 7.2.2
7.2.1.3. Control can exist via board-selection power
For purposes of determining affiliate status, a person controls an organization if the person holds the legally-enforceable power 7.51 to elect or appoint more than 50% of the members of the organization's board who are entitled to vote to approve or disapprove a proposed board action.
Comment
What voting percentage is appropriate for control? As is pretty typical, the 50% number in this Clause 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.
7.2.1.4. What if there's class-based voting?
For purposes of determining affiliate status: If an organization's voting shares are divided into classes, then control requires the requisite percentage in each such class.
7.2.1.5. Control can exist through legal management power
For purposes of determining affiliate status, one party controls another party if the first party has the legally-enforceable power 7.2.3 — for example, by an enforceable contract — to direct the other party's affairs.
7.2.1.6. Could affiliate status change?
A non-affiliate could become an affiliate by qualifying as such, and an existing affiliate could lose that status if circumstances were to change.
Comment
Gaining or losing affiliate status? 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, 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).
7.2.2. A real-world example: Google, YouTube, etc.
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.
7.2.3. Caution: Don't use unspecified "management power" for control
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).
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 a 2010 Fifth Circuit case, 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 a 2010 New York case, 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).
7.2.4.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 can be disastrous for other parties. Example: In a Seventh Circuit case:
The plaintiff, Northbound, was having business difficulties and badly wanted to be acquired by the defendant, Norvax.
When Northbound entered into the acquisition agreement, the other named party was not Norvax, but Leadbot, which was a newly-created subsidiary of Norvax: Leadbot was to acquire Northbound's assets and pay the purchase price in the form of an earnout.
Evidently Northbound couldn't get Norvax to guarantee Leadbot's payment obligations (see 2.10) — and sure enough, later a dispute arose over payments that Leadbot had withheld.
Northbound went to court for the withheld payments; it sued not just Leadbot — which had no assets and so was judgment-proof — but also Norvax, i.e., the parent company of Leadbot.
Norvax 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 [Northbound] is entitled to damages for breach of contract, it cannot recover them in a suit against [Norvax] because [Norvax] was not a party to the contract." Quoting one of its prior cases, the appellate court also implicitly noted that Norvax had not guaranteed Leadbot's payment obligations; the trial court had previously noted that "Northbound has offered no evidence that Norvax agreed to be liable for Leadbot's debts, obligations, and liabilities …." Northbound Group, Inc. v. Norvax, Inc., 795 F.3d 647, 650, 653 (7th Cir. 2015) (cleaned up, emphasis added), affirming5 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).
7.2.5. Caution: The parties aren't "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: The issue was (still is?) 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).
7.2.6. 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 Option 8.54.10.1).
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 7.2.4.
7.2.7. Could the Contract bind a non-signatory affiliate?
An affiliate of a contracting party might be bound by the contract if:
the contracting party — or the person signing on behalf of that party — controlled the affiliate, and
the contract stated that the contract is to 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).
7.3. After (or from) Definition
7.3.1. Clause text
Defining by example: 30.10.2 A time period of one year after (or from) June 30, 20x4 will end at exactly12:00:00 midnight, in the relevant time zone, at the beginning of June 30, 20x5.
7.3.2. Why define "after" or "from"?
Some contracts specify that particular obligations and/or benefits will exist only during a stated period "after" or "from" a particular date or event. This has led to high-stakes litigation, because the precise end time of an "after" or "from" period could have significant consequences. Example: In a factually-complex case 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. See Apache Corp. v. Apollo Exploration, LLC, 670 S.W.3d 319, 321 (Tex. 2023) (reversing and remanding court of appeals). The court's opinion recapped prior efforts to define "after," going back to Texas's pre-statehood days.
7.4. All Definition
7.4.1. Clause text
The term "all" means just that, unless a party were to plead and prove (1) mutual mistake or (2) fraud — in either case as provided by law — even if that party did not know and could not have known of particular things that were encompassed by the term.
7.4.2. Why define "all"?
You might think that the term "all" doesn't need to be defined, but disputes on that subject have been known to arise. See Wohlt v. Wohlt, 245 N.E.3d 611 (Ind. 2024), affirming222 N.E.3d 964 (Ind. App. 2023).
Example: The Sixth Circuit rejected an assertion that, in a settlement agreement, a release of "any and all claims" required the parties to enumerate the types of claims that were intended to be released:
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 [Tenn.], 98 F.4th 688, 691 (6th Cir. 2024) (reversing district court; release of "any and all claims" barred claim).
When this Clause is agreed to, the term "and/or" means the inclusive or, that is, "one or more of the things listed here." 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.
For emphasis: This Clause does not mean that the term or, by itself, is necessarily the exclusive or — that would be determined in the usual way.
7.5.2. Why "and/or" might be important
A problem with using the term "or" alone is that, in some circumstances, a court might read "or" as being tantamount to "and." Example: A federal court once noted:
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: In a Delaware case, the 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. 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 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 (U.S. 2024).
So: It can be useful to say and/or to be clear what's meant.
7.5.3. Another reason to define: Respond to scornful purists
Amusingly, the term and/or has provoked scorn from some purists, as well-documented in Robbins (2018).
Granted, it's possible to use and/or inappropriately, as with any term; see, e.g., the examples collected by the director of the legal-writing program at the University of Texas School of Law; see Scheiss (2013).
But as Professor Robbins correctly notes (at 311):
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.
(Emphasis and extra paragraphing added).
Moreover, trying to ban and/or entirely is almost surely a bootless errand: Drafters will continue to use and/or because of its utility.
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!)
7.5.4. Are there alternatives to saying and/or?
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." Adams (2012) (emphasis added).
In the final paragraph of one Minnesota case, a state-court judge — no slave to brevity, it would seem — 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),
7.6. As-Is Definition
Many contracts use "AS IS" as a shorthand disclaimer of warranties and representations, often in all caps for conspicuousness. Colloquially, "as is" means, more or less, "you get what you get, and don't get upset." * Such statements can pay off for businesses.
* (I'm borrowing here an expression I once heard used by a then-preschooler in my extended family — hi, Ryan!)
7.6.1. Clause text
7.6.1.1. Definition
The term "as-is" is shorthand for a disclaimer of all impliedwarranties, representations, [BROKEN LINK: as-is-uk], and terms of quality — each, generically, an implied "Warranty" — about the matter(s) in question.
Comment
Why disclaim implied conditions and terms of quality? The disclaimer of implied conditions and terms of quality is a nod to the law of England, Wales, and Northern Ireland. Example: In the England and Wales High Court, an oil seller learned — presumably to its dismay — that its contractual disclaimer of (only) implied warranties was not enough to shield it 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).
Payoff for as-is statements:Example: At the start of the COVID-19 pandemic, Amazon stopped providing its "Rapid Delivery" service to Amazon Prime subscribers without telling them — while continuing to collect full price. A Prime subscriber brought a putative federal class action lawsuit against Amazon. The district court, though dismissed the case, and the Eleventh Circuit affirmed, because Amazon's terms of service had stated that services would be provided "AS IS" and "AS AVAILABLE." See Marquez v. Amazon.com, Inc., 69 F.4th 126 (11th Cir. 2023).
7.6.1.2. Details
For this purpose, it does not matter:
whether the term as-is is capitalized;
whether the term includes a hyphen; nor
whether the (purported) Warranty is implied in fact or implied by law.
Comment
All-caps? Drafters who use the term AS IS will often capitalize it, in case the law requires such terms to be "conspicuous" (a topic discussed in more detail at 11.11).
7.6.1.3. Express written warranties unaffected
The term as-is does not disclaim any express, written Warranty in the Contract (which by definition would not be an implied Warranty).
7.6.1.4. Implied warranty of title to goods unaffected
The term as-is does not disclaim any implied Warranty of titleto tangible goods or other tangible objects being conveyed — as distinct from an implied Warranty of noninfringement — which is disclaimed), when such a Warranty is implied by law.
Comment
UCC example: An example of such an implied warranty of title can be seen in UCC § 2-312 — because even when a buyer is acquiring goods "as is," the buyer still should be entitled to presume that it's not buying stolen goods.
Comment
IP infringement warranty? For warranty language about IP infringement, see Clause 8.36 and its commentary.
7.6.1.5. Disclaimer of implied warranty of infringement
The term as-isdoes disclaim any implied Warranty of noninfringement of intellectual property rights.
7.7. Best Efforts Definition
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!)
7.7.1.1. What level of effort does best efforts require?
The term "best efforts" refers to diligent reasonable efforts to achieve the stated objective.
Comment
This diligent-reasonable-efforts standard draws on the Restatement of Agency, which states 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).
7.7.1.2. What isn't required by a best-efforts obligation?
For emphasis: When the Contract requires a party to use best efforts, it does not mean that the party must do any of the following things (not an exhaustive list):
make any unreasonable effort;
harm the party's own lawful interests in any non-trivial way;
act as a fiduciary for another party;
make every possible reasonable effort; nor
actually succeed in achieving the stated objective.
Comment
What's not required for best efforts: This section is what our British colleagues might call a "for the avoidance of doubt" provision, to try to steer clear of disputes — and differing court views — that have arisen in some past cases; see the additional reading beginning at 7.7.2.
C. Caution: The carve-outs in this section 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.
Comment
Nontrivial self-harm not required: This borrows from a Second Circuit remark that a best-efforts obligation "did not require Falstaff to spend itself into bankruptcy to promote the sales of Ballantine products …." Bloor v. Falstaff Brewing Corp., 601 F.2d 609 (2d Cir. 1979) (affirming holding that Falstaff had breached its best-efforts obligation).
Comment
Not a fiduciary: seeks to roadblock 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). To similar effect, see 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."
Comment
Exhaustive efforts not required: This disavows one line of contrary court decisions, discussed at 7.7.3.
Comment
Success not required: There'd be no need for a best-efforts obligation if the parties agreed to require achieving the stated objective — they'd just say that.
7.7.1.3. What input would the other party have into the efforts required?
The parties are urged to consult each other about whether a best-efforts obligation would be satisfied by a particular course of action — especially a course of action not yet taken.
Comment
Consultation about best efforts: This is one of those areas where the Pick up the phone! general motif of this book can pay dividends.
7.7.1.4. What if the parties disagree about best efforts?
At either party's request, the parties will escalate any persistent disagreement about what best efforts would be required when an agreed time for making such best efforts has not yet ended — first, to supervisors, see Clause 6.5, and if necessary to a neutral advisor, see Clause 6.4 — in the hope of enhancing the chances of early resolution of the disagreement.
7.7.2. Are just "reasonable efforts" enough?
Some — but not all — U.S. courts have seemingly equated 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).
In its much-noted 2017 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.
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 California Pines court (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 inCalifornia 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).
7.7.4. 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).
7.7.5. Some 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 motivated 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.
7.7.6. 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).
7.7.7. Some best-efforts analogies can be useful explainers
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.
7.7.8. "Comparables" might be a good yardstick
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 by Judge Posner:
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.
7.7.9. 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.
7.7.10. Could more-precise language work better?
Contract drafters considering a best-efforts obligation should consider stating:
as specifically and un-vaguely as possible: just what the best efforts are supposed to try to do;
clear, specific actions that the obligated party is allowed to take — or required to take — in complying with the best-efforts obligation;
particular considerations that the obligated party could take into account in deciding what specific actions to take; and/or
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.
7.7.11. Optional: Further reading about best efforts
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 7.7.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.
7.8. Business Day Definition
Clause text
The term business day (whether or not capitalized) refers to Monday through Friday except days that banks in New York City are generally closed.
Comment
Business day — when banks are open: 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).
7.9. Calendar Year Definition
7.9.1. When does a specified calendar year start and stop?
A specified calendar year (e.g., the year 2030):
begins at exactly 12:00.00 midnight at the beginning of January 1 of that year; and
ends at exactly 12:00.00 midnight at the end of December 31 of that year.
Comment
This definition should be unremarkable.
7.9.2. What time zone(s) are to be used?
If only one time zone is relevant, then the 12:00.00 midnight in question is in that time zone on the date in question.
Otherwise (in the interest of standardization), the 12:00.00 midnight is in the time zone of the latest occurrence of the stated time on the date in question.
Example: If both California time and Tokyo time are relevant, then 11:59.00 p.m. on December 31 is that of California (in Tokyo it is already 4:59.00 p.m. on January 1).
Comment
For reader convenience, this section intentionally duplicates the time-zone provision of Clause 7.49 (time of day), even though that goes against the Don't Repeat Yourself guideline discussed at 29.15.
7.9.3. Which calendar is to be used?
Unless clearly agreed otherwise, the Western (i.e., Gregorian) calendar is to be used for all calendar-year determinations.
Comment
Some Muslim countries or other places might do business on a (non-Gregorian) lunar calendar; see generally Adams (2013) and the reader comments there.
7.9.4. What about calendar years "from" a date?
A period of one calendar year beginning on (for example) July 1 ends at exactly 12:00.000 midnight at the beginning of July 1 in the following year.
Comment
The precision of this "12:00.000 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 7.26.
7.9.5. What about 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.
Comment
People with February 29 birthdays can no doubt relate.
7.9.6. And calendar years following a date?
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.
7.10.1. What does it mean if a party "certifies" something?
If a party certifies a statement, whether in the Contract or in a related document, then unless the certification clearly states otherwise, the certifying is doing the following things:
warranting that the statement is true;
representing that, so far as the certifying party is aware, (i) the statement is true, and (ii) no one has asserted otherwise;
acknowledging that the certifying party caused a reasonable investigation to be made before the certification; and
acknowledging that any other party to the Contract (i) is entitled to rely on the certification, and (ii) will be doing so.
Comment
A. Motivation: Some contracts require one party to "certify" in writing that the certifying party has complied with specified contract obligations; see, e.g., Option 8.19.1. What does that mean?
B. Subdivisions 1 and 2: See the discussion of representations and warranties (and the difference between them) at 3.17.
C. Subdivisions 2 and 3 are to give other parties to the Contract some comfort that CP actually knows what it's talking about in making the certification.
D. Subdivision 4: This acknowledgement is included because a party alleging misrepresentation must usually prove (among other things) that the party relied on the representationand that its reliance was reasonable; this subdivision makes both of these things clear.
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.
7.11.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 3.15.8 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.)
7.12. Claim Definition
7.12.1. What does claim mean?
The term "claim" — whether or not capitalized — refers to any request or demand for damages, an injunction, and/or any other form of legal- or equitable relief, by one or more individuals and/or organizations.
Comment
A. 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.
In case of doubt: A claim could be set forth, without limitation:
in a written communication such as, for example, a letter or email; and/or
in a filing with, or a submission to, a tribunal of competent jurisdiction.
Comment
Subdivision a: 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.
7.12.3. Do governmental allegations or charges count?
A claim could be made by (without limitation) one or more government authorities.
7.12.4. Are "claims" only those made in litigation?
A claim could be made in any forum, official or otherwise, allegedly having the power to award such relief.
For emphasis: The term claim encompasses — without limitation — counterclaims and cross-claims, and not merely claims in "kick-off" documents such as complaints, original petitions, and the like.
Comment
Subdivision b: Concerning counterclaims, see generally 11.17.
This Clause will apply if the Contract requires a particular factual allegation by a party to be supported by "clear and convincing evidence," as compared to the lower, "preponderance of the evidence" standard mainly used in civil cases.
Comment
A. Motivation: 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).
B. For completeness: 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.
7.13.2. What's required for clear and convincing evidence?
The term "clear and convincing evidence" refers to evidence sufficient to produce, in the mind of the factfinder, an abiding conviction that the assertion's truth is highly probable.
7.13.3. Could self-interested testimony be clear and convincing?
If an asserting party proffers testimony by a witness who has an interest (e.g., testimony by the asserting party's own people), thenclear and convincing evidence must include (at a minimum) reasonable corroboration of such testimony.
Comment
This follows the Supreme Court's remarks about the need for corroboration in its 1892 Barbed Wire Patent opinion: If a witness might have an agenda to advance, or an axe to grind, or a score to settle, then it'd be good to have more than just that witness's testimony.
7.14. Clearly Agreed Definition
7.14.1. What does it take for something to be "clearly agreed"?
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:
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 6.1.7.8.
7.14.2. What if a party claims that the term means something less?
Any claim that this Clause was waived (so that a different standard is to govern) is itself to be governed by Delaware law.
Comment
See the discussion of this choice of law at 6.1.7.8.
When this Clause is included in the Contract, the parties will follow it whenever a party (the "obligated party") is required to use "commercially-reasonable efforts" (with or without a hyphen) to achieve a stated goal.
Comment
Motivation: 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 Clause 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.
7.15.2.Prudent efforts are required
The obligated party is to make efforts that prudent people — experienced in the relevant area of business — would generally regard as constituting reasonable efforts for the circumstances in question.
Comment
We follow IBM's lead in defining commercially-reasonable efforts in the way that it did in one of its state-government IT contracts: That contract 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).
7.15.3. Certain categories of effort are not required
For emphasis: When the Contract requires a party to use commercially-reasonable efforts, it does not mean that the party must do any of the following things:
make any unreasonable effort;
harm the party's own lawful interests in any non-trivial way;
make every possible reasonable effort; nor
actually succeed in achieving the stated objective.
Subdivision a is not intended as an exhaustive list.
Comment
A. Motivation: This section inserts some roadblocks against aggressive arguments by litigation counsel.
B. Subdivision a.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).
C. Subdivision a.3 seeks to "write around" a seeming suggestion by Delaware's supreme court, in Williams Cos., 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).
The Williams Cos. court reached its conclusion even though the contract elsewhere had used the term reasonable best efforts; the court did not 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).
7.16. Consider Definition
7.16.1. Applicability of this Clause
When agreed to, this Clause will govern any case where the Contract calls for a party P to "consider" doing something ("Thing‑X") unless the Contract clearly says otherwise for particular cases.
Comment
This definition supports various Clauses 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!).
7.16.2. How much leeway will P have?
The party P is not obligated to do Thing‑X.
P gets to decide — in its sole discretion — whether, when, where, and how to do Thing‑X.
7.16.3. Must P do any particular investigation?
The party P's consideration of the matter:
is not required to rise to any particular level nor otherwise meet any particular standard; and
will be solely for P's own benefit, not for the benefit of any other party.
7.17. Contract-Related Claim Definition
The term "Contract-Related Claim" refers to any claim, obligation, liability, or cause of action — each, a "Claim" — arising out of or relating to one or more of the following:
the Contract;
the negotiation, execution, performance, or breach of the Contract;
any representation or warranty made in, in connection with, or as an inducement to, the Contract; and/or
any transaction or relationship resulting from the Contract. This Clause is a purely convenience definition; it's used, for example, in Clause 8.28 (non-recourse against party employees).
In case of doubt: The term Contract-Related Claim encompasses all Claims whether, for example —
arising in contract or in tort;
arising in law or in equity; and/or
created or granted by a constitution, statute, regulation, order precedent, or other governmentally-enforceable policy.
This Clause will apply in any situation where a party is required to provide corroborating evidence for an assertion.
The question whether the party has provided sufficient corroboration is to be governed by (what courts refer to as) a "rule of reason," with each case being decided on its own facts. This specific language is adapted from a federal-court case, which in turn is based on Supreme Court precedent, discussed below. See TransWeb v. 3M Innov. Prop., 812 F.3d 1295, 1301 (Fed. Cir. 2016), citingWashburn & Moen Mfg. Co. v. Beat ‘Em All Barbed-Wire Co., 143 U.S. 275, 284 (1892) (known as The Barbed Wire Patent case).
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).
7.18.1.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).
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. In that case:
an accused patent infringer claimed that someone else was actually the first inventor of the patented barbed wire;
but the accused infringer relied solely on oral testimony to support the claim of prior invention.
The Court was not persuaded that the uncorroborated testimony rose to the level needed to invalidate the patent in suit:
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.
In modern terms, such claims must be established by "clear and convincing evidence" — see Clause 7.13 — 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).
7.18.1.4. 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.
7.19. Days Definition
7.19.1. Definition: What counts as a "day"?
The term day refers to a calendar day, as opposed to a business day.
A period of X days: (i) begins on the specified date, and (ii) ends at exactly 12 midnight, in the relevant time zone, at the end of the day on the date X-1 days later.
Example: If a five-day period begins on January 1, then that period ends at exactly 12 midnight at the end of January 5 (not January 6).
Comment
A. A period of 30 business days would be around six weeks, not one month.
B. Pro tip: When drafting, consider saying, e.g., "three months" instead of "90 days."
C. Concerning a time period "after" or "from" a stated date, see 7.3; see also Clause 7.49 concerning time zones.
D. Note the use of an illustrative example, as discussed at 7.27.
7.20. Deadline Definition
7.20.1. What time does a deadline expire?
If the Contract 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.
Clause 7.49 (time of day) is incorporated by reference.
Comment
This definition simply provides a benchmark reference point; drafters can vary it as desired.
7.21. Deliverable Definition
7.22. Deliverable Definition
The term "deliverable" refers to any of the following that is to be delivered to a party (the "Customer") under the Contract:
any tangible goods, and
any intangible information, no matter how transmitted or stored.
For purposes of this Clause, 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 Contract.
7.22.1. Comment
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 Walmart (2020), 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).
7.23. Discretion Definition
Contracts often use the terms discretion, sole discretion, unfettered discretion, and reasonable discretion; this Clause seeks to provide clear meanings for the underlying word discretion — while recognizing that courts might impose their own meanings, as discussed below.
"Discretion," without more, means reasonable discretion while acting in good faith.
"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).
7.23.0.1. Comment
A. Subdivision a: In some U.S. jurisdictions, a party's discretion might be constrained by an implied obligation of reasonableness, or perhaps of good faith. See, e.g., Han (7th Cir. 2014). 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 8.5.3 and 8.4.14
B. But in Maverick Nat. Resources (2024), a Texas appellate court held that when a sale-and-purchase letter agreement gave a buyer the "sole discretion" to close a purchase transction (after doing due diligence about the purchase), that unfettered walk-away right rendered the agreement contract illusory and unenforceable, absent 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).
C. Subdivision b 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: A court might not go along with subdivision b; see the discussion at 7.23.1.1.
7.23.1.1. Maybe not completely "unfettered" discretion?
Even if a contract uses terms such as sole and unfettered discretion, a court might still second-guess the actor if the circumstances seem egregious. Example: 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).
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.
Counterexample: In a 2019 decision, the Texas supreme court declined to read a reasonableness requirement into an assignment-consent provision. (This is discussed in more detail at 8.5.4.) Barrow-Shaver Resources Co. v. Carrizo Oil & Gas, Inc., 590 S.W.3d 471, 476 (Tex. 2019) (affirming court of appeals).
7.23.1.2. 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 …."
7.24. Effective Date Definition
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 is likely to state that the agreement protects information disclosed for a stated number of months after that effective date.)
The "Effective Date" (whether or not the term is capitalized) of the Contract is the date that the Contract is signed by the last party necessary to make the Contract a legally-binding contract unless the Contract clearly states otherwise.
If a party's signature block in the Contract includes a handwritten date signed, then that party is to be (rebuttably) presumed to have signed the Contract on that date.
Comment
There are various ways that a contract can state an effective date; your author prefers the approach of this Clause because it's "cheap insurance" against problems that can arise with other commonly-used styles, as discussed below.
This Clause affirmatively states that the effective date of the Contract is the last date signed and not a specified date nor "as of" a specific date.
Many drafters like to include a specific effective date anyway, or to include a blank to be filled in; it's normally not worth changing if someone else has drafted it this way.
Still, the last-date-signed approach has its advantages, as discussed below:
[ x ] This Agreement is effective the last date written on the signature page.
[ x ] This 'Agreement' is made, effective the last date signed as written below, between ….
[ ] This Agreement is made December 31, 20XX, between ….
[ ] This Agreement is dated December 31, 20XX, between ….
[ ] This Agreement is dated ………………… [a blank underscored line] between ….
Any of the latter three approaches can be problematic because:
a specifically-stated date might turn out to be inaccurate, depending on when the parties actually sign the contract; and
a blank space might be overlooked and not filled in.
7.24.1.2. Caution: Backdating can be dangerous
Signers should never backdate a contract for deceptive purposes — and should not ever backdate the date signed — because people have gone to prison for doing so, as discussed at 10.1.2.
7.25. Encouraged Definition
As (hopefully) helpful prompts, some of the Clauses 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.
Contents:
This Clause will apply whenever the Contract states that one or more parties is "encouraged" to take a particular action.
The statement means that, in principle, the action is likely to be a good idea, but there is nevertheless no obligation for any such party to take the action.
Similarly, a statement in the Contract that a party is encouraged not to take an action means that the the Contract does not preclude the party from taking the action, even if the action might not necessarily be the best course in a given situation.
Comment
See also the definition of should, which has an essentially-identical meaning.
7.26. Ending Time Definition
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? Example: In Smith Bros. (1997), 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 Bradscot (1999), 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
So: This Clause sets out a default rule, which the parties are of course free to vary.
The parties will follow this Clause if the Contract states that a time period, a right, an obligation, etc., is to end or expire on a specified day.
Unless otherwise stated, that end or expiration will be at exactly 12:00:00 midnight at the end of the specified date.
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.
Comment
A. 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.
B. Time zones are also addressed at Clause 7.49 (time of day definition).
When examples are used in the Contract or related documents, they are for purposes of illustration, not of limitation, unless the context makes it unmistakably clear to the contrary.
A longer phrase — such as "by way of example and not limitation" — is not meant to imply that "for example" and similar shorter phrases have a different meaning, for example under the interpretation principle of expressio unius est exclusio alterius, "to include one thing is to exclude others." 13.12
No party is to ask a court or arbitrator to use the contract-interpretation principle of ejusdem generis to limit the meaning illustrated by examples. 7.32
See 7.32 for discussion of ejusdem generis and of expressio unius est exclusio alterius.
7.27.2.1. Language notes
C. For discussion of the benefits of including illustrative examples to help reader comprehension, see 30.10.2.
7.28. Good Faith Definition
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 § 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."
7.28.1.1. Would the law impose a general duty of good faith?
It depends:
A. 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 (2002) by the Supreme Court of Texas, 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."
B. 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 in Glaxo Group (2021):
… 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. …28
Comment
7.28.1.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.
[ x ] 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.
7.28.1.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.
Comment
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.]
7.29. Government Authority Definition
Contents:
The terms "government authority" and "governmental authority" refer to any individual or group, anywhere in the world, that exercises governmental- or regulatory power.
The terms should normally be read as including, as applicable and without limitation:
any agency; authority; board; bureau; commission; court; department; executive; executive body; judicial body; legislative body; or quasi-governmental authority,
at any level, for example, state, federal or local.
The governmental- and regulatory power referred to here is intended to include, without limitation, administrative; executive; judicial; legislative; policy; regulatory; and/or taxing power.
Comment
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.
7.30. Gross Negligence Definition
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 Clause 3.9 often exclude indemnity coverage for gross negligence. So it'd be useful to have a reference 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.
A. Subdivision a: This Definition 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 7.30.1.1; see the other notes below for standards used in some other jurisdictions.
B. Subdivision b: See the discussion in the commentary to Clause 7.13 (clear and convincing evidence definition).
This Definition is based on New York law in relation to limitations of liability, because tht 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.
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). The definition is used in § 41.003 of the Code, which conditions any award of punitive damages on a showing, by clear and convincing evidence, of fraud, malice, or gross negligence
Tangential: In 2024 the Texas supreme court held that the statutory term "willful and wanton negligence" meant at least gross negligence. See Marsillo, supra, 683 S.W.3d at 391-92
7.30.1.3. California law: Too vague?
In California: More vaguely, 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 inIn re Facebook, Inc., 402 F. Supp. 3d 767, 800 (N.D. Cal. 2019) (denying motion to dismiss claim that "plausibly allege[d] gross negligence").
7.30.1.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).
7.31. Hold Harmless Definition
Contents:
The term "Hold harmless" (whether or not capitalized) has the same meaning as indemnify (defined at Clause 3.9).
Comment
This definition reflects what seems to be a consensus by legal-writing experts: 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
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." Garner addresses this problem in his Green Bag piece, at 22.
7.32. Including Definition
Contents:
"Including" (whether or not capitalized) means "including, but not limited to" unless clearly stated otherwise.
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.
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.
Comment
A. This Definition seeks to "write around" 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).
B. 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 Samuel Alito pointed out in Cooper Distribution (1995), 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) (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)
C. Subdivision b is kinda meta ….
D. Subdivision c is an argument roadblock, intended to forestall an aggressive party from asserting the principle known as expressio unius est exclusio alterius, "to express one thing is to exclude others."
E. For additional notes in this general area, see 30.9 (ambiguity).
7.33.1. What does it mean to say that a breach is "material"?
If the Contract states (in effect) that a certain type of breach will be material, then that statement is to be considered conclusive.
Comment
A. 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 2016 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."
7.33.2. What if the Contract doesn't say which breaches are "material"?
Any non-agreed determination whether a breach of the Contract was (or would be) "material" is to take into account the factors listed in the Restatement (Second) of Contracts § 241 (1981), or its successor, if any: (i) considering the Contract as a whole; and (ii) with no single factor necessarily being decisive.
Comment
A. 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.
B. Caution: This language 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.
7.33.3. Could multiple small breaches add up to "material breach"?
Yes: In appropriate circumstances, a history of multiple non-material breaches — related or not, cured or not — could collectively constitute a material breach of the Contract when considering the Contract as a whole.
Comment
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.
7.33.4.1. Why it might matter: Suspension of other party's obligation
Perhaps the most-salient point about a material breach of contract is that in American jurisprudence, 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).
Caution: The other party might not necessarily be able to terminate the contract — as opposed to suspending its own performance — because of the first party's material breach; that could depend on all the surrounding circumstances.
For further discussion, see the commentary at 5.7.1.1, concerning termination for material breach.
7.33.4.2. Termination for material breach might be "use it or lose it"
Example: 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: Party A might not be able to use the "but they breached first!" argument — i.e., that Party B's "first material breach" justified Party A's own own material breach — if Party A waived that possibility. 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).
7.33.4.3. Caution: Don't do an own-goal termination for "material breach"
Before terminating a contract for material breach (see Clause 5.7), the terminating party should take pains to be sure that the breach truly is material. Otherwise, the terminating party risks an "own goal" where the termination is itself a material breach. (See the real-life examples discussed at 5.2.5.)
7.33.4.4. Related issue: "Material" definition
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":
Regarding the "dealbreaker" meaning, the word dealbreaker, meaning "a factor or issue which, if unresolved, would cause one party to withdraw from a deal," expresses what’s at stake better than, say, major or substantial. You wouldn’t even have to use it as a defined term.
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.
7.33.4.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 a California appellate decision, where the court affirmed a take-nothing judgment in favor of Southwest Airlines, on grounds that jury found SwiftAir did not 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).
Unless the Contract clearly states otherwise, the term "month" refers to calendar months.
Comment
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.
7.34.2. Special cases
Defining by example: Unless the Contract specifies otherwise, a stated number of months after a particular date will end as follows:
One month after January 15 is February 15.
One month after January 29, 30, or 31 is February 28 (or February 29 in a leap year).
One month after February 28 (or February 29 in a leap year) is March 31.
One month after April 30 is May 31.
One month after May 30 is June 30; two months after May 30 is July 30.
Comment
Note the use of examples, for reasons discussed at 7.27.
7.35. Party Definition
<>
This Definition is provided for clarity; it ties in with 8.66 (third party beneficiaries).
Contents:
In case of doubt: The term "party" (whether or not capitalized) refers only to those individuals and organizations that are signatory parties to the Contract unless the context clearly requires otherwise.
7.36. People Definition
Contents:
<>
This is a convenience definition, to avoid having to list (possibly repeatedly) all of the enumerated categories below.
Contents:
For reader convenience, in respect to any individual or organization ("person"), that person's "people" (whether or not capitalized) refers to any individual who, at the time in question, falls into one or more of the following categories:
an employee of the person;
an officer or director of the person, if the person is a corporation;
a holder of a comparable position, if the person is an organization of another type, such as a limited liability company; and/or
any other individuals expressly specified in the Contract, if any.
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.
(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.
7.38. Possession, Custody, or Control Definition
The term "possession, custody, or control" has the meaning used in federal-court litigation in the United States.
Comment
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., Tess Blair and Tara S. Lawler, Possession, Custody or Control: A Perennial Question Gets More Complicated (MorganLewis.com 2018).
Important: 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.
C. For a list of privacy laws, see 7.39.1.2. Caution: The list could already be out of date; check with experienced counsel.
"Privacy Law" refers 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.
7.39.1.1. 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:
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;
take reasonable security measures to protect the information;
alert the individual in cases of security breach (actual or, sometimes, potential)
report security breaches to government authorities;
purge the information upon request (the "right to be forgotten")
7.39.1.2. Appendix: Privacy laws
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.
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").
7.40. Protected Group Definition
If this Definition is adopted in the Contract, it concerns the "Protected Group" of an individual and/or organization clearly specified in the Contract as being the beneficiary of:
a defense and/or indemnity obligation; and/or
a limitation of liability;
each such individual and organization is referred to as a "protected party."
For each protected party, the term Protected Group refers to the following individuals and organizations:
any other individuals or organizations specified in the Contract; and
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.
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.
A. This is a convenience definition for use in, for example, various defense and indemnity clauses and limitations of liability.
B. Subdivision c: Note the use of an illustrative example here, to help "serve the reader"; see 7.27 for additional discussion of the benefits of examples.
7.41. Reasonable Definition
Many contracts defer detailed discussion of performance standards by saying, in effect, that Party 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.
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.
Upon request by any involved party: Any disagreement whether prospective action would be reasonable is to be addressed in accordance with Clause 6.5 (internal escalation) and, if that does not resolve the disagreement, with Clause 6.4 (escalation to neutral advisor).
Comment
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.
7.41.2. Reasonable Efforts Definition
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.
At either party's request, the parties will escalate, as stated at Clause 6.4, any persistent disagreement about what future efforts would qualify as "reasonable" in the circumstances.
Comment
A. 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 7.7 (best efforts); 7.15 (commercially-reasonable efforts); and 7.28 (good faith).
B. 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.
7.42. 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 3.3.4; 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.
the actor: • consciously disregards • a substantial and unjustifiable risk • that harm to another will result • from the actor's conduct; and
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.
Comment
A. 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).
B. 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).
3.12 (limitations of liability general provisions).
7.43. Record (as noun) Definition
Some contracts require one party to keep records, and typically allow another party to audit the records (concerning which, see generally 2.3). this Definition tries to make it clear that the term "records" encompasses practically any form of recorded information.
Records Definition (noun): Harbor Approach
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.
Comment
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).
7.44. Relating-to Definition
<>
In case of doubt: The term "arising out of or relating to this Agreement" is to be understood as, "arising out of or otherwise relating to this Agreement."
7.44.0.1. Comment
7.45. Responsible Definition
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 7.41.2) or even "commercially-reasonable efforts" (see 7.15); but
B is unwilling to make the even-stronger commitment to use "best efforts" (see 7.7).
For those situations, this Definition gives drafters a way to express that concept verbally (i.e., in words) as responsible efforts.
Contents:
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.
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.
Comment
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).
7.46. Satisfactory Definition
In a 1983 decision, federal judge Richard Posner 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 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 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).
Contents:
The meaning of the term satisfactory, when used in the context such as satisfactory to Party A, depends on the context.
If the Contract calls for A's satisfaction as to matters generally regarded as reasonably objective in nature — such as, for example, commercial value or quality — then:
the standard is what would be satisfactory to a reasonable person in the circumstances; and
A must not unreasonably assert that A is not satisfied.
If the Contract 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.
If the Contract calls for A's satisfaction in A's sole discretion or similar language, then the standard applicable to discretion will apply (see 7.23).
When this Clause is agreed to, it applies for the avoidance of doubt unless the context clearly and unmistakably requires otherwise.
Terms such as "Party A shall take Action X" mean that Party A is required to take Action X.
Likewise, terms such as "Party B shall not take Action Z" means that Party B is prohibited from taking Action Z.
Comment
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 7.47.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).
7.47.2. Additional notes (not part of this Clause)
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).
7.48. Should Definition
Rule text
As (hopefully) helpful prompts, some of the Clauses state that a party "should" take an action, or often, "should consider" taking an action. Such statements
In a Clause, 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.
Similarly, a statement in a Clause that a party "should not" take an action means that the Clause does not preclude a party from taking the action, even if the action might not necessarily be the best course in a given situation.
7.49. Time of Day Definition
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).
A specified time of day refers to the exact time. Hypothetical example:30.10.2 If a stated deadline for submitting a bid is 5 p.m., and a party submits a bid at one-half second after exactly 5:00.00 p.m., then that bid is late. 7.26
7.49.1.2. What time zone(s) would be used?
A time of day refers to the following unless clearly agreed otherwise in writing:
to local time if only one time zone is relevant,
otherwise (in the interest of standardization), 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.
7.49.1.3. Can you provide an illustrative example of time zones?
As a hypothetical example:
Alice, in Honolulu, and Benjiro, in Tokyo, enter into a contract.
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.
In that situation, the deadline expires at 12 midnight at the end of the day on January 1 in Hawai'i, when it is early evening on January 2 in Tokyo. For additional examples, see the comments at 7.26.
Comment
Alice and Benjiro: These hypothetical names are adapted from the tech world's "Alice and Bob."
7.50. Timely Definition
Some Clauses refer to "timely" action; that's a useful term but vague, so let's give the reader an idea what we mean.
7.50.1. Clause text
When this Clause is agreed to in writing:
7.50.1.1. What does timely mean in the Contract?
An action relating to the Contract is timely (or "seasonable") if the action is taken:
at or within the specific time agreed, if any; or
if no specific time is agreed, then at or within a reasonable time.
Comment
Timely definition: 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.)
7.50.1.2. Would untimely action be a material breach?
A party's failure to timely perform an action when required by the Contract would be a breach of the Contract, but not a material breach (see the definition in Clause 7.33), unless clearly agreed otherwise.
Defining by example: Consider a corporation, having a board of directors whose members are elected by holders of voting shares.
For that corporation, 50% of the "Voting Power" of the corporation refers to one or more of the following legally-enforceable rights: (see subdivision 2):
the right to vote at least 50% of the voting shares of each class of shares entitled to vote; and/or
the right to select at least 50% of the members of the board of directors.
The rights referred to in paragraph 2 can arise:
by ownership of shares or comparable interests;
by contract, for example, a voting trust or voting agreement; and/or
by a provision in the articles of incorporation or equivalent document in the relevant jurisdiction, for example a certificate of formation.
This Agreement will apply in similar fashion to organizations of any other type (including without limitation not-for-profit organizations).
Comment
Voting classes: Shares of corporations are often divided into "classes" with different classes perhaps having different voting rights; see also Clause 8.8 (board of directors).
As a hypothetical example, let's assume that:
Alpha 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
Alpha 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 Alpha 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.)
Comment
Ownership of voting shares (or of comparable interests in non-corporate organizations) is perhaps the most common way of holding voting power.
7.52. Will (as "must") Definition
Contents:
The term "will" has the same meaning as must unless the context clearly and unmistakably requires otherwise.
A hypothetical example: "Party A will take Action X" mean that Party A must take Action X.
Comment
In many cases, your author prefers the term will (or, is to), and not shall, when writing contract obligations for business reasons. That's especially true when I'm representing a supplier of goods and services that's dealing with a customer or potential customer.
Why? Because the terms will and is to seem to have a more-collaborative and less-imperious tone than shall. That can provide just a smidgen of help in establishing a cooperative attitude among the parties; that can help foster a successful long-term relationship or even just a one-shot transaction.
Moreover: From a sales-psychology perspective, in a contract drafted by a supplier, the term will seems softer and more deferential — it pays the customer the respect of implicitly acknowledging that the customer can walk away before signature.
If a supplier's contract form adopts an imperious tone, it might send the wrong signal to a prospective customer about whether the supplier, will be "a good business partner." A softer, more-deferential approach would be to say instead, "the Customer will do" this or that, instead of "the Customer must do" this or that.
But: Sometimes, "must" might be better; if a drafter anticipates trouble from a counterparty, then the term must might be preferable.
7.53. Willful Definition
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 Clause 3.9 often exclude indemnity coverage for the same.
When the Contract uses the term "willful" (or its variant spelling wilful) concerning action or conduct — for example, a willful act or willful action or willful conduct or willful misconduct or willful neglect — it refers to action or conduct ("Action") where both of the following are true:
the Action would be tortious, and/or criminal, if it were to be engaged in outside the context of a contract; and
the Action is undertaken either (i) intentionally and with knowledge of the Action's tortious and/or criminal nature, or (ii) recklessly (see Clause 7.42).
7.53.2. Source note: New York law
This Definition draws on:
New York law — in connection with a carve-out to a limitation of liability, that state's highest court looked to the doctrine of ejusdem generis in holding that, in context, 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). and
various definitions in contracts that your author has reviewed over the years.
For some other definitions used by courts and legislatures, see the appendix below.
The better practice, of course, is not to rely on guesses about how a court — possibly an unforeseesable one — might view the meaning of a term, as summarized in the acronym W.I.D.D.:When In Doubt, Define!
7.53.3. Appendix: Other 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. __, 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").
8.1.1.1. Which disputes must be arbitrated instead of taken to court?
Except as otherwise stated in this Clause, binding arbitration is to be used to resolve any dispute that relates in any way to the Contract. For this purpose, the term "the Arbitration" refers to an arbitration under the Contract.
Comment
Note the intentional use of passive voice in the phrase, "binding arbitration is to be used" — that's to accommodate the possibility that non-parties to the Contract might be required to arbitrate disputes relating to the Contract. (For now, that's beyond the scope of this book.)
8.1.1.2. Does it matter what the basis for the dispute is?
Arbitration is required no matter what the underlying legal- and/or equitable theories might be — for example, 7.27 for claims based in contract, tort, unjust enrichment, fraud, fraudulent inducement to enter into the Contract, etc.
Comment
Intentionally-broad scope of arbitration requirement: Case law is clear that parties can agree to mandatory arbitration of claims of all sorts, including fraud and other torts. See, e.g., Rosenthal v. Great Western Fin. Sec. Corp., 14 Cal. 4th 394, 58 Cal. Rptr. 2d 875, 926 P.2d 1061 (1996).
8.1.1.3. Does that apply to statute-based and constitutional claims as well?
For emphasis: Arbitration is required (without limitation) for claims arising under a statute or constitutional provision.
Comment
Arbitration of statutory- and constitutional claims: In 2009, the Supreme Court held that a particular collective bargining agreement ("CBA") was worded to "clearly and unmistakably" require arbitration of statutory age-discrimination claims. See 14 Penn Plaza LLC v. Pyett, 556 U.S. 249 (2009).
• Counterexample: The Fifth Circuit reached the opposite result under another CBA whose arbitration provision was worded differently. See Ibarra v. United Parcel Service, 695 F.3d 354, 356 (5th Cir. 2012).
8.1.1.4. Would even smaller claims have to be arbitrated?
Any party may decide to litigate a small-amount claim that would otherwise have to be arbitrated under the Contract — but only in a "small-claims court," by whatever term used in the relevant law, as follows:
If the Contract includes a forum-selection 3.6 provision, then the party wanting to go to small-claims court must comply with that provision.
No party may take a claim in small-claims court if that party already either (i) initiated arbitration for the claim, or (ii) filed an answer on the merits to another party's demand for arbitration of the claim.
The arbitrator has no power to determine whether a party has validly elected small-claim litigation under this Clause — that will be strictly for a court to decide, even if the parties have otherwise delegated authority to the arbitrator, for example by agreeing to Option 8.1.4.
Comment
Small claims might be better handled in small-claims court: 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.
• 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.
• Small-claims courts typically operate more informally than courts of "general jurisdiction," for example, by allowing a company to be represented by a non-lawyer. They're thought to be less-costly to sue in than "regular" courts or an arbitration proceeding.
Comment
Waiver of small-claims option: Suppose a party (the "claimant") demands arbitration: It'd be unfair for the claimant to be able to do an Emily Litella and say, "Never mind" and make the other party (the "respondent") shift gears to working on a small-claims lawsuit instead, likely with duplicated effort. The same should be true if the respondent filed a substantive answer concerning the merits of the claim.
Comment
No arbitrator power over small-claims election: When a party elects to go to small-claims court instead of arbitration, the other party might oppose the election and try to keep the case in arbitration. The arbitrator shouldn't be the one to determine whether the small-claims election is valid — that's because the arbitrator has a clear conflict of interest: the arbitrator will get paid more if the case stays in arbitration. Hence, this Clause says that the arbitrator has no power to make such a determination; the "has no power" language has in mind that, 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 section 15 concerning an enhanced right of appeal.)
8.1.1.5. Notice of arbitration and its required language
If a party ("P") starts arbitration, or any related legal proceedings, against another party ("OP"), then P must make sure that OP is immediately given a reasonably-detailed notice of the same, which must be written (i) in English; and/or (ii) in another language that can be read by most of OP's senior management and other relevant employees.
Comment
Arbitration-related notices in English: This Clause requires notices of arbitration-related proceedings to be given in English (or other language understood by the notified party). This 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:
The American retailer missed (what an American court found to be) a crucial deadline in a payment-dispute arbitration with a Chinese manufacturer.
The missed deadline occurred because the 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.
An American trial court court, however, 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), affirmingNo. 14-cv-03118 (D. Colo. May 29, 2015).
8.1.1.6. What governing law and rules will apply in U.S. cases?
Procedurally, for cases "seated" 8.2.22 in the U.S., the Arbitration will be governed by:
Other courts, though, have gone the other way. See Baker Hughes Saudi Arabia Co., Ltd. v. Dynamic Indus., Inc., No. 23-30827, part III.A.1, slip op. at 12-16 (5th Cir. Jan. 27, 2025) (reversing denial of motion to compel arbitration): "[t]o summarize, the text of [the arbitration agreement] designates only a set of rules and not a particular arbitral forum." Id., slip op at 16, text accompaying n.6. See also Ferrini v. Cambece, No. 2:12-cv-01954 (E.D. Cal. June 3, 2013) (citing cases); Nachmani v. by Design, LLC, 901 N.Y.S.2d 838, 74 A.D.3d 478 (N.Y. App. Div. 2010) (agreement to AAA rules was choice of rules, not of administrator).
8.1.1.9. Who is to administer the arbitration?
The Arbitration is to be administered 8.2.18 by the following:
the American Arbitration Association ("AAA"), if the case is seated 8.2.22 in any geographic location that is subject to U.S. law; and
the International Centre for Dispute Resolution ("ICDR," the international division of the AAA) otherwise.
8.1.1.10. Who would be the backup administrator?
The arbitrator is to serve as the "backup" administrator if for any reason the agreed administrator does not do so; when so serving, the arbitrator is to proceed:
as stated in the arbitration rules; and
for situations not covered by those rules, in accordance with the arbitrator's sound discretion.
Comment
A court might refuse to compel arbitration if the designated administrator declined to accept the dispute. See the previous foonote; Hernandez v. MicroBilt Corp., 88 F.4th 215 (3d Cir. 2023) (affirming denial of motion to compel arbitration).
Comment
Arbitrator's administrative discretion: The concept of "sound discretion" in administrative matters draws on extensive case law about the discretion of trial judges to decide things such as, e.g., the admissibiity of evidence, with their decisions being reviewable under an abuse-of-discretion standard.
8.1.1.11. How many arbitrators\, and how selected?
The Arbitration is to be conducted before a panel — appointed in accordance with the agreed arbitration rules, 8.2.20 or as a backup method: as provided by law 8.2.8 — consisting of: [ x ] a single, neutral arbitrator. 8.2.23 [ ] three arbitrators. 8.2.24
8.1.1.12. What language is to be used in the arbitration proceedings?
All concerned are to use the English language for all proceedings, notices, and arbitrator decisions in arbitration, unless everyone involved agrees otherwise.
Comment
Arbitration language: The arbitral language is a useful thing to nail down for transnational dealings, because translators and interpreters cost money and would be one more thing that had to be arranged. • Pro tip: Consider the country where an arbitration award might be enforced, because under Article IV.2 of the 1958 New York Convention, a sworn translation might be required, resulting in extra expense and delay.
8.1.1.13. JURY WAIVER
For emphasis: Each party in the Arbitration WAIVES any right that the party might have to a jury trial for any matter being addressed in the Arbitration.
Comment
Here, the word "WAIVED" is in bold-faced all-caps for conspicuousness (see 11.11) as "cheap insurance" in case there's a conspicuousness requirement for jury waivers that would apply to arbitration agreements. (As discussed at 8.2.30, it's an open question whether such state-law conspicuousness requirements could be preempted by the Federal Arbitration Agreement.)
8.1.1.14. Is the arbitrator's power limited?
Unless the parties clearly agree otherwise, the arbitrator has no power to do any of the following:
to grant relief clearly inconsistent with the Contract or with applicable non-arbitration law; nor
to 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
to act as amiable compositeur or ex aequo et bono. 8.2.14
Comment
Why say the arbitrator has "no power"? This "no power" language has in mind that, 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 8.2.35 concerning an enhanced right of appeal.)
Comment
Applying bench-trial standards: In U.S. litigation, a trial court's judgment after a bench trial can generally be reversed on appeal (or perhaps vacated and remanded for reconsideration) if the judgment is based: (i) on findings of fact that are clearly erroneous, and/or (ii) on errors of law; certain other trial-court actions can be set aside for abuse of discretion. See generally, e.g., Weinberger, Simon, & Ettari (AmericanBar.org 2021).
8.1.1.15. What are some examples of unauthorized arbitrator actions?
For emphasis: The arbitrator has no power to render an award that fails to give effect to a 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
that sets a deadline — or shortens a statutory deadline, known as a "limitation period" — for a party to bring a claim in court or elsewhere.
Comment
Why mention statutes of limitation? The potential concern here is that, absent specific language preserving the statute of limitations, an arbitrator might be able to ignore a claim deadline under such a statute — and there might be very little the opposing party could do about it in court by way of appeal. See Kramer (2016) and the commentary at 8.2.35 concerning an enhanced right of appeal.
8.1.1.16. Where could an arbitration award be enforced?
If a party prevails in the Arbitration, then that party may go to court to "confirm" the arbitrator's award, and to have the resulting court judgment (or order) judicially enforced against any relevant other party in any court that has jurisdiction over the other party. 8.2.15
8.1.1.17. What grounds would a party have to appeal an arbitration award?
Any party can challenge an arbitration award as provided in California's arbitration law; 8.2.35 this will be true:
even if the Contract specifies a different choice of law for the Contract generally and/or for one or more other issues; 3.7.19 and
even if the Federal Arbitration Act would otherwise limit such challenges.
8.1.1.18. What if a court holds that expansive appeal rights are not available?
If the right of enhanced appeal of this Clause is finally held to be invalid or otherwise unenforceable, by a court or other body of competent jurisdiction, with no further possibility of appeal, then Option 8.1.6 will govern.
8.1.1.19. Who will pay the expenses of a challenge to arbitration?
If a party does not timely comply with an arbitration award under the Contract or unsuccessfully challenges in court: (i) the award, or (ii) the parties' arbitration agreement; then that party must pay the other party's attorney fees 3.1 incurred as a result, including 7.32 attorney fees for any related appeals.
Comment
Attorney fees for arbitration enforcement: 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, No. B309408 (Cal. App. Feb. 24, 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.)
8.1.1.20. Does this Clause affect the rights to terminate?
The parties' agreement to arbitrate does not limit (but neither does it expand) any right that a party might otherwise have to terminate the Contract and/or a transaction or relationship governed by the Contract.
Comment
Arbitration doesn't preclude termination at will: This seeks to disavow a Fourth-Circuit 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).
8.1.1.21. Does this Clause mean that government action is precluded?
For emphasis: The parties' agreement to arbitrate does not mean that a party may not bring issues to the attention of appropriate federal, state, or local authorities, nor that such authorities would be unable to act in the matter.
Comment
Government action isn't precluded by arbitration: Hat tip: arbitrator Mark Kantor. 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 does not bar EEOC from acting) and Gilmer v. Interstate/Johnson Lane Corp., 500 U.S. 20 (1991) (arbitration agreement does not bar filing a charge with the EEOC).
8.1.1.22. Survival: Arbitration of pre-termination claims
If the Contract expires or is otherwise terminated, then the parties will continue to follow this Clause for disputes (if any) that accrued before the termination or expiration became effective.
Comment
Survival of arbitration agreement: 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. 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).
8.1.2. Arbitration Clause (drop-in version)
(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 Contract. (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.
Comment
Short-form arbitration agreement: This shorter "wall of words" clause would be harder to read but easier to copy and paste into a draft contract; for commentary, see the counterpart sections of the long-form Clause 8.1.
The parties DO NOT AGREE to arbitrate any case in which a party does, or attempts to do, any of the following:
consolidate any claim with claim(s) of any other party; 8.2.32
purport to act as a representative of other claimants; and/or
purport to act as a private attorney general, whether under a statute allowing such action, sometimes referred to as "PAGA claims," or otherwise. 8.2.44
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. 8.2.33
The parties' agreement to this Option is "material" — without this Option, one or both parties would not have agreed to arbitration at all.
8.1.4. Option: Delegation of (Most) Arbitrability Decisions
Except as clearly provided otherwise in the Contract, the arbitrator is to decide all disputes about arbitrability, including without limitation the following:
whether the parties' agreement to arbitrate was duly entered into but is nevertheless unenforceable;
whether a particular dispute comes within the scope of the arbitration agreement; and
whether the arbitration agreement conflicts with a party's non-waivable legal rights. 8.2.26
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.
But: A court of competent jurisdiction has the sole power to decide any dispute about:
whether the parties agreed to arbitrate at all; and/or
whether this section is a valid delegation of authority to the arbitrator. 8.2.29
8.1.5. Option: Nondelegation of Arbitrability Authority
Any disagreement whether or not a particular dispute is to be arbitrated is to be decided by a court of competent jurisdiction and not by the arbitral tribunal, even if the applicable arbitration rules state otherwise. 8.2.26
8.1.6. Option: Jettison Of Arbitration
This Option will be triggered if both of the following are true:
the parties' agreement to arbitrate specifies one or more provisions as "jettison triggers" (or words to that effect);
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
the parties do not agree otherwise — for example, by agreeing to a settlement of their dispute.
Either party ("P") may jettison, that is, rescind, the parties' arbitration agreement by giving the other party ("OP") clear notice to that effect no later thanfive business days after the final holding described above.
If P does timely jettison arbitration as provided in this Option, then:
Whatever actions the arbitrator previously took, in the way of a partial- or complete "final award," will be automatically "vacated," that is, set aside and of no effect; and
The status of any interim actions of the arbitrator is to be determined by the court if not otherwise agreed.
If P does jettison arbitration under this Option, then either P or OP 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:
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
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. 3.11
Comment
Jettison of arbitration: This Option is motivated by a Tennessee supreme court holding that judicially rescinded a contract's arbitration provision for mutual mistake: The 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 the arbitration agreement had to be dumped. See Pugh's Lawn Landscape Co. v. Jaycon Dev. Corp., 320 S.W.3d 252 (Tenn. 2010) (vacating judgment confirming arbitrator's award).
8.1.7. 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) will be deemed automatically severed 24.2 from the agreement to arbitrate.
Comment
Severability of arbitration provisions has been an issue in several cases. See 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 from965 F.3d 71, 82 (1st Cir. 2020); Ramirez v. Charter Comms., Inc., 16 Cal. 5th 478 (2024), on remand, No. B309408 (Cal. App. Feb. 24, 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 (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).
8.1.8. Option: No Punitive Damages in Arbitration
(a) The arbitrator has no power 8.2.14 to award punitive damages, exemplary damages, multiple (e.g., treble) damages, or similar relief. 8.2.31(b) Neither party is to seek 3.1.9 such damages.
8.1.9. 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. 8.2.31
8.1.10. Option: Limited Punitive Sanctions in Arbitration
(a) The arbitrator has no power 8.2.14 to award punitive sanctions against a party, in respect of an issue (or multiple issues) being arbitrated, in the form of: (i) preclusion of otherwise-admissible evidence; nor (ii) entry of judgment concerning the issue. (b) Neither party is to seek 3.1.9 such sanctions.
Comment
Punitive sanctions: This Option addresses a concern raised by a Minnesota case where which an arbitrator, in effect, (i) struck a respondent's pleadings as a sanction for fabrication of evidence, and (ii) awarded the claimant more than $600 million; the award was upheld by the state'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).
8.2.1. In general, what 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 voluntarilly, 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.
8.2.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.
8.2.3. Modern use of arbitration: 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 8.2.13), 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.
8.2.4. 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 Pennsylvania appeals 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).
8.2.5. Even non-signatory parties might have to arbitrate
[Optional reading for students]
Generally, a party need not arbitrate disputes if it didn't agree to arbitrate; as far back as 1960, 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).
But: A party that didn't sign a contract containing an arbitration provision might have to arbitrate disputes arising under the contract. Example: In its Wagner decision, the Texas supreme court noted:
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: Similarly, family members of a Texas homeowner wanted to sue the builder of the home; the state 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." 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), No. 23-2020 (4th Cir. Oct. 29, 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: 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," an employee of a company, who was "staffed" to Phillips 66 (a customer of the employer), sued Phillips 66 for overtime pay. The employee'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). To similar effect, cf.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), citingRieder v. Woods, 603 S.W.3d 86 (Tex. 2020), where the 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.
Counterexample: A federal district court in New York 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).
8.2.6. Some dispute-resolution procedures aren't "arbitration"
Example: A California appeals 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 context, a Delaware chancery-court judge, on his own motion, 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 must be submitted to a committee of the company's board of directors. See Terrell v. Kiromic Biopharma, Inc., No. 2021-0248, slip op. (Del. Ch. Jan. 20, 2022). The court later granted the company's motion to dismiss on grounds that Terrell had waived his rights to any unexercised options.
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 13.7.
8.2.7. Caution: Arbitrations might not be confidential
A. 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.
B. 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).
C. 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).
D. 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).
8.2.8. How would arbitrators normally be chosen?
A. 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-12.
B. Caution: 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).
8.2.9. Would arbitrator neutrality be a given? (Usually.)
A single arbitrator will usually be required to be independent and impartial, e.g., under the AAA's Commercial Rule R-18.
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-18(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: Consider the famous "Deflategate" case, which centered on legendary (U.S.) National Football League quarterback Tom Brady: In 2016, the Second Circuit 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 (2016).
Counterexample: 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, the district court did indeed sever the appointment provision and directed the parties to meet and confer about an arbitrator.
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).
8.2.10. 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).
Nor does this section authorize the arbitrator to grant preliminary injunctive relief — that would depend on the arbitration rules and any other agreement of the parties.
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 allowed, a court might dismiss an appeal of an arbitrator's preliminary injunction, on grounds that it was not an "award." See, e.g., Kirk v. Ratner, 74 Cal. App. 5th 1052 (Cal. App. 2022) (dismissing appeal from trial court's dismissal of petition to vacate arbitrator's preliminary injunction). might not have jurisdiction to review the injunction.
8.2.11. 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 Clause allows one, limited exception: Under [BROKEN LINK: arb-small], for a limited time, either party may elect to take the dispute to a small-claims court in lieu of arbitrating.)
8.2.12. 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.
(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 8.2.13.)
8.2.13. 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.
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.
8.2.14. Could an arbitrator "run amok" in a decision?
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. See generally Alexander J. Belohlavek, Application of Law in Arbitration, Ex Aequo et Bono and Amiable Compositeur (2013).
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). (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 8.2.35 for additional discussion of that point).
From what your author has seen, however: 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 side. 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 subdivision contemplates delaying that decision.)
8.2.15. Where and how can an arbitration award be enforced?
Enforcement of an arbitration award requires first that the award be "confirmed" by a court of competent jurisdiction, i.e., a court that has legal power over the target of the enforcement target (i.e., the losing party). The Second Circuit explained this: 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).
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 comply with the arbitrator's award.
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.
In that court, 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.
Once Bob gets the award confirmed, he can have the resulting court 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 Contract 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 Clause 3.6.
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).
For that reason, if diversity is indeed the only basis for subject-matter jurisdiction, then a federal court has no power to confirm an award of zero dollars (i.e., a "defense verdict" award) because the required amount in controversy for diversity jurisdiction is not satisfied. See Tesla Motors, Inc. v. Balan, No. 22-16623, slip op. (9th Cir. Apr. 14, 2025) (vacating order confirming "defense verdict" award in favor of Tesla and remanding with instructions to dismiss).
8.2.16. 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 in Concepcion:
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.
Note: As discussed at 8.2.17, Congress later prohibited compulsory arbitration for some types of claim.
Many states' laws likewise strongly favor arbitration. Example: In Apache Corp. (Tex. 2021), 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).
8.2.17. But some compulsory arbitrations might be 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) affirmingChamber 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.
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 in Murray (2024), 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 an executive order 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 order sets 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).
Relatedly: In a 2024 decision, 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, as happened, for example, in a 2022 Third Circuit case. See Zirpoli v. Midland Funding, LLC, 48 F.4th 136 (3d Cir. 2022) (reversing denial of motion to compel arbitration).
Comment
Arbitration under Truth in Lending regulations: 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).) The CRA prohibits reissuing an overturned rule in substantially the same form without specific congressional authorization. See generally Congressional Research Service, The Congressional Review Act (CRA): A Brief Overview (Congress.gov 2023).
8.2.18. What arbitration administrators are out there?
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 — among other advantages.
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).
8.2.19. But can't the arbitrator just handle the admin chores?
Experienced arbitrator Gary McGowan — previously a founding name partner of leading national litigation boutique Susman & McGowan, now Susman Godfrey LLP — points out some 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.
Moreover, 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.
8.2.20. What arbitral rules are available in the U.S.?
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: This happened, for example, in a 2023 Third Circuit decision, where 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 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 at 8.2.19.
• For international arbitration, see Gans and Billing (CorporateCounsel.com), with a chart — possibly outdated — of selected key aspects of different rules.
8.2.22. 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.
8.2.23. Why just one arbitrator (usually)?
Three arbitrators are likely to be more than three times as expensive as 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.
8.2.24. How would a three-arbitrator panel operate?
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-44 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-44 (which are a bit convoluted); 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.
8.2.25. What qualifications would arbitrators have?
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 Contract 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).
8.2.26. Delegation of arbitrability disputes to the arbitrator must be clear and unmistakable
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, as discussed at 8.2.35. 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., No. 24-1328, slip op. (4th Cir. Mar. 7, 2025) (reversing district court and remanding with instructions to compel arbitration).
On the other hand: In 2024, the Supreme Court held that, 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).
8.2.27. Delegation might be specified in arbitration rules
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., No. 90, slip op. at 5-6, 14-16 (N.Y. Nov. 25, 2024) (affirming denial of motion to stay arbitration and affirmance of order compelling arbitration) (citing Henry Schein, Inc.).
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, 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 DDK Hotels, LLC, v. Williams-Sonoma, Inc., 6 F.4th 308, 319-21 (2d Cir. 2021).
8.2.28. Would delegation be unconscionable?
A court might hold that the delegation agreement was unconscionable; this happened in a 2024 Ninth Circuit case; as stated in the court staff's syllabus:
The panel held that the delegation clause was part of a contract of adhesion, and the Terms on Ticketmaster's website, and the manner in which Ticketmaster bound users to those Terms, evinced an extreme amount of procedural unconscionability far above and beyond a run-of-the-mill contract-of-adhesion case.
In addition, four features of New Era's arbitration Rules supported a finding of substantial substantive unconscionability of the delegation clause[.]
8.2.29. 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 8.2.26.
8.2.30. Jury waivers: Can states restrict arbitration that way?
Juries aren't used in arbitration, but in some cases, a party has tried to set aside a pre-dispute arbitration agreement (e.g., in an employment agreement) on grounds that the arbitration agreement was a pre-dispute waiver of jury trial that, as such, was unenforceable in the forum jurisdiction.
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 8.42. But that shouldn't affect arbitration cases, though — at least not in those cases where the Federal Arbitration Act applied. That's because the Act would arguably preempt such state-law prohibitions of advance jury waivers. This thinking comes from the Supreme Court's 2011 Concepcion case, 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: In a 2019 decision, Nevada's 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: In 2014, 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 (your author was one of them), 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: 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.
8.2.31. Should arbitrators be able to award punitive damages?
Option 8.1.8 prohibits arbitrators from awarding punitive damages. This 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 8.2.35). 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).
Another approach 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).
Drafting note: The prohibition in Option 8.1.8 is phrased without the qualifier, "to the maximum extent permitted by law" — otherwise, the arbitrator might be able to award punitive damages anyway, as happened in a 2004 case where, the court held, state law prohibited advance waivers of liability for the (tortious) conduct in question. See Stark v. Sandberg, Phoenix & von Gontard, P.C., 381 F.3d 793, 800 (8th Cir. 2004).
8.2.32. Class-action arbitration: Is that "a thing"?
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 its 2010 Stolt-Nielsen decision, 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.).
But: As discussed in more detail at 8.2.33 just below. 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.
8.2.33. Who should decide class arbitrability?
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. 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).
Unfortunately, arbitrators have been known to "find" an agreement to class arbitration even though the contract said nothing of the sort — your author has 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: In a Fifth Circuit case, 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.
(See also section 8.2.35, providing for enhanced appeal of an arbitration award.)
8.2.34. 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).
And under the Act, arbitration awards are largely unappealable in federal court except on very limited grounds — including that "the arbitrators exceeded their powers." See 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 Clause.)
In its Hall Street decision, 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, 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 (2013) (affirming denial of motion to vacate arbitrator's approval of class action; reformatted); see also Quality Custom Dist'n Svcs. LLC v. Teamsters Local 710, No. 24-1648, slip op. (7th Cir. Mar. 13, 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).
More than a quarter century early, 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 in Zimmer Biomet 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 Brown), 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).
Editorial 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.
8.2.35. Enhanced appeals under state arbitration law?
Happily, drafters can keep in mind another possibility for enhanced appellate review: 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: The supreme court of California ruled that, in proceedings under the arbitration acts of their respective states, the parties were free to agree to enhanced judicial review. 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.)
Counterexample: The Tennessee supreme court held that an arbitration agreement's expansion of the scope of judicial review was invalid. See Pugh's Lawn Landscape Co. v. Jaycon Dev. Corp., 320 S.W.3d 252 (Tenn. 2010) (vacating judgment confirming arbitrator's award).
8.2.36. 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: In 2003, the Second Circuit 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]." 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 Assoc., Inc., v. Abumasmah, 993 F.3d 261, 264-65 (4th Cir. 2021), citingMACTEC, Inc. v. Gorelick, 427 F.3d 821, 830 (10th Cir. 2005).
8.2.37. Precluding class arbitration — a costly mistake?
Option 8.1.3'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 8.2.35).
– 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 footnote (which is optional reading for students).
8.2.38. 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 — this happened in a Ninth Circuit case in which 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).
8.2.39. Could "mass" arbitration be done in stages?
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.
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" with a "[t]echnology-focused approach to case management."
8.2.41. Or: Maybe just allow class arbitration?
At this writing, it has yet to be established which if any of the above "hybrid" approaches will be accepted by courts. As noted in a 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.
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 8.2.35.
8.2.42. Tangential: Would a waiver of class actions in court be given effect?
Example: In 2023, citing decisions from several jurisdictions, a federal district court in Rhode Island 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: In 2024, 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, 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: In 2005, 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).
8.2.43. 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 (U.S. 2019): "[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 (U.S. 2013): 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. American Express Co. v. Italian Colors Rest., 570 U.S. 228 (2013) (reversing Second Circuit).
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: In a 2023 California decision involving In-N-Out Burgers, the 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), citingViking 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, in its 2024 Johnson decision, 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).
8.2.45. Employers: Pay your arbitration fees!
In a California case, 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. But the company failed to pay a third invoice for arbitration fees. In response, the worker successfully moved to withdraw from arbitration and vacate the stay — so the company ended up in litigation after all. See Colon-Perez v. Security Indus. Specialists, Inc., No. A168297, slip op. (Cal. App. Jan. 29, 2025) (affirming trial court's actions).
8.3. Archive Copies
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 Clause 8.35 — which in turn are likely to be used in conjunction with confidentiality obligations such as Clause 8.18. (Some of the provisions of this Clause are adapted from their counterparts in Clause 8.18.)
No Options below will apply unless the Contract clearly adopts the specific Option in question.
Click the following footnote to see all of this Clause's footnotes together:
Comment
ARCHIVE COPIES FOOTNOTES start here.
8.3.1.1. Applicability
This Clause presupposes that the Contract clearly calls for one party (the "Retainer") to return, turn over, or destroy one or more of the following:
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
materials that the Retainer derived from (or had others derive from) materials provided by the Owner.
8.3.1.2. Examples of archival materials
Here are few possible examples of materials for which archive copies might be retained:
electronic documents;
"hard copies";
photographs and video / audio-visual recordings, including, for example, those made to document events and/or tangible objects.
8.3.1.3. Retention right
The Retainer may cause archive copies to be maintained of the materials described in this Clause, as follows:
indefinitely, so long as the requirements of this Clause continue to be met;
in one or more reasonable locations of the Retainer's choice — as long as those choices are consistent with this Clause (including, if applicable, any specific limitations on such locations stated in the Contract).
Comment
Backup copies could be important: The right to maintain backups of archive copies could be especially important in the case of electronic archive copies, where backups commonly happen automatically.
Comment
Indefinite archive-copy retention could be the best approach: 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.
8.3.1.4. Required security precautions
The Retainer is to cause at least prudent security measures to be taken to protect the archive copies.
8.3.1.5. Outside storage organizations
The Retainer may use one or more reputable storage organizations for custody of archive copies, but only under suitable written contracts.
8.3.1.6. Consultation about security measures
If the Owner asks from time to time, the Retainer will consult 11.12 with the Owner about archive-copy security measures.
8.3.1.7. Off-limits Retainer activities
Except as agreed in writing by the Owner — in this Clause or otherwise — the Retainer must not do any of the following things in respect of the archive copies and any Owner confidential information that's contained in them:
allow anyone to access to the archive copies; nor
disclose or use the information; nor
allow, or knowingly assist, in any unauthorized disclosure, use, or access; nor
confirm to any person whether or not particular information is contained in archive copies.
8.3.1.8. Exception for independent possession by Retainer
The Retainer may disclose or use information in archive copies if the Retainer clearly 7.13 shows that the Retainer independently possessed 8.20.6.5 the information. (For emphasis: This subdivision does not authorize the Retainer to confirm to others that the archive copies contain the information in question.)
8.3.1.9. Restricted Retainer disclosures
Unless clearly agreed otherwise, the Retainer may disclose information in archive copies (subject to any restrictions in applicable law) only as follows:
to personnel of an outside archive custodian under this Clause (if any) as needed to maintain the archive copies;
to the limited extent clearly authorized by law, for example by the (U.S.) Defend Trade Secrets Act;
in response to a subpoena, search warrant, etc. — but only in accordance with Clause 8.18.28; and
to the extent (if any) that the Owner so agrees in writing.
8.3.1.10. Restricted access by others
Unless clearly agreed otherwise, the Retainer may allow others to access archive copies from time to time only in one or more of the following ways:
by the Retainer's people who maintain the archive copies (if applicable);
as agreed in writing by the Owner — including, but not limited to, for uses authorized by the Contract; and/or
in connection with a disclosure permitted under the Contract.
8.3.1.11. Restricted use of archive copies
Unless clearly agreed otherwise, the Retainer may use information contained in archive copies only for one or more of the following purposes:
determining the Retainer's continuing rights and/or obligations under the Contract;
causing and monitoring the parties' compliance with their respective obligations;
documenting the parties' past- and present interactions relating to the Contract;
reasonable testing of the accuracy of the archive copies; and/or
as otherwise agreed in writing by the Owner.
8.3.2. Option: Use for Retainer's Business Purposes
The Retainer may, as the Retainer sees fit in its sole and unfettered discretion:
access and use archive copies — solely for the Retainer's internal business purposes — as long as as the Retainer otherwise restricts use as stated in the Contract; and/or
allow others to access and use archive copies — again, solely for the Retainer's own internal business purposes — in the same manner as in subdivision (1) above.
Comment
Caution: What constitutes the Retainer's "internal business purposes" could be open to dispute.
8.3.3. Option: "Have-Used" Rights
(a) 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 with the restrictions stated in this Option. (b) The third party's use must be solely for the Retainer's benefit. 16.3 (Incidentalthird-party benefit is permissible, for example if the Retainer pays the third party for services that are permitted under this Clause.) (c) The Retainer must enter into a written agreement with each such third party; that agreement must impose use- and disclosure restrictions on the third party that are substantially identical to those that apply to the Retainer under the Contract.
8.3.4. Option: Access List for Archive Copies
Whenever the Owner reasonably 7.41 asks, the Retainer will provide the Owner with a complete and accurate list of all persons who have had access to archive copies maintained by or for the Retainer.
Comment
Caution: The Retainer might well object to providing a list of people who had access to archive copies, on grounds that: (A) it could be burdensome, and (B) it might tempt the Owner to put its nose too far into the Retainer's business.
8.3.5. Option: No Outside Custodians
The Retainer will maintain all archive copies itself (i.e., with the Retainer's own employees), without using an outside archive custodian.
Comment
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, it might be more costly for the Retainer than simply engaging an outside custodian.
8.3.6. Option: Only Outside Custodians
The Retainer is to use an outside archive custodian, approved in advance by the Owner, for all archive copies — with such approval: [ x ] not to be unreasonably withheld, conditioned, or delayed. 8.21 [ ] to be granted or withheld in the Owner's sole discretion. 7.23
Comment
Caution: Outside custodians for archive copies would be an extra expense for the Retainer — but that might well be more cost-effective than the Retainer's trying to maintain the archive copies itself.
8.4. Assignment Consent
A contract can state that one or more specified parties may not "assign" the contract (explained at 8.4.2) without the other party's consent, even if the law would otherwise allow assignment (see 8.4.3). This can often happen, for example, when a customer with bargaining power insists that a supplier may not assign a contract for the sale of goods or for services.
a specified party to the Contract (the "Assigning Party") wants to assign the Contract to another party; but
the Assigning Party is required — by the Contract itself, and/or by law — to obtain the consent of another specified party to the Contract (the "Reviewer").
8.4.1.2. No effect on Reviewer's other rights
For emphasis: An assignment of the Contract will not affect any right or remedy that the Reviewer has against the Assigning Party, where the right or remedy accrued before the assignment took effect — unless the Contract specifically says otherwise, that is.
Comment
Assignment doesn't affect other rights: This is more or less how the law works in the U.S.; it's included here as a reminder for readers who might not know or remember; see also 8.4.19 for the special case of assignments under section 2-210 of the Uniform Commercial Code (concerning contracts for the sale of goods).
8.4.1.3. No consent needed for corporate-form change
For purposes of this Clause, the term "assignment" does not include — and so the Reviewer's consent is not required for — a change in the Assigning Party's corporate form, 8.4.10 as long as that change does not materially alter:
the beneficial ownership or control of the Assigning Party; nor
the day-to-day operations of the Assigning Party's business in respects that are relevant to the Contract.
8.4.1.4. Pledges — no consent needed
For emphasis: The Assigning Party need not obtain the Reviewer's consent for a "Pledge," namely:
an assignment, sale, or pledge of a right under the Contract, for example, a right to be paid; and/or
a grant of a "security interest" in any such right — in any such case, whether the assignment, sale, pledge, or security-interest grant is absolute or collateral — unless the Pledge: (x) delegates one or more of the Assigning Party's obligations under the Contract; and/or (y) has such an effect as a matter of law.
Comment
Pledge ≠ assignment: Sometimes a party — let's call that party the "Biller" — is owed money under a contract, and so the Biller will "sell," to a third party, the Biller's right to the future payment(s). Generally, the amount that the Biller gets from the third party will be at a discount from the face value of the amount owed; for example, the Biller might sell, for (say) $98, the Biller's contractual right to be paid $100 in three months. (The numbers here are completely fictitious.) This gives the Biller early access to the money it's owed; it's generally referred to as "factoring."
8.4.2. Reading: What happens when a contract is "assigned"?
When a contract is assigned:
the assignor delegates, to the assignee, responsibility for the assignor's obligations;
the assignor remains liable to the other party for any breach by the assignee; and
the assignee is entitled to the assignor's rights under the contract.
This general rule is reflected in, e.g., section 2-210 of the Uniform Commercial Code (which applies to the sale of goods only but is sometimes used by courts as guidance for other situations).8.4.19
The assignability of contracts is a key feature of "futures" trading in commodities, stocks, currencies, interest rates, and the like. For example, in the case of natural gas, a U.S. Department of Energy Website explains that, "The natural gas futures market is a marketplace where standardized contracts for the future delivery of set natural gas volumes are traded." U.S. Energy Information Administration, What is the natural gas futures market? (2024) (emphasis added). • For a readable explanation of commodity futures trading, see, e.g., Adam Hayes, Commodity Futures Contract: Definition, Example, and Trading (Investopedia.com 2022).
Similarly, companies and individuals buy (or sell) standardized "call" and "put" option contracts for stocks, commodities, and the like, to reduce the risk of price volatility. See generally, e.g., Casey Murphy, Put Option vs. Call Option: When to Sell (Investopedia 2024).
8.4.3. General rule: Most "ordinary" contracts can be assigned
Pro tip: Here's some sample language to consider using to require assignment: "Except as clearly stated otherwise in the Contract, [fill in the prospective assigning party's name — neither party if a name is not filled in] must not assign the Contract without the prior written consent of [fill in the reviewing party's name — ditto]."
To promote economic efficiency, the general rule is that — with some exceptions in special cases, discussed in the additional notes beginning at 8.4.4 below — contracts are assignable without consent.
8.4.4. But: IP licenses aren't assignable by the licensee
One exception to the is that intellectual-property licenses are not assignable by the licensee without the consent of the owner of the intellectual property in question. See, e.g.: In re XMH Corp., 647 F.3d 690 (7th Cir. 2011) (Posner, J.) (trademark licenses); Cincom Sys., Inc. v. Novelis Corp., 581 F.3d 431 (6th Cir. 2009) (copyright licenses); Rhone-Poulenc Agro, S.A. v. DeKalb Genetics Corp., 284 F.3d 1323 (Fed. Cir. 2002) (patent licenses).
(The licensor is presumably free to assign if it wishes.)
A tangential point: Some license agreements prohibit assignment of the license but allow the licensee to sublicense to third parties. That could result in litigation over whether a given transaction by the licensee was a prohibited assignment, or instead was a permitted sublicense. Example: In 2014, Florida's supreme court declined to impose a bright-line rule on this point, noting that the name given to the transaction ("assignment" or "sublicense") would not be determinative. MDS (Canada) Inc. v. Rad Source Tech., Inc., 143 So. 3d 881, 889 (Fla. 2014), on certification from720 F.3d 833 (11th Cir. 2013), affirming in part822 F. Supp. 2d 1263 (2011).
Another exception to the rule of free assignability is that a party may not assign a contract if the assigning party's performance is considered special or unique.
Caution: For any given contract, the question whether a particular party's performance would fall into this "special or unique performance" category would probably present factual issues that would have to go to trial, as opposed to being adjudicated more quickly and less expensively on the pleadings or on summary judgment. As a probably-absurd hypothetical example:
Suppose that Houston's own Megan Thee Stallion, a Grammy-winning rapper, entered into a contract to sing at a rap festival.
Now suppose that Megan wanted to assign her contract to, say, Ted Nugent (who is … not a rapper) without first getting an OK from the festival organizers: If that were to end up in a lawsuit, it would almost certainly result in summary judgment that Megan could not assign the contract.
It might be a different story question if Megan wanted to assign her contract, without consent, to one of her fellow rappers Cardi B and/or Nicki Minaj — that might well have to go to trial.
8.4.6. Another special case: Federal-government contracts
Author's note: For federal (U.S.) contracts, the following is an edited version of an excerpt (with extensive citations omitted) from ATS Trans LLC v. Dept. of Veterans Affairs, No. CBCA 7163, slip op. at 3-4 (U.S. Civilian Bd. of Contract App. Jun. 27, 022). No copyright is claimed in the decision text, which is a work of officers or employees of the U.S. Government under 17 U.S.C. § 105.
The Assignment of Contracts Act, 41 U.S.C. § 6305, and the Assignment of Claims Act, 31 U.S.C. § 3727, together make up the “Anti-Assignment Acts.” These Acts generally prohibit the assignment of a government contract or claim.
The Acts serve two primary purposes – first, to prevent persons of influence from buying up claims against the United States, which might then be improperly urged upon officers of the Government; and second, to enable the United States to deal exclusively with the original claimant instead of several parties.
Any attempt to transfer a contract in violation of the Assignment of Contracts Act annuls the contract. A valid transfer subject to that statute requires government approval to be binding against the Government. The Government can recognize an assignment expressly via novation or implicitly by ratification or waiver.
Assignments occurring by the “operation of law” (i.e., corporate restructurings, mergers, and name changes “where in essence the contract continues with the same entity, but in a different form”) are exempt from the Act’s application. … Courts have applied the exception to statutory mergers, concluding that such assignments do not present the danger that the statute was designed to obviate.
8.4.7.State-government contracts might not be assignable
Example: A New York statute provides that, whenever a company enters into a contract with a state agency, the company cannot assign the contract without the agency's consent; if the contractor fails to obtain the consent, the agency "shall revoke and annul such contract," and the contractor forfeits all payments except that needed to pay its employees. See N.Y. State Fin. L. art. 9, § 138.
The non-assignability of state contracts can give the state agency considerable leverage — and in New York, state agencies apparently can be quite unabashed about wielding that leverage, as seen in one noteworthy episode involving the Port of New York and New Jersey and a Dubai company (8.4.8).
8.4.8. The strategic importance of the asset-disposition exception
A prospective assigning party will want to seriously consider negotiating for Option 8.5.1 (asset dispositions) and/or Option 8.5.2 (mergers).
In the modern world (especially the startup world but also in the "oil patch"), a party to a contract might later want to do a major "corporate" transaction such as a merger or asset sale. Such a transaction might well entail "assigning" (see 8.4.2) one or more associated contracts — but the assigning party might first have to get consent for the assignment from the other party to the contract, and that might be true for multiple contracts.
Such a consent requirement could, in effect, give each of those contract counterparties a de facto veto over the assigning party's ability to do the "corporate" transaction — and if the counterparty were to stall (perhaps in the hope of "extracting" financial- or business concessions), the opportunity for the transaction might disappear as the other party to the transaction grew tired of waiting.
Example: In one high-profile, politically-sensitive case involving a Dubai company, the Port of New York and New Jersey insisted on being paid a $10 million consent fee — plus a commitment to invest another $40 million in improvements to terminal operations — in return for the Port's consent to an assignment of a lease, as reported in the New York Times.
Example: Tech giant Cisco Systems spun off its video services division, selling the division to a private equity firm; the spun-off division was rebranded as Synamedia.
As part of the transaction, Cisco sold certain assets to Synamedia, which also assumed certain liabilities. (This is not an uncommon approach.)
But there was a problem: One of the assets to be acquired by Synamedia was a 25-year lease in Hampshire, England — and that lease required the landlord's consent to an assignment.
The landlord refused to consent to Cisco's assignment of that lease.
Synamedia moved out of the space, and Cisco and Synamedia ended up in litigation over who was responsible for paying the rent. (The parties ultimately settled the lawsuit.) See Cisco Sys., Inc. v. Synamedia Ltd., 557 F. Supp. 3d 464 (S.D.N.Y. 2021) (granting in part and denying in part Synamedia's motion to dismiss). (Hat tip: @NYContracts.)
Example: Restaurant chain Ruby Tuesday ("Ruby") was the tenant in a lease of a mansion that Ruby used for corporate retreats.
Encountering financial difficulties, Ruby wanted to sell the lease to a real-estate developer, BNA Associates.
But to assign the lease, Ruby needed the consent of one of Ruby's creditors, Goldman Sachs, because of a provision in their credit agreement.
Goldman refused its consent; Ruby lost the deal and ended up in bankruptcy — and Goldman ended up with the lease that the real-estate developer had wanted to buy from Ruby.
The real-estate developer sued Goldman for intentional interference with business relations.
Affirming the trial court's order dismissing the case, the Sixth Circuit was equally dismissive: "Goldman was perhaps playing hardball. Any rational actor would likely have done the same, were it in their perceived best interest." See BNA Assoc. LLC v. Goldman Sachs Specialty Lending Grp., L.P., 63 F.4th 1061, 1063 (6th Cir. 2023).
8.4.9.Caution: A merger might be an "assignment"
For prospective assigning parties, Option 8.5.2 could be a strategically-important add-on to any assignment consent provision. That's because in some jurisdictions, the wording of a merger agreement could automatically result in an assignment of assets by operation of law. That could mean that the transaction required consent in the same way as an "assignment." For example: If the assigning party was not the "surviving entity" in the transaction, then the transaction could constitute an "assignment" and thus would require consent — and that, in turn, would give the other party considerable leverage, and even a veto, over the assigning party's strategic options.
Language choice: Option 8.5.2 is worded to allow the Assigning Party to assign the Contract to an affiliate of the buyer of the Assigning Party's business — this has in mind that a common structure for acquisition transactions is the so-called reverse-triangular merger.
Caution: Conceivably the Assigning Party might indeed be subject to other consent requirements arising outside the Contract, as discussed beginning at 8.4.4.
Comment
Merger as assignment?Example: Delaware's chancery court ruled, on summary judgment, that "mergers do not result in an assignment by operation of law of assets that began as property of the surviving entity and continued to be such after the merger." Meso Scale Diagnostics, LLC v. Roche Diagnostics GmbH, 62 A.3d 62 (Del. Ch. 2013) (partial summary judgment; emphasis added).
Example: A California appeals court held that "where the form of reorganization was not chosen to disadvantage creditors or shareholders, we will not ignore the form of reorganization chosen by the corporation." North Valley Mall, LLC v. Longs Drug Stores California LLC 27 Cal. App. 5th 598, 600, 238 Cal. Rptr. 3d 368 (2018) (California law). For a now-dated review, see generally a 2006 state-by-state survey by Jolisa Dobbs, archived at https://perma.cc/SLW4-TBP6.
Counterexample: An anti-assignment clause in a contract prohibited a particular party from assigning the contract without consent, whether "by operation of law or otherwise"; that particular party was later merged out of existence — and a Delaware trial court held that the resulting unauthorized assignment caused the assigning party, and thus its assignee, to lose the right to certain payments. See MTA Canada Royalty Corp. v. Compania Minera Pangea, S.A. de C.V., No. N19C-11-228, slip op. at text acc. nn.14 et seq. (Del. Super. Ct. Sept. 16, 2020) (granting motion to dismiss successor's claim for payment).
Relatedly: See the discussion, at 8.4.10, of the Whitson’s Food Service case, where the parties were told they still had to litigate whether a merger constituted an "assignment" requiring consent.
8.4.10. Changes in corporate form: A deemed assignment?
Background: Sometimes a party to a contract will change its organizational form, for example:
by changing from a limited-liability company ("LLC") to a corporation, or vice versa; or
by reincorporating in a different state, e.g., "moving" from Delaware to Texas, as Elon Musk's companies SpaceX and Tesla did in 2024.
If that contract required the party to obtain consent to an "assignment," would the party breach that consent obligation if it didn't obtain consent to its change of organizational form? The significance of this issue can be seen by a 2024 New York case:
The plaintiff was a corporation when it entered into the contract in suit with the defendant, but later the plaintiff changed its corporate form by merging with an LLC.
Importantly, the contract included an assignment-consent requirement: "This Agreement and the rights granted hereunder may not be assigned by either Party, whether by operation of law, merger, change of ownership or otherwise, without the prior written consent of the other Party, and any unauthorized assignment shall be void ab initio." Bold-faced emphasis added; ab initio means, roughly, "from the start."
The plaintiff sued the defendant for breach of the contract; the defendant moved to dismiss for lack of standing, on grounds that the defendant had entered into the contract with the corporation, not the LLC.
The court denied the defendant's motion, holding that "the plaintiff raised a question of fact as to whether the merger constituted an assignment that violated the nonassignment provision of the contract." Whitson’s Food Service, LLC v. A.R.E.B.A.-Casriel, Inc., 2024 NY Slip Op 04480, 230 A.D.3d 1274, 218 N.Y.S.3d 455 (App. Div.) (affirming denial of motion to dismiss for lack of standing).
See also the commentary at 8.5.2 for more on whether a merger might constitute an assignment requiring consent.
8.4.11. A change of control normally won't require consent
In the U.S., a change of control of a licensee corporation, through a transfer of the corporation's stock, is not an "assignment" of the license and thus doesn't require licensor consent (assuming that the licensee remained a separately functioning corporation). See VDF Futureceuticals, Inc. v. Stiefel Labs., Inc., 792 F.3d 842, 846 (7th Cir. 2015) (Posner, J.).
Caution: An assignment-consent provision could specifically provide that a change of control does indeed requires consent — but that would likely be objected to by any party with any sort of bargaining power.
Example: In 2022, semiconductor designer Arm announced that it had sued its licensee Nuvia after Nuvia's acquisition by Qualcomm. Arm claimed that "Qualcomm attempted to transfer Nuvia licenses without Arm’s consent, which is a standard restriction under Arm’s license agreements"; see also the complaint at paragraphs 28 and 36. At this writing (early summer 2024), the lawsuit seems still to be ongoing.
8.4.12. Just obtaining consent(s) can delay a deal
Even the burden and delay attendant to obtaining consents to assignment could pose a problem for an assigning party.
Example: In a 2014 Florida case, an assigning party wanted to sell a line of business but had to seek consent from some 25 different counterparties. See MDS (Canada) Inc. v. Rad Source Tech., Inc., 143 So. 3d 881, 889 (Fla. 2014), on certification from720 F.3d 833 (11th Cir. 2013), affirming822 F. Supp. 2d 1263 (2011).
Example: In 2015, General Electric announced that it was selling more than $30 billion of commercial loans to Wells Fargo, completing the sale in early 2016. In the worst case, the relevant GE company might have had to assign thousands of loan-related agreements to a Wells Fargo company — and that might have required checking each of those agreements to be sure it didn’t have a provision requiring GE to get the borrower’s or guarantor’s consent before assigning the agreement.
8.4.13. A reviewing party might "play chicken" about consent
A reviewing party, asked to consent to an assignment of a contract, might be willing to "play chicken" with the assigning party by (metaphorically) folding its arms and saying, in effect: We think we ARE being reasonable in withholding our consent unless you pay us big bucks. If you don't agree, then sue us — and watch your deal evaporate before your eyes while you wait months or years for the court proceedings to end.
(Presumably the reviewing party would never be so incautious as to actually say something like the previous paragraph, because it would look really bad to a judge or jury if it were to be quoted — or misquoted — in court.)
An assigning party concerned about this possibility could ask for Option 8.5.11 to impose a deadline for refusing consent.
8.4.14. "Consent not to be unreasonably withheld …" — by law?
Concerning Option 8.5.4: In some jurisidictions, the law might require that consent to assignment of the agreement must not be unreasonably withheld.
Example:Section 1995.260 of the California Civil Code provides that: "If a restriction on transfer of the tenant's interest in a lease requires the landlord's consent for transfer but provides no standard for giving or withholding consent, the restriction on transfer shall be construed to include an implied standard that the landlord's consent may not be unreasonably withheld. … "
Example: Apropos of that statutory provision, a California appeals court held that a contract provision allowing the landlord to withhold consent "for any reason or no reason" was not to be construed as including an unreasonably-withheld standard, saying that "the parties' express agreement to a ‘sole discretion' standard is permitted under legal standards existing before and after enactment of section 1995.260, as long as the provision is freely negotiated and not illegal." Nevada Atlantic Corp. v. Wrec Lido Venture, LLC, No. G039825 (Cal. App. Dec. 8, 2008) (unpublished; reversing trial-court judgment that withholding of consent was unreasonable).
Example: In an Oregon case:
A lease prohibited the tenant from assigning the agreement, including by operation of law, without the landlord's consent.
The lease also stated that the landlord would not unreasonably withhold its consent to an assignment of the lease to a subtenant that met certain qualifications.
Notably, though, the lease did not include a similar, no-unreasonable-withholding statement for other assignments.
Oregon's supreme court held that ordinarily, the state's law would indeed have required the landlord to act in good faith in deciding whether or not to consent to an assignment. But, the court said, the parties had implicitly agreed otherwise — therefore, the landlord did not have such a duty of good faith. Pacific First Bank v. New Morgan Park Corp., 876 P.2d 761 (Or. 1994) (affirming court of appeals decision on different grounds, and reversing trial-court declaration that bank-tenant had not materially breached lease).
Example: The Eleventh Circuit upheld a trial court's finding that the owner of a patent, which had exclusively licensed the patent to another party, had not acted unreasonably under the circumstances when it refused consent to an assignment by the licensee to a party that wanted to acquire the licensee's relevant product line. (This holding provides a useful illustration of how appeals courts have limited ability to "second-guess" a trial court's findings of fact.) MDS (Canada) Inc. v. Rad Source Tech., Inc., 720 F.3d 833, 850 (11th Cir. 2013), affirming in part822 F. Supp. 2d 1263 (S.D. Fla. 2011).
Example: Tennessee's supreme court held that:
where the parties have contracted to allow assignment of an agreement with the consent of the non-assigning party,
and the agreement is silent regarding the anticipated standard of conduct in withholding consent,
[then] an implied covenant of good faith and fair dealing applies[,]
and requires the nonassigning party to act with good faith and in a commercially reasonable manner[,]
in deciding whether to consent to the assignment.
Dick Broadcasting Co. v. Oak Ridge FM, Inc., 395 S.W.3d 653, 656-57 (Tenn. 2013) (affirming vacation of summary judgment and remand to district court) (formatting revised).
Example: Alabama's supreme court alluded to a similar possibility: The contract in suit specifically gave the Shoney's restauraunt chain the right, in its sole discretion, to consent to any proposed assignment or sublease of a ground lease by a real-estate developer that had acquired the ground lease from Shoney's. The supreme court held that this express language overrode a rule that had been laid down in prior case law, namely that a refusal to consent is to be judged by a reasonableness standard under an implied covenant of good faith. Shoney's LLC v. MAC East, LLC, 27 So.3d 1216, 1220-21 (Ala. 2009) (on certification by Eleventh Circuit).
Counterexample: The Texas supreme court declined to read a reasonableness requirement into an assignment-consent provision. Barrow-Shaver Resources Co. v. Carrizo Oil & Gas, Inc., 590 S.W.3d 471, 476 (Tex. 2019) (affirming court of appeals and declining to read a reasonableness qualifier into a consent-to-assign provision).
Caution for Texas lawyers and law students: Barrow-Shaver fits in with Texas's non-recognition of a general implied covenant of good faith and fair dealing. See, e.g., Subaru of America, Inc. v. David McDavid Nissan, Inc., 84 S.W.3d 212 (Tex. 2002); 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).
And again: The reviewer might be willing to "play chicken" with the proposer, as discussed at 8.4.13.
For additional discussion of consent standards, see 8.21.
8.4.15. "The economics" might justify requiring consent
A reviewing party might feel that it had made economic- or other concessions to its original counterparty that it would not be willing to do for an acquiring party. For example: Suppose that:
Researchers at a university obtain a patent on an invention.
The university grants a license to a startup company that was founded to commercialize the invention.
The license agreement contains terms very favorable to the startup company, such as a low royalty rate.
In such a situation, the university might not necessarily be willing to have the startup company — and the patent license — to be acquired by a giant corporation in the same field, because the university might not have been willing to give the giant corporation the same low royalty rate.
8.4.16. What other consent factors might be relevant?
In reviewing a request for consent to assignment, a reviewing party should give due consideration to any evidence that the assigning party provides concening the apparent qualifications of the proposed assignee.
Toward that end, see 8.21 concerning factors that a Reviewer may take into account, and those that a Reviewer must take into account, in deciding whether to grant consent.
8.4.17. Assignment in part might be desired
An assigning party might want to assign a contract only "in part" — this would be to support a not-uncommon business practice in which:
A company (the "seller") is licensed to use certain software in its business;
The seller sells an unincorporated division of its business, or a site such as a refinery or a factory;
In connection with the sale, some of the seller's people will change employers, so that after the sale closes, those people will continue in their old jobs, but they'll now be working for the buyer;
Both the seller and the buyer want those people to be able to keep using the software in question — but that might be tricky if the buyer isn't already licensed to use the software.
Moreover, the seller wants to continue using the software in the rest of its business, as before.
For that reason, Option 8.5.1 is set up to allow the seller to assign the software license "in part."
To be sure: If the software licensor (i.e., the company that makes and licenses the software) had enough bargaining power, then the licensor might demand that the buyer buy its own license to use the software; that could be a nice, incremental chunk of sales revenue for the licensor.
But that might well be short-sighted, because the buyer and seller of the business might ask, "Hey, the seller already paid for the license; why should the buyer have to re-buy it?"
Example: In one case, a software customer (i.e., the licensee) did a corporate reorganization by, in relevant part, a series of mergers.
As a result of the mergers, the named licensee technically became part of a different corporation that was owned by the same parent company — but nothing else had changed.
The software vendor demanded that the customer re-buy the license; the customer refused.
The software vendor took the customer to court — and won. See Cincom Sys., Inc. v. Novelis Corp., 581 F.3d 431 (6th Cir. 2009) (affirming summary judgment in favor of software vendor).
Editorial comment: That software vendor might have been extremely short-sighted. Look at it from a sales perspective: When a vendor treats a customer that way, what are the odds that the vendor will ever be able to sell anything again to that customer — let alone convince the customer to serve as a favorable reference to other potential customers? Talk about pennywise and pound-foolish ….
In contrast, a smart software licensor will want to agree even to just a partial assignment of the software license. Why? Because the people in the seller's spun-off division — who're now working for the buyer — could serve as unofficial ambassadors for the software licensor, encouraging their new employer to acquire more licenses to use the software elsewhere in the new employer's organization.
When a contractor enters into an agreement with an owner (for example, a construction contract to build a building), the owner's lender might ask the contractor to sign an agreement that includes — possibly among other burdens — the contractor's obligation to assign the contract to the lender in certain circumstances. For example, Taylor (2021) points out:
While the content of these agreements differs from lender to lender, here’s what they normally contain:
A. A contractor consent to a potential assignment of the prime contract to the lender in the event the owner defaults;
B. The circumstances under which the contractor will or will not get paid for past and future work;
C. A waiver of lien rights for work in place; and
D. Obligation on the contractor to seek prior written permission directly from the lender, during the project, and prior to any possible default by the owner, for any change in the plans, the schedule, and even any change orders.
In the specific context of sales of goods, UCC § 2-210 states:
(1) A party may perform his duty through a delegate [A] unless otherwise agreed or [B] unless the other party has a substantial interest in having his original promisor perform or control the acts required by the contract.
No delegation of performance relieves the party delegating of any duty to perform or any liability for breach.
(2) Unless otherwise agreed all rights of either seller or buyer can be assigned except where the assignment would materially change the duty of the other party, or increase materially the burden or risk imposed on him by his contract, or impair materially his chance of obtaining return performance.
A right to damages for breach of the whole contract or a right arising out of the assignor's due performance of his entire obligation can be assigned despite agreement otherwise.
(3) Unless the circumstances indicate the contrary a prohibition of assignment of "the contract" is to be construed as barring only the delegation to the assignee of the assignor's performance. …
(4) An assignment of "the contract" or of "all my rights under the contract" or an assignment in similar general terms is an assignment of rights[,]
and unless the language or the circumstances (as in an assignment for security) indicate the contrary, it is a delegation of performance of the duties of the assignor[,]
and its acceptance by the assignee constitutes a promise by him to perform those duties.
This promise is enforceable by either the assignor or the other party to the original contract.
The Assigning Party need not obtain consent to assignment of the Contract if the assignment occurs in connection with a sale or other disposition of substantially all of the assets of:
the Assigning Party's business in its entirety; and/or
a specific line of the Assignee's business to which the Contract relates. 8.4.8
8.5.2. Option: Merger Exception (if Necessary)
The Assigning Party need not obtain the Reviewer's consent to an assignment of the Contract that occurs as a matter of law in a consolidation or amalgamation of the Assigning Party with, or merger with or into, another organization. 8.4.9
For emphasis: By requesting or agreeing to this Option, the Assigning Party is not conceding that the Reviewer's consent would otherwise have been required.
8.5.3. Option: Assignment Consent at Discretion
The Reviewer is free to grant, or withhold, or condition its consent to assignment by an Assigning Party in its sole and unfettered discretion.
Comment
Assignment consent at discretion: This Option is the reverse of the "consent not to be unreasonably withheld" option (8.5.4) that the Assigning Party might prefer.
8.5.4. Option: Consent Not To Be Unreasonably Withheld
The Reviewer will not unreasonably withhold, delay, or condition its consent to a proposed assignment of the Contract by the Assigning Party.
Comment
Assignment consent not to be unreasonably withheld — caution: If an Assigning Party asks to include this Option, it might "poke the bear" (see 30.12) and cause more problems for the Assigning Party than it solves. See also 8.21.10.2 for additional discussion.
8.5.5. Option: Assignment as Material Breach
When this Option is agreed to: If the Assigning Party assigns the Contract without a consent required by law or by the Contract, then that assignment will constitute a material breach of the Contract.
Comment
Unconsented assignment as material breach: An assignment-consent clause might be silent about whether an assignment of the contract, without a required consent, would, or would not, constitute a "material breach" of the Contract. The applicable law might go either way in such a situation, so this Option provides parties with a way to specify materiality.
Why might this matter?
First: if the non-assigning party didn't have the right to terminate for material breach, then:
the non-assigning party could be stuck with a new contract partner;
the non-assigning party's only remedy against the assigning party (for assigning without the required consent) would presumably be money damages; and
it might be difficult — and costly — for the non-assigning party to come up with evidence to persuasively establish the fact and the precise amount of damages.
Moreover: If the non-assigning party did purport to terminate the contract merely because the other party assigned the agreement without consent, that could result in the non-assigning party being liable for wrongful termination.
Example: In a Fourth Circuit case, something like that happened when —
A party terminated a contract because of an allegedly-unconsented assignment by the other party.
The unconsented assignment was held not to be a material breach.
Thus, said the court, the termination was itself a breach, and so the terminating party was held liable for the resulting damages suffered by the other party. See Hess Energy Inc. v. Lightning Oil Co., 276 F.3d 646, 649-51 (4th Cir. 2002) (reversing summary judgment).
8.5.6. Option: Unconsented Assignment Voidable
1. If the Assigning Party assigns the Contract without a consent required by law or by the Contract, then the Reviewer may void the assignment, effective immediately upon the Reviewer's notice to both the Assigning Party and the assignee.
To avoid unfair disruption of the Assigning Party's transaction, the Reviewer's right to void the assignment will automatically expire — and the assignment will not be void — if the Reviewer's notice of voiding has not become effective, as to both the Assigning Party and the assignee, on or before the date one month7.34 after the Reviewer first learns, by any means, of the assignment.
Comment
Unconsented assignment — void, or just voidable? Under the "classical" approach, an assignment without a required consent is automatically void and thus never valid or effective, from the outset — in Latin, "ab initio." On the other hand, under the "modern" approach, such an assignment is a breach of the contract, but the assignment isn't void unless the contract says so. See, e.g., Condo v. Connors at 170-72 (Conn. 2012) (reviewing case law from numerous jurisdictions).
In this Option, we adopt the "modern" approach, based on a suggestion by Sean Hogle at his estimable redline.net site; we're looking to avoid what Vice Chancellor Laster characterized as an "inequitable" result in a 2022 case where where a non-assigning party had acquiesced in the assignment but the consent requirement stated that the assignment was void. See XRI Investment Holdings LLC v. Holifield, 283 A.3d 581, 666 (Del. Ch. 2022).
8.5.7. Option: Waiver of Damages for Withheld Consent
The Reviewer will not be liable to the Assigning Party, nor to any third party, for any kind of monetary award for having withheld, delayed, or conditioned its consent to the assigment — even if the Reviewer's action is found to have been unreasonable.
Comment
Waiver of damages for improperly withholding assignment consent: This could be relevant if the Reviewer's failure to consent ended up blowing up a deal for the Assigning Party to be acquired (completely or partly).
A related question: Without this Option, would damages for unreasonable withholding of consent be categorized as "consequential damages" — and thus subject to a contractual exclusion?
8.5.8. Option: No Assignment of Third-Party Benefits
No third-party beneficiary of the Contract8.66 (if any) may assign rights deriving from that beneficiary status — any purported assignment of such third-party benefits would be void "ab initio" (that is, from the start).8.5.6
The parties' agreement to this Option is not intended to imply that the parties to the Contract intended for any third party to benefit from the Contract, other than perhaps incidentally.
8.5.9. Option: Assignee Reasonable Assurance
When agreed to in the Contract, this Option will govern if a party to the Contract assigns the Contract to another party (the "assignee").
Another, previously-existing party to the Contract (the "requesting party") may give the assignee written notice, in accordance with Clause 6.9, that unambiguously asks the assignee for reasonable assurance of the assignee's future performance of its obligations to the requesting party under the Contract.
If — for any reason or no reason — the assignee does not provide such reasonable assurance within 30 days after the effective date of the requesting party's notice, then within 30 days after the end of that 30-day period, the requesting party may terminate the Contract — on a going-forward basis only — effective immediately upon notice of termination to the assignee. (The notice of termination may be part of the notice requesting reasonable assurance.)
The requesting party's right to reasonable assurance under this Option will expire automatically if the requesting party's notice requesting reasonable assurance has not become effective (see Clause 6.9) on or before the date 30 days after the requesting party learns, via any means, of the assignment.
Termination under subdivision c above will be the requesting party's EXCLUSIVE REMEDY for the assignee's failure to provide reasonable assurance — but without prejudice to any claim by either party for other breach of the Contract.
If the assignee and the requesting party disagree about whether the assignee's assurance, if any, was reasonable, then the assignee and the requesting party will escalate the disagreement as provided in Clause 6.4.
Comment
Assignee reasonable assurance requirement: This Option 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.
Consider this hypothetical situation:
Two parties, "Fred," a supplier, and "Ginger," a customer, sign a contract. (This intentionally evokes Fred Astaire and Ginger Rogers — and also usefully has an alphabetical sequence.)
Fred later assigns the contract to a third party, "Harry." (Another alphabetical progression.)
But Ginger isn't totally comfortable that Harry will be able to deliver on Fred's obligations under the contract.
Now, to be sure: If Harry did fail to perform Fred's obligations, then Ginger could sue both Harry and Fred for breach of the contract.
But that might be cold comfort to Ginger, who presumably doesn't want to have to deal with a breach at all: What Ginger wants is for the job to get done — properly and on time, whether by Harry or Fred — not least because if the job doesn't get done right, it might cause major problems for Ginger's business.
Moreover, in deciding to do business with Fred, Ginger might well have done some homework ("due diligence") about Fred's reliability. She might object to having to deal instead with Harry, about whom she might know little or nothing.
Oh, sure: An assignment-consent requirement would be one way for Ginger to address that concern: Ginger could insist on including a provision in the contract, saying that Fred simply isn't allowed to assign the contract to Harry without Ginger's consent.
But: An alternative to a consent requirement might be for Ginger to request "reasonable assurance" from Harry that Harry will actually be able to deliver.
So, this Option could be a useful tool for Ginger to test whether Harry is likely to present more of a business risk than Ginger is comfortable with.
8.5.10. Option: No Payment For Assignment Consent
The Reviewer is not to ask for payment, no matter how labeled, from the Assigning Party (nor from any other party) in return for consent to assignment.
Comment
No payment for assignment consent: This Option addresses situations like that of a high-profile, politically-sensitive case: The Port of New York and New Jersey insisted on a $10 million consent fee — plus a commitment to invest $40 million in improvements to terminal operations — in return for the Port's consent to an assignment of a lease, as reported in the New York Times, also discussed at 8.4.8.
Caution: This Option might not be worth much to an Assigning Party as a practical matter, because a Reviewer could "play chicken" and drag its feet while claiming that it was not "ask[ing] for" payment — moreover, even proposing this Option might be poking the bear, which the Assigning Party might not want to do.
8.5.11. Option: Deemed Consent After Deadline
The Reviewer will be deemed to have consented to an assignment by the Assigning Party if the Reviewer has not responded otherwise within ten business days after the Reviewer has received a written request for consent from the Assigning Party.
If, however, the Reviewer makes a reasonable request in writing to the Assigning Party for more information about the proposed assignment, then that request will "stop the clock," for a reasonable time, so that the Reviewer can review the information.
Comment
Deemed consent to assignment after deadline: This Option compromises between the parties' interests; for a real-world example, see an Eleventh Circuit decision where the court upheld a patent owner's refusal to consent to assignment of an exclusive license agreement, in part because the licensee didn't provide the patent owner with the requested additional information. See MDS (Canada) Inc. v. Rad Source Tech., Inc., 720 F.3d 833, 850 (11th Cir. 2013), affirming in part822 F. Supp. 2d 1263 (S.D. Fla. 2011).
8.5.12. Option: No Transfer of Consent Right
The Assigning Party need not obtain consent to assignment from a successor or assignee of the Reviewer.
Comment
No transfer of right to consent to assignment: When one party has the right to consent to — as in, veto — another party's assignment of the contract, an implicit part of the underlying bargain might be that the veto right would be exercised by the original party, not by some unknown future successor. • Caution: A prospective Assigning Party might still be restricted by law in its ability to assign the contract (see 8.4.4).
8.6. Background Checks
It's not unusual for a customer to want its service providers to run background checks8.6.7 on the service providers' key personnel. The goal is normally to identify people with criminal records, drug problems, or other indicia of potential trouble that could cause problems for the customer.
a party indicated in the Contract — referred to for convenience as the "Provider" — is to follow this Clause in connection with the performance of "Critical Activities" and/or "Restricted Activities" (those terms are defined below); and
both parties are otherwise to follow this Clause as indicated.
Comment
Why use the term "Provider"? This Clause is designed for general usage, so we need to define the parties' respective roles; for convenience, we use the defined term Provider 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 do so 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.
Pro tip: If you're copying this language for use in a contract, consider indicating which specific parties are the Provider and the Customer — but use those defined terms anyway, so that you don't have to change them everywhere in this Clause.
8.6.1.2. Whose backgrounds are to be checked?
The Provider will have commercially-reasonable background checks conducted, in advance, on each "Specified Individual" — that term refers to each employee of the Provider (and of the Provider's contractors, if any), who will be performing one or more:
"Critical Activities" and/or
"Restricted Activities," each as defined below.
Comment
Limiting the universe of people to check: It likely won't make sense to require background checks for everyone working for the Provider in connection with the contract.
8.6.1.3. What individuals would not need checking?
Here, the term "Specified Individual" does not include any employee:
of the Customer; or
of any licensee, invitee, or other contractor of another party specified in the Contract, referred to for convenience here as the "Customer."
Comment
No checks on Customer employees, etc.: It wouldn't be good to have a situation where the Customer — after the fact — claimed that one of its own employees, customers, etc., was a Specified Individual and therefore should have been background-checked by the Provider. That's because presumably the Customer would already have done background checks on its own employees, etc., to the extent that the Customer deemed it necessary.
8.6.1.4. What would count as a "Critical Activity"?
For purposes of this Clause, the term "Critical Activity" refers to any activity under the Contract, where the activity is expected to involve one or more of the following:
access to one or more of the Customer's computer systems; data; or confidential information;
the possibility of death or bodily injury to any employee, contractor, customer, licensee, or invitee of the Customer; and/or
the possibility of significant loss of (or other significant damage to) tangible or intangible property of the Customer.
Comment
Critical Activity definition: Some parties might want to customize this baseline specification.
8.6.1.5. What would count as a "Restricted Activity"?
For purposes of this Clause, the term "Restricted Activity" refers to any activity that, in the context of the Contract:
entails access, by the Specified Individual, to premises, equipment, employees, suppliers, and/or customers, of the Customer; but
does not rise to the level of a Critical Activity.
Comment
Why define "Restricted Activity"? Sometimes the Customer might want background checks done for people doing more than just Critical Activities. Toward that end, this definition of Restricted Activities is provided for drafter convenience, in case it'd be useful to have a separate category of activities that are of a less-sensitive nature than Critical Activities.
Comment
Access to Customer premises, etc.: Some drafters might want to expand this subdivision to encompass loss or damage to third parties' property, and/or to economic loss.
8.6.1.6. What consultation with the Customer is required?
Before staffing any individual to any Critical- or Restricted Activity, the Provider will consult, in advance, with the Customer in any case where prudence would suggest further inquiry — including in the specific cases mentioned below.
Comment
Consultation with Customer about background-check results: This Clause tries to strike a balance between safety and flexibility: It doesn't give the Provider carte blanche to use potentially-problematic individuals, but neither does it give the Customer an absolute veto.
(Of course, the Provider wouldn't be relieved of its responsibilities under the Contract just because the Customer did or didn't object to one or more of the Provider's staffing proposals under this Clause.)
8.6.1.7. What Restricted-Activity restrictions apply?
The Provider will not staff any individual for any Restricted Activities if the Customer timely objects on reasonable grounds.
Comment
Restricting staffing: Here, the terms timely and reasonable are intentionally vague, to encourage the parties to work together cooperatively.
8.6.1.8. What Critical-Activity staffing restrictions apply?
possible drug abuse, 8.6.5then the Provider will not staff that individual for Critical Activities without the Customer's express prior written consent.
8.6.1.9. Who pays background-check expenses?
Expenses of background checks under the Contract are the responsibility of the Provider — and the Provider will not ask the Customer (or its affiliates or its people) for reimbursement for such expenses without prominently pointing out, in the request, that the expenses are not reimbursable.
Comment
No request for reimbursement: This is designed to make it a breach for the Provider even to ask for reimbursement — because the Provider might be tempted to ask for reimbursement in the hope that the Customer's accounts-payable people wouldn't notice the discrepancy and instead would just pay.
8.6.1.10. Provider's indemnity obligation
The Provider will defend and indemnify the Customer and its Protected Group from any claim — by any third party — where the claim arises from the conduct of any background check covered by this Clause.
Comment
Indemnity obligation — why? If the Provider were to screw up a background check on an individual (e.g., if the Provider 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 Provider, 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 8.6.8.
Comment
Indemnity against "any" background-check claims: The claims requiring defense and indemnity would include, for example, any claim that alleges one or more of the following:
failure to obtain any required consents from the Specified Individual;
failure to comply with any applicable privacy laws;
failure to comply with any applicable notification requirement (for example, in credit-reporting laws) that a Specified Individual must be notified before or after a decision is made using information learned in the background check; and
any other alleged violation of of law by the Provider or its agents in respect of the background check.
Comment
Indemnity – possible third-party claimants: The third parties referred to here would include, without limitation, governmental authorities.
Comment
Indemnity insurance?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 3.10.
8.6.1.11. Escalation of disagreements
At the request of any party, each party will escalate any dispute about the Provider's staffing proposals under this Clause:
first, internally to each party's respective supervisors, 6.5
followed if necessary by escalation to a neutral adviser. 6.4
8.6.2. Background Checks Short-Form Clause
(a) Whenever [fill in party name] (the "Provider") assigns personnel for potentially-sensitive activities under the Contract (as defined in subdivision (b) below), the Provider is to 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 Contract, the Customer's suppliers and customers.
Comment
Background-checks short form: For easier copying-and-pasting, this short-form clause is condensed into a single paragraph — even though it comes close to violating the Pasta Rule (30.3) by almost being a "spaghetti clause" instead of a "macaroni clause."
8.6.3. Option: Credit Check Requirement
The Provider will cause each background check required under the Contract to include standard credit reporting from all major credit bureaus serving the jurisdiction in question.
Comment
Credit checks — caution: Credit checks are subject to considerable regulation, as discussed at 8.6.8; noncompliance has hit some well-known companies with sizable settlement payouts such as Gettings et al. (2015) (Chuck E. Cheese — $1.75 million) and Lebowitz (2014) (Publix — $6.8 million).
8.6.4. Option: Criminal-History Check Requirement
The Provider is to cause each background check to include a check for substantial evidence that the Specified Individual has ever engaged in any of the following:
any felony;
violence of any kind, including but not limited to sexual violence;
child- or elder abuse;
materially-deceitful conduct, including but not limited to fraud; and/or
acts of moral turpitude.
Comment
Criminal activity — substantial evidence requirement: Note that this Option doesn't refer to a criminal conviction, because [BROKEN LINK: bkgd-chk-flag][BROKEN LINK: bkgd-chk-flag] requires only consultation with (or, at most, consent of) the Customer if a criminal-history concern is revealed. See the extended discussion of this subject at 8.6.9.
8.6.5. Option: Drug Concern
The Provider is to cause each background check to include a check for substantial evidence suggesting that the Specified Individual makes use of one or more of the following:
illegal drugs;
alcoholic beverages to excess; and/or
prescription drugs other than in accordance with a lawfully-issued prescription.8.6.10
8.6.6. Option: Contact-Information Sources
When checking with a personal reference provided by a Specified Individual, the reference's contact information is to be obtained from a source independent of the Specified Individual.
Comment
Independent-obtained contact information can help guard against the possibility that an applicant might provide a checking party with fake contact information for references. • Relatedly: See also 11.9 (benefits of getting confirmations from third parties).
8.6.7. Some possible categories of background check
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.
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).
8.6.8. Credit checks have to be done "by the numbers"
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.
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).
8.6.9. Criminal-history checks
• 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.
• A criminal-history check would typically include a nationwide check of records of arrests, convictions, incarcerations, and sex-offender status.
• Drafters could consider whether to ask a subject to submit fingerprints to confirm the subject's identity (and guard against imposters).
• Caution: The U.S. Equal Employment Opportunity Commission (EEOC) has 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 has also taken 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).
At this writing (April 2025), it's unclear to what extent these EEOC policies will be continued, in view of President Trump's various executive orders affecting the EEOC and its mission.
• Caution: In addition, some states — and even 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).
• Caution: 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.
• Depending on the duties to be assigned, even the use of legal drugs might be a cause for concern — for example, an individual taking certain prescription medications might be unsuited to drive a bus or other commercial vehicle. (This is still-another area where language might need to be fine-tuned to fit the parties' needs.)
For obvious reasons, if a background check indicates that a person might have a drug-misuse problem, then tighter restrictions would appropriate, when it comes to using the person for critical activities, than for other restricted activities.
• Pro tip: Companies might consider the possible effect on employee morale of asking them to take a drug test – and about 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.)
8.6.11. 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? 8.21.10.1
8.6.12. 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.
8.7. Blue-Pencil Request
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.
When this Clause is agreed to, it will apply in any situation in which a court, agency, arbitation panel, or other tribunal of competent jurisdiction (the "Tribunal") holds that a provision of the Contract is invalid, void, or otherwise unenforceable.
8.7.1.2. What are the parties asking for here?
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.
8.7.2. Will courts go along with a blue-pencil request?
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 .
In some other jurisdictions, courts will refuse to engage in blue-penciling of a contract even if contract specifically authorizes it, saying in effect, You people should have drafted the contract correctly; don't expect us to fix your mistake. Example: In 2024, Delaware's supreme court declined to write a bright-line rule one way or another about blue-penciling, but upheld a chancery-court refusal to blue-pencil the noncompetition and nonsolicitation covenants in question. Sunder Energy LLC v. Jackson, No. 455, 2023 slip op. at text accompanying n.128 (Del. Dec. 10, 2024).
8.7.3. Why "request" or "direct" the tribunal?
In section [BROKEN LINK: blue-agr], 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 8.2.35.)
• In contrast, parties to a contract can't "direct" a court to do anything, as discussed at 30.14.
8.8. Board Definition (board of directors)
8.8.1. What does board mean in the Contract?
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.
Comment
A. 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.
B. In some situations, a contract between a company and an investor might give that investor the right, by contract, to appoint a certain number of members of the company's board.
Example: Consider a startup company that succeeds in attracting investment from a venture-capital firm. It's very common for the investment contract between the company and the VC firm to give the VC firm, as part of the deal, the contractual right to appoint at least one member of the startup's board (to keep an eye on things). This can come into play in determining affiliate status, as discussed at Clause 7.2.
This Clause will apply if, in any action relating to the Contract, either party (referred to here as the "Movant") applies to a court or other tribunal for a preliminary injunction, temporary restaining order, or similar interim relief against another party (the "Respondent").
Comment
A. Motivation: 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.
B. This Clause 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.
8.9.2. What are the potential defendants agreeing to here?
By entering into the Contract, the Respondent WAIVES any requirement that the Movant post a bond, or other security, as a prerequisite to obtaining the requested interim relief.
8.10.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 athttp://goo.gl/ak7Mt (books.google.com).
Incidentally, this Clause 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).
8.10.2. A hypothetical example
Consider this hypothetical situation: 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 10.5).
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.
8.10.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 movant successfully obtains a preliminary injunction forbidding the respondent from doing whatever is upsetting the movant.
This interferes greatly with the respondent's business — possibly even putting the respondent 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 the respondent had previously waived the bond requirement, then the respondent would have no recourse for the wrongful injunction.
Of course, a court might not give effect to a contractual bond waiver. Example: In a 2023 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. 2023, aff'd w/o opinion) (footnotes omitted).
But as the saying goes, hope is not a plan — it might be a considerable business risk to count on a court's disregarding a bond waiver.
This Clause will govern in any case where one party to the Contract (the "Business Associate") will be a "business associate" of another party to the Contract (the "Covered Entity") under 45 C.F.R § 160.103.
Comment
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).
8.11.2. The HHS Model BAA is adopted — with certain modifications
the parties will 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"), which is incorporated by reference into the Contract — as modified by this Clause.
Comment
A. Motivation: Adopting the HHS Model BAA — instead of reinventing the language wheel — should help the parties speed up their legal review and get to signature sooner.
B. 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.
8.11.3. How are notices to be given?
Notices under the HHS Model BAA will be 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).
Comment
This "Three Rs" approach is borrowed from Clause 6.9, because the HHS Model BAA's notices provision (section 18) is kind of open-ended.
8.11.4. Can de-identified PHI be used?
This section applies to "de-identified" (a.k.a. "anonymized") personal health information ("PHI"), namely information that cannot practicably be used to identify any individual nor obtain any individual's personal health information.
Unless clearly agreed otherwise, the Contract does not prohibit the Business Associate from using and/or disclosing anonymized PHI that the Business Associate obtains and/or creates under the Contract.
A reminder: De-identified personal health information is not the same as aggregated PHI, which is not addressed by this Clause.
Comment
A. Motivation: 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).
B. Subdivision b: Note the limited language, "the Contract does not prohibit" particular actions — the language does not say that the Business Associate "may" or "is entitled to" do the referenced things, because applicable law might impose other restrictions on such actions.
the parties will arrange for a catch-up call whenever either party reasonably requests it, e.g., to deal with problems and/or ‑opportunities (existing or anticipated).
When so agreed, the parties will schedule regular calls as calendar placeholders.
Comment
A. "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; see 8.13 for more on this subject.
B. This Clause could be thought of as a "no-ghosting" rule.
C. Pro tip: Monthly or even weekly pre-scheduled calls might be appropriate, perhaps with different schedules for different operational phases in the parties' dealings.
8.12.2. How are catch-up calls to be conducted?
Each catch-up call is to be conducted by video conference unless otherwise agreed.
The party requesting the call may choose a video-conferencing platform as long as that platform is reasonably available to the other party (or parties).
Comment
Presumably parties will be able to agree on that much, even if their relationship is becoming hostile.
8.12.3. Who is to participate in the call?
For each catch-up call, each party is to have appropriate people participate.
Comment
There seems to be little purpose for a hard-and-fast rule about required participants, because that will vary greatly with the parties and the situation.
8.12.4. What will the agenda be?
On the call, unless otherwise agreed, the parties will follow the SPUR Agenda — Status, both good and bad — things done, and left undone; Plans, including contingency plans where relevant; Uncertainties, for example unknowns and untested assumptions; and Risks, both downside and upside.
The parties are encouraged to circulate agenda items for the call in advance.
Meeting minutes are not required, but circulation of some sort of written record of the discussion is encouraged.
Comment
It's often useful for one or more parties to prepare and circulate a readout (see 23.1) of what the sending party regards as noteworthy points discussed on the call.
8.12.6. What if agreements are reached on the call?
If, during the call, the parties agree to modify or waive any provision of the Contract, they are to follow Clause 6.1 (amendments) and/or Clause 8.68 (waivers), as applicable.
8.13.1. Communication is key to reliable relationships
♫ Wouldn't it be nice to work together? ♫ 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; deal with disagreements and other adversities together; and with any luck, start to develop trusted, collegial relationships.
Timely communication is key to such relationships.
8.13.2. Tragedy can result from lack of communication
The single biggest problem in communication is the illusion that it has taken place. (Mis?)attributed to George Bernard Shaw.
In the world of contracts, parties not communicating has often resulted extra expense and even disastrous problems.
– General contractors that build skyscrapers.
– Surgical teams that do complex operations.
– Pilots that fly airliners and other aircraft.
All of those professionals are trained in lessons of history that are "written in blood," as pilots sometimes say.
Outcomes can be greatly improved — and sometimes, catastrophic failures averted — by pre-planned habits of communication.
The world has seen tragic examples of failures in this regard:
All were caused at least in part by communications failures.
Example: By comparison, here's an almost-trivial 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.
The prime contractor refused to pay the extra money; the sub sued the prime for payment — and lost.
During the trial, the 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 litigating the sub's claim for payment. 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).
8.13.3.Structured communications can help — sometimes, a lot
The importance of structured communication is a subtext of Dr. Atul Gawande's 2009 book, The Checklist Manifesto (highly recommended reading, by way). That book grew out of Dr. 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).
Dr. 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.
At 65-66; emphasis, extra paragraphing, and bullets added.
To be sure: In many contracts such intensive communication would often be costly overkill.
But anyone with much experience "in the field" would probably tell you that in the contract world, the problem is usually too little communication.
This Clause will govern if and when, in the Contract or otherwise, one party (referred to for convenience as the "Customer") prescribes a code of conduct (the "Code") that is to be followed by another party (the "Supplier").
For emphasis: This Clause will govern:
even if the Code has a different title such as "policy manual" or "supplier handbook"; and
even if the Code takes the form of, or is derived from, a general industry standard or practice.
Comment
A. Motivation: A customer might demand that its supplier contractually commit to abiding by a "code of conduct." Some customer codes of conduct can be overreaching and overbearing — possibly trampling on the supplier's legitimate interests and giving the customer unfair leverage in unrelated disputes.
B. So: This Clause 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.
C. See also Clause 5.9, addressing termination for reputation risk.
8.14.2. What if the Contract and Code don't match?
This Clause will take precedence over any inconsistent provision in the Contract or the Code.
As one, non-limiting example of subdivision a: Even if the Contract or the Code requires the Supplier to strictly comply with the Code, it would be enough for the Supplier to do as stated in this Clause.
The parties are encouraged to consult with each other if an issue comes up that might implicate the Code.
Comment
This subdivision is one of the "Pick up the phone!" provisions designed to try to identify and resolve potential disputes as early as possible.
8.14.3. Must the Supplier always comply with the Code?
The Supplier is entitled to not comply with some or all of the Code if one or more of the following are true:
the Customer does not require such compliance by the Customer's other suppliers and relevant counterparties generally; see below concerning confirmation of this point; or
the Supplier reasonably concludes that compliance with the Code would require breaking the law (or running any significant risk of doing so); or
the Code deviates unreasonably from standard business practices in the relevant line of business; or
the Customer does not provide the Supplier with the Code — in writing — on a timely basis. (A direct, "jump cite" link to a publicly-available document would suffice.)
Comment
A. Motivation: This section 8.14.3 provides specific "off ramps" for suppliers that would find it too burdensome to comply with particular requirements of customers' codes of conduct.
B. 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 the Code, then that gives the Supplier more leverage in pushing back against being forced to comply with it.
C. Subdivision 2: The term "reasonably concludes" qualifier is vague but should get the parties talking.
D. Subdivision 4: Just what would constitute a "timely" basis 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 demands that Supplier 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 the lawyer online forum redline.net.)
8.14.4. Can the Supplier verify what the Customer says about its Code?
At reasonable intervals and upon reasonable notice, the Supplier may have an independent firm of certified public accountants (CPAs) do the following in accordance with Clause 2.3 (audits and inspections, with confidentiality obligations):
inspect a representative sample of the Customer's other relevant contracts from time to time; and
report to the Supplier whether or not the Customer does in fact contractually require agreement to the Code by the Customer's relevant counterparties generally.
Comment
The Customer might be tempted to say to the Supplier, 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 8.37).
8.14.5. What would constitute "sufficient" Code compliance by the Supplier?
As a safe harbor, the Supplier will be deemed to have complied with the Customer's Code if, when reasonably requested by the Customer, the Supplier timely does the following:
conducts a reasonable review of the Code;
gives good-faith consideration to whether the Supplier's business practices are a "fit" for the Code (or could reasonably be adjusted to be a fit); and
consults with the Customer about any particular business-related practices that the Code indicates the Supplier is to follow (or not follow).
Comment
A. Motivation: 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.
B. 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 Clause, that's likely to be preferable to spending time negotiating about unlikely — or unknowable — future events.
8.14.6. Code agreement is not a general representation
For emphasis: The Supplier's agreement to follow the Customer's Code is not a representation or warranty that all of the Supplier's relevant business practices would necessarily meet (or have met) with the Customer's approval.
Comment
This is a roadblock clause to try to dissuade "creative" 20-20 hindsight arguments by litigation counsel.
8.14.7. The Customer may terminate for Code violation
This section will apply if the Supplier does not cure a noncompliance with the Customer's Code within a reasonable time after the Customer calls the Supplier's attention to the noncompliance — by notice, or otherwise — via any reasonable means.
In that situation, the Customer may terminate the Contract — but on a going-forward basis only — by giving the Supplier notice to that effect.
Comment
A. Motivation: This termination right addresses what the Customer often really wants, which might be simply the ability to announce that the Customer has cut ties with the Supplier; this has been seen this in cases involving, for example, Kanye West and Kevin Spacey.
B. Subdivision a: As to a "reasonable" cure period, in some circumstances that might be no cure period.
Comment
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.
Similarly, in a 2024 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 percent 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).
8.14.8. May the Customer sue the Supplier for a Code breach?
Other than termination as set forth above, the Customer is not to take any other action against the Supplier for breach of the Code unless one or more of the following is shown:
the Supplier's action (or inaction) that failed to comply with the Code also constituted a breach of the Contract apart from the Code; and/or
the Contract as negotiated by the parties — not just the Code, and not just the Contract in a form that the Customer provided, e.g., in the fine print of a purchase order form — clearly and specifically says that the Customer may sue the Supplier for breach of the Contract even if the Supplier breaches only the Code.
For emphasis: The prohibition of subdivision a extends (without limitation) to the Customer's doing any of the following in response to the Supplier's noncompliance with the Code:
filing suit against the Supplier;
demanding arbitration; and/or
withholding payment that would otherwise be due.
By entering into the Contract, the Customer WAIVES, and therefore must not seek, any recourse for the Supplier's noncompliance with the Code except as clearly stated in this Clause.
Comment
Motivation: This language seeks to balance the parties' legitimate interests.
Subdivision a.2 allows the parties to override this exclusive-remedy provision, but they have to be both very intentional and very clear about it.
Subdivision c: The "must not seek" phrase above 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 Contract, for which the Supplier's damages would include attorney fees for contesting the Customer's attempt.
8.14.9. Would Customer's Code termination right ever expire?
The Customer's right to terminate under this Clause will expire automatically if the Customer's notice of termination to the Supplier has not become effective in accordance with Clause 6.9 on or before the earlier of the following:
the date 60 days after the date that the Supplier first became aware, by any means, of the earliest event putatively constituting the Code breach (the "Triggering Event"); or
if earlier, the date six months after the date of that Triggering Event, regardless when, or whether, the Customer learned or should have known about it.
Comment
Motivation: A termination deadline seems fair, so that the Supplier 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 the Customer has been able to tolerate the Supplier'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.
8.14.10. Would Code termination kill other rights, etc.?
If the Customer terminates for Supplier noncompliance with the Customer's Code, the termination will not affect any party's other accrued rights and obligations under the Contract, including without limitation the following — if any:
the Customer's warranty rights; and
the Supplier's payment rights for already-completed sales.
For emphasis: The parties' (canceled) future rights and obligations would include, for example, the following — if any:
any post-termination right of the Customer to purchase goods or services from the Supplier at stated pricing or at a stated discount; and/or
any post-termination obligation of the Customer to buy goods or services from the Supplier during any particular time.
8.14.11. Survival of this Clause
If the Customer does terminate for a Code breach, then this Clause will continue in effect as stated in Clause 5.1 (survival) except as specifically provided in this Clause.
8.15. Codes of conduct compliance: Notes
8.15.1. How might a customer's code of conduct be a problem?
For the supplier, managing compliance with many customers' different codes can be a pain; here are a few specific potential concerns:
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.
8.16.1. Why do drafters use commercially reasonable efforts?
Contract drafters often use the term commercially reasonable about, e.g., an efforts requirement:
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;
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 Clause 7.7).
8.16.2. Problem: The lack of clarity in the case law
In a 2024 Delaware 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, 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).
8.16.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 commercially reasonable 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).
8.16.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).
8.16.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.
Emphasis in original, extra paragraphing added.
8.16.6. Pro tip: Agree to a process instead?
Outside of the context of efforts, a party seeking to prove (or disprove) the commercial 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 a 1990 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 Clause 6.4.
8.16.7. Whose burden is it to justify a definition?
A party that sues for breach of a commercially-reasonable-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).
When this Clause 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").
This Clause itself does not authorize anyone to access any Host System, but only states ground rules for any such use.
Comment
A. This Clause draws on numerous online "terms of service" such as, for example, Amazon's AWS agreement (which might have changed since this writing).
B. Caution: This Clause isn't intended as a "code of conduct"; were it otherwise, and if Clause 8.14 were also agreed to, then the remedies for breach of this Clause would be limited — and that's not the intent here.
8.17.2. Definitions
For purposes of this Clause:
"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 are not exclusive examples.)
"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.
For easier reading, Users might sometimes be referred to here as "Accessing Party Users" or "the Accessing Party's Users."
Comment
Subdivision a: 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, Digital Ocean, etc.
8.17.3. Basically, what must the Accessing Party do?
The Accessing Party is to see to it that the Accessing Party's Users comply with this Clause — this is to include, for example, appropriately instructing those Users in their obligations under this Clause.
The Accessing Party is to Defend and indemnify the Host and its Protected Group from any harm arising from use, by any of the Accessing Party's Users, of any Host System, where the use did not conform to the requirements of the Contract (including but not limited to this Clause).
Comment
Subdivision a: The Accessing Party might be responsible anyway for its Users' actions, under the legal doctrine of respondeat superior, but it's useful to spell it out in the Contract so that the Accessing Party will see it without having to go to the law books.
8.17.4. Users' sign-up information must be accurate
This section will apply whenever a User and/or the Accessing Party are asked to provide a Host System with sign-up about one or more Users.
The Accessing Party is to ensure:
that all such information is complete and accurate; and
that any identity-verification information submitted by or for any User is authentic (for example, proof that the User actually is who the User purports to be).
Comment
Subdivision b.1 doesn't require sign-up information to be provided, but it's certainly possible that the Host System might not allow access if signup information isn't provided.
Students: Note the use of the term "complete and accurate" instead of "true and correct" (see 25.5).
8.17.5. Unreasonable use is prohibited
Each User must strictly avoid unreasonable use of any Host System, such as, for example, those listed at section 8.17.10.
Comment
Of course it's hard, in advance, to define "unreasonable" use of a Host System; the cited section lists numerous examples.
8.17.6. Prudent malware protection is required at all time.
Each User must maintain prudent malware protection for any laptop, workstation, smartphone, tablet, terminal, etc., with which the User accesses any Host System.
The obligation of subdivision a is not limited to times when the User is actually accessing a Host System.
Comment
Subdivision a: 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 b: This malware protection obligation takes into account that at any time, "sleeper" malware could infect the User's equipment , even when not accessing a Host System; hence, this requirement applies at all times.
8.17.7. Users must comply with other rules as well
Each User must comply with the following at all times while accessing any Host System:
this Clause;
Clause 8.63 (site visits), because Host-System access is considered one kind of site visit;
any other relevant provisions of the Contract;
normal professional standards of conduct for host-system usage;
any other usage policies of the Host that get timely communicated to the User — which might happen orally and/or in writing, and maybe on an ongoing- and/or as-needed basis, instead of inundating the User with all the policies at once; and
privacy-related laws and Host rules concerning personal information accessible via any Host System.
Comment
No point in reinventing the wheel here.
8.17.8. The Host may monitor 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:
monitoring the User's access to any Host System;
having a third party engage in such monitoring; and/or
temporarily- or permanently suspending the User's access in case of suspected- or demonstrated violation of this Clause.
8.17.9. Special rules for U.S. Government Users
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.
The Host System is made available to that 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).
Comment
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).
Subdivision a — "in the User's capacity": This takes into account the case where a government employee is 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 your author is hard-pressed to think of any.)
8.17.10. Appendix: Some probably-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):
deception;
defamation — commonly understood as including libel (written defamation) and slander (oral defamation);
illegal activity, including but not limited to deployment of ransomware and other theft;
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;
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);
knowing or reckless introduction of malware, including but not limited to bots, corrupted files, crawlers, hoaxes, keystroke recorders, ransomware, Trojan horses, and viruses;
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;
obscenity according to the standards in the geographic community where the User accessed the Host System;
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
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;
allowing anyone else to access the Host System using one's own access credentials;
using someone else's credentials to access the Host System;
impersonating someone else in connection with the Host System;
establishing multiple user accounts to engage in one or more prohibited;
falsely pretending to represent another individual or entity in connection with the Host System;
accessing anyone else's information stored on the Host System without proper authorization;
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;
engaging in spoofing, for example, disguising the origin of any transmission sent via the Host System or any network associated with it;
interfering with anyone else's use of the Host System;
selling or leasing access to the Host System;
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.;
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 User's own content, or (ii) as expressly authorized in writing by the Host or other owner of the content;
otherwise infringing anyone else’s copyright, trademark, trade secret, or other intellectual property right in the course of using the Host System;
disassembling, decompiling, or otherwise reverse-engineering any aspect of the System;
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;
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;
attempting to do something prohibited by the Contract, whether or not the attempt is successful;
inducing, soliciting, allowing, or knowingly helping anyone else to do something prohibited by the Contract, whether for the User's own benefit or otherwise.
8.18. Confidential Information Clause
Many contract professionals would agree that among the most-used types of contract, confidentiality agreements — a.k.a. "nondisclosure agreements"† [sic], commonly referred to as "NDAs" — rank near the top. That's likely because many businesses regularly exchange confidential information: and as discussed at 8.18.15, without a confidentiality agreement in place, such an exchange could destroy any trade-secret rights available for the information. Moreover, quite a few other types of contract include provisions requiring one or both parties to maintain the confidentiality of another party's information.
† The name "nondisclosure agreement" is a bit misleading because NDAs almost invariably include nonuse obligations as well as other prohibitions and restrictions.
This Clause sets out confidentiality obligations of a "Recipient" with respect to certain information of a "Discloser"; both of the quoted terms are defined below.
Comment
See also: • Business associate agreements (8.11): Required by law in certain cases involving protected health information; • Export controls (13.11): Legal restrictions on disclosing certain categories of information, with possible criminal penalties for violation; • Privacy laws (7.39).
8.18.2. "Recipient": Which party will have confidentiality obligations?
The confidentiality obligations of this Clause bind each "Recipient" — that term refers to any party to the Contract that:
has clearly agreed — which could be in the Contract itself, or otherwise — to abide by the confidentiality obligations of the Contract for "Confidential Information" (see section 8.18.5) of a "Discloser" (see section 8.18.3); and
accesses such Confidential Information in connection with the Contract.
Comment
We say nothing here about the Discloser's owning 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).
8.18.3. "Discloser": Which party's information is potentially protectable?
For any given Recipient (as defined above), the term "Discloser" refers to each other party to the Contract unless the Contract clearly indicates otherwise.
Comment
One- or two-way NDA — a reverse approach: For reasons explained below, this reverses the usual approach to drafting: We don't first define Discloser and then Recipient. Instead, we define Recipient as a party that has agreed — in the Contract, or otherwise — to treat particular information in confidence. Only then do we define Discloser.
8.18.4. Each party could theoretically be a Recipient.
If the Contract states that each party is a Recipient, then: By entering into the Contract, each party has clearly agreed as provided above.
Comment
This Clause intentionally defines Recipient and Discloser so that this Clause 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, to guard against inadvertent disasters later, as discussed at 8.20.6.3. (See also 30.6 concerning two-way agreements generally.)
8.18.5. Definition: Confidential Information
The term "Confidential Information" refers to any information where all of the following are true:
the information has been, and continues to be, the subject of reasonable measures 8.19.12.3 by the Discloser to keep the information secret;
the information was initially made available to the Recipient during the "Disclosure Term," defined below;
the information was initially made available to the Recipient under the Contract, as opposed to in the course of other business dealings between the Discloser and the Recipient; and
the information is not within one or more of the exclusions below.
Comment
A. Source note: This definition of Confidential Information is adapted from the (U.S.) Defend Trade Secrets Act (DTSA), 18 U.S.C. § 1839(3); the DTSA 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., Morrison (JDSupra.com 2016).
B. For an overview of possible security measures for Confidential Information, see 8.19.12.3.
C. Some drafters — not including your author — also like to include a long "laundry list" of specific categories information that can qualify as confidential information. There's arguably little need — or none at all — for such a list, given the breadth of the definition of Confidential Information in this Clause, because:
Such a list marginally increases the workload for readers and thus can slow up the contract-negotiation process; and
There's always the risk that the Recipient could 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.
For those drafters who do like to include such a list, see the following footnote.29
D. Made available under the Contract: If you're a Recipient, you wouldn't want to be ambushed by a claim that other information of the Discloser — made available to your people in contexts outside the parties' dealings under the Contract — was somehow subject to the confidentiality obligations of the Contract.
8.18.6. The Protected Disclosure Term is one year.
For particular Discloser information to be protectable under this Clause, the information must be initially made accessible to the Recipient during the "Disclosure Term," which:
begins upon the effective date of the Contract — which could be before the effective date of the Contract if the Contract states that the parties are confirming a prior confidentiality agreement, for example, an oral agreement; 8.19.12.2 and
ends on the date the stated time afterwards.
Comment
A. If you're a Discloser, you'll want to make sure the Disclosure Term (defined below) will last long enough for your business objectives — because if you first disclose particular information after the Disclosure Term ends, it might be impossible for you to convince a court that the Recipient was bound by confidentiality obligations for that information.
B. Consider whether to "backdate" the Disclosure Term to cover previous oral confidentiality agreements, as discussed at 8.19.12.2.
8.18.7. Marked information is presumed to be confidential.
If the Recipient gains access to particular Discloser information that is marked, with appropriate prominence, as confidential, then the Recipient is to provisionally treat the information as Confidential Information until such time (if any) as the information is shown to come within one of the exclusions beginning at section [BROKEN LINK: conf-info-excl-indep] below.
Comment
Concerning marking, see the discussion at 8.19.12.1.
8.18.8. Catch-up marking is allowed (within limits).
If the Discloser wants to retroactively mark previously-unmarked information as confidential, then the Discloser must, within a reasonable time:
provide the Recipient with a marked written version of the information (this could be a reasonably-detailed written summary); and
give notice to the Recipient that the Discloser has sent the marked written version.
Comment
A. Background: Sometimes marking simply falls through the cracks. Moreover, the Discloser might make some confidential 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. For situations like those, this Clause provides a compromise, as is appropriate to a cooperative party relationship.
B. Subdivision 2's notice requirement serves both (1) to alert the Discloser about the catch-up marking, and (2) to create a paper trail about it.
8.18.9. Other parties' information can be confidential.
If the Discloser gives the Recipient access to particular information of third parties (including but not limited to information of Discloser affiliates), then the Recipient is to treat that information as Confidential Information if both of the following are the case:
reasonable people in that position would recognize that the information might qualify as Confidential Information; and
the information is marked, with reasonable prominence, as being confidential — this is to help ensure that the Recipient and its people are alerted about their obligations for the non-Discloser information.
If (i) the Discloser provides information of any third party to the Recipient, and (ii) the Recipient becomes the object of a claim, by that third party or any other, that the Discloser was not authorized to provide the Recipient with that information, then the Discloser must defend and indemnify the Recipient and its Protected Group against that claim.
Comment
Subdivision 1 is a very-common feature of confidentiality provisions; subdivision 2, not so much, but appropriate.
8.18.10. "Secret sauce" as Confidential Information
As a reminder: When otherwise eligible, particular selections and/or combinations of items of information can qualify as Confidential Information — even if one or more of the individual items (or even each of them) are within one or more of the exclusion categories of this Clause. 8.18.10
Comment
The reader is doubtless familiar with the notion of "secret sauce," i.e., a secret selection and/or combination of known "ingredients"; here are a couple of 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).
But "secret sauce" can be more than just a marketing strategy: A number of courts have held that secret selections and combinations of non-secret information can be eligible for trade-secret protection.30
8.18.11. Other information is also presumed confidential.
The Recipient is likewise to treat particular information of the Discloser as provisionally being Confidential Information if one or more of the following is true:
The Recipient initially gained access to the information in one or more of the Discloser's own files (hard copy, digital, or otherwise); and/or
reasonable people in the relevant trade or business would recognize the information as likely to be confidential.
Comment
A. If the Discloser will be letting the Recipient see the Disclosser's own internal files, the Discloser shouldn't have to worry about achieving perfect compliance in putting confidentiality markings on everything that the Recipient might see there.
B. The terms "reasonable people" and "likely to be 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.
The term Confidential Information does not include information that the Recipient shows:
was in the Recipient's possession before the Recipient gained access to it via the Discloser, or
was provided to the Recipient by a third party without breaching an obligation of confidence benefiting the Discloser, or
was independently developed by the Recipient without referring to or otherwise using Confidential Information.
The weight to be given to the Recipient's showing on any of the points listed in subdivision 1 above is to take into account the extent to which any statements by interested witnesses are corroborated.
Comment
Concerning corroboration, see the discussion at 8.20.6.5.
8.18.13. Excluded: Published, patented, etc., information
The term Confidential Information does not include information that is, or becomes, patented, published, or otherwise publicly available.8.18.35.3 (A reminder: This is not necessarily the same thing as being "in the public domain.")
Comment
Caution: Maybe don't say "public domain"? Particular information might not be confidential, but it might still not be "in the public domain" due to:
restrictions on use of the information, for example under patent law, pharmaceutical regulations, etc.; and/or
restrictions on disclosure of the information, for example, under:
copyright law's restrictions on making and/or distributing copies of eligible "works of authorship";
The term Confidential Information does not include information that is generally known or readily ascertainable without the use of improper means, in either case by persons within the circles that normally deal with the kind of information in question.
Comment
A. Caution: It can be challenging — read: costly — to litigate whether particular information does or doesn't qualify as "readily ascertainable," as illustrated by some cases where that was an issue.
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., No. 22-2185, part II-A, slip op. at 10-12 (Fed. Cir. Apr. 4, 2025) (reversing district court's finding of date that trade secret became readily ascertainable). (Hat tip: Cynthia Abesa.)
B. Improper means: The federal Defend Trade Secrets Act, from which this definition is partly derived, gives examples of improper means (at 18 U.S.C. § 1839(6)) 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[.]" Probably to the regret of businesses, the Act doesn't seem to provide any "safe harbors" for proper means. See also the U.S. Supreme Court's comment in the (IP-)famous 1974 Kewanee Oil case: "a trade secret law, however, 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).
(For more on reverse engineering, see generally 23.4.)
Question: Would breach of a confidentiality agreement be considered "improper means" of acquiring a trade secret? Under subdivision (A) quoted above in the federal (DTSA) statutory definition, that would seem to qualify as "breach … of a duty to maintain secrecy." But the answer under state law might be different. 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).
Example: 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).
C. "Persons within the circles": This phrase "by persons 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.
8.18.15. Excluded: Information freely provided to others
Confidential Information does not include information that the Discloser makes available to one or more others without restrictions that are comparable to those of the Contract.
Comment
Caution: As discussed at 8.18.35.4, if a Discloser provides confidential information to another party without a confidentiality obligation, that will destroy any legal rights that the discloser might have to enforce confidentiality restrictions in the information.
8.18.16. Excluded: Toolkit Items
Unless the Contract clearly states otherwise, the Recipient's obligations under this Clause concerning the Discloser's Confidential Information do not extend to any concept, idea, invention, strategy, procedure, architecture, or other work (collectively, "Toolkit Item"), where all of the following are true:
the Toolkit Item was wholly- or partly created by or for the Recipient while working with the Discloser's Confidential Information; but
the Toolkit Item is not specific, nor unique, to the Discloser and its business; and
the Toolkit Item itself does not include, nor otherwise reveal or clearly suggest, the Discloser's Confidential Information.
Comment
This exclusion is useful in agreements where a customer insists that everything a service provider produces while working under contract is to be considered the customer's confidential information. The exclusion tries to strike a balance between the parties' competing interests:
When a customer for services provides its confidential information to a service provider, it's eminently reasonable for the customer to expect that the provider will keep the customer's information confidential.
But unfortunately (for service providers), some customer-drafted clauses in this vein can be a bit overreaching, argubly precluding the service provider from using any information it develops during the engagement for any other purpose.
For additional discussion, see Clause 8.39.17.5 (IP ownership) and Clause 8.39.4 (Toolkit Item exclusion from ownership transfer).
8.18.17. Excluded: Recipient personnel's general knowledge & skills
The Discloser acknowledges that:
one or more of the Recipient's personnel might improve their general knowledge, skills, and experience, in the general field(s) of the Confidential Information or otherwise, as a result of their exposure to that information; and
the Recipient's obligations under this Clause do not require the Recipient to limit what those personnel do in their jobs.
Comment
A. 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."
B. Professor Hrdy points out that this 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).
C. Caution: If you're a Recipient, this general-knowledge exclusion might sound good — but it could be troublesome later because of the potential difficulty of determining, on the particular facts, whether the safe harbor applied, as happened in one case: 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).
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).
8.18.18. Not excluded: Subpoenaed information, etc.
For emphasis: Information is not considered to be within the scope of any of the exclusions above just because the information was sought by someone in a subpoena, search warrant, etc. — that possibility is addressed below at [BROKEN LINK: ConfInfoSubpoena][BROKEN LINK: ConfInfoSubpoena].
Comment
IMPORTANT. When information is subpoenaed or subject to a search warrant, its secrecy can often be protected by court order. As a result, the Discloser would not want the information to automatically lose its Confidential Information status entirely, merely because a subpoena, a search warrant, etc., had been issued.
8.18.19. Alert the Discloser about possible exclusions?
In the interest of professional comity, the Recipient is encouraged — but not required — to promptly advise the Discloser if the Recipient believes that it does not have to follow this Clause for particular Discloser information, for example because the information seems to come within within one or more of the exclusions from Confidential Information status in this Clause.
Comment
This section is one of the "Pick up the phone!" provisions designed to try to identify and resolve potential disputes as early as possible.
8.18.20. Mandatory: Secrecy measures by Recipient
The Recipient must take at least prudent measures 8.19.12.3 to preserve the secrecy of Confidential Information within the Recipient's possession, custody, or control. (For emphasis, the Recipient's measures might not be considered prudent if not at least as protective as the measures that the Recipient uses for its own confidential information of comparable significance.)
B. The term possession, custody, or control is well-known to American litigators from Rule 34(a)(1) of the Federal Rules of Civil Procedure. See, e.g., Blair & Lawler (MorganLewis.com 2018).
C. The "at least as protective" language reflects a concept often seen in Discloser-drafted confidentiality provisions, but softened somewhat.
8.18.21. The Recipient must comply with restrictions about Confidential Information.
Except as clearly agreed by the Discloser, the Recipient must not do any of the following:
use Confidential Information;
disclose Confidential Information to others;
reproduce Confidential Information;
translate Confidential Information;
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;23.4
remove the Discloser's confidentiality markings (if any);
attempt to do anything listed in any of subdivisions 1 through 6; nor
authorize or knowingly help anyone else to do anything listed in subdivisions 1 through 7 above.
8.18.22. The same goes for "derivatives" of Confidential Information.
The Recipient is to treat "derivatives" of Confidential Information as being subject to the same Confidentiality Obligations above as is Confidential Information.
For this purpose, the term derivatives refers to things such as the following when: (i) they contain or are based on Confidential Information, and (ii) are prepared by, for, or on behalf of, the Recipient: (A) analyses; (B) compilations; (C) forecasts; (D) interpretations; (E) notes; (F) reports; (G) studies; (H) summaries; and similar materials.
8.18.23. Recipient's confidentiality obligations for timely-designated trade secrets will not expire.
The Recipient's obligations in sections 8.18.20 and 8.18.21 above will not expire for Confidential Information that qualifies as a trade secret, 8.18.35.1 as defined in the U.S. Defend Trade Secrets Act ("DTSA"), where before expiration (including but not limited during initial disclosure) the Discloser provides the Recipient with a writing that — with reasonable prominence and particularity — designates the information as being a trade secret.
Comment
A. This is a "sunset" provision that tries to compromise between the parties interests:
• The Discloser is likely to balk at across-the-board expiration. That's because, if an NDA allowed confidentiality obligations to expire, it 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 court 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).
Example: The SDNY once 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 defendant on plaintiff's trade-secret claim; citing cases). To like effect, see, 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).
• On the other hand: A Recipient, for its own business efficiency, will likely want to have a "sunset" for its confidentiality obligations. That way, after the sunset date, the Recipient can relax about whether particular "ordinary" confidential information is still subject to such obligations, because it won't have to think about the question.
• So: This section gives the Discloser has a reasonable opportunity to exclude valuable information from the expiration of the Recipient's confidentiality obligations.
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 Contract — this latter alternative can be problematic, however, because the Contract per se might not have an expiration date, and the parties might forget to terminate it.
B. The written-designation requirement here is informed by "a growing body of law [that] requir[es] the trade secret plaintiff to identify its alleged trade secrets with reasonable particularity in an initial trade secret disclosure statement before the defendant is required to respond to plaintiff’s trade secret-related discovery requests." See, e.g., DeWolff, Boberg & Assoc., Inc. v. Pethick, No. 24-10375, slip op. at 6-7 (5th Cir. Apr. 3, 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); 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), cert. denied, No. 23-306 (U.S. Oct. 30, 2023).
C. Of course, for both trade secrets and other Confidential Information, Recipient's confidentiality obligations would automatically end if, at any time, the information in question were shown to come with one of the Confidential Information exclusion categories at Clause 8.18.
8.18.24. Recipient's confidentiality obligations for other Confidential Information will expire in three years.
For Confidential Information that does not qualify under section 8.18.23, the Recipient's Confidentiality Obligations under the Contract will expire the stated time after the end of the Disclosure Term.
Comment
A. 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).
B. Caution: Even after expiration of confidentiality obligations under the Contract, other law concerning, e.g., privacy or export controls might still restrict the Recipient's use- and/or disclosure of information.
8.18.25. Certain Recipient uses of Confidential Information are pre-cleared.
This Clause does not prohibit the Recipient from using Confidential Information — subject to the limitations in this Clause and any other such limitations in the Contract and/or the law — as reasonably necessary for any or all of the following purposes:
assessing whether to enter into another agreement with the Discloser;
performing the Recipient's obligations, and/or exercising the Recipient's rights, under the Contract; and/or
any other purpose specified by the Contract or otherwise agreed in writing by the Discloser.
Comment
A. Pre-cleared uses: 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.
B. Note the limited language, "This Clause does not prohibit" — that's because applicable law might impose other restrictions on such actions, e.g., in the case of privacy laws protecting, e.g., protected health information or personal financial information (see 7.39), or export-controlled information (see 13.11).
C. Subdivision 2: This use case would be appropriate in agreements in which confidentiality provisions were part of, but not the main point of, a larger agreement.
D. Have-used rights? In some circumstances, the Recipient might want to negotiate for "have-used" rights (see 16.3), that is, the right to allow specified third parties (e.g., contractors) to use Confidential Information for the Recipient's benefit.
8.18.26. Certain disclosures are pre-cleared.
This Clause does not prohibit the Recipient from disclosing Confidential Information to the Recipient's employees, officers, directors, and other individuals holding comparable positions in non-corporate organizations (collectively, "individuals") as stated in this section.
Each such individual must be bound by legally-enforceable confidentiality obligations — in a written agreement, or otherwise — that cover the Confidential Information in question.
Each such disclosure must be on a need-to-know basis in connection with an authorized use, disclosure, or translation of the Confidential Information.
The Recipient is to cause each such individual to be appropriately instructed about the confidentiality obligations attached to the Confidential Information.
Comment
A. Written agreements: Entering into a written NDA with employees, etc., might not be necessary; that's because in the U.S., employees, officers, and directors of the Recipient 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.
B. In case the Discloser additionally wants to require the Recipient to enter into written agreements even with Recipient employees, etc.: See the optional language at Clause 8.19.6 (agreement required) and Clause 8.19.7 (copy of agreements to Discloser).
8.18.27. Legally-immune disclosures are not prohibited.
This Clause does not prohibit the Recipient from disclosing Confidential Information if the disclosure falls in one of the categories of limited disclosure to law enforcement, government officials, etc., that is immune from liability under, and/or expressly authorized by, the Defend Trade Secrets Act, at Title 18, Section 1833(b) of the United States Code — the Recipient, though, is encouraged (but not required) to considerconsulting with the Discloser in advance of any such limited disclosure.
Comment
A. Important: Including something like this section could be important in view of legal requirements under the DTSA, as discussed at 8.19.12.4.
B. Consider consultation: This language doesn't impose a requirement for consultation here, because it might attract unwanted attention from government authorities (see the commentary at 8.18.35.5).
8.18.28. The Recipient must follow a procedure if served with a subpoena, etc.
This Clause does not prohibit the Recipient from disclosing Confidential Information, in a strictly-limited way, in response to compulsory legal process — for example, a subpoena or search warrant, where noncompliance could result in adverse action such as jailing — as long as the Recipient complies with this section.
The Recipient must alert the Discloser immediately upon being served with the compulsory legal process — except that the Recipient may exercise discretion about whether and when to do so: (i) if law enforcement asks the Recipient not to do so; and/or (ii) if alerting the Discloser would violate applicable law.
If the Recipient does alert the Discloser, then — only to the extent that the Discloser asks — the Recipient is to provide reasonable cooperation with any efforts by the Discloser to limit or otherwise seek protection for such compulsory disclosures.
Whether or not the Recipient alerts the Discloser, the Recipient is not to disclose more Confidential Information than the minimum required by the compulsory legal process.
For emphasis: This section 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).
Comment
A. Subdivision 3: What counts as "reasonable" cooperation might depend in part on the extent to which the Discloser agreed to bear any significant associated expenses.
B. Section 5: If a public filing by the Recipient might be in the cards, then the parties might want to consider the optional procedural language at Option 8.20.4.
8.18.29. Certain Recipient copies and translations are pre-cleared.
The Recipient may make copies and/or translations of Confidential Information (or have them made by contractors under suitable obligations of confidence) as follows:
copies and translations of Confidential Information to the extent reasonably necessary for authorized uses and disclosures;
archive copies of Confidential Information in accordance with Clause 8.3; and
reasonable routine backup copies of electronically-stored Confidential Information.
Comment
This section explicitly authorizes copies and translations to be made by contractors. Example: In a Second Circuit case, 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)).
8.18.30. The Recipient's copies and translations must be marked.
All copies and translations of Confidential Information made by or for the Recipient must reproduce the Discloser's confidentiality markings (if any) contained in or on the Disclosure source document(s) being copied and/or translated.
Hypothetical example A — situation: The Recipient makes a copy of only a portion of a Discloser source document; that document contains a confidentiality marking at the beginning. Action required: The Recipient must ensure that the copy has the same marking.
Hypothetical example B — situation: The Recipient then causes the copied portion to be translated into French. Action required: The Recipient must ensure that the translation includes the same marking, also translated into French.
8.18.31. Recipient must comply with the law.
In all of the Recipient's activities involving Confidential Information, the Recipient must comply with applicable law — including but not limited to laws concerning privacy; 7.39 export controls; 13.11 and insider trading — and this obligation will not expire.
8.18.32. These pre-clearances will expire with the Contract.
Except as clearly provided otherwise in this Clause, the Recipient's permissions under this Clause concerning Confidential Information will apply only during the term of the Contract.
8.18.33. The Recipient has indemnity obligations.
The Recipient must defend and indemnify the Discloser and its Protected Group against any harm — and the Recipient hereby RELEASES the same parties from any liability for any harm — where the harm is alleged to arise from any activity under this Clause by the Recipient and/or anyone to whom the Recipient makes Confidential Information available. (This indemnity obligation and release will not expire.)
Comment
This is a stronger version of language in section 5 of an IBM confidentiality agreement, which states: "The Discloser will not be liable for any damages arising out of the use of Information disclosed under this Agreement." (Archived here.)
8.18.34. The parties' dealings together are the Confidential Information of each.
The fact, status, and financial terms of the parties' business together are the Confidential Information of each party — even if only one party is designated in the Contract as the Discloser.
Unless clearly agreed otherwise or explicitly required or permitted by law: Each party may disclose to others only that it has entered into an unspecified agreement with the other party and that the agreement includes confidentiality provisions — and each such disclosure:
must be for good reason; and
must be on a one-by-one basis and not in a general- or public announcement.
8.18.35.1. "Trade secrets" vs. "ordinary" Confidential Information
A. In the U.S., a "trade secret" is particular confidential information that derives independent economic value from secrecy; this is provided in both:
B. 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)
C. In the U.S., various statutory remedies are available to possessors of "trade secrets" under the laws cited just above.
D. 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)
E. 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
F. 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).
8.18.35.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).
8.18.35.3. Publicly-available information doesn't qualify
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).
G. 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).
H. But: 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).
8.18.35.4. Unrestricted disclosure will kill confidentiality rights
If the Discloser makes information available to others without restriction, then (practically as a matter of law) that information isn't eligible to be treated as Confidential Information. Here are some 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, did not 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 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 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 Oswaldnotes 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."
8.18.35.5. Secrecy of dealings: Business background
For various business reasons — 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 — parties often want the mere fact that they are in discussions to remain confidential, let alone the details of their dealings. (Public information about the parties' dealings would of course not be Confidential Information.)
8.18.35.6. Secrecy of dealings: Wording can be important
Caution: Parties should carefully consider the wording of a confidentiality-of-dealings clause — because incautious wording could fail to protect what a party is really concerned about. Example: something like that seems to have happened in the settlement of a Texas medical-malpractice case:
A pain-management doctor was sued for wrongful death by the mother of a young woman. The mother alleged that her daughter died of a drug overdose while under the doctor's care.
The mother and the doctor settled the lawsuit; the settlement agreement included a confidentiality provision.
The mother, though, later posted statements on her Twitter feed regarding the doctor's alleged responsibility for several of his patients' deaths. The mother also gave an interview to a newspaper reporter, who who wrote an article critical of the doctor's work.
The Houston court of appeals held that the wording of the settlement agreement barred the mother from discussing the settlement, leaving the mother free to talk about 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) (mem. op.) (affirming summary judgment for defendant mother).
8.18.35.7. Will a secrecy-of-dealings clause 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).
On the other hand, a party's breach of a confidentiality-of-dealings clause might not be considered "material." 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).
8.18.35.8. Secrecy of dealings: Will 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 8.19.12.4 for a detailed discussion.
If this Option is agreed to, it will govern if — within a reasonable period after termination or expiration of the Contract — the Discloser provides the Recipient with a written request for the return or destruction of Confidential Information.
Comment
This Option could be trouble for a Recipient:
• In real life, a return-or-destroy requirement in a contract is likely to be burdensome and even impracticable. That's especially true when electronically-stored information ("ESI") is involved, which can be difficult and costly just to locate, let alone to destroy.
• Worse: When the contract comes to an end, the Recipient might well forget that the Recipient had committed to return or destroy the information.
For that reason, a Recipient will usually want to consider pushing back against a Discloser request to agree to this Option.
8.19.1.2. The Recipient must make commercially-reasonable efforts.
A. This Option doesn't make it an absolute requirement to return or destroy Confidential Information, because that could be burdensome for the Recipient.
On the other hand, in some cases the Recipient might consider it an acceptable business risk to agree to an absolute requirement — the thinking could be that, if the Recipient were to miss returning or destroying a copy, the Discloser's resulting damages might be minimal.
B. Caution: If the Recipient did agree to an absolute requirement, but then failed to comply with it, then that failure could give the Discloser a cudgel with which to bash the Recipient as a scofflaw.
C. Pro tip: The Recipient might want to consider segregating Confidential Information to reduce the burden and expense of compliance with a return-or-destroy obligation — and the Discloser might even want to propose requiring such segregation, possibly using Option 8.19.8.
8.19.1.3. Emails and other messages are exempt.
Except as otherwise provided in this Option, the Recipient need not destroy emails, text messages, and similar messages containing Confidential Information.
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.
• Furthermore: Attempting to surgically delete Confidential Information from such messages would usually be costly, impracticable, and even impossible.
8.19.1.4. System backups need not be purged.
Except as otherwise provided in this Option, the Recipient need not destroy system-backup copies containing Confidential Information, created as part of the Recipient's commercially-reasonable regular IT practices — but those IT practices must include secrecy measures comparable to those required by the Contract (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."
8.19.1.5. The Recipient may (securely) keep archive copies.
Except as otherwise provided in this Option, the Recipient need not return or destroy archive copies containing Confidential Information — but those copies must be retained in strict confidence and used only for archival purposes.
Comment
The Recipient will likely want to retain — and perhaps should try to insist on retaining — archive copies of Confidential Information. That's because the Recipient might someday want to be able to check its archive copies to confirm — or refute — later claims by the Discloser that the Recipient was misappropriating information that allegedly had been provided to the Recipient by the Discloser. Example: Just such a situation arose in a Florida federal-court case. 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).
The above exceptions to this Option's return-or-destroy requirement do not apply — other than as stated at subdivision 2 below — if the Recipient is an employee or individual contractor of the Discloser.
Even if the Recipient is an employee or contractor of the Discloser, however, the Recipient need not return or destroy copies containing Confidential Information that are retained solely for the purpose of:
reasonably-anticipated disclosure permitted by law under section 8.18.27, and/or
disclosure in response to a then-pending compulsory legal process under section 8.18.28, of Clause 8.18.
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.
8.19.1.7. Confidentiality obligations continue for retained copies.
For any copies or other embodiments of Confidential Information that are not returned or destroyed, the Recipient must continue to comply with the confidentiality obligations of the Contract until such time — if any — as those obligations no longer apply.
Comment
Confidentiality obligations could expire with the passage of time; see section 8.18.24.
8.19.1.8. Upon request, the Recipient must certify compliance.
If the Discloser so requests in writing within a reasonable time after the return-or-destruction request, then the Recipient is to promptly provide the Discloser with a written certificate of the Recipient's compliance with this Option — noting any known areas of noncompliance.
Comment
Caution: This certification requirement could be dangerous to the Recipient: Suppose that it later turned out that the Recipient didn't completely return or destroy the Discloser's Confidential Information: That fact could later help persuade a jury that the Recipient misappropriated the confidential information by secretly using it after having supposedly returned it.
• Example: In a 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. See S.W. Energy v. Berry-Helfand , 491 S.W.3d 699, 708 (Tex. 2016).
• 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. See Natalie Posgate, 13 Years Later, Trade Secrets Legal Battle Is Over … Almost (TexasLawbook.net 2021) (paywalled).
If this Option is agreed to, it will govern whenever there has been a possible unauthorized use and/or disclosure of particular Confidential Information to which the Recipient had access.
Comment
A Discloser will often like to include provisions such as this in an NDA, in case Discloser finds itself "going after" a third party for misappropriating Confidential Information.
8.19.2.2. The Recipient must provide reasonable assistance.
Upon request by — and only in response to the (lawful) directions of — the Discloser or the Discloser's counsel, the Recipient is to provide reasonable assistance in identifying, and/or taking legal action concerning, the unauthorized use and/or disclosure.
Comment
A. The Recipient's "reasonable" assistance to the Discloser under this Option would normally be at the Discloser's expense — but it might be a different story if the Recipient was responsible, directly or indirectly, for the unauthorized use and/or disclosure.
B. In deciding what it would do to provide such assistance, the Recipient would ordinarily want to consider (for example) any applicable attorney-client privilege to which the Recipient was entitled.
8.19.2.3. The Recipient is not to take action on its own (usually).
On its own, the Recipient is not to take any action under this Option against a third party — other than the Recipient's own employees and contractors — unless the Discloser specifically so requests.
Comment
This Option doesn't restrict the Recipient from taking (otherwise-lawful) action against a Recipient employee that engaged in unauthorized use and/or disclosure of the Discloser's Confidential Information.
8.19.3. Option: Recipient's Responsibility for Third-Party Actions with Confidential Information
If this Option is agreed to, it will govern whenever both of the following are true:
any third party — including but not limited to the Recipient's employees — obtains or otherwise accesses Confidential Information in connection with the Recipient's relationship with the third party; and
the third party uses, discloses, and/or copies Confidential Information in a manner not permitted by the Contract.
Comment
A. This is set out as an Option, and not as part of Clause 8.18, 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).
B. This language 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
8.19.3.2. The Recipient has an indemnity obligation.
The Recipient must defend and indemnify the Discloser and its 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.
For emphasis, this obligation is not limited to claims against the Discloser.
When this Option is agreed to, the Discloser may seek a restraining order against unauthorized use or disclosure of Confidential Information in accordance with applicable law.
Comment
A. This injunctive-relief option represents a compromise, but it really just states the obvious: At least in American jurisdictions, the Discloser would always be free to seek injunctive relief against breach or prospective breach of a confidentiality agreement.
B. Whether a court would grant preliminary relief would be a very-different question than the one addressed here.
C. This Option uses the better-known term "restraining order" instead of, e.g., "preliminary injunction," because the latter phrasing is likely to be less familiar to non-lawyers.
D. See also Clause 8.29 (equitable relief) and Clause 8.9 (bond waiver).
The Recipient must promptly alert the Discloser to any potential unauthorized use or disclosure of Confidential Information of which the Recipient becomes aware, even if the Recipient is actually, potentially, or arguably at fault.
Comment
Some Recipients might be reluctant to agree to the whistleblower obligations of this Option, because agreeing would mean that:
failing to blow the whistle on one's own potential problems, 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 3.1),
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.
8.19.5.2. Some examples
For emphasis: This Option would require the Recipient to report suspected activity by one or more of:
the Recipient itself;
one or more Recipient's employees, whether or not in the scope of their employment; and/or
any other party to which the Recipient provides Confidential Information, whether or not as authorized by the Contract.
8.19.6. Option: Written Confidentiality Agreements
If this Option is agreed to, it will apply, if requested by the Discloser, if the Recipient expects to provide Confidential Information to any person (including but not limited to the Recipient's employees) (the "Downstream Recipient").
Comment
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).
8.19.6.2. The Recipient must obtain specific confidentiality agreements.
The Recipient must not provide Confidential Information to the Downstream Recipient unless both of those parties enter into a written confidentiality agreement in which both of the following are clearly stated:
the Downstream Recipient commits to complying with the same confidentiality obligations as apply to the Recipient under the Contract; and
the Discloser is a named third-party beneficiary of that confidentiality agreement.
8.19.7. Option: Copies of Recipient's Confidentiality Agreements
If this Option is agreed to, it will apply, at the Discloser's request, if the Recipient provides Confidential Information to any individual and/or organization ("other person") to which the Recipient make Confidential Information available.
8.19.7.2. The Recipient must provide the Discloser with signed confidentiality agreements.
The Recipient must obtain — and provide the Discloser with a copy of — a signed written confidentiality agreement between the Recipient and each such individual or organization.
Comment
Providing signed copies of confidentiality agreements might be burdensome for Recipient, but sometimes the Discloser might feel it has a genuine need for such copies.
8.19.7.3. The confidentiality agreements must meet specific requirements.
Each such agreement must obligate the other person in substantially the same way as the Recipient is obligated under the Contract.
8.19.7.4. Reasonable redactions are permitted.
The copy of the agreement provided to the Discloser may be redacted — to a reasonable extent — so that the Discloser will not have access to confidential information of the Recipient and/or of the other person.
Comment
This 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
8.19.7.5. Disagreements about this Option are to be escalated.
If any party asks, the parties will any persistent disagreement about redactions as provided at Clause 6.4.
Comment
See the discussion at the cited clause.
8.19.8. Option: Confidential Information Segregation
The Recipient must keep Confidential Information reasonably segregated from other information, if and when the Discloser so requests in writing with regard to that information, with a view to:
providing additional secrecy protection, and
facilitating any return or destruction that might be required by the Contract (if any).
Comment
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 — it seems likely that this occurred, at least in part, because 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.
If agreed to, this Option will apply at any time that the Recipient has, or might have, Confidential Information in its possession.
Comment
This Option follows the maxim that you get what you INspect, not what you EXpect (see 8.37).
8.19.9.2. The Recipient must allow reasonable compliance inspections.
The Recipient must allow the Discloser to cause reasonable inspections of the Recipient's relevant properties and premises (tangible, electronic, and otherwise) to be conducted from time to time.
Clause 8.37 (inspections) and, where applicable, Clause 8.17 (general rules for computer-system access), are incorporated by reference.
Comment
Subdivision 2: See the commentary at the cited clauses.
8.19.9.3. The Discloser must limit its use of what it learns.
The Discloser must use any such inspection and its results (and allow such use) for no other purpose than to confirm that the Recipient is complying with its confidentiality obligations under the Contract.
Comment
This 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.
8.19.9.4. The Recipient must require its subcontractors to do the same.
The Recipient is to 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 section, in itself, does not authorize the Recipient to use subcontractors, but neither does it prohibit the Recipient from doing so.
Comment
For more about flow-down obligations, see generally 14.3.
the Recipient's use of Confidential Information, and/or
the Recipient's disclosure of Confidential Information to other parties.
Subdivision 1 will apply whether or not the Recipient's relevant use and/or disclosure of Confidential Information was of a kind contemplated by the Contract.
Comment
Insurance support? 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 3.10.
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.
The Recipient may not assign the Contract without the Discloser's prior written consent.
Comment
A. If a Discloser proposes this Option, the Recipient should think long and hard about whether to agree. That's because 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 8.4.8.
B. 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 8.4.4 and 8.4.5.
C. Pro tip: If a Recipient were asked to agree to an assignment-consent obligation, the Recipient could consider countering by proposing Option 8.5.1 (exception for asset-disposition transactions), for reasons discussed at 8.4.8.
8.19.12.1. Marking: A good idea — but don't make it mandatory
A. 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 Compaq (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, in section 8.18.7, 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.
B. 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. At this writing (fall
C. "Appropriate prominence" would ordinarily mean readily calling attention to the confidential status of the information.
8.19.12.2. Confirm a previous oral confidentiality agreement?
A drafter could adjust the start date of the Disclosure Term to take into account that the parties might want to have written confidentiality obligations to cover information that one or more of them (hypothetically) disclosed earlier under an oral confidentiality agreement. When that's the case, it's useful to be clear that such earlier-disclosed information is considered covered by the written NDA, to reduce the chances of "misunderstanding" later.
(Catch-up written agreements of this kind are sometimes referred to by the Latin phrase nunc pro tunc, "now for then.")
A written catch-up agreement can address this problem: If, say, the Discloser later had to sue the Recipient for breaching the (alleged) oral confidentiality agreement, then the Discloser's success would depend on whether the judge and/or jury believed the Discloser's witness(es) that the Recipient had indeed orally agreed to keep the Discloser's information confidential.
And the details of the oral agreement are likely to matter. Example: In one case, the Second Circuit viewed an oral agreement as insufficiently robust to protect the alleged confidential information; the court described the oral agreement as being "at most an informal understanding among [the parties]." Pauwels v. Deloitte LLP, 83 F.4th 171, 179, 182 (2d Cir. 2023) (affirming summary judgment in relevant part)
So the Discloser's drafter might want to include language in the Contract 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 [INSERT 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: In some circumstances, falsely stating the signature dates of a contract (as opposed to the contract's effective date) could be problematic, and even lead to prison time, as discussed at 10.1.2.
8.19.12.3. What sorts of security measures might be called for?
Under the law, reasonable secrecy precautions by the Discloser are pretty much an absolute necessity for legal protection of confidential information; for some examples of common security precautions, see 8.19.12.3.
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 federal-court 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. At this writing (fall 2024), the case seems to be still in the discovery stage. 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.
Caution: 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 from998 F. 3d 190, 199 (5th Cir. 2021) (reversing district court's dismissal, on limitation grounds, of trade-secret claims; cleaned up, case citations omitted).
• Use role-based permissions on computer networks — for example, marketing people might not need to see 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.
8.19.12.4. Discloser Rule: Tell employees about their whistleblower rights — and don't ask them to waive those rights
Section 8.18.27 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).
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.
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.
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.
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.
D. 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.
8.19.12.5. 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: A federal-court jury in Los Angeles once awarded a one-man startup company more than $117 million (in 2025 dollars) against aerospace conglomerate Rockwell International for breaching a confidentiality agreement that had been entered into to discuss a possible royalty-bearing license.
Rockwell's position was that the startup company's technology consisted of well-known engineering techniques and so royalty payments weren't warranted.
But the jury didn't buy Rockwell's story — after the trial, jurors said that one Rockwell employee's deposition testimony on video had made a very bad impression. See Celeritas Technologies Ltd. v. Rockwell Int'l, Inc., 150 F.3d 1354, 1359 (Fed. Cir. 1998). Disclosure: Your author was part of Rockwell's trial team in that case and participated in the post-trial juror interviews.
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.
8.19.12.6. Special case: Disclosure to venture capitalists, etc.
Amplifying the discussion in 8.19.12.5: 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 section 8.18.10) 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.
8.19.12.7. 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).
8.20.1. Option: Discloser Representation of Secrecy
The Discloser represents that the Discloser has not made any Confidential Information available to any third party without confidentiality obligations substantially the same as those of the Contract.
Comment
A. 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.
B. 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 3.17.)
C. 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).
8.20.2. Option: Recipient Disclosure to Prospective Acquirer
8.20.2.1. Applicability of this Option
If this Option is agreed to, it will apply if the Recipient contemplates engaging in a merger, spin-off, or similar "Transaction." with one or more "Transaction Prospects," namely the following:
a prospective acquirer of substantially all assets of (i) the Recipient's business as a whole, or (ii) the portions of the Recipient's business to which the Contract relates;
a prospective acquirer of substantially all of the Recipient's shares — if the Recipient is a corporation or similar organization having shares — or of equivalent ownership interest under applicable law, if the Recipient is an organization that does not have shares; and/or
a party (or an affiliate of a party) with which the Recipient anticipates engaging in a merger, or similar transaction.
Comment
A. A Recipient might someday consider being acquired by another company; in that situation, the prospective acquirer might want to review at least some Discloser confidential information during due diligence — but that could pose dangers for the acquirer if the acquirer was a competitor of the Discloser. Something like that happened in a Ninth Circuit case in which Facebook got caught in the middle, as discussed at 8.20.6.1.
B. See also Option 8.5.1 (exception to assignment-consent requirement).
Comment
A. This definition of Transaction Prospect should cover what are likely to be the most-common types of merger- and acquisition transactions.
B. "Affiliate" status might come into play here (see Clause 7.2 concerning what qualifies as an affiliate). That's because for tax purposes, many merger transactions are done as "reverse triangular mergers," as explained in GSE Consulting (11th Cir. 2023); see also Reverse Triangular Merger Definition (Investopedia.com).
8.20.2.2. Certain "Advisers" may be given access to Discloser Confidential Information.
As long as this Option is complied with, the Recipient and/or any of the Transaction Prospect(s) may provide the Discloser's Confidential Information to the following, but only if they qualify under section 8.20.2.3 below:
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
the Recipient's own Advisers.
Comment
Many of the Recipient's Advisers would likely be eligible to receive Confidential Information already under the basic confidentiality agreement, but it seems best to cover that possibility.
8.20.2.3. Need-to-know is a prerequisite
Neither the Recipient nor the Transaction Prospect may disclose Confidential Information to any Adviser unless, in each particular case, the Adviser:
has a legitimate need to know in connection with the possible transaction; and
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.
Comment
At least in the U.S., normally the respective legal counsel for the Recipient and the Transaction Prospect would automatically have an ethical obligation to comply with confidentiality obligations agreed to by the Transaction Prospect — and could be disciplined for breaching that obligation. (The same could be true of other Advisers.)
8.20.2.4. A separate Transaction Prospect NDA is required.
The Transaction Prospect must agree with the Recipient, in writing, to comply with this Option concerning the Discloser's Confidential Information.
If the Discloser asks, the Recipient is to promptly provide the Discloser with a copy of the signed confidentiality agreement between the Recipient and the Transaction Prospect.
The copy provided under subdivision 2 may be reasonably redacted to delete or conceal information that does not concern the Transaction Prospect's confidentiality obligations that would benefit the Discloser.
8.20.2.5. Disclosures must be in secure data rooms.
The Recipient is to 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.
Comment
A. In M&A transactions, either physical or, more likely, online data rooms are commonly used for due diligence disclosures.
B. Pro tip: 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).
8.20.2.6. The Transaction Prospect's copying must be restricted.
Unless the Discloser gives its prior written consent, the Recipient must take prudent measures to keep the Transaction Prospect (and the Recipient's and Transaction Prospect's respective Advisers) from:
making copies of the Discloser's Confidential Information, and/or
providing Confidential Information to others not authorized by the Contract.
Comment
A. 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 Clause 8.3) of documents inspected — possibly including the Discloser's Confidential Information.
(The Discloser would probably go along with such record-making, but the Discloser would very likely want to be pretty hands-on in negotiating boundaries and restrictions.)
B. 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.
8.20.2.7. The Discloser need not be informed about the transaction.
Neither the Recipient nor the Transaction Prospect is required to inform the Discloser:
that a transaction might occur;
the status of negotiations for the transaction; nor
any details about the possible transaction.
Comment
A. Transactions of the kind contemplated here are generally kept very hush-hush until ready to be announced. Moreover, the Recipient will not want to be obligated to report specially to the Discloser. Not least, all this is because when such a transaction is being negotiated — and particularly after the transaction agreement is signed — the Recipient is likely to have other things on its mind and might overlook such a reporting obligation.
B. There's another reason for silence here: An opportunistic the Discloser might try to parlay early knowledge of the potential transaction into some kind of leverage over the Recipient and/or the Transaction Prospect. (See the discussion at 8.4.8 for more on that possibility.)
8.20.2.8. The Discloser must comply with confidentiality obligations of its own.
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.
8.20.3. Option: Disclosure for Use by Recipient Contractors
If this Option is agreed to, the Recipient may disclose Confidential Information to the Recipient's suppliers and contractors, but only where all of the following are true:
the disclosure must be solely for use by the supplier or contractor for the Recipient's direct benefit;
the Recipient must first obtain a written confidentiality agreement from the relevant supplier or contractor; and
that confidentiality agreement must contain confidentiality provisions — expressly benefiting the Discloser — that are substantially identical to those of Clause 8.18.
Comment
A. "Have-used" rights: In today's modern economy, a Recipient might need more than just the right to make use of Confidential Information "in-house" by the Recipient's own people. (See also the discussion of that subject at 16.3.)
B. Caution: Some confidentiality agreements categorically allow disclosure to Recipient's (outside) consultants and advisors, but that should probably be negotiated on a case-by-case basis.
C. Caution: Drafters should consider the extent — if any — to which some such other persons should not be permitted to receive Confidential Information. This will be especially true the if Recipient's workforce includes so-called "leased employees" or other individuals working long-term in independent-contractor status.
If this Option is agreed to, then 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.
Comment
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.
8.20.4.2. The Recipient must consult with the Discloser in advance.
Before any public-filing disclosure under this Option, the Recipient must first consult with the Discloser, early enough to give the Discloser a reasonable opportunity to seek an order for confidential treatment or comparable relief.
Comment
A. This one of the pick up the phone! provisions designed to try to identify and resolve potential disputes as early as possible
B. 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
8.20.4.3. The Recipient is to cooperate in seeking limited disclosure.
If so requested by the Discloser, the Recipient is to cooperate 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 section 8.18.28 (subpoenas, etc.).
8.20.4.4. The Recipient must reimburse the Discloser's associated expenses.
If so requested by the Discloser, the Recipient is to reimburse the Discloser for reasonable expenses incurred by the Discloser in any efforts under section 3.
If this Option is agreed to, the Recipient will not be liable to the Discloser under this Clause — for compensation or otherwise — if the Recipient makes unaided use of Confidential Information "residuals," defined below, as stated in this Option.
Comment
A. Caution: Some recipients of confidential information (cough, Microsoft) have been known to push for "residuals rights" of this kind; disclosers likely will (and often should) push back — or at a minimum, ask for carve-outs.
B. Disclosers asked to agree to residuals-rights clauses should consider asking 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).
8.20.5.2. Consult with the Discloser in advance?
The Recipient shouldconsiderconsulting with the Discloser about any proposed reliance on this Option by the Recipient.
Comment
This is one of the pick up the phone! provisions designed to try to identify and resolve potential disputes as early as possible.
8.20.5.3. Definition: Residuals
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:
the information was retained in the unaided memory of one or more of the Recipient's people; and
none of those people intentionally memorized the information for that purpose.
Comment
A. 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.
B. Residuals – how to prove unaided retention? Suppose that the Discloser claimed that a Recipient staffer — let's call that person "Robin" — had improperly used Confidential Information, but Robin said that s/he hadn't intentionally memorized the information. That seems as though it would all come down to whether the trier of fact (the judge or jury) believed Robin's testimony.
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.
D. Here's another example of residuals language, apparently from some kind of venture-capitalist agreement form, that your author 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.
8.20.5.4. A narrow interpretation is intended.
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 Contract.
Comment
A. Caution: A broad scope of residuals rights could complicate trade-secret litigation. This seems to have happened in a case involving Google's "Project Loon," which experimented with providing global wireless Internet service using high-altitude balloons orbiting the Earth. Google 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).
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.
8.20.5.5. No other rights are granted here.
For emphasis:
This Option does not relax any restriction of the Contract on the Recipient's disclosure of Confidential Information.
Nor does this Option give the Recipient any license under any patent, copyright, or other intellectual-property right of the Discloser.
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 Clause 8.18.
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 8.19.12.5 of the Celeritas v. Rockwell case, where a one-man startup company scored a $117 million verdict (in 2025 dollars) against a defense contractor.
8.20.6.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.
8.20.6.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 Clause 7.39 (privacy) and 13.11 (export controls).)
But even if MathWhiz and Gigunda intend 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, section 8.18.2 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).
8.20.6.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.
8.20.6.5. Pro tip: Collect & save "corroborating evidence"
A Recipient of putatively-Confidential Information should seriously consider watching out for, and saving, any evidence that comes to hand that could help establish:
that the Recipient had already known the information in question before the Discloser provided it to the Recipient;
that a third party independently provided similar information to the Recipient; and/or
that the Recipient independently developed the information (that can be a tough sell).
Such corroboration might be needed to help convince a judge or jury that the Recipient wasn't just trying to get out from under its confidentiality obligations concerning the information. And a judge or jury might be skeptical of a Recipient's after-the-fact claims along these lines:
Example: In one Texas case, a federal-court jury awarded software vendor $152 million because a customer of the vendor had helped a competitor of the vendor to reverse-engineer the vendor's software product in violation of the license agreement; the jury evidently didn't believe the competitor's claim that it developed its own software without using the vendor's software. 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: In a Texas supreme court case, 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 — even though they'd been exposed to the startup company's allegedly-confidential information — but the jury didn't buy Rockwell's story. See Celeritas Technologies Ltd. v. Rockwell Int'l, Inc., 150 F.3d 1354, 1359 (Fed. Cir. 1998). Disclosure: Your author was part of Rockwell's trial team in that case.
Such cases suggest that recipients should plan to document independent possession of 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.).
8.20.6.6. 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.)
8.20.6.7. 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 understand that later the parties could revisit the question.
8.20.6.8. 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 Clause) — 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 (!).8.28
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.
8.20.6.9. Push back against return-or-destroy requirements?
See the commentary to Option 8.19.1 (return or destruction upon request).
8.20.6.10. 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 8.47), 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 8.47) 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).
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 8.39.9 concerning the difference between a "present assignment" of future IP rights and an agreement to assign such rights in the future.)
It's not unheard of for an NDA to state that the Recipient must not try to "poach" any Discloser employee; see 8.48.8 for more details and cautions.
8.21. Consent Requests
This Clause addresses the situation where a reviewer wants the right to consent to an action by or for a proposer — as in, the contract would provide that the proposer must not take the action without the reviewing party's prior written consent.
When this Clause is agreed to, the parties will follow it whenever one party (the "Proposer") asks another party (the "Reviewer") for consent to a particular action (the "Action"), where the consent is required (i) by the Contract, and/or (ii) as a matter of law.
Comment
A. This Clause is intentionally phrased to cover situations in which the Proposer might not be the one taking the Action but is simply asking for the Reviewer's consent.
B. One possibility for such a situation is if the Contract prohibits the Proposer from assigning the Contract without the Reviewer's prior written consent; be sure to see Clause 8.4 (protocol for consents to assignment of the Contract) with its options and notes).
8.21.2. The Reviewer may defer the consent decision if reasonable.
The Reviewer is free to defer the consent decision if reasonable to do so in the circumstances, for example if additional information is reasonably needed.
Comment
A. Granted, this "deferral is OK" language is vague enough to be potentially problematic. But it'd give the Proposer of the Action an incentive to cooperate with the Reviewer.
B. One reason a Reviewer might want to defer a consent decision could be to get more information about the proposed Action. Example: A federal appeals court upheld a patent owner's refusal to consent to a licensee's assignment of an exclusive license agreement, in part because the patent owner had asked the licensee for documentation about the proposed assignment transaction, but the licensee didn't comply with the request. See MDS (Canada) Inc. v. Rad Source Tech., Inc., 720 F.3d 833, 850 (11th Cir. 2013), affirming in part822 F. Supp. 2d 1263 (S.D. Fla. 2011).
8.21.3. Consent disagreements are to be escalated.
The parties will escalate any deferral dispute, starting with internal escalation under Clause 6.5 and, if necessary, progressing to escalation to a neutral advisor under Clause 6.4.
Comment
See the commentary at the cited clauses.
8.21.4. Proposer: Don't take consent as a "green light."
When the Reviewer consents to the proposed Action, it does not mean that the Reviewer affirmatively approves or authorizes the action, but only that the Reviewer will not object to the Action nor seek to block it.
Comment
This is because the law, or another contract, might separately prohibit or limit the Action; if that's the case, then the Reviewer wouldn't want to be in a position of having supposedly "authorized" the Action.
8.21.5. Consent is no substitute for judgment or advice.
The Proposer is not to rely on the Reviewer's consent as a substitute for the Reviewer's own judgment, nor for input from the Proposer's own licensed attorney and/or other professional advisor.
Comment
See the extended discussions at 6.11.5 (opportunity to consult counsel) and 8.57 (reliance disclaimer).
8.21.6. Consent is for the Reviewer's benefit only.
The Reviewer's consent-related actions are solely for the Reviewer's benefit.
Comment
See the discussion of third-party benefits in the commentary to Clause 8.66.
8.21.7. The Contract could limit the right to refuse consent.
Any limitations in the Contract on the Reviewer's right to refuse consent must be clearly stated.
Comment
A consent requirement in the Contract could include restrictions such as (for example) one or more of the following limitations or expansive permissions:
[Reviewer's name] may not unreasonably withheld, delay, or condition its consent to [Action].
[Reviewer's name] may withhold consent to [Action] in its sole and unfettered discretion.
It is conclusively deemed unreasonable and arbitrary for [Reviewer's name] to require a fee or other payment (no matter how named) in return for consent to [Action] — but a fee or other payment that would otherwise be due anyway under the Contract would not be considered such a fee.
[Reviewer's name] is free to charge a fee for its consent to [Action], in any amount, to the extent not inconsistent with applicable law.
8.21.8. The Reviewer's silence does not imply consent.
If the Reviewer does not respond to a Proposer request for consent, it does not constitute implied consent by the Reviewer — unless the Contract clearly says otherwise, that is, for example by stating that a failure to object to the action within X amount of time would be deemed as consent.
8.21.9. Reviewer: Consider explaining a declined consent.
The Reviewer is encouraged to consider explaining to the Proposer, in reasonable detail, the Reviewer's then-existing reasons for declining to give consent.
8.21.10. Additional notes (not part of this Clause)
8.21.10.1. When asking for consent: What if the answer is "no"?
Any time you ask for consent, you should be prepared for the answer to be "no." And then what? By asking, have you implicitly conceded that consent is required?
8.21.10.2. "not unreasonably withheld" – a requester trap?
When a party "Fred" negotiates a requirement that he seek "Ginger's" consent before taking some action, Fred might be tempted to ask to add, that "consent must not be unreasonably withheld, delayed, or conditioned." That might cause more problems that it solves.
A. For assignment-consent requests, a might be implied by law in certain circumstances; still, some reviewing-party drafters like to say this explicitly as cheap insurance.
B. "Not to be unreasonably withheld" might not be worth much: When one party demands the right to consent to some action by the other party, the other party will likely ask for a "consent not to be unreasonably withheld" qualifier. That might sound good, but for assignment consents it might not be of much practical value: If the reviewing party wants to cause trouble, the resulting delay and expense could impede — and even kill — the assigning party's desired transaction that it has in mind.
C. And even asking for this Option could be a case of poking the bear that causes the other party to respond by insisting on the right to grant or withhold consent in that party's sole discretion.
Comment
Example:Section 1995.260 of the California Civil Code provides that: "If a restriction on transfer of the tenant's interest in a lease requires the landlord's consent for transfer but provides no standard for giving or withholding consent, the restriction on transfer shall be construed to include an implied standard that the landlord's consent may not be unreasonably withheld. … "
Example: Apropos of that statutory provision, a California appeals court held that a contract provision allowing the landlord to withhold consent "for any reason or no reason" was not to be construed as including an unreasonably-withheld standard, saying that "the parties' express agreement to a ‘sole discretion' standard is permitted under legal standards existing before and after enactment of section 1995.260, as long as the provision is freely negotiated and not illegal." Nevada Atlantic Corp. v. Wrec Lido Venture, LLC, No. G039825 (Cal. App. Dec. 8, 2008) (unpublished; reversing trial-court judgment that withholding of consent was unreasonable).
Example: In an Oregon case, A lease prohibited the tenant from assigning the agreement, including by operation of law, without the landlord's consent. The lease also stated that the landlord would not unreasonably withhold its consent to an assignment of the lease to a subtenant that met certain qualifications. Notably, though, the lease did not include a similar, no-unreasonable-withholding statement for other assignments. Oregon's supreme court held that ordinarily, the state's law would have required the landlord to act in good faith in deciding whether or not to consent to an assignment. But, the court said, the parties had implicitly agreed otherwise — therefore, the landlord did not have such a duty of good faith. See Pacific First Bank v. New Morgan Park Corp., 876 P.2d 761 (Or. 1994) (affirming court of appeals decision on different grounds, and reversing trial-court declaration that bank-tenant had not materially breached lease).
Example: In MDS (Canada) (11th Cir. 2013), the court upheld a trial court's finding that the owner of a patent, which had exclusively licensed the patent to another party, had not acted unreasonably under the circumstances when it refused consent to an assignment by the licensee to a party that wanted to acquire the licensee's relevant product line.
(This holding provides a useful illustration of how appeals courts have limited ability to "second-guess" a trial court's findings of fact.)
Example: In 2013's Dick Broadcasting Co., Tennessee's supreme court held that:
where the parties have contracted to allow assignment of an agreement with the consent of the non-assigning party,
and the agreement is silent regarding the anticipated standard of conduct in withholding consent,
[then] an implied covenant of good faith and fair dealing applies and requires the nonassigning party to act[:]
with good faith
and in a commercially reasonable manner
in deciding whether to consent to the assignment.
Dick Broadcasting Co. v. Oak Ridge FM, Inc., 395 S.W.3d 653, 656-57 (Tenn. 2013) (affirming vacation of summary judgment and remand to district court) (formatting revised).
Example: In Shoney's from 2009, Alabama's supreme court alluded to a similar possibility; The contract in suit specifically gave the Shoney's restauraunt chain the right, in its sole discretion, to consent to any proposed assignment or sublease of a ground lease by a real-estate developer that had acquired the ground lease from Shoney's. The supreme court held that this express language overrode a rule that had been laid down in prior case law, namely that a refusal to consent is to be judged by a reasonableness standard under an implied covenant of good faith. See Shoney's LLC v. MAC East, LLC, 27 So.3d 1216, 1220-21 (Ala. 2009) (on certification by Eleventh Circuit).
Counterexample: In Barrow-Shaver Resources (Tex. 2019), the Texas supreme court declined to read a reasonableness requirement into an assignment-consent provision. Barrow-Shaver Resources Co. v. Carrizo Oil & Gas, Inc., 590 S.W.3d 471, 476 (Tex. 2019) (affirming court of appeals and declining to read a reasonableness qualifier into a consent-to-assign provision).
Caution for Texas lawyers and law students: Barrow-Shaver fits in with Texas's non-recognition of a general implied covenant of good faith and fair dealing. See, e.g., Subaru of America, Inc. v. David McDavid Nissan, Inc., 84 S.W.3d 212 (Tex. 2002); 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).
And again: The reviewer might be willing to "play chicken" with the proposer, as discussed at 8.4.13.
For additional discussion of consent standards, see 8.21.
8.21.10.3. Caution: Don't tie your client's hands in its own form
Suppose that you're drafting a contract form that your client expects to use with lots of other parties. You do not want to add language stating that your client will obtain the other party's consent before doing something — call it "Action X" — such as assigning the contract (see 8.4). That's because:
• If your client ever did want to take Action X, your client would need to seek the consent of all of the various other parties with which your client has used the contract form.
• Even seeking such consent could be burdensome and costly, as discussed at 8.4.12.
• And there's always the risk that one or more of the other parties might seize the opportunity to demand major concessions from your client as part of the price of giving consent.
The parties intend for the Contract 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").
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 how to spell contra proferentem!
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.)
8.22.1.2. Why do courts (sometimes) use the contra proferentem doctrine?
The policy basis for contra proferentem was explained by the Supreme Court in Shearson Lehman Hutton (U.S. 1995):
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.
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).
8.22.1.3. 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.
8.22.1.4. Caution: Disclaiming contra proferentem can cause problems.
In some jurisdictions, courts readily enforce contra proferentem disclaimers. Delaware is such a jurisdiction, as noted by the Chancery Court in a 2023 decision. 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, No. 478, 2023 (Del. Feb. 26, 2024).
To similar effect is the Tenth Circuit's ORP Surgical (2024), where 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.
8.22.1.5. 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.
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 in Lamps Plus (2019):
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. _ _, 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).
8.22.1.6. 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 its 2019 Lamps Plus decision concerning an arbitration provision; see 8.22.1.5.
In Lamps Plus, 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 8.1.3). The Supreme 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, Inc. v. Varela, 587 U.S. _ _, 139 S. Ct. 1407, 1417, 1418 (2019) (reversing and remanding Ninth Circuit's affirmance of order compelling class-wide arbitration) (extra paragraphing added).
8.22.1.7. 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 when a contract isn't negotiated, "[e]xtrinsic 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, Boardwalk Pipeline Partners LP v. Bandera Master Fund LP, 288 A.3d 1083, 1134-35 (Del. 2022) ("this extrinsic evidence may provide a view of what occurred in the periphery").
8.22.1.8. Related: "No drafting history" clauses might be enforced
Example: In a 2023 decision, Vice Chancellor Laster of Delaware provided an extensive review of case law in enforcing the "No Drafting History" provision 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 30.14 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.
Aggressive lawyers, for a variety of self-interested reasons, 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. This Clause seeks to discourage such opportunistic behavior by establishing consequences for it.
If agreed to, this Clause will govern if, in any lawsuit or other dispute relating to the Contract, a party "P" is found, by a tribunal having jurisdiction, to have asserted a position contrary to an express- or unmistakably-implied term of the Contract.
8.23.2. Attorney fee obligation
P must pay or reimburse all attorney fees and costs incurred by any other party to the dispute "OP" through the date (if any) that P formally withdraws the assertion in question:
in a writing communicated to OP and the tribunal, or
if orally, on the record in a proceeding of the tribunal.
OP's attorney fees and costs referred to in subdivision a are those for all aspects of the entire dispute, at all stages of the dispute proceedings, through the date indicated.
Comment
Your author hasn't seen, in actual contracts, language along the lines of this Clause. But drafters might want to consider it, for the reasons discussed in the notes following the language below.
Without language such as that of this Clause, a limitation of liability (e.g., a damages cap or a consequential-damages exclusion) 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 results.
In the first such case, James Construction Group (2022), a construction contract was between a customer and a contractor. The contract excluded consequential damages, stating that "no claim shall be made by [either party] against the other for such damages."
A 5-4 majority of the Texas supreme court held that the contract's exclusion of consequential damages was not really a covenant not to seek such damages — and thus the customer did not breach the contract by seeking such damages from the contractor. See James Constr. Grp., LLC v. Westlake Chem. Corp., 650 S.W.3d 392, 415-18 (Tex. 2022) (reversing court of appeals).
In a strong partial dissent, Justice Boyd (joined by Justices Blacklock and Huddle) argued that "the parties' agreement that 'no claim shall be made' for consequential damages constitutes a covenant not to sue for such damages." One can wonder whether Justice Boyd's view might have prevailed if the contract had abjured the passive voice and said, "neither party shall make any claim" instead of "no claim shall be made …." Id. at 425 (Boyd, J., dissenting).
On the other hand: In Transcor Astra Group (2022), the same court, this time unanimously, seems to have interpreted a settlement agreement's statement of release from liability as implicitly promising not to assert the released claims:
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. We conclude the trial court did not abuse its discretion by awarding Astra its fees and costs.
Perhaps in Transcor Astra the court regarded dispute-settlement agreements as warranting special treatment, having noted that "Texas law encourages parties to resolve their disputes by agreement …." Id. at 473
8.23.3.2. What kinds of assertion might trigger this Clause?
Here are a few examples of assertions that would normally be contrary to the Contract and thus would trigger this Clause:
claiming consequential damages (see Clause 3.2) if the Contract excludes the claimant's recovery of such damages;
claiming damages in excess of an agreed "cap" or other monetary limitation (concerning which, see Clause 3.3);
asserting a purported right, or a purported obligation, that had previously been waived (see Clause 8.68);
asserting a claim that had been released (see the real-world example at 8.23.3);
asserting that a notice took effect at a time inconsistent with the notice provisions stated in the Contract (concerning which, see Clause 6.9);
asserting that the Contract or a related document was amended or otherwise modified in a manner inconsistent with the amendment provisions of the Contract (see Clause 6.1);
an assertion that an action was timely if taken after a deadline stated in the Contract or a related document (for example, a statement of work);
filing a lawsuit or arbitration in a forum inconsistent with a forum-selection clause (concerning which, see Clause 3.6);
asserting that the governing law is that of some jurisdiction other than as stated in a governing-law clause (see Clause 3.7).
(This isn't an exclusive list, of course.)
8.24. Cooperation
When the Contract adopts this Clause, the term "cooperate" (whether or not capitalized) refers to working together with a specified party in good faith, and in a reasonable manner, in pursuit of a specified goal; the term "cooperation" has the corresponding meaning.
If either party asks, the parties will escalate any disagreement about whether a proposed course of action would satisfy the requirements of this Clause.
Comment
This definition is provided to support parties who want to "kick the can down the road" (granted, an overused expression) by deferring discussion of issues when they're reasonably confident that they'll be able to work things out between them.
Prohibitions such as those of the following are sometimes seen in contracts — but they can lead to governmental challenges, as discussed below.
8.25.1. Disparagement Prohibition
Contracts often use the terms discretion, sole discretion, unfettered discretion, and reasonable discretion; this Clause seeks to provide clear meanings for the underlying word discretion — while recognizing that courts might impose their own meanings, as discussed below.
EACH PARTY:
8.25.1.1. Prohibition
Contracts often use the terms discretion, sole discretion, unfettered discretion, and reasonable discretion; this Clause seeks to provide clear meanings for the underlying word discretion — while recognizing that courts might impose their own meanings, as discussed below.
Don't make, to any third party, any disparaging statement:
about any other party to the Contract; nor
about the products or services of that other party.
All disparaging statements to third parties are prohibited, not merely false- or misleading ones.
Disparaging statements of fact, as well as of opinion, to third parties are prohibited.
8.25.1.2. Comments
Paragraph 1: Concerning the term "third party," see the exceptions at 8.25.1.3 below.
Paragraphs 2 and 3 might be points of contention in some contract negotiations — moreover, it might even be unlawful to require another party to agree to such terms, as discussed at 8.25.2.2.
8.25.1.3. Exception for complaints to the other party
Contracts often use the terms discretion, sole discretion, unfettered discretion, and reasonable discretion; this Clause seeks to provide clear meanings for the underlying word discretion — while recognizing that courts might impose their own meanings, as discussed below.
Clause text
This Clause doesn't prohibit you from making legitimate complaints relating to the Contract to any of the following who are involved in the parties' dealings together under the Contract:
the officers, employees, distributors, resellers, and agents of the other party or any of its affiliates.
8.25.1.4. Comment
A. 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.
B. This section is worded to take into account Project44 (2024), 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 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 ¶¶ 13, 22-27 (cleaned up).
Here are couple of examples of disparagement prohibitions that were successfully asserted against parties:
/Example:/foGroup 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).
8.25.2.2. The law might limit nondisparagement provisions
Some jurisdictions might limit a party's ability to enforce a disparagement prohibition — or even make it unlawful to require one. For example:
– In California, Cal. Civ. Code § 1670.8 prohibits such provisions in consumer contracts — with civil penalties for violation. (The limitation to consumer contracts is probably why the Bachelorette disparagement prohibition, cited at 8.25.2.1, wasn't held to be unenforceable.)
(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.)
8.25.2.3. Even a "no names" disparagement might have to have a trial
In Toray Plastics (2022), 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)
8.25.2.4. The NLRB doesn't like anti-disparagement clauses
In 2019, 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.
8.25.2.5. Federal law might prohibit some non-disparagement clauses
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.)
And in Roca Labs (2018), 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).
8.25.2.6. 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.
8.25.2.7. 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).
8.26. Employees' Non-Waivable Rights
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.
Contents:
Nothing in the Contract is to be interpreted as precluding any "employee" (as defined in applicable law) from exercising legal rights that, by law, cannot be waived.
The protected employee legal rights referred to above encompass (where applicable, and without limitation) the rights to do the following:
to speak out about workplace conditions;
to make "whistleblower" disclosures to governmental authorities; and/or
to discuss or disclose information about unlawful acts in the workplace, such as (without limitation) harassment, or discrimination, or any other conduct that the employee has reason to believe is unlawful.
In McLaren Macomb (NLRB 2023), the 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; 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).
In Harper Holdings (2023), 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).
In addition, similar positions have been taken by the Securities and Exchange Commission (SEC) and the Federal Trade Commission (FTC), as discussed at 8.19.12.4.
8.28. Employee Protection
Any company or other organization that enters into a big-dollar contract might want to consider asking for "non-recourse" provisions along the lines of the following this Clause, to try to preclude lawsuits by contract counterparties against the organization's employees and other associated individuals. That's because a dissatisfied counterparty might sue not just the company, but also the company's employees and/or the company's officers, directors, etc.
This Clause will govern whenever both of the following are true:
one party (the "Claimant") makes, or considers making, a claim arising out of or relating to the Contract against another party, whether by suing in court or otherwise; and
the other party has one or more employees or other "Associates," defined below.
8.28.2. May employees, etc., be sued personally?
By signing and delivering the Contract, the Claimant WAIVES and RELEASES, in advance, any and all claims against the other party's Associates — in that capacity — where the claim arises out of or relates to the Contract or any transaction or relationship resulting from the Contract.
And: In entering into the Contract, the Claimant certifies that the Claimant is not relying, and agrees that it will not rely, on any statement or silence by an Associate of another party in his- or her personal capacity, with respect to some or all of the following:
the other party's performance under the Contract; nor
any representation or warranty made in, or in connection with, or as an inducement to enter into, the Contract.
Comment
A. 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 3.9.5.
B. "[I]n that capacity": Of course, if an Associate were to sign the Contract in his or her personal capacity — for example, as a guarantor — then this Clause wouldn't prevent the Claimant from making a claim against the Associate for the Associate's own breach(es) of the Associate's specific obligations under the Contract.
C. See the discussion of reliance waivers at 8.57.
8.28.3. This Clause is to be applied broadly
The Claimant's waiver and release in this Clause are intended to be applied broadly, including, without limitation, to the following:
any claim that the Claimant is entitled to avoid, or to disregard the entity form, of a party;
any claim based on any theory of equity; agency; control; instrumentality; alter ego; domination; sham; single business enterprise; piercing the veil; unfairness; undercapitalization; or otherwise; and
any other attempt to impose the liability of an organizational party on an Associate of any other party.
Comment
This waiver might not provide that much protection for truly bad-actor employees; see the additional discussion at 8.28.5.4.
8.28.4. Definition: "Associate" (for this Clause)
For purposes of this Clause, the term "Associate" of a party refers to the following:
any employee of the party;
any individual contractor of the party who as a practical matter is functioning as an employee of the party;
an officer, member of the board of directors, shareholder, or incorporator of a party that is a corporation;
a manager or member of a party that is a limited-liability company ("LLC");
a limited partner of a limited partnership;
someone holding a comparable position in another type of organization; and
an agent, attorney, or accountant engaged by the party.
8.28.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 3.2.9.3.)
8.28.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 told the driver to put the "bleach" in the bleach tank; the resulting chemical reaction caused significant damage to the facility.
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).
8.28.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:
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.
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.
8.28.5.4. How much protection would this Clause really provide?
This Clause 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 Clause likely protect an individual against tort-based claims. In Keyes (2024), 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). Cf. 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): "[T]he 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]."
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.
But even so: Contractual protective language for individual employees, etc., along the lines of this Clause would be better than nothing.
8.28.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 [BROKEN LINK: sigs-titles] 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 10.1.2.
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.
8.28.5.6. Appendix: Non-recourse language "in the wild"
Consider the following non-recourse clause used in a real-world contract, litigated in 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.
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).
8.28.5.7. Related: The Himalaya clause, from maritime practice
This Clause 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).
8.29. Equitable Relief
A drafter for a contracting party might ask the other party to stipulate that the drafting party will be entitled to "specific performance" or an "injunction" in the event of breach. If the other party agreed to such an "entitlement" stipulation, it'd be a major concession, as discussed at 8.29.1.3. So: This Clause provides a compromise in that regard that will often satisfy all parties.
If this Clause is agreed to, it will apply if a party materially breaches the Contract in a way that (i) is irreparably harming the interests of another party, or (ii) threatens to do so; and/or if such a breach appears imminent.
Upon a proper showing as required by applicable law, the other party will be entitled to a preliminary injunction against you or similar equitable relief.
This Clause 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; for discussion why, see the commentary below at 8.29.1.3.
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 — or worse — such peremptory statements, as discussed at 30.14.
8.29.1.2. Legal background: The plaintiff's burden of proof
We're talking here about two 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.
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.
(For a useful catalog of things that might qualify as irreparable injury – if proved – see Bartholomew (2020); scroll down to its list of bullet points.)
In eBay (2006), 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).
It's a non-trivial task for a claimant to prove that it would be irreparably injured — 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.
So: Contract reviewers being asked to agree to language in this category should pay careful attention to the exact wording, because it could end up significantly disadvantaging the party against which injunctive relief is sought, for the reasons discussed below.
On the other hand: In some cases — where misappropriation of crucial trade secrets is being alleged, for example — the existence of irreparable harm might be pretty obvious; in such a case, it might not be much of a concession for a potential respondent to stipulate in advance to the existence of irreparable harm.
(See also the commentary to 8.9 (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.)
8.29.1.4. Contractual stipulations to irreparable harm have been enforced
Example: In a 2012 decision, 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.
Relatedly, see Clause 8.9 (bond waivers) and its commentary.
8.30. Escrow (FIX - 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
8.31. Fraud Proof
Contents:
Lawyers, and even clients, can sometimes casually throw around allegations of fraud, for tactical reasons discussed in more detail at 3.15.8. Such allegations can make litigation (and arbitration) much more complicated and costly.
Clause text
EACH PARTY:
This Clause applies if you want to allege fraud arising out of or otherwise relating to the Contract, under any legal- or equitable theory.
Prove the allegation by clear and convincing evidence (defined at 7.13).
In your proof of fraud, include reasonable corroboration (defined at 7.18) of any testimony by an interested witness.
Otherwise, your allegation of fraud is WAIVED.
Comment
A. Motivation: To streamline legal proceedings when fraud-like allegations are made, this Clause is intended to lock in the usual American standard of proof in civil cases.
C. Paragraph 3: 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 inH.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).
D. Paragraph 4: For discussion of the corroboration requirement, see the commentary at 7.18.
E. Paragraph 5: This waiver is a signal to a court or arbitrator that is considering a fraud claim covered by this Clause.
8.32. Good-Neighbor
The terms and conditions listed below should help parties get off on the right foot by signaling to each other that they can be counted on to act like "good neighbors."
Clause text
The Common Draft terms listed below are incorporated by reference into the Contract:
For the meaning of incorporation by reference, see 8.34.
8.12: Catch-Up Calls: The parties will check in about their dealings together whenever reasonably requested by either party.
6.4: Escalation to Neutral Advisor Clause: Any disagreements are to be escalated if requested by either party.
6.10: Signature Document Integrity Clause: No party will surreptitiously change a final, agreed signature version of a document before signing and returning it to another party for countersignature.
8.33. Government Subcontract Disclaimer
Each party represents and warrants to the other that the Contract is not a subcontract of a contract between the representing party and any governmental entity.
Comment
This section is a "no surprises" provision: Subcontracts to government contracts might include mandatory "flowdown" obligations as a matter of law; neither party wants to be surprised to learn that the Contract includes such flowdown obligations (see 14.3).
Of course, entire books have been written about government contracting and subcontracting; this section is intended merely to "smoke out" any need to address issues that could arise in such contracts.
8.34. Incorporation by Reference
This Clause explicitly states that, when external materials are incorporated by reference into a document such as the Contract, the parties intend for incorporated material to be part of the document.
(See 29.7 for cautions when incorporating by reference.)
When material is incorporated by reference into the Contract or any related document, the material is considered 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.
Comment
Incorporation by reference — language sources: This Clause 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.
When the Contract includes this Clause, the parties will follow it in any situation in which a party indicated in the Contract (the "Possessor") is to return or destroy particular information of another party (the "Owner").
Comment
A. This Clause 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: • 8.18 (confidential information) and • 8.11 (Business Associate Agreement).
B. Caution: Recipients should think carefully before agreeing to return or destroy information they receive, for reasons discussed at 8.35.7.
8.35.2. Defined term: "Purge" of information
For purposes of this Clause, the Possessor's obligation to "Purge" information requires returning or destroying all copies and other tangible embodiments ("Copies") of the information in the Possessor's possession, custody, or control.
Comment
Concerning "possession, custody, or control," see 7.38.
8.35.3. Purging upon written request (with deadline)
The Possessor need not Purge information unless and until:
the Owner, in writing, asks the Possessor to do so; and
the Possessor receives (or refuses) the request no later than 30 days after termination or expiration of the Contract.
Comment
A. 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.
B. 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.
8.35.4. Exception: Emails, electronic files, etc.
The Possessor need not return or destroy electronic Copies (which would likely be burdensome and expensive).
Example: The Possessor need not return or destroy information in email attachments and system-backup media.
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.
8.35.5. Recommended: Check before destroying copies
The Possessor should consider advising the Owner, in writing and in advance, of the Possessor's intent to destroy "hard Copies" (e.g., printouts) of information to be Purged.
The Possessor need not turn over its Copies unless the Possessor and the Owner have clearly agreed otherwise — for example by agreeing to Option 8.35.6.1 below.
Comment
This to be neighborly is in case the Owner doesn't have its own copies of particular information 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.
8.35.6. Options
No Option below will apply unless the Contract clearly adopts the specific Option in question.
8.35.6.1. Option: Mandatory Check Before Destruction
The Possessor is to make reasonable efforts to advise the Owner, in advance and in writing — it could be by email, for example — that the Possessor intends to destroy "hard Copies" of information to be Purged, e.g., printouts, etc.
The Possessor is not to destroy such hard Copies unless:
the Owner indicates in writing that the Owner does not need the Copies in question; or
the Owner does not respond to the Posssessor's written advice on or before the date ten business days: (i) after the Owner receives or refuses the advice, or (ii) after the Possessor makes the required reasonable efforts to advise the Owner of the Possessor's intent as stated above but cannot make contact with the Owner.
If the Owner asks, the Possessor is to turn over those hard Copies to the Owner, at no charge (but the Possessor may require the Owner to reimburse the Possessor for reasonable out-of-pocket charges for shipping and/or insurance). This Option 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.)
8.35.6.2. Option: Written Purge Certification Upon Request
This Option will apply if the Owner asks — within a reasonable time after the Purge requirement of this Clause within has become applicable — for the Possessor to certify that the Possessor has complied with the Purge requirement.
The Possessor is to make a reasonable inquiry to check how well the Possessor has complied with the Purge requirement.
The Possessor is to provide the Owner with a written certificate of compliance that:
notes any known compliance exceptions; and
for each such exception, notes whether and how the exception is authorized by the Contract — unless doing so is prohibited by applicable law or otherwise authorized by the Contract, for example if the Possessor provided Copies to one or more law-enforcement authorities that have requested that the Owner not be told.
is signed (possibly electronically) by someone having authority to make a binding commitment on the Possessor's behalf (or by the Possessor him- or herself if an individual).
circulating the draft certificate to its relevant people for their review; and
sending the unsigned draft certificate to the Owner for possible feedback.
8.35.6.3. Comment
A. This Option 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.
B. 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.
8.35.7. Reading
Possessors of information "owned" by another party should think carefully before agreeing to return or destroy the information, such as at 8.19.1 (return of confidential information). Here's why:
1. Epitomizing the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings), sometimes both parties forget about the return-or-destruction obligation — which 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 a 2020 Federal Circuit decision. 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).
• 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.
2. In many situations, the possessor will want a set of archive copies of what it actually received from the owner, to guard against an owner's later claiming that it had provided more documents or information to the possessor than it actually did. See, e.g., the exception for archive copies in Option 8.19.1 (return or destruction of confidential information); 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.
3. If the possessor created the documents for the owner, then the possessor might want (or even be legally required) to maintain its own records of what it created.
4. The possessor will no doubt have other uses for the time and money it would take to purge the information.
This Clause will govern when a party (a "Supplier") represents or warrants to another signatory party to the Contract — each such party is referred to here as a "Beneficiary" — that one or more specified products and/or services does not infringe intellectual property rights of a third party. Such a warranty is referred to as an "Infringement Warranty," and is defined further below.
If this Clause is listed in the Contract, it means that:
the parties expect a clearly-indicated party to be a Supplier; and
that party is making the Infringement Warranty to another clearly-indicated party as a Beneficiary.
Comment
This Clause 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 3.17.
8.36.2. Warranty coverage: Covered Items as delivered
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 —
as delivered to the Beneficiary under the Contract, by the Supplier or on the Supplier's behalf; or
as otherwise clearly agreed in writing by the Supplier.
Comment
A. The warranty of this Clause extends to Covered Items as delivered, as opposed to warranting the items' future performance; see the discussion of this topic at 3.18.7.
B. Drafters might want to consider whether an Infringement Warranty should apply: (i) solely to goods and/or services provided directly or indirectly by the Supplier itself, e.g., goods manufactured by the Supplier and sold via a distribution channel; or (ii) also to goods and services manufactured and/or distributed by others.
8.36.3. Who can assert an Infringement Warranty
For emphasis, only the Beneficiary is intended to benefit from an Infringement Warranty.
For purposes of this Clause, the term "third party" excludes affiliates of any Beneficiary.
Comment
This exclusion is intended to help avoid possible collusion between the Beneficiary and its affiliates. (See also 8.66 (third-party beneficiaries).
8.36.4. Warranty in three parts: Copyrights, trade secrets, patents
An "Infringement Warranty" consists solely of the following — each as limited by the terms of this Clause — unless clearly agreed otherwise in writing:
A Patent Warranty is a warranty that so far as the Supplier is aware, the Covered Item does not 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.
In addition, ifthe Supplier unambiguously provides the Beneficiary with instructions for using a Covered Item (for example, in a user manual), then the Patent Warranty also applies to use of the Covered Item — by the Beneficiary and/or by other any users unambiguously specified in the Contract — in accordance with those instructions.
The Supplier does not represent or warrant that it has conducted any particular search or other investigation about any Patent Warranty unless the Supplier clearly states otherwise in writing.
Comment
A. See the commentary at 8.36.5 for why the Patent Warranty is different than the Copyright & Trade Secret Warranties.
B. Subdivision a: 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."
C. Subdivision b addresses the possibility that the Beneficiary 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 [BROKEN LINK: infr-warr-scope-pat-addl-cmt].
D. Subdivision c: For its own risk-assessment purposes, the Supplier might want to consider commissioning its own "freedom to operate" patent investigation and an opinion of counsel, to provide the Supplier with at least some comfort on in this regard — because a Covered Item might infringe a patent without the Supplier (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, as discussed in the articles cited at the following footnote:
8.36.7. No coverage for Beneficiary-provided specifications
This section applies to any claim of infringement where both of the following are true:
the claimed infringement arises from a Covered Item's compliance with a written- or oral specification; and
the specification was provided by the Beneficiary and/or by one or more third parties on behalf of the Beneficiary.
The Supplier's Infringement Warranty does not extend to any claim of infringement of the kind described in subdivision a.
If the Supplier asserts that a Covered Item complied with an oral Beneficiary specification, that assertion will not be effective unless supported by clear and convincing evidence.
Comment
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 19.3] 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.)
8.36.8. No coverage for "combination" infringements
An Infringement Warranty does not extend to any claim of infringement where both of the following are true:
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
no claim of infringement is made in respect of: (i) the Covered Item itself, nor (ii) the use of the Covered Item apart from the combination.
Comment
Caution: The warranty disclaimer of this section might not be enough to save the Supplier 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).
8.36.9. EXCLUSIVE warranty about infringement
An Infringement Warranty states the EXCLUSIVE TERMS of any and all 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:
DISCLAIMED by the Supplier; and
WAIVED by each party that might make a claim against the Supplier.
Comment
See also the discussion of implied-warranty disclaimers at 3.8.
The Supplier is to comply with the remedy provisions below in this Clause if one or more of the following "Triggering Events" occurs:
A court of competent jurisdiction enjoins the Beneficiary from using a Covered Product — as a result of an infringement claim covered by an Infringement Warranty (a "Covered Infringement Claim") — and for any reason you don't have the injunction stayed or overturned; or
You give notice to the Beneficiary that you've settled a Covered Infringement Claim on terms that call for the Beneficiary to stop using a Covered Product; or
You give notice to the Beneficiary that you've determined, in your reasonable judgment, that the Beneficiary should stop using a Covered Product because of a Covered Infringement Claim.
Comment
These three items are basic "stop use" events that might occur in an IP infringement case.
8.36.11. Beneficiary's recourse (part 2): Plans A through C
SUPPLIER: If a Triggering Event occurs in respect of a Covered Product, then: Proceed in accordance with one or more of Plans A through C below.
Plan A – modification or replacement: If you select this plan: Attempt to modify or replace the Covered Product with a non-infringing substitute that, in all respects material to the Contract, performs the same functions as the replaced deliverable.
Plan B – license: If you select this plan: Try to procure for the Beneficiary — at your own expense — a license to continue using the Covered Product under the IP right that is the basis for the infringement claim.
Plan C – refund: If you're unable to follow Plan A or Plan B, or you judge that neither Plan A nor Plan B is commercially feasible, then: Do the following:
Advise the Beneficiary to stop using the deliverable; and
Give the Beneficiary a refund in an amount computed as specified at section 8.36.12 below.
CUSTOMER: The choice of which Plan(s) to follow, and when, is up to the Supplier in its sole discretion, as long as the Supplier follows at least one of those Plans.
Comment
Plans A through C seem to be generally accepted as a sensible protocol for suppliers to follow in case of a Triggering Event.
8.36.12. Beneficiary's recourse (part 3): Computation of refund
SUPPLIER: If you proceed under Plan C above, then: Issue the Beneficiary a refundable credit as stated in this section.
The amount of the refund is to be:
the amount paid by the Beneficiary 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 paragraph xxx or paragraph xxx as applicable.
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 will be 36 months (based on the 36-month IRS depreciation period for computer-software licenses).
Hypothetical example: Suppose that:
The Beneficiary paid the Supplier a one-time fee of $400 for the permanent right to use the Covered Product.
The Supplier proceeds 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 to the Supplier.
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:
The Beneficiary paid the Supplier a one-time fee of $100 for the right to use a Covered Product for one year.
The Supplier 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 will be $25, i.e., ¼ of the $100 paid to the Supplier.
8.36.13. No responsibility for post-refund use by Beneficiary
BENEFICIARY: This section will apply if the Supplier proceeds under Plan C (refund) at section 8.36.11 above.
BENEFICIARY: The Supplier won't be responsible for any infringing use of a Covered Item, by you or any other user authorized by the Contract, beginning after a short-but-reasonable time for you to conduct a prompt, orderly transition away from the use in question ("post-transition infringing use").
BENEFICIARY: Defend and indemnify the Supplier and its Protected Group against any claim of infringement arising from such post-transition infringing use of the Covered Item.
Comment
This section represents a sensible compromise: If the Supplier gives the Beneficiary a refund for a deliverable that's accused of infringement, then the Supplier shouldn't be expected to be responsible for any subsequent, potentially-infringing use of the deliverable.
8.36.14. EXCLUSIVE REMEDY
The Beneficiary's recourses stated in this Clause are the EXCLUSIVE REMEDIES to which the Beneficiary is entitled — from the Supplier or any person affiliated with the Supplier — for:
any breach of an Infringement Warranty; and/or
any other alleged- or actual infringement of third-party intellectual property rights by, or attributable to, the Supplier.
8.36.15. Option: No Inconsistent Third-Party Assertions
This Option applies to each Copyright-, Trade Secret, and/or Patent Warranty provided by the Supplier (if any).
The Supplier is deemed to represent, solely to the Beneficiary, that, so far as the Supplier is aware, no party has asserted that any Covered Item fails to comply with any part of the Infringement Warranty.
Comment
This Option might provide a Beneficiary 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.
8.36.16.1. The broader scope of Copyright & Trade-Secret Warranties
The Copyright & Trade-Secret Warranty has a broader scope than the Patent Warranty (8.36.6). Why is that? In a nutshell:
To infringe someone's copyright, the Supplier would have to copy "protected expression" that's contained in the copyrighted work, which implies direct- or indirect access to the work.
Likewise, to misappropriate someone's trade secret, the Supplier would have to have had direct- or indirect access to the trade secret, under conditions indicating that the Supplier had a duty, by agreement or otherwise, to preserve the trade secret in confidence.
8.36.16.2. Why the Patent Warranty is narrower
The Patent Warranty is narrower because a Covered Item could infringe an issued patent — or a future patent — without the Supplier's even knowing that the patent exists. This means that the Supplier 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.
8.37. Inspections
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; see some tragic examples discussed beginning at 8.37.12.2 below.
For discussion of specific additional points, see 8.37.12.
When agreed to, this Clause entitles a party (or parties) clearly so indicated in the Contract (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.
For convenience, the singular term "Inspector" is used in this Clause even for cases where there are multiple Inspectors.
Comment
In many contexts, inspectors of physical materials use machines to run tests.
8.37.1.1. Definition: Good reason
For purposes of this Clause and other inspection-related provisions of the Contract, 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, or (ii) material breach of the Contract, in either case by, or attributable to, the Host.
The Inspecting Party is to give the Host reasonable advance notice of each requested inspection.
The Inspecting Party is not to ask for inspections except at reasonable intervals.
The Host may make reasonable 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 (absent good reason).
Comment
A. Subdivision a: Advance notice is good — at least when fraud isn't strongly suspected — to give the Host a chance to fix minor problems beforehand and thus to help all parties save on inspection costs.
B. Subdivision b: Too-frequent inspections could be burdensome and costly for the Host.
C. Subdivision c: Someone has to decide the details; this section represents a sensible compromise.
8.37.3. How much access will the Inspector have?
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:
they are reasonably related to the subject of the inspection, and
they do not come within one or more of the exceptions at § 8.37.5 below.
8.37.4. What kind of cooperating is the Host to provide?
The Host is to direct its people to provide reasonable cooperation with the Inspector, including (without limitation):
answering, completely and honestly, all reasonable questions from the Inspector; and
noting any known limitations of their answers.
8.37.5. Withholding of certain information
The Host may withhold, in the Host's sole discrection, some or all of the following "off-limits information" from the Inspectors:
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;
trade secrets; and/or
any other categories of off-limits information that are specifically agreed to in the Contract.
Comment
A. 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).
B. 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.
8.37.6. Professional conduct standard: For all concerned
Everyone involved in the inspection is to comply with the following:
Clause 8.63 (site visits) during any visits to another party's physical premises or computer system; and
Clause 8.17 (computer-system access) when accessing another party's computer system(s) and similar systems.
8.37.7. Additional conduct standards for Inspectors
Each Inspector is to act in a professional manner at all times while interacting with the Host, the Host's personnel, and the Host's facilities, records, etc.
Each Inspector is to comply with any generally-accepted standards — both procedural and substantive — for the relevant type of inspection, for example, GAAP and/or IFRS rules; electrical- or plumbing codes; AICPA rules; etc.
***** Comment :CMT:
See generally Clause 8.18 concerning confidential information.
8.37.8. Required: Escalation of disagreements
The Host and Inspecting Party are to escalate, as provided in Clause 6.5 and if necessary, Clause 6.4, any disagreement about how any imprecise term in this Clause should be applied. Examples:
This allows the parties — if desired — to defer in-the-weeds discussions.
8.37.9. Confidentiality
This section applies to the Inspecting Party and and each Inspector, each referred to here as a "Recipient."
The Recipient is to 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 gets access via any inspection under this Clause.
(Unless the Host first agrees otherwise in writing:) An Inspector is not to disclose to the Inspecting Party any more information derived from the inspection than:
whether the inspection revealed a discrepancy reportable under the Contract, and if so,
the size and general nature of the discrepancy (if applicable),
The Recipient is not to use the Host's confidential information except to the extent necessary for:
correction of any discrepancies identified in the inspection for which you bear any responsibility; and/or
enforcement of the Inspecting Party's rights under the Contract.
8.37.10. Survival of this Clause
The inspection-related provisions of the Contract, including but not limited to those of this Clause:
will survive any termination or expiration of the Contract — but only as to matters that would have been subject to inspection before termination or expiration; and
will remain subject to all deadlines and other limitations stated in the Contract.
Comment
Having inspection provisions survive termination (or expiration) could be important, as discussed at [BROKEN LINK: surv-imp-cmt].
8.37.11. Option: Host Flowdown Requirement
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 Contract, the subcontractor is legally obligated to do the following:
allow the Inspecting Party to conduct inspections (including but not limited to audits, where applicable) as provided in the Contract;
allow the subcontractor to deal directly with the Inspecting Party and Inspector in that connection; and
include substantially the same requirements in any sub-subcontract that the subcontractor enters into.
This Option does not otherwise address whether, nor how, any party may engage subcontractors.
Comment
See generally the discussion of "flowdowns" at 14.3.
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.
8.37.12.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.
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."
8.37.12.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.
The definitions in this Clause, compiled from typical contract terms, are intended in part for students and other newcomers to the field; they spell out in some detail what intellectual-property ("IP") professionals typically know implicitly but seldom state explicitly.
"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 capitalized) refers broadly to:
approaches, concepts, developments, discoveries, formulae, ideas, improvements, inventions, know-how, methodologies, plans, procedures, processes, techniques, and technology, whether or not patentable;
artwork, audio materials, graphics, icons, music, software, writings, and other works of authorship;
designs, whether or not patentable or copyrightable;
trademarks, service marks, logos, trade names, and the goodwill associated with each;
trade secrets and other confidential information;
mask works; and
all other forms of intellectual property recognized by law.
8.38.2. 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:
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 8.38.2;
all rights (whether registered or unregistered) in, or arising under laws concerning IP assets (see 8.38.1 above);
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;
any right to file such an application; and
any right to claim priority for such an application.
Comment
A. 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.
B. 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.
8.38.3. Definition: Owner and Ownership (of 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.
"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.
Comment
A. This Clause 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.
B. (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.)
8.38.4. Definitions: License; Licensee; etc.
"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 8.38.4.
"IP-Triggering Activities" refers to engaging in activities that could inge one or more IP rights of the Owner ("Owner IP rights").
"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.
"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.
"Licensee" (whether or not capitalized) refers to a party granted an IP license by an Owner.
In case of doubt, an IP license does not "authorize" the Licensee to engage in any particular activity.
Comment
A. 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.
B. 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).
C. 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.
8.39. IP Ownership Clause
This Clause sets out pretty-standard procedures for dealing with ownership of intellectual property, with:
1. baseline default rules about who owns what (unless the Contract says otherwise); and
2. procedures for confirmation and/or transfers of ownership.
When this Clause is part of the Contract, it will apply when both of the following are true:
one or more parties indicated in the Contract is involved in creating new subject matter under the Contract; and
the new subject matter could include "IP," as defined in Clause 8.38, which is incorporated by reference.
Comment
A. Caution: A party assigning IP rights might not want to give up trademark rights, as discussed at 8.39.17.1.
B. For extensive additional background information about the legal rules governing IP ownership, see [BROKEN LINK: ip-own-pat-notes] (patents); 11.16 (copyrights); and [BROKEN LINK: ip-own-addl] (other additional notes).
8.39.2. Ownership of pre-existing IP will not change.
The Contract does not transfer ownership, and does not entitle any party to demand that another party transfer ownership, of any pre-existing IP unless the Contract clearly says otherwise.
Comment
A. 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).
B. 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 8.39.17.6.
8.39.3. Who will own newly-created IP (if any)?
This section applies as between the parties unless the Contract clearly indicates otherwise.
Each party will own whatever IP that it creates on its own under the Contract (if any).
The parties will jointly own — in equal, undivided interests — any IP that they jointly create under the Contract. (See also below concerning joint works.)
As between the parties, IP created by any party under the Contract will not be a "work made for hire" unless the Contract clearly says so.
Comment
A. Subdivision 1: Concerning the language, "as between the parties," see 9.6. Here, that language recognizes that other factors — such as preexisting contracts — might affect ownership of newly-created IP.
B. Subdivision 2 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 Contract by either party." QUESTION: Should Toolkit Items (8.39.4) be excluded from such an override?
C. Caution: See [BROKEN LINK: stan-roche] 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.
D. Subdivision 3: 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 8.39.17.3.
E. Subdivision 4 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 11.16.2 and 11.16.3.)
F. Again, 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 8.39.17.6.
8.39.4. Ownership of newly-created "Toolkit Items" will not change.
Even if other IP is transferred under the Contract, ownership of "Toolkit Items" will not change, even if created under the Contract — that term refers to any concept, idea, invention, strategy, procedure, architecture, or other work (each, an "Item"), where all of the following are true:
the Item is, in whole or in part, created by a party in the course of performing under the Contract;
(if the creating party is a provider performing services for a customer:) the Item is not specific, and/or is not unique, to the customer and its business; and
the item does not encompass Confidential Information, as defined in 8.18: Confidential Information Clause, of another party.
Comment
"Toolkit Items" are treated specially here because sometimes a customer will take the overbroad view, "if we paid for it, we own it," which makes little sense economically, as discussed at 8.39.17.5.
8.39.5. For jointly-owned IP, each party will have use- and license rights.
The stated party or parties may authorize others to use jointly-created IP, in any manner that would be allowed to the authorizing party itself under the Contract, including without limitation:
use of the IP for the authorizing party's benefit; and
use of the IP for the user's own benefit as a licensee of the authorizing party.
B. Subdivision 1 is an example of what's sometimes referred to generically as "have-made rights." Example: In a 2018 Second Circuit decision, 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).
8.39.6. Joint owners need not share proceeds from their use or licensing.
This section applies if a party, referred to as "A," makes use of (or licenses) IP that A jointly created with another party "B."
In that situation, A need not share profits with B, nor otherwise account to B, for A's use or licensing.
8.39.7. How are non-transferrable moral rights, etc., to be handled?
This section will apply if, by law, any moral rights or other intellectual property rights in the specified IP cannot be assigned.
The party possessing such non-assignable rights hereby grants to the Owner a perpetual, irrevocable, worldwide, royalty-free, fully transferable license, under all such non-assignable rights.
Comment
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.
8.39.8. Each party is to have suitable agreements with employees, etc.
Each party other than the Owner is to ensure 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 Clause.
Where applicable, such agreements must also be "notarized" (acknowledged) by the signer(s).
For the avoidance of doubt: subdivision 1 in itself neither authorizes nor prohibits the use of subcontractors by any party.
Comment
A. 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). See generally this annotated flowchart that the present author prepared some years ago.
B. 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.
C. 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 8.39.17.6 — but the associated litigation would likely be an expensive headache for all concerned.
8.39.9.Future transferred IP rights are transferred now.
This section will apply if, under the Contract:
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
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.
By entering into the Contract, ABC assigns to the Owner — effective immediately upon ABC's entry into the Contract — all right, title, and interest in all such specified, future-created IP.
If, by law, any such right, title, and/or interest cannot be assigned now for future IP creations as in subdivision b above, then at the Owner's request at any time, ABC is to promptly assign to the Owner all such right, title, and interest in the specified IP (see also 8.39.10 concerning written documentation of the assignment).
Comment
Concerning the "effective immediately" language, see the discussion at [BROKEN LINK: ip-present-xfr-cmt].
8.39.10. Each party will provide other written IP transfers upon request.
This section applies whenever a party (a "former owner") is required to "assign" intellectual property in or under the Contract to another party (the "new owner").
When so requested in writing by the new owner, the former owner must permanently and irrevocably transfer all ownership of the IP, in writing, to the new owner and the new owner's successors and assigns.
Comment
This is an "upon request" obligation, on the principle that the new owner is more likely to be paying attention — and it shouldn't be deemed a breach of contract for the former owner not to remember to provide a written assignment without a request.
8.39.11. Ownership-transfer documents must meet certain requirements.
Each written transfer- or confirmation of ownership under this Clause must encompass, as applicable to the type of IP in question:
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;
any and all patents issuing on each patent application described in subdivision 1;
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;
any and all registrations for the copyright or trademark rights (if any) in the specified IP;
any and all applications to register the copyright or trademark rights (if any) in the specified IP;
any other intellectual property rights, of whatever nature, in the specified IP, together with any applications for, or issued registrations for, the same; and
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.
Comment
Subdivision 7: Under U.S. law, the rightt 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).
8.39.12. Each party is to provide other documents if asked.
This section applies if and when reasonably requested by the new- or existing owner from time to time.
The former owner is to cause appropriate additional documents to be signed and delivered to the new owner to establish, and/or confirm, the new owner's rights in the specified IP.
Comment
Such documents could include, without limitation: patent applications; copyright- or trademark registration applications; and assignment documents.
8.39.13. New owners must bear ownership-transfer expenses.
As between the former owner and the new owner, the new owner must pay for preparing and filing any such documents unless otherwise agreed in writing.
Comment
This is standard practice; see also 2.9 (expense reimbursement).
8.39.14. No additional compensation for ownership transfers.
For the avoidance of doubt: The former owner will not be entitled to additional compensation for doing the things required by this Clause, over and above any compensation clearly stated in the Contract.
Comment
This is a roadblock provision.
8.39.15. Survival of IP-ownership provisions
All rights and obligations of this Clause will survive any termination or expiration of the Contract for IP created before termination or expiration.
8.39.16. Option: Co-Owner Participation in Infringement Lawsuits
Upon request, all other co-owners of IP must join in any one co-owner's actions against infringers of the associated IP rights.
Comment
A. 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), citingEthicon, Inc. v. United States Surgical Corp., 135 F.3d 1456 (Fed. Cir. 1998).
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.
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: A California statute: (i) limits an employer's ability to require employees to assign their spare-time inventions to the employer; (ii) states that contrary provisions in employment agreements are unenforceable; and (iii) prohibits employers from requiring such provisions as a condition of employment or continued employment. See Cal. Labor Code §§ 2870-2872; Whitewater West Industries, Ltd. v. Alleshouse, 981 F.3d 1045 (Fed. Cir. 2020) (holding that invention-assignment provision in contract was void under California law).
In addition, a federal court held that a provision in an employment agreement, purporting to require assignment of post-employment inventions, was effectively a noncompetition covenant that was unenforceable under a separate provision of California law. See Whitewater West Industries, 981 F.3d at 1052-53, citingCal. Bus. & Prof. Code § 16600
8.39.17.3. IP joint owners' obligations to each other
A. 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
B. 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
8.39.17.4. Shouldn't a services customer always own newly-created IP? (No.)
A. 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."
B. But under the law, that might well not be the case, at least in the U.S., where with limited exceptions:
an author or inventor owns the intellectual-property rights in his- or her creations;
likewise as between the Provider and its Customer, the Provider will own the work product of the Provider's employees (typically because of invention-assignment agreements, but often as a matter of law).
C. 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:
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.
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.
D. To be sure: In some circumstances it might make more sense for the Customer to own the resulting IP. For example, • the Customer might engage a software developer to design and build a new software package that the customer wants to use in its business, and so • the Customer understandably wants to own the copyright and other IP rights in the new software.
8.39.17.5. 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 11.16.3), then the parties can settle in for some expensive litigation. See, e.g., the cases summarized at 8.39.17.6.
In the present author's experience, a reasonable compromise is the following, which is reflected in this Clause:
– The customer owns any newly-created IP that's unique to the customer's businessor 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.
8.39.17.6. 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 the footnote to get the basic idea.31
8.40. IP Infringement by Others
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.)
8.40.1. What does it mean to agree to this Clause?
When this Clause is included in the Contract (or is otherwise agreed to), it will govern when both of the following are true:
a party to the Contract (referred to as the "Owner") owns — or can otherwise legally assert — one or more intellectual-property rights (see the definition at 8.38.2) concerning one or more "Offerings" of goods, services, and/or other items; and
any other party to the Contract (the "Reporter") suspects that unauthorized use, copying, distribution, or modification of an Offering (collectively, "Unauthorized Activities") might be taking place.
Comment
A. This Clause 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 [BROKEN LINK: infr-warr-scope-pat-addl-cmt].)
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.
B. This Clause 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.
8.40.2. What action(s) must the Reporter take?
In such a situation, the Reporter is to do the following:
promptly advise the Owner of the situation;
provide the Owner and/or its representatives (for example, legal counsel) with all relevant information reasonably requested about the Unauthorized Activities; and
provide reasonable cooperation with any efforts by, or on behalf of, the Owner to prevent, stop, or limit the Unauthorized Activities ("Policing Efforts").
The extent to which the Reporter's requested cooperation is to be considered "reasonable" will depend (in part) on (i) the likely expense of such cooperation, and (ii) the extent to which Owner agrees to bear that expense.
Any disagreement about the reasonableness of requested cooperation is to be handled by (nonbinding) escalation as stated at 6.4.
8.40.3. May the Reporter take independent action?
The Reporter is not to undertake any Policing Efforts of its own without the Owner's prior written approval.
Comment
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.
8.41. IP Rights Challenges Clause
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 Clause 8.67.
"Other Party" refers to any other party to the Contract.
Comment
Paragraph 2: Under U.S. law, the "Owner" might possibly be an exclusive licensee instead of the "record owner" of the IP in question.
8.41.2. Applicability of this Clause
When this Clause is part of the Contract, 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:
the third party putatively infringes the Owner IP Right; and/or
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.
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:
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;
an affirmative defense or counterclaim of invalidity or unenforceability of the Owner IP Right;
a petition for an inter partes review of a patent, and/or
a petition to cancel a trademark- or copyright registration.
The foregoing is not necessarily a complete list of possible types of IP challenge.
8.41.3. Non-Owner's reporting and cooperation obligation
This section will apply if any Other Party becomes aware of any Challenge to one or more Owner IP Rights.
The Other Party must promptly advise the Owner, in writing, about the Challenge.
The Other Party must provide the Owner (and the Owner's counsel) with reasonable information and cooperation concerning the Challenge, on an ongoing basis.
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).
Comment
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.
8.41.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 Contract provides otherwise.
Comment
The Owner will certainly want to maintain control of the response to the Challenge.
8.41.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 Clause 8.18 (confidential information) will govern.
Comment
If litigation ensues, this section might be superseded by a protective order entered by the court.
8.41.6. Owner responsibility for Challenge costs
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.
Subdivision 1 applies at all phases of a Challenge proceeding, including but not limited to any appeals.
For purposes of subdivision 1:
The term "proceeding" refers to litigation; arbitration; and administrative actions such as, without limitation, inter-partes review actions; and
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.
The Other Party is not obligated to fund or reimburse any Owner expense in respect of the Challenge unless the Contract clearly says otherwise.
Comment
This section should provide some comfort to Other Parties.
Subdivision 1: For discussion of the phrase "as between," see 9.6.
8.41.7. Owner entitlement to monetary recovery
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.
For emphasis, subdivision 1 extends, without limitation, to any awards of damages, profits, costs, and/or attorney fees.
Comment
A. In some agreements, the Owner and the Other Party might agree to divide monetary recoveries among them.
B. 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).
8.42. Jury Trial Waiver Clause
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.
This Clause applies to the greatest extent not specifically prohibited by law.
Each party WAIVES any right that the party might have to a trial by jury for any dispute arising out of the Contract.
Each party certifies that the party has not relied 8.57 — and it promises that it will not rely — on anyone's alleged statement that this waiver would not be enforced.
8.42.1.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."
8.42.1.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).
8.42.1.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 in the commentary to section [BROKEN LINK: ArbJuryWaivSec] of Clause 8.1 (arbitration).
(Arbitration can be expensive as well, as discussed in the commentary at 8.2.13; more and more companies are taking that into account in deciding whether to require consumers and employees to agree to arbitration.
8.43. Lawyer Involvement on Request
The first thing we do is, let's kill all the lawyers. —the murderous Dick the Butcher, in Act IV, Scene II of William Shakespeare, Henry VI, Part II (which of course was an indirect compliment to lawyers' crucial role in civilized society).
Provide lawyer contact information upon request: If a party A reasonably asks another party B, then B is to promptly provide A with contact information for B's legal counsel for the matter in question — if any.
Lawyers may copy other parties' business people on emails, etc.: If A requests, then B is to instruct 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, as long as:
A's lawyer(s) also open-copy B's legal counsel; and
A's lawyer(s) are not doing this in a manifestly-inappropriate way.
Limitations: In case a question arises: This Clause does not obligate A to pay, or reimburse B for, the fees or expenses of B's legal counsel.
Comment
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. This could be due to embarrassment, or fear of what might get back to superiors — see the related discussion of this fear at 6.5 — or perhaps just a desire to save money on legal fees. To help each party to deal with such situations, this Clause 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?"
Comment
This Clause doesn't obligate B to engage legal counsel for any particular matter. • Of course, if B has in-house counsel, then any request by A to talk to B's in-house counsel should presumptively be reasonable, because presumably it wouldn't cost B any money in outside-counsel expenses — moreover, B's in-house counsel would always be free to cut off the discussion if A was being unreasonable.
Comment
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.
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 would 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.)
When this Clause is adopted in an agreement, it means that the parties intend for the agreement to be a "letter of intent" ("LOI").
Comment
This Clause is designed to be adopted in a short-form agreement (e.g., a term sheet or an email exchange) to turn it into an LOI.
8.44.2. The LOI is partial and preliminary.
The Contract is only a partial preliminary, provisionally-agreed document concerning a possible future business arrangement (an "Arrangement") that the parties are discussing; the parties have not agreed to all of the Arrangement's material terms.
8.44.3. Only a final written agreement will suffice.
Except as otherwise stated in the Contract, the parties do not intend to be 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.
Comment
LOI language requiring a final written agreement should usually be enough to keep prior written exchanges from being binding. For 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.
Example: Likewise, the Texas supreme court affirmed a summary judgment that, as a matter of law, a particular email exchange by parties did not create a binding agreement between them, due to a "No Obligation" clause in a confidentiality agreement. See 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); see also See Energy Transfer Partners, L.P. v. Enterprise Products Partners, 593 S.W.3d 732 (Tex. 2020), affirming529 S.W.3d 531 (Tex. App.—Dallas 2017) (disclaimer in LOI precluded claim of de facto partnership).
Example: In a Seventh Circuit opinion, Judge Frank Easterbrook explained the policy reason for not holding parties to be bound when they have explicitly stated their intent not to be bound — namely that it frees the parties up to negotiate contracts one issue at a time:
Illinois is averse to enforcing tentative agreements that are expressly contingent on the signing of formal or final documents. And for good reason. Often the parties agree on some items (such as how many trucks the buyer wants) while others (such as the price) require more negotiation.
* * *
Parties may negotiate toward closing a deal 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.
This dispute should have been resolved in Volvo's favor on summary judgment.
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 after jury verdict awarding plaintiff more than $5MM) (cleaned up, formatting lightly revised).
8.44.4. A few terms in the LOI are binding.
The only binding terms of the Contract are those of this Clause plus those — if any — concerning the following (listed alphabetically): • confidentiality of the parties' discussions; • exclusivity of the parties' discussions — for emphasis, neither party is agreeing to any kind of exclusivity in respect of their discussions relating to the Arrangement unless the Contract clearly says so; • expenses incurred by the parties in their discussions; • forum selection, a.k.a. choice of forum; • good-faith negotiation; • governing law, a.k.a. choice of law; • limitations of liability; • no-shop; • no solicitation of personnel; • reliance waiver, a.k.a. outside statements do not count; • remedy limitations; • warranty disclaimers; and • any other terms that the LOI explicitly states are binding.
Comment
Caution: Don't disclaim all LOI enforceability. 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. This meant that the agreement's confidentiality provision was not enforceable. See Mueller v. Mueller, 102 Cal. App. 5th 593 (2024) (affirming family-court judgment).
8.44.5. An early start would not replace a final written agreement.
If a party were to start early on its activities under the Arrangement, then:
The party's efforts on that score would be at the party's own expense and risk (legal risk and otherwise); and
the early start would not signify anything else, such as (for example) the party's assent to form a "partnership" as that term is understood in the law.
Comment
A. This section addresses a possible (but unlikely) concern:
• It sometimes happens that when parties sign a letter of intent, their business people decide to "get going" before the lawyers finish the final, formal contract. For example, 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).
• Under state law, however, a partnership could arise as a matter of law, based on the parties' conduct, even without a contract. 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).
• And that could present an opening for a party to claim that an offer was accepted by performance. Example: In an Alabama case, the state's supreme court affirmed a lower court's ruling that a mother's farm was the property of an implied family partnership to raise chickens. See Penney v. Penney, 355 So.3d 303 (Ala. 2021). Partial counterexample: In an initial victory, a giant energy company urged such a claim to a Dallas jury after being jilted by its prospective partner in a pipeline project, winning a judgment of more than $535 million — but the 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), affirming529 S.W.3d 531 (Tex. App.—Dallas 2017) (disclaimer in LOI precluded claim of de facto partnership).
B. In this section, the "were to start" and "would be" language is what the Seventh Circuit described as "aspirational" language, which militates against finding that the parties intended to be bound. See KAP Holdings, LLC v. Mar-Cone Appliance Parts Co., 55 F.4th 517, 524 (7th Cir. 2022) (affirming dismissal of complaint: parties' alleged oral agreement to a term sheet failed to create a binding contract).
8.44.6. Can a party withdraw from Arrangement discussions?
Withdrawal from discussions: Unless the LOI clearly says otherwise, any party ("P") may withdraw from discussions of the Arrangement: • at any time, • in P's sole and unfettered discretion, • for any reason or no reason, • without incurring any obligation or liability — under any theory, including any applicable implied covenant of good faith and fair dealing — for the withdrawal itself.
Comment
A. 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., 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); 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."
(Caution: The same is not true for a so-called "agreement to agree," which in the U.S. would be unenforceable, as discussed at 9.1.)
B. There's case law that, when parties sign even a nonbinding letter of intent or other so-called "Type II" preliminary agreement, they've implicitly committed to negotiating in good faith to try to get to a final agreement. See Adjustrite Sys., Inc. v. GAB Bus. Svcs., Inc., 145 F.3d 543, 548 (2d Cir. 1998) (affirming summary judgment that "preliminary agreement" was unenforceable agreement to agree), quoted in Sierra Club v. Franklin Cty. Power of Ill., 546 F.3d 918, 932 (7th Cir. 2008) and 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); cf.
In contrast, a so-called "Type I" preliminary agreement is considered "fully binding as to all material elements of the underlying contract …." Cambridge Capital, quoting AdjustRite (both cited above).
C. Pro tip: This section allows any party to withdraw from discussions, but it doesn't say that "neither party is obligated to negotiate in good faith," because that wouldn't look especially good to future readers — such as jurors ….
8.44.7. Procedure if a party claims that this Clause was orally waived
Any dispute about whether some or all of this Clause was orally waived is to be decided under Delaware law (both substantive and procedural). [BROKEN LINK: loi-del-l-c]
Comment
See 6.1.7.10 for discussion of the choice of Delaware law for specific provisions such as Clause 8.44.
8.44.8. Additional notes (not part of this Clause)
8.44.8.1. What's the point of an LOI; why do parties bother?
Section 8.44: In contract negotiations, parties' don't always do letters of intent ("LOIs"); instead, they simply negotiate and sign the final contract. But LOIs are quite common in merger- and acquisition ("M&A") tranactions; they're also used in some commercial transactions that have a long "runway" before the final agreement will be signed.
One of the most important functions of an LOI is to make it clear that the parties have not reached agreement on all the material terms of the arrangement and that the parties do not yet agree to be bound, except for certain limited and specific topics. Otherwise, a court could find that an LOI was binding after all — with potentially-catastrophic consequences for one party or another. See, e.g., Cathy Hwang, Faux Contracts, 105 Va. L. Rev. 1025, 1053-55 (2019).
Example: In the 1980s, oil giant Texaco was hit with a jury-verdict 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 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 also, 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).
Moreover, when parties enter into a letter of intent ("LOI"), it's generally with one or more of the following in mind:
1. They want the LOI serve as a convenient written discussion outline of a potential business arrangement as they are then currently contemplating it.
2. They want the LOI to set out agreed ground rules for the parties' anticipated discussions about the potential arrangement — including that the parties do not yet agree to be bound.
3. The individuals who are working on the deal who might need to show their bosses that yes, they really are making progress on getting the deal done.
The LOI thus provides some breathing room for all concerned. For additional discussion, see, e.g., Brown & Grinnell (2020) (real-estate LOIs); Jaskolka & Strnad (2020).
By entering into the Contract, each party ("P") is certifying that, so far as P is aware — without necessarily having checked, and with no obligation to do so — P's entry into the Contract will not be a cause of "material problems" (defined below) for any other party to the Contract ("OP"), except to the extent (if any) that P has already disclosed the same in writing to OP.
Comment
This is a fairly-weak certification, of the kind commonly known as a "knowledge rep," i.e., a representation.
8.45.2. Definition: What counts as a "material problem"?
For purposes of this Clause, 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: (i) B's carrying out B's obligations under the Contract, and/or (ii) B's exercise of B's rights under the Contract.
Comment
A. Some strategically-important types of agreement include even-more-detailed representations and warranties of this general kind. See, for example:
Section 3.3(b) of the agreement and plan of merger between Capital One and Discover, from which this Clause 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).
B. Non-trivial risk: This follows Ken Adams's suggestion of saying, "more than a non-trivial risk," discussed at 7.33.4.4 — granted, the use of "significantly interfering" is vague and open to dispute, but that seems like a worthwhile risk in this context.
8.45.3.1. How about some examples of "material" problems?
Students, feel free to just skim this section.
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 14.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.
And a tortious-interference lawsuit can have catastrophic results — for 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. True: In such a situation, Ginger might be able to assert that Fred "fraudulently induced" her into entering into the contract (concerning which, see Clause 8.57, reliance disclaimers). But Ginger surely cares far less about being able to sue Fred than in getting business done — certainly she'd much prefer to know early on about Fred's incapability, so that she could consider finding someone else in place of Fred.
Example: In 2010, a court finding of fraudulent inducement 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 3.15.8.)
"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:
any merger, consolidation, share exchange, or other business combination involving the Seller or the Seller's business or assets;
any disposition of a substantial portion of the Seller's assets, whether by sale, lease, license, pledge, mortgage, exchange, or otherwise; and/or
(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:
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 Contract.
Comment
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.
8.46.2. What Seller activities are prohibited?
This section applies except as stated in section 8.46.4 below.
The Seller must not Shop the Deal before termination (if any) of the Contract.
The Seller must not authorize, nor direct, any Seller Representative, nor any other party, to take any action inconsistent with the Seller's obligations under this Clause.
The Seller must timely direct, in writing, each Involved Seller Representative not to take any action inconsistent with the Seller's obligations under this Clause.
8.46.3. But what if the Seller is approached by others?
The Seller is to promptly advise the Buyer in writing of any inquiries and proposals received concerning possible Competing Transactions.
In doing so, the Seller is to advise the Buyer of relevant details to a commercially-reasonable extent.
Comment
A. 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.
B. Caution: The Seller might not want to be obligated to give the Buyer all the details concerning third-party expressions of interest.
8.46.4. Would the Seller have a "fiduciary out"?
Nothing in the Contract is intended to preclude an organizational Seller from Shopping the Dealif the Seller's board of directors (defined at 8.8), acting on advice of counsel, were to reach one or more of the following conclusions:
that a potential Competing Transaction proposed by a third party — if completed — would be more favorable to holders of the Seller's stock than the Transaction; or
that Shopping the Deal is necessary or advisable for the board of directors to comply with its fiduciary duties under applicable law.
The Seller must advise the Buyer in writing, at least 48 hours beforehand, that the Seller intends to invoke the fiduciary-out exception of this section.
For the avoidance of doubt: The Seller need not disclose, to the Buyer, the detailed content of the advice of the Seller's legal counsel or other advisers concerning the possibility of a fiduciary out.
Comment
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.
8.46.5. Would the fiduciary-out allow termination of the Transaction?
This Clause does not, in itself, provide either party with the right to terminate the Transaction if the Seller were to get a better offer.
Comment
A fiduciary-out clause will typically also allow a Seller not only to shop the deal but to terminate an existing acquisition agreement, e.g., if a better offer comes along. See Richard Presutti, Matthew Gruenberg and Andrew Fadale, Private Equity Buyer/Public Target M&A Deal Study: 2015-17 Review (law.harvard.edu 2018).
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.
The parties' drafter(s) would need to address the termination issue separately in the Contract, because the termination prerequisites might well be subject to serious negotiation.
8.46.6. Would a breakup fee be required?
This Clause does not address whether any party must pay a breakup fee.
Comment
A. 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.)
B. 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.
Noncompetition covenants are seen in employment agreements (sometimes) and in corporate-acquisition agreements (often). This Clause is set up to accommodate noncompetition covenants in both employment agreements and other contracts such as M&A agreements.
Caution:Post-employment noncompetes are essentially prohibited in California (which requires employers to notify employees to that effect) and in several other states, and in the future might be prohibited by FTC regulation. Moreover, in Colorado it might be a criminal offense to try to enforce one.
So this is one of those fast-evolving areas where lawyers should definitely be sure they're up to date on the latest developments, and non-lawyers should definitely seek legal advice.
the geographic area ten feet around the principal place of business of the Company; and
all market segments within that area.
"Company"[b] refers to the clearly-identified individual(s) and/or organization(s) to benefit from the noncompetition obligation stated in the Contract.
Comment
[a] These definitions are those most likely to be negotiated; the gap-filler values above are intentionally ridiculous. See the discussions at 8.47.12 for more details
[b] Subdivision c — caution: Drafters should be sure to identify the specific company or companies that are to be protected by the noncompetition covenant. Example: In a Delaware case, a holding company learned that the hard way: An employee non-competition covenant barred employees from competing with the holding company, but it didn't prohibit them from competing with their actual former employer, which was a subsidiary of the holding company. 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).
8.47.2. Definitions (part 2)
"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.[a]
The "Business Relationship End" will occur at the earliest of the following:
in the case of Employment, on the last day of the Obligated Party's employment in question;
in the case of a Transaction, at the closing of the Transaction; and
in any case, upon the termination or expiration of the Contract (but see also 8.47.10 concerning survival of the noncompetition obligation).
Engaging in a "Competing Business" refers to competing with — and/or preparing to compete with — any Protected Business.
"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 Contract does not, and vice versa.)
"Obligated Party" refers to the party that, as clearly stated in the Contract, is obligated by the noncompetition provision of the Contract.
"Protected Business" refers to any business in which, during the Business Relationship, both of the following were true:
the Company: (A) engaged in the business, and/or (B) demonstrably made active preparations to enter the business; and
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.
"Transaction" refers to a merger, asset sale, or similar transaction, in which (directly or indirectly) the Company and the Obligated Party are both involved.
Comment
[a] 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.
[b] The Business Relationship End is defined to make it relatively easy to determine the end time of the Noncompete Period — because if it's not easy, that might invalidate the noncompete.
Comment
Example: In a 2018 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 beacuse: "… 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).
8.47.3. What activities are restricted?
During the Noncompete Period, the Obligated Party is not to do any of the following things within the Noncompete Territory unless the Contract expressly provides otherwise:
engage or participate, in any manner or in any capacity, in any Competing Business;
invest in, or lend money to, any other individual or organization that proposes or plans to do anything prohibited by the Contract, except as provided at section 8.47.5 below; nor
otherwise knowingly assist any other individual or organization to do anything prohibited by the Contract.
Comment
These restrictions seem to be pretty typical, in your author's experience.
8.47.4. Anything else?
For emphasis: Section 8.47.3 prohibits the specified activities whether the Obligated Party engages or participates in such activities:
directly or indirectly; and
whether for the Obligated Party's own benefit or that of someone else.
8.47.5. Exception for small, passive ownership
For any given organization engaging in any Competing Business, This Clause does not prohibit the Obligated Party from purely-passively owning, directly or findirectly, no more than 5% each of publicly-traded[a] equity securities of the organization.
For this purpose, securities convertible into, or exercisable or exchangable for, such equity securities are counted as part of the total of the equity securities
A hypothetical example: The Obligated Party owns 2% of the publicly-traded common stock of an organization that engages in a Competing Business, as well as warrants convertible into a total 2.9% of the common stock. That adds up to 4.9%, which is under the 5% limit.
Comment
[a] The "publicly-traded" aspect is intended to keep the Obligated Party from being, e.g., a seed investor in a competing business.
8.47.6. Restrictions on changes of control
During the Noncompete Period, the Obligated Party must not allow itself to become controlled (as defined at Clause 7.2) by any individual or organization engaging in any Competing Business.
Comment
Example: In 2021, 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.
8.47.7. Extension of Noncompete Period for violation
This section will apply if the Company successfully seeks to enjoin the Obligated Party's violation of the noncompetition restrictions of the Contract.
In any such case, the Noncompete Period will be extended by a length of time equal to the time:
beginning when the Company caused the action seeking the injunction to be served on the Obligated Party; and
ending when the Obligated Party's counsel reports in writing to the court (or arbitrator, if applicable) that the Obligated Party has fully complied with the injunction.
Comment
A. 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.
b. Some courts, however, seem to be conservative in applying tolling provisions of this kind. Example: In a 2018 decision, a Minnesota 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.
This section will apply if a tribunal of competent jurisdiction determines that one or more of the noncompetition restrictions set forth in the Contract are unreasonably broad or otherwise unenforceable under applicable law.
The parties do not intend for the tribunal's determination to be binding beyond the geographic area in which the tribunal has jurisdiction.
The parties hereby jointly request that the tribunal reform the restriction — 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.
Comment
Concerning "blue-pencil" requests, see generally Clause 8.7.
8.47.9. Obligated Party's opportunity to consult legal counsel
Obligated Party: In agreeing to the noncompetition obligations of the Contract, you acknowledge that you've had the opportunity to consult with legal counsel of the Obligated Party's choice concerning those obligations.
Comment
Concerning the legal effect of acknowledgements, see 7.1.
8.47.10. Survival of noncompetition obligations
The Obligated Party's noncompetition obligations under the Contract will continue in effect until the end of the Noncompete Period, even if the Contract itself, or the Business Relationship, is terminated or expires.
In case of doubt: This section is not intended to expand or limit any other survival provision in the Contract.
Comment
Example: This survival clause seeks to avoid the result in a 2021 Eighth Circuit case, in which 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.
8.47.11. Option: Exception for Fired- or Laid-Off Employees
This Option will apply only if the Obligated Party shows that all of the following are true:
the Obligated Party is an employee of the Company — not an individual contractor; and
the Obligated Party's employment is terminated by the Company.
In any such case, the Obligated Party's noncompetition obligation will end at the same time that his- or her employment by the Company ends.
Comment
This exception is is regarded by some as a sensible one, taking employees' legitimate interests into account.
Note: 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. (On the subject of constructive termination, see generally a lawyer article at Nolo.com.
8.47.12.1. 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.
State laws designed to limit the use of restrictive covenants vary significantly. For example[:]
California; North Dakota; Oklahoma; and Washington, D.C., ban non-compete agreements outright with a few narrow exceptions.
Colorado, Illinois, Maine, Maryland, New Hampshire, Oregon, Rhode Island, Virginia, and Washington prohibit non-compete agreements unless the employee earns above a certain salary threshold.
Other states, like Iowa and Kentucky, limit the use of non-competes for certain professions such as healthcare workers.
And as of July 1, 2023, Minnesota joins the list of states banning post-employment noncompetes outright.
California's per-se prohibition for employment agreements
Famously, a California statute has been interpreted as a per-se rule prohibiting virtually all post-employment noncompetition covenants; business-to-business noncompetes, however, are subject to a rule of reason.
Relatedly: In 2020, a federal appeals court, dealing with a California case, held that a provision in an employment agreement, purporting to require assignment of post-employment inventions, was effectively a noncompetition covenant that was unenforceable under a separate provision of California law.
Moreover, 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.
Post-employment noncompetes in some other states
Caution: The following list is not necessarily complete — drafters of noncompetition covenantes should check the law in the relevant state(s); a list of links to additional reading is provided at the end of this section.
– 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.
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.
– 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.
– 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.
– 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.
Comment
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
For additional information, it'd be highly advisable to do a Google search about specific states of interest.
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 against the named plaintiffs. (The court provisionally declined to impose a nationwide injunction because of unresolved issues about standing.)
Comment
See Ryan LLC v. FTC, No. 3:24-CV-00986, slip op. (N.D. Tex. Jul. 3, 2024) (granting motion for preliminary injunction against FTC's Noncompete Rule).
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 …."
Even in those jurisdictions that allow enforcement of post-employment noncompetes, the noncompetition covenants must be "reasonable" in time.
A general impression about Noncompete Periods is that:
For post-employment noncompetition covenants, one year is likely to be a reasonably-safe bet in many jurisdictions;
For post-acquisition noncompetition covenants, two- to four years seems not-uncommon.
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.
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 a 2022 Second Circuit decision involving the originator of the "Hayley Page" line of bridal apparel.
Comment
See JLM Couture, Inc. v. Gutman, 24 F.4th 785 (2d Cir. 2022) (affirming, in relevant in part, preliminary injunction against social-media "influencer").
In a 2023 decision, Alabama'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.
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.
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)
This Clause concerns parties to the Contract, 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 Contract. Drafting suggestion: In the Contract, explicitly state which party is which.
8.48.2. Definition – Nonsolicitation Period
When agreed to, this Clause will apply during the "Nonsolicitation Period," which: (1) begins on the effective date of the Contract; and (2) ends at 12 midnight at the end of the day on the date "one year" after termination or expiration of the Contract.
8.48.2.1. Comment:
Drafters will very-likely want to custom-tailor the definition of Nonsolicitation Period.
8.48.3. Off-limits employees
During the Nonsolicitation Period, the Obligated Party must not not solicit for employment any employee of the Protected Party who, in any significant way, was involved in the Protected Party's activities under the Contract.
8.48.3.1. Comment:
A. As with noncompetition clauses (see 8.47), the enforceability of nonsolicitation clauses varies considerably by (U.S.) state; drafters should definitely do their homework and/or consult legal counsel.
B. And parties should be very cautious about so-called "no-hire" clauses, which have led to unwanted attention from the U.S. Department of Justice, as discussed at Clause [BROKEN LINK: no-hire].
8.48.4. Exception for ordinary general recruiting
The Obligated Party's nonsolicitation obligation under this Clause does not apply to 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) do not specifically target employees of the Protected Party.
8.48.4.1. Comment:
This exception for non-targeted general recruiting activities is widely used.
8.48.5. Exception for employees fired or laid off
For any employee whose employment is terminated by the Protected Party, the Obligated Party's nonsolicitation obligation under this Clause will end at the end of the day on the date one month after the employee's last day of that employment.
8.48.5.1. Comment:
This exception is less-often seen than that of section 8.48.4, but it often makes business sense.
8.48.6. Survival of this Clause
The Obligated Party's nonsolicitation obligations under the Contract will continue in effect even if the Contract itself, or the parties' business relationship under the Contract, is terminated or expires.
In case of doubt: This section is not intended to expand or limit any other survival provision in the Contract.
8.48.6.1. Comment:
This section is informed by an analogous by the Eighth Circuit in Miller (2021) that a noncompetition provision in an employment agreement did not 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).
8.48.7. Nominal damages only, for breach?
Technical breach of a nonsolicitation provision might result in an award of only nominal damages; this happened in ORP Surgical (2024), where the Tenth Circuit held:
Compensatory damages contemplate the position the nonbreaching party would have been in but for the breach, but here the court determined that the reps would have left even without Stryker’s breach. So the court concluded that compensatory damages were inapt to remedy ORP’s injury.
And even if compensatory damages had been on the table, the court wasn’t convinced by any of ORP’s damages proposals. Finding that ORP failed to carry its burden in proving damages, the court instead awarded nominal damages, which is the prescribed alternate remedy under New Jersey law.
Louisiana: Employee-nonsolicitation clauses are subject to restrictions similar to those of noncompetes.
Example: In 2024, a Louisiana appeals 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, No. 2023 CA 0706 (La. App. Jun. 27, 2024) (affirming partial summary judgment).
Contents:
<>
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 a lawsuit culminating in Syntel Sterling (2023). See Syntel Sterling Best Shores Mauritius Ltd. v. TriZetto Group Inc., 68 F.4th 792 (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.
Employee-nonsolicitation covenants, however, can be problematic and even dangerous if not done very carefully, as discussed below.
Contents:
8.49. Other Necessary Actions
Contents:
Each party is to: (i) sign and deliver any other commercially-reasonable documents, and (ii) take any other commercially-reasonable actions, as may be reasonably requested by the other party, if necessary to further the clear purpose of the Contract.
the parties will escalate, to a neutral advisor (see 6.4), any persistent disagreement about what constitutes reasonable action for purposes of this Agreement.
Comment
A. This Agreement and language like it are sometimes seen in merger- and acquisition agreements, but rarely in everyday commercial agreements.
B. Subdivision a: The use of several instances of "reasonably" is intentional:
Suppose that Party 1 requests that Party 2 take a particular Action A.
In the abstract, Action A might be commercially reasonable — in context, however, Party 1's request might not be reasonable under the circumstances.
C. Subdivision b: Chances are that a disagreement of this nature will never go very far into a dispute-management process.
8.50. Past Dealings Disclaimer
Contents:
The parties do not intend, and neither party is to assert, that the parties' past dealings will have the effect of modifying or supplementing the Contract.
Comment
A. Language like this is sometimes seen in companies' "canned" standard forms, e.g., in customers' purchase-order terms and conditions and sellers' terms of sale.
B. Caution: Agreeing to this Agreement could later put a party at a disadvantage in possibly-unpredictable ways.
8.51. Performance Improvement Plan
Performance-improvement plans are usually seen in employment relationships, but they're not unknown in ongoing business-to-business ("B2B") relationships. This Clause provides parties with 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.
When agreed to, this Clause will apply in any situation in which a party (the "Company") desires to have another party (the "Associate") agree to and comply with a performance-improvement plan (a "Plan") to remedy one or more failures on the part of the Associate to meet clearly-agreed performance requirements.
8.51.2. Notice requirement
To trigger this Clause, the Company must give the Associate notice to that effect in accordance with Clause.
The notice must specify, in reasonable detail (but see subdivision c.2 below), in what respects the Associate has failed to meet previously-agreed performance requirements.
In case of disagreement about the specificity of the notice:
the Company will consult with the Associate to a reasonable extent to try to resolve the disagreement; but
the Company will be the sole judge of whether the Company's notice is sufficiently detailed.
Comment
A. Basic fairness dictates that someone being put "on plan" should be notified of that fact.
B. The Company is given the final say because it'd be undesirable for 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.
8.51.3. Associate's first-draft responsibility
The Associate is to provide the Company with a draft of a Plan.
The Associate will preferably consult with the Company in drafting the Plan, but this is not mandatory.
Whatever else a draft Plan says, it preferably should include provisions for scheduled periodic "check-ins" beween the Associate and the Company.
The Associate is to provide the draft Plan to the Company no later than the end of the day on the date five business days after the effective date of the Company's notice to the Associate under section 8.51.2 above.
The Company will be deemed to have accepted the draft Plan if the Company does not object, in writing and in reasonable detail, on or before ten business days after the effective date of the Associate's notice to the Company that proposes the draft Plan.
Comment
A. Subdivision a puts the burden on the non-performing Associate to prepare the first draft of the Plan — but the consultation preference gives the employer or manufacturer an opportunity to provide input.
B. Subdivision c: See generally 8.12: Catch-Up Calls and its commentary.
C. Subdivision d: The Associate doesn't need to use formal notice (see 6.9: Notices Protocol Clause) to submit the draft Plan.
D. Subdivision e: If the parties don't agree on a Plan, they should consider — but this Clause doesn't require — engaging in a sensible dispute-management process such as 6.4: Escalation to Neutral Advisor Clause.
8.51.4. Termination for failure to comply with Plan
This section will apply if the Associate:
fails to propose a reasonably-acceptable draft Plan as provided above; and/or
fails to meet the agreed Plan's requirements in one or more respects — whether or not the Associate regards the failure as material.
The Associate's failure(s) will be deemed a material breach (see 7.33: Material Breach Definition) of the Contract.
The Associate will not have any cure period for that breach required except at the Company's sole discretion.
Comment
The performance-improvement plan is itself the "cure period," so there's no reason for the employee or channel partner 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.)
8.51.5. Notes: How serious is "being put on plan," really?
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.
– 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).
– Another writer, at FastCompany.com in 2018, was more optimistic, albeit not entirely convincingly: "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).
When agreed to, this Clause sets forth actions to be taken by a party indicated in the Contract (the "Customer") as being a customer of services or technology of another party (the "Provider").
Comment
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.
8.52.1.2. Customer's compliance obligation
The Customer must comply with any data privacy laws that are relevant to the Customer's activities under the Contract.
For this purpose, the term data privacy law includes, without limitation, obtaining any consents that might be needed for the Customer to manage personal data, to the extent that any such consent is required by law.
Comment
See the (relatively-short) discussion of privacy laws at 7.39 and its commentary.
8.52.1.3. Possible registration- and/or fees requirement
When required by law, the Customer is to do related things (at its own expense) such as, for example:
registering as a "data controller" with a local privacy data office; and/or
paying a related fee.
Comment
For a discussion of the effect of an acknowledgement, see 7.1 and its commentary.
8.52.1.4. Consent to certain Provider data activities
The Customer agrees that the Provider may collect, store, and use personal data as stated in the Provider's privacy policy.
8.52.1.5. Responsibility for "external" privacy paperwork
As between the Customer and the Provider, the Customer is responsible for any "external" privacy paperwork associated with the Customer's access to personal data, such as (for example) registration of any data controller(s) (if any) that the Customer engages to handle particular matters.
Each party, referred to as "A," is to take prudent measures, on a continuing basis, to cause A's "workers," defined below, to conduct themselves in a lawful, professional manner in all activities under the Contract.
For this purpose, A's "workers" are the following:
A's employees;
others under A's control at the time in question; and
the employees of A's subcontractors, if any. (This Clause does not address whether the Contract allows, or prohibits, the use of subcontractors.)
Comment
For additional discussion of subcontractors, see [BROKEN LINK: subk-cmt].
8.53.2. Handling of related third-party claims
Each party "A" is to defend and indemnify each other party "B" and its Protected Group against any claim by a third party "C" — even if A has always taken prudent measures under section 8.53.1 — where the claim arises primarily from:
alleged tortious- or unlawful conduct,
by one or more of A's workers,
in activities relating to the Contract.
In case of doubt: In subdivision 1, the term "each other party" B refers to each other party to the Contract.
8.53.3.1. Reading: Introduction: A hypothetical example
Here's a hypothetical example of when the defense- and indemnity obligations of this Clause would come into play:
Let's say that one party, which we'll call "P," enters into a contract with another party, "OP."
Now let's say that one of P's employees engages in unprofessional conduct — for example, harassment — that adversely affects one of OP's employees.
Subsequently, OP's harassed employee sues OP, claiming that P's employee created a hostile work environment — and that OP is liable for that, under some theory such as joint employer, negligent hiring, etc.
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 executive orders and will be revised." [Emphasis added.])
In that situation, this Clause requires P to defend and indemnify OP against the claim by OP's employee.
And the same would be true if OP were being sued by an unrelated third party, and not by one of OP's own employees, for conduct by P. That's a potential concern because the third party's lawyers might be very "creative" about legal theories with which to try to drag OP into litigation in the hope of getting some money to go away (i.e., to settle out).
It's a two-way street, of course: If one of OP's employees were to harass one of P's employees, then OP would be under the same defense- and indemnity obligations to P.
8.53.3.2. Why bother with this Clause?
The express defense reference in this Clause has some business significance: Suppose (for example) that:
P allegedly broke the law as part of the Contract; and
as a result, a third party made a claim — civil, or criminal — against OP.
If P didn't have an express defense obligation, such as that of this Clause, then OP would likely have to "front" its own legal expenses, even though P's noncompliance with the law might constitute a breach of the Contract if the Contract required compliance.
Comment
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).
8.53.3.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 Clause 8.63 (site visits) and Clause 8.17 (computer-system access) when engaged in activities covered by those provisions.
8.53.3.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.
8.53.3.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):
Export controls: this would include, for example, export-control law or other prohibitions on access by certain categories of individuals. Caution: In some cases, allowing non-U.S. nationals to access a computer system (or other information) could violate U.S. export-controls law — and in some circumstances, doing so could lead to criminal fines and/or prison time for the individuals responsible;
federal- and state securities laws (when applicable);
privacy laws — especially concerning health-related and finance-related matters;
false-advertising laws.
8.53.3.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 Clause in the interest of (trying for) brevity.
8.54. Purchase Orders
Many aspects of the process described in this Clause are similar to the way that procurement for the U.S. generally works, as implemented in the Federal Acquisition Regulations. See Legal effect of quotations, 48 C.F.R. § 13.004.
When this Clause is adopted in the Contract, it will apply in any situation in which 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 "Supplier").
Regardless whether the Order itself says so: The terms of this Clause:
are incorporated by reference into the Order, and
take precedence over any inconsistent terms in the Order.
Comment
A. "[O]ne or more items" could be one or more goods (tangible or intangible), services, and/or other items; would also encompass things that might not be considered goods or services, such as, for example, license rights.
B. See also Clause 4.6 (sales quotations) and its commentary.
8.54.2. How may a purchase order be submitted?
The Supplier may decide:[a]
the means by which the Customer is to submit Orders; and
what information must (or should preferably) be submitted with an Order.[b]
Comment
[a] Some supply contracts go into great detail about just how Orders must be submitted and what just information must be included in them. This likely would be overkill for many contracts, because:
The Supplier — especially the Supplier's sales people, who might have personal quotas to meet — will be motivated by competitive pressure to make it easy for the Customer to submit Orders, for example via a hard-copy purchase Order, email, a Web-based portal; etc.; and
Both the Supplier's and the Customer's preferences for ordering processes might well evolve over time, so it seems unwise to carve such details in stone, so to speak, in the Contract itself.
[b] If parties felt the need to put more details into the Contract, they could look to section 2 of a Honeywell terms-of-sale document for sample language (archived at https://perma.cc/5MB9-H6VK).
Comment
From section 2 of a Honeywell terms-of-sale document: "Orders should specify: (1) Purchase Order number; (2) Honeywell‟s part number; (3) requested delivery dates; (4) price; (5) quantity; (6) location to which the Product is to be shipped; and (7) location to which invoices will be sent for payment." • Note how this language uses the term should and not must, so it's actually helpful without being imperious.
8.54.3. Is a purchase order binding on the Supplier?
If not clearly agreed otherwise in writing, this section applies unless the Order is submitted in response to a Supplier sales quotation (see Clause 4.6) that:
states that the sales quotation itself is an offer; or
expressly invites acceptance by the Customer by submission of a purchase order.
The Customer's mere sending of the Order to the Supplier does not itself create a contract that is binding on either party.
Comment
The is because, under this Clause, the Order is merely an offer by the Customer, as opposed to the Customer's acceptance of an offer by the Supplier.
8.54.4. How can a Supplier accept an Order?
The Order may specify that it (the Order) may be accepted only in some particular manner, for example by written notification.
Otherwise, the Supplier may accept the Order in any manner not prohibited by law.
Comment
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 28.5.2.
8.54.5.Must the Supplier accept an Order?
The Supplier may decline to accept any Order unless the parties have clearly agreed otherwise in writing.
Comment
Possible override: In a master purchase agreement, Customer might want to override this section, possibly with language along the following lines: "Supplier must accept any Order that is submitted in accordance with the requirements of the Contract."
8.54.6. What if the Supplier never responds to the Order?
If the Supplier does not respond to the Order:
it does not mean that the Supplier has implicitly accepted the Order; and
the Order will expire, and can no longer be accepted, as stated in UCC § 2-205.
8.54.7. What if the Supplier simply starts performance?
If the Supplier accepts the Order by beginning performance,[a] then the Supplier's acceptance does not bind the Customer unless and until[b] the Supplier advises the Customer in writing[c] that the Customer has begun performance.
The Contract may address how the parties will proceed if the Customer changes its mind about the Order before the Supplier's performance is complete.
Comment
[a] If the Customer sends the Supplier a purchase order for goods or services, and the Supplier 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 Supplier as a "unilateral contract," as discussed at 8.54.11.4.
On the hand, if the Supplier does respond with its own terms, then it'd likely cause a "Battle of the Forms" as discusssed at 10.5.
[b] 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 …." That's why, in fairness, if the Supplier wants its acceptance to be triggered by starting work, paragraph XX requires the Supplier to advise the Customer of the same, otherwise, the acceptance won't be binding on the Customer.
[c] This does not require the Supplier to give the Customer formal notice (see Clause 6.9) that the Supplier has started performance.
8.54.8. Each Order is a separate contract
Each accepted Order is treated as a separate contract that incorporates the Contract by reference — including but not limited to this Clause — whether or not the incorporation is explicit.
Comment
This could be overridden with language such as, "Each accepted Order is to be considered an addition to the Contract and not as a separate contract." This is seen, for example, in the ISDA Master Agreement, where "netting out" of multiple transactions is desired.
Caution: From a supplier's perspective, this override 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 supplier's financial risk.
Comment
Suppose that a customer and a supplier entered into a master purchase agreement that capped the supplier's liability for damages at "the amounts paid or payable under the Contract." 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 supplier wouldn't be wild about that — although the customer certainly wouldn't mind it.
Tangentially: In a 2023 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"; the contract language at issue was the following:
… the Supplier's total liability to the Customer, whether in contract, tort (including negligence), for breach of statutory duty or otherwise, arising out of or in connection with this Agreement (including all Statements of Work) shall be limited to an amount equivalent to 150% of the Charges paid or payable in the preceding twelve months from the date the claim first arose. If the claim arises in the first Contract Year then the amount shall be calculated as 150% of an estimate of the Charges paid and payable for a full twelve months.
8.54.9. Who is financially responsible for Orders from Customer affiliates?
This section will apply:
if the Contract allows one or more affiliates of the Customer to place orders under the Contract;[a] or
if in fact this happens.
If the Customer has not guaranteed payment of its affiliates' Orders (see Option 8.54.10.1 for possible language), then the Customer is not responsible for the obligations of any Customer affiliate arising from the affiliate's Orders (if any) under the Contract.[b]
But: Unless the Customer has guaranteed payment of its affiliates' Orders, the decision[c] whether to accept or reject an Order from a Customer affiliate is within the Supplier's sole discretion — even if the Contract would otherwise obligate the Supplier to accept a similar Order from the Customer itself.
Comment
[a] When a big Customer enters into a "master purchase agreement" with a Suppler, the agreement will often allow "affiliates" of the Customer to place Orders on the same terms and conditions. (The U.S. Government "GSA Schedule" is one example; see 15.5 for a brief discussion.)
[b] This subdivision puts the burden on the Supplier to check the separate creditworthiness of the Customer's affiliates that place Orders under the Contract. (That could be a significant concern, as discussed in more detail at 7.2.6.)
Absent a Customer guaranty — concerning which, see Option 8.54.10.1) — the Supplier might want to defer or decline an Order from a Customer affiliate if the Supplier 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 Supplier from accepting or fulfilling an order from a particular Customer affiliate; see generally 13.11.
^{[c]} This is intentionally not phrased, "The Supplier may reject Customer affiliates' Orders"; the idea is to come across to the reader as slightly softer and less imperious.
8.54.10.1. Option: Customer Guaranty of Affiliate Orders
This Option applies if an affiliate of the Customer submits an Order that is accepted by the Supplier.
The Customer is jointly and severally liable, together with that affiliate, for the affiliate's obligations under that Order.
Clause 2.10 (guaranties) also applies, with the Customer being the Guarantor, the affiliate being the Debtor, and the Supplier being the Creditor.
Subdivision b overrides the gap-filler term in section 8.54.9, so that if a Customer affiliate places an order but doesn't pay, then Supplier can look to Customer for payment. (See 7.2.6 for discussion of how this is a real possibility.)
8.54.10.2. Option: Change Orders by Customer
Subject to the restrictions in this Option, the Customer may unilaterally make changes to an agreed Order for goods or services (including for example, in the latter case, changes to a statement of work for services) in one or more of the following aspects:
specifications (for goods and/or services);
designs and drawings (for items to be specially manufactured);
shipment method (for goods and/or deliverables resulting from services);
packaging method(s);
quantity of goods or other deliverables;
time or place of delivery of goods or other deliverables;
timetable for services to be rendered; and/or
quantity of services; that is, the Customer may require more- or fewer services than stated in the Order.
The Customer is bound by a change to an Order if the individual issuing the change on behalf of the Customer has have at least apparent authority to do so, unless the Contract clearly limits such authority.
If the Customer's change to an Order isn't agreed to in writing by both the Supplier and the Customer, then the change doesn't take effect unless and until both of the following things happen:
the Supplier advises the Customer in writing that the Supplier objects to a Customer change to an Order; and
the Customer receives the Supplier's objection within ten business days after the Supplier receives the Customer's change.
A. 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 supplier if the supplier doesn't object within a certain period.
In that vein, this Clause draws extensively on ideas in section 17 of a (very) customer-biased Honeywell purchase order form, reproduced in the appendix at 8.54.11.5 — 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.)
B. Caution: Suppose that the Customer asks for a costly change but the Provider doesn't follow an agreed procedure to ask for an increase in price: In such a situation, the Supplier 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).
C. Subdivision b: See generally the discussion of apparent authority at 24.3.3. Possible override language for the Contract: "Only an authorized procurement representative of [Customer] may agree to a change order."
D. Subdivision c.2: The Customer must receive the Supplier's objection — that is, the "Mailbox Rule" (discussed at 6.9) doesn't apply here.
8.54.10.3. 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 Contract:
The Customer may submit an order of any size.
or:
The Supplier 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 Supplier 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 Supplier and the Customer might have a bit of a tug-of-war over the Supplier's autonomy in accepting Customer orders:
At one end of the spectrum, the Supplier 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 Supplier 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 Supplier will not decline any order.
or:
The Supplier 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 6.4.)
or:
The Supplier 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 Supplier when due, then the Supplier may decline subsequent proposed orders by the Customer until all such past-due amounts have been paid.
or:
The Supplier is deemed to have accepted an order, and to have waived its right to decline or otherwise reject the order, if the Supplier has not declined the order in writing within [fill in time] after Supplier receives the order.
What about the Supplier's revoking of acceptance? Consider the following:
If the Customer has failed to pay one or more amounts due to the Supplier, then the Supplier may revoke its acceptance of the Customer's orders that the Supplier previously accepted but has not yet filled or completed.
or:
The Supplier may not revoke its acceptance of an order.
or:
The Supplier 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 Supplier has shipped the goods — by sending a written cancellation advice to the Supplier.
and/or:
No Customer cancellation of a Supplier-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 Supplier has shipped the goods — by sending a written cancellation advice to the Supplier.
or:
No Customer cancellation of a Supplier-accepted order for services will be effective.
and/or:
No Customer cancellation of a Supplier-accepted order for goods will be effective.
and/or:
A Supplier-accepted order for goods or other deliverables will not be deemed canceled unless the Supplier 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 Supplier may invoice the Customer for, and the Customer is to pay, a cancellation fee in the amount of [specify the amount].
8.54.11.1. An overview of the purchase-order process
Students, be sure to read this:
When a supplier sells products or services to a large, "enterprise" corporate customer, the sales contract typically comes into being via the following mating dance:
1. If the (prospective) customer and the supplier haven't dealt with each other before, then the customer might send the supplier a request for quotation ("RFQ").
(Or: If the customer just wants more information and perhaps a quotation, the customer might instead send the supplier a request for proposal, known as an "RFP.")
The customer might send the supplier an RFQ out of the blue. But often this happens because a supplier sales representative has "pitched" the supplier'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 supplier by someone working for the customer: "OK, send me a quote."
2. In response, the supplier's sales rep sends the customer a "sales quotation" or "quote" — concerning which, see the sales-quote protocol at Clause 4.6.
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 supplier can "accept" or not. (Purchase orders are the subject of this Clause.)
At this juncture, the supplier 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 supplier'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 supplier's sales rep might ask the supplier'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 supplier accepted by performance. (See 8.54.11.4 for more discussion.)
4.2 Or: The sales rep — before getting the supplier'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 10.5.
[DCT TO DO? CREATE A LADDER DIAGRAM TO ILLUSTRATE THIS PROCESS?]
5. Caution: Sometimes a supplier (or an individual sales rep) might be in danger of missing its sales-target number for a fiscal quarter. In that situation, the supplier might get a cooperative customer to place a so-called "round trip order," where the customer places an order with the supplier but the supplier 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 23.7 for examples.
8.54.11.2. The parties' business processes might impede sales
Customers and suppliers 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 supplier 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.
8.54.11.3. Caution: don't sign a PO or order confirmation … [TO DO]
Companies will want to train their front-line people: A supplier shouldn't sign a customer's purchase order, nor should a customer sign a supplier'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 supplier 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).
8.54.11.4. Caution: 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 supplier 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).
Supplier's electronic acceptance, acknowledgement of this Purchase Order, or commencement of performance constitutes Supplier's acceptance of these terms and conditions.
So: Suppose that Cisco sends a PO to Supplier, and that in response, Supplier simply ships goods to Cisco, without doing anything else — specifically, without sending Supplier's own "paper" that pro forma rejected the Cisco terms. Supplier might well find itself bound by Cisco's terms, which would almost surely be more onerous to Supplier than would Supplier's own terms and conditions.
(If Supplier did send its own rejection, then Supplier and Cisco would likely find themselves in what's known as the Battle of the Forms, discussed at 10.5.)
8.54.11.5. Appendix: Honeywell change-order language
For those interested in really-detailed change-order language, see the "spaghetti clause" language at section 17 of a Honeywell purchase order form, archived at https://perma.cc/84BS-KYXB.
8.55. Recordkeeping
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 Clause 2.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.
When parties agree to this Clause, they are to proceed as stated here when a party clearly identified in the Contract (the "Recordkeeper") is to cause records to be kept to document, for example:
the Recordkeeper's performance under the Contract,
to the extent applicable, the rights of another party (the "Beneficiary") under the Contract.
The records required under subdivision a are referred to here as "Records."
Comment
Drafting suggestion: Fill in specific party names here.
8.55.2. What standards must Records meet?
The Recordkeeper is to cause all Records:
to comply with commercially reasonable standards for the nature of the Records in question; and
to be complete and accurate in all material respects.
Comment
A. Depending on the type of Records, "commercially reasonable standards" might encompass professional- or industry standards.
B. Some drafters require records to be "true and correct," but that seems both redundant and incomplete; see the further discussion of this subject at 25.5.
8.55.3. When must Records be created?
The Recordkeeper is to cause Records to be created at all times during the term of the Contract.
8.55.4. How long must Records be preserved?
The Recordkeeper is to cause all Records to be preserved:
as required by law; and
if longer: until the completion of any timely-commenced audit.
Comment
See the additional discussion at 8.55.6.3. • See also Clause 2.3.
8.55.5. Must the Recordkeeper make any Record-relating reports?
This Clause may address whether the Recordkeeper is required to make reports relating to Records or their contents.
Comment
See generally 8.55.6.4 for possible reporting requirements.
8.55.6.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.
8.55.6.2. What kind of records might have to be kept?
Depending on the circumstances, the Contract could require a party to keep, for example: Sales journals; purchase-order journals; cash-receipts journals; general ledgers; and inventory records.
8.55.6.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 Recordkeeper 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 Contract and/or their relationship are in fact subject to the FARs.
8.55.6.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:
how often a party must make periodic reports;
what sorts of events could trigger a nonperiodic report;
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;
what information must be included in a report;
whether any particular method is to be used to generate the reports, e.g., using specific auditing software to collect and summarize electronic data;
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
what if any supporting documentation must be provided with reports.
periodic status conferences and check-in calls as in 8.12.
8.56. Referrals
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. 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
A party indicated in the Contract (the "Supplier") pays commissions to another party (the "Associate"):
on sales by the Supplier to one or more customers (each, a "Prospect"),
in a stated Territory (defined below),
where the Prospect is referred to the Supplier by the Associate.
This relationship between the Supplier and the Associate is a "Channel Partnership" as referred to at 4.5, which includes certain additional definitions and is incorporated by reference into this Clause.
Comment
Special case: In the U.S., legal-ethics rules impose strict limits on lawyers ability to pay or receive commissions for client referrals.
of "Eligible Sales," defined at section 8.56.3 below,
that the Supplier makes during the "Partnership Term" (see 4.5.1.2),
but before the relevant "cliff deadline" (see section 8.56.5),
and subject to termination as to any particular referral (see section 8.56.6),
to any Prospect whose principal place of business has a mailing address on the same city block as the mailing address of the Associate's principal place of business (the "Territory").
Comment
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.
8.56.3. Definition: Eligible Sales
Commissions will accrue only on the Supplier's sales of Supplier Offerings, to Prospects that the Associate refers to Supplier, where each of the requirements in the following paragraphs is satisfied, in addition to other requirements specified in the Contract ("Eligible Sales"):
The Prospect has substantial operations in the Territory — the Supplier's determination on that point is final and binding.
The Associate referred the Prospect to the Supplier during the Partnership Term (not before, not after).
It isn't against the law for the Prospect to acquire the relevant Supplier Offering(s) in the Territory.
The Prospect isn't a competitor of the Supplier unless the Supplier gives its prior written consent.
The Prospect didn't have had a previous connection or relationship with the Supplier at the time of the Associate's initial referral; the Supplier's determination on that point is final and binding.
Comment
A. This section assumes that the Supplier will want to pay commissions only for referrals that are genuinely useful for building out the Supplier's customer base.
B. Subdivision a: The "substantial operations" criterion is one of those that likely can be safely left up to the Supplier to determine — because if the Supplier is too stingy in that regard, then it risks finding itself getting fewer and fewer referrals from that Associate.
C. Subdivision b: Time-based "fences" around eligible sales can be extremely useful for certainty, which business people often value highly.
D. Subdivision c: Legal restrictions on a Prospect's acquiring the Supplier's offerings could include, for example, one or more of the things listed at 8.56.13.1.
E. Subdivision d: The Supplier might rightly be concerned about unwittingly providing competitors with access to (for example) trade-secret computer software.
F. Subdivision e: Purely-commercial incentives should keep the Supplier from being too aggressive in determining that it had a prior relationship with a Prospect, lest the Associate simply stop referring prospects at all.
8.56.4. Definition: When a sale is considered "made"
For commission-eligibility purposes, any given Supplier sale to a Prospect is considered "made" on the date that the Supplier and the Prospect enter into a binding contract for that sale.
Comment
A. The "made" date for a given sale might or might not be the (putative) effective date of the relevant binding agreement between the Supplier and the Prospect.
B. Caution: Be careful about using terminology such as "when a sale is consummated," which could lead to costly litigation over the meaning o that term. Example:Fed Cetera (3d Cir. 2019): 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.
8.56.5. "Cliff deadline" for first commissionable sale
A sale to a Prospect isn't eligible for a commission if the first Eligible Sale to that Prospect is "made" more than one year after the Associate's initial referral of the Prospect to the Supplier.
Comment
A. As used here, "cliff deadline" is a shorthand expression meaning that a given referral will "fall off a cliff" after the specified date. (Another metaphor would be "Cinderella deadline," with a referral turning into a pumpkin after that date.)
B. The underlying idea here is that not all referrals are "good" referrals, from the Supplier's perspective — if the Supplier is unable to make an initial sale to a prospect on or before the cliff deadline, then the Supplier shouldn't have pay commissions for any sales to that prospect.
C. Negotiation tip: In the edge case, as a cliff date approached on a particular referral, the Supplier might feel it would do better financially by delaying its first sale until after the cliff date had passed. If that's a significant concern, the parties could negotiate a "phase-out" deadline, with progressively-lower commission rates as time went on, instead of an all-or-nothing cliff deadline.
8.56.6. End date for commissions from any one referral
A sale to a Prospect isn't eligible for a commission if the Supplier enters into a binding contract for that sale more than one year following the first Eligible Sale to that Prospect.
Comment
A. This section recognizes that as time goes on, and the Supplier (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 Supplier's own success in dealing with the Prospect.
B. This section also gives the Associate an incentive to keep drumming up more new business for the Supplier, instead of "farming" commissions on old referrals.
C. Negotiation tip: To smooth out the Associate's commission revenue (instead of having it fall off a cliff after the end date), the parties could negotiate a phase-out of commissions over a longer period of time — perhaps with the commission rate being reduced by some amount each quarter or each month.
8.56.7. Exclusions: Taxes, shipping, & insurance
Separately-itemized charges for taxes, shipping, and insurance aren't eligible for commissions.
Comment
A. This exclusion is pretty customary — but it should not be interpreted as excluding additional fees and other charges imposed and kept by Supplier. (Two familiar examples: Checked-bags fees imposed by airlines, and "resort fees" charged by hotels).
B. Concerning taxes, see Clause 2.16 (tax responsibilities).
8.56.8. Commission payment due date
The Supplier pays the Associate any commission(s) earned by the Associate, in full, no later than 30 days after the end of the Supplier's fiscal quarter in which the Supplier collects the associated invoiced sale price(s).
In case of doubt, the Associate need not submit an invoice for commission payments to the Supplier.
Comment
A. 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 section 8.56.6.
B. Parties should be clear about when referral commissions are to be paid, because this might have to be litigated. Example:MAK Tech. Holdings (N.Y. 2024).
This section will apply if the parties clearly agree in writing that the Supplier will pay commissions before collection of the sale price.
When computing commissions due on sales, the Supplier may deduct from sales a reasonable allowance for returns, as long as those deductions conform to the Supplier's then-generally-effective return policy.
The Supplier may determine its return policy in its sole discretion (defined at Clause 7.23) from time to time, but the Supplier is to apply the return policy consistently for purposes of this Clause.
Comment
Keep in mind that under this Clause, the Supplier doesn't have to pay commissions until after the relevant sales proceeds have been collected, which means that this section ordinarily shouldn't even come into play.
8.56.10. Commission clawback for certain unpaid invoices
This section applies if all of the following are true:
The Supplier pays a commission before the Supplier collects payment for the relevant transaction;
The Supplier 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
The Supplier did not take a deduction for a return allowance as provided in section 8.56.9.
In that case, the Associate promptly refunds the commission (without interest) upon the Supplier's written request.
In case of doubt, the Contract 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 Clause:
the Associate;
the Associate's affiliates (if any); and
the personnel of each of them.
Comment
This is a roadblock provision — but it's possible that the parties might have other payment arrangements that are documented by separate contracts.
8.56.12. Supplier record- and reporting requirements
The Supplier keeps records to support commission amounts due under the Contract in accordance with Clause 8.55.
With each commission payment, the Supplier provides the Associate with a complete and accurate written statement of the amount(s) due, with reasonable supporting detail.
The Associate may have the Supplier's commission statements audited in accordance with the audit protocol at Clause 2.3.
Comment
A. Paragraph XX: The term "complete and accurate" is far better than "true and correct," as discussed at 25.5.
B. A recordkeeping requirement and an audit requirement will often go "hand in hand," for reasons discussed in the commentary of Clause 2.3 (audit protocol).
8.56.13. Checklist: Some other issues to consider
8.56.13.1. Legal restrictions on referred sales?
Legal restrictions on a Prospect's acquiring the Supplier's offerings could include, for example, one or more of the things:
A Prospect might be on the Consolidated Screening List of parties to whom certain exports, etc., are restricted by the U.S. Government.
In a given territory, the Supplier'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. (Nowadays, 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.)
8.57. Reliance Waiver Clause
In jurisdictions such as Texas, an entire-agreement clause in a contract (see Clause 6.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).
This Clause will apply only if agreed to in the Contract.
Comment
8.57.2. Each party is covered by this Clause.
Each party is a "Waiving Party" for purposes of this Clause unless otherwise specified.
Comment
Some drafters might want to make this a one-way waiver, in which only one party is waiving reliance.
8.57.3. Definition: "Outside Statement"
For purposes of this Clause, an "Outside Statement" is any statement of fact or opinion — including but not limited to a representation — where the representation:
is made by (or attributable to) a party to the Contract other than the Waiving Party; but
is not set forth in the Contract itself (including but not limited to its attachments, exhibits, schedules, etc., if any).
8.57.4. The Waiving Party will not rely on any Outside Statement.
By signing the Contract, the Waiving Party certifies:
that the Waiving Party is not relying on any alleged Outside Statement — and hereby WAIVES any such reliance — in deciding to enter into the Contract;
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 Contract and the transaction(s) contemplated by the Contract; and
that the Waiving Party understands and accepts those terms, conditions, and risks.
Comment
A. Example: The Eighth Circuit had zero sympathy for a group of grocery store owner-operators who signed up as licensees of a discount grocery chain — the owner-operators had not only done due-diligence homework, with the aid of attorneys and other advisors, but had also signed extensive anti-reliance disclaimers. See SBFO Operator No. 3, LLC v. Onex Corp., 101 F.4th 551, 556 & n.3 (8th Cir. 2024) (affirming summary judgment in favor of defendant Onex).
B. This Clause 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.
8.57.5. This waiver has limits.
For emphasis:
This Clause does not waive any party's reliance on any representation, warranty, or other statement in the Contract itself; this includes (but isn't limited to) any that are set forth in attachments, exhibits, materials incorporated by reference, etc.
But: Subdivision a does not affect any express waiver of reliance on a particular representation, etc., that is stated in the Contract.
8.57.6. The Waiving Party agrees to a few other things here.
By signing the Contract, the Waiving Party agrees:
that it will not rely on any alleged Outside Statement in deciding to enter into the Contract;
that it will not make any claims inconsistent with this Clause; and
that it intends for the other party or parties to the Contract — when they enter into the Contract — to rely on the Waiving Party's waiver, certifications, and agreements in this Clause.
Comment
A. Inconsistent claims: See the discussion in the commentary at 3.1.9.
B. See generally the overview of reps and warranties at 3.17 — especially the requirement that a claim of misrepresentation must be supported with proof of reasonable reliance on the allegedly-false or -misleading representation (at 3.15.3).
8.57.7. Special provision under California law
Each 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."
Comment
This section is included out of an abundance of caution, in case the reliance waiver of this Clause is considered an "advance release" under California law; see generally the discussion at 3.14.2.
8.57.8. Additional notes (not part of this Clause)
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 3.17.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;
neither of those remedies would normally be available in a breach-of-warranty action.
Example: An appeals court affirmed a $23 million jury verdict for breach of contract and fraud, noting: "Punitive damages may be awarded for fraud even though the fraud incidentally involves breach of contract." Huy Fong Foods, Inc. v. Underwood Ranches, LP, 66 Cal. App. 5th 1112, 1126, 281 Cal. Rptr. 3d 757 (2021).
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.
Students: You can just skim the remaining summaries below of case law.
Example:IBM v. Lufkin Industries: The Texas supreme court held that:
Under Texas law, a party may be liable in tort for fraudulently inducing another party to enter into a contract. But the party may avoid liability if the other party contractually disclaimed any reliance on the first party's fraudulent representations.
Whether a party is liable in any particular case depends on the contract's language and the totality of the surrounding circumstances.
Specifically, courts must consider such factors as whether
(1) the terms of the contract were negotiated, rather than boilerplate, and during negotiations the parties specifically discussed the issue which has become the topic of the subsequent dispute;
(2) the complaining party was represented by counsel;
(3) the parties dealt with each other at arm's length;
(4) the parties were knowledgeable in business matters; and
(5) the release language was clear.
Id. at 229
Example: A Houston appeals court affirmed summary judgment dismissing a fraud claim where the contract in question included this language:
This Agreement contains the entire agreement between the parties with respect to this subject matter and is not subject to any prior or contemporaneous oral or written agreements. The undersigned parties affirm that they have not relied on any representations not expressed in this Agreement in deciding to enter into this Agreement. The undersigned parties further affirm that they are relying solely on their own judgment (and the advice of their own counsel) in deciding to enter into this Agreement.
Example: In this Fifth Circuit case, the contract between an alarm-system company and its jewelry-store customer contained the following reliance disclaimer: "In executing the Agreement, Customer is not relying on any advice or advertisement of ADT." The court held that this language "was sufficiently clear as to disclaim any reliance by plaintiffs on any alleged misrepresentation ADT made prior to Plaintiffs entering into the contract. Accordingly, Plaintiffs' fraudulent inducement claim is barred under Texas law." Shakeri v. ADT Security Services, Inc., 816 F.3d 283, 288, 296 (5th Cir. 2016) (per curiam).
Example: New York's highest court ruled that a fraud complaint should have been summarily dismissed, because "plaintiffs in the plainest language announced and stipulated that they were not relying on any representations as to the very matter as to which they now claim they were defrauded." Pappas v. Tzolis, 20 N.Y.3d 228, 233-34 (2012).
Example: The Mayo Foundation had granted a license to a startup company under a patent application that Mayo had filed for certain nano technology. In the license agreement, the startup company "warranted that it had 'independently evaluated the Patent Rights, Know-How, and Confidential Information … [and] is entering into this Agreement on the basis of its own evaluation and not in reliance o[n] any representation by Mayo ….'" (Emphasis added.) The license agreement also disclaimed any implied warranties by Mayo about the patentability of the technology, among other things; the agreement stated that the licensed subject matter was being provided “as is,” “with all faults,” and “with all defects.”
Things apparently didn’t go well for the startup company: The patent application died when (i) the patent examiner issued a non-final rejection of the pending claims in the patent application, citing prior art, and (ii) the startup company (which was to take over prosecution of the patent application) failed to respond to the rejection within the six-month period prescribed by the patent statute.
The startup company then sued Mayo, alleging among other things that Mayo had engaged in fraud and misrepresentation. (The startup company had raised $500,000 in funding from investors; conceivably the lawsuit might have represented an attempt by the startup company to divert investor anger away from the company's management and toward Mayo.)
The district court held — and the Eighth Circuit affirmed — that the startup company’s fraud- and negligent-misrepresentation claims against Mayo were barred by the reliance disclaimer in the license agreement. This was because, under Minnesota law,
actual and reasonable reliance on the alleged misrepresentations was a required element of both claims, but
reasonable reliance was conclusively negated by the reliance disclaimer quoted above. OmegaGenesis Corp. v. Mayo Fdn. for Med. Educ. & Research, 851 F.3d 800 (8th Cir. 2017) (affirming dismissal for failure to state a claim upon which relief can be granted).
Of course, 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.
And a no-reliance clause in a contract might not enough to convince a court to toss out a fraudulent-inducement or negligent-misrepresentation claim, for example 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.
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.
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%.
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).
"Service of process" is something that happens in litigation; common examples are (i) a summons and complaint to kick off a lawsuit, and (ii) a subpoen aordering an individual or company to produce documents and/or to testify at a deposition or at trial. It's 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).
8.59.1. How may legal process be served?
To the extent not prohibited by law: In any dispute arising out of or relating to the Contract, any party to the Contract may cause legal process to be served upon another party to the Contract:
by notice by certified mail or established independent courier with written confirmation of delivery by the delivery service; and/or
In itself, this Clause neither authorizes nor prohibits service of process by email — whether that would be permissible is to be determined by applicable law.
Comment
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.
Comment
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).
8.60. Settlement Discussion Admissibility
If this Clause is agreed to, when would it apply? the parties engage in discussions to settle an actual controversy between them.
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.
In case of doubt, this Clause covers, without limitation:
This Clause will survive any termination or expiration of the Contract.
Comment
A. 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 Clause 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.
B. Subdivision 1: For discussion of the "actual controversy" requirement, see the commentary to Clause 6.4.22.5 (escalation to neutral).
C. Subdivision 2: Rule 408 seems to be widely accepted as a sensible approach.
D. Subdivision 4: See also Clause 5.1 concerning survival generally.
8.61. Settlement Offer Rejection
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 Clause is intended to create incentives for a party to think long and hard before rejecting a settlement offer that invokes this Clause.
In the interest of getting disputes settled more quickly and at lower cost: When this Clause is part of the Contract, it will apply in any "Dispute," namely any litigation or arbitration arising out of or relating to:
the Contract, and/or
any transaction or relationship resulting from the Contract.
Comment
A. This section is intended to make it clear that this Clause is to be applied broadly.
B. 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), citingBlinco v. Green Tree Servicing LLC, 400 F.3d 1308, 1310 (11th Cir. 2005).
8.61.2. Applicability of this Clause
This Clause will apply whenever:
a party (the "offering party") makes an offer (the "Settlement Offer"), to another party, to settle a dispute relating to the Contract; and
the offer clearly states, in effect, that it (the offer) is subject to this Clause.
the other party (the "rejecting party") does not timely accept the Settlement Offer; and
the final outcome in the dispute is not at least10% more favorable to the rejecting party than the Settlement Offer.
Comment
A. 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 Clause.
A. 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.)
8.61.3. What would the consequences be?
The rejecting party must pay or reimburse the offering party for all attorney fees (see 3.1 that the offering party incurred in the dispute after making the Settlement Offer.
Moreover: 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.
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.
Comment
Subdivision b: The "tribunal" would be the court in a lawsuit, or (if applicable) the arbitrator(s) in an arbitration proceeding.
8.61.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.
Comment
A. 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.
B. 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).
8.61.5. Survival of this Clause
The parties' agreement to this Clause will survive any termination or expiration of the Contract, regardless whether the Contract contains other survival provisions.
8.61.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.
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 Clause 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).
8.61.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).
8.62. Shotgun Buy-Sell [to come]
8.63. Site Visits Protocol Clause
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 Clause lays out a basic framework for such events.
Caution: This Clause isn't intended as a "code of conduct"; were it otherwise, and if Clause 8.14 were also agreed to, then the remedies for breach of this Clause would be limited — and that's not the intent here.
When this Clause is agreed to, it will apply 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.
For emphasis: This Clause does not itself authorize anyone to access a Host Site: it only states ground rules for any case in which such access occurs.
Comment
Subdivision a: For readability, Visitors are sometimes referred to here as the Visiting Party's Visitors.
8.63.2. Definitions
For purposes of this Clause:
The term "Host Site" refers to:
any physical premises of another party (the "Host"); and/or
any computer system, network, or other system of the Host — concerning which, see also Clause 8.17 (computer-system access).
The terms "people" and "personnel" of a party refers to the following:
for an individual party: the party him- or herself;
for an organizational party (a corporation, LLC, etc.): the party's officers, directors, employees, members, managers, and other individuals in similar positions; and
others acting under the party's direction in furtherance of the party's activities relating to the Contract.
Comment
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 30.10.3.)
8.63.3. Who is responsible for Visitors' actions?
The Visiting Party is to see to it that its Visitors comply with this Clause — this includes, for example, appropriately instructing them in their obligations under this Clause.
8.63.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.
Comment
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.)
8.63.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:
this Clause;
such other reasonable Host-Site rules and policies as the Host timely communicates to the Visiting Party and/or to the Visitor;
prudent safety practices;
Clause 8.17, which deals with computer-system access, whenever a Visitor has access to a Host system;
reasonable standards of professional conduct; and
applicable law — including but not limited to export-control law — and other prohibitions on access by certain categories of individuals.
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.
8.63.7. Indemnity obligation for unlawful conduct
Each party "Alpha" is to defend and indemnify each other party and its Protected Group "Bravo" from "unlawful conduct," defined below, on the part of Alpha and/or any of Alpha's people, at any time during a Site Visit by a Visiting Party (whether that be Alpha or Bravo).
For this purpose, "unlawful conduct" is intended to be interpreted broadly, encompassing, without limitation, any and all of the following types of conduct:
(if Alpha 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.;
other unlawful discrimination;
unlawful retaliation; and
other tortious conduct by Alpha's people.
Comment
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.
8.63.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 Contract or its people — unless clearly agreed otherwise in writing.
Comment
Concerning "As between the parties," see the discussion at 9.6.
8.63.9. Indemnity obligation against third-party claims
Each party "Alpha" is to defend and indemnify each other party and its Protected Group "Bravo" against any claim • by any third party (including but not limited to the other party's own people) • arising from misconduct by any of Alpha's people • in connection with a site visit by Alpha's people to a Bravo site or vice versa.
8.64. Support Levels Definition
Contents:
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:
Comment
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.
Level 1: Routine basic support for a product or service; it entails providing customers, where applicable, with:
compatibility information,
installation assistance,
general usage support,
assistance with routine maintenance; and/or
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.
8.65. Testing [TODO]
Before:
Following Installation, Pruitt may test the Cloud Services to determine whether they perform in material conformance with the Documentation…. With regard to Customer Use Cases, Pruitt will notify Caradigm when testing has been satisfactorily completed and Pruitt is ready for Caradigm to move the Customer Use Case to the production environment.
A federal appeals court held that this language did not mean that the Cloud Services must perform to Pruitt's satisfaction:
The testing clause's language, however, convinces us that it is not a satisfaction clause, as Pruitt contends. It doesn't read like a promise on Caradigm's part to "perform services 'to the satisfaction of' or 'satisfactory to'" Pruitt, and it looks nothing like the satisfaction clauses that Georgia courts have enforced.
The testing clause, for instance, doesn't set up an "if… then" proposition—say, that "if testing is not satisfactory to Pruitt, then Pruitt shall have the right to cancel."
Nor does it state that the project would reach First Productive Use "if testing proved satisfactory" or "if Caradigm performed to Pruitt's satisfaction."
To the contrary, the testing clause states that Pruitt "will notify Caradigm when testing has been satisfactorily completed" and Pruitt "is ready" for next steps.
If anything, the clause reads like a promise on Pruitt's part—i.e., an expression of an intention that some future performance will be rendered.
Even if the testing clause's language was ambiguous, reading the clause in the larger context of the contract confirms that it didn't give Pruitt a right to demand subjective satisfaction.
Id. at 1259 (cleaned up formatting modified).
8.66. Third-Party Beneficiaries
Introduction: 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. For that reason, it's useful to be clear about the parties intent. See generally Third-Party Beneficiary (Wikipedia.org).
Unless the Contract expressly says so, the parties do not intend for any other individual or organization to benefit except incidentally — and thus without enforceable rights — under the Contract.
8.66.2. 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: The Seventh Circuit affirmed a summary judgment in favor of an additive supplier that was sued by a distributor's end-customer; the court noted that the end-customer was not an intended third-party beneficiary of the contract between the supplier and the distributor:
Although as the ultimate consumer ACL could expect to benefit from Lubrizol’s sale of the additive to its distributor, that expectation did not make ACL a third-party beneficiary of the contract between VCS and Lubrizol. More was required.
Otherwise 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).
8.66.3. 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.)
8.66.4. Some other points to consider
• A contract might provide that third-party benefits are not assignable (8.5.8).
• Third-party beneficiaries might have to arbitrate contract-related disputes if the contract contains an arbitration provision (8.2.5).
• 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 (8.3.3).
• 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 (4.5.2.11).
8.67. Trademark License
This Clause draws on ideas found in a trademark license agreement form of The University of Texas at Austin (your author's alma mater), which for many years has been one of the most successful collegiate brand merchandisers.
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. Author's 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 did pretty much all of UT's trademark work as far as I know.
Contents:
8.67.1. Clause text
8.67.1.1. Applicability; parties
When this Clause is agreed to, it presupposes that a party clearly specified in the Contract (the "Mark Owner") is agreeing in the Contract 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".
8.67.1.2. Placeholder business terms
As a drafting checklist, the following "placeholder terms" apply except to the extent that the Contract specifies otherwise:
What "Licensed Marks" are licensed? None.
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.
How long will the Trademark License last ("Trademark License Term")? The term of the Contract.
What specific User goods and/or services are licensed ("Licensed Items")? None.
Must the User conform to any detailed specifications for Licensed Items? None specified.
Must the User conform to any detailed usage requirements for Licensed Marks? None specified.
Is the Trademark License exclusive, in the Territory or any part of it (e.g., a geographic- or market segment)? No.
May the User grant sublicenses for the Licensed Marks? No.
8.67.1.3. Grant of Trademark License
The Mark Owner grants the User the Trademark License.
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 Contract expressly says so.
8.67.1.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 Contract, 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:
the Mark Owner's then-current use of the Licensed Mark(s), and
generally-accepted good commercial practice.
8.67.1.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:
the "®" (r-in-a-circle) symbol for registered marks; or
the "™" or "SM" symbol for unregistered trademarks and service marks, respectively.
Comment
R-in-a-circle: Concerning the "®" (r-in-a-circle) symbol, see generally 15 U.S.C. § 1111.
8.67.1.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.
Comment
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.
8.67.1.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.
8.67.1.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 Clause; in addition, Clause 8.37 (inspections) will apply to any such inspections on the User's premises:
the User's use and/or display of the Licensed Marks; and/or
only if specifically stated in the Contract or otherwise agreed: The User's facilities for making products that will bear Licensed Marks, for quality-control purposes.
8.67.1.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.
Comment
Benefit of trademark use: This section derives from some technical aspects of trademark law that are beyond the scope of this discussion.
8.67.1.10. What if a third party challenges a Licensed Mark?
Clause 8.41 will govern any situation in which a third party:
might be infringing a Licensed Mark; and/or
challenges the validity or enforceability of the Mark Owner's rights in any Licensed Mark.
8.67.1.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:
register any Licensed Mark in the Territory (at the Mark Owner's expense);
maintain or renew any registration of a Licensed Mark in the Territory (at the Mark Owner's expense); and/or
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).
8.67.1.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.
By the act of entering into the Contract, the User is also — effective at that time — assigning, that is, permanently transferring, all such rights to the Mark Owner, 8.39.9 without the need for any further action in that regard by either the User or the Mark Owner.
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).
In case additional "paperwork" is needed in that regard: The User is to comply with the ownership-transfer and -confirmation provisions of Clause 8.39.
8.67.1.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:
challenge the Mark Owner's rights in any Licensed Mark;
challenge the legal protectability of any Licensed Mark;
challenge the validity of any registration or application for registration, owned or approved by the Mark Owner, for any Licensed Mark;
use any Licensed Mark, or any confusingly similar variation, in the User's corporate name or trade name;
apply for registration or recordation of (i) any Licensed Mark, or (ii) the Trademark License;
apply for registration of any Mark confusingly similar to any Licensed Mark;
attempt to register any Web address (URL) that contains any Licensed Mark or any distinguishing feature of a Licensed Mark;
attempt to register any Web address (URL) that is confusingly similar to any Licensed Mark;
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;
take any action that could invalidate or jeopardize any registration or application for registration of any Licensed Mark; and/or
purport to assign the Trademark License — any such purported assignment will be void.
8.67.1.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 [BROKEN LINK: tm-prohib], then The Mark Owner may — in its sole discretion — terminate the Trademark License; the termination will be effective immediately upon notice in accordance with Clause 6.9.
8.67.1.15. Does the Mark Owner make any warranties about a Licensed Mark?
Unless the Contract unambiguously says otherwise: The Mark Owner DISCLAIMS any representation, warranty, condition, or term of quality, to the effect —
that any Licensed Mark is legally protectable against use by others; or
that the User's use of the Licensed Mark(s) under the Contract will not infringe the rights of one or more third parties.
8.67.1.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:
in any manner that is misleading or otherwise deceptive;
in any manner that would, in the Mark Owner's sole judgment, be offensive to a relevant segment of the population;
in any manner could otherwise diminish the reputation of the Mark Owner, its Marks, or its goods and/or services;
on, or in promoting, Licensed Items that do not meet standards stated or referred to in the Contract;
to mark and promote any goods or services other than Licensed Items;
in advertising or promotion outside the Territory.
8.67.1.17. What else may the User not do concerning Licensed Marks?
The User must not:
use any Licensed Mark in any manner except as authorized by the Contract;
modify any Licensed Mark; nor
include any Licensed Mark, nor any distinguishing feature of a Licensed Mark, as a feature or design element of any other Mark;
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;
permit, encourage, or knowingly help, any other individual or organization to take any of the actions prohibited by this Clause;
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.
8.67.1.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:
deliver to the Mark Owner all tangible Licensed Items bearing any Licensed Mark;
permanently remove all Licensed Mark(s) from such Licensed Items; and/or
destroy all Licensed Items bearing any Licensed Mark.
8.67.1.19. The User is responsible for its own business liabilities
The User must defend and indemnify the Mark Owner and its Protected Group against any third-party claim arising out of or relating to:
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
any breach of the Contract by the User.
8.67.1.20. No use of any Licensed Mark in the User's Web addresses\, etc.
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.
If the User does so at any time, then the User must immediately transfer the same to the Mark Owner.
As hypothetical examples: 30.10.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.
8.67.1.21. Required: Immediate cessation of objected-to uses
If, at any time — by notice to the User in accordance with Clause 6.9 — 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 Clause, then the User must, at its own expense:
stop that use of the Licensed Mark;
work with the Mark Owner to determine a suitable course of remediation;
if reasonably determined by the Mark Owner: take one or more of the actions described at section [BROKEN LINK: tm-wrap].
8.67.1.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 Clause. 8.29
8.67.1.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.
Comment
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).
8.67.1.24. Option: Specific Mark Owner Approval Required
If the Contract 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.
Comment
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.
If the Contract 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.
8.68. Waivers
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 6.1.7.2 for an explanation of the difference between a waiver and an amendment.
Each party ("P") is to follow this Clause if P asserts that another party ("OP") supposedly waived a right or obligation relating to the Contract — whether the right or obligation arises from the Contract itself or otherwise, e.g., by law.
8.68.1.2. A written waiver is normally required:
Except as provided in section 3 below, the other party OP is not considered to have waived the right or obligation in question unless the waiver is clearly stated in a writing signed by OP.
8.68.1.3. Alternatively, an oral waiver may be confirmed in writing by the other party:
An oral waiver by OP would be effective if
the waiver was prominently documented, in a written confirmation (e.g., by email) that P sent to OP;
P shows that OP actually received the confirmation; and
OP does not object in writing within a reasonable time.
Comment
Written confirmation of oral waiver: This accommodates modern business practice. Pro tip: It'd be a very good idea for P to send OP a quick email prominently saying, in effect, Hey, OP, thanks for agreeing, in our phone call today, to waive [whatever] — if I misunderstood you, please let me know immediately. If OP doesn't object, in writing, within a reasonable time, it could help convince a court that OP really did waive whatever it was.
Pro tip: In the example email just above, P doesn't ask OP to "agree" that she waived something. That's because if OP never responded to P's email, then it'd be harder for P to prove OP's oral waiver. But: A more-neighborly practice would be for OP to "sign" the waiver, e.g., by responding to P's email, e.g., with: That's right, you don't need to do [whatever]. (P would want to keep OP's confirming email on file, of course.)
Comment
8.68.1.4. Would a waiver have broad- or continuing effect?
Any waiver under the Contract is to be given effect: (i) only narrowly, and (ii) on a one-time basis only, unless by its terms the waiver clearly states otherwise.
Comment
When a waiver is drafted too broadly — unintentionally, or otherwise — it can do serious damage to a party's position. Example: A physician served as an advisor to a bio-pharma company. Over time, he received three successive option grants (as is typical in such advisory arrangements). But after the physician left that role, the company refused to honor his first two option grants because the third grant agreement stated that the physician waived his right to any prior grants. The Delaware chancery court ruled in favor of the bio-pharma company, but the state's supreme court reversed and remanded on grounds that certain language in the waiver was susceptible to multiple reasonable interpretations, and therefore a trial was necessary. See Terrell v. Kiromic Biopharma, Inc., No. 131, 2024 (Del. Jan. 21, 2025).
8.68.1.5. Can a waiver be revoked?
Any waiver under the Contract is irrevocable unless the waiver itself clearly says otherwise.
8.68.1.6. Can this Clause itself be orally waived?
If P asserts that this Clause itself was waived in some other manner, that assertion will fail unless P proves — by clear and convincing evidence, with reasonable corroboration of statements by interested witnesses — that OP knowingly and intentionally waived this Clause itself. 6.1.7.8
8.68.1.7. Are any specific no-waiver situations contemplated?
The Contract may optionally list specific situations that would not constitute a waiver or estoppel — if so, then no party will assert otherwise in any forum.
Hypothetical example: A lease could expressly state that the landlord's acceptance of late rent would not waive the landlord's rights nor estop the landlord from enforcing any provision of the lease.
Comment
In a Texas case, the state supreme court addressed a situation like that of the hypothetical example above. Reversing a court of appeals, the supreme court declined to say that nonwaiver provisions 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
8.68.2. Pro tip: Be conspicuous about the word WAIVE, etc.
When you're drafting a contract or other document, and it states that the other party (or even your own client) "waives" something, it's a good idea to use bold-faced, all-capital letters for the word "WAIVES" (or waived, or waive, or waiver). Doing so is "cheap insurance" in case the applicable law requires waivers to be "conspicuous."
9.1. Agreements to agree: They're unenforceable … (notes)
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 a contract, an "agreement to agree" is not enforceable — but this is 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.
The following is reproduced largely verbatim (but with minor, purely-stylistic edits) from the Ninth Circuit's 2021 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). Omitted are the court's extensive citations; internal quotation marks; and (most) alteration marks. No copyright is claimed in the text of the published opinion.
9.3.1.1. 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."
9.3.1.2. But doesn't every contract "restrain" trade?
The Supreme Court has interpreted Section 1 to outlaw only unreasonable restraints.
9.3.1.3. 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.
9.3.1.4. 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., No. 2:23-cv-01391, slip op. (W.D. Wash. Dec. 4, 2024) (order denying defendants' joint motion to dismiss).
9.3.1.5. 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.
9.3.2. 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: In 2005, 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: December 2010 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.
9.3.3.Vertical- and hybrid price-fixing might be OK …
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.
9.3.4. … 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.
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).
9.4.2. A contract can rule out "apparent" authority
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.
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.
Language of this kind is often seen, e.g., in car dealers' sales contracts: Such a contract might say that only a manager- or vice-president is allowed to modify the terms of the contract. (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 as extra warranty coverage, better floor mats, etc.)
9.5. Arising out of or relating to (notes)
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.
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 boundary by indicating some direct relationship; otherwise the term would stretch to the horizon and have no limiting purpose ….
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."
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'").
9.6. 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 Contract says.
Example: As discussed at 10.2.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.
9.7. A.T.A.R.I. Rule (cross-reference)
Here, "A.T.A.R.I." stands for Avoid The Argument: Rewrite It!; see 30.9.7 for more details.
9.8.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 ….
9.8.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.
9.8.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).
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 Contract 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 10.1.2.
10.1.2. Caution: Deceptive backdating has led to long prison sentences
Never backdate a contract for deceptive purposes, e.g., to be able to report a sale in an already expired financial period — that practice has sent more than one corporate executive to prison for securities fraud, including at least one general counsel.
Example: 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).
Example: 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.
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).
10.2.1. Style tip: Don't do "Witnesseth" and "Whereas"
Note: 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 32. And if your supervising partner has a preference, then do it that way, see 33.9.1.
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 is pretty hard to read, no?
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 can be argued that the parties did not agree to the Whereas clauses.
10.2.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 10.2.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;
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 30.3.
10.2.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).
10.2.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).
10.2.5. Leave rights & obligations out of 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 29.15.
[ ] 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.
10.2.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," 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 but she really wasn't.
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.)
10.3.1. The automatic stay against termination (etc.)
Consider the situation where a party "A" wants to terminate its contract with a counterparty "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 section 5.7.1.1.
10.3.2. Ipso-facto terminations are likewise unenforceable
Likewise unenforceable in bankrupcy are so-called ipso-facto clauses, where the debtor's entering into bankruptcy proceedings would automatically terminate the contract. For an example and extensive citations, see a paper (undated) at the Web site of the Bryan Cave law firm.
10.3.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.
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.
10.4. Baskets for losses (notes)
Contents:
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.
To illustrate, let's use a hypothetical example with made-up numbers for a so-called "deductible basket":
AGGREGATE LOSSES
RESPONSIBLE PARTY
Less than $100
Buyer
$100 and up
Seller
Here's a variation on the deductible basket:
LOSSES
RESPONSIBLE PARTY
Less than $100
Buyer
$100 to $10,000
Seller
More than $10,000
Buyer
Another variation is the so-called "tipping basket" (sometimes called the "first-dollar basket"):
10.5.1. Buyers use purchase orders to try to impose terms & conditions
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. Useful reading: See generally the discussion of the "Battle of the Forms" by Brian Rogers at https://tinyurl.com/BattleFormsBrianRogers, along with his useful diagram at https://tinyurl.com/BattleFormsDiagram.
For example: When a corporate buyer makes a significant purchase, it's extremely common (and essentially a universal practice) for the buyer's procurement people to send the seller a purchase order. Typically, the seller's invoice will include the purchase-order number — if it doesn't, then the buyer's accounts-payable department generally just won't pay the invoice.
These are routine internal-controls measures; they're almost-uniformly implemented by buyers to help prevent fraud.
But some buyers put a great deal of "legal fine print" in their purchase-order forms as well. Such fine-print terms often include:
detailed — and often onerous — terms and conditions for the purchase. This could include expansive warranties, remedies, and indemnity requirements; and
rejection of the supplier's terms, to the effect of, only our terms and conditions will apply — your terms won't count, no matter what happens.
For example, a Honeywell purchase-order form states in part — in the very first section — as follows:
Honeywell rejects any additional or inconsistent terms and conditions offered by Supplier at any time.
Any reference to Supplier’s quotation, bid, or proposal does not imply acceptance of any term, condition, or instruction contained in that document.
The same section, incidentally, includes this … remarkable assertion:
A purchase order is deemed accepted upon a) the date the Supplier returns the acknowledgment copy of a purchase order to Honeywell or b) five calendar days from date Honeywell issues the purchase order to Supplier regardless of mechanism used to convey requirements, whichever is earlier.
(Emphasis added.) In other words: According to this language, if Honeywell sends you a purchase order out of the blue, then (saieth Honeywell) you're deemed to have accepted the purchase order in five business days. Um … good luck getting a court to go along with that assertion; as South Carolina's supreme court noted (in rejecting a claim that silence was consent):
Silence and inaction can constitute acceptance of an offer, but only in certain circumstances. These circumstances are limited to those from which it may be inferred that the offeree's silence and inaction meets the "manifestation of assent" test …. The Restatement sets forth examples of when this may occur ….
See Lampo v. Amedisys Holding, LLC, Op. No. 28265, slip op. (S.C. Mar. 5, 2025) (reversing and remanding court of appeals decision; cleaned up).
10.5.2. Sellers often do likewise with order confirmations
Sellers aren't always innocent parties in this little dance, either.
It's not uncommon for a seller's initial sales quotation (inviting a purchase order) to state that all customer orders are subject to acceptance in writing by the seller.
Then, when the buyer does send a purchase order, the seller 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 buyer's purchase order.
Once again, Honeywell provides an example, this time when it is the supplier and not the customer: The first section of a Honeywell terms of sale document states in part as follows:
Unless and to the extent that a separate contract executed between the procuring party (“Buyer”) and Honeywell International Inc. (“Honeywell”) applies, any purchase order covering the sale of any product (“Product”) contained in this Catalog (“Order”) will be governed solely by these Conditions of Sale, whether or not this Catalog or these Conditions of Sale are referenced in the Order.
Except as provided in the “Buyer's Orders” section below, all provisions on Buyer's Order and all other documents submitted by Buyer are expressly rejected.
Honeywell will not be deemed to have waived these Conditions of Sale if it fails to object to provisions submitted by Buyer.
Buyer's silence or acceptance or use of Products is acceptance of these Conditions of Sale.
10.5.3. Each party's paper rejects the other's terms & conditions
You might have noticed how, in the examples above, the buyer's purchase order and the seller's order confirmation each say, in effect, "only my terms and conditions will apply; yours are rejected."
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 ….
In each of the Honeywell forms quoted above, the quoted language seems to state pretty clearly that acceptance is limited to the terms stated in the form.
Important: Drafters asked to prepare standard forms of this kind should strongly consider whether to include "We reject your terms!" language along these lines.
10.5.4. The Drop-Out Rule: The UCC's solution
But in real-world dealings, what practical impact will parties' we reject your terms! statements have? This is important because the parties' people might pay no attention to these dueling forms.
Instead, what could easily happen is something like the following:
The seller's sales people receive the purchase order and send it to the order-fullfilment department.
The seller's order-fulfillment department ships the ordered goods — along with a confirmation of sale document and an invoice.
The buyer's receiving department takes delivery of the ordered goods and puts them into inventor, distributes them to end users, or whatever.
The buyer's receiving department forwards the seller's invoice to the buyer's accounts-payable department, which in due course pays the invoice.
The seller doesn't sign the buyer's purchase order; neither does the buyer sign the seller's order confirmation or invoice.
Clearly, the parties have conducted themselves as though they had a contract. But neither has agreed to the other's terms and conditions?
So whose terms and conditions will govern — those of the buyer, or those of the seller?
This sort of situation is known as the "Battle of the Forms." It's exprssly contemplated by UCC § 2-207. (It's sometimes experienced in common-law situations as well.)
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.
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.)
So suppose that:
Buyer sends Seller a purchase order for goods; the P.O. includes terms and conditions that reject the Seller's terms;
Seller sends Buyer an order confirmation containing its own terms and conditions, which reject the Buyer's terms;
Seller ships the goods ordered and sends an invoice; and
Buyer's payables department pays the invoice.
In that situation, the parties have engaged in conduct that recognizes the existence of a contract. The terms of that contract are whatever "matching" terms exist in the parties' respective forms, plus the UCC's default provisions.
Example: In 2023, the Fifth Circuit affirmed denial of a Louisiana equipment manufacturer's motion to compel arbitration of a breach of contract lawsuit that had been brought by a Canadian customer; the court summarized the relevant salvos of paper between the parties:
In sum, below were the relevant events common to these transactions:
1. [Manufacturer] MECS sent [customer] Axiall a proposal incorporating an arbitration clause and containing express limitations on acceptance;
2. Axiall sent MECS a Purchase Order incorporating the forum selection clause and containing express limitations on acceptance;
3. MECS sent Axiall an Order Acknowledgment incorporating an arbitration clause and containing express limitations on acceptance (like MECS's proposal);
4. MECS shipped Axiall the demisters; and
5. Axiall accepted the demisters from MECS.
Citing Louisiana's counterpart to UCC § 2-207, the court described the case as "a classic 'battle of the forms'" and held that the parties had not agreed to arbitration. Axiall Canada, Inc. v. MECS, Inc., No. 21-30105, slip op. part III (5th Cir. Jun. 14, 2023) (unpublished).
10.5.5. Caution: The UN CISG has a "last shot" rule instead
The Convention departs dramatically from the UCC by using the common-law "mirror image" rule (sometimes called the "last shot" rule) to resolve "battles of the forms." With respect to the battle of the forms, the determinative factor under the Convention is when the contract was formed.
The terms of the contract are those embodied in the last offer (or counteroffer) made prior to a contract being formed.
Under the mirror-image rule, as expressed in Article 19(1) of the Convention, "[a] reply to an offer which purports to be an acceptance but contains additions, limitations or other modifications is a rejection of the offer and constitutes a counter-offer."
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."
10.5.6. Selected bibliography
(Students: This additional reading is optional.)
See generally:
– Battle of the Forms – UCC and common-law variations
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 seller's warranty provision was of unlimited duration, but the seller's acknowledgement form stated that the seller'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) (Posner, J.).
10.7.1. Do you need a business-associate agreement?
Not every recipient of personal 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: 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.
10.7.2.Aggregated information is subject to different rules
Under HHS regulations, a business associate may use aggregated protected health information 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.
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).
10.7.3. Some "covered entity" rules have to be "flowed down"
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 14.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:
any demand by a governmental entity for disclosure of PHI.
(See also section 8.18.28 in Clause 8.18, which addresses how subpoenas, etc., for confidential information are to be handled.)
10.7.4. 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.
10.7.5. Certain obligations continue after termination
When you're a business associate, termination or expiration of your business-associate agreement won't end your 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.
10.7.7. 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.
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 Clause 8.37, inspections, and Clause 2.3, audits.)
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 6.4.
Optional further reading:
Both buy-sell agreements and last-offer arbitration ("baseball arbitration"; see Clause 6.4) 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.
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?]
"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 ([BROKEN LINK: sig-block-follows]). Sure, maybe you can later prove the forgery, but why not roadblock the attempt?
• 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 (8.68.2).
• Consider whether to include "for the avoidance of doubt" clauses to roadblock later attempts at "creative" contract interpretations, e.g., concerning assignment consent at discretion (Option 8.5.3). 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 30.12).
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).
11.5. Click-wrap and browse-wrap agreements (notes)
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."
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 section 6.3.6 of Clause 6.3, the "are rejected" language is intended to preclude Wrap Terms from becoming part of the Contract when they address matters that are covered (explicitly or implicitly) in the Contract.
11.6. 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."
11.7. Commissions (on sales) (rough notes)
As explained by the Texas supreme court in 2022, 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 5.3 (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)
Drafting tip: When putting together a written commission plan, consider using one or more roadblock clauses to make it abundantly clear when commissions are not owed.
Counterexample: A 2024 Fifth Circuit case involved an engagement letter between an equipment-rental company, which wanted to sell itself, and 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, and 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).
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).
11.9. Confirmations – get directly from third parties?
Getting confirmation from an independent source relates to the principle that you get what you INspect, not what you EXpect, as discussed at 8.37.
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 3.10) 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 Common Draft provisions such as the following (possibly among others):
Section 2.3.21 of Clause 2.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 8.6.6 of Clause 8.6 (background checks), contact information for personal references is to be obtained independently.
Section [BROKEN LINK: notice-3r] of Clause 6.9 (notices) requires independent confirmation of receipt of notice in most cases.
In section 2.4.4 of Clause 2.4 (backup payment sources), confirmation of a backup-payment arrangement must come from the bank or other financial institution.
11.10. Consideration (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 does not preclude enforcement of the parties' written option agreement) (extensively reviewing case law).
Example:: In a 2024 decision, the Fifth Circuit, reversing a summary judgment, held that an email exchange between Wells Fargo and Occidental Petroleum was not a contract (although another agreement between them, was):
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.
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 3.9.1.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).
11.11.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).
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:
Be judicious about what you put in all-caps.
Don't use too-small a font for language that you want to be conspicuous.
11.11.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.
11.11.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.
Courts often adopt the UCC standard for conspicuousness, as explained in the next section.
11.11.5. In judging conspicuousness, courts tend to focus on "fair notice" — which will often depend on the circumstances
In a non-UCC context, the Supreme Court of Texas held that (apart from a possibly-significant exception) 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; the court explained:
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.
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.
11.11.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).
11.12. Consultation in lieu of consent?
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 heartburn 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.
11.13. Consumer contracts (notes)
This is where I'm "saving string" for possible future use.
11.14. Consummated - not a great word (commentary)
Caution: Be careful about using terms such as "consummated" sales — that led to what must have been a costly lawsuit over a finder's fee for helping land a federal contract: The court ruled that the finder's-fee agreement did not require the resulting 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).
11.15. Contractions (notes)
Author's note: The clauses in this book are written in what I hope is pretty-accessible language. Here and there, I've used contractions, such as "don't" instead of "do not."
Contractions and other accessible language are catching on in legal-related writing. From 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.
In a 2017 post, 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 some justices use contractions in their opinions.
Example: From opinions by Justice Kagan (all emphasis added):
"So a defendant would get safety-valve relief only if he doesn't have any of the three listed criminal-history features. … * * * But second, suppose the same chef typically places a food order if the restaurant 'does not have meat, produce, or bread.' That most likely means he'll place an order when the restaurant runs out of one of those foodstuffs, not wait until it is lacking all three."
"The clear-error standard is a recognition of comparative competence. And it is a forced dose of humility—a virtue which sometimes doesn't come naturally to appellate courts. * * * Now I'll admit: I'm not a statistician. I can see what the majority is saying, but my inclination would be to seek out other opinions …. The problem is I can't do that here. … Sure, it's fun to play armchair statistician. But it's irresponsible to reverse a trial court's decision — on clear-error review — based on such hypothesizing."32
"Congress knows what it doesn't and can't know when it drafts a statute; and Congress therefore gives an expert agency the power to address issues—even significant ones—as and when they arise. * * * Until the agency action at issue, tobacco products hadn't been spoken of in the same breath as pharmaceuticals (FDA's paradigmatic regulated product)."
Example: From opinions by Justice Gorsuch (all emphasis added):
"Statutes aren't games or puzzles but instruments of a practical nature, founded on the common business of human life, and fitted for common understandings."33
"Maybe so, Justice SOTOMAYOR replies, but what if other States pass legislation similar to S. B. 8? Doesn't that possibility justify throwing aside our traditional rules?"
"In light of Pereira, the government now concedes the first document isn't enough to trigger the stop-time rule."34
"By contrast, the dissent doesn't try to defend Louisiana's law on Sixth or Fourteenth Amendment grounds …."
Example: And, from the Supreme Court of Texas: "Words aren’t ambiguous merely because they can be read differently in the abstract."35
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 11.16.2
– 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).
11.16.2. 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).
11.16.3. 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:
1. 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:
2. 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 11.16.6.)
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.
11.16.4. 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 11.16.6).
– 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 8.39.9 (present assignment of future rights) can serve as a backstop provision.
11.16.5.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).
11.16.6. 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).
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. [TO DO: Right of First Refusal, First Negotiation] See 17 U.S.C. § 203(b)(4).
11.16.7. 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 11.16.6.
Reminder: Merely saying that something will be a work made for hire isn't enough to make it so, as discussed above.
11.17. 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 2023 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, 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).
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.
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).
Most contracts never lead to serious disputes; for those that do, the parties can save a lot of time and money by agreeing to some simple ground rules to increase the likelihood of an amicable resolution.
12.2.1. What kinds of "tricks" can be used to promote settlement?
[TO DO: Fill in list]
12.2.2. 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.
I ran into a related issue a couple of years ago with a client, "Client," that:[A] was being acquired by a giant company, "Buyer"; and[B] had a significant, ongoing "Contract" with another giant company, "Customer." The Contract — which I hadn't been involved in negotiating — was on an over-aggressive Customer standard form; it said that Client could not even reveal to others the existence of the Contract, let alone its terms.
The Contract was "material" for Client but likely would not been material for either Customer or Buyer. Client told Buyer in vague terms that there was a contract that Buyer would be entitled to review under the terms of the acquisition agreement. But Buyer didn't want to reveal to anyone that Buyer was looking to acquire Client, so Client wasn't going to get Customer's permission to disclose the Contract.
So the question was: Can Client reveal the Contract to Buyer, during Buyer's due diligence, without Customer's consent, notwithstanding the prohibition in the Contract?
Client decided to take an "efficient breach" position: Client revealed a redacted version of the Contract to Buyer, on the theory that if Customer took the position that this was a breach of the Contract by Client, then Customer's damages would be nominal at best.
Things worked out fine: Client was acquired by Buyer; Client eventually told Customer about the disclosure of the redacted Contract, and Customer didn't have a problem with it.
Electronic signatures are increasingly popular; in recent years the present author has seen fewer and fewer contracts drafted for wet-ink signatures.
13.3.1. Legal basis for electronic signatures
U.S. law explicitly law supports the use of electronic signatures, and American courts now routinely honor electronic "signatures" (which are now common in England and Wales as well). 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 Commission, Electronic Execution of Documents (2019), at https://perma.cc/UCQ7-U94M.
13.3.2. Caution: Parties must agree to electronic signatures
This [Act] applies only to transactions between parties each of which has agreed to conduct transactions by electronic means. Whether the parties agree to conduct a transaction by electronic means is determined from the context and surrounding circumstances, including the parties’ conduct.
(Square brackets in original, emphasis added.) This section is intended to "check the box" that the parties have indeed agreed to conduct transactions electronically.
13.3.3. Caution: State law might limit electronic signatures
The following language is part of the California version but not of the UETA:
(b) … Except for a separate and optional agreement the primary purpose of which is to authorize a transaction to be conducted by electronic means, an agreement to conduct a transaction by electronic means may not be contained in a standard form contract that is not an electronic record.
An agreement in such a standard form contract may not be conditioned upon an agreement to conduct transactions by electronic means.
An agreement to conduct a transaction by electronic means may not be inferred solely from the fact that a party has used electronic means to pay an account or register a purchase or warranty.
And: Under California law, a car dealer apparently must still obtain a manual contract signature from a car buyer.
13.3.4. Pro tip: Be able to prove up electronic signatures
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 California court seems to have offered a road map for contract professionals about what would suffice to prove up an electronic signature in litigation:
[The employer's business manager] Main never explained how Ruiz's printed electronic signature, or the date and time printed next to the signature, came to be placed on the 2011 agreement.
More specifically, Main did not explain how she ascertained that the electronic signature on the 2011 agreement was "the act of" Ruiz. This left a critical gap in the evidence supporting the petition.
Indeed, Main did not explain[:]
• that an electronic signature in the name of "Ernesto Zamora Ruiz" could only have been placed on the 2011 agreement (i.e., on the Employee Acknowledgement form) by a person using Ruiz's "unique login ID and password";
• that the date and time printed next to the electronic signature indicated the date and time the electronic signature was made;
• that all Moss Bros. employees were required to use their unique login ID and password when they logged into the HR system and signed electronic forms and agreements;
• and the electronic signature on the 2011 agreement was, therefore, apparently made by Ruiz on September 21, 2011, at 11:47 a.m.
Rather than offer this or any other explanation of how she inferred the electronic signature on the 2011 agreement was the act of Ruiz, Main only offered her unsupported assertion that Ruiz was the person who electronically signed the 2011 agreement.
Id., 232 Cal. App.4th at 844 (extra paragraphing and bullets added, citation omitted).
13.3.5. Additional resources
See also: • 24.4 for suggestions on how to draft signature blocks, with examples, as well as • 24.3.3 for cautions about whether an individual signer has authority to sign for a party that is a corporation or other organization, and • 13.3.1 concerning electronic signatures.
See generally: • the definitions of signed and writing in UCC §1-201(37) and 1-201(43); the definition of signature in the Texas Business Organizations Code § 1.002(87); "… 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 …." Id.§ 1.007; and • the Model Business Corporation Act § 1.40 (rev. 2016).
13.4. Emphasis on words can change sentence meaning
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.
13.5.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).
13.5.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).
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.
13.6.1. Introduction: The role of exhibits, etc., in contracts
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 8.34).
The contract should made it clear that the parties intend for such ancillary documents to be deemed part of the — otherwise, the parties might have to litigate the question of just what is and isn't part of the contract.
13.6.2.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.
13.6.3. 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 the present author 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.
13.6.4. 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.
13.7. Expert determinations (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 Sapp (2023), 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.
13.8. Expert Determinations [reserved]
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”).
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
Avoid litigation: State explicitly that if the two appraisers don't agree, and 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, No. 22-1554 (4th Cir. Dec. 8, 2023) (affirming judgment confirming panel determination, of amount of rent to be paid, as binding arbitration award), citingHobson v. McArthur, 41 U.S. (16 Pet.) 182, 192-93 (1842).
13.9. Expert determinations [very-rough notes]
In a 2019 decision, a Delaware vice chancellor explained that an agreement : "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) (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), citingHobson v. McArthur, 41 U.S. (16 Pet.) 182, 192-93 (1842).
13.10. Explicitness requirements (rough notes)
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 (8.57) under Texas law, and the express negligence rule (3.9.5).
13.11. 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: In 2024, 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: In 2023, 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.
Example: In 2012, 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.:
a "red flags" list published by the Bureau of Industry and Security ("BIS") in the U.S. Department of Commerce (bis.doc.gov 2019)
13.12.Expressio unius est exclusio alterius
In 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. A 2018 Second Circuit decision provides 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; for example, in another 2018 decision the Second Circuit 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 .
Likewise, the D.C. Circuit 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, emphasis in original), vacated and remanded, 603 U.S. 593, 144 S. Ct. 2312 (2024).
Famously, of course, 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 it. See 144 S. Ct. at 2357, part III.A (Sotomayor, J., dissenting).
13.13. Extraordinary circumstances (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 3.5)?
Are the circumstances shown by clear and convincing evidence (see 7.13)?
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?
"A factoring agreement allows a business to convert receivables [that is, a right to be paid, e.g., by a customer] into cash by selling them at a discount to a factoring company, providing the business with immediate liquidity." Coosemans Specialties, Inc. v. Gargiulo, 485 F.3d 701, 704 n.1 (2d Cir. 2007) (cleaned up); see also Factor (Investopedia.com).
The term flowdown can be relevant when a contract is between a customer and a so-called "prime" contractor that is expected to use [BROKEN LINK: subk-cmt]. The prime contract might require the prime contractor:
to comply with various requirements concerning confidentiality, safety, and the like; and
to include some or all of those requirements in subcontracts — these are referred as "flowdown" clauses.
For government contracts, 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;
failure to keep required records.
14.4. 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.
Example: In a prior life, your author was vice president and (solo) general counsel of a newly-public software company — as outside counsel, I'd helped the founders to start the company a few years before.
• 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 signature — which means that if the contract were ever litigated (which never once happened), the footnotes would be available to be read by opposing counsel; the judge's law clerk; the judge him- or herself; and one or more of the jurors — and that would be no bad thing, yes?
To be sure: Someday in litigation 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 the client will likely get more overall business benefit from including footnotes if doing so will help get the client's contracts to signature sooner.
14.5. For the avoidance of doubt: A useful roadblock
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 roadblock (see 30.8) 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: Clause 7.7 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).
14.6. 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: In 2021, 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: Also in 2021, 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: In 2020, 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: In 2012, 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).
14.7. Forfeiture (notes)
"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).
"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.
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 a 2024 Second Circuit case, various solar-energy installations, operated by generator companies, were "plugged in" to an electrical grid. The grid operators' contract with the generator companies required the generator companies to pay the grid operators the costs of connecting the solar installations to the grid. A dispute arose when the grid operators also charged the generator companies a "tax gross-up adder" to offset the federal income -tax liability resulting from the generator companies' interconnection payments, leading the generator companies to sue for a declaratory judgment. (The appeals court affirmed dismissal of the generator companies' lawsuit for lack of subject-matter jurisdiction.) See Sunvestment Energy Gp. NY64 LLC v. Nat'l Grid USA Servs. Co., 116 F.4th 106 (2d Cir. 2024) (affirming dismissal for lack of subject-matter jurisdiction).
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.
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).
15.4. GSA contracts ("GSA schedules") (notes)
The following 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.
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.
15.5. GSA schedules (notes)
Here's a federal-court summary of how GSA contracts work — in pretty much the same manner as a master purchasing agreement (see 19.1):
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.
Timothy Schaun Lau, "The effect of typewriting vs. handwriting lecture notes on learning: a systematic
review and meta-analysis." (2022).
16.3. 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 a Second Circuit case, 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.
Suppose that Party A and Party B agree that A will share in the profits from B's business — after Party 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, Party B has an incentive to take as many deductions from gross revenue as it can, to try to reduce its payout to Party A. 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).
An online commenter once opined that in Hollywood, net points "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." Gabriel Snyder, How Movie Stars Get Paid (Gawker.com 2009).
(The commenter's piece provides a readable overview of how movie deals supposedly work for actors.)
17.1. Implied covenant of good faith and fair dealing
Delaware: The implied covenant of good faith and fair dealing doesn't protect an earn-out recipient 2.8 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 6.3.7.2.
17.2.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).
17.2.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 responsibility of the customer;
DDP (Delivered Duty Paid) is the other extreme: The supplier is to 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.
17.2.3. Risk of loss shifting can be quickly specified
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.
As called for by the contract, the ducks are all packed in a standard 40-foot shipping container.
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 17.2, plus 4.2.1.2 of 4.2: Deliveries) 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 3.10) 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 1992, in basically this way, thousands of plastic yellow "rubber ducks," red beavers, blue turtles, and green frogs were lost at sea during a Pacific Ocean storm.
Comment
See Friendly Floatees (Wikipedia.org). 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.
17.2.4. 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 a 2024 Fifth Circuit case, a Houston wholesaler sought — unsuccessfully — to get a refund of some $1.9 million in excise tax on truck tires that it had bought from Chinese manufacturers.
Comment
The wholesaler had paid the tax under protest, claiming that under U.S. tax law, the Chinese manufacturers were the "importers" of the tires and therefore were responsible for paying the excise tax. It didn't work: The appeals court held that on the facts, the wholesaler was the beneficial owner — and thus the "importer" — of the tires, and so the wholesaler owed the excise tax. See Texas Truck Parts & Tire, Inc. v. United States, 118 F.4th 687 (5th Cir. 2024) (reversing summary judgment).
17.4.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 6.1.7.11, 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.)
17.4.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 30.15): 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.
Example: The lack of a separate signature for an arbitration requirement proved fatal to an arbitration requirement in a California appellate court's unpublished 2018 decision:
A company's employees had each signed applications for employment; the company's standard application form included an arbitration requirement.
Notably, the arbitration requirement in the employment-application form was set off by double lines and had its own, separate signature line — which the employees did not sign.
When the employees sued the company, the trial court denied the company's motion to compel arbitration, on grounds that the employees had not signed the arbitration agreement; the trial court's decision was affirmed by the court of appeals. See Recinos v. SBM Site Services, LLC, No. A151253, slip op. (Cal. App. Aug. 10, 2018) (unpublished) (citing cases).
Counterexample: In a 2005 decision, the Northern District of California granted a company's motion to compel arbitration of an employee's claim against Pitney Bowes:
The employee had not initialed in the space provided by a statement that the employee acknowledged that he was voluntarily giving up the right to a jury trial.
But: The employment application form also called for an arbitrator to decide any disputes about arbitrability (see the discussion of such "delegation" clauses at 8.1.4 and in the commentary to the "non-delegation" option at 8.1.5.
The court held that it was up to the arbitrator, not the court, to determine whether the arbitration requirement was valid. See Anderson v. Pitney Bowes, Inc., No. C-04-4808, slip op. at 5-6 & n.7 (N.D. Cal. May 4, 2005).
(It was certainly possible that an arbitrator could decide that the arbitration requirement was invalid — which seems circular, no? — and thus that the dispute would return to court after all.)
17.4.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]
17.4.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 6.11.6.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 Clause 6.10 — in which case Alice can produce her photocopy of the pages she initialed, without the surreptitious change.
17.4.5. 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."
17.4.6. Signatures: Pro tips for drafters (and reviewers)
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:
[ x ] All parties are signing the same, final version of the document (6.11.6.1)
[ x ] Each signature block correctly states 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" (24.4.3 through 24.4.6)
[ x ] For each organization that is a party to the contract, 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.
[ x ] In addition, the contract itself doesn't 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 (9.4.2).
[ x ] Each signature block includes a blank line labeled "Date signed," not just "Date" (24.4.2).
[ x ] The law, and/or a party's publicly-filed organizational documents, don't restrict who has authority to sign on behalf of a particular type of organizational party (trust, LLC, etc.) ([BROKEN LINK: sigs-auth] and [BROKEN LINK: sigs-auth-legal]).
17.5. Intellectual property: See "IP"
17.6. Interpretation ("construction") of contract terms
Here's a quick recap of some basic principles of "construing," that is, interpreting, contract terms:
• The judge normally makes the first pass at determining the meaning of a disputed provision, using the usual rules of contract interpretation (17.6.2); if those rules produce a definite meaning for the provision, then the judge will declare that meaning, and there won't be the need for a trial to establish the meaning.
(Conceivably, the appellate court might have a different view: It might conclude that the provision is indeed ambiguous, in which case the matter might well be remanded for a trial to determine the provision's meaning.)
• If all else fails — if the usual contract-interpretation principles don't produce a definitive answer for what a contract provision means — then the judge will rule that provision is ambiguous.
• When the trial court rules that a provision is ambiguous, then the case must (usually) be tried, and the trier of fact (usually, the jury) gets to decide what the parties are deemed to have intended. The trier of fact will often do this by looking to extrinsic evidence under the parol evidence rule, such as witness testimony by the people who negotiated the contract term(s) in question (if they're available).
• If a trier of fact makes a determination what the parties are deemed to have intended in drafting the ambiguous provision, then an appellate court isn't likely to overrule that determination (at least in the United States). 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.
The Texas supreme court recapped the general ground rules for interpreting contract language, which your author has recast below into short, single-subject paragraphs to Serve The Reader:
Absent ambiguity, contracts are construed as a matter of law. [That is, the trial judge, not the jury, construes the contract, and 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.
17.6.2. Courts sometimes apply specific rules of interpretation
Courts often look to specific rules of interpretation such as the following:
– Context matters; as the Texas supreme court noted:
[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. …
On the other side of the coin, even if context does not narrow meaning, 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.
– 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 its 2016 Lockhart decision, 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 the Lockhart case just cited, 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).
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).
17.7. Interpretation of contract terms (cross-reference)
See 30.9 for a discussion of how courts approach ambiguous terms in contracts — that is, terms that could plausibly be intepreted in more than one way — to determine what the parties will be considered to have agreed to.
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.[a] 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.
Comment
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).
"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) (cleaned up, citations omitted).
Master agreements typically don't themselves obligate either party, but instead serve as a reference document containing terms and conditions for purchase orders or work orders. Example: As the Supreme Court of Texas described one such contract:
The contract itself did not obligate Westlake Chemical to assign James any work. Rather, under Section 1.2, if Westlake wanted James to "perform certain services and/or provide equipment, materials, supplies or other products," and James "agree[d] to perform and/or provide such Work," then Westlake would issue a work order for James to execute.
The contract confirmed that "[u]nless and until a Work Order has been executed by the Parties," Westlake was not obligated "to retain [James] for any Work" and James was not obligated "to accept any request for any Work."
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.
19.3. 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[:][A]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 …."
Back in 1986, federal judge Richard Posner 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 ….
Other cases and commentators have reached the same conclusion.
Comment
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).
[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.)
19.5. 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).
19.5.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 Section 8.22.]
[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."
19.5.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), 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).
19.5.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.
19.5.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).
19.5.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:
Best Pricing Clauses (KnowledgeToNegotiate.blogspot.com 2011; from a customer's perspective)
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.
Pro tip: It's "net 10 days," not "net ten days" — this is an exception to the usual rule about numbers discussed at 33.9.2.
20.2. 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.
20.2.1. Non-discrimination language?
A non-discrimination requirement at least brings a bit of overall-market discipline into the picture.
Example: "Vendor will not increase the prices it charges to Customer except as part of a non-targeted, across-the-board pricing increase by Vendor, applicable to its customers generally, for the relevant goods or services."
Comment: Vendor might want to qualify this language, so as to limit how general a price increase must be before it can be applied to Customer.
20.2.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: Vendor will give Customer at least X [days | months] advance notice of any increase in the pricing it charges to Customer under this Agreement.
20.2.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 has the right to do it.
Here's an example:
If requested by Customer within X days after notice of a pricing increase, Vendor 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 Vendor'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.
20.2.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.)
20.2.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.)
20.2.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.
20.2.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.
20.2.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.)
20.2.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; your author often uses 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 (9.8).¯
20.3. Notarizing a document (notes)
Typically, it won't be necessary (nor desirable) to get a contract "notarized." Sometimes, however, a party will want, and might need, to get "ancillary" documents — for example, a deed or an assignment of rights — "acknowledged" before a notary public (or other official) by one of more of the signers.
20.3.1. In contracts, "notarizing" (usually) means acknowledging
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:
appeared before the notary;
presented sufficient evidence to establish his or her identity (e.g., a driver's license, a passport, etc.); and
stated to the notary that he or she (the signer) signed the document.
20.3.2. Why acknowledge? To show non-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).
20.3.3. Must the document's signer swear to its truth?
Not usually: The type of notary certificte 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.
20.3.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]
20.3.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.)
20.3.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.)
20.3.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
20.3.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).
20.3.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.)
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.
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.
• 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).
Author's 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?
This Agreement will apply when, under the Contract, specified parties, referred to as "Customer" and "Supplier" respectively, agree to conduct one or more transactions such as, for example,
one or more sales or other deliveries of tangible- or nontangible goods, equipment, or other deliverables; and/or
the performance of services.
Each such transaction agreement is referred to as an "Order."
In case of doubt: Unless otherwise agreed in writing, the Customer might not be an end-customer, but instead might be a reseller, a distributor, etc.
21.2.2. Any requirements for packaging and labeling?
The Supplier is to cause all deliverables to be appropriately packaged and labeled for shipment and delivery; this includes, without limitation, conformance to:
any requirements of law (including for example any required country-of-origin labeling); and
any specific packaging- and/or labeling instructions in the Order.[a]
If the Customer provides a purchase-order number or other identifier for the order, then the Supplier is to cause that identifier to be included on shipping labels, shipping documents, and Order-related correspondence.
Comment
[a] 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.
21.2.3. Must delivery times be exact?
The Supplier is to cause[a] deliverables specified in the Order to be delivered in the time frame stated in the Order (if any).
When an Order specifies a delivery time, the Supplier will not be liable if the actual delivery time is early or late, as long as:
the variation is not unreasonable under the circumstances, and
the Order does not clearly state otherwise, for example by stating that "time is of the essence."[b]
Comment
How much flexibility should a supplier have in the timing of delivery? Let's assume that if the customer wants to insist that delivery timing is critical, then the order can say so.
[a] This is phrased as "Supplier is to cause" delivery, instead of "Supplier will deliver," because in many cases Supplier will use a carrier to actually make the delivery.
Alternative:
Supplier is to endeavor to cause delivery …."
(Leave out the italics, usually.)
[b] See generally the commentary on "time is of the essence" at [BROKEN LINK: time-essence].
21.2.4. When will title, and risk of loss, be shifted to the Customer?
If the Order does not specify otherwise, delivery is to be in accordance with INCOTERMS 2020 DDP,[a] including but not limited to its provisions for passage of title and risk of loss.[b]
Comment
[a] 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.
[b] As a default measure (and in keeping with this book's service-to-others orientation), this section puts the onus on the Supplier to get the goods or other deliverables to the Customer's door, so to speak, unless otherwise agreed.
21.2.5. Order fulfillment - discussion questions
What are some pros and cons of spelling out, in the contract, the information that Customer must submit in an order?
What are some pros and cons of:
having each order become an addition to the master agreement, versus
having each order be a separate agreement that incorporates the master agreement by reference.
Why might a supplier want a quotation to have an expiration date?
What are some pros and cons of allowing orders to be modified orally and not requiring written modifications?
FACTS: You represent Supplier. Customer wants its "affiliates" to be listed in the preamble as parties to the agreement, e.g., "The parties are ABC Inc. ('Supplier') and XYZ Inc. and its affiliates ('Customer')."
QUESTIONS: (numbering is continued before)
As Supplier's lawyer, what do you think of this — what do you think Customer really wants?
How might you structure the contract to accommodate Customer's likely desires — and to protect Supplier?
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 Clause 3.6), 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:
Make a list of things to discuss with the partner or client.
Schedule a meeting or phone call (or Zoom- or Teams call).
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 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 30.4]: 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 8.20.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].
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 8.19.1.]
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, andI 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).
Comment
22.2. Partner Preference Rule
When it comes to purely-stylistic preferences, do it the way the 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 29.15).
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.
22.4. Preambles: Front-load some useful information?
Very few contracts are ever litigated. But when drafting a contract in traditional form, it takes very little time for the drafter to help out future trial counsel by including some useful information.
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.
22.4.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") …."
Your author prefers the shorter approach shown in the quoted example above:
[ ] THIS PURCHASE AND SALE AGREEMENT (this "Agreement") ….
[ x ] 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 29.15.
(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: Serve the Reader.)
22.4.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") ….
[ x ] … 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.
22.4.4. Defined terms: Bold type, quotaion 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), ….
[ x ] … 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 29.6 for more discussion of defined terms.)
22.4.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 ….
[ x ] 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 32.)
22.4.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:
[ x ] Betty’s Used Computers, LLC, a Texas limited liability company ….
[ x ] 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 7.1), 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 24.4 for more about signature blocks for organizations.
22.4.7. Maybe: State the principal place of business (or residence) and initial address
Our preamble states some geographical information about the parties, with the same goals as stated at 22.4.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. For example, a Delaware corporation whose principal place of business was in Houston would almost certainly be subject to suit in Houston.
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 and not in 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.
22.4.8. State the effective date in the preamble? (Maybe not.)
The above preamble affirmatively states the effective date; that’s usually unnecessary (and it's not your author's preference) 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.)
Your author prefers the last-date-signed approach:
[ x ] This Agreement is effective the last date written on the signature page.
[ x ] 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 ….
[ x ] 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 (22.1)?
22.4.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.
[ x ] 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 10.1, that practice has sent more than one corporate executive to prison, including at least one general counsel.
22.4.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 7.2.5 for more details.
[ ] This Agreement is between (i) ABC Corporation, a Delaware corporation, and its Affiliates … and (ii) XYZ Inc., a New York corporation ….
[ x ] 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.
22.4.11. Is country-specific information required?
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.
22.4.12. Naming the "wrong" party can screw up contract enforcement
Be sure you’re naming the correct party as "the other side" — or consider negotiating a guaranty (see Clause 2.10) from a solvent affiliate.
Failing to name the correct corporate entity could leave your client holding the bag. This seems to have happened in the Seventh Circuit's Northbound v. Norvax case, discussed at 7.2.4, 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.
22.4.13. Does each party have 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.
22.5. 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.
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
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."
22.7.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: In 2020, 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).
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.
[ x ] (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 Pasta Rule (30.3): 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.
[ x ] 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.
"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."
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?
23.1. Readouts: Written summaries of meetings or calls
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 U.S. and Chinese presidents.
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.
23.2. 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.)
23.3. Represention drafting: A style rule
Representations are (almost always) made by individual parties, not by multiple parties jointly.
Conceivably, a "Both parties represent" phrasing could provide an opening for one of the representing parties to assert "mutual mistake" as an escape from liability for misrepresentation.
The assertion might not work, but let's not leave the opening.
Example:
[ ] Both Parties represent that they are not subject to any exclusion order barring them from federal-government contracts.
[ x ] Each Party represents that it is not subject to any exclusion order barring it from federal-government contracts.
23.4. 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.
"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.
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 8.18.14
23.4.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
B. 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; …
23.4.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:ResMan, LLC (E.D. Tex. 2021), 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), followingBowers 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).
23.4.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 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:
an acquiring company creates a transitory subsidiary,
that subsidiary merges into a target company,
and then that target company survives as the new subsidiary of the acquiring company.
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 10.2 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 "wall of words" 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 [BROKEN LINK: short-sentences].
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.
23.7. 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: In 2005, the SEC explained the basics of round-trip transactions in a 2005 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.
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 2001.
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. …
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!
24.1. 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.
24.2. Severability of contract provisions (notes)
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.
24.3. Signature authority
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.
Contents:
24.3.1. 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. See Liberty Ammunition, Inc. v. United States, 835 F.3d 1388, 1401-02 (Fed. Cir. 2016). In dissent, Judge Newman argued that the senior Army officer who signed a particular NDA had at least apparent authority, and so (said the judge) the government should have been bound by the NDA. See id. at 1403-05; see also the discussion of apparent authority below.
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.
24.3.2. 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 has authority to make commitments on behalf of the company. See Restatement (Third) of Agency § 3.03 cmt. e(4) (2006), quoted inElaazami 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 to make oral promise of bonus payment to later-fired employee).
24.3.3. But apparent authority can save the day
An individual who has "apparent authority" can bind a party to a contract — unless a hypothetical reasonable person would have reason to suspect otherwise.
24.3.3.1. What does "apparent authority" mean?
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).
24.3.3.2. Apparent authority can be ruled out (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.
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.
24.3.3.3. 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).
24.3.4. The gold standard: A board resolution — but not for everyday
The gold standard of corporate signature authority is probably a certificate, signed by the secretary 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.
24.3.5. Consider asking for a personal signer representation
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, such as the following:
Each individual who signs this Agreement on behalf of an organizational party represents that he or she has been duly authorized to do so.
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 following example.
24.3.6. Or, just take the risk?
The present author 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 Gigunda individual contributor; let's call her "Sarah" (not her name).
I raised the issue of apparent authority with the MathWhiz senior executive, who responded that he had been dealing exclusively with Sarah in negotiating the agreement, but 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 try to change the signature block to reflect someone else's title — it might offend Sarah, and it would certainly delay getting to signature, with little or no real reduction in MathWhiz's business risk.
MathWhiz did as I recommended; the parties signed the contract and carried it out to everyone's satisfaction.
24.3.7. 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 the case if the articles of organization (which are usually publicly available) expressly deprive the signer of such authority.
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.
The 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.
24.3.8. Consider including authority-disclaimer language
Some drafters might want to be explicit about who does not have signature authority, to help preclude a party from claiming to have relied on the apparent authority of other would-be signers.
This approach can sometimes be seen in sales-contract forms used by car dealer, which can say, typically 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."
24.4. Signature blocks
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.
24.4.1. Precede with a concluding paragraph? (No.)
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.
Such paragraphs are unnecessary; here's why:
First, that kind of concluding paragraph is 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, don't change it (as discussed in 32).
24.4.2. Signature dates
Author's note: I usually draft signature blocks with blanks for the signers to hand-write the date signed; see the example shown at 24.4.9.
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 10.1).
[ x ] "Signed on the dates indicated below"
[ ] "Signed December 12, 20xx"
For similar reasons, it's better not to type a purported date in the preamble:
[ x ] "This Agreement is made effective the last date signed as written in the signature blocks …."
[ ] "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 _ _, 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!)
24.4.3. Corporate- and LLC signature blocks
The signature blocks shown at 24.4.9 (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 10.1.
• 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. See 24.3.3.
24.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
24.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.
[ x ] Jane Doe
[ ] Ms. Jane Doe
[ ] Jane Doe, Esq. (if Jane is a lawyer)
[ ] Jane Doe, Ph.D. (if Jane holds that degree)
[ x ] Jane Doe, M.D. (physicians seem to like including those post-nominal initials)
24.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.)
24.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 10.1). 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.
24.4.8. Try to keep signature blocks on the same page
The author prefers 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."
24.4.9. Put the signature blocks 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 make the agreement more reader-friendly:
You can see at a glance whether you're looking at the signed agreement; and
To find a party's (initial) address for notice, you don't need to go rummaging through the document
24.4.10. 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 the contract later "goes south," the lawyer won’t want her 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:
Novartis’s top lawyer is to retire from the company over payments made by the pharmaceutical giant to President Trump’s personal lawyer Michael D. Cohen, the Swiss drug maker said on Wednesday. * * *
"Although the contract was legally in order, it was an error," Mr. Ehrat said. "As a cosignatory with our former C.E.O., I take personal responsibility to bring the public debate on this matter to an end."
Any provisions after the signatures should be clearly incorporated by reference Example: In Dixon (Ky. 2015), 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 Clause 8.34, concerning incorporation by reference.)
Here are some basic tips for drafting a term sheet:
Short "macaroni" sentences are best — ideally, one per paragraph (30.3).
Be very clear who is responsible for doing what, when, to avoid false imperatives (29.14); as the business cliché puts it: Whose throat gets choked?
Specify any relevant time frames such as:
deadlines;
earliest- and latest start dates; and/or
maximum- or minimum time periods.
Fences: Spell out any relevant restrictions or limitations. For example: If payments must be made by wire transfer, then say so.
If your client is or will be relying on information provided by another party, then consider saying so, to make it easier for your client to prove a misrepresentation claim if necessary (3.15.3; see the discussion of the "Hill of Proof" at 3.17.2).
Bullet points are fine as long as they're clear.
Hypothetical examples (30.10) can be really useful to illustrate points and educate future readers, such as:
business people who need to get up to speed;
judges and jurors.
Diagrams, tables, flow charts, footnotes (30.10)? Why not — when in doubt, Serve the Reader! (30.1.1).
25.2. Text-message conversations can be binding
Caution: Even a very-terse exchange of text messages or instant messages ("IM") can create a binding contract.
25.2.1. Example: Agreeing to sell an entire warehouse of furniture
Two Texas furniture dealers had a conversation — entirely by text message — in which they negotiated for one of the parties to sell the entire contents of a furniture showroom to the other party.
The conversation ended with the parties agreeing to the transaction — but the seller backed out.
The buyer sued and won a partial summary judgment that the parties had entered into an enforceable contract. An appeals court affirmed that part of the judgment. See 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) (affirming judgment below in relevant part).
25.2.2. Example: Agreeing to pay more than $1 million in extra ad-buy fees
An IM exchange between a digital ad agency and an electronic cigarette manufacturer served as a binding agreement to increase the ad agency'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).
25.2.3. Caution: California law limits contracts-by-text in real-estate deals
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).
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 your author's 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 7.31.
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 30.13)}}} 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.
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
27.1. Within X [hours] "of" Y: Before Y, or after?
From the NY Times, about improvements in training junior doctors to intubate infants:
Intubation 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.
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) …."
Author's 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?
27.2. Within X [hours] "of" Y: Before Y, or after?
From the NY Times, about improvements in training junior doctors to intubate infants:
Intubation 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.
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) …."
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.
(For numerous examples of court cases involving email contracts, see the following footnote:)
Comment
Email contracts: In various cases, courts have held that exchanges of emails were sufficient to form binding contracts for: [Students: Just scan the following list for general familiarity; you won't be tested on the details.]
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 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, 384 Wis. 2d 632, 922 N.W.2d 310 (2018) (per curiam, affirming judgment on jury verdict; unpublished);
the 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);
an employment agreement including nine months' severance pay in case of termination, see Nusbaum v. E-Lo Sportswear LLC, No. 17-cv-3646 (KBF), slip op. (S.D.N.Y. Dec. 1, 2017) (granting former employee's motion for summary judgment). 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." Id., slip op. at 9 (emphasis added);
settlement of a lawsuit — notice how many cases there are in this category; 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).
28.1.2. How business seem to view email-exchange contracts
A quick exchange of emails can be a low-cost way to enter into a contract. But email exchanges don't seem to be used as contracts very often.
One possible reason: Parties often neglect to file emails in an organized fashion. If that happened with an email contract, a party might forget about the contract.
And if a party forgot about an email-exchange contract, then perhaps one day the party might find itself (i) in breach of the contract, or (ii) missing a deadline to claim a benefit.
So parties often prefer contracts to be a bit more formal.
BUT: Parties might use an email exchange for "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.1.3. The usual requirements for contracts must be met
An email exchange won't create a binding contract if the content of the emails fails to meet the usual requirements of establishing a meeting of the minds on all material terms, consideration, and an agreement to be bound.
28.1.4. Signatures can be email signature blocks or even names in "From" fields
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.37
Comment
28.1.5. Emails can be convenient for pro forma written contracts
Email contracts can be especially useful when "it's not a big deal" and the parties are mainly interested in having something in writing. For an example, see this blog entry about a contract that your author helped a client to negotiate a few years ago: By prearrangement with The Other Side's lawyer, the parties "signed" the contract by exchanging "We agree to the attached final draft" emails.
28.1.6. Pro tip: Consider a disclaimer in your email signature block
Because of the established law discussed above, your author has long included a disclaimer in email signature blocks; at this writing (early 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.
Letter agreements can work because they're (often) simpler yet still get the job done. That can be appealing to business people, who aren't fond of spending time negotiating contract terms and conditions.
28.2.2. The Pathclearer letter-agreement approach: Rely on the general law
Example: One 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. The Pathclearer approach entails:
using short letter agreements instead of long contracts, and
relying on the general law and commercial motivations — i.e., each party's ability to walk away, coupled with each party's desire to retain a 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 (emphasis added).
Tangentially related: In a dictum, the Ninth Circuit noted: "If the copyright holder agrees to transfer ownership to another party, that party must get the copyright holder to sign a piece of paper saying so. It doesn't have to be the Magna Charta[sic; Carta]; a one-line pro forma statement will do." Effects Assoc., Inc. v. Cohen, 908 F.2d 555, 557 (9th Cir. 1990) (affirming summary judgment; emphasis added).
28.2.3. Offer letters as employment agreements
Letter agreements are often used for employment agreements, in form of offer letters.
Then there 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. The Ford-Bond letter agreement is archived at https://perma.cc/53XV-43TD.%3C/cite%3E
28.2.4. NDAs [sic] by letter
See the short letter agreement "NDA" (confidentiality agreement) that your author drafted as a baby lawyer, discussed at 30.2.
28.3. 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 your author eviewed 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. Note: At this writing (January 2025), the Biden Administration's decision is being challenged in court.
• Somewhere in the middle, complexity-wise, are online agreements such as that for customers of Amazon Web Services.
28.4. Review: Basic requirements for a binding contract
Here's a basic review: An agreement will typically be legally binding as a contract if it meets the usual requirements, such as:
There must be a "meeting of the minds," generally in the form of an offer by one party that is accepted by another party.
"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."
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), citingTenn. Code Ann. § 47-50-103.
28.5. Review: Oral contracts can be binding
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.
(This section uses the term oral contract, because strictly speaking a written contract is also "verbal," that is to say, "of, relating to, or consisting of words." See Verbal (adjective).)
28.5.1. 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:
The contract cannot be of a type that, by law (the Statute of Frauds), must be in writing (see the discussion at 28.5.2); and
The jury,* after hearing the witness testimony and weighing the evidence, must find that there was, in fact, an oral agreement. (* Or the judge in a nonjury trial, or the arbitrator in an arbitration.)
An email trail might not be enough to be binding in itself as a written contract, but it can provide evidentiary support for a jury verdict that an oral contract was reached; this happened, for example, in an Idaho supreme court case. See, e.g., Hawes v. Western Pacific Timber LLC, 477 P.3d 950, 963 (Id. 2020) (affirming judgment on jury verdict for breach of oral agreement to pay severance).
As another 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 jurors believed the employee; they didn't buy the company's claim that the employee had been told only that he might get a bonus. 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).
Now recall that under standard American legal principles — including the Seventh Amendment to the U.S. Constitution — if a reasonable jury could reach the verdict that the actual jury did, then the actual jury's verdict must stand (with certain exceptions).
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 3.1.6.
28.5.2. 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 won't discuss here.
28.5.3. 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 20.3.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 could be performed within a year is not within the Statute, even if it turns out that the agreement actually did take longer than a year to perform. (See the extended discussion of this topic in a 2024 Fifth Circuit decision.)
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 Clause 2.10) for someone else's debt.
28.5.4. 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."38 (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?)
Comment
28.5.5. Use a written contract to replace an informal oral agreement?
As addressed at 6.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.
28.5.6. Oral contracts can result in big-bucks jury verdicts
Example: In a Minnesota case, a jury awarded a bank $1.9 million for breach of an oral agreement to buy assets:
The bank loaned money to a trash-collection company (the "borrower").
The borrower's business failed; the borrower filed for bankruptcy protection.
The bank sought bidders for its borrower's business assets (garbage trucks, etc.).
The bank itself bought its borrower's business assets.
The bank entered into an oral "flip" agreement with Buyer 1, under which Buyer 1 would acquire the business assets from the bank for $6 million.
Buyer 1, though, backed out of its oral agreement with the bank.
The bank sold the business assets to Buyer 2 — but at a significantly lower price.
At trial, the jury found that Buyer 1 had breached its oral contract with the bank and awarded the bank $1.9 million in damages; the state supreme court affirmed. See Vermillion State Bank v. Tennis Sanitation, LLC, 969 N.W.2d 610 (Minn. 2022): The court held that the Statute of Frauds in UCC article 2 did not apply because the "predominant purpose" of the parties' "hybrid" oral contract (involving both goods and intangible assets) was not for the sale of goods; "most witnesses testified to the primary value being the customer routes" (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).
29. Appendix: Mechanics of starting a drafting project
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 11.4.)
29.2. 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 usually want to use their contract forms, not yours.
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 ….
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 startthis 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.
29.3.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.
29.3.3. Online forms abound — but use with caution
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 is not 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 2007 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 that closed its doors in 2014 when hundreds of its lawyers left to join the Morgan Lewis firm.
29.4.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:
29.4.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 the 2000 "Agreement" between Amazon and Drugstores.com — you guessed it, the title is "Agreement."
AGREEMENT
This Agreement, dated as of January 24, 2000 is made and entered into by
and between Amazon.com Commerce Services, Inc., ("ACI"), an indirect wholly
owned subsidiary of Amazon.com, Inc. ("Amazon.com"), and drugstore.com, inc.
("drugstore.com"). ACI and drugstore.com sometimes are referred to collectively
as the "Parties" and individually as a "Party." ACI and drugstore.com agree as
follows:
29.4.3. Title style 2: More information
A more-expansive style is fairly typical for contracts:
Agreement and Plan of Merger
29.4.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 style 3, incidentally, is from the 2023 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.
Caution: From style 3, be careful about including "Dated as of …" 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 29.15.)
29.5. Copy-and-paste can be dangerous if done mindlessly
Don't just copy and paste language from an old contract without thoroughly reviewing it. 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.
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.
Put the defined-term label in bold-faced typeand quotation marks (and possibly parentheses).
Examples:
[ ] This Agreement is between MathWhiz LLC, a Texas limited liability company ("MathWhiz") ….
[ x ] This Agreement is between MathWhiz LLC, a Texas limited liability company ("MathWhiz") ….
Another example:
[ ] The term "Affiliate" refers to ….
[ x ] 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.
[ x ] 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.
29.6.2. The 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 22.4.
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.
29.6.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:
right after the Background section — this is perhaps the most-common practice;
at the back of the contract, just before the signature blocks or as an appendix after the signature blocks (with results that might be surprising, as discussed in the note just below); 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. Cummins 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).
in a separate exhibit or schedule (which can be handy if using the same definitions for multiple documents in a deal).
29.6.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.
29.6.5. Don't put substantive terms in definitions
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."
29.6.6. Other style preferences for defined terms
The following are some personal style preferences that help enhance readability (in your author’s 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):
Before:
[ ] Confidential Information means information where all of the following are true ….
[ x ] "Confidential Information" refers to information where all of the following are true ….
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).
29.6.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. 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 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).
29.7. Incorporate external materials by reference?
Consider incorporating external materials by reference, and perhaps including Clause 8.34 to be explicit about the co-equal status of the incorporated materials.
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.
29.7.2. Incorporations "must be clearly and expressly identified"
In a 2022 decision, 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.
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).
Wording can matter – Example: In a 2024 decision, the "Warranty" section of the contract in suit 3stated: "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).
29.7.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: In a 2015 decision, Oklahoma's supreme court ruled that a contract form for the sale of hardwood flooring did not successfully incorporate "Terms of Sale," mentioned in the form, because the contract form gave no indication where to find the referenced terms:
[A] contract must[:]
make clear reference to the extrinsic document to be incorporated,
describe it in such terms that its identity and location may be ascertained beyond doubt, and
the parties to the agreement had knowledge of and assented to the incorporated provisions. …
BuildDirect's attempt at incorporation was nothing more than a vague allusion.
Pro tip: At the very least, provide a Web link — preferably a short, memorable one — where the additional incorporated terms can be found.
29.7.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 a 2015 Nebraska supreme court decision:
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.
29.7.5. But a clear intent to incorporate might suffice
In a 2014 decision, the Fifth Circuit 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 it 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).
29.7.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.
29.7.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.
29.7.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.
29.7.9. A purchase order might implicitly incorporate text
In a 2016 decision, 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 8.22), 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.*.
29.7.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).
29.7.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.
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).
29.7.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).
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 your author started this project several years ago ….
29.8.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:
1. One of the defendants, Robert Urich ("Dad"), was the father of Stephen Urich, who was one of the principal actors in the events leading to the lawsuit.
Dad was the treasurer of Stephen's company; Dad had signed the contract that was the subject of the lawsuit, but 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, Vice Chancellor Zurn 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, slip op, at part II.B.2, text accompanying nn.248, 255.
2. The screwed-up cross-references also hurt the plaintiff — one of them led to the court's refusing to grant preliminary injunctive relief against defendant Stephen for allegedly breaching a noncompetition covenant:
Section 9.12 of the contract expressly allowed any party to sue for specific performance; that normally would have provided a basis for the court to grant a preliminary injunction to enforce the noncompetition covenant.
But the contract also contained an exclusive-remedies provision: Apart from a carve-out for "Section 10.12," the parties' only recourse would be indemnification in certain stated circumstances.
Vice Chancellor Zurn said that she was inclined to agree with the plaintiff that this carve-out of Section 10.12 was meant to cover the specific-performance provision of Section 9.12. But she ruled that she'd have to wait for trial to make that determination based on a more-developed factual record. 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.
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
29.8.3. Use special software to check cross-references?
Your author has 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.
(Author's note: Decades 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".)
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.
29.10. Schedules: Use for deal-specific "variables"
You might know from experience that the other side is likely to want to make changes to certain contract terms. For example, a supplier who asks for net-30 payment terms might know that some customers will want net-45 or even net-60 terms.
If that's the case, then 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: Consider the following excerpt from a 2007 real-estate lease between Stanford University (landlord) and Tesla (tenant):
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. Any capitalized term not defined in this Lease shall have the meaning set forth in the Glossary that appears at the end of this Lease.
Address of Premises: 300 El Camino Real, Menlo Park, California
Term: Five (5) years
Scheduled Date for Delivery of Premises: August 1, 2007
Commencement Date: August 1, 2007
Expiration Date: July 31, 2012
Base Rent:
Year One:
$60,000 ($5,000 per month)
Year Two:
$90,000 ($7,500 per month)
Year Three:
$120,000 ($10,000 per month)
Year Four:
$165,000 ($13,750 per month)
Year Five:
$165,000 ($13,750 per month
This 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 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 29.5).
(This principle is an example of the rule: R.O.O.F: Root Out Opportunities for F[oul]ups.)
29.11. Side letters: Caution! (notes)
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.
According to the SEC, the customer sales executive not only knew that the supplier planned to fraudulently misstate its financial results, he even advised the supplier's own sales people how to conceal the cancellation right from the supplier's finance department. See Securities and Exchange Commission Press Release, SEC Charges Former Logicon Executive With Aiding and Abetting Financial Accounting Fraud at Legato Systems, Sept. 8, 2003 (SEC.gov).
The customer's executive later consented to a $35,000 fine and a cease-and-desist order prohibiting him from future violations — which was not a good career move, because it's the sort of thing that can hinder someone's future job prospects, possibly disqualifying the person from certain regulated- or licensed positions in the financial industry. See Securities and Exchange Commission Litigation Release No. 19385, Court Enters Final Judgment Against Former Sales Executive of Customer of Legato Systems, Inc., Sept. 21, 2005 (SEC.gov).
It's usually worth 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. 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 [BROKEN LINK: conf-info-expir-cmt] for more on this particular example.)
29.13. 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 Party A will pay $3.00 per share, provided that, if it it rains at least 6 inches on Sunday, then Party 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:
Party A will pay the amount stated in the table below, based on how much rain falls on Sunday:
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
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:
Party 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?
29.14. False imperatives: Whose throat to choke?
A "false imperative" is a provision in a contract — commonly written in passive voice, see 33.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.
If the pest-control requirement is in a section titled, e.g., "Tenant's responsibilities," 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.
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)
29.15. D.R.Y.: Don't Repeat Yourself (in critical areas)
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.
[ x ] 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. • Unfortunately for the bank, though: 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). So 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.39
(You probably wouldn't want to be the junior associate or paralegal who oversaw the document preparation in that case.)
Example: One of your author’s 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.9.7
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.
[ x ] 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.)
Comment
29.15.2. D.R.Y. for fill-in details ("variables")
If you're using a schedule (see 29.10) 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:
define a term for each of those details, e.g., "Buyer," "Purchase Price," etc; and
elsewhere in the document, use that defined term exclusively (perhaps with a cross-reference to the schedule).
[ x ] The Buyer will pay the Seller the Purchase Price.
† Note the spelling out of "million"
29.15.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 30.18), not merely to slavishly follow drafting guidelines like this one.
30. Appendix: General strategic drafting principles
— Jim VandeHei, Mike Allen, and Roy Schwartz, Smart Brevity ch. 1 (2022) (edited).
"Serve the Reader!" is easily the leading candidate for The Great Rule of All Writing.
When drafting a contract, you'll want to ask yourself: • Who will be reading the contract? • What tasks will your readers need to do with the contract? • For each of those tasks: How can you help the reader do the task?
30.1.2. Serve the client by serving the readers, plural
As contract drafters:
For now: We want our clients to be able to quickly make informed choices at all phases of the contract-negotiation process. That means making our contracts easy for clients to read, by following:
the Pasta Rule: Draft macaroni clauses, not spaghetti (30.3); and
For later: We want our clients' deals to work — to help clients serve their own (lawful) needs and those of their customers and other stakeholders and to build reliable, resilient business relationships that can be leveraged in the future. For the contract drafter, that means "learning the [client's] business" and looking ahead to future opportunities and threats (see 31).
For later still: If a serious contract dispute arises, we want to serve our clients by helping other readers to to quickly and accurately grasp what the parties did agree to; those other readers could include, for example:
each party's senior business people, who might fear losing but might also fear that backing down could show weakness;
the parties' lawyers, looking for language loopholes to justify telling their clients what they (the clients) want to hear;
perhaps a judge and his/her law clerk, reading the contract "cold" and wondering, á laLiz Lemon: What the what?; and
(rarely) jurors in a contract-related lawsuit.
Finally, for lawyers there's the little matter of serving the public good; that duty arises from the role that each lawyer plays as "an officer of the legal system and a public citizen having special responsibility for the quality of justice." The quoted language is from the very-first sentence of the ABA Model Rules of Professional Conduct, which are the basis of the legal-ethics rules in many if not most American states.
30.1.3. The client's likely goal: Get an "OK" deal signed now
In one way, we contract drafters are like high-society caterers: We prepare what our clients want, using skills that they might or might not have, and they expect top quality.
But in contract cuisine, the reality is less glamorous. Our "diners" are in a hurry: They want reasonably-tasty meals. They want quick service. They don't want to pay Michelin-star prices.
Let's face it: We're not celebrity chefs. We're short-order cooks in an Appleby's or Chili's restaurant.
In Contract World, clients typically want contract drafts to strike a reasonable balance between:
getting signed as quickly as possible — because everyone involved has other things to do. This generally means writing the draft in the plainest language possible;
after signature, providing the parties with an understandable user manual for their deal;
addressing not-unlikely future contingencies — but without trying to cover every conceivable scenario (which would increase the cost of the negotiation in both money and time);
if necessary, helping a judge and jurors get up to speed about the deal (although the vast, vast majority of contracts never go to court); and
Now: Imagine that a client had a choice between:
a relatively short, utilitarian draft contract that did a reasonable job of covering the bases above and could get to signature quickly; versus
an exhaustive (and exhausting) encyclopedic draft, written in long, wall-of-words paragraphs of complex legalese.
It's a safe bet that, in the history of the world, no client has ever asked for the latter.
30.1.4. Contract review can be a bottleneck
When a client asks for a contract to be drafted, the client probably imagines (often correctly) that the business terms are pretty much agreed and that the only thing standing in the way of a done deal is "legal" — both the client's lawyer and the other side's lawyer.
But it's usually more-complicated than that: A contract will almost never get signed before it has been extensively reviewed, on both sides of the deal, by (often multiple) lawyers and business people, and sometimes by accountants, insurance professionals, and others.
Toward that end: To speed up the process — and keep the client happy on that score — make your contracts as easy to read and review as possible, given the time- and budget constraints under which you're working.
30.2. Draft something the other side could sign quickly?
Some years, ago, your author started work as an associate at Arnold, White & Durkee, then one of the largest IP-litigation firms in the United States. One day, the senior name partner, Tom Arnold, † assigned me to draft a confidentiality agreement for a friend of his, "Bill," who was going to be disclosing a business plan to Bill’s friend "Jim."
† A personal note: Tom Arnold (1923-2009) founded the law firm Arnold, White & Durkee, which grew to become what we think was the second-largest intellectual property boutique in the United States, with some 150 lawyers in six cities across the country. (In 2000, the firm merged with national antitrust litigation boutique Howrey & Simon.) "TA," as we referred to him, was everything a lawyer should be; multiple lawyers outside the firm told me that Tom was very likely the best-known IP attorney in the world. Tom hired me at the firm, I think in part because we'd both been seagoing Navy engineering officers, with his service coming during World War II and mine during the Cold War. For many years Tom and his wife, the aptly-named Grace Gordon Arnold (1926-2015), were very good to my wife and me; I'm proud to have been Tom's law partner and friend.
Tom instructed me not to draft a conventional contract for his friend. Instead, the confidentiality agreement was to take the form of a short letter. I don't remember exactly what it 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, isn’t this pretty sparse? Tom agreed that yes, it was sparse — but:
The signed letter would be a binding, enforceable contract — Bill could take it to court if his friend Jim breached it (which Bill judged to be a low risk).
Equally important to Bill: Jim would probably sign the letter immediately, whereas if Bill had asked Jim to sign a full-blown confidentiality agreement, Jim likely would have asked his lawyer to review the full-blown agreement.
If Jim's lawyer had gotten involved, it 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 the changes that Jim's lawyer likely would have requested.
That experience was an eye-opener. It taught me that contracts aren’t magical written incantations: they’re just simple statements of simple things.
The experience was also my first 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) "acceptable business risk," than they are in signing a theoretically-better contract, but having to wait around to do so.
30.3. The Pasta Rule: Short, single-subject paragraphs
In the computer-software world, the term "spaghetti code" is a mildly-contemptuous epithet for unstructured, hard-to-maintain source code for computer programs. The name derives from the observation that cooked spaghetti is something of a tangled mess. Spaghetti code "can be due to any of several factors, such as volatile project requirements, lack of programming style rules, and software engineers with insufficient ability or experience." Spaghetti code (Wikipedia.org).
The same can be true with contract clauses when drafted by L.O.A.D.s — Lazy Or Arrogant Drafters (30.5). Example: Here's a side-by-side comparison by Wikimedia of two versions of a well-known Creative Commons license document:
Even without reading the actual text, which version above would you prefer to review? See also the horrible example at the following footnote, and a before-and-after example at 30.4.
In contrast, cooked macaroni is easy to separate and to move around as desired.
So: Strive to write modular "macaroni clauses," i.e., short, single-subject paragraphs, and eschew — nay, scorn — "spaghetti clauses." Author's note: I originally used the term barf clause to describe convoluted contract language, but spaghetti seems to be a better visual metaphor. The term "barf clause" was inspired by Jennifer Pahlka's (excellent) book, Recoding America: Why Government Is Failing in the Digital Age and How We Can Do Better: In chapter 8, the author quotes an unnamed digital-services designer as saying that an agency "had 'vomited the policy into the forms.' She [the designer] meant not that the policy stank, necessarily, but that it had been left as an essentially undigested mess."
30.3.2. Why draft modular macaroni clauses?
It's relatively quick and easy to draft a tangled-spaghetti clause: You just put words on the page as they come to you. Less drafter time means lower client cost, right?
But that's not the only consideration:
• Your client wants the deal signed ASAP.
• You want to try to avoid having your draft contain hidden landmines — which you could later be blamed for if the deal were to go sideways.
• Your draft might very well get some of the deal details wrong, or create ambiguities — we all do it now and then. This could someday lead to costly litigation. So, you want to make it easier for your supervising partner (if any) and your client to spot problems in their own review of your draft.
• Once you send the draft to The Other Side, you and your client will be impatiently waiting for The Other Side's lawyer to review your draft.
• If negotiations ensue, and your draft needs to be revised, then you want that process to go as quickly and smoothly as possible.
• Now suppose the contract is signed but the transaction or relationship doesn't go well. Litigation could ensue. The judge, the judge's law clerk, and possibly jurors, will be reading the signed contract. You'll want them to quickly understand the relevant agreed terms: that way, they'll be less likely to be fooled by the "creative" contract-interpretation arguments of The Other Side's trial counsel.
That's where following the Pasta Rule can help: Write macaroni clauses.
30.3.3. How? By breaking up "spaghetti" clauses
Following the steps below will help drafters to avoid writing spaghetti clauses:
In each (short) paragraph in a contract, 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. That way, contract clauses can be more like macaroni — or even broken-up spaghetti noodles.
30.3.4. Preferring short, single-subject paragraphs isn't new
Write short paragraphs and cover one topic per paragraph.
Long paragraphs discourage users from even trying to understand your material.
Short paragraphs are easier to read and understand. …
There is nothing wrong with an occasional one-sentence paragraph.
(Emphasis added.)
30.3.5. Three crucial reasons for short paragraphs
Drafters should take the time to craft short paragraphs because — other things being equal:
1. Short paragraphs are easier for The Other Side to review and, if necessary, revise during negotiation; this can speed up the negotiation process and help the parties get to signature sooner.
2. Short paragraphs are better workaday tools for business managers — and, if necessary someday, for trial counsel and judges.
3. Short paragraphs can be more-easily copied and pasted into a different contract without inadvertently messing up some other clause.
30.3.6.Paragraph length matters more than contract length
For readability, paragraph length matters more than contract length.
True, sometimes contracts run too long as a whole. That's often because of over-lawyering, where the drafter(s) try to cover every conceivable issue.
But focusing too obsessively on the length of a contract will obscure a more-important issue: the contract's readability.
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) to get the deal signed.
Almost certainly, most contract negotiators would prefer to read a somewhat-longer draft, consisting of short, understandable sentences and paragraphs, than to read a shorter draft that contains lots of dense, convoluted clauses.
So: The Way to draft a contract is to write as many short sentences and paragraphs — "sound bites," if you will — as are needed to cover the subject.
And if a sentence or paragraph starts to run long: Seriously consider breaking it up.
Even if the resulting draft happens to take up a few extra pages, your client likely will thank you for it.
30.3.7. White space is your friend
In the days of hard-copy paper contracts, lawyers typically used a "compressed" format for contracts — narrow margins, long paragraphs, small print — so as to fit on fewer physical pages. Readers tended to react negatively when they saw a document with "many" pages.
Those days are long gone. Nowadays, pretty much everyone reviews contract drafts on a screen. So larger print and more white space:
makes the draft easier to review and, if necessary, redline — and making the reviewer's job easier is always a nice professional courtesy that might just help to earn a bit of trust; and
makes it easier for the parties to discuss any points on which they disagree. In a Google search for the phrase "White space is your friend," the earliest use listed appears to have been Paul Sanderson, White Space is Your Friend (How To Cure Horror Vacui) (5thColor.Wordpress.com 2011).
30.3.8. Blaise Pascal's explanation: "If I'd had more time …."
Why do drafters persist in creating wall-of-words clauses? Especially when the benefits of short paragraphs are so, well, plain?
An obvious candidate is the classic explanation paraphrased in English as: "If I'd had more time, I'd have shortened this letter." That paraphrase is itself a simplification of Blaise Pascal's original, which has been translated as "The present letter is a very long one, simply because I had no leisure to make it shorter." Blaise Pascal, Lettre XVI, in Lettres provinciales, Letter XVI (Thomas M'Crie trans. 1866) (1656), available at https://tinyurl.com/PascalLetterXVI (WikiSource.org).
30.3.9. Spaghetti-clause history: A throwback to the days of dictation?
Long, dense, "spaghetti clauses" in contracts might well have come from law practice before desktop computers and word-processing software. When your author was a new lawyer:
An attorney would typically dictate contract language to a secretary; she (yes, she) would take down the lawyer's words on a steno pad, often using Pitman or Gregg shorthand. (Sometimes the attorney would use a tape recorder such as a Dictaphone and give the tape to the secretary.)
If the lawyer was struck by a new thought in mid-dictation, the lawyer might well say, "semicolon; provided, however, that …."
The secretary would type up the lawyer's dictation on a manual typewriter, possibly with "flimsies" (carbon-paper sets) to make additional copies.
Any editing of typed drafts was laborious. It was done with typewriter erasers and/or Wite-Out or Liquid Paper correction fluid. Only when necessary, entire pages would be retyped.
So it's easy to see how wall-of-words contract clauses came to be regarded as acceptable, even unavoidable. Likewise with the occasional "provided, however" interruption.
In the modern era, though, there's no excuse for drafting a contract without editing it to serve the reader as described above — and preferably, to write it mainly in that way to start with.
30.3.10. Caution: Is a L.O.A.D. trying to sneak in an unfavorable term?
A long paragraph of dense legalese raises the question: Was a Lazy Or Arrogant Drafter (30.5) secretly hoping to use the MEGO factor ("Mine Eyes Glaze Over") to sneak an objectionable term past the reader?
This actually happens sometimes. For example, in the estimable redline.net forum (for lawyers only, membership required), a lawyer recounted how:
The commenting lawyer recounted how an early client was a writer who was looking for an agent for representation in dealing 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 the agency would own whatever work product that the writer produced while the agency was representing the writer.
The commenting lawyer naturally advised the writer, "DO NOT SIGN."
30.3.11. Or is the L.O.A.D. just trying to look important?
Some lawyers might flatter themselves that by using dense legalese, they'll enhance their personal prestige as High Priests of the Profession, privvy to secret legal knowledge not revealed to ordinary mortals. That seems a dubious proposition at best — and indeed a risible one.
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 author's byline indicates that he is a U.S. Navy veteran.
(If we wanted to stay with the Pasta-Rule theme, see 30.3, we could call this "the Sauce Rule: Sauce goes on top." But BLUF takes less work to remember what it stands for, and a lot of people are already familiar with BLUF.)
To illustrate, here's another unfortunately-typical example of a spaghetti clause that's in serious need of clean-up; it's from the March 2022 merger agreement by which Hewlett-Packard (HP, Inc.) acquired well-known headset manufacturer Plantronics. Since Where's Waldo? is no longer "a thing," let's instead try playing a short game of, Where's the Action Verb?
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.
For an even worse example in the very next paragraph of that merger agreement, see the following footnote:
Let's rewrite subdivision (a) above, using the rules we've just discussed:
1. Short paragraphs;
2. Just one negotiation point per paragraph; and
3. 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:
SECTION 6.07 Indemnification and Insurance.
(a) See subdivision (c) below for definitions of particular capitalized terms. [Comment: Note the forward reference.]
(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 ….
Comment
The even-worse example is subdivision (b), which clocks in at 928 words (!), addressing 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.
30.4.2. A BLUF example in a contract
Before: Here's a contract provision that was litigated in a state court:
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, [here we finally get to the "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.
(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.)
One would hope there'd be no dispute about which of these versions is more readable.
30.4.3. A statutory BLUF example
As a statutory example, this rewrite, by law professor Mark Cooney, was retweeted by legal-writing guru Bryan Garner:
Before:
A person who engages in conduct proscribed under section 530 and who in the course of engaging in that conduct, possesses a dangerous weapon or an article used or fashioned in a manner to lead any person present to reasonably believe the article is a dangerous weapon, or who represents orally or otherwise that he or she is in possession of a dangerous weapon, is guilty of a felony punishable by imprisonment for life or for any term of years. If an aggravated assault or serious injury is inflicted by any person while violating this section, the person shall be sentenced to a minimum term of imprisonment of not less than 2 years.
So what exactly is the bottom line of this statutory provision?
BLUF rewrite by Prof. Cooney:
A person is guilty of a felony if, while committing a crime under section 530, he or she:
(1) possesses a dangerous weapon;
(2) possesses an article used as a dangerous weapon; … [etc.]
(Emphasis added.)
30.4.4. BLUF clauses are more memorable, too
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, namely "center-embedded clauses" — i.e., sentences and paragraphs where the action verb is buried in a spaghetti-clause (see 30.3) mass of verbiage. The researchers found that such clauses "inhibited recall to a 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).
30.5. Legalese: Only L.O.A.D.s love it
The modern trend is decidedly to use plain language in contracts, and also in just about any other kind of document you can imagine — even though it often takes more work to write plainly. See generally the references cited by an informal consortium of U.S. Government civil servants in Plain Language in the Legal Profession (PlainLanguage.gov, undated).
As we'll see later in examples: Readers loathe dense, "spaghetti clauses" (see 30.3), that is, walls of words in pompous legalese favored by Lazy and/or Arrogant Drafters (30.3.3). Having to read such text is like having to hack through a jungle with a machete.
• Clients prefer plain language in contracts because plain language speeds up legal review, which generally is one of the biggest bottlenecks in getting a deal to signature.
Example: The general counsel of a GE business unit reported that, when his group switched to plain-language contracts, the new contract forms "took a whopping 60% less time to negotiate than their previous legalese-laden versions did. … Customer feedback has been universally positive, and there hasn’t been a single customer dispute over the wording of a plain-language contract." Shawn Burton, The Case for Plain-Language Contracts, Harv. Bus. Rev. Jan.-Feb. 2018 at 134, archived at https://perma.cc/HW85-FGSA. When that article was published, Burton was the general counsel of GE Aviation’s Business & General Aviation and Integrated Systems businesses.
• Plain language makes it more likely that potential problems will be spotted and fixed before signature — which reduces the opportunities for future disputes that could waste the parties' time, opportunities, and money.
• 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.
Moreover, during jury deliberations, plain language can help refresh jurors' recollections as part of the "real" evidence in the record, not merely as 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.
• It's hard to educate or persuade a reader — two key missions of every contract drafter — when you write dense legalese. 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
• The trend toward plain language is by no means limited to purely-legal documents; contract drafters can take a leaf 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.
No siblings to write to? Borrow mine: Just begin with "Dear Doris and Bertie."
30.6. Balanced, two-way terms usually get signed sooner
The shortest path to signature — and the best plan for a producing a workable contract — is often to draft terms that your client wouldn't mind agreeing to if the parties were to switch sides.
If you're doing the drafting, you can help speed things up considerably by being reasonable in what you offer to the other side. That's because many business people greatly prefer to sign contracts that are reasonably balanced, because such contracts —
require less time-consuming legal negotiation; and
help to promote mutual trust between the parties' business people.
Your author learned this from experience: I used to be vice president and general counsel of BindView Corporation, a publicly-traded, network-security software company, based in Houston but with extensive international operations, until we were acquired by Symantec Corporation, the global leader in our field. As outside counsel, I'd helped BindView's founders to start the company.
As soon as I went in-house, I had to handle all our negotiations with customers about our standard contract form. That was a big time sink, both for me and for our sales people (who would sit in on negotiation calls).
To reduce the time we spent in such "legal" negotiations, in successive deals we gradually revised our standard contract form: We dramatically speeded up our deal flow by revising our contract form to proactively provide balanced legal terms that our customers typically asked for, in ways that we knew we could support.
In addition to helping us get to signature sooner, the (re)balanced contract form indirectly promoted our product in another way: Customers began to tell me how much they liked our contract, which validated their decision to do business with us.
I started making notes of customers’ favorable comments, and eventually quoted some of the comments (anonymously) on a cover page of our contract form. Here are just a few of those customer comments, which I posted online some years ago; all are from negotiation conference calls except as indicated:
– 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.
You might wonder whether BindView ever experienced legal- or business problems from having a balanced contract form. I’ll note only that:
With the CEO’s permission, I talked about our balanced-contract philosophy in continuing-legal-education ("CLE") seminars, and even included a copy of our standard form in written seminar materials; and
In due course we had a successful "exit" when we were approached and acquired by Symantec Corporation, one of the world’s largest software companies and the global leader in our field.
To be sure: Some business people just love to "win" as much as they can in every contract negotiation, often violating Wheaton's Law ("Don't be a d**k"). If that's you, please consider whether that approach best serves your (or your client's) long-term goals.
The W.I.D.A.C. Rule applies here: When in doubt, ask the client — and document that you raised the issue and what the client's decision was, for example in a quick confirming email to the client..
30.6.2. Rule of thumb: Don't ask for what you wouldn't agree to?
There's a useful rule of thumb when thinking about including a particular provision in a contract: Suppose that someday the parties' roles were ever to be reversed — which could happen (30.6.3) — and that you'd recommend that your client reject the provision. In that situation seriously consider omitting the provision.
As a contract drafter, you'd do well to follow the negative version of the Golden Rule attributed to the ancient Greek rhetorician Isocrates: Do not do to others that which angers you when they do it to you. Similarly, Jewish sage Hillel the Elder said, What is hateful to you, do not do to your fellow: this is the whole Torah; the rest is the explanation; go and learn. See Golden Rule (Wikipedia.org).
The flip side of that rule of thumb is also handy when thinking about leaving out a provision: If your client would likely insist on having the provision in the contract if the parties' roles were reversed, then think seriously about including the provision.
Here again: W.I.D.A.C. — When In Doubt, Ask the Client.
30.6.3. Balanced terms make role reversal easier
Agreements that would apply equally if the parties were to switch sides will generally be more balanced; to illustrate this principle, we'll use confidentiality agreements as an example.
In many cases, a two-way confidentiality agreement that protect's 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 — to be more balanced.
Your author saw this, too, as general counsel at BindView, where on a couple of occasions:
We were the customer, licensing another vendor's software for our internal use;
On each of those occasions, the other vendor's software license agreement would have required considerable revision and, presumably, negotiation, to make it workable for us, the customer;
So instead, I proposed to the vendor that we just use BindView's standard software license agreement — but with BindView as the customer instead of as the vendor;
Each time, the vendor reviewed our license agreement and quickly agreed to our proposal.
(This basic approach — of being reasonable — is analogous to the ancient "divide and choose" procedure, sometimes known as "I cut, you choose," by which children can evenly divide a cookie between them, often used in buy-sell agreements.)
30.6.4. Reduced danger if roles do get reversed
See the discussion at 30.7, especially the tale of how the Trump Organization switched roles from landlord to tenant under its own standard lease terms — and found itself at a significant disadvantage.
30.6.5. Example: A one-way NDA later leaves a party unprotected
With a one-way nondisclosure agreement, only the originally-intended disclosing party's information is protected. This means that any disclosures by the receiving party might be completely unprotected — resulting in the receiving party's losing its trade-secret rights in its information.
That's just what happened to the plaintiff in a Seventh Circuit case: The plaintiff signed a confidentiality agreement with the defendant, but that agreement protected only the defendant's information. Consequently, the plaintiff's later 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 defendant).
(For more about the dangers of unrestricted disclosures of confidential information, see 8.18.15.)
It's not hard to imagine the thought process that the plaintiff's business people's went through: "We need to disclose our information to you, but hey, we've already got an NDA in place, so sure, let's do it." But the NDA didn't do what the plaintiff needed.
30.6.6. Future delays and embarrassments can be avoided
A two-way confidentiality agreement might help avoid future drafter embarrassment: Suppose that Fred and Ginger agree to a confidentiality provision that protects only Ginger's information. Also suppose that the confidentiality provision was strongly biased in favor of Ginger, who is currently the discloser.
But now suppose that, at a later date, Fred and Ginger decided that they also needed to protect Fred's confidential information as well, so that Fred can disclose it to Ginger. In that case, with the shoe on the other foot, Ginger as receiving party might not want to live with the obligations that she previously made Fred accept when she was the disclosing party.
As a result, Ginger might find herself in a doubly-embarrassing position:
Ginger would be asking Fred to review and agree to a new confidentiality provision — and having to explain to Fred why Ginger wasn't willing to live with the same procedure that she had earlier pressed upon Fred.
Moreover: Ginger might turn to (or on) her original drafter and ask, Why didn't you do this the right way in the first place, instead of wasting everybody's time?
So: It's often a good idea to insist that any confidentiality provision be two-way in their effect from the start, protecting the confidential information of both parties.
30.6.7. Caution: a two-way agreement can still 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:
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.
Ginger, as Discloser, would therefore have to review the confidentiality provisions carefully to make sure it contained sufficient protection for her Confidential Information.
Conversely, if Ginger's drafter is doing the drafting, knowing that she'll be 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.
30.6.8. A one-way clause could be thrown back at you in negotiation
Consider this not-so-hypothetical example: You're helping to negotiate a contract between your client, Ginger, and another party, Fred. Your draft contract is a tough one; among other things, it contains an exclusive-jurisdiction forum clause (see 3.6) that requires all litigation to be conducted in Ginger's home-court jurisdiction.
In negotiating the contract, Fred's counsel says, sure, an exclusive-jurisdiction clause is fine with us — BUT the exclusive jurisdiction has to be our home court, not yours.
If Fred has more bargaining power than your client Ginger, your proposal of a tough first-draft contract might have "boomeranged" to create problems for your own client, by requiring any litigation to take place in a city that she might not want.
(This is an example of "poking the bear"; see 30.12.)
Exactly this once happened to one of your author's past clients:
In a negotiation of a big commercial deal, the client had forwarded its standard form contract — which I hadn't written — to a prospective customer that had significantly-more bargaining power than my client did.
The client's standard form contract included a forum-selection provision requiring all litigation to take place exclusively in the client's home city.
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.
That wouldn't have been good for my client, because litigating in the other city 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 — not realizing that this was a win for my client:
Without a forum-selection stipulation, the customer likely would not have been able to sue my client in the customer's home city at all, because the courts in that city would almost certainly not have had personal jurisdiction over my client. (Of course, that wouldn't have stopped the customer from filing suit anyway, which would have meant that my client would have to spend money to get the case dismissed or transferred.)
In contrast, my client would have been able to sue the customer in my client's home city, because the customer had significant operations in that city.
The customer's lawyer apparently didn't tumble to the fact that he was making a potentially-big concession.
30.7. Boomerang clauses could hurt you later
Contract drafters will often do well to heed advice similar to that of the Kingston Trio's (somewhat-offensive) 1958 version of the risqué Spanish-language song Coplas, where Dave Guard's "translation" of one verse is, Tell your parents not to muddy the water around us — they may have to drink it soon. A contract drafter's client might someday have to live with the hardball provision that the drafter forces the other side to accept.
30.7.1. The Trump Organization gets hoist by its own petard
Example: Trump Corporation ("Trump") has been a real-estate landlord, among other things. (Author's note: I wrote this section before Donald Trump announced his successful 2016 presidential campaign.)
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."
For the opposite story, see 30.6.3 about how your author's former company successfully used its own standard contract for a transaction in which we were the customer, not the supplier.
30.7.2. Example: Tilly's sets the signature bar too high
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. 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.
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. BUT: The signed acknowledgement didn't contain the three executive signatures needed to modify the 2001 employment agreement.
So: Because Tilly's set the so bar high for modifying the 2001 employment agreement — requiring three executive signatures — the company found itself facing high-stakes litigation by a class of plaintiffs, whereas it had thought it would be arbitrating low-stakes claims individually. 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).
30.8. Roadblock 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.
The inadvertent drafting of ambiguous terms is an occupational hazard for contract drafters. You'll definitely want to stay alert to the possibility that you might be creating such terms.
A contract term is ambiguous if it is susceptible to two or more plausible interpretations that can't be resolved by the usual tools of interpretation (known as "construction").
30.9.2. Why is ambiguity 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 is not ambiguous.
Example: In one Texas case, 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 Clause 7.3, 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 a Fifth Circuit case, 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 parties hotly contested that meaning (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, versus losing on summary judgment without ever getting a shot at persuading a jury. But for the drydock owner, not having to go to trial was most assuredly a win in its own right.
30.9.3. How do courts deal with (possible) ambiguity?
Court generally use a two-step process in dealing with potentially-ambiguous contracct terms?
1. The judge might be able to use standard legal rules of interpretation to decide the case quickly, e.g., on a motion to dismiss on the pleadings or a motion for summary judgment (see 17.6.2).
2. But if applying those rules doesn't resolve the dispute, then the term in question is indeed ambiguous. When that happens, (in the U.S.) the court is not allowed to grant a quick summary judgment on undisputed facts — instead, the court must conduct a trial (if they're lucky, a trial on just that one issue), so that the trier of fact (a jury, or perhaps the judge) can find facts as needed to determine the parties' intent concerning the disputed provision.
30.9.4. Does disagreement automatically result in ambiguity?
30.9.5. 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 your author's 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."
A New York City judge notes: "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).
30.9.6. What's the best way to spot ambiguities in your drafts?
Two main possibilities, and maybe a third:
Ideally: Have someone else review your draft with fresh eyes.
Or: Put the draft aside for awhile and re-read it later; chances are that you'll spot something you didn't before.
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 — butyou'll want to be very careful not to reveal client confidential 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.)
30.9.7. The A.T.A.R.I. Rule: Avoid the Argument: Rewrite It — Usually
Answer: Because there are (rare) times when you might not want to fix an ambiguity, as discussed in more detail at 30.9.9.
30.9.8. 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!.
30.9.9.But: Strategically, an ambiguity might be better left in place
The A.T.A.R.I. Rule (9.7) and W.I.D.D. are great rules of thumb — but neither 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 (8.22), a court might resolve the question in favor of the other side because your side was responsible for the ambiguity.
• What if the other side drafted the potentially-ambiguous language? If the other side drafted the language in question, then you might not want to say anything about it, in the hope that contra proferentem (8.22) 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" (30.12) — 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 30.12 for examples.)
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 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 22.1 for more on this.)
30.9.10.Vagueness is a type of potential ambiguity – fix it?
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, in Houston in August a mid-day temperature of 80ºF would be regarded as (comparatively) cool, whereas in Point Barrow, Alaska, the same temperature at that time would likely be thought of as a real scorcher.
(Of course, as any parent in an English-speaking family knows, the word cool could also be ambiguous — in the sense of having multiple possible meanings — in addition to being vague.)
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 is potentially ambiguous, in that conceivably it could 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.
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.
But:Too-vague a term might lead to an agreement being held unenforceable. Example: 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).
So here's a rule of thumb: Vagueness is not 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.
30.9.11. What if The Other Side balks at fixing ambiguities?
It's been known to happen that, during contract negotiations, Party A asks to rewrite an ambiguity, but Party 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 Party A meekly accept Party B's assertion? Very possibly not:
In a dispute, Party B's lawyers will argue — often shamelessly — for whatever interpretation seems good to them at the time, regardless of what was previously said by Party B.
Party A will be reluctant to risk having a court hold that, by not insisting on clarifying the ambiguity, Party A waived its own preferred interpretation of the language.
On the other hand: Party B might be stuck with its prior assertion to Party A, on estoppel grounds or analogously to contra proferentem (see 8.22).
This will ultimately come down to how Party A's business people judge the overall business risk.
30.9.12. 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).
30.9.13. Exercise: A (hypothetical) date-related ambiguity
Here's a simple example of a potential ambiguity: Suppose that our hypothetical client MathWhiz ([BROKEN LINK: hypo-facts]) 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?
This illustrates a useful drafting principle: W.I.D.D. – When In Doubt, Define! (30.9.8)
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.
QUESTION: How would you rewrite the "Tenant will vacate the Premises no later than 12 midnight on December 15 …." sentence to resolve this ambiguity?
30.10. Examples, sample calculations, and footnotes
30.10.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.)
Day refers to a calendar day, as opposed to a business day.
A period of X days:
begins on the specified date, and
ends at exactly 12 midnight (see subdivision d concerning time zones) at the end of the day on the date X days later.
Example: Suppose that a five-day period begins on January 1 — that period ends at exactly 12 midnight at the end of January 6.
For purposes of subdivision b, the term 12 midnight refers:
to local time if only one time zone is relevant,
otherwise, to the latest occurrence of 12 midnight on the date in question.
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 14.4.)
In one litigated 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.
30.10.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.
Moreover, you've doubtless seen examples in well-written user manuals.
30.10.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 7.19.
(Alternatively, an example could be put in a footnote, as discussed at 30.10.)
Example: In BKCAP (2009), 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).
30.11. 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.
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. (Your author 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. )
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 that 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.
… 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.40
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.
Comment
30.12.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 8.4.14 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.
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 a 2022 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.
30.14. 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).
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.
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, No. 2021-0173, slip op. at 22 (Del. Jul. 19, 2023).
30.14.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 8.2.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.
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.
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) ….
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
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. …
Similar language can be found in section 30 (independent contractors) and section 37 (waivers) of the same Honeywell purchase-order form.
30.15. 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.
30.15.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 8.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).
30.15.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 8.19.12.1).
30.15.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 8.35 for more details and suggestions for dealing with these problems.)
30.15.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 Contract, see 24.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 17.4.2 for more discussion of this problem.)
These examples illustrate the R.O.O.M. Principle — Root Out Opportunities for Mistakes (or Misunderstandings).
30.16. 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.
30.16.1. Exercises and discussion questions
30.16.1.1. Basic questions
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?
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?
True or false: Contract drafters should avoid including explanations of particular terms. EXPLAIN.
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?
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?
What are the two essential components of a contract drafter's mission?
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.
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.
In the context of contract drafting, what's a "L.O.A.D."?
What's one of the most important ways of avoiding being a L.O.A.D.?
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.
What does BLUF mean?
What's "the MEGO factor"?
Name two advantages of putting a contract's key business details into a schedule, perhaps at the front of the contract.
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.)
Why state that the Lease is entered into "as of July 25, 2007"?
Why do you think the names of the parties are capitalized?
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?
To what extent is the "Each item in this Article 1 incorporates …" worth including?
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 29.6.)
Any comments about the way the "Term: Five (5) years" portion is stated? How about the way that the Base Rent amounts are stated?
30.17. Hamburger for the guard dog can help get signed sooner
When drafting a contract, 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 an intellectual-property license agreement, or perhaps a real-estate lease.
It might be tempting to omit an audit clause from your draft. (Concerning audit clauses, see 2.3.) Your reasoning could be that The Other Side's contract reviewers might not think to ask for an audit clause, and it's not your job to remind them — which is certainly true.
But consider these points:
• It might be wishful thinking to imagine that The Other Side's contract reviewer won't notice the absence of an audit clause — The Other Side's reviewer might be an expert who knows exactly what to look for and what to demand.
• Suppose that The Other Side'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 can live with — and then, if The Other Side makes unreasonable change requests, you can try standing on principle to reject the requests. (See also 20.2 for when you just can't say no to an unreasonable request.)
• Finally, suppose The Other Side really doesn'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 Other Side's "legitimate needs and greeds" in a reasonable way along with as your client's needs. BUT: Don't go overboard with this; to repeat, it's not your job to propose provisions that could disadvantage your client and that The Other Side didn't ask for.
30.18. Task: Reminding the parties — and persuading them?
That view would be fine — if it weren't for a few inconvenient facts:
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.)
People can forget (sometimes "conveniently") what was agreed to before. Worse: Memories can sometimes be "creative" when individuals' personal incentives — which often are hidden — are involved (31.4). And that in turn means that sometimes people have to be reminded of what the contracting parties agreed to.
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.
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.
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.
30.18.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 7.27.2, possibly stated in footnotes, see 14.4, 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.
30.18.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 Party A must take Action X, and Party 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! (22.1).
30.19. Perfect is the enemy of good enough - but …
When it comes to contracts, clients are firm believers that "perfect" is the enemy of "good enough." 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 for lawyers, 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?
30.20. Bright-line standards for significant triggers
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.
30.20.1. Contract "executed" — does that mean "performed"?"
It's better to refer to the contract's being "signed" instead of "executed," because the latter could be interpreted as the contract's being performed by the parties. Example: This happened in a Delaware case. 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).
30.20.2. Is a sale "consummated" upon signature, or performance ?
Example: 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).
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.
30.20.3. Be clear that a right or obligation does or doesn't end
Example: 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 expired. But the trial court and appellate court disagreed:
{¶ 5} … The purchase option provided that "[t]he Option to Purchase period commences on December 1, 2019 and expires on December 1, 2021 11:59 PM with the option to purchase at any time within."
The agreement included the following "notice" provision: "To exercise the Option to Purchase, the Lessee must deliver to the Landlord written notice of Lessee's intent to purchase. In addition, the written notice must specify a valid closing date. The closing date must occur before the original expiration date of the Lease Agreement.
If notice of intent to purchase is not provided by June 1, 2021, [then] Landlord has the right to list the house for sale and make showings available to prospective buyers."
Finally, the agreement reiterated that "[n]otice to purchase needs to be initiated by June 1, 2021. Timing is of the essence in this Option to Purchase Agreement."
* * *
{¶ 16} Although the agreement also stated that notice needed to be "initiated" by June 1, 2021, a failure to meet that deadline did not nullify the option, which, again, could be exercised "at any time" up to December 1, 2021. Rather, the contract identified specific consequences for failing to give notice by June 1, 2021. It provided that "[i]f notice of intent to purchase is not provided by June 1, 2021, Landlord has the right to list the house for sale and make showings available to prospective buyers." …
In other words, if the plaintiffs failed to give written notice of exercising the option by June 1, 2021, [then] the defendants were entitled to begin making alternative plans by listing and showing the house to obtain back-up offers.
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.
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.
30.20.4. 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 Clause 6.4; 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).
31. Appendix: Business planning for contract drafters
[Note to the author's law students: You can just skim this section; 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.
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").
31.1. Introduction: "Learn the business" – but how?
One of the big complaints clients have about lawyers is that "they just don't understand the business." But it's singularly unhelpful to just say to a lawyer: Hey, you: Learn the business! The beneficiary of such advice might not know what to do to make that happen.
Neither is it particularly useful to add, Just ask questions! It might not be obvious what questions should be asked.
So, this 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.
31.2. Stephen Colbert proves the benefits of thinking ahead
Years ago, 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.
31.3. Hope is not a plan — or, 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). Photo: Bed Bath & Beyond.
31.4. Incentives (the personal kind) can matter. A lot.
Berkshire Hathaway's vice-chairman Charles Munger has said that "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.%3C/cite%3E
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.
31.5. T O P S P I N: 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:
• 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; Political issues can raise their heads; for example, in 2019, convention organizers attracted attention for inserting "morals clauses" into their contracts: "Organizations will not bring events to Texas if [anti-LGBTQ] discriminatory bills become law, and most convention contracts allow organizers to cancel if such laws take effect." Chris Tomlinson, Bigot bills would damage Texas economy, Houston Chronicle, April 3, 2019, page B1, at B7 col. 2 (emphasis added).
• N: Nature, which can cause all kinds of threats and opportunities to arise in a contract relationship.
31.6. 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: Immediateaction, e.g., to mitigate the threat or to seize the opportunity.
• A: Additionalactions, 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.
31.7. 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).
31.8. 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.)
31.9. Finally, ask the investigator's all-round favorite question
When your author 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 ….)
31.10. Learn the business! – but how, exactly?
Clients want their contracts to help them get stuff done, quickly and economically. Clients want their contract drafters to understand how stuff gets done; a frequent client complaint about lawyers is that "they just don't understand the business."
But it's not helpful to just say to a law student or junior lawyer: Hey, you: Learn the business!
• The beneficiary of such advice might not know what to do to make that happen.
In the '90s, your author was an assistant coach for my son's Little League teams. I'd sometimes hear a mom in the bleachers shouting "Be a hitter, Johnny!" when her little boy came up to bat. (Oh, and it was pretty much always moms doing this, not dads. We did have one or two girls on my son's Little League teams over the years.)
But "be a hitter!" isn't helpful 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.
Telling a law student or new lawyer "learn the business!" is much the same.
• By the way: Neither does it help to add, Just ask questions! It might not be at all obvious what questions to ask.
This book will help you to learn the business: both your client's business and your business of drafting and helping to negotiate contracts.
32. Appendix: Reviewing & revising a draft contract
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.
32.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.
32.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"
32.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).
32.4. Redline your changes
Always use "Track Changes" in Microsoft Word (or whatever word processor you use). See 6.10 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:
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.
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.
Ginger emails her (revised) Version 2 to Fred.
Fred repeats what Ginger did to create a new Version 3 and emails Version 3 to Ginger.
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 6.10).
32.5. 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 10.2 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.
32.6. But do break up "spaghetti clause" provisions
Another party's draft is likely to have long spaghetti clauses (30.3). That might be accidental — or perhaps not.
So, break up the spaghetti clauses:
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").
32.6.1. Expand single-spaced paragraphs
After you save a new Word document (see above), use 1.5 spacing for 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 30.3.
32.6.2. 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?)
I've 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.
32.7. 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.
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 20.1. (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 bar30.15 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 be gracious. Graciousness is a useful signal to the vendor that MathWhiz might well be a Good Business Partner. 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 29.5 for more on this subject.)
32.8. 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:
Email storage space is cheap.
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.
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.
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.
32.9. 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.)
[See your author's 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.
[ x ] 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 19.2.)
But: Be careful not to let sloppy passive-voice drafting become a harmful false imperative (29.14).
Author's note: 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).
Comment
Sources for active-voice note: See: • the U.S. Securities and Exchange Commission’s Plain English Handbook (Aug. 1998) at https://goo.gl/DZaFyT (sec.gov); • the PlainLanguage.gov Web site at https://goo.gl/FcvL (PlainLanguage.gov), by "a group of federal employees from many different agencies and specialties who support the use of clear communication in government writing"; • the U.S. Air Force’s writing guide, The Tongue and Quill (rev. Nov. 2015), at https://goo.gl/1y1b0j (static.e-publishing.af.mil).
Comment
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 your author 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.C.D.C. 1967) (again denying declaratory judgment to publisher), on remand from369 U.S. 111 (1962), reversing and remanding (on case-or-controversy grounds) 284 F.2d 262 (D.C. Cir. 1960) (Rickover's speeches had lost their copyrights due to unrestricted publication), reversing177 F. Supp. 601 (D.C.D.C. 1959) (denying declaratory judgment to publisher because Rickover held copyrights).
33.2. Hereunder
Example:
… a party's failure to comply with its obligations hereunder ….
… a party's failure to comply with its obligations under this Agreement ….
33.3. Lists - include them?
Maybe not: Could you just say "all," instead? (7.4)
33.4. 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:
[ x ] The police officer:
(a) told us to observe the speed limit; and
(b) asked us to dim our lights.
Much better.
33.5. 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.
[ x ] 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.
33.6. 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.
[ x ] 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, perhaps with "romanettes" (lower-case Roman numerals in parentheses), thusly:
[ x ] 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.
33.7. 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]
[ x ] 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]
33.8. 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:
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.
i) (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)athat years's Earn-Out Payment to Seller.
33.9. Numbers Rule
These are style rules, not hard-and-fast requirements
33.9.1. Style Rule 1: Follow your supervisor's style preferences
Caution: Many of the rule in this chapter are stylistic conventions —
If your supervisor (e.g., law-firm partner) prefers one way over another, then do it that way.
Don't make purely-stylistic revisions in another party's draft contract, for reasons discussed at 32.
33.9.2. Style Rule 2: 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 20.1). 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.
BEFORE: 42 was Douglas Adams’s answer to The Ultimate Question of Life, the Universe, and Everything.
AFTER: According to the late novelist Douglas Adams, the answer to The Ultimate Question of Life, the Universe, and Everything is … 42.
33.9.3. 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.
[ x ] 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:]
[ x ] Approximately 90% of baseball salary disputes are resolved by settlement due to the arbitration process without having to actually go to arbitration.
33.9.4. Exception: Numbers in payment terms
Use digits for payment terms, e.g., "net 10 days" or "net 5 days" (see 20.1).
Examples:
[ ] Payment is due net ten days.
[ x ] Payment is due net 10 days.
33.9.5. 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.
33.9.6. Exception: Numbers in clock time
Time is written with digits: 5:00 p.m. not five p.m.
33.9.7. Style Rule 3: Million, billion, trillion – 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.
33.9.8. Style Rule 4: 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 29.6.)
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.
33.10. Paragraph-Numbering Rule (for drafters)
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.)
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 …."
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).
33.11. Term-Label Drafting Rule
Put the term label in bold-faced type and quotation marks (and possibly parentheses).
Examples:
[ ] This Agreement is between MathWhiz LLC ("MathWhiz") ….
[ x ] This Agreement is between MathWhiz LLC ("MathWhiz") ….
[ ] The term "Affiliate" refers to ….
[ x ] 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.
[ x ] 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.
33.12. "They" Drafting Rule (for drafters)
In contracts, don't use "they" as a gender-neutral singular pronoun — if necessary, repeat the noun in question.
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.
[ x ] The Party seeking to terminate this Agreement under this Section must show that the Party used best efforts to remove the Blocking Order.
34. Georgetown ILI course "scripts" [in progress]
Course material: Common Draft (DCT's course materials): An extensively-annotated library of pragmatic, balanced, "two-way" model contract clauses — written in plain English, with a minimum of "legalese."
(Any other written materials will be made available.)
DCT to attenders: Much of this course will be very interactive; we are hoping for active participation from each of you.
Please feel free to ask questions throughout, instead of waiting until the end. You're welcome to:
unmute your microphone and ask; or
type your question into the Zoom chat — either to the whole group or to just D.C. or Hernando.
EXERCISE FOR ATTENDERS (Hernando to kick off): To make sure everyone is comfortable with the Zoom features we'll be using, please find the following Zoom controls on your computer:
The "raise hand" feature — and then please "raise your hand"
The "chat" feature — and then please type a message, either to the whole group or just to D.C. or Hernando.
34.1.2. Introductions: First group (DCT to kick off)
First group: Please unmute your microphones, turn on your cameras (optional), and briefly tell us:
Name;
Law firm or company;
Practice area and types of contracts you typically work with;
A specific current need related to international contracts; and
A very-brief summary of what you hope to get from this course. (We can't promise that everyone will get what they want, but we will try to get as close as we can.)
EXERCISE FOR PARTICIPANTS (Hernando to kick off): In the Zoom chat, please type a very-brief summary of what you think is meant by the word "triage" in this context.
Reading: See World Commerce & Contracting's Most Negotiated Terms 2024 study (a biennial series). WorldCC is the successor organization to the International Association for Contract and Commercial Management, or "IACCM." For some years now, DCT has been an IACCM/WorldCC member and an occasional speaker at its conferences.
Here are the top 10 most-negotiated terms overall, according to the WorldCC 2024 study — ranked alphabetically:
The report includes separate summaries for big business and small- to medium-sized enterprises ("SMEs"). The report defines SME as businesses with less than USD $1B in annual revenue.
QUESTION: In the Zoom breakout rooms:
Please see if you can come to a consensus about the "top three" terms from the above list.
Designate a spokesperson to "report out" to the class as a whole when we return from the breakout rooms.
34.1.4. Introductions: Second group (DCT to kick off)
Next group: Please unmute your microphones, turn on your cameras (optional), and briefly tell us:
Name;
Law firm or company;
Practice area and types of contracts you typically work with;
A specific current need related to international contracts; and
A very-brief summary of what you hope to get from this course. (We can't promise that everyone will get what they want, but we will try to get as close as we can.)
34.1.5. Quick review in breakout rooms: International v. domestic contracts (Hernando to kick off)
In your Zoom breakout rooms:
Please see if you can come up with a consensus of one or two key differences between international contracts and domestic ones.
Please discuss: To what extent do you think most Chinese contract lawyers are familiar with:
The U.N. Convention on Contracts for the International Sale of Goods ("CISG"); and
Designate a spokesperson — preferably a different one than last time — to "report out" about your discussion.
34.1.6. Introductions: Third group (DCT to kick off)
Next group: Please unmute your microphones, turn on your cameras (optional), and briefly tell us:
Name;
Law firm or company;
Practice area and types of contracts you typically work with;
A specific current need related to international contracts; and
A very-brief summary of what you hope to get from this course. (We can't promise that everyone will get what they want, but we will try to get as close as we can.)
34.1.7. Review: Contract shapes and sizes (DCT, Hernando)
EXERCISE FOR PARTICIPANTS (DCT to kick off): In the Zoom chat, please type a one- or two-word label for some "styles" of contract you've seen used, other than conventional, full-blown formal documents.
HERNANDO TO ASK DCT: To what extent can a "contract" be something other than a full-blown formal document? (28)
HERNANDO TO ASK DCT: What might happen if the parties carried out a transaction but they never signed any kind of written contract per se?
34.1.8. Introductions: Fourth group (DCT to kick off)
Next group: Please unmute your microphones, turn on your cameras (optional), and briefly tell us:
Name;
Law firm or company;
Practice area and types of contracts you typically work with;
A specific current need related to international contracts; and
A very-brief summary of what you hope to get from this course. (We can't promise that everyone will get what they want, but we will try to get as close as we can.)
34.1.9. General strategic drafting principles (DCT)
HERNANDO TO ASK DCT: Can you suggest any general ideas for getting resilient contracts to signature sooner? (30)
DCT to address:
The importance of a reader-oriented mindset (30.1)
Serve your readers — help them to do their jobs (30.1.1)
The Pasta Rule: Draft "macaroni clauses," not "spaghetti" (30.3).
DCT: The client's likely goal is to get an "OK" deal signed now (30.1.3). And "perfect is the enemy of good enough."
HERNANDO TO ASK ATTENDERS: Please use the Zoom "raise hand" feature: How many of you have seen (or written) "spaghetti clauses"?
HERNANDO TO ASK ATTENDERS: Please use the Zoom "raise hand" feature: How many of you have ever had an impatient client who wanted to know: "When will you be finished drafting my contract?" Or if you're reviewing another party's draft: "When will we be able to get back to The Other Side?
Contract review can be a big bottleneck (30.1.4). That's where the Pasta Rule and BLUF Rule can be a big help.
Draft something the other side could sign quickly? (30.2)
34.1.10. Questions to ask new clients to help identify key "what if?" contract issues (DCT)
BREAKOUT ROOM QUESTION for attenders: What do you do (or what have you seen others do) to start to learn a new client's business, or a new business of an existing client?
34.1.11. Preview: Next time + attender feedback
1. See 34.2 just below for what we'll be doing next time.
BREAKOUT ROOM QUESTION: From what you've seen so far, what's your initial impression of how this course will meet your needs? What might you hope to see done differently? (Again: We can't promise anything, but we want to serve attenders' needs.)
34.2. Day 2: Apr. 10: Choosing forms & begin review (Hernando, DCT)
Many thanks for the feedback received. Here are a few points:
Career Experience Sharing: There is an interest in hearing more about the instructors' career experiences. QUESTION for attenders: Can someone please explain what's meant here?
More Detailed Explanation of Contract Clauses: Some participants are looking forward to more detailed explanations of contract clauses. RESPONSE: Definitely.
Common Disputes and Practical Techniques: Participants hope to learn more about the key points that foreign lawyers consider when reviewing contracts from the perspective of common disputes, along with methods and techniques for revising contracts. RESPONSE: Definitely; we'll be doing that as we go along.
34.2.2. Governing law / enforcement (DCT, Hernando)
HERNANDO TO ASK DCT: To what extent will U.S. courts enforce a choice-of-law provision in a contract?
HERNANDO TO ASK ATTENDERS: In the Zoom chat: When you draft contracts for the sale of goods across international borders, do you typically exclude application of the UN Convention on Contracts for the International Sale of Goods ("CISG")? Why or why not? 3.7.12
HERNANDO TO ASK DCT: Where do the INCOTERMS (17.2) fit in here?
34.2.3. Sources of good forms (DCT)
HERNANDO TO ASK DCT: Where do you find good contract forms?
Ambiguity in contracts is a leading cause of dispute between contracting parties. (See 30.9.)
EXAMPLE: From here: "When filling out a job application, I saw they had a section for 'previous life experience', so I wrote down that I was a Pharoah in 2300 B.C."
34.3.2. Payment terms: Breakout room questions
We're going to open up the breakout rooms.
When you get to your breakout room, please briefly introduce yourself (unless everyone in your room already knows everyone else).
Please designate a spokesperson for each of the questions below. (It doesn't matter whether it's the same spokesperson for all questions.)
Please discuss the following questions — think about what you've encountered in your own work.
Perhaps your company or your clients typically do things a certain way.
Perhaps, in contract negotiations, you've seen other parties typically do things in a certain way.
Please feel free to click on the links to specific sections of this Clause ("real-time reading").
QUESTION 1: From what you typically see in your work: When a Biller issues an invoice to a Payer, when does the "countdown clock" for the payment deadline start? (2.14)
on the date that the Payer receives the Biller's invoice?
on the date that's "printed" on the invoice?
something else?
QUESTION 2: From what you typically see in your work: When a Biller issues an invoice to a Payer, how long does the Payer have to pay?
Net 30 days, that is, payment in full in 30 days? (20.1)
Net 45 days?
Net 60 days?
Net 90?
Net 120?
Something else?
For an example of a large customer (Honeywell) that stretches its payment terms even more, see 2.12.6.10:
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.
QUESTION 3: From what you typically see in your work: How do parties handle disputes about whether an invoice is correct? (See section 2.14.6 of Clause 2.14.)
QUESTION 4: From what you see in your work: Do parties typically specify a procedure for handling payment set-offs? Or are set-offs typically handled on an "ad hoc" basis, that is, "if the issue ever comes up, we'll figure it out then"? (See section [BROKEN LINK: pmt-off] of Clause 2.14.)
QUESTION 5: From what you typically see in your work, do purchase agreements often include audit provisions allowing the customer to audit the supplier? (See 2.3.)
Please come back to the main Zoom room when you're finished.
34.3.3. Liability: Representations and warranties
DCT to talk about the difference between a representation (defined at 3.15) and a warranty (see the notes at 3.18).
Real-time reading: 3.17 (basics of reps and warranties), especially the discussion of the "Hill of Proof" at 3.17.2.
Strategy:
A buyer will usually want a seller to provide both a representation and a warranty.
A seller will want to think about whether to provide just one or the other. (See 3.17.3.)
34.3.4. Liability: "Implied" warranties
DCT to discuss disclaiming implied warranties, conditions, and terms of quality. (See 3.8.)
Carve-out (exception) to the disclaimer for the implied warranty of title to goods (i.e., "I'm not selling you stolen goods")
Real-time reading as needed: Indemnities (3.9) and defense obligations (3.4)
Important points:
Liability for indemnity might not be limited to "foreseeable" harm.
In some jurisdictions, an indemnity obligation might implicitly include an obligation to defend against third-party claims.
Always think about insurance coverage for indemnity obligations — whether you're the indemnifying party or the party that would be indemnified. (Mnemonic: "I&I" – insurance and indemnity; see 3.10.)
QUESTION for Kiran: How have you seen parties choose a forum?
To what extent have you seen it be important to the parties to choose their own "home field" (home pitch, home court)?
Would it complicate matters to choose a third forum? E.g., the parties are in the U.S. and China but choose to litigate in Singapore or London?
What if activities under the contract (or investment) would be mainly in a third jurisdiction, where the local law is not familiar to either party to the contract?
QUESTION FOR DCT: To what extent should the choice of forum and the choice of law be considered together as connected issues? Why?
Example: If New York courts are selected as forum, New York law might best suit the contract, because the judge would be most comfortable/familiar with NY law.
Problem of proof: If the agreed law is something other than the law of the agreed forum, then one or another party might have to prove what the agreed law says — in the U.S., this would require "expert testimony."
34.4.4. Instructor discussion: Courts vs. arbitration
QUESTION FOR DCT: Is arbitration really cheaper than litigation? (8.2.13)
QUESTION FOR KIRAN: What features of an arbitral institution are worth considering?
Support provided by the secretariat of the arbitral institution
Costs and filing fees - some arbitral institutions calculate fees based upon amount in dispute, procedural rules of the institution and whether they cover special circumstances such as evidentiary procedures/discovery
QUESTION FOR DCT: Should the evidentiary requirements/procedures (e.g. US style discovery) play into the choice of a particular court or other jurisdiction as the venue/forum for the dispute?
QUESTION FOR KIRAN: Are there any special circumstances that Chinese parties might want to consider?
In 2019 a special law went into effect allowing for the enforcement of interim measures issues by Hong Kong Courts to be enforced in Mainland China. This has given Western parties more comfort in arbitrating disputes in Hong Kong with Chinese counterparties
Chinese Arbitration Law is going through a revision process. Article 16 of the Chinese Arbitration Law continues to specifically only recognize arbitration under the auspices of recognized arbitral institutions. Ad hoc arbitration is not permitted. CIETAC is one of the biggest and most frequently used institutions.
34.4.5. Breakout room: Preference for arbitration or for litigation?
Please discuss the following and, as before, choose a spokesperson to "report out."
QUESTION 1: In your experience (personal or what you've seen): When negotiating transnational contracts, do companies tend to prefer arbitration, or litigation?
QUESTION 2: Do companies tend to specify a city or country for arbitration? Some examples:
Choice of arbitrators - what are the best features?
34.4.7. Breakout room discussion: Finding qualified local counsel in negotiations
Questions for breakout rooms: In your experience (personal or what you've seen): When negotiating transnational contracts:
How often do companies engage local counsel?
How do companies typically find local counsel?
What qualifications do companies look for in local counsel?
To what extent are companies concerned about the possibility that a prospective local counsel might have a conflict of interest — especially local counsel at a large law firm?
To what extent are companies willing to discuss waiving conflicts of interest for prospective local counsel?
Please choose a spokesperson to "report out" when we return to the main Zoom call.
34.4.8. Breakout room discussion: Early arbitration choices
Questions for breakout rooms: In your experience (personal or what you've seen): When negotiating transnational contracts:
What "arbitration institutions" do companies tend to agree on for administering an arbitration? (8.2.18)
Is confidentiality in arbitration important to the parties? (If so, it should preferably be expressly discussed at the outset.) (8.2.7)
Similar discussions might be needed for data protection and cybersecurity during arbitral proceedings.
Should arbitration hearings be conducted in person, virtual, or hybrid?
Do companies often agree to just have the arbitrator administer the arbitration? (8.2.19)
What do companies end up agreeing to as the "seat" (official location) of an arbitration? (8.2.22)
What are some key milestones to consider and include in the procedural timetable of the case? How long should resolution take?
34.4.9. Selected legal materials
(Thanks to Kira for providing these links.)
Arrangement Concerning Mutual Assistance in Court-ordered Interim Measures in Aid of Arbitral Proceedings by the Courts of the Mainland and the Hong Kong Special Administrative Region (the “Arrangement”) came into force on 1 October 2019 and applies to applications for interim measures made under the Arrangement on or after that date.
Question for breakout rooms: In your experience (either personal, or what you've seen): When negotiating a confidentiality agreement, what issues are generally of the most concern to the parties and their lawyers?
As usual:
Please designate a spokesperson to "report out"
Please return to the main Zoom room when you're finished with this discussion.
34.5.3. Confidentiality agreements / NDAs (DCT)
Confidentiality agreements a.k.a. "NDAs" (a misnomer): 8.18
Reference: Some key Common Draft NDA provisions:
Two-way protection, BUT: The Recipient must consent to receive information in confidence — otherwise, the Recipient will not be bound by confidentiality obligations
reasonably recognizable as likely to be confidential; or
in the Discloser's own internal files.
No expiration of confidentiality obligations for timely-designated trade secrets
Tell employees about their affirmative disclosure rights under (federal) Defend Trade Secrets Act
Procedure for responding to subpoenas, search warrants, etc. — IMPORTANT: Just because Confidential Information is subject to a subpoena, that should not completely exclude the information from protectability.
QUESTION 1: What's the difference between an assignment of IP versus a license of the same IP?
QUESTION 2: Can you tell us about "background vs. foreground" IP rights?
QUESTION 3: Does it matter whether particular IP rights are "registered" vs. unregistered?
34.5.7. Property Rights: Liens and security interests
QUESTION 1, for Michael:
Can you explain what a "lien" is, and is it any different from a "security interest"? \\ (See the very-brief notes on liens at 18.2, and on security interests at 24.1.)
QUESTION 2, for DCT:
Suppose that:
• a creditor has a lien, or a security interest, on collateral;
• the creditor hasn't been paid and wants to "foreclose" on the lien or security interest; and
• "American law"* applies.
* In the usual case, this would normally be a matter of state law, for example the Uniform Commercial Code, and not federal (national) law.
Question: In the real world, in general, what steps must the creditor party take to foreclose? \\ [DCT to recount son's experience as a moving man, helping a law-enforcement officer to execute on a court judgment.]
34.5.8. Breakout room: Foreclosures in China
How are "foreclosures" commonly done under Chinese law?
Has anyone had any personal experience in doing foreclosures, or in resisting foreclosures?
34.5.9. Conditional vs. unconditional transfers
QUESTION, for Michael: Could you talk briefly about conditional vs. unconditional property transfers?
Transfer now, but with possibility of reversion later if escape-clause conditions are satisfied
Future transfer when all prerequisite conditions are satisfied
34.6. Day 6: Apr. 24: Language Issues - Triage Phase 4 (DCT)
34.6.1. Reiterating: Links in this document
DCT note: Robert Sargin asked me to reiterate that the Common Draft online "clause book" contains many links to statutes, court opinions, law-firm memos about specific issues, and other useful reading.
34.6.2. Letters of intent
RAISE HANDS: Who thinks a letter of intent ("LOI") is binding? (On Zoom, see the "More" button, usually at the bottom of the screen.)
Use "Yes" if you do think an LOI is binding.
Tap "No" if not, or if you're not sure.
Under U.S. law, a letter of intent could be binding, or some indicated parts could be binding – see 8.44 for a sample clause.
34.6.3. "Boilerplate" (general provisions): Some useful clauses & notes
BREAKOUT ROOM DISCUSSION: In your experience, have any of the following types of clause been an issue for a client? (As usual, please choose a spokesperson to "report out.")
The client's likely goal is to get an "OK" deal signed now (see 30.1.3), while spending as little money on legal fees as possible. (Reprise.)
"Perfect is the enemy of good enough" — but what is "good enough"? (W.I.D.A.C.: When In Doubt, Ask the Client.)
Watch out for "precatory" language (nonbinding statements of "hopes and dreams") (see 22.5).
D.R.Y.: Don't Repeat Yourself — usually (see 29.15). Especially: Don't write numbers as, e.g., one million seven thousand dollars ($1,700,000.00); that's from a real contract that cost a Dallas lender USD$693K.
T.T.O.: For any contract clause that creates a right or an obligation, think about the following:
Triggers: What would cause the right or obligation to come into existence? (In legalese: Are there any "conditions precedent" to the right or obligation?)
Time? When would the right or obligation start? When would it end (or, how long would it last after it starts?)
Off-ramps? Are there any exceptions to the right or obligation? (In legalese: Are there any "conditions subsequent" that would defeat the right or obligation?)
"Notwithstanding any other provision ….": What if two of these clauses conflict? (See 20.4.)
Shall might be viewed as an option or prediction and not as a command (see 7.47).
Must is clearly mandatory: Party P must take Action A.
Will might be a "softer" phrasing of a mandate: Party P will use commercially-reasonable efforts to achieve Objective O. (Consider defining the word will in that way; see 7.52.)
Is to (or is not to) is not quite as "soft" as will while not quite as brusque as must: Party P is to use commercially-reasonable efforts to achieve Objective O.
Serve your readers — help them to do their jobs (see 30.1.1) (reprise).
The Pasta Rule: Draft "macaroni clauses," not "spaghetti" (30.3).
Late-submitted invoices: Here's an indirect, real-world example of how late-submitted invoices could be very bad news:
1. In 2006, Calgon Carbon Corporation, a public company (NYSE), learned that some $1.4 million in outside-counsel invoices had not been properly recorded as expenses for the relevant financial periods.
2. Calgon Carbon's accounting department did not 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, had not processed the invoices. (Author's note: I'm pretty sure I read an article, but now I can't find it, 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.)
3. 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.
4. 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 ).
5. The Calgon Carbon general counsel apparently lost his job because of this — 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).
Example: 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.
Example: In a similar vein, 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).
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).
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).
Rivera v. Centro Medico de Turabo, Inc., 575 F.3d 10, 18 (1st Cir. 2009) (affirming dismissal of action based on forum-selection clause), in part quotingBremen, 407 U.S. 1, 10, 15 (1972) (internal quotation marks, alteration marks, and citations by 1st Cir. omitted; bracketed material and extra paragraphing added). 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
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").
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 your author has 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.
• 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).
Example:Asset Marketing (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), citingGraham 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).
Email "from" fields as signatures: 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 an email 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).