Birthday invitations: manage the RSVP without chasing

You send the birthday invitation to the family group at nine at night. By half past it sits under a video of someone's dog, two voice notes and a photo of a new kitchen. The next morning three people ask what time it starts, and you have already written it down once.

Sending birthday invitations is the easy part. Managing the RSVP is where the week goes sideways. The date gets buried under chat, replies arrive in four different tones across four different threads, and on the night before the party you are counting heads by scrolling. A prettier design does not fix that. Where the confirmation lives does.

A link that opens beats a pretty PDF

A JPEG in a group chat is not an invitation, it is a photo, and photos scroll away. A PDF is barely better: it asks your guests to download a file, find the date inside it, and then answer you somewhere else entirely. An invitation that is its own web page works the other way round. It opens in the browser they already have, on the phone already in their hand, and the confirm button sits on the same page as the time and the address. Nothing to install, nothing to download.

• Open the link on your own phone before you send it. If the date and the place take more than five seconds to find, your guests will take longer.
• Keep date, time and place in one block, so nobody hunts through paragraphs for a postcode.
• Use a cover photo that says whose birthday it is before anyone reads a word.
• Send it with days to spare. An invitation that lands on Thursday for a Saturday gets a shrug.

How to manage the RSVP without forty private messages

Forty one-to-one 'are you coming?' messages end as forty answers in forty tones, half of them scrawled on a scrap of paper. A reply in a chat is not a confirmation either. When someone types 'I think so', nobody knows whether to count them, so you ask again, and the loop starts over.

A confirmation form inside the invitation turns that 'I think so' into a yes or a no. Who is coming, whether they are bringing someone, and a short line for a note: two or three questions, answered in under a minute, on the page they just read. The answers land in one list instead of a chat.

An invitation is not finished when you send it. It is finished when the replies arrive in one place.

One tidy list beats twenty screenshots

Twenty screenshots of 'yes, we are in' spread across three conversations will not tell you how many chairs to borrow. One list will. It also survives a change of plan: move the party from 6pm to 7:30 because a friend finishes work late, edit the page, and everyone sees the new time at the same address, without a reprint or a second round of messages. Check the list on the morning of the party rather than the week before, because there is almost always one late yes. One page, one payment of €29.99, and the confirmations come to you.