Washington Public Records Act: deadlines, penalties, and the five-day rule

Washington's Public Records Act is one of the most requester-friendly disclosure laws in the United States. It is construed liberally and its exemptions narrowly. Courts review agency decisions de novo, with the burden on the agency. A requester who prevails in court recovers all costs and reasonable attorney fees — and the judge can attach a price to every single day of wrongful delay. There is no fixed final deadline to produce records, and that is precisely what makes the PRA operationally demanding. The question a Washington records officer has to be able to answer is not “did we hit the deadline?” but “can we defend every day between receipt and closure?”

This guide covers the parts of the Act that determine whether that defence holds: the five-day rule, reasonable estimates and installments, the withholding statement, the 2017 amendments on bot requests, fees, and JLARC reporting, and the penalty case law that puts numbers on failure. Statute citations link to the official text. This is general information, not legal advice.

The ground rules

The PRA, chapter 42.56 RCW, applies to state agencies and to every local government — cities, counties, special purpose districts, school districts, ports. A request does not need to use a particular form, cite the Act, or state a purpose, and agencies may not distinguish among requesters. (The narrow exception: an agency may ask enough to determine whether a request is for a list of individuals for commercial purposes, which RCW 42.56.070 prohibits it from fulfilling.) Under RCW 42.56.080, a request must be for “identifiable records”: a request for all or substantially all of an agency's records is not valid, but a request for all records on a topic, keyword, or name is.

Two phrases in RCW 42.56.100 do a great deal of work: agencies must provide the “fullest assistance to inquirers” and the “most timely possible action on requests.” These are enforceable standards, not aspirations — courts weigh them when deciding whether an agency's pace and conduct were reasonable. The same section also freezes destruction: once a record is requested, it cannot be destroyed even if its retention schedule says it is due.

The five-day rule (RCW 42.56.520)

RCW 42.56.520 gives an agency five business days after receiving a request to respond in one of five ways:

1. Produce the records. The clean close — realistic for small, well-indexed requests.
2. Provide an internet address and link to the specific records on the agency's website. This option was added in 2017; if the requester tells you they cannot access the records online, you must provide copies or in-person access.
3. Acknowledge the request and provide a reasonable estimate of the time needed to respond. This is the workhorse response for anything non-trivial.
4. Acknowledge the request and seek clarification if it is unclear — and still provide, to the greatest extent possible, a reasonable estimate of time if it is not clarified.
5. Deny the request, with a written statement of the specific reasons.

The statute also names the legitimate reasons more time may be needed beyond the five days: clarifying the request's intent, locating and assembling records, notifying third parties or other agencies affected by the request, and determining whether records are exempt.

Counting the days

The five days are business days — weekends and state holidays don't count — and under the attorney general's model rules, day one is the first business day after receipt. A request that lands Wednesday afternoon is owed a response by the following Wednesday. Missing the window is itself a violation, and it is the easiest violation for a requester to prove, because it is date arithmetic. Log every request the day it arrives and calendar day five before you do anything else with it.

Clarification and denial mechanics

If a request is unclear, you may ask the requester to clarify. If the requester never answers and the entire request is unclear, the statute says you need not respond further — but if any portion is clear, you must respond to that portion. Denials must be written, must state the specific reasons, and trigger an internal review obligation: the agency's denial is deemed final at the end of the second business day after the denial, which is what opens the courthouse door quickly. A denial letter is never the place to be vague.

After day five: estimates, installments, and “fullest assistance”

Once you have acknowledged a request, your own reasonable estimate becomes the working deadline. “Reasonable” means built from something you could explain to a judge: the number of custodians to canvass, the volume to review, redaction time, third-party notice periods. An estimate produced by a method survives scrutiny; a round number produced by habit does not. If circumstances genuinely change, revise the estimate and tell the requester why — a documented, explained revision reads as diligence, while a silent slide past your own date reads as delay. Courts have little patience for estimates that are padded “to be safe” and then coasted against; under RCW 42.56.100, the standard is the most timely possible action.

For large requests, installments are the tool the statute hands you. RCW 42.56.080 directs agencies to produce records on a partial or installment basis as they are assembled, and RCW 42.56.120 lets you charge for each installment as it is provided and require a deposit of up to ten percent of the estimated cost. A fast first installment is the best evidence of fullest assistance you can create. The statute also protects you from abandoned requests: if an installment is not claimed or reviewed — within thirty days, under the model rules' framing — the agency is not obligated to fulfill the balance of the request.

Penalty exposure: $0 to $100 a day, and it compounds

