How to Plan a Group Activity Without 200 WhatsApp Messages

WhatsApp Event Planning August 22, 2026 13 min read By the Ontaym Editorial Team

Seven people, one park, nine days and a thread nobody wants to scroll back through. The message count is a symptom, and when you break it down the causes are not what anyone expects, because a quarter of the volume is the part you should keep.

Two hundred messages to eat some sandwiches in a park

Seven people wanted to do something on a Saturday. Not a wedding, not a conference. A picnic, possibly a game of football afterwards, in a park that everyone had already been to.

By the time it happened, the thread had run to something like two hundred messages. Nobody counted at the time, because nobody ever counts at the time.

The number is illustrative, not measured. It is the number people say when you ask them how bad it got, and it feels about right for a plan that took nine days and changed twice.

What is genuinely surprising is where the volume comes from when you actually break it down. It is not the arguing. The arguing is maybe fifteen messages, and half of them are funny.

The volume comes from four ordinary, well-intentioned habits, none of which anybody would describe as a problem. That is exactly why the thread keeps growing.

Where the messages actually come from

Take a plan for seven people that moved once and had one venue change. Sort the messages by what they were doing, rather than by who sent them.

You end up with roughly five categories, and the shape of the pile is not what you would guess.

Look at the last two rows before you look at anything else. Roughly a quarter of the thread is not admin at all.

That part is the reason the group exists. Any advice that trims it is bad advice, however tidy the result looks.

You are not trying to have a shorter conversation. You are trying to stop the conversation doing paperwork.

Source one: the open question

Here is the message that costs the most, and it looks like the politest thing in the thread.

"What does everyone fancy doing Saturday?"

Seven people, seven opinions, and each opinion is a legitimate contribution. Then people react to each other's suggestions, which is also legitimate, and now you are at twenty-five messages with no decision in sight.

The problem is arithmetic rather than manners. An open question multiplies by the size of the group, and then the replies multiply again as people respond to the replies.

A group of four survives this. A group of twelve does not, which is part of why so many people quietly dread group chats without being able to say exactly what went wrong.

It gets worse when the question is undecidable. "What should we do?" has no correct answer, so nobody can end it by being right.

Compare it with "picnic in the park at one, or football at three?" Two options, one reply each, done in seven messages.

Why open questions feel safer than they are

Nobody asks openly by accident. It feels like the considerate move, because a proposal can look like you are steamrollering everyone.

That instinct is real, and it is also expensive. The considerate version generates work for six other people, and the work lands as notifications during their afternoon.

There is a second cost that is harder to see. When there is no proposal on the table, opinions arrive unanchored, so they do not converge.

Twelve people saying "somewhere nice" is not progress towards a venue. Twelve people saying yes or no to one venue is.

Source two: the decision that never closed

This one is subtler, and it produces the most tired messages in the thread.

On Tuesday the group settles on the park. Nobody says so. It just becomes obvious from the last few messages that the park has won.

On Thursday somebody says "or we could do the river bit instead?" They are not being difficult. From where they are sitting, that question was never actually answered.

And they are right. A decision that only exists as a vibe in the recent messages is not closed, it has simply gone quiet.

So the venue thread restarts, and this time it costs more, because two people have to explain the reasoning again and one person is annoyed. That is thirty messages to re-agree something you already agreed.

A reopened decision is worse than a slow one. The first round is people thinking. The second round is people repeating themselves while suspecting they are repeating themselves.

What closing actually sounds like

Closing a decision costs one message. It has to be explicit, and it has to be boring.

"Right, park it is. One o'clock, the entrance by the cafe. Shout now if that breaks anything for you."

Three things happen in that message. The decision is stated as a decision, the details are attached, and there is one clearly signposted moment to object.

Without that last part it reads like an instruction, and groups of friends push back against instructions. With it, you have given everyone a proper exit and the silence afterwards means something.

This is the same move as giving a group event one source of truth, done at the level of a single question rather than the whole plan.

Source three: the update that gets repeated

Now count the messages that exist only because somebody missed something.

The time moved from one to two. It was announced once, on Wednesday evening, between a photo of a dog and a discussion about parking.

Three people missed it. Not because they are careless, but because a chat sorts by newest and only by newest, so the announcement sank the same way everything sinks.

Each of them asks separately, over four days. Each gets a full answer, sometimes from different people, sometimes with slightly different details.

That is one change, three retellings, and roughly twelve messages. If the plan changes twice and the group has ten people, this category alone can pass fifty.

The failure mode is worse than volume, though. Retellings drift, and a retelling with one wrong detail is more dangerous than no retelling at all, which is the thing that makes catching people up late in a WhatsApp plan such reliably miserable work.

The right-hand column is the one that catches people out. Nothing doubled. The two categories tied to both people and changes went up several times over.

