Run the eight rules below in order and stop at the first one that matches. This page is for the operations lead at a consultancy, accounting firm, agency or fund who keeps the firm's referral records and has to say, every week, which quiet rows are still live. Stage names come from the stage dictionary; this page decides only whether any closing event has happened yet.
Two mistakes a quiet row invites
A quiet row tempts people in two opposite directions. Nobody has published how often either happens.
| Mistake | What it looks like (Illustrative) | What it costs |
|---|---|---|
| Calling a live referral closed | A row is archived on day 50 because the CEO has not replied; the company applies on day 71 | Nobody reads the dashboard, the notes showing when and how the introduction was made get deleted, and a colleague may approach the company as if it were free |
| Calling a closed referral stalled | The CEO wrote "not for us" on day 20, but the row still says chasing | More messages to a CEO who has already answered, and a pipeline report that counts a dead row |
| Treating a lapsed window as a stall | Day 104, no application, and the row says follow up next week | Effort on an introduction the terms no longer credit, since section 2 ties credit to an application inside the 90 days |
| Treating review time as a stall | An application on day 18 and the dashboard label unchanged for weeks | Pressure on a company whose next steps belong to SourceX, measured against a duration nobody published |
Two fields on the record: the referral's status and your outreach
Most trackers squeeze two different facts into one dropdown. Split them.
- Referral status is set by evidence other people produce: the CEO, SourceX, a payout, the calendar. It reads Moving, With SourceX, Stalled or Closed, and the rules below fill it in.
- Outreach is your firm's own choice: Active, Paused or Stopped. You may stop at any time, for any reason. Stopping writes nothing into the status.
The usual pairing is Stalled with outreach Stopped: you asked the CEO one question, heard nothing, and now wait for the window to decide.
Around those two fields, the record holds only what the rules need. The unsigned sample of the Channel Partner Agreement says an introduction record identifies the company, domain, partner, opportunity, introduction method and timestamps (section 3.3). Add the date an application appeared and where you saw it, the dashboard label copied as displayed with the date you read it (partners follow their own referral through generic stages or reference codes, section 4.6), the next step with its holder and due date, and a closing-event field that stays blank until a closing event exists. When one does, the field records its type, its date, who produced it and a pointer to the evidence. The record never holds the company's files, samples or logins, the CEO's private reasons, or any amount before Paid.
Ticketing tools show why that field matters. Atlassian's support articles explain that Jira counts an issue as resolved only when it sits in the Done status category and carries a resolution value, so an issue marked completed with an empty resolution still triggers the unresolved-issues warning when a version is released (our paraphrase). A status word is not a closing: "Closed" in a referral dropdown means nothing until the closing-event field points at evidence.
The status transition decision rules
Evaluate every open record against these rules from the top. The first rule that matches sets the status, and the rules below it are not read.
| Rule | First match when the record shows | Status it sets | Evidence produced by | Your next move |
|---|---|---|---|---|
| R1 | A written no or withdrawal from the CEO, or a call with the CEO noted the same day | Closed by the CEO | The company's CEO | Set outreach to Stopped and record the decline without its reasons; only the CEO reopens it |
| R2 | A SourceX outcome that ends the referral: not credited after duplicate review, a reward canceled as ineligible, or a no-deal notice the CEO chose to share | Closed by SourceX | SourceX | Stop outreach; if you hold earlier dated evidence, log a dispute in its own field and send it once under section 7 |
| R3 | The reward reads Paid and the money has arrived | Closed by payout, still adjustable | SourceX | Reconcile the cash and keep the reward records |
| R4 | More than 90 days since the recorded introduction, with no verified application shown | Closed by the calendar | The window itself | Stop outreach; later calls and messages change nothing |
| R5 | A verified application is shown and no outcome has been reported | With SourceX | The company applied; SourceX holds the next steps | Read the dashboard on your set day and send the company nothing about pace |
| R6 | A named holder and a due date that has not passed, including a date the company asked for | Moving | Whoever holds the step | Nothing until the date |
| R7 | Before any application, a step whose date has passed or which nobody holds | Stalled, on your side or the company's | Nobody yet | Your side: reassign today. The company's side: one question to the CEO |
| R8 | No step anyone can name | Stalled, unnamed | Nobody | Name a step, or set outreach to Stopped and let R4 close the record |
Why the order matters. Closing events sit above every open state because they outrank a pending date: a CEO's no on day 30 ends a referral whose application was due on day 40. R5 sits above R6 and R7 because once the company has applied, your own due dates stop governing anything; the steps that follow belong to the company and SourceX.
Notes on three rules.
- R2. SourceX's company process page says a company whose deal does not close receives a no-deal notice and its declined data is deleted. Section 2.6 of the partner agreement adds: "An expired or declined unclosed deal creates no purchase or referral reward merely because time, introductions or review were involved." That notice goes to the company, and partners see generic stages, so it may reach you late or never. Do not ask the CEO to forward it.
- R4. Count from the introduction date in your record; where it differs from SourceX's, SourceX's dated records decide (terms, section 2). Assessment, exclusive holds, acceptance review and Closing run on clocks of their own that never extend attribution (agreement, section 3.2).
- R5. SourceX's process page gives companies targets for some deal steps, for example that commercial feedback "usually takes 7–14 days; that is a target, not a promise". Those timings describe the company's deal, whose events a partner cannot see, so none of them is a stall date for your record.
Moves the rules never allow: Stalled to Closed because you are tired of waiting; Closed by the CEO back to open because you sent another message; Closed by the calendar back to open because the company applied later (record the application, and leave credit to SourceX); With SourceX to Stalled because the review feels long; and Closed by payout to final, since a later cut to the company's payout means the reward is recalculated proportionately on the reduced payout.
Six quiet records, run through the rules (Illustrative)
Illustrative. Generic companies and invented dates; no outcome is implied beyond what each row says.
| Record | What the file shows today | First match | Status | Next move |
|---|---|---|---|---|
| A | Introduced on day 0; on day 20 the CEO asked to talk again after the company's March close, a date beyond day 90 | R6 now, R4 from day 91 | Moving, then closed by the calendar | Nothing before the CEO's date; the window will close the record first |
| B | Introduced on day 0; the CEO said the COO would apply by day 30; it is day 41 and nothing shows | R7 | Stalled, the company's side | One question to the CEO, then outreach Stopped if no answer comes |
| C | Application shown on day 18; the dashboard label unchanged for seven weeks | R5 | With SourceX | Read the dashboard monthly |
| D | Dashboard shows not credited after duplicate review; your firm believes its introduction came first | R2 | Closed by SourceX | Send the dated evidence once under section 7; the status stays closed unless SourceX changes its decision |
| E | Day 97 and no application; the relationship owner had a warm call with the CEO last week | R4 | Closed by the calendar | Note the call; it changes nothing |
| F | The COO says the company is not doing this; the CEO has said nothing | R7 | Stalled, the company's side | Ask the CEO once; a no from anyone else does not trigger R1 |
Record F is easy to get wrong. The CEO authorizes a licensing discussion for the company, so only the CEO's answer closes the record; a COO's view is a reason to ask the CEO, not a closing event.
A closed record that moves later (Illustrative). Record G read Paid after SourceX paid the company $400,000 on its first qualifying transaction; the reward was $70,000 (USD 50,000 plus 5%, the greater of the two 2026 measures). If that payout is later cut to $240,000, the record stays closed by payout, but the reward is recalculated on the same formula to $62,000, and the $8,000 already paid above that is adjusted. A reversal cuts the reward in step with the payout; it never raises it.
Who moves a record, and the one thing a partner closes
The operations lead runs the rules weekly and writes the first-match rule beside each status. Only the relationship owner speaks to the CEO, and only the partner of record, who signed the Channel Partner Agreement before submitting, asks SourceX about the referral. A step stalled on your side is reassigned the same day, as the next-step owner register shows. A step stalled on the company's side gets one question to the CEO; escalating without repeated messages covers that message and what follows it. A record with SourceX is never escalated by elapsed time, and a disputed R2 outcome travels in its own field while the status stays closed.
A partner can close exactly one thing: its own outreach. Everything else on the record waits for the CEO, SourceX, a payout or the calendar.
Reconciling and keeping closed records
Monthly. Re-run the rules on every record, open and closed, and compare each status with the dashboard label stored beside it; for anything SourceX produces, its label wins. A record marked Closed with an empty closing-event field goes back through the rules.
Retention. The agreement's return-or-delete clause makes an exception for records needed for reward accounting and dispute evidence (section 4.4), and it says a dispute must not erase original evidence (section 3.3). Keep the introduction record, the closing event with its pointer, and any dispute file. Free-text notes follow your firm's policy, and a CEO's private reasons never enter the record; the decline record guide stores a no without them.
Reopening. Only a new dated event from a closer reopens a record: the CEO raising the subject again, SourceX changing an outcome after a dispute, or a later transaction with the same company. For a later transaction, remember that a parent and its subsidiaries count as one referred company, so the USD 50,000 floor applies only to that company's first qualifying transaction.
Reporting. Count open and closed records separately, and show stalled rows by side. Never add stalled rows into anything that reads like value; until a reward reads Paid, there is no amount to add.
Where the rules misfire
- Outcomes you never see. Partners receive generic stages or reference codes, so a record can read With SourceX after the company already has its no-deal notice. Read the partner dashboard and the status glossary; do not ask the company.
- Ownership changes. If the company is acquired, its own CEO decides until the deal closes and the acquirer's CEO decides afterward. A new CEO is not a closing event; it changes who can produce R1.
- Several partners. When more than one partner knows the company, only one introduction can be credited, and SourceX settles overlapping cases in duplicate review. Your record learns the result only through R2 or R5.
- Untested rules. No figures exist for how often each rule fires. Log the first-match rule weekly for a quarter before drawing conclusions. When to stop messaging altogether is covered in inactive referral follow-up, a company that named its own date in the follow-up after a request for more time, and more operations guides sit in the guides library.
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 next weekly review, register as a partner if your firm has not yet signed the Channel Partner Agreement, recheck open companies against who qualifies, and keep the version of the program terms that your 90-day arithmetic follows.