Skip to main content

The BUSKLAW June Newsletter: Do Your Contracts Contain "Empty" Words?


Until 1800 or so, lawyers who drafted contracts in the U.K. were called scriveners, and they were paid by the number of words in their documents. More words resulted in more money. This encouraged the use of excessive words in contracts - and the legal mumbo jumbo that plagues the legal profession to this day. 

"Empty" words in a contract are more than just unnecessary; they create ambiguity, cause confusion, incite litigation, and increase the time it takes to read and understand a contract, especially for the business folks who must understand the contract to effectively administer it.  

Most contracts (especially the forms that you can download from LegalZoom and RocketLawyer - excuse me if I don't give you the links) contain empty words, and these are some of the worst offenders:

  • Archaic words. At the beginning of a contract, you'll often see a paragraph with the heading "Recitals" followed by several "Whereas" clauses and concluded by a "Therefore" clause that commonly includes the phrase "in consideration of." None of these terms add any business or legal value and should be junked. Better to replace them with an introductory paragraph captioned "Background" followed by a brief description of the parties' business relationship giving rise to the contract. And there's no excuse for the phrase "in witness whereof" before the parties' signatures at the end of the contract! 
  • Confusing references to the contracting parties. For example, software license agreements commonly refer to the parties as "licensor" and "licensee." These words are so similar that it's easy to use the wrong one. Why not simply use the real names of the parties? Just define "Able" as licensor and "Baker" as licensee at the beginning of the agreement, and then use Able and Baker throughout the document.    
  • Vague antecedent references. In the body of the contract, you'll often see such terms as "said," "such," "aforementioned," "above-mentioned," "hereinabove," "above," "foregoing," or the like. These terms often cause problems. For example, beginning a sentence with "except for the foregoing..." What does "foregoing" refer to? A preceding sentence or a preceding paragraph? Judges have had to grapple with these terms to decide what the parties intended when there is a lawsuit over what one of these terms actually referred to.
  •  Words used incorrectly. The phrase "due to" shouldn't be a substitute for "because." The proper use of "upon" is only for a condition or event. The verb "execute" shouldn't be used in lieu of "sign." The phrase "provided that" is usually not the best way to describe a condition. And don't use "shall" and "will" to create language of obligation interchangeably; better to forget "shall" altogether and use "will" or "must." And "which" should only replace "that" before a non-restrictive clause that is preceded by a comma. 
  • Grandiose words. The words in this bucket sound impressive but usually add nothing of substance where they appear: "forthwith," "merely," "completely," "duly," "whatsoever," "without limitation," and "for all purposes." Other examples: "with respect to," "in connection with," and "in order to." And "prior to" is best replaced with "before." Finally, "as of" should be replaced with "on."
Lawyers have various excuses for holding on to legal jargon. I will address these in a future post. For now, let's make a long story short: none of the excuses for using empty words in a contract are persuasive. 

An effective contract creates an easily understandable blueprint of the parties' legal and business relationship rather than a meandering mystery tour of that relationship. If you find that your contracts are rife with empty words, the remedy is simple: find a lawyer who will take the plain-language pledge and purge these pointless words from your contracts! As for me, I'll practice plain-language principles until the hearse horse snickers as he hauls my carcass away. 
__________________________________________ 

If you find this post worthwhile or entertaining, please consider sharing it with your colleagues. The link to this blog is www.busklaw.blogspot.com and my website is www.busklaw.com. Thanks!

Comments

Popular posts from this blog

The BUSKLAW 2021 Year in Review - Brit English Sums It Up!

  I'm at a loss to describe 2021 using American English, sorry. AmE has grown tiresome. Don't believe me? Just turn on your local TV news and listen for how many times the news people use "prior" instead of "before" and pepper their speech with "as well," frequently tacking it on after using "also" in the same sentence, as in "It will also rain tomorrow as well." How can all be WELL when every other sentence ends with AS WELL? Warning: don't play a drinking game to count the number of  AS WELLs or you'll be pished (as they say in Scotland) in 10 minutes. Which reminds me of why we should be thankful for Brit English to describe 2021: it was another year that we good guys got knackered .   Consider: Covid continues unabated - now improved with variants (get your booster, wear a mask)! The peaceful transition of the U.S. government after the 2020 presidential election almost didn't happen (can you say "insurrectio...

The BUSKLAW Halloween 2022 Post: Stephen King's Asides on Poor Writing in Fairy Tale

  Having just read  Stephen King's Fairy Tale in time for Halloween, it's appropriate to examine his asides on poor writing included in the book. (BTW, Fairy Tale is a good read with King's typical well-executed character development, plot, and a great finish to the story. But you have like the whole Grimm fairy tale genre before you read his take on it.)  Stephen King doesn't tolerate anything less than crisp prose. When the story's hero, Charlie Reade, tries to read a book about the origins of fantasy and its place in the world matrix ("what a mouthful"), he can only scan it because: It was everything I hated about what I thought of as "hoity-toity" academic writing, full of five-dollar words and tortured syntax. Maybe that's intellectual laziness on my part, but maybe not. Later on, Charlie tries to focus on a particular chapter in the "origins of fantasy" book about the story of Jack and the Beanstalk but is put off by "t...

The BUSKLAW May Newsletter: The Foolhardy Practice of Using Faux Terms of Art in Your Contracts

  Most lawyers draft contracts. That's what lawyers do. And they use perceived terms of art ("TOAs") because they want to be paragons of contract-drafting precision. But here is where the canker gnaws:  the words that lawyers insert in their contracts as TOAs are actually not, potentially causing problems in clarity and interpretation. And as I've said time and again, these problems lead to disputes, and disputes lead to litigation, which is always time-consuming and expensive for the parties involved.  Let's first define TOAs in the legal context. According to Professor Bryan Garner in his Dictionary of Legal Usage , TOAs have specific, precise meanings that are "locked tight" and based on legal precedent. But then there are the faux TOAs, "whose meanings are often unhinged." Expert contract drafters, Garner says, know that clear, simple drafting is less subject to misinterpretation than using TOAs that are nothing more than "mere jargon....