- •CONTENTS
- •CONTRIBUTORS
- •PREFACE
- •Introduction
- •I. A Positive Account
- •II. Normative and Historical Accounts
- •III. Explaining Legal Doctrine
- •A. Willful Breach
- •B. Comparative Fault
- •Conclusion
- •ACKNOWLEDGMENT
- •Introduction
- •C. Summary
- •Conclusion
- •Introduction
- •B. Some Striking Nuances in Common Law Systems
- •II. A Market Function Approach
- •A. Ethics or Economics – The Wrong Question
- •B. Party and Market Expectation as Guidelines
- •D. Fault, Foreseeability, and Other “Softeners” of Strict Liability
- •Conclusion
- •I. Fault and Uncertain Contractual Intent
- •II. An Expanded Law and Economics Approach to Fault
- •III. A Fault-Based Approach to Contract Damages
- •Conclusion
- •Introduction
- •A. A Model
- •B. Fault
- •C. A Comparison: Strict Liability Versus Negligence
- •II. Doctrine
- •A. Impossibility/Impracticability
- •B. Reasonable or Substantial Performance
- •C. Good Faith and Best Efforts
- •D. Interpretation/Implied Terms
- •E. Conditions
- •F. Damages
- •Introduction
- •I. Unconscionability
- •A. Markets
- •B. Moral Fault
- •II. Unexpected Circumstances
- •III. Interpretation
- •IV. Mistake
- •C. Cases in Which the Nonmistaken Party Neither Knew nor Had Reason to Know of the Mechanical Error
- •V. Nonperformance
- •Conclusion
- •Introduction
- •I. Modernizing Tort and Contract Around Fault
- •II. Explaining the Fault Swap
- •Conclusion
- •Introduction: From Fault to Negligence – and Back
- •I. Tort Law
- •III. Gratuitous Transactions: Bailment and Agency
- •A. Coggs v. Bernard
- •C. Siegel v. Spear and Comfort v. McGorkle
- •D. Medical Malpractice, Occupier’s Liability, and Guest Statutes
- •IV. Frustration and Impossibility
- •Conclusion
- •Conclusion
- •A. Analogies in Criminal Law
- •B. Lay Assessments of Culpability
- •C. Two Ways of Defining “Willful”
- •B. “Willful” as a Test for Inefficiency?
- •B. Optimal Damages Under Strict Liability
- •Conclusion
- •II. Cost of Correction Versus Diminution in Value
- •B. Treatment by the Courts
- •Conclusion
- •Introduction
- •C. An Information-Based Explanation
- •B. Informal Lessons from the Example
- •D. From Moral Hazard to Adverse Selection
- •II. Willful Breach Doctrine
- •A. Overcompensatory Expectation Damages
- •B. Tort Damages for Bad-Faith Breach
- •C. Restitution
- •Conclusion
- •Introduction
- •I. Expectation Damages and Willful Breach
- •II. Willfulness, Material Breach, and Damages
- •Conclusion
- •Introduction
- •A. Noncooperation
- •B. Overreliance
- •A. Setting the Stage
- •B. Noncooperation
- •1. When Should Avoiding Overreliance be the Default Rule?
- •Conclusion
- •Introduction
- •I. Stipulation, Fault, and Mitigation
- •II. Encouraging Stipulation
- •A. How Courts Encourage Parties to Stipulate
- •B. Two Advantages of Stipulation: Knowledge and Mitigation
- •Conclusion
- •Introduction
- •II. Comparative Negligence
- •III. Mitigation
- •IV. Reasonable Reliance
- •V. Causation
- •VI. Foreseeability
- •Conclusion
- •I. Summary of the Argument that Breach May Not Be Immoral Given the Incompleteness of Contracts
- •F. When Is Breach Immoral and When Is It Moral in Practice?
- •II. Criticism and Discussion of the Foregoing Argument
- •Conclusion
- •Introduction
- •I. Promise De-moralized, Contract Moralized
- •II. Contract and Promise: More on the Relationship
- •IV. Harm, Fault, and Remedies for Breach
- •V. Fault and Institutional Harm
- •Conclusion: Toward a Moral Law of Contract
- •I. Breach as Moral Harm
- •III. Moral Norms as Default Rules
- •Conclusion
- •CASE INDEX
- •SUBJECT INDEX
78 • Eric A. Posner
C. Good Faith and Best Efforts
In Feld v. Henry S. Levy & Sons, Inc.,17 the contract required the defendant, a bread-baking business, to sell to the plaintiff all of its breadcrumbs output for a certain period. Later, the defendant decided to stop production of breadcrumbs in order to create space for a computer room. Because the contract required defendant only to sell its output, and its output ceased when it dismantled the equipment for making breadcrumbs, the defendant argued that it had not breached the contract. The plaintiff argued that the defendant had breached the contract by failing to act in good faith. The court agreed.
Th e court acknowledged that the defendant could have reduced its output without violating the contract, and could even have ceased production if its losses were “more than trivial.” But it held against the defendant because the defendant asserted in a “conclusory” fashion (i.e., without evidence) that the breadcrumb operation had become “uneconomical.”18 Th e court also mentioned that the six-month cancellation clause allowed the defendant to protect itself to some extent, that the defendant offered to resume breadcrumb production if plaintiff paid a slightly higher price than that stipulated in the contract, and that the defendant did not take steps to obtain “more economical equipment.”19
Th e court appeared to believe that the defendant’s breach was willful. The defendant had simply discovered that the price it obtained was less than its costs, including its opportunity costs, tried to hold out for a higher price, and then shut down operations when the plaintiff refused the offer. What is relevant to the argument here is the reference in the opinion to the conditions under which defendant’s behavior might have been excused. The language implies that defendant could have avoided liability by showing that it could not have taken reasonable steps to reduce its costs to a tolerable level.20 Because the defendant did not make such a showing, we do not know whether the court would have excused liability based on the absence of fault (on the cost-benefit interpretation or any other), but the language does suggest such an outcome.21
17335 N.E.2d 320 (N.Y. 1975).
18Id. at 322–3.
19Id. at 321.
20However, the court expressed doubt about whether such a test would be feasible. Id. at 323 (“In any event, ‘economic feasibility’, an expression subject to many interpretations, would not be a precise or reliable test.”)
21Cf. Charles J. Goetz & Robert E. Scott, Principles of Relational Contracts, 67 Va. L. Rev. 1089 (1981). Goetz and Scott similarly argue that in such “relational contracts,” courts cite the doctrines of good faith and best effort when they are really just trying to determine whether continued performance would be value maximizing.
Fault in Contract Law • 79
D. Interpretation/Implied Terms
One might respond by arguing that the court in Feld was not so much relying on notions of fault as interpreting the contract. The case was a strict liability case; it is just that the court (in effect) interpreted the contract to implicitly provide that the baking company could cease output when cost-justified steps could not ensure efficient performance and not otherwise. Having construed the contract in that way, the defendant was strictly liable for failing to engage in cost-justified behavior.
But this is just an argument by definition. We could say that courts import fault principles when they interpret contracts in order to preserve strict liability in making the liability determination; or we could say that courts interpret contracts literally and use a negligence rule in the liability determination. The two statements amount to the same thing. The larger point is that courts, one way or the other, try – at least sometimes – to eliminate or limit damages when the promisor could not have avoided breach through cost-justified actions – that is, was not negligent.
Consider the following illustration from the Second Restatement of Contracts. A mining company hires an engineer to help reopen a mine for “$10,000 to be payable as soon as the mine is in successful operation.”22 Th e engineer performs but the mine cannot be reopened. The Restatement says that the engineer should nonetheless be paid.23
Th e point seems to be that the mining company most likely hired the engineer to provide a service, and not to provide insurance in case that the service does not result in successful opening of the mine. The only possible interpretation of this argument is that the engineer should supply cost-justified efforts and no more. Again, the negligence idea reappears. It is idle to argue about whether the doctrinal reason for this result is that the contract “really” provides for only cost-justified performance or that the contract requires performance but the engineer will be excused from liability as long as the performance that he actually provides is cost justified. In both cases, contract law operates as a negligence-based system rather than as a strict liability system.24
22Restatement (Second) of Contracts, § 227 cmt. B, illus. 2 (1981).
23Id.
24To be sure, if the contract explicitly provides for a negligence standard of liability – that is, it says that the promisor must take cost-justified actions – then “strict” enforcement of such a contract would produce the same outcome as fault-based enforcement.
80 • Eric A. Posner
E. Conditions
Many contracts contain express conditions, and the promisor is obligated to perform only if those conditions are met. Even when contracts do not contain express conditions, courts frequently imply conditions. There are no hard and fast rules governing when conditions are implied, but there are patterns. For example, courts frequently make payment conditional on performance even when the contract does not say so.
Courts also imply conditions in much the same way that they imply other sorts of terms, based on a judgment about what the parties would have agreed to. This kind of judgment will reflect principles of fault when courts believe that parties would have wanted such principles in their contract. For example, in Jacobs & Youngs, Inc. v. Kent, a contractor breached a contract by failing to install the type of pipes that the contract specified.25 Th e promisee refused to pay, invoking the traditional rule that payment is conditional on performance.26
Th e court appeared to believe that the cost of performance, tearing down the building and installing the correct pipes, exceeded the value of performance, installation of the correct pipes, which apparently were not functionally different from the pipes that were installed;27 the question is whether it also believed that the failure to notice the mistake before installation occurred was inadvertent rather than negligent. In pointing out that an architect inspected but failed to notice the error, the court implied that the error was inadvertent.28 In the face of explicit contractual language to the contrary, the court eliminated liability (or greatly reduced it) because the breach was not negligent or willful.29
For another example, consider Royal-Globe Insurance Co. v. Craven.30 An insurance contract conditioned payout on notice of the claim within twentyfour hours of the accident. Theresa Craven, the insured, was unconscious during that period and so could not provide notice, but failed to give notice until three months after she was released from the hospital. The court excused her from the promise to give notice within twenty-four hours but held that she failed to comply with an implicit obligation to give notice within a reasonable time after she had recovered, and thus was not entitled to payment.31 Alternatively, one could describe the result in terms of a negligence system. Craven’s breach of her promise to give notice within twenty-four hours was
25129 N.E. 889 (N.Y. 1921).
26Id. at 890.
27Id.
28Id. at 890. The brand was printed on the outside of the pipe in intervals but the pipe was otherwise indistinguishable from other pipes.
29Id.
30585 N.E.2d 315 (Mass. 1992).
31Id. at 316–18.
Fault in Contract Law • 81
not willful or negligent – she was unconscious. Further, there was nothing she could have done prior to the date of performance to ensure that she could have given notice when her duty to do so arose. By contrast, the failure to inform promptly after she returned to health was clearly negligent (or even willful). It would have cost Craven very little, while notice gives the insurance company a chance to verify the claim before the evidence becomes stale.
F. Damages
George Cohen argues that the damage measures reflect fault principles. He points out that courts sometimes award restitution damages when breach is willful, and sometimes award reduced damages – reliance damages, for example – when the breach is inadvertent or negligent.32 Similarly, the draft Third Restatement of Restitution and Unjust Enrichment provides that the remedy for “opportunistic breach” may be disgorgement of the breacher’s gains.33 When the breacher’s gains are significant, the victim’s remedy may be supracompensatory.
In fact, in a fault-based system, courts should award zero damages rather than reliance damages when breach is inadvertent, and should award at least full damages (V minus any unpaid portion of the price) when breach is negligent. Thus, a negligence regime would operate by excusing conduct through liability rules rather than adjusting damages. Nonetheless, Cohen may well be right that the range of damage remedies reflects different attitudes toward willful, negligent, and inadvertent breach. In a strict liability system of contract liability, a supracompensatory remedy for breach makes no sense. Putting aside special cases,34 a supracompensatory remedy just deters efficient breach under strict liability.35 In a negligence regime, by contrast, a supracompensatory remedy for opportunistic breach does not deter efficient breach, as long as opportunistic breach means that V > C – that is, as long as breach would be, in fact, inefficient. The promisor should always perform when performance is efficient. There is no reason to award greater damages when breach is willful than when breach is negligent, but no harm comes from this practice, either.36
32Cohen, supra note 1.
33Restatement (Th ird) of Restitution and Unjust Enrichment § 39 (Tentative Draft No. 4, 2005). For similar principles, see Restatement (Second) of Contracts § 357 (1981).
34Special cases include the use of damage multipliers when breach is difficult to detect. See Craswell, supra note 6, at 2230.
35See Alan Schwartz, The Myth that Promisees Prefer Supracompensatory Remedies: An Analysis of Contracting for Damage Measures, 100 Yale L.J. 369 (1990).
36Again, a similar result can be found in the literature on tort law. See, e.g., Shavell, supra note 7.
