# Referral rights screening questions: 8 to ask | SourceX

Canonical: https://refer.sourcex.si/guides/the-rights-questions-that-belong-in-a-referral-summary
Last updated: 2026-11-05

A referral summary should carry rights questions, never rights conclusions. Eight belong in it: who created the records, which entity holds them, what customer contracts and privacy promises say, whether those terms have changed, how much personal information the records hold, whether third-party material is mixed in, whether anything is already licensed, and whether a lender, investor or parent must consent. For each, the appendix records who at the company can answer and whether they have. Counsel and SourceX's rights review supply the answers.

The appendix sits under the short company summary and travels with it. It is written for the analyst who prepares portfolio introductions and for the CEO who approves them.

## Why a summary carries questions, not conclusions

SourceX's screening profile defines rights to license as owning the material, or being able to license it without breaching client confidentiality, employee privacy or third-party contracts. Each of those three tests is answered by reading a document: an employment or contractor agreement, a customer contract, a privacy notice. A partner does not read those documents and should not. "Rights look clean" in a summary is a sentence no partner can support, and a reviewer has to discount it.

What a partner can contribute is a record that each question was asked, of whom, on what date and with what result. That record has value on the developer side too. NIST's AI Risk Management Framework includes GOVERN 6.1: "Policies and procedures are in place that address AI risks associated with third-party entities", and NIST counts infringement of a third party's intellectual property or other rights among those risks. A developer working to that subcategory has reason to ask where licensed material came from, and an appendix written early catches those questions while the people who can answer them are easy to reach. That is a reason to write it carefully, not evidence that any reviewer or Acquisition Partner relies on it.

## The rights-questions handoff appendix

Eight lines. Each line names the question, why it is asked, who at the company usually answers, and one of four statuses: answered (with role and date), estimate, open (with the person who will answer) or for SourceX review.

| No. | Question | Why it is asked | Usually answered by |
|---|---|---|---|
| R1 | Who created the records: employees, contractors, customers or vendors? | The Copyright Office explains that an employee's work within the scope of employment is a work made for hire, while a commissioned work qualifies only in listed categories with a signed written agreement | Operations or HR lead |
| R2 | Which legal entity holds them? | The holder is the party that would license, and a parent and its subsidiaries count as one company for the reward cap | CFO |
| R3 | What do customer contracts, privacy notices and terms say about using these records? | FTC staff have warned that breaking a promise not to use customer data for model training can create liability, including promises made in marketing or online terms | General counsel or outside counsel |
| R4 | Have those terms or notices changed, and when? | FTC staff have said that quietly loosening data-use terms to enable AI training may be unfair or deceptive | General counsel |
| R5 | How much of the material is about identifiable people? | Personal consumer data is usually not a fit, and employee privacy is part of the rights test | Privacy or operations lead |
| R6 | Is third-party material mixed in, such as vendor manuals, purchased content or partner data? | Third-party intellectual property is the risk GOVERN 6.1 points to | Operations or procurement lead |
| R7 | Has any of it been licensed already, exclusively or not? | An earlier license can limit what remains available | CEO or CFO |
| R8 | Must a lender, investor, acquirer or parent consent before the company licenses data? | Financing and shareholder documents sometimes carry consent rights that only the company can check | CFO or counsel |

Four rules keep the appendix honest:

1. **Name documents; never attach them.** "Customer agreement template, current version, held by outside counsel" is a complete entry.
2. **Quote the company, do not upgrade it.** "We think the contracts allow it" stays exactly that.
3. **Attribute every answer.** Role and date on each line, such as "CFO, 2026-10-20".
4. **Unknown is a valid status.** An open line is not a failed line; it tells SourceX where to start.

For R8, the [lender consent question](/questions/lender-consent-to-license-intellectual-property-credit-agreement) shows what a CFO checks in a credit agreement; for R3, [whether customer consent is needed](/questions/do-you-need-customer-consent-to-license-data) sets out the questions counsel weighs.

## The minimum context the appendix sits under

The appendix does not stand alone. Above it sits a company summary of a few lines, approved by the CEO: the kind of work the records follow, roughly since when, a volume range, the kinds of system, and that the CEO wants a conversation. Three fit facts belong there as well. The company needs 50 or more full-time employees at peak, contractors excluded, and documented operating history. The third is 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. None of these replaces SourceX's review, which also checks relevance to current data needs.

## A filled appendix for a property manager (Illustrative)

Illustrative. An invented property manager, used only to show how the eight lines read when filled.

A 240-person residential property management company, 17 years old and run by its owner as CEO, manages buildings on behalf of about 60 property owners. The CEO wants a conversation and named the CFO, the operations director and outside counsel to answer.

