Design preview · adopts the Kaharagian design system
An official training service of the State of the Kaharagians
ADM 310 Orderly Room and Headquarters Administration
Lesson 4 of 10ADM 310

Consolidating Returns: the Picture Command Needs

Lesson Overview

A commander cannot see the whole unit at once. They cannot count every member on parade, read every training record, walk every store, and hold it all in their head in one true picture. They rely instead on the headquarters to do that work for them, to gather the many separate records the unit keeps and turn them into a few clear summaries they can act on: how many people are on strength and fit, how the unit's training stands, what stores and equipment are held and serviceable. This lesson is about how those summaries are built. It is about the headquarters as the place where the unit's returns are consolidated into the picture command needs, and about the Orderly Room NCO who does the consolidating: turning many separate records into one trustworthy summary, made accurate and made timely.

The work has two halves, and both matter. The first is the assembly itself: drawing the strength state from the personnel records you met in ADM 210, the training state from the course records of ADM 220, the logistics state from the stores accounts of the LOG stream, and more, and bringing them together into one consolidated unit-state picture without losing, double-counting, or muddling the numbers. The second is the judgement that must run through the assembly, captured in one hard principle: garbage in is garbage out. A summary is only ever as true as the records it is built from, so the consolidator does not simply compile what arrives; they check it. They know what the numbers should look like, they question what does not add up, and they go back to the source rather than passing a doubtful figure up the chain. A neat summary built on bad data is more dangerous than no summary at all, because command believes it.

This is the knowledge layer. Reading will teach you what the returns are, how they feed one picture, and the checks that keep that picture honest, but the hands-on work this feeds, pulling a real strength state from the records, reconciling figures that do not match, building a consolidated return from live data, and presenting it to a commander, is practised and signed off in person where supervision allows, in a working orderly room. By the end you will be able to explain what it means to consolidate returns and why the headquarters is where it happens; name the main returns that feed the picture command needs and the records and courses each draws from; build a consolidated unit-state summary from several separate returns without losing or double-counting; apply the "garbage in, garbage out" principle by checking returns at the point of consolidation rather than merely compiling them; recognise the common errors that corrupt a return and the checks that catch them; and explain why accuracy at the source and a checking consolidator are what make the commander's picture one they can safely act on.

Key Terms

  • Return: a structured report of a defined state of the unit at a point in time, rendered to a deadline: a count, a list, or a table answering a standing question, such as "who is on strength" or "what is held". Returns are the raw material the picture is built from.
  • Consolidation: the act of bringing several separate returns or records together into one summary, reconciling and combining them so that the whole is shown clearly and correctly in one place.
  • The picture command needs: the small set of consolidated summaries a commander relies on to understand and act on the state of the unit, chiefly its strength, its training, and its logistics state, made accurate and timely.
  • Strength state: the personnel picture, from ADM 210: how many members are on strength, how many are present and available, and how many are accounted for as absent, on leave, sick, detached, or otherwise non-effective.
  • Training state: the qualification and readiness picture, from ADM 220: which members hold which courses and qualifications, and therefore what the unit can field, against what it is required to hold.
  • Logistics state: the stores and equipment picture, from the LOG stream: what is held, what is serviceable, and what is short or due, drawn from the stores accounts.
  • Unit-state summary (consolidated return): the single combined picture that brings the strength, training, logistics, and other states together for the commander on one sheet or screen.
  • Source record: the original, authoritative record a return is drawn from, such as a service record or a stores ledger; the return is only ever as true as its source.
  • Garbage in, garbage out: the principle that a summary can be no better than the data fed into it; a wrong figure at the source becomes a wrong figure in the picture, however neatly it is presented.
  • Reconciliation: checking that two records which should agree actually do, and resolving the difference where they do not, before a figure is passed up.
  • Effective and non-effective: the distinction, in a strength state, between members available for duty (effective) and those accounted for but not available (non-effective): on leave, sick, detached, under training away, and the like. The two must add up to the total on strength.
  • As-at (currency stamp): the date and time a return is true for; a return without an as-at date cannot be trusted, because the state it reports is always changing.

