Skip to content

CV in the PPP Passport ​

Feature Overview ​

The doctor's CV today is a write-only dead end: it can be uploaded on My Profile, but it is not surfaced in the PPP Passport, not shown at appraisal, not shareable with a hospital, and not used in any report — uploading it only ticks an onboarding item. Separately, PPP has the beginnings of a generated CV from job-role history (the "exportable CV report", #8088) that is not connected to the uploaded file. There are thus two disconnected "CV" concepts.

This feature unifies them by making the CV a first-class, living artefact of the PPP Passport — the portable, shareable record that already travels with the doctor between hospitals and into appraisals. PPP holds the raw material a CV is made of (verified registration, job-role/grade history, CPD, surgical logbook volumes, appraisals), so the platform can keep the CV current automatically instead of asking the doctor to maintain a separate document.

Direction (Rob, 2026-06-24, engineering default pending Matt): import an existing CV, extract its data into the Passport, keep it current from PPP's work history, allow the doctor to edit it, and make it downloadable as part of the Passport. See #9195 (direction) and #9196 (build).

Matt's confirmation (2026-06-24, #9195/#9196 comments): the PPP Passport should house the current CV uploaded at sign-on, stored for ease of sharing as part of the HR-compliance package; long-term PPP continues to build the CV (generated from the portfolio) and builds on the uploaded CV year on year, storing it here in addition. The generated CV should cover registration, roles/grades, CPD summary, qualifications/exams, publications, presentations; WBAs, appraisals and logbook numbers likely belong in the exportable report rather than the CV. Sharing is at the doctor's discretion only. Presentation/design to be agreed with Matt.

