
Start with a decision, not a topic
A brief is useful when it prevents two plausible but incompatible videos from being made. Replace “make a Reel about our reporting tool” with four fields: viewer, situation, outcome and proof. A workable line is: “For an agency account manager reconciling Friday reports, show how to find one missing campaign in under a minute, so they can decide whether to investigate the import.” The duration is a production constraint, not a promised result. The proof is the visible search and the flagged record.
Copy this fillable brief
Viewer: [role and experience]. Moment: [when the problem appears]. One outcome: [what the viewer can understand or do]. Evidence on screen: [demonstration, source, comparison or result]. Opening hypothesis: [why this first frame may earn attention]. Required context: [facts without which the clip misleads]. Action: [one next step]. Exclusions: [claims, features or audiences not covered]. Owner: [person who approves accuracy and rights]. This operationalizes the research report’s production system; it is an editorial method, not a platform rule.
See a hypothetical example
Imagine a neighborhood bakery testing pre-order pickup. The viewer is a commuter who passes the shop after work. The outcome is knowing how to reserve tomorrow’s bread before the cutoff. Proof is a screen recording of the real checkout flow plus a storefront shot. The opening hypothesis is “Tomorrow’s loaf can already be waiting.” The exclusion says the clip does not promise stock after the displayed cutoff. The action is “Open the pickup page.” This is a hypothetical planning example, not a report of bakery results.
Pressure-test before scripting
Ask a producer who did not attend the meeting to underline the viewer, outcome and proof. If they underline two viewers or three outcomes, split the assignment. If the proof depends on narration alone, identify what can be shown: a cursor path, product behavior, source card or before/after under matched conditions. Then check whether the proposed action is proportionate. A cold viewer may reasonably save a checklist; asking for a purchase may require more context. The brief should also name sensitive claims, releases, music scope and platform-specific disclosures before editing begins.
Use the brief as the review contract
At rough-cut review, do not ask whether the video feels punchy. Ask whether a stranger can identify the intended viewer, see the promised outcome and verify the evidence without hidden context. Log changes to the outcome separately from changes to the hook; otherwise a late stakeholder request quietly turns one test into another. Platform systems personalize distribution, and YouTube says performance includes whether viewers choose to watch and continue watching, but those signals do not rescue an unclear assignment. Its current Shorts discovery guidance is directional, not a guarantee. The brief’s job is narrower: make the editorial hypothesis falsifiable and the deliverable reviewable.
Put it into practice
Sources & limits
The template improves scope discipline but does not predict distribution, persuasion or conversion; teams should adapt legal and approval fields to their jurisdiction and risk.
- Search & discovery tips — Shorts ↗
YouTube identifies chose-to-view, average view duration and average percentage viewed as performance signals, while noting topic interest and competition also affect reach.
YouTube Help · Source publication date not stated · Reviewed: 2026-09-19