Royal Army College

Lesson Overview

A training standard is only as good as the authority behind it and the control kept over it. A course can be soundly designed, well implemented, and faithfully delivered, and still be worthless if no one owns its standard, if it was never properly approved, if it drifts and changes informally with no one in charge, or if the qualification it grants is recognised and trusted by no one. This lesson is about the governance of training: who owns a standard and has the authority to set and change it, how a course and its standard are approved and authorised, how a standard is held stable through controlled change, and how a course and the qualifications it grants are accredited so that they mean something and are trusted. It is the framework of authority and control within which all the design and delivery of the other lessons sits.

The governing idea is that a standard must have an owner, an authority, and control, or it is not really a standard at all. A standard no one owns drifts, because there is no one to hold it; a course no proper authority approved is one person's opinion, not the Army's standard; a standard that anyone can change informally is not stable enough to be relied on; and a qualification that no recognised authority stands behind certifies nothing anyone need believe. Governance supplies all four: a clear owner with the authority to set and maintain the standard, a proper approval before a course or standard takes effect, controlled change so the standard stays stable and current together, and accreditation so the qualification is recognised and trusted. Without this framework, the finest course design in the world produces qualifications no one can rely on.

This is the knowledge layer. It teaches you the ownership, approval, control, and accreditation that govern training standards, so that you understand the authority framework a course must sit within to be trustworthy. The actual exercise of training authority, the approving of courses, the owning of standards, is a command and staff responsibility carried out by those holding the proper appointments, and learned in the appointment under qualified oversight; this lesson is the understanding behind it. Read this to know how training is governed; the authority itself is exercised by those who hold it.

By the end you will be able to explain why a standard needs an owner, authority, and control, describe the approval and authorisation of a course or standard, set out the governance roles and why they are separated, explain accreditation and what makes a qualification trusted, and apply controlled change so a standard stays stable and current.

Key Terms

Training governance: the framework of ownership, authority, approval, and control within which training standards are set, maintained, and trusted.
Standard owner: the appointment with the authority and responsibility for a particular training standard: to set it, maintain it, and approve changes to it.
Training authority: the body or appointment with the command authority to approve courses and standards for the Army, making them official rather than a designer's proposal.
Approval (authorisation): the formal act by the proper authority that makes a course or standard official and in force, as opposed to a draft proposal.
Accreditation: the formal recognition that a course meets a standard, and that a person who passes it holds a genuine, recognised qualification.
Recognition: the trust placed in a qualification by others, inside or outside the Army, which depends on the authority and control behind it.
Configuration control: the disciplined management of changes to a standard or course, so it changes only through a controlled process and its version is always known.
Separation of duties: the governance principle that the roles of designing, approving, delivering, and assuring training are held by different people, so no one marks their own work.
Assurance (audit): the independent checking that standards are owned, current, properly applied, and trusted, which confirms the governance is actually working.
The training record: the durable record of who holds which qualification (ADM 220), which is the proof that makes a qualification real and auditable.

Why a standard needs an owner and authority

It is natural to think that once a standard is well written, it will simply hold, but standards do not hold themselves; they are held by people with the authority and responsibility to hold them, and a standard without such an owner drifts. The standard owner is the appointment responsible for a particular standard: for setting it, keeping it current, and approving any change to it. Their existence answers a question every standard must answer, "who is in charge of this?", and the answer matters because a standard that is everyone's responsibility is no one's, and erodes quietly as each person who touches it bends it a little, with no one positioned to notice or to stop the drift. Naming an owner pins the responsibility to a person, and responsibility that can be pinned to a person gets kept, exactly as the safety lesson said of the safety officer.

Beyond ownership, a standard needs authority, because a standard is a claim about what the Army requires, and only the Army, through its proper command and staff authority, can make that claim official. A standard or a course designed by an individual, however expert, is a proposal until a training authority with the command authority to do so approves it; only then is it the Army's standard rather than one person's view. This is why the College's own drafted standards are explicitly marked draft, for command approval, and are not in force until approved by the proper authority of the Principality: the College can design and propose, but it cannot, of itself, make a standard binding; that takes the authority of command. The distinction between a well-designed proposal and an authorised standard is not a formality but the difference between an opinion and a rule.

