Defensible Document Provenance: File Databases

In historical document collections, provenance is not an administrative detail. It is the foundation of defensibility. A file database is the tool that makes provenance trackable, searchable, and explainable.

Why Provenance Matters in Litigation

Provenance (the documented history of where a record came from, who handled it, and how it entered the collection) determines whether a record can be authenticated, relied on, and defended under scrutiny.

For historical records, provenance is especially important because the records may have passed through multiple custodians, repositories, filing systems, and formats over decades or centuries. Without a clear provenance trail, the reliability of the record is open to question.

What a File Database Does

A file database is a structured record of every source in the collection. It tracks the origin of each file or group of files: the repository, the archive, the access date, the condition of the records, any restrictions on access, and the chain of custody from source to collection.

The file database is not the same as the document database. The document database tracks individual records within the collection (their coding, metadata, and classification). The file database tracks the sources those records came from: their provenance.

Source Tracking

Effective source tracking means documenting not only what was found, but where it was found, when it was accessed, what condition it was in, and what the access terms were. For historical records, source tracking also includes noting the institutional context of the repository: who created the records, for what purpose, and what filing system or organizational logic they followed.

Source tracking creates a verifiable link between the record in the collection and the archive it came from. Without it, the record exists in the collection without a documented origin.

Chain of Custody

Chain of custody documents what happened to the record after it left the repository: who handled it, how it was copied or digitized, how it was transferred into the collection, and who had access to it during the process.

For historical records, chain-of-custody documentation is often incomplete because the records may have changed hands multiple times before reaching the legal team. A file database helps identify and document those gaps, rather than leaving them invisible.

Provenance Gaps

Not every provenance question can be answered. Some records have uncertain origins. Some repositories have incomplete finding aids. Some access conditions limit what can be verified. What matters is that the gaps are identified, documented, and explainable, not hidden or ignored.

A file database that identifies provenance gaps explicitly is more defensible than one that presents every record as if its origin is certain when it is not.