Back to Knowledge Management

Starter · Part of Knowledge Management

Ownership + staleness alerts

Available

Every article has an owner and a reviewer. A two-pass staleness sweeper flips articles to stale when they're past their expiry window and notifies the owner; if no action, the reviewer is notified next.

Handling PII During Verification flipped to stale by the nightly sweep — the article header shows the stale state badge, the Compliance category, the assigned Owner (Hannah Cabrera), the Reviewer (Aisha Diallo), and the past expiry date (May 5) that triggered the flip. Stale articles still serve agents with a 'needs review' badge so confidence is flagged; pass-2 of the sweep escalates to the reviewer if the owner doesn't act in time.
Handling PII During Verification flipped to stale by the nightly sweep — the article header shows the stale state badge, the Compliance category, the assigned Owner (Hannah Cabrera), the Reviewer (Aisha Diallo), and the past expiry date (May 5) that triggered the flip. Stale articles still serve agents with a 'needs review' badge so confidence is flagged; pass-2 of the sweep escalates to the reviewer if the owner doesn't act in time.

For the operator

KM lead sees a stale-article queue on the analytics page; ownership transfers are first-class (employee picker on the editor). The staleness sweeper does the chasing, not the lead — the lead works exceptions.

Business impact

Stale knowledge is the failure mode that kills KM programs in year two. Active ownership + automatic staleness alerts + escalation to reviewer turns the staleness problem from 'we know it's a problem' into 'the system runs itself'. The lead's time goes to authoring and review, not to chasing.

Ownership + staleness alerts — Knowledge Management — FrontLine Atlas | FrontLine