What a manager can actually grant

Usually within a line manager's gift

• Which days you take. The count comes from above; the days almost never do. This is the single most useful fact on this page.
• A team anchor day. A team agreeing among themselves when they will be in is not usually a policy matter at all.
• What goes on which day. Moving the planning, the one-to-ones and the review onto one day is ordinary scheduling.
• Where the team sits. A known corner of a floor costs nothing and recovers most of what unassigned seating removes.
• Whether a plan for the week gets shared. Nine messages on a Friday. No permission required from anyone.

Every one of those would have made a material difference to the quarter recorded on this site, and not one of them requires a change to any document.

Usually not within a line manager's gift

• The number of days. Set centrally, and asking a manager to vary it puts them in an awkward position without improving your odds.
• A permanent, recorded exception. This normally involves HR, and an informal version granted locally is fragile — it ends when the manager does.
• A change to contractual terms. A different question with a different process.
• Anything that would set a visible precedent. Managers are appropriately cautious here, and a request framed so that it would apply to everyone is heard as a policy proposal rather than a personal one.

The practical consequence

Sort your request before making it. If what you want is on the first list, ask directly, now, and expect a yes. If it is on the second, either frame it so that it is not — which is usually possible — or accept that it needs a longer route and more evidence.

The most common failure is taking a first-list problem to a second-list conversation: raising the coordination collapse as a complaint about the three-day policy, when the fix was a weekday swap that the person in the room could have agreed in ten seconds.

What a manager gets out of the first list

Worth saying, because it is not a favour being requested.

A team with a named day gets more out of its office time, which is the thing the manager is being measured on by whoever set the policy. A team that shares its plans wastes fewer journeys. A team that sits together produces the unscheduled hour the policy was written to buy.

The first list is not a set of concessions. It is the set of things that would make the arrangement work, and it is entirely available at the level where the work actually is.

Why the first list goes unused

Not because managers refuse. Because nobody asks, and nobody asks for two reasons.

The problems present as policy problems. The experience is "the office does nothing for me three days a week", which sounds like a complaint about the three-day rule. The fix is a weekday swap. Nothing about the experience points towards the fix.

The requests look too small to make. Asking to move a Thursday to a Monday feels like an imposition about nothing, which is precisely why it is granted instantly when it is finally asked. People save up their requests for things that feel proportionate to the trouble of asking, and the useful requests are all small.

The five, as sentences

Ready to use, because the phrasing is most of the difficulty:

Could I move my Thursday to a Monday? Same three days — most of the people I work with are in Monday and Tuesday.

Could we pick one day a week when we are all in? I think we would get more out of it than three separate days.

Could the planning and the one-to-ones go on the same day?

Could we agree to sit together when we are in — the north end of the third floor, say?

Could we post where we will be each week? Just a thread on Fridays.

Five sentences. None of them mentions the policy, asks for an exception, or requires anybody to check with anyone. On this record they would have been worth more than removing a day.

What to do if a manager says no to these

Ask which part. A refusal of something this small is usually not a refusal of the thing itself; it is a constraint nobody has mentioned — a floor plan agreed elsewhere, a desk policy, a view from above about consistency between teams.

Knowing which constraint is operating is worth more than the request was, because it tells you where the decision actually lives and whether the second list is where you have been all along.