The policy
Three policies and what each leaves open
The same three days, written three ways, and the quite different weeks each one produces. A worked comparison rather than a recommendation.
Days this part is about, hour by hour
Monday, the third week
0 of 7Came in to make up a day missed through illness
Wednesday, the third week
1 of 7Tuesday, the second week
0 of 7three days · 21 hours logged · one of them was only possible there · two of the three days contained no such hour at all · four were made worse by being there
Three days the policy treats as identical.
Where work is split across locations, managers can review the complete platform details to make project effort and recurring bottlenecks clear enough for a transparent capacity discussion.
Teams can compare this approach with current guidance available from CNET.
Most hybrid policies are one of three shapes. They look like small variations on each other and they produce substantially different weeks.
The three
A. The count. Three days a week in the office.
B. The count with an anchor. Three days a week, one of which must be Wednesday.
C. The named day. Wednesdays, everyone. The rest is yours.
What each produces
| A. Count | B. Count + anchor | C. Named day | |
|---|---|---|---|
| Journeys a week | 3 | 3 | 1 |
| Days with guaranteed overlap | 0 | 1 | 1 |
| Days chosen with no information | 3 | 2 | 0 |
| Can a room be booked ahead? | No | For one day | Yes |
| Can a day be judged? | No | The anchor, yes | Yes |
| Scheduling freedom | 5 days, constrained by a count | 4 days free | 4 days free |
| Measured by | Attendance | Attendance | Whether the day worked |
Reading the table
A is the common case and it is the worst of the three on every column that matters. It maximises journeys, guarantees no overlap, and produces the coordination collapse described throughout this site.
B is the usual improvement and it is a strange compromise. It fixes one day, which is most of the benefit — but it keeps the other two journeys, which is most of the cost, and those two days remain exactly as uncoordinated as before. It is the version most often adopted because it reads as a minor amendment to A.
C is less restrictive than either on any ordinary measure of freedom, and it is the only one that reliably produces the thing all three are nominally for. It is also the hardest to write centrally, because the right day differs by team, which is why it is rare.
The honest objections to C
It is not costless and the case for it is weaker in two situations.
Where the work genuinely needs sustained co-presence — some kinds of design, some operational work, a team in its first months — one day is not enough, and C with a single anchor undersupplies it. The answer is two named days, not a count.
Where the office has to be justified by occupancy, C produces a building that is full on one day and empty on four, which is worse for the property argument than A. That is a real conflict and it should be argued about openly rather than through a collaboration policy that is doing a different job.
What this comparison is not
It is not a recommendation to adopt C, and no table settles a question like this. It is an attempt to make visible that the three options differ in more than tone, and that the choice between them is usually made as though the only variable were strictness.
The variable that actually differs is who does the coordinating, and in A the answer is nobody.
The same week lived under each
One person, the same work, the same team, three policies.
Under A. Three journeys. Tuesday — four colleagues in, one useful hour. Wednesday — seven in, no room available, two useful hours taken in a corridor. Thursday — nobody in, nothing. Six and a half hours of travel; three useful hours; two of them degraded.
Under B. Three journeys. Wednesday is now guaranteed, so the planning lands there and a room is booked: three useful hours, undegraded. Tuesday and Thursday are unchanged — one useful hour and none. Six and a half hours of travel; four useful hours.
Under C. One journey. Wednesday, everybody in, room booked, the planning and the one-to-ones on it: four useful hours. Two hours and ten minutes of travel.
| A | B | C | |
|---|---|---|---|
| Travel | 6h 30m | 6h 30m | 2h 10m |
| Useful hours | 3 | 4 | 4 |
| Travel per useful hour | 2h 10m | 1h 38m | 33m |
The illustration is constructed rather than measured, and the direction is the thing to take from it rather than the numbers. B improves the return and keeps the cost. C changes both.
Why B is adopted anyway
Because it looks like an amendment and C looks like a retreat.
B can be introduced by adding eight words to an existing document. C requires deleting the number, which is the part of the policy that people believe is doing the work, and which is the part that is most visible to whoever approved it.
That is a reason about documents rather than about outcomes, and it is worth naming, because it explains why the version with the worst cost-to-benefit ratio is the one most organisations converge on.