Public Records Fee Calculator Guide for Minnesota

What this calculator does

DocketMath’s Public Records Fee Calculator (Minnesota) helps you estimate the likely fees involved in obtaining copies of public records in Minnesota. The goal is practical: you enter key details (like the type of request, the amount of material, and any copy/format you want), and the tool produces an itemized fee estimate you can use when planning and budgeting.

This guide explains:

• Which inputs matter (and how they affect the output)
• How to run the calculation using DocketMath
• Common Minnesota scenarios that change how fees tend to look
• How to sanity-check the result before you submit your request

When to use it

Use DocketMath’s calculator when you’re preparing a Minnesota public records request and you want a quick, defensible estimate of what you might be charged.

It’s especially useful when:

• You’re requesting multiple pages or multiple documents
• You want records in a specific format (for example, electronic copies versus printed pages)
• You’re asking for a large media volume (e.g., many emails or attachments)
• You’re trying to decide whether to narrow the scope of a request to reduce cost

Don’t confuse fee planning with timing rules

The calculator focuses on fees, not how long you have to bring a claim. Still, Minnesota law does establish a general civil statute of limitations (SOL) that some requesters care about in planning how far back they might need records.

Minnesota’s general SOL period is 3 years, and it’s codified at Minnesota Statutes § 628.26. The general SOL reference you provided indicates the default period; no claim-type-specific sub-rule was found. That means:

• Treat 3 years as the general/default lookback for “time window” planning, not a special rule tailored to a particular type of case.

For reference on criminal court record timelines, one source provided notes criminal record context and includes a link that discusses “general/default period” framing:

• https://minnesotacourtrecords.us/criminal-court-records/gross-misdemeanor/

Step-by-step example

Below is a concrete walkthrough showing how a requester might run the calculation using the DocketMath tool.

Example request (illustrative)

Suppose you want:

• 250 pages of records
• in printed form (you will receive copies as pages)
• you expect the agency may need a mix of scanning/copying for a portion

Now run the calculator:

1. Open the DocketMath tool: **/tools/public-records-fee
2. Enter the estimated page count

   • Example: 250
3. Select the delivery/copy format that best matches what you’re asking for

   • Example: printed pages
4. If the calculator asks for an estimated processing component (some versions include toggles for scanning or compilation effort), set it based on your best expectation

   • Example: some scanning/compilation
5. Review the itemized output
6. Save or screenshot the estimate for your request planning

What the output typically looks like

A good fee calculator estimate usually breaks into:

• Copying cost (driven primarily by page count)
• Processing cost (driven by whether documents require scanning, compiling, or formatting)
• Delivery/medium cost (driven by whether you want paper, electronic files, or a special medium)

In this example, your estimate would increase mostly due to:

• the 250-page quantity, and
• any flag you set for scanning/formatting.

If you later decide to narrow the request (e.g., from 250 pages to 100 pages), the output should drop materially because the copying component scales with page count.

Timeline planning side note (how SOL intersects with scope)

If you are trying to decide “how far back” to request records for planning purposes, the general SOL reference you provided is 3 years under Minnesota Statutes § 628.26 (general/default period). With no claim-type-specific sub-rule found in your materials:

• using a 3-year lookback is the safest default planning assumption.

Common scenarios

Minnesota public record requests come in many shapes. The fee estimate often changes based on the size of the request, the format you want, and whether there’s significant processing.

Scenario checklist (choose what matches your request)

Below are common scenarios and how they tend to affect the calculator’s output.

1) Low-volume, straightforward page requests

If your request is, for example, 30–60 pages and the agency can reproduce them with minimal processing, your estimate typically stays closer to the copying portion. Processing flags (if you can control them in the calculator) should be kept conservative unless you know scanning/formatting is involved.

2) Bulk document pulls (hundreds to thousands of pages)

Requests in the 200–1,000+ page range usually produce estimates dominated by the page-driven component. Even small changes can matter:

• narrowing your time window
• narrowing the list of custodians/units
• requesting fewer categories of records

3) Electronic records with formatting or compilation needs

Some records are “electronic,” but not automatically delivered in a ready-to-use dataset. If you need:

• conversion (e.g., native format → PDF/exports)
• compilation of many attachments
• organization into a specific structure

…your estimate may rise due to processing/formatting effort.

4) Requests that span multiple systems

If records live across:

• email + shared drives
• databases
• separate departmental storage

…agencies often need more time to locate, review, and assemble responsive material. In the calculator, that may show up as additional processing toggles or higher estimated effort.

5) Scope planning with the 3-year general SOL window

When requesters are planning “how far back,” a common default is a 3-year lookback based on Minnesota Statutes § 628.26 (general/default period). Since your materials indicate no claim-type-specific sub-rule was found, treat 3 years as the planning baseline rather than a precision rule for every possible legal situation.

Tips for accuracy

Fee estimates are only as good as the inputs. Use these tips to make your DocketMath calculation more accurate.

1) Start with a realistic page count

If you don’t know the final page count, avoid guessing wildly. Better approaches:

• count pages from a sample batch
• estimate based on typical document length
• use a range (run the calculator twice: e.g., 150 pages and 250 pages)

2) Reflect actual work you expect the agency to do

The largest estimation errors usually come from underestimating processing, not copying. Consider:

• Will documents need scanning?
• Will records need conversion to a requested format?
• Is compilation required?

If the calculator lets you select processing categories, match them to your best description of what you’re requesting.

3) Narrowing scope can reduce cost more than you expect

A request that is broad in topic but narrow in time might cost less than one that is narrow in topic but broad in time (depending on how records are generated and stored). If fees look high:

• reduce the time window (still using the 3-year general planning baseline if you’re doing a lookback estimate)
• list fewer record categories
• request a smaller set of custodians or locations

4) Use the 3-year general SOL period correctly (default only)

For timing window planning, the provided general rule is:

• General SOL Period: 3 years
• General Statute: Minnesota Statutes § 628.26
• Your materials specify this is the general/default period and no claim-type-specific sub-rule was found.

So if you use a lookback window for planning, it should be understood as a default planning assumption, not a specialized limitation for every matter.

5) Keep an audit trail of your assumptions

Before you send a request, save:

• the DocketMath estimate
• your entered page count and settings
• any assumptions (e.g., “estimated scanning required”)

This helps if the agency’s actual estimated fee differs later.

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