Operations Policy

Section 1 - Chain of Command

The Chain of Command (CoC) is the path that members should take to ask questions and resolve issues related to specific issues like awards, promotions, and activities, or to seek mediation for disputes. If a resolution can’t be reached or if a member of the chain of command is unavailable, you may ask the next person in the chain. General questions may be asked in the appropriate areas on Discord, and suspected violations of the Magistrate Code should be reported directly to the Magistrate. Not all of these roles may be present for every member to go through:

• Task Group Commanding Officer or Staff Assistant: New Members
• Task Force Executive Officer or Staff Officer: New Members
• Task Force Commanding Officer
• Bravo Fleet Operations Officer
• Bravo Fleet Executive Officer
• Bravo Fleet Commanding Officer

Section 2 - Units

All active members are assigned to a Unit, which is either a Task Force or a Training Unit. The purpose of these units is to divide the fleet’s membership up to allow for individualized attention for awards, promotions, and competitions. Each unit has its own theme and strives to build a sense of esprit de corps and camaraderie for everyone. This is the level at which most members will have their most regular interactions and is your home within the fleet.

Task Forces are the primary organizational units of Bravo Fleet, which house all active members at the rank of Ensign or higher. They are led by Task Force Commanding Officers (TFCOs). Task Forces are divided into at least two Task Groups. The Fleet currently has four Task Forces:

• Task Force 17;
• Task Force 72;
• Task Force 86; and
• Task Force 93.

Training Units are an additional organizational unit in Bravo Fleet, which house all active members who have not yet reached the rank of Ensign. They are led by staff members in the Operations Office. The Fleet currently has one training unit, which serves as a place for new members to learn the ropes before being placed into one of the task forces:

• Starbase Bravo

Section 2.1 - Unit Staff

• Every task force has a staff with leadership responsibilities within the unit:
  • Task Force Commanding Officers (TFCOs) are the charter-defined leaders of task forces, with primary responsibility for awards, promotions, competitions, and promoting a positive and active community. Task Force Commanding Officers are appointed by the Bravo Fleet Commanding Officer.
  • Task Force Executive Officers (TFXOs) are the deputy leaders of Task Forces, sharing responsibility for awards, promotions, competitions, and promoting a positive and active community. Task Force Executive Officers are nominated by the Task Force Commanding Officers to the Bravo Fleet Operations Officer, who will consult with the Bravo Fleet Commanding Officer and Bravo Fleet Executive Officer to consider the appointment.
  • Task Group Commanding Officers (TGCOs) are staff members at the Staff Assistant level assigned to assist a Task Force Commanding Officer in leading a Task Force by taking specific charge over mentoring and encouraging the members within that unit assigned to one of its sub-units. This is a leader-in-training position suited for members wishing to gain experience mentoring others. Task Group Commanding Officers are appointed by the Task Force Commanding Officers with the approval of the Bravo Fleet Operations Officer.
• The New Member team has responsibility for helping new members integrate into the fleet, especially those members assigned to a training unit. This team is part of the Operations Office.
  • The Staff Officer: New Members has primary responsibility for awards, promotions, competitions, and promoting a positive and active community for the training units.
  • Staff Assistants: New Members help welcome new members to the fleet, especially to help steer them towards activities that interest them and how to advance through the OCS ranks and awards system.

Section 3 - Departments

Departments are the primary support system for Bravo Fleet’s community. A department oversees a service, or range of services, offered to/for the fleet community.

• Each department derives its power from Charter-defined Bravo Fleet Command positions;
• Department Heads may, upon conferring with the BFCO or BFXO, appoint Deputies and Staff Officers to assist in operating a department;
• Department Heads may, at their discretion, create teams with Staff Assistant positions to help departmental operations.

Bravo Fleet’s chartered departments are organized as follows:

• The Bravo Fleet Lore Office maintains and develops the fleet’s canon;
• The Bravo Fleet Office of the Chief of Staff maintains the fleet’s roster, awards, and competitions;
• The Bravo Fleet Operations Office supervises unit leadership and oversees the fleet’s games;
• The Bravo Fleet Communications Office provides recruitment, social media, and news services to the fleet;
• The Bravo Fleet Internet Office maintains the fleet’s online infrastructure;
• The Bravo Fleet Gaming Office supports online video gaming activities for the membership;
• The Bravo Fleet Magistrate Office investigates player complaints and mediates conflicts.

Section 4 - Roleplaying Games

