This decision tree is part of the change collision recovery guide. It answers one question for ticketing platform implementation partners: when two separately approved changes broke something together, and the company kept the trail, who can say yes to a conversation about licensing that trail?
Start at the record: who holds each piece of conflict history
The history of a conflicting-change outage sits with several teams. Each can describe its part. Very few can commit the company. Begin by listing the holders, then mark which ones have authority.
| Record | Usual system | Who holds it day to day | Can authorize a licensing talk? |
|---|---|---|---|
| Change requests, approvals, planned windows | Change module of the ITSM platform | Change manager and CAB chair | No, describes only |
| Conflict results per change | Conflict checks in the same tool | Platform owner | No, describes only |
| Dependency relationships and their history | Configuration database | Configuration manager | No, describes only |
| Alerts, incidents and change events | Monitoring and on-call tools | Monitoring admin, SRE lead | No, describes only |
| Rollback approvals | ServiceNow or on-call tool | Service delivery director | Convenes; rarely signs |
| Post-incident reviews | Wiki or ServiceNow knowledge | Service delivery director | Convenes; rarely signs |
| Client contracts for managed environments | Contract system | General counsel | Advises the CEO |
The who-can-say-yes tree, question by question
Work down the tree with the service delivery director in one conversation. Each answer moves the introduction one step.
- Does the company keep closed records of these incidents at all? If closed changes, conflict results and reviews were purged, stop: there is nothing to introduce. If yes, go on.
- Who would sponsor a data licensing discussion? The CTO when the question is technical risk, the COO when it is service delivery, the CFO when it is a revenue line. The director usually knows which one. Name a person, not a title.
- Do the records describe only the company's own systems? If the company runs its own infrastructure, the path is short: sponsor, CEO and counsel. If it manages environments for clients, go to question 4.
- Do client contracts say anything about environment or incident data? If yes, counsel decides which client environments are out of scope before anyone talks about buyers. If no one knows, that is the answer for now; record it as open.
- Do post-incident reviews name hosted customers or individuals? If yes, mark them for counsel. Where EU law applies, the GDPR treats any information relating to an identifiable person as personal data, which includes an on-call engineer named in a review. That shapes scope; it does not rule the company out.
- Is anyone else's consent needed? A private equity sponsor, a parent company or a board. Note it.
The lit path in the graphic ends at the CEO and counsel together, with the sponsor alongside. That is who the introduction should reach.
Branches that need counsel or customer sign-off
Some records leave the main path and wait for counsel. Mark them in the handoff; do not try to resolve them yourself.
| Branch | Why it needs review | Who decides | Common outcome |
|---|---|---|---|
| Reviews naming hosted customers | Customer identity and outage details | General counsel | Names removed or reviews excluded |
| Managed client environments | Contract terms may restrict use of environment data | General counsel, per contract | Restricted clients excluded |
| Engineer names in incidents and on-call logs | Personal data where privacy law applies | Counsel and the privacy lead | Pseudonymized |
| Security incidents mixed with change records | May involve disclosure obligations | Security lead and counsel | Usually excluded |
| Records on legal hold | Cannot be altered or moved | General counsel | Left alone |
None of these ends the conversation. They decide what is in scope, which is the question why data rights matter explains: SourceX reviews rights before anything else happens.
Two service providers, two routes (Illustrative)
The same tree gives different introductions depending on who owns the infrastructure. Both companies are fictional.
| Question | 180-person SaaS company running its own platform | 650-person managed services provider |
|---|---|---|
| Who describes the records? | Platform owner and SRE lead | Service delivery director and the ServiceNow platform owner |
| Who convenes? | VP of engineering | Service delivery director |
| Who sponsors? | CTO | COO |
| Counsel branch | Engineer names in reviews | Client contract terms for each managed environment |
| Other consent | None | Private equity sponsor |
| Route length | Two people | Three people plus a sponsor consent |
The SaaS company's path is short because every record describes its own systems. The managed services provider has the richer history, since it sees change conflicts across many client environments, and the longer path, because each client contract is a branch. If the client will not give you admin credentials in the first place, what to do when an MSP will not share admin access covers that separate problem; authority to license is a different question again.
What the rights review settles later
Once the CEO agrees to talk, these questions remain open, and only SourceX's review answers them:
- Rights: which environments, record classes and years the company can license after contract and privacy checks.
- Preparation: what redaction or de-identification the reviews and incident notes need.
- Demand: whether any buyer wants change conflict histories when SourceX reviews them.
- Terms: whether an offer follows, and on what schedule.
The introduced company needs 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. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company.
What the describers can tell you is still useful. ServiceNow's documentation shows why the platform owner matters: a stored conflict lists the conflicting change, the affected configuration item and the issue type, such as CI already scheduled or outside a maintenance window. On the monitoring side, PagerDuty change events do not create incidents on their own; an incident's Recent Changes view shows up to three change correlations from the past 24 hours with a reason. Both people can say whether those records exist and for how many years, which is exactly what the convener needs. Neither can license them.
Stay at metadata level throughout: record classes, years, systems and owners. Do not export changes, screenshot reviews or pull a sample change conflict to prove the point. The referral brief template puts the tree's answers on one page, and the software implementation partners page and ITSM ticket history describe the wider fit.
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.
Once the service delivery director has agreed to bring in the CEO, who can say yes, and flagged any client contract limits, register as a partner, confirm the company on who qualifies and read the program terms before making the introduction.