# Preservation specialist data referral: handoff | SourceX

Canonical: https://refer.sourcex.si/guides/a-preservation-specialist-s-role-in-a-company-introduction
Last updated: 2026-11-04

A preservation specialist is a messenger in a company introduction, never the source of its facts. You were engaged to protect an archive against alteration or destruction for a client, usually counsel, the company or an estate's controller, and what you hold or learned belongs to that engagement. If licensing might interest the records' owner, say so once to whoever engaged you, without describing anything you preserved, and let the company's controller decide. You make the introduction only if the controller wants that and your engagement and counsel allow it.

"Preservation specialist" here means a forensic collection firm, an e-discovery vendor, a records or archive firm engaged for a hold or a wind-down, or a consultant hired to keep data intact through a transition. The general case of anyone holding a copy is covered in Wave 9's [custodian checklist](/guides/an-archive-custodian-is-not-always-the-licensing-decision-maker), and counsel-led escalation under a hold in [the litigation hold map](/questions/litigation-hold-records-can-they-be-shared). This page is the narrower seat: the specialist who was hired to preserve, whose own reports describe the archive in more detail than anyone else's.

## Protection against loss is the whole mandate

EDRM's reference model defines the stage in one line: "Preservation – Ensuring that ESI is protected against inappropriate alteration or destruction." Read it as a scope statement. Preservation keeps records as they were; it does not describe them to outsiders, open them to new purposes or decide what happens to them next. A specialist who suggests licensing has stepped outside that line, which is why the suggestion travels as a single sentence through the engagement rather than as anything the engagement produced.

The specialist's knowledge is also unusually detailed. Collection reports, custodian lists and hit counts are exactly what a licensing conversation would like to see. That detail is the reason none of it travels.

## Who hired you, and who decides about licensing

Three parties sit around every preservation engagement: the one that engaged you, the one that controls the company today, and counsel, who sets the scope of what must be kept. They are often different people. SourceX's screening page defines the controller as "Whoever directs that entity now: its board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process," and warns that in a formal process the CEO alone may not be enough.

| Engagement | Who engaged you | Who decides about licensing | Your one sentence goes to |
|---|---|---|---|
| Litigation hold at an operating company | Outside counsel | The company's CEO | Counsel, who decides whether to raise it |
| Wind-down preservation before any filing | The company | Its CEO, until a formal process starts | The person who signed your engagement, once you confirm they still control |
| Preservation for a trustee, receiver or assignee | That controller or its counsel | The controller, with counsel | The controller, through its counsel |
| Subcontract under another vendor | The prime vendor | Whoever the prime vendor's client answers to | The prime vendor |
| Integration preservation after an acquisition | The buyer or its counsel | The acquirer's CEO | The buyer's counsel or project lead |

In every row the sentence reaches the controller, if at all, through the party that engaged you. Going around that party, even to the right person, steps outside the engagement you were hired under, and the controller should hear the idea from someone it already trusts. SourceX's screening page also lists introductions made without the decision maker's knowledge among the usual poor fits.

## The specialist-to-owner handoff guide

Seven steps, each with what you do, what you never do and what you keep. The guide hands a topic to the owner; it never hands over records.

| Step | What you do | What you never do | What you keep |
|---|---|---|---|
| 1. Name the engagement | Write down who engaged you, the scope, the confidentiality terms and what ends the engagement | Treat an interesting archive as a new piece of business | One line in your own file |
| 2. Check your own seat | Ask your own counsel whether your engagement and obligations let you raise an unrelated commercial topic, and whether you would register as a partner | Register first and ask afterwards | Counsel's answer, dated |
| 3. Write the sentence | Mention SourceX and say the decision is the controller's, with no counts, names or findings from your work | Quote your collection report, custodian list or data map | The sentence as sent |
| 4. Time it | Send it after urgent preservation work is done and never during active collection | Use a deadline in your own engagement as urgency for licensing | The send date |
| 5. Let them carry it | The party that engaged you decides whether the controller hears about it | Contact the CEO or the estate directly | Their reply, or a note that none came |
| 6. Step back or introduce | If the controller wants a conversation, the company applies itself, or you introduce it if you are registered, have signed the Channel Partner Agreement and are allowed to | Attach anything, or describe the records beyond what the controller says | The introduction text |
| 7. Close the loop | Preserved copies follow the engagement's release, return or destruction instructions | Extend retention "in case licensing happens" | A handoff or stop record |

Model wording for step 3 (Illustrative): "Separately from our engagement: SourceX licenses business records directly from companies for AI training and evaluation. Whether that is worth a conversation is a decision for whoever controls the company, and nothing from our preservation work would be part of it. I mention it once and will not raise it again unless you ask."

**Method note.** The table applies the controller definition, the formal-process caution and the poor-fit list on SourceX's who-qualifies page, the program terms and the first-step description on its how-it-works page, all read on 2026-10-28, with EDRM's definition of preservation as the boundary of the engagement. It sorts roles and timing. It does not read engagement letters, decide what must be preserved or say whether any reward could be accepted, and it has not been tested on completed introductions.

