Lesson Overview
Lessons 03 and 04 covered the staff work that prepares and issues orders. This lesson covers the staff work that runs while the operation is happening: the reports, returns, and records by which a command keeps its picture current and knows its own state. Once orders are given and the operation is under way, the commander's grip on the situation, which the command course showed is always partial and ageing, must be continually refreshed. It is refreshed chiefly by the reports flowing in from the command.
A command that reports well keeps an accurate picture and can be commanded. A command that reports badly leaves its commander blind. But reporting is peculiarly prone to a particular failure: reports and returns generated for their own sake, burdening the command with traffic that serves the form rather than the commander. A command can be drowned in reporting as easily as starved of it. The staff officer's task is to get the balance right, and it matters greatly in a small humanitarian home-defence force whose soldiers are doing relief work that needless reporting should not interrupt.
By the end you will be able to explain why a command reports to be commanded; describe the main kinds of report and return and what each is for; explain the qualities of a good report (timely, accurate, relevant, clear) and the special importance of honest bad news; explain how to get the reporting flow right, applying the service of command; and explain the purpose of records and how a command keeps what it needs without drowning in paper.
Key Terms
- Report: a communication that tells the commander or headquarters something about the situation, so the picture can be kept current.
- Return: a regular, usually structured account of the state of something (strength, stores, readiness) by which a command knows and accounts for its own resources.
- Record: the kept information a command needs to function and account for itself, from the log of events to the registers of what it holds and has done.
- The current picture: the command's working understanding of the situation and its own state, the thing the commander commands from, always being refreshed against its drift from reality.
- The situation report: the periodic report giving the current state of the situation and the command; often the backbone of a command's reporting.
- Reporting by exception: the discipline of reporting what has changed or what matters, rather than everything, so the flow carries the significant and does not bury it.
- Information overload: the failure in which so much is reported that the important is lost in the volume and the command is burdened rather than informed.
Why a command reports: keeping the picture current
Begin with the purpose, because all the craft follows from it. A command reports so its commander and headquarters can keep their picture of the situation current. The command course explained why this matters: a commander's grip on a situation is always partial and always ageing, a model simpler than reality and behind it in time, and the moment it is formed the world has moved on. Reporting is the chief means of refreshing it. A commander whose picture is kept current commands the actual situation; a commander whose picture is not refreshed commands a situation that no longer exists, decides on stale information, and is surprised when reality breaks through.
The phrase to hold is that a command reports to be commanded. Reports tell the commander what is happening so they can decide what to do, reveal the changes and surprises that call for a decision, and let the headquarters coordinate its parts. A command that does not report well cannot be commanded well, because its commander cannot see it: the soldiers may be acting, but the commander cannot tell whether the plan is working or where the difficulties are, and so cannot adjust, reinforce, or redirect, the very things the command course said commanding in execution consists of. This is why reporting is a genuine operational matter, not mere administration. A command that reports badly goes dark to its own commander at exactly the moments when being seen matters most.
The kinds of report and return
An officer should know the main kinds and what each is for, because using the right kind for the right purpose is part of the craft. Reports tell of the situation; returns account for the command's own state.
The backbone of most commands' reporting is the situation report, sent on a regular rhythm. It answers the standing question of what the position is now, summarising what is happening, what the command is doing, and what has changed, so the headquarters' picture is refreshed steadily. Alongside it are by-exception reports, sent at once when something occurs that cannot wait for the next scheduled report: a significant change, an unexpected development, a problem, an opportunity. There are also special reports for particular purposes, such as a report on completing a task, a casualty report, or a request for something the command needs.
Returns are the other family. A return is a regular, structured account of the state of something the command must track: its strength (how many soldiers, fit and present), its stores (what it holds and is running short of), its readiness (the state of its kit). Returns let the commander know their own means, what they can do, what they are short of, and when they must resupply or rest. A commander who does not know their own strength and stores commands blind in a different way, ignorant not of the situation but of themselves. The officer uses each kind for its purpose, so the right information flows to the right place by the right means.
The qualities of a good report, and honest bad news
A report that is late, wrong, irrelevant, or unclear fails to keep the picture current however faithfully it was sent. The qualities of a good report are the qualities of good service writing applied to reporting, with one addition.
A good report is timely: it reaches the commander in time to be acted on, because a report that arrives too late is useless however accurate, the same truth the command course taught of decisions. It is accurate: it tells the truth, distinguishing what the reporter knows from what they suppose, because a wrong report is worse than none. It is relevant: it carries what the commander needs, not everything the reporter could say, because padding buries the significant; the discipline of reporting by exception serves this. And it is clear: it conveys its meaning plainly and cannot be misread, in the brief, standard form that service writing teaches.
The addition of special importance is the honest reporting of bad news, because this is where reporting most often fails and where failure is most dangerous. There is a strong human temptation to soften, delay, or suppress the report that the task is going wrong, because bad news is unwelcome and the reporter fears the reaction. But honest bad news, reported promptly, is exactly what a commander most needs, because it is the news that calls for a decision: the failing plan that must be changed, the developing problem that must be met. A commander kept ignorant of it cannot act until it has grown into a crisis. The ethical-leadership course taught that a healthy command makes it safe to report bad news, and that the silencing of bad news is the mark of a command going wrong; here the same truth appears as a reporting discipline. The reporter must report bad news honestly despite the temptation to soften it, and the command's climate must make it safe to do so. A command whose good news flows freely but whose bad news is slow or suppressed will be surprised by disasters that earlier honest reporting would have let it prevent.
THE QUALITIES OF A GOOD REPORT
TIMELY ----- reaches the commander in time to act on; a late
report is useless however accurate
ACCURATE --- tells the truth; distinguishes known from supposed;
a wrong report is worse than none
RELEVANT --- carries what the commander NEEDS, not everything;
report by exception (what changed, what matters)
CLEAR ------ plain, brief, standard form; cannot be misread
+ HONEST BAD NEWS, promptly: the report that the plan is failing
is exactly what the commander most needs, because it calls for
a DECISION. Make it SAFE to report; a command that suppresses
bad news blinds its commander to what it most needs to see.
Getting the flow right, and the purpose of records
The final craft is getting the reporting flow right and keeping the records a command needs. Both are governed by the service of command that has run through the course: reporting and records exist to serve the command, and they are got right by that test, not by maximising either.
Getting the flow right means steering between two failures. The first is too little reporting, which leaves the commander under-informed, picture stale and gapped. The second, equally real and often less noticed, is too much: information overload, in which the important is lost in the volume and the soldiers' time and the communications are consumed by traffic that does not earn its place. Three disciplines achieve the balance. Reporting by exception, so the flow carries the significant rather than the routine. A sensible reporting rhythm, with situation reports at intervals matched to how fast the situation changes, neither so frequent they burden nor so rare the picture goes stale. And the service-of-command test applied to every report and return required, cutting what does not actually help. In a small humanitarian force this matters greatly: the staff must require only the reporting that genuinely keeps the commander informed, not reporting for the form's sake that steals soldiers from the people they are helping.
Records hold the information the command needs to function and account for itself: the log of events, the registers of what it holds and has done, the returns of its state. A command keeps records so it can track its history, account for its resources and actions, hand over cleanly to a relief or successor, and learn afterward. Like all staff work, records are governed by the service of command and the discipline of simplicity: keep what is genuinely needed, accurately and simply, and no more. Records kept for their own sake are the same failure as reports generated for their own sake, paper that serves the form rather than the command. Keep too few and you cannot account for the command; keep too many and you drown in paper that serves no one.
In Practice: The Reports That Kept the Picture
An officer of the Royal Kaharagian Army runs the small headquarters of an element spread across a wide area on a multi-day relief task after a flood, with sections working far apart at different sites. The orders are given; the task now is to keep the commander's picture current so the operation can be commanded as it unfolds.
The officer sets a rhythm of situation reports, each section reporting at intervals matched to how fast things are changing, frequent enough to keep the picture current but not so frequent that reporting interrupts the relief work. Alongside the rhythm they require reporting by exception, so any significant change is reported at once. They resist demanding detailed returns that would steal the sections' time, holding the service-of-command test and cutting reporting that does not earn its place. They train the sections to report timely, accurate, relevant, and clear, distinguishing what they know from what they suppose. Above all, they build a culture in which bad news travels fast: the sections know it is safe to report that a site is going wrong, and they do, because the officer wants exactly that news and does not punish it.
The value shows on the second day. A section reports, promptly and honestly, that the water is rising faster than expected and its site will be cut off sooner than planned. Because the report is timely, accurate, relevant, and clear, the commander's picture is refreshed at once with the thing they most need to know, and they redirect effort to the threatened site while there is still time. Had the flow been wrong, the same situation would have gone badly: too little reporting and the commander learns of the rising water too late; softened bad news and the commander is surprised by a crisis; information overload and the crucial report is lost in routine traffic. Through the rest of the task the officer keeps a simple log and the returns of strength and stores, accurately and without multiplication, so the command knows its own state and can hand over cleanly to the relief that follows.
Check Your Understanding
- Explain why a command reports, in terms of keeping the commander's picture current, and why "a command reports to be commanded" captures it. Why is reporting an operational matter rather than mere administration, and what happens to a command that reports badly during a changing operation?
- Describe the main kinds of report and return (the situation report, the by-exception report, special reports, and the returns of the command's own state) and what each is for. Why must an officer use the right kind for the right purpose, and what is a commander missing if their command keeps no returns?
- Explain the qualities of a good report (timely, accurate, relevant, clear) and why neglecting each causes a real failure. Then explain the special importance of honest, prompt bad news, and how to get the reporting flow right between too little and too much, with the service-of-command discipline that governs records.
Reflection (write a short paragraph): This lesson says there is a strong human temptation to soften, delay, or suppress bad news, and that honest bad news reported promptly is exactly what a commander most needs, because it is the news that calls for a decision. Think honestly about your own behaviour. When something you are responsible for is going wrong, are you quick to report it to those who need to know, or do you tend to delay, soften, or hope to fix it quietly first? Be truthful, because the instinct to hide bad news is strong and feels like protecting oneself. Then consider its cost in a command: the commander kept ignorant of a problem cannot act until it has grown into a crisis. Describe one habit you could begin building now, of reporting bad news honestly and promptly even when it reflects on you, so that the command you one day run has the fast, honest bad news on which a commander's grip most depends.
Summary
- A command reports so its commander can keep an accurate, current picture, because the commander's grip is always partial and ageing. A command reports to be commanded: the reports let the commander see, decide, adjust, and coordinate. Reporting is an operational matter, not administration; a command that reports badly goes dark at the moments when being seen matters most.
- Reports tell of the situation; returns account for the command's own state. The backbone is the situation report, on a regular rhythm; alongside it are by-exception reports for the urgent, and special reports for particular purposes. Returns track strength, stores, and readiness, since a commander ignorant of their own means commands blind. Use each kind for its purpose.
- A good report is timely, accurate, relevant, and clear. The addition of special importance is honest, prompt bad news, which there is a strong temptation to suppress but which a commander most needs because it calls for a decision. A command must make it safe to report bad news, or it will be surprised by preventable disasters.
- Get the flow right by steering between too little (commander under-informed) and too much (information overload). The disciplines are reporting by exception, a sensible rhythm matched to how fast the situation changes, and the service-of-command test cutting what does not help, which matters greatly in a small force whose soldiers should not be stolen from relief work.
- Records hold what the command needs to function, account for itself, hand over, and learn. Like all staff work they are governed by the service of command and the discipline of simplicity: keep what is genuinely needed, accurately and simply, no more. This applies the service writing of Lesson 02 and the service of command of Lesson 01 to the running operation, supports the commanding-in-execution of LDR 410, and leads into the running of a small headquarters in Lesson 06.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia