Animation Production Pipeline: Where Every Review Gate Belongs
A stage by stage map of the animation production pipeline, showing where each review gate belongs, who signs it, and how statuses and version stacks keep every shot honest.
The animation blocking pass for shot 14 is open in my browser, sh014_blocking_v03.mov, and the client's comment pinned at 00:00:41:12 says the hand reaching for the bottle should feel a little more confident. That's a completely fair note, right, except the lighter finished that exact shot on Monday and the comp is already half built on top of it.
So the animation production pipeline on a 45-second 3D product spot has just let a blocking note walk straight into the lighting stage, and I've seen some version of this moment play out more than once. Nobody did anything wrong, the animator did solid work and the client is being honest, but the blocking gate was never properly closed, it got a thumbs up on WhatsApp on a Friday and everyone downstream treated that as a signature.
And to be very honest, this is the most common way I see small studios lose a week, because the stages are usually fine but the gates between them are basically vibes. So here's the full pipeline from story to final, where each review gate belongs, who signs it, and how I set that up inside PlayPause, including where it stops and a production tracker takes over.
The animation production pipeline stage by stage
Every team names the stages a little differently, and the names matter far less than the order. For client work, a 3D animation pipeline starts with story and script, moves into storyboard panels and thumbnails, then into the animatic as a timed cut with scratch audio, before anything gets built. Here's how I write the stages down, each with the one question its review has to answer:
- Story and script: is the message clear, and does it fit the runtime?
- Storyboard: does every beat have a shot, and does the staging read?
- Animatic: does the pacing work against the scratch voiceover?
- Layout: are the cameras, lenses and framing locked?
- Blocking: do the key poses and timing sell the performance?
- Polish: does the motion carry weight, overlap and clean arcs?
- Lighting and comp: does the look match the approved hero frames?
- Final: is the film finished, with sound, grade and delivery specs right?
The 2D animation workflow follows the same logic with different labels, right, so you get boards and an animatic, then rough animation, line test, cleanup and color, and comp. I've written separately about tracking notes across line test, color and render passes, because that's where 2D teams quietly bleed time.
The one idea I really really want producers to keep is that every stage multiplies the cost of a change made in the stage before it. A timing change in the animatic is a quick drag in the edit, the same change in blocking costs an animator an afternoon, and after lighting it means a re-render, a comp rebuild and an awkward call about the schedule, so the whole animation production process is basically a bet that you'll catch each decision while it's still cheap.
Where review gates belong and who signs each one
The way I think about gates is pretty simple, right, the client signs wherever a change is still cheap and they can actually judge the work, and the lead signs wherever the work is too rough or too technical for a client to read. The producer's whole job is making sure no shot moves forward without the right signature on it, does that make sense, right.
So the client signs the script and the animatic first, and the animatic is the biggest lever in the whole thing, which is why I keep pointing people to storyboard to animatic approval. The client signs blocking too, because that's where timing and staging become real, and a client who approves poses at blocking won't be surprised by those poses at final.
Layout is mostly internal with a quick client look at framing on the hero shots, and polish is fully internal, owned by the animation lead in something close to traditional dailies with the whole team. Lighting goes back to the client on a few hero frames per sequence, because showing every lit shot invites fresh notes on poses they already approved, and I wrote the longer version in reviewing lighting passes with a director.
Comp stays internal, and final is the client's last signature, which should be about the finished film rather than a sneaky second round of blocking notes. The catch here is that clients will reopen early stages at final if you let them, and in my agency that usually happens because nobody showed them clearly what they already signed. For shorter work, the explainer video production process post maps the same thinking onto six stages.
- Client signs the animatic before layout starts
- Blocking approved in writing on the shot itself
- Polish stays internal with the animation lead
- Lighting shown to the client on hero frames only
- Final review limited to finish and sound
Turning animation pipeline stages into custom statuses
This is where PlayPause comes in, right, and the first thing I set up on any animation project is custom statuses, which every plan has. A status that says Blocking approved on a shot card is a gate the whole team can see, while a gate that lives in a producer's head is basically a rumour.
I make one status per gate, so for instance Animatic in review, Animatic approved, Blocking client review, Blocking approved, Polish internal, Lighting client review, Comp internal and Final approved. The rule I run is that only the producer moves a shot into an approved status, and nobody starts the next stage until the card shows that approval, and trust me on any level, that one rule saves more weeks than any software feature ever will.
On the client side, the reviewer opens one link in a browser with no account and no install, and every comment sticks to the exact frame, so the note at 00:00:41:12 lands where the hand actually is. For blocking, the client can also draw the arc they want on the frame, or drop a range comment across a hold that feels long, and the fuller setup is on the PlayPause for animation studios page.
A worked example on a 12-shot spot
Say that 45-second spot is cut into 12 shots across two sequences, the kitchen and the product reveal, so you have one animatic card and 12 shot cards split across two folders. The client signs the animatic once, and from then on every gate closes per shot rather than per film, right, so if shots 4 and 9 come back from blocking with notes, those two go round again while the other ten move into Polish internal.
Counting it out, that's one animatic signature, 12 blocking signatures, a few lit hero frames per sequence and one final, and each one is just the producer moving a status after the client has written approved on the shot. The slow shots never hold up the fast ones, and the lighter never opens a shot whose card doesn't say Blocking approved, which is exactly what would have saved shot 14.
Version stacks from animatic to final render
Statuses tell you which gate a shot is at, and version stacks tell you how it got there, and you need both, right. On Creator and up, every new pass stacks on the same card as MV1, MV2, MV3, MV4, so the shot carries its own history the way version control in software keeps every commit, and nobody hunts through files named final_v2_really_final.
I use one folder per sequence and one card per shot, and the stack follows the shot through the stages, so for instance MV1 is the first blocking pass, MV2 is blocking with the client's notes addressed, MV3 is polish and MV4 is the first lit render. The animatic gets its own card, because it's reviewed as a film rather than shot by shot, and our animatic review for animation teams page goes deeper.
Guest version upload, on Agency and up, helps with freelancers, because a freelance lighter can drop a new pass onto the card with just a name and email, without joining your workspace. I'm pretty sure a big chunk of version confusion in small studios comes from files sent over chat, and brands reviewing product shots hit the same mess, which I covered in notes on 3D product animation.
Comparing passes side by side
The most underrated check in the pipeline is the one between two passes of the same shot, right, because you want to know whether the notes got addressed and whether anything else quietly moved in the process.
Side-by-side version compare is on Agency and up. When polish comes back as MV3, the lead opens it next to MV2, the approved blocking, and that's where you catch a camera nudged a couple of frames or a pose that drifted from what the client signed, which nobody spots flipping between browser tabs.
It's equally useful at final, because when someone tries to reopen timing, you put the final next to the approved blocking, and that conversation goes very very differently with both versions on screen. You see what I mean here, everyone is looking at the same evidence.
two browser tabs, two timecodes and a guess about what changed between passes
the new pass next to the approved one on the same shot card
Folder playbooks for per-sequence direction
The last piece is direction that doesn't belong on any single frame, like palette and motion rules, and that's what Playbooks are for on Agency and up. A brand playbook holds a client's permanent rules, for instance the logo never squashes and the product is never shot from below.
Folder playbooks are where this gets really practical, because you write one per sequence folder, so the kitchen sequence might say warm key from the window and every hero hold on the product lasts at least eight frames. Checklists in a playbook aren't done until somebody ticks them, so the lighter ticks that the rim light matches the product reveal before moving a shot to Lighting client review. Playbooks also share as a no-login page for a freelancer on day one, and our review for cartoon and series work page shows how this works across episodes.
A gate only works when the person signing it can see exactly what they signed and the rules it was judged against.
Where a review tool fits next to a production tracker
Now the honest bit, right, because PlayPause doesn't run your whole production, it's the review layer and that's where it stops. Bids, schedules, artist assignments, render queues and so on belong in a production tracker, whether that's a dedicated tool or a well kept spreadsheet, and the producer updates it by hand when a status changes in PlayPause.
What PlayPause adds is visibility, so on Creator and up every comment can land in a Slack channel, and who-watched analytics show who opened the blocking link, when, and from which city. If your animatic is cut in Premiere, the Premiere Pro panel shows comments inside Premiere and jumps the playhead to each note, while for After Effects, DaVinci Resolve or Final Cut Pro the flow is export, upload, review, then work through the notes in the app. Studios closer to VFX might also like my shot review workflow for small VFX studios without a pipeline team.
At the end of the day the split is clean, the tracker answers who is doing what by when, and PlayPause answers what the client saw and what they signed. For a studio of five to forty people I'd start on Agency, since compare, guest upload and Playbooks all live there and the price is flat for the workspace.
Frequently asked questions
What are the main animation pipeline stages?
For most client work it's story and script, storyboard, animatic, layout, blocking, polish, lighting and rendering, comp, and final delivery. A 2D studio swaps blocking and polish for rough animation, line test, and cleanup and color, but the logic stays the same, right, every stage locks a decision, and every review gate makes sure that decision is locked before the next team builds on it.
How many client review rounds does a 3D animation pipeline need?
The way I set it up, the client signs four times on a typical spot, at script, animatic, blocking and final, with a look at lit hero frames in between. Each one sits where a change is still cheap, and adding more client rounds usually means the earlier gates weren't closed properly, while internal rounds with the lead can happen as often as the team needs.
Can PlayPause replace our production tracker?
Not really, and I'd rather say that upfront. PlayPause is the review layer, so it holds the shots, the frame-accurate notes, the versions and the approvals, while schedules, bids, assignments and render queues stay in your tracker, and the producer updates that tracker whenever a shot changes status in PlayPause.
Does a 2D animation workflow need different review gates?
The gates sit in the same places and only the names change. The client still signs the animatic and something equivalent to blocking, which in 2D is usually the rough or the line test, then cleanup and color are reviewed internally, and the client comes back for comp and final. Range comments are really useful in 2D, because timing notes often cover a few drawings rather than a single frame.
Where to start this week
Pick the project on your slate that's furthest from delivery, write its gates on one page with a name next to each signature, and turn them into statuses before the next shot goes out, because I'm pretty sure you'll find at least one gate that currently closes with a thumbs up.
If you want to try this on a live project, every plan comes with a 7-day free trial, and the PlayPause pricing page shows what each plan includes, so set up one sequence, run one shot through every gate, and see whether a stray blocking note like the one on shot 14 can still reach your lighter.
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