
employee engagement
The attendance problem: why people skip team events
People skip team events for a handful of ordinary reasons: the time slot costs them something outside work, the format leaves them out, or the last few events weren't worth the evening. "I'm busy" usually covers one of those. The fix is to find out which one applies to your team, by looking at who is missing and asking a few of them, and then change the event rather than push harder on the invite.
This guide is for organizers of internal gatherings: team outings, dinners, happy hours, celebrations and offsites. It ends with a table that maps the pattern you're seeing to its likely cause and a fix.
The time slot asks too much
An evening event asks people to give up personal time, and for many of them that time is already spoken for. In 2025, both parents were employed in 66.3% of married-couple families with children, according to the Bureau of Labor Statistics' Employment Characteristics of Families report. For those people, a 6 pm dinner means arranging pickup or a sitter. Add long commutes, second jobs, classes and caregiving for parents, and a Friday night event filters out a predictable group before anyone reads what the event is.
This is the easiest cause to test. If the people who skip evening events show up to the occasional lunch, timing is your problem.
The format leaves people out
Many team events are built around a bar. That made more sense when most adults drank. In July 2026, 54% of U.S. adults said they drink alcohol, a record low held for the second year in a row, according to Gallup's 2026 consumption survey. On a team of 20, that's roughly nine people for whom "drinks after work" is an event centered on something they don't do.
Alcohol is one example. Others: a physical activity that some people can't or won't do, a loud venue where people with hearing loss can't follow conversation, a restaurant with nothing on the menu for someone with an allergy, or a two-hour block of unstructured mingling that's tiring for people who don't already have friends on the team. The manager's guide to inclusive team outings covers these checks in more detail, and how to handle dietary restrictions covers food.
The last events weren't worth it
Every invite carries a promise that the event will be worth the time. When the last three were the same restaurant, ran an hour past the stated end, or turned into a forced icebreaker, people stop believing the promise and decline early.
Forced fun has a measurable downside. In a 2014 Wharton working paper, Ethan Mollick and Nancy Rothbard studied games that a company imposed on 448 salespeople. People who accepted the game felt more positive at work; people who didn't accept it felt worse than before. Giving people a choice in the game helped them accept it. A sales game isn't a team outing, but the lesson carries: an activity people had no say in can make them feel worse about work, not better.
Nobody asked
When the same two or three people pick every event, the events end up suiting those people. Everyone else rarely complains. They just stop coming. Asking before you book costs little: offer two or three options that fit the budget and the date, let the team vote, and do what wins.
Some people won't come, and that's fine
Some people keep work and personal life separate, and that's a reasonable choice. Pressure ("we missed you!" in the group chat, announcements saved for the event, a manager tracking who came) mostly makes the people who do attend feel watched. Keep the invitation open and the absence unremarkable.
Our rule of thumb
Judge your program by how many different people came to at least one event this quarter, not by turnout at any single event. If most of the team turns up somewhere across a quarter, your mix is working, even when an individual event draws half the team.
Read the pattern before you change anything
Look at the last four to six events and note who came. You need names, not percentages, so this is a 15-minute job with your RSVP lists. Then match what you see:
| What you see | Likely cause | What to try |
|---|---|---|
| Same people missing every evening event, but they come to lunches | Time slot | Hold the next one during work hours, Tuesday to Thursday, ending near the usual end of the day |
| People who don't drink, parents or newer hires missing most events | Format | Pick a venue where the activity, not the bar, is the point; add a shorter or daytime option |
| Attendance falling event by event across the whole team | Events haven't been worth it | Change the format, keep to the stated end time, and ask three people who stopped coming what would work |
| A whole team or office missing | Location or travel | Rotate locations, or hold a separate event closer to them |
| People RSVP yes, then don't show | Low commitment or a bad slot | Ask for replies closer to the date and send a personal note to the maybes |
| New hires come once and never again | First event didn't go well | Pair each new hire with someone for their first event and introduce them around |
| One or two people never come, everyone else does | Personal preference | Leave it. Keep inviting them, and say nothing about it |
The time-slot suggestion and the thresholds above are our guidance, based on what usually works for office teams, not a study.
Ask the people who stopped coming
Data from your RSVP list tells you who. Only people tell you why. Pick three or four people who used to come and stopped, and ask each one privately, in person or by direct message: "What would make the next one worth your time?" Make it clear there's no wrong answer and nothing gets reported. You'll hear things like "anything before 6," "somewhere I don't have to shout" or "something other than another bar," which is exactly the information you need.
Ask in private. A question in the group chat gets polite silence or answers from the people who already come.
Plan the next event around the answers
Choose one change and make it visible. If the answer was timing, move the next event to work hours and say so in the invite. If it was the format, pick an activity that people who skipped suggested. Then use the team outing checklist and timeline to book it, and the RSVP guide to write an invite people answer.
Expect it to take a few events to win people back. One good event after several weak ones doesn't reset expectations, but a run of them does. Gallup's research on workplace friendships (2022, updated 2024) recommends preplanned social events "whether an off-site event or an impromptu team lunch," which is a reminder that smaller, cheaper and more frequent can beat one big dinner a quarter.
Where TeamOutings fits
TeamOutings helps with two steps in this guide. Polls let the team vote on the activity, date or place before you book, and each outing keeps its Yes, No and Maybe replies with optional notes, so you can open past outings to see who said yes. It doesn't produce attendance reports or send reminders, so the pattern-reading and the personal follow-up are still done by you.
Let the team choose the next outing
Run a poll on the activity, date or place, then collect replies in one place.
See how it worksResearched and drafted with AI assistance, then edited and fact-checked by the TeamOutings team. Sources are linked in the text.
- attendance
- team events
- inclusion
- event planning
- employee engagement