Raid Strategy Documentation Best Practices

Written strategy documentation ensures everyone in your raid understands the plan before stepping into the instance. Good documentation reduces explanation time between pulls, prevents misunderstandings about mechanic assignments, and provides reference material for absent members who need to catch up before the next raid night.

How We Selected: We evaluated options using gameplay testing, community feedback, and performance benchmarks. Our criteria covered price-to-performance, build quality, input responsiveness. All picks reflect editorial judgment; no brand paid for inclusion.

What to Document for Each Encounter

Document positioning assignments for every role and phase, mechanic responsibilities with specific player names, defensive cooldown rotations with timing, add kill priorities, and any encounter-specific notes about damage patterns or phase transitions. Include diagrams or annotated screenshots where visual reference adds clarity that text descriptions cannot match.

Positioning diagrams are particularly valuable. A top-down diagram showing where each player stands during a spread mechanic communicates more clearly in one image than three paragraphs of text. Tools like MythicTrap for WoW, Toolbox for FFXIV, or simple drawing tools in Discord provide diagram creation capability.

For each phase of a multi-phase encounter, document what changes from the previous phase. Players do not need the entire strategy repeated; they need to know what is new or different. “Phase 2: same as Phase 1 except add spawn from north, Tank2 picks up, and AoE position shifts to southeast” is more useful than rewriting the entire Phase 1 strategy with Phase 2 additions.

Include a “Common Mistakes” section highlighting the errors your group makes most frequently. If your group consistently fails to spread for a specific mechanic, a bold note reading “SPREAD IMMEDIATELY on Meteor cast, DO NOT finish your current cast” directly addresses the observed problem rather than leaving it buried in general strategy description.

Format, Structure, and Accessibility

Keep documents concise and organized by encounter with clear headings. Use bullet points and role-specific sections so each player can quickly find their assignments without reading the entire document. A healer should be able to scan the document and find “Healer Assignments” within seconds.

Create both detailed and summary versions. The detailed version contains full strategy explanation for study before raid night. The summary version fits in MRT notes or a single Discord message and serves as an in-raid quick reference. The summary might read: “P1: Stack south, spread on circles, interrupt Healer add first. P2: Split east/west by group, dodge orbs clockwise, burn boss at 20%.”

Store documents in a shared location every raid member can access: Discord pins in a dedicated strategy channel, a shared Google Doc, or a guild website strategy section. Every raid member should know exactly where to find current strategy documentation without asking. A pinned message in your strategy Discord channel saying “Current tier strategies: [link]” eliminates confusion.

Use consistent formatting across all encounter documents. When every boss document follows the same structure (Overview, Phase 1, Phase 2, etc., Role Assignments, Cooldown Rotation, Common Mistakes), members build familiarity with the format and can find information faster.

Maintaining Living Documents

When strategy adjustments are made during raid, update the documentation promptly. Outdated documentation creates dangerous confusion when returning members reference old strategies that the group has since modified. The worst scenario is half the group following the updated strategy from memory and the other half following the outdated documentation.

Designate a specific person responsible for updating strategy documents after each raid night. This does not need to be the raid leader. An officer or dedicated note-taker who stays ten minutes after raid to update notes prevents documentation drift.

Version your documents or include a “Last Updated” date so members can verify they are reading current information. A simple “Updated 3/15 after adjusting P3 positions” note at the top tells everyone whether the document reflects recent changes.

Archive superseded strategies rather than deleting them. If the group returns to an earlier strategy approach or if a member was absent during the strategy change, having the previous version available provides context for why the change was made.

Documentation as a Learning Tool

Strategy documentation serves double duty as a learning resource for new or trial members. A comprehensive strategy document for each encounter eliminates the “just watch a video” approach that leaves gaps in understanding. Your documentation reflects your group’s specific strategy, which may differ from the approach shown in public video guides.

Recording and linking POV videos from successful kills alongside the written strategy provides multimodal learning that accommodates different learning preferences. Some people learn best from reading, others from watching, and the combination covers both.

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