How to Lead a TBC Classic Raid

The best raid leaders win encounters before the first pull. Start by setting expectations in your guild's Discord or chat channel at least a day before raid night. Confirm the instance, expected duration, and any specific bosses you plan to attempt.

Make sure your roster is locked in advance. Knowing whether you have two or three tanks, how many healers you need, and which DPS classes are available lets you plan compositions for specific encounters. TBC raids are less forgiving than retail — running Serpentshrine Cavern without a warlock tank for Leotheras or without enough Nature Resistance tanks for Hydross will cost you hours of wipes.

Prepare your boss notes ahead of time. Tools like RaidForge let you write role-specific strategies (tank, healer, melee, ranged) for every boss and push them to your entire raid in-game with a single command. This eliminates the "alt-tab to Discord" problem and keeps your raiders focused.

TBC Classic raids are built around class synergies and buff groups more than any other expansion. A well-constructed raid should consider:

Once you're inside, pacing is everything. A raid that moves too slowly loses focus; one that moves too fast makes careless mistakes. Here's what good raid leaders do:

Call out mechanics in voice. Don't assume everyone read the strategy. Before each boss, give a 30-second summary: "Hydross — we transition at 4 stacks. Frost tank starts, nature tank taunts on the swap. Kill adds fast after each transition. Healers pre-shield the incoming tank."

Set a pull timer. Use DBM or BigWigs pull timers so everyone can pre-pot and pre-cast. Consistent pull timers build rhythm.

Don't over-explain wipes. After a wipe, identify the one or two things that went wrong. "We were slow on adds after the second transition — DPS needs to swap faster." Then pull again. Long post-wipe lectures kill morale faster than the boss does.

Delegate. Assign a healing officer to manage healer cooldowns. Let your tank officer handle tank swaps. A raid leader who tries to micromanage 25 players will burn out and miss the big picture.

Track attempts. Knowing how many pulls you've spent on a boss helps you decide when to move on. RaidForge's addon tracks kills and wipes automatically in the background, so you can review your session stats without manually counting.

The raid doesn't end when you hearth out. Spend five minutes reviewing what went well and what didn't. Did a specific boss take too many attempts? Was your composition wrong for an encounter? Did someone consistently miss a mechanic?

Export your attempt data from the RaidForge addon and import it into your guild's raid page on the website. Over time, you'll build a history of progression that helps you identify patterns — maybe your guild always struggles on week-one re-clears, or maybe a specific healer comp works better for certain encounters.

Encourage feedback from your raiders. An anonymous feedback form or a dedicated Discord channel for post-raid thoughts gives quieter guild members a voice. The best raid leaders are the ones who listen.