Abstract background illustration for How to calculate Damages Allocation in Wisconsin

How to calculate Damages Allocation in Wisconsin

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Quick takeaways

  • Wisconsin’s damages allocation analysis in practice is tied to contributory negligence that is not “greater than” the defendant’s negligence. Wisconsin uses a comparative-negligence threshold under Wis. Stat. § 895.045.
  • The DocketMath Damages Allocation calculator for US-WI applies that jurisdiction-aware rule when you allocate responsibility between the claimant and the defendant.
  • If the claimant’s negligence is greater than the defendant’s negligence, recovery is barred under the statute’s plain terms. If the claimant’s negligence is not greater than the defendant’s negligence, recovery is allowed with a percentage reduction.
  • This is a general/default rule: you’re not selecting a claim-type-specific sub-rule for Wisconsin in this workflow (no claim-type-specific carve-outs were identified for the required statute citation you provided).

Note: This guide explains how to calculate and allocate damages percentages using the Wisconsin comparative-negligence threshold. It’s not legal advice.

Inputs you need

To run the DocketMath → Damages Allocation (US-WI) calculator (at /tools/damages-allocation), gather the items below. Having the numbers in writing reduces back-and-forth later.

1) Negligence percentages (must total to 100%)

You’ll typically need:

  • Claimant negligence % (e.g., plaintiff/driver/pedestrian): ____%
  • Defendant negligence % (e.g., defendant/owner/driver): ____%

In many workflows, those two add up to 100%. If your scenario includes multiple actors, consolidate to one claimant-side and one defendant-side total before entering numbers.

Checklist

  • Claimant negligence % = ______
  • Defendant negligence % = ______
  • Claimant % + Defendant % = 100%

2) Damages amount(s) to allocate

Choose the monetary basis you want allocated by negligence (often you’ll start with a combined damages figure).

Common starting inputs:

  • Total compensatory damages ($): ____
  • (Optional) Breakdown by category if your DocketMath workflow supports multiple lines (e.g., medical expense, property damage, wage loss):
    • Medical/health care: ____
    • Property damage: ____
    • Lost earnings: ____
    • Other: ____

Checklist

  • Total compensatory damages ($) entered
  • If using categories, each category entered consistently (and avoid double counting)

3) Threshold status (interpreted by the calculator using Wisconsin’s rule)

You generally don’t need to make a separate legal determination step if DocketMath calculates the threshold outcome for you. But you should be ready to interpret it:

  • If claimant negligence > defendant negligence, recovery is barred
  • If claimant negligence ≤ defendant negligence, recovery is allowed (with a reduction).

How the calculation works

DocketMath’s US-WI damages allocation logic follows the comparative-negligence threshold stated in Wis. Stat. § 895.045.

Step 1: Apply the statutory bar (“greater than” threshold)

Wisconsin provides (in substance): contributory negligence does not bar recovery when the claimant’s negligence was not greater than the negligence of the person against whom recovery is sought. The practical flip side is:

  • If the claimant’s negligence is greater than the defendant’s negligence, recovery is barred.

Here’s how that maps to your input percentages:

Claimant negligence %Defendant negligence %Recovery allowed?Why
50%50%YesClaimant is not greater than (equal)
49%51%YesClaimant is less than defendant
40%60%YesClaimant is less than defendant
51%49%NoClaimant is greater than defendant

Practical warning: small changes can flip the result because the statute uses a “not greater than” threshold. Make sure your negligence split is consistent with the evidence you’re modeling.

Step 2: Reduce damages when recovery is allowed

When recovery is allowed (claimant negligence is defendant negligence), the claimant’s recoverable damages are reduced proportionally.

A common way to think about this in the calculator is:

  • Allocated damages = Total damages × (Defendant negligence % / 100)

So:

  • If defendant is 60% responsible, the claimant recovers ~60% of the damages basis.
  • If defendant is 50% responsible, the claimant recovers ~50%.

Step 3: Allocate across categories (if you enter multiple lines)

If you input category totals (e.g., medical, property, lost earnings), DocketMath typically applies the same proportional reduction to each category so your totals stay consistent:

  • Allocated medical = Medical total × (Defendant % / 100)
  • Allocated property damage = Property total × (Defendant % / 100)
  • …and similarly for other categories.

Step 4: Interpret the output as a Wisconsin-aware result

After you enter:

  • claimant negligence %,
  • defendant negligence %,
  • and damages totals (or categories),

DocketMath should show, at minimum:

  • Recovery allowed / barred
  • Allocated damages total
  • (Optionally) category-level allocations

Sanity checks you can do quickly:

  • If the calculator says recovery barred, verify that claimant % > defendant %.
  • If the calculator says partial recovery, verify the allocation roughly matches Total × Defendant % (or the same percentage applied to each entered category).

Common pitfalls

Even in straightforward negligence splits, these mistakes commonly derail results.

1) Percentages that don’t reconcile

If you enter 35% claimant and 60% defendant, you’ve “lost” 5%. That may be appropriate for a broader multi-party model, but it can also distort allocation if you’re implicitly treating only two parties as the whole.

  • Confirm claimant % + defendant % = 100% (unless your workflow accounts for more actors)

2) Reversing claimant vs. defendant negligence

Wisconsin’s threshold depends on who is seeking recovery and who recovery is sought against. In DocketMath terms:

  • “Claimant negligence %” should match the person seeking recovery.
  • “Defendant negligence %” should match the person against whom recovery is sought.

If you swap them, the “greater than” bar can flip.

3) Assuming shared negligence always means you recover something

Wis. Stat. § 895.045 is not purely “comparative.” It includes a bar when claimant negligence is greater than defendant negligence.

  • Pitfall: Don’t stop at “both sides were negligent.” Under the statute, the claimant may still recover $0.

4) Double counting damages

Avoid entering both:

  • total compensatory damages and
  • categories that sum to the same total,

unless your workflow is explicitly designed for that structure. It will overstate allocated damages.

5) Treating Wisconsin as claim-type-specific (without support)

For this calculator workflow, the statute citation you provided supports the general/default comparative-negligence threshold. No claim-type-specific sub-rule was identified for this required Wisconsin rule, so don’t invent extra cutoffs.

Sources and references

  • Wis. Stat. § 895.045 (comparative negligence threshold)
    https://docs.legis.wisconsin.gov/statutes/statutes/895/iv/045
    Key excerpt (summary of provided text): contributory negligence does not bar recovery when the claimant’s negligence was not greater than the negligence of the person against whom recovery is sought.

Next steps

  1. Open the DocketMath Wisconsin calculator: /tools/damages-allocation
  2. Enter:
    • claimant negligence %,
    • defendant negligence %,
    • and your damages basis (total or categories).
  3. Run the calculation and review:
    • If it shows recovery barred, confirm claimant % > defendant %.
    • If it shows recovery allowed, check whether allocated damages are roughly Total × Defendant % (and category allocations follow the same pattern).
  4. If you’re comparing scenarios, change only one input at a time (e.g., claimant % from 49% → 50%) to see how the “not greater than” threshold affects the outcome.

Related reading