How to reflect on podcasts and videos for CPD

Yes, when they contribute to your professional learning. You might gain a new perspective, understand an existing approach more clearly or recognise a question worth exploring. The useful part may be a short exchange or demonstration within a longer recording.

For HCPC registrants, the HCPC's activity guidance includes self-directed and online learning and emphasises relevance to practice. Follow your own regulator's or employer's requirements for recording activities, evidence and hours.

You may already be reflecting as you listen: connecting an idea to an experience, questioning a claim or recognising why something has worked. Writing gives you a way to explore that thinking and return to it. You do not need to produce a synopsis of the whole recording.

• What caught your attention, and why?
• How does it fit with what you already know or do?
• What did it challenge, clarify or reinforce?
• What remains uncertain, and is there anything you want to explore further?

A confident speaker can make an idea sound convincing. Consider the evidence behind the claim and whether it applies in your setting. A video demonstration may leave out the difficulties, decisions or context that shape the same task in practice.

A summary: “The video explained how to make presentation slides clearer.”

A reflective note: “I realised I use my slides as both a live explanation and a reference document. That may explain why I find it difficult to decide what to leave out.”

You might leave with a clearer reason for continuing an approach, rather than a change to make. You do not need to invent an action. A brief note may be enough; if you want a structure for your thinking, the Rolfe model or Gibbs reflective cycle can help you explore it further.

This fictional example follows a physiotherapist listening to a podcast about patient communication. The episode and reflection are invented to illustrate the thinking process.

What caught my attention

The discussion made me think about the difference between giving a clear explanation and knowing how someone has understood it. I often finish an explanation by asking, “Does that make sense?” I had treated a positive response as a reasonable indication that I had communicated clearly.

The assumption I started to question

I realised that the response tells me little about what the person has taken from the conversation. I may be judging the clarity of my explanation mainly from my own perspective. The episode prompted me to question that assumption, but it cannot tell me what any particular patient understood or whether my communication needs to change in every situation.

What I want to explore

I want to discuss this in supervision and consider how I currently check understanding, including what feedback could help me judge my communication more thoughtfully. For now, my learning is recognising the assumption. I have not yet evaluated a different approach or established any effect on patient outcomes.

Why this works: the reflection identifies a familiar habit, examines the thinking behind it and explains what remains uncertain. It keeps the learning separate from an outcome that has not happened.

In this fictional example, a team leader watches a demonstration of how to make presentation slides easier to follow.

What I noticed

I watched the section comparing a crowded slide with a version built around one main point. I had assumed that including all the detail helped colleagues refer back to my presentation. Seeing the examples made me question whether the slides were doing too many jobs at once.

How it relates to my work

My learning was to separate the message I need people to follow during a session from the detail they may need afterwards. The demonstration did not tell me what every colleague would find accessible, so I will ask about their needs rather than assume one design suits everyone.

A small experiment

I will revise one section of my next presentation and offer the supporting detail separately. I will ask colleagues whether the main point was clear and whether they could find the detail they needed. Their feedback will help me decide what to retain or change.

Why this works: a visual comparison helps the viewer recognise a problem in their own work. The reflection leads to a small experiment whose usefulness can be reviewed. The podcast example opens a question for discussion; this one proposes something to try.

Use your existing notebook, document or CPD system. The aim is to be able to find the source again and understand what you took from it. A simple record can include:

• The source: title, creator or provider, link, date you listened or watched, and a useful timestamp.
• Your learning: the idea that stood out and why it matters to your work.
• What follows, if anything: a question, something to continue or try, or a point to revisit. Keep planned actions distinct from completed ones.
• Supporting evidence: your notes and any certificate or attendance record supplied, with further evidence where your requirements call for it.

If you report hours, record the time you actually spent learning rather than automatically using the full running time. Follow the applicable rules for any separate reading, discussion or reflection, and avoid counting the same time twice. Describe a recording watched alone accurately; it is different from taking part in a discussion.

Keep materials you have permission to save and leave out identifiable patient, client or colleague details. For demonstrations of practical or clinical techniques, distinguish what you observed from skills you have practised or demonstrated yourself.

For the team leader in the video example, the useful starting point is their own observation about slides serving two purposes. Here is how they could keep that learning in HandyCPD:

1. Capture the starting point. In Plant a Seed, add the video details, learning time and a few notes about what they noticed and want to try.
2. Review the draft. Check the suggested activity details and summary. Make sure the presentation changes are described as a plan, with no invented feedback or results, then file the record.
3. Return to the learning. Use the saved record as a starting point when reviewing the presentation feedback. If there is more to explore, the Reflection Engine can help structure a fuller reflection for them to review and edit.

The CPD logging walkthrough shows the capture and review process in more detail.

Do not assume that adding a podcast or video link means HandyCPD has listened to or watched the whole recording. Include the relevant learning in your own notes and check any generated wording against what you actually learned. See what HandyCPD reads from files and links for the current limits.

What if I disagreed with the speaker?

Record the specific claim, your reason for questioning it and what evidence you checked or still need to consult. A disagreement can be a starting point for learning without becoming a conclusion that either person must be right.

Can I use an AI summary as my reflection?

A summary can help organise information, but it cannot establish your personal learning or verify that you completed an activity. Write about your own understanding and review any AI-assisted draft before filing it. Our guide to writing a CPD reflection explains the distinction in more detail.