# Portfolio transition referral calendar | SourceX

Canonical: https://refer.sourcex.si/guides/a-portfolio-transition-calendar-for-data-partnership-reviews
Last updated: 2026-11-05

Set data partnership reviews by event, not by month. A portfolio transition calendar lists the dated events that move who holds a company's records or who decides about them, such as an approved sale process, a closing, a system retirement, a layoff notice or a new CEO, and fixes the day each review falls relative to that event. Every review answers three questions only: who holds the records now, who decides, and whether an introduction is open, on hold or closed. Financing rounds and valuation marks never trigger one.

Private equity sponsors can hang a records-and-rights screen on a yearly rhythm, and the [annual portfolio operations calendar](/resources/portfolio-operations-annual-calendar-private-equity) does exactly that. A venture portfolio rarely moves in step. Its exits, shutdowns and leadership changes arrive on deal timelines, and a quarterly review can land in the worst possible week: inside an exclusivity period, after an archive scope was signed, or a month after the person who could answer has left. The [venture platform teams overview](/for/venture-platform-teams) covers the program from the portfolio side.

## Why a fixed month misses the transitions that matter

Three things change during a transition, and each one can end a referral that nobody declined.

- **Custody moves.** Records shift from live systems to exports, data room archives, an acquirer's platform or storage arranged by counsel.
- **Control moves.** The person who decides changes. SourceX's screening guidance is explicit that once a company is acquired, the acquirer's CEO decides for it, and that in an assignment for the benefit of creditors, a receivership or a bankruptcy the CEO alone may not be enough.
- **People leave.** The system owner who could describe an archive in one call may have a known last day.

A calendar keyed to those events reviews a company when something real has changed, and stays quiet when nothing has.

## A baseline line for each company before any trigger goes in

Each company gets one line before any trigger is entered, with the date you checked it:

| Field | What to write | Who usually knows |
|---|---|---|
| Operating entity | The legal entity whose employees created the records | The company's CFO or counsel |
| Record families and systems | Support, operations, project or finance history, and the systems that hold it | The system owner or CTO |
| Current decider | The CEO today, and since when | Public record or the board member |
| Relationship owner | The person in your network the CEO listens to | Your own team |
| Known dated events | Contract ends, retention purges, planned retirements | The system owner |

Nothing on this line is a record. It is the minimum needed to know, on a trigger date, whether anything moved. The [portfolio operations review screen](/guides/moment-portfolio-operations-review-vc-platform-teams) covers the size and history questions that decide whether a company belongs on the calendar at all.

## The trigger-based review calendar

Ten triggers, each with the day its review falls. Day 0 is the date the trigger itself carries.

| Trigger | What dates it | Review day | What the review settles | Hold or stop rule |
|---|---|---|---|---|
| 1. Board approves a sale process | Board minutes | +14 days | Which record families exist and who will run diligence | No ask unless the CEO raises licensing |
| 2. Letter of intent with exclusivity | LOI date | None until signing or expiry | Nothing new | Hold: the company's attention belongs to the deal |
| 3. Purchase agreement signed | Signing date, and any HSR filing | Expected closing date | The closing date and who decides afterwards | Hold until closing |
| 4. Closing | Closing date | +30 days | The acquirer's CEO now decides; is there a live path to them? | Introduce only through that path |
| 5. Integration plan dates a system retirement | The plan's retirement date | The day the date is set | Which archive survives and when its scope is signed | The window closes at archive sign-off |
| 6. WARN notice issued | Notice date | The same week | Which system owners are leaving, and the CEO's interest | Ask only if the CEO wants it; never extend anyone's stay for it |
| 7. Wind-down vote or formal filing | Resolution or filing date | At once | Who controls the company's assets now | Counsel first; the CEO alone may not be enough |
| 8. CEO change | Effective date | +30 days | The new CEO's view; an earlier yes lapses | Re-ask once; never rely on the old answer |
| 9. Retention purge or contract end | Policy date or contract end | 60 days before | What the purge or exit removes | Never ask the company to delay it |
| 10. Full-time headcount first passes 50 | The company's HR record | +30 days | The full fit screen, for the first time | Normal screen |

Two triggers carry outside clocks worth knowing. For a deal large enough to need a Hart-Scott-Rodino filing, the FTC's fiscal 2025 annual report says the parties typically wait 30 days after filing before closing, or 15 days for a cash tender offer or a bankruptcy sale, unless the agencies end the wait early. That gives trigger 3 a floor, not a date: the closing can come later, and the review follows the actual closing. Under the WARN Act, as the Department of Labor summarizes it, employers of 100 or more workers must give at least 60 days' notice of a plant closing or mass layoff to affected workers, the state dislocated worker unit and the local government. A notice is therefore a public, dated sign that the people who can describe the records may be gone within two months.

**Events that are not triggers.** A new financing round, a valuation mark, press coverage, a product launch or a hiring announcement. None changes who holds the records or who decides, and none of SourceX's screening checks mentions funding.

**Every review writes four fields and nothing more.**

| Field | Example entry |
|---|---|
| Custody | Support history still in the original help desk; export planned for March |
| Control | The acquirer's CEO, since 18 Sep 2026 |
| Introduction | Open, on hold or closed, with the reason |
| Next review | The next trigger's review day, or "none set" |

