Director and Editor Communication Protocols That Survive the Rough Cut Stage

The rough cut is where most productions quietly fall apart. Not because the edit is bad, but because nobody agreed on how to talk about it. Notes arrive as voice messages, scattered emails, a PDF someone annotated in Preview, and a five-minute phone call that nobody wrote down. By the time the editor opens the timeline the next morning, they are guessing which version they are supposed to be working on.

A solid director-editor communication protocol rough cut stage is not a luxury. It is the thing that keeps a film moving forward instead of spinning in circles.

Why the Rough Cut Is the Hardest Stage for Communication

At rough cut, the film looks and sounds rough by definition. That is scary for directors, especially first-timers. The instinct is to over-communicate: call the editor, send a late-night voice note, drop a paragraph in Slack, then send a "by the way" follow-up the next morning. None of those notes are pinned to a frame. None of them create a record.

For editors, this stage is actually very precise work. They need to know: which scene, which moment, what change, and whether it supersedes or adds to the previous note. Vague feedback delivered through the wrong channel wastes hours.

The protocol has to handle two things at once: give the director a fast, low-friction way to react to what they are seeing, and give the editor structured, frame-referenced notes they can act on immediately.

The Protocol That Actually Works

Here is what I recommend, and what we built PlayPause around.

First: the director watches the cut in one place, not in their inbox, not on a downloaded file. A single shared review link, time-code enabled, where every comment is stamped to the exact frame it references. The director clicks pause wherever they have a thought, types the note, and moves on. No screenshots. No phone calls explaining what timecode to find.

Second: all notes live in one thread attached to the specific version the director watched. If there is a V3 rough cut, the notes for V3 are attached to V3. When V4 goes up, V3 and its notes do not disappear. The editor can see what changed between rounds and confirm they addressed each note.

Third: the editor responds directly in the same thread. Not a reply email, not a Slack message. A threaded comment on the same frame: "Fixed. Tightened the cut by 12 frames and added a beat before the dialogue." Now you have a full exchange that reads like a conversation and documents itself.

For a deeper look at how this works in practice, see our guide on how editors collect frame-accurate notes from directors without a single email.

What to Decide Before the First Rough Cut Drops

The protocol should be set up before the director sees anything. That means agreeing on three things:

• One channel for notes. Everything goes into PlayPause. Not in addition to email, not as a backup, not alongside WhatsApp. One place.
• One version at a time. The director does not watch V2 and V3 simultaneously and compare in their head. They watch one, give notes, the editor cuts a new version, and the cycle repeats.
• A turnaround window. Agree that notes on a rough cut come back within 48 hours. No open-ended "whenever you get a chance." This keeps the edit moving and prevents the feedback pile-up where a director dumps two weeks of thoughts in one session.

You can document this in a one-page note that goes out with the first review link. Nothing formal, just: here is how this works, here is where you watch, here is how you leave a note. It takes five minutes and saves hours.

Handling the Director Who Prefers Calls

Some directors want to talk. That is fine. I am not saying eliminate the relationship or turn the collaboration into a ticketing system. The conversation is valuable.

But after the call, one person writes a summary and posts it to the review thread. Not an email. A note on the cut, timestamped to the frame where the discussion was most relevant. "Per our call 14 April, remove the third shot in the opening sequence and try a harder cut from the wide to the close-up."

Now the call happened, but the note also exists where the editor can find it without digging through a phone log.

For productions where the director and editor are on different continents, this documentation habit is not optional. See our piece on managing dailies review when your director is in a different time zone for how to structure the async loop.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

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

Version Labeling and the Cut as a Document

One of the most common failure modes I see: the director is giving notes on V3 but the editor has already sent out V4. The notes get applied to the wrong version, confusion ensues, and someone has to call someone.

The fix is to treat each version of the cut as a distinct document with a lock. When V4 is uploaded, the director gets a notification and knows that V3 is now archived. They do not go back and annotate V3 unless they are specifically comparing versions side by side.

PlayPause supports version stacking so you can pull up V3 and V4 next to each other. That is useful when a director says "I preferred the opening from the last cut." Instead of exporting both versions and hoping the director can find the right file, you put them side by side in the review interface and ask the director to mark which moment they mean. Read more about how this fits into a broader edit workflow in our edit approval loop guide.

Notes Hygiene for the Editor

Editors sometimes resist note-tracking platforms because they feel like surveillance. I get that. The goal is not to create a paper trail to hold over anyone. The goal is to get the edit done cleanly and not waste two days re-cutting something the director already approved.

Practically, after each round of notes, the editor should mark each comment as resolved or open. If a note is not going to be addressed (because the director agreed on a call to drop it, or it conflicts with another note), that should be written in the thread. Not in the editor's personal notes, not in their memory. In the thread.

This protects the editor as much as the director. If someone asks "why is that scene still in there?" the editor can point to the thread where the director said to keep it.

• Set up single review link before first cut drops
• Agree on one-channel note policy with director
• Establish 48-hour turnaround window for note cycles
• Archive each version when the next one is uploaded
• Editor marks all comments resolved or open after each round

Onboarding a New Director to the Protocol

If you are working with a director who has never used a video review tool, do not assume they will figure it out. Send them a 90-second screen recording showing exactly how to leave a comment. Or better, drop them a note saying: "Play the cut, hit pause wherever you have a thought, and type your note. That is it." Most people get it in the first session.

The directors who give the cleanest, fastest notes are usually the ones who tried the old system long enough to be tired of it. They know exactly what it feels like to have a note misunderstood because it was scribbled in the margin of a PDF at frame 01:14:32 with no context.

The Downstream Effect

Good director-editor communication protocols at the rough cut stage do not just make the rough cut smoother. They set the tone for the rest of post. The picture lock is cleaner. The sound mix notes are more accurate. The color grade has fewer surprises. Every department that touches the project after picture lock benefits from a well-documented note history.

For a checklist of what to hand off after picture lock, our handoff checklist from picture lock to sound design covers exactly what information needs to travel with the cut.

If your current director-editor workflow involves a lot of email chains, scattered voice messages, and the occasional "wait, which version is this?" moment, it is worth switching to something built for the job. PlayPause is free to start, and the Agency plan at $19/month covers the whole workspace including unlimited guest reviewers, so your director never needs to pay for access. Try it on your next rough cut and see what a single source of truth actually feels like.