How to Scope a Video Retainer So Clients Cannot Keep Adding Deliverables

Retainer clients are supposed to be the stable revenue that lets you plan your month. In practice, a lot of retainers quietly double in scope by month three because nobody put clear walls around what is included. A social reel becomes a social reel plus a YouTube cut plus a "short version for the CEO's LinkedIn", and suddenly you are doing three deliverables for the price of one.

Scoping a video retainer to prevent deliverable creep is not about being difficult. It is about being professional. Here is how to do it without killing the client relationship.

The Core Problem: Deliverables That Breathe

Most retainer proposals describe deliverables in natural language: "monthly video content", "social assets", "campaign support". Natural language breathes. Clients naturally fill that breathing room with requests, and since nothing was technically ruled out, they assume it is all fair game.

The fix is to replace breathing room with exact counts and format definitions. Not "social videos" but "four 60-second vertical videos, edited from a single shoot day, delivered in MP4 format for Instagram Reels and TikTok". Every word is a boundary. When the client asks for a 16:9 version, you can say with zero ambiguity: that is outside the four vertical deliverables we agreed on.

Write Deliverables as a Table in Your SOW

Put a table in your statement of work. Clients read tables more carefully than paragraphs, and a table makes the scope visually concrete.

When the client asks you to add a landing page cut-down or a 30-second ad version, you pull up this table. The conversation is objective, not personal. You are not saying no to them. You are pointing at a document you both agreed to.

Define What Triggers an Addendum

Every retainer should have a one-paragraph section that describes what happens when something falls outside scope. Something like: "Additional deliverable formats, increased revision rounds beyond those listed, and same-week rush requests outside the standard production calendar are billed at [rate] per hour or agreed as a separate addendum before work begins."

This does two things. It closes the loop on what happens when the scope question comes up, which it always does. And it normalizes the addendum as a routine business process rather than a conflict. You are not pushing back on the client. You are running the process you both agreed to.

How to price extra revision rounds into an agency proposal goes deeper on the pricing mechanics if you want to get specific about how to structure those rates.

The Production Calendar Is a Scope Tool

Here is one that agencies underuse. A monthly production calendar, shared with the client in advance, is one of the most effective scope control tools you have.

When the client can see that shoot day is the 5th, edit delivery is the 14th, revision deadline is the 18th, and final delivery is the 22nd, there is no invisible space for add-ons. Every day is accounted for. If they want to add a deliverable, they can see with their own eyes that there is nowhere to put it in the current cycle.

You can share this calendar as a shared doc or run it through your project management tool. The point is that it is visible to the client, not just internal. Visibility creates accountability on both sides.

Handle the "Just a Quick Version" Ask

The most common scope expansion is the one that is framed as tiny: "Could you just do a quick 15-second version for the story?" It is almost always positioned as something that should take five minutes and therefore should not cost anything.

Be ready for this. Your response should be warm and immediate: "Happy to add a story cut! That will be an addendum to this month's retainer. I can quote that for you today if you want to move forward. It usually runs around [rate] given the additional edit and export."

You have said yes in spirit and no to doing it for free. You have also made it easy for them to say yes to the addendum because you are moving fast and being helpful. A lot of clients will approve it without issue. Some will decide it is not worth it. Either answer is fine.

The one answer you cannot afford is "sure, I'll throw it in" because that trains the client that ask equals receive, and you will be drowning in thrown-ins by month four.

Use the Review Tool as Part of Scope Enforcement

One underrated way scopes expand is through informal feedback channels. The client sends a WhatsApp message asking for a change that was never in the plan. You make it because it feels rude not to. Next month they do it again.

Lock feedback into a formal review channel. When every revision request goes through a structured review link in PlayPause, you have a record of every round. You can see how many revision rounds happened on each video. If a client has used their two rounds and is asking for a third, you have the receipts. "I can see we've used both revision rounds on this one. I am happy to make this change as an addendum or roll it into next month's scope, whichever works better for you."

PlayPause's approval records are also useful when billing. If there is ever a question about whether a video was signed off before the client requests more changes, you have a timestamped, documented sign-off. That is protection for both of you.

• Table-based SOW before work starts
• Addendum clause for out-of-scope requests
• Monthly production calendar shared with client
• Formal review channel only, no WhatsApp revisions
• 60-day scope review built into retainer calendar

Reframe at Onboarding, Not Mid-Contract

The best time to set all of this up is before you start, not after the scope is already slipping. When you are onboarding a new retainer client, spend fifteen minutes walking through the SOW together. Not just emailing it for signature, but actually reviewing it live.

Point to the table. Point to the addendum clause. Say "when something comes up that is outside these deliverables, which it will at some point, here is exactly how we handle it." You have framed it as routine, not defensive. The client has heard you say it, not just read it.

For more on how to structure the agreement language itself, see what agencies should put in their SOW to define video approval and completion and how to write a revision policy clients actually read and respect.

If you want a review and approval system that makes scope enforcement easy and keeps every round documented, try PlayPause free. Guest reviewers are always free, every plan includes version history and approval locks, and the Agency plan at $19 per month covers unlimited projects for one workspace. See the full breakdown at /pricing.