Alerts
Filterable table of every current alert on the left; select one to see its identity, why it matters (Risk & Impact), and the decision to make — the rest (map, threshold detail, forecast, history, verification) was removed from this page per direct product-owner feedback, 2026-08-04, to keep it to only what's necessary here. Placement of Alerts/Drafting & Dissemination/Thresholds as separate screens vs. tabs is deferred (reconciled-implementation-spec.md) — kept as three screens here.
How this works
A detected situation is auto-opened and confirmed here — this page handles the alert's own lifecycle (escalate, or manually resolve). The outgoing narrative/CAP text is then composed at Drafting and submitted for review; a different person approves or rejects it there (the composer can't approve their own words). Approval is what makes the alert disseminable — sending happens from Dissemination.
Who is responsible for each hazard/severity — release authority, response time — is set at Response Protocols.
Alerts sudden-onset · alert surface
An alert stays visible across every screen until someone acts on it — reviews it, rejects it, or drafts from it. Seeing it is not an action. Data-source health is a separate, lower-priority surface and never competes with this one.
| Alert | Affected area | Hazards | Severity | State | Review | Est. impact | |
|---|---|---|---|---|---|---|---|
| ALT-2026-0142 | Ambohidratrimo | Cyclone Flood | Severe | Escalated | Pending Review | 38,400 (est.) | Draft → |
| ALT-2026-0139 | Atsinanana | Cyclone | Watch | Open | Approved | 4,200 (est.) | Draft → |
| ALT-0098 | Boeny | Drought | Watch | Resolved | Approved | Peak 2026-06-30 | Example row only |
ALT-2026-0139 / ALT-0098: detail view not built for these example rows (static mockup, one full worked example) — every column above is still real content, not placeholder.
Slow-onset records not the alert surface
Drought and other slow-onset hazards are evaluated on a schedule and produce a bulletin, not a push alert. Their records are listed here for the analyst, and are deliberately kept off the notification bell and out of the queue above. Which section a record lands in follows the hazard's onset class on the hazard registry.
| Record | Area | Hazard | Severity | State | Cycle | Output |
|---|---|---|---|---|---|---|
| DRT-2026-0007 | Androy · Grand Sud | Drought | Watch | Open | 1 of 2 monthly cycles — awaiting confirmation | Monthly bulletin → |
Verification outcomes (toggle)
| Alert | Area | Hazard | Peak | Outcome | Resolved |
|---|---|---|---|---|---|
| ALT-0101 | Atsimo-Andrefana | Flood | Watch | Closed — no warning issued | 2026-07-04 |
A readiness trigger that does not confirm resolves with nothing released, and stays fully readable rather than being discarded — it is the evidence for whether a threshold is too sensitive. The opposite error, an event that occurred with no alert at all, is logged as a miss on Historical Events.
Select an alert from the table on the left to see its full detail here.
Alert ALT-2026-0142
Analamanga · Ambohidratrimo District · opened 2026-07-21 09:14
Workflow stage
Auto-detected 2026-07-21 09:14. A Rejected draft would branch off at the Approved step instead of continuing.
Trigger evidence
| Triggering value | Forecast river level 6.1 m · valid 2026-07-25 06:00 UTC |
| Threshold | Flood · Severe · ≥ 6.0 m v3 view → |
| Source | GloFAS EXT · base run 2026-07-24 06:00 UTC view → |
| Affected area | Ambohidratrimo District — resolved by spatial intersection of the forecast footprint with ADM2 boundaries v4 |
Risk & Impact
| Flood risk (INFORM) | Elevated |
| Cyclone risk | High |
| Population affected (est.) | 38,400 |
| Critical assets affected | 1 hospital, 4 schools, 2 bridges |
Estimate derived from the Flood/Cyclone Risk baseline — not a predictive model.
Auto-attached protocol — Flood / Warning
Release authority: Admin · SLA: 4h · full protocol console →
Ready to draft? Use the Draft → shortcut next to this alert in the table on the left.
Decision
Escalate/Override are only shown to Analyst/Admin roles.
Composing, commenting on and approving the alert's narrative happens on Drafting, not here.
Every action above is written to the audit log (actor, from→to, timestamp).
Once Resolved, a “Record verification” action becomes available here (forecast vs. observed, accuracy score, calibration notes).
Switch role via the header user menu's "Preview as (mockup only)" to see Approve/Escalate/Override.
History append-only
- 2026-07-21 09:14 · System — Detected (auto): Flood threshold v3 breached, Warning
- 2026-07-24 14:02 · System — Escalated (auto): Severity Warning → Severe, GloFAS 3-day forecast crossed the Severe threshold
- 2026-07-24 14:02 · System — Review status set to Pending Review, awaiting analyst
Every transition is recorded with actor, action and timestamp. Records cannot be edited or deleted, including this history itself. Full cross-entity log on System Health.