The referral note format that preserves context: a facts, questions and permission entry that records who introduced whom, when, what was asked and what waits on whom, and carries none of the company's records

Short answer

A referral CRM note should let a colleague who has never met the company rebuild the route of an introduction in under a minute: who introduced whom and how they know each other, when and through which channel, what was asked, what is waiting and on whom, and what the company's CEO has allowed, in the CEO's own words. Write every entry in three blocks, facts, questions and permission. Tag each line with where it came from, add new entries instead of editing old ones, and keep the company's records, figures and attachments out of the note entirely.

Visual briefFull-size diagram
A luggage-style label for one Illustrative note entry dated 14 Oct with three bands: facts, an introducer to a CEO by email on 13 Oct; questions, asked about customer files and waiting on the CEO since 13 Oct; permission, the CEO's quoted yes with a limit that the board is not told yet. Small tags mark each line CEO said or we saw, and a stamp across the corner reads contents: not carried.
Illustrative entry. Names, dates and wording are invented to show the format; no real company or introduction.

This page is about the text inside a note. Which objects and fields a referral CRM should hold is covered by the three-object CRM schema, and what travels to SourceX on the day of the yes by the accepted-introduction handoff.

How a referral note goes stale in one quarter

Most notes are written for the writer. "Call w/ Dana, keen, export Fri" is perfectly clear on the afternoon it is typed. Three months later the writer has moved on, nobody knows which Dana, keen on what, or whether "export" means the company planned to send a file it should never have sent. The note has kept the writer's shorthand and lost the route.

The route is what the firm will be asked about. SourceX's terms decide credit from dated records, naming written introduction evidence, existing applications and preexisting relationships, and they say a link click alone does not decide it. The partner agreement adds that an introduction must be recorded in writing and that an oral one must be confirmed in writing before protection attaches. A note does not decide anything, but a dated, sourced entry is how a firm finds its own written evidence when the question comes, instead of searching inboxes.

What counts as route context, and what never enters the note

Route context answers six questions about the introduction, one per row below. Everything else stays out, and most of it already has a better home.

In the note: route contextOut of the noteWhere that item lives instead
The introducer, their role and how they know the CEOOpinions about peopleNowhere
The company as the legal entity whose CEO decides, with its web domainRecord counts, system names, years of historyThe company's own application to SourceX
The channel and timestamp of each stepFiles, exports, samples, screenshots, links to themNowhere; the partner agreement bars a partner from keeping dataset copies without separate written authorization
The question asked, in the asker's wordsContract terms or customer names the CEO mentionedThe company and its counsel
What is waiting, on whom, since whenGuesses at value or rewardNowhere; SourceX publishes no typical payouts
What the CEO allowed or limited, quoted, with date and channelWhat another adviser or fund is said to be doingNowhere; SourceX settles overlapping claims in duplicate review

The second row surprises people. A note that says "eleven years of job files in one system" feels harmless, yet it is the company's description of its own records, written down by someone else. SourceX's referral overview says the partner makes the introduction and never needs to export, upload or describe confidential records, and the company states its own systems when it applies.

The facts, questions and permission entry

One entry per event, written the same day, in this shape. The example lines are Illustrative.

Entry 3 below was written by the partner manager on 14 Oct 2026 at 09:40 ET.

BlockLineTagText
FactsF1we sawIntroducer: the audit partner who has advised the company since 2019
FactsF2CEO saidCompany: the operating entity and its web domain; the CEO is its founder
FactsF3we sawChannel: the CEO replied by email on 13 Oct at 16:02 ET to the introducer's note of 10 Oct
QuestionsQ1CEO saidAsked: "Would our customers' project files be part of this?"
QuestionsQ2we sawWaiting on: the CEO, to say whether the COO joins the first call; open since 13 Oct; next look 20 Oct
PermissionP1CEO said"Yes, please introduce us to SourceX." Email, 13 Oct, 16:02 ET
PermissionP2CEO saidLimit: "Keep our board out of it until I raise it myself."

Seven rules keep the format honest.

  1. Fixed headings in a fixed order. Clinical documentation worked this out decades ago. The StatPearls chapter on SOAP notes, as listed on PubMed, describes Subjective, Objective, Assessment and Plan as a widely used method that lets clinicians record patient information in a structured, organized format, and credits Larry Weed with the structure almost 50 years ago (our paraphrase). A reader who knows where permission sits finds it without reading the rest.
  2. A source tag on every line. Use a closed list: [CEO said], [introducer said], [we saw] for a message or document the firm holds, [dashboard] for SourceX's partner dashboard, and [our inference]. Inference may appear in questions, never in facts or permission.
  3. Permission is quoted, never summarized. The CEO's words, the date and the channel. "CEO is fine with it" is not permission; it is the writer's reading of permission.
  4. Roles beside names. "The audit partner who has advised the company since 2019" survives staff turnover in a way that initials do not.
  5. Append, never overwrite. A correction is a new entry naming the entry it corrects. The partner agreement says a dispute must not erase original evidence, and an edited note is erased evidence.
  6. Oral gets a follow-up entry. A yes heard on a call is entered as "oral; written confirmation requested," and a second entry records the written confirmation when it arrives.
  7. No content, ever. If writing a line requires describing the company's records, the line does not belong in the note.

