Tool
Random Meeting Slot Picker
Draw fairly from the slots that actually work for everyone — intersection first.
Random Meeting Slot Picker
Slots must match one of: Mon 9am, Mon 11am, Mon 2pm, Mon 4pm, … through Fri 4pm.
Paste everyone's availability, intersect it, and draw at random from the slots that work for all of them. When the intersection is empty, the tool says so rather than proposing a near-miss.
The random draw is the least important part and is included for a specific reason: among slots that are all genuinely valid, choosing at random stops the meeting drifting toward whatever suits whoever replied first.
Everything interesting happens in the intersection, which is a set operation rather than a probability question.
How the Random Meeting Slot Picker works — and why it's fair
Each person's availability is parsed into a set of slot labels from a fixed twenty-slot week — five days by four times. The tool then computes the intersection: the slots present in every single person's set. That is a strict AND, not a majority vote and not a best-fit score.
Strictness is the design decision. A tool that ranked slots by how many people could make them would produce an answer in every case, and that answer would routinely exclude somebody. Since the whole purpose is to find a time everyone can attend, a slot that misses one person is not a worse answer — it is not an answer.
When the intersection has more than one slot, the tool picks uniformly among them. This is genuinely useful and genuinely minor: all the slots in the intersection are equally valid by definition, so any of them would do, and randomising removes the small bias toward the first slot in the list, which in practice means the slot that suits whoever set up the poll.
The empty-intersection case is the common one for groups above about five, and the honest output is that no slot works. The right responses are to shorten the meeting, to split it, or to accept that somebody will miss it and pick deliberately rather than pretending the tool found something.
The slot grid is fixed at twenty labels rather than free text, because a free-text availability field means one person writing "Mon 9" and another writing "Monday 9am" and an intersection of zero for a reason that has nothing to do with anyone's calendar. A fixed vocabulary is a real constraint and it is the one that makes the intersection trustworthy.
Nothing is transmitted. The availability lists you paste stay in the page — which matters, since a set of calendars is a reasonably sensitive thing to hand to a website.
When the Random Meeting Slot Picker is fair — and when it is not
What it does guarantee
- The intersection is strict: a slot is proposed only if every single person listed it.
- Among valid slots, the draw is uniform, so no slot is favoured by its position in the week.
- An empty intersection is reported as empty rather than filled with a near-miss.
What it does not
- It has no notion of preference or priority — a slot someone hates but listed is as valid as one they wanted.
- It treats everyone as equally required. There is no way to mark one person optional.
- The slot vocabulary is fixed at twenty labels, so it cannot express a calendar with finer granularity.
Two worked examples
3 people, overlapping availability
- Ana lists 4 slots, Ben 3, Cleo 3.
- The intersection is 1 slot: Wed 2pm, which all three listed.
- With only one valid slot the draw is trivial, and the tool names it.
6 people, no overlap
- Every slot is missing from at least one person's list.
- The intersection is empty and the tool refuses to propose anything.
- The honest options are a shorter meeting, a split meeting, or a deliberate decision about who misses it.
Meetings that have to include everyone
Small recurring meetings where attendance is genuinely required are the fit — a decision meeting, a retro, anything where a missing person means the meeting has to happen twice. That is precisely where a best-fit ranking is the wrong tool.
Cross-timezone teams hit the empty intersection constantly, and getting that answer explicitly is more useful than a scored list that quietly puts someone at 6am. It converts a scheduling problem into a structural one, which is what it actually is.
Study groups and project teams use it for the small-group version, where the intersection is usually non-empty and the random draw among two or three valid slots is a genuinely convenient way to stop the discussion.
For choosing a random date or time without constraints, the random date generator and random time generator draw directly. For building a recurring rotation rather than picking one slot, the chore rota assigner handles multi-week scheduling.
Frequently asked questions
Why not rank slots by how many people can make them?
Because a ranked answer routinely excludes somebody, and the purpose is to find a time everyone can attend. A slot that misses one person is not a worse answer — it is not an answer.
Why randomise among the valid slots?
Because they are all equally valid by definition, and picking the first one biases toward whatever suits whoever set up the poll.
What if the intersection is empty?
The tool says so. The real options are a shorter meeting, splitting it, or deciding deliberately who will miss it.
Why can't I type my own slot labels?
Because free text produces 'Mon 9' and 'Monday 9am' as different slots, and an intersection of zero for reasons unrelated to anyone's calendar.
Can I mark someone as optional?
No. Everyone listed is treated as required. Leave optional attendees out of the list entirely.
Can it handle preferences as well as availability?
No — a slot is available or it is not. Preferences would require a scoring model, which is the thing this deliberately avoids.
Is my availability data sent anywhere?
No. It stays in the page and is discarded when you close the tab.
How many people can it handle?
Any number, though the intersection shrinks rapidly with group size. Above about six people, an empty intersection is the usual result.
Does it cover weekends or evenings?
No, the grid is five weekdays by four daytime slots. That is a deliberate limit rather than an omission.