This agenda belongs to the catalog rollout guide, which explains why the three-part question matters. Use this page to run the conversation itself, ideally the week after a stewardship workshop.
The 15 minutes at a glance
Illustrative. A data governance advisor is mid-rollout at a fictional 420-person freight forwarding firm. The catalog covers its transport management system, a customs filing tool, a claims database and shared mailboxes.
| Minutes | Block | The question asked | Who answers |
|---|---|---|---|
| 0-2 | Record groups | Which three to five record groups are the largest or oldest? | Data steward |
| 2-5 | Source | Which system and process produced each group, and is that path captured automatically or by hand? | Data steward or platform owner |
| 5-9 | Decision | Which business judgment does each group record, and by whom? | Process owner, often the COO |
| 9-12 | Permitted scope | What do customer contracts, notices and policies allow for each group? | Counsel or contract owner |
| 12-15 | Disclosure and decision | Would the owner like an introduction to SourceX, and who would lead it? | Owner |
Send the invite with one line of purpose: "Fifteen minutes on three record groups from the catalog: where they come from, what they record and what we may do with them. Descriptions only." People answer more plainly when they know no screen will be shared.
Block by block: what a good answer sounds like
Block 1, record groups (0-2 minutes). Good: "Shipment files from 2014, claims from 2017, customs entries from 2019." Each group has a name, a start year and a rough size. Weak: "Everything in the lake." If the steward cannot name groups, pick the ones the rollout scanned first.
Block 2, source (2-5 minutes). Good: "Claims come from the claims database; the path into reporting is captured automatically, and the last hop was added by hand." This is the answer tooling supplies most readily. Microsoft documents that Purview builds its technical Data Map from automated discovery, with a business-facing layer above it, and that hand-entered or custom paths cover systems automation cannot reach, so "partly manual" is a normal and honest answer.
Block 3, decision (5-9 minutes). Good: "Each claim records an accept, partial settlement or reject decision by a named adjuster, with a reason code." This is the longest block because tooling rarely captures it. A useful prompt from the W3C's provenance ontology: every record (an entity) was produced by some activity and some responsible agent. Ask about the activity and the agent, not just the table. Weak: "They're operational records." Note it and move on.
Block 4, permitted scope (9-12 minutes). Good: "Our customer terms allow internal analytics; counsel has not reviewed licensing. Customs entries include broker data under separate agreements." Partial answers are fine. What matters is that someone owns the question. Weak: "Probably fine." Record "unknown, counsel to confirm by {date}" instead.
Block 5, disclosure and decision (12-15 minutes). Say that SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Say that you are a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes, funded separately and never deducted from the company's payout. Then ask for the decision.
Reading the answers on one card
Fill one line per record group during the meeting. Three states only: named (a person gave a specific answer), partial (some of the answer is known, with an owner for the rest) or open (nobody knows yet).
| Record group | Source | Decision | Permitted scope |
|---|---|---|---|
| Shipment files, 2014 onward | Named | Partial: routing choices, approver not recorded | Open |
| Claims, 2017 onward | Named | Named: adjuster outcome with reason code | Partial: counsel reviewing customer terms |
| Customs entries, 2019 onward | Named | Named: classification by licensed broker | Open: third-party broker agreements |
| HR casework | Named | Named | Excluded by policy |
The claims line is the strongest candidate for a licensing discussion: source and decision are named, and scope already has an owner. The HR line shows that "excluded" is a complete answer, not a failure. The data catalog vs data inventory comparison explains why a catalog entry alone does not establish what the business holds, and data lineage vs data provenance separates the source slot from the decision slot.
The decision the meeting must produce
End on one of three outcomes, written down with a name and a date.
| Outcome | When to choose it | What happens next |
|---|---|---|
| Introduce now | At least one substantial group has source and decision named, scope has an owner, and the owner opts in | Send the catalog rollout introduction email to the authorized contact |
| Revisit by a date | Scope is open but counsel has agreed to look | Add the open items to the archive context checklist and book a follow-up |
| Stop | The owner declines or every group is excluded | Record the date; the catalog still gains named decision and scope owners |
A "stop" is a good outcome for the rollout. The decision and scope fields now have owners, which is work the catalog needed anyway.
Who must be in the room for "introduce now"
The owner or an executive who can authorize a licensing discussion must hear block five directly. A data steward can describe groups but cannot open a licensing conversation, and counsel advises rather than decides. If the owner is absent, close on "revisit" and schedule five minutes with them alone.
Fit also matters before anyone is introduced: 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. SourceX's current data needs, the rights review result and any offer stay unknown until SourceX reviews an application.
Sign the Channel Partner Agreement before submitting. 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. 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). For another timed format aimed at investors, see the portfolio review meeting agenda.
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 block five closes on "introduce now", register as a partner, confirm fit on who qualifies and read the program terms before you send the introduction.