A useful roster records more than names
Use one row for each person’s intended main. Record alts separately in your own notes so you do not count the same person as two available raiders. Select a role only after the player confirms it. The counts above summarise intentions; they do not recommend a raid composition or guarantee attendance.
- Player / character: use a familiar handle before character names are final.
- Intended role: tank, healer, damage or undecided. Leave uncertain choices open.
- Availability: write days, times and a named time zone. Include a finish time where possible.
- Profession plans: record preferences, not unverified crafting capability.
- Last confirmed: the date the player confirmed their choices. This is a manual planning date, not an in-game observation.
Example: make a recruitment gap specific
Suppose Thorn intends to tank on Tuesdays, Elowen can heal on Thursdays and two damage players can attend both nights. You have four interested players, but you do not yet have the same team available on either night. Resolve the schedule overlap before advertising for an arbitrary number of each role.
At each officer check-in, look first for missing availability and old confirmations. Ask those players for an update, then decide what to recruit. Use our guild launch checklist to give those follow-ups an owner.
Save and share your plan
This tool stores changes on your device, supports up to 80 planning rows and downloads a plain-text summary. Blank unnamed rows are omitted from downloads. The print view can be saved as a PDF through your browser. Your roster is not published or automatically imported into RaidMuster.
When you want to explore the shared workspace, see the RaidMuster getting-started guide. For profession coordination, read the guild profession planning guide.