Best Prompts for Internal Communications

Organizational changes create two communication problems at once. Employees need a clear explanation of what is changing, why it matters, and what they should do. Managers need enough detail to answer questions consistently without improvising policy or sharing information that has not been approved.

When the announcement is vague, people fill the gaps themselves. When it is overloaded with corporate language, they may miss the practical impact. A coordinated announcement and manager FAQ can reduce avoidable confusion while preserving honest uncertainty.

Why ordinary prompting fails

“Write an upbeat change announcement” puts tone before accuracy. An AI may minimize disruption, promise a smooth transition, or invent reassuring details about roles, timing, support, or employee impact. It may also give managers answers that go beyond the approved decision.

A better prompt starts with confirmed facts, affected audiences, effective dates, and decision boundaries. It requires the announcement and FAQ to use the same source of truth and makes unanswered questions visible.

The prompt

Copy
ROLE
You are an internal communications lead preparing an employee change announcement and a manager FAQ. Your job is to communicate confirmed information clearly, acknowledge uncertainty, and help managers route questions appropriately.

REQUIRED INPUTS
- Approved description of the change
- Business reason that may be shared
- Affected and unaffected audiences
- Effective date, transition dates, and key milestones
- Confirmed impact on roles, workflows, systems, locations, policies, or customers
- Actions employees and managers must take
- Support channels, resources, training, and named contacts
- Approved language, confidential topics, and legal or HR constraints
- Questions already raised by employees or managers
- Sender, communication channel, and publication date

STEPS
1. Extract confirmed facts, approved rationale, required actions, known impacts, and unresolved questions.
2. Identify what each audience needs to know now, later, or only through a private channel.
3. Draft an announcement that states the change early, explains why it is happening, describes practical impact, gives dates, and lists required actions and support.
4. Avoid false reassurance, promotional language, and promises not supported by the inputs.
5. Draft a manager FAQ covering likely questions about timing, responsibilities, workload, process, support, and escalation.
6. For sensitive or unanswered questions, provide a safe response boundary and the correct referral path rather than inventing an answer.
7. Check the announcement and FAQ for contradictions.
8. Create a pre-publication verification list.

OUTPUT FORMAT
# Employee Change Announcement
Subject:
Opening summary:
What is changing:
Why it is changing:
Who is affected:
What happens and when:
What employees need to do:
Support and resources:
What is still being finalized:
Closing and contact:

# Manager FAQ
For each question include:
- Approved answer
- What the manager should not speculate about
- Referral or escalation path
- Source

# Manager conversation guide
- Three points to emphasize
- Questions to invite
- Concerns to record and escalate

# Pre-publication verification
A checklist for facts, dates, audiences, links, accessibility, approvals, and channel timing.

EVIDENCE AND UNCERTAINTY RULES
- Use only approved, supplied information.
- Do not invent employee impacts, implementation details, rationale, support commitments, or future decisions.
- Cite the source or approver for sensitive answers.
- State “This has not yet been confirmed” when necessary and provide the next expected update only if supplied.
- Do not imply that no disruption, role change, or concern will occur unless that statement is explicitly approved and supported.
- Flag content requiring HR, legal, executive, or policy-owner review.

What to provide

Give the prompt the approved change brief, dates, audience list, impact assessment, and required actions. Include the exact names of systems, policies, teams, and support channels. If different groups will receive different information, specify those boundaries and the order of communication.

Add the questions already being asked, including difficult ones. Managers benefit more from an honest response boundary than from a polished answer that has not been approved. Clearly identify confidential information and do not provide it to a system or audience that is not authorized to receive it.

How to review the output

Start by checking the first paragraph. An employee should be able to identify the change and its relevance without reading several paragraphs of context. Verify every date, audience, required action, link, and contact.

Compare the FAQ against the announcement line by line. Managers should not receive a different explanation of the reason or timing unless the distinction is intentional and approved. Ask HR, legal, policy owners, or leadership to review the sections within their responsibility.

Finally, test the draft with a reader who has not been involved in planning. Ask them what is changing, when it affects them, what they must do, and where they would go with a question. Their answers will reveal whether the message is practical enough.

Where it fails

No prompt can compensate for an unmade decision or an unwillingness to explain material impact. If the organization has not confirmed the timeline, responsibilities, or support model, the draft should expose those gaps rather than hide them.

Sensitive changes involving employment, compensation, restructuring, legal obligations, health, safety, or labor relations require qualified review and careful sequencing. The prompt also cannot manage the human response to difficult news. Managers need time, context, and a real escalation route, not only a document.

Practical takeaway

Clear change communication says what is known, what people must do, and what remains unresolved. It gives managers approved language without asking them to pretend certainty. Try this prompt in Agentic Workers with the approved change brief, then complete the human reviews and audience checks before anything is published.

<!-- X derivative: A useful change announcement pairs clear employee actions with a manager FAQ that acknowledges uncertainty and prevents unsupported answers. -->