Description versus reflection: how to turn what happened into what you learned

Most reflective accounts that get sent back, or that quietly fail to satisfy an assessor, are not badly written. The sentences are fine. The problem is subtler: the account describes what happened and then stops, just where the reflection was supposed to begin.

This is the single most common weakness in reflective writing, and it is easy to fix once you can see it. This article explains the difference between description and reflection, why both the HCPC and the NMC ask for the second and not the first, and how to make the shift in your own accounts, with worked before and after examples.

What description is, and why it is not enough

Description is the story of the event. Who was there, what you did, what happened next. It is necessary, because a reader needs enough context to follow you, but on its own it proves nothing about your learning.

Consider a clinician who writes this:

A patient became breathless during a routine appointment. I recognised the signs, escalated to a senior colleague, and the patient was reviewed and stabilised. The episode resolved without further problems.

That is a clear, competent description. The trouble is that an assessor cannot tell what the clinician learnt, whether their practice changed, or why the event mattered beyond the moment it happened. Everything in it is in the past tense and points backwards. Nothing points forward.

Both UK regulators are explicit that this is not what a reflective account is for.

What the regulators actually ask for

The NMC is direct. Its guidance on written reflective accounts asks you to record what you learnt from an event, activity or piece of feedback, how you changed or improved your work as a result, and how this is relevant to the Code. Two of those three elements are about change, not about the event.

The HCPC frames it through its standards of continuing professional development. Two of the five standards ask registrants to seek to ensure that their CPD has contributed to the quality of their practice and service delivery, and that it benefits the service user. Reflection is how you show that link. A description of an event cannot demonstrate that anything improved as a result.

In other words, the part of the account that carries the weight is not the story. It is what you did with the story.

The shift, in one question

If you take one thing from this article, take this. After you have described what happened, ask yourself a single question and answer it in writing:

So what, and what now?

• So what pushes you into meaning. Why did this matter? What did it reveal about your knowledge, your assumptions, your communication, or the system you work in? How did you feel, and did that affect your judgement?
• What now pushes you into change. What will you do differently, or keep doing deliberately? What have you read, asked, or practised since? What would you tell a colleague facing the same situation?

Everything that separates reflection from description lives in the answers to those two questions.

The same example, reflected

Here is the breathless patient account again, rewritten so that the description is the setup and the reflection is the substance.

A patient became breathless during a routine appointment. I recognised the signs and escalated to a senior colleague, and the patient was stabilised. What stayed with me afterwards was how close I came to putting the breathlessness down to anxiety, because the appointment had started as a low acuity review. I realised I had let the context of the appointment shape my expectation of the patient, which is a bias I now watch for. Since then I have revisited our escalation criteria and made a point of treating the presenting complaint on its own terms, whatever the appointment was booked as. In the following weeks I raised two concerns I might previously have talked myself out of. I now brief newer colleagues to trust the clinical picture over the appointment label.

The event is identical. The word count on the description barely changed. What changed is that the account now shows a named learning point (a bias about appointment context), a concrete change in practice (treating the presenting complaint on its own terms), and evidence that the change held (two later escalations). That is a reflective account. The first version was a report.

A practical structure that forces reflection

You do not need a particular model to reflect well, but a light structure stops you drifting back into narration. A simple four part shape works for almost any account:

1. Context. A few sentences on what happened. Set the scene, then stop. Resist the urge to keep narrating.
2. Response and meaning. What you thought and felt at the time, and what the event revealed. This is your so what.
3. Change. What you have done differently since, or decided to keep doing on purpose. This is your what now.
4. Relevance. For NMC accounts, tie it to the Code. For HCPC, show the link to the quality of your practice and to service users.

If you prefer a named model, the same principle applies. In the Gibbs reflective cycle, description is only the first of six stages, and the real substance sits in the later ones.

Common traps, and quick fixes

• The whole account is in the past tense. Reflection needs future facing sentences. If nothing in your account points to what you will do next, you have described, not reflected.
• Feelings are mentioned but not used. Saying you felt anxious is description. Explaining how that anxiety affected a decision, and what you now do about it, is reflection.
• The learning is generic. A line like "I learnt the importance of communication" could be pasted into any account. Name the specific thing you now do differently.
• Too much scene setting. If three quarters of the account is the story, rebalance. Aim for roughly a quarter description and three quarters reflection.

A note on difficult events

Reflection often draws you towards the shifts that went wrong or stayed with you, and that is legitimate and valuable. There is a line, though, between reflection and rumination. Reflection moves towards learning and a change you can name. Rumination circles the same distress without moving. If writing about an event leaves you feeling worse rather than clearer, it is a sign to pause and, if you need it, to seek support from your occupational health service, your union, or the Samaritans on 116 123, free at any time.

Getting the balance right, faster

The description versus reflection line is easy to understand and surprisingly hard to hold when you are tired and staring at a blank form. That is exactly the gap Reflectory is built for. It interviews you about your event, asks the so what and what now questions for you, and produces a reflective account in your own words, with identifiable details screened out and an AI assistance note included. You supply the practice and the insight. The tool makes sure the account shows them.