Workflow

How to Give Async Video Feedback Your Editor Will Actually Understand

Jun 4, 2026 · 6 min read

The gap between "I gave my editor feedback" and "my editor made exactly the changes I wanted" is almost always a communication problem, not a skill problem. Here are five habits that close that gap — so your editor can work from your brief without a single follow-up.

Async video feedback is the art of leaving notes your editor can act on independently — without a phone call to clarify what you meant by "this part feels off" or a follow-up message explaining which cut you were referring to.

The five habits below work whether you're leaving notes in a dedicated briefing tool, a Google Doc, or a voice message. The underlying principle is the same: your editor should be able to pick up your brief at 2am in a different timezone and know exactly what to do.

1. Use the exact timecode, not an approximation

"Around two minutes in" forces your editor to hunt. Your video player shows you the exact timecode — use it. Write 2:03 or 2:03.4, not "about 2 minutes."

If you're using a tool that pins notes to the timeline automatically (which is far better than writing timecodes by hand), make sure you're pausing on the exact frame before dropping the note — not the nearest convenient moment.

Better: "Cut at 2:03 — pause is too long between the question and the answer."

Worse: "Around 2 minutes in the pace slows down."

2. Annotate the frame, not just the timecode

Some edits are about when something happens. Others are about where in the image — a lower-third that's in the wrong position, a background element you want removed, a face that needs to be blurred.

Written descriptions of spatial problems are always ambiguous. "The graphic is covering the text" doesn't tell your editor whether you mean the top text or the lower caption, the left side or the right, the first appearance or the repeated one.

A three-second circle drawn on the frame is unambiguous. If your briefing workflow allows it, draw on the frame for any note that has a spatial component. Even a rough arrow is clearer than a verbal description.

3. Tell your editor what you want, not just what's wrong

Diagnostic notes describe the problem. Actionable notes describe the solution. Your editor doesn't need a diagnosis — they need an instruction.

Diagnostic: "This section feels slow."

Actionable: "Cut from 4:10 to 4:45 — the point is made by 4:10, the rest is repetition."

The diagnostic version puts the solution-finding on your editor. Sometimes that's fine — good editors figure it out. But when you have a specific outcome in mind (and you usually do, or you wouldn't have flagged it), just say it. It's faster for both of you.

If you genuinely want to leave the solution to your editor's judgment, say that explicitly: "This section feels slow — I'll leave the exact cut to you." That's not vague feedback; it's a clear delegation. Your editor knows they have creative license.

4. Label your notes by type

Most video edits fall into a handful of categories: structural cuts, b-roll requests, audio fixes, graphics and text changes, color/grade notes, and transition changes. Labeling each note by type lets your editor batch similar work — all the audio fixes in one pass, all the b-roll swaps in another.

It also makes your brief easier to scan. An editor looking for the audio note at 3:42 can find it faster in a labeled list than by reading 25 unlabeled notes.

A simple label system:

[CUT] — remove this section
[B-ROLL] — swap or add footage here
[AUDIO] — fix sound, add music, adjust levels
[TEXT] — change a lower-third, caption, or title card
[TRANSITION] — change how this cut feels
[POLISH] — color, grade, stabilization, subtle fixes

5. Send everything at once — not in drips

The worst brief format is a series of messages spread over the day: three notes at 10am, two more at noon, one more at 4pm when you remembered something. Your editor processes each batch in isolation, notes get missed in the scroll, and by the time they start working they're not sure if more notes are coming.

Finish your complete review first. Watch the cut from start to finish, noting everything. Then send everything in one bundle.

This is uncomfortable for people who like to act on thoughts immediately, but the discipline pays off. Your editor gets a complete picture before they start, can plan their session accordingly, and doesn't have to re-open parts of the timeline they already finished.

If you think of something after sending: Add it to the next round's brief, or flag it clearly as a late addition with a note like "caught this after sending — sorry for the drip." Don't just fire off another message as if it's part of the original brief.

Putting it together

A brief that applies all five habits looks like this:

[CUT] 0:03 — Start on "Today we're covering…", cut the first 3 seconds
[B-ROLL] 0:47 — Product close-up here, see /assets/product folder
[CUT] 1:22–1:38 — Remove this section entirely, point is made at 1:20
[TEXT] 2:15 — [drawing on frame] lower-third is covering speaker's mouth at this frame, nudge it down ~20px
[AUDIO] 3:41 — Hard cut before this needs a 0.5s fade-out
[TRANSITION] 6:08 — Use zoom wipe here instead of hard cut

Exact timecodes. Frame drawing for the spatial note. Actionable instructions, not diagnoses. Labeled by type. Sent all at once.

An editor working from a brief like this can open it, work through the list in order or by type, and check items off as they go — without messaging you once to clarify what you meant.

That's the standard to aim for. Every round of revisions you avoid is time neither of you spent on unnecessary back-and-forth.

Build briefs that don't need a follow-up call

Scoutzera pins your timestamped notes and frame drawings directly to the video timeline. Your editor opens one link and starts working.

Start a brief free