# Remote Team Building Across Time Zones: A Rota

- Author: Bomb Appétit (https://bombappetit.com)
- Published: 2026-10-20
- Category: Remote teams
- Canonical: https://bombappetit.com/blog/remote-team-building-across-time-zones-rota

> Remote team building across time zones without a 3 a.m. call: a rota of regional bomb rounds that hand the mission on, with a sample rota for three regions.
Remote team building across time zones works better as a relay than as one big call. Each region plays a short bomb round in its own working hours, posts the result, and hands the next mission to the region that wakes up after it. Nobody joins at night, and the whole team still moves through the same missions together.

## Why remote team building across time zones fails with one big call

Remote team building across time zones fails with one big call because a single time slot is always somebody's evening or early morning. The people who drew the bad hour join tired, leave early or skip it, and the event meant to bring the team together ends up showing who the schedule favours.

A global team usually has a narrow overlap, if any. A slot that suits two regions lands outside working hours for the third. Organizers often accept that cost once, for a special event. The trouble starts when it becomes the normal pattern and the same region keeps paying it.

There is also a practical limit in the activity itself. A co-op bomb defusal round needs every player live at the same moment. In Bomb Appétit, the Defuser sees the bomb and describes it, and the Experts read the manual and answer. No part of the round can be played asynchronously. So the choice is not whether to have a live call, but how many smaller ones to run.

And one bomb holds two to five players, one Defuser and up to four Experts. A team of fifteen cannot share a bomb anyway. It would split into rooms whether it met on one call or not.

Once you accept that the team will play in groups, it makes sense to draw the groups by region. Each one meets at a civil hour.

## Regional rounds: every time zone plays in daylight

Regional rounds let every time zone play in daylight: each region runs its own short bomb session inside its working hours, with its own online room and its own call. The regions play the same sequence of missions, so the whole team shares the experience even though nobody plays with every colleague every week.

Each regional session is small and quick. One person opens Play, creates a room and shares its five-letter code. The game runs in any recent browser and needs no install or account, which helps when regions use different laptops and IT rules. A round takes five to fifteen minutes depending on the mission, so a session of two rounds fits in half an hour.

Keep each regional group to the size of a bomb where you can. A region of eight can split into two rooms of four. For ideas on what each person does in a group of two to five, see [team building activities for small groups of two to five](/blog/team-building-activities-for-small-groups-two-to-five).

Rotate the Defuser within each region, week by week, so everyone in that region gets the bomb over the month.

Give each region a lead for the month. The lead books the slot, opens the room, checks that the manual is on rule seed 1, and writes the hand-on post afterwards. Rotating the lead between months spreads the small admin load, and it means no single organizer in one time zone has to stay up to run another region's round. A lead who cannot attend one week simply names a stand-in from the same region.

## A three-region rota for team building

A three-region rota for team building gives the Americas, Europe and Asia-Pacific one slot each per week, in local working hours, on the same mission sequence. The region that plays first in the week sets the mission, and each region hands on to the next. The table below shows four weeks as an example.

Times and missions here are examples. Pick slots that fit your own team's hours. The missions come from the first two sections of the [mission list](/missions), which start at one module and build to five.

| Week | Region (example slot, local time) | Mission played  | Hands on to the next region                 |
| ---- | --------------------------------- | --------------- | ------------------------------------------- |
| 1    | Asia-Pacific, Tuesday 10:00       | First bite      | First bite cleared, so Button up            |
| 1    | Europe, Tuesday 11:00             | Button up       | Button up cleared, so Strange symbols       |
| 1    | Americas, Tuesday 11:00           | Strange symbols | Strange symbols failed, so Strange symbols  |
| 2    | Asia-Pacific, Tuesday 10:00       | Strange symbols | Strange symbols cleared, so Table for three |
| 2    | Europe, Tuesday 11:00             | Table for three | Table for three cleared, so Quick snack     |
| 2    | Americas, Tuesday 11:00           | Quick snack     | Quick snack failed, so Quick snack          |
| 3    | Asia-Pacific, Wednesday 10:00     | Quick snack     | Quick snack cleared, so Echo chamber        |
| 3    | Europe, Wednesday 11:00           | Echo chamber    | Echo chamber cleared, so Word salad         |
| 3    | Americas, Wednesday 11:00         | Word salad      | Word salad cleared, so Second helpings      |
| 4    | Asia-Pacific, Wednesday 10:00     | Second helpings | Second helpings failed, so Second helpings  |
| 4    | Europe, Wednesday 11:00           | Second helpings | Second helpings cleared, so Mixed plate     |
| 4    | Americas, Wednesday 11:00         | Mixed plate     | End of month: everyone tries Mixed plate    |

Each "cleared" or "failed" above is an invented result, there to show how the hand-on works. Over a month, the team climbs from the first section into the second, and every region has played its share.

The week moves west with the sun. Asia-Pacific starts the day, Europe picks up later, and the Americas finish. If your regions sit differently, follow the order in which their working days begin.

## How do regions hand the mission on to each other?

Regions hand the mission on with a short post in a shared team channel after each session: the mission played, whether the bomb went quiet, the number of strikes, and the next mission for the following region. A region that clears a mission passes on the next one. A region that fails passes on the same mission.

The post should take two minutes to write. A template helps: "Europe, Button up, defused with one strike. Over to the Americas for Strange symbols." Add one sentence on what helped, such as a name the group agreed for an odd symbol.

That sentence is the real hand-on. A tip from one region becomes the next region's head start. Over a few weeks, the channel turns into a running record of how the team learned the game, written by every region.

Results can also be compared on the leaderboards. Signed-in players who defuse appear on a board for that mission, ranked by time left and then strikes. There is no single overall ranking, and the reason is explained under [one board per mission and why there is no overall ranking](/blog/games-with-leaderboards-how-a-defusal-gets-ranked#one-board-per-mission-why-there-is-no-overall-ranking). For a relay, that is a feature: regions only compare on the same mission.

Keep the tone cooperative. The relay is one team moving forward, not three teams racing.

## What about people whose hours overlap with no one?

People whose hours overlap with no one, such as a single colleague several zones from the rest, can join the nearest region's session when it falls in their working day, or play with one partner in a pair round at a time they choose. They should not be the person routinely asked to join at night.

A pair round, with one Defuser and one Expert, is a complete game. Two people can play at any hour that suits both of them, and the result goes into the shared channel like any other region's.

Sometimes the isolated person can be the link between two regions. If their day starts as one region finishes, they can play with the end of one region and the start of the next on alternating weeks.

If nothing fits, let them take part in the channel instead: reading the posts, suggesting a tip, or joining the occasional special session when the organizer has deliberately picked a slot for them.

The aim is that their participation is never a favour they grant the rest of the team at personal cost.

When the whole team does want to meet at once, the guide to [running a single session across time zones](/blog/team-building-activities-for-remote-teams-free#how-do-you-run-the-session-across-time-zones) covers finding the overlap and cutting the plan to fit.

## The time zone mistake: always rotating the pain onto one region

The time zone mistake is always rotating the pain onto one region: the inconvenient slot rotates among people in theory, but in practice the same region keeps getting the late call because it is smaller or further from head office. Over a year, those colleagues learn that team events are for someone else.

The regional rota above avoids the problem by giving every region a daytime slot. But even with a rota, special sessions creep back. A year-end event or a big launch celebration gets scheduled for the main office's afternoon, and the far region is up at midnight again.

Make the rule explicit. Any all-team session that falls outside someone's working hours rotates which region is inconvenienced, and the organizer writes down who carried it last time.

Ask the far region directly. They may prefer their own session to a shared one at a bad hour, and they are the people who know.

For broader ideas on activities that keep every person involved, see [team building games for work where nobody sits out](/blog/team-building-games-for-work-nobody-sits-out). The general plan for [free team building activities for remote teams](/blog/team-building-activities-for-remote-teams-free) works for any one of the regional sessions.