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
Dhaka aquifer drop driving subsidence
The curated problem note is direct: the Dhaka aquifer drop is driving subsidence. Land subsidence is a slow-onset, structural hazard, meaning the surface sinks gradually as the city pumps water out of the ground faster than the aquifer can recharge. The mechanism is physical and cumulative: as the water table falls, the soil and clay layers beneath the city compact, and that compaction is largely permanent. Unlike a flood that recedes, subsided land does not bounce back when pumping pauses.
This matters now for three reasons. First, the damage is irreversible at the margin, so every year of unchecked drawdown raises the long-run cost and forecloses options. Second, subsidence compounds every other Dhaka risk it touches: it lowers the effective ground level against river and tidal flooding, cracks foundations and buried utilities, and degrades drainage gradients. Third, there is no current published indicator value in the grounded context (current_state is null) and the data status is flagged as needing a collector. That data gap is itself a policy failure: a slow hazard that is not measured is a hazard that is allowed to accumulate silently. The lead responsible body is the Ministry of Environment, Forest and Climate Change (MoEFCC), supported by the Bangladesh Meteorological Department, the Department of Environment, and the Ministry of Disaster Management and Relief.
Start with action 1: monitoring. Nothing else can be targeted, enforced, or evaluated without a measured baseline, and the context shows there is none today. The monitoring network is the keystone: it converts a vague slow hazard into a managed quantity, it identifies which zones get the drawdown cap (action 2), it ranks which abstractors to switch first (action 3), and it supplies the risk map for planning (action 4). In parallel, MoEFCC should draft the critical-zone circular so it can be issued the moment the first quarter of data lands, rather than waiting a full year.
The binding constraint is that groundwater is the path of least resistance for water supply, so a drawdown cap without a credible surface-water substitute simply creates shortages and political backlash. Sequencing substitution alongside the cap is therefore not optional. Enforcement is the second constraint: caps and permits mean little if metering is unverified, which is why the monitoring network and abstractor metering must precede penalties. Finally, MoEFCC sets climate and environment policy but does not directly run water supply or building approvals, so delivery depends on genuine interagency coordination with the supporting bodies named in the context rather than ministry fiat.
Dhaka is sinking because it is draining its own aquifer, and the damage compounds and largely will not reverse. MoEFCC should treat measurement as the first move, then cap drawdown and substitute surface water in the worst zones, because a slow hazard left unmeasured is a hazard chosen.
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.