Slip and fall settlement guide for South Carolina

Direct answer

In South Carolina, slip-and-fall settlement value is shaped by S.C. Code Ann. § 15-38-15, which uses a comparative negligence framework that can reduce recovery and can bar recovery if the plaintiff’s share is high. For settlement math in US-SC, the key is to model how your fact record supports particular fault percentages—not just to list injuries.

You can translate those fault percentages into a settlement range with DocketMath using the jurisdiction-aware damages allocation workflow: /tools/damages-allocation.

What you need to know

Slip-and-fall settlements in South Carolina usually depend on two related workstreams:

1. Liability allocation (comparative fault)
2. Damages allocation (how you model the total value into categories for discussion)

DocketMath helps you keep those workstreams organized by giving you a consistent way to enter the same categories and compare multiple fault-percentage scenarios for a US-SC settlement posture.

Comparative fault affects the “recoverable” outcome

Because S.C. Code Ann. § 15-38-15 governs how comparative negligence impacts recovery, your settlement valuation will change when your assumed fault percentages change.

Practically, that means:

• If the plaintiff’s fault is modeled at or below the 51% bar threshold, the allocation may allow some recovery.
• If the plaintiff’s fault is modeled above that threshold, the modeled recovery can be blocked.

(That’s why scenario planning matters early—before you commit to a single demand figure.)

Evidence quality drives credible fault assumptions

Even strong medical documentation may not produce a strong settlement if the opposing side can credibly argue for a higher plaintiff-fault allocation. To keep fault assumptions defensible, focus on incident-specific proof such as:

• What condition existed (spill/debris/uneven surface), and how it was presented
• Notice issues (what the store/property knew or should have known)
• What the plaintiff did (footwear, attention to surroundings, whether the hazard was avoidable)

DocketMath can only reflect the fault inputs you choose—so your collection and organization of evidence determines how realistic those inputs are.

Step-by-step

Use this workflow to turn a slip-and-fall claim into settlement-ready allocation numbers in DocketMath (US-SC).

1) Build a fault-and-damages checklist before you run the tool

Create two short lists you’ll reuse across scenarios.

A. Fault inputs (who contributed to the loss)

• Premises actions or omissions (maintenance, cleanup, inspection practices)
• Hazard characteristics (visibility, location, duration indicators)
• Plaintiff conduct (watchfulness, footwear, choices made immediately before the fall)

B. Damages inputs (what the incident cost or worsened)

• Medical bills (keep dates/ranges so you can align items to your model)
• Lost wages / reduced work capacity evidence
• Non-economic impacts you intend to quantify in settlement discussions

The goal is not to “pick winners” yet—it’s to ensure your inputs are traceable to documents.

2) Prepare at least 2 fault allocation scenarios

Settlement discussions rarely progress smoothly on a single number. Build scenarios that reflect different plausible ways the fault story could be credited.

Start with:

• Scenario A: plaintiff fault at or below the 51% bar threshold
• Scenario B: plaintiff fault above the 51% bar threshold

This helps you avoid surprise later if the other side’s framing pushes fault above the modeled bar.

3) Open DocketMath and enter the US-SC inputs

Go to the allocation tool first: /tools/damages-allocation.

Then enter:

• Your comparative fault percentages for the scenario you’re modeling (consistent with S.C. Code Ann. § 15-38-15)
• The damages categories you want to allocate and discuss

Even if you’re not ready to settle, you should be able to use the output to understand what range is realistically available under each scenario.

4) Run the allocation and record the results

For each scenario:

• Save the allocation output (the adjusted/recoverable amount the tool shows)
• Note how the result changes when you shift plaintiff fault toward or beyond the 51% bar threshold

This gives you an internal “swing point” view—what assumptions change the settlement posture.

5) Connect the numbers to your evidence narrative

After you have scenario outputs:

• Choose the scenario that best matches the evidence you can actually support
• Confirm your narrative aligns with the fault assumptions (notice, hazard visibility, avoidance opportunity, and causation linkage)

Common alignment failure: the settlement model may show a favorable number, but the underlying fault inputs aren’t supported by the documents you plan to rely on in negotiation.

Key statutes and citations

South Carolina slip-and-fall settlement allocation is driven by the comparative negligence framework in:

• S.C. Code Ann. § 15-38-15 — the operative comparative negligence statute referenced for settlement allocation modeling in US-SC.
• S.C. Code Ann. § 15-38-15(F) — a subsection within S.C. Code Ann. § 15-38-15 that is part of the comparative negligence framework.
• Nelson v. Concrete Supply Co., 303 S.C. 243, 399 S.E.2d 783 (1991) — provides case context commonly associated with the South Carolina comparative fault landscape.

When you run DocketMath for US-SC, treat your fault inputs as a reflection of how your fact record could be credited under S.C. Code Ann. § 15-38-15, rather than as pure estimation.

Common pitfalls

These are the most common reasons slip-and-fall damages-allocation models don’t match what the other side will accept:

1) Using fault percentages that the record can’t support

• Example: setting plaintiff fault low because it “helps the math,” but ignoring deposition or incident details that could support higher fault.
• Result: the opponent treats your numbers as aspirational, not anchored.

2) Confusing “bigger medical value” with “higher recoverable value”

High treatment costs don’t automatically produce a high settlement allocation result if comparative fault reduces the modeled recovery under S.C. Code Ann. § 15-38-15.

3) Inconsistent damages category inputs

If you change categories between the demand packet and the tool run:

• your settlement arithmetic becomes hard to reconcile
• the other side can attack the mismatch and slow resolution

4) Not planning around the 51% bar threshold

If you only model one scenario (and it ends up above the 51% line), your settlement range can collapse without warning. Two scenarios early keeps your negotiation strategy grounded.

Run the numbers

DocketMath’s damages-allocation calculator helps you see how comparative fault assumptions change settlement outcomes in US-SC.

Quick modeling checklist (inputs to confirm)

Before running /tools/damages-allocation, verify:

• Plaintiff fault % aligns with your best-supported evidence theory under S.C. Code Ann. § 15-38-15
• Defendant fault % aligns with your premises evidence (condition, notice, maintenance/cleanup)
• Total damages are entered in consistent categories you intend to discuss
• You have at least two scenarios:

  • Scenario 1: plaintiff fault at or below the 51% bar threshold
  • Scenario 2: plaintiff fault above the 51% bar threshold

How to interpret output (what changes when fault changes)

When you compare Scenario A vs. Scenario B, focus on whether the modeled recoverable amount:

• remains meaningful under Scenario A
• drops materially and/or becomes barred under Scenario B (depending on the tool’s US-SC allocation mechanics tied to S.C. Code Ann. § 15-38-15)

Turn results into next negotiation steps

• If Scenario A produces a workable number, prioritize evidence that supports fault allocation consistent with that scenario.
• If Scenario B bars recovery in the model, you need to identify which fact assumptions are pushing fault above the 51% line and develop counter-proof for negotiation.

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