INT-03 — Lesson 2 of 5
SPOT and SALT: Speed-Priority Formats
When the decision window is seconds, not minutes
The Speed-Priority Problem
Why Short Forms Exist
A SALUTE report, completed to the standards taught in Lesson 1, takes between 30 seconds and two minutes to transmit depending on the detail available and the communications method. In most situations, that is acceptable. But consider: you are on a mobile patrol and spot an armed group 200 meters ahead before they see you. You have approximately 10 seconds before you need to either take cover or change direction. You cannot complete a SALUTE. You have one radio transmission window before your movement priority takes over. What do you send?
The answer is whatever gets the essential information to the receiving element before the window closes. SPOT and SALT exist to define what “essential” means so that an observer under extreme time pressure does not have to decide in the moment. The format makes that decision in advance: report these four things, in this order, and the receiving element can act on it.
The tradeoff is information depth. A SPOT or SALT report is actionable but incomplete. The receiving element knows a threat exists, approximately where, and approximately what. They do not know Unit/Uniform or detailed Equipment. That is acceptable for an immediate reaction. It is not acceptable for planning or pattern analysis, which is why the short-form report is always followed by an upgraded SALUTE when the situation allows.
SPOT: Rapid Threat Observation
Size, Position, Observed Time, Type
SPOT is used in the most time-critical situations: when you are about to lose visibility, when the threat requires immediate counter-action, or when you are in a movement situation and can only pause briefly to transmit. It is sometimes called SPOTREP and is integrated directly with fire support requests and immediate reaction triggers.
S — Size
Same standard as SALUTE: number or bounded estimate. “Six personnel” or “approximately eight to ten.” Do not use vague descriptors.
P — Position
Note the field name: Position, not Location. In a SPOT report, position is reported using a bearing and distance from your current location or from a known reference point: “bearing 045 from OP Alpha, approximately 300 meters” or “bearing 270 from my current position, 150 meters.” This is faster to generate than a grid coordinate and is sufficient for an immediate action response. If you have a grid ready, use it. If not, bearing and distance is acceptable in SPOT.
O — Observed Time
The time at which you observed the threat. In a SPOT report, this is often the current time or seconds ago. Use local time or Zulu consistently. Example: “Observed 1032 local, still in position.”
T — Type
The nature of the threat. This field combines elements of the SALUTE Activity and Equipment fields into a single brief entry: “armed foot patrol moving north,” “vehicle-borne, one pickup with mounted weapon,” “individuals emplacing obstacles on road.” Include the primary threat indicator — armed, vehicle, blocking action — and direction of movement or activity. Keep it brief: this is a single sentence or phrase, not a full description.
SPOT Transmission — 0847 Local
S: Eight personnel, dismounted.
P: Bearing 310 from OP Bravo, approximately 400 meters, near tree line.
O: Observed 0845 local, still in position at time of transmission.
T: Armed foot element, moving west along field edge, two individuals carrying long guns, remainder unknown.
This transmission takes approximately 15 seconds to deliver verbally over radio. The receiving element now has sufficient information to dispatch a response element, alert other OPs, and begin tracking the contact.
SALT: The First-Pass Report
Size, Activity, Location, Time
SALT (Size, Activity, Location, Time) is the simplified initial report format. It is designed for two situations: when an observer has basic information and needs to get it into the reporting chain quickly even if incomplete, and when the report is a first-pass that will be expanded into a full SALUTE. SALT is simpler than SPOT in that it does not use the bearing-and-distance Position field — it uses a Location field with the same standards as SALUTE (grid, named point, or distance from reference). It omits Unit/Uniform and Equipment entirely as initial fields.
S — Size
Same standard as SALUTE and SPOT: precise count or bounded estimate. Never vague.
A — Activity
What you observed, stated as observable behavior. Same standard as the SALUTE Activity field: report what you see, not what you infer. “Moving east on foot” or “stationary, appearing to observe the road” or “searching parked vehicles.” Single sentence.
L — Location
Where the element is located. Grid reference, named point, or distance-and-bearing from a known reference. Same standard as SALUTE Location. If precise location is unavailable, give the best available with a confidence note.
T — Time
When you observed the activity. Precise timestamp, local or Zulu, consistent with your group’s standard. Note transmission delay if present.
SALT Transmission — 1312 Local
S: Five individuals on foot.
A: Moving north on the main road, passing through the intersection at slow walking pace.
L: Main road intersection, 300 meters south of OP Delta. Grid to follow in SALUTE upgrade.
T: Observed 1310 local, still in movement at time of transmission.
Note: This SALT report gets the contact into the log immediately. The observer then continues observation and transmits a full SALUTE within the next few minutes as more information becomes available (clothing, visible equipment, group behavior).
Choosing Between SPOT and SALT
Format Selection Logic
Both formats serve the same speed-priority function, but they differ in what information they prioritize. Use SPOT when: you are in a movement situation and cannot stop to observe fully; the threat is immediate and requires the fastest possible transmission; you need to integrate with a fire support request or immediate reaction protocol; the position of the threat relative to your position is the most critical piece of information.
Use SALT when: you have a basic observation with more than just position — you can describe what they are doing (Activity); you are at a fixed OP and can take a few seconds more; you are writing a quick first-pass that you know you will expand to a SALUTE; your communications environment makes the SALUTE Activity field more useful than the SPOT Type field for describing the threat.
In practice, many groups adopt one short-form format as their standard rather than both, to reduce cognitive load in the field. If your group has a standard, use it. If not, the guidance above gives you a principled basis for choosing.
SPOT and SALT, Field by Field
| SPOT | SALT | |
|---|---|---|
| Field 1 | Size | Size |
| Field 2 | Position — bearing and distance | Activity — observed behavior |
| Field 3 | Observed Time | Location — SALUTE standard |
| Field 4 | Type — behavior and threat indicator in one entry | Time |
| Use when | In movement, threat immediate, position relative to you most critical | Fixed OP, a few seconds more, first pass before a SALUTE |
Both short forms carry four fields for speed — pick by whether relative position or observed activity matters most, then upgrade to SALUTE.
Upgrading a Short-Form Report to SALUTE
The Upgrade Procedure
A SPOT or SALT is always a temporary report. Once the situation allows — you have reached cover, the element has stabilized, communications are open — you transmit the full SALUTE using the same contact reference (time and location from your initial report). The upgrade adds the Unit/Uniform, Equipment, and any additional Activity and Location detail that was not available for the initial transmission.
When transmitting the upgrade, identify it explicitly: “SALUTE upgrade to SPOT reported at 0847.” This allows the receiving element to link the full report to the initial sighting rather than logging it as a new contact. Without that linkage, you may generate duplicate contact entries and confuse the operating picture.
Set a timer for 15 seconds. Read the following scenario and transmit a verbal SPOT report before the timer expires. Scenario: You are at OP Bravo and observe three individuals on foot appear from the tree line 250 meters north of your position bearing 015. They are moving toward the road. At least one appears to carry a long weapon. Time is 1418 local.
After your timed attempt, write out your SPOT and evaluate it against the field standards in this lesson. If any field was missing or vague, note what prevented you from completing it and adjust for the next attempt.
The same 1310 contact, filed two different ways depending on which fields the observer has ready:
SPOT Report — 1310 Local
| Field | Entry |
|---|---|
| Size | 8 individuals |
| Position | Bearing 045, 300 meters from OP Alpha |
| Time | 1310 local |
| Type | Armed, moving north on foot |
SALT Report — 1310 Local
| Field | Entry |
|---|---|
| Size | 8 individuals |
| Activity | Moving north, weapons visible |
| Location | Bearing 045, 300 meters from OP Alpha |
| Time | 1310 local |
Same event, same four data points, organized two different ways. SPOT compresses behavior and threat indicator into one Type entry; SALT keeps them as separate Activity and Location fields. Either is correct here — the choice comes down to which structure the observer already has memorized under pressure.
Scenario: your team is on a road overwatch. A group of five appears at the tree line 200 meters north, moving toward your position at a fast walk. You are about to lose visibility behind a rise in the terrain. You have 90 seconds before that happens. Draft a complete SPOT report — Size, Position, Time, Type — before the timer runs out. This is not graded; it is a rehearsal for producing a report under the exact kind of pressure SPOT is built for.
Lesson 2 Checkpoints
- SPOT and SALT are not inferior alternatives to SALUTE — they are the correct format when time does not allow complete observation
- SPOT uses Position (bearing and distance) rather than Location (grid/named point) because bearing-distance is faster to generate under extreme time pressure
- SALT uses the same Location field standard as SALUTE and is the preferred first-pass format when you have slightly more than SPOT’s 10-second window
- SPOT’s Type field compresses SALUTE’s Activity and Equipment into a single brief statement — report what you see, not a threat level label
- Every SPOT or SALT must be upgraded to a full SALUTE as soon as the situation allows — the short-form report is temporary, not a final entry
- When transmitting a SALUTE upgrade, explicitly reference the initial SPOT or SALT by time and location to link them in the contact log
Free tool · practise it
Practise SALUTE, SPOT and SALT in the free Ready Messenger: a form for each, with a hint on every line. See Field Report Formats.
| Complete this lesson’s Knowledge Check to continue |
| ← INT-03-01 — SALUTE: The Full Threat Report | Course Map |
Fortune Favors the Prepared · Semper Paratus, Semper Gumby · fortunefavorstheprepared.com