Schema note (2026-10-04, #12872): users.ts also gained the off-platform supervisor / appraiser nominee columns (migration 0257). No CV or Passport behaviour changed; the spec is touched only because it lists that file in its code-paths.

Delivery phases ​
  • P1 (built, #9196) — house the doctor's uploaded CV (users.cv_file) in the PPP Passport as a first-class, downloadable artefact, private by default and shared only at the doctor's discretion. Reuses the private signed-URL storage from #9194. The CV tab carries the stable key cv in PASSPORT_TABS, so other surfaces target it by key, not position (#12809).
  • P2 (follow-up) — AI-extract the uploaded CV (Gemini OCR) into structured Passport/profile data with a human-review step (Q2 open).
  • P3 (built, #10348) — generated living CV kept current from the portfolio (registration, roles/grades, CPD summary, qualifications/exams, publications, presentations), unifying with the #8088 generated CV report; PDF export. WBAs/appraisals/logbook numbers deferred to the exportable report.
  • P4 (in progress, #10619, engineering default pending Matt) — richer formatting control over the generated CV: template selection (3–5 brand-kit-approved templates), section reorder/show-hide, accent-colour selection within the brand kit, and a live split-pane preview matching the exported PDF exactly. Shipped to UAT as a testable prototype for Matt's review before this phase is confirmed as final.

Open Questions ​

#QuestionSourceOwnerStatus
Q1Should PPP generate the CV from the portfolio (roles, CPD, logbook), or keep it as a stored upload only?Rob 2026-06-24MattCONFIRMED (Matt 2026-06-24) — house the uploaded CV now and generate/build the CV long-term; both stored in the Passport.
Q2What is the acceptable AI-extraction approach for parsing an imported CV (reuse the Gemini OCR pipeline), and what is the human-review step before extracted data is written to the Passport?Rob 2026-06-24MattOPEN — P2 follow-up.
Q3Which sections should a generated/maintained CV include (registration, roles/grades, CPD summary, logbook volumes, appraisals, qualifications, publications, personal statement)?Rob 2026-06-24MattCONFIRMED (Matt 2026-06-24) — registration, roles/grades, CPD summary, qualifications/exams, publications, presentations; WBAs/appraisals/logbook → exportable report.
Q4Who can see/share the CV — the doctor only, the appraiser at appraisal, the hospital admin during onboarding?Rob 2026-06-24MattCONFIRMED (Matt 2026-06-24) — share at the doctor's discretion only.
Q5Does the doctor's self-uploaded CV remain alongside the generated one (e.g. as a personal-statement narrative)?Rob 2026-06-24MattCONFIRMED (Matt 2026-06-24) — yes, the uploaded CV is kept in addition and built on year on year.
Q6The generated CV's confirmed section list includes publications, presentations, and formal qualifications/exams, but PPP has no data-capture schema for these today (only free-text users.medicalDegree / users.awardingUniversity exist; no publications, presentations, exams, or fellowships table). Should PPP add structured capture for these, and where does the doctor enter them — a new Passport section, or CV-import extraction (P2)?Engineering-raised (#10348)MattOPEN — until answered the generated CV renders a "not yet captured in PPP" placeholder for those sections (never silently dropped). Does not block export of the sections that DO have data (registration, roles/grades, CPD summary, medical degree).
Q7Rob raised "richer control over formatting" for the generated CV during #10606 (2026-07-14) — layout/section choices, not just the fixed P3 template. Engineering scoped this as: template gallery (3–5 brand-kit-approved templates), section reorder/show-hide (required fields locked), accent-colour selection within the brand kit, live preview matching the exported PDF. Does this concrete scope match Matt's intent, and should any of it (e.g. custom branding beyond the kit, more than 5 templates) go further or narrower?Rob 2026-07-14 (#10608/#10619)MattOPEN — engineering default: built to UAT as a testable prototype per this scope (#10619) pending Matt's confirmation. Nothing here removes or changes the P3 default output for a doctor who doesn't opt in.

Acceptance Criteria ​

The P1 criterion below is built (#9196); the remaining ⏳ criteria are P2/P3 follow-ups — engineering default pending Matt's confirmation of the extraction/generation detail (see Open Questions).

  • ✅ passport-cv.uploaded-cv-housed — the doctor's uploaded CV (users.cv_file, captured at sign-on) is housed in the PPP Passport as a first-class artefact on a dedicated CV tab: it is downloadable via a short-lived signed URL, private by default, and clearly marked as shared only at the doctor's discretion (never exposed to anyone else). When no CV has been uploaded, the empty state offers an Upload CV button, and a present CV offers Replace CV (PDF or Word, up to 10 MB; stored under a per-user folder, #12876). (#9196, P1) †
  • ✅ passport-cv.import-existing — built (#12876, PassportCvSection: PDF/DOC/DOCX, 10 MB, upload and replace; the live upload leg is @wip because the signed PUT route is container-only). The doctor can import an existing CV (PDF/DOC/DOCX) into the PPP Passport. †
  • ⏳ passport-cv.extract-data — on import, PPP extracts the structured data from the CV (work history, qualifications, registration) and proposes it for addition to the Passport, with a human-review step before anything is written. Reuses the existing AI/OCR pipeline. †
  • ⏳ passport-cv.populates-passport — extracted data populates the doctor's PPP Passport / profile records (e.g. job-role history, qualifications) rather than sitting as an opaque file. †
  • ✅ passport-cv.kept-current — the generated CV is composed live from the doctor's portfolio already in PPP, with no double-entry: registration + roles/grades from the profile / job-role history (the #8087/#8088 verified/unverified career history), and CPD summary from the CPD activities the doctor has logged. Because it is generated on demand from source records, it reflects the current state every time it is exported — unifying with the generated CV report (#8088). (#10348, P3) † †
  • ⏳ passport-cv.editable — the doctor can review and edit the extracted/maintained CV data. †
  • ✅ passport-cv.downloadable — the generated CV is downloadable as a PDF from the Passport CV section, on demand. A dedicated Resume/CV export produces a branded PDF composed of the confirmed CV sections (below), distinct from the multi-feature exportable report; the file is served through the same authenticated download path as other Passport documents, never a public blob. (#10348, P3) † †
  • ✅ passport-cv.generated-sections — the generated CV renders exactly Matt's confirmed section list: registration, roles/grades, CPD summary, qualifications/exams, publications, presentations. WBAs, appraisals, and logbook numbers are excluded (they belong to the exportable report, not the CV); timesheets are excluded entirely; wellness appears only as cohort signals per exportable-reports.md Q4 and is not one of the CV sections. Sections whose source data is not yet captured render an explicit "not yet captured in PPP" note rather than being silently dropped (see Q6). (#10348, P3) † †
  • ⏳ passport-cv.housed-in-passport — the CV lives in the PPP Passport (the portable, shareable record), not siloed on My Profile; sharing/visibility scope per Q4. †
  • ⏳ passport-cv.private-storage — (signed URLs since #9194) the CV is stored privately (signed-URL read only), never as a public blob; replacing a CV deletes the prior file. Partly built: the sign-up upload targets the private ppp/cv_uploads/ prefix (onboarding.feature @issue-9194), but userCvService.setMyCv only re-points users.cvFile and never deletes the prior file, and no non-WIP scenario proves either half end to end; the @wip scenario in passport-cv.feature stays WIP. Prerequisite, tracked in #9194. †
  • ✅ passport-cv.formatting-template-choice — the doctor can choose from 3–5 brand-kit-approved templates for the generated CV via a visual gallery picker; the default (P3) template remains the zero-config output for any doctor who does not opt in. (#10619, P4) †
  • ✅ passport-cv.formatting-section-control — the doctor can reorder and show/hide generated-CV sections via a single unified drag-and-drop list; required fields (registration, name) are visible but locked, not hideable. Keyboard-operable and screen-reader-accessible (WCAG 2.1 AA). (#10619, P4) †
  • ✅ passport-cv.formatting-branding — accent-colour selection is constrained to the existing brand kit tokens (themes/colors.ts / themes/tokens.ts); no free-form hex or fonts outside docs/features/design-system.md. (#10619, P4) †
  • ✅ passport-cv.formatting-live-preview — formatting changes (template/sections/branding) render in a live split-pane preview that matches the exported PDF exactly, sourced from the same structured layout description consumed by PDF generation — never a separately-drifting HTML mirror. (#10619, P4) †
Open GitHub Issues ​

Open issues on label:feature:passport-cv — issue data unavailable at build time.Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Change Log ​
DateChangePR/IssueReason
2026-10-06passport-cv.private-storage re-statused from built to not built: sign-up uploads go to the private prefix, but replacing a CV does not delete the prior file (setMyCv only re-points users.cvFile) and no non-WIP scenario proves it.#9194The AC traceability gate found the built AC had no proving scenario; checking the code showed the replace-deletes-prior-file half is not implemented.
2026-10-04The CV tab in PASSPORT_TABS (PassportDocumentTabs.tsx) now carries a stable key (cv), like every other passport document tab. The PPP Passport overview's domain cards resolve their tab by key, so the CV tab's position can no longer capture another card's deep link. The CV tab's behaviour and content are unchanged.#12809Bug #12809 (ppp-passport). Inserting the CV tab at index 6 (#9196) silently re-pointed the Right to Work domain card, which targeted that index, to the CV tab. Recorded here because PassportDocumentTabs.tsx is in this spec's code-paths:.
2026-10-04No behaviour change. users.ts gained off-platform supervisor / appraiser nominee columns (migration 0257); a schema note was added so the spec-drift gate sees the file's owner reviewed.#12872, #11189passport-cv lists users.ts in its code-paths; the columns belong to profile-doctor (#12872).
2026-10-04The Passport CV tab can now upload or replace the CV (PDF or Word, up to 10 MB). Uploads go to a per-user folder (ppp/cv_uploads/user-<id>/); users.setMyCv and storage.generateUploadUrl both reject any key outside the caller's folder.#12876, #12783The CV is optional at sign-up (#12783), so a doctor who skipped it had no way to add it later. The upload key is user-scoped because sign-up keys are not, and accepting a client-supplied key would let one doctor point at another's file.
2026-07-14P4 — richer formatting control over the generated Resume/CV. A "Customize formatting" split-pane flow on the Passport CV section lets the doctor choose from 3 brand-kit-approved templates (Standard/Compact/CPD-forward) via a visual gallery, reorder and show/hide generated-CV sections in one unified drag-and-drop list (registration + name locked and never hideable; keyboard-operable via @hello-pangea/dnd + explicit move buttons, WCAG 2.1 AA), and pick an accent colour constrained to the brand-kit accent tokens. A live split-pane preview renders the REAL exported PDF via the same server generation path (previewCvFormatting → generateResumeCvPdf), so it can never drift from the download. Preferences persist to four new users columns (migration 0198) and are honoured server-side on the next Resume/CV download automatically. Section keys, template ids, accent tokens (hex mirroring the exact frontend brand-kit values) and the locked-section invariant live in one shared @ppp-org/ppp/constants contract used by both the frontend and backend. Byte-identical-default guarantee — a doctor who does not opt in gets exactly the P3 output (verified by test). ACs formatting-template-choice, formatting-section-control, formatting-branding, formatting-live-preview marked built.#10619, #10608Rob raised "richer control over formatting" for the generated CV during #10606 (2026-07-14, #10608). Engineering scoped it as a template gallery, section reorder/show-hide with required fields locked, brand-kit-constrained accent selection, and a live preview matching the exported PDF exactly. Shipped to UAT as a testable prototype for Matt's review — Open Question Q7 records this as an engineering default pending Matt's confirmation; nothing here changes the P3 default output for a doctor who does not opt in. Reused @hello-pangea/dnd (already the app's drag-and-drop primitive, used by the dashboard customise grid) rather than adding a second DnD library, per the repo's reuse-over-new-primitive guardrail.
2026-07-10P3 — generated Resume/CV export (generateResumeCvPdf) composed live from stored PPP data, distinct from the multi-feature report. Renders Matt's confirmed section list — registration + roles/grades (via the shared #8087/#8088 title page), CPD summary (reusing the shared multi-feature CPD payload), and qualifications/exams (medical degree + awarding university). Publications and presentations render an explicit "not yet captured" placeholder (Q6, no capture schema yet). A "Download Resume/CV" control in the Passport CV section decodes the base64 PDF and downloads it (mobile-webview aware). WBAs/appraisals/logbook belong to the exportable report and are excluded; timesheets are excluded entirely; individual wellness scores are never a CV section (cohort-only).#10374, #10348Matt confirmed (2026-06-24, Q3) the exact six-section CV composition and that the CV is a living document kept current from the portfolio. Rob (2026-07-10) directed building the generated export now, reusing the existing title-page registration/roles-grades composition and CPD summary rather than new data plumbing. Publications/presentations/formal-exams are surfaced as placeholders + Open Question Q6 rather than silently dropped, since PPP has no capture schema for them yet.
2026-06-29P1 — house the doctor's uploaded CV (users.cv_file) in the PPP Passport on a dedicated CV tab. Downloadable via short-lived signed URL, private by default, marked as shared only at the doctor's discretion, with an empty-state prompt when no CV is uploaded. AI-extraction (P2) and generated living CV (P3) remain follow-ups.#9196, #9195, #9194Matt confirmed (2026-06-24, #9195/#9196) the PPP Passport should house the CV uploaded at sign-on for ease of HR-compliance sharing, shared at the doctor's discretion only, while PPP continues to build the CV long-term. Reuses the private signed-URL storage from #9194.
2026-06-24New feature spec — CV in the PPP Passport. Import an existing CV, AI-extract its data into the Passport, keep it current from PPP's work history (unifying with the #8088 generated CV report), make it editable and downloadable as part of the Passport. Registered under capability Work & Employment. All ACs PROPOSED pending Matt (Open Questions Q1–Q5).#9197, #9196, #9195, #9194The CV is currently a write-only upload on My Profile with no downstream value and is not in the Passport. Rob (acting PO, 2026-06-24) directed unifying the two disconnected CV concepts (uploaded file + generated CV report) into a living, shareable, downloadable CV housed in the PPP Passport.

See docs/features/.changelog/passport-cv/.

Internal documentation — org members only