Slip and fall settlement guide for North Dakota

Slip and fall settlement guide for North Dakota

8 min read

Published July 14, 2025 • Updated April 23, 2026 • By DocketMath Team

Article claim inventory in progress

Trust release 4

This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.

Direct answer

Run this scenario in DocketMath using the Damages Allocation calculator.

In North Dakota, slip-and-fall settlement negotiations typically hinge on comparative negligence under N.D.C.C. § 32-03.2-02 and the court’s allowance of damages such as medical expenses, wage losses, and non-economic harms. In DocketMath, the /tools/damages-allocation calculator helps you translate your estimated damages and an expected fault story into settlement-ready totals that match how liability is likely to be argued.

A practical way to think about settlement value is:

  • If the plaintiff’s fault is found at p%, recovery generally shrinks to about (1 − p%) of recoverable damages under North Dakota’s comparative negligence framework.

DocketMath doesn’t replace evidence review, but it can help you model multiple fault scenarios so your settlement number aligns with your litigation risk.

Note: This guide explains settlement mechanics and key statutes in North Dakota. It’s not legal advice. Outcomes depend heavily on facts such as notice, foreseeability, the premises condition, and the plaintiff’s conduct.

What you need to know

North Dakota slip-and-fall cases usually turn on two questions:

  1. Duty and breach (what the premises owner did or failed to do), and
  2. Causation plus comparative negligence (whether the plaintiff’s own conduct contributed to the fall).

In settlement discussions, parties often focus on:

  • Liability allocation: fault percentages under N.D.C.C. § 32-03.2-02.
  • Damages categories: how much of the claimed total is economic vs. non-economic, and whether each component is supported by records.
  • Evidence strength: photos, incident reports, witness statements, maintenance logs, and “notice” facts (how long the hazard existed).
  • Timing and consistency: when medical treatment and work-status evidence remain consistent, it’s usually easier to justify settlement ranges.

How settlement posture typically forms

A settlement number is rarely “just” a damages total. Negotiations often follow a chain:

  1. Estimate total damages (medical + lost wages + out-of-pocket + non-economic).
  2. Apply comparative negligence (reduce by plaintiff fault percentage).
  3. Decide whether to include or discount certain claims based on evidentiary support.
  4. Adjust for leverage: trial cost, uncertainty, and risk tolerance about fault percentages.

Step-by-step

Use this workflow to build a North Dakota slip-and-fall settlement range in DocketMath, using /tools/damages-allocation to keep your math consistent as assumptions change.

1) Gather facts that drive liability and fault

Create a case file summary with bullets like:

  • Hazard type: ice, wet floor, debris, uneven surface, lighting/visibility issues
  • Location and conditions: entryway, hallway, parking lot, stairwell
  • Notice facts: how long the condition existed (or why it should have been discovered)
  • Maintenance/control: cleaning schedules, salting logs, inspections
  • Incident documentation: incident report timing, photographs, witness names
  • Plaintiff conduct: footwear, speed, whether distracted, known hazards

Even if you don’t know the exact fault percentages yet, you’ll need enough detail to justify them during settlement.

2) Build a damages worksheet (records first)

Estimate damages by category and keep two versions:

  • Conservative: only fully supported amounts
  • Expanded: includes items you can likely substantiate (e.g., projected rehab supported by treating notes)

Common categories:

  • Medical expenses (ER/urgent care, imaging, PT/OT, prescriptions)
  • Future medical (if supported by treating provider notes)
  • Lost wages (pay stubs, employer letter, attendance records)
  • Loss of earning capacity (only if supported by evidence)
  • Out-of-pocket (transportation, home services)
  • Non-economic damages (pain and suffering, inconvenience, loss of enjoyment)

In DocketMath, you’ll get the most reliable outputs when you input numbers that correspond to real evidence and clearly labeled categories.

3) Choose expected fault inputs for comparative negligence

Because North Dakota uses comparative negligence, settlement planning requires an expected plaintiff fault percentage (and sometimes how you want to frame allocation).

A practical method is to bracket with 2–3 scenarios you can defend:

  • Scenario A: plaintiff 20% fault
  • Scenario B: plaintiff 40% fault
  • Scenario C: plaintiff 60% fault

The goal isn’t perfect prediction—it’s to avoid anchoring on one assumption when the evidence may support multiple outcomes.

4) Run DocketMath’s allocation tool

Open /tools/damages-allocation and input:

  • Damages totals by category (or an all-in total, depending on how the tool is structured in your workflow)
  • Expected plaintiff fault percentage (and any other allocation fields the tool requests)
  • Any adjustments you want to model (e.g., anticipated future treatment costs)

