# Correct a referral email sent with too much detail | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-correct-a-referral-email-sent-with-too-much-detail
Last updated: 2026-11-05

Stop the email from traveling further, tell the company's CEO what went out and to whom, and ask every recipient in writing to delete it along with any forwards. Then send a replacement that carries only what an introduction needs, and record the incident in your own files without copying the detail again. Recall buttons rarely help once a message has left your own organization. Whether the slip triggers any legal duty is a question for your counsel and the company's, not for the correction email.

This page is for the counsel liaison at a fund who hears from a partner, usually a day late: "I think I put too much in that introduction." The usual culprits are a headcount or revenue figure lifted from a board pack, customer names, a pending transaction, a screenshot of a system or an attachment. None of it belonged there. SourceX's sample partner agreement gives a partner "no authority to share a supplier's inventory, records, raw data or personal information," and SourceX's referral process page says a partner never needs to export, upload or describe confidential records.

## The first hour: who received what

The first hour is about not making it worse. Replying to everyone with an apology that quotes the thread sends the detail again; forwarding it to colleagues for advice adds recipients. Freeze the thread and work from the Sent folder.

Do not count on recall. Microsoft's support page is plain: "Messages sent to people outside your organization, or to personal accounts such as Outlook.com or Gmail, can't be recalled." Gmail's Undo Send works only inside a send cancellation period of 5 to 30 seconds that the sender sets in advance (a paraphrase of Google's help page). By the time anyone notices an overshared introduction, it has arrived.

Sort what went out into one of three tiers. The tier decides how fast the CEO hears and how wide the deletion requests go.

| Tier | What the email carried | Typical example | What it adds to the base checklist |
|---|---|---|---|
| A. Files or records | Attachments, screenshots, exports, samples, or personal data about customers or staff | A screenshot of the support queue; an org chart | The CEO hears today by phone; deletion requests name each file; the company's privacy lead and counsel decide whether anything more is owed |
| B. Confidential facts | Non-public facts the sender held in confidence | Headcount or revenue from a board pack; customer names; a sale in progress | The CEO hears today; deletion request to every recipient; fund counsel checks the fund's own documents |
| C. Too much public detail | Public facts or the sender's opinions, at length | Three paragraphs of company history from its website | A leaner replacement if the CEO wants one; no deletion request needed |

Then list every recipient, because what you can ask for depends on who they are.

| Recipient | What you can ask for | The limit |
|---|---|---|
| SourceX | Deletion of the email, by a written request that names its date, time and subject | The sample agreement's written-request route has exceptions, and whether it reaches this email is for counsel to say |
| Colleagues inside the fund or firm | Deletion, confirmation and no forwards, including copies pasted into a CRM or a shared inbox | Copies inside your own systems are yours to find |
| Anyone else: a co-investor, another adviser, an assistant | Deletion and confirmation | No agreement with you may bind them; the request may rest on courtesy alone |

## The incident triage and correction checklist

Ten steps, in order. Each has a time, a person and a test for when it is done.

| Step | When | Who acts | Done when |
|---|---|---|---|
| 1. Freeze: no replies, forwards or new messages about the company | Hour 1 | The sender | Colleagues on the thread have been asked, by a message that quotes nothing, not to forward it |
| 2. List each recipient and exactly what each received, attachments separately | Hour 1 | The sender | A list exists in your own files with times and addresses |
| 3. Assign the tier | Hour 1 | The sender, checked by counsel | Tier A, B or C is written beside the list |
| 4. Tell the CEO what went out, to whom and what you plan to ask | Hour 1 for tiers A and B; day 1 for C | The relationship owner | The CEO has heard it from you, plainly, before hearing it from anyone else |
| 5. Send a written deletion request to each recipient | Day 1 | The sender | Each request went as a new message, identifying the email by date, time and subject, with nothing quoted or attached |
| 6. Ask each recipient to confirm deletion, forwards included | Day 1 | The sender | Confirmations, or their absence, are logged with dates |
| 7. Send the five-line replacement, if the CEO still wants the introduction | Day 1, after step 4 | The partner of record | The CEO has approved the wording |
| 8. Bring in counsel: the fund's own, and the company's if the CEO wants | Day 1 | Fund counsel | Counsel has the recipient list and tier, not the overshared material itself |
| 9. Record the incident | Day 2 | Counsel or compliance | The record holds dates, recipients, tier, the CEO's decision and confirmations, and none of the overshared content |
| 10. Fix the cause | Day 2 | Whoever owns the template | The template, intake form or habit that let the detail in has changed |

Step 5 has a contractual hook. Section 4.4 of the sample agreement says: "On written request or termination, each Receiving Party will return or delete the other Party's Confidential Information, except records needed for legal obligations, reward accounting, dispute evidence or routine inaccessible backups." Whether a given email counts as the sender's confidential information under the agreement it actually signed is a reading for counsel; section 8 of the program terms says the signed agreement governs confidentiality. Either way, the written request is the step that leaves a record.

Write the request the way SourceX asks people to write when they report a security concern on its trust page: "Please do not include passwords, personal information or confidential customer records." Identify the message; never repeat what it said. A deletion request that restates the revenue figure has simply sent it again.

