Florida Requires Apportionment in All Joint Proposals for Settlement—even for a Unified Single Claim

Trace Elements, Inc. v. Nadja Mackensen (Fla. July 2, 2026) (Muñiz, J.)

1) Introduction

This Supreme Court of Florida decision resolves a direct inter-district conflict over the scope of Florida Rule of Civil Procedure 1.442(c)(3), which provides that “[a] joint proposal must state the amount and terms attributable to each party.” The core question was whether that apportionment requirement can be bypassed when multiple plaintiffs assert what an appellate court labeled a “unified, single claim.”

The parties were:

• Petitioner: Trace Elements, Inc., a professional design company.
• Respondents: Wolfgang and Nadja Mackensen, a married couple who contracted with Trace Elements to oversee renovations of their vacation rental property.

After Trace Elements terminated performance, the Mackensens sued for breach of contract and unjust enrichment; Trace Elements countersued for breach of contract and tortious interference with a business relationship. Before trial, the Mackensens served a single lump-sum proposal for settlement of $10,000 to resolve all claims and counterclaims. Trace Elements rejected the proposal. The jury later awarded the Mackensens $41,273.70 on breach of contract; Trace Elements recovered nothing on its competing contract claim, and a directed verdict was granted against its tortious interference claim.

The fee dispute that followed required the Court to decide whether the Mackensens’ unapportioned joint proposal (made by two plaintiffs) could support fee shifting under section 768.79, Florida Statutes, and rule 1.442.

2) Summary of the Opinion

The Court quashed the Fourth District’s decision in Mackensen v. Trace Elements, Inc., 388 So. 3d 815 (Fla. 4th DCA 2024), and approved Cobb v. Durando, 111 So. 3d 277 (Fla. 2nd DCA 2013), to the extent consistent with its decision.

It held:

Rule 1.442(c)(3) requires apportionment of a joint proposal even when the proposal concerns a “unified, single claim.”

Because the Mackensens’ proposal was a joint proposal (two distinct plaintiffs) and did not allocate an amount “attributable to each party,” it was invalid. Therefore, the trial court correctly denied fees under section 768.79, and the Fourth District erred by creating an ad hoc exception for unified claims.

3) Analysis

3.1 Precedents Cited (and How They Shaped the Holding)

(a) Strict enforcement of apportionment for any “joint proposal”

• Willis Shaw Express, Inc. v. Hilyer Sod, Inc., 849 So. 2d 276 (Fla. 2003): The Court treated “joint proposal” as a proposal “made by or to multiple parties” and enforced the textual requirement that multi-offeror proposals must apportion. This decision supplies the definitional baseline: “joint” is triggered by party multiplicity, not by claim structure.
• Lamb v. Matetzschk, 906 So. 2d 1037 (Fla. 2005): The Court required apportionment even where one defendant’s liability was “purely vicarious,” rejecting practicality-based arguments and emphasizing the rule “makes no distinction” based on theories of liability.
• Pratt v. Weiss, 161 So. 3d 1268 (Fla. 2015): The Court reiterated that even where liability may be “coextensive,” this is “not an exception to the apportionment requirement,” stating: “Even where no logical apportionment can be made, it is nonetheless required where more than one offeror or offeree is involved.”
• Audiffred v. Arnold, 161 So. 3d 1274 (Fla. 2015): The Court invalidated a proposal involving additional parties/claims not properly resolved by compliant proposal terms, reinforcing formal compliance as the operative test.

(b) Apportionment as implementing a statutory “substantive requirement”

• Att'ys' Title Ins. Fund, Inc. v. Gorka, 36 So. 3d 646 (Fla. 2010): The Court described section 768.79 as a sanction and stated rule 1.442 provides the method to implement the substantive right. It tied apportionment to § 768.79(2)(b)’s requirement to “name the party making it and the party to whom it is being made,” reasoning from the statute’s use of “party” in the singular and relying on Allstate Indem. Co. v. Hingson, 808 So. 2d 197 (Fla. 2002).
• Kuhajda v. Borden Dairy Co. of Ala., LLC, 202 So. 3d 391 (Fla. 2016): The Mackensens relied on Kuhajda, but the Court distinguished it because Kuhajda excused noncompliance with a different rule subsection (rule 1.442(c)(2)(F) on attorney’s fees) precisely because that requirement did not implement a substantive requirement of § 768.79. By contrast, Kuhajda itself recognized that cases like Willis Shaw, Gorka, Lamb, and Pratt involve strict enforcement where the rule implements § 768.79’s substantive requirements—placing apportionment squarely in the “strict compliance” category.

(c) Direct conflict authorities and reaffirmation

• Cobb v. Durando, 111 So. 3d 277 (Fla. 2nd DCA 2013): The Second District held an unapportioned joint proposal by married homeowners on a “unified, single breach of contract claim” was invalid. This is the decision the Supreme Court approves.
• Mackensen v. Trace Elements, Inc., 388 So. 3d 815 (Fla. 4th DCA 2024): The Fourth District created the “unified, single claim” exception to apportionment; the Supreme Court rejects that approach as inconsistent with the rule’s text and the Supreme Court’s apportionment jurisprudence.
• Watkins v. Corbett, 2026 WL 816637 (Fla. 2d DCA Mar. 25, 2026): Cited to show the Second District’s continued rejection of the “tenants by the entireties / impractical apportionment” argument.

(d) “Strict compliance” is the test, not “no ambiguity”

• R.J. Reynolds Tobacco v. Ward, 141 So. 3d 236 (Fla. 1st DCA 2014): The Court quoted Ward for the proposition that the Supreme Court’s test is strict compliance, not merely absence of ambiguity—undercutting the Mackensens’ “our proposal was clear” defense.

