How to Process a Public Records Request: A Clerk's Workflow and Tracking System (2026)

Every clerk's office has a version of the same bad afternoon: a records request that arrived three weeks ago surfaces in an email thread nobody flagged, the statutory clock ran out somewhere around day eleven, and now the question is not what the records say but why the agency never responded.

The work of a public records request is rarely difficult. The tracking is what fails. This is the workflow and the log structure that keeps a small clerk's office defensible, written for the people who actually run it.

Quick answer: process every public records request through six fixed stages: log it on the day it arrives, clarify the scope in writing, direct a documented search to every custodian, issue a written determination within your statutory window (10 days in California), redact under a cited exemption rather than withholding whole records, then release and close the request in a log that records dates, exemptions, and volume. The log, not the response, is what proves compliance a year later.

---

The distinction that causes most violations

The single most common failure in a small agency is not refusing to produce records. It is misreading the clock.

In California, Government Code section 7922.535 gives an agency 10 days from receipt to determine whether it holds disclosable records and to notify the requester of that determination and the reasons for it. If the answer is yes, the agency must also state the estimated date and time the records will be available.

Read that again, because it is the whole ballgame: the 10 days is a deadline to respond, not a deadline to produce. A clerk who sits on a large request for 10 days assembling documents has already missed the deadline, even if the records go out on day 12. A clerk who sends a short determination letter on day 4 that says "yes, we have responsive records, and we estimate producing them on October 3" is compliant, even if the production is genuinely weeks away.

Most state statutes draw the same line between acknowledging and producing, with different numbers attached. Find your number, write it on the wall, and build the workflow around the determination rather than the delivery.

---

The intake log

Everything else in this article is process. This is the artifact. If your office keeps nothing else, keep this.

Field	Why it exists
Request number	Gives staff, counsel, and the requester one shared reference
Date received	Starts the statutory clock, and is the fact most often disputed later
Channel	Email, portal, counter, mail, phone, or a comment made at a meeting
Requester name and contact	Needed for the determination and any clarification
Verbatim request text	Paraphrasing the request is how scope disputes begin
Departments searched	Demonstrates the search was reasonable and complete
Custodian responses	Including written "no responsive records" replies
Determination date and content	Proves the 10-day obligation was met
Extension taken, and the stated basis	An extension with no documented ground is worse than none
Exemptions applied, with citation	Per document or per category, never a blanket label
Release date and format	Matches what the requester asked for where you hold it that way
Volume released	Page or file count, useful for both defense and workload data
Fees quoted, charged, collected	Apply the published schedule identically to everyone
Closure date	Turns an open-ended obligation into a completed one

A spreadsheet with these columns is genuinely sufficient for a small city. Purpose built request portals are excellent and worth budgeting for, but the failure mode in a two-person clerk's office is almost never the software. It is that a request arrived as a reply inside an unrelated email thread and nobody logged it.

One rule makes the whole system work: a request is not received by the agency until it is in the log, and it is the receiving employee's job to put it there the same day. Publish that expectation to every department, not just to the clerk's office, because requests do not politely arrive only at your counter.

---

Handling the request that is not really a request

Three shapes come in constantly and none of them are records requests in the statutory sense:

Questions. "How much did the city spend on the park project?" is a question, not an identifiable record. You are not obligated to answer it, and you are not obligated to build a report that answers it. You are obligated to help the requester identify records that might contain the answer, which in this case is probably a set of invoices and a budget line. Answer helpfully, in writing, and log it.

Prospective requests. "Please send me every agenda from now on." A public records request reaches records that exist when it is made. Explain that, then offer the notification subscription, which is almost always what the person actually wanted.

Overbroad requests. "All emails about housing." Do not simply refuse. In most states you have a duty to assist the requester in focusing the request, and a documented, friendly attempt to narrow the scope is both good service and excellent evidence if the matter is ever litigated. Suggest a date range, named custodians, and search terms, and put the suggestion in writing.

The through line: do the clarification in email, never only by phone. The exchange becomes part of the file at no extra cost.

---

The search

The weakest link in most agencies is not the clerk. It is the department that searched one shared drive, found nothing, and said so verbally.

Send a written search directive to every custodian who might reasonably hold responsive records. It should state the request number, the verbatim request, the date range, the specific locations to search (email, shared drives, personal devices used for agency business, text messages, and any department specific systems), and a firm internal deadline several days ahead of your statutory one.

Then require a written response either way. A custodian's "no responsive records" email is a record you will want.

Text messages and personal accounts deserve their own sentence, because they are where agencies lose these cases. In most states, a record about the public's business is subject to disclosure based on its content, not on which device or account it happens to live in. Tell council members and staff this once a year, in writing, before a request makes the point for you.

---

Exemptions and redaction

