Royal Army College

Lesson Overview

Staff work is easily misjudged. Some dismiss it as paperwork and procedure; others let it swell into an end in itself, generating reports and processes that serve the headquarters rather than the command. This lesson sets the matter straight at the start, because the rest of the course follows from it. The staff exists to serve the commander and the command, and every piece of staff work is judged by one thing: does it help the command achieve its purpose, not whether it is correctly formatted or impressively long.

This course is written for a small humanitarian home-defence force, where a dedicated staff is rare. More often an officer and a few others do the staff work alongside their other duties. That makes the principles matter more, not less: there is no large staff to absorb waste, and no spare capacity for work that serves no one. It also means the staff officer is usually a commander too, so these skills belong to every officer, not a separate staff caste.

By the end you will be able to explain what the staff and the headquarters are and the single purpose they serve; state the principle that staff work serves command and the test that follows; describe the main functions a staff performs; explain why staff work must be kept simple, and the danger of it becoming an end in itself; and understand the staff officer as servant and enabler of the commander's decision, never a substitute for it.

Key Terms

Staff: the officers and others who assist a commander in exercising command, by gathering and presenting information, preparing plans and orders, and coordinating the command; helpers, not commanders.
Headquarters: the place and organisation from which a command is directed; the staff at work, with the means (communications, records, the commander's presence) by which command is exercised.
The service of command: the principle that the staff and headquarters exist solely to serve the commander and the command, and that all staff work is judged by whether it helps the command achieve its purpose.
Staff functions: the main kinds of work a staff does: gathering and presenting information, helping prepare decisions, turning decisions into orders, coordinating execution, and keeping records.
The staff officer: an officer doing staff work; in a small force usually also a commander, who serves by doing the work that enables the commander's decision and the command's coordinated action.
Simplicity in staff work: doing staff work as plainly and economically as the task allows, since complexity burdens the command rather than serving it.
Staff work as an end in itself: the failure in which a headquarters generates process and reports that serve the form or itself rather than the command.

What the staff and the headquarters are

The staff are the people who help a commander exercise command. No commander can personally gather all the information, work out every detail of a plan, write every order, coordinate every part, and track everything at once. Others do that work on their behalf and under their direction. Those people are the staff; what they do is staff work. The headquarters is where it happens: the staff at work together, with the communications that carry orders out and reports in, the records that hold the command's information, and usually the commander's own presence. In a large army the staff is a sizeable specialised body. In a small home-defence force it may be an officer and a few others, the headquarters a vehicle, a tent, or a room with a radio and a map. The scale differs enormously; the thing is the same.

What matters most about both is what they are for. The staff and headquarters have no purpose of their own. The staff does not command; it serves the commander who does. The headquarters does not exist for its own sake; it exists to help the command succeed. Hold this firmly, because much that goes wrong in staff work comes from forgetting it, when a staff begins to serve its own procedures, appearance, or convenience instead of the command. Everything that follows is the working out of this one idea.

The principle: staff work serves command, and the test that follows

From the nature of the staff comes the governing principle of the course: staff work serves command, and every piece of it is judged by whether it helps the command achieve its purpose. This is the test to apply to any staff work, your own or another's. Does this help the commander decide, the command prepare, the soldiers act, the picture stay current? If so, it is good staff work, however humble. If not, it is not, however correct its format or impressive its volume.

The test catches two failures. The first is staff work that is correct but useless: a report perfectly formatted but holding nothing the commander needs, a plan elaborately worked but answering the wrong question. Usefulness is the standard, not correctness of form. A humble note that tells the commander the one thing they needed beats a polished document that does not. The second is staff work that serves the staff rather than the command: process generated for the headquarters' own convenience, reports required because the form requires them, work that makes the headquarters feel busy while burdening the command.

Apply the test constantly, to the work you produce and the work you require of others, and cut what fails it. This is vital in a small force, which has no capacity to spare. Every hour a small staff spends on useless work is stolen from work that would have served the command.

The functions the staff performs

The staff serves command through several interlocking functions. Together they are what staff work consists of, and the course teaches each in turn.

The first is gathering and presenting information. A commander buried in raw, unsorted information is no better off than one with none. The staff sorts the flood and presents the few things the commander needs to know, clearly. The second is helping prepare decisions. The staff works the detail the commander has no time for, lays out factors and options, and does the analysis that informs the commander's judgement, but never decides; that is the commander's alone. The third is turning decisions into orders: once the commander has decided, the staff renders the decision into clear orders the command can act on (the written orders and orders process of Lessons 03 and 04). The fourth is coordinating execution: as the operation runs, the staff keeps the command's elements working together rather than at cross-purposes, and manages resources. The fifth is keeping records and information, so the command knows its own state, can account for what it has done, and has what it needs to hand.

These five are one service seen from different angles: enabling a commander to command a body larger and more complex than one person could manage.

   WHAT THE STAFF DOES FOR THE COMMANDER

   GATHER & PRESENT INFORMATION -- turn the flood into the few
        |                          things the commander needs to know
   HELP PREPARE DECISIONS -------- work the detail, lay out factors
        |                          and options (never decide)
   TURN DECISIONS INTO ORDERS ---- the commander's intent into clear
        |                          orders the command can act on
   COORDINATE EXECUTION ---------- keep the moving parts working
        |                          together, not at cross-purposes
   KEEP RECORDS & INFORMATION ---- so the command knows its own state
                                   and has what it needs to hand

   All one service: ENABLING a commander to command a body larger
   and more complex than they could personally manage.

Keeping it simple, and the danger of staff work for its own sake

The last theme matters most for a small force. Staff work must be kept simple, and it must never become an end in itself. These are two sides of one discipline, and both follow from the service of command.

Simple staff work is understood, done faster, less prone to error, and lighter on the command. Complex staff work, with its elaborate procedures and lengthy documents, costs time a small force does not have, multiplies the points at which things go wrong, and often obscures rather than clarifies. So do staff work as plainly as the task allows: the shortest order that conveys the intent, the simplest report that carries the information, the fewest records that hold what is needed. This is harder than it sounds. There is always a temptation to add, to make the document fuller and the process more thorough, and resisting it means asking whether each addition truly serves the command or merely pads the work.

The related danger is staff work becoming an end in itself. A headquarters that has lost its purpose generates reports because reports are required, follows procedure because it is procedure, all of it serving the form or its own sense of busyness rather than the command. This is insidious because it can look like diligence. A headquarters drowning the command in process may believe itself hard at work while failing its one purpose. The cure for both excess and self-service is the same: keep asking whether each piece of staff work helps the command achieve its purpose, and cut what does not. The purpose, not the procedure, is the point.

In Practice: Two Headquarters in a Flood

Two officers of the Royal Kaharagian Army each run the small headquarters of a company-sized element responding to a flood. Each has a staff of a few people working alongside their other duties. Both do the same job; they do it very differently, and the whole difference is whether they understand the service of command.

The first headquarters serves the command, simply. Incoming information, fragmentary and abundant, is sorted into the few things the commander actually needs. The orders that go out are short and clear, carrying the intent in a form the soldiers can act on under pressure. The reports it requires of its elements are the minimum needed to keep the picture current, because every extra return steals time from relief work. The records kept are the few the command needs. The whole headquarters is lean, fast, and useful, so the commander can command: well informed, intent reaching the soldiers clearly, the operation coordinated.

The second headquarters has lost the principle. Trying to be thorough, its officer has let the staff work become an end in itself. It demands detailed returns no one needs, stealing time from the relief. Its orders are long and elaborate, burying the intent the soldiers cannot hold under pressure. Raw information reaches the commander unsorted, so they are buried rather than informed. The records multiply beyond use. The headquarters feels busy and believes itself diligent, but it serves the form and its own thoroughness rather than the command, and the command is slower and less clear for it.

Same job, same small staff. The first holds the principle and keeps its work simple and useful; the second has let staff work become its own end and burdens the command it should serve. To run a headquarters well is to be the first kind.

Check Your Understanding

Explain what the staff and the headquarters are, and the single purpose they serve. Why is it accurate to say they have no purpose of their own, and why is holding that firmly the key to keeping staff work useful?
State the principle that staff work serves command, and the test that follows from it. What two failures does the test catch, and why is applying it especially vital in a small force?
Describe the main functions a staff performs and explain how they are one service, the enabling of command. Then explain why staff work must be kept simple, and why the danger of it becoming an end in itself is so insidious.

Reflection (write a short paragraph): This lesson judges staff work not by whether it is correctly formatted or thorough but by whether it actually helps the command achieve its purpose, and it warns that the instinct to be thorough can lead a headquarters to burden the very command it serves. Think about how you support others in any part of your life. Are you inclined to add, to make things fuller, or to keep them focused on what is actually needed? Be honest, because the urge to be seen as thorough is strong and feels like diligence. How often do you do something because it is the procedure or looks diligent, rather than because it helps? Describe one way you could begin asking, of any work you do for others, whether it truly serves the purpose or merely satisfies a form.

Summary

The staff are the people who help a commander exercise command; the headquarters is where they work, with the means by which command is exercised. The scale ranges from a large specialised body to an officer and a few others in a room with a radio and a map, but the thing is the same. Both have no purpose of their own: they exist to serve the command.
Staff work serves command, and every piece is judged by whether it helps the command achieve its purpose. The test catches staff work that is correct but useless, and staff work that serves the staff rather than the command. Apply it constantly; it matters most in a small force with no capacity to spare.
The staff serves through five interlocking functions: gathering and presenting information, helping prepare decisions (never deciding), turning decisions into orders, coordinating execution, and keeping records. These are one service: enabling a commander to command a body larger than one person could manage.
Keep staff work simple: simple work is understood, fast, and less error-prone, while complexity costs time a small force lacks and obscures rather than clarifies. Resist the temptation to add. The related danger is staff work becoming an end in itself, insidious because it looks like diligence while burdening the command.
The cure for both excess and self-service is one test: ask whether each piece of staff work helps the command succeed, and cut what does not. This principle governs the whole course, which teaches the craft in turn: service writing (Lesson 02), written orders and the orders process (Lesson 03), warning orders and the planning sequence (Lesson 04), reports and records (Lesson 05), and running a small headquarters (Lesson 06). It builds on Foundations of Military Leadership (LDR 201) and supports Command, Mission Command, and Decision-Making (LDR 410).

The Staff and the Headquarters: the Service of Command