Proxy Confirmation Screen
Component Detail
Description
Confirmation step presented before final proxy submission, showing a full summary of the activity details and the complete list of attributed peer mentors. Requires explicit coordinator approval to prevent accidental multi-mentor submissions.
proxy-confirmation-screen
Summaries
The Proxy Confirmation Screen is a critical safeguard in the proxy activity registration workflow that protects data integrity and coordinator accountability. Before any activity is submitted on behalf of one or more peer mentors, coordinators are presented with a complete, readable summary of all details — activity type, date, duration, notes, the acting coordinator's identity, and the full list of attributed mentors. This explicit confirmation step prevents costly data entry errors, particularly in bulk submissions where a coordinator might inadvertently register an activity for the wrong mentors or with incorrect details. Correcting such errors after submission requires manual database intervention and erodes trust in reporting accuracy.
This screen is a low-cost quality gate that protects the integrity of all downstream program metrics and stakeholder reports.
The Proxy Confirmation Screen is a low-complexity terminal step in the proxy registration flow, with no external component dependencies. It is a pure display screen that receives fully assembled data from its parent (proxy-registration-screen or bulk-proxy-registration-screen) and presents it for review. Development effort is low — estimated 1–2 days — but it is a required deliverable before either registration screen can complete end-to-end testing. The primary delivery risk is ensuring the data contract between parent screens and this screen is well-defined early: the ActivityData structure and mentor ID list format must be agreed upon before implementation begins.
UAT must verify that the mentor attribution list renders correctly for both single-mentor and multi-mentor cases, and that the back navigation correctly returns to the registration screen without losing form state. No backend calls are made from this screen, simplifying testing.
The Proxy Confirmation Screen is a StatelessWidget (or minimal StatefulWidget) that receives its display data entirely via constructor parameters or route arguments — it makes no service calls or database queries. renderActivitySummary(ActivityData data) builds a structured display of activity type, date, duration, and notes from the passed ActivityData object. renderMentorAttributionList(List
onBack() pops the route, returning the user to the registration screen; the parent must preserve form state across this navigation (use a shared Bloc or ChangeNotifier, not ephemeral widget state). The screen consumes activity and peer-mentor data models for display only. Execution contexts are frontend and mobile. Ensure mentor ID list rendering handles both the single-mentor case (proxy-registration) and multi-mentor case (bulk-proxy-registration) gracefully, ideally via a shared renderMentorAttributionList implementation.
Responsibilities
- Display full activity details summary
- List all attributed mentor names with IDs
- Show acting coordinator identity
- Handle final confirm or back navigation
Interfaces
build(BuildContext)
onConfirm()
onBack()
renderMentorAttributionList(List<String> mentorIds)
renderActivitySummary(ActivityData data)