How to Give Animation Feedback on a Blocking Pass That Sticks

Blocking notes in my agency used to be a single WhatsApp line typed on my phone between two calls, right. An outsourced animator would drop a stepped playblast into the chat, I would watch it once and write something like "the jump feels slow in the middle and the landing pose is weak". To be very honest, that was my whole idea of how to give animation feedback on a blocking pass.

The next pass would come back with the wrong section sped up and a landing pose that had moved somewhere I never meant, so we burned a full round basically just agreeing on where the problem was. Repeat that on every shot of a sequence and those wasted rounds are exactly what pushes blocking past its slot on the schedule.

Now it runs very very differently, right. The playblast goes up as a version, every note sits on the exact key it is about, I draw the pose I want over the frame, and timing notes cover the range that actually drags. The next pass stacks on the same card, so I can compare the two and see whether each note landed, and this post walks through the whole method, including a worked note sheet for one shot.

What animation blocking feedback should focus on

Blocking is where the animator commits to the key poses, the main timing and the staging in stepped keys, so the pass looks choppy on purpose, right. The catch here is that a lot of supervisors react to the choppiness itself, writing notes about overlap and stiff fingers that are not meant to exist yet, and then the animator either ignores the note or starts polishing far too early.

Good animation blocking feedback answers one question per shot, which is whether the acting and staging would still read if the shot stayed this choppy forever. If the answer is no, the note has to name the pose, the beat or the camera choice that breaks it, and that is exactly where most feedback goes vague.

So I review in a fixed order, and I really really recommend keeping it even when something lower down is screaming at you. Acting choice comes first, then staging and silhouette against the camera, then key poses, then timing between those keys, and arcs last where they are already visible. A timing note is wasted if the pose it leads into is getting redrawn anyway, does that make sense, right.

Blocking sits after the animatic stage has locked the story beats and before spline, polish and lighting. I mapped every review gate in the animation production pipeline post, and the short version is that blocking is the last cheap place to change your mind.

• Acting choice reads clearly without sound
• Staging and silhouette clear from this camera
• Key poses strong and readable
• Timing between keys feels right
• Visible arcs heading the right way

How to give animation feedback on poses, timing and staging

Most blocking notes I see, plenty of my own old ones included, describe a feeling, right, and a feeling only gives the animator a mood to chase. So every note I write now carries four parts, where it sits on the timeline, what reads wrong, which direction to push and why it matters to the shot.

Writing "the jump feels floaty" gives none of the four. Writing "anticipation crouch holds 4 frames, push it to 8 so we feel the weight load before takeoff" gives all of them, and the animator can act on it without a call.

For poses, I name the key and describe what is wrong with the pose itself, like weight centered over both feet on a landing, so it reads as a step down instead of a fall. I suggest a direction and leave room for the animator's own choice.

For timing, I always talk in frames, because "faster" means something different to every animator on the team, while "this take holds 20 frames, aim for 10" leaves nobody guessing.

For staging, I talk about camera and silhouette. When an arm disappears into the torso, I ask for it to clear or for a small camera change, and I tag whoever owns layout so the decision does not sit with the animator alone.

Tone matters as much as precision, to be very honest, because blocking is the most exposed stage and every choice is naked. I keep notes about the shot rather than the effort, and I always say what is already working so they protect it, and those two habits are the animation critique tips I would give any new lead first.

Feeling note

The jump feels floaty, can you make it snappier

Fix note

Anticipation holds 4 frames, push it to 8 so the weight loads before takeoff

Drawing over a key pose on the frame

Words only go so far with a pose, right, and with a weak line of action or a muddy silhouette I hit that limit very fast. Instead of three sentences about the curve of the spine, I pause on the key and draw the line of action I want right over the character.

In PlayPause I sketch with the drawing and markup tools, and the drawing saves with the comment on that exact frame. The animator sees the same key I was looking at with my sketch on top, so there is no screenshot to match and no timecode to hunt for.

I keep drawings rough on purpose, a line of action or an arc path for a hand, because a rough sketch reads like a direction the animator can still own. Every drawing also gets one line of text, like "spine curve, push the chest past the knee", and that pairing pretty much ended the back and forth about what I meant.

I went deeper on pinning notes to a key in frame-accurate notes on an animation pass.

“

A rough line of action drawn on the key does more work than three paragraphs describing the same pose.

Range comments for holds and timing

Single-frame comments suit poses, but timing problems usually live across a stretch of frames, right, a hold that goes dead or a reaction that lands a little late. Pin that to one frame and the animator has to guess where the problem starts and ends.

So for timing I use range comments, which cover a span of frames. I set the range across the whole hold and write how long it runs, where it dies and what I am aiming for, and the animator makes their own call on how to get there.

For instance, I sometimes mark three beats in a row and say the middle one should be shortest because it is the surprise, and seeing those spans laid out beats describing rhythm in chat, you see what I mean here.

All of this sits on time-coded annotations, so every note keeps its place even after a dozen replies. If timing is where your notes usually fall apart, read precise timing notes on animation next.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

A worked example of animation blocking notes on one shot

Here is a full note sheet for one simple shot, right. Say a character runs and leaps a gap between two rooftops, 96 frames at 24 fps, the frame rate most character work runs at. On MV1, the first stepped pass, these five notes go out after two watches at speed.

