Public trust in government is eroding.
According to Gallup, who have been tracking trust at every level of government for decades, all trends point in the same direction. While state and local governments still fare better than Feds in the eyes of most Americans, that advantage is fragile.
And few things destroy it faster than the appearance of hiding, losing, or deleting public records.
The challenge is that most agencies aren't trying to hide anything. They're just underprepared.
A city clerk fielding a public records request for a deleted Facebook comment or a prior version of the city's website may have every intention of complying — and no way to actually do it.
Manual capture methods fail. Institutional memory fades. And when the response is late, incomplete, or contested, the public doesn't assume good faith. They assume the worst.
This is the transparency problem facing state and local governments today: not misconduct, but a recordkeeping infrastructure that hasn't kept pace with how government agencies communicate.
The good news is that it's a solvable problem — and solving it is one of the most direct investments an agency can make in public trust.
Government Websites and Social Media Are Public Records
Most open records laws were written long before social media existed. But that hasn't stopped courts and legislatures from making clear that online digital content, including websites and social media posts, are public records.
The governing principle that has emerged across nearly every state is straightforward: what makes something a public record is its nature, not its medium. If it was created or received in connection with official government business, it's a record — regardless of whether it lives in a filing cabinet or a Facebook post.
Florida's statute is a useful illustration of how broadly most states define the term. Florida law defines public records as any material "regardless of the physical form, characteristics, or means of transmission" made or received in connection with official agency business. That language was written to be expansive on purpose.
In practice, that means the following all qualify as public records:
- Posts and updates on official government social media accounts
- Comments left by members of the public on those accounts
- Individual pages on a government website
- Every version of a webpage or social media post, even when it's edited or updated
- Comments or posts that were deleted — even if they were only visible for seconds
That last one surprises a lot of people. Say a staff member posts an update, spots a typo, and deletes it within a minute to repost a corrected version. That original post is still a public record. The public could have seen it. It was created in connection with official business. Therefore, it has to be retained.
This is where manual recordkeeping starts to break down — and where the gap between what agencies intend to preserve and what they actually preserve begins to widen.
The Risk of Treating Digital Recordkeeping as an Afterthought
When agencies think about digital recordkeeping at all, the default approach is usually some version of the same thing: a staff member takes screenshots of the website, copies text from a social post into a document, or relies on a platform's built-in export tools. It is reactive, and it feels like a reasonable workaround.
In practice, it's a problem waiting to happen. Especially if they’re just relying on screenshots.
The fundamental issue with manual capture is three-fold:
1. Screenshotting is a waste of time (and effort)
First, it is a huge time and resource waste. It takes an incredible amount of time for staff to:
- manually scroll and capture entire timelines that could span decades
- manually expand and capture every single comment
- download every single video that can’t be captured by a simple screenshot tool
- ensure every single page of the website has been captured
- capture every single form, drop down menu, or interactive feature on the site
- organize and store image or text files for later retrieval
- locate records based on the content of the post or comment
- produce the records in a readable format for requester
Not to mention the effort it requires to make sure no records are missed while they’re scrolling or no new comments have appeared since the last time they took a screenshot.
From a time and resource perspective, manual recordkeeping of digital content is untenable.
2. Screenshots aren’t good enough for public records
The second problem is that the method itself is structurally inadequate for what open records laws actually require.
Start with authenticity. A screenshot is an image file. It carries little to no metadata, no context, no way to verify it hasn’t been photoshopped.
If a requester or a court asks you to prove that what you're producing is an accurate, unaltered record of what appeared on your website or social media account on a specific date, a JPEG image is not going to hold up. It could easily have been altered and could miss important context.
FOIA and most state open records laws do have stipulations about how records should be delivered to requesters, and in most cases, screenshots wouldn’t be acceptable on their own.
3. Manual capture almost guarantees missing records
Then there's the timing problem. Manual capture depends on a human being in the right place at the right time. Social media moves in seconds. A comment goes up, gets flagged, and is deleted before anyone on staff has seen it — let alone screenshotted it.
A webpage gets updated during a council meeting. A post is edited after a reporter calls with questions. No one informs the records clerk and now the records are out of date.
Manual workflows aren't built for that pace, and no amount of diligence fully closes the gap.
Even when records are captured, the back-end problem remains.
Files saved to shared drives, email folders, or personal desktops means that whenever there is a records request, a scavenger hunt ensues.
Sure, technically there is a record, somewhere. But you still have to find it.
This problem scales dramatically when the requestee asks for all the records on a particular topic or everything your agency posted online about it. You would have to scour every single post to see if it is relevant and then attempt to reconstruct the history from scratch.
What we’re trying to illustrate here is that manual recordkeeping doesn't fail because staff aren't trying. It fails because it asks people to do consistently and perfectly what software should be doing automatically.
And the fallout can be devastating.
How Missing Records Damage Public Trust
When New Jersey lawmakers proposed changes to the state's Open Public Records Act in 2024, 81 percent of residents polled opposed them — not because the changes were radical, but because they were perceived as making records harder to access. That's not a partisan number. That's a near-unanimous public telling their government that transparency isn't negotiable.
Hopefully your agency has never faced a moment that dramatic. But the same underlying dynamic plays out at a smaller scale all the time, and the consequences are just as corrosive.
Picture a familiar scenario: a resident files a public records request for communications related to a zoning decision they think was mishandled. The agency can't produce complete records — a relevant webpage was updated without the prior version being saved, and a handful of social media comments were deleted during routine moderation. Staff respond as best they can, but the response is incomplete and takes longer than it should.
The resident concludes that something is being hidden. They aren’t thinking that maybe the city has some recordkeeping issues, they assume the worst. They contact a local reporter. Now the story isn't about zoning — it's about a city that can't or won't produce its own records. The agency spends the next several weeks in damage control, and the reputational cost far exceeds whatever it would have taken to maintain proper records in the first place.
This is how trust actually erodes at the local level. Not in a single scandal, but in a slow accumulation of delayed responses, incomplete records and unanswered questions that leave residents wondering what else is hidden or missing. The fines for open records noncompliance are real, but they're almost beside the point. The more damaging cost is the reputational damage.
We don’t have to tell you that in government, reputation can mean the difference between getting funded or not, getting voted in or out, or even having a baseline of support from your own community to make improvements.
But there is good news embedded in that New Jersey poll: the public wants to trust their local institutions. The appetite for transparency is broad and bipartisan. Agencies that make records consistently accessible actively building trust — something that's genuinely hard to earn back once it's lost.
Warning: Transparency Extends to Edited & Deleted Content
Most records managers intuitively understand that official documents need to be preserved. The part that catches agencies off guard is the scope of what "official" actually covers in a digital environment — specifically, that the obligation to retain content extends to content that has been edited, deleted, or removed during moderation.
That means every version of a webpage is its own record. When your communications team updates the city's budget page, the prior version doesn't cease to exist as a public record just because it was replaced. Both versions have to be retained.
The same logic applies to social media: an edited post creates two records — the original and the revision. A deleted post doesn't disappear from your retention obligations just because it was removed from the platform.
The time threshold here is lower than most people expect. Consider a routine scenario: a staff member posts a meeting notice with the wrong date, catches the error within two minutes, and deletes the post to reissue a corrected version. That original post — the one that was live for two minutes — is a public record. Someone could have seen it. It was created in connection with official business. It has to be preserved.
Manual workflows have no reliable way to handle this. By the time a staff member thinks to screenshot the original, it's already gone.
Comment Moderation Is Its Own Minefield
Deletions get even more complicated when it comes to public comments on official social media accounts.
In 2019, the U.S. Court of Appeals for the Fourth Circuit affirmed that individuals have a First Amendment right to post critical comments on public officials' social media pages. Government agencies cannot delete or hide comments simply because they're negative, unflattering, or uncomfortable to leave up.
The narrow exceptions — spam, content that incites unlawful activity — are real, but they're genuinely narrow. Agencies that err on the side of deletion because a comment is hostile or critical can be exposed to First Amendment litigation, not just public records issues.
When agencies do have legitimate grounds to take action on a comment, that's precisely when a complete, timestamped record matters most. Automated recordkeeping creates a clear, authenticated record of what was posted, when it was visible, and what action was taken — documentation that is very difficult to reconstruct after the fact and invaluable if the decision is ever challenged in court.
How to Reduce Manual Workload while Improving Agency Reputation Through Proactive Disclosure
There's a version of transparency that's purely reactive: someone asks, you produce. It's the minimum the law requires, and for many agencies operating under staffing and budget constraints, it's all they have bandwidth for.
The problem is that reactive transparency is expensive — in staff time, in response delays, and in the public perception that information only surfaces when someone fights for it.
Proactive disclosure flips that dynamic. When records are made available through a public-facing self-service portal, residents can find what they're looking for without filing a formal request at all. The information is just there — searchable, accessible, and available at any hour without staff involvement.
The operational impact can be significant. One agency using Pagefreezer's Website Archiving platform saw public records requests drop by 30 percent after launching a self-service portal. For a city clerk's office already stretched thin, that's not a marginal improvement — it's hundreds of hours reclaimed every year, backlog reduced, and staff freed up for work that actually requires human judgment.
There is also a huge reputational benefit. An agency that proactively publishes its records tells residents that there's nothing to hide, that access isn't something you have to fight for, and that transparency is a standing commitment rather than a response to pressure. That signal accumulates over time in a way that even the most efficient responses never can.
The shift from reactive to proactive access to digital records stewards a fundamentally different relationship with the public you serve.
And with public records requests on the rise, these benefits cannot be overstated.
How Transparency Builds Long-Term Trust
Trust in local government isn't built in a single moment. It's built — or lost — in the accumulated experience residents have when they try to access information about the people and institutions making decisions that affect their lives.
A fast response to a records request. A public portal where historical information is easy to find. A clear record of what was said, when, and by whom when a decision gets contested. These aren't dramatic gestures. They're the ordinary mechanics of accountability, and they compound over time.
For records managers and city clerks, this is worth sitting with for a moment.
The work of maintaining a complete, accessible archive can feel administrative — a compliance obligation sandwiched between more visible responsibilities. But it sits at the center of something much larger. Every time your office produces a complete record quickly, you're demonstrating that the government works as it should. Every time you can't, you're feeding a suspicion that it doesn't.
The Digital Recordkeeping Best Practices That Build Trust
The consequences of non-compliance with open records laws can feel abstract until a requester takes your agency to court — and only then do the gaps in a manual recordkeeping system become impossible to ignore.
The agencies that build genuine long-term trust in their communities tend to share a few best practices:
1. They capture everything, before someone asks for it
Website updates, social media posts, and public comments are records the instant they exist, not after someone asks for them. Getting ahead of that means building recordkeeping into your workflow rather than bolting it on afterward.
Build a recordkeeping infrastructure that holds up before anyone ever has to ask.
2. They replace manual capture with automated archiving
No manual process can reliably capture content that changes or disappears in seconds. Screenshots miss metadata. CMS exports miss context. And both depend on staff remembering to do them consistently, which is an unrealistic standard for any team managing competing priorities.
Automated archiving removes the human bottleneck entirely — content is captured continuously, completely, and in a format that will hold up to scrutiny.
3. Their records are searchable and authenticated
Capturing records is only half the job. If your archive is a disorganized collection of files that takes hours to search, you haven't solved the problem — you've just moved it downstream.
Records need to be indexed, searchable, and authenticated so that when a request comes in, you can produce what's needed quickly and confidently. A response that arrives fast and complete drives trust and confidence.
4. They make information publicly accessible
When residents can search your archived records without filing a formal request, they get faster answers and your staff gets fewer interruptions. More importantly, easy public access signals that your agency isn't guarding its records. That signal is worth more than any press release about your commitment to transparency. When access feels like a feature of local government rather than a struggle, that’s when trust is built.
None of this requires a large team or an outsized budget. It requires the right infrastructure and a consistent commitment to the principle that the public's right to know isn't a burden to manage — it's the point.
Complete and Accessible Public Records Foster Transparency and Trust
Nobody gets into public service to manage a records archive. City clerks, records officers, and communications directors are already stretched across more responsibilities than any job description fully captures.
The case for investing in better digital recordkeeping has to be honest about that reality — because "you might get sued" is not, on its own, a compelling enough argument to justify a new line item in a constrained budget.
Here's the more honest case: the infrastructure that protects your agency from litigation is the same infrastructure that builds public trust. These aren't separate investments. An archive that's complete, authenticated, and searchable doesn't just hold up in court — it produces fast, confident responses to records requests. It powers a public portal that reduces your team's workload. It creates a documented record of what your agency said and did that makes accountability feel like a feature, not a threat.
Trust in local government is still recoverable. Unlike trust in federal institutions, which has been in structural decline for decades, state and local governments retain genuine goodwill with most of their residents — goodwill that's worth protecting. The agencies that hold onto it longest aren't the ones that never make mistakes. They're the ones that have built systems transparent enough that mistakes can be seen, explained, and corrected in the open.
Pagefreezer Archiving Suite automatically captures website and social media content continuously, preserving every version, edit, and deletion in an authenticated, searchable archive. If your current recordkeeping approach depends on staff remembering to screenshot the right things at the right time, it's worth seeing what a system built for the actual pace of digital content looks like.
Schedule a demo to find out how we can help you build trust and confidence with your digital recordkeeping.
Digital Recordkeeping and Government Transparency FAQs
Are website updates public records at the state or local level?
Yes — both versions are. When your team updates a page on the city website, the prior version doesn't stop being a public record just because it was replaced. Each iteration of a webpage is its own record, which means an agency that has updated its budget page, its meeting schedule, or its contact information a dozen times over the past few years technically has a dozen records to account for. Continuous automated archiving is the only practical way to ensure none of those versions slip through the cracks.
Do deleted social media comments need to be retained?
Yes. If a comment was publicly visible — even briefly — it's a public record. There's no minimum visibility threshold. A comment that went up at 9:02 and was deleted at 9:03 still has to be retained in accordance with your jurisdiction's records retention schedule. This is one of the areas where manual capture methods are most likely to fail, since the window between a comment appearing and disappearing can be shorter than the time it takes a staff member to notice it.
How can cities reduce open records request backlogs?
The most effective approach is to reduce the number of requests that require staff involvement in the first place. A public-facing self-service portal — where archived records are searchable and accessible without anyone having to file a formal request — takes a significant portion of routine inquiries off your plate entirely. Agencies that have implemented this approach have seen request volumes drop by as much as 30 percent.
For requests that do come in, automated archiving dramatically cuts retrieval time. Instead of reconstructing a record from scattered screenshots and exports, staff can search a centralized, authenticated archive and produce what's needed in minutes rather than weeks or months. That speed matters operationally, but it also matters for trust — a prompt, complete response to a records request is one of the clearest signals an agency can send that it has nothing to hide.
Is a screenshot ever sufficient for open records compliance?
In most cases, no — and the gap between what a screenshot captures and what open records compliance actually requires is wider than most people realize. A screenshot is an image file. It records what something looked like at a moment in time, but it carries no metadata, no cryptographic hash, and no verifiable timestamp that an independent party can authenticate. If a requester or a court challenges the accuracy of a screenshot — arguing that it was altered, misdated, or incomplete — you have very little to stand on.
There's also the practical problem of what screenshots miss entirely: dynamic content, embedded links, comment threads that have since changed, and any edits or deletions that happened before or after the capture. For routine, low-stakes documentation, a screenshot might be better than nothing. For open records compliance, it's not a reliable foundation.
What makes an archived record legally defensible?
A legally defensible record needs to do two things: prove what the content was, and prove that it hasn't been altered since it was captured. That requires more than a saved file. Defensible digital records typically include a verified timestamp showing exactly when the content was captured, a cryptographic hash value that confirms the file hasn't been modified, and a documented chain of custody showing how the record was stored and managed over time.
This is why the format and method of capture matters as much as the act of capturing. A record that was automatically archived by purpose-built software — with metadata intact and hash values generated at the moment of capture — is in a fundamentally stronger position than one reconstructed from manual exports and folder structures after a request arrives.
Do open records laws apply to personal social media accounts if they're used for official business?
This is one of the most actively contested questions in public records law right now, and the short answer is: it depends on the content, not the account. Several courts have ruled that if a public official uses a personal social media account to conduct official government business — announcing policy decisions, responding to constituents about government matters, or coordinating with staff — that content may qualify as a public record regardless of where it was posted.
The U.S. Supreme Court addressed this directly in its March 2024 ruling in Lindke v. Freed. In a unanimous decision, the Court established a two-part test for determining when a public official's personal social media activity constitutes state action: the official must have actual authority to speak on behalf of the government, and must be exercising that authority when posting.
The practical implication for agencies is that the line between personal and official is fact-specific and often blurry — blurry enough that relying on "it's a personal account" as a compliance strategy is risky. Training staff on appropriate use of personal accounts for government business and maintaining clear policies about it is increasingly important, and so is having an archive that can document what was posted, in what capacity, and when.
