How to run Offer Of Judgment Analyzer in DocketMath for Florida

Step-by-step

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

You can run DocketMath’s Offer Of Judgment Analyzer for Florida (US-FL) to model how an offer of judgment under Florida Statutes § 768.79 may affect later costs and attorney’s fees. This walkthrough focuses on the tool workflow—not legal advice.

1) Open the tool for the correct jurisdiction

1. Go to /tools/offer-of-judgment-analyzer
2. Select Jurisdiction: US-FL (Florida).
3. Confirm the tool is using Florida’s jurisdiction-aware rules. For Florida, the analyzer is grounded in Fla. Stat. § 768.79, which governs offers of judgment in qualifying civil damages actions.

2) Understand the statute period the tool is using

Florida’s offer framework includes a key timing requirement tied to the applicable “offer period.” In the information provided for this setup, no claim-type-specific sub-rule was found, so the analyzer is using the default/general period.

3) Enter the case numbers and dates

In the analyzer, you’ll typically provide inputs like these (field names may vary slightly by UI):

• Action type / damages context (if prompted): Choose the option that indicates a civil action for damages, consistent with Fla. Stat. § 768.79.
• Offer date: The date the offer was served.
• Response deadline window (if prompted): Enter the period the tool asks for, or use the UI’s Florida defaults if it pre-fills.
• Offered amount: The offer of judgment amount stated in the offer.
• Judgment amount (or projected judgment): Use the final judgment amount when available, or your scenario estimate when stress-testing.
• Prevailing party / threshold comparison inputs (if prompted):

  • Which side made the offer (plaintiff/defendant), if the tool asks.
  • The analyzer will then compare outcomes using its threshold logic to model fee/cost consequences.

If the interface asks for fields such as estimated costs or attorney’s fees, treat those as optional modeling inputs: enter them only if you intend to estimate magnitude, not just whether the threshold outcome shifts.

4) Choose scenario mode (what changes the output)

Most analyzers change results based on the relative relationship between the offer and the eventual judgment, plus timing assumptions. In DocketMath, the output typically changes most when you adjust:

• Judgment amount vs. offered amount

  • If the modeled outcome crosses the analyzer’s threshold comparison (offer vs. judgment), the fee/cost consequence narrative can change significantly.
• Timing assumptions

  • Changing the offer date can change whether the tool considers the timing to “fit” the period it’s modeling.

5) Review the threshold and consequence breakdown

After submission, the results generally provide a breakdown such as:

• Threshold / comparison logic

  • How the tool compares the offer amount to the judgment amount under the Florida framework reflected by Fla. Stat. § 768.79 concepts.
• Modeled cost/fee exposure

  • Output that explains potential costs and attorney’s fees consequences depending on whether the outcome is favorable relative to the offer.
• Timeline checks

  • A section that flags whether the offer date aligns with the analyzer’s jurisdiction period assumptions.

6) Adjust inputs and compare outcomes (fast iteration)

To see what drives risk or leverage, iterate methodically by changing one input at a time:

• Change offered amount (for example, test increments like ±10%)
• Swap judgment amount (actual vs. forecast)
• Change which side made the offer (if the tool asks)
• Re-run to compare the resulting threshold and consequence sections

A practical iteration plan:

• Scenario A: Offer slightly below your expected judgment
• Scenario B: Offer near your expected judgment
• Scenario C: Offer above your expected judgment

7) Export or capture the result for discussion

If the tool provides export/copy options:

• Save the results summary and the input values you used.
• Capture the threshold comparison outcome and the modeled consequence text/numbers.

This can be useful for internal settlement discussions and for communicating the assumptions you used with your team—without converting the tool into legal advice.

Common pitfalls

These are common reasons people get confusing or “unexpected” results when running the Florida Offer Of Judgment Analyzer in DocketMath:

1. Using the wrong scope assumptions

   • Fla. Stat. § 768.79 applies to civil actions for damages with qualifying offers of judgment to the opposing party.
   • If the matter doesn’t match the damages scope, the analyzer’s modeling may not align with how the statute would apply.

2. Incorrect offer date handling

   • A small date difference can materially affect whether the timing “fits” the analyzer’s jurisdiction period assumptions.
   • Re-check the exact served date of the offer (and how your case record defines key dates).

3. Confusing “offer amount” with total settlement figures

   • The tool needs the offer of judgment amount—the amount stated in the offer itself.
   • Don’t substitute broader settlement totals unless the UI clearly ties those totals to the offer amount.

4. Assuming claim-type-specific timing rules are loaded

   • The setup here explicitly states: no claim-type-specific sub-rule was found.
   • That means the analyzer uses the general/default period.
   • If your case involves unusual timing issues, the analyzer may not reflect that specificity.

5. Treating modeled fee/cost numbers as guaranteed

   • Even when the threshold logic suggests a favorable outcome, actual court awards can vary based on additional factors.
   • Use the analyzer for scenario comparison, not certainty.

6. Not running sensitivity tests

   • One run rarely reveals where the decision boundary is.
   • Run at least 3 scenarios (low / near / high offer) to understand how sensitive the outcome is to the numbers you input.

Try it

Use a quick 3-run test in DocketMath with your numbers to see how sensitive the results are for Florida.

• ✅ Run 1 (baseline):

  • Offer amount = your best estimate
  • Judgment amount = actual (or forecast)
  • Offer date = the date from your record
• ✅ Run 2 (risk test):

  • Increase the offer amount by 10%
  • Keep the judgment amount the same
  • Re-run
• ✅ Run 3 (conservative test):

  • Decrease the offer amount by 10%
  • Keep the judgment amount the same
  • Re-run

When you compare results, focus on:

• The threshold comparison outcome
• Any modeled cost/fee exposure language or numeric estimates
• Any timeline fit warnings or confirmations

To start right away, open: /tools/offer-of-judgment-analyzer

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado