The FourteenFish ePortfolio

Write at the end of every third clinic session — not at the end of every day. Trying to write after every single session is exhausting. But writing after every third (roughly once a day in GP) keeps you on track for 3 entries per month without burning out.

Pre-write your ESR capability justifications while writing your logs. When you link a log to a capability, write one sentence about why in the notes. When ESR preparation comes around, you'll have thirty of these sentences ready — instead of trying to recall three months of consultations under pressure.

The boxes in the log entry are guides — not a straitjacket. You don't have to fill in every single box. The ones marked with an asterisk (*) are mandatory. For others, if it makes more sense to combine "what I learned" and "what I'd do differently" into one box, that is absolutely fine.

The portfolio is a snapshot — not a confession. Some trainees avoid writing about cases where things didn't go perfectly because they're worried about who might read it. In reality, honest reflection on difficult cases is exactly what educators want to see. It demonstrates insight and professional maturity — both highly valued at ARCP.

Use your GP surgery admin time properly. Many trainees burn through admin time answering emails. Reserve at least part of it for ePortfolio entries. Even two rough entries in a 30-minute admin slot adds up to well over 36 per year without needing any additional time outside work.

Poor typing slows you down more than anything else. If you're spending most of your log time just typing, invest in a decent voice-to-text solution. Most smartphones now have excellent built-in dictation. Dictate your rough reflection immediately after a consultation, then clean it up later.

Your portfolio tells a story — make sure it's a good one. When an ARCP panel looks at your portfolio, they're looking for evidence of development over time. An ST1 portfolio that shows uncertainty and developing skills, moving to an ST3 portfolio that shows confident, competent practice — that is the arc they want to see. Perfection at ST1 is neither expected nor convincing.

Start conversations about portfolio struggles early — not after the damage is done. Every year, trainees who were silently falling behind come to their TPD in a panic at week 22 of a 26-week block. Your trainer and TPD have seen this before and genuinely want to help. A quiet word at week 6 is infinitely better than a crisis at week 22.

The "I test." When assessors across multiple UK deaneries review log entries quickly, they look for the word "I" in your learning section as an instant indicator of reflection. If your "what I learned" section doesn't use first-person statements about your own thinking, behaviour, or development, it is probably still a description. Count your "I" statements: "I realised...," "I noticed I defaulted to...," "I would now approach this by..." — these are the signals.

The bottom-heavy rule. A well-written CCR has its weight in the right place. The "what happened" box should be brief — two or three lines of anonymised context. The bulk of your writing belongs in "what I learned" and "what I'd do differently." If your entry is top-heavy, you're describing. If it's bottom-heavy, you're reflecting. Most trainees get this backwards initially.

If writing it feels mentally taxing, that's a good sign. Genuine reflection is effortful — it involves analysing, questioning your assumptions, and confronting uncomfortable gaps in your knowledge or skills. If writing a log entry feels slightly uncomfortable or demanding, that's your brain doing real learning. If it feels quick and easy, ask yourself honestly whether you're reflecting or just narrating. The best entries often take more out of you than you expect.

Don't leave your emotions out of it. A log entry that describes how a case made you feel — frustrated, worried, out of your depth, proud, or relieved — is not self-indulgent. It's evidence of professional self-awareness. The RCGP explicitly expects reflection on emotional responses alongside clinical and educational analysis. Trainers and panels notice when trainees demonstrate this kind of honesty. It's one of the things that distinguishes an average entry from an excellent one.

Be specific about your future learning. "I plan to read around the subject" is the most common, least convincing future learning statement in GP portfolios everywhere. It's meaningless and unverifiable. Instead: "I have booked onto the local diabetes shared care clinic for 3rd of next month" or "I completed the RCGP e-learning module on ADHD management in adults." Specific, verifiable, and time-linked future learning is what makes an entry genuinely convincing.

Don't pad your capability links. Trainees sometimes try to link every entry to four or five capabilities to make the portfolio look comprehensive. Assessors see through this immediately. A simple UTI management case almost certainly does not meaningfully demonstrate community orientation, ethics, and fitness to practise all at once. Link only where the capability was genuinely relevant in the actual consultation — and say why in your justification. Two strong, justified links beat five unconvincing ones every time.

