People who said yes and did not come
Free events in a chat group attract an enthusiastic yes and a quiet absence. Here is why that happens, what it costs you, and the handful of changes that turn a maybe into a chair with someone in it.
Forty-two people reacted to the message. Thirty said they were coming. You booked for thirty, ordered food for thirty, and on the night nineteen turned up. The room looked empty in a way that was slightly deflating for everyone in it, including the eleven who had genuinely wanted to be there.
This is the most common operational problem in community organisations, it is almost entirely predictable, and most of it can be designed away. What it is not is a sign that your members are unreliable people.
Why a free yes means so little
The gap comes from the difference between what saying yes costs and what turning up costs. In a group chat, "yes" costs a tap. It is a friendly gesture, a signal of goodwill towards the organiser, and at the moment of tapping it is completely sincere - the person genuinely intends to come.
Then Saturday arrives and turning up costs an hour in traffic, a shower, and getting off the sofa. Nothing was ever committed, nobody is expecting them specifically, and cancelling has no cost either because there is nothing to cancel. The yes did not create an obligation, so it did not survive contact with a tiring week.
Once you see it as a cost mismatch rather than a character flaw, the fixes become obvious: raise the cost of saying yes slightly, or raise the cost of not turning up slightly. Both work, and both need a light touch.
Ask for something small
The cheapest reliable fix is making registration slightly more effortful than a chat reaction. Not a barrier - just a small deliberate act. A short form. A reply with your name and how many you are bringing. A ticket, even a free one.
This works for two reasons. It filters out the reflexive yes, so your number is more honest. And it creates a small psychological commitment: someone who typed their name has done something, and people are noticeably more likely to follow through on things they have taken a deliberate step towards.
Expect your headline number to drop, and do not be alarmed. Thirty chat reactions becoming eighteen registrations is not a decline in interest; it is the discovery that twelve of those thirty were being polite. Nineteen people turning up out of eighteen registrations is a far better event to plan than nineteen out of thirty.
The number to watch is your show-up rate against registrations, not your total yes count. If forty percent of registrations turn up, your registration step is too easy. If ninety-five percent do, you have got the balance right and can plan catering with confidence.
Where a deposit is worth it
For anything with a real per-head cost - a meal, a bus, a venue charged per person - a small payment changes behaviour more than any amount of reminding. It need not cover the cost. Rp 25.000 against a Rp 100.000 dinner is enough to make people either come or tell you they cannot.
The useful variant is a deposit returned or credited on arrival, which feels fair and removes the sense that you are profiting from absence. It is more admin, so use it where the money genuinely matters and not for a free talk in a room you already have.
For free events, resist the urge to charge purely for commitment. It changes the relationship into something transactional in a way that a community event usually should not be, and you can get most of the benefit from a registration step. Our guide on selling event tickets to members covers when a real charge is the right call.
Remind well, which mostly means remind late
Reminders are the standard answer and they are only half right. A reminder a week out does very little - the person's Saturday is not yet real to them. The one that matters is the morning of, or the evening before, when they are actually deciding what their day looks like.
Two is usually the right number: one a few days ahead so it can be planned around, one on the day. Make the day-of reminder practical rather than promotional. Where exactly, what time, what to bring, how to find the room. You are not persuading them any more; you are removing the small frictions that turn a maybe into a no.
Personal beats broadcast substantially here. A message that names the person and says "hope to see you tonight" gets a meaningfully better response than the same information sent to everyone, because it turns "an event is happening" into "somebody expects me".
Give people a reason to be missed
The most effective anti-no-show mechanism is not administrative at all. People turn up when their absence would be noticed by a specific person, and they skip when it would not.
So build small expectations into the event. Ask someone to bring something. Give someone a two-minute part in the programme. Pair a newcomer with a regular who is expecting them. Any of these converts "an event I might go to" into "a thing where somebody is counting on me", and that is worth more than every reminder you will ever send.
Plan for the gap rather than fighting it entirely
Even done well, some no-shows are permanent. Traffic happens, children get ill, work runs late. The mature version of this is to design so a partial turnout does not look or feel like a failure.
Book a room that is comfortable at seventy percent rather than one that only looks right at full capacity. Order catering for your realistic number rather than your optimistic one, and top up if needed. And be honest with yourself about the ratio - if two-thirds is what actually happens, plan for two-thirds. An event that looks well-attended at nineteen people is a far better experience than the same nineteen people in a room set for thirty.
