Describe your event, invitation rules, and the details you need from each party. Makeform turns that brief into a guest list form that collects attendance, named guests, plus-ones, meal choices, accessibility requests, and contact details in one organized response flow.
Send guest responses to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose the event closest to yours, adjust the prompt, or send it to the Makeform builder. Each structure is an example you can edit before publishing.
Audience
Invited households responding to a wedding invitation
Format
Party-based RSVP with names and meal choices
Prompt size
430 chars
Example form structure
Party-based RSVP with names and meal choices
Invitation name and primary contact
Will anyone in your party attend?
Names of all attending guests
Meal choice for each guest
Dietary, accessibility, or shuttle needs
Suggested routing tags
Attending
Not attending
Needs follow-up
Collect one primary contact per invitation party and ask for every attendee's name separately. That keeps household responses easy to contact without turning the final headcount into guesswork.
Step 1
Invite
share one RSVP link with invited guests
Step 2
Collect
capture attendance and every guest name
Step 3
Organize
separate attending, declined, and incomplete replies
Step 4
Prepare
use final counts for seating, meals, and check-in
A reliable headcount
A simple attending-or-not question misses who is actually coming. A structured guest list form connects each response to a primary invitee, names every attendee, and captures the practical details your venue, caterer, and check-in team need.
Ask for a primary contact, then collect each attendee's full name in a repeating group. Your headcount and check-in list come from named people, not an ambiguous response such as me plus three.
Use conditional paths so attending guests see meal, transport, and accessibility questions while declined guests can finish quickly. Plus-one fields appear only when the invitation permits one.
Store attendance, party size, guest names, meal choices, and requests in the same submission. Filter the response list instead of reconciling email replies, messages, and a separate spreadsheet.
Designed around the event
Start with the event pattern that matches your invitation style, then change the language, fields, and response paths before you share the form.
Manage households, permitted plus-ones, children's names, entrée selections, shuttle seats, and accessibility requests without making every invitee answer irrelevant questions.
Collect organization, role, work contact, approved guest details, seating preferences, and consent to receive event updates in a professional registration flow.
Keep the response short on a phone while still collecting family member names, total party size, allergies, parking needs, and an optional note for the host.
Route guests by ticket or invitation type, identify minors, record accessibility needs, and send volunteer interest into a follow-up path without maintaining another signup list.
Build your RSVP workflow
Describe who is invited and what the planning team needs to know. Then refine the generated guest list form, share it, and turn responses into a practical event-day view.
Tell Makeform the occasion, date, audience, RSVP deadline, and whether invitations cover individuals, households, or named plus-ones. Include every choice your planning team must count.
Edit the event language, mark essential contact and attendance fields required, add your real meal options, and hide follow-up questions when a guest declines or has no plus-one.
Send the public link by invitation email, message, or event page. Use confirmation text to repeat the submitted party names and tell guests how to request a change before the deadline.
Separate attending, declined, and incomplete responses. Export or connect the data so seating, catering, badges, transport, and door check-in all work from the same named guest list.
Form vs messages vs spreadsheet
Small gatherings can begin in a group chat, but guest information becomes harder to reconcile as parties add names, change meal choices, or reply through different channels. A form gives every invitation the same route.
Field guide
The best field set is short enough for an invitee to finish, yet structured enough for the host to count people and prepare for them. These six sections cover the complete RSVP from identity through follow-up.
Invitation identity
Begin with the name shown on the invitation or a private invitation code, then collect one primary contact. This helps the host match nicknames, couples, and households to the original invite list without asking every attendee for duplicate contact details.
Attendance status
Make the attendance decision explicit and place it early. Conditional logic can end a declined response after an optional message, while attending parties continue to names and choices. If maybe is allowed, set a follow-up date rather than counting it as a seat.
Party members
A total of four does not tell a greeter who should enter or a caterer which person chose which meal. Use a repeating set of attendee fields and keep plus-one questions conditional on the invitation rule.
Meals and seating
Ask for the specific menu option for each named attendee, followed by a separate dietary-needs field. If the event uses assigned seating, collect useful preferences without promising a placement the host may not be able to provide.
Access and logistics
Accessibility, transport, and arrival questions turn the guest list into a preparation tool. Phrase requests openly, let respondents share only what is useful for participation, and direct sensitive follow-up to the appropriate event contact.
Confirmation and updates
The confirmation should summarize what was submitted, repeat essential event details, and explain how to correct a guest name or choice. On the organizer side, tag incomplete replies and assign follow-up rather than quietly treating missing information as a decline.
Related tools
Choose a focused RSVP tool for a particular occasion or start with a broader registration flow. Every link below points to an existing Makeform tool.
Create a general attendance form with contact details, party information, and event-specific questions.
Open toolCollect household attendance, named plus-ones, meal choices, and wedding-day logistics.
Open toolRegister individual guests with identity, contact, affiliation, and arrival information.
Open toolMake a friendly party response form for invitees, families, food needs, and host messages.
Open toolCapture professional profiles, organization details, attendance, and networking preferences.
Open toolStart from the established RSVP builder when you need a straightforward response form for any occasion.
Open toolFAQ
Practical answers for hosts and event planners building a clean RSVP and attendance workflow.
A guest list form is an online RSVP that turns each invitation into structured attendance information. It usually records the primary invitee, whether the party will attend, every attendee's full name, contact details, permitted plus-ones, and event-specific choices. The resulting submissions help a host create an arrival list, calculate the headcount, and prepare seating, food, transport, or badges.
Start with the invitation or household name, a primary email or phone number, attendance status, and the full name of each person attending. Add plus-one details only when they are allowed. Then include the planning fields that lead to an action: meal selection, dietary needs, accessibility requests, event date or session, transport, parking, organization, or badge name. Finish with an optional note and clear confirmation instructions.
Treat the invitation party as one response with one primary contact, but collect every attendee as a named person inside it. Ask for each family member's full name and only request age group when it affects event planning. Show the plus-one field conditionally for invitations that include one. This structure prevents duplicate household responses while preserving an accurate named headcount.
Yes. Put attendance near the beginning and use conditional logic for the rest. Attending guests can continue to party names, meal choices, transportation, and accessibility questions. Declining guests can skip those fields and optionally leave a message. The shorter decline path encourages a definite response, while the attending path still captures everything the planning team needs.
State the RSVP deadline and give guests a clear method to request a correction, such as replying to the confirmation or contacting the host. Keep the invitation name and primary contact in every submission so updates can be matched safely. For high-change events, track a response status and last-confirmed date, and preserve one current source of truth for caterers, seating planners, and check-in staff.
Yes. A structured response list can be filtered or exported for different operational views. Check-in needs attendee names and perhaps organization or ticket type. Catering needs meal counts connected to dietary notes. Seating needs party relationships and optional preferences. Keep the original response data together, then create focused views instead of maintaining unrelated lists that can drift apart.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect event replies without a response cap. The paid tier removes the Makeform badge. You can refine the questions and event wording before sharing the form, and the unlimited free positioning applies to the complete form rather than only an initial draft.
Collect only information the event team will use, explain why sensitive planning details are requested, and limit access to the people handling the event. Do not ask for birth dates when a broad age group is enough, or medical history when a guest can simply describe an accommodation or dietary need. Set an internal plan for correcting responses and removing data when the event workflow no longer requires it.
Build the list before event day.
