How to run Settlement Allocator in DocketMath for Tennessee

Step-by-step

You can use DocketMath’s Settlement Allocator for Tennessee (US‑TN) by following a jurisdiction-aware workflow. This guide explains how to run the calculator and what Tennessee’s governing rule does for timing and allocation mechanics. This is general procedural guidance, not legal advice.

1) Open the tool and select the correct calculator

1. Go to the primary call-to-action: /tools/settlement-allocator
2. Confirm you’re using the Settlement Allocator calculator (not a general totals tool).

2) Confirm Tennessee jurisdiction settings (US‑TN)

Within the tool, locate the jurisdiction selector and choose:

• Jurisdiction: Tennessee
• Jurisdiction code: US‑TN

If the tool asks you to pick a ruleset/version, choose the option labeled for Tennessee (US‑TN). This ensures the calculator applies Tennessee-specific logic tied to Tenn. R. Civ. P. 23.

3) Understand the Tennessee rule period the allocator uses

For Tennessee, the relevant framework comes from Tenn. R. Civ. P. 23 (Civil Procedure—Class Actions). In this project’s jurisdiction data, no claim-type-specific sub-rule was found. That means the allocator uses the general/default period tied to Rule 23 rather than a claim label–specific period.

Important: The Tennessee configuration uses the general/default class-action period under Tenn. R. Civ. P. 23 because no claim-type-specific sub-rule was identified in the provided jurisdiction data. So you should not expect different timing/period inputs based on claim type labels inside the tool for Tennessee.

4) Enter allocation inputs (what to provide)

Settlement allocation depends on the eligibility structure and how the settlement fund should be distributed. Provide inputs that match your settlement agreement and class-action setup.

Typically, DocketMath’s Settlement Allocator will need, at minimum:

• Total settlement amount (the fund to be allocated)
• Number of claimants / eligible recipients (or the recipient structure the tool supports)
• Weights, share factors, or claim values (whatever fields the calculator requests)
• Any provided caps/floors (if your agreement includes limits)
• Eligibility/class membership filters (if supported)

Practical tip: If you have multiple groups (e.g., by status or damages measure), enter them as separate categories/rows (or whatever structure the calculator expects). Avoid mixing distinct groups into one figure, because that can change the proportional weights and therefore the outputs.

5) Run the calculation

After inputs are complete:

1. Click Calculate (or the tool’s equivalent).
2. Review the computed results on-screen, usually including:

   • Per-recipient or per-category allocation
   • Proportional factors / normalization logic
   • Any rounding adjustments (especially when distributing a single fund across many shares)

6) Check the Tennessee-specific outputs for consistency

Because the Tennessee ruleset is anchored in Tenn. R. Civ. P. 23, validate that the allocator’s results match the structure you intended.

Use this quick checklist:

• Eligible coverage: Are all intended recipients included based on your eligibility criteria?
• Correct “default period” assumption: Does your settlement documentation align with the tool’s general/default period approach (not claim-type-specific periods)?
• Total reconciliation: Do the allocations sum to the settlement amount (allowing for expected rounding)?
• Unexpected zeros: Do any categories/recipients show zero allocation due to weighting/eligibility rules you intended?

7) Export or save your output

If the tool supports it, export or download your results (often PDF/CSV). Also consider saving:

• the input values you used, and
• the output snapshot for auditability and comparison

If you re-run, keep changes minimal and record what you changed (for example: updating category weights or recipient counts).

Common pitfalls

Settlement allocation is usually straightforward when your inputs mirror the settlement agreement and class-action structure. For Tennessee (US‑TN), watch for these common issues:

1. Assuming claim-type-specific timing exists in the tool

   • The Tennessee configuration relies on Tenn. R. Civ. P. 23 using the general/default period because no claim-type-specific sub-rule was identified in the jurisdiction data.
   • If your settlement agreement uses different time periods by claim label, the tool’s default logic may not replicate that nuance.

2. Double-counting recipients

   • If the input form allows multiple categories, it’s easy to place the same claimant/recipient into two categories.
   • Overlaps happen when eligibility definitions were imported or translated from multiple sources.

3. Rounding drift

   • Even correct allocations can produce small dollar/cent differences due to rounding.
   • If the tool provides a “rounding adjustment” line, don’t manually override it without confirming where the residual was applied.

4. Using an incorrect settlement base amount

   • Verify whether the settlement amount should be treated as:

     • gross vs. net, and
     • inclusive vs. exclusive of administration costs, certain fees, or deductions specified in the agreement.
   • Using the wrong base number can cause outputs that don’t match the settlement paperwork—even if the allocator’s math is consistent.

5. Failing to reconcile totals

   • Always confirm that the sum of all allocations matches the settlement amount (within expected rounding).

Try it

Ready to run Settlement Allocator for Tennessee (US‑TN)?

1. Open /tools/settlement-allocator
2. Select Tennessee (US‑TN) as the jurisdiction.
3. Enter:

   • total settlement amount
   • eligible recipients/categories
   • weights/share factors as requested by the calculator
4. Click Calculate and review:

   • per-category/per-recipient allocations
   • total reconciliation
   • any rounding adjustments

When you review results, keep this in mind:

• The calculator’s Tennessee setup is grounded in Tenn. R. Civ. P. 23.
• Because no claim-type-specific sub-rule was found for Tennessee in this configuration, expect a single general/default period approach, not claim-type-specific period customization.

For rule reference, see: Tenn. R. Civ. P. 23
https://www.tncourts.gov/rules/rules-civil-procedure/23

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations