Why Structured Settlement results differ in Arkansas

The top 5 reasons results differ

If you run DocketMath’s Structured Settlement calculator for the same case facts in Arkansas (US-AR), you may still see different outputs across attempts. That’s not automatically a “calculator bug”—it’s usually the interaction between inputs (assumptions) and Arkansas’s default statute of limitations (SOL) baseline.

Arkansas generally uses a 6-year limitations period for many civil claims. The governing general provision is Ark. Code Ann. § 5-1-109(b)(2). No claim-type-specific sub-rule was found, so the practical diagnostic approach is to treat 6 years as the starting baseline, not a guaranteed, case-specific rule.

Here are the top 5 reasons structured settlement results differ in Arkansas:

1. **Wrong start date (when the clock begins)

   • DocketMath projections can change materially depending on whether you model the start as a filing-date proxy, an incident date, a discovery date, or a notice/policy trigger.
   • Even a shift of 30–180 days can change timing-based inputs that affect present value.

2. **Different SOL modeling assumptions (baseline mismatch)

   • Arkansas’s general/default SOL period is 6 years under Ark. Code Ann. § 5-1-109(b)(2).
   • If one run effectively uses a shorter or longer horizon (for example, due to an internal assumption or category setting), the model’s timing horizon can shift—leading to different projected totals.

3. Payment schedule structure differs

   • Structured settlement outputs depend heavily on how payments are scheduled, such as:

     • lump sum + annuity installments
     • level vs increasing payments
     • period-certain vs life-contingent streams
   • Changing schedule structure changes cashflow timing, which changes present value.

4. Interest rate / discount rate inputs differ

   • Many discrepancies come from selecting different discount assumptions (e.g., conservative vs aggressive yields).
   • In longer payment streams, small rate differences can compound quickly and move totals meaningfully.

5. Inflation and escalation settings differ

   • If you model payments as fixed dollars but the intended structure includes escalation (or the reverse), outputs can diverge—especially over multi-decade streams.

Common pitfall: Switching between an “incident date” and a “demand/notice date” in different runs can accidentally change the effective timing horizon, even when the payment terms are identical.

How to isolate the variable

Use DocketMath to run a controlled diagnostic: change one input at a time, keep everything else constant, and measure the impact.

1. Lock the Arkansas SOL to the general/default baseline

   • Set the limitations horizon to 6 years, based on Ark. Code Ann. § 5-1-109(b)(2).
   • Because no claim-type-specific sub-rule was identified in the provided materials, don’t shorten or lengthen the period unless you have a documented basis for doing so.

2. Run a baseline

   • Use your best estimates for:

     • payment start timing
     • payment frequency
     • payment amounts
     • term/certain or equivalent schedule settings
     • discount/interest and any escalation/inflation toggles
   • Record the totals from this baseline run.

3. Swap only one lever at a time

   • Change only the start date (and keep SOL horizon at 6 years).
   • Re-run and record the delta.
   • Next, change only the discount rate.
   • Re-run and record the delta.
   • Next, change only escalation/inflation settings (on vs off, or rate).
   • Next, change only payment schedule structure (level vs increasing, etc.).

4. Create a difference table

   • Track deltas rather than relying on final numbers alone.

For fast navigation, start your Arkansas-anchored run with DocketMath here: structured settlement tool.

Next steps

1. Standardize your “time zero” date

   • Pick a single consistent anchor for the diagnostic (even if you later refine it). Use the same “time zero” across runs so differences come from inputs, not shifting definitions.

2. Document the SOL approach

   • Record that Arkansas’s general/default SOL baseline is 6 years under Ark. Code Ann. § 5-1-109(b)(2).
   • Also record that no claim-type-specific sub-rule was found in the materials used here—so your comparisons remain apples-to-apples.

3. Validate payment schedule inputs

   • Confirm the schedule type matches the actual structure:

     • fixed vs increasing
     • timing of installment start
     • lump sum timing (if any)
     • installment frequency
     • term/certain assumptions

4. Run two “sanity check” scenarios

   • Scenario A: conservative discount rate, escalation off.
   • Scenario B: different discount rate with escalation on (if appropriate).
   • If A and B produce wide variance, your output differences may be driven more by finance assumptions than by date/SOL modeling.

Gentle disclaimer: This is a diagnostic and educational workflow, not legal advice. Structured settlement projections depend on inputs and claim facts, and jurisdiction-specific analysis may be required.

Related reading

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