RSVP Etiquette: A Guide for Hosts and Guests

Etiquette guides tell you the rule and leave out the reason. The reason is always the same: your answer is a number somebody books a table against. Here is what each reply actually commits you to, on both sides of the invitation.

Quick answer

Reply as soon as you can, and prefer a clear no to an open maybe. A no closes the question at no cost to anyone, while a maybe leaves the host guessing and paying for the guess.

If you must be uncertain, name the date your uncertainty clears and come back on it unprompted. Silence is the most expensive answer you can give, because it forces the host to either chase you or guess.

Hosts should make answering a single tap, give a deadline with a real reason attached, chase at most twice, and then count silence as a no and close the list.

Twenty-two said yes. Fourteen came.

Somebody you know has told this story. They booked for twenty-two, cooked for twenty-two, and stood in a room with fourteen people in it.

The eight who did not come were not villains. Six of them never actually said yes, they said something yes-shaped, and the host counted it because counting it felt kinder than asking again.

That is the whole problem in one sentence. An RSVP is a number somebody spends money against, and we treat it like a mood.

Etiquette guides usually approach this from the wrong end. They tell you what a well-raised person does, as though the rule came first and the reason came later.

It is the other way round. Every RSVP rule that survives contact with real life exists because somebody had to buy something.

What an RSVP actually is

The letters are French, and they are not a noun. Merriam-Webster traces RSVP to repondez s'il vous plait, meaning "please reply", with the English verb recorded from 1934.

So the original request was not "tell me if you feel like coming". It was "reply". The instruction was always about the answer, not about the enthusiasm.

That matters, because the modern failure mode is not rudeness. It is a slow drift where an answer became an opinion.

A yes is not a compliment to the host. It is a line item in their budget.

Once you see the RSVP as a commitment rather than a courtesy, most of the etiquette derives itself. You do not need to memorise rules from a 1953 manual about calling cards.

You need to know what your answer buys, what it costs the person who receives it, and how long they can wait for it.

The three things your answer moves

Every reply touches money, space and food, usually all three. A caterer wants a headcount, a restaurant wants a table size, and a friend wants to know how many chairs to borrow.

It also touches other guests. Venues have capacity, tables have seats, and a held place you never used was a place somebody else could have had.

And it touches the host's attention, which is the resource nobody costs. Chasing eight people for three weeks is the single most tiring part of hosting anything.

A table of what each answer commits you to

Most people answer honestly and still cause chaos, because the words do not carry agreed meanings. Here is what each answer actually does once it lands.

Your answer - What the host hears - What it commits you to - What it costs the host

Yes - One confirmed head - Attending, or telling them the moment that changes - A seat, a portion, a share of the deposit

No - One head removed, permanently - Nothing further, and no need to explain - Nothing. This is the cheapest answer you can give

Maybe - An unresolved head they must ask about again - Coming back with a real answer, unprompted - A guess, plus a follow-up conversation

Yes plus a guest - Two heads, one of whom they have never met - Your guest's behaviour and their attendance - Two seats, and a seating plan they now redo

A thumbs-up reaction - Something between yes and "seen it" - Nothing legible - A count that has to be verified by hand

Silence - Nothing they can act on at all - Nothing, which is the problem - The most expensive answer of the lot

Read the last row twice. Silence feels like the polite option because it avoids saying an unwelcome thing.

It is the opposite. Silence transfers the entire burden of resolution onto the person who already did the work of inviting you.

Notice also how badly the thumbs-up performs. We have written about why emoji reactions do not make an attendance record, and this table is the short version: a reaction is a feeling with no agreed meaning.

For guests: the honest rules

Answer sooner than feels necessary

The instinct is to wait until you are certain. The instinct is wrong, because your certainty is not the thing being requested.

What the host needs is your best current answer plus a commitment to update it. Those are two different obligations, and most people only offer the first.

A reasonable default is within three days for anything casual, and within a week for anything with a formal card. If you cannot answer by then, say that out loud rather than going quiet.

How to say no gracefully

A clear no is a gift, and almost nobody believes this until they have hosted something. It removes a head from the count and closes the question forever.

The good no has three parts and takes one message. Thank them, decline clearly, and offer something small that is actually true.

"Thank you for asking, I can't make the 14th. Have a wonderful evening, and I'd love to see you soon." That is complete.

Notice what is missing. There is no elaborate excuse, because a detailed excuse invites negotiation and implies your reason must qualify.

You do not owe anyone the reason. You owe them the answer.

The "maybe" problem

Maybe is not dishonest. It is usually the most truthful thing a person can say, and that is exactly why it does so much damage.

A host cannot buy half a chicken for a maybe. They round it up, cook for it, and absorb the waste when it resolves to no.

If you genuinely do not know, give the host something to work with. Name the blocker and name the date it clears: "I'm on call until the 9th, I'll confirm that morning either way."

That converts an unbounded maybe into a scheduled yes-or-no. It costs you one sentence and saves the host three weeks of wondering.

And then keep the appointment you just made. An unfulfilled "I'll let you know" is worse than a maybe, because the host stopped chasing you on the strength of it.

What a plus-one actually asks for

People treat a plus-one as a small ask. From the host's side it is one of the largest.

You are asking for a second seat, a second meal, a second share of the drinks, and a stranger placed into a room that the host has been arranging in their head for weeks.

At a wedding it is more concrete than that. A plus-one is a line on a catering invoice, and catering is usually charged per head with a locked-in final count.

The rule is simple. If the invitation did not offer one, there is not one, and asking puts the host in the position of refusing you.

If the invitation named you and a guest, that guest is expected, and dropping them silently is also a change worth mentioning. The host reserved for two.

When you can change your answer

You can always change your answer. What varies is the cost, and the cost rises steeply and then goes vertical.

Genuine illness, emergencies and things beyond your control are never the etiquette failure. Handling them badly is.

The wrong move is a group-chat message at 6pm on the day. The right move is a direct message to the host, as early as you know, saying plainly that you cannot come.

Do not bury a cancellation in a thread and assume it was seen. If your plans live in a chat, this is worth reading on its own, because changing an RSVP inside group planning is where most cancellations get lost.

If your withdrawal costs the host real money, offering to cover your share is a genuinely good look. Most hosts will refuse, and they will remember that you offered.

Why silence is the rudest option

This is the part that surprises people, so it is worth being blunt. Not replying is worse than replying no, and it is worse than a late cancellation.

A no closes the question. A late cancellation at least gives the host information they can use.

Silence does neither. It leaves an item permanently open, and it forces the host to choose between chasing you (awkward) and guessing (expensive).

It also has a compounding effect that nobody sees. A host chasing twelve silences learns that hosting is exhausting, and next year they do not host.

For hosts: how to ask so that answering is easy

Half the non-replies you get are not rudeness. They are friction, and friction is your department.

Every extra step between reading the invitation and answering it loses people. An invite that requires an account, an app or a reply-all email will underperform one that does not.

The strongest invitation makes the answer a single tap, from a phone, at the exact moment the person reads it. That is the entire design brief.

Ask one question with clear options

Ask "are you coming?" and offer yes and no. Do not offer maybe if you can avoid it, because a maybe button is a permission slip to not decide.

If your event genuinely has a soft tier, name it honestly: "yes", "no", and "want to come but can't confirm until the 9th". That third option carries a date, which makes it actionable.

Include everything a person needs to answer in the invitation itself. Date, start time, rough end time, place, what it costs and what to bring.

An invitation that omits the end time or the cost is asking people to commit to an unknown. Some of them will simply not answer, and you will read it as apathy.

Give a real deadline and say why

"Let me know" is not a deadline. It is a wish, and it produces exactly the trickle of replies you would expect.

A deadline with a reason attached performs far better than a bare date. "Please answer by the 9th, because I book the table that evening" is a fact people can respect.

The reason is doing the work. It converts your request from a preference into a constraint, and most people are decent about constraints.

Set the deadline before your real deadline. If the caterer needs numbers on the 12th, ask for answers by the 8th, because you will need those four days.

How to chase without nagging

Chasing is a normal part of hosting, not a sign that your friends are bad. Do it in a structured way and it stops feeling like begging.

• Send one public reminder, three days before the deadline. Keep it warm and factual: numbers are due, here is the link, here is the date.
• Message the non-repliers individually after the deadline. One message, direct, no guilt. Public chasing embarrasses people and rarely converts them.
• Make the ask binary and easy. "Just yes or no is perfect, and no is completely fine" removes the social cost of declining, which is what the silence was about.
• Give a real closing point. "I'm confirming the booking Thursday morning, so anyone I haven't heard from I'll count as a no." This is fair, stated in advance, and enormously effective.
• Then actually close it. Count silence as no, book accordingly, and stop carrying the open question around.

That last step is the one hosts skip. Holding places for people who never answered is a decision to be disappointed later.

Two chases is the limit. Beyond that you are not gathering information, you are applying pressure, and pressure produces reluctant yeses that turn into no-shows.

