Design preview · adopts the Kaharagian design system
An official training service of the State of the Kaharagians
ADM 201 Service Records and Registry
Lesson 5 of 10ADM 201

Routine Orders and Recording Personnel Events

Lesson Overview

In Lesson 02 you learned that the service record is the single trusted account of one member's service, and in Lesson 03 you learned how the registry keeps every document the force produces findable and accounted for. This lesson answers a question those two raised but did not settle: by what authority does anything ever get into a record at all? A promotion happens, a member is posted, a recruit attests. Each of those is a real event in a person's service, and each must end up in the record. But it must not get there because a clerk heard about it, or because someone said so in passing, or because it seemed true. It gets there because the unit has formally ordered it and published that order. The instrument that does this in the Commonwealth pattern is routine orders, and the part of them that carries personnel events is the Part II order.

Routine orders, also called daily orders, are how a unit promulgates its instructions and records its events. They split into two parts that do two different jobs. Part I orders carry instruction and routine: the duties for the day, the parades, the notices, the things the unit needs everyone to know and do. Part II orders carry personnel events with authority: promotions, appointments, postings, attestations, transfers, and the like, each published as a numbered entry that says what has happened, to whom, from what date, and on whose authority. The idea that holds the whole speciality together is this: a Part II order entry is the authority that updates the service record. An event becomes a record by passing through a proper order, not by rumour and not by a clerk's whim. Until the order is published, the event is not yet, administratively, true.

This is the knowledge layer. Reading will teach you the difference between Part I and Part II orders, why a Part II entry is the authority that moves an event into the record, and how a clear, correct order entry is drafted, but the hands-on work this feeds, raising an order entry from a proper authority, publishing it, and posting it to the record, 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 routine orders are and why a unit publishes them; distinguish Part I orders (instruction and routine) from Part II orders (personnel events recorded with authority) and place a given matter in the right part; explain why a Part II order entry is the authority that updates a service record, and why an event recorded without a proper order is not properly recorded at all; draft a clear, correct Part II order entry that states the event, the person, the effective date, and the authority; and trace the flow from authority, to order entry, to the record it updates, so that every change to a record can be proved back to the order that authorised it.

Key Terms

  • Routine orders (daily orders): the unit's published orders, issued on a regular cycle, by which it promulgates its instructions and records its events; the means by which what the unit has decided becomes known and becomes official.
  • Promulgate: to publish a thing formally so that it is officially known and takes effect; an order is promulgated when it is issued, not merely when it is drafted.
  • Part I orders: the part of routine orders that carries instruction and routine, the duties, parades, notices, and standing information the unit needs everyone to know and act on.
  • Part II orders: the part of routine orders that records personnel events with authority, promotions, appointments, postings, attestations, transfers, and the like, each as a numbered entry that updates the service record.
  • Personnel event: a change in a person's service that must be recorded, such as a promotion, an appointment, a posting, an attestation, or a release; the thing a Part II order entry exists to record.
  • Part II order entry (serial): one numbered item in the Part II orders, recording one personnel event for one or more named persons, with the effective date and the authority for it; it is the document that authorises the record to be updated.
  • Authority: the source that justifies an entry, the order, decision, or instruction that gives the unit the right to record the event; every Part II entry cites its authority so the change can be traced back to who decided it.
  • Effective date: the date from which a personnel event takes effect, which is not always the date the order is published; a promotion may be effective from a date earlier than the order that records it.
  • Posting (to a record): the act of carrying a published Part II entry into the service record, so that the record now shows the event; not to be confused with a posting as a personnel event (a move to a new appointment or location).
  • Attestation: the formal act by which a person enlists and takes on the obligations of service; an attestation is a personnel event recorded by Part II order.
  • Promulgation authority: the officer under whose authority the orders are issued, typically the commanding officer through the Adjutant; the orders carry that authority and so the entries within them do too.

What routine orders are and why a unit publishes them

A unit cannot run on word of mouth. Duties have to be known before they fall due, parades have to be timed, notices have to reach everyone, and the events that change people's service have to be recorded in a way the whole unit, and the chain above it, can rely on. Routine orders are the instrument that does all of this in one regular, published document. They are issued on a cycle, daily in a busy headquarters, less often in a small or part-time unit, but always on a known rhythm so that everyone knows when to look and what to look for. The act that matters is promulgation: an order is not in force because it was drafted or because the commanding officer meant it, but because it was published as part of the orders. Promulgation is the moment a decision becomes official and takes effect.

