# Competitive Team Games: Two Teams, One Mission Board

- Author: Bomb Appétit (https://bombappetit.com)
- Published: 2026-10-20
- Category: Missions and leaderboards
- Canonical: https://bombappetit.com/blog/competitive-team-games-two-teams-one-mission-board

> Competitive team games from a co-op bomb: two teams take the same mission in turns, and time left and strikes on the board decide who won the night.
Competitive team games can grow out of a co-op bomb when two teams play the same mission one after the other and compare the clock. Nobody plays against anybody. Each team fights its own bomb, then the time left decides the winner, and strikes break a tie. A mission board gives both teams the same rules.

## How can competitive team games work in a co-op bomb?

A co-op bomb turns into a contest when two teams play the same mission separately and compare what each run left behind. The numbers that matter are time left on the clock when the last module goes green and the strikes taken on the way. Higher time wins. Fewer strikes settles a tie.

Bomb Appétit is built for cooperation inside one team. One player, the Defuser, sees the bomb. The others, the Experts, read the manual and never see the case. With two to five people per bomb, a group of six to ten splits cleanly into two teams that each run their own round. Nothing in the game pits the teams against each other directly. The competition lives in the comparison afterwards.

That comparison needs both teams to face the same conditions. A mission does that job. It fixes the time limit, the strike limit, the module pool, how many modules and needy modules appear, the case size and the rule seed of the manual. When both teams pick, say, Quick snack, both get four minutes, four modules and three strikes, with modules drawn from the same three types.

The results screen at the end of each run gives you the raw material: the time left, the strikes against the limit, and each module with the time it was solved. Write those down before anyone presses Play again. If the Defuser on each team is signed in, the run can also land on that mission's board on the [leaderboard page](/leaderboard), which gives you a second record that nobody can misremember. To learn what each column on that board says, read our guide to [reading a mission board row by row](/blog/game-leader-board-reading-a-mission-board).

The game keeps no running score between rounds, so a night of several missions needs a sheet on paper. For a simple tally that works over a whole evening, see [how to score across rounds by hand](/blog/game-night-ideas-for-adults-bomb-defusal#how-do-you-score-across-rounds-without-a-spreadsheet) in our [game night plan for adults](/blog/game-night-ideas-for-adults-bomb-defusal).

### A two-team match sheet

Here is the sheet we use, with an invented result filled in. The team names, players and times are examples.

| Round | Mission         | Team | Defuser | Time left | Strikes | Round winner |
| ----- | --------------- | ---- | ------- | --------- | ------- | ------------ |
| 1     | Table for three | Red  | Sam     | 2:31      | 0       |              |
| 1     | Table for three | Blue | Priya   | 2:31      | 1       | Red          |
| 2     | Quick snack     | Blue | Leo     | 1:12      | 2       |              |
| 2     | Quick snack     | Red  | Ana     | 0:58      | 0       | Blue         |
| 3     | Echo chamber    | Red  | Jo      | 3:05      | 1       |              |
| 3     | Echo chamber    | Blue | Kim     | 2:40      | 0       | Red          |

In this example Red takes the night two rounds to one. Round 1 is a tie on time, so the strike column decides it. Round 2 shows that strikes only matter on a tie: Blue took two strikes and still won by fourteen seconds. Swap which team goes first each round, and change the Defuser every round so everyone holds a bomb once.

## Picking the mission for a team-versus-team night

A fair team night uses missions where luck plays a small part and both teams can finish. Section 1 and Section 2 missions suit most groups. They run on the smaller case, carry no needy modules and give four to seven minutes, so a round stays short enough that the waiting team does not get bored.

The [missions page](/missions) prints each mission's settings on its card, which makes it easy to pick before the night. Two missions, First bite and Button up, deal the identical bomb to every player. Every other mission deals a fresh bomb from its pool, so the two teams get different module mixes under the same rules. Both kinds can work, but they ask for different handling.

A same-bomb mission is the fairest comparison on paper, since both teams solve exactly the same puzzle. It is also the easiest to spoil, because one overheard answer gives the second team the solution. Why those two missions matter for a challenge between friends, and how to protect them, is covered in [why a friends challenge needs the same bomb](/blog/challenge-games-for-friends-online-beat-our-time#why-a-friends-challenge-needs-the-same-bomb).

A fresh-bomb mission cannot be spoiled in the same way, but one team may draw a kinder set of modules. Table for three narrows the gap well: three modules from only three types, so the draw rarely tilts much. Quick snack does the same with four modules in four minutes, and adds pressure. For later rounds, Mixed plate and Rush hour draw from six module types, which spreads the luck wider.

To smooth out the draw, play each mission twice, once with each team going first, and add the two times together. A group that wants one quick decider can pick a same-bomb mission and run both teams at the same moment in different rooms, which the next section covers.

Avoid the late missions for a first contest. A team that cannot finish Double shift or the one-strike final mission will explode, and two explosions leave little to compare.

## Who sits out while the other team runs the mission?

The waiting team should be somewhere it cannot hear a single word of the round. A bomb round is loud. The Defuser describes, the Experts read rules aloud and repeat instructions back, and every one of those sentences is a free lesson for whoever is listening next door.

In one house, send the waiting team to another room with the door shut, or outside. Give them something to do so they do not drift back: a snack, a drink, or the printed manual to study. Studying the manual is fair. Both teams have the same manual, and learning it is part of getting faster. Our [printable manual for rule seed 1](/manual/1) prints cleanly in black and white.

Remote teams have an easier time. Each team creates its own online room, which gets its own five-letter code, and uses its own call. The game has no voice chat of its own, so the separation is as good as the separation between the two calls. Experts in a room see only the timer, the strike count and how many modules are solved, never the bomb itself.

Better still, run both teams at once. With two laptops and two rooms, both teams can start the same mission at the same moment in different parts of the house or on different calls. Neither team waits, so nobody can listen in, and the night moves twice as fast. This is the best way to play a same-bomb mission as a contest.

One person can act as referee. The referee keeps the sheet, checks that each team picked the right mission, and reads both results screens before anyone starts another bomb. On a small group, the referee can be whoever sat out the last round.

## Settling a team result when both teams fail

When both bombs go off, neither run reaches the leaderboard, so the teams compare what they achieved before the end. Count the modules each team solved first. More solved modules wins. If the counts match, the team that solved its last module earlier on the clock takes the round.

Only defusals are ranked on Bomb Appétit's boards. A run that ran out of time or hit the strike limit is still shown on the results screen, which lists every module with either the time it was solved or "not solved", plus a strike count against each one. That screen is the evidence for a failed round, so photograph it or copy it before the next bomb.

Agree the house rule before the first round, not after the first double failure. A rule invented after the fact always seems to favor whoever invented it. Here is one we like, written as an example rather than a game feature:

1. The team with more regular modules solved wins.
2. On equal modules, the team whose last solve happened earlier in the run wins.
3. On a full tie, the team with fewer strikes wins.
4. On a dead heat, both teams replay the mission.

Needy modules do not count in step 1. They cannot be solved, only kept quiet, so they show as needy on the results list.

A double failure also tells you the mission was too hard for this group. Drop back a step for the next round. A night of explosions is less fun than a night of close finishes, even for competitive players. If a round produces one defusal and one failure, the defusal wins, whatever the failing team had solved.

## The team-versus-team mistake: the second team watching the first

Letting the second team watch the first team play is the most common way a team contest goes wrong. On a same-bomb mission, watching hands over the answers outright. On a fresh-bomb mission, it still teaches the module types, the manual pages to open and the pace the clock allows.

Hosts often think watching is harmless on a fresh-bomb mission, since the second team gets a different bomb. It is not harmless. A watching team learns which manual pages to have open, how the first team named a symbol, and which phrasing caused a strike. Each of those is worth seconds, and seconds decide the result.

Spectating is fine once both teams have played. Many groups enjoy watching a replay of the other team's results screen and comparing where each team lost time. Our post on [climbing a leaderboard when only your best run counts](/blog/how-to-climb-a-leaderboard-best-run-counts) covers how to turn that comparison into a better next attempt.

If the room really is too small to split, run the contest across two evenings instead, or let the first team go second next round so the advantage swaps. Fun competitive team games depend on both sides believing the result. A win that came from overhearing feels hollow to the winners too.

When the contest is over, try one round with everyone on the same team. Mixing the two sides on one bomb lets the best describers from each team work together, and it ends the night with a shared win instead of a split one. Head to [Play](/play) to start it.