Extra RSVP fields beyond yes/no

The RSVP form collects more than just attending/declining. Three optional fields live alongside the basic response — none are required, but each maps to a real coordination job hosts run after the responses land.

Plus-ones (additional guest count)

A small numeric stepper between 0 and 20. Guests pick the number of extras they're bringing. The host stats tile on the responses card shows the catering headcount ("18 guests expected" instead of just "12 attending") when plus-ones contribute. The dedicated "guests expected" subline on the Attending tile only renders when at least one attending RSVP carries plus_ones > 0 — fresh galleries with all-singles stay visually quiet.

Dietary requirements

A free-text textarea, 500 character cap. "Vegetarian", "Nut allergy", "gluten-free, no shellfish" — whatever the guest needs the kitchen to know. Per-row the entry surfaces as a bordered blockquote under the guest's name; aggregated across attending and maybe RSVPs, the responses card surfaces a "Dietary requirements for the caterer" block sorted alphabetically by guest name, ready to hand to the venue.

Song request

A short text input, 120 character cap. Wedding + party galleries surface this field; business and memorial galleries hide it (where DJs and party playlists aren't a thing). The responses card surfaces both the per-row request AND a dedicated "Song requests for the DJ" aggregation block that deduplicates case-insensitively and sorts most-requested-first so the same track requested by three guests floats to the top with a count badge.

Why we made these optional

Required fields are friction. Most guests RSVPing to a wedding don't need a dietary requirements blank — they're not bringing one. Forcing every guest to skip past empty fields adds drag to the response rate. Each field is optional and the dialog hides them under labels guests can ignore without thinking.

Where the data goes

Everywhere the responses live:

• The host detail's RSVP responses card (per-row inline + aggregated blocks for songs and dietary).
• The /api/galleries/[id]/rsvps.csv export and the in-archive rsvps.csv companion in the full-gallery ZIP — both carry every extra column.
• The host notification email fired on each submit includes the plus-ones count alongside the attending status.

Coordinating with a caterer or DJ

The dietary aggregation block and songs aggregation block on the responses card are designed for one-shot hand-off:

• Take a screenshot of the dietary block and email it to the caterer.
• Copy the songs list straight into a message to your DJ — the dedupe + count gives them a usable playlist without you spending an hour deduping it yourself.

Both blocks self-hide when zero guests submit the relevant field, so quiet galleries don't pretend to have data that isn't there.