Professional bodies require CPD. None require outcomes. This isn’t negligence — it’s a rational position given the measurement infrastructure gap that has existed until recently. Understanding what professional bodies are actually optimising for explains why outcome measurement hasn’t been part of their requirements, and what would need to change for it to become one.
What professional bodies are actually managing.
A professional body’s CPD requirement exists to serve several objectives simultaneously: risk management (members maintain a baseline of current knowledge), public trust (the body can point to an ongoing development requirement when its members’ competence is questioned), and member engagement (CPD requirements keep members connected to the body’s activities and content). None of these objectives currently extend to outcome measurement, and that’s not an oversight — it’s because verifying outcomes at scale, across a membership numbering in the tens of thousands, has never had a practical mechanism. Requiring hours is auditable at scale. Requiring demonstrated practice change has not been, until recently.
The global pattern is already shifting.
This is worth stating plainly, because it changes the frame from “professional bodies are behind” to “professional bodies are already moving, and the direction is consistent.” ARB made an annual reflective statement mandatory from January 2025 — architects must map their learning to core competencies, not just log hours. RIBA moved from a points-based system to a reflective outcomes model. Engineers Australia has required reflective statements in CPD records for years, with audit every five years from Chartered status. Canadian provincial portals — the OAA, the AIBC — require descriptive “Relevance to Practice” text for every logged activity, not just a title and duration. These are not outliers. They’re evidence of a coordinated global move toward structured reflection, and that move creates demand for exactly the kind of measurement infrastructure CPD Impact provides.
Why hours became the default, and why it’s changing.
A professional body setting a CPD requirement decades ago faced the same infrastructure gap every provider and practice faced: no scalable, verifiable way to capture whether training produced practice change, so hours became the auditable proxy. That proxy served its purpose reasonably well as a baseline requirement — it ensures a minimum level of ongoing engagement with the profession. What it was never designed to do, and what nobody claimed it did, was demonstrate that CPD produces measurable competence development. The reflective-statement requirements now appearing across multiple jurisdictions are professional bodies acknowledging, implicitly, that hours alone were always insufficient — and doing something about it as verification infrastructure starts to exist.
What this piece is not arguing.
This isn’t a case that professional bodies have failed their members, or that CPD requirements have been a waste of time. Hours-based requirements did what they were built to do: establish a floor. The argument here is narrower and more constructive — professional bodies are the entities best positioned to eventually require outcome evidence, once that evidence is practical to collect, and the infrastructure for collecting it now exists. CPD Impact isn’t adversarial to professional bodies. It’s the infrastructure they could use when they choose to extend their requirements from attendance to outcome — which several already are, in different ways, right now.
What comes next.
As reflective-statement requirements spread — and the pattern suggests they will continue to — professionals and providers alike will need a practical way to generate the structured, longitudinal evidence those requirements ask for. That’s the same infrastructure this piece has described throughout: a record of what was intended, and what actually changed.
FAQs
Professional bodies’ CPD requirements are built primarily to manage risk, maintain public trust, and keep members engaged — not, historically, to verify outcomes at scale. Verifying that CPD produced practice change across a membership of tens of thousands has never had a practical, auditable mechanism, which is why attendance hours became the default proxy. That’s beginning to change as reflective-statement requirements spread across multiple bodies and jurisdictions.
Yes, in a consistent pattern across jurisdictions. ARB made an annual reflective statement mandatory for architects from January 2025. RIBA moved from a points model to a reflective outcomes model. Engineers Australia has required reflective statements in CPD records for years. Canadian provincial bodies require descriptive relevance-to-practice text per logged activity. This is a coordinated shift, not an isolated policy change.
No. Professional bodies are well positioned to eventually require outcome evidence as part of their CPD frameworks, and several are already moving toward exactly that through reflective-statement requirements. CPD Impact provides the infrastructure that makes generating that evidence practical, for members and, potentially, for the bodies themselves.
“CPD Impact is building the measurement infrastructure. Contribute to it.”
