# Limited scope data referral: boundary statement | SourceX

Canonical: https://refer.sourcex.si/guides/when-the-company-wants-to-limit-which-records-are-discussed
Last updated: 2026-11-05

Let it, and write the limit down before anyone is introduced. SourceX's own process leaves scope to the company, so a CEO who wants some records kept out of the conversation is using a right the program already gives. Turn that wish into a short scope boundary statement the CEO approves: record families open for discussion, families parked until a named condition, and families closed, each named by category and system only. Send the statement, never the records.

For a portfolio operations analyst the request usually arrives sideways. The founder says "happy to talk, just not about the HR side," or "leave the commercial division out of it." The reflex is to treat that as an obstacle to negotiate around. Read it as information instead: a CEO who already knows where the line sits has done part of the rights thinking a review will need. SourceX's short answer on [keeping information outside an agreed scope](/questions/can-a-company-keep-certain-information-outside-an-agreed-data-scope) says the same from the company's side.

## Scope belongs to the company at every stage

The company's control does not start at the contract. It runs from the first conversation to the reward calculation.

| Stage | Who sets the scope | Published basis |
|---|---|---|
| Before the introduction | The CEO, through the statement on this page | Referral how-it-works page: the company controls "what scope to offer" |
| Application | The company lists its systems and history; no records are shared | SourceX's how-it-works page |
| Deal | The company approves scope and terms and signs before any data is delivered | SourceX's how-it-works page |
| License | Only the selected data; future data and unselected records are excluded | SourceX's how-it-works page |
| Reward | Based on compensation paid for "selected data that reaches Closing" | Program terms, section 4 |

The last row matters to anyone counting on a reward. A record family the company keeps out never enters the payout, so it never enters any reward either. An analyst gains nothing by quietly widening the frame.

Companies narrow scope for ordinary reasons. Employee files are the commonest: under the EU's General Data Protection Regulation, Article 9(1) prohibits processing special categories of personal data, among them data revealing trade union membership and data concerning health, unless an Article 9(2) exception applies, and HR and leave records are where such data tends to sit. The [note on employee data and AI training](/questions/can-employee-data-be-used-to-train-ai) covers the wider question. Other reasons: material held under client confidentiality, a legal hold, a business unit in a sale process, a system halfway through migration, or a plain wish to see how the first call goes. A company that wants no conversation at all is somewhere else, and SourceX's main site covers [declining an AI company's data request](https://sourcex.si/insights/how-to-say-no-to-an-ai-company-that-wants-your-data).

One discipline applies to funds in particular. What the fund learned in a board meeting is not permission to mention it. The statement contains only what the CEO approves for it.

## Context to gather first, and who supplies each line

Keep the context short and sourced to the company, never to a data room or a board deck.

| Line | Supplied by | Label it as |
|---|---|---|
| Legal entity and its CEO | The CEO | Fact, with the date |
| Full-time employees at peak, and the month | The CEO, or a finance lead the CEO names | Fact or estimate |
| The year records begin in each open system | Whoever administers that system | Estimate unless counted |
| Systems, by plain name | The system administrators | Fact |
| Location, and the language of the records | The CEO | Fact |
| Any earlier contact with SourceX | The CEO | Fact; section 3 counts any earlier correspondence as a relationship |
| Who in the fund holds the CEO relationship | The analyst | Fact |

Location matters because of the program's geography rule. 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 English share is measured on what is actually offered, so a boundary that changes which families are open can change that share too.

## The scope boundary statement template

One page, six parts, with no records, samples or screenshots attached. The CEO approves it line by line.

1. **Header.** Legal entity, the CEO's name, the approval date, a version number and who prepared it.
2. **Open for discussion.** Each record family with its system, years covered and a rough volume band, each labeled, plus whose records they are.
3. **Parked.** Each family, why it is parked, the condition that would reopen it and who decides.
4. **Closed.** Each family by category only, with a broad reason class: personal data, client-owned, legal, transaction or not now.
5. **What the partner may say aloud.** One or two sentences the CEO has approved word for word.
6. **Open questions for SourceX.** What the company wants to learn, and what nobody can answer yet.

Illustrative. A generic 230-person HVAC services company, invented facts.

| Zone | Record family | System | Years covered | Note |
|---|---|---|---|---|
| Open | Work orders with technician notes | Field service system | 2012 to 2026, company estimate | Company's own work records |
| Open | Quotes and estimates | CRM | 2015 to 2026, company estimate | Company's own; customer contact fields to be removed later |
| Parked | Dispatch call recordings | Phone platform | Not stated | Reopens when counsel finishes reviewing the phone vendor's contract; the CEO decides |
| Closed | Employee HR and leave files | HR system | Not stated | Personal data |
| Closed | Records of the commercial refrigeration division | Separate ERP | Not stated | Transaction |

What the partner may say: "The company is open to discussing its service and quoting records. Other areas are outside this conversation for now."

Notice what the closed rows leave out: no counts, no detail on the sale, no description of the HR system's contents. A reason class tells SourceX why a door is shut without opening it. The template's open zone is, in effect, a smaller version of a [metadata-only inventory of business systems](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems).

**Method note.** The template follows SourceX's published process pages and program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and GDPR Article 9, all checked 2026-10-27. The three zones and the reason classes are our own structure. It does not measure whether a narrower scope changes how SourceX assesses a company; SourceX has published no figures on that.

## Estimates, constraints and the questions nobody can answer yet

Four labels cover every line in the open and parked zones.

| Label | What it means | Example |
|---|---|---|
| Fact | Confirmed by a named company person, with a date | "Field service system in use since March 2012, per the operations director, 14 October" |
| Estimate | A figure with its method and a range | "About 300,000 to 400,000 work orders, read from the system's dashboard" |
| Constraint | A limit the company knows about, in its own words | "The phone vendor's contract may restrict use of recordings" |
| Unknown | An open question, with who could answer it | "Whether quotes include supplier pricing under confidentiality; SourceX's rights review" |

Closed families get no labels at all, only their category and reason class. Two habits keep the statement honest. Never firm up an estimate because the scope shrank. And never interpret a constraint yourself: "may restrict" stays "may restrict" until someone who has read the contract says otherwise.

## Handoff, and a first call that stays inside the line

The relationship owner sends the approved statement after signing the SourceX Channel Partner Agreement, with a two-line note to the CEO and SourceX. The analyst joins the call only if the CEO wants that. A thirty-minute agenda:

| Minutes | Item | Led by |
|---|---|---|
| 0 to 3 | The CEO restates the boundary in their own words | CEO |
| 3 to 10 | How SourceX works and where the company approves each step | SourceX |
| 10 to 22 | Open families at metadata level: what, how long, which system, whose | CEO or a system owner |
| 22 to 25 | Parked families, only if the CEO raises them | CEO |
| 25 to 30 | Next steps and who follows up | SourceX |

Nobody but the CEO raises a closed family. If the CEO later moves a family between zones, the statement gets a new version and a new approval date; [updating a referral brief after facts change](/guides/how-to-update-a-referral-brief-after-material-facts-change) sets out that routine.

## Why a narrow scope can still fail, and other limits

- **Too little left to assess.** SourceX's how-it-works page says qualifying companies list at least 5 systems, and its fit signals include volume and historical depth. A statement that opens one small system may not carry a review. Whether systems named as closed count toward that is SourceX's call.
- **Rights trouble inside the open zone.** An open family can still hold client-owned material or personal data. The screening page's rights test, licensing "without breaching client confidentiality, employee privacy or third-party contracts", is applied in review, not by the analyst.
- **Investor pressure.** A fund that leans on a portfolio CEO to open more risks the relationship, and gains nothing on families that never close.
- **Demand.** SourceX checks relevance to current programs during review. A cleanly bounded company can still be declined.
- **Drift.** Boundaries move as sales close and contracts get reviewed. An undated statement is a liability.

## 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 the CEO has approved a dated boundary statement and the open zone still holds records the company created itself, [register for a partner link](/register), test the open families against [who qualifies](/who-qualifies) and read the [program terms](/terms) on what a reward is calculated from. Platform teams will find the wider program in the [venture platform overview](/for/venture-platform-teams) and more methods in the [guides library](/guides).

Whether SourceX itself deserves a place in a fund's portfolio is a different question from where a company draws its boundary; SourceX shares company and commercial metrics with investors directly, and materials can be requested on its [investor page](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://refer.sourcex.si/how-it-works
- https://sourcex.si/how-it-works
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://sourcex.si/investors
