Coordinator Team Reports

Coordinators are the operational backbone of every participating organisation, yet they currently rely on manually aggregated Word and Excel reports to understand what their team is doing. This creates a reporting lag of days or weeks, makes it difficult to spot underperforming or overwhelmed peer mentors in time to intervene, and consumes coordinator time that could be spent on actual support work. A real-time team report view eliminates this overhead entirely. The feature is also a prerequisite for Bufdir reporting automation: the same aggregated data that coordinators use for internal oversight feeds directly into the Bufdir export pipeline. Building team reports as a first-class feature rather than a reporting afterthought ensures the data model is correct, auditable, and ready for regulatory submission from day one, reducing compliance risk for all four organisations.

Team report data is fetched from the REST API (`GET /api/v1/reports/team`) which accepts organisation_id, association_id, date_range, and optional peer_mentor_id parameters. The endpoint aggregates from the activities table with a JOIN on users and organisation_memberships, enforcing tenant isolation at the query level. Response is paginated by peer mentor to keep payload sizes manageable for large associations (NHF has up to 1 400 local chapters). On the mobile side, a Riverpod FutureProvider fetches and caches the report; pull-to-refresh triggers a re-fetch. The Admin Web Portal renders the same data via a server component with React Table for sorting and filtering, plus a CSV export endpoint. Role guard middleware on both client and API ensures only Coordinator and Org Admin roles can access team-level data. The inactive-mentor flag is computed server-side (no activity in configurable N days, default 30) and surfaced as a highlighted row in the report table.