Worked example: Closing Cost in Tennessee

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

This worked example shows how DocketMath’s Closing Cost calculator can be used in Tennessee (US‑TN) while applying Tennessee’s jurisdiction-aware rules.

Because your brief specifies no claim-type-specific sub-rule was found, the example uses the general/default period rather than any narrower category. Tennessee’s relevant general/default period is:

Also note the jurisdiction data you provided:

  • General SOL Period: 1 years
  • General Statute: **Tenn. Code Ann. § 40-35-111(e)(2)

To make the calculator run concrete, we’ll choose simple numbers consistent with common closing-cost modeling workflows (you can replace them with your actual figures). This is a calculation walkthrough, not legal advice.

Scenario setup (example case)

Assume:

  • Closing date (start of the timeline we’re measuring): April 15, 2025
  • Amount associated with the closing-cost calculation base: $12,000
  • Closing cost percentage (or rate applied to the base): 6%
  • Taxable portion flag: Yes (so the calculator includes the applicable adjustment logic within the closing-cost model)
  • Filing/notice timing: At closing (so no additional delay input is added)

Inputs to enter in DocketMath

Use these example inputs when you open the tool at:

Checklist of example inputs:

Note: This walkthrough demonstrates how the Tennessee jurisdiction setting and the general/default period (per Tenn. Code Ann. § 40-35-111(e)(2)) are used. It does not determine eligibility, liability, or enforceability—use it as a workflow reference, not legal advice.

Example run

Now let’s run the numbers through DocketMath’s Closing Cost calculator using the inputs above.

Run the Closing Cost calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Compute the core closing cost

Using the base amount and the rate:

  • Base amount: $12,000
  • Closing cost rate: **6% (0.06)

Core closing cost:

  • $12,000 × 0.06 = $720

So, before any additional adjustments, DocketMath’s closing-cost model starts at:

  • Core closing cost: $720

Step 2: Apply taxable portion adjustment (based on the tool’s closing-cost logic)

Because the input says “Apply taxable portion adjustment: Yes,” DocketMath includes the taxable adjustment portion in the model.

In this worked example, we’ll reflect that with a simplified adjustment factor consistent with typical closing-cost modeling workflows:

  • Example taxable adjustment factor: +2% of the core closing cost

Adjustment amount:

  • $720 × 0.02 = $14.40

Total closing cost output:

  • $720 + $14.40 = $734.40

DocketMath output (rounded to cents): $734.40

Step 3: Confirm the Tennessee “general/default period” setting

DocketMath’s jurisdiction-aware rules include a time-period component. For Tennessee, your brief specifies:

  • General SOL Period: 1 years
  • Rule reference: **Tenn. Code Ann. § 40-35-111(e)(2)

Because no claim-type-specific sub-rule was identified, the tool applies the general/default period.

That means, from the start date (2025-04-15), a 1-year period ends on:

  • 2026-04-15 (one-year mark)

Even if the dollar output is primarily driven by base and rate, the modeled time window can still matter for workflow logic inside the tool—such as whether an event is treated as within the relevant timeframe.

Warning: This example uses the general/default period because your research did not identify a narrower sub-rule. If a specialized category applies to your fact pattern, results may change—confirm the correct rule set for your situation.

What the tool is effectively combining

In plain terms, the DocketMath run combines:

  1. Money math (base × rate)
  2. Adjustment logic (taxable portion on/off)
  3. Tennessee jurisdiction timing logic using 1-year default tied to **Tenn. Code Ann. § 40-35-111(e)(2)

Sensitivity check

Next, let’s stress-test the result with changes that typically move the output the most. In DocketMath’s closing-cost workflow, the biggest drivers are usually:

  • the base amount
  • the rate/percentage
  • whether a taxable adjustment is applied
  • the jurisdiction-aware time component (here: the general/default 1-year period)

A) Change the base amount (+25%)

Keep everything else the same (rate 6%, taxable adjustment Yes).

  • New base amount: $12,000 × 1.25 = $15,000
  • Core closing cost: $15,000 × 0.06 = $900
  • Taxable adjustment: $900 × 0.02 = $18.00
  • New total: $900 + $18.00 = $918.00

Result moves from $734.40 → $918.00
That’s a gain of $183.60.

B) Change the closing cost rate (6% → 5%)

With original base ($12,000) and taxable adjustment Yes:

  • Core closing cost: $12,000 × 0.05 = $600
  • Taxable adjustment: $600 × 0.02 = $12.00
  • New total: $600 + $12.00 = $612.00

Result moves from $734.40 → $612.00

C) Turn off the taxable adjustment (Yes → No)

Keep base $12,000 and rate 6%:

  • Core closing cost: $720
  • Taxable adjustment: $0
  • New total: $720.00

Result moves from $734.40 → $720.00
In this example, the taxable adjustment accounts for $14.40.

D) Time component sensitivity (date shift across the 1-year mark)

The general/default period is 1 year under Tenn. Code Ann. § 40-35-111(e)(2) (as provided).

Compare two trigger dates:

Start date1-year endpoint (general/default)Practical effect in the model
2025-04-152026-04-15Event falls within the modeled 1-year window
2026-05-012027-05-01A later trigger may fall outside the window when compared to an external deadline

DocketMath’s dollar figure may not change if only the start date shifts, but the timing logic can affect whether the modeled event is treated as “within” the jurisdiction-aware window. So track both:

  • Closing-cost dollars (base/rate-driven), and
  • Timing compliance within the 1-year general/default period.

Pitfall: Some users focus only on the dollar output and ignore the date window. If the modeled timeline affects “timeliness” flags inside DocketMath, the scenario can change even when base × rate stays the same.

Related reading