Guide
Preparing a WoW Forever Guild for Launch
An adaptable pre-launch checklist for guild identity, recruitment, schedules, group plans and officer responsibilities.
Use this countdown as a planning sequence, not a confirmed release timetable. If you have fewer than six weeks, combine the steps. Adjust plans when Blizzard publishes new information rather than treating assumptions as commitments.
Six weeks out: agree on the essentials
Write a short statement covering region, faction, intended ruleset, activities, atmosphere and available nights. Record what is decided and what is still open.
Check Blizzard's official Forever information before making game-specific promises. Ask members to confirm that their plans fit the same environment; a shared guild name alone does not resolve conflicting expectations.
Assign responsibility for recruitment, scheduling, policies and member questions. A small guild can combine jobs, but should still know who owns each decision.
Five weeks out: publish an accurate listing
Use the guild directory to review what applicants can see about your group. Include the schedule's timezone, known openings and a working contact route.
Ask application questions that help you decide: availability, intended class and what the player wants from the group. Set a response target your officers can meet and identify who covers absences. Turn roster goals into specific openings: "two healers for Tuesday and Thursday" gets applications that "healers wanted" does not.
Four weeks out: organize optional groups
Invite members to share their likely play windows and preferred pace. Build groups around compatible availability, not only an ideal class combination. Have a way for solo players and late arrivals to find company.
If you plan shared professions or resources, make contributions and access rules clear. Do not assume everyone can commit to the same levelling speed or a fixed first-raid date.
Three weeks out: settle policies
Write down attendance expectations, loot rules, trial arrangements and how rotations will work. Invite questions before members rely on those policies.
Set up communication channels and permissions. Keep applications and personal information visible only to the people who need them. Publish a simple route for members to raise concerns privately, and name one officer for each recurring job so no question waits on one person.
Two weeks out: rehearse communication
Run a planning call or optional group activity to check voice access, sign-ups and announcements. A raid in another available game mode can be useful, but participation should not be confused with a confirmed Forever launch requirement.
Review availability by role. Record missing information and contact the members involved instead of treating an unconfirmed plan as a commitment.
One week out: reconfirm, then simplify
Reconfirm openings, officer availability and the information new members need first. Post a short arrival guide: where to find announcements, how to join groups and who can help.
Have a fallback for delays or changing launch conditions: dates and server details still move during the beta, and WoW Forever News follows each announcement and patch note. Avoid making one officer the only person who can update the plan.
Launch and the first group events
Welcome arrivals, help people find groups and explain any changes. Confirm the actual readiness of members before scheduling mandatory events.
After the first organized activity, ask what was confusing and update the instructions. Keep answering applications and maintaining recruitment needs as the roster changes. The launch plan is a starting point for running the guild, not the end of the work.
Browse guilds recruiting now, or read the other guides.