Abstract background illustration for Slip and fall settlement guide for Washington

Slip and fall settlement guide for Washington

6 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Direct answer

In Washington, RCW 4.22.005 uses a comparative-fault rule: any contributory fault chargeable to the claimant reduces the compensatory damages in proportion to the claimant’s share of fault. In practice, slip-and-fall “settlements” are often driven by a fault-allocation math model (not only by medical expenses and liability risk).

DocketMath’s damages-allocation calculator can help you structure that model so you can estimate how a proposed settlement might change when fault percentages, total damages, and liability share inputs are updated.

Note: The jurisdiction data you provided does not identify any claim-type-specific sub-rule, so this guide treats RCW 4.22.005 as the general/default period for comparative-fault diminishment in Washington (not a special exception).

What you need to know

Washington settlement values in slip-and-fall cases often come from two linked “buckets”:

  1. Total compensatory damages
    These are the economic and noneconomic damages (commonly including medical expenses, lost wages, and pain and suffering) the injured person claims were caused by the incident.

  2. Fault allocation (comparative fault)
    Under RCW 4.22.005, any contributory fault by the claimant diminishes the compensatory damages proportionately. So if you model:

    • Total compensatory damages: $120,000
    • Claimant’s fault: 20%

    Then the claimant’s modeled recoverable amount (before other offsets or procedural adjustments) is often represented as: $120,000 × (1 − 0.20) = $96,000

Why that matters for settlement

Settlement ranges frequently reflect how each side argues:

  • Whether the incident looks like a foreseeable hazard and whether cleaning/inspection was reasonable,
  • Whether the claimant’s conduct (e.g., distraction, ignoring warnings, improper footwear) supports comparative fault,
  • Whether the evidence on causation is stronger for one side.

Even if liability seems likely, a small change in assumed fault can move the modeled number—especially when pain-and-suffering meaningfully affects the total.

Step-by-step

Use this workflow to estimate settlement impact with DocketMath (this is for education and modeling, not legal advice).

Step 1: Build your “total damages” estimate

Create a single number for Total Compensatory Damages using your best-faith estimate of:

  • Medical expenses (past)
  • Future medical (if known)
  • Lost wages (past and future)
  • Other economic losses (e.g., out-of-pocket costs)
  • Noneconomic damages (pain and suffering)

Step 2: Estimate the claimant’s comparative fault %

Washington comparative fault is governed by RCW 4.22.005. For modeling purposes, choose a claimant fault percentage supported by your evidence assumptions, such as:

  • 0% (claimant fully not at fault)
  • 10–20% (some fault argument)
  • 30–40% (significant fault argument)

Keep the figure explicit so the calculator outputs are traceable.

Step 3: Apply the statutory diminishment to get “fault-reduced damages”

DocketMath’s damages-allocation workflow supports the core statutory concept in RCW 4.22.005: compensatory damages reduce in proportion to the claimant’s contributory fault.

A simple model is:

  • Fault-Reduced Damages = Total Compensatory Damages × (1 − Claimant Fault %)

Step 4: Convert the fault-reduced figure into a settlement estimate

Modeled damages are not the same as a settlement offer. To get an estimate, apply a settlement discount (your internal litigation-risk adjustment), for example:

  • lower discount if liability/evidence looks strong
  • higher discount if there are weak medical causation points or weaker liability evidence

Treat the calculator output as a damages anchor and then adjust for the risk you’re modeling.

Step 5: Run multiple scenarios (sensitivity analysis)

Don’t rely on one fault percentage. Run a range, such as:

  • Low fault: 0–10%
  • Mid fault: ~20–25%
  • High fault: 35–40%

This produces a defensible settlement range you can explain to stakeholders.

Step 6: Keep documentation organized

Even when using a tool, keep the “why” behind your inputs:

  • Injury timeline (date of fall → treatment → if known, maximum medical improvement)
  • Medical billing summaries / treatment notes
  • Wage-loss documentation
  • Incident evidence (photos/video, weather conditions, signage, prior complaints)

Key statutes and citations

Comparative fault in Washington: RCW 4.22.005

RCW 4.22.005 provides the governing comparative-fault rule for fault-based diminishment of compensatory damages. The provided excerpt reflects that contributory fault chargeable to the claimant diminishes proportionately the compensatory damages for an injury attributable to the claimant’s contributory fault.

Modeling translation (how it fits settlement math):

  • Compensatory damages = Total claimed injury value before fault reduction
  • Contributory fault (claimant share) = the percent reduction applied
  • Proportionate diminishment = linear scaling with claimant fault %

Warning: Comparative fault diminishment is about attributing responsibility for the claimant’s injury. If you’re modeling, tie fault assumptions to evidence categories (e.g., distraction, ignoring warnings, known hazards, weather-related slickness with notice).

Common pitfalls

Fault modeling pitfalls

  • Forgetting to apply the comparative-fault reduction under RCW 4.22.005 (people sometimes compute total damages and then negotiate without fault math).
  • Using a single fault % when evidence supports a range; settlement negotiations often shift on the “reasonable” mid-point.
  • Mixing liability arguments and damages math—treat fault as the fault-driven compensatory diminishment, not a vague general discount.

Damages input pitfalls

  • Double counting medical categories (e.g., past medical listed twice).
  • Including amounts that aren’t compensatory in “total compensatory damages.”
  • Overstating future losses without a basis (future medical/wage loss should align with diagnoses and employment facts).

Tool workflow pitfalls

  • Changing fault % but not updating the same Total Compensatory Damages number, which makes scenario comparisons misleading.
  • Failing to document the rationale behind your inputs, so the output can’t be explained during negotiation.

Run the numbers

Use DocketMath’s damages-allocation tool to apply the Washington comparative-fault diminishment concept from RCW 4.22.005: /tools/damages-allocation.

Example scenario set (for a modeling range)

Assume:

  • Total Compensatory Damages: $150,000

Run three claimant fault assumptions:

ScenarioClaimant Fault %Fault-Reduced Damages (RCW 4.22.005 concept)Settlement-use note
Low fault10%$150,000 × 0.90 = $135,000Use when claimant conduct looks reasonable
Mid fault25%$150,000 × 0.75 = $112,500Common negotiation “battleground” point
High fault40%$150,000 × 0.60 = $90,000Use when notice/distraction arguments are strong

Then apply your chosen settlement discount (example: 10–30%) based on internal litigation risk:

  • Example at mid scenario with a 20% discount: $112,500 × 0.80 = $90,000 (modeled settlement anchor)

Inputs checklist for DocketMath (damages-allocation)

  • Total compensatory damages amount ($)
  • Claimant fault percentage (%) for Washington comparative-fault diminishment
  • Any planned settlement discount factor (%) you’re using for negotiation range modeling

Pitfall: If you adjust claimant fault %, consider whether you should also keep the discount consistent across scenarios—unless you have a reason to believe litigation risk changes with the fault argument.

Related reading