Turn Notes into Revisions
From reaction to note
Reactions are real data. If a viewer says “I got bored around the middle”, something happened. The problem is that a reaction alone does not tell the editor what to change. A useful note adds three things: where it happened, what effect it had, and one possible option. The option is an offer, not an instruction; the editor may solve the problem differently, and that is fine.
Compare two notes on the same moment. “The middle drags” is honest but vague. “From 0:11 to 0:16, the three close-ups show similar information, so my attention drifted. If the goal is pace, cutting the second close-up might help, though you would lose the detail of the hands” gives the editor something to test. It also names a trade-off, which shows you understand the editor's choice was not careless.
A template you can paste
Editor's question: [copy it here] What works: At [timecode], [specific strength] because [reason]. What I noticed: At [timecode], [what happens on screen]. Effect on me: [feeling / confusion / drift]. One option: If the goal is [goal], try [change]. Trade-off: [what might be lost]. Answer to your question: [direct reply]
How to use it well
- Answer the editor's question first. They asked it for a reason.
- Limit yourself to two or three “noticed” points. A long list buries the important one.
- Make strengths specific too. “Nice edit” teaches nothing; “the cut on the door slam at 0:07 lands perfectly” teaches the editor what to keep.
- Describe your viewing conditions: phone or monitor, sound on or off.
- Leave taste out unless you label it: “Personal preference, but…”.
What a good exchange can look like
Editor's question: “Does the ending feel earned, or too sudden?”
Reviewer: “The match cut from the spinning wheel to the clock at 0:04 is clean and sets up the time theme. At 0:22, the final shot cuts away as the cup is set down, before the steam rises, so the ending felt slightly sudden to me (phone, sound on). If you want a softer landing, holding 12–15 more frames might let the steam finish. Trade-off: the piece goes over your 25-second limit, so you might trim the second pouring shot to compensate.”
Editor's revision note: “Held the end 14 frames and cut the second pour. Kept the opening as is.”
Notice what the reviewer did not do: compare the editor to anyone else, suggest replacing the music they chose, or rewrite the whole piece. The note served the editor's goal.
When the problem is technical
Technical issues need a different kind of note. Always state the software and version, operating system, source device and the exact symptom. Fixes vary between DaVinci Resolve, Adobe Premiere Pro, Final Cut Pro, CapCut, Kdenlive and Shotcut, so treat these as starting points.
Audio drifts out of sync over time
Most often caused by variable frame rate footage from phones or screen recorders. Convert to a constant frame rate (for example with HandBrake or your editor's own transcode option) before editing, then re-sync.
Timeline playback stutters or drops frames
Long-GOP codecs such as H.264 and H.265 are demanding to scrub. Generate proxies or optimised media, reduce playback resolution, and check that your cache drive has free space.
Exported colours look different from the timeline
Frequently a gamma tagging mismatch, especially with Rec.709 exports viewed in QuickTime on macOS. Compare in several players before regrading, and check your project colour management settings.
Gradients show banding after upload
Platforms recompress heavily. Add a very light grain or noise layer to smooth gradients, and export at a higher bitrate than you think you need.
Volume jumps between clips or videos
Measure loudness rather than relying on peaks. Broadcast in Europe follows EBU R128 at −23 LUFS; many streaming and social platforms normalise to roughly −14 LUFS. Pick a target and keep dialogue consistent.
Black bars appear on vertical exports
Your sequence settings probably do not match 9:16. Set the timeline to 1080 × 1920 before reframing, rather than scaling a 16:9 sequence at export.
Receiving notes without losing your edit
You do not have to take every note. A good practice is to sort them into three groups: notes that point to the same moment (strong signal, investigate), notes that conflict (often a sign the moment is ambiguous) and notes about taste (consider, then decide). When you share a revision, say which notes you applied and why you passed on others. That helps reviewers calibrate, and it shows the edit is still yours.
If a note stings, wait a day before replying. Then ask a clarifying question: “When you say it felt slow at 0:12, was that the shot length or the music?” Most frustration in feedback comes from vague notes, and a question turns them into something useful. Have a question we did not cover? Send it to us.