Who can say yes to licensing change collision recovery records? A decision tree for ITSM partners

Short answer

Introduce the CEO, usually with general counsel, and ask the service delivery director to convene. The director knows which change conflicts happened, where the conflict results and post-incident reviews were written, and who would weigh a new revenue line against customer concerns. The ServiceNow platform owner, the monitoring admin and you, the implementation partner, have access, not authority. Reviews that name hosted customers need counsel, and what can be licensed stays unknown until SourceX's rights review.

Visual briefFull-size diagram
A top-down approval tree: the ServiceNow platform owner, monitoring admin and implementation partner hold access only; the service delivery director convenes; a counsel branch covers reviews naming hosted customers and client contract terms; the lit path ends at the CEO with general counsel as authorized signer.
The lit path is the introduction. Grey boxes can describe the records but cannot agree to license them.

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.

RecordUsual systemWho holds it day to dayCan authorize a licensing talk?
Change requests, approvals, planned windowsChange module of the ITSM platformChange manager and CAB chairNo, describes only
Conflict results per changeConflict checks in the same toolPlatform ownerNo, describes only
Dependency relationships and their historyConfiguration databaseConfiguration managerNo, describes only
Alerts, incidents and change eventsMonitoring and on-call toolsMonitoring admin, SRE leadNo, describes only
Rollback approvalsServiceNow or on-call toolService delivery directorConvenes; rarely signs
Post-incident reviewsWiki or ServiceNow knowledgeService delivery directorConvenes; rarely signs
Client contracts for managed environmentsContract systemGeneral counselAdvises 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.

  1. 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.
  2. 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.
  3. 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.
  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.
  5. 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.
  6. 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.

BranchWhy it needs reviewWho decidesCommon outcome
Reviews naming hosted customersCustomer identity and outage detailsGeneral counselNames removed or reviews excluded
Managed client environmentsContract terms may restrict use of environment dataGeneral counsel, per contractRestricted clients excluded
Engineer names in incidents and on-call logsPersonal data where privacy law appliesCounsel and the privacy leadPseudonymized
Security incidents mixed with change recordsMay involve disclosure obligationsSecurity lead and counselUsually excluded
Records on legal holdCannot be altered or movedGeneral counselLeft 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.

Question180-person SaaS company running its own platform650-person managed services provider
Who describes the records?Platform owner and SRE leadService delivery director and the ServiceNow platform owner
Who convenes?VP of engineeringService delivery director
Who sponsors?CTOCOO
Counsel branchEngineer names in reviewsClient contract terms for each managed environment
Other consentNonePrivate equity sponsor
Route lengthTwo peopleThree 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.

  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

I am the ServiceNow partner with admin rights on the instance. Can I start the conversation myself?

You can raise it with the service delivery director, but you cannot speak for the client. Admin rights let you describe which tables and years exist. Only the CEO, usually with counsel, can agree to discuss licensing.

What if the company is owned by a private equity sponsor?

Treat sponsor consent as one more box on the tree. Portfolio companies often need it for anything that treats company information as an asset. Note it in the handoff; SourceX will ask.

Do hosted customers have to approve before the company can apply?

Not before applying. Whether any customer-related content can be in scope is a question for the company's counsel and SourceX's rights review, which happen after the application, not before the introduction.

Sources

  1. refer.sourcex.si/terms
  2. docs.servicenow.com/bundle/paris-it-service-management/page/prod…
  3. support.pagerduty.com/docs/change-events
  4. eur-lex.europa.eu/eli/reg/2016/679/oj/eng

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