Together, ownership and authority give a standard the two things it needs to be real: someone responsible for it, and the command authority behind it. The remaining two, controlled change and accreditation, keep it stable and make it trusted, and follow below. The whole framework exists because a standard is a load-bearing thing, qualifications, capability, and lives rest on it, and load-bearing things need clear ownership and proper authority, not goodwill alone.

Approval and authorisation

A course and its standard pass from proposal to reality through approval: the formal act by the proper authority that makes them official and in force. Until that act, however polished the design, the course is a recommendation; after it, the course is the Army's, to be run and trusted as such. Approval matters because it is the point at which responsibility for the course passes from the designer, who proposes, to the command authority, who adopts it and stands behind it, and at which the course gains the authority that makes its qualification mean something.

Approval is not a rubber stamp but a real check, and the thing approved is checked against what matters: that the course genuinely meets the need it was built for, that its standard is right for the job, that it is sound, safe, and deliverable, and that the Army is willing to stand behind the qualification it will grant. The authority approving a course is taking responsibility for it, so it satisfies itself before doing so, which is why approval sits with command and staff authority and not with the designer alone, a point of separation taken up below. The "draft, for command approval" marking on the College's standards is exactly this discipline made visible: the work is done, proposed, and held explicitly as not-yet-in-force until the proper authority has checked it and adopted it.

