Explore
Flagship studies, sector briefs, and recurring reports, by topic.
Long-form data narratives that walk through an argument.
Recurring advisor series, from weekly reads to annual reviews.
The daily policy prescription, generated each morning.
Seven sector deep-dives: banking, trade, energy, agriculture, and more.
Ask the corpus: answers grounded in published work, with citations.
Grounding verified
Brahmaputra / Padma / Meghna monsoon stages above danger
The hazard is recurrent monsoon flooding driven by the country's three largest rivers. The curated characterization is direct: "Brahmaputra / Padma / Meghna monsoon stages above danger." When these rivers stand above their danger stages at the same time, the floodplains they drain are inundated together, which is the worst case for a deltaic country where most of the population and cropland sit on those plains.
Two facts make this urgent now. First, this is a Tier 1, short-horizon, event-driven hazard: it arrives on a monsoon clock, not a policy clock, so the window to prepare closes when the rains start. Second, the lead responsible body, the Ministry of Disaster Management and Relief (MoDMR), per the GovTwin entity registry, currently has no live indicator feeding this dashboard (the current state is null and the data status is "needs collector"). A Tier 1 hazard with no live signal means the government is reacting to floods after they crest rather than acting before. That gap, not the river itself, is the policy failure.
Build the collector first. Nothing downstream works without a live, trusted danger-stage reading, and once it exists every other action has an objective trigger to hang on. Next, write the trigger circular into the Standing Order on Disaster so thresholds are binding before the monsoon, not improvised during it. Then ring-fence the anticipatory-action line and pre-register eligible unions so money can move the day a trigger fires. The public feed comes last because it depends on a tracker the ministry already trusts. Done in this order, one collector unlocks pre-agreed triggers, which unlock pre-positioned money and a clear chain of command.
The binding constraint is institutional, not technical: gauge data sits with BWDB while response sits with MoDMR, and triggers only work if both honor the same numbers. Anticipatory cash also asks the treasury to release funds before visible damage, which cuts against an audit culture that pays after loss is proven. Politically, evacuation orders that fire on a forecast and then under-flood invite blame, so the trigger circular must protect officials who act on a valid signal. Without that cover, the safe choice stays "wait and see," which is exactly the failure this brief targets.
A Tier 1 monsoon hazard on the Brahmaputra, Padma, and Meghna is running with no live signal feeding MoDMR's decisions, and that blind spot, not the rivers, is what turns floods into disasters. Stand up the danger-stage collector first, bind pre-agreed triggers and anticipatory money to it, and the ministry shifts from cleaning up after the crest to acting before it.
Where this hazard bites hardest, ranked by population in the 100-year floodplain, population-weighted with WorldPop 2020. Source: multi-hazard exposure atlas (GloFAS, FABDEM, MODIS, ACAG).
| District | Division | population in the 100-year floodplain |
|---|---|---|
| Jhalokati | Barisal | 98.3% |
| Pirojpur | Barisal | 97.5% |
| Lakshmipur | Chittagong | 96.9% |
| Gopalganj | Dhaka | 96.4% |
| Barguna | Barisal | 96.1% |
| Barisal | Barisal | 96% |
| Madaripur | Dhaka | 94.8% |
| Shariatpur | Dhaka | 94.1% |
The figures and responsible bodies cited in this prescription are drawn from the platform's own data and the GovTwin registry listed below.
Drafted by an Opus writer grounded in the facts above. Where the prescription cites a figure, it is drawn from those facts. The diagnosis derives from the BDPolicyLab crisis taxonomy; the responsible body and budget from the GovTwin registry. Recommended actions are the think tank's policy judgment.