By August 2023, return-to-office mandates had become the defining conflict of the post-pandemic workplace. Meta had mandated three days a week in the office and was firing people who didn’t comply. Apple demanded three days a week and faced employee rebellion. Google was pushing a hybrid model. Amazon and others were quietly moving toward full-time office returns. At the same time, organizations like Stripe, Airbnb, and others were doubling down on remote work. The industry was splitting into two camps. Some organizations saw in-person work as essential to their culture and operations. Others saw it as an outdated relic. And employees were left trying to figure out whether their employer’s RTO mandate was a reasonable business decision or whether it was time to start looking for a company that respected their time.

This is a decision that matters to your career and your life, so let’s think through it carefully and honestly.

The Legitimate Case for Being in an Office

First, let’s acknowledge that there are genuine reasons companies want people back in the office. Some of these reasons are real and meaningful. Onboarding new employees is easier when you can put them next to an experienced engineer who can answer questions in real time. Mentoring junior staff happens more naturally when you see people regularly and can have hallway conversations about problems they’re stuck on. Complex whiteboarding sessions, architectural discussions that require a lot of back and forth, sometimes those are genuinely better in person. Some people, especially those early in their careers, may benefit from being around more senior colleagues and learning through observation.

Cultural bonding is real, though it gets oversold. Teams that work together in person do build relationships that remote teams sometimes miss. There’s a spontaneity to office interaction that’s hard to replicate on video. If you’re building something that requires tight collaboration and rapid iteration, having people in the same physical space can help.

And there’s a legitimate business continuity argument that some organizations make: if a crisis happens and we need everyone coordinating in real time, having a location where people can gather matters. That argument applies to certain organizations more than others. It’s much stronger for a crisis response organization than for a software company.

The point here is that these reasons for returning to the office aren’t absurd. They’re not purely about control. Some of them are real concerns that reasonable people can have about distributed work. A company that acknowledges these tradeoffs and says “we think the benefits of office work outweigh the costs for our organization” is being more honest than one that just mandates RTO without explaining why.

The Case Against It

That said, there are also real costs to returning to the office that don’t get discussed enough. The most obvious one is time. If you have an hour commute each way, three days a week in the office means three hours a week in a car or on public transit that you weren’t spending three months ago. That’s roughly 150 hours per year. In salary terms, if you make $100,000 a year, that’s about $7,000 worth of time that you’re now spending on commuting instead of doing something valuable.

The financial cost matters too. Parking, tolls, gas, public transit passes, meals you buy closer to the office instead of making at home, dry cleaning because you’re wearing professional clothes more often, all of these add up. Some people calculate that their net pay dropped by 5 to 10 percent when you factor in the direct costs of returning to the office. That’s real money out of your paycheck.

There’s also the reality that for many IT professionals, the work hasn’t fundamentally changed since they’ve been working remotely. You’re still writing code, still administering systems, still responding to tickets, still in meetings. The tools have gotten better. Remote development tools, remote access to infrastructure, video conferencing, they all work well enough now that the work doesn’t require you to be in a physical office. If your job can be done remotely with the same productivity, then the mandate is about something other than business need.

And then there’s the accessibility question. People with disabilities, people with chronic illnesses, people dealing with family caregiving situations, people in certain financial situations where they can’t afford the cost of commuting, all of these people lose optionality when work becomes mandatory office time. That’s not a niche concern. That’s affecting a meaningful portion of the workforce.

How to Calculate Your True Cost

Before you make a decision about whether to accept your employer’s RTO mandate, calculate the actual cost. Be concrete about it. How long is your commute? How many days a week are they asking you to come in? Multiply that out to annual hours. At your hourly rate, how much is that time worth? What’s the direct cost of commuting? Gas, parking, public transit, all of it. What’s the indirect cost? If you’re now spending more on lunch and coffee because you’re not at home, factor that in. If you have childcare costs that increase because you’re not home to handle school pickup, that matters.

Some people do this calculation and realize the cost is genuinely minimal. Maybe they live close to the office. Maybe they’re already driving in that direction anyway for other reasons. Maybe the office has free parking and subsidized meals, so the direct cost is zero. For those people, the decision is easier. The main cost is time and flexibility, and whether that’s worth it depends on whether they value the office experience.

Other people do the calculation and realize that going from remote to three days a week in the office is effectively a 5 to 10 percent pay cut. That changes the math significantly. If you’re being asked to take a 5 to 10 percent pay cut, that matters. You should think of it that way.

Red Flags and Green Flags

Some RTO mandates are about legitimate business need. Others are about control, about managers feeling more comfortable when they can see people working, about executives worried that remote work is eroding company culture, about real estate investments that the company wants to justify. The question is: which kind of mandate is yours?

Red flags for a problematic mandate include: no flexibility at all, even for people in specialized situations like caring for disabled family members. An inability to articulate specifically why the office time is necessary. A mandate that increased over time, starting with “one day a week” and creeping toward five days. A mandate that applies to teams that don’t interact with each other anyway. An RTO that happens because your CEO read an article about the importance of in-office culture, not because there’s specific business need. A mandate that came from executives at headquarters with no input from the people who would be affected by it. Management dismissing remote work concerns as “not being a team player.”

Green flags include: genuine acknowledgment of the tradeoffs and why the company thinks the office time is worth it. Flexibility for people with documented reasons for needing remote work. Reasonable accommodation for people who are relocating or have caregiving obligations. Management saying “we tried this, it didn’t work well, and here’s why we’re changing” rather than “we’ve decided this is how we do things now.” Acknowledgment that the mandate has a cost and that the company is trying to minimize that cost by offering things like flexible hours, free transit passes, subsidized meals, or compressed schedules.

Negotiating a Better Arrangement

If your company has mandated RTO but you think you can do your job well remotely, you can try to negotiate. This is where being good at your job matters. If you’re already someone the company values, someone who delivers results, someone who is reliable and effective, you have negotiating power.

Start with a specific proposal. Don’t ask for complete remote work if the company is mandating office time; that’s an opening position that will be rejected immediately. Ask for something more modest: two days in the office instead of three, flexible days so you can work around your schedule, the ability to take your commute cost out in additional salary, a compressed schedule where you come in for longer days but fewer of them.

Anchor your request to business value. If you’ve been productive remote, show that. If your work has been of high quality, reference specific projects. Make the case that remote work doesn’t negatively impact your performance. Then propose an arrangement that’s different from what the company announced but that acknowledges their concerns: “I’d like to come in two days a week, specifically on days when the team is collaborating on architecture. On those days, I’ll be fully present and available. For the other three days, I’ll be remote and fully focused on individual work.”

The company might say no. They might enforce the mandate universally. But you can also ask for a trial period: “Can we try this arrangement for three months and then evaluate whether it’s working?” That’s often easier for a company to agree to than a permanent change, and if it works, you can extend it.

When to Walk

Sometimes a company’s RTO mandate isn’t worth negotiating. Sometimes it’s time to move to a company that respects remote work. Here’s how to make that decision.

Calculate whether your current company plus the new cost of RTO is still competitive with what you could earn elsewhere. If your current salary is $100,000, and the RTO mandate costs you $7,000 to $10,000 a year in time and direct costs, and fully remote jobs at competitors pay $100,000, you should probably look around. You’re not trading money; you’re trading money and quality of life.

Look at the market. In 2023, there are still a lot of fully remote IT jobs. If you’re skilled in infrastructure, security, cloud engineering, DevOps, there’s still significant demand for remote work. The job market has softened compared to 2021 and early 2022, but fully remote positions still exist and still pay competitively. Some are even willing to accept lower salaries in exchange for the cost savings of remote work.

Consider the alternative. Sometimes accepting a job that pays slightly less but is fully remote is actually a better deal than staying at a higher-paying job with mandatory office time. A $95,000 fully remote job might be worth more to you than a $105,000 job where you’re commuting 10 hours a week.

The decision is ultimately personal. Some people value office culture, mentorship, and in-person collaboration enough that they’re willing to bear the cost. Others decide it’s not worth it. Both are reasonable positions. The point is to make the decision consciously, with full information about what it’s costing you, rather than accepting the mandate as inevitable.

The Bigger Picture

Return-to-office policies have fundamentally changed how organizations think about work arrangements. Some of the companies that mandated RTO most aggressively also had the highest turnover rates among remote-capable employees. Others found that the mandate worked better than they expected. The reality is probably in the middle. Office time has value in some contexts. Full-time remote work works better in others. For most organizations, some balance is probably optimal. But the specific balance is going to vary.

What matters is that you understand the trade-offs, you calculate your personal costs accurately, and you make a decision based on your own situation rather than just accepting whatever the company announces. If the RTO mandate is reasonable and well-justified, you might decide it’s worth it. If it’s not, you have the power to look elsewhere. That power matters especially in IT, where skilled professionals are still in demand and you have options.

Don’t just accept the ultimatum. Think through it. Calculate the cost. Negotiate if possible. And if it’s not acceptable to you, be willing to make a change. Your time is your most valuable resource, and you get to decide how it gets spent.