# Referral next step ownership: a triage register | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-referral-has-no-named-next-step-owner
Last updated: 2026-11-04

When nobody owns the next step on a referral, nothing pauses: the 90-day attribution window keeps running from the recorded introduction, and the CEO's interest cools. Find the last dated event, decide whose side the next step is on, and act only on your own side. A step at your firm gets a named colleague who acknowledged it in writing, and a date. A step at the company belongs to whoever the CEO names, so you ask the CEO once. A step at SourceX is SourceX's; you read your dashboard and never fill the gap yourself.

This page is for the operations lead at a consultancy, accounting firm, managed service provider or agency whose people introduce companies to SourceX. It starts from a referral where the CEO has already agreed to be introduced and something has gone quiet.

## How a step loses its owner after the yes

Most ownerless steps follow a handful of patterns. They are illustrations, not measured frequencies; nobody has published how often each one happens.

| Gap | What it looks like (Illustrative) | Whose side the step is on |
|---|---|---|
| The delegated yes | The CEO says "my COO will handle it," and nobody tells the COO | The company's, once the CEO names someone |
| The absent colleague | The person at your firm who holds the relationship goes on leave or leaves | Yours |
| Two advisors, no submitter | The company's banker and its accountant each assume the other sent the introduction | Yours or the other advisor's; only one introduction can be credited, so agree who submits |
| The wrong expectation | The company waits to hear from SourceX, while SourceX's published process starts with the company's own short application | The company's |
| The unread inbox | The introduction went to a shared address the CEO never checks | The company's, through a contact the CEO chooses |

