medium complexity extracted Reporting & Export Confidence: 100%
3
Components
39
Shared
0
User Stories
Yes
Analyzed

Description

Team Reports provides coordinators and organization administrators with structured, aggregated views of activity data across all peer mentors within their scope. The feature consolidates individual activity registrations into meaningful summaries - total hours, activity types, contact coverage, and trend lines - displayed through a dedicated reports page in the Admin Web Portal. Reports can be filtered by date range, activity type, and organizational unit. This supports the recurring operational need to understand team performance without manually aggregating data from spreadsheets or Word forms, which all three workshop organizations described as a significant time sink.

Analysis

Business Value

All three workshop organizations - NHF, Blindeforbundet, and HLF - cited manual aggregation of activity data as a major operational burden. Coordinators currently compile Excel sheets from Word forms submitted by individual peer mentors, a process that is both error-prone and time-consuming. Team Reports eliminates this entirely by surfacing pre-aggregated data in real time. For organization administrators, the feature provides a live operational dashboard that replaces end-of-period reporting scrambles. Strategically, accurate team-level data is the prerequisite for both Bufdir reporting and internal management decisions, making this a foundational capability that multiplies the value of activity registration across the entire platform.

Implementation Notes

The Team Reports page is a server-side rendered Next.js page consuming a dedicated `/api/v1/reports/team` endpoint that aggregates data from the activities and organization_memberships tables in PostgreSQL. Query parameters support date range, activity type filter, and organizational unit scoping. The backend applies role-based tenant isolation - coordinators see only their local chapter, org admins see their full organization, global admins are blocked from operational data by default. Report data is computed on-demand rather than materialized to avoid stale caches; for large organizations a pagination or chunked fetch strategy is needed. The frontend renders a responsive data table and summary stat cards using the admin portal design system. No PDF export is required at this tier - that belongs to Bufdir Export.

Components (42)

User Interface (2)

Service Layer (1)

Shared Components

These components are reused across multiple features

User Stories

No user stories have been generated for this feature yet.