Public Records Fee Calculator Guide for Illinois

What this calculator does

Run this scenario in DocketMath using the Public Records Fee calculator.

DocketMath’s Public Records Fee Calculator (jurisdiction: Illinois) helps you estimate the likely fees you may be asked to pay when requesting public records. It’s designed for day-to-day use and focuses on the fee components that commonly appear in Illinois public-records processing—so you can budget before you submit.

This guide explains how to use the calculator effectively, what inputs matter, and how the output changes as you adjust assumptions.

Key Illinois scope points:

• The tool is built around Illinois’s general public-records fee framework.
• For record-retention timing and related planning, this guide also notes the general statute of limitations (SOL) period: 5 years under 720 ILCS 5/3-6.

  • Source: https://ilga.gov/ftp/Public%20Acts/101/101-0130.htm?utm_source=openai
• Clear default SOL rule: The general/default SOL period is 5 years. No claim-type-specific sub-rule was found in the provided materials, so this guide treats 5 years as the baseline.

If you want to start immediately, use: /tools/public-records-fee.

When to use it

Use the calculator when you’re preparing a public-records request and want to anticipate costs before you submit.

It’s especially useful when your request details are likely to affect fees, such as:

• Page/output size (how many pages or equivalents the request will produce)
• Delivery format (electronic vs. paper-like outputs)
• Attachments or exports (where file content can translate into many output units)
• Search scope (custodians, date ranges, and systems)

Common moments to run the numbers:

• You know (or can estimate) the number of pages you’re requesting.
• You’re requesting electronic records but want to understand how costs may change versus paper.
• Your request includes media or large data exports, where cost can scale with output size.
• You’re considering narrowing your request to reduce fees (e.g., tighter date ranges, fewer custodians, specific file types).
• You’re planning follow-up requests and want more consistent budgeting across iterations.

Because Illinois fee handling depends on how records are described and delivered, the calculator works best when your inputs reflect how the agency is likely to compile and produce what you’re asking for.

Also, if you’re doing broader timeline planning (for example, enforcement or dispute strategy), the general SOL period is 5 years under 720 ILCS 5/3-6 (baseline rule). That matters for “how long you have,” but it’s separate from fee calculation.

Step-by-step example

Below is a concrete example you can mirror. This example assumes you’re requesting records in Illinois and that the agency will provide a mix of paper-like pages and/or standard electronic outputs.

Scenario: “Contract-related communications” request

Imagine you want:

• A specific set of emails and attachments
• From January 1, 2022 through December 31, 2022
• For one department
• Delivered as PDFs and/or exported files

You decide to run the fee estimate before submitting.

Step 1: Open the tool and choose the calculator flow

Go to /tools/public-records-fee and enter your request assumptions into the fee categories the tool supports.

Because the tool’s UI may label inputs slightly differently, focus on supplying the best estimates you can for:

• Expected page count (or output units)
• Expected format (paper/PDF/export)
• Any search/retrieval time assumptions the tool asks you to model
• Any optional parameters that reflect what you’re really asking the agency to produce

Step 2: Estimate pages (the biggest lever)

Your biggest driver is often page/output size.

A realistic estimation approach for this scenario might look like:

• Emails in the date range: 120
• Typical attachment frequency: 25%
• Average pages per attachment: 6 pages
• Plus the email bodies converted into pages (e.g., about 1 page per email)

One way to compute:

• Email bodies: ~120 pages
• Attachments: 120 × 25% × 6 = 180 pages
• Total estimated pages: 300 pages

Enter 300 as the expected output size (or the closest equivalent your tool accepts).

Step 3: Set the delivery format assumption

If the tool supports it, choose electronic/PDF delivery instead of paper when you expect the agency to produce PDFs.

How output can change:

• If the calculator distinguishes formatting/conversion or reproduction assumptions, selecting electronic delivery may reduce certain components compared to paper.
• If the calculator treats outputs more uniformly, the difference may be smaller—but it’s still worth matching what you’ll actually request.

Step 4: Add search effort/time assumptions (if prompted)

If you expect the agency will search a limited set of custodians and a narrow date range, model a lower search effort than you would for multi-year, multi-department requests.

In this example:

