How to calculate attorney fee in Tennessee

Quick takeaways

• In Tennessee, attorney fees in contingency matters are evaluated under Tenn. Sup. Ct. R. 8, RPC 1.5 using a reasonableness approach—not a one-size-fits-all percentage formula.
• If your case is a health care liability action with a contingency fee, Tennessee imposes a 33 1/3% cap on contingency attorneys’ fees tied to damages awarded to the claimant.
• DocketMath’s US-TN attorney-fee calculator should be modeled using the correct branch:

  • General contingency (RPC 1.5 reasonableness), or
  • Medical malpractice / health care liability contingency (statutory cap behavior).
• For Tennessee multiplier modeling, DocketMath’s configuration includes lodestar_multiplier_cap.default_multiplier = 1 (i.e., the tool should not inflate results via a multiplier above 1).

Inputs you need

Before you use DocketMath’s US-TN attorney-fee calculator at /tools/attorney-fee, gather the facts that drive the Tennessee-specific fee model. The calculator can’t reliably infer these from other inputs.

A. Identify the fee type (controls the rule branch)

• General contingency fee (RPC 1.5 reasonableness applies)
• Health care liability action with a contingency fee (statutory cap behavior applies)

If you’re not sure whether your claims qualify as a health care liability action, resolve that classification from the pleadings and claims first—otherwise any computed fee estimate may be based on the wrong Tennessee branch.

B. Damages base (required when the cap branch applies)

• All damages awarded to the claimant (the amount you’ll apply to the cap calculation)

C. Lodestar-style inputs (use if your workflow includes lodestar modeling)

Depending on your approach in DocketMath, you may need:

• Reasonable time and effort devoted to the litigation (e.g., hours × rates, if using a lodestar-style workflow)
• Complexity of the claim (often used qualitatively in reasonableness modeling)
• Other pertinent matters affecting reasonableness

D. Multiplier inputs and limits (DocketMath-specific behavior)

• Confirm whether your run uses default multiplier behavior

  • DocketMath includes lodestar_multiplier_cap.default_multiplier = 1 for the US-TN flow

E. Medical-malpractice contingency cap override (when applicable)

• Confirm whether your run activates the medical malpractice override

  • DocketMath includes contingency_fee_cap.claim_type_overrides.medical_malpractice.max_percentage = 33.33

How the calculation works

DocketMath’s Tennessee attorney fee calculation works like a jurisdiction-aware rule router: it selects a cap model or a reasonableness model depending on the case type you choose.

1) Choose the Tennessee rule path: cap vs. reasonableness

If this is a health care liability action with a contingency fee

Tennessee uses a reasonableness framework for determining reasonable attorneys’ fees based on factors such as:

• time and effort devoted to the litigation
• complexity of the claim
• other pertinent matters

However, for this contingency setting, the resulting contingency fee amount cannot exceed 33 1/3% of all damages awarded to the claimant.

In DocketMath, that statutory cap behavior is implemented using:

• max percentage = 33.33

Cap-branch math (practical):

1. Identify Damages Awarded (to the claimant).
2. Compute Cap Amount = Damages Awarded × 33.33%.
3. Ensure the modeled fee output does not exceed the cap.

If this is not a health care liability contingency

For general contingency arrangements, Tennessee applies RPC 1.5 reasonableness. In practice, that means the output is modeled as a reasonableness-driven estimate rather than a fixed statutory percentage.

2) Use damages as the anchor (when the cap applies)

When the 33 1/3% cap branch is active, changes in your damages input should affect the cap amount predictably:

3) Apply multiplier logic cautiously (DocketMath cap is 1)

If your DocketMath workflow uses multiplier concepts in a lodestar-style process, the Tennessee configuration includes:

• lodestar_multiplier_cap.default_multiplier = 1

So, for the US-TN attorney-fee calculator, you should expect the multiplier behavior not to push results above the modeled cap logic via enhancement above 1.

If you see an output that looks “inflated” compared to how you expect Tennessee to behave, first confirm you are using the US-TN calculator path and that the Tennessee default multiplier cap setting is in effect.

4) Reconcile “reasonableness” with the medical cap (two layers)

In a health care liability contingency setting, two ideas may coexist:

• The fee determination considers time and effort, complexity, and other pertinent matters (reasonableness factors).
• But the contingency fee amount still can’t exceed the 33 1/3% of damages awarded ceiling.

So, even if a reasonableness-driven estimate trends higher, the cap branch should act as an upper bound in the DocketMath model.

5) Use DocketMath outputs as estimates—not guarantees

Treat DocketMath results as:

• a structured estimate of what the Tennessee branch allows, and
• a comparison point for settlement budgeting, internal modeling, or case evaluation.

To keep results trustworthy:

• ensure your case classification (medical vs. general contingency) is correct
• ensure your damages anchor matches the tool’s intent for the cap calculation
• ensure any multiplier inputs align with Tennessee’s configured behavior (1)

Common pitfalls

Here are frequent causes of Tennessee attorney-fee calculation mismatches in DocketMath workflows:

1. Using the general contingency path for a health care liability action

   • Result: you may miss the 33 1/3% cap behavior.

2. Applying the cap to the wrong damages number

   • The cap is based on damages awarded to the claimant. If your “damages” input doesn’t match that concept, the cap math will be off.

3. Letting multiplier behavior drift above Tennessee’s modeled default

   • DocketMath includes lodestar_multiplier_cap.default_multiplier = 1 for this configuration.
   • If your run implies higher enhancement behavior, verify you’re using the correct US-TN tool flow.

4. Failing to activate the medical-malpractice contingency override when appropriate

   • If the medical-malpractice override isn’t engaged, the tool may not enforce 33.33% cap behavior.

5. Assuming RPC 1.5 means a fixed percentage

   • Under Tenn. Sup. Ct. R. 8, RPC 1.5, the general approach is reasonableness, not a simple fixed contingency percentage.

Sources and references

• Tenn. Sup. Ct. R. 8, RPC 1.5 — https://www.tncourts.gov/rules/supreme-court/8
• TODO: Confirm and link the official Tennessee Code page for the health care liability contingency fee cap referenced in the verified authorities packet (Tenn. Code citation details are present in the packet, but the tool requires that only verified source URLs be used).

Next steps

1. Open DocketMath’s US-TN attorney-fee calculator: /tools/attorney-fee
2. Select the correct fee path:

   • Use the health care liability cap branch when the cap applies.
   • Otherwise use the RPC 1.5 reasonableness branch for general contingency modeling.
3. Enter inputs:

   • Damages awarded to the claimant (for the cap branch)
   • Any time/effort/complexity/other pertinent matters inputs you’re using for reasonableness modeling
4. Check your output:

   • If the medical cap branch is active, the computed contingency fee should not exceed the cap enforced by 33.33%.
   • Verify multiplier behavior stays consistent with default_multiplier = 1.

Related reading

• Attorney fee calculations in United States (Federal) — Full how-to guide with jurisdiction-specific rules
• Why attorney fee calculations results differ in United States (Federal) — Troubleshooting when results differ
• Attorney fee calculations reference snapshot for United States (Federal) — Rule summary with authoritative citations