Skip to content
View in Notion

Onboarding ​

Sign-up has its own spec: the 3-step sign-up flow, registration fields, sign-up payment/pricing, CPD Plan step and their questions (Q1–Q4, Q9, Q10) moved to Sign-up & Registration (split 2026-09-29, restored 2026-10-03). This spec keeps post-sign-up onboarding, SSO profile completion, the payments lifecycle and the guided tour.

Feature Overview ​

The onboarding flow takes a new doctor from sign-up (see Sign-up & Registration) through to a fully configured PPP profile: specialty and placement information, supervisors, roadmap, wearable connection, immunizations, CV upload.

The design principle: onboarding steps are completable in stages, and the Getting Started checklist is the subtle mechanism to return later. There is no skip: every step reflects live data and cannot be marked done without being done (#8027, see onboarding-checklist.md).

Sign-up, then dashboard onboarding (#8027) ​

A new doctor passes through a lean 3-step sign-up and then completes the rest of their setup inline on the dashboard via the onboarding checklist. There is no separate Phase 2 Setup Wizard.

  • Sign-up (3 steps) is deliberately lean: just enough to verify the doctor and take payment. See Sign-up & Registration.
  • Dashboard onboarding then surfaces the remaining setup tasks (complete profile, CPD plan, log activity, wellness, connect data, surgical cadence targets, and — for full-platform users only — appraisal date, logbook import and Smart GeoTag; CPD-only users are not offered them, #12550 / #12675) as a single Getting Started checklist whose steps always reflect live completion. See Post-Signup Onboarding.

On first login the user lands directly on their access-appropriate dashboard (or /my-profile when their profile is incomplete) — there is no forced redirect into a wizard. The checklist auto-hides once every step is genuinely complete.

Removed in #8027 (decision: 2026-06-02 call with Matt). The Phase 2 Setup Wizard (/onboarding), its first-login redirect, the outstanding-items banner, and the per-step / whole-section "show complete so you don't answer again" skip were all removed because they double-handled data the user had already provided. CV upload is captured at sign-up and managed in the PPP Passport (#9196) — removed from My Profile (Rob, 2026-06-24); immunisations move into the PPP Passport, never the sign-up flow; supervisors, placement and cadence are covered by "complete your profile"; wearables connect from the Wellness Data Sources page.

Open Questions ​

#QuestionSourceStatus
Q7Cadence denominator — a number of years, or the CCT date? Resolved by Rob 2026-10-04 on #12813: the CCT date when one exists, otherwise an editable years-to-complete field pre-filled with 5 (built, #12813). On 2026-09-21 Matt said "Cadence will be set by the denominator so over how many year; Default to 5 years; user can change". The shipped Cadence step instead asks for an expected completion (CCT) date (Rob acting-PO, 2026-06-01) and shows no pace until one is entered. Matt has not said whether the doctor should enter a number of years (default 5) in place of the CCT date, or whether 5 years is only the fallback when no CCT date is given. Either reading needs the 5-year default (onboarding.cadence.default-five-year-denominator, #12736).#11144 (2026-09-21); #12813 (2026-10-04)Resolved
Q8Primary-surgeon default — also pegged to the speciality documents? Matt's 2026-09-21 statement covers "Surgical case volume" (the total). The 2026-09-29 Weekly Tech notes record that "primary and secondary operational goals originated from the extraction document and specialty PDFs". The shipped primary-surgeon default is still one figure (1260) for everyone, and the curriculum extraction (#8552) supplies only a total. Should the primary-surgeon default also come from the speciality curriculum, and from which figure in it?#11144 (2026-09-21); notes-2026-09-29-weekly-techOpen — for Matt
Closed Questions (2) — click to expand
#QuestionSourceStatus
Q5Cadence model — default reference totals. The cadence model was decided earlier (Rob acting-PO, 2026-06-01, deep-dive on #7344): a unified Cadence step (surgical targets + WBA/appraisal cadence), a surgical whole-of-training total from which PPP derives per-year and per-3-month pace, and training duration from the doctor's expected completion (CCT) date — see the ✅ onboarding.cadence.* ACs below. The only part left open was the default reference totals to pre-fill.#7344 #8104Resolved 2026-06-03 (Matt, morning meeting): leave the default. One default for everyone — total cases 1800, primary-surgeon 1260 — pre-filled as whole-of-training totals, which the doctor can then edit. The default is the orthopaedic figure; per-specialty autofill of different default numbers is a contemplated future enhancement once the other surgical programmes are reviewed (Matt, 2026-06-03), not a current variance. This is already how the build behaves (code:instances/ppp/src/components/widgets/SurgicalLogbookWidgets/cadenceTargetDefaults.ts; per-user override + save in CadenceTargetsDialog, persisted in the cadenceTracker JSONB, #2885), so onboarding.cadence.defaults-not-misleading flips ✅. #8104 closed not-planned (no build needed). Superseded 2026-09-21 (Matt, #11144): "our default will be pegged to Surgical speciality documents provided based on uk system" — the total now defaults per speciality from the UK (ISCP/JCST) curriculum, already built by #8552; 1800/1260 remain only the fallback. Same comment adds "Default to 5 years" for the denominator (Q7).
Q6Admin supervisor-assignment surface. Is an Admin/Super-Admin path desired to assign/reassign a doctor's Educational/Clinical supervisors on their behalf (placement changes etc.)? (#8171)#7932 #8171Resolved 2026-07-10 (Matt): NO admin surface — self-serve. Matt: "no; user reaches out; no admin involvement; hospital admin could assist but not default" (#8171, 2026-06-30, restated for build 2026-07-10). The doctor sets their own supervisors on My Profile — Educational Supervisor, Clinical Supervisor(s), Colleague Appraiser — which is already shipped (code:instances/ppp/src/modules/identity-profile/UserForm/SupervisorFields.tsx, SupervisorsSection.tsx; data model + candidate-pool ACs below, #7932/#9173). No admin assign/reassign UI and no confirmation handshake are built (an earlier "Option-2 handshake" draft in the thread was superseded by this answer). Two adjacent flows Matt confirmed are separate and tracked elsewhere: the MCR/MSF/360 assessment-participant model (appraisals domain — MCR user-assigned in-form already built, MSF by the Named Professional Supervisor, 360 platform-or-non-platform email-lite) and the logbook responsible-consultant picker (defaults to Clinical Supervisor, remembers last-entered until logout, favourites, smart-list by hospital+dept) — filed as follow-on work off #8171, not part of onboarding.
Original Vision ​

Post-Signup Onboarding (dashboard checklist) ​

After sign-up + payment, the remaining setup happens on the dashboard Getting Started checklist — there is no separate Setup Wizard (removed in #8027). The checklist mechanism, its steps, live-completion logic, no-skip rule, visibility and acceptance criteria are specified in their own feature spec: Onboarding Checklist.

Onboarding as Feature Tutorial (#3605) ​

  • After sign-up, walk-through of key platform features
  • Contextual guidance at first use of each module

Acceptance Criteria ​

Onboarding checklist (#8027) ​

The Phase 2 Setup Wizard was removed and onboarding consolidated into the dashboard Getting Started checklist. Its mechanism, steps, live-completion logic, no-skip rule, visibility, and acceptance criteria (plus the collapsed superseded-wizard ACs) are specified in Onboarding Checklist.

Supervisor candidate pool (selected on My Profile — was the wizard Road Map step):

  • ✅ Both supervisor pickers (Educational and Clinical) list the same candidate pool: users where userType = 'consultant' AND isSuperAdmin = false AND accountAccess is not cpd (#7932; code:api/backend-ppp/src/services/userProfileService/index.ts getConsultantUsers). The cpd exclusion keeps CPD-only accounts out of the pool because they hold no Consultant role on the platform (origin: appraisals-wba.md Q9/#5063).
  • ✅ The candidate pool excludes the doctor themselves so a user cannot pick themselves as their own supervisor (#7932/#4549; getConsultantUsers excludeUserId).
  • ✅ Educational supervisor is a single self-FK column on the user (educational_supervisor_id); Clinical supervisors are many, stored in the user_supervisors junction (#7932; code:packages-shared/ppp/src/schema-groups/users.ts educationalSupervisorId, code:packages-shared/ppp/src/schema-groups/userSupervisors.ts userSupervisors).
  • ✅ A user only becomes an eligible supervisor (a consultant) via AHPRA/GMC verification at sign-up — self-elevation is rejected (#7932/#7643; code:api/backend-ppp/src/services/authService/index.ts, code:api/backend-ppp/src/services/authService/ssoSignup.ts).
  • ✅ A local/E2E supervisor candidate pool is seeded onto the seeded non-consultant test accounts; seed logic is shared between the local runner and the CI/UAT seeder (#7931/#7932; code:api/backend-ppp/scripts/seedSupervisors.ts, code:api/backend-ppp/scripts/seed-data/supervisorSeedData.ts).
  • ✅ A consultant's Colleague Appraiser is not a hard-required profile field — getOnboardingStatus surfaces it as a "Nominate your appraiser" checklist nudge (consultants only) that ticks when users.colleagueAppraiserId is set, and the former cosmetic required asterisk was removed (#9173; code:api/backend-ppp/src/services/onboardingService/index.ts step id nominateAppraiser). Full model + open points in profile-doctor.md (profile.supervisor.appraiser-nudge-not-hard-required) and the checklist behaviour in onboarding-checklist.md.
  • ✅ getOnboardingStatus derives an "Add your hospital" step for full-platform doctors that ticks once any user_assigned_hospitals row exists — the prerequisite that unlocks Smart GeoTag, timesheet-approver suggestions and the hospital-scoped supervisor picklist (#9173; code:api/backend-ppp/src/services/onboardingService/index.ts step id addHospital; unit-covered in onboardingService/index.test.ts).

Cadence model (edited on the My Profile cadence card; surgical targets in cadenceTracker):

  • ✅ Surgical case targets reject negative values (#4897; code:instances/ppp/src/modules/MyProfile/config/utils/UserFormResolver.ts Zod .min(0))
  • ✅ onboarding.cadence.unified-step — the Cadence Settings card collects both surgical case targets and WBA/appraisal cadence (CBD, CEX, PBA, MCR, 360, MSF over a selectable 3/6/12-month period) in one place, not surgical targets alone.† (#7344, #8043; code:instances/ppp/src/modules/MyProfile/UserForm/index.tsx surgical fields + CadenceTracker, code:instances/ppp/src/components/CadenceTracker.tsx)
  • ✅ The checklist's "Set your surgical case targets" step is listed for non-consultant surgeons only: consultants have no whole-of-training case total and their My Profile cadence card shows only MSF and 360, so the step could never tick (T7-16, Rob 2026-10-05, #11189). Case targets are set on the My Profile cadence card (/my-profile#cadence) and in the Surgical Logbook widget's "Set Case Targets" dialog.
  • ✅ onboarding.cadence.surgical-total-over-training — the surgical input is the total cases to achieve across the whole of training (not a per-year figure); PPP derives the per-year and per-3-month pace from it. The Cadence Settings fields (total cases + primary-surgeon cases) are labelled "(whole of training)" and read as totals, and the derived per-year / per-3-month pace shows beneath once a CCT date is set.† (#7344, #8044; code:instances/ppp/src/modules/MyProfile/UserForm/index.tsx whole-of-training cadence fields, code:instances/ppp/src/utils/cadencePace.ts derivePace)
  • ✅ onboarding.cadence.completion-date-input — the Cadence step captures the doctor's expected completion (CCT) date via a date picker; years-remaining (today → CCT) is derived as the divisor for the per-year and per-3-month surgical pace. Already-qualified consultants (non-surgeons) have no CCT and see only the WBA/appraisal cadence half. Past/blank CCT yields no pace (never negative or Infinity) — superseded in part: a blank duration must fall back to the 5-year default (onboarding.cadence.default-five-year-denominator, Matt 2026-09-21; Q7). Stored on the nullable users.expectedCompletionDate column.† (#8045; code:packages-shared/ppp/src/schema-groups/users.ts expectedCompletionDate, code:instances/ppp/src/utils/cadencePace.ts derivePace/yearsRemaining, code:instances/ppp/src/modules/MyProfile/UserForm/index.tsx)
  • ✅ onboarding.cadence.derived-pace-readout — once a total and completion date are entered, the surface shows the derived per-year and per-3-month targets as a live read-out that recomputes as either input changes; a missing total or CCT shows nothing (no NaN/Infinity).† (#8046; code:instances/ppp/src/utils/cadencePace.ts derivePace returns perYear/perThreeMonths, code:instances/ppp/src/modules/MyProfile/UserForm/index.tsx derived-pace-readout)
  • ✅ onboarding.cadence.defaults-not-misleading — pre-filled defaults are presented as whole-of-training totals, never as per-year figures, and the doctor can edit them. The total-cases default is pegged to the doctor's surgical speciality: it is the "Program sign off" figure from the UK (ISCP/JCST) curriculum for that speciality, and the field names that source and asks the doctor to edit it if their number differs. Where the speciality has no curriculum figure, the fallback is total cases 1800 and primary-surgeon 1260 (the orthopaedic figures). The primary-surgeon default is still the single fallback figure for everyone (Q8). The confirmed defaults are a single default for everyone — total cases 1800, primary-surgeon 1260; per-specialty autofill is a contemplated future enhancement (Matt, 2026-06-03). Superseded by Matt 2026-09-21.†††‡ (#7344, #8104, #8552, #11144)
  • ✅ onboarding.cadence.default-five-year-denominator — Built in #12736 (fallback reading of Q7: 5 years applies when no completion date is entered; entering a completion date changes it). The cadence pace is "set by the denominator" — the number of years the whole-of-training total is spread over. That denominator defaults to 5 years, and a doctor who has not entered a duration still sees a per-year and per-3-month pace computed over 5 years, labelled as a default for them to review; entering a completion date replaces the default. This ✅ covers only the 5-year default. The separate question of letting the doctor enter a number of years is onboarding.cadence.denominator-years-input below (Q7, not built).†‡ (#12736, #11144)
  • ✅ onboarding.cadence.denominator-years-input — Built in #12813 (Rob, 4 Oct 2026: "use the CCT date when one exists; otherwise show an editable 'years to complete' field, pre-filled with 5"). The CCT date wins; with none, the Cadence step shows an editable Years to complete field pre-filled with 5, stored as cadenceTracker.yearsToComplete, (whole number, 1-15). The per-year / per-3-month read-out, the backend logbook quarterly goal behind the dashboard pace widget, and the Roadmap surgical milestone all use it; entering a completion date hides the field and the date takes over. It is labelled a default only while it is the unedited 5. Original wording, kept for the record: If Matt chooses the "number of years" reading, the Cadence step lets the doctor enter the denominator as a number of years (pre-filled with 5) instead of / alongside the CCT date. †† (#12813, split from #12736)
  • ✅ Immunisations guidance shows which immunisations are required for the user's jurisdiction (hospital country + state) with per-requirement evidence upload; now surfaced in the PPP Passport (#7338; code:instances/ppp/src/modules/PppPassport/components/ImmunisationsCard.tsx, code:api/backend-ppp/src/services/passportImmunisationService/index.ts resolveUserJurisdiction). Multi-vaccine OCR remains a follow-up (#7941).

The checklist mechanism, visibility/return, and the collapsed superseded Setup Wizard ACs moved to Onboarding Checklist when the checklist became its own feature spec.

Payments lifecycle ​

Sign-up-time payment (country-currency pricing, GST-inclusive display, the early payment_intent.succeeded webhook) is in Sign-up & Registration.

  • ✅ Webhook handles charge.refunded and payment_intent.canceled to revoke access (#4969; paymentService/webhookService.ts:102-251 — revokeAccessOnRefund + canceled case; tests in webhookService.test.ts)
  • ✅ /billing and /plans-and-pricing remain reachable for unpaid users (#4971; PppModules.tsx:609,611)
  • ✅ Stripe Customer Portal available for invoices and payment-method updates (#4972; paymentService/index.ts:468 — createBillingPortalSession; route in procedures/payments/)
  • ✅ Upgrade flow is atomic — no partial success with wrong access tier (#4968)
  • ✅ UpgradePaymentModal records correct paymentAmount and paymentDate — fixed in #6343, then hardened in #12605 so the server derives amount/date/tier from the Stripe-verified PaymentIntent rather than trusting any client-sent value at all; UpgradePaymentModal.tsx/UpgradePaymentFormInner.tsx now send only { userId, paymentIntentId } (#4967; code:api/backend-ppp/src/services/payments-and-subscriptions/paymentService/index.ts confirmPaymentFromStripe; BDD: payment.feature "Upgrading from CPD to PPP records the actual prorated Stripe charge, not the original amount")
  • ✅ Downgrade confirmation copy matches actual access-revocation timing (#4966)
  • ✅ Google Pay integration does not spam console with Permissions-Policy violations

SSO profile completion ​

  • ✅ Account type (accountAccess) is selected on the Payment step, not step 0 — SsoProfileCompletion's Payment step renders the same PaymentForm component the main sign-up flow uses (CPD-only vs CPD+PPP toggle, tied to Stripe pricing/currency); step 0 (Profile Details) has no accountAccess control and does not gate on it (#12642; code:instances/ppp/src/modules/identity-profile/signup/SsoProfileCompletion.tsx, code:instances/ppp/src/modules/identity-profile/signup/components/PaymentForm.tsx).
  • ✅ The client-submitted accountAccess is an intent, not a grant — completeSsoProfile floors the persisted tier to cpd server-side regardless of what was selected; the real paid tier is set only from a verified Stripe PaymentIntent webhook (#12594; code:api/backend-ppp/src/services/identity-and-profile/authService/ssoSignup.ts).
  • ✅ Country of primary practice is a required field on the Profile Details step — it drives the Payment step's currency/billing-country default via the shared PaymentForm (watch('country')), the same behaviour the main (non-SSO) sign-up flow has via GeneralForm's Country field. Left optional, a user could advance without selecting one, silently defaulting Payment to the wrong currency (#12650; code:instances/ppp/src/modules/identity-profile/signup/sso-profile-completion/ssoProfileSchema.ts, code:instances/ppp/src/modules/identity-profile/signup/SsoProfileCompletion.tsx).
  • ✅ /complete-profile is gated on the session actually needing it — an already-onboarded user (real pppUserId on session) is redirected away before the wizard ever renders, never shown the 3-step form again (#12672). Before this, useSsoSession.ts rendered the full wizard for any authenticated session with no pppUserId check, mirroring the login-entry gate useSessionBootstrap.ts already has. This mattered beyond a UX nit: the Payment step creates a real Stripe PaymentIntent and confirms it client-side independently of completeSsoProfile's own idempotency guard, which only fires after a charge could already have been taken — an already-onboarded user re-reaching this page could be charged a second time before anything caught it. (code:instances/ppp/src/modules/identity-profile/signup/sso-profile-completion/hooks/useSsoSession.ts)

Post-login Guided Walkthrough ​

  • ✅ Post-login experience for new users
  • ✅ Feature tutorial on first use of each module

Canonical tour steps (built via react-joyride in instances/ppp/src/components/GuidedTour/index.tsx) ​

The first-login tour walks the user through 4 key UI elements. Each step is configured by a Step in the TOUR_STEPS array and must satisfy the acceptance criteria below.

#TitleTarget selectorLocated in
1PPP Featuresnav, [class*="sidebar"], [class*="Sidebar"], [class*="drawer"], [class*="Drawer"]Layout — PppAppContainer
2Dashboard Overview[data-tour="dashboard-widgets"]Both modules/cpd/dashboard/sections/CpdWheelSection.tsx (CPD-only, /cpd-dashboard) and modules/admin-org/ppp-dashboard/sections/WidgetsSection.tsx (CPD+PPP, /ppp-dashboard, added #8502)
3Search[data-tour="search"]PppAppContainer (top bar)
4Notifications[class*="notification"], [class*="Notification"], [aria-label*="notification"], [aria-label*="Notification"], [aria-label*="inbox"]PppAppContainer (top bar)

Acceptance criteria:

  • ✅ All 4 steps render consecutively (no skipping) regardless of which dashboard the user lands on, which viewport width, or whether the tour auto-runs on first login (components/GuidedTour/index.tsx — TOUR_STEPS + data-tour selectors in every layout). Two silent-skip gaps found and fixed during the Task 7 re-audit:
    • #12670 — a brand-new user with an incomplete profile first lands on /identity-profile, not a dashboard; step 2's [data-tour="dashboard-widgets"] target never resolved there, so the tour silently went 1→3. GuidedTour now redirects to the user's default dashboard route once before auto-running, mirroring the existing "Take the Tour Again" (#12649) manual-retrigger behaviour. #12825: that redirect no longer fires from / (the root redirect in PppModules owns it, with the payment and profile gates) or from /identity-profile (the intended landing for an incomplete profile), and the tour is held back there until the user reaches a dashboard; the catch-all route no longer redirects / to the dashboard. An incomplete-profile user now reaches /identity-profile from / without visiting /ppp-dashboard.
    • #12674 — on a handheld viewport (375px) the sidebar is a closed MUI Drawer that renders no DOM content until opened, so step 1's nav/sidebar/drawer selectors never resolved there either. Fixed by adding data-tour="sidebar-toggle" to the Topbar hamburger IconButton as a mobile-only fallback target for step 1 — it never competes with the desktop selectors since the hamburger only exists in the DOM when isHandheld.
  • ✅ Every step — including the final step — displays an (N of 4) progress indicator in its primary button (GuidedTour/index.tsx — nextWithProgress + last: 'Finish (4 of 4)')
  • ✅ Step 1 title reads "PPP Features" and the body mentions "all features" (GuidedTour/index.tsx — TOUR_STEPS[0])
  • ✅ The tour only runs once per user (tracked via onboardingStatus.guidedTourCompletedAt) unless re-triggered via "Take the Tour Again" in the user account menu, which sets forceRun (#12649; GuidedTour/index.tsx — forceRun || !guidedTourCompletedAt; slots/CoreAppUserAvatarMenu/index.tsx — handleRestartTour; components/GuidedTour/tourRestartSignal.ts). There is no dedicated "Help menu" in the app — the user account menu (avatar) is the closest equivalent and where this actually lives; forceRun had no UI consumer anywhere prior to #12649.
  • ✅ Any new Step added to TOUR_STEPS must ship with a data-tour attribute or equivalent stable selector in every layout that can host it — not just one dashboard variant (regression guard for #4572)
  • ✅ Missing selectors must be logged via console.warn, not silently skipped (#5173; GuidedTour/index.tsx:81)
  • ✅ Step definitions for guided tour BDD scenarios are implemented and runnable (#5172; e2e/bdd/steps/guided-tour.steps.ts)
  • ✅ Tour buttons and body text use the brand font (Nunito) and base-text colour token, never Arial or pure black (#7936; GuidedTour/index.tsx — styles + FONT_FAMILY.body + COLORS.ppp.baseText)
Status ​
Sub-featureStatusNotes
Phase 2 Setup Wizard🗑️ RemovedRemoved in #8027; replaced by the dashboard Onboarding Checklist
Dashboard onboarding checklist✅ BuiltOwn spec → onboarding-checklist.md (#8027)
Cadence model✅ BuiltSurgical totals + CCT-date pace model; total default per speciality (#8552), 1800/1260 fallback; 5-year default denominator (#12736); years-to-complete fallback (#12813)
Post-login walkthrough✅ BuiltHardened in Track E (#4572 / #4573 / #4571)
Feature tutorial✅ Built
Payments lifecycle✅ Built#4969/#4971/#4972/#4967/#5140 shipped (re-verified live 2026-09-30, sprint/onboarding-refine); #12648 (Payment History error-masking) filed and fixed same pass
SSO profile completion✅ Built#4992 fix merged
Open bugs (under review)✅ None#7341 and #7344 are closed; the checklist-side rows are tracked in onboarding-checklist.md

Open issues on label:feature:onboarding (1)

#Title
#12868feat(medical-registration-verification): AHPRA verification stays on the public AHPRA register (o…

Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Change Log ​
DateChangePR/IssueReason
2026-10-05Task 7 fix lane. The "Set your surgical case targets" step is no longer listed for consultant surgeons (T7-16); the Smart GeoTag step now ticks for any timesheet, not only a geofence-sourced one (T7-28); the spec's checklist mount points are corrected to CPD Home (OnboardingChecklist) and the PPP Dashboard (OnboardingSection) (T7-47); My Profile shows a "Profile saved" toast on a successful save (#12878); Billing shows a pending-downgrade indicator (#12686).#11189Rob 2026-10-05 live audit decisions. Consultants have no whole-of-training case total and their cadence card shows only MSF and 360, so the case-target step could never tick. A manual first timesheet is the documented fallback for the Smart GeoTag step. The spec mis-stated where the checklist is mounted.
2026-10-05Feature Overview no longer says onboarding can be skipped ("skip/save-for-later" contradicted the no-skip rule from #8027); it now points at the Getting Started checklist. The Open bugs status row is cleared because #7341 and #7344 are closed.#11189Task 7 spec review (5 Oct 2026), drift items S8 and S10.
2026-10-04With no CCT date the Cadence step shows an editable whole-number "Years to complete" field (1-15) pre-filled with 5; a completion date hides it and takes over. The profile pace read-out, the logbook quarterly goal and the Roadmap surgical milestone all divide by it. Q7 is resolved and AC onboarding.cadence.denominator-years-input is built.#12813, #11144, #11189Rob, 4 Oct 2026 on #12813: "use the CCT date when one exists; otherwise show an editable 'years to complete' field, pre-filled with 5". Matt, #11144 2026-09-21: "Default to 5 years; user can change".
2026-10-04Loading / right after login no longer bounces an incomplete-profile user between /ppp-dashboard and /identity-profile. The catch-all route skips the root path, and the first-login GuidedTour no longer redirects from / or /identity-profile (and is held back on /identity-profile until a dashboard is reached).#12825, #11189Three redirects raced on the same render: the catch-all route to the dashboard, the root redirect to My Profile, and the tour redirect back to the dashboard (#12670). Reproduced live: / -> /ppp-dashboard -> /identity-profile -> /ppp-dashboard -> ...
2026-10-03Split the Q7-dependent part of the cadence denominator out of the built AC. onboarding.cadence.default-five-year-denominator stays ✅ for the 5-year default only; new onboarding.cadence.denominator-years-input (⏳, not built) covers letting the doctor enter a number of years.#12778, #12736, #12813#12736's third AC requires Q7 to be resolved first and it is still Open for Matt, so the PR cannot claim that part. Tracked in #12813.
2026-10-03A trainee surgeon with a whole-of-training total but no expected completion date now sees a pace computed over a default of 5 years, labelled as a default to review. Entering a completion date replaces the default. A past completion date still shows no pace.#12736Matt (#11144, 2026-09-21) - "Default to 5 years; user can change". Built as the fallback reading of Q7 because both readings need the 5-year default. OPEN QUESTION Q7 for Matt - whether the doctor should instead enter a number of years in place of the completion date is not decided and not built.
2026-10-03Sign-up content moved to its own spec, signup-registration.md (split 2026-09-29, restored 2026-10-03). Moved — not copied — the Sign-up Flow (3 steps) section, Matt's 17 Apr 2026 Notion brief, the Registration ACs (including onboarding.signup.additional-specialities-prompt), the sign-up CPD Plan ACs, the sign-up payment ACs (onboarding.signup.price-matches-country, GST-inclusive display, early payment_intent.succeeded webhook), Original Vision "Registration & Medical Verification", open Q9 and Q10, and closed Q1–Q4. A one-line pointer replaces them. Title is now "Onboarding". The Payments section is renamed "Payments lifecycle" and keeps refunds, upgrade/downgrade, the Customer Portal and Google Pay. code-paths: re-pointed from signup/** to the SSO completion files (SsoProfileCompletion.tsx, sso-profile-completion/**), which this spec still owns.#11187, #11189, #12746Rob's 2026-09-29 decision to give Task 6 (Sign up and Registration) its own spec, restored on 2026-10-03 after the split never reached git. Moving rather than duplicating keeps one source of truth per AC. Re-pointing the glob avoids both specs claiming the same sign-up files at equal specificity, which would make the spec-drift gate demand both specs on every sign-up change.
2026-10-03Cadence defaults refreshed to Matt's 2026-09-21 statement (#11144), resolving the Task 7 handoff on #12720. onboarding.cadence.defaults-not-misleading now states the total-cases default is pegged to the doctor's speciality from the UK (ISCP/JCST) curriculum, with 1800/1260 kept only as the fallback. This matches the code shipped in #8552. The old "single default for everyone" wording is kept struck through. Added AC onboarding.cadence.default-five-year-denominator ("Default to 5 years; user can change"), marked drift (#12736). Noted on completion-date-input that a blank duration must fall back to 5 years. Q5 marked superseded. Added Open Questions Q7 (years count vs CCT date) and Q8 (should the primary-surgeon default also come from the speciality documents?). Status set to partial-drift.#11189, #11144, #12736, #8552, #8104Async Task spec refresh, where the newest dated Matt statement wins. Matt's 2026-09-21 comment on #11144 supersedes his 2026-06-03 "leave the default 1800/1260" answer (#8104) and the 2026-06-01 Rob acting-PO decision that the CCT date is the only divisor. A WhatsApp top-up found no Matt statement on cadence.
2026-10-03Task 6 (Sign up and Registration) made small sign-up edits to this Task 7-refreshed spec. The "Sign-up Step 3 pricing shows AUD only in v1" AC is rewritten as onboarding.signup.price-matches-country. The Payment step (step 2) shows AUD for Australia and GBP for the UK, taking the currency from the Country of Primary Practice field (built, #5863). The superseded wording is kept struck through. Added onboarding.signup.additional-specialities-prompt (Matt's 2026-05-03 Notion comment), marked drift (#12746). Added Open Questions Q9 (should the regulatory body, not the Country field, lock the currency?) and Q10 (the billing-cycle and refund sub-questions Matt raised on 2026-05-03, which were stranded inside closed Q4). Notion re-synced; the page was last edited 2026-05-26.#11187, #12746, #5255, #5863Async Task spec refresh, where the newest dated Matt statement wins. Matt's 2026-04-21 comment on #5255 accepts GBP pricing for UK users, so the "AUD only" AC was both out of date and wrong against the shipped code. The 2026-05-03 prompt requirement was recorded as an answered question but never became an AC, and it is not built. The two unanswered sub-questions sat in the collapsed Closed Questions table, so they are moved to the Open table.
2026-10-01Guided Tour no longer silently skips a step: it redirects to the user's default dashboard before auto-running (fixing a silent 1->3 skip for new users first landing on /identity-profile), and step 1 falls back to a mobile-only sidebar-toggle target on handheld viewports where the drawer renders no selectable content.#12670, #12674Found during a full Task 7 re-audit, walking the tour at both breakpoints and from a fresh-user first-login state rather than only re-testing the two already-known fixes. Both gaps produced the same user-visible symptom as the old #4572 (a step silently vanishing), through two previously-untested paths.
2026-10-01/complete-profile (the SSO profile-completion wizard) now redirects away immediately for any already-onboarded session instead of rendering the full 3-step wizard, including a real Stripe payment step, again.#12672Found during a full Task 7 re-audit: an already-onboarded user navigating to /complete-profile hit no guard at all and saw the full wizard pre-filled with their real name. The Payment step creates and confirms a real Stripe PaymentIntent independently of completeSsoProfile's idempotency check, which only runs after a charge could already have succeeded -- a real double-charge risk, not just a UI nit.
2026-10-01The dashboard "Set your appraisal date" checklist step is now listed for full-platform doctors only, joining logbook import and Smart GeoTag in that group (previously only those two were full-platform-only).#12675Found during the Task 7 team-mode re-audit: /appraisals/upcoming is gated to full-platform accounts (RequirePppAccess), but the step was in the unconditional base list, so a CPD-only doctor who clicked it was bounced back with two stacked "not available on your current plan" snackbars. Gated the same way as #12550.
2026-09-30SSO profile completion's Country field is now a required selection, not just present — it drives the Payment step's currency/billing-country default, and left optional a user could advance without ever selecting one.#12653, #12650PR #12653 added the Country control for #12650 but left it z.string().optional() with no validation on advancing past step 0, so a user could click Next without touching it and still land on Payment with country unset — reproducing the exact wrong-currency bug #12650 was meant to close, via silent omission instead of the field being entirely absent. Found in code review (sge:code-reviewer, Major finding) of #12653; fixed in the same PR, matching the main (non-SSO) sign-up flow's existing required country enum.
2026-09-30Corrected both SSO profile-completion ACs — account type is selected on the Payment step (via the shared PaymentForm), not gated at step 0 (removed the dead step-0 accountAccess validation that could never fail); and the "payment success persists accountAccess" AC now describes the real #12594 design — the client value is a plan intent only, floored server-side to 'cpd' until a verified Stripe PaymentIntent webhook confirms payment.#12642Step 0 (Profile Details) never had a UI control for accountAccess — the schema silently defaulted it, so the "blocks advance" check was vacuous dead code. The real selector already existed correctly one step later, on Payment, matching the main sign-up flow. The second AC's original wording ("persists accountAccess, not discarded") predated #12594's tier-flooring hardening and no longer matched the code — updated both bullets together since they describe the same flow.
2026-09-30Payments (sign-up + lifecycle) re-verified live — #4967 (UpgradePaymentModal paymentAmount/paymentDate) and #5140 (VAT/GST handling) both confirmed already fixed/resolved on uat and flipped from ⏳ to ✅ in the spec; the #5140 AC text was also corrected, since it still described the rejected automatic_tax-exclusive option rather than the GST-inclusive decision actually shipped. Found and fixed a new bug along the way — Payment History on /billing rendered "No payment history found." indistinguishable from a real failed listUserPayments load (#12648).#12648, #4967, #5140Both flagged items were stale spec status, not live bugs — #4967 was fixed by #6343 and hardened further by #12605 (server derives amount/date/tier from the Stripe-verified PaymentIntent; client sends only the intent id); #5140's actual shipped decision (2026-05-05, Matt) was GST-inclusive display with no automatic_tax, which the spec's AC text never caught up to. Leaving the spec on ⏳ for already-shipped work misdirects future audits into re-investigating settled questions. #12648 was a genuine new finding from exercising the live Billing page during this audit: listUserPayments reads live from Stripe, so a transient Stripe failure in production would silently read as "you never paid" instead of surfacing as a load error.
2026-09-30Added a live re-trigger for the guided tour ("Take the Tour Again" in the user account menu) and corrected the spec's Guided Tour AC to describe it; forceRun had no UI consumer anywhere in the app before this.#12649A live audit of the Guided Tour found the spec's "unless re-triggered from the Help menu with forceRun" AC described functionality that was never built — no "Help menu" exists, and git log -S"forceRun" showed the prop was only ever consumed by its own unit test since the original #3712 commit. Once a user's tour auto-completed, there was no self-serve way to see it again.
2026-07-10Resolve onboarding Q6 (admin supervisor-assignment surface) — Matt confirmed NO admin path; the doctor self-serves supervisor selection on My Profile. Moved Q6 Open → Closed. No code — self-serve is already shipped (#7932/#9173, SupervisorFields.tsx/SupervisorsSection.tsx). Noted the two adjacent flows Matt confirmed separate (MCR/MSF/360 participant model → appraisals; logbook responsible-consultant picker → logbook) as follow-on work off #8171.#10367, #8171Matt's final answer on #8171 ("no; user reaches out; no admin involvement; hospital admin could assist but not default", 2026-06-30, restated for build 2026-07-10) reverses the earlier Option-2 handshake draft. The admin-surface interpretation the issue title carried is dead; self-serve was already delivered, so this is a spec-only resolution.
2026-06-29Drop cvFile from the hasBaseProfileFields gate in onboardingService — regulatory body + registration number are now the only two base fields required.#9221CV upload was removed from My Profile (#9202), so cvFile gating "Complete your profile" created an uncompletable checklist step. CV is owned by sign-up + PPP Passport (#9196).
2026-06-22Extended code-paths: to include the backend onboarding procedure and onboardingService alongside the Signup module.#9068, #9056SGD C6 drift — the built Onboarding spec listed only the frontend Signup path, breaking automated code traceability for the onboarding backend.
2026-06-10Add the dashboard-widgets guided-tour anchor to the canonical PPP dashboard so tour step 2 no longer silently skips for full-PPP users.#8502Surfaced by the #8432 consolidation review — only the deleted orphan Dashboard module ever carried the anchor; GuidedTour step 2 targeted a selector absent from /ppp-dashboard.
2026-06-03Rewords the "Set Case Targets" dialog intro from "Set your personal annual targets for surgical case metrics" to state the targets are whole-of-training totals, with PPP deriving the per-year / per-3-month pace from the expected completion date. Removes the last per-year framing on a live cadence surface; defaults (1800 / 1260) and field labels were already correct (#8044/#8046/#8104).#8291, #8047onboarding.cadence.defaults-not-misleading (#8047) requires the pre-filled defaults to read as whole-of-training totals, never per-year. The dialog copy still opened with "annual targets" — the exact misleading framing #7344 flagged — directly above two "(whole of training)" fields. AC stays ✅; this closes the contradiction and adds a @regression @issue-8047 scenario guarding the dialog from regressing to the annual framing.
2026-06-03Resolve Cadence Open Question Q5 — defaults confirmed as one default for everyone (total cases 1800, primary-surgeon 1260), pre-filled as whole-of-training totals and editable by the doctor; no specialty/stage variance. Q5 moved to Closed Questions; AC onboarding.cadence.defaults-not-misleading flipped to delivered.#8164, #8104, #7344Matt confirmed "leave the default" in the 2026-06-03 morning meeting; the build already behaves this way (cadenceTargetDefaults.ts + CadenceTargetsDialog, cadenceTracker JSONB), so the spec is brought into line and #8104 closed not-planned with no code change.
2026-06-03Record the Educational Agreement upload as won't-do and confirm no orphaned-blob cleanup is needed.#8163, #8074Follow-up to #8074 (closed won't-do). Code is already clean (repo-wide grep returns zero hits, removed in #8027 / PR #8073). The orphaned-blob sweep is a no-op — verified zero blobs under ppp/educational_agreement/ in the UAT pppukuatsa/uploads container, and no prod storage account exists; the upload writer never ran against a deployed backend (last successful CD was 2026-05-27, before #7925 merged, and the feature was removed before any redeploy). The superseded AC is requalified so the spec no longer reads as a live surface.
2026-06-02Adds ✅ onboarding.cadence.unified-step. The Cadence Settings card collects both surgical case targets and WBA/appraisal cadence (CBD, CEX, PBA, MCR, 360, MSF over a selectable 3/6/12-month period) in one place, not surgical targets alone.#8119, #8043Verify-and-close: already shipped by the My Profile cadence card (surgical fields + CadenceTracker). Documents the unified step as a ✅ AC so it is no longer surfaced as a gap.
2026-06-02Flips onboarding.cadence.surgical-total-over-training ⏳ → ✅. The My Profile Cadence Settings surgical inputs (total cases + primary-surgeon cases) are now explicitly labelled "(whole of training)" with helper text stating they are whole-of-training totals, not per-year figures; PPP derives the per-year and per-3-month pace from them via the expected-completion (CCT) date (read-out shipped in #8083/#8046).#8117, #8044#8083 shipped the cadence step, CCT capture and derived-pace read-out, but the surgical input label/helper text was ambiguous and could read as a per-year figure — exactly the misleading framing #7344 flagged. This makes the whole-of-training-total meaning explicit in the UI. Default reference totals stay PROPOSED, gated on Matt (onboarding Q5, tracked on #8047).
2026-06-02Cadence step now captures the doctor's expected completion (CCT) date via a date picker; years-remaining (today → CCT) is derived as the divisor for the per-year and per-3-month surgical pace read-out. Already-qualified consultants (non-surgeons) have no CCT and see only the WBA/appraisal cadence half. Stored on a new nullable users.expectedCompletionDate column (migration 0152). Flips onboarding.cadence.completion-date-input ⏳ → ✅.#8083, #8045Deep-dive resolution on #7344 (Rob, acting PO, 2026-06-02): training duration is captured via an expected-completion (CCT) date — no such field existed. Past/blank CCT yields no pace (never negative or Infinity). Scoped to capture + derive + persist + no-CCT gating only; #8042 (re-defining the stored cadenceTracker target meaning / getThreeMonthGoal math) is intentionally held out of scope.
2026-06-02Split the dashboard Getting Started checklist out into its own spec (onboarding-checklist.md / feature:onboarding-checklist); onboarding.md now scopes sign-up + cadence model + supervisor pool, with a cross-reference to the new spec.#8082, #8077, #8027After #8027 the dashboard checklist is the surviving, central onboarding surface and warranted a 1:1 label↔spec of its own. Cadence model (#8043–47) stays feature:onboarding.
2026-06-02Scrubbed 3 residual Setup Wizard references that contradicted the #8027 removal; confirmed the dashboard Getting Started checklist as the sole, well-defined onboarding surface.#8072, #8068, #8027#8049 removed the Phase 2 Setup Wizard and updated most of the spec, but three sentences still described the wizard as the current home for setup tasks (the "3 steps" note, Open Question Q6's Road Map reference, and the feature-tutorial "after setup wizard" phrasing). Reworded to point at the dashboard checklist / My Profile / PPP Passport so the spec no longer contradicts itself.
2026-06-02Removed the Phase 2 Setup Wizard and consolidated onboarding into the dashboard Getting Started checklist. Deleted the /onboarding wizard, its first-login redirect, the outstanding-items banner and the onboardingTracking router/service. The checklist now reflects live completion only — no per-step Skip, "Restore skipped steps" or whole-section "Skip onboarding". Added connectData (verified wearable connection, deep-links to Wellness Data Sources) and surgeon-only cadenceSettings (deep-links to the My Profile cadence card) checklist steps; immunisations are captured in the PPP Passport, never the sign-up flow; CV at sign-up / My Profile; supervisors + cadence under "complete your profile". Dropped the wizard tracking + per-step skip columns (migration 0151).#8049, #80272026-06-02 call with Matt: the Phase 2 Setup Wizard double-handled data the user had already provided (CV at registration; immunisations belong to the Passport and are hard to find at sign-up) and risked overwhelming new users. Consolidating onboarding into the single dashboard checklist removes the redundancy, and the "show complete so you don't answer again" skip is taken out so the checklist can never claim a step is done that isn't. Supersedes #7344.
2026-06-02Flips onboarding.cadence.derived-pace-readout ⏳ → ✅. The derived per-year and per-3-month surgical pace read-out — recomputing live as the whole-of-training total or the expected-completion (CCT) date changes, and showing nothing when either input is missing — shipped with the CCT-date capture in #8083 (the cadence read-out in MyProfile/UserForm driven by utils/cadencePace.ts derivePace).#8046#8083 (the #8045 CCT-date capture) implemented the live read-out in code but only flipped onboarding.cadence.completion-date-input; the derived-pace-readout AC was left ⏳. This is a documentation-only reconciliation closing #8046 against the already-shipped implementation — no behaviour change.
2026-06-02"Save for Later" on the onboarding setup wizard now persists the durable cross-device defer signal reliably. handleSaveForLater previously fired the backend scheduleReminder (the reminderAt write that shouldRedirectToOnboarding reads to suppress the first-login redirect) fire-and-forget, so a transient failure left reminderAt unset — on a SECOND device, where the local saved-for-later flag is absent, the gate then force-redirected the deferred user back into the wizard (a narrowed recurrence of #7337). The handler now AWAITS the write and RETRIES once; on a genuine persistence failure it still navigates to the dashboard (never traps the user) but surfaces a non-blocking warning toast so the user knows the cross-device reminder did not sync.#8021, #7952Follow-up from the #7949 review (which fixed #7337). The #7337 fix made the deferral durable via reminderAt, but the write itself was still fire-and-forget, so a network blip silently lost the cross-device signal and re-introduced the wizard-bounce on a new device — once per new device rather than every login. Awaiting + retrying the write closes that gap while keeping the user-never-trapped guarantee: navigation always proceeds, with a toast on genuine failure. No migration — reuses the existing reminderAt signal.
2026-06-01Onboarding Cadence step model agreed — unified (surgical + WBA/appraisal cadence), surgical input is a whole-of-training total with PPP-derived per-year/per-3-month pace from the expected completion (CCT) date; default reference totals stay PROPOSED pending Matt.#8005, #7344Matt (#7344) flagged the shipped step as oversimplified — it asked only for surgical "cases per year" while cadence also covers WBAs/Appraisals, and the 1800/1260 defaults are whole-of-training figures wrongly shown as per-year. Model decided by Rob (acting PO, deep-dive 2026-06-01); ACs drafted ⏳ ahead of build.
2026-06-01Documented the Road Map supervisor candidate-pool rule and the Educational (single FK) vs Clinical (junction) data-model split as shipped ACs; narrowed Q6 to the still-open admin-assignment-surface question.#7994, #7932Rob flagged the Road Map supervisor behaviour was undocumented. Grounded each AC in shipped code — candidate pool = getConsultantUsers (userType='consultant' AND !isSuperAdmin AND accountAccess != 'cpd', minus self #4549); educational_supervisor_id FK vs user_supervisors junction; consultant eligibility only via AHPRA/GMC verification (#7643); local/E2E seed (#7931). Whether an admin/super-admin assignment surface is wanted stays an Open Question for Matt.
2026-06-01The first-login guided tour (react-joyride) now renders its Skip / Back / Next / Close buttons in the brand font (Nunito) and its tooltip body copy in the PPP base-text colour token. Previously GuidedTour set only primaryColor, so the buttons fell back to react-joyride's default Arial and the body text was pure rgb(0,0,0). The fix adds options.textColor = COLORS.ppp.baseText and a styles block setting FONT_FAMILY.body on the tooltip and every button slot (buttonPrimary / buttonBack / buttonSkip / buttonClose) plus COLORS.ppp.baseText on tooltipContent — all from tokens, no hardcoded values.#7966, #7936Surfaced during a screen-by-screen review of the CPD dashboard orientation guide: the tour buttons were Arial and the body text pure black, both off-brand. react-joyride's buttons do not inherit the MUI theme typography, so the brand font must be set explicitly on the joyride styles. Using the Nunito FONT_FAMILY.body token and the COLORS.ppp.baseText token keeps the fix compliant with the no-hardcoded-brand-values rule.
2026-06-01The onboarding Road Map supervisor feature-highlight no longer claims supervisors "can see your progress". It is reframed as privacy-first — label "Supervisor sign-off", body "Share assessments with your educational and clinical supervisors for sign-off, directly in PPP. They only see what you choose to share — your profile stays private." Supervisors only see explicitly-shared items, never the full profile.#7958, #7343The previous copy overstated supervisor access, implying blanket profile visibility. PPP's actual (and Matt's required) model is doctor-controlled: the doctor explicitly shares specific assessments for sign-off via WBA / Reflection / Work Queue, and the profile stays private. The behaviour was already correct — only this onboarding highlight copy was misleading, and it was the only instance of the claim in the codebase.
2026-06-01"Save for Later" on the onboarding setup wizard now persists across logins. The first-login gate in PppModules previously redirected any non-admin paid user whose wizard was not marked complete to /onboarding on every landing — it OR''d in the always-truthy onboardingTracking.getStatus object, so the deferral was ignored and the user was bounced back into the wizard each login. A new pure helper, shouldRedirectToOnboarding, suppresses the redirect when the user has deferred (the durable backend reminderAt scheduled on Save for Later, or the local saved-for-later flag), so they land on their dashboard and resume via the outstanding-items banner. Only a genuine, never-deferred first login is redirected. No migration — reuses the existing reminderAt signal already returned by getStatus.#7949, #7337Matt reported (#7337) that after a password reset + login he landed on the setup wizard and asked whether it would reappear on every login until completed. It would — "Save for Later" deferred only within the session and the user was force-redirected back on the next login, contradicting the spec's Save-for-Later + outstanding-items design. The fix makes the deferral durable so the wizard helps new users without ever trapping them in a login loop.
2026-06-01Document onboarding upload validation (CV, Immunisations, Educational Agreement) + shared dropzone, compact mobile stepper, and a supervisor candidate-pool Open Question.#7925, #7922The upload steps' accepted types/size/validation, the shared drag-and-drop panel, and the supervisor model were built but unspecced; surfaced during a screen-by-screen review.
2026-05-27The sign-up Registration step's Date of Birth field now displays and accepts dd/mm/yyyy for AU/UK users. The DOB control is a native <input type="date"> (#7720), which formats by the element's lang attribute rather than the value's; with no lang it fell back to the browser/OS locale and defaulted to en-US (mm/dd/yyyy). Pinning lang="en-GB" on the input forces dd/mm/yyyy display and entry regardless of browser locale. The stored value is unchanged (ISO yyyy-MM-dd), so the #7720 verbatim paste/autofill behaviour and Zod validation are untouched.#7768, #7761Surfaced during the investor-demo sign-up: the native date input rendered in en-US (mm/dd/yyyy), the wrong convention for PPP's Australian and UK doctors. A native <input type="date"> cannot be reformatted by its value — the display format follows the element locale — so the minimal, autofill-safe fix (keeping the #7720 native input) is to pin lang="en-GB".
2026-05-27Payroll ID is now OPTIONAL across every profile-completion surface. A payroll-less full-platform doctor is no longer redirected to /my-profile (by ProfileCompletionGuard or the PppModules root-path redirect), no longer shown the persistent "complete your profile" banner, no longer warned by the My Profile completion panel (ProfileCompletionStatus), and no longer listed an outstanding "Payroll ID" item by the OnboardingOutstandingBanner. ProfileCompletionGuard, PppModules, ProfileCompletionStatus, useOutstandingItems and onboardingService.getOnboardingStatus now share one payrollId rule (optional) so the redirect, banner, panel and checklist can never contradict each other. The stale consultant colleague-appraiser requirement in PppModules / ProfileCompletionStatus was also dropped to match #4471.#7758, #7656#7655 (fixes #7634) decoupled the Getting Started onboarding checklist from payrollId — PPP doctors who legitimately operate without a payroll (#7348 / #7358) get a complete profile and the Smart GeoTag step gated on full-platform access. But ProfileCompletionGuard (instances/ppp/src/components/ProfileCompletionGuard/index.tsx) and useOutstandingItems (instances/ppp/src/hooks/useOutstandingItems.ts) still treated payrollId as a hard requirement, so a payroll-less doctor was redirected, banner-nagged and shown an outstanding Payroll ID item — directly contradicting the checklist. Rob's product decision: payrollId CANNOT be mandatory. This change removes the mandatory gating from both surfaces (payroll features for doctors who DO have a payrollId are untouched) and aligns all three readers on the single optional rule the backend already uses.
2026-05-27The sign-up "Suggested CPD Plan" dialog now shows a "Use this plan" button that pre-fills the CPD Plan step with the suggested activities, matching the in-app /cpd-plans flow. Previously the dialog only offered Close, so suggestions could not be added during sign-up.#7731, #7728SuggestPlanDialog only renders the "Use this plan" action when an onAutopopulate handler is passed (#4411). The in-app MakeCpdPlan/index.tsx passed it, but Signup/RegistrationForm.tsx did not, so sign-up users saw only Close. RegistrationForm now adds a handleAutopopulate callback that maps suggestions via mapSuggestionsToFormValues into suggestInitialValues, feeds that to CPDActivityForm.initialValues, and passes onAutopopulate to SuggestPlanDialog — making the sign-up behaviour identical to the in-app one.
2026-05-27Made the sign-up Registration fields password-manager & autofill friendly — replaced the masked DOB DatePicker with a native date input (no more 12/03/1975 → 03/12/2005), relabelled "Registration Number" → "Medical Registration Number" with non-vehicle autofill semantics, and added correct autocomplete tokens to the name/email fields.#7723, #7720The masked DOB input mangled pasted/programmatic/autofilled dates and Roboform offered saved car-registration numbers for the registration field, making onboarding feel low-quality for the medical professionals who rely on password managers (and breaking the investor-demo automation). The native date input preserves a full value verbatim and the clearer semantics let fillers map every field correctly.
2026-05-27The "Complete a wellness questionnaire" onboarding item (and the Pulse widget's add CTA) now open the WHO-5 questionnaire inline in a dialog on the dashboard instead of deep-linking to /wellness and forcing the user to find the start button. A fallback link to the full Wellness page is kept in the dialog footer.#7632, #7350Matt (#7350) recorded clicking "Complete wellness questionnaire" from the onboarding widget and being taken to /wellness, where he then had to hunt for the start button. He wanted the questionnaire to pop up in the first instance "to show the user how easy it is to complete." A new shared useInlineQuestionnaire hook (PPPDashboardV2/useInlineQuestionnaire.tsx) renders the existing QuestionnaireFormDialog directly on the dashboard and invalidates the onboarding status + wellness questionnaire queries on submit so the onboarding item and Pulse widget update in place. The weekly-prompt → notification → popup workflow Matt mentioned is tracked separately in #7606.
2026-05-26SGD spec-accuracy pass. Flipped ~17 stale ⏳ → ✅ ACs whose code is shipped (wizard stepper/skip/save, Roadmap & CV steps, #4412 post-login redirect, #4904 single primary action, #4897 cadence min(1), #5146 error-boundary, #5599 QR codes, profile banner + return notification, #4902/#5145 step-state retention, #4905 consistent Skip, #4969 refund/cancel webhook, #4971 billing/plans routes, #4972 Stripe Customer Portal, and all 7 Guided Tour ACs). Corrected the #7301 personal-email AC to the prominent-warning reality (GeneralForm.tsx:447-453). Trimmed the duplicated med-reg/speciality narrative to a cross-reference to medical-registration-verification.md. Added Open Question Q5 for the cadence model (#7344) without inferring Matt's intent, and added ⏳ ACs for open bugs #7338 (immunisation guidance + OCR), #7341 (connect tick must reflect a verified connection), #7350 (questionnaire inline).#7601, #7600, #7301, #7338, #7341, #7344, #7350Spec was status:built but ~17 of ~27 ⏳ ACs lagged shipped code; the markers were stale. Each flip was verified against the cited file/symbol before editing. The surgical-logbook-import step AC was left ⏳ — it is genuinely not a wizard step (ONBOARDING_STEPS has only CV, Immunisations, Connect Data, Road Map, Cadence). Docs-only; no BDD change.
2026-05-26Setup wizard now exits to the access-appropriate dashboard — /ppp-dashboard for full CPD+PPP users, /cpd-dashboard for CPD-only — instead of a hardcoded /cpd-dashboard on every exit.#7574, #7356Matt (#7356) completed the new setup wizard as a full PPP user and landed on CPD Home instead of the PPP Dashboard. The wizard hardcoded /cpd-dashboard on complete, skip, and the already-completed guard (modules/Onboarding/index.tsx), bypassing the accountAccess-aware landing logic in PppModules.tsx. Extracted that logic into a shared getDefaultLandingPath helper (utils/landingPath.ts) and routed both the post-login redirect and all three wizard exits through it so they can no longer diverge.
2026-05-26Spec status flipped in-progress → built — the Onboarding module ships in production.#7454, #7312Gap issue #7312 (Category D status mismatch) flagged the spec as understating delivery. The full Onboarding journey is on disk and shipping: instances/ppp/src/modules/Onboarding/ (wizard, steps, session storage), instances/ppp/src/components/OnboardingChecklist/, and instances/ppp/src/components/OnboardingOutstandingBanner/, backed by onboarding/onboardingTracking routers and services. The spec already carried 16 ✅ ACs and an 80-scenario BDD file (onboarding.feature). Status updated to reflect built reality. No acceptance criteria changed, so no .feature update.
2026-05-26Corrected AHPRA-validation spec — it is a live lookup against the public AHPRA register (our own ahpraScrapeClient), NOT the PCA API. Flipped the "AHPRA validation via PCA API" AC to ✅ with accurate wording.#3939, #5991, #6306The spec claimed AHPRA validation was "via PCA API (live)" and "format-only … no-op until AHPRA data becomes available" — both wrong. PCA (pcaClient.ts) was never wired into the live path and has no credentials anywhere; the working implementation scrapes the public AHPRA register and returns registration existence + practitioner name + active status (no specialty/consultant signal, so AU registrants default to Non-Consultant). Confirmed working live with real registration numbers. Open Question Q1's AU/AHPRA paragraph still references the dormant PCA qualifications[] path and remains to be tidied.
2026-05-26Collapsed the delivered Registration ACs (all referenced issues verified closed) into a "Delivered" section so the spec reads as current; Medical Registration Verification already split to its own spec.#4548, #4613, #4792, #4894, #4903, #5183, #5189, #7021Rob asked to confirm each referenced issue's state and prune completed ones from the active spec. All 8 issues were CLOSED (none needed implementing), so the delivered ACs were collapsed (kept for traceability, not deleted) leaving the active Registration list as a pointer to the new Medical Registration Verification spec.
2026-05-26Clarified the two-phase structure — added an explicit "Sign-up Flow (3 steps)" section + phase diagram, and corrected the Setup Wizard section to the 5 as-built steps (CV Upload, Immunisations, Connect Your Data, Road Map, Cadence Settings).The spec documented sign-up's pieces (registration, payment, CPD plan) but never stated sign-up is a 3-step flow, and the Setup Wizard section listed an aspirational 8 items that didn't match the shipped 5 steps — conflating sign-up with the post-payment wizard. Rebased the docs to the code (RegistrationForm.tsx 3-step; ONBOARDING_STEPS 5-step). 3-step sign-up confirmed correct (Rob, 2026-05-26).
2026-05-19Drift re-baseline — 10 closed-issue ACs flipped to ✅, 2 new ACs added (#5355 shipped, #5599 open), status promoted to specified.#6299, #5347, #3601, #3605, #3646, #3701, #3709, #5036, #5041, #5049, #5161, #5255, #5355, #5599, #5172Spec carried 10 ACs still marked open for issues that had been closed (#3601, #3605, #3646, #3701, #3709, #5036, #5041, #5049, #5161, #5255). Smart GeoTag step (#5355) was shipped but absent from ACs. App store QR codes (#5599) is a new open enhancement. Guided tour step-defs gap (#5172) now tracked in ACs.
2026-05-05Apply Matt's 3 May Sign-up doctor answers — Q1 AHPRA returns specialist + GP qualifications (binary userType + display specialty proposed); Q2 confirmed defer secondary dept to Profile + Consultant flag drives CPD Home hours; Q3 confirmed temp-password flow; Q4 tax-inclusive display locked by legal constraint (ACCC § 48 + UK DMCCA 2024) — overrides Matt's ex-GST/VAT preference; commercial UX sub-questions noted for live discussion.#5713Q1-3 had engineering proposals; Matt confirmed Q2/Q3 verbatim and asked for clarity on Q1 — code audit confirmed existing AHPRA + GMC integrations surface what's needed. Q4 — Matt preferred ex-tax display; Rob flagged legality concern; legal research confirmed B2C ex-tax display is unlawful in AU and inadvisable in UK, so resolved by law not by call.
2026-05-05Awaiting-Matt sweep — Q4 (#5140 Stripe VAT/GST) resolved engineering-led. AU-first; enable automatic_tax for AUD with 10% GST registered, display tax-inclusive on public pricing page. UK GBP deferred to UK launch phase. for-discussion label removed from #5140.#5140Aligns with AU-first project memory; tax-inclusive matches AU consumer-protection norms.
2026-05-05Wearable connection step priority order updated to match Matt 2026-05-03 lock — WHOOP → Apple HealthKit → Samsung/Google/Android Health → Garmin → Aura.#3646Cross-spec consistency with wellness.md § Integrations; Matt's ordering moves Samsung/Google/Android ahead of Garmin.
2026-04-13Transcript audit 2026-04-13 — §Emergency-contact classified R (requirement); 1 new exclusion AC added under new "Excluded fields" section in Setup Wizard; 1 @wip BDD scenario added.#~§Emergency-contact (~00:07:49) of the 2026-04-13 Dev Session transcript ("Dev environment strategy, timesheet governance, OCR, enterprise pricing") confirmed that the emergency contact field should be removed entirely from the setup wizard. Matt Randell identified it as unnecessary; Rob Duncan confirmed removal. This is an explicit exclusion that was not previously captured in the onboarding spec.
2026-04-01Transcript audit 2026-04-01 — §14 classified R (requirement); 1 new AC added to Setup Wizard section; 1 @wip BDD scenario added.#~§14 of the 2026-04-01 Dev Session transcript ("Testing readiness — infrastructure bugs, mobile menu, CPD logic") identified that the surgical logbook import should be exposed as a step in the onboarding setup wizard so that new users with existing case data can import it during onboarding. This was not previously captured in the onboarding spec. All other paragraphs were classified C (process/workload) or F (bugs already tracked in GH: email infrastructure, mobile menu reversion, CPD home nav, onboarding tracker logic, logbook scroll freeze, OCR, wearables not streaming).
2026-03-18Transcript audit 2026-03-18 — §5 classified R (requirement); 1 new AC added to Registration section; 1 @wip BDD scenario added.#~§5 of the 2026-03-18 Dev Session transcript ("Profile UI & logbook import review") introduced a recommendation that doctors register with a personal email address rather than a hospital email, to avoid losing account access when changing employer. This was not previously captured in the spec. All other paragraphs touching onboarding were classified C or CONFIRM against existing ACs.
Mar 2026AHPRA live validation via PCA API#3939Previous validation was mock/offline
Mar 2026Setup wizard scaffolded#3692Foundation for all onboarding steps
Mar 2026Roadmap and CV steps completed#3705, #3698First steps in wizard
Mar 2026Wearable connection step added#3646Surface all providers, not just Apple Health
2026-04-15Added server-side speciality resolution layer (GMC → PPP today, reusable for AHPRA); broadened canonical speciality list to cover non-surgical fields#4613Frontend fuzzy substring match silently failed on three GMC labels (Cardio-thoracic surgery, Anaesthetics, Plastic surgery), only ran in Signup, and didn't re-run on profile edits. The old 16-entry surgery-heavy seed had no entries at all for most physician, psychiatric, diagnostic or primary-care doctors. Anti-corruption layer separates regulator vocabulary from PPP canonical vocabulary and gives us a forward path to AHPRA + SNOMED/Ontoserver
Apr 2026Guided tour canonical steps enumerated; fixes for step 2 skip (CPD dashboard selector gap), final-step progress indicator, and step 1 copy#4572, #4573, #4571Track E of epic #4636 — regression #4534 introduced a selector gap that silently skipped step 2 for CPD_ONLY users
2026-04-21Fail-fast Stripe key prefix check at backend startup (sk_live_ required in production, sk_test_ required in non-production)#4973Previously getStripe() accepted any string, so a prod deploy with a test-mode key silently no-opped real charges and a dev deploy with a live key risked accidental real charges. Assertion runs before app.listen() so a misconfigured container fails readiness instead of serving broken traffic.
2026-04-22Drift re-baseline — spec reconciled with 26 unreferenced open issues (payments lifecycle, SSO validation, wizard persistence/validation, signup polish); Change Log de-duplicated; Q4 added for Matt on Stripe VAT/GST#5347; issues #4412, #4620, #4792, #4894, #4897, #4902–#4905, #4966–#4972, #5036, #5041, #5049, #5140, #5145, #5146, #5161, #5176, #5183, #5189, #5255, #5261, #5264Spec referenced 6 of 32 open feature:onboarding issues. Payments lifecycle, SSO validation, and wizard persistence were entirely missing from ACs. See audit docs/features/.drift-audits/onboarding.md (2026-04-22). Status stays partial-drift pending Matt Q1–Q4.
Sources & Recordings ​
SourceNotes
https://drive.google.com/file/d/1HDF4acVA0QKImQ29Wu0rp_kVIgb-VGFVg_XwcZnUV6EDescription pending SGD audit
https://docs.google.com/document/d/1YhgQSFL9iOlQLoTrQYSwxRNXH4Dg4wefkItcwljQZmoDescription pending SGD audit

Internal documentation — org members only