When this is useful
Requests such as “make it premium” describe a feeling but leave the crucial decisions unresolved. A useful brief translates taste into observable choices: fewer headlines, slower evidence shots, a defined colour palette and a particular ending.
The working process
- Choose one audience and one action you want them to take after watching. State what they already know so the introduction does not repeat unnecessary context.
- Pair the central promise with source evidence. Identify available recordings and any missing scenes that need capture before editing can start.
- Specify format, tone, reference characteristics and exclusions. Describe the quality bar in reviewable terms, such as readable labels and a complete action-to-result sequence.
A production example
An illustrative brief could ask for a landscape launch demo showing a support ticket becoming an assigned task, with a calm opening, two readable close-ups and a final invitation to try the workflow. That is more actionable than “make a cinematic SaaS video”.
Brief skeleton
Illustrative copy to adapt. Replace bracketed fields and verify every claim against your product.
Limits and checks
References communicate direction; they do not grant rights to copy another studio’s project, music or artwork. Capability requirements should be checked against the recorder and editor you will actually use.
Your next step
Approve the brief before generating several variants, then judge each variant against the same evidence and audience.
References and scope
Examples are illustrative production guidance, not measured customer results. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.