Bulk Registration

Description

This feature enables coordinators to register the same activity for multiple peer mentors or contacts in a single operation. Instead of creating identical records one by one, the coordinator defines the activity once - type, date, duration, and notes - then selects a list of participants. The system generates individual activity records for each selected participant from the shared template. This is particularly important for recurring group activities such as weekly training sessions, group meetings, or organized events where many peer mentors participate simultaneously. The feature dramatically reduces administrative overhead for coordinators managing large groups and ensures that high-volume activities are never omitted from reports due to the cost of manual entry.

User Flow

Click to expand

Analysis

Business Value

HLF reported peer mentors with up to 380 individual registrations per year, and NHF coordinators manage recurring group activities across large local associations. Manual one-by-one entry for group events is a primary driver of underreporting - coordinators either skip registration entirely or delay it until details are forgotten. Bulk registration directly resolves this bottleneck and is expected to recover a significant volume of currently unregistered activities that affect funding calculations. Beyond reporting completeness, bulk registration respects coordinator time. Reducing a 20-record group session from 20 separate data entry flows to a single operation is a meaningful quality-of-life improvement that increases willingness to use the platform consistently. This also reduces the risk of data inconsistencies across records for the same event, since all records derive from a single source entry.

Implementation Notes

The bulk registration screen presents a standard activity form followed by a multi-select participant picker scoped to the coordinator's local association. On submission, the BLoC layer dispatches a batch creation event that iterates the selected participants and creates individual activity records, reusing the proxy registration service for each. The API should expose a dedicated bulk endpoint that accepts an activity template plus a participant ID array and processes them transactionally to ensure all-or-nothing persistence. Flutter UI should provide clear feedback during batch creation - a progress indicator and a post-submission summary showing how many records were created and flagging any failures. Large batches (50+ participants) should be processed in chunks to avoid request timeouts. The participant selector must support search and filter by name to handle coordinators managing dozens of peer mentors efficiently. All individual records created via bulk registration are marked with both the coordinator's ID and a shared batch reference ID for audit traceability.