Public Records Fee Calculator Guide for Utah

8 min read

Published March 22, 2026 • By DocketMath Team

What this calculator does

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

DocketMath’s Public Records Fee Calculator (Utah) helps you estimate the fees you may be charged when requesting records under Utah’s public records framework—and it does so in a structured way so you can see how each input changes the total.

Because public-records fees often depend on what format you request and how much work is required to produce the records, the calculator is designed to let you model common fee components (for example, clerical time, duplication, and delivery-related costs) based on the information you have before you submit a request.

What you’ll get from the calculator

  • A fee estimate based on your selected options and quantities
  • A breakdown of the estimated line items
  • A quick way to compare scenarios (for example, “electronic” versus “paper” delivery)

Note: A fee estimate is not an official determination. Agencies can apply their own fee schedules and production methods. Use the tool to plan and budget, not to guarantee a specific amount.

When to use it

Use the DocketMath calculator when you’re preparing a records request and you want to anticipate budget and timing implications. It’s especially useful for requests that are likely to require more than a single page printout.

Good times to run the calculator

  • You’re requesting a substantial volume of records (e.g., hundreds or thousands of pages)
  • You need records in a specific format (PDF, scanned images, printed copies, etc.)
  • You expect some records to require review, redaction, or compilation
  • You’re comparing multiple requests (for example, “send as electronic files” versus “paper copies”)

Timing reality check (Utah context)

Utah has a general statute of limitations period of 4 years for many civil claims. The general limitation period referenced by the Utah courts is 4 years under Utah’s general rule for civil actions. In general terms, that period is tied to Utah Code § 76-1-302, as reflected in the Utah courts’ legal help materials.

Warning: The 4-year general statute of limitations (Utah Code § 76-1-302) is a different question than fees for a public records response. Don’t treat the calculator’s fee estimate as anything related to deadlines for claims. Fees and limitations are separate legal topics.

Step-by-step example

Here’s a concrete walkthrough showing how you can model an estimate with DocketMath’s public-records-fee calculator for Utah.

Scenario: Records request likely to generate a moderate fee

Assume you’re requesting:

  • 250 pages of records
  • You want electronic delivery (for example, a PDF or electronic files)
  • You expect the agency will need some review time due to standard handling (e.g., organizing, compiling)

Step 1: Choose your delivery format

Select the option that best matches your request, such as:

  • Electronic (often reduces duplication costs compared to printing)
  • Paper (often increases duplication and printing-related costs)

Effect on the output: Electronic delivery typically reduces or changes the duplication component. Paper delivery can increase per-page costs.

Step 2: Enter approximate pages or pages-equivalent

Enter the estimated volume:

  • Pages: 250

Effect on the output: Page volume usually scales the duplication component and may indirectly influence time estimates if the system uses page-based assumptions.

Step 3: Estimate “processing” time or complexity

If the calculator includes a field for estimated processing time, select a reasonable level based on what you’ve requested:

  • e.g., “moderate compilation/review”

If the calculator provides a time-based slider or a checkbox-based complexity option, use the one that matches your request scope.

Effect on the output: Higher processing time increases the labor/time line items.

Step 4: Add or confirm delivery-related costs (if available)

Some calculators include toggles for delivery method:

  • pickup versus mailing
  • shipping or other handling

Effect on the output: Delivery toggles can add a flat handling fee.

Step 5: Read the breakdown—not just the total

After you calculate, focus on:

  • which line item dominates your estimate
  • which input you can adjust to lower the total

Example outcome (illustrative structure):

Line item (estimated)Likely driverHow to reduce
Processing / clerical timecomplexity and volumenarrow scope; request a date range
Duplication / per-page costpages requestedrequest electronic; reduce page range
Delivery handlingmethodchoose pickup or electronic delivery

Even if the exact dollar amounts vary based on the calculator’s built-in fee model, the workflow stays consistent: volume + format + processing assumptions determine the estimate.

Common scenarios

Public records requests come in patterns. Below are common scenarios you can model in the calculator to see how fee estimates may shift.

1) “Small, targeted request” (low volume)

Typical request shape

  • 1–25 pages
  • specific documents or a specific incident
  • electronic delivery preferred

Calculator inputs to model

  • pages: 10
  • format: electronic
  • processing: low

What to expect

  • Total often stays low because the per-page and time components remain limited.

✅ Good move: If you can specify exact records, do so—narrow scope usually reduces processing time.

2) “Broad date range” (high volume)

Typical request shape

  • 2–5 years of responsive records
  • broad category (e.g., “all communications”)
  • agency must compile and sort

Calculator inputs to model

  • pages: 1,500–4,000
  • format: electronic or paper
  • processing: high

What to expect

  • Processing/time can become the largest driver, especially if the request is not already organized.

✅ Good move: Break a large request into smaller date windows so you can confirm what’s responsive before expanding.

3) “Request for records with likely redaction”

Even without assuming a specific fee policy, redaction and confidentiality screening typically increase labor.

Calculator inputs to model

  • pages: 500
  • format: electronic
  • processing: high

What to expect

  • Line items tied to review time will rise more noticeably than duplication costs.

Pitfall: If you only budget for per-page duplication and ignore processing time, your actual charge can exceed your estimate.

4) “Delivered by mail vs pickup”

Delivery can add a handling cost depending on the agency’s approach.

Calculator inputs to model

  • pages: 200
  • format: paper
  • delivery: mail (or shipping)

What to expect

  • A flat handling component may apply on top of per-page duplication.

✅ Good move: If pickup is an option and you can wait, model pickup to reduce delivery-related charges.

Scenario comparison checklist (use before calculating)

Use these items to decide what to enter:

Tips for accuracy

Small adjustments to your assumptions can materially change the estimate. These tips focus on making your inputs closer to how the agency will practically produce the records.

1) Use page estimates tied to how records are actually stored

If you don’t know the page count, estimate based on:

  • how the records are kept (e.g., emails exported to PDFs, scanned documents)
  • typical page count per record unit
  • whether attachments are included

Better than: guessing a round number with no basis.
Better approach: approximate from sample output or a smaller pilot request.

2) Prefer electronic delivery when it reduces duplication costs

If the calculator lets you toggle format, compare:

  • electronic delivery: duplication costs often drop
  • paper delivery: duplication costs often rise

Why this matters: duplication fees frequently correlate directly with page volume.

3) Model processing time separately from duplication

If you only adjust pages, you may miss the labor component.

Use the calculator’s processing/time inputs to reflect:

  • sorting and compilation
  • identifying responsive records
  • review/redaction steps

4) Keep your request scope consistent with the estimate

If your request is “all records from 2019–2024,” but you estimate based on 50 pages, your estimate will likely miss the processing burden and the response volume.

Rule of thumb: the broader the scope, the more you should shift assumptions from “low processing” to “moderate/high processing.”

5) Run multiple scenarios and choose the most budget-realistic one

Instead of one number, produce a small set:

  • Scenario A: narrow scope + electronic
  • Scenario B: broader date range + electronic
  • Scenario C: broader date range + paper delivery

Then compare totals and line items to decide what you can afford.

6) Understand where legal timelines fit (and where they don’t)

Utah’s general statute of limitations is 4 years, referenced under Utah Code § 76-1-302 in Utah courts’ legal help materials.

That 4-year rule affects certain legal timeframes for bringing claims; it generally doesn’t determine what an agency charges for producing documents. Keep your budgeting separate from timing of legal rights.

Related reading