Video Editing SOP Template: One Playbook per Client, Zero Repeat Notes
Repeat client notes are a memory problem. This is the video editing SOP template I run in my agency: a brand playbook, folder playbooks and checklists editors must tick.
Say one client sends you 20 videos a month and one in every five comes back with a note you have already heard, like the logo belongs in the bottom right corner, right. That's 4 extra rounds a month, and if each round eats about 45 minutes of fixing, exporting, uploading and checking, you are losing 3 hours a month on one client for a problem you already solved once.
That is illustrative math, not a measured number, but stretch it across eight clients and a couple of subcontract editors and you see very very quickly where the margin goes. The fix I landed on in my own agency is a video editing SOP template, basically one per client, because the note was given once, to one person, and the next editor on the next video simply never heard it.
So in this post I'll walk you through what goes into that template, with a filled-in example you can copy, how I split permanent client rules from per-project instructions, and how we run the whole thing inside PlayPause using Playbooks so it never goes stale.
Why editing teams keep getting the same client note twice
Every repeat note I have ever traced back in my agency comes from the same place, right, the rule lived in one person's head. The client said it on a call, or dropped it in a WhatsApp voice note to that week's editor, and that editor followed it perfectly. Then two weeks later the next video went to a different subcontract editor who had never seen that chat, and the logo went straight back to the top left corner.
The catch here is that nobody actually did anything wrong in that story. The second editor did a good edit by their own standards, and the client still feels like they are repeating themselves, which to be very honest is the most dangerous feeling a client can have about an agency, because it reads as carelessness.
A proper standard operating procedure is the boring answer to this, a written set of steps that anyone can follow without needing the person who wrote it. Editing teams mostly don't have one, because editing feels creative and SOPs feel like paperwork, so the rules live in chats and we hope they survive every handover.
I've written before about how clients who skip the brief quietly eat agency margins, and repeat notes are the same leak from a different pipe, because on a flat retainer every extra round is time you are not billing for, right.
The client told someone once, and that someone was not the editor on this video. A written SOP lets the rule outlive the conversation.
What belongs in a video editing SOP template
The generic SOP templates I looked at when I built our first one leaned towards the agency's internal process, file naming, handoffs and so on. That stuff matters, but my repeat notes were almost always about the client's taste, so the template I use is basically a style guide for one client, written so a new editor can make the first cut look like the fifth.
The first block is the look, right, so fonts with exact weights, colour codes, where the logo sits and how big it is, safe margins and the lower third style. The second block is captions, which is where most of my repeat notes used to come from, so I write down size, case, words per line and the highlight colour, because trust me on any level, one client's fun captions are another client's nightmare.
The third block is sound and pacing, so the music they like, how loud it sits under voice, whether zoom punches are welcome, how dense the B-roll should be and how long the hook runs. The fourth block is things to avoid, which people forget, like a competitor's product on screen or a phrase the founder hates. The last block is delivery, meaning aspect ratios, export settings, file naming and who gives final approval.
- Fonts, colours and logo placement
- Caption size, case and words per line
- Music style and how loud it sits under voice
- Pacing, zooms and B-roll density
- Words, products and colours to avoid
- Export specs, file naming and approver
A filled-in example you can copy
Here is roughly how one brand playbook reads, with made-up values for an imaginary podcast clips client, because "use the brand font" is not a rule an editor can check against.
- Fonts: Montserrat Bold for captions, Inter Regular for lower thirds, nothing else
- Logo: bottom right, about 8% of the frame width, hidden during the hook
- Captions: sentence case, four words per line at most, the spoken word in brand yellow
- Sound: soft acoustic music sitting well under the voice, never over the first line
- Pacing: hook done inside 3 seconds, one zoom punch on the key line, B-roll every 6 to 8 seconds
- Avoid: the old logo, any rival app on screen, the word "hustle"
- Delivery: 9:16 at 1080 by 1920, named by client, episode and clip number, the founder approves
Every line there is something an editor can check with their own eyes before export, right, and that is the test I run on every rule. If your client and editor keep talking past each other, a plain glossary of editing terms helps, because half the rules clients give you arrive as "make it pop" and need translating first. And if the client already has a brand document, my older post on building a brand style guide covers that side.
Permanent client rules versus per-project instructions
The split that made the whole thing actually work for us was separating what never changes from what changes every project, right. When everything goes into one document, the permanent stuff like the font gets mixed with temporary stuff like this month's red CTA card, and editors start skimming, and the moment they skim, the SOP is basically dead.
So inside PlayPause we use Playbooks, which is a per-client document of creative style and direction, and it has two layers. The brand playbook holds the permanent rules, the fonts, the logo placement, the caption style, everything that should be true on video 1 and on video 200. Folder playbooks sit on each folder, so a six-part launch campaign can carry its own instructions, like how a sponsor's product placement should look, without touching the permanent rules.
For instance, on podcast clients in my agency, the brand playbook says how captions and logos look across everything, and each episode folder carries the guest's name spelling and any topic the guest asked us not to use. The editor reads the folder playbook for that episode and the brand playbook for the client before cutting, so they get both layers without me forwarding a single message.
The brand playbook changes rarely and the folder playbook changes every project, and keeping them apart stops the permanent rules from getting buried, does that make sense, right. I touched on this when writing about onboarding a new YouTube editor, because the brand playbook is the first thing a new editor should read on day one. The page on creative project management and review shows how folders, reviews and playbooks connect.
permanent rules and this month's notes mixed in one long doc that editors skim
a brand playbook for permanent rules and a folder playbook for each project
Checklists that are not done until they are ticked
Most SOPs quietly fail at this point, and I'm pretty sure it's the part that matters most. A rule that an editor has to remember is still a memory problem, because at 1 am on a deadline nobody rereads a two-page document before hitting export.
So the part of our video editing checklist template that does the heavy lifting is the checklist itself, right. Playbooks let you add checklists, and a checklist is not done until it is ticked, which sounds small but changes the behaviour completely. Before uploading MV1, the editor goes down the list, logo placement, caption case, no music under the testimonial and so on, and if one item is not ticked, the checklist is simply not done.
I keep it short, maybe eight to twelve items per client, and I only add things that have actually come back as notes, because a checklist with forty items becomes the same skimmed document we were trying to escape. The brand playbook holds the detail and the checklist holds the mistakes that already cost us a round.
In my team the Owner or an Admin sets up the brand playbook, a Manager usually owns the folder playbooks and the Editors tick the checklists before every upload. The video production workflow page shows how that fits alongside custom statuses and reviews.
If an editor has to remember a rule, sooner or later someone forgets it, so make them tick it instead.
Share the SOP with the client for a sign-off
I skipped this step for a long time, and to be very honest I think most small agencies skip it too. You write the SOP from your own notes, so it's based on your interpretation, and part of it is slightly wrong, like no music under talking when they meant no music under the founder talking.
So once the brand playbook is ready, I share it with the client as a clean page, and they don't need an account or a login to read it. I ask one question, whether anything here is wrong or missing, and give them a day. Most clients either say it looks right or correct two or three lines, and those lines are exactly the repeat notes we would have got later, right.
I treat that sign-off as part of onboarding, the same way I treat the approval clauses in a video editing contract template. I've also started mentioning it in the pitch, because a proposal that sells your review process lands better when the client sees you'll write their rules down.
These client editing guidelines then live in the same place as the review itself. The client opens one link in the browser, leaves frame-accurate comments, draws on the frame when the logo is off, and every new version stacks on the same card. So when they say the caption looks too big, the editor can check it against the rule the client already signed off on.
Keep the SOP alive after every revision round
An SOP that never changes is basically a museum, and the client's taste does change, right, they rebrand or they see a reel somewhere and suddenly want faster cuts. So the habit I push on my team is simple, after every revision round you look at the notes and ask whether each one is a rule or a one-off.
If the client says trim this pause at 0:42, that's a one-off and it stays in the comment thread. If the client says never let B-roll cover my face when I'm making a point, that's a rule, so it goes into the brand playbook the same day, and onto the checklist if it already cost a round.
Every cut goes up as MV1, MV2, MV3 and so on, and on the Agency plan and up you get side-by-side version compare, so when a note keeps coming back I can see exactly where the rule got broken.
Editors in Premiere can use our Premiere Pro panel, which brings the comments inside Premiere, and clicking one jumps the playhead to that frame. Editors on DaVinci Resolve or Final Cut export, upload, review in PlayPause and then use the notes in their editor. If you run a bigger studio, the page for post-production houses covers how this scales, and a clear revision policy for scope creep keeps the rounds you do run about real creative changes.
At the end of the day, the number I care about is how many notes we hear twice, and in my experience that number drops really really fast once the rule lives somewhere other than someone's memory.
Frequently asked questions
Do I need a separate SOP for every client?
For the client-specific part, I'd say you do, right, because repeat notes come from each client's taste, and one master document for everyone just gets ignored. I keep one internal video editing standard operating procedure for how my team works, covering file naming, review steps and delivery, and then a brand playbook per client for their look, captions and rules. The internal one barely changes, while the client ones change every month or two.
Which PlayPause plan includes Playbooks?
Playbooks come with the Agency plan and up, so Agency at $19 a month or Enterprise at $27 a month, and both are flat per workspace instead of per member. Agency gives you 50 members and 250 GB of storage. The Creator plan at $9 doesn't include Playbooks, so if the SOP workflow is the main reason you're looking, start on Agency.
Can my client read the SOP without creating an account?
They can, and that's basically the whole point of the sign-off step. You share the playbook as a clean page, the client opens it in the browser with no login and no install, and tells you what is wrong or missing. Reviewing the videos works the same way, one link, comments on the exact frame, and no account at any point.
How is this different from a brand style guide?
A brand style guide is usually written by the brand for everyone who touches it, designers, social teams and so on. An editing style guide per client is narrower and more practical, written by the agency only for editors, and it covers things a brand guide never mentions, like words per caption line or how long the hook runs. I often start from the client's brand guide and pull only the video bits into the playbook.
If you're tired of hearing the same note twice, start with one client tonight, write their brand playbook, add a checklist built from the last five notes they gave you, and share it with them for a sign-off. You can set all of this up on the Agency plan with the 7-day free trial, and every plan is laid out on the PlayPause pricing page.
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