Bulk Registration

Description

Enables coordinators to register the same activity for multiple peer mentors simultaneously, targeting recurring group activities such as weekly training sessions with many participants. Rather than submitting individual records sequentially, the coordinator selects multiple peer mentors, enters shared activity details once, and the system generates individual activity records for each participant. This reduces administrative overhead for high-volume coordinators and prevents the underreporting caused by unsustainable per-entry workflows.

Sources & reasoning

Lines 83-84 explicitly describe bulk registration for recurring group activities as a coordinator need shared by NHF, HLF, and Barnekreftforeningen. Line 151 assigns SHOULD HAVE priority in Phase 2 (Fase 2), mapping to v1.0 by ordinal position. The blueprint confirms [v1.0] for this feature. The SHOULD HAVE classification and second-phase placement together rule out MVP and confirm v1.0.

docs/source/likeperson.md · line 83-84

Koordinatorer må ha mulighet til å registrere aktivitet på vegne av sine likepersoner, enten enkeltvis eller samlet for faste aktiviteter (f.eks. ukentlig trening med mange deltakere).
docs/source/likeperson.md · line 151

| Bulkregistrering / proxy-rapportering | ✓ | ✓ | - | ✓ | ✓ | SHOULD HAVE | 2 |

Analysis

Business Value

HLF reported a single peer mentor accumulating 380 individual registrations in one year, illustrating the scale of repetitive data entry that bulk registration must address. For coordinators overseeing weekly group activities across many peer mentors, individual submissions are unsustainable and a primary driver of underreporting. Bulk registration reduces coordinator time-per-activity, increases reporting completeness, and supports accurate Bufdir data collection. Organizations like NHF with up to 1,400 local associations particularly benefit from efficient batch workflows that can cover an entire group session in one submission.

Implementation Notes

Extends the standard activity registration flow with a multi-select peer mentor picker, reusing existing contact and roster query infrastructure. BulkRegistrationService orchestrates transactional batch inserts with per-record validation, ensuring a single failed record does not abort the entire batch. BulkResultSummaryWidget presents post-submission counts of successful and failed insertions. Role guard middleware restricts bulk registration to coordinator and admin roles. Offline support is provided via the mutation outbox, which queues individual records generated from the batch for sync with retry and backoff logic matching the standard offline-first architecture.