How to calculate Treble Damages in Tennessee

Quick takeaways

• Tennessee commonly uses two different “treble damages” mechanics:

  • Automatic 3× for procured breach of contract under Tenn. Code Ann. § 47-50-109.
  • Discretionary up to 3× for TCPA willful/knowing violations under Tenn. Code Ann. § 47-18-109.
• In DocketMath, the “treble” result is driven by:

  1. Which statutory path applies, and
  2. What base damages amount you are authorized to treble.
• Important default-period note: You did not identify a claim-type-specific timing/period sub-rule for treble damages in the provided data. So this guide treats any period/timing inputs as coming from the calculator’s general/default workflow, not a special Tennessee sub-rule for a particular claim type.
• Primary CTA: use DocketMath here: /tools/treble-damages

Inputs you need

To calculate treble damages in Tennessee with DocketMath, gather the inputs below first.

1) Treble rule selection (statute path)

Choose the Tennessee treble trigger you’re modeling:

• § 47-50-109 — Procured breach of contract (automatic 3×)
  Generally used where a person unlawfully induces/procures a breach or refusal/failure to perform a lawful contract.

• § 47-18-109 — TCPA (discretionary up to 3×)
  Used where the TCPA conditions are met and the violation is willful/knowing—and the court may award up to three times damages (not necessarily pegged at 3× in every scenario).

2) Base damages to treble

Provide the monetary base that the statute authorizes to be multiplied.

In most practical workflows, this is one of:

• a contract damages amount (e.g., unpaid amounts or other measurable monetary loss), or
• a TCPA damages amount that the TCPA provision authorizes.

In DocketMath, you’ll input:

• Base Damages ($) = the single number the calculator will treble.

3) Willfulness/knowing flag (only for § 47-18-109)

If you are modeling § 47-18-109, you typically need facts supporting the willful/knowing threshold.

In DocketMath terms:

• Willful/knowing?

  • Yes → the discretionary treble model (≤ 3×) is available.
  • No → you generally should not apply the “up to 3×” TCPA trebling logic.

4) Treble multiplier (3.0 vs. “≤ up to 3×”)

• For § 47-50-109, use 3.0 (automatic 3×).
• For § 47-18-109, use m ≤ 3.0 because the award is discretionary up to three times.

5) Scenario mode (recommended)

If you’re not sure which statutory hook a case will align with, run scenarios to avoid locking into the wrong multiplier.

A practical approach:

• Scenario A (contract procurement): model § 47-50-109 at 3×
• Scenario B (TCPA discretionary): model § 47-18-109 at ≤ 3× (for example, 2× and/or 3×, depending on how you want to scenario-test discretion)

Checklist:

• Select § 47-50-109 or § 47-18-109
• Enter Base Damages ($)
• If TCPA: set willful/knowing?
• Apply 3.0 for automatic; apply m ≤ 3.0 for discretionary
• Consider running more than one scenario

How the calculation works

DocketMath’s treble damages modeling for Tennessee can be expressed as a simple multiplier—but the multiplier logic depends on the statute path you select.

Step 1: Determine the Tennessee treble trigger

Your provided Tennessee statutes outline two distinct mechanics:

Step 2: Apply the treble formula

Once you enter Base Damages ($) into DocketMath, the treble calculation follows:

• Automatic 3× (for § 47-50-109)
  Treble Damages = Base Damages × 3.0

• Discretionary up to 3× (for § 47-18-109)
  Treble Damages = Base Damages × m
  where m is ≤ 3.0

Step 3: Use scenario testing when the statute hook is uncertain

Because Tennessee has more than one treble framework, the calculator will be more useful when you scenario-test rather than assume “treble = 3×.”

A common workflow:

• Compute 3× under § 47-50-109
• Compute 2× and/or 3× under § 47-18-109 (only if willful/knowing fits your facts)

Default period rule (jurisdiction note)

Your brief includes a clear instruction:

• “No claim-type-specific sub-rule was found. The above is the general/default period.”

So if DocketMath requests period inputs (for example, how damages are measured across time), treat those inputs using the calculator’s general/default approach rather than introducing a specialized Tennessee timing rule that isn’t supported by the provided data.

Practical warning: The biggest mistake people make is using 3.0 for every Tennessee “treble” calculation. For § 47-18-109, the statute is discretionary up to 3×, so your modeling should reflect m ≤ 3.0.

Common pitfalls

Below are the most frequent errors when users model treble damages in Tennessee using DocketMath.

1) Applying 3× to a pathway that is “up to 3×”

• § 47-50-109 → model exactly 3.0
• § 47-18-109 → model m ≤ 3.0 (and only if willful/knowing applies)

2) Trebling the wrong base number

Even with the right multiplier, the output will be wrong if Base Damages ($) is not the measure the statute authorizes.

Common base-damages confusion includes:

• mixing contract unpaid amounts with other losses inconsistently,
• combining damage components twice, or
• applying adjustments (like mitigation) to only part of the figure.

Mitigation for your workflow: apply any adjustments consistently before you enter Base Damages ($) into DocketMath.

3) Not running statute-specific scenarios

If the statutory hook is still uncertain, consider computing:

• Scenario A: § 47-50-109 at 3×
• Scenario B: § 47-18-109 at ≤ 3×

This helps prevent an all-or-nothing “single number” approach.

4) Inventing a timing/period rule that isn’t supported

Your jurisdiction note states no claim-type-specific sub-rule was found. Avoid adding a special “treble period” rule unless the statute text (or other reliable Tennessee-specific authority) explicitly supports it. Use DocketMath’s general/default period logic for any timing inputs.

Sources and references

• 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)

Disclaimer: This guide is for how to model treble damages in DocketMath using the statute mechanisms you provided. It is not legal advice.

Next steps

1. Open DocketMath treble damages tool: /tools/treble-damages
2. Select the Tennessee treble rule you are modeling:

   • § 47-50-109 → apply 3×
   • § 47-18-109 → apply m ≤ 3× (and set willful/knowing as appropriate)
3. Enter Base Damages ($) that the statute authorizes to be trebled.
4. If statute alignment is uncertain, run two scenarios (automatic vs. discretionary) and compare the range.

Related reading

• How to calculate Treble Damages in Texas — Full how-to guide with jurisdiction-specific rules
• How to calculate Treble Damages in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Treble Damages in Philippines — Worked example with real statute citations