Write the dishes and the numbers — three mains, four sides, six desserts, drinks — and share the link. Members claim a dish with their name; a dish closes once enough people have it. The kitchen committee sees what is still missing without walking the clipboard around after the service.
A list for a fellowship lunch of about sixty people. Each line has a number; guests see what is still needed and claim from the same link they RSVP with.
| Needed | Claimed so far | |
|---|---|---|
| Main dishes | 6 | ✓6 — closed |
| Sides and salads | 8 | ~5 — 3 still needed |
| Desserts | 6 | ~4 — 2 still needed |
| Bread and rolls | 2 | ✓2 — closed |
| Drinks and ice | 2 | ✗0 — 2 still needed |
Illustrative. The numbers are whatever the kitchen committee sets; a line closes automatically when its number is met.
The link goes in the bulletin, the email and the group chat. Members who don’t use apps open it in a browser; members who do get it in the community’s events tab with a push notification.
The same link takes the RSVP — adults and children counted — so the dish count and the headcount agree. If forty households say yes and only two desserts are claimed, you know on Wednesday, not on Sunday.
Free · no account · about a minute
Yes. Quantities can be as large as you need, and the list closes each dish when covered.
Yes, if the organizer allows it.
No. Members open the link in a browser and claim with their name.
Yes. In a community, the hospitality team and the office can all edit the event.