October 25, 2026

Return-to-office mandate: how to keep senior engineers and staff the roadmap

Your CEO wants everyone back in the office. Who is at risk, what to negotiate, the attrition budget, and where UK, Dutch and German law stands.

Guide

Tech

A return to office mandate for your engineers has just landed on your desk, and you didn't write it. Your job now is narrower than the policy debate: find out which senior engineers are exposed, negotiate the exceptions that are worth having, and put a number on the roadmap capacity you may lose. This guide is for a VP of Engineering or Head of Engineering in that position. It takes no side on offices. Reasons CEOs commonly give include collaboration, onboarding and culture. The plan works whichever way the policy ends up.

What the research on office mandates and senior engineers shows

Two research papers are often cited. Both are US studies of large companies, and both are more careful than the headlines built on them.

What the tenure study found

Van Dijcke, Gunsilius and Wright studied resume data from three firms: Microsoft, SpaceX and Apple. The abstract of the paper, revised as version 2 on 24 September 2026, concludes that "Return-to-office mandates appear to drive senior employees away, posing a risk to firm productivity and innovation."

That sentence is the one people repeat. The appendix says something different and more useful: "RTO mandates changed who left but not how many left." Read it twice. The paper doesn't find that total departures rose. It finds that the mix of people leaving shifted toward the senior end. For a VP of Engineering that's arguably worse than a headcount hit, because you can backfill ten juniors faster than you can replace two people who hold the architecture in their heads.

Early press coverage quoted figures from the first version (May 2024). We don't repeat them; this article cites the revised version.

The authors flag the limits themselves. The sample is three firms. The study also ran a 2023 replication for Amazon and Google that found no significant effects, with layoffs confounding the period, and the appendix advises readers to "interpret the null results for 2023 cautiously". So the honest summary is: one well-run study of three large employers shows senior-weighted departures, and a weaker replication neither confirms nor rules it out.

What the S&P 500 study found

Ding and Ma's research (SSRN 4675401, summarised by Pitt Business) looked at S&P 500 firms. Their summary reads: "We provide evidence that RTO mandates hurt employee satisfaction but do not improve firm performance." It speaks about the firm as a whole, not about engineering delivery. Treat the conclusion as the authors' interpretation.

What the evidence cannot tell you

Neither study measures your team. The samples are US big-tech and large-cap firms, not a 40-person company with a Series B and one office in a city where half the engineers have never lived. Neither measures delivery: cycle time, incident rate, shipped features. Nobody can tell you from these papers whether your velocity moves.

Your own data fills that gap. What the research does give you is a direction to plan for: if people leave, expect the senior ones to be over-represented, and don't assume the headline number will move either way; the one study that looked found the total unchanged at three firms.

Which of your engineers are at risk

This is judgment, not a validated model. No study ranks these factors, and we won't invent percentages. But you know your team, and the questions below are cheap to answer from HR records and one-to-ones.

Risk factorHow to checkQuestion to ask
Long tenure plus strong outside demandStart dates and recent recruiter inbound the engineer mentions"If you got three offers tomorrow, what would keep you?"
Commute changeHome postcode against the office, door-to-door time"What does a five-day week add to your day?"
Fixed-hours caregivingExisting flexible arrangements on file"Which hours can't move?"
Relocated since hireAddress changes in HR records"Are you still within reach of the office?"
Hired as remote, contract names homeThe place-of-work clause in each contractNothing yet: read the clause first, then ask counsel
Sole owner of a critical systemYour bus-factor map"Who else can run this on a bad night?"

Rank each senior engineer on this table, then add one more column: how much the roadmap depends on them. A senior with two risk factors and a system only they understand is where your plan starts. One with four risk factors on well-documented work is a lower priority.

What you can negotiate before the policy is announced

If the policy is already public, you still have room. Mandates are often written at company level and executed at team level, and in our experience of how these decisions get made, a CEO cares more that the policy works than that it's uniform.

Role-based carve-outs

Some work really does depend on where you are. On-call rotations with a hardware lab, security-sensitive environments, and incident-response roles are cases a CEO can accept without feeling the policy has been gutted. Anchor days, where the team is in on set days and free otherwise, are the other common compromise. Which fits depends on whether the mandate's stated goal is time together (anchor days work) or presence (they don't).

Grandfathering and written exceptions

Ask for written exceptions with an end date and a review, not verbal ones. A verbal exception disappears when you leave or when someone asks why one team has different rules. Put the name, the arrangement, the reason and the review date in a document.

The risk to manage is a two-tier team: some engineers exempt, some not. Resentment forms fast when the rule appears arbitrary. Tie exceptions to criteria you can say out loud (role, contract terms, pre-existing arrangements), not to who asked loudest. Our guide to running a blended distributed team covers keeping a split team working as one.

What to put in the memo to the CEO

Skip the argument about whether offices work. Write a one-page memo: the exceptions you want, each named by role or criterion with the business reason; what each costs (coordination overhead, culture risk, precedent); and what the alternative costs, using the attrition budget from the next section, expressed as roadmap items delayed.

CEOs approve trade-offs more readily than complaints. "Exempting these four roles costs us some in-person time, and not exempting them puts Q3's migration at risk" gives them something to decide. On the retention side, see retaining senior engineers without a promotion budget, because a mandate is rarely the only reason a senior is already half out the door.

How to budget attrition and plan the backfill

Treat potential departures like any other roadmap risk: put a number on it, then decide what you'd do about it. The arithmetic below uses your own inputs, not a replacement-cost percentage.

For each senior engineer on your risk list, write down three things.

  • Probability of leaving within the year. This is your own assumption, labelled as such. Use three bands (low, medium, high) if a percentage feels false.
  • Months until a replacement is productive. Take this from your last two senior hires: the time from opening the role to a first merged change, plus the time to full independence. Your history beats any benchmark.
  • Share of the roadmap that engineer carries, in engineer-months for the next two quarters.

