This run sheet is part of the parent guide on telling binding end dates from planned cuts. This page is the meeting itself: the time boxes, who answers, what a useful reply sounds like and how to close.
The run sheet at a glance
| Minutes | Block question | Who answers | A useful answer sounds like |
|---|---|---|---|
| 0-5 | Which tools in the plan hold three or more years of workflow history? | IT lead, CFO | "The old help desk, the acquired unit's tracker and the CRM we are dropping." |
| 5-12 | For each tool, what written event fixes the end of access? | General counsel, procurement | "Non-renewal notice sent; the contract ends on the date in that letter." |
| 12-18 | Who can still run a full export before that date? | IT lead | "Two admins, both staying through cutover; nobody has tested an export yet." |
| 18-24 | Who owns these records, and who could authorize a licensing discussion? | General counsel, CEO or CRO | "The operating company owns them; the CEO decides, with lender consent to confirm." |
| 24-30 | After disclosure: does the owner want to hear more? | CEO or CRO | "Yes for the help desk, not yet for the rest." |
Send the five questions with the invitation so general counsel can bring the notices and court papers rather than describe them.
Block by block: what to ask and how to read the reply
Minutes 0-5: find the tools that hold history
Ask for the tools being cut or consolidated that hold at least three years of tickets, cases, projects, deals or messages. Ignore tools that only hold configuration. A good reply names systems and years; a weak reply is "everything in the plan". If the list runs past five tools, take the five with the longest history and park the rest.
Minutes 5-12: separate dates from plans
This is the block to protect. For each tool, ask what document fixes the date. Three kinds count: a notice the company has already sent, a court order on the contract, and the vendor's written policy on what happens to data after cancellation. Ask whether anyone has read that policy for this specific account, because contracts can override it. Examples of each are in the section on running the clock below.
"Q3 in the model" or "when the new platform is live" is not a date. Write "no date yet". Rejecting software contracts in Chapter 11 explains the court side if the company is in a case.
Minutes 12-18: check that someone can still export
Cost programs often remove the people who know the old tools. Ask who holds admin rights today, whether they stay through the end date, and whether a full export has ever been tested. A reply of "the admin leaves in the next wave" moves that tool to the top of the reduction-in-force IT checklist.
Minutes 18-24: name the owner and the approver
Ask which legal entity owns each tool's records and who can authorize a licensing discussion. In a court process, debtor's counsel should say whether a license needs court or lender approval. A good reply names a role, not a team.
Minutes 24-30: disclose, then let the owner decide
Say what SourceX does, that you are a referral partner and that any reward is paid separately. Then ask the owner directly whether they want an introduction. Silence is a no.
Who sits in and who stays out
| Attendee | Why they are there | Blocks they carry |
|---|---|---|
| CEO or chief restructuring officer, with the CFO | The CFO owns the cost plan; the CEO or CRO makes the final choice | 1, 4, 5 |
| IT lead for the retiring tools | Knows history, admins and export status | 1, 3 |
| General counsel or debtor's counsel | Holds notices, court papers and contract terms | 2, 4 |
| Restructuring technology advisor | Runs the clock and records answers | All |
Leave out vendor representatives, lenders' advisers and anyone without authority over the records. If a lender must consent, note it and let counsel take it up later.
Running the clock when answers spill over
Two blocks tend to overrun. Block two runs long when nobody brought the documents: record "to confirm" and give general counsel an owner and a date, rather than reasoning about what the contract probably says. Block four runs long when ownership is mixed after an acquisition: write down which entity is in doubt and move on. When general counsel does bring documents, these are the patterns to recognize. Under 11 U.S.C. 365, a debtor or trustee may assume or reject an executory contract with the court's approval; in Chapter 11 that choice can wait until plan confirmation, while in Chapter 7 a contract not assumed within 60 days after the order for relief is deemed rejected. Among vendor policies, as checked on 2026-10-18, Zendesk's Service Data Deletion Policy starts automated deletion 90 days after an account is canceled or terminated, and Atlassian keeps data for deactivated paid cloud sites for 60 days after the subscription period ends. If you reach minute 24 with blocks unfinished, still do the disclosure and the decision on what you have; a partial picture with a clear "not yet" is better than an unfinished meeting.
What the meeting must decide
Close on exactly one outcome per tool, written down before people leave.
| Outcome | When it fits | Who records it | What happens next |
|---|---|---|---|
| Introduce now | A binding date exists, the company owns the records, the owner said yes | Advisor | Send the introduction email to the named approver |
| Watch list | No binding date yet, or ownership is still being confirmed | CFO's office | Revisit when a notice is sent or counsel confirms; use the archive context checklist |
| Stop | The owner declined, or the records belong to someone else | Advisor | Note the reason; the cost plan continues unchanged |
Before any introduction, confirm the baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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. What stays unknown until SourceX reviews it: buyer interest in these record types, the rights review result, any de-identification required and any offer. Partners collect answers, never exports, logins or sample records.
Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. The sell-side kickoff agenda and the portfolio review agenda use the same time-boxed method in other settings.
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 meeting closed on "introduce now" for a tool with a binding date, register as a partner, check the company against who qualifies and read the program terms before you write to the approver.