A Guild Leader's Guide to Using Logs

Every guild that progresses seriously ends up reviewing logs. The ones that improve use logs to find the next thing to fix. The ones that implode use logs to find someone to blame. The data is identical; the framing is everything. This guide is about running log review in a way that makes the raid better instead of bitter.

Review wipes, not just kills

The instinct is to open the kill and admire it. The progression value is in the wipes. Take the pull you got furthest on and ask one question: what ended this attempt? The deaths tab answers it directly. A wipe is almost always a small number of specific events — a missed soak, a botched swap, an early death that cascaded. Find the actual cause, fix that one thing, and the next night moves. Reviewing kills feels good; reviewing wipes is where bosses die.

Lead with mechanics, not the damage chart

Opening review with the damage meter trains your raid to pad instead of execute. Start with survival and mechanics: who died and to what, were the assignments executed, did the cooldown plan happen. Only after that look at throughput, and even then look at it as "is anyone systematically low across many pulls" rather than "who lost the meter tonight." A raider who executes a hard assignment perfectly and parses low contributed more than a padder with a big number, and your review should make that obvious to the room.

Understand the parse before you quote it

A guild leader who calls someone out for a low parse without understanding what produced it loses credibility fast — and loses the raider eventually. Before you raise a number, know whether the kill was slow, whether the player had a mechanical assignment that suppresses damage, whether they were the buff provider rather than receiver, and which difficulty and gear bracket the parse is from. The earlier guides in this series exist precisely so a leader can tell a real performance problem from a logging or context artifact: what a good parse is, meter vs. parse, and tank parsing cover the most common false alarms.

Make it about the next pull, not the last one

The single most effective framing change is tense. "You died to that and cost us the pull" puts a person on trial. "Next pull, use your defensive on that cast and we get past it" gives the same information as a solvable action. Logs are evidence; your job is to convert evidence into a clear, forward-looking instruction. Raiders will accept an enormous amount of correction if it is framed as a path forward and almost none of it if it is framed as a verdict.

Audit the boring things first

Before any conversation about anyone's rotation, scan the Buffs tab for the raid: flasks, food, prepots, augments, defensive cooldown usage on the big hits. These cost no skill and are the most common silent drain on a raid's output. Fixing "three people had no food and nobody prepotted" is easier, less personal, and often more impactful than coaching a rotation. See burst windows and consumables for the full checklist.

Celebrate the log too

Logs are not only a fault-finding tool. A clean kill, a defensive used perfectly, a huge improvement on a prog death — calling those out from the same log builds the culture that makes review welcome instead of dreaded. A guild that only opens logs to find problems trains its raiders to fear the log. A guild that opens logs to find both problems and progress trains them to want it. ParseCard's recap cards are one lightweight way to surface the good moments — see how it works.