# Compliance consultant data referral: owner sheet | SourceX

Canonical: https://refer.sourcex.si/guides/the-compliance-consultant-who-spots-a-potential-data-owner
Last updated: 2026-11-04

A compliance consultant often notices, before anyone else, that a client has kept years of its own records in well-run systems. That noticing can justify one question to the CEO; it cannot be the introduction. What you learned from asset registers, data flow diagrams and findings stays inside the engagement. The introduction rests on a short discovery sheet the CEO answers from their own knowledge: which records the company creates for itself, which it holds for customers, whether it has dealt with SourceX before, and who decides. That person is the CEO.

This guide is for security, privacy and regulatory compliance consultants and the law firm alliance managers and regulated advisors who work beside them. It is not advice on your contract, independence or professional rules; the sheet below names who answers each.

## What the consultant saw, and why none of it travels

Compliance work puts you inside the company's record-keeping: the source of the insight, and the reason it cannot be reused.

| Engagement material | What it tells you | Why it stays in the engagement | What the CEO can say instead |
|---|---|---|---|
| Asset register or system inventory | Which systems hold which records, and for how long | Prepared for the engagement, in confidence | "We run our support desk and project history in two systems, back to 2014." |
| Data flow diagrams | Which data the company receives from customers and which it creates | Often maps customers' data, not the company's | "Most of what our platform stores is our customers'." |
| Findings and exceptions | Where controls failed | Sensitive, and irrelevant to licensing | Nothing; findings never enter the conversation |
| Retention schedule and access reviews | How far back archives go; who can reach what | Internal control and security material | "We keep closed cases for about ten years." |

The data flow row matters most for consultants who work with service organizations. The AICPA, in its guidance on privacy in service-organization examinations, notes that "A single organization may possess the personal information of many user entities (customers)" who expect it to stay protected. Much of what sits in scope of an engagement like that is the customers' information, held by your client. SourceX's screening page lists material that belongs to a company's clients among its usual poor fits, along with data the company does not control. Holding data is not the same as owning it, and which records the company owns is read by its counsel and SourceX's rights check.

SourceX's own documents draw the same line from the other side. Section 4.2 of the sample Channel Partner Agreement says it "gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems," and section 4.4 bars a partner from collecting supplier dataset copies through the program without separate written authorization.

## Three kinds of "owner," and only one decides

Compliance vocabulary is full of owners: asset owners, control owners, data owners. None of them is the person this page is about.

| Sense of "owner" | Who it usually is | What they can tell you | Can they agree to a licensing discussion? |
|---|---|---|---|
| Asset, system or control owner | A manager responsible for a system or control | How the system works, what it holds | No |
| The company as owner of its records | The legal entity whose staff created them | Nothing directly; its rights are read by counsel and SourceX's rights check | It acts through its CEO |
| The customer as owner of its data | The client's own customers | Nothing to you | No, and their data is usually out |
| The decision-maker | The CEO | Whether the company wants the conversation | Yes |

So "spotting a potential data owner" means spotting a company that may own records worth discussing, then learning whether its CEO wants to talk. A keen head of IT or privacy lead can say what exists, never yes; the [guide to reading job titles](/guides/how-to-avoid-inferring-data-ownership-from-a-job-title) treats authority-sounding titles the same way.

## The owner introduction discovery sheet

Ten lines. The CEO answers lines 1 to 8 in a conversation; you answer line 9 with your own adviser; line 10 is a joint record. Every answer is a sentence someone said, with a date, never something copied from the engagement.

| Line | Question | Who answers | Never taken from |
|---|---|---|---|
| 1. Origin | Did the CEO raise the topic, or agree to hear it when you asked? | The CEO | Your own assumption |
| 2. Own records | Which records does the company create about its own work (tickets, QA logs, project histories, procedures)? | The CEO | The asset register |
| 3. Held for others | Which records does it hold or process for customers or clients? | The CEO | Data flow diagrams |
| 4. Size | What was full-time headcount at its peak, and when? Contractors are left out | The CEO | Org charts from the engagement |
| 5. History | Roughly how many years of those records exist, and in which systems by name? | The CEO | Retention schedules |
| 6. Earlier contact | Has the company ever applied to, held an account with or exchanged email with SourceX? | The CEO | Nobody else's records |
| 7. Location | Where is the company, and in what language are the records? | The CEO | Assumption |
| 8. Who decides | Is the CEO the decision-maker today, or has an acquisition or formal process changed that? | The CEO | Titles |
| 9. Your position | Your role, your engagement terms, any certification or attest role, your firm's policy | You, with your own adviser | The client |
| 10. Route | Partner introduction, unpaid introduction, or none | The CEO and you | Pressure from either side |

Notes on four lines:

- **Line 2** carries the opportunity: a service company whose platform holds customers' data still writes records about its own operations, the self-created material SourceX's screening profile looks for.
- **Line 6** matters because section 3 of the terms makes any earlier lead, account or email correspondence with SourceX a duplicate, credited to no later partner.
- **Line 7** is answered against SourceX's published geography. 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.
- **Line 8** is usually the CEO. Once a company is acquired, the acquirer's CEO decides; in a receivership, an assignment for creditors or a bankruptcy, the CEO alone may not be enough, because whoever controls the estate decides.

