The BUSKLAW Newsletter: What We Discussed in 2018

'Tis the week before Xmas and a good time to look back on the topics that we covered in 2018. So have some eggnog (or a nice Pinot Noir), play this Xmas music, and let's reminisce:

>January: we reviewed recent cases proving that in a contract, every word has meaning.
> February: we discussed the best response when you receive an unsolicited product idea from a customer.
>March: we pondered the scenario of whether a disgruntled buyer of a haunted house can sue and get some relief.
>April: we examined the effect of an "immortal soul clause" buried in a website's terms and conditions.
>May: we discovered that mere pressure to sign a contract isn't sufficient to void the contract for duress.
>June: No post - on family business.
>July: We found out what happens when you horse around with non-compete clauses.
>August: No post - on family business.
>September: We determined what you can do about lawyers who use goofy words.
>October: We sussed out whether "efforts" provisions in contracts are worth the drafting effort.
>November: We examined why your accounts payable folks should be familiar with the contractual doctrine of accord and satisfaction.
>December: We explained why, in a contract, a "condition" does not a "promise" make.

Apart from my advocacy of plain language in drafting contracts, my goal with this posts is to discuss a court case or contract law doctrine that is relevant to my target audience: those who work with contracts and would like a better understanding of what they mean.

The sad truth is that all too often business contracts: 1) are relegated to an electronic or physical file cabinet, never to see the light of day unless there's a problem; and 2) contain legal jargon that at worst is meaningless and at best frustrates the reader's understanding of the contract's content, regardless of whether the reader is a layperson, a judge, or a lawyer. In 2019, we'll continue the good fight to change this predicament!

___________________________________

If you find this post worthwhile, please consider sharing it with your colleagues. The link to this blog is www.busklaw.blogspot.com and my website is www.busklaw.com. And my email address is busklaw@charter.net. Thanks!

Comments

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....

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 Newsletter

Search This Blog