How to interpret Structured Settlement results in Arkansas
6 min read
Published April 15, 2026 • By DocketMath Team
What each output means
Run this scenario in DocketMath using the Structured Settlement calculator.
When you run a Structured Settlement calculation in DocketMath for Arkansas (US-AR), the outputs are meant to help you interpret what a structured settlement “pays” in cash terms and how that payment stream may look in today’s dollars.
Below is a practical guide to the common result lines you may see from the calculator.
1) Total scheduled payments
Total scheduled payments is the sum of all future payment amounts shown in the structure (for example, “$X per year for Y years,” or “$A due at date B”).
It answers:
- What is the contract paying, on paper?
- How much money will be distributed over time (generally without discounting to today’s dollars).
2) Present value (PV) / “today’s value”
If your results include present value (PV), DocketMath converts future payments into today’s dollars using the calculator’s discounting assumptions.
In general:
- A higher discount rate → PV typically falls
- A lower discount rate → PV typically rises
PV helps you compare a structure to a lump-sum amount and interpret “value” under the calculator’s assumptions. It’s a model-based valuation metric, not a guarantee of what a court would order.
3) Undiscounted totals vs. discounted totals (if shown together)
Many structured settlement calculators show both:
- Undiscounted total: the arithmetic sum of payments (what will be paid)
- Discounted value (PV): what those payments are worth today under the model
Think of it like this:
- Undiscounted total answers: “How much is paid?”
- PV answers: “How much is that likely worth today?”
Gentle disclaimer: PV depends on the assumptions used in DocketMath—especially timing and the discount rate. It’s not a legal conclusion and isn’t a substitute for reviewing the settlement agreement and getting legal advice when appropriate.
4) Payment timing and start date effects
Structured settlements often include a delay before payments begin (for example, first payment due 30/60/90 days after a triggering event). Outputs that depend on timing (including PV and any timing-sensitive comparisons) can change when:
- the start date shifts earlier or later, or
- the payment schedule changes (monthly vs. annual; level vs. stepped)
Even if headline payment amounts stay the same, timing changes can materially affect PV, because PV is sensitive to how soon cash flows arrive.
5) “Net” results (only if shown)
If your DocketMath output includes a net line or adjustment-based view, treat it as model output—not an automatic legal or contractual determination.
If you see “net” results:
- Check what adjustments were applied (for example, discounting only vs. other model adjustments)
- Use the “net” figure as one way to summarize results, and still confirm the underlying schedule matches the agreement.
What changes the result most
For Arkansas-aware interpretation, the biggest “real-world” impact usually comes from timing—especially how long you have to pursue legal steps after a triggering event. The DocketMath math still depends on inputs like discount rate and schedule, but Arkansas timing rules affect what time window matters for action.
Arkansas default SOL period (general/default):
- General SOL Period: 6 years
- General Statute: **Ark. Code Ann. § 5-1-109(b)(2)
- Important: No claim-type-specific sub-rule was found in the provided jurisdiction data, so the 6-year default is the baseline discussed here.
The biggest drivers in DocketMath structured-settlement outputs
Use this checklist to identify what most affects your results:
- Discount rate (if you can adjust it): higher rate → lower PV; lower rate → higher PV
- Start date / first-payment timing: delays reduce PV (cash arrives later)
- Payment frequency: monthly vs. annual can shift effective timing of cash flows
- Number of payments / term length: more payments generally increases both total and PV
- Step-ups / increases (if included): higher later payments raise PV
- Lump-sum components (if included): an earlier lump sum increases PV more than the same amount later
How the Arkansas 6-year SOL concept affects “what you can do”
DocketMath does not determine legal rights. But when interpreting results for Arkansas, you typically also think about whether relevant issues are still within a workable time window for taking action.
Using:
- 6-year default period under **Ark. Code Ann. § 5-1-109(b)(2)
you can frame your timeline this way:
- If the relevant triggering event is within the last 6 years, the default SOL window is more favorable for pursuing time-sensitive steps.
- If the triggering event is more than 6 years old, the default timeframe would generally be harder to satisfy.
Pitfall to avoid: Don’t confuse “the structure’s scheduled payments” (which may continue for years) with the deadline to take certain legal steps, which can be governed by statutes like Ark. Code Ann. § 5-1-109(b)(2).
Next steps
Open the calculator you plan to use
- Start at: /tools/structured-settlement
Capture your structure inputs exactly
- Term length and total number of payments
- Payment dates (or start date) and frequency
- Step-ups or any special lump-sum payments
Record the DocketMath assumptions shown on-screen
- Discount rate used (if shown)
- “As of” or valuation date (if the interface provides it)
Compare timing to Arkansas’s 6-year default SOL baseline
- Identify the triggering event date you’re interpreting
- Compare it to the 6-year default timeframe under Ark. Code Ann. § 5-1-109(b)(2)
- Because the provided jurisdiction data found no claim-type-specific sub-rule, treat 6 years as the default baseline for this interpretation
Sanity-check by matching the schedule to the actual settlement documents
- Verify payment amounts and dates match the settlement agreement or exhibit
- If you find any mismatch, rerun DocketMath—small date changes can shift PV meaningfully
Run sensitivity checks
- If DocketMath lets you vary discount rate or start date, rerun with updated assumptions to see which output lines are most sensitive (usually PV)
