dontflake.lol Start a plan
Guide · Scheduling

How to find a date everyone can make

“When works for everyone?” is the question that kills plans. It's too open, it's asked in the wrong format, and the answers arrive in an order that quietly corrupts them. Here's a better way.

Group scheduling is genuinely hard, and it's worth being precise about why, because the difficulty is mathematical before it's social. If each person in your group is free on roughly 40% of weekends — a reasonable estimate for an adult with a job, a family, or hobbies — then the chance that a specific weekend works for all of them falls off a cliff as the group grows. Four people: about a one-in-forty shot for any given weekend. Eight people: closer to one in fifteen hundred.

That's why asking “does the 14th work?” almost always fails for a large group. You're sampling one date at a time from a space where hits are rare. The fix isn't more persistence. It's changing the question.

The four failure modes of scheduling in a chat thread

Before the method, it helps to name what's actually going wrong, because each problem has a specific remedy.

1. The question is unbounded

“When works for everyone?” has an infinite answer space. People faced with an unbounded question either write an essay about their calendar or postpone answering until they have time to write that essay — which is to say, never. Every good scheduling question comes with a window attached: “which of these three weekends in March?”

2. Answers are sequential, so they contaminate each other

This is the subtle one. In a chat, the first person to answer sets an anchor. The second person reads it and answers relative to it — they emphasize their overlap and soften their conflicts, because being the obstacle feels bad. By the fifth reply, the group isn't reporting calendars anymore; it's converging on a socially comfortable answer. The date that emerges has nobody's explicit objection and two people's silent conflicts. Those two people become the “flakes” three weeks later.

The remedy is blind collection: everyone submits their real availability without seeing anyone else's, and the overlap is revealed only once the last person is in. Same people, same calendars, dramatically more honest data.

3. Preferences get mixed in with constraints

“I'd rather not do the 8th” and “I physically cannot do the 8th” look identical in a chat message and are completely different facts. Ask explicitly for constraints — the days you cannot make — and handle preferences in a separate, later, much cheaper conversation. Groups that conflate the two spend weeks optimizing for someone's mild preference while a hard conflict sits undiscovered.

4. There's no deadline, so there's no decision

An open question with no deadline is a question that stays open. Every availability request needs an explicit “reply by Thursday and we'll lock it Friday,” and the deadline needs to be short — two to four days. Longer deadlines don't get more responses; they get later responses.

The one-message template

Send exactly this, once, instead of a thread: “Trying to lock our weekend. Here are the four weekends in October. Mark the ones you genuinely can't make — link below, takes 30 seconds. I'll post the winner Friday and book it.”

It bounds the window, asks for constraints rather than preferences, sets a deadline, and names who's deciding. Four fixes in four sentences.

The method, in five steps

  1. Pick a window, not a date. Three to six candidate dates, or a two-to-four week range. Wide enough to contain a real overlap, narrow enough that nobody has to think about December.
  2. Ask for hard conflicts only. “Mark what you can't make.” Inverting the question is a real trick: people are much faster and more accurate at recalling blocked days than at constructing free ones, and it produces less negotiation.
  3. Collect blind, with a deadline. Nobody sees the results until everyone has submitted. Chase the last person directly and privately — group chases are ignored by everyone, including the person being chased.
  4. Reveal the overlap and take the best one. Usually a clear winner appears. If two dates tie, the organizer picks; do not put it back to the group.
  5. Lock it and send calendar invites the same hour. A date that isn't on calendars isn't locked, it's just discussed.

What to do when there is no overlap at all

Sometimes the honest answer is that no date works for all eight people. This is the moment most plans quietly die — the organizer sees the mess, feels defeated, and stops replying. Don't stop. You now have exactly four options, and they're all better than nothing:

Small tactics that reliably help

Why the tool matters slightly less than the format

Any structured collector beats a chat thread — a poll, a shared grid, a scheduling app. What actually produces the result is the format: bounded window, hard conflicts only, collected blind, fixed deadline, one person decides. Get those five right with a spreadsheet and you'll beat a group using the best tool in the world with the wrong process.

Next, decide who has the authority to call it: who should organize, and what that role actually covers.

Blind availability, built in

dontflake.lol runs this exact method: one link, everyone marks the days they can't make, and the overlap stays hidden until the last person submits. No accounts, no app, free.

Start a plan