FRE 902(13) Explained: How Electronic Evidence Authenticates Itself

Before December 1, 2017, every piece of electronic evidence offered in federal court needed a live foundation witness. Someone had to take the stand, describe the system that generated or stored the evidence, and testify that the system produced accurate results. For a surveillance video, that meant the IT administrator who maintained the camera system. For server logs, the system engineer. For a forensic disk image, the examiner who created it.

In practice, this meant flying witnesses across the country, scheduling depositions around their availability, and paying expert fees — often for testimony that went unchallenged. As the Advisory Committee recognized, "it is often the case that a party goes to the expense of producing an authentication witness and then the adversary either stipulates authenticity before the witness is called or fails to challenge the authentication testimony once it is presented."

That changed when Rules 902(13) and 902(14) took effect. These two amendments — modest in length, significant in consequence — created a pathway for electronic evidence to self-authenticate through written certification rather than live testimony.

What Rule 902(13) Actually Says

The full text of Rule 902(13) reads:

(13) Certified Records Generated by an Electronic Process or System. A record generated by an electronic process or system that produces an accurate result, as shown by a certification of a qualified person that complies with the certification requirements of Rule 902(11) or (12). The proponent must also meet the notice requirements of Rule 902(11).

That is the entire rule. Three sentences. But each clause does specific work.

"A record generated by an electronic process or system" — This defines the scope. Rule 902(13) covers records that are the output of an electronic process: server logs, automated reports, hash values computed by software, metadata extracted by forensic tools, timestamps generated by a database. The record must be generated by the system, not merely stored by it. A Word document saved to a hard drive is not "generated by" the file system — but the file system's metadata about that document (creation date, last modified timestamp, file path) is.

"that produces an accurate result" — The proponent must demonstrate that the electronic process reliably does what it claims to do. This is the substantive heart of the rule and maps directly to Rule 901(b)(9), which allows authentication through "evidence describing a process or system and showing that it produces an accurate result."

"as shown by a certification of a qualified person" — Instead of live testimony, a written certification suffices. The certifier must be "qualified" — meaning someone with sufficient knowledge of the electronic process to describe it and attest to its accuracy. This does not require a forensic expert. It means someone who understands how the system works.

"that complies with the certification requirements of Rule 902(11) or (12)" — The certification must follow the procedural format established for domestic business records (Rule 902(11)) or foreign business records (Rule 902(12)). This means compliance with 28 U.S.C. § 1746 — a written declaration under penalty of perjury.

"The proponent must also meet the notice requirements of Rule 902(11)" — The proponent must give all parties reasonable written notice in advance of trial that it intends to offer the evidence, and must make the evidence and the certification available for inspection.

What the Advisory Committee Notes Tell Us

The Advisory Committee Notes to Rule 902(13) make several points that practitioners should internalize.

First, the rule works through Rule 901(b)(9). The Notes state: "The Rule specifically allows the authenticity foundation that satisfies Rule 901(b)(9) to be established by a certification rather than the testimony of a live witness." This is the mechanism — the certification is not some new form of authentication but rather the existing 901(b)(9) foundation delivered in writing instead of from the witness stand.

Second, the certification must contain substantive information. A proponent must present "a certification containing information that would be sufficient to establish authenticity were that information provided by a witness at trial." The Notes continue: "If the certification provides information that would be insufficient to authenticate the record if the certifying person testified, then authenticity is not established under this Rule." In other words, the certification cannot be conclusory. A statement that "the evidence is authentic" without describing the process is insufficient — just as that bare assertion would be insufficient if given as live testimony.

Third, the rule addresses only authentication. The Notes emphasize that the reference to Rules 902(11) and (12) is "only to the procedural requirements for a valid certification." There is no intent to require, or permit, a certification under Rule 902(13) to prove the requirements of a hearsay exception such as Rule 803(6) (business records). Authentication and hearsay are separate hurdles. A 902(13) certification gets you past the first one. You still need independent grounds for the second.

Fourth, the opponent retains all other objections. The Notes state that the opponent "remains free to object to admissibility of the proffered item on other grounds — including hearsay, relevance, or in criminal cases the right to confrontation." Self-authentication under 902(13) does not make evidence admissible. It makes evidence authenticated. The distinction matters.

The Certification Requirements

Gregory P. Joseph, in his 2018 analysis published on the Southern District of Texas website, breaks the certification requirements into substantive and procedural components. Joseph — a former member of the Advisory Committee on the Federal Rules of Evidence (1993–99) and past president of the American College of Trial Lawyers — provides what is arguably the most authoritative practitioner-level treatment of these rules. His analysis, together with the comprehensive scholarly treatment in Hon. Paul W. Grimm, Daniel J. Capra & Gregory P. Joseph, "Authenticating Digital Evidence," 69 Baylor L. Rev. 1 (2017), forms the foundation for understanding the certification requirements.

