Public records
A Practical Guide to Modernizing Public Records Request Management
A step-by-step approach for small and mid-sized municipalities to modernize public records request handling without losing control of the process.
· 8 min read · Civicade
Modernizing public records request management is less about buying software and more about making a process visible, consistent, and defensible. This guide walks through how a small or mid-sized municipality can take stock of its current process, decide what "better" means locally, and make changes in an order that protects staff time and public trust. It applies whether you eventually adopt a dedicated tool or simply tighten up the process you already have.
Why modernization matters for smaller municipalities
In many cities and towns of 10,000 to 100,000 residents, public records requests are handled by a clerk or records officer who also manages council agendas, minutes, licensing, elections support, and a long list of other duties. Requests arrive by email, through a web form, over the phone, or at the front counter. Responsive records live in several departments, on shared drives, in email accounts, and sometimes on paper.
That setup can work for years. It starts to strain when:
- Volume grows or requests become more complex (body-camera footage, large email searches, multi-department requests).
- The one person who "knows how it works" goes on leave or retires.
- A requester disputes a response and the city has to reconstruct what happened from scattered emails.
- A redaction is questioned and no one can say with confidence what was removed and why.
Modernization means reducing those risks: fewer things depending on memory, more things written down, and a clear record of who did what and when.
Start with the process, not the tool
Before evaluating any product, document how requests actually move through your organization today. Not the policy on paper — the real path.
Map the current journey
Walk through a few recent requests from start to finish. For example, a clerk might trace one simple request (a copy of a building permit), one moderate request (a week of police incident reports), and one complex request (emails between two departments over several months). For each, write down:
- How the request arrived and who first saw it.
- How the due date was calculated and where it was recorded.
- Which departments were asked for records, how, and how long they took to respond.
- Who reviewed the records, who redacted them, and with what tool.
- Whether legal counsel reviewed anything, and how that review was documented.
- How the records were delivered and how the request was closed.
Our Records Request Process Mapping Worksheet provides a printable template for this exercise.
Identify the friction points
Once the journey is mapped, look for the steps where things slow down, get lost, or depend on one person. Common patterns include:
- Intake scattered across channels. Requests come into several inboxes and some are not logged right away.
- Deadlines tracked by hand. Due dates sit in a spreadsheet or calendar, calculated manually, with holidays and pauses handled inconsistently.
- Department collection by email. The clerk sends a request to a department and then follows up repeatedly.
- Redaction with drawing tools. Black boxes are drawn over text in a PDF editor without confirming the underlying text is actually removed.
- No single history. The record of the request is split across email threads, a spreadsheet row, and a folder on a shared drive.
Define what "modernized" means for your municipality
Every jurisdiction is different. Your state's public records law, your local ordinances, your staffing, and your request volume all shape what a good process looks like. Requirements vary by state and locality, so involve your municipal counsel early and refer to your state's official guidance when defining rules.
A useful way to set goals is to write them as outcomes you can observe:
| Goal | What it looks like in practice |
|---|---|
| Every request is logged | Each request has a reference number and an owner within one business day of arrival (or whatever internal target you set) |
| Deadlines are explainable | Anyone on the team can see the due date and how it was calculated |
| Department work is tracked | Assignments to departments show who has them and whether they are complete |
| Redactions are defensible | Each redaction has a recorded reason, and the released copy no longer contains the redacted content |
| Review is documented | Legal review and release approval are recorded, not implied |
| History is complete | The full timeline of a request can be produced without searching through inboxes |
These are internal targets, not legal standards. Your counsel should confirm what your obligations actually are.
Build the foundations in the right order
Trying to change everything at once usually fails. A more reliable sequence is to fix the foundations first and add sophistication later.
1. Centralize intake
Pick one place where every request is logged, regardless of how it arrived. If a request comes in by phone or at the counter, staff log it on the requester's behalf. If you offer a public web portal, give requesters a reference number and a way to check status without calling.
- One intake log or system for all requests
- A consistent reference number format
- A defined acknowledgment step, using wording reviewed by counsel
- A way for requesters to check status
2. Make deadlines consistent and explainable
Write down how your municipality calculates response deadlines, with counsel's review: whether the period is counted in business or calendar days, when the clock starts, how holidays and closures are handled, and whether the clock can pause (for example, while waiting for a requester to clarify) or be extended. Then apply that rule the same way every time.
If you use software for this, look for rules you configure yourselves rather than rules a vendor claims to have encoded for your state, and for tools that show the calculation in plain language. Our article on request visibility and deadline tracking goes deeper.
3. Structure department collection
Turn "please send me anything you have" emails into assignments with an owner, a target date, and a clear way to respond — including a simple way to say "no responsive records." Keep internal discussions separate from messages to the requester.
4. Make redaction reliable
Redaction errors are among the most consequential mistakes in records work. A visual black box on a PDF does not necessarily remove the underlying text; it may still be selectable, searchable, or recoverable. Whatever tool you use, make sure redactions are applied permanently, that the original is preserved separately, and that each redaction is linked to a reason your counsel has approved.
5. Document review and release
Decide which requests require legal review — all of them, or only certain categories — and record the decision for each one. Record who approved the release and what exactly was released.
6. Keep a complete history
An audit trail is not about distrust; it protects staff. When a response is questioned months later, a clear timeline of who did what and when is the best defense your team has.
Common pitfalls to avoid
Buying before mapping. A tool configured around a process nobody has examined tends to reproduce the old problems in a new interface.
Assuming software handles the law. No software can guarantee compliance with public records law. Deadline rules, exemption reasons, and templates need to be reviewed and approved by your counsel. Be cautious of any product that claims to have your state's rules built in and fully correct.
Treating AI as a decision-maker. Some tools offer AI-assisted features such as suggested redactions. These can save time, but disclosure and redaction decisions are legal judgments that belong to people. See AI-Assisted Redaction: Why Human Review Must Stay in Control.
Skipping department buy-in. If department contributors find the new process harder than replying to an email, they will keep replying to email. Involve them early and keep their part simple.
Migrating everything at once. Bring open requests into the new process first; closed requests can often stay in the old system or be imported later.
No owner after launch. Someone needs to own the process: keeping calendars current each year, updating templates, and reviewing reports.
A realistic timeline
The right pace depends on your staffing and approval processes. As a hypothetical example, a city with a one- or two-person records team might plan something like this:
| Phase | Typical activities |
|---|---|
| Weeks 1–2 | Map current process, gather sample requests, list departments and contacts |
| Weeks 3–4 | Draft deadline rules and exemption reasons with counsel; agree on goals |
| Weeks 5–6 | Configure intake, templates, and roles; test with internal sample requests |
| Weeks 7–8 | Train department contributors; run a limited pilot on new requests |
| After pilot | Review what worked, adjust, and expand |
Your timeline may be shorter or longer. Counsel review and procurement approvals are often the longest steps, so start them early. A dedicated implementation checklist can help you break each phase into concrete tasks.
Where software fits
Software is a way to make a good process easier to follow, not a substitute for one. A dedicated request management tool can help by giving requests a single home, calculating deadlines consistently from rules you configure, tracking department tasks, keeping internal notes separate from requester messages, applying permanent redactions, and recording an audit trail.
CivicRecords, our public records request management product, is built around those workflows, with a public request portal, configurable deadline rules with plain-language explanations, department tasks, permanent redaction with automated verification, legal review and release approval, and an audit trail. We are preparing pilot programs with municipalities now. You can read more on the CivicRecords product page.
Whatever you choose, evaluate it against your mapped process and your own goals. Our Public Records Workflow Assessment Checklist is a good place to start.
Quick-start checklist
- Map two or three recent requests from arrival to closure
- List every channel where requests arrive today
- Write down how deadlines are calculated, and have counsel review it
- List every department that regularly holds responsive records, with a contact
- Check how redactions are applied and whether the underlying content is removed
- Decide which requests need legal review
- Identify who will own the process after any changes
- Set three to five observable goals for the next six months
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.