The absent-colleague case has its own preventive routine in [the platform manager's handoff before leave](/guides/the-platform-manager-s-handoff-when-taking-leave). The two-advisor case is better settled before anyone submits; the [duplicate-claims guide](/guides/how-to-prevent-duplicate-claims-before-they-reach-sourcex) covers it.

## What an ownerless week costs

**Days from a fixed window.** The agreement's Schedule A credits an introduction only if the company submits a verified application within 90 days of the recorded introduction, and the terms add that the window does not extend because contact protection under the agreement continues. The agreement also keeps the deal's own deadlines on separate clocks: assessment, exclusive holds, acceptance review and Closing never lengthen attribution. Every day a step sits unowned comes out of the same 90.

**A yes that ages.** A yes that was never submitted has no window running yet, but it grows stale. A CEO who agreed in June may have different priorities by September, so confirm a long-stalled yes before submitting anything on the strength of it.

**Trust.** A CEO who agreed and then heard nothing can read the silence as carelessness. The cost lands on the relationship you will want the next time.

## The owner-and-date action register

The register holds one line per next action, and every line answers three questions: whose side is it on, who has agreed to own it, and by when.

| Field | What goes in it | Rule |
|---|---|---|
| Line | A short code such as L1 | One action per line |
| Action | A verb and an object, such as "submit the written introduction" | "Follow up" is not an action |
| Side | Your firm, the company or SourceX | Decides who may own the line |
| Named owner | One person | On the company's side, only someone the CEO named; on SourceX's side, simply "SourceX" |
| Acknowledged | The date the owner confirmed in writing that the line is theirs | A message sent to someone is not an acknowledgment |
| Due | A calendar date | If no date is possible, the line is parked with a review date |
| Closes on | The evidence that ends the line | A dated message, a portal reference, or a dashboard label read on a stated date |
| If late | The one move allowed | Your side: reassign. Company side: one ask to the CEO. SourceX side: a question to SourceX about your own referral |

The acknowledgment column is the one most trackers lack. SourceX's partner agreement applies the same standard to its own notices: an automated send event alone does not count as acknowledgment of receipt. A colleague copied on an email, or a COO the CEO mentioned in passing, has not taken a line until they say so.

Task software already encodes half of this. Asana explains that a task can have only one assignee, though many collaborators, and traces the choice to Apple's idea of a directly responsible individual (our paraphrase of its "Why one assignee?" page). The register adds the other half: some referral lines can only be owned by people you do not manage, so it records who named them and when they agreed.

**The register for the case in the graphic (Illustrative).** A logistics firm's CEO agreed on Monday of week 1 and said someone on her team would pick it up, without saying who.

| Line | Action | Side | Named owner | Acknowledged | Due | Closes on |
|---|---|---|---|---|---|---|
| L1 | Submit the written introduction | Your firm | The relationship owner | W1 Mon | W1 Tue | Portal reference, W1 Tue |
| L2 | Send the CEO SourceX's process and what you will not do | Your firm | The relationship owner | W1 Mon | W1 Tue | Sent email, W1 Tue |
| L3 | Complete the company's application | The company | Blank until W3 Thu, then the COO, named by the CEO | W3 Thu, by the COO | The date the COO gave | Dashboard shows the application, W4 Tue |
| L4 | Review the company | SourceX | SourceX | Not needed | Not yours to set | A stage change on the dashboard |
| L5 | Read the dashboard and record the label | Your firm | The operations lead | W1 Mon | Every Friday | Label and reading date written down |
| L6 | Check for an application before day 90 | Your firm | The operations lead | W1 Mon | Day 85 | Application shown, or the line closes as lapsed |

Line L3 is where the ten working days went. "Someone on my team" named nobody; the register showed a blank owner on a company-side line, and the only permitted move was one message to the CEO. It went out on Wednesday of week 3, the CEO named the COO on Thursday, the COO confirmed that day, and the company applied the following Tuesday, day 22 of the 90.

## Triage in four questions

Run these whenever a line has no owner, no acknowledgment or a missed date.

1. **What is the last dated event, and who produced it?** The CEO's yes, your submission, a dashboard label, a reply.
2. **Whose side is the next step on?** Use SourceX's published process as the map: after an introduction the company applies; SourceX checks fit, proposes and aligns the deal; the company and SourceX sign. Your firm owns only its own messages, the submission and reading the dashboard.
3. **Is a named person holding it, and did they acknowledge it?**
4. **What is the date, and what happens if it passes?**

| Triage answer | The move |
|---|---|
| Your side, no owner | Name one colleague today, get a written acknowledgment and set a date |
| Company's side, no owner named by the CEO | One message to the CEO asking who on their side will take the company's next step, or whether they would rather pause; record the answer and contact nobody else at the company |
| SourceX's side | Record the dashboard label and the date you read it; if it has not moved and the CEO asks, put one question to SourceX about your own referral and expect a generic stage in reply |
| No step anyone can name | Close the line as stalled, keep the record and leave the CEO free to restart |

## Escalation that never goes around the CEO

- **Inside your firm.** An overdue line goes to the operations lead, who reassigns it or closes it.
- **At the company.** Escalate only to the CEO, and once. Never push through a board member, an investor or another executive; a fund partner on the board cannot decide the company's step, and pressing staff behind the CEO's back undermines the yes you already have. If the CEO has changed their mind, [what happens when an owner changes course](/questions/what-happens-if-the-owner-changes-their-mind-after-an-introduction) covers the rest.
- **With SourceX.** Questions about your own referral are fine. Disputes about credit go to SourceX with supporting evidence, as section 7 of the terms sets out. Never hand SourceX company material to unstick a review.
- **Never do the company's step for it.** You do not fill in its application, describe its systems or gather its files. The agreement gives a partner no authority to share company records, and SourceX may work with the company directly without you.

## Three stalled referrals, repaired (Illustrative)

Illustrative. Generic companies and firms, invented details, no outcomes implied beyond what each row says.

| Ref | What the register showed | Triage answer | Line written | What happened |
|---|---|---|---|---|
| S1 | A logistics firm's CEO said someone on her team would pick it up, then ten working days of silence | Company's side, no owner named | One email to the CEO; the CEO named the COO, who acknowledged | The company applied on day 22 of the window, the case in the graphic |
| S2 | A colleague left, and a five-week-old written yes from a CEO was never submitted | Your side, with no window running yet but a stale yes | The operations lead reassigned the line; the new owner asked the CEO whether the yes still stood | The CEO reconfirmed, and the introduction went in that day |
| S3 | The dashboard has shown the same stage for weeks, and the CEO asks you what is happening | SourceX's side | Label and reading date recorded; the CEO reminded that SourceX deals with the company directly; one question to SourceX about the referral | A generic stage confirmed, and nothing further for you to do |

## Keeping the register honest

- **Weekly.** Every open line has a named owner, an acknowledgment date and a due date. A line missing any of the three goes back through triage.
- **Closing lines.** A line closes only on its evidence. The referral itself closes when the CEO stops, the window passes with no application, SourceX reports an outcome or the reward is paid.
- **Retention.** How long closed lines stay is your firm's policy. The agreement's return-or-delete clause makes an exception for records needed for reward accounting and dispute evidence; free-text notes can go once a line closes.

When chasing should stop altogether, [inactive referral follow-up rules](/guides/when-to-stop-following-up-on-an-inactive-referral) set the limits, and a company that asked for time is handled in the [follow-up after a request for more time](/guides/a-referral-follow-up-after-a-company-has-asked-for-more-time).

## Where an owner-and-date register falls short

- **It cannot create an owner at the company.** Only the CEO can.
- **Acknowledgment is a step people skip.** If it turns into a formality, the column means nothing.
- **It sees nothing inside SourceX.** Partners follow their referral through generic stages or reference codes, and the register cannot do better.
- **Its effect is unmeasured.** Whether the register shortens the time from a CEO's yes to an application is untested. Log the yes, the submission, each acknowledgment and the application date for two quarters; no figures are published.
- **Networks need more.** A firm whose referrals come through many people may also need one person who owns escalations across all of them, as [an escalation owner for a referral network](/guides/a-referral-network-needs-an-escalation-owner) describes.

More operations guides are in the [guides library](/guides), and the partner-side stages are 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.

Before the next introduction leaves your firm, [register as a partner](/register) if you have not, screen the company against [who qualifies](/who-qualifies), and date line L6 from the 90-day window in the [program terms](/terms).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/how-it-works
- https://asana.com/resources/why-one-assignee
