23 people. Three bring potato salad. Nobody brings dessert.

The problem with WhatsApp and spreadsheets

A BBQ for 23 people usually means one WhatsApp thread generating 80 messages in two days. "I'll bring a potato salad." "Oh, I was going to bring salad too, what should we do?" "I can bring something else." Three days later, still no clear answer on who is bringing what.

The classic problem at spontaneous family and friend grills: at least two people accidentally bring the same thing. Three bowls of salad, zero dessert. Nobody gets upset, but it happens every single time.

On top of that comes the address chaos. You share the location once in WhatsApp, four days later three people privately message you asking for it again. You repeat yourself, copy the entry from your calendar, all in the middle of the chaos right before the first guests arrive.

With larger summer gatherings it gets even messier. Who said yes? Who said maybe? Who is only coming "if the weather cooperates"? Three categories that simply cannot be sorted inside a chat thread.

How it works with events

A BBQ party is at its core three lists: who is coming, who is bringing what, and who is a last-minute yes or no. With events, those are three tabs in one app. No threading, no sticky notes.

Clear RSVPs via one link

Instead of asking 23 people individually over WhatsApp, you post the link in the family chat or send it as a direct message. Guests open it, see the date, time and address, and RSVP with one click. The list fills up in front of your eyes.

Three statuses are possible: yes, no, maybe. You see at a glance how many people to expect. For a typical summer gathering with 23 invites: 16 confirmed, 4 maybe, 3 declined, one no response yet. You plan for 18 to 20 people, which is a much more honest estimate than any WhatsApp gut feeling.

Bring list with categories

Here is the key trick: instead of an open list, you create categories with slots. Example structure for a BBQ with 20 guests:

• Meat: 2 slots (typically one for sausage, one for steaks)
• Vegetarian option: 1 slot
• Salads: 3 slots
• Sides (bread, corn on the cob, foil potatoes): 2 slots
• Dessert: 2 slots
• Drinks: 2 slots (non-alcoholic plus alcoholic)
• Tableware and napkins: 1 slot

Thirteen slots for 20 guests. Everything else guests bring for themselves or you provide. Once a salad slot is full, additional guests cannot reserve a fourth salad. The system blocks it. Duplicates are eliminated by design. The same slot logic works with adjusted categories for winter occasions; see the New Year's party planning page for a version with sparkling wine slots and midnight programming.

Message board for last-minute updates

Weather change, address update, start time pushed back: everything goes through the message board. One post reaches all guests via push notification. In a WhatsApp thread, that same update would be buried under 80 messages. Here it sits at the top of the event, visible to everyone.

Photo album as a shared collection

After the evening, everyone has somewhere between 5 and 30 phone photos. Instead of posting them one by one in the WhatsApp thread and losing them three weeks later: photo tab in the event, everyone uploads, you download a ZIP for your personal archive.

Guests need no account

The most important point for a relaxed family BBQ: no account, no required email address, no app installation. One click on the link, one RSVP, done. The first three events are free, no trial period, no credit card.

Step by step

Example: 20 guests, backyard BBQ, a Saturday in July, living room as a Plan B if it rains.

1. You create the event: type Summer Party, date July 12, 4:00 PM, address with house number and buzzer name. Note the Plan B for rain in the description field.
2. You build the bring list with the 13 slots from the example above. Name slots clearly: not "Salad 1" but "Salad (green or mixed)" and "Salad (potato or pasta)". Specific labels help.
3. You share the link in the family chat. Anyone who does not use WhatsApp gets it by email. The link works everywhere, no account required.
4. One week before the date: the system automatically sends a reminder to everyone who has not yet RSVPed. Response rates typically climb to around 90 percent.
5. Three days out, you post a quick note on the message board: "Take bus 71 to stop XY, then two minutes on foot." Push notification to all confirmed guests.
6. On the day itself: check the weather. If rain is coming, post an update to the message board with Plan B. Guests see it immediately. You do not have to type 16 individual WhatsApp replies.
7. Evening winds down, grill cools off, album fills up. Two days later you download the ZIP, done.

What you actually need

The checklist above covers the standard situations. Three points matter most.

First, a weather backup plan. A BBQ without a Plan B is a BBQ with a 50-percent chance of stress. Write in the description: "If it rains we move inside, same address, just ring the bell." That reassures guests without forcing you to take twelve phone calls on the day.

Second, a bring list with slots, not an open one. An open list leads to pile-ups on the popular items (salad) and gaps on the unpopular ones (tableware, sides). Clear slots force a fair distribution.

Third, a complete address. Street, house number, buzzer name, and an optional directions note. At city summer parties, guests without a buzzer name often cannot find the entrance on the first try. Being specific up front saves 20 minutes of stress on the day itself.

Once everything is set up, preparing a BBQ party for 20 guests takes about 25 minutes. The system handles the rest: reminders, confirmations, bring list updates, weather push, photo album after the evening.

Special case: multi-generational family gathering

Organizing a BBQ for three generations brings two specific challenges: a higher technical barrier for older guests and different expectations around noise levels and timing.

On the technical side: parents and grandparents are generally less comfortable with apps than younger adults. In practice, the web link works without any friction because it opens like a normal website. Guests who have never installed an app do not have to install one. Recommendation: write in the family WhatsApp chat "Click the link, one click to RSVP, done." Be explicit about what to do. About 90 percent of grandparents manage on their own.

On the content side: a three-generation BBQ needs a time structure. Start no earlier than 2:00 PM, since older guests tend to arrive around midday. Main food around 5:00 PM, which fits the usual dinner rhythm of seniors. Ending after 10:00 PM is uncommon, since grandparents often want to head home earlier. Build this structure into the event description so all generations know when to show up.

For large family gatherings that include young children: mention shade and restrooms explicitly. Parents with toddlers often decide whether to attend based on exactly those two factors.

What is different with spontaneous grills

Not every BBQ is planned three weeks in advance. Spontaneous Thursday evenings with "anyone up for a grill tonight?" work differently. Here the bring list matters less; the link matters more.

The typical spontaneous BBQ: 10 to 15 people, an evening get-together, three hours of lead time. You create the event in five minutes, post the link in the family or friend chat. Bring list trimmed to the minimum: one slot for a side dish, one for salad, one for drinks. That is enough, because most guests will bring whatever they have at home anyway.

The advantage: within 30 minutes you can see who is coming. Three statuses, a clear list. In a classic WhatsApp thread, those same 30 minutes would have produced 18 messages, 14 of which added no useful information.

For very last-minute spontaneous grills (less than six hours of lead time), the push notification is the most powerful lever. Anyone who has opened the event link even once gets an immediate notification. That works better than any WhatsApp message because it does not get buried in the chat stream.