Slip and fall settlement guide for Missouri

Direct answer

In Missouri, a slip-and-fall settlement often turns on comparative fault under Mo. Rev. Stat. § 537.067, with a 51% threshold built into the fault-allocation workflow.

Using DocketMath (US-MO), you can convert your estimated fault percentages into an allocation-adjusted settlement value—especially when multiple actors may share fault (e.g., property owner and plaintiff). Practically, the “51% rule” means your numbers should be modeled so that once plaintiff fault reaches 51% or more, recovery becomes effectively barred, and when plaintiff fault stays below 51%, recovery continues but is reduced.

What you need to know

Before you calculate, you need three input buckets that map cleanly to a DocketMath damages-allocation workflow in US-MO:

1. Damages totals (medical, lost wages, out-of-pocket, and non-economic damages you can support)
2. Fault percentages (your best estimate of how evidence supports each party’s negligence)
3. Receipts / limitation-related documentation (to the extent your workflow includes items tracked as “receipts” or limitation inputs)

1) Comparative fault drives the settlement posture

Missouri uses comparative fault under Mo. Rev. Stat. § 537.067. In this guide’s allocation model, a verified 51% threshold percentage controls the practical output:

• Plaintiff is at or above 51% fault → recovery is effectively blocked in the allocation output.
• Plaintiff is below 51% fault → recovery proceeds but is reduced according to the plaintiff’s percentage fault, consistent with the comparative-fault operation reflected in Mo. Rev. Stat. § 537.067.1.

2) Settlement math must match the fault theory, not just the medical bills

Two cases can have similar total damages but widely different settlement values if the expected fault split changes. For slip-and-fall matters, your fault theory is often shaped by evidence such as:

• condition notice (what was known and when),
• cleaning/inspection practices and whether they were reasonable,
• lighting, signage, and how obvious the hazard was,
• the plaintiff’s route/awareness and whether reasonable care was used.

In DocketMath terms, those become inputs you translate into a plausible percentage argument.

3) Track “receipts” / limitation-related inputs with care

This guide’s verified packet flags “receipts” limitation tracking as “see statute.” That doesn’t mean you ignore it—it means your settlement workflow should confirm what limitation logic applies to the specific expenses and documentation you’re including.

Anchor the overall comparative-fault allocation workflow to Mo. Rev. Stat. § 537.067, but keep your documentation organized so your damages package stays consistent with whatever limitation-related handling your case requires.

Step-by-step

Use this workflow to build a jurisdiction-aware Missouri slip-and-fall settlement estimate in DocketMath (US-MO).

Step 1: Enter a damages subtotal (before fault reduction)

Start with a damages figure you can defend with itemized support. Typical categories include:

• medical costs,
• lost wages (if applicable),
• out-of-pocket expenses,
• and non-economic damages (pain, suffering, and similar impacts).

In DocketMath, input your total damages figure(s) first. Don’t reduce for fault yet—fault allocation comes next.

Step 2: Choose the allocation model (shared-fault setup)

Missouri’s comparative-fault framework under Mo. Rev. Stat. § 537.067 means you’ll model how fault is split between actors.

Before entering numbers, list the parties and your expected fault story:

• Defendant/property owner: failure to keep premises reasonably safe or address a hazard
• Plaintiff: conduct that may have contributed (e.g., failure to observe obvious conditions)

DocketMath is most useful when your percentages reflect an evidence-backed narrative you expect a finder of fact to accept.

Step 3: Enter plaintiff fault and the other parties’ fault percentages

Now input the fault percentages DocketMath will use.

Then apply the allocation logic tied to the 51% threshold:

• Plaintiff ≥ 51% → allocation output should reflect that recovery is effectively barred.
• Plaintiff < 51% → allocation output reduces recovery by plaintiff’s percentage fault.

Because the threshold is the dividing line, even small percentage shifts near the cutoff can meaningfully change settlement value.

Step 4: Run multiple settlement scenarios

Negotiations rarely reflect a single “true” fault split. To avoid relying on a fragile one-number estimate, run at least three scenarios in DocketMath:

• Plaintiff-favorable: plaintiff fault modeled clearly below 51%
• Midpoint: plaintiff fault modeled in a middle range
• Defense-favorable: plaintiff fault modeled near the cutoff (and test whether it crosses 51%)

This helps you create a settlement range that tracks comparative-fault math rather than gut feeling.

Step 5: Turn the allocation output into offers

When DocketMath provides allocation-adjusted recovery amounts:

• Convert those values into negotiation anchors (e.g., offer ranges by scenario).
• Tie your settlement posture to your fault narrative. If a scenario pushes plaintiff toward 51%, be ready to explain why the evidence supports a percentage below the threshold—or, if you’re on the defense side, why the evidence supports crossing it.

Key statutes and citations

What Mo. Rev. Stat. § 537.067 does for allocation math

Mo. Rev. Stat. § 537.067 provides the comparative-fault framework that governs how negligence percentages affect recovery. In a settlement workflow, it’s the anchor for converting fault estimates into expected value.

Why the workflow includes a 51% threshold

This guide’s allocation model uses a verified 51% threshold percentage. Practically, it ensures the DocketMath output reflects the comparative-fault cutoff behavior used to model whether plaintiff recovery continues or is effectively barred.

How § 537.067.1 fits operationally

Mo. Rev. Stat. § 537.067.1 supports the operational step of applying plaintiff fault percentages to reduce recovery when plaintiff fault is below the threshold in the comparative-fault framework.

Comparative-fault adoption context (optional support)

Gustafson v. Benda, 661 S.W.2d 11 (Mo. banc 1983) discusses comparative-fault adoption. While slip-and-fall matters may not be products cases, the case is useful background for understanding why Missouri’s negligence allocation behaves in a comparative-fault manner.

Common pitfalls

• Ignoring the 51% threshold in negotiations

  • If your plaintiff-fault scenario reaches 51% or more, the allocation output may effectively block recovery. Offers built without modeling this can collapse when the other side points to comparative-fault structure under Mo. Rev. Stat. § 537.067.

• Treating damages totals as the only driver

  • High medical bills don’t guarantee a high settlement if comparative fault pushes toward the cutoff.

• Disconnecting evidence from percentage inputs

  • DocketMath can output clean numbers, but your percentage allocations must connect to evidence (notice, reasonableness, and awareness). Otherwise, your “math” may not match the story.

• Skipping “receipts” / limitation-related documentation discipline

  • This guide flags the receipts limitation field as “see statute.” If you include expenses in the settlement package that are sensitive to limitation-related treatment, keep documentation organized so your workflow doesn’t become inconsistent.

• Running a single scenario only

  • One number is fragile when the fault split is near the threshold. Use scenario bands so you can explain sensitivity clearly.

Run the numbers

Use DocketMath (damages-allocation) to generate a Missouri settlement range based on comparative fault and the 51% threshold.

Scenario planning table (fault-driven outputs)

What to compare across DocketMath outputs

When reviewing results, focus on:

• the allocated recovery under each scenario,
• how quickly results flip as plaintiff fault approaches/crosses the 51% line,
• the sensitivity of the settlement range to percentage assumptions.

How to present the math in discussion

You can present it in plain terms without over-claiming:

• “If plaintiff fault is found below 51% under Mo. Rev. Stat. § 537.067, recovery continues but is reduced by plaintiff’s percentage fault.”
• “If plaintiff fault reaches 51% or more, recovery is effectively blocked by the allocation threshold logic used in the comparative-fault framework.”

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 real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance

For the Missouri slip-and-fall allocation workflow, run the calculator directly here: /tools/damages-allocation