Agency CMS and publishing handover matrix

Prepared by Derrick Kityo · Reviewed

Follow a new case study or campaign from approved material to a live page. Keep content fields, permissions and connected updates in the same record.

Completed fictional agency campaign example. Roles, records and URLs are illustrative, separate from Aura Ads or Creative Balcony operations.

1. Case-study scope

Example content or field
Client, work delivered and collaborator credit.
Owner
Project lead
Handover check
The wording accurately identifies the agency and delivery roles.

Your notes

2. Assets and permission

Example content or field
Approved images, logo and quotation record.
Owner
Account or content owner
Handover check
An editor can find the publishable versions and their restrictions.

Your notes

3. CMS entry

Example content or field
Project title, service links and page content.
Owner
Website editor
Handover check
Preview the complete page on a phone and check the intended project links.

Your notes

4. Migration or campaign URL

Example content or field
Old path and matching new destination.
Owner
Website owner
Handover check
The actual old link reaches the agreed page, rather than an unrelated homepage.

Your notes

5. Lead handoff

Example content or field
Campaign context and receiving team.
Owner
Marketing operations
Handover check
A fictional enquiry reaches the intended owner and records.

Your notes

Use this with your team

  1. Choose a real upcoming case study or campaign rather than auditing every historical item at once.
  2. Replace the example fields and roles with your actual CMS, source records and review owners.
  3. Ask a cover editor to rehearse the update, then check links, enquiries and the live page together.

Source notes

Google: site moves with URL changes
Use a URL map and test actual redirects during a migration. This worksheet complements the detailed migration checklist linked on the page.