Public Records Fee Calculator Guide for Oregon

What this calculator does

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

DocketMath’s Public Records Fee Calculator (Oregon) estimates the kinds of costs an Oregon public body may charge when it produces records in response to a request. It’s designed to help you forecast fee ranges so you can decide how to refine your request, anticipate timing, and budget for production.

This tool is especially useful because Oregon public records fees can involve multiple components—often including search time, review time, copying/scanning, and delivery costs—and those components can change depending on how your request is framed.

You can use the calculator here: /tools/public-records-fee

When to use it

Use the calculator when you’re preparing a public records request to an Oregon agency and want a structured way to estimate production costs. It works best if you can approximate the following before filing:

• How many records you’re asking for (e.g., 25 emails vs. 2,000 pages)
• What time frame you’re requesting (e.g., January 2023 only vs. January–December)
• How the agency will likely search (e.g., “emails from a named account” vs. “all documents mentioning ‘project phoenix’ across multiple departments”)
• Whether redactions are expected (redactions increase review time)
• Preferred delivery format (electronic vs. paper)

Common times to run the calculator:

• Before you file, to decide whether to narrow scope to reduce costs.
• After you receive an estimate, to compare your assumptions (e.g., number of pages, expected redactions).
• When planning multiple related requests, so you can keep your budgeting assumptions consistent.

Step-by-step example

Below is a realistic example using DocketMath’s Oregon calculator. The calculator is the public-records-fee tool at /tools/public-records-fee.

Scenario: A “narrowed” request for emails with redactions

You request:

• Record type: emails
• Custodian scope: one named employee and one backup mailbox
• Time period: January 1–31, 2024
• Search terms: a known project name
• Delivery: electronic (PDF export)
• Expected redactions: yes (emails likely contain personal information)

Step 1: Estimate the scope

Start by translating “records” into likely output pages, since pages often drive production effort.

You estimate results might include:

• Number of emails/messages: ~180 messages
• Average pages per message when exported: ~2 pages
• Total pages likely produced: ~360 pages (180 × 2)

Step 2: Estimate search vs. review effort

In the tool, you’ll typically provide estimates that reflect effort that can include search and review/redaction.

For this example, suppose you enter:

• Search time: 2–3 hours (finding and extracting relevant emails)
• Review/redaction time: 6–8 hours (removing exempt information)
• Copy/scan/format time: relatively small, since you requested electronic delivery—but not necessarily zero (preparing/exporting and formatting files can still take time)

Why these numbers make sense here:

• Your request is for one month and two mailboxes, so search is likely lower than a broad “all departments” request.
• You expect redactions, so review time may be the biggest driver.

Step 3: Account for delivery and format

Because you requested electronic delivery, you’re usually avoiding (or reducing) paper copying costs. Still, the agency may need to convert/export, package files, or otherwise process the data into a deliverable format.

So you include whatever the calculator’s delivery input requires (electronic vs. paper), and you keep in mind that “electronic” is often cheaper, but it doesn’t automatically mean “zero processing.”

Step 4: Interpret the calculator’s output

After you enter your estimates, the calculator returns an estimated fee range based on the components you selected.

A practical way to use the results:

• If the estimate is higher than expected, adjust the assumptions that match the real-world situation, such as:

  • Reducing estimated pages if you can narrow the time window (e.g., 2 weeks instead of 1 month).
  • Modifying review/redaction time only if you have a strong basis (e.g., records are already known to be largely sanitized).
  • Increasing search time if you expect multiple systems, manual exports, or multiple search locations.

A short “what-if” check

If you widen the request from 1 month to 3 months, and the volume is similar, your estimated pages might rise from ~360 to ~1,080 pages. In many fee frameworks, the biggest drivers are often:

• number of records/pages produced
• amount of review/redaction
• search complexity

That’s why the calculator is most valuable as a scenario tool—not just a one-time number.

Common scenarios

These scenario patterns help you choose inputs that meaningfully affect cost—and understand what happens when you change your request.

1) Broad timeframe + vague search terms

You ask: “All emails mentioning ‘project phoenix’ between 2022 and 2024 across all departments.”

Typical calculator impact:

• Search time increases sharply (more custodians/systems)
• Review time increases (more irrelevant hits to evaluate and potentially redact)
• Pages produced can explode

Cost reducers to consider:

• narrow custodians
• narrow the program/unit
• narrow the time window
• tighten search terms

2) Small set of records with low redaction risk

You ask: “Meeting agenda PDFs for March 2024 and attendance logs,” and you expect they’re already publicly posted with minimal sensitive content.

Typical calculator impact:

• Review/redaction time may be low
• Copy/scan/delivery may dominate the estimate

In scenarios like this, delivery format can noticeably change the outcome (electronic delivery usually helps).

3) Document-heavy requests (scanned records/attachments)

You ask: “All invoices and receipts for FY 2023 related to procurement contracts,” including scanned attachments.

Typical calculator impact:

• Pages produced can be large even if the “number of items” seems moderate
• Review may still be required if invoices include personal info or sensitive financial details

Practical cost management:

• start with a smaller segment (e.g., one quarter)
• request electronic/searchable formats if feasible

4) Redaction-heavy requests

You ask: “Records showing internal deliberations, including emails, memos, and drafts,” which often include personal data and sensitive internal content.

Typical calculator impact:

• Review time becomes the biggest variable
• Even fewer pages can still require substantial redaction work

If your goal is factual information, you can sometimes reduce burden by requesting final versions or specific categories (e.g., “final reports” rather than drafts).

5) Requests after receiving a prior production

You ask: “All revisions to document X after the version you produced last month.”

Typical calculator impact:

• Search may be efficient because the agency already understands the document family
• Review can still be significant, but the scope may be more bounded

This is often a good scenario to run the calculator twice:

• once before you request
• again after the agency explains its approach (so you can refine inputs)

Tips for accuracy

These practical tips help make your assumptions more realistic—so the DocketMath estimate is more useful.

1) Use “pages likely produced” as your anchor

If you can estimate pages rather than just “documents,” your estimate tends to track effort better.

Example:

• 200 emails ≠ 200 pages
  Exported emails often include headers/signatures/forwarded content and attachments, which can raise page count.

A common approach:

• estimate an average pages-per-item, then multiply by item count.

2) Separate “search” from “review”

Even if records are easy to locate, review/redaction can take longer. In particular, requests involving:

• personal information
• security-related details
• internal deliberations

often increase review work substantially.

3) Predict redaction likelihood, not just “redactions in general”

Instead of guessing broadly, evaluate whether your request likely includes:

• names + contact info
• account identifiers
• system logs
• medical or financial details
• minors’ information

If redactions are likely in most records, set review/redaction time higher rather than assuming a low workload.

4) Validate with incremental requests

If you don’t know how many records exist, consider a smaller “test” portion:

• request a shorter time window (e.g., 2–4 weeks)
• then expand once you see actual volume

This often produces a much more accurate second estimate than trying to guess everything upfront.

5) Keep a simple notes log of your inputs

Write down your basis for each estimate:

• how you counted pages
• what export format you assumed
• why you chose 2 hours vs. 6 hours of review

If the agency provides an itemized fee explanation later, these notes make it easier to identify which assumptions were off.

Pitfall to avoid: Don’t understate redaction risk when entering review time. Requests involving internal communications or sensitive/personal information can make a low review-time estimate substantially underestimate the likely charges.

Sources and references

Start with the primary authority for Oregon and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

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