SETTLEMENT AGREEMENTS AND CONTRACTS REQUIRE A MEETING OF THE MINDS

A settlement agreement does not need to be executed for it to be enforceable as long as there was a MEETING OF THE MINDS.  The same rings true for any contract regardless of whether the contract is signed – THERE NEEDS TO BE A MEETING OF THE MINDS.

In a recent case dealing with the settlement agreement on a construction lien, the essential settlement terms (money and mutual release) were memorialized in an e-mail exchange between the parties (owner and subcontractor). The settlement required the owner to pay the principal amount plus some attorney’s fees and then a mutual general release would be prepared. In response to the confirmatory email, the owner sent a check, which the subcontractor deposited, but the owner refused to sign the release signed and sent by the subcontractor. The owner further claimed it doesn’t need to pay the attorney’s fees because the lien amount was paid in full. The subcontractor sued arguing the owner breached the terms of the settlement. The appellate court agreed.

The law of contracts governs settlements.  “To form a binding contract there must be an offer and acceptance.”  “[A]n acceptance must contain an assent — or meeting of the minds — to the essential terms contained in the offer.”  “The making of a contract depends not on the agreement of two minds in one intention, but on the agreement of two sets of external signs — not on the parties having meant the same thing but on their having said the same thing.”  “There must therefore be an objective manifestation by both parties of assent to the same terms.” 

We find that a valid and enforceable settlement exists between the parties because there was “an objective manifestation by both parties of assent to the same terms.”  The parties “said the same thing” and agreed to all essential elements — which includes use of a mutual general release.  The [owners] objectively demonstrated their assent in several ways: not objecting to the settlement confirmation email, sending the check in the negotiated amount, and replying “ok, thanks, will have to you tomorrow” to the email with the proposed release. [The owner’s] testimony on his subjective intent and state of mind does not overcome these objective, external signs. 

Adonel Concrete Corp. v. Furshman, 51 Fla. L. Weekly D1292c (Fla. 3d DCA 2026) (internal citations omitted).

 

Please contact David Adelstein at dadelstein@gmail.com or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.

 

RELEASE LANGUAGE EXTENDED TO SUCCESSOR ENTITY BUT ONLY COVERED “KNOWN” CLAIMS

A recent case contains valuable analysis that has impact on whether a “successor” entity will be bound by a settlement agreement it was not a direct party to.  This case contains arguments for contractors that can be raised in a number of different contexts if it is sued by a successor or related entity.  

 

The same case discusses the difference between releasing a party for “known” claims without releasing the same party for “unknown” claims.  This is an important distinction because unknown claims refer to latent defects so a release that only releases a party for known claims is not releasing that party for latent defects.

 

 

In MBlock Investors, LLC v. Bovis Lend Lease, Inc., 44 Fla. L. Weekly D1432d (Fla. 3d DCA 2019), an owner hired a contractor to construct a project.  At completion, the owner transferred the project to an affiliated entity (collectively, the “Owner”).  The contractor sued the Owner for unpaid work, the Owner claimed construction defects with the work, and a settlement was entered into that released the contractor for KNOWN claims.  Thereafter, the Owner defaulted on the construction loan and agreed to convey the property through a deed in lieu of foreclosure to an entity created by the lender (the “Lender Entity”). 

 

The Lender Entity sued the contractor for construction defects – in negligence (negligent construction) and a violation of Florida’s building code.   The contractor argued that such claims should be barred by its settlement agreement with the Owner.  There were two driving issues:

 

First, did the settlement agreement with the Owner extend to the Lender Entity because the Lender Entity was a successor entity to the Owner?  

 

Second, even if the Lender Entity was a successor entity to the Owner, were the construction defects latent defects because the settlement agreement only provided a release of KNOWN (or patent) defects?

 

As to the first issue, the appellate court held that the Lender Entity was a successor entity to the Owner. 

 

[I]t is rather clear that [Lender Entity] is in fact, [Owner’s] ‘successor’ for purposes of the settlement agreement with [contractor] because [Lender Entity] took over the Property and all of [Owner’s] rights with regard to the Property.  Thus, [Lender Entity] clearly met the privity requirement for the application of res judicata in this case: it has a mutual or successive relationship to the same right that [Owner] had when it settled with [contractor]: a reduction in the amount owed to [contractor] for its services in exchange for releasing [contractor] from any claims of construction defects as provided for in the [settlement agreement].

 

As to the second issue, and really the driving issue whether or not the Lender Entity was a successor, was whether the release even protected the contractor from the types of construction defect claims sought.   This is a question of fact because the settlement agreement only included a release of “known” claims and did NOT release the contractor for “unknown” claims, i.e., latent defects.    Hence, the Lender Entity will establish such claims were unknown or could not reasonably have been discovered at the time of the settlement (a latent defect).  The contractor will try to argue otherwise creating an issue of fact as to whether the settlement agreement released the contractor for the construction defects the Lender Entity is asserting.

 

 

Please contact David Adelstein at dadelstein@gmail.com or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.