Guild operations
A LORDNINE guild boss-event preparation checklist that reduces last-minute confusion
Prepare boss events with a small, repeatable briefing that covers roles, timing, attendance, communication, and post-event records.
- By
- ForgeKeep editorial team
- Published
- Reviewed
- Reading time
- 7 min read
Step 01
Publish the purpose before the roster
Members can make better choices about attendance when they understand the event goal. State whether the session is progression, practice, a scheduled rotation, resource collection, or a limited-capacity attempt. The purpose determines which roles, preparations, and rules need emphasis.
Keep the briefing in one discoverable place. Chat reminders are useful, but a durable event record prevents the same questions from being answered differently as the start time approaches.
Step 02
Assign operational ownership, not status labels
A raid lead, attendance reviewer, loot recorder, and communication owner can be different people. Assign the responsibility that must be completed, not merely a rank. That makes handoffs visible when someone is unavailable.
Use the smallest role structure that works. Too many titles make it unclear who acts; too few concentrate every decision in one person during the busiest minutes of the event.
Step 03
Close the event with a factual record
After the event, record the outcome, attendance exceptions, relevant drops, and any decision that affects guild resources. Do this before a new conversation replaces the details in memory.
Separate the factual record from the review conversation. A record says what happened; a later review can decide what to improve without rewriting the event to fit the conclusion.
Continue reading