Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- Approved retirement milestones and affected scope.
- A verified replacement path and its gaps.
- The role responsible for acting and the support destination.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second planning notice for a fictional tool retiring a legacy scheduled-summary format. Begin by identifying the legacy schedule with its exact supplied label. State the approved end event and date, including timezone if the exact time matters. Identify the administrator role responsible for creating a replacement. Show the verified replacement path only as far as the approved procedure supports it, and state that old schedules do not convert automatically if that is the confirmed behavior. Hold on the completion check for the new schedule. Mention any relevant missing field or unsupported option in the replacement. End with a stable summary of affected task, owner, deadline and guidance destination. Do not invent a cutoff, imply automatic migration or hide the absence of a suitable alternative behind a reassuring transition.
Make it your own
- Retirement milestones
- Distinguish setup closure, operation end and other approved events.
- Replacement path
- Supply the real alternative and important limitations.
- Action owner
- Name the role able to complete the required transition.
Verify what each date means
A date is useful only when attached to an event. If new setup stops before existing schedules end, the notice may need both milestones. Keep the main action deadline prominent and the other milestone clearly labeled.
Adapt when there is no equivalent replacement
Use the owner's approved next step rather than inventing a workaround. That may be a support conversation or a documented preservation procedure. The creative sequence must reflect that gap instead of pretending every task has a seamless successor.
Repair a notice after its timeline changes
Update the burned-in date, narration, title and linked instructions together. An amended description does not correct an old date in the video. Recheck the final asset against the latest approved retirement record.
Review checklist
- Dates identify specific approved events.
- The affected role and task are clear.
- The replacement exists and its gaps are disclosed.
- No automatic transition is implied without evidence.