On October 2, 2026, in In Re: Amendments to Florida Rules of Civil Procedure, Case No. SC2026-0170, the Florida Supreme Court declined to adopt a proposed amendment to Rule 1.442 that would have given trial courts an express mechanism to enforce an accepted proposal for settlement. The Court held that an enforcement provision “appear[s] to touch on matters of substantive law” and, for that reason, is not something the Court can add through its procedural rulemaking authority. The Court was clear about what Rule 1.442 is, and is not, for: “The only purpose of Rule 1.442 is to provide a procedural framework to implement the substantive requirements of section 768.79.”
Translated: Florida practitioners who use the rule to resolve a case, and then get stiffed on payment, still do not have a Rule 1.442 remedy. The Court agrees the gap exists. It just says the Legislature has to fill it.
The Problem the Proposal Tried to Solve
The amendment was proposed by former Civil Procedure Rules Committee member Paul Regensdorf and grew out of a real case. A defendant accepted a proposal for settlement, failed to perform on the agreed payment terms, eventually paid only one-third of what was owed, and the trial court declined to enter judgment on the agreement. In Regensdorf’s own words to the Court, “Eventually the defendant paid 1/3. The Judge has so far declined to enter a judgment, DESPITE the fact that the Proposal was also made under 768.79.”
Any Florida litigator who has worked with proposals for settlement has seen some version of this. The accepted proposal looks, functionally, like a settlement. But the moment the obligor stops paying, counsel discovers there is no Rule 1.442 path to force performance. The movant is thrown back on contract law, on a separate breach-of-contract action, on a motion to enforce settlement if the trial court happened to retain jurisdiction, and on the standard list of remedies that any contracting party has when a counterparty defaults. The one tool the rule was designed to deploy, Section 768.79’s fee-shifting mechanism, remains available on paper, but it keys to the offer-rejection math under the statute, not to a post-acceptance breach.
What the Proposed Subdivision (j) Would Have Done
The proposal was short and direct. A new subdivision (j), titled “Enforcement of Accepted Proposal,” would have read:
“After timely acceptance of a proposal, in the event of any breach or failure to perform under the agreement, the court on motion may impose sanctions, including costs, attorneys’ fees, or other appropriate remedies including entry of judgment on the agreement.”
The provision was patterned on Florida Rule of Civil Procedure 1.730(d), which gives trial courts a parallel enforcement power for mediated settlement agreements. Mediated settlements can be enforced by motion in the pending case. Rule 1.442 accepted proposals cannot. That asymmetry is now officially left in place.
Why the Court Said No
The Court’s reasoning turns on the Article V boundary between its procedural rulemaking power and the Legislature’s substantive lawmaking power. A rule that supplies the machinery of a cause of action is procedural. A rule that creates, enlarges, or modifies the underlying right or remedy is substantive. The majority treated the proposed subdivision (j) as creating a new remedial regime, including an entitlement to fees, costs, and entry of judgment on the agreement, that goes beyond providing a procedural vehicle to administer what Section 768.79 already supplies.
The Court’s single-sentence description of Rule 1.442’s role is the most important sentence in the opinion for working lawyers: “The only purpose of Rule 1.442 is to provide a procedural framework to implement the substantive requirements of section 768.79.” That is a jurisdictional and interpretive statement. It tells trial judges to read Rule 1.442 narrowly, to resist invitations to graft new remedies onto it, and to send proponents of substantive relief to the statute instead.
What the Court Did Not Do
Three things are worth naming because practitioners will see arguments built on each in the coming months.
- The Court did not say an accepted Rule 1.442 proposal is unenforceable. It is enforceable. It is a contract. The Court said there is no Rule 1.442 motion to enforce it.
- The Court did not disturb the practice of enforcing settlements through retained jurisdiction. A trial court that enters a dismissal order expressly retaining jurisdiction to enforce the settlement keeps the power to do exactly that. The Court’s opinion does not touch Paulucci v. General Dynamics or the long line of retained-jurisdiction authority.
- The Court did not announce a sanctions prohibition. A party who breaches an accepted proposal still exposes itself to a Section 57.105 motion if its post-breach position is frivolous, to inherent-authority remedies if the breach was accompanied by misconduct, and to Section 768.79 fees in the ordinary course if the rejection-trigger math eventually runs in the offeror’s favor.
What To Do About It (Drafting and Preservation)
The practical response is drafting discipline on the front end and procedural discipline on the back end. Six items belong on every Florida civil practitioner’s checklist going forward.
- Pair every proposal for settlement with a separate written settlement agreement. The proposal and the acceptance operate within Rule 1.442. The separate agreement operates within contract law. The second document is where the enforceable payment terms, default remedies, and fee-shifting live. Serve the agreement, or at a minimum the agreement’s material terms, as an exhibit to the proposal so the acceptance covers both.
- Build default remedies into the written agreement. Include an acceleration clause, a liquidated-damages or stipulated-judgment provision, prevailing-party fees for an enforcement motion, and (where appropriate) a consent to entry of judgment on default. These are substantive terms the Court just said the rules cannot supply, which is exactly why counsel must supply them by contract.
- Insist on retained jurisdiction. Submit a proposed order of dismissal that expressly retains jurisdiction to enforce the settlement agreement for a defined period. This is the single highest-leverage protective step. Without retained jurisdiction, enforcement after dismissal usually requires a new breach-of-contract case.
- If possible, hold the dismissal until payment is made. For short-fuse settlements, do not dismiss on acceptance. Dismiss on receipt of funds. A pending case is a more compliant counterparty than a dismissed one.
- Build in confession-of-judgment or stipulated-judgment language where the client’s risk warrants it. Florida accepts stipulated judgments when properly drafted. In matters where the defendant’s solvency or payment reliability is in doubt, insist on this backstop.
- On breach, choose the right vehicle quickly. If jurisdiction was retained, file a motion to enforce the settlement agreement. If not, file a separate action for breach of contract and, where supported, add Section 57.105 and (if applicable) Section 768.79 claims. Do not try to construct a Rule 1.442 enforcement motion. The Supreme Court has now said twice over what the rule is for, and that is not it.
Where This Goes From Here
The Court’s decision is less an endpoint than a referral. By classifying the problem as substantive, the Court has pointed the bar at the Legislature and, specifically, at Section 768.79. The Florida Bar’s Legislation Committee, the Business Law Section, and the civil-practice sections will almost certainly take up a statutory amendment in the 2027 session. The simplest fix is a short addition to Section 768.79 authorizing a trial court, on motion, to enforce an accepted proposal, award costs and attorneys’ fees incurred in enforcement, and enter judgment on the agreement. Until that fix lands, the drafting and preservation playbook above is the way to close the gap one case at a time.
The Bottom Line
Florida’s highest court looked at a working gap in Rule 1.442, agreed the gap exists, and said the fix is the Legislature’s to make. For now, an accepted proposal for settlement is still a contract, and the enforcement toolbox is the one every commercial litigator already carries: a well-drafted settlement agreement, retained jurisdiction, prevailing-party fees in the agreement, and the willingness to file a motion to enforce or a new breach-of-contract case the moment payment stops coming. Draft like the rule has no teeth, because at least for the time being, it does not.
See also: No More “Unified Claim” Exception: Florida Reinstates Strict Apportionment for Joint Proposals on the Florida Supreme Court’s July 2026 decision in Trace Elements, Inc. v. Mackensen, which tightened the drafting rules on the front end of Rule 1.442 practice.