A weekend is not one party,
so it is not one RSVP.
Add the welcome dinner, the ceremony, the reception and the brunch. Each one carries its own time, place, dress code, capacity and reply, and the ones that are private are invisible to everyone not on them. Guests open a single link and see the schedule that applies to them.
Included in the Event Pass, $39 once · No subscription · No per-guest charge
The Schedule panel on your event dashboard: four parts of one wedding weekend, each with the replies it has collected.
- 1
Four parts, four sets of answers. Every row is stored separately, with its own time, place, dress code and reply. Sunday brunch has no time yet, so it says so and sits below the parts that have one.
- 2
Coming counts replies, People counts heads. One yes from a couple is one reply and two chairs. Both numbers are printed, and capacity is measured against the second one.
- 3
Invite only is a badge, not a buried setting. The amber badge on the welcome dinner means the other guests' invitation pages do not contain that row at all. The screens further down show what that looks like from a guest's phone.
- 4
Arrows, not drag. Two labelled buttons move a part earlier or later, and the top row's up arrow is dimmed because there is nowhere above it. Keyboard and thumb both work.
Built for the parts, not the day
Most RSVP tools model one event and ask you to explain the rest in a paragraph. A weekend has separate rooms, separate lists and separate answers, so it is stored that way.
Each part has its own details
A name, a description, a place, a start and an end time, and a dress code that belongs to that part alone. Black tie on Saturday and swimwear on Sunday are two different instructions, and guests read them where they read the invitation.
Its own RSVP, not one blanket yes
Coming to the ceremony is not the same as coming to the rehearsal dinner. Each part carries its own reply and its own head count, and a guest can change any of their answers later without touching the others.
Invite-only means invisible
Mark a part invite-only and it exists for exactly the people you add to it. The welcome dinner for twelve does not appear on the invitation of the two hundred people asked to the ceremony. Not greyed out, not locked: not there.
Capacity counts heads, not invitations
One yes from a couple is one reply and two seats. The host panel prints both numbers side by side — Coming counts replies, People counts heads — and capacity is measured against the second, because that is the number the caterer asked for.
One link, the schedule that applies to them
A guest opens their invitation and sees the parts they are allowed to see, with places left where you set a limit and two buttons against each one. No app, no account, no password.
Up to 40 parts, in the order you choose
Reorder with the up and down arrows on each row: full-size touch targets with real labels, because a drag handle is unusable with a keyboard and awkward with a thumb. Anything you have not given a time yet sits below the parts that have one, instead of floating to the top of the weekend.
How it works
Four steps, three of them screens you can look at before you pay for anything.
First, the part everything else hangs off
A schedule is built on a guest list: one row per invitation, with the size of each party. Every reply to every part is attached to one of those rows, and there is no anonymous way to answer a part — which is exactly what makes a private dinner possible. If you are starting from scratch, the invitations and RSVP page is where that begins.
Open the Plan tab and start from nothing
The schedule lives on your event dashboard under Plan, and it opens on a dashed card that reads One event, for now. Nothing about your event changes until you add a part, so a simple party stays a simple page. If you have not set a time zone on the event yet, the panel says so in amber before you type a single time — and it refuses to schedule a time it cannot place rather than quietly putting your dinner in the wrong zone.
The Schedule panel before anything exists — the empty state and the missing-time-zone notice, exactly as they render.
Add the parts of the weekend
Six plain fields: what is it, where, starts, finishes, dress code, how many fit. Only the name is required — a brunch you have not fixed a time for is a legitimate row. The capacity field says what blank means in the field itself, and one checkbox at the bottom decides who the part exists for at all.
The add form. It is the same component the edit pencil opens, so a change reads exactly like the original entry.
Choose who sees the private ones
Invite-only parts get a checklist of the people already on your guest list, with the size of each party beside the name. Everyone and Nobody are there for the two common cases; the rest is taps. Saving writes only the difference, so a guest who already answered keeps their answer, and the server checks every name against your guest list again before it writes.
The invitee picker, open under the welcome dinner, with the status line the save leaves behind.
Send one link each. The private part stays private.
Invite-only is the rule the rest of the schedule depends on, so it is enforced on the server twice: once when the invitation page is assembled, which leaves the part out of the response entirely, and again when a reply arrives, because the id in a reply did not have to come from the list we sent. A guest asking about a part that is not theirs gets the same answer as a guest asking about a part that does not exist, so the endpoint cannot be used to confirm that a private dinner is happening at all.
Here is what that looks like. Same weekend, same host, two invitations.
Marta, who is on the dinner list
Luis, who is not
Two guests' invitation pages. The welcome dinner is not greyed out on the right-hand one — it is not on it.
- 1
The missing card is the feature. The invite-only dinner is filtered out before Luis's page is built, so there is no row, no lock and no message telling him there is something he is not invited to.
- 2
The same flag, two words. What reads as an amber Invite only badge to the host who set it reads as a mint Just for you to the guest who got it.
- 3
One reply per part. Yes and No sit against each card, and How many of you starts at the party you invited — the usual answer, one tap fewer. A part that is full says so and stops taking a yes.
- 4
Places left is all anyone learns about the others. The number of free places crosses the wire because a guest needs it. Who else said yes, and what they said, never leaves your dashboard.
Who runs an event in parts
Multi-day weddings
Rehearsal dinner on Friday for the wedding party, ceremony and reception on Saturday for everyone, brunch on Sunday for whoever is still in town. Three guest lists, three replies, one invitation link per guest.
Destination weddings
Guests who have flown in want the whole weekend in front of them: the welcome drinks, the boat, the beach barbecue, and which of them they said yes to. Capacity on the parts with a real limit keeps the transfers and the tables honest.
Conferences with a dinner
The talks are open to every attendee; the speakers dinner is not, and putting it on the public agenda invites a conversation nobody wants to have. Mark it invite-only and it is visible to the speakers alone.
Family reunions
A Saturday lunch the whole family comes to, a cousins-only evening, a Sunday walk with room for thirty. Each part takes its own answers, so the organiser knows how many chairs, cars and packed lunches to count on.
What it does not do
Every one of these is a decision rather than a gap, and it is better you read it here than find it out the week of the wedding.
No calendar file
There is no .ics export and no Google Calendar link. Guests read the times on their invitation page, in your event's time zone.
No per-part reminder emails
Nothing chases a guest who has not answered one particular part. The invitation link is the nudge, and you send it.
No waitlist
When a part fills, the guest is told it is full and asked to talk to you. Nobody is queued behind it automatically.
No meal choices per part
A part collects yes, no and how many. Dietary requirements belong in your invitation's own questions, not here.
One more, in the other direction: if your Event Pass lapses you keep reading the schedule and every reply it collected. Only adding, editing, reordering and deleting need the pass.
Questions hosts ask
Can a guest be invited to the ceremony but not to the welcome dinner?
Yes. Any part of the weekend can be marked invite-only, and then it is visible to exactly the people you add to it. It is filtered out before the invitation page is built rather than hidden in the interface, and a reply posted for it by anyone else is refused with the same answer they would get for a part that does not exist.
Do I need a guest list before I can build a schedule?
Yes. Every reply to a part is attached to a row on your guest list, and there is no anonymous or public way to answer one — which is also what makes an invite-only part possible in the first place. The picker says as much when the list is empty: add people to the guest list first, then choose from it here.
Does a guest have to reply to each part separately?
Yes, and that is the point. A yes to the ceremony is not a yes to the rehearsal dinner, and treating it as one answer is how couples end up cooking for people who were never coming. Each part takes its own reply and its own party size, and a guest can change any of their answers later.
Do guests need an account or an app to reply?
No. A guest opens the personal invitation link you sent them and the schedule is already on it, under their main RSVP. The token in that link is the only credential there is: the reply is filed against the guest that token belongs to, never against an identifier the browser sends, so a guest cannot answer on somebody else's behalf and has nothing to sign in to.
What happens when one part of the weekend is full?
Set a capacity and it is counted in heads rather than invitations: one yes from a couple bringing two people is two places, not one. Guests see how many places are left, and a reply that would overfill the room is refused with the number still available and a nudge to talk to you. To be exact about it: the check counts and then writes rather than locking the row, so two guests claiming the last seat in the same instant can both get in. That is a phone call to the caterer, not a corrupted list — and a blank capacity, or a zero, means no limit at all rather than a closed room.
Can guests see the parts of the weekend they were not invited to?
No. A guest sees the open parts, which everyone on the guest list can see, plus any invite-only parts they are personally on. They can see how many places are left on a part they can see; they never see who else replied or what anyone else answered.
How do I change the order of the weekend?
With the up and down arrows on each row, not by dragging. A drag handle is unusable with a keyboard and awkward with a thumb, so the order moves with two labelled buttons — move this earlier, move this later — and the whole new order is saved in one go, so no two parts can end up sharing a position. Parts you have not given a time yet sit below the parts that have one.
How many parts can one event have, and how big can they get?
Up to 40 parts per event. Each one takes a name of up to 120 characters, a description of up to 1,000, a place of up to 300, a dress code of up to 120, and a capacity of up to 100,000 heads. An invite-only part can hold up to 2,000 named guests.
Which timezone are the times shown in?
The one you set on the event, not the one the guest's phone happens to be in. A 7pm dinner reads as 7pm to somebody who is still on the clock they flew from, which is the only reading that is ever useful to a guest. If you have not set an event time zone, times fall back to UTC and carry a visible zone label so nobody misreads them as local — and if you try to give a part a time while there is no zone to place it in, you are asked to set the event time zone in settings first rather than being given a time that means nothing.
What happens to a part once it is over?
It stops taking replies. The Yes and No buttons disappear from that card and it reads: this one is over. Everything already answered stays where it is, and the rest of the weekend carries on taking replies as normal.
What happens if I delete a part of the weekend?
Its replies go with it, and you are told so before it happens — the confirmation says everyone's replies to it go too. If you only want to move a part, edit it; deleting is for parts that are not happening.
What does the weekend schedule deliberately not do?
There is no calendar export or .ics file, no reminder email for an unanswered part, no waitlist when a part fills, no meal or dietary choice per part, and no list of who else is coming for guests to browse. Each of those is a decision rather than a gap, and it is better you know before you buy than after.
What happens to my schedule if my Event Pass runs out?
You keep reading it. Viewing the schedule, the replies and the head counts is never gated — the pass covers adding, editing, reordering and deleting. Locking a host out of the answers they have already collected would be hostage-taking, so the panel keeps showing them and tells you the pass is what unlocks editing again.
Is this only for weddings?
No. Anything that runs longer than one gathering fits the same shape: a conference with a speakers dinner, a festival with a limited-capacity workshop, a family reunion with a cousins-only evening. The words on the page are the ones you type.
What does the weekend schedule cost?
It is part of the Event Pass, $39 paid once for the event, with no subscription and no per-guest charge. The same pass covers the guest photo gallery, the guestbook, the slideshow and 12 months of hosting.
Put the whole weekend on one link
Set the parts up in an afternoon, send one invitation each, and stop reconciling three spreadsheets. If you want a hand with a complicated guest list, write to Support@Picsui.com and a person will help you lay it out.