How to get employees to RSVP to team events

To get employees to RSVP to a team event, make the reply take one tap, put enough detail in the invite that people can picture going, show who has already said yes, and follow up once, personally, with the people who haven't answered. Most missing RSVPs aren't refusals. People mean to reply, the message sinks under the rest of the day, and nobody asks again.

This guide is for internal events: team outings, dinners, happy hours, kickoffs and celebrations. It ends with an invite and a follow-up message you can copy.

Why people don't reply

The usual reasons are mundane. The invite lands mid-afternoon between two meetings. It's missing something the person needs to decide, such as how long it runs, whether food is included or whether it's on work time, so they park it for later. Replying means opening a form and typing a name the organizer already knows. Or they aren't sure yet, and the only choices are yes and no.

None of that is hostility toward the event. Treating it as hostility, with "mandatory" in the subject line and a third all-staff reminder, tends to make the silence louder.

Make the reply one tap

Ask one question: are you coming? Offer yes, no and maybe. Anything else you need (food preferences, a plus-one, who can drive) you can collect later, and only from the people who said yes.

Keep the maybe. It gets an answer out of people who would otherwise say nothing, and it hands you a short list of exactly who to follow up with.

Write an invite people can picture

An invite that reads like a memo ("Team outing March 15. Please RSVP.") gives people a date and a demand. Give them what they need to decide in one read:

• What it is, in a sentence that sounds like something they'd enjoy
• The day, a start time and an end time
• The place, with the address and how people are getting there
• What's covered (food, drinks, the activity) and whether it's on work time
• How to reply, and by when you need to know

Specific times matter more than they look. In a 2011 field experiment published in PNAS, employees of a large firm who were prompted to write down the date and time they planned to get a flu shot at an on-site clinic were vaccinated at a rate 4.2 percentage points higher than a control group (33.1%), while a date-only prompt made no significant difference. A flu shot isn't a team dinner, but the mechanism carries over: a concrete when and where is easier to commit to than "sometime next week."

Show who's already going

People take cues from what others like them are doing. In hotel field experiments reported in the Journal of Consumer Research in 2008, a card telling guests that most other guests reused their towels worked better than the standard environmental appeal, and it worked best when the norm referred to guests who had stayed in the same room.

For a team event, the "same room" is the team. "Eight of the twelve of us are in" says more than "please RSVP." A practical way to get there: before the invite goes to everyone, ask two or three people who usually come to reply early, so the first thing others see is a headcount rather than an empty list.

Keep it about who's coming. Naming the people who haven't replied, in a group channel, turns a nudge into pressure.

Pick a time that doesn't cost people their evening

Our guidance: when you can, hold the event during work hours, Tuesday through Thursday, ending at or near the usual end of the day. A Friday night asks parents to arrange childcare and asks commuters to stay in town. A mid-afternoon event replaces work time instead of personal time, which removes the most common reason to say no before the invite is even read.

If evenings are the only option, rotate them. Same night, same people left out, every quarter, is how a team ends up with a regular crowd and a regular set of absentees. The manager's guide to inclusive team outings covers more on choosing times and places that work for everyone.

Let people choose the activity

When people helped choose, they have a reason to show up. Before you book, run a quick poll with two or three options that all fit the budget and the date. Then do what wins. Overriding the vote because a senior person prefers something else teaches everyone that the poll was decoration.

Follow up once, personally

A second blast to the whole team mostly reaches the people who already replied. A direct message to each person who hasn't answered works better, and you're probably underestimating how often it gets a yes. In studies published in the Journal of Personality and Social Psychology in 2008, people underestimated by as much as half how likely others were to agree to a direct request for help. Those were face-to-face requests rather than invitations, but the lesson for organizers holds: a personal ask is harder to scroll past than a group message, and people say yes to it more often than you'd guess.

Our guidance on timing: one short group nudge two or three days before your reply-by date, then direct messages to whoever is still silent. After that, stop. People who say no or never reply are still part of the team the next day.

Make no an easy answer

A no is useful. It tells you the headcount and it tells you something about the event. If the same people decline every time, ask them privately what would work better: a different time, something without alcohol, something less physical, a shorter format. Their answers are the cheapest planning research you'll get. Why people skip team events goes deeper on the patterns behind repeated no's.

Templates you can copy

Invite

Team dinner at [Restaurant], Thursday, Oct 16, 5:00 to 7:00 pm

We're taking over the back room at [Restaurant] ([address], a 10-minute walk from the office). Dinner and drinks are covered, and it's during work hours, so head over straight from your desk. [Name], [Name] and [Name] are already in.

Can you let me know yes, no or maybe by Monday? I need to give the restaurant a count on Tuesday.

Follow-up (direct message)

Hi [Name], are you in for the team dinner Thursday at 5? No worries either way. I just need a count for the restaurant by Monday.

For the full planning sequence around the invite, from budget to booking to the day itself, see the team outing checklist and timeline.

Where TeamOutings fits

In TeamOutings, each outing has Yes, No and Maybe replies with an optional note, and a live headcount everyone on the team can see, which takes care of the "who's going" signal without anyone posting a list. If someone tells you in person, an admin can update their reply. You can poll the team on the activity, date or place before you set the plan, and every outing has its own chat for questions like "is it walking distance?"

TeamOutings doesn't send reminders today, so the personal follow-up described above is still yours to do.