# Change collision referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/change-collision-recovery-referral-brief-template
Last updated: 2026-11-04

A change collision recovery introduction needs one page of metadata: what the company does and how big it is, which service management, monitoring and on-call systems hold the history, how many years they cover, a rough count of reviewed clashes, who owns the records, who can authorize a licensing discussion, the open rights question, and any documented access deadline. No change records, screenshots or review text. Fill the template below with the service delivery director, then let them forward it.

This template is part of the [change collision recovery guide](/guides/workflow-change-collision-recovery). It turns a conversation with the service delivery director into a handoff an executive can read in two minutes.

## The blank brief: eight fields, metadata only

Copy the fields into an email or document. Every answer is a fact the director can give from memory, a project plan or a count of titles. If a field is unknown, write "unknown" rather than guessing.

| Field | What to write | Where the answer usually comes from |
|---|---|---|
| 1. Company, size and task | Business type, full-time headcount at peak, one line on what a clash recovery is here | Director or HR, not a contractor list |
| 2. Systems | Plain-text names of the service management environments, monitoring, on-call and wiki tools | Platform owner |
| 3. Years of history | First and last year per system; when change events started | Platform owner, monitoring admin |
| 4. Volume | Approximate counts of changes, stored conflicts and clash reviews, with how they were counted | Director, from report totals or review titles |
| 5. Record owner | Who is responsible for each record class | Director |
| 6. Who can authorize | The CEO, who can approve a licensing discussion, plus counsel | The [who-can-say-yes tree](/questions/who-can-license-change-collision-recovery-records) |
| 7. Open question | The rights question nobody can answer yet | Director |
| 8. Deadline | Any documented access end date | Contract or decommission plan |

What never goes in the brief: change numbers, CI names, hostnames, alert payloads, review excerpts, customer names, engineer names, or a guess at value.

## How to fill each field without opening a record

**Systems and years.** The platform owner can say which tables exist and from when without exporting anything. ServiceNow stores a conflict against a change only when the change has a configuration item and planned start and end dates, so ask whether those fields were mandatory and from which year; before that, conflict results may be sparse. Write the year, not the reason.

**Alert links.** Ask the monitoring admin from which year alerts and incidents carry a reference to the change that preceded them. In PagerDuty, for example, change events do not raise incidents themselves; an incident shows up to three correlated changes from the previous 24 hours with a reason. That year is often the start of the most traceable history, because before it the link between a change and the alert it caused lived only in someone's written review.

**Volume.** Counts come from totals, not rows. "Roughly 40 clash reviews, counted from review titles" is the right level. Say how you counted so SourceX can judge the number.

**Open question.** Keep it in. For a managed services provider it is usually whether reviews that name hosted customers can be in scope at all. That tells SourceX where its rights review starts. The [incident and on-call introduction checklist](/resources/a-company-introduction-checklist-for-incident-and-on-call-records) covers neighboring record classes if the director mentions them.

**Deadline.** Write a date only when a document gives one: a decommission plan, a vendor contract end, a retention setting. No date is better than a guessed one.

## Completed example: a 260-person managed services provider (Illustrative)

A fictional company, written for this page. The numbers are invented and show the level of detail, not a real case.

| Field | Illustrative entry |
|---|---|
| 1. Company, size and task | Managed services provider, 260 full-time staff at peak; recovers when two separately approved changes conflict: detection, rollback, review and process fix |
| 2. Systems | Two ServiceNow instances being consolidated, a monitoring platform, an on-call tool, a team wiki for reviews |
| 3. Years of history | Changes for seven years; change events linked to incidents from year four onward |
| 4. Volume | About 40 reviewed clashes, counted from review titles; stored conflicts present from year three |
| 5. Record owner | Service delivery director for reviews and rollbacks; platform owner for change and configuration database tables |
| 6. Who can authorize | CEO, with the CTO and general counsel; service delivery director convenes |
| 7. Open question | Whether reviews naming hosted customers can be in scope |
| 8. Deadline | Old instance read access ends March 31 per the decommission plan |

Notice what the example leaves out. There is no change number, no host, no client name and no estimate of value. An executive reading it knows what exists, who is responsible and what is unresolved, which is all an introduction needs.

## Before you send it: a five-line check

Run through these with the director before the brief leaves the room.

1. **Headcount:** full-time employees at peak are 50 or more, counted without contractors.
2. **No record content:** every line is a count, a year, a system name or a role.
3. **Named authority:** field 6 names the CEO, who can approve a discussion, not the platform owner.
4. **Open question stated:** the rights question is written plainly, not softened.
5. **Deadline documented:** any date in field 8 comes from a plan or contract the director can point to.

If the brief fails line 3, go back to the decision tree before sending. If it fails line 1, the company does not qualify for the program.

## What happens after the brief is forwarded

The CEO decides whether the company applies. If it does, SourceX reviews the record classes, rights and qualification. Until then, buyer interest, the rights outcome for client-related records, the preparation needed and whether an offer follows all stay unknown.

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. Sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application.

The [client opportunity brief generator](/tools/client-opportunity-brief-generator) can turn the eight fields into a forwardable note, and the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner) shows how to frame it for an owner. If the executive asks why AI developers care about change and incident history, [AI agents in ITSM](/guides/ai-agents-itsm) and [ServiceNow incident data](/systems/servicenow-incident-data-for-ai-training) give the background.

## 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 all eight fields are filled and the five-line check passes, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before the director forwards the brief.

## Sources

- https://refer.sourcex.si/terms
- https://docs.servicenow.com/bundle/paris-it-service-management/page/product/change-management/task/t_RunManualConflictDetection.html
- https://support.pagerduty.com/docs/change-events