Who writes the entry at each stage

The person closest to the event writes the entry, and the block that must not be empty changes with the stage.

EventWho writes the entryBlock that must be filled
The CEO agrees to be introducedThe introducerPermission, quoted
The introduction is submittedPartner operationsFacts, with the timestamp
The CEO asks somethingWhoever received the questionQuestions, in the CEO's words
The dashboard shows a new stagePartner operationsFacts, tagged [dashboard]
The CEO narrows or withdraws permissionWhoever hears itPermission, quoted, marked as replacing the earlier entry
Day 90 passes with no verified applicationPartner operationsFacts: the window has ended

When a question line passes its next-look date, the operations lead decides what happens, rather than anyone asking the CEO again; the question owner and deadline board sets those rules, and the manager transfer checklist covers notes that change hands.

A shorthand note, rewritten (Illustrative)

Illustrative. A generic 210-person building services company, an invented introducer and invented dates.

Before. "Spoke to Dana, keen!! 12 yrs of job files, about 40k jobs, she'll send an export Fri. Prob a big one. Other fund knows her too."

After.

EntryBlockLine
1, 6 OctFacts[we saw] Introducer: our tax partner, adviser to the company for six years; first call with the CEO on 6 Oct
1, 6 OctPermission[CEO said] Oral: "Happy to hear more about it." Written confirmation requested 6 Oct
1, 6 OctQuestions[our inference] Waiting on: the CEO, to confirm in writing whether she wants an introduction
2, 9 OctPermission[CEO said] "Please go ahead and introduce us." Email, 9 Oct
2, 9 OctQuestions[CEO said] Asked: "Do we have to send anything to you?" Answered the same day: no, and nothing should come to us

Left out, and why. The years and job counts describe the company's records and belong in its own application. The export must not be accepted at all; the CEO was told that any material goes to SourceX only through SourceX's own process. "Prob a big one" is a value guess. The other fund's interest is a claim about a third party, and SourceX decides overlapping cases from dated records in duplicate review.

Closing a note and keeping it

The last entry names the event that ended the referral and its source: the CEO's decision, quoted; the window passing; a SourceX outcome seen on the dashboard; or a payout recorded. Keep the entries that evidence the route for as long as your firm's retention policy says. The partner agreement excepts records needed for reward accounting and dispute evidence from its return-or-delete clause, and a route-only note is exactly that kind of record. Anything that slipped in and is not route context, a pasted figure, a forwarded attachment, is deleted rather than archived.

If the company ever comes back through another route, the old entries show what the firm knew and when, which is all they should show. For reconciling what the notes say with what the dashboard says, use the live guide to matching SourceX statuses with a fund's CRM; for an adviser writing to a CEO after a deal, the post-closing note template is a separate, outward-facing format.

Where a structured note still falls short

  • Discipline. The format only works if entries are written the same day; a weekly catch-up rebuilds shorthand.
  • Wrong tags. A line tagged [CEO said] that was really heard from the introducer misleads more than an untagged line.
  • Editable systems. Many CRMs let anyone edit a past note, so "append, never overwrite" is a team rule, not a technical lock.
  • No proof of credit. A company SourceX already knew through an earlier application, lead, account or email thread is a duplicate, however tidy the firm's notes are.
  • People in the note. Entries name individuals, so access to the notes should be limited to the people working the referral.
  • No outcome data yet. Whether this format shortens the time to answer a question about an introduction has not been measured. Time a sample of lookups before and after adopting it; no figures are published.

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.

Before your team writes its first entry under this format, make sure the firm has registered as a partner and signed the Channel Partner Agreement, check the CEO's account of the company against who qualifies, and keep the version of the program terms you rely on named in the note's first entry. More operations formats are in the guides library.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can we paste the CEO's whole email into the note?

Quote only the sentences that grant or limit permission, with the date and channel, and point to where the full message is kept. Pasting whole threads drags in figures, attachments and other people's details that the note was designed to leave out.

Does a well-kept note decide who gets credit?

No. SourceX decides credit from dated records, including its own, and a company it already knew is a duplicate whatever your notes say. A clean note helps your firm find its own written evidence quickly; it decides nothing.

What if a colleague's earlier entry is wrong?

Write a new entry that names the wrong entry by number and states the correction with its source. Leave the original in place, so the history of what the firm believed and when stays readable.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/how-it-works
  4. refer.sourcex.si/who-qualifies
  5. pubmed.ncbi.nlm.nih.gov/29489268

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment