Describe your dinner seminar, venue, menu, and audience. Makeform creates a registration page for attendee contacts, guests, meal preferences, and accessibility requests.
Send new registrations to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose an example, adapt it, or send it into the Makeform builder as an editable starting point.
Audience
Invited prospects and business leaders
Format
Invitation-code registration with meal choices
Prompt size
337 chars
Example form structure
Invitation-code registration with meal choices
Name, title, and company
Work email and mobile number
Invitation code
Select your dinner entrée
Dietary or accessibility requests
Suggested routing tags
Confirmed attendees
Dietary follow-up
Waitlist
Ask for one meal selection per named attendee, including guests, to produce usable catering counts.
Step 1
Invite
share the seminar details and registration link
Step 2
Register
collect contacts, seats, meals, and requests
Step 3
Prepare
organize headcount, catering, and seating
Step 4
Follow up
send reminders, changes, and event resources
Why use a dedicated form
Email may confirm a seat but omit structured meal and guest details. A dedicated form keeps the attendee list useful through check-in.
Required contacts identify each guest and give the team a way to send reminders or venue changes.
Show dinner questions to diners and reveal guest fields only when someone adds a guest.
Keep names, meal counts, accommodation notes, and status together instead of reconciling emails.
Adapt it to the room
Choose the closest event model, then replace its agenda, menu, and rules with your details.
Add an invitation code, company and title fields, a named host, and concise meal choices for a curated guest list.
Collect a guest's name and meal separately, then keep the pair connected under the primary registrant.
Ask for household seats, interpretation, transport, childcare interest, and accessible seating in one public signup.
Use member identifiers, topic interests, presenter questions, and dinner-versus-seminar attendance choices.
Registration workflow
Give the builder your event details, then review the result for catering, venue, and attendee communications.
Include the date, location, agenda, capacity, menu, guest policy, and required attendee information.
Mark essential contact fields required, connect guest questions to the guest answer, and show meal fields only to dinner attendees.
Share the page in invitations, campaigns, listings, or a QR code.
Route submissions to the people handling communications, catering, accommodations, and check-in.
Registration page vs email replies
Structured registration reduces missing meal, guest, and accommodation details.
Field guide
These six groups create a handoff for marketing, catering, venue staff, speakers, and check-in.
Attendee identity
Identify each person and their business or community context without slowing registration.
Contact details
Collect channels used for confirmations, schedule changes, and day-of notices.
Attendance and guests
Ask for seats and every attendee's name so check-in and catering totals count people, not submissions.
Meals and dietary notes
Use fixed menu options plus a dietary-notes field, repeated for every diner.
Event logistics
Place essential logistics near the fields and use specific dates and times.
Participation and accommodations
Collect accessibility requests and presenter questions, routing notes to responsible staff.
Related tools
Choose a focused generator for conferences, general RSVPs, catering requests, or nonprofit dinners.
FAQ
Answers for event marketers building a clear page and useful attendee list.
It explains the event and collects structured details for each seat: identity, contacts, attendance, guests, meal preferences, dietary notes, accessibility requests, and seminar questions.
Collect name, organization or role, email, phone, and attendance. Add guest details, each person's meal, dietary and accessibility requests, and a speaker question. Display the date, agenda, venue, parking, deadline, and change contact.
Ask whether the attendee is bringing a guest. If yes, reveal the guest's name, menu, and dietary fields. Separate choices make every entrée count attributable to one person.
Yes. Ask whether the person will attend dinner, the seminar, or both. Show meal questions only when dinner is selected, while retaining contact and participation fields for seminar-only attendees.
State the deadline and seat policy, with a contact for changes. For a waitlist, collect core contact details and label those responses separately. Confirm the capacity workflow before sharing the link widely.
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and collect registrations without a response cap; the paid tier removes the Makeform badge.
Yes. Label the event invitation-only and collect an invitation code or host name for review. Show registrants the necessary venue details and a contact for registration problems.
Route responses to the event owner and organize a list for communications, catering, venue arrangements, and check-in. Keep meal and accommodation notes connected to named attendees.
Replace replies with a prepared guest list.
