Why Structured Settlement results differ in Illinois

The top 5 reasons results differ

If you run the Structured Settlement calculator in DocketMath for Illinois (US-IL) and notice that similar-looking cases produce different results, the cause is usually jurisdiction-aware inputs interacting with Illinois timing rules. Illinois uses a 5-year general limitations period for many personal injury–related actions under 720 ILCS 5/3-6. (Statute reference: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai)

DocketMath can’t standardize outcomes when the inputs aren’t the same. Two entries that “look alike” can still embed different timing, risk, or netting assumptions—so the math will diverge even if the underlying settlement concept is similar.

Here are the top 5 reasons:

1. Different “clock starts” (when the claim is considered ripe)

   • Downstream settlement projections often depend on when payments are scheduled and when parties start assessing risk.
   • Even if the structure is the same, changing the effective date (or the start date your workflow treats as operative) changes discounting and present value.

2. 5-year general limitations period affects valuation assumptions

   • Illinois provides a general/default period of 5 years under 720 ILCS 5/3-6 (per the jurisdiction data you’re using).
   • Your workflow may incorporate that timeline (for example, when estimating exposure, expected dispute window, or how long settlement timing might realistically be delayed).
   • Important: The provided jurisdiction data did not identify a claim-type-specific sub-rule, so treat 5 years as the general baseline, not a guarantee that every scenario maps to the same exact timing rule.

3. Confusion between “payment schedule” and “legal timeline”

   • Structured settlements model future payment streams (e.g., an initial payment plus periodic installments).
   • But the legal timeline (and the workflow’s assumptions about it) can change the probability-weighted view of whether payments occur on schedule, are delayed, or change through process.
   • If your DocketMath inputs blend these concepts differently across runs, results will differ.

4. Different discount rate / inflation assumptions

   • Even when the “structure” looks identical, small input differences can swing outputs:

     • discount rate (risk/finance assumption)
     • timing granularity (monthly vs annual steps)
     • inflation adjustment settings (if enabled in your workflow)

5. Credit / tax / fee modeling differences

   • Outputs can diverge when runs net out different items:

     • transaction fees or service charges
     • offset assumptions
     • any modeling toggles you apply before presenting the “net” number
   • DocketMath reflects the assumptions you enter—so two “same structure” inputs can still produce different totals.

How to isolate the variable

You can debug this like a spreadsheet: change one variable at a time, and keep everything else constant.

A quick DocketMath isolation checklist

• Lock the payment schedule (start date, number of installments, frequency)
• Use the same discount rate/inflation setting across runs
• Normalize dates so the “effective date” means the same thing in both runs
• Record the exact assumptions you entered (copy the input set for each run)

Create two runs that differ only by the Illinois-linked timing input

Because your Illinois jurisdiction baseline is the general 5-year period, focus on timing behavior.

• Run A: Use the timeline assumption aligned to the 5-year general baseline from 720 ILCS 5/3-6.
• Run B: Keep the rest of the math the same, but shift the effective date by a known amount (e.g., 30/90/180 days).

If the present value moves a lot between Run A and Run B, the differences are likely driven by timing (dates) rather than by the structure itself.

Sanity-check against the statute baseline

Your jurisdiction data states:

• General SOL Period: 5 years
• General Statute: 720 ILCS 5/3-6
• No claim-type-specific sub-rule was found in the provided jurisdiction data, so the 5-year period is the default baseline to apply in your workflow.

If a DocketMath run appears to behave as though a different limitations period applies, it usually means an input or template step is overriding the general baseline.

Next steps

1. Run one baseline scenario in DocketMath (US-IL)

   • Use the 5-year general baseline consistent with 720 ILCS 5/3-6.
   • Match the payment schedule of the cases you’re comparing.

2. Duplicate the scenario

   • Change only one element at a time:

     • effective date
     • discount rate
     • inflation toggle
     • installment frequency

3. Calculate the sensitivity

   • Track which change creates the largest swing in:

     • total present value
     • payment timing impact
     • any net amounts (if your model includes offsets or fees)

4. Document your “assumption set”

   • Write down the input set for each run so you can explain result differences quickly.

Gentle note: This is a practical modeling guide, not legal advice. For legal questions about limitations periods or claim classification, consult a qualified attorney.

If you want to apply the Illinois-aware workflow directly, use the tool here: /tools/structured-settlement.

Related reading

• Browse the blog