Record way-forward tasks and next steps in the post-session report
The 'way forward' section in the post-session report is a structured list of tasks or action items generated from observations during the session. A peer mentor might note that the contact needs a referral to a hearing course, an assessment for an assistive listening device, or a follow-up call in two weeks. These items are stored as structured way-forward records linked to the report and the contact, and are surfaced to the coordinator as pending tasks. This replaces informal phone calls or untracked notes.
User Story
Audience Summaries
This story elevates the post-session report from a static document into a live coordination tool, directly addressing the organizational risk of follow-up tasks being lost after peer mentor home visits. For Blindeforbundet, the 'way forward' section functions as a formal task request mechanism — replacing informal phone calls and untracked notes with structured, timestamped action items visible to coordinators. This improves service continuity, ensures that every expressed need (device assessments, course referrals, follow-up calls) is captured and actioned, and provides leadership with visibility into pending and completed follow-ups. The closed-loop status update (coordinator actions item, peer mentor sees resolution) also improves transparency and trust between field and office staff, directly contributing to service quality and beneficiary outcomes.
This story has a declared dependency on story 808 (the post-session report form) and must be sequenced after it. Delivery complexity is moderate: it requires designing a structured way-forward record model (description, due date, status, linked report and contact), CRUD operations for way-forward items within the report form, and a coordinator-facing task list view on the contact profile. The status update feedback loop (coordinator marks item done, peer mentor sees it) introduces a bidirectional state-sync requirement that should be clarified — real-time or eventual consistency. Testing must cover multi-item add/remove within a single report session, status transitions, and cross-role visibility.
Stakeholder sign-off from both peer mentor and coordinator user groups is recommended before development begins to confirm the workflow matches field expectations.
This feature requires a `way_forward_items` table (or embedded JSON structure) with fields for description, optional due date, status (pending/actioned), and foreign keys to the parent report and contact. The report form must support dynamic addition and removal of way-forward items before submission, with client-side list management (add, edit, delete without page reload). On report save, all items are persisted atomically with the parent report. The coordinator's contact detail view must query way-forward items filtered by contact, displaying status badges and timestamps.
A status update endpoint is required for coordinators to mark items as actioned, with the change reflected on the peer mentor's side — evaluate whether WebSocket push or polling is appropriate given the app's real-time requirements. Edge cases: deleting all items before save, submitting with zero items (should be allowed), and preventing status regression. Ensure cascading deletes if the parent report is deleted.
Acceptance Criteria
- Given the peer mentor is on the post-session report screen, when they reach the way-forward section, then they can add one or more structured action items with a description and optional due date
- Given the peer mentor adds a way-forward item, when they save the report, then the item is persisted as a linked way-forward record in the database
- Given a report with way-forward items is submitted, when the coordinator views the contact's profile, then all way-forward items are listed with their status
- Given a way-forward item has been actioned by the coordinator, when the item status is updated, then the peer mentor can see it has been addressed
- Given the peer mentor needs to remove a way-forward item before submitting, when they delete it, then it is removed from the list without affecting other items
Business Value
Structured way-forward items transform the post-session report from a passive document into an active coordination tool. Coordinators get an actionable task list directly from peer mentors' field observations, reducing the risk of follow-up tasks being lost. This is critical for Blindeforbundet where the report explicitly serves as a formal task request to the coordinator, and it improves overall service quality by ensuring every contact's needs are tracked and followed up.