Proxy Mode Selector Screen
Component Detail
Description
Entry screen allowing coordinators to choose between single-proxy mode (one peer mentor) and bulk mode (multiple peer mentors). Presents clear visual distinction between the two flows and explains the audit trail implications to the coordinator before proceeding.
proxy-mode-selector-screen
Summaries
The Proxy Mode Selector Screen is the entry point for coordinators submitting expenses on behalf of peer mentors, a workflow that directly enables the organisation's volunteer support model. By clearly presenting the choice between single-proxy and bulk submission modes — and explicitly surfacing the audit trail implications of each — the component reduces the risk of misattributed expense claims and protects the organisation during financial audits or grant reporting. A clear, guided entry point lowers coordinator training costs, reduces submission errors, and builds confidence in the integrity of the reimbursement process. This directly supports compliance with funder requirements and strengthens trust between the organisation and its volunteer network.
This screen has low technical complexity with no external dependencies, making it a straightforward deliverable. However, it is a critical branching point in the coordinator workflow — its design must be validated with real coordinators before downstream proxy selection and bulk upload screens are built, as its navigation decisions shape the entire proxy submission flow.
User testing should confirm that the audit trail explanation is understood by non-technical coordinators. Delivery risk is low, but scope creep is possible if stakeholders request additional mode options or conditional routing logic mid-sprint. Ensure UI copy for the audit trail explanation is reviewed and approved by compliance or programme staff before release.
This is a mobile-only UI screen that acts as a navigation dispatcher for the proxy submission flow. It presents two selectable modes — single-proxy and bulk — and routes to the appropriate peer mentor selection screen via `navigateToMentorSelection(mode)`. The `displayModeDescription(mode)` interface should drive dynamic descriptive text explaining audit trail implications per mode, keeping the component data-driven and easy to update without code changes. There are no service or data dependencies, so the component can be built and tested in isolation using mock navigation handlers.
Navigation state passed downstream (the selected mode) must be typed and validated to prevent downstream screens from receiving an undefined or invalid mode value. Keep mode selection state local — no global store needed for this transient choice.
Responsibilities
- Present single-proxy and bulk mode options with clear labels
- Explain audit trail and attribution distinction to coordinator
- Navigate to appropriate peer mentor selection flow
Interfaces
selectSingleProxyMode()
selectBulkMode()
displayModeDescription(mode)
navigateToMentorSelection(mode)