Skip to content

Leadership and readiness

Supplier archive ownership documentation: name an evidence owner first

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Supplier archive ownership documentation should exist before anyone discusses price. Name one evidence owner who assembles three dossiers: systems (where records were created, what changed, how they leave), rights (who controls them, under which contracts and notices) and task context (what work they record, what outcome codes meant). Score each answer as documented, known, conflicting or unknown, and price only the scope documents can explain.

License terms

Supplier archive ownership

This page covers supplier archive ownership documentation: name an evidence owner first.Illustrative

Key takeaways

  • Name one evidence owner before any price is discussed; approving and signing the deal are separate jobs.
  • Sort every buyer question into three dossiers: source systems, rights and task context.
  • Score each answer as documented, known, conflicting or unknown, and estimate effort from those states rather than archive size.
  • Rights answers must come from dated documents, including the notice in force when each record was collected.
  • Price only the scope every dossier supports; otherwise narrow, reconstruct or stop.

What must an archive owner document before a price is discussed?

Three things, held by one named person: where the records came from and how they can leave, who controls them and under which promises, and what work they record. Call that person the evidence owner. Until the evidence owner can answer a buyer's questions in those three areas from documents, any price attaches to a scope nobody can yet describe.

The evidence owner is not the person who approves the deal or the officer who signs it. Approval is a judgment about whether to proceed; evidence ownership is the job of finding, dating and filing the answers that judgment rests on, and of routing each buyer question to whoever can answer it. In a 60-person company one executive may hold both roles, but they fail in different ways: an approver without evidence decides on belief, and evidence without an owner sits in five inboxes.

Documentation gaps are normal, not a sign of a bad archive. When researchers at the MIT Media Lab audited more than 1,800 text datasets on popular hosting sites, they found license information missing for more than 70 percent of them and error rates above 50 percent in what was shown. Those were datasets built for machine learning. A business archive built to run a company starts further back, which is why supplier archive ownership documentation belongs before the price, not after it.

Why a buyer cannot price records nobody can explain

Because a price covers a scope, and scope is written in terms only the evidence can supply: which systems, which years, which fields, which record types, under which rights. A buyer who cannot get those answers either narrows the scope to what is explained or adds conditions that move the risk back to the company.

Source systems hide their own history. Salesforce documents that, without its Field Audit Trail add-on, tracked field history is retained for up to 18 months in the interface and up to 24 months through the API. Whether a CRM holds three years of stage changes or eighteen months is a fact about one system's configuration, and someone has to know it before the archive is described as a complete sales history. Migrations, retention settings and fields repurposed over the years raise the same question in every system.

Rights hide in documents written for other purposes: customer agreements, privacy notices, vendor terms and acquisition papers. Buyers publish limits of their own. OpenAI's data partnerships page asks for large datasets not already easy to reach online, and it excludes sensitive or personal information along with any information whose owner is a third party. A company that cannot show whose information sits in its records cannot show that it meets a condition like that.

Task context hides in people's heads. A resolution code, a reason-for-return field or an approval flag means what the team used it to mean, and that meaning often drifted. Without it, a buyer receives rows; with it, the records can become training or evaluation tasks.

System, rights and task context: the three dossiers

Group every buyer question into three dossiers, because each draws on a different part of the company and goes stale on a different clock. The grouping follows established dataset documentation practice rather than inventing a new one.

At a glance

System, rights and task context: the three dossiers

Datasheets for Datasets, the framework proposed by Timnit Gebru and colleagues, organizes its questions along a dataset's life: motivation, composition, collection process, preprocessing and labeling, uses, distribution and maintenance. The MLCommons Croissant responsible-AI vocabulary asks for similar facts in machine-readable form, including who created a dataset and for which purpose, when it was created, which sources were used and how each version is timestamped. A business archive maps onto those questions in three groups.

  • System dossier: the systems of record, when each was adopted, migrations and their dates, retention settings, field definitions and how records can be exported. Usually held by the system administrator or IT lead; it goes stale when configuration changes.
  • Rights dossier: who owns or controls the records, the customer agreements, vendor terms and privacy notices in force when they were created, third-party content and any acquired data. Usually assembled by the contracts owner with counsel; it goes stale when terms or notices change.
  • Task-context dossier: what work the records capture, what each outcome or status code meant over time, who did the work and how exceptions were handled. Usually held by operations leads and long-tenured staff; it goes stale when those people leave.

The evidence owner roster: eight questions and who answers them

The roster names, for each question a buyer is likely to ask, the role that usually knows the answer and the document that settles it. Fill in real names and dates; a role is a placeholder, not an answer.

The last column matters most. Every question without a documented answer becomes one of three things in a draft agreement: an exclusion, a condition the company must satisfy later, or a representation the company signs on belief. Deciding which, before a price is discussed, is the evidence owner's main job. The figure shows the same eight questions moving from their dossiers into a pricing conversation only once each answer is documented.

The evidence owner roster: eight questions and who answers them
Dossier and questionWho usually knowsDocument that settles itIf nobody can answer
System: which systems hold the records, and since when?IT lead or system administratorSystem inventory with adoption and migration datesLimit scope to years after the last documented migration
System: what history did each system keep?System administratorRetention and audit-history settings, captured with datesDescribe the records as current state only
System: can the records leave with their links intact?Administrator with export rightsA recorded test export of a sampleHold any pricing until a test export succeeds
Rights: who owns or controls the records?CEO or general counselFormation, acquisition and asset-transfer documentsStop until counsel resolves ownership
Rights: what did customers and users agree to when the records were created?Contracts owner with counselDated contract templates and every privacy notice versionExclude periods with unknown terms
Rights: whose third-party or personal information is inside?Privacy lead or data protection officerData map or record of processing, plus a sampled content reviewExclude affected record types pending review
Task: what work does each record capture, start to finish?Operations leadProcess description tied to record types and fieldsOffer the records as raw history, not tasks
Task: what did each outcome or status code mean, and when did that change?Long-tenured team leadCode list with change dates and examplesDrop the field or flag it as undefined
Three lanes of buyer questions for systems, rights and task context, each question marked documented, known, conflicting or unknown, with only documented answers passing a gate into the priceable scope.
From dossier to priceable scope. Illustrative: the answer states are an example, not measured data.

Rights answers have to come from dated documents, not memory

Rights questions are the ones where memory is least acceptable, because the answer has to survive a reading by the other side's lawyer. Ownership, system access, privacy permission and the right to license are four separate questions, and having one never proves another. De-identifying records does not create a right to license them.

Start with what the company already keeps. Article 30 of the GDPR requires a controller to maintain a record of its processing activities, including the purposes of processing and the categories of data subjects, personal data and recipients. Organizations with fewer than 250 employees are exempt only when their processing is occasional, unlikely to result in a risk to individuals and free of special-category or criminal-conviction data. For an EU company, that record is usually the first draft of the rights dossier's personal-data section.

Date every notice. In February 2024 the FTC's technology staff warned that a company may be acting unfairly or deceptively if it shifts to looser data practices, training AI on its data for instance, by quietly and retroactively amending its terms or privacy policy. For an archive, the notice that matters is the one in force when each record was collected, so the rights dossier needs every version with its effective dates, not only today's policy.

Counsel decides what the documents mean. The evidence owner's job is to make sure counsel reads the right documents, for the right periods, with nothing missing.

The answer-state test: documented, known, conflicting or unknown

Score each roster question by the state of its answer, then estimate effort from those states rather than from the size of the archive. A ten-terabyte archive with documented answers can be quicker to scope than a small one where nobody knows what a status code meant.

The four states are deliberately blunt. Documented means a dated record answers the question. Known means a named person can answer but nothing is written down. Conflicting means two sources disagree, such as a contract template and a signed agreement with different data clauses. Unknown means nobody can answer yet.

Effort follows a simple sum: for each state, the number of questions in it times the hours to close one, added across the four states. The hour values in the worksheet are Illustrative placeholders for a company to replace with its own; they are not benchmarks. In an Illustrative case, a 120-person distributor scores its eight roster questions: three documented (the systems in use, a test export and control of the records), three known, one conflicting (two privacy notice versions) and one unknown (what an old status code meant). The placeholder values give 3 x 1 + 3 x 4 + 1 x 8 + 1 x 20, or 43 hours, before any export work, and nearly half of that sits in the single unknown question. That is where the evidence owner starts.

The worksheet sets out each state, the work that closes it and who usually does it.

The answer-state test: documented, known, conflicting or unknown
Answer stateWhat it meansWork to close itIllustrative hours per question (editable)Usual owner
DocumentedA dated record answers the questionCheck the record still matches the system or the terms1Evidence owner
KnownA named person can answer; nothing is writtenInterview, write the answer, have the person confirm it against records4The person who knows, with the evidence owner
ConflictingTwo sources disagreeFind the governing document and record why it governs8Counsel or system administrator
UnknownNobody can answer yetReconstruct from records, or decide to exclude20Evidence owner, with outside help if needed

Reconcile the dossiers with scope, conditions and payment triggers

Before any figure is discussed, write the scope the dossiers can support and compare it line by line with whatever draft terms exist. Every scope line, condition and payment trigger in a draft should point to a dossier answer marked documented; anything else is a risk the company is taking without having priced it.

  • Scope: each system, year range, record type and field named in the draft should match the system dossier. A draft that reaches back before the last migration needs a documented answer for those years.
  • Internal effort: the answer-state worksheet gives the hours to reach that scope. Estimate export and review work separately so the two are not confused.
  • Conditions: representations about ownership, consents and third-party content should be backed by the rights dossier. A condition the company cannot evidence today is a promise to do the work later.
  • Payment triggers: where payment depends on delivery or acceptance under the signed terms, list what must be true for each trigger and which dossier answer covers it. Leave timing to the signed agreement.

Is the evidence work wasted if no offer follows?

