User story · Persona: ASHA, ASHA Supervisor, CHO, ANM. Every recipient role needs full notification coverage for the events that affect their work, so that the framework is operationally complete and not lopsided towards a few personas.

Implement the rest of the in-app triggers as one work unit. They all share the same scheduler-and-template plumbing, so building them together avoids repeated rework. Copy and cadence remain hardcoded; configurability arrives in Phase 3.

• ASHA · Submission reminder: For every ASHA who has not yet submitted for the current month, fire at the start of the submission window (read from the state-variant cut-off config). Repeat every 2 days (hardcoded default) until the ASHA submits or the window closes. Title: "Submit your monthly incentive claim". Body: month-year and last date of the window. Event type: "ASHA Submission Reminder".
• ASHA · Stage-change notifications: Fire when the ASHA-month transitions to Verified by Supervisor, Verified by CHO, Verified by ANM, or Eligible for SSD Processing. Title: "Your claim is now <stage label>". Body: short message confirming stage and next expected step. Event type: "ASHA Stage Change" with the new stage in the payload.
• Supervisor · Auto-routing alert: Fires once per Supervisor per cut-off cycle, the moment the configured Supervisor verification cut-off elapses while one or more ASHA-months are still Pending. Title: "Pending claims have been routed to CHO or ANM". Body: count of ASHA-months routed forward; note that the Supervisor's review of those is no longer required. Event type: "Supervisor Auto-routing Alert".
• CHO · Verification reminder with cadence: Fires the moment an ASHA-month arrives at the CHO stage (via Supervisor verification or auto-routing). If still Pending with CHO, repeat every 2 days until the CHO verifies or rejects, or the configured CHO cut-off elapses. Title: "Pending CHO verifications for <Month YYYY>". Body: consolidated count of ASHAs and activities pending CHO verification. Event type: "CHO Verification Reminder".
• ANM · Verification reminder with cadence: Fires the moment an ASHA-month arrives at the ANM stage (alternate path when CHO is unavailable, or via auto-routing). If still Pending with ANM, repeat every 2 days until the ANM verifies or rejects, or the configured ANM cut-off elapses. Title: "Pending ANM verifications for <Month YYYY>". Body: consolidated count of ASHAs and activities pending ANM verification. Event type: "ANM Verification Reminder".
• Affected modules: Notification service (five new event handlers, scheduler extensions). FLW Android app (notification panel surfaces in ASHA, Supervisor, CHO, ANM logins). Activity workflow service (emits stage-change and auto-routing events the notification service subscribes to).