Planning core
Guest list
Track the real guest list for this wedding workspace.
Total guests
Everyone currently tracked in this workspace.
0
Current guest count.
Invited
Guests already moved into invite territory.
0
Ready for outreach.
Confirmed
People currently expected to attend.
0
Expected attendees so far.
Structured groups
Real guest groups now saved for this wedding.
0
Saved group records.
Grouped guests
Guests already linked to structure or legacy labels.
0
Guests already tied to a group.
Guest groups
Create wedding-specific structures like households, family clusters, and wedding-party groupings.
Create group
Use structured groups for the real wedding shape: households, family clusters, wedding party, or custom planning buckets.
Add guest
Guests can now attach to real wedding-specific groups instead of only carrying a text label.
Create your first structured group before falling back to legacy labels. The app now supports real guest structure; use it.
Guest records
A real list you can build on now, with structured guest grouping wired into the workflow.
What this pass adds
The wedding-specific structure that now exists.
- Real guest groups as first-class records
- Guest assignment into households, family, wedding party, friends, or custom groups
- Editable group records that can evolve as planning gets more real
Permission sanity
What this shared-access pass means in practice.
You are seeing the owner-edit version of the guest list. Collaborators still get visibility, but not guest/group write authority yet.
Rollout sanity
What the current mixed model means.
All currently grouped guests are already using the structured model or no legacy labels remain.
That is acceptable during rollout. The important thing is that new structure no longer depends on freeform labels alone.
What still comes later
Still intentionally deferred.
- RSVP workflows and event attendance logic
- Seating chart structure
- Meal selection and invitation-response systems
QA sanity
What 34.6 should verify before closeout.
- Owner can create a group, assign a guest, edit both, and remove both cleanly
- Collaborator can view guests/groups but sees no fake write path
- Legacy-label fallback still reads clearly during rollout
- Search and filters still behave after guest/group changes
Workspace context
This page stays tied to the real wedding workspace.
Workspace context will appear here once a wedding is loaded.
Guest grouping now behaves more like a real wedding-planning system and less like a flat note pile pretending to be structured.