Explain offshoring to your team, with real scripts
You have to tell your team some roles are moving to another country. Here’s exactly what to say, how to explain the why without spin, and how to answer transfers, timelines, and “why us, not them.”
How do you open the conversation?
Keep it plain and specific. Don’t tease it. Say the headline, the impact, and what happens next.
Say this:
“Thanks for joining at short notice. I need to share hard news. The company is moving [function/work] for [product/region] to our [country/city] site. That means some roles here will change or end over the next [timeframe]. I’ll explain why, what I know, what I don’t, and how we’ll support people. I’m here for questions right now and after.”
What do you actually say?
Your job is to be clear, human, and steady. Three parts: why, what it means, and support.
Say this:
“The decision was made at [level]. The reasons given are cost, time zone coverage, and access to local customers and talent. I know that lands as ‘cheaper elsewhere.’ It’s also about proximity to growth. I won’t spin it.”
“Here’s what it means: [X] roles in [teams] are in scope. The current plan is [transfer work by date]. Impacted folks will hear 1:1 this week. Roles not in scope: [list]. If your role is unclear, I’ll tell you by [date].”
How do you explain the business case without sounding cold?
Name the factors and the tradeoffs. Acknowledge the human cost.
Say this:
“Yes, labor costs and incentives matter. So do time zones and being closer to [customers/suppliers]. Those are the drivers leadership cited. The tradeoff is losing experience here, disrupting lives, and risking execution. That’s real, and we’ll try to reduce that harm.”
If someone says, “This is just offshoring for profit,” reply: “Profit is part of it. So is positioning where the company is growing. You deserve the straight answer, not spin.”
How do you handle ‘why us and not them’?
You’ll hear comparisons to other sites or expansions elsewhere. Address it directly, once, then refocus on what you control.
Say this:
“I’ve seen the headlines about companies growing in one place while cutting in another. Our specific call is about [function/scope]. Other sites have different costs, incentives, and customer proximity. I can explain the criteria used here; I can’t speak for other orgs’ choices. What I can do is fight for fair process and support.”
What if someone asks to relocate or transfer?
Have a clear path for yes, maybe, and no.
Say this:
“If you want to pursue a role at the destination site, here’s the process: internal application opens [date], we will fast-track impacted employees, and we’ll share relocation/visa details by [date].”
“If you want to move but can’t for family or visa reasons, I get it. We’ll prioritize internal transfers locally as roles open.”
How do you talk timelines, packages, and fairness?
Specifics reduce panic. Don’t guess. Where rules vary, say so and point to the source.
Say this:
“Timeline: knowledge transfer starts [date] and ends [date]. Impacted employees will have [notice period] plus [severance/benefits continuation/outplacement]. Details are in the FAQ I’ll send and in HR’s portal. If you have a unique situation, talk to me or HR 1:1.”
“Selection: roles are in scope based on [clear criteria: product line, shift, customer region]. We are not using performance ratings as a proxy here.” Check with HR or an employment lawyer if your jurisdiction requires a different process.
A script you can adapt
Before you walk in
- Align with HR on what’s decided vs. what’s still a proposal.
- Write the plain-English headline: what moves, where, when, who’s in scope.
- Get exact timelines, selection criteria, and support details you can say out loud.
- Prepare a one-pager: in-scope/out-of-scope, dates, FAQs, contacts.
- List internal and destination-site openings; confirm transfer and relocation policy.
- Decide what you’ll say if you personally disagree, without undermining clarity.
Rehearse it before you say it
If you have to explain offshoring soon, practise it out loud with Rehearse so you can land it clearly and with care—and get feedback before the room does. 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.
Questions people ask
Should I tell the team before everything is finalized?
Tell them once the direction is decided and timing is likely, not while it’s speculative. Early enough to be honest and useful, late enough that your facts are solid. If you must brief during consultation periods, label what’s draft and what’s locked.
How specific should I be about cost differences and incentives?
Be specific about the factors (labor cost, time zone, customer proximity, incentives). Avoid throwing out numbers you can’t defend. Tie reasons to how work gets done; don’t reduce people to a spreadsheet.
Do I need to explain taxes or government incentives?
Only if they materially drove the decision and you have accurate details. Keep it short and connect it to operations. If you’re unsure, say you’ll confirm and follow up rather than guess.
What if someone gets angry in the meeting?
Acknowledge the emotion without escalating. Pause, reflect back what you heard, and offer a 1:1. “I hear you’re angry and worried—fair. I’ll stay after this to talk.” Don’t argue motives in the room; return to facts and support.
How do I handle media or social posts by team members?
Don’t police people, but remind them of policy and personal risk. Offer a safe internal forum for questions. If press contacts you, route to Comms. Focus your time on direct support and clarity.