A records request passes through five people. Only one of them is the clerk.
Someone asks the city for a set of emails and inspection reports. Behind that one request sit a clerk, a couple of departments, a lawyer, a deadline in law and, very often, a shared inbox holding the whole thing together.
Public records requests involve more people than the intake form suggests: the requester, the records officer who logs it, the departments that hold the records, the reviewer who redacts, and whoever releases and closes it. Tracking only the intake leaves everything else in email. Give each request one record with its legal clock, a named owner for every step, a place for departments to upload what they find, a log of redactions and reasons, and plain status updates for the requester. Federal FOIA covers federal agencies; state and local requests follow each state's own law.
One request, five people
A resident emails the city. She wants the inspection reports for a building on her street, plus any emails between the building department and the owner over the past year. To her it's one question. Inside the city it becomes a small project with a cast.
The request in this note is a composite, but the cast will be familiar to anyone who has handled one. First the requester, then the records officer or clerk who logs it, then the departments that actually hold the records, then whoever reviews them for things that can't be released, and finally the person who sends them out and closes the request. Each has a different job, a different deadline in their head, and usually a different tool.
There's also a clock. In the US the federal Freedom of Information Act covers federal agencies only. State and local governments follow their own state's public records law, each with its own response times, fees, exemptions and appeal routes. So whatever you build has to take its deadlines from your law, not from a template.
When requests go wrong, it's rarely because one person did their job badly. The request isn't stuck with the clerk. It's stuck between people. So let's meet them one at a time.
How the work moves
One request, five hands
- Requester
Asks, gets a reference and an expected date.
- Records officer
Logs, clarifies scope, starts the clock, assigns departments.
- Departments
Search, upload what they find or confirm there's nothing.
- Reviewer
Redacts, applies exemptions, logs the reasons.
- Release
Fees, files, what was withheld and how to appeal; request closed.
The requester
She wants three things, and only one of them is the records. She wants to know her request arrived. She wants a realistic idea of when she'll hear back. And when that date moves, she wants to be told before she has to ask.
Most of the follow-up calls a records office gets are about the second and third. A confirmation with a reference number, an expected date and a way to check status removes a surprising amount of that. Our note on where-is-my-application calls makes the same point for permits and benefits.
She may also be happy with part of the answer sooner. If the inspection reports are easy and the emails need review, she'd probably rather have the reports now. That only works if the system can release in pieces.
The request isn't stuck with the clerk. It's stuck between people.
The records officer
The clerk or records officer is the one everybody sees, and the one who gets the blame when things are slow. Their real job is coordination: log the request, clarify it with the requester if it's vague, decide which departments to ask, start the clock and chase.
Clarifying matters more than it looks. "All emails about the building" might mean a few dozen messages or several thousand, depending on the search terms and date range. A short conversation at the start can save weeks later, and the record should show what was agreed.
Requests also arrive from everywhere. A web form, an email to the general inbox, a letter, a phone call, someone at the counter, an email sent directly to the department head. Each channel tends to have its own little list. The first job of any system here is to make sure every request, however it came in, ends up in the same place with the same reference number and the same clock. Otherwise the deadline starts on the day a letter arrived and the clerk learns about it a week later.
Chasing is where the time goes. In most offices it's done by email and memory: a spreadsheet of open requests, a folder per request, and reminders set by hand. When the records officer is out for a week, the chasing stops.
The departments holding the records
The building department didn't ask to be part of this. Records requests arrive as an interruption to their actual work, often as a forwarded email with no due date that anyone in the department can see.
What they need is simple: a clear description of what's being asked, the date they need to respond by, a place to put what they found (or a way to say they found nothing), and someone to ask if they're unsure. What they shouldn't have to do is reply-all with attachments, because then the records exist in five inboxes and nobody's sure which set is final.
If you only fix one thing, fix this handoff. Give departments a task with a due date and an upload, and let the system do the reminding instead of the clerk.
The reviewer, and the person who sends it out
Before anything goes out, someone has to check it: personal information, things exempt under your law, material that belongs to another agency. In a small city that's often the city attorney's office, squeezed between other work.
Two things help the reviewer. Seeing everything for one request in one place, rather than across email threads, and a log of what was withheld or redacted and why. That log matters later if the requester appeals, and it's much easier to write as you go than to rebuild afterwards.
Then someone releases the records: works out any fees, sends the files, tells the requester what was withheld and how to appeal, and closes the request. It sounds administrative, and it is, but it's the moment the requester judges the whole process. A clear closing message with everything in one place lands very differently from a bare link.
Decision guide
Where the request lives
| Consideration | In the inbox | On one record |
|---|---|---|
| Deadline | In the clerk's spreadsheet. | Calculated from your law, visible to everyone. |
| Department tasks | Forwarded emails, no due date. | Assigned steps with due dates and reminders. |
| Records | Attachments across several inboxes. | Uploaded once, reviewed in place. |
| Redactions | Reconstructed if someone appeals. | Logged with reasons during review. |
| Requester updates | When they call. | Plain status online; partial releases where possible. |
Put the cast on one record
The fix is to stop tracking the request and start tracking the work. Each request gets one record that everybody can see, and on it:
- The clock, calculated from your law, with any agreed extensions and the reason.
- An owner for every step, so departments see their part and their due date.
- One place for records, uploaded by departments, reviewed and marked there.
- A redaction and exemption log, written during review.
- Status the requester can see, in plain words, with partial releases where possible.
Once requests live on one record, the office also learns something it couldn't see before: where the time actually goes. Which departments take longest to respond, which kinds of request need legal review, how often scope gets narrowed after a conversation. That's what you need when you ask for more staff, or decide that some records should simply be published proactively so nobody has to request them.
None of this needs an enormous system. Many offices start with a public intake form, a shared case record and automatic reminders, and that already takes most of the chasing off the clerk. If your office still runs on a PDF form, putting the PDF online isn't the same as putting the service online.
We work with public-sector teams on intake, case handling and the systems behind them, and on the workflow automation that keeps requests moving between departments. If your records requests live in one person's inbox, we'd be glad to map them with you.
Related work: Wellthie.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.