Choosing the right Damages Allocation tool for Illinois

Choose the right tool

Run this scenario in DocketMath using the Damages Allocation calculator.

If you’re trying to allocate damages in an Illinois matter—such as splitting categories of loss, reconciling multiple time periods, or preparing a damages narrative for a filing—DocketMath’s Damages Allocation tool can help you structure the math consistently.

Because your jurisdiction is Illinois (US-IL), the tool’s workflow should be paired with the correct jurisdiction-aware rule set, particularly when your damages window is driven by a statute of limitations.

1) Start with the Illinois limitations window (default rule)

For Illinois, the general/default statute of limitations is 5 years under:

• 720 ILCS 5/3-6 (General Statute; general limitations period)
  Source: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai

Per the jurisdiction data you provided: General SOL Period: 5 years.

Also, your note states that no claim-type-specific sub-rule was found. That means you should treat the 5-year general period as the default and not apply claim-specific exceptions based on these inputs.

2) How the right tool choice affects the “damages allocation” outcome

Damages allocation often turns on two practical decisions:

• What damage components you’re allocating (e.g., categories of loss or different cost types)
• What time span counts for those components (often anchored by an SOL-driven filtering window)

If your allocation logic includes a damages period ending at a cutoff date (for example, a filing date, demand date, or another boundary in your workflow), the length of the SOL window can change the result by:

• determining which months/years are included,
• determining which earlier amounts get excluded,
• and shifting how totals roll up in the final allocation summary.

In short: even with the same underlying numbers, aligning the tool’s date filtering to the Illinois general/default 5-year window can materially change allocated totals.

3) Choose DocketMath’s Damages Allocation and verify SOL alignment

Use DocketMath’s Damages Allocation tool when you need structured output such as:

• allocation totals by component,
• totals by period, or
• totals after filtering a specific date range.

Then confirm your inputs match the Illinois default approach:

• Jurisdiction: US-IL
• Limitations window used by the tool/rules: 5 years
• Legal basis (general limitations period): 720 ILCS 5/3-6

A typical operational pattern when you’re SOL-driven is:

• Pick a start date (e.g., when damages began or when relevant conduct started for your timeline)
• Pick an end/cutoff date (e.g., filing date or another defined boundary in your workflow)
• Use the SOL window to determine how much of the start-to-end span is included in the allocation

4) Inputs to prepare before you run the calculator

Before you run Damages Allocation, gather the minimum inputs needed to produce an allocation you can explain clearly:

• Jurisdiction: US-IL
• SOL period to apply: 5 years (default/general)
• Key dates for your damages timeline:

  • a damages start date (or first relevant transaction/date)
  • a damages end/cutoff date
• Damage component breakdown:

  • for example, amounts by category and/or by time slices that match your records (monthly, quarterly, annual, etc.)

To avoid mismatched results, keep your definitions consistent:

• If the tool excludes amounts outside the SOL window, your source totals should reflect the same underlying accounting basis you intend to summarize.

5) Practical example of how outputs change with the 5-year rule

Suppose your damages timeline includes amounts going back 7 years to a present cutoff date.

Using Illinois’s general/default 5-year rule (5 years under 720 ILCS 5/3-6), the allocation may:

• exclude older amounts from the earliest portion of the timeline,
• reduce included totals relative to an “include everything” approach,
• and shift allocation emphasis toward the most recent 5-year portion that falls within your chosen window logic.

If you used a different (longer) time horizon for comparison, included totals would generally increase because more historical amounts would remain in scope—though, again, for Illinois SOL-driven analysis, your final position should reflect the 5-year default unless you have separate claim-type-specific authority beyond what’s contained in your inputs.

6) Quick checklist for selecting the right setup

Use this checklist to ensure your DocketMath run matches an Illinois-default approach:

When you’re ready to move from setup to calculation, start with the calculator here: /tools/damages-allocation.

Next steps

Once you’ve selected DocketMath’s Damages Allocation tool and aligned it to the Illinois default limitations period, your next job is to make the output usable—internally, in a demand package, or in a damages model that you can revise.

1) Map your data to DocketMath inputs

Translate your records into the tool’s structure:

• If you have line items, group them into consistent categories or time slices.
• If you have a single lump sum per year, ensure your time slicing is consistent (for example, calendar years vs. rolling periods).
• If your damages are event-based, decide how you assign event values into months/periods for allocation.

This step matters because the tool will only allocate what you input—structured clarity reduces avoidable confusion later.

2) Run two passes if you need a reasonableness check

A practical workflow some teams use (for modeling clarity, not as a substitute for legal analysis) is:

• Pass A: allocate using the 5-year default SOL (Illinois: 720 ILCS 5/3-6)
• Pass B: allocate using a broader window (for internal comparison only)

Compare:

• how much total changes when the SOL filter is enforced,
• whether excluded amounts look “time-consistent” with your timeline definitions.

3) Export the allocation summary into a narrative-friendly structure

Even without providing legal advice, you can produce a damages output that’s easier to explain by including:

• included period (start through cutoff date),
• excluded period (what falls outside the 5-year window, if applicable),
• allocation totals by component,
• and subtotals by period (if you used time slices).

DocketMath helps keep those moving parts synchronized to the same assumptions—especially the SOL window.

4) Confirm the assumptions you used (and where they came from)

Because your jurisdiction input includes the general/default period (and no claim-specific sub-rules were identified), document this plainly in your internal notes:

• You applied the general/default 5-year SOL from 720 ILCS 5/3-6
• You did not apply claim-type-specific SOL exceptions because none were identified in the provided rule set

That reduces the risk of “rule drift” if the model gets reused or updated later.

5) Where to go in DocketMath next

If you’re building a complete docket or evidence timeline alongside your damages model, you may also want to review other DocketMath workflows for structuring dates and tracking events, then bring the aligned timeline back into damages allocation.

Start with the tool again at: /tools/damages-allocation. If you want additional context, you can also browse related resources via: Browse the blog.

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