Certification Expiry Auto-Pause
Feature Detail
Description
Certification Expiry Auto-Pause monitors peer mentor certification expiry dates and automatically transitions the mentor to paused status when their certification lapses. The mentor and coordinator are notified in advance of impending expiry and again at the moment of auto-pause. The mentor is blocked from receiving new assignments until certification is renewed and the pause is cleared by renewal completion or a coordinator override with recorded justification.
Sources & reasoning
HLF explicitly linked pause to certification expiry in workshops - expired cert should auto-remove the mentor from public listings. Certification training is scoped to Fase 3 in the roadmap (v1.1 ordinal), and auto-pause depends on that system being present. The blueprint lists this feature at v1.1, consistent with Fase 3 ordinal mapping.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
HLF explicitly tied the pause mechanism to certification: when a certification expires, the mentor must automatically disappear from the local association's public-facing listings and stop receiving assignments. This is a compliance concern - dispatching assignments to uncertified mentors creates organizational liability. Auto-pause removes the dependency on manual coordinator action, which is error-prone under workload. For HLF and Barnekreftforeningen, both with structured certification programs, this automation makes certification a trustworthy enforcement mechanism rather than advisory guidance that can be bypassed under operational pressure.
A scheduled backend job (daily cron) queries the certifications table for records where expiry_date falls within a configurable warning window (default 30 days) or is already past. Approaching expiry dispatches push notifications to the mentor and dashboard alerts to linked coordinator(s). On expiry the job calls the same status-transition logic as manual pause, writing peer_mentor_statuses.status as paused with a system-generated reason. The Flutter app reflects this identically to a manual pause and displays an expiry banner linking to the course registration or renewal flow. This feature is only active when both peer-mentor-status and certification-training modules are enabled for the tenant.
Components (45)
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.