Resume Function
Feature Detail
Description
The Resume Function allows a paused peer mentor to return to active status. The flow guides the mentor through reactivation, confirms their availability and contact details are current, and notifies their coordinator that they are again available for assignments. Resume may be self-initiated by the mentor or prompted by a coordinator reminder notification sent after an extended pause period has elapsed.
Sources & reasoning
Resume is the logical completion of the pause lifecycle. The source describes pause as "midlertidig deaktivering" (temporary deactivation), which directly implies reactivation is expected. It shares the same Fase 2 placement as pause-function (v1.0 ordinal). Without a resume flow, pause becomes a one-way exit rather than a temporary state - defeating its stated purpose.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
The resume flow closes the lifecycle loop opened by the pause function. Without a structured resume path, paused mentors remain inactive indefinitely due to friction or forgetfulness, eroding the active mentor pool over time. A guided resume flow reduces this risk and gives coordinators a mechanism to prompt mentors who have been paused for extended periods. For organizations dependent on volunteer capacity - HLF and NHF in particular - retaining experienced mentors through structured lifecycle management directly supports program continuity and reduces the cost of onboarding replacements who lack the same depth of relationship experience.
Resume is a status transition on peer_mentor_statuses (paused to active), triggered from the same Pause Toggle Screen used for the pause action. A brief confirmation step optionally verifies the mentor's availability preferences before the backend clears paused_at, resets status to active, and dispatches a push notification to linked coordinator(s). The flow must handle the expired-certification edge case: if certification lapsed during the pause period, the backend returns a validation error and routes the mentor to the certification renewal flow rather than reactivating directly. Status transitions must be atomic so no partial state persists on network failure.
Components (44)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.