Celebrer › The Celebrer Journal

Workplace farewells

How to collect farewell messages from the team

The card goes round the office and comes back with twenty-three variations on “all the best”. It isn’t that nobody cares. It’s that we ask for it in a way that guarantees that answer.

Updated September 2026 · 16 minute read

Somebody resigns on a Tuesday. You find out on the Wednesday. Their last day is in seventeen working days, one of which is a public holiday, and you’ve just volunteered to “sort something out”.

That is the real shape of this job, and it’s why workplace farewells go wrong in ways birthdays don’t. A 70th you can see coming a year out. A leaving do you find out about three weeks before, from someone who heard it in the kitchen. And unlike a birthday, the person you’re hiding it from is sitting inside every single channel you’d normally use to organise it.

This guide covers the parts that actually decide whether you end up with something worth giving: why messages come out bland and how to fix it mechanically, who to ask that nobody thinks of, what to say when you ask, how the tone changes depending on why they’re leaving, and when to hand it over.

Why farewell messages come out bland

This is not a people problem. It’s a design problem, and once you see the mechanism you can’t unsee it.

Almost every default method collects in public. The card sits open on a desk. The email thread is reply-all. The Slack channel shows every previous message above the box you’re typing into. So the first person writes “All the best in the new role!” — safe, because they had nothing to calibrate against. The second person reads that and matches it. By the tenth contributor the register is set in concrete, and writing four warm sentences underneath nine one-liners would feel like showing off.

Nobody wants to be the one who wrote something too sincere directly above their manager’s signature.

There are three fixes, and they’re all mechanical rather than moral. You don’t need to persuade your colleagues to care more. You need to stop showing them each other’s answers.

• Collect privately. If nobody sees what anyone else wrote until the whole thing is assembled, there’s nothing to anchor to. People write what they actually think.
• Replace the blank box with a question. More on this below, but it is the single highest-leverage thing in this entire guide.
• Ask the most senior person last. If the head of department writes first, everyone underneath writes a shorter, safer version of whatever they said. If they write last, they write into a space other people have already made warm.

Who to ask — including the four groups everyone forgets

Most organisers work from the team list. The team list is an org chart, which is a picture of who reports to whom, not a picture of who mattered to this person.

People who already left the company. This is the big one. The best message in a collection often comes from the person who trained them in their first month, four years ago, and now works somewhere else entirely. They have perspective nobody currently employed has. They are also on precisely zero distribution lists, so you have to go and find them — LinkedIn, or simply ask the leaver’s closest work friend for three names.

People in other offices and other floors. A card physically visits the desks nearest to it. If your company is hybrid, multi-site, or just large, the card reaches the people who sat near the card, which is not the same set as the people who worked with them.

People they managed, not just their peers. “You were the first manager who told me it was fine not to know something” is the message they will still have in ten years. Junior people often assume their message doesn’t count and need to be asked directly rather than through a group.

The people outside the company. The agency contact they spoke to every Thursday for three years. The supplier rep. The client they’ve had since 2021. These relationships are often the most genuinely warm ones a person has at work, and they’re invisible to HR. Use your judgement about anything commercially sensitive, and ask through the relationship, not through a mailing list.

And one group to go carefully with: the colleague they didn’t get on with. Ask once, take a no, and don’t chase. A missing message is kinder than a visibly dutiful one.

The five ways teams collect farewell messages

If your whole team sits in one room and always has, buy a good card. The moment the list includes someone who left in 2023, or someone who works from Adelaide, the card stops being a way of collecting and starts being a way of excluding.

Ask a better question than “write something for Sarah”

Give someone a blank box and the word “farewell” and they will produce a farewell-shaped sentence. It isn’t laziness. It’s that “summarise this person” is a genuinely hard request, and under time pressure people fall back on the template.

Ask for one specific memory instead and the same person writes you something nobody could have predicted. Pick one of these and put it in the ask:

• What will the team not be able to do once they’ve gone?
• What did they teach you that you still use?
• What’s the story about them you’ll still be telling in five years?
• When did they get you out of a hole?
• What do they always say?
• What were they like on your first day?

Notice what they have in common: every one asks for an event, not an assessment. “What are they like?” produces adjectives. “When did they get you out of a hole?” produces a Thursday in March when the numbers didn’t reconcile and someone stayed until nine.

Two more things to put in the ask, because both failure modes are common enough to be worth naming:

Give a length. “Three or four sentences is perfect” gets you three or four sentences. Say nothing and you get one line, because people assume short is safer. The number does the work; it gives permission.

Warn off the performance review. “Always reliable, a real team player, will be missed” is the language of an exit interview, and it lands like one. If it could appear on a reference, it’s not a farewell message. The test: could this sentence have been written about anyone else in the building?

And the opposite failure — a wall of in-jokes that only six people understand. Worth one line in the ask, because a leaving keepsake almost always gets shown at home, and a message their partner can’t follow is a message that gets skipped.

What to actually send

Three versions, because the same wording doesn’t work for the team, for someone who left years ago, and for the chase.

Send the chase individually, not to the group. People who haven’t written aren’t refusing — they opened it on their phone in a meeting, meant to come back to it, and didn’t. A group reminder is easy to assume is aimed at someone else.

Example farewell messages you can adapt

These aren’t templates to fill in. They’re here to show the shape: one specific thing that happened, then what it meant. Read a couple, then write your own version of whatever they remind you of — the memory is the part that can’t be borrowed.

Worth sending two or three of these along with the ask. People who say they “aren’t good at this sort of thing” almost always mean they don’t know what one looks like.

Notice what none of them do: summarise the person. Not one says “hard-working”, “dedicated” or “a real asset to the team”. They each pick one Thursday and describe it, and the character comes out sideways. That’s the whole trick, and it’s why the question you ask matters more than the wording you suggest.

