Every Tuesday at 7pm. Set it up once, runs by itself.

The problem with WhatsApp and a fresh invitation every week

A weekly board game night, a Tuesday training session, a monthly book club. The pattern is the same: you create a WhatsApp group, you ask "who is coming this week" every Sunday, three people answer right away, four answer Tuesday morning, two never answer at all. You count zero against twelve and hope it adds up to enough players.

After a while, the WhatsApp group fills up with old polls, photos, off-topic chatter and the actual attendance question gets lost. New members join in the middle of the season and have no clue what is going on. Old members drop off silently, you only notice three months later.

The fundamental issue: a WhatsApp group is a chat, not a structure. It cannot tell you who is in the group right now, how many people came last week, who has missed three sessions in a row, or how many are on the bring list for next Saturday. You have to count by hand every time.

How it works with events

A recurring event is, structurally, two things: a group with members and a schedule that produces sessions. Set them up once, then everything else happens automatically.

Group as the container

The group holds your members. You give it a name like "Tuesday training" or "Boardgame night Frankfurt" or "Yoga circle". You invite members once, by sharing the group link. They open the link, enter their name, and they are in. No password, no email loop, no app install required.

For a typical sports team with 18 members, all of them join in the first week. After that, the group is stable. New members come in two or three times a year, when someone moves to the city or a friend brings a friend.

Recurring schedule with weekly, biweekly or monthly cadence

Inside the group, you add a recurring event. Set the cadence: every Tuesday, every other Saturday, the first Friday of each month. Set the time and the location. Set the season end if the group pauses in summer or winter.

The system then generates each session as a separate event. Members see "Tuesday training, May 5" as one event, "Tuesday training, May 12" as the next. Each session has its own attendance list, its own bring list if you need one, its own message board for last-minute updates.

Attendance per session

This is the part that no chat group can replicate cleanly. Each session has a yes / no / maybe button for every member. Members confirm in two clicks: open the link, click yes. The list updates live, you see at any moment how many will be there.

For a sports team needing six players to play, you can set a threshold: if fewer than six confirm 24 hours before, the session is automatically marked as cancelled and everyone gets a notification. No more "how many are coming, should we cancel" rounds in the chat.

Bring list for shared gear

Who washes the jerseys this week? Who brings the balls, the cones, the music speaker? The bring list works the same way as in single events: you add items, members reserve their slot. For a weekly training, the bring list often repeats: same jerseys, same balls, same person every week. You can set defaults so members do not have to re-reserve every time.

Reminders without lifting a finger

One day before each session, the system sends a reminder to anyone who has not yet confirmed. Push notification if the member uses the native app, otherwise email. Members who confirmed yesterday get nothing, members who said no get nothing, only the undecided get a nudge.

In practice this lifts the response rate from around 60 percent to 95 percent without any work on your side. For a club with 18 members, that means seeing 17 confirmed answers by Tuesday morning, instead of guessing.

Step by step

Example: a recreational soccer team, 20 members, weekly training every Tuesday from 7pm to 9pm, season runs from September to June.

1. You create a group called "Tuesday Soccer". Open-ended mode for now, you can add a season end date later.
2. You share the group link in the team chat once. Twenty members join over the next four days, that is normal. The slowest joiners are usually two who only open WhatsApp on weekends.
3. You add a recurring event inside the group: "Training", every Tuesday, 7pm to 9pm, location field set to your usual pitch. The system generates the next 40 sessions until June.
4. You set the attendance threshold to 8. If fewer than 8 confirm by Tuesday noon, the session auto-cancels with a notification to everyone.
5. You add a bring list with two items: "Wash jerseys this week" and "Bring music speaker". Both repeat each week with a default assignment that rotates through five members.
6. Each Sunday evening, the system sends a reminder to anyone who has not confirmed for the upcoming Tuesday. Most members confirm within a few hours.
7. After each session, you take three or four photos. They go into the group photo album. End-of-season, you have around 200 photos for a quick highlight reel.
8. End of June, the season ends. The group stays, the schedule pauses. In September, you reactivate with one click.

What you actually need

Four points make the difference between a recurring schedule that runs itself and one that drains your time.

First, a clear cadence. Weekly is the easiest pattern because everyone remembers it. Biweekly is fine if you communicate it clearly. Monthly is fine for casual meetups but tends to get forgotten. Avoid irregular cadences like "every other Tuesday except holidays", they create confusion and missed sessions.

Second, a low-friction join flow. Members should be in the group within two minutes. The link approach achieves that. Asking for an account creation upfront cuts your signup rate by about 40 percent, based on what we see in the data.

Third, a co-admin. You will go on vacation, you will get sick, you will miss a session. A co-admin can send reminders, cancel sessions and update the bring list while you are away. For a club, this is non-negotiable. Pick someone who is reliable and has organizing instincts.

Fourth, an attendance threshold. For sports teams, board game nights or anything that needs a minimum quorum, set the threshold and let the system auto-cancel when it is not met. Saves the awkward "should we still meet" chat every week.

Once these four are in place, the group runs itself. Your time investment per week drops to under five minutes: read the attendance list, post a quick note if needed, done. For one-off team events that fall outside the recurring rhythm, the team event guide covers carpool and task setup. For occasional birthday parties or family events the group might host, see the birthday guide.

Different recurring formats

Three recurring formats show up most often in practice, each with slightly different needs.

The first is sports and exercise: training, yoga, running groups. Weekly cadence, fixed location, fixed time. Attendance threshold matters, bring list matters less unless gear rotates. Photo album is a nice addition for end-of-season summaries.

The second is hobby and culture: board game night, book club, choir rehearsal, language tandem. Weekly or biweekly cadence. Attendance is more about social commitment than quorum. Bring list often used for snacks, drinks or shared materials. Message board is the most-used feature here.

The third is community and family: parents' group, neighborhood meetup, monthly family dinner. Monthly or quarterly cadence. Attendance threshold less relevant, since the group runs regardless. Bring list important for potluck dynamics. The group photo album turns into a long-term family or community archive.

Pitfalls when running a recurring group

Three issues show up regularly with recurring groups. Avoiding them keeps the group healthy across multiple seasons.

First, members who silently drop off. After three or four missed sessions, a member is effectively out. Without a system, you only notice six months later. With the attendance dashboard, you see it after two missed sessions. A friendly direct message at that point keeps half of them in. The other half had already mentally left, but at least the conversation is honest.

Second, bring list fatigue. If the bring list repeats every week and the same person always brings the same thing, members stop checking it. Solution: rotate the bring list every four weeks. Person A brings drinks weeks 1 and 5, Person B weeks 2 and 6, etc. Predictable but not boring.

Third, the announcement-only chat. If the group chat fills up with off-topic conversation while important announcements get lost, consider muting or splitting. The events message board is read-only for everyone except admins, which keeps important information visible. Casual chat lives in WhatsApp, structural information lives in the event group.