How to run Settlement Allocator in DocketMath for Arkansas

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

Below is a jurisdiction-aware walkthrough for running Settlement Allocator in DocketMath for Arkansas (US-AR). This guide focuses on operational steps—what to enter, what assumptions DocketMath uses for Arkansas, and how to interpret the output. It’s not legal advice; treat results as a budgeting/allocation aid and verify with case-specific documentation.

1) Start the tool from the primary call-to-action

Open Settlement Allocator here:

• /tools/settlement-allocator

If you’re coming from a different page, use DocketMath’s search or navigate to the Tools area, then select Settlement Allocator.

2) Select the jurisdiction and confirm Arkansas rules are active

Within the tool, set the jurisdiction to US-AR (Arkansas). DocketMath will apply Arkansas time-basis settings relevant to the calculator’s logic.

For Arkansas, DocketMath uses the general/default statute of limitations period for its settlement allocation timing assumptions:

• General SOL Period (default): 6 years
• Ark. Code Ann. § 5-1-109(b)(2) (general limitation)

Important note (claim-type-specific rules): In Arkansas for this tool run, no claim-type-specific sub-rule was found. That means DocketMath applies the general/default 6-year period under Ark. Code Ann. § 5-1-109(b)(2) as the governing assumption for timing.

3) Enter case inputs (match them to the tool’s field labels)

Settlement Allocator is designed to turn a set of case facts into an allocation range. While field names can vary slightly by UI version, you’ll typically provide:

• Demand / settlement amount (the fund to allocate)
• Key dates (commonly: incident/occurrence date and/or notice date, plus the date of filing if the tool asks)
• Potential claim categories you want included in the allocation logic
• Allocation weights or splits (if your DocketMath version supports proportional allocation factors)

How to think about inputs in Arkansas terms

The calculator needs timing inputs to relate your dates to the 6-year default SOL window under Ark. Code Ann. § 5-1-109(b)(2).

• If your event dates are within that window, the model will generally treat the claims as more viable under its timing assumption.
• If dates fall outside the 6-year period relative to the tool’s relevant “anchor” date, the allocation may shift because the model treats time-bar risk differently.

Checklist for clean data entry:

4) Choose allocation options (if your DocketMath version offers them)

Some DocketMath builds include switches such as:

• enabling/disabling SOL-based adjustments
• choosing whether to allocate across claim buckets equally vs. weighted
• setting assumptions for damages components

If you see SOL-related options, keep Arkansas enabled. When SOL logic is on, DocketMath will apply the 6-year default assumption under Ark. Code Ann. § 5-1-109(b)(2) (not claim-type-specific variations, since none were identified for this run).

5) Run the calculation

Click Calculate / Run.

Once the run completes, you’ll typically see:

• a total allocation broken into categories (or claimant components)
• an adjustment explanation tied to timing/SOL assumptions
• summary figures reflecting the selected settlement amount and enabled options

6) Interpret the output (and watch what changes when you edit dates)

Use these output behaviors to validate your run:

A. Allocation totals

• Your allocation should reconcile to the settlement amount you entered (or show a remaining/unallocated balance if the tool supports “unassigned” buckets).

B. SOL timing effects Because Arkansas is set to the general/default 6-year period:

• Dates within the 6-year lookback generally produce allocations that assume more viable timing risk within the model.
• Dates beyond 6 years may cause allocations to reflect increased time-bar risk within the model.

C. Category-level differences If you input multiple claim types/categories, the distribution may change even when the settlement amount stays constant—because the SOL timing assumption influences relative weights across categories.

7) Re-run with controlled changes to sanity-check your assumptions

A reliable way to test robustness is to change one variable at a time.

Practical re-run plan:

If small date changes cause large swings, check:

• whether you are near the 6-year boundary under **Ark. Code Ann. § 5-1-109(b)(2)
• whether you selected the correct anchor date the tool uses
• whether any other assumptions (weights, bucket enablement) changed between runs

Common pitfalls

These are the most common issues that lead to misleading outputs when running Settlement Allocator for Arkansas:

• Using the wrong anchor date

  • The SOL logic depends on which date the tool uses for its timing comparison.
  • Confirm the tool prompt clearly identifies the anchor date.

• Assuming claim-type-specific SOL rules were applied

  • For this tool run, DocketMath applies the general/default period only: 6 years under Ark. Code Ann. § 5-1-109(b)(2).
  • No claim-type-specific sub-rule was found for this jurisdiction setup, so you should not expect claim-specific SOL variations in the output.

• Entering estimated dates

  • Allocations can pivot near the 6-year mark. Even “small” date differences can be material in a boundary-driven model.

• Forgetting to reconcile the settlement amount

  • If allocations don’t add up to your input settlement amount, verify whether:

    • some categories are disabled,
    • there is an “unallocated” bucket,
    • or weights changed during re-runs.

• Changing multiple inputs at once during testing

  • When testing sensitivity, change one input at a time so you can attribute differences to a specific factor.

Try it

Ready to run a sample allocation in your own workflow? Start here:

• /tools/settlement-allocator

Before you click Calculate, use this quick pre-flight checklist:

After the run:

• Compare allocations across categories.
• Re-run once with the anchor date moved slightly (e.g., ±60 days) to see how sensitive the model is near the 6-year boundary.

If you want broader DocketMath context, you can also browse:

• Browse the blog

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado