For the relative quietly keeping the list
Half your family already said yes over the phone. The problem is that nobody wrote it down. This is about turning those spoken yeses into one real list, and collecting every reply against a name.
By the time a graduation is announced, the phone has done most of the inviting. An uncle says he and his wife will come, a cousin promises the whole family, a grandparent asks whether the children are included. None of this is written anywhere, so it lives in three people's memories and quietly disagrees with itself.
A guest list exists to turn those conversations into a single honest number. You build it once from who has actually been invited, and from then every reply — yes, no, plus-one, a note — attaches to a name you already recognised. The ceremony seat count, the caterer, and the anxious question of whether there is room for an aunt's side all resolve against that one list.
Not everyone who might come — everyone you actually said the word to. Enter them before you send anything, so there is a known total to measure replies against rather than a drifting guess.
When someone confirms on the page, it ticks their row rather than arriving as a fresh message. You can see who answered and who still owes you, without re-reading the group chat.
A relative's promise of the whole family becomes two named companions inside whatever limit you set, instead of an open invitation the caterer discovers on the day.
Ceremony seats and reception places both want a number weeks ahead. A live list gives you one you can hand over, and update if plans shift.
Building it once removes the recurring argument about who is actually coming.
An invitation without replies is just a wish. What turns a guest list into a number is that each invited person can answer from their phone in a couple of taps, and the answer lands on the list rather than in your messages. That is why the list and the invitation should be the same page: send the link, and the counting begins the moment the first guest opens it.
You start free, enter everyone you have invited, and share the one link into the family chat. As yeses gather you can upgrade as your guest list grows if the crowd turns out larger than the phone calls suggested. Drafts stay private until you publish, so no relative ever sees a half-built list of names.
How it works
Uncles, cousins, the neighbours who promised. Names first, before you send a thing, so the list has a real total from the start.
Build it in the web app or ask Jitabi on WhatsApp. The page carries the date and venue, and the guest list sits behind it, waiting for answers.
Post the same invitation to the family group. Each person replies on the page, and their yes ticks their own row instead of starting a new thread.
The list shows confirmed against outstanding at a glance. Send a gentle reminder to the quiet rows and the count settles before anyone needs the final figure.
Questions
Yes, especially then. A spoken yes has no date, no name for a plus-one, and no record. Putting everyone you invited on one page turns those promises into a count you can actually use and keep correct.
You set how many companions each guest may name, and the reply form holds to that limit. Extra places arrive as named guests before the day, not as surprises at the door.
Yes. You can add collaborators with their own access, so a relative handling one side of the family and you handling the other both work from the same live list rather than two separate notes.
The list separates those who have confirmed from the rows still open, so you always know how many owe an answer. Reminders to the quiet ones go out without you writing to each person.
Get Started
Write down who you invited, hand them a link to answer, and let the list do the remembering. The ceremony seats and the caterer both get a real figure, not a family argument.
