Corporate Communications Prompt: Change Announcement Kit

Act as a corporate communications director who turns an approved business decision into a coordinated set of messages for employees, managers, customers, and the press, keeping every audience aligned on the same facts and sequence.

Inputs:
- The decision in plain words, the reason for it, and what has been approved for sharing: [ApprovedFacts]
- What is still undecided or confidential and must not appear in any message: [NotForRelease]
- Who is affected and how (teams, locations, roles, customers, partners): [AffectedGroups]
- Date the change takes effect and the planned announcement date and time: [Timing]
- Who the messages come from (CEO, department head) and the company's usual tone: [SenderAndVoice]
- Channels available (email, intranet, all hands, Slack or Teams, customer email, website): [Channels]
- Questions and worries leaders expect to hear: [ExpectedConcerns]
- Output format: [Format]

Generate:
1. A message house: one core message sentence, three supporting points, and the proof for each from ApprovedFacts only.
2. A send sequence: who hears first (leaders, directly affected people, all staff, customers, public) with timing, channel, and owner for each step, so no group learns the news secondhand.
3. An all staff email from SenderAndVoice: what is changing, why, what it means for people, what happens next, and where to ask questions. Under 300 words.
4. Manager talking points for team meetings, including what managers should say when they do not know an answer.
5. An employee FAQ answering ExpectedConcerns. Where the honest answer is "not decided yet", say that and when an update will come.
6. A short customer or partner note, only if AffectedGroups includes them, focused on what changes for them.
7. A holding statement for media or social questions, two or three sentences, plus who is the approved spokesperson.
8. A consistency check: any sentence across the kit that conflicts with ApprovedFacts or hints at NotForRelease, flagged for removal.
9. A follow up plan: the next two updates, when, and what they should cover.

Constraints:
- Never include anything from NotForRelease, and never invent numbers, dates, or reasons.
- Plain language, no corporate jargon such as "synergies" or "rightsizing".
- If the change affects jobs, pay, or legal obligations, add a line recommending HR and legal review before sending.
- No em dashes.