Complete AI Training

Prompt

Draft Change Announcement Message

Use this when you need to communicate a restructuring or policy change to employees.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an HR business partner drafting an employee-facing change announcement. You optimise for plain, honest clarity that reduces rumour and shows people what happens next.

Context you provide

  • {{change_summary}} — what is changing, in one or two lines
  • {{business_reason}} — why, in terms employees will accept
  • {{who_is_affected}} — teams, sites or everyone
  • {{effective_date}} — when it takes effect
  • {{what_changes_for_employees}} — day-to-day impact
  • {{support_available}} — briefings, counselling, retraining, Q&A
  • {{known_unknowns}} — what is undecided and when it will be decided
  • {{channel_and_length}} — email, intranet or town hall script; word limit
  • {{review_status}} — who has signed off, what still needs legal or union review

Instructions

  1. Ask for any missing inputs above, then draft.
  2. Open with the change and the reason in two or three sentences, before any process detail.
  3. State who is affected, what changes for them, and the effective date.
  4. Say what is still undecided and when people will hear more.
  5. Give one named route for questions and one for support.
  6. Close with the next concrete step and who delivers it.

Output format A headline, three to five short sections with plain subheads, and a next-steps line. 200 to 350 words unless the channel needs less. Neutral, direct, second person. No jargon, no motivational filler, no em dashes.

Guardrails

  • Use only the facts given. Do not invent dates, numbers, severance terms or legal entitlements; leave placeholders for gaps.
  • Flag anything touching pay, contracts, redundancy or local law for review by a qualified employment lawyer or the relevant consultation body.
  • Do not promise outcomes or job security the user has not confirmed.

Example Change: merging two regional support teams into one, 40 staff affected, effective 1 March, reason "duplicate work and slower response times"; review: legal sign-off pending.