Lesson Overview
This is the last lesson of the course, and it is about the one thing that holds all the rest up. You have learned the orderly room, the service record, the registry and the registered file, retention and confidentiality, and the routine orders that carry the authority to update a record. Every one of those systems is built to do a single job: to keep the truth of the force, and to keep it findable, so that command can act on it and a member can rely on it. None of those systems is worth anything if the truth they carry is wrong. A perfectly numbered file full of false entries is a tidy lie. The standard this lesson teaches, accuracy and honesty, is therefore not an extra virtue added on at the end; it is the whole reason the work exists.
The reason the standard is absolute, and not merely desirable, is that records are acted on. Command reads a strength return and moves a section on the strength of it. A clerk posts a promotion to a record and the member's pay, in USD, changes because of it. A training record says a member is qualified and they are put forward, or held back, accordingly. A medical category, held appropriately, governs what a member may be asked to do. When a record is right, all of that is right. When a record is wrong, whether by a lie or by a careless slip, the force acts on a falsehood, and a real person carries the harm: the wrong pay, the missed course, the unrecognised service, the entitlement denied, the duty they should never have been given. A false or careless entry is not a paperwork error. It is harm done to a national who trusted the force to keep their service true.
This is the knowledge layer. Reading will teach you why accuracy and honesty are the administrator's first duty, how to reconcile records and check their accuracy before they are relied on, and how to correct an error properly, in the open, with authority, rather than rubbing it out or quietly changing it. The hands-on work this feeds, reconciling a return against the records behind it, finding and correcting a real error to standard, and signing your name to records you have made true, is practised and signed off in person, where supervision allows, in a working orderly room. By the end you will be able to explain why an administrator's records must be accurate and honest, and what real harm a false or careless entry does to a member and to command; reconcile records against one another and check accuracy so that errors are caught before they are acted on; correct an error the proper way, as a transparent, dated, authorised correction that leaves the original visible, and recognise an improper alteration or erasure as a thing never to be done; explain the administrator as the guardian of the truth of the force, and how that duty ties to the ethical leadership taught in LDR 420; and draw the whole course, records, registry, retention, and orders, into one accountable, honest system.
Key Terms
- Accuracy: the quality of a record being correct, that what it states is what truly happened or is truly the case; an accurate record can be acted on without doing harm.
- Integrity (of records): the wholeness and honesty of a record, that it has not been falsified, tampered with, or quietly altered, and that what it shows can be trusted to be the real account.
- Honesty (of the administrator): the administrator's own integrity, the refusal to enter, change, or conceal anything to make a record say what is convenient rather than what is true.
- Reconciliation: checking two or more records that should agree against one another, a return against the records behind it, a nominal roll against the strength, a copy against its source, so that any disagreement is found and resolved before either is relied on.
- Accuracy check (verification): confirming that a record is correct against its authority, the document, the Part II order, the attestation, that proves it, before it is treated as true.
- Error: an entry that is wrong, whether by mistake (a slip, a miscopy, a wrong date) or otherwise; an error in a record is a falsehood the force may act on until it is corrected.
- Correction (proper): the authorised, dated, attributable putting-right of an error, made so that the original is still visible, the correct entry is clear, and the authority and reason for the change are recorded.
- Alteration (improper): changing a record so that the original can no longer be seen, by erasing, overwriting, or quietly editing it; an alteration destroys the audit trail and is never permitted.
- Erasure: removing an entry so that no trace of it remains; like alteration, it is forbidden, because it hides that anything was ever there to question.
- Authority: the documented basis on which an entry or a correction is made, the Part II order, the signed instruction, the source document, cited so the change can be traced and trusted.
- Guardian of the truth: the administrator's role and duty, to hold the records of the force as a true account and to defend that truth against pressure, convenience, and carelessness alike.
Why accuracy and honesty are the first duty
It is tempting to rank the administrator's duties and put accuracy somewhere in the middle, after speed and tidiness and keeping up with the traffic. That ranking is wrong, and getting it wrong is how records quietly rot. Accuracy and honesty are the first duty, ahead of everything, because they are the only duties that, if broken, make all the others worthless. A record produced quickly but wrong is worse than a record produced slowly but right, because the wrong record will be acted on with confidence and will do its harm before anyone thinks to doubt it. A file kept beautifully but containing a false entry is a trap, not a record. The point of the orderly room is not paper; it is truth that can be acted on, and the moment the truth fails, the paper is just a way of spreading a falsehood faster.
The reason this matters so much in a force, more than in many other kinds of office, is that records are command's eyes. A commander cannot personally verify who is on strength, who is qualified, who is owed leave, or what was ordered yesterday; the commander reads the records and acts. The records stand in for direct knowledge. This is the gift the orderly room gives command, the ability to act on the whole force at once through a few trusted documents, and it is exactly why a false record is so dangerous: it is believed precisely because the system is trusted. An administrator who lets an error stand, or worse, who enters something untrue, is not just making a mistake on a page. They are feeding a falsehood into the one channel command relies on to see, and command will act on it as if it were sight.
And on the other end of every record is a person. The abstractions, strength, qualification, entitlement, category, all resolve into a national whose service the force has undertaken to keep truly. When a promotion is posted late or wrong, a member's pay in USD is wrong and their family feels it. When a course or qualification is not recorded, real training is lost to the force's memory and the member is held back from what they have earned. When service is left unentered, a person's contribution to the Principality goes unrecognised. When a medical category is wrong, a member may be ordered to do what they should not. These are not paperwork outcomes. They are wages, careers, recognition, and welfare, riding on whether the administrator did the work truly. The first duty is accuracy and honesty because a national is trusting the force, through the administrator, to hold their service straight, and that trust is the thing the whole speciality exists to keep.
WHY A FALSE OR CARELESS ENTRY DOES REAL HARM
THE RECORD (what the administrator keeps)
|
v
COMMAND ACTS ON IT (records are command's eyes; a commander
| cannot verify everything in person, so the
| record stands in for direct knowledge)
v
A NATIONAL CARRIES THE RESULT
+-------------------------------------------------------------+
| Wrong / late entry -> Real harm to the member |
+----------------------------+--------------------------------+
| Promotion posted wrong -> Wrong pay (USD); family feels |
| Course not recorded -> Held back; training lost |
| Service left unentered -> Contribution unrecognised |
| Wrong medical category -> Ordered to do what they must |
| not; welfare put at risk |
+-------------------------------------------------------------+
The record is believed BECAUSE the system is trusted. So a
falsehood fed into it is acted on as if it were the truth.
Accuracy and honesty are the FIRST duty, ahead of speed and
tidiness, because if they fail, everything else is worthless.
Checking accuracy and reconciling records
Accuracy is not something you hope for; it is something you check, deliberately, before a record is relied on. Two habits do most of the work, and an administrator practises both as routine. The first is the accuracy check, sometimes called verification: before you treat an entry as true, you confirm it against the authority that proves it. You do not post a promotion because someone said so in the corridor; you post it because the Part II order says so, and you check that the name, the rank, the date, and the authority on the order match what you are about to enter. You do not record a qualification on a hearsay; you record it against the course result or certificate that proves it. The discipline is simple to state: every entry is made against, and traceable to, a document that proves it, and you check the entry against that document before it is trusted. An entry with no authority behind it is not yet a fact; it is a claim.
The second habit is reconciliation, the checking of records that should agree against one another so that any disagreement surfaces before either is acted on. Records in a force are not independent; they overlap on purpose, and where they overlap they should match. A nominal roll, the list of who is on strength, should agree with the strength return, the count reported up the chain; if the roll names twenty-eight and the return says twenty-nine, one of them is wrong, and reconciliation is how you catch it before the wrong number reaches command. A copy issued to a member should match its source record; the entries on a service record should match the Part II orders that authorised them; the training record should match the course results behind it. Reconciliation is the act of laying two such records side by side, walking them line for line, and resolving every difference, by finding the authority and correcting the record that is wrong, never by simply picking the number you prefer. A disagreement found is a gift, because it has shown you an error while it is still cheap to fix.
The reason both habits matter is timing. An error caught at the desk, before the return goes up or the entry is acted on, costs a minute to fix and harms no one. The same error, undetected, travels: it reaches command, command acts, the wrong pay is issued or the wrong member is moved, and now the error must be chased back through everything it touched and every consequence undone. The whole purpose of checking accuracy and reconciling is to catch errors at the cheapest possible moment, at the source, before the force has acted. An administrator who checks before relying, and reconciles where records should agree, stops most errors at the desk, which is the only place they are cheap to stop. This is the same instinct as the registry's discipline in Lesson 03 and the record's single source of truth in Lesson 02: the work is built so that truth is verified, not assumed.
ACCURACY CHECK + RECONCILIATION · catch the error at the desk
(A) ACCURACY CHECK before you treat an entry as true:
Entry to be made ---> the AUTHORITY that proves it
e.g. "promote Pte X to Cpl, 12 Apr"
check against the PART II ORDER: name? rank? date?
authority cited? ALL MATCH -> post it. ANY MISMATCH
-> stop, resolve, do NOT post.
Rule: no entry without an authority behind it.
(B) RECONCILIATION where records should agree:
NOMINAL ROLL (who is on strength) STRENGTH RETURN
+-----------------------------+ +---------------+
| 28 names listed | <-----> | reports 29 |
+-----------------------------+ +---------------+
\ /
\ THEY DISAGREE -> ONE IS WRONG
\ /
v v
Walk line for line, find the authority, correct
the record that is wrong. NEVER just pick a number.
WHY: an error caught HERE costs a minute and harms no one.
The same error, missed, reaches command, is acted on, and
must then be chased back through everything it touched.
Correcting an error the proper way
Everyone who keeps records will, sooner or later, find an error, their own or someone else's. The mark of an administrator is not that they never err; it is how they put an error right. There is a correct way and a forbidden way, and the difference between them is the whole of records integrity. The forbidden way is to make the error disappear: to erase the wrong entry, to overwrite it, to quietly edit the record so that it now reads correctly and the mistake never shows. This is tempting precisely because it looks clean, and it is the worst thing you can do, because it destroys the audit trail. A record that has been silently altered cannot be trusted at all, even where it happens to be right, because there is no way to know what else has been changed. An erasure does not just hide a mistake; it hides that anything was ever there to question, and in doing so it turns an honest record into one that can never be relied on again.
The correct way is the opposite in spirit: you correct in the open. A proper correction leaves the original entry still visible, marks it clearly as superseded, makes the correct entry plainly, and records who made the correction, when, and on what authority, with the reason. The wrong date is not scrubbed out; it is struck through with a single line so it can still be read, the right date is entered beside or below it, and a dated, signed note records the correction and cites the authority for it. Anyone reading the record later sees the whole truth: that an entry was wrong, that it was corrected, by whom, when, and why. The correction is itself part of the record, an honest event in the life of the file, exactly as a minute is in Lesson 03. The point is not to pretend the error never happened; it is to make the record true while keeping it honest about how it got there.
Why so strict? Because integrity is not the absence of mistakes; it is the trustworthiness of the whole. A record that openly shows its corrections is more trustworthy, not less, because a reader can see that errors are caught and put right in the daylight, which is exactly what tells them the rest can be believed. A record that shows no corrections might be perfect, or it might be one that hides them, and there is no way to tell, so it cannot be fully trusted. The transparent correction protects everyone: the member, whose record is now both correct and provably so; the administrator, who has a dated, authorised account of exactly what they changed and why, and so cannot later be accused of tampering; and command, which can act on the record knowing that where it has been corrected, it has been corrected honestly. Never erase, never quietly alter, never overwrite. Strike through, enter the truth beside it, date it, sign it, cite the authority, and let the record carry its own honest history.
CORRECTING AN ERROR · the proper way vs the forbidden way
THE ERROR: record reads "Promoted Cpl: 02 Apr"
the Part II order authority says 12 Apr.
+---------------------------+ +-----------------------------+
| IMPROPER (FORBIDDEN) | | PROPER (REQUIRED) |
+---------------------------+ +-----------------------------+
| Erase "02" and write | | Promoted Cpl: ~~02~~ 12 Apr |
| "12" over it, OR quietly | | Corrn: date amended to |
| edit so it now reads | | 12 Apr per P.II Order 14/26|
| "12 Apr" with no trace. | | R. Okoro, 13 Apr (signed) |
| | | |
| Result: the original is | | Result: original still |
| GONE. No one can see an | | READABLE (struck once), |
| error was ever there, so | | correct entry CLEAR, plus |
| NOTHING on the record can | | WHO, WHEN, WHY, and the |
| be fully trusted again. | | AUTHORITY cited. |
+---------------------------+ +-----------------------------+
THE RULE: NEVER erase, overwrite, or quietly alter a record.
Strike through once (leave it readable), enter the truth beside
it, then date it, sign it, and cite the authority. The correction
is itself an honest event in the record, like a minute on a file.
A record that shows its corrections in daylight is MORE trusted,
not less, because a reader can see errors are caught and put right.
The administrator as guardian of the truth of the force
Put all of this together and a role comes into focus that is larger than clerking. The administrator is the guardian of the truth of the force. The records are the force's memory and its account of itself, who belongs to it, what they have done and hold, what was ordered, what is owed, and the administrator is the person who holds that account true. It is a position of real trust, because almost no one else checks the records the administrator keeps; command reads them and acts, members rely on them, the College builds qualification on them, and all of that rests on the quiet assumption that the person at the desk kept them honestly. That assumption is the administrator's charge. To keep it is the whole of the job; to break it, even once, even conveniently, is to betray the thing the speciality exists to protect.
Being a guardian of the truth means defending it against three pressures, and they are worth naming because each is real. The first is convenience: it is always quicker to skip the accuracy check, to not reconcile, to let a small error stand, and the administrator must refuse the quick path when it costs the truth. The second is pressure from people: there will be times when someone, sometimes someone senior, would prefer the record to say something other than what is true, a date moved, an entry softened, an inconvenient fact left out. The administrator's answer is the same to everyone: the record says what the authority shows, and a change is made only with proper authority, in the open, as a transparent correction, never as a quiet favour. The truth of the record is not the administrator's to bend, and it is not anyone's to bend; it belongs to the force and to the national whose service it records. The third pressure is carelessness, the slow erosion of standards when no one is watching, and against that the only defence is the administrator's own discipline, holding the standard on the dull day exactly as on the watched one.
This is why the standard is an ethical one, and why it ties directly to the ethical leadership taught in LDR 420. Integrity there is the leader's refusal to act dishonestly even when it would be easier or expected; integrity here is the administrator's refusal to keep a dishonest record even when it would be easier or asked for. They are the same virtue applied to different work, and in a force they reinforce each other: a leader can only lead ethically if the records they act on are kept honestly, and an administrator can only keep records honestly if the command climate backs them when they hold the line. The administrator does not need rank to exercise this leadership. Holding the truth of the force, against convenience, against pressure, against carelessness, is leadership of exactly the kind LDR 420 describes, exercised from the orderly-room desk. The guardian of the truth is a leader, and the record is the ground they hold.
In Practice: A clerk is asked to move a date
Corporal Adeyemi, the orderly room's senior clerk, is reconciling the month's records before the strength and qualification returns go up. Laying the nominal roll beside the strength return, he finds they disagree by one: the roll carries a member the return has dropped. He does not pick the number that makes the return tidy. He works back to the authority, finds the Part II order that posted the member in, confirms the member is on strength, and corrects the return against the roll and the order, noting the authority. The error is caught at the desk, a minute's work, and the wrong number never reaches command. While he is in the records, he finds a second thing: a promotion entered on a member's service record shows the wrong date, two days before the Part II order that authorised it. He checks the order, confirms the true date, and prepares to correct the record the proper way.
As he does, the member's section commander, who has heard the promotion is in question, asks him quietly to "just leave the earlier date, it's kinder, and no one will check." Adeyemi declines, and he is right to. He does not erase the wrong date and he does not overwrite it; that would destroy the record's integrity, and it is exactly what he must never do. Instead he strikes the wrong date through with a single line so it stays readable, enters the correct date from the Part II order beside it, and writes a dated, signed correction citing the order as the authority and the reason for the change. The record now reads true, and it reads honestly: anyone looking at it later can see that an entry was wrong, that it was corrected, by whom, when, and on what authority. He explains to the section commander, without heat, that the record says what the authority shows, that any change is made in the open with authority, and that a quiet favour on a date is not a kindness but a falsehood the force might later act on, with the member's pay in USD riding on it.
The returns go up reconciled and the record stands corrected and honest. Months later, when the member's promotion date is queried for a seniority calculation, the record answers from its own pages: here is the true date, here is the correction, here is the authority, here is who made it and when. Nothing has to be reconstructed, no one has to be taken on trust, because Adeyemi reconciled before relying, checked every entry against its authority, and corrected the one error he found in the daylight rather than the dark. He kept the truth of the force, against the convenience of a tidy return and against pressure to bend a date, and that is the whole of the administrator's standard. It is also, exactly, the ethical leadership of LDR 420, exercised from a desk.
Check Your Understanding
An administrator is busy and posts a promotion to a member's service record on the strength of a corridor conversation, without checking the Part II order, and the date turns out to be wrong. Trace the harm: who acts on the record, what real consequence the member carries because the entry is wrong (use the member's pay, in USD, and one other consequence), and explain why "accuracy and honesty are the first duty, ahead of speed and tidiness" is the right way to rank the administrator's duties.
You are reconciling a nominal roll that lists 28 members on strength against a strength return that reports 29, and the two disagree. Explain step by step how you reconcile them properly, what you must never do (such as simply picking the number you prefer), and why catching this disagreement at the desk, before the return goes up, matters so much compared with catching it after command has acted.
You find a wrong date on a record and are tempted, or asked, to "just fix it quietly" by erasing the old date and writing the right one over it. Explain why this improper alteration is forbidden and what it does to the record's integrity, then describe the proper correction in full, what you do to the original entry, what you add, and what you record, and explain why a record that openly shows its corrections is more trustworthy, not less.
Reflection (write a short paragraph): Think of a time you held, or wished you had held, an accurate honest account when it would have been easier or more comfortable to fudge it, a number, a date, an admission of a mistake. What pressure pushed you towards the convenient version rather than the true one, and how does the administrator's standard, that the record says what the authority shows and is corrected only in the open, change how you would handle being the person others are quietly trusting to keep the truth?
Summary
- Accuracy and honesty are the administrator's first duty, ahead of speed and tidiness, because they are the only duties whose failure makes all the others worthless: a record produced quickly but wrong is worse than one produced slowly but right, since the wrong record is acted on with confidence and does its harm before anyone doubts it.
- A false or careless entry does real harm because records are command's eyes (a commander acts on the record in place of direct knowledge) and because a national is on the other end of every record: wrong or late entries mean wrong pay in USD, lost training, unrecognised service, and welfare put at risk.
- Accuracy is checked, not hoped for: every entry is made against, and traceable to, an authority that proves it (the Part II order, the certificate, the source document), and is verified against that authority before it is trusted; an entry with no authority behind it is a claim, not yet a fact.
- Reconciliation lays records that should agree side by side, nominal roll against strength return, copy against source, record against the orders that authorised it, and resolves every difference by finding the authority and correcting the wrong record, so errors are caught at the desk where they are cheap, before command acts.
- An error is corrected the proper way, in the open: the original is left visible (struck through once, still readable), the correct entry is made clearly, and the correction is dated, signed, and made against a cited authority; a record that openly shows its corrections is more trustworthy, not less.
- An improper alteration or erasure, scrubbing out, overwriting, or quietly editing so the original cannot be seen, is forbidden, because it destroys the audit trail and means nothing on the record can be trusted, even where it happens to be right.
- The administrator is the guardian of the truth of the force, holding the records true against convenience, against pressure from people who would prefer them to read otherwise, and against carelessness; the truth of the record belongs to the force and to the national whose service it records, and is no one's to bend.
- This closes the course by drawing the whole into one accountable, honest system: the service record (Lesson 02) and the registry and registered file (Lesson 03) keep the truth findable and audited; retention and confidentiality (Lesson 04) keep it only as long and as safely as it should be held; routine orders (Lesson 05) carry the authority that updates it; the administrative workflow (Lesson 06) and the suspense system (Lesson 07) make sure business is handled and nothing is dropped; releasing and disclosing records (Lesson 08) lets the truth out only to those entitled to it; the records management system (Lesson 09) keeps the whole findable and safe in digital form; and this standard of accuracy and honesty is what makes every part of it worth keeping.
- Builds on every earlier lesson of ADM 201 and ties the speciality together. Connects to PME 210 · Basic Staff Duties and Written Orders (the correction and the minute are service writing), CIS 220 · Identity, Access, and Records Security (accuracy and integrity sit alongside confidentiality as data-protection principles), LOG 201 · Stores, Equipment, and Accountability (the same honest accounting applied to property), and above all LDR 420 · Command Responsibility and Ethical Leadership, of which the administrator's standard is one true expression: integrity exercised from the orderly-room desk.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia