What this calculator does

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

The DocketMath Public Records Fee Calculator (Michigan) helps you estimate the fee components you may be charged when requesting copies from Michigan public bodies. Instead of guessing whether a request will be expensive, the tool lets you enter request details (like number of pages and delivery format, including electronic vs. paper) to produce an estimated total you can plan around.

This guide is built to be practical:

• You control the inputs. Adjust pages, delivery format, and other request variables to see how the estimate changes.
• You get a single estimated total. Use it as a budgeting number, not a guarantee.
• You get planning support. Learn what to watch for and how to improve the reliability of your estimate.

If you want to run the estimate right away, use: /tools/public-records-fee.

Default context: timing (6-year lookback)

Sometimes public records requests involve questions like “how far back should I look?” Michigan has a general/default 6-year period referenced for limitations-period context in this guide:

• MCL § 767.24(1) (general/default six-year period)
• Source reference context: Michigan government information is hosted at https://www.michigan.gov

Important clarification for this guide: no claim-type-specific sub-rule was found, so the 6-year statement is presented as the general/default period for planning purposes in this article.

When to use it

Use the DocketMath public-records-fee calculator when you need a quick, structured way to estimate likely charges before you submit (or refine) a public records request.

Common reasons to use it:

• Budget planning: You’re requesting records that may span multiple dates or document types and want an estimate you can plan around.
• Comparing request formats: You want to see how choosing electronic copies vs paper copies could affect the estimated total.
• Narrowing scope: You’re deciding whether to request “all emails” for a period or a smaller subset and want to see how the page count changes the total.
• Preparing a cost-conscious request: You want a clear estimate you can use when asking the agency to prioritize or clarify scope.

A practical workflow looks like this:

1. Draft your request.
2. Estimate the pages you expect the agency to produce.
3. Use the calculator to refine assumptions until the estimate is manageable.
4. Submit or adjust—especially if the agency asks for narrowing/clarification.

Step-by-step example

Below is a concrete walk-through using a realistic Michigan-style planning approach. Because the calculator is designed for practical estimates, you’ll enter the request’s likely output characteristics (what the agency would ultimately produce), not every internal step that may occur during processing.

Example: “30-day emails, 60 pages, paper copies”

Imagine you’re requesting email printouts for a 30-day window. You estimate the agency will produce around 60 pages of responsive material in paper form.

Step 1: Estimate the output pages

Decide your estimate for how many pages the agency is likely to produce.

Checklist for this input:

Step 2: Choose delivery format assumptions

Select paper copies in your calculator inputs (as opposed to electronic copies).

Why this matters:

• Paper production often has a different cost profile than electronic delivery because the agency may need to generate and prepare physical copies.

Step 3: Apply the calculator

Run DocketMath using inputs like:

• Pages: 60
• Format: Paper

Step 4: Review the output estimate

The tool returns an estimated total fee.

Use it for planning decisions:

• If the estimate is too high: Narrow the date range (e.g., 30 days → 14 days), reduce the number of custodians/search terms, or request a narrower set of document types.
• If the estimate is manageable: Keep the scope and submit, then be ready to respond if the agency later asks you to clarify.

“What changes when I change inputs?” (quick sensitivity test)

Use this approach to learn which assumptions most affect your estimate.

Common scenarios

Real public records requests don’t always follow a perfectly simple pattern. Here are common situations where you’ll get more value from iterating on calculator inputs.

1) Broad requests that generate high page counts

Scenario: You request “all records” relating to a topic for a year.

What to do:

• Use the calculator to see how costs scale with estimated pages.
• Consider splitting by smaller date windows (e.g., quarterly) so scope—and cost planning—becomes more manageable.

Practical refinement ideas:

• Ask for specific document types (e.g., “final reports” rather than “all communications”).
• Limit by program/department/custodians where feasible.

2) Email requests with attachments (hidden volume)

Scenario: You’re requesting email threads, but attachments dramatically increase page count.

Why it matters:

• Attachments often dominate produced pages.
• One email thread can produce multiple documents once exported or printed.

Action:

• If you can, estimate based on produced pages rather than counting emails.
• For example: “Approximately 12 emails include PDFs averaging 4 pages each” → total attachment pages becomes part of your page estimate.

3) Electronic delivery requests

Scenario: You want the records in digital format.

How to use the calculator:

• Select electronic delivery assumptions so your estimate reflects reduced reproduction/printing effort.

Reassessment trigger:

• If you expect large files (e.g., CAD drawings, videos, large PDFs), “pages” may not map cleanly to file size. In those cases, revisit your assumptions and treat the estimate as a rough planning number.

4) Requests where you may adjust scope after initial results

Scenario: You submit a request, then the agency asks for clarification or provides an initial estimate.

How the calculator helps:

• Update your estimated pages based on the agency’s description of what’s responsive.
• Re-run the calculator with revised assumptions after narrowing scope.

5) Backdating / lookback questions and the 6-year default context

Scenario: You’re deciding how far back to request records.

This guide uses a general/default six-year period for timing framing:

• MCL § 767.24(1) (general/default six-year period)
• No claim-type-specific sub-rule was found in the research behind this guide, so the six-year statement is presented as general/default.

Tips for accuracy

A fee estimate is only as good as the assumptions you enter. These tips help you improve reliability without needing legal analysis.

1) Build your page estimate using a repeatable method

Pick one method and stick to it:

• Sampling: Review 5–10 representative items and estimate average pages.
• Historical precedent: Use a prior response from the same agency to guide your estimate.
• Document-type mapping: Estimate based on typical formats (e.g., meeting agendas are often a few pages; minutes might be longer).

Convert your approach into a single input:

• **Total expected pages = (average pages per item) × (expected number of items)

2) Separate “search volume” from “production volume”

Many requests generate lots of internal work, but what drives the calculator estimate is produced output, not the time spent searching.

Practical checklist:

3) Use consistent assumptions about format

Be consistent:

• If you estimate paper output, match the calculator’s paper format.
• If you estimate electronic output, use electronic format.

Avoid mixing:

• Estimating “60 paper pages” but selecting electronic assumptions can understate the mismatch between what you think will be produced and how the agency exports or copies.

4) Re-run the calculator after scope changes

Update the estimate immediately when you change:

• date range
• number of custodians
• search terms
• record categories
• delivery format

Quick loop:

• Change one scope element → rerun → compare totals.

5) Use the calculator number to structure your request

If you’re trying to control cost while still getting useful records, consider a structured request approach:

• Ask for prioritized categories (e.g., “first 30 days” then refine after response).
• Request the most essential items first if the agency is likely to seek clarification.

6) Timing awareness: the 6-year default context

When your request planning includes “how far back,” remember:

• Michigan general/default planning anchor in this guide: **6 years

Related reading

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