How to Run a Render Review Session for a CG Feature Without Flooding Email Threads

A render review session for a CG feature is not a single event. It is a recurring ritual that happens across every department, every week, for the full length of production. Lighting review, lookdev review, animation blocking, spline, polish, comp, final. Every pass generates notes. Every round of notes generates replies, revisions, and more notes.

If you are managing this through email threads, you will eventually lose track of something critical. A note that was addressed in v02 gets re-raised in v04 because the original thread is buried under 200 messages. An approval given over email turns out to be provisional. An artist acts on conflicting notes from two different supervisors and re-renders a shot that did not need to be re-rendered.

Here is how to run a render review session for a CG feature at scale, without flooding anyone's inbox.

The Core Principle: Notes Travel With the Render

The fundamental shift is this: notes should live where the render lives, not in a separate channel. When a lighting supervisor watches a render and leaves a note, that note should be attached to the specific frame of that specific version of that specific shot. The artist opens the review link, sees the note exactly where the problem is, and understands it in context.

Email breaks this because notes are detached from the footage. A director types "the rim light on the right feels overexposed" in an email body. The lighting artist has to load the render, find the frame, match the description to what they see, and interpret whether "right" means screen-right or the character's right. Three interpretive steps between the note and the action.

In a review platform like PlayPause, the director pauses the playback at the exact frame, clicks, types "rim light overexposed," and submits. The lighting artist opens the link, the video plays, and there is a comment marker right on the problem frame. Zero interpretive steps.

Setting Up the Session Structure

For a CG feature with multiple departments reviewing simultaneously, I would structure the render review sessions as follows:

Daily department reviews. Each department (lighting, animation, comp, fx) has a daily review that covers new renders from the previous 24 hours. Supervisors leave notes in the relevant department review session. These are departmental notes, not cross-department.

Weekly combined review. Once a week, the CG supervisor or VFX supervisor runs a combined review of hero shots and priority sequences. The director may or may not attend. Notes from this session are broader creative notes, not technical departmental notes.

Approval queue reviews. Shots that are believed to be final get their own review link and go through a formal approval gate. Once a shot is approved in this queue, it is locked and sent to the finishing house.

This three-tier structure means each review has a clear scope. Artists know whether they are looking at a departmental note or a combined review note. They know whether the shot is in the daily loop or in the approval queue.

Organising Renders by Shot and Version

The naming convention is the backbone of any render review workflow that does not collapse under the volume of a feature production. Here is what works:

When you upload to PlayPause, paste this as the video title. When a supervisor opens a review link, the title tells them the sequence, shot, department, pass, and version. They know exactly what they are looking at before the video starts playing.

• Consistent naming before upload
• One review link per shot per pass per version
• Notes close after a set window, no rolling feedback
• Supervisor consolidates notes before artist acts
• Approval is logged with a timestamp, not assumed

Managing the Supervisor Note Load

On a feature with 800 shots, a lighting supervisor might be reviewing 40 to 60 renders per day. At three comments per render, that is 120 to 180 individual notes generated per day, per supervisor. The volume is real and it is relentless.

The key to handling this without burning out supervisors is batch review with a hard time window. Supervisors review all of today's renders within a two-hour window at the start of the day. They leave notes directly on the review links. After two hours, the window closes. Notes submitted after the window are held for the next day's review. Artists who completed renders that day know their notes will be ready by the end of that two-hour window.

This predictability is what makes the system work. Artists can plan their day: review notes arrive by 11am, revisions are complete by end of day, new renders are submitted before the next morning's window.

Cross-Department Notes Without Cross-Department Chaos

On a CG feature, a single shot might have notes from lighting, animation, and compositing simultaneously. The comp supervisor wants the integration fixed. The lighting supervisor wants the rim light adjusted. The animation supervisor wants the settle timing on the hero tightened. These notes are often generated on the same review session.

The challenge is that different notes belong to different departments. If you put all three sets of notes in the same review link, the lighting artist sees the animation notes and wonders whether they are expected to fix the settle, and the animation artist sees the lighting note and wonders the same thing in reverse.

The fix: use separate review links for each department's notes on the same shot. The comp supervisor reviews the comp version and leaves comp notes. The lighting supervisor reviews the lighting pass and leaves lighting notes. The same shot has three review links, each with department-specific notes, each visible only to the relevant department.

This is exactly how parallel review for edit and color when both departments are working simultaneously works in live-action post, and the same logic applies to CG features. For animation supervisors managing across sequences, consolidating animation supervisor notes from multiple sequences in one pass covers the same department-segregation logic in depth.

The Approval Gate: When Is a Shot Actually Done?

The most common source of wasted re-renders on a CG feature is unclear approval. A department supervisor says "this looks good" in a Slack message. The artist interprets that as approval. The shot moves to the next department. Three weeks later, the VFX supervisor sees it in the final comp and sends it back for a round of changes. The department-level "looks good" was not actually an approval.

In PlayPause, approval is an explicit action. The supervisor marks the shot as approved. This generates a timestamp and locks the version. If someone comes back after the lock and wants changes, there is a documented record that the shot was approved at a specific time, and the new changes are formally a revision against that locked version.

For running a final comp review before online delivery on a tight VFX schedule, this approval gate approach is the difference between a clean handoff and a last-minute scramble. Studios handling episodic should also read VFX coordinators keeping shot review notes organised across a full season for the per-shot approval tracking that scales with volume.

What You Gain by Dropping Email

I want to be concrete about what switching from email-based render review to a frame-pinned review tool actually changes for a CG feature production:

• You stop spending time at the start of every review call asking "which version are we on?" The review link title tells you.
• You stop losing notes in inboxes. All notes are in the review platform, version-locked, searchable.
• You stop having supervisors re-raise notes that were already addressed. The artist can reply to a comment with "addressed in v05" and the thread is visible to everyone.
• You stop having artists act on conflicting notes. The consolidation step resolves conflicts before they reach the artist.
• You start having documented proof of approvals. When the client comes back six months after delivery and says a shot was not approved correctly, you have timestamps.

PlayPause is built for this workflow. Free guest reviewers mean directors and clients do not need paid seats. Flat per-workspace pricing means your cost does not scale with your team size. If you are also coordinating dailies review when your director and supervisor are in different time zones, PlayPause's async review infrastructure handles both workflows in the same tool. Check the pricing page and the video review overview to start the free trial and run your next render review session without an email thread in sight.