Workers compensation settlement guide for Arkansas
8 min read
Published June 4, 2026 • By DocketMath Team
Direct answer
Arkansas workers’ compensation settlements often involve more than one “kind” of claim. Fault comparison under Ark. Code Ann. § 16-64-122 is generally relevant to third-party tort “actions for damages”—not automatically to a straightforward workers’ compensation benefits compromise.
So, the key practical question is:
- Are you settling an “action for damages… where recovery is predicated upon fault” (typical of a tort case)?
- If yes, comparative-fault logic can affect how you allocate damages in your settlement math.
- Are you settling workers’ compensation benefits through the workers’ compensation system without a fault-predicated tort damages component?
- If yes, you should generally not assume § 16-64-122 comparative-fault allocation mechanics apply.
Why this matters: § 16-64-122’s default framework compares “the fault chargeable to a claiming party” against the fault chargeable to the other liable party or parties. Your settlement documents may require allocation only where the settlement component matches that “fault-predicated damages” framing—not where the agreement is simply a benefits compromise.
Note: The provided statute excerpt does not identify a workers’-compensation-specific sub-rule; treat § 16-64-122 as the general default comparative-fault framework for qualifying “actions for damages… predicated upon fault,” not as a workers’-compensation-specific formula.
What you need to know
1) Use DocketMath to organize allocation work
DocketMath is the tool name you’ll use to keep your settlement allocation inputs and outputs consistent. For Arkansas, you’ll use DocketMath’s damages-allocation calculator when your settlement package includes damages allocation that corresponds to comparative-fault concepts.
Inline link: /tools/damages-allocation
2) Don’t mix up “benefits compromise” with “fault-based damages”
A single settlement package can be one of these:
- Benefits compromise (administrative/benefits-focused): typically handled under the workers’ compensation framework.
- Third-party tort damages (fault-based): the part where comparative fault can matter.
- Mixed settlement: both benefits and third-party damages, requiring careful separation of the “allocated damages” portion from the benefits-only portion.
If your settlement math is meant to “split the damages by fault,” you should first verify that the agreement actually treats those dollars as part of a fault-predicated damages resolution.
3) Inputs drive outputs (so label everything)
When you run DocketMath, you’ll usually provide:
- Fault % for the claiming party
- Fault % for each relevant other party
- Total amounts by damages category (and whether each is past vs. future, if your model separates those)
Small input mistakes—like swapping party roles or using percentages that don’t reconcile—can produce output tables that are internally consistent but misaligned with the settlement’s legal structure.
Step-by-step
Step 1: Triage what claim component you are allocating
Read the settlement description and release language to determine whether the dollars you’re allocating come from:
- An “action for damages… predicated upon fault” (tort-like damages resolution), or
- A workers’ compensation benefits compromise.
Quick triage questions:
- Does the settlement language mention fault, negligence, or comparative fault?
- Does it involve a tort damages claim (often third-party defendants beyond the workers’ comp system)?
- Does it state a purpose to allocate damages among multiple actors by fault?
If you can’t reasonably connect the allocation to a fault-predicated damages component, plan on not applying § 16-64-122 allocation logic to benefits-only portions.
Step 2: Confirm the “comparative fault” structure matches the statute trigger
§ 16-64-122 compares fault between a claiming party and the party or parties from whom the claiming party seeks recovery. In settlement terms, make sure:
- You know who the claiming party is in the statute sense
- You know who the other parties are for the fault comparison
If the settlement uses different labels, map them carefully before calculating.
Step 3: Extract fault percentages and ensure they reconcile
From the agreement, mediation, settlement allocation exhibit, or agreed findings:
- Enter the claiming party fault %
- Enter each other party fault %
- Make sure totals reconcile (commonly to 100%, unless the agreement uses another agreed method)
Step 4: Break damages into categories you will allocate
Build a damages-category list that matches what your settlement exhibit actually breaks out. Common illustrative categories include:
- Past medical expenses
- Future medical expenses
- Lost wages / wage earning capacity
- Impairment-related amounts (only if treated as a damages category in the settlement structure)
- Other compensable items expressly listed
Keep past vs. future separate if your settlement schedule does, because many drafting/reporting workflows treat them differently.
Step 5: Decide which categories are allocated by fault
Not every settlement line item should automatically be allocated by comparative fault. In practice, allocate by fault only when the settlement ties those dollars to the fault-predicated damages component.
Conservative workflow for tool-based planning:
- Allocate categories that clearly correspond to tort-like damages subject to comparative-fault framing.
- Exclude or separately treat categories that are clearly part of benefits-only resolution.
Step 6: Run the calculation in DocketMath
Use DocketMath’s allocation tool:
- /tools/damages-allocation
Enter your:
- Category totals
- Claiming party fault %
- Other parties fault %
Step 7: Validate against the settlement package
After running DocketMath:
- Check that allocated totals match the settlement’s category totals (for the categories you intended to allocate).
- Check that the claiming party’s allocation corresponds to how the agreement frames the “claiming party” and “other parties.”
- Verify you did not allocate benefits-only components using comparative-fault mechanics.
Warning: It’s easy to create a mathematically correct allocation that conflicts with the settlement’s legal theory if you apply § 16-64-122-style fault comparisons to a benefits-only workers’ compensation compromise.
Step 8: Use outputs for drafting and exhibits
Turn the DocketMath output into settlement-ready numbers for:
- exhibit schedules
- release language cross-references (e.g., “$X allocated to category Y”)
- any downstream lien/reimbursement calculations you manage in your broader workflow
Key statutes and citations
Arkansas comparative fault framework (default rule)
- Ark. Code Ann. § 16-64-122 (Comparative fault in “actions for damages”)
Jurisdiction-aware trigger (what matters for settlement allocation modeling):
The statute applies to “actions for damages for personal injuries or wrongful death or injury to property” where recovery is “predicated upon fault,” and it requires determining liability by comparing:
- fault chargeable to a claiming party, with
- fault chargeable to the party or parties from whom the claiming party seeks recovery.
Statute text 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
Practical non-advice interpretation: Treat § 16-64-122 as the general comparative-fault framework for qualifying “actions for damages… predicated upon fault.” If your settlement component is a benefits-only workers’ compensation compromise, § 16-64-122 may not be the right allocation lens.
Common pitfalls
Applying comparative fault to benefits-only workers’ comp
- If the settlement resolves only benefits without a fault-predicated damages component, don’t assume § 16-64-122 allocation logic automatically fits.
Fault percentages that don’t reconcile
- If the settlement says 70/30 but your inputs total 99% (or 110%), your DocketMath output may be mathematically consistent yet inconsistent with the agreement.
Allocating categories that the settlement treats as non-fault-based
- Allocate only categories that the settlement structure ties to the fault-predicated damages component.
Mixing past and future amounts
- Many settlement exhibits separate past/future; combining can create drafting and reporting errors.
Swapping the claiming party role
- § 16-64-122 uses “fault chargeable to a claiming party” versus “fault chargeable” to the other parties. If the worksheet swaps roles, your allocations can effectively reverse.
Run the numbers
Use DocketMath (damages-allocation)
Go to: /tools/damages-allocation
Input checklist (prepare these before running)
- Fault % for the claiming party
- Fault % for each other party included in the comparison
- Total damages per category (as listed in your settlement exhibit)
- Identify which categories are allocated by fault vs. excluded/separately treated
- Confirm reconciliation:
- Fault % totals align with the settlement’s agreed method (commonly 100%)
- Category totals match the agreement for the categories being allocated
Example allocation table format (illustrative)
| Category | Total damages | Claiming party % | Other party % | Allocated to claiming party | Allocated to other party |
|---|---|---|---|---|---|
| Past medical | $25,000 | 70% | 30% | $17,500 | $7,500 |
| Lost wages | $40,000 | 70% | 30% | $28,000 | $12,000 |
| Total | $65,000 | — | — | $45,500 | $19,500 |
After you run DocketMath, compare the output table back to your settlement exhibit line items.
Related reading
- [How to calculate Damages
