A flat policy produces a predictable, uneven pattern
A hybrid work policy requiring, say, three in-office days per week without specifying which days almost universally produces the same observed pattern across organizations: Tuesday, Wednesday, and Thursday attendance spikes well above the team's average, while Monday and Friday attendance drops well below it — not because those specific days were chosen for a good reason, but because employees converge on the days they expect colleagues to also be present, and that expectation becomes self-reinforcing.
Why the midweek peak is self-reinforcing
Once a critical mass of a team starts favoring Tuesday-Thursday, additional employees rationally choose those same days — coming in on a day nobody else is around defeats much of the collaboration purpose in-office time is meant to serve, which reinforces the imbalance rather than correcting it over time.
The capacity planning mistake this pattern causes
Provisioning desk capacity based on team size divided evenly across the week — or based on an average daily attendance number — systematically underestimates real midweek demand and overestimates Monday/Friday demand, leading to a real, recurring desk shortage on exactly the days it matters most for collaboration, while the office sits underused on the days it's fully provisioned for.
What planning around the actual pattern looks like
Rather than assuming even distribution, modeling expected attendance with realistic day-of-week weighting reveals the actual capacity gap in advance — informing decisions like assigning specific teams to specific required days (spreading demand more evenly) or accepting a genuinely lower desk-to-headcount ratio calibrated to true peak, not average, demand.
External constraints add a further layer worth accounting for
A meaningful share of any team has hard external constraints — school schedules, caregiving commitments, other recurring obligations — tied to specific days, meaning a policy that ignores individual constraints and assumes total flexibility will predictably clash with real employee circumstances on top of the general midweek-peak pattern.
Frequently Asked Questions
Employees converge on the days they expect colleagues to also be present, since coming in when nobody else is around defeats much of the collaboration purpose of office time — this expectation is self-reinforcing and produces the same Tue-Wed-Thu peak pattern across hybrid workplaces broadly, independent of any specific policy design choice.
Even distribution assumes attendance spreads uniformly across weekdays, but the real pattern concentrates well above average on Tuesday-Thursday and well below on Monday/Friday — planning off an average systematically underestimates real midweek demand while overestimating quieter-day demand.
Assigning specific teams or groups to specific required in-office days spreads total demand more evenly across the week, rather than leaving every employee free to independently gravitate toward the same midweek days everyone else is choosing.
Yes — whether a policy requires two, three, or four in-office days a week, the underlying convergence dynamic still concentrates chosen days toward the middle of the week unless days are explicitly assigned rather than left to individual choice.
No. All calculation happens locally in your browser — your team size, desk count, and attendance projections are never uploaded or logged.