This checklist belongs to the catalog rollout guide. The three-part question is first asked in the 15-minute meeting agenda; this page carries the open answers forward to the day the old inventory goes dark.
What actually gets switched off in a catalog rollout
A catalog is additive, so the risk is easy to miss. What disappears is the material around it.
| Thing retired | Why it matters | Where the date comes from |
|---|---|---|
| The spreadsheet or wiki inventory stewards kept before the catalog | It often holds the only written note of what a dataset means and which decision it records | The rollout plan's decommission step |
| A legacy data dictionary or older catalog tool | Business descriptions and owners may not import cleanly | The old tool's license or support end |
| A source system replaced during the program | Records may move while their process context stays behind | The replacement project's cutover plan |
| Lineage events older than a platform's retention window | History of how data moved may age out | The platform's documentation |
The last row is documented for some platforms. Databricks states that its Unity Catalog lineage system tables keep a rolling one-year window, with older events removed, while Catalog Explorer and the lineage API keep lineage captured after September 1, 2024. That sets no deadline for any company; it tells you to ask what the company's own platform keeps.
Mark every item confirmed (a responsible person said so), unknown (with a name for who will find out) or at risk (the current plan loses it). Ask for descriptions; never ask anyone to open the catalog or send an export.
Milestone one: before the rollout is announced
The program scope is still being drawn. Questions cost nothing now.
| Confirm | Owner | If skipped |
|---|---|---|
| Which record groups the rollout will cover first, with start years and rough volumes | Data governance lead | The checklist has nothing concrete to track |
| Where business definitions live today (spreadsheet, wiki, old dictionary) | Data steward | The only written context is treated as disposable |
| Whether "decision documented" will be a catalog field, or only technical metadata | Data governance lead | The catalog launches with source filled and decision blank |
| The CEO, who can authorize a licensing discussion about the company's records, by name | Owner or CEO | An interested company has nobody able to say yes |
Milestone two: before the catalog goes live
Go-live is when people stop updating the old inventory. Capture what it knows first.
| Confirm | Owner | If skipped |
|---|---|---|
| Each priority group's source is scanned, or manually entered where scanning does not reach | Platform owner | Lineage gaps look like missing data rather than manual work |
| Each priority group names the decision it records and the role that made it | Process owner | "Rows in a table" is all anyone can say later |
| Permitted scope has an owner for each priority group, even if the answer is "under review" | Counsel or contract owner | Scope stays nobody's question indefinitely |
| Descriptions from the old inventory are carried into the catalog's business layer | Data steward | Years of notes vanish when the spreadsheet is archived |
The second row is the one catalogs miss. In Microsoft Purview, scans fill the Data Map and stewards curate the Unified Catalog; Microsoft's lineage guide covers manual and custom lineage where automation does not reach. None of that captures the business judgment a record documents. The W3C PROV model calls this the activity and the agent, alongside the entity, and it is the part a person has to write down.
Milestone three: before legacy sources are switched off
Once the old inventory is archived or a source system is retired, missing context is hard to recover.
| Confirm | Owner | If skipped |
|---|---|---|
| The actual switch-off date for each retiring tool or system, from its contract or plan | IT or finance lead | The team learns the date after it has passed |
| Records from any retiring source system have a readable home and a named custodian | Platform owner | Records survive but nobody can explain them |
| Lineage history the company wants kept is copied before any retention window removes it | Platform owner | How data moved between systems is lost |
| Scope answers marked "under review" have a dated follow-up with counsel | Owner | Open questions quietly become permanent gaps |
The guide to assessing governance procedures without exposing restricted documents shows how to ask about policies without reading them, and the data catalog vs data inventory comparison explains why retiring the inventory is the risky step.
The summary you hand the owner
Illustrative. A fictional 310-person regional utility contractor completed all three milestones. The advisor's one-page summary read:
| Area | State | Note |
|---|---|---|
| Priority record groups | Confirmed | Work orders from 2012, safety inspections from 2015, change requests from 2018 |
| Source and lineage | Confirmed | Scanned, with manual lineage for the field app |
| Decision recorded | Partial | Inspections and change approvals named; work orders lack approver role before 2016 |
| Permitted scope | Partial | Counsel reviewing client contracts; follow-up dated |
| Legacy inventory | At risk | Spreadsheet scheduled for archive; descriptions half migrated |
| Authorized contact | Confirmed | CEO |
That is a sound metadata-level description. If the owner wants to explore licensing:
Disclose. You are a SourceX referral partner. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward that it funds separately and never deducts from the company's payout.
Check fit. 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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. SourceX's current data needs, the rights review result and any offer stay unknown until SourceX reviews an application.
Introduce. Use the catalog rollout introduction email, after signing the Channel Partner Agreement. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Illustrative only: an $800,000 payout to the company on its first qualifying transaction would mean a USD 120,000 reward (15%, above the USD 50,000 plus 5% floor), and there is no cap per company. The rewards page lists every condition. Advisors working inside SAP programs can compare the SAP partner referral page.
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 checklist shows priority record groups keep their source, decision and scope through switch-off and the owner wants to talk, register as a partner, check who qualifies and read the program terms before introducing.