🏠 Overview › 🎯 Features ›🎯 Bulk Registration & Proxy Reporting

Bulk Registration & Proxy Reporting

Feature Detail

high complexity extracted Activity Registration Confidence: 100%
4
Components
58
Shared
0
User Stories
Yes
Analyzed

Description

Enables coordinators to register activities on behalf of peer mentors who cannot or will not use the mobile app, and to submit bulk registrations for recurring group activities. Merges Bulk Registration, Coordinator Proxy Reporting, and Report on Behalf of Others into a unified workflow. The coordinator selects one or more peer mentors from their local association, enters shared activity details once, and submits collectively. The proxy relationship is recorded for audit transparency and compliance reporting.

User Flow

Bulk Registration & Proxy Reporting user flow
Click to expand

Analysis

Business Value

A significant proportion of peer mentors — particularly older volunteers or those with disabilities — will not independently adopt the app during the transition period. Without proxy reporting, coordinators must maintain parallel paper or Excel systems indefinitely, negating the app's efficiency benefits and creating ongoing reconciliation overhead. NHF and HLF both identified proxy reporting as a critical bridge function for the rollout. Bulk registration for recurring activities (weekly training sessions with fixed participants) eliminates repetitive manual entry that currently consumes coordinator time weekly. This feature determines whether organizations can fully retire their legacy reporting processes or remain permanently split across systems.

Implementation Notes

BulkRegistrationScreen uses PeerMentorSelectionScreen to select one or more proxy subjects from the coordinator's assigned peer mentor list, fetched from PeerMentorRepository. The selected mentors are passed as context into the standard activity wizard, which renders a proxy indicator banner throughout. ProxyRegistrationService submits via /api/v1/activities with a registered_by field containing the coordinator's user ID, enabling auditability. For bulk submissions, the service fans out a single activity payload into N individual activity records server-side. Role enforcement via RoleGuardService restricts access to Coordinator role and above. Offline support uses the shared sync queue, with per-record failure handling to prevent a single failed submission from blocking the batch.

Components (62)

User Interface (3)

ui Bulk Registration Screen high ui Peer Mentor Selection Screen medium ui Proxy Indicator Banner low

Service Layer (1)

service Proxy Registration Service high

Shared Components

These components are reused across multiple features

Infrastructure (20)

infrastructure JWT Infrastructure medium Shared infrastructure JWT Infrastructure low Shared infrastructure Auth Middleware medium Shared infrastructure Report API Middleware low Shared infrastructure Report Access Guard low Shared infrastructure Approval Audit Logger low Shared infrastructure End-to-End Encryption Infrastructure high Shared infrastructure Email Delivery Infrastructure low Shared infrastructure Invitation Token Infrastructure medium Shared infrastructure Signed URL Provider low Shared infrastructure Multi-Tenancy Infrastructure high Shared infrastructure Calculator Export Infrastructure medium Shared infrastructure Request & Response Interceptors high Shared infrastructure Design Token System medium Shared infrastructure Semantic Labels Infrastructure medium Shared infrastructure Connectivity Infrastructure low Shared infrastructure Local Database Infrastructure high Shared infrastructure Secure Storage Infrastructure medium Shared infrastructure Connection Pool Infrastructure medium Shared infrastructure Database Migration Infrastructure medium Shared

User Stories

No user stories have been generated for this feature yet.