Atlas
An intelligence layer for the RCOG ePortfolio. It shows you where you actually stand against the curriculum, and drafts the entries you've been putting off.
The ePortfolio is a box you put things in. It won't tell you which competencies you're short on, whether you're on track for ARCP, or help you write the entry at all. I'm a trainee living that gap, so I started building the layer that sits on top.
What it is
Atlas is a tool that sits on top of the RCOG ePortfolio and does the thinking the ePortfolio itself won't. It takes your training data and turns it into something you can actually act on — where you're strong, where you're behind, and what to chase before your next review.
It started life as a skill I'd built for writing my own portfolio entries. Atlas is that idea grown up: the entry-writing is still in there, but now it sits alongside a dashboard and proper gap analysis. It began as PortfolioIQ; Atlas is the name it ended up with.
What I built
The core is three things, all aimed at the same anxiety: am I actually on track?
- An ARCP readiness dashboard — pulls your portfolio data together and tells you, at a glance, whether you're on course or have work to do before review
- A CiP heatmap — all 14 Capabilities in Practice laid out so you can see which ones are strong, which are thin, and which are empty, so you know which cases to go after
- An AI entry generator — give it rough notes from a case and it drafts the Mini-CEX, NOTTS, OSAT, CBD or reflection in proper portfolio language, mapped to the right competencies
- A planned mobile companion for logging cases on the ward the moment they happen, rather than trying to remember them weeks later
Why I built it myself
Every O&G trainee knows the ARCP scramble: scrolling the ePortfolio trying to work out which CiPs you're behind on, writing reflections at midnight the night before, never quite sure you've got enough evidence.
The reason I think I can build this and someone outside medicine can't is the curriculum mapping. Tagging an entry to the right CiP and the right key skill — not just defaulting everything to emergency obstetrics — takes knowing the curriculum properly. I'd already worked that logic out for my own entries. Atlas is what happens when you turn it into something other people can use.
And I'm the user. I'm not guessing at the pain from the outside. I'm the one writing the entries at midnight.
Stack
Next.js and TypeScript, PostgreSQL for the data, the Anthropic API doing the entry generation, Stripe for payments, hosted on Vercel. The mobile companion is planned as a PWA off the same backend rather than a separate app.
Most of this is the stack I already knew from MedRank, which was deliberate — the interesting problem here is the curriculum logic and the analytics, not learning new tools. I reused what worked and put the effort where it mattered.
Where it's at
Honest status: this one is still being built. The portfolio-entry logic is real and battle-tested on my own ePortfolio. The dashboard and the rest are coming together.
I'm doing the unglamorous part deliberately — actually asking trainees whether they'd use it and what it's worth, before I build everything out. It would be easy to keep adding features I find interesting. The harder discipline, and the one I'm holding myself to here, is letting what people actually need decide what gets built.
Of everything on this page, Atlas is the one I think matters most. It's also the one with the furthest still to go.
Think Atlas would help you stay on top of your portfolio?
It's still being built, but the core is working on my own ePortfolio. If you're an O&G trainee who'd use this, get in touch — I'm looking for people to test it with.
Get in touch