Give the content one clear job
Before choosing a creator or writing a script, finish this sentence: after watching, the viewer should understand, feel or do this one thing. A product introduction, a useful tutorial and a sales offer are different jobs.
Keep the objective specific enough to guide a decision. 'Show how this fits into a weekday routine' is more useful than 'make us go viral'. Neither is a promise of reach or revenue.
Separate requirements from suggestions
Requirements define what must be present: the correct product, a demonstrable feature, approved claims, language, duration, delivery route and any necessary disclosure. Put one requirement on each line.
Suggestions can include opening angles, locations, pacing or a reference video. Explain what you like about a reference instead of asking for a copy. Let the creator choose phrasing and execution within the agreed boundaries.
Use a brief you can review against
Use this checklist while drafting in Vouched. Availability of individual fields depends on the campaign format and the current editor.
- State the goal and intended audience.
- Name the deliverable: submitted file, public channel post or both, with the applicable format.
- Add talking points, suggested hooks, visual requirements and things to avoid.
- Provide the correct product or app links and examples the creator can access.
- Agree compensation, usage rights, deadlines, revisions and any visit or booking details before work starts.
- Review the complete brief from the creator's perspective before launching. Do not assume live campaign terms can be edited freely.
Make feedback point back to the brief
A useful review names the unmet requirement and the change needed. 'Please show the app screen clearly in the demonstration' is actionable. 'Make it more engaging' leaves the creator to guess.
If the goal changes, discuss a new scope rather than treating a new creative direction as a correction. A clear agreement protects both the brand's outcome and the creator's time.
Common questions
Should every line be scripted?
Script exact wording only when it is genuinely required, such as an approved product claim. Keep optional hooks and style references separate from mandatory requirements.
Need a hand?
Use Feedback in your dashboard if a guide does not answer your question. Include the page, what you expected and what happened. Never include a password, API key, account number or private payload.
Open brand workspace