Science Guide: Command Unit Article Development

How to Use This Guide

Command Unit Article Development
What you need to know before creating or developing a Command Unit article

Before You Begin

This guide outlines the minimum quality and formatting standards expected when creating and developing Command Unit articles on the Bravo Fleet Wiki.

Members creating or developing Command Unit articles must follow all requirements identified in this guide.

Read this guide alongside:
Submission & Involvement Guide  ·  Science Office Policy  ·  Intelligence Office Policy  ·  Creative Integrity Policy

Where this guide and a Bravo Fleet policy differ, the relevant Bravo Fleet policy takes precedence.

Know What the Requirements Mean
The following terms are used throughout this guide to make expectations clear.

Required

The item must be followed.

Required Where Applicable

The item must be followed when it applies to the Command Unit, article, or situation being described.

Recommended

The item is strongly encouraged and will usually improve the article.

Optional

The item may be used where helpful, but is not expected for every article.

Need a hand?
Ask the Bravo Fleet Science Officer and their wonderful team if you are unsure whether something is required, recommended, optional, or applicable to the article you are developing.

1. Purpose of This Guide

This guide explains how members should create and develop Command Unit articles on the Bravo Fleet Wiki. For the purposes of this guide, Command Unit articles refer to Divisions, Squadrons, and Flotillas recorded on BFMS.

Command Unit articles provide an in-universe reference for groups of linked ships, stations, or other commands. They should help members understand what the Command Unit is, how it is organised, how its component commands work together, and how it fits into the wider Bravo Fleet setting.

This guide exists to:

• Set clear expectations for members creating and developing Command Unit articles
• Establish consistent standards for article structure and content
• Explain what information must be retained for leadership, command history, and tracking
• Explain how to represent the full BFMS Command Unit, including any sub-command units
• Explain how ship and station articles may link directly to relevant sub-command sections
• Provide a clear basis for Science Office review and support
• Provide practical guidance for developing Command Unit articles over time

This guide supplements, but does not replace, the general Submission & Involvement Guide. Members must also follow the required standards in that guide, including its broader requirements relating to canon, writing style, article perspective, links, images, generative artificial intelligence, and review.

Members are welcome to ask the Bravo Fleet Science Officer and their wonderful team for help at any point when creating or developing Command Unit articles.

2. Creating a Command Unit Article

Required

Start With BFMS

Before creating a Command Unit article, members must ensure that the Command Unit is correctly established on BFMS.

This includes, where applicable:

• The Command Unit itself being recorded on BFMS
• The relevant ships, stations, or other commands being correctly assigned
• The Primary Command being correctly identified
• Any Division, Squadron, Flotilla, or other sub-command structure being correctly represented
• Relevant command and leadership information being current

Members must also check whether a wiki article for the Command Unit already exists before creating a new page.

Required

The Wiki Must Reflect BFMS

The Bravo Fleet Wiki must reflect the Command Unit recorded on BFMS. Members must not use a wiki article to establish, remove, or change a Command Unit assignment or organisational structure that is not reflected in BFMS records.

If a member identifies a difference between BFMS and the wiki that they believe needs correcting, they should contact the Science Office.

Required

One BFMS Command Unit, One Wiki Article

A single article must represent the entire BFMS Command Unit, including any Division, Squadron, or Flotilla designations that form part of the same organisational structure.

Members must not create separate articles for sub-units within the same BFMS Command Unit. Sub-units must instead be represented within the main Command Unit article using headings, subheadings, Composition table groupings, and linkable anchors where appropriate.

Once the BFMS structure is established, the member holding the command may develop the wiki article into a useful in-character reference that supports storytelling, continuity, and future use by other members.

3. Required Minimum Expectations for Command Unit Articles

Required

At minimum, a developed Command Unit article must:

