# Discussing an active referral in a partner meeting | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-discuss-an-active-referral-in-a-partner-meeting
Last updated: 2026-11-05

Give an active referral a short slot at the end of the partner meeting, after guests have left and any automatic note-taking has stopped. Say five things aloud: the reference code, who holds the CEO relationship, the stage in generic words, the next action and whether the room has to decide anything. Minute one line per referral. The company's records, figures, any estimate, the buyer, SourceX's reasons and anything a board seat revealed stay out of the room and out of the notes. The company's CEO, not the meeting, decides what the company does next.

## What the meeting is for, and who it is not for

A partner meeting touches an active referral for coordination, not assessment: making sure only one person approaches a CEO or corporate group, settling firm decisions (who owns the relationship now, whether a possible payment is logged under firm policy) and recording step-outs. Fit is decided in SourceX's review and the deal by the company's CEO. [Who qualifies](/who-qualifies) is direct about the second: "Under the program, opening a licensing discussion and signing for the company fall to the CEO."

That narrow purpose sets the audience. NIST's security glossary describes need-to-know, in its government setting, as a decision by the person holding information that a recipient needs specific information to do their job (paraphrase). Applied here, a person stays for the item only if the item serves a decision they make.

| Person in the room | Stays for the referral item? | Why |
|---|---|---|
| The relationship owner | Yes | Gives the update and owns the next step |
| A partner whose decision is needed | Yes | Relationship changes, overlapping approaches, firm-policy questions |
| Other partners | Yes, for the one-line update | Prevents a second approach to the same CEO or group |
| The associate taking minutes | Yes | Writes the template line and nothing else |
| Compliance or legal | Yes, when the item raises a policy question | Payment logging, conflicts, a legal request |
| Anyone with an interest in the company beyond the referral | Declares it and may step out | Conflicts are settled in [the operating committee process](/guides/how-to-discuss-referral-conflicts-at-an-operating-committee), not mid-update |
| An LP observer, a visiting founder, a recruiter or other guest | No | None of their decisions turns on the item |
| A recording, transcript or AI note-taker | Off | It keeps more than the minute line and sends it further |

For what SourceX tells a partner, section 4.2 of the sample Channel Partner Agreement draws a similar circle: "employees, professional advisers and service providers who need the information for the permitted purpose." What the company told the relationship owner falls under the owner's own duties, which counsel reads. Board-seat facts are simpler: who qualifies calls them "a reason to ask the CEO, never material to pass along."

## Automatic notes reach everyone on the invitation

Recording and note-taking tools rarely know that the agenda changed halfway through. Google's settings page for its "Take notes for me" feature offers to share notes with all invited guests, including people outside the organization, with invited guests inside it, or with hosts and co-hosts only, and adds: "Invited guests means all guests on the Calendar invite, not guests who actually attended." An LP observer who left after the portfolio review can still receive notes covering the referral item if the setting reaches all guests.

Three ways to keep the item clean, in order of reliability:

1. **A separate short meeting** with its own invitation listing only the people who stay. The tool's sharing then matches the room.
2. **The item last**, with recording and note-taking switched off before it starts, and the minute taken by hand.
3. **A spoken pause** ("notes off for this item"), confirmed by the associate.

Other products differ; the invitation, not the room, usually sets who receives the output.

## The need-to-know meeting notes template

Use the template as written. It has an agenda line, a minute line with seven fields, and a list of content the minutes never hold.

**Agenda line, circulated to the whole invitation:** "Introductions in progress (number)". No company names in a document everyone on the invite receives.

**Minute line, one per referral:**

| Field | Write | Never write |
|---|---|---|
| Reference | Your internal code, or SourceX's reference code | The company name, if the minutes travel beyond those who need them |
| Relationship owner | A name | A list of everyone who knows the CEO |
| Stage | Not yet asked, Asked, Introduced, With the company or Concluded | Dashboard labels that imply a paid deal, or any amount |
| CEO's position | Agreed or declined, with the date | What the CEO said about the business |
| Next action | One verb, an owner and a date | Pressure ("push the CEO before quarter end") |
| Decision taken | Owner changed, overlap resolved, payment logged under policy, step-out recorded, or none | Any view on whether the company qualifies |
| Present for the item | Names, and who stepped out | Guests' reactions |

**Never minuted:** company records or links to them; headcount, system names or customers; any estimate, reward or payout figure; the buyer or Acquisition Partner; deal terms; SourceX's reasons for any decision; board-pack or information-rights facts; the CEO's personal or financial circumstances.

The stage words follow the outward vocabulary in the [referral status glossary](/resources/referral-status-glossary), so the minutes never say more than an outside update would. The sample agreement points the same way: the partner tracks its own referral "using generic stages or reference codes" (section 4.6), and section 1.6 counts introduction records, buyer identities, pricing and negotiation details as confidential information.

**Method note.** The template was built on 2026-10-28 from program terms version 2026-10-22.2, since replaced by version 2026-11-04 (sections 1 to 3, 5 and 7), sections 1.6, 1.9, 4.2, 4.5 and 4.6 of the sample Channel Partner Agreement (version 2026-10-19), who qualifies, SourceX's company page, NIST's need-to-know entry and Google's note-taking settings page. Each field was kept only if a decision the room makes needs it. No fund has reported using the template, and it interprets no one's confidentiality duties.

