Safety alerts

Example data. No member has ever spoken to a persona, so no safety event here is real. Level-3 events are alerted within 5 minutes and the clock runs to acknowledgement, not to sending.

5 events · 3 unacknowledged · worst SLA state first, oldest first within it
CaseLevelMemberPersonaAlertedSLAExcerpt
SE-44723Member EPersona c7d0Never sent
No assigned counselor, so there was nobody for it to reach. H-10
breached
Escalation due. Nowhere defined to send it — RFD-0022
Withheld — the member did not grant transcript access
SE-44653Member DPersona 0b945.0 h agobreachedExcerpt withheld in the example data.
SE-44713Member APersona a31f22 min agobreached
Not acknowledged
Escalation due. Nowhere defined to send it — RFD-0022
Withheld — the member did not grant transcript access
SE-44703Member CPersona 51ae2 min agowaiting
Not acknowledged
Withheld — the member did not grant transcript access
SE-44683Member BPersona 77c240 min agometExcerpt withheld in the example data.

What this screen cannot do

Acknowledgement cannot be recorded here. The action log takes an actor and refuses an empty one, and nothing in this build establishes who is looking at the screen — authentication was left open at S24, and H-10 means no licensed counselor has ever had an account.

A button that marked an alert acknowledged without recording who did it would satisfy the SLA figure above and tell nobody anything. The figure is the point: it is the one number that distinguishes an alert that arrived from an alert that was sent.

Where an unanswered alert goes

Nowhere. There is no on-call rota, no second recipient and no fallback anywhere in this system. An alert past its deadline with nobody acknowledging it is reported as escalating and the destination is null, because inventing one here would be worse than having none.

RFD-0022 — open, no safe default, past its decide-by date. It needs H-06 and H-10, and it is the reason this column can say an escalation is due without saying where to.