Skip to content
View in Notion

Action Items ​

Feature Overview ​

Action Items is the single place a user goes to see everything that needs their attention: their own outstanding To-dos, Notifications from other users and system events, and Platform Reminders driven by compliance / cadence rules. It replaces the fragmented surfaces previously split across "Actions", Notifications, and inline prompts. This spec supersedes notifications.md.

📌 The Menu's Action Items pill counts only items in the To-do tab. Bell-icon notifications are the Notifications tab. See menu.md.

Open Questions ​

#QuestionSourceOwnerStatus
Q6Platform Reminders: (a) keep them as their own third tab in Action Items, or (b) show them inside the Notifications tab? (Reopens Q1. Engineering decided "own tab" on 5 May and you never ratified it.) Your Notion brief puts Platform Reminders under Notifications. On 26 May you said Action Items would show "all of the notifications … including platform reminders". On 20 Sep you said Action Items is "to do specifically and maybe platform reminders if these are separate". The app has three tabs today, and Platform Reminders is still an empty placeholder (#12330).notion-action-items-brief; transcript-2026-05-26 ~01:15:06; transcript-2026-09-01 ~00:29:59; issue-12234 (2026-09-20T15:10Z)MattOpen. Blocks action-items.core.tab-model and #12330.
Q3Platform Reminders fast follow: what is the time frame? Matt asked on 20 Sep: "What's the time frame on the fast follow?" The scope is decided (7 types now; immunisation renewal, mandatory training expiring and CPD plan not submitted as the fast follow). This is Rob's to answer, not Matt's. The domain groupings are still for Matt to review.issue-12234 (2026-09-20T17:31Z)RobOpen, awaiting Rob. Scope decided by Matt on 2026-09-20 (#12234): "7 with a fast follow". The 7 types with a live processor ship first (#12329/#12330).
Q5Tile copy standard — level of detail expected, who owns the style guide?Matt's brief, "require more detail"MattBuilt engineering-led (#12327), Matt to review the wording. Tiles use [Verb] [Subject] — due [date] (unified-inbox/utils/tileCopy.ts).
Closed Questions (8) — click to expand
#QuestionSourceOwnerStatus
Q1Platform Reminders: separate tab or section within Notifications?Matt's brief, tab structureMattResolved 5 May (engineering-led): separate tab. Avoids ambiguous bell-count contract. Reopened 2026-10-03 as Q6. Matt never ratified it, and his 2026-05-26 and 2026-09-20 statements leave it open.
Q2Triage tool: keep, remove, or replace with deadline surfacing?Matt's brief, to-do'sMattResolved 5 May (engineering-led): remove and replace with a deadline sort. Ratified by Matt on 2026-09-20 (#12234): the admin triage overlay is "drift and overkill. Due dates are worthwhile if they exist for a certain item". Drift fix: #12762.
Q4"Purple box" on current moreton-vs-uat screen — intentional or bug?Matt's brief, screenshots commentaryMattClosed 2026-10-03 (inferred from existing evidence, Rob approved): not a product defect. The purple boxes are the magenta masks the visual-comparison screenshots paint over badge counts (COMMON_MASKS = ['.MuiBadge-badge'] in instances/ppp/e2e/visual/moreton-vs-uat-tour.spec.ts; screenshots from commit f6babf57f, 2026-04-15). They are not in the app. Engineering's proposed answer: treat it as a bug — a hard-coded purple wash on items in some state; replace it with a plain card plus a state chip. That proposal is withdrawn. The "Purple box investigation" AC is retired (struck through, kept visible) and its Status row is removed.
Q7Which to-dos have a real due date? On 20 Sep you said "Due dates are worthwhile if they exist for a certain item". Your Notion brief gave appraisals as the example. Which types should carry a due date, and where does it come from?issue-12234 (2026-09-20T17:31Z); notion-action-items-briefMattClosed 2026-10-03 (inferred from existing evidence, Rob approved). A to-do shows a due date only where its source record already carries a deadline. Nobody sets one by hand. The yearly appraisal is Matt's named example. action-items.todo.deadline-surfacing is reworded to say so. Which source records gain a deadline is decided feature by feature, not here.
Q8Can a user delete a single to-do? Your Task 15 brief lists "?prompt to delete". On 4 Aug you wanted to "delete it if it's an error" from inside a group (#12763). Should every to-do be deletable after a confirm prompt, or only drafts the user created themselves?issue-11217 (brief 2026-07-29); transcript-2026-08-04 ~00:32:57; issue-8653 (2026-06-13)MattClosed 2026-10-03 (inferred from existing evidence, Rob approved). A user can delete their own draft to-dos one at a time, after a confirm prompt (new AC action-items.todo.delete-own-draft-with-confirm, #12763). Requests from other users (e.g. a review someone sent you) are never deletable and clear only when completed. That second part is engineering-led: it rests on Matt's "Forms need to be completed to be done" (#8653), not on a statement about deleting.
Q9For each notification in the admin Notification schedule, should "goes to To-do / Notifications / both" be (a) a fixed rule shown read-only, or (b) a setting an admin can change per item?issue-11217 (brief 2026-07-29); notion-admin-console (2026-08-04)MattClosed 2026-10-05: (b), an admin can change it. Answered by Rob (acting product owner) on 2026-10-04 in his comments on #12548 and #12764 ('editable routing + schedule console, also answers Action Items Q9'), consistent with Matt's Task 15 brief. Matt's Task 15 brief asks for a console "that determines which items go to which of either 'To-do' or notifications" (src:issue-11217), so the setting is editable, not a fixed rule. Built in #12764 and proven live by the @issue-12764 scenarios: routing a trigger to Notifications only takes its item off the reviewer's To-do list.
Q10Do admins get to-dos? On 13 Apr you said a consultant self-electing as timesheet approver "comes [as] an action item in our … PPP super admin". On 14 Jul Rob said "I don't think we should ever have action items for a super admin".transcript-2026-04-13 ~00:40:41; transcript-2026-07-14 ~01:07:05 (Rob); notion-admin-console (2026-08-04)MattAnswered by Matt (Notion ADMIN CONSOLE page, last edited 2026-08-04). Admins get a separate "Task Manager" in the admin console: "One List (ie remove separation of To-do and Notifications)", with platform auto-actions logged into it. Doctors keep the split To-do / Notifications page. This supersedes Rob's 2026-07-14 position. #11779 built that single list on the doctors' page, which Matt called "an aberrant build" on 2026-09-20 (#12234). action-items.home.quick-access-hidden-for-admin stays: admins have no personal doctor-style to-do peek.
Q11"?Remove Tracker for this feature": which tracker did you mean, and should it go?notion-action-items-briefMattClosed 2026-10-03 (inferred from existing evidence, Rob approved). The tracker was the daily "items completed today" progress ring at the top of the To-do list. It was removed on 2026-06-17 by PR #8717 (commit 573a06ece) with the mark-as-done controls it depended on. New AC action-items.todo.no-daily-progress-tracker keeps it out.
Matt's Requirements (from Notion brief) ​

Issue ​

  • It is hard to keep track of everything a user needs to do.

Purpose ​

  • One-stop shop for finding and actioning outstanding tasks.
  • Ease the burden for users and make the platform feel achievable, less onerous.

Tab structure ​

Three tabs inside Action Items (Q1 resolved engineering-led 5 May, never ratified, reopened as Q6 on 2026-10-03. Platform Reminders is its own tab. Engineering dropped the earlier "sub-section within Notifications" reading because it conflicts with the bell-badge-count contract in menu.md and leaves the count source ambiguous. Matt's Notion brief, last edited 2026-05-26, still nests Platform Reminders under Notifications.):

  1. To-do — items that require action by the user.
  2. Notifications — items received from third parties / other users (e.g. a document has been verified, a form has been completed on their behalf).
  3. Platform Reminders — system-generated cadence/compliance prompts (CPD deadlines, registration expiry, immunisation renewal, etc.).

Platform Reminders ​

  • Rob to summarise all current platform reminders on the Notion page for review and a decision on what's missing / what needs improvement (open research task on Matt's brief, tagged @Rob).

Screenshots / UX changes called out by Matt ​

These are regression-grade — each becomes an AC that must be covered by a @regression BDD scenario.

  • Rename "Action" → "Action Items" across the entire platform.
  • Purple box on current screen — is this a bug? Confirm and fix or document. (Closed Q4, 2026-10-03: the purple boxes are the masks the visual-comparison screenshots paint over badge counts, not part of the app.)
  • To-do's:
    • Remove "mark all as done" — the system should determine completion state, not the user.
    • Tiles need more detail about what is required from the user (current tiles are too terse).
    • Consider removing the triage tool. If an item has a deadline, surface the deadline (e.g. for appraisals).
  • Review Notifications tab for what goes in which tab (e.g. is a Platform Reminder a Notification or its own tab? — resolved engineering-led 5 May, see Tab taxonomy below).

Tab taxonomy (engineering-led 5 May, Matt to ratify) ​

Surface eventTab
WBA verification request received from another consultantTo-do
WBA you submitted has been verifiedNotifications
HR Passport doc verified by recruiter / adminNotifications
Appraisal submitted to you for reviewTo-do
Timesheet awaiting submission this fortnightTo-do
Sign-off Dr Smith's MCR (deadline Friday)To-do
CPD activity awaiting your approval (external approver / supervisor)To-do
CPD plan deadline approachingPlatform Reminders
Medical registration expiring within 90 daysPlatform Reminders
Immunisation renewal duePlatform Reminders
Mandatory training expiringPlatform Reminders
Geo-fence exit → "Complete your timesheet"Platform Reminders
Generic system event you did not request (e.g. "Your CPD plan was approved" — informational)Notifications

Rule of thumb: To-do = user must act. Notifications = a thing happened, no action needed. Platform Reminders = system-generated cadence/compliance nudge.

On 2026-09-01 Matt asked for "a metric" that delineates an action item from a notification. That rule is owned by notifications.md (notifications.delineation.notification-vs-todo, Q4 there, formerly OQ-N3) and was settled on 2026-10-03: a to-do is something this user must act on, a notification tells the user something happened or a third party completed something, and one event can raise both. The rows above follow that rule. The Platform Reminders rows still depend on Q6.


Acceptance Criteria ​

Core — tab model ​

  • ✅ action-items.core.tab-model — the Action Items screen exposes three tabs, To-do, Notifications and Platform Reminders. ?tab=notifications and ?tab=platform-reminders select a tab. Built (#12342, #12329, #12330): the tab shell ships and Platform Reminders lists the caller's reminders under domain headers, with the count beside the tab label. Rob decided on 2026-10-04 that it stays a separate third tab (Q6). Matt confirmed the Notifications part on 2026-09-01: the bell's "view all" goes "to the notifications part of the action items". CONTRADICT, superseded wording kept visible: #11779 (2026-08-24) merged To-do and Notifications into one "Task Manager" list → Matt, 2026-09-20: "the 'task manager' was an aberrant build … action items wins". The tabs were restored by #12342.††† (#11217)
  • ⏳ Tab counts render next to each tab label when non-zero. (Not built: the tab labels carry no count today. No Matt statement asks for per-tab counts. His 2026-05-26 ask was the menu pill below.)
  • ✅ action-items.core.menu-pill-todo-only — the Menu's Action Items pill count comes from the To-do tab only, not Notifications or Platform Reminders. Built by #12328 (useSidebarMenuClusters reads todoList.getPrioritised.totalCount). The bell count can differ from it, which was decided on the 2026-06-03 call (#8101).†† (#11217)

To-do tab ​

  • ⏳ Regression — no "mark all as done" button present. Item completion is system-determined (e.g. the action was taken elsewhere, the deadline passed, the referenced record was verified).
  • ⏳ Each To-do tile shows: (a) what action is required, (b) the trigger/context (which record or event), (c) the deadline if one exists.
  • ✅ action-items.todo.priority-and-age — each To-do tile shows its level of importance (a priority chip whose tooltip explains the level, #8653) and how long ago it was created ("Today" / "Nd ago"). These are the "level of importance" and "time since creation" in Matt's Task 15 brief. CONFIRM: TodoItemCard renders both.† (#11217)
  • ✅ action-items.todo.no-triage-overlay — built (#12762). To-do cards carry no triage tool: no hand-set status, due date, assignee or tags, for any role. CONTRADICT, superseded wording kept visible: #11779 (2026-08-24) added an admin-settable status / due date / assignee / tags bar (TaskMetadataBar) plus 7-day/1-day due-date reminders → Matt, 2026-09-20: "I think this is drift and overkill". Fixed: TodoItemCard.tsx no longer mounts the editor for any role and the TaskMetadataBar component is deleted. The taskManager router, its tables and the unscheduled processTaskManagerReminders job are left dormant: removing them needs a migration (decision recorded in the Change Log).††‡ (#11217, #12762)
  • ⚠️ action-items.todo.deadline-surfacing — a to-do shows a due date only where the source record carries a deadline (the yearly appraisal is Matt's named example). Where it does, the tile shows it and the list sorts deadline-ascending, with items that have no deadline at the bottom. A due date is never set by hand (see the AC above). Partly built (#12327, #12965): the sort and the "— due [date]" tile copy exist, and an MCR now carries the end of its collaboration window (collaborationWindowExpiresAt) as its deadline, so an MCR tile shows "— due [date]". Every other work-queue source still returns deadline: null (NO_DEADLINE in workQueueService/index.ts); appraisal cadence dates (calculateAppraisalDueDates) are the next candidate. Which types carry one is Q7. Q7 closed 2026-10-03: this spec does not require any to-do type to gain a deadline. Each source record's own feature spec decides whether it has one.†† (#11217)
  • ✅ action-items.todo.group-individual-oversight — Similar draft to-dos still collapse into one grouped row so a large import doesn't flood the list. The group can also be opened as a drop-down under its topic that lists each item. From there the user can action any single item directly or, for their own draft created in error, delete it, as well as step through them all. Grouping and Open apply to every grouped type (logbook drafts, WBA drafts, timesheets and so on), not just logbook; Delete is offered only on the viewer's own activity-backed drafts (WBA, feedback, reflection, audit event, logbook case), never on timesheet or 360 groups or on other people's requests. CONTRADICT, superseded wording kept visible: 2026-06-03: one grouped row that opens a stepped flow through each item, with skip → Matt, 2026-08-04: "There's no oversight to be able to … select exactly the one that you want". Built (#12763, with the logbook instance #12724): GroupedTodoItemCard has a "Show N items" toggle ("cases" for logbook) listing each member by its own label — operation text and case date for a logbook draft, otherwise the draft's own title (if any) and its record date. Each row has Open (that one item, outside the stepped flow) and, for the viewer's own draft, Delete after a confirm. Clicking the row still starts the stepped flow.††‡ (#11217, #12724, #12763)
  • ✅ action-items.todo.delete-own-draft-with-confirm — a user can delete one of their own draft to-dos at a time, from the list or from inside a group, after a confirm prompt. Nothing is deleted without that confirm. Requests from other users (a review, a sign-off or a form someone sent you) are never deletable and clear only when completed. That second part is engineering-led: it rests on Matt's "Forms need to be completed to be done" (#8653), not on a statement about deleting. Built (#12763, #12824): inside a group, the viewer's own activity-backed drafts (WBA, feedback, reflection, audit event, logbook case) offer Delete behind the shared confirm dialog. Other people's requests and timesheets / 360s offer none (isOwnDeletableDraft), and activities.delete refuses a non-owner server-side. A single, ungrouped To-do row offers the same Delete behind the same confirm (#12824).††† (#11217, #12763)
  • ✅ action-items.todo.no-daily-progress-tracker — the To-do list has no daily progress tracker (the "items completed today" progress ring). Matt's brief asked to "?Remove Tracker for this feature". PR #8717 removed it on 2026-06-17, together with the mark-as-done controls it depended on (Q11).†‡ (#8653)

To-do row actions — touch-safe (#8590) ​

  • ⏳ action-items.todo.card-tap-opens — Tapping or clicking a To-do row always opens the item to action it; it never snoozes or completes the item. †
  • ⏳ action-items.todo.row-actions-touch-visible — On touch devices (no hover) the Snooze action renders as a real, visible button of at least 44×44 CSS px, placed outside the row's open-the-item tap target so it cannot be triggered by an open tap. †
  • ⏳ action-items.todo.row-actions-hover-reveal — On hover-capable devices the Snooze action stays hover-revealed (hidden until the row is hovered) and never sits inside the row's tap target. †
  • ⏳ action-items.todo.action-undo — Snoozing a To-do item raises a snackbar with an Undo action; choosing Undo immediately restores the item (un-snoozes it) so nothing silently disappears. †

Home-screen quick-access affordance ​

  • ✅ action-items.header.logo-control — the circle of the PPP logo in the top bar is the Action Items control. It carries a red marker when there are outstanding to-dos. Tapping it opens a drop-down headed "Action Items": tapping the heading opens the Action Items page, and tapping an item opens that item. Notifications stay separate in the bell. Built on handheld web and the native shell (#12141): the dashboard peek is hidden on mobile so there is one Action Items badge. Rob committed on 2026-09-20 to mock it up for Matt; the UAT build serves as the mock-up. This is the newest placement for the quick-access peek below. The 2026-07-14 home-screen drop-down shipped first, and whether it stays once this ships is part of #12141.††† (#11217, #12141)
  • ✅ action-items.home.quick-access-affordance — The home screen surfaces a notifications-style quick-access affordance (an anchored dropdown/popup, patterned on the notifications bell) that lists the user's most recent outstanding action items, so the item they just created (e.g. a just-scanned logbook draft) is one tap away without navigating to the full Action Items list. †
  • ✅ action-items.home.quick-access-recency — The affordance orders items most-recent-first and shows a capped peek (not the full list); the item most recently created appears at the top. †
  • ✅ action-items.home.quick-access-tap-opens — Tapping a listed item takes the user directly to that item's review surface (deep-link) where one exists; item types that open in a dialog fall back to the Action Items To-Do list. A footer link opens the full Action Items list. †
  • ✅ action-items.home.quick-access-hidden-for-admin — The affordance is hidden for admin personas, who have no personal to-do list on the dashboard (placeholder view). Admins do get tasks, but in a separate single-list "Task Manager" in the admin console, not on this doctor-facing page (Q10, answered by Matt's ADMIN CONSOLE page, 2026-08-04). Whether admins should have to-dos at all is Q10.† †

Notifications tab ​

  • ⏳ Notifications include: third-party events (document verified, form completed by another user), system events (CPD point awarded, WBA completed). What counts as a notification and what counts as a to-do is owned by notifications.delineation.notification-vs-todo (Q4 in notifications.md, formerly OQ-N3, settled 2026-10-03).
  • ✅ action-items.notifications.bell-unseen-vs-unread — the bell badge counts unseen notifications and the Notifications tab's Unread (N) counts unread ones, so the two can show different numbers by design. Opening the bell clears the red badge (seen); a row keeps its blue bar until it is clicked (read). Matt's #8942 statement (2026-06-20) — "click on the bell should take away red pill and click on notification should take away left justified vertical blue bar" — is newer than the 17 Apr brief line "badge count equals Notifications tab count" and supersedes it (#12563, option B). Behaviour owned by notifications.md (#8978). † ‡
  • ✅ action-items.notifications.bell-view-all — the bell opens a drop-down of the latest five notifications over the current screen (owned by notifications.bell.heads-up-dropdown). Its "View all notifications" link lands on the Notifications tab of Action Items (/action-items?tab=notifications, wired by #12342), which keeps the full history. CONTRADICT, superseded wording kept visible: "Clicking the bell deep-links to the Notifications tab". Since 2026-05-26 Matt wants the bell to be a drop-down that doesn't navigate away, and only "view all" goes to the tab.†† (#11217)

Platform Reminders tab / section ​

  • ⏳ Platform Reminders are system-generated cadence / compliance prompts, distinct from event-driven Notifications. A reminder fires on a schedule or a threshold crossing (a date approaching, a cadence elapsing, a target not met) — never as a direct reaction to another user's action.
  • ⏳ Platform Reminders are grouped by domain in the tab so related reminders sit together; the inventory below is the canonical grouping. (Q3 — Rob's research task; supersedes the flat, mis-grouped tables that previously lived in notifications.md.) Matt raised the grouping himself on 2026-05-26: wellness questionnaire, profile completion and CPD plan not submitted "don't seem to be related".†
  • ⏳ action-items.reminders.v1-seven-then-fast-follow — the Platform Reminders tab launches with the 7 reminder types that already have a live scheduled processor (see the backend sourcing note below). Immunisation renewal due, mandatory training expiring and CPD plan not submitted follow as a fast follow, not a blocker. This is Matt's call on 2026-09-20, and it ratifies Rob's #12331 proposal. The tab is built (#12329, #12330). The CPD plan not submitted reminder and the MCR / MSF / 360 cadence reminder (appraisal_reminder) are now catalogued as Platform Reminders (#12966); immunisation and mandatory training expiry still arrive through the generic passport sweeps. The tab-vs-section question is Q6.† (#11217, #12330)
  • ✅ action-items.admin.routing-console — a super-admin view shows which events land in To-do and which land in Notifications, and lets an admin change it (#12764). Built 2026-10-05 as the "lands in" control on /settings/notification-triggers; the work queue and To-do sources read it, so routing a trigger to Notifications only takes its item off the To-do list (@issue-12764, live-proven red then green). Location settled 2026-10-03: it is a "lands in: To-do / Notifications / both" column on the admin Notification schedule table (notifications.admin.trigger-catalogue, #12760), not a separate screen. Editable per item (Q9, closed 2026-10-05). The to-do vs notification rule it applies is settled (notifications.md Q4). Its shape is Q9. It depends on the to-do vs notification rule (notifications.md OQ-N3) and sits naturally next to the notification-trigger list (#12760).†† (#11217, #12764)

Platform Reminders inventory (scheduled reminders) ​

Each row is a scheduled / threshold reminder. Grouped by domain so related reminders stay together (the prior notifications.md tables interleaved unrelated categories — e.g. weekly wellness questionnaire, CPD-plan-not-submitted, and profile completion were lumped into one ungrouped list).

GroupReminderFires whenCadence / triggerOpt-out?
Compliance / expiryMedical registration expiringRegistration within 90 days of expiryDaily check, thresholdNo (compliance)
Compliance / expiryImmunisation renewal dueImmunisation record within renewal windowDaily check, thresholdNo (compliance)
Compliance / expiryMandatory training expiringTraining certificate approaching expiryDaily check, thresholdNo (compliance)
CPD cadenceCPD plan deadline approachingSubmission deadline within reminder windowDaily check, thresholdYes
CPD cadenceCPD plan not submittedPlan overdue past its deadlinePersistent until actionedYes
CPD cadenceCPD hours deficitUser behind their target hours for the periodPeriodic re-evaluationYes
Timesheet / attendanceTimesheet awaiting submissionFortnightly submission window openFortnightly cadenceYes
Timesheet / attendanceGeo-fence exit → complete timesheetUser exits a hospital geo-fence with an open shiftEvent-evaluated, scheduled follow-upYes
WellnessWellness questionnaire dueWeekly questionnaire cadence elapsedWeekly cadenceYes
ProfileProfile completion nudgeRequired profile field (CV, immunisations, supervisor) missingPeriodic until resolvedYes

The opt-out column matches the channel/opt-out matrix in notifications.md Q1. Compliance reminders are mandatory; cadence nudges are opt-out per category.

Platform Reminders backend sourcing (Rob, 2026-09-20 — grounds #12329/#12331's scope decision) ​

Confirmed by reading the actual backend code (not assumed) before deciding what's in v1 vs. deferred. Every row in the inventory table above maps to one of three states:

Already produced by an existing scheduled processor — v1, no new work:

  • Medical registration expiring (90 days) / CPD plan deadline approaching / CPD hours deficit / Timesheet awaiting submission / Geo-fence exit / Wellness questionnaire due / Profile completion nudge — each has a live process*Notifications.ts file under api/backend-ppp/src/services/notifications/scheduledNotificationService/, wired into the scheduler and already writing to notifications. The Platform Reminders epic's aggregation router reads these as-is.

Domain logic exists, scheduled processor does not — v1.1 follow-up, not "no backend source":

  • Immunisation renewal due — passportImmunisationService/cadence.ts's deriveCadenceStatus() already computes a pure, tested 'due'/'expired'/'current' status per immunisation record (annual-cadence-aware, #8244). No processImmunisationRenewalNotifications.ts consumes it on a schedule yet — this is a wiring gap, not a missing domain model.
  • Mandatory training expiring — pppPassportTraining (schema) already carries a per-record status ('expired' is a defined enum value) and an expiry-date field populated once a provider verifies a certificate (mandatoryTrainingSeed.ts's populateForUser). Same shape as the immunisation gap: the data exists, no scheduled scan-and-notify processor reads it.

Named in the spec as a distinct signal, but only a different-shaped mechanism exists today — needs its own design, not just a wiring job:

  • "CPD plan not submitted" as distinct from "CPD plan deadline approaching" — cpdReminderSchedules.ts defines CPD_PLAN_REMINDER_TICK (annual) and CPD_SUBMISSION_PROMPT_TICK (weekly) cron timings, migrated from dormant Azure Container Apps Jobs (#11836) — but no processor file consumes either tick; both are orphaned schedule constants, not a working reminder. Building this needs the same process*Notifications.ts treatment as the immunisation/training gap above, so it's grouped with them for v1.1 scheduling purposes even though the spec lists it under CPD cadence, not Compliance/expiry.
  • The registration-recheck mechanism that DOES exist (processRegistrationReCheckNotifications.ts) is a once-a-year live AHPRA/GMC lookup confirming registration is still active — a different signal from "registration expiring within 90 days" (a date-threshold check against the stored expiry, same shape as the passport-document expiry check). These are not duplicates of each other; both are legitimate, and the 90-day one is already covered by the generic passport-expiry processor above.

Decision (Rob, 2026-09-20, resolves #12331): ship the Platform Reminders tab in v1 with all 7 "already produced" types live. Immunisation renewal, mandatory training expiring, and CPD plan not submitted ship as a v1.1 follow-up epic (3 new process*Notifications.ts files following the existing pattern — each is a schedule-plus-query job, not new domain modelling, since deriveCadenceStatus/pppPassportTraining.status/the CPD tick constants already do the hard part). Do not block v1 on this follow-up.

Event-driven vs scheduled — what does NOT belong here ​

These are event-driven and route to To-do or Notifications, never Platform Reminders (see the Tab taxonomy table above):

  • ⏳ A request that requires the user to act (WBA verification request, appraisal sent for review, CPD activity awaiting your approval) → To-do, triggered by another user's/event's action.
  • ⏳ An informational "a thing happened" event you did not schedule (document verified, WBA you submitted verified, "your CPD plan was approved") → Notifications.
  • ⏳ Rule: if the surface event is a reaction to another party's action it is event-driven (To-do / Notifications); if it is the system watching a clock or a threshold on the user's own record it is a Platform Reminder.

Labels / branding ​

  • ⏳ Regression — every screen, notification, email, and menu entry referring to this feature uses the term "Action Items" (not "Action", "Actions", "Inbox" or "Task Manager"). CONTRADICT, superseded wording kept visible: "Task Manager" (#11779, 2026-08-24) → Matt, 2026-09-20: "action items wins". The page title and web menu were renamed back by #12342. The native More menu is still pending (#12688).†† (#11217)
  • ⏳ action-items.label.native-menu-renamed — The native mobile app's More-menu entry for this surface reads "Action Items" (not "Action"/"Actions"), matching the web page header. Tracked by #8651 until a new native build ships (re-statused from built: a source rename is not the shipped device behaviour). Built in source (mobile/ppp/lib/config/menu-items.ts, asserted by menu-items.test.ts and MoreSheet.test.tsx); only a native build check on a device remains. †
  • ⏳ "Purple box" investigation on the current moreton-vs-uat screen — either confirmed as a bug and fixed, or explicitly documented as intentional. Track as a separate issue with the bug label if confirmed. Retired 2026-10-03 (Q4 closed): the purple boxes are the magenta masks moreton-vs-uat-tour.spec.ts paints over badge counts (COMMON_MASKS = ['.MuiBadge-badge']) in the comparison screenshots, not something the app renders. No bug to file.

Tile detail ​

  • ⏳ Regression — To-do tiles state the required action in plain language (e.g. "Sign off Dr Smith's MCR — due Friday" rather than "MCR pending"). Engineering + Matt to agree tile-copy standard.
  • ✅ Regression — a To-do tile for the viewer's own item (e.g. their own draft WBA) addresses them — "Complete your WBA (PBA)" — rather than naming them in the third person ("Complete Tom Walsh's WBA (PBA)"); the "{name}'s" form is kept for items about someone else's work (#12709, found live in the Task 4 audit #11183).
Downstream References ​
FeatureLinkage
MenuAction Items pill count = To-do tab count; bell badge = Notifications tab count
CPDCPD reminders and verification events flow into Platform Reminders and Notifications
HR PassportExpiry reminders (registration, indemnity, immunisations, mandatory training) flow into Platform Reminders
Attendance"You have entered / exited hospital" events — current brief marks these as toasts, NOT bell-triggered
TimesheetFortnightly submission prompt — Platform Reminder
Appraisal / WBA / RetrospectiveVerification-complete events flow to Notifications
Status ​

As of 2026-10-03 (Task 15 refresh): the three-tab Action Items page is live (#12342), with Platform Reminders still a placeholder. "Mark all as done" is gone (#8653). Tiles use the [Verb] [Subject] — due [date] copy (#12327). The admin triage overlay drifts from Matt's newest statements (#12762). Grouped cards now expand to open or delete one item (#12763).

Sub-featureStatusNotes
Three-tab Action Items screen🚧 PartialShell built (#12342); Platform Reminders tab built (#12329/#12330). Q6 answered: own tab
Menu pill = To-do count✅ Built#12328
"Mark all as done" removal✅ Built#8653
Triage tool removal⚠️ DriftAdmin TaskMetadataBar still mounted. Matt 2026-09-20 "drift and overkill" → #12762
Deadline surfacing🚧 PartialSort + copy built (#12327). Shown only where the source record has a deadline; none do yet
Grouped to-dos: pick/delete one✅ BuiltExpand / Open / Delete own draft for every draft type (#12763, #12724)
Delete own draft (confirm prompt)🚧 PartialInside a group (#12763); a single ungrouped row has no Delete yet (#12824)
No daily progress tracker✅ BuiltRemoved by PR #8717 (Q11 closed)
Priority + age on tiles✅ BuiltTask 15 brief CONFIRM
Tile detail rewrite✅ Built#12327. Matt to review the wording (Q5)
Rename → "Action Items"🚧 PartialWeb done (#12342, @issue-7389). Native More menu awaits a native build (#8651, #12688)
Home quick-access peek✅ Built#10642
Logo / top-bar Action Items control📋 Specified#12141, mock-up first
Platform Reminders inventory📋 SpecifiedMatt 2026-09-20: 7 + fast follow (#12329/#12330)
Admin routing console✅ Built#12764. Editable "lands in" column on the Notification Triggers console; read by the work queue and To-do sources

Open issues on label:feature:action-items (8)

#Title
#12234feat(action-items): build the three-tab Action Items screen (To-do / Notifications / Platform Reminders)
#12329epic(action-items): Platform Reminders backend aggregation
#12330feat(action-items): final PR — Platform Reminders tab UI
#12688feat(action-items): The native mobile app's More-menu entry for this surface rea…
#12861feat(action-items): Tapping or clicking a To-do row always opens the item to act…
#12862feat(action-items): On touch devices (no hover) the Snooze action renders as a r…
#12863feat(action-items): On hover-capable devices the Snooze action stays hover-revea…
#12864feat(action-items): Snoozing a To-do item raises a snackbar with an Undo action;…

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

Change Log ​
DateChangePR/IssueReason
2026-10-06action-items.label.native-menu-renamed re-statused from built to not built: the rename exists in source, but it only reaches devices with a new native build, tracked by #8651.#8651The AC traceability gate found the built AC had no scenario proving it; the honest status is not built until the native build ships (matches the sibling mobile.nav.action-items-menu-label).
2026-10-05The sidebar Action Items To-do pill and the CPD Home dot now render (the menu item renderer ignored label.ParentNode, so neither ever showed). The priority chip explains its level in an MUI tooltip instead of a native title. The Platform Reminders tab label no longer clips at 375px, and a CPD deadline reminder shows its real deadline date rather than the day it was raised.#11217, #11218Task 15 recording audit of 5 Oct 2026 (B1, B10, B11, B13). @issue-11217 live scenarios for the pill and the tooltip were red on the pre-fix renderer (badge element not found; no tooltip role) and green after.
2026-10-05action-items.admin.routing-console is now built and live-proven. The Notification Triggers console''s "lands in" setting is editable and read by the work queue and the To-do sources: routing a trigger to Notifications only takes its item off the reviewer''s To-do list, and a trigger switched off or routed to To-do only raises no Notifications row. Q9 (fixed rule or editable) is closed as editable, inferred from the Task 15 brief wording "console that determines which items go to which".#12764, #11217The @issue-12764 and @issue-12548 live scenarios were run on an isolated stack, red against the pre-change gates (To-do row still present; notification count 3 to 4) and green with them. Matt to correct the Q9 inference if he meant a read-only view.
2026-10-05An MCR To-do tile now shows the collaboration window end as its due date (the only source with a stored deadline); the native More-menu label and the dead /work-queue and /verification Task Manager route titles are reconciled; the Platform Reminders fast-follow text is corrected.#12965, #12966, #11217Task 15 reachability check (5 Oct 2026) R15-15, R15-28, R15-32, R15-33, R15-36; covered by @issue-12965 in action-items.feature. Wave 2 lane; Matt closes #11217.
2026-10-04action-items.header.logo-control flipped to built: on handheld web and the native shell the PPP logo circle is the top-bar Action Items control, a button named Action Items with a To-do-only red marker and the quick-access drop-down (heading opens /action-items). The wordmark grows from 18px to 24px and also shows on handheld web. The dashboard peek is hidden on mobile.#12141Matt 2026-09-20 (#12234): 'what would be neat would be if it was the logo'; Rob 2026-09-20 agreed. Admin personas keep it hidden.
2026-10-04action-items.core.tab-model flipped to built: notifications.platformReminders.list (read-only, over the notifications table, type-to-domain map in packages-shared/ppp/src/constants/platformReminders.ts) feeds the Platform Reminders tab, grouped under Compliance / expiry, CPD cadence, Timesheet / attendance, Wellness and Profile with the count beside the tab label. Reminder types are excluded from the Notifications feed, bell counts and the feed's Mark all as read, so a reminder lives in one tab. Compliance reminders show as Required.#12329, #12330, #12234Rob 2026-10-04 on #12234: Platform Reminders is the third tab, on UAT by 11 Oct. Wellness reminders now live in this tab rather than the bell, which diverges from the wellness prompts-as-notifications AC; flagged for Matt.
2026-10-04action-items.notifications.bell-unseen-vs-unread now cites #12563 and is proven by a real-backend @regression scenario (opening the bell takes the bell count to 0 while the Unread tab count is unchanged).#12563The AC was marked built but the only scenarios near it (#8978) have no-op step definitions, so nothing proved the rule Rob ratified (option B).
2026-10-04Replaced the open AC "Bell-icon badge count equals Notifications tab count" with action-items.notifications.bell-unseen-vs-unread: the bell counts unseen items and the Unread tab counts unread items, so they may differ. No code change; the shipped behaviour (#8978) already matches.#12563, #8942, #8978Matt's #8942 comment of 2026-06-20 (bell click removes the red pill; clicking a notification removes the blue bar) is newer than the 17 Apr brief line the old AC came from, so option B in #12563 wins.
2026-10-04action-items.todo.no-triage-overlay flipped from drift to built: the admin status / due date / assignee / tags editor (TaskMetadataBar) is no longer mounted on To-do cards for any role, and the component is deleted. Decision on the back end: the taskManager router, the task_manager_metadata / task_manager_reminders_sent tables and processTaskManagerReminders are left dormant for now. Deleting the tables needs a migration, so that is a separate change if wanted.#12762, #11217Matt, 2026-09-20 (#12234): "I think this is drift and overkill. Due dates are worthwhile it they exist for a certain item". A due date shows only when the record carries one (action-items.todo.deadline-surfacing).
2026-10-04action-items.todo.group-individual-oversight flipped from drift to built: a grouped To-do row of any draft type expands ("Show N items") to list each member by its own title / record date, with per-item Open and, for the viewer''s own activity-backed drafts, Delete behind the shared confirm dialog. action-items.todo.delete-own-draft-with-confirm moves to partial: deleting from a single ungrouped row is split out to #12824.#12763, #12724, #11217Matt, 2026-08-04 catch-up (~00:32:57): "There''s no oversight to be able to … select exactly the one that you want … grouped in a drop down … action it or delete it if it''s an error". Grouping covers every draft type, so #12763 generalises the logbook-only #12724 delete. Other people''s requests stay non-deletable (Q8, engineering-led on #8653). Supersedes the closed cloud PR #12812.
2026-10-04action-items.todo.delete-own-draft-with-confirm flipped from partial to built: a single (ungrouped) To-do row for the viewer's own activity-backed draft now offers Delete behind the same confirm prompt as a grouped row. Other people's requests, timesheets and 360s still offer none.#12824, #12763, #11217Matt, 2026-08-04 catch-up (~00:32:57): "delete it if it''s an error". Closes the remainder split out of #12763.
2026-10-04action-items.todo.group-individual-oversight wording qualified: Open applies to every grouped type, Delete only to the viewer's own activity-backed drafts (not timesheet or 360 groups, not other people's requests). Built: each expanded row's Open and Delete buttons carry a title naming the row, and a To-do tile no longer flashes the third-person headline before the viewer loads.#12828, #12763#12828 review follow-up: the AC implied Delete applied to every grouped type, which isOwnDeletableDraft does not allow; and every row shared one button name.
2026-10-04To-do rows, tiles, groups and the dashboard Recent Action Items menu label an MSF (persisted as WBA subtype qmf) as MSF (Appraisal) instead of WBA (QMF), through one shared formatTodoTypeLabel helper replacing four copies of the label logic.#0, #12836#12836 Rob decision 4 Oct 2026: MSF is an Appraisal, not a WBA. This is the Action Items display slice only; the persistence remodel (new record type, migration and backfill, all other surfaces) is not built and the issue stays open.
2026-10-04The reviewer a reflection was submitted to can now open it from their "Sign off <name>''s Reflection" To-do. activities.getById now allows the reflection''s assigned reviewer (assessorId) to read it once it is no longer a draft, as it already did for a shared WBA. Before this, the To-do opened a "Reflection Details" modal reading only "Record not found". Other activity types stay owner-only for their assessor, and an unsubmitted draft reflection stays owner-only.#12837, #11209Rob's UAT report #12837: the reviewing consultant could not complete the Reflection sign-off item at all. Same defect class as the WBA read fixed in #12543.
2026-10-03To-do tile headlines now address the viewer for their own items ("Complete your WBA (PBA)") instead of naming them in the third person; buildTileHeadline takes the viewer id and TodoItemCard passes the signed-in user.#12709, #11183Bug #12709, found live on UAT (2026-10-02) during the Task 4 audit: Tom Walsh''s own To-do read "Complete Tom Walsh''s WBA (PBA)". The tile originator is always the submitter, whoever views it. Applies the [Verb] [Subject] tile-copy proposal (Q5) unchanged for items about someone else.
2026-10-03Phase C open questions resolved from existing evidence (Rob approved 2026-10-03). Closed Q4 (the "purple box" was the magenta badge masks in the visual-comparison screenshots; the engineering "hard-coded purple wash" proposal and the Purple box Status row are removed, and the investigation AC is retired, struck through), Q7 (action-items.todo.deadline-surfacing reworded to "only where the source record carries a deadline"), Q8 (new ⏳ AC action-items.todo.delete-own-draft-with-confirm, tied to #12763; the "requests from others clear only on completion" part is marked engineering-led), Q10 (admins get a separate single-list Task Manager in the admin console, per Matt's Notion page of 2026-08-04; Rob's 2026-07-14 position is superseded) and Q11 (the tracker was the daily progress ring removed by PR #8717; new ✅ AC action-items.todo.no-daily-progress-tracker). Narrowed Q9 to editability only, since the location is settled as a column on the admin Notification schedule (action-items.admin.routing-console updated). Q6 kept open with a two-option draft. Q3 kept open with Rob as owner (fast-follow time frame).#11217, #12763, #12764Research on 2026-10-03 against #12234, #11217, #8653, Matt's Action Items and ADMIN CONSOLE Notion pages, the 2026-08-04 transcript, moreton-vs-uat-tour.spec.ts and commit 573a06ece. New source fragments notion-admin-console and issue-8653. Spec-only; no BDD scenarios added, per the spec-refresh rule. The @regression requirement for the delete AC sits with #12763.
2026-10-03The Action Items spec was refreshed for Async Task 15 (#11217). Two ACs are marked drift and filed as bugs. action-items.todo.no-triage-overlay (#12762) is drift because the admin TaskMetadataBar is still mounted, and Matt called it "drift and overkill" on 2026-09-20. action-items.todo.group-individual-oversight (#12763) is drift because grouped to-dos of any draft type can't be expanded, picked or deleted (Matt, 2026-08-04; the logbook instance is #12724). Four new not-built or partial ACs: action-items.header.logo-control (#12141), action-items.reminders.v1-seven-then-fast-follow (Matt's 2026-09-20 call), action-items.admin.routing-console (#12764, from the Task 15 brief) and action-items.todo.deadline-surfacing (sort built, no source carries a deadline). Five ACs CONFIRMed against the code: action-items.core.menu-pill-todo-only, action-items.todo.priority-and-age, action-items.notifications.bell-view-all, and the four action-items.home.quick-access-* ACs (#10642), now ✅. action-items.core.tab-model is now ⚠️ partial. The "Task Manager" naming and single-list model from #11779 are recorded as superseded. The bell AC "Clicking the bell deep-links to the Notifications tab" is superseded by the bell drop-down plus a "view all" link to that tab. New Open questions Q6 to Q11. Q1 (Platform Reminders tab vs section) is reopened as Q6. Q2 (triage) is ratified by Matt. The Status table is rebuilt. status: is now partial-drift, and notion-last-synced: is 2026-10-03.#11217, #12762, #12763, #12764Async Task spec refresh, Task 15 (#11217). The newest dated statement from Matt wins. Drift was confirmed by read-only code checks against real call sites (TodoItemCard.tsx, groupTodoItems.ts/GroupedTodoItemCard.tsx, workQueueService/index.ts). No BDD scenarios were added, per the spec-refresh rule (Rob, 2026-10-03). The @regression requirement sits on #12762 and #12763.
2026-09-28The Notifications tab's 'Unread (n)' / 'All (n)' filter counts now show true server totals instead of the number of rows loaded so far (the feed pages 20 at a time).#12566, #12545Bug #12545 from the 28 Sep walkthrough — the counts capped at 20 while the bell showed 67+. Relevant to this spec's 'Tab counts render next to each tab label when non-zero' and 'Bell-icon badge count equals Notifications tab count' ACs, both still ⏳. Open Question (not resolved by this fix): the second AC assumes one notion of 'unread', but the code has two — the bell badge counts notifications never seen (seenAt IS NULL, cleared by opening the bell, #8978) and the Unread filter counts notifications not read (isRead = false, changed only per row). After this fix each label is correct for its own predicate, but the two numbers are equal only by coincidence. Whether the bell badge and the Unread filter should share one definition is a product decision; implementation detail is in the notifications spec's Change Log.
2026-09-20Restored the three-tab shell (To-do / Notifications / Platform Reminders) this spec's "Core — tab model" AC calls for, following the TimesheetTabsView/Reviews360TabsSection precedent. Renamed the page back from "Task Manager" to "Action Items" (Matt's #12234 confirmation, 2026-09-20), superseding #11779's rename. Wired the existing ?tab= query param (previously a no-op) to select a tab, so the notification bell's "View all notifications" link now actually lands on the Notifications tab instead of the top of a merged scroll. Platform Reminders ships as a stub in this PR — real content is a separate epic (#12329/#12330). Extracted NotificationItem out of NotificationFeed.tsx into its own file.#12342, #12326, #11779, #11217, #12234Resolves the governance divergence #11779 itself flagged (that PR's own Change Log fragment recorded diverging from this spec's three-tab AC and "Task Manager" naming as a deliberate-but-unreconciled scope decision). #12217/#12234 established the naming should revert to "Action Items". This PR is PR1 of the reconciliation — the scaffold only; #11217 (grouped to-do card title distinctness) is unaffected and re-verified under the new tab structure rather than re-litigated.
2026-09-20Threaded a deadline field through the To-do tab's WorkInProgressItem/PrioritisedTodoItem pipeline and made sortByPriority sort deadline-ascending (no-deadline items drop to the bottom) ahead of the existing priority tiering. Standardized each To-do tile's headline to "[Verb] [Subject] — due [date]" (new tileCopy.ts), replacing the bare originator-name + type-chip line. Retired the stale #8629 "mark as done Undo" BDD scenario, which clicked a "Mark as done" button removed by #8653 — the scenario described UI that no longer exists.#12327Spec ACs "Current triage tool is removed and replaced by deadline surfacing — items default-sort by deadline ascending; items without a deadline drop to the bottom" (Q2) and tile-copy standard "[Verb] [Subject] — [deadline]" (Q5) were still ⏳. Audited all 9 WorkInProgressItem source types (wba/feedback/reflection/auditEvent/logbookCase/timesheet/ppp360/timesheetBatch/360_supervisor_review) against their Drizzle schemas before implementing — none stores a real due-date today, so deadline is threaded through as null everywhere rather than a fabricated value; the sort is a correctly-scoped no-op against current data and activates once a source type starts populating a real deadline in a future PR. Does not touch TaskMetadataBar.tsx's admin-only triage-state overlay (status/due-date/assignee/tags) — whether that is the "triage tool" the spec means, or an acceptable survivor, is still awaiting Matt's answer on #12234.
2026-09-20Fixed TodoItemCard mounting the admin-only Task Manager metadata bar (TaskMetadataBar) for every viewer regardless of role. The underlying taskManager.getMetadata/upsertMetadata procedures are adminProcedure-only (#11779 security review — task_manager_metadata has no owner/hospital column to scope by user), so a non-admin viewer's request always 403'd. Now gated behind useIsAdmin().#12339Found while auditing recoverable local git state (an uncommitted stash with the fix already written but never opened as a PR) — verified independently against current uat that the gap was real and still present. No spec change: this restores #11779's own already-stated admin-only constraint; the code just hadn't caught up to it for this one call site.
2026-08-24Renamed "Action Items" to "Task Manager" (page title + sidebar nav label; the /action-items route path is deliberately unchanged to preserve existing bookmarks/redirects). Merged the To-do and Notifications tabs into a single unified scrollable list (to-do items followed by notifications), replacing the tab UI entirely. Added admin-settable triage state, due date, assignee, and tags to each item (task_manager_metadata table, taskManager tRPC router, TaskMetadataBar UI), plus 7-day/1-day due-date admin reminder notifications (task_manager_reminders_sent idempotency table, processTaskManagerReminders scheduled trigger) and a stubbed ingestScheduledMeeting() entry point for the future Meeting QR feature (#11773).#11779, #11767Task 18 S1 (#11767) — the Platform Reminders tab and the To-do/Notifications tab split specified in this spec's "Core — tab model" AC and Q1 are superseded by a decision to unify Action Items into a single Task Manager list, consistent with the platform simplification direction. The three-tab AC (Core — tab model, ⏳ Action Items screen exposes three tabs) and the Notifications-tab-specific ACs are DIVERGED FROM by this PR: there is now one list, not three tabs. This is a deliberate scope decision (team-lead sign-off), not a silent removal — flagging here per CLAUDE.md's "update the spec with the reason in the Change Log" rule. The spec's AC checklist itself has NOT been rewritten in this PR (that rewrite is a larger governance pass outside this issue's scope) — this fragment records the divergence so the drift is visible rather than silent.
2026-07-14Added a Home-screen quick-access affordance section — a notifications-style dropdown on the dashboard (RecentActionItemsMenu) surfacing the user's most recent outstanding action items, recency-sorted and capped, each deep-linking to its review surface, with a footer link to the full Action Items list. Hidden for admin personas. New ACs action-items.home.quick-access-affordance / -recency / -tap-opens / -hidden-for-admin, plus a @smoke BDD scenario.#10642, #10600Matt (Dev Session 2026-07-14) wanted the item he just created (e.g. a scanned logbook draft) one tap away from the home screen, instead of opening the full Action Items list and scrolling to find it.
2026-06-20Add atomic per-issue BDD acceptance scenarios for the four touch-safe To-do row-action ACs (card-tap-opens, row-actions-touch-visible, row-actions-hover-reveal, action-undo), closing the SGD traceability gap; fix a step-text mismatch in the existing #8590 open-tap scenario and add the hover-reveal step.#8976, #8958, #8959, #8960, #8961The behaviour shipped under the umbrella #8590 work but the four atomic sgd:gap ACs had no per-issue executable scenario, so each remained open and untraceable. Each AC now maps to its own @issue-&lt;N&gt;-tagged scenario (smoke for row-open and Undo happy paths, regression for the touch/hover affordances) that asserts and locks in the existing TodoItemCard sibling-tap-target, 44px touch snooze, hover-revealed snooze, and Undo snackbar behaviour.
2026-06-17Verified the action-items.todo.action-undo AC and added a @smoke @issue-8629 scenario covering the mark-as-done Undo path (the snooze Undo path was already covered under #8590); both snooze and mark-as-done now have BDD traceability.#8718, #8629The undo snackbar was implemented under #8590 but only the snooze Undo path had a scenario; the mark-as-done Undo path (the riskier per-device localStorage tick a mis-tap could hide) had no explicit acceptance scenario, leaving the AC partly untraceable.
2026-06-17Remove mark-as-done controls and ProgressRing; narrow row-actions ACs to Snooze-only; add priority chip tooltips.#8717, #8653Mark-as-done was localStorage-only (items reappeared daily) and violated the spec's "system-determined completion" requirement. Matt's UAT feedback confirmed removal. ProgressRing depended on the same hook and was always 0% without mark-as-done. Priority tooltip addresses UAT confusion ("what's low?").
2026-06-17Added an executable guard for action-items.label.native-menu-renamed — a menu-items unit test and a source-inspection BDD regression scenario assert the native "More" sheet entry reads "Action Items", not "Action"/"Actions".#8630, #8631PR #8607 renamed the label in source but a web-repo PR cannot rebuild the separate Expo app, so the device rename still awaits a native build (#8651). This locks the source label so the rename cannot silently regress; the AC stays ⏳ until a native build ships.
2026-06-16Recorded #8651 (Matt's 16 Jun UAT) as a confirming-drift citation on action-items.label.native-menu-renamed. The web sidebar/drawer menu was already renamed to "Action Items" and is BDD-guarded (notifications.feature @issue-7389), but the native app's More-menu still reads "Action" on the device build. Status row for the rename moved 📋 Specified → 🚧 Partial; the existing web nav-label regression scenario is now also tagged @issue-8651.#8651PR #8607 (issue #8590) claimed the native More-menu rename had shipped, but a web-repo PR cannot rebuild the separate Expo native app, so the rename never reached the device build Matt tested. #8651 is the drift signal proving the AC is not yet satisfied on native; it should stay open and link to a native app build rather than be closed by this spec PR. Duplicate-of-record for gap issues #8630 / #8631.
2026-06-10To-do row actions (Snooze / Mark as done) are now real, visible, 44px buttons rendered OUTSIDE the card's tap target on touch devices, with hover-reveal preserved on hover-capable devices; the card tap always opens the item; snooze and mark-as-done now raise an Undo snackbar. Native More-menu label 'Action' renamed to 'Action Items'.#8607, #8590Matt's UAT phone testing exposed hover-only icon buttons that stayed present-but-invisible (opacity:0) inside the card tap area on touch devices, so tapping the right edge of a card silently snoozed or ticked it off instead of opening it — and mark-as-done is localStorage-only, so items could disappear while still outstanding.
2026-05-26Rebuilt the Platform Reminders inventory table — grouped reminders by domain (compliance/expiry, CPD cadence, timesheet/attendance, wellness, profile) and separated event-driven Notifications/To-do from scheduled Platform Reminders.#7448, #7390The prior tables (inherited from notifications.md) interleaved unrelated categories — weekly wellness questionnaire, CPD-plan-not-submitted, and profile completion were lumped together with no grouping. Compiles the Q3 Platform Reminders research inventory and brings the section out of its "blocked" placeholder format.
2026-05-05Awaiting-Matt sweep — Q1 (Platform Reminders is its own tab), Q2 (triage tool removed, replaced with deadline-sort), Q4 (purple box treated as bug) and Q5 (tile copy [Verb] [Subject] — [deadline] standard) resolved engineering-led, Matt to ratify. Added Tab Taxonomy table mapping every surface event to the right tab.Shrink Matt's question queue to genuinely-blocked commercial decisions; engineering can answer UX/structural questions with project-memory-aligned defaults.
2026-04-21Spec created from Matt's 17 Apr 2026 Notion brief. Supersedes notifications.md — Matt now frames Notifications as one of three tabs inside a broader Action Items surface, rather than a standalone featurethis PRWave 1 foundation — Menu spec cites the pill/bell split; multiple downstream features emit events into this surface

Internal documentation — org members only