This is for the solo advisor, the two-person practice or the operations person with a few hours a week for referrals. A firm with enough open records and colleagues to justify a standing review can add an exception-only weekly meeting; the routine here is the upkeep that keeps records honest between meetings, or in place of them. One word on terms: the pipeline here is your list of introductions, not the data pipeline that prepares a company's records, which is SourceX's work.
Why rereading every record is the wrong kind of work
Google's site reliability book has a name for the chore. It describes toil as work that is manual, repetitive, automatable, tactical and without lasting value, and that grows with the size of what is being run; a task that leaves the system in the same state it found it was probably toil (our paraphrase). A weekly read-through of twenty referral records, seventeen of which have not changed, fits that description exactly. It grows with every record you add and leaves the pipeline as it was.
The routine below grows with events and dates instead. A record nobody needs to touch this week stays shut, and a record with three facts due gets those three checked, not reread from the top.
How fast each part of a referral record goes stale
Facts decay at different speeds, and a few never decay on a schedule at all. Set the next check when you write the fact, using the column on the right.
| Fact in the record | What makes it stale | Check-by date, set when the fact is written | Where the truth lives |
|---|---|---|---|
| Introduction date and day 90 | Nothing changes it, but day 90 passes | Day 91 after the written introduction: is a verified application showing? | Your dated introduction record and SourceX's dashboard |
| The CEO's answer | Only the CEO saying something new | None scheduled; a "not now" takes the date the CEO named | The CEO's own words, dated |
| The next action | Its date passing | The action's own date | Your record |
| SourceX's status | SourceX moving the stage or reward status | 14 days after the last reading, while the referral is open | The dashboard, copied as displayed with the reading date |
| Who decides for the company | An acquisition, a new CEO, a group change | When news arrives, and at each stage change | A public announcement or the CEO |
| The contact route | A bounce or a new address | The day the bounce or change arrives | The person, confirmed through a channel you already trust |
| Questions waiting on the company | Your own stop date | The day you said you would stop asking | Your record |
| Your payment and tax details | Changes on your side | The day the reward status first reads Eligible | Your account with SourceX |
Three rows rest on published rules. Credit goes to the first valid introduction of a new company within the 90-day window, and only when that company files a verified application (terms, section 2), so the day-91 check is the one that cannot slip. The dashboard shows each referral's stage and a reward status of Estimated, Eligible, Approved or Paid, and shows Paid only after an actual payout has been recorded (how it works), which is why you copy the label as displayed rather than paraphrase it. And payment needs your payment and tax details on file (terms, section 5), so check them the day Eligible first appears, not the day you expect money.
The record itself stays small. The sample Channel Partner Agreement gives a partner the information reasonably needed to follow its own referral and reward, in generic stages or reference codes (section 4.6), and an introduction record needs only what section 3.3 lists: the company, its domain, the Partner, the opportunity, how the introduction was made and when. Nothing from a client's systems belongs in it.
The date-filed upkeep routine
Think of a folder rack with one slot per day: each record is filed behind the next date one of its facts needs you, and on any given day you open only that day's slot. Four parts make it run.
- File on arrival. When a CEO replies, a status changes in front of you or an email bounces, write the new fact into the record that day with its date and source, then reset any check-by date it affects. It takes a couple of minutes and spares you rebuilding the history from your inbox later.
- Pull what is due. One saved view lists every record with any check-by date on or before today. Work it daily, or twice a week if you hold only a handful of records. Each due fact gets exactly one of four moves: confirm it is still true and set its next date; change it, writing the new fact and its date; close the record because an ending has arrived, such as a CEO's no, day 91 with no verified application, a SourceX outcome or a recorded payment; or hand it up to the partner of record or SourceX, as the next section describes.
- Read the dashboard on one day. Batch the fortnightly status readings for introduced referrals so the portal is opened once, not once per record.
- Nothing else. No record is opened because a week has passed.
When you fall behind, clear the backlog in this order: day-91 checks first, because a lapsed record left open misleads everyone who reads it; then dates a CEO named, because a promise to a company is at stake; then dashboard readings; then everything else.
Method note. The check-by intervals, the four moves and the backlog order are this page's design, built on SourceX's terms and how-it-works page and the sample agreement, read on 2026-10-27. They have not been tested against outcomes, and the 14-day reading interval is a starting point, not a SourceX rule.
Who owns each check, and where it goes when it cannot be cleared
Even a one-person practice has two roles. The upkeep owner files, pulls and reads; the relationship owner holds every fact that only the CEO can change. When they are the same person, write down which hat each fact belongs to anyway, because it decides who acts when you are away.
A fact goes up the chain in four cases:
- It cannot be confirmed after two passes. It goes to the partner of record, who decides whether to close the record or ask once more. When a referral has no named next-step owner covers stalls of this kind.
- A second claim appears on the same company. Only one introduction can be credited, and SourceX settles overlapping cases in duplicate review; send your dated record and stop.
- A status moves backward. Record the label, the date and any reason SourceX gives.
- You disagree with a decision. Write to SourceX with the referral details and supporting evidence, as section 7 of the terms sets out.
Name a backup who opens the same due view on the same days. Because the dates live in the records, the view itself is the handover.
Four weeks of upkeep in a two-person practice (Illustrative)
Illustrative. A generic advisory practice; invented records and counts.
| Week | Open records | Filed on arrival | Facts due | Moves | Minutes |
|---|---|---|---|---|---|
| 1 | 14 | 2 | 6 | 3 confirm, 2 change, 1 close at day 91 with no application | 22 |
| 2 | 13 | 1 | 3 | 2 confirm, 1 hand up after a status moved backward | 12 |
| 3 | 14 | 3 | 7 | 5 confirm, 1 change, 1 close after a CEO's no | 25 |
| 4 | 13 | 1 | 2 | 2 confirm | 6 |
Over four weeks the practice checked 18 facts and filed 7 arrivals. A full weekly read-through would have opened every record every week, 54 record openings for the same month, and found most of them unchanged. Week 3 carried the batched dashboard reading for five introduced referrals, which is why it ran longest.
Closing a record and keeping only what policy allows
When a record reaches its ending, strip it to its code, the ending and the dates. Section 4.4 of the sample agreement allows keeping what legal obligations, reward accounting or dispute evidence need, and your firm's retention policy decides for how long. The rules for telling a closed record from a stalled one are in the difference between a stalled referral and a closed one. Comparing your records against the portal line by line is a separate monthly job, described in reconciling manual introductions with portal activity, and questions you are waiting on the company to answer have their own board in tracking questions waiting on the company.
Where a date-filed routine fails
- A wrong date at entry. A check-by date typed a month late hides a record for a month. Read each new date back once when you set it.
- Events that never arrive. A CEO can change without any news reaching you. The stage-change check on who decides catches some of these, not all.
- Nobody opens the view. Holidays and busy weeks break the routine silently. The backup is not optional.
- Low volume tempts skipping. With three records it feels unnecessary, until day 91 passes unseen.
- No benchmarks exist. SourceX's terms give no typical stage durations, and no data on upkeep time has been published. Log your own minutes per week, facts past their check-by date and the age of your oldest dashboard reading.
The rest of the referral operations series is listed 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 the next introduction goes into the rack, make sure you are registered as a partner and have signed, screen the company against who qualifies, and note which version of the program terms your check-by dates follow.