How to allocate table time in a small club
Paper, WhatsApp, a spreadsheet or fixed sessions: how many members each table allocation system can handle, and where it breaks.
Sharing out a club's tables is a problem of allocating a scarce resource among users whose schedules overlap. In a small club it is usually settled without any written rule, and when demand piles up in two or three slots a week, the lack of a rule hands access to whoever arrives first or whoever is most present at the club.
The usual diagnosis —not enough tables— is almost always wrong. Before budgeting for another table, it is worth measuring real capacity and setting it against demand, because in most cases what is missing is not floor space but a rule for allocating it.
First: how many table-hours there really are
The unit worth thinking in is not "tables" but table-hours: one table available for one hour. It is the only thing that can actually be shared out.
The calculation is simple. Multiply the number of tables by the hours the hall is open each week:
- 6 tables × 4 hours a day × 5 days = 120 table-hours a week
Now demand. Count the active members —the ones who actually turn up, not the ones on the list— and estimate how many hours each wants to play per week:
- 40 active members × 2.5 hours on average = 100 hours of demand
On those numbers there is slack: 120 available against 100 demanded. The feeling of saturation is nonetheless real, and it comes from demand not being spread evenly: in a typical club, around 60% of those 100 hours falls into three two-hour slots. For the rest of the timetable the tables are underused.
That gives the decision rule: if there are spare table-hours overall but a shortage in the busiest slots, the problem is allocation, not capacity. If the overall count falls short too, then it really is capacity, and the way out is longer opening hours or more tables. Only then does an investment make sense.
Two refinements worth building into the calculation:
- An occupied table is not necessarily a table played by two people. In a match it is two; in multiball training it may be one; in doubles or a three-player rotation, more. In a club where three-player play dominates, the real capacity per table goes up and the calculation above is pessimistic.
- Slots are not interchangeable. An evening table-hour and a morning one count the same in the total but are not worth the same in practice. The allocation system only has to cover the contested slots; the quiet ones need none.
The four manual systems, and where each one breaks
None is better than the others in the abstract: each holds up to a certain club size and fails in its own way once past it.
1. The sheet of paper on the wall
A printed grid of days and slots, a pen hanging from a string, and whoever wants a table writes their name.
It works well up to about 25 active members. It is the cheapest system, it shuts nobody out on grounds of age or phone skills, and it has an underrated virtue: the information sits where the problem happens, in plain view.
It breaks in three places. First, members have to be physically at the club to sign up, which favours whoever comes every day and penalises whoever comes twice a week. Second, there is no record: if someone crosses out a name, nothing shows who did it. Third, and most common, the week fills up on Monday and the other members never get a look in.
2. The WhatsApp group
Someone writes "table tomorrow at 7?" and it gets sorted out by consensus in the chat.
It works well up to about 20 members, and only if the group is used for nothing else. It is immediate and needs nobody to maintain anything.
It breaks sooner than paper, modern as it looks. The problem is that a chat has no state: finding out whether a table is free on Thursday means scrolling back through forty messages, and once those are mixed with photos from the last tournament and equipment links, it becomes unworkable. Past a certain volume people stop reading, and once they stop reading the system has ceased to exist, even if the group is still active. It also skews allocation: access to a table tracks how often someone posts in the chat, not need or the order of requests.
3. The shared spreadsheet
A cloud document with one tab per week, editable by everyone or by a few.
It works well up to about 50 members, and it is the first system that really solves remote access: anyone can book from home on Sunday night. It keeps a change history, which settles arguments about who deleted what.
It breaks in two different places. The technical one is simultaneous editing: two people booking the same cell at once, and one of them loses the booking without noticing. The human one is more serious: someone has to set up next week's tab every Sunday. It works as long as that person has the time and the will; the day they go on holiday, the system goes down. A club that depends on a spreadsheet really depends on one person.
4. Fixed sessions by group
Nothing is booked: each slot has a permanent owner. Tuesdays from 19:00 to 20:30 belong to the competition squad, Thursdays at the same time to the beginners' group, Fridays are open play.
It works well in clubs with a structured training programme, at any size. Nothing has to be managed week to week: it is decided in September and reviewed in January. For a club with league teams it is close to essential, because it protects training from open play.
It breaks on flexibility. The member who fits no group —the recreational adult who comes when they can— is left without a place, and that is usually the person who pays the subscription without causing trouble. It also wastes capacity: if the competition squad is eight people with six tables blocked off, tables sit empty while others wait. In practice, almost no club uses this system on its own: it is combined with one of the other three for the open slots.
Summary
| System | Holds up to | Point of failure |
|---|---|---|
| Paper on the wall | ~25 members | Members have to be there to sign up |
| WhatsApp group | ~20 members | No state; whoever posts most plays most |
| Spreadsheet | ~50 members | Depends on one person to maintain it |
| Fixed sessions | Any size | Leaves out the irregular member; wastes tables |
Rules matter more than the tool
A tool enforces rules; it does not replace them. A club that moves from paper to an app without having defined how long a session lasts keeps the original problem intact, just in a different medium.
The four decisions that have to be made, and that are almost never written down:
How long a session lasts. Ninety minutes is usual for open play; sixty if the hall is very tight. The number matters less than its existence: with no set length, whoever arrives first stays until they get tired.
How far ahead tables can be booked. Seven days is a good starting point. Allow more and a few organised members hog the whole month; allow less and nobody can plan. A parallel limit helps a great deal: how many active bookings each member can hold at once, usually two or three. It is the rule that does most to stop hogging.
What happens with no-shows. This is the point that decides whether the system works. A booking that is not honoured and costs nothing is worse than having no system, because it blocks a table someone would have used. The minimum is easy cancellation up to a few hours before, and that whoever fails to show without notice two or three times temporarily loses the right to book ahead. There is no need to be harsh; there is a need for a consequence.
What takes priority. Coached training ahead of open play, and competition ahead of both on match days. It is worth writing this down before the first conflict, not after. If the club runs an internal league, its rounds belong here: they are the clearest case of a slot that is not up for negotiation.
Three questions that always come up
Can members book for someone else? It is worth allowing —the one who books answers for both— but the session should count against the booker's allowance only, not both. Otherwise two organised members block twice as many slots.
What about those who turn up without booking? Any table not booked on the hour goes to whoever is in the hall. This is what stops the system from pushing out the member who comes when they can, who is usually the majority.
Does the club charge for bookings? In a members' club, no: the subscription already pays for access. Charging per slot is for hiring tables out to non-members, which is a different use and is best kept separate from the start so the rules do not get mixed up.
The four rules fit on half a page. Drafting them, having the committee approve them and posting them in the hall resolves a large share of the conflicts at no cost. They are also the settings any later automated system would need, so the work carries over.
The free slot nobody uses
So far the problem has been sharing out what was planned. There is a second problem, less obvious and more costly than it seems: capacity that frees up without warning.
A training session cancelled because the coach is ill, a group that finishes half an hour early, two players who do not turn up for their session, a table left free because the internal league finished early. In every case, capacity appears in a slot that is normally saturated —that is, the club's scarcest resource— and in most clubs it is lost entirely.
It is not lost because nobody wants it. It is lost because by the time the information reaches someone who could use it, the slot has already gone.
Why a manual heads-up never arrives in time
The usual mechanism is the WhatsApp group, and it fails because of its form, not because of how it is used. A message saying a training session is off sets off a chain of questions —what time, how many tables, who is going— that takes a good half hour to resolve, by which point the slot has started. Three reasons:
- The chat has no state. It cannot answer the only question that matters, "what is free right now?": the answer has to be pieced together by scrolling back, and each reader pieces it together separately.
- The message goes unseen. Whoever is at work sees it two hours later; whoever muted the group, never. The information does not stay available to look up.
- Nobody knows who took the slot. Either two people turn up for the same table, or nobody does because each assumed the other was going.
The result: a slot freed up with less than 24 hours' notice is almost never filled, even when there are members who would have gone.
What can be done without tools
Two measures that reduce the loss without changing system:
A channel just for free slots. A separate group, with no conversation, where the only posts are "Tuesday 19:00–20:30, 2 tables free" and the only replies are "I'll take it". Because it is not mixed in with other messages, people look at it. It is the bare minimum of having state.
An automatic release rule. Whoever has not turned up within the first ten minutes loses the table, and it becomes available to whoever is in the hall. It turns an absence into recovered capacity without anyone having to announce anything. It is worth writing down alongside the four rules in the previous section.
Neither solves getting word, two hours ahead, to people who are not at the club: there, a manual system cannot move faster than the person running it.
When manual stops being enough
The systems above do not fail all at once. They degrade, and there are four fairly reliable signs that the limit has been reached:
No-shows cost nothing and everyone knows it. When booking without turning up is free, tables show as taken while they sit empty. It cannot be policed by hand, because it requires someone to check attendance slot by slot.
More than one group is treading on another. While there is only open play, paper holds up. As soon as coaching, competition, outside hire and individual members coexist, each with different rules, no manual system stays consistent.
Someone spends hours refereeing. If there is a person at the club who every week settles table disputes, prepares the sheet and answers messages, the club is already paying for a system. It pays in a volunteer's time, which is the scarcest resource it has.
Unexpected free slots go to waste. The sign from the previous section, and the easiest to measure: count for a month how many slots were freed and how many ended up taken. If the gap is noticeable, the club is losing capacity it has already paid for.
When two of the four appear, the next step is for the system itself, not a person, to handle allocation. What changes is not that there are rules —those are already written— but that the state of the hall is published and keeps itself up to date: anyone can check what is free without asking, a cancellation opens the slot instantly, and there is a record of who took it.
How Open-TT handles it
Open-TT has a table booking module designed for exactly this point, free for the club and for its members. It runs in the browser with nothing to install, and each part matches something covered above:
- The hall timetable. The club organiser adds the tables and sets a weekly template: which table is available, on which day and in which slot. From there, the system generates the free tables for the coming weeks on its own.
- The slots that are not up for negotiation. Coaching, training sessions or a league round are blocked out in the calendar, and those tables are no longer offered for booking.
- The question "what is free now?". Members answer it from their phone and take the slot they want. If they cancel, the table shows as free for everyone else at that moment, without anyone having to post in the group. Bookings close fifteen minutes before each slot, so there are no last-minute changes.
- No-shows. The organiser marks whoever booked and did not come. The system counts each member's cancellations and no-shows over 30 days and flags anyone who goes over the limit the club has set. The consequences are for the club to decide.
- Members. The organiser links the club's players to the venue from the admin panel.
The four rules from earlier remain the club's business: the length of each slot and how many days ahead bookings open are set in the template, but priority between groups and what happens to those who fail to show are decided by the committee, not the system. The details and sign-up are on the table booking page for clubs.
The scope of this step is worth keeping in proportion: in a twenty-member club with a sheet on the wall that works, automating adds nothing. A booking tool solves a coordination problem that only appears beyond a certain size and a certain mix of uses.
What to do this week
Four steps, in order:
- Do the table-hours count. Ten minutes. It shows whether the problem is capacity or allocation, and avoids buying a table the club does not need.
- Draft the four rules —length, notice, no-shows, priority. Get the committee to approve them and post them in the hall.
- Pick the system that matches the club's size from the table above, without skipping steps because one looks more modern.
- Set a review date three months out, and meanwhile keep count of slots freed and slots filled. If two of the four signs from the previous section show up at the review, it is time for the next step.
The order matters: the count decides whether the problem is capacity or allocation, the rules define what gets shared out, and only then does it make sense to choose the tool that shares it out. Reversing that order —changing tool before writing the rules— reproduces the same problem in a different medium.