Write a farewell message to my coworkers using the details below. Audience and channel: [AUDIENCE AND CHANNEL] My role and final date: [ROLE AND FINAL DATE] What I am comfortable sharing about the change: [CHANGE DETAILS] People, projects, or moments to acknowledge: [SPECIFIC THANKS]
Tone and contact or handoff request: [TONE AND ASK]
Write one message of 140 to 220 words. Open with the final date and a direct, calm statement that I am leaving or moving on. Give two or three specific acknowledgments drawn from my notes: name a project, shared challenge, team practice, or support received, rather than praising everyone in generic terms. Keep the focus on the coworkers and work, not on a long explanation of my next job or departure circumstances.
Include a practical closing if relevant: how remaining work will be handed off, whom to contact, or how colleagues can stay in touch. If I provide contact details, include them exactly; do not invent a LinkedIn profile, email address, personal reason for leaving, or future plan. Avoid promises such as “keep in touch” unless the message gives a concrete way to do so.
Return three versions: a standard team email, a shorter Slack or Teams post of 60 to 90 words, and a manager-appropriate version if the audience includes direct reports. Label any detail that might be too personal for a broad company channel.
Before answering, check that every named person and claim comes from my notes, and that the tone matches the stated audience. Ask up to 3 clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [AUDIENCE AND CHANNEL] | State who will receive the message and whether it is an email, Slack post, Teams message, or another channel. | Email to the 18-person Product Operations team, with a short Slack version |
| [ROLE AND FINAL DATE] | Enter your role, team, and last working day or transition date. | Product Operations Manager; last day is Friday, October 9 |
| [CHANGE DETAILS] | Say what you are willing to disclose about why or where you are going, if anything. | I am taking time before my next role and do not want to discuss details publicly. |
| [SPECIFIC THANKS] | List colleagues, projects, achievements, or moments you want to recognize accurately. | Thank Priya for partnering on the release calendar; thank the support team for candid feedback; mention the Q2 incident review process we rebuilt together. |
| [TONE AND ASK] | Describe the desired tone and any handoff, contact, or networking request to include. | Warm and professional; direct urgent launch questions to Marco; include my personal email [email protected] for staying in touch. |
How to use
- Decide in advance what you want to say about your next step; “I’m moving on” is enough when details are private.
- Give the AI a few real memories or contributions so the gratitude does not become a list of empty compliments.
- Check handoff details, names, dates, and contact information against the final transition plan before sending.
- Follow up with: “Make the email 120 words, remove the personal contact, and keep the acknowledgment of the incident-review work.”
Variations
Direct reports note
Use this when you are a manager saying goodbye to your own team.
Write a 160-word farewell message to my direct reports. My final date and role are [ROLE AND DATE]. The team’s recent work and achievements are [TEAM WORK]. The transition owner and immediate next steps are [HANDOFF]. Use a steady, appreciative tone that acknowledges the team’s work without making promises about future decisions. Include a clear operational contact for questions. Do not invent personal reasons for my departure or praise individuals beyond the details supplied. Ask up to 3 clarifying questions only if necessary.
Client farewell
Use this when you are leaving an external client relationship.
Draft a concise client transition email for [CLIENT NAME]. My last day is [FINAL DATE], and [SUCCESSOR NAME AND ROLE] will take over. Mention these completed or active items: [ACCOUNT DETAILS]. Keep the message professional, reassure the client only with confirmed facts, and give a specific handoff action such as a meeting or introduction. Do not disclose internal personnel matters or promise service levels not approved by the company. Ask up to 3 clarifying questions only if a required input is missing.
Contract end note
Use this when a contract or temporary assignment is ending.
Write a 100-word farewell note for the end of my [CONTRACT TYPE] with [TEAM OR COMPANY] on [END DATE]. Thank colleagues for these specific collaborations: [PROJECTS OR PEOPLE]. State the approved handoff contact or repository: [HANDOFF]. The channel is [CHANNEL], and the tone is [TONE]. Do not imply I am an employee, add future work plans, or invent contact information. Ask up to 3 clarifying questions only if needed.
Tips
- State the last day near the beginning so coworkers know when the transition actually happens.
- One concrete acknowledgment, such as a difficult launch or a process the team improved, is more meaningful than a long list of adjectives.
- For a broad message, do not explain a departure that involves private employment, health, performance, or compensation matters.
- If there is unfinished work, name the next owner and location of the handoff; a farewell note should not leave operational ambiguity.
FAQ
How long should a farewell email to coworkers be?
About 140 to 220 words is usually enough for a team email. A Slack or Teams note can be shorter if handoff information is already documented elsewhere.
Should I say where I am going next?
Only if you want to and it is confirmed. You can simply say that you are moving on or taking time before your next step.
Can I thank individual coworkers by name?
Yes, when the examples are genuine and the list will not unintentionally exclude key people. For a large audience, thank a group or mention a shared project instead.