Coordinator Proxy Reporting

Underreporting is the primary data quality risk for all partner organizations. NHF and HLF both explicitly raised this in workshops - if a peer mentor cannot or will not log their own activity, the coordinator must be able to do it for them or the activity disappears from the record entirely. This directly affects Bufdir grant compliance, since reported activity volumes determine funding levels. The feature also reduces coordinator frustration by giving them a single tool to maintain accurate team records without switching to Word or Excel fallbacks. Strategically, it is a prerequisite for Bufdir reporting accuracy and a key differentiator over generic activity-tracking tools that assume every user is self-sufficient.

The coordinator's session must carry a role claim that gates access to the proxy registration flow; the backend validates this before accepting submissions on behalf of another user. The activity record schema requires two user references - the performing peer mentor and the submitting coordinator - both stored and indexed. The mobile UI reuses the existing activity wizard screens but prepends a peer-mentor selection step driven by the coordinator's managed-members list fetched from the API. Offline support follows the same mutation outbox pattern as standard activity logging, with the proxy relationship preserved in the queued payload. Audit log entries are created server-side on every proxy submission.