How to run Damages Allocation in DocketMath for Tennessee

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Tennessee (US-TN). The calculator uses a jurisdiction-aware approach so your time-related assumptions align with Tennessee’s baseline framework for limitation periods.

1) Open the correct tool

Start here to ensure you’re using the Tennessee damage allocation workflow:

• Go to /tools/damages-allocation

2) Confirm the jurisdiction setting: US-TN

Within the tool:

• Select Jurisdiction: Tennessee
• Confirm the jurisdiction code shows US-TN

Why this matters: the tool’s time-window logic relies on Tennessee’s general/default limitation period.

3) Enter your damages allocation inputs

Damages Allocation typically requires inputs that let the tool (a) understand the damages components you want allocated and (b) determine how to allocate them to a total (or to compute allocations based on a specified basis). Exact field names can vary by UI, but commonly you’ll see a mix of:

• Damages components (categories that need allocation)
• Total damages (or the components that sum to a total)
• Allocation basis (how DocketMath should distribute amounts across categories)
• Relevant dates (if the tool includes fields to apply limitation-period logic)

A practical approach:

• If you have multiple damages categories: enter each category amount and choose the allocation basis the calculator expects.
• If you have a single total: enter the total and make sure the allocation basis fields are completed so DocketMath can split the total into the categories.
• If your process depends on time eligibility: enter the dates in the date fields provided by the tool. These dates are what the calculator uses to decide whether amounts fall inside or outside the applicable limitation window.

4) Use Tennessee’s default limitation period (general SOL)

For Tennessee, the calculator is grounded in the general/default limitation period. Based on the jurisdiction data provided, no claim-type-specific sub-rule was found—so the tool should rely on the baseline period below (rather than using different periods by claim type).

Use the following inputs/rules in the tool:

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

In plain terms: when DocketMath applies limitation-period logic for Tennessee, it uses a 1-year general/default period. Because no claim-type-specific period was identified in the provided rules, you should not expect different limitation windows for different claim categories within this setup.

5) Run the calculation

Once your inputs are complete:

• Click Calculate (or the tool’s equivalent action button)

DocketMath will compute outputs based on the damages inputs and the selected allocation method/basis. If you provided relevant dates, also watch for time-limited or eligible period indicators.

6) Interpret the outputs in context

After results load, review the main outputs for three things: allocation, totals, and time eligibility.

Common output areas include:

• Allocated damages by category/component
• Totals (allocated sum vs. your provided total)
• Eligibility adjustments (if date inputs cause some amounts to be limited by the limitation period)

Sanity checks you can do quickly:

• Verify that the allocated category amounts add up to the expected total, unless the calculator explicitly shows truncation or eligibility reductions.
• If time eligibility is applied, confirm the calculator is using the 1-year general/default period for Tennessee (not a claim-type-specific rule).
• If the outputs include an “eligible” vs. “limited” breakdown, treat that strictly as calculator logic tied to dates—not as a determination about the merits of a claim.

7) Iterate quickly with “what-if” input changes

A practical advantage of DocketMath is fast iteration. If you need to test scenarios:

• Change damage category inputs and re-run to see how allocations shift across categories.
• If you’re testing whether amounts fall inside/outside the limitation window, adjust the date inputs the tool provides and re-run.

Important caution:

• Small date changes can move portions of damages from eligible to limited (or vice versa). Treat date edits like data corrections—not new assumptions—so you can explain why the output changed.

Common pitfalls

Use this checklist to avoid the most frequent issues when running Damages Allocation in Tennessee (US-TN):

• If you leave the jurisdiction on a different setting, DocketMath’s limitation-period logic won’t match Tennessee.

• With the provided jurisdiction data, the tool relies on Tennessee’s general/default 1-year period from Tenn. Code Ann. § 40-35-111(e)(2).

• Because no claim-type-specific sub-rule was found, you should not expect different limitation windows by claim category in this setup.

• If category inputs don’t sum to your stated total (and you didn’t intend a different allocation structure), you may see output totals that look “wrong” even if allocation logic is functioning correctly.

• Date fields may require a specific format (for example, MM/DD/YYYY vs YYYY-MM-DD). Use the format the tool requests.

• When you re-run, note which field you modified (e.g., “event date moved from 2023-01-10 to 2023-03-01”). This makes it easier to interpret why allocations or eligible amounts changed.

• If the output indicates an amount is limited by the 1-year general/default period, that’s calculator logic tied to dates—not a legal determination about entitlement.

Try it

Follow this short practice workflow to validate your end-to-end run:

1. Go to /tools/damages-allocation
2. Select **Tennessee (US-TN)
3. Enter:

   • At least 2 damages categories (so you can observe allocation across categories)
   • A total and/or category amounts that reconcile cleanly with the tool’s expected structure
4. Enter a date that is:

   • Within 1 year of the relevant “start” date the tool uses (if the tool provides date inputs)
5. Click Calculate
6. Re-run with the same damages inputs, but change the date to be:

   • More than 1 year away, then click Calculate again

What you should observe:

• Allocation results by category should reflect your allocation basis/method.
• If limitation-period gating is enabled by your date inputs, the “eligible” vs. “limited” outcome should reflect the 1-year general/default period for Tennessee under Tenn. Code Ann. § 40-35-111(e)(2) (not a claim-type-specific alternative), because none was identified in the provided jurisdiction data.

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