# Contract administration records referral | SourceX

Canonical: https://refer.sourcex.si/guides/contract-administration-histories-the-referral-starts-with-counsel
Last updated: 2026-11-05

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.

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:

| Layer | Typical contents | Usual author | First read |
|---|---|---|---|
| Internal administration work | Obligation registers, deadline calendars, deviation requests, approval memos, issue logs, closeout checklists | The company's contract administrators | Likely the company's own work |
| Executed agreements and amendments | Signed contracts, often on the other side's template, and later changes | Both parties | Mixed; the contracts' own confidentiality terms matter |
| Counterparty correspondence | Notices, claims, change requests and invoices sent by the other side | The counterparty | The other party's material |
| Legal advice inside the file | Counsel's emails and memos on disputes or interpretation | Counsel | Privileged; stays out unless counsel decides otherwise |
| Files administered for a client | Contracts the company managed on a client's behalf, often in the client's system | Company staff, for the client | The client's material; usually not a fit |
| Personal details | Signatory names, contacts, employees named in disputes | Various | A 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.

| # | Question | Answered by | A clear answer | What sends it back |
|---|---|---|---|---|
| 1 | Which parts of the file did the company's own staff write, rather than receive? | Contracts lead | Named record types such as obligation logs, approval memos and closeout checklists | Most of the file is the other side's paper |
| 2 | Which entity employed those staff when the records were made? | Counsel or HR | One named entity, still in the group | A predecessor or acquired entity not yet traced |
| 3 | Was any of the work done for a client, inside the client's systems? | Contracts lead | No, or a clearly separate portion | Yes, for most of the history |
| 4 | Do the main contract templates carry confidentiality terms that reach internal administration notes? | Counsel | A known set of clauses and a view on their scope | Hundreds of contracts with unread, inconsistent clauses |
| 5 | Do any contracts with public bodies or regulated counterparties add handling rules of their own? | Counsel | Identified and countable | Unknown |
| 6 | Can the company's own work be separated from counterparty documents at system level? | Systems owner | Yes, by record type, field or folder | Only by reading each file |
| 7 | Where does legal advice sit, and can it be excluded cleanly? | Counsel | In identifiable locations | Woven through email threads |
| 8 | Which categories of personal data appear? | Counsel or privacy lead | Known categories, such as signatories and contacts | Unknown |
| 9 | How many years and which systems hold the history, and has any of it been licensed for AI training before? | Contracts lead and CEO | Years and systems named; no earlier AI-training license | An earlier AI-training license, which rules the data out |
| 10 | With answers 1 to 8 in hand, does the CEO want a licensing conversation? | CEO | A yes in the CEO's own words | A 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.

| Question | Construction contractor | Government services contractor | Outsourced provider |
|---|---|---|---|
| 1. Own work | Most of the file | Consent memos and monitoring notes | Its own playbooks and training material only |
| 3. Done for a client | No | No | Yes, for nearly all records |
| 4. Confidentiality terms | Subcontract templates need counsel's reading | Several clause sets, some from prime contracts | Service agreements unread |
| 5. Public-body rules | None found | Yes, counsel to identify | Unknown |
| 6. Separable by system | Yes: attachments are a separate object | Partly | No: records live in clients' systems |
| Likely path | Counsel answers, attachments scoped out, then the CEO decides | Counsel decides whether internal notes can stand apart; may narrow or stop | Hold 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](/data-types/contract-review-workflows), [assessing contract process materials without sharing privileged work](/guides/how-to-assess-contract-process-materials-without-sharing-privileged-work) and [customer contract data-use restrictions](/guides/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](/guides/when-a-founder-wants-to-bring-counsel-to-the-first-call) 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](/register), check the company against [who qualifies](/who-qualifies) and read the attribution and duplicate sections of the [program terms](/terms) before you submit; advisors working alongside legal teams can also start from the [fractional general counsel page](/for/fractional-general-counsel-referral-opportunities).

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://www.acquisition.gov/far/42.302
- https://nvlpubs.nist.gov/nistpubs/ai/nist.ai.100-1.pdf
- https://sourcex.si/how-it-works
