# Cross-system workflow referral: who to ask | SourceX

Canonical: https://refer.sourcex.si/guides/cross-system-workflow-histories-one-introduction-several-owners
Last updated: 2026-11-04

A workflow that runs through several systems has several owners and one decision-maker. Administrators keep each system, different teams write each step, and some of the content arrived from customers, vendors or subcontractors. None of those people can authorize licensing; under SourceX's program the CEO does. So the partner makes one introduction, to the CEO, after a short run of metadata conversations the CEO has agreed to, each one placing a record set as company-made, third-party or unplaced. An unplaced record set goes to SourceX's review as an open question; nobody guesses its owner.

This guide is for the specialist who already knows how a piece of work moves through a company: an implementation consultant, a fractional operator, a former head of field service. How linked records are keyed, cleaned and checked for buyers is covered in SourceX's own [cross-system workflow guide](https://sourcex.si/ai-data/agents/cross-system-workflow-records); this page stays on whom to talk to, in what order, and what to ask.

## What a cross-system workflow history is, in plain terms

Take one warranty claim. A customer emails a complaint, a service agent opens a CRM case, a dispatcher raises a field-service work order, a technician uploads photos and a subcontractor's inspection report, and finance issues a credit memo in the ERP. Five records in four systems describe one piece of work. SourceX's buyer guide describes cross-system workflow records as the events of one piece of work "pulled from each system it touched and merged into a single ordered timeline", and says the value for agent training and evaluation sits in the joins between systems. Why agent builders look for this kind of multi-system work is set out on the [AI agent use-case page](/datasets/use-cases/ai-agents).

The history is valuable because it crosses boundaries, and those same boundaries split its ownership. OCEL 2.0, a published format for object-centric event logs, lets one event relate to several objects, each tagged with the role it plays in that event, and lets objects relate to one another outside any event. Read that as a referral problem: the credit memo touches the case, the work order and the customer account at once, and each object can sit with a different team under a different contract. SourceX's published process gives a practical marker too: companies that qualify list at least 5 systems when they apply, and share no records at that stage.

"Owner" means five different things in a workflow like this. Keep them apart before the first conversation.

| Kind of owner | Usually | Ask them about | Never treat them as |
|---|---|---|---|
| Decision owner | The CEO | Whether the company wants the conversation, and whether you may talk to its teams | A sign-off to collect after the discovery is done |
| Process owner | Head of the team that writes a step: service, dispatch, finance | Which system holds the step, how long the practice has run, who else writes into the record | The person who authorizes licensing |
| System custodian | Administrator of the CRM, field-service tool or ERP | Year span, retention settings, whose name the account is held in | Proof that the company owns what the system holds |
| Content origin | Staff, a customer, a vendor or a subcontractor, field by field | Learned from the process owner, never from a sample | Something you can infer from the system the content sits in |
| Contract holder | Counsel, or whoever keeps customer and subcontractor agreements | Which agreements a rights review would need to read | A clearance; SourceX's review decides rights |

The custodian and owner distinction is drawn more fully in [data owner versus data custodian](/compare/data-owner-vs-data-custodian), and an operating partner's version of the same roles sits in the [map of data owners and gatekeepers](/guides/an-operating-partner-s-map-of-data-owners-and-gatekeepers).

## The multi-owner discovery conversation map

Six conversations in a fixed order, then one introduction. The order matters more than the wording: the CEO hears about it first and last, and every conversation in between happens because the CEO agreed to it.

| Step | Talk to | Their ownership | The one question | Write down | Stop or flag when |
|---|---|---|---|---|---|
| 1 | The CEO, directly or through whoever holds that relationship | Decision | "May I map, without any files, which teams and systems hold the history of this workflow, and report back to you?" | Date and answer | The CEO declines or wants to wait: stop |
| 2 | Process owner of the first step | Process | "Where does this work start, which system records it, and which teams write into the same case later?" | Systems in order; the year each practice began | Nobody can say where the work starts: stop and tell the CEO |
| 3 | Each system custodian | Custody | "How many years does the system hold, is history kept or purged, and is the account in the company's name?" | Year span, retention and account holder per system | An account is held by a former parent, a vendor or a customer: code it unplaced and continue |
| 4 | Process owners of the later steps | Process and origin | "Which fields does your team write, and which arrive from customers, vendors or subcontractors?" | An origin code per record set | Most of the history proves to be customers' material: stop |
| 5 | Contract holder | Contracts | "Which customer or subcontractor agreements would a rights review need to read?" | Agreement types, never their contents | Anyone offers to send an agreement: decline and note the type only |
| 6 | The CEO again | Decision | "Here is the map. Do you want a conversation with SourceX?" | Decision and date; the map stays with the company | No, or not now: close the file with the date |

The introduction follows step 6, once: the company applies itself through your partner link, with the CEO's agreement behind it. Before step 1, check that the company plausibly passes the published fit facts: 50 or more full-time employees at its peak, contractors left out; years of its own operating records; the rights to license them; a CEO who wants the conversation; and a location listed on [who qualifies](/who-qualifies).

**Method note.** The map combines SourceX's screening guidance and its published process (both checked 2026-10-27) with the five ownership roles above. It records who said what, and when. It does not estimate demand for the workflow, the quality of its records or any payout; only SourceX's review assesses those. Putting the CEO at both ends follows the program's emphasis on an informed decision-maker; it is a working rule, not a measured result.

## Placing the origin of every record set

Three codes are enough. **Company-made (C):** written by the company's own staff in the course of the work. **Third-party (T):** sent in by a customer, vendor or subcontractor, such as an attached inspection report or a customer's photo. **Unplaced (U):** nobody you spoke to can say. Code record sets, not systems: one ticketing tool can hold agent notes the company wrote and customer messages it did not, in neighboring fields.

Origin matters more than location because rights follow the content. SourceX's screening guidance asks that a company own the material, or have room to license it without breaking a client's confidentiality, its staff's privacy or a contract with someone else, and it counts client-owned material among the usual misfits. Later in the process the supplier itself confirms it holds the rights and that the data has not been licensed for AI training before. On the developer side, NIST's AI Risk Management Framework asks, in subcategory MAP 4.1, for documented approaches to mapping the legal risks of an AI system's components, third-party data included, along with the risk of infringing someone else's intellectual property or other rights (our paraphrase). A history full of T codes is not automatically out, but it is the part of your map a rights review reads first.

An unplaced record set is not a no. Write down why it is unplaced (an account in another entity's name, an outsourcer's staff writing the notes, a migration nobody remembers) and leave the answer to SourceX's review. Guessing an owner to keep the map tidy is the one mistake that can make an honest introduction misleading.

## Three workflows on the map (Illustrative)

Illustrative. All three companies are invented, and each row describes a state of the map, not a result.

| Check | Original work | Mixed third-party content | Uncertain ownership |
|---|---|---|---|
| Company | 160-person equipment rental firm | 240-person HVAC service contractor | 310-person regional logistics company |
| Workflow | Fleet pricing change approvals | Warranty claims, complaint to credit memo | Dispatch exceptions, booking to settlement |
| Systems | Ticketing tool, ERP, document library | CRM, field-service tool, ERP, shared drive | Booking system, dispatch platform, payments system |
| Origin codes | C, C, C | C, C, C, T (subcontractor reports and customer photos on the shared drive) | C, U (dispatch history before 2021 sits in a platform account registered to the group that sold the company), C |
| What the CEO hears at step 6 | Every record set is the company's own work | One of four record sets carries third-party content a rights review will read | One account's controller is unknown, and the question goes to SourceX unanswered |
| Decision so far | Wants the conversation; the company applies | Wants the conversation and asks counsel to list subcontractor agreement types | Prefers to settle the account question with the former owner first; file dated and parked |

In the third case the partner never contacted the former owner group, asked for a screenshot of the account settings or called the dispatch history the company's. A parked row with its reason is finished work, not a failure.

## Bounded questions that never require a file

Every one of these can be answered from memory or a systems list, and none requires opening a record:

1. Which step starts the work, and in which system?
2. Which systems does one case pass through, in order?
3. For each system, what is the first year of usable history, and was anything purged or migrated since?
4. Whose name is each system's account held in?
5. Which fields does your team write, and which arrive from customers, vendors or subcontractors?
6. Does one reference number follow the case across systems, or do people link records by hand?
7. Roughly how many cases does the workflow handle in a year?
8. Has any part of this history been licensed for AI training before? (A yes takes that part out.)

Never ask for exports, sample records, screenshots of a case, a read-only login or a walk-through on a live screen. The walk-through feels harmless and shows you customer content nobody meant you to see. Discovery questions that fit a broader owner meeting are collected in the [business owner discovery questions](/resources/business-owner-discovery-questions-financial-advisor).

## Several owners, still one credit

However many teams the map touches, the program sees one company and one partner. Section 2 of the terms is blunt: "Only one partner is credited per company." Credit goes to whoever made the first valid introduction inside the 90-day attribution window, and only once the company submits a verified application. If an implementation consultant and a former operations director both know the workflow, settle in writing before step 1 which of you will submit.

At step 1, also ask the CEO whether anyone at the company has already spoken to, applied to or emailed SourceX. Section 3 says a relationship "includes any earlier lead, account or email correspondence between SourceX and the company, however it began", and a company SourceX already knew is not credited to a later partner.

Workflows often cross entity lines. For the reward cap, a parent and all its subsidiaries count as one company. Whether a sister entity's earlier dealings with SourceX change who is credited is left to SourceX's duplicate review; the published terms set no rule for that case. Any reward is funded by SourceX itself, so the compensation in the company's signed agreement carries no deduction for the partner.

## Where the conversation map can mislead

- **Single-system work in disguise.** If the workflow lives almost entirely in one tool, one process owner knows everything and six conversations are too many.
- **Memory is not the record.** Process owners describe what should happen, and recalled year spans can be off by years; they start SourceX's inventory, they do not replace it.
- **Codes are notes.** A T can turn out to be licensable and a C can carry a restriction nobody mentioned.
- **Word travels.** If the CEO wants the idea kept between two people, skip steps 3 to 5 and let the company's application carry those questions.
- **Demand moves.** SourceX's screening guidance says requirements follow its current data needs, so a clean map does not mean a current program wants this workflow.

## 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 every record set on your map carries a code and the CEO has said yes at step 6, [create your partner account](/register), run the company once more against [who qualifies](/who-qualifies) and read the [program terms](/terms) before your link goes out. More specialist referral guides sit in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/ai-data/agents/cross-system-workflow-records
- https://sourcex.si/how-it-works
- https://www.ocel-standard.org/2.0/ocel20_specification.pdf
- https://airc.nist.gov/airmf-resources/airmf/5-sec-core/
