How to brief a video editor.
Most revision rounds are not disagreements about the edit. They are the brief arriving late, one note at a time.
By Team Gaurify, Gaurify Productions5 min read
Almost every painful edit we have seen, ours or anyone else's, has the same shape. The first cut comes back, it is not right, and the notes that follow slowly reveal what the video was supposed to be. By round three everyone knows the brief. It just arrived in instalments, after the work.
Briefing well is not about writing more. It is about front-loading the few decisions that everything downstream depends on.
The six things worth saying
Who it is for. Not the demographic, the person. "Founders who already post and are getting nothing back" tells an editor how fast to cut, how much to explain, and what tone will not survive contact with that audience.
What it has to do. Build authority, drive a click, explain a product, or start a conversation. These produce genuinely different edits. A video meant to convert ends differently from one meant to be remembered.
Where it is going. A Reel, a Short, a LinkedIn post, and a YouTube video are four formats, not one video in four sizes. Say which is primary, because the primary platform decides the aspect ratio, the pacing, and whether the first frame has to work silently.
The one line that must survive. If the whole video collapsed to a single sentence, which sentence is it. This is the most useful thing in any brief and the least frequently included. It tells the editor what the structure has to protect.
What you do not want. Constraints save more time than preferences. No trending audio, no zoom transitions, no captions covering faces: each of those is one revision round you never have.
Anything technical. Brand colours, fonts, logo placement, subtitle style, and any legal or compliance rule. Boring, and it is the category that causes the most rework when it shows up late.
References, with reasons
Sending three videos you like is helpful. Sending three videos you like with one line each about why is transformative.
"This one for the pacing", "this one for how the captions sit", "this one for the tone, not the graphics". Without that, an editor is reverse-engineering your taste from evidence, and they will guess wrong on at least one dimension. It is the cheapest clarity available to you.
Give feedback that can be acted on
The second half of briefing happens after the first cut, and this is where most weeks get lost.
Useful notes point at a timestamp and describe a problem. "The section at 0:22 drags" is actionable. "It feels off" is not, and the round that follows it is guesswork. If you cannot name the fix, name the feeling and the moment it happened, and let the editor solve it. Diagnosing is your job. Prescribing is theirs.
Collect notes in one pass, from everyone who gets a say, before sending. Three people sending contradictory notes over two days is the single most expensive pattern in content production, and it is entirely avoidable.
And separate two things that look alike: a fix, which is the edit not matching the brief, and a new idea, which is the brief changing. Both are fine. Calling the second one the first is how timelines quietly break.
The brief that repeats
If you are publishing regularly, write the standing rules once rather than restating them every time. Format, captions, brand assets, tone, the things you never want. Then each video only needs what is different about it.
That is what a production system is, underneath the software: the decisions made once so they do not have to be made again. We wrote about the wider version of that in what a content system looks like, and it is why every project we run lives in Gaurify OS, where the standing brief sits in one place and each video only carries its own notes.
Get the first cut close and the rest is detail. That is the whole game.
Tell us who it is for and what it has to do. We will handle the rest. Start a project.
Common questions.
Straight answers before you decide.
How long should a brief be?
Shorter than you think, as long as it answers who the video is for and what it has to achieve. Half a page that names the audience and the goal beats three pages describing shots.
Should I send reference videos?
Yes, and say what you like about them. A reference without a reason is a guess: an editor cannot tell whether you sent it for the pacing, the captions, the colour, or the energy.
What if I don't know what I want?
Say that plainly. It is a legitimate brief, and a good editor will make the first pass a proposal rather than a delivery. What wastes time is pretending to have a direction and discovering the real one during revisions.
How many revision rounds are normal?
Two, when the brief was clear. Round one catches structure and pacing, round two catches detail. If you are routinely at four, the problem is upstream of the edit.
Send us a brief. We'll do the rest.
Not ready to commit? Try a sample edit first →
Sixty seconds to configure. One reply, within the day.