Civicade

Worksheet · About 45 minutes per request

Records Request Process Mapping Worksheet

A printable worksheet for tracing one public records request from arrival to closure, so you can see handoffs, delays and gaps in your current process.

Free to print and share within your organisation.

How to use this

This worksheet helps you trace how one public records request actually moved through your organization, step by step. Mapping a real request reveals handoffs, delays and gaps that are easy to miss in a policy document.

  1. Choose a recent, closed request. Mapping three requests (one simple, one moderate, one complex) gives the fullest picture; use a separate copy for each.
  2. Gather what you have: the original request, emails, your log or spreadsheet entry, department replies, and the released records.
  3. Fill in each section. Use dates where you can find them; estimate where you can't, and mark estimates with "~".
  4. Remove or abbreviate requester names and other personal information on this sheet.
  5. Review the completed worksheet with your team and note improvement ideas at the end.

This worksheet describes your current practice. It does not assess legal compliance. Questions about deadlines, exemptions or review requirements should go to your municipal counsel.

Completed by: ______________________ Date: ____________

1. About the request

Field Your answer
Internal reference
Request type (simple / moderate / complex)
Short description (no personal information)
Category
Date and time received
Channel (email, web form, phone, mail, counter, other)
Date closed
Outcome (released in full / in part / no records / withdrawn / other)

2. Step-by-step journey

List every step from arrival to closure, in order. Include waiting periods as their own steps (for example, "Waiting for Police to respond").

# Step Who did it (role) Tool used Date started Date finished Notes or problems
1
2
3
4
5
6
7
8
9
10
11
12

Prompts if you are stuck:

  • Who first saw the request, and how did it reach the person who handled it?
  • When was it acknowledged, and how?
  • When and how were departments asked for records?
  • Did anyone ask the requester for clarification?
  • Who reviewed and redacted the records? Did counsel review them?
  • Who approved the release, and how were records delivered?

3. Deadline

Question Your answer
What was the due date?
Who calculated it, and how?
Where was it recorded?
Business days or calendar days?
Did any holidays or closures fall in the period?
Was the clock paused? Dates and reason
Was there an extension? Length, reason, who approved
Was the due date updated after a pause, extension or closure?
Was the request completed by the due date?
Could a colleague have explained the due date to the requester?

4. Department involvement

Department Contact Date asked How asked Date responded How records were sent Follow-ups needed
  • Every department that held records was identified early
  • Each department knew what was needed and by when
  • "No responsive records" answers were recorded

5. Communication with the requester

Date Direction (to / from requester) Purpose Channel Template used? (Y / N)
  • All messages are stored in one place with the request
  • No internal discussion was sent to the requester by mistake
  • The requester could find out the status without contacting staff

6. Documents, redaction and review

Question Your answer
How many documents or pages were gathered? (approximate)
Where were they stored while being worked on?
Were duplicates gathered?
What tool was used to redact?
How was the redaction checked before release?
Was each redaction linked to an exemption reason?
Did legal counsel review? How was the decision recorded?
Who approved the release?
How were records delivered?

7. Time and effort

Measure Your answer
Total calendar days from receipt to closure
Days spent waiting on departments
Days spent waiting on the requester
Days spent in review
Estimated staff hours across all people involved
Number of people who touched the request
Number of tools or systems used

8. Friction points

Mark each step from Section 2 that caused a delay, duplicate effort, confusion or risk.

Step # What went wrong or slowed down Why it happened Impact (time / risk / requester experience)

Common friction points to look for:

  • Request sat in an inbox before anyone owned it
  • Due date was unclear, unrecorded or not updated
  • Departments needed several reminders
  • Records arrived in several formats or locations
  • Requester follow-ups were separated from the original request
  • Redaction had to be redone or was uncertain
  • Review or approval was informal or unrecorded
  • Only one person knew the status

9. Improvement ideas

Idea Which friction point it addresses Effort (low / medium / high) Needs counsel? (Y / N) Owner

Reflection questions

Write a few sentences for each.

If the main person who handled this request had been out, what would have happened?



If the requester disputed the response six months later, how quickly could we reconstruct what happened?



Which single change would have saved the most time on this request?



Next steps

Once you have mapped a few requests, use the Public Records Workflow Assessment Checklist to look at your process as a whole. If you are moving away from an email-based process, From Shared Inboxes to a Trackable Public Records Workflow covers the transition step by step.

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