WoW raid management: a practical guide for guild officers

Most raid leaders never decide to "do raid management." They start with a Discord channel and a Tuesday night, and a year later they're the person who knows who owns which alt, who has missed three weeks in a row, and why the Thursday team has two healers too many. This guide lays out what that job covers and where each piece tends to break.

What raid management covers

Strip away the tooling and there are four jobs.

1. Signups: who plans to be there, and in what role.
2. Attendance: who was actually there.
3. Roster: which characters belong to which team, and what they play.
4. Progression: which bosses are dead, on which difficulty, and how fast.

Recruiting sits on top of these, and it works the same way as the roster job, only from the outside.

Each of these is easy alone. The trouble is that they depend on each other. A signup is only useful if you know the character's role. Attendance only means something against the nights the team was supposed to raid. Progression needs to know which team made the kill. If those live in four different places, somebody is copying data between them every week.

Signups: five answers are enough

A yes/no signup hides most of what you need to know on Tuesday afternoon. The set that works in practice has five states:

• Attending
• Tentative
• Late
• Bench
• Absent

Tentative and Late are the useful ones. "Tentative" tells you to line up a backup before pull time instead of at it. "Late" lets the group plan the first pulls around who is missing. Bench is a decision the officers make, not the raider, so it should appear as its own state rather than getting folded into Absent.

Role counts matter more than headcount. Mythic raids take 20 players, and Normal and Heroic flex between 10 and 30. A roster of 20 attending players can still fail if five of them are healers. Show the count per role next to the signup list so the problem is visible at a glance, and set a target (many Mythic teams run 2 tanks and 4 or 5 healers) so it is obvious when the group is short.

One more rule that saves arguments: set a signup cutoff and say it out loud. Raiders who change their answer six hours before the raid should tell an officer, since nobody is watching the button.

Roster: track characters, not people

The player who logs in is not the same record as the character on the raid. One person has a main, two alts and a Delve character. Another has a second account. If your roster is a list of Discord names, you can't answer simple questions like "which of Sam's characters is geared for Heroic?"

A character-based roster needs, at minimum:

• Name, realm, class and spec
• Role (derived from spec, so you don't type it by hand)
• Item level and, for Mythic+, a rating
• Which team the character is on, and how it is used there (core, fill, bench, trial)
• Which player owns it, so alts roll up to a main

Item level and rating go stale in days. If somebody has to type them in, they won't be right for long. Pulling them from Blizzard's and Raider.IO's public data is a better habit than asking people to update a sheet.

Attendance: record it after the raid, separately from signups

Signups are intent. Attendance is what happened. Mixing them up is a common mistake in homemade systems: the Attending column gets used as proof of presence, and then nobody can say who no-showed.

Mark attendance once, after the raid, using more than a present/absent tick. A usable set is:

• Attended
• Late
• Benched
• Excused
• No call, no show
• Did not attend

Each status answers a different question. A benched player followed instructions and shouldn't be penalized. An excused absence (told you a week ahead) shouldn't drag down a percentage either. A no-show without a word deserves a different conversation than an announced absence. Our guide to tracking attendance goes through the math in more detail.

A Warcraft Logs report is a good cross-check, since it lists everyone who was in the group. It can't tell you who sat out on purpose, and it knows nothing about nights where the team didn't log.

Progression: record kills by difficulty

Progression tracking looks like bookkeeping, but it answers the question every officer eventually gets asked: "are we improving?" Record each boss kill with a date and difficulty (Normal, Heroic, Mythic) per team. A grid with bosses down the side and difficulties across makes stalls obvious. If the team has been at 5/8 Heroic for six weeks, you want to see that before the raiders start asking about it.

Where this breaks as the guild grows

One team of 20 can run on a pinned message and one shared sheet. The cracks show up in a predictable order.

1. Signups scatter. Reactions in one channel, replies in another, a DM to an officer.
2. The sheet forks. Somebody copies the tab for the alt night and the two drift apart.
3. Alts break the numbers. A raider attends on an alt and the main gets marked absent.
4. History disappears. Attendance lives in an officer's memory until that officer burns out.

Asking officers to be more disciplined doesn't help. What does help is one record per character, with signups, attendance and kills attached to it. Most dedicated tools, whether they started as a Discord bot or a web app, are built around that. If you run more than one team, the problems compound; we wrote about that in running multiple raid teams in one guild.

A weekly routine that works

This is the loop a lot of officer teams settle into, whatever tool they use.

1. After the raid, mark attendance and record any kills. Do it the same night, while you remember who left early.
2. Early in the week, check next raid's roster against the role targets. Fix gaps while people still have free evenings.
3. A day or two before the raid, nudge everyone who hasn't answered.
4. On raid day, confirm the bench and tell the people who aren't starting.
5. Once a month, look at attendance trends and have the awkward conversations early.

Where RaidOps fits

We build RaidOps, so weigh this section accordingly. It is a free web app for Retail guilds that covers the four jobs above in one place: a character roster with teams, five-state signups with role counts, an attendance grid with the statuses listed earlier, and a boss-kill grid by difficulty. A Discord bot posts each raid in the team's channel with signup buttons. You can click through all of it in the demo without signing up.

It won't suit every guild. It supports Retail only, and it doesn't replace loot tools or log analysis. The comparison with Raid-Helper lays out where each one makes more sense.

Frequently asked questions

What is raid management in World of Warcraft?

Raid management is the work of organizing a raid team: collecting signups, balancing roles, tracking attendance, maintaining the roster and recording boss kills. Officers do it with spreadsheets, Discord bots or dedicated web apps.

What is the best tool for WoW raid management?

It depends on the size and needs of your guild. Discord bots such as Raid-Helper are strong for signups, WoWAudit is built around gear and loot, and RaidOps puts rosters, attendance and progression in one app. We compare them in our roundup of WoW raid management tools.

Can Discord alone manage a raid team?

For one team, yes. A signup channel and a pinned schedule work fine. Discord has no memory of who attended or which alt belongs to whom, so attendance and roster history usually need a second tool once you have more than a couple of teams.

How do I stop raiders from forgetting to sign up?

Make the signup a single click in the place they already look, show the role counts so gaps are visible, and message the people who haven't answered a day or two ahead. Reminders from a person work better than another bot ping.

Is RaidOps free?

Yes. RaidOps has no paid tier and no features behind a paywall. Donations cover hosting.