Damages Allocation rule lens: Tennessee
4 min read
Published April 15, 2026 • By DocketMath Team
The rule in plain language
Run this scenario in DocketMath using the Damages Allocation calculator.
In Tennessee, this damages allocation lens begins with a time boundary: the general statute of limitations (SOL) is 1 year for the default category the rule covers.
For Tennessee, the jurisdiction-aware source you provided for this general/default SOL period is:
- Tennessee Code Annotated § 40-35-111(e)(2) — general/default SOL period: 1 year
Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
Key scope statement (based on your jurisdiction data):
No claim-type-specific sub-rule was found in the materials you supplied. That means the 1-year default above is treated as the general rule for this lens, rather than automatically branching into special SOL periods for particular claim types.
Gentle warning (not legal advice): Even where a rule is described as a “default” period, real-case results can still change based on facts such as tolling, multiple claims with different accrual dates, or whether a claim fits a different statutory category than the default. DocketMath’s calculator helps you apply the rule you input, but it can’t replace legal analysis of your specific facts.
Why it matters for calculations
Damages allocation isn’t only about how damages are split—it’s also about which portions are eligible once you apply the SOL time boundary.
Using the Tennessee 1-year general/default SOL lens, the calculator typically functions like a time filter:
- If a component of damages falls outside the 1-year SOL window, it may be treated as unavailable for allocation in your model.
- If a component falls within the 1-year window, those portions are the ones most likely to be considered in the allocation outputs.
Practical effect on your inputs
In DocketMath’s damages-allocation workflow, outputs usually change when you change the relevant dates. The core date fields often include:
- Accrual/incident date (when the damages began accruing, in your model)
- Filing/model date (the date used to test whether damages fall within the SOL window)
- Damages period start / end (if your workflow divides damages into dated segments)
Because the cited Tennessee general/default SOL is 1 year, the calculator uses that to determine the allowed lookback/eligibility window for allocation.
A quick Tennessee lens check
Before you calculate, confirm you’re applying the correct level of the rule:
How outputs typically shift when you move dates
Here’s what you should expect at a high level when adjusting inputs:
| Input change | Likely calculation impact |
|---|---|
| Filing/model date moves later | More damages may fall within the 1-year window (depending on accrual dates) |
| Filing/model date moves earlier | Fewer damages may qualify within the 1-year window |
| Accrual/incident date moves earlier | More of the damages period may fall outside the 1-year window |
| Accrual/incident date moves later | More damages may fall inside the 1-year window |
| Damages segment end date expands | Additional segments may be included if they remain within the 1-year window |
Use the calculator
DocketMath’s Damages Allocation tool is the most direct way to apply the Tennessee general/default 1-year SOL lens to your allocation model.
Primary CTA: /tools/damages-allocation
When you open the calculator:
- Select jurisdiction: US-TN
- Enter the key dates (at minimum, the dates that define the damages period and the model/filing date)
- Review the calculator’s constrained damages window (based on the 1-year general/default rule)
- Check whether your allocation segments map cleanly to that window
What to enter (to get usable outputs)
Use inputs that match how you’re modeling damages:
- Start of damages accrual/incident date: when damages began accruing in your model
- End of damages period: last date you want considered for allocation
- Filing/model date: the date used to test whether damages fall within the 1-year SOL window
- Damages amounts (and segment dates if your workflow uses segments)
What to watch during the run
Pay close attention to whether parts of your damages timeline fall beyond the SOL boundary:
Pitfall: If your damages are entered as a single lump sum with no segment dates, the tool may have difficulty distinguishing what portion is inside versus outside the 1-year window. Segmenting damages with date ranges often produces more transparent, auditable allocation results.
If the calculator indicates part of the damages period is outside the 1-year window under Tenn. Code Ann. § 40-35-111(e)(2), consider whether you should:
- split damages into dated components, or
- adjust the accrual/date inputs to reflect the timeline you’re actually relying on
Output interpretation checklist
After you run the calculation, verify:
