From Bravo Fleet Infobase
- Task Forces are the primary organizational units of Bravo Fleet. The Fleet is divided into the following Task Forces, based on Areas of Operation and player participation:
- Task Force 9 operates in the Gamma Quadrant;
- Task Force 38 operates in the Delta Quadrant;
- Task Force 72 operates in the Alpha Quadrant;
- Task Force 93 operates in the Beta Quadrant;
- Task Force 64 operates in pre-TNG (2360) eras;
- Task Force 99 operates in alternate timelines and universes, including non-Trek genres.
- Task Force Commanding Officers must, upon conferring with the Bravo Fleet Senior Staff, appoint a Task Force Executive Officer to assist in operating a Task Force;
- Task Force Commanding Officers may divide their Task Force into different Task Groups;
- Task Force Commanding Officers may appoint Task Group Commanding Officers at their discretion.
- A qualified command applicant must have at least four verifiable months of active player experience on a Bravo Fleet simulation, or equivalent experience elsewhere.
- Depending on the Task Force and era, applicants may apply for any class listed on the Bravo Fleet Infobase;
- For a proposal to be considered, the applicant must submit a detailed plan for their game, including a premise, possible missions, and a realistic class. The proposal should reflect the applicant’s ability to manage a game;
- By submitting a sim proposal, all Commanding Officers agree to the following:
- You acknowledge that you are applying for a command in Bravo Fleet for the ship that you have listed. If for whatever reason you resign your command, your Task Force Commanding Officer and/or Bravo Fleet may, at their discretion, without restriction and without notice to you, reuse the name and registry number of the ship you commanded in Bravo Fleet. By submitting this application, you acknowledge that you understand and agree to this;
- You acknowledge that if you resign/are removed from your command for whatever reason, the Task Force Commanding Officer and/or the Bravo Fleet Admiralty may contact your crew about the situation to make sure that they have been given the option of staying in Bravo Fleet;
- You acknowledge that if you resign/are removed from your command for whatever reason, and if the incoming Commanding Officer is a current member of your simulation, Bravo Fleet reserves the right to use your simulation’s plot and story;
- You also acknowledge that if your website is hosted with Bravo Fleet, the fleet reserves the right to use your website if the incoming Commanding Officer is a current member of your simulation.
- Notwithstanding any of the above, a Task Force Commanding Officer may award command of a sim to the XO or another crew member when a CO resigns or is removed. Such a CO will be required to complete any requirements laid out in this section, if they are not already completed, immediately after his/her assuming the role of CO.
Simulation Standards & Status Classifications
- Bravo Fleet has five distinct status classifications for simulations:
- An active simulation is defined as:
- A simulation with a Commanding Officer that regularly communicates with their Task Force Senior Staff (at least once a month, other than monthly reports).
- A simulation whose Commanding Officer submits a report to TFSS on the 5th of each month.
- A simulation maintaining two (2) posts-per-player each month;
- This metric counts joint posts an individual post for each contributing writer.
- A long-form simulation is defined as:
- A simulation that focuses on post content and quality, rather than quantity;
- Long-form simulations must be approved by both the relevant Task Force Commanding Officer and the Bravo Fleet Senior Staff;
- Long-form simulations may lose their status and become inactive at the discretion of the Task Force Commanding Officer.
- A fiction simulation is defined as:
- A provisional simulation is defined as:
- A simulation that has been in the fleet fewer than two (2) months;
- A simulation with fewer than two (2) posts-per-player.
- An inactive simulation is defined as:
- A simulation that fails to maintain two (2) posts-per-player, without approval as a long-form simulation;
- A simulation whose Commanding Officer fails to respond to communications from the Task Force Senior Staff.
- Task Force Commanding Officers may, upon conferring with the Bravo Fleet Senior Staff, remove the Commanding Officer of a simulation if two (2) of the following circumstances are true:
- The Commanding Officer fails to respond to communications from the relevant Task Force Senior Staff;
- The Commanding Officer fails to adequately complete two (2) consecutive monthly reports;
- The Commanding Officer maintains an inactive simulation for two (2) consecutive months;
- The Commanding Officer of an inactive simulation fails to communicate a satisfactory plan for improvement.
- Within 24 hours of removing a Commanding Officer, the Task Force Senior Staff must inform the crew of the simulation. The Task Force Commanding Officer may select a new Commanding Officer from the crew at their discretion. If no replacement is selected within seven (7) days after notifying the crew, the Task Force Commanding Officer must close the simulation.
- Upon a Commanding Officer’s resignation or removal, that player shall not be able to take another command in the fleet for 90 days.
- If a Commanding Officer is removed for extended inactivity or demonstrated misconduct, that player shall not be able to take another command in the fleet for 180 days. Upon applying to return, a full review must be conducted by the Bravo Fleet Executive Officer and relevant Task Force Commanding Officer.
- An active simulation is defined as:
If a simulation within Bravo Fleet wishes to transfer Task Forces, the following procedure must be followed:
- The Commanding Officer must contact the Bravo Fleet Executive Officer outlining the reasons for the request;
- Within 48 hours of receiving a transfer request, the Bravo Fleet Executive Officer must either approve/deny the request or ask for more information;
- If the Bravo Fleet Executive Officer approves the request, they must contact the relevant Task Force Commanding Officers and inform them of the pending transfer;
- If the Bravo Fleet Executive Officer denies the request, they must inform both the Commanding Officer and current Task Force Commanding Officer of the reasons why the request was denied.
- A transfer can only be approved if the incoming Task Force Commanding Officer approves the request.
A simulation requesting a transfer into Bravo Fleet from outside of Bravo Fleet may not be accepted unless it meets the following requirements:
- A simulation wishing to come into Bravo Fleet will be treated as a general transfer as if it were already in the fleet. A CO wishing to bring their game into Bravo Fleet should first contact a TFCO about joining the Fleet.
- The simulation must agree to follow all Bravo Fleet rules and guidelines laid out by the Bravo Fleet Charter and Policies. Circumnavigation of these rules will result in a disqualification in becoming a Bravo Fleet member simm.
- The simulation must be willing to meet with any other requests which the TFCO may present at the time of application, including, but not limited to, reduction in rank for the CO and/or crew to meet the Task Force's story.
- 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. Bravo Fleet’s departments are organized as follows:
- The Bravo Fleet Communications Office provides recruitment, social media, and news services to the fleet;
- The Bravo Fleet Logistics Office maintains and develops technology specifications for the fleet’s simulations;
- The Bravo Fleet Lore Office maintains and develops the fleet’s canon, in conjunction with Task Force Commanding Officers, simulation Commanding Officers, and players;
- The Bravo Fleet Internet Office maintains and develops the fleet’s software, including BFMS, FNS, RSB, and the Infobase;
- The Bravo Fleet Magistrate Office investigates player complaints and mediates conflicts.
- A department may be created or disbanded upon an affirmative vote from the Bravo Fleet Admiralty;
- Department Heads are defined as members of the Bravo Fleet Admiralty who oversee a fleet department;
- Department Heads may, upon conferring with the Bravo Fleet Senior Staff, appoint a Command Adjutant to assist in operating a department;
- Department Heads may, at their discretion, create teams, committees, and non-Command Adjutant level positions to help departmental operations.