Coordinator Team Reports
Feature Detail
Description
This feature gives coordinators a team-level overview of activity across the peer mentors they manage within their local association. Coordinators can view aggregated statistics including total activities logged, active versus inactive peer mentors, and period-over-period comparisons. The reports support the coordinator's oversight responsibility - identifying peer mentors who may need follow-up - without requiring access to the Admin Web Portal. Data is scoped strictly to the coordinator's own local association and does not expose cross-organization records.
Sources & reasoning
Line 322 names coordinator-level statistics as a Phase 1 MVP deliverable in the same bullet as personal statistics. Line 257 confirms the coordinator's oversight scope is the local association, establishing the correct data boundary for team reports. Both are placed in MVP by ordinal mapping of Fase 1.
-
docs/source/likeperson.md · line 322Enkel statistikkvisning per likeperson og per koordinator
-
docs/source/likeperson.md · line 257Coordinator: Oversees peer mentors within their local association, dispatches assignments, approves expenses, registers on behalf of others.
Analysis
Coordinators are responsible for quality and consistency of peer mentor activity within their local associations. Without team-level reporting in the mobile app, coordinators must use the Admin Web Portal or perform manual aggregation. Bringing team reports into the mobile app enables coordinators to act on insight immediately during field work. For organizations like NHF with 1,400 local associations, this reduces central administrative burden significantly. The feature also supports Bufdir data quality by surfacing activity gaps before they become reporting problems at export time.
TeamReportService queries the REST API for activities scoped to the coordinator's local association, applying role-based filtering enforced server-side by RoleGuardMiddleware. The API returns pre-aggregated summaries to minimize payload size and avoid exposing individual raw records unnecessarily. TeamReportScreen renders charts and tables using the same components as PersonalStatsScreen for visual consistency. Data is cached in Drift with a last-refreshed timestamp displayed to the user. The feature uses the organization labels system for tenant-specific terminology. Access is restricted to the Coordinator role at the API layer - peer mentors cannot access team-level data.
Components (6)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.