How to run Wage Backpay in DocketMath for Illinois

Step-by-step

Run this scenario in DocketMath using the Wage Backpay calculator.

This guide shows you how to run Wage Backpay calculations in DocketMath for Illinois (US-IL) using jurisdiction-aware rules. The goal is to help you produce an auditable backpay number you can attach to internal case materials, while keeping the approach aligned with Illinois’ general statute of limitations.

1) Open the Wage Backpay calculator

1. Go to the tool: /tools/wage-backpay
2. Select (or confirm) jurisdiction is set to Illinois (US-IL).

If your interface asks for additional jurisdiction inputs, keep the setting aligned with US-IL so the calculator applies the correct default limits.

2) Enter the key dates (these drive the lookback window)

In Illinois, the general limitations period used for wage backpay calculations in DocketMath is:

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

To make the calculator compute a lookback window, you’ll typically provide:

• Start date of the relevant wage period
• End date (or “as of” date)

What to expect in DocketMath output:

• If your wage period starts more than 5 years before the end/as-of date, DocketMath will generally limit the counted portion to the most recent 5-year window.
• If your wage period starts within the 5-year window, the full period may be included.

Important jurisdiction note (per the brief): No claim-type-specific sub-rule was found for this workflow’s instruction set. So, the tool should apply the default/general 5-year period under 720 ILCS 5/3-6 unless your inputs or configuration indicate otherwise.

3) Add your wage inputs (hourly or salaried, plus work pattern)

Next, enter the wage details that DocketMath uses to compute wage totals. Common inputs include:

• Pay rate (e.g., hourly rate)
• Hours per week (or days worked)
• Pay frequency (if requested)
• Any wage changes (if your interface supports tiered rates)

If you have multiple wage rates during the period, enter them as separate segments if DocketMath supports that structure. If segmentation isn’t supported, use a single blended rate and document how you derived it.

How outputs change:

• Higher hourly rate or hours/week increases gross wage backpay.
• Splitting the period into segments can materially change the result if rates changed during the relevant window.

4) Configure any deductions/offsets (if available in your workflow)

Some backpay workflows account for offsets such as:

• mitigation earnings (if applicable),
• reimbursements,
• or other wage adjustments,

depending on what DocketMath fields you have and what you intend to model.

Because this workflow guide is focused on the Illinois SOL rule and the general backpay calculation flow, treat these inputs as modeling parameters—enter only what you’re ready to defend with documentation and internal support.

5) Review the calculated results

After you run the calculation, DocketMath should output:

• Total backpay amount (wage portion)
• The effective counted date range after applying jurisdiction-aware rules (not always shown as a labeled “range,” but you should be able to verify which portion is included)
• Any breakdowns by year/period (when supported)

Use the reviewed date window to verify you’re not unintentionally calculating outside the 5-year default.

6) Export or record the audit trail

For litigation-adjacent workflows, you’ll typically want:

• a screenshot or PDF export,
• the input values recorded in your notes,
• confirmation of:

  • the jurisdiction setting (US-IL), and
  • the default 5-year SOL basis under 720 ILCS 5/3-6.

This helps later when someone asks, “Where did the dates come from?” or “Why did the earlier portion drop out of the calculation?”

Common pitfalls

Wage backpay calculations often fail for reasons unrelated to math. Here are the issues that most commonly distort outcomes when running Illinois calculations in /tools/wage-backpay.

The calculator’s lookback window is tied to your “as-of” or end date inputs. Even a small shift can change which portions fall inside the 5-year window.

For this Illinois workflow, DocketMath should apply the general/default period because no claim-type-specific sub-rule was found for this instruction set. The applicable general rule is 5 years under 720 ILCS 5/3-6.
If your matter requires a different limitations analysis, you’ll need a different modeling approach.

Wage increases, reduced hours, or rate changes during the period can significantly alter totals. Splitting segments improves accuracy.

Decide whether your inputs represent actual compensation under the employment contract/practice you’re modeling. Inconsistent inputs can create backpay estimates that don’t reflect your evidence.

In multi-tool or multi-tab environments, it’s easy to accidentally keep a prior jurisdiction selection. Confirm US-IL every time before running.

Try it

To run a quick test, use DocketMath’s /tools/wage-backpay calculator:

1. Set jurisdiction to Illinois (US-IL).
2. Choose a conservative example so you can easily verify the date window:

   • Wage period end/as-of date: today (or a date you pick)
   • Wage start date: more than 5 years earlier (to test the truncation)
3. Enter a basic wage scenario:

   • Hourly rate: e.g., $20/hour
   • Hours/week: e.g., 40
4. Run the calculation and confirm:

   • The counted period aligns with the most recent 5 years governed by 720 ILCS 5/3-6.
   • The total backpay reflects only that included portion.

If your output doesn’t reflect the expected 5-year window, re-check:

• your end/as-of date,
• your start date,
• and the jurisdiction selection (US-IL).

Related reading

• Wage & Backpay Calculator Guide for Alabama
• Wage & Backpay Calculator Guide for Arizona
• Wage & Backpay Calculator Guide for Colorado