TabletopTourney · Fictional worked scenario

Seeing the One-Table Bottleneck for Six Players

This is an invented planning exercise, not a customer event or testimonial.

Background and constraints

A fictional host has six players but only one usable table. A complete round robin may be mathematically valid yet too long for the booking.

Exact tool inputs

names	Ari Bea Cleo Dev Em Fox
format	Round robin
tables	1
groups	1

Actual generated result

names

Ari
Bea
Cleo
Dev
Em
Fox

format

Round robin

round

losses

Ari: 0
Bea: 0
Cleo: 0
Dev: 0
Em: 0
Fox: 0

history

round
1
a
Ari
b
Fox
sa
1
sb
0
table
1
wave
1
winner
Ari
round
1
a
Bea
b
Em
sa
1
sb
0
table
1
wave
2
winner
Bea
round
1
a
Cleo
b
Dev
sa
1
sb
0
table
1
wave
3
winner
Cleo
round
2
a
Ari
b
Em
sa
1
sb
0
table
1
wave
4
winner
Ari
round
2
a
Fox
b
Dev
sa
1
sb
0
table
1
wave
5
winner
Fox
round
2
a
Bea
b
Cleo
sa
1
sb
0
table
1
wave
6
winner
Bea
round
3
a
Ari
b
Dev
sa
1
sb
0
table
1
wave
7
winner
Ari
round
3
a
Em
b
Cleo
sa
1
sb
0
table
1
wave
8
winner
Em
round
3
a
Fox
b
Bea
sa
1
sb
0
table
1
wave
9
winner
Fox
round
4
a
Ari
b
Cleo
sa
1
sb
0
table
1
wave
10
winner
Ari
round
4
a
Dev
b
Bea
sa
1
sb
0
table
1
wave
11
winner
Dev
round
4
a
Em
b
Fox
sa
1
sb
0
table
1
wave
12
winner
Em
round
5
a
Ari
b
Bea
sa
1
sb
0
table
1
wave
13
winner
Ari
round
5
a
Cleo
b
Fox
sa
1
sb
0
table
1
wave
14
winner
Cleo
round
5
a
Dev
b
Em
sa
1
sb
0
table
1
wave
15
winner
Dev

matches

round
1
a
Ari
b
Fox
sa
1
sb
0
table
1
wave
1
round
1
a
Bea
b
Em
sa
1
sb
0
table
1
wave
2
round
1
a
Cleo
b
Dev
sa
1
sb
0
table
1
wave
3
round
2
a
Ari
b
Em
sa
1
sb
0
table
1
wave
4
round
2
a
Fox
b
Dev
sa
1
sb
0
table
1
wave
5
round
2
a
Bea
b
Cleo
sa
1
sb
0
table
1
wave
6
round
3
a
Ari
b
Dev
sa
1
sb
0
table
1
wave
7
round
3
a
Em
b
Cleo
sa
1
sb
0
table
1
wave
8
round
3
a
Fox
b
Bea
sa
1
sb
0
table
1
wave
9
round
4
a
Ari
b
Cleo
sa
1
sb
0
table
1
wave
10
round
4
a
Dev
b
Bea
sa
1
sb
0
table
1
wave
11
round
4
a
Em
b
Fox
sa
1
sb
0
table
1
wave
12
round
5
a
Ari
b
Bea
sa
1
sb
0
table
1
wave
13
round
5
a
Cleo
b
Fox
sa
1
sb
0
table
1
wave
14
round
5
a
Dev
b
Em
sa
1
sb
0
table
1
wave
15

champion

null

standings

name
Ari
points
15
played
5
for
5
against
0
rank
1
name
Bea
points
6
played
5
for
2
against
3
rank
2
name
Cleo
points
6
played
5
for
2
against
3
rank
2
name
Dev
points
6
played
5
for
2
against
3
rank
2
name
Em
points
6
played
5
for
2
against
3
rank
2
name
Fox
points
6
played
5
for
2
against
3
rank
2

tables

waves

Planning process

The organizer generates all fifteen matches and reviews the table-wave assignments. With one table, every match needs a separate wave. The host multiplies the actual game length by fifteen and adds transitions before deciding whether to keep the format.

Result explanation

Pairing correctness does not create playing capacity. At fifteen minutes per game, playing alone would require 225 minutes. The planner’s wave count exposes the bottleneck instead of pretending simultaneous matches can share the same table.

Alternative

Use two groups of three with a final, or a knockout, if those formats fit the group’s goals and published rules.

Execution notes

Confirm actual table availability and game duration. Do not cut a game off under an unannounced scoring rule.

Continue planning

Open TabletopTourney

How to Organize a Cosplay or Board Game Gathering

An Eight-Player Knockout with Four Opening Tables

FAQ

Are these real event records?

No. All people, dates, constraints and planning amounts in this scenario are fictional inputs supplied to demonstrate a workflow.

How can I try this plan?

Open the linked tool, enter the exact inputs above, review the result and save it locally. Export a backup if you want a separate copy.