• Clearly identify the Command Unit and its place within Bravo Fleet
• Represent the full BFMS Command Unit in a single article
• Remain consistent with the Command Unit structure and assignments recorded on BFMS
• Include clear current leadership information
• Include the required Command History subsection
• Include a clear Composition section linking to assigned ships, stations, or other commands
• Use clear sub-command headings where the Command Unit contains Divisions, Squadrons, Flotillas, or other internal groupings
• Use anchors where another wiki article needs to link directly to a specific sub-command within the article
• Not duplicate substantial information already covered by individual ship or station articles
• Not make unsupported claims about the Command Unit's wider importance, reputation, status, or significance
• Follow the required standards in the Submission & Involvement Guide and comply with relevant Bravo Fleet policies

Command Unit articles do not need to be long to be useful. A concise article that clearly explains the unit's structure, leadership, composition, and wider context is often more useful than a long article filled with repeated ship details or mission summaries.

4. Suggested Article Template

Recommended

Members may use the following template as a starting point when creating a Command Unit article. This example uses the Squadron infobox template.

Members should adapt the wording and relevant fields for a Division, Squadron, or Flotilla while retaining the required leadership, command history, and Composition sections.

Infobox information and Command Unit composition must remain consistent with current BFMS records.

{{Squadron
| name = 
| seal = 
| unit = 
| taskforce = 
| taskgroup = 
| headquarters = 
| flagship = 
| co = [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
| xo = [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
| quadrant = 
| mission = 
}}

<!-- Insert quote here if you have one, using the quote template. -->

'''(Flotilla/Squadron/Division full name goes here, e.g. Example Exploratory Squadron)''' is a (Division/Squadron/Flotilla) of [[Fourth Fleet]] operating under [[(Task Force, Task Group, or Fourth Fleet Operations goes here)]]. It is commanded by [[bfms_char:(BFMS character number here)|(Character rank and name here)]].

== Mission Profile ==

== Operating Area ==

== Leadership ==

* '''Command Unit Commander:''' [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
* '''Command Unit Deputy Commander:''' [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
** '''(Sub-command name goes here):''' [[bfms_char:(BFMS character number here)|(Character rank and name here)]]

=== Command History ===

* (start year, e.g. 2403) - Present: [[bfms_char:(BFMS character number here)|(Character rank and name here)]]

== Composition ==

{| class="wikitable" style="width:100%"
! colspan="3" |
=== (Command Unit name goes here) ===
|-
| '''[[(Primary command article goes here)|(Primary command display name goes here)]]'''<br />{{class|(ship class)}}
| Command Unit Flagship / Primary Command
| [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
|-
! colspan="3" |
=== <span id="(Sub-command anchor goes here)"></span>(Sub-command name goes here) ===
|-
| '''[[(Ship or station article goes here)|(Ship or station display name goes here)]]'''<br />{{class|(ship class)}}
| (Command role goes here)
| [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
|-
| '''[[(Ship or station article goes here)|(Ship or station display name goes here)]]'''<br />{{class|(ship class)}}
| (Command role goes here)
| [[bfms_char:(BFMS character number here)|(Character rank and name here)]]
|}

== History ==

{{clear}}

Required

Members must remove instructional comments and replace all placeholder text before saving the article.

The Leadership, Command History, and Composition information must remain accurate and consistent with BFMS records.

The Composition section should link to individual command articles rather than repeating substantial information already available on those pages.

Images, seals, patches, and other media used in the article must follow the image, credit, source-link, and generative artificial intelligence requirements in the Submission & Involvement Guide.

5. Headers and Article Structure

Command Unit articles must retain the required sections identified in this guide. Recommended and optional sections may be added where they are relevant and help members understand the Command Unit.

Required

Sections that must be present.

Recommended

Sections strongly encouraged where relevant.

Optional

Sections used where they add value.

5.1 Required Sections

Required

The following sections are required for developed Command Unit articles.

Leadership

Required

A Command Unit article must include clear current leadership information.

The section may be titled Leadership or Staff and Leadership where the Command Unit has enough staff positions to justify the broader title.

The section must identify the current Command Unit commander and should identify a deputy or executive officer where one exists.

Additional positions may be included where they help explain how the Command Unit operates.

These may include:

• Squadron, Division, or Flotilla commanders
• Specialist group leaders
• Starfighter unit commanders
• Starfleet Corps of Engineers leads
• Medical, scientific, diplomatic, intelligence, or logistical support leads
• Headquarters staff or command support staff

Leadership information must remain consistent with current command records.

The section should focus on the organisation and leadership of the Command Unit. It must not become a complete personnel roster or collection of character biographies.

Example

== Staff and Leadership ==

* '''Flotilla Commander:''' Vice Admiral Example Name
* '''Squadron Commander:''' Commodore Example Name
** '''Starfighter Group Commander:''' Commander Example Name
** '''Starfleet Corps of Engineers Unit Commander:''' Commander Example Name
* '''Chief Intelligence Officer:''' Captain Example Name

Command History

Required

The Command History subsection is required and must be retained. It records changes in Command Unit leadership over time and supports historical continuity and command tracking.

Entries must:

• Be listed in chronological order
• Include the commanding officer's rank and name
• Include the year or date range of command
• Include relevant BFMS links where available
• Remain factual and concise

Example

=== Command History ===

* 2401 - 2402: Captain Example Name
* 2402 - 2403: Commodore Example Name
* 2403 - Present: Vice Admiral Example Name

Detailed narrative about individual commanders or command periods should be included in the History section where relevant rather than within Command History.

Composition

Required

The Composition section is required. It must accurately represent the ships, stations, and other commands assigned to the Command Unit on BFMS.

The Composition section should normally include:

• Links to assigned ship or station articles
• Each command's class and type where applicable
• The Command Unit's flagship or Primary Command
• The Command Unit's headquarters where applicable
• The commanding officer of each command where useful
• Relevant operational roles where appropriate
• Any Division, Squadron, Flotilla, or other sub-command grouping recorded within the BFMS Command Unit

Required

Members must not add ships, stations, or other commands to the Composition section as assigned commands unless that assignment is reflected in BFMS records or has otherwise been appropriately authorised.

For larger Command Units, the Composition section should normally use a wiki table so the internal structure, sub-command units, command roles, and individual commands remain easy to understand.

The Composition section must link to individual command pages rather than repeating substantial information from those articles.

Sub-command Headings and Anchors

Required Where Applicable

Sub-command units must have clear headings within the Composition section where they form part of the BFMS Command Unit structure.

These headings allow ship and station articles to link directly to the relevant part of the Command Unit article.

An anchor is an invisible link target within an article. It allows another wiki page to link directly to a particular section or sub-command.

Where another article needs to link directly to a sub-command, members must provide a suitable anchor.

A manual anchor can be created using <span id="..."></span>.

Example

! colspan="3" |
=== <span id="Example Division"></span>Example Long-Range Explorer Division ===

In this example, Example Division is the anchor.

Another article can then link directly to that part of the Command Unit article using:

[[Example Exploratory Squadron#Example Division|Example Division]]

Anchor names should be short, clear, and stable so that links are less likely to break if the displayed sub-command name changes later.

Composition Table Example

A Composition table may use columns for the assigned command, its role, and its commanding officer or other relevant leadership position.

Example

{| class="wikitable" style="width:100%"
! colspan="3" |
=== Example Flotilla ===
|-
| '''[[USS Example|USS ''Example'']]'''<br />{{class|Odyssey}}
| Flotilla Flagship
| [[bfms_char:00000|Captain Example Name]]<br />''Flagship Commanding Officer''
|-
! colspan="3" |
=== <span id="Example Squadron"></span>Example Squadron ===
|-
| '''[[USS Sample|USS ''Sample'']]'''<br />{{class|Sovereign}}
| Deep Space Exploration
| [[bfms_char:00000|Captain Sample Name]]
|-
| '''[[USS Trial|USS ''Trial'']]'''<br />{{class|Inquiry}}
| Tactical Operations
| [[bfms_char:00000|Captain Trial Name]]
|}

Class Links and Hyphen Usage

Required Where Applicable

The {{class|}} template automatically creates the correctly formatted link to a class specification article.

When using the template, enter only the class name after the pipe/vertical bar symbol. Do not include the word "class" after the class name inside the template.

Example

{{class|Odyssey}}

This displays as Odyssey-class.

When writing about a ship or station class in prose, the hyphen should only be used when the class name is used as an adjective before another noun.

Examples

• Correct: USS Enterprise-D is a Galaxy-class starship.
• Correct: The Galaxy class is known for its size and versatility.
• Correct: Starfleet assigned several Galaxy-class starships to deep-space exploration.
• Incorrect: The Galaxy-class is known for its size and versatility.

The class name may also be used on its own where the meaning is clear.

• USS Enterprise-D shares many design features with other ships of the Galaxy class.

5.2 Recommended Sections

Recommended

The following sections are recommended where relevant. They are not required for every Command Unit article, but should normally be included where enough information exists to support them.

Where one of these sections is included, it must meet the standards described below.

Mission Profile

Recommended where enough information exists

Where included, the Mission Profile section should clearly explain the Command Unit's overall purpose and the types of operations it is organised to undertake.

This may include:

• Exploration
• Diplomacy
• Border patrol
• Rapid response
• Humanitarian support
• Scientific operations
• Defence
• Training
• Logistics or infrastructure support
• Specialist operations, such as engineering, medical, or intelligence support

The section should describe the shared purpose of the Command Unit as a whole. It should not repeat the individual mission profile or capabilities of every ship or station assigned to it.

Claims about the Command Unit's role must remain proportionate to its established status and assignments.

Operating Area

Recommended where applicable

Where included, the Operating Area section should explain where the Command Unit usually operates or the geographical context relevant to its activities.

This may include:

• A sector or region
• A border area
• A Task Force area of operations
• A patrol route
• A humanitarian or diplomatic support zone
• A broader exploration area

The section should provide enough context for members to understand where the unit typically operates and the kinds of situations it may encounter.

Remember: Describing an operating area does not establish ownership, territorial control, or exclusive responsibility for that area.

Required

Members must contact the Science Office before establishing an operating area or strategic responsibility that could affect territorial boundaries, major governments, significant routes, wider Fleet Canon, or other elements of the shared setting.

History

Recommended where enough information exists

Where included, the History section must provide a concise, in-universe account of significant developments in the Command Unit's documented history.

This may include:

• Formation
• Major assignments
• Changes in composition
• Changes in leadership
• Relocation or reassignment
• Participation in significant Bravo Fleet Canon events
• Major operational milestones

History must be written in broad strokes and should record significant developments and outcomes rather than becoming a mission log or detailed story recap.

Required

Historical material must remain compatible with established Star Trek canon, Bravo Fleet canon, BFMS records, and existing documented continuity.

Members must not use the History section to contradict or overwrite established events, substantially redefine a previous Bravo Fleet command period, or invent significant actions or decisions for another member's characters.

Where the treatment of existing historical material is unclear, members should contact the Science Office before making substantial changes.

History may be written in either of the following formats.

Recap Paragraphs

Under a subheader identifying the relevant period, such as 2403-2404, members may provide a concise summary of significant events, developments, and outcomes from that period.

Chronological Bullet Summary

For each year, and where useful each month, members may provide one or two brief sentences summarising significant events and their outcomes.

Example

• 2403
  • March: The squadron was formed under Task Force 17 to support long-range exploration and diplomatic operations beyond the Federation frontier.
  • June: The squadron's composition changed following the reassignment of two support vessels and the addition of a dedicated medical frigate.

Members should use whichever format presents the Command Unit's history most clearly. The two formats may be combined where this improves readability.

5.3 Optional and Situational Sections

Optional

The following sections may be used where they add useful, relevant, or distinctive information.

• Patch History - A concise explanation of the Command Unit's seal, patch, insignia, or visual identity where this has changed over time or has historical or storytelling significance.
• Gallery - Images of assigned ships, stations, patches, seals, or other visual material that helps illustrate the Command Unit.
• References - References or footnotes linking to relevant stories, fleet events, BFMS records, or other suitable sources where useful.
• Additional Staff Information - Further staff positions where these help explain how a larger or more complex Command Unit operates.

Images, seals, patches, and other media must follow the image, credit, source-link, and generative artificial intelligence requirements in the Submission & Involvement Guide.

Optional sections should make the article more useful, distinctive, or easier to understand. They should not be added simply to make the article longer or repeat information already available elsewhere.

6. Development Philosophy

Command Unit articles are intended to function as in-universe reference material. They should give readers a clear sense of what the Command Unit is, how it is organised, how its assigned commands work together, and how it fits into the wider Bravo Fleet setting.

Recommended

When developing an article, members should aim to:

• Write from an in-character, in-universe perspective
• Add information that supports storytelling and continuity
• Leave room for future development
• Remain compatible with established Star Trek canon, Bravo Fleet canon, BFMS records, and Intelligence Office guidance
• Keep the focus on the Command Unit as a whole
• Keep the article useful to members beyond the commands directly assigned to the unit

Required

Keep the Focus on the Formation

Command Unit articles must not recreate substantial information already available on individual ship or station articles.

The Composition section should link readers to individual command pages for more detailed information.

The main Command Unit article should focus on shared purpose, structure, leadership, composition, history, operating context, and other information relevant to understanding the formation as a whole.

7. Status, Reputation, and Significance

Members may describe their Command Unit as important, respected, effective, or influential within their own stories, Task Force, local area of operations, or other appropriate context where this is supported by established continuity.

Claims about a Command Unit's status, reputation, importance, or influence must remain proportionate to its established role and history.

Required

Keep Status and Significance Proportionate

Members must not give a Command Unit fleet-wide, civilisation-wide, government-wide, or setting-defining status unless that status has been established through Bravo Fleet Canon or approved by the Intelligence Office.

Examples of claims that must not be made without established canon or appropriate approval include:

• Stating that a Command Unit is the flagship unit of the Fourth Fleet
• Stating that a Command Unit is Starfleet's premier, most elite, most important, most successful, or most decorated formation
• Presenting a Command Unit as the sole or primary reason a major war, fleet-wide event, or galactic incident was resolved
• Claiming that a Command Unit controls or has exclusive responsibility for a major strategic region, route, border, or area of space
• Giving a Command Unit a unique status, capability, reputation, or influence that would require other members to recognise or account for it in their own stories

This does not prevent members from giving their Command Units meaningful histories, honours, reputations, traditions, or significance within an appropriate scale.

A Command Unit may reasonably be important to its crews, its Task Force, its usual operating area, or a regional story without becoming a setting-defining formation for the wider Fourth Fleet.

Where a member is unsure whether a proposed claim goes beyond the reasonable significance of the Command Unit, they should contact the Science Office before adding it.

8. Recommended Qualities of a Strong Command Unit Article

A strong Command Unit article should help readers understand what the unit is, how it is organised, what its assigned commands do together, and how it fits into the wider Bravo Fleet setting.

Recommended

A well-developed article will usually:

• Clearly explain the Command Unit's structure and composition
• Explain its overall mission profile where enough information exists
• Identify its usual operating context where relevant
• Link clearly to the ships, stations, and other commands assigned to it
• Use clear sub-command headings where the Command Unit contains internal Divisions, Squadrons, Flotillas, or other groupings
• Use a Composition table where this makes a larger Command Unit easier to understand
• Summarise significant documented history without becoming a mission log
• Focus on the Command Unit as a whole rather than repeating individual command articles
• Use clear and consistent terminology, grammar, formatting, and section structure
• Leave room for future stories, changes, and development
• Remain useful to members who are not directly involved with the Command Unit
• Remain compatible with BFMS records, established canon, and wider Bravo Fleet continuity

Well-developed sections should be informative, focused, and reusable. They should provide enough information for members to understand the Command Unit without attempting to document every detail of its ships, personnel, or missions.

9. Quick Reference

At a glance: This section summarises the main requirements and recommendations in this guide. Members should refer to the relevant section above for full guidance.

9.1 Required

Required

Members must:

• Ensure the Command Unit is correctly established on BFMS before creating or substantially developing its wiki article
• Check whether a Command Unit article already exists before creating a new page
• Represent the full BFMS Command Unit in a single article
• Include any Division, Squadron, or Flotilla designations that form part of the same BFMS Command Unit within that article
• Not create separate articles for sub-units within the same BFMS Command Unit
• Keep the Command Unit article consistent with current BFMS structure and assignments
• Include clear current leadership information
• Retain the required Command History subsection
• Include a clear Composition section linking to assigned ships, stations, or other commands
• Ensure the Composition section reflects current BFMS assignments
• Use clear sub-command headings where the Command Unit contains internal Divisions, Squadrons, Flotillas, or other groupings
• Use anchors where another wiki article needs to link directly to a specific sub-command
• Not duplicate substantial information from individual ship or station articles
• Keep historical material compatible with established canon, BFMS records, and existing documented continuity
• Not make unsupported claims about the Command Unit's wider importance, reputation, status, or significance
• Follow the required standards in the Submission & Involvement Guide and comply with relevant Bravo Fleet policies

9.2 Recommended

Recommended

Members are encouraged to:

• Explain the Command Unit's Mission Profile where enough information exists
• Identify its usual Operating Area where relevant
• Use a wiki table for the Composition section where this makes the Command Unit's structure easier to understand
• Link clearly to assigned ships, stations, or other commands
• Summarise the Command Unit's documented History in broad, in-universe terms
• Keep the focus on the Command Unit as a whole rather than repeating information from individual command articles
• Use short, stable anchor names where anchors are needed
• Retain useful elements of established continuity where they continue to add value
• Update the article when the Command Unit's composition, leadership, or BFMS structure changes
• Look at similar Command Unit articles for examples of structure, formatting, and appropriate level of detail
• Ask the Bravo Fleet Science Officer and their wonderful team for help when needed

9.3 Optional

Optional

Members may include the following where they add useful, relevant, or distinctive information:

• Patch History - A concise explanation of the Command Unit's seal, patch, insignia, or visual identity
• Gallery - Images of assigned ships, stations, patches, seals, or other relevant visual material
• References - References or footnotes linking to relevant stories, fleet events, BFMS records, or other suitable sources
• Additional staff positions where these help explain how a larger or more complex Command Unit operates
• Additional subheadings where these make the article easier to navigate

Optional content should make the article more useful, distinctive, or easier to understand. It should not be added simply to make the article longer.

9.4 Do Not

Required

Members must not:

• Create separate articles for sub-units within the same BFMS Command Unit
• Use the wiki article to establish, remove, or change Command Unit assignments or organisational structures that are not reflected in BFMS
• Add ships, stations, or other commands to the Composition section as assigned commands unless that assignment is reflected in BFMS or otherwise appropriately authorised
• Remove required leadership, Command History, Composition, or BFMS tracking information
• Treat the article as a personal command log or mission list
• Turn the article into a complete crew roster or collection of character biographies
• Repeat substantial information already available on individual ship or station articles
• List every minor operational detail where a concise summary would be clearer
• Use mission, campaign, Fleet Action, or storyline titles as in-universe history headers
• Present speculative or future events as established history
• Use historical material to contradict or overwrite established events, substantially redefine a previous Bravo Fleet command period, or invent significant actions or decisions for another member's characters
• Claim that the Command Unit is the premier, most elite, most important, most successful, or most decorated unit in Starfleet without established canon or appropriate approval
• Claim that the Command Unit controls or has exclusive responsibility for a major strategic region, route, border, or area of space without appropriate approval
• Give the Command Unit an unsupported fleet-wide, civilisation-wide, government-wide, or setting-defining status
• Give the Command Unit a status, capability, reputation, or influence that would require other members to recognise or account for it in their own stories without appropriate approval

10. Review and Ongoing Development

Command Unit articles are living documents. Members are encouraged to update them following significant developments, particularly changes to leadership, composition, BFMS structure, operating context, or other developments that materially affect the Command Unit.

Updates should preserve the article's usefulness as an in-universe reference rather than recording every mission, story, or minor operational development.

Science Office Review

The Science Office may review Command Unit articles in accordance with the Submission & Involvement Guide to ensure they remain useful, accurate, and consistent with this guide and relevant Bravo Fleet policies.

During review, the Science Office will usually consider the following:

Area Reviewed	Requirement Level	What This Means
Command Unit scope	Required	The article represents the full BFMS Command Unit in one place, including any Division, Squadron, or Flotilla designations forming part of the same organisational structure.
BFMS consistency	Required	Leadership, assigned commands, Primary Command, sub-command structure, and other tracked information remain consistent with current BFMS records.
Required structure	Required	Leadership, Command History, Composition, and other required structural elements are present, clear, and easy to follow.
Canon and continuity	Required	The article remains compatible with established Star Trek canon, Bravo Fleet canon, BFMS records, and existing documented continuity.
Article focus	Required	The article functions as an in-universe reference for the Command Unit rather than a personal command log, mission list, complete personnel roster, or collection of individual ship articles.
Composition structure	Required Where Applicable	The Composition section clearly represents assigned commands and sub-command groupings, using headings and anchors where other wiki articles need to link directly to part of the Command Unit.
Scale and significance	Required	Claims about the Command Unit's status, reputation, importance, operating responsibility, or influence remain proportionate to its established role and do not create unsupported setting-wide consequences.
Formatting and presentation	Required Where Applicable	Ship names, section headers, BFMS links, class links, images, patches, seals, categories, and other formatting elements follow the relevant standards in this guide and the Submission & Involvement Guide.
Story usefulness	Recommended	The article provides enough information about the Command Unit's structure, purpose, history, and operating context to support storytelling and future use.

Recommended

Common issues can usually be prevented by:

• Summarising significant documented events in-universe rather than using mission, campaign, Fleet Action, or storyline titles as history headers
• Keeping complete crew rosters and character biographies out of the Command Unit article
• Linking to individual command articles rather than repeating substantial information from them
• Updating the Composition section after Command Unit assignments change through BFMS
• Keeping sub-units within the main Command Unit article rather than creating separate pages
• Using clear sub-command headings and stable anchors where other articles link directly to part of the Command Unit
• Keeping historical material compatible with established continuity
• Avoiding unsupported claims that make the Command Unit unusually elite, famous, symbolic, strategically dominant, or setting-defining
• Contacting the Science Office before developing material that may affect wider canon, territorial boundaries, administrative records, or command tracking
• Asking the Bravo Fleet Science Officer and their wonderful team for guidance where the appropriate treatment of a Command Unit is unclear

Articles requiring further development may be identified in accordance with the Submission & Involvement Guide.

Build the Formation with Confidence
This guide is intended to make expectations clear and help members develop Command Unit articles that are consistent, easy to understand, and useful to the wider Bravo Fleet membership. If something is unclear, ask the Bravo Fleet Science Officer and their wonderful team.