RTI Finality Clauses Do Not Bar Article 226 Review of CIC Orders; “No Policy Number” Requests Require Reasonable Identifiers

1. Introduction

The Delhi High Court (Division Bench) in AMBIKA GUPTA v. CPIO LIC OF INDIA (LPA 113/2026, decided on 08.04.2026) considered the interface between (i) the “final and binding” character of Central Information Commission (“CIC”) decisions under the Right to Information Act, 2005 (“RTI Act”), (ii) the statutory bar on courts under Section 23 of the RTI Act, and (iii) the High Court’s constitutional power of judicial review under Article 226.

The appellant (an individual RTI applicant) sought a complete list of all LIC policies in which she was the insured person “at any point in time” without furnishing policy numbers. LIC’s CPIO declined on the basis that its “base” is the policy number; the First Appellate Authority upheld that view. On second appeal, the CIC issued directions/advice that LIC must develop systems enabling retrieval even where policy numbers are unavailable. LIC challenged the CIC order by writ petition, and the learned Single Judge substantially treated CIC’s system-improvement directions as advisory, while permitting the applicant to file a fresh application with supporting particulars.

The intra-court appeal raised two principal issues: (a) whether Section 19(7) (“final and binding”) and Section 23 (bar on court proceedings) block writ review; and (b) whether LIC can be compelled, through RTI, to locate all policies merely on a broad request unaccompanied by workable identifiers.

2. Summary of the Judgment

  • The Division Bench dismissed the appeal and upheld the Single Judge’s approach.
  • The Court held that statutory finality under Section 19(7) and the jurisdictional bar under Section 23 of the RTI Act do not restrict the High Court’s plenary writ jurisdiction under Article 226.
  • On the merits, the Court endorsed the view that an insured person may seek policy information even without policy numbers, but must supply reasonable personal identifiers (e.g., name, date of birth, address, mobile/email, NEFT-registered bank account) enabling retrieval from LIC’s vast database.
  • The Court accepted the practical constraint that LIC cannot be expected to search across 27 crore policies and a database stated to exceed 72 crore entries without adequate identifying particulars.
  • The Court also agreed that CIC’s directions regarding building or upgrading systems were appropriately treated as non-mandatory/advisory in the circumstances, while leaving open that courts may issue directions in a future case if necessity arises.

3. Analysis

3.1 Precedents Cited

The judgment does not cite any prior judicial precedents by name. Instead, the Court anchors its conclusion in constitutional structure—particularly the doctrine that judicial review is a basic feature and that statutory “finality” or “bar” clauses cannot oust constitutional remedies.

Although no case law is referenced, the reasoning follows a well-established line of constitutional jurisprudence: provisions that declare decisions “final” or attempt to limit court proceedings generally cannot exclude the High Court’s Article 226 jurisdiction, even if they may influence the manner or self-restraint with which courts exercise review.

3.2 Legal Reasoning

(A) Maintainability of writ proceedings notwithstanding Sections 19(7) and 23 of the RTI Act

  • Section 19(7) RTI Act: The appellant argued that because CIC decisions are “final and binding,” the Single Judge could not have modified or diluted the CIC’s order unless there was a jurisdictional error of the certiorari type. The Division Bench rejected this, holding that statutory finality does not bar Article 226 review.
  • Section 23 RTI Act: The appellant argued that the RTI Act bars courts from entertaining proceedings “in respect of any order” made under the Act. The Court held this bar may apply to ordinary civil proceedings, but cannot operate as an impediment to Article 226, because judicial review is a basic feature of the Constitution.
  • Writ jurisdiction described as “plenary”: The Court emphasised the breadth of Article 226 and reaffirmed that statutes cannot remove constitutional remedies through finality clauses.

(B) RTI disclosure versus feasibility of retrieval in large legacy databases

  • The Court treated the dispute as practical as well as legal: LIC’s records are policy-number centric and cover huge volumes, including older, potentially non-digitized policies.
  • The Court accepted that an insured person may not know the policy number (especially if insurance was taken without their knowledge), but held that other identifiers are presumed to be within the person’s knowledge and are necessary for retrieval.
  • The Court thus validated a middle path:
    • No absolute requirement of a policy number; but
    • A legitimate requirement of reasonable supporting particulars to enable search and avoid impossible burdens.
  • The Court also endorsed the Single Judge’s concern that indiscriminate disclosure of policy details to third parties could be dangerous; sensitive policy data, if released improperly, could jeopardize the insured’s safety. Even though the appellant sought information about her own policies, this observation supported the need for careful handling and verification through identifying details.