A mechanics-only illustration with made-up inputs: you judge three seniors likely to leave, and your last two senior hires took four months to reach independence. Three seniors times four ramp months is 12 engineer-months of capacity at risk, before counting the work they'd have done. Replace every figure with yours. The result is a number you can set against the roadmap, instead of "we might lose some people."

That number gives you four options, and you can combine them.

  1. Reprioritise. Cut or delay the items the at-risk engineers carry. Cheapest if the items aren't critical.
  2. Backfill permanently. Start the search before the resignation, when you have the lead time. Slow, but the right answer for roles you'll keep.
  3. Add interim senior capacity. It starts faster than a permanent search and can overlap with the leaver. This is where remote or nearshore engineers working outside the mandate are one option among several, and a trade-off the CEO should see in the memo, not a way around the policy. Our guide to managing nearshore developers covers what that takes.
  4. Reduce the single points of failure now. Knowledge that lives in one head is your exposure under any scenario.

What the law says about changing place of work

Can your company make people come back? The answer depends on the country and, above all, on the contract. This is general information, not legal advice. Take the specifics to an employment lawyer in each country before you act.

UK

The government's page on employment contracts says that terms are changed "usually by agreement between the employee and employer". If the contract fixes the place of work, moving it is likely a change to the terms, so check the clause. Ask counsel what happens without agreement.

Separately, the Employment Relations (Flexible Working) Act 2023 changed the right to request flexible working. On the text of section 1 on legislation.gov.uk, an employee may not make more than two applications to the same employer in any period of 12 months. The employer may not refuse an application unless it has consulted the employee about it. And the decision period is two months, shortened from three. The page records these amendments as in force from 6 April 2024, and they apply regardless of when the employment began. For you, that means engineers can ask whatever their length of service, and your managers must consult before saying no.

Germany

Section 106 of the Gewerbeordnung (GewO) says: "Der Arbeitgeber kann Inhalt, Ort und Zeit der Arbeitsleistung nach billigem Ermessen näher bestimmen". Put plainly, the employer can specify the place of work at its reasonable discretion. That applies only where the employment contract, a works agreement, a collective agreement or a statute doesn't already fix it. So a contract that names the engineer's home as the place of work changes the answer. Which one you have is a question for German counsel, along with what "reasonable discretion" means for a particular individual.

Netherlands

The Eerste Kamer, the Dutch Senate, rejected the "Wet werken waar je wilt" bill on 26 September 2023. Its own announcement says the chamber "heeft dinsdag 26 september een initiatiefwetsvoorstel van de Tweede Kamer verworpen". The bill would have treated a request about where to work like a request about working hours. It didn't become law, so Dutch employees have no statutory request right built on it. What the existing flexible-work rules give them, and how they interact with each contract, is for a Dutch employment lawyer.

With engineers in all three countries, one global policy meets three different legal starting positions. Ask counsel before the memo goes to the CEO.

What this means for your headcount plan

You're deciding three things: how many exceptions to ask for, how much senior attrition to budget, and whether to hold part of the roadmap on capacity that sits outside the mandate. None of that needs the mandate to be right or wrong.

Our judgment: ask for the fewest exceptions you can defend by role or contract, budget for the senior end of the team rather than the average, and start the replacement lead time before anyone resigns, because the ramp months you wrote down above are what the roadmap actually loses. Present the CEO a cost of exceptions against a cost of attrition, in roadmap items, and let them decide with the numbers in front of them.

If a senior engineer does resign, the 30-day knowledge transfer and backfill plan covers the first month.

FAQ

Can I refuse to return to the office?

It depends on the country and on the contract. In the UK, contract terms change usually by agreement, so the place-of-work clause matters. In Germany, section 106 GewO lets the employer set the place of work at reasonable discretion unless a contract, works agreement, collective agreement or statute fixes it. In the Netherlands, a bill that would have extended the flexible-work request right to place of work was rejected in 2023. This is general information, not legal advice.

Do return-to-office mandates make people quit?

The best primary evidence we found says the mix changes more than the total: the tenure study of Microsoft, SpaceX and Apple concludes that RTO "changed who left but not how many left". It covers three firms, and its 2023 replication was weaker. Plan for senior departures.

Which engineers are most likely to leave?

The tenure study points to seniors. Beyond that, no source ranks the factors; our judgment is in the risk table above.

How many exceptions should I ask for?

Fewer than you want, tied to criteria you can state aloud: a role that needs presence or access to hardware, a contract term, or an arrangement that predates the mandate. That's judgment, not a benchmark. Every exception you can't explain feeds the two-tier-team problem.

Can nearshore or contract engineers stay outside the mandate?

Whether the mandate applies to contractors depends on how it's written and on each engagement, so ask your CEO and counsel. If you want capacity outside it, HighCircl matches senior engineers in seven European countries, 72 hours to a shortlist of 3 to 5, with no minimum hour commitment and no recruitment fee. Details are on the HighCircl hiring page.

Sources

Share this article

Author Image

HighCircl Editorial Team

The HighCircl editorial team writes about hiring software engineers, nearshore development, and engineering team building. Our articles draw on direct experience sourcing and placing senior developers across Poland, Hungary, Slovakia, Serbia, Slovenia, Romania, and Spain — and on candid conversations with the CTOs and engineering leads who hire them.

HighCircl is a nearshore engineering network that delivers matched candidate shortlists in 72 hours. Every piece of content we publish is informed by real engagement data: actual developer rates, real hiring timelines, and what separates engineering teams that scale cleanly from those that stall.

Take Me to the Experts

Access our network of industry-leading software engineers.

Start Now