A quarterly cleanup that improves referral data quality: a five-dimension record audit in which every fix is a new dated entry, nothing is edited or back-dated, and no SourceX decision moves

Short answer

Referral CRM data quality is how far a colleague who has never worked a record can trust it without asking anyone: every company, decider, permission and step present, in the allowed form, consistent with itself, current and traceable to where it came from. Once a quarter, test every open record and a sample of closed ones on those five dimensions, and repair each defect by adding a dated correction entry. Never edit, back-date or resubmit. The cleanup changes what your record says about itself and nothing SourceX has decided.

Visual briefFull-size diagram
An Illustrative dumbbell chart of one quarterly audit of 48 referral records: completeness defects fall from 9 found to 2 still open, validity from 14 to 0, consistency from 5 to 1 and timeliness from 11 to 4, while accuracy stays at 3, marked flagged, never rewritten. A strip beneath reads uniqueness: run the dedup rule, and SourceX decisions changed: 0.
Illustrative audit of a generic consultancy's records. Counts are invented and match the worked example on this page.

This is for the operations lead at a partner firm whose referral records are a few months old and starting to drift.

Why referral records decay between quarters

Nobody sets out to keep a bad record. Four ordinary things degrade one:

  • Companies change hands. Once an acquisition closes, the acquirer's CEO decides for the company, and a decider field confirmed last spring may name someone with no authority today.
  • Free text creeps into fixed fields. "Approved-ish", "won" and "with legal" appear where a stage or a portal label belongs.
  • Evidence moves. A permission row points to an email in a mailbox that was archived when someone left.
  • People leave. The relationship owner named on a record may no longer work at your firm.

The stakes are higher than tidiness. Section 2 of the terms says attribution is decided from dated records, including written introduction evidence, and section 7 sends disputes to SourceX with supporting evidence. Your records are the evidence your firm would rely on. Overwriting a field to make it look right destroys the very history that made it evidence, which is why every fix in this routine is an addition.

Five quality dimensions, applied to a referral record

The UK government's Data Quality Framework measures data on six dimensions: completeness, uniqueness, consistency, timeliness, validity and accuracy (our paraphrase), and it sets no universal standard, because different uses call for different combinations. A referral record needs five of them in this audit. Uniqueness, one record per company, already has its own routine in the deduplication rule for legal entities and brand names, so the quarterly audit runs that rule rather than repeating it.

DimensionWhat it means for a referral recordA typical defect
CompletenessThe facts every open record needs are thereA decider with no date confirmed
ValidityEach value takes the allowed formA stage typed as "nearly there"
ConsistencyFields agree with each otherThe person who gave permission is not the decider
TimelinessFacts are still currentA decider confirmed before the company was acquired
AccuracyFacts match their sourceA pointer to a message that no longer opens

The audit sits beside other routines without replacing them: quiet records are sorted by the stalled or closed rules, introductions made outside the portal by the monthly manual reconciliation, files that never belonged in the CRM by the attachment boundary review, and day-to-day freshness by the date-filed upkeep routine. The cleanup checks what all of them left behind and corrects only your firm's own statements.

The quarterly record audit checklist

Before the first check, write down the terms version in force on the audit date (2026-10-22.2 today) and whether section 11 lists any change since the last audit. Then run twelve checks across every open record and ten closed records chosen at random.

CodeDimensionTestIf it fails, add an entry thatSigns
C1CompletenessOpen record names the legal entity, its decider and the date the decider was confirmedSupplies the missing fact with its source, or reads "unknown, asked on" a date by a named ownerRelationship owner
C2CompletenessEach submitted introduction carries its portal reference and submission timeCopies the reference as the portal shows it, or flags that none existsOperations lead
V1ValidityThe stage field holds a value from your stage dictionaryRestates the stage in the dictionary's word, with the original left visibleCoordinator
V2ValidityReward status is written in the portal's own words with the date it was readRecords the label as displayed and today's dateCoordinator
V3ValidityMoney appears only where the status reads PaidMarks any figure on an Estimated, Eligible or Approved row as superseded and excluded from reportsOperations lead
K1ConsistencyThe person who gave the introduce permission is the decider named on the company rowNotes the mismatch for the operations lead; nothing is renamedOperations lead
K2ConsistencyParent and subsidiary links match in both directionsAdds the missing link, so the group's single cap can be readCoordinator
T1TimelinessEvery open fact that needs a check-by date has one, and none is overdueRecords the missing or overdue date and hands the fact back to the daily upkeep; the audit does not re-check itOperations lead
T2TimelinessNo acquisition, merger or sale of the company was announced since the last auditNames the decider now: the target's CEO before closing, the acquirer's CEO afterRelationship owner
T3TimelinessThe relationship owner still works at your firm and still holds the relationshipNames the new owner, and the record moves under the manager transfer checklistOperations lead
A1AccuracyEach sampled permission pointer opens its message, and the message says what the row saysReads "evidence missing since" a date; no copy is recreatedOperations lead
A2AccuracyEach sampled fit answer carries a source tag that matches where it came fromRe-tags it, or marks it "source unknown"Relationship owner

