GuidesRemote workProductivity

Writing a Hybrid Work Policy That Survives Contact

Most hybrid policies specify days in the office and nothing else, which is why they're renegotiated every quarter. The five decisions that actually need making.

Hybrid policies get rewritten more often than almost any other HR document, and the reason is consistent: most of them answer one question and leave four unanswered.

The one they answer is how many days. The four they leave are the ones that actually generate disputes.

The five decisions

Who decides, and at what level. Company-wide mandate, team discretion, or individual arrangement. Each is defensible; what fails is leaving it ambiguous, because then it is decided case by case by whoever asks most persistently. Set the framework centrally and let teams set the pattern within it — a support rota and a research group genuinely need different things, but unbounded manager discretion produces inconsistency that looks like favouritism and sometimes is.

Coordinated or individual office days. This is the decision that most determines whether the policy delivers anything, and it is the one most often skipped. A three-day mandate where everyone picks their own days produces offices full of people on video calls to colleagues who came in on different days. You have paid the full commute cost and bought none of the collaboration the mandate was justified by.

Coordinated days — same days for a team, or anchor days company-wide — are the whole mechanism. Two coordinated days beat three uncoordinated ones on every dimension except the appearance of compliance.

Core hours or full flexibility. Separate from location and frequently conflated with it. Core overlap hours make synchronous work possible without dictating a full schedule; full flexibility maximises individual autonomy and pushes everything asynchronous. Both work. What does not work is implying flexibility while scheduling as though everyone is available 9 to 5 — our time zones playbook covers overlap design.

How split meetings run. The default failure is a conference room with six people and three faces on a screen nobody can hear. Pick a rule and hold to it: either everyone joins from their own device regardless of location, or meetings with any remote attendee are fully remote. The hybrid room is the worst of both and it quietly excludes whoever is not present.

What is explicitly not conditional on attendance. The clause most policies omit. Promotion, pay, project allocation, access to opportunity. Writing it down matters because proximity bias is well documented and does not announce itself; and writing it down creates something to check against.

The proximity bias problem

This is the part of hybrid that goes wrong slowly and is hard to reverse.

Managers who see some people and not others allocate differently, not through malice but through availability. The person who happens to be there gets asked, gets included in the corridor conversation where the decision is actually made, gets the visible project. Over eighteen months that compounds into a real divergence in progression between two populations doing comparable work.

Stating that attendance is not a factor is necessary and insufficient, because nobody believes they are doing it. What helps is checking: whether project allocation, promotion rates and development opportunities differ between office-heavy and remote-heavy staff. If they do, the policy is not what is operating.

This is also the strongest argument for coordinated days. If the team is together on the same days, the corridor conversation includes everyone, and the mechanism that produces the bias is weakened structurally rather than by exhortation.

What to measure instead

If you want to know whether a hybrid arrangement is working, the useful signals are about coordination and concentration rather than location.

Whether meeting load changed, and in which direction. Many hybrid arrangements increase meetings, because teams compensate for reduced informal contact with scheduled contact. That is usually a net loss, and it is measurable — the cost of meetings piece covers pricing it.

Whether focus time improved or fragmented. Office days are frequently worse for concentration and better for collaboration, which is fine if that is the intent and a problem if nobody said so. If both office and home days are fragmented, the policy is not the issue. Our note on focus time versus active hours covers the measurement.

Whether after-hours work changed. Flexibility that becomes availability is the most common way hybrid degrades, and it shows up here first — see burnout signals.

Whether workload distribution shifted. If the people in the office are absorbing more, that is proximity bias showing up in load before it shows up in promotion data, and it is a capacity finding.

Also worth separating from engagement, which a hybrid policy affects and these metrics do not measure — engagement and productivity come apart often enough that one is a poor proxy for the other. And if you are weighing a schedule change more generally, the four-day week evidence is the best-documented natural experiment available.

Read all of these at team level over months. Per-person location data is both less informative and much harder to justify — the return to office productivity piece covers what the evidence does and does not support about mandates.

A hybrid policy and a remote monitoring system answer different halves of the same question. Remote employee monitoring software covers the measurement side, including why presence is the one signal not worth collecting.

Keeping it short

A hybrid policy that runs to nine pages will not be read and will not be followed. The useful version is one page per the five decisions above, plus a stated review date.

The review date matters more than it sounds. Hybrid arrangements that are presented as permanent get litigated internally forever, because anyone unhappy with them is arguing against a settled position. The same arrangement presented as reviewed in six months with stated criteria gets a much easier reception, and you keep the ability to change it without it reading as a defeat.

Where ProdView fits

ProdView measures the coordination and concentration signals: focus time, fragmentation, meeting load, after-hours patterns and workload distribution, at team level, from activity metadata rather than screen content. That is the data that tells you whether a hybrid arrangement is producing the collaboration and focus it promised.

When not to pick us: you want attendance enforcement. We have no badge integration, no presence tracking and no location data, and we would not recommend running a mandate that way regardless. Compliance measurement is a facilities question; whether the policy works is a different one.

Try before you commit

Three seats are free forever, which is enough to see whether your office days are actually less fragmented than your home days — a question most organisations assume the answer to. The meeting cost calculator prices the coordination overhead if it turns out to have grown.

P
ProdView Team

The ProdView team builds privacy-first workforce analytics for engineering managers. We write about measuring productivity without surveillance, the laws that govern monitoring, and how the best teams run their week.

Frequently asked questions

What should a hybrid work policy include?
Who decides where someone works and at what level, whether office days are coordinated or individual, core hours versus full flexibility, how meetings work when attendance is split, and what is explicitly not conditional on attendance. The last one is the clause most policies omit and most disputes concern.
How many days in the office should a hybrid policy require?
The number matters far less than whether the days are coordinated. Three uncoordinated days where you see nobody you work with deliver none of the collaboration benefit the mandate was justified by, while costing the full commute. Two coordinated days generally beat three random ones.
Should hybrid policy be set centrally or by team?
Set the framework centrally and the pattern by team. Teams differ legitimately — a support rota and a research group have different needs — but leaving everything to managers produces inconsistency that reads as favouritism and creates genuine fairness problems.
How do you stop hybrid becoming unfair to remote workers?
Write down that promotion, pay, project allocation and opportunity are not conditional on attendance, then check whether that is true using actual data rather than assurance. Proximity bias is well documented and it does not announce itself; it shows up as remote staff being allocated less visible work.
Do you need monitoring to run a hybrid policy?
No, and monitoring attendance to enforce a mandate is usually counterproductive. Badge data that answers whether the policy is complied with tells you nothing about whether it is working. The useful measurement is whether coordination and focus time improved, which is a different question.
Related reading
  • Measuring Technical Debt Without Pretending
    Debt resists measurement because it isn't one thing. Four proxies that actually correlate with pain, and why a single debt score is worse than no number.
  • How Many Reports Is Too Many?
    Span of control gets set by org-chart convenience and discovered by attrition. The signals that show a manager is over-extended before their team tells you.
  • Badge Data Is Not Productivity Data
    Office utilisation tells you who turned up. It cannot tell you whether the day worked. What each measurement supports, and the error of substituting one.

Put a number on it

Before you change anything, put a figure on it. The calculator is free and needs no signup.

Open the ROI calculatorStart free — 3 seats