Skip to main content

The BUSKLAW February Newsletter: "What's in Your Contracts?" The Case for Auditing Your Contracts (Part 2)

In last month's newsletter, we discussed the importance of auditing your business contracts and pointed to five potentially troublesome provisions: identification of the parties, agreement term, payment, intellectual property rights, and confidentiality. But there are additional provisions that deserve careful scrutiny:

> Indemnification. To understand this concept, start with three players: the parties to the contract (call them Able and Baker) and a third player who isn't a contracting party (call him Charlie). Let's say Able manufactures widgets, Baker sells them in its retail stores, and Charlie is a customer who purchases an Able-produced widget from Baker. The widget injures Charlie. Charlie's lawyer sues Able and Baker because Able produced the widget and Baker sold it to Charlie. Baker's only involvement was selling the widget, so he tells Able to take care of it, i.e., defend him in the lawsuit and pay the settlement or the court judgment if the case goes to trial. The extent to which Able must protect Baker from Charlie's lawsuit is what indemnity is all about; chances are that the sales contract for the widgets between Able and Baker discusses indemnification. Lawyers love to fight over indemnity, including whether the buyer's negligence is covered, i.e., if Charlie's injuries from the widget didn't result from a manufacturing defect but because Baker damaged the widget before it was sold to Charlie and thus created the hazard that caused Charlie's injury.

The proper drafting of indemnification provisions is crucial, and exceptions or conditions to the duty to indemnify should be carefully stated. And indemnification should always relate to third-party claims and not to damages between the contracting parties for breach. Do the indemnity provisions in your contracts pass this test? 

>Insurance. Insurance provisions are vital in business contracts, but in my experience, transactional lawyers don't always understand the various insurance coverages available and how they relate to other contractual provisions. Using the above example, Baker may require to Able to maintain contractual liability insurance (and Able may want this as well) to fund (or "insure over") Able's obligation to defend Baker from Charlie's product liability suit. And cyber-risk insurance has become available that should protect a company from claims resulting from data breaches. Companies that handle customer data should seriously consider obtaining that insurance, and a savvy information technology/business lawyer can add value to that process. Is your insurance coverage adequate and complete? Is it properly described in your contracts? What about the other party's insurance?  

>Limitation of Liability and Exclusion of Certain Damages. These are key provisions that must be carefully considered unless you don't care about "betting your company" by having unlimited liability when you sign a contract. To simplify a bit, there are three major points to ponder: first, whether there should be a cap on direct damages resulting from a party's breach of the contract; second, whether a party's indirect damages should be entirely excluded from available damages resulting from a breach; and third, whether a dollar cap should apply to a party's obligation to indemnify the other.  Do your contracts contain understandable limitation of liability and damages exclusion provisions? And are they consistent with all of the other contractual provisions?

>Governing Law, Jurisdiction, and Venue. What State's laws govern your contract? If you're a Michigan-based company doing business with a California-based company, you probably shouldn't agree that California law governs the contract. And where would legal action under the contract occur? Would you rather litigate in a Michigan court or in a California court? Your decision could make the difference between driving to court proceedings in downtown Grand Rapids  - or lengthy plane trips to and from a California court. Do the governing law, jurisdiction, and venue provisions in your contracts prevent you from being dragged into a faraway court? 

>Litigation or Arbitration of Contract Disputes. Arbitration proceedings are private; court proceedings are not. Would you care if the news media attends court hearings about your dispute? And court proceedings may be more expensive than arbitration and may involve a jury trial. But if your arbitration provision isn't carefully drafted, you may wind up spending just as much for arbitration than litigation. Do you know if your contracts contain litigation or arbitration provisions? If arbitration, is that provision carefully drafted to ensure that arbitration would indeed be less expensive than litigation? 

>Legal Jargon. I've already posted about lawyers and their goofy words. But some legal jargon should simply be removed from your contracts: "and/or;" "execute" to mean "sign;" vague pointing words such as "aforementioned," "foregoing," or "below;" confusing phrases such as "including but not limited to," "in witness whereof," and "for the avoidance of doubt;" and such verbs as "may," "must," "will," and "shall," that can be confusing when used in the wrong context. And the stupid yet common practice of writing numbers in both words and digits, e.g., "thirty (30)." All it takes is a contract containing "fifteen (30)" to land you in court. Have you detected and removed all legal jargon from your contracts? (If your lawyer uses legal jargon, best get a new one.)

And what about words or phrases that sound like legal jargon but aren't? Two examples: first, there's definitely a need to insert "hereby" in some cases. Second, "according to" isn't necessarily the same as "in accordance with." And to further complicate matters, some apparent legal jargon should be retained as terms of art. Do you know what specialized legal language should remain in your contracts - and why?   

When Ben Franklin said that "an ounce of prevention is worth a pound of cure," he didn't have contract audits in mind, but his logic holds true. You can hire me to find and correct these potential problems in your contracts for a modest fee. Or you can wait until they blow up and you're forced to hire a litigator to sort them out - at a much greater cost.

2019 is here. What's in your contracts?



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

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…

The BUSKLAW September Newsletter: Lawyers and Their Goofy Words - and What to Do About It

Growing up, I was told that lawyers were smart cookies. After all, getting a law degree isn't an easy task. You first go to college and find a subject that is best suited to how your brain works so that you can maintain a high GPA. In my case, I quickly discovered that I wasn't a good fit for the "hard sciences." So I took a lot of Political Science and English courses, learned how to write fairly well, suffered through the tedious law school aptitude test on October 20, 1973, graduated with a B.A. degree in 1974 and then went on to law school. There, I endured a legal education infused with the Socratic method (here's an example), suffered occasional migraines (because some of my law professors were truly smart but couldn't teach) and graduated with my law degree on Mother's Day, 1977. Passed the Michigan bar exam and by God, became an honest-to-goodness lawyer in November of 1977!

So having gone through undergraduate studies, law school, and the bar exam…

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…