# Data referral quality checklist before you send | SourceX

Canonical: https://refer.sourcex.si/guides/the-referral-quality-review-before-pressing-send
Last updated: 2026-11-05

A data referral quality checklist should score the outgoing message, not the company. Before anything leaves, four stop lines must be clean: the right recipients, the CEO's dated consent, zero attachments and no sentence that tells anyone the company qualifies. Ten more lines check that every fact is the company's own, labeled and owned, and that the handoff names a contact and an agenda. A zero on any stop line holds the message, whatever its total.

Fit was screened weeks earlier. This is the last read, done in the ten minutes before the relationship owner sends, by someone who did not write the draft. On a venture platform team that reader is often the portfolio operations analyst.

## Why the last read has to happen before the button

Most mail clients now offer a short way back. Gmail's help pages describe an Undo Send setting whose cancellation period can be set to 5, 10, 20 or 30 seconds. Half a minute catches a typo you notice as the message goes. It does not catch a judgment nobody made: whether the deal-team list belonged in CC, or whether the sample spreadsheet should have been attached at all.

Wrong recipients are a recognized failure, not a hypothetical one. The UK Information Commissioner's Office tracks email sent to the wrong recipient as its own incident type in its data security incident trends, and its glossary describes it as an email containing personal data reaching the wrong address. A referral message carries a CEO's name and contact details and often a paragraph about the company's systems and staff. The recipient line is the first stop line for that reason.

This review is also narrower than the work before it. Whether the company passes the screening facts was settled when it was first discussed; how to lay out the page is covered in [the one-page brief a founder can approve](/guides/the-one-page-data-referral-brief-a-founder-can-approve). Here the only question is whether the text about to leave matches what the CEO approved, and nothing more travels with it.

## The minimum company context the message carries

Eight lines, each supplied by the CEO or by someone the CEO names, all of them metadata:

1. The operating entity, its country and the main language of its records.
2. Full-time headcount at the company's largest, with the year, leaving contractors out.
3. The record families and the systems that hold them, each with a start year.
4. Who created those records, and whether any of them belong to clients.
5. Known constraints, in the company's words.
6. Earlier contact with SourceX, as far as the CEO knows.
7. The CEO's consent: date, channel and what may be shared.
8. The person who will take the first call.

Location matters because the screening profile depends on it. 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.

Four things stay out of the message even when they are at hand: numbers from board decks or monitoring reports, any valuation or payout expectation, anything a client of the company owns, and every file. A portfolio analyst often knows more than the CEO has said for this purpose; that knowledge prompts questions to the CEO and never fills a line. If the company's records are about to move or lapse, the dated event belongs in line 5, and the [archive context checklist for portfolio reviews](/resources/portfolio-operations-review-archive-context-checklist) shows how to date it.

## The final submission review scorecard

Score each line 2 if it is clean, 1 if it can be fixed in minutes, 0 if it is missing or wrong. Lines marked as stop lines need a 2 for the message to go. Our working rule for sending, not a program requirement: every stop line at 2 and a total of at least 24 out of 28.

| # | Line | Clean (2) looks like | Usual miss | Stop line |
|---|---|---|---|---|
| 1 | Recipients | Only the people the CEO agreed should read it, each address checked by eye | A fund distribution list in CC, or an autocompleted look-alike name | Yes |
| 2 | Sender | Whoever submits has signed the SourceX Channel Partner Agreement | An analyst sending from a colleague's partner account | No |
| 3 | CEO consent | A dated, written yes from the CEO that says what may be shared | "The founder sounded keen on the call" | Yes |
| 4 | Attachments | None at all: no files, samples, screenshots or exports | A sample export added "so they can see the data" | Yes |
| 5 | Source of each fact | Every line traces to a named person at the company and a date | Figures lifted from a board deck | No |
| 6 | Number labels | Each figure marked counted or estimated, with its basis | "About 200 staff" | No |
| 7 | Constraints | Written as the company stated them | Softened, or dropped to make the message read better | No |
| 8 | Open questions | Listed, each with the person who can answer it | Removed because they look like weaknesses | No |
| 9 | Fit language | "May be a fit; SourceX decides after review" | "They clearly qualify" or "a great dataset" | Yes |
| 10 | Money | No value, price, payout or reward figure for the company | A calculator estimate pasted in | No |
| 11 | Partner's stake | The CEO has been told the introducer may receive a reward from SourceX that never reduces the company's own payout | Disclosed to SourceX but not to the CEO | No |
| 12 | Earlier contact | The CEO's answer, marked "as far as the CEO knows" | Left blank | No |
| 13 | First-call contact | The CEO or a person the CEO named, with role | "Someone in IT" | No |
| 14 | First-call agenda | Three to five items, each tied to an open question | No agenda, or a sales pitch | No |

The four stop lines share one property: a follow-up message cannot repair them. A wrong reader has already read, an unapproved introduction has already reached SourceX, a file has already left the company, and a promise of fit has already set an expectation that review may not meet. Everything else on the card can be corrected in a second email without harm.

Lines 10 and 11 are not in tension. The message to SourceX carries no money figure, while the note to the CEO carries the disclosure of your interest. The program terms describe estimates shown in the portal or calculator as projections, not promises, so line 10 keeps them out of a document that speaks for the company.

## One draft rescored, line by line (Illustrative)

Illustrative. A generic company, invented facts and no outcome implied. A deal partner drafts the introduction of a 190-person freight audit company in the portfolio, and the analyst scores the draft before it goes.

