Hybrid work policy: writing rules people can actually follow

A hybrid work policy sets out where people work and when. Almost every version in circulation states a number of office days and leaves everything else to interpretation, which is why hybrid generates more friction than either fully remote or fully in-person arrangements: the rule is clear and the practice is not.

The friction is predictable and comes from four unanswered questions: which days, who decides, what happens to meetings when some people are in and some are not, and whether the policy applies to everybody.

What the policy has to answer

• How many days, and measured over what period. Three days a week and twelve days a month are different arrangements, and the second is far easier to live with.
• Which days, and who chooses. Fixed days for the whole team, team-chosen anchor days, or individual choice — each has real consequences and only one of them produces days when everybody is in.
• What the office is for. If people commute in to sit on video calls, the policy will not survive contact with the second week, and everybody will notice.
• How meetings work when attendance is mixed. Default to everyone dialling in individually, or accept that the people in the room dominate — those are the two honest options.
• Exceptions: roles that must be on site, people hired as fully remote, and how somebody requests a variation.
• Whether it applies to leadership. Nothing kills a hybrid policy faster than the people who wrote it being visibly exempt.

Anchor days beat total counts. Three days of your choosing means everybody optimises individually and the office is randomly populated, which delivers the cost of commuting with none of the benefit of colocation. Two agreed days when the whole team is present, plus flexibility for the rest, produces actual overlap — and overlap is the entire argument for hybrid.

The problems worth planning for

1. Proximity bias: people in the room get more attention, more informal information and, over time, more opportunity. Watch who is being promoted rather than assuming good intentions handle it.
2. Mixed meetings, which are worse than either extreme unless everybody joins individually. Decide the convention and enforce it.
3. Desk supply. Hot desking with fewer desks than people works until the anchor day when everybody arrives.
4. Documentation drift: decisions made in the room and not written down are invisible to whoever was at home, which is where async habits stop being optional.
5. Fairness across roles. Some jobs cannot be done remotely, and pretending otherwise is more corrosive than acknowledging it and compensating differently.

The legal and practical edges

Home working touches areas that vary by jurisdiction — health and safety assessment of the home workspace, equipment and expense reimbursement, insurance, and whether a change to working location alters the employment contract. Several regimes also give employees a right to request flexible working with a defined process for responding. Those are worth checking properly for where your people are, rather than adapting another company's policy, which is where most of the copied text comes from.

Where it lives

Ettex Teams holds who works where and the team structure the anchor days apply to, with the policy itself in Ettex Docs alongside remote work policy, and shared in-office days visible in Ettex Calendar. The communication habits that make mixed attendance workable are in asynchronous communication.

The boundary: no desk booking, no occupancy tracking, no attendance monitoring. Measuring badge swipes to enforce a policy is a management decision rather than a tooling one, and it usually signals that the policy has no agreed purpose.