The RSVP questions worth asking

Every question should earn its place

An RSVP form is the one document almost every guest fills in, and it is the moment you learn most of what you need to plan. That makes it tempting to ask everything: song requests, a favourite memory, shoe size for the dance floor slippers. Each extra question feels small. Together they turn a thirty-second reply into a chore that sits unanswered in someone’s inbox for a fortnight.

A good test for any question is to ask who will act on the answer, and when. If the caterer needs it, ask it. If the shuttle company needs it, ask it. If nobody will read the answer until after the event, it probably belongs in a thank-you note or a guestbook rather than the RSVP.

• Who will use this answer?
• What will they do differently because of it?
• Does every guest need to see this question, or only some?
• Could the answer reveal something sensitive, and who should see it?
• Would the event be harmed if you did not ask?

The essentials: who is coming, to what

Attendance is the question everything else depends on, so ask it clearly and per person. "Will you attend?" is ambiguous when one invitation covers a family. "Which of you will attend?" with a line for each named guest is not.

If your event has several parts, ask attendance per part. A wedding with a ceremony and a reception, a conference with a workshop day and a main day, a festival with a Friday and a Saturday: each needs its own answer. A guest who comes to the ceremony but leaves before dinner changes your catering count without changing your ceremony seating, and you can only plan for that if you asked separately.

Ask attendance per person and per function. A single yes or no per invitation is the root of most headcount errors.

Meals, allergies and dietary needs

If you are serving a plated meal, ask each attending guest to choose. Keep the options to what the kitchen will actually prepare, and describe them plainly: "Grilled fish with rice" is more useful to a guest than a menu poem.

Ask about allergies separately from preferences. An allergy is a safety matter for the kitchen; a preference is a matter of taste. Mixing them in one free-text box produces answers like "not a fan of coriander, also severe nut allergy", which is exactly the kind of note that gets misread at nine in the evening during service. A short dropdown for common requirements plus a free-text field for anything else works well.

Dietary answers can reveal health conditions or religious practice, so treat them with care. Your caterer needs the counts and the table numbers; your seating designer does not need to know why someone is vegetarian. Share the minimum each supplier needs to do their job.

Access needs, asked well

Many hosts leave access needs off the form because they are unsure how to ask. The result is that guests with mobility, sensory or other needs either do not come or arrive to find a staircase between them and their seat. A simple, respectful question solves most of this.

Ask what a guest needs rather than asking them to describe a condition. "Do you need a step-free route or seat?", "Would captions or a sign language interpreter help you?" and "Is there anything that would make attending easier?" are all questions a guest can answer without disclosing more than they wish. Then make sure the answer reaches the people who arrange the room and the seating.

• Step-free route and seating, and space beside a seat for a wheelchair
• A seat near the front, or with a clear view of an interpreter or screen
• Quieter seating away from speakers
• Reserved parking or a drop-off point near the entrance
• An accompanying carer, who should be counted as a guest

Plus-ones and companions

If you have offered someone a plus-one, the form should collect that person’s name and the same essentials as everyone else: attendance, meal and access needs. A plus-one recorded as a nameless extra produces a place card with no name on it and a meal count that is quietly wrong.

If you have not offered a plus-one, do not leave a blank "guest" field on the form; some people will fill it in in good faith. Show each invitation exactly the seats it includes.

Travel, transport and accommodation

For events where guests travel, a few logistics questions save many messages later. Arrival and departure dates help you size welcome events and shuttles. Whether a guest is staying at a recommended hotel helps you plan pickups. Whether they need transport from the venue at the end of the night tells you how many seats to book on a late coach.

Ask these only of guests they apply to. Local guests do not need to see airport transfer questions, and conditional questions that appear only after a guest says they are travelling keep the form short for everyone else.

Make the form conditional

Conditional questions are the single best way to ask more without burdening more people. A guest who declines should see a short, kind confirmation and perhaps a space for a message, not a menu choice. A guest attending only the ceremony should not be asked about dinner. A child should not be offered the option to meet new people.

Sketch the form as a simple tree before you build it. Start with attendance per function, then branch: meals only for functions with food, travel questions only for travelling guests, access questions for everyone who is attending.

1. Ask attendance for each named guest and each function.
2. For each function a guest attends, ask only what that function needs.
3. Ask access needs of every attending guest.
4. Show travel questions only to guests who say they are travelling.
5. End with an optional message and a clear note of the reply deadline.

Optional questions and consent

Some hosts like to ask lighter questions: a song request, a hope for the couple, a topic a conference attendee would like to discuss. These are fine as optional extras, clearly marked as optional and placed after the essentials.

Be more careful with anything social. A question such as "Would you like to be seated near people with similar interests?" is useful for seating, but it should be optional, asked only of adults, explained in one line, and easy to change later. Never use answers to guess at things a guest has not told you, such as relationship status or faith.

Deadlines, changes and reminders

Set your reply deadline backwards from your suppliers’ deadlines. If the caterer needs final numbers fourteen days before the event, a reply deadline about three weeks out gives you a week to chase the last answers. Tell guests whether and until when they can change their replies, and make changing easy; a guest who can update their own answer is far less likely to message you at midnight.

Plan two gentle reminders: one about a week before the deadline and one a day or two before. Send them only to guests who have not replied, and respect quiet hours in each guest’s time zone.

Where the answers go next

An RSVP is only as useful as what happens to the answers. Meal choices should become catering counts. Access needs should become reserved seats and a route on the floor plan. Attendance per function should become the door list for each day. If every answer has to be copied by hand into another spreadsheet, errors will creep in at exactly the busiest point of planning.

Attergo is designed so that replies flow straight into headcounts, meal counts, seating and check-in lists, but whatever you use, decide before you send invitations how each answer will reach the person who acts on it.