For providers
How to write learning outcomes that pass CPD accreditation
Published 29 August 2026 · 5 min read
Alongside inflated hour claims, vague learning outcomes are the single most common reason a course only partially clears assessment. The good news is the fix is straightforward: swap aspirational verbs for demonstrable ones, and make sure the content actually covers what the outcome says. Here's exactly how the standard is written, and how to meet it first time.
The short answer: a learning outcome should describe a specific thing a learner can do, or correctly identify, or demonstrate, on completion — not something they'll "appreciate" or "gain an awareness of". If an assessor couldn't design a check for it against your course content, it's an aspiration, not an outcome. Rewrite it.
What the standard actually says
AssuredCPD's Standards Framework defines it precisely, in the domain covering learning outcomes:
"Outcomes are specific, measurable, and achievable through the course. A learner can reasonably be expected to demonstrate each outcome on completion. Met when: outcomes are written as demonstrable capabilities (not vague aspirations) and are covered by the content."
Two tests are embedded in that: demonstrable (a learner can show it, an assessor can check it) and covered by the content (the course actually teaches what the outcome claims). Miss either and it scores Partially met.
The verb test
The single fastest way to spot a weak outcome is to look at the verb. Aspirational verbs describe internal states no one can verify; demonstrable verbs describe observable behaviour. Compare:
| Weak (aspirational) | Stronger (demonstrable) |
|---|---|
| Understand UK GDPR | Correctly classify personal data under UK GDPR in five realistic scenarios |
| Appreciate the importance of safeguarding | Identify three statutory safeguarding responsibilities that apply to your role |
| Be aware of infection control | Demonstrate hand hygiene technique to the WHO five-moment standard |
| Gain an understanding of team dynamics | Describe two ways role clarity reduces team conflict, with an example |
| Learn about active listening | Use one active-listening technique in a recorded roleplay and describe its effect |
Notice the pattern on the right: each outcome names a specific action (classify, identify, demonstrate, describe, use), an object (personal data, responsibilities, technique), and often a condition or standard (five scenarios, to the WHO five-moment standard, with an example). That's what makes it checkable.
The four verbs to avoid
Not a hard rule, but a useful heuristic: if the main verb of your outcome is understand, appreciate, be aware of, or gain an understanding of, the outcome is almost certainly too soft to pass on its own. Not because those things aren't real learning — they are — but because they don't describe anything anyone can observe or check.
Rewrite them by asking: if a learner really understood this, what would they be able to do? The answer is your outcome.
The coverage test
The second half of the standard — "covered by the content" — catches a different failure mode: outcomes that sound great on their own but describe more than the course teaches. A common version is aspirational lift: writing outcomes that promise application in complex real-world settings when the course only presents the underlying concept.
The check is mechanical: for each outcome, point to where in the course a learner would acquire that capability. If the answer is "well, they'd extrapolate" or "it's implicit", the outcome overreaches and needs either scaling back to what the course really teaches, or adding content that actually covers it.
How many outcomes to write
There isn't a required number. The right count is however many it takes to describe what the course teaches — no more. In practice:
- A one-hour micro-course: usually 2–4 outcomes
- A half-day session: 3–6
- A full-day workshop: 5–8
- A multi-week programme: 6–12, often grouped by module
These are guidelines, not rules. Ten outcomes on a one-hour course reads as padding; two on a full-day workshop reads as thin. Match the count to the real weight of what learners will take away.
A quick five-minute audit before you submit
Before you press submit on your application, run each outcome through these five questions:
- Verb check. Is the main verb demonstrable (identify, describe, calculate, demonstrate, use, produce) rather than aspirational (understand, appreciate, be aware)?
- Specificity check. Does the outcome name what, to what standard, or under what conditions? Not just use — use X in Y situation.
- Content check. For each outcome, can you point to the module, slide, or exercise where it's taught? If not, either add that content or trim the outcome.
- Assessability check. Would a competent assessor be able to write a quiz question, task, or observation checklist that tested this outcome directly? If not, it's still too fuzzy.
- Match to hours check. Does the number of outcomes match the claimed course length? Too many for a short course, too few for a long one, both attract questions — and we've covered the related risk in our article on CPD hours.
What this doesn't mean
None of the above requires jargon, taxonomies, or formal instructional-design language. Bloom's Taxonomy is a useful reference when you're stuck for a verb, but the Standards Framework doesn't ask for it. Plain English that's specific and honest passes; formal-sounding language that hides aspirational verbs behind long noun phrases does not. The test is always the same: could someone check whether the learner can do it?
FAQ
What is a learning outcome?
A learning outcome is a specific, demonstrable capability a learner is expected to have after completing a course. Under AssuredCPD's Standards Framework it must be written as a demonstrable capability rather than a vague aspiration, and the course content must actually cover it. "Understand data protection" is an aspiration; "Correctly identify personal data under UK GDPR in five realistic scenarios" is an outcome.
How many learning outcomes should a CPD course have?
There is no fixed number — the right count is however many it takes to describe what the course actually teaches, and no more. A one-hour micro-course typically has two to four outcomes; a full-day workshop, five to eight. Padding a short course with ten outcomes signals that the outcomes aren't taken seriously; too few for the material can look thin.
Why are learning outcomes a common reason courses fail accreditation?
Because the two easiest mistakes to make are also the two an assessor catches fastest: outcomes written as fuzzy aspirations ("appreciate", "be aware of", "gain an understanding") that no assessor can check against the content, and outcomes that don't match what the course actually covers. Both produce a Partially met score on the Learning outcomes domain until they're rewritten.
Do I need to use Bloom's Taxonomy for CPD learning outcomes?
No. Bloom's Taxonomy is a useful reference when you're stuck for a verb, but AssuredCPD's Standards Framework does not require it. What the framework does require is that outcomes be specific, measurable, and demonstrable through the course. If your outcomes achieve that in plain English, they don't need a taxonomy label.