Skip to content
View in Notion

PPP Dashboard (PPP Home) ​

Feature Overview ​

Landing page for full-platform users. Surfaces broad, at-a-glance insights across every PPP feature so doctors do not drown in data. One widget per feature (or major sub-feature); each widget is a click-through into the feature. Separate from CPD Home, which is the landing for CPD-tier subscribers.

Three sections ​

  1. Outstanding Onboarding — prompts to finish incomplete setup.
  2. PPP Platform Widgets — one widget per feature.
  3. PPP Roadmap — short- and long-term view of what the user needs to achieve.

Outstanding Onboarding ​

First-run prompts surfaced on the Dashboard so the user finishes setup in context. Includes a "Use Smart GeoTag to enter first timesheet entry" step (22 Apr).

Platform Widgets (7 canonical) ​

  1. PPP Pulse (Wellness)
  2. CPD Progress
  3. Surgical / Practical Logbook
  4. WBA
  5. Retrospective
  6. Appraisals
  7. Timesheet

Each widget has a headline figure for the current calendar year, a sub-breakdown, a click-through to the feature, and an add button where it makes sense.

Widget specifications ​

PPP Pulse (Wellness) — ​

  • Overlay the Weekly Wellness Questionnaire on the existing 14-day Pulse chart as a distinct Weekly Wellness series
  • Readiness line stays in PPP Dark Blue #003977; Weekly Wellness overlay uses Forest Green #167D62 so the two series are visually distinguishable
  • The Pulse widget exposes an Add check-in button in the card header (the visible label is also its accessible name per #7773 — a bare Add was unclear about what was being added, #8641); clicking it opens the WHO-5 questionnaire inline in a dialog on the dashboard (via the shared useInlineQuestionnaire hook), keeping a fallback link to the full Wellness page in the dialog footer, rather than deep-linking to /wellness?openQuestionnaire=true — and does not trigger the surrounding widget navigation (stopPropagation) (#7350, #8641)
  • When the user has no Weekly Wellness Questionnaire submission in the last 7 days, the + Add button shows an amber pending dot #E58117
  • Data contract: the existing useWellnessScoreHistory hook already returns a 14-day Weekly Wellness Questionnaire window via wellness.getQuestionnaireRange; no new procedure is required for the overlay (supersedes the invented wellness.who5.getWeeklyScores in Prototype B below — code identifier retained as the underlying instrument is still WHO-5)

CPD Progress — ​

AHPRA Medical Board rule (AU) — THIS IS WHAT THE WHEEL MUST ENFORCE:

  • 50 hours total annual CPD
  • ≥ 12.5 hours Educational Activities
  • ≥ 25 hours Combined (Measuring Outcomes + Reviewing Performance), with ≥ 5 hours in each
  • Remaining 12.5h flexible across any category

Widget shape:

  • One wheel (simplify from multiple tiles)
  • Four segment minimums visible: MO ≥5, RP ≥5, Combined (MO+RP) ≥25, Education ≥12.5
  • Central number: total hours logged (not capped at 50)
  • Inner + outer rings differentiate booked vs required
  • Light fill; lighter for vacant segments
  • Verified hours only (verified + unverified breakdown lives on CPD Home)
  • "+ activity" button top-right
  • Click widget → CPD Home
  • Remove standalone "CPD Home Widget" duplicate

Overflow / over-minimum behaviour (AHPRA has no upper cap — many doctors log well above 50h):

  • Each category shows current / min. Once current ≥ min, a green ✓ replaces the — remaining.
  • Central number displays total hours logged (e.g. 62 h) — no cap, no stopping at 50.
  • Sub-label shows compliance state: ✓ 50 min + 12 surplus (green) when all mins met and total ≥ 50; X min remaining (amber) when any minimum still unmet.
  • A dashed green outer ring indicates surplus hours beyond the 50h minimum — purely celebratory, not required for compliance.
  • Non-compliant state possible even with high totals: e.g. 80h total but Combined = 20 → not compliant. The Combined chip stays amber until ≥ 25h.

Root cause of repeated display errors (Matt 22 Apr): backend getCPDData tracks MO/RP/Education individual minimums only — the Combined 25h constraint is not modelled in code. See #5361. RACS surgeons have a different framework (65h) — per-regulatory-body targets tracked in #4641.

Surgical / Practical Logbook ​

  • Visible to Surgeon roles only (physician equivalent deferred)
  • Current-calendar-year cases
  • Breakdown by region/category (e.g. Hip, Knee for Ortho) using PPP DB subcategorisation
  • User can choose which category to display
  • "+" button → logbook entry; camera icon → OCR capture

WBA ​

  • Current-calendar-year completions
  • Breakdown per WBA type (CEX / CBD / PBA / SSA)
  • Click a WBA type → list filtered to 12 months + that type (user can change filter)
  • Click the widget card body → WBA feature (/wba) [ac:dashboard.wba-card-click]
  • Non-consultant: "number collected" + Add WBA button
  • Consultant: "number assessed" (attached to other users' profiles)

Retrospective ​

  • Current-calendar-year completions
  • Breakdown per sub-feature: Feedback / Reflections / Audit
  • Click a sub-feature region → that sub-feature screen
  • Click the widget card body → Retrospective feature (/retrospective) [ac:dashboard.retrospective-card-click]
  • Add Retro Entry button

Appraisals ​

  • Rename "Yearly Appraisal" → "Appraisals" everywhere
  • Current-calendar-year completions
  • Breakdown by type: MCR / MSF / 360 / Yearly
  • Click the widget card body → Appraisals feature (/appraisals) [ac:dashboard.appraisals-card-click]
  • Add appraisal button
  • Consultant: separate counts for personal (MSF / 360 / Yearly) vs assessed/provided (MCR / MSF / 360 / Yearly)

Timesheet — ​

  • [ac:dashboard.active-shift-indicator] Active geotag shift indicator — a single banner at the top of the PPP Dashboard shows when a Smart GeoTag timesheet shift is actively running: status (workplace name + "since HH:MM" with a live elapsed-time tick) and an End Shift action. It appears/prompts only once a shift becomes open (not polled or always visible) and disappears the moment the shift closes. Reuses the ShiftRunningIndicator / EndShiftButton pair already shipped for the Timesheet feature's own dashboard (#11126/#10205/#6785) — same timesheets.getActiveShift state source, no duplicated logic. Matt's second UI suggestion on #11101 (2026-07-27); distinct from #11126, which fixed the Timesheet page's own inconsistent display. The banner is not shown to admin-only users (it is a doctor's own shift state; !isAdmin in ppp-dashboard/index.tsx). (#11128)
  • Fortnight view (~10 entries target)
  • Denominator grows as Smart GeoTag detects the user in the workplace
  • Numerator = entries the user has completed
  • Top-left button → create timesheet entry
  • Top-right button → submit current fortnight (jumps to latest fortnight)
  • Click widget → Timesheet feature top
  • Click central number → outstanding entries
Source ​
PPP Roadmap ​

Section 3 of the Dashboard. Full feature spec lives in ppp-roadmap.md — three milestone sources (Cadence Meter / Enterprise / SMART), UK ePortfolio ternary-state timeline, tied to existing PPP activity (WBA / Appraisal / Retrospective / Logbook). National-framework preset library is a separate build in roadmap-national-frameworks.md (#5356).

Open Questions ​

#QuestionProposed answer / statusRef
Q6Cadence settings appear oversimplified / lost vs the configured Cadence Meter when surfaced on the dashboard roadmap. Which cadence items must survive into the dashboard, and at what fidelity?Open — needs Matt's confirmation of the expected cadence-item set and detail level before the roadmap "What's Next" / compliance-snapshot work can faithfully reflect profile-configured cadence.#7344
Closed Questions (5) — click to expand
#QuestionResolutionRef
Q1Include surgical/practical logbook volume targets in Roadmap v1 or defer?Moved + deferred (Rob, 2026-05-06). Question now lives at ppp-roadmap.md § Closed Questions. Roadmap v1 ships without logbook volume targets; SMART-goal tiedTo: { feature: 'logbook' } already covers user-authored logbook targets.—
Q2Enterprise pathways — who authors the templates (engineering vs Admin UX)?Moved to ppp-roadmap.md § Open Questions. Pathway authoring is a Roadmap-scope decision, not a Dashboard one.—
Q3Where is the WHO-5 form? Blocks #5331Resolved 2026-04-27: existing QuestionnaireFormDialog modal at instances/ppp/src/modules/WellnessScore/Dashboard/components/QuestionnaireFormDialog.tsx. Opened from the Pulse widget's + Add button (amber pending dot when no submission in 7 days). Submission shows in Today's Inputs strip — see pulse.html lines 295–299 ("PPP-5 (WHO-5) · Submitted 07:42")..
Q5CPD wheel display mental model — Notion n/50 or spec current/min?Resolved 2026-04-27: neither — see cpd-home.html#cpd-wheel. Two-ring layout: outer (r=82) light tracks for required minima as proportional segments, inner (r=62) saturated achieved arcs (verified 0.45 / unverified dashed 0.25); centre = total verified n h over of {65 RACS | 50 non-consultant} h annual; click segment → filter activity list.
Q4Is B2C timesheet (no hospital configured) in the investor demo?Resolved 6 May (Matt): Yes — B2C timesheet is in the investor demo. It doubles as the Queensland Health demo dry-run; timesheet functionality is a specific QLD Health interest.6 May call

Acceptance Criteria ​

Page-level access (#5515) ​

The PPP Dashboard at /ppp-dashboard is the landing surface for full-platform subscribers only. CPD-tier subscribers and admin personas must never land here — they are routed to their own home surface. This is a page-level visibility AC (a sibling of the per-widget Role-Visibility Matrix). Each persona row is a contracted AC with its own ID so the gate is testable end-to-end without depending on widget-level checks.

Persona rowBehaviour on hitting /ppp-dashboardAC IDIssue
cpd-consultant / cpd-non-consultantRedirect to /cpd-dashboard (CPD Home)dashboard.access-product-tier-cpd-only#5515
ppp-consultant / ppp-non-consultantRender the PPP Dashboard (no redirect)dashboard.access-product-tier-ppp-tier#5515
hospital-admin / hospital-super-admin / super-adminRedirect away from /ppp-dashboard to the admin landing (/hospital-admin or /settings) — admins do not consume the doctor's homedashboard.access-product-tier-admin#5515

The gate runs in the live app (hasFullPlatformAccess route guard at /ppp-dashboard, #5056). The persona switcher mirrors the gate — selecting a CPD persona while on /ppp-dashboard navigates to /cpd-dashboard.

  • ✅ dashboard.single-canonical-module — One canonical dashboard module; /ppp-dashboard-v2 redirects to /ppp-dashboard. † ‡

Layout ​

  • ✅ Dashboard renders three sections: Outstanding Onboarding, Platform Widgets, Roadmap
  • ✅ On mobile the dashboard's recent Action Items peek is hidden: the top-bar logo circle is the Action Items control there (#12141, action-items.header.logo-control), so there is one Action Items badge per screen. Desktop keeps the peek.
  • ✅ Widget list matches 7-item canonical list
  • ✅ Standalone "CPD Home Widget" removed
  • ✅ Widget grid breakpoints: 3 cols ≥1100 px · 2 cols 900–1099 px · stacked 1 col <900 px (mobile polish <480 px tightens padding + typography)
  • ✅ Orphan-row centring — last-row trailing widget sits centred under the middle column at all breakpoints
  • ✅ Sidebar / anchor-nav hides ≤768 px; role switcher becomes a compact <select> on mobile
  • ✅ Every section H2 is deep-linkable via hash anchor; a matching #slug in the URL auto-expands the collapsed section and scrolls it into view
  • ✅ Sections are expandable/collapsible with chevrons in each H2; expand state persists per-user in localStorage; defaults open (Onboarding only when incomplete)
  • 🅼 dashboard.ux.breadth-first — the dashboard layout and content ordering prioritises breadth-first information architecture: high-level status tiles at the top (Pulse summary, CPD %, HR Passport Blue Tick), drill-down sections below. A user should be able to assess their overall health at a glance in the top viewport without scrolling. Design principle — applies to all dashboard layout decisions, not a discrete deliverable. (22 Apr 2026) (closed — architectural guideline, not a work item)
  • ✅ dashboard.welcome-back-frequency — "Welcome back" message/banner is suppressed for users whose last_login_at is within the last N days (default N = 7, config-driven via env or feature flag so it can be tuned without a redeploy); renders only for users returning after a longer absence; dismissable within a session with dismissal persisting for that session (12 May 2026) (#5939)
  • ✅ dashboard.greeting.rotating — the dashboard H1 greeting rotates across a small on-brand set (e.g. "Welcome back", "Good to see you", "Ready when you are", "Let's get to it", + name), one line picked per mount, so it stays fresh instead of the same "Welcome back" on every load. Supersedes the dashboard.welcome-back-frequency 7-day gating — variety removes the repetition rather than suppression. Copy pending Matt. † ‡
  • ✅ dashboard.cpd-metric-hover-tooltips — Explanatory text for each dashboard metric tile is moved off the surface and into an info icon (i glyph) adjacent to the metric label; hover (desktop), tap (mobile), and keyboard focus on the icon reveals the tooltip — a11y requirement: tooltip is keyboard-accessible and meets WCAG 2.1 AA; metric tile shows value + label only by default (12 May 2026) (#5938)
  • ✅ dashboard.org-dashboard.cpd-alignment-okr-cross-ref — The Hospital Executive Admin dashboard's CPD-alignment OKR card (CpdAlignmentSection.tsx under instances/ppp/src/modules/HospitalExecutiveAdmin/Dashboard/, wiring the CPD-alignment OKR v1 shipped in #7363) is the B2B Organisational Dashboard, not the doctor's PPP Dashboard. It matches this spec's instances/ppp/src/**/Dashboard/** code-path glob but is governed by organisational-dashboard.md; the OKR framework, Key Result targets, and cohort anonymisation guard acceptance criteria are maintained there — see organisational-dashboard.md § OKR framework. (#7363)
  • ✅ dashboard.profile-non-doctor.seat-usage-metering-cross-ref — The Hospital Executive Admin dashboard's "Doctor Seats Used" metering tile (Dashboard/index.tsx under instances/ppp/src/modules/HospitalExecutiveAdmin/Dashboard/, wiring the seat-usage meter shipped in #7877) is the B2B Organisational Dashboard, not the doctor's PPP Dashboard. It matches this spec's instances/ppp/src/**/Dashboard/** code-path glob but is governed by profile-non-doctor.md; the seat-economics acceptance criteria — admin tiers provision unlimited doctor seats with no cap, and doctor seat usage is metered for reporting only (seatLimit null = Unlimited) — are maintained there — see profile-non-doctor.md § Seat economics. (#7877)
  • ✅ [ac:dashboard.nav-cpd-tier] CPD-tier users see CPD Home / Reports / My Profile only — PPP Dashboard, Wellness, Surgical Logbook, WBAs, Retrospective, Appraisals, Timesheet, Attendance, PPP Passport hidden. (Wellness is a full-PPP feature, not part of the CPD-only tier; the PPP Dashboard landing surface is PPP-tier only — CPD-only users land on CPD Home.)
  • ✅ [ac:dashboard.nav-ppp-logbook] All PPP-tier doctor personas (consultant + non-consultant) see the Logbook nav item — gated on PPP access, not isSurgeon. The label still varies surgical/procedural via logbookVariant. CPD-only and admin/staff personas do not see it. (#7358)
  • ✅ [ac:dashboard.nav-admin] Admin personas see admin surfaces only, not the doctor feature set

Section 2 period filter ​

  • ✅ Section 2 header renders a 3M / 6M / 1Y / All period filter
  • ✅ Default is 1Y — matches the UAT dashboard convention; supersedes "All Time" per Matt 22 Apr
  • ✅ Filter control appears once at section level (avoids redundancy)
  • ✅ Each widget's subheading reflects the active filter — e.g. "Primary cases · Last 3 months" or "Collected · All time" — so the scope is visible without referencing the filter control (#8954)
  • ✅ Filter selection is session-scoped; reverts to 1Y on next page load

Widgets — infrastructure ​

  • ✅ All module widgets render and are tappable
  • ✅ Tier-gated by accountAccess via hasFullPlatformAccess
  • ✅ Explicit staleTime on dashboard queries (SUMMARY 5m, WELLNESS 1m)
  • ✅ Surgical Cases and WBA Summary widgets refresh after mutation
  • ✅ CPD widget refreshes after CPD add/edit/delete
  • ✅ "View All" in Recent Activities widget routes to /cpd-activities
  • ✅ TotalOperationsWidget drill level 2 slice navigates to cases list
  • ✅ Surgical Performance Overview counts imported CSV cases
  • ✅ BDD step defs wired for doctorsWithLockedPlanPercentage
  • ✅ Current-calendar-year default scoping across widgets — locked by Matt 22 Apr, supersedes
  • ✅ dashboard.report.date-default — Exportable report date pickers default to current calendar year; user can narrow to a shorter custom period for a specific export.† (built: instances/ppp/src/modules/Reports/CPD/UserActivities/hooks/useFilterState.ts — defaultStartDate = new Date(currentYear, 0, 1), defaultEndDate = new Date(currentYear, 11, 31); verified by @regression BDD) (#7489)
  • ✅ Surgical useQuery duplicate enabled key fixed — silent tier-gate shadow resolved
  • ✅ dashboard.customise-widgets — a discoverable "Customise" button toggles a reorder-only edit mode on the PPP dashboard widget grid: a banner explains the interaction, each widget gains a reorder affordance, and "Done" exits; outside edit mode the dashboard is pixel-unchanged. Widgets are NOT deletable (#8671) — there is no remove/− control. The reorder affordance differs by breakpoint (#8671): on the desktop/pointer breakpoint a single grab handle drag-reorders (no arrows); on the mobile/touch breakpoint up/down arrows reorder (no grab handle, since drag is unreliable on touch); the split is gated on the existing MUI breakpoint, not a new convention. Pulse stays fixed chrome above the grid and is not customisable; role-hidden widgets never enter the customisable set.††‡ (#8592, #8671)
  • ⛔️ dashboard.customise-add-remove — Superseded by #8671 (2026-06-17). Widgets are no longer deletable, so the per-widget remove badge and the bottom "Add widgets" tray were removed; the AddWidgetTray component and the removeWidget/addWidget/hiddenWidgets hook API were deleted. The customisable set is now exactly the role-resolved default set, reorder-only. A widget a returning user had hidden under the old behaviour re-surfaces (the stored hidden list is ignored on read).† (#8592, superseded by #8671)
  • ✅ dashboard.customise-persistence — PPP-dashboard customisation persists per user, per dashboard, across devices via the dashboardLayouts JSONB map under the dashboard id ppp-dashboard; a doctor who never customises sees the default set + order, unknown widget ids are skipped, and newly shipped widgets append visible. The persisted hidden array is always written empty (#8671 — reorder-only) and any legacy hidden entries are ignored on read.†‡ (#8592, #8671)
  • ✅ dashboard.widget.donut-center-label-legible — the shared donut centre label (PieCenterLabel) paints a thin paper-coloured outline behind its glyphs (stroke: theme.palette.background.paper + paintOrder: 'stroke') so both the primary value and the secondary caption stay legible where the label overlaps a coloured donut segment, regardless of segment colour. Applied on the shared primitive so every donut widget benefits.†‡ (#9927)

Exportable Report — structure ​

  • ✅ dashboard.report.three-tier — Exported portfolio report follows a three-tier structure: (1) high-level summary page, (2) detailed activity log exportable as CSV, (3) associated evidence documents in an appendix or as attachments.† (built: api/backend-ppp/src/services/reportPdfService/pages/ — titlePage.ts → summaryPage.ts → onePager.ts → appendix.ts; CSV at instances/ppp/src/modules/Reports/{CPD/UserActivities,MultiFeature}/utils/csvExport.ts; verified by @smoke BDD) (#7489)
  • ✅ Evidence files in the exported report are not exposed as direct hyperlinks; all evidence downloads are routed through authenticated backend routes.† (built: api/backend-ppp/src/services/reportPdfService/shared/evidenceRef.ts emits only relative session- (/reports/evidence/:activityId) or token-scoped (/r/:token/evidence/:activityId) routes, never a blob/public URL — guarded by isDirectEvidenceHyperlink; resolved through the authenticated route in api/backend-ppp/src/utils/publicReportRoute.ts; report tier rendered by api/backend-ppp/src/services/reportPdfService/pages/evidence.ts) (#7490)

Widget — PPP Pulse ​

  • ✅ Overlay Weekly Wellness Questionnaire on the Pulse widget
  • ✅ Weekly Wellness Questionnaire submission feedback — modal shows score on submit
  • ✅ Broad-panel layout [ac:dashboard.pulse-broad-panel] — Pulse renders full-width above the widget grid, matching V1 <Grid item xs={12}> layout. Card is clickable → /wellness. The whole-card navigation is a real semantic <button> overlay (#7773/#7870) that sits above the embedded chart so a tap anywhere on the chart navigates, including on touch devices (#8640 — previously the chart's SVG plot sat above the overlay and swallowed the tap, so the card read as unclickable on mobile). The chart's own interactive controls (range pill switcher, + Add button, inline questionnaire dialog) stay above the overlay and remain tappable; in day-one (no data sources) mode the card instead routes to /my-profile#wellness-sources.
  • ✅ Dual-series line chart [ac:dashboard.pulse-readiness-ring, ac:dashboard.pulse-history-chart] — uses ScoreHistoryChart (variant="embedded", modules/WellnessScore/Dashboard/components/ScoreHistoryChart.tsx). Chart: MUI LineChart (@mui/x-charts), Y-axis 0–100 WHO-5 standardised scale ((sum/25)×100), X-axis 14-day window. Readiness series in PPP Dark Blue ``; Weekly Wellness series in Forest Green #167D62. Motivational message from latest score. Amber pending dot on + Addwhen no submission in 7 days. Live wiring usesuseWellnessScoreHistory hook (instances/ppp/src/modules/PPPDashboard/index.tsx).

Widget — CPD Progress ​

  • ⏳ Single wheel with category minimums shown inside (Partial. A single SimpleCpdWheel renders with three category arcs (MO / RP / Education), but no category minima are shown — arcs are purely proportional to logged hours (SimpleCpdWheel.tsx comment: "3 category arcs visible … no minima"). (#5969))
  • ✅ Inner + outer rings differentiate booked vs required (built: instances/ppp/src/components/widgets/SimpleCpdWheel.tsx — outer ring = 50h target boundary, inner ring = achieved category arcs)
  • ✅ Light colour palette; lighter still for vacant segments (built: SimpleCpdWheel.tsx — CPD_WHEEL_PALETTE fill/primary tones)
  • ✅ Verified hours only on Dashboard — the PPP Dashboard passes verifiedHours/unverifiedHours from getCPDData through WidgetsSection to CPDProgressWidget, whose headline and wheel centre count verified hours and whose pending hours show as the unverified overlay and callout (wired 5 Oct 2026, #12954; #5969)
  • ✅ "+ activity" button top-right (reinstated CTA) (built: CPDProgressWidget.tsx — cpd-quick-add Activity button)
  • ✅ dashboard.cpd-widget.live-totals — CPD widget central number and all segment hour values reflect live computed DB state, not static fixture data. Regression: a user with 62 h logged must see 62 h in the central display — not a different figure in the widget vs another dashboard surface. Static/fixture data in any widget component is a blocking bug. (#5945)
  • ✅ dashboard.cpd-widget.hours-unit-clarity — CPDProgressWidget's subheading and category legend use the unambiguous "hrs" unit (e.g. "30 hrs of 50 hrs annual", "Measuring Outcomes 6 hrs"), never a bare "h" — the same #7909 bare-unit regression cpd-home.md fixes on the CPD Home wheel, surfacing here because the /ppp-dashboard widget is this spec's own code, not cpd-home's. (#12661; code:instances/ppp/src/components/widgets/CPDProgressWidget.tsx)
  • ✅ dashboard.cpd-widget.hours-unit-clarity — The SimpleCpdWheel renders every hours value with the unambiguous "hrs" unit, never a bare "h" suffix. A bare "h" (e.g. "0h") was misread as "Oh"/zero in Kristin's demo-walkthrough feedback. The wheel centre total, the wheel sub-label, the below-wheel callout and the per-arc hover tooltip all use the "hrs" unit. (#7909) † ‡
  • ✅ dashboard.widget.canonical-standard — every PPP Home widget renders via the shared WidgetCard + WidgetDonut for a uniform grid. Bottom legends split into 2 side-by-side columns from 2+ items (was 4+, #8247) to halve the legend's vertical whitespace; a single item stays centred. Every legend item — whether static or interactive (a drill-down button) — renders with the identical compact 6px swatch-to-label spacing and left-aligned label, so a widget's legend reads the same regardless of whether its items are clickable (#10050 — a bare gap number in the interactive item's MUI sx was read as 6 spacing units = 48px, bloating clickable-legend widgets like Trauma vs Elective so they spread apart and truncated while static-legend widgets like Adult vs Paediatric stayed compact). Equal-size tiles are enforced via one shared DASHBOARD_DONUT_SIZE token (#10186 — Surgical Logbook and Retrospective had silently drifted onto WidgetDonut's smaller pre-#9959 default while WBA/Timesheet/Appraisals passed size={200} explicitly, rendering visibly smaller on the same dashboard; Surgical Logbook's live-data legend also fell back to nothing at all with zero cases logged, unlike its fixed-category siblings, and now renders a "No cases" placeholder row like the sibling SurgicalCasesWidget). † ‡ (#8247, #9983, #10050, #10186)
  • ✅ dashboard.timesheets-submitted.stat-grid — the Timesheets Submitted widget intentionally does not render via the shared WidgetDonut (it is the sole exception to dashboard.widget.canonical-standard, which continues to govern equal-size donut tiles). It presents a compact stat grid: one number-focused StatTile per timesheet status (count as the headline number, status hue as a left accent bar) plus a total summary badge carrying the "N / M fortnights" ratio the old donut centre label showed. Built entirely from existing dashboard tokens (DASHBOARD_WIDGET_FONT / DASHBOARD_WIDGET_COLORS / DASHBOARD_RADIUS and the existing CHART_PALETTE.timesheetStatus palette) — no new brand primitive. Presentation-only change: same three data points, no data-model or backend change. The other four Timesheet donut widgets (Fatigue Shifts, Missed Lunch Breaks, Overtime Shifts, Recall Hours) are unchanged and still enforce the canonical donut standard. † ‡ (#10585)
  • ✅ Click widget routes to CPD Home
  • ✅ Deduplicate shared scoring logic between Dashboard + PPPDashboard
  • ✅ AHPRA Combined ≥25h backend constraint enforced
  • ⏳ Display mental model (approved 2026-04-27). Two concentric rings, proportional minima segments on outer, saturated achieved arcs on inner, dashed unverified overlay (0.25 opacity), centre shows total verified n h over per-role annual target, "on track" pill when ≥70% of target. Click a segment → filter the activity list to that category. (Drift — thinner than spec. CPDProgressWidget renders SimpleCpdWheel (instances/ppp/src/components/widgets/CPDProgressWidget.tsx → instances/ppp/src/components/widgets/SimpleCpdWheel.tsx) with only categories/totalHours/size. The wheel supports a verified/unverified split, but the widget passes no verifiedHours/unverifiedHours, so no dashed unverified overlay shows. The "on track" text was removed (SimpleCpdWheel comment line ~383, #5954). Segment-click activity filtering is not wired from this widget. (#5969))
  • ⏳ Per-role annual target — RACS Specialist Surgeon = 65 h annual; PPP non-consultant + CPD-only = 50 h annual. The wheel denominator and AHPRA/RACS rule tooltip flip on isConsultant. (Drift — not built. SimpleCpdWheel hardcodes the denominator to TOTAL_CPD_TARGET_HOURS (50h, from hooks/useCpdScoreBreakdown); there is no 65h consultant flip. CPDProgressWidget never reads isConsultant. (#5969))
  • ⏳ Wheel sidebar composition — alongside the wheel: Annual CPD Plan tick · Annual CPD Reflection tick · PLR/CAPE "x of 3 groups met" pill. (Drift — not built. CPDProgressWidget renders a category legend and an HLSR tick only; there is no Plan tick, Reflection tick, or PLR/CAPE pill in the component. (#5969))
  • ⏳ Verified vs unverified treatment — verified arcs at 0.45 opacity (saturated category colour); unverified overlay dashed at 0.25 opacity over the same arc. Centre total counts verified hours only. (Drift — not wired in this widget. SimpleCpdWheel can render the verified/unverified split, but CPDProgressWidget passes no verifiedHours, so the legacy single-tone arc renders and the centre shows totalCpdHours (all logged hours), not verified-only. (#5969))
  • ✅ dashboard.cpd-widget.hlsr-tick — CPD Progress widget sidebar displays a dedicated HLSR (High-Level Specialist Requirement) tick for specialties that have an HLSR obligation (e.g. ANZASM for surgical specialties). The tick renders green (✅ complete) when the HLSR is verified for the current year; outlined (⬜ not complete) otherwise. Hidden for specialties with no HLSR (e.g. non-RACS roles). (29 Apr 2026) (#5969) (Built and wired (#7579, resolving the #7577 gap). HlsrTickRow shows/hides on the specialty's HLSR obligation. PPPDashboard/index.tsx queries ppp.cpdHlsrAttestation.getStatus for the current CPD year and passes the persisted hlsrAttested flag. Honestly pending until verified; never fabricated. #8732: HlsrTickRow extracted from CPDProgressWidget.tsx into the shared instances/ppp/src/components/widgets/HlsrTickRow.tsx so the same read-only binary tick renders on both the PPP Dashboard CPD widget and the CPD Home hero panel (cpd.home.hlsr.simple-tick); copy now reads "complete" / "not complete" per Matt's wording.)
  • ✅ dashboard.cpd-wheel-combined-25h-display — the combined Measuring Outcomes + Review of Performance metric (≥25h AHPRA combined requirement) is displayed as a distinct indicator on the CPD wheel sidebar, separate from the total hours target (currently 50h — no 65h tier is wired in this widget's path; the 25h MO+RP minimum is an independent AHPRA constant that applies uniformly). Users see both: total-hours progress AND the 25h MO+RP combined sub-requirement. (22 Apr 2026) (#5973) (Built (#8526). CombinedTickRow in instances/ppp/src/components/widgets/CPDProgressWidget.tsx renders a sidebar "MO + RP combined: X / 25 hrs" row with a green tick once met and amber/pending below — derived via deriveCombinedMoRp (instances/ppp/src/components/widgets/combinedMoRp.ts) from the same MO + RP aggregated hours that feed the wheel arcs; no extra backend call. On /cpd-dashboard the same 25h sub-requirement also surfaces as the dedicated cpd-category-card-combined tile.)

Widget — Surgical Logbook (#5354) ​

  • ✅ [ac:dashboard.surgical-visibility] Visible to all PPP-tier doctor personas (consultant + non-consultant) — gated on PPP access, not isSurgeon; hidden for CPD-only and admin/staff personas (#7358)
  • ✅ Current-year cases with region/category breakdown (Hip / Knee / Other for ortho via PPP DB subcategorisation)
  • ✅ User can choose displayed category
  • ✅ "+" opens logbook entry (/logbook?new=1); camera icon opens OCR (/logbook?new=1&ocr=1)
  • ✅ Existing Total Cases + Primary Surgeon surfaces preserved as-is for surgeons — no behavioural regression
  • ✅ V1 live wire-up — V2 uses fixture data; live wiring needs dashboardLogbook.getSurgicalCasesData tRPC procedure
  • ✅ Physician-equivalent widget for non-surgeon roles — deferred future work, triggered when physician customers enter the pipeline (#5432)

Widget — WBA (#5353) ​

Note (#12836, Rob 2026-10-04): MSF is an Appraisal, not a WBA — the dashboard's Recent Action Items menu labels it MSF (Appraisal) rather than WBA (QMF). Not an acceptance criterion; MSF is now stored as an Appraisal record (type: 'appraisal'), so no surface can show it as a WBA.

  • ✅ Current-year WBAs by type
  • ✅ Click type → list pre-filtered 12 months + type
  • ✅ Non-consultant sees collected count + Add button
  • ✅ Consultant sees assessed count from other users' profiles
  • ✅ The shared WBA dashboard datasets (dashboardService/wba) carry the doctor's specialty curriculum level-4 wording (curriculumRequirement) for the /wba competency and critical-condition widgets; null when no curriculum data is held. Behaviour is specified in appraisals-wba.md wba.competency.preloaded-horizontal-bars. (#12716)

Widget — Retrospective ​

  • ✅ Current-year Feedback / Reflections / Audit breakdown. The shared feedback widget service (dashboardService/feedback) always returns all three states, Submitted, Received and Draft, including zero counts, so a widget legend can list every state (#12770).
  • ✅ The card's Feedback / Reflections / Audit counts resolve for the selected period. Feedback counts Pending and Reviewed rows, and the period's date range is built once per period, not on every render (Task 11 D1, 2026-10-05).
  • ✅ Click sub-feature region opens that sub-feature screen [ac:dashboard.retrospective-subfeature-click]
  • ✅ Add Retro Entry button (via cog-menu quick-action)

Widget — Appraisals ​

  • ✅ Label is "Appraisals" (not "Yearly Appraisal")
  • ✅ dashboard.appraisals-cadence-meter — a horizontal 12-month cadence meter (appraisal-cadence-meter) renders on the appraisals surface: a month-labelled rail with a today needle and coloured chips at each due-date month (MSF distributed forward, MCR / 360 backward) derived from the user's cadenceTracker / cadencePeriodMonths via the shipped calculateAppraisalDueDates engine; past dates are muted and an empty-state message shows when no targets are set. † (#9652)
  • ✅ Current-year count by type (MCR / MSF / 360 / Yearly)
  • ✅ Consultant: separate personal vs assessed counts
  • ✅ dashboard.appraisals-msf-mcr-split — the appraisals summary widget renders MSF and MCR as two distinct labelled sections (appraisals-msf-section / appraisals-mcr-section) instead of one undifferentiated legend row; each section shows the doctor's own "Submitted & Completed" count and, for consultants, the incoming "Received & Reviewed" peer-feedback count, retiring the old "Assessed for others" label platform-wide (the dashboard AppraisalsWidget subText follows the same "Submitted & Completed / Received & Reviewed" vocabulary). † (#9651)

Widget — Timesheet ​

  • ✅ Fortnight view, ~10 entries target
  • ✅ Denominator grows via Smart GeoTag workplace detection
  • ✅ Create-entry button top-left; submit-fortnight button top-right
  • ✅ Click widget routes to Timesheet feature top
  • ✅ Click central number shows outstanding entries
  • ✅ dashboard.timesheet-renders-without-payroll — Timesheet widget renders for every PPP-tier doctor regardless of payroll; no-payroll shows the empty state. † ‡

Outstanding Onboarding ​

  • ✅ "Use Smart GeoTag to enter first timesheet entry" step included (built: instances/ppp/src/modules/PPPDashboard/index.tsx — ONBOARDING_STEPS geotag-first-entry entry)
  • ✅ Section renders only when onboarding is incomplete (built: instances/ppp/src/modules/PPPDashboard/index.tsx — OutstandingOnboarding returns null when remainingCount === 0)
  • ✅ dashboard.onboarding.no-skip — The per-step Skip, "Restore skipped steps" and whole-section "Skip onboarding" affordances were removed in #8027 (Matt 2026-06-02: "the show-complete-so-you-don't-answer-again logic is removed"). The Outstanding Onboarding section now reflects live onboarding.getStatus completion only — nothing can be marked done that isn't — and auto-hides once every step is complete. The wizard tracking + skip columns (onboarding_dismissed_at, dismissed_onboarding_steps, etc.) were dropped (migration 0151_warm_bucky). (#8027, supersedes #7345)
  • ✅ dashboard.onboarding.geotag-prompt-destination — The "Smart GeoTag" first-run prompt links to the hospital linking section under My Profile (not a modal or inline flow); completing hospital linking activates the geofence and enables automated timesheet creation.† (built: instances/ppp/src/modules/PPPDashboard/index.tsx — geotag-first-entry step route: '/my-profile#hospitals'; [ac:timesheets.geotag.hospital-link-destination] markers in instances/ppp/src/modules/MyProfile/components/MyHospitals.tsx; verified by @regression BDD. GeoTag service non-functionality (#7384) does not block the prompt destination.) (#7489)
  • ✅ dashboard.onboarding.complete-profile-accuracy — The "Complete your profile" onboarding step is only marked complete when all required profile fields are filled; partial completion must not check the step off (bug — 1 Apr 2026) † (built: the PPP Home OutstandingOnboarding section on /ppp-dashboard now renders the live onboarding.getStatus result — no fixture done literal (#7345). The completeProfile step's completed is computed by the single backend predicate hasBaseProfileFields && hasSupervisors in api/backend-ppp/src/services/onboardingService/index.ts (getOnboardingStatus), which requires regulatoryBody AND registrationNumber AND cvFile — plus an educational + clinical supervisor for non-consultants — so partial completion can never tick the row. Row tick indicator carries an aria-label of "… — completed" or "… — open" for accessibility and assertion in instances/ppp/src/modules/PPPDashboard/index.tsx; backend unit regression + @regression BDD @issue-7848.) (#7848)
  • ✅ dashboard.onboarding.logbook-import-step — Onboarding tracker includes an "Import your logbook" step; completing a logbook import marks the step as done (1 Apr 2026) † (built: api/backend-ppp/src/services/onboardingService/index.ts — importLogbook step, route: '/logbook-case?import=1', completion predicate eq(activities.isImported, true) reusing the flag set by importSurgicalLogbook.ts; surfaced generically by OutstandingOnboarding in instances/ppp/src/modules/PPPDashboard/index.tsx (live onboarding.getStatus data, no localStorage fixture); @regression BDD @issue-7849) (#7849) When imported cases still have unresolved procedure/hospital matches, the step shows a "Partially complete — N imported cases still need a procedure/hospital match reviewed" note on the full-platform dashboard too (OnboardingSection.tsx, shared text helper utils/onboardingImportNote.ts; Matt #10130, #11186).
  • ✅ dashboard.onboarding.cpd-plan-single-source — The onboarding checklist's CPD-plan step and the dashboard's CPD-plan signal share one canonical "has a CPD plan" definition with the CPD Home tile, the CPD Plans tab and the profile/to-do surfaces. All readers route through the shared backend helper cpdPlanService.hasEstablishedPlan(userId, year, ctx) / establishedPlanCondition() (ne(status, 'draft')), so the surfaces cannot silently diverge when new plan statuses become reachable. (built: api/backend-ppp/src/services/cpdPlanService/hasEstablishedPlan.ts; consumed by onboardingService, dashboardService/cpd, userProfileService, todoListService; @regression BDD @issue-7486) (#7346, #7486)
  • ✅ dashboard.onboarding.row-semantic-button — Every clickable Outstanding-Onboarding row and the whole-card widget navigation overlays are real semantic <button> elements (not a <div>/<li>/<article> carrying a bare onClick), so they are keyboard-operable and screen-reader-announced as buttons; the visible step label remains the accessible name. Completed/non-clickable rows render as plain non-interactive elements. This satisfies the platform interactive-controls standard (#7773) and the now-blocking eslint-plugin-jsx-a11y gate wired into instances/ppp. † ‡

What's Up Next (#8398, #12884) ​

The What's Up Next section (renamed from "This Year's Compliance" by Matt, #11144 2026-09-21) is a horizontal runner of the next 3 months, permanent and foldable (Matt chose option C on #8398). It sits directly above the Roadmap and stays visually distinct from the multi-year Roadmap career view. Items run strictly by date from left to right, with no type weighting (Matt: "ordered in chronological order left to right").

  • ✅ dashboard.compliance-snapshot — The "What's Up Next" runner (#12884) is always visible, collapsible, remembers state, and shows the next 3 months only, strictly in date order: a 3-month surgical-case and WBA cadence check-in, MCR/MSF/360 due dates, CPD reminders at 3, 2 and 1 months before the CPD deadline (the dates processCpdDeadlineReminders fires, DB-tunable), and roadmap milestones. The "Stay on track" nudge shows when an item is overdue. Not yet built: turning a runner item into a To-do or Platform Reminder (waits on #12234), and the "activate" date for each appraisal type is shown as the due date (Matt's "?and also when due" is unanswered). The horizontal runner as a design-system primitive is for-discussion pending Matt's sign-off; it is built as a dashboard-local component until then. † † ‡ (#6382, #7298, #8309, #8398)
  • The snapshot aggregates: (1) the user's Cadence Meter items (configured in profile), (2) CPD activity due dates, and (3) the Annual CPD Reflection window (Nov–Dec, per cpd-home.reflection.november-only); it surfaces a friendly "Stay on track" prompt when a user is falling behind (example copy: "Hey [user], to stay on track with your yearly goals complete [feature] this week"). Shown to every doctor all year — new and established — no onboarding gate. Iterative — UI mockup follow-up tracked in #6382.

Roadmap (#5356) ​

  • ✅ Section 3 renders the Roadmap — full AC in ppp-roadmap.md (built: instances/ppp/src/modules/PPPDashboard/index.tsx — RoadmapSection mounts WhatNextBanner, RoadmapMilestoneTimeline, EnterpriseObjectivesPanel, SmartGoalList from components/roadmap; gated !isCpdTier && !isAdmin). The demo EPA entrustability ladder was unmounted in #8433 (see ppp-roadmap.md § EPA entrustability ladder).
  • ✅ dashboard.roadmap-no-empty-card — The Roadmap bottom row never renders an empty, contentless bordered card. EnterpriseObjectivesPanel self-hides when the doctor has no org pathway; its bordered wrapper is gated on the same condition, so SMART Goals spans full width and no orphaned card shows (#8431).

BDD coverage ​

  • ✅ Missing scenarios authored for every widget AC (#5359)
  • ✅ Stale/malformed scenarios (S06/S10/S14/S20/S21/S28) cleaned up
  • ✅ @regression scenario: no empty bordered card renders beside SMART Goals on the dashboard bottom row (@issue-8431)

Aesthetic (no regression) ​

  • ✅ No Morton Blue UI remnants
  • ✅ No generic emojis
  • ✅ dashboard.clean-prototype-names — No old prototype name references (e.g. "CAPE" from the Moreton Blue prototype) appear in any user-facing dashboard string, label, or placeholder. Regression test to detect re-introduction. (#5946)
  • ✅ Charts have sufficient data density
  • ✅ Chart click-through works
  • ✅ Mobile header regressions cleared
  • ✅ Date filter range works
Status ​
Sub-featureStatusNotes
Widget grid✅ BuiltAll 7 modules represented
Tier gating✅ Built
Query staleTime✅ Built
Surgical + WBA freshness✅ Built
CPD widget freshness✅ Built
Recent Activities navigation✅ Built
Surgical drill level 2✅ Built
Surgical CSV imports in metrics✅ Built
BDD hospital-stats steps✅ Built
Three-section layout✅ BuiltV2 demonstrates (#5429)
Pulse + Weekly Wellness overlay✅ Implemented
Pulse broad-panel layout✅ Built
Pulse + ScoreHistoryChart (live)✅ Builtlive tRPC —
Single CPD wheel✅ Built
Surgical Logbook widget (live)✅ Builtlive tRPC —
WBA widget (consultant + non)✅ Builtlive tRPC —
Retrospective widget (live)✅ Builtlive tRPC —
Appraisals widget (live)✅ Builtlive tRPC —
Fortnight Timesheet widget (live)✅ Builtlive tRPC —
Timesheet orphan fix✅ Builtdiv→article CSS fix
Sidebar nav by persona✅ BuiltPPP-tier + CPD gate — / #7358
Persona matrix (4 PPP personas)✅ Builtlogbook = all PPP personas — / #7358
Onboarding GMC removal (AU)✅ BuiltAU-first —
Onboarding day-one step 2 fix✅ BuiltlocalStorage reset —
Single canonical PPPDashboard✅ BuiltV1 + orphan Dashboard retired (#8432); /ppp-dashboard-v2 → /ppp-dashboard —
Section collapse + hash links✅ BuiltuseSectionExpanded + useHashAnchorDeepLink in PPPDashboard/index.tsx — #5430, #5447
Onboarding conditional hide✅ BuiltremainingCount===0 && !hasSkipped → null in PPPDashboard/index.tsx — #5449
Roadmap section✅ BuiltRoadmapSection (WhatNextBanner/RoadmapMilestoneTimeline/EnterpriseObjectivesPanel/SmartGoalList) in PPPDashboard/index.tsx — #5356
BDD full widget coverage⏳ NeededAll widget ACs — #5359

Open issues on label:feature:ppp-dashboard — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.

Change Log ​
DateChangePR/IssueReason
2026-10-05The PPP Dashboard CPD widget headline and wheel centre now count verified hours only, with pending hours as the unverified overlay and callout, matching CPD Home.#11192, #12954Task 8 reachability check of 5 Oct 2026 (item 21): getCPDData already returned the split but the dashboard dropped it.
2026-10-05The Retrospective card on the PPP dashboard now resolves its Feedback, Reflections and Audit counts. The dashboard builds the selected period's date range once per period instead of on every render.#11209Task 11 audit D1. The range was rebuilt with a new end time on every render, so each Retrospective query got a new key and never settled, and the card stayed at 0 with records present.
2026-10-04The shared feedback widget service (dashboardService/feedback) now always returns Submitted, Received and Draft, including zero counts, instead of dropping zero-count states.#12770, #11209Matt, Notion Retrospective page 2026-05-19, Feedback widget: 'Legend to show items regardless in entries for those events'. The service is shared with the Retrospective Feedback widget, whose legend now lists every state.
2026-10-04The Outstanding Onboarding section on the PPP dashboard now shows the "Partially complete — N imported cases still need a procedure/hospital match reviewed" note beside the "Import your logbook" step when imported cases are still unresolved.#0, #10130, #11186Matt (#10130) asked for the remaining-count note after an import; the dashboard section dropped the backend count (Task 5 #11186 checklist T5-28).
2026-10-04The dashboard's recent Action Items peek (dashboard.recent-action-items) is hidden on mobile, where the top-bar logo circle is now the Action Items control. Desktop is unchanged.#12141#12141 AC8: no two Action Items badges at the top of a mobile screen.
2026-10-04The dashboard Recent Action Items menu labels an MSF as MSF (Appraisal) instead of WBA (QMF), using the shared formatTodoTypeLabel helper. No acceptance criterion changed.#0, #12836#12836 Rob decision 4 Oct 2026: MSF is an Appraisal, not a WBA. Display slice only.
2026-10-04The dashboard "This Year's Compliance" section becomes the "What's Up Next" runner. It is a horizontal, strictly date-ordered outlook of the next 3 months (cadence check-in, MCR/MSF/360 due dates, CPD 3/2/1-month reminders, roadmap milestones) instead of a 12-month calendar grid.#12884, #11144Matt, #11144 (2026-09-21): name "What's up next", scope "next 3 month outlook", "ordered in chronological order left to right". Inclusions from his 28 Jun Notion brief. The runner's design-system-primitive status is for-discussion.
2026-10-04The Appraisals overview widget (MSF, MCR, 360) shows the panels Matt's per-role matrix gives each role, headed "Submitted and completed" and "Received and reviewed". The Completed count shows for every role.#12757, #11194Spec drift #12757 against the Notion Appraisal brief. The PPP Dashboard card stays a single ring (the first panel the role is entitled to).
2026-10-03The WBA dashboard datasets (getCriticalConditionsData, getWBACompetencyData) now return the specialty curriculum's level-4 wording as curriculumRequirement.#12716Bug #12716 — the /wba widgets derive their level-4 target from the doctor's specialty curriculum instead of a global constant; see appraisals-wba.md.
2026-10-01CPDProgressWidget''s subheading and category legend (the CPD wheel embedded on /ppp-dashboard) now read "30 hrs of 50 hrs annual" and e.g. "Measuring Outcomes 6 hrs" instead of a bare "h" unit.#12661Found live during the Async Task 8 CPD Home Lifecycle audit (#11192) — same #7909 bare-unit regression as the CpdComplianceTile fix in cpd-home.md's changelog, surfacing here because the wheel widget is dashboard.md-owned code, not cpd-home.md's. No AC text changes.
2026-09-20Renamed the "Task Manager" heading in the dashboard's RecentActionItemsMenu quick-access overlay (dashboard-action-items-overlay) to "Action Items", matching action-items.md's current naming (Matt's #12234 confirmation, superseding #11779's "Task Manager" rename).#12342, #12326, #12234This spec's code-paths: govern instances/ppp/src/modules/admin-org/ppp-dashboard/**, which includes RecentActionItemsMenu.tsx. No AC in this spec pins the overlay's heading text, so this is a straight label-consistency fix — flagged here per CLAUDE.md's spec-drift gate rather than left unrecorded.
2026-08-24"RecentActionItemsMenu.tsx" heading and CTA text updated from "Action Items" / "View all action items" to "Task Manager" / "View all tasks", matching the #11767 platform-wide rename. No change to the widget's poll/refresh behaviour (notifications.perf.action-items-badge-poll, #10931) — label text only.#11779, #11767#11767 renamed the Actions/Action Items surface to "Task Manager" across the app; this dashboard dropdown is one of the surfaces naming it, so its label needed updating to stay consistent, without touching the already-documented polling logic this spec covers for the same file.
2026-08-20PPP Dashboard shows a single "shift running" indicator when a Smart GeoTag timesheet is actively running — status (workplace + elapsed time) plus an End Shift action — that appears only once a shift becomes open.#~, #11128Matt's second UI suggestion on #11101 (2026-07-27), answered 2026-08-11: a single indicator, showing status + an end-shift action, that prompts once a shift is open rather than always visible. #11126 (closed) first fixed the Timesheet feature's own inconsistent active-shift display; #11128 surfaces that same trustworthy state on the main PPP Dashboard, where nothing showed it before. Reuses the ShiftRunningIndicator / EndShiftButton pair already shipped for the Timesheet page (#10205/#6785) — no duplicated open-shift logic, same timesheets.getActiveShift source.
2026-07-15Timesheets Submitted widget re-presented as a compact stat grid (Concept 2) — one number-focused tile per status (Approved / Submitted / Saved) plus a total summary badge — replacing the WidgetDonut for this widget only. The other four Timesheet donut widgets are unchanged and still enforce dashboard.widget.canonical-standard.#~, #10585Rob (issue #10585, deep-dive decision recorded on the issue): the Timesheets Submitted doughnut was "flabby and oversized for the value of what it is conveying" — three simple counts do not warrant a chart. Concept 2 (compact stat grid) was chosen as the fastest, lowest-risk alternative, built entirely from existing dashboard tokens (DASHBOARD_WIDGET_FONT / DASHBOARD_WIDGET_COLORS / DASHBOARD_RADIUS and the existing timesheet-status palette) with no new brand primitive. dashboard.widget.canonical-standard is unchanged: it enforces equal-size donut tiles across the donut widgets, and this widget is now intentionally not a donut, so no existing AC's stated behaviour changes.
2026-07-08dashboard.widget.canonical-standard: extracted a shared DASHBOARD_DONUT_SIZE token so every PPP Home donut tile (Surgical Logbook, WBA, Retrospective, Appraisals, Timesheet) renders at the same fixed size; Surgical Logbook''s legend now falls back to a "No cases" row instead of rendering no legend at all when there is no data for the selected period.#10186Rob + Matt (Dev Session call transcript 2026-07-08 06:15 BST, ~00:25:59-00:26:34): the Surgical Logbook donut had no legend and appeared a different size to WBA's, and the Retrospective donut differed again. Root cause: WBA/Timesheet/Appraisals already passed an explicit size={200} (#9959) but Surgical Logbook and Retrospective omitted it, silently falling back to WidgetDonut's smaller pre-#9959 default; Surgical Logbook's legend was also the only one of the five built from live category data with no empty-state fallback, so it disappeared entirely with zero cases logged. Rob's decision on the call: every dashboard donut chart must be identical in size with a consistent legend.
2026-07-06dashboard.widget.canonical-standard: WidgetDonut's interactive (clickable) legend items now use an explicit '6px' string for the swatch-to-label gap instead of a bare number, matching the static legend item's spacing (was rendering 48px via MUI's sx spacing-transform vs. the static path's plain-style 6px).#10050PO-reported inconsistency (#10050): the shared itemStyle object is spread into a plain style={} for static legend items (bare 6 -&gt; 6px, per React DOM convention) but into an sx={} for interactive ones (bare 6 -&gt; 6 * theme.spacing(1) = 48px under the app's default 8px theme unit), so clickable legends looked visibly more spread out than static ones despite sharing one style definition. The fix lives in the shared WidgetDonut primitive, so every widget with a clickable legend (WBA, Timesheet, CPD, Retrospective, etc.) is corrected for free.
2026-07-02dashboard.widget.canonical-standard: WidgetDonut bottom legends now split into 2 side-by-side columns from 2+ items (was 4+, superseding the #8247 threshold), halving the legend's vertical whitespace on the PPP Home widget grid. A single-item legend still renders as one centred item.#9987, #9983PO request (Rob, 2026-07-02): a 2- or 3-item legend was stacking as one tall centred column even though the widget standard already supports a 2-column layout at 4+ items — lowering the threshold applies the same density improvement to the common 2-3 item case.
2026-07-01Added dashboard.widget.donut-center-label-legible AC — the shared PieCenterLabel donut centre label now paints a thin paper-coloured outline behind its glyphs (stroke: background.paper + paintOrder: 'stroke') so both the primary value and secondary caption stay legible where the label overlaps a coloured donut segment.#9936, #9927PR #9936 fixes user shake-to-report #9927 (dark centre-label text overlapping the coloured ring on the /add-timesheet Timesheets Submitted donut). The reporter's suggested fix — "Add a thin white border to text" — is applied on the shared primitive so every donut widget benefits; the new AC records the shipped behaviour, cited via src:issue-9927.
2026-06-29Added dashboard.appraisals-cadence-meter AC — the appraisals widget now surfaces a horizontal 12-month cadence meter (month-labelled rail, today needle, per-type due-date chips) derived from the user's cadence settings via the shipped calculateAppraisalDueDates engine, with muted past dates and an empty-state when no targets are set.#9753, #9652PR #9753 added the horizontal appraisal cadence meter, a dashboard-surfaced widget change the spec-drift gate maps to the dashboard feature; the new AC records the shipped behaviour, cited to the 2026-05-19 Dev Session transcript via src:issue-9652.
2026-06-29Added dashboard.appraisals-msf-mcr-split AC — the appraisals summary widget now splits MSF and MCR into two distinct labelled sections (appraisals-msf-section / appraisals-mcr-section) and adopts the agreed received/reviewed vs submitted/completed vocabulary platform-wide (dashboard AppraisalsWidget subText included), retiring the old "Assessed for others" label.#9750, #9651PR #9750 surfaced a dashboard-visible change to the appraisals widget (MSF/MCR split + vocabulary) that the spec-drift gate maps to the dashboard feature; the new AC records the shipped behaviour, cited to the 2026-05-19 Dev Session transcript via src:issue-9651.
2026-06-21Clarified the CPD-tier sidebar nav AC (dashboard.nav-cpd-tier) — CPD-only users see CPD Home / Reports / My Profile only; Wellness and the PPP Dashboard landing surface (plus Attendance and PPP Passport) are now explicitly listed as hidden.#9018, #5579The AC text previously listed Wellness as visible to CPD-tier users, but Wellness is a full-PPP feature gated behind PPP access — the zero-trust routing already redirects CPD-only users away from /wellness (see auth.feature "CPD-only user navigating directly to /wellness is redirected to the CPD dashboard"). This corrects the spec to match the shipped native CPD-only menu (#8964/#8950/#8951); docs-only, no code/BDD change.
2026-06-20Default feature-page WidgetSection components to open on first visit; persist collapse choice per user in localStorage.#8991, #8949UAT: mobile user (iPhone) found feature widgets collapsed by default with no indication content existed — #8949. WidgetSection now defaults to expanded on all viewports and remembers the user's explicit collapse/expand choice via localStorage keyed by sectionId + userId.
2026-06-20Wire Timesheet, Retrospective (×3), and Appraisals orchestrator queries to activeDateRange so data matches the period filter label#8988, #8954PR #8981 squash-merged only the label-threading commits; the follow-on commits wiring activeDateRange into index.tsx orchestrator queries were not included. This PR completes the full fix: all non-CPD queries now respect the selected period.
2026-06-20Widget subheadings now reflect the active period filter — selecting 3M/6M/1Y/All updates the subheading line on every widget card (e.g. "Primary cases · Last 3 months", "Collected · All time"). Previously the subheadings showed a hardcoded calendar year that never changed when the filter was toggled.#8981, #8954The period filter state was managed in PPPDashboard but was never passed down to WidgetsSection, so all widget subheadings derived their scope text from currentYear directly. Added periodToLabel() helper to PeriodFilter.tsx and threaded period → activePeriodLabel through the component tree. This clarifies to the user which time window each widget's data covers, addressing the UAT bug report (#8954). The existing AC "Filter label appears once at section level" refers to the filter control placement, not the subheading scope text; no AC changes required.
2026-06-17Restored the Add WBA affordance on the PPP dashboard WBA tile — the non-consultant "+ Add WBA" button now routes to /wba?add=1 (the working add flow) instead of the dead /wba?new=1 the WBA page ignored. Aligned the legacy WBASummaryWidget's Add WBA route off the non-existent /wba/add subroute too.#8716, #8666During the atomic-design UI standardisation the Add WBA button kept rendering but its navigation drifted to /wba?new=1, which the WBA page never handles (it opens its add dialog only on ?add=1 via useModalStates FORM_MODES.add). The affordance was effectively dropped — the button did nothing. Matches the existing dashboard.wba-collected-visibility AC, so no AC change; this fragment records the regression fix. (#8666)
2026-06-17Dashboard customise-widgets edit mode is now reorder-only — widgets are NOT deletable (the per-widget remove badge and the bottom Add-widgets tray are removed). The reorder affordance differs by breakpoint: desktop uses a single drag grab handle (no arrows); mobile uses up/down arrows (no grab handle, since drag is unreliable on touch). Applied to the shared customise framework so both the PPP dashboard and the surgical logbook follow the same rules.#8671Product decision (Dev Session 2026-06-16, confirmed by Rob 2026-06-17). The call was contradictory on deletability; Rob resolved it to re-order only. Drag is the natural desktop interaction but unreliable on touch, so mobile keeps explicit arrows. Removing deletion drops the AddWidgetTray and the removeWidget/addWidget/hiddenWidgets hook API; previously-hidden widgets re-surface (stored hidden list ignored on read, always written empty). Supersedes the dashboard.customise-add-remove AC; updates dashboard.customise-widgets and dashboard.customise-persistence. (#8671)
2026-06-16Renamed the PPP Pulse widget add button from a bare "Add" to "Add check-in" so it is clear what tapping it adds, and made the visible label its accessible name (dropping the diverging aria-label).#8684, #8641UAT report — "Not clear what user is adding here". The icon-plus-"Add" label gave no context, and the aria-label diverged from the visible text.
2026-06-16Fixed the PPP Pulse widget reading as unclickable on mobile — the whole-card navigation button now sits above the chart and a tap anywhere on it routes to /wellness, honouring the existing dashboard.pulse-broad-panel "Card is clickable → /wellness" criterion.#8673, #8640UAT report — the chart's SVG plot sat above the navigation overlay and swallowed every tap, so the card never navigated on touch devices.
2026-06-10Adopt the shared customise-widgets edit mode (#8241) on the PPP dashboard widget grid. The grid (CPD Progress, Surgical Logbook, WBA, Retrospective, Appraisals, Timesheet) becomes the array-driven WidgetConfig + renderWidget model and mounts the shared CustomisableDashboardGrid + CustomiseButton under the dashboard id ppp-dashboard. Adds dashboard.customise-widgets, dashboard.customise-add-remove, dashboard.customise-persistence.#8619, #8592Cascade of #8241 (Rob, acting PO, 10 Jun 2026): the approved customise-dashboard edit mode must appear on every page with a widget grid, as a DRY adoption of the dashboard-agnostic shared framework — no per-page fork. Pulse stays fixed chrome above the grid; role-hidden widgets never enter the customisable set.
2026-06-10Built the Combined (Measuring Outcomes + Review of Performance) ≥25h AHPRA sub-requirement indicator on the CPD Progress widget sidebar. CombinedTickRow in CPDProgressWidget.tsx renders a "MO + RP combined: X / 25 hrs" row (green tick once met, amber/pending below) derived via deriveCombinedMoRp (combinedMoRp.ts) from the same MO + RP aggregated hours that feed the wheel arcs — no extra backend call. Flipped AC dashboard.cpd-wheel-combined-25h-display from drift to built.#8557, #8526SGD Spec→Code drift (#8526) — buildDefaultCategoryArcs emitted only MO / RP / Education arcs, so doctors had no view of the ≥25h MO+RP combined AHPRA sub-requirement (a non-compliant state is possible even with high total hours). The sidebar row (vs a new arc) keeps the wheel uncrowded and the 25h minimum legible, distinct from the 50h total the ring shows.
2026-06-10Made the Timesheet/Logbook widget visibility gate drift-proof and confirmed the empty state for payroll-less PPP doctors. Extracted the tier/role gates into shared, unit-tested predicates in PPPDashboard/widgetVisibility.ts (showTimesheetWidget/showSurgicalWidget = !isCpdTier &amp;&amp; !isAdminPersona, deliberately payrollId-free); index.tsx now derives isCpdTier/isAdmin/showSurgical/showTimesheet from them instead of inline logic. Payroll presence gates only the data fetch and the "set up payroll" footer. Flipped AC dashboard.timesheet-renders-without-payroll from "Bug — currently gated" to built.#8548, #8527SGD drift (Spec → Code). The dashboard gate had read showTimesheet = !isCpdTier &amp;&amp; !isAdmin &amp;&amp; !!user?.payrollId, so a PPP-tier doctor with no payrollId lost the Timesheet widget entirely instead of seeing its zero/empty state — a broken-looking feature. Centralising the gate in a tested predicate stops it silently re-acquiring a payrollId condition, and a @regression BDD + unit tests pin the no-payroll/CPD/admin matrix.
2026-06-10Split 2121-line PPPDashboard/index.tsx into single-responsibility section components (sections/, hooks/, components/) — behaviour-locked refactor, zero functional change.#8516, #8221index.tsx was the largest component in the app (2121 lines); decomposing it makes each section independently navigable and reviewable, reduces max-lines lint warnings, and mirrors the User Profile refactor pattern (PR #8200).
2026-06-10Consolidated the three dashboard modules to one canonical PPPDashboard. Deleted the rollback-only V1 PPPDashboard module and the orphaned Dashboard module, renamed PPPDashboardV2 → PPPDashboard (history preserved), and collapsed /ppp-dashboard-v2 into a redirect to /ppp-dashboard. Relocated DASHBOARD_STALE_TIME to WellnessScore/constants. Added AC dashboard.single-canonical-module.#8500, #8432Three parallel dashboard modules let a widget be built on the rollback-only V1 (or the additive V2 preview) and silently never appear on the live dashboard — the YearAtAGlanceSnapshot strand-then-port bug (#7152 → #8395). One canonical module removes that whole class of drift; rollback now relies on git history, not a parallel live module.
2026-06-10Year-at-a-glance compliance snapshot is now always visible in its own collapsible "This Year's Compliance" section, no longer hidden once onboarding completes.#8448, #8398, #8309, #6382Matt chose option C on #8398 — the snapshot is most useful to established doctors tracking year-round compliance, so it earns a permanent (foldable, state-remembering) spot. Lifted YearAtAGlanceSnapshot out of OutstandingOnboarding (which returns null once setup is done) into a top-level section above the Roadmap, re-keyed AC dashboard.onboarding.compliance-roadmap → dashboard.compliance-snapshot, and added a new hash-deep-linkable section id. Framed "This year's compliance" to stay distinct from the multi-year Roadmap career view.
2026-06-10Fixed an empty, contentless bordered card rendering beside SMART Goals on the dashboard Roadmap bottom row.#8436, #8431EnterpriseObjectivesPanel self-hides when the doctor has no org pathway, but its bordered grid-cell wrapper still rendered as an empty white box. The wrapper is now gated on the same hasEnterprise condition, so the CSS auto-fit grid collapses SMART Goals to full width with no orphaned card (desktop + 390px mobile).
2026-06-09Mounted the year-at-a-glance compliance snapshot (incl. the "Stay on track" prompt) on the live PPPDashboardV2 onboarding section. dashboard.onboarding.compliance-roadmap flips to built-and-live.#8395, #8309, #7152, #7015SGD C6 drift — the widget (#7152) was stranded on the rollback-only V1 PPPDashboard, so the live /ppp-dashboard route never rendered it. The V1→V2 port (#8309) resolves the spec↔code gap.
2026-06-04Annotated dashboard.onboarding.compliance-roadmap with a built-but-stranded note — the YearAtAGlanceSnapshot widget (incl. the "Stay on track" prompt) exists (#7152) but is mounted only on the rollback-only V1 dashboard, not the live PPPDashboardV2. V1→V2 port tracked in #8309.#8309, #8214, #7152SGD alignment sweep (2026-06-04) found spec↔code drift — the AC read ⏳ as if unbuilt when it is built-but-unrouted.
2026-06-03Added dashboard.widget.canonical-standard — every /ppp-dashboard widget now renders via the shared WidgetCard + WidgetDonut primitives (DASHBOARD_RADIUS token, legible true-px donut centre, uniform left-aligned legend, square swatches, info-hover, equal-size tiles, responsive 3→2→1, hover tooltips, click-to-filter). CPD Progress migrated onto WidgetCard (dual-ring SimpleCpdWheel kept, compact "X / 50" centre); Surgical / WBA / Retrospective / Appraisals / Timesheet unified through the one standard. Timesheet "incomplete" recoloured from alarm-red to calm slate (palette mock pending PO sign-off).#8266, #8246, #8247The dashboard widgets were inconsistent — bespoke donuts, ragged legends and heights, an MUI sx numeric-radius bug turning cards into circles and buttons into pills. Rob's 2026-06-03 direction was one DRY/SOLID, Storybook-tested widget standard that is best-in-class and demonstrably better than the Moreton Blue origin. Verified via 12 Storybook interaction tests on the primitives.
2026-06-02Made the rotating dashboard-greeting criterion (dashboard.greeting.rotating) executable — implemented its BDD step definitions with real assertions derived from the shared GREETING_TEMPLATES, added a data-ac="dashboard.greeting.rotating" anchor to the greeting H1, and fixed the greeting name to first-name basis (dropping a dead user.surname read that was always undefined and a type error).#8060, #7763, #8061The rotating greeting shipped in #7833 but its BDD scenario referenced two undefined Then steps, so playwright-bdd silently skipped it (missingSteps: skip-scenario) and the criterion was never verified. While wiring the steps, the greeting was found to read a non-existent user.surname (the field is lastName), silently rendering first-name only; per #8061 first-name basis is intended, so the dead reference was removed (clearing a TS2339) and a regression scenario pins the name form.
2026-06-02Outstanding Onboarding section — removed the per-step Skip, "Restore skipped steps" and whole-section "Skip onboarding" affordances. The section now reflects live onboarding.getStatus completion only and auto-hides once nothing remains; the localStorage/tRPC skip persistence (#7345) and its DB columns were dropped (migration 0151).#8049, #8027Part of #8027 (remove Phase 2 Setup Wizard). Matt 2026-06-02: "the show-complete-so-you-don't-answer-again logic is removed." The dashboard Outstanding Onboarding ACs that described localStorage/tRPC skip persistence were stale once the skip was removed.
2026-06-01Added dashboard.onboarding.row-semantic-button AC — clickable Outstanding-Onboarding rows and the whole-card widget navigation overlays are now real semantic &lt;button&gt; elements (not a &lt;div&gt;/&lt;li&gt;/&lt;article&gt; with a bare onClick).#7995, #7870, #7773Wiring eslint-plugin-jsx-a11y into instances/ppp as a PR-blocking gate (#7870) surfaced the dashboard's non-interactive elements carrying click handlers. Refactored the onboarding rows and PPP Pulse card navigation to real buttons so they are keyboard-operable and screen-reader-announced, satisfying the platform interactive-controls standard (#7773).
2026-06-01Dashboard CPD Progress widget HLSR tick is now wired to live attestation data. PPPDashboardV2 queries ppp.cpdHlsrAttestation.getStatus for the current CPD year and passes the persisted hlsrAttested flag to CPDProgressWidget, so the green attested state is reachable. Previously the tick was inert — mounted without hlsrAttested and always pending because no attestation backend existed.#7942, #7579, #7577Resolves the #7577 backing-data gap noted on dashboard.cpd-widget.hlsr-tick. The manual-attestation feature (#7579, Option a) supplies the per-user/per-CPD-year flag the dashboard tick reads; honestly pending until the doctor attests on CPD Home, never fabricated.
2026-06-01Documented that the Hospital Executive Admin dashboard's CPD-alignment OKR section (CpdAlignmentSection.tsx under instances/ppp/src/modules/HospitalExecutiveAdmin/Dashboard/) is an admin-tier surface governed by organisational-dashboard.md, not the doctor's PPP Dashboard, via a cross-reference AC.#7924, #7363The CPD-alignment OKR wiring (#7363) added CpdAlignmentSection.tsx under instances/ppp/src/modules/HospitalExecutiveAdmin/Dashboard/, which dashboard.md owns by code-path glob (instances/ppp/src//Dashboard/); the feature is the B2B Organisational Dashboard spec'd in organisational-dashboard.md § OKR framework, so dashboard.md carries a cross-reference rather than duplicating the criteria.
2026-06-01The dashboard CPD Progress widget (SimpleCpdWheel) now renders all hours with the unambiguous "hrs" unit (wheel centre total, sub-label, below-wheel callout, per-arc hover tooltip) instead of a bare "h" suffix.#7920, #7909A bare "h" hours suffix (e.g. "0h") was misread as "Oh"/zero in Kristin's demo-walkthrough feedback; "hrs" removes the ambiguity.
2026-06-01Documented that the Hospital Executive Admin dashboard's "Doctor Seats Used" metering tile (Dashboard/index.tsx under instances/ppp/src/modules/HospitalExecutiveAdmin/Dashboard/) is an admin-tier surface governed by profile-non-doctor.md § Seat economics, not the doctor's PPP Dashboard, via a cross-reference AC.#7877The seat-usage metering wiring (#7877) edited Dashboard/index.tsx under instances/ppp/src/modules/HospitalExecutiveAdmin/Dashboard/, which dashboard.md owns by code-path glob (instances/ppp/src//Dashboard/); the feature is the B2B Organisational Dashboard spec'd in profile-non-doctor.md § Seat economics, so dashboard.md carries a cross-reference rather than duplicating the criteria.
2026-06-01Onboarding tracker "Import your logbook" step marked built — AC moved to done with built citation and @issue-7849 regression scenario.#7849The "Import your logbook" onboarding step is already implemented end-to-end: getOnboardingStatus returns an importLogbook step (route /logbook-case?import=1) whose completion predicate eq(activities.isImported, true) reuses the isImported flag stamped by importSurgicalLogbook.ts, and OutstandingOnboarding renders all backend steps generically from live onboarding.getStatus data (no localStorage fixture as the old AC note implied). This change reconciles the stale spec note, moves the AC from pending to built, and tags the existing @issue-6381 regression scenario with @issue-7849 for traceability.
2026-06-01Complete your profile onboarding step on PPP Home now ticks complete only when ALL required profile fields are filled — partial profiles keep the row open.#7848Bug (Dev Session 2026-04-01 §OnboardingTracker) — the step was reported as checking off with outstanding profile information. The PPP Home Outstanding Onboarding section is now driven by the live onboarding.getStatus predicate (hasBaseProfileFields && hasSupervisors), not a fixture; added a backend regression test for the partial-completion case and an accessible aria-label on each row tick so completion state is announced and assertable.
2026-05-28Filter bars now consume the shared PillDateRangeFilter; doughnut widgets share the THIN_DOUGHNUT_CONFIG from the canonical ThinDoughnutChart component.DRY refactor — eliminate duplicated chip-preset and chart-radius logic so a single source of truth governs the date-range pill and thin-doughnut look across the app.
2026-05-27Decomposition verification of parent #7321 — reconciled the final stale ⏳ marker ("evidence files not exposed as direct hyperlinks; downloads via authenticated routes") to ✅ with file:line evidence. No code change.#~, #7321The four deferred ACs bundled into parent #7321 (date-picker default, three-tier report, evidence non-hyperlink security, Smart GeoTag destination) were decomposed into #7489 (doc-only reconciliation of the three already-built ACs) and #7490 (the one genuine gap — evidence-document tier via authenticated routes). Both closed. Code-verification confirmed #7490 shipped: reportPdfService/shared/evidenceRef.ts emits only relative session/token- scoped routes (guarded by isDirectEvidenceHyperlink), resolved through publicReportRoute.ts, rendered by pages/evidence.ts. Marker flipped to ✅; #7321 closed as the decomposition tracker.
2026-05-26Onboarding CPD-plan step and the dashboard CPD-plan signal now share one canonical "has a CPD plan" helper with the CPD Home tile, CPD Plans tab and profile/to-do surfaces.#7622, #7486, #7346Behaviour-preserving consolidation so the surfaces cannot silently diverge on plan presence when new plan statuses become reachable (#4839); removes the #7346 bug class at its root.
2026-05-26SGD spec-accuracy pass — demoted over-claimed onboarding + CPD-widget ACs to match the thin live PPPDashboardV2/CPDProgressWidget, promoted Roadmap section / section-collapse+hash-deeplinks / onboarding auto-hide to Built, superseded the contradicted Pulse conic-ring AC (line-chart reality), added a #7348 Timesheet-without-payrollId regression AC and a #7344 cadence Open Question, and extended code-paths to PPPDashboardV2/** + components/widgets/**.#7564, #7563, #7345, #5969, #7348, #7344Spec marked several fixture/hardcoded behaviours ✅ and several built behaviours ⏳; reconciled against ground-truth code so the spec is truthful.
2026-05-26Reconciled three already-shipped deferred dashboard ACs from ⏳ to ✅ — exportable report date pickers default to the current calendar year (dashboard.report.date-default), the exported portfolio report follows a three-tier structure (dashboard.report.three-tier), and the Smart GeoTag first-run prompt links to the hospital-linking section under My Profile (dashboard.onboarding.geotag-prompt-destination). Doc-only; added [ac:...] code markers and BDD scenarios.#7498, #7489, #7321The #7321 dashboard spec audit verified these three ACs as already implemented in code (useFilterState.ts calendar-year defaults; reportPdfService/pages titlePage→summaryPage→onePager→appendix three-tier; PPPDashboardV2 geotag-first-entry route /my-profile#hospitals). The markers were stale ⏳; flipping them keeps the spec truthful. The evidence-document-tier AC is intentionally left ⏳ (owned by sibling #7490).
2026-05-26WBA, Retrospective and Appraisals widget card bodies are now click-through into their feature, via a shared ClickableWidgetCard wrapper.#7370, #7347Spec requires every widget to be a click-through into its feature, but only CPD and Timesheet implemented a card-body click — the other three only navigated via their inner +Add buttons (#7347).
2026-05-26Logbook nav + dashboard widget re-gated on PPP access, not isSurgeon. Collapsed nav-ppp-surgeon/nav-ppp-non-surgeon into a single nav-ppp-logbook AC; re-contracted surgical-visibility.#7369, #7358The #5354/#5579 isSurgeon gate removed the Logbook from every non-surgeon PPP doctor. The logbook is a PPP-tier feature (logbook.md, #4881) — hidden only from CPD-only and admin/staff personas, visible to all PPP doctors. Label still switches surgical/procedural via logbookVariant.
2026-05-21Add year-at-a-glance compliance snapshot widget to dashboard onboarding section (initial iterative UI mockup).#7152, #7015, #6382Matt requested a heads-up display of required tasks with due-date windows and a stay-on-track prompt; initial mockup shipped in #7015 pending design iteration in #6382.
2026-05-21Add year-at-a-glance compliance snapshot widget to dashboard onboarding section (initial iterative UI mockup).#7015, #6382Matt requested a heads-up display of required tasks with due-date windows and a stay-on-track prompt; initial mockup shipped in #7015 pending design iteration in #6382.
2026-05-19PPP Dashboard heading hierarchy fixed — element levels now step by ≤1 (WCAG 1.3.1)#6601, #6521Section headings rendered as h2 were followed by widget card titles rendered as h6, a gap of 4 that confused screen readers; visual typography unchanged via MUI component= swaps.
2026-05-19Resolve gap #6380: AC dashboard.onboarding.complete-profile-accuracy flipped to ✅ — the 'Complete your profile' onboarding step already only ticks when ALL required profile fields are present (regulatoryBody + registrationNumber + cvFile + payrollId, plus an educational + clinical supervisor for non-consultants). Added a @regression @issue-6380 BDD scenario in dashboard.feature that asserts the step is never pre-ticked while fields are outstanding.#6573, #6380Spec-drift: implementation in onboardingService.getOnboardingStatus already satisfied the requirement (predicate hasBaseProfileFields &amp;&amp; hasSupervisors, mirroring ProfileCompletionGuard per #4547) and is covered by the onboardingService unit suite. The transcript-2026-04-01 §OnboardingTracker bug had already been fixed; gap analysis only needed AC verification + a dashboard-level regression guard.
2026-05-19Resolve gap #6381: confirmed the Outstanding Onboarding tracker already includes an 'Import your logbook' step (backend onboardingService + frontend OnboardingChecklist) that deep-links to /logbook-case?import=1 and is marked done once an imported logbook activity exists. Flipped dashboard.onboarding.logbook-import-step AC to satisfied and added a @regression BDD scenario.#6568, #6381Spec-drift reconciliation — feature was implemented under #5435-era onboarding work but the AC was never flipped from pending.
2026-05-19Resolve on-hold gap #6382: compliance HUD refined to year-at-a-glance snapshot view sourcing Cadence Meter items, CPD activity due dates, and Annual CPD Reflection window (Nov–Dec). Includes friendly 'Stay on track' prompts. Flagged as iterative — initial UI mockup to follow before build.#6480, #6382Matt confirmed answer on 2026-05-19 via GitHub comment on #6382.
2026-05-12Remove topbar "Welcome back" entirely; gate dashboard H1 greeting to returning users (absent > 7 days).#6023, #5939Reduces noise for daily users — the greeting was shown on every load in two places simultaneously. Now shown at most once per session and only when the user has been absent for more than the configured threshold (default 7 days, tunable via VITE_WELCOME_BACK_DAYS env var).
2026-04-28Transcript audit 2026-04-28 — §SmartGeoTag classified R (requirement); 1 new AC added to Outstanding Onboarding section; 1 @wip BDD scenario added.#~§SmartGeoTag (~00:10:14) of the 2026-04-28 Dev Session transcript ("React PPP Dashboard prototype — WHO-5 rebrand, smart geo tag, scoping paused") confirmed that the Smart Geo Tag onboarding step on the dashboard must link to the hospital linking section under My Profile. Completing hospital linking activates the geofence and enables automated timesheet creation. The existing AC (✅ #5355) captured the step's presence but not its link destination. WHO-5 rebrand to "Weekly Wellness Questionnaire" already in wellness.md. All other paragraphs were classified C (development process, scoping pause, UK/AU comparison).
2026-03-11Transcript audit 2026-03-11 — §14 classified R (requirement); 2 new ACs added under "Exportable Report — structure"; 2 @wip BDD scenarios added.#~§14 of the 2026-03-11 Dev Session transcript ("Platform overview — first full review") introduced two requirements about the exported portfolio report structure that were not previously captured in the spec: (1) a three-tier report layout (high-level summary → CSV activity log → evidence appendix), and (2) that evidence file links must be routed through authenticated backend routes rather than exposed as direct hyperlinks. All other paragraphs in the transcript were classified C (context) or CONFIRM against existing ACs.
Mar 2026Morton Blue UI replaced with new design system#3629, #3650, #3703–3708Old UI inconsistent with brand
Mar 2026Chart click-through added#3626Users couldn't drill into data
Mar 2026Mobile panels collapsed by default#3497Too much scrolling on mobile
Apr 2026Documented widget-freshness invariant#5028, #5029Surgical + WBA widgets served stale data because fetchers were missing from invalidation helpers
Apr 2026Explicit staleTime policy for dashboard queries#5030All dashboard useQuery calls defaulted to staleTime: 0, cascading re-fetches on every window focus
Apr 2026Tier-gated widgets by accountAccess#5056CPD-only users saw Surgical/WBA/Appraisals widgets they were not entitled to
2026-04-21Triage sweep — 9 open issues mapped to specUnblocks drift detection on the features index
2026-04-22Drift re-baseline — 4 ACs added, 14 stale closed refs marked, Change Log de-duplicated#5344Spec had drifted: duplicated Change Log tables, mangled YAML, closed issues flagged as open
2026-04-22Refocused as pure PPP Dashboard. Split CPD Dashboard content into new cpd-home.md. Removed absorbs: roadmap-national-frameworks.md (Matt flagged as separate build). Captured 22 Apr widget refinements per-widget.22 Apr catchup: "PPP Dashboard and CPD Home are two separate features"; widget shapes locked; Roadmap auto-prefill is a separate QLD-Health scope
2026-04-22Deep spec↔code↔BDD audit — 11 new issues filed for widget-level gaps, bugs, and BDD coverage#5356, #5359Matt's 22 Apr brief required role-aware widgets, current-year scoping, 3-section layout, Cadence Meter roadmap framework; code audit also surfaced a silent tier-gate shadow bug (#5358) and duplicated CPD scoring logic (#5357). All gaps now have traceable issues before any engineering build starts
2026-04-22Year-scoping decision locked — current calendar year is the default across all widgets; supersedes #3951 for the Dashboard#5351Matt 22 Apr: every widget scoped to current calendar year. Cumulative All-Time remains available via filter chip
2026-04-22Implementation Prototypes section added — engineering-ready data contracts, layouts, states, and role gating for all 10 surfaces (A–J)#5350–#5360Path B: rapid prototype pass to unblock parallel build-out today without further spec ping-pong. [INVENTED] markers flag new fields/procedures needing sign-off
2026-04-28Page-level access ACs added (dashboard.access-product-tier-cpd-only / -ppp-tier / -admin); prototype /ppp-dashboard now mirrors the live hasFullPlatformAccess redirect; persona switcher hops to /cpd-dashboard when switching to a CPD persona#5515V1 had the gate (#5056) but no AC ID, so V2 prototype skipped the redirect (intentionally, per #5429) and let CPD personas exercise V2 inline — Matt now wants page-level parity end-to-end so the prototype shows the same routing the live app does
Sources & Recordings ​
SourceNotes
https://drive.google.com/file/d/1HDF4acVA0QKImQ29Wu0rp_kVIgb-VGFVg_XwcZnUV6EDescription pending SGD audit
https://docs.google.com/document/d/1NC6uzEjdGk5jSll-LGNmXGcfYJZLwS5KQnTEEissjic/editDescription pending SGD audit

Internal documentation — org members only