What is a Contract: Part 4:
Representations, Warranties, Covenants - The Bones of the Agreement
This is the fourth installment of my continuing blog series explaining the main elements of a contract, which are outlined on the infographic on page 4. My goal is to demystify some of these basic provisions to help business owners have a better general understanding of what they are signing.
This article discusses representations, warranties, and covenants, which are the “bones” of the parties’ agreement. These provisions represent the statements of the underlying facts, mutual assurances, and promises of performance which form the basis of the parties’ mutual understanding. It’s not uncommon to find these concepts used interchangeably in a contract – “ABC represents, warrants, and covenants…”, but the meaning and effect of each of these are quite distinct from one another. It’s important to understand these distinctions so that your contracts accurately reflect the assumptions, obligations, and risks that you are comfortable with.
A representation is a statement of past or present fact (either express or implied) made by one party to induce the other party to enter into the agreement. For example, the seller of a business might represent that gross revenues from the business were a certain dollar amount for the past several years or that there are no claims asserted against the business. If a representation proves to have been untrue when made, the injured party will have a claim of fraudulent misrepresentation if she can prove that: (i) the party making the representation knew or should have known the statement was false when made; (ii) the other party intended the injured party to rely on the statement; and (iii) the injured party’s reliance on the statement in entering into the agreement was justifiable. The injured party can seek monetary damages for its losses or it may ask the court to rescind (void) the entire contract. It is therefore very important to avoid “over-representing” in your contracts.
A warranty is essentially a promise that an assertion made by a party is true, coupled with an implied promise of indemnity if the assertion made by the party is false. As such, a warranty is both present-focused, like a representation, and forward-looking, like a covenant. If a warranty is breached, the injured party is entitled to be made whole; this usually means that the injured party can recover the difference between the value of the contract as agreed upon and the value of the contract in light of the breach. In other words, the injured party is entitled to receive the benefit of the bargain he initially made. The injured party is not required to demonstrate that he relied on the warranty or that the other party knew that the warranty was false when made. Often, but not always, representations and warranties go hand-in-hand to allow the parties to preserve remedies that are as broad as possible. In complex agreements, the parties usually spend a significant amount of time negotiating how the risks embodied by representations and warranties should be allocated by qualifying and limiting these concepts (e.g., a representation is true to the best of the maker’s knowledge and/or in all material respects).
Product and service warranties are specialized contractual provisions that are actually hybrids of representations, warranties, and covenants. These provisions commonly create limited express warranties that apply to the products or services, identify specific contractual remedies for breach, and disclaim implied warranties that are provided by law.
A covenant is a party’s promise to perform an action or to refrain from performing an action. It relates to the future, as opposed to representations, which are provided as of a specific date. An example of a covenant is a borrower’s promise to make loan payments in accordance with the terms of a promissory note. Covenants can be express or implied. Pennsylvania law imposes an implied covenant of good faith and fair dealing in most contracts.
Stay tuned for Part 5 of this series, which will move on to discuss some possible hidden perils of what is commonly dismissed as “just boilerplate” language.