Two habits separate offices that survive a challenge from offices that do not.

Redact, do not withhold. If a five-page memo contains one exempt paragraph, the other four and a half pages are still disclosable. Blanket withholding of an entire record because part of it is exempt is the error most likely to draw a lawsuit and the one least likely to be defended successfully.

Cite the specific statute, every time. Not "attorney client," not "personnel," not "exempt." The actual section. California's public records exemptions live across Government Code sections 7923.600 through 7929.610, plus the balancing provision at section 7922.000, and the whole Act was recodified in 2023 into section 7920.000 and following without substantive change. If your templates still cite the old section 6250 numbering, they are out of date and should be updated, even though the underlying rights did not change.

Route anything novel, sensitive, involving personnel, litigation, law enforcement, or a third party's private information to counsel before release. Log the referral. Counsel's review time is generally not chargeable to the requester.

---

Where records requests and meeting records collide

A large share of the requests that land in a clerk's office are about meetings: the agenda packet, the writings distributed to the body, the recording, the minutes.

Two facts are worth having at hand.

First, in California, writings distributed to all or a majority of the members of a legislative body in connection with a matter subject to discussion at an open meeting are disclosable public records under section 54957.5, and the Brown Act requires agenda related writings for the open session of a regular meeting to be posted alongside the agenda. In other words, much of what a requester will ask for should already be public before they ask.

Second, the approved minutes are the official record of what the body did. A recording is evidence of what was said. Those are different things, and a requester asking for "the minutes" and a requester asking for "the audio" are asking for genuinely different records with different retention treatment. California cities have a specific destruction pathway for certain recordings under Government Code section 34090.6, and a general framework in section 34090 under which a department head may destroy records no longer required, with the approval of the legislative body by resolution and the written consent of the city attorney, subject to the rule that records less than two years old are retained.

The practical takeaway for a clerk's office is the same either way: the better your minutes are, the less pressure lands on your recordings. An agency with thin, ambiguous minutes gets requests for the audio, because the minutes did not answer the question. An agency whose minutes state clearly what was moved, who moved it, who seconded, how each member voted, and what the body directed staff to do resolves most requests at the minutes.

That is worth investing in on its own merits, and it is the reason the agenda, the minutes, and the records request queue are really one workflow rather than three. For the drafting side of it, see our guides on what to include in board meeting minutes and official meeting minutes versus verbatim transcripts under FOIA.

---

Fees

Keep this simple and keep it published.

You may generally charge the direct cost of duplication and any fee the statute specifically authorizes. You generally may not charge for the staff time spent searching, reviewing, or redacting, and you may not charge for counsel's review. California's standard is at Government Code section 7922.530, which also protects a requester who inspects records on your premises and photographs them with their own equipment in a way that does not touch the record.

Two rules prevent nearly every fee dispute: publish the schedule on the website, and apply it identically to the frequent requester, the journalist, the resident, and the law firm. Selective fee waivers create far more risk than the revenue is worth.

---

Common failure modes

• The clock started at the wrong date. A request that arrived at the public works counter on the 3rd but reached the clerk on the 10th was received on the 3rd.
• The determination never went out. Records were produced eventually, so the office believes it complied. It did not.
• An extension was taken with no stated basis. Unusual circumstances are defined by statute, and "we were short staffed" is not among them.
• A whole record was withheld for a partial exemption. Segregate and release the rest.
• The search skipped text messages. Content governs, not the device.
• Nothing was logged. Two years later, nobody can prove what was released or when. This is the failure that turns a routine request into a finding.

---

The 30-minute version

If you are starting from nothing, do these four things this week:

1. Create the log with the columns above and backfill every open request you know about.
2. Write a one-page intake rule and send it to every department: date stamp on arrival, forward to the clerk the same day.
3. Build three email templates: determination with records, determination with no records, and written extension with the statutory basis stated.
4. Diary the determination deadline for every open request in whatever calendar you actually look at.

That is the whole system. Everything above is detail on top of it.

---

Related Reading

• Public Records Requests for Board Meeting Recordings Are Surging
• Official Meeting Minutes vs. Verbatim Transcripts Under FOIA
• The City Clerk's Agenda Preparation Workflow
• Ordinance vs. Resolution vs. Motion: A Clerk's Guide
• Open Meeting Laws in All 50 States: A Board Clerk's Compliance Guide
• Are Board Meeting Minutes Public Records?
• Free Meeting Minutes Templates

Nothing here is legal advice. Public records law varies by state and your city attorney is the authority on how it applies to your agency.

---

Strong minutes are the cheapest records request defense a clerk's office has. BoardBreeze turns a recording of your meeting into formatted minutes organized by agenda item, with motions, seconds, and votes captured in an approval ready structure, and uploaded audio is automatically deleted within days. Start a free trial, no credit card required.