## One update, spoken twice (Illustrative)

Illustrative: a fictional fund's Monday meeting and a fictional 300-person logistics company. Nothing here describes a real referral.

The draft, as a partner might say it unprompted: "Quick one on the logistics company from the last board meeting. They've got fifteen years of dispatch data, about 300 people, SourceX's dashboard shows an estimate that looks big, and the CEO's keen because they need cash before the refinancing."

| Phrase in the draft | What it gives away | Where it belongs |
|---|---|---|
| "from the last board meeting" | That board knowledge is driving the item | Nowhere: board material never travels |
| "fifteen years of dispatch data, about 300 people" | Company facts the CEO shared for a different purpose | The company's own application to SourceX |
| "an estimate that looks big" | A proposed figure the company has not disclosed; terms section 5 calls estimates "projections, not promises" | Nowhere in the meeting |
| "need cash before the refinancing" | The company's financial position | Nowhere |

The rewrite, which is also the minute line: "L-07. Dana holds the CEO relationship. The CEO agreed on 14 October and we introduced the company on 16 October; it is with the company now. Next action: none until the CEO contacts Dana. No decision for this room."

## Questions from the room, and where each one goes

Partners ask natural questions. Most of them have a one-line answer in the room and a proper home outside it.

| Question asked | Answer in the room | Where it goes |
|---|---|---|
| "How big could this be?" | "We don't discuss estimates here." | Nowhere until a reward is approved; then to finance only |
| "Is SourceX buying it?" | "It's with the company." | The CEO; SourceX's company page says "Neither side publicizes the deal" |
| "Who's the buyer?" | "Not ours to know." | Nowhere: the sample says the Acquisition Partner's "identity and contract may remain confidential" (1.9) |
| "Why is it in duplicate review?" | "SourceX is reviewing credit." | The relationship owner, who may write to SourceX with referral details and evidence (terms section 7) |
| "Can I mention it to an LP I'm seeing?" | "No." | The CEO decides what the company says publicly |
| "They were just acquired; do we still ask the old CEO?" | "Pause the line." | Before closing the target's CEO decides; once acquired, the acquirer's CEO does |
| "Should we introduce their sister company too?" | "Log it on the same line." | A parent and its subsidiaries share one reward cap, and SourceX decides overlapping credit in duplicate review |

For what a co-investor may hear after submission, use [the co-investor sharing guide](/guides/what-to-share-with-a-co-investor-after-a-referral-is-submitted); if the relationship owner is leaving the firm, [the departing partner guide](/guides/when-a-partner-leaves-the-fund-with-an-active-introduction) covers the handover.

## Escalation, withdrawal and publication happen outside the meeting

**Escalation.** Anything the template cannot hold moves to a smaller conversation: the relationship owner and the one partner whose decision needs it, or counsel when a legal request or a duty is involved. The meeting hears only that the conversation happened.

**Withdrawal.** When the CEO stops the process, the line reads "Concluded" with a date and leaves future agendas. No reason is minuted, and nobody proposes trying again unless the CEO asked to be contacted later.

**Publication.** Minutes are never a source for an LP letter, a fund newsletter or a conference slide. Section 4.5 of the sample reads: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." On those words, public mention of SourceX as the firm's partner waits for SourceX's written authorization, and anything about the company waits for its CEO; counsel reads the signed version.

## Fit, credit and the written record

The meeting neither screens nor credits a company. Fit is a matter of the company's own facts: full-time staff that numbered 50 or more at its largest, with contractors left out, a record history it built itself and may license, and a CEO who wants the discussion. 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. Whether the records match current demand stays unknown until SourceX's review.

Credit rests on dated records, including written introduction evidence. The earliest valid introduction wins it, but only if the company's verified application follows inside the 90-day window, and a company SourceX already knew goes to duplicate review. A line in partner meeting minutes is your firm's note, not that evidence, so keep the written introduction itself where it was sent. No introduction is submitted before the partner has signed the Channel Partner Agreement. A session with outside founders in the room needs a different protocol, set out in [running a closed-door session](/guides/how-to-run-a-closed-door-session-without-sharing-company-records).

## Where a meeting template falls short

- **Small partnerships.** Where three partners share everything, the template still limits what is written, which matters when minutes outlive the people who heard them.
- **Fund documents.** Limited partnership agreements and side letters may require reporting the template does not contemplate; fund counsel decides.
- **Tool settings.** The note-taking behavior above comes from Google's help as checked on 2026-10-28; other tools and administrator settings differ.
- **Signed documents.** Your signed Channel Partner Agreement and any Schedule A or addendum govern; this page reads the unsigned sample.
- **No evidence yet.** No fund has reported results. A firm adopting the template can count, each quarter, the items minuted in one line and the questions routed out of the room.

More guides for partners are collected in the [guides library](/guides).

## 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.

Move referral items to the end of your next partner meeting and adopt the one-line minute; then [register as a partner](/register) and sign the Channel Partner Agreement, check each company against [who qualifies](/who-qualifies), and keep the [program terms](/terms) version you rely on with the minutes.

Meeting discipline is partner housekeeping; anyone evaluating SourceX itself as an investment should request materials 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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://csrc.nist.gov/glossary/term/need_to_know
- https://support.google.com/meet/answer/16909639?hl=en
- https://sourcex.si/investors
