For the list behind everything
The invitation gets the attention, but the guest list is what you work from all the way to the door. A guest-list website lets you invite from it, watch it tick itself as replies arrive, and hand it to a co-host with a number you can stand behind.
The invitation is read once. The list is used every day until the event.
The list is where the guests live, so sending the invitation means sharing one link with the names already gathered there. No separate mailing to keep in step with the count, and replies arrive against those same names.
As each guest answers on the invitation, their name moves to confirmed. Companions attach under the guest who brought them. You read a live status of the day rather than updating a column by hand.
A co-host, a planner, or a family member can be added with their own level of access, so several people can see and manage the same list without three copies drifting apart on three phones.
The Lindqvist family learned this the hard way. The graduation party had four organisers, each keeping their own tally: Grandma's side here, cousins there, the neighbours in a note app. By Friday night nobody agreed on whether it was forty people or sixty, and the venue needed a number in the morning.
A shared guest list ends that argument because there is only one. Anyone invited appears once, anyone who replies is ticked once, and the shape of the day is legible to everyone with access at the same time. The count stops being a memory and becomes something the list maintains itself.
It is the view you keep returning to as the event fills in.
Every event has one: the call from the venue or the caterer wanting a final figure. A guest list that has been reading itself the whole way means you have that number ready, drawn from the same page that invited the guests and collected the replies.
That is the payoff the invitation quietly works toward. The pretty page gets people to answer; the list is what turns those answers into a headcount you can hand over with confidence. One page holds both, which is why the list is the part worth building properly.
How it works
Begin with the names you intend to invite. The list is the spine, so the invitation and every reply hang off those names.
Share one link with the people already there. Confirmations tick names off automatically, with companions attached to the right guest.
Add a partner, parent, or planner as a collaborator with their own access level, so the same list is visible to everyone managing it.
Open the live list for the caterer or the venue. Confirmed heads, meals, and notes are already totalled and ready to hand over.
Questions
The invitation is read once; the list is what you manage the whole way to the event. It is the source of the headcount you give vendors, so keeping it accurate matters more than any single design choice on the page.
Yes. You can add a co-host or planner as a collaborator with a defined level of access, so several people see and manage one list rather than maintaining separate tallies that drift apart as replies come in.
They attach to the guest who brought them, within the limit you set. The list reflects the real seat count because companions arrive as part of a reply, not as a loose note you have to remember.
On the day, QR check-in marks each confirmed guest in as they reach the door, so the list separates who promised from who is in the room, without a helper working a paper sheet.
The live list totals confirmed guests and meal choices as they arrive, and you can close it at your deadline. That gives you the settled figure to hand over rather than a guess reconstructed the night before.
Get Started
Invite from it, let the replies tick it down, share it with a co-host, and open it for the venue. A guest list that reads itself is the calmest thing on an event page.
