Review changes to an event’s invitation list

An event has its own invited guests and replies. You can change the rehearsal supper list without changing ceremony invitations, and you can invite a previously removed guest again without restoring an old acceptance.

Open Hospitality → Guest replies → Event invitation lists, then choose the event. The owning business can also open Guest hub → Review invitation list and reply history. Reading requires guest access; saving requires the named account’s current Edit guests permission. A connected business must be explicitly granted that section.

Select, review and save

Checked guests are invited. Check an uninvited guest to add them; uncheck an invited guest to remove their event access. A previously removed guest is clearly labeled: selecting them creates a new invitation generation that needs a fresh reply.

Enter the reason, then choose Review invitation changes. The review lists each addition, removal or reinvitation and the effects on current replies, household forms, saved seating and transport reservations. Nothing is sent to guests by this action.

Confirm that you reviewed those exact changes before saving. A review expires after twenty minutes. If someone replies, edits a seat or changes an affected transport source while you are reviewing, saving stops and asks for a new review. The service checks event and invitation revisions as well as the reviewed operational sources.

A worked example

Finley has accepted the courtyard supper and selected the herb garden plate. Quinn, in the same household, was not invited. Finley also has a saved seat and a reserved shuttle place.

The host unchecks Finley and checks Quinn. The preview explains that Finley’s reply will leave current supper attendance and meal totals, while their saved seat and shuttle reservation remain allocated. After saving, the household’s existing private link shows the supper for Quinn only. A form opened before the change must reload before it can submit.

If the host later checks Finley again, the supper appears with an unanswered invitation. The previous herb garden plate and acceptance remain in Retained reply history; neither counts as a new answer. Finley must reply again.

Preserve operational assignments deliberately

Invitation changes do not delete seating assignments or release shuttle capacity. Review those assignments separately. A retained shuttle passenger who is no longer invited makes the current handoff stale; an authorized transport operator can explicitly cancel the reservation or transfer it to an eligible run. Reinviting the person does not reactivate the older manifest or acknowledgment.

If the person is already checked in or boarded, removing their invitation is blocked. First record an explicit correction through the current reviewed transport handoff, with a reason. You can then review the invitation change again. This prevents a guest-list edit from silently rewriting live transport execution.

For the explicitly selected main event, removal clears current attendance and meal fields while keeping the saved seat. The legacy guest-list status becomes non-attending; the event invitation screen shows that the person is not invited. The earlier manual RSVP baseline stays retained. Clearing or changing the main-event source restores that baseline through the existing source-change action. Guests who were never managed by that main-event invitation keep their separate manual records.

Current replies and historical answers

Current meal reports, event-specific floor-plan packets and RSVP screens use active invitations and the matching invitation generation. An older reply cannot count after a reinvitation. Plus-one invitations inherit only events currently shared by every named household member.

Replaced and reset replies are retained with their original answer time and invitation generation. Removing an invitation also retains its last reply. The history lists older answers separately from the current guest list and verifies the saved snapshot before displaying it. Older audit events remain in their original history; no earlier missing history is invented.

Invitation change history and retained reply history have separate page controls. These views exclude household capability tokens and private business records. A guest’s household link remains private to that household and only shows currently permitted events.

Messages and recovery

Saving an invitation list does not send email or SMS. Previously reviewed event email audiences are rechecked against current guest identities, invitation generations and event revision. A changed audience is held for a fresh review through guest communications.

If a save response is lost, retry the same reviewed save. Its request identity is bound to the account, workspace and exact reviewed input; a successful retry returns the original result. Changed input or a different account cannot reuse that receipt, and withdrawn access cannot replay it. Use Reload current invitation list when a source has changed, then review the new effects.

The named-account API is documented at /api/v1/openapi; the route is /api/v1/projects/{id}/event-roster. Provider setup is unnecessary for invitation-list changes. Actual guest-message delivery remains a separately reviewed and activated workflow.