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 context | Out of the note | Where that item lives instead |
|---|---|---|
| The introducer, their role and how they know the CEO | Opinions about people | Nowhere |
| The company as the legal entity whose CEO decides, with its web domain | Record counts, system names, years of history | The company's own application to SourceX |
| The channel and timestamp of each step | Files, exports, samples, screenshots, links to them | Nowhere; the partner agreement bars a partner from keeping dataset copies without separate written authorization |
| The question asked, in the asker's words | Contract terms or customer names the CEO mentioned | The company and its counsel |
| What is waiting, on whom, since when | Guesses at value or reward | Nowhere; SourceX publishes no typical payouts |
| What the CEO allowed or limited, quoted, with date and channel | What another adviser or fund is said to be doing | Nowhere; 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.
| Block | Line | Tag | Text |
|---|---|---|---|
| Facts | F1 | we saw | Introducer: the audit partner who has advised the company since 2019 |
| Facts | F2 | CEO said | Company: the operating entity and its web domain; the CEO is its founder |
| Facts | F3 | we saw | Channel: the CEO replied by email on 13 Oct at 16:02 ET to the introducer's note of 10 Oct |
| Questions | Q1 | CEO said | Asked: "Would our customers' project files be part of this?" |
| Questions | Q2 | we saw | Waiting on: the CEO, to say whether the COO joins the first call; open since 13 Oct; next look 20 Oct |
| Permission | P1 | CEO said | "Yes, please introduce us to SourceX." Email, 13 Oct, 16:02 ET |
| Permission | P2 | CEO said | Limit: "Keep our board out of it until I raise it myself." |
Seven rules keep the format honest.
- 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.
- 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.
- 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.
- Roles beside names. "The audit partner who has advised the company since 2019" survives staff turnover in a way that initials do not.
- 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.
- 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.
- 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.
| Event | Who writes the entry | Block that must be filled |
|---|---|---|
| The CEO agrees to be introduced | The introducer | Permission, quoted |
| The introduction is submitted | Partner operations | Facts, with the timestamp |
| The CEO asks something | Whoever received the question | Questions, in the CEO's words |
| The dashboard shows a new stage | Partner operations | Facts, tagged [dashboard] |
| The CEO narrows or withdraws permission | Whoever hears it | Permission, quoted, marked as replacing the earlier entry |
| Day 90 passes with no verified application | Partner operations | Facts: 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.
| Entry | Block | Line |
|---|---|---|
| 1, 6 Oct | Facts | [we saw] Introducer: our tax partner, adviser to the company for six years; first call with the CEO on 6 Oct |
| 1, 6 Oct | Permission | [CEO said] Oral: "Happy to hear more about it." Written confirmation requested 6 Oct |
| 1, 6 Oct | Questions | [our inference] Waiting on: the CEO, to confirm in writing whether she wants an introduction |
| 2, 9 Oct | Permission | [CEO said] "Please go ahead and introduce us." Email, 9 Oct |
| 2, 9 Oct | Questions | [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.