Recurring raid signups in Discord: set the week once
Recurring raid signups in Discord without the weekly chore: standing raid nights, a nudge when a sheet is missing, reminders, cutoffs and repeating events.

In this post
Recurring raid signups work best when the week is set once and the bot handles the reminders. In GuildPro you set standing raid nights per team. The bot warns the signups channel when a night has no sheet, one click fills in the form, and reminders and the cutoff run on their own. Raid sheets still take one press from an officer. Dungeon nights, socials and other events can repeat and post themselves.
Why do recurring raid signups go wrong?
Because “someone posts the sheet on Sunday” is a job with no owner. It works for three weeks. Then the officer who does it is away, the sheet goes up on Wednesday for a Thursday raid, half the raid has made other plans, and the night is short.
The fix isn’t a better reminder in an officer’s head. It is writing the week down once, so the guild’s tools know when you raid and can say when something is missing. Our raid night schedule post covers how many nights to run. This one is about making those nights run themselves.
It matters more from 9 December. WoW Forever opens three raids at once: Barrow Deeps for 10 players, Hyjal Summit for 20 and Onyxia’s Lair for 40, per Wowhead’s raids hub. Blizzard has said Tier 1 is split across all three, per Wowhead’s summary of the interview, so plenty of guilds will run more than one raid a week. Three sheets a week is exactly where “someone will post it” falls apart.
What is a standing raid night?
A weekly slot your guild always raids, saved once: day, time, team, instance and size. In GuildPro an admin adds them on the Raid teams page, under Raid schedule. Times are in the guild’s timezone.
| Field | What it does |
|---|---|
| Team | A raid team, or the whole guild |
| Day and Time | The weekly slot, on the guild’s clock |
| Instance | Optional, for example Hyjal Summit |
| Label | A name for nights that aren’t a raid |
| Notice | How many days ahead (2 to 14) GuildPro starts telling you the night has no sheet |
| Size | The raid size the sheet will use |
Once a night is saved, the calendar shows it as planned until a sheet exists, and the guild dashboard shows “no sheet” against it. The full walkthrough is on the teams docs page.
Does GuildPro post raid sheets on its own?
No. It tells you a sheet is missing and fills in the form, and an officer presses the button. That is the honest answer, and it’s on purpose: the sheet is the one post an officer should look at before it goes out.
Here is what does happen on its own:
- When a raid night enters its notice window with no sheet, the Signups page shows it under Coming up, no signup yet, with a Post it button.
- Post it opens the raid form with the time, instance and size already filled in from the schedule. Nothing posts until you press Create and post.
- If an admin has turned on the No sheet up yet automation, the bot also posts a notice in your signups channel, with a Post a sheet button that opens the Signups page.
So the weekly job shrinks from “remember, write the sheet, post it” to “press the
button the bot just put in front of you”. Any sheet on that day counts, including one
posted with /raid, so the notice never nags about a night you’ve already handled.
If two teams raid the same night, give each its own raid night and its own signups channel on the Bot page. A sheet made for a team goes to that team’s channel. One thing to know: the missing-sheet notice looks at the day, so on a shared night, the first team’s sheet also quiets the second team’s notice. Check the Signups page on those nights.
What reminders can run each week?
Four automations cover a raid week: the missing-sheet notice, a reminder before the raid, DMs to people who haven’t answered a roster, and closing the sheet. Every one is off until an admin turns it on, on the Automations page.
| Automation | When | What it does |
|---|---|---|
| No sheet up yet | 1 to 14 days before (the raid night’s own notice wins) | Posts a notice with a Post a sheet button in the signups channel |
| Raid starts soon | 15 minutes to 1 day before | Posts under the sheet: signed, tentative, out, and how many short. Optional @here |
| Chase the silent | 30 minutes to 7 days before | DMs people on a posted roster who haven’t answered, once a day until they do |
| Close the sheet | From the start to 6 hours after | Closes signups, so the buttons stop working |
Two settings keep it polite: quiet hours, when no automation posts, and a daily cap on how many messages automations send. Both are under The clock on the same page. The automations docs list every option.
What signup cutoff should a recurring raid use?
Close signups when the raid starts, and ask for changes 24 hours before. The bot can enforce the first. The second is a rule your raiders agree to.
- Add each raid night on the Raid teams page, with team, instance and size
- Give each night a notice of 5 to 7 days
- Pick a Signups channel on the Bot page (per team, if you run several)
- Turn on No sheet up yet
- Turn on Raid starts soon, 1 to 2 hours before
- Turn on Close the sheet, 30 minutes after the start
- Set quiet hours for your guild’s night-time
- Pin your signup rules: answer by 24 hours before, press Late or Can’t make it if plans change
Close the sheet stops new answers once the raid is under way. That keeps the record clean: people who pressed Late or Can’t make it before the start count as excused in attendance, and the sheet stops changing after the pull. The default is 30 minutes after the start, which covers a late first pull.
A 24-hour “please don’t change” line is still worth writing down, because the comp is usually built the night before. Our raid signup rules post has wording to copy.
Can dungeon nights and socials repeat on their own?
Yes. Events that aren’t raids can repeat weekly or monthly, and each one posts itself a set number of days ahead. This is the part of GuildPro that is fully hands-off.
When you create an event on the Events page, open More options and set Repeat:
- Every week
- Every month, same date
- Every month, same weekday (for example the 2nd Saturday)
Then pick Post repeats 1, 3, 5 or 7 days ahead. The bot posts each one with the same settings, such as its role slots, reminders and channel. Repeating events are listed under Repeating on the Events page, each with a Stop repeating button. Events already posted stay up when you stop.
Events have their own reminders that don’t depend on any automation: a DM to people going (15 minutes to 1 day before), and an optional “get on” DM at the start.
Could you run a raid as a repeating event with Tank, Healer and DPS slots? You could, but it wouldn’t be a raid sheet. Event sign-ups don’t feed the comp builder or the attendance page. For a raid you want counted, post a raid sheet.
What does a raid week look like once it’s set up?
Mostly quiet. Officers press one button a week per raid night and read the reminders.
| Day | What happens | Who does it |
|---|---|---|
| 5 days before | “No sheet up for Hyjal Summit” in #raid-signups | The bot |
| Same evening | Post it, check, Create and post | An officer, 1 minute |
| Raiders’ week | Sign up, press Late or Can’t make it if plans change | Raiders |
| Day before | Build the comp, post the roster | Raid leader |
| Hours before | DMs to anyone on the roster who hasn’t confirmed | The bot |
| 1 hour before | Reminder under the sheet with the count | The bot |
| 30 minutes in | Sheet closes | The bot |
| After the raid | The night is matched to its sheet once the addon’s record uploads | GuildPro |
The weekly social or dungeon night posts itself in the middle of all that.
GuildPro’s raid nights, signup sheets, automations and repeating events are free for every guild. Set the nights once on the Raid teams page, turn on the automations you want, and the week mostly runs itself. Set up your guild.
For everything else to have in place before the raids open on 9 December, see the WoW Forever guild checklist.
FAQ
Does GuildPro post raid signup sheets automatically?
Not raid sheets. It knows your standing raid nights, warns the signups channel when a night has no sheet, and fills in the form for you, so an officer posts it with one click. Non-raid events can repeat and post themselves.
How far ahead should a recurring raid sheet go up?
Far enough for raiders to plan their week. Many guilds post 5 to 7 days ahead. In GuildPro each raid night has its own notice, from 2 to 14 days.
Can the bot close signups at a cutoff?
For raid sheets, the Close the sheet automation closes signups from the start time to 6 hours after it. Events can have their own Signups close at time.
Can the bot remind people who haven't signed up?
Yes. Raid starts soon posts a reminder under the sheet with how many have signed and how many seats are left. Chase the silent DMs people on a posted roster who haven't confirmed.
Are these automations on by default?
No. Every automation is off until an admin turns it on, and there are quiet hours and a daily cap.