The sheet never holds findings, screenshots, evidence files, customer names, control exceptions, credentials or anything you could only know from the engagement. A line only your file could answer stays blank. SourceX's own first step asks the company "A few questions, no files," and completes the inventory with it during qualification, so a blank costs nothing.

## Confidentiality, conflict and compensation: what to settle first

Line 9 is yours, and it comes before the first question to the CEO, not after. Whoever engaged you sets the first limits.

| Your position | Ask about this first | Who answers |
|---|---|---|
| Independent consultant engaged by the company | Confidentiality and non-solicitation clauses; whether a third-party payment must be disclosed | Your own counsel |
| Consultant inside a firm that also performs attestation work for this client | Independence, and whether any part in an introduction is open to you | Your firm's independence or ethics function |
| Auditor for a certification body | The body's impartiality policy | The certification body |
| Consultant engaged through a law firm for the client | What the firm's instructions allow you to discuss | The engaging law firm, before anyone else |
| Consultant whose employer holds the client relationship | The employer's outside-activity policy | Your employer, in writing |

Questions to take to whoever answers:

1. **Confidentiality.** Given what I saw, may I suggest a conversation to the CEO, and name the company to SourceX if the CEO agrees?
2. **Conflict.** Would a reward tied to the client licensing data affect my advice on its controls, notices or vendors?
3. **Compensation.** May I accept a reward at all, what must the client be told, and would I or my firm be the partner?

None has a general answer, and this page offers none. If your employer must approve, the [employer approval guide](/guides/when-a-professional-s-employer-must-approve-referral-activity) has a request template. If you work alongside lawyers, the [role separation guide](/guides/how-to-separate-legal-advice-from-a-data-referral-discussion) keeps their advice and your introduction apart.

## Record the permitted next step and the handoff

Each sheet ends in one of three routes.

| Route | When it fits | Who takes the next step | Open questions go to |
|---|---|---|---|
| Partner introduction | Line 9 is cleared and the CEO wants the conversation | You submit after signing the Channel Partner Agreement; the company applies itself | Rights: company counsel and SourceX's rights check |
| Unpaid introduction | Your rules or choice rule out a reward | The company applies alone, or you write to SourceX first: the terms are silent on a declined reward | The same |
| No part | Your role, policy or the CEO's answer says stop | Nobody; the sheet is closed with a date | Nobody |

The handoff is the CEO's answers to lines 1 to 8, the date and who was told what. Scope, price and processing are agreed between the company and SourceX in its own signed papers, without you.

## Three consultants, three endings (Illustrative)

Generic companies, invented facts, no outcomes implied.

**A referral.** After a quarterly review, the CEO of a 180-person specialty insurance administrator asks its independent privacy-program consultant whether "our claim notes are worth anything to AI people." The consultant's own counsel confirms the engagement letter allows a disclosed introduction. The CEO's answers: eleven years of adjuster notes written by staff, peak headcount 190, no earlier contact with SourceX, and the CEO decides. The consultant signs the Channel Partner Agreement, tells the CEO in writing who would pay the reward and submits; the company applies and describes its records itself.

**An unpaid introduction.** A readiness consultant works inside a firm that also performs attestation work for a 260-person software vendor. On line 3 the CEO says almost everything in the platform is customers' data; on line 2, the company writes its own support tickets and implementation project histories. The firm's independence function rules out any reward for this client. The CEO applies directly with the sheet in hand, and no partner is named.

**No part.** During an on-site audit of a 400-person manufacturer, a certification auditor sees a quality archive going back two decades. The body's impartiality policy keeps commercial topics out of audits, so the auditor says nothing. If the CEO ever raises licensing unprompted, the question goes to the certification body first.

## Where this approach falls short

- **The sheet can look weaker than the company.** A CEO may not know peak headcount or describe the archive well, while your file says it is strong. Unknown means ask later, never open the file.
- **Rights are not settled by the sheet.** SourceX's screening page asks whether a company "owns the material, or can license it without breaching client confidentiality, employee privacy or third-party contracts," and that is read by counsel and SourceX's rights check.
- **Data already licensed for AI training is out.** SourceX's how-it-works page lists not having licensed the data for AI training before among the things a supplier confirms.
- **Timing.** Credit goes to the earliest valid introduction of a new company once it files a verified application within 90 days, judged on dated records. If a slow line 9 costs that window, so be it.
- **No outcome data.** Nobody has published how often a compliance consultant's introduction leads anywhere.

Neighboring cases: [an introduction kept apart from an audit engagement](/guides/how-to-keep-a-data-introduction-separate-from-an-audit-engagement) and [a client's archive review that raises a licensing question](/guides/when-a-client-s-archive-review-raises-a-data-licensing-question).

## 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 line 9 is settled and the CEO's own answers fill lines 1 to 8, [register as a partner](/register), compare those answers with [who qualifies](/who-qualifies) and read the [program terms](/terms) on duplicates before anything is submitted; related professional guides are in the [guides hub](/guides).

## Sources

- https://www.aicpa-cima.com/resources/download/privacy-considerations-in-a-soc-2-r-examination
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
