Who this is for: Launch teams translating a specific creative job into a motion brief.
What to prepare
- Approved release status
- Verified platform or region facts if relevant
- Any eligibility conditions
- The real access destination
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 15- or 30-second availability reveal for PRODUCT_NAME. Use only AVAILABILITY_FACTS supplied by the release owner. Separate product identity, supported context and access status into readable information roles. Do not infer support from a device mockup or add platform logos without verified relevance. Introduce the product task briefly, then reveal one availability card at a time. Each card must name its exact status, such as available, beta, planned or waitlist, using approved wording. Keep an important eligibility condition beside the card it qualifies. Avoid a global map or universal checkmarks unless the supplied facts justify that scope. Hold the combined summary so viewers can see which statement applies to them. End with ACCESS_ACTION and the actual destination. If platform, region or timing information is unresolved, omit that claim and request confirmation rather than filling the visual layout with assumptions. The sequence should clarify access, not manufacture urgency.
Make it your own
- AVAILABILITY_FACTS
- Provide exact approved statements and their scope.
- STATUS_LABELS
- Keep released, beta and planned states distinct.
- ACCESS_ACTION
- Use the action the destination currently supports.
- PRODUCT_NAME
- Use the approved product identity and a short accurate task description before presenting access conditions.
Choose relevant facts
An illustrative launch might be waitlist-only with a planned desktop workflow. Showing phone, tablet and desktop checkmarks would imply broader availability than that brief supports.
If geography does not affect access, do not add a map simply to make the reveal feel larger.
Adapt the information density
Use one summary card when the access condition is simple. Use sequential cards when different audiences have different verified states.
For a longer version, explain the most important eligibility distinction rather than repeating the product's general benefits.
Correct false equivalence
If planned and available features share the same success styling, revise the labels and hierarchy. If a device mockup suggests a native app that does not exist, replace it with a neutral product frame.
Recheck the closing destination immediately before publication; availability can change after the storyboard is approved.
Review checklist
- Every availability statement has a current owner-approved source.
- Planned and available states are distinguishable.
- Device imagery introduces no unverified platform claim.
- The final action matches the relevant access state.