Professional Documents
Culture Documents
October 2004
The Battle Command Training Center will update this publication IAW
ARNG transformation requirements.
REPORTS ------------------------------------------------------------------- 98
Operations Reports--------------------------------------------------------100
Operations Report (OPREP) -------------------------------------------------- 100
Format ------------------------------------------------------------------------------------------100
SALT / SPOT Report (SPOTREP) -------------------------------------------- 101
Purpose-----------------------------------------------------------------------------------------101
Instructions ------------------------------------------------------------------------------------101
Format ------------------------------------------------------------------------------------------101
FBCB2 Report --------------------------------------------------------------------------------101
Serious Incident Report (SIR) ------------------------------------------------ 103
Contact Report -------------------------------------------------------------------- 105
Format ------------------------------------------------------------------------------------------105
Situation Report (SITREP) ----------------------------------------------------- 106
Purpose-----------------------------------------------------------------------------------------106
Instructions ------------------------------------------------------------------------------------106
Format ------------------------------------------------------------------------------------------106
FBCB2 Report --------------------------------------------------------------------------------106
Combat Slant Report ------------------------------------------------------------ 108
Short Slant Report ---------------------------------------------------------------------------108
Long Slant Report----------------------------------------------------------------------------108
Closure Report -------------------------------------------------------------------- 109
Purpose-----------------------------------------------------------------------------------------109
Instructions ------------------------------------------------------------------------------------109
Format ------------------------------------------------------------------------------------------109
Airspace Control Means Request (ACMREQ)--------------------------- 110
Report Number -------------------------------------------------------------------------------110
Instructions ------------------------------------------------------------------------------------110
Format ------------------------------------------------------------------------------------------110
Downed / Missing Aircraft Report------------------------------------------- 111
Purpose-----------------------------------------------------------------------------------------111
Instructions ------------------------------------------------------------------------------------111
Format ------------------------------------------------------------------------------------------111
Instructions ------------------------------------------------------------------------------------118
Format ------------------------------------------------------------------------------------------118
NBC 6 Report (Detailed Contamination Report)------------------------ 119
CHEMWARN Report ------------------------------------------------------------- 120
Effective Downwind Message Report-------------------------------------- 121
NBC Situation Report (NBC SITREP) -------------------------------------- 122
Engineer Reports-----------------------------------------------------------123
Scatterable Minefield Warning Report (SCATMINWARN) ---------- 123
Purpose-----------------------------------------------------------------------------------------123
Format ------------------------------------------------------------------------------------------123
Scatterable Minefield Report and Record (SCATMINREP) --------- 124
Format ------------------------------------------------------------------------------------------124
Obstacle Turnover / Transfer Report -------------------------------------- 125
Report for Bridge, Overpass, Culvert, Underpass, or Tunnel
(BRIDGEREP) ---------------------------------------------------------------------- 126
Purpose-----------------------------------------------------------------------------------------126
Instructions ------------------------------------------------------------------------------------126
Format ------------------------------------------------------------------------------------------126
FBCB2 Report --------------------------------------------------------------------------------126
Report for Ford, Ferry, or Other Crossing Site (CROSSREP) ----- 128
Purpose-----------------------------------------------------------------------------------------128
Instructions ------------------------------------------------------------------------------------128
Format ------------------------------------------------------------------------------------------128
Obstacle Report------------------------------------------------------------------- 129
Purpose-----------------------------------------------------------------------------------------129
Instructions ------------------------------------------------------------------------------------129
Format ------------------------------------------------------------------------------------------129
FBCB2 Report --------------------------------------------------------------------------------129
Obstacle Request, Intent or Status Report ------------------------------ 131
Purpose-----------------------------------------------------------------------------------------131
Instructions ------------------------------------------------------------------------------------131
Format ------------------------------------------------------------------------------------------131
Format ------------------------------------------------------------------------------------------132
Route Reconnaissance Report (ROUTEREP) --------------------------- 133
Purpose-----------------------------------------------------------------------------------------133
Instructions ------------------------------------------------------------------------------------133
Format ------------------------------------------------------------------------------------------133
Closure Report -------------------------------------------------------------------- 134
Purpose-----------------------------------------------------------------------------------------134
Instructions ------------------------------------------------------------------------------------134
Format ------------------------------------------------------------------------------------------134
Bypass Report --------------------------------------------------------------------- 135
Purpose-----------------------------------------------------------------------------------------135
Instructions ------------------------------------------------------------------------------------135
Format ------------------------------------------------------------------------------------------135
Unexploded Ordnance (UXO) Report -------------------------------------- 137
Purpose-----------------------------------------------------------------------------------------137
Instructions ------------------------------------------------------------------------------------137
Format ------------------------------------------------------------------------------------------137
Purpose-----------------------------------------------------------------------------------------153
Instructions ------------------------------------------------------------------------------------153
Analog Format --------------------------------------------------------------------------------153
FBCB2 PERSTAT Report -----------------------------------------------------------------154
Personnel SPOT Report -------------------------------------------------------- 156
Casualty Report ------------------------------------------------------------------- 157
Purpose-----------------------------------------------------------------------------------------157
Instructions ------------------------------------------------------------------------------------157
Format ------------------------------------------------------------------------------------------157
MEDEVAC Request -------------------------------------------------------------- 158
Purpose-----------------------------------------------------------------------------------------158
Instructions ------------------------------------------------------------------------------------158
Format ------------------------------------------------------------------------------------------158
FBCB2 MEDEVAC Message -------------------------------------------------------------160
Medical Situation Report (MEDSITREP) ---------------------------------- 162
Purpose-----------------------------------------------------------------------------------------162
Instructions ------------------------------------------------------------------------------------162
Analog Format --------------------------------------------------------------------------------162
Casualty Feeder Report -------------------------------------------------------- 164
REFERENCES--------------------------------------------------------------171
List of Figures
While FM 5-0 and 101-5 are the principal references used in preparation of
this guide, a regurgitation of these documents is not provided. It is expected
that commanders and staffs will refer to these and other doctrinal references
as added detail and example are required. Numerous unit Tactical Standing
Operating Procedures (TACSOP) were referred to in the build of this guide
and selections provided as applicable.
The guide addresses three principal reference areas, General Staff Planning
Considerations that includes the MDMP, Special Staff Planning
Considerations that includes specific special staff checklists, and Reports
that provides examples of 54 reports a battalion may find the need to use.
Unit staff personnel are encouraged to refer to the guide for examples and
doctrinal direction.
All graphics contained in this guide may be viewed at the BCTC AKO
Collaboration Website.
Following are command and staff duties and responsibilities presented in the
unique context of, “what the staff officer needs to know from the
commander”, and “what the commander needs to know from the staff
officer.” The following lists provide core duties and responsibilities. Each
unit may have many more to add.
Commander
The commander must decide what has to be done and the best method to get
it done, then lead his unit through mission accomplishment. Regarding
planning, the commander:
Sets the standards for training the staff
Drives the deliberate planning process
Performs the key steps in each step of the MDMP process
Directs courses of action (COA)
Is the link between the analytical MDMP and the reality of battlefield
execution
Engineers provide the Commander with the technical skills and equipment
needed to execute the mobility, counter-mobility, and survivability
requirements of the battalion.
The Engineer should have the following information posted in the TOC or
on templates:
Dozer blades available
Mines - Class V
Barrier material - Class IV
Situational obstacle information
Demolitions status
Mine detectors, etc. status
Supply points, etc.
IPB NAI / MSR / route clearance operations
Planned, expected, % complete obstacles
Areas of responsibilities / task organization
Planned, completed survivability %’s (red, green, amber)
The Commander, quite literally, calls the shots. He should make sure that his
intent is known to the FSO during the planning phase of the operation. The
Commander must use all of the people and equipment at his control to insure
that he gets the most from his fire support system. Advanced planning is
important. Once the enemy is stopped, the commander must consider his
next actions. He should be frugal in planning and not create an
unmanageable number of targets.
Communication is the key to success between the fire planner and the
maneuver commander. The process must be continual and the intent of both
parties understood. To assist in this process, the following information
checklists are provided. Some of the questions will require input from the
Commander, others will require special staff input, while many will require a
coordinated staff solution.
The chaplain provides the Commander, the staff, and the soldiers with
religious support and pastoral care.
The CSM is the Commander's eyes and ears. A CSM has no conflicts of
interest. He is dedicated to assisting the Commander in directing the unit
towards the successful accomplishment of the mission.
There are three orders groups that may be called at any time:
0500
0630 OPREP AND SENSITIVE ITEMS BDE UPDATED AS PER RPT BATTLE
REPORT DUE TO BDE CAPTAIN
0700 TF CDR’S CONFERENCE CALL CDR UPDATED ON PAST & NEXT 24 SIGO
HRS. CO. CDRS RECEIVED GUIDANCE,
RAISED CONCERNS, AND REPORTED
SENSITIVE ITEMS. CDR PREPARED FOR
BDE CONFERENCE CALL
0730 TF TARGETING MEETING
(XO, S3, S2, FSO, OTHERS A/R)
1100
1130 CDR’S NARRATIVE (CHARLIE WRITTEN RECORD OF PAST & NEXT 24 BATTLE
RPT) TO BDE HRS ACTIVITIES CAPTAIN
1700
Return fire with aimed fire. Return force with force. You always have the
right, when in danger, to repel hostile acts with necessary force. “Return
fire” means that if you have been fired on or otherwise attacked, you may do
what you must to protect yourself or fellow soldiers.
Anticipate attack. Use force first if, but only if, you see clear indicators of
hostile intent. This means that self-defense is not limited to returning fire.
Soldiers do not have to receive the first shot before using force to protect
themselves and other’s lives. When soldiers initiate the use of force to
defend themselves, they use what is known as “anticipatory” or
“preemptive” force. During non-combat operations, unless ordered
otherwise, you must use anticipatory or preemptive force only when you face
an imminent threat of attack and can identify or describe to yourself certain
clear indicators of hostile intent. Determine whether someone’s intentions
are hostile by considering the same factors you use when reporting enemy
information to your leader under the SALUTE format.
Size. How many individuals are you facing?
Activity. What is he doing? Pointing a weapon?
Location. Is he within small arms range? In a prepared fighting
position? Has he entered a restricted area?
Measure the amount of force that you use, if time and circumstances
permit. Use only the amount of force necessary to protect lives and
accomplish the mission. As a soldier - a professional in the use of force -
you are expected to adjust the intensity, magnitude and duration of your
force to fit the scale of threat that you face. Excessive force endangers
innocent lives and hinders mission accomplishment. If possible, apply a
graduated escalation of force, particularly when facing civilian crowds that
appear to be unarmed, but also unfriendly. In handling potentially hostile
situations, use one or more of the actions in V-E-W-P-R-I-K.
Verbal warning. Tell person(s), in their language, if possible, to
disperse, stay away, or halt.
Exhibit weapon. Show your weapon or use some other display that you
have superior force at your disposal.
Warning shot. Shoot a warning shot, if authorized.
Pepper spray. Spray cayenne pepper spray, if authorized and available
and the individual is close enough.
Riot stick. Strike with riot stick, if authorized and available and if the
individual is close enough. Poke fleshy parts of the body first, arms and
legs next, and, if necessary, escalate to striking the head.
Injure with fire. Shoot to wound.
Kill with fire. Shoot to kill.
Protect with deadly force only human life and property designated by
your commander. Stop short of deadly force when protecting other
property.
Liaison
Bearing. The liaison officer / NCO is the standard bearer for his unit.
Personal appearance, physical fitness, technical / tactical expertise, and
professionalism are key to ensuring that the liaison officer / NCO gives
a lasting first impression.
Briefing Skills. The liaison officer / NCO will often be required to brief
the gaining unit on various topics. He must articulate and possess good
briefing skills.
Aggressiveness. The information flow is critical to liaison officers /
NCO’s success. He must be aggressive in gathering information and
ensure it flows properly to the right people.
Duties. Listed below are the specified duties of the liaison officer / NCO.
They have been broken down into actions taken prior to departure, during
execution of the mission and actions taken upon return. This list is not all-
inclusive but does provide a solid base to facilitate planning once notified
that a liaison officer / NCO will be required.
At a minimum, the TF should provide one LNO team to the BCT Main CP.
Rehearsals
It is important that the commander and staff understand what they want from
a rehearsal. Consider the following.
Reduced Force. Involves only the unit’s and subordinate unit’s key leaders.
Is less time and resource intensive than the full dress rehearsal.
Sketch Map. Can be used almost anywhere day or night. You use the same
procedures as the terrain model technique, except the commander uses a
sketch in place of the model. Sketch must be large enough for all
participants to see as each subordinate commander walks through the verbal
interactive execution of the operation.
Map. Similar to the sketch map rehearsal, except the commander uses a
map and operations overlay of the same scale as being used to plan and
control the fight. (This technique is generally the least effective because of
map scale.)
The following figure depicts the relationships between the six rehearsal
techniques and the amount of preparation/resources required, time used,
OPSEC risk, leadership participation and the amount of detailed
understanding that the participants will likely gain.
Rehearsal Relationships
Rehearsal Responsibilities
TOPIC BRIEFER
ORIENTATION S3
ENEMY SITUATION S2
ISR OPERATIONS S2/S3
MAIN EFFORT CO TM CO COMMANDER
SUPPORTING EFFORT CO TM CO COMMANDER (S)
FIRE SUPPORT FSO
MOBILITY/COUNTERMOBILIT EN CO COMMANDER
Y/SURVIVABILITY
AIR DEFENSE ADA PLT OR SECTION LEADER
MI GSR OR HUMINT TEAM LEADER
NBC CHEMO
COMMAND AND CONTROL S6
Backbriefs
Final backbriefs are conducted after the BN OPORD but before the CO
OPORDs. Each CO Commander backbriefs the BN Commander using a
blow-up sketch (butcher block size) and desk-side binder.
Time allotted is 20 minutes for each CO Commander. Location: BN TOC.
Estimates
Estimate
• Threat COAs
CDR’s
Staff
• Wargame results
• Threat COAs COA
COA Analysis
Analysis • Task organizations
• COA statements & (War
Sketches (War Game)
Game) • Mission to subordinates units
• Refine CCIR
• Wargame results
COA • Decision matrix
• Establish criteria COAComparison
Comparison
• Approved COA
• Refined CDR’s intent
COA
COA Approval
Approval • Specified type of order
• Decision matrix Approve COA • Specified type of rehearsal
• HPT list
• WARNO 3
Preparation
Rehearsals
Execution
Staff integration requires that staff officers plan beyond themselves, know
what to look for to execute their tasks, know where to get it, and know to
start early. The applicability of a particular BOS for a given mission may
take the forefront over another, just as the battalion staff personnel
supporting that BOS at that time may have more critical task responsibilities
than other staff members.
3
•Develop threat event templates (S2 SEC)
Ste p 4 . A n a ly z e C O A s
4 •Develop modified combined obstacle overlay (M COO) (S2 SEC)
•Conduct initial risk assessment
•Coordinate COA analysis (XO)
Note: This graphic is intended •Nominate information requirements (IR) to become CCIR
•Gather the tools
to help BN battle staffs w ith the •Recommend PIR (S2) & approve PIR (CDR)
•List all friendly forces
•M onitor, assess, and manage CCIR (XO)
integration effort required of •List critical assumptions
•Review and approve initial CCIR (CDR)
selected critical tasks. The •List known critical events & decision points
•Revise estimates
actions, duties, and •Determine evaluation criteria
Ste p 3 . D e v e lo p C o u rs e s o f •Revise initial Commander’s intent (CDR)
responsibilities listed, while in •Select war game method & recording method (S3)
A c tio n (C O A ) •Identify intelligence gaps (XO & S2 SEC)
•Record results of war gaming (S3 / OPS NCO)
consonance with the ARTEP 71- •Review & modify CCIR (CDR) •Develop initial R&S plan (S2, S3, & staff)
•Role-play friendly commander (S3 or CDR)
2-M TP, are not intended to be all S te p 4 . A n a ly z e C O A s •Continue risk management (XO & staff) •Turn R& S plan into initial reconnaissance annex (S3 & S3 SEC)
•Role-play enemy commander (S2)
inclusive, but sufficient for BN (c o n tin u e d ) •Analyze relative combat power •Publish R&S order (S3 SEC)
•Develop critical threat decision points (S2)
CDRs and battle staffs to gain a •Analyze COAs (sustainment feasibility, •Generate options •M anage, and enforce planning timeline
•Project & capture enemy actions & losses (S2)
perspective for the spectrum of shortfalls, & movement) (S4) •Array initial forces •Refine, manage, & enforce planning time line (XO)
•Identify IRs, refine event template, & matrix (S2)
integration. Those tasks specific •Analyze COAs (communications support) (S6) •Develop scheme of maneuver •W rite the restated mission (XO or S3)
•Analyze COAs (battle losses & personnel support) (S1)
•Analyze COAs for BOS supportability •Assign headquarters •Conduct mission analysis briefing (S3)
to a member of the BN are •Assess IR to finalize CCIR
•Supervise targeting session (XO) •Prepare COA statements & sketches •Approve restated mission (CDR)
noted. If not noted otherw ise, •Refine the ISR plan based on CCIR
•Participate in targeting session (Targeting Team) •Screen COAs against criteria •Issue CDR’s guidance and intent (CDR)
all other tasks are comm on to •Issue W ARNO 2 to subordinate & supporting units (S3 SEC)
•M odify & approve CCIR (CDR) •Conduct COA development briefing (XO or S3)
the entire BN battle staff. •Receive COA briefing (CDR) •Perform recurring functions
•Revise & update CDR & staff estimates
•Direct, supervise, & coordinate staff planning (XO) •Participate in the COA briefing (staff) •Supervise integration of risk management (XO)
REF: FM 6-0, FM 5-0
•Identify / develop risk reduction measures •Direct, supervise, & coordinate staff planning (XO) •Direct, supervise, and coordinate staff planning (XO)
ARNG POCKET PLANNING GUIDE
Page 32
www-bctc.army.mil
ARNG POCKET PLANNING GUIDE
Formatted mission analysis worksheets S3 OPS NCO Mission Analysis Mission Receipt
Blown-up, laminated mission analysis briefing boards S3 OPS NCO Mission Analysis Mission Receipt
Enlarged, blank timeline with space for light data, enemy & friendly
S3 OPS NCO Mission Analysis Mission Receipt
actions
Examples of previous products used & approved by the CDR Staff NCOs Mission Analysis Mission Receipt
CDR’s guidance checklist S3 OPS NCO Mission Analysis Mission Receipt
Wargaming staff input checklist S3 OPS NCO Wargaming COA Development
Mission Analysis nesting diagram S3 OPS NCO Wargaming COA Development
Synchronization matrix S3 OPS NCO Wargaming COA Development
COA statements and sketch boards with decision graphics Staff NCOs Wargaming COA Development
CDR’s guidance S3 Wargaming COA Development
Battle staff estimates Staff Wargaming COA Development
Operational graphic overlays S3 OPS NCO Wargaming COA Development
List of friendly forces available S3 OPS NCO Wargaming COA Development
Enemy SITEMPs and EVENTEMPs S2 NCO Wargaming COA Development
List of possible enemy reinforcements S2 NCO Wargaming COA Development
List of known higher / friendly & enemy critical events S2, S3 Wargaming COA Development
List of known higher / friendly & enemy decision points S3 & S2 NCOs Wargaming COA Development
Friendly and enemy ICONs S3 & S2 NCOs Wargaming COA Development
Supplies (paper, markers, acetate, etc.) S3 OPS NCO Wargaming COA Development
Imagery (if available or applicable), TERRABASE II products S3 & S2 NCOs Wargaming COA Development
Task organization chart S3 OPS NCO Wargaming COA Development
Reference library (CD or paper) Staff NCOs Throughout MDMP Mission Receipt
The MDMP begins with receiving or anticipating a new mission. This can
come from an order issued by higher headquarters or be derived from an
ongoing operation. When a new mission is identified, commanders and
staffs perform the process actions and produce the outputs shown in the
following graphic. Note the process actions in the diagram.
Process
Includes…
Ops section alerts staff Includes…
Initial timeline
Ops section
Unit alerts staffwho participates
SOP identifies
Alert the staff Initial timeline
Abbreviate the MDMP?
Unit SOP identifies who participates Gather tools Abbreviate the MDMP?
Required coordination
Update estimates Required coordination
Initial surveillance & reconnaissance
Initial surveillance
Authorized movement & reconnaissance
Conduct initial Authorized
Higher HQ order or plan and ops graphics Additionalmovement
staff tasks
Higher assessment
Maps HQ order
of the AO or plan and ops graphics Additional staff planning
Collaborative tasks
Maps
Ownofand
thehigher
AO HQ SOPs Collaborative planning
Own and higher
Appropriate FMsHQ SOPs
Appropriate FMs
Current staff estimates
Current Time from mission receipt to msn execution
Others staff estimates
as required by the mission Tim e from
Time mission
needed by HQreceipt
& subto units
msn execution
to plan & prepare As a minimum…
Others as required by the mission Tim e needed AsType
a minimum…
Current IPBbyproducts
HQ & sub units to plan & prepare
available Type
of operation
of operation
Curre
Staffntestimates
IPB products available
current, need updating General location of operation
Staff estimates General location of operation
Time requiredcurrent, needcritical
to position updating
elements for Ops Initial Ops
Initial Ops
timeline
Begun immediately Tim
Staeffrequired to position
experience, criticalrest,
cohesiveness, elements
stressfor Ops Recon andtimeline
surveillance begin
Begun immediately Staff experience, cohesiveness, rest, stress Recon and
Movements surveillance
to initiate begin
Continuous throughout operations process Movements to initiate
Continuous throughout
How updates operations
affect COA process
development Collaborative planning sessions
How updates affect COA development Collaborative planning sessions
One of the most important outputs of the “Receipt of Mission” process is the
commander’s initial guidance. The commander should focus the staff by
visualizing where he thinks the decisive terrain is and what will be the
decisive operation. He may also discuss shaping operations, but it is not
critical at this point. The commander’s initial guidance should address the
following:
Friendly / Enemy COAs to consider
CCIR
Identification of decisive terrain and decisive operation
ISR guidance
Reconnaissance guidance
Deception guidance (if any)
Fire support guidance and EFSTs
Mobility and counter-mobility / survivability guidance
Air Defense guidance
NBC protective posture
risk
Combat support and service support priorities
CDR’S Intent:
Key Tasks:
End State:
Guidance:
Decisive Points:
INTEL:
ISR M/CM/S CA
Intelligence ADA PSYOP
Maneuver CSS PAO
Aviation C2 JMC
FS MP Deception
CSM Focus
FORCE PROTECTION:
Fratricide prevention Time plan
Weapons control status / THREATCON
Force protection level Type order
NBC posture
Safety Type rehearsal
ACTION WHO
Alert staff of pending planning requirement. S3
Gather tools for mission analysis. STAFF
Provide staff copies of higher headquarters’ base S3
operations order and appropriate annex(es).
Brief commander and staff on mission, instructions, and S3 / XO
developments.
Conduct commander and staff initial assessment. CDR
STAFF
Determine IPB requirements. S2
Determine initial allocation of available time. S3
Refine initial reconnaissance requirements. S2/S3
Complete Reconnaissance and Surveillance Order and S2/S3
Intelligence Summary.
Develop initial planning and operational timelines. S3
Conduct Mission Analysis briefing to the commander. STAFF
Prepare and issue Warning Order #2 per planning S3
timeline with Reconnaissance and Surveillance order and
Intelligence Summary.
Receive and log subordinate and supporting units’ S3
acknowledgment of Warning Order #2.
Receive commander’s initial guidance consisting of… STAFF
♦ Initial time allocation.
♦ LNOs to dispatch.
♦ Authorized movement.
♦ Any additional tasks.
Status of units CCIR, PIR, FFIR The decisive operation Initial IPB products, M COO, SITEM PS
Status of units CCIR, PIR, FFIR The decisive operation Initial IPB products, M COO, SITEM PS
Input-Process-Output Diagram (Mission Analysis)
Risk guidance Specific COAs & priority Pertinent facts & assumptions
Risk guidance Specific COAs & priority Pertinent facts & assumptions
Surveillance & recon instructions Initial CCIR Specified, implied, essential tasks
Surveillance & recon instructions Initial CCIR Specified, implied, essential tasks
Restrictions pled on the command by higher Initial movement instructions Surveillance & reconnaissance Constraints
Restrictions pled on the command by higher Initial movement instructions Surveillance & reconnaissance Constraints
Restrictions to freedom of action Security measures Risk Forces available
Restrictions to freedom of action Security measures Risk Forces available
Deception guidance Military deception Initial risk assessment
Deception guidance Military deception Initial risk assessment
Mobility & countermobility Fires Recommended CCIR
Mobility & countermobility Fires Recommended CCIR
Known data concerning the situation guidance Mobility & countermobility Recommended time lines
Known data concerning the situation guidance Mobility & countermobility Recommended time lines
Supposition on the current situation Specific priorities Security measures Recommended restated mission
Supposition on the current situation Specific priorities Security measures Recommended restated mission
Expected conditions Updated time line Time plan Recommended collaborative planning sessions
Expected conditions Updated time line Time plan Recommended collaborative planning sessions
Collaborative events, rehearsal Type of order
Collaborative events, rehearsal Type of order
guidance Collaborative planning
guidance Collaborative planning
Movements to initiate Can be staff’s recommended msn statement
Identifying, assessing, and controlling risks Movements to initiate Can be staff’s recommended msn statement
Identifying, assessing, and controlling risks Type of rehearsal Can be modified version of staff recommendation
M aking decisions that balance risk costs with mission benefits Type of rehearsal Can be modified version of staff recommendation
M aking decisions that balance risk costs with mission benefits Additional priorities for CS& CSS Can be commander-developed
Additional priorities for CS& CSS Can be commander-developed
Page 37
www-bctc.army.mil
ARNG POCKET PLANNING GUIDE
Mission Analysis requires the entire battle staff to integrate their efforts to
get ready for COA development. The TF XO will ensure total staff
involvement and provide direction from the commander as required. The
task force planning staff should automatically pursue the deliberate MDMP
model unless the commander directs otherwise.
During mission analysis what must be accomplished is see ourselves, see the
terrain, and see the enemy. This helps accomplish the purpose of mission
analysis – which is, to understand our tactical problem.
Identify the assets identification of additions and/or deletions to the task organization
available to the TF identification of supporting assets (e.g., artillery)
to accomplish the the current status of all TF units (e.g., equipment, personnel, etc.).
assigned mission.
Determine from all known / established information such as situation data, enemy
the task information and friendly dispositions, troops available, etc. (facts)
available those
pieces of information assumed -to-be -true information that is judged valid and essential
that may be for planning such as weather, enemy threat capabilities, etc.
considered facts and (assumptions).
those that are best
categorized as
assumptions.
Identify any risks identification of any hazards that may be encountered as a resul t
that must be of enemy presence (tactical risk)
managed to
accomplish the identification of other operational risks not considered tactical
mission. (accidental risks)
Brief the (A sample briefing format is provided at the end of the mission
commander on the analysis section of this guide.)
mission analysis that
has been done.
Periodically review identification of any new facts that may alter unit requirements
the facts and identification of any assumptions that may have become facts
assumptions that assessment of any change.
have been
established.
Seeing Ourselves
One of the most important tasks associated with analyzing the higher HQ
order is identification of specified, implied, and essential tasks. Following
are OPORD examples reflecting the location of these tasks.
3. Execution.
Commander’s Intent Mission
a. Concept of the Operation (See Annex C – Ops
Overlay)
Essential
(1) Scheme of Maneuver. BN defends to block Task
Implied enemy threat to prevent envelopment of the BDE main
effort.
Tasks (2)
b. Tasks to maneuver units.
(1) Security zone (1) BN
in place NLT H-24 (2) BN
(a) Be prepared to counterattack NET H+26 to Specified
(2) Complete refueling protect flank of BDE. Tasks
NLT H+26 (b)
d. Coordinating Instruction.
(1) H-Hr is defined as enemy 1st echelon crossing PL
GIANTS
(2) BN defenses must be complete NLT 080800 ____.
(3) MOPP 2 in effect on 080400 _____.
(4)
Nesting Graphic
II
1 ME
P: Prevent enemy penetration
beyond PL Red
T: O/O Block AA # 2a
Assets available include not only organic assets but also supporting units,
such as artillery, aviation, engineers and intelligence. Additionally, it is
important to understand the command and support relationships that are
specified in the Task Organization paragraph or annex to the OPORD.
1 x arty battery
1 x engineer company
Availability Capabilities /
Unit Type / Equipment (O/H – FMC) Limitations
MANEUVER (Armor / Infantry)
Building a MCOO
VEGETATION
SURFACE DRAINAGE
OTHER OBSTACLES
COMBINED OBSTACLE
OVERLAY
Severely Restricted
II
PL
x
Restricted
II Unrestricted
II
mobility
corridors
II
I
Severely Restricted
X
I
II
II
PL
x
Restricted AA
1B
II Unrestricted
AA AA1
II 1A
AA1 K
EA 2
K
II
+781 I
Severely Restricted
EA 1
X
AA2 I AA2
I
AA
2A
K
II
II
AA
PL
2B
I I
I
ENEMY
Fire Sack TEMPLATE
MCOO
=
I I
I
SITEMP
Fire Sack
FIXING
FORCE AA1
EXPLOITATION
K FORCE
K
+781
ASSAULT
AA2 FORCE
II
PL
x
ATTACK TIMELINE ENTERING AO
H-24
DTG
RECON
H-12
BTG
RECON
H-15
FPs
H-Hour
ASLT &
FIXING FORCE
H+1 to H+3
BTG
EXPL FORCE
H+2 to H+6
DTG
EXPL FORCE
NAI 2 NAI 1
FIXING
FORCE AA1
EXPLOITATION
K FORCE
K
NAI 4
+781
ASSAULT
AA2 FORCE
NAI 3
H + 1130
H + 12
H + 1140
K
II
PL PL
2 Prioritize IR into CCIR, RFIs, Intel Reqs Select CCIR, RFIs, Intel Reqs 3
1
Determine Information Requirements
Developing the ISR collection plan requires the input of the entire staff.
While there are numerous battalion tasks where staffs may have a choice as
to when they are initiated and not worry about the sequence in which they
are accomplished, developing a collection plan is not one of them.
Development is “first things first,” and each development piece builds on
the next. The following checklist is intended to assist staffs with the
building sequence for a battalion collection plan. While the worksheet
checklist is comprehensive and in consonance with doctrine, it is not all-
6
___ Final Plan Ingredients:
___ ISR Assets:
___ Scout PLT?
___ MI assets?
___ GSR?
___ Maneuver companies?
___ FISTs?
___ Colts?
___ Radars?
___ Other?
___ CDR’s ISR Guidance:
___ Priority? 4
___ Focus? ___ Develop a Collection
5
___ Tempo? Strategy:
___ Consider Assets:
___ Engagement criteria? ___ Considerations:
___ Availability?
___ Event or Timeframe to Answer IR? ___ Cueing
___ Capability?
Fort Leavenworth, KS 66027-2346
Collection Plan Development Checklist
___ Redundancy
___ Vulnerability?
___ Mix
___ Performance history?
___ Integration
1
___ Determine Requirements: 3
2 ___ IRs: ___ Select PIRs:
___ Determine IRs: ___ Done during MA ___ From original list of IRs?
© Battle Command Training Center (BCTC)
___ How important? ___ Answers questions about ___ Supports single tactical decision (fires or maneuver)?
___ Where are we in the battle? terrain & enemy ___ Ask only one question.
___ How much collection time do we have? ___ Lists information needed ___ Focused on a specific fact, event, or activity?
___ Type collectors available? to complete the plan ___ Linked to NAI and LTIOV?
___ Lists information needed ___ Addresses post-mission analysis CDR’s guidance?
to execute the fight smoothly ___ List in descending order.
___ Specified tasks ___ Focused, specific?
___ From higher HQ ___ Directly related to friendly decision.
___ Listed during MA to be executed during COA?
___ Specific request for
intelligence / information
___ Received from subordinate
or higher units
___ Specified information
___ Based on MA
___ Confirms / denies SITEMP
ARNG POCKET PLANNING GUIDE
Page 51
www-bctc.army.mil
Appendix 4 (ISR Sketch) to A nnex L (ISR) to 2/52 ID (M ) OPORD02-2
04
COLT 2:
___ Determine CSS.
T1: Observe NAI G2
P1: ID / TGT forces
___ Determine fire support.
ARNG POCKET PLANNING GUIDE
Page 52
www-bctc.army.mil
ARNG POCKET PLANNING GUIDE
Facts: Assumptions:
From: Constraints:
Notes:
DEFEAT DZ E ARLY
EARLY
MAXIMIZE USE OF TRUCK AND AIR MOVEMENT
EARLY EYES ON OBJ, AT AMBUSH VS TK RSV
ENVELOP REAR/INTERIOR
REAR/INTERIOR FLANKS
CONSIDER MOBILE RESERVE
MAKE ENEMY FIGHT TWO DIRECTIONS SAME TIME
• Allocate the minimum combat power necessary for supporting efforts (shaping
operations)
• Weight the main effort (decisive operation) with sufficient combat power to
ensure it is capable of achieving overwhelming mass and effects against the
enemy.
Do This… Remember…
ES
SI
O
N
N
PR
DE
KE
LA
GR
AV
EL
HIL
LS
OPEL
MTNS
II
I
I
PR
ES
S IO
N
I II I N
DE I
KE
LA
I
I
II
I I
I
GR
AV
E LH
ILL
S
OPEL
MTNS
BLACK MTNS
LOA
(PL REAGAN)
II O/O FEBA
O
N I
(PL CARTER)
N
SI I II
ES I
PR
DE I
PL KENNEDY
KE
LA I
OBJ I
I
II FISH
X
X
I
PL REAGAN
X
I PL HOOVER
I
GR
AV
EL BHO
HIL
O/O FEBA LS
(PL GARFIELD)
(PL CARTER)
LD/LC
(PL LINCOLN)
OPEL
PL KENNEDY
MTNS
X
BLACK MTNS
PL HOOVER
LOA
(PL REAGAN)
II O/O FEBA
(PL CARTER)
KE
LA )
I
N
N I II OBJ
CK IO I
BA SS CAT PL KENNEDY
D DE PRE I
E
CU (D I
OBJ I
II
X
FISH
X
I
X
PL REAGAN I
PL HOOVER
I
II
GR
AV
E LH
ILL BHO
O/O FEBA S
(PL GARFIELD)
(PL CARTER)
LD/LC
2-3
(PL LINCOLN)
OPEL
PL KENNEDY
MTNS
X
BLACK MTNS
PL HOOVER
Roll Call
XO
Purpose and Agenda
Brief changes only
1. Weather changes
2. Update most likely enemy COA
3. Threat evaluation Weather changes
S2 4. Threat Evaluation
5. Update Most Likely Enemy COA
6. Update Most Dangerous Enemy
COA
7. R&S Efforts and Results
Division Mission and Intent (Chart)
Brigade Mission & Intent (Chart)
S3
CDR’s Initial Planning Guidance Bullets
(Chart)
COA Statement and Sketch (Chart)
S3 Plans Officer
Describe COA
BOS Brief by Exception
Decision
CDR Intent
Further Planning Guidance
Prepare WARNORD #3 (See Appendix
34, 34A)
S3 Plans Officer If Necessary, Prepare R&S FRAGO
Get Approval of WARNORD #3 and
R&S FRAGO
Issue WARNORD #3 and R&S FRAGO,
Battle Captain if applicable.
Ensure Acknowledgment
XO Conduct Targeting Meeting
COA Analysis allows the staff to synchronize the BOS for each COA and
identify which COA best accomplishes the mission. This step is comprised
of two parts: war-gaming and contingency planning. The war game is a
disciplined process that attempts to visualize the flow of the battle,
synchronize friendly assets/unit actions, and identify contingencies. If the
commander is present for the war game, he will conduct contingency
planning concurrently. If he is not, the S3 will do so immediately following
the war game.
Wargame results to
include:
Staff estimates
Perform Concept of Ops
IPB (enemy COAs)
Inputs Sync matrix Outputs
COA Statement & sketch COA
Ops overlay
Supporting staff Analysis Decision spt template
functional COAs
Task Org
Updated CCIR
Process
The TF Planning Staff will utilize one of two different methods (Hasty and
Deliberate) for conducting war gaming. The XO selects the method based on
time available.
The TF XO moderates the war game, facilitates and focuses discussion, and
resolves disputes to keep the war game on schedule.
Determine how much time is available for the war game and ensure that
this limit is observed.
Allocate a specific amount of time for each COA. (Normally more for
the first COA because of slower initial process).
Conduct the war game according to the prioritized list of critical events
within allotted timeline.
War game critical events.
Use a synchronization matrix or war game worksheet. Critical events are
identified and war gamed by battlefield operating system, with four
columns, headed: Action, Reaction, Counteraction, and Reaction.
Gather the Tools/Assemble the Battle staff. Post the COA Statement and
Sketch. (Note: A preferred technique is to supplement this with an overview
sketch of each critical engagement for all COAs on a dry erase board with
copy capability. Beneath each sketch, the assistant S3 lists critical
battles/events and the S2 lists pertinent expected enemy activities associated
with that engagement). Post the Initial (Draft) Commander's Intent and
Commander's Guidance from Mission Analysis. Erect the war gaming table
with map and tentative graphics. Gather the battle staff. Distribute copies of
the COA statement and sketch (on one document if possible).
Brief the Course of Action. S2 quickly reviews the SITTEMP and any
pertinent intelligence updates. Planner briefs general concept of the
operation. Planner briefs scheme of maneuver for each phase and / or critical
engagement.
Questions on Course of Action. The XO / S3 opens the floor for clarification
of the COA. (This is NOT the time for BOS input; rather, it is a chance to
ensure the plans team understands the COA before proceeding).
BOS Input. XO / S3 queries each member of the battle staff to provide the
following:
Any suggested modifications to the COA
Brief general concept on how his BOS will support the COA
Alibi Time. Any member of the battle staff may address any issue
pertinent to the COA not covered to their satisfaction to this point.
Open the board up for BOS graphics input / analysis.
The most critical phase of the war game is preparation. Following are some
of the critical preparation responsibilities.
Have available examples of critical events and decision points in the offense:
passage of lines; breaching of main obstacle belt; penetration; reaction to
counterattack; seizing the objectives; BCT shaping operations, including use
of artillery fires and attack helicopters.
The S2 identifies the enemy situation expected at the start of the war game.
Unit locations, strengths, postures, and probable intents are specified. The
specific enemy course of action to be wargamed is explained.
The game starts at the first reliably known start point for the task force,
either in the TAA, defensive sector, or LD / LC.
XO
K nown decision points ADO
S2 Critical events to be wargam ed Staff Inputs Tentative system s positions
S2
Enem y repositioning PIR / NAI linkages To M ovem ent triggers
Reserve comm itm ent Wargaming Anticipated W CS changes
Special m unitions use S1 / S4
Obstacle locations
Fort Leavenworth, KS 66027-2346 Scout recon tim eline Projected supply status ENG
Engineer assets available
Reconnaissance operations Projected personnel status
Tentative AXP locations Tentative breach sites
S3 Tentative trains location Directed obstacles
M ovem ent rates Tentative m obile preposition / Tentative situational obstacles
Breach tim eline cache locations OBSINTEL focus
Actions on the objective
© Battle Command Training Center (BCTC)
Page 73
www-bctc.army.mil
ARNG POCKET PLANNING GUIDE
ASSETS
TIME
DECISION POINT
CCIR
CONTROL
MEASURES
REMARKS
Synchronization Matrix.
TIME
H - ______ H - HOUR H + ______ H + ______
EVENT
ENEMY ACTION
DECISION
POINTS
M TM A
A
N
TM B
E
U
V TM C
E
R
TM D
FIRE SPT
ADA
AVN
ENG
INTEL
CSS
C2
NOTES
COA comparison starts with all the staff members analyzing and evaluating
the advantages and disadvantages of each COA from their perspectives.
Staff members each present their findings for the other’s consideration.
Using the evaluation criteria developed before the war game, the staff
outlines each COA and highlights its advantages and disadvantages. By
comparing the strengths and weaknesses of each COA, a logical choice
emerges.
Perform
• War game results • Decision matrix Outputs
• Staff estimates
Inputs COA • COA decision briefing
Comparison
Process
• Conduct a COA advantage & disadvantage analysis
• Compare COAs
• Develop a recommended COA
The selected COA should represent the highest probability of success against
the most likely enemy COA and the most dangerous COA and:
pose the minimum risk to the force and mission accomplishment
place the force in the best posture for future operations
provide maximum latitude for initiative by subordinates
provide the most flexibility to meet unexpected threats and
opportunities.
Three Components
Perform
Staff recommends a COA COA CDR decides which COA to approve
Approval
Decision Matrix
A Decision Matrix is a tool that helps the commander visualize the
comparison results of the wargame.
Decision Matrix
Courses of Action Advantages Disadvantages
Force ratios
Main Attack
Supporting Attack
Decision Briefing
The purpose of the decision briefing is to allow the commander the benefit
of the staff’s analysis of how the fight unfolds, a dispassionate analysis of
the COAs war gamed, and the staff recommendation. While there are
differences in the stated formats in FM 101-5 and FM 5-0, this purpose
should be the constant factor influencing the format. Following are the listed
formats in both FMs.
FM101-5
Intent of higher headquarters
Restated mission
Status of own forces
Updated intelligence estimate presentation of COAs
Recommended COA
FM 5-0
Enemy COA that were war-gamed
Friendly COAs that were war-gamed
Wargaming technique used
For each COA war-gamed (critical events, possible enemy actions and
reactions, modifications to the COA, strengths and weaknesses)
Results of the war game
The staff prepares the order or plan by turning the selected COA into a clear,
concise concept of operations and required supporting information. The
concept of operations for the approved COA becomes the concept of
operations for the plan, and the COA sketch the basis for the operations
overlay. Commanders review and approve orders before the staff reproduces
and disseminates them.
Produce
Staff prepares the order or plan by turning
Staff preparesCOA
the order The
the selected into aorclear,
planconcise
by turning
the selected
concept of COA into a clear, concise
operations. Order
concept of operations.
Staff implements risk controls by The order communicates how controls are The order is briefed to subordinate
Staff implements risk controls by The The order is briefed
CDRtoand
subordinate
coordinating and integrating them into the putorder communicates
into effect, how controls are
their implementation, and commanders.
commanders.
staff conduct
coordinating
order. and integrating them into the put
howinto effect,
they their
fit into implementation,
the and
overall operation. confirmationCDR andwith
briefing staffsubordinates
conduct
order. how they fit into the overall operation. confirmation
afterwards. briefing with subordinates
afterwards.
Orders Annexes
Following is a list of orders annexes. Units may dictate which annexes and
appendices they want to accompany their base order and their length.
If the OPORD is for an offensive operation, generally only the enemy event
template, operations, and fires overlay will be disseminated with the order;
defensive orders will also include an engineer overlay. Other overlays, such
as air defense and CSS, will be completed and remain posted or accessible in
the TOC but not necessarily disseminated.
This section addresses the organization of the TF Fire Support Element, the
supporting Tactical Air Control Party (TACP), and indirect fire assets /
capabilities, and TF planning / fires integration procedures.
TF Fire Support Element (FSE). The FSE is designed to help the task force
commander and staff integrate FS and lethal and non-lethal effects into all
plans. The major functions of the FSE are to:
Plan, control, and synchronize all FS.
Establish priorities and allocate available FS resources to support the
TF.
Participate in and supervise the routine activity and coordination of the
targeting process within the task force main CP.
Coordinate with the A2C2 element regarding artillery firing unit
locations, changes to FSCMs, and airspace coordination measures
(ACMs).
Coordinate air support through the TACP.
Coordinate suppression of enemy air defense (SEAD) and / or joint
SEAD (J-SEAD) operations.
Coordinate combat aviation employment with FS operations.
Air Force units are attached to the TF to plan, control, and direct close air
support. The TACP is the normal air force asset attached to the TF.
Artillery Munitions
COPPERHEAD is a 155-mm cannon launched guided projectile with a
shaped charge and laser seeker. The optimum use of COPPERHEAD is
against multiple targets in large arrays outside the range of maneuver direct
fire systems. Moving targets can be engaged at a range of three to four KM
depending on the skill of the observer. Stationary targets can be engaged out
to five KM. The minimum visibility for effective COPPERHEAD use is
five KM. Angle T should not exceed eight hundred mils left or right of the
gun-target line.
Cannon Artillery Smoke Rounds. Plan for no more than sixty minutes of
smoke from a DS battalion. Both White Phosphorous (WP) and Smoke
rounds take thirty seconds time to build up effective smoke. WP rounds have
an average burn time of sixty to ninety seconds per round while Smoke
rounds average burn time is five to ten minutes.
For planning purposes the TF can plan on one or two priority targets when
they are the main effort of the BCT. However if the TF is the supporting
effort, then the TF should plan on using the mortars for one or two priority
targets and not the DS artillery battalion.
For force protection, the artillery batteries are integrated within the TF.
When the DS cannon battalion fires missions, normally the entire battalion
(eighteen howitzers) fire on a single target with three rounds each. By
massing the indirect fires on one target, they are much more effective.
The M120 mortar is capable of firing fifteen rounds per minute for the first
minute, with a sustained rate of fire of four rounds per minute after the first
minute. It is capable of firing high explosives, illumination, and white
phosphorus rounds to a maximum range of 7,200 meters. Mortars provide
the TF commander with the most responsive fires. Use the mortars for FPFs,
and for initiating and sustaining smoke missions. They are also effective in
urban areas given high angle fire and comparatively reduced collateral
effects.
The TF Mortar Net is the primary means to clear mortar fires and the TF
Fires Net is the alternate net. The mortar platoon is normally kept together
under centralized control and but can be split into two sections.
Within the TF, mortars will normally be given to the supporting effort.
Mortars are effective when employed against dismounts covering obstacles,
covering infiltration and exfiltration routes, and for providing immediate
smoke.
ADVANTAGES LIMITATIONS
Fast response rate Short range
High rate of fire Limited ammo carrying capacity
Fire from deep defilade Ammo resupply
Fire without FDC Less accurate in high winds
High-angle fire Detected by radar
Attack targets on reverse slopes Ineffective against point targets
Simplicity Lack of organic survey and MET
Task Force Commander. The key role of the task force commander in
indirect fire planning is the synchronization of fires with maneuver. Fires
and maneuver must be thought of together. Commanders must first decide
precisely what they want their fires to accomplish.
For each phase or time period of the operation the FSO should, as a
minimum:
Verify grid locations for all critical targets
Verify engagement criteria
Confirm primary and backup observers for each target
Verify primary and backup communications links for each observer
Verify that each target has a task and purpose (what effects are to be
achieved)
Verify the method of engagement (at my command, time on target, or
when ready)
Verify that attack guidance, such as shell-fuse combination, number of
volleys, and unit(s) to fire, is specified for each target
Verify the movement plan, specifying when and where units and
observers will move
Keep it simple (not more than ten TF Targets); memorize priority targets.
Plan on an eight-minute shift times between priority targets.
Mass all artillery on three or four essential fire support targets rather than
pound sand everywhere on the battlefield. For defensive operations, probable
priority targets include likely penetrations points, anticipated enemy breach
sites, defiles/choke points, and behind the most likely inter-visibility line(s)
that the enemy will use for ABF / SBF positions.
A fully developed essential fire support task has a task, purpose, method, and
effects.
Triggers
Observation plan
Communication plan
Decontamination plan
First aid / casualty collection plan
Re-supply plan
At times a Task Force may have a mechanized smoke platoon and one dual-
purpose platoon. These platoons should be kept intact and not split into
squads. Assignment of smoke support within the TF is dependent on the
mission and forces employed. Units must coordinate with adjacent units for
cross boundary smoke effects.
Smoke Uses
Offensive Operations:
Obscure enemy reconnaissance efforts
Conceal river crossings
Conceal breaching operations
Isolate enemy forces
Defeat enemy electro-optical systems
Deception
Defensive Operations:
Obscure enemy reconnaissance efforts
Conceal obstacle emplacement
Canalize enemy forces
Isolate enemy forces
Defeat enemy electro-optical systems
Deception
Conceal movement of disengaging forces
Air Defense Artillery protects the TF and selected assets from aerial attack
and surveillance. The primary aerial threats that must be countered by Short
Range AD (SHORAD) employment guidelines are UAVs, rotary-wing
aircraft, and fixed-wing aircraft. A task force is typically supported by a
Linebacker platoon, consisting of four firing units and a C2 vehicle. The
platoon is organized into a headquarters section and two maneuver sections.
Linebacker firing units should be positioned along the most likely air
avenues of approach to support the Commander’s main effort and also
positioned in depth so that they can provide continuous fires along enemy air
avenues.
Linebackers normally accompany the main effort of the task force or may be
positioned with the task force reserve in the defense. Other likely points of
protection include breach sites and passage lanes, ROM sites, and guarding
likely PZs during limited visibility periods.
The task force and air defense firing units broadcast flash precedence “FM
voice” early warning to maneuver elements on the TF Command net.
The ADA LNO and his driver position themselves with the TF CP full time.
The Linebacker platoon leader rotates his time between the TF Main CP and
his platoon. He is actively involved in the planning process for each TF
mission.
The ADA LNO in the TF CP monitors four nets: Division Early Warning;
the TF command net; the ADA battery net; and the Linebacker platoon net.
During Transition:
Reorganize assets, task organization change required
Reconstitute assets
Establish Class IV / V points
Dig in Q36, FA, C2, ADA, Log
FASCAM to facilitate transition to defense.
REPORTS
A key requirement during the planning process is knowledge of the various
reports that will be required internal to the battalion and external to higher,
adjacent, and subordinate elements. Following are fifty-four (54) examples
of reports and formats the battalion may need to use. They are organized as
follows:
Operations Reports
Operations Report (OPREP)
SALT / SPOT Report
Serious Incident Report (SIR)
Contact Report
Situation Report (SITREP)
Combat Slant Report (Long and Short)
Closure Report
Airspace Control Means Request (ACMREQ)
Downed / Missing Aircraft Report
NBC Reports
Request for NBC / Smoke Support
NBC 1 Report (Initial Observer Report)
NBC 2 Report (Evaluated Data Report)
NBC 3 Report (Immediate Warning of Expected Contamination)
NBC 4 Report (Report of Radiation Dose Rate Measurement)
NBC 5 Report (Report of Areas of Contamination)
NBC 6 Report (Detailed Contamination Report)
CHEMWARN Report
Effective Downwind Message Report
NBC Situation Report (NBC SITREP)
Engineer Reports
Scatterable Minefield Warning Report (SCATMINWARN)
Scatterable Minefield Report and Record (SCATMINREP)
Obstacle Turnover / Transfer Report
Report for Bridge, Overpass, Culvert, Underpass or Tunnel
(BRIDGEREP)
Report of Ford, Ferry, or Other Crossing Site (CROSSREP)
Obstacle Report
Obstacle Request, Intent or Status Report
Route Reconnaissance Report (ROUTEREP)
Closure Report
Bypass Report
Intelligence Reports
Sensitive Item Report
Battle Damage Assessment Report (BDAREP)
Detained Civilian Personnel Report (DETAINCIVREP)
R&S Report
Weather Forecast
Weather Advisory
Request for Information (RFI)
Response to Request for Information (RRFI)
Intelligence Summary (INTSUM)
Patrol Report
EPW / Captured Material Report
SAEDA Report
SALUTE A Report
Debrief Format
Personnel Reports
Personnel Status Report (PERSTAT)
Personnel SPOT Report
Casualty Report
MEDEVAC Request
Medical Situation Report (MEDSITREP)
Casualty Feeder Report
Logistics Reports
Logistics Status Report (LOGSTAT)
Battle Loss Report
AMMO Status / Request
POL Status / Request
Operations Reports
The OPREP outlines the relative combat power of each Task Force unit.
Place color code (green / amber / red / black) in items 1-5. Green = 100-
80%, Amber = 79-60%, Red = 59-40%, and Black = 39-0%. Add %
complete for item #5. Put number of mission capable / number authorized in
items 6-28.
Format
Line / Item / Quantity
Sample OPREP
Purpose
Provide and disseminate information on enemy activity and contact.
Instructions
FBCB2 is the primary method in order to establish SU visibility across the
network. FM is the alternate method. In many cases, an FM report should
occur first followed by a digital report. Units in contact will report the
enemy via FM to the company CP, XO or 1SG who will enter the digital
report.
Format
Size. Give number and type of assets observed. Be as specific as possible, using
individual systems.
Activity. Specific actions of enemy force observed. Include orientation, movement
direction, speed and as much information on their actions as possible.
Location. Grid of enemy activity observed. Use 6-digit grids whenever possible.
Avoid generic descriptive names for landmarks.
Time. Time of enemy activity; not the time of message if significantly different.
Your Actions. What actions are you taking at the time you submit the report.
FBCB2 Report
The FBCB2 SALT Report is selected from the Combat Messages. Fill in the
mandatory fields using the drop down menus. Users with LRF can LASE
the enemy and auto fill the location. Those without LRF should use the auto
fill capability by selecting the location on the FBCB2 map.
The grid may also be typed in (include grid zone designator).
Do not delete from the default address group, additions may be made.
Ensure that the BDE S2 or TF S2 ASAS is included in the action addressees.
The Long form of the message may be used for providing additional
information or for creating a Position Report for a friendly element (see Card
214.9).
If the CFF MSG button is used, the only options will be immediate
suppression or immediate smoke. The user must be in the AFATDS
observer role database, and the supporting FSE AFATDS must be in the
address group.
From: CDR, X
To: CDR, X
Subject: Serious Incident Report, Number XXXXXXX
Category
Type of Incident:
Date / Time:
Location:
Other Information
Training related:
Firing incident
Personnel Involved:
Name
Rank or Grade
Social Security Number
Race
Sex
Age
Position:
Security Clearance: Y or N
Unit; Station of Assignment
Duty Status
Summary of Incident:
Commander Reporting
Point of Contact;
Downgrading Instructions
Report Originated by
Report Released By
Notification:
Position
Name
Time
Category of Incidents
Category 1:
Fratricide
Riots, serious disturbances
War crimes
Soldiers requesting asylum
Terrorist activities
Bomb or explosion incident
Threats against weapons / ammunition
Category 2:
Loss / theft of sensitive items
Narcotics / drugs
Theft / loss of ammunition, armament, or explosives
Contact Report
Format
Call sign
Contact
Form of contact (observed, obstacle, direct fire, NBC, etc.)
Cardinal Direction or grid reference
Out
Purpose
Provides update on unit status, activities, and problems.
Instructions
Battalions submit via MCS, MSE or FM (in priority). Separate companies
submit via FBCB2 SITREP or Free Text Message following the format
below modified to fit their unit. Provide unit locations only if friendly force
SU feed is not functioning at the command post. Individual platforms send
SITREP to PL / PSG who consolidate and forward to 1SG / XO /
Commander / CP. Reports are due NLT 0545 or at Stand-to as specified and
at 1630. Mid-day and night reports are not required unless directed. Reports
are due to TF at 0500, 1100, 1700, and 2300. Reports from TF are due to
BDE Main CP at 0600, 1200, 1800, and 2400 daily.
Format
Line 1: Unit:
Line 2: Main CP Location: (6- digit grid)
Line 3: Obstacle / defensive prep status (% complete)
Line 4: Scout / IEW OP locations
Line 5: _______ Co/Tm: ____ / ____ / __________ M1 M2 (6-digit grid)
Line 6: _______ Co/Tm: ____ / ____ / __________M1 M2 (6-digit grid)
Line 7: _______ Co/Tm: ____ / ____ / __________M1 M2 (6-digit grid)
Line 8: _______ Co/Tm: ____ / ____ / __________M1 M2 (6-digit grid)
Line 9: _______ Co/Tm: ____ / ____ / __________M1 M2 (6-digit grid
Line 10: TF : / / / M1 M2 M3 Mortar SCT)
Line 11: CLIII Assessment: (*GREEN, AMBER, RED, BLACK)
Line 12: CLV Assessment: (*GREEN, AMBER, RED, BLACK)
Line 13: Personnel Assessment: (*GREEN, AMBER, RED, BLACK) *GREEN (80+%) -
AMBER (60-79%) - RED (40-59%) BLACK (39% or less)
Line 14: Overall Assessment: GREEN: Fully mission capable AMBER: Status has minor
impact RED: Status has major impact BLACK: Cannot accomplish mission
Line 15 (remarks): give reason for any line 14 rating other than green. "paint the picture" of the
unit, from east to west or north to south.
FBCB2 Report
Company / troop and smaller elements reporting to brigade / task force
should submit the SITREP using FBCB2. The report should be
accompanied by comments to elaborate on the basic status information
provided in the report format and to paint the picture of the unit and actions
on-going and projected.
The Self Tab reports data for own platform. The Unit Tab has option for
‘Platforms’ (those in the reporting unit), and ‘Units’ for the status of the
immediately subordinate units (for a company / troop it would be for the
subordinate platoons).
Any element in the unit can submit the report.
This report states the number of primary combat vehicles the unit has that
are both operational and under the control of the unit. If a vehicle is non-
mission capable, it is not counted in this report.
Closure Report
Purpose
Reports unit movement status and capability of units to conduct future
operations.
Instructions
Submit using FBCB2 Free Text message as primary with FM as alternate.
Battalions may submit Closure Reports using MCS or MSE as alternate.
Submit report to TF / BDE Main with info addresses TF / BDE TAC, BDE
ALOC, BDE CDR / CSM / S3. Garrison reports may be submitted by
telephone.
Submit initial report via FM including unit and CP location upon closure of
TOC. Submit final report upon completion of movement of the main body,
or at a designated time, to the TF / BDE MAIN CP (field) or brigade
SDNCO (garrison). The closure report is a status report and units need not
be 100% to submit. A final report, however, is required once the unit is
100% complete (NLT arrival + 2 hours). For prolonged or complex
movements (combination of transport modes), submit report every two hours
or as directed by brigade.
Format
SP date / time.
RP date / time.
CP location (6-digit grid).
Closure date / time.
Accidents / incidents.
Estimated time unit ready to conduct operations.
Weapons / sensitive items inventory complete (YES / NO).
Report Number
A025 (USMTF # F658)
Instructions
Use To Request That A Specific Airspace Control Means Be Specified In A
Future Airspace Control Order.
Reference FM 100-103
Format
LINE 1 – DATE AND TIME (DTG)
LINE 2 – UNIT (Unit Making Report)
LINE 3 – REQUESTING UNIT (Name of Unit or Agency Requesting Airspace)
LINE 4 – TYPE (Type of Airspace)
LINE 5 – AIRSPACE (Name of Airspace)
LINE 6 – PURPOSE (Purpose of Special Use Airspace)
LINE 7 – TRANSIT (Transit Instructions)
LINE 8 – FROM (DTG to be Established)
LINE 9 – UNTIL (DTG to be Dis-established)
LINE 10 – AREA (Description of the Area to be Defined (Boundary or Circle))
LINE 11 – COORDINATES (UTM or 6-Digit Grid Coordinate with MGRS Grid Zone
Designator)
LINE 12 – WIDTH / RADIUS (Width or Radius)
LINE 13 – LOWER (Lower Altitude of Designated Area to Nearest 100 Feet or Ground Level)
LINE 14 – UPPER (Upper Altitude of Designated Area to Nearest 100 Feet)
LINE 15 – CONTACT (Call Sign of Control Agency)
LINE 16 – PRIMARY (Primary Frequency or Frequency Designator)
LINE 17 – SECONDARY (Secondary Frequency or Frequency Designator)
LINE 18 – NARRATIVE (Free Text for Additional Information Required for Clarification of
Report)
LINE 19 – AUTHENTICATION (Report Authentication)
Purpose
To report downed or missing friendly aircraft.
Instructions
Submit initial report to TF / BDE Main using FM on TF / BDE CMD net.
Report to higher on DIV CMD net and to DIV G3 OPS via MSE. Submit
follow-up reports to BDE Main via FM, MCS, FBCB2 (Free Text message)
or FM.
Format
Type of Aircraft (describe A/C if type unknown) (e.g., “H-60 Blackhawk”)
A/C Call sign or Tail Number if known (any markings if unknown) (e.g., “Shark 23”)
Grid location and / or nearest landmark or graphic control measure (e.g., “14RPV 654 765, LZ
Silver”)
Time of downing if known (e.g., “0655 Zulu”)
Number / status of survivors and their last action if known (include last known radio frequency)
(e.g., “Two crewmen seen exiting and moving south into tree line”)
Status of A/C (e.g., “Aircraft on fire” or “Aircraft intact, damage to rotors”)
Cause of downing if known (include anti-aircraft weapon type if shot down) (e.g., “Shot down
by small arms” or “rotor blades struck tress”)
Enemy / Threat / NBC in vicinity of aircraft if known (e.g., “2 Enemy soldiers seen searching
aircraft”)
Friendly forces in vicinity of A/C and actions if known (e.g., “Scout 42 moving to secure crash
site”)
NBC Reports
Format
Requesting Unit ID
Type of support requested: (Note 1)
FM Net and VINSON key for coordination / contact: (Note 2)
Location of mission: (6-digit grid)
Location of contact point: (Notes 3 and 6)
Type of mission being supported: (Note 4)
Amount of support requested: (Note 5)
Mission start DTG: (Note 6)
Mission end DTG: (Note 6)
Point of contact in unit
Remarks
BB CMD, BDE O/I, BDE A/L, CO CMD, etc. indicate which net and secure
key in the SOI is to be used for coordination and / or contact.
Location and time where supporting unit is to meet supported unit. This
location should be for initial contact and detailed coordination / planning.
Purpose
Reports observation or detection of a nuclear, biological or chemical attack.
Instructions
Submitted by the fastest means available. Initial reports should be by FM
and immediately followed by an FBCB2 NBC1 report to create a geo-
reference icon on the network. DO NOT DELAY SENDING THE
REPORT in an effort to make it complete. Send what you have
immediately. Always initiate with “NBC 1 Report” and state what kind –
Nuclear, Biological or Chemical.
Omit information that is not applicable or available. Items that must always
be included are type of report, lines D and H, and one of the following: B,
C, F, or G. Ensure TF / BDE Main and TF / BDE CHEMO are included in
addressees. TF / BDE Chemical forward report to higher, adjacent and
subordinate units by fastest means available, following with MCS report.
Format
ALPHA: Strike serial number (if known).
BRAVO: Position of observer (UTM coordinates or name of place).
CHARLIE: Grid or magnetic bearing (specify which is used) or azimuth of attack from
observer (in degrees or mils; specify which is used).
DELTA: DTG attack started (ZULU).
ECHO: Illumination time in seconds (for nuclear burst); time the attack ended (toxic agent
attack only).
FOXTROT: Location of attack (UTM coordinates) and / or vicinity of attack (actual or
estimated; specify which is given).
GOLF: Means of delivery (if known).
HOTEL: Type of burst (air, surface, unknown), type of toxic agent, or type of attack.
INDIA: Number of shells; other data (for toxic attack only).
JULIET: Flash-to-bang time (in seconds).
KILO: Crater present or absent; diameter in meters (if known).
LIMA: Cloud width (degrees or mils; specify which) five minutes after burst.
MIKE: Cloud height (top or bottom; specify which) ten minutes after burst (degrees or mils;
specify which).
SIERRA: DTG of reading (local or ZULU time).
Note: Carefully specify the units of measure used (degrees, mils, or grid
azimuth).
FBCB2 Report
Select the NBC 1 Report from the Combat Messages Box using the
NBC 1 tab. Use the drop down menus to fill in the type of attack and
the delivery means (if known).
Fill in the attack locations by either typing in the grid location
(including grid zone designator), using the Map option and clicking the
cursor on the location of the attack on the map display, or using the LRF
fill if platform is capable.
Use the Long Form message for providing additional information.
The report will create a geo-referenced contamination icon network
wide.
Ensure the TF / BDE Main (S3 and Chemical), TF / BDE TAC and Rear
CPs are included in the action addressees.
Purpose
Provides warning of expected NBC contamination.
Instructions
Normally initiated by BDE or higher. Disseminate via FM, FBCB2 and
MCS to ensure all units alerted.
Always initiate with “NBC 3 Report” and state what kind – Nuclear,
Biological or Chemical.
Format
ALPHA: Strike serial number (if known).
DELTA: DTG when attack started.
FOXTROT: Location of attack (actual or estimated; specify which).
PAPA: Area of expected contamination.
YANKEE: Bearing or azimuth of left, then right radial lines (specify degrees or mils; use four
digits for each line).
ZULU: Effective downwind speed (in Km-PH; use three digits), downwind effective distance
of Zone 1 (in km; use three digits), and cloud radius (in km; use two digits).
FBCB2 Report
The NBC 3 report is usually disseminated from brigade or higher echelon.
The message subtype (nuclear or chemical / biological) must be filled out
along with Strike Serial #, Attack Time, Attack Location, and Wind data.
Report must be disseminated unit wide.
Purpose
Reports detection and monitoring of radiation.
Instructions
Submit initial report when radiation initially detected and routinely thereafter
as defined in OPORD. State “NBC 4” at the start of FM reporting. Submit
initial report via FBCB2 with an FM alert to higher headquarters, ensuring
all TF / BDE command posts and TF / BDE Chemo are included in
addressees. BDE Chemo disseminates to higher, adjacent and subordinate
units via MCS and / or MSE.
Format
QUEBEC: Location of reading; use friendly graphics or encryption. Omit this line when
transmitting on a wire net.
ROMEO: Dose rate in cGy / hr (average total dose rounded to the nearest ten cGy). Specify
whether the dose rate is "INITIAL," "INCREASING," "PEAK," or "DECREASING;" specify
"SHIELDED" if the dose rate was measured inside a vehicle.
SIERRA: DTG of reading. Specify the time zone.
FBCB2 Report
The message subtype (nuclear or bio / chemical survey), type event and
attack analysis data must be completed along with reading location and
results. Strike Serial # is filled if known.
Purpose
Reports areas of contamination.
Instructions
Submit initial report when radiation initially detected and routinely thereafter
as defined in OPORD. State “NBC 5” at the start of FM reporting.
Submit initial report via FBCB2 Free Text message with an overlay of the
contaminated area. Send an FM alert to higher headquarters, and ensure all
TF / BDE command posts and TF / BDE Chemo are included in addressees.
BDE CHEMO disseminates to higher, adjacent and subordinate units via
MCS and / or MSE.
Format
ALPHA: Strike serial number, if known.
OSCAR: Reference DTG for estimated contours of contaminated areas.
SIERRA: DTG when contamination was initially detected.
TANGO: H+1 DTG or DTG of latest reconnaissance of contamination in the area.
UNIFORM: Coordinates of contour lines marking dose rate of one thousand (1,000) cGy/hr.
VICTOR: Coordinates of contour lines marking dose rate of three hundred (300) cGy/hr.
WHISKEY: Coordinates of contour lines marking dose rate of one hundred (100) cGy/hr.
X-RAY: Coordinates of contour lines marking dose rate of twenty (20) cGy/hr.
CHEMWARN Report
Due to Battalion NLT 1630 hours daily with an as-of time of 1600 hours by
all subordinate units.
1. DTG / Unit
2. Enemy NBC Activity: (briefly state, i.e., “Enemy has increased protection
or tempo of NBC attacks, employing SCUDS, FROGS, MRL and tube
artillery assets.”
3. Enemy NBC Attacks: (DTG of attack, location, unit attacked, agent used,
delivery system, NBC casualties).
Engineer Reports
Purpose
Sent on BN CMD net one hour prior to emplacement.
Format
Line A: EMPLACING SYSTEM:
Line B: AT: YES / NO
Line C: AP: YES / NO
Line D: # AIM POINTS/CORNER POINTS:
Line E: GRID COORDINATES OF AIM POINTS / CORNER POINTS AND SIZE OF
SAFETY ZONE:
Line F: DTG OF SELF-DESTRUCT PERIOD
Format
Line 1: APPROVING AUTHORITY:
Line 2: TGT OBSTACLE NUMBER:
Line 3: TYPE EMPLACING SYSTEM:
Line 4: TYPE MINES:
Line 5: SELF-DESTRUCT PERIOD:
Line 6: AIM POINTS / CORNER POINTS OF MINEFIELD:
Line 7: _____________________________________
Line 8: _____________________________________
Line 9: _____________________________________
Line 10: ____________________________________
Line 11-14: __________________________________
Line 15: SIZE OF SAFETY ZONE FROM AIM POINT:
Line 16: UNIT EMPLACING MINES / RPT #:
Line 17: PERSON COMPLETING REPORT:
Line 18: DTG OF REPORT:
Line 19: REMARKS:
OBSTACLE-TURNOVER/TRANSFER REPORT
OBSTACLE DATA
Obstacle Number Obstacle Type Emplacing Authority
TURNOVER CHECKLIST
Intelligence.
• Enemy activity forward of the obstacle (discuss enemy recon and breaching efforts).
• Friendly activity in the vicinity of the obstacle (discuss LOGPAC, recon, counter-recon maneuver).
Maneuver.
• Obstacle protection against enemy recon/breaching (discuss overwatch, counter-recon patrols,
sunrise sweep).
• Location of TRPs and indirect-fire targets (point out location on graphics and terrain).
• Rearward/forward passage of lines (discuss planned and routine activity around the obstacle).
Mobility/Survivability
• Obstacle trace (discuss corner grids on map and point them out on terrain).
• Obstacle marking (rear side, all four sides, fence, signs, HEMMS poles, or no marking).
• Obstacle composition.
• Location of gaps/lanes.
• Method of closing gaps/lanes (MOPMS, ADAM, RAAM, conventional mines).
• Location of material to close gaps/lanes.
CSS. Planned casualty evacuation and supply routes in the vicinity of the obstacle.
C²
• DA Form 1355 or 1355-R, dated __________, transferred to receiving unit.
• Obstacle overlay, dated ___________, transferred to receiving unit.
• Target folder, dated _________, preparing headquarters ____________, transferred to receiving uni
• Higher headquarters (transferring, receiving, and emplacing units) notified of transfer.
• DA Form 1355 or 1355-R forwarded. (NOTE: Three copies are required for transfer – one to
transferring unit, one to receiving unit, and one to next higher headquarters common to both.
CERTIFICATION
The undersigned certify that the receiving unit has assumed full responsibility for the obstacle indicated above.
The unit commander understands all the information related to the obstacle, the obstacle intent, and his
responsibility to transfer or recover the obstacle upon his departure.
___________________________________
___________________________________
Signature of Transferring Unit Commander Signature of Receiving Unit
Commander __________________________________
___________________________________
Printed Name, Rank, and Date Printed Name, Rank, and
Date
Purpose
To report nature and condition of bridge, overpass, culvert, underpass or
tunnel.
Instructions
Use FBCB2 Bridge Report as primary means of reporting. Since the
BRIDGEREP creates a network wide icon with an associated hook dialog
box with the text information from the message format, specific addressing
is not required. If specific comments are included in the report comment
box, only those to whom the message is addressed will receive those, so
include the unit leadership, CP and supporting engineers in the address
group. Submit FM reports to the next higher CP, unit leader or engineer as
appropriate.
Format
Type and location (for a long tunnel, include both entrance and exit locations).
Overall length.
Width of roadway.
Height restrictions.
Length and number of spans.
Computed classification.
Bypass locations and conditions. Use this report for disseminating bypass
information.
FBCB2 Report
The bridge report creates a geo-referenced icon network wide and can be
used for sending bridge data, but is also used for creating an icon for a lane
through an obstacle or an obstacle bypass. For creating a lane icon, the
message is filled as shown below, with no statement for bridge type, the start
and end points for the lane in the bridge beginning and end location fields,
and unknown for the controlling force field.
Purpose
Reports nature and condition of ford, ferry or other crossing site.
Instructions
Utilize FBCB2 Free Text Message as primary means. Battalions may submit
using MCS or MSE. FM is least preferred method.
For all echelons, send report to next higher main CP and supporting
engineer. Include unit leaders as appropriate or directed.
Format
Type and location.
Length of crossing in meters.
Usable width.
Current speed in meters per second.
Maximum depth in meters.
Bottom material and condition.
Capacity classification of any existing ferry equipment.
Slope of entry bank.
Slope of exit bank.
Other comments as necessary.
Obstacle Report
Purpose
Reports obstacles encountered or constructed.
Instructions
Submit immediately when obstacle is observed or when obstacle
construction is initiated. Utilize FBCB2 Obstacle Report as primary means.
The network-wide icon has a hook dialog box with the formatted message
information. If special comments are included only those to whom the
message is addressed will receive the message with comments. In this case,
include those who need to read the comments (supporting engineer, S3
section or unit leaders). TF Engineer forward to BDE Engineer via FBCB2
or MCS; BDE Engineer forward to DIV and higher / adjacent units using
MCS (message and overlay as appropriate).
Format
Type of obstacle or obstruction.
Location, using grid coordinates. For large, complex obstacles, send the coordinates
of the ends and of all turn points.
Dimensions and orientation.
Composition.
Enemy weapons influencing obstacle.
Observer's actions.
Soil
FBCB2 Report
The obstacle report will create a geo-referenced icon network wide. It is
critical that the report be generated when an obstacle is initiated / completed,
or when an unreported obstacle is encountered. Utilize the drop down
menus to complete the report, ensuring that all corners/points of the obstacle
are entered in the location fields.
Purpose
To request, report intention or status on all obstacles.
Instructions
Submitted by all assigned and attached units requesting or emplacing
obstacles in the BDE or TF AO. Submitted when requesting to emplace and
report intention to construct an obstacle. Also used to report the status of
obstacle emplacement (25%, 50%, 75%, 100%). Submitted to next higher
headquarters (and forwarded higher) by fastest means available. Within the
BDE, FBCB2 is the primary means followed by MCS and MSE. FM is the
least desired means. Use FBCB2 Obstacle Report to create geo-referenced
icon when beginning construction. Use free text format for requesting
obstacle emplacement.
Format
Line-Item-Example
1OBSTACLE CONTROL DESIGNATOR Ex: (I004-H14-MD01)
OBSTACLE LOCATION (GRID)
EFFECTIVE DATE/TIME DATA (DTG)
EMPLACING UNIT Ex: (1/A/299 EN BN)
IMPACT ON MOVEMENT Ex: (DISRUPT)
OBSTACLE TYPE Ex: (MINEFIELD)
OBSTACLE DIMENSIONS (Height, Depth, Width, Length)
MINEFIELD DATA (LAND SURFACE)
OBSTACLE STATUS (PLANNED / EXECUTED)
SAFE LANE LOCATION (GRID)
11ENEMY ACTIVITY Ex: (ATTACKING)
BYPASS POTENTIAL (EASY / DIFFICULT)
BY LOCATION (GRID)
OBSERVATION DTG
COMMENTS (REMARKS)
Format
Line-Item-Example
Approving Authority
Ex: BDE CDR
Target / Obstacle Number
Ex: I004-K1A-SM01
Type of emplacing system
Ex: MOPMS
Type of mines
Ex: AP / AT
Life Cycle
Ex: NET 270400MAY00
Ex: NLT 271000MAY00
Ex: 4HR
Aim Point
Ex: PV04586210 COM
Corner Point
Ex: Centerline SP*
Corner Point
Ex: Centerline EP*
Corner Point
Ex: Friendly Side SP**
Corner Point
Ex: Friendly Side EP**
Corner Point
Ex: Enemy Side SP**
Corner Point
Ex: Enemy Side EP**
Corner Point
Corner Point
Size of safety zone from aim point
Ex: 55 m Radius from COM***
Unit emplacing mines
Ex: EN SCT / 299 EN BN
Person completing report
Ex: 1LT DABE
DTG of report
Ex: 250300MAY00
Remarks
Ex: Trigger is FSE south at NAI 501
Notes:
COM (Center of Minefield
SP (Start Point)
EP (End Pt)
* Ground / Air Volcano, GATOR, and Flipper minefields only
** ADAM / RAAMS minefields only
*** See FM 20-32 for Safety Zones and use the longest distance as the
radius
Purpose
Reports the results of a route reconnaissance.
Instructions
Submitted at the initiation and conclusion of reconnaissance. Appropriate
portions of report submitted when obstructions encountered or changes to
route required. Utilize FBCB2 Free Text Message as primary means.
Battalions may submit using MCS or MSE. FM is least preferred method.
Individual platforms or platoons submit PL / PSG, CO Commander / XO /
CP.
Submit at least twelve hours prior to planned execution.
Format
"From" location.
"To" location.
Type of route, report using the following designations:
Highway, report using the no. "1."
Road, number "2."
Trail, number "3."
Cross-country, number "4."
Classification of route. Check for height, width, and weight restrictions to determine the
appropriate class, and report what vehicles the route is capable of handling using the following
designations:
All squadron / battalion vehicles (70 class minimum), report using the number "1."
Tracked vehicles only, number "2."
BFVs (or smaller) only (35 class restriction), number "3."
Seasonal limitations of route based on weather-support capability, report as follows:
All-weather (usable year-round), report using the letter "X."
Limited all-weather (use limited during bad weather), letter "Y."
Fair weather (may be impassable during bad weather), letter "Z."
Rate of movement the route will support, report as follows:
Fast, report using the number "1."
Slow, number "2."
Location and type of any critical points (send the applicable report). Report the following
obstructions in all cases: curves with a radius of forty-five meters or less; uphill slopes with
grades of 5% or greater; width restrictions of six meters or less for one-way traffic, ten meters or
less for two-way traffic; and overhead clearance of 4.3 meters or less.
Closure Report
Purpose
Reports unit movement status and capability of units to conduct future
operations.
Instructions
Submit using FBCB2 Free Text message as primary with FM as alternate;
battalions may submit closure reports using MCS or MSE as alternate.
Submit report to TF / BDE Main with info addresses TF / BDE TAC, BDE
ALOC, BDE CDR / CSM / S3. Garrison reports may be submitted by
telephone.
Submit initial report via FM including Unit and CP location upon closure of
TOC. Submit final report upon completion of movement of the main body,
or at a designated time, to the TF / BDE MAIN CP (field) or brigade
SDNCO (garrison). The closure report is a status report and units need not
be 100% to submit. A final report, however, is required once the unit is
100% complete (NLT arrival + two hours). For prolonged or complex
movements (combination of transport modes), submit report every two hours
or as directed by brigade.
Format
Unit.
SP date / time.
RP date / time.
CP location (6-digit grid).
Closure date / time.
Accidents / incidents.
Estimated time unit ready to conduct operations.
Weapons / sensitive items inventory complete (YES / NO).
Bypass Report
Purpose
Reports an obstacle bypass route.
Instructions
Submitted immediately when obstacle bypass confirmed using FBCB2
BRIDGEREP. Utilize FBCB2 as primary means. FM is alternate method.
TF Engineer forward to BDE Engineer via FBCB2 or MCS; BDE Engineer
forward to DIV and higher / adjacent units using MCS (message and overlay
as appropriate).
Format
Observer or source.
Length; width; surface type; grade.
Coordinates of "from" / "to" locations.
Seasonal / weather limitations.
All-weather (usable year-round), reported using the letter "X."
Limited all-weather (use limited during bad weather), letter "Y."
Fair weather (may be impassable during bad weather), letter "Z."
Bypass markings.
Observer’s actions.
OBSTACLE-TURNOVER/TRANSFER REPORT
OBSTACLE DATA
Obstacle # Obstacle Type Emplacing Authority
TURNOVER DATA
Transferr ing Unit Receiving Unit Date/Time of Transfer
TURNOVER CHECKLIST
1. Intelligence.
a. Enemy activity forw ard of the obstacle (discuss enemy recon, breaching efforts, direction of movement, expected time)
b. Friendly activity in the vicinity of the obstacle (discuss LOGPAC, recon, counterrecon, maneuver)
c. Critical aspects of terrain in the vicinity of the obstacle
2. Maneuver.
a. Obstacle protection against enemy recon/breaching (discuss overw atch, counterrecon patrols, sunrise sw eep)
b. Location of TRPs and indirect fire targets (point out location on graphics and terrain)
c. Rearw ard/forw ard passage of lines (discuss planned and routine activity around the obstacle)
d. Familiarize w ith other friendly units adjacent to the obstacle
3. Mobility/Survivability.
a. Obstacle trace (discuss corner point grids on map and point out on terrain)
b. Obstacle marking (explain type of marking and on w hich sides of the obstacle)
c. Obstacle composition (location of disarming materials)
d. Location of lanes/gaps and method of closing lanes/gaps
e. Location of material to close lanes/gaps
f. Explain purpose and target of obstacle, reporting procedures, and authority for emplacement
4. CSS.
a. Planned casualty evacuation and supply routes in the vicinity of the obstacle
5. C2.
a. DA Form 1355 or 1355-1-R, dated __________, transferred to receiving unit
b. DA Form 2203, dated _________, trans ferred to receiving unit
b. Obstacle overlay, dated __________, transferred to receiving unit
c. Target folder, dated _________, transferred to receiving unit
d. Higher headquarters (transferring, receiving, and emplacing units) notified of transfer
e. DA Form 1355 or 1355-1-R forw arded
f. 2 Copies of this form, dated ________, given to receiving unit
RECEIVING UNIT REQUIREMENTS
_______ Emplace the obstacle _______ Overw atch the obstacle
_______ Complete the obstacle _______ Remove the markings
_______ Execute the obstacle _______ Close the Lanes
_______ Guard the obstacle _______ Report the Effect
The Authority to Execute this Obstacle is: ______________________________________________
You MA Y / MAY NOT Execute this Obstacle to Prevent Immediate Capture by the Enemy
CERTIFICATION
The undersigned certify that the receiving unit has assumed full responsibility for the obstacle indicated above. The unit
commander understands all the information related to the obstacle, the obstacle intent, and his responsibility to transfer of
recover the obstacle upon his departure.
_______________________________________ _________________________________________
Signature of Transferring Unit Commander/Date Signature of Receiving Unit Commander/Date
_______________________________________ _________________________________________
Printed Name and Rank Printed Name and Rank
Purpose
Report discovered unexploded ordnance.
Instructions
Report by the fastest means available to next higher HQs. Ensure TF / BDE
Main is notified.
Format
DTG
Reporting unit and location
How unit can be contacted (FM frequency / call sign or phone number)
Type munitions and how it appears to have been delivered (dropped, placed,
projected, etc.)
NBC contamination
Resources threatened
Impact on mission
Protective measures taken; how UXO marked
Priority (immediate, minor, no threat)
Intelligence Reports
Purpose
Maintain status of accountability for unit sensitive items.
Instructions
Platoons submit to company CP NLT 0530 and 1730, or upon sensitive item
being unaccounted for. Companies / separate platoons report to TF NLT
0600 and 1800; TF to BDE NLT 0630 and 1830. Routine report submitted
by FBCB2, MCS, MSE or FM. Report of unaccounted item submitted
immediately by fastest means available. Reports submitted to BDE Main.
Format
Report should read "GREEN for sensitive items" if all weapons and sensitive items
are accounted for.
Submit report immediately, in following format, if there are sensitive items
unaccounted for during daily checks, or at any time an item is lost or stolen.
DTG of loss / theft.
Unit reporting loss / theft.
Type of sensitive item lost / stolen, including serial number.
Name / Rank / SSN of individual(s) involved in incident.
Synopsis of events surrounding the loss / theft.
Report Number
B005 (USMTF # C104)
Instructions
Use to provide a timely and accurate estimate of damage resulting from the
application of military force, either lethal or non-lethal, against a
predetermined objective. Reference: FM 9-43-1.
Format
LINE 1 – DATE AND TIME (DTG)
LINE 2 – UNIT (Unit Making Report)
LINE 3 – NAME (Target or Installation Name)
LINE 4 − COUNTRY CODE (2-Letter Country Code)
LINE 5 − LINE BEN (Basic Encyclopedia Number, NA or UNKNOWN)
LINE 6 − LOCATION (UTM or 6-Digit Grid Coordinate with MGRS Grid Zone Designator)
LINE 7 − TM REF (Target Material Reference)
LINE 8 − PAGE NO. (Page or Sheet Number)
LINE 9 − COLLECTION DATE / TIME (IMINT Collection DTG)
LINE 10 − TYPE (Type of IMINT)
LINE 11 − QUALITY (Image Quality; GOOD / FAIR / POOR)
LINE 12 − ANGLE (Viewing Angle – Vertical or Oblique)
LINE 13 − TOT (Time-Over-Target for Attack DTG)
LINE 14 − DELIVERY SYSTEM (Number and Type of Delivery System)
LINE 15 − WEAPONS (Number and Type of Weapons and Fusing)
LINE 16 − AIM POINT NAME (Name or Description of Target Element)
LINE 17 − LOCATION (UTM or 6-Digit Grid Coordinate with MGRS Grid Zone Designator)
**Repeat lines 1 through 17 for multiple missions or sets of mission data. Assign sequential
lines to succeeding iterations; for example, first iteration 13 through 17; second iteration 13a
through 17a; third iteration 13b through 17b; and so on.
LINE 18 − BDA ANALYSIS (Narrative of Target Damage and Munitions Effects to Include:
Element Name, Grid Reference, Physical Damage, Confidence Level, and Whether Re-attack is
Required)
LINE 19 – NARRATIVE (Free Text for Additional Information Required for Clarification of
Report)
Report Number
D020 (USMTF # C070)
Instructions
Use to provide commander of incidents where the unit has detained civilian
personnel. Send report IAW unit SOPs.
Reference: FM 19-40.
Format
LINE 1 – DATE AND TIME (DTG)
LINE 2 – UNIT (Unit Making Report)
LINE 3 – NO. DETAINEES / NO. AWAITING RELEASE (Number of Personnel
Detained and Awaiting Release to Foreign Nation Authorities)
LINE 4 – LOCATION (UTM or 6-Digit Grid Coordinate with MGRS Grid Zone
Designator of Collection Point)
LINE 5 – REASON FOR DETENTION (Reason for Detaining Civilian Personnel)
LINE 6 – MEDICAL CONDITION (Report if Detained Persons Require Any
Emergency Medical Treatment)
LINE 7 – POC (POC of Foreign Nation Support)
LINE 8 – PM ASSESSMENT (PM Assessment)
LINE 9 – NARRATIVE (Free Text for Additional Information Required for
Clarification of Report)
LINE 10 – AUTHENTICATION (Report Authentication)
R&S Report
Line 1 - Unit:
Line 2 - R & S Asset (Patrols, Sensors, Ops, etc) (Include size of patrols):
Line 5 - Start time (DTG) of asset activity (Include time of departure for patrols and time
surveillance Started):
Line 6 - Stop time (DTG) of asset activity (Include time of return for patrols and time
surveillance ceased):
Weather Forecast
Line 2 -
Valid period (DTG):
Narrative (24 hour forecast):
Line 3 -
Valid period (DTG):
Narrative (24-48 hour forecast):
Weather Advisory
Purpose
To request information from higher, adjacent or subordinate units to resolve
intelligence gaps.
Instructions
Submit to action addressee via digital system if possible, with MSE or FM as
alternate means.
Format
DTG of request.
Unit requesting information.
Information requested.
Response NLT DTG.
Instructions
Submit to requester via digital system if possible, with MSE or FM as
alternate means.
Format
DTG of response.
Unit answering RFI.
Response to RFI.
DTG of further explanation, if applicable.
Distribution
The TFS2 section will send the INTSUM at 0600 and 1800, two hours
prior to an LD or Defend NLT time, and as the situation requires.
The S2 section will send written and graphic INTSUMS via ASAS to
FBCB2. The section will notify the units once complete.
FM updates will be on the TF CMD net.
Graphic INTSUM: One page picture with brief situation description, analysis
and assessment.
Patrol Report
Purpose
To provide a guide for debriefing dismounted patrols and reporting patrol
results to higher HQs.
Instructions
If submitted to higher headquarters, utilize MCS, ASAS, or FBCB2 free text
formats summarizing information if appropriate. Utilize MSE or FM as
alternate means.
Format
Designation of patrol. Include “To,” “From,” and “Maps
Size and composition of patrol.
Task.
Time of departure.
Time of return.
Routes (out and back).
Terrain. This includes a description of terrain by type, depth of ravines and draws, condition of
bridges, and effect of terrain on tracked and wheeled vehicles.
Enemy. This includes details of enemy strength, disposition (including any shifts in
disposition), defenses, equipment, weapons, attitude, morale, exact location, and movements.
The report should include the time enemy activity was observed and coordinates of the location
where activity occurred.
Any map corrections.
Miscellaneous information, including pertinent details of NBC warfare.
Results of encounters with the enemy. This includes enemy prisoners and casualties, captured
documents and equipment, identification of enemy elements, and enemy disposition after the
contact.
Condition of the patrol, including disposition arrangements for any dead or wounded.
Conclusions and recommendations, including the extent to which the mission was accomplished
and any recommendations as to patrol equipment and tactics.
Additional remarks by the debriefer.
Note. The report should conclude with the name, rank / grade, and
organization / unit of the patrol leader.
Purpose
Reports possible enemy disruption of communications or imitative deception
communications.
Instructions
Submit ASAP following capture, prior to evacuation. Primary means is
FBCB2 Free Text message with FM as alternate. Platforms / platoons
submit report to chain of command to CO Commander / XO / 1SG / CP.
Companies report to next higher; addressees are TF / BDE S2 with
information to TF / BDE Main, TAC, Rear CPs and BDE MP PLT for EPW
RPT.
Format
For EPW
State "GREEN 6."
Item captured (state "EPW").
DTG of capture ("260845SEP83").
Place of capture, using grid coordinates ("NS 621434").
Capturing unit (appropriate call sign).
Circumstances of capture, described as briefly as possible.
For Captured Equipment
State "GREEN 6."
Item captured ("MATERIAL").
Type of document or equipment ("ANCD").
DTG of capture ("160900JUN02").
Place of capture, using grid coordinates ("NE 824615").
Capturing unit (appropriate call sign).
Circumstances of capture, described as briefly as possible.
SAEDA Report
Purpose
Reports attempts by individuals to obtain classified information, conduct
espionage and / or subvert US forces, their friends or family.
Instructions
Submit ASAP to TF / BDE S2 and unit leaders via digital system if possible,
with MSE or FM as alternate means.
Format
DTG of incident
Location of incident
Persons involved, including witnesses and other sources and suspects
Narrative of incident
Actions taken by personnel involved
Comments
Debrief Format
Line-Format-Example
Patrol Identification: (2/B/1-187 Patrol 2)
DTG of Report: (27 0430R JUL 95)
Maps Used: 1:50,000 FTCKYMIM
LINE A Size and Composition of Team
Ex: 6; 3/2/B/1-187 IN
LINE B Mission
Ex: At 0100 2/B/2-14 IN conducts a squad sized security patrol to DR345876 to prevent enemy
infiltration.
LINE C Specific Information Requirements (SIR)
Ex: Any enemy activity.
LINE D Reporting Requirements
Ex: Any enemy activity.
LINE E Time of Departure (DTG)
Ex: 271255R JUL 95
Method of Infiltration
Ex: Foot
Point of Departure (Grid)
Ex: DR321654
LINE F Enemy Spotted En-route
Ex: None
1. Ground Activity
2. Air Activity
3. Miscellaneous Activity
LINE G Routes (Out)
Ex: 1 - DR321654, DR345875
1. Dismounted
2. By-Aircraft
3. By-Vehicle
LINE H Terrain
Ex: Key terrain - Hilltop 651 controls road. Key Terrain, Compartmented Terrain intersection.
Significant Terrain, Terrain Corridors & Map corrections: Road from DR4567 DR45779 (not on
map).
LINE I Enemy Forces and Installations
Ex: 2-man sniper team at DR326687 @ 0145.
LINE J Miscellaneous Information
1. Lack of animals/Strange animal behavior
2. Mutilated Plants
3. Strange, uncommon Insects
4. Abandoned Military Equipment
(a) out of fuel
(b) unserviceable
(c) destroyed / damaged
Ex: 4c. 2 x BTR-60s with wheels blown off
(d) intact
Ex: 4d. 1 x T-80 hidden in brush DR645987
5. Abandoned Towns / Villages
LINE K Results of Encounters with Enemy Force and Local Populace
Ex: 2 enemy KIA; a local from Drumville stated the enemy was foraging for food and using
local water supply.
LINE L Condition of Team (Include Disposition of Dead and Wounded)
Ex: One soldier shot in left arm, currently stable at the battalion aid station.
LINE M Any maps or other identifiable equipment lost on patrol and estimated location.
Ex: PLGR with “2/b/1-187 IN label was lost vic. DR154784.
LINE N Conclusions and Recommendations
Ex: Small units are probing perimeter.
LINE O Captured Enemy Equipment and Material Ex: 1 x SVD, 1 x AK-74.
LINE P Time of Extraction (DTG)
Ex: 27 0245R JUL 95
Method of Exfiltration
Ex: Foot
LINE Q Routes (Back)
Ex: 1. DR347873 to DR321655
LINE R Enemy Spotted during the Return
1. Ground Activity
Ex: N of DR128764
Air Activity
Ex: U/I Helicopter passed 1km
3. Miscellaneous Activity
Ex: 10 minute firefight heard at 032 degrees magnetic from DR127763 at 0245.
LINE S Time of Return (DTG)
Ex: 27 0345R JUL 95
Point of Return (Grid)
Ex: DR321655
Team Leader Name and Rank
Ex: SSG Prussia
Personnel Reports
Purpose
Reports personnel status to higher headquarters and provides a tool for
requisitioning new personnel.
Instructions
Companies and lower submit using FBCB2 PERSTAT with FM as alternate,
with addressees including TF / BDE Rear and TF / BDE S1. Platoons report
to CO 1SG / XO / Commander / CP NLT 1200 and 2400 daily. 1SG
forwards company report to TF S1 NLT 1230 and 0030 daily. TF submits to
BDE NLT 0200 and 1400 daily. Attachments, DS and OPCON units report
though the unit being supported or attached to.
Battalions submit via FBCB2 PERSTAT, MCS or MSE.
Analog Format
Submitted By Line In Slant Format By Officer / Warrant / Enlisted
Line –Item-Example
1UNIT / DTG
2PERSONNEL ASSIGNED Ex: (5/0/86)
3PERSONNEL ATTACHED Ex: (0/0/7)
4PERSONNEL DETACHED Ex: (0/0/4)
5TOTAL PERSONNEL Ex: (5/0/89)
6TOTAL PERSONNEL PRESENT FOR DUTY
Ex: (5/0/75)
7WOUNDED IN ACTION
8KILLED IN ACTION
9MISSING IN ACTION
10PERSONNEL ON LEAVE/PASS Ex: (0/0/2)
11PERSONNEL TDY
12PRSONNEL AWOL
13PERSONNEL ON REAR DETACHMENT
Ex: (0/0/12)
14PERSONNEL REPLACEMENTS REQUIRED
(RANK / SPECIALTY / QUANTITY)
The initial unit roster is created from the bottom up with each platform in
putting the personnel data for the soldiers associated with that system. The
PERSTAT is then rolled up at platoon and company and sent as a company
roll-up to the BDE CSSCS for action with an info copy to the BN CSSCS (if
equipped). The BN PERSTAT report is then sent back down to each
platform so that changes in personnel status can be tracked and reported back
up the chain. When changes are reported, the system only reports on changes
to records in the database from the last time a personnel status report was
sent. Default addressees are not provided with this message.
The PERSTAT build and CTIL receipt are sent immediately following a
UTO change. In the ideal scenario, the UTO is transmitted as part of pre-
deployment operations order. After commanders have reported 100 %
acceptance of the UTO, the CTIL action message can be sent and accepted
and the PERSTAT can be built. These tasks can then be checked as part of
PCC / PCIs.
KI A
WI A
MI A
G. TOTAL LOSSES
H. REMARKS______________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
________________________________________________________
Casualty Report
Purpose
Reports personnel status to higher headquarters and provides a tool for
requisitioning new personnel.
Instructions
Companies and lower submit using FBCB2 Free Text message with FM as
alternate, with addressees including BDE ALOC and BDE S1 with BDE
Main / TAC as info addressees. Battalions submit via FBCB2 or MCS with
MSE or FM as alternate means. Submit ASAP.
Format
A. Battle roster number.
B. DTG of the incident.
C. Location of the incident (encoded).
D. Type of casualties, encoded by letter as follows:
ALPHA: KIA, hostile action.
BRAVO: KIA, non-hostile action.
CHARLIE: Body recovered.
DELTA: Body not recovered.
ECHO: Body identified.
FOXTROT: Body not identified.
GOLF: MIA.
HOTEL: Captured.
INDIA: WIA, slight, hostile action.
JULIET: WIA, serious, hostile action.
KILO: WIA, slight, non-hostile action.
LIMA: WIA, serious, non-hostile action.
MIKE: Accident.
Status of evacuation and location to which casualties are evacuated.
MEDEVAC Request
Purpose
Requests immediate evacuation of casualties.
Instructions
Submitted by the fastest means available. Requests for urgent casualties
should always be initiated on FM to get the most rapid response, followed by
a digital request. Routine evacuation request may be sent via FBCB2
MEDEVAC message, but should be accompanied by an FM alert to the
primary addressee.
Format
1. Location of pickup site (grid coordinates)
2. Radio Frequency (your call sign and suffix)
3. Number of patients by precedence:
A –Urgent (save life, limb, eyesight within two hours)
B –Urgent -Surgical (surgery required to save life and stabilize)
C – Priority (required medical care is not available, will deteriorate to Urgent if not evacuated
within four hours)
D – Routine (sick and wounded who require evacuation within twenty-four hours)
E – Convenience
4. Special equipment required
A – none
B – hoist
C – extraction
D – ventilator
5. Number of patients by type L + # patients – Litter
A + # patients – Ambulatory
6. Security of pick up site
N – no enemy troops in area
P – possible enemy troops
E – enemy troops in area, approach with caution
X – enemy troops in area, armed escort required
7. Method of marking pickup site (LZ)
A – panels
B – pyrotechnic signal
C – smoke signal
D – none
E – other
8. Patients nationality and status (military / civilian)
A – US military
B – US civilian
C – Non-US military
D – Non-US civilian
E – EPW
9. NBC contamination
N – Nuclear
B – Biological
C – Chemical
U – Unknown
A – All Clear
**When air / ground communications are established, the pilot will require
the following information from the ground (LZ): Size of LZ, obstacles
(wire, antennas, ditch, vehicles), wind direction and velocity and the slope of
the terrain.
Prior to utilizing the combat MEDEVAC, users must enter the Radio
Frequency and Call Sign for their platform in the “Admin>Platform
Settings>Misc” dialog box on the BCOPS screen. This will allow the
software to automatically fill the information in the message. Users cannot
enter this information directly into this form. Both fields require more
characters than Army call signs / frequencies have, so use zeros to fill them
completely.
Select the MEDEVAC report from the Combat Messages Box using the
MEDEVAC tab. Fill in the fields using the drop down menus. Type in the
pickup location or use the map or LRF fill options. Ensure that the Radio
Frequency and Call Sign are showing.
Purpose
To report medical status, medical trends, and patients treated.
Instructions
Medical platoons and FSC Medical Company submit daily at 2300 using
FBCB2 Medical SITREP (See below) format. Data is from 0100 to 2300.
Submit to BDE Surgeon and FSB Area Treatment Team, with TF / BDE
Rear and FSC / FSB SPO as info addressees. BDE Surgeon compiles data
and submits to DIV Surgeon NLT 2400.
Analog Format
DTG:
FROM:
LINE 1: VEHICLE STATUS:
TYPE-O/H-FMC-NMCA. M997
B. M113
C. M923
D. M1068/M557
E. M998
LINE 2: CLASS VIII CRITICAL SHORTAGES:
NOMENCLATURE-REQ-O/H
LINE 3: CRITICAL SHORT MED PERSONNEL STATUS:QUANTITY-MOSLINE 4: DNBI
INFORMATION:
A. MEDICAL TRENDS, CONCERNS, POTENTIAL THREATS
B. REAL WORLD PATIENTS (LAST 24 HOURS):
TOTAL SEEN:
RTD
EVAC
C. REAL WORLD PATIENTS (LAST 24 HOURS):
TOTAL SEEN:
RTD
EVAC
LINE 5: CASUALTIES (LAST 24 HOURS)
A. EVAC BY AIR
B. EVAC BY GROUND
C. DOW
D. RTDE. TOTAL ______LINE 6: CASUALTIES (TOTAL)
F. EVAC BY AIR.
G. EVAC BY GROUND
H. DOW
I. RTD
J. TOTAL ______
Logistics Reports
Purpose
Reports logistical status and requirements forecast.
Instructions
Report is initiated starting at platform level, and rolled up at platoon and
company level. Platform sends to PL / PSG; PSG consolidates and sends to
1SG / Commander daily by 0700. 1SG consolidates and sends company
report to TF Rear (S4), Main CPs, FSC SPO, and the brigade S4 and FSB
SPO CSSCS box NLT 0800. (CSSCS will only receive the LOGSTAT from
the 1SG, Commander, XO, or Company CP FBCB2.)
LOGSTAT reports initiate at the platform level, with the flow of the reports
from the platform to the PSG, who consolidates the platoon’s reports and
forwards a single report to the 1SG. The 1SG consolidates the company’s
reports and forwards a single report to the BN S4, the FSC and the FSB
SPO. BN S4’s may roll up the reports to a single BN report for his use or as
required by the Commander / staff, but the individual company reports must
be sent to the FSB SPO CSSCS in order to track units at the lowest possible
level.
Before consolidating (roll-up) reports, check the FIPR queue to see if the
right number of reports has been received.
Save the message before sending; a warning will be given if this is not done.
The best TTP for both the PERSTAT build and CTIL receipt is to schedule
these events right after the UTO has been sent and received. In the ideal
scenario, the UTO is transmitted as part of pre-deployment operations order
(i.e., the week before training). Later that day, after commanders have
reported 100% acceptance of the UTO, the CTIL action message can be sent
and accepted and the PERSTAT can be built. These tasks are checked as part
of PCC / PCIs.
The Battle Loss Report outlines critical equipment that is rendered non-
mission capable.
1. LIN #
2. UNIT
3. LOCATION OF LOSS
4. NOMENCLATURE
5. QUANTITY
6. REASON FOR LOSS
7. REPORTING UNIT
CONTROL #
8. BDE CONTROL #
9. DMMC DOC #
Purpose
Reports status or request ammunition.
Instructions
These reports are primarily used internally at task force and below, but may
be used by platoon and company elements such as the BRT operating
directly under TF / BDE control.
Format
AMMO Status
1. GREEN: 90% or more on hand, all ammunition types.
2. AMBER: 80% to 89% on hand, all ammunition types.
3. RED: 60% to 79% on hand, all ammunition types.
4. BLACK: 59% or less on hand, all ammunition types.
AMMO Request
The FBCB2 SITREP can be used to report ammo status and request, but only
one type of ammo can be entered in the message field per message.
Additional shortages / requests can be added in the comments field. At TF
level and lower, critical ammo shortages will be reported and requested
using FM as primary method. If requesting via FM, provide the ammunition
type / nomenclature / DODAC or line number and number of rounds
required.
Purpose
Report status or request ammunition.
Instructions
These reports are primarily used internally at task force and below, but may
be used by platoon and company elements such as the BRT operating
directly under TF / BDE control.
Format
POL Status
1. GREEN: 90% or more on hand, all ammunition types.
2. AMBER: 80% to 89% on hand, all ammunition types.
3. RED: 60% to 79% on hand, all ammunition types.
4. BLACK: 59% or less on hand, all ammunition types.
POL Request
The FBCB2 SITREP can be used to report POL status and request. At TF level and
lower, critical POL shortages will be reported and requested using FM as primary
method. Provide POL item description or line number and quantity required.
REFERENCES
FM 3-0, Operations
FM 5-0 (101-5), Army Planning and Orders Production
FM 6-0, Mission Command: Command and Control of Army Forces
FM 17-95, Cavalry Operations
FM 34-8, Combat Commander’s Handbook on Intelligence
FM 34-2, Collection Management and Synchronization Planning
FM 34-2-1, Tactics, Techniques, and Procedures for Reconnaissance and
Surveillance and Intelligence Support to Counter-reconnaissance
ST 3-90.23, Mechanized Infantry and Armor Battalion Task Force Tactical
SOP
FM 101-5-2, U. S. Army Reports and Message Formats
Commander’s Battle Staff Handbook, ARI Research Product
Battle Command Training Program, C-Team Workshops
Selected Unit TACSOPs