How to calculate Structured Settlement in Tennessee

Quick takeaways

• A structured settlement in Tennessee is typically evaluated using the terms of the annuity contract (payout schedule, discounting method, and the annuity’s present value), not a single one-size-fits-all statutory formula.
• Tennessee’s statute of limitations timing (for limitations-style analyses) uses a general/default period when no claim-type-specific rule applies; in the jurisdiction data provided, no claim-type-specific sub-rule was found, so you should use the general/default rule for timing modeling until the underlying claim category is confirmed.
• DocketMath’s Structured Settlement calculator helps you model the payout stream (lump sums and periodic installments) and compute key figures like total scheduled payouts and present value using your selected discount rate and timing assumptions.
• Before you rely on any output numbers, confirm three contract items: start date, payment frequency, and whether payments escalate (e.g., annual increases).

Inputs you need

Gather these inputs before running the DocketMath calculator at /tools/structured-settlement (US-TN):

A. Settlement payment structure (annuity terms)

• Contract start date (e.g., 2026-07-01)
• Payment type (choose one):

  • Periodic payments (monthly/quarterly/annual)
  • Lump sum payment(s)
  • Mixed (lump + periodic)
• Payment frequency (e.g., monthly)
• Number of payments (or end date)
• Initial payment amount (for periodic payments)
• Escalation / growth rate (if payments increase over time)

  • Example: 0% (fixed) or 2% annual escalation
• Day-count convention used by your modeling approach (if DocketMath asks for it; if not, use the default consistently across scenarios)

B. Financial modeling parameters

• Discount rate (annual)

  • This is what converts future payments into present value.
• Discounting timing convention

  • Typically whether payments are discounted at the beginning or end of each period
  • Pick the same convention you’ll use consistently across scenarios

C. Tennessee timing analysis inputs (for limitations-related modeling)

If you’re also analyzing deadlines (for example, to understand whether settlement-structure timing aligns with a claim posture), you’ll need:

• Date of injury / accrual trigger

  • The date the claim “starts” for timing purposes in your scenario
• Date the structured settlement is intended to be implemented
• What claim type you believe applies

  • The provided Tennessee jurisdiction data did not identify a claim-type-specific sub-rule, so for this guide’s modeling assumption you’ll use the general/default period (explained below).

How the calculation works

DocketMath’s Structured Settlement calculation in Tennessee (US-TN) is essentially a two-part model:

1. Cash-flow projection from the payout schedule you enter
2. Present value computation by discounting those future cash flows to a single “as-of” date (typically the settlement/valuation date implied by your inputs)

1) Build the payout timeline

For each payment period (t):

• If payments are fixed, the payment amount is constant:

  • [ \text{Payment}(t) = P ]
• If payments escalate, payments grow by the escalation rate (g):

  • [ \text{Payment}(t) = P \times (1+g)^{k} ]
  • where (k) is the number of escalation intervals that have occurred by period (t).

Mixed structures are handled by summing cash flows:

• Lump sum payments occur on the dates you specify
• Periodic payments contribute cash flows at each frequency interval

2) Compute totals and present value

DocketMath aggregates:

• Total scheduled payouts [ \sum_{t=1}^{n} \text{Payment}(t) + \text{LumpSumPayments} ]

• Present value (PV) using a discount rate (r)

  If the discounting aligns with the payment period length you selected: [ PV = \sum_{t=1}^{n} \frac{\text{Payment}(t)}{(1+r)^{t}} ] In practice, DocketMath applies the PV logic according to the timing convention and period structure represented by your inputs.

3) Optional: incorporate Tennessee limitations timing (general/default period)

Your provided Tennessee jurisdiction data says:

• No claim-type-specific sub-rule was found.
• Therefore, limitations-style timing modeling should use the general/default period.

Because limitations timing depends on what the underlying claim actually is, this “general/default period” is best treated as a conservative scenario assumption, not a substitute for confirming claim categorization from the underlying facts.

The referenced limitations framework commonly points to:

• Tenn. Code Ann. § 28-3-104 — general limitations for specified categories within Title 28, Chapter 3 (including a one-year limitations period for certain specified actions/categories)
• Tenn. Code Ann. § 28-3-105 — additional limitations provisions within Title 28, Chapter 3
• plus the general limitations structure under Title 28, Chapter 3

4) How outputs change when you change inputs

Use DocketMath to run “what-if” iterations:

• Higher discount rate → lower PV (future payments are worth less today)
• Add escalation (e.g., 2% annual) → higher PV and higher total scheduled payouts
• Delay the start date → lower PV because payments occur later
• Change payment frequency (monthly vs. quarterly) → timing becomes more granular; PV often shifts depending on how the first payment lands under the convention
• Fixed vs. escalated vs. mixed → long-tail impacts show up strongly when payments extend across many years

Common pitfalls

Avoid these recurring issues when using DocketMath for US-TN structured settlement calculations:

• Forgetting the payment start date

  • Even a one-month shift can materially affect PV, especially for long schedules.
• Mixing discounting conventions

  • If you assume “end of period” for PV but enter payments as if they were “beginning of period,” results can fail to reconcile with the annuity/accounting methodology.
• Assuming escalation where none exists

  • Many annuities are fixed unless the contract expressly provides increases.
• Treating the limitations period as claim-type-specific

  • The provided data did not identify a claim-type-specific sub-rule. If you select a different claim category without support, you may conflict with the Tennessee limitations framework.
• Conflating “total payout” with “value today”

  • Total scheduled payouts can be much larger than PV; PV is what changes most with discount rate and timing.
• Not reconciling lump sums

  • Ensure lump sums are placed on the correct dates; missing or misdating one lump can distort PV.

Sources and references

Tennessee statutes relevant to the limitations framework referenced in this jurisdiction-aware guidance:

• Tenn. Code Ann. § 28-3-104 — Limitations for actions under specified categories within Title 28, Chapter 3
• Tenn. Code Ann. § 28-3-105 — Additional limitations provisions within Title 28, Chapter 3

Operational note tied to your provided jurisdiction data:

• No claim-type-specific sub-rule was found for structured settlement-related timing assumptions in the dataset. Therefore, the model uses the general/default period for scenario timing unless claim categorization is confirmed from the underlying facts and applicable Tennessee limitations provisions.

Next steps

1. Open /tools/structured-settlement and load your structured settlement parameters.
2. Enter annuity terms accurately:

   • Start date, frequency, end date/number of payments, and escalation (if any).
3. Select a discount rate appropriate for your scenario.

   • Then test sensitivity (e.g., 3% vs. 5% vs. 7%) to see how PV changes.
4. If you are modeling Tennessee timing, document:

   • The accrual/injury trigger date used
   • The general/default period assumption (because no claim-type-specific sub-rule was found in the provided jurisdiction data)
5. Reconcile outputs with contract documents:

   • Verify the payout schedule in your annuity matches your inputs.

Related reading

• How to calculate Structured Settlement in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Structured Settlement in Philippines — Worked example with real statute citations
• Inputs you need for Structured Settlement in Philippines — Input checklist with sourcing guidance