What Happens to Your Video Review Comments When Someone Files a FOIA Request

A city communications office spends three weeks going back and forth on a public safety PSA, arguing about which frame the department seal appears in and whether a claim about average emergency response times needs a citation on screen, and then six months after the video goes live a local reporter files an open-records request asking for "all internal communications, comments, and edits related to the production of this video." Suddenly the question isn't whether the video turned out well, it's whether anyone can actually reconstruct who said what, when, and why a specific line got cut, and for a lot of the government communications teams, public information officers, and agency video staff we talk to, that question catches them completely off guard.

This isn't a rare edge case either. Public-facing video work, whether it's a city council explainer, a transit safety campaign, a hospital system's community health message, or a university's enrollment video, gets produced with public dollars or under public scrutiny, and that means the conversation around it can become a public record just as easily as a memo or an email chain. The video review process itself, the comments, the version history, the approval sign-offs, is often the part nobody thinks to protect until someone asks for it.

Why Your Comment Threads Are a Public Record Whether You Planned For It or Not

Federal FOIA and the state-level open-records laws modeled after it generally cover any record "created or obtained" by a government agency in the course of doing its work, and courts have been fairly consistent about reading that broadly. That doesn't just mean the final rendered video. It can mean the draft cuts, the notes a reviewer left about a specific claim, the email where a department head asked for a graphic to be removed, and the timestamped log of who approved the final version and when. If your agency produced it, or paid a vendor to produce it, the working files around it are fair game for a request, and the federal government alone processes something in the neighborhood of 800,000 FOIA requests a year, so this genre of request is not exotic.

The catch here is that most video teams never set out to build a system that could survive a records request. They built a system that could survive a launch deadline, which is a completely different design goal. Comments live wherever they were easiest to leave in the moment, a Slack thread, a marked-up PDF, a verbal note in a Tuesday meeting, and none of that was ever meant to be reassembled into a coherent timeline for a reporter or an attorney six months later.

What a Records Officer Actually Asks For When the Letter Arrives

When a request lands, it rarely says "send me the video." It says something closer to "all records related to the production, review, and approval of [project name]," and a records officer reading that literally has to go looking for comment logs, reviewer names and titles, timestamps on every note, and any redline showing what changed between drafts. If that information is scattered across four tools and a dozen inboxes, the records officer is now doing forensic archaeology under a legal deadline, and that's a bad position to put your own staff in.

We've heard this exact scenario from communications directors at municipalities and public agencies more than once: the video is fine, the process behind it is the liability. A reviewer's offhand comment questioning a statistic, taken out of context and without the follow-up conversation that resolved it, can look a lot worse in a records production than it ever looked in the room.

The Old Way: Comments Scattered Across Email, Slack, and a Shared Drive

If you've ever tried to answer "did legal actually sign off on version 4, or just version 3" three months after the fact, you know exactly what I mean. Email threads get forwarded and lose context. Slack messages reference "the clip at like 1:40ish" without ever pinning down which version that was. A shared drive full of files named final, final_v2, and final_ACTUALLY_final tells you nothing about who reviewed what or when. None of this is anyone's fault exactly, it's just what happens when a review process grows organically across whatever tools were already open.

Frame-Accurate Comments Matter More Than You'd Think Here

This is the part that surprises people the first time it comes up. A records request tied to a public-facing video often isn't asking about the video in general, it's asking about a specific claim, a specific graphic, or a specific ten seconds where a controversial statistic appeared on screen. If your review notes just say "fix the stat around the middle," that's useless six months later when someone needs to show exactly what was said, at exactly what timecode, and who flagged it first. Frame-accurate, timecoded commentary isn't a nice-to-have for this use case, it's the entire difference between a five-minute export and a week of digging through old files trying to remember which cut had the problem.

For instance, imagine a county emergency management office puts out a wildfire preparedness video, and a resident later disputes a specific evacuation-route claim shown on screen for four seconds near the two-minute mark. If a reviewer had flagged that exact line during production, wanting a source cited before it went live, and the note is sitting in a general email chain with no timecode attached, good luck finding it fast. If that same note is pinned to frame 2,880 of version 6 with a name and a timestamp next to it, the whole story reconstructs itself in seconds, and the agency can show, clearly, that the claim was reviewed and how it was resolved before the video ever aired.

Building an Audit Trail Before You Ever Need One

The teams that handle these requests calmly are the ones who built the habit before the letter ever arrived, treating every review cycle as if it might get pulled into daylight later, because at the end of the day, you genuinely don't know in advance which video is going to end up in a request. It's rarely the one you'd guess.

