How to run raid signups and a roster in Discord

To run raid signups in Discord, keep a table with one row per player (role, class, availability) that members fill in with a slash command and officers query to see the roster. A signup sheet answers three questions: who's coming, in what role, and who's still missing. Discord servers usually handle it with a reaction poll (fast, but you can't record a role or a class), a Google Form (good data, but members leave Discord to fill it in) or an event bot.

Start with the event bot question, because it decides everything else.

First: do you need an event bot instead?

If you're scheduling a specific event and want an RSVP button on the post, reminders before it starts and timezone handling, use an event bot. Raid-Helper is the usual pick for MMO raids, and Apollo and Sesh handle general events with calendar sync. They do that job better than a table, and CordBase doesn't post events or send reminders at all.

A signup table earns its place when the list outlives one event: a standing roster of who plays which role, availability for the month, attendance across a season, or signups with fields an event bot doesn't ask for.

Set up the signup table

This uses CordBase, which we build. It takes a few minutes.

1. Sign in at cordbase.gg with Discord, pick your server, and add the bot when the dashboard asks.
2. Install the Raid Signup template. It has player (member, required), role (Tank, Healer, DPS or Flex, required), class (text), available (true/false) and signup date.
3. The command is named after the table, so you'll get /raid-signup. You can rename the slug on the table's edit page if you want something shorter, like /signup.

For a non-raid event, create your own table instead. A game night signup might have name (text), member, game (a choice list), bringing a guest (true/false) and notes.

Members sign up from Discord

/raid-signup add player:@Ari role:Healer class:Druid available:True signup_date:2026-10-17

Discord shows a member picker for player, a menu for role and a true/false toggle for available, so nobody types "heals" or "healz". The row is posted in the channel so everyone sees it.

If someone's plans change, they update their row instead of signing up twice: /raid-signup update row:Druid available:False. Start typing in row and pick from the list. The search runs on the table's first text column, which is class in this template; add a name column if you want to find people by name.

Officers check the roster

• /raid-signup query role:Healer available:True lists available healers.
• /raid-signup query player:@Ari shows one person's signups.
• /raid-signup view row:Druid shows a single row in full.

Filters combine, and results show the newest signups first, up to 25 at a time.

Permissions

By default anyone can do anything, including delete. For a signup sheet:

• Members get write, so they can add and update rows.
• Officers get admin, so they can remove signups.

Note that write access covers every row, not just a member's own, so this works best in servers where you trust people not to edit each other's signups. Discord Administrators always have full access.

Keep attendance history

Signup tables keep rows until someone deletes them, so they double as a record. For proper attendance tracking, add a second table with member, event and date columns and log who actually showed up. On a paid plan you can export it to CSV at the end of a season, or schedule a weekly post with the row count.

Limits

• Free: 2 tables, 100 rows each. That's a signup table and an attendance table for a small group. Pro ($8/month) removes the table limit and allows 10,000 rows per table.
• Up to 25 columns per table, and choice lists should stay at 25 options or fewer.
• Tables are created on the web, not from Discord.