Mandatory Compliance Training vs CPD: What's the Difference?

"Compliance training" and "CPD" get used almost interchangeably in a lot of healthcare workplaces, and that's a mistake — they're built on genuinely different logic, answer to different authorities, and failing to tell them apart tends to produce muddled training plans where neither obligation gets tracked properly. This post explains the actual conceptual difference, not just a list of examples.

The core distinction

Mandatory compliance training exists because a law, regulation or your employer's own risk policy requires it — it's imposed, non-negotiable, and typically the same for everyone in a given role regardless of experience or specialty. CPD (Continuing Professional Development) exists because a professional body requires practitioners to keep developing their competence to remain registered — it's still mandatory in the sense that you must complete it to keep your registration, but it's individually directed, tied to your own scope of practice and career stage, and the content is substantially up to you to select within your regulator's framework.

Put simply: compliance training answers "what does the law or our organisation require everyone in this role to know?" CPD answers "what do I, specifically, need to keep learning to remain safely and currently competent in my own practice?"

Side-by-side comparison

Where the two genuinely overlap

The confusion is understandable because some content counts toward both categories at once. A safeguarding module might be mandated by your employer as compliance training and simultaneously count toward your CPD hours if your regulator recognises it as structured learning. That overlap is legitimate and useful — it's efficient to design training that satisfies both obligations where the content genuinely fits — but it doesn't mean the two categories have merged. The overlap is coincidental content, not a shared underlying purpose. A piece of training can satisfy your CPD requirement for the year and still not satisfy your employer's separate, specific compliance obligations (and vice versa) if the content doesn't line up with both sets of criteria.

Why organisations mix them up — and what it costs

• One tracking system, two obligations. Many organisations run a single LMS report for "training completed" without distinguishing which records satisfy compliance requirements versus CPD requirements — which means neither obligation is actually verifiable in isolation when an auditor or regulator asks specifically about one.
• Staff assume compliance training "counts" for CPD without checking. Not all mandatory compliance training meets a regulator's structured CPD criteria — assuming it does, without confirming against your specific regulator's rules, can leave a practitioner short on CPD hours at registration renewal despite having completed plenty of workplace training.
• CPD gets deprioritised because compliance feels more urgent. Compliance training often comes with an internal deadline and escalation; CPD, being more self-directed, can quietly slip until close to a registration renewal date, creating a last-minute scramble that a clearer separation of the two tracks would prevent.

How regulator-specific CPD requirements differ

Beyond the general employer-vs-regulator distinction covered here, the specific CPD rules themselves vary significantly between professional bodies — required hours, the ratio of structured to unstructured learning, and mandatory topics all differ. Our comparison of CPD requirements across NMBI, the Medical Council, CORU and PSI breaks down exactly how those regulator-specific rules compare, which is the natural next step once the compliance-vs-CPD distinction covered here is clear.

Building a training plan that keeps both straight

The practical fix is straightforward: tag every piece of training in your tracking system against both categories separately — mandatory compliance (yes/no, and which specific requirement it satisfies) and CPD-eligible (yes/no, and how many structured or unstructured hours it counts toward, per your regulator's rules). That single change makes it possible to answer "are we compliant?" and "is this practitioner on track for their CPD renewal?" as two distinct, verifiable questions, rather than one blended and ultimately unreliable answer.

Learnsignal's CPD courses are built and mapped against specific regulator frameworks for exactly this reason — so the CPD hours a practitioner earns are clearly documented against the criteria their own registration body actually requires, rather than left ambiguous.

Frequently asked questions

Does completing mandatory compliance training count toward my CPD hours?

Sometimes, but not automatically — it depends on whether the specific content meets your professional body's criteria for structured or unstructured CPD. Always check against your own regulator's requirements rather than assuming workplace training counts by default.

Who decides what counts as CPD — my employer or my professional body?

Your professional registration body sets the CPD requirement and the criteria for what counts. Your employer may provide or fund training that happens to meet those criteria, but the requirement itself, and the standard it must meet, comes from the regulator.

What happens if I complete my mandatory compliance training but fall short on CPD?

The consequences are separate and don't offset each other. Falling short on CPD hours is a risk to your professional registration specifically, regardless of how compliant you are with your employer's separate mandatory training requirements.

Compliance training and CPD both matter, and good training programs deliberately satisfy both — but they exist for different reasons, are governed by different authorities, and need to be tracked as two distinct obligations rather than one blended training record.