Bulk Registration
Feature Detail
Description
Bulk Registration allows coordinators to register the same activity type for multiple peer mentors or contacts in a single operation, designed for recurring group activities such as weekly training sessions, group meetings, or events with many participants. Instead of submitting one registration per person, the coordinator defines the activity once (type, date, duration, location) and selects multiple participants, generating individual activity records for each. This dramatically reduces administrative overhead for high-frequency group activities.
User Flow
Analysis
A single coordinator managing a weekly group session with 10–15 participants would otherwise need to submit 10–15 individual activity records per session — potentially hundreds per month. HLF documented a peer mentor with 380 individual registrations in a single year, highlighting the scale of the problem. Bulk registration directly addresses this by collapsing repetitive data entry into a single action. This reduces friction enough to meaningfully improve reporting compliance for group activities, which are currently among the most underreported due to effort. Accurate group activity data also strengthens Bufdir reporting and provides richer coordinator-level statistics.
The implementation requires a multi-select participant list UI (Flutter) with search and filter capabilities scoped to the coordinator's local association. The activity definition form mirrors the standard wizard but omits the single-contact selector in favor of the participant list. On submission, the backend generates one activity record per selected participant atomically within a database transaction — partial failures must roll back the entire batch to avoid inconsistent state. The API endpoint should accept a `participants` array alongside standard activity fields and return a summary of created records. Bulk operations should be clearly labeled in the activity feed and audit log. Consider a confirmation step showing participant count and activity details before final submission to prevent accidental bulk entries. Performance testing required for batches of 50+ participants.
Components (114)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.