The instinct is understandable: if learning counts, record all of it, and a thick portfolio must be a safe portfolio. UK guidance points the other way. NHS England and the RCGP consistently advise proportionate, selective documentation, a meaningful sample of learning reflected on well, rather than an exhaustive log, and the GMC's framing has always been quality over quantity. Recording everything is not just unnecessary; past a point it actively works against you. Here is why, and the system that replaces it.
Why volume obscures rather than protects
An appraisal portfolio is read by a human being in finite time. Two hundred entries of tracked pages, confirmed doses and fifteen-minute modules bury the eight entries that matter, the corrected misconception, the changed prescribing habit, the learning that followed a significant event, under an administrative haystack, and the appraisal conversation degrades from discussion of your development into archaeology. Worse, indiscriminate logging quietly changes what you optimise for: the metric becomes entries created rather than learning done, which is precisely the credit-counting mindset current guidance spent a decade dismantling. And exhaustive logs are where anonymisation errors live; every reflexively saved interaction is another chance for an identifiable detail to reach an exported document unreviewed.
A private trace is not a portfolio
The confusion underneath over-logging is between two objects with different jobs. Your private learning trace, search history, question sessions, notes, reading logs, can be as complete as you like; completeness there costs nothing and helps the systems that schedule your retesting and map your coverage. Your appraisal portfolio is an argument, not an archive: a curated selection demonstrating relevant learning across your scope, reflected on meaningfully. The trace feeds the portfolio; it should never be the portfolio. Platforms that pipe every interaction straight into an appraisal export have confused the two on your behalf.
The CPD inbox
The working alternative is an inbox-and-curation model. Through the month, likely learning events, a genuine question that exposed a gap, an assessed session, a course, a striking article, go into a CPD inbox with minimal friction: one tap, the minimum viable fields captured, no decision yet about appraisal. Trivial confirmations do not enter at all; a dose check that taught you nothing is safe practice, not CPD. Once a month, ten minutes of curation: merge duplicates and clusters, the four related questions about the same topic are one learning event, not four, discard what looks thinner than it felt, and promote the handful of entries that demonstrate something, breadth into a neglected corner of your scope, a meaningful correction, PDP-linked progress. At year end, the appraisal pack is the promoted entries, perhaps eight to fifteen, each carrying a real reflection, with the inbox retained privately as depth if any discussion wants it.
What still gets kept regardless
Selectivity has exceptions. Certificates for mandated training, safeguarding, life support, keep, always, since those are contractual artefacts, not CPD judgement calls. Evidence connected to significant events, complaints or compliments belongs in its own supporting-information category and follows its own rules. And anything your PDP names should be evidenced deliberately, because the PDP is the one place appraisal expects completeness of story rather than sampling.
How iatroX implements this
Declared interest: this article describes the design My CPD is built around. Question sessions and askiatroX interactions that look like genuine learning events offer themselves to the inbox rather than auto-filing; clusters of related questions merge; and at review time the platform recommends the entries that demonstrate the most, the high-confidence error corrected and retained, the neglected domain finally sampled, the PDP-linked progress, rather than exporting the year wholesale. The export is a concise selected-evidence pack with the full trace held privately behind it, which is the trace-versus-portfolio distinction made mechanical.
Frequently asked questions
Will a slim portfolio look like I did less?
A curated portfolio with visible reflection reads as more development, not less; appraisers are explicit about this, and guidance says so in terms. Eight meaningful entries spanning your scope beat two hundred receipts every time.
What if my responsible officer or organisation asks for hours?
Local expectations vary and some roles carry specific requirements; where a count is genuinely required, your private trace supplies it in minutes. Curation changes what you present, not what you can substantiate.
How do I start if I currently log everything?
Change nothing about capture; add the monthly ten minutes. Curation is a layer on top of your existing habit, and after two cycles the reflex to file everything into the portfolio itself quietly dies.
Does selective logging risk missing something an appraiser wants?
The inbox model is precisely the insurance: nothing meaningful is lost, it is simply held privately rather than presented. If a discussion turns to a topic your pack does not feature, the trace is there to draw on, which is a stronger position than a portfolio so dense that neither of you can find the relevant entry in the meeting.