Coordinator Team Reports
Feature Detail
Description
This feature gives coordinators an aggregated view of their team's activities, showing totals, trends, and individual mentor breakdowns for their local association. Coordinators can filter by date range, activity type, and individual mentor, and export or share summary data as needed. The reports are designed to support coordinators in their oversight role, enabling them to identify underreporting, recognize top contributors, and prepare for organizational review meetings without manually collecting data from each mentor.
User Flow
Analysis
Coordinators are the operational backbone of each partner organization, and they currently spend significant time chasing activity data from individual mentors and aggregating it manually in Excel. Providing automated team reports directly addresses this pain point, freeing coordinator time for actual mentor support. The feature also provides the data layer that underpins Bufdir reporting, meaning accurate team reports have a direct compliance and funding impact. All four partner organizations highlighted coordinator oversight as a core requirement, making this feature essential for organizational adoption and retention of the platform.
The team stats service queries the same activity tables as the personal stats service but scoped to all mentors within the coordinator's local association, enforcing row-level security at the database layer. Aggregation logic runs server-side via the Next.js REST API to keep the mobile client lightweight. The Flutter UI presents data in sortable lists and summary cards; charts use fl_chart with accessible alternatives. Coordinators with access to multiple local associations (supported by the multi-association model) can switch between association contexts. Pagination and lazy loading are required for associations with large mentor counts. Export functionality (CSV/PDF) is deferred to the admin portal but the data model must support it from day one.
Components (114)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.