How to Run a CG Lighting Review That Actually Cuts Iteration Time in Half

CG lighting is one of the most technically demanding review stages in animation, and it is also one of the most commonly mismanaged. Directors give notes that make sense to them and mean almost nothing to the lighter. Artists iterate on things nobody actually asked for. Review sessions run long and produce ambiguous outcomes. Then everyone does it again the next day.

I have watched this cycle happen in small studios and large ones. The problem is almost never the quality of the work. It is the structure of the review. Here is how to run a CG lighting review that actually moves production forward instead of spinning it in place.

Start With Reference Before You Start With Notes

The single fastest thing you can do to cut lighting iteration time is establish a shared visual reference before the first review. Not a general mood board from pre-production. A specific, scene-level reference that everyone in the review has seen and agreed on.

This matters because "make it warmer" means something different to a director and to a lighting artist. "Match the warmth in frame 47 of the reference" means the same thing to both of them. The reference converts subjective language into a concrete target.

If you are reviewing multiple lighting setups in the same session, associate each setup with its own reference images. Upload them to the same review thread where the shots live. When a note is left at a specific frame, the artist can toggle to the reference without leaving the review session.

Structure the Review Around Decisions, Not Observations

Lighting reviews fail when they are structured as screenings where the director watches and reacts and the artist takes notes. That process produces observations ("something feels off about the shadows") rather than decisions ("increase ambient occlusion intensity by 20% in the eye area of shot 043").

A better structure is to enter the review with specific questions that need answers. Before the session, your lighting supervisor should prep a short list of unresolved decisions for the director:

• We have two lighting approaches for the key shot. Which direction should we commit to?
• The fill light is currently diffuse. Do you want hard-edged shadows in this scene, or do we keep soft?
• The practical lamp in frame needs to be motivated. Should it read warm or neutral?

When the director knows the review is structured around decisions rather than open critique, the session runs in half the time because everyone knows what they are there to resolve.

Use Frame-Accurate Comments to Eliminate Post-Session Transcription

The most expensive part of most lighting reviews is not the session itself. It is the hour afterward where a coordinator tries to reconstruct the director's notes from memory and translate them into tasks for artists.

PlayPause eliminates that step by capturing frame-level comments in real time. The reviewer pauses on a specific frame, clicks the comment tool, and the note is timestamped and tied to that exact frame. Your coordinator does not need to take notes in a separate document and then cross-reference with the timecode later. The notes are already in the right place.

For lighting specifically, this matters because the difference between frame 214 and frame 220 might be a significant shift in the shadow pattern as the camera moves. A note that says "the shadows look wrong" with no timecode is almost useless. A note at frame 217 is specific enough to act on.

Separate Technical Notes From Creative Notes

This is a simple practice that pays off immediately. When you are running a lighting review, technical notes (specular blowout on the wet surface, flickering in the shadow at frame 302, the HDRI seam is visible at the edge of the frame) belong to the lighting department and should go directly to the artist. Creative notes (this scene needs to feel lonelier, the contrast ratio is too harsh for the emotional tone) belong to the director and should go to the lighting supervisor for interpretation.

Mixing both types in the same note stream creates a filtering problem. Artists receive creative direction they cannot interpret without context. Directors receive technical notes that should never have reached them.

In your review session, have a clear protocol: technical notes go in the main comment thread with the shot tag. Creative notes go in a separate thread or are flagged with a specific tag so the lighting supervisor can filter and translate them before they hit the artist's queue.

The Review Cadence That Cuts Iteration

Instead of a once-a-week lighting review that covers everything in a marathon session, I would push for a shorter daily or bi-daily cadence that covers a smaller number of shots in depth.

Here is why this cuts total iteration time even though it means more sessions:

• Notes are given while the artist's context is fresh. They remember what choices they made and why.
• Decisions are made quickly because the session scope is small. Nobody is decision-fatigued by shot 30.
• Problems are caught earlier. A lighting direction that is off by 10 degrees does not propagate across 50 shots before anyone notices.
• Approvals happen faster because the director is reviewing a small number of shots they have context on, not a large batch they have to re-orient themselves to.

The table below shows how iteration time typically compares:

How to Get Director Buy-In on a Structured Review

The biggest obstacle to running tight CG lighting reviews is usually not the process itself. It is getting directors to show up to shorter, more structured sessions instead of the informal "let me watch everything" review they are used to.

The pitch to a director is simple: more sessions but shorter, and every session ends with a clear list of what is approved and what changes. You are not asking for more of their time; you are asking for the same time structured differently. Most directors will take that deal once they see how much faster their shots move through the pipeline.

If you are managing a remote director who reviews on their own schedule, async review with PlayPause gives them the same frame-level precision without requiring a live session. For CG feature work where multiple departments review in parallel, how to run a parallel review for edit and color when both departments are working simultaneously is a useful companion. They watch the shots when they have time, leave comments at the exact frames that need attention, and you get actionable notes without scheduling a meeting.

Close the Loop With Explicit Approvals

The last step in every lighting review cycle should be an explicit approval on the shots that passed. This is where a lot of studios leave value on the table. The director says "looks good" about shot 043, and that shot stays in a perpetual state of technical completion but no formal approval.

Then, two months later, someone revisits shot 043 for a pickup pass, and nobody can confirm which version was signed off on. You end up re-reviewing something that was already approved because the approval was never documented.

PlayPause's approval workflow ties the sign-off to a specific version of a specific shot. When the director approves shot 043 v7, that is the record. It is timestamped, it is permanent, and if anything touches that shot later, everyone knows exactly what the approved baseline was.

This is the last step in cutting iteration time: once a shot is approved, it is locked. No informal notes, no "while you are in there" changes. If it needs to change, it goes back through the review process.

Start free or see the plans at /pricing. Most animation studios land on the Agency plan at $19/mo, and every guest reviewer, including your directors and clients, is always free. For teams that also need a QC pass before the client sees anything, the internal QC pass workflow for an animation studio before client delivery covers that step. And for large render reviews on CG features, how to run a render review session for a CG feature without flooding email threads applies the same principles at scale.