Bulk Registration
Feature Detail
Description
Bulk Registration allows a coordinator to register a single recurring or group activity once and attribute it to multiple peer mentors simultaneously. The primary use case is a fixed weekly group session (e.g. a training session or support group) where the coordinator records one activity entry covering all attendees rather than filing individual records for each participant. The coordinator selects the participating peer mentors, fills in shared activity metadata (type, date, duration, summary), and the system creates one activity record per selected participant. This feature directly addresses the administrative burden documented for coordinators who oversee large peer mentor pools. A single coordinator managing a weekly group of ten peer mentors would otherwise face ten individual registrations per session - hundreds per year. Bulk registration collapses that into a single action while preserving per-peer-mentor granularity in reporting.
Sources & reasoning
The 380-registrations-per-year figure from §1.1 (HLF context) is the clearest quantitative evidence for bulk registration's value. §2.4 explicitly describes the group-activity use case. The matrix places it SHOULD HAVE Phase 2 → v1.0 by ordinal normalization. Bulk is modeled as a separate feature from proxy because its trigger (group activity, one submission many targets) is operationally distinct from individual proxy attribution, even though both are coordinator-only capabilities.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
HLF documented a peer mentor with 380 individual registrations in a single year, which the organization cited as evidence that the current manual process is unsustainable. Bulk registration directly solves the highest-volume registration scenario - recurring group activities - by replacing N individual submissions with one. NHF and Barnekreftforeningen also confirmed the need. The feature increases data completeness for Bufdir reporting because coordinators are more likely to register group activities when the cost is one action rather than ten. It also supports the platform's incremental adoption strategy: coordinators who manage large groups can realize immediate value without waiting for all peer mentors to self-register, reducing resistance to switching from legacy systems during the parallel-running transition period.
Bulk registration is implemented as a multi-select extension of the proxy activity wizard. After selecting activity metadata (type, date, duration, summary), the coordinator is presented with a searchable, multi-select peer mentor picker scoped to their organization. On submission the API receives a single payload with the activity data and an array of target user IDs; the backend creates one activity row per user ID in a single transaction, ensuring atomicity. Each created record links to the same coordinator as submitter and its respective peer mentor as owner. The mobile UI must handle large peer mentor lists efficiently - virtual list rendering is required for organizations with many members. Offline support must serialize the multi-target payload in the mutation outbox as a single outbox entry and expand it server-side on sync, avoiding N outbox entries for one user action. Duplicate detection (NHF requirement) should flag when a bulk submission covers an activity date/type/peer-mentor combination that already has a record.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.