Group planning

How to pick a date everyone can actually make

Eleven people, one group chat, no date. Here is the method that ends it — and the three mistakes that keep it going.

Updated 2026-09-11 · 5 min read

Why the group chat can't decide

A group chat is a terrible decision-making tool, and it fails the same way every time: it asks an open question to everyone at once, with no deadline and no rule for what counts as a decision.

"When is everyone free?" has no answer. It invites each person to describe their whole calendar, in prose, to ten people who are not tracking it. Three people answer, one answers with a question, and the thread goes quiet for two days. Nobody is being difficult — the question is unanswerable.

The fix has three parts, and all three matter.

1. Propose, don't poll the void

Never ask "when works?" Ask "Thursday the 15th or Saturday the 17th?"

Two or three concrete options is the sweet spot. One option isn't a choice and gets read as a summons; five options recreates the original problem with extra steps. With two or three, replying costs one tap and no thought, which is the entire game.

Pick the options yourself, as the organizer. This feels presumptuous and it is not — everybody in that chat is quietly hoping somebody else will decide.

2. Put a deadline on it, out loud

"Let me know" is not a deadline. "I'm booking Wednesday night" is.

State the decision date in the same message as the options. It converts an open-ended social request into a small, closeable task, and it gives you permission to decide without anyone feeling steamrolled — you told them when.

A good rule of thumb: the deadline is halfway between when you ask and when the thing happens, and never less than 48 hours before you have to book anything.

3. Announce the tiebreak rule before you need it

Say how it resolves: "most votes by Wednesday wins." Then the person who didn't vote has no standing to reopen it, and — more importantly — you don't have to litigate it. The rule did it, not you.

If it ties, break it toward whoever has the least flexibility: the friend with a newborn, the one working weekends, the one travelling in. They're the constraint; the rest of you are not.

The mistakes that keep it going

Asking for availability instead of a commitment. "I'm free either" is not an RSVP. It's a person deferring to the group, and a group made entirely of deferrers never decides. Ask "which one are you coming to", not "which could you do".

Letting a thumbs-up count. A reaction means "I have seen this message". It doesn't say how many people are coming, whether they're bringing someone, or whether they'll be there at seven. If you book a table off a count of thumbs-ups, you will be wrong, and usually in the expensive direction.

Re-opening after you've decided. Once it's locked, one person's "actually could we do Friday?" is a fresh negotiation for ten people. The answer is "we're locked for Thursday — catch you next time." Say it warmly and move on.

How far ahead to ask

It scales with how much of a production the thing is:

The follow-up nobody does

Two days before, send the details again — time, address, what to bring, whether there's parking. Not a nudge, just the facts.

Half of all no-shows are not flakes. They're people who said yes three weeks ago, never wrote it down, and have genuinely lost the thread. A single message the day before converts a surprising number of them back.

Doing this without the spreadsheet

This is the loop Whosly is built around: put up two or three times, everyone taps one from a link, and the plan locks itself in on your deadline — Float it is the feature name, and it settles the time without you having to referee it.

The part that matters for a group chat: the people you invite don't need the app or an account. They tap the link, pick a time, and say whether they're in — from whatever phone they already have. You get a live headcount of going, maybe and can't, with names rather than reactions.

RSVPing is free for everyone, always — no app, no account. On the free tier you host

three plans at a time and RSVP to as many as you like.

Common questions

How many date options should I give people?
Two or three. One reads as a summons rather than a choice, and five recreates the problem you're trying to solve. Two or three keeps replying to a single tap, which is what actually gets answers.
What if someone can't make either date?
Decide anyway, and tell them warmly that you'll catch them next time. A group that waits for unanimity never meets. The exception is the person the event is for, or the one whose constraint is genuinely immovable — build around them from the start instead of putting it to a vote.
How long before the event should I send the invite?
Three to five days for a weeknight drink, two to three weeks for a weekend dinner or birthday, six to ten weeks for anything with a booking or flights, and four to six weeks for a holiday gathering — November and December calendars fill far earlier than the rest of the year.
Do people need an app to RSVP to a Whosly plan?
No. You text one link and anyone can RSVP from any phone with no download and no account. Starting a plan and RSVPing are free on every tier.

Stop chasing the group chat

Put two dates up, let everyone tap one, and watch it lock itself in. Free for anyone to RSVP — no app, no account.

Get Whosly — free on iPhone
About Whosly. Whosly is an iPhone app for group plans, saved places and RSVPs. Anyone you invite can RSVP from a link on any phone, with no app and no account — that part is free for everyone, always. On the free tier you host three plans at a time and RSVP to as many as you like; multi-stop nights, Surprise mode and City Packs are Planner Pro. whosly.app

Keep reading