The Chenab river at Ramban, Jammu and Kashmir, India. Photo Credit: Shoaib tantray111, Wikipedia Commons
June 27, 2026
By Umair Khan
India’s reported push on the Chenab–Beas Link Tunnel, plus sediment management works around the Salal Dam, is not really just “another project” in the ordinary way. It feels like a meaningful jump in South Asia’s water-security atmosphere. In practice, these efforts can’t be separated from the broader political setting, because they are moving forward even as India says the Indus Waters Treaty is in abeyance, while Pakistan insists the treaty stays legally binding, operational, and protected from any one‑sided suspension. That mismatch, is basically the core trouble.
The Chenab is not only a Himalayan River, it’s one of the western rivers under the Indus Waters Treaty. It is assigned primarily to Pakistan, alongside the Indus and Jhelum. India still holds limited permissions for domestic use, non-consumptive use, agricultural use, and treaty-compliant hydropower generation, but those exceptions do not hand India a blank cheque to reshape what happens downstream in the river system. So any plan that redirects water from the Chenab basin into the Beas basin brings up immediate legal problems, technical constraints, and strategic risks all at once.
The proposed Chenab–Beas Link Tunnel feels especially sensitive, because it’s not only some dam-design argument, or a technical disagreement. It is also, reportedly, about an inter-basin transfer, from the upper Chenab system toward the Beas system which is an eastern river assigned to India. India might call it a diversion of “surplus” water, but that wording is kind of legally heavy and hydrologically loaded. In a basin run by treaty, surplus cannot be declared in a one-sided way by the upstream state. What looks like surplus up top may actually be seasonal necessity lower down, particularly for irrigation scheduling, canal command management , groundwater replenishment, flood pulses, sediment movements, and ecological continuity too.
Pakistan’s concern, honestly, isn’t just emotional alarmism. It’s rooted in how the treaty is structured. The western rivers are the backbone of Pakistan’s agriculture and food security. The Chenab supports one of the most important irrigation zones in Pakistani Punjab. Any upstream ability to regulate, delay, divert, or more or less manipulate flows, spills over beyond engineering. It changes sowing timing, crop yields, livestock arrangements, rural earnings and food pricing. And in a country already dealing with climate stress, water insecurity isn’t some distant strategic risk. It is a direct economic and social threat.
The Salal Dam component adds another layer of concern, like seriously. India says sediment management is needed to restore day to day operational efficiency and well, technically they are not wrong. Sedimentation is a real challenge in Himalayan hydropower systems. Reservoirs on steep, sediment heavy rivers lose capacity over time, and then infrastructure deterioration drifts into the electricity generation side. Still the treaty question isn’t whether sediment management is useful, at all. The real point is whether these works are planned, notified, designed, and operated in a way that matches India’s obligations on western rivers.
And this is where transparency kind of becomes decisive. If India withholds hydrological data, avoids meaningful notification or skips treaty mechanisms while expanding hydraulic control infrastructure, Pakistan can reasonably see the projects as part of a coercive hydro political pattern. Data sharing is not some diplomatic favour you hand out politely. It’s a safety requirement for downstream flood forecasting, agricultural planning, reservoir operations and disaster preparedness. In a climate volatile basin, denying or delaying the information can be just as destabilising as messing with physical flows.
The timing of these projects is equally troubling. Infrastructure development during normal treaty compliance would still require technical scrutiny. Infrastructure development during declared “abeyance” carries a very different political signal. It suggests that India is using the period of suspended engagement to accelerate control over western river systems while weakening Pakistan’s ability to monitor, object or seek timely remedies through established channels. That is why the issue has moved from water management to strategic coercion.
The Permanent Court of Arbitration’s findings reinforce Pakistan’s position. The Court has emphasized that India must generally let the waters of the western rivers flow for Pakistan’s unrestricted use, except where the treaty expressly allows otherwise. This principle directly challenges any expansive Indian interpretation that treats western rivers as available for unilateral engineering optimization. India cannot replace treaty limits with its preferred technical convenience or domestic political needs.
The international community should not treat the Chenab developments as some kind of bilateral irritant. It’s bringing up a bigger issue for global transboundary water governance, I mean, really, beyond the usual diplomacy. If an upstream state can suspend a treaty politically, withhold data advance diversion infrastructure, and then just normalize pressure on a downstream state, then every shared river basin starts looking vulnerable to this same kind of coercive pressure. And the precedent would not stop at South Asia, it would travel much further.
Pakistan’s response should be disciplined, and also evidence based, not emotional. It should push for full project disclosure, complete hydrological data, clear design details, proper treaty notifications, and third party legal scrutiny where it’s needed. Islamabad should also steer away from exaggerated claims that can easily get pushed back on technically. Instead it should concentrate on the strongest points: the Chenab is a western river; inter-basin diversion creates serious treaty concerns; India cannot decide surplus unilaterally; and no political declaration can simply suspend treaty obligations.
India’s Chenab projects are not only concrete, tunnels, and turbines. They are also a real test of whether international law can still restrain upstream leverage. In the Indus Basin water is food, livelihood, and national stability all at once. Turning the Chenab into an instrument for pressure would endanger millions, and it would erode one of the world’s most important water sharing frameworks. The responsible path here is pretty straightforward: restore treaty compliance, resume data sharing, submit the projects for legal scrutiny, and keep shared rivers away from political coercion.
About Umair Khan
Umair Khan has a Master's in International Relations from Quaid-e-Azam University and is an independent researcher from Islamabad, Pakistan.
View all posts by Umair Khan →
By Umair Khan
India’s reported push on the Chenab–Beas Link Tunnel, plus sediment management works around the Salal Dam, is not really just “another project” in the ordinary way. It feels like a meaningful jump in South Asia’s water-security atmosphere. In practice, these efforts can’t be separated from the broader political setting, because they are moving forward even as India says the Indus Waters Treaty is in abeyance, while Pakistan insists the treaty stays legally binding, operational, and protected from any one‑sided suspension. That mismatch, is basically the core trouble.
The Chenab is not only a Himalayan River, it’s one of the western rivers under the Indus Waters Treaty. It is assigned primarily to Pakistan, alongside the Indus and Jhelum. India still holds limited permissions for domestic use, non-consumptive use, agricultural use, and treaty-compliant hydropower generation, but those exceptions do not hand India a blank cheque to reshape what happens downstream in the river system. So any plan that redirects water from the Chenab basin into the Beas basin brings up immediate legal problems, technical constraints, and strategic risks all at once.
The proposed Chenab–Beas Link Tunnel feels especially sensitive, because it’s not only some dam-design argument, or a technical disagreement. It is also, reportedly, about an inter-basin transfer, from the upper Chenab system toward the Beas system which is an eastern river assigned to India. India might call it a diversion of “surplus” water, but that wording is kind of legally heavy and hydrologically loaded. In a basin run by treaty, surplus cannot be declared in a one-sided way by the upstream state. What looks like surplus up top may actually be seasonal necessity lower down, particularly for irrigation scheduling, canal command management , groundwater replenishment, flood pulses, sediment movements, and ecological continuity too.
Pakistan’s concern, honestly, isn’t just emotional alarmism. It’s rooted in how the treaty is structured. The western rivers are the backbone of Pakistan’s agriculture and food security. The Chenab supports one of the most important irrigation zones in Pakistani Punjab. Any upstream ability to regulate, delay, divert, or more or less manipulate flows, spills over beyond engineering. It changes sowing timing, crop yields, livestock arrangements, rural earnings and food pricing. And in a country already dealing with climate stress, water insecurity isn’t some distant strategic risk. It is a direct economic and social threat.
The Salal Dam component adds another layer of concern, like seriously. India says sediment management is needed to restore day to day operational efficiency and well, technically they are not wrong. Sedimentation is a real challenge in Himalayan hydropower systems. Reservoirs on steep, sediment heavy rivers lose capacity over time, and then infrastructure deterioration drifts into the electricity generation side. Still the treaty question isn’t whether sediment management is useful, at all. The real point is whether these works are planned, notified, designed, and operated in a way that matches India’s obligations on western rivers.
And this is where transparency kind of becomes decisive. If India withholds hydrological data, avoids meaningful notification or skips treaty mechanisms while expanding hydraulic control infrastructure, Pakistan can reasonably see the projects as part of a coercive hydro political pattern. Data sharing is not some diplomatic favour you hand out politely. It’s a safety requirement for downstream flood forecasting, agricultural planning, reservoir operations and disaster preparedness. In a climate volatile basin, denying or delaying the information can be just as destabilising as messing with physical flows.
The timing of these projects is equally troubling. Infrastructure development during normal treaty compliance would still require technical scrutiny. Infrastructure development during declared “abeyance” carries a very different political signal. It suggests that India is using the period of suspended engagement to accelerate control over western river systems while weakening Pakistan’s ability to monitor, object or seek timely remedies through established channels. That is why the issue has moved from water management to strategic coercion.
The Permanent Court of Arbitration’s findings reinforce Pakistan’s position. The Court has emphasized that India must generally let the waters of the western rivers flow for Pakistan’s unrestricted use, except where the treaty expressly allows otherwise. This principle directly challenges any expansive Indian interpretation that treats western rivers as available for unilateral engineering optimization. India cannot replace treaty limits with its preferred technical convenience or domestic political needs.
The international community should not treat the Chenab developments as some kind of bilateral irritant. It’s bringing up a bigger issue for global transboundary water governance, I mean, really, beyond the usual diplomacy. If an upstream state can suspend a treaty politically, withhold data advance diversion infrastructure, and then just normalize pressure on a downstream state, then every shared river basin starts looking vulnerable to this same kind of coercive pressure. And the precedent would not stop at South Asia, it would travel much further.
Pakistan’s response should be disciplined, and also evidence based, not emotional. It should push for full project disclosure, complete hydrological data, clear design details, proper treaty notifications, and third party legal scrutiny where it’s needed. Islamabad should also steer away from exaggerated claims that can easily get pushed back on technically. Instead it should concentrate on the strongest points: the Chenab is a western river; inter-basin diversion creates serious treaty concerns; India cannot decide surplus unilaterally; and no political declaration can simply suspend treaty obligations.
India’s Chenab projects are not only concrete, tunnels, and turbines. They are also a real test of whether international law can still restrain upstream leverage. In the Indus Basin water is food, livelihood, and national stability all at once. Turning the Chenab into an instrument for pressure would endanger millions, and it would erode one of the world’s most important water sharing frameworks. The responsible path here is pretty straightforward: restore treaty compliance, resume data sharing, submit the projects for legal scrutiny, and keep shared rivers away from political coercion.
About Umair Khan
Umair Khan has a Master's in International Relations from Quaid-e-Azam University and is an independent researcher from Islamabad, Pakistan.
View all posts by Umair Khan →
No comments:
Post a Comment