This has a practical consequence for the designer: a course is designed toward approval, with the approving authority and its concerns in mind, and is presented for approval in a form the authority can actually check, the need, the objectives, the design, the standard, the safety, the deliverability, set out clearly (the course specification, written as PME 210 teaches). A designer who treats approval as an obstacle to be got past has misunderstood it; approval is how the designer's good work becomes the Army's real standard, and designing for it is part of designing well.

   FROM PROPOSAL TO STANDARD

   DESIGNED COURSE + STANDARD          a designer's PROPOSAL
   (sound, but one person's work)            |
                                             | presented for approval
                                             | (clear specification:
                                             |  need, objectives, design,
                                             |  standard, safety, deliverability)
                                             v
   PROPER TRAINING AUTHORITY checks:   meets the need? standard right?
   (command/staff, NOT the designer)   sound, safe, deliverable? willing
                                       to stand behind the qualification?
                                             |
                                             v approves / authorises
   THE ARMY'S STANDARD, IN FORCE       now official, run and trusted as such

   ("Draft, for command approval" = done, proposed, NOT yet in force.)

Governance roles and their separation

Good governance distributes the roles in training across different people, and the principle behind it is separation of duties: the people who design, approve, deliver, and assure training should not all be the same person, because concentrating these roles lets errors and self-interest go unchecked. The roles are distinct. The designer proposes the course and standard. The standard owner / approving authority checks and authorises it, taking responsibility for it on the Army's behalf. The deliverer (the instructors and course manager) runs it as designed. The assessor judges learners against the standard. And an assurer independently checks that the whole is working. These are different responsibilities, and separating them is what keeps any one of them honest.

The reason separation matters is the same reason it matters in assessment and in any system of integrity: no one should mark their own work. A designer who is also the sole approver approves their own design with no independent check; an assessor who is also the appeal authority judges challenges to their own decisions (which TRG 310 forbids); a deliverer who is also the assurer certifies that their own delivery met the standard. In each case the absence of separation removes the independent eye that catches the error or the bias, and the standard is protected only by the goodwill of one person, which is exactly what a standard should not depend on. Separation builds the independent check into the structure, so that the standard is protected by the system and not merely by individual virtue.

In a small force this is harder, because there are few people and one person may genuinely have to wear several hats, and the lesson is honest about it: perfect separation may be impossible when the same handful of members design, deliver, and assess. But the principle still guides, and the most important separations are protected even when others cannot be, especially that the authority who approves a course and the authority who assures it are not simply the designer marking their own work, and that an appeal is heard by someone other than the original decider. A small force keeps the separations that matter most and is honest where it cannot keep them all, rather than pretending an unseparated system is fully governed.

Accreditation and the trusted qualification

The point of all this governance is finally a qualification that means something, and that is the work of accreditation: the formal recognition that a course meets a standard, and that a person who passes it genuinely holds the qualified competence it certifies. A qualification is a promise, this person can do this thing to this standard, and accreditation is what makes the promise believable, because it ties the qualification to an owned standard, a proper approval, and controlled delivery and assessment, so that those who rely on it, commanders posting people, other members trusting a comrade's competence, partners recognising the qualification, can do so with reason.

Recognition is the trust others actually place in a qualification, and it is earned, not declared. A qualification is trusted to the degree that the authority and control behind it are sound: that its standard is owned and right, that it was properly approved, that it is delivered and assessed honestly and consistently (TRG 310's reliability and the integrity of the standard), and that the record of who holds it is reliable (ADM 220). A qualification with weak governance behind it may carry an impressive name and certify nothing, because nothing reliable stands behind the name; a qualification with sound governance is trusted even if modest, because what it claims is real. For a young Army earning its standing, this matters greatly: its qualifications are trusted, internally and by any partner, exactly to the extent that the governance behind them is real, which is one more reason the honesty of the whole training system matters.

This is also where cooperation and mutual recognition enter: a small force can extend the reach of its training by aligning its standards with recognised external ones and seeking mutual recognition, so that its qualifications are trusted beyond its own borders and it can in turn trust others'. But mutual recognition rests entirely on the governance: others will recognise a qualification only if the authority and control behind it are sound, so good governance is the price of recognition. A qualification, in the end, is worth precisely what its governance makes it worth.

Configuration control: keeping the standard stable and current

A standard must be at once stable and current, and these pull against each other: stable, so it can be relied on and does not shift under people's feet; current, so it keeps pace as doctrine, equipment, and law change. Configuration control is what reconciles them: the disciplined management of changes to a standard or course, so that it changes only through a controlled process, by the authority of its owner, and its version is always known. With configuration control, a standard is stable between changes and changes only deliberately and visibly; without it, a standard drifts informally, different people running slightly different versions, no one quite sure what the current standard is, which is as bad as having no standard at all.

The discipline has a few elements. Changes are made only by or with the authority of the standard owner, not by whoever is running the course this week, so the standard does not erode through a thousand small unauthorised adjustments (the normalisation of deviance the safety course warned of, applied to standards). Each change is deliberate and recorded, so that the standard's current version is always known and everyone runs the same one. Significant changes are themselves approved, like the original, because a changed standard is a new standard and needs the same authority. And the change is propagated: when the standard changes, the materials, the assessment, and the people are updated together, so the course as delivered stays aligned with the standard as written, closing the gap the implementation lesson warned of. Configuration control is, in effect, the maintenance of standards (Lesson 05) given a formal mechanism, and it is what lets a standard live, changing as it must, without dissolving.

Underpinning recognition and control alike is the training record (ADM 220): the durable, reliable record of who holds which qualification, to which version of which standard. The record is the proof that makes a qualification real and auditable; a qualification no record can confirm is a claim, not a certified fact. So governance and records are partners: governance sets and controls the standard, and the record captures who has met it, and together they make the qualification a trustworthy, provable thing.

In Practice: Giving a Standard an Owner and an Authority

A course designer of the Royal Army College has designed an excellent course, and a junior member assumes the work is therefore done. The designer knows it is not, because a course is not the Army's standard until it is governed, and she walks the course through the governance this lesson describes.

She does not treat the design as in force; she presents it for approval as a clear specification, the need, objectives, design, standard, safety, and deliverability set out so the proper training authority can actually check it, and she holds it explicitly as draft, for command approval until that authority has checked it against the need and the job, satisfied itself it is sound, safe, and deliverable, and adopted it. Only with that approval does the course become the Army's standard rather than her proposal, and only then does its qualification carry authority. She ensures the standard has a named owner responsible for keeping it, so it will not drift ownerless, and she respects the separation of duties: she designed it, but she is not its sole approver or assurer, because no one should mark their own work, and where the small force forces her to wear more than one hat she is honest about it and protects the separations that matter most, the approval and the appeal.

She sets up configuration control so the standard will change only deliberately, by the owner's authority, with its version always known and its materials, assessment, and people updated together, rather than drifting informally into a dozen private versions. She ties it to the training record (ADM 220), so that who holds the qualification, to which version of the standard, is reliably recorded and provable. And she designs with recognition in mind, aligning where she can with standards others trust, knowing that the qualification will be worth exactly what its governance makes it worth. The course is now not just well designed but properly governed: owned, authorised, controlled, recorded, and trusted, which is what turns a good design into a real qualification that the Army and its partners can rely on.

Check Your Understanding

Explain why a standard needs an owner and an authority, and what each supplies. Why is a standard that is "everyone's responsibility" no one's, and what does the "draft, for command approval" marking on the College's standards signify?
Describe what approval is and why it is a real check held by command and staff authority rather than the designer, and how a designer designs toward approval. Then explain separation of duties, the principle that "no one should mark their own work," and how a small force handles it honestly.
Explain accreditation and what makes a qualification trusted (owned standard, proper approval, honest delivery and assessment, reliable record), and why this matters especially to a young Army and to mutual recognition. Then explain configuration control and how it keeps a standard both stable and current.

Reflection (write a short paragraph): This lesson says a qualification is worth precisely what its governance makes it worth, and that a young Army's qualifications are trusted exactly to the extent that the authority and control behind them are real. Think about a qualification or certificate you hold or have seen: what made it trusted, or not, the authority behind it, the rigour of its standard, the reliability of its records? Then consider the challenge for a small force where the same few people may design, deliver, and assess: which separations of duty would you fight hardest to protect even when people are scarce, and why?

Summary

Training governance gives a standard the four things it needs to be real and trusted: an owner (an appointment responsible for setting and keeping it, so it does not drift ownerless), an authority (command/staff authority that makes it official, not one person's view), controlled change, and accreditation. A standard without owner, authority, and control is not really a standard.
A course passes from proposal to the Army's standard through approval: a real check by the proper training authority, who satisfies itself the course meets the need and is sound, safe, and deliverable, and stands behind the qualification. The College's "draft, for command approval" marking makes this visible; the designer designs toward approval and presents a clear specification.
Separation of duties distributes the roles, designer, approving owner, deliverer, assessor, assurer, so that no one marks their own work. A small force cannot always separate everyone, but protects the separations that matter most (approval and assurance not by the designer alone; appeals heard independently) and is honest where it cannot.
Accreditation makes a qualification a believable promise by tying it to an owned standard, proper approval, and controlled delivery and assessment. Recognition is earned, not declared, and rests on the governance behind the qualification; for a young Army, and for mutual recognition with partners, qualifications are trusted exactly to the extent the governance is real.
Configuration control keeps a standard both stable and current: changes made only by the owner's authority, deliberate and recorded, significant ones re-approved, and propagated to materials, assessment, and people together, so the course as delivered stays aligned with the standard as written. The training record (ADM 220) proves who holds which qualification to which version, making it real and auditable.
This is the knowledge layer; the exercise of training authority, owning standards and approving courses, is a command and staff responsibility carried out by those holding the proper appointments. This lesson sits the design, implementation, and standards of the whole course within a framework of authority and control, connects to ADM 220 (records), LDR 420 (the integrity of the standard), and PME 510 (cooperation and the small force), and is closed by the evaluation of Lesson 10.

Governance, Standards Authority, and Accreditation