How to design a wedding or event enquiry form people actually finish
Which questions earn their place, how to ask about budget, when a multi-step form helps, and the mobile details that stop people abandoning the form halfway.
Ask only what you need for a useful first reply: name, one contact method, event date, venue or suburb, guest count, what they’re interested in, and an optional budget range. Use visible labels rather than placeholder text, offer choices instead of typing where you can, say what happens after they submit, and test the whole thing on a phone.
Start from your first reply, not a wish list
Every field should answer one question: does this help me send a useful first reply? If you can’t confirm a date, give a ballpark or suggest a next step without it, ask for it. If not, leave it for the conversation. Baymard Institute’s checkout research found the average checkout uses 11.3 form fields, when most need only 8. Event forms tend to bloat the same way.
| Field | Why you need it | Best format |
|---|---|---|
| Name | To reply personally | One field, not first and last |
| Email or phone | To reply at all | Ask which they prefer; require one, not both |
| Event date | Availability is the first thing you check | A date input, plus a “date not set yet” option |
| Venue or suburb | Travel, access and whether you serve the area | Short text, or a suburb list if your area is small |
| Guest count | Drives quantities and price | Ranges such as 1–20, 21–50, 51–100, 100+ |
| What they’re interested in | Routes the enquiry and shapes your reply | Tick boxes of your real services |
| Budget range (optional) | Avoids mismatched proposals | Ranges, clearly optional |
Fields to cut or make optional
- “Tell us about your vision” as a required essay. Keep it optional. Some couples love writing it. Many will leave rather than start.
- Full street address. A suburb is enough to quote travel at this stage.
- “How did you hear about us?” Useful, but make it an optional dropdown. Better still, capture the source automatically with tracking.
- Separate first and last name, title, company for private events. Every extra box costs a little patience.
How to ask about budget without being awkward
Budget is the field people argue about most. Asked well, it helps both sides. Offer ranges that match how your work is priced, include “not sure yet”, and add one line of context: “This helps us suggest options that suit you.” Make it optional. Combined with a starting price on your website, most people choose a range honestly.
One page or several steps?
Short forms of five or six questions work fine on one page. Beyond that, a step-by-step form can feel lighter, especially when it starts with an easy, low-commitment question like “What are you planning?” and shows only the questions relevant to that answer. A proposal enquiry doesn’t need the same questions as a 150-guest wedding.
If you go multi-step, show progress (“Step 2 of 4”), keep answers when people go back, and never ask for contact details on the first screen. Earn them.
The mobile details that make or break it
- Every field has a visible label above it. Nielsen Norman Group’s testing found placeholder text used as a label hurts usability: it disappears when people type, so they can’t check their answers.
- Inputs use the right keyboard: email, phone (tel) and date types, with autocomplete for name, email and phone.
- Buttons and tick boxes are easy to tap. WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels at level AA. Bigger is kinder.
- Errors appear next to the field, in words, and keep everything already typed.
- Choices use buttons or tick boxes rather than long dropdowns where possible.
- The submit button says what it does: “Check my date”, not “Submit”.
What happens after they press send
This is where most event forms quietly fail. The thank-you message should say when you’ll reply and how, and only appear once the enquiry has genuinely been received. Some form setups show success even when the email never sends, because the provider wasn’t activated or the message was rejected. Test with a real submission to your real inbox after every change.
- Send an automatic confirmation email with a copy of their answers.
- If you’re slower on weekends or during events, say so.
- For spam, a hidden “honeypot” field and server-side checks usually beat puzzles that frustrate real people.
- Count a lead in your analytics only when the enquiry is confirmed as received, not when someone clicks the button.
A quick test before you publish
Ask someone who has never seen the form to enquire about a real-sounding event on their own phone while you watch, without helping. Note every pause. Each pause is a field to cut, reword or turn into a choice. Then look at your pricing visibility, because a form works best when visitors already know they’re in the right place.
Sources
- Checkout Optimization: 5 Ways to Minimize Form Fields in CheckoutBaymard Institute. 26 June 2024: average of 11.3 fields; most sites need 8.
- Placeholders in Form Fields Are HarmfulNielsen Norman Group
- Understanding Success Criterion 2.5.8: Target Size (Minimum)W3C Web Accessibility Initiative