How Offer Of Judgment Analyzer rules vary in Tennessee

What varies by jurisdiction

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Offer of judgment rules can change in meaningful ways between states, even when the tool you’re using (here, DocketMath’s Offer Of Judgment Analyzer) shows a similar workflow. For Tennessee (US-TN), the core statutory framework you’ll want to map your timelines to is Tenn. Code Ann. § 20-1-116, which governs when a party can recover the judgment amount plus interest at 10% per year, measured from the appropriate procedural milestone.

Because Tennessee’s statute (as provided in your source text) is not claim-type-specific, the main “variation” for your calculator in Tennessee is typically how the interest start date is anchored, not whether a different rule applies based on claim category. In other words: follow the general/default period unless another Tennessee provision or a specific procedural posture changes the timing.

Tennessee baseline: interest on the judgment (general/default rule)

Under Tenn. Code Ann. § 20-1-116, a party may recover:

• the amount of the judgment, and
• interest at 10% per year on the judgment,

with interest calculated from:

• the date the judgment is entered, or
• if there is a delay in entry of judgment, from the date of the jury verdict or ruling of the court that results in entry of judgment.

Practical translation for DocketMath: the analyzer needs a timing anchor to determine whether it should start interest on judgment entry or, if entry was delayed, on the verdict/ruling.

Important clarity: Per your note, no claim-type-specific sub-rule was found in the Tennessee statutory text you provided. So Tennessee’s treatment here should be applied as a general/default rule for the analysis in this article (rather than creating separate claim-category branches).

How jurisdiction-aware rules change outputs (what changes numerically)

Even when offer-of-judgment mechanics look similar across states, Tennessee can produce a different interest output if the timeline facts differ. In DocketMath, “jurisdiction-aware rules” for Tennessee generally means:

• it uses the correct interest rate for the jurisdiction (10% per year under § 20-1-116), and
• it chooses the correct interest start date logic:

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

So if two scenarios share the same judgment amount and the same offer/response timing, your results can still differ due to delays in judgment entry—because that changes the date from which interest accrues.

What to verify

Before you run DocketMath’s Offer Of Judgment Analyzer for Tennessee, verify the items below so the tool can correctly apply Tenn. Code Ann. § 20-1-116.

• The governing rule or statute for the jurisdiction.
• Any local rule overrides or administrative guidance.
• Effective dates and whether amendments apply.

1) Confirm the correct “interest start” anchor (judgment entry vs. verdict/ruling)

Tennessee’s statute sets different measurement points depending on whether entry of judgment was delayed.

• Use Judgment entered date if judgment was entered without relevant delay.
• Use Jury verdict date or court ruling date if judgment entry was delayed.

Checklist (Tennessee timing):

2) Ensure the interest rate aligns with the Tennessee statute (10% per year)

Your Tennessee calculation should reflect:

• 10% per year interest on the judgment

A common practical error is to substitute a different post-judgment interest figure from a different statute/context. For this article’s purposes, the relevant figure you cited is the § 20-1-116 interest language: 10% per year.

3) Confirm you’re applying the general/default rule (no claim-type-specific split based on provided text)

Because no claim-type-specific sub-rule was identified in the provided text of § 20-1-116, your Tennessee run should generally not require a special branch like “different interest periods for certain claim types.”

• If you see different behavior in the analyzer, it’s more likely driven by timing inputs and procedural posture (e.g., whether judgment entry was delayed), rather than claim category.

4) Map your inputs to the outputs you care about

In practice, your DocketMath output for Tennessee under § 20-1-116 typically tracks:

5) Keep terminology consistent in your case records

When you compile dates for the calculator, use consistent labels so you don’t accidentally switch the anchor. For example:

• “Order date” (ruling) vs. “judgment entered date”
• “Verdict date” vs. “ruling on verdict” vs. “entry of judgment”

This matters because § 20-1-116 hinges the calculation on the appropriate procedural milestone.

Sources and references

Start with the primary authority for Tennessee and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

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