Public records
From Shared Inboxes to a Trackable Public Records Workflow
How municipal records teams can move from a shared email inbox to a workflow where every request has an owner, a status, and a clear history.
· 7 min read · Civicade
A shared inbox is often where public records work begins, and for good reason: it is free, familiar, and easy to set up. But as requests multiply, an inbox makes it hard to see who owns what, what is due, and what was said to whom. This article explains how to move from a shared inbox to a trackable workflow step by step, without interrupting service to the public.
Why the shared inbox stops working
A shared mailbox such as records@ or clerk@ is a reasonable starting point. Everyone on the team can see incoming requests, and replying is as easy as answering any other email. The trouble is that email was designed for conversations, not for tracking work with deadlines, handoffs, and approvals.
Consider a hypothetical week in a city clerk's office. A request for code enforcement complaints arrives on Monday. A colleague reads it, flags it, and plans to forward it to the department after lunch. On Tuesday the requester sends a follow-up with a narrower date range, which lands in a different thread. On Wednesday the department replies to the original forward with a link to a shared folder. By Friday, two people believe the other is handling the request, the narrowed scope is buried, and nobody has written down when the response is due.
None of these are failures of effort. They are what happens when a tool built for messages is asked to carry a process.
Signs your team has outgrown the inbox
- Staff ask each other "is anyone handling this?" more than occasionally
- Due dates live in someone's head, a personal calendar, or a spreadsheet that is updated after the fact
- Follow-ups from requesters start new threads that get separated from the original request
- Department responses arrive as attachments or links scattered across replies
- Internal discussion and requester-facing messages are mixed in the same threads
- Reconstructing the history of a request means searching several mailboxes
- Coverage during vacations depends on forwarding rules and good luck
If several of these sound familiar, the inbox is costing your team more than it saves.
What a trackable workflow looks like
A trackable workflow does not have to be complicated. At minimum, every request should have five things.
| Element | Why it matters |
|---|---|
| A unique reference | Everyone, including the requester, can refer to the same request without confusion |
| An owner | One named person is responsible for moving it forward, even when others help |
| A status | Anyone can see at a glance where it stands: new, in progress, awaiting clarification, in review, ready for release, closed |
| A due date with its basis | The deadline is recorded along with how it was calculated |
| A single history | Messages, notes, files, and decisions are kept together in one timeline |
Beyond those basics, a mature workflow typically adds department assignments with their own status, a clear separation between internal notes and requester messages, reusable message templates, and a documented review and release step.
Making the transition, step by step
You do not have to switch everything over on a single day. A staged transition is easier on staff and lowers the risk of losing a request in the gap.
Step 1: Write down your current statuses
Before changing tools, agree on the stages a request moves through. Many teams find something like this works:
- Received
- Acknowledged
- Collecting records
- Awaiting requester clarification
- Reviewing and redacting
- In legal review (if applicable)
- Ready for release
- Released / closed
Keep the list short. Each status should answer one question: "what has to happen next, and who does it?"
Step 2: Define ownership rules
Decide how requests are assigned. A small office might have one person triage everything each morning. A larger one might route by category, for example sending police records requests to a records specialist familiar with them. Write down who owns a request when the main assignee is out.
Step 3: Start logging every request in one place
Even before adopting new software, you can begin logging every incoming request in a single list with the five core elements above. This creates the habit and quickly reveals gaps. Requests that arrive by phone or at the counter should be logged the same way, on the requester's behalf.
Step 4: Separate internal notes from requester communication
One of the most valuable changes is making it structurally hard to send internal discussion to a requester by accident. In email, a "reply all" on the wrong thread can expose an internal comment. In a dedicated workflow tool, internal notes and requester messages should be clearly different actions.
Step 5: Standardize recurring messages
Acknowledgments, clarification requests, fee notices, and release messages tend to follow patterns. Turn them into templates and have your counsel review the wording. Templates save time and keep communications consistent, but staff should still read and adjust each message before sending.
Step 6: Move department requests out of email threads
Instead of forwarding the requester's email to a department, create a specific assignment: what is needed, by when, and how to respond. Make "we have no responsive records" an easy, recorded answer — it is a common outcome and should not require a long email.
Step 7: Bring open requests across, then switch intake
When you adopt a new system, start by moving open requests into it, keeping their original received dates so deadlines stay accurate. Then switch intake: update your website, the auto-reply on the shared inbox, and any printed materials to point to the new channel. Keep the shared inbox monitored for a while, since some requesters will keep using it. Staff can log those requests into the new workflow.
Keeping the requester in the loop
A trackable workflow helps requesters too. When requests have a reference and a status, staff can answer "where is my request?" quickly, and some systems let requesters check status themselves.
Common approaches include:
- A confirmation message with a reference number as soon as a request is logged.
- A private tracking link, so requesters can check status without creating an account.
- Plain-language explanations of the due date and what happens if the clock pauses while the team waits for a clarification.
- Notifications when records are ready.
Whatever you choose, make sure the information shown to requesters is accurate and reviewed. A status page that is out of date causes more confusion than none at all.
Pitfalls during the transition
Running two systems indefinitely. Overlap is fine for a short period. If the shared inbox and the new workflow both remain "official" for months, requests will fall between them. Set a cutover date.
Over-engineering statuses. A workflow with fifteen statuses that nobody understands is worse than six that everyone uses correctly.
Losing history. When moving open requests, bring their key history along — at least the original request, received date, and any clarifications — so that deadlines and decisions remain traceable.
Leaving departments out. If departments are expected to respond in a new way, explain why and show them how. Keep their part as simple as possible.
Forgetting the auto-reply. The shared inbox auto-reply is often the first thing requesters see. Update it to explain the new process and where to submit.
Assuming the tool settles legal questions. A workflow tool helps you follow your process; it does not determine your legal obligations. Response periods, pause and extension rules, and exemptions need to come from your state's law as interpreted by your counsel.
Measuring whether it is working
A few simple measures will tell you whether the new workflow is helping. These are internal indicators for your team, not benchmarks:
- How many open requests have no owner? (Ideally none.)
- How many open requests have no recorded due date?
- How many requests are past their internal target dates, and why?
- How long do department assignments typically take?
- How often do staff have to search email to answer a requester's question?
Review these monthly for the first few months. Most workflow tools, including spreadsheets, can produce them with a little setup; dedicated tools usually include reports and CSV export.
How CivicRecords approaches this
CivicRecords was designed around the move from inbox to workflow. Requests submitted through its public portal receive a reference number and a private tracking link. Staff can log requests received by phone, mail, or in person. Each request has an owner, a status, and a deadline calculated from rules your municipality configures. Department assignments are tracked as tasks, internal notes are kept separate from requester messages, and message templates can be adapted to your counsel's wording. Every step is recorded in the request timeline and audit trail.
CivicRecords does not currently read email directly; requests that arrive in the shared inbox are logged by staff. Spreadsheet import is available for bringing over open requests. You can see how the pieces fit together on the platform overview or the CivicRecords product page.
A transition checklist
- Agree on a short list of statuses
- Define who owns requests and who covers absences
- Log every request in one place, regardless of channel
- Separate internal notes from requester messages
- Draft message templates and have counsel review them
- Replace forwarded emails to departments with clear assignments
- Move open requests with their original received dates
- Update the website, auto-reply, and printed materials
- Set a cutover date for the shared inbox as an official channel
- Review simple workflow measures monthly
For a structured look at where your current process stands, try our Public Records Workflow Assessment Checklist. You may also find it helpful to read A Practical Guide to Modernizing Public Records Request Management.
This article is general information, not legal advice. Public records requirements vary by state and locality. Confirm your obligations with your municipal counsel and official state guidance.