Slip and fall settlement guide for Wisconsin

Direct answer

In Wisconsin, contributory negligence does not bar recovery in a negligence case (including a slip-and-fall claim) if the fact-finder determines your negligence was not greater than the defendant’s under Wis. Stat. § 895.045. Put simply, Wisconsin applies a “greater than” threshold: when the plaintiff’s fault is 50% or less, recovery is generally allowed but typically reduced to reflect fault; when it is greater than 50%, recovery is barred.

What you need to know

Wisconsin slip-and-fall settlement negotiations usually turn on two linked issues:

1. Fault allocation: What percentage of negligence each side is assigned (plaintiff vs. defendant).
2. Damages allocation: What losses are claimed and how they are quantified (medical bills, wage loss, and negotiated non-economic damages like pain and suffering).

Settlement talks can stall when the parties disagree on things like:

• whether the plaintiff’s negligence could be found to be greater than the defendant’s (which can trigger a bar under Wis. Stat. § 895.045),
• whether specific treatment and time off work are properly connected to the fall,
• whether the medical record and timeline are consistent (for example, immediate symptoms vs. later complaints).

A practical way to keep negotiations moving is to package evidence in a form that supports straightforward fault and damages inputs:

• Create a fact timeline (when the hazard existed, when it was noticed, what the plaintiff did).
• Build damage evidence by category with dates and amounts.
• Convert that evidence into calculator-ready inputs for DocketMath.

DocketMath’s role in settlement planning (practical workflow)

Use DocketMath to translate your evidence into clear, adjustable settlement numbers you can discuss with precision. The goal is to model how results change when:

• the plaintiff fault assumption is 49% vs. 51%,
• medical and wage numbers shift,
• you tweak non-economic damages assumptions.

If you want to run the calculator-driven part, start with: /tools/damages-allocation.

Step-by-step

Use this settlement-focused workflow for Wisconsin slip-and-fall cases. Adjust the steps depending on whether you’re at the demand stage, responding to a denial, or preparing for mediation.

1) Identify the negligence themes you’re negotiating around

Even if you don’t frame every legal argument explicitly, you should understand what will matter to fault allocation, such as:

• Notice/foreseeability: How long the condition existed and whether it should have been discovered.
• Cause of the fall: Surface condition, lighting, footwear, distractions, and movement patterns.
• Reasonableness of the plaintiff’s conduct: Whether the plaintiff acted as an ordinary person would under the circumstances.

These themes generally influence the fault percentages that control settlement viability under Wisconsin’s rule.

2) Build a fault allocation “scenario set”

Because Wis. Stat. § 895.045 uses a “not greater than” threshold, you should test outcomes around the dividing line.

Create at least three scenarios:

• Scenario A: Plaintiff fault = 45%
• Scenario B: Plaintiff fault = 50%
• Scenario C: Plaintiff fault = 55%

Then document what evidence supports (or undermines) each fault assumption.

3) Collect damages evidence by category (with dates)

Organize settlement inputs so you can defend them quickly. A practical checklist:

• Medical bills: provider statements and dates of service
• Paid vs. owed amounts: confirm totals (some insurers pay directly)
• Future treatment estimates (only if used): rely on documentation/records that support it
• Lost wages: pay stubs, employer letters, and dates missed
• Mileage/transportation: receipts if you plan to include them
• Non-economic damages: pain and suffering amounts used for negotiation (often less “bill-based,” more scenario-based)

This is where DocketMath helps: you enter the evidence-supported figures and see how changing fault and damages assumptions alters the allocation outcome.

4) Confirm the “default” contributory negligence rule you’re applying

For this Wisconsin contributory negligence threshold, the provided guidance is:

• Wis. Stat. § 895.045 (general/default rule framework for contributory negligence bar purposes)
• No claim-type-specific sub-rule was identified in the supplied statute excerpt.

So, for the purpose of this guide, treat Wis. Stat. § 895.045 as the general/default period and rule framework unless a different statute applies to a specific claim type.

5) Run DocketMath damages allocation across your fault scenarios

Use DocketMath to combine:

• your damages inputs (medical, wages, and non-economic components), and
• your fault assumptions (plaintiff vs. defendant percentages)

so you can produce allocation outputs that match your settlement posture.

Start here: /tools/damages-allocation.

6) Use the output to frame a settlement demand

After you run scenarios, translate the outputs into negotiation structure:

• Target demand: your most reasonable settlement based on the strongest evidence
• Walk-away floor: the point where fault + damages math makes the case unattractive
• Mediation number: often set between target and floor

If the other side argues for plaintiff fault above 50%, your numbers may become less relevant due to the statutory bar risk under Wis. Stat. § 895.045—so keep scenario documentation handy.

Key statutes and citations

Wisconsin contributory negligence / fault threshold

• Wis. Stat. § 895.045 — Contributory negligence; recovery allowed only if plaintiff’s negligence is not greater than the defendant’s

From the statute text provided:

• Recovery is allowed “if that negligence was not greater than the negligence of the person against whom recovery is sought…”
• And the contributory negligence rule is described as not greater than rather than “always reduces” or “never bars.”

Cite: Wis. Stat. § 895.045 (Wisconsin Legislature)
https://docs.legis.wisconsin.gov/statutes/statutes/895/iv/045

Common pitfalls

1. Assuming comparative fault always means you still get paid.
   Under Wis. Stat. § 895.045, if plaintiff negligence is greater than the defendant’s, recovery can be barred, affecting both valuation and leverage.

2. Over-including weak or unsupported damages.
   Settlement numbers become harder to justify when:

   • medical bills relate to unrelated issues,
   • wage loss isn’t documented,
   • symptom timelines don’t match treatment dates.

   Use DocketMath to identify which inputs drive the outcome before finalizing a demand.

3. Anchoring on one single outcome rather than scenario modeling.
   If you only compute one fault split, the other side can change the fault narrative and collapse your settlement basis. Run multiple scenarios around the 50% threshold.

4. Not separating medical categories by timing and causation.
   Even if total bills look large, settlement negotiations often depend on what’s attributable to the fall and what’s not.

5. Missing documentation that allocation math needs.
   If you can’t support an input (wage period, billed amount, or treatment date), opposing counsel may dispute it—changing the settlement math.

Run the numbers

Use DocketMath to model how settlement value changes based on your damages inputs and fault assumptions.

Suggested scenario table (Wisconsin-focused)

Copy this structure when you run DocketMath:

Practical inputs to enter into DocketMath

Collect and standardize these categories before running scenarios:

• Medical totals (sum of bills you intend to claim)
• Wage loss totals (match the approach supported by records—net vs. gross)
• Other economic losses (e.g., mileage or out-of-pocket care, if included)
• Non-economic damages estimate (pain and suffering amount used for negotiation)
• Fault split assumptions (plaintiff % and defendant %)

Output interpretation (what changes when inputs change)

• Fault assumptions: Crossing the 50% line can determine whether recovery is possible under Wis. Stat. § 895.045.
• Damages inputs: Medical and wage totals typically move the baseline value directly; non-economic damages often determine how wide the settlement range may be.
• Sensitivity check: If a result only makes sense under a very favorable fault assumption, rerun scenarios and tighten your supporting evidence.

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