The whole party in one thread
Date, page, guest list, replies and reminders can all live in one conversation. Send what is decided today and let the plan take shape in the thread as the rest of it closes around you.
Planning normally happens in fragments. The date lives in a calendar, the guest list in a spreadsheet a cousin technically owns, the venue negotiation in its own thread, and the final invitation in a message you will retype once everything is set. Each fragment is manageable; the joins between them are where evenings disappear, because every join is a copy-paste someone has to do and then check.
The alternative is not a project tool. It is a single thread that holds the structure: one conversation with Jitabi where details get sent, changed, and turned into an invitation page. The chat is where planning happens; the page and the list are what the chat produces.
Not a rule so much as a shape that has held up for most hosts.
Guests reply to a day, not an address. With a date you can publish an invitation that marks the location as to be confirmed; swapping the venue later is one message, and the link never changes.
The sooner the reply button exists, the sooner the list fills, and the more distance you get between the first yes and the final number you will plan food around.
Plus-ones are counted in the reply itself, within limits you set, so the headcount grows honestly instead of by optimism.
When replies slow, messages go from the guest list to the people who have not answered, over WhatsApp or email — not to the group that already has.
Honesty matters here. A WhatsApp planning thread is not a supplier directory, not a budget sheet, and not a caterer you can negotiate with. What it holds is the part of planning that gets handed to guests: the page, the list, the reminders, and every change you make along the way. What stays outside the thread — the food tasting, the deposit — stays where it always was. Hosts who plan this way tend to finish earlier, mostly because the invitation stopped being a separate project.
How it works
The date and the shape of the party, even if the venue is still a maybe. The page drafts with the gap marked as an honest placeholder.
Group chat, individual messages, a printed card with the QR. Every guest opens the same live page, so retyping details never enters anyone's week.
The guest list counts yeses, plus-ones and meal notes while you finalise food and seating elsewhere; edits you make in the thread land on the page guests see.
A quiet week still needs a push — non-responders get a message from you without the whole group being pinged again.
Questions
Yes, and it is often the right order. Guests care about the date first. Publish with the location marked to be confirmed, promise a fill-in date in the wording, and make the venue update a single reply to Jitabi.
No. It drafts and edits the event page, and the guest list tracks replies and reminders. Supplier conversations, payments and budgets stay in your own notes; the thread holds the part guests actually see.
Soon enough that slow repliers still get a nudge before it turns awkward. Most parties send two to four weeks ahead; events with travelling guests need longer, because their reply is a decision rather than a reflex.
Collaborators can be given access at different levels, so two people can watch replies and send reminders without sharing logins or photographing a phone screen across a table.
Reminders go from the guest list to individual non-responders over WhatsApp or email. People who have already answered are left alone, and the group chat does not get a second broadcast.
Get Started
Everything the party needs is in your head already, or will be by Thursday. Message it over in pieces; the thread keeps the shape while the details arrive.
