Skip to main content

The BUSKLAW August Newsletter: Clean Out Those Cobwebs in Your Contracts!

Cobwebs are subtle signs of neglect. Although supposedly spider-generated, I swear that they appear out of thin air. They sneak into attics, ceiling corners, under sinks, and in the guts of your personal computer. But they can also lurk in your contracts, figuratively speaking. August is the perfect time to pause your hectic pace (perhaps while your tireless first assistant is enjoying a rare vacation), open your contracts file cabinet, and clean out the cobwebs in your contracts.

Before we discuss the cobwebs to search for and destroy, you may respond, "but I don't have a contracts file cabinet - all my contracts are stored digitally on my computer." Wrong approach! It makes good sense to print out your contracts and put them in a physical (dustproof) file folder that is then stored in a physical (fireproof and locked) file cabinet. Does this sound old-fashioned? Consider the established fact that reading text on paper has several advantages to reading text on a screen, as this Scientific American article describes. So fire up your printer and print out your contracts "before you dot another 'i' Bob Cratchit!"

So we'll assume that you now have your paper contracts in front of you. Let's begin the cobweb-cleaning work. Here's what to look for:
  • Are your contracts legible, i.e., can you actually read the print on all of the pages? When I practiced in U.S. Bankruptcy Court (a long time ago), Judge Nims wouldn't even consider admitting a document into evidence unless it was totally legible. So if you discover unreadable pages in your contracts, you need to fix that, even if it means asking the other party for a clearly readable copy of the contract. 
  • Are your contracts signed and dated? I once had a client who (before they hired me) avoided signing any of their contracts (after the other party signed first and would hopefully forget to ask for a fully-signed copy) on the assumption that if the relationship didn't work out, you could escape liability because you never signed the contract! Nice try, but it doesn't work that way. If the parties acted according to the contract, a judge or jury may find that the contract is enforceable, even if it wasn't fully signed. (And no, "executed" isn't the synonym of "signed.")
  • Are your contracts still in effect? Do you track the expiration (and any renewal) terms of your contracts? The more contracts that you have, the more likely it is that you are operating under an expired contract. This can cause problems for everyone involved. If you want the relationship to continue, you best prepare an amendment retroactively extending the termination date. But don't be surprised if the other party demands something in return. After all, contracts are a two-way street! 
  • Are you (and the other party) in compliance with the contract's insurance provisions? If your contracts contain insurance provisions (whether applicable to one or both parties) are you in compliance? What about the other party? Unless you have a close relationship with your risk manager, you may not know if your company still has the required insurance coverages in effect, or if the same is true for the other party. And if the parties are required to exchange insurance certificates reflecting the required insurance, do you have a current insurance certificate from the other party? And if the contract requires the other party to name you as an additional insured, does your insurance certificate from the other party reflect that? If not (e.g., the certificate simply names you as a "certificate holder"), you have unexpected liability exposure to third-party claims.
  • (For IT folks) Do you have contracts for cloud services? If so, whether you are the customer or vendor, the data security provisions deserve close scrutiny. Data security standards and audit rights are essential parts of any cloud services agreement together with appropriate insurance, indemnity, and limitation of liability provisions. (If you have any questions about those, please remember this recent post.)
  • Do your contracts contain confusing, ambiguous, and turgid legal jargon?  My readers know the mantra: lawyers who draft contracts containing legal jargon are doing a great disservice to their clients. It's axiomatic that legal jargon leads to disputes, disputes lead to litigation, and litigation outcomes at best are a Pyrrhic victory. So if your lawyer doesn't use plain language principles advocated by such respected legal scholars as Ken Adams, Bryan Garner, and Joe Kimble, find a lawyer who does and have them cleanse that poppycock from your contracts. (If you need help with that, drop me a line.) 
Having eradicated these cobwebs from your contracts, you can show your first assistant that you remained terrifically productive during her summer-vacation absence! 

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



Popular posts from this blog

The BUSKLAW April Newsletter: Pulling Apart the Purchase Agreement for the ICON A5: "The Jet Ski with Wings"

The ICON A5 is an amphibious "light-sport aircraft" that is marketed primarily to adventurous amateur pilots with deep pockets (and spacious home garages in which to store their ICONs). The plane has a recreational focus; it can seat only two, has limited load capacity, and isn't intended to go very far. The cost of the plane was $139K when first introduced in 2006 but is now $389K for a "fully-loaded version."

YouTube is full of videos showing how much fun you can have with an ICON A5 (especially with water landings and take-offs), bringing to mind the "jet ski with wings" analogy. So the ICON A5 is perhaps the ultimate high-tech, outdoor adult toy (unless you're afraid of heights). There have been several fatalities with the A5, but these apparently resulted from pilot error in one case and reckless flying in another rather than from mechanical defects or design flaws. 

The ICON A5 Purchase Agreement (including the Operating Agreement as Exhibit B…

A BUSKLAW Newsletter Aside: We Speak Information Technology Law

When I describe my legal specialty as information technology ("IT"), the common response (along with a puzzled look) is, "what does that mean?"

Short answer: "It means a lot." 

Because there isn't a business in existence that isn't affected by something IT related. Does your firm have a website that collects personal information? Then you should have terms of use (and a cookie policy) that comply with state and federal laws, regulations, and the GDPR. Do you sell things on your website and accept credit cards as payment? Then you must institute payment card industry data security standards to protect that credit card data from hackers. And you also must have credit card agreements with your card companies and processing bank that contain indemnity and other "bet your business" obligations. In my experience, credit card agreements are notoriously one-sided and chock full of legal jargon. Have you read yours?  

Apart from those considerations…

The BUSKLAW May Newsletter: "Here's Another Clue for You All, the Walrus Was..."

To continue the title: Paul. As in Sir Paul McCartney. But in 1969, there was a problem: several radio stations broadcast a conspiracy theory: Paul died in a car crash in 1966. And the remaining Beatles covered it up and replaced the dead Paul with an (apparently equally-talented) imposter. Fans began scouring Beatles songs for evidence of the ruse; they pointed to "The walrus was Paul" line from the song White Onion, concluding that "walrus" was the Greek word for corpse (it isn't). in reality, John Lennon was messing with fans' propensity to find meaning to those lyrics when there was none. In an interview for what later became the Beatles Anthology television documentary, John said: 

I threw the line in—"the Walrus was Paul"—just to confuse everybody a bit more. It could have been "The fox terrier is Paul." I mean, it's just a bit of poetry. I was having a laugh because there'd been so much gobbledygook about Pepper—play it bac…