The trigger is useful because of the sorting, not the event. Most firms never write down which material is theirs. A firm that has just finished a handover has done it under contract and against a deadline, and its transition lead can describe the result from memory.
What a handover makes a services firm settle
A knowledge transfer is the planned handover of how a piece of work is done: documents, training, shadowing and a date on which each area passes to the new owner. Some contracts spell it out in detail. One published example is the U.S. federal clause 52.237-3, Continuity of Services: on the contracting officer's written notice, the contractor provides phase-in, phase-out services for up to 90 days after the contract expires and negotiates a plan with the successor, including a training program and a transfer date for each area of work (our paraphrase of a search excerpt from Acquisition.gov). Commercial contracts set their own terms, often less formally.
However it is written, the handover splits the firm's material in two. Deliverables, client data and client-specific documents leave. The firm's own methods, training and internal records stay. That split is the first thing SourceX's screening asks about. Its screening profile looks for material the company "owns", or "can license it without breaching client confidentiality, employee privacy or third-party contracts", and lists material that "belongs to the company's clients rather than the company" among things usually not a fit.
Which side of the handover your contact sits on
This page is about the firm that handed the work over. The other parties have their own questions.
| Your contact | Their position after the transfer | Where to read |
|---|---|---|
| The services firm that handed the work over | It kept its own methods and internal records and returned the client's | This page |
| The client that brought the work in-house | It now writes its own records and may hold some of the provider's years | When a company brings outsourced work back in-house |
| The client whose long contract ended | It is sorting what came back and what the provider kept or deleted | The referral questions after a long-term vendor contract ends |
| The successor provider | It has just started and holds little history of its own on this client | Not a trigger yet |
A transfer inside one company, from a retiring owner to a successor, is a different subject again, covered in knowledge transfer from a retiring owner.
The owned-versus-client content review
Seven content families, sorted by the firm's own leaders: usually the CEO with the transition or delivery lead. The partner writes down their answers at the level of family, years, system and whose it is, and never sees, copies or asks for the material itself. The sample Channel Partner Agreement gives a partner no authority to share a supplier's records (section 4.2), and nobody collects them for SourceX.
| Content family | Usually whose after the handover | What decides it | For the introduction |
|---|---|---|---|
| 1. Work delivered to the client: reports, designs, configurations, client runbooks | The client's | The contract's deliverables or work-product clause | Leave out |
| 2. Client data the firm processed: tickets, cases and records in the client's tools | The client's | Ownership and confidentiality clauses, and whose system holds it | Leave out |
| 3. Transfer material made for this handover: the plan, recorded training, shadowing notes | Often the client's, as part of the transfer | The transition or exit terms | Leave out unless counsel says otherwise |
| 4. The firm's own procedures, playbooks and templates, written before or outside the engagement | The firm's, usually | Any pre-existing materials clause | Talk about |
| 5. The firm's internal training curricula and onboarding courses | The firm's, usually | Who wrote it, and for which audience | Talk about |
| 6. Internal quality reviews, escalation notes and staffing records about the firm's own way of working | The firm's, though they may name clients | The confidentiality terms of each client named | Talk about; client mentions go to counsel and SourceX's rights review |
| 7. Copies of client material kept after the handover | Whatever the contract allows | Return or deletion duties | Settle first whether the firm may keep them at all |
Families 4 to 6 are the conversation. Two checks apply to them before anyone is introduced. The firm must be able to confirm the material has never been licensed for AI training, one of the confirmations SourceX's supplier process asks for, along with rights to license and lawful collection of any personal data. And the firm needs full-time headcount of 50 or more at its peak, contractors excluded, which a services firm built on subcontractors may not reach.
How the clauses behind families 1 to 3 usually read is explained in what a customer data ownership clause decides, and the process-material side for support outsourcers in how outsourced support providers can assess rights over process materials.
Method note. The families and their default owners are this page's construction, drawn from SourceX's screening profile, the supplier confirmations on its how-it-works page and section 4.2 of the sample agreement, all read on 2026-10-27, with clause 52.237-3 as one published example of a formal handover. "Usually" means only that: a contract can move any family to the other column, and the firm's counsel and SourceX's rights review decide.
When to ask: after sign-off, not during the handover
The question waits for the work to be finished and the client relationship to be settled.
- During the transfer, hold. The firm's people are working for the client, and a licensing question then sounds as if it concerns the client's material.
- After sign-off and any support period, ask. Formal transfers end on dates the contract sets, so the CEO knows when the firm is free of them.
- After a disputed or bitter exit, wait. If the firm lost the client in a rebid or the handover ended in an argument, let the CEO raise the subject.
- If the firm still serves the client in other ways, say plainly that only the firm's own material is in question.
Two lines never move. Nobody approaches the client or the successor about the firm. And if you advised the client on the transfer, what you learned about the provider came to you for the client and stays there.
Transition lead, sponsor and the CEO who decides
Three people matter, and only one decides. The transition or delivery lead knows what moved and what stayed, and can describe the families. A sponsor, often the head of delivery or quality, may carry the idea internally. The firm's CEO alone decides whether the firm talks to SourceX, and signs for it.
Check four facts before the question goes out. Is the firm part of a group? A company and its corporate group share one reward cap, and in a platform with add-ons SourceX's screening guidance names the platform CEO as the decider for the whole group. Has it been acquired? Then the acquirer's CEO decides. Has it ever applied to, emailed or held an account with SourceX? Then it is a duplicate under section 3 of the terms and earns no credit. And who will submit? Only one partner can be credited, and that person signs the Channel Partner Agreement first.
The single question, and the note that follows it
Ask once, in the CEO's own channel. A version that keeps the client out of it (Illustrative):
Now that the handover to [client] is signed off, the line between what you passed on and what you kept is unusually clear. Would you want a short conversation with SourceX about whether the material that stayed yours, your own procedures, training and internal quality history, could be licensed for AI training and evaluation? Nothing the client received would be part of it, and it is entirely your call. If it went ahead, SourceX could pay me a referral reward; your firm's payout would be the same either way.
Then write one dated note: the question as sent, the CEO's answer in a sentence, the families the CEO named, the next step and who takes it. If the answer is no, record it and do not raise the subject again at the next handover.
A service desk handover, sorted (Illustrative)
Illustrative. A generic firm and client with invented facts; no outcome implied.
A 240-person IT service desk provider completes a 12-week transfer of a manufacturer's support back to the manufacturer's own team, signed off in August. The transition lead sorts the families with the CEO:
| Family | Answer | Status |
|---|---|---|
| Ticket history | In the manufacturer's own service tool since day one | Client's; left out |
| Client runbooks | Written for the manufacturer's systems, delivered under the contract | Client's; left out |
| Technician training curriculum | Written in-house since 2014, used for every client | Firm's; talk about |
| Internal quality scoring | Since 2016, across all clients; some reviews quote client tickets | Firm's; client mentions to counsel and rights review |
| Retained copies | The contract required deletion within 30 days of handover; confirmed done | Nothing kept |
In October the partner asks the CEO the single question. The CEO wants a conversation about the curriculum and the quality scoring, the firm applies itself, and the partner who had agreed to submit does so with a dated note of the CEO's yes.
When a finished handover points the wrong way
- Client-shaped material. In some firms almost everything of value was written for one client and left with it.
- Methods clauses. Some contracts give the client rights in methods developed during the engagement; counsel reads them.
- Size. A firm that delivers through subcontractors may fall short of 50 full-time employees at its peak.
- Earlier licensing. Material already licensed for AI training is out, however well it is sorted.
- A lost client is a sore subject. Many handovers follow a lost renewal, and the CEO may not want the conversation for months.
- No published figures. Nothing has been published on how often firms that complete a transfer are introduced or accepted; log your own questions and answers.
Other trigger guides for business changes sit in the guides library.
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 a firm's handover is signed off and its leaders have sorted what stayed theirs, create your partner account, check the firm against who qualifies, and read the program terms before the single question reaches the CEO.