Reports & Bulletins
Two distinct surfaces on this one screen (reconciled-implementation-spec.md, Reports & Bulletins): a public-facing Published Reports & Bulletins list below, and the Analyst/Admin-only Drafting & Report Distribution queue further down (renamed from "Drafting & Dissemination" per DD-126 — that term is reserved for the alert-side screens, now split into screen-drafting.html and screen-dissemination-alerts.html per DD-136/DD-137). The per-report workspace itself is a separate page (DD-143), reached via "Open →" in the queue below — same drill-down-detail-page split already applied to Drafting (DD-138), to keep this screen to one thing at a time.
Published Reports & Bulletins public — no sign-in required
| Title | Type | Published | Audience | Area | Download |
|---|---|---|---|---|---|
| Weekly situation report — Analamanga | Weekly | 2026-07-24 | Public bulletin | Analamanga | PDF · HTML |
| Flash bulletin — Ambohidratrimo cyclone/flood | Flash | 2026-07-21 | Public bulletin | Ambohidratrimo | PDF · HTML |
| Monthly outlook — all regions | Monthly | 2026-07-01 | Government authority | All regions | PDF · HTML |
Only Approved & Published/Sent output appears here — Draft and Pending Review items never do.
Drafting & Report Distribution queue (Analyst/Admin view)
| Type | Areas | Status | Updated | |
|---|---|---|---|---|
| Flash | Ambohidratrimo | Pending Review | 2026-07-21 | Open → |
| Weekly | Analamanga | Approved | 2026-07-20 | Example row only |
| Monthly | All regions | Sent | 2026-07-01 | Example row only |
Flash/Ambohidratrimo: full worked example (static mockup convention) — every column above is still real content, not placeholder.
Report type & where it comes from
The four types in FR-22, mapped to what produces them. This is the output path for slow-onset hazards — they never appear on the alert surface, so a scheduled bulletin is their warning, not a summary of one.
| Type | Produced for | Triggered by | Cadence |
|---|---|---|---|
| Weekly situation | Routine reporting, and slow-onset hazards on a weekly evaluation cadence | Schedule | Weekly |
| Monthly situation | Slow-onset hazards — drought's monthly evaluation cycle lands here, including the cycle that confirms persistence and escalates | Schedule | Monthly |
| Quarterly situation | Routine reporting regardless of whether a hazard is present | Schedule | Quarterly |
| Flash | Sudden-onset hazards — drafted from an open alert | Event — from the alert queue | Per event |
Advisory content can be nested inside either. A routine situation report is still produced when no hazard is present — the schedule does not depend on there being something to warn about.
Each type carries both a current conditions section from indicator data and a what’s expected section from forecast data, never merged. For drought, “what’s expected” is the long-range seasonal outlook (L-08) — the part that buys the lead time.
New draft setup — Report settings
1 selected — Ambohidratrimo. Region and Commune scoping follow the same admin-level fallback as the Dashboard (FR-17).
- Audience / Language — change on the draft directly; it re-renders the same content through a different template (FR-25). No regeneration.
- Narrative text — edit the sections inline while status is Draft (FR-23).
- Same data, fresh draft — “Regenerate from this snapshot” on the detail page re-runs generation on the identical snapshot (FR-26).
- Different districts / type / period — that is a different data snapshot, so it is a new Generate (this form, pre-filled from the current draft), not an edit of the existing one — a report stays tied to the one snapshot it was built from (FR-26).
- Once Submitted / Approved, settings and content are locked; a change means a new draft, and the prior review history is preserved (FR-31).