Apply Default Activity Values for Faster Proxy Entry
The documentation cites HLF where 60–70% of registrations require no reimbursement and should be 'extremely simple.' The design principle across all organizations is minimum cognitive load with standard values. For proxy registration, the defaults system must be context-aware: default date is today, default duration matches the most recently used duration for this activity type, and the most common activity type for this peer mentor can optionally pre-select. Coordinators who are registering for many mentors in sequence should experience a fast, consistent flow with minimal required input.
User Story
Acceptance Criteria
- Given the coordinator opens the proxy activity form for a peer mentor, when the form renders, then the date field defaults to today's date
- Given the coordinator opens the proxy activity form, when the form renders, then the duration field defaults to 30 minutes (or the organization's configured standard)
- Given the coordinator has previously registered activities of the same type, when they open the proxy form, then the activity type pre-selects the most recently used type
- Given defaults are pre-filled, when the coordinator reviews the form, then all default values are editable and the UI clearly indicates which fields are pre-filled vs. manually entered
- Given the coordinator completes a proxy registration successfully, when they immediately start another proxy registration for a different mentor, then the previous activity type and duration are retained as defaults for the next entry
- Given an organization has configured custom default durations or activity types, when a coordinator from that organization opens the proxy form, then the organization-specific defaults are applied
Business Value
The entire product philosophy is built around minimizing cognitive load and registration friction. HLF's most common registration type (short informal contact, no reimbursement) should require essentially zero thought. Smart defaults that reflect usage patterns directly reduce the number of required taps per registration, making it realistic for coordinators to log activities in real time rather than batching them up into a stressful end-of-month reporting session.
Components
- Bulk Registration Defaults Provider infrastructure
- Registration Defaults Manager service
- Registration Preferences Store data
- Proxy Activity Form ui
- Proxy Registration BLoC service
- Proxy Registration BLoC service