It can be, and the company should plan for that. Eligibility, a positive assessment or an indicative offer does not mean a buyer will select the dataset, that a deal will close or that any particular amount will be paid. Spend on evidence in stages, and stop when the next stage depends on a commitment nobody has made.

Stage the roster. Answer the rights questions first, because an unknown on ownership ends the conversation whatever the system and task dossiers say. Then answer the system questions that define scope. Leave the slower task-context interviews until a buyer has said which records interest it.

Some of the work keeps its value without a deal. A dated system inventory, a notice history and a code list help with audits, retention decisions, internal AI projects and the diligence for any future sale of the company. That is a reason to close the cheap documented and known items now, not a reason to fund reconstruction of unknowns on speculation.

The decision memo: price now, narrow, reconstruct or stop

End with a one-page memo that states the decision, the roster results that justify it, the limits of what was checked and the next evidence needed. Four decisions cover most archives.

The memo has limits worth writing into it. It checks whether answers exist and where they live; it does not decide whether a use is lawful, measure data quality or predict an offer. Those need counsel, a sample review and a buyer.

The decision memo: price now, narrow, reconstruct or stop
DecisionWhen the roster showsWhat to tell the buyer or assessorNext evidence needed
Price nowEvery rights question documented; system questions documented or knownThe full scope, with known but unwritten answers flaggedWritten confirmation of each known answer
NarrowGaps confined to some systems, years or record typesA smaller scope that excludes the gaps, named exactlyDossier answers for any excluded slice worth recovering
ReconstructUnknowns in system or task questions that matter to the scopeA date by which answers are expected, and no price before thenReconstruction results, graded documented or known
StopOwnership or control unknown, or a conflict counsel cannot resolveThat the archive is not ready to licenseCounsel's resolution of the ownership question

Taking the roster into a SourceX assessment

SourceX works with companies that want to license selected business records to AI developers, and the deal steps it takes on run from sourcing, qualification and rights review through contracting and data preparation to delivery and payment. Whether a company qualifies is checked first, in a short assessment of the company that requires no uploaded data.

The system dossier usually answers the first fit questions. SourceX's rough guide is that buyers want one system with tens of thousands of records or more and a consistent history going back years, typically two or longer; a smaller archive can still qualify when the work it documents is rare, and each case is assessed on its own.

The rights and task-context dossiers matter at the next stage. The company's own sign-off comes first: it approves the scope and the terms and signs before SourceX receives a single record, and the dossiers are what make that sign-off an informed one. An assessment is not an offer and does not promise any payout.

Frequently asked questions

Who should be the evidence owner for a business archive?

Usually someone senior enough to get answers from IT, legal and operations, and close enough to the records to judge whether an answer is complete, such as a COO, head of operations or general counsel in a mid-size company. The role needs time more than title. What matters is that one named person files every answer with its date and source.

Is the evidence owner the same person who approves or signs a data license?

Not necessarily. Approval is a judgment about whether to proceed, and signing requires authority to bind the company; evidence ownership is the work of assembling and dating the answers those people rely on. One executive can hold all three roles, but the work should be planned as three jobs.

What if the person who understood an old system has left the company?

Mark those questions unknown and decide whether reconstruction is worth it for the scope in view. Catalogs, reports, lookup tables and remaining users can often rebuild field meanings, but each rebuilt answer should be graded honestly rather than promoted to documented. The guide to recovering a legacy data dictionary covers the technique.

Does good documentation prove a company may license its records?

No. Documents show what was agreed and when; counsel decides what they permit. Ownership, system access, privacy permission and the right to license are separate questions, and de-identification does not create a licensing right. This is general information, not legal advice.

Can a company ask for an indicative price before its dossiers are complete?

It can ask, but any figure will rest on scope assumptions the dossiers are meant to settle, and it may change or disappear as answers arrive. A short assessment can check fit without any data upload; it is not an offer and does not promise a payout.

Sources

  • The MIT Media Lab's large-scale audit of more than 1,800 text datasets found license omission above 70 percent and error rates above 50 percent on popular dataset hosting sites. Source
  • Salesforce documents that, with Field Audit Trail turned off, field history data is retained for up to 18 months in the interface and up to 24 months through the API. Source
  • OpenAI's data partnerships page seeks large-scale datasets not already easily accessible online and says it does not seek sensitive or personal information or information that belongs to a third party. Source
  • Datasheets for Datasets proposes that every dataset carry a datasheet, with questions grouped by motivation, composition, collection process, preprocessing, uses, distribution and maintenance. Source
  • The Croissant RAI specification asks for who created a dataset and for which purpose, when it was created, which sources were used and versioning with timestamps for each version. Source
  • GDPR Article 30 requires controllers to keep a record of processing activities with purposes and categories of data subjects, data and recipients; Article 30(5) limits the exemption for organizations under 250 employees. Source
  • FTC technology staff wrote in February 2024 that adopting more permissive data practices, such as AI training, through a surreptitious, retroactive change to terms or a privacy policy may be unfair or deceptive. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies