By mid-2025, the return-to-office trend has crystallized into something you can measure clearly. Fifty-four percent of Fortune 100 companies now require five days a week in the office, up from approximately five percent two years earlier. The mandate is real, it’s widespread, and it’s being enforced with varying degrees of seriousness across different companies. But here’s where the story gets interesting, and where most IT workers misread the situation.

The companies that mandated full-time office presence are seeing actual office attendance increase by only one to three percent from the hybrid baseline. In other words, when you account for sick days, vacation, and flexibility that supervisors still grant despite official mandates, office occupancy barely moved. Simultaneously, eighty percent of companies that instituted RTO mandates reported losing talent, with high performers departing at rates sixteen percent higher than low performers. The group most likely to leave when an RTO mandate is introduced is exactly the group every company wants to keep.

Understanding what this data actually means requires moving past the headlines and into what’s driving both the mandate and the exodus. Your career decision about where to work, whether to comply with an RTO demand, or whether to negotiate around it should be based on reading these signals clearly.

Why Companies Are Mandating Return-to-Office

The stated reasons for RTO mandates are usually some variation of: culture, mentorship, collaboration, spontaneous innovation. These are the reasons you hear in company-wide announcements and news articles. The actual reasons are more varied, and understanding the real motivation behind a particular company’s RTO mandate tells you something important about whether it’s genuine or performative.

Some companies genuinely believe that in-office work is more productive. This is a real position held by some executives, particularly in industries where collaboration is synchronous (trading, consulting, certain creative fields). These companies have data that suggests in-office workers are more productive, or they have cultural values around in-office presence that predate remote work. For them, RTO is consistent with how they’ve always managed. It’s not a reaction to remote work failing; it’s a return to what they consider normal.

Other companies are managing through real estate. When companies signed long-term real estate leases in 2020, they signed based on employee density assumptions. As remote work became permanent, those leases became liabilities. Some companies are mandating return-to-office not because they believe it’s more productive, but because they have committed real estate costs and need bodies in buildings to justify those costs. This is actually quite transparent in the companies that have announced RTO mandates; many of them are explicitly managing real estate portfolios at the same time they announce RTO requirements.

A third group is mandating RTO as a culture reset after significant remote-work-era growth and decentralization. These companies brought on thousands of remote employees, had to establish new hiring and collaboration patterns, and now want to rebuild what they perceive as core culture. For them, RTO is about cohesion and shared identity. The risk with this approach is that it assumes the remote employees will actually re-cohere and that the productivity losses from requiring commutes will be offset by culture gains. The data suggests this isn’t happening universally.

Finally, some companies are using RTO mandates as a polite layoff mechanism. They know that requiring office presence will cause a percentage of their workforce to leave voluntarily. From the company’s perspective, this achieves headcount reduction without the PR and legal cost of formal layoffs. This is harder to detect when it’s happening, but it’s a real pattern. Companies that announce aggressive RTO mandates and then report that people left are sometimes making the data work for them: they wanted people to leave, and the mandate achieved it.

What matters for your career decision is figuring out which of these motivations is driving your own company’s RTO mandate. That determines whether the mandate is likely to be flexible over time, whether it reflects a genuine strategic belief, or whether it’s temporary cover for other organizational change.

What the Exodus Actually Means

The statistic that eighty percent of mandating companies lost talent is important, but it’s hiding nuance. The companies that lost people aren’t all losing the same people or losing them in the same ways. Some companies mandated RTO, lost high performers to competing companies, and still considered it worth the productivity cost because they preserved their real estate commitment. Other companies mandated RTO, realized within months that they were losing the people they wanted to keep, and quietly softened the requirement. The variation matters.

The data on high performers leaving at sixteen percent higher rates is the important signal here. When a company mandates RTO and discovers that their most effective people are the most likely to leave, that creates pressure to either enforce the mandate really aggressively (and accept the loss) or to weaken it (and preserve talent). Most companies are choosing somewhere in the middle: they keep the mandate on the books, they enforce it unevenly, and they end up with a bifurcated workforce where some people are fully remote, some are complying with five days, and most are hybrid but not officially.

