Bearpointᛏ

For Washington Requesters Facing a Stonewalled Production

The Washington Public Records Act, chapter 42.56 RCW, is one of the strongest transparency statutes in the United States and one of the most routinely violated. The pattern repeats: silent five-day clocks, indefinite "reasonable estimates," exemption logs that omit the exemption, and productions printed to paper and re-scanned to strip every byte of forensic metadata. This guide tells a requester how to recognize each move, document it, and compound pressure through channels the agency cannot consolidate.

1. The PRA Penalty Structure (and Why It Matters)

RCW 42.56.550(4) authorizes courts to award penalties of up to $100 per day for each record the agency wrongfully withheld. The Washington Supreme Court resolved any ambiguity about aggregation in Yousoufian v. Office of Ron Sims, 152 Wn.2d 421, 98 P.3d 463 (2004) (Yousoufian I), and again in Yousoufian v. Office of Ron Sims, 168 Wn.2d 444, 229 P.3d 735 (2010) (Yousoufian V): there is no aggregate cap on PRA penalties, and the per-record, per-day structure compounds across the duration of the violation. An agency sitting on even a few hundred wrongfully withheld records faces statutory exposure that compounds rapidly before attorney fees and costs under RCW 42.56.550(4). That math is not theoretical. It is the number a superior court is empowered to enter.

2. The Five-Day Acknowledgment Clock

RCW 42.56.520(1) requires the agency to respond within five business days with one of four actions: provide the records, acknowledge the request and give a reasonable estimate, request clarification, or deny in writing. Silence is itself a violation. The clock excludes Saturdays, Sundays, and legal holidays under RCW 1.16.050. Calendar the receipt date, count five business days forward, and screenshot the inbox if nothing arrives. The five-day record is the first exhibit in any enforcement action.

3. What "Reasonable Estimate" Means

Agencies frequently issue acknowledgments that promise records "as soon as practicable" with no production date. That is not an estimate. WAC 44-14-04003 instructs agencies that estimates must be based on the actual time needed to assemble the response, must be revised when circumstances change, and must be communicated to the requester. In Hobbs v. State, 183 Wn. App. 925, 335 P.3d 1004 (2014), the court rejected open-ended timelines and confirmed that an agency cannot use a vague estimate as cover for indefinite delay. Demand a specific date. When the date slips, demand a written revision. Each missed estimate is a documentary brick.

4. The Print-to-Scan Spoliation Pattern

Bearpoint has documented this pattern across multiple Washington public-records productions. The typical indicators are consistent: the agency had native electronic records, chose to print and re-scan the entire production, and delivered image-only PDFs. In one case, the technical capability for native production was proven by a native-format board agenda the same agency published to its public website days before the response went out. Selective destruction, not technical limitation. Indicators to flag:

• Identical scan timestamps appearing across allegedly distinct document classes
• All-image PDFs where the underlying source was clearly a searchable native file (Outlook email, Word document, native PDF)
• Byte-identical "duplicate" PDFs used to pad the production count
• Stripped metadata: no Author, no Modified date, no Application field, no Creator tool
• Missing email headers in produced email "records" (no Message-ID, no Received chain, no DKIM signature)
• Fujitsu ScanSnap or comparable consumer-scanner signature in the PDF Producer field

5. Building the Spoliation Record

Forensic preservation begins the moment the production arrives. Hash every received file with SHA-256 before opening it. Run ExifTool against every PDF and save the full metadata dump to a dated log. Compare PDF Producer fields across the production: if the agency claims a uniform scanning workflow but the metadata shows three different producers, the workflow narrative is false. After cataloguing, send a follow-up request demanding the native files. Refusal to produce natives when natives demonstrably exist is itself probative evidence of bad faith under the standards discussed in Neighborhood Alliance of Spokane County v. County of Spokane, 172 Wn.2d 702, 261 P.3d 119 (2011). Document chain of custody from the moment of receipt forward; a clean chain is the difference between a courtroom exhibit and a hearsay objection.

6. Independent Enforcement Channels

Filing in superior court under RCW 42.56.550 is the formal remedy, but it is not the only pressure point. The following vectors operate in parallel and cannot be consolidated by the agency:

• Washington State Auditor: the fraud reporting program under RCW 43.09.260 reaches records destruction that violates retention schedules under chapter 40.14 RCW. Single Audit Act and 2 CFR Part 200 routing applies when the agency receives federal pass-through funds.
• Attorney General's Open Government Ombudsman: no statutory deadline, but the office creates a written record of the complaint and a paper trail of the agency's response or non-response.
• Joint Legislative Audit and Review Committee (JLARC): appropriate when the noncompliance is systemic across multiple requesters or appears in multiple audits of the same agency.
• OSPI for school districts specifically: the Office of Superintendent of Public Instruction holds accreditation and apportionment leverage over districts that systematically defy statutory disclosure obligations.
• Federal regulator mirror filings: when the underlying records concern Title VI of the Civil Rights Act of 1964, FERPA, IDEA, or a federally funded program, the federal agency is independently entitled to the same records under its enforcement authority.

Each vector compounds. None of them stops a 42.56 action in superior court.

7. What a Complete PRA Demand Letter Looks Like

This is a structural checklist, not a template. A demand that omits any of these elements weakens later enforcement:

• Specific identification of the records sought, narrowed where possible to avoid "any and all" framings that invite over-broad objections
• Date range with start and end dates
• Requested format, with native electronic preferred and explicitly stated
• Statutory authority cited (RCW 42.56.080, .520, .550 at minimum)
• Express deadline for the five-day acknowledgment with the calendar date computed
• Reservation of rights as to penalties under RCW 42.56.550(4), attorney fees, and costs
• Service method: email to the records officer plus certified mail with return receipt to the agency head

8. Common Agency Tactics and Counter-Tactics

• "Records do not exist": demand documentation of the search performed. RCW 42.56.080 imposes an affirmative search obligation; a bare denial is insufficient.
• "Exempt under deliberative process": the exemption must be specific to each record and logged. RCW 42.56.210(3) and RCW 42.56.240 require an itemized exemption log identifying each withheld record and the statute relied on.
• "Third party objection": RCW 42.56.540 creates a ten-day notice procedure. Inspect for sham objections solicited by the agency itself to manufacture delay.
• "Excessive request": not a recognized exemption. Agencies cannot deny disclosure for administrative inconvenience under Hangartner v. City of Seattle, 151 Wn.2d 439, 90 P.3d 26 (2004).
• Privacy exemption inflation: the right of privacy in RCW 42.56.050 is narrow. Bainbridge Island Police Guild v. City of Puyallup, 172 Wn.2d 398, 259 P.3d 190 (2011), and the SAFER Act framework constrain how broadly an agency can invoke it.

9. When to Bring in Bearpoint

Bearpoint does not represent requesters. We build the evidentiary architecture that makes a lawyer's enforcement case cheaper to assemble: metadata forensics, SHA-256 chain of custody, exemption-log analysis, and multi-vector escalation maps. We are an evidence shop, not a law firm. If you suspect spoliation in a Washington PRA production, email info@bearpointfdn.org with the agency name, request date, and production date.