Damages Allocation Guide for South Dakota — Comparative Fault Rules

8 min read

Published March 22, 2026 • By DocketMath Team

What this calculator does

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s damages-allocation tool helps you estimate how total damages might be allocated between parties in a South Dakota case using comparative fault concepts. The core idea is straightforward:

  • The trier of fact assigns fault percentages to each responsible party.
  • The calculator applies those percentages to the claimed total damages to estimate each side’s share of liability.

In South Dakota, the comparative fault framework is built into the state’s civil negligence approach, codified in SDCL 22-14-1. While this tool focuses on allocation math (not case strategy), it uses the key allocation principle: a plaintiff’s recovery is reduced in proportion to the plaintiff’s fault.

Note: This guide is for modeling and planning. It’s not legal advice, and it won’t substitute for a lawyer’s review of case-specific facts, evidentiary issues, or jury instructions.

What the tool outputs (typical)

Depending on how your inputs are structured, the calculator generally produces:

  • Plaintiff damages estimate = Total damages × (1 − plaintiff fault %)
  • Defendant damages estimate(s) = Total damages × defendant fault %
  • Checks that help catch unrealistic inputs (like fault percentages that don’t add up to 100%)

Related reading

When to use it

Use DocketMath’s damages allocation calculator when you need a defensible first-pass allocation model for a South Dakota negligence case. It’s especially helpful when you have:

  • A draft comparative fault discussion (e.g., “plaintiff is 30% at fault”)
  • Multiple defendants with known fault estimates
  • Negotiation documents that require numerical allocation ranges
  • A damages spreadsheet that already has totals, but not fault-adjusted figures

Apply it early—then refine

You’ll get the most value by running the model:

  • Before writing a demand letter or settlement memo
  • After initial fault hypotheses are developed
  • After receiving any preliminary fault findings (e.g., from mediation briefs or expert reports)

Use the general limitation period for timing (if you’re modeling a claim window)

For timing purposes, South Dakota’s general statute of limitations is 3 years under SDCL 22-14-1. The jurisdiction data provided here does not identify a claim-type-specific sub-rule, so the safest way to state this is:

  • Default SOL: 3 years for the general rule under SDCL 22-14-1
  • No claim-type-specific sub-rule identified in the information provided, so this guide treats 3 years as the default

Warning: Limitations periods can turn on the exact claim type and legal theory. This calculator is about damages allocation math—not SOL compliance or deadline strategy.

Step-by-step example

Below is a realistic, numbers-first walkthrough showing how fault percentages affect the damages allocation in South Dakota.

Scenario

  • Total claimed damages: $200,000
  • Plaintiff fault: 25%
  • Defendant fault: 75%

Assume a single defendant for simplicity. (If multiple defendants exist, you’ll allocate the defendant side across them using their separate percentages.)

Step 1: Enter the inputs

In DocketMath’s damages-allocation tool, you would supply inputs like:

  • Total damages: 200000
  • Plaintiff fault %: 25
  • Defendant fault %: 75

If you’re entering multiple defendants, split the defendant fault:

  • Defendant A: 50%
  • Defendant B: 25%

Step 2: Run the allocation

The calculator applies proportional allocation:

  • Plaintiff recovery estimate
    = $200,000 × (1 − 0.25)
    = $200,000 × 0.75
    = $150,000

  • Defendant liability estimate
    = $200,000 × 0.75
    = $150,000 total apportioned to defendants

Step 3: Sanity-check the fault math

A common modeling check is whether fault adds up properly:

ItemFault %
Plaintiff25%
Defendant (single)75%
Total100%

If your percentages don’t total 100%, the tool may:

  • normalize them (depending on configuration), or
  • flag an error so you can correct the inputs.

Step 4: Read the output as an estimate

The calculator’s numbers reflect allocation math. They do not automatically incorporate:

  • caps on certain damages types
  • evidentiary disputes about causation or damages
  • offsets, settlements, or collateral sources
  • apportionment by the trier of fact beyond the percentages you input

Common scenarios

