Star Citizen organization guide: crew plans and shared proceeds

Owning a ship is not the same as providing a crew. A Star Citizen operation needs to know which ships are available in the current session, who will fly them, and which responsibilities the remaining members can cover.

Keep organization identity recognizable

Use the organization’s Spectrum ID as well as its name in recruitment. RSI distinguishes organizational ranks from management roles: a rank does not itself grant administrative rights. Keep your community permissions equally deliberate.

Ask recruits for their handle, availability, preferred activities, and the responsibilities they want to practice. Do not make ship ownership the only path into the organization. A willing crew member can help an operation even without providing its main vessel.

Plan the crew before the fleet

For an outing, identify available ships and assign pilots, crew positions, escorts, and other responsibilities supported by the current build. Confirm access and preparation on the day. A theoretical fleet list should not become an operational promise.

Name an operation leader and a fallback objective. If the required ship or player is unavailable, the group should know whether to change the mission or postpone.

Brief the session with practical details

Publish server region, version, meeting location, start time, expected duration, and communication plan. Include what participants need to bring and how the group will regroup after a disruption.

Keep live and test-environment plans distinct. Alpha changes can affect missions and available systems. Use current RSI information for mechanics rather than treating a previous operation as permanent documentation.

Agree on proceeds and costs

Before a shared cargo, mining, salvage, or combat outing, decide who receives the mission reward and how proceeds, supplies, and losses will be settled. Check which actions and transfers the current game permits.

Record the actual settlement after the session. Explain any remaining payment and who owns resolving it. This gives crew members a clear answer without mixing a single operation’s money with every other organization project.

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 Star Citizen guides.

Sources

• RSI’s organization guidance. 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.