Add Optional Free-Text Notes to a Registration
After confirming the core registration fields, a notes step is available but entirely optional. The step presents a single multi-line text field. The peer mentor can skip directly to confirmation without entering anything. Notes are stored alongside the activity record and are visible to the coordinator on the activity detail view. The notes field should support speech-to-text input via the device's native keyboard dictation button so that peer mentors who prefer spoken input can use it without a dedicated in-app speech feature.
User Story
Audience Summaries
Optional free-text notes directly address a formal compliance requirement for Blindeforbundet, where structured documentation after home visits is part of mandated reporting to Bufdir. By making notes optional rather than required, the product preserves the speed and simplicity that drives adoption among peer mentors — the primary field-level users — while enabling richer qualitative data capture when context demands it. This design decision supports two competing business priorities simultaneously: high registration completion rates and regulatory reporting completeness. The inclusion of native speech-to-text support via device keyboard dictation broadens accessibility for users with visual impairments or motor limitations, which is directly aligned with Blindeforbundet's core mission.
Coordinators gain richer activity context without additional administrative burden, improving decision-making quality for follow-up actions and strengthening the organisation's ability to demonstrate program impact to funders.
This story introduces an optional notes step into the existing multi-step registration flow, building on the dependency story-quick-activity-registration-peer-mentor-001. Delivery effort is moderate: the UI step is straightforward, but validation logic (1000-character limit with real-time counter and accessible error state), skip-path handling, and data persistence alongside the activity record all require careful coordination. No dedicated in-app speech feature is needed — native keyboard dictation satisfies the requirement, which removes a significant implementation risk. Acceptance criteria are well-defined and testable, making UAT planning straightforward.
Key stakeholders include coordinators (who consume note data) and accessibility reviewers (to validate the error message implementation). A risk to flag: character limit enforcement must be tested across iOS and Android keyboard behaviours, particularly with pasted content and dictated input, where character count can spike unexpectedly. Rollout can be feature-flagged to validate coordinator uptake before full release.
Implementation requires adding a new optional step to the registration wizard after the core fields confirmation. The step renders a single `