Client Feedback SOP for Video Agencies: From First Link to Final Approval
The client feedback SOP my video agency runs on every project, from sending one review link and naming a consolidator to closing rounds, naming MV versions and recording approval.
Client feedback on launch_film_MV2.mp4 is arriving from two directions at once, and the file sits paused at 00:01:12:08 on my second screen. The client's marketing lead has just sent a WhatsApp voice note saying the stretch around one minute twelve feels slow, right, while twenty minutes earlier their founder emailed to call that exact stretch his favourite part of the video.
And this is the moment it hits me that my agency has a really really solid editing SOP and nothing written down for client feedback. My editor has already started trimming off the back of that voice note, so two people on the client side are pulling in opposite directions and an editor is halfway through a change nobody has agreed on.
So this is the client feedback SOP for video agencies that runs inside my agency now, sitting right next to our production SOP. It covers how the link goes out, who sends notes, how a round closes, how versions get named and how approval gets recorded so nobody argues about it later.
Why a client feedback SOP for video agencies needs its own document
Most agencies I talk to already have a production SOP, right, the document that says how projects get set up, how files get named and so on, and ours is written up in a post production workflow for agencies. The catch here is that a production SOP only controls what happens inside your building, while feedback is the one place where somebody from outside gets to put their hands on the work.
So the feedback SOP has a different owner, and in my agency that is the account manager or producer on the client, never the editor. The editor makes the changes, and the producer makes sure they are the right changes arriving in one clean batch. When those two jobs blur, notes coming in over WhatsApp and email at the same time basically double the length of a round in my agency, you see what I mean here.
The goal is that every round runs the same way no matter which editor is cutting and which client is watching. That is the whole idea behind our client approval workflow for video, and it's the biggest lever I know if you want to reduce video revision rounds without being rude to anyone.
notes arrive on WhatsApp and email, two client voices contradict each other and the editor guesses which one wins
one link, one consolidator per client, frame comments only and a round that closes on an agreed date
Step one: sending the review link
The link goes out from the producer, right, never from the editor, and it is one link per deliverable. So a 60 second hero film and three cutdowns means four cards and one message pointing to all of them. With PlayPause the client opens the link in a browser with no account and no install, which matters because the moment a client has to sign up to give feedback, they drift straight back to WhatsApp.
The message carrying the link is basically a template, and ours reads something like "MV1 of the hero film is ready, we want notes on story, pacing and on-screen text since colour and the mix come next round, please leave everything in the link by Thursday 5 pm and your consolidator will confirm when you're done." I'm pretty sure that one message prevents more confusion than anything else in the process. It names the stage of the cut, the kind of note that helps right now, the close date and whose word is final on their side.
For anything unreleased, like a launch under embargo, we use a password-protected link and send the password in a separate message. If a link gets forwarded somewhere it shouldn't, we revoke it instantly and send a fresh one. Link life matters too, right, because Creator links last 30 days and the files expire, Agency links last 90 days and Enterprise links never expire, so we pick the plan by how long our clients actually take to watch.
After that the producer checks who-watched analytics, which on Creator and up shows who opened the link, when and from which city. If nobody has opened it by Wednesday, we nudge the consolidator instead of assuming that silence means approval.
Step two: how clients should leave notes
This is where most of the confusion lives, because clients describe time the way normal people do, right, they say "around the one minute mark" or "the bit where she smiles". An edit is measured in SMPTE timecode down to the individual frame. Depending on the frame rate one second holds 24, 25 or 30 frames, so "around 1:12" can point at dozens of possible cut points and the editor ends up guessing.
So our kickoff email walks the client through the tools in the link before the first cut. A frame comment is for one moment, for instance a typo in a lower third, and in PlayPause it sticks to the exact frame so the editor lands on it directly. A range comment is for a stretch, like "00:41 to 00:58 drags", which is the comment clients need most and almost never know they can leave. Drawing on the frame is for anything spatial, like moving a logo, because one circle saves a whole paragraph.
Back on that launch film, under this SOP the voice note becomes a range comment from 00:01:08 to 00:01:16 saying the section drags. The founder's email becomes a threaded reply right under it, so the disagreement sits on the exact frames it is about and nobody on my team touches the timeline until it's settled.
There are two more rules here that clients push back on at first and end up very very grateful for. The first is one idea per comment, because "logo bigger, music quieter and can we try a different ending" turns into several tasks that get resolved at different times. The second is that nothing outside the link counts, so voice notes and screenshots don't exist as far as the round is concerned. Questions go in a threaded reply on the comment, so the question and the answer live on the same frame. I go deeper into note shape in structuring a video feedback document, and our video feedback and review page covers the client side.
A comment that bundles several changes gets resolved at several different times, so ask clients to give every note its own frame or range comment.
Step three: consolidating and clarifying notes
Before the project starts, every client names one consolidator, right, one person who makes sure whatever sits in the link at close is the brand's actual position. On the launch film the consolidator reads the range comment and the founder's reply and makes the call in that same thread, so the editor never sees two contradicting notes on one frame. Clients accept this easily when you pitch it as protecting their own time.
On our side, the producer reads every comment before the editor touches anything, answers what can be answered in the threads, @mentions the editor on anything technical and sends contradictions back to the consolidator. Slack is on Creator and up, so every comment lands in a Slack channel as it arrives. Permanent rules, like a logo that always sits bottom right, go into a brand Playbook on Agency and up. Since Playbook checklists are not done until they're ticked, it's basically a quality check the editor runs before every upload.
- Every client question answered in its own thread
- Technical notes tagged to the editor with a mention
- Out of scope notes parked for a later round
- Contradictions sent back to the client consolidator
- Permanent brand rules moved into the client Playbook
The editor should never be the one deciding which of two client notes wins, does that make sense, right, because the editor has neither the context nor the relationship to make that call. This producer layer is also why the feedback SOP matters most once you grow past a handful of clients, which I go into in scaling a video editing agency.
Step four: closing a round and uploading the next MV
A round closes on the date in the link message or when the consolidator says they're done, whichever comes first, and anything later goes into the next round. A round that never closes is just a slow conversation with an invoice attached, right. So the producer sets a custom status we call Changes requested, and from that point the editor works only from what's in the link.
In practice a hero film round in my agency runs on a weekly rhythm, so MV1 goes out Monday morning with a Thursday 5 pm close and the producer checks analytics on Wednesday. Consolidation happens Friday morning and MV2 goes out the following Tuesday, so everyone knows exactly when notes stop moving.
Version naming gets messy really fast, so we borrow one rule from version control in software, which is that every round produces a new numbered version and nothing overwrites anything. In PlayPause the first cut is MV1, then MV2 and so on, and with version stacks on Creator and up they all sit on the same card, so the client never watches an old cut. On Agency and up we put MV3 next to MV2 in side-by-side version compare before it goes out, to check every note from the round is done.
Our Premiere editors use the PlayPause Premiere Pro panel, where comments show up inside Premiere, clicking one jumps the playhead to that frame and the next MV uploads straight from the timeline. Our Resolve and Final Cut Pro editors export, upload, review and then work through the notes in their own editor, which is fine as long as the SOP says so. I wrote more about that side in building a revision loop that closes.
Step five: recording approval
Approval is the step everyone forgets to write down, right, and then three weeks later there's an argument about whether the client approved MV3 or just stopped replying. In our SOP approval only counts when the consolidator writes it as a comment on the exact version, something as simple as "approved for delivery". The producer then sets the Client approved status on that card, so the approval sits on that specific MV with a name and a time attached.
Custom statuses are on every plan, and we use In edit, In review, Changes requested and Client approved across the agency, so anyone opening a project can tell where it stands without asking. If a project ever turns into a "we'll pay after one more round" situation, that record keeps the conversation calm, and I've written separately about clients who delay payment for revisions. Trust me on any level, the five seconds it takes to set that status will save you a very uncomfortable phone call one day.
If approval is not written on the exact version, it did not happen.
A video feedback SOP to copy
If you want the condensed version as a video feedback template for your own docs, this is the client revision process for video exactly as my producers run it, so swap in your own names and dates.
- At kickoff, the client names one consolidator and agrees the round dates.
- The producer sends one review link per deliverable, password-protected if unreleased.
- The link message states the stage, what to review, the close date and the consolidator.
- Clients leave frame comments, range comments or drawings, one idea per comment.
- Client questions go in threaded replies on the comment, never in WhatsApp or email.
- The producer consolidates, @mentions the editor and moves permanent rules into the Playbook.
- The round closes on its date, and the next cut uploads as the next MV on the same card.
- Approval is a written comment on the exact version plus the Client approved status.
New editors learn this in their first week as part of our video editor onboarding process, because an editor who knows the feedback rules stops treating every WhatsApp message as an instruction. Wedding work runs on the same SOP with a softer tone, which is how we approach delivering wedding videos to clients, and at the end of the day the structure stays the same whoever is on the other side.
Frequently asked questions
What is a client feedback SOP for a video agency?
It's the written process for everything between sending a cut and getting it approved, right, so who sends the link, who on the client side consolidates, how notes are left, when a round closes, how versions are named and how approval is recorded. It sits next to your production SOP and belongs to the producer or account manager rather than the editor.
How many revision rounds should the SOP include?
In my agency we include two rounds in the quote and price anything after that as extra, and we say so in the kickoff call so it never feels like a surprise. The number matters less than the rule that every round has a close date, because two rounds that close cleanly will always beat four rounds that drift into each other over WhatsApp.
What if the client refuses to use the review link?
To be very honest this happens less than people expect, because the client opens the link in a browser without an account or an install. When it does happen, the producer copies the note into the link as a comment on the right frame, notes who it came from and replies there, so the round still lives in one place.
Does this SOP work for editors outside Premiere Pro?
It works the same way, because the SOP lives in the review link rather than in the editing software. Premiere Pro editors see comments inside the panel, while editors on Resolve, Final Cut Pro or After Effects export, upload, review and then work through the notes in their editor, so the client side doesn't change at all.
If you want to run this SOP on PlayPause, every plan starts with a 7-day free trial, and you can see what Creator, Agency and Enterprise each include on the PlayPause pricing page before you set up your first client.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free