What it means to consolidate, and why the headquarters does it

Consolidation is the act of turning many records into one picture. The unit holds a great deal of recorded fact, scattered by design across the records that hold it best: every member's service record, the leave and sickness entries, the course records, the stores ledgers, the nominal rolls. Each of these is the right home for its own detail, but none of them, on its own, answers the question a commander actually asks, which is not "what does Private A's record say" but "how many of my people can I field, trained for what, with what to do it". Consolidation is the work of reaching across all those separate records and assembling from them the few clear summaries that answer that question. It is the headquarters turning detail into a picture.

The headquarters is where this happens, and that is not an accident of where the desks are. The headquarters is the one place that sees across the whole unit. A section commander knows their own section; a stores person knows the stores; the personnel clerk knows the personnel records. None of them sees the whole, and none of them should be asked to, because their job is to keep their own part right. The headquarters sits above all of them, receives each part as a return, and is the only place positioned to combine the parts into a whole. The Orderly Room NCO, running the hub where the returns come together, is therefore the natural consolidator: not because they hold the detail, but because they hold the position from which the whole can be seen and assembled.

Two qualities make a consolidated picture worth anything, and the headquarters owes both. It must be accurate, because command acts on it and a wrong picture leads to a wrong decision. And it must be timely, because a true picture of last week is a false picture of today; a unit's strength and stores change daily, and a summary that is right but late is reporting a state that no longer exists. The battle rhythm of Lesson 02 exists in large part to serve this: the returns fall due on a cycle, are consolidated to a deadline, and reach command in time to be acted on. Accurate and timely are not two competing virtues to be traded off; the headquarters must deliver both, and the discipline of this lesson is how.

   MANY RETURNS  ->  ONE PICTURE COMMAND NEEDS

   SOURCE RECORDS              RETURNS                CONSOLIDATED
   (where detail lives)        (rendered to HQ)       (one summary)

   service records,    \
   leave & sick,        > ---> STRENGTH STATE  --\
   nominal rolls       /        (from ADM 210)    \
                                                   \
   course & qual       \                            \
   records,             > ---> TRAINING STATE  ------>  UNIT-STATE
   pathway tracking    /        (from ADM 220)    /     SUMMARY
                                                  /      (for the
   stores ledgers,     \                         /       commander,
   equipment cards,     > ---> LOGISTICS STATE -/        accurate
   serviceability      /        (from LOG)               and timely)
                                                  ^
   other returns ----------> (vehicles, comms,  --/
                              attachments, etc.)

   The HQ is the only place that sees ACROSS all of these. The
   Orderly Room NCO REACHES into each, draws the return, and
   COMBINES the returns into one picture. Detail stays in the
   source records; the picture is the summary built FROM them.

The returns that feed the picture

The picture command needs is built from a small number of main returns, each drawn from records you have already met, and it is worth knowing each one, what it answers, and where it comes from. The first is the strength state, the personnel picture, drawn from the records of ADM 210. It answers how many members the unit holds on strength, how many of those are present and available for duty, and how the rest are accounted for. Its discipline is the split between effective and non-effective: every member on strength is either available, or accounted for as on leave, sick, detached, away under training, or otherwise unavailable, and the two must add back up to the total on strength. A strength state where the parts do not sum to the whole is wrong on its face, and the consolidator catches that before anyone else sees it.

The second is the training state, the qualification picture, drawn from the course and qualification records of ADM 220 and the College's pathways. It answers what the unit can actually field: which members hold which courses and qualifications, how many qualified people the unit has against what it is required to hold, and where the gaps are that the next course must fill. A unit may be at full strength on the personnel return and still unable to do its task because the trained people are not there, and only the training state shows that. It is built directly on the training records ADM 220 teaches, which is why those records being right matters far beyond the individual whose course they record. The third is the logistics state, the stores and equipment picture, drawn from the stores accounts of the LOG stream. It answers what the unit holds, what of it is serviceable and ready, and what is short, unserviceable, or due, drawn from the stores ledgers and equipment records. Beyond these three sit other returns the picture may need, vehicle and communications states, attachments and detachments, and the like, each the same in principle: a defined question, drawn from a source record, rendered to a deadline.

