For the cook with a set menu and twelve chairs
One long table, a menu written down, and replies that come back with names and dietary notes attached. The invitation is the small part; the list behind it is what saves the Thursday.
Every dinner party runs from two pieces of paper. One has names, the other has ingredients and quantities. When replies arrive as messages, you end up translating between them by hand: counting heads for the loaf, remembering that Jonas's partner cannot have almonds, discovering on the evening that two of the twelve came from one invitation.
Put the invitation on a page with the menu on it and the translating disappears. A guest confirms against a name, chooses from what you are actually serving, and adds the allergy note in the same reply, while the market is still open and there is time to change a course.
Not a read receipt or a thumbs-up. The record says whether the person is coming, and it is the same record all week.
Offer the options you can cook and each guest picks one, so the plate count per dish is a number rather than a hope.
Room for a note under the choice, which is where the difficult one arrives: no shellfish, no gluten, the one guest who will eat none of it.
Companions counted inside the limit you set, so the table has a place for everybody before you lay it.
A menu paragraph on a card is decoration. On a page it is the question guests answer.
Dinner invitations are one of the formats My Joyfullday builds rather than something you assemble yourself: the menu, the replies and the notes sit together on one page from the start, and the shareable link behaves like any other invitation here. To see the finished thing, look at /features/dinner-invites; to describe your dinner instead of configuring it, send a sentence to Jitabi on WhatsApp.
The general platform shape is unchanged whichever route you take. Details live in one place, guests reply on the page, the list keeps the count, and a change to the menu reaches everyone who opens the link afterwards. For eight at home that is a convenience. For a longer table with a hired cook, it is the difference between planning and hoping.
How it works
Courses you can actually cook, in quantities you can carry. The page needs the real thing, because that paragraph doubles as the question guests answer.
Turn the courses into reply options, allow a line for allergies, and give yourself a date you can shop to rather than a feeling.
Use the web app or message Jitabi with the menu and the table size. Courses, time, address and the reply button should all be visible without hunting.
Publish and share the link. Confirmations, plate choices and companion counts gather on the list, and the shopping is done off a real total.
Questions
Yes. Guests answer differently when they can see the food, and it is how an allergy surfaces early instead of on the evening itself. Write the courses plainly and keep the surprises for the table.
Leave space for a note beside the meal choice on the reply. Guests write it as they would to you, and it lands with their name rather than in a message you have to find again later.
It usually is. Better to have one reply cover the invitation, with companions named inside the limit you set, because two separate answers for the same address is how a chair goes missing.
For eight it removes the translation step, which is the irritating part: counting, checking who can eat what, and remembering who mentioned they might bring someone.
Only once, as part of the link. Guests re-open the page on the day instead of searching the chat, and if the start moves by half an hour you change one line.
Get Started
Put the menu where the reply is, catch the notes as people confirm, and lay the table from a list you can read the morning of the dinner.
