This guide is for people who know change control from the inside: IT service management consultants, platform implementers who configure change modules, IT governance and audit advisors, and former change managers who now advise. "Introduce the process owner first" means first inside the company. The person you eventually introduce to SourceX is the CEO, or whoever the CEO designates to apply, once the CEO wants the conversation.
A change record, from request to review
NIST's guide to security-focused configuration management, SP 800-128, describes configuration change control as the process that "identifies the steps to move a configuration change from its initial request to eventual release into the operational environment". It places setting up the CCB in the planning phase and ties it to control CM-3, Configuration Change Control, in SP 800-53. Whatever a company calls the steps, a formal change process leaves a trail of the same shape: someone asks, someone weighs the risk, someone approves or refuses, someone implements, and someone looks back.
SourceX's change approval records page describes the same arc, the request, the review, the approval and the result, and lists ServiceNow, Jira and Azure DevOps as typical homes. It also says what AI developers look for: complete start-to-finish records and edge cases and failures, not only successes. By that test, a rejected change with the reviewer's reasoning, or a failed change linked to the incident it caused, says more than a long run of routine approvals.
Why the process owner comes before anyone else
Each role around a change sees one slice. The engineer who raised it knows the request. The board members know the meetings they attended. The tool administrator knows the fields and the retention settings. Only the process owner knows the design: which change types exist, which approvals happen inside the tool and which in email or chat, how emergency changes are approved after the fact, and when the process last changed.
That knowledge makes the process owner the right first conversation and the wrong final one. The program gives the CEO the authority to open a licensing discussion and to sign for the company. A change manager who loves the idea still has to take it upstairs, often through the CIO, and the CEO has to know about it: SourceX's screening guidance puts introductions the CEO has not been told about among the cases that usually do not fit.
The approval workflow owner map
Six steps, five columns. Fill it in conversation with the process owner and date it. The last column is the question that decides each row.
| Step | Who writes it | Where it usually lives | Outside content that can appear | Question for the process owner |
|---|---|---|---|---|
| 1. Request | The engineer or analyst raising the change | The change module of the service management or work tracking tool | A vendor's release notes; a client's own ticket | Can clients or vendors raise changes directly in your tool? |
| 2. Risk and impact | The requester, then the change manager | Risk fields and notes on the same record | Vendor advisories pasted in | Is risk scored by a rule, a person or both, and since when? |
| 3. Approval or rejection | Named approvers or a change board; standard changes come pre-approved | Approval entries and board minutes | A client approver's sign-off, in a provider's records | Which approvals happen outside the tool, by email or chat? |
| 4. Implementation | The implementer | Change tasks and deployment notes | A vendor engineer's notes under the vendor's own ticket | Do vendors implement under their own tickets? |
| 5. Review afterward | The change manager | Post-implementation review, linked incidents | Rarely any | Are failed changes linked to the incidents they caused? |
| 6. Emergency approval after the fact | The on-call engineer and the change manager | Retrospective approval on the record | Rarely any | How are emergency changes recorded, and roughly how many a year? |
Mark each step one of three ways: the company's own, owner named; owner named, outside content present; or nobody knows. A trail worth introducing has steps 3 and 5, the decision and the look back, marked as the company's own. Outside content is not a stop; it is a part to describe separately so rights review can scope it. "Nobody knows" on step 3 usually means the decisions live in inboxes, and the tool holds only the paperwork.
Then name the people, because the map's value is in showing who answers which question:
| Role | Can tell you | Cannot decide |
|---|---|---|
| Process owner (change manager) | Workflow design, change types, where each step is recorded, when the process changed | Whether the company licenses anything |
| Tool administrator | Fields, years retained, migrations, exports possible | Rights in vendor or client contracts |
| Change board members | How decisions were argued | Anything about the records as a whole |
| Counsel | What vendor, outsourcing and client contracts say | Whether the company wants to talk |
| CEO | Whether the company discusses licensing, and signs for it | What contracts allow, which counsel and rights review settle |
Original, mixed and unclear approval trails (Illustrative)
Illustrative. Three generic companies with invented details; nothing here describes an outcome.
A. The company's own trail. A 400-person regional insurer's IT department has run every change through one service management tool since 2017. Board minutes are attached to each normal change, rejected changes keep the reviewer's reason, and failed changes link to incidents. The head of service management, who owns the process, fills in the map with every step marked as the company's own. She briefs the CIO, the CIO raises it with the CEO, and if the CEO wants the conversation the insurer applies through your partner link.
B. Mixed third-party content. A 150-person managed service provider runs change management for about 60 clients in its own service platform. Most records describe changes to clients' systems, approved by clients' own staff. Its changes to its own internal systems, a few thousand a year, are its operating history. The client change records sit under client agreements, so they are described as a separate part for counsel and rights review, and the process owner says plainly that they are the bulk of the volume. Managed service providers meet this split constantly.
C. An uncertain owner. A 220-person manufacturer outsourced IT from 2018 to 2022 to a provider that ran change control in the provider's own tool. When IT came back in-house, an export of those four years landed on a file share, and nobody can find the outsourcing contract's terms on records. Changes since 2022 are plainly the manufacturer's own. The 2018 to 2022 share is marked "nobody knows" on ownership. If the CEO wants to explore it, the introduction goes ahead with that open question written down, and counsel and SourceX's rights review answer it.
Origin questions for the process owner, and the one only the CEO answers
The process owner can usually answer where each step came from: which tool, which years, whether a migration carried history across, whether clients or vendors write directly into records, and whether security-sensitive changes are tagged. That last point matters because SourceX's page lists excluding security-sensitive changes and removing names and hostnames among the preparation steps, so a company that already tags them has an easier description to give.
Rights are a separate matter. On SourceX's who-qualifies page a company has them when the material is its own, or when licensing it would not breach a duty to clients, to employees or under a third party's contract. Client sign-offs and vendor notes inside change records bear on the first and the last of those.
Before any of this, the company has to pass the published screen. Its full-time headcount must have reached 50 at some point, with contractors left out; its records must document years of operation; it must hold the rights; and its CEO must want to talk. 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. The question only the CEO answers is whether the company wants the conversation at all.
A first message to the process owner, with no tickets attached
Keep the first note short and the questions descriptive:
- Which tool holds change records, and since which year?
- Roughly how many changes close each year, and what share are standard, normal and emergency?
- Are rejected changes kept with the reviewer's reasoning?
- Are failed changes linked to the incidents they caused?
- Which approvals happen outside the tool?
- Do clients, vendors or an outsourcer write directly into the records, now or in the past?
- Have these records ever been licensed for AI training?
- Would you be comfortable raising this with your CEO, and through whom?
A yes to question 7 ends the conversation, because every SourceX supplier confirms its records were never licensed for AI training before. And if the process owner offers a sample export to prove how rich the trail is, say no thanks: a referral runs on descriptions of the records, never on copies, and SourceX's own first step with a company is a few questions with no files. For the wider service management history, see ITSM ticket history; for timing around a platform merger, see ITSM consolidation introductions.
Limits of mapping a change process from one conversation
- Designed versus practiced. A process owner describes the process as designed. If approvals drifted into chat years ago, the tool shows rubber stamps. Question 5 is the test.
- Process changes over time. A tool migration or a new risk model can split the history into eras with different fields. Date each era on the map.
- Thin approvals. A trail of standard changes with no reasoning records compliance, not judgment.
- Demand is decided elsewhere. Whether a current SourceX program wants change records from that industry is a review question, and the AI agents for ITSM guide explains why demand varies.
- Your own numbers are the only numbers. Introduction and license rates for change records are not yet published. A plain log of each map, the steps that scored as the company's own and what the CEO said will tell you more than any guess.
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 the process owner's map shows decisions and reviews the company wrote itself and the CEO wants to talk, create a partner account, test the company against who qualifies and read the program terms, which require a signed Channel Partner Agreement before any submission. Related workflow guides, including nonstandard contract approval records, sit in the guides hub.