WhatsApp Screenshots in a PoSH Inquiry: What Makes Digital Evidence Reliable?

An Internal Committee reviewing WhatsApp screenshots should ask more than whether the words look inappropriate. It should establish what the material can reliably show, what remains disputed and whether the people affected have had a fair opportunity to explain it.

This guide proposes a practical approach to digital evidence in a PoSH inquiry. The preservation and assessment steps below are practitioner recommendations, not a compulsory forensic protocol or a substitute for the applicable inquiry procedure.

Start with the allegation the screenshot is meant to support

Before asking for more files, identify the point being examined. Is the screenshot offered to show a sexual remark, a repeated request after refusal, a threat linked to work, or a disclosure made to someone afterwards?

Record that purpose beside the item. A message describing an incident afterwards should prompt different questions from a message alleged to be the incident itself. Avoid treating every attachment as proof of every allegation.

Ungender’s guide to the Internal Committee’s quasi-judicial role explains the broader responsibility to assess material and explain findings.[3] This article concentrates on the narrower task of handling disputed digital records.

Preserve what was received before preparing working copies

Keep the submitted file unchanged in a restricted case folder. Record who supplied it, when it arrived, how it was received and whether the person captured it or received it from someone else. Give it a stable reference that can be used in questions and the report.

Make separate working copies for annotations, translations or necessary redactions. Label each change and retain the link to the submitted version. Do not overwrite an attachment with a clearer-looking image and lose the version originally considered.

Where relevant material remains accessible, ask the holder to preserve it without editing or deleting it. Consider a proportionate request for surrounding messages or a chat export, where available and lawfully obtainable. Explain what is needed and why; a request for every conversation on a personal phone is not a sensible default.

Do not ask HR colleagues to circulate the screenshot informally to find out what others think. Keep collection and assessment within the authorised process. For the earlier receiving stage, see Ungender’s first-day HR disclosure protocol, which separates preservation from an unofficial inquiry.[5]

Separate identity, completeness and meaning

Use distinct questions rather than one general demand to “authenticate the chat”:

• Identity: What supports the claimed connection between the account and the person? Ask about the number or account details and whether authorship is accepted or disputed, rather than stopping at the displayed contact name.
• Completeness: What happened immediately before and after the extract? Are there gaps, missing attachments or a reply whose original message is absent?
• Meaning: What does each party say the words referred to? Does a translation preserve the wording, tone and ambiguity of the original?

Request enough context to test the disputed point, not an unlimited personal history. If surrounding material contains unrelated private information, consider a controlled review and justified redactions. Preserve any context necessary for a meaningful response.

Hypothetical example: A screenshot shows “come to my room tonight.” The complainant describes an unwelcome personal invitation. The respondent says it concerned a group work discussion. The committee should examine relevant surrounding messages, the explanations and other available material. It should neither accept the explanation because it sounds possible nor reject it because the screenshot looks decisive in isolation.

Put the specific dispute to the parties

Ask the respondent which part is disputed: sending the message, the date, completeness, translation or the interpretation. A general denial should lead to focused questions. Ask the complainant to address relevant contradictions with the same care, without turning technical uncertainty into an accusation.

Section 11 of the PoSH Act provides for inquiry under applicable service rules where the respondent is an employee, or the prescribed procedure where such rules do not exist.[1] Its further proviso expressly provides an opportunity to be heard where both parties are employees.[1]

As a practical safeguard, identify the material proposed to be relied upon, provide a meaningful opportunity to respond and record the response. If a new version changes the picture, revisit the affected question before reaching a finding. Quietly substituting a later file leaves uncertainty about what was actually answered.

Do not confuse an evidence certificate with a reliability assessment

Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 addresses electronic-record admissibility and contains certificate requirements for evidence tendered by virtue of that section.[2] This article does not resolve its application to every IC proceeding or later court proceeding.

Before demanding a certificate as a condition of considering a screenshot, obtain advice on the applicable forum, procedure and rules. Equally, do not assume that preserving an image is all that later litigation may require. Plan preservation early where a separate proceeding is foreseeable.

Keep the practical assessment separate: who supplied the material, what supports its origin, what is missing and how the dispute was tested. A technical document should not replace the committee’s reasoning about the allegation.

Escalate technical questions selectively

If a disputed alteration or account-access question could materially affect a finding, consider whether an appropriately qualified specialist is needed. Define the question before commissioning work: comparison of two files is different from a request to recover missing material.

Agree the lawful access basis, permitted scope, secure transfer arrangements and recipients of the specialist’s output. Do not seek passwords or use another person’s logged-in session as a shortcut. Keep the specialist’s technical conclusions distinguishable from the committee’s assessment of the complaint.

If relevant material cannot be recovered, record the attempts and the remaining limitation. Section 14 of the PoSH Act expressly says that mere inability to substantiate a complaint or provide adequate proof need not attract action against the complainant.[1] Missing digital material should not be casually labelled fabrication.

Protect the record without preventing a fair response

Section 16 restricts disclosure to the public, press and media of specified complaint and inquiry information, including the identities of the parties and witnesses.[1] Do not use a workplace-wide chat, presentation or training session to discuss identifiable case screenshots.

For case handling, define authorised access and a controlled sharing method. Record which version was shared with whom. Decide retention and deletion through the applicable requirements and any preservation hold; do not invent a universal retention period or promise immediate deletion at closure.

Where a committee needs procedural support, Ungender’s PoSH advisory services include support for inquiries with fairness and due process.[4] Any technical evidence question should still receive an appropriately scoped response.

Write down what the screenshot establishes, and what it does not

For each material item, record its reference, the allegation it bears on, its source, the parties’ explanations, the checks undertaken and the unresolved gaps. Then explain the weight given to it alongside the other evidence.

Avoid a conclusion that says only “WhatsApp proof verified.” State what was checked. Distinguish an accepted message from a disputed attribution, and an incomplete record from a finding that someone fabricated it.

A useful final check is whether another reader can follow the route from the submitted material to the finding without guessing what the committee assumed.

General practitioner guidance. Check case-specific law, service rules and procedure before acting. The cited PoSH Act copy is dated 31 August 2021; the cited BSA edition is dated 6 October 2025. Neither is represented here as a newly consolidated October 2026 text.

Sources

1. https://www.indiacode.nic.in/bitstream/123456789/2104/1/A2013-14.pdf
2. https://www.indiacode.nic.in/indiacode/bitstream/123456789/20063/1/aa202347.pdf
3. https://www.ungender.in/internal-committee-quasi-judicial-role-posh
4. https://www.ungender.in/posh-compliance-services
5. https://www.ungender.in/hr-sexual-harassment-disclosure-first-24-hours