Civicade

Checklist · About 30 minutes

Public Records Workflow Assessment Checklist

A printable checklist to assess how your municipality receives, tracks, collects, redacts, reviews and releases public records requests today.

Free to print and share within your organisation.

How to use this

This checklist helps you take an honest look at how your municipality handles public records requests today. It is not a compliance test and it does not reflect any state's legal requirements, which vary by state and locality. Use it to spot gaps and decide where to focus.

  1. Print this page or copy it into a document.
  2. Work through it with the person who handles most requests, ideally with one recent request in front of you.
  3. Check each item that is true today. Leave it blank if it isn't, or if you aren't sure.
  4. Use the notes lines to record who owns a gap or what you would change.
  5. Review the unchecked items with your team, and with your municipal counsel for anything involving deadlines, exemptions or legal review.

Assessment completed by: ______________________ Date: ____________

1. Intake

  • We know every channel through which requests arrive (email, web form, phone, mail, counter)
  • Every request is logged in one place, whatever channel it came through
  • Requests received by phone or in person are logged by staff on the requester's behalf
  • Each request gets a unique reference number
  • Requesters receive an acknowledgment, using wording reviewed by counsel
  • Requesters can find out the status of their request without calling or emailing staff
  • Our website explains how to submit a request and what to expect
  • We point requesters to records that are already published online, where that applies

Notes: ____________________________________________________________

2. Ownership and visibility

  • Every open request has one named owner
  • Anyone on the team can see all open requests in one view
  • Each request has a current status that describes the next step
  • Someone is assigned to cover requests when the owner is absent
  • We can tell at a glance which requests are waiting on a department, the requester, or legal review
  • We could produce a list of all open requests within a few minutes if asked

Notes: ____________________________________________________________

3. Deadlines

  • Our deadline rules are written down
  • Our written rules have been reviewed by municipal counsel
  • We know whether our response period is counted in business or calendar days
  • We know when the clock starts and how after-hours or weekend receipts are handled
  • We keep a current calendar of holidays and office closures
  • We record how each request's due date was calculated
  • Pauses (for example, awaiting clarification) are recorded with dates and reasons, where counsel says they are permitted
  • Extensions are recorded with a reason and the name of the person who approved them
  • Due dates are recalculated when a pause, extension or closure changes them
  • Staff get reminders before deadlines, not on the day
  • Someone with authority is alerted when a request becomes overdue
  • When our rules change, we know how requests already in progress are affected

Notes: ____________________________________________________________

4. Department collection

  • We have a current list of departments and a records contact in each
  • Requests to departments state what is needed and by when
  • We can see which departments have responded and which have not
  • Departments have a simple way to say "no responsive records"
  • Department responses are stored with the request, not scattered across email
  • Department contributors can see only the requests relevant to them

Notes: ____________________________________________________________

5. Communication

  • Internal discussion is kept separate from messages to requesters
  • We use templates for common messages (acknowledgment, clarification, fees, release)
  • Our templates have been reviewed by counsel
  • All messages to and from the requester are kept with the request
  • Clarification requests to requesters are clear about what we need and why

Notes: ____________________________________________________________

  • Responsive documents are stored in one place per request
  • Original documents are preserved and kept separate from redacted copies
  • Uploaded files are checked (file type, size, malware scanning) before staff open them
  • Text in documents, including scanned documents, can be searched
  • We can tell when the same file has been gathered more than once
  • Access to unredacted originals is limited to staff who need it

Notes: ____________________________________________________________

7. Redaction

  • Redactions permanently remove the underlying content, not just cover it
  • We check that redacted text cannot be selected, searched or copied in the released copy
  • Document metadata is reviewed or removed before release
  • Each redaction is linked to an exemption reason approved by counsel
  • Staff who redact have had training on our exemption reasons
  • We have a process for file types our tools cannot redact
  • If we use any automated or AI-assisted suggestions, a person reviews every page and accepts each redaction

Notes: ____________________________________________________________

8. Review and release

  • We have decided which requests need legal review
  • Legal review decisions are recorded, including requests for changes
  • Release is approved by an authorized person, and that approval is recorded
  • We know exactly which version of each document was released
  • Records are delivered securely to the requester
  • Partial releases and withholdings are explained to the requester using reviewed wording

Notes: ____________________________________________________________

9. Audit and reporting

  • We can reconstruct the full history of any request without searching inboxes
  • The history shows who did what and when
  • The history cannot be quietly edited after the fact
  • We can report on open, overdue and closed requests
  • We review workload and turnaround at least monthly
  • We can export request data if needed

Notes: ____________________________________________________________

10. Security and continuity

  • Each staff member has their own account (no shared logins)
  • Two-step verification is used for systems that hold request data
  • Access is removed promptly when staff leave or change roles
  • Requester personal information is visible only to staff who need it
  • More than one person knows how the process works
  • Our process is documented well enough that a new staff member could follow it

Notes: ____________________________________________________________

Reading your results

Count the unchecked items in each section and write the totals below. There is no passing score. The goal is to see where gaps cluster.

Section Unchecked items Priority (high / medium / low) Owner
1. Intake
2. Ownership and visibility
3. Deadlines
4. Department collection
5. Communication
6. Documents and search
7. Redaction
8. Review and release
9. Audit and reporting
10. Security and continuity

Gaps in deadlines, redaction and review are usually worth addressing first, because errors there are hardest to undo. Bring those items to your municipal counsel.

Next steps

From Civicade · General guidance, not legal advice. More resources