Coordinator Proxy Reporting

Description

Coordinators can register activities on behalf of peer mentors unable or unwilling to use the app directly. This enables accurate reporting even when peer mentors are digitally excluded or temporarily unavailable. The feature supports single-entry proxy registration, allowing a coordinator to select a peer mentor from their managed roster and submit activities as that person, maintaining reporting fidelity without forcing full platform adoption across all participants in the organization.

Sources & reasoning

Lines 83-84 define proxy reporting as a shared coordinator need for NHF, HLF, and Barnekreftforeningen, explicitly motivated by peer mentors who will not or cannot use the app. Line 151 places the requirement at SHOULD HAVE in Phase 2 (Fase 2), which maps to v1.0 by ordinal position. The blueprint also assigns [v1.0] to this feature, confirming the target release.

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

Multiple organizations (NHF, HLF, Barnekreftforeningen) explicitly require proxy reporting because not all peer mentors will or can use the app. Without this capability, organizations face underreporting that directly impacts Bufdir funding calculations and program accountability. Coordinators are already responsible for oversight, making them natural proxies for digitally excluded volunteers. This feature bridges the gap between digital adoption and operational continuity, ensuring the platform delivers value during partial rollout periods where some peer mentors have not yet transitioned from legacy processes.

Implementation Notes

Implemented as a coordinator-only flow gated by role-based access control. The UI presents a PeerMentorSelectorWidget filtered to the coordinator's managed roster, sourced from the contacts and user management system. Activity submission routes through the standard ActivityService but tags each record with both the coordinator's identity and the proxied peer mentor's ID for audit and Bufdir reporting. Backend validation enforces coordinator-to-peer-mentor scope before accepting a proxy submission, preventing cross-organization abuse. Offline proxy submissions are queued in the mutation outbox with standard retry and backoff logic.