Nobody leaves an agency over one bad post. They leave over the fourth round of edits on a post that was fine in round one — and so does your designer, who has now rebuilt the same static three times while this month's actual work piles up.
Revisions aren't the problem. Revisions are the job; the client knows their business better than you do, and round one usually makes the work better. The problem is unbounded revisions with no record, arriving as voice notes at 11 PM. Here's the system that fixed it at my agency, and the one uncomfortable truth underneath it.
Why do revisions spiral out of control?
In my experience it's almost never a difficult client. It's one of four structural failures:
- The wrong person is approving. The marketing executive approves, then the founder sees the post on the feed and hates it. That's not round four — that's round one, arriving late, because the actual decision-maker was never in the loop.
- Feedback trickles. Three WhatsApp messages on Monday, one more on Tuesday, a voice note on Wednesday. Your designer implements each one as it lands and rebuilds the file four times. Consolidated feedback — everything in one pass — is the single biggest lever here, and it's the one thing every practitioner guide agrees on.
- Nobody can find the current version. When approvals live in WhatsApp and files live in Drive, version control collapses — you're scrolling a chat thread to work out whether v3 or v4 was the approved one. Sometimes the wrong one goes live.
- No round limit exists. If nothing in the contract says how many rounds are included, the honest answer is infinite, and the client is not wrong to keep asking.
How many revision rounds should you include?
Two. The industry standard sits at one to two rounds, and for social content two is the honest number: round one catches the real problems, round two confirms they're fixed. A third round almost never improves the post — it means the brief was wrong, or a new stakeholder just walked in.
The point of the limit isn't to punish anyone. It's that a stated limit changes client behaviour before the feedback arrives: when people know they have two rounds, they read the whole calendar properly and send everything at once. An unlimited process invites the trickle. Write it into the retainer as a term:
| Clause | What it says | Why it works |
|---|---|---|
| Revision rounds | Two rounds per post included; further rounds billed at ₹X or drawn from a change budget | Makes round three a priced choice, not a fight |
| Consolidated feedback | All feedback for a round arrives together, in the approval tool | Kills the trickle; one rebuild, not four |
| Feedback window | Feedback due within 48 working hours of submission | Silence can't quietly become your delay |
| Deemed approval | No feedback in the window = approved, and it publishes | Stops one slow approver freezing the calendar |
| Freeze date | No changes to the approved calendar after the 30th | Protects a month of production from a last-minute rethink |
| Scope of a revision | Edits to an approved concept; a new concept is new work | Draws the line between "fix the CTA" and "redo it" |
That last row is the one agencies forget, and it's where the money leaks. "Change the offer text to 20% off" is a revision. "Actually, let's make it a reel instead" is a new post wearing a revision's clothes. Naming the difference in writing means you can say it out loud later without it sounding like a fight.
What is a content freeze date — and why does it matter in India?
A freeze date is a fixed day each month after which the approved calendar cannot change; anything raised later goes into next month's queue. It's what stops one Thursday-evening request from dismantling three weeks of work.
Indian agencies need one more than most, for a specific reason: the festival calendar. A Diwali or Raksha Bandhan campaign is produced weeks ahead, and it's exactly the campaign a client wants to "just tweak" on the 29th — when every other client wants the same thing in the same week. A freeze date on the 30th, agreed in the retainer, is what lets you say "that's a January change" without it landing as a refusal.
Pair it with an escape hatch, because real urgencies exist: an urgent post-freeze change is allowed, it just goes through the founder and it's billable. Clients accept this readily. What they don't accept is a flat no.
Track revisions against the post, not the conversation
Every rule above is unenforceable if you can't prove what happened. "This is round three" is an opinion when your evidence is a WhatsApp thread; it's a fact when the post carries its own history.
What to capture on each post: the version, who requested the change, what they asked for, when, and which version actually published. That's it — five fields, and they change the conversation completely. When a client can see they've requested four rounds on one static, the behaviour corrects itself without you ever having to be the difficult one. It also protects your team from the reverse accusation: the post that went live is the post that was approved, and the record says so.
This is why we moved approvals off WhatsApp entirely and into a client approval app: not because WhatsApp is bad at messaging, but because it's a conversation, and revisions need to be a record. The four-stage approval workflow we use — draft, internal QC, client review, scheduled — gives each revision a place to live. Round three physically cannot get lost, because it's attached to the post, not to a chat.
And the payoff compounds at month end: when revisions are logged against posts, you already know which client is running four rounds a post. That's not a grievance to air — it's data for the renewal conversation, and it tells you whether the retainer is priced right. A client averaging four rounds isn't a bad client. They're an underpriced one.
The uncomfortable part
Most revision spirals are an agency problem wearing a client costume. Vague briefs, no QC before it reaches the client, the wrong approver, no record. Fix those four and revision rounds drop on their own — before you've enforced a single clause.
The clauses are the backstop, not the strategy. If you're reaching for the round limit every month, the limit isn't what's broken. Start with an internal QC step so nothing sloppy ever reaches the client, put the real decision-maker in the approval seat during onboarding, and watch how many "difficult clients" quietly stop being difficult.
Frequently asked questions
How many revision rounds should a social media retainer include?
Two is the industry norm, and two is right for social. Round one catches real problems, round two confirms they're fixed. A third round almost never improves the post — it means the brief was wrong or a new stakeholder appeared. Write the number into the retainer so it's a term, not an argument.
What is a content freeze date?
A fixed day each month after which the approved calendar cannot change. Revisions raised after the freeze go into next month's queue, unless the client pays for an urgent change. It protects a month of production work from being dismantled by a last-minute request.
How do you handle a client who keeps changing their mind?
Usually the wrong person is approving. Get the actual decision-maker into the approval step, insist feedback arrives consolidated in one pass rather than trickling in, and keep a visible revision history. When a client can see they've asked for four rounds, the behaviour corrects itself without a confrontation.
Give every revision a place to live.
Approvals, revision history and version tracking attached to each post — plus scheduling, reports and GST invoicing in one login. 7-day free trial, from ₹999/month for your whole team.
Start Free Trial