Contract administration histories: the referral starts with counsel, and ten bounded questions sort a contract file into the company's own work, the other side's paper and material nobody can claim yet

Short answer

Contract administration histories, meaning obligation trackers, amendment and change logs, approval trails, notice registers and closeout files, can point to a company worth introducing. But a contract file blends the company's own work with counterparties' confidential paper and, often, legal advice. So the first substantive conversation is with the company's counsel, reached through the CEO: ask bounded questions about who wrote what and what the contracts allow, request no files, and introduce the company only when its CEO wants the conversation.

Visual briefFull-size diagram
A fanned stack of three contract file folders labeled own work in green, the other side's paper in orange and owner unclear in grey; arrows lead from the stack to a box reading counsel answers, then to a box reading the CEO decides, with a note that no files leave the company.
The three layers this page sorts a contract administration history into, and the order in which counsel and the CEO answer.

Record type proves nothing on its own. A drawer of executed contracts says nothing about rights, suitability or whether anyone wants the records today; those answers come from counsel, from the CEO and finally from SourceX's review.

What a contract administration history actually contains

Contract administration is everything a company does to make a signed contract happen. In federal contracting the work is codified: FAR 42.302 lists functions such as post-award orientation conferences, property administration, consent to subcontracts, monitoring small business subcontracting plans and administrative closeout. Commercial companies do similar work under other names, in contract lifecycle software, ERP modules, project systems, spreadsheets, shared drives and email.

A typical history has layers that differ in who wrote them:

LayerTypical contentsUsual authorFirst read
Internal administration workObligation registers, deadline calendars, deviation requests, approval memos, issue logs, closeout checklistsThe company's contract administratorsLikely the company's own work
Executed agreements and amendmentsSigned contracts, often on the other side's template, and later changesBoth partiesMixed; the contracts' own confidentiality terms matter
Counterparty correspondenceNotices, claims, change requests and invoices sent by the other sideThe counterpartyThe other party's material
Legal advice inside the fileCounsel's emails and memos on disputes or interpretationCounselPrivileged; stays out unless counsel decides otherwise
Files administered for a clientContracts the company managed on a client's behalf, often in the client's systemCompany staff, for the clientThe client's material; usually not a fit
Personal detailsSignatory names, contacts, employees named in disputesVariousA privacy question for review

The company's own reasoning, such as why a deviation was approved or how an entitlement was calculated, is usually the layer with the most operating knowledge. It is also the layer most tangled with paper written by someone else.

Why counsel answers before anyone introduces the company

Four kinds of question sit inside a contract file, and every one of them is a legal reading:

  1. Confidentiality. Many commercial contracts restrict what either side may disclose. Whether a clause reaches the company's internal notes about a contract, or only the other side's information, is counsel's call.
  2. Privilege. Legal advice is scattered through dispute and interpretation files, and only counsel can say where it sits and how to keep it out.
  3. Third-party rights. AI developers face the same question from their side. NIST's AI Risk Management Framework, in subcategory GOVERN 6.1, calls for policies that address AI risks tied to third parties, including infringing someone else's intellectual property or other rights. Mixed contract paper is exactly where such a question arises.
  4. What the supplier must confirm. SourceX's published process has the supplier confirm it holds the rights to license the data, that personal data was collected lawfully and that the data has not been licensed for AI training before.

Starting with counsel does not make counsel the decision-maker. Under the program, the CEO authorizes a licensing discussion and signs for the company. The order is CEO, then counsel's answers, then the CEO's decision, and the advisor never goes around the CEO to reach counsel.

Ten counsel-led introduction questions

These questions stay at metadata level: categories, counts, systems and clause types, never contents. The advisor gives them to the CEO, who decides who answers.

#QuestionAnswered byA clear answerWhat sends it back
1Which parts of the file did the company's own staff write, rather than receive?Contracts leadNamed record types such as obligation logs, approval memos and closeout checklistsMost of the file is the other side's paper
2Which entity employed those staff when the records were made?Counsel or HROne named entity, still in the groupA predecessor or acquired entity not yet traced
3Was any of the work done for a client, inside the client's systems?Contracts leadNo, or a clearly separate portionYes, for most of the history
4Do the main contract templates carry confidentiality terms that reach internal administration notes?CounselA known set of clauses and a view on their scopeHundreds of contracts with unread, inconsistent clauses
5Do any contracts with public bodies or regulated counterparties add handling rules of their own?CounselIdentified and countableUnknown
6Can the company's own work be separated from counterparty documents at system level?Systems ownerYes, by record type, field or folderOnly by reading each file
7Where does legal advice sit, and can it be excluded cleanly?CounselIn identifiable locationsWoven through email threads
8Which categories of personal data appear?Counsel or privacy leadKnown categories, such as signatories and contactsUnknown
9How many years and which systems hold the history, and has any of it been licensed for AI training before?Contracts lead and CEOYears and systems named; no earlier AI-training licenseAn earlier AI-training license, which rules the data out
10With answers 1 to 8 in hand, does the CEO want a licensing conversation?CEOA yes in the CEO's own wordsA no, or an open-ended "later"

Questions 1 to 3 settle origin, 4 to 8 settle what the contracts and the law allow, and 9 and 10 settle history and authority. A clean answer to 6 matters more than it looks: if the company's own work cannot be separated from counterparty paper without reading every file, preparation becomes expensive whatever the rights picture says.

