Planning Defensive Cooldown Rotations for Raids

Coordinated defensive cooldown rotations prevent raid damage from overwhelming healers during predictable high-damage phases. Planning these rotations before the pull ensures every dangerous moment has coverage and no cooldown is wasted on trivial damage.

Mapping the Encounter Damage Timeline

Identify every significant raid-wide damage event in the encounter timeline. Note the timing, damage type (physical, magical, or bleed), and severity of each event. Boss ability timers from addons like Deadly Boss Mods, BigWigs, or FFXIV’s Cactbot provide exact timing data. This map becomes the foundation for your cooldown assignments.

For a WoW encounter like Mythic Smolderon, the damage timeline might read: raid-wide AoE at 0:25, tank buster at 0:40, heavy raid damage at 1:10, intermission AoE at 1:35, repeating raid-wide at 2:00, and escalating damage from 2:30 onward. Each of these events needs appropriate cooldown coverage based on its severity.

FFXIV encounters follow precise, scripted timelines that can be mapped down to the exact server tick. A Savage boss like P12S Athena has raid-wide damage at predictable intervals, allowing healers to plan mitigation down to the individual oGCD. Scholar’s Expedient, Sage’s Kerachole, White Mage’s Temperance, and Astrologian’s Collective Unconscious can be assigned to specific damage events weeks in advance.

Distinguish between events that require major cooldowns and those that healers can handle with normal throughput. Not every damage event needs a raid cooldown. Reserve major defensives for the moments that would kill players without them, and let standard healing handle routine damage.

Assigning Cooldowns to Damage Events

Distribute defensive cooldowns across damage events so each dangerous moment has at least one major cooldown covering it. Avoid stacking multiple cooldowns on the same event while leaving another uncovered. The goal is even distribution that handles every spike without waste.

In WoW, the defensive cooldown toolkit includes healer raid cooldowns like Aura Mastery, Spirit Link Totem, Darkness, and Rallying Cry, plus personal externals like Pain Suppression, Blessing of Sacrifice, and Ironbark. Map each of these to specific damage events based on their cooldown duration, effect type, and positioning requirements.

Spirit Link Totem redistributes health among nearby allies, making it ideal for moments when damage hits some players harder than others. Aura Mastery with Devotion Aura provides raid-wide damage reduction, best used on the highest raw damage events. Anti-Magic Zone provides magic-specific reduction, suited for magical damage spikes. Matching the right cooldown to the right damage type maximizes its effectiveness.

FFXIV defensive planning involves layering mitigation rather than relying on single abilities. A standard mitigation plan for a major raidwide might combine Reprisal from a melee DPS (10% damage reduction), Shield Samba or Troubadour from a physical ranged (10-15% reduction), Addle from a caster (10% reduction to magic damage), and a healer shield or mitigation. Layering multiple smaller reductions prevents any single player’s missed cooldown from causing a wipe.

GW2 raid encounters require coordinated projectile destruction, condition cleanse, and stability application rather than traditional damage reduction cooldowns. A Firebrand’s Tome of Courage provides stability and aegis for mechanics that would knock players off platforms, while a Druid’s spirit totems and healing output handle sustained damage pressure.

Creating and Sharing the Cooldown Sheet

Post the cooldown rotation where everyone can reference it during the encounter. Method Raid Tools (MRT) notes in WoW allow you to type cooldown assignments visible to the entire raid during the encounter. Discord pins preserve the rotation for reference between sessions. In-game macros can announce when cooldowns are being used.

Format the cooldown sheet as a timeline: “0:25 AoE - Rallying Cry (Warrior), 1:10 Big hit - Spirit Link (Shaman) + Devotion Aura (Paladin), 1:35 Intermission - Darkness (DH) + Anti-Magic Zone (DK).” This format is scannable during combat and eliminates ambiguity about who is responsible for each event.

Include backup assignments for when primary cooldown holders are dead. If the Shaman dies before the 1:10 hit, specify that the backup plan is a healer popping their personal major cooldown plus the Priest using Barrier. Having contingency plans prevents the cascade failure where one death leads to a wipe because the subsequent damage event had no coverage.

Adjusting Through Progression

Your initial cooldown plan will need adjustment as you learn the encounter. Some damage events hit harder than expected, requiring additional coverage. Others hit lighter than expected, freeing cooldowns for reassignment to more critical moments.

Track which cooldowns are available for each damage event based on their cooldown timers and when they were last used. A three-minute cooldown used at 0:25 is available again at 3:25. Verify that your assignments respect these timing constraints and that no cooldown is assigned to two events closer together than its recharge time.

As gear improves throughout the tier, damage events that required major cooldowns during early progression may become healable with standard throughput. Reassign freed cooldowns to cover the diminishing margins on later, harder phases where the extra mitigation allows more aggressive play from DPS.

For more, see our healing strategies guide and raid leading guide.