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, $29 once · No subscription · No per-guest charge
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. Capacity is measured in the people who will actually walk in, so a boat trip for forty stops accepting replies at forty heads rather than forty envelopes.
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
Drag the schedule into the shape you mean and it reads that way for guests. Anything you have not given a time yet sits below the parts that have one, instead of floating to the top of the weekend.
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.
How it works
Add your guest list
One row per invitation, the way a printed card works, with the size of each party. Everything else in the weekend hangs off this list.
Add the parts of the weekend
Welcome dinner, ceremony, reception, brunch. Give each one a time, a place, a dress code and, where it matters, a capacity in heads.
Choose who sees the private ones
Mark a part invite-only and add the people it is for. Everyone else never sees that it exists, on the page or in the data behind it.
Send the invitations and watch the replies land
Each guest gets one link. Replies arrive per part, with the head count next to each, so you can hand the caterer a number rather than an estimate.
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.
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.
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.
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.
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 many parts can one event have?
Up to 40, each with its own name, description, place, start and end time, dress code and capacity. You set the order they read in, and parts without a time yet sit below the ones that have a time.
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.
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, $29 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.