Thursday, June 14, 2012

Knock-for-knock Indemnities

A knock-for-knock indemnity is a reciprocal or mutual indemnity that is frequently used in the oil or gas industry where injuries could occur only to the employees of the contracting parties and damage could occur only to the property of both parties. Under a knock-for-knock indemnity both parties agree to indemnify the other against claims for injuries or damages that they or their employees sustained regardless of who was at fault or who was negligent.

For example under a knock-for-knock indemnity, you could have Oil Company X and Drilling Company Y. In a knock-for knock or mutual indemnity Oil Company X will be responsible for any damages to Oil Company X’s property or employees and has to indemnify Drilling company Y against any claims and pay any damages awarded.The same would apply if an employee of Drilling Company Y were to sue Oil Company X for injuries they sustained from Oil Company X or Oil Company X’s employees negligence. In that suit Drilling Company Y would indemnify Oil Company X from those claims and would be responsible to defend and pay any damages awarded. Over time a number of companies have modified the true “knock for knock indemnity” where they exclude gross negligence or willful misconduct from those indemnities. The problem is when you do that it become similar to comparative negligence in that the parties have to establish those behaviors.

Knock-for-knock indemnities help avoid the cost of litigation that occurs with comparative negligence claims. A comparative negligence claims is one where both parties are sued and the court determines the percentage of negligence that applies to each of the parties. They share the responsibility to pay the damages based upon their percentage of negligence. Knock for knock creates a simple sharing of the risk where each party agrees to be fully responsible for any damages they sustain or that their employees sustain and not look to the other party.

Where a knock-for-knock indemnity doesn’t work or would need to be modified is when the property of a third party is damaged or a third party who is not an employee of either of the parties to the agreement is injured. Those types of claims are outside the scope of the knock-for-knock indemnity. If you failed to address claims by third parties if one party was sued and felt the other party was fully or partially responsible, they would need to enjoin the other company in the law suit and because there was no indemnification relating to third party claims, the court would decide the responsibility for damages. The damages would be apportioned based upon their percentage of negligence that was attributed to the parties.

Having an indemnity doesn’t fully protect a party, especially where it’s a Buyer / Supplier or Prime Contractor /Subcontractor situation Even if the court found the supplier or subcontractor to be 100% of the cause for the negligence, even that may not excuse the buyer or prime contractor from payment. Under the theory of agency, those parties are considered principals and the other company is consider an agent. Principals are liable for the acts of their agents.
So if the Supplier or Subcontractor didn’t have the insurance coverage to cover those damages and didn’t have the assets to make the payments, the principal could be forced to pay the damages.

6 comments:

  1. Would a knock for knock also preclude the two parties from suing each other for breach of contract for property damage? For example, drilling contractor does not perform its work properly, and operator loses the well. If operator sues the driller for losing the well, which is the operator's property, the operator has to indemnify the drilling contractor. So in essence, the drilling contractor is protected from all liability related to operator's property damage.

    ReplyDelete
  2. Armanius, A knock for knock indemnity does not preclude either party suing for breach. What it does do is in the event there is property damage or personal injury, that results for accidental negligence each party is responsible for their own losses and injury to their own people irrespective of which party negligent. If there were specific contract requirements for the drilling and the drilling contractor was not following them, it would not be accidental, it would be deliberate. They would have breached the contract and what the operator could recover for that breach would depend upon what the limitation of liability provides in terms of the types and amounts of damages that may be claimed.

    ReplyDelete
  3. Jack... Is it neccesary to expressly include the wording even when causde by the negligence of the indemnified party if i am writing "regardless of cause" ?

    ReplyDelete
  4. In contract drafting it's not what you call something or the heading you put on a clause, its the words that you use to establish the responsibilities of the parties. There are many types of indemnities and the scope and intent of those are created by the specific wording used. The key aspect in a knock for knock is you want to eliminate arguments about who caused what because each party is working in close proximity of the other. To make it clear that it is a true knock for knock indemnity you need to show the intent that you have agreed to indemnify each other irrespective of what the cause was or who may have caused it. If you don't do that even if you titled the section "knock for knock indemnity" it may not be interpreted as one. Therefore it is best to include those words.

    ReplyDelete
  5. Jack, under english law is it possible to enforce the knock for knock principle even in cases of Gross Negligence (defined) and Willful misconduct if the parties agreed to indemnfy each other?

    ReplyDelete
  6. The post identified the general concept of a knock-for-knock indemnity. I'm not familiar with english law on the subject. However, I could easily envision the parties carving gross negligence or willful misconduct out of the indemnification so that it applies only to ordinary negligence irrespective of who caused it.

    ReplyDelete