How to tell someone their role is being transferred

You have to tell a report their current role is ending and they’re being moved to a different team, shift, or location. Here’s the exact language, structure, and pushback handling so you can deliver it clearly and with respect—no spin, no jargon.

What do you actually say?

Say the decision first, simply, then the why, the specifics, and the options. Here’s a compact version you can adapt today:

“I need to let you know your current role is ending, and we’re transferring you to [new team/shift/location] effective [date]. The reason is [one clear business reason]. Your base pay will [stay the same/change to X]; your title will [stay/change]. Here’s what the day-to-day looks like: [3 bullets of responsibilities].”

“You have two options: accept this transfer and we’ll support you with [training/stipend/schedule flexibility], or decline it and we’ll discuss [internal openings/severance/next steps per policy]. I’ll answer every question now, and I’ll follow up in writing by [date].”

Don’t bury the lead. Don’t make them fish for impacts on pay, title, or location. Say the decision first, then what it means for them, then their choices.

How do you explain the why without corporate fog?

You owe a reason. One. Not a paragraph stuffed with buzzwords.

Use this template: “We’re doing this because [constraint or goal] and we need [capability/coverage] in [place/time]. Moving this role is how we get there.”

Examples:

• “Customer demand has shifted to evenings. We need experienced coverage at night to hit SLAs.” • “We’re consolidating support into one hub to cut handoffs and response time.” • “The product line you support is winding down; the transfer puts your skills on the growth work.” If the decision came from above, you can say: “This decision was made at [level]. I’m responsible for delivering it well and supporting you through it.” You don’t need to defend every upstream choice. You do need to be specific about cause and effect.

How do you present options and timelines clearly?

People hear better when they have agency. Even limited agency.

Spell out exactly what “yes” and “no” mean, by when, and what happens in-between.

Say:

• “If you accept, the transfer date is [date]. We’ll schedule [training/shadowing] the week before. You’ll report to [manager].” • “If you decline, here are the paths: [apply for open roles by X date], [we explore a leave or part-time bridge], or [we move to separation under policy]. Please check with HR or an employment lawyer about your options.” • “Your decision deadline is [date/time]. If I don’t hear from you, we’ll treat it as [accept/decline] per policy.” Put it in writing the same day. Ambiguity breeds rumor and regret.

What do you say about pay, title, and location?

Hit these head-on, in plain English:

• Pay: “Your base stays at $X. Differential for nights is Y%. Overtime rules don’t change.” Or, “Base changes to $X because [band/market].”

• Title: “Your title remains [title]. Org name on the badge changes.” Or, “Title changes to [new title]. This is not a demotion; the level stays [level].”

• Location: “This role is in [site]. We offer [relocation stipend/commute support], and the expectation is on-site [days] starting [date].” If relocation is required, say that clearly and urge them to check details with HR or an employment lawyer for their situation.

How do you handle real pushback in the room?

Expect emotion. Don’t argue with feelings; answer the question under the question. Keep your voice calm, your sentences short, and write down open items you can’t answer on the spot. Examples below; a full script is at the end.

• “Why me?” → “We matched skills and coverage needs across the team. For you, it was [specific factor]. I know that still lands hard.”
• “This feels like a demotion.” → “Level stays [level], pay is [same/change]. Scope shifts to [X] because that’s where we need the experience.”
• “I can’t work nights.” → “I hear you. Options are [X, Y]. If none work, we can talk about internal openings or separation under policy.”
• “Who else is being moved?” → “I can share the structure: [team/functions]. I won’t share others’ situations.”
• “If I say no, do I lose severance?” → “Here’s what policy says today: [say what you know]. Please confirm details with HR.”
• “Is this permanent?” → “The assignment is planned for [duration]. If that changes, I’ll tell you fast.”

How should you structure the meeting?

Keep it under 20 minutes for the first pass; don’t trap them in a long talk while they process.

A simple arc works:

1) Decision and effective date. 2) One clear reason. 3) What changes for them (pay/title/location/schedule/reporting). 4) Options and deadlines. 5) Questions now; time for a second meeting in 24–72 hours. 6) Written summary same day.

Bring a printed one-pager with the specifics. When people are stressed, paper helps.

A script you can adapt

Before you walk in

• Get the exact decision in writing: destination team, level, title, pay, shift, location, effective date.
• Write one plain-English reason that links business need to their transfer. No buzzwords.
• List the non-negotiables and negotiables. Decide what you can flex on (start time, training, stipend).
• Pre-clear options and deadlines with HR. Confirm what happens if they decline. If relocation or policy questions arise, advise them to check with HR or an employment lawyer.
• Draft the one-pager you’ll hand them. Include contacts for HR and the new manager.
• Schedule a private room with enough time for questions—and a follow-up slot within 48 hours.

Rehearse it before you say it

Before you walk into this, rehearse the exact words and the pushbacks out loud with Rehearse so your delivery is clear, steady, and human. Rehearse gives you an AI partner who plays the other person — by voice or face-to-face — then coaches you on clarity, empathy and structure.

On your phone? Tap here →

Questions people ask