Who this is for: Launch teams translating a specific creative job into a motion brief.
What to prepare
- Verified integration scope and release status
- The exact source and destination
- A supplied example of the transferred item
- Approved identity assets and eligibility
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second announcement for NEW_INTEGRATION in PRODUCT_NAME. The verified new capability is NEW_SCOPE. Show SOURCE, TRANSFERRED_ITEM and DESTINATION with clear labels. This brief describes the reader's product integration; it does not imply that Animro connects to either service. Open with USER_TASK, then explain what has newly become available. Use a simple directed path to show the verified handoff. Keep the same example value or object visible before and after transfer. Do not add two-way arrows, real-time timing, automatic setup or additional fields unless the supplied scope supports them. Show any prerequisite needed to interpret the announcement, then hold the destination result. Include ELIGIBILITY and CURRENT_STATUS beside the access invitation. Keep setup detail subordinate; a separate walkthrough can cover field mapping and troubleshooting. If the source assets conflict about direction or supported data, flag the mismatch before production.
Make it your own
- NEW_SCOPE
- State exactly what is newly supported.
- TRANSFERRED_ITEM
- Use one approved field or object with consistent example content.
- ELIGIBILITY and CURRENT_STATUS
- Use verified release facts and access conditions.
- NEW_INTEGRATION and PRODUCT_NAME
- Use the approved relationship and product names without implying unapproved partner endorsement.
- SOURCE and DESTINATION
- Identify the exact endpoints and verified transfer direction.
- USER_TASK
- Describe the concrete task enabled by the newly supported scope, distinct from setup instructions.
Focus on newly available scope
An illustrative task tool might newly accept one labeled event from another system. The announcement can show that event reaching a task record, while avoiding claims about every event type or reciprocal updates.
This page's job is announcing scope and relevance; the detailed configuration belongs in another resource.
Adapt the proof
If real screens are supplied, use them to show the source item and destination result. If only an approved flow diagram exists, label the sequence as an explanatory diagram rather than a recorded transfer.
For a longer version, add one limitation or eligibility detail that affects the viewer's decision.
Correct expanded scope
Remove bidirectional arrows when the connection is one-way. Remove instant-transfer effects when no timing evidence is supplied. Do not let decorative partner logos imply endorsement or support beyond the approved relationship.
Keep the ending aligned with the actual integration release state.
Review checklist
- The new scope is stated precisely.
- Source and destination direction are accurate.
- The same example item persists through the handoff.
- No automatic setup or broader synchronization is invented.
- The access condition is visible.