A portfolio operations analyst preparing a brief usually hears a confident answer first: "it's all ours, it's in our systems." That answer describes where the records live. It says little about who made them, and for licensing the maker is what counts.
One record, several makers
Take a single support ticket at a software company. The customer wrote the opening message and attached a screenshot of their own system. An employee wrote the reply, which quotes the customer, and added an internal note the customer never saw. Part of the reply came from a canned macro that a contractor drafted years ago. Five layers, at least three makers, one record.
SourceX's screening profile on who qualifies describes rights to license as owning the material, or being able to license it without breaching client confidentiality, employee privacy or third-party contracts. It also names material that belongs to the company's clients as usually not a fit. So the question is never "is this system ours" but "which layers in it did the company make, and can they be lifted out cleanly".
Five origins, and what each usually means for the brief
Employees. Under U.S. law, a work an employee creates within the scope of employment is a work made for hire, according to the Copyright Office's Circular 30. Staff-written procedures, notes, reports and replies are therefore the strongest starting point for a claim that material is the company's own. They can still contain other people's information, which is why origin is the first question and not the last.
Contractors. Circular 30 sets a narrower test for commissioned work. It is a work made for hire only if it falls into one of nine statutory categories and the parties signed a written agreement expressly saying so; a commissioned work that misses any requirement is not one. Whether the company owns contractor-made material then depends on what the contractor agreed, which only the company and its counsel can answer. Note the era: the Circular says the status turns on the facts when the work was created, so a 2017 contractor agreement matters for 2017 material.
Customers. Messages, uploads, requirement documents and data a customer supplied. Contracts govern them, and the screening profile treats client-owned material as usually not a fit. Mark them as customer-supplied and move on.
Licensed vendors. Stock media, purchased training content, vendor documentation pasted into a knowledge base. The license terms decide what can be done with them, so they go in the brief as third-party with the license noted, not read.
The software itself. Timestamps, status changes, routing and assignment events. These record the company's own work, but individual entries can carry customer details. Ask the company how its logs are built before calling them owned.
Outside the United States the rules on employee and contractor works differ. SourceX's rights review handles the jurisdiction; the brief only records origin as the company states it.
The content-origin screening table
The asset this page adds is the fourth column: whether the split can be made from metadata, by reading, or not at all. That decides how much work a family will cost the company before anyone can discuss it. Illustrative: a 180-person business software company with its own support desk and implementation team, generic and invented.
| Record family (Illustrative) | Origins inside it | Origin marker the company may keep | Can the split be made without reading files? | Brief entry |
|---|---|---|---|---|
| Support tickets, 2015 to 2026 | Customer messages and attachments; staff replies and internal notes; macros, some drafted by a contractor in 2017 | An author role on each comment, and a macro author, if the helpdesk records them | Partly: internal notes may split by author role; replies quote customers | Mixed; staff notes may be separable by author role, to confirm with the helpdesk administrator |
| Implementation project folders | Staff-written plans, runbooks and status reports; requirement documents and data extracts supplied by customers | A folder template with a separate customer-uploads subfolder, used since 2019 | From 2019 yes, by folder; before 2019 only by reading | Mixed; split by folder from 2019, unsplit before |
| Internal knowledge base | Staff articles; passages pasted from vendor documentation | Article author and edit history | Mostly; pasted vendor text is not flagged | Mostly staff-written; vendor passages unmarked |
| Engineering issues and code reviews | Staff, and contractors from 2016 to 2019 | The account that filed each issue or authored each change | Yes, by account | Separable by account; contractor terms for 2016 to 2019 need rights review |
| Customer data in the hosted product | Customers | The tenant boundary | Yes: the whole family is excluded | Out of scope: customer-owned |
| Licensed training videos | A third-party vendor | The purchase or license record | Yes | Out of scope unless the license allows it |
Three grades for the fourth column, and what each means:
- Separable by metadata. The system already records the author, uploader or account for each item. The company can count and filter its own layer without opening anything.
- Separable only by reading. Someone at the company would have to open items to sort them. That is a real cost to the company; it is never done by the partner.
- Not separable. The layers are woven together, as in a reply that quotes the customer line by line. Record it honestly; the company decides whether the family stays in.
Minimum company context, collected first
Before the table is worth filling, confirm the facts that decide whether there is an introduction at all: the legal entity that owns the records, the CEO, peak full-time headcount (50 or more, contractors excluded), years of operation and location. 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. Then list the record families and the system that holds each. All of it comes from the company in conversation; no file is needed.
Shares, eras and unread contracts: what to label
- Origin shares are estimates. "About 70% of ticket text is staff-written, per the support lead" goes in with its source. Do not round it into "mostly ours".
- Eras matter. Contractor periods, acquisitions and system changes split a family in time as well as by maker. Give the years.
- Contracts stay unread. Note that customer agreements and contractor terms exist and who holds them. Reading them belongs to the company's counsel and to SourceX's review. The rights questions for a referral summary show how to word them so they stay open.
- Markers can be wrong. A migration may have stamped every imported item with one administrator's name. Ask whether author fields survived the last system change.
Sending the CEO-approved table, and the first call it sets up
The CEO, who authorizes a licensing discussion, reads and approves the table before it goes anywhere. It travels with the introduction as a summary; no records, samples or folder listings are attached. The person submitting it has already signed the SourceX Channel Partner Agreement, or holds a copy signed under the agreement's previous title (Channel Partner Non-Circumvention and Non-Disclosure Agreement), which continues in force as signed. If credit arises at all, it belongs to the earliest valid introduction made within the 90-day attribution window and is assigned when the company submits a verified application.
A first call built on the table can take four items: which families the company considers its own and why; which can be split by metadata today; which need reading or are not separable; and which contract questions are already known. SourceX's review takes it from there.
Where origin screening can be wrong
- Owned is not the same as clear. A staff-written note can name employees or repeat a client's confidential plans. The screening profile lists employee privacy and client confidentiality alongside ownership for that reason.
- Scope of employment is factual. Circular 30 ties work-for-hire status to the facts when the work was made. An employee who wrote training material on their own time, or a founder who wrote it before the company existed, changes the answer.
- Buyers will check again. NIST's AI Risk Management Framework, under GOVERN 6.1, asks organizations to have policies for risks from third-party entities, including infringement of others' intellectual property, and its generative AI profile suggests contracts that address content ownership and screening training data against copyrights and other rights. A vague origin line does not avoid that scrutiny; it delays it.
- Demand is separate. A family that splits perfectly can still be of no interest, because relevance to current data needs is assessed in SourceX's review.
Methods note. The five origins come from Circular 30 and SourceX's published screening profile, checked on 2026-10-27; the separability grades were written for this page. The table describes one Illustrative company. It does not measure how often record families split cleanly, how separability affects acceptance or what any family is worth; SourceX has not published those figures. For related screens, see company data versus customer data, original versus licensed content, platform versus content owners, who owns support conversations and agency records versus client work.
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.
Once the CEO has signed off on a table showing at least one family the company made itself and can split by metadata, register as a partner, run the company past the published fit criteria and work through the referral terms before anything is sent; more screening guides sit in the guides hub.
Sorting a portfolio company's records by origin is referral preparation; an analyst asked to look at SourceX as an investment is doing different diligence, and materials for that are available on request through the SourceX investor overview.
This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.