Organize · Scheduling

Find a time the whole community can make

Members tick every day and slot that works, across two axes, and you get an availability heatmap instead of an endless does-8pm-work thread.

Organize CommunitiesGamers Multi-selectAvailability gridTimezonesPer-option emoji
What it showcases

Features most survey bots don't have

🗓️

Two-axis availability

Pick every day that works, then every time slot. Multi-select on both axes is exactly the right tool for a scheduling problem.

🌍

Timezone aware

A quick region question keeps a global community from talking past each other, so the winning slot is unambiguous.

✍️

Catches the exceptions

An optional note field captures the 'any day but the 14th' nuance a grid alone cannot express.

Thirty seconds flat

Tap the days, tap the slots, add a timezone, done. High turnout is what makes a scheduling poll actually work.

Worked example This template comes with a a weekly community game night example so you can see exactly how it plays. Edit the questions and content to make it your own.

Finding the best time for a community event is a “tick every option that works for you” problem across two axes: which days and which time slots. This template makes that a thirty-second tap-through and hands you an availability heatmap, instead of a message thread that loses replies and never converges.

Run it before any recurring or one-off event where the time is not fixed: the weekly game night, a raid, a community call, a tournament slot, a watch party.

The overlap is the answer

Members select every day that could work, then every time slot, then their timezone. You tally where availability overlaps and pick the slot that gets the most people in the room. An optional note field catches the constraints a grid cannot.

The example is a weekly community game night. Swap the event and the axes and it fits any group coordinating a shared time.

Variants

  • Specific dates: swap the weekday list for concrete calendar dates when you are choosing between real options.
  • Session format: add a question for duration or format (voice, stream, in-game) to plan more than the time.
  • Cadence check: ask how often people would attend to size a weekly versus monthly event.
  • RSVP follow-up: once the slot is set, follow with a simple yes/no RSVP.
How to run it

Live in a few minutes

  1. 1

    Clone and name the event

    Swap the event placeholder for your game night, raid, community call, or watch party.

  2. 2

    Set the days and slots

    Adjust the day list and time slots to fit your audience, and tune the timezone regions to match where your members are.

  3. 3

    Publish and collect

    Members tick every day and slot that could work, add their timezone, and flag any hard constraints.

  4. 4

    Tally the overlap

    Read the heatmap, pick the slot that maximizes attendance, and post the winning time.

FAQ

Common questions

Why multi-select instead of pick one?

Asking people to select every option that works surfaces the slot that fits the most members. A pick-one poll forces a false choice and hides the real overlap.

Does it handle timezones?

Yes. A quick region question means a global community is not guessing whether 8pm means your evening or theirs. Adjust the regions to your audience.

Can members flag a conflict?

An optional note field catches the constraints a grid cannot: a date to avoid, a hard cutoff time, a recurring conflict.

Does it book the event for me?

It surfaces the best slot to you. It does not send calendar invites or hold time, so pair it with your calendar tool for the actual booking.

Use this template

Clone it into your community, swap in your content, and share it. No building from scratch.