How to interpret Damages Allocation results in Illinois

What each output means

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath → Damages Allocation (US-IL), the calculator applies Illinois jurisdiction-aware rules to translate your case’s damages inputs into an allocation-style breakdown you can use for internal planning (e.g., settlement conversations, drafting support, or audit organization). Treat the outputs as estimation and structuring help, not a final judicial determination.

Below are the outputs you’ll typically see in an Illinois run, and how to interpret them:

1. Allocated amounts by category

   • This shows how your total claimed damages are grouped into the category buckets you entered (for example, category-level totals that the tool can time-split).
   • Practical meaning: each bucket is the portion the tool will treat as subject to the same Illinois timing logic (in this run), then recombine into in-scope/out-of-scope results.

2. **Jurisdictional timing window (Illinois lookback)

   • For Illinois, DocketMath uses the general statute of limitations period: 5 years.
   • The general/default rule is drawn from 720 ILCS 5/3-6, which provides a 5-year limitations period for many civil actions without a more specific limitations rule.
   • Important clarity for this calculator: No claim-type-specific sub-rule was found, so the calculator applies the 5-year default across the provided damages inputs rather than switching limitations terms by claim label.

3. In-scope vs. out-of-scope portions

   • If your damages cover multiple years, the tool estimates how much falls within the 5-year lookback and how much falls outside it.
   • Practical meaning:

     • In-scope amounts: the portion most consistent with the calculator’s Illinois-default limitations timing.
     • Out-of-scope amounts: the portion effectively excluded from the tool’s timing window (e.g., losses occurring earlier than the 5-year window).

4. Net allocable figure

   • The “net” number is typically the consolidated estimate derived from the in-scope portion(s).
   • Practical meaning: use this as a single-number summary of what the tool thinks remains most supportable under the Illinois general 5-year default framework used in this run.
   • It is still a model output—use it to structure your work, not to replace a claim-specific limitations analysis.

5. Assumptions summary

   • DocketMath generally displays the jurisdiction framework it used (here: US-IL) and the governing limitations baseline (5-year default).
   • Practical meaning: the largest error is assuming the tool automatically picks a claim-specific limitations rule. In this Illinois run, it does not—it stays on the general 5-year rule from 720 ILCS 5/3-6.

Gentle reminder: damages allocation results are model-based estimates. They don’t account for every pleading nuance, accrual theory, tolling issue, or claim-specific limitations argument. Use them to guide documentation and next-step analysis.

Quick checklist to read the results correctly

What changes the result most

In Illinois runs using DocketMath’s Damages Allocation, the output typically changes most when you alter timing inputs, the date coverage of each damages entry, or how your damages are split across categories. Because this run uses the general/default 5-year limitations period (and no claim-type-specific sub-rule was found), the dominant driver is usually how much of the total falls inside vs. outside the 5-year window under 720 ILCS 5/3-6.

Here are the most common “result movers”:

1. **Loss start dates (earlier = more out-of-scope)

   • Move earlier events farther back, and the tool will likely increase the out-of-scope portion.
   • Under the general 5-year framework, older losses are less likely to remain within the lookback window.

2. **Loss end dates or ongoing timing (later = more in-scope)

   • Push the timing later (or model ongoing losses as extending forward), and the tool typically increases the in-scope share.

3. How you break damages into categories

   • Even though the timing window is the same baseline across the inputs in this run (5 years), the relative size of each category still affects the shape of the allocation table.
   • If one category concentrates earlier losses, it can pull down the net allocable outcome more than categories concentrated later.

4. Granularity of date entries

   • Using more precise time splits (e.g., monthly/quarterly where available) can produce a more nuanced in-scope/out-of-scope split.
   • Coarser inputs (e.g., broad start-to-end ranges) can yield a smoother or more generalized allocation estimate.

Bottom line: since this Illinois setup applies the general 5-year default without claim-type-specific switching, changes that affect the percentage of damages landing within the 5-year window will usually have the biggest impact.

Next steps

To use the Damages Allocation outputs effectively in an Illinois workflow, focus on verification, documentation, and controlled re-runs.

1. Reconcile your timeline to the 5-year window

   • Identify the date ranges driving the tool’s in-scope/out-of-scope split.
   • Compare those dates to your underlying records (e.g., ledgers, invoices, pay history, milestones, or other evidence used to support damages).

2. **Write a short “allocation memo” (internal use)

   • Include:

     • Jurisdiction: US-IL
     • Limitations baseline applied: 5-year general default
     • Statute reference: 720 ILCS 5/3-6
     • The tool’s total claimed vs. net allocable outputs
   • Keeping this memo aligned with your DocketMath inputs will reduce inconsistencies later.

3. Stress-test the inputs with a “date shift” run

   • Run the tool at least twice:

     • Once using your earliest loss date you plan to rely on
     • Once with a later cutoff (for example, shifting the start date forward by a few months)
   • If the net allocable figure swings sharply, your timeline inputs are the primary driver—double-check them first.

4. If you believe claim-specific limitations could apply, plan a separate review

   • This Illinois calculator run did not find a claim-type-specific sub-rule.
   • If your pleaded claims typically involve different limitations logic, treat the DocketMath output as a baseline estimate and consider a separate, claim-focused limitations analysis as a next workstream.
   • DocketMath is best used to structure the analysis, not to replace legal research.

5. Use the output to format damages support

   • When you build charts or submission-ready summaries, mirror the tool structure:

     • In-scope vs. out-of-scope
     • Then the net allocable estimate
   • If you’re starting from scratch, begin with the baseline and only adjust inputs where you have evidence-backed support.

If you want to generate or iterate results quickly, you can start from /tools/damages-allocation.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules