Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Guide:TF Report Template

From Bravo Fleet
Revision as of 23:56, 31 October 2025 by Greyimage (talk | contribs) (Layout & Style guide)

Purpose

The purpose of the Task Force Report is to give the wider fleet membership a short summary about the activities of the Task Force in the last quarter (approximately). The Bravo Fleet Operations Office will give a schedule via the Discord Lounge, which can move and shift to accomodate campaigns and fleet events.

The Task Force Report is intended to be a positive and engaging news report about highlights and major events. It is not a blow by blow of everything single thing that has happened.

Examples of Reports

Example 1 - TFXX Report # - DD.MM.YYYY

This is a good report because its brilliant.

Example 2 - TFXX Report # - DD.MM.YYYY

This is a good report because it's gorgeous.

Example 3 - TFXX Report # - DD.MM.YYYY

This is a good report because it does loads of stuff.

Things to Remember

  • Remember the style guide for the fleet, particularly;
    • the italisation of ship names,
    • the full title of the fleet is Bravo Fleet (remember the capitals),
    • refer to Task Forces and Task Groups, not TFs & TGs;
    • members should be referred to by their avatar unless they are commonly known by another term e.g Hurk
  • Remember the four eyes mantra, always check with Operations staff before posting the report for a proofing.
  • Task Force Reports are numbered sequentially by author's contribution within a Task Force.
    • For example, Hurkx has returned to TF17, his last report here was #4, his next will be #5.
    • If Hurkx moves over to TF47 where he has never authored a report he will start again at report #1.
  • The report is your opportunity to champion members and special events, take the opportunity to wave your flags!

Basic Layout & Style Guide

Opening

An opening paragraph or two highlighting any recent special activity or events.

Highlight any staffing changes and any special changesor additions to the TF, e.g new assets.

Fiction Summaries

  • Squadron/Division Name (No Italics) [HYPERLINK TO RELEVANT BFMS PAGE]
  • OR Command Name (Italics) [HYPERLINK TO RELEVANT BFMS PAGE]
    • Brief summary of recent fictions, this is a sales pitch not a retelling. It should be enough to wet readers appetites. Don’t give away the big reveal or the secret twist!  
    • Where missions have featured a command outside of the TF, include a hyperlink to that command.
    • Where a division or squadron has only one ship to summarize, include it as a solo command.
    • Formatting is open to your own style but it should be clear at the top of each summary the command being referred to.

Task Force Recognition

Awards
  • RANK AVATAR NAME - Awards [with individual hyperlinks] In ascending order.
    • Whole list by highest award descending.

EXAMPLE

Promotions
  • AVATAR NAME (NO RANK) [with hyperlink to BFMS avatar] - promotions in ascending order.
    • Whole list by highest final rank descending.

EXAMPLE

  • Varyn K’lev – Cadet Freshman Grade, Cadet Sophomore Grade, Cadet Junior Grade, Cadet Senior Grade, Midshipman, Ensign, Lieutenant Junior Grade and Lieutenant
  • Aev Flammia – Ensign
  • Vegeto – Cadet Freshman Grade

Conclusion

A short conclusion reflecting on the next developments, highlighting upcoming events, campaigns. This should be flavoured with the mission brief of the TF.

Posting Instructions