Pre/Post-Offer Damages Split Guide for Tennessee

What this calculator does

DocketMath’s Pre/Post-Offer Damages Split Guide for Tennessee (calculator: /tools/pre-post-offer-damages) helps you divide a damages amount into two time-based portions:

• Pre-offer damages: the portion attributed to the time before a settlement “offer” date
• Post-offer damages: the portion attributed to the time after the offer date

In Tennessee, this split is commonly used in contexts where a court’s later determination can change the consequences of recovery depending on whether the plaintiff accepted an offer or recovered a greater amount. One key Tennessee rule governing the relevant time window is:

• Tenn. Code Ann. § 40-35-111(e)(2) — 1-year period (with an exception labeled V2 in this project’s jurisdiction data)
  Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Additionally, your jurisdiction data indicates a second Tennessee limitations/cutoff reference:

• Tenn. Code Ann. § 40-2-102(a) — 1-year period (with an exception labeled V3 in this project’s jurisdiction data)

This guide is designed to help you structure the calculation and understand what you’re splitting—without giving legal advice.

When to use it

Use DocketMath’s pre/post-offer damages split when your workflow requires a time-based division anchored to an “offer” date. Typical triggers include:

• You’re preparing a damages schedule for an evaluation that depends on pre- vs. post-offer timing.
• You have a known total damages figure but need to allocate it by date relative to an offer.
• You must produce a supportable timeline for a settlement-related comparison (for example, “before the offer” vs. “after the offer”).

Tennessee-specific timing window to keep in mind

Your calculator and supporting workflow should reflect the 1-year limitation period shown in your jurisdiction data:

• Tenn. Code Ann. § 40-35-111(e)(2): 1 year
• Tenn. Code Ann. § 40-2-102(a): 1 year

Because both are labeled with 1-year periods in your Tennessee configuration, the safest practical approach is to:

• Ensure your date inputs are complete (start date, offer date, end date)
• Confirm whether your damages model assumes the relevant period is capped at 1 year for purposes of the split

Step-by-step example

Below is a concrete example showing how the pre/post split changes when the offer date shifts. You can mirror this structure using DocketMath’s calculator at:

• Primary CTA: /tools/pre-post-offer-damages

Example inputs (scenario)

Assume you have:

• Total damages claim (amount): $90,000
• Damages accrual start date: 2025-01-01
• Offer date: 2025-07-01
• Damages measurement end date: 2025-12-31

Assume the model divides damages proportionally by time between dates (i.e., based on days).

Step 1: Compute the day counts

• From 2025-01-01 to 2025-07-01 (pre-offer): 181 days
• From 2025-07-01 to 2025-12-31 (post-offer): 184 days
• Total days: 365 days

Step 2: Allocate the total across the split

• Pre-offer damages
  = $90,000 × (181 / 365)
  = $44,616.44 (rounded)

• Post-offer damages
  = $90,000 × (184 / 365)
  = $45,383.56 (rounded)

Example output (what you’d report)

Common scenarios

Below are practical scenarios where the split behaves differently, and what to double-check before running the calculator.

Scenario A: Offer date falls outside the damages measurement window

If your offer date is earlier than your accrual start or later than your end date, the split becomes one-sided.

Checklist:

• 100% pre-offer (offer after end), or
• 100% post-offer (offer before start)

Scenario B: Your damages window is capped by a 1-year rule

Because your Tennessee configuration includes 1-year periods under:

• Tenn. Code Ann. § 40-35-111(e)(2) (1 year)
• Tenn. Code Ann. § 40-2-102(a) (1 year)

…you may need to cap the measurement window to 365 days (or to an exact day span that matches the dates used in the framework) for purposes of the split.

Checklist:

Scenario C: Multiple offers (sequential splits)

If you have more than one offer date (e.g., Offer #1 and Offer #2), do separate splits rather than forcing everything into one allocation unless your model specifically supports it.

Recommended workflow:

Scenario D: Partial damages inputs (line items)

If your total damages figure is made of multiple components (for example, medical expenses vs. wage loss), you typically get the most defensible result by splitting each component separately and then summing.

Checklist:

Tips for accuracy

Use these to keep your inputs consistent and your split defensible.

1) Define the “damages accrual” dates precisely

The split depends on dates, not just months.

2) Confirm day-count conventions (especially around the offer date)

Even when using proportional-by-day logic, day-count conventions can change outcomes by a few hundred dollars at scale.

Practical actions:

3) Match the 1-year configuration to your measurement window

Your Tennessee data includes 1-year references via:

• Tenn. Code Ann. § 40-35-111(e)(2) (1 year)
• Tenn. Code Ann. § 40-2-102(a) (1 year)

So before you rely on the numeric output:

4) Re-run after correcting only one input

When something looks off, change one variable at a time:

5) Use a reconciliation step

After running the split, reconcile:

Related reading

• Pre/Post-Offer Damages Split Guide for Alabama
• Pre/Post-Offer Damages Split Guide for Arizona
• Pre/Post-Offer Damages Split Guide for California