Designing RSVP questions that people answer
The RSVP form is easy to build and easy to overload, and every extra question lowers replies and raises what you must look after.
The short answer
Ask only what you will use to make a decision: whether the person is coming, who is coming, and the few practical needs you can act on. Each question should have a purpose, a named person who uses the answer and an owner for how long it is kept.
Separate required from optional, explain why you ask, and treat questions about health, religion, family or other sensitive matters as a topic for your organisation's data protection contact before they reach the form.
Start from the decisions, not from the form
List the decisions the RSVP must feed: seat and catering numbers, name badges, accessibility arrangements, transport or session choice. Only questions that support one of these belong on the form.
If you cannot name who will use an answer, leave the question out. You can always ask later and only of those who need it.
Core RSVP questions
| Question | Purpose | Required? | Who sees it |
|---|---|---|---|
| Will you attend? (yes, no, a delegate will attend) | Core count and next step. | Required | Secretariat |
| Name as it should appear, and organisation | Name badge, attendee list. | Required if yes | Secretariat, badge printer on a need-to-know basis |
| Role or segment | Pick the right follow-up message. | Optional unless used | Secretariat |
| Contact for event-day information | Send joining instructions. | Required if yes | Secretariat |
| Session or track choice | Room allocation. | Only if rooms are limited | Programme owner |
| Dietary requirement | Catering. See dietary count reconciliation. | Optional | Caterer via the secretariat, as agreed |
| Access needs | Arrangements you can act on. See accessibility questions. | Optional | Named person only |
Wording that gets honest answers
- Offer a clear decline option and a delegate option, so people do not ignore the form because yes is the only button.
- Use plain words and one question at a time.
- Say what the answer is used for and who will see it, next to the question.
- Avoid 'tentative' unless you will follow up on it. If you do use it, say when you will ask again.
Check each field against the minimiser
- List every proposed field and its purpose.
- Mark each as required, optional or removed.
- Name the retention owner for each field.
- Run the list through the registration form field minimiser, which produces a worksheet of rationale and privacy-review questions.
- Take the unresolved items to the data protection contact.
After the form: where answers go
Decide before launch where responses are stored, who can open them and how they will feed the reminder list. Responses that say decline must update the invitation sequence so the person is not reminded again.
If counts are uncertain, use the attendance scenario planner to look at different possible outcomes rather than quoting a single number.
Worked example · Fictional example
A fictional RSVP trimmed from nine fields to five
Fictional organisation and figures, for illustration only.
Seminar Fiktif Pengurusan Risiko drafts a form asking for name, organisation, job title, mobile number, home address, dietary requirement, access needs, how the person heard about the event and seat preference. These figures are illustrative.
The secretariat checks each against a decision. Home address and how the person heard about the event have no user and are removed. Job title and seat preference become optional. Dietary and access needs stay optional, each with a line saying who sees it. The form has five core fields, and the data protection contact is asked about the optional ones.
Use this yourself
RSVP question worksheet
Fill in one row per proposed question before the form is built.
| Question | Decision it feeds | Required or optional | Who uses the answer | Retention owner | Sensitive? Ask data protection contact |
|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- The form has a handful of questions and one person owns the replies.
- The list is small and known.
- Your data protection contact has already approved the standard fields.
Outside planning help earns its fee when
- Several committees want to add their own questions.
- Sensitive or special-need answers are being collected and nobody has reviewed them.
- Replies are spread across email, forms and chat and no one has a single count.
Need the RSVP designed with the plan behind it?
A conference project lead can turn your decisions into a short RSVP, run the field-minimisation worksheet with your secretariat, and connect replies to the reminder and attendance plan. What may be collected and kept is for your data protection contact to confirm.
Questions organisers ask
Is a phone number necessary on an RSVP?
Only if someone will use it, for example for event-day information. Ask the data protection contact whether it is needed, who can see it and how long it is kept.
Should we ask about dietary needs on the first RSVP?
Often it is better as an optional field or a later, short follow-up to those attending. Decide with your caterer when numbers are needed.
Can we ask why someone declined?
You can offer an optional reason, but plan how you will use it. A short, optional question is better than a long one. See decline response process.
How many questions is too many?
There is no fixed number. If any question has no named user and purpose, it is too many.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.