Picture the email. It lands on a Monday morning. "Effective September 1st, all employees are expected in the office five days per week." Three sentences. Four at most. An HR contact at the bottom for questions. No context. No conversation. No reason.
The email went out at thousands of companies. The results were predictable.
The Numbers Are Brutal
Before we talk about leadership, let's talk about the data... because leaders love data until it tells them something uncomfortable.
Research from King's College London found only 42% of UK workers would comply with a full-time RTO mandate today. In early 2022, the number was 54%. It is going in the wrong direction.
58% of workers say they would either quit immediately or start searching for a new job if forced back full-time. Among mothers with young children, only 33% would comply at all.
Eight in ten companies pushing RTO policies acknowledged losing talent as a result. Companies with the strictest mandates experienced turnover 13% higher than those with flexible approaches. Some were twice as likely to report increased staff losses.
And yet the mandates kept coming.
What Were the Reasons?
This is the question nobody in senior leadership wanted to answer clearly. Ask someone why their company issued a five-day return-to-office policy in 2023 or 2024. Watch them search for words.
"Collaboration." "Culture." "Visibility." "The CEO thinks it's better."
None of those are reasons. They are assertions. There is a difference.
A reason explains the mechanism. It connects the action to the outcome. "We are going back five days because our onboarding data shows new hires take 40% longer to become productive when fully remote" is a reason. It is specific, falsifiable, and connected to something measurable.
"Culture" is not a reason. It is a word meaning nothing when deployed as justification for a mandate.
The Psychological Contract
Your employees signed up for a job under certain conditions. Many made life decisions... where to live, how many children to have, how to manage childcare, what commute was workable... based on arrangements in place at the time of hire.
When you issued an RTO mandate without a coherent reason, you broke something. Not a legal contract. Something harder to rebuild: trust.
People Management notes employees "will make sense of the call to action by first and foremost asking themselves 'what's in it for me?'" When the answer is nothing... when the mandate costs two extra hours of commuting per day, more childcare bills, less flexibility... employees do one of two things. They leave. Or they stay and switch off.
Neither is good for you.
The Real Why Behind Most RTO Mandates
I am going to say something most corporate communications departments would never put in writing: a significant number of RTO mandates were not about productivity, collaboration, or culture.
They were about managing headcount without severance.
A BambooHR study found 1 in 4 executives admitted RTO policies were in part designed to prompt voluntary resignations. You do not need to pay someone a severance package when they choose to leave.
If this was your strategy, at least be honest with yourself. Do not dress up a cost-reduction exercise in the language of culture and collaboration. Your people are not foolish. They sense the difference.
The ones who leave first in these situations are, almost always, your best people. They have options. They go. The ones without options stay, resentful, and you are left with exactly the workforce you deserve.
What Good Looks Like
Not every RTO mandate is cynical. Some companies have genuine, data-backed reasons to bring people back. Mentorship pipelines. Client relationships. Training programmes not suited to video calls. Early-career employee development. These are defensible.
But defensible requires defense. It requires leaders to do the work of explanation.
What does good look like in practice?
Show the data. If you believe remote work is hurting your business, show which metric. If you cannot point to a measurable indicator, your belief is not a business case.
Acknowledge the trade-off. Your employees are not children. They understand business needs exist. What they will not accept is being treated as though their lives are a footnote. A leader who says "I know this is a real cost for many of you, and here is why we are asking for it anyway" will get more compliance and more respect than one who issues a mandate and calls it final.
Listen before you decide. Some teams work brilliantly when remote. Some roles genuinely require presence. A blanket five-day policy not distinguishing between a client-facing sales rep and a developer shipping code alone is not a strategy. It is laziness.
Hold the line on the reason. If your reason is real, it will survive scrutiny. If it collapses under a few direct questions from your senior team, you do not have a reason. You have an opinion. Opinions do not justify restructuring people's lives.
On "Collaboration" Specifically
I want to address the most common word used to justify RTO policies, because it has become almost entirely devoid of meaning.
Collaboration is not a physical act. I have worked in open-plan offices where teams of twenty people sat three feet apart and never said anything meaningful to each other. I have also worked remotely with teams building trust faster than any office environment I have been part of.
Proximity is not collaboration. Collaboration is intentional, structured, and cultural. You are able to build it in an office. You are able to build it remotely. What you are not able to do is mandate it into existence by making people commute.
If your collaboration is broken, the office is not the fix. The fix is looking honestly at how your teams are structured, how information flows, and how your managers are facilitating... or not facilitating... genuine connection.
Bringing everyone in on Monday and calling it a collaboration win is not a strategy. It is a photo opportunity.
The Talent Problem You Created
According to data compiled by Archie, 25% of companies pushing RTO policies offered no additional support, no incentives, no acknowledgment of the cost to employees when implementing their mandates. They sent the email and waited.
Across those companies, turnover climbed. The best people left first. Hiring costs rose. Institutional knowledge walked out the door.
And then, in quarterly reviews, those same leaders talked about the talent shortage.
There is no talent shortage. There is a leadership shortage. Specifically, a shortage of leaders willing to explain their decisions honestly and then live with the consequences of bad ones.
Before You Send the Email
Before issuing an RTO mandate, answer these questions out loud to your senior team:
- What specific outcome are we expecting from this policy?
- Which metric will tell us in six months whether it worked?
- What is the cost to our employees, and how are we accounting for it?
- What is our plan if we lose 15% of our staff in the first three months?
If you cannot answer those questions clearly, you are not ready to issue the mandate. Write the rationale first. The email second.
Your employees will do a great deal for you. They will work hard, stay late when it matters, give you discretionary effort you never asked for and cannot mandate into existence. None of it happens when they believe you see them as units of output rather than people whose lives your decisions materially affect.
The return to office is not inherently wrong. Doing it without a reason is.