Complete a structured post-session report after a home visit
After a peer mentor completes a home visit or session, they need to fill in a structured post-session report. The form presents org-configured sections including the contact's current health status, expressed interest in courses or programs, assistive device situation, and a 'way forward' section that captures concrete next steps. The form is rendered dynamically based on the organization's field configuration, so different organizations can have different required and optional fields. The report is saved to the database and made visible to the assigned coordinator.
User Story
Audience Summaries
This high-priority story directly addresses a critical operational gap for Blindeforbundet and similar organizations: post-session follow-up is currently communicated informally, leading to lost tasks, missed referrals, and inconsistent service quality. By formalizing the post-session report into a structured, database-backed workflow, the organization gains a reliable audit trail of every peer mentor interaction. This drives measurable improvements in coordinator responsiveness, supports compliance with Bufdir reporting requirements, and reduces administrative overhead. The dynamic field configuration model also positions the platform as a multi-tenant solution adaptable to diverse organizational workflows, increasing commercial scalability and customer retention across the disability services sector.
This is a high-priority story with moderate-to-high delivery complexity. It requires coordination across three functional areas: dynamic form rendering (org-specific field configuration), data persistence (report submission and database storage), and coordinator notification (real-time or async alerting on report submission). The org-configured field system introduces a dependency on an existing or new field-configuration admin interface, which must be confirmed in scope. Acceptance criteria are well-defined and testable.
UAT should involve both peer mentor and coordinator personas across at least two different org configurations to validate multi-tenancy. Risks include field configuration schema design decisions that could affect downstream reporting features. Timeline should account for notification infrastructure if not already in place.
Implementation requires a dynamic form rendering engine that reads org-specific field configurations from a configuration table and renders required and optional fields accordingly. The form component must support text input, field-level validation, and conditional required-field enforcement before submission. On submission, the report record is persisted to the database with a foreign key to the peer mentor, contact, and organization. A notification must be dispatched to the assigned coordinator — this could use an existing notification service or require a new trigger.
The coordinator's contact detail screen must query and display submitted reports ordered by timestamp. Key edge cases: concurrent submissions, missing org field config (fallback rendering), and coordinator assignment changes after report submission. Consider schema versioning for org field configs to support future changes without breaking existing reports.
Acceptance Criteria
- Given a peer mentor has completed an activity, when they open the post-session report screen, then the form displays all org-configured sections (health status, course interest, assistive device situation, way forward) in a logical order
- Given the report form is open, when the peer mentor fills in each section, then each field accepts text input and the form validates required fields before submission
- Given the peer mentor submits the report, when all required fields are complete, then the report is saved to the database and the coordinator is notified
- Given a report has been submitted, when the coordinator views the contact's detail screen, then the report is visible and timestamped
- Given the report form has org-specific custom fields, when the peer mentor opens the form, then only their organisation's configured fields are shown
Business Value
Formalising post-session reporting eliminates the current situation where follow-up tasks are communicated informally or forgotten. For Blindeforbundet this is a core workflow: the report acts as a task request to the coordinator covering assistive device inquiries, course referrals, and health observations. Structured data also enables future aggregation for Bufdir reporting and quality assurance, directly reducing administrative burden at the organisational level.
Components
- Post-Session Report Screen ui
- Dynamic Field Renderer ui
- Way Forward Section Widget ui
- Report Form Orchestrator service
- Report Schema Service service
- Report Field Validator service
- Post-Session Report Repository data
- Report Schema Cache data
- Organisation Field Config Loader infrastructure