---
name: continuing-professional-development
description: Use when asked to plan or evidence continuing professional development (CPD) — a CPD log/portfolio, reflective practice, or setting individual development goals — as an individual practitioner activity, as distinct from the organizational People & OD function that supports it (see people-and-organizational-development) or a specific framework's own CPD checklist (see united-kingdom-government-digital-and-data-profession-capability-framework for one real example).
---

# Continuing Professional Development

Continuing professional development (CPD) is the ongoing, deliberate
maintenance and growth of an individual's professional knowledge and
skill after formal qualification — an individual practitioner discipline,
distinct from [[people-and-organizational-development]]'s
organizational responsibility for L&D infrastructure, though the
organization typically supports and sometimes requires it.

## Why CPD is structured, not incidental

Many professions (law, medicine, accountancy, engineering, teaching) and
several published frameworks require CPD as a condition of continued
registration/certification — the underlying reasoning applies more
broadly, though: a professional's knowledge decays in relevance as the
field moves, and deliberate, tracked development counters that in a way
informal "keeping up" rarely does on its own, because informal learning
is easy to defer indefinitely under day-to-day work pressure.

## The reflective cycle

CPD is most effective structured as a repeated cycle, not a one-off
activity log:

1. **Reflect** — what's a real gap or growth area, grounded in actual work
   experience (a project that went badly, a skill a role increasingly
   demands) rather than an arbitrary course catalog choice.
2. **Plan** — a specific, time-bound learning goal and the activity meant
   to close the gap.
3. **Act** — the learning activity itself (a course, mentoring, a stretch
   assignment, reading, a conference, structured practice).
4. **Evidence and reflect again** — what changed as a result, and what
   that reveals about the next gap — closing the loop back to step 1
   rather than treating the activity as the end point.

Kolb's experiential learning cycle (concrete experience → reflective
observation → abstract conceptualization → active experimentation) is a
widely-referenced formal version of the same underlying idea.

## CPD logs and portfolios

A CPD log records activities (what, when, how long, what was learned); a
CPD portfolio goes further, curating evidence (work samples, reflective
write-ups, feedback received) that demonstrates the learning actually
applied, not just attended — many professional bodies specifically
require evidence of impact/application, not just a list of hours logged,
because hours logged without applied impact is a weak proxy for actual
development.

## Individual development goals

Effective CPD goals connect to both the individual's own career direction
and the organization's actual needs — a goal set in isolation from either
tends to either not get supported (no organizational relevance) or not
sustain motivation (no personal relevance). Cross-reference against a
published capability framework where one exists for the discipline — see
[[united-kingdom-government-digital-and-data-profession-capability-framework]]
for a real, published example (the UK GDaD PCF) that includes CPD
checklists per role level, useful as a concrete worked template even
outside that specific framework's own domain.

## Common pitfalls

- **Logging hours without evidencing applied impact** — many CPD schemes
  (and, more importantly, the actual value of CPD) depend on the learning
  changing practice, not merely being attended; an activity log with no
  reflection or evidence of application is a weak record.
- **Choosing development activities from a catalog rather than a genuine
  reflected gap** — courses picked because they're available/convenient
  rather than because they close a real identified need produce lower
  transfer to actual practice.
- **Treating CPD as compliance only** — doing the minimum to satisfy a
  registration requirement, disconnected from any real reflective cycle,
  captures the letter of a CPD obligation while missing its actual
  purpose.
- **No connection to organizational needs or career direction** — an
  isolated development goal is harder to get supported and harder to stay
  motivated to complete.
- **Confusing individual CPD with the organization's L&D responsibility**
  — see [[people-and-organizational-development]] for that
  distinction; an organization providing L&D infrastructure doesn't
  replace the individual's own reflective ownership of their development.

## Learn more

- [CPD Institute](https://cpdstandards.com/) and most professional bodies' own CPD guidance (varies by profession/jurisdiction — check the specific body's current requirements).
- [Kolb's experiential learning cycle](https://www.simplypsychology.org/learning-kolb.html) — a widely-referenced formal model of the reflective cycle above.
- [[united-kingdom-government-digital-and-data-profession-capability-framework]] for a real, published framework with per-role-level CPD checklists.
- [[people-and-organizational-development]] for the organizational L&D function CPD sits alongside.