Settlement Allocator Guide for Illinois

What this calculator does

Run this scenario in DocketMath using the Settlement Allocator calculator.

DocketMath’s Settlement Allocator helps you break a settlement payment into allocation categories so you can estimate how much of the total might be treated as covering different kinds of claims—using a simple, math-first approach.

In Illinois, one of the most common reasons people allocate settlement amounts is to understand how much time has passed since the underlying events and whether a claim type (or claim category) could still be within a filing window. This guide is built around the general/default Illinois statute of limitations (SOL) period for civil actions that fall under the catch-all framework.

The Illinois SOL baseline used in this guide

Illinois’ general/default civil SOL period is:

• 5 years under 720 ILCS 5/3-6
  Source (Illinois General Assembly): https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai

Important limitation: the jurisdiction data you provided states that no claim-type-specific sub-rule was found. So this article uses the general 5-year default period as the baseline, and does not attempt to apply different SOL rules for different underlying causes of action.

When to use it

Use DocketMath’s Settlement Allocator when you want a structured way to translate a settlement agreement into numbers you can organize for analysis, recordkeeping, and timeline checks.

Common situations include:

• You have a lump-sum settlement amount and need to model how it might be distributed across:

  • damages vs. non-damages components (e.g., fees, interest, or other negotiated components), or
  • categories you track for internal workflows and document support.
• You’re reviewing the settlement timing against a 5-year SOL baseline (general/default period) to confirm whether an item likely falls within the window.
• You need an auditable method for allocation assumptions—especially when multiple parties (or accounting teams) will rely on the same breakdown.
• You’re reconciling settlement language (“this portion is for X, this portion is for Y”) with a spreadsheet-based approach.

A quick way to decide whether to run it

Check the items below:

If you can’t identify components or agreed amounts, you can still use the calculator, but you’ll need to make and document reasonable assumptions.

Step-by-step example

Below is a realistic walkthrough showing how to use DocketMath’s Settlement Allocator in an Illinois-focused workflow.

Scenario

• Settlement agreement date: March 1, 2026
• Underlying incident date: March 1, 2021
• Total settlement payment: $120,000
• Agreement language (example allocation terms):

  • $90,000 for compensatory damages
  • $20,000 for attorney’s fees/costs
  • $10,000 for other negotiated amounts

Step 1: Confirm the SOL baseline you’re using

Under your provided Illinois jurisdiction data:

• General/default SOL period: 5 years
• Statutory reference: 720 ILCS 5/3-6
• Source: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai

Timeline check using the baseline:

• From March 1, 2021 to March 1, 2026 = 5 years
• Under the general 5-year default rule, this sits at the boundary.

Because your data does not provide claim-type-specific SOL sub-rules, the calculator/workflow should treat this as a baseline timing check, not a claim-specific determination.

Step 2: Decide your allocation categories

In DocketMath’s Settlement Allocator workflow, you typically enter:

• Total settlement amount
• Component amounts (or proportions)
• Category names you’re tracking (e.g., “Damages,” “Fees/Costs,” “Other”)

For this example:

• Damages: $90,000
• Fees/Costs: $20,000
• Other: $10,000

Step 3: Enter inputs into the calculator

Go to the tool first here:

• /tools/settlement-allocator

Then input:

• Total settlement: $120,000
• Damages: $90,000
• Fees/Costs: $20,000
• Other: $10,000

Most settlement allocators will either:

• validate that components sum to the total, or
• compute missing categories if you leave one blank, depending on how the tool is designed.

Step 4: Interpret the calculator output

You should expect outputs that include:

• Category totals (the same $90,000 / $20,000 / $10,000)
• Percent allocations, such as:

  • Damages: 90,000 / 120,000 = 75%
  • Fees/Costs: 20,000 / 120,000 = 16.67%
  • Other: 10,000 / 120,000 = 8.33%
• A consistency check that components equal the settlement total

Step 5: Run the timeline check using the SOL baseline

Now connect allocation work to timing analysis using the general SOL baseline (5 years, 720 ILCS 5/3-6):

• Incident date: March 1, 2021
• Assessment date: March 1, 2026
• Baseline SOL: 5 years

In a practical workflow, you can record:

• “Within 5-year baseline (general/default SOL period).”

Again, this does not confirm the SOL for every claim type; it only confirms whether the matter is in the ballpark for the general/default period used in this guide.

Common scenarios

Settlements rarely fit neatly into one allocation pattern. Here are frequent cases and how to approach them in a structured way with DocketMath.

1) The settlement is a lump sum with no internal breakdown

Inputs you’ll need:

• Total settlement amount (e.g., $200,000)
• Allocation method (proportions you choose)

How allocation changes:

• If you allocate 70/20/10 instead of 60/30/10, your category totals and percentages change even though the total remains $200,000.

Checklist:

2) Settlement agreement includes a clear damages vs. fees split

If the agreement already specifies amounts, you can enter them directly. This generally produces the most reliable outputs.

Example:

• Total: $80,000
• Damages: $60,000
• Fees/Costs: $15,000
• Other: $5,000

Changes you’ll observe:

• Percentages reflect the pre-set split.
• The sum-to-total validation typically passes without adjustments.

3) You’re comparing “same total, different allocations” for internal analysis

Sometimes you’re not disputing the total; you’re testing consequences of different component allocations.

Try running two passes:

• Allocation A: more damages, less other
• Allocation B: more other, less damages

Watch what changes:

• Category percentage mix
• Any downstream calculations tied to categories (e.g., reporting breakdowns)

4) Timing question: “Is this outside the SOL baseline?”

If your goal is timeline organization rather than claim-type specificity, use the general/default SOL baseline:

• 5 years under 720 ILCS 5/3-6

Inputs:

• Date of relevant event (e.g., incident date, claim accrual date as tracked in your file system)
• Date you’re assessing from

Output usage:

• Record a “within/outside 5-year baseline” flag for workflow triage.

5) Settlement paid in installments

If the settlement totals $150,000 but is paid in three checks, you have two practical choices for allocation math:

• Allocate based on agreement total (usually the cleanest for allocation categories)
• Record payment dates separately for payment tracking

The calculator is most straightforward when based on the total settlement amount.

Tips for accuracy

A few disciplined steps will make your settlement allocation output more defensible and easier to audit.

Use the tool consistently

• Enter the same total settlement amount across runs.
• Keep category definitions stable (e.g., “Damages” always means the same thing in your internal system).

Document your assumptions right next to the calculation

If your agreement doesn’t specify amounts:

• write the allocation rationale
• note the basis (e.g., damages estimates, demand breakdown, or negotiated proportions)

Validate totals before relying on outputs

At minimum, ensure:

Tie timelines to the Illinois general/default SOL

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado