Pakistan Affairs Model Answer – Indus Waters Treaty

This is an original model answer for a Pakistan Affairs / Current Affairs question. It is not an FPSC official answer, and this site is not affiliated with FPSC. Subject: Pakistan Affairs (Compulsory, 100 marks) / Current Affairs crossover. Question type: 20-mark subjective question. Time: ~35–40 minutes. Length: 900–1,100 words + outline. This question rewards structure: treaty design + survival + current threats + verdict. Do not write a one-sided history essay. Do not memorise word-for-word. Learn structure, facts, and evaluation, then write in your own words under timed conditions.

Question

Critically examine the Indus Waters Treaty (1960) as a model of water diplomacy. Why has it survived wars, and what threatens it now?

Outline

1. Introduction — thesis: IWT survived because of design, not goodwill — but design is now under strain.
2. What the Treaty does — division, commission, dispute ladder.
3. Why it survived wars — legal clarity, third-party role, mutual interest, technical insulation.
4. What threatens it now — hydropower disputes, trust deficit, climate, population, 2025 abeyance announcement.
5. Critical evaluation — is it still a model? Three tests: compliance, adaptability, legitimacy.
6. Way forward — technical, legal, climate, and diplomatic steps.
7. Conclusion — restate verdict.

Model Answer

Introduction

The Indus Waters Treaty (IWT), signed in 1960 between India and Pakistan with the World Bank as broker, is often called one of the world’s most successful water agreements. It has survived two full wars, a limited war, and decades of hostility. That survival is remarkable — but it is often misunderstood. The Treaty did not survive because India and Pakistan trusted each other. It survived because it was designed to work without trust: clear division, a permanent commission, and a graded dispute ladder. That design is now under its greatest strain, from hydropower disputes, climate change, and — in 2025 — India’s announcement that it was holding the Treaty in abeyance. The question is no longer whether the Treaty was a good model. It is whether a 1960 design can handle 2026 pressures.

What the Treaty Does

The Treaty divides the six rivers of the Indus system. The three eastern rivers — Ravi, Beas, Sutlej — were allocated to India. The three western rivers — Indus, Jhelum, Chenab — were allocated to Pakistan, with limited Indian rights for domestic use, irrigation, and run-of-the-river hydropower (with design constraints on storage and flow). Pakistan, as the lower riparian, received the larger volume, while India, as the upper riparian, accepted restrictions on its use of the western rivers.

Two institutions matter. First, the Permanent Indus Commission, with one Commissioner from each side, meets regularly, exchanges flow data, and inspects projects. Second, a three-step dispute ladder: questions go to the Commission; if unresolved, to a Neutral Expert; if still unresolved, to a Court of Arbitration. This ladder matters for exams: it explains why disputes over dams did not immediately become crises — they had a technical channel.

The Treaty also included transitional arrangements and international finance for Pakistan’s replacement works (link canals, dams) to replace eastern-river supplies. In short, it was not just a legal text. It was a bargain: division + data + dispute process + finance.

Why It Survived Wars

1. Legal clarity. Division by river, not by percentage, reduced daily bargaining. Each side knew which rivers were “its” rivers. Ambiguity breeds disputes; clarity contains them.

2. Technical insulation. The Commission kept engineers talking even when politicians were not. Water data, inspections, and project notifications continued through crises. Technical channels do not resolve political hostility, but they prevent a technical disagreement from becoming a war trigger.

3. Mutual interest. Both sides gained. Pakistan secured its irrigation lifeline. India secured its eastern rivers and avoided a permanent water war. The World Bank’s involvement gave both sides a face-saving reason to sign and a third party to appeal to.

4. Graduated disputes. Baglihar, Kishanganga, and other dam disputes tested the Treaty, but the Neutral Expert / arbitration mechanisms gave each side a way to lose a point without losing face. A treaty that cannot handle losing a case cannot survive.

The lesson for a model answer: survival was institutional, not sentimental. Do not write “both countries respected the Treaty.” Write “the Treaty was designed so it did not need respect to function.”

What Threatens It Now

1. Hydropower and design disputes. India’s run-of-the-river projects on the western rivers — notably Kishanganga and Ratle — have led to disputes over design, storage, and flow timing. Pakistan argues that pondage, spillways, and drawdown affect its flows. India argues its designs comply with the Treaty. The technical details matter, but the political point matters more: each new project reopens the same distrust, and the dispute ladder has become slower and more contested, including parallel proceedings (Neutral Expert and Court of Arbitration) that risk conflicting outcomes.

2. Trust deficit and securitisation. Water is increasingly framed as a security issue, not a technical issue. After terrorist attacks, water is invoked in public debate as leverage. That framing makes compromise harder: a technical concession looks like a security concession. Once water is securitised, engineers lose room to negotiate.

