Scheduling meetings for a distributed team: time zones, hybrid and slots that hold

A team of twelve people spread across three cities and two countries doesn't have a tool problem. It has a time problem. The weekly check-in was set for Tuesday at 9 a.m. because that's what was free on the manager's calendar when it was created, and eighteen months later, two people dial in at 8 a.m., a third joins from the car while dropping off the kids, and the person in Warsaw has given up trying to speak.

Nobody complains: a recurring slot is treated as a given, almost like a load-bearing wall. That's exactly what makes it costly. A poorly placed slot doesn't trigger a crisis, it triggers a quiet, lasting withdrawal.

What a poorly placed meeting really costs

The math is harsher than it looks. A one-hour meeting with twelve people consumes twelve hours of work. At an average loaded cost of €45 an hour, that's €540 per session, or roughly €25,000 a year for a weekly check-in. That amount is spent whether the meeting is useful or not.

The visible cost isn't the worst part. Three invisible costs pile on top:

• Fragmentation. A meeting placed at 11 a.m. wrecks the entire morning: nobody starts a task that takes forty-five minutes right before an interruption. The slot costs one hour and destroys three.
• Silent withdrawal. The person for whom the time is painful stops speaking up, then stops preparing, then gets labeled "not very engaged" in reviews. The diagnosis is wrong: they're simply badly placed in the schedule.
• Rescheduling. A meeting moved three times consumes more time in coordination than in actual content. Every postponement costs a dozen messages and a decision left waiting.

First: does this meeting need to be live at all?

Before hunting for a slot, ask the question that saves the most time. Three formats exist, and only one justifies bringing everyone together at the same moment.

Top-down information — figures, announcements, progress updates — needs no live session at all. A written message or a six-minute video is read by everyone, whenever they can, with a record that's still searchable six months later. Gathering twelve people to read a dashboard out loud is the most common waste in companies.

Decisions justify a live session when they require weighing conflicting viewpoints. In that case, only the people making the decision and those it depends on should attend. Three to six participants, rarely more.

Cohesion and collective problem-solving — a workshop, a retrospective, untangling a fuzzy problem — fully justify a live session, and that's where scheduling effort should go. It's also the format most often sacrificed because the calendar is already saturated with the first type.

A rule that works: any recurring item whose agenda would fit in a message becomes a message.

The time-zone case

Once a team spans more than a two-hour gap, intuition stops being enough, and the usual reflex — "let's just split the difference" — produces a slot where nobody is really available.

The right approach is to think in terms of an overlap window: the hours during which everyone is reasonably at work. Paris and Warsaw share almost the whole day. Paris and Montreal share the European afternoon against the Canadian morning, roughly three hours. Paris and Bangalore share late European morning. Paris and San Francisco share 5–7 p.m. European time, which isn't a comfortable working window for parents.

Three principles hold up over time:

• Never schedule outside 8 a.m.–7 p.m. local time for anyone. A slot at 10 p.m. local time isn't a compromise, it's a polite exclusion.
• Rotate the burden. When no slot is comfortable for everyone, alternate: one week favoring the west, the next favoring the east. Nobody bears it every single time.
• Record and write up a summary, systematically. It's the only thing that lets someone miss a session without missing the decision.

Watch out for daylight-saving shifts: Europe and North America don't switch on the same dates, and several countries don't observe any change at all. Twice a year, a slot that used to work shifts by an hour for part of the team, without anyone having changed anything.

The hybrid case

Hybrid work adds a constraint many organizations underestimate: the office day isn't a preference, it's a household arrangement. Someone working from home on Tuesdays and Thursdays has often built childcare around those two days. Moving an in-person meeting from Wednesday to Thursday isn't a scheduling inconvenience for them — it's finding a childcare solution in forty-eight hours.

Three rules prevent most of the damage:

Meetings that genuinely require physical presence are set on a stable day, known in advance, ideally the same one every week or month. Everything else happens over video, even when half the team is in the office.

A mixed meeting is a video meeting. If even one person is remote, everyone joins individually, headset included. Six people around a room microphone and two remote means two people who don't hear the side conversations and never get to speak.

In-person time is reserved for what actually warrants it: workshops, onboarding a new hire, a contentious topic, creative work. Bringing eight people in for a thirty-minute update that would have worked fine on video is the surest way to make returning to the office unpopular.

Consulting people without losing a week to it

