Retrospective
Feature Overview
Retrospective is the reflective practice module. Doctors record reflections on clinical events, give and receive peer feedback, and log audit events. It feeds into the annual appraisal portfolio.
Open Questions
Questions for Matt. Q4 to Q7 were added by the 2026-10-03 Task 11 refresh (#11209). On 2026-10-03 Q4, Q5 and Q6 were closed from existing evidence (Rob approved), and Q7 was narrowed. None has been sent to Matt.
| # | Question | Source | Answer |
|---|---|---|---|
| Q7 | Notion 2026-05-19 "attached to other linked user profiles (reducing double handling…)"; transcript 2026-04-01 ~00:41:51; Rob on #12769, 2026-10-04 | View-only (Rob) |
Closed Questions (6) — click to expand
| # | Question | Source | Answer |
|---|---|---|---|
| Q1 | Non-Consultant ↔ Non-Consultant feedback — intentionally out of scope, or on roadmap? | Feedback sub-feature | Answered (transcript 2026-05-19 ~00:45:53): Intentionally out of scope for v1. On the future roadmap. Matt: "Currently we won't open the non-consultant to non-consultant feedback system but that's potential to open that in the future." |
| Q2 | Audit spreadsheet import — which audit-event types are in-scope for v1? | Audit sub-feature | Answered (transcript 2026-05-19): v1 audit-event types = the Queensland Health audit events enumerated in the QH spreadsheet Matt included, PRELOADED like critical conditions so they appear before population; each taggable to a surgical/practical/logbook case. † |
| Q3 | MOS admission-trigger flow — when is this sequenced? | Long-term Audit vision | Answered (transcript 2026-05-19 ~00:47:24): Long-term future feature. Matt described the "long-term plan" for a management operating system where patient admissions automatically trigger audit notifications. Not in v1 scope. |
| Q4 | Reflection tags: what does "order them how they wish" mean? Is it a user-chosen order of their tag groups, or sorting the reflections inside one tag? | Transcript 2026-07-14 ~01:08:59 | Closed 2026-10-03 (inferred from existing evidence, Rob approved). Tags are for grouping and recall: the user creates their own tags so they can pull related reflections back up. There is no custom sort order. On 2026-07-14 Matt framed the problem as "when there's many reflections how we order them and sequence them to be … easily drawn down on". His 2026-07-29 brief asks only whether tags were added "for user grouping and recall", and on 2026-05-19 he wanted reflections "grouped in ways in which … a user could go back to them".††† retrospective.reflection.user-tags-group-recall is updated. |
| Q5 | Group sharing at ≥3 participants (Jan 2026 walk-through): on 29 Jul you said only audit events go to every user on the case, and reflections don't. Does group sharing still apply to feedback, or is it retired for every type? | #11209 brief item 4 (2026-07-29) vs walk-through Jan 2026 | Closed 2026-10-03 (inferred from existing evidence; Rob decided it is settled). Group sharing at ≥3 participants is retired for every type. Feedback stays one-to-one: Matt's Notion brief (2026-05-19) describes it as bilateral, Consultant ↔ Non-Consultant or Consultant ↔ Consultant. Only audit events reach everyone on the case, by being attached to their profiles (retrospective.audit-event.attach-to-linked-profiles).†† retrospective.multi-person.share-by-default and retrospective.multi-person.opt-out are retired. |
| Q6 | Audit events and CPD: on 26 May you wrote "Audit events are NOT RELATED to CPD Activities". Today the platform awards 1 CPD point when a consultant verifies an audit event. Should an audit event earn CPD at all? | #7308 (2026-05-26); #11209 brief item 3 "CPD scoring where appropriate"; cpd-sheet | Closed 2026-10-03 (inferred from existing evidence, Rob approved): keep the 1 point. Matt's CPD Sheet (Working Sheet) scores "AUDIT - Upload Audit + get verification from other user + Receive Feedback" at 1 per entry, no max, as "Peer review of cases / charts with feedback". The code was built from that sheet ("based on ruleset given by client"). Matt's 2026-05-26 "NOT RELATED" corrected the list of audit-event types (an audit event is not the CPD "audit" quality-improvement activity); it did not address scoring.<abbr title="src:cpd-sheet — Working Sheet row: 'AUDIT - Upload Audit + get verification from other user + Receive Feedback |
Original Vision
Three Tabs
- Feedback — give/receive peer feedback on clinical performance
- Reflection — personal reflection entries on significant events
- Audit Events — logging of clinical audit participation
Multi-person Retrospective (Jan 2026 — new requirement)
From walk-through notes:
"New requirement - if 3 or more people are in a surgery then retrospective needs to go to all those who were in the surgery — not just one to one — so we share by default"
When ≥3 clinicians are present in a procedure, the retrospective/feedback should be shared with ALL participants rather than being one-to-one. (Retired 2026-10-03, Q5: only audit events reach everyone on the case.)
Charts
- Feedback chart (trends over time)
- Reflection chart (frequency/type)
- Audit event chart
CTA on Dashboard
- Expandable button with 3 actions (new reflection, new audit event, view all)
Matt's 17 Apr 2026 Notion Brief — Requirements Update
Source: Retrospective Notion brief.
Framing
- Issue: retrospective practice is lacking across the profession. Feedback is hard to give and easy to misconstrue as bullying without structure.
- Purpose: represent retrospective practice through three protected, trackable sub-features; provide a safe feedback channel; produce exportable datasets for communication of involvement.
Three sub-features (authoritative)
- Feedback — Pendleton model (already built). Bilateral Consultant↔Non-Consultant; Consultant↔Consultant also allowed; NOT currently Non-Consultant↔Non-Consultant. CPD scoring attached.
- Reflections — repository for tidbits of learned insights; shareable for peer feedback to earn CPD scoring; easy-to-find; tagged to surgical/practical cases.
- Audit — track audit events tagged to surgical/practical cases. Populate via spreadsheet import (e.g. readmission within 30 days, return to theatre, mortality within X). Long-term MOS vision: when PPP becomes an integrated Medical Operating System, a patient admission to hospital could trigger an audit event → notify the doctor through the app → increasing awareness and enabling self-investigation.
Acceptance Criteria
Core
- ✅ Feedback tab: give and receive feedback entries — Status table: Feedback tab ✅ Built (#7581) (code-paths:
instances/ppp/src/modules/appraisal/reviews/Feedback/**,instances/ppp/src/forms/GiveFeedbackForm/**,instances/ppp/src/forms/ReceivedFeedbackForm/**) - ✅
retrospective.feedback.pendleton-model— the platform supports the Pendleton model of feedback to create safe, implementable feedback loops; the feedback form structure guides both the giver and receiver through the Pendleton steps.† (#6412) - ✅ Reflection tab: personal reflection with free text and categories — Status table: Reflection tab ✅ Built. Free-text fields (Title, Case Summary, Situation, Learning) plus a free-solo category multi-select (
attributes.categories, astring[]persisted in the activityattributesJSONB) (#7582) (code-paths:instances/ppp/src/forms/ReflectionForm/CreateViewUpdateForm.tsx,instances/ppp/src/constants/retrospective-types.tsREFLECTION_CATEGORIES,packages-shared/ppp/src/zodSchema.tsactivityAttributesSchema.categories) - ✅ Audit Event tab: log participation in clinical audits — Status table: Audit Events tab ✅ Built (#7581) (code-paths:
instances/ppp/src/modules/Development/**,instances/ppp/src/forms/AuditEventsForm/**) - ✅
retrospective.audit-event.qh-hospital-link— audit events can be linked to Queensland Health hospital cases to increase systemic awareness of clinical audit participation across QH facilities.† — anauditEventactivity carries a nullablehospitalIdFK tohospitals; QH facilities are identifiable viahospitals.state = 'Queensland', so linking an audit event to a QH hospital case is supported end-to-end - ✅ All three overview charts render on the canonical dashboard widget organism — Feedback, Reflections and Total Audit Event Numbers each compose
WidgetCard+WidgetDonut(square-swatch legend ≥14px, true-px centre value, info "i" hover, empty-state-safe); no bespoke@mui/x-chartsPieChart remains, segment colours are teal/purple family with red reserved for alerts (#8196) (#8441, #7581) (code-paths:instances/ppp/src/modules/appraisal/reviews/Feedback/components/FeedbackWidget.tsx,instances/ppp/src/modules/appraisal/reviews/Reflection/components/ReflectionsWidget.tsx,instances/ppp/src/modules/Development/components/TotalAuditEventNumbersWidget.tsx,instances/ppp/src/components/widgets/dashboard/**) - ✅
retrospective.shared-page-template— the Retrospective page uses the sharedPageHeaderandSectionCardprimitives with design tokens, not a hand-rolled header or hardcoded colours.†‡ (#7824) (code-paths:instances/ppp/src/modules/appraisal/reviews/index.tsx,instances/ppp/src/modules/appraisal/reviews/components/SharedReviewModule/index.tsx)
Reflections — fields and searchability
- ✅
retrospective.reflection.linked-case-reminder-fields— Reflection form displays the linked surgical case's operation name and hospital number as read-only reminder fields so the user retains context while writing the reflection.† (#7460) (code-paths:instances/ppp/src/forms/ReflectionForm/CreateViewUpdateForm.tsx) - ✅
retrospective.reflection.searchable-title-hospital-number-area— Reflections are searchable by hospital number (URN), broad/specific clinical area, and user-defined title. A search box above the Reflection grids filters the loaded reflections case-insensitively across those fields, which are also surfaced as grid columns.† (#7584) (code-paths:instances/ppp/src/modules/appraisal/reviews/components/SharedReviewModule/index.tsx,instances/ppp/src/modules/appraisal/reviews/Reflection/utils/reflectionSearch.ts,instances/ppp/src/modules/appraisal/reviews/Reflection/config/columns.tsx) - ✅
retrospective.reflection.user-defined-title— Each reflection entry carries a user-defined title field, stored as a realtitlecolumn on the activity so it is indexable and searchable.† (#7458, #7584) (code-paths:instances/ppp/src/forms/ReflectionForm/CreateViewUpdateForm.tsx,packages-shared/ppp/src/schema-groups/cpd/activities.ts) - ✅
retrospective.reflection.duplicate-prevention-linked-case— When a surgical logbook entry already has a linked reflection, the "Add Reflection" option is hidden or disabled for that entry to prevent duplicate reflections being created for the same case.† (#7460) (code-paths:instances/ppp/src/forms/LogbookCaseForm/Consultant/CheckboxOptions.tsx,instances/ppp/src/forms/LogbookCaseForm/NonConsultant/CheckboxOptions.tsx) - ✅
retrospective.reflection.hospital-search-shared-picker— the Reflection form's Hospital field uses the shared instance-scoped hospital search picker (search-as-you-type with fallback), not a dropdown filtered by the user's profile country, so a doctor's assigned hospitals in another country stay selectable. The picker is the sharedHospitalSearchField/useHospitalPickerField, also used by the WBA form (#12796). † (#8585) (code-paths:instances/ppp/src/forms/ReflectionForm/CreateViewUpdateForm.tsx,instances/ppp/src/hooks/useHospitalSearch.ts) - ✅
retrospective.reflection.free-text-not-pendleton— a Reflection is free text, following the original "PPP - Retrospective Evaluations" spreadsheet (Case Summary / Situation / Learning). It does not use the Pendleton prompts, which belong only to the Feedback tool. Matt said this on 30 Jun and again on 13 Jul and 14 Jul. The shippedReflectionFormalready matches. The run-through call he asked for is tracked separately (#10826).††† (#9653, #9827) (code-paths:instances/ppp/src/forms/ReflectionForm/**) - ✅
retrospective.reflection.user-tags-group-recall— a doctor can create their own tags on a reflection. Tags they have used before are offered again on later reflections, and the Reflections list can be grouped, filtered and recalled by tag, so a large set of reflections stays easy to find. Built (2026-10-05, #12772): the free-solo "Categories" field (#7582) now offers the doctor's own earlier tags first (most used first, across every working year), then the 8 curatedREFLECTION_CATEGORIESthey have not used. Tags are searchable (reflectionSearch.ts), shown in a Tags column, and the Reflections tab has a tag chip filter (a reflection must carry every selected tag). True row grouping is a DataGrid Premium feature and is not built; the chip filter is the "group by tag" answer. Tags exist for grouping and recall only; there is no user-defined sort order (Q4, closed 2026-10-03).What "order them how they wish" means is Q4.†† (#12772) - ✅ Overview does not show "No Feedback" when feedback entries exist
- ✅ Audit event notification deep-links to correct record
- ✅ Reviewer notification click loads reflection details
Audit Event — Notifications
- ✅
retrospective.audit-event.auto-notify-all-users— when a user creates an audit event linked to a specific case or hospital number, the system notifies all other users linked to that case that an audit event has occurred, even if they did not enter the information themselves.† (#6414) - ⚠️
retrospective.audit-event.attach-to-linked-profiles— an audit event linked to a surgical case is attached to the profile of every other clinician on that case. It appears in their Audit Events list and widget without them entering it again ("reducing double handling"), and they also get the notification above. Drift (2026-10-03, #12769): the notification fires (notifyParticipantsOnAuditEventCreation), but the record isn't attached.auditEventStats.tscounts only the creator (userId) and the assessor (assessorId), so co-participants never see it. Once attached, it counts in each linked user's own Audit Events widget as well as the creator's; Matt confirmed both users count it on 2026-04-01. Linked users are view-only; the creator is the sole editor (Q7, closed 2026-10-04 by Rob on #12769).††† (#12769) (code-paths:api/backend-ppp/src/services/admin-and-org/dashboardService/development/auditEventStats.ts,instances/ppp/src/modules/Development/**) - ✅
retrospective.audit-event.v1-types— v1 offers the five audit-event types: In-hospital complication; Readmission within 30 days of operation; Representation to Emergency department within 60 days of operation; Reoperation within 90 days of operation; Mortality. Users pick from this list; nothing is triggered automatically from hospital systems (that is the long-term MOS vision, closed Q3).† (code-paths:instances/ppp/src/constants/audit-events.ts) - ✅
retrospective.audit-event.distinct-from-cpd-audit— an audit event is something that happens on a patient case, most often linked to a surgical logbook case. Physicians may log one without a case link, because their admissions aren't tied to surgical cases. It is not the CPD "audit" activity, which is a quality-improvement process. The Audit Event form's logbook-case link is optional (logbookCaseIdcan be cleared). This AC is about the list of audit-event types, not about CPD scoring: Matt's "NOT RELATED" corrected which types appear, and an audit event still earns CPD underretrospective.cpd.audit-event-score(Q6, closed 2026-10-03).Whether an audit event should earn CPD is Q6.† (code-paths:instances/ppp/src/forms/AuditEventsForm/**)
Retrospective lifecycle and CPD (Task 11)
Matt's Task 11 brief (#11209, 2026-07-29) asks for each type to show: entry and completion, the interaction with another user and their response, CPD scoring where it applies, and attachment to surgical cases. Entry and response are covered by the Core ACs above (give/receive feedback, share a reflection for review, the audit event review form). The ACs below cover CPD and case attachment.
- ✅
retrospective.cpd.feedback-and-reviewed-reflection-score— Feedback earns CPD ("CPD Scoring opportunity"), and so does a Reflection shared for review ("ability to share for feedback to achieve cpd scoring"). The credit is logged as a CPD activity record, so it appears in CPD Home.cpdUserActivityHandlerawards 1 point per entry, no maximum, once the item has been completed by a consultant and verified. Feedback scores as "Structured conversation with a peer" and a Reflection as "Peer review of cases / charts with feedback", matching Matt's CPD Sheet.awards 1 point (Peer review with feedback) on the(corrected 2026-10-03: the feedback category was misnamed here; the code and the sheet both use "Structured conversation with a peer").††† (code-paths:FEEDBACK_TYPEandREFLECTION_TYPEbranchesinstances/ppp/src/forms/ReflectionForm/**) - ✅
retrospective.reflection.not-propagated-to-case-participants— a reflection linked to a surgical case stays with its author. It is not attached to, or announced to, the other clinicians on that case. Only audit events propagate (seeretrospective.audit-event.attach-to-linked-profiles). The participant notification returns early for anything that isn't an audit event, and no reflection path reads the group share list.† (code-paths:instances/ppp/src/forms/ReflectionForm/**) - ✅
retrospective.cpd.audit-event-score— an audit event earns 1 CPD point per entry, no maximum, as "Peer review of cases / charts with feedback" (categories Audit, Performance Review - Self), once it has been uploaded, verified by another user and has received feedback. The credit is logged as a CPD activity record and shows in CPD Home. This follows Matt's CPD Sheet. Matt's 2026-05-26 "Audit events are NOT RELATED to CPD Activities" was about the audit-event type list, not scoring (seeretrospective.audit-event.distinct-from-cpd-audit).††‡ (#11209)
Multi-person (Jan 2026) — retired 2026-10-03 (Q5 closed)
Matt's 29 Jul brief replaces the Jan 2026 rule: only audit events go to everyone on the case, by being attached to their profiles (retrospective.audit-event.attach-to-linked-profiles). Q5 was closed on 2026-10-03 (Rob decided it is settled): group sharing is retired for every type, and feedback stays one-to-one. The two ACs below are retired, with their wording kept visible. Engineering note (2026-10-03): resolveGroupRetrospectiveSharing computes sharedWithUserIds, but no delivery path reads it, and the GroupRetrospectiveOptOut toggle isn't shown on any screen. In practice nothing is group-shared today.
⏳Retired 2026-10-03 for every type (Q5 closed). Useretrospective.multi-person.share-by-default— when a surgical case has ≥3 distinct clinician participants, the retrospective is shared with all participants by default (Jan 2026). Superseded for reflections on 2026-07-29 (seeretrospective.reflection.not-propagated-to-case-participants). Whether it still applies to feedback is Q5.retrospective.audit-event.attach-to-linked-profilesinstead: only audit events reach everyone on the case.†† —resolveGroupRetrospectiveSharingflags the case as a group retrospective at theGROUP_RETROSPECTIVE_PARTICIPANT_THRESHOLD(=3) and returns the participant list, but nothing consumes it (#7463) (code-paths:api/backend-ppp/src/services/logbook/surgicalCaseService/groupRetrospective.ts)⏳Retired 2026-10-03 (Q5 closed): there is no group share to opt out of. The unused table, endpoint and component are left in place; removing them is a separate clean-up, not a requirement.† (#7463) (code-paths:retrospective.multi-person.opt-out— a participant can opt out of the group-shared retrospective. The opt-out is persisted insurgical_case_retrospective_opt_outand the endpoint exists, butGroupRetrospectiveOptOutisn't shown on any screen. Depends on Q5.api/backend-ppp/src/routers/procedures/appraisal-and-feedback/retrospectiveSharing/**)- ✅
retrospective.multi-person.no-regression— cases with ❤️ participants retain existing one-to-one behaviour (no group share, empty shared list).† (#7463)
Overview widgets and date range (Matt's Notion page, 2026-05-19)
These come from the "Screenshots Comparison/Commentary" section of Matt's Retrospective Features page, last edited 2026-05-19. No later Matt statement replaces them. Drift for all four widget ACs is tracked in #12770 and for the date range in #12771.
- ✅
retrospective.widget.audit-title-and-breakdown— the audit widget is titled "Audit Events", not "Total Audit Event Numbers". For both user types it shows totals broken down by audit-event type and by whether the event is attached to a logbook case. Partly built (2026-10-04, #12770): the title now reads "Audit Events" and the legend breaks the total down by audit-event type. Built (2026-10-05, Task 11 D5):getAuditEventStatsalso returnsbyCase(attached / not attached to a logbook case) and the legend shows it as "With case N" and "No case N".† (#12770) (code-paths:instances/ppp/src/modules/Development/components/TotalAuditEventNumbersWidget.tsx) - ✅
retrospective.widget.legend-shows-all-items— the Feedback and Audit widget legends list every state and type, including those with no entries yet. Built (2026-10-04, #12770):auditEventStats.tsreturns every configured audit-event type and the feedback service returns Submitted, Received and Draft, each including zero counts. Both widgets build the legend from the full list and draw arcs only for non-zero items.† (#12770) (code-paths:instances/ppp/src/modules/appraisal/reviews/Feedback/components/FeedbackWidget.tsx,api/backend-ppp/src/services/admin-and-org/dashboardService/development/auditEventStats.ts) - ✅
retrospective.widget.reflections-breakdown— the Reflections widget shows Total Reflections Completed, broken down by what they are attached to: a logbook entry, a WBA, or nothing ("novel"). Consultants also see Total Reflections Reviewed. Built (2026-10-05, Task 11 D5):getReflectionWidgetDatareturns Logbook / WBA / Novel counts of completed reflections (a reflection is Logbook when tagged to or generated from a logbook case, WBA when generated from a WBA), plus Reviewed for consultants. The widget reusesWidgetDonutwith existing palette colours.† (#12770) (code-paths:api/backend-ppp/src/services/admin-and-org/dashboardService/reflection/**,instances/ppp/src/modules/appraisal/reviews/Reflection/**) - ⚠️
retrospective.widget.status-shading— the Feedback widget shows Feedbacks Received and Feedbacks Submitted for both user types. Shading tells the states apart: Submitted is hatched or lighter and Reviewed darker; Received is lighter and Actioned darker. Matt marked this "IMPORTANT ACROSS ALL WIDGETS". Drift (2026-10-03, #12770): the segments use flat category colours (CATEGORY_COLORS) with no reviewed or actioned shade. Any new shading primitive must come from design-system tokens and be flaggedfor-discussion.† (#12770) (code-paths:instances/ppp/src/modules/appraisal/reviews/Feedback/components/FeedbackWidget.tsx) - ✅
retrospective.page.working-year-default— the Retrospective page's date range defaults to the user's full current working year, not a rolling period, and the user can go back to previous years. The 3/6/12-month presets are removed here and kept only for exporting reports. Built (2026-10-04, #12771): the page resolves the working-year anchor the same way as the timesheet surfaces (earliest per-hospital start date, then the user-level start date, then 1 Feb AU) and scopes every Overview widget and tab grid to that whole year. A working-year stepper (WorkingYearStepper) replaces the 3M/6M/1Y Overview presets and steps back to previous years. The rolling presets remain only on the Audit Events filter bar, next to its Export button.† (#12771) (code-paths:instances/ppp/src/modules/appraisal/reviews/index.tsx)
Input validation
- ✅ Reflection free-text fields (
learning,situation,summaryOfCase,feedback,comments) are capped at 10,000 characters server-side via Zod.max(10000)onactivityAttributesSchema— shipped #5000 (REFLECTION_TEXT_MAX_LENGTH=10_000applied via.max()inpackages-shared/ppp/src/zodSchema.ts) - ✅ Submitting a reflection field longer than 10,000 characters returns a 400
BAD_REQUESTZod error (not a 500 DB error) — shipped #5000 (the.max(REFLECTION_TEXT_MAX_LENGTH)Zod bound rejects oversized input before any DB write) - ✅ Frontend reflection forms surface the 10,000-char limit via
inputProps.maxLengthand helper text — shipped #5000 (instances/ppp/src/forms/ReflectionForm/CreateViewUpdateForm.tsxsets theinputProps.maxLengthtoREFLECTION_TEXT_MAX_LENGTHandMax 10,000 charactershelper text on each free-text field) - ✅
retrospective.reflection.minimum-content-required— a completed reflection must not be entirely empty; saving with no title and no content (Case Summary, Situation, Learning) is blocked client-side with a helper message and rejected server-side on the completed path.† (#8585) (code-paths:instances/ppp/src/forms/ReflectionForm/CreateViewUpdateForm.tsx,instances/ppp/src/forms/ReflectionForm/reflectionContent.ts,api/backend-ppp/src/routers/procedures/activities/inputSchema.ts)
EOY Reflection availability window
- ✅ EOY Reflection is only creatable between 15 November and 31 December of the plan year (inclusive, UTC), or at any time after the plan year has ended — shipped #5005 (
isWithinEoyReflectionWindowinpackages-shared/ppp/src/constants/cpd-eoy-window.tsenforces theEOY_WINDOW_START_*/EOY_WINDOW_END_*bounds in UTC) - ✅
createEndOfYearReflectiontRPC procedure rejects out-of-window calls with aFORBIDDENTRPCErrorand user-readable message (authoritative server-side check — the frontend gate is a convenience, not a security boundary) — shipped #5005 (api/backend-ppp/src/services/cpd/cpdPlanService/index.tsthrowsTRPCErrorcode: 'FORBIDDEN'withEOY_WINDOW_CLOSED_MESSAGE/EOY_WINDOW_NOT_OPEN_MESSAGEwhenisWithinEoyReflectionWindowreturns false) - ✅ Client (
isEOYReflectionAvailable) and server share the same window bounds via theisWithinEoyReflectionWindowhelper in@ppp-org/ppp/constantsso they cannot drift — shipped #5005 (instances/ppp/src/modules/cpd/plans/helpers.tsisEOYReflectionAvailabledelegates to the sharedisWithinEoyReflectionWindow, the same helper imported by the backend service) - ✅
retrospective.reflection.december-for-hlsr— for a doctor whose specialty carries HLSR requirements, the EOY Reflection window opens 1 December (Dec 1 – Dec 31 of the plan year) instead of 15 November, aligning it with the December HLSR verification window (#8728/#8730) so an HLSR doctor is not told they are "done" while their HLSR verification is still outstanding. Non-HLSR doctors are unchanged (Nov 15 – Dec 31). The shared selectorisWithinReflectionWindow(hasHlsrRequirements, planYear, currentDate)(inpackages-shared/ppp/src/constants/cpd-eoy-window.ts) routes HLSR users to the newisWithinHlsrReflectionWindow(Dec 1 start) and everyone else toisWithinEoyReflectionWindow; the client EOY-button gate (isEOYReflectionAvailable(hasHlsrRequirements)) and the servercreateCpdEndOfYearReflectionenforcement both read this selector so they still cannot drift. Past plan years stay always-available and future plan years stay locked for both cohorts. Logic-only — date-derived, no migration. † (#8735) (#8715)
Dashboard
- ✅ Retrospective CTA button with 3 actions visible on dashboard — the live dashboard Retrospective card's "+ Add Retro Entry" button now opens a menu of Give Feedback / Add Reflection / Add Audit Event, each going straight to that type's add flow (
instances/ppp/src/modules/admin-org/ppp-dashboard/sections/WidgetsSection/RetrospectiveWidget.tsx; #11209) - ✅ Retrospective widget links correctly — the live card (
WidgetsSection/RetrospectiveWidget.tsx) links each legend row to its tab (/retrospective/{feedback,reflection,audit-event}); the olderinstances/ppp/src/components/widgets/RetrospectiveWidget.tsxis unrouted (story only; removal tracked in #12942) (#7307)
Empty States
- ✅ EOY Reflection module: first-time user (no reflections) sees a friendly empty-state block instead of a blank grid/list
- ✅ Empty state renders on both mobile and desktop viewports — shipped #5006; the EOY empty-state block (
instances/ppp/src/modules/wellness/EndOfYearReflection/index.tsx) and the reflection overview widget empty branch (instances/ppp/src/modules/appraisal/reviews/Reflection/components/ReflectionsWidget.tsx, "No Reflections" gray segment) render responsively (#7307)
Status
| Sub-feature | Status | Notes |
|---|---|---|
| Feedback tab | ✅ Built | Works |
| Reflection tab | ✅ Built | Works |
| Audit Events tab | ✅ Built | Works |
| Audit event: QH hospital link | ✅ Built | activities.hospitalId FK → hospitals (#6413) |
| Audit event: auto-notify users | ✅ Built | #6414 — notifies all users linked to same case |
| Audit event CPD (1 point) | ✅ Built | Matt's CPD Sheet; Q6 closed 2026-10-03 |
| Feedback: Pendleton model | ✅ Built | Verified built; structural test added #6412 |
| Charts | ✅ Built | Working |
| Overview "No Feedback" bug | ✅ Fixed | #3987 closed; covered by the "No Feedback" regression scenario |
| Audit event deep-link | ✅ Built | |
| Reviewer notification deep-link | ✅ Built | |
| Dashboard CTA (3 actions) | ✅ Built | Menu on the live dashboard card (5 Oct 2026, #11209) |
| Multi-person retrospective | Retired | Q5 closed 2026-10-03: retired for every type; audit events attach instead (#12769) |
| Audit event attached to co-participants | ⚠️ Drift | #12769 — notified only, not attached; co-participants view-only (Q7 closed) |
| Overview widgets (Notion 2026-05-19) | ⚠️ Drift | #12770 — title and legends built; reflection/logbook breakdowns, shading open |
| Working-year date default | ✅ Built | #12771 — full current working year, step back by year |
| Reflection user tags (group/recall) | ✅ Built | #12772 — own tags offered back; tag chip filter on the grid; no custom sort (Q4) |
Open issues on label:feature:retrospective — issue data unavailable at build time.Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Change Log
| Date | Change | PR/Issue | Reason |
|---|---|---|---|
| 2026-10-05 | A sent-back feedback record that the giver resubmits now returns to the consultant as Pending (whether the giver picks Coffee or "No - Save feedback"). Only the consultant's Accept makes it Reviewed and earns the CPD point. A consultant giving feedback can now pick a non-consultant recipient. The dashboard Retrospective card now resolves its counts. | #11209 | Task 11 audit D1, D2, D3 (Rob's decisions of 5 Oct 2026). Matt's Q1 says feedback is bilateral. The dashboard counts stayed at 0 because the period date range was rebuilt on every render, so the queries never settled. |
| 2026-10-05 | Reflection tags (the Categories field) now have a Tags column in the Reflection grid and are matched by the grid search. Grouping and recall suggestions by tag are still not built. | #11209, #12772 | Task 11 audit D7. This covers the search and the column of #12772 only, so its AC stays open. |
| 2026-10-05 | The live dashboard Retrospective card's "+ Add Retro Entry" button now opens a three-action menu (Give Feedback, Add Reflection, Add Audit Event). Reflection Categories offers the doctor's own earlier tags first, and the Reflections tab has a tag chip filter. Q7 closed (co-participants view-only), "No Feedback" bug row and CTA citation corrected, retired group-sharing BDD scenarios removed. Grid fixes D14 (directory-first user names, no 403 per row) and D15 (row actions reveal on keyboard focus). | #11209, #12772 | Task 11 wave-2 reachability pass (5 Oct 2026): the CTA was a wiring gap, own-tag recall and tag filtering were the small half of #12772, and the spec text still described the unrouted widget and an open Q7 that Rob answered on #12769 on 4 Oct. |
| 2026-10-05 | The Reflections widget now shows completed reflections split into Logbook, WBA and Novel (plus Reviewed for consultants), and the Audit Events widget also splits its total into With case / No case. Both reuse the existing widget donut and palette. The Feedback widget now counts Reviewed feedback. | #11209, #12770 | Task 11 audit (5 Oct 2026) D1 and D5, Rob's decision to build the splits with existing components only. Matt's 19 May Notion brief asked for both splits. The status shading (D4) is not built, because it needs a new visual primitive and is for-discussion with Matt. |
| 2026-10-04 | Settings > Form Prompts rows for GiveFeedback and ReceivedFeedback now drive the question text shown on the Give Feedback form (situation / what went well / what could improve), its sent-back section and the Received Feedback reviewer form. Hardcoded text remains the fallback when no prompts are configured. Rows in a 'further' section drive the further-details question; every other section drives the provider questions. | #11209 | Rob, 4 Oct 2026 video rule: every config screen #11209 names must visibly change the feature. The GiveFeedback/ReceivedFeedback prompt hooks existed but no form called them, so the Form Prompts settings were dead config for Feedback (checklist T11-38). |
| 2026-10-04 | Overview widgets, first slice of the 2026-05-19 widget spec: the audit widget is titled 'Audit Events', and the Feedback and Audit legends list every state and audit-event type, including those with 0 entries (the backend no longer drops zero-count items; the widgets draw arcs only for non-zero items). retrospective.widget.legend-shows-all-items flipped to built; retrospective.widget.audit-title-and-breakdown stays drift for the logbook-attached breakdown. | #12770, #11209 | Matt, Notion Retrospective page 2026-05-19: ''Change "Total Audit Event Numbers" to "Audit Events"''; ''Show audit events "legend" in widget regardless of entries for those events''; Feedback ''Legend to show items regardless in entries for those events''. The reflections breakdown, the logbook-attached audit breakdown and the Submitted/Reviewed status shading are not in this change: the shading needs a new design primitive flagged for-discussion, and both breakdowns need a layout decision for a second split in one donut. |
| 2026-10-04 | Retrospective page date range now defaults to the user's full current working year (anchored on the earliest per-hospital start date, then the user-level start date, then 1 Feb AU) instead of a rolling 3 months. A working-year stepper replaces the 3M/6M/1Y Overview presets and steps back to previous years; the Audit Events tab follows the stepped range. retrospective.page.working-year-default flipped to built. | #12771, #11209 | Matt, Notion Retrospective page 2026-05-19: 'Change this to a working year - not rolling period - Default to full current year. With ability to go to previous years - 3/6/12M is being confused with the roadmap so we should look to remove and replace with a roadmap but keep for exporting reports'. The rolling presets remain only on the Audit Events filter bar, which carries the Export button. |
| 2026-10-04 | The Reflection form's Hospital picker moved into the shared HospitalSearchField / useHospitalPickerField used by the WBA form. Behaviour is unchanged. The linked logbook case's hospital still takes precedence. | #12796 | #12796 asked for one shared hospital picker across forms. This is a refactor of the Reflection form so the WBA form can reuse it. |
| 2026-10-03 | Phase C open questions resolved from existing evidence (Rob approved 2026-10-03). Closed Q4 (tags are for grouping and recall, with no custom sort; retrospective.reflection.user-tags-group-recall updated), Q5 (Rob decided group sharing is settled as retired for every type; retrospective.multi-person.share-by-default and retrospective.multi-person.opt-out retired, struck through, pointing to retrospective.audit-event.attach-to-linked-profiles) and Q6 (keep the 1 point from Matt's CPD Sheet; new ✅ AC retrospective.cpd.audit-event-score; retrospective.audit-event.distinct-from-cpd-audit clarified as being about the type list, not scoring). Narrowed Q7 to edit rights only, since viewing is settled (the event counts in each linked user's widget, Matt 2026-04-01). Corrected the feedback CPD category in retrospective.cpd.feedback-and-reviewed-reflection-score from "Peer review with feedback" to "Structured conversation with a peer". | #11209, #12769, #12772 | Research on 2026-10-03 against Matt's CPD Sheet (Drive), the Retrospective Evaluations spreadsheet (Drive), #11209, #7308, Matt's Retrospective Notion page and the 2026-04-01, 2026-05-19 and 2026-07-14 transcripts, plus a read-only check of cpdUserActivityHandler.ts. New source fragments cpd-sheet and retrospective-evaluations-spreadsheet. Spec-only; no BDD scenarios added, per the spec-refresh rule. |
| 2026-10-03 | Task 11 spec refresh (Retrospective lifecycle, 3 types) against Matt's latest dated statements. Added drift ACs: audit event attached to case co-participants' profiles (#12769); four overview-widget ACs from the 2026-05-19 Notion page: audit title 'Audit Events' plus type and logbook-attached breakdown, legends show every item, reflections broken down by logbook/WBA/novel, Submitted/Reviewed shading (#12770); working-year date default (#12771). Added specified AC: reflection user tags for grouping and recall (#12772, enhancement). Added built ACs: reflections are free text, not Pendleton (#9653); the five v1 audit-event types and audit event vs CPD audit (#7308); CPD for feedback and reviewed reflections; reflections are not propagated to case participants. Multi-person share-by-default and opt-out moved from built to specified under Q5, with the Jan 2026 wording struck through. New Open Questions Q4–Q7. Frontmatter YAML normalised; code-paths extended (all resolve); stale inline paths re-pointed after the bounded-context reorg (modules/Reviews → modules/appraisal/reviews, CPDPlans → cpd/plans, schema-groups/activities → schema-groups/cpd/activities, wellness/EndOfYearReflection; the deleted AddRetrospectiveButton reference removed). status built → partial-drift; notion-last-synced → 2026-05-19 (page last edit). | #11209, #12769, #12770, #12771, #12772, #9653, #7308 | Async Task spec refresh (#11209). The newest dated Matt statement wins. Propagation: walk-through Jan 2026 ('retrospective needs to go to all those who were in the surgery … share by default') → Notion 2026-05-19 (audit 'attached to other linked user profiles') → #11209 brief 2026-07-29 ('only audit would trigger for attachment on all user profiles attached to that case; reflection wound not'). This supersedes the Jan rule for reflections; feedback is open as Q5. Reflection structure: #9653 2026-06-29 ('prompts are for FEEDBACK NOT REFLECTION') → 2026-06-30 call → 2026-07-13 ('Free-text as per original spreadsheet') → 2026-07-14 call ('It's not Pendleton'). Tags: 2026-07-14 call → 2026-07-29 brief item 5. A read-only code check found the group-share resolver has no consumer and the opt-out toggle isn't shown on any screen. Spec-only, no BDD: the scenario requirement is on each fix issue. |
| 2026-07-12 | Fix stale cpdPlanService path citation — update from pre-reorg flat path to api/backend-ppp/src/services/cpd/cpdPlanService/index.ts (bounded-context reorg ADR-0003). | #10519, #10490 | SGD drift C13 — the service moved under services/cpd/ during the bounded-context reorg but the spec still cited the old flat path. Content and behaviour are unchanged; path-only correction. |
| 2026-06-10 | Reflection form Hospital field migrated to the shared instance-scoped search picker; minimum-content guard added so an empty reflection can no longer be saved as completed. | #8611, #8585 | Matt's UAT report (#8585) — the profile-country filter on the old picker hid his assigned GB hospitals from his AU profile ('No options'); and an entirely empty reflection saved with status=completed because neither the form nor the server zod schema required any content. (Complaint B, category provenance, is routed to Matt as a separate product decision and is not addressed here.) |
| 2026-06-10 | Fix the auto-opened reflection dialog so the "Linked Logbook Entry" reminder shows the real operation and hospital names from the just-created case (conforms to retrospective.reflection.linked-case-reminder-fields; no AC text change). | #8604, #8556 | Matt's UAT bug report #8556 (2026-06-10) found the reminder panel showed "Operation: N/A" / "Hospital: N/A" after logging a surgical case. Root cause: the dialog was fed the bare activities.create insert row, which carries procedureId/hospitalId but none of the nested procedure.principalProcedure / hospital relations the names require (those exist only on logbook read queries via LOGBOOK_WITH_CLAUSE); the hospital name was further resolved through the client-side country-filtered list, which dropped on a null hospitalId or country mismatch. The existing AC was already correct — the implementation was violating it. Fixed frontend-only (Option 1): a one-shot logbook.getById re-read re-hydrates the relations and the resolved names are threaded into the form via logbookContext, decoupled from the country-filtered list. The pre-existing @issue-7460 BDD scenario hand-fed the reminder object and never exercised the real create→dialog wiring, so it missed the bug; new @regression @issue-8556 scenarios drive the real resolver. Backend create-response shape unchanged (Option 2 rejected); the hospital-search pathology itself is owned by #8585. |
| 2026-06-10 | Migrate the Retrospective overview charts (Feedback, Reflections, Total Audit Event Numbers) onto the canonical dashboard widget organism (WidgetCard + WidgetDonut). | #8519, #8441 | The overview cards — Reflections and Audit in particular — still used bespoke @mui/x-charts PieCharts, inconsistent with the canonical donut/card/legend standard (#8245/#8236). DRY/SOLID: reuse the shared widget primitives, retire the one-off charts and the red/orange palette (#8196). |
| 2026-06-03 | Resolve Q2 to Closed Questions — v1 audit-event types = the preloaded Queensland Health audit-events spreadsheet (transcript 2026-05-19). | #8166 | SGD governance sweep — transcript-grounded audit found these questions already answered; reconciled the spec to shipped reality and moved them out of Open Questions. |
| 2026-05-27 | Decomposition verification of parent #7307 — reconciled the final two stale ⏳ markers ("Retrospective widget links correctly" and "Empty state renders on mobile and desktop") to ✅ with file:line evidence. No code change. | #~, #7307 | All deferred ACs bundled into parent #7307 were decomposed into sub-issues (#7458, #7460, #7463, #7465, #7466, #7581, #7582, #7584, #7587, #7592, #7598), every one of which has merged/closed. Code-verification confirmed the two markers that remained ⏳ were in fact built: RetrospectiveWidget navigates to the Feedback/Reflection/Audit work-queue routes, and the EOY/reflection empty states (shipped #5006) render responsively. Markers flipped to keep the spec consistent with shipped code; #7307 closed as the decomposition tracker. |
| 2026-05-26 | Reflection enhancements: reflections are now searchable by user-defined title, hospital number (URN), and clinical area via a search box above the Reflection grids, with those fields surfaced as Title / Hospital No. / Clinical Area grid columns. Verified and cited the sibling-delivered ACs — linked-case reminder fields (#6398), user-defined title column (#7458), and duplicate-link prevention (#7460) — and flipped the two searchability/title ACs to built. | #7625, #7584 | #7584 (decomposed from #7307) carried four ⏳ ACs. Three were already implemented by sibling issues (#6398 reminder fields, #7458 title column, #7460 Add-Reflection duplicate prevention); the searchability AC was the genuine gap. Added an opt-in enableSearch path to SharedReviewModule plus a shared, unit-tested reflectionMatchesSearch predicate (title + URN + broad/ specific area, case-insensitive) reused by the grid and the @smoke @issue-7584 BDD scenarios. No schema change — title and urn are existing columns and clinical area is read from the procedure relation already joined server-side. |
| 2026-05-26 | Core: confirmed and smoke-covered the three #7307-decomposed ACs — Feedback tab (give/receive feedback entries), Audit Event tab (log participation in clinical audits), and all three overview charts (Feedback, Reflection, Audit Event) rendering correctly. Cited #7581 on the three Core ACs and corrected their code-paths to the real source locations. | #7620, #7581 | All three ACs were already implemented in modules/Reviews/{Feedback,Reflection} and modules/Development (forms, grids, notifications, export, and three MUI PieChart widgets), but inherited ⏳ markers in the parent #7307 decomposition and carried stale AppraisalsWidgets/** code-paths. #7581 adds the missing @smoke @issue-7581 BDD coverage (give+receive feedback directions, audit-event draft→pending→verified lifecycle, and the empty-state-safe chartData series shared by all three widgets) and points the spec code-paths at the actual files. Test-and-docs only; no runtime or schema change. |
| 2026-05-26 | Wired the 10,000-char reflection/feedback free-text cap into the activity create/update tRPC input schema (api/backend-ppp/.../activities/inputSchema.ts) so an over-limit submission returns a 400 BAD_REQUEST from the input validator instead of a 500 DB error. | #7614, #7587 | The .max(REFLECTION_TEXT_MAX_LENGTH) cap existed on activityAttributesSchema (#5000), but the activity create/update procedures validate input via a local schema that treated attributes as a bare z.record(z.unknown()) — so the cap never enforced on the actual request path and over-limit input still reached Postgres. A superRefine now caps the free-text fields (learning, situation, summaryOfCase, feedback, comments) while preserving the broad Record<string, unknown> type for downstream service consumers. Server-side only; the frontend inputProps.maxLength half is tracked by #7465. |
| 2026-05-26 | Reflection tab core: added a free-solo category multi-select to the personal reflection form (Categories), backed by a new attributes.categories (string[]) field on the shared activityAttributesSchema, plus a curated REFLECTION_CATEGORIES default list. Categories are included in CSV/PDF exports. The Reflection tab, free-text fields, and Reflection chart were already built; this closes the remaining "categories" gap in the core AC. | #7582 | Issue #7582 (decomposed from #7307) required the core Reflection tab to support free text AND categories. The free-text fields, tab wiring, and pie chart already existed, but there was no category field. Categories persist in the existing attributes JSONB column, so no migration is required. |
| 2026-05-26 | Reflections — fields and searchability: two scheduled ACs converted ⏳→✅. (1) ReflectionForm surfaces the linked surgical case's operation name and patient hospital number (URN) as read-only reminder fields; (2) the "Add Reflection" retrospective option is hidden/disabled for a surgical logbook entry that already has a linked reflection, preventing duplicates for the same case. | #7528, #7460 | Implements transcript 2026-03-25 §16 (reminder fields) and §15 (duplicate prevention). The linked-case reminder block already existed from the #6398 logbook↔reflection link work; #7460 confirms it satisfies §16 and adds a defensive disabledOptions guard to AddRetrospectiveButton alongside the existing CheckboxOptions filtering so an already-linked retrospective type can never be re-selected. Frontend-only; linked-reflection state is read from existing relatedForms data, so no migration was required. |
| 2026-05-26 | Group retrospective for multi-person cases — when a surgical case has ≥3 participants the retrospective is shared with all participants by default, with per-participant opt-out. | #7510, #7463 | Walk-Through Notes Jan 2026 — 'if 3 or more people are in a surgery then retrospective needs to go to all those who were in the surgery — not just one to one — so we share by default'. Implements the deferred Multi-person retrospective requirement and clears the 'no issue raised yet' status note. |
| 2026-05-26 | Reconciled stale ⏳ AC markers to ✅ for already-built functionality — the three tabs (Feedback/Reflection/Audit Event) + charts, the 10,000-char server-side Zod cap on reflection free-text fields (with frontend maxLength + helper text), and the server-side EOY Reflection availability-window enforcement (Nov 15 – Dec 31, shared isWithinEoyReflectionWindow helper). Each flipped AC now cites its shipping PR and code path. | #7466, #7307 | The ## Acceptance Criteria ⏳ markers had drifted from the ## Status table and ## Change Log — #5000 (REFLECTION_TEXT_MAX_LENGTH cap) and #5005 (EOY window server enforcement) shipped the work but the AC checkboxes were never flipped, so the spec audit kept re-flagging built features. Genuinely-unimplemented ACs (reflection fields/searchability, multi-person, mobile empty state, widget link) left ⏳ — tracked by sibling issues #7458/#7460/#7463/#7465. |
| 2026-05-20 | AC retrospective.audit-event.qh-hospital-link flipped ⏳ → ✅. Audit-event activities can be linked to Queensland Health hospital cases via the existing activities.hospitalId FK to hospitals (QH facilities filterable by hospitals.state = 'Queensland'). @smoke BDD scenario added under @issue-6413. Status-table row flipped to ✅ Built. | #6413 | Schema audit confirms the requirement from Dev Session 2026-05-19 §QHAuditEvents ("audit events related to Queensland Health Hospitals tracked to increase awareness") is already satisfied by existing infrastructure: activities.type = 'auditEvent' combined with activities.hospitalId referencing hospitals.id, and hospitals.state carries the QLD discriminator. No code change needed — this PR is the spec/BDD record of an existing capability so it stops appearing as a gap in transcript audits. |
| 2026-05-19 | Audit events created on a case now auto-notify every other user linked to that case (via surgicalCaseId, logbookCaseId, or URN+hospitalId match). | #6589, #6414 | Implements retrospective.audit-event.auto-notify-all-users — participants on a shared case should become aware of an audit event even if they did not enter it themselves. |
| 2026-05-19 | Verified the Pendleton feedback model is built; flipped retrospective.feedback.pendleton-model to ✅. Added a structural contract test and a @regression BDD scenario locking the giver/receiver form structure to the Pendleton steps. | #6563, #6412 | Gap issue #6412 added the AC retrospective.feedback.pendleton-model from the 2026-05-19 Dev Session transcript (§PendletonFeedback ~00:43:00). Investigation confirmed the feedback forms already implement the Pendleton model end-to-end: the giver form (FEEDBACK_PROVIDER_QUESTIONS) walks situation → what went well → what could improve, and the receiver form (FEEDBACK_REVIEWER_QUESTIONS) walks clarify → what went well → what could improve → learnings to take forward. A pendleton-model.test.ts structural contract and a @regression @issue-6412 scenario were added to keep the AC traceable to code. |
| 2026-05-19 | Fixed flaky keyboard-focus E2E check for Retrospective Feedback buttons (e2e/a11y/retrospective-accessibility.spec.ts). The prior assertion read document.activeElement synchronously after .focus(), racing with React commits when tabs/modals mounted. Replaced with Playwright's auto-waiting expect(locator).toBeFocused(). Added @regression @issue-6536 BDD scenario. | #6536 | Test reliability — the e2e keyboard-accessibility job was failing intermittently. The buttons themselves ARE keyboard-focusable; only the test's focus-detection pattern was racy. |
| 2026-03-25 | Transcript audit 2026-03-25 — §15 and §16 classified R (requirement); 4 new ACs added under new "Reflections — fields and searchability" section; 3 @wip BDD scenarios added. | #~ | §15 and §16 of the 2026-03-25 Dev Session transcript ("Round 2 feature review — logbook, WBA, OCR, appraisals") introduced requirements for the Reflections sub-feature that were not previously captured in the spec: (1) operation name and hospital number displayed as read-only reminder fields in the reflection form; (2) reflections searchable by hospital number, broad/specific area, and user-defined title; (3) user-defined title field on each reflection; (4) "Add Reflection" hidden/disabled for a logbook entry that already has a linked reflection, to prevent duplicates. All other paragraphs in the transcript were classified C (context), F (feedback — bugs tracked in GH and/or confirmed ✅ in the spec), or CONFIRM against existing ACs. |
| 2026-04-21 | Server-side enforcement of the EOY Reflection Nov 15 – Dec 31 availability window on createEndOfYearReflection; shared isWithinEoyReflectionWindow constant between frontend helper and backend procedure | #5005 (complements #4989) | Previously only the client-side isEOYReflectionAvailable helper gated the window — direct API calls (or the DEV_BYPASS_EOY_DATE localStorage flag, removed in #4989) could create out-of-window reflections. Window now enforced authoritatively server-side. |
| 2026-04-21 | Added 10,000-char .max() cap to reflection free-text fields on activityAttributesSchema | #5000 | Prevent arbitrarily large strings reaching Postgres unguarded (TOAST / storage abuse) |
| Apr 2026 | EOY Reflection empty state added (mobile + desktop) | #5006 | First-time users saw a blank area with no guidance; now shows a friendly empty-state block consistent with other modules |
| Jan 2026 | Multi-person retrospective identified as new requirement | Walk-through notes | Multi-surgeon cases need shared reflection |
| Jan 2026 | Notification deep-links fixed | #3549, #3576 | Clicking notifications opened blank dialogs |
| Jan 2026 | Dashboard CTA redesigned | #3627 | Old button didn't expose key actions |
| Date | Change | PR/Issue | Reason |
| ---------- | --------------------------------------------------------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 2026-04-21 | Added 10,000-char .max() cap to reflection free-text fields on activityAttributesSchema | #5000 | Prevent arbitrarily large strings reaching Postgres unguarded (TOAST / storage abuse) |
| 2026-04-21 | EOY Reflection DEV_BYPASS_EOY_DATE localStorage bypass is now dev-only (gated on import.meta.env.DEV) | #4989 | Security: dev escape hatch was shipping to production — any user could unlock the Nov 15 – Dec 31 window year-round. Blocks #5005 (server-side enforcement). |
| Apr 2026 | EOY Reflection empty state added (mobile + desktop) | #5006 | First-time users saw a blank area with no guidance; now shows a friendly empty-state block consistent with other modules |
| Jan 2026 | Multi-person retrospective identified as new requirement | Walk-through notes | Multi-surgeon cases need shared reflection |
| Jan 2026 | Notification deep-links fixed | #3549, #3576 | Clicking notifications opened blank dialogs |
| Jan 2026 | Dashboard CTA redesigned | #3627 | Old button didn't expose key actions |
| Date | Change | PR/Issue | Reason |
| ---------- | --------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 2026-04-21 | Triage sweep — 6 open issues mapped to this spec | #5051, #5005, #5004, #5003, #5001, #4999 | Unblocks drift detection on the features index. |
| 2026-04-21 | Added 10,000-char .max() cap to reflection free-text fields on activityAttributesSchema | #5000 | Prevent arbitrarily large strings reaching Postgres unguarded (TOAST / storage abuse) |
| 2026-04-21 | EOY Reflection DEV_BYPASS_EOY_DATE localStorage bypass is now dev-only (gated on import.meta.env.DEV) | #4989 | Security: dev escape hatch was shipping to production — any user could unlock the Nov 15 – Dec 31 window year-round. Blocks #5005 (server-side enforcement). |
| Apr 2026 | EOY Reflection empty state added (mobile + desktop) | #5006 | First-time users saw a blank area with no guidance; now shows a friendly empty-state block consistent with other modules |
| Jan 2026 | Multi-person retrospective identified as new requirement | Walk-through notes | Multi-surgeon cases need shared reflection |
| Jan 2026 | Notification deep-links fixed | #3549, #3576 | Clicking notifications opened blank dialogs |
| Jan 2026 | Dashboard CTA redesigned | #3627 | Old button didn't expose key actions |
Sources & Recordings
| Source | Notes |
|---|---|
| https://drive.google.com/file/d/1HDF4acVA0QKImQ29Wu0rp_kVIgb-VGFVg_XwcZnUV6E | Description pending SGD audit |
| https://docs.google.com/document/d/1YhgQSFL9iOlQLoTrQYSwxRNXH4Dg4wefkItcwljQZmo | Description pending SGD audit |