Collect preferences before assigning jobs
Begin by asking players which professions they want to play and how much time they want to put into crafting. A plan works better when its main crafter is interested in the job. Record undecided choices explicitly so officers know where a conversation is still needed.
Use the profession field in the roster template for intentions such as ‘Alchemy preferred; second profession undecided.’ This is useful before a character exists. It is not evidence of a learned profession, skill level or recipe.
Separate coverage from concentration
A guild can plan broadly across different crafting interests while still having several players choose the same profession. Decide what you are trying to achieve: access to a particular capability, easier material gathering or simply helping members find a crafting partner.
Do not force one player into every specialist responsibility. A single interested crafter may have limited availability. Record a backup contact or a way to request help when that person is offline. This is an organisational choice; the best in-game distribution depends on confirmed Forever mechanics.
Keep three kinds of information separate
A useful profession record distinguishes what a player hopes to do from what their character can currently do. Mixing these creates avoidable confusion when someone requests a craft.
- Planned: the profession or speciality a player intends to pursue.
- Observed: a profession or capability captured from the supported game client, with its observation time.
- Confirmed for this request: the crafter has checked the recipe, materials and availability needed for the specific job.
Make crafting requests easy to answer
Agree on a simple request format: what is needed, who it is for, when it is needed and which materials the requester already has. Keep private contact details out of public planning documents. A player handle is usually enough for the guild to find the right person.
For a larger guild task, name the organiser and intended crafters. Ask them to confirm availability before assigning gathering work. Avoid counting the same materials twice if several players are contributing toward one request.
Recheck the plan against the live game
Profession rules, recipes and supporting addon APIs need confirmation for the actual Forever client. A Classic guide or a beta observation can help form a question, but neither should silently become a final release requirement.
RaidMuster’s development preview includes profession and crafting-related workflows. Their usefulness depends on the observations and game data available. Read the sync guide before relying on an automated capability view, and keep unverified fields labelled as unknown.
Review profession plans when players change mains or availability. The goal is a small, current set of useful contacts and responsibilities, not a perfect chart that nobody maintains.