Turn a company announcement into a coordinated comms rollout

Start in Google Docs with one source brief that explains what is being announced, why it matters, who is affected, and when it can be shared. Add the approved headline, core message, spokesperson quote, audiences, launch date, embargo notes, partner or customer restrictions, approved claims, and phrases to avoid. Mark which facts are public, internal-only, partner-sensitive, or still pending review so Claude does not treat every detail as usable copy. Include one owner who can resolve conflicts when legal, executive, customer, or partner feedback disagrees. This brief becomes the source of truth for every downstream asset, so do not start channel drafting until it is approved.

Create an Airtable rollout tracker with one row per audience and channel. Include employees, customers, prospects, partners, press, analysts, investors, sales, customer success, executives, and the brand social account only if each audience truly needs a message. For each row, define the communication purpose, asset type, CTA, owner, reviewer, approval status, publish window, and suppression notes. This prevents the common failure mode where every channel receives the same generic announcement instead of the version that audience actually needs. Add a review owner and deadline to every asset so the rollout is operational, not just a list of copy ideas.

Create an announcement rollout map from this source brief.

Announcement brief:
{{announcement_brief}}

Possible audiences:
{{audience_list}}

Channels available:
{{channels}}

Launch date and timing restrictions:
{{timing_rules}}

For each audience and channel, output:
1. Asset needed
2. Purpose of the message
3. Primary CTA or action
4. Owner
5. Required reviewer
6. Approval risk
7. Publish window
8. Suppression or restriction notes

Do not create assets for audiences that do not need a message.