Royal Army College

Lesson Overview

The last lesson taught the workflow that carries a single piece of business from arrival to a clean conclusion. But an orderly room never handles one piece of business at a time. It handles dozens at once, all at different stages: an application waiting on a commander's recommendation, a return due at the end of the week, a query awaiting a reply from another unit, a decision made but not yet notified, a record change waiting on an order to be published. Each of these is an action in flight, and the danger is not that any one of them is hard, but that one of them, quietly, gets forgotten. The reply that was never chased, the return that slipped past its date, the application that sat in a tray behind a busier one, these are the failures that an orderly room is judged by, and they almost never come from a decision; they come from an action that no one was tracking. This lesson is about the system that makes sure that never happens: the suspense system, the orderly room's way of holding every open action until it is done.

The lesson takes two joined ideas. First, the suspense itself: the principle that every action which is not finished and cannot be finished now is placed under a date by which it must be progressed or completed, and brought back to attention on that date, so that nothing waits silently and nothing falls past its deadline unseen. A suspense is a promise the orderly room makes to itself that an open action will be looked at again on a known day, rather than left to be remembered by luck. Second, the bring-up system that delivers on that promise: the diary, the tickler, or its digital equivalent, that surfaces each action on its due date, together with the disciplines of suspensing every action when it is opened, chasing what is overdue, and closing an action only when it is genuinely done. This is the difference between an orderly room that completes its work and one that merely starts it.

This is the knowledge layer. The hands-on work this feeds, putting an action under suspense, running a bring-up check, chasing an overdue action, and closing one out properly, is practised and signed off in person where supervision allows, in a working orderly room, because tracking work to completion is a habit built by doing it daily. By the end you will be able to explain why an orderly room needs a suspense system and what failure it prevents; place every open action under a suspense date when it cannot be completed at once, and choose a sensible date; run a bring-up system so that each action surfaces on its due date and nothing waits unseen; chase an overdue or stalled action and escalate it before it becomes a failure; and close an action only when it is genuinely complete, distinguishing a finished action from one merely set aside.

Key Terms

Suspense: the discipline of holding an open action under a date by which it must be progressed or completed, so that an action which cannot be finished now is not forgotten but brought back to attention on a known day.
Suspense date (due date): the date set on an action for when it must be done or chased, chosen to leave enough time to act before any hard deadline behind it.
Bring-up (BU) system: the mechanism, a diary, a tickler file, a digital reminder list, that surfaces each suspensed action on its due date, so the orderly room is reminded of what falls due without having to remember it.
Tickler / suspense diary: the dated index of open actions, organised by due date, that the bring-up system works from; checked at the start of each working day.
Open action: any piece of business that has been started but not yet concluded; it remains the orderly room's responsibility until it is genuinely closed.
Overdue action: an action whose suspense date has passed without it being completed; a signal to chase, escalate, or re-suspense, never to ignore.
Chasing (follow-up): actively pursuing an action that is waiting on someone else, a recommendation, a reply, an order, so that a stalled action is moved rather than left to drift.
Escalation: raising a stalled or at-risk action to a higher authority when chasing alone will not move it in time, so a looming failure is surfaced while it can still be prevented.
Closing an action: concluding an action only when it is genuinely done, decided, recorded, notified, filed, and removing it from suspense; a half-done action is never closed.
Deadline: the hard date by which an external requirement must be met, a return due up the chain, a reply owed; the suspense date is set earlier than the deadline so there is room to act.

Why nothing can be left to memory

The first thing to accept is that memory is not a system, and an orderly room run on memory will, sooner or later, drop an action. Not because the people are careless, but because the human mind cannot reliably hold dozens of open actions, each with its own date and its own next step, across days of constant interruption. The busy clerk remembers the action in front of them and the loudest one shouting; the quiet action waiting on a reply that has not come, the return due in nine days that nothing is yet pushing, these are exactly the ones memory loses, because nothing is prompting them. And the actions memory loses are not random: they are the ones with no immediate pressure, which is to say the ones whose deadline is still far enough off to be ignored, right up until the day it is suddenly too late. An orderly room that relies on remembering will be reliable on the urgent and unreliable on the merely important, which is the worst possible pattern, because the merely important is most of the work.

