Why Damages Allocation results differ in Tennessee

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

If you’re running DocketMath’s damages-allocation calculator for Tennessee (US-TN) and see different outcomes across teams, versions, or case files, the differences are usually traceable to a small set of inputs or assumptions. Tennessee’s default timing rule for certain sentencing-related calculations is governed by Tenn. Code Ann. § 40-35-111(e)(2), which provides a general/default period of 1 year. Importantly, no claim-type-specific sub-rule was found in the provided jurisdiction data—so the 1-year general/default period is applied unless your dataset explicitly encodes a different rule.

Here are the top 5 reasons damages-allocation results differ in Tennessee:

1. Different “start date” inputs

   • DocketMath timelines are sensitive to the earliest relevant date (e.g., notice date, incident date, or filing date).
   • Shift that start by even 30 days, and allocation often changes because the calculation window changes.

2. Different “end date” inputs

   • Similarly, changing the termination/end date alters the eligible period and can change the weighting DocketMath applies across time.

3. Conflicting credit for the 1-year general/default period

   • Tennessee’s general/default period is 1 year under Tenn. Code Ann. § 40-35-111(e)(2).
   • If one run assumes the 1-year window and another run omits it (or applies it inconsistently), the outputs will diverge.

4. **Input category mismatches (e.g., damage components)

   • Damages allocation often depends on how you break amounts into components (principal/damages types/period-specific portions).
   • If the same dollar figure is assigned to different components in different spreadsheets, totals may look similar, but the allocation order can change.

5. Rounding rules and currency precision

   • Different tools or spreadsheet exports can round at different steps.
   • A difference of 1–2 decimal places can compound across multiple allocation slices, leading to noticeably different allocated amounts.

How to isolate the variable

Use a “single-change” diagnostic workflow. If you change only one thing at a time, you can pinpoint what drives the divergence.

1. Record the baseline run

   • Save the inputs snapshot you used in DocketMath (dates, amounts, and component mapping).
   • Keep the jurisdiction setting explicitly at US-TN.

2. Verify the 1-year rule behavior

   • Confirm that the run incorporates the general/default 1-year period from Tenn. Code Ann. § 40-35-111(e)(2).
   • Because no claim-type-specific sub-rule was found in the provided data, you should expect the same default 1-year period across runs unless your inputs encode a different logic path.

3. Run four controlled tests

   • Test A: Change only the start date by a small increment (e.g., 15 days).
   • Test B: Change only the end date by the same increment.
   • Test C: Keep dates constant, change only component mapping (e.g., move one amount from “Category 1” to “Category 2”).
   • Test D: Keep everything constant, but adjust rounding/precision settings (if your workflow allows).

4. Compare outputs side-by-side

   • Look for:

     • changes to total allocated amount
     • changes to distribution across time slices/components
     • changes concentrated in only one component (often indicates a mapping mismatch)

If you want to start immediately, go to /tools/damages-allocation and rerun using the same inputs for each controlled test.

Next steps

Follow these action items to make your Tennessee damages-allocation outputs reproducible:

• Write down what “start” and “end” mean in your organization’s template.
• Ensure the same dollars always map to the same field(s) in DocketMath.
• Cite Tenn. Code Ann. § 40-35-111(e)(2) and note that the general/default SOL period is 1 year.
• Also record the finding: no claim-type-specific sub-rule was found in the provided jurisdiction data.
• For example: round to 2 decimals only at the final step.
• Run-to-run consistency matters; version control inputs is often the fastest way to resolve discrepancies.

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