Hybrid Schedules: How to Design One That Works for the Team

How to choose and pilot a hybrid schedule, using research on retention, isolation and collaboration to decide which days your team should spend together.

Collaboration Center · Last reviewed October 23, 2026 · 6 min read

Many hybrid schedules start as a number: two days home, three in the office. The number is the easy part. What makes a schedule work is whether the days people spend together are the days when being together actually helps, and whether the rules feel fair to everyone on the team.

This guide covers what research says about hybrid schedules, the common models, and a simple way to pilot one with your own team.

What the research says, and what it doesn't

The strongest recent evidence comes from a randomized trial published in Nature on June 12, 2024, by Nicholas Bloom, Ruobing Han and James Liang. Over six months in 2021 and 2022, 1,612 graduate employees in the airfare and IT divisions of Trip.com, a large travel technology company, were randomly assigned either to work from home on Wednesdays and Fridays or to come in all five days. The hybrid group's quit rates fell by one-third, and job satisfaction rose. The researchers found no difference in performance reviews or promotions over the following two years. Managers in the study also changed their minds: before the trial they expected hybrid work to hurt productivity slightly; afterward, on average, they expected a small gain.

Keep the limits in view. This was one company, one country, mostly university-educated staff, and a schedule of two remote days. It does not tell you what happens with four remote days, in a retail shop or with a team of six.

Older research adds a caution about intensity. A 2007 meta-analysis in the Journal of Applied Psychology by Ravi Gajendran and David Harrison combined 46 studies covering 12,883 employees. Telecommuting generally had small, mostly beneficial effects and no general harm to workplace relationships, but high-intensity telecommuting, defined as more than 2.5 days a week, harmed relationships with coworkers. A 2008 study by Timothy Golden, John Veiga and Richard Dino of 261 professional teleworkers and their managers found that professional isolation hurt job performance, that the effect grew with time spent teleworking, and that more face-to-face interaction reduced it.

The practical reading: a modest amount of remote time is well supported, and the in-person time you keep is worth protecting.

Start with the work, not the calendar

Before choosing days, list what your team actually does in a typical month and sort it into two piles.

Work that benefits from being together: onboarding and training, planning sessions, complex problem-solving, conversations about feedback or conflict, and getting to know people on other teams.
Work that benefits from quiet: writing, analysis, design, coding, focused review, and most individual tasks.

A 2021 study in Nature Human Behaviour by Longqi Yang and colleagues, using data from 61,182 Microsoft employees in the U.S., found that firm-wide remote work made collaboration networks "more static and siloed," with fewer bridges between different parts of the company. That suggests in-person days are especially useful for the cross-team contact that remote work tends to squeeze out.

Choose a scheduling model

Most hybrid schedules fall into one of four patterns:

Team anchor days. The team picks one to three shared office days, and everyone is in on those days. Collaboration is predictable, but the chosen days need to suit most people's commitments.
Organization-wide fixed days. Everyone comes in on the same days. Cross-team contact is easiest, but office space and parking must handle peak days.
Flexible with a minimum. People choose their own office days within a weekly or monthly minimum. Individuals get the most freedom, but the team may rarely overlap, which defeats much of the purpose.
Role-based. Some roles are fully on-site, some hybrid, some remote, based on the work. This fits mixed organizations but needs clear, published criteria.

For most small teams, anchor days are the simplest place to start. The Trip.com experiment offers a useful detail: large meetings and product launches there usually happened midweek, and employees who had the option mostly worked from home on Friday. Put the meetings that matter on anchor days and let the remote days carry the focus work.

Make the policy the default, not a favor

The same Nature study found that employees who had not volunteered for remote work still used about 40 percent of their remote days once the option was assigned, compared with about 55 percent for volunteers. The researchers read this as support for the company's suspicion that many people did not volunteer out of fear of how it would look. If hybrid work is something people must ask for, some will not ask. Writing the schedule as the team's standard arrangement removes that signaling problem.

Fairness also includes people whose needs differ. The U.S. Equal Employment Opportunity Commission notes that working at home can be a reasonable accommodation for an employee with a disability, so route those requests through your accommodation process rather than the general schedule rules. For nonexempt employees, the U.S. Department of Labor's Field Assistance Bulletin 2023-1 notes that a flexible schedule with an off-duty block in the middle of the day can be legitimate, as long as the employee is completely relieved from duty during that block.

Make office days worth the trip

An office day spent on video calls with people at home is a commute without a purpose. A few habits help:

Schedule team meetings, workshops and one-on-ones on anchor days and keep remote days light on meetings.
Invite people from other teams to join for lunch or a working session once in a while.
When some people must dial in, have everyone in the room use the same meeting tools (shared document, chat) so remote participants are not an afterthought.
Keep a short list of "best done together" work and check it when planning the week.

Pilot, measure and adjust

Treat your first schedule as an experiment. For example, imagine a 12-person accounting office that tries Tuesday and Wednesday anchor days for one quarter. Before starting, it agrees on what to watch: client deadlines met, how quickly internal questions get answered, a short monthly pulse survey on workload and connection, and any resignations. At the end of the quarter the team reviews the results together and decides whether to keep the days, change them or adjust the minimum.

Good questions for the review:

Did anchor days actually contain the collaborative work, or did it leak into remote days?
Did anyone end up isolated, such as a new hire or the one person on a different shift?
Were the rules applied the same way across managers?
What would people change, and why?

Write down what you decide and when you will look again. A schedule that is reviewed on purpose tends to hold up better than one that changes by exception.

Key takeaways

A randomized trial at Trip.com found that two remote days a week cut quit rates by one-third with no measured harm to performance or promotions.
Research on heavier remote work flags weaker coworker relationships and professional isolation, so protect regular in-person time.
Decide what work benefits from being together before you pick days.
Team anchor days are a simple starting model; put important meetings on them.
Make hybrid the standard arrangement rather than a favor, and pilot it with clear measures before locking it in.

Sources

Spotted something out of date? Let us know.

Hybrid Schedules: How to Design One That Works for the Team

What the research says, and what it doesn't

Start with the work, not the calendar

Choose a scheduling model

Make the policy the default, not a favor

Make office days worth the trip

Pilot, measure and adjust

Key takeaways

Sources

More in Remote & Hybrid Work

Remote and Hybrid Work Policy: What to Include and Why

Asynchronous Communication: When to Work Async and How

Onboarding Remote Employees: Paperwork, People and First Tasks