- Voting
- Create categories, auto-nominate everyone who's coming, add or hide individual nominees, watch counts live, publish results when you're ready, or clear the votes and run it again.
- Polls
- Any mix of question types, open and close on demand or on a timer, see exactly who hasn't answered, and send them a reminder — including one an AI drafts from the question.
- Jobs
- Create the work by phase — lead-up, the night, the clear-up — assign a leader, a crew and a checklist, set a budget and a due date, attach a plan document, and watch guests claim the rest, tick the steps and mark their own jobs done.
- Backstage
- The production desk: the jobs as a phase board, named crews you can WhatsApp in one paced send, and a contact book for the DJ, the caterer and the venue — bookings, fees against job budgets, set times on the schedule, and private notes guests never see. On the day, one button sends every worker their own running order.
- Where they sleep
- An inventory of rooms, beds, tents and pitches, each with how many it sleeps a night. Put guests in it or let them ask and approve the queue; the desk counts every night separately, tells you who's coming with nowhere to sleep, and keeps a part-stayer's bed theirs for the whole weekend unless you free it.
- Feeding them
- A grid of sittings across the party's days — which is the nights plus the departure breakfast — each with its menu, its caterer and a head count worked out from the RSVPs rather than typed. It shows its working (confirmed, presumed, said no), flags a main that's short, and names any dietary need nothing on the menu answers. Then lay the tables out and it proposes who sits where, from partner links, who's sharing a room, who's on a crew and who's been to parties with whom — honouring the two people you've said to keep apart as a hard rule, not a preference.
- What else is on
- The clay shooting, the boat trip, the sauna hour, the club night. Each holds a set number of places and, if you want, a price a head — and the desk tracks who's on it, who's waiting, who has paid, who part-paid and who you owe a refund. A full one waitlists the next person to ask rather than turning them away, and moves the list up on its own when somebody drops. Leave the price blank and no money appears anywhere; it's simply a sign-up sheet.
- Getting there
- Guests log the flights, hotels and transfers they're taking — on their own page or just by telling the party's assistant — and the desk shows you the waves: five guests into Faro, Friday 17:00–19:20, the way you'd tell a taxi firm. It matches on times and places and nothing else, names who's coming but has told you nothing, and counts the journeys logged with no clock on them, because those are invisible to it. Guests can see who lines up with them, or not, as you prefer — and any one journey can be kept private, which only you ever see. This is the one module that waits to be switched on.
- Picking the date
- When the party exists before its date does, put a few days up and let the guests say which they can do — yes, maybe or no against each — and read it back as a grid of people rather than a bar chart, because who can make the 12th is the question. Pick the winner and everyone who said yes is marked Coming in one press; the maybes are left alone and named, so you know who to ask.
- Signups, or just a link
- For the party people ask to join rather than get invited to. Switch a party to signup mode and it gets a public promo page in your own theme, with your sell copy, your how-to-pay details and a review queue behind it. Approving turns a signup into a guest, RSVP'd Coming — and sends nothing on your behalf. We're not a ticketing platform: no payments, no tickets issued, no cut. Or skip the queue entirely: a party can be one link you paste into the group chat, and whoever opens it is on the list and RSVPs themselves.
- Badges
- Award from the guest list, from a guest's profile, or in bulk after the party. Notifications optional.
- Karma weights
- One screen, six numbers, applied everywhere retroactively.
