AdvancedHRCEOFounder

RIF communication sequence: what to say, in what order, to whom — hour by hour

The 24 hours around a layoff are an operations problem, not a writing problem. A minute-by-minute comms sequence — managers first, affected next, surviving…

14 min read

On this page▾

T-minus 24 hours — manager prep
T-minus 2 hours — final lock
T-zero — the public moment
T+1 to T+4 — individual conversations
T+4 — all-hands for survivors
T+24 — external comms
The three scripts

60-Second Summary

The order matters more than the words. Managers brief 24h before, affected hear within 30 min of the public moment, survivors get a full meeting same day, external hears last.
Never let anyone find out from Slack, Twitter, or a customer. That's the failure mode the sequence exists to prevent.
Have three scripts ready: 'you are affected', 'you are not affected', 'you are a manager of affected reports'. All three rehearsed.
The 4 PM debrief on day 1 with the leadership team is the single most important meeting of the week — it shapes whether day 2-30 hold together.

Every RIF I've watched fail did the same thing wrong: they treated comms as a writing exercise instead of an operations sequence. The CEO email is fine; the order it lands in matters more. This is the hour-by-hour playbook — the one that prevents 'I found out from a customer' which is the only outcome that turns a hard day into a six-month culture wound.

T-minus 24 hours — manager prep

Closed-door briefing with every manager of an affected report. 90 min. They learn who, when, and the script.
Each manager gets a printed packet: list of their affected reports, severance terms, talking points, FAQ they're allowed to share, FAQ they must escalate.
Managers rehearse their 'you are affected' conversation with a peer manager. Out loud. No 'I'll just wing it.'
Confidentiality: explicit. Anyone who leaks early forfeits severance for the day's process and damages every conversation downstream.

T-minus 2 hours — final lock

Final list locked. No 'one more change' after this — every change creates a downstream leak risk.
IT prepared: account suspensions scheduled, not executed. Trigger is the end of the individual conversation, not the public moment.
Severance packets ready to send — email scheduled, not auto-fired. Manager triggers send after the conversation.
Building access, Slack DM access — handled at end of conversation, never before.

T-zero — the public moment

CEO email goes to all-staff. Single subject line: 'A difficult update on company changes today.' Three paragraphs: what (number of affected, departments at high level), why (one paragraph, no spin), what happens next (manager will reach out within the next hour to every person, all-hands at 4 PM, external comms tomorrow). No specific names. No FAQ. The FAQ comes at the all-hands.

T+1 to T+4 — individual conversations

The 30-minute rule

Every affected person must hear from their manager within 30 minutes of the CEO email. If your structure can't support that, your group is too large for one announcement — split the RIF into 2-3 windows over 2-3 days.

Conversations are 20-30 min. Manager + HR partner together for affected. Manager alone for unaffected (the 'you are safe, here's what changes for you' conversation matters almost as much).

T+4 — all-hands for survivors

CEO opens. Acknowledges the day. Restates the why. Does not minimize.
5-10 min: what changes operationally — reporting lines, priorities cut, what we're keeping.
FAQ — read out top questions submitted in last 2 hours, with honest answers including 'I don't know yet, here's when I will'.
Close with what the next 30 days look like: comms cadence, manager 1:1 expectations, when external comms goes out.
Total: 45-60 min, not more. Then small-team huddles for the next 90 min.

T+24 — external comms

External comms (customers, candidates, press if relevant) goes out 24 hours after internal. Never before. The order is: affected, survivors, external — in every case. Customers who find out before affected employees is the failure mode that destroys retention of the people you kept.

The three scripts

Script A — 'You are affected'

'I have hard news. As part of the company changes [CEO] just announced, your role is being eliminated. This decision is final. It's not a reflection of your performance — I want to be clear about that. I'm going to walk you through the package, the timeline, and the support available. Take whatever time you need, and ask whatever questions you have. Here's the packet.'

Script B — 'You are not affected'

'Your role is not affected by today's changes. I know that's a relief and also confusing on a day like today. Here's what changes for you: [reporting line, scope, priorities]. Here's what doesn't: [comp, role, level]. The all-hands is at 4. I want a 1:1 with you tomorrow to talk through anything that's sitting with you.'

Script C — 'You manage affected reports'

'Before today's announcement, I need to give you the list of your reports affected and the timing. We will talk to each of them in this hour. I will be in every conversation with you. Here are the talking points. Here's the packet. We rehearse once, now, and then we go.'

Written by Pawan Joshi.Sources cited inline.

First published 16 Jun 2026See site changelog →