Slip and fall settlement guide for Tennessee

Direct answer

A Tennessee slip-and-fall settlement posture should account for comparative fault under Tenn. Code Ann. § 29-11-103 and the comparative-negligence framework discussed in McIntyre v. Balentine, 833 S.W.2d 52 (Tenn. 1992). Practically, the negotiation often turns on whether a factfinder could assign the injured person 50% or more fault, because that allocation drives (or can sharply limit) expected recovery.

In settlement terms, you typically model fault allocation alongside damages allocation—then negotiate using the range of outcomes that your evidence supports. DocketMath helps you do this quickly by letting you test multiple fault scenarios and see how settlement value changes as estimated fault changes.

What you need to know

Slip-and-fall cases in Tennessee are commonly resolved through two interacting parts of the settlement story: (1) the fault-allocation theory (who caused the fall and why), and (2) the damages reduction that follows from the injured party’s percentage of fault under Tenn. Code Ann. § 29-11-103, as framed in McIntyre v. Balentine, 833 S.W.2d 52 (Tenn. 1992).

1) Comparative fault reduction is the math driver

Under Tenn. Code Ann. § 29-11-103, a plaintiff’s damages are reduced based on the proportionate fault attributed to the injured person. That means your settlement value can move significantly even when medical treatment and injury severity are well documented—because fault allocation determines what the plaintiff can recover.

2) The allocation threshold matters for modeling

For Tennessee settlement modeling in DocketMath workflows, use a 50% bar threshold concept: if the injured person is found to have 50% or more fault, recovery may be cut off in the settlement math model you run. (This is an allocation modeling input, reflected in the safe facts for this guide.)

3) Settlements are typically negotiated across a fault “range”

Fault percentages are rarely exact early on; they’re debated based on:

• the condition and what caused it,
• notice/warnings (if any),
• visibility/lighting and how obvious the condition was,
• the plaintiff’s conduct at the moment of the fall (e.g., attention, footwear, distraction),
• witnesses or video, and
• credibility issues.

DocketMath supports this reality: you can run multiple scenarios (e.g., plaintiff 30%, 45%, 55% fault) and compare the modeled settlement value to see which narrative is most supported by your evidence.

Step-by-step

Here’s a practical, jurisdiction-aware workflow for using DocketMath to prepare a Tennessee slip-and-fall settlement position (US-TN).

Step 1: Gather the facts that will be used for fault allocation

Start by collecting the facts you’ll later map to fault arguments under Tenn. Code Ann. § 29-11-103 and the comparative-fault framework discussed in McIntyre v. Balentine, 833 S.W.2d 52 (Tenn. 1992 (as applicable to how comparative negligence is analyzed).

Use a quick checklist:

• Where did the fall happen (entryway, hallway, stairs, parking area)?
• What was the hazardous condition (wet floor, debris, uneven surface)?
• Was there a warning sign or barrier?
• How visible was the condition at the time?
• What was the plaintiff doing (walking normally, rushing, distracted)?
• Are there witnesses or video?
• Was there evidence of what the venue knew/should have known after notice?

Step 2: Create 2–3 structured fault scenarios (don’t rely on one number)

Before you run math, decide what you will test. For example:

• Scenario A (plaintiff-favorable): plaintiff 30% fault / defendant 70% fault
• Scenario B (mixed): plaintiff 45% fault / defendant 55% fault
• Scenario C (defense-favorable): plaintiff 55% fault / defendant 45% fault

You’re not “predicting the verdict.” You’re pressure-testing your settlement range against the comparative-fault impact—especially around the 50% modeling threshold.

Step 3: Break the damages into categories you can justify

DocketMath’s damages-allocation workflow is easier to defend if your claimed harm is organized into proof-based buckets. Typical slip-and-fall categories include:

• medical expenses (past)
• medical expenses (future, if supported)
• non-economic damages (e.g., pain and suffering, if your workflow supports it)
• other provable losses connected to the fall

For each category, keep your evidence notes close so you can explain and defend your assumptions during settlement.

Step 4: Run DocketMath in the damages allocation tool

Open the DocketMath calculator here: Damages Allocation Tool.

Then:

1. Enter damages amounts by the categories you identified.
2. Input comparative fault estimates for each scenario (Scenario A / B / C).
3. Ensure the tool settings are aligned to US-TN comparative-fault modeling consistent with Tenn. Code Ann. § 29-11-103 and McIntyre v. Balentine, 833 S.W.2d 52 (Tenn. 1992).

Step 5: Turn the outputs into settlement negotiation guidance

Once you run the scenarios, translate the results into negotiation strategy:

• If Scenario A yields meaningful value but Scenario C drops sharply, that’s a sign your strongest negotiation lever is keeping the plaintiff’s fault estimate below the 50% threshold by focusing on the evidence that supports defendant responsibility.
• If Scenario B and Scenario C are close in value, you may need to reevaluate whether your fault story has the evidentiary support you assumed.

Step 6: Document assumptions so your model stays consistent

Create a one-page assumptions summary you can reuse:

• the fault scenarios you tested (A/B/C),
• what evidence supports each scenario,
• and the range of modeled settlement values.

When new evidence arrives (video, witness updates, missing signage, clarification of lighting/visibility), rerun DocketMath rather than “eyeballing” the impact.

Key statutes and citations

Tennessee slip-and-fall settlement math in this guide is tied to comparative fault concepts:

• Tenn. Code Ann. § 29-11-103
  Comparative fault framework that reduces damages based on proportionate fault.

• McIntyre v. Balentine, 833 S.W.2d 52 (Tenn. 1992)
  Tennessee Supreme Court guidance discussed in connection with comparative negligence principles used to frame fault allocation analysis.

• Tenn. Code Ann. § 29-11-107
  Additional Tennessee authority referenced in the allowed packet for comparative-fault-related treatment.

For Tennessee legislation access: https://www.capitol.tn.gov/legislation/

Common pitfalls

1. Using a single fault estimate Negotiations often stall when only one percentage is proposed. Test at least 2–3 fault scenarios in DocketMath so you can show the settlement range that follows from Tenn. Code Ann. § 29-11-103 comparative-fault reduction.

2. Forgetting to test around the 50% threshold If you never run a scenario at/above 50% plaintiff fault, your internal numbers may overstate what settlement could reasonably look like.

3. Mismatch between damages assumptions and fault theory Medical documentation may be strong, but settlement math can still drop if the fault assumptions shift. Keep damages categories tied to evidence, and keep fault inputs tied to facts.

4. Weak mapping from facts to fault arguments “It was slippery” alone isn’t enough. Your fault inputs should connect to specific comparative-fault points like visibility, warnings, and plaintiff conduct at the time of the fall.

5. Not updating the model A new witness statement or video can shift fault allocation materially. Rerun DocketMath when key evidence changes.

Run the numbers

Use DocketMath to model how changes in fault allocation affect settlement value under Tenn. Code Ann. § 29-11-103.

Practical modeling structure (illustrative)

Assume total claimed damages before fault allocation = $100,000.

Test these fault allocations:

What to watch in the outputs

• Look for how modeled settlement value decreases as plaintiff fault increases.
• Pay special attention to behavior around the 50% bar threshold (e.g., sharp changes in modeled recovery when crossing that point).
• Use the sensitivity to decide what evidence you most need to emphasize to keep the plaintiff-fault estimate below 50%.

Quick checklist (numbers → negotiation messages)

• Can I justify Scenario A with specific evidence?
• Do I have facts that make Scenario B more likely than Scenario C?
• Did I connect each damages category to proof I can explain?
• Did I rerun the model after any evidence updates?

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance