Two cyclone seasons a year: making the Ministry of Disaster Management and Relief ready before each Bay of Bengal window

Diagnosis

Bangladesh is exposed to tropical cyclones in two distinct windows each year: the Bay of Bengal pre-monsoon season and the post-monsoon season (per the curated note). This is not a single annual event to plan around but a recurring twice-yearly hazard, which means readiness cannot be a one-time push. It has to be a cycle that resets and is re-verified before each window opens.

The lead responsible body is the Ministry of Disaster Management and Relief (MoDMR), per the GovTwin entity registry. The decision problem MoDMR owns is therefore not whether a cyclone will form, but whether the warning, evacuation, shelter, and recovery chain is fully primed at the start of each season and stays primed through it. Because this is a nowcast, event-driven hazard, the binding question is operational latency: how many hours and how many handoffs sit between a Bay of Bengal track forecast and a fisherman, a coastal farmer, or a char household actually moving to safety.

The current_state indicator is not populated in the context, which is itself a finding: MoDMR cannot manage what it does not measure in near real time. A standing, observable readiness signal is the first thing to build.

Recommended actions

1. Pre-season readiness certification. Owner: MoDMR. Mechanism: a binding ministry circular that requires every coastal district disaster management committee to certify, before each pre-monsoon and post-monsoon window opens, that designated cyclone shelters are stocked, accessible, and staffed, and that volunteer rosters are current. Observable signal: a completed certification on file for every coastal district before each season, with named gaps and a closure date.
2. Last-mile warning hardening. Owner: MoDMR, working through the existing coastal volunteer warning programme. Mechanism: a standing operating procedure that pushes the same forecast simultaneously through multiple channels (volunteers, mosque and community announcement, mobile alert) so no single channel is a single point of failure. Observable signal: drop in the time between an official warning being issued and confirmed receipt at union level, measured in a post-event after-action log.
3. Shelter and evacuation route audit. Owner: MoDMR with local government engineering counterparts. Mechanism: a programme budget line for inspecting and repairing shelter structures and access roads, prioritised by the coastal districts with the longest evacuation distances. Observable signal: shrinking list of shelters flagged unusable, and shorter worst-case evacuation distances year over year.
4. Pre-authorised post-event relief and payout. Owner: MoDMR. Mechanism: a trigger-based relief protocol, agreed in advance, that releases relief and cash support automatically once a cyclone of a defined severity makes landfall, rather than after a slow damage-assessment loop. Observable signal: relief reaching affected unions within a pre-committed number of hours after landfall, tracked per event.
5. Standing readiness dashboard. Owner: MoDMR. Mechanism: a live operational indicator (the missing current_state) that aggregates certification status, shelter availability, and volunteer coverage into one number leadership can see daily during each window. Observable signal: the indicator exists, updates in season, and is reviewed at ministry level.

Sequencing (first 12 months)

Start with the readiness dashboard and the pre-season certification circular, because every other action needs a baseline and an accountability hook. Certification surfaces the real gaps in shelters, volunteers, and warning reach; the dashboard makes those gaps visible to leadership. With gaps named, sequence the shelter and route audit to the next budget cycle and stand up the warning SOP and the pre-authorised payout protocol ahead of the following season window. By month twelve MoDMR should have run at least one full season under the new certification-and-dashboard loop and have an after-action log to tighten the next cycle.

Risks and constraints

The binding constraints are fiscal and institutional, not technical. Shelter repair and pre-authorised payouts compete with other claims on a tight relief budget, so the trigger protocol must be sized to what can actually be released, not to aspiration. Certification depends on coastal district committees and volunteers who are not full-time staff, so the circular must come with clear accountability or it becomes a paper exercise. Finally, multi-channel warning only works if the channels are maintained between seasons; the recurring twice-yearly nature of the hazard is the main reason readiness decays, and it is also the main argument for institutionalising the cycle rather than mobilising ad hoc each time.

Bottom line

Bangladesh faces a Bay of Bengal cyclone risk in both pre-monsoon and post-monsoon seasons, so MoDMR's task is to keep the warning, shelter, and payout chain certified and visible before each window rather than scrambling at landfall. The first move is a standing readiness indicator plus a binding pre-season certification circular, because everything else depends on knowing, in advance and in real time, where the gaps are.