Under RCW 42.56.550(4), a person who prevails against an agency is awarded all costs, including reasonable attorney fees, and the court may award “an amount not to exceed one hundred dollars for each day” the person was denied the right to inspect or copy the record. Until 2011 the statute carried a mandatory $5-a-day minimum; ESHB 1899 (Laws of 2011, ch. 273) removed it, so the daily penalty now runs from zero to $100 at the court's discretion. Review is de novo, the agency bears the burden of proving an exemption applies, and the limitation period is one year from the agency's claim of exemption or its last production of records on an installment basis. (One carve-out: under RCW 42.56.565, incarcerated requesters cannot be awarded penalties unless the agency acted in bad faith.)

How courts pick the number inside that range comes from Yousoufian v. Office of Ron Sims (2010), which laid out sixteen factors — seven mitigating, nine aggravating. Read as an operations checklist, the mitigating factors are striking: prompt responses, good-faith compliance, proper training and supervision of personnel, reasonable explanations for noncompliance, helpfulness to the requester, and the existence of systems to track and retrieve records. Process is literally a defence. On the other side sit negligence, recklessness, bad faith, the public importance of the records, economic loss to the requester, and the deterrence a court thinks an agency of your size requires.

Three cases every records officer should know

• Yousoufian v. Office of Ron Sims, 168 Wn.2d 444 (2010). A 1997 request to King County for records on the public financing of the Seahawks stadium turned into more than a decade of litigation. The trial court found the county “negligent … at every step of the way.” The Supreme Court set the penalty at $45 a day applied across grouped records — $371,340, plus attorney fees.
• Wade's Eastside Gun Shop, Inc. v. Department of Labor & Industries, 185 Wn.2d 270 (2016). The Supreme Court affirmed a $502,827 penalty against L&I for delayed production of investigation records sought by the Seattle Times — and confirmed that in appropriate cases trial courts may calculate penalties per page, not just per request. Still the largest penalty in a reported Washington decision.
• Zink v. City of Mesa, 162 Wn. App. 688 (2011) and later proceedings. The cautionary tale for small agencies. Records disputes with a city of roughly 500 people ran for over fifteen years; the trial court's initial award of penalties, costs, and fees was about $246,000, and on remand in 2018 the court calculated a $353,000 penalty and reduced it to $175,000 expressly because of the town's size — still roughly $350 per resident. Small agencies are not graded on a curve until after the violations are counted.

Withholding without a log is silent withholding

RCW 42.56.210(3) requires that any response refusing inspection, in whole or in part, include the specific exemption authorizing the withholding and a brief explanation of how the exemption applies to the record withheld. In Sanders v. State (2010) the Supreme Court made the corollary explicit: the existence of withheld records must be disclosed to the requester. Redacting or omitting records without saying so — silent withholding — is a violation on its own, separate from whether the exemption would have held up.

The standard tool is the exemption log (the model rules call it a withholding index): one line per record or redaction, identifying the record (date, type, author, recipient), the statute relied on, and a brief, record-specific explanation of how it applies. “Exempt under RCW 42.56.230” pasted down a column is not a brief explanation; it is a template. Build the log as you redact — reconstructing one eighteen months later, in litigation, from a folder of flattened PDFs, is how weak explanations get written.

Third-party notice

Under RCW 42.56.540, an agency has the option of notifying people named in or specifically affected by a record before releasing it, giving them the chance to seek an injunction in superior court — the standard being that release would clearly not be in the public interest and would substantially and irreparably damage a person or a vital government function. Notice is good practice for personnel records, complaints, and commercial information, and RCW 42.56.520 explicitly recognizes third-party notice as a legitimate reason for additional response time. But notice does not transfer the decision: unless a court enjoins release, the agency still owns the response and the clock.

The 2017 amendments: bots, fees, and JLARC reporting

EHB 1594 and EHB 1595 (both effective July 23, 2017) were the biggest operational update to the PRA since the chapter was recodified. Three pieces matter day to day.

Bot requests

RCW 42.56.080(3) lets an agency deny multiple requests from the same requester within a 24-hour period if it reasonably believes they were automatically generated by a computer program or script and responding to them would cause excessive interference with the agency's other essential functions. Both conditions must hold, and the provision covers the flood, not the topic — it is not a tool for turning away persistent humans.

The default fee schedule

Before 2017, agencies could not charge for electronic production at all without an actual-cost study few could afford to run. RCW 42.56.120 now gives agencies that have not calculated actual costs a statutory default schedule: 15 cents per page for photocopies, 10 cents per page for records scanned into electronic format, 5 cents per each four electronic files or attachments uploaded or transmitted, and 10 cents per gigabyte transmitted electronically — or a flat fee of up to $2 for a request where costs are documented to reach it. Customized service charges are available where a request needs specialized IT expertise. The amounts are modest by design; the point of charging them is less revenue than the discipline of measuring what production costs.

JLARC annual reporting

