Sajjad Husain LawSajjad Husain Law Associates

Introduction

A single archaic word — "whence" — used to be the entire legal wall between a police informant and public exposure. In the Bharatiya Sakshya Adhiniyam, that word is gone, replaced by "when." Read literally, the replacement does not just modernise old English; it may quietly dismantle the very protection the provision existed to provide.

Section 131 of the Bharatiya Sakshya Adhiniyam, 2023 (BSA) sits between the two privilege clusters this run has covered — legal-advice privilege in Sections 132 to 134, examined in the previous three articles, and official/state communications in Section 130, taken up next. This piece walks through what may be the most consequential single-word drafting question anywhere in the new Act, why courts are being urged to read the text against its own plain wording, and what remains unresolved as of this writing.

Section 131 BSA and Section 125 IEA: One Word, Possibly the Wrong One

Section 125 of the Indian Evidence Act, 1872 protected a Magistrate, police officer, or revenue officer from being compelled to say "whence" — an old English word meaning "from where," or "from what source" — they got information about an offence. That word is what shielded a police informant's identity: the officer could refuse to reveal where a tip came from. Section 131 of the BSA, confirmed across independent bare-act sources, replaces "whence" with "when" — a word about timing, not source.

Deliberate Change or Drafting Error?

Legal commentary on this exact question has already emerged. An analysis published on LiveLaw — authored by a retired judicial officer, Justice P.V. Kunhikrishnan Pisharadi — frames the question directly: is Section 131's "when" a deliberate legislative choice, or a draftsman's error carried through the BSA's enactment process? The article's own conclusion leans firmly toward error. Reading "when" literally, it argues, produces an absurd result: a provision whose entire historical purpose was to protect informants from exposure would, on its face, no longer do that at all — while still oddly shielding the comparatively unimportant detail of what time an officer received a tip. Nothing in the BSA's legislative history or accompanying materials suggests Parliament intended to strip away informant protection specifically, making an unintentional slip the more plausible explanation than a deliberate policy reversal.

The Proposed Fix: Purposive Interpretation

The suggested remedy is not to wait for a formal amendment, but for constitutional courts to apply purposive interpretation — reading "when" as if it said "whence," or reading "when" in context to mean "from where," on the settled principle that where the literal meaning of a statutory provision produces absurdity or defeats the evident object of the provision, courts may correct the wording through interpretation rather than enforce an absurd result. This is a recognised, conservative interpretive tool, not a licence for courts to rewrite legislation freely — it applies specifically where the plain text cannot sensibly be reconciled with the provision's obvious purpose.

Why the Original Protection Exists at All

The rationale behind Section 125 IEA — and, on the purposive reading, Section 131 BSA — is straightforward: effective policing and revenue enforcement depend on members of the public being willing to report wrongdoing, and that willingness collapses if informants can be identified and exposed to retaliation. Shielding the officer from having to disclose the source of a tip is what makes it safe for a source to give one. The same logic extends to revenue officers investigating offences against public revenue — tax evasion and similar offences are often uncovered through tips from people with inside knowledge who would not come forward if their identity could be forced into the open in court.

The Common Law Roots of Informer Privilege

The principle Section 125 IEA codified in India traces to the English case Marks v. Beyfus, (1890) 25 QBD 494, where Lord Esher held that the identity of a police informer is protected as a rule of law, not merely a matter of judicial discretion — because if informants could be exposed through court proceedings, "these sources of information would dry up and the police would be hindered in their duty of preventing and detecting crime." The same judgment recognised one important limit even to this strong rule: where disclosing an informant's identity is genuinely necessary to establish an accused person's innocence, that competing public interest can prevail. Section 131's "whence"/"when" controversy sits directly on top of this century-old doctrine — the purposive-interpretation argument is, in substance, an argument that Parliament could not have meant to abandon a protection this deeply rooted without saying so far more clearly than a single quiet word substitution.

Worked Example One: The Purposive Reading Applied

A police officer is cross-examined at trial and asked to name the person who tipped them off about a planned robbery. Applying the purposive reading urged by commentators — treating "when" as meaning "whence" — the officer can decline to answer, exactly as they could have under Section 125 IEA. The informant's identity stays protected, and the provision does the work its heading, "Information as to commission of offences," suggests it should.

Worked Example Two: The Literal Reading's Absurd Result

The same officer, this time before a court applying Section 131's text literally, is asked the identical question — who was the informant? On a strictly literal reading, the section only protects the officer from having to say when the tip arrived, not from whom. The officer would have no textual basis to refuse naming the source, even though doing so exposes the informant to exactly the retaliation risk the provision was designed to prevent — the outcome commentators point to as evidence that "when" cannot have been the intended word.

Why This Matters in Practice

For police officers and revenue officers testifying about how they came to investigate an offence, the safest current practice is to resist disclosing an informant's identity and to be ready to argue the purposive interpretation explicitly if pressed, rather than assuming the statute's plain words will be read narrowly against them. For defence counsel probing the reliability of an investigation's origins, the unresolved textual question is itself a live argument — until a court rules definitively, there is a genuine textual basis to press for disclosure that would not exist under the old, unambiguous "whence" wording. For anyone drafting or briefing on this provision, precision matters: describing Section 131 as "unchanged from the old law" is not accurate, even if most commentators expect it to be applied as if it were.

Key Takeaways

1. Section 131 BSA replaces Section 125 IEA's word "whence" (source) with "when" (timing) — a confirmed textual change, not a search-result artifact.
2. Read literally, "when" would strip away the provision's core historical purpose of protecting a police or revenue informant's identity.
3. Legal commentary treats this as a likely drafting error and urges courts to apply purposive interpretation, reading "when" as "whence" to avoid an absurd result.
4. No court decision has yet definitively settled which reading governs — treat the purposive interpretation as the dominant view, not confirmed law.
5. The Explanation defining "revenue officer" is unaffected and applies regardless of how the "whence"/"when" question is ultimately resolved.

Conclusion

Section 131 is a reminder that even a single-word substitution in a routine-looking provision can put a core protective purpose at risk, and that courts and practitioners are left to reconcile literal text against evident intent until either a judgment or an amendment resolves it definitively. The next article in this run moves to another form of protected communication — official communications between government officers, examined in Section 130.