Catalog rollout: the source, decision and scope question data governance advisors can ask

Short answer

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.

Visual briefFull-size diagram
Three catalog entry cards for record groups, each with slots for source, decision and permitted scope: the first is complete, the second lacks a permitted scope, and the third has a source but no decision or scope.
Illustrative catalog entries. A scanner fills the source slot; people fill the other two.

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, and 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 groupSourceDecision it documentsPermitted scopeStatus
Inspection reports, 9 yearsField app to document store, lineage scannedPass, fail or conditional pass by a certified inspectorClient contracts reviewed by counsel; reuse terms recordedComplete
Nonconformance logERP quality module, scannedDisposition: rework, accept as is or scrap, with approverNot yet reviewed; some client contracts silentScope gap
Client correspondenceShared mailboxes, partly scannedUnknown: mixes scheduling, disputes and approvalsNot reviewedDecision and scope gaps
Payroll and HR filesHR systemEmployment decisionsExcluded by policy from any reuse discussionOut 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 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.

QuestionUsually answered byWhat stays unknown until SourceX reviews it
Which record groups exist, how old, how largeData steward or ITWhether they match current dataset demand
Permitted scope under contracts and noticesThe company's counselThe outcome of SourceX's rights review
Who can authorize a discussionCEO, often the ownerAny offer, its terms and timing
Company size and historyOwner or HRFinal eligibility confirmation

Eligibility is on 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, the network opportunity finder helps scan other clients, and the partner hub lists other roles.

Go deeper on the catalog rollout

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, check the company against who qualifies, and read the program terms before introducing.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

Doesn't the catalog already answer the source question?

Partly. Scanners record which system holds an asset and, where supported, its technical lineage. They do not record which business decision the records document or what customer contracts allow, so those two slots are filled by people or stay empty.

Should the permitted scope column say whether data can be licensed for AI?

It should record what the company's contracts, notices and policies say, as the company's counsel reads them. Whether a specific licensing use is permitted is decided by the company and its counsel, and then by SourceX's rights review; the advisor does not decide it.

Can I share the catalog or a lineage graph with SourceX?

No. A catalog export can reveal system names, schemas and sensitive classifications. Partners stay at metadata level: record groups, rough volumes, years and owners. If the company proceeds, SourceX works with it directly under its own agreement.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/purview/unified-catalog
  3. learn.microsoft.com/en-us/purview/data-gov-classic-lineage-user-…
  4. docs.databricks.com/aws/en/admin/system-tables/lineage
  5. w3.org/TR/prov-o

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment