How to run Treble Damages in DocketMath for Tennessee

Step-by-step

Use DocketMath’s Treble Damages calculator for Tennessee (US-TN) to estimate 3× damages and to see how Tennessee treats trebling as automatic under one statute versus discretionary (up to 3×) under another. This guide is about running the calculator and selecting the right jurisdiction-aware option—not about legal advice.

Before you start, keep this baseline in mind:

1) Open the Treble Damages tool

1. Go to the tool page: /tools/treble-damages
2. Confirm the jurisdiction is set to Tennessee (US-TN).

If the UI asks you to choose a jurisdiction again inside the calculator, select US-TN there as well—don’t assume it will carry through from the page level.

2) Choose the trebling basis (automatic vs. discretionary)

Tennessee’s statutes you provided point to two different trebling patterns:

In DocketMath, reflect this by selecting the matching basis (or “rule”) for the scenario you’re modeling:

• For an automatic 3× scenario, choose the § 47-50-109-type option when available.
• For a TCPA willful/knowing scenario, choose the § 47-18-109-type option and plan for the possibility that the result may be less than 3×, because it’s discretionary.

Key warning: Don’t mix assumptions. Modeling § 47-50-109 automatic 3× while telling yourself the court has discretion (or vice versa) can change how you present the numbers internally.

3) Enter the core amounts the calculator needs

Most treble calculators require at least:

• a base damages amount (the “1×” number), and
• sometimes additional fields for adjustments (fees, costs, offsets), depending on the tool’s structure.

Use these practical steps:

• Base damages: Enter the single (1×) damages figure you want trebled.
• Pre- vs. post-credits: If you already netbed payments or offsets, enter the net amount you expect to be recoverable so the treble calculation matches your intended outcome.
• Multiple components: If the tool doesn’t support separate line items, combine the components you intend to be part of the “base” into a single base number.

If you’re unsure what the tool expects, do a quick sanity check first: a $10,000 input should produce a clean $30,000 treble outcome for a true 3× basis.

4) Set any timeline/assumption options shown in the UI

Some tools include toggles that affect how totals are framed (for example, whether you’re modeling a guaranteed treble or an “up to” maximum).

For § 47-18-109 (TCPA), model it as:

• Maximum: 3× base damages
• Potentially lower: the award may be less than 3× because the multiplier is discretionary

If DocketMath provides an option like “show up to 3×” or “range/discretionary,” use it so your output matches Tennessee’s discretionary framing for willful/knowing TCPA violations.

5) Run the calculation and review outputs

After you click calculate, review that you’re getting the outputs you expect.

Common outputs include:

• 1× base damages
• 3× treble amount (or “up to 3×” maximum, depending on the basis)
• Total treble damages (the final recovery figure shown)

For workflow consistency (especially if you anticipate back-and-forth on the trebling theory), save both:

• the base (1×) number, and
• the trebled (3×) number (or the max treble number in a discretionary scenario)

That way, if you need to change the selected statute basis later, you can quickly re-run without losing your original assumptions.

6) Use the jurisdiction-aware explanation to sanity-check

DocketMath’s US-TN jurisdiction-aware logic should align with the statutes you’re modeling:

• Tenn. Code Ann. § 47-50-109 → trebling treated as automatic 3× for procurement of contract breach/refusal/failure to perform.
• Tenn. Code Ann. § 47-18-109 → TCPA trebling treated as discretionary up to 3× for willful/knowing violations.

If the calculator lets you switch bases, compare the results and ensure the difference matches what you intended:

• one path should look like a straight 3× outcome,
• the TCPA path should show “up to” or discretion framing.

For reference, the statutes you provided are:

• Tenn. Code Ann. § 47-50-109 (procurement of breach of contract — automatic 3×): https://law.justia.com/codes/tennessee/2010/title-47/chapter-50/47-50-109/
• Tenn. Code Ann. § 47-18-109 (TCPA — discretionary up to 3× for willful/knowing violation)

Common pitfalls

Below are practical errors that commonly lead to incorrect treble estimates in a calculator run. These are input/logic issues—not legal determinations.

1) Double-counting by entering already-trebled damages

If your base damages field already contains a 3× total, the tool will apply trebling again.

Checklist:

• You entered the 1× base damages amount
• You didn’t paste a “total treble” figure into the base field
• You didn’t accidentally enter the same component (e.g., fees) twice

2) Choosing the wrong Tennessee trebling basis

• § 47-50-109 is tied to procurement of breach/refusal/failure to perform of a lawful contract.
• § 47-18-109 is tied to TCPA willful/knowing violations (discretionary “up to” trebling).

Pitfall pattern: selecting the TCPA/discretionary basis but expecting an automatic guaranteed 3×, or selecting the automatic contract-procurement basis while your facts are actually TCPA-related.

3) Treating “up to 3×” as guaranteed 3× (TCPA discretion)

For § 47-18-109, your model should communicate that the multiplier is discretionary.

In practice, that means:

• use the tool’s maximum treble output for the up-to-3× figure, and
• don’t present it as a guaranteed award unless your inputs reflect something beyond discretion (the tool won’t do that for you automatically).

4) Not aligning inputs with willful/knowing TCPA modeling

Even for a “math only” run, your basis selection should track whether you’re modeling willful/knowing TCPA trebling.

If DocketMath includes a “willful/knowing” toggle or selection, use it. If it doesn’t, at least note internally which basis you chose in the run.

5) Assuming the tool will change trebling by claim subtype

Because you were told that no claim-type-specific sub-rule was found, the calculator should not silently swap to a different trebling period based on hidden claim subtypes.

So if you need a different modeling outcome, it should come from:

• selecting a different statute basis/rule inside the tool, or
• adjusting your inputs—not expecting an automatic hidden override.

Try it

Use this quick test to verify your Tennessee setup in DocketMath:

1. Set the jurisdiction to US-TN in the Treble Damages tool.
2. Choose one basis first:

   • § 47-50-109 type (automatic 3×), or
   • § 47-18-109 type (TCPA discretionary up to 3×)
3. Enter a simple base damages number first—try $10,000.
4. Run the calculation and confirm the arithmetic behavior:

   • Automatic 3× basis should yield $30,000
   • Discretionary basis should show $30,000 maximum and may show “up to” framing rather than a guaranteed award

Then repeat with a second number (for example $2,500) and switch bases again. If the outputs don’t scale exactly by 3× (or show “up to 3×” for the discretionary basis), revisit:

• whether you entered a 1× base,
• and whether you selected the correct Tennessee trebling basis option.

Related reading

• How to calculate Treble Damages in Texas — Full how-to guide with jurisdiction-specific rules
• [How to calculate Treble Damages in Philippines]