Announce a colleague’s departure on Slack or Teams

To move from reading to a structured collection, open a colleague farewell card page—one link, centralized messages, PDF export.

The post pings everyone's notifications: too terse and it reads like admin; too long and nobody scrolls to the link. On Slack or Teams, the sweet spot is an announcement you can read in a few seconds that still opens the door to notes and a guestbook — without flooding the channel.

The goal is not to write a "perfect message." The goal is to publish something usable now that respects the person leaving and gives the team one clear action.

In practice, the announcement does not replace the card — it launches it. Think of it as a simple triad: facts (who is leaving, when), recognition (one credible team line), action (link + deadline). If the guestbook is already open, the post mainly sets tone and keeps replies from getting lost in the noise.

What this looks like on real teams (scenario-level)

Typical scenario: a hybrid team, a short runway before the last day, and a busy team channel. You need everyone informed without notification spam, while still giving distant time zones a fair window to contribute.

What teams tend to value: one clear opening post, the guestbook link on its own line, a cutoff with an explicit time zone, and a simple thread rule (stories in-thread, structured notes on the link).

Common observed mistake: a warm but long message where the link is buried mid-paragraph — lots of channel reactions, but fewer people actually land on the guestbook page.

A short structure that actually works

1. Factual hook: "Today is Alex's last day with us."
2. One concrete line of team gratitude (impact, working style, shared moment).
3. Clear instruction: where to write, and by when — ideally on its own line for the link.
4. Collective sign-off (manager, team, or People team).

If you need language ideas, keep this structure and borrow phrasing from our list of touching farewell messages. For card content (tone, timing, phrases to avoid), pair it with common mistakes and templates.

Five message models by context

Each model below is intentionally short: swap names, times, and ritual details (onsite party, video farewell, no event). What matters is that the person leaving feels seen by the team — not processed.

1) Classic departure (next role already shared)

When to use: voluntary move, calm context, the team already knows what is next (new company, career change, planned long break).

Tip: one line about what is next is enough; no need to repeat what is already on LinkedIn or in a team meeting.

"Team, today is Claire's last day with us. Thank you for your impact on product launches and your support in day-to-day work. You can leave Claire a note here before 5pm: [link]. Wishing you the best, Claire!"

2) Remote departure (distributed team)

When to use: multiple time zones, few shared in-person moments, or a team that mostly meets on video.

Tip: state the time zone for the deadline and say whether messages will be read aloud or shown on screen — that nudges people who worry about writing something "too personal."

"Sami's last day is today. Even remotely, Sami created strong team connection and smoother handovers. Please leave a note in the guestbook before 6pm Paris time: [link]. We'll share selected notes in tomorrow's video farewell."

3) Manager departure

When to use: the manager is leaving; the post should mark the moment without hagiography or shutting down the team voice.

Tip: have the announcement posted by leadership (skip-level, director) or People — not by the departing manager — so it reads clear and avoids awkwardness.

"Today we are marking Nora's departure after two years of leading the team through growth. Thank you for the clarity, trust, and support you brought to daily work. If you want to leave a personal or professional note, use this link before end of day: [link]."

4) Sensitive departure (discreet context)

When to use: mutual separation, departure after conflict, burnout, or any situation where details are not for the whole channel.

Tip: align the wording with HR and, when possible, with the person leaving; avoid ambiguous humor, hints, and thread questions like "where are you heading?"

"Today we are marking Paul's departure. Thank you for your contribution and commitment across team projects. If you would like to leave a short and kind note, you can do it here: [link]."

In this case, keep it intentionally simple: no ambiguous humor, no private details, no speculation.

5) Departure with a planned party (onsite or virtual)

When to use: you have a celebration date and you want to avoid everyone repeating the same long story in the channel before the event.

Tip: separate "write on the guestbook" from "channel noise": invite longer notes on the link, keep the channel for logistics or a quick RSVP emoji.

"We'll meet at 6pm to celebrate Lina's departure. Before that, please add your note here: [link]. We'll read selected messages during the party, and a PDF keepsake will be shared with Lina afterward."

For event logistics, use the farewell party checklist or, for distributed teams, the virtual farewell guide.

Slack and Teams pitfalls to avoid

Both tools share the same basics (channel, notifications, threads), but habits differ: what works in a 12-person project channel can feel heavy in a broad general channel.

