Breakup & Fee Clauses Calculator Guide for Tennessee

What this calculator does

Run this scenario in DocketMath using the Breakup Fee Clauses calculator.

DocketMath’s Breakup & Fee Clauses Calculator (for Tennessee, US-TN) helps you model contract provisions that include (1) “breakup”/termination-related clauses and (2) fee/shifting/cost reimbursement concepts tied to a breakup or early termination event.

In Tennessee, the practical problem is often timing: many parties want to know how long they have to act after a triggering event and whether a clause’s timing aligns with Tennessee’s post-conviction timelines or other procedural deadlines.

This guide is designed to pair two things:

• Calculator inputs (the clause trigger date, relevant event date, and the clause-based deadline mechanics you enter)
• Tennessee deadline constraints using the cited statutes below, so you can sanity-check the result against commonly applied timing rules

Key Tennessee timeline reference used in this calculator guide:

• Tennessee Code Annotated § 40-35-111(e)(2) — sets a 1-year limitations period, with stated exceptions (the data you provided labels this as exception V2)
  Source: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/
• Tenn. Code Ann. § 40-2-102(a) — also reflected in your provided rules as a 1-year limitations period (labeled exception V3)

If you want the calculator directly, use: /tools/breakup-fee-clauses.

When to use it

Use DocketMath’s Breakup & Fee Clauses Calculator when you have a contract (or related dispute posture) where:

• A specific “breakup” event is identified (termination, rescission, failed closing, default, repudiation, or similar)
• A clause references:

  • a deadline to demand payment or initiate an action after the breakup trigger
  • a fee component (attorneys’ fees, costs, reimbursement, liquidated amounts, or other compensation that becomes due upon breakup)
• You want to compare your clause timeline against Tennessee’s 1-year post-trigger limitation framework referenced by:

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

Checklist: good candidates for calculator modeling

Step-by-step example

Below is a fully worked example using the Tennessee-focused timelines you provided (both relevant entries are 1-year). I’ll show how the inputs you enter change the outputs the calculator produces.

Assume this situation:

• A contract includes a breakup provision that triggers when a party provides written notice and the deal fails to close.
• The agreement says the breakup-related payment demand must be made within the applicable deadline window.
• You want to model whether a demand date fits within the 1-year limitations period framework reflected in the Tennessee statutes used by this guide.

Example dates

• Breakup trigger date (event date): January 15, 2025
• Notice sent: January 20, 2025
• Demand/action date you plan: January 10, 2026

Statutory timing framework used here (1-year)

• Tenn. Code Ann. § 40-35-111(e)(2) — 1-year limitations period, with exceptions (exception V2)
• Tenn. Code Ann. § 40-2-102(a) — 1-year limitations period (exception V3)

How to translate into calculator inputs

When you open DocketMath’s calculator (/tools/breakup-fee-clauses), you typically provide:

1. Trigger/starting date: the date the breakup event occurs (January 15, 2025)
2. Deadline rule: the clause-based period you’re testing (e.g., “within 1 year” as modeled against Tennessee’s 1-year entries)
3. Planned action date: the date you want to submit the demand/action (January 10, 2026)

What you should expect as outputs

Because both Tennessee entries in your provided data are 1-year, the calculator will model a “latest permissible date” around:

• January 15, 2026 (the 1-year anniversary of the trigger date)

Then it checks whether your planned action date (January 10, 2026) falls before that modeled deadline.

Example output logic (illustrative)

Now change one input to see how results shift

Suppose instead you planned to act on:

• Planned action date: January 20, 2026

This is the practical value of the calculator: small date shifts can flip a modeled “in time” result.

Common scenarios

Breakup and fee clauses show up in several recurring patterns. Here are common Tennessee deadline-modeling situations where the calculator can clarify how timing changes your outcome.

1) Trigger date is ambiguous (notice vs termination)

Scenario

• The clause says breakup happens “upon notice,” but you may disagree on whether it happens on notice date or termination date.

Calculator approach

• Run two models:

  • Start date = notice date
  • Start date = termination/effective date

Output you’re looking for

• Which model keeps the planned demand/action inside the 1-year window referenced by Tenn. Code Ann. § 40-35-111(e)(2) or § 40-2-102(a).

2) Clause includes a shorter internal deadline than the statutory model

Scenario

• Agreement requires action “within 90 days,” but Tennessee’s referenced timing framework is 1 year.

Calculator approach

• Enter the clause deadline first (e.g., 90 days) and compare it to the 1-year model separately.
• If the clause deadline expires earlier, your “real” risk may be the clause itself even if a longer statutory model exists.

3) Fee shifting depends on who initiates the breakup

Scenario

• The fee clause triggers only if Party A initiates a breakup or if the breakup is “for cause.”

Calculator approach

• Use separate runs for each path:

  • model where you initiate breakup
  • model where the other side initiates breakup
• Track which date is the true “trigger” for each path.

4) Multiple breakup events occur

Scenario

• First default notice is sent, then a second event occurs later (cure fails, final termination happens).

Calculator approach

• Treat each event as its own potential trigger:

  • Run a model for Event 1 → demand date
  • Run a model for Event 2 → demand date

Output you’re looking for

• Whether your planned action ties to the earlier or later trigger changes whether you’re within the modeled 1-year deadline.

5) Clause uses “business days” or counts days differently

Scenario

• “Within 30 business days” can shift deadlines compared to “calendar days.”

Calculator approach

• If the calculator supports day-counting, align your entry to the clause language.
• If it doesn’t, manually convert to calendar dates for the modeling run.

Tips for accuracy

Use the following practices to get trustworthy outputs from DocketMath’s calculator and avoid common timing mistakes.

1) Confirm the trigger date you’re using

Before running the calculator, write down the trigger date definition from your clause:

• Is the start date:

  • notice date?
  • termination effective date?
  • breach date?
  • demand date?

Then be consistent across all scenarios you model.

2) Run “sensitivity tests” with realistic alternatives

A quick way to stress-test your result is to run 2–3 variants:

• Trigger date + 5 days
• Trigger date − 5 days (if defensible)
• Planned action date + 7 days

If outcomes flip repeatedly, you may need to tighten your factual record on the actual triggering event date.

3) Keep a decision log

Track your runs like this:

• Trigger date used:
• Clause deadline used:
• Planned action date:
• Output: in time / out of time

This makes it easier to explain the timeline logic later.

Related reading

• Breakup & Fee Clauses Calculator Guide for Alabama
• Breakup & Fee Clauses Calculator Guide for Arizona
• Breakup & Fee Clauses Calculator Guide for California