Team Reports
Feature Detail
Description
Team Reports gives coordinators and organization administrators structured views of activity data aggregated across their peer mentor teams. The feature enables coordinators to track participation rates, identify underreporting gaps, and verify data quality before it feeds into formal grant reporting cycles. Reports support filtering by date range, activity type, and individual peer mentor, giving administrators the oversight needed for operational management and internal accountability across an organization's local chapters and regions.
Sources & reasoning
The source doc describes manual Excel aggregation as unsustainable and explicitly lists aktivitetsoversikt og grunnleggende statistikk as an MVP admin deliverable in Phase 1. Blueprint assigns [MVP], matching Phase 1 (first/launch phase). Team Reports is the foundational reporting layer that makes raw activity data visible to coordinators before Bufdir-specific export is introduced in Phase 2.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Without team-level reporting, coordinators cannot verify whether peer mentors are logging accurately, catch coverage gaps, or produce the organizational summaries required for internal accountability. All four organizations identified current reporting workflows - Word forms, manual Excel aggregation - as unsustainable and a direct cause of massive underreporting. Team Reports transforms raw activity registrations into actionable oversight data, allowing coordinators to catch missing entries well before Bufdir reporting deadlines rather than discovering gaps at crunch time. For NHF with 1,400 local chapters, filtered views by region and local association are essential for verifying data completeness across a highly distributed volunteer network.
Implemented as a Next.js server-side rendered page in the Admin Web Portal, querying the shared PostgreSQL database via the REST API. All queries carry strict tenant-scoped WHERE clauses against users, activities, and user_organization_roles to enforce multi-tenancy. The UI exposes date range pickers, activity type filters, and peer mentor selectors labelled with each organization's configured terminology overrides. Role-based guards restrict the page to Coordinator and Org Admin. Pagination and cursor-based loading handle NHF-scale organizations. A secondary CSV export endpoint streams query results server-side. The reports table persists generated report metadata for audit reference.
Components (47)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.