Damages Allocation Guide for Indiana — Comparative Fault Rules

What this calculator does

Run this scenario in DocketMath using the Damages Allocation calculator.

DocketMath’s damages-allocation tool helps you allocate damages using Indiana’s modified comparative fault rules (often discussed as “comparative negligence” in negligence-based cases). The core idea is straightforward:

• Indiana uses a modified comparative fault system: the plaintiff’s recovery is barred only when the plaintiff is more than 50% at fault.
• If the plaintiff is 50% or less at fault, the damages award is reduced by the plaintiff’s share of responsibility.

This guide focuses on the damages-allocation math, not on proving fault or valuing injuries.

Indiana’s general limitations period (statute of limitations) is often a separate question. For reference, Indiana’s general SOL period is 5 years, governed by Indiana Code § 35-41-4-2:
https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/

There’s no claim-type-specific sub-rule provided here, so the content below uses that general/default 5-year period as the baseline.

To access the tool, open: /tools/damages-allocation.

When to use it

Use DocketMath’s damages-allocation tool when you have (or are working with) numbers that represent fault responsibility and you want to see the impact on recoverable damages under Indiana’s modified comparative fault framework.

Good fits

• You have an estimated plaintiff fault % and one or more defendant fault % figures (often from discovery, expert reports, or settlement discussions).
• The dispute is centered on comparative fault concepts (typical in many negligence and premises-related fact patterns).
• You’re doing scenario planning: “If the jury attributes 30% fault to the plaintiff, what happens?”

Not a fit (or needs a different framework)

• Cases where the dispute is not reasonably framed as comparative fault (for example, purely contractual allocation issues).
• Situations where fault percentages are unknown and would require substantial additional fact development.

Quick limitation reference (separate from fault math)

If you’re also checking timing, Indiana’s general statute of limitations is 5 years under Indiana Code § 35-41-4-2. The tool itself won’t calculate SOL; it’s mainly about allocation of damages. Still, knowing your timing baseline helps keep settlement and litigation planning coherent.

Step-by-step example

To use DocketMath, you’ll provide inputs such as:

• Total claimed damages (the “before reduction” amount)
• Plaintiff fault percentage
• Defendant fault percentage(s) (often the remainder)

Then the tool applies Indiana’s modified comparative fault logic:

• If plaintiff fault > 50% → plaintiff recovers $0
• If plaintiff fault ≤ 50% → plaintiff recovers **total damages × (1 − plaintiff fault%)

Example: Plaintiff is 35% at fault

Assume:

• Total claimed damages: $200,000
• Plaintiff fault: 35%
• Defendant fault: 65%

Step 1: Determine whether recovery is barred
35% is not more than 50%, so recovery continues.

Step 2: Reduce by plaintiff’s share
Reduced recovery = $200,000 × (1 − 0.35)
Reduced recovery = $200,000 × 0.65
Plaintiff’s estimated recoverable damages: $130,000

Step 3: Interpret what the number means
This $130,000 reflects fault reduction only, not:

• policy limits,
• offsets,
• liens,
• or evidentiary challenges.

Running the same number at 51% (barred case)

Now change only the plaintiff fault:

• Total claimed damages: $200,000

• Plaintiff fault: 51%

• Plaintiff fault is more than 50%

• Estimated recoverable damages: $0

Example table (same damages, different fault)

If you’re using DocketMath directly, your workflow usually looks like: open /tools/damages-allocation, enter the inputs, and compare outcomes across multiple fault estimates before you commit to settlement terms.

Common scenarios

Fault allocation questions usually come in a few predictable patterns. Below are practical scenarios and how the outputs generally respond when the plaintiff fault % moves.

Scenario 1: Multiple defendants (aggregate defendant fault)

Even when there are two or more defendants, comparative fault still centers on the plaintiff’s percentage. Many people enter defendant allocations that sum to 100% when combined with the plaintiff.

Example:

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

Output logic:
Plaintiff’s recoverable = $300,000 × (1 − 0.40) = $180,000

In practice, you’ll often see defendant shares used later for apportionment among defendants. DocketMath’s primary output is whether the plaintiff’s recovery is barred and what the plaintiff’s net recoverable amount becomes after plaintiff fault.

Scenario 2: Fault at the threshold (50% exactly)

Indiana’s modified comparative fault rule draws a line at “more than 50%.”

Example:

• Total damages: $80,000
• Plaintiff fault: 50%

Output:

• Plaintiff is not more than 50%
• Plaintiff recoverable = $80,000 × (1 − 0.50) = $40,000

This is a high-sensitivity zone for negotiations. If you’re modeling settlement positions, it can be useful to run:

• “plaintiff = 49%” and
• “plaintiff = 50%” and
• “plaintiff = 51%”

Scenario 3: Quick “break-even” planning

If you’re trying to understand how much damages reduction a claim might absorb, solve for a “break-even” fault concept using the same formula.

Formula:

• Recoverable = Total × (1 − plaintiff fault%)

Rearrange for a desired recoverable target:

• (Desired recoverable / Total) = 1 − plaintiff fault%
• plaintiff fault% = 1 − (Desired recoverable / Total)

Example:

• Total claimed damages: $250,000
• Target recoverable amount: $150,000
• plaintiff fault% = 1 − (150,000 / 250,000)
• plaintiff fault% = 1 − 0.60 = 40%

So in this planning scenario, keeping plaintiff fault at or below 40% yields at least $150,000 under fault-only math.

Scenario 4: “Why did my damages drop so much?”

Often the drop isn’t random—it’s proportional. A common shift:

• From 20% to 35% plaintiff fault
• Loss increases because plaintiff share increases.

Example:

• Total damages: $120,000
• At 20% fault → recoverable = 96,000
• At 35% fault → recoverable = 78,000
• Change = $18,000 drop, driven entirely by fault math.

Tips for accuracy

These tips help you enter inputs cleanly and interpret outputs correctly.

Input hygiene checklist

Interpreting outputs (what the number does and doesn’t include)

DocketMath’s output reflects fault allocation only under the comparative-fault logic. It does not automatically incorporate:

• insurance policy limits,
• medical bill admissibility issues,
• collateral source offsets,
• attorney fees arrangements,
• or statutory caps (if any exist for particular causes of action).

Keep timing separate from fault

Because Indiana’s general SOL period is 5 years under Indiana Code § 35-41-4-2, some users try to bundle timing and fault into one step. Don’t. In most workflows:

• fault % → determines damages reduction;
• filing deadline → determines whether the claim is time-barred.

A practical workflow

For settlement planning:

1. Enter base case fault estimate (e.g., 35%).
2. Enter a defense-favorable fault estimate (e.g., 45%).
3. Enter a worst-case threshold estimate (e.g., 51%).
4. Compare the delta in net recoverable damages.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules — Complete guide
• Damages Allocation Guide for Alaska — Comparative Fault Rules — Complete guide
• Damages Allocation Guide for American Samoa — Comparative Fault Rules — Complete guide