Then generate totals that you can use directly in negotiation.

5) Convert outputs into a negotiation range

Use the tool results to set:

  • Walk-away number (lowest scenario)
  • Target number (middle scenario)
  • Stretch number (highest scenario)

Many parties negotiate off a range because fault and damages are uncertain, and the defense may attack specific components.

Warning: If you overstate future medical or wage loss without documentation support, it can inflate your demand and give the defense credibility leverage to argue for a different fault story or reduced damages.

Key statutes and citations

Below are North Dakota legal anchors that commonly appear in slip-and-fall settlement discussions. This is not exhaustive, but it focuses on the framework that most often affects settlement math and the parties’ negotiation posture.

Comparative negligence: reduction based on fault

  • N.D.C.C. § 32-03.2-02 (Comparative negligence)
    North Dakota applies comparative negligence, meaning the plaintiff’s recovery is reduced by the plaintiff’s percentage of fault.

Why it matters for settlement math:
If your damages are $100,000 and the plaintiff is assigned 30% fault, your recovery expectation is roughly $70,000 before other offsets or evidentiary discounts.

Premises-related themes (often influence fault even when statutes aren’t quoted)

Slip-and-fall cases typically involve premises-duty and breach evidence, including notice, foreseeability, and reasonable care. Even if settlement letters don’t cite the full body of duty doctrine, the evidence themes that support or undermine “notice” and “reasonable care” often drive fault percentage arguments.

Note: Comparative negligence is frequently the most cited statute because it directly affects the final number through percentage allocation.

Interest and timing (procedural impacts)

Settlement discussions sometimes factor in post-filing or post-judgment interest and procedural timelines. Availability and timing can vary based on facts and posture, so treat this as context for negotiation rather than a guaranteed add-on.

Common pitfalls

Avoid these mistakes that commonly derail settlement math or reduce credibility.

  • Treating fault as binary
    Comparative negligence means even “small” plaintiff fault can significantly reduce recovery. Use multiple fault scenarios rather than one number.

  • Overcounting non-economic damages without anchoring
    Defense teams often argue non-economic damages should track symptom severity and treatment duration. Keep your non-economic claim tied to documented medical findings and functional impact.

  • Ignoring notice and documentation gaps
    If you can’t credibly show when the hazard existed or who should have known, the defense may push for a higher plaintiff fault narrative. Include notice-related evidence in your case summary.

  • Mixing categories without clear support
    Lost wages and future medical claims usually need stronger proof. If you can’t support a component, keep it in an “expanded” scenario only.

  • Using a single demand number too early
    A single early demand can compress negotiation. A range built from DocketMath outputs usually gives more flexibility.

Pitfall to watch: If you only input an “all-in” medical total and forget wage loss separately, you can underestimate how wage documentation issues change the economic damage picture.

Run the numbers

Here’s an illustrative example of how DocketMath’s /tools/damages-allocation outputs can translate into a settlement range for a North Dakota slip-and-fall claim.

Example inputs (illustrative)

Estimated damages:

CategoryAmount
Past medical expenses$28,000
Future medical (supported estimate)$10,000
Lost wages (documented)$14,500
Out-of-pocket$1,200
Non-economic damages (pain & suffering)$35,000
Total claimed damages$88,700

Then model comparative negligence scenarios for the plaintiff:

  • Scenario A: plaintiff 20% fault
  • Scenario B: plaintiff 40% fault
  • Scenario C: plaintiff 60% fault

Output logic (how the allocation changes totals)

A simplified expectation under comparative negligence:

  • Scenario A recovery ≈ $88,700 × (1 − 0.20) = $70,960
  • Scenario B recovery ≈ $88,700 × (1 − 0.40) = $53,220
  • Scenario C recovery ≈ $88,700 × (1 − 0.60) = $35,480

Turn outputs into negotiation anchors

A common structure using these outputs:

  • Demand/target range: $53,220 to $70,960
  • High-end aspiration: $70,960 (Scenario A)
  • Low-end risk floor: $35,480 (Scenario C)

Now adjust your totals based on what evidence strengthens or weakens:

  • Stronger future medical support → increase future medical and rerun
  • Incomplete wage evidence → reduce lost wages and rerun
  • Better photos/witnesses on notice → consider lowering expected plaintiff fault and rerun

What to input in DocketMath (to keep results usable)

Before running, confirm:

  • Past medical totals are supported (by date/provider where possible), not a single untraceable lump
  • Lost wages are supported by pay stubs or employer

Related reading