And don’t worry about raising issues that I’ve discussed in months past; it would be pretty sad if I assumed that every reader had read every post. On the other hand, I hope you don’t mind if I critique your suggestions and point you to the relevant analyses.

So, for example, the idea of having factual assertions separate from remedies makes sense, but I would never use the wording you suggest. This isn’t the appropriate forum for lengthy explanations; you might want to check out MSCD 12.433 regarding use of the verb to warrant. And it’s best not to refer to “breach” of a factual assertion: representations are simply accurate or inaccurate. (See MSCD 12.316.) So I’d state the facts, then I’d state simply, without any magic words, what happens if any of those facts are inaccurate.

Ken

“Utter bollocks!” I love it!

For the record, I did not begin my subscription to your blog until recently, so I was not aware that you had already addressed this issue. I apologize for raising the dead. Also, to be clear, I wrote to report on what others have argued; I did not necessarily mean to suggest that their arguments were persuasive.

You struck a chord when you said that caselaw provides examples of usage sufficiently unclear that the parties ended up in litigation. Personally, I’ve deemed every contract I’ve negotiated that ended in litigation as evidence of a failure on my part (and on the part of my adversaries).

The primary objective of the contract drafter should be to memorialize a complete agreement between parties in language that the parties (and a reasonable trial judge and jury) can understand. Consideration as to how an appellate court might construe clear language should be secondary, because if the language is clear and the agreement complete, litigation will never be necessary.

The language you “just dreamed up,” however, seems no clearer than the “represents and warrants” language it is designed to replace. [Just as the language of my emails, written "on the fly," likely is less than optimally clear.] Your proposed provision seems exactly the type of verbiage that a party is not going to understand, at least not easily.

