How to run Damages Allocation in DocketMath for Florida

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Florida (US-FL), using jurisdiction-aware rules that reflect Florida’s general statute of limitations (SOL). You’ll also see how your inputs change the calculator’s outputs—without getting bogged down in legal theory.

1) Open the right calculator

1. Go to the calculator: /tools/damages-allocation.
2. Select Florida as the jurisdiction (code US-FL) if the tool prompts you.
3. Confirm you’re using the Damages Allocation calculator (not a different module such as fees or interest).

2) Choose the case timeline inputs

DocketMath’s damages allocation is timeline-driven. Gather the dates you’re going to use before you start:

• Incident / accrual date (start point)
• Filing date (when the claim was filed)
• Payment / damages period start and end (if the tool asks for a damages window)
• Any allocation categories you plan to split (for example: different damage components)

If the tool offers a “damages period” option, enter the period you want to allocate across. If you’re unsure, use the date range your document set already uses (complaint allegations, pretrial disclosures, or discovery responses).

3) Enter allocation inputs (what gets split)

Damages Allocation typically requires you to define:

• Total claimed damages (or the relevant numeric base)
• Allocation categories (each category gets its own amount or shares)
• How you want allocation to be applied (for example, by percentage, component totals, or by time periods—depending on the calculator’s UI)

Practical approach:

• Start with a single category to verify dates and SOL handling.
• Then split into multiple categories once the baseline output looks right.

4) Ensure Florida SOL rules are applied correctly

For Florida, DocketMath uses the general/default SOL period unless the tool has claim-type-specific rules available (in this setup, no claim-type-specific sub-rule was identified).

Florida general SOL period used here:

• 4 years under Florida Statute § 775.15(2)(d) (general period referenced for the default rule set).
  Source: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai

Jurisdiction rule note you provided:

• No claim-type-specific sub-rule was found.
  That means the tool should apply the general/default 4-year SOL rather than switching periods based on a claim label.

What to check in the UI:

• Look for a line or setting showing the SOL duration (e.g., “4 years”) and whether it’s the default/general period.
• If the tool shows “custom SOL,” do not override it unless you have a documented basis for a different period.

5) Run the calculation and review outputs

After inputting dates, damages, and allocation categories:

1. Click Calculate (or the equivalent button in the calculator).
2. Review the output sections in order—date eligibility first, then allocation results.

Common output elements you should expect to see:

• SOL cutoff / last eligible date (derived from the incident/accrual date plus 4 years)
• Eligible vs. ineligible portions of the damages window (if your damages span beyond the cutoff)
• Allocated amounts per category, potentially reduced or re-timed based on eligibility

6) Iterate: tighten the damages period and compare outputs

Because SOL eligibility often hinges on whether portions of a damages period fall inside or outside the cutoff, iteration is key.

Try this workflow:

• Version A: Use the broadest damages window you have.
• Version B: Use a narrower window that begins later (for example, after a known notice date or a document-specific milestone).

Compare:

• total allocated damages
• category-by-category allocations
• how much of your window becomes ineligible

Even small date changes can swing results when the window crosses the 4-year boundary.

7) Export or capture results for your workflow

If DocketMath provides export options:

• Save the run under a consistent label (e.g., “FL—Default SOL 4 yrs—Version B”).
• Capture key figures:

  • SOL cutoff date
  • eligible damages portion
  • allocated category totals

This makes it easier to track what changed and why—especially if you later adjust dates or split categories.

Common pitfalls

Avoid these issues—each one can cause Florida Damages Allocation results to drift from what your filings assume.

• Using the wrong start date

  • SOL calculations are sensitive to the “incident/accrual date.” If your team uses a different definition across documents, you’ll see mismatches in eligible vs. ineligible portions.

• Assuming a claim-type-specific SOL applies

  • In this Florida setup, no claim-type-specific sub-rule was found, so DocketMath should use the general/default 4-year SOL based on Florida Statute § 775.15(2)(d).
  • If the calculator UI offers a claim-type option, confirm it’s actually mapped to Florida-specific rules rather than generic assumptions.

• Letting the damages window extend beyond the SOL cutoff

  • When the damages period runs past the calculated cutoff, the output may reduce or segment amounts.
  • Double-check that your “damages period start/end” align with the same methodology used in your complaint or damages report.

• Allocating totals that don’t reconcile

  • If the tool expects category amounts to sum to a total, mismatched inputs can distort the category allocation even if dates are correct.
  • Do a quick consistency check before you rely on the numbers.

• Not running a baseline single-category test

  • If you jump straight into multiple categories, you may miss a date eligibility issue.
  • Start with one category, confirm SOL behavior, then expand.

Try it

Get hands-on by running a Florida test case through Damages Allocation:

1. Open /tools/damages-allocation.
2. Set jurisdiction to Florida (US-FL).
3. Use these verification checks:

   • Confirm the SOL period shown is 4 years (default/general).
   • Confirm the tool references the default rule, not a claim-type-specific override (since none was identified in the rule data you provided).
4. Enter:

   • an incident/accrual date
   • a filing date
   • a damages window that either:

     • stays within the 4-year span (to see the “fully eligible” behavior), or
     • crosses beyond it (to see segmentation or reduction)
5. Add 1–2 allocation categories.
6. Run the calculation.
7. Adjust one variable at a time and re-run:

   • change only the damages window end date, then re-run
   • change only the accrual date, then re-run
   • keep everything else constant

For the fastest sanity check, do this mini-matrix:

If your outputs behave consistently with those expectations, you’re ready to run your real damages allocation.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules