Running a fair queue on a single pool table
One table, a bar full of people, and a chalkboard that says who is next. It works until it does not, and then it causes more arguments than the game itself.
Why the chalkboard breaks
A written list solves the simple case. Somebody wins, they stay on, the next name goes up. That is fine when the bar is quiet and everyone knows each other.
It falls apart in three predictable ways.
- Nobody owns the pen. The bartender is pouring drinks. The list says one thing, the table says another, and the person who thinks they were next has no way to prove it.
- The winner-stays rule distorts everything. A strong player can hold a table for forty minutes. Everyone waiting watches their evening disappear, and the weaker players stop putting their names down at all.
- The list is invisible from the table. Someone walks to the board to check, comes back, gets it wrong, goes back again. Multiply that by ten people and you have a room full of mild irritation.
None of this is anyone's fault. It is what happens when the record of the queue lives somewhere nobody can see it.
What a queue actually needs
Strip away the app and the software, and a fair queue is four things. Get these right and the implementation does not matter much.
- One authoritative order. There is exactly one list. Not the board, not the bartender's memory, not the regular who has been here longest. One list, and everyone sees the same one.
- Visible position. Every waiting player can see where they are without asking. This single change removes most of the friction, because the arguments are nearly always about uncertainty rather than fairness.
- Rotation rules that are stated up front. Winner stays, or two games and off, or rotate every match. It does not matter which, as long as everyone knows before they put their name down.
- Something that survives the wifi. A queue that stops working when the connection drops is worse than the chalkboard, because now the room is standing around waiting for a computer.
The rules that cause the fewest arguments
There is no single correct rule set, but some choices cause less trouble than others in a typical bar.
| Rule | Effect |
|---|---|
| Winner stays on | Rewards skill, punishes everyone waiting. Fine on a quiet night, miserable on a busy one. |
| Play two, then off | Keeps the table moving and gives weaker players a turn. The most common compromise. |
| Play one, then off | Fastest rotation, most even. Good for short-format nights and busy rooms. |
| Arrival-based only | Ignoring who won entirely. Rarely used, but easy to explain and impossible to argue with. |
The pattern: the more rigid the rule, the fewer the arguments. Ambiguity is what costs you, not strictness. A house rule of "two games then off, no exceptions" will annoy fewer people than "winner stays, unless..." ever will.
The busy-night problem
When there are more than about six people waiting, the queue stops being the main issue and waiting time becomes one. Two things help.
First, tell them the wait. A rough estimate in minutes is far better than "about four more games", because people plan their evening in time, not in games. If you can show position and a running average of match length, the room calms down noticeably.
Second, consider whether the losers should rejoin at the back or leave the queue. In a busy bar, sending losers to the back is usually right. In a small local, letting a regular stay in rotation keeps the table full.
What the app does
Pool Queue was built for exactly this situation: one table, a bar, and a rotation that needs to be visible to everyone.
- The queue order lives in one place, and staff control it with drag-to-reorder when someone needs slotting in.
- Players scan a QR code and see their own position on their phone, so nobody crowds the bar to ask.
- A wall-mounted screen shows the queue to the whole room, which removes the walk-and-check loop entirely.
- It runs offline. If the bar wifi drops mid-game, the queue keeps working and syncs when the connection returns.
It does not invent a rotation rule for you. You pick the house rule and the app keeps it consistent, which is really the whole point.
Last updated 16 September 2026