Role-playing games (RPGs) are an activity offered by the fleet where a group of members comes together on a regular basis to tell the story of a single ship or base together as a crew. Generally, each member controls a character or set of characters and they work together to either roleplay through a scenario or to proceed through a set plot, though there are many variations on these themes.

RPGs are standing groups of members run by a Game Manager that write together collaboratively to either roleplay out a story or to construct a narrative together with an agreed upon set of plot points. These groups have more infrastructure than collaborative fiction, which can include an external website and a Discord server. They are meant to be used by groups of six or more people, where writing together on the forums would be unwieldy.

Section 4.1 - General RPG Policies

All RPGs are administered through the Operations Office, which offers games set within the fleet’s shared canon in 2399 (the Expeditionary Group and Forward Support Group), games set before or after 2399 but still in our shared canon (the Historical Group), and games set in other realities or in non-Star Trek universes (the Alternate Reality Group and the Holodeck). Each game is free to decide where it wants to be set and what kinds of stories it wants to tell within the boundaries of its proposal and fleet canon.

1. RPGs are standing groups of members run by a Game Manager that write together collaboratively to either roleplay out a story or to construct a narrative together with an agreed-upon set of plot points. These groups have more infrastructure than collaborative fiction, which can include an external website and a Discord server. They are meant to be used by groups of six or more people, where writing together on the forums (/through the built-in writing functions of the BFMS) would be unwieldy.
   1. Members interested in writing with smaller, more informal groups may do so with their avatar ships. Consult the Lore Policy for more information on avatar ships.
2. There are two kinds of RPGs: custom RPGs and pre-built RPGs, each with its own set of game manager requirements and its own application process.

Section 4.1.1 - RPG Age Restrictions & Ratings

1. Bravo Fleet uses the RPG Rating System to define appropriate content based on three metrics: Language, Sex, and Violence. RPGs should not use the MPAA rating system (G, PG, etc.).
2. Each RPG must list a rating of each metric on a scale of 0-3.
3. Game Managers are allowed to designate their own rating up to Language: 2, Sex: 2, and Violence: 2 (16+ age rating).
   1. Any rating above “2-2-2” (16+ age rating) must be approved by the Bravo Fleet Operations Officer.
   2. Any RPG rating above “2-2-2” must have a content filter to restrict access to explicit content.
   3. Any RPG rating above “2-2-2” must have a member of the Operations Staff present on the writing platform.
4. No RPG may inappropriately depict acts of sex, assault, or violence. Appropriate content is determined by Bravo Fleet Command.
5. RPGs using a three in any category must not allow the explicit content to be the primary theme of their game. For example, explicit sexual content and explicit violent content should only be present when it would be a logical component of the story, rather than as the extent of the story.
6. Game Managers may not admit players who are younger than 16 for any RPG with a two in any category or younger than 18 for any RPG with a three in any category.
7. If a game breaks any of the restrictions outlined in this section, Bravo Fleet Command reserves the right to remove the Game Manager and suspend Fleet hosting.

Section 4.1.2 - Activity Classifications

There are four activity classifications for games in Bravo Fleet, which refer to the administrative classifications in place related to the number of members writing on a game, its activity, and the status of its GM, active, provisional, inactive, and open:

1. An active game:
   1. Has a game manager in good standing as defined in section 4.2.3;
   2. Has been in the fleet for at least one (1) month;
   3. Has at least two members (including the GM); and
   4. Adheres to its activity plan and proposal.
2. A provisional game:
   1. Has a game manager in good standing as defined in section 4.2.3; and
   2. Has been in the fleet less than one (1) month; or
   3. Is a pre-built RPG still within its first mission or its first two (2) months of activity under a new game manager, whichever is later.
3. An inactive game is defined as:
   1. Has a game manager in good standing as defined in section 4.2.3; and
   2. Is on hiatus, but has communicated a plan to the Operations staff to return to active status within an agreed-upon timeframe.
4. An open game is defined as:
   1. A game that is open for applications from members interested in becoming game managers.

Section 4.1.3 - RPG Infrastructure (Websites & Discord servers)

1. The infrastructure (website and Discord server) used by an RPG are property of Bravo Fleet and will be turned over to a new GM (per policies elsewhere in this document) to provide for continuity of the game, should a GM resign or be removed.
2. Unless an RPG existed within Bravo Fleet before April 25th, 2020, its website must be hosted directly on the Bravo Fleet server and is subject to all of the appropriate Bravo Fleet Internet Office policies on web hosting.
3. If an RPG uses a non-BFMS website, a member of Bravo Fleet Operations staff must have administrative access to said website.
4. All RPGs must have a member of Bravo Fleet Operations staff on their Discord server, should they use one. This staff member should have access to all areas the crew has access to.

Section 4.1.4 - RPGs and the Lore Policy

1. RPGs set inside of our canon must operate within the Lore Policy. The majority of things written about in an RPG would be covered by ‘Member Canon’ but significant developments to lore should be proposed to the Bravo Fleet Loremaster.
   1. RPGs set outside of our canon (in a purely alternative reality or outside of Star Trek) are not beholden to the lore policy.
2. Major changes (defined as a change that would alter the RPGs niche within the fleet or possibly impact other RPGs) to an RPG’s proposal must be approved by the Bravo Fleet Operations Officer, and if necessary the Bravo Fleet Loremaster
3. Minor changes to an RPG’s canon (slight modifications to specifications, custom departments, variations of insignia, and other items that would fall under ‘Member Canon’ under the lore policy) do not require approval.

Section 4.1.5 - Changes to Name, Class, or Registry

Changes to vessel/base name, class, or registry must be approved by both the Bravo Fleet Operations Officer and the Bravo Fleet Loremaster. These changes will only be entertained in situations where the change is absolutely necessary to the success of the game.

Section 4.1.6 - Approving, Rejecting, and Removing Players

A player is defined in this section as any member who wishes to participate in an RPG. Players must be members of Bravo Fleet.

1. Game Managers have sole authority to approve or reject any application that any member submits to their RPG, for lore reasons, incomplete submission, or otherwise, regardless of their standing in the fleet.
2. Game managers have sole authority to remove any player from their RPG, for poor conduct, inactivity, writing standards, or otherwise, regardless of their standing in the fleet.
3. Game managers should not apply in-character punishments for out-of-character actions. Specifically, demoting or killing a character for a player’s lack of activity is inappropriate. In that case, it’s better to just remove the player.
4. Game managers should not apply in-character rewards for out-of-character actions. Rather than promote a character for a player’s awesome conduct, consider talking to that member’s Task Force Commanding Officer to recommend a merit award.
   1. While some Game Managers have informal OOC awards (post of the month, player of the month, etc.) it’s preferred that GMs help their players get recognized through the official OCS system instead.
5. If a player applies to an RPG but is not already a member of Bravo Fleet, that player must also join Bravo Fleet as soon as is possible. It is recommended that GMs do not formally approve any players before they have completed this process.

Section 4.2 - Game Managers

Game Managers are the leaders of Role-playing games, with responsibility for maintaining their RPGs’ infrastructure (website and Discord presence), approving or rejecting applications, determining the course of their RPGs’ stories, and driving activity.

Game Managers may appoint as many Deputy/Assistant Game Managers as they would like, with duties assigned as appropriate. It is not necessary for a DGM/AGM to also hold a senior in-character role to be able to serve in this capacity.

Section 4.2.1 - Appointment of Game Managers

Game Managers are appointed by the Bravo Fleet Operations Officer, after the completion of a proposal and/or application process, as described in the sections on custom RPGs and pre-built RPGs.

Section 4.2.2 - Game Manager Responsibilities

While the role of Game Manager is not a staff position, it is a position that has significant responsibilities, given that Game Managers interact frequently with other members. They have a responsibility to be up-to-date on what the fleet is doing and to help newer members integrate, especially if a new member joins their game before joining the fleet itself. Game managers are expected to:

1. Follow the appropriate lore, operations, and internet office policies while managing their RPG;
2. promote the fleet's other activities with the members participating in their RPGs, including competitions, campaigns, fiction writing, and video gaming opportunities. At a minimum, this means ensuring that fleet-wide announcements are forwarded to their groups. Active members tend to be more active in all areas of the fleet when they participate widely, which makes our games and our whole community stronger;
3. ensure that any individuals who join their RPG before formally joining the fleet do so as soon as is practicable;
4. ensure that the members on their RPG keep an accurate record of their characters positions on their game on the BFMS;
5. maintain an active dossier within a task force and report their own activity through the BFMS on a regular basis, as to set a good example for those writing in their RPGs;
6. develop, follow, and update as necessary an activity plan with the Operations Office which explains their goals for posting and recruitment on their RPGs;
7. participate actively in their own RPGs;
8. work towards maintaining an active game, as defined in the activity policy; and
9. remain in regular contact with the Operations Office about the status of their RPGs, at least once per month.

Section 4.2.3 - Game Manager Good Standing

Game managers must remain in good standing to retain their RPG; failure to maintain good standing will first result in an attempt by the Bravo Fleet Operations Staff to help the GM in question return to good standing before the removal process (defined in section 4.2.4) begins.

Good standing for game managers is defined as:

1. Following the policies listed in section 4.2.2;
2. Maintaining their RPG’s activity level as listed in section 4.1.2;
3. Responding in a reasonable amount of time to Operations staff about matters pertaining to their RPGs, which is defined as within seventy-two (72 hours).

Game managers who lose good standing will be informed by the Bravo Fleet Operations Officer via Discord and via email. They will have thirty days to correct whatever issue has caused them to leave good standing, provided that they respond to the notice of their loss of good standing within one week.

Section 4.2.4 - Removal of Game Managers

1. The Bravo Fleet Operations Officer may remove a game manager if they fail to maintain good standing and do not rectify the situation within thirty (30) days of being informed of their loss of good standing.
   1. If a game manager fails to respond within one week of being informed they have lost good standing, they can be removed without an opportunity to return to good standing.
2. The Bravo Fleet Operations Officer with the approval of the Bravo Fleet Executive Officer may remove a game manager if credible complaints from a game’s players regarding the game manager’s conduct, activity, or ability to run the game are received and substantiated, and mediation between the game manager and the other members on the game is unsuccessful.
3. Within 24 hours of removing a Game Manager, the Operations Office must inform the crew of the game. The Bravo Fleet Operations Officer may select a new Game Manager at their discretion. If no replacement is selected within seven (7) days after notifying the crew, the Bravo Fleet Operations Officer must close the game.
4. Notwithstanding the above, the game manager of a pre-built RPG within its provisional period may be removed at the discretion of the Bravo Fleet Operations Officer and Bravo Fleet Executive Officer for not demonstrating progress towards getting their game active or for otherwise violating fleet policies, but as this is meant to be a learning experience, mediation and opportunities to rectify the situation must occur first.

Section 4.2.5 - Game Manager Cooling-Off Period

To help ensure that resignations are thought through carefully and to help ensure that members stick with their RPG plans, there will be a cooling-off period for members who resign or are removed from their RPG during which they can’t propose a new game or be appointed as a GM to an existing one.

1. Game Managers who resign from their RPGs are ineligible to propose a new RPG or become a game manager for 90 days.
2. Game Managers who are removed from their RPGs are ineligible to propose a new RPG or become a game manager for 180 days.

Section 4.3 - Custom RPGs

Custom RPGs are defined as RPGs that members propose formally, with a lore-complaint premise, ideas for several missions, and a plan for recruiting. These RPGs receive hosting from the fleet, but their GMs are responsible for setting up and maintaining the game’s website.

1. Members must reach the rank of Lieutenant Commander to propose a custom RPG.
2. Members must submit a formal proposal through the BFMS.
   1. For canon 2399 RPGs:
      1. Members must select an existing registry item (i.e. a base or ship that is already in the registry) unless the class has no available names, in which case they may propose a new registry item.
         1. Use of a registry item or the creation of a new one is at the discretion of the Bravo Fleet Loremaster.
         2. Starbases and non-Starfleet ships are examples of concepts where it would be appropriate to ask for an item that’s not already in the registry.
   2. For historical and alternate reality RPGs:
      1. Given that the registry primarily reflects our current 2399 fleet, proposals for historical or alternate reality games must contain a custom registry item, subject to the approval of the Bravo Fleet Loremaster.
      2. Historical RPGs may take place in any time period within Star Trek lore and are considered to be part of the shared canon in use for our 2399 games.
      3. Alternate reality RPGs must take place in a recognized alternate reality (the Mirror Universe, the Kelvinverse, the Anti-Time Future, etc.) seen on-screen or in an alternate reality that is substantially different from our canon in a way that would make it impossible to run in the prime universe.
   3. For non-Star Trek RPGs:
      1. Bravo Fleet offers a limited number of RPGs set outside of Star Trek entirely. Before proposing a game of this type, members should consult with the Bravo Fleet Operations Officer.
