Skip to main content

The BUSKLAW September Newsletter: Both Parties Breach the Contract - Now What?

 


(Author's aside: Why no post since May? Because things have been busy here at BUSKLAW HQ - practicing law for clients!)

When both parties to a contract breach it, what's a court to do? This was the issue presented to Kent County Circuit Court Judge Christopher Yates in Zackary Electric, Inc. v Knoebel Construction, Inc. The facts are straightforward. Defendant Knoebel Construction was hired as a general contractor to build out an Altar'd State clothing store in Woodland Mall in Grand Rapids, Michigan. Knoebel in turn hired Zackary Electric as its electrical subcontractor for the project, and Zackary started work in July 2018.  On August 12, 2018, Zackary sent an invoice to Knoebel for $47K, but Knoebel did not promptly pay Zackary because Knoebel hadn't yet received any payment from Altar'd State. Unhappy with not being paid, Zackary left the job site on August 31, 2018, and it sent a letter to Knoebel declaring it to be in breach of the subcontract between the parties. Knoebel responded that it wasn't in breach because the subcontract with Zackary stated that payment to Zackary wasn't due until Altar'd State paid Knoebel, and Knoebel had not received any funds from Altar'd State. Further, Knoebel alleged that Zackary breached the subcontract by failing to complete the work, forcing Knoebel to hire another electrical subcontractor, Hardy Electric, to finish the job. Litigation ensued. 

Fortunately, Michigan contract law is clear on resolving a case where both parties breach a contract: the party who first breaches a contract cannot sue the other contracting party for their subsequent breach or failure to perform. However, this rule only applies if the initial breach was substantial. And to determine whether a substantial breach occurred, a Michigan trial court must consider whether the non-breaching party obtained the benefit which they reasonably expected to receive. 

Judge Yates found that Zackary failed to complete the work before leaving the job site in breach of the subcontract with Knoebel. He then considered whether Knoebel breached the subcontract by failing to pay Zackary's August 18th invoice and concluded that Knoebel did not (substantially or otherwise) breach the subcontract for the very simple reason that Knoebel had not received funds from Altar'd State, and the subcontract stated that payment will be made following Contractor's receipt of payment from the owner. Knoebel did not receive payment from Altar'd State until September 12, 2018, so Knoebel wasn't obligated to pay Zackary until that date.

The penultimate issue for Judge Yates to consider was damages. He found that Knoebel paid Hardy $71K to finish the electrical work after Zachary left the job, thus avoiding paying Zachary every single dollar that it would have earned if had completed the work. Of the $71K, Knoebel claimed (for some undisclosed reason) $65K in damages. Since the subcontract price for the work was $60K, and the price for Hardy to complete the work was $65K, the Court awarded damages to Knoebel in the amount of the difference, or $5K (figures rounded for simplicity). 

The final issue was the award of legal fees to Knoebel from Zachary based on the blanket indemnity provision in the subcontract. Judge Yates decided to conduct a post-trial evidentiary hearing to determine the proper amount of those fees.

One wonders if this entire litigation would have been avoided if Zachary had simply read  - and understood - that it wasn't entitled to payment from Knoebel until Knoebel had received payment from Altar'd State. Alas, this apparently* not being the case, the compensated lawyers in this dispute once again emerge as the real victors. 

*(Or did Zackary walk away from the job because they found a more lucrative contract for another project?)  

Moral: Read Your Contracts, People!

_____________________________________________

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 June Newsletter: Forcing Business Behavior Changes Through Buried Contract Provisions: Salesforce and Camping World

As reported by  The Washington Post , business-software giant Salesforce  recently instituted a policy barring its retailer customers from using its technology to sell semi-automatic weapons, including the AR-15 used in numerous mass shootings. One such customer is  Camping World , whose Gander Outdoors division sells many "AR" and other semi-automatic rifles .  Rather than approach Camping World/Gander, a "leading" Salesforce customer, and negotiating the termination of their semi-automatic rifle sales in exchange for some benefit (such as a software discount), Salesforce was tricky. They buried a provision barring the sale of semi-automatic rifles in the acceptable-use policy  ("AUP") binding on Camping World/Gander: Salesforce wants to force Camping World/Gander to make a major change to its business model via an addition to their AUP that is irrelevant to their customer's licensed use of Salesforce software. And although sneaky, I bet tha

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 April Newsletter: A Force Majeure Clause for the New Millennium

(Author’s Note: I originally wrote this post for Y2K, but I’ve updated it using plain English.  Happy April Fool’s Day 2016!)             A standard force majeure contract clause, where "Acts of God" excuse one party from performing their obligations without that non-performance being a breach of contract, are so 20th Century. So what if fire, flood, hurricane, snowstorm, or riot excuse contractual non-performance. Those events are too mundane to contemplate! Contract lawyers desperately need a force majeure clause for the clear and present dangers of the new(er) millennium! So, as a public service to the legal profession, I’ve assumed the heavy burden of drafting a "new age" force majeure clause for my colleagues to freely use: Either party's non-performance of this agreement will be excused to the extent that it is caused by the occurrence of any of the following events or circumstances: (i) Alien abduction, alien invasion, alien cerebral possession,