(e) Policy backdrop: § 768.79 as a penalty statute

• Coates v. R.J. Reynolds Tobacco Co., 365 So. 3d 353 (Fla. 2023): Cited for the characterization of section 768.79 as a “penalty statute,” reinforcing the Court’s insistence on predictable, consistent, strict rule application.

(f) Institutional preference for rule amendment over judicial “exceptions”

• In re Amends. to Fla. Rules of Civ. Proc., 52 So. 3d 579 (Fla. 2010): Used as an example of the Court addressing perceived overbreadth through formal amendment (after Lamb, adopting rule 1.442(c)(4)), rather than case-specific carveouts.
• Fox Valley & Vicinity Constr. Workers Pension Fund v. Brown, 897 F.2d 275 (7th Cir. 1990) (Easterbrook, J., dissenting): Cited for the rules-versus-standards tradeoff: rules sometimes yield hard outcomes, but legislatures (and by analogy rulemakers) choose that regime for predictability and administrability.

3.2 Legal Reasoning

The Court’s reasoning is openly textual and administrability-driven:

• Text controls: Rule 1.442(c)(3) states, without qualification, that “[a] joint proposal must state the amount and terms attributable to each party.” The Court treats “joint proposal” as a term of art that depends on the number of parties, not on whether the claim is “unified.”
• No extra-textual exception: The Fourth District’s “unified, single claim” exception is described as an ad hoc creation not grounded in the rule’s text.
• Precedent demands strict enforcement: The Court emphasizes that across “myriad factual scenarios,” it has never made apportionment depend on relationships, liability theories, or claim structure.
• Predictability over case-by-case equity: The Court prefers a clear, ex ante drafting rule that parties can rely on, rather than litigating whether a particular proposal “should” be exempt because apportionment seems “nonsensical.”
• Procedural rule as statutory implementation: Because apportionment implements § 768.79(2)(b), noncompliance is not treated as a harmless technicality.

Notably, the Court rejects two common defenses:

• “But it was unambiguous”: clarity does not cure noncompliance under the Court’s strict-compliance framework.
• “But apportionment is impractical (tenants by the entireties, unified damages)”: impracticality is not a recognized basis to “disregard or circumvent” the rule.

3.3 Impact

(a) Drafting consequences (immediate and concrete)

• Married couples and other co-plaintiffs must apportion even when suing on a single contract, seeking an undivided damage recovery, or owning property as tenants by the entireties.
• “Unified claim” proposals are now squarely unsafe unless they assign a stated amount (and any terms) to each offeror/offeree.
• Fee exposure becomes more predictable: the decision favors bright-line administrability over litigation about “functional unity.”

(b) Litigation-system effects

• More proposals will be rejected/defeated on formal grounds if parties continue using lump-sum joint proposals—reinforcing Florida’s reputation for technical offer-of-judgment disputes.
• Rulemaking pressure increases: the majority expressly signals that any “flaw” is better addressed by amending rule text, echoing the post-Lamb amendment path.

(c) Doctrinal consolidation

• The Court reaffirms that rule 1.442(c)(3) is treated as implementing a substantive statutory requirement, so courts are unlikely to excuse noncompliance through purposive interpretation (as was possible in Kuhajda for a different subsection).

4) Complex Concepts Simplified

• Section 768.79 (offer of judgment / demand for judgment): A fee-shifting mechanism. If a qualifying offer is rejected and the rejecting party later does sufficiently worse at trial (e.g., plaintiff beats its offer by at least 25%), the offeror can recover attorney’s fees and costs from the offer date—unless the offer was not made in good faith.
• Rule 1.442: The procedural rule that sets the required form/content for settlement proposals under § 768.79.
• Joint proposal: A proposal made by or to more than one party (multiple offerors or multiple offerees).
• Apportionment requirement: When a proposal is joint, it must specify the amount (and terms) “attributable to each party”—i.e., it must break down the lump sum by person/entity, rather than offering only one global number.
• Strict compliance: Florida courts often require technical adherence to rule 1.442’s content requirements; a proposal can be invalid even if its meaning is clear, because the fee-shifting statute is treated as penal and the rule is applied predictably.
• “Quash” vs. “approve”: To “quash” is to nullify the lower appellate decision under review; to “approve” is to endorse another court’s decision (here, Cobb v. Durando) as consistent with the Supreme Court’s rule.

5) Note on the Dissent

Justice Sasso’s dissent argues that this case is meaningfully distinct because the Mackensens are a “legally recognized unit” and sought undifferentiated damages, so apportionment serves no evaluative purpose. The dissent also criticizes the doctrinal basis for “strict construction” of procedural rules and cites authorities on stare decisis and holdings versus dicta, including State v. Yule, Pedroza v. State, Cusick ex rel. Cusick v. City of Neptune Beach, and Forman v. Fla. Land Holding Corp., as well as tenancy-by-the-entireties doctrine from Beal Bank, SSB v. Almand & Assocs.. It further notes later statutory/rule developments and points to cases like Wheaton v. Wheaton and procedural principles reflected in Fla. R. Civ. P. 1.010. The majority, however, declines to recognize a “unified claim” exception and channels any reform into rule amendment rather than adjudicative carveouts.

6) Conclusion

Trace Elements, Inc. v. Nadja Mackensen establishes (and reaffirms) a firm rule: apportionment under rule 1.442(c)(3) is mandatory for any joint proposal, even when multiple parties assert a unified, single claim and even when apportionment feels impractical. The decision prioritizes predictable administration of a penal fee-shifting regime over case-specific notions of fairness or common sense, and it signals that any softening of the apportionment requirement must come through formal rule amendment—not judicial exceptions.