That last step is the one that matters most under deadline pressure. A records officer with 20 business days to respond does not have time to reconstruct a paper trail from scratch, they need something they can pull and hand off, which is exactly why the review tool a team uses day to day quietly becomes a compliance tool the one time it counts.

Redaction Is Still Your Job, But Only If You Can Find What to Redact

None of this replaces your agency's counsel or your records officer's judgment about what's exempt, deliberative-process material and attorney-involved comments often have narrower protections than people assume, and that's a legal call, not a tooling call. What a structured review process gives you is the ability to actually find every comment that might be responsive in the first place, so your legal team can make an informed decision about redaction instead of hoping nothing slips through because half the conversation happened somewhere nobody thought to search.

Why This Isn't Just a Government Problem

Public agencies feel this most acutely, but they're far from the only ones. Public universities, hospital systems, utilities, and nonprofits that answer to grant funders all face some version of the same exposure, and even privately held production houses working on government contracts inherit it the moment they sign the vendor agreement. If your corporate video work touches public funds, public infrastructure, or a regulated industry, the same discipline applies, and the Nonprofit Marketing Guide has useful frameworks for building accountable communication practices into a small comms team that's worth borrowing even outside the nonprofit world.

A transit authority producing a fare-change explainer, a school district producing a bond-measure video, a state health department producing a vaccination campaign, all of these sit in the same exposed position, and the pattern we see is that the risk isn't proportional to the size of the team. A two-person comms shop at a small county agency has just as much exposure as a twenty-person department at a state agency, because the request doesn't care how big your team is, it cares whether the record exists and whether you can find it. Basically, the smaller the team, the more it hurts to lose a week reconstructing a paper trail by hand, because that's a week nobody had to spare in the first place.

Version Control Isn't Optional When Every Draft Might Be Requested

There's a second wrinkle that catches teams off guard, which is that a records request doesn't necessarily stop at the final approved version. Depending on the jurisdiction and the specifics of the request, draft cuts and intermediate versions can be responsive too, especially if the request is specifically probing for what changed between an early cut and the version that actually aired. That means "we only kept the final export" is a real liability, not a tidy workflow. A review platform that automatically preserves every version alongside the comments left on it turns this from a scramble into a non-event, because nothing had to be manually archived in the first place, it was just sitting there the whole time as a natural byproduct of how the review happened.

This matters even more for anything that touches broadcast news partnerships or gets syndicated across multiple public channels, where a single project might spin off half a dozen cuts for different platforms, each with its own review cycle and its own set of sign-offs. Trying to keep that straight in a shared drive, where file names are the only signal of what's current, is exactly how agencies end up unable to answer a straightforward question like "which version did the director actually approve on March 4th."

What We Tell Teams Who Ask Us This

We built PlayPause's comment and approval structure because we kept seeing the same failure mode across broadcast news partners, agencies, and in-house comms teams: feedback that lived in the review tool for a week and then evaporated once the project shipped. So every comment in PlayPause attaches permanently to the frame and version it was left on, every reviewer signs in under their own name instead of a shared link, and every approval gets logged with a timestamp that doesn't move. When someone needs the full history, it's an export, not an investigation. We also lean on expiring share links and workspace-level sharing security so that access itself is auditable too, which matters just as much as the comments when a reporter or an attorney is asking who could even see the draft before it was public.

If your agency currently reviews video over email because that's what's always been used, it's worth reading how teams replace email with a structured approval workflow built around a single client review portal instead of a scattered inbox. The same underlying problem, needing every stakeholder's feedback to be equally visible and permanently attributable, shows up again in a slightly different form when election offices need bipartisan sign-off on voter education video, which is worth a look if your agency handles anything election-adjacent.

Sound Familiar? Run This Checklist Before Your Next Public-Facing Cut

• Every reviewer has a named account, not a shared password
• Every comment is stamped to a timecode and a specific version
• Every approval is logged with a name and a date, not a verbal okay
• The full history can export in minutes without asking IT for a favor
• Your retention settings actually match your state or agency's records schedule

Most of this isn't expensive to fix, it's mostly a matter of picking a tool that was built to hold onto this information instead of treating it as disposable once a project ships.

Treat Every Public Video Like It's Already Been Requested

The honest truth is you can't predict which video is going to draw a records request, so the only reliable move is building the habit into every project instead of scrambling to reconstruct one after the fact. PlayPause is a flat-price, per-workspace platform, so adding every named reviewer your agency actually needs, legal, communications, department heads, doesn't blow up your budget the way per-seat pricing does, which matters when public accountability means everyone with a stake in the video needs their own attributable account. Check PlayPause pricing and reach out through Contact PlayPause if you want to walk through what a FOIA-ready review workflow would look like for your team specifically.