Nobody reads an internal announcement to be informed. They read it to answer one question: does this change what I do on Monday? If the answer is buried in paragraph four, the announcement has failed no matter how well written it is.
The fix is structural rather than stylistic. What is changing, first. What is not changing, second — because unaddressed silence gets filled with assumption. When it takes effect. Where to ask questions. Background and rationale go last, for the people who want them.
The eight templates
1. Policy or process change
Use when: a rule that affects daily work is changing.
Subject: [Policy] changes on [date]
What is changing: [one sentence].
What is not changing: [one sentence].
Effective: [date].
What this means for you: [the specific difference to how you work].
Why: [one or two sentences of rationale].
Questions: [channel or person].
2. New hire
Use when: someone is joining, and the team needs to know why and who to talk to.
Subject: Welcome [Name], joining as [Title] on [date]
[Name] joins us on [date] as [Title], working on [area].
[Name] comes from [previous organisation or background], where [they did what].
[Name] will be working closely with [teams] on [what]. [He/She/They] will be based in [location] and reachable at [channel].
3. Departure
Use when: someone is leaving. Keep it factual, and confirm with them before sending.
Subject: [Name] is leaving on [date]
[Name] will be leaving [Company] on [date]. [He/She/They] has been with us since [year], and [specific contribution stated without flourish].
Going forward, [responsibility] moves to [person or team]. Questions about [area] should go to [contact].
[Optional and only with their agreement: how to stay in touch.]
4. Promotion or role change
Use when: someone's scope is changing.
Subject: [Name] becomes [new title]
From [date], [Name] takes on [new title], with responsibility for [scope].
This follows [what they did that led here, stated concretely].
[Name] continues to [what stays], and [what changes for the people who reported to them].
5. Office move or workspace change
Use when: where people work is changing.
Subject: We move to [location] on [date]
From [date] our [office/floor] is [address or location].
What changes: [desk arrangement, commute, parking, meeting rooms].
What stays the same: [hours, team structure, equipment].
Before the move: [what to pack, by when]. First day: [where to go, who to ask].
6. Tool or system change
Use when: software people use daily is being replaced or upgraded.
Subject: We are moving from [old tool] to [new tool] on [date]
On [date] we switch [function] from [old tool] to [new tool].
What you need to do before: [action, deadline].
What happens automatically: [migrations, exports].
What stops working: [old tool, integrations] on [date].
Training: [session, date]. Help: [channel].
7. Team restructure
Use when: reporting lines or team boundaries change. This one needs more care than the others.
Subject: Changes to [team or department] structure
From [date], [what changes] — specifically [change 1] and [change 2].
Who is affected: [groups]. What stays the same: [explicitly named things].
We will [briefing sessions, dates]. Questions can go to [person or channel], including anonymously at [channel].
8. Planned outage or maintenance
Use when: something will be unavailable, and people need to plan around it.
Subject: [System] unavailable [date], [start]–[end] [timezone]
[System] will be unavailable from [start] to [end] on [date] for [reason].
Affected: [what users will notice].
Not affected: [explicitly named systems].
Save work before [time]. If it is not restored by [time], we will update [channel].
Three lines that decide whether it gets read
The subject line carries the change, not the topic. "Update to our expense process" tells you nothing; "Expense receipts now need pre-approval from 1 Nov" tells you everything. The first line states the effect in one sentence — if it cannot be stated in one, the announcement is trying to cover too much. The last line names a person. A channel with no owner gets no questions, and unanswered questions turn into hallway speculation.
Timing and channel
Send changes that affect Monday on Thursday or Friday — not Monday morning, when the reader already has the day planned. Never let a rumour beat the announcement; if it might leak, send it earlier and less polished. And for anything affecting more than a handful of people, put it somewhere permanent rather than only in chat, because chat scrolls away and the question will be asked again in three weeks.
Write the change, not the topic
Draft the announcement in a tool, then check the first line answers "what changes for me". If it does not, rewrite the first line.
Try Rytr →Frequently Asked Questions
Where should internal announcements go?
Somewhere permanent and searchable first, chat second. Chat is fine for the pointer, poor as the record.
How long should one be?
Short enough to read without scrolling. Move background and rationale to the bottom or a linked page.
Should I name people in a departure note?
Only with their agreement, and only what they are comfortable with. When unsure, ask.
What if I do not have all the answers yet?
Send what is settled and name the date the rest will follow. Silence gets filled with worse guesses.
Do I need to state what is not changing?
Yes, especially in a restructure. Unaddressed areas are assumed to be in scope.
Can AI draft these?
Yes for structure and neutral phrasing. Have a person check anything involving individuals, roles or pay.