๐Ÿ“‹ Free HR Resource ยท No Email Required

Layoff Notification Checklist: How to Notify Employees of a Layoff

A practical, step-by-step guide for HR and people-ops teams handling a layoff or reduction in force โ€” before, during, and after the notification conversation.

~10 minute read ยท Last reviewed August 2026

This is general best-practice guidance, not legal advice. Notice periods, mass-layoff thresholds, final pay timing, and benefits continuation rules vary by country, state, and company size, and change over time. Confirm every legal requirement with your employment counsel before finalizing your process.

Start Here: What Kind of Layoff Are You Running?

The core process below applies whether you're letting go of one person or fifty, but scale changes what else is required. A single-role elimination is mostly an HR and management conversation. A larger reduction affecting many employees within a short window can trigger additional advance-notice and consultation obligations in many jurisdictions โ€” mass-layoff notice laws in parts of the US, collective redundancy consultation requirements in the EU and UK, and similar rules elsewhere. The exact thresholds and timelines differ by location and change over time, so treat "how many people, how fast, where" as the first question you take to legal counsel, before you build your timeline around this checklist.

Planning Checklist (2โ€“4 Weeks Before)

Everything on this list should be settled before a single manager or employee is told anything.

  1. 1

    Get legal sign-off on the list and process

    Before anything else is scheduled, have employment counsel review the affected roles, the selection method, and any notice obligations that apply in your jurisdiction. This is the one step that's genuinely not optional -- everything else on this page is best practice, this one is risk management.

  2. 2

    Finalize the list and freeze it

    Get final leadership sign-off on exactly who is affected before you tell a single manager. Lists that change after managers have been briefed are how leaks, confusion, and inconsistent messaging happen.

  3. 3

    Document your selection criteria

    Write down, in advance, why these roles and not others (role elimination, restructuring, performance, tenure, business need). Keep that documentation on file. You may never need it -- but if a decision is ever questioned, 'we decided in the room' is a much weaker position than a dated rationale.

  4. 4

    Calculate final pay, severance, and benefits for every individual

    Have exact numbers ready before the notification meeting, not 'we'll follow up.' Final paycheck timing, PTO payout, severance formula, and benefits continuation rules vary by state and country -- confirm each with payroll/legal rather than assuming last year's numbers still apply.

  5. 5

    Decide the notification method

    Live conversation -- video call or in person -- for every affected employee, every time. Never a mass email, a group Slack message, or a surprise all-hands as the way someone learns they no longer have a job.

  6. 6

    Build a day-of runbook with exact sequencing

    Write down the order of who gets told what, and when: leadership, then managers, then affected employees individually, then the rest of the company. A runbook removes the need for anyone to improvise sequencing under pressure.

  7. 7

    Decide exactly when system access is revoked

    Agree on the moment -- typically at or immediately after the notification meeting, not hours before (which tips off the employee before they've been told) and not left open-ended for days after (which creates security and equity concerns).

  8. 8

    Line up outplacement or transition support to offer in the meeting

    Have something concrete to hand the employee beyond a goodbye -- severance details, benefits information, and a resource for what comes next. Arriving at this step with nothing prepared is one of the most common and most avoidable gaps.

  9. 9

    Prepare managers with real talking points, not just a heads-up

    Give every manager delivering the news a written script or set of talking points, and run through it with them beforehand. A manager hearing about the layoff for the first time an hour before they have to deliver it will improvise, and improvisation under emotional pressure goes badly more often than it goes well.

  10. 10

    Draft the internal message for the rest of the company

    Prepare what you'll tell the remaining team before the day arrives, not after. They will notice within minutes, and silence gets filled with speculation.

  11. 11

    Prepare external/public communications only if relevant

    If the layoff is large enough to be newsworthy, affects public-facing roles, or is likely to surface on Glassdoor, LinkedIn, or local press, have a short, honest holding statement ready. Most layoffs do not need this step -- do not build a press strategy for a five-person reduction.

Day-Of Notification: Sequencing Checklist

Order matters here as much as content โ€” get the sequence wrong and even a well-planned layoff feels chaotic to the people living through it.

  1. 1

    Brief leadership the morning of

    A short, final confirmation that the plan, numbers, and list have not changed since the last review.

  2. 2

    Brief managers shortly before, not days before

    One to two hours ahead is usually enough to prepare a manager without creating a long window for the news to leak. Give them the exact list, the exact language, and the answer to the questions they will be asked.

  3. 3

    Notify affected employees first, individually, before any group message

    Nobody should learn they've been laid off from a companywide announcement, a colleague, or a system that suddenly stops working. Every affected person hears it directly, from a person, before anything else goes out.

  4. 4

    Keep each conversation short, direct, and compassionate

    Ten to fifteen minutes is usually enough. Lead with the decision in the first sentence -- do not bury it under five minutes of preamble. State the business reason briefly. This is not the moment to negotiate, debate the decision, or promise things you are not authorized to promise.

  5. 5

    Have HR present alongside the manager where possible

    A second person in the room (or on the call) both supports the manager and ensures the employee gets accurate, consistent answers on pay, benefits, and next steps in the moment, not "someone will follow up."

  6. 6

    Give the employee something in writing before the meeting ends

    A summary letter covering last day of employment, final pay date, severance (if any), benefits continuation, and who to contact with questions. Verbal-only notification leaves people re-explaining the situation to their own family from memory.

  7. 7

    Revoke access at the agreed moment -- not before, not late

    Coordinate with IT so access changes happen at the point you decided during planning, consistently across everyone affected. Doing it early (before they know) or inconsistently (some people keep access for days) both create real problems.

  8. 8

    Send the internal announcement once every affected person has been told

    Only after every 1:1 notification is complete -- never before, and never so long after that the remaining team hears it secondhand first.

What to Say โ€” and What to Avoid

Do

โœ“State the decision in the first sentence: "I have to share some difficult news -- your position is being eliminated as part of [reason], effective [date]."
โœ“Give the real business reason in one or two sentences, without over-explaining or sounding defensive.
โœ“Acknowledge that this is hard news, once, sincerely -- and then move to practical information.
โœ“Walk through severance, final pay, benefits, and next steps clearly, using the written summary as the anchor.
โœ“Tell them what support is available (severance, extended benefits, outplacement resources) and how to access it.

Avoid

โˆ’Vague euphemisms as the only explanation ("we're going in a different direction") with no concrete reason offered.
โˆ’Making it personal or implying it's about their effort, unless performance genuinely is the documented reason.
โˆ’Promising specific outcomes you cannot guarantee -- a strong reference, a rehire, a "we'll bring you back soon."
โˆ’Negotiating severance or reversing the decision in the room. If there's genuine flexibility, that's a follow-up conversation, not an in-the-moment concession.
โˆ’Debating the business rationale live. The meeting is for delivering the decision and the practical next steps, not re-litigating it.

Immediately After: What Departing Employees Need

The notification meeting is the beginning of the process, not the end of it. What happens in the days after shapes how the whole experience is remembered.

  1. 1

    Confirm final pay timing in writing

    Final paycheck deadlines vary by state and country, sometimes significantly. Put the exact date in the written summary and confirm it matches what payroll/legal actually requires.

  2. 2

    Put severance terms in writing, with a clear response deadline

    If severance is contingent on signing an agreement (e.g. a release of claims), state the deadline and who to contact with questions, and route the agreement through counsel before it goes out.

  3. 3

    Explain benefits continuation clearly

    Employees need to know exactly when coverage ends and what their continuation options are (in the US, this typically involves COBRA-style continuation; requirements differ elsewhere). Don't assume they already know -- most people don't until they need to.

  4. 4

    Make equipment return simple, not punitive

    A clear, low-friction process (prepaid shipping label, drop-off window) for returning laptops and badges. Treating this like a security incident when it isn't one damages goodwill for no real benefit.

  5. 5

    Decide your reference policy before you need it -- and apply it consistently

    Whatever you decide (dates-and-title-only, manager discretion, HR-mediated), apply the same policy to everyone affected. Inconsistency here is one of the more common sources of ill will and complaints after the fact.

  6. 6

    Offer real transition support, not just a goodbye

    This is the step that gets skipped most often, usually because nobody prepared it in advance. Employees who leave with a concrete next step -- an updated resume, a plan for the first weeks of a job search, some structure -- tend to land faster and speak far more neutrally about the company afterward than employees who leave with a box of desk items and no direction. It doesn't have to mean an expensive traditional outplacement contract to be worth doing.

Handling a layoff right now and need transition support in place fast?

Rezycle.me provides instant, per-employee AI outplacement โ€” resume rewriting, ATS optimization, and a 6-week transition plan โ€” that HR teams can deploy the same day, without a weeks-long agency intake process.

See Enterprise Outplacement Pricing โ†’

Ready to actually compare vendors? See the outplacement provider evaluation checklist.

Supporting the Team That Stays

A layoff doesn't end when the affected employees leave the building โ€” it continues in how the remaining team experiences the weeks after.

  • โœ“Send the internal announcement promptly once everyone affected has been told -- silence gets filled with speculation, and speculation is usually worse than the truth.
  • โœ“Be honest about what happened and what happens next, within the limits of confidentiality. "We can't share details on individuals, but here's what changes for the team" is fair; saying nothing at all is not.
  • โœ“Redistribute workload deliberately, not by default. An unplanned pile-up on remaining staff is one of the fastest ways to trigger a second wave of voluntary departures.
  • โœ“Watch for disengagement and burnout in the weeks after, not just the day of. Survivor guilt and anxiety about 'who's next' tend to show up gradually.
  • โœ“Give managers explicit permission and time to check in with their teams -- this is not a distraction from the day job right now, it is the day job.

Common Mistakes That Make a Layoff Worse

Most layoffs that become a public relations or morale problem don't fail on the decision itself โ€” they fail on the execution below.

  • โˆ’Notifying people over a mass email, a group video call, or a system that just stops working, instead of an individual conversation.
  • โˆ’Cutting off system access before the employee has actually been told, so they find out from a locked laptop instead of a person.
  • โˆ’Changing severance terms after employees start comparing notes with each other -- inconsistency is discovered fast and damages trust for everyone, not just the person who got the worse deal.
  • โˆ’Skipping documentation of the selection rationale, leaving nothing on record if a decision is ever questioned later.
  • โˆ’Letting the news leak before every affected person has been told individually, because managers were briefed too early or the list wasn't kept tight.
  • โˆ’Having no single person or channel prepared to answer follow-up questions, so departing employees are left chasing answers for days.
  • โˆ’Ignoring the team that stays, and assuming morale will sort itself out without any direct communication.
  • โˆ’Scheduling the notification right before a holiday or major personal date without a real operational reason to do so.
  • โˆ’Letting managers freelance their own version of the message instead of using shared talking points, so different employees hear inconsistent explanations for the same layoff.

Quick Answers

What day of the week should we schedule layoffs?

There's no universally 'correct' day, despite strong opinions on both sides. Early in the week gives people access to HR, benefits contacts, and support resources before a weekend; late in the week can reduce the immediate disruption to team operations. Pick based on your team's actual support availability, not superstition -- and avoid scheduling around a holiday or major personal date without a real operational reason.

Should layoffs be delivered one-on-one or in a group?

One-on-one, individually, essentially always. Group notifications save time but strip away the ability to answer someone's specific questions, and they make an already hard moment feel impersonal. Group settings are appropriate for the follow-up announcement to the rest of the company -- not for telling someone their job is gone.

Do we legally have to give advance notice before a layoff?

It depends heavily on where you operate, how many employees are affected, and over what time window -- larger or mass layoffs often trigger advance-notice requirements (for example, WARN Act-style obligations in parts of the US, or collective redundancy consultation requirements in the EU and UK) that smaller reductions may not. These rules vary by jurisdiction and change over time, so this is exactly the kind of question to confirm with employment counsel before finalizing your timeline, not something to infer from a checklist.

What should we offer beyond severance?

At minimum: clear written terms, accurate benefits information, a consistent reference policy, and a simple equipment-return process. Beyond that minimum, some kind of transition or career support -- even a lightweight one -- measurably improves how people land and how they talk about the experience afterward, which is worth factoring into the plan rather than treating as optional polish.

Want more HR resources like this one? Optional โ€” the checklist above is free either way.