**Method note.** The checklist was assembled on 28 October 2026 from sections 1.6, 3.3, 4.2, 4.4 and 4.5 of SourceX's unsigned sample partner agreement (version 2026-10-19), sections 2, 4 and 8 of the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's process and trust pages and the Microsoft and Google help pages on recalling mail. It has not been tested against incident data, and no figures on how often referral emails overshare have been published.

## A replacement message with five lines in it

The replacement should be shorter than anyone expects. It needs only what lets SourceX identify the company and reach the person who decides; the company describes itself when it applies.

1. The CEO's name, and that the CEO asked for the introduction.
2. One line on what the conversation is about, in the CEO's own words.
3. Who is making the introduction: the partner of record.
4. The CEO's work email.
5. The date.

Illustrative. A generic fund, an invented email and an invented company. A fund partner's original introduction ran to 410 words. Counsel sorted it line by line:

| Item in the original | Tier | What happens to it |
|---|---|---|
| "Their 2025 revenue was just under the number in the last board deck" | B | Deleted; deletion requested |
| Names of the company's three largest customers | B | Deleted; deletion requested |
| A screenshot of the company's ticket queue, attached | A | Deleted; deletion request names the file |
| "They are quietly exploring a sale next year" | B | Deleted; deletion requested; the CEO told first |
| "Founded in 2009, on the same ticketing system ever since" | C | Dropped; the company can say it in its application |
| The CEO's name and work email | Keep | Lines 1 and 4 |
| "She wants to understand how licensing her support records would work" | Keep | Line 2, confirmed in the CEO's words |

The replacement ran to five lines, approved by the CEO before it went. For the less fraught cousin of this problem, a correct email with a wrong company name, see [correcting a mistyped company name in a referral record](/guides/how-to-correct-a-mistyped-company-name-in-a-referral-record).

## The CEO's decisions after a slip

The checklist hands three decisions to the CEO, because the information is the company's and SourceX's screening page says the CEO authorizes a licensing discussion.

**Whether the introduction goes ahead.** Some CEOs shrug; some withdraw. A withdrawal ends it: record the date, send nothing further, and still finish the deletion requests. The process page says the company controls whether to proceed, so the fund does not argue the point.

**Who else is involved.** If tier A material included personal data, the company's own privacy lead or counsel may want to take over the questions; [the referral conversation with a privacy officer](/guides/the-referral-conversation-with-a-privacy-officer) covers that handoff. If privileged material was in the email, [keeping privileged material out of referral discussions](/guides/how-to-keep-privileged-material-out-of-data-referral-discussions) applies, and counsel leads.

**Who speaks next.** The CEO may prefer to apply directly. Section 2 of the terms lets SourceX communicate directly with a referred company without affecting valid attribution, so a CEO who takes over is not cutting the partner out. The published terms do not address an introduction that had to be resent; credit is decided from dated records, and SourceX decides how they read.

What the CEO never has to decide is publicity. The incident is not a story for an LP letter, a newsletter or a conference anecdote that could identify the company; section 4.5 of the sample bars disclosing non-public deal details without written authorization, and the company's own wishes come first.

The incident record itself belongs with counsel. Kept in the layered way described in [how to limit access to referral notes inside a fund](/guides/how-to-limit-access-to-referral-notes-inside-a-fund), it holds the dates, the recipients, the tier and the CEO's decision, and nobody outside that small group can open it.

## What a correction cannot reach

- **Backups and retained copies.** The sample agreement's own deletion clause excepts routine inaccessible backups and records kept for legal or accounting reasons. A deletion confirmation means the visible copies are gone, not every copy.
- **Recipients outside any agreement.** A co-investor copied in error may delete as a courtesy, but nothing in your agreement with SourceX binds them.
- **Tools on the receiving end.** Automatic forwarding rules, shared mailboxes and summary features in a recipient's own systems can copy a message before anyone reads it. You cannot see them, so ask about forwards explicitly.
- **The relationship.** A CEO who learns that board figures went to a third party may trust the fund less, whatever the cleanup; telling them early and plainly is the part you control.
- **Legal duties.** This checklist does not say whether a breach notice, a contractual notice or anything else is owed. Your counsel reads your documents; the company's counsel reads the company's.
- **Prevention data.** No one has published how often referral emails overshare or which controls prevent it best. Count your own incidents by tier for a year and see whether step 10 is working.

A related but different question, who owns the messages sitting in a company's own mailbox, is answered in [who owns emails sent to a company](/questions/who-owns-emails-sent-to-a-company); and when the files arrive in the other direction, unasked, see [what to do when someone sends confidential files unasked](/guides/what-to-do-when-someone-sends-confidential-files-unasked). More guides are in the [guides hub](/guides), and the overall process is on [how it works](/how-it-works).

## 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 the cleanup is done and the CEO still wants the conversation, send the five-line replacement from a [registered partner account](/register), check the company against [SourceX's screening criteria](/who-qualifies) and read the [program terms](/terms) on how credit is decided from dated records.

Cleaning up an overshared introduction is a referral matter; evaluating SourceX as a company to invest in is a separate one, and materials for that can be requested 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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/terms
- https://support.microsoft.com/en-us/outlook/mail/how-to-recall-an-email-in-outlook-requirements-limitations-steps
- https://support.google.com/mail/answer/2819488?hl=en
- https://refer.sourcex.si/how-it-works
- https://sourcex.si/trust
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