The reason a unit puts its instructions and its personnel events into one published instrument, rather than passing them around informally, is that publication does two things informality cannot. First, it makes the matter known to everyone at once, in the same words, so there is one version and not many. A duty announced in orders is a duty no one can later claim not to have known; an event recorded in orders is an event the whole unit has been told of in identical terms. Second, it fixes the matter in a dated, numbered, attributable record. Orders are kept, so the unit can always show what it ordered and when, and under whose authority. A force that orders by publication can prove what it ordered; a force that orders by conversation cannot, and is left arguing about what was said.

Routine orders are issued under the authority of the commanding officer, in practice through the Adjutant and the orderly room, which drafts, assembles, and publishes them. That single line of authority is what gives the orders their weight: because they are the commanding officer's orders, what they instruct must be done and what they record is official. The orderly room's handling of orders is therefore not clerical tidying but the exercise of the unit's authority in written form, drafted to the clear, correct, properly formatted service writing of PME 210, because an order that is ambiguous or wrong does its damage at the scale of the whole unit.

   ROUTINE (DAILY) ORDERS  ·  one published instrument, two parts

   COMMANDING OFFICER'S AUTHORITY
        |  (drafted and published by the Adjutant / orderly room,
        |   on a regular cycle: daily, or whatever the unit's rhythm)
        v
   +================== ROUTINE ORDERS ==================+
   |                                                    |
   |   PART I  ........  INSTRUCTION & ROUTINE          |
   |                     duties, parades, notices,      |
   |                     standing information           |
   |                     -> tells the unit what to DO   |
   |                                                    |
   |   PART II  .......  PERSONNEL EVENTS, with AUTHORITY|
   |                     promotions, appointments,      |
   |                     postings, attestations, etc.   |
   |                     each a numbered entry (serial)  |
   |                     -> the AUTHORITY to update the  |
   |                        SERVICE RECORD               |
   +====================================================+

   PROMULGATION is the act that matters: an order is in force
   because it is PUBLISHED, not because it was drafted or meant.
   Published = known to all in one version, and fixed in a dated,
   numbered, attributable record the unit can always produce.

Part I and Part II: two parts, two jobs

The split into Part I and Part II is not a filing convenience; it separates two genuinely different kinds of thing, and keeping them apart keeps each part doing its job cleanly. Part I orders carry instruction and routine. They tell the unit what to do and what to know: the orderly officer and orderly NCO for the day, the timings of parades, the dress for a coming event, ranges and training, leave arrangements, security and safety notices, lost property, standing information that everyone needs. Part I is forward-looking and operational in the administrative sense; it organises the unit's coming hours and days. A Part I order is read, acted on, and then largely spent, though it is kept as the record of what was instructed.

Part II orders do something different. They record personnel events, and they do so with authority. A Part II entry does not tell anyone what to do tomorrow; it states what has formally happened to a named person's service and from what date: that a private has been promoted corporal with effect from a given date, that a member has been appointed to a duty, that a national has attested and joined the strength, that a member has been posted, transferred, or released. Each such entry is the authority on which the service record is changed. That is the heart of the matter and the reason Part II is kept separate and handled with particular care: a Part I order, once acted on, is spent, but a Part II entry goes on to alter the permanent record of a person's service, and so it must be exactly right.

Placing a matter in the right part is usually clear once you ask the right question: does this instruct or inform the unit (Part I), or does it record a change to a named person's service that the record must reflect (Part II)? A notice that promotion boards will sit next month is Part I, because it instructs and informs; the actual promotion of a named member is Part II, because it records an event and authorises a record to change. When in doubt, the test is whether a service record should change as a result: if yes, it is a Part II event and must be ordered as one.

   PART I  vs  PART II  ·  same orders, two different jobs

   +---------------------------+---------------------------------+
   |   PART I  (instruction)   |   PART II  (recorded events)    |
   +---------------------------+---------------------------------+
   | Tells the unit what to DO | Records what has HAPPENED to a  |
   | and what to KNOW          | named person's service          |
   +---------------------------+---------------------------------+
   | Forward-looking, routine  | Records a past event, with an   |
   |                           | EFFECTIVE DATE                   |
   +---------------------------+---------------------------------+
   | Spent once acted on       | Goes on to update the SERVICE   |
   | (still kept as a record)  | RECORD; is the AUTHORITY to do  |
   |                           | so                              |
   +---------------------------+---------------------------------+
   | Examples:                 | Examples:                       |
   |  - orderly officer/NCO    |  - promotion (Pte -> Cpl)       |
   |  - parade timings         |  - appointment to a duty        |
   |  - dress for an event     |  - posting / transfer           |
   |  - range & training notes |  - attestation (joins strength) |
   |  - leave & safety notices |  - release                      |
   +---------------------------+---------------------------------+

   THE TEST when unsure: "Should a service record change because of
   this?"  YES -> it is a PART II event, order it as one.
                    NO -> it is PART I instruction or notice.

Why a Part II entry is the authority that updates the record

This is the single idea the whole lesson turns on, and it is worth stating plainly and then defending. A personnel event becomes part of a person's service record because, and only because, a Part II order entry has authorised it. The order is the authority. The record follows the order; the record does not lead it. A clerk does not write a promotion into a record because they believe it happened, or because the member says so, or because a parade was held; the clerk writes it because a Part II entry, published under the commanding officer's authority, says it happened, with effect from a stated date. No proper order, no proper record change. That is not bureaucratic caution; it is the only way a record can be trusted.

Consider the alternative. If a record could be changed on rumour, on a verbal say-so, or on a clerk's own judgement that something was probably true, then no entry could be relied on, because no one could tell which entries rested on authority and which on someone's impression. Command acts on records, entitlements flow from records, careers and pay and eligibility turn on records, as Lesson 02 set out, and a record anyone could amend on their own belief would be worthless for any of that. The rule that every personnel change must trace back to a published order is what makes the record provable: for any entry, you can ask "on what authority?" and the answer is a specific, dated, numbered Part II serial, which in turn cites the decision behind it. The chain runs unbroken from the decision, to the order that promulgated it, to the entry in the record.

This also tells you what an event is, administratively, before it has been ordered. A promotion that a board has decided but that has not yet been published in Part II orders is a decision, not yet a recorded fact of service; the member is not, for the record, promoted until the order is out, which is why the effective date is stated explicitly and may differ from the publication date. The orderly room's discipline, then, is never to update a record ahead of the order, and never to fail to update it once the order is published. The order is the gate: nothing passes into the record except through it, and everything that passes through it must reach the record. An event recorded without an order is unproven; an order not posted is a change authorised but not carried out. Both are failures, and the administrator's job is to let neither happen.

   FROM EVENT TO RECORD  ·  the order is the gate, and the authority

   A DECISION is made
   (e.g. a board recommends Pte A.N. for promotion to Cpl)
        |
        |   <-- not yet a recorded fact of service. A decision only.
        v
   PART II ORDER ENTRY is raised and PUBLISHED
   "Serial 07/26: Pte A.N. promoted Cpl, w.e.f. 01 Jun 26,
    authority: CO's approval of board, file ADM/PER/014"
        |
        |   <-- THIS is the authority. Published = official.
        v
   THE SERVICE RECORD is updated (POSTED)
   rank changed Pte -> Cpl, effective 01 Jun 26, with a
   reference back to the Part II serial that authorised it
        |
        v
   ANY LATER QUESTION "on what authority is this rank?"
   is answered: Part II serial 07/26, which cites the board
   decision on file ADM/PER/014.

   THE GATE:  nothing enters the record except through a published
   order;  and everything a published order records MUST be posted.
   Record FOLLOWS order. Never the other way, never on rumour.

Drafting a clear, correct Part II order entry

A Part II entry has one job, to record a personnel event unambiguously and with its authority, and a good entry does that job so completely that no one reading it later has to ask a question of it. The discipline is to make every entry answer, on its own, four things: what event, to whom, from when, and on what authority. Leave any of the four unclear and the entry fails, because a promotion with no effective date cannot be posted correctly, an appointment to no named person records nothing, and an event with no cited authority breaks the very chain the entry exists to make. So an entry is built deliberately to carry all four, in clear, correct, properly formatted service writing of the PME 210 standard.

Take each in turn. The event must be stated precisely in the unit's standard terms: "promoted Corporal", "appointed Orderly Room NCO", "posted to", "attested and taken on strength", "released", and not a loose phrase that could be read two ways. The person must be named so that there is exactly one of them, by the unit's identifying convention, rank or status, name, and the service identifier the record uses, because two members may share a name and the record must attach to the right one. The effective date must be given, the date from which the event takes effect, stated as "with effect from" and a date, and recognised as possibly different from the date the order is published. And the authority must be cited, the decision or instruction that justifies the entry, by its own reference, typically the file or order on which the decision sits, so the entry can be traced back. An entry with all four, in correct form, can be posted to a record by anyone competent, with no guesswork, and defended later from its own words.

Two habits keep entries honest in practice. The first is that an entry records one clean event; where several members are promoted on the same authority and date you may list them under one serial, but you do not blur two different kinds of event into one entry, because posting then becomes ambiguous. The second is that the entry is checked against its authority before it is published, not after, because a Part II order is the authority for a permanent record change, and an error promulgated has now been formally ordered and must be corrected by a further order rather than quietly fixed. Accuracy before publication is therefore not a courtesy but a duty, tied to the standard of accuracy and honesty that Lesson 02 set for records and that LDR 420 sets for those who keep them: the entry must be true, complete, and exactly right before it carries the unit's authority into a person's permanent record.

   A PART II ORDER ENTRY  ·  the four things every entry must carry

   PART II ORDERS  -  Serial 07/26
   +-----------------------------------------------------------------+
   |  PROMOTION.  No. 00231 Pte A.N. (a national), [Section/Coy],    |
   |  is promoted CORPORAL with effect from 01 Jun 26.               |
   |  Authority: CO's approval of promotion board, file ADM/PER/014. |
   +-----------------------------------------------------------------+
        |          |                          |              |
        v          v                          v              v
     EVENT      PERSON                   EFFECTIVE DATE    AUTHORITY
   what has   named so there is        "with effect      the decision
   happened,  exactly ONE of them:     from" + a date    that justifies
   in standard  status/rank, number,   (may differ from  it, cited by
   terms        name, identifier       the publish date) its reference

   IF ANY OF THE FOUR IS MISSING, THE ENTRY FAILS:
     no event in standard terms  -> cannot be posted cleanly
     no unique person            -> record may attach to the wrong one
     no effective date           -> the record's "from when" is wrong
     no cited authority          -> the chain back to the decision breaks

   AND: check the entry against its authority BEFORE publishing. A
   published error is now formally ordered; it takes a FURTHER order
   to correct, never a quiet amendment.

In Practice: A clerk raises a Part II entry and posts it to the record

Corporal Mensah is the orderly-room clerk preparing the week's routine orders. On her desk is a file, ADM/PER/014, that came back yesterday with the commanding officer's minute on it, dated and signed: a promotion board has recommended Private A.N., a national, for promotion to corporal, and the commanding officer has approved it with effect from the first of the coming month. Mensah knows that the approval on the file is a decision, not yet a recorded fact of service. For the record to change, the promotion has to pass through orders. So she begins by drafting the Part II entry, not by touching the service record, because the order comes first and the record follows it.

She drafts the entry to carry all four things. The event she states in the unit's standard form, "is promoted Corporal". The person she names so there is exactly one of them: the service number, status, and name as the record holds them. The effective date she takes from the commanding officer's minute and states as "with effect from" the first of the month, noting to herself that this is earlier than the date the orders will be published, which is correct and intended. The authority she cites as the commanding officer's approval of the board on file ADM/PER/014, so that anyone reading the entry later can trace it back to the decision. Before it goes anywhere, she checks the drafted entry against the file: the name, the number, the rank, the date, and the authority, line by line, because once published the entry is the authority for a permanent change and an error would now be formally ordered. The Part I matter she is also assembling, the duties and a parade timing for the week, she keeps in its own part, because instruction and recorded events do different jobs and do not mix.

The orders are published under the commanding officer's authority through the Adjutant, and only now, with the Part II serial promulgated, does Mensah update the service record. She posts the promotion, changing the rank from private to corporal with effect from the stated date, and enters against it a reference to the Part II serial that authorised it, so the record carries not just the new rank but the proof of why it changed. She places a copy of the published order on file ADM/PER/014 as the next enclosure and minutes the file that the entry has been raised, published, and posted, closing the loop. Months later, when someone asks on whose authority this member holds the rank of corporal and from when, the record answers it: corporal with effect from that date, authority Part II serial such-and-such, which cites the board decision on the file. The event became a record the only way an event should, through a proper order, traceable end to end.

Check Your Understanding

  1. A member tells the orderly room that they have been promoted and asks for their service record to be updated to show it, and the clerk on duty can see that a promotion board did sit and that the member was a strong candidate. Explain why the clerk must not update the record on this basis, what is missing, and what must happen before the record can properly be changed. State the principle in your own words.

  2. Sort each of the following into Part I or Part II orders, and for each give the one-line reason: (a) the orderly officer and orderly NCO for the coming week; (b) the appointment of a named member as Orderly Room NCO, recorded against their service; (c) a notice that the dress for a forthcoming event is to be a particular order of dress; (d) the attestation of a national who has just joined and is taken on strength; (e) the timings of Tuesday's parade. State the single test you used to decide.

  3. Draft a Part II order entry for the following: a private (give them any name and a service number) is appointed to a duty with effect from a date you choose, on the authority of a decision held on a named file. Then list the four things every Part II entry must carry, point to each in your draft, and explain what would go wrong in posting the record if your draft omitted the effective date, and separately if it omitted the authority.

Reflection (write a short paragraph): Think about why a force insists that a real event, something everyone agrees happened, still does not change a record until it has been formally ordered and published. What is gained by making the order the gate, and what would be lost if records could be changed on what people knew to be true rather than on what had been properly ordered? Relate this to the trust that command, and the member whose record it is, place in the record being right.

Summary

  • Routine orders (daily orders) are how a unit promulgates its instructions and records its events in one regular, published instrument, issued under the commanding officer's authority through the Adjutant and orderly room; an order is in force because it is published, not because it was drafted or intended.
  • Routine orders split into two parts doing two jobs: Part I carries instruction and routine (duties, parades, notices, standing information, what the unit must do and know), and Part II records personnel events with authority (promotions, appointments, postings, attestations, transfers, releases).
  • The test for which part a matter belongs in is whether a service record should change as a result: if yes, it is a Part II event and must be ordered as one; if it only instructs or informs, it is Part I.
  • A Part II order entry is the authority that updates the service record: the record follows the order, never the other way, and never on rumour, say-so, or a clerk's own belief, so that any entry in a record can be traced back to a dated, numbered, published serial and the decision it cites.
  • An event not yet published in orders is a decision and not yet a recorded fact of service; the order is the gate, and the orderly room neither updates a record ahead of the order nor leaves a published order unposted.
  • A clear, correct Part II entry carries four things, the event (in standard terms), the person (named so there is exactly one), the effective date ("with effect from", possibly earlier than the publish date), and the authority (cited by reference), written to the PME 210 service-writing standard and checked against its authority before publication, because a published error is now formally ordered and takes a further order to correct.
  • Builds on Lesson 02 · The Service Record (the record a Part II entry updates) and Lesson 03 · The Registry and the Registered File (the file on which the authority sits and the published order is enclosed). Connects to ADM 210 · Personnel Administration (the joining, promotion, and appointment paperwork that Part II entries record), ADM 220 · Course Records and Qualification Tracking (qualifications likewise recorded by proper authority), PME 210 · Basic Staff Duties and Written Orders (the service writing that order entries are drafted to), ADM 310 · Orderly Room and Headquarters Administration (the battle rhythm by which orders are published), CIS 220 · Identity, Access, and Records Security (controlling who may see and amend the records orders update), and LDR 420 · Command Responsibility and Ethical Leadership (the accuracy and honesty an order entry, and the record it authorises, depend on).

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

Lesson 5 · Knowledge Check

Question 1 of 3

When is an order in force?