A video brief is a review-round prevention device that happens to also help the edit. Most painful rounds trace back to something the brief skipped: no references (so taste battles), no deliverables matrix (so the vertical cut appears in round three), no review rules (so feedback arrives from seven people by email). Design teams have standardized the brief; video teams mostly have a blank doc. Here is the skeleton with the sections filled in - copy it, and note that the last section (the review process) is the one that pays for itself first.
The copyable skeleton
- Objective (one sentence). What this video must accomplish, stated as an outcome: "drive trial signups from the pricing page" beats "make a cool launch film". The objective is also the tiebreaker in round disputes - the note that serves it wins.
- Audience + where it plays. Who watches, on what surface, in what context (muted autoplay on mobile is a different brief than a keynote screen). Where it plays determines specs, and specs are review criteria later.
- The message (three beats max). What the viewer should think, feel, and do. If the beats are not agreed in the brief, round one becomes a strategy meeting.
- Deliverables matrix. Every file: duration, aspect ratio, language, captions, end-card variants. A table, not prose - this is the section that kills scope creep and the "can we also get a 6-second bumper" surprise in delivery week. Ties directly to the proposal's deliverable section (video production proposal template), which prices the same matrix.
- References (two columns). "Like this" and "not like this" - three examples each, with one line saying what to take from them. References convert taste disputes into checkable facts and are the single highest-leverage section for round count.
- Mandatories + legal. Logos, legal supers, claims that need substantiation, accessibility requirements (captions - and audio description where visuals carry meaning), brand rules. Anything that must be in the final file, written here.
- Review process (the section everyone skips). Stated in the brief, not discovered in round two: how many rounds, what ends a round, where feedback lives (one review link - never email), who the decision owner is, and who reviews in which lane. Five lines that prevent the seven-channel feedback disaster.
- Timeline. Shoot, edit, round one, round two, lock, delivery - with the round dates as real calendar commitments, and feedback-latency expectations on the client side (48 hours to comment keeps the calendar honest).
- Success metric. How you will know it worked. The metric reframes round-two arguments: notes get weighed against the metric, not against taste.
Why the review-process section belongs in the brief
Everything in that section has a mechanical payoff on the review link: lanes match the stakeholder groups you named, the decision owner matches the approval rights, round rules match the version stack (version per round - video versioning carries the convention), and "feedback lives on the link" is the anti-scatter rule that keeps notes out of email (consolidating client notes is the cleanup manual for when it fails anyway). Teams that onboard clients formally already state these rules at kickoff - the client onboarding checklist and this brief section are the same five sentences, written at two different moments. Writing them twice is the point: the brief promises the process, the kickoff confirms it.
Common brief failures (and the round they cause)
| Brief gap | The round it produces |
|---|---|
| No references | Round one is taste discovery; rounds two and three relitigate it |
| Deliverables as prose | Round three: "we also need the vertical" - scope, not feedback |
| No named decision owner | Approval by silence, then a surprise note in week four |
| No mandatories list | Legal lands in the approval round, not the edit |
| No review rules | Feedback by email, doc, and voicemail; the editor consolidates by memory |
One closing honesty note: a perfect brief does not make rounds disappear - video is subjective and clients change their minds. The brief changes what rounds are about: with references and rules in place, round notes argue against the agreed frame instead of discovering it.
FAQ
What should a video production brief include?
Nine slots: a one-sentence objective, audience and playback context, the message in three beats, a deliverables matrix (every duration/aspect/language/caption variant), two-column references, mandatories and legal requirements, the review process (rounds, rules, decision owner), a timeline with round dates, and a success metric.
Who fills in the brief - client or agency?
The producer drafts it with the client's answers: you run the intake conversation, the client confirms. A brief the client writes alone usually misses the review-process section; a brief the agency writes alone usually misses the mandatories. Draft together, sign off once.
How detailed should the deliverables matrix be?
Every file that will exist: duration, aspect ratio, language, caption file needs, and any end-card or platform-specific variant. If it is not in the matrix, it is a new deliverable - and new deliverables are scope conversations, not review notes.
Does the brief really reduce review rounds?
The references and review-rules sections do, consistently: references make taste checkable, and stated round rules (one link, one owner, what ends a round) stop the feedback-scatter that manufactures extra rounds. A brief without those two sections is a nice-to-have; with them, it is process.