What this calculator does

DocketMath’s Public Records Fee Calculator helps you estimate the timing and likely fee components you may encounter when requesting records under Indiana public records law. The tool is designed for planning: it lets you model typical cost drivers like search time, copy/duplication charges, and other service-related charges that a records provider may assess.

This guide focuses on Indiana (US-IN) and uses the law’s general/default retention timeline for record consideration:

• General default period (Indiana): 5 years
• General statute cited: Indiana Code § 35-41-4-2 (source: Justia)

Because this guide is meant to be practical (not legal advice), treat the calculator as a planning estimator, not a guarantee of what any agency will charge in a specific request.

If you’re budgeting for a request, the calculator can help you answer questions like:

• “How does my requested date range affect fees?”
• “If I narrow to a specific incident window, will the estimate drop?”
• “What happens if I need electronic copies instead of paper?”

When to use it

Use the DocketMath calculator when you’re preparing an Indiana public records request and you want a defensible estimate before you submit. It’s especially useful in these situations:

• You’re requesting records for a defined time window
  The tool can model different ranges—e.g., 30 days vs. 2 years—so you can see how scope affects estimated work and duplication costs.
• You want to sanity-check a provider’s estimate
  If an agency later quotes a cost figure, your pre-submission estimate helps you understand whether the amount tracks the size of what you asked for.
• You’re planning multiple requests
  Instead of sending separate requests without a budget, you can compare estimates side-by-side based on scope.
• You’re requesting records that are likely to require staff time
  Search and review effort is often the main driver. The calculator helps you factor in those inputs consistently.

Checklist for best results:

Step-by-step example

Below is an example walkthrough showing how to use DocketMath’s public-records-fee tool logic for Indiana, aligned with the general/default 5-year period reflected in Indiana Code § 35-41-4-2.

Scenario

You’re requesting incident-related records from an Indiana county agency for:

• Time window requested: January 1, 2022 to December 31, 2022
• Delivery format: electronic copies
• Expected volume: roughly 120 pages total (or comparable electronic equivalents)

Step 1: Open the tool

Go to the DocketMath tool here: **/tools/public-records-fee

Step 2: Confirm the baseline date consideration

The calculator’s approach assumes the general/default period is 5 years, using the baseline reflected in Indiana Code § 35-41-4-2 (5-year general/default period). In other words:

• If you request a range within the last 5 years, the calculator treats it as within the general baseline.
• If you request a range beyond 5 years, the tool’s estimation is limited by the baseline approach—meaning you may see outputs that don’t scale linearly past that 5-year window.

Step 3: Enter your request scope inputs

Common inputs you’ll typically model in the tool include:

• Start date: 01/01/2022
• End date: 12/31/2022
• Search scope: “All items matching my criteria in that date range” (modeled as broad within that period)
• Estimated pages/documents: 120
• Format: electronic (often lower duplication effort than paper)

Step 4: Review how changes affect the estimate

Now try a “what if” adjustment to see why the calculator is useful:

Change A: Narrow the date window

• Original: 12 months (Jan 1–Dec 31, 2022)
• Revised: 2 months (e.g., Nov 1–Dec 31, 2022)

Expected effect: estimated staff work and duplication scope typically decreases when the date window narrows.

Change B: Switch to paper delivery

• Original: electronic
• Revised: paper copies

Expected effect: estimated duplication/printing effort can increase for paper, which may raise the total estimate.

Step 5: Interpret the output carefully

Your output is best read as:

• A planning estimate for the components you modeled
• A sensitivity indicator (how much total cost might move if your scope or format changes)

Common scenarios

Not every Indiana request looks the same. Here are recurring patterns and how the fee estimator typically reacts to each.

1) Short window, narrow criteria (often lowest estimates)

Request pattern

• Date range: 1–4 weeks
• Criteria: specific event type or a known incident number
• Format: electronic

Calculator impact

• Lower estimated search footprint (fewer days/items)
• Duplication estimate smaller if pages are limited

2) Multi-month window with broad criteria (search-heavy)

Request pattern

• Date range: 6–18 months
• Criteria: “all records relating to …” with minimal identifiers
• Format: electronic or mixed

Calculator impact

• Larger scope across the timeline
• Potential increase in estimated staff time and review effort

3) “All reports” requests (volume-driven)

Request pattern

• Date range: up to the baseline 5-year general/default period
• Criteria: recurring reports category (e.g., monthly logs)
• Format: paper

Calculator impact

• Pages/documents become the dominant variable
• Paper conversion can add duplication cost

4) Requesting beyond the 5-year baseline

Request pattern

• Date range: 5+ years (e.g., 10-year span)
• Criteria: broad
• Format: electronic

Calculator impact

• Because this guide uses the general/default 5-year period reflected in Indiana Code § 35-41-4-2, the tool’s estimate may not increase proportionally beyond 5 years based on that baseline approach.
• This is a practical modeling limitation: agencies can treat older records differently depending on retention and system indexing.

5) Mixed-format request (electronic + paper)

Request pattern

• You want electronic copies for efficiency, plus paper for a subset

Calculator impact

• Model it as two delivery requirements.
• Expect the estimate to reflect duplication differences.

Quick reference table: inputs that move the estimate most

Tips for accuracy

To get the most reliable estimate from DocketMath’s public-records-fee tool for Indiana, focus on precision in your modeled scope.

1) Use the correct baseline period

This guide applies the general/default period of 5 years using Indiana Code § 35-41-4-2.

• Keep your modeled date range consistent with that baseline where possible.
• If you request older records, consider whether you can reduce scope by using event identifiers (incident number, case number, names/dates, locations).

2) Translate your request into measurable scope

If you can, convert vague language into estimable units:

• “All emails” → estimate number of email threads or folders
• “All reports” → estimate number of report entries per month
• “Body-worn camera” → estimate clips (or length if known)

3) Model format decisions early

If you need electronic records to review efficiently, request electronic copies and specify delivery. Then, only request paper for what you truly need.

In the tool:

• Choose electronic when appropriate
• Separate paper-only subsets to avoid inflating the base duplication estimate

4) Re-run the tool after narrowing

A common workflow that improves accuracy:

1. Run your initial estimate with a broader scope.
2. Identify high-cost drivers (usually date range + volume).
3. Narrow the window or add identifiers.
4. Re-run and compare.

This creates an audit trail of why your request scope is more targeted—and helps you manage expectations before you submit.

5) Align expectations with likely agency workflow

Some requests are “search-heavy,” even if they’re “small” in pages. If your criteria require review for responsiveness, you may see cost differences driven by staff time rather than duplication alone.

Related reading

• Browse the blog
• Indiana Code § 35-41-4-2 (Justia)

Related reading

• Public Records Fee Calculator Guide for Alabama — Complete guide
• Public Records Fee Calculator Guide for Arizona — Complete guide
• Public Records Fee Calculator Guide for California — Complete guide