Wind-downs leave accounts behind. People leave on fixed dates, administrators go first, and the person who knows the system best may still have a login weeks later. That makes the shortcut tempting for anyone trying to help. This page is about refusing it while still making a useful introduction.
Why a working password is not a path
Access and authority come apart the day an employee leaves. Security guidance treats a lingering login as something to close: NIST's control PS-4, Personnel Termination, asks an organization to "Disable system access within [Assignment: organization-defined time period]" when employment ends, and in paraphrase also covers revoking the authenticators and credentials tied to the person. A password that still works after a shutdown is a gap for the estate's controller to know about. It is not a door for an introduction.
SourceX's documents point the same way. Its screening questions are answered from a conversation, "never from files, samples or logins", and section 4.2 of the sample Channel Partner Agreement says: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." An introduction that leans on someone's old login has already left the program's shape.
Who controls the estate, and what former staff can still offer
Name the controller before anything else, with the date you checked. SourceX's screening page sets the rule for a closing company: the CEO may not be enough, and the estate's controller decides, with counsel. In a formal process that controller may be a trustee, receiver or assignee. Where nobody can say who that is, who can authorize a referral for a closed business and locating the authorized successor cover the search.
Former employees still matter as witnesses. They can say which systems existed, which years they cover, who ran them and when they were due to be switched off. All of that goes to the controller, and the controller decides what, if anything, reaches SourceX. A former employee can point; only the controller can decide. The case of a founder holding a physical copy is worked through in the founder has the hard drive.
The authorized-access handoff checklist
Three parts, filled in by the introducer from the controller's answers. Nothing on it requires opening a system.
Part A: what the introduction contains
| # | Item | Where it comes from |
|---|---|---|
| 1 | The controller's name and role, how the role was confirmed, and the date | A record the controller did not write, such as a court docket or appointment letter |
| 2 | The company's status today: wound down, in a formal process or sold | The controller |
| 3 | Systems by name and the years each covers | The controller, helped by former staff if the controller chooses |
| 4 | Who administers each system for the estate now, as a role | The controller; never a username |
| 5 | Known dates: subscription end, disablement, deletion | The controller's own notices and contracts |
| 6 | Preservation status | Counsel's word, dated |
| 7 | Fit facts: full-time headcount at peak, years of records, any rights notes | The controller |
| 8 | A closing line: nothing has been opened, signed into or copied | The introducer |
Part B: what never enters it, and what to do instead
| Offered or tempting | Do instead |
|---|---|
| A password, PIN, one-time code or recovery code | Decline it; how the estate opens its own systems is the controller's matter with counsel |
| A shared administrator account several people used | Mention to the controller that it exists; never use it |
| A password-manager entry or export | Decline it and do not store it |
| A screenshot taken inside a system | Do not accept or forward it; describe nothing from it |
| A former employee's offer to sign in and check | Ask them to tell the controller what they remember instead |
| A request to carry credentials to the controller | Refuse to be the courier; the sender contacts the controller directly |
Part C: wait and stop rules
- A fact could only be learned by signing in: it stays "unknown" in the introduction, and the introduction says so.
- Counsel has not cleared preservation: wait.
- The controller asks the introducer to sign in and look: decline, and pause until the controller can describe the records without the introducer.
- Nobody can confirm who controls the estate: stop.
Method note. Parts A to C follow SourceX's screening page, its program terms and the unsigned sample agreement, read on 2026-10-28, plus one NIST security control cited for how organizations treat a departed employee's access. The checklist gives no legal or security advice and has not been tested on real wind-downs; SourceX publishes no figures on how often a closing company's introduction leads to a license.
Preservation and transition constraints in a wind-down
- Deletion dates belong to the controller. Tell the controller the earliest documented date you know of; never act on it yourself. How shutdown dates interact with an introduction is laid out in the data introduction before a wind-down team disconnects systems.
- Who signed in, and when, may matter to counsel. A preservation duty can make any activity in a system a question for counsel, which is one more reason the introducer's answer to every login is no.
- Nothing runs for SourceX. No subscription is extended, no account reactivated and no system kept alive for an introduction.
- Credit does not reward speed. The first valid introduction in the 90-day window is credited once the company submits a verified application, and only one partner can be credited. Hurrying past the controller wins nothing.
A model introduction with no login behind it, or a stop note
A model introduction, sent only after the controller agrees:
"I am introducing [controller's name], [role] for [company], who has asked to hear about SourceX. The company peaked at about [number] full-time employees and ran [systems] from [years]. [Item] is unknown. Counsel has confirmed [preservation status] as of [date]. Nothing has been opened, signed into or copied for this introduction."
A stop note records the company, the date, which Part C rule applied and who was told. It ends the file cleanly. For an estate with an advisor in the middle, the stop memo in the data referral question for a liquidation advisor serves the same purpose.
Two offers of access (Illustrative)
Illustrative. Invented companies and facts; no outcome implied.
The former IT manager. A 140-person engineering consultancy closed this year and an assignee now controls its assets. Its former IT manager still has the administrator password to the document system and offers a restructuring adviser to sign in and count the project folders. The adviser declines and asks her to call the assignee instead. She tells the assignee which systems held project files and from which years; the assignee agrees to hear about SourceX. The introduction lists the systems and years and marks the folder count unknown.
The forwarded password. After a 90-person distributor winds down, a former founder emails a restructuring adviser the shared admin login so that SourceX can see what is there. The adviser deletes the message without using it and tells the founder that the estate's controller decides. Once the controller is identified, the adviser mentions that a shared login is still active; no introduction goes out until that controller agrees.
Fit, credit and reward without any login
For a closed company the headcount test reads the peak, not today's zero: 50 or more full-time employees at the high point, contractors excluded. The other checks are records the company itself produced over several years, rights it can grant, a controller who agrees to the conversation and fit with a current program. 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.
The introducer signs the Channel Partner Agreement before submitting. Any reward is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap for the company and its corporate group, paid separately and never taken from the company's payout. No one can say before SourceX's review what a closing company's records are worth or when any money would arrive.
What the checklist cannot fix
- Unknowns may be most of the brief. An introduction with many unknown lines is still honest; it may also be too thin for SourceX to act on yet.
- The controller may not know the systems. Former staff can help the controller, on the controller's terms, without the introducer in the loop.
- Some estates move slowly. A controller appointed months after the shutdown may find accounts already deleted; the checklist cannot bring back what is gone.
- Policies differ. A NIST control describes good practice for organizations that adopt it; it says nothing about what a particular estate did.
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 the estate's controller is named, agrees to the conversation and can describe the records without anyone signing in, register, set the controller's answers beside who qualifies and file the program terms version that applied with the checklist.