Slip and fall settlement guide for Arkansas

Direct answer

In Arkansas slip-and-fall cases, settlement value is commonly driven by comparative-fault allocation under Ark. Code Ann. § 16-64-122, which requires comparing the fault charged to the claiming party against the fault charged to the other parties. Based on the statute text you provided, there was no slip-and-fall-specific exception located—so the general/default comparative-fault framework applies.

In practical terms: rather than treating settlement as a simple “who caused the fall” binary, you typically size negotiations by running the fault percentages through the damages allocation math. That’s exactly what DocketMath’s damages-allocation workflow can help you do—turning your categories and fault assumptions into consistent settlement-facing numbers.

What you need to know

Slip-and-fall disputes often include negligence concepts like notice, reasonable care, and causation. But when you’re converting those disputed facts into settlement numbers, comparative fault is usually the key mechanism.

How § 16-64-122 affects settlement allocation

Arkansas uses a comparative fault approach. Under Ark. Code Ann. § 16-64-122, liability is determined by comparing:

• the fault chargeable to the claiming party, and
• the fault chargeable to the party or parties from whom recovery is sought.

For settlement preparation, that means your damages allocation inputs should usually include:

• Total claimed damages (economic and non-economic, plus any property damages you’re accounting for)
• Fault percentages for the claimant and for each defendant/other responsible party you plan to include in the model
• A way to translate those percentages into an expected net recoverable amount

Think in scenarios (not one number)

Comparative fault is sensitive to how facts are framed and how parties anticipate blame being assigned. To keep negotiations grounded, model multiple fault outcomes (for example: claimant at 20% vs. 35% vs. 50%), and use the resulting net amounts as a negotiation range.

Where DocketMath fits

DocketMath’s damages-allocation tool helps you:

• keep damage categories consistent,
• apply fault percentage assumptions consistently, and
• update net recoverable outputs when your numbers change.

If you want to start immediately, use: /tools/damages-allocation.

Step-by-step

Use this workflow to estimate an Arkansas slip-and-fall settlement range using DocketMath with jurisdiction-aware comparative-fault logic.

1) Start with a damages list (category-first)

Before you touch fault, total your claimed categories. A simple structure might be:

Add them to get Total claimed damages.

2) Decide who gets blamed (fault model)

Under Ark. Code Ann. § 16-64-122, settlement allocation depends on comparative fault. Build one or more fault “stories,” such as:

• Scenario A: Claimant 20% fault / Defendant 80% fault
• Scenario B: Claimant 35% fault / Defendant 65% fault
• Scenario C: Claimant 50% fault / Defendant 50% fault

If there are multiple defendants/parties, the fault allocations should be modeled so the total fault you’re assigning across parties sums to 100% (or the tool’s expected total, if it uses a normalized approach).

3) Keep gross vs. net definitions consistent

For settlement math, you typically work with:

• Gross damages = the total of your category amounts
• Net recoverable = gross damages adjusted by the comparative-fault allocation

As a rule of thumb, don’t mix these in your negotiations. If you’re offering a “net number,” make sure the inputs and the outputs align to the same fault-adjustment method.

4) Enter inputs into DocketMath

Open DocketMath’s allocation calculator here: /tools/damages-allocation

Then input (based on what the tool prompts for):

• your damage categories and amounts,
• the fault percentages for claimant and each allocating party, and
• any tool-specific settings for how allocation is applied across categories (if the tool offers options).

5) Run “what-if” rounds (sensitivity testing)

Because fault percentage changes can materially shift net results, run multiple rounds:

• Increase claimant fault in steps (for example, 10–15% increments)
• Re-run DocketMath each time
• Track how the net recoverable output changes

This creates a defensible settlement range rather than a single guess.

6) Turn outputs into a settlement range (not a point)

Use the scenario outputs to build:

• a low-end net recovery figure (often driven by higher claimant fault), and
• a high-end net recovery figure (often driven by lower claimant fault).

This gives you a structured basis for negotiation while staying consistent with Ark. Code Ann. § 16-64-122 comparative-fault allocation.

Key statutes and citations

• Ark. Code Ann. § 16-64-122 (comparative fault framework)
  The statute provides that in actions for damages for personal injuries, wrongful death, or injury to property where recovery is predicated upon fault, liability is determined by comparing the fault chargeable to the claiming party with the fault chargeable to the party or parties from whom the claiming party seeks recovery.

Source (PDF): https://arkleg.state.ar.us/Home/FTPDocument?path=%2FBureau%2Fpublications%2FArkansas+Code%2FTitle+16%2FSubtitle+5%2FChapter+64%2FSubchapter+1%2F16-64-122.pdf

Important default framing: You noted that no claim-type-specific sub-rule was found in the statute text you provided. So this article uses the general/default comparative-fault rule as the governing framework for settlement allocation math.

Common pitfalls

Avoid these issues that commonly derail allocation-based settlement numbers:

• Using fault narratively but not numerically
  Settlement allocation needs percentages. Under Ark. Code Ann. § 16-64-122, fault comparison is what drives liability allocation.

• Running only one fault scenario
  One number hides uncertainty. Build a range by running multiple fault assumptions.

• Mixing gross and net damages
  Clearly label whether your figure is a total claimed amount (gross) or a fault-adjusted recoverable amount (net).

• Assuming there’s a slip-and-fall carve-out
  Based on the provided statute text, no slip-and-fall-specific exception was identified. Use the general comparative fault framework.

• Over-rounding fault percentages too early
  Small shifts (like 5–10%) can change net exposure when damages totals are large—especially for medical and non-economic categories. Re-run the model when you update assumptions.

Run the numbers

Below is a simplified example to mirror the comparative-fault mechanics you’d input into DocketMath.

Example assumptions

• Total claimed damages: $120,000

  • Past medical: $45,000
  • Future medical: $25,000
  • Lost wages: $20,000
  • Non-economic (pain/suffering): $30,000
  • Total: $120,000

Now apply three comparative-fault scenarios consistent with the fault comparison logic under Ark. Code Ann. § 16-64-122.

How DocketMath changes the workflow

Instead of recalculating manually:

• DocketMath’s damages-allocation flow helps keep category totals stable
• it applies your fault percentage assumptions consistently
• it updates outputs when you change damages or fault assumptions

To run your version, go to: /tools/damages-allocation.

Practical settlement takeaway

If the facts you expect to be persuasive support lower claimant fault, net recoverable tends to be higher. If the expected fault allocation is higher against the claimant, net recoverable tends to be lower. That movement is not a “strategy” choice—it’s the mechanical result of comparative fault allocation under Ark. Code Ann. § 16-64-122.

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