Why not keep it really simple? In a Party Assertions section [Yes, I've read some of the debate over capitalization, and I extend my advance apologies to the offended multitudes.] provide, “Party ‘A’ asserts as follows …” Then, deal with the remedy ramifications of the assertions in the appropriate remedies section [Insert as part of the Indemnity boilerplate, for example, "Party 'A' warrants that the assertions made in section (whatever) of this Agreement are true as of the Effective Date and shall be true as of the Closing Date ... (continuing with any appropriate materiality limitations)."]. This probably makes “covenant” language unnecessary, but if someone feels otherwise, similar language can be inserted where appropriate. [Party Covenants? Pre-Closing Conditions? I really have no settled view as to the proper place, if any, for such language. It depends on the nature of the assertions and whether they should survive closing.]

Ken, I don’t think you’re “missing anything.” As I wrote earlier, adding “covenants” is probably surplusage at best. On the other hand, the concept of “breaching” [if that's the right word] a “representation” is conceptually unclear, while the concepts of breach of warranty and breach of covenant are very clear. In the end, however, it is probably a semantic issue of little significance.

Regards and renewed best wishes for the new year.

/s/Michael D. Scott

Mark: So we meet again over this issue!

My argument isn’t expedient. I hold that the goal in drafting is to articulate the intent of the parties without having to call on the courts to breathe meaning into contract provisions. So my recommendations are primarily grounded in semantics.

Caselaw is relevant in three ways. First, it provides me with plentiful examples of usages that were sufficiently unclear that the parties ended up in a fight. Second, if courts in some jurisdictions have been irrational enough to insist on certain magic words for a given provision to be enforceable, I obviously take that into account. And third, if the bulk of precedent is consistent with my understanding of a given usage, that suggests that I might be on the right track.

My understanding of the way language works tells me that the “magic words” approach to represents and warrants is fundamentally unhelpful. And on this issue, I’m not going to automatically defer to a court’s conclusions—a judge is no better equipped than, say, a journalist to tell me how language works.

And the fact that no U.S. caselaw supports the “magic words” approach, and the fact that the Uniform Commercial Code goes out of its way to refute it, tells me that I won’t have to work too hard to convince lawyers in the U.S. that my approach makes sense. If a case or two to the contrary should surface, would that weaken my argument? Hardly. I might even welcome a few such cases—they’d give me something to throw rotten tomatoes at.

For the same reason, the reasoning in the Man Nutzfahrzeuge case—I should probably have used the other party’s name, Freightliner!—gives me no pause. Similarly, I’d be a twit to pay attention to what the judge in Rhodia v. Huntsman had to say about best endeavours.

As for what some PLC functionary had to say, I don’t give a fig. It’s blather of the sort that’s routinely used to introduce a boiled-down version of caselaw. I had a good, hollow, laugh when I saw a similar formulation used in a law-firm newsletter to introduce a summary of Rhodia v. Hunstman.

I’m aware of the doctrinal distinction between representations and warranties, but that doesn’t have to bear any relation to the verb you use to introduce a factual assertion. You’re certain that the “magic words” approach is clear and understood by all, but the Jones Day briefing paper that I cited suggests otherwise.

And more to the point, one of the great things about contract drafting is that you’re at liberty to articulate meaning in any way you see fit. Anyone who can improve on time-honored but deficient formulations is perfectly free to do so, and in this case would benefit from doing so.

By the way, I too have a soft spot for Robert Harris’s historical novels.

Michael: No killing, I promise! But I have to say that the notion of represent, warrant, and covenant accomplishing anything is, pardon my French, utter bollocks. I discussed it in this June 2009 blog post. Say in standard English whatever you’re trying to accomplish with respect to remedies! If you think I’m missing something, please let me know.

Aquariumdrinker: It’s great to have your input. I wouldn’t have recommended my approach if I didn’t think it would, for the most part, fly under the radar.

Chris: I agree that the best way to avoid fights would be to use a verb like asserts, as it’s free of any baggage. But I haven’t recommended that approach—like you, I have little hope of convincing lawyers to use a brand-new word. Instead, I’ve opted to suggest that they drop the more problematic component of the traditional couplet.

And regarding your notion of adding a provision to the effect that the contract is to be interpreted consistent with MSCD, I’m not sure that would work, as MSCD is geared to drafting contracts, not interpreting them. Maybe you’d achieve the desired effect by including with any draft contract a cover note of the sort I proposed in this January 2009 blog post.

Ken

Instead I would have a section in which a party makes factual assertions about current or past states of affairs, introduced by something that is very plain English, like “XYZ confirms that . . . .” By itself, that supports a misrepresentation claim or a breach of warranty claim. If I want to limit the remedy, I would do that separately.

Then I would put “representations” about future states of affairs as positive promises (using “shall” as Ken requires). There is no misrepresentation claim there, but there is a breach of contract claim.

I won’t ever get my way on this, so I’ll use what Ken says instead. And, if I am successful in getting a contract drafted to Ken’s standards, I might put in a provision saying that it should be interpreted in light of MSCD. That way, when the question of what “represents” means comes up in a case, we have an interpretive guide. I’d use something like the following: “This agreement is to be interpreted consistently with the second edition of Kenneth A. Adams’ A Manual of Stye of Contract Drafting, which the parties used in drafting this agreement.” I would throw that in right after the standard bit that negates the rule of interpretation against the drafter.

Chris

Even if this is considered necessary, I dislike the word “covenant”. Under English law, a covenant is an undertaking given in an agreement made as a deed, although it is often used in ordinary agreements to make the obligation sound more important. It is therefore magic wording without the magic.

More often (but still not all that often), attorneys representing smaller counterparties have inserted “and warrants”. When the draft goes to Jones Day, for example, they tend to focus on more substantive issues. I’m most likely to be “corrected” by attorneys at smaller shops for whom (I’m guessing) contract or deal work may make up on a middling part of their practice.

Of course, the set of contracts that fourth year associates at mid-size firms “own”, however briefly, isn’t representative of (and probably isn’t even a particularly good proxy for) the larger body of agreements being drafted today. But my experience within that set is that convention may not be so far away from allowing contract drafters to avoid the use of both “representations and warranties”.

At bottom, there is a distinction between a “representation,” which is properly construed as nothing more than a statement or an assertion, and a “warranty,” which encompasses the remedy notion that Glenn discusses. But, I recall an “old-school,” “magic words” focused article suggesting that “represents and warrants” is still not enough! The author of that article claimed that the real magic words were “represents, warrants and covenants.” “Covenants,” the author claimed, was to be read as “stipulates,” thus covering matters as to which a party has made a good faith, yet erroroneous, “representation.”

In other words: “represents” means “says” or “asserts,” “warrants” has the meaning Glenn suggests, and “covenants” means “agrees” or “stipulates” (without regard to truth).

Having served as in-house counsel to one of Glenn’s firm’s more cantankerous, nit-picking corporate clients (the CEO was a cranky lawyer), I was sensitized to “magic words.”

While I agree that all of this is probably the proverbial distiction without a difference, there are still some clients who want to pretend they live in 13th Century England.

Two suggestions (to the extent they may prove necessary):

Assuming the contract needs and contains a “Definitions” section, why not simply provide that, “Represents means represents, warrants and covenants.”

Alternatively, if the client is fixed on encompassing all three concepts, but is not necessarily wedded to particular language, simply say what you mean. Instead of “represent, warrant and covenant,” each party could “assert, warrant and stipulate” or, better yet, “state, warrant and agree.”

Regards and best wishes to all for 2010,

/s/ Michael D. Scott

One thing I hate, is rhetorical arguments. In your earlier post one of your arguments was that you couldn’t find a single case supporting Tina’s approach. Now that a case has been found, you change your argument and say it is only one case, by a “semantically challenged” judge. Will 10 cases by judges with higher degrees in linguistics close off this point, or will you change the argument again?

Part of the difficulty with arguing with you is that you set the rules of the game.

According to my rules, good contract drafting needs to take full account of the approach taken by judges, particularly senior ones, when interpreting contract wording. You can dismiss the case as having been decided by a semantically-challenged judge. I have to take account of it. PLC, the leading UK resource for legal research, began its summary of this case as follows: “In October 2005, Moore-Bick LJ gave one of the most valuable judgments ever delivered by the English courts. ”

Under English law, there is a distinction between a warranty and a representation, and they do have different legal consequences, both as to the remedies available and the method of calculating damages. When you use one of these magic words in a contract, the court’s starting assumption is that you meant to use the word in its magic sense. However, there are also some legal safety valves, where the legislature or court recognises that the draftsman may not be using the word “correctly”.

For instance, the UK Sale of Goods Act 1979 distinguishes between conditions and warranties. However, section 11(3) of that Act provides:

“Whether a stipulation in a contract of sale is a condition, the breach of which may give rise to a right to treat the contract as repudiated, or a warranty, the breach of which may give rise to a claim for damages, but not to a right to reject the goods and treat the contract as repudiated, depends in each case on the construction of the contract; and a stipulation may be a condition, though called a warranty in the contract.”

Similarly, case law provides:

“Whether a stipulation in a contract of sale is a condition, the breach of which may give rise to a right to treat the contract as repudiated, or a warranty, the breach of which may give rise to a claim for damages, but not to a right to reject the goods and treat the contract as repudiated, depends in each case on the construction of the contract; and a stipulation may be a condition, though called a warranty in the contract.”(LG Schuller AG v Wickman Machine Tool Sales Ltd [1974] AC 235, House of Lords)

As a practising lawyer, I need to take account of this stuff. I can’t just dismiss it by saying that the judge is semantically challenged.