How Many Office Days Is "Three Days a Week," Actually?
"Three days a week in the office" sounds like a fixed, easy number. It isn't, once you try to turn it into a monthly total. A five-week month with a public holiday landing on one of your in-office days produces a different office-day count than a four-week month with no holidays at all — even though the underlying policy, "three days a week," never changed. Anyone trying to plan desk space, commuting costs, or simple fairness across teams on different in-office days needs the actual count, not the weekly shorthand.
Turn your office pattern into a workweek
The trick to counting this precisely is to stop thinking of "three office days" as a quantity and start thinking of it as a specific set of weekdays — Tuesday, Wednesday, Thursday, say, with Monday and Friday remote. Once the pattern is a defined set of days rather than a vague count, it behaves exactly like a business-day calendar: you can count how many of those specific weekdays fall inside any date range, the same way a standard calculator counts Monday-through-Friday business days. The only difference is which days are "in."
Holidays don't land evenly on every pattern
This is where the weekly shorthand breaks down. A public holiday that falls on a Monday costs a team with a Monday/Wednesday/Friday office pattern one of their three office days that week — but costs a team with a Tuesday/Wednesday/Thursday pattern nothing at all, because their in-office days weren't touched. Both teams are nominally on "three days a week," and both experience the same holiday, but only one of them loses an office day to it. Multiply that across a year of holidays landing on different weekdays and the two teams end up with a meaningfully different real office-day total, even though HR wrote the same policy for both.
Months are not interchangeable either
Calendar months don't contain the same number of each weekday. A 31-day month can contain five Mondays and only four Fridays, or vice versa, depending on where the 1st falls. A hybrid pattern anchored on Monday will therefore produce a different office-day count in a "five-Monday" month than in a typical one — again, without the policy itself changing at all. Anyone booking desks by headcount-per-day, or comparing office attendance across months for a utilization report, needs the actual day-by-day count for the specific month, not an assumed constant.
A worked example
Take a Tuesday/Wednesday/Thursday hybrid pattern across a month with a public holiday on the second Wednesday. A naive "three days a week times roughly four weeks" estimate suggests about 12 office days. The real count depends on exactly how many Tuesdays, Wednesdays, and Thursdays the month contains and which one the holiday removes — often landing at 11 once the holiday is correctly subtracted from the Wednesday total, not from the month as a whole. Run the same exercise for a Monday/Tuesday pattern in the same month and, because the holiday didn't touch either of those days, the count comes out differently again. The "three days a week" framing hides all of this; the day-by-day count doesn't.
Why the precise count matters
Beyond curiosity, the exact office-day total feeds real decisions: desk-booking systems sized to actual attendance rather than nominal policy, commuting-cost or transit-subsidy calculations, fairness checks between teams on different in-office patterns, and utilization reporting that compares one month against another. A policy that reads identically for two teams can produce a noticeably different lived experience — and a different real cost — once holidays and month length are accounted for.
Facilities teams sizing a desk-booking system face a related version of the same problem at scale: if half the workforce is on a Tuesday/Wednesday/Thursday pattern and the other half on Monday/Wednesday/Friday, Wednesday becomes the single busiest office day of every week by a wide margin, while Monday and Friday sit comparatively empty. Planning desk capacity around an average "three days a week" figure would understate Wednesday demand and overstate it on the other days — a mismatch that only shows up once the patterns are counted day by day instead of averaged into one weekly number.
Comparing two patterns fairly
The same day-by-day count is also the only fair way to compare two hybrid policies against each other. "Three days in office" and "two days in office" sound like a fixed one-day-a-week difference, but the actual gap for a given month depends on which specific weekdays each pattern uses and where the month's holidays fall. A team on a two-day Monday/Friday pattern in a month with a Monday holiday can end up closer in real office days to a three-day Tuesday/Wednesday/Thursday team than the nominal policy would suggest. Comparing the policies by their weekly number alone hides that; comparing the actual counted totals for the month does not.
Count your own pattern precisely
The Hybrid Work Schedule Calculator takes your actual in-office weekdays, a date range, and the public holidays that apply, and returns the real business-day count of office days inside that range — not an estimate derived from multiplying a weekly number by a rough number of weeks. Run your team's real pattern through it before finalizing a desk-booking plan, comparing utilization across months, or reconciling a commuting stipend, and "three days a week" stops being a shorthand and becomes an actual number you can plan around.