← Guide Library
RaidingIntermediate

How to Review a Wipe

Reading a failed pull constructively — what killed us, what was avoidable, and what changes next pull.

Written by Blackwake Armada · Published September 18, 2026 · Updated September 18, 2026 · 1 min read

RaidingImprovementWarcraft Logs

A wipe is a lesson the game charges a repair bill for. Reviewing one well takes ninety seconds and is the difference between a raid that progresses and one that repeats.

Ask in order

  • What killed us? Find the first death that started the collapse — usually one mechanic, not a general failure.
  • Was it avoidable? Ground effects, missed interrupts, and standing in soaks are execution problems. Unavoidable raid damage is a planning problem.
  • What changes next pull? 'Do better' is not a change. 'Stack on the star for the third blast' is.

Use the tools

Boss mods and logs both tell the story — the death recap shows what killed each person, and damage-taken breakdowns show who ate avoidable hits. In guild raids this review is collective and blameless: the goal is a different next pull, not a guilty party.

Keep it kind

The fastest way to make people hide mistakes is to punish them for admitting them. 'I got caught by the frontal — my bad' should always be met with 'got it, next pull', never a lecture. Raids that learn together clear together.

Stuck on something here? Post a note on the Academy Learning Board — someone aboard has been exactly where you are.

Still charting this water?

Guides start the conversation — the crew finishes it. Pin a note to the Learning Board and someone aboard will sail it with you.

Ask the Crew