## Work product that must never become a referral summary

A specialist's files describe an archive better than any summary a partner could write. That is why each of these stays inside the engagement:

- **Collection reports and chain-of-custody logs.** They record what was taken, from where and by whom, for the legal duty they serve.
- **Custodian lists and data maps.** They name people and systems in detail the controller may not want shared.
- **Search terms and hit counts.** They reflect counsel's strategy as much as the archive.
- **Hash manifests and file inventories.** They are a list of the records in all but name.
- **Screenshots from review platforms.** Each is a new copy, as [the no-copy process map](/guides/how-to-avoid-creating-a-new-copy-of-a-sensitive-archive) explains.

None of it is needed. SourceX's first step for a company is "A few questions, no files": the company lists its systems and years of history, and no records are shared at that stage. The controller can answer those questions from its own knowledge.

## Preservation clocks that outrank any introduction

Several clocks run beside an engagement, and each one outranks a licensing idea.

- **An active hold.** While counsel holds records, a conversation that touches them waits for counsel's scope. Wave 9's [pause guide](/guides/when-a-restructuring-team-needs-to-pause-licensing-discussions) lists the triggers that stop discussions during a restructuring.
- **A change of controller.** A filing, an appointment or a sale can move the decision while your engagement continues unchanged. Recheck who controls before step 5.
- **A release.** Release instructions decide what happens to preserved copies. Follow them; a licensing hope is never a reason to hold a copy longer.
- **A storage end date.** If your firm also stores the media, the end date belongs to the account holder, and [the storage-deadline checklist](/guides/the-archive-review-before-a-storage-contract-ends) carries it to the controller.
- **A value question.** A restructuring may want to know what records are worth. Never offer a figure; [the conditional discussion guide](/guides/how-to-refer-a-business-in-restructuring-without-promising-recovery-value) shows what each stage can honestly support.

## Two engagements, two outcomes (Illustrative)

Illustrative. Composites built for this page; no real firms, companies or outcomes.

**The records firm and the assignee.** A records firm is engaged by an assignee's counsel to preserve the project archive of a 150-person engineering consultancy whose assets passed into an assignment. Once the firm has verified the preserved set and reported to counsel, it sends the step 3 sentence to counsel. The assignee asks to hear more. The firm's own counsel reads its engagement letter, which bars side arrangements during the engagement, so the firm does not register; it tells counsel that the estate can apply to SourceX itself. The assignee, as controller, decides to do so. The firm keeps the sentence, counsel's reply and the date, and nothing else.

**The subcontractor during active collection.** An e-discovery vendor is collecting mailboxes for another vendor whose client is in active litigation. A technician remarks that the support archive "looks like exactly what AI companies want". The vendor's lead checks step 4: collection is under way and the hold is active. The sentence waits. The vendor records a stop with its reopen condition, the hold released and the prime vendor willing to carry a message, and says nothing to anyone else.

## When a specialist could be paid for the introduction

A reward is a second interest beside the engagement fee, and it has to be visible to everyone it could affect.

- **Who can sign.** The sample Channel Partner Agreement names the Partner as "[an individual, or entity type and jurisdiction]", so a firm can register as a partner. How a firm's account relates to its staff's own accounts is not settled by the published terms; SourceX decides it.
- **Whether you may.** Your engagement terms, your conflicts process and any professional obligations you carry come first. Ask your own counsel, and see [the conflict check before a data introduction](/guides/the-client-conflict-check-before-a-data-introduction) for the parties to run.
- **What you disclose.** Tell the party that engaged you and the controller, in writing, that SourceX could pay you if a deal completes, and that SourceX pays any reward separately: section 4 of the terms says it is "never deducted from the supplier's agreed compensation."
- **Order of steps.** Sign the SourceX Channel Partner Agreement before introducing anyone, as section 1 requires. Credit goes to the earliest valid introduction once the company follows with a verified application inside the 90-day window, judged on dated records; a link click alone decides nothing.
- **Fit stays the controller's to describe.** The company needs 50+ full-time employees at its peak, contractors excluded, years of records it created itself and the rights to license them. 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.

## Where the handoff guide falls short

- **Engagements differ.** Some specialists work under counsel's direction, others for the company or an estate directly; the guide reads none of the letters.
- **Knowledge cannot be unlearned.** Even a bare sentence reveals that you noticed something. If your engagement treats that as confidential too, the sentence itself may be out of bounds.
- **Controllers change mid-engagement.** The party that engaged you may lose control before your sentence arrives.
- **Silence is an answer.** If the party that engaged you does not reply, the file closes; there is no second channel.
- **No published results.** SourceX has not published how often specialist-originated introductions reach an application.

## 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 controller asks for an introduction and your own counsel agrees that you may make it, sign up through [partner registration](/register), measure the company against [who qualifies](/who-qualifies) and go through the [program terms](/terms) first; more restructuring guides are in the [guides hub](/guides).

## Sources

- https://edrm.net/wiki/edrm-model/
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