3. Proposals will be reviewed first by the Bravo Fleet Operations Officer, who is evaluating the potential RPG’s niche within the fleet, how it would overlap with other offerings, the recruitment potential, and the feasibility of the game’s use of web resources.
4. After being evaluated for its operational viability, the proposal will be evaluated second by the Bravo Fleet Loremaster, who will evaluate the proposal for its adherence to the fleet’s established lore and any changes that might need to be addressed, in addition to the suitability of the proposed registry item.
5. Following concurrence between the Operations Officer and the Loremaster, the Operations Officer will communicate the approval or rejection to the member. Approval may also come with required changes to the proposal. A rejection will explain why the proposal didn’t meet the criteria described above.
6. By submitting an RPG proposal, all potential Game Managers agree to the following:
   1. You acknowledge that you are applying to run an RPG in Bravo Fleet. If for whatever reason you resign your RPG, Bravo Fleet may, at their discretion, without restriction and without notice to you, reuse the name and registry number of the ship, base, or other entity in use by your RPG in Bravo Fleet. By submitting this application, you acknowledge that you understand and agree to this;
   2. You acknowledge that if you resign/are removed from your RPG for whatever reason, Bravo Fleet may contact the members writing on your RPG about the situation. RPGs cannot be removed from Bravo Fleet;
   3. You acknowledge that if you resign/are removed from your RPG for whatever reason, Bravo Fleet reserves the right to use your RPG’s plot and story; and that your game’s history will remain a part of fleet canon;
   4. You acknowledge that the fleet reserves the right to reuse your Bravo Fleet-hosted website (including all of its content).
   5. You acknowledge that if you resign/are removed from your RPG for whatever reason, Bravo Fleet may repurpose your game as a pre-built RPG, open for any eligible member to apply for.
   6. You acknowledge that any major changes to the premise of your RPG must be approved by the Bravo Fleet Operations Officer, who may request a new proposal. Changes to name, class, or registry must also be approved by the Bravo Fleet Loremaster.
   7. Notwithstanding any of the above, the Bravo Fleet Operations Officer may award an RPG to the AGM or another crew member when a GM resigns or is removed.

Section 4.4 - Pre-Built RPGs

The fleet offers a number of RPGs that have already been provided with a website, Discord server, and general theme for the game, which is tailor-made to fit into a niche within the fleet and which is designed for a novice game manager to be able to pick up and run. These games are mentored by a member of the Operations Office staff, which provides a hands-on learning experience and helps them get off of the ground more quickly.

1. Members must reach the rank of Lieutenant to apply to run a pre-built RPG.
2. Pre-Built RPGs are listed under Avalon Fleet Yards as “Open.”
3. Members must submit an application describing why they want to run an RPG, their prior experience running RPGs, their understanding of the concept, and what support they think they will need from the Operations Staff.
4. Pre-Built RPG applications are reviewed by the Bravo Fleet Operations Officer, who will then either approve or reject the application.
5. Pre-Built RPGs are considered provisional for the duration of their first mission or for two months, whichever is longer. During this time, they are actively mentored by a member of the Operations staff, who serves as a secondary game manager to help review applications, offer advice, and manage the website.
6. If for whatever reason a game manager resigns or is removed during the provisional period, the RPG will be reset to its original configuration and offered again as an open game, if none of the current crew are eligible to take over as the new GM.
7. Once a pre-built RPG has left the provisional period, it is treated the same way as all other RPGs.
8. By submitting an application to run a pre-built RPG proposal, all potential Game Managers agree to the following:
   1. You acknowledge that you are applying to run an RPG in Bravo Fleet. If for whatever reason you resign your RPG, Bravo Fleet may, at their discretion, without restriction and without notice to you, reuse the name and registry number of the ship, base, or other entity in use by your RPG in Bravo Fleet. By submitting this application, you acknowledge that you understand and agree to this;
   2. You acknowledge that if you resign/are removed from your RPG for whatever reason, Bravo Fleet may contact the members writing on your RPG about the situation. RPGs cannot be removed from Bravo Fleet;
   3. You acknowledge that if you resign/are removed from your RPG for whatever reason, Bravo Fleet reserves the right to use your RPG’s plot and story; and that your game’s history will remain a part of fleet canon;
   4. You acknowledge that the fleet reserves the right to reuse your Bravo Fleet-hosted website (including all of its content).
   5. You acknowledge that if you resign/are removed from your RPG for whatever reason, Bravo Fleet may repurpose your game as a pre-built RPG, open for any eligible member to apply for.
   6. You acknowledge that any major changes to the premise of your RPG must be approved by the Bravo Fleet Operations Officer, who may request a new proposal. Changes to name, class, or registry must also be approved by the Bravo Fleet Loremaster.
   7. Notwithstanding any of the above, the Bravo Fleet Operations Officer may award an RPG to the AGM or another crew member when a GM resigns or is removed.