6 Farewell Email Mistakes to Avoid on Your Last Day
Here's the short answer: most farewell email mistakes come down to six things — sending it Friday afternoon, writing four hundred words when a hundred and fifty will do, naming the next employer, treating the group email as the whole goodbye, closing with "I'll keep in touch," and picking the wrong recipient list. The fixes are small. The difference is not.
Everyone tells you to send one. Nobody tells you what makes yours land.
What follows is the actual list of things that go wrong when a smart person writes a farewell email in a hurry — and the small edits that turn each one around. If you have thirty minutes and a draft open in another tab, this is worth reading before you hit send.
Mistake 1: Sending it late Friday afternoon
The most common timing mistake. You finish handover, close a few tabs, and hit send at 4:47 pm on your last day. Half the people you wanted to hear from are already in weekend mode. Nobody replies. The silence stings on Monday, when you're not there to feel it in context.
Fix: send mid-morning the day before your last day, or by 10:30 on the last day itself. That window catches people while their inboxes are open and gives them a real chance to reply, forward, or walk over. If your last day is a Friday, mid-morning Thursday is better than any time Friday.
Mistake 2: Writing four hundred words when a hundred and fifty will do
The urge to summarize your entire tenure is strong. Resist it. Long farewell emails read as performance. Short ones read as sincere.
A good group farewell email covers five things, in this order: your last working day, who's covering what you did, one specific thank-you that names something real, your personal contact info, and a warm forward-looking line. That's a hundred and fifty to two hundred words. Two or three short paragraphs. Nothing else.
Fix: if you can't cut it under two hundred words, the extra weight belongs in a personal note to one or two people, not in the group email. There are plenty of solid farewell email templates for coworkers that show the shape.
Mistake 3: Naming your next employer
You don't owe anyone the next company's name in the group email. Naming it invites politics you're about to leave behind: comparisons, competitive tension, the odd LinkedIn message from a recruiter at a rival firm you didn't want. If your next employer is a direct competitor, naming them can also complicate your handover in the last two weeks.
Fix: leave the destination out, or share the shape without the name. "Moving to a small climate-tech startup" or "starting at a healthcare company in Boston" is plenty. If people want the name, they can ask you directly, and you can decide case by case.
The same rule applies to subject lines. Skip the "Onward and Upward" humblebrag — a plain "Last day tomorrow" is stronger. If subject lines are where you're getting stuck, look at farewell email subject lines that actually get opened.
Mistake 4: Treating the group email as the whole goodbye
This is the mistake with the longest tail. The group email catches the network. It does not catch the five to fifteen people who actually shaped your time there. When those people only hear from you through a mass email, the message they get is: I did not remember you specifically.
You will hear from some of them right after. Nice replies. But there is a quieter set — the senior peer who unblocked something for you in year one, the analyst you mentored for six months, the cross-functional partner who defended your project in a meeting you didn't see — who will not reply, and will notice. Personal notes go out before the group email hits.
Fix: spend an hour picking five to fifteen names. Write two-to-four-sentence personal notes to each. Send them the day before you send the group email, or in the morning window before the group email goes out. Most of these are email; the closest few can be a handwritten card or a short in-person conversation.
The hard part is picking the names. Memory over-weights the last two months and forgets the quiet contributors from last summer. The last twelve months of your work calendar is the only honest record of who you actually worked with — meetings you accepted, recurring 1:1s, projects that repeat someone's name — and it usually surfaces four or five people you would have missed otherwise.
That is the problem It Was Great Working With You was built for. Upload your Google or Outlook calendar export, and it returns a ranked list of the people who actually shaped your time at this job. It takes about three minutes. The rest of the farewell writes itself once you know who it's for.
Mistake 5: Closing with "I'll keep in touch" and nothing else
"I'll keep in touch" is the placeholder line every farewell email defaults to when the writer is tired. The reader knows. It reads as polite and empty. The people who hear it most are the ones who most wanted a specific line.
Fix: in personal notes, replace "I'll keep in touch" with one specific stay-in-touch line per person. Not a promise you can't keep — a concrete next thing. "Let's do coffee sometime in October." "I want to hear how the launch goes — email me in a few weeks." "I'll ping you when I'm back in Chicago in the fall." One dated, real, small commitment. If you can't think of one for a particular person, that's a signal: warm goodbye, no promise. Silence is better than a promise you'll break.
The group email is different. There, "wishing everyone well" or a plain "thanks for the years — my personal email is below" is fine. Group emails aren't the place to make individual commitments.
Mistake 6: The wrong recipient list
Two ends of the same mistake. Some people send the farewell email to the whole-company alias — eight thousand people who mostly didn't know them. Others send it only to their direct team of five and skip the cross-functional partners who were in half their meetings. Both leave you with regret in different flavors.
Fix: the group email goes to your team, your immediate stakeholders, and the recurring cross-functional partners you actually collaborated with. Not the whole-company alias. Not "everyone in the building." Somewhere between fifteen and eighty names, depending on your role.
If you're on a large distribution list where your team is a rounding error, use your team's alias plus a personal Bcc to the cross-functional people you want to reach. The Bcc keeps the reply-all count sane and lets each person feel personally addressed.
If you were laid off, the picture is different. The recipient list is often smaller, the tone is more careful, and the timing is tighter — what to say and what to skip in a layoff goodbye email covers those tradeoffs specifically.
What actually makes one land
Three things, in order of what matters most. First: the personal notes went out before the group email. Second: the group email is short, warm, specific about one thing, and includes your personal contact. Third: it landed in a window when people could read and reply.
That's the whole game. The five things in the body matter, but they matter less than these three. A generic group email that lands at 10:15 am on the day-before after fifteen personal notes have already gone out will do more for your relationships than a beautifully written email sent at 4:47 pm Friday to the wrong list.
A quick pre-send check
Before you hit send on the group email, run through this:
- Under two hundred words
- Last day and coverage named
- Personal email or LinkedIn in the body, not just the signature
- One specific thanks (a project, a team habit, a small ritual — something real)
- No next-employer name
- No "I'll keep in touch" as the only sign-off
- Sent between 9 and 11 am, ideally the day before your last
- Personal notes to the five-to-fifteen people already went out
If seven of those check, you're in good shape. If the last one hasn't happened yet, that's the one to fix. The group email is the easy part; the personal list is where the actual goodbye lives, and it's the part the calendar can help you build in the ninety minutes before you send.
Small edits. Real difference. Send the one you'd want to receive.