Build slack into your numbers

Confirmed yeses do not all arrive. This is not cynicism, it is planning, and every experienced host does it quietly.

How much slack depends on the event's weight. A ticketed wedding with a seating plan loses very few. A free casual thing in a group chat loses a meaningful slice.

The heuristic that works: the lower the cost of attending and the looser the invitation, the more your yeses will drift. A paid deposit is the strongest commitment device ever invented for this.

Plan the food and the space so that a shortfall is survivable and a small overage is survivable too. Order for slightly under your confirmed count on casual events, and slightly over on anything where running out would be a disaster.

Handling a late cancellation or a no-show

Somebody will cancel on the day. Your response to this determines whether they tell you next time.

Be gracious in the moment, genuinely. "That's a shame, don't worry, see you soon" costs you nothing and keeps the channel open.

If there was a real financial cost and the relationship is close enough, you can mention it once, calmly, afterwards. "No stress at all, the only annoying bit was the per-head charge" is fair and not a confrontation.

A no-show with no message at all is different, and you are allowed to notice it. You are not obliged to say anything, and you are also not obliged to invite them to the next one.

That is not pettiness. Guest lists are finite, and a place is worth giving to someone who will use it.

Deadlines by event type

There is no universal RSVP deadline, and anyone who tells you there is has only hosted one kind of event. What follows is a practical range, not a law.

Event - When to invite - Answer due - What sets the deadline

Casual drinks or a park meet - 1 to 2 weeks ahead - 2 to 3 days before - Nothing much. Just the host's headcount

Dinner at home for eight - 2 to 3 weeks ahead - 1 week before - The shopping list and the number of chairs

Restaurant booking - 3 to 4 weeks ahead - The venue's own confirmation date - Table size and any per-head minimum spend

Children's party - 3 to 4 weeks ahead - 1 to 2 weeks before - Party bags, cake, and venue capacity rules

Wedding - Save the date 6 to 12 months, invite 6 to 8 weeks - Roughly 3 to 4 weeks before - The caterer's final count and the seating plan

Catered or ticketed event - 4 to 8 weeks ahead - Whatever the supplier's cut-off is, minus days - A contract with a locked-in number

Recurring club or team night - Standing invitation - Same day, by a set hour - Whether there are enough people to run it

Two things are worth pulling out of that table. The deadline is always set by a supplier or a physical constraint, never by the host's impatience.

And the gap between the answer date and the real cut-off is deliberate. That gap is where the chasing happens, and hosts who skip it end up chasing during the cut-off itself.

None of this is universal

Everything above describes a broadly Western, largely Anglophone convention, and it is worth saying so plainly. Presenting one culture's manners as etiquette itself is how etiquette got its bad name.

The variation is real and it runs deep. In some cultures a firm advance headcount is expected and a late guest is a genuine breach. In others, open-house hospitality is the norm, extra guests are welcome by default, and demanding a precise count reads as cold.

Timing conventions differ too. The stated start time of a party is understood very differently across communities, and neither reading is the wrong one.

Religious and family occasions carry their own rules, which frequently outrank general etiquette. A family obligation may simply not be declinable, and an invitation may extend to a household rather than an individual.

The practical move is not to memorise a global table. It is to state your own expectations explicitly in the invitation, so that nobody has to guess which convention is operating.

"Please let me know by the 9th, and please tell me if you're bringing anyone" removes ambiguity in any culture. Explicitness travels better than assumed rules.

Occasion changes the rules as much as culture does

The same person is right to behave differently at a wedding and at a Tuesday pub night. The variable is what your answer costs.

Where the host has signed a contract, treat your yes as binding and your changes as urgent news. Where the host has signed nothing, a same-day change is genuinely fine.

That single question, "what did my yes cause someone to buy?", resolves most etiquette disputes without any manual at all.

Why the group chat makes all of this harder

Most invitations now happen in a thread, and threads are hostile to this specific job. Not because chat is bad, but because it was built for conversation rather than for counting.

The core issue is that a chat records what was said, not what is currently true. If someone says yes on Monday and cancels on Thursday, both messages sit there with equal weight and equal permanence.

Nobody is keeping score except the one person who has decided to keep score. That person is now a database, and the count lives in their notes app.

Answers also arrive in incompatible formats. A thumbs-up, an "in!", a poll vote, a private message, and a joke that might have been a yes.

Then there is the silence problem, made worse. In a thread you cannot tell the difference between someone who declined, someone who is thinking, and someone who muted the group in March.