Source four: counting people by hand

Somebody in your group is keeping a list. There is always somebody.

They are doing it because "who's in?" produces a thumbs-up, an "I'll try", a message that says "count me in for the picnic but not the football", and silence from four people.

All of those are real social signals. None of them is a headcount, and the difference matters as soon as you have to book something or buy food.

So the list-keeper starts chasing, and chasing generates messages in both directions. A nudge, a reply, a clarification, then a change of mind on Friday that undoes the lot.

Every one of those messages exists because there is nowhere for an answer to live except the conversation. The conversation is very bad at holding answers, since an emoji reaction was never designed to be an attendance record.

Worth being clear about the honest version of this. People change their minds, and that is fine, so the goal is not fewer changes but changes that do not each cost a round of messages.

What is not the problem

Two things regularly get blamed and should not be.

The first is the chatter. Jokes, tangents, a photo of somebody's terrible attempt at a picnic loaf, the ongoing bit about the one person who is always late.

That is the group being a group. Strip it out and you get a coordination channel, which is a thing nobody has ever enjoyed being added to.

The second is enthusiasm. Twelve people wanting to talk about a plan is not a failure of discipline, it is the plan working.

The target is narrow: messages that exist only because facts have nowhere to live. Everything else can stay.

The techniques, in the order they pay off

Four moves cut most of the volume. None of them requires announcing a new system, which matters more than it sounds.

The moment a group feels managed, people stop being funny in it. Then somebody adds the phrase "action points" and the thread dies of embarrassment.

1. Propose instead of asking. Replace "what shall we do?" with one concrete option and a real exit. "Picnic in the park, Saturday one o'clock, football after for whoever wants it. Any objections?" You have swapped seven opinions for six yes-or-no answers, and given the group something to react to instead of something to invent.
2. Offer two options, never five. When a proposal genuinely needs a choice, cap it at two. Two options fit in one screen and one decision, while five produce a discussion about the shortlist before anyone gets to the actual question.
3. Close decisions out loud. When something is settled, say that it is settled, in a message that does nothing else. "Park confirmed, one o'clock" reopens nothing later, and costs one message now against thirty in three days.
4. Batch your updates. Resist announcing each small thing as it arrives. One message a day carrying everything that changed is far cheaper than five messages carrying one change each, and it is much easier for a person catching up to find.
5. Put the facts somewhere they stop needing repeating. Time, place, meeting point, what to bring, who is coming. Once those live at one address that anyone can check, every future "what time again?" is answered with a pointer rather than a retelling.
6. Answer with the pointer, every time. This is the step people skip, because restating feels friendlier. Restating creates a second copy that can drift, and the second copy is how two people end up at different entrances of the same park.

Do the first three and the thread halves. Do all six and the remaining messages are mostly people being pleased about Saturday, which is the correct end state.

Why "just pin it" only gets you halfway

Pinning a message is the right first instinct and it is genuinely better than nothing. It creates a place to point at, which is most of the idea.

Its limit shows up the moment something changes. A pin is a photograph of the plan at one moment, so it is either edited, replaced, or quietly wrong.

Replace it and the people who read the first version never learn there was a second. They now hold old facts with complete confidence, which is worse than holding none.

A pin also cannot answer the two questions that generate the most chasing. It cannot tell you who is coming, and it cannot tell you when it was last true.

That is the specific gap between a message and a record, and it is why event details end up buried in a WhatsApp thread even in groups that pin diligently.

The poll trap

Polls deserve their own warning, because they look like the exact fix for source one and are only half of it.

A poll is excellent at closing one question at one moment. Three dates, one winner, twelve replies compressed into twelve taps. That is a real saving.

The trouble starts after it closes. A poll captures preference, not commitment, and those two things drift apart over a week.

Voting that Saturday works is a statement about your calendar. Saying you are coming is a promise, and the gap between them is the whole subject of saying you are going versus answering a poll.

There is a second failure that is easy to miss. A poll result is itself a message, so it sinks like every other message, and a week later somebody asks what the poll said.

Use polls for the choice. Do not expect them to carry the answer forward, and do not treat the vote count as a headcount.

A worked example, before and after

Same group, same picnic, same nine days. Once the expensive way, once the cheap way.

The expensive version starts on a Monday with "anyone free this weekend?" Nine replies establish that most people are free, which everyone already suspected.

Tuesday is spent on what to do. Three ideas, a tangent about a place that closed last year, and a soft landing on the park that nobody announces.

Wednesday somebody proposes the river instead, because the park was never formally decided. Twenty messages later the park wins again.

Thursday the time moves to two, announced once at eleven at night. Friday, Saturday and Sunday each produce someone asking what time it is.

