Scheduling a recurring meeting without a recurring thread

Something you run every week should be the easy part. The group is the same, the room is the same, the agenda is half written before you start. And yet the question comes back: can everyone do Tuesday? No? Wednesday then? Each message proposes one date, each reply answers the message before last, and by the time three people have written back, nobody can say what was actually agreed.

The thread never ends because it asks a one-off question about a thing that happens again. Tuesday the 4th is not the problem. Tuesdays are the problem, and nobody is being asked about Tuesdays.

The usual reaction is to go wide: one availability poll holding every date of the next six months, sent once, and the group scheduling question closed for good. It never survives contact.

• Nobody finishes it. Thirty rows is thirty decisions. People tick the first week, promise themselves they will come back, and do not.
• It is stale by week three. A yes given for March is worth very little in January: most people do not know their calendar beyond two months.
• The answers scatter. Thirty dates ticked at random by eight people point to no clear winner, and the table has nothing to highlight.

A long poll and a long thread fail for the same reason. Both treat a regular meeting as a series of unrelated dates, when what the group needs is one decision that holds.

“Which Tuesday suits you?” and “which evening works for you every week?” are two different questions, and only the second one is worth asking. Ask it once, on one representative week, and read the winner as a weekday and an hour rather than as a date.

1. 1

   Pick an ordinary week

   Not a school holiday, not the week of the long weekend. You want the week that looks like all the others, because its answers are the ones that will keep being true.

2. 2

   Offer four to six slots inside it

   Use the “Time slot” type, which asks for precise hours: two evenings, one lunchtime, one early morning. Several slots can sit on the same day.

3. 3

   Say in the title that it recurs

   “Book club: which evening every week?” tells people to answer as a habit and not for one night. The wording does the work no feature can do for you.

4. 4

   Announce the slot once, then stop asking

   One message with the weekday, the hour and the first date. From there the meeting lives in everyone’s calendar, not in a thread.

Green marks the slot every single voter said yes to; amber marks the next best one, which is your fallback if the group loses someone. If your team is spread across countries, nobody has to convert anything: each reader sees the hours in their own time zone, shown next to the table, and the displayed zone can be changed in the settings menu.

Sometimes the slot genuinely cannot hold: shift work, a rota, a committee whose members travel. Then you do poll dates, but a month at a time, never a year. The rule of thumb: the poll should never contain a date that people cannot honestly answer for.

A slot that keeps being re-opened is worth nothing: people stop putting it in their calendar because they assume it will move again. So hold it by default, and re-poll only when the team availability behind it has actually changed.

• The membership changed. Two people joined, one left. The old unanimous row was unanimous for a group that no longer exists.
• A term or a season ended. September and January rewrite everybody’s evenings. A class, a support group or a club night is worth re-polling at those two moments and at no other.
• Someone changed job, shift or childcare. One person with a structurally different week is enough reason: they will otherwise miss every single session.
• Attendance dropped three cycles in a row. People vote with their feet long before they tell you the slot is wrong.

One absence is not one of those. A single person missing a single week is a message, not a poll: move that one session or let it run without them.

Recreating the poll each cycle is less work than it sounds, and it is worth doing with a title convention the group learns to recognize: “Stand-up November”, “Stand-up December”. Same shape, one word different. People see the link in the channel and know what it is without opening it.

Neither you nor the participants need an account, so a new poll each month costs nobody a sign-up. Participants give a name, and an email only if you ticked the option asking for one. Signing in with Google is optional and does exactly one thing: it lets you find your own polls again from another device, which matters more when there is a new one every month.

Once a row is highlighted, Add to calendar sits on it and offers iCalendar (.ics), Google Calendar and Outlook Web. If you collected participants’ emails when creating the poll, the calendar event can invite the people who said yes. And a date that lives in a calendar is a date you will not be asked about again.

Most of them, once the slot is set. A recurring meeting that already sits in everyone’s calendar needs no vote, no link and no thread: it needs an agenda. Polling it again every week is how a group starts resenting the thing.

Keep the poll for the three moments that deserve it: the first time you look for the slot, the day the group changes, and the one-off sessions that fall outside the rhythm: the away day, the end-of-term dinner, the extraordinary committee. Those are plain date polls, and a weekly club night is the same exercise one notch smaller. For anything spanning several days, a seminar or a residential weekend, the “Period” type covers consecutive days instead of single ones.