Informational Fresh jira_story: GOV-150

Lesson 1 of 4 — Notifications and reminders for tasks

Cross-Cutting & Hardening · Source: Jira Story GOV-150 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Nudge owners about overdue work via in-app and email.

Why it matters

Governance stalls without reminders; nudges keep work moving.

Where this lives

Runs in the Customer AI Governance platform (components: platform). A reminder job notifies the task owner in-app and by email on the next run. Learn teaches this read-only.

Workflow

Given an overdue task
When the next run fires
Then the owner gets an in-app and email reminder

Worked example

A task goes overdue. Who should be reminded, and how?

The accountable owner, in-app and by email — not the whole tenant.

Acceptance criteria (authoritative — GOV-150)

Given an overdue task, when the next run fires, then the owner gets an in-app and email reminder.

Common pitfalls

Notifying everyone instead of the accountable owner.

Knowledge check

Scenario: A task goes overdue. Who should be reminded, and how?
Look for: The accountable owner, in-app and by email — not the whole tenant.

Key concepts

task reminders
in-app + email
owner targeting

For the AI Tutor

Summary: Nudge owners about overdue work via in-app and email.
When to use: teaching or answering questions about "notifications and reminders for tasks".
When NOT to use: escalating to executives (that is Phase 2, GOV-202).
Key concepts: task reminders, in-app + email, owner targeting.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-150's acceptance criterion.

Module: LEARN-MOD-005 (Cross-Cutting & Hardening)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-029