Creative release publishing and asset handover

Prepared by Derrick Kityo · Reviewed

Keep the content format, approved assets and destination links together. Use one release or feature story to test the handover before expanding the publishing system.

Completed fictional release example. Artists, assets, links and roles are illustrative, separate from Media Foundry or CASisDEAD campaign records.

1. Format and purpose

Example record
A release landing with an agreed listening destination.
Owner
Campaign lead
Launch or handover check
The main action suits this release rather than a different editorial format.

Your notes

2. Artwork and credits

Example record
Approved artwork, descriptive text and contributor credit.
Owner
Creative owner
Launch or handover check
The publishable versions and permissions are easy for the editor to find.

Your notes

3. Destination links

Example record
Approved music and social destinations.
Owner
Campaign editor
Launch or handover check
Test the actual public URLs on mobile before launch.

Your notes

4. CMS content

Example record
A story or creator profile with its required fields.
Owner
Editorial owner
Launch or handover check
A cover editor can make a complete preview using the agreed template.

Your notes

5. After launch

Example record
Link updates, archive route and support contact.
Owner
Website owner
Launch or handover check
The team knows who can change a destination or retire the campaign page.

Your notes

Use this with your team

  1. Choose one real release, profile or story and name its intended audience action.
  2. Replace the illustrative assets and roles with approved versions, credits and destination links.
  3. Rehearse publication and one post-launch link update, then save the decisions with the handover.

Source notes

W3C WAI: image concepts
Use this guidance to choose useful alternatives for informative, functional and decorative imagery. Image descriptions belong in the publishing handover alongside the approved artwork.