The first cut and the review round without endless revisions

3 days ago
3 min read

Introduction

A video edit can absorb an unlimited amount of revision. There is always a slightly different take, a marginally better music bed, a colleague who has just been shown it and has thoughts. Projects do not usually fail on the shoot; they fail in the fortnight after the first cut, when three people send conflicting notes and nobody has the authority to decide.

The first cut is not really a deliverable. It is the beginning of a structured process that either converges or does not, and that depends almost entirely on how it is set up. The setup takes one paragraph in the quote.

1. The first cut and the review round need rules before the link goes out

Set the process before there is anything to argue about. Nobody objects to it in advance.

Say how many rounds are included

Two rounds of consolidated feedback, then a final. Written into the quote, it is a normal term; introduced halfway through, it sounds defensive.

Name one person who signs off

A single approver who collects internal opinions. Feedback from four people in three channels is how a fortnight disappears. Insist on it politely.

2. Explain what the first cut is and is not

Clients judge an early edit as though it were finished. They have no reason not to.

Say what is deliberately unfinished

Colour, sound mix, graphics, music placeholder. Without that sentence you will get notes about the grade when you wanted notes about the structure.

Ask for the right feedback at the right stage

Structure and story first, detail later. Say which round covers what. A client picking at a caption in round one is a client who will re-cut the whole thing in round three.

3. Make feedback easy to give properly

Vague notes are a process failure, not a client failure. Make the good version easy.

Ask for timecoded comments

A review tool, or a simple list with times. "The middle feels slow" cannot be actioned; "0:47 to 1:05 feels slow" can.

Ask what the problem is, not what the fix is

Clients often prescribe a solution to a problem they have described badly. Understanding the objection usually produces a better answer. Ask one clarifying question.

4. Keep the project converging

Each round should be smaller than the last. If it is not, something is wrong with the process.

Consolidate before you start editing

Wait for the full set of notes and read them together. Working on notes as they arrive means editing against contradictions. Wait for the deadline.

Flag scope changes as they arise

A new section, a different edit length, a reshoot. Say plainly when a note is a change rather than a revision, politely and at the time.

5. Close it out cleanly

Approval needs to be an event. Otherwise projects simply trail off.

Get written sign-off on the final version

One line against a named version. It ends the project and it protects you if somebody reopens it later.

Deliver in the formats they actually need

Social crops, subtitles, a web version, the master. Ask where it is going and supply accordingly rather than sending one large file.

Conclusion

Video projects fail in the review round rather than on the shoot, so set the rules before the first link goes out: how many rounds are included, and one named person who consolidates internal opinion and signs off.

Say explicitly what is deliberately unfinished in the first cut — colour, mix, graphics, placeholder music — or you will get notes on the grade when you needed notes on the structure. Ask for timecoded comments rather than impressions, and ask what the problem is rather than accepting a prescribed fix. Consolidate notes before editing, name scope changes politely as they arise, get written sign-off against a named version, and deliver in the formats and crops they will actually use.