Sharing calendars solves a small part of the problem: it shows free slots, not acceptable ones. An empty calendar on Friday at 5 p.m. doesn't mean the person is available; it often means they're wrapping up their day.

What you need to gather to set a recurring slot fits in five questions, asked once:

1. Your actual working hours, in your time zone, distinguishing contractual hours from the hours you actually keep.
2. Your recurring hard blocks: childcare, part-time schedule, commute, classes, a regular personal commitment. No forced detail — "unavailable" is enough.
3. Your office days, and how flexible they really are.
4. The time of day you're most effective for demanding collaborative work.
5. Other recurring meetings you already attend, to avoid days where everything stacks up.

These answers shouldn't be public. Someone who announces in front of the whole team that they're unavailable at 5 p.m. ends up justifying themselves; the same person answering confidentially simply states the truth. That's exactly the difference between a schedule that holds and one you'll be renegotiating in three weeks.

OuiCanPlan is built for this exact step: you describe the meeting in a few lines, each person answers via a link in two minutes without seeing anyone else's answers, and you get back the slots that are genuinely compatible with everyone's time zone and constraints, along with the detail of who is excluded by what. You decide with full knowledge instead of guessing. The results are real, and there's no advertising involved.

Set it, announce it, and stop revisiting it

Once the slot is decided, the announcement matters as much as the choice itself. It contains three elements and fits in four lines:

"The team check-in is moving to Tuesday 2 p.m. Paris time, which is 3 p.m. in Warsaw and 8 a.m. in Montreal. It's the only time all three time zones fall within working hours. Duration: forty-five minutes maximum. The session is recorded and a written summary is published right after, for anyone who can't make it."

The slot, the reasoning, the capped duration, the solution for absentees. An announcement built this way doesn't get renegotiated, because the logic is visible and there's already a way out.

The rules that make a recurring slot stick

• A capped duration that's actually respected. A meeting that systematically runs over becomes a meeting people avoid.
• An agenda sent the day before. No agenda, no meeting: it's a hard rule, and it's the one that most improves the quality of team check-ins.
• A quarterly review. Three questions: is this still the right slot? Is the frequency still justified? Who could stop attending without anything changing?
• The right not to show up. Someone with nothing to bring or receive should be able to opt out without having to negotiate it. It's the best health indicator for a meeting: if everyone opts out, the meeting only ever existed for the organizer.
• No meetings on Friday afternoon, nor in the first hour of Monday. Those are the two slots that produce the most absences and the least content.

What changes when it's done right

A distributed team whose slots are chosen explicitly, announced with their reasoning, and reviewed regularly behaves very differently. People arrive prepared because the agenda exists. The people furthest away speak up because the time is bearable for them. And above all, the number of meetings goes down: once you start looking at a recurring slot as a €25,000-a-year expense, you naturally cut the ones that aren't worth half that.

It's an hour of work, once. It pays for itself by the second week.

Three real-world situations

A nine-person product team, Paris, Lisbon and Bucharest. A one-hour gap at most: the constraint isn't the time zone, it's childcare and part-time schedules. The solution comes down to two protected slots — a thirty-minute check-in on Monday at 10 a.m., a one-hour retrospective on Thursday at 2 p.m. — and a strict ban on adding anything on Wednesday, a meeting-free day. Everything else goes in writing.

A twenty-person customer support team on a two-shift rotation. Here, no slot brings everyone together, and trying to find one is a waste of time. The right answer is structural: a handover point at the junction of the two shifts, fifteen minutes of overlap with a verbal handoff, and a monthly service meeting held twice, identically, once per rotation. Two sessions beat one session half the team can't attend.

A six-person executive committee where two members travel constantly. The issue isn't the time but the stability: a fixed slot, locked in a year in advance, joined from an airport if needed. An executive committee that shifts around at the mercy of calendars teaches the whole company that slots are negotiable.

Tools don't replace the decision

Shared calendars, date polls and scheduling assistants solve the mechanical part. They don't solve the fact that three people wanted incompatible things, and that a choice has to be made. Most teams that complain about their tool actually have an unowned arbitration problem: nobody has said out loud which criterion wins.

Choose explicitly between three criteria, and state which one you're applying: maximum number of available participants, mandatory attendance of certain key people, or minimum disruption for the most constrained person. These three criteria yield three different slots. None is objectively "the right one"; the right one is the one you explained.