• One department
• One year
• Defined keywords or identifiable threads

If the tool offers a “search effort” selector, pick something like moderate. If it asks for numeric inputs, estimate based on how many systems and how many custodians are likely involved.

Step 5: Run the calculation and review line items

After you compute, review the fee breakdown:

• Identify which category is the largest driver (often page/output-based).
• Check whether search effort is a major contributor.
• Revisit your page assumptions if the total feels unexpectedly high or low.

Step 6: Use the calculator to test narrowing strategies

Now adjust your inputs to see how the estimate changes.

Example narrowing:

• Reduce the date range to Q3 2022 only
• Limit to fewer custodians or a smaller scope of keywords
• Ask for records in a format you can accept that the tool models accurately

If your estimated output drops from 300 pages to 160 pages, your total fee estimate should drop meaningfully—especially when the page/output component dominates.

Step 7: Tie time planning to the Illinois SOL baseline (context only)

If your request connects to a longer-term issue (for example, potential claims), remember:

• Illinois general/default SOL period is 5 years under 720 ILCS 5/3-6.
• No claim-type-specific sub-rule was provided in the materials, so treat 5 years as the baseline.

Common scenarios

People use public records fee estimates in different ways. Below are practical scenarios and how to think about inputs so the calculator output reflects what’s likely to happen.

Scenario A: “High page count” paper-heavy requests

Typical facts

• Broad “all documents” request across a long date range
• Scanned documents
• High likelihood that the response converts into many pages

Calculator input focus

• Start with a realistic page/output estimate.
• Expect page/output to be the dominant driver.

Optimization ideas

• Narrow the date range (e.g., 2 years → 6 months)
• Tie requests to events, identifiers, or specific milestones
• Limit to specific record types (e.g., only “incident reports”)

Scenario B: Electronic records with attachments

Typical facts

• Emails + attachments
• Delivered as PDFs or exports
• Some emails include multi-page attachments

Calculator input focus

• Page/output still matters a lot—attachments can “inflate” results.
• Delivery format assumptions matter if the tool distinguishes output types.

Optimization ideas

• Specify the delivery format you can accept (PDF vs native export), consistent with your tool selections
• Define keywords precisely if you’re using search terms
• Provide custodians or systems to narrow search scope

Scenario C: Broad search effort (many custodians/systems)

Typical facts

• “All communications” across multiple departments
• Long time range
• Many possible data sources

Calculator input focus

• Search/retrieval assumptions can strongly influence total cost if modeled by the tool.
• Narrowing custodians can reduce search effort.

Optimization ideas

• Identify custodians by role (or by name if you know them)
• Define data sources (e.g., “Finance system” vs all shared drives)
• Shorten the date range and rerun the calculator

Scenario D: Planning for escalation or disputes (timeline context)

Even though the tool is for fee estimation, some people pair fee budgeting with timeline awareness.

**Illinois baseline time context (from provided materials)

• 5-year general SOL period under 720 ILCS 5/3-6
• No claim-type-specific sub-rule was provided in the materials, so treat 5 years as the general/default baseline

Tips for accuracy

The biggest difference between a helpful estimate and a misleading one is input quality. Use these practices to improve accuracy.

1) Estimate pages using a sampling approach

If possible:

• Review a small sample or pull a quick preview
• Count pages for that sample
• Scale up based on the full scope

Even a rough sample is usually better than guessing the total.

2) Treat date ranges like multipliers

A smaller date range often reduces:

• Number of records
• Search effort
• Total pages/output size

Try running multiple scenarios:

• 1 month vs 3 months vs 12 months

You may see near-linear changes at first, with steeper jumps when attachment-heavy periods enter the range.

3) Be consistent about delivery format

If you’re willing to accept multiple formats, select the option that matches what you will actually request.

In fee calculators, format selection can change:

• reproduction/conversion assumptions
• output units
• how the tool interprets what you’ll receive

4) Don’t forget attachments

A common misestimation pattern is focusing on email bodies and ignoring attachments’ page impact

Related reading

• Public Records Fee Calculator Guide for Alabama
• Public Records Fee Calculator Guide for Arizona
• Public Records Fee Calculator Guide for Colorado