ReadyRoll

A lightweight scheduling board for groups that meet regularly.

ReadyRoll helps recurring groups keep track of who can make which dates, without making everyone create an account. A host creates a shared date range, people mark availability, and the group can see the best upcoming dates without digging through chat.

It is live, early, and deliberately small: enough structure to solve the planning problem without turning casual meetups into admin.

Open ReadyRoll

Why this exists

Recurring groups often need more than a one-off poll, but less than a full calendar system. Chat is good for conversation but bad at maintaining availability across weeks or months.

People reply at different times, answers get buried, and the organiser ends up asking the same questions every few days. ReadyRoll gives the group a shared view of availability without replacing the places they already talk.

Why accountless?

Most casual groups do not need another login just to find a date. ReadyRoll uses links and tokens instead of requiring accounts. This keeps planning lightweight and avoids collecting personal profiles for basic scheduling.

The trade-off is that links need to be managed carefully and some persistent group features are easier with accounts. The long-term direction is to add optional accounts alongside the accountless flow, not replace it.

What ReadyRoll does

Create a planning board with a date range

Set up a shared board covering several weeks or months. Give it a name like "Game Night" or "RPG Session" and generate invite links.

Collect availability across weeks or months

Participants mark availability across the entire date range, not just one meeting at a time.

Let people vote Yes / Maybe / No

Participants can update their votes as plans change. Votes are saved against their participant token.

Show perfect days and best alternatives

ReadyRoll calculates which dates work for everyone, and highlights the best alternatives when perfect days are not available.

Mark planned days

The host marks dates as planned once the group has decided. The board can continue to be used for future planning.

Extend or reuse the board over time

Hosts can extend the date range or reuse the board rather than starting from scratch each time.

Discord bot integration

Connect the board to a Discord channel for group visibility and quick access.

How it works

  1. Host creates a planning board

    The host sets up a board with a rolling date range and receives an admin link for managing it.

  2. Participants join by link

    Each participant receives a unique link. No account, no password, no signup form.

  3. Availability builds over time

    Participants mark availability across the date range and can update votes as their schedule changes.

  4. Best dates surface automatically

    ReadyRoll shows which dates work for everyone, and highlights the best alternatives.

  5. Host marks planned days and continues using the board

    Once a date is chosen, the host marks it as planned. The board stays active for future planning.

Built for group chat

ReadyRoll does not try to replace the places groups already talk. The Discord bot lets a group connect an event to a channel, check status, view planned days, and send people back to the voting page when needed.

Where ReadyRoll is heading

Roadmap is subject to change based on usage and feedback.

  • Better group-chat support

    Improve the Discord bot with clearer summaries, reminders, and board visibility. Explore support for other group-chat tools such as Slack.

  • Richer planning boards

    Add features like notes, time preferences, location tracking, and better recurring date management.

  • Optional accounts

    Add accounts for people who want saved groups, history, and preferences, while keeping the current accountless flow available.

  • Stronger organiser tools

    Improve board management, participant controls, and organiser workflows.

Technical notes

  • Next.js
  • TypeScript
  • Tailwind CSS
  • Supabase
  • Vercel
  • Discord Interactions API
  • Link/token participation model
  • Server-side Supabase access