Say what kind of leaving this is

This is the part most advice skips entirely, and it’s the part that decides whether the whole thing feels right or makes everyone wince.

They’ve resigned for a better job. Straightforwardly celebratory. Jokes about how jammy they are land fine. Excitement about the new role is welcome.

They’ve been made redundant. “Good luck on your next adventure!” is tone-deaf and every person in the room knows it. Redirect the question away from the future entirely: ask people to write about the work they did and what they were like to work alongside. No speculation about what they’ll do next, no “everything happens for a reason”, no silver linings. The useful message here is evidence that the work mattered, which is precisely what redundancy makes a person doubt.

They’re retiring. Different register again — you’re marking a whole career rather than one job, and the guest list stretches back decades. That has enough in it to need its own guide, and it changes who you ask more than what you ask.

It’s the end of a contract or a secondment. Nobody organises anything, because it doesn’t register as a “real” leaving. Which makes it the one where fifteen messages land hardest, because the default is silence and they know it.

They’re leaving because of illness, or something difficult at home. Keep it entirely about the person and the work. Don’t reference the reason, don’t wish them a swift anything, and let them decide what’s public. Ask first whether they’d even like a send-off; some people would much rather leave quietly.

And if someone is leaving under a cloud, don’t run one. A collection of carefully neutral sentences is worse than nothing at all.

Keeping it from them is harder at work

At a birthday you’re hiding something from one person who isn’t looking. At work you’re hiding it from someone who is inside the same email system, the same chat platform and the same calendar — and whose final fortnight is unusually quiet, which means they have more attention spare than usual, not less.

• Don’t put it in the shared calendar, and don’t name a channel or a document after them.
• Say “this is a surprise” in the ask itself, in bold. The leak almost never comes from the organiser — it comes from the twenty-second contributor who genuinely didn’t realise and mentions it in the standup.
• Tell people not to reply-all, explicitly, every time. Someone will otherwise hit it out of habit.
• Use a channel the leaver isn’t in. Personal email, or a link shared by text, beats anything running on company infrastructure.

Worth asking yourself whether it needs to be a surprise at all. For a redundancy or a difficult departure, telling the person “we’re putting something together for you” can be the kindest part of the whole process — it gives them something to hold onto during a fortnight that is otherwise all handover documents.

Timing, and the chase

Work backwards from the leaving do, not from the last day — they’re often not the same, and the do is usually earlier in the week than you think.

• Day one: get the list. Ask the leaver’s closest work friend for the names you’d never think of, especially anyone who’s already left.
• Day two: send the ask, with a closing date two days before the do.
• Three days before closing: one chase, sent individually.
• Two days before the do: close it. Assemble. Check for anything that reads badly out of context.

Do not collect on the last day itself. The messages written that morning are visibly worse than the ones written the week before — half the team is already in the pub and the rest are typing with one hand while clearing a desk with the other. And you want a clear day to read everything before it’s handed over, because occasionally someone writes something that was funny in their head.

Expect about two-thirds of the people you ask to contribute. That is a normal, healthy rate and not a sign anybody disliked them. Twenty good messages beats forty dutiful ones, and inviting more people is a better lever than chasing the same people twice.

Handing it over — and why not at the drinks

Here’s the thing nobody warns you about. At their own leaving drinks, the person leaving does not get to read anything. They are being talked at from the moment they arrive. Hand them a book or a folder of messages at 7pm and they will say thank you, turn two pages while someone waits to hug them, and put it in their bag.

So separate the moment from the reading. Do the handover publicly — that part genuinely matters, and it’s the bit the rest of the team came for — but make the thing itself something they can take away and read alone.

The moment it actually lands is a few days later: the Sunday night before a new job starts, or the odd unmoored week in between, when somebody who has just been told they were replaceable reads forty people explaining that they weren’t. That is what you are making. Build it so it survives being carried home.

If you’re playing messages on a screen at the do, some arithmetic: twenty messages at roughly eight seconds each is under three minutes, which a room will hold comfortably. Double that and you’ll watch people start checking their phones. Show a selection on the night and let the keepsake carry all of them — the same principle applies whether you’re doing this for a colleague or for a milestone birthday.

One last thing: choose who speaks. The default is the most senior person in the room, and the default is usually wrong. Give it to whoever actually worked next to them.

Common questions

How many messages should we aim for?

Fifteen to twenty-five is plenty. Under ten starts to feel thin for a whole team; past about forty a playback gets long, though they all belong in the keepsake. Better to widen the invitation than to chase the same people a third time.

What if they’ve only been here six months?

Ask fewer people and ask a narrower question — “what was your first impression of them, and was it right?” works well for a short stint. Short tenures are also when people most doubt they made any impression at all, so the messages tend to matter more, not less.

Should the manager write one?

Yes, and last. If a manager writes first, everybody else writes a shorter, more careful version underneath. Ask them to write about one specific thing the person did, not about their performance — the shift from appraisal language to a real memory has to start at the top or nobody else will risk it.

Can we include people who’ve left the company?

Include them deliberately. They write the best messages in the collection and they’re on no list, so you have to go looking. Ask the leaver’s closest work friend for three names and work outwards from there. Use a method that doesn’t require a company login, or they simply can’t take part.

What if they’ve been made redundant?

Ask people to write about the work and about them, and say nothing about what comes next. No “exciting new chapter”, no silver linings. Redundancy makes people doubt that any of it counted; the entire value of the collection is forty pieces of evidence that it did.

How long should each message be?

Ask for three or four sentences. It reads as achievable rather than as an essay, and it’s long enough to force a specific memory rather than a stock phrase. People write to whatever number you give them, so give one.