Public Records Fee Calculator Guide for Colorado

8 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

What this calculator does

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

DocketMath’s Public Records Fee Calculator (Colorado) helps you estimate public-records production costs under Colorado law so you can budget requests and understand what a custodian may reasonably charge. The tool is designed for the most common expense categories that appear in public-records responses—especially costs tied to labor, search, review, and duplication.

At a high level, the calculator can help you translate request details into an estimated total by letting you adjust inputs such as:

Estimated search time (e.g., how long it takes to locate responsive records)
Estimated review time (e.g., time spent redacting or determining exemptions)
Duplication method (paper copies, electronic export, scanning, etc.)
Number of pages or files
Whether items are already electronic (which can reduce duplication time)

Because fee calculations depend heavily on request scope and record format, your estimate can change dramatically if you adjust just one input—particularly pages, format, and labor time.

Note: This guide is for planning and estimation. It doesn’t replace a custodian’s final fee assessment or your ability to challenge a fee determination through the statutory process.

When to use it

Use this calculator when you’re preparing a public-records request in Colorado and want a practical cost preview before you submit (or after you receive a cost estimate). It’s most useful in situations like:

You’re sending a targeted request (e.g., emails from a specific date range, incident reports, or a particular dataset) and can reasonably estimate search/review effort.
You’re expecting redactions (because many records require exemption review). If you anticipate redaction, consider adding review time rather than only duplication.
You’re converting formats (e.g., “provide in CSV” or “scan paper records”). Duplication method can matter as much as page count.
You’re comparing multiple request versions (e.g., narrower date range vs. broader scope). Different inputs produce different fee implications.
You’re preparing a fee rebuttal after receiving a request response. While this isn’t legal advice, having a baseline estimate helps you spot when an amount appears disproportionate to the scope you requested.

When not to rely on an estimate:

If your request scope is vague enough that “responsive records” could include many different systems, the actual search effort may be impossible to forecast accurately.
If records exist primarily in a form that requires significant technical work (custom exports, complicated data extraction), a simple page/file model may understate complexity.

Step-by-step example

Below is a realistic example showing how you’d use the DocketMath calculator.

Scenario

You want: “All written policies and procedures relating to vehicle towing, adopted or amended between January 1, 2024 and June 30, 2024.”
Assume:

The custodian will search one internal department
Responsive records are likely stored as PDFs
You expect minor redactions (names, phone numbers, or other exempt details)
Total responsive material might be about 60 pages once compiled

Step 1: Set your search estimate

Start with a conservative estimate you can defend.

Estimated search time: 2 hours
Rationale: One department, six-month window, targeted policy/procedure category.

Step 2: Set your review/redaction estimate

Review time is often where costs diverge.

Estimated review time: 1.5 hours
Rationale: Expect some redactions but not an exhaustive redaction effort for every page.

Step 3: Set duplication/export parameters

Because you’re requesting PDFs, duplication may be closer to electronic delivery than physical copying.

Choose:

Duplication method: electronic (PDF export or email transfer)
Estimated pages: 60
Expected file count: 3 (e.g., one policy document plus related amendments)

Step 4: Run the estimate

In DocketMath’s Public Records Fee Calculator, you would enter those inputs and generate an estimated total.

Step 5: Interpret output and adjust

After the first run, consider sensitivity—what changes the estimate the most?

Common “levers” in the output:

If you widen the date range from 6 months to 2 years, estimated search and review time can grow quickly.
If the custodian says the records are in scanned images requiring OCR and page-by-page processing, duplication and labor may rise.
If you request metadata plus attachments from multiple systems, file count and search effort can jump.

Example sensitivity tweak

Suppose you rerun the estimate with:

search time increased from 2 hours to 4 hours
review increased from 1.5 hours to 3 hours
pages increased from 60 to 110

Even without changing duplication method, the estimate could increase sharply because labor time often dominates total cost.

Warning: If your estimate assumes “electronic delivery” but the custodian can only provide records after heavy conversion, the actual fee could be higher. Try to specify preferred formats clearly in your request to reduce reformatting.

Common scenarios

This section covers recurring request patterns and how they tend to affect fees. You can use these as a planning checklist while preparing inputs for the calculator.