A small city gets the same public records requests a large one does: an email asking for correspondence, a request for a contract, a reporter asking for expense records, but usually with a fraction of the staff to handle them. Without a clear process, the request lands on whichever desk happens to be open, and the deadline clock starts running before anyone realizes it. This guide lays out a plain process a small office can actually run, day to day, without a dedicated records team.
What counts as a public record
Most state public records laws define a record broadly: any information created or received by a government agency in the course of business, regardless of format. That generally includes emails, text messages sent on city business, contracts, meeting minutes, budgets, and internal memos, not just formal documents with a letterhead or an official seal.
A few categories are commonly exempt, such as certain personnel records, active investigation files, or attorney client privileged communications, but the exemptions are narrower and more specific than most staff assume. When in doubt, treat the item as a record and check the exemption list rather than assuming it is excluded because it feels informal or internal.
Even something as ordinary as a scheduling text between two staff members can qualify if it was created in the course of city business, which is why many offices now set clear expectations about which devices and accounts employees use for that business in the first place, rather than discovering the gap only after a request arrives asking for exactly that kind of message.
Records myths worth clearing up early
A handful of assumptions cause more trouble than the actual law does. One is the belief that a draft document, because it was never finalized, is automatically exempt. In many states a draft is still a record if it was created or received in the course of business, even if it was later revised or abandoned. Another is the assumption that a personal cell phone or personal email account is automatically outside the reach of a request. If city business was actually conducted on that device or account, many states still consider the resulting message a record, regardless of who owns the device.
A third common myth is that metadata, the hidden information behind a document such as who created it, when it was last edited, or what changes were tracked, is never part of what has to be produced. Depending on your state's law and the specific request, metadata can sometimes be responsive in its own right. None of this means every draft, text, or metadata field must always be produced. It means the format or the device something lives on is not, by itself, a reliable test for whether something is a public record. Check your specific state's definition before ruling something out on the basis of format alone.
Set up an intake process that does not depend on one person
The most common failure point in a small office is a request arriving by phone, email, or in person to whoever happens to answer, with no shared record that it came in at all. If that person is out sick the day the deadline lands, the request slips through entirely, and nobody may realize it until the requester follows up, frustrated.
A workable intake process needs three things: a single point of entry, such as a dedicated email address or online form, a shared log that any authorized staff member can see, and a named backup person who can pick up a request if the primary person is unavailable. None of this requires new software or a large budget. A shared spreadsheet and a written policy on who checks it daily can carry a small office a long way.
Make sure every staff member, not just the records officer, knows what to do if a request comes to their desk directly: log it immediately and route it to the right person, rather than trying to answer it themselves on the spot or setting it aside to deal with later.
Track the clock
Most state laws set a specific deadline, or at least a requirement to acknowledge the request and provide a timeline, within a set number of business days. Know your specific state's deadline and build it into your log the moment a request comes in, not after searching for the records, since the clock in most states starts on receipt rather than on when the office gets around to reading it carefully.
If a request is broad or the records are voluminous, most states allow an extension if you notify the requester and explain why. Silence past the deadline is almost always worse, both legally and in terms of trust, than an honest update that more time is needed and a realistic new date for a response.
Build a simple internal reminder system, even a shared calendar with an entry for each open request's deadline, so a request does not quietly age past its due date while staff attention is on something more urgent that week.
Clarify scope before you start searching
Some requests arrive broad enough that searching for everything literally described would take an unreasonable amount of staff time: all emails mentioning a topic over several years, for instance, across every department. Rather than guessing at scope or refusing outright, contact the requester and ask them to narrow it, suggesting a date range or a specific department if that would help produce useful records faster.
This step protects both sides. The requester gets records faster once the scope is workable, and your office avoids spending days on a search that produces mostly irrelevant results neither side actually wanted. Document the clarification in your log just as you would the original request, since the clarified scope is now what actually defines what you are responding to, and it is worth having in writing if the scope is ever disputed later.
Be careful not to use a clarification request as a way to slow walk or discourage a legitimate request. Ask a genuine, narrow question aimed at making the search workable, not a vague request to "clarify" that puts the burden back on the requester with no real guidance about what would help.
Search every place a record could live
Once you know what is being asked for, search every location that might hold responsive records: shared drives, individual staff email if city business was conducted there, physical files, text messages if your policy allows business use of personal devices, and any relevant department's own systems, not just the records office's files.
Do not rely on one person's memory that the city does not have something. A quick check with the department that would logically hold the record, even if you are fairly confident it does not exist, takes a few minutes and prevents a far more damaging situation later: telling a requester no responsive records exist, only to have the record surface anyway during a dispute or a subsequent request.
If the request touches a contracted vendor or a service the city has outsourced, such as a third party managing utility billing or a shared regional dispatch center, check whether records held by that vendor on the city's behalf are covered by your state's law, since many states extend records obligations to a private contractor performing government functions.
Review and redact before release
Before release, review each document for anything that falls under a specific legal exemption, such as personal identifying information, and redact only what the law actually allows you to withhold. Over redacting invites a challenge just as under redacting creates liability, so when a redaction call is unclear, loop in your city attorney rather than guessing under time pressure.
Work document by document rather than applying a blanket rule across an entire batch, since the same category of information, a name, an address, a financial detail, is not always exempt in every context. A resident's address might be routine in one record and legitimately sensitive in another, depending on what the record is actually about.
Keep your redaction method consistent and documented, whether that is a permanent redaction on a printed copy or a properly flattened digital redaction, since an improperly applied digital redaction can sometimes still be reversed by the recipient, which defeats the purpose entirely.
Handle exemptions and denials carefully
If part or all of a request is denied, cite the specific legal exemption that applies, not a general statement that the records are confidential. A requester is entitled to know exactly why something was withheld, and a vague denial is more likely to trigger an appeal or a complaint than a specific, well grounded one.
Keep a copy of what was withheld and the specific reason, separate from what was released, so you can defend the decision later if it is questioned by the requester, a reviewing body, or a court. The standard practice when a record is only partly exempt is to redact the specific exempt portion and release the rest, rather than withholding the entire document because part of it is sensitive.
Fees, cost estimates, and what you can reasonably charge
Many states allow a reasonable fee for costs like copying or extensive staff time spent searching and redacting a large request, but the rules on what can be charged, and how it must be calculated and disclosed, vary significantly by state. Check your specific state's law before setting a fee, and be prepared to explain exactly how any charge was calculated if asked.
If a fee estimate is going to be substantial, provide it to the requester before doing the work, not as a surprise attached to the finished response. Many states require this kind of advance notice for large requests, and even where it is not strictly required, it avoids a dispute after the fact about a bill nobody expected. A requester who is given a fair estimate up front can decide whether to narrow the request, which often serves everyone's interests better than an unexpectedly large invoice.
Requests that touch other offices or vendors
Not every request stays neatly inside city hall. A request touching a joint powers authority, a regional dispatch center, or a service shared with a neighboring city may require coordinating with another office's records officer to identify who actually holds the responsive records and who is legally responsible for producing them.
Similarly, records held by an outside vendor performing a government function on the city's behalf, an IT provider hosting city email, a contracted engineering firm working on a capital project, may still be within scope depending on your state's law and the terms of the underlying contract. Build a habit of asking, early in a request that seems to touch outside parties, exactly where the responsive records actually live before promising a response date you may not be able to meet on your own.
Common bottlenecks in a small office
A few patterns show up repeatedly in small offices: no backup person when the records officer is out, requests scattered across email inboxes with no shared log, uncertainty about whether a text message or personal email counts as a record, and last minute searching when a deadline is close and everyone realizes at once how much work remains.
A records officer who personally reviews every request, even routine ones a trained staff member could handle without escalation, creates a bottleneck that has nothing to do with the law and everything to do with how the office assigned the work. Each of these is fixable with process, not necessarily more staff: a shared log, a clear written policy on what counts as a record, and a habit of starting the search the same day a request arrives rather than waiting for a quiet afternoon that may not come.
Keep a log that protects your office later
Track every request: when it arrived, what was asked for, what was searched, what was released or withheld and why, any fee charged, and when it was closed. This log does more than track deadlines. It is your evidence, if a decision is ever questioned later, that the process was followed in good faith and applied consistently across similar requests.
A well kept log also reveals patterns over time, such as a records category that comes up often enough to justify proactively posting it online, which reduces the number of requests your office has to handle one at a time going forward. Review the log itself every few months, not just when a request is active. Patterns that are invisible request by request, a department that consistently generates records slowly, a category that keeps triggering the same clarifying question, become obvious once you look at a quarter's worth of entries side by side.
Building a proactive disclosure habit
The single most effective way to reduce the workload of individual records requests is to publish commonly requested records before anyone has to ask. Meeting minutes, adopted budgets, contracts above a routine threshold, and salary schedules are frequently requested items in most cities, and posting them on a regular schedule turns a recurring request into a non event.
This does not eliminate the need for a records process, since specific and unusual requests will always come in, but it does shrink the volume of routine requests your office has to individually log, search, and respond to. Start with whatever category shows up most often in your own log, since that is the clearest signal of what your particular community actually wants access to, rather than guessing at what transparency should look like in the abstract.
Records retention schedules and how they interact with requests
A records request only produces what your city still has, which makes your retention schedule just as important to the process as your intake log. Most states set minimum retention periods for different categories of records, and destroying something before its scheduled retention period ends, even by accident, can turn a routine request into a serious compliance problem. Before responding that a record does not exist, confirm it was not simply destroyed on schedule, and be ready to explain that distinction clearly to the requester.
If a request arrives for records that fall within an active litigation hold or a known dispute, pause any routine destruction that would otherwise apply under the schedule, and check with your city attorney before anything in that category is disposed of. Keeping your retention schedule current, and actually followed in practice rather than just filed away, is one of the more overlooked pieces of a records program that otherwise looks solid on paper.
Working with your city attorney on harder requests
Most public records requests are routine and do not need legal review, and treating every one of them as a legal question slows the office down without adding real protection. Reserve that review for the requests that genuinely call for it: a request touching pending or anticipated litigation, one that raises a genuinely unclear exemption question, or one from a requester who has indicated they intend to challenge the response.
When you do bring a request to your city attorney, come with the specific question rather than the entire file: which exemption might apply to which specific document, or whether a particular category of communication is covered at all. A focused question gets a faster, more useful answer than handing over the whole request and asking generally whether anything looks like a problem. Over time, keep a simple internal note of how similar questions were resolved before, so your office is not asking the same foundational question fresh every time a similar request comes in.
A quick reference for a first request
A new staff member handling their first request benefits from a short, concrete reference rather than the full policy manual. At minimum: log the request the moment it arrives, note the deadline based on your state's law, search every plausible location rather than just the obvious one, flag anything uncertain to a supervisor or the records officer rather than guessing, and close the loop with the requester even if the answer is that no responsive records exist.
That kind of simple, repeatable routine, more than any single rule about exemptions or fees, is what actually keeps a small office's records program running smoothly day to day.
What to expect if a response is disputed
Occasionally a requester disagrees with how a request was handled, whether that is the scope of a search, a fee charged, or a specific redaction. Most states provide a formal path for this, sometimes through a state attorney general or a similar oversight office, sometimes only through a court, and knowing which applies in your state before a dispute arises makes the actual moment far less stressful.
If a requester raises a concern informally first, before filing any formal appeal, treat it as a chance to explain the reasoning behind a decision rather than a challenge to be managed defensively. A clear, specific explanation, this portion was withheld under this particular exemption, this search covered these locations, resolves a surprising number of disputes before they ever become formal. When a dispute does escalate, your log becomes the primary evidence of what your office actually did, which is exactly why keeping it complete and contemporaneous matters more than it might seem to in the middle of a routine week.
Building confidence without a legal background
Most clerks and records staff are not attorneys, and the law in this area can feel more intimidating than it needs to be for the great majority of requests, which are routine and do not raise any genuinely close legal question. Build general familiarity with your own state's public records law, its deadlines, its common exemptions, and its fee rules, so the routine cases can move quickly without needing legal review every time.
Save that legal review for the requests that actually call for judgment: a genuinely ambiguous exemption, a request tied to active litigation, or a pattern of requests from the same person that raises questions your written policy does not clearly answer. Knowing the difference between a routine request and one that needs a second opinion is, in practice, the single most valuable skill a records officer in a small office can develop.
