5CO03 Reflective Writing: How to Evidence Your Examples

The reflective element is the part of 5CO03 that learners worry about most, and the part where referred work most often falls down. You are asked to write about yourself, in the first person, analysing your own behaviour, and nothing else in a CIPD qualification quite prepares you for that. Many capable writers respond by describing events in careful detail and hoping that counts as reflection. It does not, and assessors can tell the difference in a single paragraph.

The good news is that reflective writing is a learnable technique, not a personality trait. This guide shows you how to choose examples worth reflecting on, how to use a reflective model without letting it take over, how to move from describing events to analysing behaviour, and what strong reflection looks like at sentence level, including a worked comparison of a weak and a strong paragraph.

In this guide you'll learn

• How to choose real workplace examples that give your reflection something to work with
• How Kolb, Gibbs and Driscoll differ, and how to apply one without describing it
• The shift from recounting events to analysing behaviour and learning
• Sentence-level habits that make first person reflection sound analytical rather than chatty
• The pitfalls that make reflective accounts read as thin, generic or fabricated

Start with real examples worth examining

Reflection is only as good as its raw material. Before you write anything, gather a shortlist of genuine situations from your own practice that involved ethics, inclusion, wellbeing, relationships or your own learning. The best candidates share one quality: friction. A disagreement you handled imperfectly, a decision you hesitated over, feedback that stung, a process you got wrong before you got it right. Situations where everything went smoothly rarely reveal much about your behaviour, because nothing was tested.

Be honest about scale too. A small, real moment, such as realising mid-meeting that you had talked over a quieter colleague, gives you far more to analyse than a grand initiative you only observed from a distance. Assessors are looking for depth of insight, not seniority of example.

Reflective models, and how to hold them lightly

Three models cover most needs. Kolb's learning cycle frames learning as a loop: concrete experience, reflective observation, abstract conceptualisation, active experimentation. Gibbs' reflective cycle adds an explicit emotional step, moving through description, feelings, evaluation, analysis, conclusion and action plan, which suits situations where your reaction was part of the story. Driscoll's model is the simplest: What, So what, Now what. What happened, what did it mean, what will you do differently.

Pick one and use it as scaffolding, not subject matter. A common failure mode is spending a hundred words explaining what Gibbs' cycle is and then fifty words actually reflecting. The model should shape your paragraphs invisibly: a sentence or two of description, then meaning and analysis, then future action. Name the model once if your brief expects it, then let it disappear into the structure. If a marker can see your thinking developing through the account, the model has done its job whether or not it is mentioned again.

From describing events to analysing behaviour

The single biggest upgrade in reflective writing is changing the question your sentences answer. Description answers what happened. Analysis answers what it reveals. After every descriptive sentence, push yourself with follow-up questions: why did I respond that way, what assumption was I making, what was the effect on others, what does this tell me about how I work, and what would I do differently now.

Notice that the analytical questions are about you, not about the event. A paragraph can be full of sharp observations about a difficult restructure and still contain zero reflection if the writer never appears in it. In 5CO03 the unit of analysis is your behaviour: your choices, your assumptions, your habits, your growth. The event is just the setting.

Learning statements need the same discipline. I learned the importance of communication is a description of a cliché, not learning. Real learning is specific: I learned that I default to email when a conversation feels difficult, and that this delays resolution and reads as avoidance. Specific learning also feeds naturally into development planning, because it points at a behaviour you can actually change.

Sentence-level guidance

First person is expected in reflection, so use it without apology: I decided, I assumed, I misjudged. Writing around yourself in the passive voice, as in it was decided that, hides exactly the agency the assessor needs to see. Keep sentences short and concrete. Prefer verbs that own the action, including the uncomfortable ones: I avoided, I underestimated, I delayed. Honest verbs are what make reflection credible.

Balance matters too. An account that is all self-criticism reads as performance, and one that is all triumph reads as advertising. Aim for a fair audit: what worked, what did not, and what you are doing about it. Finally, keep some emotional honesty without turning the account into a diary entry. I felt defensive when the feedback arrived is useful data if you then analyse what the defensiveness did to your listening.

Structuring a reflective entry

1. Set the scene in two or three sentences at most: the situation, your role, and why it mattered.
2. State what you did and what happened, keeping the description tight and factual.
3. Analyse your behaviour: why you acted as you did, what assumptions or habits were driving you, and what effect your choices had on others.
4. Draw out the learning as something specific about you, not a general truth about workplaces.
5. Commit to action: what you will do differently, how, and how you will know it is working.
6. Link the entry to your development plan so the account and the plan clearly belong to the same person.

Worked example: weak versus strong

Both paragraphs below are fictional and describe the same invented situation, a learner named Sam handling a flexible working request.

Weak version: Last year I dealt with a flexible working request from a team member. I followed the policy and arranged a meeting with the employee and their manager. We discussed the options available and eventually agreed a compromise that worked for both sides. This showed the importance of good communication and following correct procedures, and I learned that handling requests properly is essential for employee wellbeing.

Strong version: When a team member requested compressed hours, I noticed my first instinct was to look for reasons the rota could not absorb it, because I was anticipating the manager's objections rather than assessing the request on its merits. Catching that assumption changed how I ran the meeting: I asked the employee to walk us through how the pattern would work before anyone raised problems, and the discussion became collaborative rather than defensive. The request was agreed with a review point. What stays with me is how quickly I had adopted the manager's frame without noticing, which tells me my inclusive values need conscious effort under stakeholder pressure, not just agreement in principle. I now prepare for such meetings by writing down the requester's case first, and my development plan includes seeking feedback on how I balance competing voices in meetings.

The weak version describes a process and ends on a cliché; Sam barely appears in it as a thinking person. The strong version is built around a self-observation, analyses a specific assumption, names honest learning and converts it into concrete action. It is also, tellingly, more interesting to read.

Common pitfalls

• Recounting events in detail and leaving reflection to a single final sentence
• Describing the reflective model instead of using it on an experience
• Choosing examples with no friction, which leave nothing genuine to analyse
• Generic learning statements about communication or teamwork that could belong to anyone
• All-success accounts that read as self-promotion rather than self-assessment
• Fabricated or borrowed examples, which undermine the unit's purpose and tend to collapse under an assessor's eye for specific detail
• Writing a development plan that has no visible connection to the reflections that precede it

Go deeper

This guide is part of the 5CO03 cluster. For the full picture of the unit, including how it is assessed and a step-by-step approach, start with 5CO03 Assignment: The Complete Guide. For quick answers on first person writing, models and evidence, see 5CO03 FAQs: Your Questions Answered, and for the fundamentals that apply across qualifications, read the guide on what a CIPD reflective account is.

Reflective accounts must always be your own genuine experience in your own words, and that is exactly where coaching helps most: our 5CO03 support includes reflective structure coaching and draft review that strengthen your account while keeping it authentically yours.