Lesson Overview
A patrol's most valuable product is rarely a thing it carries back. It is the information it sends. A section that finds a missing person, reaches an isolated household after a storm, or meets the unexpected on an exercise has done only half its work until what it knows has reached the person who can act on it, accurately and in a usable form. Earlier lessons gave you the means of sending: communication discipline, voice procedure on the net, and silent field signals. This lesson gives you the shape of what you send, so that nothing vital is lost and the receiver can write it down and act.
The heart of the lesson is the standard report format. Under stress, soldiers forget things, run their words together, and leave out the awkward fact. A known structure guards against all three by asking for each piece of information in a fixed order that sender and receiver have both learned. You will meet the situation report, the contact report, the sighting or information report, and the casualty report, along with the everyday craft of sending grid references, numbers, dates, and times clearly, and of confirming and logging what passes. You will also learn how the Army fixes a moment in time without ambiguity: the 24-hour clock, the date-time group, and the single-letter time zones that let units in different places work to one clock. Remember the character of this Army throughout: on Royal Kaharagian Army operations the commonest urgent reports are a found or missing person and a casualty, not an enemy. By the end you will be able to: state the principles of a good service message and separate fact from opinion; explain why standard report formats matter; send a situation report, a contact report, a sighting report, and a casualty report in correct form; pass grid references, numbers, and times without error; write and speak a date-time group and name the operational time zone; and confirm and log a message in a simple signals log.
Key Terms
- Service message: any item of information passed for a military purpose, by whatever means, held to the standards of accuracy, brevity, and clarity.
- Report format: an agreed, fixed structure for a particular kind of report, learned by both sender and receiver, so that information arrives in a predictable order.
- Situation report (SITREP): a structured update on where you are and what is happening, sent routinely or on request.
- Contact report: the short, immediate report sent the moment a section makes contact, saying who is in contact, what is happening, where, and what is being done.
- Sighting report: a structured report of something observed when you are not yourself in contact, built on a fixed aide-memoire so nothing is forgotten.
- Casualty report: a structured request for help to an injured person, giving the location, the casualty's condition and number, and what is needed.
- Assessment: a stated opinion or judgement, clearly labelled as such so the receiver does not mistake it for fact.
- 24-hour clock: the way time is written and spoken in service, from 0000 to 2359, so that no hour can be confused with another.
- Date-time group (DTG): the standard way to write a single instant: the two-figure day, then the hours and minutes, then a single zone letter, then the month and year.
- Zone letter: a single letter naming the time zone a time is given in; Z, spoken "Zulu", means Coordinated Universal Time, the common operational clock.
- Signals log: a simple written record of messages sent and received, with the time, the station, and the substance.
Accuracy First: The Principles of a Good Service Message
A service message is judged first on whether it is true, and only then on whether it is brief and clear. Brevity and clarity serve accuracy; they never replace it. A short, clear message that is wrong sends help to the wrong place and a commander to the wrong decision. So the first discipline is to report fact: what you actually saw, heard, found, or did, not what you assume, expect, or fear.
This does not forbid opinion. A commander often needs your judgement as well as your observation, because you are the one on the ground. The rule is to say plainly when you are giving opinion rather than fact, so the receiver can weigh it correctly. "Two people are sheltering under the collapsed barn" is a fact. "I think there may be a third inside, but I cannot see" is an assessment, and labelling it as such tells the commander exactly how much to trust it. The Basic Training Manual offers a useful habit: separate fact, assessment, and gap, that is, what you know, what you think it means, and what you do not know. Three honest lines in that order give a commander everything needed to decide.
FACT what you actually observed or did
ASSESSMENT what you think it means (labelled as opinion)
GAP what you do not know, stated plainly
FACT: two people are under the collapsed barn, both moving.
ASSESSMENT: there may be a third inside; I judge it likely from the
size of the building, but I cannot confirm it.
GAP: I cannot see the far side of the barn or reach it yet.
Notice the discipline of the gap line. Most soldiers will give a fact and many will offer an assessment; what separates a trained reporter from an untrained one is the willingness to write down what is unknown. A stated gap tells the commander where the picture is thin and where to send the next effort, and it stops a reader from quietly assuming you have seen what you have not. Never let a gap pass as a fact by saying nothing about it.
Two failures corrupt reports more than any other, and both are matters of character before they are matters of skill. The first is inflation: making a report sound more certain, more serious, or more complete than the truth warrants, whether to seem useful or to avoid an awkward gap. The second, and more common, is omission: leaving out the detail that complicates the picture, so that a clean-looking message quietly misleads. Report what is uncomfortable as readily as what is clear. Never guess to fill a silence; "unknown" is a complete and honest answer, and far better than a confident invention. When you are unsure whether a thing is fact or assessment, demote it: call it an assessment, and let the commander promote it if other reports confirm it.
Why Standard Formats Matter
If accuracy is the first discipline, the standard format is the tool that protects it under pressure. A format is simply an agreed order in which the pieces of a report arrive, learned in advance by everyone on the net. Its value is plain once you picture the receiver, who is usually writing your message down, often by hand, sometimes in poor light or while doing three other things. When your report follows a known shape, that person knows what is coming, can lay out the page to receive it, and notices at once if a line is missing.
A format does the same service for the sender. Under stress the mind drops things; a structure that asks for each item in turn means nothing vital is forgotten, because the format remembers for you. You do not compose a report from nothing while your pulse is high; you fill in a frame you already know. This is why the Army teaches a small number of standard reports and drills them until they are automatic. These formats are not bureaucracy. They are the tested means by which tired people pass accurate information to other tired people and have it acted upon.
There is a second, quieter benefit. A format lets a receiver who misses a line ask for exactly the piece that is missing. If the casualty report has a known shape, a watchkeeper who failed to catch the number of casualties can call "say again your line four, number of casualties", and you give that one line again without resending the whole message. A free-form report has no line four to ask for, so a single missed word costs a full repeat and wastes the net when it is busiest. Learn the formats well enough to give any single line on request, not only to recite the whole from the top.
The Situation Report (SITREP)
The situation report is the steady heartbeat of a patrol's communication: a structured update on where you are and what is happening, sent at set times, on reaching a checkpoint, or whenever the controlling station asks. It keeps the commander's picture current so that direction and support can follow you. A SITREP need not be long, but it must be complete and in order. A simple, reliable structure is:
SITREP
Callsign: who is reporting
Time: time of the report (24-hour clock)
Location: grid reference of your position
Situation: what is happening; "nothing significant" if so
Activity: what you are doing now and next
Intentions: where you are going; expected time
Other: anything the commander needs (supplies, persons, requests)
Sent on the net, that becomes a brief, ordered passage: callsign, time, grid, what you see, what you are doing, where you are going, and any need. The receiver writes it straight down because it arrives in the order the page is ruled for. Patrolling and Tactical Movement, the course this one most closely serves, depends on these routine updates to keep a moving section located and supported.
Two habits make a SITREP genuinely useful. The first is the honest "nothing significant" line. A SITREP reporting a quiet sector is not wasted; it confirms positively that the section is in place, on time, and well, and its absence is itself information that something may be wrong. Send the routine SITREP even when nothing has happened, because the commander is tracking your safety as much as your progress. The second is to make the intentions line a genuine forecast, not a vague hope. "Moving to the river crossing, expect to be there in three-zero minutes" tells the controlling station when to expect your next call and when to begin worrying if it does not come. A clear expected time turns the next silence into a deadline, which is exactly what a watchkeeper needs.
The Contact and Sighting Reports
The contact report is the shortest and most urgent report you will send. It goes the instant a section makes contact, before anything else, because it tells the commander that the situation has changed and the section's attention is now fixed. Keep it to four things: who is making the contact (your callsign), what is happening, where, and what is being done. Send it, then act; the fuller picture follows once you can give it.
CONTACT
Callsign: who is in contact
What: nature of the contact
Where: grid or clear location
Action: what you are doing now
The contact report is short because it competes with the very thing it reports. At the moment of contact your hands and attention are needed for the contact itself, so the report is cut to the four facts a commander cannot act without. Think of it as a flare, not a letter: it says "the situation has changed, here, and I am dealing with it", and it buys you the right to fall silent and act while the controlling station holds the net clear. Say the four parts, end with "wait out" to tell the net that more will follow when you can give it, then turn back to the task.
In the small, defensive, humanitarian setting of this Army, the word "contact" is far more likely to mark a found person, a hazard, or an unexpected encounter than an enemy. The discipline is the same: report it at once, in four parts, then say more when you can. The immediate-action drills that follow a contact, and the fuller reports that come after, are taught in detail in Patrolling and Tactical Movement; this lesson gives you the reporting frame those drills hang upon.
The sighting or information report carries what you have observed when you are not yourself in contact: a person, a vehicle, a hazard, a group at a distance. Because an element under observation is easy to forget, use a simple aide-memoire: what you see (size or number), where it is, when you saw it, what it is doing, and what you are doing about it. Hold the five by the question word that begins each, the four W's and the deed, "What, Where, When, What doing, What I am doing", and a sighting report almost writes itself. As a template it sits like this:
SIGHTING REPORT (aide-memoire: What - Where - When -
What doing - What I am doing)
Callsign: who is reporting
What: size or number, and a plain description
Where: grid reference or a clear, unmistakable location
When: the time you observed it (24-hour clock)
What doing: the activity: still, moving, and in what direction
What I am doing: your action: observing, holding, withdrawing
Filled in, that becomes: "Three persons, at the road junction grid given, observed at one-four-three-zero, on foot moving north, I am keeping watch and holding position." That is complete, ordered, and free of guesswork; if you do not know a thing, say "unknown" and move on. The "what doing" line is where soldiers most often slip into assessment, so guard it: "three persons walking north" is a fact, while "three persons searching for someone" is an opinion that belongs on the assessment line, plainly labelled, if you give it at all.
The Casualty Report
When someone is hurt, the report's whole purpose is to get the right help to the right place quickly, and the casualty report is built for exactly that. It is a structured request for help, not a medical account. Your job on the net is to say where the casualty is, what state they are in and how many there are, and what you need; the clinical work of treating and prioritising the casualty belongs to Combat First Aid, which teaches the casualty report and the priorities of evacuation in full. Keep your message to the request:
CASUALTY REPORT
Callsign: who is sending
Location: grid reference of the casualty
Number: how many casualties
Condition: brief state (conscious or not; walking or not;
nature of injury in plain words)
Help needed: what you require (medical team, stretcher party,
evacuation)
Access: how to reach the site; hazards on the way
The format keeps you to a structured description, not treatment: "conscious, breathing, suspected broken leg, cannot walk" is the right level of clinical detail for the net. Combat First Aid trains you to do more for the casualty in person; this report is how you summon the people and means to help. As with the contact report, a casualty is one of the two urgent reports an RKA soldier is most likely ever to send, so know it cold.
Two lines repay extra care. The number must be exact and given digit by digit, because it sizes the whole response: one casualty brings a stretcher party, several may change the means of evacuation entirely. If the number may yet rise, say so as an assessment: "one casualty confirmed, possibly a second still in the water". The access line is the one inexperienced soldiers forget, and it is often the difference between a fast evacuation and a wasted hour. A confirmed grid tells the rescue party where the casualty is; the access line tells them how to reach the spot with a stretcher and what threatens them on the way: "approach on foot from the forestry track, the ground is steep and wet, no vehicle access". Help that cannot reach the casualty is not yet help, so describe the route and the hazards as plainly as the injury.
Sending Grids, Numbers, Dates, and Times Clearly
A report is only as good as the numbers in it, and numbers are exactly what a degraded radio, a tired ear, and an unfamiliar accent corrupt most easily. Three habits protect them. First, grid references: give them digit by digit, never as a whole number. The grid Quebec Romeo two-four-eight three-seven-one is unmistakable; "two hundred forty-eight" is not. Navigation and Fieldcraft teaches how a grid reference is read off the map and to what precision; this course teaches you to send it so it survives the journey. Lead with the two grid-square letters when the reference may be plotted on another sheet or passed to another agency, and speak them phonetically, "Quebec Romeo", so the letters carry through noise the way the figures do. Second, numbers generally: pass them one figure at a time using the spoken numerals introduced in Lesson 02, so that the figures carry through noise the way the phonetic alphabet carries letters. Third, dates and times: use the 24-hour clock, state the figures clearly, and remove ambiguity. "Zero-six-three-zero" cannot be mistaken for half past anything else.
Be precise about how the figures are spoken, because the whole system rests on each digit arriving whole. Speak each figure on its own, "two-five-four", never "two hundred fifty-four", with the natural slight pause between groups that lets the receiver write each digit as it lands. Service practice sharpens two figures easily lost through noise: nine is often spoken "niner" so it cannot be heard as "five", and a decimal point is spoken "decimal". The principle is the one Lesson 02 set out for letters: replace anything a tired ear could confuse with a sound that cannot be mistaken.
The single habit that catches the error these precautions miss is the readback. The receiver repeats the critical part, the grid, the number, the time, the negative instruction, back to the sender, who confirms it. Lesson 01 named confirmation one of the four marks of good communication, and this is where it earns its place: an unconfirmed grid is a hope, and help sent to a hoped-for grid may never arrive. Always read back, and always wait to be read back to, the numbers that matter. If a readback comes back wrong, do not repeat the whole message; say "negative" and give the corrected figure alone, then have it read back again, so the correction is as clear as the original.
Time in Military Messages
Time deserves its own discipline, because a report that fixes the wrong moment can mislead as badly as one that fixes the wrong place. A casualty seen "an hour ago" means nothing to a watchkeeper who does not know when you spoke; a rendezvous set for "half five" can be missed by twelve hours. The Army therefore writes and speaks time in a single, unambiguous way, and learns it until it is second nature.
The foundation is the 24-hour clock. The day runs from 0000, the first minute after midnight, to 2359, the last minute before the next midnight, and every time is given as four figures: the first two the hour, the last two the minutes. Morning times look familiar, "zero-six-three-zero" for half past six in the morning; afternoon and evening times count on past twelve, so one in the afternoon is 1300, half past five in the evening is 1730, and ten at night is 2200. Always speak all four figures, including the leading zero, because "zero-six-three-zero" cannot be mistaken for anything, while "six thirty" can be heard as morning or evening, as a time or as a fraction. Midnight is written 0000 and may be confirmed in words to avoid any doubt at the turn of the day. The 24-hour clock removes at a stroke the commonest civilian time error, the confusion of morning and afternoon, and it is the clock every report in this lesson uses.
For a precise instant that names not just the time but the day, the month, and the year, the Army uses the date-time group, or DTG. It packs a whole moment into one compact, ordered group that can be written in a log, spoken on the net, and read back without ambiguity. A DTG is built in a fixed order: the two-figure day of the month, then the hours and minutes on the 24-hour clock, then a single zone letter that says which time zone the time belongs to, then the abbreviated month, and finally the two-figure year. Written out, a moment looks like this:
DATE-TIME GROUP: 050930Z JUN 26
| | | | | |
| | | | | +-- year: 20-26
| | | | +------- month: JUN (June)
| | | +--------- zone: Z = Zulu (UTC)
| | +------------ mins: 30 minutes past
| +--------------- hour: 09 (the 24-hour hour)
+----------------- day: 05 (5th of the month)
reads as: the 5th day, at 0930 hours, Zulu time, in June 2026
Read each part in turn and the group comes apart easily: 05 is the fifth of the month, 0930 is half past nine on the 24-hour clock, Z is the zone, JUN is June, and 26 is the year 2026. The order never changes, so a reader always knows that the first two figures are the day and the next four are the time, however unfamiliar the rest. Spoken on the net, a DTG is read figure by figure with the zone and month phonetic where needed: "zero-five-zero-niner-three-zero Zulu, June two-six". Because it is read digit by digit, the same rules apply as for any number: speak each figure on its own, and read back the whole group, because a single wrong figure changes the day or the hour.
The single letter in the middle of the DTG is the time zone, and it solves a problem that grows the moment more than one location is involved. Clocks differ from place to place, so a time plainly understood by the soldier who sends it can be an hour or several hours out for the soldier who receives it, and a casualty or rendezvous timed against the wrong clock is a serious failure. The Army's answer is to give every operational time against one agreed clock and to name that clock with a single letter. The most important letter is Z, spoken "Zulu", which means Coordinated Universal Time (UTC), the world's reference clock. When a time carries the Zulu letter, everyone who reads it knows it is given against the one common clock, whatever the local time happens to be where they stand, so units in different places all work to a single time without converting in their heads. That is why Zulu is used as the common operational time: it gives every station, every log, and every plan one shared moment to point at.
The other letters name local zones. Each band of the world is given its own letter, and a time carrying that letter is the local clock in that band rather than the universal one. The full set is not worth memorising, but the idea is simple: where Zulu is the common reference, a local zone letter says "this time is the clock on the wall here", convenient for a purely local matter but dangerous the moment a message crosses zones. The safe rule for a small home-defence force is plain. Keep routine local work to your own local time when everyone shares it, but the instant a time will be read by anyone working to a different clock, or logged for a record that others will rely on, give it in Zulu. A time without a zone letter is an invitation to error; a time with the wrong zone letter is worse, because it looks precise and is not.
ZONE LETTERS
Z "Zulu" Coordinated Universal Time (UTC) - the common
operational clock; use this when units in different
places must work to one time, and for records.
local other single letters name local time bands; a time
letters with a local letter is "the clock here", fine for
shared local work, risky once a message crosses zones.
rule of thumb: local time for shared local work;
Zulu the moment a time crosses zones or enters a log.
Confirming and Logging
The last habit closes the loop and makes it accountable. Every message of any importance should be confirmed, by readback or by a clear acknowledgement, so the sender knows it landed; an unacknowledged message has been spoken, not communicated. And it should be logged. A signals log is a plain written record kept at the controlling station, and often by the patrol too: the time in 24-hour clock, the station, and the substance of what passed, line by line in ink. It need not be elaborate; it must be honest and contemporaneous.
SIGNALS LOG
Time Station In/Out Message Action
0612 Two Alpha In SITREP, grid QR 251 373, no sig. Logged
0648 Two Alpha In Found person, grid QR 254 371... Passed up
0651 Two Alpha Out Readback grid, stretcher sent Actioned
The time column is the heart of the log, and where the discipline of this lesson comes together. Each entry carries the time the message passed, in the 24-hour clock, written as it happens; for a record that may be read across zones, or compared with another unit's log, the full date-time group is used so the moment is fixed beyond doubt. Times are never rounded to look tidy or adjusted afterwards to fit the story; the value of the log is precisely that it records what happened when it happened, so that two reliable logs laid side by side will agree.
The log matters for two reasons. While the task is live, it lets a relief or a handover see at a glance what has happened and what is outstanding, so nothing is dropped between shifts. Afterwards, it is the record of what was actually sent and when, which protects the soldier who reported honestly as much as the chain that relied on the report. Entries are never erased or backdated; an error is struck through with a single line, initialled, and corrected. The signals log is a quiet discipline, but it is part of the accountability this whole course rests upon.
In Practice: A Search on the Slopes
A walker is overdue on the wooded slopes above a small town, and a Royal Kaharagian Army section is searching its assigned spur while the duty office keeps the net. Forty minutes in, the section commander finds the walker, who has fallen, is conscious, and cannot stand. There is no enemy here and never was; this is the kind of report this Army most often sends. The commander pauses, drops the pitch, and passes it in two parts. First the contact, immediate and short: "Zero, this is Two Alpha, found person, grid Quebec Romeo two-five-four three-seven-one, casualty, wait out." Then, moments later, the casualty report in order: "Zero, this is Two Alpha, casualty report. Location grid Quebec Romeo two-five-four three-seven-one. One casualty. Conscious, breathing, suspected broken ankle, cannot walk. Request stretcher party and medical assessment. Access on foot from the forestry track, ground is steep and wet. Over."
Zero reads back the grid and the request, and the duty watchkeeper logs both lines with their times. Because this report will be passed up and may later be compared with the rescue service's own record, the watchkeeper times the find with a full date-time group, 050948Z, the fifth at 0948 Zulu, so the moment is fixed against the one clock both organisations share. A stretcher party is on its way to a confirmed location. Fact came before opinion, the format kept anything from being forgotten, the readback fixed the grid, the time was recorded against the common clock, and the log will show exactly what was done and exactly when.
Check Your Understanding
- Why is accuracy placed ahead of brevity and clarity in a service message? Give an example of a short, clear report that would nonetheless be a failure, and explain why. In your answer, say what the "gap" line of the fact-assessment-gap habit adds that a fact and an assessment alone do not.
- A standard report format helps both the sender and the receiver. Describe one way it helps each, including how a named line lets a receiver recover a single missed item. Then explain how separating fact, assessment, and gap keeps a report honest.
- Write out the date-time group 050930Z JUN 26 in plain words, naming each part in order, and say how you would speak it on the net. What does the zone letter Z mean, why is Zulu used as the common operational time, and when would you use a local zone letter instead?
Reflection (write a short paragraph): The most common reporting failure is not invention but omission: leaving out the awkward detail so the message looks clean. That is a question of character before it is a question of skill, and a commander's decision, and perhaps someone's safety, rests on what you choose to include. Think honestly about the pull to tidy a report, whether by dropping an inconvenient fact or by rounding a time so the log looks neat. What standard will you hold yourself to when the inconvenient fact is the one the commander most needs, and how does reporting the uncomfortable truth fit the humanitarian purpose this Army serves?
Summary
- A service message is judged first on accuracy, then on brevity and clarity. Report fact; when you give opinion, label it plainly as an assessment; and separate fact, assessment, and gap, including the gap line, so the picture stays honest.
- Standard formats protect accuracy under pressure: they let the receiver write the message down and act, they let a receiver ask for a single missed line by name, and they ensure the sender forgets nothing, because the structure asks for each item in turn.
- The SITREP gives a structured update on position and activity, including an honest "nothing significant" and a genuine expected time; the contact report is the short, immediate report on making contact (who, what, where, what is being done); the sighting report uses a fixed aide-memoire (what, where, when, what doing, what you are doing about it) as a usable template.
- The casualty report is a structured request for help, giving location, the casualty's exact number and condition, what is needed, and the access route with its hazards; the treatment itself belongs to Combat First Aid. Grids and numbers go digit by digit with the spoken numerals from Lesson 02, and the critical figures are always read back.
- Time is fixed without ambiguity: the 24-hour clock (0000 to 2359, all four figures spoken), the date-time group (two-figure day, hours and minutes, a single zone letter, the month, the two-figure year, as in 050930Z JUN 26), and the zone letters, with Z "Zulu" meaning Coordinated Universal Time as the common operational clock so units in different places work to one time, and local zone letters reserved for shared local work.
- On RKA operations the commonest urgent reports are a found or missing person and a casualty, not an enemy. Confirm every message that matters and log it honestly and contemporaneously, with reliable times, because the signals log supports both the live task and later accountability.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia