How to Write a GP Portfolio Reflection

Most trainees know portfolio reflections matter. Most also feel vaguely fraudulent writing them — either padding a thin entry into something that sounds substantial, or staring at the blank box after a long clinic with nothing coherent to put in it.

The blank box problem is solvable. The padding problem is also solvable. They have different causes and different fixes.

What You Are Actually Required to Submit

Before the reflection structure, the numbers matter:

• 36 Clinical Case Reviews per training year — roughly 3 per month. All must be about real patients you personally saw.
• At least 1 Learning Event Analysis (or Significant Event Analysis) per training year.
• At least one log entry addressing each of the 13 capabilities per six-month review period.

The RCGP curriculum was updated in August 2025. The required numbers did not change. Capability descriptor wording was modernised, and ST1/ST2 progression point descriptors were merged into a single combined descriptor. Evidence previously linked to capabilities remains valid.

The 13 capabilities require you to spread your entries across different clinical and professional domains throughout the year — not just write 36 similar clinical case reviews that all map to the same three capabilities.

Your Portfolio Is Not Private

Before anything else about structure: your ePortfolio is readable by your trainer, clinical supervisor, educational supervisor, TPD, deanery administrators, and ARCP panel. In fitness-to-practise cases the GMC may review it. Write honestly and reflectively — but as a professional, not in a private journal.

Two rules that follow from this:

No identifiable patient information. Age, sex, and a brief clinical descriptor are enough. Full names, dates of birth, NHS numbers, and any combination of details that could identify a patient are a data protection breach.

Don’t back-date large batches of entries with the same style and timestamp. ARCP panels see submission timestamps. A cluster of 20 identical-looking entries in the final two weeks before your review is a probity concern, not just a quality issue.

Start With the Event, Not the Capability

The most common reflection failure — even among trainees who write regularly — is choosing a capability first and then searching for a case to justify it. The entry comes out generic because the thinking went backwards.

Start with what actually happened. Ask:

1. What was uncertain, difficult, surprising, or emotionally memorable about this case?
2. What did I do during or after the consultation?
3. What did I learn that should change my next similar consultation?
4. Which capabilities does that learning genuinely demonstrate?

The capability links are a conclusion, not a starting point.

Write Freely First, Then Structure

Bradford VTS’s practical advice for trainees who get stuck: get the case out of your head as quickly as you can — on paper, in your phone’s notes app, in a rough draft. Don’t try to make it good yet. Just get the clinical memory and the uncertainty onto the page.

Then step back and work through the 13 capabilities one by one. Five seconds per capability: “Did this scenario demonstrate this?” Most will be no. Two or three will be obvious yes answers. Those are your capability links.

The Portfolio Mode guided approach works exactly this way. It takes you through the clinical event first, then works back to the curriculum links with questions rather than blank boxes — which is why it resolves the paralysis that comes from staring at an empty form.

A Five-Part Structure for Any Entry

This structure works for clinical case reviews and adapts to other entry types. Use it as a skeleton before editing into natural prose.

1. Context

Two or three anonymised sentences locating the case and why it mattered.

Avoid:

“I saw a patient with chest pain.”

Prefer:

“During a GP clinic I reviewed an adult patient with symptoms that initially appeared low-risk but became more concerning after focused history-taking.”

The second version protects confidentiality and still explains why the case warranted reflection.

2. The Uncertainty or Tension

Name the real difficulty. This is usually the most educationally valuable part of the entry, and the part most commonly omitted.

Examples of named tensions worth writing about:

• The referral threshold was unclear and I was uncertain whether it was met.
• My initial plan was too routine for the patient’s actual risk profile.
• I recognised that time pressure was changing how I was working through the problem.
• I needed to balance reassurance with explicit safety-netting and found the right words difficult.

If there was no genuine tension, the case probably does not need a reflection. The RCGP expects entries about real learning moments, not mandatory documentation of every consultation.

3. What You Did

Factual account of the actions taken — checking guidance, asking a supervisor, arranging follow-up, documenting safety-netting, changing the plan. Keep this brief.

4. What You Learned

The entry earns its value here. Connect the case to a principle you can reuse.

Weak:

“I learned to check guidelines.”

Stronger:

“I learned that NICE threshold criteria often have exception clauses for known risk factors, and that checking those clauses rather than relying on the headline rule is the more reliable practice.”

The stronger version shows transferable reasoning.

5. What Changes Next

One or two concrete actions.

• Add a personal checklist for this presentation type.
• Read the relevant local pathway before the next clinic.
• Practise a specific safety-netting phrase with a supervisor.
• Flag the topic for tutorial discussion.

An action point makes the entry useful at your next ESR rather than just marking a historical moment.

The Capability Table Method

Capability mapping should be a conclusion, not a search exercise. But there is a practical technique that makes it faster and more accurate.

In FourteenFish, click the capability name, then click “Show word descriptor.” Scroll to the Competent or Excellent column and find the descriptor statement that best matches what your case demonstrated. Then write: “I demonstrated this capability by [specific clinical action from the case].”

This does two things: it forces you to be specific rather than generic, and it pre-populates your ESR evidence with justification you already wrote. At review time, the capability boxes are filled, not blank.

Portfolio Mode guides you to capability links after the reflection is already written — not before. The prompt is: which capabilities does this reasoning demonstrate? That question, asked at the right point in the process, produces justifications that sound like you rather than like a capability glossary pasted in.

For mapping, the Portfolio Workspace supports up to 3 capabilities and 2 clinical experience groups per entry. Map selectively. Two well-justified links are stronger evidence than six weak ones.

Coverage Gaps and the Clustering Trap

The single most common portfolio problem is not bad writing. It is timing — clustering 20 entries in the two weeks before ARCP. The entries are rushed, all similar, and the trainer cannot give meaningful feedback because everything arrived at once.

Three entries per month, written consistently, produces a better portfolio than thirty written in a panic, and it is much easier to manage alongside clinical work.

Two specific ways ARCP panels notice clustering: the timestamp pattern, and the feedback pattern. When a supervisor comments on ten entries at the same time, those ten entries show no evidence of feedback being received, digested, and applied. Spread writing across the year and that progression becomes visible.

The Portfolio Workspace shows your current coverage — how many entries you have logged, which capabilities are covered, and where the gaps are. Running a quick check every few weeks is faster than discovering a large gap at the month before your ESR.

For trainees who benefit from a regular nudge: Weekly Portfolio Reminders sends a Wednesday-morning summary with your entry count, capability coverage, open gaps, and days until your next ESR. It is opt-in, zero credits, and does nothing except show you the data — which is usually enough.

Don’t Only Write Clinical Case Reviews

CCRs alone cannot evidence all 13 capabilities. Ethics, fitness to practise, organisational skills, and community orientation require other log types to demonstrate adequately.

ARCP panels notice variety in log types as a green flag. What panels want to see:

• Evidence spread across the whole year
• Progression in capability ratings over time (NFD early in ST1, moving towards Competent by ESR)
• Concise but substantive reflections — quality and insight, not word count
• Specific justification for capability links
• Variety: CCRs, tutorials, LEAs, prescribing reflections, QI activity, supporting documentation

The Portfolio Workspace supports eight entry types: Clinical Case Review, Supporting Documentation/CPD, Reflection on Feedback, Leadership/Management/Professionalism, Academic Activity, Learning Event Analysis, Quality Improvement Activity, and Prescribing. Using the full range keeps your capability coverage broad and gives panels what they want to see.

On Using AI for Reflections

The Reddit community for GP trainees is honest about this: AI-written reflections are common. The argument for them is that the reflection requirement is performative and the AI entry satisfies the box without wasting clinical time.

The argument against is simpler and clinical: you learn nothing from a reflection you did not write. The three-question test at the end of this article exists because it surfaces gaps in your own reasoning — a process that cannot be outsourced. If an entry cannot withstand “would I recognise this as mine at ESR?”, it is not doing its job for you.

The Portfolio Mode occupies the middle ground. It coaches the reflection rather than generating it — asking questions about your case that you answer in your own words. The thinking stays yours. The entry takes shape in the Portfolio Workspace as the conversation progresses, and can be edited freely before submission.

Final Check Before You Submit

• Have I removed all identifiable patient information?
• Is the learning event specific enough to revisit at ESR?
• Does the reflection show what I thought, not just what happened?
• Are the capability justifications specific — not just a tick?
• Is there at least one realistic action point?
• If I read this in six months, would I recognise the learning as mine?

If the answers are yes, the entry is ready. It gives your supervisor something specific to respond to, and it gives you a record of how your practice is actually changing — which is the point.

When the entry is ready, FourteenFish Sync pushes it from ClinicQuest to your ePortfolio in one click, with sync status tracked (Local, Synced, Modified, Locked, Stale) so nothing gets lost between the two platforms.

References

• RCGP. WPBA Learning Log.
• RCGP. Trainee Portfolio — features and walkthrough.
• Bradford VTS. ePortfolio and Log Entries.
• iGP Wales. Reflection guide.