| # | Draft as written | Score | Revised before sending | Score |
|---|---|---|---|---|
| 1 | SourceX address, with the fund's deal-team list in CC | 0 | CC removed; only the relationship owner and SourceX remain | 2 |
| 2 | Sent by the partner who signed the agreement | 2 | Unchanged | 2 |
| 3 | CEO's email of 14 Oct 2026 agreeing to the introduction | 2 | Unchanged | 2 |
| 4 | A 200-row sample of invoice exceptions attached | 0 | Deleted; one line describes the record family instead | 2 |
| 5 | Headcount taken from the second-quarter board deck | 1 | Line held back until the CFO states the figure | 1 |
| 6 | "12 years of data" | 1 | "Audit records in the current platform since 2014, per the operations lead; earlier years not confirmed" | 2 |
| 7 | Two carrier contracts limit reuse of rate tables | 2 | Unchanged | 2 |
| 8 | Three open questions, each with an owner | 2 | Unchanged | 2 |
| 9 | "They clearly qualify" | 0 | "May be a fit; SourceX decides after review" | 2 |
| 10 | No figures | 2 | Unchanged | 2 |
| 11 | Reward not mentioned to the CEO | 1 | One sentence added to the CEO's copy | 2 |
| 12 | Blank | 1 | "None known to the CEO as of 20 Oct 2026" | 2 |
| 13 | The COO, named by the CEO | 2 | Unchanged | 2 |
| 14 | No agenda | 1 | Four items written, one per open question plus the constraint | 2 |
| Total | Three stop lines at 0 | 17 | Every stop line at 2 | 27 |

Line 5 stays at 1 on purpose. A board figure is probably accurate, but it was given to the fund for another purpose, so the line waits for the CFO rather than borrowing it. The message can go at 27 because the rule asks for clean stop lines and 24 overall, not for a perfect card.

## Estimates, constraints and questions nobody has answered yet

The scorecard checks that labels survived editing. Drafts drift: "140 to 160 full-time at the 2022 peak, CFO's estimate" becomes "150 staff" two versions later, and the range, the basis and the year are gone. Keep four kinds of line visibly apart:

- **Counted:** a person at the company read it from a named source on a date.
- **Estimated:** a range with its basis, who made it and when, as [labeling estimates in a founder brief](/guides/how-to-label-estimates-in-a-founder-referral-brief) sets out.
- **Constraint:** a known limit in the company's words, never rephrased into something milder.
- **Open:** a question with its owner, whether the CEO, the company's counsel or SourceX in review, kept on a list like the one in [recording what you do not know about a dataset](/guides/how-to-record-what-you-do-not-know-about-a-dataset).

An honest unknown costs a message nothing. A reviewer at SourceX will find a missing rights answer either way; finding it written down, with a named owner, saves the first call ten minutes.

## The authorized handoff and a first-call agenda

The order matters more than the speed:

1. **The CEO sees the final text.** Not a summary of it: the same words that will be sent, after every fix.
2. **The relationship owner sends**, or gives the CEO a partner link so the company applies itself. Either way, the submitter's signed Channel Partner Agreement is in place first.
3. **Credit follows the dated record.** Section 2 of the program terms credits "the first valid introduction of a new company within the 90-day attribution window" once that company submits a verified application. Under section 3, a company SourceX already knew through an application, a lead, an account or earlier email is reviewed as a duplicate, which is why line 12 exists; [the duplicate-claim checklist](/guides/how-to-prevent-duplicate-claims-before-they-reach-sourcex) covers the 48 hours before sending.
4. **Nothing else travels.** [No documents go with an introduction](/questions/should-i-upload-company-documents-when-making-an-introduction), before or after the message.

A 30-minute first call can run straight from line 14:

1. Who decides and who attends: the CEO as authorizer, and the contact the CEO named (5 minutes).
2. The open questions, taken in order of who owns them (10 minutes).
3. The stated constraints, with anything for counsel marked (8 minutes).
4. What SourceX's review covers, from fit with a current program to rights and relevance, and what the introducer stays out of (5 minutes).
5. The next step and its date (2 minutes).

## Where a send gate fails

- **Totals can flatter.** A 24 built from soft 1s on lines 5 to 8 is a weaker message than a 24 with one known gap. Read the zeros and ones, not just the sum.
- **Clean is not accepted.** A perfect card for a company whose records belong to its clients is still a poor fit, and demand for any record family is assessed only in review. Program criteria also change, so a company declined now may suit a different program later.
- **The author scores their own draft.** Under time pressure the card becomes a formality. If the reviewer and the author are the same person, wait an hour or swap roles.
- **Fund knowledge leaks in as context.** "We know from the board pack that..." is the most common way confidential investor information reaches a referral message. Line 5 is where it gets caught.
- **Nothing has been measured yet.** Whether scored messages move through review faster or succeed more often is unknown, and SourceX has not published review figures. A platform team can test it by logging, per message, the draft score, the sent score, the number of questions in SourceX's first reply and the days until the company applies.

**Methods note.** The scorecard was built from SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and published screening profile, Gmail's Undo Send documentation and the ICO's incident-type glossary, all checked on 2026-10-27. The threshold of 24 and the choice of stop lines are our working rules. The worked review is Illustrative. Nothing here measures review outcomes, record quality or demand, which only SourceX's review assesses.

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

Once the outgoing message holds a 2 on all four stop lines and at least 24 overall, open a partner account through [registration](/register), hold the confirmed facts against [who qualifies](/who-qualifies) and reread the [program terms](/terms) before the relationship owner presses send. Other portfolio guides sit in the [guides hub](/guides).

Scoring a referral message is partner work; judging SourceX as a company to invest in is a different decision, made separately, and the [SourceX investor overview](https://sourcex.si/investors) is where investor materials can be requested.

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://support.google.com/mail/answer/2819488
- https://ico.org.uk/action-weve-taken/complaints-and-concerns-data-sets/data-security-incident-trends/glossary-of-terms/incident-types/
- https://sourcex.si/investors
