Notification Scenarios

Description

Notification Scenarios define the business rules that trigger notifications automatically based on platform events and time-based conditions. Examples include an automatic reminder when a peer mentor has not logged contact with an assignment within 10 days, and a push alert when certification is approaching expiry. The NotificationScenarioEngine evaluates registered trigger rules against platform state at scheduled intervals and fires the appropriate notification type and channel via NotificationDispatcher.

Sources & reasoning

Line 95 documents Blindeforbundet's explicit 10-day uncontacted-assignment reminder requirement - a textbook notification scenario. Line 116 frames HLF's follow-up improvement around scenario-based push messages. Both sources place this in Phase 2 (→ v1.0), matching the blueprint's [v1.0] tag.

docs/source/likeperson.md · line 95

Automatisk påminnelse etter 10 dager dersom kontakt ikke er opprettet.
docs/source/likeperson.md · line 116

Scenariobaserte push-meldinger og kalendersynkronisering.

Analysis

Business Value

Manual follow-up coordination is a significant coordinator workload item across all organizations. Automating scenario-based notifications proactively alerts peer mentors and coordinators when action is needed, without requiring manual monitoring. For Blindeforbundet, the 10-day automatic reminder for uncontacted assignments is a documented requirement that directly reduces risk for vulnerable individuals awaiting peer mentor contact. For HLF, certification expiry reminders reduce coordinator effort in tracking renewal deadlines across large mentor populations. Scenario automation enables coordinators to scale oversight without proportional headcount growth.

Implementation Notes

NotificationScenarioEngine runs as a scheduled background worker on the Next.js backend, evaluating trigger conditions stored in NotificationTriggerRepository at configurable intervals. Triggers are rule objects (event type, threshold, time window, target audience) persisted in the database and editable by Org Admins without deployments. The engine queries domain tables (assignments, certifications, activities) and emits events consumed by NotificationDispatcher. New scenarios are added by inserting trigger rules, enabling per-organization configuration of which scenarios are active and at what thresholds.