South Dakota comparative fault models frequently show up in several patterns. The calculator can accommodate most of these as long as you can express fault as percentages.

1) Plaintiff fault reduces recovery (single defendant)

  • Plaintiff fault: 10%
  • Defendant fault: 90%
  • Total damages: $80,000

Expected math:

  • Plaintiff recovery = $80,000 × (1 − 0.10) = $72,000
  • Defendant liability allocation = $72,000 (under this simple one-defendant model)

Key takeaway: even modest plaintiff fault reduces the plaintiff’s share.

2) Shared fault with multiple defendants

  • Total damages: $300,000
  • Plaintiff fault: 40%
  • Defendant A: 35%
  • Defendant B: 25%

Expected math:

  • Plaintiff recovery = $300,000 × 0.60 = $180,000
  • Defendant A allocation = $300,000 × 0.35 = $105,000
  • Defendant B allocation = $300,000 × 0.25 = $75,000
PartyFault %Allocation of $300,000
Plaintiff40%$180,000 recovery (plaintiff share)
Defendant A35%$105,000
Defendant B25%$75,000
Total fault100%$360,000 (illustrative if you compare “recovery” vs. total modeled allocations)

Careful: the “plaintiff recovery” figure is not an additional pot separate from total damages—it’s the reduced recovery after plaintiff fault. The defendant allocations sum to the same reduced total in a clean one-pool model.

3) Plaintiff is assigned 0% fault

  • Total damages: $150,000
  • Plaintiff fault: 0%
  • Defendant fault: 100%

Expected math:

  • Plaintiff recovery = $150,000 × (1 − 0) = $150,000
  • Defendant allocation = $150,000

This is a good scenario for verifying that your inputs match the intended baseline.

4) Plaintiff is assigned 100% fault

  • Total damages: $120,000
  • Plaintiff fault: 100%
  • Defendant fault: 0%

Expected math:

  • Plaintiff recovery = $120,000 × (1 − 1.00) = $0
  • Defendant allocation = $0

5) Fault percentages don’t add to 100%

This is common when:

  • you’re estimating from witness testimony,
  • you have partial fault hypotheses,
  • you’re missing a non-party allocation component.

Checklist before running the tool:

  • Do you have enough parties identified to express all fault?
  • Are there any “unknown” or “unallocated” fault components you should incorporate?
  • Have you converted fractions to percentages correctly?

Pitfall: If you enter fault that sums to 90% or 110%, you can accidentally model an artificial “extra fault” or artificially reduce liability. Fix the percentages first, then rerun.

6) Modeling different fault outcomes (range estimates)

Settlement work often uses ranges, such as:

  • Low: plaintiff 20% fault
  • Mid: plaintiff 30% fault
  • High: plaintiff 45% fault

You can run the calculator multiple times with the same total damages but different fault inputs, then compare output.

Example with total damages = $200,000:

  • Low (20%): plaintiff recovery = $200,000 × 0.80 = $160,000
  • Mid (30%): plaintiff recovery = $200,000 × 0.70 = $140,000
  • High (45%): plaintiff recovery = $200,000 × 0.55 = $110,000

This approach helps you quantify how sensitive the settlement math is to fault assumptions.

Tips for accuracy

Getting the math right depends on clean inputs and consistent assumptions.

1) Use one total damages figure, consistently

Pick a single total damages number for the model, such as:

  • economic damages only, or
  • economic + non-economic damages (if you’re modeling both)

Mixing categories without clarity can produce misleading output.

2) Match your fault basis to the damages model

If your fault percentages are for:

  • liability only (causation + breach), but your damages figure includes unrelated harms, the allocation won’t align with the real case theory.

A quick internal alignment check:

  • “Do my fault inputs describe the same conduct that caused the damages I totaled?”

3) Keep units clean

  • Percentages should be whole numbers (e.g., 25 for 25%), or decimals (e.g., 0.25)—but use one convention consistently.
  • Dollar amounts should be in the same currency and not partially adjusted (e.g., don’t mix inflated dollars with discounted dollars).

4) Confirm fault totals before interpreting results

A simple pre-run checklist: