Rights and contracts
Legal data document provenance: prove each file's source before licensing
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
To establish legal data document provenance before licensing, trace every document to the system and matter it was exported from, record who wrote it and in what capacity, identify the instrument that authorizes reuse, fix the controlling version and its dates, and log a counsel-run privilege and confidentiality screen. Documents whose source or authority cannot be shown stay out of the dataset.
Provenance trail
Legal data document
Key takeaways
- Legal records mix authors inside one matter, so provenance has to be recorded per document or per tightly defined class.
- The source category sets the default: court edicts are usually easiest, client and counterparty material usually hardest.
- Every row needs a reuse authority from a record, such as a confidentiality clause or documented consent; an empty field means exclusion.
- Log the privilege screen like a privilege log entry: outcome, basis category and reviewer, never the protected content.
- Hash files at screening and at packaging so the delivered file can be shown to be the one counsel reviewed.
How do you establish where a legal document came from before licensing it?
Build one evidence row per document, or per tightly defined document class, before anything is offered. The row names the system the file was exported from, the matter or contract it belongs to, the author and the capacity in which they wrote it, the version that controls, and the instrument that permits reuse. A counsel-run screen for privilege and client confidentiality is recorded on the same row, along with who approved inclusion.
The test is simple to state and strict in practice: if the row cannot be completed from records the company already holds, the document is excluded or held. A contract repository that looks complete often fails this test for drafts received by email, scanned amendments with no execution date, and files copied between matters.
Legal documents need more than a generic data inventory because their authorship is mixed. One matter folder can hold a court order, a filing written by opposing counsel, a client's own spreadsheet and an internal memo, and each of those carries a different answer to who controls reuse.
Why a folder path is not proof of origin
A document management path records where a file sits today, not how it got there. A redline saved under the company's matter folder may be a counterparty's draft that arrived as an email attachment, was edited by in-house counsel and saved again. The path makes all of that look like the company's own work.
The W3C PROV ontology gives a useful vocabulary for separating these facts. It distinguishes entities (the document versions), activities (drafting, receiving, executing, exporting) and agents (the people and organizations responsible), and it treats derivation, one entity made from another, separately from attribution, an entity ascribed to an agent. A provenance row for a negotiated contract should record both: this executed version was derived from that counterparty draft, and that draft is attributed to the other side.
The Data & Trust Alliance Data Provenance Standards make the same point for datasets as a whole, with fields for source, origin, generation dates and collection method. The legal version of the exercise applies that discipline at the level of the individual document, because rights can change from one file to the next inside a single matter.
Who wrote it, and in what capacity, decides what can be reused
Sort documents by source category first, because the category sets the default treatment. The table below is a starting classification; counsel confirms each default for the jurisdiction and the agreements involved.
- Court material: the U.S. Copyright Office's Compendium says it will not register government edicts such as judicial decisions, legislative enactments and administrative rulings, which is why court-issued text is usually the easiest category to clear.
- Client material: the ABA's comment on Model Rule 1.6 frames the core duty as not revealing information relating to the representation without the client's informed consent, and that duty reaches information from any source, not only privileged communications.
| Source category | Typical examples | Who controls reuse | Default treatment |
|---|---|---|---|
| Court-issued material | Opinions, orders, docket entries | Generally not protected by copyright as a government edict; sealing and protective orders still apply | Candidate after a sealing and protective-order check |
| Filings written for the company | Briefs, motions, pleadings drafted by in-house or outside counsel | The company and its counsel, subject to the engagement terms and client confidentiality | Hold until the engagement terms and privilege screen are recorded |
| Filings by other parties | Opposing briefs, third-party declarations | Their authors; public filing does not transfer rights | Exclude unless counsel confirms a reuse basis |
| Executed agreements | Signed contracts, amendments, statements of work | Both parties, often bound by confidentiality clauses | Candidate only where the agreement's confidentiality terms permit or consent is documented |
| Counterparty drafts and redlines | Markups received during negotiation | The counterparty for its text; the company for its own edits | Usually exclude; keep only the company's own clause language |
| Internal templates and clause libraries | Form contracts, playbooks, fallback clauses | The company, unless built from a licensed form | Strong candidate once the source of each form is recorded |
| Licensed research and forms | Content copied from paid legal databases or form publishers | The publisher, under its license | Exclude unless the license allows this use |
| Client or customer documents | Records supplied to counsel or to a legal operations team | The client, plus confidentiality duties of counsel | Exclude unless documented client consent covers the use |
The source and rights evidence inventory
Use the inventory below as the working template. Each field should be filled from an existing record, with the record's reference stored alongside it, so a reviewer can check the claim without asking anyone to remember. Example values are illustrative.
- Fill the row from records, not recollection: every value carries a pointer to the export log, signature page, consent or approval it came from.
- One row per document is ideal; a class row is acceptable only when every member shares the same source, authority and screen outcome.
- An empty reuse authority field means the document is excluded, however clean the text looks.
| Field | What to record | Illustrative value | Filled by |
|---|---|---|---|
| Document and fixity | Stable document ID plus a hash of the exact file screened | DOC-00412, SHA-256 recorded at screening | Legal operations |
| Source system and export | System of record, export job or date, and the person who ran it | Contract repository export run on a dated ticket | Legal operations |
| Matter or contract link | Pseudonymous matter or agreement reference, not the client name | MATTER-7731, agreement family A-19 | Legal operations |
| Source category and author capacity | Category from the classification table; author role | Executed agreement; drafted by in-house counsel from company template | Counsel |
| Version and amendment chain | Which version controls, what it supersedes, and later amendments | Version 4 executed; amended once; amendment 1 recorded separately | Legal operations, checked by counsel |
| Key dates | Created, received, executed or filed, superseded, and any confidentiality expiry | Executed and amendment dates from the signature pages | Legal operations |
| Reuse authority | The instrument that permits this use and the clause or record reference | Confidentiality clause permits de-identified use; or documented client consent | Counsel |
| Privilege and confidentiality screen | Reviewer, date, outcome and basis category, without privileged content | Screened; not privileged; no protective order | Counsel |
| Approvals | Who approved inclusion and under which internal policy | General counsel approval logged on the release record | Approver |
| Exclusion record | If excluded: reason category, date and reviewer | Excluded: counterparty authorship, no reuse basis | Counsel |
Which version, amendment or authority controls the decision?
The executed version controls, together with every later amendment, and the governing authority is whatever those instruments and the relevant engagement or consent records say about reuse. Drafts are not the agreement, and an unsigned amendment does not change it. The inventory therefore records the chain, not just the latest file.
Three situations cause many errors. An amendment can tighten a confidentiality clause after the original signing, so a reuse basis that existed earlier no longer does. A master agreement can carry the confidentiality terms while the statement of work holds the commercial detail, so the document under review is governed by a different file. And a signature by someone without delegated authority leaves the version's status uncertain, which belongs in the row as an open question rather than a silent assumption.
Where the authority is a client's consent, ABA Formal Opinion 512 is a useful signal of how strictly the profession reads consent in AI contexts. Its guidance on generative AI tools says lawyers should get informed consent before entering information relating to a representation into self-learning tools, and that boilerplate consent in an engagement letter is not enough. Licensing is a different use, but a team should expect counsel to apply at least that standard.
Logging a privilege screen without exposing what it protects
Record the screen's outcome and basis category, never the privileged content. The model is the description courts already require when a party withholds material: Federal Rule of Civil Procedure 26(b)(5)(A) asks the withholding party to expressly make the claim and describe the nature of the withheld documents in a way that lets others assess the claim without revealing the protected information.
For a licensing inventory, that means an excluded row reads like a short privilege-log entry: document class, date range, the general basis (attorney-client communication, work product, protective order, client confidentiality) and the reviewer. It does not quote or summarize the advice. The exclusion record is kept internally; it is evidence that the screen happened, not material for the dataset.
Redaction is not a shortcut around the screen. Removing names from a privileged memo does not change what the memo is, and a de-identified document still needs a reuse authority. Access to a file, privacy clearance, ownership of the text and a contractual right to license it are four separate questions.
Proving the delivered file is the one counsel screened
Hash each file when it is screened and again when it is packaged, and keep both values in the row. If the hashes differ, the file changed after review and goes back through the screen.
Evidence law offers a familiar benchmark for why this matters. Federal Rule of Evidence 901 requires evidence sufficient to support a finding that an item is what its proponent claims it is. Rule 902(14) allows data copied from an electronic device, storage medium or file to be authenticated by a qualified person's certification, and the committee notes explain that identical hash values make it highly improbable that the copy differs from the original.
A licensing review is not a trial, but the same logic gives a buyer and a reviewer something concrete: the file that was screened, approved and delivered can be shown to be the same file, without anyone reopening its contents.
Worked example: a lease portfolio with two exceptions (illustrative)
A property management company's legal operations team considers offering its commercial lease records. The figures here are illustrative counts, not results. The repository holds roughly 4,000 files across three classes: executed leases built from the company's own template, tenant redlines received during negotiation, and court filings from collection cases.
Executed leases pass the classification step, but the reuse authority field depends on each lease's confidentiality clause. Counsel finds two template generations: the older one is silent on de-identified use, the newer one permits it. The team includes only the newer leases where the version chain is complete, which removes about a third of the class. Tenant redlines are excluded except where the company's own clause text can be separated from the tenant's edits. Court orders pass; the company's filings are held until outside counsel's engagement terms are recorded.
Two exceptions show why the row matters. A set of amendments was signed by regional managers whose signing authority is not documented, so those leases are held with an open question rather than counted as executed. And one collection case has a protective order covering exhibits, so every document from that case is excluded with a logged reason, even though the orders themselves would otherwise qualify.
Signals that a document class should stay out
Any one of these is a reason to narrow the scope rather than argue for inclusion. A smaller set with complete rows is easier to defend than a large set with gaps, and counsel review of the remaining rows is faster when the hard cases have already been set aside.
- The source system cannot be named, or the files arrived as an undifferentiated archive with no export record.
- Authorship is mixed inside single files, such as merged redlines, and the company's own text cannot be separated.
- The reuse authority depends on client consent that was never documented, or on an engagement letter's boilerplate alone.
- A protective order, sealing order or litigation hold covers the matter.
- The controlling version or its execution date cannot be shown from signature pages or the repository's records.
- The content came from a licensed research database or form publisher whose license does not cover this use.
Taking a documented legal record set into a licensing review
Companies that license operational records for AI meet the same questions this inventory answers, so the work is not wasted if a deal never happens. When a legal team does take records to SourceX, the work runs through rights review, contracting, preparation and delivery, with SourceX turning the chosen documents into a licensed dataset for AI.
On the SourceX path, the company approves the scope and terms and signs the agreement before any data is delivered, and a short company assessment is the first step, with no data upload needed to learn whether the company qualifies. The inventory described here is the kind of record that makes that scope decision quick and specific.
Frequently asked questions
Are court opinions and orders free to include in a dataset?
Judicial decisions and other government edicts are generally not protected by U.S. copyright, which the Copyright Office's Compendium reflects. That does not settle everything: sealing orders, protective orders and the confidentiality of the client file they sit in can still restrict use. Record the check on each row before including them.
Can a company license contracts it signed with customers or vendors?
Only where the agreements' confidentiality terms permit the use or the other party has consented, and counsel should confirm either way. Some older templates are silent on de-identified use, so the answer can differ between versions of the same form. The inventory's reuse authority field records which clause or consent the decision rests on.
Does redacting names make a privileged document usable?
No. Privilege and client confidentiality attach to the communication and the information, not only to the names in it. A redacted privileged memo is still excluded, and the exclusion is logged by category and reviewer without describing the advice.
What is the difference between provenance and a privilege log?
Provenance records where a document came from, who authored it, which version controls and what authorizes reuse. A privilege log describes documents withheld from disclosure and the basis for withholding them. The inventory borrows the privilege log's discipline for excluded rows so the screen is documented without exposing protected content.
How should scanned paper documents be handled?
Treat the scan as a derived copy and record the original's location, the scanning date and who scanned it, plus a hash of the scan. If an execution date or signature cannot be read from the scan, the version's status is an open question on the row. Scans with unreadable signature pages are usually held until the original is checked.
Sources
- The W3C PROV ontology models provenance with entities, activities and agents, and separates derivation (prov:wasDerivedFrom) from attribution (prov:wasAttributedTo). Source
- The Data & Trust Alliance Data Provenance Standards define metadata for a dataset's source, origin, generation dates and collection method. Source
- The Copyright Office will not register government edicts, including legislative enactments, judicial decisions and administrative rulings. Source
- Under Model Rule 1.6, absent the client's informed consent a lawyer must not reveal information relating to the representation, whatever its source. Source
- ABA Formal Opinion 512 says informed client consent is needed before inputting information relating to a representation into self-learning generative AI tools, and boilerplate engagement-letter consent is not adequate. Source
- Rule 26(b)(5)(A) requires a party withholding privileged material to expressly make the claim and describe the nature of the withheld documents without revealing the protected information. Source
- Rule 901 requires evidence sufficient to support a finding that an item is what its proponent claims it is. Source
- Rule 902(14) allows certified authentication of data copied from an electronic device, storage medium or file; the committee notes describe matching hash values as making differences between original and copy highly improbable. Source
See if your company qualifies
A short company assessment. No data uploads are needed.