The suspense system exists to take the burden off memory entirely. Its premise is simple: the orderly room does not try to remember its open actions; it writes them down under dates and lets the bring-up system remind it. Every action that cannot be finished on the spot is given a date and entered, and from then on the system, not the clerk's recall, is responsible for surfacing it at the right moment. This is the same instinct as the registry in Lesson 03, where a document is recorded so it cannot be lost; here an action is recorded so it cannot be forgotten. The relief this gives is real and practical: a clerk who knows that every open action is safely under a suspense can put one down to deal with another without fear, because the system is holding the rest. Freedom from having to remember everything is what lets the orderly room handle many things at once without dropping any of them.

   WHY MEMORY FAILS, AND THE SUSPENSE SYSTEM CATCHES

   MEMORY remembers...        but LOSES...
   - the action in front       - the action waiting on a reply
   - the loudest / urgent      - the return due "next week"
                               - the decision made but not notified
        |                            |
        |  the lost ones share one thing: NOTHING is prompting them
        |  (no immediate pressure) -> ignored until suddenly too late
        v
   SUSPENSE SYSTEM: don't remember actions -> WRITE THEM under DATES
        every open action -> a suspense date -> entered in the BU diary
        the SYSTEM surfaces it on its day, not the clerk's recall
        |
        v
   RESULT: reliable on the IMPORTANT, not just the urgent; a clerk
   can put one action down to handle another WITHOUT fear of dropping
   it, because the system is holding the rest.

Suspensing an action and setting the date

Putting an action under suspense is a small act done at a precise moment: whenever an action cannot be completed now, before it is set down, it is given a suspense date and entered in the bring-up system. The trigger is the words "cannot finish this now," which arise constantly, the application that needs the commander's recommendation before it can be staffed, the query that has been sent to another unit and now waits on a reply, the record change that waits on the next order to be published, the return that cannot be compiled until month end. Each of these is about to leave the clerk's hands or attention, and that is exactly the moment it must be suspensed, because an action set down without a suspense is an action trusting to luck. The rule is unforgiving and simple: nothing open is set down without a date on it.

Choosing the date is a matter of judgement, and the principle is to work back from the deadline and leave room to act. The suspense date is not the deadline; it is earlier, set so that when the action surfaces there is still time to do what it needs. An action waiting on someone else's reply is suspensed for a date by which, if no reply has come, there is still time to chase it and get an answer before it bites, not for the day the answer is finally needed. A return due at month end is suspensed for several days before, so it can be compiled and checked without a scramble. The harder or more uncertain the action, or the more it depends on others, the more margin the suspense date leaves, because the things that depend on other people are the things most likely to need chasing. A well-chosen suspense date is the difference between surfacing an action while it can still be saved and surfacing it the day it has already failed. And an action can be re-suspensed: when it surfaces but still cannot be completed, it is progressed as far as it can be, then given a fresh date and put back, so it keeps coming round until it is done.

The bring-up system and closing the loop

A suspense is only a promise; the bring-up system is how the promise is kept. The bring-up system is whatever mechanism surfaces each suspensed action on its due date, a dated diary, a card tickler with a slot for each day, a digital reminder or task list, and its form matters far less than the discipline of using it. The central habit is the daily bring-up check: at the start of each working day, the orderly room looks at what falls due today, and works it. Everything suspensed for that date comes up, and each is dealt with, completed if it now can be, chased if it is waiting on someone, escalated if chasing will not move it in time, or progressed and re-suspensed if it needs more time. The day's overdue actions, anything whose date has passed unfinished, are caught here too and not allowed to drift further. The daily check is the heartbeat of the system: do it, and nothing falls past its date unseen; skip it, and the suspense dates become as forgotten as the actions they were meant to protect.

Two disciplines complete the loop. The first is chasing and escalation: an action waiting on someone else does not progress by itself, and when its suspense surfaces it unanswered, the orderly room chases, a reminder, a call, a follow-up, and if chasing will not move it before the deadline, escalates it to someone who can. The point of suspensing early is precisely to make room for this: a stalled action surfaced with time in hand can be saved by a chase; the same action surfaced on its deadline can only be reported as a failure. The second is closing the loop honestly: an action is removed from suspense only when it is genuinely complete, decided, recorded, notified, and filed as Lesson 06 requires, not when it has merely been worked on or set aside. The temptation, on a busy day, is to clear an action from the diary because it has been touched; that is how half-done actions vanish, looking closed but leaving a member without an answer or a return unsent. The rule is the mirror of the suspense rule: as nothing open is set down without a date, so nothing is closed until it is truly done. Between those two rules, every action is held from the moment it is opened to the moment it is finished, and nothing falls through.

   THE BRING-UP SYSTEM  ·  closing the loop, every day

   DAILY BRING-UP CHECK (start of each working day)
        |  pull everything suspensed for TODAY + any OVERDUE
        v
   FOR EACH ACTION:
        can it be COMPLETED now?  --> do it -> CLOSE (truly done:
        |                                        decided, recorded,
        |                                        notified, filed)
        waiting on someone? -------> CHASE (reminder / call / follow-up)
        |        chasing won't move it in time? --> ESCALATE
        still needs time? ---------> PROGRESS as far as possible,
                                     then RE-SUSPENSE (fresh date)

   TWO RULES THAT BOUND EVERY ACTION:
     OPEN:  nothing is set down WITHOUT a suspense date.
     CLOSE: nothing is removed from suspense until it is TRULY done.
        (touched / set aside  is  NOT  closed)

   Skip the daily check and the suspense dates are as forgotten as
   the actions they were meant to protect.

In Practice: The return that did not slip

Lance Corporal Sefu runs the orderly room's suspense as a daily habit, and one quiet week shows why. Three actions are in flight, none of them urgent yet, which is exactly why they are dangerous. A strength return is due up the chain at the end of the month. A query about a member's prior service has been sent to another unit and awaits a reply. And a member's posting, decided by command, needs a Part II order published before it can be posted to the record. None of the three is pressing today, so on an orderly room run by memory all three would sit unprompted until one of them suddenly failed. Sefu does not run on memory. Each was suspensed the moment it could not be finished: the return for five days before its deadline, so there is room to compile and check it; the query for a week out, by which time a reply should have come; the posting for the day the next orders are drafted.

The bring-up does its work. When the query's suspense surfaces and no reply has come, Sefu does not shrug and wait; he chases the other unit with a follow-up, with days still in hand because he suspensed early, not on the deadline. A polite reminder brings the answer, and the action moves. When the return's suspense comes up five days out, he compiles it without a scramble, reconciles it against the records behind it as the accuracy standard of Lesson 10 requires, and has it ready well before it is due. The posting's suspense surfaces on orders-drafting day, the order is published, and only then, with the proper authority in hand, does he post the change to the record and close the action. Each one he closes only when it is genuinely done, recorded and filed, not when it has merely been touched.

The month ends with all three concluded on time and nothing dropped, and the value is precisely that nothing dramatic happened, no missed return, no unanswered query discovered too late, no posting stuck because an order was forgotten. Down the corridor, a clerk who kept his open actions in his head has a strength return go up two days late because nothing prompted him until the deadline had already passed, and a query he genuinely meant to chase surfaces only when the member it concerned is held up for want of the answer. Both had the same actions in flight. One wrote them down under dates and let the system bring them up; the other trusted his memory, and memory, as it always eventually does, lost the quiet ones.

Check Your Understanding

Explain why an orderly room cannot safely run its open actions on memory, and which kind of action memory is most likely to lose. What does the suspense system do instead, and how does writing actions down under dates free a clerk to handle many things at once?
Describe how and when an action is placed under suspense, and explain why the suspense date is set earlier than the deadline rather than on it. What does it mean to re-suspense an action, and when is that the right thing to do?
The bring-up system has a daily check at its heart. Explain what the daily bring-up check does, the four things that can happen to an action when its suspense surfaces, and why an action is closed only when it is genuinely done. What goes wrong when a clerk clears an action from the diary merely because it has been touched?

Reflection (write a short paragraph): Think about how you currently keep track of things you have started but cannot finish at once, replies you owe, tasks waiting on others, deadlines still far off. Which of them tend to slip, and are they the urgent ones or the quietly important ones? How would running your own work on a suspense and bring-up discipline, nothing set down without a date and nothing closed until it is truly done, change which things you drop, and what does that tell you about why an orderly room cannot rely on good intentions alone?

Summary

An orderly room handles many actions at once, all at different stages, and its characteristic failure is not a hard decision but a forgotten action: the reply never chased, the return slipped past its date, the application left in a tray. These come from actions no one was tracking.
Memory is not a system: the human mind reliably holds the urgent and loses the quietly important, the actions with no immediate pressure, right up until their deadline is suddenly too late. The suspense system takes the burden off memory entirely.
Suspense every open action that cannot be finished now: the moment an action is set down, it is given a suspense date and entered in the bring-up system. Nothing open is set down without a date on it.
Set the suspense date earlier than the deadline, working back so there is room to act, with more margin for actions that are harder or depend on others; re-suspense an action that surfaces but still cannot be completed, so it keeps coming round until it is done.
Run the bring-up system through a daily check: surface everything due today and any overdue, and for each, complete it, chase it, escalate it, or progress and re-suspense it. The daily check is the heartbeat; skip it and the suspense dates are forgotten too.
Chase actions waiting on others while there is still time, and escalate when chasing will not move them in time; suspensing early is what makes a saving chase possible instead of a failure report.
Close an action only when it is genuinely done, decided, recorded, notified, and filed, never merely when it has been touched. As nothing open is set down without a date, so nothing is closed until it is truly complete.
Cross-references: extends the administrative workflow of ADM 201 Lesson 06 by holding every action to completion; mirrors the never-lose-a-document discipline of the registry in ADM 201 Lesson 03; reconciles returns before they go up to the accuracy standard of ADM 201 Lesson 10; and supports the timeliness on which ADM 210 (Personnel Administration) and ADM 310 (Orderly Room and Headquarters Administration) depend for returns and the command battle rhythm.

The Suspense System: Tracking Actions to Completion