Damages Allocation reference snapshot for Tennessee

Rule or statute summary

In Tennessee, the baseline rule for how long you have to seek damages in a criminal-case context (using the provided Tennessee SOL framework) is set by Tennessee’s general statute of limitations rule in Tenn. Code Ann. § 40-35-111(e)(2).

For this Damages Allocation reference snapshot, DocketMath applies the general/default period because no claim-type-specific sub-rule was found in the provided materials. That means the snapshot focuses on using the 1-year default window as the timing constraint for the calculator’s damages allocation logic.

Baseline period used in this snapshot

• General SOL Period: 1 year
• Authority: **Tennessee Code Annotated § 40-35-111(e)(2)

What this means for a damages allocation workflow (non-legal guidance)

When you run a damages allocation workflow, the SOL window often affects whether certain parts of your damages timeline are considered within the limitations horizon or treated as outside it. In practical terms, a 1-year baseline can:

• Cut off earlier damages that fall before the SOL cutoff date
• Exclude or down-weight damages components associated with time periods outside the window
• Require careful alignment of your baseline/accrual date with the calculator’s notion of when timing starts

DocketMath behavior (as used in this snapshot):

• The calculator uses the 1-year Tennessee default as the starting point.
• It will continue using that default unless you identify a claim-type-specific limitation rule that should override the general/default period based on your scenario.

How the “allocation snapshot” concept fits in

Damages allocation calculators typically distribute or sequence damages components across time (for example: which portions are eligible, which time buckets are counted, and how different date ranges affect totals). The SOL period matters because it often determines:

• the time horizon included in the allocation
• the boundary between included vs. excluded segments
• how the calculator calculates the SOL cutoff relative to your selected baseline date

Because the provided Tennessee authority is a general SOL rule (not claim-type-specific), this snapshot is a time-horizon reference for the calculator’s default SOL handling.

Citations

• General SOL Period used in this Tennessee snapshot: 1 year
• Citation: **Tennessee Code Annotated § 40-35-111(e)(2)
• Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Use these sources to confirm the authoritative text before finalizing the calculation.

• Primary authority reference

Capture the source for each input so another team member can verify the same result quickly.

Rule selection logic for this snapshot

Sources and references

• Tennessee Code Annotated § 40-35-111(e)(2) (Justia): https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Use the calculator

To apply the Tennessee 1-year default SOL period in a damages allocation workflow, use DocketMath’s damages-allocation tool:

• Primary CTA: /tools/damages-allocation

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Inputs to provide (and how they affect outputs)

Set the timeline assumptions that control what falls inside vs. outside the 1-year window.

Common input patterns include:

• Jurisdiction: **Tennessee (US-TN)
• Baseline date (often treated as an “accrual”/start date for timing)
• End date (often the last date included in your damages calculation)
• Component dates (if the tool breaks damages into separate buckets)

Because this snapshot is tied to Tenn. Code Ann. § 40-35-111(e)(2), DocketMath will apply the 1-year SOL lookback/time horizon logic internally based on your dates.

What outputs typically change when SOL applies

Once the calculator enforces the 1-year default, you should expect allocation outputs to reflect:

• Covered portion expands/contracts depending on how far your timeline extends relative to the baseline date
• Time-bucket boundaries shift based on the SOL cutoff
• Net allocation amount may reduce if earlier periods fall outside the limitations window

Quick scenario check (conceptual)

If your damages timeline extends more than ~365 days beyond the relevant baseline date, then—depending on the calculator design—earlier segments are more likely to be treated as outside the limitations horizon, reducing the allocation attributable to excluded time.

To sanity-check:

• Run a comparison where end date is within 1 year vs. beyond 1 year
• Keep the baseline date constant across both runs
• Compare how bucket eligibility changes

Gentle compliance note

This is a reference snapshot based on the general/default period identified in the provided Tennessee statute citation. It does not replace a case-specific legal analysis. For best results, make sure your DocketMath timeline inputs match the real-world dates underlying your facts.

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