How to estimate car accident settlements in Arkansas

Direct answer

You can estimate an Arkansas car accident settlement by modeling comparative fault under Ark. Code Ann. § 16-64-122 and then applying that fault allocation to your estimated damages (economic + non-economic). DocketMath’s damages-allocation tool is designed for this workflow: you translate the case facts into (1) economic damages, (2) non-economic damages, and (3) fault percentages, and it outputs an allocation-aware settlement value you can use as an anchor.

Gentle note: this is an estimation workflow, not legal advice. Real outcomes depend on evidence, proof of causation, and how a judge or jury applies fault.

What you need to know

Arkansas uses a fault-comparison (comparative fault) approach in actions for damages where recovery is predicated upon fault. Ark. Code Ann. § 16-64-122(a) directs the factfinder to compare:

• the fault chargeable to the claiming party, versus
• the fault chargeable to the party or parties from whom the claiming party seeks recovery.

Default (claim-type) rule you should apply

Use § 16-64-122 as the general/default allocation framework for your damages-allocation estimate. No claim-type-specific sub-rule was identified in the jurisdiction notes provided, so there’s no separate cause-of-action exception to pivot to in this workflow. In practice, that means your settlement math should start with § 16-64-122 unless you have a clear, specific statute saying otherwise.

What “damages allocation” means for settlement estimation

In settlement planning, “damages allocation” usually combines:

• Economic damages (often document-driven)

  • medical bills (including plausibly related future care, if supported)
  • lost wages and/or loss of earning capacity
  • property damage
• Non-economic damages

  • pain and suffering
  • inconvenience and loss of enjoyment of life
• Fault percentages under the comparative fault framework in § 16-64-122

DocketMath’s damages-allocation tool matches that structure, helping you connect damages inputs to an allocation-aware result.

Why you should think in ranges

Settlement values are typically not a single number because key inputs—especially:

• fault percentages (which depend heavily on evidence), and
• non-economic damages (often tied to credibility and functional impact evidence)

—vary depending on negotiation posture and how litigation would likely develop. Modeling multiple scenarios is the practical way to estimate.

Step-by-step

Below is a practical, Arkansas-jurisdiction-aware workflow using DocketMath and comparative fault modeling under § 16-64-122.

1) Gather your damages inputs (make them evidence-ready)

Build totals you can defend with records. Keep separate buckets so you can see how changes affect the overall estimate.

Inputs to prepare

• Property damage total (repair estimate / replacement)
• Medical expenses to date (itemized bills)
• Future medical estimate (only if there’s a treatment plan or provider support)
• Lost wages (pay stubs, W-2s, employer verification)
• Lost earning capacity (work restrictions, vocational evidence, if applicable)
• Non-economic damages estimate (consistent method across scenarios)

2) Create multiple fault scenarios (don’t rely on one number)

Comparative fault is an evidentiary question. Build at least three scenarios tied to how the facts might be interpreted:

• Scenario A (best liability view): your side assigned relatively low fault
• Scenario B (middle): fault split closer to a disputed midpoint
• Scenario C (worst liability view): your side assigned meaningful fault

Even before a verdict, you can model how each side’s story could land.

3) Define “claiming party” and allocate fault across modeled parties

Ark. Code Ann. § 16-64-122(a) frames the comparison as fault chargeable to:

• the claiming party, compared to
• the party or parties from whom recovery is sought.

In your modeling:

• Ensure your modeled fault percentages add up to 100% across the parties you’re allocating between.
• If you model only two drivers, allocate the remaining fault between those two.
• If other potentially responsible parties are realistically in play, include them so your allocation reflects that evidence.

4) Use DocketMath’s damages-allocation tool

Use the primary CTA:

/tools/damages-allocation

Then enter, for each scenario:

• Economic damages total (or breakouts, if your workflow supports it)
• Non-economic damages total (or a range mapped into scenarios)
• Fault percentages for the claiming party and the other party/parties

DocketMath will calculate an allocation-aware figure you can use as your settlement anchor per scenario.

5) Turn allocation outputs into a negotiation range

Because non-economic damages and fault are contestable, convert scenario outputs into a range approach:

• Lower estimate: use the worst liability scenario (and often conservative non-economic assumptions)
• Target estimate: use the middle scenario
• Upper estimate: use the best liability scenario (and stronger, evidence-supported non-economic assumptions)

Then adjust for practical settlement realities like:

• proof strength (causation and documentation),
• credibility and medical record consistency,
• litigation risk and costs,
• likely negotiation posture (mediation timing, trial proximity, etc.).

Key statutes and citations

Comparative fault framework in Arkansas

Ark. Code Ann. § 16-64-122(a) (comparative fault) provides that in actions for:

• damages for personal injuries, or
• 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

Statute text excerpt provided in brief (a):
“In all actions for damages for personal injuries or wrongful death or injury to property in which recovery is predicated upon fault, liability shall be determined by comparing the fault chargeable to a claiming party with the fault chargeable to the party or parties from whom the claiming party …”

How to use this in settlement estimation:
If your side is assigned any fault, it typically reduces the portion of damages you can recover compared to an “all-fault-by-defendant” view—so fault modeling must be part of your damages allocation workflow.

Common pitfalls

1. Ignoring fault modeling

   • If you estimate settlement based only on “total damages,” you’ll likely overstate value when fault is disputed.

2. Using a single fault percentage

   • Fault is rarely a settled input. Use multiple scenarios tied to what the evidence supports.

3. Mixing property damage and injury damages without tracking buckets

   • Separate them so you can see how causation and fault arguments affect each component.

4. Changing the non-economic method between scenarios

   • Pick a consistent non-economic approach across scenarios so comparisons remain meaningful.

5. Overstating future damages

   • Future medical and functional impact must be plausibly attributable to the crash and supported by treatment plans and records. Inflated future assumptions can produce unrealistic “upper” values.

Run the numbers

A practical way to estimate is to create a scenario table and feed each row into DocketMath.

Example scenario structure (copy/paste and customize)

Assume you estimated damages totals as follows:

• Economic damages: $25,000
• Non-economic damages: $20,000

Then test fault scenarios:

How outputs change when inputs change

• Higher fault assigned to your side → lower allocation-adjusted recovery
• Higher non-economic damages → higher allocation-adjusted recovery (assuming fault stays constant)
• More supported future medical → higher economic damages, which can lift your floor for defended claims

Compute and record scenario results in DocketMath

For each scenario, enter:

• economic damages total
• non-economic damages total (or the chosen scenario number)
• fault percentages

Then summarize:

• Lower estimate: Scenario C result
• Target estimate: Scenario B result
• Upper estimate: Scenario A result

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