How to keep a referral pipeline current with limited staff: a date-filed upkeep routine in which every fact gets a check-by date when it is written, only the records due today are opened, and anything that arrives is filed the same day

Short answer

Give every fact in a referral record its own check-by date at the moment you write it, and open a record only when one of those dates arrives or something new comes in about it. The 90-day attribution window, the CEO's latest answer, the next action and SourceX's dashboard status each go stale on a different clock. A ten-minute pass through the facts due that day, plus filing anything that arrives on the day it arrives, keeps a small pipeline current without anyone rereading every row.

Visual briefFull-size diagram
A date-filed folder rack with tabs for days 1 to 14 of an Illustrative month and Illustrative referral cards standing behind their next check-by dates; the tab for day 9, today, is raised and its three cards are pulled forward, labeled day 91 check, next action due and dashboard reading, while every other card stays filed and unopened.
Illustrative records and dates. Each card sits behind the next day one of its facts needs checking, as the routine on this page describes.

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 recordWhat makes it staleCheck-by date, set when the fact is writtenWhere the truth lives
Introduction date and day 90Nothing changes it, but day 90 passesDay 91 after the written introduction: is a verified application showing?Your dated introduction record and SourceX's dashboard
The CEO's answerOnly the CEO saying something newNone scheduled; a "not now" takes the date the CEO namedThe CEO's own words, dated
The next actionIts date passingThe action's own dateYour record
SourceX's statusSourceX moving the stage or reward status14 days after the last reading, while the referral is openThe dashboard, copied as displayed with the reading date
Who decides for the companyAn acquisition, a new CEO, a group changeWhen news arrives, and at each stage changeA public announcement or the CEO
The contact routeA bounce or a new addressThe day the bounce or change arrivesThe person, confirmed through a channel you already trust
Questions waiting on the companyYour own stop dateThe day you said you would stop askingYour record
Your payment and tax detailsChanges on your sideThe day the reward status first reads EligibleYour 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.

  1. 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.
  2. 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.
  3. Read the dashboard on one day. Batch the fortnightly status readings for introduced referrals so the portal is opened once, not once per record.
  4. 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.

WeekOpen recordsFiled on arrivalFacts dueMovesMinutes
114263 confirm, 2 change, 1 close at day 91 with no application22
213132 confirm, 1 hand up after a status moved backward12
314375 confirm, 1 change, 1 close after a CEO's no25
413122 confirm6

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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should a CEO's yes be reconfirmed every few weeks to keep the record fresh?

No. A yes stays current until the CEO withdraws it, and asking again to refresh a record puts pressure on the company for your convenience. The record changes only when the CEO says something new.

Does the routine need CRM software?

No. A spreadsheet with one column per check-by date works, sorted or filtered by the earliest date. The rule that matters is that every fact gets its next date at the moment it is written.

What if the person who runs the routine is away?

Name a backup who opens the same due view on the same days. Because each record already carries its own next dates, the backup needs no briefing beyond where the view is and who to hand things up to.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/how-it-works
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. sre.google/sre-book/eliminating-toil

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment