My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Resolution 7026
>
Resolutions
>
Resolution 7026
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/21/2016 9:24:32 AM
Creation date
9/21/2016 9:24:28 AM
Metadata
Fields
Template:
Resolutions
Resolution Number
7026
Date
9/7/2016
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
• An initial response may propose fulfilling large or complicated requests on an installment <br /> basis and provide an estimated time frame for preparation of the first installment. <br /> • An initial response may be a written denial of the request based on exemptions under <br /> Washington State Law. <br /> Records Liaisons must respond to the Public Records Officer within two (2) business days <br /> as to whether the records can be provided within five (5) business days or provide an estimated <br /> date for fulfillment if to exceed five (5) business days. <br /> Records liaisons shall advise department record holders of the five-day response deadline when <br /> forwarding records requests and consult with record holders when estimating the fulfillment <br /> date. <br /> 4.8 Locating Responsive Records <br /> Staff shall make a reasonable effort to identify and locate any and all responsive records. When <br /> identifying records, the Records Liaison or Public Records Officer may ask the requestor for <br /> clarification or refinement of the request. Such clarifications may be verbal or in writing. In the <br /> case of verbal clarifications, staff involved in the conversation shall document the clarification in <br /> writing and include the information in the request file. Staff shall not conclude that a request is <br /> overly broad or does not adequately identify the records requested without attempting to obtain <br /> clarification from the requestor. <br /> Records Liaisons and staff are not required to create new records in response to a request for <br /> public records, but shall when deemed feasible, tailor existing informational databases or indexes <br /> to provide a report responsive to a request that otherwise would not be produced in the normal <br /> course of business. The determination of the feasibility of creating such reports shall take into <br /> account the ability to redact or withhold exempt information. When the production of a tailored <br /> report requires additional resources such as customized programming or fact-specific analysis, or <br /> would otherwise interfere with other essential functions, the City is not required to produce such <br /> tailored reports but should instead consult with the requestor. <br /> The City is only required to provide records that exist at the time a request is made — the City <br /> cannot fulfill "standing" requests or requests for records that may be created at a future date. <br /> Fulfillment of requests shall be processed in the order that provides the timeliest response. <br /> Requests may be fulfilled in the order of receipt as long as easily fulfilled requests are not <br /> postponed behind larger or more complicated requests strictly because they were received later. <br /> 4.9 Immediate Provision or Inspection of Records "Over the Counter" <br /> Staff may respond immediately to verbal requests for records without the need for completion of <br /> a written request, entry into a request log, or a written response by the City when all of the <br /> following conditions exist: <br /> • The records requested are easily accessible to staff; <br /> • The requested records do not contain lists of individuals; <br /> 10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.