Open your ePortfolio at the same time you open your clinical system. In GP, this means FourteenFish is open alongside SystmOne or EMIS from the moment your surgery starts. Between patients — especially if there's a gap — jot three bullet points about a case in the log. Add context and reflection later during admin time. This one habit alone makes 36 CCRs per year very achievable without it feeling like a second job.

The timestamps are visible to ARCP panels. They will notice if a year's worth of entries appear over a two-week period in May. It raises immediate concern — not just about your portfolio habits, but about whether the entries can really reflect genuine learning from actual patients seen over time. Write consistently throughout the year. The pattern of engagement matters as much as the content.

Share your logs regularly — not in batches. Your supervisor cannot read or comment on a log until you click "Share Log." Hoarding ten half-finished entries and then sharing them all on the same day creates a tsunami of reading for your trainer — and out of courtesy, spread this out. Regularly sharing also lets you receive feedback progressively through the placement, which is far more valuable than a pile of comments at the end.

Use your Curriculum Coverage section as a revision checklist. At mid-placement, open this section and look for gaps. Clinical experience groups you haven't evidenced yet signal cases you should actively seek out or discussions you should initiate with your trainer. Many trainees never look at this section until the ESR — by which point it's too late to plug the gaps easily.

PSQ takes longer than everyone thinks. Gathering 34+ patient responses to the Patient Satisfaction Questionnaire almost always takes weeks longer than trainees anticipate. Start distributing the PSQ as early as reasonably possible in your GP placement. Don't leave it until the final three weeks — you will run out of time or end up pestering patients at the end of every consultation, which creates its own problems.

Backdating to the event date is fine — bunching entries is not. You can retrospectively date a log entry to the day you saw the patient or the day the event occurred. What is not acceptable is writing eighteen entries over a single weekend and backdating them to span six months. FourteenFish records two separate things: the date you assign to the entry, and the timestamp of when it was actually created. ARCP panels can see both. Date your entries to the event; write them as promptly as you reasonably can.

The ESR Lock — do not sign off until you are completely satisfied. Once you complete and save the ESR sign-off in FourteenFish, your portfolio locks. You cannot edit entries or add to them without your supervisor manually unlocking it. Before you click sign-off, run through your checklist: all minimum numbers met, capabilities linked with justification, QIA/QIP present, safeguarding annual update done, LEA completed. Rushing the sign-off and needing changes afterwards adds unnecessary stress and delay for both you and your supervisor.

Go directly to your personal requirements page — not the general guidance. In FourteenFish, navigate to: Portfolio → ESR Preparation → Requirements. This page shows exactly what you need for your current review period — not the generic yearly total, but the half-year equivalent specific to your current stage. If you are training Less Than Full Time, your requirements are automatically reduced in proportion here. Always check your own requirements page rather than assuming the standard figures apply to you.

Log every HDR session and teaching event — including the ones that feel routine. Every half-day release session, in-practice teaching session, or external course can be recorded as a Supporting Documentation entry. It takes about two minutes, and it consistently evidences the "Maintaining Performance, Learning and Teaching" capability — one of the capabilities that purely clinical case reviews can rarely demonstrate. Trainees who do this habitually end up with remarkably broad curriculum coverage by their ESR without any extra effort.

Set a QIA calendar reminder on Day 1 of every new training year. A Quality Improvement Activity is required every training year — and it is surprisingly easy to reach October of a hospital year and realise you have not done one, with no obvious opportunity left. Set a calendar reminder in the first week of each new training year: "QIA due this year — what will I do?" Choosing your topic early means you can collect data gradually rather than rushing at the deadline. Equally useful: download the RCGP Mandatory Evidence Summary and Tracker PDF (available in FourteenFish via Training Map → Roadmaps), print it, and use it as a hand-filled personal checklist. Tracking progress visually prevents surprise gaps at ARCP.