(C) Characterisation of CIC directions as “advisory” and judicial restraint

  • The CIC had directed LIC to take steps to ensure disclosure even without policy numbers and “advised” development of a robust identification system.
  • The Court agreed with the Single Judge that, given LIC’s submission that a system already exists (capable of retrieving policies using personal identifiers), and given the practical challenges of legacy/non-digitised data, it was appropriate to refrain from issuing mandatory technology/system-building directions.
  • Importantly, the Court did not foreclose future intervention: it recorded that if necessity arises later, appropriate directions could be issued. This preserves judicial oversight while avoiding over-intrusive operational mandates on a public insurer in the present factual matrix.

3.3 Impact

(A) On RTI litigation and CIC “finality”

  • The ruling reinforces that CIC finality (Section 19(7)) is not constitutional finality; CIC orders remain open to judicial review under Article 226. Practically, this makes clear that parties (including public authorities) may still approach the High Court against CIC orders, notwithstanding Sections 19(7) and 23.
  • At the same time, the judgment signals that the High Court will examine the substance and feasibility of CIC directions—particularly where directions resemble broad administrative reform mandates rather than case-specific disclosure adjudication.

(B) On RTI requests to large data custodians (insurers, banks, utilities)

  • The decision effectively recognizes a principle of reasonable identifiability: information must be disclosed under RTI if not exempt, but the applicant must provide sufficient identifiers to make retrieval possible where databases are massive.
  • For future cases, public authorities may rely on this reasoning to resist overly broad RTI requests that require near-impossible searches—while still being obligated to assist where the seeker provides workable particulars.
  • Applicants, conversely, gain clarity that they are not confined to “policy number only” requests; they can seek information using personal details, but should be prepared to provide a structured set of identifiers.

(C) On systemic directions under RTI

  • The judgment reflects judicial caution in turning RTI adjudication into an enforceable blueprint for enterprise-wide database modernization. CIC’s encouragement for robust systems is not rejected in principle, but the Court treats it as context-dependent and, here, non-mandatory.
  • Nonetheless, the Court’s “open door” observation (that directions may be issued later if necessity arises) may motivate public bodies to improve systems proactively to avoid future mandatory orders in a more compelling case.

4. Complex Concepts Simplified

  • Writ jurisdiction under Article 226: The High Court’s constitutional power to review actions/orders of public bodies for legality, fairness, and constitutional compliance. It is not granted by a statute and therefore cannot be taken away by a statute.
  • Judicial review as a “basic feature”: A foundational constitutional principle—Parliament (or a State legislature) cannot remove the courts’ power of judicial review through ordinary legislation.
  • Section 19(7) RTI Act (“final and binding”): Means final within the RTI appellate structure (CPIO → FAA → CIC), but does not eliminate constitutional remedies.
  • Section 23 RTI Act (bar on court proceedings): Prevents ordinary suits or applications challenging RTI orders, but does not bar the High Court’s Article 226 powers.
  • Writ of certiorari: A form of judicial review traditionally used to quash unlawful orders of inferior tribunals/authorities. The Court here clarifies that even where a statute declares an order final, the High Court can still review it under Article 226.
  • “Advisory” directions: Non-binding guidance, as opposed to enforceable mandatory commands. The Court accepted that CIC’s system-improvement directions operated more as advice in the given context.

5. Conclusion

The Division Bench’s decision in AMBIKA GUPTA v. CPIO LIC OF INDIA cements two practical constitutional propositions in RTI administration: (i) RTI “finality” and “bar” clauses do not oust Article 226 judicial review; and (ii) RTI entitlements must be implemented in a manner that is workable for large-scale record custodians—an insured person can obtain policy information without a policy number, but must supply reasonable identifying particulars to enable retrieval.

By balancing access-to-information goals with feasibility, privacy, and operational realities, the judgment is likely to influence how CIC directions are framed (more case-specific and enforceable) and how RTI applicants structure requests (with identifiers that make retrieval practicable), especially in domains involving massive legacy datasets like insurance.