Worked example: Damages Allocation in Arkansas
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Damages Allocation calculator.
Below is a jurisdiction-aware worked example for damages allocation in Arkansas (US-AR) using DocketMath and a default statute-of-limitations (SOL) framework.
Gentle note: This is an illustration of how a timing-based allocation model can work. It is not legal advice, and real-world results can depend on claim specifics, accrual facts, and any claim-type-specific limitations rules.
Scenario (worked example)
Assume a plaintiff brings a damages claim in Arkansas tied to a dispute that produces two categories of monetary damages:
- Past damages (already incurred): $120,000
- Future damages (to be incurred later): $80,000
To allocate damages, DocketMath uses a timing model tied to the General SOL Period in Arkansas.
Timing inputs (the core of allocation)
Use these as the “date math” inputs:
- Date of injury/trigger: January 15, 2019
- Date suit filed: June 1, 2024
- Future damages start date: January 1, 2025
- Future damages end date: December 31, 2026
Statute-of-limitations rule used (Arkansas)
For this example, DocketMath uses Arkansas’s general/default SOL rule because no claim-type-specific sub-rule was found in the jurisdiction data you provided. That means the model applies the general SOL rather than a special, shorter/longer period for a specific claim.
- General SOL Period: 6 years
- Ark. Code Ann. § 5-1-109(b)(2) (as provided in the jurisdiction data)
Note: This example treats the 6-year SOL as the default allocation driver. If your situation involves a claim category with a different SOL or accrual rule, the allocation can change materially.
Tool link (where you’d run this)
You can run the same type of analysis using the Damages Allocation calculator here: /tools/damages-allocation
Example run
Run the Damages Allocation calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Compute the filing window relative to the SOL
With a 6-year general period, the latest date for actionable recovery tied to the trigger date is:
- Trigger date: Jan 15, 2019
- SOL length: 6 years
- Conceptual “deadline” anchor (6-year window): Jan 15, 2025
Suit filed: June 1, 2024, which is within the 6-year window.
So, under this simplified worked example, the model treats the pre-deadline portion as potentially recoverable (subject to proof), and then applies the boundary logic to the portion of damages that occurs around/after the SOL anchor.
Step 2: Allocate past damages (already incurred)
In this example, past damages are treated as falling within the general recoverability window because the suit is filed within the 6-year period from the trigger date.
- Past damages input: $120,000
- Filing occurs within the general 6-year window
- Allocated past damages (example output): $120,000
Step 3: Allocate future damages using the SOL boundary
Future damages start on Jan 1, 2025 and run through Dec 31, 2026.
Key boundary:
- Conceptual SOL anchor: Jan 15, 2025
Because future damages can straddle a limitation boundary, the allocation is sensitive to where the model draws the SOL anchor relative to the future period. In this worked example, DocketMath allocates future damages based on overlap between the future-damages interval and the actionable portion of the timeline.
Future damages window: Jan 1, 2025 – Dec 31, 2026
Overlap window (starting at the SOL anchor): Jan 15, 2025 – Dec 31, 2026
Approximate day-counts (for illustration):
- Total future period: 731 days (Jan 1, 2025 to Dec 31, 2026)
- Overlap portion: about 717 days (Jan 15, 2025 to Dec 31, 2026)
- Overlap fraction ≈ 717 / 731
Future damages input: $80,000
Allocated future damages (example output):
- $80,000 × (717 / 731) ≈ $78,400
Step 4: Total allocated damages
Add allocated past and allocated future:
| Category | Input amount | Allocation basis | Allocated amount |
|---|---|---|---|
| Past damages | $120,000 | within general 6-year SOL window | $120,000 |
| Future damages | $80,000 | overlap with actionable SOL portion | ~$78,400 |
| Total | $200,000 | ~$198,400 |
What In DocketMath, this appears as (practical output framing)
In a DocketMath “damages allocation” run, the results are typically summarized as:
- Allocated Past Damages: $120,000
- Allocated Future Damages: ~$78,400
- Total Allocated Damages: ~$198,400
- SOL boundary anchor driven by Ark. Code Ann. § 5-1-109(b)(2) and the 6-year general/default period
Warning: In timing-driven allocations, small changes to the “trigger date” or the future start date can noticeably affect how much of the future period overlaps the SOL anchor.
Sensitivity check
Change one input at a time to see how the allocation moves. This is the “what if” section where DocketMath’s practical value shows—especially when future damages are near the SOL boundary.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Sensitivity 1: Filing date moved by +90 days
Adjust Date suit filed from June 1, 2024 to August 30, 2024 (+90 days).
- This still falls within the 6-year window ending around Jan 15, 2025
- Expected impact: past damages allocation stays about the same; future overlap changes only slightly (depending on how the model anchors the boundary)
Directional expectation:
- Past: ~same
- Future: slight change (likely still near ~$78k–$79k)
Sensitivity 2: Trigger date moved back by 30 days
Change Date of injury/trigger from Jan 15, 2019 to Dec 16, 2018 (-30 days).
- The conceptual SOL anchor moves later
- That tends to increase overlap with the future damages window
Directional expectation:
- Past: ~same
- Future: increases modestly (example outputs could move from ~$78,400 toward something like ~$79,500, depending on day-count conventions)
Sensitivity 3: Future damages start date delayed by 60 days
Change Future damages start date from Jan 1, 2025 to Mar 2, 2025 (+60 days).
Now the future period shifts later relative to the conceptual SOL anchor:
- In a strict overlap model, future damages could be fully outside the portion deemed actionable by the boundary logic (depending on how the tool draws the anchor window).
- That would materially reduce the allocated future component.
Directional expectation:
- Past: likely unchanged
- Future: decreases sharply (and could approach $0 in a strict boundary/overlap implementation)
Pitfall: A zeroed-out “allocated future” result in a boundary-based allocation does not necessarily mean the future damages are legally unavailable—it means the allocation method tied to a SOL-window overlap may assign little or no recoverability to the shifted future timing.
Sensitivity summary (directional)
| Input changed | Past damages allocation | Future damages allocation |
|---|---|---|
| Filing date +90 days (still within SOL) | ~same | slight to none |
| Trigger date -30 days (SOL boundary later) | ~same | increases |
| Future start +60 days (future shifts relative to boundary) | ~same | decreases sharply |