Reflective account examples: how to write one for your portfolio

The reflective account is the most useful piece of evidence in most portfolios, because it lets you narrate your own management practice in your own words. It is also the piece learners most often get wrong — usually by describing what happened without showing their own thinking. This guide gives you a structure, a worked example, and the specific things assessors look for.

What is a reflective account?

A reflective account is a first-person written account of a real event at work, in which you explain what happened, what you did, why you did it, and what you learned. It is a recognised form of evidence for portfolio-based qualifications, including the current ILM 8723 and 8725 suites, where it sits among the permitted evidence sources.

The word that matters is reflective. A description says "we held a team meeting and agreed actions". A reflection says "I chose to open the meeting by acknowledging the team's frustration, because I judged that pushing straight to solutions would lose their buy-in — and in hindsight that decision was what turned the conversation around." The second one evidences leadership judgement. The first does not.

A structure that works

You do not need a fancy model, though you can use one (Gibbs' reflective cycle is popular). This four-part structure satisfies assessors reliably:

1. Context — briefly set the scene. What was the situation, your role in it, and what needed to happen?
2. Action — what did you do, and crucially why? This is where your reasoning goes. Use "I", not "we".
3. Outcome — what happened as a result? Be specific and honest, including anything that did not go to plan.
4. Reflection — what did you learn? What would you do the same or differently next time?

Then, separately, map the account to the assessment criteria it evidences (more on that below).

A worked example

Here is a short reflective account for a Level 3 learner evidencing aspects of managing performance. Notice how much of it is reasoning, not description.

Context. One of my team members, "J", had missed three deadlines in a month. As team leader I am responsible for managing performance, and I needed to address it before it affected the wider team's workload and morale. > Action. Rather than raising it informally in passing, I arranged a private one-to-one, because I judged that a public comment would be humiliating and counterproductive. I prepared by gathering the facts — the specific deadlines and their impact — so the conversation stayed objective rather than personal. I opened by asking J how they felt things were going, because I wanted to understand the cause before jumping to a solution. It emerged that J had been given conflicting priorities by another manager. I chose to focus on the workload conflict rather than the missed deadlines themselves, and together we agreed a shared priority list that I would confirm with the other manager. > Outcome. J met the next two deadlines. Just as importantly, J came to me early the following week when another clash arose, which told me the one-to-one had rebuilt trust rather than damaged it. > Reflection. My instinct had been to treat this as a performance problem, but the real issue was a systems problem — unclear priorities. I learned to test my assumption about the cause before acting. Next time I would clarify cross-team priorities earlier, before they become missed deadlines, and I have since introduced a fortnightly priority check-in for exactly that reason.

That account evidences several things at once: choosing an appropriate method to manage performance, understanding causes of underperformance, and reviewing and improving your own practice. That is holistic evidence, and it is efficient.

What assessors are looking for

• Your own actions, in the first person. "We" hides your contribution. Assessors need to see what you did.
• Reasoning, not just events. The "why" behind each decision is what evidences management judgement.
• Specificity. Real names (or initials), real numbers, real outcomes. Vague accounts read as invented.
• Honesty. An account where you got something wrong and learned from it is usually stronger evidence than one where everything went perfectly.
• A clear link to the criteria. See below.

Mapping to assessment criteria

A reflective account only becomes evidence when it is linked to what it proves. After writing, note which unit and assessment criteria the account satisfies. For example: "Evidences AC 2.1 (identify causes of underperformance) and AC 2.2 (select an appropriate method to address it)." A single good account often covers several criteria — do not write a new account for every line of the standard; write about meaningful events and map them thoroughly.

Common mistakes to avoid

• Pure description with no reflection. The most common failure. Add the "why" and the "what I learned".
• Too much background. Keep the context tight; spend your words on your actions and reasoning.
• Hypotheticals. "I would..." is not evidence. Write about what you actually did.
• No mapping. Unmapped evidence makes the assessor do your job, and slows down your result.

A reusable template

Copy this and fill it in for each event:

Unit / criteria targeted: … Context: … Action (what I did and why): … Outcome: … Reflection (what I learned / would change): …

Next steps

• See how reflective accounts fit the whole picture in What is a portfolio of evidence?
• Pair a reflective account with confirmation from a colleague — see witness testimony examples.