Start with a promise your guild can keep
Before asking people to commit, describe the guild in a few sentences. Say what a typical week should feel like, whether new players are welcome and how much attendance you expect. ‘Two evenings a week, with a clear finish time and patient progression’ gives a prospective member something concrete to evaluate.
Avoid locking your guild into encounter-specific requirements before the relevant Forever content is confirmed. Social expectations, communication and officer responsibilities can be decided now; game-specific rules can follow reliable evidence.
Confirm availability before counting your roster
An enthusiastic response in chat is not an attendance commitment. Ask each player for an intended role, the nights they can usually attend, a start and finish time, and a time zone. Record when they last confirmed those choices.
For example, eight interested players may split into two groups of four with no common raid night. That is a scheduling problem before it is a recruitment problem. Find the overlap, check it with the group, then recruit for gaps in that actual schedule.
- Keep undecided roles visible rather than guessing.
- Count a person once when planning attendance, even if they have several characters.
- Write the time zone with the schedule; a bare ‘8 pm’ is ambiguous.
- Agree how members report absences and who updates the plan.
Give each recurring job a named owner
Split preparation into a few jobs: recruitment, roster updates, profession coordination and launch communications. One person can cover more than one job, but everyone should know who is responsible for the next action.
Replace a vague task such as ‘sort out professions’ with ‘collect each player’s first and second profession preferences by the next officer check-in.’ The useful output is a recorded decision or question, not another long discussion.
Prepare a first-week plan that tolerates change
Choose a single place for the final realm and faction announcement once those decisions can be confirmed. Pair players with similar levelling schedules if they want company, and give late starters an easy way to reconnect with the group.
Publish a short joining note: where to find the guild, who can invite, where the current plan lives and how to ask for help. Keep important decisions separate from general chat so a member returning after several days can catch up quickly.
Review intentions against reality after launch
The first roster is a plan. After launch, replace intentions with confirmed characters and actual availability. Some people will choose another role or level at a different pace. Update the plan without treating an early preference as a promise someone cannot revise.
When using a character tracker, inspect the capture time before drawing a conclusion. Old or missing information should generate a follow-up question. Only treat a requirement as complete when you have suitable evidence for the current content.
Use the free launch checklist to track decisions and the roster template to record the people behind them. Both work without an account and can be downloaded as text for your officers.