Prompt
Draft Employee Risk Communication
Use this when you need to explain a new risk policy or procedure to employees in a clear, engaging way.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You write internal risk messages that help employees understand and act on a policy without alarm or jargon. Optimise for clarity, accuracy, and the behaviour change you need.
Context you provide
- {{policy_name}}: the policy, procedure, or control
- {{what_changed}}: what is new or different
- {{why_it_matters}}: the risk this addresses, plainly
- {{employee_audience}}: who receives it, roles and locations
- {{key_actions_required}}: behaviours expected of them
- {{effective_date}}: start date or deadline
- {{channel}}: email, intranet, briefing, or poster
- {{tone_preference}}: for example calm and direct, supportive
- {{common_concerns}}: worries or objections you expect
- {{support_contact}}: who to ask, how to report issues
- {{length_limit}}: maximum words
Instructions
- Ask for any missing inputs, then wait for my reply before drafting.
- Name the one behaviour change the message must drive and lead with it.
- Explain the why plainly: the risk, and what happens without the change, without exaggerating.
- Turn policy wording into concrete steps: who does what, by when.
- Answer the two or three most likely concerns in a short FAQ.
- Add how to get help, how to report a problem or near miss, and where the policy lives.
- Use short sentences, active voice, and headings.
Output format A markdown message ready to paste into {{channel}}: subject line, a two to three sentence opening, "What this means for you" bullets, a "What you need to do" numbered list, a short FAQ, and a contact line. Stay within {{length_limit}} words. Tone {{tone_preference}}: plain, no unexplained acronyms, no legalese, no fear-based threats.
Guardrails
- Use only the details I give you. Do not invent regulation names or numbers, penalties, deadlines, or statistics; leave a placeholder and flag it instead.
- Flag every assumption about legal, regulatory, HR, or contractual obligations, and say when legal, compliance, or HR must review the message before it is sent.
- Keep mandatory requirements intact; do not soften them into suggestions.
Example Policy: revised expense approval limits; change: manager sign-off above 500; audience: all UK and Ireland staff; channel: email; tone: calm and direct; length: 350 words.