How to calculate Settlement Allocator in Arkansas
8 min read
Published January 17, 2026 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Quick takeaways
- Arkansas uses a general 6-year statute of limitations for many civil claims when there isn’t a claim-type-specific limitations rule.
- The default limitations period used here is Ark. Code Ann. § 5-1-109(b)(2), which provides a 6-year timeframe.
- In DocketMath’s Settlement Allocator (US-AR), you’ll typically allocate the settlement by applying jurisdiction-aware time windows (and any case-specific allocation inputs you provide) anchored to that 6-year default.
- If your inputs imply that portions of damages fall outside the 6-year lookback, those portions generally end up with reduced or zero recoverable allocation weight under the default assumptions in the tool.
- For arbitration, fraud, product-liability, construction, or other specialized claims, a different limitations rule might apply—this walkthrough is for the general/default period only.
Note: This guide uses the general/default statute of limitations for Arkansas because no claim-type-specific sub-rule was provided in the jurisdiction data. If your matter involves a specialized claim, the limitations period could be different.
Inputs you need
Before you start DocketMath’s Settlement Allocator for Arkansas (US-AR) using the default 6-year rule, gather the inputs that drive (1) the limitations timeline and (2) the proportional allocation weights.
Use this intake checklist as your baseline for Settlement Allocator work in Arkansas.
- jurisdiction selection
- key dates and triggering events
- amounts or rates
- any caps or overrides
If any of these inputs are uncertain, document the assumption before you run the tool.
Case timeline inputs
- Date of injury / event date (DOI): When the underlying harm occurred (or when the relevant event happened).
- Date the lawsuit was filed (filing date): The date the complaint was filed.
- Cutoff date for allocation (if different from filing date): Some teams use a later date for internal modeling; DocketMath can often accommodate a modeling cutoff depending on your setup.
Damages structure inputs (the “bucket” math)
- Total settlement amount: The gross settlement figure you want the tool to allocate.
- Damages buckets: The categories you want to allocate (examples commonly used in practice):
- Past medical / expenses
- Past lost wages
- Future medical / expenses
- Future lost wages / earning capacity
- Non-economic damages (only if your allocation workflow treats them as a bucket)
- Amount in each bucket (or a method to derive it)
Time slicing parameters (what DocketMath uses to apply the limitations window)
- What dates each bucket corresponds to:
- For past buckets: the start date and end date the past damages cover
- For future buckets: the expected future start date and expected horizon (or an end date)
- Any special exclusions or modeling choices you want reflected in the allocation (for example, portions you’re treating as clearly non-recoverable based on your internal case assumptions)
Jurisdiction selector (Arkansas)
- Jurisdiction = US-AR
- Limitations window = General/default 6 years based on **Ark. Code Ann. § 5-1-109(b)(2)
How the calculation works
DocketMath’s Settlement Allocator for Arkansas (US-AR) uses a jurisdiction-aware approach anchored to the general 6-year statute of limitations described by Ark. Code Ann. § 5-1-109(b)(2) (the default rule provided). Here’s how to think about the mechanics so you can predict the output before you run it.
Step 1: Compute the “lookback window” using the default 6-year period
For this walkthrough, the recoverable window is modeled as:
- 6 years (general SOL period)
- **Source: Ark. Code Ann. § 5-1-109(b)(2)
How to model it (practically in your workflow):
- Choose the anchor date the tool uses (commonly the filing date, or your selected modeling cutoff).
- Subtract 6 years from that anchor date.
- The resulting date is the beginning of the recoverable allocation window under the default assumption.
Illustrative example (timeline only):
- Filing date: March 15, 2026
- Lookback start: March 15, 2020 (6 years earlier)
Any past damages bucket dates that fall entirely before March 15, 2020 will typically receive low or zero weight under the default overlap logic (depending on how the bucket is defined). Buckets that straddle the boundary generally receive partial weight.
Warning: If a bucket overlaps both sides of the lookback start, the tool generally treats it as proportional overlap rather than “all-or-nothing.” That’s why your bucket start/end dates matter as much as the dollar amounts.
Step 2: Assign each bucket a recoverable overlap fraction
For each damages bucket, the tool looks at the date span your bucket covers and calculates how much of that span lies within the 6-year window.
A common way to conceptualize this is:
- **Overlap fraction = (Days in bucket covered by the SOL window) / (Total days in the bucket span)
Then:
- Allocated bucket amount is driven by that overlap fraction (or by a proportional time-weighting model consistent with your selected workflow).
In other words, two buckets with the same dollar amount can produce different allocated results if one bucket occurs mostly inside the lookback window and the other occurs mostly outside it.
Step 3: Allocate the settlement amount consistently with your workflow
After DocketMath calculates recoverable portions by time overlap (based on your bucket dates), it generates allocations that match the total settlement under the allocation approach you selected.
Two broad ways results can behave:
Recoverable-first / time-overlap reduction behavior
- The tool reduces buckets that extend beyond the limitations window.
- Final allocations reflect only the time overlap that fits within the 6-year default.
Proportional redistribution behavior
- The tool may reallocate value associated with non-overlapping periods into buckets that remain within the recoverable window (depending on tool settings/workflow).
- This is common when the model must keep allocations summing to the entire settlement.
Either way, the key Arkansas input driving the jurisdiction-aware aspect here is the 6-year lookback from Ark. Code Ann. § 5-1-109(b)(2)—and the explicit caveat that specialized claims may use different limitation periods.
Step 4: Validate with quick consistency checks
After running the allocation, check whether the results “make sense” relative to your timeline:
- Did the tool substantially reduce allocations for buckets whose dates are mostly before the lookback start?
- Are boundary-crossing buckets getting partial credit (not binary zero/one outcomes)?
- Does the tool’s allocation output total equal your input settlement total under the selected workflow?
Common pitfalls
Even with a good jurisdiction model, settlement allocation can go off the rails due to input issues or misunderstanding how overlap math works. Common pitfalls include:
- Using the wrong date boundaries for “past” buckets
- Example: If a medical bucket truly covers 2018–2021 but you enter 2020–2021, you may unintentionally inflate recoverable overlap.
- Forgetting that this is the Arkansas default/general rule
- With the provided jurisdiction data, the relevant period is Ark. Code Ann. § 5-1-109(b)(2) (general/default 6 years).
- No claim-type-specific sub-rule was provided here, so specialized limitations periods are not automatically applied by this walkthrough.
- Entering future damages without a clear horizon
- If future buckets have vague or overly broad dates, the overlap math can produce misleading allocations.
- Modeling “six years” as one single boundary with no overlap logic
- Buckets often span multiple years. The tool needs date ranges, not just totals.
- Rounding / day-count sensitivity
- When bucket spans are short (weeks/months), small date-entry differences can materially change overlap fractions.
Pitfall example: If you enter “Past medical: $80,000” but don’t provide correct start/end dates, you can’t compute overlap with the 6-year window tied to Ark. Code Ann. § 5-1-109(b)(2). For accurate allocation, the tool needs your underlying timeline.
Sources and references
- Ark. Code Ann. § 5-1-109(b)(2) (general/default limitations period used here: 6 years)
- DocketMath tool: Settlement Allocator (US-AR) — accessed via https://docketmath.com/tools/settlement-allocator
Start with the primary authority for Arkansas and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.
Next steps
- Gather bucket start/end dates for each damages category you plan to allocate.
- Confirm the anchor date your model uses (typically the filing date, or your selected modeling cutoff) since the 6-year lookback is measured from that anchor under the default rule.
- Run DocketMath with:
- Jurisdiction: US-AR
- Limitations window: 6-year general/default (Ark. Code Ann. § 5-1-109(b)(2))
- Review the outputs specifically for overlap-driven results:
- If allocations look unexpectedly low, check whether many bucket dates fall largely outside the 6-year lookback window.
- If you suspect the claim is specialized (even if you’re not fully sure), re-check whether a different Arkansas limitations statute might apply—this walkthrough uses only the general/default period based on the provided data.
Gentle disclaimer: This is a practical walkthrough of how to run a time-based allocator using the provided default Arkansas limitations rule; it is not legal advice.
