Deadline Calculator Guide for Illinois

7 min read

Published April 8, 2026 • By DocketMath Team

What this calculator does

Run this scenario in DocketMath using the Deadline calculator.

DocketMath’s Deadline Calculator (US-IL) helps you compute the end date of a 5-year limitations period in Illinois using a straightforward timeline method. For Illinois, this guide focuses on the general/default statute of limitations (SOL) period of 5 years, citing:

Key constraint (important):

Note: No claim-type-specific sub-rule was found for this calculator guide. The content below treats 720 ILCS 5/3-6’s general 5-year period as the default rather than tailoring for specialized causes of action.

In practice, you’ll enter dates related to the start of the limitations clock (the “trigger”), then the tool calculates the deadline date—using day-level date arithmetic.

What you’ll typically manage with it

  • Pick the SOL start date (the “trigger date” you’re using for your scenario)
  • Apply a 5-year duration
  • Get a calculated deadline date you can copy into a case checklist

What you should not assume

This calculator guide does not replace case-specific legal analysis. Limitations law can involve exceptions, accrual nuances, tolling, or statutory special rules. Use DocketMath to structure your own timeline, then verify the inputs against the underlying facts and procedural posture.

If you want to run the calculation, use: /tools/deadline

When to use it

Use DocketMath’s Deadline Calculator for Illinois when you need a quick, auditable deadline estimate tied to the general 5-year SOL in 720 ILCS 5/3-6.

Good times to run the calculation

  • You have a known event date that you believe starts the clock (your “trigger”)
  • You’re preparing an internal checklist and want a single deadline date to track
  • You’re comparing two potential trigger dates to see how much the deadline shifts
  • You need to standardize deadlines across a team using the same 5-year rule

Inputs you’ll generally decide before clicking “calculate”

To get a useful output, you’ll usually define:

  • SOL start date (trigger/accrual date you’re using)
  • Duration rule: 5 years under 720 ILCS 5/3-6
  • Whether the computed date should be treated as the “last day” for filing purposes in your workflow

If you’re unsure which date should start the clock, run two calculations with competing trigger dates and see which one produces the more conservative deadline—then reconcile with the facts.

Warning: Limitations periods can be affected by tolling, special accrual rules, or statutory exceptions. Treat DocketMath’s output as a timeline calculation based on the general 5-year rule, not as a guaranteed filing deadline.

Step-by-step example

Below is a concrete walkthrough showing how changing inputs changes the output. This example assumes the general 5-year SOL applies under 720 ILCS 5/3-6.

Scenario assumptions (for illustration)

  • You identify an event you believe is the SOL start (trigger) date
  • You want the end of the 5-year period using calendar arithmetic

Example timeline

  • SOL start date (trigger): March 15, 2021
  • General SOL duration: 5 years (per 720 ILCS 5/3-6)
  • Computed deadline: the last day in the calculated 5-year window

How to compute the date (with day-level precision)

  1. Start counting from the SOL start date: March 15, 2021
  2. Add 5 years
    • March 15, 2021 + 5 years = March 15, 2026
  3. The tool will reflect the result as the deadline date based on its date arithmetic rules.

What you’d enter in DocketMath

  • Jurisdiction: Illinois (US-IL)
  • Calculator: Deadline Calculator
  • SOL rule: General 5-year period
  • SOL start date: 03/15/2021

Expected output

  • Deadline date: 03/15/2026 (computed for the general 5-year period)

Quick sanity check (visual)

ItemDate
SOL start03/15/2021
1-year mark03/15/2022
3-year mark03/15/2024
5-year mark / deadline03/15/2026

Common scenarios

You’ll see deadline calculations vary mostly due to what you choose as the trigger date and how your workflow treats the “last day.” Here are common ways teams use DocketMath with Illinois’s general 5-year rule.

1) Trigger date is a single known event

Inputs

  • One clear event date (e.g., an injury date, an alleged wrongful act date, or another “trigger” date you’re using)

Effect

  • Deadline shifts linearly: move the trigger by 10 days → deadline typically moves by 10 days.

Example pattern:

  • Trigger: 01/10/2022 → Deadline: 01/10/2027
  • Trigger: 01/20/2022 → Deadline: 01/20/2027

2) You have competing trigger dates

When facts suggest multiple possible accrual points, a practical workflow is:

  • Run calculation A using trigger date #1
  • Run calculation B using trigger date #2
  • Use the earlier deadline as a conservative target for internal tracking

Checklist:

Pitfall: If you calculate from the later trigger date and that trigger is wrong, the missed deadline risk increases. Using both triggers helps prevent this operational error.

3) Leap years and end-of-day confusion

Date math across leap years is usually straightforward when done by calendar date arithmetic, but teams sometimes misinterpret how the tool handles exact dates.

Practical tip:

  • Use consistent formats (MM/DD/YYYY)
  • Confirm you’re using the correct calendar day, not an approximate period (e.g., “around March”)

Example:

  • Trigger: 02/29/2020
  • Add 5 years → depends on calendar arithmetic; many systems land on 02/28/2025 or 03/01/2025 depending on how they treat non-existent dates. DocketMath’s output will follow its date rules—double-check for accuracy in leap-year edge cases.

4) Internal deadline vs. filing deadline

Teams often track an “internal deadline” earlier than the computed SOL expiration date to allow time for review and filing steps.

A common operational approach:

  • Compute the SOL expiration date (from the tool)
  • Set an internal filing target (e.g., 7–30 days earlier)

This avoids crunch scenarios such as:

  • missing supporting documentation
  • late approvals
  • administrative filing delays

Tips for accuracy

You can improve reliability quickly by tightening inputs and documenting assumptions.

Use consistent date formats

  • Prefer MM/DD/YYYY input formatting
  • Avoid ambiguous entries like “3/5/21” (could be March 5 or May 3)

Treat the 5-year rule as the default—not a universal rule

For Illinois, this guide’s calculator logic is anchored in:

  • 720 ILCS 5/3-6 (general SOL period of 5 years)

Because no claim-type-specific sub-rule was identified for this guide, the general 5-year period is the only rule being applied here.

Note: The general 5-year SOL under 720 ILCS 5/3-6 is your baseline in this guide. If your situation involves a different statutory scheme or an exception, your correct deadline may not equal “trigger date + 5 years.”

Run “what if” calculations

When you aren’t 100% sure about the trigger date:

Record the assumptions alongside the output

For auditability and team alignment, keep a small record:

  • Trigger date used
  • Rule applied: general 5-year period under 720 ILCS 5/3-6
  • Output deadline date

That way, if someone challenges the trigger, the calculation history is available.

Verify the timeline before calendaring

Before you enter anything into a case management system:

  • Confirm the output date matches the intended “last day” concept in your workflow
  • If your workflow requires filings to be submitted by end-of-business-day, align the deadline accordingly (some teams use a same-day cutoff and move earlier)

Related reading