If That Pepsi Spot Had Gone Through Proper Video Review

You remember the soda ad. The one with the influencer handing a cold can to a line of police officers, and the protest melting into a smile. It got pulled in about a day. Brand says sorry. Internet says everything else.

I am not here to dunk on it. I am here to ask a boring, useful question: who actually watched that cut before it went live, and what did they say? Because somewhere between the storyboard and the publish button, a lot of smart, well paid people looked at this and nobody hit the brakes. That is not a creative failure. That is a review and approval failure. And it is the exact failure I watch teams repeat every single week with much smaller videos and much smaller budgets.

So let me walk through what a real review process would have done, and why the tool you use for it matters more than people think.

The problem was never the footage. It was the feedback loop

Here is the thing nobody says out loud. Big productions do not skip review. They drown in it. There are decks, there are threads, there are calls, there are "quick thoughts" pinged at 11pm. Feedback exists. It is just scattered, unattributed, and impossible to act on.

When feedback lives in a hundred places, the uncomfortable note is the easiest one to lose. Somebody on that project almost certainly felt off about the ending. Maybe they said it in a hallway. Maybe they buried it in paragraph four of an email nobody opened. The note existed. The system to surface it did not.

“

Bad ads do not happen because nobody objected. They happen because the objection had nowhere to land.

This is the contrarian take I will die on: most teams do not need more opinions on their videos. They need fewer, clearer, traceable ones, pinned to the exact frame, owned by a named person, impossible to ignore. That is a workflow problem. You solve workflow problems with the right surface, not with more meetings.

What frame-accurate review actually changes

When someone leaves a note like "the ending feels tone deaf" in a chat thread, it is a vibe. Nobody knows which second they mean. Nobody knows if it got addressed in version 3. It evaporates.

Now put that same note on the timeline. It sticks to 0:58. It has a name on it. You can draw a circle right on the frame where the can changes hands. The director can reply inline. The strategist can @mention legal. And when the edit changes, the version stacks so you can see v2 and v4 side by side and confirm the fix actually landed.

That is the difference between "someone mentioned a concern once" and "a concern was raised, assigned, and resolved on the record."

This is what frame-accurate comments with drawing and @mentions are for. Not nitpicking pixels. Catching the moment everyone felt weird about but nobody could point to.

A review process that would have caught it

You do not need a 40 page approval bible. You need a short, enforced loop that the uncomfortable note can survive. Here is the one I hand to every team.

Notice step two. The soda ad did not lack talented creatives. It lacked a sceptic with standing, someone whose job was to ask "how does this read to a person having the worst week of their life?" A structured review invites that person in by default instead of hoping they speak up.

And notice the last step. An approval lock is not bureaucracy. It is the moment where someone with their name on it says yes, on the record. When approval is implicit, everyone assumes someone else signed off. When approval is a deliberate lock, the buck stops somewhere visible.

• One canonical version, not five files in five inboxes
• Every comment pinned to a timestamp with an owner
• Legal and brand looped in before publish, not after
• A real approval lock, so "ship it" is a decision someone made on purpose

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

Why the tool you pick decides whether this happens

Here is where I get opinionated. You can have the best process on paper and still fail, because the friction of your tools quietly kills it.

If review means downloading a heavy file off Google Drive, scrubbing in a player with no comment pinning, and replying in a separate email, people will not do the careful pass. They will skim and thumbs up. Email, WeTransfer, Drive and Dropbox are great at moving files. They are not review tools. There is no frame, no version stack, no approval lock, no record of who said yes. The careful objection has nowhere to live, so it dies. Again.

Frame.io is a real review tool, I will give it that. The catch is the pricing model. It charges per seat. On a spot like the soda ad you want the strategist, the freelance editor, the brand lead, outside counsel, and the regional teams all in the room. Every one of those people is another seat, another line on the bill. So the quiet temptation is to keep the circle small to control cost, which is the precise opposite of what you want when you are trying to catch a blind spot. The tool's pricing is fighting your process.

This is why I build review around PlayPause, and yes I am biased, I help make it. The pricing is flat per workspace, not per seat. You add the sceptic, the lawyer, the freelancer, the regional reviewer, and the price does not move. Guest upload means a collaborator can drop a cut in with no account at all. Wide review is the default, not a budget line you have to defend.

And it is not just review. Secure share links carry passwords, expiry, domain restriction and watermarking, so a sensitive cut of a national campaign does not leak from a forwarded link. Version stacks plus side-by-side compare let you prove the fix landed. Premiere Pro and After Effects panels mean the editor never leaves the timeline to read notes. Camera-to-Cloud proxies get footage into review straight from set. Slack, Microsoft Teams and Zapier push approvals where your team already lives. Centralized assets mean there is one source of truth, not a graveyard of "final_FINAL_v7.mov" files. Viewer analytics tell you who actually watched before they approved, which, if we are honest, is the question you most want answered after a spot goes sideways.

A small scenario, the same lesson

Forget the national ad for a second. Picture a five person agency shipping a brand video for a regional client. The editor cuts v1 and drops it in PlayPause. The account lead leaves three frame-accurate notes. The junior strategist, the one nobody would have invited if every seat cost money, pins a comment at 0:42: "this joke lands weird for their audience." The creative director almost waves it off, then watches the moment again and agrees. v2 fixes it. The client gets a watermarked share link with a one week expiry. They approve. Approval lock on. Done.

That junior note is the whole ballgame. Flat pricing is why that person was in the room. The frame-accurate comment is why the note was specific enough to act on. The approval lock is why nobody shipped before the fix. None of it is glamorous. All of it is the difference between a clean launch and a public apology.

Bottom line

The soda ad did not fail because the footage was bad or the people were dumb. It failed because the one note that mattered had nowhere to land, no name on it, and no gate it had to clear. That is a review and approval problem, and it is fixable with a process you can write on an index card and a tool that does not punish you for inviting the right people.

Get the cut into one place. Pin every note to a frame, with a name. Loop in the sceptic, because flat pricing means they cost you nothing. Lock approval on the record before anything ships. Do that, and the uncomfortable note survives long enough to save you.

You can run that exact loop on PlayPause today. The Free plan is 0 dollars and review, frame-accurate comments, version stacks and approval locks are right there. Start a workspace, invite everyone who should have a say, and never let the important objection die in an email thread again. Try PlayPause free.