The responsible handoff from wind-down advisor to SourceX: an authority-and-preservation handoff packet that passes the conversation to whoever controls the estate, carries counsel's constraints in counsel's own words, and ends the advisor's part on a named date

Short answer

A responsible handoff moves a conversation, never records. Once whoever controls the estate has agreed in writing, the advisor sends an eight-item packet: the entity and its status, the controller, the controller's written agreement, counsel's preservation position in counsel's own words, dated system and storage events, the controller's fit statements, the advisor's role and reward disclosure, and what the advisor will not do. From then on the controller deals with SourceX directly, and the advisor's part ends on a date both have agreed.

Visual briefFull-size diagram
Four swimlanes, custody, control, preservation and advisor, cross a vertical line marked handoff date. Records stay put in the custody lane; control moves from the controller alone to the controller with SourceX; preservation reads counsel's words throughout; the advisor's lane holds an eight-item packet that ends at the handoff and continues only as a thin dashed line marked news only. A note reads no copies, no logins, no value talk.
Illustrative handoff timeline matching the freight forwarder case on this page; no recovery, amount or timing is implied.

The wind-down guides on this site get an advisor to the controller's yes: the shutdown decision timeline for timing, and the liquidation advisor's inquiry checklist for the ask. This page starts where they stop: the moment of handing over, and what responsibility looks like afterward.

Two receivers: the estate's controller and SourceX

The handoff runs from the advisor to two parties at once: the controller, who decides, and SourceX, which talks to the controller from then on.

On the estate side, SourceX's screening page leaves no shortcut. For a wound-down company or one in a formal process, "The CEO may not be enough; the estate's controller decides." The controller is "Whoever directs that entity now: its board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process," and the page's first route for such a company is "The controller of the estate, with counsel." The advisor confirms who that is, as of the handoff date, through the controller's counsel.

On SourceX's side, the program lets the advisor step back. Section 2 of the terms says SourceX "may communicate directly with a referred company without affecting valid attribution," and the sample Channel Partner Agreement says the partner "need not join every call, email or negotiation." A responsible handoff uses that room rather than keeping the advisor in the middle.

The authority-and-preservation handoff packet

Eight items, written by the advisor and read and corrected by the controller before anything is submitted. Each states who said it and when. None of it is copied from the company's records.

ItemWhat it saysWhose statementNever included
1. Entity and statusLegal name, status, and the date and source of that statusThe controller's counselYour own reading of registry entries
2. ControllerName, role and the date control beganThe controller's counselYour view on whether an appointment is valid
3. Written agreementThe controller's dated agreement to a licensing conversation, and whom SourceX should schedule withThe controllerAnything suggesting the advisor speaks for the estate
4. PreservationWhether preservation instructions exist, and who owns themThe controller's counselThe scope, documents or reasons behind any instruction
5. Dated eventsStorage end dates and system disconnection or deletion dates the controller knows ofThe controllerRequests to vendors, which are the controller's to make
6. Fit statementsPeak full-time headcount and its year, years of records, record families named at metadata levelThe controllerSamples, file lists, screenshots or volumes read from systems
7. Advisor's roleWho engaged the advisor and when that ended, partner registration, agreement signed, reward disclosureThe advisorAny statement about what the estate will receive
8. What the advisor will not doNo copies, logins, indexing, negotiation or value statementsThe advisorExceptions made "to help"

Item 3 needs care. The controller may name someone to handle scheduling, but authority stays with the controller, and the packet says so in plain words.

Item 6 rests on SourceX's screen: headcount at peak rather than today's, counting full-time employees and leaving contractors out, plus documented history and the rights to license. The controller states these; the advisor does not estimate them.

Item 7 deserves the most care. Any reward is paid by SourceX separately and, in section 4's words, "is never deducted from the supplier's agreed compensation," so the company receives the same amount with or without a partner. Whether an advisor who was engaged by the company or the estate may accept a reward at all is a question for the advisor's own counsel and the controller, settled before item 7 is written. The partner must also have signed the Channel Partner Agreement before submitting anything (terms, section 1).

Method note. The eight items apply SourceX's who-qualifies page, its terms (version 2026-10-22.2, since replaced by version 2026-11-04), its trust and process pages and the unsigned sample Channel Partner Agreement (version 2026-10-19) linked from terms section 9, all checked on 2026-10-28. The packet transfers statements, not judgments: it does not test authority, preservation duties or rights, which belong to the controller's counsel and to SourceX's review, and it has not been tested against completed estate introductions.

One estate across the handoff (Illustrative)

Illustrative. The company, the advisor and every date are invented; no recovery, amount or timing is implied.

A 340-person freight forwarder stopped trading in May 2026, and in June its board made an assignment for the benefit of creditors. A turnaround consultant whose engagement ended at the assignment is a registered partner who has signed the Channel Partner Agreement. In September the assignee's counsel confirms that the assignee controls the company and wants a conversation about the forwarder's shipment exception and claims records.

