How Many Revisions for an Animated Video? A Studio's Honest Answer
Most advice gives one revision number for a whole animated video. I count rounds per stage instead, and here is the policy and setup that keeps an explainer at two rounds a stage.
Animated video revision advice, at least most of what is out there on how many revisions an animated video should include, is, to be very honest, answering the wrong question, right, because it hands you one number for the whole project, usually two or three rounds. Then it leaves you alone with the fact that an explainer is really four or five separate jobs stacked on top of each other, each with its own cost when somebody changes their mind.
I see this from two seats, right, because my video editing agency lives and dies by revision rounds with our own clients, and on the PlayPause side I spend a lot of my week with small animation studios quoting SaaS marketers. The fight usually starts when the second animation round turns out to be the first time a VP has seen the script, and suddenly nobody can agree which round the project is even on, so the studio quietly eats the difference.
So my answer is two rounds per stage, counted stage by stage, with every person who can veto the video watching from round one, and the rest of this post is how I make that number actually hold at the end of the day.
How many revisions an animated video usually needs
The short version, if you are a marketer holding a quote right now, is that two rounds per production stage is fair and normal, plus one round for the final polish. Most of the studio pages ranking for this question land on two to three rounds as the standard, and the better ones mention one or two per stage, which is basically the same idea said less loudly.
For a typical explainer video of 60 to 90 seconds for a SaaS product, the stages are the script, the storyboard, the styleframes and animatic, the animation itself, and the final pass with voiceover, music and sound. Two rounds on each of the first four and one on the last gives you nine small rounds, which sounds like a lot until you realise that each one has a single person signing off and closes before the next stage even starts, right.
Nine small explainer video revision rounds are far less scary than three big ones, because rounds get cheaper the earlier they happen, and our page on explainer video review and approval covers the PlayPause side of that flow.
Script, storyboard, styleframes and animation each get two rounds and the final polish gets one, so every decision is locked while it is still cheap to change.
Revisions per stage, not per project
The per-project number breaks because the same note costs wildly different amounts depending on when it arrives, right. At the script stage a change is a text edit and maybe twenty minutes of work, at the storyboard it is a redraw of a few frames, and at the animatic stage of production it means re-timing. In full animation that same note can mean a voiceover re-record, new kinetic type, three scenes re-timed to the new read, a fresh render and so on, all for what the client honestly thinks of as one small change.
A worked example for a 90-second SaaS explainer
Say the client is a project management tool and the video is 90 seconds, right, and treat my numbers as illustrative rather than a quote. Each of the nine rounds gets a client review window of two working days, so that is eighteen working days of the client's time on top of production, and I put that math in the proposal on day one. When a marketer sees eighteen days written down, the conversation moves from how many revisions do I get to who on their side needs to clear their calendar for each window.
For instance, say that during animation round one the product team renames a feature. On a per-project policy that is one round out of three, used up, and the client feels fine about it because it was one line. On a per-stage policy it is a script change after the script was locked, which the studio flags and prices before anyone opens After Effects, and that is really really the difference between a healthy project and a studio working weekends for free.
This is also why I push clients hardest at the storyboard as a planning tool, the last cheap place to catch a wrong idea, and if the CMO wanted a phone mockup where the board shows a dashboard, I'm pretty sure you would rather hear it while it is still a sketch.
What pushes an explainer past three rounds
The biggest one by a long way is the late reviewer, right, where the marketer approves the script and the storyboard, then in animation round two the head of product watches it for the first time and has opinions about the messaging, and now round two of animation is secretly round one of the script. It is the pattern I see most in my own agency, which is why we wrote a longer piece on managing too many reviewers.
The second is where the notes live. In my agency, notes that come in over WhatsApp and email at the same time basically double the round, because half the notes contradict the other half and someone has to reconcile them. Then the reconciled list goes back to the client for a check, which is another round nobody counted. The third is vague direction like "make it feel more premium", which the animator has to guess at, and a guess always produces another draft.
The fourth is having no definition of what approved means, so the client says "looks good" on the storyboard but meant it as a direction, while the studio heard locked. Architectural visualisation and 3D product work fight the exact same problems, right, and a lot of what we wrote on cutting 3D rendering revisions applies to animation almost word for word.
A round only counts as closed when every person who can say no has actually watched the draft.
Writing an animation revision policy clients accept
The trick with an animation revision policy is that the client has to be able to read it in two minutes and feel protected by it rather than fenced in, right, so I write it around what they get and let the limits follow from that. When a SaaS marketer asks me which revisions are included in an animated video quote, the answer on paper is the per-stage breakdown above, with the number of rounds and the review window written next to each stage.
Then I define a round in one sentence, which is one consolidated set of notes from one named approver, delivered in one place, within an agreed number of working days. That sentence alone does most of the work, because it kills the drip feed of notes and it makes the client name their approver before kickoff, while everyone is still excited.
Revision or change request
The other line I write into every policy is the difference between a revision and a change, because clients genuinely do not know it until you tell them. A revision adjusts something inside the direction that was already approved, like a slower transition or a bigger logo on the end card, while a change touches something that was locked, like a new line of script or a different product screen, and changes are priced as new work no matter how small they look in an email.
After that come the edges, where extra rounds are priced before the project starts so nobody negotiates in the middle of a deadline, and each stage gets a written sign-off before the next one begins. This is the part that stops scope creep without anyone having to play the bad guy, and our post on writing an agency revision policy has the fuller version I use across the agency.
- Rounds named per stage in the proposal
- One consolidated note set per round
- One named approver per stage
- Changes to a locked stage priced as new work
- Extra rounds priced before kickoff
Counting rounds with version stacks and statuses
A policy is only as good as your ability to count, right, and this is where most studios fall apart. The drafts live as files called things like explainer_final_v3_REAL across three email threads, and nobody can say with a straight face whether this is round two or round four, so this is how we set it up in PlayPause.
Every stage gets its own card, and every new draft stacks on that card as a new version, so the animatic goes up as MV1, the revision becomes MV2, and it carries on to MV3 and MV4 if you ever get that far, and version stacks are on Creator and up. Then we use custom statuses, which every plan has, to name each round in plain words, something like "Animation R1 in review" and "Animation R2 approved", so the status is the round. The catch here is that the count only works if every draft goes on the card, including the quick one somebody sent over chat at midnight.
The client opens one link in their browser, with no account and no install, and every comment sticks to the exact frame, so a note about a tiny logo arrives pinned to the frame where the logo is tiny. They can draw on the frame and leave range comments across a whole scene, which matters a lot for animation because timing notes usually span a few seconds. On Agency and up you also get side-by-side version compare, so you can put MV2 next to MV3 and check every note got fixed before you close the round.
One honest note for animation studios, right, our native editor panel is built for Premiere Pro, so from After Effects the flow is export, upload, review, then take the notes back into your comp. If your finishing happens in Premiere, the Premiere Pro panel shows comments inside Premiere and clicking one jumps the playhead to that frame. There is more on our page for animation studios using PlayPause, and our post on tracking rounds across four stakeholders walks through a longer example.
drafts named final_v3_REAL across email and WhatsApp, and nobody agrees which round it is
MV1 to MV4 stacked on one card with a custom status naming each round
Getting every stakeholder into round one
Everything above only holds if the people who can say no actually watch the draft in round one, right, so this is the part I care about most. At kickoff I ask the marketer for every name that can veto the video, including the founder who probably will not look at it, and all of those people get the same review link from round one, which can be password protected and revoked instantly if the project is sensitive.
The second thing is checking who actually watched before we open round two. Who-watched analytics on Creator and up shows who opened the link, when, and from which city, so if the head of product has not opened the storyboard link, I know round two is going to turn into a surprise. I nudge the marketer now instead of discovering it at animation, and you see what I mean here, the analytics turn a guess into a quick message.
The third is writing down what approved means for each stage. On Agency and up, Playbooks let you keep a per-client document of creative style and direction, and a checklist inside it is not done until every item is ticked, so storyboard approved can mean the messaging, the scene order and the product shots are all signed off. The playbook is shareable as a no-login page, so the client's whole team reads one definition. Brands doing product animation hit the same wall, which we covered in giving 3D product animation notes, and our guide to reducing revision rounds puts the method in one place.
Frequently asked questions
How many revisions are standard for an animated explainer video?
Two rounds per stage is the standard I use and recommend, covering script, storyboard, styleframes with animatic, and animation, plus one round for final audio and polish. Most studios quote two to three rounds for the whole project, which works for tiny videos but breaks on anything with several stakeholders, because the rounds get used up at the expensive stage instead of the cheap one, right.
Should an animation studio offer unlimited revisions?
To be very honest, I would not, and trust me on any level, what clients really want is to feel safe, and unlimited rarely delivers that. Unlimited revisions usually means unlimited late reviewers and a margin that disappears, which we unpacked in our post on whiteboard animation unlimited revisions. Two clear rounds per stage with priced extras feels safer to most SaaS marketers than a vague promise.
What counts as one revision round?
One consolidated set of notes from one named approver, delivered in one place within an agreed window, against one draft. If notes arrive in three batches from three people over a week, that can still be one round, but only if your policy said so before kickoff. Naming each round with a custom status keeps everyone counting the same way, does that make sense, right.
How do I limit revision rounds without annoying the client?
Limit revision rounds by making them generous where changes are cheap and tight where they are expensive, and explain that with one concrete example in the proposal, because clients rarely push back on a limit they understand. Put every stakeholder on the same link from round one, and check who watched before you open round two, so the limit never needs an awkward conversation.
If you run a small animation studio, or you are the marketer trying to keep an explainer on schedule, set up your next project with stages, statuses and one link for every reviewer. Every plan on PlayPause pricing comes with a 7-day free trial, the price is flat per workspace instead of per person, and your clients review without an account anyway.
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