Training - Guerilla Fire Team Reports
In a guerrilla fire team context, timely and accurate reporting is critical for situational awareness, decision-making, and coordinating with other elements or leadership.
Reports like LACE and SALUTE are highly relevant, but additional report formats can enhance a guerrilla fire team’s effectiveness in irregular warfare.
Below is a breakdown of contextually relevant reports for guerrilla fire team scenarios, focusing on their purpose and application.
SALUTE Report (Size, Activity, Location, Unit, Time, Equipment)
- Purpose: Provides a standardized format to report enemy observations quickly and concisely.
- Contextual Relevance
- Used during reconnaissance or patrols to report enemy sightings (e.g., spotting an enemy patrol or convoy).
- Critical for ambushes or raids, allowing the team to assess enemy strength and prepare.
- Helps track enemy movements for intelligence gathering.
- Example Scenario: While on a recon patrol, the team observes an enemy squad setting up a checkpoint. They note: Size (8 soldiers), Activity (establishing roadblock), Location (grid 123456), Unit (unknown militia), Time (1400 hrs), Equipment (small arms, one light vehicle).
- Why It Matters: SALUTE reports enable rapid dissemination of enemy intelligence to plan attacks, avoid detection, or request support.
LACE Report (Liquid, Ammunition, Casualties, Equipment)
- Purpose: Assesses the team’s status after an engagement or during extended operations to report resource levels and operational capability.
- Contextual Relevance
- Used post-contact (e.g., after an ambush or react-to-contact) to evaluate the team’s ability to continue the mission.
- Critical in resource-scarce guerrilla operations to manage limited supplies like water, ammo, and medical gear.
- Helps leadership decide whether to resupply, withdraw, or press the attack.
- Example Scenario: After breaking contact with an enemy patrol, the team reports: Liquid (50% water remaining), Ammunition (60% remaining, 2 magazines per member), Casualties (1 minor injury), Equipment (all radios functional, one NVG damaged).
- Why It Matters: LACE ensures the team remains combat-effective and informs resupply or exfiltration needs.
SITREP (Situation Report)
- Purpose: Provides a general update on the team’s status, mission progress, and situational context.
- Contextual Relevance
- Used during patrols, after significant events, or at regular intervals to keep higher command informed.
- Includes friendly status, enemy activity, terrain, and mission updates.
- Essential for coordinating with other guerrilla units or support networks.
- Example Scenario: During a multi-day patrol, the team sends a SITREP: “Team Alpha at grid 789123, moving to objective Bravo, no enemy contact, low water, morale high, ETA 1800 hrs.”
- Why It Matters: SITREPs maintain situational awareness across dispersed guerrilla elements, especially when operating independently.
SPOT Report (Similar to SALUTE, but more immediate)
- Purpose: A quick, simplified report for urgent enemy observations, often a precursor to a full SALUTE report.
- Contextual Relevance
- Used in fast-moving situations, like spotting an enemy patrol approaching the team’s position.
- Focuses on immediate threats to trigger rapid decisions (e.g., evade, engage, or report).
- Example Scenario: The team spots an enemy drone overhead and sends a SPOT report: “Enemy drone, grid 456789, heading north, 1500 hrs.”
- Why It Matters: SPOT reports enable quick reactions to immediate threats, critical for guerrilla teams avoiding detection.
CASEVAC/MEDEVAC Request (Casualty Evacuation/Medical Evacuation)
- Purpose: Reports casualties and requests evacuation or medical support.
- Contextual Relevance
- Used when a team member is injured or killed, especially in remote areas with limited medical resources.
- Includes casualty status, location, and urgency to coordinate evacuation or self-aid.
- Example Scenario: After an ambush, a team member is shot. The team sends: “CASEVAC request, grid 321654, one GSW to leg, stable, need extraction ASAP.”
- Why It Matters: Guerrilla teams often lack immediate medical support, so clear CASEVAC requests can save lives.
ACE Report (Ammunition, Casualties, Equipment)
- Purpose: A simplified version of LACE, focusing on combat-critical resources post-engagement.
- Contextual Relevance
- Used immediately after contact to assess combat readiness for follow-on actions (e.g., pursue, withdraw, or hold position).
- Common in small-unit engagements where water (Liquid) is less urgent than ammo and equipment status.
- Example Scenario: Post-ambush, the team reports: Ammunition (3 mags per member), Casualties (none), Equipment (one radio battery low).
- Why It Matters: ACE reports ensure the team can continue fighting or identify critical shortages.
GOTWA Report (Going, Others, Time, What, Actions)
- Purpose: Used when a leader or team member leaves the group temporarily, outlining their plan to ensure continuity.
- Contextual Relevance
- Common during reconnaissance or when splitting the team (e.g., sending a buddy team to scout).
- Includes where they’re going, who’s with them, time away, what to do if they don’t return, and actions in case of contact.
- Example Scenario: A team leader scouts a cache site: “Going to grid 987654, taking one member, back in 2 hours, if not back by 1800 move to rally point Delta, if attacked, break contact north.”
- Why It Matters: GOTWA ensures the team remains coordinated and can react if the detached element is compromised.
CACHE Report
- Purpose: Details the location, contents, and status of supply caches.
- Contextual Relevance
- Essential for guerrilla teams relying on pre-positioned supplies (e.g., food, ammo, medical gear).
- Includes grid coordinates, contents, and security status (e.g., compromised or secure).
- Example Scenario: After establishing a cache, the team reports: “Cache at grid 654321, 200 rounds 5.56, 10 MREs, medical kit, concealed under rock pile.”
- Why It Matters: Caches are a lifeline for guerrilla operations, and accurate reporting ensures resupply reliability.
EPW Report (Enemy Prisoner of War)
- Purpose: Reports the capture and status of enemy prisoners.
- Contextual Relevance
- Used when capturing enemy personnel during raids or ambushes for intelligence or leverage.
- Includes prisoner condition, location, and intelligence gained.
- Example Scenario: After capturing an enemy scout, the team reports: “EPW at grid 123987, one male, uninjured, carrying maps, awaiting interrogation.”
- Why It Matters: Captured prisoners can provide valuable intelligence but also pose security risks for small teams.