DateCustody: where records sitControl: who decidesPreservation: counsel's positionThe advisor's part
2 Oct 2026Hosted platform, paid by the assignee until JanuaryThe assigneeInstructions exist and counsel owns themDrafts the packet and sends it to the assignee to correct
9 Oct 2026UnchangedThe assigneeUnchangedThe assignee corrects item 5; the advisor submits the introduction
10 Oct 2026UnchangedThe assignee, now talking to SourceX directlyUnchangedHandoff date: the advisor confirms in writing that their part has ended
November 2026UnchangedThe assigneeCounsel updates its instructionsNothing; counsel and the assignee handle it
December 2026A former employee says a laptop holds a partial copyThe assigneeUnchangedTells the assignee's counsel what was heard and from whom; asks for nothing

The packet never mentioned what the preservation instructions cover, and the advisor never learned it. The December row is the advisor's only re-entry, and it carries news, not records.

The advisor's part after the handoff date

What stops at the handoff:

  • Acting as the channel. Questions from SourceX about the estate go to the controller, and the controller's questions about SourceX go to SourceX. The advisor relays neither.
  • Any contact with records. No copies, logins, indexes or file lists, then or later. Former employees' passwords are not a route, even when offered. The sample agreement "gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems," and says a partner "must not collect or retain supplier dataset copies through the referral program without separate written authorization."
  • Talking value. No estimates to creditors, the controller or anyone else. A payout is fixed only in a signed Dataset Deal Confirmation, and the conditional recovery discussion guide explains why no number belongs with the advisor.
  • Following the deal. The sample agreement gives a partner what it needs "to track its own referral and reward, using generic stages or reference codes." That is all the advisor should expect, and all they should pass on.

What continues:

  • Passing on what the controller may not know. A deletion date, a copy someone mentions, a vendor notice that reached the advisor by mistake. Tell the controller's counsel what was heard and from whom, then nothing more.
  • Answering the controller. If the controller asks about history, answer from memory at the level of systems and years, and say where memory is unsure.
  • Respecting a change of control. If a new trustee or buyer takes over, the old yes does not carry across. Whether to continue is the new controller's decision.

A sale process or filing that arrives after the handoff follows the pause-trigger review sheet; a new preservation instruction follows the counsel-led escalation map.

When no packet should be sent

Do not send a packet, or submit an introduction, when:

  • counsel has not confirmed a controller, so item 2 is empty;
  • the controller's agreement is spoken only, or arrives through someone else;
  • counsel says the archive should not be discussed while instructions run;
  • the controller says the records were already licensed for AI training, one of the things SourceX's process page says a licensing company confirms has not happened;
  • the company, its controller or its former team already applied to or corresponded with SourceX, which section 3 of the terms treats as a duplicate. The controller can carry on directly, and no handoff is needed.

In each case write a dated note of the reason, the evidence and what would reopen it, using the no-go reason and evidence register. A successor who appears late is checked with the successor contact verification plan.

Credit and payment once the advisor has stepped back

Stepping back costs nothing under the terms. Section 2 says "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application," and that an earlier link click alone does not decide credit. SourceX's direct contact with the controller does not affect valid attribution. The terms set no pause in the 90-day window for an estate's own process, so submit only when the controller is ready to apply.

If a reward follows, section 5 starts a 60-calendar-day clock from whichever happens last: the Acquisition Partner accepting the complete, validated dataset in writing, or the completed handoff of that dataset to it. Anything still outstanding when the clock runs out is paid as soon as it is satisfied, and the clock does not restart. Nothing earlier, not an introduction, a call or a signature, makes anything payable.

How a careful handoff still goes wrong

  • Control can change. The packet is true on its date; a new appointment after the handoff makes item 2 stale.
  • Controllers stall. A controller may agree and never apply. The advisor does not chase on SourceX's behalf: one reminder to the controller, then a note.
  • Reward objections surface late. A creditor may object to an advisor being paid at all. Item 7 and the advisor's own counsel come first, not afterward.
  • The packet grows. Each helpful addition, a file list, a screenshot, a value range, turns a handoff into custody or a promise. Eight items is the ceiling.
  • Review still decides. A clean handoff to an authorized controller can end in a decline for rights, relevance or demand.

A measurable check. For your next three estate handoffs, note the handoff date and count every contact you have with SourceX or the controller about the company afterward. More than two per estate means you are still in the middle. Other wind-down guides sit in the guides hub.

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.

Before the handoff date, an advisor who is not yet a partner should register and sign, confirm the controller's fit statements line up with the published screen, and reread the terms on credit, so the packet goes out once and the advisor can step back cleanly.

  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

Should the advisor stay on the calls between SourceX and the controller?

There is no need. Section 2 of the terms lets SourceX communicate directly with a referred company without affecting valid attribution, and the sample partner agreement says the partner need not join every call, email or negotiation. Stepping back keeps authority visibly with the controller.

The controller asks the advisor to send SourceX a file listing to save time. Should they?

No. The sample agreement gives a partner no authority to share a supplier's inventory or records. The controller describes the records in the company's own application, and SourceX's trust page says the supplier decides which systems, records and date ranges are in scope.

What if a new trustee replaces the controller after the handoff?

The earlier yes came from someone who no longer decides, and the new controller chooses whether to continue. If their counsel asks, say whom you dealt with and when; do not reopen the conversation yourself.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. sourcex.si/trust
  5. sourcex.si/how-it-works

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