Slack-specific

• @channel vs @here: @channel pings people who are away; use it sparingly for one well-crafted post, or prefer @here if your workspace still uses it for people who are present.
• Thread vs main channel: if emotional replies pile in the main timeline, the link sinks fast. Say explicitly: "Stories in the thread — guestbook link stays in the pinned post."
• Link previews: check the unfurl (title, image) before sending; a broken or silly preview reads careless. Fix the page title if you can.
• Emoji and joke stacks: a few reactions, yes; a wave of GIFs on a sensitive departure, no.

Microsoft Teams-specific

• Announcements channel: if your org uses it, a structured announcement can beat a long block in general chat — still keep one obvious sentence with the link.
• Meeting chat vs channel: posting only in a recurring meeting chat makes the news disappear. Mirror the essentials in the durable team channel.
• Very large teams: posting in "General" can expose someone to a wide audience. Prefer the tighter team channel first, then a controlled relay.
• Mobile notifications: the first paragraph is often all people see on a phone; put the essentials up top, not after three lines of context.

Shared pitfalls (Slack and Teams)

• Wrong channel choice: posting in a very broad channel can feel like a cold broadcast. Start in the core team channel, then relay if needed.
• Too many mentions: a workspace-wide mention plus multiple same-day reminders creates fatigue. One main post plus one reminder is usually enough.
• Buried link: if the link sits inside a long paragraph, people skip it. Put it on its own short sentence.
• Unframed thread behavior: without guidance, replies scatter. Say "reply in thread" or "add your note on the guestbook link."
• Humor drift: a joke that works in one small group may age badly in a cross-team channel. Quick review before posting helps.

Card wording deserves the same care: tone, clichés, and timing mistakes are covered in farewell card mistakes and templates.

Announcement timing: what is realistic

Initial announcement

When possible, post between D-5 and D-2 before the last day. That gives remote colleagues and people in back-to-back meetings enough time to contribute without a rush.

If the departure is only confirmed at D-3 or D-2, still open the guestbook immediately and state a tight deadline in the post — people handle a short window better when it is explicit than a link that quietly opened ten days ago without them noticing.

Time zones and hybrid teams

Always name the time zone for the cutoff. If part of the team is in the Americas and part in Europe, a 9am Paris close without context silently excludes contributors.

One useful follow-up

One reminder on D-1 or on the morning of D-day is enough in most teams. More than that often increases noise more than participation quality.

Who should post the announcement?

• Direct manager: usually the best owner because the message feels both legitimate and human.
• People/HR: useful for sensitive contexts, cross-department moves, or when the manager role just changed hands.
• Organizing teammate: works well in small tight teams if tone is aligned with manager and HR before sending.

The key is one single official voice for the initial announcement, so people do not see duplicates or mixed instructions. Behind the scenes, HR often reviews sensitive wording, or a manager sends from their account after sign-off — either is fine as long as the channel does not get three conflicting versions.

Also clarify who moderates if the thread goes sideways (edgy joke, nosy question): usually the manager or People replies briefly in DM or reframes in-thread.

Follow-up reminder example (copy-paste)

A reminder as a new channel message (not only a buried bump) usually outperforms three scattered pings.

"Quick reminder team: Claire's farewell guestbook closes today at 5pm. If you want to leave a note, use this link: [link]. Thanks everyone for contributing."

Short, polite, no pressure — this format usually performs best. If you want to avoid another channel-wide notification, reply in the original announcement thread with the same text and pin the thread — but only if your team actually reads threads.

In practice

A strong Slack/Teams farewell announcement is 5 to 7 lines, sets tone, and gives one clear action. Emotional quality then comes from team contributions — for lines to steal or refine, use touching farewell messages and card mistakes to avoid. If you follow with a party, onsite or remote, continue with the farewell party checklist or virtual farewell guide.

Create a guestbook in two minutes to pair with your announcement.

Read next

1. Farewells

   Warm goodbye lines that skip empty office clichés

   To go deeper on emotional lines without clichés.

2. Farewells

   Farewell card pitfalls: what to fix before day one

   To dodge tone or timing mistakes on the card.

3. Farewells

   Structured video send-off across time zones (2026)

   To run a remote party that matches the announcement.