Coordinator Team Summary View
Component Detail
Description
Aggregated summary screen visible only to coordinators, listing each peer mentor's period metrics in a scrollable list. Highlights underactive or overloaded mentors with visual indicators to enable proactive follow-up.
coordinator-team-summary-view
Summaries
The Coordinator Team Summary View empowers program coordinators with an at-a-glance dashboard of their entire mentor team's performance, enabling proactive intervention before issues escalate. By surfacing underactive or overloaded mentors through visual indicators, coordinators can redistribute workloads and prevent mentor burnout — directly protecting the quality of peer mentoring relationships that drive participant outcomes. This capability reduces the operational overhead of manual check-ins, freeing coordinator time for higher-value activities and strengthening the organisation's ability to deliver consistent, high-quality mentoring at scale.
This is a mobile UI component of medium complexity requiring integration with the activity-aggregation-repository and summary-generation-service. Development should be sequenced after both backend dependencies are stable and tested, as the view has no value without accurate aggregated data. Key delivery risks include performance on large mentor lists (scrollable list rendering) and the correctness of outlier threshold logic, both of which require dedicated QA passes. Testing must cover pull-to-refresh behaviour, tap-through navigation, status filter interactions, and outlier badge rendering across varying dataset sizes.
Plan for at least one design review cycle to validate coordinator usability.
CoordinatorTeamSummaryView is a mobile-only UI component that consumes data from activity-aggregation-repository and summary-generation-service via the TeamSummaryView({coordinatorId, period}) interface. It renders a scrollable list using renderMentorRow(mentor, summary, status), applying outlier badges via renderOutlierBadge(type) for mentors outside configured thresholds. Navigation to individual mentor profiles is handled through onMentorTap(mentorId). The component must manage local state for the active filter (filterByStatus) and refresh lifecycle.
Data models consumed are periodic-summary and peer-mentor. Ensure the outlier threshold values are configurable and sourced from a central constants layer rather than hardcoded to simplify future tuning.
Responsibilities
- List all peer mentors under coordinator with period metrics
- Highlight outliers (underactive below threshold, overloaded above threshold)
- Allow tap-through to individual peer mentor profile
- Support pull-to-refresh for latest data
Interfaces
TeamSummaryView({coordinatorId, period})
renderMentorRow(mentor, summary, status)
renderOutlierBadge(type)
onMentorTap(mentorId)
refresh()
filterByStatus(status)
Relationships
Dependencies (2)
Components this component depends on
Related Data Entities (1)
Data entities managed by this component