The edit is ready, you send it, and the notes come in: a WhatsApp message saying "the intro drags", an email about "the music around the middle", a voice note with no reference point. None is useless on its own, but none tells you exactly where to act. You spend as much time locating the notes as applying them.
What makes video feedback unusable
Three things break edit feedback: no timecode ("near the end" forces a full rewatch), spread across channels (WhatsApp, email, DM), and feedback trickling in as several contradictory waves. A vague, out-of-context note costs you more than the change itself.
The timecode, the one non-negotiable
A useful note points to a precise second. "At 0:42 the transition is too harsh" gets handled immediately; "the transition is too harsh" sends you hunting for which one. Ask for a timecode every time, even rough to the second, for each note.
On xFer, the revision request happens right on the delivery page while the client watches the video, with the option to leave a voice note. The feedback arrives tied to the edit and to the right moment, with no reconstruction on your end.
One list, one round
Resist the urge to fix things the moment the first note lands. If several people sign off on the client's side, wait for a single, coherent compilation before you touch the edit, or you risk undoing one change to make another that contradicts it.
Announce this from the moment you deliver: one place to reply, one round of batched feedback, a timecode per note. A frame set in advance beats an edit that restarts a correction on every notification.
In short
Usable video feedback comes down to three rules: a timecode every time, one channel, one batched list before you start. A structured revision request on the delivery page beats WhatsApp and email back-and-forth, not because the edit is any longer to fix, but because it finally becomes clear to understand.