Worked example: Damages Allocation in Florida

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

Below is a worked example of damages allocation in Florida using DocketMath with jurisdiction-aware rules. This is a practical walkthrough of how the calculator is typically used to allocate damages and reflect key timing rules that affect which damages may be recoverable.

Scenario (facts assumed for the example)

• Jurisdiction: Florida (US-FL)
• Claim type: Not specified → we apply the general/default timing rule only.
• Trigger date (e.g., injury/discovery trigger for the general timing rule): March 15, 2020
• Date the lawsuit was filed: June 20, 2023
• Damages buckets you want to allocate:

  • Economic losses (e.g., out-of-pocket medical costs)
  • Non-economic losses (e.g., pain and suffering)
  • Statutory/fee-like amounts (treated as a separate bucket in your model)

DocketMath inputs

You’d enter these kinds of inputs into the Damages Allocation calculator (access it at /tools/damages-allocation):

• Jurisdiction code: US-FL
• Trigger date: 2020-03-15
• Filing date: 2023-06-20
• Damages by category (example numbers):

• Allocation methodology (example):

  • Allocate the “timing-eligible” portion of each category proportionally.
  • Exclude the “timing-ineligible” portion (if any) based on Florida’s general/default timing rule.

Florida timing rule used by this example (general/default only)

This example uses Florida’s general limitations period of 4 years. The purpose of the worked example is to show how the calculator behaves under the default/general timing gate—no claim-type-specific sub-rule was provided/found, so we do not apply any claim-specific override.

• Florida Statute: § 775.15(2)(d) (general 4-year limitations period used here)
• Source: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai

Clear statement for the run: Because no claim-type-specific sub-rule was found, this example applies only the general/default 4-year period to determine timing eligibility.

Example run

Now let’s walk through the DocketMath calculation step-by-step using the inputs above.

Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

1) Compute elapsed time between trigger and filing

• Trigger date: 2020-03-15
• Filing date: 2023-06-20

Elapsed time (approximate):

• 2020-03-15 → 2023-03-15 = 3.00 years
• 2023-03-15 → 2023-06-20 ≈ 97 days ≈ 0.27 years

Total ≈ 3.27 years

2) Compare elapsed time to the general period (4 years)

• General SOL Period: 4 years
• Elapsed: ≈ 3.27 years
• Since 3.27 < 4, this example assumes the damages are timing-eligible under the calculator’s default rule.

Why this gate matters in practice: many damages allocation workflows use the timing gate to decide whether the damages are included fully, excluded fully, or partially reduced.

3) Apply allocation (timing-eligible logic)

Because the filing date is within the 4-year window, DocketMath includes 100% of each damages bucket in the timing-eligible pool (given the “general/default only” setup described above).

Claimed totals:

• Economic losses: $120,000
• Non-economic losses: $60,000
• Fee-like / costs bucket: $10,000

Total claimed: $190,000

**Output allocation (timing-eligible = 100%)

What DocketMath is doing (conceptually)

In this default setup, the calculation is effectively:

1. Apply the timing gate using Florida’s general/default 4-year rule (§ 775.15(2)(d)).
2. If eligible, allocate the full category amounts.
3. If not eligible, allocate only the portion deemed attributable to timing-eligible time (or otherwise reduce, depending on the calculator’s internal proration approach).

Pitfall to avoid: Don’t assume a claim-specific Florida statute automatically changes the timing outcome. This example intentionally stays with the general/default 4-year period only, consistent with the “no claim-type-specific sub-rule found” constraint.

Sensitivity check

A good way to validate assumptions is to change one input at a time and observe how results shift. Below are two sensitivity checks that focus on the timing gate.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity check A: File later (crossing the 4-year threshold)

Change only the filing date:

• Trigger date: 2020-03-15 (unchanged)
• Filing date (new): 2024-03-16 (one day after 4 years)

Elapsed time: about 4.00 years + 1 day.

Result expectation: the matter becomes outside the 4-year default period. The allocation should move from “include 100%” toward reduced eligible amounts.

Because the brief does not provide a precise proration formula for partial eligibility, treat this as a directional check: the allocated totals should decrease when crossing beyond the default timing window.

Directional outcome (illustrative):

When you run DocketMath, you should see exact dollar values based on the calculator’s internal proration method (if it uses partial eligibility rather than a strict cutoff).

Sensitivity check B: Move the trigger date earlier (keeping filing constant)

Change only the trigger date:

• Filing date: 2023-06-20 (unchanged)
• New trigger date: 2019-05-01

Elapsed time now becomes approximately:

• 2019-05-01 → 2023-05-01 = 4 years
• plus ~50 days → slightly over 4 years

Result expectation: an earlier trigger can push the case beyond the general/default 4-year period, shifting the output from full inclusion toward reduced eligible allocation.

Quick checklist to interpret sensitivity results

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