How to find a meeting time for a large group without a reply-all storm
A practical method for getting twenty, fifty or more people to a single time: narrow the options first, ask once, set a deadline and decide.
Published 23 October 2026
Finding a time for five people is a conversation. Finding a time for fifty is a logistics problem, and it goes wrong in a predictable way. Someone sends an open question to the whole list. The first dozen replies each suggest a different day, and the next dozen reply to the replies. Three weeks later the meeting still has no date and half the group has stopped reading the thread. The method below is the opposite of that. It works for a parents' committee, a volunteer crew, a department of forty or a society with two hundred members, and it rests on one idea: the organiser does the narrowing, and the group does only the choosing.
Step one: narrow the options before you ask anyone
An open question ("when suits everyone?") invites fifty answers in fifty formats. A closed question ("which of these four times?") invites fifty answers in one format, which you can count. So the first job is to get from infinite possibilities to a handful of candidates, and to do it alone, at your desk, before a single message goes out.
Start with the fixed constraints. The room is free on Tuesdays and Thursdays. The treasurer is away the second week. School pick-up rules out anything between three and four in the afternoon. The speaker can only do evenings. Write these down and strike out every slot they eliminate. For most groups this removes more than half the week without asking anybody.
Then look at the pattern of the group. A workplace group has its best overlap mid-morning and early afternoon on Tuesday to Thursday. A club of working adults meets in the evening or at the weekend. A group spread across continents has a narrow overlap you should map first (the time zone guide shows how). Pick four to six candidate slots inside the pattern, on different days where you can, and spread across at least two weeks so that one bad week does not sink everything.
Step two: ask once, in a form that can be counted
The ask should be one message, sent to everyone at the same moment, containing the candidate slots, the way to answer, and the deadline. The way to answer matters more than people expect. If you say "reply with your preference", you will get prose, and prose has to be read, interpreted and tallied by hand. For fifty people that is an evening of work and a spreadsheet nobody trusts.
Ask for a ranking instead of a yes or no. "Yes" to three slots tells you nothing about which of the three is painless and which means a cancelled dentist appointment. A first, second and third choice, plus "also fine" and "cannot do", gives you enough to find the slot that is most people's good option rather than the slot that is merely tolerable to the largest number. The guide to why ranked voting beats a yes/no grid has a worked example. Whatever tool you use to collect answers, make sure it does the tally for you, so that the fiftieth reply costs you nothing more than the first.
A workable template, short enough to read on a phone:
- One line on what the meeting is for and how long it will run.
- The four to six slots, each with day, date, time and time zone.
- How to answer, in one sentence, with the link if there is one.
- The deadline, as a day and a time, not "soon".
- What happens next: "I will confirm the time on Friday morning."
Send it through the channel the group already reads, not a new one. Asking people to join a new platform to answer a scheduling question loses a tenth of them before you start.
Step three: set a deadline and hold it
Large groups respond in a burst and then a trickle. In practice something like half the replies arrive in the first day, three quarters within three days, and the rest dribble in for as long as you let them. Without a deadline the trickle never ends, because there is always one more person who might answer tomorrow.
For a group of twenty or more, three to five working days is about right. Shorter than two and the people who check messages weekly miss it; longer than a week and the early responders have forgotten they answered. Put the deadline in the first message and send exactly one reminder, a day before it, addressed to the whole group rather than to the stragglers by name.
When the deadline passes, stop. You are not waiting for everyone; you are waiting for enough. For a decision that binds the whole group, a response from two thirds is plenty, and the slot that wins among two thirds almost always wins among the full set too.
Step four: decide, announce, and do not reopen
Look at the tally and pick. Usually one slot is clearly ahead. Sometimes two are close, and the tiebreak should be the one with fewer "cannot do" answers, because a meeting that excludes six people is worse than one that is a second choice for ten. Occasionally the numbers show that no slot works for a person you actually need, such as the chair or the speaker, in which case their constraint outranks the vote, and you should say so plainly when you announce.
Announce the result as a decision, not a proposal. "The meeting is Thursday 14 May at 19:00; calendar invitation to follow" closes the question. "Looks like Thursday is winning, any objections?" reopens it, and with fifty people there is always an objection. Send the calendar invitation the same day, because an event in a calendar is accepted in a way a line in a chat never is.
Then hold the line. Someone who did not vote will ask to move it; the honest answer is that the time was chosen by the people who answered, and moving it now would undo their choice.
A worked example
The fixtures officer of a running club needs a planning meeting for forty-two members. Constraints: the clubhouse is booked on Mondays and Wednesdays, the head coach cannot do Fridays, and daytime is out because most members work. That leaves Tuesday, Thursday, Saturday and Sunday evenings. He picks five slots across two weeks and posts them in the club chat on a Monday with a deadline of Thursday at 18:00.
By Tuesday night, twenty-three members have answered. A single reminder on Wednesday brings the total to thirty-one. At the deadline, the second Thursday leads on first choices and has only two members unable to attend; the first Sunday has more "also fine" answers but seven cannot make it. He picks the Thursday, posts the decision on Thursday evening, and sends the invitation. Thirty-four people turn up, including several who never voted, because the invitation in their calendar did what the chat could not. The thread that would normally have run for three weeks never started.
The checklist
- Collect the fixed constraints and strike out the slots they eliminate.
- Choose four to six candidate slots on different days across two weeks.
- Send one message with the slots, the way to answer and the deadline.
- Ask for a ranking, and collect answers somewhere that counts them for you.
- Send one reminder, to everyone, the day before the deadline.
- Decide at the deadline on the answers you have, with the tiebreak going to the slot that excludes fewest.
- Announce the decision, send the calendar invitation the same day, and do not reopen.
Steps two and four are the ones a tool can carry for a group of fifty. FINDaTIME takes the four to six slots you narrowed down to and lets each member rank them from a private link that arrives by email. It keeps a running tally with the count of people unavailable against every slot, so the tiebreak in step four is already on the page when the deadline passes. Create a free poll once the constraints are struck out, and the fiftieth reply really will cost you nothing.