The samples of ten, for closed records, pointers and fit answers, are starting points, not program rules; set your own sizes and write them at the top of the audit log.

Correct by adding: the shape of a correction entry

A correction entry is one dated line appended to the record. It names the check code, the field, what the field said, what the record now holds, the source of the new fact and who added it. The original line stays where it was, visible and unchanged.

Four things a correction never does:

  1. Edit or delete the original line. A wrong value is superseded, not erased.
  2. Back-date. The entry carries the day it was written, even when the fact it records is older. If the date the fact became true matters, add it as a separate "as of" date with its own source.
  3. Resubmit. No introduction is sent to SourceX a second time to refresh a date or repair a field.
  4. Touch SourceX's side. An outcome, a status label or a credit decision recorded by SourceX is copied, never improved.

One more boundary: the audit is not a reason to contact a company. If a fact can only come from the CEO and no open step with the CEO's permission already covers asking, the field stays "unknown" with an owner and a date.

Who runs the audit, who signs, and what goes up a level

The operations lead runs the audit in the last week of the quarter and keeps the log. Relationship owners answer C1, T2 and A2 from correspondence they already hold. A second person, never the one who added an entry, signs each entry before the log closes.

Three findings go straight to the operations lead:

  • Missing evidence on a submitted introduction (C2 or A1). It cannot be rebuilt, so the record says so plainly.
  • A sign of earlier contact between the company and SourceX, such as a line saying the CEO "spoke to them last year". Section 3 of the terms treats a company with any earlier application, relationship or valid introduction as a duplicate, and SourceX makes that call in duplicate review. The entry records what was found, not a conclusion.
  • A terms change since the last audit. Someone reads the changed section before the next introduction goes out.

One quarter's audit at a 25-person consultancy (Illustrative)

Illustrative. A generic firm with invented records; no outcomes implied.

The firm audits 38 open records and 10 closed ones, 48 in all, and finds 42 defects. Entries correct 32 of them; 10 remain open at the end of the week.

DimensionDefects foundStill open after the auditWhy the open ones stay open
Completeness92Two deciders are unknown; each has an owner and a date, and nobody wrote to the companies
Validity140Stage words and portal labels restated; three Estimated figures marked superseded
Consistency51A CFO is recorded as giving permission; the operations lead is reviewing it with the relationship owner
Timeliness114Two acquisitions missed during the quarter now name the new deciders; four overdue check-by dates are back with the daily upkeep
Accuracy33Three pointers lead to a deleted mailbox; each is flagged, never rewritten
SourceX decisions0 changed0Nothing in the audit touches them

The accuracy row is the uncomfortable one, and it should be. A routine that could make those three defects disappear would be a routine that rewrites evidence.

What a quarterly cleanup cannot fix

  • It sees only your firm. Another partner's claim, or an earlier contact between SourceX and the company, is outside your records; overlapping cases are SourceX's to decide.
  • Lost evidence stays lost. The audit can say a message is missing; it cannot bring it back.
  • Clean is not qualified. A flawless record does not make a company fit, and it earns nothing on its own. Fit, rights and demand are settled in SourceX's review, and the company's CEO decides whether to proceed.
  • No benchmark exists. Nobody has published defect rates for referral records. Track your own by check code, quarter on quarter, with the sample size beside each figure.

Related operations guides are collected 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.

Once your records pass the quarter's checks, register as a partner if your firm has not signed yet, screen the next company against who qualifies and note the program terms version at the top of the next audit log.

  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

Why not simply correct a wrong field in place?

Because the record is evidence. SourceX decides credit from dated records, and a field that was quietly overwritten can no longer show what your firm knew and when. A correction entry fixes what the record says today and keeps the history that makes it worth trusting.

Can the cleanup reopen a referral that SourceX did not credit?

No. The audit corrects your firm's own statements about its records. It never resubmits an introduction, never re-sends one to SourceX to refresh a date and never changes an outcome SourceX recorded. If you hold earlier dated evidence, the route is the dispute process in section 7 of the terms, with the evidence as it stood.

How large a sample should the accuracy checks use?

There is no published benchmark. Start with ten permission pointers and ten fit answers a quarter, raise the sample if a check finds more than one defect, and record the sample size beside the result so quarters can be compared.

Sources

  1. refer.sourcex.si/terms
  2. gov.uk/government/publications/the-government-data-…
  3. refer.sourcex.si/how-it-works
  4. refer.sourcex.si/who-qualifies

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