Report Formats

B52

Without an effective means to relay what you’ve found, your mission is absolutely pointless. Effective, quick methods to send traffic are absolutely essential. Remember as a rule:

  1. Keep your transmissions as short as possible; and
  2. Keep your transmitting power as low as possible.

In order to accomplish #1, standard formats are the only way to go. We’ve talked about SALUTE/SALT. That’s standard Army stuff; what follows builds upon this.

Operating Procedure

Messages can be sent by any means possible; normally digital modes are most efficient if at all possible for brevity’s sake. If digital is out, messages can be sent by voice or IMC. Each line of the message format takes a letter as a proword, for example, ALPHA being the first line. The proword is repeated three times.

Once, while teaching this, I was asked by a former Line NCO why we do this. Simply put, is so that no other traffic is mistaken for these reports. They are their own animal aside from duress/immediate action report formats, such as MEDEVAC and Call for Fire.

The procedure would sound something like this:

  • “You, this is Me, Over”
  • “Me, this is You”
  • “(name of the report), Acknowledge”
  • “(name of the report), Roger”
  • “Alpha, Alpha, Alpha…(line 1 traffic), Break, Bravo, Bravo, Bravo…”

And then your message is sent. Simple enough, right? Roger that.

Reports

There are five reports relevant to the Recon mission. The Initial Entry Report, Intelligence Report, Situation Report, Cache Report, and Battle Damage Assessment. Each report gets it’s own codename; this is for brevity’s sake.

Initial Entry Report

This report is sent once a team completes entry into the operating area. Normally this is sent once the hide site is completed. I’ll point out here that during insertion and extraction phases, everyone’s lines of communication is up, 100%. If your commo fails during insertion, the mission is aborted right then and there. It looks like this:

  1. Date/Time Group(DTG)
  2. Team Status (again, use codewords for good to go, or shot to hell and needing rescue)
  3. Current Location(use grid with letter identifier)
  4. Any deviation from the plan that occurred and why
  5. Any additional info

Intelligence Report

Unlike SALUTE or SALT, these are compiled over time and developed into what’s known as a product. With digital modes, it’s possible to send pictures in with this report.

  1. DTG
  2. DTG of Observed Activity
  3. Location of Observed Activity
  4. Observed Activity
  5. Description of Personnel, Equipment, Vehicles, and Weapons
  6. Team Assessment(how is who you’re watching broken down? Who’s the leader, what are their capabilities, etc.)

Situation Report

  1. DTG
  2. Current Location
  3. Medical Status of Team
  4. Equipment Status
  5. Supply Status( batteries, weapons, water, food, in that order)
  6. Team Activity since last Commo Window
  7. Team Activity till next Commo Window
  8. Team Leader remarks

Cache Report

Often equipment is cached in the area of operations to extend the length of time the team can operate and possibly expand mission capabilities. Most importantly, it lightens the load on your back. The report is as follows:

  1. DTG
  2. Type of Cache(surface, buried, or underwater)
  3. Contents
  4. Location
  5. Depth
  6. Any additional info(normally specific markings)

Battle Damage Assessment

BDAs are import for a couple reasons; for starters, it’s an accurate gauge of either friendly forces’ capabilities or your enemy’s. What’s more important though is the observation of the effect on the people in the area. If it disrupts civilian life too much, it could be a possible means to exploit. That’s situation dependent though. The report is as follows:

  1. DTG
  2. Location of Target
  3. Type of Target
  4. Description of Target
    1. Physical Damage
    2. Functional Damage
  5. BDA analysis
    1. Was the attack successful?
    2. Is re-attack necessary?
    3. What are the Human Terrain(civilian) consequences?

Summary

These are the standard, professional report formats used. Mastering these skills now ensures it’s done right when the time is needed. Only one way to do this.

commosold

Get to it.

Advertisements

12 thoughts on “Report Formats

  1. Pingback: Report Formats | The Defensive Training Group

  2. Pingback: Commo Windows | brushbeater

  3. Pingback: Bushbeater: Report Formats | Western Rifle Shooters Association

  4. shocktroop0351

    How would you encode the location line in your reports? Would you use a one-time pad for those or something else? I think they also used to use target reference points, so couldn’t you give your position in reference to those? Thanks again.

    Liked by 1 person

    1. Good Question. OTP is a good way to do it if you were sending a location not already pre-planned. Almost every time these reports are sent however(and I didn’t note because I wanted to stick to the basic format) they’re sent from a pre-planned transmitting position. During your planning phase these are each given a codename. The same would be done with Observation Posts(OPs, AKA Hide Sites) and phase lines passed during the individual movements. In today’s world, electronic encryption solves 99% of these issues; but it’s not allowed in Amateur Radio. Planning, Codewords in the SOI, and constant Rehearsal are the best workarounds.

      Like

      1. shocktroop0351

        Thank you for the timely response. I guess pre-planning is an area that I am fairly weak at. I’ve written some 5-paragraph orders before and I’ve also studied max velocities method, but I still haven’t gotten very good at it as it pertains to a scouting or reconnaissance patrol.

        Liked by 1 person

      2. It’ll come in time. There’s a reason in the Asymmetric Warfare world that the planning phase often lasts longer than the mission itself. The “Planning your Footprint” post is a large factor in it; knowing your capabilities, down to ranges and times of everything, lends itself to precision. The greater the precision and the less variables to be accounted for, the greater chance you give yourself of mission success.

        Like

  5. Pingback: Deployable Communications Concerns – brushbeater

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s