FRE 901(b)(9) Requires an Expert. FRE 902(13) and FRE 902(14) Don't.

Most digital evidence disputes come down to timestamps. Not whether the file exists. When it was created, when it was captured, and whether the system that recorded that moment can be explained to a court.

I built ProofLedger around that problem. Here's what I've learned about the authentication path.

The Default: FRE 901(b)(9)

FRE 901(b)(9) allows authentication of evidence produced by "a process or system that produces an accurate result." Courts are familiar with it. It's the rule most practitioners reach for when digital evidence needs authentication.

The cost is the foundation requirement. Someone has to establish that the process is reliable. Usually that's an expert. That expert can be challenged under Daubert on qualifications and methodology. In a contested case with a funded opponent, that's real risk and real cost.

For a single high-value matter, manageable. For claims teams handling volume, the overhead adds up.

What Changed in 2017

Two rules were added to the Federal Rules of Evidence that get less attention than they deserve.

FRE 902(13) covers records generated by an electronic process or system. FRE 902(14) covers data copied from an electronic device, storage medium, or file. Both allow authentication through written certification. No live testimony required.

The opposing party can still challenge. But that challenge happens through motion practice, not cross-examination. You're not scheduling an expert for every contested file. For litigation teams and claims departments handling volume, that distinction matters.

Both rules have been available since 2017. Most practitioners still default to 901(b)(9) out of familiarity. For documentation designed to be verifiable, the certification path is worth building toward.

Where Blockchain Timestamps Fit

A blockchain anchor creates a record that a specific file, identified by its SHA-256 hash, existed at a specific point in time. That record lives on a public ledger and can't be altered after the fact. The file itself stays on your device.

When challenged, the anchor can be authenticated under FRE 901(b)(9) as a record produced by a reliable process. Depending on how the documentation is structured, a written certification may also support authentication under FRE 902(13) without requiring live testimony.

The cryptography isn't the hard part. The documentation is. Having the hash, the anchor, and the chain-of-custody record in a form that can be presented and certified is what most teams skip when they're capturing evidence.

What It Looks Like in Practice

A claims team documents a roof before repairs are authorized. Photos are anchored at the time of capture. If coverage is disputed months later, the timestamp question is already answered. The anchor exists. The hash matches. The record shows the photos predated the repair, the dispute, and the filing.

A construction firm photographs site conditions at each project milestone. When a defect claim arrives two years later, the question isn't what the photos show. It's whether those conditions were documented before a specific date. The blockchain anchor answers that without scheduling an expert.

ProofLedger organizes evidence by case or matter, with loss dates and pre/post classification. That's not a technology decision. It's because that's how documentation gets used in a dispute.

The Authentication Path Is a Design Choice

If a timestamp on digital evidence gets challenged tomorrow, what's your path? If the answer is "we'd call an expert," it's worth asking whether FRE 902(13) or 902(14) might serve the same purpose with a written certification instead.

The rules exist. The question is whether the documentation was captured in a way that supports using them.