EHB 1594 added the requirement that turns records management into a reported metric. Under RCW 40.14.026(5), every agency whose actual staff and legal costs for fulfilling public records requests reached $100,000 in the prior fiscal year must report to the Joint Legislative Audit and Review Committee by July 1 each year, against fifteen enumerated metrics: five-day response compliance, estimates provided, average and median time to close, clarifications sought, denials and their bases, abandoned requests, requester types, electronic versus physical fulfillment, staff time per request, total costs, litigation counts, litigation costs and penalties paid, records management expenses, and costs recovered from requesters. Agencies under the threshold still log in to attest they are under it. JLARC publishes the results in public dashboards — your numbers sit next to your peers'. The practical read: the statute is a management-dashboard specification. If your request tracking produces these fifteen numbers as a byproduct, July 1 is an export; if it doesn't, July 1 is an annual archaeology project.

Records officers, training, and the model rules

Every state and local agency must designate and publicly identify a public records officer under RCW 42.56.580 — the public's point of contact and the person who oversees compliance. Under RCW 42.56.152 (the Open Government Trainings Act, 2014), records officers must complete PRA and records-retention training within ninety days of assuming the role and refresh it at least every four years; online training counts. Remember that Yousoufian lists proper training as a penalty-mitigating factor — keep the completion records.

The attorney general's model rules, chapter 44-14 WAC (last updated effective April 2, 2018), are advisory and nonbinding, but they are the closest thing Washington has to a reference implementation of the PRA: day-counting, estimates, installments, withholding indexes, fee practice. Agencies are encouraged to adopt them by rule or ordinance, and courts and auditors treat them as the baseline of what a well-run agency does. If your local procedure differs from the model rules, know why.

What a defensible PRA operation looks like

• Log every request the day it arrives and calendar day five automatically — the five-day response is the one deadline with no judgment in it.
• Template the five responses so day-five letters are assembled, not composed.
• Estimate by method, not habit: custodians × volume × review rate, written down, so every estimate has a defensible basis.
• Default to installments on anything large, and get the first installment out early.
• Build the exemption log as you redact — record, statute, brief record-specific explanation — never after the fact.
• Capture staff time and cost per request as you go; it is your JLARC report, your fee justification, and your penalty mitigation in one dataset.
• Train on schedule and keep the certificates — training is both a statutory duty and a named mitigating factor.

Where AccessPoint fits

Everything above is a systems problem wearing a legal costume: a clock that starts on receipt, letters generated on day five, estimates with a written basis, installments tracked to closure, a withholding log built during redaction, and fifteen JLARC metrics that should fall out of the data instead of being excavated every June. That is what AccessPoint is for. It runs the full request lifecycle inside your own Microsoft 365 tenant — your records never leave your environment — and the Washington PRA jurisdiction pack preloads the five-business-day clock, response templates, exemption logging, installment and fee tracking, and JLARC-shaped reporting, so the platform speaks RCW 42.56 out of the box.

Related reading

See how AccessPoint handles Washington's rules end to end on the Washington PRA jurisdiction page, or walk through the full request lifecycle in FOI request management. Replacing an existing system? Compare AccessPoint with GovQA and NextRequest — or skip ahead and book a live demo on Washington's rules.

Sources

• RCW 42.56.520 — Prompt responses required, Washington State Legislature (last amended 2017; accessed August 2026)
• RCW 42.56.550 — Judicial review of agency actions, Washington State Legislature (penalty provision at subsection (4); accessed August 2026)
• RCW 42.56.100 — Protection of public records — public access (“fullest assistance” standard; accessed August 2026)
• RCW 42.56.080 — Identifiable records; bot requests (accessed August 2026)
• RCW 42.56.120 — Charges for copying; deposits; installments (accessed August 2026)
• RCW 42.56.210(3) — Brief explanation of withholding (accessed August 2026)
• RCW 42.56.540 — Court protection of public records; third-party notice (accessed August 2026)
• RCW 42.56.580 — Public records officers and RCW 42.56.152 — Training (accessed August 2026)
• RCW 40.14.026(5) — JLARC public records reporting and JLARC public records reports and dashboards (annual reports 2019–2025; accessed August 2026)
• Chapter 44-14 WAC — Attorney General's Model Rules on Public Records Act compliance (last updated effective April 2, 2018) and the AGO Open Government Resource Manual (accessed August 2026)
• Yousoufian v. Office of Ron Sims, 168 Wn.2d 444 (Wash. 2010)
• Wade's Eastside Gun Shop, Inc. v. Dep't of Labor & Indus., 185 Wn.2d 270 (Wash. 2016)
• Zink v. City of Mesa, 162 Wn. App. 688 (Wash. Ct. App. 2011) and Spokesman-Review coverage of the 2018 remand award (June 15, 2018)
• MRSC — Responding to Public Records Requests and MRSC — Tracking Records Requests and Reporting PRA Metrics (accessed August 2026)

Last reviewed: August 2026. This guide is general information for records practitioners, not legal advice — rely on the official text of chapter 42.56 RCW and your agency's counsel.