CPD explained
How to write a CPD reflective statement
Published 30 October 2026 · 6 min read
Short answer: a CPD reflective statement answers four questions in your own words: what you did, why you did it, what you learned or changed your mind about, and what you will do differently as a result. Most UK professional bodies that ask for reflection — the RCVS, ARB, the CII, BACP among them — are checking for that last step above all. A certificate proves you attended. A reflective statement proves you learned.
Of all the parts of a CPD record, the reflective statement is the one people put off longest and get the least guidance on. A blank box that says “what did you learn?” is intimidating precisely because it has no right length and no obvious structure. This guide gives you one: a short, repeatable method that works whether your body wants two sentences or two paragraphs.
Why bodies ask for it
Attendance is easy to fake and easy to game: sit in a room, collect a certificate, move on. Reflection is harder to fake, because it asks you to say something specific about your own practice. That is exactly why so many UK bodies build it into their CPD schemes. The RCVS requires reflection as part of its plan-do-record-reflect cycle. ARB says a recorded reflection, not a certificate, is the evidence that demonstrates compliance. The CII asks for a reflective statement answering whether the activity met your learning need and how it benefited you professionally. BACP's guidance describes a cycle of reflect, plan, act and evaluate, and says the evaluation step — what changed in your practice — is central. Different wording, same underlying test: did this change anything?
A four-question method
Whatever your body's specific template, these four questions cover what almost all of them ask for. Answer each in a sentence or two and you have a usable reflective statement.
- What did you do, and why that activity? Name the activity and the development need it was meant to address. This ties the learning to a plan, not to whatever happened to be on offer.
- What did you actually learn? Be specific. Not “I learned about data protection” but the particular point that was new to you, or that corrected something you had wrong.
- What will you do differently? This is the step most people skip, and the one assessors look for first. A concrete change — a different question you'll ask a client, a check you'll now run, a process you'll update — is worth more than a general statement that the session was useful.
- How will you know it worked? Optional for some bodies, but it is what turns a reflection into something you can revisit. A simple marker — you'll check at your next review, or ask a colleague for feedback — is enough.
A worked example
Take a one-hour webinar on handling a specific type of client complaint. A thin reflection reads: “Attended a webinar on complaint handling. Useful session.” That tells an assessor nothing beyond attendance.
A reflection using the four-question method reads closer to: “Attended a one-hour webinar on handling complaints involving a third party, chosen because I had two recent cases where I was unsure of the right sequence of steps. I learned that the first contact should go to the complainant directly, not through the third party, which is the opposite of what I had been doing. I will update my own checklist to reflect this and flag it to two colleagues who handle similar cases. I'll know it has worked if the next case I handle this way closes without a follow-up complaint about process.” Same length roughly, far more evidential weight.
What goes wrong
- Describing the content, not the learning. “The course covered X, Y and Z” is a summary of the syllabus, not a reflection. The assessor wants to know what landed with you specifically.
- Stopping at step two. Plenty of reflective statements name what was learned and go no further. The action and the check are what distinguish reflection from a book report.
- Writing it weeks later. Detail fades fast. A two-line note written the same day beats a polished paragraph reconstructed from memory at audit time.
- Including things that don't belong. Several bodies, including BACP, specifically ask members to leave out personal, confidential or identifiable client information unless an audit specifically requests it. Reflect on the learning, not the case detail.
- Making it longer because longer feels safer. Length isn't the test. A specific two-sentence answer to all four questions beats a vague half-page.
Reflection and the course itself
A well-designed course makes this easier. If the learning outcomes are written down and specific, you have something concrete to reflect against; if they're vague, you're reflecting on nothing in particular. Under AssuredCPD's Standards Framework, domain D2 requires outcomes to be specific, measurable and achievable — which is exactly the raw material a good reflective statement needs. Our guide to writing learning outcomes that pass covers the provider side of the same point.
If you are choosing between courses and your body requires reflection, a course with clearly stated outcomes and a certificate that names them (see what a CPD certificate should show) will save you time every time you come to write up what you learned.
Keep it, and keep it current
Write the reflection close to the activity, while it's still specific in your mind. Most audits, from the CII's to BACP's, are run at renewal or at random, not on a fixed annual date, so the safer habit is a short note after each activity rather than a single session reconstructing a year's worth of learning in one sitting. See our guide to how to record CPD for the record-keeping side of this.
Common questions
What is a CPD reflective statement?
A short written account of a learning activity that goes beyond attendance: what you did, what you learned, and what you will do differently in your practice as a result. Many UK professional bodies require it alongside, or instead of, a certificate.
How long should a CPD reflection be?
There is no universal length. A specific few sentences that answer what you learned and what you'll change are worth more than a long but vague paragraph. Follow your own body's template if it has one.
What makes a reflective statement weak?
Describing the course content instead of what you personally learned, and stopping before saying what you will do differently. Those two gaps are the most common reason a reflection reads as thin at audit.
Should I include client details in a CPD reflection?
Generally no. Several bodies, including BACP, specifically ask members to leave out personal, confidential or identifiable information unless an audit specifically requests it. Reflect on the learning, not the case.
When should I write the reflection?
As close to the activity as possible, while the detail is fresh. A short note written the same day is more useful, and more accurate, than one reconstructed from memory months later.
Does every professional body require reflection?
No, but many of the ones with a strong record-keeping culture do, including the RCVS, ARB, the CII and BACP. Others judge CPD on hours or a declaration alone. Check your own body's requirement.