FFXIV guild guide: Free Companies, statics, and job commitments

A Free Company roster and a raid static answer different questions. One shows community membership. The other shows who has committed to a particular encounter, time, and job. Keep both useful without assuming every Free Company member wants the same progression schedule.

Check where friends can play together

Ask recruits for their character, Home World, data center, play times, and goals. Consult the current official travel rules before promising that a cross-world or cross-data-center team can meet exactly as planned.

Give social members an onboarding path that does not require a raid commitment. Give static applicants a clear schedule, expected preparation, and explanation of how absences are handled.

Sign up with a job, not an unlimited promise

FFXIV characters can change classes and jobs. For an event, ask which job the player commits to using and which alternatives are prepared for the same content. Keep experience and equipment relevant to that job.

If someone switches to heal, identify who covers their former assignment. A flexible character is helpful, but one player still fills one seat at a time.

Write the progression agreement

A static description should state encounter, progression point, session length, preparation expectations, and the substitute policy. Distinguish learning, clear, and farming sessions. A new learner should not discover a farming expectation after joining voice.

For loot, check the current encounter’s weekly and eligibility rules in game. Agree on how upgrades, job changes, and substitutes affect the team’s priorities. The agreement should explain an actual decision without suggesting that officers can override the game’s restrictions.

Keep the next session easy to resume

Save the last useful progression point and the next practice goal. Record confirmed absences and who owns finding a substitute. Keep feedback specific to mechanics and preparation.

For example, “practice this transition, confirm these jobs, bring this substitute” gives the next organizer a workable handoff. A long discussion about whether the team is sufficiently serious does not.

Put the plan into practice

Keep your roster, event commitments, and decisions together with Guild Manager’s guild tools. For Discord setup and participation checks, read the command guide and voice attendance guide.

Browse all Final Fantasy XIV guides.

Sources

• Square Enix’s FFXIV game manual. Use the publisher or server operator’s current information for mechanics and access rules.
• Guild Manager features. The planning recommendations above are our editorial advice, not publisher requirements.

Published October 5, 2026. Check the edition, region, and current patch before applying game-specific rules.