How to run a revision round without a chat thread

The second round is where wedding films go wrong. The first pass is easy — your editor sends a cut, you watch it, you have three notes. By the second round you have your notes, the couple’s parents have an opinion about the speeches, and someone has said “the bit near the end feels long” in a message thread that also contains a parking question and a photo of a dog.

Nobody is being unprofessional. The tooling is just built wrong for the job.

What actually goes missing

A revision note has two halves: what you want changed, and where. Chat carries the first half perfectly and destroys the second.

Write 01:12:40 — hold this longer in a message and you have handed your editor a lookup task. They open the project, scrub to roughly that point, and now they are guessing: hold what longer? The shot before the cut, or the cut itself? Sometimes the timecode is from the previous version and points at a different moment entirely, because you watched v1 while they were exporting v2.

Multiply that by fifteen notes and you have lost an hour before any editing happens. Worse, the guessing is invisible. Your editor doesn’t tell you they guessed. They make a change, you watch it, and it isn’t what you meant, so you write another message. That is the third round, and it exists purely because the first one was ambiguous.

Anchor the note to the frame

The fix is boring and it works: every note should live at the timecode it refers to, and you should be able to click it and land there.

This is the difference between a comment that says “01:12:40” and a comment that is at 01:12:40. The first is a description of a location. The second is the location. When your editor opens their list, each note takes them to the exact frame — no scrubbing, no guessing which version the number came from, because the note belongs to a version too.

For anything visual, draw on the frame. “The third guest from the left” is a sentence somebody has to decode. A circle around that guest is not. This matters most for the notes that are hardest to write: colour on one face, a boom in the corner, the wrong take of a reaction shot.

Give one signal at the end, not fifteen

Here is the part most studios skip. After the notes, your editor needs to know one thing: what happens now?

Fifteen comments and no verdict is not an answer. It leaves them deciding whether this is a small pass or a re-edit, and whether to start now or wait for more. Most editors, sensibly, wait — which reads to you as slowness.

Three outcomes cover every real case:

• Approve. Done. Nothing further. This goes to the couple.
• Approve with changes. The notes are small, you trust them to apply the changes, and you do not need to see it again before it ships.
• Request changes. Apply the notes and send another version.

The middle one saves the most time and gets used the least. A colour tweak and two trims do not need a fourth review cycle; they need permission. Saying so explicitly turns a two-day round trip into an afternoon.

Keep the old versions readable

When v2 arrives, v1 should not disappear, and neither should the conversation attached to it.

Half the questions in a revision round are archaeological: did we already decide about the speeches? Was the shorter opening my idea or theirs? If v1 is gone, nobody can check, so somebody re-litigates it. Keeping every version and its notes turns that into a five-second look rather than a debate.

It also protects you. When a couple asks in September why the film is different from the version they saw in July, the honest answer is a link.

What a clean round looks like

1. Your editor uploads v2 and marks it ready for review — an explicit handoff, so you are never reviewing something mid-export.
2. You watch it once through without writing anything. Resist this at your peril; notes written in the first two minutes are usually about pacing that resolves itself by minute four.
3. You watch it again and leave notes on the frames they belong to. Draw when the note is visual.
4. You pick one of the three outcomes.
5. Your editor works from a list where every item takes them to the right frame, and replies on the notes they have questions about rather than starting a new thread.

No chasing, no “did you see my message”, no timecode arithmetic.

The part nobody plans for

The couple will have a note too. That is normal and it is not a failure of your process — they are seeing it for the first time.

The question is where their note lands. If it arrives as an email that you then paraphrase to your editor, you have reintroduced exactly the ambiguity you spent the whole round eliminating, at the point where you can least afford it. Their feedback should arrive in the same place, anchored the same way, so the last round of the job is as precise as the first.

That is the loop Delsity is built around: your editor uploads, you decide, the couple watch a branded page, and anything they ask for comes back to the same thread rather than to your inbox.

If you want the other half of this — what to do the day you actually hand the wedding over — read the wedding delivery checklist.