Return to Office: How to Run an RTO Transition
How to run a return to office transition: choosing the mandate, setting the days, handling ADA and caregiver exceptions, and enforcing it.
Return to Office
The operational version rather than the trend piece: how to decide whether you need a mandate at all, how to choose the days, how to build the exception process before you announce, where the disability and caregiver exposure actually sits, what notice you owe, and how to enforce the thing consistently once somebody tests it
The first return to office announcement I sent went out on a Thursday afternoon with an effective date eleven days later. By Monday I had two resignation conversations, an accommodation request I had no process for, and a manager quietly telling his team that the rule did not really apply to them.
None of that was about the office. All of it was about the order I did things in. The policy document was fine. It was the last thing I needed and the first thing I wrote.
A return to office transition is a sequencing problem: justify the mandate, choose the days, define the exceptions before anyone can ask for one, check what notice you owe, announce once, then enforce it through a single path. I build the people and records tooling for small businesses without an HR department at FirstHR, and this is the order I would use now. It is general information rather than legal advice, and a change of this size is worth twenty minutes with employment counsel in your state.
What RTO Means in Practice
RTO stands for return to office. It means requiring employees who have been working remotely, in whole or in part, to perform their work at a company location again, either every scheduled day or on a defined number of days each week.
That distinction matters more than it sounds. I have seen a single document try to cover both, and the result was an attendance policy carrying leave language it could not support. Keep the office attendance rule separate from anything touching medical leave, and if you want the drafting done for you, the return to office policy templates are already scoped that way.
The second thing worth knowing before you decide anything is where the market actually sits, because most employers overestimate how unusual their situation is. According to the Bureau of Labor Statistics American Time Use Survey (2025 results), 35 percent of employed people did some or all of their work at home on days they worked, compared with 33 percent in the 2024 results, which is not the picture the headlines describe.
Gallup reports that the share of remote-capable US employees in a hybrid arrangement moved from 55 percent to 51 percent over two quarters, with fully on-site and fully remote each gaining two points (Gallup). That is a drift, not a reversal. Planning a transition as though everyone else has already gone back will lead you to a harsher mandate than your competition for talent is actually running.
Decide What the Mandate Is For
Before choosing days, write one sentence describing the behavior you want that is not happening now. If you cannot write it without using the words culture or collaboration, you do not yet have a reason you can defend to the person who has to rearrange their childcare.
The test I use is whether the sentence contains something observable. "Engineers and support never see the same problem at the same time" is observable. "We have lost our culture" is a feeling that may be true and cannot be scheduled against. The first one tells you which people need to overlap and on which days. The second one tells you nothing, which is why it usually produces a five-day mandate.
The cost side is real and measurable. Research covered by SHRM found that companies imposing return to office mandates experienced unusually high turnover and longer time to hire, with the effect most pronounced among senior employees, women, and more skilled workers. That is not an argument against mandates. It is an argument for knowing what you are buying, because the bill lands on exactly the people who are hardest to replace.
| Stated reason | Is it observable? | What it should drive |
|---|---|---|
| Cross-team problems take days to resolve | Yes, cycle time is measurable | Shared anchor days for the two teams involved, not a company rule |
| New hires ramp slowly and ask nobody for help | Yes, ramp time and early attrition | On-site requirement weighted to the first months rather than forever |
| Customers or equipment are on site | Yes, the work is physically located | Role-by-role designation written into the job description |
| Managers cannot tell who is working | No, this is a management problem | Clear expectations and a review cadence, not a commute |
| We have lost our culture | No | Nothing until it is restated as an observable behavior |
| The lease is expensive and the office is empty | Yes, but it is a real estate decision | An honest conversation about the lease before a mandate |
The last row is the one people are least willing to say out loud, and employees can smell it from a distance. If the driver is a lease you signed before the world changed, saying so is better received than a collaboration argument nobody believes. Honesty about a commercial reason survives contact with a skeptical team. A borrowed justification does not.
Setting the Days
Pick the smallest number of on-site days that produces the overlap you named, and where overlap is the point, name the specific days rather than the count. A minimum-days rule with free choice is the most popular model and the one most likely to fail at its own purpose.
Here is the failure mode nobody predicts. You require two days a week and let teams choose. Engineering picks Tuesday and Wednesday because of a standing planning meeting. Support picks Wednesday and Thursday because of shift coverage. The two teams that most needed to see each other now overlap for one day, and half your people are commuting on days that produced nothing. The structure of the hybrid schedule decides whether the mandate works, more than the number does.
Midweek days are the compromise most employers land on, and there is a reason. Monday and Friday attract the highest exception traffic, carry the most childcare conflict, and generate the most resentment per commute. If your goal is overlap rather than symbolism, a pair of midweek days will get you further than a Monday requirement chosen to make a point.
Consider also whether the rule should be uniform. A company-wide standard is simpler to explain and harder to defend when a role genuinely does not benefit from it. Role-by-role designation is more defensible and requires you to write down a reason for each designation, which is work most small employers skip and then regret. Whichever you pick, it belongs in your written company policy set rather than in a manager's head.
Build the Exception Process First
Decide who may request an exception, who decides, what evidence is required, how long a decision takes, and whether an approval is permanent or reviewed, all before the announcement goes out. An exception process invented in response to the first request will look like favoritism no matter how fair it actually is.
The reason is not legal, it is social. The first exception you grant becomes the precedent everyone else measures their own case against. If it was granted informally by one manager over a coffee, that is the standard you have set, and you will spend the next quarter explaining why somebody else with a similar story got a different answer.
The response time item is the one small employers underestimate. During my own transition the single largest source of goodwill was answering exception requests within a week, including the ones I declined. A fast no is easier to absorb than a slow maybe, and it lets people plan.
Where the Legal Exposure Sits
The mandate itself is rarely the legal problem. In most states employment is at will and work location is a term the employer sets. The exposure comes from how individual requests are handled, and it concentrates in four places.
On disability, the framework is well established. According to the Equal Employment Opportunity Commission, the Americans with Disabilities Act does not require an employer to offer telework to everyone, but where an employer does offer it, employees with disabilities must have an equal opportunity to participate, and allowing an employee to work at home may be a reasonable accommodation where a disability prevents performing the job on site and the work can be done at home without significant difficulty or expense (EEOC).
Two practical consequences follow. First, if you already allowed remote work broadly, it becomes harder to argue that on-site presence is an essential function of a specific job. Second, you may explore effective on-site accommodations before agreeing to remote work. Joint technical assistance the Commission and the Office of Personnel Management issued in February 2026 for the federal sector says an employer may ask an employee to try an in-office accommodation it reasonably believes will be effective, and that a telework accommodation need not continue in perpetuity, while cautioning against rescinding telework across the board without an individualized determination in each case.
Pregnancy sits in its own lane. Federal law requires covered employers to reasonably accommodate known limitations related to pregnancy, childbirth, and related medical conditions, and telework and schedule modification are among the accommodations most commonly requested. A return to office change is exactly the event that surfaces them, so read the Pregnant Workers Fairness Act requirements before you set an effective date rather than while you are answering the first request.
Caregiver exposure works differently and catches more small employers. Caregiver status is not itself protected under federal law. The Commission has nonetheless warned for years that unfavorable treatment of workers with caregiving responsibilities can constitute unlawful disparate treatment where it is based on a protected characteristic such as sex, including decisions driven by assumptions about which parent wants flexibility (EEOC enforcement guidance). The safe pattern is written criteria, applied identically, with the reasoning on file. Separately, an employee using intermittent leave has protections that no attendance policy overrides, which is worth checking against your FMLA obligations if you are covered.
What Notice You Owe
No general federal rule requires advance notice before changing where employees work. Several state and local rules apply around the edges, and your own documents may create obligations that statutes do not.
| Source of obligation | What it can require | Who it typically reaches |
|---|---|---|
| State wage notice laws | Written notice before a change to the information in the wage notice takes effect, in New York at least seven calendar days unless the change appears on the wage statement | All employers in the state, triggered by changes to the rate or basis of pay |
| Predictive scheduling laws | A written schedule a set number of days in advance plus premium pay when it changes late | Large employers in covered hourly industries such as retail, hospitality, and food service in Oregon and several cities |
| Employment agreements and offer letters | Whatever the document promised about location or notice | Individual employees, and often the most senior ones |
| Handbook and policy language | Notice periods your own handbook committed to | Everyone who received the handbook |
| Collective bargaining agreements | Bargaining obligations before a unilateral change | Represented workforces |
| Practical runway | Nothing legally, but transitions announced with less than a month land badly | Everyone, every time |
Oregon is the state to know on scheduling. Its predictive scheduling law requires covered employers to provide written work schedules 14 calendar days in advance and to pay predictability pay when a schedule changes with less notice, including an hour of pay at the regular rate when the employer adds more than 30 minutes of work to a shift (Oregon Bureau of Labor and Industries). Coverage is limited to large retail, hospitality, and food service employers, so it rarely bites an office return, but if you run mixed operations it can. The wider map of predictive scheduling laws by state is worth a scan.
The pay-notice trap catches office employers more often. If your remote arrangement came with a home internet stipend, an equipment allowance, or a different rate, check whether ending it changes anything you listed in the wage notice, because New York requires written notice at least seven calendar days before a change to that information takes effect, unless the change shows up on the wage statement. The practical rule is to treat any money attached to remote work as a separate change with its own notice, documented alongside the schedule change itself.
Announcing It
Announce once, in writing, to everyone at the same time, with a real effective date and a named route for exceptions. Every hour between the first leak and the official message gets filled with a worse version of the story than the one you are about to tell.
The acknowledgment step is the one small employers skip and the one that matters most later. A signed acknowledgment stored in the employee record is the difference between an expectation you can enforce and a memo somebody credibly claims never to have seen. If your employee handbook already has an acknowledgment flow, run this through the same one.
One more thing about tone. The message that landed best for me admitted the trade openly: this costs you something, here is what we are getting for it, here is what we are doing to make the days worth the commute. Announcements that pretend nobody is losing anything get read as either dishonest or unaware, and both are worse than the actual news. Change of this size is a change management exercise before it is a policy exercise.
Enforcing It Without Losing People
Enforce through one documented path with one reviewer rather than through manager discretion. Inconsistent enforcement is simultaneously the biggest legal exposure and the fastest way to lose the people who are complying.
The sequence that works is unremarkable: a private conversation first, then a written reminder, then formal discipline, with the same reviewer signing off at each stage. What makes it work is not the steps, it is that everyone goes through the same ones. A team that watches two people skip the office with no consequence while a third gets a written warning has learned that the rule is about who your manager likes.
Consider what you are measuring and why before you turn on any attendance tracking. Recording who is on site on which day is reasonable and often necessary for space planning. Using it as the primary performance signal is not, and it changes behavior in ways that produce compliance without producing the overlap you wanted. Keep any attendance record proportionate to the reason you started it.
Finally, accept that some attrition is the price and decide in advance which of it you can absorb. Research covered by SHRM found the turnover effect of return to office mandates was concentrated among senior and more skilled employees. If two of those people leaving would break something, the honest options are a softer mandate, a role-designated exception, or a retention conversation before the announcement rather than after the resignation. Your broader retention plan should account for this rather than react to it.
What to Track After the Effective Date
Track four things for the first two quarters: whether the behavior you named actually improved, how many exceptions were requested and granted, whether resignations rose in specific teams, and whether enforcement was consistent across managers.
The first one is the one everybody forgets. You wrote a sentence describing an observable behavior that was not happening. Go back and check whether it is happening now. If cross-team resolution time has not moved after a quarter of shared anchor days, the days are not the constraint, and adding a third day will not fix a problem that was never about location.
Exception volume tells you whether the mandate fit the workforce. A handful of requests suggests the policy matched reality. A flood suggests you set the bar somewhere your people cannot reach, and it is cheaper to adjust the policy than to process a hundred individual negotiations. Pay attention to which teams the requests cluster in, because that pattern usually points at a role that should have been designated differently.
Consistency is the one that protects you. Once a quarter, read the exception log end to end and ask whether two similar requests got two different answers. If they did, find out why while the answer is still an administrative correction rather than an exhibit. That review takes half an hour and is the single highest-value thing on this list.
Where Small Employers Get This Wrong
Five patterns, and the first one is the one I ran into personally.
Announcing before the exception process exists is first. The requests arrive within hours, you improvise the first few answers, and those improvised answers become the precedent for every case after them.
Writing the policy before deciding the reason is second. The document is the easy part and doing it first lets you skip the only genuinely hard question, which is what behavior you are trying to change.
Letting managers grant local exemptions is third. It feels generous in the moment and it destroys the rule for everyone else, while creating exactly the inconsistent treatment that turns an attendance matter into a discrimination claim.
Treating an accommodation request as a complaint is fourth. Nobody uses the legal words. A manager who answers a health-related objection with a restatement of the policy has just skipped the interactive process on your behalf.
And giving too little runway is last. Childcare, school pickup, commuting arrangements, and in some cases housing all take longer than two weeks to rearrange, and a compressed effective date converts people who would have complied into people who resign. If you are moving from a fully remote arrangement, the hybrid transition guide covers the operational side of that shift in more depth.
Frequently Asked Questions
What does RTO mean?
RTO stands for return to office. It describes an employer requiring people who have been working remotely, either fully or partly, to perform their work at a company location again. The requirement can be full time, a fixed number of days each week, or a set of named days everybody shares. RTO is not the same thing as return to work, which refers to an employee coming back from medical leave, workers compensation, or another protected absence. The two get confused constantly, and mixing them in one policy document creates a mess, because return to work carries leave and disability obligations that an office attendance rule does not.
Can an employer legally require employees to return to the office?
Generally yes. In most US states, employment is at will and the location of work is a term the employer sets, so requiring on-site work is lawful in principle. The limits are specific rather than general. An individual employment agreement or a union contract may promise remote work. A disability, or a limitation related to pregnancy or childbirth, may trigger a duty to consider remote work as a reasonable accommodation. And treating similar employees differently along lines that track a protected characteristic creates exposure regardless of what the policy says. The mandate itself is rarely the legal problem. The handling of individual cases is.
How many days a week should a return to office policy require?
There is no correct number, but there is a correct method: pick the smallest number that produces the specific overlap you need. If the reason is that people who work together are never in the same room, then the days matter more than the count, and naming shared anchor days beats requiring an unnamed number. If the reason is customer or equipment access, the number follows from the work itself. Gallup research on remote-capable US employees shows hybrid remains the most common arrangement rather than a transitional stage, so a policy built around a realistic mid-week overlap tends to hold better than a maximal one.
Do you have to give employees notice before changing to in-office work?
No general federal law requires advance notice of a change in work location, but several state and local rules apply around the edges. New York requires written notice to employees at least seven calendar days before a change to the information in the wage notice, such as the rate or basis of pay, takes effect, unless the change appears on the wage statement. Oregon and a number of cities have predictive scheduling rules that require written schedules in advance and premium pay for late changes, though those rules reach large employers in hourly industries such as retail, hospitality, and food service rather than office roles. Beyond the statutes, contracts, offer letters, and handbook language can create notice obligations of their own.
What if an employee asks to stay remote as a disability accommodation?
Treat it as an accommodation request and start the interactive process, even if it arrives as a complaint about the new policy rather than as a formal request. According to the Equal Employment Opportunity Commission, the Americans with Disabilities Act does not require an employer to offer telework to everyone, but where an employer does allow it, employees with disabilities must get an equal opportunity to participate, and allowing work at home can be a reasonable accommodation where a disability prevents performing the job on site. You may explore alternative on-site accommodations first, and you may decline remote work if attendance is genuinely an essential function, but you have to document how you reached that conclusion.
Can you deny remote work to an employee with childcare responsibilities?
Usually yes, because caregiver status is not a protected class under federal employment discrimination law. The risk is comparative rather than absolute. The Equal Employment Opportunity Commission has long warned that unfavorable treatment of workers with caregiving responsibilities can amount to unlawful discrimination when it is based on a protected characteristic such as sex, including assumptions about which parent will want flexibility. Approve or decline caregiver requests using written criteria applied the same way to everybody, keep the reasoning on file, and never let the decision rest on an assumption about what a particular employee probably wants.
How do you enforce a return to office policy without losing people?
Enforce it through one documented path rather than through manager discretion, and separate the people problem from the attendance problem. Route every case through the same progressive steps: a private conversation, then a written reminder, then formal discipline, with the same reviewer signing off each time. Research covered by SHRM has found that employers imposing return to office mandates saw unusually high turnover and longer hiring cycles, with the effect concentrated among senior and more skilled employees, which means the cost of inconsistent enforcement is paid disproportionately by the people you least want to replace.