3. Climate change and variability. The Treaty was written for a more predictable climate. Glacial melt, erratic monsoons, floods, and droughts now make flows less predictable. Both countries face water stress from population growth, urbanisation, and inefficient irrigation. A treaty that allocates rivers cannot allocate a changing climate. Without joint work on forecasting, storage, efficiency, and flood management, climate stress will increase disputes.

4. The 2025 abeyance announcement. In 2025, after the Pahalgam attack, India announced it was holding the Treaty in abeyance. Pakistan has maintained the Treaty remains binding and cannot be suspended unilaterally. The legal status is contested and evolving — a model answer should state the positions without taking a legal stance: India cites security concerns and a need to revisit the Treaty; Pakistan cites the Treaty’s binding character and the absence of a unilateral suspension clause. The practical effect is uncertainty: data exchange, Commission meetings, and project notifications are disrupted. Uncertainty itself is a threat, because the Treaty’s value was predictability.

5. Domestic politics and implementation. On both sides, water is used in domestic politics. Projects are announced for political effect, not just technical need. Media narratives simplify a complex treaty into “water war” headlines. That makes quiet technical resolution harder.

Critical Evaluation — Is It Still a Model?

Apply three tests: Compliance: Has the Treaty been complied with? Largely yes for six decades, with disputes channelled through its mechanisms — a strong record by global standards. Adaptability: Can it handle climate, hydropower, and new demands? Weakly. It has no climate clause, no joint watershed management, and no mechanism for revising allocations as conditions change. Legitimacy: Do both sides still see it as fair? Declining. Pakistan sees upper-riparian projects as encroachment. India sees the Treaty as constraining its legitimate use and out of date.

Verdict: The IWT remains a model of how to design a water treaty — division, commission, graded disputes — but it is no longer a model of how to sustain one under climate and geopolitical stress. Its design was excellent for 1960. It needs updating for 2026, without discarding what worked.

Way Forward

1. Restore technical channels: resume Commission meetings, data exchange, and inspections, even during political crises. Technical insulation is the Treaty’s core strength.
2. Clarify the dispute ladder: avoid parallel proceedings that produce conflicting rulings. One track at a time, with clear jurisdiction.
3. Add a climate and data annex: joint forecasting, flood/drought early warning, and shared work on efficiency and storage — without reopening the core division.
4. Make hydropower design transparent: early notification, shared design data, and independent technical review for western-river projects.
5. De-securitise water in public discourse: treat water as a shared resource to be managed, not a weapon to be threatened.
6. Pursue dialogue on updating the Treaty by mutual consent — not unilateral suspension. Any revision must be negotiated, not imposed.

Conclusion

The Indus Waters Treaty survived wars because it was built for distrust: clear division, a permanent commission, and a dispute ladder. Those features remain valuable. But survival is not success if the Treaty cannot adapt to climate change, hydropower, and a collapsed trust environment. The 2025 abeyance announcement is a warning: even a successful treaty can be undermined if its mechanisms are bypassed. The path forward is not to abandon the Treaty, but to restore its technical channels and update it by mutual consent — preserving what made it a model, while making it fit for a climate-stressed, water-scarce future.

Examiner Tips

Gets marks: Clear thesis, returned to in conclusion. Precise treaty facts (1960, six rivers, eastern/western division, Commission, three-step ladder). Balanced analysis (why it survived + what threatens it). Distinguishing positions on 2025 abeyance without taking a legal stance. Concrete way forward.

Loses marks: Vague history with no treaty mechanics. One-sided blame. Treating announced projects as completed. Confusing eastern/western rivers. No outline, no conclusion, or conclusion contradicting introduction. Presenting contested 2025 legal status as settled.

Data Bank (use 3–4)

• Signed 1960, Karachi; brokered by World Bank; signed by Jawaharlal Nehru (India) and Ayub Khan (Pakistan).
• Eastern rivers (to India): Ravi, Beas, Sutlej.
• Western rivers (to Pakistan, with limited Indian use): Indus, Jhelum, Chenab.
• Institutions: Permanent Indus Commission (one Commissioner each side).
• Dispute ladder: Commission → Neutral Expert → Court of Arbitration.
• Key disputes: Baglihar, Kishanganga, Ratle (design/storage/flow issues).
• 2025: India announced holding Treaty in abeyance after Pahalgam attack; Pakistan maintains Treaty is binding and cannot be suspended unilaterally. Legal status contested and evolving — state positions, do not assert a settled legal outcome.
• Caution: Do not cite a single “water share %” as exact — the Treaty divides rivers, not percentages. Do not invent flow volumes.

This is an original model answer written for csspastpapers.pk. It is not an FPSC official answer, and this site is not affiliated with FPSC.

See also: Pakistan Affairs Past Papers, Current Affairs Past Papers, CSS Syllabus, and Pakistan Affairs CPEC model answer.