Select Peer Mentors from Contact List for Proxy Registration
In larger chapters, coordinators may be responsible for dozens of peer mentors. An unfiltered flat list makes peer mentor selection slow and error-prone. The peer mentor selector used in proxy and bulk registration must leverage the same contact list infrastructure, supporting search by name, filtering by status (active, paused), and showing enough contextual information (certification status, last activity date) to help the coordinator confirm they have selected the right person. This is especially important for coordinators at NHF with its complex 12-national-association structure.
User Story
Acceptance Criteria
- Given the coordinator opens the peer mentor selector for proxy registration, when the list loads, then it shows all peer mentors within the coordinator's access scope, with name and chapter affiliation visible
- Given the peer mentor selector is open, when the coordinator types in the search field, then the list filters in real time to show only matching names
- Given the peer mentor selector is open, when the coordinator applies a status filter (e.g., 'Active only'), then paused or inactive peer mentors are hidden
- Given the coordinator searches and finds a peer mentor, when they tap the entry, then the mentor's name, chapter, and certification status are confirmed before proceeding
- Given the coordinator is in bulk selection mode, when they search and select mentors one by one, then each selected mentor is added to a 'selected' list visible at the top of the screen
- Given a peer mentor is on pause, when they appear in the selector, then a pause status indicator is shown and the coordinator sees a warning if they attempt to select a paused mentor
Business Value
The speed and accuracy of peer mentor selection directly determines whether coordinators actually use proxy registration or give up and skip the entry entirely. A well-designed selector that supports fast name search and shows relevant context (certification status, pause state) eliminates the friction that causes coordinators to skip logging — which is the root problem the entire feature set is designed to solve.