Book clubs, rehearsals, games nights: scheduling the weekly gathering

From the outside these three look like the same problem: a small group, a recurring evening, a date to agree on. They are scheduled with the same availability poll, and they fail in three completely different ways. Knowing which one you are organizing tells you how far ahead to ask, how many dates to offer, and whose answer actually counts.

A reading group has a cadence before it has a date. One chapter a month, one book a quarter: that rhythm is the real constraint, and the evening itself can slide by a week without doing any damage. What does the damage is asking too late. A date agreed five days in advance leaves nobody time to finish the reading, and half the room arrives having skimmed the last three chapters.

1. 1

   Send the poll four weeks out

   Far enough that the book can be read, close enough that people still know their calendar. A yes given for three months out is worth very little.

2. 2

   Offer three or four evenings

   Two in the last week of the month, two in the first week of the next. A single busy week then does not rule everybody out at once.

3. 3

   Announce the reading with the date

   The chosen evening and the chapters in one message. The poll settles when; the announcement is what tells people what to read.

The “Date” type is the one for this: whole evenings, with the hour already settled by habit. If the group reads a long book over a weekend away, the “Period” type covers several consecutive days instead.

A choir, a band, an amateur theatre group: the concert or the opening night is printed on something, and no poll is going to shift it. The question is never which date, it is which of the eight Tuesdays left you can actually fill. You are rationing weeks, and every one you lose to a half-empty room is one you do not get back.

Attendance here is not counted per head. A run-through with ten of your twelve singers is useful; the same rehearsal with both sopranos missing is not. So poll the people who have to be in the room for that specific rehearsal (the section, the leads, the four musicians working on one piece), and read the table knowing which absence hurts and which one does not.

Rehearsals are scheduled on hours rather than on days, so the “Time slot” type fits them: precise hours, several per day if you want a sectional in the afternoon and a full run in the evening. Green marks a slot every single person ticked; amber marks the next best one after it, which is the one you keep in reserve.

Nobody ever cancels a games night. It simply stops being proposed. One week someone is away, the next week the message goes out on the Thursday and it is already too late, and then three weeks pass before anyone asks whether the thing is still running. There is no deadline to miss, which sounds relaxing and is in fact the whole problem: a habit with no external date decays unless something regular pushes it.

That something can be a poll, as long as it goes out on a rhythm rather than when someone remembers.

• Tie the poll to a fixed trigger. “The first poll of every month”, sent by the same person. The evening you end up with moves around; the sending never does.
• Keep it short. Four or five evenings across the next three weeks. A poll that can be answered in ten seconds comes back the same day.
• Send it even when the month looks bad. A bad month with one possible evening still gives you one evening. Skipping the poll gives you none, and skipping it twice ends the group.

The same discipline is what keeps any weekly game alive. A long campaign is the hardest version of it, because the table only works at full strength: finding a weekly slot for a role-playing group is the same mechanism with less room to manoeuvre.

Almost every club has two rings. A core of five or six who come every time and whose absence cancels the evening, and a wider circle of drop-ins who come when it happens to suit them. The mistake is to send one link to everybody and treat the result as a decision.

The results table counts one column per voter, with no weighting at all. A drop-in who has come twice this year carries exactly as much as the person who hosts every session, so twenty casual answers can bury the four that matter. Poll the core, then announce the chosen date to the rest: the drop-ins lose nothing, because they were never going to be the reason a date was rejected.

If someone votes who should not have, you can remove that participant from the table and the highlight is recalculated without them. It is worth doing before you read the result rather than after you have announced it.

Every extra option is one more decision for every participant, and the answers scatter as you add them. The right number depends on which of the three habits you are scheduling.

• Book club: three or four evenings, spread over two weeks and sent four weeks ahead. The group is small and the date is flexible, so a narrow choice is enough.
• Rehearsal: every week that is left, because the question is which ones you can fill, not whether one works. Eight rows is fine here; the table is a planning grid, not a vote.
• Games night: four or five evenings in the next three weeks. Any further out and people answer about a calendar they cannot see yet.

Whatever the number, say when you will close it. There is no automatic closing date, so one line in the message does the work: “I’ll pick the evening on Sunday”. Without it the last two people answer on the day of the gathering, or not at all.

A gathering held at home has a participant nobody thinks to list: the host. Their availability is not one opinion among six, it is a veto: a date that works for everyone except the person whose table you are sitting at is not a date. Put the host in the poll first, and if the hosting rotates, ask whoever is hosting that round before you send anything to the others.

When the venue is a room you book instead (a hall, the back room of a café, a library meeting room), the constraint moves upstream. Check what the room has free, then offer only those dates. Polling six people on four evenings and discovering that two of them were never available is how a group ends up voting twice.

Reading groups that meet online have one less problem and one more: there is no room to book, but there may be several time zones in the group. Each person sees the dates and hours converted into their own, with the time zone in use shown next to the table, so nobody is doing arithmetic before answering. Once the evening is settled, everyone adds it to their own calendar straight from the highlighted row, as an iCalendar file, in Google Calendar or in Outlook Web. A habit that lives in people’s calendars is the one that survives a busy month.