How to be a raid leader in WoW: before, during, after
How to be a raid leader in WoW: the prep before the pull, the calls and wipe recovery during it, and the debrief after, with a pre-raid post to copy.

In this post
A raid leader’s job splits into three parts: before, during and after. Before: a full roster, a plan for each boss and a pre-raid post. During: short calls, one voice in charge and a calm reset after each wipe. After: a short debrief and a record of who came. Hand everything else to assist leaders.
What does a raid leader actually do?
A raid leader owns raid night: who comes, what the plan is, the calls during each pull, and when to stop. Loot rules, recruitment and guild direction belong to other officers, even if one person wears several hats. Our guild officer roles post shows how the jobs split.
The job grows with the raid. In WoW Forever the first raids open on 9 December: Barrow Deeps for 10 players, Hyjal Summit for 20 and Onyxia’s Lair for 40, per Wowhead’s raids overview. A 10-player night can run on one person’s voice. A 40-player night can’t.
What should a raid leader do before, during and after the raid?
Pick a tab. Each one is the part of the job that happens at that point in the night, in the order you do it.
Before
Settle the roster the evening before. Close signups, build the comp, and post who is in and who is on the bench. People plan their evening around that post. Fill the tank and healer seats first, because they decide whether the raid can happen.
Read up on every boss you plan to pull. For new raids, read the guides as they appear. Wowhead keeps Forever’s raid pages together in its raids hub. Write a one-line plan per boss: who tanks what, where the raid stands, the one thing that kills people.
Post the pre-raid message. Time, consumables, the plan and who is benched. A template is below.
Send invites 15 minutes before the pull. Have an assist do it so you can answer questions.
During
One voice for calls. Only the raid leader calls during a pull, unless a role lead has a job (a tank swap, a healer cooldown). Everyone else keeps voice clear.
Short calls, said early. “Spread now” beats a paragraph. Use the same words every pull so they become habit.
Recover from a wipe in under 2 minutes. Run back, rebuff, then say one cause and one change: “We wiped to adds. Hunters on adds next pull.” Pull again. Don’t review every mistake in voice.
Set a stop rule before the night starts. For example: 5 wipes with no progress on a boss and we move on or call it. It takes the emotion out of the decision.
Watch the clock. If the raid ends at 23:00, the last pull starts by 22:45.
After
Thank people and say what’s next. One line in voice: what went well, when the next raid is.
Hold a 10-minute debrief with the officers. What blocked progress, who needs help, whether the comp needs to change. Keep criticism of individuals private, and make it specific.
Check who actually came. Compare the sheet with who was there. No-shows and bench credit are easier to settle the same night than a week later.
Post a short recap. Kills, loot and the plan for next week.
Do raid leaders need addons in WoW Forever?
A boss mod helps, but don’t plan around addons that read combat. Forever runs on the modern engine. Addons can’t read the combat log during play, and health, power, auras and threat are hidden from them in combat. Our WoW Forever addons guide covers it in full.
That changes a few habits from Classic:
- No threat meter. Give the tanks a few seconds of head start before DPS opens up, and say so in the pre-raid post.
- No live damage meter as an addon. Judge a pull by whether mechanics were done,
not by a number on screen. Damage and healing can be looked at after the raid from
the combat log file, if someone runs
/combatlog. - Boss mods work from the game’s encounter signals. Deadly Boss Mods has said Forever has the same structure as Midnight. What each boss mod supports for the new raids is for its authors to announce.
What should the pre-raid post say?
When to log on, what to bring, the plan, and who is benched. Post it the evening before, in the raid channel, and pin it. Copy this and fill in the brackets.
**[Raid name] · [day] [date]**
Invites [time], first pull [time], we finish by [time] (guild time).
**Bring:** flasks or elixirs, food, [consumables for this raid], repaired gear.
**Voice:** [channel]. Be in voice and in the instance by the first pull.
**Tonight's plan**
1. [Boss one]: [one-line plan]
2. [Boss two]: [one-line plan]
Stop rule: [5] wipes with no progress and we move on.
**Tanks:** [names] · **Healers:** [names]
**Bench:** [names] (thank you, you are credited for tonight)
Can't make it? Say so on the roster post before [time].
How should a raid leader handle wipes?
Calmly, quickly and with one change at a time. A wipe is information. The raid needs to know what happened and what to do differently, and nothing else.
- Let people run back and rebuff. Don’t explain while people are still corpse-running.
- Name one cause. The biggest one, not all of them.
- Name one change. Who does what differently on the next pull.
- Pull. Momentum matters more than a perfect explanation.
If the same thing kills the same person 3 pulls in a row, take it to a whisper, not to voice. If a boss isn’t moving after your stop rule, move on and come back next week with a new plan.
What should a raid leader delegate?
Everything that isn’t the plan and the calls. A raid leader who also invites, hands out loot, counts tanks and answers whispers will make worse calls.
| Job | Hand it to |
|---|---|
| Invites and summons | An assist |
| Tank assignments and swaps | The tank lead |
| Healer assignments and cooldowns | The healer lead |
| Loot distribution | A loot officer, under your guild’s loot rules |
| Chasing no-shows | An officer, before the raid |
| Recruitment for gaps | The recruiter |
In a 10-player raid you may do most of this yourself. By 20 players, hand over invites and loot. By 40, you need a tank lead, a healer lead and someone on loot, and you should mostly be talking to them. Loot rules deserve their own decision: see loot council vs DKP.
What is the raid leader’s checklist?
The same steps every week. Ticks save in this browser, and the button copies the list for your officer channel.
- Signups posted with at least 5 days’ notice
- Signups closed and comp built the evening before
- Roster and bench posted, with confirmations chased
- One-line plan written for every boss
- Pre-raid post pinned in the raid channel
- Assist leaders know their jobs (invites, tanks, healers, loot)
- Stop rule agreed before the first pull
- Officer debrief held after the raid
- Sheet compared with who actually came
- Recap posted with kills, loot and next week’s plan
In GuildPro, the raid plan shows who has confirmed a posted roster and lets you DM everyone who hasn’t with one button. After the raid, attendance credits the bench and lists who said yes and never came. Free for every guild. Download the GuildPro app so the night gets recorded.
For everything your guild should have ready before raids open, see the WoW Forever guild checklist.
FAQ
What does a raid leader do in WoW?
A raid leader owns raid night: the signups and roster, the plan for each boss, the calls during the fight, and the decision to keep going or stop. Good raid leaders hand the rest to assist leaders.
How do I recover after a wipe?
Give the raid a short break, name one cause of the wipe and one change for the next pull, then pull again. Don't review every mistake in voice. Save that for the debrief.
Do raid leaders need addons in WoW Forever?
A boss mod helps everyone hear the same warnings. Forever runs on the modern engine, so addons can't read combat in real time and there is no threat meter. Our Forever addons guide explains what still works.
How many assist leaders does a raid need?
One per 10 players is a fair rule of thumb: a 10-player raid can run with the leader alone, a 20 with one or two assists, and a 40 with a tank lead, a healer lead and someone on invites and loot.