How to design a key employee retention plan that keeps IT admins through a wind-down

Why IT admins belong in a wind-down retention plan

In a wind-down, records are only as useful as someone's ability to get them out. That ability usually rests with a handful of IT staff who hold admin rights to email, file storage, identity, cloud accounts and backups, and they are often among the first to leave because their skills move easily to a new employer. A retention plan that covers finance and legal but skips those admins can leave the company, or later the estate, owning records nobody can reach.

The cost shows up everywhere records are needed: claims reconciliation, litigation, tax filings and, for qualifying companies, a data license. SourceX treats a company where nobody can export the data as a red flag, so a CRO who keeps the keys keeps that option open. Once nobody can reach the archives, a trustee may simply move to destroy them; see motions to destroy debtor books and records.

What to settle before you design the plan

• Legal posture. A chapter 11 debtor, a chapter 7 trustee, an assignee for the benefit of creditors and an out-of-court wind-down each have a different approval path for retention pay.
• Insider status. Have counsel decide who counts as an insider before any number is discussed. A head of IT with an officer title may be treated differently from a systems administrator.
• The access map. For every system, list who holds admin rights, who holds the multi-factor authentication device and where the recovery codes are kept.
• Renewal and cancellation dates. Note when each subscription renews, lapses or is scheduled for cancellation, and read the vendor's own terms on what happens to data afterwards rather than assuming.
• Budget. Retention pay and subscription costs need a line in the wind-down or DIP budget; DIP and forbearance sale milestones shows how to leave room for a records track.

If the case converts to chapter 7, the trustee will demand the same credentials; the guide to turnover of electronic records and passwords to a trustee covers that demand list.

How section 503(c) shapes retention pay in a bankruptcy case

Section 503(c) of the Bankruptcy Code sharply restricts payments that induce insiders to stay. In general terms, it requires findings that include a bona fide competing job offer and that the person's services are essential to the survival of the business, and it caps the amount by reference to similar payments made to non-management employees. It also bars transfers outside the ordinary course that are not justified by the facts and circumstances of the case, including to officers, managers or consultants hired after the filing. Read the current text with counsel; courts look closely at plans labeled as incentive plans to see whether they are retention pay in disguise.

Three practical consequences follow:

• Rank-and-file administrators are often the easier case, because they may not be insiders at all.
• Pay tied to verifiable work, such as completed exports and a delivered inventory, is easier to explain than pay for simply staying.
• Outside bankruptcy, in an assignment for the benefit of creditors or a board-led wind-down, stay bonuses are contract matters, though the assignee or board still answers for the spend.

Step by step: building retention around export milestones

1. List the keys. For each system, record the admin, the backup admin, the MFA holder and the billing owner.
2. Rank people by how hard they are to replace. A sole global administrator outranks a second helpdesk engineer. No single person should be the only route into any system.
3. Choose the structure. Combine a modest time-based payment with milestone payments, or use milestones alone where insider limits apply.
4. Write milestones you can verify. Examples: all mailboxes and shared drives exported to company-controlled storage with job logs; credentials handed to two named officers; break-glass accounts documented and tested; a data inventory listing each system, its years of history and its export status.
5. Match the retention period to the assessment window. Cover at least qualification and the inventory. If a license is signed, preparation and delivery may need a short consulting tail.
6. Add conditions. Confidentiality, no deletion or wiping without written instruction, return of laptops and MFA tokens, and a written assignment of any scripts or documentation the admin produces.
7. Get the approvals. Board or CRO sign-off, lender consent under the DIP or forbearance agreement, and court approval wherever counsel says it is required.
8. Pay on evidence. Release milestone payments against job logs, completed-export reports and an officer's sign-off, not verbal assurances.

Which roles to cover and what to tie pay to

Contractors, scripts and who owns the work

Wind-downs often convert departing admins into contractors, and that changes who owns what they produce. According to the Copyright Office's Circular 30 on works made for hire, when an employee creates a work as part of the job, the employer is treated as its author and owner. A commissioned work from an outside contractor gets that treatment only if it falls into one of the listed categories and both sides sign a written work-for-hire agreement. Put a written assignment in every contractor agreement so export scripts, runbooks and system documentation stay with the company.

Common mistakes

Illustrative example

Illustrative, with a fictional company. A 140-person logistics software business is winding down after a failed sale process. The CRO finds that two people hold every admin credential, and one has an offer elsewhere. The CRO sets a small payment at 30 days and the balance on three milestones: verified mail and drive exports, two officer-controlled admin accounts, and a completed data inventory. Counsel confirms neither admin is an insider. The exports finish in the third week, the company completes a SourceX qualification call, and the CRO can decide on a license with the records intact instead of guessing what a lapsed tenant once held.

What the retained team does once an introduction is made

The CRO's role after the introduction is light, but it depends on the people you kept:

1. A partner shares a referral link or submits the referral form, or the company applies itself.
2. SourceX confirms the basics: 50+ full-time employees at peak (contractors excluded), a documented history of several years, records spread across many business systems, the right to license them, and an authorized sponsor, here the CRO or board.
3. The retained admins build the data inventory from system metadata, without moving any records.
4. The company and SourceX settle the price and terms first; buyers only see the opportunity after that.
5. Buyers, meaning AI labs and other data buyers, assess it; responses typically come within about two weeks once the company is deal-ready.
6. After signing, the admins prepare the agreed records under redaction rules set in the agreement, delivery follows and the company is paid.

The full baseline is on who qualifies.

Rewards for CROs and wind-down advisors

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and rewards become payable only after the buyer pays and SourceX receives its fee. Because the reward comes out of SourceX's own fee, the company's proceeds are untouched; rewards are not guaranteed.

A CRO serving under a court-approved engagement should not accept third-party compensation tied to the case without counsel's advice and whatever disclosure the court requires. The company can apply on its own if that is cleaner.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

Next step

This week, list every admin credential and who holds it, then put the people behind them into the retention plan. If the company may qualify, register as a partner to introduce it, or let the company apply itself at sourcex.si/apply.