**Method note.** The calendar applies the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's screening guidance on control after acquisitions and in formal processes, the FTC's fiscal 2025 HSR report and the Department of Labor's WARN summary, all checked 2026-10-27. The ten triggers, the review offsets and the hold rules are this page's method, not legal requirements or SourceX rules. The calendar does not measure how many introductions follow a review or how often they are accepted; SourceX has not published such figures.

## The 90-day clock belongs on the calendar too

Attribution has its own date. Section 2 of the program terms reads: "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application." The same section adds that the window does not extend because contact protection continues. An introduction made in the first week of an exclusivity period can run out of window long before the company is free to apply.

So the calendar schedules introductions, not just reviews. An introduction goes on the calendar only on a day when the decider is settled, no hold applies and the CEO has said yes, so that the company can realistically apply within 90 days. The partner who submits must have signed the SourceX Channel Partner Agreement first.

## One portfolio run through the calendar (Illustrative)

Illustrative. Generic companies, invented dates, no outcome implied.

| Company | Trigger | Trigger date | Review | What the review recorded |
|---|---|---|---|---|
| A. 210-person payments operations software | 3 Signed; closing expected | 3 Aug 2026 | 18 Sep 2026, the actual closing | Hold ended; acquirer's CEO decides; former board member has a path |
| A, continued | 4 Closing | 18 Sep 2026 | 18 Oct 2026 | The acquirer's CEO wants a conversation; introduction made 22 Oct 2026 |
| B. 140-person logistics marketplace | 6 WARN notice for a site closure | 1 Oct 2026 | 2 Oct 2026 | The CEO declines; closed, no re-ask |
| C. 95-person vertical software company | 8 New CEO | 15 Sep 2026 | 15 Oct 2026 | Earlier yes lapsed; new CEO asked once, wants to wait for the next budget cycle |
| D. 310-person field-services platform | 5 Help desk retirement dated | 9 Oct 2026 | 9 Oct 2026 | Archive scope due 15 Jan 2027; the CEO will decide before signing it |
| E. 60-person analytics company | Series C closed | 2 Sep 2026 | None | Not a trigger; nothing recorded |

Company A shows the calendar doing its main job: no ask during the signed-to-closing stretch, then one review once control had moved. Company B shows the other: a no is recorded with its date and the calendar does not schedule another try. The [system retirement window](/guides/the-referral-window-before-a-portfolio-company-retires-a-system) goes deeper on a case like company D, and [restructuring and the person who can say yes](/guides/when-restructuring-changes-the-person-who-can-say-yes) on a case like company C.

## Duties a trigger can bring with it

Each trigger can bring duties that settle the outcome for some records before anyone thinks about licensing: a hold because a dispute is in view, a retention minimum, a contract that requires client data to be returned or deleted at exit. On a review day these are inputs from the company and its counsel, never judgments the fund makes. Write down that a duty exists and which record family it covers; leave its meaning to counsel. A wind-down adds its own sequence of decisions, set out in [preserving a conversation through a wind-down](/guides/how-to-preserve-a-conversation-when-a-company-winds-down).

## Open, hold or close each row on its review day

- **Open** when the decider is settled, no hold covers the records in question, the CEO wants the conversation and the company can apply within the attribution window.
- **Hold** through exclusivity, signing to closing, and the first weeks of a new CEO's tenure, with the next review day written down.
- **Close** when the CEO says no, when a duty removes the records, or when the archive is gone. A closed row reopens only on a new trigger, never on a calendar anniversary.

## Where a trigger calendar can mislead

- **Confidential triggers.** A fund often learns of a sale process or a layoff under confidentiality. The calendar is internal, and a trigger is a reason to ask the CEO, never information to pass on.
- **Not every deal files.** HSR applies only to reportable transactions, so a smaller exit may involve no filing and no wait at all, and a wait that does apply can end early.
- **WARN has thresholds.** It covers employers of 100 or more workers and specific events, so a smaller company's shutdown may carry no federal notice at all.
- **Offsets are guesses.** The 14-day and 30-day review days are our method. Adjust them to how each company actually moves, and record why.
- **Calendars create pressure.** A review day is a prompt to check facts, not an obligation to ask. Whether any company's records are wanted is decided only in SourceX's review.

**A measurable next step.** Enter every portfolio company with its one-line baseline, then count over two quarters how many reviews fell inside a hold period under your old fixed schedule and how many triggers your calendar caught that the old schedule missed. If the counts are close to zero, the fixed schedule was serving you well.

## 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 a review day finds a settled decider, no hold and a CEO who wants the conversation, [register for your partner link](/register), run the company past [who qualifies](/who-qualifies) and check the [program terms](/terms) before the introduction goes on the calendar.

A transition calendar decides when to raise a referral; deciding whether SourceX belongs in a fund's own portfolio is separate work, and investor materials for it are available through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.ftc.gov/system/files/ftc_gov/pdf/fy_2025_hsr_annual_report_for_transmittal_to_congress.pdf
- https://www.dol.gov/general/topic/termination/plantclosings
- https://sourcex.si/investors
