Why Damages Allocation results differ in Illinois
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Damages Allocation calculator.
If you run the Damages Allocation calculator in DocketMath for Illinois matters, you may notice allocation outputs that don’t match across datasets or versions. In Illinois, the mismatch usually comes from a small set of repeatable variables—especially when the tool is pairing time windows to damages.
Below are the top five reasons Illinois results differ, even when the same parties are involved.
| Difference trigger | What changes in the model | Typical symptom in output |
|---|---|---|
| 1) Different assumed time window | The calculator applies a lookback period based on the selected rule set | One run shows fewer payable months/years than another |
| 2) Ambiguous incident date vs. claim date | The start of the calculation shifts | Total allocable damages move materially |
| 3) Inconsistent allocation method settings | How DocketMath distributes damages across categories | Category totals may agree, but category splits differ |
| 4) Missing or altered damages line items | The calculator sums and then allocates from different inputs | Totals change, or certain categories drop to zero |
| 5) Jurisdiction rule configuration differences | Illinois uses a general/default statute of limitations rule when no claim-type-specific sub-rule is selected | Results diverge from other states or “other Illinois” runs |
A key Illinois anchor for this analysis: Illinois’ general statute of limitations is 5 years under 720 ILCS 5/3-6. When no claim-type-specific sub-rule is found or selected, DocketMath uses this general/default period to set the lookback window.
- General SOL Period: 5 years
- General Statute: 720 ILCS 5/3-6
- Rule-selection note: No claim-type-specific sub-rule was found for this setup, so the general/default period is the rule in these runs.
Practical takeaway: If one run used the general/default 5-year SOL (720 ILCS 5/3-6) and another run used a different time window (or a claim-type-specific shortcut), the allocation will predictably diverge—even if all other inputs match.
How to isolate the variable
Use this checklist to pinpoint why two DocketMath outputs don’t reconcile.
- Freeze the jurisdiction and tool settings so both runs use the same rule set.
- Compare one input at a time (dates, rates, amounts) and re-run after each change.
- Review the breakdown to see which segment or assumption drives the difference.
1) Lock the jurisdiction and confirm the time rule
In your DocketMath run, confirm you’re using US-IL and the default SOL behavior:
- Rule applied: General/default 5-year SOL (720 ILCS 5/3-6)
- No claim-type-specific sub-rule: meaning the model uses the general period
If you see a lookback window other than 5 years, you’ve found the first likely cause.
2) Compare the exact dates used to compute the lookback
Even small date shifts matter. Focus on:
- Incident / damage start date
- Filing / valuation cut-off date
- Any “event” date chosen during import or mapping
Then verify both runs compute the same number of months/years falling inside the 5-year window.
3) Normalize the damages inputs
Create a “diff view” of your line items:
- Total damages per category
- Any withheld / blank categories
- Whether “unknown” values were treated as zero vs. excluded
A single missing line item can change the denominator used for allocation, which changes the split even if the overall picture looks similar.
4) Verify allocation method settings
If your runs used different toggles (for example, proportional vs. weighted allocation), totals may look close while splits diverge. Lock the method and rerun.
5) Confirm the tool run configuration is identical
Reconcile:
- Jurisdiction selection (US-IL)
- The damages-allocation calculator configuration/version
- Any imported assumptions (especially date-field mapping to the calculator’s expected fields)
For a consistent starting point, use the primary CTA: /tools/damages-allocation.
Next steps
Re-run with a controlled test case
Keep everything constant except one variable (date mapping, SOL window behavior, or allocation method). Record how the output changes.Create a two-run comparison sheet
One row per run:- Lookback window start/end
- Total allocable damages
- Split by category
Validate the Illinois time rule once, then stop guessing
Illinois general SOL is 5 years under 720 ILCS 5/3-6—and when no claim-type-specific sub-rule is found, that general/default period governs the time window.If disagreement persists, audit the mapping
Most “mysterious” differences turn out to be:- date-field mapping (incident date mapped to filing date, etc.)
- category exclusions introduced by the dataset import
Warning: Don’t fix discrepancies by changing multiple settings at once. Adjust one lever per run so you can attribute the difference.
