Prepare a Manager to Discuss a Changed Work Location

A work location change lands differently than most announcements. It touches commutes, childcare, budgets, and a person's sense of control over their own life. When a manager delivers that news without confirmed details, the meeting turns into a guessing exercise, and every guess the manager makes becomes a promise someone remembers later. Your job as the HR business partner is to make sure the manager walks in with facts, not hopes.

Why This Conversation Goes Wrong

Most managers want to be helpful in the moment. An employee asks, "Will I still get a parking spot," and the manager, wanting to ease the tension, says, "I'm sure that will work out." That sentence has no basis. Nobody has approved it. Three weeks later, when parking is not available, the manager looks like they misled the team, even though they were only trying to be reassuring.

The second failure mode is the opposite problem. A manager who feels unprepared says almost nothing, reads a short announcement, and leaves the room fast. Employees fill the silence with speculation, and rumors move faster than any official update. Both failures come from the same root cause. The manager does not have a clear line between what is confirmed and what is still being worked out, so they either invent details or avoid the conversation entirely.

A location change also carries personal weight that a schedule change does not. Someone may have arranged childcare around a fully remote job. Someone else may have taken the job because of a specific commute. The manager cannot fix those situations in a team meeting, but they can make sure the facts they share are accurate and the path for individual concerns is clear.

How to Prepare the Manager

Start by building a two column document with the manager before they say a word to their team. Label one column confirmed and the other pending. In the confirmed column, list only what has been approved in writing, the effective date, which roles or locations are affected, any required in office days, and where employees send questions. In the pending column, list everything still under review, desk assignments, parking, equipment moves, whatever applies.

For every item in the pending column, ask the manager to write down two things, who owns that decision and when an update is expected. If the manager cannot answer either, cross out any language that implies a date or an outcome. This step matters because a manager who cannot name an owner will unconsciously default to a soft guess, and a soft guess sounds like a commitment to the person hearing it.

Next, prepare the manager for questions about individual circumstances. Some employees will not raise concerns in a group setting, and some will, expecting a private answer to be worked out publicly. The manager needs a standard line that routes those requests to the designated process without making the employee feel dismissed. This is also where a written summary matters. If the manager sends a short recap after the meeting, employees do not have to rely on memory or secondhand accounts of what was said.

What to Say

HR partner Priya sat down with manager Devon two days before his team meeting. Devon said, "I want to tell the team we are all moving to the downtown office next month, but I do not have every desk assignment yet." Priya asked, "What has actually been approved so far." Devon said, "The location, the October 15 start date, and three required days in the office each week."

Priya said, "Then lead with exactly that. Do not mention desks. Tell the team that workplace operations owns desk assignments and will confirm them before the move. Point any individual questions to the designated process instead of answering them yourself." Devon practiced the line out loud. "Starting October 15, our team will work from the downtown office Tuesday through Thursday. I will send arrival guidance today, and workplace operations will confirm desk assignments before the move. If you have a circumstance you want reviewed individually, use the link in that guidance."

An employee on Devon's team might ask, "What if the commute does not work for my schedule." Devon's prepared answer would be, "I understand that concern. I cannot make an exception in this meeting, but the designated process exists for exactly this kind of request, and I will make sure you have the link today." That answer does not solve the employee's problem, but it does not close the door either, and it does not put Devon in the position of deciding something he has no authority over.

Mistakes to Avoid

The most common mistake is softening a pending item into a promise. Words like probably, should be fine, or I would guess turn into commitments in an employee's memory, even when the manager did not mean them that way. The fix is mechanical, replace every soft prediction with an owner and a date, or leave it out entirely.

A second mistake is asking employees to explain private reasons for a request during a group meeting or a hallway conversation. If someone says they need an exception, the manager does not need to know why on the spot. The designated process exists so that sensitive details go to the right reviewer instead of becoming part of a public conversation.

A third mistake is treating the announcement as a one time event. A single meeting cannot answer every question that comes up over the following weeks. Build in a way for employees to ask follow up questions, and commit to a date for the next update, even if that update is only "still confirmed for October 15, no new information."

Finally, avoid letting the manager skip the written summary. A verbal announcement gets retold with small distortions by the end of the day. A short written recap, sent the same day, gives everyone the same source of truth.

How to Practice and Score This Conversation

Reading a script once is not the same as saying it under pressure, especially when an employee pushes back or gets emotional. Have the manager run through the exchange with a practice partner who plays a skeptical or upset employee, asking about parking, commute time, or exceptions the manager cannot grant. Score the run on three things, did the manager state only confirmed facts, did they name an owner and a timeline for anything still pending, and did they route individual requests to the right process instead of answering them on the spot.

DealSpeak gives you a way to run this rehearsal with an AI counterpart that pushes back the way a real employee might, then scores the manager on those same three points. It is one of the HR and Leadership practice conversations built for exactly this kind of announcement, where the stakes are real but the room is not.

If your manager already handles reflection conversations well, the same discipline applies. You can see a similar structure in how to Close a Coaching Engagement With a Realistic Reflection Planwhere clear ownership and dates replace vague promises. The same logic shows up in Close an Intake With an Upset Caller Who Understands the Next Stepwhere the goal is not to resolve everything in one conversation but to give the other person a clear next step.

Closing Thoughts

A location change announcement succeeds when the manager says only what is true and points everything else to a name and a date. Prepare the two column document, rehearse the delivery, and send the written recap. Do that consistently, and the team trusts the next announcement too, even before they hear the details.