Formal systems solved this decades ago by giving silence a name. The IETF's iCalendar specification, RFC 5545, gives every attendee a participation status, and the default value is NEEDS-ACTION.

The other values are ACCEPTED, DECLINED, TENTATIVE and DELEGATED. That is the maybe problem, formally acknowledged and separated from a yes, in a document from 2009.

It also means the person who has not answered is visibly distinct from the person who said no. A chat cannot make that distinction, which is why hosts recount by hand.

Polls are not RSVPs

Polls feel like the answer and they are solving an adjacent problem. A poll asks which option people prefer, and attendance asks whether a specific person will show up on a specific night.

Voting that Saturday works is a statement about your calendar. Saying you are coming is a promise, and the difference between saying "going" and answering a poll is exactly the difference this whole article turns on.

The other trouble is that polls close and attendance does not. People's plans keep moving for weeks after the votes are counted.

Use a poll to pick the date. Then ask the actual question again, separately, once the date is fixed.

Where Ontaym fits

Ontaym exists for the counting half of this, which is the honest reason this article is on our blog.

An event is a record with one address rather than a run of messages. Each guest has a state that is either yes, no or unanswered, and the host can see which is which without scrolling.

Guests answer with a tap, without an account and without swapping phone numbers with everyone else on the list. That matters because every step you remove converts some silences into answers.

Your group chat stays exactly where it is, doing the part it is genuinely good at. If you want the fuller argument, we have written about why an RSVP is not the same thing as a reaction in a group chat.

It is not right for everything. A ticketed conference wants a ticketing platform, and coffee with one friend needs nothing at all.

The short version, for both sides

If you are a guest, answer. Answer early, answer clearly, and prefer a clean no to a warm maybe you have not thought about.

Tell the host directly when something changes, as soon as you know, rather than hoping the thread absorbs it. Assume your yes cost somebody money, because it usually did.

If you are a host, make answering trivial and make the deadline real. Give a reason for the date, chase twice at most, and then close the list and stop carrying it.

Build in slack, be gracious about cancellations, and remember which people reliably answer. That last piece of information is more useful than any rule in any etiquette book.

None of this is about manners in the ornamental sense. It is about the fact that gatherings need someone to do the arithmetic, and everyone benefits when that arithmetic is easy.

Frequently asked questions

How long do I have to reply to an invitation?

As a default, within three days for anything casual and within a week for anything with a printed card or a stated deadline. If the invitation names a date, that date is the answer. If you genuinely cannot decide in that window, say so rather than going quiet.

Is it rude to say no to an invitation?

No, and it is far better than not answering. A clear no removes a head from the count, closes the question permanently and costs the host nothing. You do not owe a detailed reason, only a clear answer and a bit of warmth.

Why is a maybe such a problem for hosts?

Because a host cannot buy food, book a table or plan a room for a maybe, so they round it up and absorb the waste if it resolves to no. If you truly do not know, attach a date: name the thing blocking you and the day it clears, then come back on that day without being asked.

Can I bring a plus-one if the invitation did not offer one?

Generally no. A plus-one is a second seat, a second meal, a share of the cost and a stranger placed into a room the host has been arranging for weeks. Asking also puts the host in the position of having to refuse you, which is why the safe rule is that if it was not offered, it is not available.

What is the right way to cancel at the last minute?

Message the host directly, as early as you know, and say plainly that you cannot come. Do not bury it in a group thread and assume it was seen. If your withdrawal costs the host money, offering to cover your share is a good look, and most hosts will decline the offer.

How should a host chase people who have not replied?

Send one warm public reminder before the deadline, then message the remaining non-repliers individually once, directly and without guilt. Make the ask binary by saying that a no is completely fine, and state a closing point after which silence will be counted as a no. Two chases is the limit.

Should hosts assume some confirmed guests will not show up?

Yes, and the looser the invitation the bigger the drift. A free casual event announced in a chat loses a meaningful slice of its yeses, while a paid or seated event with a deposit loses very few. Plan food and space so that a modest shortfall and a modest overage are both survivable.

Are RSVP rules the same everywhere?

No. Some cultures expect a firm advance headcount and treat a late guest as a real breach, while others run open-house hospitality where extra guests are welcome by default and a demand for exact numbers reads as cold. Rather than assuming a shared rulebook, state your own expectations in the invitation.

Ontaym Editorial Team

Ontaym builds tools for organising real-world gatherings, so the team spends its days on the coordination problems this article describes. Articles are researched against primary sources, reviewed before publication, and revised when the underlying facts change rather than on a schedule.

Give your next plan one address instead of one more thread.