Public Records Fee Calculator Guide for Washington
8 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
DocketMath’s Public Records Fee Calculator helps you estimate likely public records production costs for requests in Washington (US‑WA), using a consistent set of assumptions tied to Washington’s public records framework.
Because Washington law distinguishes between different kinds of record work and different categories of “charges,” calculators need parameters. This tool is designed to make that process transparent by turning common request details into a fee estimate you can compare against your request plan.
In Washington, baseline fee logic often uses the general statute of limitations period of 5 years as timing context in record/retention discussions—cited here for clarity as:
Note: The calculator uses the general/default 5-year limitation period as its timing assumption. No claim-type-specific sub-rule was found in this guide for narrowing that default period, so the estimate treats 5 years as the default.
What the calculator typically needs (as inputs) includes:
- Time range requested (e.g., “January 1, 2021 through December 31, 2025”)
- Number of records or pages you expect to receive (or an estimate)
- Search/browsing scope (e.g., “1 department” vs. “multiple offices”)
- Expected redactions (if any)
- Format preference (paper vs. electronic), when relevant to your request planning
What you get back (as outputs) is an estimate designed to be actionable for drafting your request, asking follow-up questions, or planning whether to narrow the scope.
Warning: A calculator estimate is not a final agency quote. Agencies can assess actual time, use their own cost accounting practices, and may adjust based on what they find during the search.
To use the tool effectively, link your drafting choices to the likely cost drivers—especially scope and time range.
When to use it
Use DocketMath’s public-records-fee calculator when you’re trying to prevent avoidable cost surprises and you want to compare request variants before submitting.
Great times to use it:
- Before sending a broad request
- Example: You’re considering requesting emails for 5+ years. The calculator can show how fee risk increases when the time window expands.
- When you’re refining the “scope” to reduce costs
- You can test two versions: “one agency’s custodians” vs. “all divisions,” or “a specific subject keyword” vs. “all records about a general topic.”
- When an agency asks you to pay for production
- Many agencies will provide a breakdown of fees or ask for clarification. Your calculator estimate can help you evaluate whether the proposed scope seems reasonable.
- When you plan staged requests
- You may request one subset first (e.g., 12 months), then expand only after receiving initial results.
How timing fits in (using your jurisdiction data)
- The default timing assumption in this guide uses 5 years.
- Washington’s default period is referenced here through RCW 9A.04.080 for general context: RCW 9A.04.080 sets a general 5-year period.
- The calculator uses that 5-year default as the baseline time window assumption unless you explicitly narrow the range you’re requesting.
Pitfall: If you assume “the agency should only charge from the last 12 months,” but your request covers a broader timeframe, the cost impact can still be substantial. The safer approach is to narrow the time range in your request to match the scope you can afford.
If your request truly must be broader than 5 years, you can still run the calculator by adjusting the time window input—but be aware your estimate may be less aligned with the calculator’s default timing assumption.
Step-by-step example
Below is a concrete walkthrough using DocketMath’s Public Records Fee Calculator for Washington.
Example request
You want:
- “All emails between Jan 1, 2022 and Dec 31, 2024 from a specific staff member relating to a vendor contract.”
- You expect the agency will need to search email systems and likely make a few redactions (names, private contact info).
Step 1: Open the tool
Use this link: **/tools/public-records-fee
Step 2: Enter your time range
- Start date: 01/01/2022
- End date: 12/31/2024
Even though Washington’s general default period is often described as 5 years under RCW 9A.04.080, your request is 3 years, so your estimate should generally be lower than a 5-year sweep.
Step 3: Enter expected volume
Choose the closest estimate available in the calculator UI:
- Expected pages/emails: 250 pages (or “~250 pages” equivalent)
If you don’t know the volume, you can start with a conservative estimate, then rerun after you narrow the request (e.g., “one keyword,” “one mailbox,” “only finalized messages”).
Step 4: Specify search scope
- Search locations: 1 mailbox / 1 custodian
- Search complexity: medium (because you’re using a topic/vendor keyword)
This is one of the biggest levers. Expanding to “multiple custodians” often increases effort in ways that aren’t linear.
Step 5: Redaction expectations
- Redactions expected: yes, minor to moderate
If you include categories of documents likely to contain personal data, expect higher redaction effort. Conversely, narrowing to “public-facing final documents” may reduce redaction needs.
Step 6: Run the calculation and review outputs
After running, you should get an estimated fee figure plus (typically) a breakdown by major cost drivers such as:
- search/processing time component
- duplication/media component (if included)
- redaction review component (if included)
Use the output in two practical ways:
- Compare Request A vs. Request B
- Example: If you rerun with a narrower keyword list and the estimated fee drops by 35%, that’s a measurable benefit.
- Draft your request to match your budget
- If the estimate is above your comfort threshold, reduce the timeframe (e.g., 36 months → 12 months) or reduce the number of custodians.
Note: The general/default time assumption referenced in this guide is 5 years, tied to RCW 9A.04.080 for context. Your example request is narrower (3 years), which should generally reduce your estimate.
Once you have a number, decide whether you want to:
- proceed as-is,
- split the request into smaller periods, or
- narrow the record categories or custodians.
Common scenarios
The best way to control fees is to recognize predictable patterns in how requests translate into work for an agency. Use the scenarios below to decide what to enter in the calculator and what you can change to lower cost risk.
Scenario 1: “Five-year fishing expedition”
Request style: broad timeframe, broad custodians, broad topic.
Typical cost driver: search time and review/redaction workload.
How to use the calculator:
- Time range: 5 years (default baseline aligned with the general 5-year period referenced here via RCW 9A.04.080)
- Custodians: many
- Keywords: broad
- Redactions: unknown/likely
Cost-reducing adjustments:
- limit to one office or one custodian
- narrow keywords or require a document type (e.g., “final agreements”)
- request shorter slices (e.g., 12 months)
Scenario 2: “Single transaction, narrow window”
Request style: one vendor, one contract action, short date range.
Typical cost driver: targeted search but still requires review.
How to use the calculator:
- Time range: 90–365 days
- Custodian: 1–2
- Document type: specific (contracts, invoices, final versions)
- Redactions: likely but manageable
Cost-reducing adjustments:
- request final documents first
- ask for an index or list of responsive records (if the agency offers that process)
Scenario 3: “Emails are the target”
Request style: correspondence between individuals or within a system.
Typical cost driver: email search complexity and content review.
How to use the calculator:
- Time range: adjust based on your budget
- Search scope: mailbox + keyword + sender/recipient filters
- Redactions: medium likelihood
Cost-reducing adjustments:
- request “emails with attachments” vs. all emails
- narrow to “sent/received between [two people]”
- narrow to subject lines or specific tags
Scenario 4: “Requesting electronic exports”
Request style: you want data in CSV or a structured format.
Typical cost driver: duplication/formatting effort and review.
How to use the calculator:
- Record count: estimated number of rows/files
- Format preference: electronic export
- Redactions: potentially heavy if personal data is included
Cost-reducing adjustments:
- request de-identified fields if permissible in your request context
- ask for records “as stored” if that avoids reformatting
Scenario 5: “You need to know the timeframe first”
Request style: you don’t know what records exist or when.
Typical cost driver: broad exploratory search.
How to use the calculator:
- Start with a shorter range (e.g., 12 months)
- Use results to decide whether to expand to additional years
- Rerun the calculator for each expansion stage
Quick decision checklist
Use these checkboxes to choose how you’ll fill the calculator:
Tips for accuracy
To get a useful estimate, your inputs should mirror
Sources and references
Start with the primary authority for Washington and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.
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