What every one of these returns shares is that it has a source record behind it and an as-at date on it. The return is not the truth; it is a report of the truth as held in the source record, true as at a stated moment. This is why the as-at stamp is not a formality. A strength state is right for the morning it was pulled and begins ageing the instant a member goes sick or returns from leave; a logistics state is right until the next issue or receipt. A return without an as-at date claims a permanence it does not have, and a consolidator who combines returns of different dates without noticing has built a picture that was never true at any single moment. Every return carries its as-at; the consolidated summary carries its own, and the honest consolidator makes sure they are close enough together to mean something.

Garbage in, garbage out: why the consolidator checks

Here is the principle that this whole lesson turns on, and it is worth stating as plainly as it deserves: garbage in, garbage out. A consolidated picture can be no better than the returns it is built from, and a return can be no better than the records behind it. If a section renders a strength figure that is wrong, and the consolidator simply adds it in, the error does not stay small and local; it is now baked into the unit's picture, presented neatly to command with all the authority of a headquarters summary, and command will act on it. A wrong figure does not announce itself. Once it is inside a tidy total, it looks exactly like a right one. The danger of consolidation is precisely that it makes data look trustworthy, so a careless consolidator launders bad numbers into a respectable-looking lie.

This is why the consolidator's job is to check, not merely to compile. Compiling is mechanical: take the figures that arrive and add them up. Any clerk can compile, and a spreadsheet can compile faster. Checking is the judgement that earns the Orderly Room NCO their place at the hub. The consolidator knows roughly what the numbers should look like, so a figure that is suddenly far off draws their eye. They know the internal sums that must hold, so they test them: effective plus non-effective must equal total strength; this month's strength should be last month's plus joiners minus leavers; the people shown qualified cannot exceed the people on strength. They reconcile returns that should agree against each other and against the source record, and where two do not match, they do not pick the one they like or split the difference; they go back to the source and find out which is right. The consolidator who checks turns a heap of returns into a picture command can rely on; the one who only compiles turns it into a guess with a header on it.

When a check fails, the discipline is to go back, not to guess and not to bury. A figure that will not reconcile is queried at its source: the section that rendered it, the clerk who keeps the record, the ledger it came from. Sometimes the return was wrong and the source is right; sometimes the source itself is wrong, which is a more serious finding and one that must be put right at the source so the error does not return next month. Either way the resolution is recorded, so that anyone reading the consolidated return later can see that the figure was questioned and on what basis it was settled. And accuracy at the source is the long game: the consolidator who keeps sending bad figures back, every time, teaches the sections and clerks that the headquarters checks, and over time the returns that arrive get cleaner, because everyone knows a careless figure will be caught and bounced. A consolidator who waves everything through teaches the opposite.

   THE CONSOLIDATOR'S CHECK  ·  compile is not enough

   RETURN ARRIVES
        |
        v
   COMPILE?  (just add it in)  -----------> [ DANGER ]
        |                                   a wrong figure, now
        |  no: CHECK first                  laundered into a tidy
        v                                   total, looks exactly
   +--------------------------------+       like a right one
   | Does it reconcile?             |
   |  - effective + non-eff = total |
   |  - this month = last +/- moves |
   |  - qualified <= on strength    |
   |  - return agrees with source   |
   +--------------------------------+
        |                  |
     YES|               NO |
        v                  v
   ACCEPT into        GO BACK TO SOURCE
   the picture        - query the section / clerk / ledger
        |             - find which is right (return or source?)
        |             - correct AT SOURCE if the record is wrong
        |             - record how it was settled
        |                  |
        +<-----------------+
        v
   CONSOLIDATED SUMMARY  (every figure either reconciled
                          or queried and resolved, never
                          guessed and never buried)

   GARBAGE IN  ->  GARBAGE OUT.  The check is the only thing
   standing between a bad source figure and the commander's
   decision built upon it.

Building the consolidated summary

With the returns gathered and checked, the last step is to assemble them into the one summary command will read, and the way it is built is itself part of keeping it honest. The consolidated unit-state summary brings the strength, training, and logistics states, and any others command needs, onto one sheet or screen, each shown clearly, with the unit's headline figures visible at a glance and the detail available beneath. It carries one as-at date for the whole, chosen so that the returns behind it are all current to roughly the same moment, because a summary stitched from a fresh strength state and a fortnight-old logistics state is a picture that was never true at once. The aim is that a commander can read the top of it in a minute and know where the unit stands, and read down into it when they need to know why.

A good summary shows not only the numbers but enough around them to be acted on. It shows the total and its parts, so the commander sees both that the unit is, say, forty-two on strength and that thirty-one of those are effective and where the other eleven are. It shows the figure against what it should be where there is a requirement, so a training state shows not just twelve members holding a qualification but twelve against a required sixteen, because the gap is what command acts on. And it shows movement where movement matters, so a strength state that is down on last month says so, prompting the question of why. None of this is decoration; each addition is there because it turns a number command would otherwise have to interpret into one they can act on directly. The consolidator builds for the reader, not for the file.

   CONSOLIDATED UNIT-STATE SUMMARY  ·  as at 0800, 06 Jun 2026

   +=====================================================================+
   |  STRENGTH STATE            (from ADM 210 personnel records)         |
   |  On strength ........ 42                                            |
   |    Effective ........ 31   (available for duty)                     |
   |    Non-effective .... 11   = leave 5 · sick 3 · detached 2 · crse 1 |
   |    [check: 31 + 11 = 42  OK]   Last month 40 (+3 join, -1 leave) OK |
   +---------------------------------------------------------------------+
   |  TRAINING STATE            (from ADM 220 course & qual records)     |
   |  Medic-qualified ...  4 / 6 required      gap: 2  (course Sep)      |
   |  Signals-qualified .  9 / 8 required      OK                        |
   |  Driver-qualified .. 14 / 12 required     OK                        |
   |    [check: none shown qualified exceeds 42 on strength  OK]         |
   +---------------------------------------------------------------------+
   |  LOGISTICS STATE           (from LOG stores accounts)              |
   |  Radios ............ 18 held / 16 svc / 2 u-s        short of need? |
   |  Vehicles ..........  4 held /  3 svc / 1 u-s (due back 09 Jun)     |
   |  First-aid sets .... 40 held / 40 svc                OK            |
   +---------------------------------------------------------------------+
   |  Notes: 1x radio u-s awaiting part. Medic gap is the standing       |
   |         shortfall; nominations for the Sep course requested.        |
   |  Consolidated by: Orderly Room NCO.  Source returns on file.        |
   +=====================================================================+

   ONE as-at date. Totals AND their parts. Held AGAINST required.
   Movement on last month shown. Internal sums CHECKED. The commander
   reads the top line in a minute and reads down for the why.

In Practice: An Orderly Room NCO builds the weekly unit state

It is the morning the weekly unit-state summary falls due, and Sergeant Owusu, the Orderly Room NCO, has the returns in front of him. The personnel clerk has rendered the strength state from the ADM 210 records; the training figures come from the ADM 220 course records; the stores person has sent the logistics state from the ledgers. His job now is not to staple them together and send them up. It is to consolidate them into the one picture his commander will act on, and to make sure that picture is true.

He starts with the checks, because a tidy total of bad figures is the thing he is paid to prevent. The strength state shows forty-two on strength, thirty-one effective, eleven non-effective. He tests the sum: thirty-one and eleven make forty-two, so the parts add to the whole. He tests it against last month: forty was the figure, three joined, one left, which gives forty-two, and it holds. The training state shows nine members signals-qualified, but the strength is forty-two and he knows the unit has never had nine signallers, so he stops. He queries the clerk, who finds two members were counted from an old course list and have since left; the real figure is seven. The source record was wrong, so Owusu has it corrected at source, not just on the return, so the error does not come back next week. The logistics state shows eighteen radios held but sixteen serviceable, and a note that one is awaiting a part; that reconciles, and he lets it stand.

Only now does he build the summary. He brings the three states onto one sheet, gives the whole a single as-at stamp of eight o'clock that morning so the picture is true at one moment, and shows each figure with its parts and against its requirement: strength with its effective and non-effective split, the medic qualification at four against a required six with the gap flagged and the September course noted, the corrected signals figure, the stores held against serviceable. He adds two lines of notes so the commander reads not just the numbers but what they mean: the medic shortfall is the standing gap, nominations for the next course have been requested. When the commander reads it, the top line tells them in a minute where the unit stands, and the detail beneath answers why. And because Owusu checked rather than merely compiled, the picture the commander acts on is one they can safely act on. Had he passed the nine signallers up unchecked, the unit would have been recorded as able to do something it could not, and someone might have been tasked on the strength of a figure that was never true.

Check Your Understanding

  1. A section renders a strength state showing 38 on strength, 30 effective, and 6 non-effective. Without going any further, explain what is wrong with this return, what internal check reveals it, and what the consolidator should do before this figure goes anywhere near the consolidated summary. Then explain why catching it at consolidation matters more than it might first appear.

  2. Explain the principle "garbage in, garbage out" in the context of consolidating returns, and use it to explain the difference between a consolidator who compiles and a consolidator who checks. Give two specific checks you would apply to a consolidated unit-state summary, and say what each one would catch.

  3. A commander is handed a single-page unit-state summary that shows only three headline totals: 42 on strength, 12 qualified, 18 radios. Explain why this is not yet the picture command needs, and describe at least three things you would add to make each figure one the commander can act on, drawing on what a good consolidated summary shows.

Reflection (write a short paragraph): Think of a time you relied on a summary, a total, a report, or a figure someone else had put together, and acted on it, only to find later that it was wrong because the underlying detail was wrong. What happened, and how did the neat presentation of the figure make it easier to trust than it deserved? How will the principle that a summary is only as good as its sources, and the habit of checking rather than just compiling, change how you handle information that other people will act on?

Summary

  • Consolidation is the act of turning many separate records into one picture: the headquarters reaches across the unit's records, draws each as a return, and combines the returns into the few clear summaries command needs.
  • The headquarters does this because it is the only place that sees across the whole unit, and the Orderly Room NCO is the natural consolidator, holding the hub where the returns come together.
  • The picture command needs is built from a small set of main returns: the strength state (from ADM 210), the training state (from ADM 220), the logistics state (from the LOG stream), and others, each drawn from a source record and stamped with an as-at date.
  • The picture must be both accurate and timely: command acts on it, and a true picture of last week is a false picture of today, which is why returns are consolidated to the battle-rhythm deadlines of Lesson 02.
  • Garbage in, garbage out: a summary is only as good as its sources, and consolidation makes bad figures look trustworthy, so the consolidator must check, not merely compile, testing the sums that must hold, reconciling against source records, and going back to the source when a figure will not reconcile.
  • A good consolidated summary shows totals and their parts, figures against requirement, and movement that matters, on one sheet with one as-at date, so the commander reads the top line in a minute and reads down for the why.
  • Builds on Lesson 02 · The Administrative Battle Rhythm (the deadlines returns are consolidated to) and Lesson 03 · Correspondence, Minuting, and Tasking (the flow that delivers returns on time). Leads into Lesson 05 · Supervising Clerks and Safeguarding Records (leading the clerks who render the returns) and Lesson 06 · The Headquarters in Support of Command and People. Connects to ADM 210 · Personnel Administration (the strength state), ADM 220 · Course Records and Qualification Tracking (the training state), LOG 201 · Logistics and Stores Accounting (the logistics state), PME 210 · Basic Staff Duties and Written Orders (reports at scale), and LDR 420 · Command Responsibility and Ethical Leadership (the integrity of the figure command acts on).

Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia

Lesson 4 · Knowledge Check

Question 1 of 3

What is consolidation?