This agenda is part of the ITSM consolidation guide for ServiceNow consultants, which explains why change-failure chains are worth noticing. This page is for the meeting itself: who sits in, what each block asks, how to read the replies, and the close.
Who sits in, and when to book it
Book it once the target instance and the merge approach are agreed, and before field mapping is signed off. People still remember how each legacy instance handled failed changes, and the mapping can still move.
| Attendee | Why they are needed | Blocks |
|---|---|---|
| Change manager or change board chair | Knows how failed changes are handled and where decisions get written | 2 and 3 |
| Platform owner or admin | Knows which fields are filled, which tables are archived and the mapping plan | 1, 2 and 4 |
| Incident or service desk manager | Knows whether agents set the caused-by-change reference consistently | 2 |
| CEO or owner, with the CIO | The CIO owns the platform decision; the CEO can authorize a licensing discussion | 4 and 5 |
Send a one-line purpose: "25 minutes on what the old instances record about changes that went wrong. Description only; no exports." If a managed service provider runs the desk, invite its service lead to answer block two, with the company's owner present for blocks four and five.
Chairing rules that keep it to 25 minutes
A short slot fails when one block swallows the rest. Agree these before minute zero.
- You chair; someone else keeps time. Ask the platform owner to call each boundary aloud. A visible timer on the shared screen helps more than reminders.
- One parking lot. Questions about the target design, licensing costs or workflow redesign go on a list for the project team. This slot is only about history.
- Answers as words, not proof. If someone offers to share their screen or pull a list, thank them and decline. A description is the whole output.
- A four-column note. Block, answer (yes, partial, no, unknown), who said it, follow-up owner. You read it back at minute 21.
- End on time even if block four is open. An open item with a named owner is a better close than an overrun that loses the decision maker.
Five blocks in 25 minutes
Illustrative. A 540-person healthcare billing company is merging a legacy ServiceNow instance from an acquired subsidiary into its main instance. The consultant runs this agenda during mapping design.
| Minutes | Block question | Answered by | What a good answer sounds like |
|---|---|---|---|
| 0-3 | How many instances or tools are merging, and when is cutover? | Platform owner | "Two instances; cutover is in the migration plan; the old one goes read-only after." |
| 3-10 | When a change breaks something, does the incident point back to that change? | Incident manager and change manager | "Yes. Major incidents must name the triggering change, in both instances, since 2020." |
| 10-16 | Where is the decision to back out or fix forward written down? | Change manager | "Every normal change carries a restore plan; the actual call goes into the notes and the change board record." |
| 16-21 | What happens to archive tables and the retired instance, and who owns the history? | Platform owner and CIO | "Archived years are out of the current scope; the CIO decides on the old instance." |
| 21-25 | Would the company like to hear how licensing of approved records works, and who would lead it? | CEO or owner | "Yes, I can authorize it; the head of IT operations is the working contact." |
Block two is why you booked the room
On a standard ServiceNow incident form, the Caused by Change field holds the number of the change request that resulted in the incident. The link is stored on the incident, so a migration that maps changes and incidents separately can bring both across and lose the join between them. Ask whether teams fill it in, and since when; do not ask anyone to run a report to show you.
Block three finds the reasoning
The Backout plan field on a change request holds what is needed to restore the system if an implementation fails. That is the plan, not the decision. The decision to use it, or to fix forward instead, sits in work notes, change board discussion or a post-implementation review. Ask which of those exist in writing and which live only in meeting memory.
Block four is about the years nobody mapped
ServiceNow data archiving moves older records out of live tables into archive tables. A mapping scoped to live tables can leave the oldest change history behind without a decision ever being made.
Reading the replies in the room
| Reply | Likely meaning | What to do before the next block |
|---|---|---|
| "The field exists, but only the major incident team uses it." | The chain is partial and concentrated in high-severity events | Note "partial, major incidents" and the years |
| "We renumbered changes when we merged last time." | An earlier consolidation may already have broken links | Ask whether a cross-reference table was kept |
| "Reviews are in Confluence." | Reasoning sits outside ServiceNow and outside migration scope | Note the system name only |
| "The MSP owns the old instance." | Rights depend on the service contract | Mark ownership "to confirm"; do not proceed past block four without the owner |
| "Archive tables are being dropped." | The oldest years are at risk | Hand it to the archive context checklist |
A good meeting ends with a description like "partial chain, four years, two instances, reviews in a wiki, CEO to decide". That is enough. Background on what complete ticket records look like is on the ITSM ticket history page.
Before the decision block: disclosure and fit
Three things are said aloud before minute 21.
What SourceX does. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. The meeting shares nothing.
Your interest. You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward under the terms, funded separately and never deducted from the company's payout. Illustrative only: an $800,000 payout to the company on its first qualifying transaction would mean a USD 120,000 reward (15%, since that exceeds USD 50,000 plus 5%); the program has no cap, and this is not a promise of earnings.
Fit. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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.
Unknown until SourceX reviews it: demand for change-failure records, the rights review result including provider contracts, de-identification of names in work notes, any offer and any reward. Partners never ask for or handle tickets, work notes or CAB minutes.
Closing on one of three outcomes
| Outcome | Fits when | Who records it | Next action |
|---|---|---|---|
| Introduce now | Block two is yes or partial, the company owns the history, the owner opted in | Consultant | Send the introduction email to the named contact |
| Revisit after cutover | Answers depend on the final mapping or an admin's check | Platform owner | Agree a date tied to the documented cutover |
| Stop | The owner declines, or the provider controls the records | Consultant | Note the reason; the consolidation proceeds as planned |
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. The ServiceNow incident data page and the ITSM agents guide give more context, and the portfolio review agenda shows the time-boxed method in an investor setting.
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 the meeting closed on "introduce now" with a named contact, register as a partner, confirm the company against who qualifies, and read the program terms before you write the introduction.