The platform · 12
Several events. One celebration.
A wedding is rarely one evening. The welcome dinner, the ceremony, the brunch — each has its own guests, its own replies, its own seating and its own door, and all of them belong to one celebration, with one roster of your people underneath.
What hangs off the main event.
Wedding
Welcome dinner, rehearsal, ceremony, reception, after-party, brunch.
Bar or bat mitzvah
Friday dinner, ceremony, party, brunch.
Gala, or brand launch
Donor reception, VIP dinner, after-party. For a launch: press preview, VIP dinner, after-party.
Conference
Breakfast, workshops, cocktails, VIP dinner, after-party.
Add as many as you need, whenever they appear. Each one joins the same celebration.
Each event is its own event.
Its own guests
Invite a different circle to each. The rehearsal is forty people; the reception is two hundred. Nobody is told about a party they are not going to.
Its own replies
A decline on Friday never silences a Saturday invitation. Each event keeps its own count, and each count is right.
Its own seating and door
The brunch is seated from the brunch’s replies. The Saturday door admits Saturday’s codes.
One roster underneath
Households, plus-ones and dietary notes are entered once. For each event you choose who belongs, from people you already have.
One design world.
The same identity across the days — or evolved for each, or new.
The Friday dinner can wear the wedding’s world lightly, the brunch can take it somewhere warmer, and a launch’s press preview can look nothing like its party. That is a creative choice, made per event.
What never copies is a guest’s answer. The roster carries forward; the replies do not. Nobody arrives at the brunch already marked as coming because they came on Saturday.
What it costs.
One linked event is included with Fully Handled.
A Friday welcome dinner, a Saturday ceremony and a Sunday brunch can be run as one connected celebration, under one commission.
On every plan, each further event that belongs to the same celebration is priced at a flat reduced rate, because the identity, the roster and the foundation already exist.
As delivered.
One list, three days, on four delivered weddings.
Rendered from the file each event ran as — its own guests, dates and colour. Open any one to see it full size.
What it will not do.
Several events under one roof is where a system most wants to over-share. These are standing rules, not settings.
- Copy a reply from one event to another
- Invite the whole roster to every event
- Merge two evenings’ seating, or two doors, into one
- Tell a guest about an event they were not invited to
- Charge the full price twice for one celebration
- Decide which world each event wears — that is yours, per event
One celebration, however many days. One list of your people underneath it.
The rest of the platform
Three more services,
reading from the same event.
Guests & Households
The guest list itself: households, plus-ones, addresses, dietary notes — checked as it is built.
Explore → 02Invitations & Personalization
One design, and every guest receives their own copy — their name, their greeting, their code.
Explore → 03RSVPs & Replies
One private reply link per guest, and one live count that everything else reads.
Explore →