Certificate Renewal Reminder
Feature Detail
Description
Certificate Renewal Reminder automatically notifies peer mentors when their certification is approaching expiry, prompting them to re-enrol in renewal courses before active status lapses. The feature monitors expiry dates in the certifications table and dispatches push and in-app notifications on configurable lead times. For HLF an expired certificate triggers automatic removal from local association websites, making proactive renewal notification operationally critical - unnoticed expiry is a direct service disruption that forces coordinators to intervene manually.
Sources & reasoning
Phase 3 (v1.1) per priority matrix Fase column. Section 3.3 explicitly specifies 'automatisk påminnelse ved utløp' for HLF. Section 2.3 establishes the operational consequence of expiry - automatic removal from public websites - making proactive reminders a direct mitigant for a documented service disruption risk, not merely a convenience.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Unnoticed certification expiry creates immediate operational disruption: the mentor disappears from public directories, assignment dispatch stops, and coordinators must manually identify and contact lapsed mentors. An automated reminder removes this risk, reducing coordinator workload and maintaining continuous mentor availability. For HLF, where certification is tied to regulated status, this feature is a compliance enabler that directly reduces the incidence of non-compliant active mentors. The push notification infrastructure established by the Notifications area is already available, making this a low-cost feature with outsized operational impact relative to implementation effort.
A scheduled backend job queries the certifications table for records with expiry_date within configured reminder windows (default: 60, 30, and 7 days before expiry). For each matched record it inserts a notifications row and dispatches via the Push Notification Service. Reminder windows are configurable per organization via organization_settings to accommodate different renewal cycles. On Flutter, tapping a renewal notification deep-links directly to the relevant course catalog entry. Dispatch must be idempotent - the job checks for existing notifications for the same user, certification, and window before inserting. No new database tables are required; the certifications and notifications tables plus organization_settings cover all state.
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.