How to run Offer Of Judgment Analyzer in DocketMath for Tennessee

Step-by-step

You can run the Offer Of Judgment Analyzer in DocketMath for Tennessee (US-TN) to model how Tennessee’s 10% per year interest language tied to judgment entry (or delayed entry) can affect the modeled recovery amount.

1) Start in the right tool

1. Open the primary call-to-action: /tools/offer-of-judgment-analyzer
2. Set the jurisdiction to Tennessee (US-TN).

   • DocketMath uses jurisdiction-aware rules so the calculation logic aligns with Tennessee’s offer-of-judgment statute framework.

2) Use the correct statute timing concept (Tenn. Code Ann. § 20-1-116)

Tennessee’s statute provides the default interest timing used in the analyzer’s Tennessee logic:

• Interest rate: 10% per year
• Interest starts from:

  • the date the judgment is entered, or
  • if there’s a delay in entry of judgment, from the date of the jury verdict or court ruling (as reflected in the statute text).

Because no claim-type-specific sub-rule was provided, treat this as the general/default period for the analyzer baseline logic.

Statute anchor: Tenn. Code Ann. § 20-1-116 (General default timing and 10% rate)
Source: https://law.justia.com/codes/tennessee/2022/title-20/chapter-1/part-1/section-20-1-116/

3) Enter the scenario inputs

In the analyzer, enter the facts the calculator needs to compute the interest impact tied to the judgment timeline. While labels can vary slightly by UI, the key inputs usually include:

• Offer amount (the proposed judgment amount)
• Judgment amount (the court’s entered judgment amount, used to model the “amount of the judgment” portion)
• Offer date
• Key decision dates, such as:

  • jury verdict date (if applicable)
  • court ruling date (if applicable)
  • judgment entry date
• If the interface asks you to choose how to handle delayed entry, select the interest-start basis that matches your timeline:

  • judgment entry date vs.
  • jury verdict or court ruling date (when entry is delayed)

If you don’t see a separate “delay” option, look for a selector (or implied logic) that changes the “interest starts” date. The goal is to match the start-date trigger described in § 20-1-116.

4) Watch the analyzer’s outputs update

After each input change, the analyzer should refresh its outputs. In a Tennessee scenario based on § 20-1-116, outputs commonly include:

• Interest start date (derived from your selected basis)
• Interest duration (time between the chosen start date and the tool’s interest endpoint)
• Projected interest amount using the fixed 10% per year rate
• A modeled total recovery component that combines:

  • the amount of the judgment, plus
  • the 10% annual interest projected from the statute’s start-date trigger

Since the rate is fixed, the biggest drivers are typically:

• how far apart the start date is from the tool’s interest endpoint, and
• whether you use judgment entry date or jury verdict/court ruling date when modeling “delay.”

5) Sanity-check your timeline before you rely on results

Before exporting, saving, or comparing scenarios, do a quick consistency check:

• Does the interest start date occur on or before the endpoint date the tool uses?
• Are your dates in a logical chronological order?
• If you include both verdict and ruling dates, confirm your selection matches the outcome you’re trying to model (especially if you’re testing a “delayed entry” theory).

6) Save or compare scenarios

A practical workflow is to run at least two variants:

• Scenario A (judgment entry basis): interest starts from the judgment entry date
• Scenario B (delay basis): interest starts from jury verdict or court ruling when entry is delayed

Compare the modeled interest totals to see how sensitive the results are to the statute’s start-date trigger under Tenn. Code Ann. § 20-1-116.

Tennessee rule anchor (quick reference)

Tenn. Code Ann. § 20-1-116 provides, in part, that a party may recover:

• the amount of the judgment, plus
• interest at 10% per year on the judgment
• calculated from (1) the date judgment is entered, or (2) if delayed, from the date of the jury verdict or court ruling.

Source: https://law.justia.com/codes/tennessee/2022/title-20/chapter-1/part-1/section-20-1-116/

Common pitfalls

Running the analyzer successfully usually comes down to matching Tennessee’s timing language and avoiding input mismatches.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Pitfalls to watch

• Using only one date without aligning to the statute’s trigger

  • Tenn. Code Ann. § 20-1-116 contemplates two start-date paths: judgment entry vs. verdict/ruling date if entry is delayed.
• Mixing up “verdict,” “ruling,” and “judgment entry”

  • Verdict/ruling can occur earlier than judgment entry. If the analyzer asks you to select the interest-start basis, be consistent with the timeline you’re modeling.
• Assuming a different interest rate

  • Tennessee’s rate here is 10% per year (based on the statute text). If results look off, check whether the analyzer is set to the Tennessee rules and that no other override is selected.
• Assuming claim-type-specific sub-rules exist

  • For this Tennessee brief, no claim-type-specific sub-rule was provided, so the default period described in the statute text should govern the baseline logic described here.
• Date chronology errors

  • If the interest start date ends up after the tool’s endpoint, the calculation may become incorrect or fail validation.

Quick checklist before you submit

Try it

If you want a fast, hands-on run, use this mini test plan to see how the results change:

1. Open **/tools/offer-of-judgment-analyzer
2. Keep Tennessee selected (US-TN).
3. Enter a simple scenario designed for easy sanity-checking:

   • Choose a round judgment amount (e.g., 100,000)
   • Enter an interest start basis using:

     • Scenario A: judgment entry date
     • Scenario B: jury verdict/court ruling date (delay basis)
4. Verify the outputs reflect:

   • 10% per year
   • a different modeled interest amount between Scenario A and Scenario B, driven by the shifted start date.

What you should expect to change

Because the statutory rate is constant, your results should primarily react to:

• the interest start date, and
• the elapsed time between that start date and the tool’s interest endpoint.

If you keep the same start and endpoint dates across both scenarios, totals should match (aside from rounding). If you change the start date basis, interest totals should diverge.

How to interpret results without overreaching

DocketMath’s analyzer output is best understood as a modeled estimate grounded in statute text timing and rate. It doesn’t replace a court’s discretion or a full legal analysis of issues like procedural eligibility and enforceability.

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado