Keep event replies and potluck plans together

Eight friends have said yes to dinner, two are bringing someone, and three have volunteered dessert in different messages. The host needs a headcount and something green on the table. An invitation with an RSVP form and a shared dish board gives those answers a home.

Use this for a potluck, club gathering, neighborhood meetup, or small team event where replies affect the plan. The useful part is the connection between attendance and preparation: a guest can say whether they are coming and what they will bring without the organizer copying replies into a second list.

The short version

Describe the event details and the reply you need from each guest. Try an RSVP and a dish signup in the example below. Create your invitation app, then check the guest information and collection permissions. Publish its link when the invitation is ready to share.

Give guests a clear reply to make

Write the date, time, and location yourself. Then decide which details the host needs and which should be visible to the whole group. A dietary note and a public greeting have different audiences even when they appear in the same form.

Try this starting request:

Build a potluck invitation for a fictional Saturday dinner on November
21 at 4 PM. Say that the host will share the address separately. Let
guests reply Going, Maybe, or Can't make it, add a first name, plus
ones, and an optional dietary note. Include a shared dish signup with
Mains, Sides, Desserts, and Drinks categories, plus a still-needed list.
Show the confirmed headcount and make it possible to update a reply.
Use sample guests and dishes for testing.

For creating the app, publishing its link, and setting who can read or change records, follow Build a live app on your canvas.

Try the Friendsgiving invitation

The example combines an event invitation, RSVP roster, potluck board, and still-needed list. Its pie limit adds a small but useful constraint: a signup board should help balance the meal, not merely collect names.

1. Add a sample RSVP with a plus one and a dish. Compare the confirmed guest count with the dish list; they describe different parts of the host's preparation.
2. Find an open item in the still-needed list and claim it. Look at how a specific request helps a guest who does not know what to bring.

This is a disposable demonstration. Replies and dish changes reset when the preview reloads. It does not send invitations, reminders, or calendar updates.

Solve the organizer's next question

After a few sample replies, refine the part that would save the host a round of messages:

Add a clear summary for the host showing confirmed guests including
plus ones, undecided replies, and unclaimed food requests. Keep the
existing RSVPs and dish signups.

Before sharing a real invitation, enter a test reply and check exactly what another visitor can see. Decide how much guest information the group needs, then configure collection permissions accordingly. Keep the final event details easy to find so guests can return to the invitation for the plan, not just their own reply.