Inputs you need for Damages Allocation in Tennessee
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
DocketMath’s damages-allocation calculator is designed to take a small set of case-specific numbers and allocate damages consistently using Tennessee jurisdiction-aware rules. Before you run anything, gather the inputs below in a single worksheet so you can trace every output back to a source.
Quick note: This is a practical workflow for modeling. It’s not legal advice, and it won’t replace an attorney’s analysis of the facts and the claims you’re actually making.
Core inputs (damages + allocation drivers)
The full dollar figure you want to allocate (e.g., total compensatory damages claimed).
Examples (adjust to your case):
- Economic losses (medical bills, wage loss)
- Non-economic losses (pain and suffering)
- Other claimed components (property damage, specified fees)
These should sum to the total claimed damages amount. If they don’t, the allocation math can produce outputs that look “off” compared to your filing posture.
If you have partial payments, reimbursements, or settlement credits, list the amount(s) you intend to offset against the allocation base.
Depending on how you’re modeling damages allocation in Tennessee, DocketMath may require:
- Allocation weights (percentages) by category, or
- Allocation amounts by category based on your evidentiary structure
Time-related inputs (used to validate whether a filing window may apply)
Even when the calculator’s allocation math focuses on damages, a Tennessee-specific timing check can affect what damages you include in the modeled claim window. For Tennessee, use the general/default statute of limitations period below.
For Tennessee, the general/default period used here is 1 year under Tenn. Code Ann. § 40-35-111(e)(2):
Tenn. Code Ann. § 40-35-111(e)(2) (general/default) — https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
Because no claim-type-specific sub-rule was found in the provided jurisdiction data, this post uses that general default as the baseline, rather than trying to change periods based on claim labels.
Optional documentation inputs (recommended)
These aren’t required to run the allocation math, but they help you defend your inputs internally:
Where to find each input
Use your case file (or your case tracking system) to find each number.
Total claimed damages amount (USD)
- Look in the most current draft of the pleading, demand letter, or damages summary you’re using as your baseline.
Category amounts (USD)
- Economic losses: medical bills, invoices, employer statements, pay stubs, repair estimates.
- Non-economic losses: your narrative damages framework (often expressed as a lump sum). Convert to a numeric amount you can model consistently.
Payments already made / offsets (USD)
- Settlement documents, insurer payment summaries, prior judgments, lien releases, and any credited reimbursements.
Accrual date
- Case timeline: identify the key “event date” you treat as the accrual point (and, if relevant to your internal method, the discovery date you’re using—just be consistent).
Filing date
- Filing receipt, docket entry date, or your internal calendaring log.
When you build this in DocketMath, keep your inputs consistent with the dates and amounts used in your filings—especially category totals and offsets—because the calculator’s outputs depend on those entries directly.
Run it
To run the Tennessee allocation model in DocketMath:
Open the calculator: **/tools/damages-allocation
Select jurisdiction: **US-TN (Tennessee)
Enter:
- Total claimed damages (and/or category amounts)
- Any offsets/payments to credit
- Accrual date and filing date for the timing validation using the general/default 1-year window (Tenn. Code Ann. § 40-35-111(e)(2))
Generate results and export/save the allocation output for review.
What you should expect the outputs to do
When you change inputs, DocketMath’s outputs typically respond in predictable ways:
Changing category amounts
Updates category-by-category allocation totals and the final allocated remainder after offsets.Adding or increasing offsets
Reduces the portion available to allocate (depending on how your allocation configuration treats offsets).Adjusting accrual or filing dates
Performs a timing validation against Tennessee’s general/default 1-year period under Tenn. Code Ann. § 40-35-111(e)(2).- If the filing is outside the general default window, DocketMath can flag that the modeled damages window may be affected (review your workflow settings and your internal assumptions).
Warning: A “timing check” is a modeling guardrail, not a merits ruling. Even with the 1-year baseline, keep your jurisdiction logic aligned with the case-specific theory you’re applying—DocketMath reflects what your inputs support, not what a court will ultimately determine.
A quick Tennessee-specific sanity table
Use this to confirm your date setup before running:
| Input | Your entry | Calculator expectation (US-TN) |
|---|---|---|
| Accrual date | 2025-01-10 | Treated as baseline for limitations calculation |
| Filing date | 2026-02-01 | Compared against 1-year general default |
| Period basis | — | Tenn. Code Ann. § 40-35-111(e)(2) (general/default) |
| Claim-type customization | None found in provided data | General default used as baseline |
