Worked example: Damages Allocation in Tennessee

Example inputs

This worked example shows how DocketMath can allocate damages using Tennessee-aware rules for general default limitations. Because the provided jurisdiction data shows no claim-type-specific sub-rule was found, the example uses the general/default period you provided:

• General SOL period: 1 year
• General statute (Tennessee): Tennessee Code Annotated § 40-35-111(e)(2) (default rule)

Scenario (inputs)

Assume a Tennessee damages claim where damages can be separated into two time buckets (earlier vs. later accrual periods):

To make this concrete, we’ll interpret the inputs as follows:

• Bucket 1 = damages tied to the “older” portion of the accrual timeline
• Bucket 2 = damages tied to the “newer” portion of the accrual timeline

In a real workflow, you’d either (a) provide bucket amounts tied to dates or (b) provide enough date-linked structure for the tool to compute how much falls inside vs. outside the default limitations cutoff.

How the 1-year default drives allocation

Under the provided default rule (Tenn. Code Ann. § 40-35-111(e)(2)), the applicable timing cutoff in this example is 1 year.

Since your note indicates no claim-type-specific sub-rule was found, DocketMath applies the 1-year general/default period rather than swapping in a different limitations duration for a specific claim category.

Plain-English impact: damages that fall outside the 1-year window (measured from the relevant start point used in the tool) are treated as outside the default limitations window for allocation purposes.

Example run

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.

Step 1: Determine the default “timely window”

Using the key inputs:

• date_of_injury (accrual start): 2024-01-15
• default_sol_years: 1 year

The default cutoff date is therefore:

• Default cutoff date: 2025-01-15

Now compare that to:

• date_filing: 2025-03-01

Because 2025-03-01 is after 2025-01-15, only the portion of damages associated with the timeframe on or before 2025-01-15 is treated as within the default limitations window.

Step 2: Apply the allocation to the time buckets

Assume:

• Bucket 1 ($70,000) is tied to the pre-cutoff timeframe (on or before 2025-01-15)
• Bucket 2 ($50,000) is tied to the post-cutoff timeframe (after 2025-01-15)

Then, under the default 1-year cutoff logic, the included/excluded allocation is:

What DocketMath would display (conceptual output)

When you run the tool, the output will reflect the cutoff:

• Allocated damages (timely): $70,000
• Unallocated/excluded damages (outside default window): $50,000
• Effective included percentage:
  [ \frac{70,000}{120,000} = 58.33% ]

If you’re running it directly, start here: /tools/damages-allocation.

Statutory anchoring (why the cutoff is 1 year here)

This example uses 1 year because:

1. Your jurisdiction data provided a general/default limitations period of 1 year, and
2. It cites Tenn. Code Ann. § 40-35-111(e)(2) as the general/default source, and
3. No claim-type-specific sub-rule was found in your dataset, so the tool applies the default rather than a different category-specific period.

Sensitivity check

A practical sensitivity check varies one input at a time and observes how the included amount changes, using the same underlying bucket-to-date interpretation.

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 A: Move the filing date earlier by 30 days

Change only date_filing:

• Original: 2025-03-01
• New: 2025-02-29

Since both are still after the cutoff (2025-01-15), the bucket classification remains the same:

• Bucket 1 = timely
• Bucket 2 = untimely

Result: allocated damages remain $70,000.

Sensitivity B: Move the filing date to before the cutoff

Change only date_filing:

• New date_filing: 2025-01-14

Now filing is 1 day before the cutoff (2025-01-15). If we keep the same bucket definitions as before (Bucket 1 = pre-cutoff, Bucket 2 = post-cutoff), the included/excluded amounts still land as:

• Included: $70,000
• Excluded: $50,000

Result: allocated damages stay $70,000.

Key practical takeaway: In this simplified setup, sensitivity may not change the numeric output unless your “bucket” mapping to the cutoff changes (or unless the tool is configured to allocate proportionally by actual dates).

Sensitivity C: Make allocation proportional (boundary-sensitive)

Keep filing at 2025-03-01, but adjust the assumed bucket/date relationship so Bucket 2 straddles the cutoff.

Example proportional model (illustrative):

• Only 40% of Bucket 2 is within the timely window
• Included from Bucket 2 = $50,000 × 0.40 = $20,000

Then:

• Included: $70,000 + $20,000 = $90,000
• Excluded: $50,000 − $20,000 = $30,000

Sensitivity takeaway

For Tennessee damages-allocation modeling using this default approach:

• The timing anchor is the 1-year default cutoff tied to Tenn. Code Ann. § 40-35-111(e)(2).
• Whether outputs behave like a binary include/exclude or a proportional split depends heavily on how your data/buckets map to dates (and how granular the tool inputs are).

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