An agency that runs on individual knowledge is an agency that breaks when people leave, get sick, or go on holiday. Every process that lives in someone's head — how we handle client feedback, what we do when source video arrives late, how we QA before delivery — is a liability waiting to surface at the worst possible moment.
SOPs (Standard Operating Procedures) sound corporate. They don't have to be. At its simplest, an SOP is just a written answer to the question: "What do we do when X happens?" Here are the five SOPs every video agency needs — and how to write them without it becoming a documentation project that never ends.
Why most agencies avoid writing SOPs (and why that's a mistake)
The usual objection is time. "We're busy actually doing client work, we don't have time to write it all down." This is backwards. The agencies that don't write anything down spend more total time on every task because each person is making decisions from scratch that someone else already figured out.
The better objection is that SOPs go stale. You write the process, the tools change, nobody updates the document, and eventually the SOP is worse than nothing because people follow outdated instructions and trust them.
The fix for that is in the SOP format itself — which we'll cover. But first, the five you actually need.
The 5 SOPs every video agency needs
New client onboarding SOP
What it covers: Everything that happens from signed contract to first delivery.
Include: Intake form sent, configuration document created, folder structure set up, kickoff call scheduled (if applicable), test batch produced, test batch approved, full production scheduled.
Onboarding done inconsistently means some clients get a great experience and some get a chaotic one. The difference in retention between those two groups is significant.
Weekly production SOP
What it covers: The repeatable cycle for every active client, every week.
Include: Source video intake deadline, production run timing, internal QA checklist, delivery process, client approval window, what happens if client doesn't respond.
This is the core of your business. If it's not written down, every person on the team runs it slightly differently. The variance compounds into quality inconsistency.
Revision handling SOP
What it covers: What happens when a client requests changes.
Include: How to receive revision requests (specific channel or form), what counts as a revision vs a new deliverable, turnaround time for revisions, what happens when a client exceeds their revision allowance.
Revisions without a clear process turn into unlimited free work. This SOP is the one that protects your margins most directly.
Late source video SOP
What it covers: What to do when client sends their video after your intake deadline.
Include: First time: push to next cycle, notify the client. Second time: same, with a reminder of the intake deadline. Third time: handling fee applies. How to communicate each scenario.
Without a written policy, every late source video becomes a negotiation. With one, you just follow the process and the client knows what to expect.
Offboarding SOP
What it covers: What happens when a client leaves — whether they cancel or you fire them.
Include: Final deliverable checklist, asset delivery process, access revocation steps, how to handle any outstanding invoices, what to archive.
Offboarding done poorly leaves loose ends: clients who still have access to shared drives, outstanding invoices that get ignored, assets that weren't delivered. This SOP closes everything cleanly.
How to write an SOP that doesn't go stale
Most SOP formats are too detailed. Step-by-step instructions with screenshots for every click are thorough but brittle — one tool update makes them wrong. Write at a higher level instead.
The format that holds up:
- Purpose: one sentence on what this SOP covers
- Trigger: what event starts this process
- Steps: what needs to happen, in order, without tool-specific clicks
- Owner: who is responsible for this process
- Review date: when to check if this is still accurate
The review date is the part people skip. Add a calendar reminder for every SOP, 90 days out. When it triggers, spend 10 minutes reading the SOP and asking "is this still how we do it?" That's the entire maintenance burden.
Where to store them
Notion, Google Docs, Confluence — the tool matters less than the consistency. Pick one place, make sure everyone knows where it is, and make sure new team members get introduced to it in their first week. An SOP library nobody knows exists is as useful as no SOP library.
One structural recommendation: keep client-specific information in the client's own folder, not in the SOP. SOPs describe the process. Client configs hold the specifics. That separation means your SOPs don't need updating every time a client changes a preference.
Common questions
What SOPs does a video agency need?
The five core ones: new client onboarding, weekly production, revision handling, late source video handling, and client offboarding. These cover 90% of the situations that create confusion or margin erosion without a written process.
How do you keep agency SOPs up to date?
Write SOPs at process level, not tool level. Add a review date (90 days works well) and a calendar reminder. When the reminder fires, spend 10 minutes checking if the SOP still reflects how you actually work. That's the entire maintenance routine.
How long should a video agency SOP be?
One page maximum, usually less. If an SOP is more than 500 words, it's probably covering two processes that should be separated. Shorter SOPs get read and followed. Longer ones get filed and forgotten.
Scale your short-form without the babysitting
Good SOPs tell your team what to do. Good tools make sure they don't have to remember the client-specific details. Skapo stores every client's configuration so your production SOP stays consistent regardless of who runs the batch.
Try it freePosted by the Skapo team — June 2026