An electronic-record certificate needs a source trail, not just an attachment

A digital file can be easy to forward and hard to explain. When a party relies on computer output in an Indian proceeding, a handover should explain what the record is, where it came from, how it was produced, and who can speak to the process. Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 (BSA) connects admissibility conditions with a certificate and Schedule. A last-minute certificate detached from the evidence workflow may leave questions unanswered.

Begin with the record and the claim

Identify the proposition the evidence is meant to support: a message, transaction entry, video segment, server log, or cloud export. Preserve the record as received or held, with a working copy where appropriate. Record source account or system, custodian, collection date/time and time zone, relevant period, export settings, and transformations. Keep the unedited source available where lawful and practicable; a printed output may omit relevant context or metadata.

This is operational discipline, not a claim that every screenshot is invalid or every case requires one forensic procedure. Under BSA sections 61 and 62, electronic form alone is no ground to deny admissibility, while contents may be proved under section 63. Section 63(1) addresses computer output subject to statutory conditions; it does not make a file trustworthy merely because it is electronic.

Map the process to section 63

Section 63(2) asks whether the device was regularly used for the activity under the concerned person’s lawful control; whether relevant information was regularly fed into it in the ordinary course; whether malfunction or outage affected the record or its accuracy; and whether the output reproduces or derives from information so fed. Section 63(3) recognizes that a function may involve multiple computers, networks, resources or intermediaries, treating the devices used for it as one computer for this purpose.

Convert those questions into a source trail: name the system/device/service and its role, period, ordinary workflow, known interruptions, and path from source to output. Distinguish the collector’s actions from system or provider processes. State unknowns and who may verify them; do not fill template blanks with guesses.

Use both parts of the Schedule carefully

Section 63(4) calls for a certificate with the electronic record each time it is submitted for admission. It must identify the record and production method, give appropriate particulars of devices, and address section 63(2) matters. It must purport to be signed by the person in charge of the computer/device or management of relevant activities, as appropriate, and an expert. A matter may be stated to the signer’s best knowledge and belief.

The Schedule structures the task. Part A, for the party, asks for source type and identifiers, lawful control, routine activity and operation, and whether the source was owned, maintained, managed or operated by the signer. It provides for hash values, algorithm, an enclosed report, signature, date, time and place. Part B, for the expert, repeats source/device and hash details and asks for name, designation, signature and date/time/place. The fields are not permission to guess. A hash can help show whether a copy changed after hashing; it does not alone prove who created the record, source accuracy or meaning.

Separate provenance, admissibility and weight

Provenance describes origin, custody and transformation. Admissibility asks whether material can be received under applicable rules, including section 63 where invoked. Weight is its persuasiveness after evaluating reliability, context and competing evidence. A coherent certificate and matching export may strengthen the handover, but do not guarantee admission or prove every assertion. Address gaps with clarification or additional evidence, not generic assurances.

Section 170(2) preserves the Indian Evidence Act, 1872 for an application, trial, inquiry, investigation, proceeding or appeal pending immediately before the BSA came into force. Confirm the applicable regime before selecting a form or importing older section 65B practice; do not assume old decisions transfer word-for-word.

Hypothetical handover and checklist

Suppose, hypothetically, a company relies on an email export showing that a purchase instruction was sent. Its team records the mailbox custodian, export method/time, date range, source location, PDF conversion, and hash. The person responsible for the mailbox process checks ordinary operation and flags an outage. The party and an appropriately engaged expert review which Schedule fields they can honestly complete. This preparation predicts no ruling.

Before transfer to counsel, check:

  • The offered record and the fact it is said to prove are precisely identified.
  • The source, device/service, relevant period, export steps and transformations are documented.
  • The section 63(2) conditions are addressed with verified facts and candid limits.
  • Part A and Part B responsibilities, identifiers, hash report and signatures are reviewed against the actual Schedule.
  • The preserved source, working copy, certificate and hash report are linked and versioned.
  • The team has checked whether section 170 savings or another evidentiary route affects the matter.

A certificate should travel with an intelligible record of how the output came to exist. That source trail helps assess provenance and statutory fit, leaving admissibility and weight to the court. Accuracy is more useful than confidence unsupported by system history.

Get in touch

Please keep your message brief and avoid sharing confidential information.
Scroll to Top