# Archive with unclear provenance: a handoff memo | SourceX

Canonical: https://refer.sourcex.si/guides/when-an-archive-has-valuable-context-but-unclear-provenance
Last updated: 2026-11-05

An archive can be full of useful context and still have no settled origin. Before it reaches SourceX, write a provenance uncertainty handoff memo: ten questions about who created the records, how they arrived, whose material is mixed in and what the licensing company would have to confirm, each marked known, unknown or disputed, with who said so and when. Give it to whoever decides for the records. A no on a required confirmation ends the file; an unknown goes to that decision-maker, never to your own guesswork.

This page narrows [an archive custodian is not always the licensing decision-maker](/guides/an-archive-custodian-is-not-always-the-licensing-decision-maker). There, the open issue is who decides; here, the decider is known or findable, and the open issue is what nobody can yet say about the records' history.

## Context tells you what records describe; provenance tells you whose they are

A project drive holding change orders, the emails around them and the sign-offs that closed them shows how work was really done; long email archives draw interest for that reason, as [why business email archives are valuable](/proof/why-email-data-is-valuable) sets out. None of it answers the licensing question, which is about origin: who made the records, for whom, and on what terms they came to sit where they are.

Archivists draw the same line. The Society of American Archivists' dictionary defines provenance as the origin or source of something, and explains that what archival records mean depends heavily on the context in which they were created, which is why records of different provenance are kept apart (our paraphrase of the dictionary entry). SourceX's short definition, in [what data provenance is](/proof/what-is-data-provenance), is knowing where data came from, who consented to its use and what rights attach to it.

Four situations produce rich context with a cloudy origin:

- **Inherited folders.** An acquired firm's files poured into the buyer's shared drive with no label.
- **Mixed deliverables.** The company's working files beside reports written for clients, and possibly owned by them.
- **Copies nobody claims.** Backups held by a vendor, a former administrator or a storage firm after a closure.
- **Material from outside.** Purchased lists or imported datasets stored next to the company's own records.

SourceX's screening page states the test all four must eventually meet: the company "owns the material, or can license it without breaching client confidentiality, employee privacy or third-party contracts." Its list of usual misfits includes data the company does not control and "Material that belongs to the company's clients rather than the company."

## The decider and the people who remember the history

Doubts about origin never change who decides; they change what that person has to find out. For an operating company, the CEO decides. Once a company is acquired, the acquirer's CEO decides for it. For a company that was wound down or sits in a formal process, SourceX's screening matrix says "The CEO may not be enough; the estate's controller decides," and describes that controller as whoever directs the entity now: "its board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process."

The people who know the history, such as a former records manager, the IT firm that ran a migration or deal counsel, are witnesses, not deciders. Reach them only through the decision-maker, who chooses whether to ask them at all. For routes after a closure, see [who can authorize a referral for a closed business](/guides/who-can-authorize-a-referral-for-a-closed-business); for archives that changed hands in a sale, see [the retained archive after a business divestiture](/guides/the-retained-archive-after-a-business-divestiture).

## The provenance uncertainty handoff memo

Ten lines, asked of the decision-maker in conversation, each with one of three statuses: **known** (the decision-maker states it and can say how they know), **unknown** (nobody has answered yet) or **disputed** (two people with standing give different answers). Every line also carries a "how we know" note: who said it, in what role, on what date. Nothing in the memo comes from opening the archive.

| Line | Question for the decision-maker | Why it matters | Who can usually answer |
|---|---|---|---|
| 1. Creator | Whose staff created these records, and over which years? | Rights start with who made the material | The decision-maker, from HR or project history |
| 2. Arrival path | Made in-house, bought with a business, inherited from a predecessor or received from someone else? | How a sale was structured decides who holds records afterward | Deal counsel, through the decision-maker |
| 3. Client share | Does any of it belong to clients rather than the company? | Client-owned material is usually not a fit | The decision-maker, with its contracts owner |
| 4. Contract limits | Do customer or vendor contracts restrict reuse? | SourceX's rights review looks for these limits | Company counsel |
| 5. Personal data | Is personal data present, and was it collected lawfully? | The licensing company confirms lawful collection | The privacy lead or counsel |
| 6. AI-training license | Has any of it been licensed for AI training before? | The licensing company confirms it has not | The decision-maker |
| 7. AI-made content | Was any of it created or altered with AI for the sale? | The licensing company confirms it was not | The decision-maker |
| 8. Copies | Which copies exist, and who holds each one? | Holding a copy decides nothing | The decision-maker's administrator |
| 9. Preservation | Has counsel placed any preservation instruction on it? | Counsel's instruction outranks a licensing conversation | Counsel for the decision-maker |
| 10. Earlier SourceX contact | Has the company ever applied to or corresponded with SourceX? | An earlier relationship makes a later introduction a duplicate | The decision-maker |

Lines 4 to 7 restate what SourceX says a supplier must stand behind. Its trust page says the rights review covers "whether the supplier owns the original records and can license them, including any customer or vendor contract limits," and that "The supplier confirms its rights in the agreement." Its how-it-works page lists what a licensing company confirms, among them that the data "hasn't been licensed for AI training before" and "wasn't created or altered with AI for the sale."

**Reading the statuses.** A known yes on line 6 or 7, or a dispute on either, stops the file, because the company could not give that confirmation. A known answer on line 3 that the archive is mostly client material stops it too, unless the decision-maker identifies a part the company itself created. Unknowns on lines 1 to 5 stop nothing. They are the decision-maker's questions, and SourceX's rights review later tests whatever the company claims.

**Method note.** The ten lines map SourceX's who-qualifies page, its terms (version 2026-10-22.2, since replaced by version 2026-11-04), its trust page and its how-it-works confirmations, all checked on 2026-10-28, plus the archival definition paraphrased above. The memo records statements and their sources. It does not judge rights, record quality or demand, which belong to the company's counsel and to SourceX's review, and it has not been tested against completed licenses.

## Custody, control and preservation on one dated line (Illustrative)

Illustrative. The firm, its archive and every date are invented; nothing here predicts a result.

A 260-person engineering services firm, still operating and run by its founder as CEO, keeps a shared project drive going back to 2009. In 2018 it bought a 40-person surveying practice, whose folders were copied into the same drive. An adviser on a 2026 storage move hears the CEO wonder whether the drive could be licensed.

| Date | Custody: where copies sit | Control: who decides | Preservation: what applies | Memo lines affected |
|---|---|---|---|---|
| 2009 to 2018 | The firm's own servers | The CEO | Nothing reported | Line 1 known for the firm's own folders |
| 2018 | Surveying folders join the drive | The CEO | Nothing reported | Line 2 unknown: nobody has read the purchase agreement for record terms |
| 2024 | A hosted file service | The CEO | Nothing reported | Line 8 known: one hosted copy and one tape backup held by the IT firm |
| September 2026 | Unchanged | The CEO | Counsel confirms no preservation instruction | Line 9 known |
| October 2026 | Unchanged | The CEO | Unchanged | Line 3 disputed: the project lead says client deliverables sit apart, the contracts manager says they are mixed in |

The adviser's memo shows lines 1, 6, 7, 8, 9 and 10 known, lines 2, 4 and 5 unknown and line 3 disputed. Line 6 is a clear no, never licensed for AI training, so nothing stops the file yet. The CEO asks the contracts manager to settle line 3 and counsel to read the 2018 purchase agreement for line 2. The adviser does neither; both are the company's work.

Two other answers would have ended it: a 2023 sale of training rights to the drive (line 6), or a preservation instruction from counsel, which would have meant waiting for counsel's release.

## Nothing on the referral side settles provenance by looking

Unclear origin invites investigation. Resist every form of it:

- **No opening, sampling or indexing.** Folder trees, file names and dates seen on a screen are not evidence of provenance, and seeing them puts you in the archive's chain of access.
- **No logins.** Not the administrator's, and not a former employee's. A departed employee's password is not a route to anything.
- **No copies held for safekeeping.** If a copy is at risk, tell the decision-maker the date you heard about; preserving it is their decision, made with counsel.
- **No requests to the custodian.** Asking a vendor or storage firm to export, extend or describe contents is an instruction only the account holder can give.
- **No promotions.** "Unknown" and "disputed" stay as written. The memo never turns a guess into "known."

Personal data needs separate care. For a wound-down company SourceX's matrix gives the rights test as "The estate's control, plus personal data limits," and an unclear origin often means an unclear consent history, a question for the company's privacy lead or counsel. Where a preservation duty and a licensing idea meet, follow [the counsel-led escalation map for litigation holds](/questions/litigation-hold-records-can-they-be-shared).

## Where the memo goes, and the two ways a file ends

The memo goes to one person, whoever decides for the records: not to SourceX on its own, the custodian, creditors or colleagues.

**If the decision-maker wants a conversation**, they decide what the company tells SourceX, including which unknowns to raise. The company applies itself; SourceX's how-it-works page describes the first step as "A few questions, no files, and an indicative licensing estimate." Your introduction, if you make one, names the company, the decision-maker and their dated agreement, and says you have seen and copied nothing. You must have signed the Channel Partner Agreement before submitting (terms, section 1), and credit follows section 2: the first valid introduction within the 90-day attribution window is credited when the company submits a verified application, decided from dated records.

**If the memo stops**, close the file with the line that stopped it, the date, who told you and the event that would reopen it. [How to document why an archive referral cannot proceed](/guides/how-to-document-why-an-archive-referral-cannot-proceed) gives the register for that note. Line 10 works differently from the rest: under section 3 of the terms, a company with an earlier application, relationship or valid introduction is a duplicate, so a yes there means no later partner is credited, even though the company can still talk to SourceX itself.

## How a provenance memo can mislead its reader

- **Witnesses disagree.** A disputed line may never be settled; the memo records the disagreement and does not break the tie.
- **Known is not proven.** A confident answer can be wrong; SourceX's rights review and the supplier's own confirmations test it.
- **It is not a rights opinion.** Contract and privacy questions belong to the company's counsel.
- **Review still decides fit.** An archive with every line known can be declined for relevance or demand, which SourceX judges in review.
- **The cost falls on the company.** Settling lines 2 to 4 takes counsel's time; raise the memo when the decision-maker is interested enough to spend it.

**A measurable check.** Draft the memo for the next five archives you meet before saying anything to anyone. Count how many clear every stopping line, how many stop on line 3 or 6 and how many stall on unknowns. If most stall, reach decision-makers sooner rather than finding more archives. Related guides sit in the [guides hub](/guides).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the decision-maker reads the memo and still wants to talk, your next moves are [partner registration](/register), a fresh look at the [published fit criteria](/who-qualifies) with the memo's unknowns in mind, and a careful reading of the [program terms](/terms), all before anything is submitted.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/how-it-works
- https://sourcex.si/trust
- https://dictionary.archivists.org/entry/provenance.html