• Frame 14, anticipation key, with a drawing: hips sit too high, drop them and bend the line of action into the curve I drew so we feel the load.
• Frames 14 to 18, range comment: the crouch holds 4 frames, push it to 8 so the takeoff has something to push against.
• Frame 40, apex key: the far arm crosses the face from this camera, swing it up and back, and I tag the layout lead in case a camera nudge is the better fix.
• Frame 58, landing contact: weight is centered over both feet so it reads like a step down, put the hips past the front foot.
• Frames 58 to 88, range comment: the recovery holds 30 frames and goes dead after about 12, cut it to 14 or make it a moving hold.

One parked comment on the last frame lists the polish I noticed, finger curls, the settle on the jacket and so on, marked as not for this pass. Every line has a place, a problem, a direction and a reason, and at the end of the day that is how to give animation feedback an animator can act on without a call.

12

frames make half a second at 24 fps

4 to 8

frames, the anticipation change in this example

30 to 14

frames, the recovery hold cut in this example

Comparing blocking passes side by side

The second pass is where feedback loops quietly fail, right. The animator says the notes are addressed, the supervisor watches once and it feels better, and two passes later you find out the anticipation was never lengthened.

A new pass goes up on the same card as a new version, so the shot carries MV1, MV2 and MV3 as one version stack with the old notes still on their frames. It works like version control for software, where the history stays together and nothing gets overwritten.

Then I open side-by-side version compare, blocking on the left and blocking plus on the right, and go through each old note. On the rooftop shot that means frame 58 on both sides to see whether the hips moved, then the 14 to 18 range to count the crouch. If a note missed, I reply in the same thread with an @mention so its history stays in one place.

Side-by-side compare is on the Agency plan and up, and to be very honest it is the feature I would miss most in a blocking pass review, because blocking plus shifts spacing and timing in small ways you cannot catch from memory.

1Upload blocking plus as the next version on the same card

2Open side by side compare against the previous pass

3Go to each old note and check that frame on both sides

4Reply and tag the animator on any note that missed

Common mistakes in animation blocking notes

The first mistake is noting polish during blocking, right, finger curls and overlap on a tail, which is why I park those in one comment on the last frame.

The second mistake is letting notes arrive from five directions, and trust me on any level, this one costs more time than the others combined. The director, the lead, the client and a producer all leave notes, some contradict each other, and the animator either picks one or freezes. I consolidate before anything goes out, which I wrote up in consolidating supervisor notes across sequences, and when the client and I disagree I reply in their thread with the final call.

The third mistake is stepping through frame by frame first, when timing and acting only read at speed, so I watch every pass twice before touching a single frame.

The fourth is reviewing without the audio or the reference, since a pose that looks too big might be exactly right for the line under it, and brand work follows the same logic, as I covered in giving notes on 3D product animation.

Signing off blocking before spline

Moving to spline is where cheap changes stop being cheap, right, because once curves are in, changing a key pose means fixing interpolation all around it. So blocking sign-off gets its own gate and its own status, and a thumbs up in chat no longer counts as approval in my agency.

In PlayPause I set custom statuses like "Blocking notes", "Blocking plus review" and "Blocking approved", so anyone can see where each shot stands without asking. When a shot hits approved, the animator knows they can spline and the producer knows it can go on the schedule.

For rules that apply to every shot I use Playbooks, on the Agency plan and up. A folder playbook for the sequence holds the director's direction, like how big takes should be and how long holds can run, plus a checklist that is not done until every item is ticked. It can also be shared as a no-login page for an outsourced animator joining halfway through.

If an outside director needs to sign off, they open one link in the browser and comment without an account, a bit like supervisors used to watch film dailies together in one room. Who-watched analytics on Creator and up tell me whether they opened it before I start chasing, and that is basically how we run PlayPause for animation studios.

Frequently asked questions

What should a good animation note include?

A good note has four parts, right, where it sits on one frame or a range of frames, what reads wrong, which direction to push and why it matters to the shot. "Anticipation holds 4 frames, push it to 8 so the weight loads" covers all four in one line, and a rough drawing on the frame helps whenever the note is about a pose.

How do I give animation feedback on blocking without discouraging the animator?

Start with what is working, right, because blocking is rough by design and the animator already knows it. Keep every note about the shot, name the key or the frame range, and leave the exact solution to them. I'm pretty sure most discouraging feedback comes from vague notes, because vague notes make people redo the same work twice.

What is the difference between blocking and blocking plus notes?

In blocking I note the acting choice, the staging, the key poses and the main timing. In blocking plus the animator has added breakdowns, still stepped, so my notes move to spacing, arcs and whether earlier notes landed, which is why I compare the two passes side by side instead of judging blocking plus on its own.

Can a director or client review blocking without a PlayPause account?

They can, right, they open one share link in the browser with no account and no install, and they leave frame-accurate comments and drawings on the same frames your team sees. You can password-protect the link and revoke it instantly once blocking is approved, so access ends when the review does.

If your next blocking pass is sitting in a chat thread right now, try running it this way, because every plan starts with a 7-day free trial, and PlayPause pricing shows which plan fits your team.

So yeah. That's my way of saying it.