INT-03 — Lesson 3 of 5
SITREP: The Situation Report
Periodic status reporting, standard line items, and aggregating your intelligence picture
What a SITREP Is and Is Not
Purpose and Scope
SALUTE, SPOT, and SALT reports are event-driven: something happens, you report it. The report represents a discrete observed event and it goes into the log as a contact entry. A SITREP is time-driven: it is transmitted at scheduled intervals (every four, six, or twelve hours depending on your SOP) or at command request, and it represents the status of your element over a period, not a single event.
The SITREP serves four functions in a reporting chain. First, it provides command with positive confirmation that your element is operational — a SITREP received on schedule is a status check that does not require additional communication. Second, it summarizes the intelligence picture for the reporting period, referencing sighting reports so command can see the pattern without reprocessing every individual report. Third, it reports your element’s resource and personnel status so command can plan resupply and reinforcement. Fourth, it surfaces requests — for additional personnel, supplies, guidance, or communications support — in a structured format that command can respond to.
A SITREP is longer than a SALUTE but it is not a narrative. It follows a line-item format and every line should be as brief as the information allows. “Enemy: two contacts reported this period — see SALUTE reports filed at 0842 and 1317. No activity since 1317.” That is a complete Enemy line. You do not restate the full SALUTE content inside the SITREP.
Event-Driven vs. Time-Driven Reports
|
SALUTE, SPOT, SALT
Event-driven: something happens, you report it. One discrete observed event, logged as a contact entry. |
SITREP
Time-driven: sent at scheduled intervals or at command request. The status of your element over a period — references the sighting reports rather than restating them. |
Sighting reports go out the moment something happens; the SITREP goes out on schedule and points back to them — it never replaces them.
Standard SITREP Line Items
The Reporting Template
Line 1: DTG
Date-Time Group. The time the SITREP is submitted. Format: Day-Hour-Minute-Timezone-Month-Year. Example: 221430ZJUN26 (22nd day, 1430 Zulu, June 2026). If your group uses local time: 221430LJUN26. The DTG anchors the SITREP in the timeline. Do not omit it.
Line 2: As Of
The time the information in this SITREP is current as of. Often the same as DTG or slightly earlier. If conditions changed significantly between your last observation and when you wrote the report, note the difference. “AS OF: 221415L” when your DTG is 221430L means you are accounting for a 15-minute write time.
Line 3: Unit / Element
Reporting element identification. Your team designation, OP name, or patrol identifier. “Patrol Team Bravo,” “OP Alpha,” “Security Team 2.” This allows the receiving element to file and track the SITREP correctly without ambiguity about which element is reporting.
Line 4: Activity
What your element has been doing during the reporting period. Summarize operations conducted: “Maintained static OP on north road corridor from 0600 to 1400. Conducted one foot patrol of eastern perimeter at 0930, returned 1015. No incidents during patrol.” This is your element’s operational summary, not a threat report.
Line 5: Enemy / Threat
Summary of threat activity observed during the reporting period. Reference SALUTE/SPOT/SALT reports by time for detail rather than restating them: “Two contacts during this period. SALUTE filed 0842 (armed foot element, seven personnel, northwest sector). SALUTE filed 1317 (vehicle-borne, three personnel, main road, moving south). No threat activity observed since 1317 as of report time.” If no activity was observed: “NEGATIVE enemy activity this period.”
Line 6: Friendly
Status of your own element and any coordination with adjacent friendly elements. Personnel present and accounted for, operational status, any coordination with other teams. “All four personnel present and operational. Coordinated with OP Bravo at 1100, they reported negative activity on their sector.”
Line 7: Logistics
Resource status using the ACE or LACE framework if your group uses it. At minimum: ammunition (if applicable), food and water, fuel, communications battery life. Use a simple status: GREEN (sufficient for 24+ hours), AMBER (8-24 hours remaining), RED (less than 8 hours or immediate resupply needed). “Ammo: GREEN. Water: AMBER, 8 hours remaining. Communications batteries: GREEN. No resupply needed this period.”
Line 8: Personnel / Casualties
Headcount and any casualties. “All four personnel accounted for, no casualties.” If there are injuries or absences, report status, disposition, and impact on operations. Maintain OPSEC on casualty names in transmitted reports if communications may be monitored.
Line 9: Remarks / Requests
Anything that does not fit the above lines, plus any requests to command. “Request relief team at 1800 — current team has been on station 14 hours. Recommend increased monitoring of northwest corridor based on contact pattern.” This is your opportunity to surface recommendations, anomalies, and requests in a format command can respond to.
SITREP — Patrol Team Bravo — 221400L
Line 1 DTG: 221400LJUN26
Line 2 As Of: 221350L
Line 3 Unit: Patrol Team Bravo
Line 4 Activity: Maintained static observation of south road corridor from 0600. Conducted one mounted patrol of sector perimeter at 0800, completed 0920 without incident. Returned to OP. Continuous static observation 0920 to 1350.
Line 5 Enemy: One contact this period. SALT filed 1112 — five individuals on foot, moving north on main road at intersection 300m south of OP. Upgraded to SALUTE at 1140 — civilian dress, no visible weapons, one individual had large backpack, no markings. Departed north, not seen since. No other activity.
Line 6 Friendly: Four personnel present, all operational. No coordination with adjacent elements this period. OP Bravo SITREP not yet received.
Line 7 Logistics: Water GREEN. Food GREEN. Comms batteries GREEN. Fuel for generator at 40 percent — request resupply within 48 hours.
Line 8 Personnel: All four present and accounted for. No casualties. One team member reporting minor foot injury from morning patrol, non-mission-impacting.
Line 9 Remarks: The group observed at 1112 matches general description of individuals reported by OP Delta last week. Recommend comparison against OP Delta log. Request guidance on whether to attempt contact if group returns. Generator fuel resupply needed by 24 June.
SITREP in Low-Resource Environments
Adapting for MAG and Community Security Operations
A full nine-line SITREP transmitted over voice radio is a two-to-three-minute transmission. In a high-noise or low-battery environment, that may not always be feasible. Your group’s SOP should establish a minimum SITREP — the abbreviated version transmitted when full transmission is not possible. A minimum SITREP contains: DTG, Unit, Enemy (with a reference to any filed reports), Personnel (headcount only), and a one-line Logistics status.
When communications are extremely limited (one-way transmissions, runner-based messaging, or written notes), use written SITREP format with the same line structure. A written SITREP on a half-page sheet, filed with the communications log, serves the same function as a transmitted report. The standard is structured information that can be read, logged, and acted on without a follow-up conversation. Paper copies work. The format is what matters.
SITREP schedule should be set by SOP at the start of operations, not ad hoc. A team that transmits when they feel like it provides no baseline for command to detect problems. A team that transmits at 0600, 1200, and 1800 every day provides a schedule against which missed transmissions are immediately detectable. Missed SITREPs are a signal, not just an administrative inconvenience.
A SITREP is not a substitute for immediate reporting. If you observe a significant threat during the reporting period, you file a SALUTE/SPOT/SALT report immediately and then reference it in your next scheduled SITREP. You do not hold threat intelligence until the next SITREP window. A SITREP that says “at 0342 we observed an armed group of fifteen individuals moving toward the main camp” is a failed reporting chain — that observation should have been in a SPOT report six hours earlier. SITREPs summarize; they do not substitute for immediate reports.
You are the team leader for OP Foxtrot. The current time is 1800L. Your team of three has been on station since 0600. During the day you filed one SALUTE at 1045 (four individuals in a vehicle, moving west on the county road, civilian appearance, no visible weapons). Water is running low — approximately four hours remaining. One team member has been complaining of headaches since noon, non-impacting. You need a relief team by 2000 or you will have to consolidate with OP Echo. You have not coordinated with adjacent elements today.
Write a complete nine-line SITREP for this situation. Use DTG format consistent with 1800L on today’s date. Compare your product against the example above before moving to Lesson 4.
A single periodic status report pulling together everything this lesson covers:
SITREP — DTG 1800 Local
| Field | Entry |
|---|---|
| As Of | 1745 local |
| Personnel | 4 of 4 present, no injuries |
| Observed | Two SALUTE reports filed today (0930, 1340); road junction quiet since the 1340 contact |
| Logistics | Water: RED (approx. 6 hours remaining) · Ammo: GREEN · Comms: GREEN |
| Threat Picture | Elevated — armed group of 8 in AO as of 1340, direction of travel unconfirmed since |
| Remarks | Request 4 liters of water per person delivered by 2200, or authority to relocate to cache point Bravo |
Notice the As Of line is earlier than the DTG — the team knows its own information is 15 minutes stale at transmission time, and says so. Notice also that the Logistics RED flag and the Remarks request are two separate lines working together: one states the problem’s severity, the other states exactly what should be done about it.
Lesson 3 Checkpoints
- SITREP is time-driven, not event-driven — it reports the state of your element over a period, not a discrete threat sighting
- SITREPs reference SALUTE/SPOT/SALT reports for threat detail rather than restating them — keep the Enemy line brief and point to the filed reports
- A SITREP does not substitute for immediate reporting — file SPOT/SALUTE first, reference it in the next SITREP
- Logistics status uses GREEN/AMBER/RED: 24+ hours, 8-24 hours, less than 8 hours or immediate need
- Missed SITREPs are a detectable signal — schedule must be set by SOP and maintained, because deviations from schedule are themselves informative
- Remarks must include actionable requests, not just problem flags — “Water RED, request resupply by 2200” is complete; “Water RED” without a request is not
- In low-resource environments, a minimum SITREP (DTG, Unit, Enemy summary, Personnel headcount, Logistics status) preserves the function of the report when full transmission is not possible
Free tool · practise it
Practise the 9-line SITREP in the free Ready Messenger, with a Now button for the date-time group. See Field Report Formats.
| Complete this lesson’s Knowledge Check to continue |
| ← INT-03-02 — SPOT and SALT: Speed-Priority Formats | Course Map |
Fortune Favors the Prepared · Semper Paratus, Semper Gumby · fortunefavorstheprepared.com