From an employee perspective, this creates opportunity. If your company has mandated RTO but is enforcing it unevenly, you have more negotiating room than the mandate itself suggests. If your company is enforcing it strictly, you have clarity: you either accept it or you leave. That’s not necessarily a bad thing. Clear expectations, even if you disagree with them, let you make career decisions with good information.

How to Read Your Specific Situation

When evaluating an RTO mandate at your own company, ask yourself these specific questions. First, is the mandate being enforced consistently? If ninety percent of your company is actually complying with five days, that’s a real mandate. If leadership is in the office five days but individual contributors are hybrid, that’s theater. The companies where RTO is most painful are often the ones where it’s enforced inconsistently, because you’re commuting when others aren’t, and the stated reason (better collaboration) isn’t actually changing.

Second, has leadership been clear about what happens if you don’t comply? Some companies announce RTO mandates but never follow through on consequences. Others fire people or push them out. The difference is huge for whether the mandate is a genuine business decision or a test to see what you’ll tolerate. Ask peers in your company or people who have left recently what actually happened when people didn’t comply.

Third, is the company losing people you would normally want to work with? If everyone leaving is from one department or at one level, that’s a targeted exodus and it’s signaling something. If it’s random across the organization, the mandate is probably the primary driver.

Fourth, what would compliance actually cost you? The cost of RTO isn’t just time commuting; it’s childcare, office clothing, less flexibility for medical appointments or home maintenance, and lost ability to live in lower-cost areas. For some people, those costs are minor. For others, they’re significant. Be honest about what compliance actually costs you personally, and whether your compensation accounts for that cost.

Fifth, is the company willing to negotiate? Some companies have formal flexibility programs or will negotiate exceptions if you have pull. Some companies are absolutist about the mandate. Knowing which one you’re dealing with helps you decide whether negotiating is possible or whether you’re making a binary choice.

Making Your Actual Decision

If your company has announced or is considering RTO, you’re basically facing three choices. You can comply, you can negotiate, or you can leave. Each choice has different implications depending on your situation.

Complying makes sense if the cost of commuting is tolerable for you, if the role itself is strong enough to justify it, or if your personal circumstances make it feasible. It also makes sense if the company is credible about why they need RTO and you believe in the mission. Some people choose to comply because they believe in their team and their company’s direction, and the commute cost is just part of that commitment.

Negotiating makes sense if you have bargaining power. That power comes from: being in a specialized skill area the company needs, having offers from other companies, being high-performing and connected to important work, or simply being willing to leave if you don’t get flexibility. If you have that position, use it. Most companies are more flexible with people they really value than the official mandate suggests. The conversation is usually worth having.

Leaving makes sense if the cost of compliance is genuinely high for you, if the company’s reasons for RTO don’t align with your values, or if you have better options elsewhere. The job market for IT talent is still strong enough that leaving over RTO is a viable strategy. You can move to a fully remote company, a company with genuine flexibility, or a company where your compensation is high enough that the commute cost doesn’t matter.

What you shouldn’t do is comply silently while resenting it. That’s not sustainable. It affects your work, your mood, and your job search process if you eventually decide to leave. Be honest with yourself about what you’re willing to accept, and be willing to make a decision either way.

The Bigger Trend

The RTO trend is stabilizing. The aggressive mandates of 2023 and 2024 have mostly been announced. What’s happening now is enforcement and adaptation. Some mandates are softening as companies realize they’re losing talent they value. Some are being enforced strictly as companies accept the talent loss as a cost of culture reset or real estate management. Some are being worked around through bureaucratic flexibility.

For IT workers in particular, the dynamics are interesting because IT is one of the only functions where remote work truly didn’t degrade productivity. Engineers, architects, and systems administrators shipped more code and infrastructure changes during the remote period than they do now. That’s actual measurable data. Companies mandating RTO for IT roles are usually doing it for reasons other than IT productivity, which means the mandate has a different character than it might in other functions.

If you’re in IT and evaluating an RTO mandate, use that position. Your function has proven data showing that remote work doesn’t reduce output. That changes the negotiation. You’re not arguing subjectively about culture; you’re discussing objective productivity measures.

For more context on negotiating around RTO and evaluating offers in the current remote work environment, see how to evaluate and respond to RTO mandates at your employer. And for historical perspective on how remote work negotiation has evolved, understanding the earlier remote negotiation picture helps contextualize how much power has shifted since companies first started making these demands.