Substantive Requirements

1. Qualifications of the certifier. The person signing the certification must have sufficient knowledge of the electronic process or system to describe how it works. This is not a credentials test — there is no requirement for a computer science degree or forensic certification. The certifier must simply know enough about the system to provide the information that a witness would provide at trial. A paralegal who manages evidence in a platform and understands its upload, hashing, and storage processes can be a qualified person. So can the platform provider's technical lead.

2. Description of the process or system. The certification must explain what the system does and how it does it. For an evidence management platform, this means describing how files are uploaded, how cryptographic hashes are generated, how files are stored, and what access controls exist. The description must be specific enough that a reasonable person could evaluate whether the system produces accurate results.

3. Attestation of accuracy. The certifier must state that the process or system produces an accurate result. This is the 901(b)(9) foundation — the same substantive showing that would be required of a live witness, now reduced to writing.

4. Non-conclusory content. The certification must contain actual information, not bare conclusions. "The system is reliable" is insufficient. "The system computes a SHA-256 cryptographic hash at the time of upload, stores files in encrypted cloud storage with access logging, and verifies file integrity by comparing the current hash against the original hash at the time of retrieval" is the kind of specificity the rule requires.

Procedural Requirements

1. Compliance with 28 U.S.C. § 1746. The certification must be a written declaration under penalty of perjury. The statute prescribes specific language: "I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on [date]." This carries the same legal weight as sworn testimony — a false certification is punishable as perjury.

2. Reasonable written notice. The proponent must give all parties reasonable written notice before trial of the intent to offer the evidence under Rule 902(13). What constitutes "reasonable" depends on the circumstances. Joseph suggests that pretrial and scheduling orders should address how far in advance of trial the certification and evidence must be provided — sound advice that eliminates ambiguity.

3. Evidence available for inspection. Both the evidence itself and the certification must be made available to all parties for inspection sufficiently in advance of their introduction. This is not a mere formality. As the Advisory Committee Notes observe, "a challenge to the authenticity of electronic evidence may require technical information about the system or process at issue, including possibly retaining a forensic technical expert; such factors will affect whether the opponent has a fair opportunity to challenge the evidence given the notice provided."

The Procedural Flow

Putting it together, the 902(13) procedural flow looks like this:

1. Generate the evidence through a reliable electronic process or system that you can describe and attest to.
2. Prepare the certification — a written declaration under penalty of perjury from a qualified person, describing the process and attesting to its accuracy.
3. Serve written notice on all parties that you intend to offer the evidence as self-authenticating under Rule 902(13).
4. Make the evidence and certification available for inspection with sufficient time for the opposing party to review and, if necessary, retain a technical expert.
5. Offer the evidence at trial or in a filing. If the opposing party does not challenge authenticity, the evidence is admitted without a foundation witness. If they do challenge, the court determines sufficiency under Rule 104(a).

How Rule 902(14) Complements Rule 902(13)

Where Rule 902(13) addresses records generated by an electronic system, Rule 902(14) addresses copies of electronic data authenticated through digital identification — most commonly, hash values.

The full text of Rule 902(14) reads:

(14) Certified Data Copied from an Electronic Device, Storage Medium, or File. Data copied from an electronic device, storage medium, or file, if authenticated by a process of digital identification, as shown by a certification of a qualified person that complies with the certification requirements of Rule 902(11) or (12). The proponent also must meet the notice requirements of Rule 902(11).

The Advisory Committee Notes to Rule 902(14) specifically discuss hash values and their role in authenticating digital copies. The Notes explain: "Today, data copied from electronic devices, storage media, and electronic files are ordinarily authenticated by 'hash value.' A hash value is a number that is often represented as a sequence of characters and is produced by an algorithm based upon the digital contents of a drive, medium, or file."

The Notes then make the critical point: "If the hash values for the original and copy are the same, it is highly improbable that the original and copy are not identical." This language — "highly improbable" — is the evidentiary standard the Advisory Committee endorsed for hash-based authentication.

Under 902(14), a qualified person certifies that they checked the hash value of the proffered copy and confirmed it was identical to the original. The certification describes the hashing process and identifies the algorithm used. The Notes also anticipate future developments, stating that the rule "is flexible enough to allow certifications through processes other than comparison of hash value, including by other reliable means of identification provided by future technology."

In practice, Rules 902(13) and 902(14) work together. Rule 902(13) authenticates the output of the evidence management system — the hash logs, the access records, the chain of custody documentation. Rule 902(14) authenticates the evidentiary files themselves — the video, the photograph, the document — by confirming through hash comparison that the copy offered is identical to the original collected.

What This Means in Practice

The practical impact is straightforward. Before 2017, authenticating a piece of electronic evidence in federal court required either a stipulation from opposing counsel or a live witness. If opposing counsel would not stipulate — and in adversarial litigation, they often will not — the proponent had no choice but to produce a witness. For a forensic examiner, that meant $3,000 to $5,000 per appearance, travel costs, and scheduling constraints that could delay proceedings.

Under Rules 902(13) and 902(14), the same attorney can now authenticate the same evidence with a written certification. The qualified person does not need to appear. The certification is served in advance, the evidence is made available for inspection, and unless the opposing party affirmatively challenges authenticity, the evidence comes in without testimony.

But the certification must be substantive. Courts will reject conclusory certifications that state "the evidence is authentic" without describing the underlying process. The certification must contain the same substantive information that a witness would provide on the stand — how the system works, what it does, and why its output is accurate. The difference is the delivery mechanism (paper instead of testimony), not the substance.

Joseph notes another practical consideration: the possibility of combining a Rule 902(11) certification (business records) with a Rule 902(13) certification to address both authentication and the business records hearsay exception in a single document. This is efficient practice when the electronic record also qualifies as a business record — which many evidence management system outputs do.

Key Cases to Know

Rules 902(13) and 902(14) did not emerge in a vacuum. They are the legislative response to nearly two decades of case law grappling with digital evidence authentication. Three cases are essential background.

Lorraine v. Markel American Insurance Co., 241 F.R.D. 534 (D. Md. 2007)

Magistrate Judge Paul W. Grimm wrote a 101-page opinion rejecting virtually all digital evidence offered by both parties — emails, spreadsheets, and web-based records — because neither side properly authenticated any of it. The opinion is the most comprehensive judicial analysis of the Federal Rules of Evidence as applied to electronically stored information. Judge Grimm systematically walked through Rules 901, 902, and the hearsay exceptions, concluding that attorneys routinely fail to lay proper foundation for digital evidence.

Lorraine established that authentication of digital evidence requires affirmative proof that the evidence is what it purports to be — producing a file and asserting it is authentic is insufficient. The case became the roadmap for digital evidence authentication that practitioners, and the Advisory Committee itself, would follow for the next decade. Judge Grimm later co-authored the definitive scholarly treatment of these issues in Grimm, Capra & Joseph, "Authenticating Digital Evidence," 69 Baylor L. Rev. 1 (2017) — an article that directly informed the 2017 amendments.

United States v. Vayner, 769 F.3d 125 (2d Cir. 2014)

The Second Circuit reversed a conviction because the government failed to properly authenticate a social media profile page. The government offered a printout of a VKontakte (Russian social media) profile page attributed to the defendant, but provided no evidence that the defendant actually created or controlled the profile. The court held that the mere fact that a profile bears someone's name and photograph is insufficient to authenticate it as that person's profile — anyone can create a page using another person's information.

Vayner underscored the authentication gap for internet-sourced evidence. A printout or screenshot, without evidence linking it to a particular person or establishing when and how it was captured, fails under Rule 901(b)(1) and (b)(4). The case demonstrates exactly the kind of authentication challenge that a proper 902(13) certification — describing the process of capture, the system that generated the record, and the integrity of the output — is designed to resolve.

United States v. Lizarraga-Tirado, 789 F.3d 1107 (9th Cir. 2015)

The Ninth Circuit addressed whether a Google Earth satellite image with a digitally placed marker (tack) constituted hearsay. The court drew a distinction between the satellite imagery itself — machine-generated output not subject to hearsay analysis because no human "declarant" was involved — and the location marker, which could have been placed by a human user. The machine-generated imagery was not hearsay; the marker required authentication as to who placed it and when.

Lizarraga-Tirado is significant for 902(13) practice because it clarifies that machine-generated records (the core of 902(13)'s scope) are not hearsay. A system that automatically computes a hash value, generates a timestamp, or records an IP address is producing machine output, not a human statement. This means that for many types of electronic evidence authenticated under 902(13), the hearsay objection — the other major admissibility hurdle — does not apply at all.

Conclusion

Rules 902(13) and 902(14) are tools. They do not change what authentication requires — they change how the foundation is delivered. The substance remains the same: a qualified person must describe a reliable electronic process and attest that it produces accurate results. The delivery mechanism shifts from courtroom testimony to written certification under penalty of perjury.

Practitioners who understand these rules have a clear procedural advantage. They authenticate evidence earlier, spend less on foundation witnesses, and arrive at trial with evidence that opposing counsel must affirmatively challenge rather than passively exclude. Eight years after the amendments took effect, there is no reason to default to live testimony for authentication that a properly prepared certification can accomplish.