Informational Fresh jira_story: GOV-202

Lesson 2 of 3 — Escalation and overdue board alerts

Automated Review Cadence · Source: Jira Story GOV-202 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Escalate overdue reviews to executives.

Why it matters

Overdue governance needs visibility at the right altitude.

Where this lives

Runs in the Customer AI Governance platform (components: workspace). An overdue timer escalates to the Executive after N days. Learn teaches this read-only.

Workflow

Given an overdue review
When it stays overdue
Then it escalates to the Executive after N days

Worked example

A review is one day overdue. Should the Executive be alerted yet?

Not until the N-day threshold is crossed — escalation is deliberate, not immediate.

Acceptance criteria (authoritative — GOV-202)

Given an overdue review, when it stays overdue, then it escalates to the Executive after N days.

Common pitfalls

Escalating immediately instead of after the configured N-day threshold.

Knowledge check

Scenario: A review is one day overdue. Should the Executive be alerted yet?
Look for: Not until the N-day threshold is crossed — escalation is deliberate, not immediate.

Key concepts

escalation
overdue threshold
executive alert

For the AI Tutor

Summary: Escalate overdue reviews to executives.
When to use: teaching or answering questions about "escalation and overdue board alerts".
When NOT to use: opening the cycle (that is GOV-201).
Key concepts: escalation, overdue threshold, executive alert.

Completion criteria

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

Module: LEARN-MOD-006 (Automated Review Cadence)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-034