How to run Settlement Allocator in DocketMath for Tennessee

Step-by-step

Below is a practical walkthrough for running Settlement Allocator in DocketMath for Tennessee (US-TN), using jurisdiction-aware rules and the calculator’s Tennessee default limitations logic.

1) Open the Settlement Allocator tool

Start at the primary call to action:

• /tools/settlement-allocator

If you’re already in DocketMath, navigate to the Settlement Allocator calculator and select Tennessee (US-TN) in the jurisdiction selector.

2) Choose the settlement inputs the calculator requests

Settlement Allocator uses your settlement-related amounts to allocate components (for example, allocations that align with the calculator’s model). Use values that you can support with your settlement paperwork.

Typical inputs include:

• Settlement total (the gross settlement amount being allocated)
• Any category amounts you already know (if DocketMath prompts you for partial breakdowns)
• Offsets or adjustments (if applicable in your agreement)
• Date-related information used for timing logic, if the tool asks for it

If the tool offers multiple date fields (for example, a relevant event date vs. claim filing date), enter the dates that correspond to the timeline you’re modeling. The goal is consistency: use the same “timeline story” you would document in your case materials.

3) Confirm the tool is using Tennessee’s general default SOL logic

DocketMath’s jurisdiction-aware rules for Tennessee rely on the general/default limitations period when no claim-type-specific sub-rule is identified.

For Tennessee, the default provided is:

• General SOL period: 1 years
• General statute: 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/

Important: No claim-type-specific sub-rule was found in the provided jurisdiction data. That means the calculator should use the general/default 1-year period tied to Tenn. Code Ann. § 40-35-111(e)(2)—not a more specific claim-type rule.

In practice, that translates to: if your scenario doesn’t clearly map to a more specific limitations rule using the inputs available in the tool, the 1-year default is the logic that governs how timing affects the outputs.

4) Enter dates accurately (because 1 year is a tight window)

With a 1-year general default, small date differences can change results.

Use this checklist:

If DocketMath shows an “elapsed time” value or a “within SOL” / timing indicator, treat that as a quick validation step. If the indicator looks wrong, fix the date inputs before interpreting the allocation output.

5) Run the allocator

Click Calculate / Run Settlement Allocator.

As it runs, watch for:

• Any warning banner about missing required fields
• Any indicator that the Tennessee default (1-year) logic is being used
• Output sections that reflect whether timing affects allocations

6) Review the outputs and how they change

Settlement Allocator outputs typically include some combination of:

• Allocated amounts by component/category
• Remaining amounts after offsets
• Timing-dependent flags (for example, whether the input dates fall inside the limitations window)

What to look for specifically in Tennessee runs:

• Whether the tool treats your timing as within or outside the 1-year general default period
• Whether any category allocations change when the “within SOL” condition flips

If your results seem off, use this order of operations:

1. Dates first: confirm the start/end dates correspond to what the tool expects.
2. Offsets/adjustments second: ensure deductions and adjustments were entered consistently with your settlement documents.
3. Settlement total last: verify you entered the correct “gross” figure if the tool expects a gross settlement total (not net after fees, unless the tool explicitly asks for net).

7) Export or record results for your workflow

If DocketMath supports saving, exporting, or copying results:

• Save the run with a clear label (for example, “US-TN settlement allocation—default SOL 1 year”)
• Record the assumptions shown in the output (especially the SOL/timing indicator)

This makes it easier to rerun with updated dates or revised totals without losing context.

Common pitfalls

Tennessee-specific timing defaults can create errors that look “minor” in input but significant in output. Here are the most frequent issues people run into when running Settlement Allocator for US-TN.

Pitfalls to avoid

• Using the wrong “start date”

  • The tool’s timing logic depends on which date it treats as the trigger.
• Assuming a claim-type rule applies when the tool only has a general/default rule

  • Based on the provided jurisdiction data, no claim-type-specific sub-rule was found, so DocketMath uses the general/default 1-year period under Tenn. Code Ann. § 40-35-111(e)(2).
• Entering dates in the wrong format

  • Month/day swaps can silently move elapsed time across the 1-year boundary.
• Mismatching the settlement total

  • If the tool expects the “gross settlement total” and you input “net after fees,” allocations can be distorted.
• Forgetting offsets/adjustments

  • If your settlement agreement includes deductions, ensure DocketMath’s inputs reflect them consistently.

Quick verification checklist (before calculating)

Try it

Ready to run a Tennessee allocation on your own inputs?

1. Open Settlement Allocator: /tools/settlement-allocator
2. Select **Tennessee (US-TN)
3. Enter:

   • the settlement total
   • the relevant dates the tool prompts for
   • any offsets/adjustments you have
4. Run the calculator and review whether results reflect the 1-year general/default timing logic associated with Tenn. Code Ann. § 40-35-111(e)(2).

If you want a fast sanity-check:

• Change only one variable at a time (often the end date first)
• Re-run and confirm whether outputs shift in a predictable way when elapsed time crosses the 1-year threshold

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado