How to run Offer Of Judgment Analyzer in DocketMath for Florida

Step-by-step

This guide shows how to run Offer Of Judgment Analyzer in DocketMath for Florida (US-FL), using jurisdiction-aware rules tied to Fla. Stat. § 768.79. DocketMath helps you model how offer timing + acceptance can affect potential costs and attorney’s fees exposure—but it’s still a planning tool, not legal advice.

1) Open the calculator

1. Go to the tool: /tools/offer-of-judgment-analyzer.
2. Select Jurisdiction: Florida (US-FL).

If you don’t see a direct jurisdiction selector, look for a Jurisdiction field in the form or a ruleset dropdown. The key is to ensure the calculator applies Florida’s acceptance/timing logic associated with Fla. Stat. § 768.79.

2) Confirm the timing rule DocketMath will apply (default rule)

Under Florida’s offer of judgment statute, the default acceptance clock is 30 days in the general scenario. The statute provides that when a defendant files an offer of judgment that is not accepted within 30 days, the defendant may recover certain reasonable costs and attorney’s fees.

• General/default period: 30 days
• Source: Fla. Stat. § 768.79(1)
  (Text includes: “if a defendant files an offer of judgment which is not accepted by the plaintiff within 30 days … from the date of filing o…”)
• How to apply it in the calculator: DocketMath should treat this general language as the governing acceptance window for standard Florida modeling.

No claim-type-specific sub-rule was found, so the analyzer should use the general/default 30-day period from § 768.79(1) rather than attempting to switch to a different time limit based on claim type.

3) Enter the inputs DocketMath needs

Exact field labels can vary, but Florida modeling typically works best when you provide the core numbers that drive the analysis:

• Offer amount
  The defendant’s offer of judgment value.
• Date the offer was filed
  Used to anchor the 30-day clock under Fla. Stat. § 768.79(1).
• Acceptance details / modeled timing outcome
  If your scenario is “not accepted,” explicitly model that it was not accepted within 30 days (or use the tool’s equivalent timing fields).
• Amount ultimately recovered
  The amount the plaintiff recovers (judgment and/or settlement amount—whichever definition the tool uses for “ultimate recovery”).
• Role / prevailing-party framing (if requested)
  Some analyzers use this to determine whose fees/costs exposure they’re estimating.
• Reasonable costs and attorney’s fees inputs (if prompted)
  If DocketMath asks for amounts, you’ll generally want numbers that you can support as reasonable for the scenario you’re modeling.

If the tool offers multiple ways to estimate fees (for example, “rate × hours” vs. “total fees”), choose the method that best matches the information you actually have.

4) Choose the modeling approach (if the tool offers options)

Some offer-of-judgment tools let you select how results are calculated. If available, consider:

• Fee/cost approach using reasonable costs + attorney’s fees (often closest to the statute’s structure)
• Offer-vs-judgment comparison mode (sometimes produces only economic differences without fully reflecting fee/cost inputs)

To reflect § 768.79’s potential impact, prefer the approach that accounts for reasonable costs and attorney’s fees—assuming you can provide defensible inputs.

5) Run the analysis

1. Click Calculate (or the equivalent button).
2. Review outputs in two passes:

   • Pass A: Timing & eligibility logic
     Confirm the analyzer uses the 30-day non-acceptance framework under Fla. Stat. § 768.79(1).
   • Pass B: Economic outcome
     Check how the tool compares your offer amount vs. the amount ultimately recovered, and how it applies any fee/cost consequences it estimates.

6) Interpret the results (what changes when inputs change)

Use DocketMath as a “what-if” model. Common sensitivity patterns include:

• Offer amount increases
  This often changes how strongly the offer influences the outcome in the analyzer’s compare-to-recovery logic.
• Judgment/settlement recovered changes
  This is frequently the biggest driver because the tool may hinge the estimated exposure on where recovery lands relative to the offer.
• Timing changes (offer date / acceptance timing)
  If you model acceptance within vs. after the 30-day window, outputs typically shift because § 768.79(1) conditions the mechanism on whether the offer was “not accepted … within 30 days.”

Pitfall (common): The tool won’t automatically know your case facts. If you’re modeling “not accepted within 30 days,” make sure you enter that explicitly using the fields the calculator provides for acceptance/timing. Otherwise, the statutory trigger logic may not match your intended scenario.

7) Save or export your scenario (optional but useful)

If DocketMath allows saving or exporting:

• Save with a descriptive name like: “FL OJ - Offer filed 2026-01-15 - Not accepted within 30 days”.
• Export results for quick comparison across multiple offers or multiple recovery ranges.

This is especially helpful if you plan to test several offers (e.g., different offer amounts) against multiple settlement outcomes.

Common pitfalls

These are the issues that most often make Florida outputs look “wrong,” or at least less useful.

• Using the wrong jurisdiction rules

  • Florida’s offer of judgment statute is Fla. Stat. § 768.79. If the jurisdiction is set incorrectly, the analyzer may apply a different acceptance deadline or fee logic.
• Mismatching offer date and the 30-day clock

  • Florida’s default is 30 days under § 768.79(1). Make sure the offer filing date and any acceptance/timing fields align with that window.
• Ignoring the “general/default period” assumption

  • Since no claim-type-specific timing sub-rule was found, the analyzer should use the general 30-day period from § 768.79(1). Don’t expect different deadlines unless the calculator has a specific option for them.
• Feeding unrealistic (or unjustified) fee/cost estimates

  • The statute references reasonable costs and attorney’s fees. If you can only provide rough numbers, note that your output is only as credible as your inputs. Garbage in → exaggerated or misleading results.
• Entering the wrong “amount ultimately recovered”

  • Many offer analyzers depend on how the ultimate recovery compares to the offer. Confirm the tool’s definition (judgment amount vs. settlement amount vs. another recovery measure).

Try it

1. Go to the tool: /tools/offer-of-judgment-analyzer.
2. Set Jurisdiction: Florida (US-FL).
3. Enter inputs for at least two scenarios:

   • Offer amount
   • Offer filing date
   • Acceptance timing modeled as either:

     • Accepted within 30 days, or
     • Not accepted within 30 days (the default statutory window under Fla. Stat. § 768.79(1))
   • Amount ultimately recovered
   • Reasonable costs and attorney’s fees inputs if prompted

Then run the calculations side-by-side.

• If you modeled the statutory timing correctly, you should see meaningful differences because § 768.79(1) conditions the mechanism on whether the offer was not accepted within 30 days.
• If the analyzer includes a section like Eligibility, Timing, or Statutory trigger, check that first—then review the estimated fee/cost outcome second.

Gentle reminder: This is not legal advice. If you’re using the output for decisions, consider validating assumptions with qualified counsel and your case record.

Related reading

• How to calculate Offer Of Judgment Analyzer in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Offer Of Judgment Analyzer in Philippines — Worked example with real statute citations
• Inputs you need for Offer Of Judgment Analyzer in Philippines — Input checklist with sourcing guidance