Coordinator Proxy Reporting
Feature Detail
Description
Coordinator Proxy Reporting enables coordinators to register activities on behalf of peer mentors who are unable or unwilling to use the app themselves. This is a critical operational capability since not all peer mentors are digitally proficient or have consistent access to mobile devices. The feature supports single-entry proxy registration with full context (contact, date, duration, type) attributed to the correct peer mentor, ensuring accurate reporting without requiring the peer mentor to be present in the system.
User Flow
Analysis
Many peer mentors — particularly older volunteers or those with cognitive or physical challenges — will never adopt a mobile app independently. Without proxy reporting, their contributions go unregistered, leading to systematic underreporting that distorts Bufdir statistics and undermines the organization's funding case. This feature ensures full activity coverage regardless of digital adoption rate. For coordinators, it consolidates their oversight role: they already manage peer mentors day-to-day, so registering on their behalf is a natural extension of that responsibility. It directly improves data completeness and reduces the administrative burden of chasing missing reports.
The feature requires a coordinator-scoped UI flow that mirrors the standard activity registration wizard but includes a peer mentor selector at the start. The selected peer mentor's ID is stored as the activity owner while the coordinator's ID is logged as the submitting proxy — this distinction matters for audit trails and Bufdir reporting accuracy. Backend validation must enforce that coordinators can only proxy-register for peer mentors within their local association scope. The Flutter BLoC layer should reuse existing activity form state management with an injected 'on-behalf-of' parameter. API endpoint must accept an optional `proxy_user_id` field, validated server-side against the coordinator's organizational scope.
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.