ES Start a project →
Workflow · 2026

How to give editor feedback that actually gets results

The right and wrong ways to send feedback. When to be specific, when to back off, when to do a video call instead of Discord, and the unspoken rules that separate fast revision rounds from painful ones.

By Kevin Tabares · Apr 21, 2026 · 9 min read

Most of the friction in creator-editor relationships doesn't come from skill mismatches. It comes from feedback that's vague, contradictory, or phrased in a way that makes the editor defensive. You watch a rough cut, something feels off, and you send a message like "make the energy better" or "tighten it up." Your editor has no idea what you mean. Three days later you get a revision that missed the mark by a mile, and now you're frustrated and they're frustrated.

The best creator-editor pairs have a shared language for feedback. Specific but not micromanaging. Technical but not condescending. Urgent when it matters, patient when it doesn't. This guide covers the patterns that work — and the ones that consistently create friction.

Vague feedback is expensive feedback

Vague: "The pacing feels slow in the middle."

Specific: "The pacing dips between 3:00 and 5:00 — there's air after you finish the first point and before you pivot to the second. Cut that dead air or cover it with B-roll."

The difference is 15 minutes of edit time vs 3 hours of guessing. When you give specific feedback, you're telling your editor exactly what to cut, what to reframe, or what B-roll to add. They can execute in one pass. Vague feedback sends them back to hunt for the problem.

Always include:

If you can't be specific, you don't fully understand what's wrong yet. Watch it again. Take notes. Then send feedback when you know what you're asking for.

The specificity rule: An editor should be able to execute your feedback in a single pass without asking for clarification. If they need to message you back asking "what do you mean?", your feedback was too vague.

Written vs voice feedback (and when to use each)

Use written feedback for:

Written feedback is traceable, searchable, and gives the editor time to think through the changes. It also forces you to be clear — you can't wave your hands vaguely in a text.

Use voice feedback for:

Voice memos are faster. But if you're sending more than a one-minute voice note, you should've written it down. Your editor will play it back three times trying to remember what you said at 0:42.

When to do a video review call instead

Video review calls are expensive in time. But they're free in comparison to an edit that completely misses the mark and requires a full re-cut.

Do a video call if:

In a call, you can show the editor your retention graphs, reference other videos in real time, and notice when their interpretation diverged from yours. You catch the mismatch on the first revision instead of the second.

Skip the call if:

The unspoken rules of revision rounds

Two rounds are standard. If your contract says two revisions and you're asking for a third, that's escalation. Some editors absorb one extra round. Others charge. Know the terms upfront.

Scope creep kills relationships. If you asked for "tight pacing" and your editor delivered tight pacing, and now you're asking them to "add more energy" and "switch up the B-roll strategy," that's scope creep. You moved the goal post. Either you misunderstood the brief or you're developing new ideas mid-edit. Acknowledge it: "I know this is outside our original scope — how much extra would this cost?" Editors respect directness more than demands masked as feedback.

Don't ask for contradictory feedback. "Make it longer but also tighter" or "keep all the moments but cut the pacing dead time" is contradictory. You can't do both. Editors will choose one and you'll be unhappy. Be clear about priorities: "I'd rather lose length than lose pacing."

Turnaround expectations are two-way. If you ask for feedback to be done in 24 hours, your editor needs 24 hours to deliver. If you send feedback at 11pm Wednesday expecting it Friday morning, adjust your timeline. They're not a customer service line.

"The editors I work with longest are the ones who understand that revision rounds are collaboration, not criticism. They brief clearly once, trust me to nailed the edit, and only ask for changes when something genuinely doesn't match the brief."

Tone is invisible in text but editors feel it

Wrong: "This is way too slow. Fix it."

Right: "This feels slower than I'd like. Can you tighten the pacing in the 3:00-5:00 section?"

The second one assumes your editor is competent and tried their best, and you're just asking for a direction change. The first one sounds like criticism. Both ask for the same thing. One makes your editor want to do the next revision quickly. The other makes them defensive and slower.

Most editors are independent contractors. They chose to work with you. If every feedback round feels like criticism, the relationship decays. Feedback that sounds collaborative holds relationships together.

When to say "this isn't working, let's restart"

Sometimes you watch the first cut and it's fundamentally misaligned. The editor shot for a different vibe, misunderstood the brief, or nailed something you didn't actually want. Rather than ask for three revisions that still won't land, call it: "I realize my brief was unclear. This doesn't match the direction I want. Let me re-brief and you start fresh."

This is collaborative. Your editor gets to start over with better direction. You get a video that matches your vision. Most editors prefer this to three revision rounds that never land.

What you don't do is ask them to eat the work. If you're asking for a restart, they should be paid for the initial cut or you're setting a bad precedent for the next video.

Related guides

Workflow
How to brief your video editor: the template that prevents revisions
Hiring
How to hire a long-form YouTube editor in 2026
Hiring
How to test an editor in one paid trial video