Lead Opinion
On July 16, 2007, this сourt adopted an opinion in this case. On July 18, 2007, this case was transferred to the Missouri Supreme Court pursuant to Rule 83.03. On August 22, 2007, the Missouri Supreme Court retransferred the case to this court. This court’s original opinion now is readopted.
We consider in this case whether an exculpatory clause is effective, and if so, who can claim its protection.
Plaintiff was injured when she fell two stories while saving herself and her children from a fire that destroyed their apartment building.
Defendants asserted an affirmative defense of release, and eventually moved for summary judgment, based on the exculpatory clause plaintiff read and initialed when she signed hеr apartment lease:
27. WAIVER OF LIABILITY
Lessee hereby agrees that Lessor shall not be liable to Lessee, his family, guests, invitees, servants, or others for injury to or death of any person or pet, nor for loss or damage to property (including the property of Lessee) occurring in or about the Leased Premises from any cause whatsoever, even if the cause or damages or injuries are alleged to be the fault or caused by the negligence or carelessness of the Lessor. /s/DM (Lessee(s) initials) (Language taken from Warren vs. Paragon Technologies Group, Inc.)
Plaintiff cross-moved for a partial summary judgment declaring Paragraph 27 unenforceable. The trial court ultimately granted defendant’s motion for summary judgment and denied plaintiffs cross-motion.
Our review is de novo. ITT Commercial Finance Corp. v. Mid—America Marine Supply Corp.,
Public poliсy disfavors but does not prohibit releases of future negligence. Warren,
Point I — Paragraph 27’s Enforceability
Lease Paragraph 27, titled “WAIVER OF LIABILITY,” releases injury claims at or about the apartment “from any cause whatsoever, even if the cause or damages or injuries are alleged to be the fault or caused by the negligence or carelessness of the Lessor.” Plaintiff, a high school graduate, read the lease before she signed it. She read and initialed, in particular, Paragraph 27’s “WAIVER OF LIABILITY.” Absent other evidence — and plaintiff cites none — this demonstrates the parties agreed upon this release. Warren,
Given these circumstances, Plaintiffs Point I makes a narrow claim. It asserts, as a matter of law, Paragraph 27 is unenforceable because “from any cause whatsoever” does not expressly exclude intentional torts, gross recklessness, or activities involving the public interest. Plaintiff is not claiming the Lessor did not effectively notify her she was releasing it from its own negligence. Alack,
First conversation:
P: I sue you for negligence.
D: You already released me from all future claims, including my own future negligence. Your release of my negligence was clear, conspicuous, and effectively notified you that you were releasing me from future negligence claims. You are suing me for what you clearly and con-*617 spieuously released me from. Your claims are barred.
Second conversation:
P: I sue you for negligence.
D: You already released me from all future claims, including my own future negligence. Your release of my negligence was clear, conspicuous, and effectively notified you that you were releasing me from future negligence claims. You are suing me for what you clearly and conspicuously released me from. Your claims are barred.
P: But my release doesn’t mention assault.
D: I didn’t assault you. You’re not suing me for assault. Assault doesn’t matter.
P: Yes it does. My suit is for the negligence from which I clearly and conspicuously released you. But my release of “all” claims is silent about assault, and assault can’t be released, so my release is automatically “ambiguous” and unenforceable. You didn’t assault me, nor am I suing you for assault, but that makes no difference. A release of “any” or “all” claims that is silent about assault is legally unenforceable, even against the negligence claims it clearly and conspicuously releases.
The first conversation represents the trial court’s basis for summary judgment. The second illustrates plaintiffs Point I. Plaintiff cites as support passages from Alack and Lewis v. Snow Creek, Inc.,
Alack
Alack’s principal and dissenting opinions focused almost exclusively on enforceability of its future negligence release. See
Sectiоn 1, citing Missouri cases, reiterated that exculpatory clauses are not prohibited by our public policy, but are disfavored, never implied, and must be clearly and explicitly stated. Clear and explicit language is required to absolve a person from future negligence, and is strictly construed against the party claiming its benefit. Id. at 334 (citations omitted).
Section 2 examined decisions of our sister states, most of which “have enforced exculpatory clauses when they include specific references to the negligence or fault of the drafter.” Id. The court cited Minnesota, Maine, North Dakota, and Delaware cases, and considered at greater length Texas and New York opinions, to the effect that exculpatory clauses must expressly mention the drafter’s negligence or fault. Id. at 334 — 35. Section 2 also cited minority-view cases, including those holding that “any” and “all” language alone сan be sufficient without specifically mentioning “negligence.” Id. at 335 — 36.
Section 3 returned to Missouri cases. “Historically, Missouri appellate courts have required that a release from one’s own future negligence be explicitly stated.” Id. at 336. The court cited six examples, but focused on Vergano v. Facility Management of Missouri, Inc., 895 S.W.2d
Section 4 began by summarizing the lessons of sections 1 — 3:
We are persuaded that the best policy is to follow our previous decisions and those of other states that require clear, unambiguous, unmistakable, and conspicuous language in order to release a party from his or her own future negligence. The exculpatory language must effectively notify a party that he or she is releasing the other party from claims arising from the other party’s own negligence. Our traditional notions of justice arе so fault-based that most people might not expect such a relationship to be altered, regardless of the length of an exculpatory clause, unless done so explicitly. General language will not suffice.
Id. at 337. This announced no new law. Nor did these pronouncements, or to our knowledge the cases cited in sections 1 — 3, suggest plaintiffs Point I argument, let alone elevate it to equal billing with Alack’s future negligence analysis.
Alack’s mention of ambiguity was in reply to defendant Tanny’s claim that its clause was adequate (Id.), basically arguing the minority view that “any” or “all” covers negligence without using that word or its equivalents. “Any” and “all” seem unambiguous and all-encompassing, but not so under the law governing exculpatory clauses. The court perceived a “latent ambiguity” since Tanny’s clause, while extensive, did not specifically release Tanny’s negligence. Id. The court illustrated its point with other claims (intentional torts, gross negligencе,
a bright-line test ... certain to alert all involved that the future ‘negligence’ or ‘fault’ of a party is being released. The words ‘negligence’ or ‘fault’ or their equivalents must be used conspicuously so that a clear and unmistakable waiver and shifting of risk occurs.
Id. This would leave “no doubt that a reasonable person agreeing to an exculpatory clause actually understands what future claims he or she is waiving.” Id. at 337 — 38. The court mentioned nothing in this bright-line test or its purpose that supports plaintiffs Point I. The court’s remedy, even if Tanny’s clause had several
Alack’s approval of Vergano and Hom-beck strengthens this conclusion. Both cases involved “any” and “all” language that plaintiff claims Alack condemns, but Vergano’s clause mentioned “negligence” and Hombeck’s did not. Vergano,
Lewis and Warren
Although Alack is the principal case, we will briefly address Lewis, Warren, and the parties’ overbroad readings of each.
Lends is somewhat unusual, in that the court declined to consider whether the exculpatory language operated as a release, since the defendant ski resort never pleaded that defense.
10. I hereby release from any legal liability the ski area and its owners, agents and employees, as well as the manufacturers and distributors of this equipment frоm any and all liability for damage and injury or death to myself or to any person or property resulting from the selection, installation, maintenance, adjustment or use of this equipment and for any claim based upon negligence, breach of warranty, contract or other*620 legal theory, accepting myself the full responsibility for any and all such damage, injury or death which may result.
Under these circumstances, the Lewis court deemed the exculpatory clause language and format neither unambiguous nor conspicuous, and thus insufficient under Alack to establish an express assumption of risk of ice defense. Id. at 395. We agree with this result, which is fully consistent with Alack. The Lewis clause mentioned “negligence” and arguably met Alack’s bright-line rule. But five-point type is barely readable, let alone clear, conspicuous, unmistakable, or effective to notify ski renters they were releasing the resort from its own negligence. The ambiguity discussion was unnecessary to the holding, and Lewis does not say a clause can satisfy Alack’s future negligence requirements, yet automatically fail under plaintiffs Point I reasoning.
While plaintiff reads Lewis too broadly, defendants do likewise with Warren. Judge Robertson persuasively argued for that clause’s ultimate validity (
Analysis
Our analysis yields two conclusions relevant to Plaintiffs Point I. First, Alack’s analysis culminates in its essential holding that “exculpatory language must effectively notify a party that he or she is releasing the other party from claims arising from the other party’s own negligence.”
Plaintiff has not convinced us of a second bright-line rule akin to Point I and our second hypothetical conversation above. Paragraph 27 met Alack’s bright-line rule. Its release clearly, unambiguously, unmistakably, and conspicuously applied “even if the cause or damages or injuries are alleged to bе the fault or caused by the negligence or carelessness of the Lessor” (emphasis ours). It effectively notified plaintiff she was releasing the Lessor from claims arising from its negligence, and thus met Alack’s bottom-line standard as well. Point I fails.
Point II — Paragraph 27’s Scope
Plaintiffs Point II notes that Paragraph 27 releases only the “Lessor.” She claims McCormack is neither the “Lessor” nor a third party beneficiary of the lease, and thus cannot claim the clause’s protection. We consider McCormack’s three counterarguments out of order.
Can McCormack enforce the clause as a party ?
McCormack claims it is the (or at least a) Lessor; thus a party to the lease; and in turn entitled to Paragraph 27’s protection. However, the lease is ambiguous about who the “Lessor” is. Paragraph 1 of the lease describes the parties as:
McCormack Baron Ragan Management Services, Inc. as agent for Chesterfield Village Apartments hereinafter referred to
(Property Name)
as “Lessor” whose address is 2310 W. Chesterfield Bind, and Deanna Milligan, who is (are) jointly and severally responsible under this Lease, hereinafter referred to as “Lessee.”
Paragraph 2 ties the leased premises to paragraph l’s address for “Chesterfield Village Apartments” and “Lessor.” We think the best interpretation has Chesterfield as Lessor, and McCormack acting as agent for a disclosed principal and thus not itself a party to the lease. It is fundamental that an agent signing a contract on behalf of a disclosed principal binds only the principal but not the agent itself, absent clear and explicit evidence that the agent also intended to be bound. See, e.g., Professional Laundry Management Systems, Inc. v. Aquatic Technologies, Inc.,
The lease evinces no intent to bind or benefit McCormack as a contracting party. To the contrary, Paragraph 1 expressly identifies McCormack as “agent” for the disclosed principal Chesterfield. Paragraph 1 also uses “jointly and severally” with the singular term “Lessee” to accommodate multiple persons, but eschews comparable language for its singular term “Lessor.” Paragraph 25 does not mention “agents” as persons to be bound and benefited by the agreement. Paragraph 27’s exculpatory language easily could have included “and agents,” but it does not. The lease language does not indicate the agent McCormack is individually obligated. If not, McCormack cannot claim lease benefits unless it is a third-party beneficiary, a claim McCormack has not made. To be a third-party beneficiary, the contact must clearly express intent to benefit that party or an identifiable class to which the party belongs. Absent express declaration of such intent, it is strongly presumed that the third party is not a beneficiary and the рarties contracted only to benefit themselves. Nitro Distributing, Inc. v. Dunn,
Is McCormack released by operation of law?
Next, McCormack argues release of a master also releases its servant, citing Max v. Spaeth,
Did plaintiff admit herself out of a claim against McCormack?
McCormack claims plaintiff cannot deny Paragraph 27 protects McCormack because she admitted entering the lease with defendants. We consider this a non sequi-tur. Uncontroverted fact No. 1 in defendants’ summary judgment motion asserted that plaintiff entered a lease agreement with defendants and a copy of the lease was attached. Rule 74.04(c)(2) required plaintiff to “admit or deny each of mov-ant’s factual statements,” and plaintiff admitted the facts as to No. 1.
An agreement to release one person’s tort liability discharges no other tort-feasor unless the agreement so provides. RSMo § 537.060. This “operates to preclude the unintended release of persons liable in tort.” Manar,
Point II is well taken. On this record, Paragraph 27 does not preclude plaintiffs claims against McCormack.
Conclusion
We affirm the judgment for Chesterfield. We reverse the judgment for McCormack and remand those claims for proceedings consistent with this opinion.
Notes
. A neighbor perished in the blaze. Her death is the subject of a companion case, Kaufold v. Chesterfield Village GP, LLC, et al, # 28178,
. The court initially granted plaintiffs motion and denied defendants’ motion. Defendant sought reconsideration and the court reversed its rulings.
. Less precise language may be effective between businesses of equal powеr and sophistication. Alack,
. Our supreme court did not quote Warren’s exculpatory clause in its opinion. Warren is the subject of Karen A. Read, Note, Public Policy Violations or Permitted Provisions?: The Validity of Exculpatory Provisions in Residential Leases, 62 Mo. L.Rev. 897 (Fall 1997), which purports to cite the clause.
. Our general tort law does not recognize degrees of negligence. Tendai v. Bd. of Reg. for Healing Arts,
. Indeed, Alacies approval of Vergano, and the supreme court’s prima facie approval of Warren's clause one year after Alack, may lend credence to the Alack dissenters’ contention that the majority’s “latent ambiguity” discussion was:
not talking about an ambiguity at all. The general rule of law that courts will properly refuse to give effect to exculpatory clauses for intentional torts is not a rule governing interpretation and construction. It is part of the substantive law of contracts. "[A] rule of law which forbids effect being given to that [clear] meaning is part of the substantive law of contracts which comes into play after interpretation and construction have finished their work." 4 Williston on Contracts, § 602 (3d ed.). Thus, courts refuse to enforce such exculpatory clauses not on the basis of ambiguity and not as a matter of contractual interpretation or construction, but as a matter of public policy.
Alack,
. That said, even Alack’s dissenters expressed strong personal and policy concerns with exculpatory clauses in a health club contract.
. "Max v. Spaeth ... includes dicta that ‘release of the master releases the servant.’ We need not determine whether that dicta correctly states the law in Missouri in cases involving vicarious liability.” Id.
Concurrence Opinion
dissenting in part and concurring in part.
I respectfully dissent from the majority’s opinion that Paragraph 27 is unambiguous, but concur in the majority’s opinion that Paragraph 27 does not preclude Appellant’s claims against McCormack. In light of Lewis v. Snow Creek, Inc.,
On October 6, 2004, while Deanna Milli-gan (“Appellant”) was a tenant living on the second floor of an apartment building owned by Chesterfield Village GP, LLC, d/b/a Chesterfield Village Apartments, LP (“Respondent”), the building was destroyed by a fire and she was injured when she fell to the ground while trying to save herself and her two children by escaping her second-story apartment through a bedroom window. Appellant was forced out her window by the fire because, two days before, the breezeway between her apartment and the exit route became blocked with boxes and other materials from a new tenant. These boxes were not moved for the two days before the fire and completely blocked ingress and egress until the time of the fire. Appellant alleges that these boxes and other packing material not only blocked her escape route, but also that they contributed to the cause of the
The majority opinion finds the exculpatory clause was not ambiguous based upon the “test” adopted by the Missouri Supreme Court in Warren v. Paragon Technologies Group, Inc.,
Based upon these two alternative holdings, the majority states that the “ambiguity discussion was unnecessary to the holding, and Lewis does not say a clause can satisfy Alack’s future negligence requirements, yet automatically fail under plaintiffs Point I reasoning.” In fact, that is exactly what Lewis stated. Its first holding is that the general language in the exculpatory clause, specifically, that it purports to exonerate future liability for “any claim” including a claim which one may never exonerate future liability for, makes it ambiguous. Id. at 394. The fact that its alternative second holding is that the exculpatory clause is also invalid because it was not conspicuous does not render its other holding meaningless.
When there are alternative holdings each is authoritative. Woods v. Interstate Realty Co.,
It is well settled that when a court bases its decision on two or more distinct grounds, each is as authoritative as the other and neither is obit[e]r dictum. This rule is the оnly reasonable inference to be drawn from alternative holdings. Unless all the alternatives are to be considered authoritative, how is one to pick which is the rule of law and which is dictum?
Holt,
Based upon Lewis and Alack, I would find the exculpatory clause in Paragraph 27 of the lease to be ambiguous as the release purports to absolve the landlord of all actions intended and unintended. We look to the lease contract principles to determine whether the contract is ambiguous. An ambiguity arises when, from the four corners of the contract alone, it appears that “ ‘the terms are susceptible of more than one meaning so that reasonable persons may fairly and honestly differ in their construction of the terms.’ ” Eveland v. Eveland
27. WAIVER OF LIABILITY
Lessee hereby agrees that Lessor shall not be liable to Lessee, his family, guests, invitees, servants, or others[2 ] for injury to or death of any person or pet, nor for loss or damage to property (including the property of Lessee) occurring in or about the Leased Premises from any cause whatsoever, even if the cause or damages or injuries are alleged to be the fault or caused by the negligence or carelessness of the Lessor.
As a reviewing court, this Court must determine, solely from the four corners of the contract, whether this provision is susceptible to more than one meaning, and is therefore ambiguous. Seeck v. Geico Gen. Ins. Co.,
Through hypothetical, the majority opinion illustrates its view that the exculpatory provision cannot be ambiguous because Appellant’s only claim is that of negligence and there is no ambiguity with regards to negligence. What the majority fails to accomplish, however, is a proper review of this contract’s construction. As previously stated, the terms of a contract are reviewed first, within the four corners for ambiguities. Then, where, as here, ambiguities are present, the court should look
This case clearly illustrates the fact that if you start at the end you will, of course, be able to identify one clear meaning; however, a proper review of contract construction is meant to start at the beginning and make sure there is only one path to the end result. Interpreting this contract from beginning to end reveals that the “waiver of liability” provision is subject to more than one meaning and is therefore ambiguous.
The Warren court adopted the ambiguity test directly from Alack, which dealt with an exculpatory clause in a health club membership. The Alack court was presented with the question of whether or not the specific exculpatory clause in question was ambiguous. Alack,
Covenants that relieve parties of future negligence are not void 'per se as against public policy, yet this rule does not apply in cases involving gross negligence, fraud, unequal bargaining power, or a public interest. Kansas City Stock Yards Co. v. A. Reich & Sons,
Missouri courts have chosen to review the validity of exculpatory clаuses through a strict review of the language involved. As mentioned previously, the intention to release one from his or her negligent acts must be clearly expressed in plain terms that are “clear, unambiguous, unmistakable, and conspicuous.” Even more specifically, the Missouri Supreme Court chose to require the words “negligence,” “fault,” or an equivalent to be used in the exculpatory clause. A different approach has come from those states which have recognized that the use of exculpatory clauses necessarily challenges the principles of freedom to contract and common law requirements that a person be accountable for their own bad acts. See e.g. Stanley v. Creighton Co.,
While many other approaches exist, it is possible to reassess this topic within the confines of established Missouri law. Here, the basis for allowing the use of exculpatory clauses in residential leases stems from the idea thаt residential leases are essentially private contracts; however, it is unrealistic to ignore the present day realities of the landlord-tenant relationship. There is rarely a negotiation in a private residential lease where bargains and concessions occur until an agreement is reached. A tenant does not negotiate to pay more and bargain for extra protection from his landlord’s negligence. See Crawford,
We no longer live in an era of the occasional rental of rooms in a private home or over the comer grocery. In the relatively short span of 30 years the*628 publiс’s use of rental units in this state has expanded dramatically. In the past 10 years alone, in the state of Washington, there has been an increase of over 77,000 rental units. It takes no imagination to see that a business which once had a minor impact upon the living habits of the citizenry has developed into a major commercial enterprise directly touching the lives of hundreds of thousands of people who depend upon it for shelter.
Thus, we are not faced merely with the theoretical duty of construing a provision in an isolated contract specifically bargained for by [o]ne landlord and one tenant as a purely private affair[ ]. Considered realistically, we are asked to construe an exculpatory clause, the generalized use of which may have an impact upon thousands of potential tenants.
McCutcheon v. United Homes Corp.,
It takes no imagination to see that, when a tenаnt signs a lease, he has become vulnerable to the carelessness of the landlord, the person who is literally charged with the protection of the roof over a tenant’s head. By allowing exculpatory clauses to save landlords from responsibility from their own negligence, we are putting tenants at risk. See Lewis v. Biegel,
Before this Court relieves landlords of their long-held obligation to use reasonable care, a meaningful review of the various
(1) where the landlоrd had superior knowledge of a dangerous condition not discoverable by his tenant and he fails to warn of said condition; (2) where the injury occurs in an area over which the landlord retains actual control; (3) where the landlord is responsible for premises maintenance and repair or (4) where the landlord leases for a “public use” premises that are in a dangerous condition.
Lammert v. Leseo Auto Sales,
“[Tjhere is no question that one may never exonerate oneself from future liability for intentional torts or for gross negligence, or for activities involving the public interest.” Alack,
. This case is different from Lewis because here the issue is whether the exculpatory clause operated as a release of liability and in Lewis the issue was whether the exculpatory clause established an express assumption of risk; however, the analysis as to the validity of the exculpatory clause remains the same in each circumstance.
. The grossly overbroad scope of this waiver is apparent from its attempt to exclude liability to "family, guests, invitees, servants, or others” via a contract to which they are not parties and, in all likelihood, is unknown to them.
