For a single session, use WoW Forever looking for group. For a recurring roster and long-term home, use the guild directory. A complete group post helps people decide whether your evening fits theirs before either side spends time arranging it.
Read the practical details first
Check the region, character ruleset, faction, activity, start time, and host's contact. Public group times use Central Europe for EU, New York for NA, and UTC for OCE. Read the displayed UTC offset for the actual date; EU and North American daylight-saving changes can differ. The friends checklist explains the distinction between a character ruleset and an activity.
Read the description before messaging. Ordinary group listings do not reserve a place; contact the organizer to confirm availability. The separately labelled Scheduled events on the same page link to our event manager, with character/spec signup and the host's roster and loot rules. Those controls require Discord sign-in and membership of this community server; browsing a listing is not a signup.
Write a post people can answer
Use a title that identifies the activity and purpose. "Learning group, two roles needed" is more useful than a general invitation to join something exciting. In the description, explain the goal, expected length, roles needed, preparation, voice expectations, and relevant loot rules.
Form field
What belongs there
Region, character ruleset, faction
Confirm all three with the organizer; a PvP activity is not a character-ruleset choice
Activity
The game activity that matches the session
Start time
The actual date and time, checked against the form's time-zone label
Description
Goal, duration, roles, preparation, communication, and rules
Discord contact
A current handle the host agrees to publish
There is no separate duration field, so put your intended finishing time or session length in the description. Do not advertise unavailable content as a confirmed run.
The form above was captured from this website on September 29, 2026. It is an empty form, not a live group or a completed signup.
A useful description structure
Example structure: We are forming a learning group and will explain the route before starting. State the region, faction, exact date/time, roles still needed, expected finish, voice requirements, and agreed loot policy. Ask interested players to contact the named organizer to confirm a place.
This is a writing example, not a live group. Fill it with your actual plan before submitting. The loot checklist helps you avoid ambiguous rules.
Submit a listing or create a signup event
Submit a group with a future date and a complete description. With your explicit public-sharing consent, the listing appears immediately on the website and is queued for the matching faction/activity Discord forum. Moderators review afterward and may hide posts that break the rules. Discord delivery is asynchronous: an available website listing does not prove that its Discord post has already arrived. Follow the confirmation's Discord link and allow the worker to deliver it; contact staff if delivery remains missing instead of submitting duplicates.
The form supports dungeon, raid, PvP premade, battleground, world PvP, RP, questing, social and other activities. A character's PvP ruleset does not turn a dungeon session into a PvP activity. Choose both fields for what they actually describe. Do not advertise unavailable content as a confirmed run.
For character/spec signups, roster selection and supported loot reservations, use the event manager. Sign in with Discord, join the community first if needed, and read the selected game version and host rules. Event publication and website approval are separate from the immediate-publication listing form. Only staff can override the normal posting channel. A website approval is not a guarantee of a raid place or the host's conduct.
For an ordinary group listing that needs correction or cancellation, contact staff in the Discord community with its title, date and exact change. For a managed event you created, use its event controls; changes are recorded in its history. An unrelated ordinary Discord message is not a synchronized website listing.
Read a real planning post carefully
The October 7 directory contains an EU Alliance PvP-ruleset questing plan titled 5ftofNovemberpowerleveling, scheduled for November 5 at 08:30 Central Europe (UTC+1). That is a future plan, not a completed session or a promise of open places. Check the current directory before responding because listings and availability change. Notice that its activity is Questing even though its character ruleset is PvP. Read the described starting location, level checkpoints and organizer contact before asking to join. A useful post lets you answer when, where and which character without inferring those details from the title.
Confirm the plan before the session
Confirm each participant's role and the host's current contact.
Repeat the start time with a time zone and the intended finish.
Make preparation and voice expectations available beforehand.
Share the same written loot agreement with everyone.
Tell the group promptly when a role opens or the plan changes.
Started or expired posts should not be relied on as upcoming availability. Ask the organizer rather than assuming an old listing still needs players.
Find people you want to play with again
After a good session, ask whether people would enjoy another. A recurring group can form gradually without immediately becoming a guild. If your goal becomes a fixed raid roster, revisit the guild-selection guide.
Complete this for one real session, not an entire guild's launch. A place is confirmed only when the organizer agrees; copying this template does not create a signup.
Activity and purpose:
Region / character ruleset / faction:
Date (YYYY-MM-DD):
Start time and named time zone:
UTC start for that date:
Expected finish or duration:
Roles confirmed / roles still needed:
Newcomers and experience expectations:
Preparation and voice requirements:
Written loot rules / reservations:
Public organizer handle:
How to confirm a place:
Cancellation or change contact:
Pick the calendar date before converting any time.
Use a named zone such as Europe/Sofia or America/New_York, not only "server time" or "evening."
Check the UTC equivalent for that date in your calendar. Do not reuse an offset from a different season.
In the website form, follow its displayed time-zone label. Compare the resulting regional time and UTC offset with your original plan.
Ask one other participant to confirm the same instant before recruiting more players.
Example only: a weekly group can remain at 20:00 in its organizer's local zone while its UTC time changes when local clocks change. A fixed 20:00 UTC group makes a different commitment. EU and North American clock changes can fall on different dates; do not silently shift a recurring group's schedule.
For a shared launch plan across several days, use the launch checklist. If you are arranging beta testing, check the beta preparation guide before advertising access or content.