How to Announce a Layoff to Your Team

The individual conversations happen first. Every person losing their job hears it directly, in a call or a meeting, before anyone else on the team knows layoffs happened at all. That part is settled by the time you sit down to write to everyone else.

This message, the one to the people who stayed, is a different problem. They just watched colleagues disappear from the calendar and the group chat with no warning, and they are reading this note to figure out two things: whether it is safe to trust what you tell them next, and whether they are next. Get either of those wrong and you spend the following months managing an exodus of your best remaining people, who now have every reason to update their resumes on company time.

Tell People What Changed For Them, Not For The Company

The instinct is to open with strategy: market conditions, the roadmap, the reasons this was necessary. Save it for the third paragraph. The first thing a reader needs is what is different starting today: who is gone, whether their own role is affected, and whether more cuts are coming.

Before:

Team, as part of our ongoing efforts to optimize our organizational structure and position the company for long-term success, we have made the difficult decision to eliminate several positions. We are grateful for the contributions of all affected team members and wish them well in their future endeavors. We remain confident in our strategy and excited about what lies ahead.

After:

Team, six people on the design and support teams were let go this morning: Priya, Tom, Marcus, Elena, Josh, and Dana. Each of them spoke with their manager and with HR before this note went out, and today is their last day.

No one else on the team is affected, and we do not have further cuts planned for the rest of this quarter. Their open work is being reassigned this week; you will hear from your manager about what specifically lands on you.

I know this is unsettling regardless of whether your own job is safe. I will explain why we made this decision below, and I am holding an open session tomorrow at 10:00 for any question you want to ask directly.

The second version names the people, states the scope, and answers the safety question in the first two sentences. The first version could describe almost any layoff at any company and answers nothing.

Say Whether More Cuts Are Coming, Even If The Answer Is Uncertain

“No further cuts are planned this quarter” is a sentence people will hold you to, so only write it if it is true. If you genuinely do not know, say that instead of staying silent on the question. Silence reads as confirmation that more is coming, and it is the fastest way to trigger voluntary departures among people you cannot afford to lose.

The honest version costs you nothing to keep: “I cannot promise there will be no further changes this year, but nothing further is planned right now, and I will tell you the moment that changes.”

Cut The Language That Makes People Distrust Everything Else You Write

Right-sizing, restructuring for future growth, difficult but necessary decision, and streamlining the organization are all phrases that a reader has seen used to describe layoffs before, and every one of them signals that the writer would rather not say the plain thing. Once a reader catches one euphemism, they start reading the rest of the message for what else is being softened.

Say what happened in one sentence, using the words layoff or position eliminated rather than a synonym for it. Then explain the reasoning in plain terms: a specific budget target, a product line closing, a client contract ending. A vague appeal to “market conditions” without a specific cause reads as a decision nobody wants to own.

Where legal or contractual obligations apply to the notice itself, such as advance notice periods for larger layoffs under regulations like the United States’ WARN Act, confirm the specific requirements with HR or legal counsel rather than guessing at what the message needs to include. Requirements vary by jurisdiction, headcount, and the size of the layoff, and getting the notice period wrong is a separate problem from getting the tone wrong.

What Happens In The Days After

Be available, not just on the day of the announcement but for the following week. People will want to ask questions they were not ready to ask in the room, and a manager who sends the message and disappears into a full calendar confirms every suspicion that the announcement was a formality rather than a real conversation.

Follow up in writing once the redistributed workload has actually settled. A second message a week later, stating plainly what changed about people’s day-to-day responsibilities, is the one most leaders skip and the one that actually determines whether the team stabilizes or keeps quietly job hunting. The same principle applies to any team change announcement: the first message states the change, and the second message is what proves you meant it.

A Wrivio Context for this could say:

Rewrite this as a layoff announcement to the remaining team. Plain, direct language, no euphemisms for job loss such as right-sizing or restructuring. State who was affected, the scope of the layoff, and whether further cuts are planned in the first three sentences. Calm and factual tone, not upbeat or reassuring beyond what is actually true. Keep every name, date, headcount, and commitment exactly as written and do not add reassurances about job security that are not already in the draft.

Press Ctrl+Shift+Space, paste the draft, and check the diff line by line. On a message like this, an added reassurance you did not intend to make is a far worse outcome than an awkward sentence.

Not every departure is a layoff. If someone is leaving on their own terms, the tone and the content are different; see how to write a farewell email when leaving a job for that situation instead.

Common Questions

Should the layoff announcement come from HR or from the manager?

From the most senior leader the team actually works under, not from HR. An HR-branded message reads as a process notification rather than a leader taking responsibility for a hard decision.

How much detail should I give about why specific people were chosen?

None, in the group message. Explain the overall criteria used for the decision, such as role elimination or a specific team being closed, but never discuss an individual’s selection in front of the wider group. That conversation, if it happens at all, belongs in a private follow-up with someone who asks.

Is it wrong to mention severance or support being offered to the people who left?

Briefly, yes, mention it. A short line confirming that departing colleagues are receiving severance and transition support tells the remaining team that people are being treated fairly, which matters directly to how safe they feel staying.

How long after the individual conversations should the team message go out?

The same day, ideally within an hour or two. A gap of even a day between the individual departures and the team learning why creates a window for rumor that is worse than any imperfection in the message itself.

Download Wrivio for Windows to get the tone right on the hardest message a team ever reads from you.