Original work, mixed paper and an unclaimed file (Illustrative)

Illustrative. The three companies are fictional composites built to show the questions at work, with no real records, deals or outcomes behind them.

Original work. A 320-person specialty construction contractor whose contract administrators kept twelve years of change-order logs, notice registers and closeout checklists in its own project system. Most entries are their own words: quantity reconciliations, entitlement reasoning and approval notes. The project owners' directives and subcontractor quotes sit as attachments.

Mixed paper. A 150-person government services contractor whose subcontract files combine flow-down clauses from its prime contracts, subcontractors' proposals and pricing, and its own consent memos and monitoring notes. Consent to subcontracts and subcontracting-plan monitoring are both on the FAR list, and here the company's notes describe other firms' prices.

Unclaimed file. A 110-person outsourced contract management provider that administers its clients' supplier contracts inside the clients' own contract systems, under service agreements whose work-product clauses nobody has reread in years.

QuestionConstruction contractorGovernment services contractorOutsourced provider
1. Own workMost of the fileConsent memos and monitoring notesIts own playbooks and training material only
3. Done for a clientNoNoYes, for nearly all records
4. Confidentiality termsSubcontract templates need counsel's readingSeveral clause sets, some from prime contractsService agreements unread
5. Public-body rulesNone foundYes, counsel to identifyUnknown
6. Separable by systemYes: attachments are a separate objectPartlyNo: records live in clients' systems
Likely pathCounsel answers, attachments scoped out, then the CEO decidesCounsel decides whether internal notes can stand apart; may narrow or stopHold until counsel says what, if anything, is the provider's own

The provider shows why record type misleads. Its staff did skilled, original work, yet most of the records sit in systems its clients own and were made under contracts that may give the work product to those clients. SourceX's screening guidance usually treats client-owned material as a poor fit, so the honest answer may be that only the provider's own methods material is worth a conversation.

Finding the owner of the file and where it came from

Trace four things, each at metadata level:

  • Who ran the function. A contracts manager, legal operations, procurement, project controls or an outside provider. That person explains the records but does not authorize anything.
  • Where the records sit. Contract lifecycle software, an ERP module, a project system, shared drives, email archives, or a client's tenant.
  • Which entity holds them. After acquisitions, files can sit in a different entity from the one that created them. There is no cap on rewards, but the USD 50,000 floor applies once per referred company, so which entity counts as the company matters.
  • Who decides. The CEO of the entity that holds the records. Counsel advises on rights; the contracts lead explains; the CEO says yes or no.

If another company in the same group has already been in touch with SourceX, do not tell anyone how credit will fall. The terms are silent on related companies, and SourceX works that out in its duplicate review.

The published fit facts apply before any introduction: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized CEO. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

The note to the CEO, and what never travels with it

A first note can be four sentences. Illustrative wording: "Your contract administration history, the change logs and closeout files in particular, may be the kind of operating record some companies license for AI training. Before anyone discusses it, your counsel would need to answer a short list of rights questions, which I can send. Nothing leaves your systems, and the decision is yours. Would you like the list?"

Never ask for, accept or forward:

  • Contracts, amendments, clause libraries or playbooks
  • Samples, screenshots or exports of any kind
  • Logins to contract lifecycle software, ERP or project systems
  • Counterparty names, pricing or dispute details

The live pages on contract review workflows, assessing contract process materials without sharing privileged work and customer contract data-use restrictions cover the record type and the restrictions in more depth. If the founder asks to bring a lawyer to the first SourceX call, the first-call agenda with counsel shows how to run it.

Limits of a counsel-first question set

  • Counsel's time costs money. Ten questions can mean hours of legal review before the company knows whether anyone wants the records. Questions 1, 3 and 6 are cheap to answer first and can end things early.
  • Clean answers are not acceptance. Relevance to SourceX's current data needs is checked only in its review, and a well-sorted file can still be declined.
  • Volume hides variation. A company with thousands of contracts will have clauses nobody has read in years. Counsel may only be able to answer for the main templates, and the gaps should be recorded rather than assumed away.
  • The advisor's own position. Advisors who administered the contracts themselves, as outside counsel or consultants, hold engagement confidences of their own and should check their professional rules before making any introduction.

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.

When counsel has answered the origin and rights questions and the CEO wants the conversation, register for a partner link, check the company against who qualifies and read the attribution and duplicate sections of the program terms before you submit; advisors working alongside legal teams can also start from the fractional general counsel page.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does counsel decide whether the company licenses its contract records?

No. Counsel answers the rights questions and advises; the CEO authorizes a licensing discussion and signs for the company. Starting with counsel simply means the CEO hears the rights picture before deciding, rather than after.

Can an advisor who once worked on the contracts describe them to SourceX?

No. What an advisor learned on an engagement belongs to that engagement. The introduction carries only what the CEO agrees to share, at metadata level, and SourceX's own review takes it from there.

What if a sister company in the same group already spoke to SourceX?

Do not guess how that affects credit. The terms do not address related companies directly, and SourceX resolves it in duplicate review. What is settled is that there is no cap on rewards, and that the USD 50,000 floor applies once per referred company, not again on a repeat.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. acquisition.gov/far/42.302
  4. nvlpubs.nist.gov/nistpubs/ai/nist.ai.100-1.pdf
  5. sourcex.si/how-it-works

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment