How Offer Of Judgment Analyzer rules vary in Tennessee

What varies by jurisdiction

Offer-of-judgment rules can look “universal” at a glance, but the details that control the math are jurisdiction-specific—especially deadlines, who may use the rule, and how costs and “timing windows” are applied. For Tennessee, DocketMath’s Offer Of Judgment Analyzer uses the Tennessee Civil Procedure Rule governing offers: Tenn. R. Civ. P. 68.

Tennessee’s baseline rule (general/default timing)

In Tennessee, no claim-type-specific sub-rule was found for the offer timing. That means the default framework governs when calculating eligibility and timing for offers under Tenn. R. Civ. P. 68.

Under Tenn. R. Civ. P. 68, a party defending against a claim may serve an offer “at any time more than 10 days before the trial begins.” The rule also contemplates judgment on the offer’s specified terms, including “costs then accrued.”

Practical impact for your analysis:

• If your offer was served 10 days or fewer before trial, DocketMath’s analyzer should flag it as outside Tennessee’s window, because the rule requires more than 10 days before the trial begins.
• If your offer was served more than 10 days before trial begins, the analyzer can proceed under the baseline assumptions for Tennessee’s timing structure.

Why this matters in the output

DocketMath’s Offer Of Judgment Analyzer turns those timing requirements into:

• Eligibility flags (for example, “served too late to qualify under TN R. Civ. P. 68 timing”)
• Cost-and-effect calculations that depend on the offer date and trial start date inputs
• Summary reasoning that ties the results back to the Tennessee rule framework

Even if the offer amount looks “right,” the offer can be treated as non-qualifying if the timing window is missed. And because other jurisdictions can use different day-counts or different definitions of when the “trial begins,” the same dates can produce different analyzer results across jurisdictions.

Tool entry point (DocketMath)

Start with the DocketMath calculator here: /tools/offer-of-judgment-analyzer.

What to verify

To make Tennessee-specific results accurate, verify these items before relying on the analyzer output. Treat this as a practical checklist you can run against your case file (not legal advice).

1) The offer is served by the correct procedural posture

Tenn. R. Civ. P. 68 describes offers served by the party “defending against a claim.” If the offer you’re entering was served by a plaintiff (or otherwise doesn’t match the defending posture), the analyzer may still calculate numbers, but the “rule-fit” interpretation may not reflect how Tennessee’s mechanism is intended to apply.

Checklist

• Confirm who was “defending against a claim” when the offer was served
• Confirm the offer is structured as an offer to allow judgment on the specified terms (money/property or its effect), consistent with the rule framing

2) The offer service date is more than 10 days before trial begins

This is the Tennessee timing anchor.

Rule mechanic (timing):

• Serve the offer “at any time more than 10 days before the trial begins.”

Checklist

• Identify the trial beginning date your case calendar uses (not just a preliminary event)
• Compute the day difference between the offer service date and the trial beginning date
• Ensure the result is strictly greater than 10 days (e.g., 11 days qualifies; 10 days does not)

3) Costs “then accrued” and what you model for costs

The rule text includes “with costs then accrued.” Your analyzer inputs should align with how your workflow captures costs as of the offer date.

Checklist

• Indicate whether you’re modeling costs then accrued as of the offer date (per the analyzer’s cost handling approach)
• Confirm what cost categories you included (if your process separates costs from other amounts)

4) No claim-type-specific timing rule found (baseline assumption)

For Tennessee, the analyzer’s timing logic should be treated as the default, because no claim-type-specific sub-rule was found for this period.

Checklist

• Don’t switch timing windows based solely on claim labels unless you have additional Tennessee authority for that specific scenario
• Use the baseline “more than 10 days” window for Tenn. R. Civ. P. 68 timing calculations

5) Confirm the analyzer configuration is Tennessee (US-TN)

Since Offer Of Judgment Analyzer behavior can differ by jurisdiction, confirm these settings.

Checklist

• Jurisdiction code: US-TN
• Rule source in the calculator: Tenn. R. Civ. P. 68 (Tennessee Civil Procedure, Rule 68)

How DocketMath changes results in Tennessee

When you use DocketMath’s Offer Of Judgment Analyzer for Tennessee, the output typically becomes more sensitive to a few inputs than people expect.

Inputs that most affect TN calculations

Output interpretation (practical)

Use the analyzer results to do two things:

1. Sanity-check timing under Tenn. R. Civ. P. 68’s “more than 10 days before the trial begins” requirement.
2. Compare offer terms vs. case outcome using the Tennessee cost-and-effect framing.

Because the rule depends heavily on timing eligibility, DocketMath’s most actionable part is often the “rule-fit” component (for example, whether the offer qualifies under Tennessee’s mechanism), not just the raw arithmetic.

Related reading

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

Sources and references

• Tenn. R. Civ. P. 68 (Tennessee Courts) — https://www.tncourts.gov/rules/rules-civil-procedure/68

  • Quoted timing language used: “At any time more than 10 days before the trial begins…”
• TODO: If you need deeper analysis of the TN Rule 68 “effect” and cost-shifting consequences beyond the quoted excerpt, pull the full Rule 68 text and reconcile it with the specific outcome you are modeling in DocketMath.