Built on a ward, not in a boardroom.

Clerkfolio is built and run by a UK junior doctor who kept hitting the same problem every application cycle: the evidence existed - the audits, the teaching, the cases, the certificates - but it lived in photo rolls, email attachments, half-finished spreadsheets and three different portfolio systems, and none of it was shaped like the self-assessment form in front of them.

Clerkfolio is the tool that was missing: one place to log clinical experience as it happens, keep evidence attached to the entries it proves, and map the lot onto the criteria each specialty actually publishes - so an application weekend is an export, not an archaeology dig.

No patient identifiers, by design. Case logging is anonymised. The forms remind you at every step, the terms require it, and nothing in the product ever asks for information that could identify a patient.

You do the judging. Clerkfolio shows official criteria next to your evidence and lets you self-assess. It will never score your readiness, predict an outcome, or tell you whether you are good enough - that judgement belongs to you and the people who assess you.

Your data is yours. Everything is exportable - PDF, Word, CSV, JSON, or a full ZIP backup - and stopping a subscription never deletes anything. UK-hosted (London), encrypted in transit and at rest. The detail is in the privacy policy and security policy.

Independent, and clear about it. Clerkfolio is not affiliated with the NHS, the GMC, or any Royal College, and it does not replace the official portfolio your deanery requires (Horus, Turas, or a college ePortfolio). It is the personal layer that makes those official processes less painful.

Every specialty configuration in Clerkfolio cites the official source it was built from - person specifications, self-assessment guidance and recruitment-office pages - together with the date it was last verified, shown in the app. Configurations are re-verified against those sources each recruitment cycle, and automated checks flag any that go stale. If something changes mid-cycle, always treat the official applicant guidance as authoritative and tell us so we can fix it quickly.

Questions, corrections, feature requests or security reports all reach a person, not a ticket queue: admin@clerkfolio.co.uk, or the contact page.