The act also requires agencies to adopt and enforce rules to provide for the "most timely possible action on requests."RCW 42.56.100. This principle should guide agencies when processing requests. It should be noted that this provision requires the most timely "possible" action on requests. This recognizes that an agency is not always capable of fulfilling a request as quickly as the requestor would like.
For large requests, the agency may ask the requestor to prioritize the request so that he or she receives the most important records first. If feasible, the agency should provide periodic updates to the requestor of the progress of the request. Similarly, the requestor should periodically communicate with the agency and promptly answer any clarification questions. Sometimes a requestor finds the records he or she is seeking at the beginning of a request. If so, the requestor should communicate with the agency that the requested records have been provided and that he or she is canceling the remainder of the request. If the requestor's cancellation communication is not in writing, the agency should confirm it in writing.
If the agency is considering creating a new record instead of disclosing the underlying records, or creating new records from a database, it should obtain the consent of the requestor to ensure that the requestor is not actually seeking the underlying records, and describe any customized service charges that may apply.
Making an electronic copy of an electronic record is not "creating" a new record; instead, it is similar to copying a paper copy. If an agency translates a record into an alternative electronic format at the request of a requestor, the copy created does not constitute a new public record. RCW 42.56.-120(1). Similarly, eliminating a field of an electronic record can be a method of redaction; it is like redacting portions of a paper record using a black pen or white-out tape to make it available for inspection or copying. Scanning paper copies to make electronic copies is a method of copying paper records and does not create a new public record. RCW 42.56.120(1).
An estimate must be "reasonable." The act provides a requestor a quick and simple method of challenging the reasonableness of an agency's estimate. RCW 42.56.550(2). See WAC 44-14-08004(5)(b). The burden of proof is on the agency to prove its estimate is "reasonable."RCW 42.56.550(2).
To provide a "reasonable" estimate, an agency should not use the same estimate for every request. An agency should roughly calculate the time it will take to respond to the request and send estimates of varying lengths, as appropriate. Some very large requests can legitimately take months or longer to fully provide. There is no standard amount of time for fulfilling a request so reasonable estimates should vary.
Some agencies send form letters with thirty-day estimates to all requestors, no matter the size or complexity of the request. Form letter thirty-day estimates for every requestor, regardless of the nature of the request, are rarely "reasonable" because an agency, which has the burden of proof, could find it difficult to prove that every single request it receives would take the same thirty-day period.
While not required,6 in order to avoid unnecessary litigation over the reasonableness of an estimate, an agency could briefly explain to the requestor the basis for the estimate in the initial response. The explanation need not be elaborate but should allow the requestor to make a threshold determination of whether he or she should question that estimate further or has a basis to seek judicial review of the reasonableness of the estimate.
An agency should either fulfill the request within the estimated time or, if warranted, communicate with the requestor about clarifications or the need for a revised estimate.7 An agency should not ignore a request and then continuously send extended estimates. Routine extensions with little or no action to fulfill the request would show that the previous estimates probably were not "reasonable." Extended estimates are appropriate when the circumstances have changed (such as an increase in other requests or discovering that the request will require extensive redaction). An estimate can be revised when appropriate, but unwarranted serial extensions have the effect of denying a requestor access to public records.
If the requestor fails to clarify an entirely unclear request, the agency need not respond to it further. RCW 42.56.520. However, an agency must respond to those parts of a request that are clear. If the requestor does not respond to the agency's request for a clarification within thirty days of the agency's request or other specified time, the agency may consider the request abandoned. If the agency considers the request abandoned, it should send a closing letter to the requestor if it has not already explained when it will close a request due to lack of response by the requestor.
An agency may take additional time to provide the records or deny the request if it is awaiting a clarification. RCW 42.56.520. After providing the initial response and perhaps even beginning to assemble the records, an agency might discover it needs to clarify a request and is allowed to do so. A clarification could also affect a reasonable estimate.
If agency employees or officials are using home computers, personal devices, or personal accounts to conduct agency business, those devices and accounts also need to be searched by the employees or officials who are using them when those devices and accounts may have responsive records.10 If an agency's contractors performing agency work have responsive public records of an agency as a consequence of the agency's contract, they should also be notified of the records request. It is better to be over inclusive rather than under inclusive when deciding which staff or others should be contacted, but not everyone in an agency needs to be asked if there is no reason to believe he or she has responsive records. An email to staff or agency officials selected as most likely to have responsive records is usually sufficient. Such an email also allows an agency to document whom it asked for records. Documentation of searches is recommended. The courts can consider the reasonableness of an agency's search when considering assessing penalties for an agency's failure to produce records.11
Agency policies should require staff and officials to promptly respond to inquiries about responsive records from the public records officer.
After records which are deemed potentially responsive are located, an agency should take reasonable steps to narrow down the number of records to those which are responsive. In some cases, an agency might find it helpful to consult with the requestor on the scope of the documents to be assembled. An agency cannot "bury" a requestor with nonresponsive documents. However, an agency is allowed to provide arguably, but not clearly, responsive records to allow the requestor to select the ones he or she wants, particularly if the requestor is unable or unwilling to help narrow the scope of the documents. If an agency does not find responsive documents, it should explain, in at least general terms, the places searched.12
The act provides that before releasing a record an agency may, at its "option," provide notice to a person named in a public record or to whom the record specifically pertains (unless notice is required by law). RCW 42.56.540.14 This would include all of those whose identity could reasonably be ascertained in the record and who might have a reason to seek to prevent the release of the record. An agency has wide discretion to decide whom to notify or not notify. First, an agency has the "option" to notify or not (unless notice is required by law). RCW 42.56.540. Second, if it acted in good faith, an agency cannot be held liable for its failure to notify enough people under the act. RCW 42.56.060. However, if an agency had a contractual obligation to provide notice of a request but failed to do so, the agency might lose the immunity provided by RCW 42.56.060 because breaching the agreement probably is not a "good faith" attempt to comply with the act.
The practice of many agencies is to give ten days' notice. Many agencies expressly indicate the deadline date on which it must receive a court order enjoining disclosure, to avoid any confusion or potential liability. More notice might be appropriate in some cases, such as when numerous notices are required, but every additional day of notice is another day the potentially disclosable record is being withheld. When it provides a notice, the agency should include in its calculation the notice period in the "reasonable estimate" of time it provides to a requestor.
The notice informs the third party that release will occur on the stated date unless he or she obtains an order from a court enjoining release. The requestor has an interest in any legal action to prevent the disclosure of the records he or she requested. Therefore, the agency's notice should inform the third party that he or she should name the requestor as a party to any action to enjoin disclosure. If an injunctive action is filed, the third party or agency should name the requestor as a party or, at a minimum, must inform the requestor of the action to allow the requestor to intervene.
Notes: | 1See also Op. Att'y Gen. 2 (1998). |
2See Hobbs v. State, 183 Wn. App. 925, 335 P.3d 1004, n.12 (2014) (Court of Appeals encouraged requestors to communicate with agencies about issues related to their records requests). | |
3See Smith v. Okanogan County, 100 Wn. App. 7, 13, 994 P.2d 857 (2000) ("When an agency fails to respond as provided in RCW 42.17.320 (42.56.520), it violates the act and the individual requesting the public record is entitled to a statutory penalty."); West v. State Dep't of Natural Res., 163 Wn. App. 235, 243, 258 P.3d 78 (2011) (failure to respond within five business days); Rufin v. City of Seattle, 199 Wn. App. 348, 398 P.3d 1237 (2017) (failure to respond within five business days entitles plaintiff to seek attorneys' fees but not penalties). | |
4Smith, 100 Wn. App. at 14. | |
5Fisher Broadcasting v. City of Seattle, 180 Wn.2d 515, 326 P.3d 688 (2014). | |
6Ockerman v. King County Dep't of Dev. & Envtl. Servs., 102 Wn. App. 212, 214, 6 P.3d 1215 (2000) (agency is not required to provide a written explanation of its reasonable estimate of time when it does not provide records within five days of the request). | |
7Andrews v. Wash. State Patrol, 183 Wn. App. 644, 334 P.3d 94 (2014) (the act recognizes that agencies may need more time than initially anticipated to locate records). | |
8An exception is some state-agency employee personnel records. RCW 42.56.110. | |
9Neighborhood Alliance v. Spokane County, 172 Wn.2d 702, 261 P.3d 119 (2011); Forbes v. City of Gold Bar, 171 Wn. App. 857, 288 P.3d 384 (2012). | |
10O'Neill v. City of Shoreline, 170 Wn.2d 138, 240 P.3d 1149 (2010); Nissen v. Pierce County, 182 Wn.2d 363, 357 P.3d 45 (2015); West v. Vermillion, 196 Wn. App. 627, 384 P.3d 634 (2016). | |
11Yousoufian v. Office of Ron Sims, 168 Wn.2d 444, 229 P.3d 735 (2010); Neighborhood Alliance, 172 Wn.2d at 728. | |
12Neighborhood Alliance, 172 Wn.2d at 722. | |
13Andrews v. Wash. State Patrol, 183 Wn. App. 644 at 653; Hikel v. Lynnwood, 197 Wn. App. 366, 389 P.3d 677 (2016). | |
14The agency holding the record can also file a RCW 42.56.540 injunctive action to establish that it is not required to release the record or portion of it. An agency can also file an action under the Uniform Declaratory Judgments Act at chapter 7.24 RCW. Benton County v. Zink, 191 Wn. App. 194, 361 P.2d 283 (2015). |
Wash. Admin. Code § 44-14-04003
Statutory Authority: 2005 c 483 § 4, amending RCW 42.56.570. 07-13-058, § 44-14-04003, filed 6/15/07, effective 7/16/07. Statutory Authority: 2005 c 483 § 4, RCW 42.17.348. 06-04-079, § 44-14-04003, filed 1/31/06, effective 3/3/06.