Lesson Overview
Command sits at a distance from the strength. It cannot see every member on parade, every soldier on leave, every clerk away on a course; it sees what the orderly room tells it, and it plans on that. The work of telling it, accurately and on time, is the subject of this lesson. A force that keeps a true picture in its own files but never sends it up has done half the job; the picture is only of use to command when it is rendered to command, in the form command needs, on the cycle command relies on. This lesson is about that rendering: the regular returns and reports the orderly room sends up the chain, and the discipline that keeps them honest.
It draws together threads you have met across the course. The personnel picture from Lesson 01, establishment and strength, the nominal roll and the strength return, is the raw material; here you learn the routine by which it is reported. The events of Lessons 02 and 03, joinings and departures, promotions, appointments, and postings, are what keep changing the picture that the returns report. And the standard of accuracy that has run through all of it now meets a hard new demand: the return must be not only true but on time, because a true return rendered late is a picture command did not have when it had to decide. Running underneath is the work of reconciliation, keeping the strength account square, so that the roll, the records, and the people on the ground all agree before the figure ever leaves the orderly room.
This is the knowledge layer. Reading and understanding the returns cycle is taught here; the hands-on administration of it, compiling a strength return from a current roll, reconciling the strength account before rendering, and rendering a report into the battle rhythm on time, is practised and signed off in person where supervision allows, on a real or representative orderly-room set, because rendering returns is a routine of the hands as much as the head. By the end you will be able to explain what regular returns and reports are and why command depends on them; name the common returns the orderly room renders, including strength, leave, and training state; explain what the strength account is and how it is reconciled so the roll, the records, and the people on the ground agree; explain the administrative battle rhythm and how returns sit within it; and explain why returns must be accurate and on time, and what harm a late or careless return does.
Key Terms
- Return: a routine report of figures rendered up the chain of command on a set cycle, for example a strength return or a leave return. A return reports a count or a state; it answers "how many" or "in what condition", in a fixed form, at a fixed time.
- Report: a piece of information rendered up the chain, routinely or on occasion. Every return is a report; not every report is a routine return. The terms are used together because the orderly room renders both, but a return is specifically the regular, scheduled, fixed-form kind.
- Strength return: the return that reports the numbers on strength against establishment, rendered up the chain on a routine cycle. The central personnel return, met in Lesson 01 and built out here.
- Leave return: a return reporting who is on leave and the leave state of the force, so command knows how much of the strength is away and how much remains available.
- Training state: the return or report of where members stand on required training and qualification, drawn from the training record, so command knows the trained strength, not just the head count.
- Strength account: the running, reconciled account of who is on strength, kept square so that the nominal roll, the service records, and the people actually present all agree. To "keep the account" is to maintain it; to "reconcile the account" is to check and correct it.
- Reconciliation: checking that the nominal roll, the service records, and the bodies on the ground all agree, and running down and correcting any difference. Met in Lesson 01; here it is the routine that squares the account before a return is rendered.
- Battle rhythm: the routine cycle of reports, orders, and meetings by which a headquarters runs. Each return, order, and meeting has its place and its time in the rhythm, so the work is regular and predictable rather than chased in a crisis.
- Suspense (or deadline): the time by which a return is due. A return rendered after its suspense is late, and a late return is a picture command did not have when it needed it.
- Render: to send a return or report up the chain to the headquarters that requires it. The orderly room compiles, reconciles, and then renders.
Returns and reports: keeping command informed
Start with the plain purpose. The orderly room holds the truth of the unit's people, and command, sitting above it, needs that truth to plan. A return is how the truth travels upward. It is a routine report of figures, rendered to the higher headquarters on a set cycle, in a fixed form, so that command always holds a current account of the force without having to ask for it.
Notice the two words that do the work: routine and rendered. Routine means the return goes up on a known cycle, weekly or daily or whatever the headquarters has laid down, not only when someone remembers to ask. Command can rely on a Monday strength return the way it relies on the sun rising; it plans the week around the figure it knows will arrive. Rendered means the return is actively sent up, not merely held below for someone to come and find. A picture kept in the orderly room and never sent is a picture command does not have. The whole point of a return is to close the distance between the strength on the ground and the command that must plan for it.
A report, in the wider sense, is any information rendered up the chain, and not every report is a routine return. An occasional report, a member taken seriously ill, a sudden departure, a discrepancy found in the account, goes up as the event demands, outside the cycle. But the backbone of keeping command informed is the routine return, because it is regular, predictable, and complete: it does not wait for something to go wrong before it tells command how the force stands. The good orderly room renders both, and command is never surprised by something the orderly room knew and did not pass up.
The reason all of this matters reaches back to Lesson 01: command cannot plan what it cannot count, and it counts on what the orderly room renders. A return is not paperwork for its own sake. It is the instrument by which a commander who cannot see the strength directly comes to know it, and every plan, tasking, relief, and request rests on the figures the orderly room sent up.
The common returns: strength, leave, and training state
Several returns recur in personnel administration, and an administrator should know what each reports and why command wants it. Three are central.
The strength return, met in Lesson 01, reports the numbers on strength against establishment. It is the answer to "how many do we have, set against how many we are authorised". It shows held strength, established strength, and the gap between them, and a good one goes further to show, of those held, how many are presently available and how many are away. It is the foundational personnel return, because the strength is the first thing command must know about its people.
The leave return reports who is on leave and the leave state of the force. Command needs this because leave is the largest predictable cause of members being on strength but not available, and a force that has granted leave to a third of its members has a held strength that overstates what it can call on this week. The leave return lets command see how much of the strength is away on leave at any time, plan tasking around it, and make sure that grants of leave are balanced against the need to keep a working force on the ground. It also protects the member: leave properly returned is leave properly recorded, and a member whose leave is on the return is a member whose entitlement is being honoured and counted.
The training state, drawn from the training record that ADM 220 tracks, reports where members stand on required training and qualification. It tells command not just the head count but the trained strength: how many are qualified for the tasks the force may be set, how many are part-trained, how many still owe a required course. Two forces of equal head count can differ greatly in what they can actually do, and the difference is in the training state. Command plans tasking, and the College plans courses, on what the training state reports, so it must be drawn accurately from the training record and kept current as members qualify.
These three are not the whole of it. Orderly rooms render other returns as their headquarters requires, on pay, on discipline, on whatever command must routinely know. But strength, leave, and training state are the core of the personnel returns, and learning to render those three cleanly teaches the discipline for all the rest: draw from a current and reconciled source, set the figures in the fixed form the higher headquarters wants, and render on the cycle.
THE COMMON PERSONNEL RETURNS
Return Answers Drawn from
---------------- ------------------------- ----------------------
Strength return How many held vs estab, Nominal roll
and of those available? (reconciled)
Leave return Who is on leave, how much Leave record /
of the force is away? leave balances
Training state Trained strength: who is Training record
qualified, part, owing? (ADM 220)
---------------- ------------------------- ----------------------
Occasional An event command must The event, as it
report know now (illness, happens, outside
discrepancy, sudden the routine cycle
departure)
---------------- ------------------------- ----------------------
Each routine return: rendered on its cycle, in fixed form,
from a current and reconciled source.
The figure sets the three routine returns beside the occasional report, and shows for each what it answers and where its figures come from. The point to carry away is the last line: every routine return is rendered on a cycle, in the form the higher headquarters wants, from a source that has been made current and reconciled before the figure is drawn. A return is only ever as good as the account it is drawn from, which brings us to the strength account.
The strength account: keeping it square
Behind every strength return stands the strength account: the running, reconciled account of who is on strength, kept square so that three things always agree. The nominal roll, the named list of who is held. The service records, the trusted accounts behind each name. And the people actually on the ground, the bodies present and accounted for. When those three agree, the account is square and a return drawn from it is true. When they do not, the account is out, and a return drawn from it carries the error upward.
You met reconciliation in Lesson 01 as the discipline that keeps the picture honest. Here it becomes a routine you run before you render. To keep the strength account is to maintain it continuously, updating the roll from every joining and departure as Lesson 02 taught, from every promotion, appointment, and posting as Lesson 03 taught, so the named account tracks reality. To reconcile the strength account is to check, on a set rhythm and always before a strength return goes up, that the roll, the records, and the people present still agree, and to run down and correct any difference before the figure leaves the orderly room.
Three kinds of difference can surface, and each points to a specific fault. A name on the roll with no one present, and no leave, course, or sickness to explain the absence, points to a departure not recorded: someone has gone off strength in truth but is still carried on paper, a phantom inflating the count. A person present with no line on the roll points to a joining not entered: someone is on strength in truth but missing from the named account, a real member the count is failing to hold. And a roll line the records do not support, or a record with no matching roll line, points to an error in one or the other that must be traced and put right. The administrator does not paper over these. A reconciled account is a true one; an unreconciled account only looks true, and a return drawn from it looks just as authoritative whether it is right or wrong.
Reconciliation is not an accusation that someone has been careless. It is the normal hygiene of an account that is always changing, because people are always joining, leaving, moving, and going on and off availability. The account drifts in the ordinary course of things, and reconciliation is how it is pulled back square before its figures are reported. Run it on rhythm and before every strength return, and the account stays honest. Skip it, render straight from a roll no one has checked, and you are reporting a guess dressed as a count.
RECONCILING THE STRENGTH ACCOUNT (a worked check)
Step 1 - Three sources, laid side by side
--------------------------------------------------------------
ROLL says held: 30 RECORDS on file: 29 PRESENT/accounted: 29
(the named list) (trusted accounts) (bodies + leave/
course/sick state)
Step 2 - Walk the roll, line by line, against records and ground
--------------------------------------------------------------
No. On roll? In records? Accounted for? Finding
----- -------- ----------- --------------- ------------------
K0118 yes yes present agree
... yes yes present agree
K0709 yes NO (disch'd NOT present DIFFERENCE:
10 days ago) departure not
struck from roll
K0742 NO yes (joined present DIFFERENCE:
3 days ago) joining not
entered on roll
Step 3 - Run each difference down and correct
--------------------------------------------------------------
K0709 -> verify discharge authority; STRIKE from roll.
Held 30 -> 29.
K0742 -> verify attestation/joining authority; ADD to roll.
Held 29 -> 30.
Step 4 - Account now SQUARE
--------------------------------------------------------------
ROLL held: 30 = RECORDS: 30 = PRESENT/accounted: 30
The three agree. NOW the strength return may be rendered.
The figure walks one reconciliation through. The three sources are laid side by side; the roll is walked line by line against the records and the ground; two differences surface, a discharged member never struck off and a new joiner never entered, that happen to cancel in the head count but are two real faults all the same. Each is run down, its authority verified, and corrected. Only when the three agree is the account square, and only then is the strength return rendered. Note the order: reconcile first, render second, never the other way round. A return rendered from an unreconciled account is a figure you have not earned the right to send.
The administrative battle rhythm
Returns do not happen at random. They sit within the administrative battle rhythm: the routine cycle of reports, orders, and meetings by which a headquarters runs. The battle rhythm is the heartbeat of the orderly room. It lays out what is done daily, what weekly, what monthly, so that the administrative work of the force is regular and predictable, each task with its place and its time, rather than a scramble of things remembered too late.
Why have a rhythm at all? Because a headquarters that does its administration only when prompted does it badly. Returns get chased in a panic, orders go out late, the strength account drifts because nobody set a time to square it. A rhythm replaces all that with routine: everyone knows the strength return is rendered on Monday, the routine orders are published each morning, the leave and training states go up on their set days, the headquarters meets on its set cycle to read the returns and decide what the orders will carry. The work becomes steady and dependable, and command comes to rely on information arriving when it is supposed to, because it always does.
Returns are woven through this rhythm. Each return has a cycle and a suspense, a time it is due, and the rhythm is what holds those cycles together so they do not collide or drift. The strength account is reconciled on rhythm so it is square when the strength return is due. The returns are rendered on rhythm so command's picture is refreshed on schedule. And the rhythm closes a loop: the returns inform the meetings, the meetings inform the decisions, the decisions become orders, the orders generate the very personnel events, promotions, postings, leave grants, that change the strength and feed the next cycle of returns. Lesson 03's Part II orders and this lesson's returns are two phases of the same turning wheel, the orders recording what command decided and the returns reporting where the force now stands as a result.
THE ADMINISTRATIVE BATTLE RHYTHM (an example orderly-room week)
DAILY
Open of business : update strength account from overnight events
(joinings, departures, sickness, returns from leave)
Morning : publish routine orders (Part I instructions;
Part II personnel events with authority)
Through the day : record events as they happen, action correspondence
WEEKLY
Mon : reconcile strength account, then RENDER strength return up
Tue : render leave return; update training state from ADM 220 record
Wed : headquarters administrative meeting (read returns, decide,
set what the orders will carry)
Fri : weekly check of the account; clear the week's correspondence
MONTHLY
Month-end : fuller reconciliation; pay and entitlements review;
longer-cycle returns rendered up
----------------------------------------------------------------------
THE LOOP: returns -> meeting -> decisions -> orders -> events
-> (events change the strength) -> next cycle of returns
The figure lays out one example week. Read it for the shape, not the exact days, since each headquarters sets its own rhythm. What matters is that every administrative task has a slot: the account is updated daily and reconciled before the weekly strength return; orders are published each morning; returns are rendered on set days; the headquarters meets to read the returns and decide. The loop at the foot is the engine: returns feed the meeting, the meeting feeds decisions, decisions become orders, orders generate events, events change the strength, and the strength feeds the next returns. An orderly room that runs to a rhythm like this keeps command informed without ever being chased, because the information arrives on time, every time, by routine.
On time as well as true: the discipline of returns
You have learned across this course that a return must be true. This lesson adds a second demand that is just as hard: it must be on time. A true return rendered late is a picture command did not have when it had to decide, and command does not wait. If the strength return is due Monday and command plans the week's tasking on Monday, a return that arrives Tuesday is useless however accurate it is, because the decision was already made, on a stale figure or no figure at all.
This is why every routine return has a suspense, the time it is due, and why meeting the suspense is itself a discipline, not a nicety. A force runs on its battle rhythm, and a return that misses its slot throws the rhythm out: the meeting reads an old figure, or waits, or decides without one. The administrator owes command the return on time the way a sentry owes the line their watch on time, because something downstream depends on it arriving when it is supposed to. Late, in returns work, is a fault in its own right, separate from and as serious as wrong.
But on time never excuses untrue, and the tension between the two is the real discipline. The pressure of a suspense tempts the careless administrator to skip the reconciliation, to render straight from an unchecked roll because the deadline is close, and that is exactly the wrong response. A return that is on time but built on an unreconciled account is fast and false, the worst of both, because it arrives looking authoritative and misleads command precisely because it was trusted. The answer is not to choose between true and on time but to build the rhythm so both are met: reconcile on a cycle that finishes before the suspense, keep the account square continuously so squaring it is quick, render the moment it is right. An administrator who runs to rhythm does not have to choose, because the account is already square when the return falls due.
And accurate and on time is, finally, a matter of integrity, which ties this lesson to LDR 420. Command acts on what you render. A figure rounded up to look tidier, a leaver left on the roll because striking him is fiddly, a return delayed and then back-dated to look as if it met its suspense, each of these is a small dishonesty with real consequences downstream: a task committed on people who are not there, a vacancy command never learns of, a decision made on a picture that was a lie. The administrator's returns are taken seriously and rendered honestly, true and on time, because careers, entitlements, and operations ride on them. That is the standard, and there is no comfortable figure or convenient delay worth falling short of it.
In Practice: The Monday Return Under Pressure
It is Monday morning and the strength return is due to battalion by ten o'clock. The Orderly Room NCO comes in to find the week already complicated. Two members returned from leave over the weekend, one went sick on Sunday, a new joiner attested on Friday afternoon and was in-processed but the roll line was never added, and a discharge that fell on Friday was actioned, kit cleared and access revoked, but not yet struck from the nominal roll. The roll on the system, untouched since Thursday, shows thirty held against an establishment of thirty. Tidy, fully held, and wrong in at least two places.
The easy course, with the suspense an hour off, is to render the thirty and be done. The figure is round, the deadline is close, and no one upstream will know the difference this morning. The NCO does not take it. Before a strength return goes up she reconciles, suspense or no suspense, because a fast false figure is worse than no figure at all. She lays the three sources side by side: the roll, the service records, and the company's weekend attendance and leave state.
The differences come out quickly because the account was nearly square to begin with, kept current through the week. The Friday discharge, K0709, is in the records as off strength and is not present, but is still carried on the roll: a departure not struck. She verifies the discharge authority and strikes the line, taking held to twenty-nine. The Friday joiner, K0742, is in the records as attested and is present this morning, but has no roll line: a joining not entered. She verifies the attestation authority and adds the line, taking held back to thirty. The two faults cancel in the head count, which is exactly why a lazy reconciliation, one that only checks the total, would have missed both and reported a thirty that was right by accident and wrong in substance. Now the named account is true, not just the number.
Then she does the further work command actually needs. Of the thirty held, she walks the availability state: two returned from leave and are available again, one went sick on Sunday and is not, and two others remain on leave from last week. So thirty held, three not available this week, twenty-seven available. She sets the return in battalion's fixed form, held against establishment with the availability broken out, dates it, signs it as having rendered it, and takes it to the Officer Commanding to authorise. It reaches battalion at twenty to ten, on time and true.
The return that goes up tells battalion the truth twice over: a force fully held at thirty against thirty, with a correctly recorded roll behind the figure rather than a discharged man and a missing joiner cancelling in the dark, and twenty-seven available this week rather than a held thirty masquerading as ready. Battalion plans the week on that. The whole of the NCO's value was in the twenty minutes of reconciliation she ran before the suspense rather than the rounding-up she could have done in two. On time and true, because she kept the account square through the week and squared it once more before she let the figure leave her hands.
Check Your Understanding
- Explain what a routine return is and why command depends on returns to keep it informed, using the ideas of "routine" and "rendered". Name the three core personnel returns covered in this lesson, say what each one answers and where its figures are drawn from, and explain the difference between a routine return and an occasional report.
- Explain what the strength account is and the three things that must agree for it to be square. Describe how the account is reconciled before a strength return is rendered, name the two kinds of difference that surface when a departure or a joining has not been recorded, and explain why the order must always be reconcile first, render second.
- Explain the administrative battle rhythm and how returns sit within it, including the loop by which returns lead to meetings, decisions, orders, and the events that change the strength. Then explain why a return must be on time as well as true, and what specific harm a return does when it is late, and when it is on time but rendered from an unreconciled account.
Reflection (write a short paragraph): This lesson sets two demands against each other that will pull at you all your administrative life: a return must be true, and it must be on time, and the pressure of a deadline tempts you to buy the second by sacrificing the first, rendering fast from an account you have not squared. Think honestly about which pull you feel more strongly, the fear of being late or the discomfort of an awkward figure, because that tells you where your own risk lies. Then think about why the disciplined answer is not to choose between true and on time but to keep the strength account square continuously, through the week, so that squaring it once more before the suspense is quick and both demands are met without a contest. Describe one habit you could build now, in any account or record you keep, that would let you meet a deadline with something true rather than something merely finished, so that command always plans on a picture you have earned the right to send.
Summary
- Returns and reports are how the orderly room keeps command informed. A return is a routine report of figures, rendered up the chain on a set cycle in a fixed form, so command always holds a current account without having to ask. A report in the wider sense is any information rendered up; occasional reports go up as events demand, outside the cycle. Both close the distance between the strength on the ground and the command that plans for it.
- The three core personnel returns are the strength return (how many held against establishment, and of those available), the leave return (who is away on leave), and the training state (the trained strength, drawn from the ADM 220 training record). Each is rendered on its cycle, in the form the higher headquarters wants, from a source made current and reconciled first.
- The strength account is the running, reconciled account of who is on strength, kept square so that the nominal roll, the service records, and the people on the ground all agree. Reconciliation is run on rhythm and always before a strength return: walk the roll against the records and the ground, find each difference (a departure not struck, a joining not entered, a record that does not match), run it down, and correct it. Reconcile first, render second.
- The administrative battle rhythm is the routine cycle of reports, orders, and meetings by which a headquarters runs. Returns sit within it on their cycles and suspenses, and the rhythm closes a loop: returns feed the meetings, the meetings feed decisions, decisions become orders, orders generate the personnel events that change the strength, and the strength feeds the next returns. An orderly room run to rhythm keeps command informed without being chased.
- A return must be on time as well as true. A true return rendered late is a picture command did not have when it had to decide; a return that is on time but drawn from an unreconciled account is fast and false and misleads command because it was trusted. The answer is to keep the account square continuously so both demands are met, and to render honestly, because careers, entitlements, and operations ride on what you send up. This is the integrity of LDR 420 applied to returns.
- This lesson builds out the returns cycle introduced in Lesson 01 (the personnel picture, the nominal roll, and the strength return) and reports the picture that Lessons 02 and 03 keep changing (joinings and departures, promotions, appointments, and postings). It connects to ADM 220 (the training record behind the training state), PME 210 (the service writing in which returns and reports are set down), CIS 220 (the data-protection care owed to personal data in any return), and LDR 420 (the integrity an accurate, on-time return demands). It leads on to ADM 310 (Orderly Room and Headquarters Administration), where the battle rhythm and the returns up the chain are the daily work of running a headquarters.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia