Reflective Writing at CIPD Level 3, 5 and 7: What Changes

Reflective writing is the one skill every CIPD learner carries through the whole qualification. The units change, the briefs change, the expected depth changes, but the core act stays the same: examining your own real experience honestly and converting it into learning and action. What trips learners up is pitching that skill at the wrong altitude, writing Level 3 description in a Level 7 unit, or dressing a Level 3 account in postgraduate vocabulary it cannot carry.

This guide maps how reflective writing at CIPD levels 3, 5 and 7 differs, what stays constant, and how to check your own pitch, including one fictional incident written acceptably at all three depths. It assumes the fundamentals covered in the pillar guide What Is a CIPD Reflective Account and How to Write One, and as ever, your current assessment brief and your study centre's guidance are the final word on what your unit actually requires.

Level 3: honest description plus genuine learning

At Level 3, assessors want genuineness and clarity. The expectation is honest first-person description of a real situation, simple learning stated plainly, and clear next steps. Nobody is looking for named models, theory or sophisticated self-analysis; they are looking for evidence that you noticed something true about your own practice and intend to act on it.

The best Level 3 reflection uses small, real examples: a task that went wrong, a conversation that landed badly, feedback you did not expect. Write what happened, what you felt and noticed, what you learned in plain words, and what you will do next. The commonest failure at this level is not lack of depth but lack of genuineness, accounts that sound copied from a textbook rather than lived. For the wider Level 3 context, including how the foundation units are assessed, see 3CO03 Assignment: The Complete Guide.

Level 5: analysis and evidence of change

Level 5 keeps everything Level 3 asked for and adds analysis. Description alone is no longer enough: your behaviour must be connected to its outcomes, so that every choice you describe is traced to its effect on other people and on results. Why did you act that way, what assumption was driving you, what did your choice do to the room, and how do you know?

A reflective model earns its place here as light scaffolding, shaping paragraphs without becoming their subject, and assessors expect evidence that your practice actually changed: something you now do differently, described concretely, with honest observation of the difference it made. The dedicated guide 5CO03 Reflective Writing: How to Evidence Your Examples covers this standard in unit-specific detail.

Level 7: critical reflection

Level 7 keeps the analysis and turns it on your own thinking. Critical reflection questions the assumptions beneath your actions: not just why did I do that, but why did I frame the situation that way at all, what was I taking for granted, and whose perspective is missing from my account. Theory enters as a lens brought to bear on your own behaviour at the moment it explains or challenges something, never as decoration.

Two further expectations mark the postgraduate standard: change in practice that can be evidenced rather than merely claimed, and a degree of self-scepticism, meaning the account doubts its own first reading of events and says so on the page. 7CO03 Reflective Writing at Masters Level shows what this looks like in practice, including how to hold first person and academic rigour together.

One incident, three levels

The clearest way to see the differences is the same event written three ways. Carys is an invented team leader at Bryn and Mercer, a made-up conveyancing firm, and the incident is entirely fictional: in a monthly team meeting she announced a new rota as a settled decision, two colleagues objected, and she closed the discussion down, leaving the meeting flat and the team unhappy.

An acceptable Level 3 account

I announced the new rota in our team meeting as a decision that had already been made, because I was worried a discussion would take the whole hour. Two colleagues objected and I cut the conversation short, saying we would pick it up later, which I never arranged. The rest of the meeting felt flat, and afterwards one colleague told me the team had not felt listened to, which was hard to hear because she was right. I learned that saving time in the meeting cost me more time and goodwill afterwards, and that my team take decisions better when they hear the reasons first. Next month I will send the draft rota out before the meeting and keep ten minutes for questions.

The same incident at Level 5

When I announced the new rota as settled and two colleagues objected, I closed the discussion down, and the more useful question is why. I had framed the meeting as a delivery task rather than a consultation, because I was assuming that pushback simply meant delay, and shutting the conversation down told the team their input was a problem to be managed. The effect showed immediately: contributions dried up for the rest of the agenda, and a colleague's comment afterwards that the team felt unheard matched what I had seen in the room but chosen not to act on. I have since changed how decisions reach my team: the draft goes out in advance, meetings open with objections instead of ending with them, and the two meetings since have carried noticeably more challenge and less resentment. The habit I am still working on is treating disagreement as delay, and I have asked my manager to watch for it and tell me honestly.

The same incident at Level 7

What troubles me about the rota meeting is not the decision but the frame I brought to it: I had defined an efficient meeting as one without discussion, an assumption imported from a previous role and never examined. Schön's distinction between reflection-in-action and reflection-on-action is uncomfortable to apply here, because I did register the room's reaction in the moment and overrode it, which means the failure was not one of awareness but of a frame that ranked pace above voice. Read from my colleagues' side, the meeting was efficient at exactly one thing: signalling that consultation was theatre. I am wary of overcorrecting into performative openness, so the change I made is structural rather than tonal: decisions affecting working patterns now go to the team as open questions with the constraints stated, and the different register of the two meetings since, along with one colleague's unprompted remark that the process felt fairer, suggests the shift has been noticed. The real test will be the first decision where I cannot afford to consult, and I do not yet know how I will handle that.

What changed between the versions

Notice what moves and what does not. All three accounts describe the same honest failure in the first person and end with action. The Level 3 version tells the truth plainly and learns something real. The Level 5 version explains the behaviour, traces its effect on others and evidences a change. The Level 7 version questions the frame behind the behaviour, uses theory where it earns its place, considers the other side of the room, doubts its own correction and still ends on an open question. The depth of thinking rises; the honesty is constant.

What stays constant at every level

• A genuine experience from your own practice, because invented material fails at every level for the same reason
• First person throughout, since your own behaviour and thinking are the object of assessment
• Honesty about imperfection, which assessors read as self-awareness rather than weakness
• Learning that leads to action concrete enough for a reader to check later

A self-check for pitching your level

1. Reread your brief and your centre's guidance and note the exact reflective requirement, because units differ even within a level.
2. Measure your description: more than half the words at Level 5 or above means the account is pitched too low.
3. At every level, confirm the account is in the first person and describes something that genuinely happened to you.
4. At Level 5 and above, check that every behaviour you describe is connected to an effect on someone, with your evidence for it.
5. At Level 7, confirm you have named and questioned at least one assumption of your own, and used any theory as a lens rather than decoration.
6. At any level, check the ending: a specific action a reader could verify later, not a general intention to improve.

Common pitfalls

• Writing below your level, usually careful description at Level 5 or 7 with the analysis left implicit
• Importing Level 7 jargon into Level 3, where borrowed vocabulary reads as inauthentic and buries the genuine learning
• Recycling the same account across units, which assessors notice and which stops the reflection answering the brief in front of you
• Treating the levels as writing styles rather than depths of thinking, and polishing the prose instead of pushing the analysis
• Choosing a grand but distant example when a small incident you actually own would carry far more insight

Go deeper

The pillar guide What Is a CIPD Reflective Account and How to Write One covers the fundamentals beneath all three levels, including structure, evidence and a step-by-step method. Its companion, Reflective Models Compared: Kolb, Gibbs, Driscoll and Schön, will help you choose scaffolding suited to your level and your material. For unit-level depth, see 3CO03 Assignment: The Complete Guide, 5CO03 Reflective Writing: How to Evidence Your Examples and 7CO03 Reflective Writing at Masters Level.

Pitching reflection at the right depth is far easier with an experienced outside reader, and that is exactly what our reflective writing support offers: level-aware coaching on structure and analysis, plus honest review of your drafts, with the experience and every word of the account remaining your own.