How to run Structured Settlement in DocketMath for Arkansas

Step-by-step

This guide shows how to run a Structured Settlement workflow in DocketMath for Arkansas (US-AR) using jurisdiction-aware rules and the structured-settlement calculator template. It’s written to help you model a structured payment plan and how timing can affect the results—not to provide legal advice.

1) Start from the Structured Settlement tool

1. Open DocketMath’s Structured Settlement calculator via the primary CTA:

   • **/tools/structured-settlement
2. Select the jurisdiction:

   • Jurisdiction: **US-AR (Arkansas)

2) Confirm the timing rule DocketMath will use (Arkansas SOL baseline)

For Arkansas, DocketMath’s jurisdiction settings should apply the general statute of limitations (SOL) baseline tied to Arkansas’s general limitations rule.

Use this provided default SOL baseline:

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

3) Enter the inputs that drive the structured payment math

DocketMath’s Structured Settlement calculator typically models settlement value by splitting it into a lump sum and/or periodic payments over a schedule.

Enter the inputs that match your settlement structure, such as:

• Start date / first payment date (controls the payment stream timeline)
• Payment frequency (e.g., monthly, annual)
• Number of payments or end date (controls total duration)
• Payment amounts

  • either one recurring amount, or a list/series if the tool supports multiple phases
• Discount rate / present value assumption (if the tool asks)
• Lump sum amount (if applicable)

If your structure includes phases (for example, different amounts early vs. later), enter each phase according to how DocketMath’s UI segments the plan, rather than averaging everything.

4) Set the Arkansas “timing context” fields

When DocketMath asks for timing context tied to enforceability windows or limitations modeling, anchor those fields using the Arkansas default SOL baseline:

• SOL baseline: 6 years
• Statutory citation: **Ark. Code Ann. § 5-1-109(b)(2)

Practically, that means:

• If the tool asks “how long you have” based on a limitations clock, model a 6-year window.
• If it asks “is it within the limitations period,” the outcome is based on whether the settlement-relevant dates you input fall inside the 6-year baseline.

5) Run the calculation and interpret output changes

After you run DocketMath, review outputs such as:

• Total nominal payout (sum of scheduled payments + any lump sum)
• Present value (depends on the discount assumptions)
• Payment schedule breakdown (dates and amounts by period)
• SOL/timing flags (if the calculator includes them for this workflow)

Use a simple “what changes if I adjust X?” approach to interpret results:

• Change the first payment date

  • Earlier payments typically increase present value; later payments typically decrease it (because of discounting).
• Change payment frequency

  • More frequent payments can change both cash flow timing and present value.
• Extend the end date

  • Increases nominal total; present value changes depending on how far out additional payments extend.
• Shift value between lump sum and installments

  • Moving more value into the lump sum generally increases present value when discounting is positive, because the cash is received sooner.

6) Export or capture the structured schedule for review

If DocketMath provides a download/export or copyable schedule:

• Capture the full payment table (date + amount)
• Capture the parameters used (frequency, discount assumption, start date, and any phase inputs)
• Capture any timing/SOL baseline indicator tied to **Ark. Code Ann. § 5-1-109(b)(2)

That way, you can compare scenarios without re-entering everything.

Common pitfalls

Structured settlement modeling is math-heavy and timing-sensitive. These are the most common issues when running the Arkansas workflow in DocketMath:

• The provided Arkansas jurisdiction data includes only the general/default baseline:

  • 6 years
  • **Ark. Code Ann. § 5-1-109(b)(2)

• If no claim-type-specific sub-rule is provided, treat the calculator as using the general baseline.

• A small date shift changes which payments arrive earlier vs. later, which can affect both timing indicators and present value.

• For example: selecting monthly frequency but entering a count that was meant for yearly payments will change the total duration and schedule.

• Two plans can have the same nominal payouts but different present values if discount rate assumptions differ.

• If the plan changes over time, enter those phases explicitly if DocketMath supports it—don’t average different installments into one number.

Try it

Use this quick scenario checklist to run your first Arkansas structured settlement computation in DocketMath:

• 6 years using **Ark. Code Ann. § 5-1-109(b)(2)
• No claim-type-specific sub-rule is included in the provided jurisdiction data, so the general/default period is used

Want to stress-test your model quickly? Create 2–3 runs that differ in only one variable:

• Run A: original first payment date
• Run B: first payment moved forward by 3 months
• Run C: end date extended by 1 year

Compare present value and any timing/SOL flags to see whether the results are driven more by cash flow timing or by value allocation.

Related reading

• Structured Settlement Calculator Guide for Alabama
• Structured Settlement Calculator Guide for Arizona
• Structured Settlement Calculator Guide for Colorado