For the evening with a dress code and a small room
Standing room, an arrival window, one line about what you will be pouring. A page holds those properly and turns each yes into a name, so nobody has to guess how full the room will be.
A cocktail party fails on timing and crowding more often than on drinks, so these go on the page before the decoration.
The room that feels charming at eighteen is unpleasant at thirty. Because nobody is seated, the only honest measure is how many bodies fit by the bar and around the tables, which is why the reply needs to attach to names rather than to enthusiasm. One tap marks an invitation confirmed, with the companions that guest is allowed inside the limit you set.
The quieter advantage is the declines. At a standing party everyone assumes a full room; a list that shows the empty spaces tells you to open the second bottle and to stop buying the snacks nobody eats.
A good page answers each of these without needing a reply address.
Give the level, then one concrete example each side: jacket and no tie, or dark colours and comfortable shoes. People read examples faster than adjectives.
Name the window and what happens at either end: the host is at the door early, the first drinks are out at seven, nothing proper begins before eight.
Say whether it is canapés passed around or a standing plate, and when. Guests who were counting on eating plan their whole evening around that sentence.
State what each invitation allows. A cocktail crowd grows quietly, and a written limit is friendlier than an awkward message later.
None of these are complicated. All of them get buried in a thread of forty replies.
Now the page becomes the running note. If the drink list changes, or the arrival window shifts by fifteen minutes, you revise one line and everyone reading after that gets the corrected evening. Nothing arrives as a message a guest has to search for on a Friday afternoon.
If you are running the night with someone else, they can work on the same page rather than asking you for screenshots, since collaborators can be added with their own level of access. And the names that never answer show as a gap rather than a vague worry: reminders go out to non-responders from the list itself, which is less personal and more reliable than you typing the nudge.
How it works
Pick the arrival window, the end time you can genuinely hold, and the number of bodies the room and the bar can take. Those three constrain everything else.
Sign up on the web, or send Jitabi one line on WhatsApp: a cocktail evening on the fourteenth, jackets optional, forty standing. The page and the reply flow come back together.
The level of smartness with one example, what you will be pouring, whether there is food. These are the lines guests screenshot for their partner.
Publish, post the link where your guests already are, and watch confirmations arrive against names. Companion limits keep the count inside what you planned.
Questions
Name the level, then give one example either side: jacket and open neck, or dark and comfortable. A short note about shoes or the cloakroom does more than any formal phrase.
Yes, and for a cocktail crowd it is usually better. Give the window, what is happening at the beginning of it, and by when everybody will be there, so latecomers know they are not missing anything.
Set how many people each invitation may confirm and state that number on the page. The reply form holds to it, so the count you pour for is the count you decided on.
No. They open the link on their phone, tap, and their name is marked confirmed along with anyone they are bringing. Nothing to install and no sign-up involved.
The list. Names that have not answered appear as a gap, and a reminder can go to them through WhatsApp or email without you writing a personal note to each one.
Get Started
State the arrival window, the dress code and the drinks, and let replies land against names. You get a room that fits and a bar that was never a guess.
