RSVP by event: ceremony, pre-wedding, meal, party, and brunch

When a wedding in Spain includes several moments, the usual mistake is not asking for too much information but asking for all of it at once and without context. If the ceremony, pre-wedding gathering, meal, party, and brunch have different audiences or requirements, the RSVP should reflect that reality. A guest who can attend dinner but not brunch needs a clear, fast path with no ambiguity. The best approach is to separate each event as a concrete decision, explain only what matters, and make the expected answer visible in each case. That reduces scattered messages, helps you avoid rebuilding the seating plan at the last minute, and gives family and friends a more organized experience.

The short answer

Event-by-event RSVP works best when each guest first sees the overall plan and then responds only to what applies to them: ceremony attendance, pre-wedding plans, meal choice when relevant, presence at the party, and whether they will join the brunch the next day. In a wedding in Spain this is especially useful because some guests are local, others are travelling, families ask about children or plus-ones, and suppliers need numbers at different moments. If each form block answers a real planning decision, the couple stops chasing replies on WhatsApp and starts working with useful data.

The easiest way to present it is through a wedding website where guests can read timings, locations, and context before replying. If the form is also tied to an online RSVP flow the experience is much clearer than mixing messages, calls, and manual lists.

What each guest should confirm

Think about the form as a sequence of decisions. First, overall wedding attendance. Second, the events before or after the ceremony. Third, the logistical details tied to those events: menu, allergies, shuttle, departure time, or whether someone will attend only part of the celebration. You do not need to show every question to every guest. If brunch only applies to people staying overnight or travelling in, that part should feel like an optional block with a clear explanation. The more obvious the link between the question and the real plan, the fewer contradictory answers you will receive.

It also helps to define the tone of each block. The ceremony usually needs a simple confirmation. The pre-wedding gathering may need headcount and estimated arrival time. The meal needs actionable catering choices, such as the main option or dietary restrictions. The party may share transport or access details. Brunch normally asks for one final yes-or-no reply to calculate tables, coffee, or replenishment. That logic gives each event its own purpose and avoids endless forms that exhaust guests before they finish.

Checklist before opening RSVP