Ever tried to figure out what your town, city, county, or special district is doing—only to run into a maze of forms, deadlines, and “we’ll get back to you” emails? Open records laws exist so regular people can see how public business is being done. But the process can feel confusing on both sides of the counter: residents want answers, and staff members are juggling legal rules, limited time, and real privacy concerns.
This guide breaks down, in plain English, how local governments typically handle open records requests—from the moment a request arrives to the moment records are released (or withheld). It’s not legal advice, and the exact rules vary by place, but it will help you understand the moving parts, why responses can take time, and how to make your request more likely to succeed.
We’ll cover what counts as a “record,” what governments can redact or withhold, how timelines and fees usually work, and what happens when a request turns into a dispute. Along the way, you’ll also see how open records intersects with meetings laws, litigation holds, and even day-to-day email habits.
Open records in real life: what the law is trying to balance
At a high level, open records laws are built on a simple idea: government work belongs to the public. If a local government is making decisions, spending money, or enforcing rules, people should be able to look behind the curtain and understand what’s happening.
But transparency isn’t the only value in play. Local governments also have to protect sensitive information—things like medical details, student records, certain law enforcement data, and private identifying information. They also have to preserve the integrity of investigations, ensure fair bidding processes, and respect legitimate confidentiality rules.
So the job isn’t “release everything” or “deny everything.” The job is to find the right balance: release what the public is entitled to see, while carefully withholding or redacting what the law protects.
What counts as a public record (and what surprises people)
Many people assume “public records” means official documents like ordinances, budgets, or signed contracts. Those are usually included, but open records often go much broader. In many jurisdictions, a “record” can be almost any information created, received, or kept by a public agency in connection with public business.
That can include emails, text messages on government devices, staff reports, internal memos, drafts, calendars, audio recordings, photos, GIS data, and more. The tricky part is that the format doesn’t matter as much as the function: if it’s used to conduct public business, it may be a record.
What surprises people most is how informal communications can become part of the record universe. A quick email like “Can you move that agenda item?” or “Here’s the updated spreadsheet” can be responsive to a request. Even if no one thought of it as “a document,” it may still be retrievable and reviewable.
“But it’s on someone’s phone”—does that matter?
Some of the thorniest questions arise when officials use personal devices or personal accounts for public work. Many open records frameworks focus on the content and purpose of the communication, not the device it lives on. If the message is about public business, it can still be subject to disclosure—even if it’s on a personal phone.
That doesn’t mean the public gets to rummage through someone’s entire personal life. Instead, agencies typically have to take reasonable steps to search for responsive public-business communications while limiting access to private, unrelated content.
In practice, this is one reason many local governments push staff and elected officials to use official accounts and systems. It’s cleaner for retention, easier to search, and less likely to trigger privacy headaches.
Drafts, notes, and “work in progress” materials
Another common misconception is that drafts are automatically exempt. Sometimes drafts can be withheld under specific rules (for example, deliberative process protections), but the details vary widely. In some places, drafts are still records; in others, certain pre-decisional materials may be protected.
Notes can be even more complicated. A sticky note used as a personal reminder might not be a public record, while notes used to brief decision-makers could be. The deciding factor is usually how the notes are used and maintained—not whether they look “official.”
If you’re making a request, it helps to be specific about what you’re looking for (final report, staff memo, attachments, supporting spreadsheets) and to understand that drafts may trigger extra review time and extra exemptions.
How requests actually arrive: channels, tracking, and triage
Local governments receive open records requests in a bunch of ways: through web portals, email, paper forms, or even in-person requests at the counter. Many agencies route requests to a clerk’s office, a records custodian, or a legal/compliance team that coordinates the response.
Once received, the request is typically logged and assigned a tracking number. This is not just bureaucracy—tracking helps ensure deadlines are met, searches are documented, and the agency can explain what it did if the response is challenged later.
Then comes triage. Staff will often do an initial read to figure out what you’re asking for, how broad it is, which departments might have responsive records, and whether any special issues are obvious (personnel files, law enforcement investigations, ongoing litigation, protected health information, and so on).
Clarifying the scope without “stonewalling”
It’s common for agencies to ask clarifying questions. Done well, this is helpful: it can save time, reduce fees, and get you the most relevant information faster. Done poorly, it can feel like delay or resistance.
A good clarification request explains what’s unclear and offers options. For example: “Do you want all emails about the project, or only emails between specific dates?” or “Are you looking for the executed contract only, or also the proposals and scoring sheets?”
If you’re the requester, responding quickly and narrowing where you can often leads to a faster, cheaper result. If you truly need a broad set of records, you can say so—but it helps to understand that broad requests can take longer because they require more searching and more legal review.
When the request is too broad to process as written
Sometimes a request is so wide that it’s hard to know where to start: “All records related to the city manager for the last five years,” or “Everything about downtown development.” Agencies may need to negotiate a manageable scope.
In many systems, the agency isn’t required to create new records or answer questions like a research service. They generally have to produce existing records. So a request that reads like an interrogation (“Why did you do X?”) may be redirected into a records-focused request (“Provide the staff reports and meeting minutes where X was discussed”).
If you’re hitting a wall, try rephrasing your request in terms of specific record types, date ranges, and known project names. That makes it easier for staff to identify where to search and what to pull.
Searching for records: where governments look (and why it takes time)
After the request is scoped, the agency has to search for responsive records. This can be straightforward if everything lives in a modern document management system. But many local governments have a patchwork of systems: email servers, shared drives, case management tools, finance software, HR platforms, police records systems, and old archives.
Staff may need to coordinate across departments—planning, public works, finance, HR, law enforcement, the clerk’s office, and others. Each department might have its own filing habits and its own “institutional memory” about where records are stored.
Searches also have to be defensible. If a response is challenged, the agency may need to show it performed a reasonable search. That’s why you’ll sometimes see careful documentation of where staff looked and what search terms they used.
Email searches: keywords, date ranges, and custodians
Email is often the biggest time sink. A request for “all emails about Project X” might involve dozens of staff members and thousands of messages. Agencies may need to identify the right “custodians” (people likely to have the records), decide on search terms, and set date ranges.
If the request is broad, the agency may ask you to narrow it to certain senders/recipients, a shorter time window, or specific topics. This isn’t necessarily about avoiding disclosure—it’s often about making the search feasible.
From a requester perspective, including known email addresses, project names, contract numbers, or meeting dates can dramatically improve the odds of finding relevant messages without pulling half the server.
Text messages, chat apps, and collaboration tools
Many local governments now use tools like Teams, Slack, or other platforms for quick coordination. Depending on retention settings, these messages may be stored in ways that are searchable—or they may be more difficult to retrieve.
Agencies that have strong information governance policies can often export and review these communications. Agencies without those policies may struggle, especially if messages are ephemeral or stored inconsistently.
For requesters, it can help to explicitly include “text messages and chat messages” if that’s what you’re after, but be ready for the agency to explain limitations or to propose alternative sources (like meeting notes or emails) if chat retention is limited.
Review and redaction: the careful part you don’t see
Once records are collected, the agency has to review them for exemptions and privacy issues. This is where a lot of the time goes, especially when there are many pages or when the records contain sensitive information.
Review often happens in layers. Staff may do an initial pass to remove clearly non-responsive material (like unrelated email threads). Then someone with records training—or legal counsel—reviews for exemptions, required redactions, and anything that might trigger notice obligations.
Redaction isn’t just “black out the juicy parts.” It’s supposed to be precise: redact only what’s protected and release the rest. That takes attention to detail, because accidental disclosure of protected information can create real harm and legal risk.
Common categories that get redacted
While the exact rules vary, a few redaction categories come up again and again: personal phone numbers and home addresses, dates of birth, driver’s license numbers, bank account details, medical information, and certain information about minors.
Personnel-related information is another frequent flashpoint. Some information about public employees is often disclosable (like job titles and salaries), while other parts may be protected (like medical leave details or certain disciplinary records, depending on the jurisdiction).
Law enforcement records can be especially complex, with different rules for active investigations, informant information, victim privacy, and officer safety. Even when some information is withheld, agencies may still be required to release a redacted version.
Exemptions that protect decision-making and legal strategy
Many open records systems recognize that some internal deliberations need breathing room. There may be protections for pre-decisional advice, draft policy discussions, or internal recommendations—though the scope of these protections varies widely.
Another common protection is attorney-client privilege and attorney work product. If the agency’s lawyers are providing legal advice, those communications are often exempt from disclosure. This is not about secrecy for secrecy’s sake; it’s about allowing the government to get candid legal guidance like any other client.
In practice, when a request touches on legal issues, agencies often coordinate with counsel to ensure privileged communications aren’t accidentally released. If you’re trying to understand a decision, you may get more mileage requesting the final staff report, the adopted resolution, and the meeting recording rather than “all legal advice about the issue.”
Timelines: why “as soon as possible” still isn’t tomorrow
Most open records laws set response deadlines—sometimes a fixed number of business days, sometimes a “prompt” standard with extensions allowed for complex requests. Even when the law sets a short initial deadline, that deadline often applies to acknowledging the request or providing an initial determination, not necessarily producing everything immediately.
Local governments often have to balance open records work with their regular workload. A small town might have a single clerk handling elections, meeting packets, licensing, and records requests. A sudden surge of broad requests can create backlogs.
That said, agencies usually can’t just sit on a request. If more time is needed, they typically have to communicate that, explain why, and provide an estimated timeline or a plan for rolling production.
Rolling productions and partial releases
For large requests, agencies may produce records in batches. This can be a win-win: you start receiving documents sooner, and staff can keep moving without waiting until every last page is reviewed.
Batch releases also help surface misunderstandings early. If the first batch isn’t what you expected, you can clarify before the agency spends hours reviewing the wrong set of documents.
If you’re requesting records, it’s fair to ask whether the agency can provide rolling production. If you’re the agency, it’s a practical tool to demonstrate good-faith effort and steady progress.
When deadlines collide with elections, emergencies, and big projects
Real life matters. Elections, wildfire response, flooding, major construction incidents, and other emergencies can pull staff away from records work. Many open records frameworks allow some flexibility, but agencies still need to communicate.
From the public side, it can be frustrating to hear “we’re busy,” but it’s also helpful to understand that local government teams are often small and wearing multiple hats.
A collaborative approach—narrowing the request, accepting rolling batches, or prioritizing key items—can keep things moving even when the agency is under pressure.
Fees and costs: what you might pay for (and how to keep it reasonable)
Open records laws often allow agencies to charge certain fees, especially for copying, physical media, or staff time spent on searching and compiling records. Some places limit fees to actual duplication costs; others allow charges for extensive staff time.
Fees can be a major point of tension. Requesters may view fees as a barrier to transparency, while agencies may view them as necessary to avoid diverting staff from core services.
The best outcomes usually come from clear communication: an estimate up front, an explanation of what drives the cost, and options to narrow the request to reduce time.
Practical ways to reduce fees without sacrificing what you need
If you’re trying to keep costs down, start with a narrow date range and a specific project name. Ask for electronic records instead of paper copies. Request “final versions” if drafts aren’t essential.
Another tactic is to ask for an index or list first—like a list of contracts, invoices, or permits—then request only the specific items you care about. That can dramatically reduce the volume.
If the agency offers inspection (viewing records without copies), that can help too. You can review what’s available and decide what to copy or download.
Fee waivers and public-interest considerations
Some jurisdictions allow fee waivers or reductions if the request is in the public interest, for journalism, or for noncommercial purposes. The standards vary, and waivers are not automatic.
If you think a waiver applies, explain why clearly and briefly: how the records will inform the public, whether you plan to publish, and why the request isn’t for private commercial gain.
Even when a full waiver isn’t available, agencies may still work with you to reduce costs by narrowing scope or using more efficient search methods.
How local governments decide what to release: the internal workflow
Behind the scenes, many agencies follow a structured workflow. Someone coordinates the response, departments search their files, records are centralized, and then a reviewer applies redactions and exemptions. Finally, the agency prepares a response letter or email describing what’s being produced and what’s being withheld.
In more complex cases, the agency may involve its legal counsel early—especially if the request touches on litigation, personnel matters, law enforcement issues, or sensitive infrastructure information.
In communities with frequent requests, governments may invest in software to track requests, store responsive records, and produce them in a consistent format. That can improve speed and reduce errors, but it also requires training and consistent use.
Records custodians, clerks, and department leads
The “records custodian” role is often central. This person may not personally locate every record, but they coordinate the process and ensure compliance. They might be in the clerk’s office, administration, or a dedicated compliance unit.
Department leads are important because they know where records live and what terms staff actually use. A requester might say “the river project,” while the department files everything under a grant name or a capital improvement code.
When coordination is strong, responses are faster and more consistent. When it’s weak, requests can bounce around, searches can be incomplete, and timelines can slip.
Legal review and risk management
Legal review isn’t only about denying records. It’s often about making sure the agency releases as much as it can without violating privacy laws or privileges. That protects the public too, because accidental disclosure can harm individuals or compromise investigations.
When a request is likely to become contentious, agencies may also consider how to explain their decisions clearly. A well-written response that cites the applicable exemptions and describes the search effort can reduce misunderstandings.
In Colorado communities, for example, agencies often rely on counsel familiar with local government operations and records law to navigate these issues; many people in the area turn to a local government attorney in Glenwood Springs when questions about compliance, governance, and public records get complicated.
Common pain points (and what helps)
Open records requests can go off the rails for predictable reasons: unclear scope, unrealistic expectations, mistrust, and the emotional heat around controversial projects. The good news is that small adjustments often prevent big conflicts.
One major pain point is when requesters assume the agency is hiding something, while staff assume the requester is trying to create extra work or “catch” someone. Those assumptions make communication worse and slow everything down.
Another pain point is the mismatch between how the public imagines records are stored and how they actually are stored. A requester might picture a neat folder labeled “Downtown Plan,” while the reality is scattered emails, attachments, and versioned files.
Making a request that’s easier to fulfill
If you want a smoother experience, think like a librarian. Include names, dates, addresses, project numbers, meeting dates, and likely departments. Ask for specific record types (permits, inspection reports, staff memos, contracts, invoices, email correspondence).
Also, consider stating your purpose in a neutral way. You don’t have to justify your request, but a simple note like “I’m trying to understand how the project was approved” can help staff point you to the most relevant records.
Finally, be open to alternatives. If a request for “all emails” is overwhelming, you might accept a narrower set like “emails between the project manager and the contractor from March through May.”
How agencies can reduce friction without bending the rules
From the government side, a few practices make a big difference: quick acknowledgment, clear timelines, and a willingness to clarify scope. Even a short message like “We received your request and are gathering records; we’ll provide an estimate by Friday” builds trust.
Posting commonly requested records online is another huge help—contracts, check registers, meeting packets, ordinances, and policies. Proactive disclosure reduces the number of formal requests and saves staff time.
Training matters too. When staff understand retention rules, know how to use search tools, and recognize common exemptions, they can respond faster and with fewer errors.
When open records intersects with disputes, claims, and lawsuits
Open records requests often spike when there’s a dispute: a terminated contract, a zoning fight, a public works project gone sideways, or allegations of misconduct. At that point, records requests can overlap with legal claims, insurance issues, or pending litigation.
Local governments have to be careful in these situations. They may have additional obligations to preserve records (a “litigation hold”), and they may need to coordinate with outside counsel. They still have to comply with open records laws, but they must also protect privileged communications and ensure they don’t inadvertently waive legal protections.
For requesters, it’s important to understand that open records is not the same thing as discovery in a lawsuit. Open records laws provide access to public records; discovery is a separate legal process with its own rules and broader tools.
Litigation holds and why deletion policies suddenly matter
When litigation is reasonably anticipated, agencies typically have to preserve relevant records—even if normal retention schedules would allow deletion. That can include emails, texts, drafts, and attachments.
This preservation duty can affect open records responses because staff may need to ensure records are properly collected and preserved before production. It can also mean the agency is working with IT to prevent auto-deletion.
If you’re a business or individual in a dispute with a local government, coordination between records strategy and legal strategy becomes important. In those scenarios, people sometimes consult a commercial litigation lawyer in Glenwood Springs to understand how public records, claims, and courtroom procedures fit together.
Vendor relationships, procurement records, and contract conflicts
Procurement is a frequent source of records requests: bid submissions, scoring sheets, evaluation notes, and contract negotiations. Governments often must disclose a lot of this information, but there may be protections for trade secrets or proprietary details.
Agencies may notify vendors if their information is being requested, giving them a chance to assert confidentiality claims. The agency still has to decide what the law requires, but vendor input can shape the review.
If you’re a vendor, it’s smart to label truly proprietary information clearly at the time of submission and to understand that “confidential” stamps don’t automatically make something exempt. Businesses sometimes work with a business lawyer in Glenwood Springs to set up practical processes for bids, confidentiality claims, and contract compliance that won’t fall apart under public scrutiny.
Appeals, denials, and “we can’t find it”: what happens next
Sometimes a requester receives a denial, a heavily redacted packet, or a response that says “no responsive records.” That doesn’t always mean the agency is acting in bad faith. It can mean the request was too narrow, the records were never created, the agency doesn’t keep them, or the search terms missed how the agency labels things.
Still, requesters often have options. Depending on the jurisdiction, you may be able to ask for reconsideration, submit a revised request, pursue an administrative appeal, or seek judicial review.
Before escalating, it often helps to ask a few calm questions: What systems were searched? Which departments were contacted? What date range was used? Were specific custodians included? A transparent explanation can resolve many disputes.
Understanding a denial letter in plain language
Denial letters often cite statutes or exemptions that look like alphabet soup. The key is to focus on what the agency is saying: is it denying the entire request, or only parts? Is it withholding because of privacy, privilege, or an ongoing investigation? Is it saying the record doesn’t exist?
If the agency withheld records, it may be required to identify the exemption category and sometimes to describe the type of record withheld. In some places, agencies provide a “withholding log” or similar explanation.
If you think the agency misapplied an exemption, you can ask for a more detailed explanation or request that segregable portions be released (meaning: release what can be released, redact the rest).
When the agency says “no records” but you’re sure they exist
This happens more than you’d think. Sometimes the records exist but weren’t found due to search terms, naming conventions, or because they’re held by a contractor or a different agency.
Try submitting a follow-up request with alternative terms, broader date ranges, or specific names. If you have evidence (like an email referencing an attachment), mention that reference in your revised request.
Also consider that some information might be in a different form than you expect. For example, what you think is a “report” might actually be a set of inspection notes in a database, or a staff presentation attached to a meeting packet.
Proactive transparency: the easiest records request is the one you never have to file
Many local governments are moving toward proactive disclosure—posting frequently requested records online before anyone asks. This can include meeting agendas and packets, ordinances, budgets, contracts, check registers, and policy manuals.
Proactive transparency is more than a nice idea; it reduces workload. If residents can find what they need on the website, staff spend less time processing formal requests and more time serving the community in other ways.
It also improves trust. When information is easy to access, people are less likely to assume the worst. And when a formal request does come in, it’s often narrower and easier to fulfill.
Website organization that actually helps real people
It’s amazing how often records are technically “available online” but practically impossible to find. Clear navigation, search features, and consistent naming conventions matter.
Posting meeting packets in a searchable format, keeping an archive that goes back several years, and labeling documents with dates and topics can save everyone time.
Even simple improvements—like a dedicated “Public Records” page explaining how to request records, typical timelines, and fee policies—can reduce confusion and make the process feel less intimidating.
Retention policies and the long game
Retention schedules determine how long records are kept and when they can be destroyed. Strong retention practices help agencies respond to requests because records are organized and consistently stored.
Poor retention practices create chaos: missing records, inconsistent archives, and last-minute scrambles. That’s when open records becomes slow and contentious.
For the public, understanding retention is useful too. If you request something from ten years ago, it may legitimately no longer exist. Asking for older records is still okay—just know that retention limits can shape what’s available.
Tips for writing an open records request that gets better results
If you want to increase the odds of getting what you need without a drawn-out back-and-forth, a well-crafted request is your best tool. Think of it as giving the agency a map rather than a riddle.
Start by identifying the agency and department most likely to have the records. Then specify the record types, date range, and subject matter. If you know key people involved, include their names as likely custodians for email searches.
Finally, be clear about the format you prefer (electronic PDF, native spreadsheet, etc.) and whether you’re open to rolling production.
A simple template you can adapt
You can adapt language like this: “Please provide copies of [record types] related to [project/topic] from [date range]. This includes emails and attachments between [names/titles], as well as staff reports, contracts, invoices, and inspection reports. Please provide records electronically if available. If any portion is withheld or redacted, please identify the basis for the withholding.”
This kind of request is specific enough to search, broad enough to capture common record types, and clear about expectations.
If you’re concerned about cost, add: “If fees are expected to exceed $X, please provide an estimate before proceeding, and I’m open to narrowing the request to reduce costs.”
How to stay persistent without burning bridges
If you don’t hear back, a polite follow-up is reasonable. Ask for the status, confirm the scope, and request an estimated timeline. Keeping communication in writing helps everyone stay aligned.
If the agency is overwhelmed, you can ask what narrowing would make the biggest difference. Sometimes reducing custodians from 20 to 5, or shrinking a date range from two years to three months, cuts the workload dramatically.
If you believe the agency is not complying, you can explore appeal options—but even then, staying factual and calm tends to produce better outcomes than escalating emotionally.
What transparency looks like when it’s working
When open records systems work well, it doesn’t feel like a battle. Requests are acknowledged quickly, clarified when needed, and fulfilled in a reasonable time. Fees are predictable. Redactions are explained. And the public gets meaningful access to how decisions are made.
Local governments benefit too. Clear processes reduce risk, improve consistency, and build credibility. Staff spend less time firefighting and more time serving residents.
For residents, journalists, and businesses, understanding the process helps set realistic expectations and improves the quality of requests. The more both sides treat open records as a shared civic tool—not a weapon—the better it works for everyone.
