# Referral CRM data quality: a quarterly audit | SourceX

Canonical: https://refer.sourcex.si/guides/a-quarterly-cleanup-that-improves-referral-data-quality
Last updated: 2026-11-04

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.

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](/guides/a-crm-deduplication-rule-for-legal-entities-and-brand-names), so the quarterly audit runs that rule rather than repeating it.

| Dimension | What it means for a referral record | A typical defect |
|---|---|---|
| Completeness | The facts every open record needs are there | A decider with no date confirmed |
| Validity | Each value takes the allowed form | A stage typed as "nearly there" |
| Consistency | Fields agree with each other | The person who gave permission is not the decider |
| Timeliness | Facts are still current | A decider confirmed before the company was acquired |
| Accuracy | Facts match their source | A 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](/guides/the-difference-between-a-stalled-referral-and-a-closed-one), introductions made outside the portal by the monthly [manual reconciliation](/guides/how-to-reconcile-manual-introductions-with-portal-activity), files that never belonged in the CRM by the [attachment boundary review](/guides/how-to-avoid-building-a-shadow-data-room-in-your-crm), and day-to-day freshness by the [date-filed upkeep routine](/guides/how-to-keep-a-referral-pipeline-current-with-limited-staff). 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.

| Code | Dimension | Test | If it fails, add an entry that | Signs |
|---|---|---|---|---|
| C1 | Completeness | Open record names the legal entity, its decider and the date the decider was confirmed | Supplies the missing fact with its source, or reads "unknown, asked on" a date by a named owner | Relationship owner |
| C2 | Completeness | Each submitted introduction carries its portal reference and submission time | Copies the reference as the portal shows it, or flags that none exists | Operations lead |
| V1 | Validity | The stage field holds a value from your [stage dictionary](/guides/a-stage-model-for-sourcex-referrals-that-does-not-imply-revenue) | Restates the stage in the dictionary's word, with the original left visible | Coordinator |
| V2 | Validity | Reward status is written in the portal's own words with the date it was read | Records the label as displayed and today's date | Coordinator |
| V3 | Validity | Money appears only where the status reads Paid | Marks any figure on an Estimated, Eligible or Approved row as superseded and excluded from reports | Operations lead |
| K1 | Consistency | The person who gave the introduce permission is the decider named on the company row | Notes the mismatch for the operations lead; nothing is renamed | Operations lead |
| K2 | Consistency | Parent and subsidiary links match in both directions | Adds the missing link, so the group's single cap can be read | Coordinator |
| T1 | Timeliness | Every open fact that needs a check-by date has one, and none is overdue | Records the missing or overdue date and hands the fact back to the daily upkeep; the audit does not re-check it | Operations lead |
| T2 | Timeliness | No acquisition, merger or sale of the company was announced since the last audit | Names the decider now: the target's CEO before closing, the acquirer's CEO after | Relationship owner |
| T3 | Timeliness | The relationship owner still works at your firm and still holds the relationship | Names the new owner, and the record moves under the [manager transfer checklist](/guides/when-a-referral-moves-between-partner-managers) | Operations lead |
| A1 | Accuracy | Each sampled permission pointer opens its message, and the message says what the row says | Reads "evidence missing since" a date; no copy is recreated | Operations lead |
| A2 | Accuracy | Each sampled fit answer carries a source tag that matches where it came from | Re-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.

| Dimension | Defects found | Still open after the audit | Why the open ones stay open |
|---|---|---|---|
| Completeness | 9 | 2 | Two deciders are unknown; each has an owner and a date, and nobody wrote to the companies |
| Validity | 14 | 0 | Stage words and portal labels restated; three Estimated figures marked superseded |
| Consistency | 5 | 1 | A CFO is recorded as giving permission; the operations lead is reviewing it with the relationship owner |
| Timeliness | 11 | 4 | Two acquisitions missed during the quarter now name the new deciders; four overdue check-by dates are back with the daily upkeep |
| Accuracy | 3 | 3 | Three pointers lead to a deleted mailbox; each is flagged, never rewritten |
| SourceX decisions | 0 changed | 0 | Nothing 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](/guides).

## 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](/register) if your firm has not signed yet, screen the next company against [who qualifies](/who-qualifies) and note the [program terms](/terms) version at the top of the next audit log.

## Sources

- https://refer.sourcex.si/terms
- https://www.gov.uk/government/publications/the-government-data-quality-framework/the-government-data-quality-framework
- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
