How to organize raid cooldowns efficiently

Why does poorly organized raid cooldowns destroy progression?

Because raids without a cooldown plan always play late. When the damage increases, people press the button in fright, two defenders enter together, the next spike comes without response and the attempt collapses. The problem is not a lack of button. It's a lack of sequence.

Good cooldown in raid is not the prettiest. It's what enters at the right time, in the right quantity and with a defined owner.

---

Cooldown mapping by function

The first step is simple: list what the raid actually has.

Tanks

• large defensive units per phase
• resources for moments of predictable damage
• stabilization buttons

Healers

• throughput cooldowns
• mitigation/security cooldowns
• response to collective damage spikes

DPS / support

• group defensive
• utilities that help cut damage or stabilize mechanics
• personal resources that avoid overloading the healer

The most common mistake is leading a raid without knowing exactly what cooldowns exist and how long they take to return.

---

Distribution by boss phase

After the cooldown inventory, you need to map out the encounter.

Right questions:

1. where does the boss really press?
2. Which phases punish the group the most?
3. where does the tank suffer most?
4. When does raid damage go up?
5. In which window does the error kill the most?

The ideal distribution matches the cooldowns with the design of the encounter. Not with the anxiety of the moment.

---

How to adapt when trying to progress

Cooldown plan is not stone. It needs to change when the attempt shows something important.

Example of adaptation:

• cooldown coming in too early
• useless overlay
• phase 2 always dying dry
• healer with no response in the longest part
• tank holding too many buttons

Good progression revises cooldown as it revises positioning: right after the wipe, clearly.

---

Common overlap or delay errors

1. Two cooldowns for the same small spike

There's a lot of comfort there and a lack later.

2. Save for “the perfect moment”

Many raids die with cooldowns available.

3. No one knows whose button it was

The classic: everyone thought the other would wear it.

4. Don't align tank cooldowns with real damage

Tank suffers in the wrong phase and the raid blames heal.

5. Ignore personal cooldown

Raid cooldown does not exist to cover individual defensive laziness.

---

Simple cooldown plan template

Step 1

List all available cooldowns.

Step 2

Mark the boss's actual spikes.

Step 3

Assign owner to each critical window.

Step 4

Avoid unnecessary overlap.

Step 5

Review after each significant wipe.

This simple model already solves many raids that live in improvisation.

---

Cooldown plan checklist

Before pulling, confirm:

1. Does each dangerous phase have a cooldown assigned?
2. Does each player know when to use it?
3. do tank and healer know where they are most exposed?
4. Is there a plan B if something goes wrong?
5. Does the group know when to save and when to spend?

When these answers are clear, the attempt becomes much more stable.

---

Minimum recommendation

To organize raid cooldowns better:

1. map cooldowns by role
2. distribute by boss phase
3. Assign Owner, Not Vague Intent
4. review the plan after the wipes
5. stop using cooldown on scare

Stable raiding almost always has less improvised “heroism” and more order.