The information layer between “who’s coming” and “doors open”
Registration tells you how many. Planning tells you what they need — and that second question is where events quietly succeed or fail. The dinner ordered on guesses, the venue with no step-free route for the attendee who needed one, the breakout session double-booked because nobody collected preferences — none of these are planning failures of effort. They’re failures of structured input.
This page owns that layer: the forms that run between registration and the event itself, plus the internal intake forms (vendors, speakers, volunteers) that organizers forget they also need. The boundaries in the event system: event registration covers the signup moment, this page covers the logistics intelligence, and event feedback covers the morning after. Starting points are in the event template collection, and everything below runs on the free plan.
The three-phase data plan
Event data has deadlines built in, so the collection has to be phased:
| Phase | Form | Deadline logic |
|---|---|---|
| Registration (theirs, not this page’s) | Signup — name, email, ticket | Opens with the announcement |
| Preferences | Dietary, accessibility, sessions, sizes | 2–4 weeks out, ahead of vendor deadlines |
| Final logistics | Arrival times, dinner RSVPs, last changes | 1 week out, ahead of final counts |
The planning instinct — one big form collecting everything — fails precisely because the phases have different deadlines. The preference form must go out before catering is locked; the dinner RSVP makes no sense six weeks early and is forgotten if sent too late. Three small forms, three deadlines, one system. The pre-event survey template is the preference phase, ready to go.
What to collect, and which question type does it properly
The single most common planning-form mistake is a question-type choice that silently breaks the branching. The rules:
- Dietary requirements — multiple choice, not dropdown. This matters twice: multiple choice can drive conditional logic and a dropdown cannot — so if you want menu-specific follow-ups (“select your starter” for meat, fish, and plant-based paths), the question must be multiple choice. It also needs an “Other — please specify” path for allergies that don’t fit the list; the dietary restrictions form is built this way.
- Accessibility needs — ask plainly, make it easy to answer. “Do you have any accessibility requirements we should plan for?” as Yes/No with an optional long-text follow-up — never a public dropdown of visible labels. The respectful pattern is to ask everyone, not just those who “look like” they might need it, and to keep answers private rather than routing them through visible option lists.
- Session preferences — multiple choice for the single pick; checkbox when attendees can choose several. Checkbox answers can’t drive clean jump logic (the first matching rule fires), so keep session counts on checkboxes and session-specific follow-ups on a single-choice version.
- T-shirt and merch sizes — multiple choice, recalled later in the confirmation (“Your {{size}} shirt will be at check-in”).
- Arrival times and attendance at sub-events — date and Yes/No questions feeding the final counts.
- Contact structure for group bookings — the contact info block, plus a “how many are in your party?” number question when invitations cover households or teams.
The branch recipes that remove the irrelevant-question tax
Three setups that keep every attendee’s form feeling personally sized:
By format — “Are you joining in person or virtually?” as question one, two jump rules: virtual attendees skip travel, lodging, and parking questions entirely; in-person attendees skip timezone and stream-access questions. Both branches converge on the shared preferences.
By ticket type — if registration already captured it, don’t re-ask: pass the ticket type through a hidden field in the planning form’s link (built with the UTM builder for bulk sends), use it as a condition source, and show the VIP dinner RSVP only to the people holding that ticket.
By meal path — the dietary branching done right: multiple choice for the main requirement, then a jump per option into that menu’s specific questions. “Vegetarian” never sees the steak options; the allergy path gets a text box and an urgent-flag question instead of a menu.
One caveat that keeps expectations honest: Formware’s logic evaluates rules left to right and fires the first match — it can route people down paths, but it can’t sum the answers. Which brings us to the counting.
The counting problem — solved outside the form, honestly
A planner’s week-before ritual is producing totals: 34 plant-based meals, 12 step-free seating requests, 85 medium shirts. Formware collects the answers but doesn’t aggregate them in the dashboard — so the counting happens in one of two places:
- In the responses view: filter by the answer to see the count for each option, then note the totals. Fine for a one-off event.
- In your spreadsheet: every response can push through a webhook — included on free — into a sheet that counts live as responses arrive. This is the version the caterer can be sent a link to, refreshed hourly on the deadline day.
Neither is complicated; both just need to be planned as your step rather than assumed to be automatic.
The intake forms organizers forget they need
“Event planning forms” usually means attendee questions — but the planning phase runs on supplier and contributor intake too, and these are often the highest-value forms of the whole project because the people filling them are essential:
- Vendor and supplier intake — contacts, insurance, setup requirements, power needs. The vendor registration template structures it, and file upload takes the certificates and floor plans (10 MB on free, fine for PDFs; Pro lifts the cap for larger media).
- Speaker and performer intake — AV requirements, bio, photo, intro script. The speaker booking template covers the booking, and recall personalizes the confirmation.
- Volunteer coordination — shifts, roles, t-shirt sizes, emergency contacts. The volunteer form handles signup, and the shift questions feed the roster.
- Catering and banquet orders — when you’re the client rather than the host, the banquet event order template keeps the specification in writing.
- And if you’re the planner selling services — the event planner consultation form is your own client intake, the first artifact a prospective client experiences from you.
Getting the forms in front of people
- Email remains the spine — a direct share URL, no login for respondents, “2 minutes” stated in the invitation.
- QR codes carry the paper layer. Save-the-dates, printed invitations, and venue posters each get a QR code — with a hidden field per placement so you know which print run produced which responses.
- Embed on the event site — the planning form lives next to the agenda and FAQ via embedding.
- WhatsApp is where community events actually coordinate. Local events, weddings, and meetups plan in WhatsApp groups — sharing forms into the chat meets people inside the conversation already happening.
- Event branding on every touchpoint. Colors, fonts, and backgrounds are customizable on free so every form matches the event’s identity; on Pro the badge comes off and your logo takes its place — worth it for weddings and client-facing events where the form is part of the occasion.
After submission
- One dashboard replaces the inbox archaeology. Filter by answer for the counts; export for the vendors who want lists.
- Push to the planning sheet. The webhook into your spreadsheet is the single highest-leverage automation in event planning — counts that update themselves.
- Committee access without password-sharing. Event planning is the most naturally multi-person work in this whole system — co-organizers, volunteers lead, caterer liaison. Free is single-user; Pro adds workspaces with roles, so the committee sees what it needs (Viewer) while one person owns the forms (Editor). This is the use case where Pro’s collaboration layer earns itself most directly.
- Send people somewhere useful afterward. Pro’s custom redirects land respondents on the agenda, the venue map, or the parking instructions — the planning form doubles as the “here’s what to know” moment.
- Chase the missing answers precisely. For long intake forms (vendors especially), Pro’s partial submissions keep whatever was entered before abandonment — view-and-export only, but “their insurance certificate is what’s missing” beats re-requesting everything.
The form is a preview of the event
The self-referential trap, party-planner edition: the preference form is the first course of the event itself. A chaotic, ten-minute questionnaire with dropdown mazes predicts — to the attendee — a chaotic dinner. A fast, one-question-at-a-time form that remembers their name and confirms their menu choice demonstrates the same competence the event promises. Guests read the form the way they’ll read the table settings.
If you’re comparing builders, Formware vs. Google Forms covers the free default every volunteer committee reaches for, and Formware vs. Typeform the other conversational builder event teams hear about first.
Free runs the whole system above — unlimited forms and responses, branching, recall, QR, embeds, WhatsApp, webhooks — subject to fair use, with Formware branding on the forms. Pro ($29.99/mo or $299/yr) removes the badge, adds your domain and logo, custom redirects, larger uploads, partial submissions, and the committee workspaces; the breakdown is on plans and pricing.
The event arc: event registration opens it, this page runs the middle, event feedback closes it — and the volunteers who made it work are recruited and thanked through the volunteer workflows.
Frequently Asked Questions
What should an event planning form actually collect?
By phase: preferences (dietary, accessibility, sessions, sizes) 2–4 weeks out before vendor deadlines; final logistics (arrival times, dinner RSVPs, last changes) about a week out. Registration data — who’s coming — belongs to the registration form and should be passed into planning forms via hidden fields, not re-asked.
How do I collect dietary requirements without annoying anyone?
One multiple-choice question with an “Other — please specify” path, asked of everyone, kept private. Use multiple choice rather than a dropdown if you want menu-specific branching — dropdown answers can’t drive logic conditions. Confirm the choices back on the thank-you page with recall so guests trust it was captured.
Can one form serve both virtual and in-person attendees?
Yes — “joining in person or virtually?” as question one, a jump rule per branch, each branch holding only its own questions, both converging before submission. The same pattern splits day-pass versus full-conference, and diners versus non-diners.
How do I get meal counts for the caterer?
Formware collects the answers; the totals come from your side. Filter the responses view by each answer for a quick count, or push every response through a webhook into a spreadsheet that tallies live — send the caterer a link to that sheet and the numbers stay current through the deadline. There’s no built-in aggregation to rely on, so plan the counting as your step.
Can my co-organizers and committee see the responses?
On Pro, yes — shared workspaces with roles: co-organizers as Editors who can manage forms, committee members and volunteers leads as Viewers who see responses without touching the builder. Free keeps everything with a single user, which works until the second person needs access.
