HIGH story-structured-post-session-report-coordinator-006 5 pts
5
Story Points
High
Priority
Structured Post-Session Report
Feature

User Story

As a Coordinator
I want to see a report form that is tailored to my organisation's specific field configuration, including custom terminology and required sections relevant to my work
So that I only fill in fields that are relevant to my organisation and the report captures the specific information my coordinator and organisation need

Acceptance Criteria

  • Given a peer mentor from Blindeforbundet opens the post-session report, when the form loads, then only Blindeforbundet-configured sections and fields are displayed
  • Given a peer mentor from HLF opens the post-session report, when the form loads, then only HLF-configured sections are shown with HLF-specific terminology
  • Given the device is offline when the peer mentor opens the report form, when the cached schema is available, then the form loads using the cached configuration with an offline indicator shown
  • Given org-specific terminology is configured (e.g., 'contact' vs 'recipient'), when the report form renders field labels, then the org-specific term is used throughout
  • Given the org field configuration is updated by an admin, when the peer mentor next loads the report form with connectivity, then the updated schema is fetched and the cache is refreshed

Business Value

Each organisation has distinct reporting needs shaped by their workflows, Bufdir requirements, and operational structure. A one-size-fits-all report form would either overwhelm peer mentors with irrelevant fields or omit critical organisation-specific data. Dynamic org-configured forms ensure high data quality and relevance, reduce cognitive load, and make the app viable for a multi-tenant deployment across NHF, Blindeforbundet, and HLF without forking the codebase.