How to find a timethat works for everyone
“Find a time that works for everyone” sounds like a wish, but it's really a consensus problem — and consensus problems have a method. The trick is to make everyone's availability visible in one place, capture more than a flat yes/no, and be honest that past a handful of people, “works for everyone” usually means “works for the most people.” Here's how to find that overlap quickly.
Capture availability once, from everyone
The overlap only appears when you can see everybody's constraints in one place. Trying to hold five people's schedules in your head — or reconstruct them from a thread — is where consensus goes to die. Put the candidate times on one shared surface and let each person mark themselves against all of them at once. You want every response in the same view, not scattered across replies.
Treat "maybe" as its own answer
Yes-or-no is too blunt for real life. Plenty of people can make a time if they have to, but would rather not — and that information is the difference between a good time and a resented one. A three-way answer (Available / If-need-be / Busy) surfaces the slot that's a genuine yes for the most people, and gives you a fallback that's at least workable when no perfect slot exists. When you tally, weight a clear 'yes' above a reluctant 'maybe.'
Let timezones convert themselves
Across timezones, 'the time that works for everyone' is a moving target: 3pm for you is 9am for one person and midnight for another. Never make people do that math — it produces errors and quietly excludes the person who got it wrong. Show each participant the same slots in their own local time, so a 'yes' means what they think it means. This is the single biggest reason distributed groups end up double-booked.
Settle for the best real option, then commit
Past three or four people, a slot that's perfect for everyone usually doesn't exist — and waiting for it just delays the meeting. Aim for the option with the most clear 'yes' votes, confirm it, and move on. The goal isn't unanimous enthusiasm; it's a time the group can actually meet. Once you've picked it, lock it in on everyone's calendar so the consensus you worked for doesn't slip away.
Why availability polls beat “reply-all”
A reply-all thread makes you the human spreadsheet: you read each message, translate timezones in your head, and try to hold the overlap in memory. An availability poll does that work for you. Everyone marks the same set of candidate times on one link, and the overlap becomes obvious — the row of green where the most people are free. You stop being the coordinator and become just the person who reads off the answer.
That's exactly what Meetsched does: propose a few times, share one link, and everyone votes Yes / Maybe / No — each in their own timezone, no account needed. It scores every slot (weighting a clear yes above a reluctant maybe), recommends the best real option, and turns it into a calendar event with reminders so the time you found actually holds.
Find your group's time now
One link, Yes/Maybe/No, automatic timezones. Free — no account for you to try it, none for your group to vote.
Related reading: How to schedule a group meeting · Meetsched vs When2meet · Scheduling team meetings across timezones