By the following Saturday there have been two people at the wrong entrance, one person who brought food for a picnic that had become a barbecue, and an organiser who is glad it is over.

The cheap version starts differently. Monday: "Picnic in the park Saturday, one o'clock, entrance by the cafe. Football after for anyone who wants it. Any objections?"

Four people say yes, one asks about parking, one cannot make one but can make two. Tuesday morning: "Two o'clock then, everything else the same, that is confirmed."

Facts go on a page the group can open. From then on every question gets a link, and the thread goes back to being about whether anyone is bringing that dip again.

Same plan, same people, same changes. The difference is that facts stopped being transmitted and started being stored, an idea taken apart properly in the difference between a conversation and an event object.

This was specified a long time ago

The thing your thread is missing is not a clever new app feature. It was written down as a standard before most group chats existed.

It is called an event object, and the current specification is RFC 5545, published by the IETF in 2009. It is the reason a calendar file opens on every device you own.

What it defines is a set of named fields rather than a description. One start time, one location, one organiser, and for each attendee a participation status that can be needs-action, accepted, declined or tentative.

That last one is the interesting bit for our purposes. The default value is needs-action, which gives silence a name.

In a chat, the person who has not replied looks exactly like the person who is coming, the person who is not, and the person who last opened the app on Tuesday. That ambiguity is what forces a human to chase, and chasing is pure message volume.

There is a companion specification, RFC 5546, covering how invitations and replies travel between people. So the record, the invitation and the answer have all been formally defined for well over a decade.

None of which means you should send your friends calendar invites. It means the shape of the missing thing is known, and the gap is purely about where to put it socially.

What each technique is actually doing

It helps to see why these moves work, because then you can improvise instead of following a list.

Proposing rather than asking converts an open question into a closed one. Open questions scale with the group. Closed questions do not.

Closing out loud converts an implicit state into an explicit one. An implicit decision can be reopened by anyone in good faith, and it will be.

Batching converts many interruptions into one. The cost of an update is not the message, it is the seven people who look at their phone.

And moving facts out of the thread converts transmission into storage. A fact you transmit has to be transmitted again for every person who missed it, while a fact you store is read by whoever needs it, whenever they need it.

That last conversion is the one that keeps working as the group grows. The others reduce the volume, but this one changes what the volume depends on, which is why it matters most for plans running inside a genuinely huge group.

Things that sound like solutions and are not

A few popular fixes are worth naming, because they cost social capital and buy very little.

A second group chat for logistics. Now the facts are split across two threads and everyone has to remember which. You have added a routing decision to every message.

Asking people to keep it on topic. This works for about a day and makes the group less pleasant permanently. The chatter was never the problem.

Muting the group. Understandable, and it converts your quiet person into someone who will ask what time it is on Friday. Muting moves the cost, it does not remove it.

One person taking on all the admin. This does work, right up until that person is busy or annoyed. A plan that depends on one heroic organiser is one bad week away from collapse, which is a good chunk of why group plans fail in such predictable ways.

Announcing a new process. "From now on can we all..." is the fastest way to make seven people feel like colleagues. Change your own behaviour and let the group follow.

Doing this without being the group's manager

The techniques are easy. Applying them without becoming insufferable is the actual skill.

Keep the tone of the group. A proposal can be casual: "park, one o'clock, I'm bringing crisps" does the same structural work as anything more formal.

Always leave a genuine exit. "Objections?" and "shout if that doesn't work" are what stop a proposal from reading as a decree.

Never correct anyone's messaging habits in the group. If somebody asks a question that is already answered, answer it with the link and move on.

Protect the chatter actively. If the thread has gone quiet and administrative, be the person who posts the daft photo.

You are aiming for a group that plans quickly and does not notice why. Nobody should be able to point at the moment things got organised.

Where Ontaym fits

Ontaym exists for step five, which is the one you cannot do inside a chat.

An event gets one page holding the current time, the current place and who has actually said yes. It has an address you can drop into any conversation, and the answers do not require anyone to install anything or hand over their phone number.

Your group chat stays exactly where it is, doing the part it is genuinely good at. The facts stop being repeated, which is what removes the two categories that grow fastest.

That is a deliberately narrow scope. A ticketed event belongs somewhere built for selling tickets, and coffee with one friend needs nothing at all.

The number was never the point

Two hundred messages is a symptom, and it is a good one, because it is the first thing anyone notices.

What it tells you is not that your friends talk too much. It tells you that a conversation is being asked to store things it cannot store, and paying for that in repetition.

The test is simple. Look at the last plan your group made and ask how many messages would still have existed if the facts had lived somewhere findable.

The jokes stay. The logistics on the day stay. The excitement on Friday night stays.

Most of the rest turns out to be the same eight facts being carried around by hand, one person at a time, until Saturday finally arrives.

Frequently asked questions