| No. | Status | Entry |
|---|---|---|
| R1 | Answered (operations director, 2026-10-20) | Work orders and inspection notes are written by the company's own staff; vendor invoices are attached to some |
| R2 | Answered (CFO, 2026-10-20) | Held by the operating company, a subsidiary of a family holding company; one reward cap would cover the group |
| R3 | Open (outside counsel) | Management agreements with building owners address records; nobody has read them for this purpose |
| R4 | Answered (CFO, 2026-10-21) | Resident privacy notice last revised in 2025, for an unrelated reason |
| R5 | Estimate (operations director) | Residents' names and unit numbers appear on most work orders |
| R6 | Open (operations director) | Manufacturer manuals are stored alongside some equipment records |
| R7 | Answered (CEO, 2026-10-21) | Nothing licensed before |
| R8 | Open (CFO) | Credit facility terms not yet checked |

Read as a whole, the appendix tells SourceX three things without offering an opinion. R3 is the decisive line: if the management agreements make the records the building owners' property, much of the archive is client material, which is usually not a fit. R5 points to heavy personal information. R7 is clean. The analyst sends it with three open lines and no forecast.

One more entry belongs here. If the holding company or a sister business had ever been in touch with SourceX, the appendix should say so. The published terms do not address whether contact by a related entity changes credit for this introduction; that is decided in SourceX's duplicate review, and the appendix only records the facts.

## Writing an open question so it stays open

Most damage happens in the wording. The partner's job is to keep each question exactly as open as it really is.

| Partner wrote | Write instead | Why |
|---|---|---|
| "Rights are clean" | "R1 to R8: three answered, five open; see entries" | No partner can certify rights |
| "Standard customer contracts, should be fine" | "Customer agreement template not yet read by counsel" | "Standard" is a guess about a document nobody read |
| "No personal data" | "Operations director estimates names appear on most records" | An estimate stays labeled as one |
| "We own everything" | "CEO states the company owns the records (2026-10-20)" | Attributes the claim to the person who made it |
| "Lender won't mind" | "Credit facility consent terms not yet checked by the CFO" | Consent is a document question |

**Method note.** The eight questions were drawn from SourceX's who-qualifies page and program terms (version 2026-10-22.2, since replaced by version 2026-11-04), Copyright Office Circular 30, two FTC staff posts from 2024 and NIST AI 100-1, all checked on 2026-10-27. The appendix has not been tested with counsel or reviewers, and SourceX has not published how often specific rights questions end a review; those figures are not yet published. To measure it, log each introduction's open lines at handoff and which of them SourceX's rights review raised first.

## The handoff and the first rights conversation

1. **The CEO approves** the summary and the appendix together, edits included.
2. **Prior contact is recorded.** A company with any earlier application, lead, account or email correspondence with SourceX is a duplicate and is not credited, so the CEO's answer goes on the form.
3. **A named submitter.** A verified application from the company is what triggers credit, which goes to one partner per company: whoever made the first valid introduction inside the 90-day attribution window. Decide in writing who that partner is; they sign the SourceX Channel Partner Agreement before submitting.
4. **Nothing attached.** Documents named in the appendix stay with the company; if the company proceeds, they are shared with SourceX under its own agreement.

On the first call, SourceX can explain how its rights review works, the CEO decides whether counsel joins, and the open lines are taken in order of how much they could narrow scope, R3 and R1 usually first. The analyst's part ends once that call is booked. For deeper preparation the company can use the [rights readiness checklist](/resources/rights-readiness-checklist), and deal teams will recognize the four data questions in the [IT due diligence checklist](/resources/it-due-diligence-checklist).

## Where a rights appendix can mislead

- **Answers from the wrong person.** An operations lead's view of what customer contracts say is not counsel's. Each line names its answerer for that reason.
- **Jurisdiction matters.** Privacy and employment rules differ by country and state; R5 is a count, not a legal analysis.
- **Guidance moves.** The FTC posts are staff statements of enforcement posture, not new rules, and positions can change.
- **Documents change.** Renewals and amendments alter contracts after the appendix is dated; date every line.
- **Asking has a cost.** Rights questions from an investor can feel like diligence. Say plainly that the answers belong to the company and that no one outside it will read its documents at this stage.
- **Fit and demand still decide.** A clean appendix does not make a company fit a current program; SourceX applies each program's criteria, and a company that fits none now may fit one later.

The program overview for funds is at [venture platform teams](/for/venture-platform-teams), and related walkthroughs are in the [guides library](/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.

When a CEO has approved a summary whose rights appendix names an answerer for every line, [join as a partner](/register), compare the summary's three fit facts with the [qualification page](/who-qualifies), and keep the [program terms](/terms) open while you submit the introduction.

Preparing rights questions for a portfolio introduction is referral work. A fund assessing SourceX as a potential investment is making a separate decision, and can ask for investor materials through the [SourceX investor overview](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.copyright.gov/circs/circ30.pdf
- https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/01/ai-companies-uphold-your-privacy-confidentiality-commitments
- https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/02/ai-other-companies-quietly-changing-your-terms-service-could-be-unfair-or-deceptive
- https://nvlpubs.nist.gov/nistpubs/ai/nist.ai.100-1.pdf
- https://sourcex.si/investors
