How to calculate Offer Of Judgment Analyzer in Florida

Quick takeaways

• Florida’s Offer of Judgment cost/fee-shifting framework is governed by Fla. Stat. § 768.79 and is triggered in civil actions for damages when a defendant files an offer of judgment.
• If the plaintiff does not accept within 30 days, the defendant may recover “reasonable costs and attorney’s fees” that are incurred “from the date of filing” the offer. (See Fla. Stat. § 768.79(1).)
• For a calculator like DocketMath’s Offer Of Judgment Analyzer (US-FL), your core job is to:

  • compare the plaintiff’s final recovery to the offer amount using consistent damage math, and
  • estimate the fee/cost exposure based on the post-offer time period (because the statute ties recovery to fees/costs incurred from the offer filing date).
• Default timing rule: Florida uses the 30-day acceptance window described in § 768.79(1) for the general offer mechanism (no claim-type-specific sub-rule was identified in the provided statute text—so treat 30 days as the default).

Inputs you need

Before you use the Offer Of Judgment Analyzer (US-FL), gather the specific numbers the tool uses to model Florida outcomes under Fla. Stat. § 768.79.

A. Case + offer basics

• Jurisdiction: Florida (US-FL)
• Offer date (used to align the “from the date of filing the offer” concept)
• Offer amount (the $ figure stated in the offer of judgment)

B. Damages and ultimate recovery

• Plaintiff’s final recovery (or projected recovery)

  • This is the number you’ll compare against the offer amount logic in the analyzer.
• Pre-judgment interest included? (Yes/No + amount if you track it separately)
• Costs tracked separately? (if your workflow or the tool models costs outside “damages”)

C. Fees and costs inputs (for estimating exposure)

Because § 768.79 uses the phrase “reasonable costs and attorney’s fees”, the analyzer commonly needs fee/cost inputs focused on the period after the offer is filed.

Practical inputs to collect:

• Attorney hourly rates (or a fee estimate)
• Post-offer hours (hours incurred after the offer filing date)
• Reasonable fees estimate for the post-offer period (if the tool accepts a total rather than hours)
• Taxable costs estimate after the offer date (optional; depends on how your setup models “costs”)

D. Acceptance and timing (critical)

• Was the offer accepted within 30 days?

  • If yes, § 768.79’s non-acceptance-triggered cost/fee-shifting mechanics you’re modeling may not apply in the same way.
  • If no, proceed with the calculator’s § 768.79 comparison/exposure logic.

Florida’s default trigger depends on the 30-day non-acceptance window in § 768.79(1):

• “if a defendant files an offer of judgment which is not accepted by the plaintiff within 30 days…”

Tip: Many “wrong result” scenarios come from entering an acceptance flag that doesn’t match the actual 30-day timeline.

How the calculation works

DocketMath’s Offer Of Judgment Analyzer (US-FL) is best thought of as a structured comparison model that uses the core ideas of Fla. Stat. § 768.79(1):

1. confirm whether the 30-day non-acceptance condition applies,
2. compare final recovery versus the offer amount under the analyzer’s “who beats the offer” logic, and
3. if exposure is triggered, estimate reasonable fees/costs incurred from the date of filing the offer.

1) Start with the statutory trigger: 30-day non-acceptance

Under Fla. Stat. § 768.79(1):

• When a defendant files an offer of judgment in a civil action for damages,
• and the plaintiff does not accept within 30 days,
• the defendant may recover reasonable costs and attorney’s fees incurred from the date of filing the offer.

So the analyzer begins with your non-acceptance within 30 days input (often entered as a yes/no acceptance toggle).

Practical effect in the analyzer

• If you mark accepted within 30 days, the tool typically suppresses or reduces the fee/cost-shifting output.
• If you mark not accepted within 30 days, it applies the statutory comparison/exposure logic.

2) Compare final recovery vs. the offer amount

Next, the analyzer performs a “who beats the offer” comparison. Conceptually, it needs two consistent inputs:

• Offer amount (defendant’s offer)
• Final recovery (plaintiff)

Consistency rule (where errors often happen) To avoid accidental flips:

• Use the same damages basis for both numbers.
• If the offer amount (or your comparison number) implicitly assumes certain components, your “final recovery” should match that approach.

Common consistency choices:

• Include or exclude pre-judgment interest the same way on both sides.
• Treat costs consistently (either folded into the recovery comparison number if that’s how your tool expects it, or kept separate if the tool separates them).

3) If exposure is triggered, estimate post-offer fees and costs

If your inputs cause the analyzer to indicate fee/cost exposure, it estimates what a defendant may recover—modeled around § 768.79’s timing language:

• “reasonable costs and attorney’s fees … from the date of filing [the] offer”

How to feed DocketMath correctly

• If you have total attorney’s fees through the end of the case, don’t enter the total unless the tool is explicitly expecting “post-offer only.”
• Split your time into:

  • pre-offer (before the offer filing date)
  • post-offer (from the offer filing date forward)

Then enter:

• post-offer fees = (post-offer hours × applicable rate) (if the tool uses hours/rates), or
• your post-offer total fee estimate (if the tool uses totals).

For costs, do the same:

• enter costs incurred after the offer date, if the tool expects that breakdown.

4) Read the output as a modeled scenario, not a guarantee

Typical analyzer outputs are layered:

1. Outcome determination (e.g., whether the plaintiff’s recovery is modeled as favorable/unfavorable relative to the offer)
2. Estimated exposure (e.g., a dollar estimate for fees/costs based on your post-offer inputs)

Practical reminder: the calculator models outcomes using your numbers. Courts may later determine disputes about damages, the meaning of offers, and what qualifies as “reasonable” fees/costs.

Common pitfalls

Here are the mistakes that most often distort a Florida Offer of Judgment calculation in DocketMath.

1) Using the wrong damages basis

If your final recovery excludes something that the offer amount assumes (or vice versa), you can flip the comparison result.

Watch for:

• pre-judgment interest treatment
• whether costs are included in the number you’re comparing

2) Forgetting (or mis-entering) the 30-day trigger

If you enter acceptance timing incorrectly, the analyzer may show fee/cost shifting even when the statutory condition isn’t modeled as satisfied.

3) Estimating fees without honoring “from the date of filing”

Because § 768.79(1) ties recovery to fees/costs incurred from the offer date:

• entering “total fees to date” can overstate exposure.
• entering “post-offer only” is usually more aligned with the statute’s timing concept.

4) Mixing final judgment with projections

If you use an estimate at one time and a final number at another, the comparison result changes. Label scenarios clearly (e.g., “Scenario A: low recovery projection”).

5) Assuming a claim-type-specific timing rule

In the provided statute text, no claim-type-specific sub-rule was identified. Treat 30 days as the default acceptance window for the general § 768.79 mechanism in this guide.

Sources and references

• Fla. Stat. § 768.79(1) (Offer of judgment; acceptance window; cost/fee recovery tied to the offer filing date)
  https://www.flsenate.gov/Laws/Statutes/2023/768.79
  Statute excerpt (as provided in the brief): “In any civil action for damages filed in the courts of this state, if a defendant files an offer of judgment which is not accepted by the plaintiff within 30 days, the defendant shall be entitled to recover reasonable costs and attorney’s fees incurred by her or him … from the date of filing o…”

Next steps

1. Open DocketMath → Offer Of Judgment Analyzer (US-FL) using the primary CTA: /tools/offer-of-judgment-analyzer
2. Enter:

   • offer amount
   • plaintiff final recovery (or the scenario’s projected recovery)
   • the yes/no flag for acceptance within 30 days
3. Enter fee/cost estimates as post-offer totals (or