Reports: ACE - Communication - United Task Force (UNITAF) Arma 3

P10-42 Reports: ACE

UNITAF / Arma 3 / Communication Procedures

Version 4 / 8min read / Updated Mon 01 Nov 2021 / 1178 views

ACE Reports

An ACE report is a quick report given to the next-higher element leader regarding your element's status. When giving an ACE report, only include the important parts.


  • If your team is low on ammo, give details on it.
  • This can be in general (“Low on ammo”) or more specific (“AR is low on ammo, but we have plenty of rifle ammo”).



  • Simply reply with how many units are alive (“up”) and how many are wounded.
  • Anything more detailed, such as triage information is part of a CASREP instead.



  • If the team has lost any important equipment, it is noted here.
  • For example, if the automatic rifle has been lost due to a casualty, and the AAR was unable to retrieve it, the team leader states so here.
  • If the anti-tank weapons have been expended, state that as well.
  • Equipment extends to any special equipment you were given for the mission.

As a Squad Leader, ACE reports from your fireteam leaders are compiled to form the SITREP that you give to the platoon commander.



Outlaw: Bravo, this is Outlaw, ACE Report.

Bravo: Outlaw, this is Bravo, WAIT OUT.

(30 to 60 seconds pass while information is gathered)

Bravo: Outlaw, this is Bravo.

Outlaw: Bravo, this is Outlaw.

Bravo: We are orange STANAG, red 9 mm, we have 5 up 1 wounded, we’re red on AT.

Outlaw: ROGER, OUT.

Notice that Bravo doesn't mention in their report anything that isn't relevant. And uses the simple ORANGE for LOW and RED for OUT. Green should never be used, since it wouldn't be relevant information.


Conducting a Fireteam-level ACE check

From a Fireteam Leaders perspective

To form the ACE report to pass up to your superior you must first gather the respective information.

This is best done by conducting the ACE check together with your buddy team and then ask the leader of the other buddy team for an ACE check on their team. Alternatively if you are in very close proximity to everyone of your team, you can also gather around the team and conduct the ACE check together with everyone. I.e. off radio. If this both options aren't possible you have to ask every single member of the fireteam for an ACE check individually.


From a Fireteam members perspective

A grave missconception is that every fireteam member gives an ACE report to the FTL. This is never the case, as the ACE report is used only between elements and not on an individual basis. Here, the fireteam member responds with his needs in the order of A C E and mentions nothing else. To preserve detail information before the FTL compresses it to his ACE report, no colors are used here but instead the raw information!


Example 1:

In this example the fireteam member needs ammunition in the form of 5.56 mm 30 round magazines, his casualty status is that he needs a stitch and he needs equipment in the form of bandages.

Hence, the correct way to tell this is his FTL is:

Correct: Low on 5.56 STANAG, need a stitch, and nearly out of bandages.

It would be incorrect if he included unecesary information like to use colors. This is because it prolongs the chatter and detailed information might get lost due to the generalization into a color:

Wrong: Orange on 5.56 STANAG, orange need a stitch, red on bandages

It would also be incorrect if he included unecesary information like if he is talking about A C or E, as the FTL can think of that himself. Again this just prolongs the chatter for no reason:

Wrong: Ammo: low on 5.56 STANAG, Casualty: need a stitch, Equipment: low on bandages


Example 2:

In this example the fireteam member needs ammunition in the form of 5.56 mm 30 round magazines, his casualty status is now fine and he needs equipment in the form of bandages.

Hence, the correct way to tell this to his FTL is to not give any information for the C, as there is nothing relevant to report:

Correct: Low on 5.56 STANAG and nearly out of bandages.

It would be incorrect if he included unecesary information like that he doesn't need medical treatment:

Wrong: Low on 5.56 STANAG, good on medical, and nearly out of bandages.


Example 3:

In this example the fireteam member needs no ammunition, his casualty status is fine and he doesn't need any equipment.

In this special case the information can be compressed to something like:

Correct: All good.

However as no detail information can be lost, as there is none, this is the only time you might as well use a color if you so desire:

Correct: All green.

Though it would still be wrong to provide unecesary information like going over each area on its own:

Wrong: Ammo: good, Casualty: good, Equipment: good


Example 4:

This example cover the process of compiling the ACE Report for a whole team.

The SL asks the FTL, Kevin, for an ACE report

SL: 1-1, this is Actual, ACE report.

FTL (Kevin): Actual, 1-1, ROGER, WAIT OUT.

Now the FTL, Kevin, asks the members of his buddy-team, James and Gunther, for an ACE check. As he is with them, this can be done off the radio.

FTL (Kevin): James, Gunther, give me an ACE check.

James: Low on 5.56 STANAG, out of 9 mm need a stitch, and low on bandages.

Gunther: All good.

The FTL, Kevin, himself is low on 5.56 STANAG, needs blood, and is low on bandages as well. Hence, his buddy-teams is low on 5.56 STANAG and low on 9 mm (Note that they are not out, as both the FTL and Gunther can share some with James), a stitch is needed and they are running low on bandages.
However he doesn't know about the other buddy-team yet. Therefore he asks his 2IC, who is leading the other buddy, Chris, team to compile an ACE check of them

FTL (Kevin): Green, give men an ACE check.

Chris: Wait 1.

Now Chris asks his buddy-team-member, Joe, for an ACE check

Chris: Joe, ACE check.

Joe: Low on 5.56 100 round belts, need a stitch, out of bandages.

Chris' himself is running low on 5.56 STANAG as well but is good otherwise. Hence his team in total is running low on 5.56 STANAG and 100 round belts, a stitch is needed, but they are only low on bandages as Chris can spare a few for Joe. Hence he can transmit this to his FTL, Kevin.

Chris: Kevin, we're low on 5.56 STANAG and 100 round belts, need one stitch and are low on bandages.

FTL (Kevin): Roger.

Now the FTL, Kevin, can merge the buddy-teams ACE checks together and form the ACE Report. He knows both buddy-teams are running low on 5.56 STANAG and his team is running low on 9 mm, meaning both are "orange". Further two people require a stitch and he needs blood, whereas the rest didn't indicate any need for treatment. Therefore they are all up but three are wounded. Lastly he knows both teams are running low on bandages, so orange as well.

FTL (Kevin): Actual, this is 1-1.

SL: 1-1, this is Actual.

FTL (Kevin): We're orange 5.56 STANAG, orange 9 mm, we have 5 up, 3 wounded, orange on bandages.


UNITAF Standard Operating procedures (SOP)
are adapted primarly from US Army Training and Doctrine Command (TRADOC). Our written and audio procedures are a combination of the following primary source materials, as well as our own learnings, modifications and adaptations:
- US Army Techniques Publication, Infantry Platoon and Squad (ATP 3-21.8)
- Soldier’s Manual of Common Tasks Warrior Leader Skills Level 2, 3, and 4 (STP 21-24-SMCT)
- The Warrior Ethos and Soldier Combat Skills (FM 3-21.75 / FM 21-75)
- Leadership Development (FM 6-22)
- Dyslexi's Tactics, Techniques, & Procedures for Arma 3 (TTP3)

Some aspects of this website are fictional. United Task Force is an online gaming organisation that simulates real-world military operations using Arma 3, a sandbox PC game and custom software. Any usage herein of logos, representations of nations or military organisations is done for the sole purpose of historical representation and under fair use.

The UTFN software, and is the sole intellectual property of United Task Force (UNITAF) and it's IP rights holders, All rights are reserved. ©2019-2021