# Catalog rollout data referral guide | SourceX

Canonical: https://refer.sourcex.si/guides/moment-catalog-rollout-data-governance-advisors
Last updated: 2026-11-05

Often for the source, rarely for the other two. A catalog rollout makes a company list its record groups and connect scanners, which usually answers where records come from. Few owners can also say which business decision each group documents and what contracts permit for it. Data governance advisors can ask that three-part question while the catalog is being built. If the gaps can be closed and the company qualifies, the owner may want an introduction to SourceX, which licenses approved business data for AI training and evaluation.

## Can the owner identify the source, decision and permitted scope for each record group?

Ask it exactly that way, one record group at a time. A "yes" needs three separate answers, and catalogs fill them unevenly.

**Source** is the system and process the records came from. This is the slot catalog tooling does best. In Microsoft Purview, scans build the Data Map, the technical layer, and the Unified Catalog sits above it as the business layer where stewards curate assets. Automated lineage covers many sources, and Microsoft's documentation describes manual and custom lineage for the gaps automation does not reach.

**Decision** is the business process step or judgment the records capture: an approval, a rejection, an exception, a resolution. The W3C PROV ontology is a useful frame here. It models provenance as entities, the activities that generated them and the agents associated with them. Catalogs record the entity well and the activity poorly, so "these are rows in a table" is known while "these are credit decisions by named approvers" is not.

**Permitted scope** is what customer contracts, employee notices and internal policies allow the company to do with the records. No scanner reads a master services agreement. This slot is filled by counsel and the business owner, or not at all.

That is why process-level rights and lineage gaps are easy to overlook. The rollout is judged on coverage: how many assets are scanned, classified and searchable. A record group with a clean source and empty decision and scope fields still counts as "cataloged". The difference between lineage and provenance is explained in [data lineage vs data provenance](/compare/data-lineage-vs-data-provenance), and [data catalog vs data inventory](/compare/data-catalog-vs-data-inventory) explains why a catalog alone does not tell you what the business holds.

### A worked field map

Illustrative: a 380-person engineering inspection firm rolling out a catalog over its document store, field app and ERP. Metadata only; the advisor sees entries, not records.

| Record group | Source | Decision it documents | Permitted scope | Status |
|---|---|---|---|---|
| Inspection reports, 9 years | Field app to document store, lineage scanned | Pass, fail or conditional pass by a certified inspector | Client contracts reviewed by counsel; reuse terms recorded | Complete |
| Nonconformance log | ERP quality module, scanned | Disposition: rework, accept as is or scrap, with approver | Not yet reviewed; some client contracts silent | Scope gap |
| Client correspondence | Shared mailboxes, partly scanned | Unknown: mixes scheduling, disputes and approvals | Not reviewed | Decision and scope gaps |
| Payroll and HR files | HR system | Employment decisions | Excluded by policy from any reuse discussion | Out of scope |

The second row is the interesting one for a referral conversation. Its source and decision are clear, so closing the scope gap is a counsel task, not a data project. The fourth row shows that "out of scope" is a valid and useful answer.

## Which four metadata questions come after the three-part answer?

Once the owner has gone through the record groups, four short follow-ups show whether a licensing conversation is worth raising. Write down only the answers.

1. **Which groups are complete?** Name the record groups with all three slots filled, and the ones where only scope is missing, since those are a counsel task rather than a data project.
2. **How long and how much?** Years of history and rough volumes for those groups, as ranges.
3. **Will any context be lost?** Some platforms keep lineage for a limited window. Databricks documents that its Unity Catalog lineage system tables keep a rolling one-year window, while Catalog Explorer and the lineage API keep lineage captured after September 1, 2024. Ask whether any scanned system is due to be retired during the rollout, and record only dates that are written down.
4. **Who answers for scope?** The name of the counsel or contract owner who reviews customer agreements and notices.

No documented event means no deadline; do not create one. The guide to [assessing governance procedures without exposing restricted documents](/guides/how-to-assess-governance-procedures-without-exposing-restricted-documents) covers how to ask about policies without reading them.

## How do you disclose the reward and get the owner's permission?

Raise it with the owner or COO, not only the data steward, and keep it separate from steering meetings. Explain that SourceX is a licensing company that pays businesses for approved data, that you are a SourceX referral partner, and that you may receive a referral reward which SourceX funds separately and which never reduces the company's payout. Note the date you disclosed it.

Then ask a plain question: would the owner like an introduction, or should you leave it? Even a "no" leaves the catalog better, because the decision and scope fields now have owners. If the answer is yes, the introduction names the authorized contact and the record groups at metadata level, and says that no catalog export, lineage graph or record has been shared.

## Who owns cataloged record groups, and who can authorize a licensing discussion?

The company owns its records; the advisor holds a consulting mandate. A data steward can describe a group, but authorizing a licensing discussion belongs to the CEO (in an owner-run company, usually the owner), with counsel answering scope questions.

| Question | Usually answered by | What stays unknown until SourceX reviews it |
|---|---|---|
| Which record groups exist, how old, how large | Data steward or IT | Whether they match current dataset demand |
| Permitted scope under contracts and notices | The company's counsel | The outcome of SourceX's rights review |
| Who can authorize a discussion | CEO, often the owner | Any offer, its terms and timing |
| Company size and history | Owner or HR | Final eligibility confirmation |

Eligibility is on [who qualifies](/who-qualifies): 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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 default reward is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap across all agreements and renewals. Illustrative only: a $400,000 payout would mean a $70,000 reward. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards). Sign the Channel Partner Agreement before submitting introductions. Advisors on knowledge projects can compare the [Confluence project guide](/guides/how-knowledge-management-consultants-spot-referral-opportunities-during-confluence-projects), the [network opportunity finder](/tools/network-opportunity-finder) helps scan other clients, and the [partner hub](/for) lists other roles.

## Go deeper on the catalog rollout

- [Catalog rollout meeting agenda](/resources/catalog-rollout-meeting-agenda): a timed 15-minute agenda for the owner conversation.
- [Catalog rollout archive context checklist](/resources/catalog-rollout-archive-context-checklist): a tick-box checklist to complete before the rollout settles which context is kept.
- [Catalog rollout introduction email](/resources/catalog-rollout-introduction-email): a ready-to-edit email for introducing the owner to SourceX.

## 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.

If the owner can name the source, decision and permitted scope for at least one substantial record group and opts in, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/purview/unified-catalog
- https://learn.microsoft.com/en-us/purview/data-gov-classic-lineage-user-guide
- https://docs.databricks.com/aws/en/admin/system-tables/lineage
- https://www.w3.org/TR/prov-o/
